Automatic Creation of RSVP-TE LSP Mesh
Page 126 7450 ESS MPLS Guide
8. Changing between node-protect and “no node-protect” (link-protect) values in the LSP
level fast-reroute option.
9. Changing LSP primary or secondary path priority values (setup-priority and hold-
priority).
10. Changing LSP primary or secondary path class-type value and primary path backup-class-
type value.
11. Changing LSP level and path level hop-limit parameter value.
12. Enabling/disabling primary or secondary path record and record-label options.
This feature is not supported on a manual bypass LSP.
P2MP Tree Level Make-before-break operation is supported if changes are made to the following
parameters on LSP-Template:
1. Changing Bandwidth on P2MP LSP-Template.
2. Enabling Fast -Re-Route on P2MP LSP-Template.
Automatic Creation of RSVP-TE LSP Mesh
This feature enables the automatic creation of an RSVP point-to-point LSP to a destination node
whose router-id matches a prefix in the specified peer prefix policy. This LSP type is referred to as
auto-LSP of type mesh.
The user can associate multiple templates with the same or different peer prefix policies. Each
application of an LSP template with a given prefix in the prefix list will result in the instantiation
of a single CSPF computed LSP primary path using the LSP template parameters as long as the
prefix corresponds to a router-id for a node in the TE database. Each instantiated LSP will have a
unique LSP-id and a unique tunnel-ID.
Up to five (5) peer prefix policies can be associated with a given LSP template at all times. Each
time the user executes the above command with the same or different prefix policy associations, or
the user changes a prefix policy associated with an LSP template, the system re-evaluates the
prefix policy. The outcome of the re-evaluation will tell MPLS if an existing LSP needs to be torn
down or if a new LSP needs to be signaled to a destination address that is already in the TE
database.
If a /32 prefix is added to (removed from) or if a prefix range is expanded (shrunk) in a prefix list
associated with a LSP template, the same prefix policy re-evaluation described above is
performed.
The trigger to signal the LSP is when the router with a router-id the matching a prefix in the prefix
list appears in the Traffic Engineering database. The signaled LSP is installed in the Tunnel Table
To Next Page
Loading...
