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

ME60 V800R010C10SPC500 Feature Description - System Management 01

This is ME60 V800R010C10SPC500 Feature Description - 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).
Basic LLDP Concepts

Basic LLDP Concepts

LLDP Packets

LLDP encapsulates Ethernet packets encapsulated into LLDP data units (LLDPDUs). LLDP supports two encapsulation modes: Ethernet II and Subnetwork Access Protocol (SNAP). The versatile routing platform (ME60) supports the Ethernet II encapsulation mode.

Figure 11-1 shows the format of an Ethernet II LLDP packet.

Figure 11-1 Ethernet II LLDP packet format

Table 11-1 describes the fields in an Ethernet II LLDP packet.
Table 11-1 Fields in an Ethernet II LLDP packet

Field

Description

Destination MAC address

A fixed multicast MAC address 0x0180-C200-000E.

Source MAC address

A MAC address for an interface or a bridge MAC address for a device.

Type

Packet type, fixed at 0x88CC.

LLDPDU

Main body of an LLDP packet.

FCS

Frame check sequence.

LLDPDU

An LLDPDU is a data unit encapsulated in the data field in an LLDP packet.

A device encapsulates local device information in type-length-value (TLV) format and combines several TLVs in an LLDPDU for transmission. You can combine various TLVs to form an LLDPDU as required. TLVs allow a device to advertise its own status and learn the status of neighboring devices.

Figure 11-2 shows the LLDPDU format.

Figure 11-2 LLDPDU format

Each LLDPDU carries a maximum of 28 types of TLVs, and that each LLDPDU starts with the Chassis ID TLV, Port ID TLV, and Time to Live TLV, and ends with the End of LLDPDU TLV.

TLV

A TLV is the smallest unit of an LLDPDU. It gives type, length, and other information for a device object. For example, a device ID is carried in the Chassis ID TLV, an interface ID in the Port ID TLV, and a network management address in the Management Address TLV.

LLDPDUs can encapsulate basic TLVs, TLVs defined by IEEE 802.1 working groups, TLVs defined by IEEE 802.3 working groups, and Data Center Bridging Capabilities Exchange Protocol (DCBX) TLVs.

  • Basic TLVs: are the basis for network device management.

    Table 11-2 Basic TLVs

    TLV Name

    TLV Type Value

    Description

    Mandatory

    End of LLDPDU TLV

    0

    End of an LLDPDU.

    Yes

    Chassis ID TLV

    1

    Bridge MAC address of the transmit device.

    Yes

    Port ID TLV

    2

    Number of a transmit interface of a device.

    Yes

    Time To Live TLV

    3

    Timeout period of local device information on neighboring devices.

    Yes

    Port Description TLV

    4

    String describing an Ethernet interface.

    No

    System Name TLV

    5

    Device name.

    No

    System Description TLV

    6

    System description.

    No

    System Capabilities TLV

    7

    Primary functions of the system and whether these primary functions are enabled.

    No

    Management Address TLV

    8

    Management address.

    No

    Reserved

    9-126

    Reserved for special use.

    No

  • Organizationally specific TLVs: include TLVs defined by IEEE 802.1 and those defined by IEEE 802.3. They are used to enhance network device management. Use these TLVs as needed.

    1. TLVs defined by IEEE 802.1

      Table 11-3 Description of TLVs defined by IEEE 802.1

      TLV Name

      TLV Type Value

      Description

      Reserved

      0

      Reserved for special use.

      Port VLAN ID TLV

      1

      VLAN ID on an interface.

      Port And Protocol VLAN ID TLV

      2

      Protocol VLAN ID on an interface.

      VLAN Name TLV

      3

      VLAN name on an interface.

      Protocol Identity TLV

      4

      Protocol type that an interface supports.

      Reserved

      5-255

      Reserved for special use.

    2. TLVs defined by IEEE 802.3

      Table 11-4 Description of TLVs defined by IEEE 802.3

      TLV Name

      TLV Type

      Description

      Reserved

      0

      Reserved for special use.

      MAC/PHY Configuration/Status TLV

      1

      Duplex and bit-rate capability, current duplex and bit-rate settings, and auto-negotiation status.

      Power Via MDI TLV

      2

      Power supply capability of an interface, that is, whether an interface supports PoE and whether an interface supplies or requires power.

      Link Aggregation TLV

      3

      Link aggregation status.

      Maximum Frame Size TLV

      4

      Maximum frame length supported by interfaces. The maximum transmission unit (MTU) of an interface is used.

      Reserved

      5-255

      Reserved for special use.

Figure 11-3 shows the TLV format.

Figure 11-3 TLV format

The TLV contains the following fields:

  • TLV type: a 7–bit long field. Each value uniquely identifies a TLV type. For example, value 0 indicates the end of LLDPDU TLV, and value 1 indicates a Chassis ID TLV.

  • TLV information string length: a 9–bit long field indicating the length of a TLV string.
  • TLV information string: a string that contains TLV information. This field contains a maximum of 511 bytes.

LLDP Management Addresses

The NMS uses LLDP management addresses to identify devices and implement network management.

Each management address is encapsulated in a Management Address TLV in an LLDP packet. The management address must be set to a valid unicast IP address of a device.
  • If you do not specify a management address, a device searches the IP address list and automatically selects an IP address as the default management address.
  • If the device does not find any proper IP address from the IP address list, the system uses a bridge MAC address as the default management address.
NOTE:
The device searches the IP address list for loopback interfaces, management network interface, and VLANIF interfaces in sequence and automatically selects the smallest IP address of the same interface type as a management IP address.
Translation
Download
Updated: 2019-01-04

Document ID: EDOC1100059466

Views: 10564

Downloads: 7

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