See all Tutorials
 

Tutorial

Introduction to MPlS and GMPLS
(continued)

The GMPLS Control Plane

In order to control components outside of the standard data packet, a separate control plane was developed for GMPLS.  This control plane is the true magic of GMPLS.  It allows for the total control of network devices. 

The GMPLS control plane provides for six top-level functions:  1) Discovery of Neighborhood Resources; 2) Dissemination of Link Status; 3) Topology Link State Management; 4) Path Management and Control; 5) Link Management; and 6) Link Protection.

1) Neighbor Discovery.  In order to manage the network, all network devices must be known:  switches, multiplexers and routers. GMPLS will use a new protocol called Link Management Protocol (LMP) to discover these devices and to negotiate functions (Figure 8).


Figure 8

2) Dissemination of Link Status.  It does no good just to know what hardware is out there, if the link is down or having problems.  To disseminate this information, a routing protocol must be used. For GMPLS, both the OSPF and the IS-IS protocols are being modified to support this function (Figure 9).


Figure 9

3) Typology State Management. Link-state routing protocols, such as OSPF and IS-IS, can be used to control and manage the link state typology (Figure 10).


Figure 10

<< Previous page     Next page >>

Page 4 of 7

Tutorials

Wireless LAN
1) Wireless LAN Technology and Network Implementation
2) Wireless LAN Antennas

Quality of Service
What Ever Happened to QoS?

MPLS
1) An Introduction to MPLS 
2) Introduction to MPLS Label Distribution and Signaling
3) Advanced MPLS Signaling
4) MPLS Network Reliance and Recovery
5) MPLS Traffic Engineering
6) Introduction to MPlS and GMPLS 

Ethernet  Ethernet in Metro and Long Haul Networks

Recent MPLS News

Database Results Error
Could not find file 'D:\Inetpub\www-silver\fpdb\article test.mdb'.
Guest Columns
Programmability for SIP-based Services
Michael Doerk, 
Nortel Networks
Hardening MPLS Networks
Steve Vogelsang
Laurel Networks
Exempting Packetized Traffic from Unbundling Requirements is Bad Policy  Shawn M. LewisCaerus, Inc.
Voice over Packet Protocols
VoIP and VoATM (VoAAL1, VoAAL2) 
  Michel Laurence, Octasic, Inc. 

See all Guest Columns

 

 

 

Subscription Info  |  UnSubscribe  |  Archive  | Marketing & Advertising  |  Link2Us Events  | About Us  |  Contact Us
Copyright © 2008 Converge! Media Ventures, Inc.  All rights reserved.