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

Fat AP and Cloud AP V200R008C00 CLI-based Configuration Guide

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).
Configuring the LLDP

Configuring the LLDP

Configuring Basic LLDP Functions

When LLDP is configured on devices, the NMS can obtain detailed information such as the network topology, device interface status, and management address.

Pre-configuration Tasks

Before configuring LLDP, ensure that the local device and NMS are reachable to each other, and configure the Simple Network Management Protocol (SNMP).

Enabling LLDP

Context

The LLDP function enables a device to send LLDP packets with local system status information to neighbors and parse LLDP packets received from neighbors. The NMS obtains Layer 2 connection status from the device to analyze the network topology.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    lldp enable

    LLDP is enabled globally.

    By default, LLDP is disabled globally.

(Optional) Disabling LLDP on an Interface

Context

LLDP can be enabled in the system view and the interface view.

  • When LLDP is enabled in the system view, LLDP is enabled on all interfaces.
  • When LLDP is disabled in the system view, LLDP is disabled on all interfaces.
  • An interface can send and receive LLDP packets only after LLDP is enabled in both the system view and the interface view.
  • After LLDP is disabled globally, the commands for enabling and disabling LLDP on an interface do not take effect.
  • If LLDP needs to be disabled on some interfaces, enable LLDP globally first, and run the undo lldp enable command on these interfaces. To re-enable LLDP on these interfaces, run the lldp enable command in the views of these interfaces.
NOTE:
  • Only physical interfaces support LLDP. Logical interfaces such as the VLANIF and Eth-Trunk interfaces do not support LLDP.
  • On an Eth-Trunk, LLDP can only be enabled on member interfaces. LLDP status of a member interface does not affect that of another.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interface interface-type interface-number

    The interface view is displayed.

  3. Run:

    undo lldp enable

    LLDP is disabled on the interface.

(Optional) Configuring an LLDP Management IP Address

Context

The management address of a device is carried in the Management Address TLV field of the LLDP packet. The NMS uses management addresses to identify and manage devices.

If the configured management IP address is invalid or no management IP address is configured, the system sets an IP address in the address list as the management IP address. The system selects the IP address in the following sequence: loopback interface address and VLANIF interface address. Among the IP addresses of the same type, the system selects the smallest one. If the system does not find a management IP address, the bridge MAC address is used as the management IP address.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    lldp management-address ip-address

    The LLDP management address is configured.

    The value of ip-address must be a valid unicast IP address existing on the device.

(Optional) Configuring LLDP Time Parameters

Context

Interval between sending LLDP packets

When the LLDP status of the device keeps unchanged, the device sends LLDP packets to the neighbors at a certain interval.

Consider the value of delay when adjusting the value of interval because it is restricted by the value of delay.

  • The value of interval ranges from 5 to 32768. Increasing the value of interval is not restricted by the value of delay.
  • The value of interval must be equal to or greater than four times the value of delay. Therefore, if you want to set interval to be smaller than four times the value of delay, first reduce the delay value to be equal to or smaller than a quarter of the new interval value, and then reduce the interval value.
Delay in sending LLDP packets

There is a delay before the device sends an LLDP packet to the neighbor when the device status changes frequently.

Consider the value of interval when adjusting the value of delay because it is restricted by the value of interval.

  • The value of delay ranges from 1 to 8192. Decreasing the value of delay is not restricted by the value of interval.
  • The value of delay must be smaller than or equal to a quarter of interval. Therefore, if you want to set delay to be greater than a quarter of interval, first increase the interval value to four times the new delay value, and then increase the delay value.
Hold time multiplier of device information on neighbors

The hold time multiplier is used to calculate the Time to Live (TTL), which determines how long information about a device can be saved on the neighbors. You can specify the hold time of device information on the neighbors. After receiving an LLDP packet, a neighbor updates the aging time of the device information from the sender based on the TTL.

The storage time calculation formula is: TTL = Min (65535, (interval x hold)).
  • TTL is the hold time of device information. It is the smaller value between 65535 and (interval x hold).

  • interval indicates the interval at which the device sends LLDP packets to neighbors.

  • hold indicates the hold time multiplier of device information on neighbors. The value ranges from 2 to 10.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    lldp message-transmission interval interval

    The interval between sending LLDP packets is set.

    The default interval between sending LLDP packets is 30 seconds.

  3. Run:

    lldp message-transmission delay delay

    The delay in sending LLDP packets is set.

    The default delay in sending LLDP packets is 2 seconds.

  4. Run:

    lldp message-transmission hold-multiplier hold

    The hold time multiplier of device information stored on neighbors is set.

    The default hold time multiplier is 4.

(Optional) Configuring the Delay in Initializing Interfaces

Context

The delay in initializing interfaces is the delay before LLDP is re-enabled on an interface. The delay suppresses the topology flapping caused by the frequent LLDP status changes.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    lldp restart-delay delay

    The delay in initializing interfaces is set.

    The default delay is 2 seconds.

(Optional) Configuring the Type of TLVs that an Interface Can Send

Context

LLDPDUs can encapsulate basic TLVs, TLVs defined by IEEE 802.1 working groups, TLVs defined by IEEE 802.3 working groups, and Media Endpoint Discovery (MED) TLVs.

NOTE:
  • When the supported TLVs are basic TLVs, TLVs in the IEEE 802.1 format, and TLVs in the IEEE 802.3 format, the lldp tlv-enable command with the all parameter advertises all TLVs. When the supported TLVs are MED TLVs, the lldp tlv-enable command with the all parameter advertises all TLVs except Location Identification TLV.

    If the all parameter is not specified, only one type of TLV can be advertised. To advertise multiple types of TLVs, run this command multiple times.

  • You can specify the other types of MED TLVs only after specifying the MED Capabilities TLV.

    To disable the MED Capabilities TLV, first disable the other types of MED TLVs.

    To disable the MAC/PHY Configuration/Status TLVs, first disable the MED Capabilities TLV.

  • The 802.3 MAC/PHY Configuration/Status TLVs are automatically advertised after the MED Capabilities TLV is advertised.
  • If you disable the MED TLVs using the command with the all parameter, the 802.3 MAC/PHY Configuration/Status TLVs are not disabled automatically.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interface interface-type interface-number

    The interface view is displayed.

  3. Run the following commands to set the type of TLVs to be advertised on the interface:

    • Run:
      lldp tlv-enable basic-tlv { all | management-address | port-description | system-capability | system-description | system-name }

      The interface is configured to advertise basic TLVs.

    • Run:
      lldp tlv-enable dot1-tlv { all | port-vlan-id | protocol-vlan-id [ vlan-id ] | vlan-name [ vlan-id ] | protocol-identity }

      The interface is configured to advertise TLVs defined by the IEEE 802.1 working group.

    • Run:
      lldp tlv-enable dot3-tlv { all | link-aggregation | mac-physic | max-frame-size | power }

      The interface is configured to advertise the TLVs advertised by the IEEE 802.3 working group.

    • Run:
      lldp tlv-enable med-tlv { all | capability | inventory | location-id { civic-address device-type country-code { ca-type ca-value } & <1-10> | elin-address Tel-Number } | network-policy | power-over-ethernet }

      The interface is configured to advertise MED TLVs.

    By default, an interface advertises all types of TLVs except the Location Identification TLV and advertises MED TLVs only when receiving MED TLVs.

  4. Run:

    lldp dot3-tlv power { 802.1ab | 802.3at }

    The standard with which the 802.3 Power via MDI TLV sent by the interface complies is set.

    By default, the 802.3 Power via MDI TLV sent by a PoE interface conforms to 802.3at.

    NOTE:

    Before selecting a format of the 802.3 Power via MDI TLV, you must know the TLV format supported by the neighbors. The TLV format on the local device must be the same as that on the neighbors.

Checking the Configuration

Procedure

  • Run the display lldp local [ interface interface-type interface-number ] command to view LLDP local information on a specified interface or all interfaces.
  • Run the display lldp neighbor [ interface interface-type interface-number ] command to view neighbor information in the system or on an interface.
  • Run the display lldp neighbor brief command to view brief information about neighbors.
  • Run the display lldp tlv-config [ interface interface-type interface-number ] command to view TLV types supported by the entire system or an interface.

Configuring the LLDP Alarm Function

This section describes how to configure the LLDP alarm function on a network device, so that the device can send alarms to the NMS when information about neighbors changes.

Pre-configuration Tasks

Before configuring the LLDP alarm function, complete the following task:

  • Configuring reachable routes between devices and the NMS, and SNMP parameters

Setting the Delay in Sending Traps About Neighbor Information Changes

Context

There is a delay before the device sends LLDP traps about neighbor information changes to the NMS. When neighbor information changes frequently, extend the delay to prevent the device from sending traps to the NMS too frequently. This suppresses the topology flapping.

The configured delay applies only to the trap, which reports changes in neighbor information, including the number of added neighbors, number of deleted neighbors, number of neighbors that are aged out, and number of neighbors of which the information is deleted.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    lldp trap-interval interval

    The delay in sending neighbor change traps to the NMS is set.

    The default delay in sending neighbor change traps to the NMS is 5 seconds.

Enabling the LLDP Trap Function

Context

After the LLDP trap function is enabled, the device sends traps to the NMS in one of the following cases:
  • The LLDP function is enabled or disabled globally.
  • The local management address changes.
  • Neighbor information changes. No trap is generated if the management address of a neighbor changes.
NOTE:
  • The LLDP trap function applies to all interfaces. The LLDP trap function takes effect no matter whether LLDP is enabled globally.
  • If the network topology is unstable, disable the LLDP trap function to prevent frequent trap sending.
  • To set the interval between sending neighbor change traps to the NMS, run the lldp trap-interval commands. If neighbor information changes frequently, extend the interval to reduce the number of traps. In this way, network topology flapping is suppressed.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    snmp-agent trap enable feature-name lldptrap [ trap-name { hwlldpdisabled | hwlldpenabled | hwlldplocmanipaddrchange | lldpremtableschange } ]

    The LLDP trap function is enabled.

    By default, the LLDP trap function is enabled.

Checking the Configuration

Procedure

  • Run the display snmp-agent trap feature-name lldptrap all command to view status of all traps on the LLDP module.
  • Run the display lldp local [ interface interface-type interface-number ] command to view LLDP status in the system or on an interface.
Translation
Download
Updated: 2019-01-11

Document ID: EDOC1000176006

Views: 118754

Downloads: 309

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