GMPLS
7450 ESS MPLS Guide Page 425
GMPLS UNI Architecture
This section specifies the architectural and functional elements of the GMPLS UNI on the 7x50 in
Release 13.0, and how they relate to one another. The architecture is illustrated in Figure 38.
Figure 38: GMPLS UNI Architecture
On the UNI-C side, the UNI consists of the following functional components:
• A set of one or more data bearers between the UNI-C and UNI-N. Each data bearer maps
to a black and white Ethernet network port.
• A Traffic Engineering (TE) link (RFC 4202), represented by an identifier on the UNI-C
and UNI-N nodes. This identifier is manually configured in Release 13.0. A TE link maps
to a single data bearer. There may be one or more TE links per UNI between a UNI-C and
UNI-N pair.
• An IP Control Channel (IPCC) between the UNI-C and UNI-N. This carries GMPLS
control plane traffic between the two nodes and is separate from the links carrying user
plane traffic. This carries the following two control protocols:
→ LMP — Link Management Protocol. This is responsible for checking the correlation
between the UNI-C/UNI-N and the TE link/Data Bearer identifiers, and maintaining
the IPCC adjacency between the UNI-C and UNI-N. LMP runs on a network IP
interface bound to an Ethernet port on an Ethernet MDA/IMM. This is a separate port
to the TE Links.
→ RSVP-TE — RSVP-TE runs on the same network interface as LMP. The next hop
from an RSVP-TE perspective is the UNI-N. RSVP-TE is used to establish and
maintain a GMPLS LSP.
x/y/z
v/w/s
gLSP
IP
LB
LMP
RSVP-TE
Data bearer (Port) TE Link
IPCC (Control Channel) Maintenance
TE Link identifier corelation
NW
IP IF
IP Management
LB
gLSP
a/b/c
d/e/f
g/h/i
IGP
BGP
MPLS/
RSVP
NW
IP IF
7750 (UNI-C) 1830 (UNI-N)
24852
To Next Page
Loading...
