How to set the durations of the Hold timer and Keepalive timer of the BGP peer

10

You can run the peer timer command to set the durations of the Hold timer and Keepalive timer. This command specifies the timeout period of the BGP connection and the interval to send the Keepalive message. A longer timeout period can relieve the impact of link flapping, whereas a shorter timeout period makes the timer rapidly perceive link changes. After connections are established between two peers, the durations of the two timers are negotiated by the two peers and the shorter durations are adopted.

Other related questions:
On S series switches, what are the methods of defining the values of Hold and Keepalive timers on BGP peers
For S series switches that support BGP, the value of Hold and Keepalive timers can be set with the peer timer command. This command specifies the hold time when the BGP connection is interrupted and the interval for sending Keepalive messages. Large values of the two timers reduce the impact of link flapping, and small values enable the device to detect link changes. After the peer relationship is set up, the values of the two timers are negotiated by both peers, and the smaller ones are used.

How to set the ringing timer duration for the call forwarding on no reply (CFNR) service of the U1900?
The duration of the timer for triggering the CFNR service must be shorter than that of the ringing timer. Otherwise, the CFNR service cannot be triggered. The default duration of the timer for triggering the CFNR service is 20s and the default duration of the ringing timer is 60s. Commands for modifying timer settings: 1. To modify the duration of the timer for triggering the CFNR service for a single personal user, run the config modify cfnrtime type cfnr timelen xx dn xxxx command. In this command, xx indicates the new waiting time, which ranges from 5 to 50, in seconds, and the xxxx indicates the user number. 2. To modify the duration of the timer for triggering the CFNR service globally, run the config modify cfnrtime type cfnr timelen ** command. 3. To modify the ringing timer, run the config modify timerinterval pid os_pid_ccm timergroup 0 timerindex 17 interval command.

How to troubleshoot the fault of LDP session flapping due to the expiration of KeepAlive Hold timer
If the KeepAlive Hold timer expires, run the display mpls ldp session command to check whether KeepAlive messages are properly sent on the two ends of the LDP session. If not, the system is busy or faulty. If KeepAlive messages are properly sent but the peer end does not receive them, ping the transport address of the TCP connection with the peer end to check the forwarding status.

Why is the LDP GR duration in the log longer than 10 minutes, which is the interval of the MPLS Forwarding State Holding timer
After the GR restarter performs an active/standby switchover, LDP GR starts only after route GR is complete. The MPLS Forwarding State Holding timer is started immediately after the active/standby switchover but restarted when route GR is complete. In the log, the GR begin time is the time when the MPLS Forwarding State Holding timer is first started; the GR end time is the time when the MPLS Forwarding State Holding timer expires. Therefore, the LDP GR duration recorded in the log is the sum of the route GR duration and MPLS Forwarding State Holding timer interval (10 minutes).

How to troubleshoot the fault of LDP session flapping due to the expiration of Hello Hold timer
If the Hello Hold timer expires, run the display mpls ldp interface command to check whether Hello messages are properly sent on the two ends of the LDP session. If not, the system is busy or faulty. If Hello messages are properly sent but the peer end does not receive them, ping the address of the peer end to check the forwarding status.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top