Thursday, January 8, 2009

Local Management Interface (LMI)

Local Management Interface

Initial proposals for frame relay were presented to the Consultative Committee on International Telephone and Telegraph (CCITT) in 1984. Lack of interoperability and standardization, prevented any significant Frame Relay deployment until 1990 when Cisco, Digital Equipment Corporation (DEC), Northern Telecom, and StrataCom formed a consortium to focus on its development. They produced a protocol that provided additional capabilities for complex inter-networking environments. These Frame Relay extensions are referred to as the Local Management Interface (LMI).

Datalink connection identifiers (DLCIs) are numbers that refer to paths through the frame relay network. They are only locally significant, which means that when device-A sends data to device-B it will most-likely use a different DLCI than device-B would use to reply. Multiple virtual circuits can be active on the same physical end-points (performed by using subinterfaces).

The LMI global addressing extension gives Frame Relay data-link connection identifier (DLCI) values global rather than local significance. DLCI values become DTE addresses that are unique in the Frame Relay WAN. The global addressing extension adds functionality and manageability to Frame Relay internetworks. Individual network interfaces and the end nodes attached to them, for example, can be identified by using standard address-resolution and discovery techniques. In addition, the entire Frame Relay network appears to be a typical LAN to routers on its periphery.

LMI virtual circuit status messages provide communication and synchronization between Frame Relay DTE and DCE devices. These messages are used to periodically report on the status of PVCs, which prevents data from being sent into black holes (that is, over PVCs that no longer exist).

The LMI multicasting extension allows multicast groups to be assigned. Multicasting saves bandwidth by allowing routing updates and address-resolution messages to be sent only to specific groups of routers. The extension also transmits reports on the status of multicast groups in update messages.

No comments:

Post a Comment

  • High-Speed LANs Part II
  • Chassis Design w/ Upgradeable Modules
  • ChemEng's Shared 100FX Backbone
  • Buying Equipment: What to Evaluate
  • Theory
  • High Speed LANs
  • ATM Data Types and Quality of Service
  • Windows ATM Services 2
  • Windows ATM Services
  • ATM Glossary
  • The Traffic descriptor
  • ATM Cell Structures
  • ATM CELL HEADER
  • ATM (asynchronous transfer mode)
  • ATM logical connections
  • ATM logical connection
  • network is based on virtual path identifiers
  • Protocols in multi-service networks
  • ATM protocol architecture
  • Asynchronous Transfer Mode and ATM addressing
  • Asynchronous Transfer Mode Overview
  • Asynchronous Transfer Mode
  • Market reputation
  • Committed information rate (CIR)
  • Local Management Interface (LMI)
  • Frame Relay origins
  • Virtual circuits
  • Physical layer
  • Media Access Control (MAC)
  • Logical Link Control (LLC)
  • Data Link Layer
  • Network Layer
  • Transport Layer
  • Session Layer
  • Presentation Layer
  • OSI protocols
  • Application Layer
  • Frame Relay versus X.25
  • Design
  • frame-relay network technique
  • F rame Relay