From a PCC router’s CLI, you can create LSP templates
to define a set of LSP attributes to apply to PCE-initiated LSPs.
Any PCE-initiated LSPs that provide a name match with the regular
expression (regex) name specified in the template automatically inherit
the LSP attributes that are defined in the template. By associating
LSPs (through regex name matching) with a specific user-defined LSP
template, you can automatically turn on (or turn off) LSP attributes
across all LSPs that provide a name match with the regex name specified
in the template.
When auto-bandwidth is enabled, LSP auto-bandwidth parameters
must be configured from the router, even when the LSP has been delegated.
Under no circumstances can the NorthStar Controller modify the bandwidth
of an externally-controlled LSP when auto-bandwidth is enabled. The
PCC enforces this behavior by returning an error if it receives an
LSP update for an LSP that has auto-bandwidth enabled. Currently,
there is no way to signal through PCEP when auto-bandwidth is enabled,
so the NorthStar Controller cannot know in advance that an LSP has
auto-bandwidth enabled. However, when auto-bandwidth is enabled by
way of a template, then the NorthStar Controller knows that the LSP
has auto-bandwidth enabled and disallows modification of bandwidth.
The following configuration example shows how to define the
regex-based LSP name for a set of LSP “container” templates
that you can deploy to apply specific attributes to any LSPs on the
network that provide a matching LSP name.
Create the templates under the lsp-external-controller-pccd hierarchy to specify the regex-based character string to be used
to identify the LSPs whose attributes you want to update.
- Create a name matching scheme to identify the NorthStar
Controller provisioned (PCE-initiated) LSPs to which you want to apply
specific link protection attributes.
To specify that any PCE-initiated LSP that provides a
name match with the prefix PCE-LP-* will
inherit the LSP link-protection attributes defined in the LINK-PROTECT-TEMPLATE template,
configure the following statement from the PCC router CLI:
[edit protocols mpls lsp-external-controller pccd]
user@PE1# set pce-controlled-lsp PCE-LP-* label-switched-path-template LINK-PROTECT-TEMPLATE
To specify that any PCE-initiated LSP that provides a
name match with the prefix PCE-AUTOBW-* will inherit the LSP auto-bandwidth attributes defined in the AUTO-BW-TEMPLATE template,
configure the following statement from the PCC router CLI:
[edit protocols mpls lsp-external-controller pccd]
user@PE1# set pce-controlled-lsp PCE-AUTOBW-* label-switched-path-template AUTO-BW-TEMPLATE
- Create the templates that define the attributes you want
to apply to all PCE-initiated LSPs that provide a name match.
Define link-protection attributes for the LINK-PROTECT-TEMPLATE template.
[edit protocols mpls ]
user@PE1# set label-switched-path-template LINK-PROTECT-TEMPLATE template
user@PE1# set label-switched-path-template LINK-PROTECT-TEMPLATE hop-limit 3
user@PE1# set label-switched-path-template LINK-PROTECT-TEMPLATE link-protection
Define auto-bandwidth attributes for the AUTO-BW-TEMPLATE template.
[edit protocols mpls ]
user@PE1# set label-switched-path-template AUTO-BW-TEMPLATE template
user@PE1# set label-switched-path-template AUTO-BW-TEMPLATE auto-bandwidth adjust-interval 300
user@PE1# set label-switched-path-template AUTO-BW-TEMPLATE auto-bandwidth adjust-threshold 20
user@PE1# set label-switched-path-template AUTO-BW-TEMPLATE auto-bandwidth minimum-bandwidth 10m
user@PE1# set label-switched-path-template AUTO-BW-TEMPLATE auto-bandwidth maximum-bandwidth 100m
user@PE1# set label-switched-path-template AUTO-BW-TEMPLATE auto-bandwidth adjust-threshold-overflow-limit 5
user@PE1# set label-switched-path-template AUTO-BW-TEMPLATE auto-bandwidth adjust-threshold-underflow-limit 5
- Create LSPs in NorthStar by specifying LSP names based
on the regex-based name defined in Step 1 above.
- Verify the LSP configuration on the PCC router.
user@PE1> show mpls lsp detail
