300-415 · Question #103
A network administrator is tasked to make sure that an OMP peer session is closed after missing three consecutive keepalive messages in 3 minutes. Additionally, route updates must be sent every…
The correct answer is A. omp timers advertisement-interval 60 holdtime 180 graceful-restart-timer 43200. OMP timers control route update frequency, session timeout based on missed keepalives, and how long stale routing information is retained during a graceful restart.
Question
Options
- Aomp timers advertisement-interval 60 holdtime 180 graceful-restart-timer 43200
- Bomp timers advertisement-interval 1 holdtime 180 graceful-restart-timer 43200
- Comp timers advertisement-interval 1 holdtime 180 graceful-restart-timer 720
- Domp timers advertisement-interval 60 holdtime 60 graceful-restart-timer 720
How the community answered
(39 responses)- A77% (30)
- B8% (3)
- C13% (5)
- D3% (1)
Why each option
OMP timers control route update frequency, session timeout based on missed keepalives, and how long stale routing information is retained during a graceful restart.
The `advertisement-interval` is set to 60 seconds for route updates every minute, the `holdtime` is set to 180 seconds (3 minutes) to allow for three missed keepalives, and the `graceful-restart-timer` is set to 43200 seconds (12 hours) to retain stale routes during an outage.
The `advertisement-interval` is set to 1 second, but the requirement is for route updates every minute (60 seconds).
The `advertisement-interval` is set to 1 second, which is incorrect, and the `graceful-restart-timer` is 720 seconds (12 minutes), which is incorrect for a 12-hour requirement.
The `holdtime` is set to 60 seconds, which would close the session after only one missed keepalive, and the `graceful-restart-timer` is 720 seconds (12 minutes), which is incorrect for a 12-hour requirement.
Concept tested: OMP timer configuration
Source: https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/sdwan-xe-gs-book/m-sdwan-basic-config.html#Cisco_Concept.dita_e836ec27-d0d9-4cfc-a292-0b32e18d098e
Topics
Community Discussion
No community discussion yet for this question.