350-501 · Question #360
The NOC team must update the BGP forwarding configuration on the network with these requirements: - BGP peers must establish a neighborship with NSF capability and restart the session for the…
The correct answer is D. Set the BGP restart-time to 120 seconds and the stalepath-time to 360 seconds. To implement NSF and BGP graceful restart, the BGP restart-time must be set to 120 seconds for session re-establishment, and the stalepath-time must be set to 360 seconds to control the retention of stale routes.
Question
The NOC team must update the BGP forwarding configuration on the network with these requirements:
- BGP peers must establish a neighborship with NSF capability and
restart the session for the capability to be exchanged after 120 seconds.
- BGP peers must delete routes after 360 seconds of inactivity.
Which action meets these requirements?
Options
- ASet the BGP restart-time to 120 seconds and the BGP ha-mode sso to 360 seconds.
- BSet the stalepath-time to 120 seconds and the BGP restart-time to 360 seconds.
- CSet the BGP ha-mode sso to 120 seconds and the BGP restart-time to 360 seconds.
- DSet the BGP restart-time to 120 seconds and the stalepath-time to 360 seconds.
How the community answered
(22 responses)- A9% (2)
- B18% (4)
- D73% (16)
Why each option
To implement NSF and BGP graceful restart, the BGP restart-time must be set to 120 seconds for session re-establishment, and the stalepath-time must be set to 360 seconds to control the retention of stale routes.
The `BGP ha-mode sso` command relates to Stateful Switchover for high availability and does not control the duration for which stale BGP routes are retained after inactivity during a graceful restart.
This option incorrectly assigns the 120-second value to `stalepath-time` and 360 seconds to `BGP restart-time`, reversing the required timings for each parameter.
This option incorrectly uses `BGP ha-mode sso` for the stalepath requirement and assigns the incorrect time to `BGP restart-time`.
The `BGP restart-time` parameter defines how long a router signals its peers to retain its routing information during a graceful restart before BGP sessions are re-established, correctly aligning with the 120-second requirement. The `stalepath-time` parameter specifies the maximum duration a graceful restart-capable peer will keep stale routes from a restarting peer before deleting them due to inactivity, fulfilling the 360-second requirement.
Concept tested: BGP Graceful Restart and Stalepath Timer
Source: https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_bgp/configuration/xe-16/irg-xe-16-book/bgp-graceful-restart-llgr.html
Topics
Community Discussion
No community discussion yet for this question.