Feature Requirements |
Series |
Models |
|---|---|---|
The static routes to participate in FRR must have different priorities configured. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When the number of load-balancing static routes exceeds an upper limit specified in a PAF file, the preferred static route may change after the active preferred route is modified or the active/standby switchover is performed twice. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Before you associate a static route with a BFD session, the session must have been created. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
If recursion depth-based static route selection is configured, the number of static routes for load balancing may decrease. As a result, static routes may fail to implement load balancing. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When configuring a static route, the following features are mutually exclusive: 1.BFD for static routes 2.NQA for static routes 3.Association between static routes and EFM 4.Permanent advertisement of static routes Determine which feature to use as required: BFD for static routes eNonebles a static route to be bound to a BFD session. After BFD for static routes is configured, the system can use a BFD session to detect the link status of a static route and determine whether to activate the route. NQA for static routes eNonebles an NQA test case to detect the link status of a static route. After NQA for static routes is configured, the system can determine whether to activate a static route based on the detection result. When BFD for static routes is not easy to configure or cannot be used, you can use NQA for static routes. Association between EFM and static routes eNonebles the system to respond to an interface Up or Down event that is triggered by changes in the EFM OAM extension status and determine whether to activate the static routes with this interface as their next hop outbound interface. This mechanism controls route advertisement and ensures that the traffic from the remote end can be correctly forwarded. Permanent advertisement of static routes eNonebles traffic to be forwarded over a specific path even when the path is uNonevailable. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
You can run the route recursive-lookup tunnel command to allow IPv4 VPN static routes with a public network next hop to recurse to a public network tunnel. After this command is run, the system preferentially recurses a static route to an IP route. If no matching IP route is available for recursion, the system does not recurse the static route to a tunnel. If a matching BGP route is available for recursion, the static route recurses to the BGP route. If a matching non-BGP route is available for recursion, the static route recurses to a tunnel based on the tunnel policy. If a matching network segment (non-host route) is available for recursion, the network segment address is used to recurse the static route to a tunnel. Therefore, the static route can recurse to a public network tunnel based on the next hop address only if a matching non-BGP route corresponding to the next hop is available. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |