An administrator is implementing a floating static route on a Cisco IOS router to act as a backup path for a primary route learned dynamically via internal EIGRP (Administrative Distance 90) to the destination subnet . The administrator executes the following command:
`ip route 10.100.50.0 255.255.255.0 172.16.1.2 90`
While the primary EIGRP route remains active, traffic destined for is unexpectedly load-shared across both the dynamic route and the static route. Which configuration change will ensure that the static route functions exclusively as a backup route?
- Reconfigure the static route with an administrative distance greater than 90.Cevap
- BReconfigure the static route with an administrative distance lower than 90.
- CSpecify an exit interface instead of the next-hop IP address while keeping the administrative distance at 90.
- DAppend the overload parameter to the static route command string.
Cevap
Reconfigure the static route with an administrative distance greater than 90.
For a static route to act as a floating backup route, its administrative distance must be configured higher than the administrative distance of the primary route. Since internal EIGRP uses an AD of 90, configuring the static route with an AD of 90 causes both routes to share the same administrative distance, resulting in unexpected dual-path active insertion. Assigning an AD greater than 90 keeps the static route out of the routing table until the primary EIGRP route fails.
Adım Adım Çözüm
Anahtar Kavram
Floating Static Route Administrative Distance Calibration