MPLS and RSVP
7450 ESS MPLS Guide Page 227
Default no admin-group
Parameters group-name — Specifies the name of the group with up to 32 characters. The association of group
name and value should be unique within an IP/MPLS domain.
auto-bandwidth-multipliers
Syntax auto-bandwidth-multipliers sample-multiplier number1 adjust-multiplier number2
no auto-bandwidth-multipliers
Context config>router>mpls
Description This command specifies the number of collection intervals in the adjust interval.
Parameters sample-multiplier number1 — Specifies the mulitplier for collection intervals in a sample interval.
Values 1 — 511
Default 1
adjust-multiplier number2 — Specifies the number of collection intervals in the adjust interval.
Values 1 — 16383
Default 288
auto-lsp
Syntax auto-lsp lsp-template template-name {policy peer-prefix-policy [peer-prefix-policy...(upto
5 max)] | one-hop}
no auto-lsp lsp-template template-name
Context config>router>mpls
Description This command 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 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. This feature does not support the automatic
signaling of a secondary path for an LSP. If the user requires the signaling of multiple LSPs to the
same destination node, s/he must apply a separate LSP template to the same or different prefix list
that contains the same destination node. Each instantiated LSP will have a unique LSP-id and a
unique tunnel-ID. This feature also does not support the signaling of a non-CSPF LSP. The selection
of the no cspf option in the LSP template is thus blocked.
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.
To Next Page
Loading...
