Configure an S series switch to accelerate OSPF route convergence

8

The following network changes affect OSPF route convergence.
A device detects that the peer link is down and the neighbor relationship becomes invalid.
A new link-state advertisement (LSA) is generated and flooded.
The Link State Database (LSDB) is updated. A new route is calculated through the Shortest Path First (SPF) routing algorithm and delivered to the Forwarding Information Base (FIB) table.

To accelerate OSPF aggregation, you can perform the following operations on a switch:
Set a Hello interval and a Dead interval on the peer device or configure the BFD to rapidly detect failures.
Set spf-schedule-interval (of which the default value is 5, in seconds) to a smaller value to shorten the SPF calculation interval.
Set the LSA generation interval to a smaller value.
Set the LSA arrival check interval to a smaller value.
Run the ospf trans-delay command in an interface view to speed up LSA flooding.

Other related questions:
How is convergence performance of Layer 2 multicast accelerated on an S series switch?
When the network topology changes, Layer 2 multicast detects the topology change by responding to notification messages of ring network protocols. Layer 2 multicast sends General Query messages in the VLAN where the topology changes to re-collect group member relationships. Ring network protocols include STP, MSTP, RRPP, Smart Link, and SEP. The ring network protocols supported by the switches excluding the S1700 are as follows: - STP: supported by all switch models - MSTP: supported by all switch models excluding the S2700SI - RRPP: supported by all switch models excluding the S1720 and S2700SI - Smart Link: supported by all switch models excluding the S1720, S2700SI, S2710SI, and S2700EI - SEP: supported by all switch models excluding the S1720, S2700SI, S2710SI, and S2700EI

Configure the priority of an OSPF route on an S series switch
The routing protocols may share and select the routing information because a switch may run multiple dynamic routing protocols simultaneously. In this case, a priority should be set for each routing protocol. When different protocols find multiple routes to the same destination, the route discovered by the protocol with a higher priority is preferred. On an S series switch, you can run the preference command in the OSPF process view to configure the OSPF priority. Perform the following operations: 1. Run the ospf [ process-id ] command in the system view to enter the OSPF process view. 2. Run the preference [ ase ] { preference | route-policy route-policy-name } * command to configure the OSPF priority. The parameters are described as follows: ase: indicates the priority of the AS-External route. preference: indicates the OSPF route priority. A smaller value indicates a higher priority. route-policy route-policy-name: indicates the priority for specified routes in the routing policy. The default OSPF priority value is 10. When an ASE is specified, the default OSPF priority is 150. For example, set the priority of routes in OSPF process 100 to 150 as follows: [HUAWEI] ospf 100 [HUAWEI-ospf-100] preference 150

Why configure OSPF route tag on S series switches
For S series switches supporting OSPF, the OSPF router tag is applied to VPNs and prevents loops of Type 5 LSAs in CE dual-homing networking. If the tag of a received Type 5 LSA is the same as the router tag of OSPF on a PE, the PE neglects this LSA when calculating routes. When a CE is connected to two PEs, PE1 generates a Type 5 LSA based on the imported BGP route and sends the LSA to the CE, and the CE forwards the LSA to PE2. The OSPF route takes precedence over the BGP route, so PE2 replaces the BGP route with the OSPF route. As a result, a loop occurs. If the route tag is configured on a PE, when the PE receives an LSA with the same route tag as its own route tag, it neglects this LSA, avoiding loops. By default, the route tag is calculated using the BGP AS number. If BGP is not configured, the route tag is 0. In OSPF public network instances, router tags cannot be used to prevent loops but can be used as a filtering condition in a policy. When setting the router tag of ASE-LSAs and NSSA-LSAs, not the following: The route-tag command is used in the OSPF multi-instance scenario. The default tag command is used in the OSPF public network instance scenario. The import-route tag command can be used in either of the preceding scenarios.

Configure OSPF to filter received routes on S series switches
The Open Shortest Path First (OSPF) is a routing protocol based on the link status. Unlike the routing protocols using the distance-vector (D-V) algorithm, OSPF ensures topology consistency and provides loop-free routes. To configure OSPF to filter routes, run the filter-policy import command. The record about the LSA of a route filtered out exists in the OSPF database. The OSPF process does not add the route to the routing table but the LSA of the route is advertised. That is, the peer end can receive the route. The filter-policy export command can only be used to configure OSPF to filter imported external routes to be advertised. OSPF also supports the filtering of routes carried in Type 3 LSAs on ABRs. This feature enables ABRs to filter routes when advertising Type 3 LSAs between OSPF areas. Only the packets with prefixes meeting requirements can be transmitted from one area to another. In this way, the incoming and outgoing packets of an area are controlled.

Precedence of external routes imported by OSPF on S series switches
When an S series switch runs OSPF, you can run the import-route command in the OSPF process view to import external routes. The routes imported using this method are OSPF ASE routes and default precedence is 150.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top