GMPLS
7450 ESS MPLS Guide Page 455
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.
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 doesn't 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 will bring the member operUp if
it passes.
A gLSP associated with a tunnel group member will be 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 will not be 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.
To Next Page
Loading...
