No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

NE40E-M2 V800R010C10SPC500 Configuration Guide - System Management 01

This is NE40E-M2 V800R010C10SPC500 Configuration Guide - System Management
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Overview of LLDP

Overview of LLDP

LLDP provides a standard link-layer discovery method to encapsulate information about the capabilities, management address, device ID, and interface ID of a local device into LLDP packets. These packets are sent to neighboring devices that save the information received in a standard Management Information Base (MIB) to help the NMS query and determine the communication status of links.

Background

Diversified network devices are deployed on a network, and configurations of these devices are complicated. Therefore, NMSs must be able to meet increasing requirements for network management capabilities, such as the capability to automatically obtain the topology status of connected devices and the capability to detect configuration conflicts between devices. A majority of NMSs use an automated discovery function to trace changes in the network topology, but most can only analyze the network layer topology. Network layer topology information notifies you of basic events, such as the addition or deletion of devices, but gives you no information about the interfaces to connect a device to other devices. The NMSs cannot identify neither the device location or the network operation mode.

LLDP is developed to resolve these problems. LLDP can identify interfaces on a network device and provide detailed information about connections between devices. LLDP can also display information about paths between clients, switches, routers, application servers, and network servers, which helps you efficiently locate network faults.

LLDP Implementation

Figure 4-1 shows how LLDP is implemented.
Figure 4-1 Implementation diagram for LLDP

  1. DeviceA encapsulates its status information into an LLDP packet and sends the packet to the neighboring device DeviceB.
  2. DeviceB parses the LLDP packet received and saves information about DeviceA to its LLDP remote system MIB, allowing the NMS to collect topology information.
  3. DeviceB encapsulates its status information into an LLDP packet and sends the packet to the neighboring device DeviceA. DeviceA parses the LLDP packet received and saves information about DeviceB to its LLDP remote system MIB, allowing the NMS to collect topology information.
  4. By exchanging SNMP packets with DeviceA and DeviceB, the NMS collects information about DeviceA and DeviceB from their LLDP local system MIBs and LLDP remote system MIBs, and analyzes the status information to determine network topology.

Benefits

Deploying LLDP improves NMS capabilities. LLDP supplies the NMS with detailed information about network topology and topology changes, and it detects inappropriate configurations existing on the network. The information provided by LLDP helps administrators monitor network status in real time to keep the network secure and stable.

Download
Updated: 2019-01-02

Document ID: EDOC1100058392

Views: 16479

Downloads: 26

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next