A GMPLS tunnel group is a bundle of gLSPs providing an abstraction of the data bearers that are intended to be associated with one IP interface. This object allows, for example, end-to-end load balancing across the set of data bearers corresponding to a set of gLSPs. A gLSP is bound to a GMPLS tunnel group by a gLSP tunnel (session) name at both the head end and the tail end UNI-C nodes of the gLSP. A sender address (the far-end) may optionally be configured for the tail end of a gLSP in case different head end nodes use overlapping gLSP tunnel names.
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. When 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.
All members of a tunnel group must be of the same bandwidth.
The member-threshold is the number of member gLSPs that must be operationally up before the gmpls tunnel group is considered operationally up.
A member of a GMPLS tunnel group may be treated as down for one of the following reasons. These reason codes are recorded in the tmnxGmplsTunGrpMemberTable in the MIB:
adminDn — The member or the related tunnel-grp is administratively down.
wpLspDn — The associated working lsp-path is down.
wpPortDn — The data-bearer port associated with the working lsp-path is down.
wpPortNoRsrc — The data-bearer port associated with the working lsp-path has no resource to support the services over the gmpls-tunnel-grp logical port.
ppLspDn — The associated protect lsp-path is down.
ppPortDn — The data-bearer port associated with the protect lsp-path is down.
ppPortNoRsrc — The data-bearer port associated with the protect lsp-path has no resource to support the services over the gmpls-tunnel-grp logical port.
Note that in the case of wpPortNoRsrc and ppPortNoRsrc, the term 'resources' relates to QoS or ACL related resources. For example, this can happen when a subsequent physical or data bearing port is added to a GMPLS tunnel group, which already has services running over it. If the new-complex does not have the resources to support those services over that GMPLS tunnel group, the related member operState would be down with reasonCode PortNoRsrc. If a gLSP is already established on a data bearer when a resource failure is experienced, the RSVP PATH message A-Bit is updated so that both ends ensure that the LSP Path is held down.
The user should free resources from the complex, and shutdown/no shutdown the GMPLS tunnel group member. This repeats the resource check, which brings the member operUp if it passes.
A gLSP associated with a tunnel group member is down if the member is operationally down, or a fault is detected on the associated data bearer.
If a member is in the admin down state, a gLSP is not set-up. If a gLSP is already up, the RSVP Path message A-Bit is updated so that both ends of the gLSP path are kept down.