Creating Templates with Junos OS Groups to Apply Attributes to PCE-Initiated Label-Switched Paths
From the Path Computation Client (PCC) router’s
command line interface, you can use the Junos OS groups
statement with label-switched path (LSP) templates to define a set
of LSP attributes to apply to PCE-initiated LSPs. Any PCE-initiated
LSP that provides a name match with the regular expression (regex)
name that is specified in the template automatically inherits the
LSP attributes that are specified in the template. Thus, by associating
PCE-initiated LSPs with a 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 that is specified in the template.
The following example show how you can use templates to apply auto-bandwidth and link-protection attributes to LSPs. For example, 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. A 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 the LSP has auto-bandwidth enabled. However, if auto-bandwidth is enabled by way of a template, the NorthStar Controller knows that the LSP has auto-bandwidth enabled and disallows modification of bandwidth.
To configure and apply groups to assign auto-bandwidth and link protection attributes to label-switched paths: