Change Details

FRRouting was initially installed only on routers (D4055), but it is also required on devservers (Ysul and Windriver) for OSPF to operate correctly and establish neighbor relationships. To address this, the FRR installation logic has been moved to the core role so it can be reused across both routers and devservers, avoiding duplication of the installation process. However, the FRR configuration itself remains separated, as routers and devservers have different routing requirements. Dedicated configuration files and Salt states are therefore still maintained in: ``` roles/router/frrouting ``` ``` roles/devserver/frrouting ``` while the shared installation logic is located in: ``` 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 OSPF added for route network Intranought:** The IntraNought network `172.27.27.0/27` is shared with Windriver and Ysul. On routers, two GRE tunnels (gre1 (windriver) and gre2(ysul)) 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, 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 and gre2 is left to its default value (10) ------------------------------------- **Configuration OSPF added: for active router to share default route** A new script, set-ospf-default-route.sh, was added in roles/router/frrouting/files/ to automate the OSPF default route advertisement according to the CARP state of the routers. When a router becomes CARP PRIMARY, the script configures FRRouting to advertise the default route through OSPF. This allows other nodes participating in the OSPF process, such as complector, to dynamically relearn the correct default gateway over the GRE tunnels. As a result, traffic is automatically redirected to the active router after a failover, without requiring manual static route modifications. This ensures routing continuity and keeps the infrastructure synchronized with the CARP state. OSPF configuration for IntraNought nodes, excluding routers, has been added to ``` roles/core/frrouting ``` So, the vmx0 interface on the routers is no longer configured as passive, because OSPF neighbor relationships must now be maintained with the IntraNought nodes in order to advertise and receive the default route dynamically. --------------------------------------------- Ref T2303

FRRouting was initially installed only on routers (D4055), but it is also required on devservers (Ysul and Windriver) for OSPF to operate correctly and establish neighbor relationships. To address this, the FRR installation logic has been moved to the core role so it can be reused across both routers and devservers, avoiding duplication of the installation process. However, the FRR configuration itself remains separated, as routers and devservers have different routing requirements. Dedicated configuration files and Salt states are therefore still maintained in: ``` roles/router/frrouting ``` ``` roles/devserver/frrouting ``` while the shared installation logic is located in: ``` 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 OSPF added for route network Intranought:** The IntraNought network `172.27.27.0/27` is shared with Windriver and Ysul. On routers, two GRE tunnels (gre1 (windriver) and gre2(ysul)) 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, 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 and gre2 is left to its default value (10) ------------------------------------- **Configuration OSPF added: for active router to share default route** A new script, set-ospf-default-route.sh, was added in roles/router/frrouting/files/ to automate the OSPF default route advertisement according to the CARP state of the routers. When a router becomes CARP PRIMARY, the script configures FRRouting to advertise the default route through OSPF. This allows other nodes participating in the OSPF process, such as complector, to dynamically relearn the correct default gateway over the GRE tunnels. As a result, traffic is automatically redirected to the active router after a failover, without requiring manual static route modifications. This ensures routing continuity and keeps the infrastructure synchronized with the CARP state. OSPF configuration for IntraNought nodes, excluding routers, has been added to ``` roles/core/frrouting ``` So, the vmx0 interface on the routers is no longer configured as passive, because OSPF neighbor relationships must now be maintained with the IntraNought nodes in order to advertise and receive the default route dynamically. --------------------------------------------- Ref T2303

FRRouting was initially installed only on routers (D4055), but it is also required on devservers (Ysul and Windriver) for OSPF to operate correctly and establish neighbor relationships. To address this, the FRR installation logic has been moved to the core role so it can be reused across both routers and devservers, avoiding duplication of the installation process. However, the FRR configuration itself remains separated, as routers and devservers have different routing requirements. Dedicated configuration files and Salt states are therefore still maintained in: ``` roles/router/frrouting ``` ``` roles/devserver/frrouting ``` while the shared installation logic is located in: ``` 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 OSPF added for route network Intranought:** The IntraNought network `172.27.27.0/27` is shared with Windriver and Ysul. On routers, two GRE tunnels (gre1 (windriver) and gre2(ysul)) 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, 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 and gre2 is left to its default value (10) ------------------------------------- **Configuration OSPF added: for active router to share default route** A new script, set-ospf-default-route.sh, was added in roles/router/frrouting/files/ to automate the OSPF default route advertisement according to the CARP state of the routers. When a router becomes CARP PRIMARY, the script configures FRRouting to advertise the default route through OSPF. This allows other nodes participating in the OSPF process, such as complector, to dynamically relearn the correct default gateway over the GRE tunnels. As a result, traffic is automatically redirected to the active router after a failover, without requiring manual static route modifications. This ensures routing continuity and keeps the infrastructure synchronized with the CARP state. OSPF configuration for IntraNought nodes, excluding routers, has been added to ``` roles/core/frrouting ``` So, the vmx0 interface on the routers is no longer configured as passive, because OSPF neighbor relationships must now be maintained with the IntraNought nodes in order to advertise and receive the default route dynamically. --------------------------------------------- Ref T2303