Table 1 describes the timers for an LDP session.
LDP Timer |
Description |
Suggestion |
---|---|---|
Hello send timer:
|
Used to send Hello messages periodically to notify a peer LSR of the local LSR's presence and establish a Hello adjacency. |
On an unstable network, decrease the value of a Hello send timer, speeding up network fault detection. |
Hello hold timer:
|
Used to exchange Hello messages periodically between two LDP peers to maintain the Hello adjacency. If no Hello message is received after the Hello hold timer expires, the Hello adjacency is torn down. |
On a network with unstable links or a large number of packets, increase the value of the Hello hold timer, preventing the LDP session from being torn down and set up frequently. |
Keepalive send timer |
Used to send Keepalive messages periodically, maintaining the LDP sessions. |
On an unstable network, set a smaller value for a Keepalive send timer, speeding up network fault detection. |
Keepalive hold timer |
Used to send LDP PDUs over an LDP session, maintaining the LDP session. If no LDP PDU is received after the Keepalive hold timer expires, the TCP connection is closed and the LDP session is terminated. |
On a network with unstable links, increase the value of the Keepalive hold timer, preventing the LDP session from flapping. |
Exponential backoff timer |
Started by an LSR that plays an active role after an LDP Initialization message sent by the LSR to another LSR that plays a passive role fails to be processed or parameters carried in the message are rejected. The LSR that plays the active role periodically resends an LDP Initialization message to initiate an LDP session before the Exponential backoff timer expires. |
|
When local and remote LDP sessions coexist, the timeout interval of the Keepalive hold timer of the local and remote LDP sessions must be the same.