HPE6-A86 · Question #63
You have configured the following on a Core-1 HPE Aruba Networking CX switch for primary and secondary ISP connectivity: Core-l(config)# ip route 0.0.0.0/0 10.1.251.2 Core-l(config)# ip route…
The correct answer is D. When the 10.1.251.2 is no longer in the routing table. Static route failover occurs only when the preferred static route is removed from the routing table. If the next hop 10.1.251.2 remains reachable at Layer 2/Layer 3 on the local link, the switch keeps the primary default route installed even if there is an upstream failure, so…
Question
You have configured the following on a Core-1 HPE Aruba Networking CX switch for primary and secondary ISP connectivity:
Core-l(config)# ip route 0.0.0.0/0 10.1.251.2 Core-l(config)# ip route 0.0.0.0/0 10.1.252.2 distance 10 The default route via 10.1.251.2 stopped working, and no failover happened. The ISP reported a broken fiber on the path of an upstream device. In what condition should the route failover to the 10.1.252.2 router?
Options
- AWhen the uplink-failure-detection enables 10.1.252.2 route.
- BWhen the BFD session terminates on 10.1.251.2.
- CWhen the default route graceful-restart timer expires.
- DWhen the 10.1.251.2 is no longer in the routing table.
How the community answered
(39 responses)- A18% (7)
- B3% (1)
- C8% (3)
- D72% (28)
Explanation
Static route failover occurs only when the preferred static route is removed from the routing table. If the next hop 10.1.251.2 remains reachable at Layer 2/Layer 3 on the local link, the switch keeps the primary default route installed even if there is an upstream failure, so the secondary route is not selected until the primary route is no longer present in the routing table.
Topics
Community Discussion
No community discussion yet for this question.