GMPLS protocols use a new loopback address type, called a gmpls-loopback, on the IPCC. The address of this loopback is termed the local GMPLS router ID. Packets that do not belong to a GMPLS protocol that are destined for this loopback address will be dropped. An interface is configured as a GMPLS Loopback using the
gmpls-loopback keyword.
config
router
interface local-gmpls-router-id-name
gmpls-loopback
address local-gmpls-loopback-address //Local LmpNodeId
The config>
router>
lmp>
lmp-peer peer-cp-node-id command creates a context per LMP peer. The entry
peer-cp-node-id is the control plane identifier of of the adjacent UNI-N. It is an IPv4 or unsigned integer-formatted address that is used by the UNI-C for LMP and RSVP-TE messages if a peer-loopback address is not subsequently configured. The local GMPLS Router ID is used as the source address.
A control channel to an LMP Peer is configured using the config>
router>
lmp>
lmp-peer peer-cp-node-id>
control-channel context. Control channels are indexed using the
lmp-cc-id parameter, which corresponds to the lmpCcId object in the LMP MIB.
config
router
[no] lmp
[no] te-link te-link-id
link-name te-link-name
remote-id id
[no] data-bearer data-bearer-id
port port-id
remote-id id
[no] shutdown
[no] shutdown
gmpls-loopback-address local-gmpls-loopback-address
[no] lmp-peer peer-cp-node-id
peer-loopback-address peer-loopback-address
retransmission-interval interval
retry-limit limit
[no] control-channel lmp-cc-id
peer-interface-address ipcc-destination-addr
hello interval interval dead-interval interval
passive
[no] shutdown
te-link te-link-id
te-link te-link-id
[no] shutdown
lmp-peer lmp-peer-address
...
[no] shutdown
[no] shutdown
If peer-loopback-address is entered, then this is used as the routable peer address, otherwise the
peer-cp-node-id is assumed to correspond to a routable peer loopback.
The peer-interface-address is mandatory and is the destination address of the IPCC on the peer UNI-N used to reach the GMPLS Router ID of the peer. It corresponds to the lmpCcRemoteIpAddr in RFC 4631. If the
peer-interface-address is used as the destination IP address in the IP packet on the IPCC, then the 7x50 local interface address is used as the source IP address.
A te-link is configured under
config>
router>
lmp>
te-link. The
te-link parameter under
config>
router>
lmp>
lmp-peer then assigns the control of the TE-links to the LMP protocol to a given peer. Each TE-Link can only be assigned to a single LMP peer.
The hello interval ranges from 1000 to 65535 milliseconds. The default hello interval is 1000 milliseconds.
The hello dead-interval ranges from 3000 to 65535 milliseconds. The default hello dead interval is 4000 milliseconds.
The retransmission-interval ranges from 10 to 4294967295 milliseconds in 10 millisecond intervals, with a default of 500 milliseconds.
Traffic engineering (TE) links are configured under the config>
router>
lmp with a specific command,
te-link, to create a specific context to hold TE specific configuration information pertinent to the local and remote identifiers, and physical resources assigned to the te-link. Only one data bearer per TE link is supported.
A TE-link has a unique link-id, which identifies it in RSVP-TE signaling.
config
router
[no] lmp
[no] te-link te-link-id
link-name te-link-name
remote-id id
[no] data-bearer data-bearer-id
port port-id
remote-id id
[no] shutdown
[no] shutdown
[no] shutdown
The te-link-id can take the form of an unsigned integer or 64 character (max) name: [1..2147483690] |
te-link-name: 64 char max
config>
port>
ethernet>
report-alarm signal-fail
Only ports with report-alarm signal-fail configured can be included in LMP, and that
report-alarm signal-fail cannot be subsequently removed from a port in LMP.
config
router
[no] gmpls
te-link te-link-id
[no] shutdown
where te-link-id: [1..2147483690] |
te-link-name: 32 char max
config>router>gmpls
path path-name
no path path-name
hop hop-index node-id node-id [te-link te-link-id]
[strict | loose]
no hop hop-index
no shutdown
shutdown
node-id: IPv4 address a.b.c.d | 1830-data-plane-node-id 32-bit unsigned integer
config
router
gmpls
no gmpls
peer peer-cp-node-id
gr-helper-time max-recovery recovery-interval max-restart restart-interval
no gr-helper-time
keep-multiplier number
no keep-multiplier
no rapid-retransmit-time
rapid-retransmit-time hundred-milliseconds
no rapid-retry-limit
rapid-retry-limit limit
no refresh-time
refresh-time seconds
no refresh-time
lsp-init-retry-timeout seconds
no lsp-init-retry-timeout
no shutdown
shutdown
The LMP Peer is configured under config>
router>
gmpls>
peer peer-cp-node-id, where the
peer-cp-node-id is control plane identifier of the adjacent optical cross connect (UNI-N node). RSVP uses the destination address returned by LMP for this peer control plane node ID as the destination address, and the loopback address referenced under
config>
router>
lmp>
gmpls-loopback-address local-gmpls-loopback-address as the local router ID to use for the session.
config
router
gmpls
peer peer-cp-node-id
no peer peer-cp-node-id
lsp-hold-timer hold-timer
no lsp-hold-timer
hello-interval milliseconds
no shutdown
shutdown
The per-peer lsp-hold-timer hold-timer parameter is used to configure a node-wide hold-down time. This timer is started when a RESV for a new gLSP is first received, or a failed gLSP path is restored (or the 7x50 is notified of a restoration following segment recovery) in order to give the optical network time to program its data path. The value range is 5 to 300 seconds, with a default of 60 seconds. A member of a GMPLS tunnel group is not considered up until the hold-timer has expired. Note that different optical network technologies have different data path programing/setup times.
Note that the no hello-interval command sets the hello-interval to the default value of 3000 milliseconds. Configuring
hello-interval 0 will disable hellos in GMPLS.
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 i.e. it uses the set of functions and CLI commands applicable to an overlay gLSP, rather than a peer model gLSP. Only overlay model gLSPs are supported in Release 13.0; this is the default type of GMPLS LSP. The 7x50 can only act as an LER terminating a gLSP, and cannot switch a GMPLS i.e. it cannot act as a GMPLS LSR
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 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 in Release 13.0.
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 in Release 13.0.
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 in Release 13.0.
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.
The default setup and
hold priorities are 5 and 1, respectively, and cannot be configured in Release 13.0. gLSP preemption is not supported.
Record and
record-label are enabled by default and no user configurable command is therefore provided.
config
router
gmpls
lsp gmpls-tunnel-name [gmpls-uni]
to remote-uni-c-gmpls-router-id
working-path path-name
bandwidth signal-type rfc3471-name
Already-established gLSPs within a load-sharing tunnel group or for which 1:N recovery is configured can be made mutually diverse by applying a shutdown /
no shutdown operation. GMPLS LSPs with other types of protection can be made mutually SRLG-diverse by performing a shutdown of the gLSP, reconfiguring the SLG list to exclude using the
exclude-srlg command, and then applying a
no shutdown of the gLSP.
These resiliency options are configured under the segment-protection-type command for a given path.
config
router
gmpls
lsp gmpls-tunnel-name [gmpls-uni]
to remote-uni-c-gmpls-router-id
working-path path-name
[no] segment-protection-type {unprotected | sbr | gr | sncp | prc}
...
[no] shutdown
The default segment-protection-type setting is
unprotected.
The Table 11 illustrates the recommended combinations of segment protection type and end-to-end protection type.
config
router
gmpls
lsp gmpls-tunnel-name [gmpls-uni]
to remote-uni-c-gmpls-router-id
e2e-protection-type [unprotected|1toN|sbr]
revert-timer timer-value
|
•
|
1toN — 1:N protection. Extra traffic is not supported. Note that 1:1 protection is a special case of 1:N. 0x04
|
|
•
|
sbr — Full LSP rerouting; 0x01
|
config
router
gmpls
lsp lsp-name gmpls-uni
to remote-uni-c-gmpls-router-id
e2e-protection-type 1toN // Only these types are allowed for gmpls-uni
switching-type ethernet
encoding-type ethernet
generalized-pid ethernet
revert-timer timer-value
retry-limit limit
working-path path-name1 [lmp-peer <peer-gmpls-router-id>] ...
[no] shutdown
working-path path-name2 [lmp-peer peer-gmpls-router-id] ...
[no] shutdown
working-path path-name3 [lmp-peer peer-gmpls-router-id] ...
[no] shutdown
protect-path path-name4 [lmp-peer peer-gmpls-router-id] ...
[no] shutdown
config > gmpls-tunnel-group 2 create
type head-end
far-end remote-uni-c-router-id
mode protection
member 1 create
glsp session-name lsp-name:path-name1
no shutdown
no shutdown
config > gmpls-tunnel-group 3
type head-end
far-end remote-uni-c-router-id
mode protection
member 1 create
glsp session-name lsp-name:path-name1
no shutdown
no shutdown
config > gmpls-tunnel-group 4
type head-end
far-end remote-uni-c-router-id
mode protection
member 1 create
glsp session-name lsp-name:path-name1
no shutdown
no shutdown
config > gmpls-tunnel-group 2
type tail-end
far-end remote-uni-c-router-id
mode protection
member 1 create
glsp session-name lsp-name:path-name1
no shutdown
no shutdown
config > gmpls-tunnel-group 3
type tail-end
far-end remote-uni-c-router-id
mode protection
member 1 create
glsp session-name lsp-name:path-name1
no shutdown
no shutdown
config > gmpls-tunnel-group 4
type tail-end
far-end remote-uni-c-router-id
mode protection
member 1 create
glsp session-name lsp-name:path-name1
no shutdown
no shutdown
config
gmpls-tun-grp gmpls-tun-grp-id
type {head-end | tail-end}
far-end remote-uni-c-router-id
mode {load-sharing | active-standby}
no mode
[no] member-threshold threshold [action down]
member mem-id [create]
glsp session-name name
no glsp session-name name
[no] shutdown
...
[no] shutdown
gmpls-tun-grp-id is an unsigned integer from 1 to 1024, shared with the Ethernet tunnel ID range.
The GMPLS Tunnel Group must be configured as either at both the head-end or
tail-end of a set of member gLSPs (identified using the
head-end or
tail-end keywords). These keywords are mutually exclusive.
Nodes at the head-end initiate signaling of gLSPs. The far-end is the far end of the GMPLS tunnel group. If this node is a head end, then the far end address is taken as the to address for the member gLSPs. Each gLSP that is bound to the tunnel group must have a to address matching the
far end address. A binding is held down if a gLSP to and the tunnel group to do not match.
Nodes at the tail end wait for the first path message for a gLSP. The far-end-address address must be configured at the tail end. It is the GMPLS Router ID of the head-end UNI-C (the
remote-uni-c-node-id), and must be configured at the tail end UNI-C of a gLSP. The combination of
session-name and
remote-uni-c-node-id provides a unique key to bind an incoming gLSP setup request to a tunnel group. A binding to the tunnel group is held down at the tail end until a gLSP PATH message with a matching
session-name and source address that matches the tunnel group's far-end address is received.
At the tail end, the session-name is composed of the LSP name and Path name as configured at the head end
If load-sharing is configured, then all of the gLSPs must terminate on the same far-end node. All of the ports used by gLSPs in a load-sharing must be equivalent in that they must have the same named QoS policy, bandwidth, and so on. Once more than one gLSP is associated with a tunnel group, the QoS policy/scheduler policy cannot be changed in any of the ports. All gLSPs must be unprotected end-to-end in load-sharing mode. Segment protection is allowed for gLSPs associated in load sharing mode to a GMPLS tunnel group.
In active-standby mode, only one member gLSP can be associated with the tunnel group.
The member-threshold is the number of member gLSPs that must be operationally up before the gmpls tunnel group is considered operationally up.
config
router
interface if-name
address a.b.c.d|ipv6-address
port gmpls-tunnel-group gmpls-tunnel-group-id
