MPLS and RSVP
7450 ESS MPLS Guide Page 153
The timer value can be configured in one minute increments, up to 4320 minutes (72 hours). Once
a timer has started, it can be modified using this command. If a new value is entered, then the
current timer is canceled (without reverting the LSP) and then restarted using the new value.
The no form of the command cancels any currently outstanding revert timer and causes the LSP to
revert to the primary path if it is up.
If the LSP secondary path fails while the revert timer is still running, the system cancels the revert-
timer and the LSP will thus revert to the primary path immediately. A user can manually force an
LSP to revert to the primary path while the revert-timer is still running, using the following tools
command:
tools>perform>router>mpls revert lsp lsp-name
This command forces the early expiry of the revert timer for the LSP. The primary path must be up
in order for this command to work.
Automatic Creation of an RSVP One-Hop LSP
Feature Configuration
The user first creates an LSP template of type one-hop:
config>router>mpls>lsp-template template-name one-hop-p2p
Then the user enables the automatic signaling of one-hop LSP to all direct neighbors using the
following command:
config>router>mpls>auto-lsp lsp-template template-name one-hop
The LSP and path parameters and options supported in a LSP template of type one-hop-p2p are
that same as in the LSP template of type mesh-p2p except for the parameter from which is not
allowed in a template of type one-hop-p2p. The show command for the auto-LSP will display the
actual outgoing interface address in the ‘from’ field. The full list of template parameters is shown
in the CLI Section. Also, the rules for adding or modifying the template parameters are as
described in 7.1.1.
Finally the auto-created one-hop LSP can be signaled over both numbered and unnumbered RSVP
interfaces.
Feature Behavior
Although the provisioning model and CLI syntax differ from that of a mesh LSP only by the
absence of a prefix list, the actual behavior is quite different. When the above command is
executed, the TE database will keep track of each TE link which comes up to a directly connected