Change Details

FRRouting was initially installed only on routers (D4055), but it is also required on devservers (ysul, windriver) for OSPF to work correctly and establish neighbor relationships. To address this, FRR installation and configuration have been moved to the core role so they can be reused across both routers and devservers. ``` roles/core/frrouting ``` A pillar has also been added to define router IDs per host, allowing them to be easily retrieved and avoiding hardcoding in State Salt. ``` pillar/core/frr.sls ``` ------------------------ **Configuration added : ** Add Salt configuration for FRRouting OSPF on routers and devservers. The IntraNought network will be shared to Windriver and Ysul. Two GRE tunnels (gre1 and gre2) are established over this network to provide direct point-to-point links between each router and Windriver and Ysul. OSPF is configured on gre1, gre2, and vmx0. However, OSPF neighbor relationships and route exchange take place only on gre1 and gre2, as these interfaces are explicitly set as non-passive using no ip ospf passive. The vmx0 interface remains passive. Each router has a unique OSPF router-id (RID) to ensure correct neighbor relationships. RID are not real IP addresses, but arbitrary 32 bits values. The OSPF cost for interface gre1 is left to its default (10) value for now and will be adjusted later depending on which router is active. Ref T2303

FRRouting was initially installed only on routers (D4055), but it is also required on devservers (ysul, windriver) for OSPF to work correctly and establish neighbor relationships. To address this, FRR installation and configuration have been moved to the core role so they can be reused across both routers and devservers. ``` roles/core/frrouting ``` A pillar has also been added to define router IDs per host, allowing them to be easily retrieved and avoiding hardcoding in State Salt. ``` pillar/core/frr.sls ``` ------------------------ **Configuration added:** Add Salt configuration for FRRouting OSPF on both routers and devservers. The IntraNought network is shared with Windriver and Ysul. On routers, two GRE tunnels (gre1 and gre2) are established over this network to provide direct point-to-point links between each router and the devservers. On devservers, a single GRE interface (gre1) is used to connect to the routers. OSPF is configured on gre1, gre2, and vmx0 on routers, and on gre1 on devservers. However, OSPF neighbor relationships and route exchange only occur on gre1 and gre2 (on routers), as these interfaces are explicitly set as non-passive using `no ip ospf passive`. The vmx0 interface remains passive. Each host (router and devserver) has a unique OSPF router-id (RID) to ensure proper neighbor relationships. Router IDs are not real IP addresses, but arbitrary 32-bit values. The OSPF cost for interface gre1 is left to its default value (10) for now and will be adjusted later depending on which router is active.. Ref T2303

FRRouting was initially installed only on routers (D4055), but it is also required on devservers (ysul, windriver) for OSPF to work correctly and establish neighbor relationships. To address this, FRR installation and configuration have been moved to the core role so they can be reused across both routers and devservers. ``` roles/core/frrouting ``` A pillar has also been added to define router IDs per host, allowing them to be easily retrieved and avoiding hardcoding in State Salt. ``` pillar/core/frr.sls ``` ------------------------ **Configuration added : **:** Add Salt configuration for FRRouting OSPF on both routers and devservers. The IntraNought network will beis shared towith Windriver and Ysul. TwoOn routers, two GRE tunnels (gre1 and gre2) are established over this network to provide direct point-to-point links between each router and Windriver and Ysulthe devservers. On devservers, a single GRE interface (gre1) is used to connect to the routers. OSPF is configured on gre1, gre2, and vmx0. on routers, and on gre1 on devservers. However, OSPF neighbor relationships and route exchange take place onlyonly occur on gre1 and gre2 (on routers), as these interfaces are explicitly set as non-passive using `no ip ospf passive`. The vmx0 interface remains passive. Each host (routerer and devserver) has a unique OSPF router-id (RID) to ensure correct neighbor proper neighbor relationships. Router IDs are not real IP addresses, but relationships. RID are not real IP addresses, but arbitrary 32 bits-bit values. The OSPF cost for interface gre1 is left to its default (10) value for now and will be adjusted(10) for now and will be adjusted later depending on which router is active.. Ref T2303