Gmpls Tunnel Groups - Alcatel-Lucent 7450 Manual

Ethernet service switch
Table of Contents

Advertisement

GMPLS Tunnel Groups

GMPLS Tunnel Groups
A GMPLS tunnel group is a bundle of gLSPs providing an abstraction of the data bearers that
are intended to be associated to 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-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 the head-end or tail-end of a set
of member gLSPs. 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
Page 454
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
7450 ESS MPLS Guide

Advertisement

Table of Contents
loading

Table of Contents