A network administrator is configuring a backup floating static route to reach an external corporate subnet 172.31.50.0/24. The primary path to this destination is learned dynamically via External BGP (eBGP). During testing while the primary eBGP connection is fully operational, the administrator observes that traffic toward 172.31.50.0/24 is being forwarded across the backup static path rather than the primary link. Which static route command entry in the router configuration caused this improper failover behavior?
- ip route 172.31.50.0 255.255.255.0 192.168.12.2 15Cevap
- Bip route 172.31.50.0 255.255.255.0 192.168.12.2 25
- Cip route 172.31.50.0 255.255.255.0 192.168.12.2 90
- Dip route 172.31.50.0 255.255.255.0 192.168.12.2 110
Cevap
The command 'ip route 172.31.50.0 255.255.255.0 192.168.12.2 15' sets the administrative distance lower than eBGP, causing it to preempt the primary route.
Cisco IOS assigns default Administrative Distance values to evaluate route trustworthiness. External BGP (eBGP) routes carry a default AD of 20. To create a floating static backup route for an eBGP path, the trailing administrative distance argument in the 'ip route' command must be set higher than 20. Specifying an administrative distance of 15 makes the static route more preferred than the eBGP route (15 < 20), causing the router to immediately install the static path into the routing table even when the eBGP link is active.
Adım Adım Çözüm
Anahtar Kavram
Floating Static Route Administrative Distance relative to eBGP
Tahmini Süre:1m 30s