By default, a device cannot recurse static routes to SRv6 routes. In L3VPNv4 HoVPN over SRv6 BE, L3VPNv4 HoVPN over SRv6 TE Policy, EVPN L3VPN HoVPN over SRv6 BE or EVPN L3VPN HoVPN over SRv6 TE Policy scenarios, you can enable a device to recurse static routes to SRv6 routes to prevent traffic black holes.
In an L3VPNv4 HoVPN over SRv6 BE, L3VPNv4 HoVPN over SRv6 TE Policy, EVPN L3VPN HoVPN over SRv6 BE or EVPN L3VPN HoVPN over SRv6 TE Policyscenario, if the next hop of a default static route on the SPE is the SPE itself and the link between the SPE and the NPE fails, the UPE cannot detect the link fault. As a result, a traffic black hole occurs after traffic reaches the SPE. To resolve this problem, you need to specify the NPE's address as the next-hop address of the default static route on the SPE. In this manner, the validity of the static route depends on whether the link between the SPE and NPE is available. If the link fails, the default static route on the SPE becomes inactive. In addition, you need to enable the SPE to recurse static routes to SRv6 routes. This configuration allows the SPE to withdraw this inactive route when the SPE-NPE link fails so that the UPE can detect the route withdrawal and no longer sends traffic to the SPE, thereby preventing a traffic black hole.
The system view is displayed.
The device is enabled to recurse static routes to SRv6 routes.
The configuration is committed.