A GMPLS LSP is configured under config>router>gmpls>lsp name gmpls-uni. The optional gmpls-uni keyword indicates that the LSP is an RSVP signaled GMPLS LSP, which is profiled for the GMPLS UNI that is it uses the set of functions and CLI commands applicable to an overlay gLSP, instead of a peer model gLSP. Only overlay model gLSPs are supported; this is the default type of GMPLS LSP. The router can only act as an LER terminating a gLSP, and cannot switch a GMPLS that is it cannot act as a GMPLS LSR
GMPLS LSPs use the working path and protect path terminology from RFC 4872. Each gLSP configuration is composed of a working path and an optional protect path if end-to-end recovery is used.
Note that on-the-fly changes to an LSP or LSP path configuration are not allowed. This is because MBB is not supported for gLSPs. The LSP or LSP Path must be shut down to make configuration changes.
A GMPLS LSP (gLSP) is configured using the following CLI tree:
config
router
gmpls
lsp lsp-name [gmpls-uni]
no lsp lsp-name
to remote-uni-c-gmpls-router-id
switching-type {dcsc}
no switching-type
encoding-type {line}
no encoding-type
generalized-pid {ethernet}
no generalized-pid
e2e-protection-type {unprotected | 1toN | sbr}
no e2e-protection-type
protect-path path-name
no protect-path path-name
peer peer-gmpls-router-id
no peer
bandwidth signal-type rfc3471-name
no bandwidth exclude-srlg group-name [group-name...(upto 5 max)]
no exclude-srlg
segment-protection-type {unprotected | sbr | gr | sncp | prc}
no segment-protection-type
no shutdown
shutdown
revert-timer timer-value //1 to 1800 seconds, default 0
no revert-timer
retry-limit limit
no retry-limit
no shutdown
shutdown
working-path path-name
no working-path path-name
bandwidth signal-type rfc3471-name
no bandwidth
exclude-srlg group-name [group-name...(upto 5 max)]
no exclude-srlg
peer peer-gmpls-router-id
no peer bandwidth
segment-protection-type {unprotected | sbr | gr | sncp | prc}
no segment-protection-type
no shutdown
shutdown
no shutdown
shutdown
The loopback address of the remote router (UNI-C) must be configured after the to keyword and takes an IPv4 address as input.
The switching-type indicates the type of switching required for the gLSP. This can take a number of values, as defined in RFC 3471, and extended in RFC 6004 and RFC 7074 for Ethernet VPL (EVPL) services. The default CLI value is DCSC. This is the only supported value.
The encoding-type configuration specifies the encoding type of the payload carried by the gLSP. line, indicating 8B/10B encoding, is the only supported type.
The generalized-pid parameter specifies the type of payload carried by the gLSP. Standard ethertype values are used for packet and Ethernet LSPs (see RFC 3471). Only Ethernet (value 33) is supported.
Note that gLSPs are inherently bidirectional. That is, both directions of the gLSP are bound together. The destination UNI-C node automatically binds an incoming gLSP PATH message to the corresponding egress direction based on the session name in the session object.
Any gLSP that needs to be bound to a specific TE Link (as referred to in the pPATH), is only allowed if the corresponding TE Link exists under config>router>gmpls. Constraints such as HOP definition, SRLG, BW, and so on, is checked before signaling the gLSP.
Because RSVP signaling operates out of band, refresh reduction is not supported. RSVP authentication is not supported on the 1830 PSS UNI-N, but MD5 authentication is implemented.
A configurable retry-timer is supported.
A configurable retry-limit for each gLSP is supported, with a range of 0 to 10000, and a default of 0.
The working-path and protect-path command allows paths to be configured for the gLSP. At least a working-path must be configured, although the path-name that it references may contain an empty path. The optional working-path>peer and protect-path>peer commands allow the user to specify a first hop UNI-N node to use for the gLSP path. The protect path is only configurable for 1:N recovery option.
Reversion from the protect path to the working path is supported.
RSVP uses the Fixed Filter (FF) style of RESV. The signaled MTU is hard-coded to 9212 bytes, as appropriate for Ethernet gLSPs.
The default setup and hold priorities are 5 and 1, respectively, and cannot be configured. gLSP preemption is not supported.
Record and record-label are enabled by default and no user configurable command is therefore provided.