MPLS and RSVP
7210 SAS M, T, X, R6, Mxp MPLS Configuration Guide Page 169
separate RSVP neighbor. The user will have to enable BFD on each interface and RSVP will register
with the BFD session running with each of those neighbors independently
Similarly the disabling of BFD on the interface results in removing registration of the interface with
BFD.
When a BFD session transitions to DOWN state, the following actions are triggered. For RSVP
signaled LSPs, this triggers activation of FRR bypass/detour backup (PLR role), global revertive
(head-end role), and switchover to secondary if any (head-end role) for affected LSPs with FRR
enabled. It triggers switchover to secondary if any and scheduling of re-tries for signaling the primary
path of the non-FRR affected LSPs (head-end role).
The no form of this command removes BFD from the associated RSVP protocol adjacency.
Default no bfd-enable
hello-interval
Syntax hello-interval milli-seconds
no hello-interval
Context config>router>rsvp>interface
Description This command configures the time interval between RSVP hello messages.
RSVP hello packets are used to detect loss of RSVP connectivity with the neighboring node. Hello
packets detect the loss of neighbor far quicker than it would take for the RSVP session to time out
based on the refresh interval. After the loss of the of number keep-multiplier consecutive hello
packets, the neighbor is declared to be in a down state.
The no form of this command reverts to the default value of the hello-interval. To disable sending
hello messages, set the value to zero.
Default 3000 milliseconds
Parameters milli-seconds — Specifies the RSVP hello interval in milliseconds, in multiples of 1000. A 0 (zero)
value disables the sending of RSVP hello messages.
Values 0 — 60000 milliseconds (in multiples of 1000)
implicit-null-label
Syntax implicit-null-label [enable | disable]
no implicit-null-label
Context config>router>rsvp
Description This command enables the use of the implicit null label for all LSPs.
All LSPs for which this node is the egress LER and for which the path message is received from the
previous hop node over this RSVP interface will signal the implicit null label. This means that if the
egress LER is also the merge-point (MP) node, then the incoming interface for the path refresh
message over the bypass dictates if the packet will use the implicit null label or not. The same for a 1-
to-1 detour LSP.
To Next Page
Loading...
Need help?
General
