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

CX11x, CX31x, CX710 (Earlier Than V6.03), and CX91x Series Switch Modules V100R001C10 Configuration Guide 12

The documents describe the configuration of various services supported by the CX11x&CX31x&CX91x series switch modules The description covers configuration examples and function configurations.
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.

  3. Run:

    commit

    The configuration is committed.

(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 lldp disable command on these interfaces. To re-enable LLDP on these interfaces, run the undo lldp disable 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:

    lldp disable

    LLDP is disabled on the interface.

  4. Run:

    commit

    The configuration is committed.

(Optional) Configuring an LLDP Management IP Address

Context

The LLDP management address is carried in the Management Address TLV field in LLDP packets. It is used by the NMS to identify a device, and this helps to detect network topology and facilitate network management. Two methods are available to configure an LLDP management address:
  • Run the lldp management-address command to configure an LLDP management address.
  • Run the lldp management-address bind command to bind the LLDP management address to an interface so that the device uses the interface's IP address as the management address.
The LLDP management address is selected based on the following principles:
  1. If the LLDP management address has been configured using the lldp management-address command, the device uses this LLDP management address.
  2. If no LLDP management address has been configured using the lldp management-address command, but the management address is bound to an interface, the devices uses the interface's IP address as the LLDP management address.
  3. If no LLDP management address has been configured using the lldp management-address command, and the management address is not bound to any interface, the device searches the IP address list and automatically specifies an IP address as the LLDP management address. If no IP address is available, the device uses the bridge MAC address as the LLDP management address.
    NOTE:

    The device searches IP addresses of the following interfaces in sequence for the LLDP management address: Loopback interface, management network interface, and VLANIF interface. The device selects the smallest IP address of the same type of interface as the LLDP management address.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run either of the following commands:

    • To configure an LLDP management address, run the lldp management-address ip-address command.

      ip-address specified in this command can be any IP address except 0.0.0.0. It is recommended that you use the IP address of the management network interface as the LLDP management address.

    • To bind the LLDP management address to an interface, run the lldp management-address bind interface interface-type interface-number command.

  3. Run:

    commit

    The configuration is committed.

(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 transmit interval interval

    The interval between sending LLDP packets is set.

    The default interval between sending LLDP packets is 30 seconds.

  3. Run:

    lldp transmit delay delay

    The delay in sending LLDP packets is set.

    The default delay in sending LLDP packets is 2 seconds.

  4. Run:

    lldp transmit multiplier hold

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

    The default hold time multiplier is 4.

  5. Run:

    commit

    The configuration is committed.

(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

    The delay in initializing interfaces is set.

    The default delay is 2 seconds.

  3. Run:

    commit

    The configuration is committed.

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

Context

TLVs that can be encapsulated into an LLDPDU include basic TLVs, TLVs defined by IEEE 802.1, TLVs defined by IEEE 802.3, and DCBX TLVs.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    interface interface-type interface-number

    The interface view is displayed.

  3. Run:

    lldp tlv-enable { dot1-tlv protocol-identity | dcbx }

    Types of TLVs allowed to be advertised by LLDP are configured.

    By default, all TLVs except DCBX TLVs and Protocol Identity TLVs are allowed to be advertised by LLDP.

    NOTE:

    CX11x switch module GE switching plane does not support DCBX TLVs.

    To disable LLDP on an interface from advertising any TLVs except DCBX TLVs and Protocol Identity TLVs, run the lldp tlv-disable command.

  4. Run:

    commit

    The configuration is committed.

(Optional) Configuring the Number of LLDP Packets Quickly Sent by the Device to a Neighbor

Context

When the device discovers a neighbor, LLDP status changes from disabled to enabled on the device, or the status of interfaces on the device changes from Down to Up, the device quickly sends a specified number of LLDP packets to the neighbor to notify it of local device information.

The device sends one LLDP packet to the neighbor per second without any delay. After sending the specified number of LLDP packets, the device sends LLDP packets to the neighbor at the interval set in the lldp trasmit interval interval command.

Procedure

  1. Run:

    system-view

    The system view is displayed.

  2. Run:

    lldp fast-count count

    The number of LLDP packets being sent in quick succession to neighbors is configured.

    By default, the number of LLDP packets being sent in quick succession to neighbors is 4.

  3. Run:

    commit

    The configuration is committed.

(Optional) Configuring MDN

Context

MAC Address Discovery Neighbor (MDN) obtains the MAC addresses of non-Huawei devices. As shown in Figure 14-26, SwitchA is a Huawei device and SwitchB is a non-Huawei device. After MDN is configured on SwitchA, SwitchA can receive non-Link Layer Discovery Protocol (LLDP) packets from SwitchB and obtain SwitchB's MAC address carried in the packets. The MDN function helps the NMS draw the network topology between SwitchA and SwitchB.

Figure 14-26 Networking diagram for MDN application

Procedure

  • Enable MDN globally.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      lldp mdn enable

      MDN is enabled globally.

      By default, the MDN function is disabled globally.

      NOTE:

      After MDN is enabled globally, the MDN function takes effect on all interfaces on the device.

    3. Run:

      commit

      The configuration is committed.

  • Enable MDN on an interface.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      interface interface-type interface-number

      The interface view is displayed.

    3. Run:

      lldp mdn enable

      MDN is enabled on the interface.

      By default, if MDN is enabled globally, the MDN function takes effect on all interfaces on the device. If MDN is disabled globally, the MDN function does not take effect on any interface.

      NOTE:

      If the undo lldp mdn enable command is configured on a specified interface, the MDN function on the interface is disabled but uses the global configuration in the configuration file. If MDN is enabled globally, the interface still has this function enabled. If MDN is disabled globally, the interface has this function disabled.

    4. Run:

      commit

      The configuration is committed.

  • Disable the MDN function on a specified interface after MDN is enabled globally.
    1. Run:

      system-view

      The system view is displayed.

    2. Run:

      interface interface-type interface-number

      The interface view is displayed.

    3. Run:

      lldp mdn disable

      The MDN function is disabled on the interface.

    4. Run:

      commit

      The configuration is committed.

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.
  • Run the display lldp mdn local [ interface interface-type interface-number ] command to view MDN status in the system or on an interface.
  • Run the display lldp mdn neighbor [ interface interface-type interface-number ] command to view MDN neighbor status in the system or on 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.

  3. Run:

    lldp mdn trap-interval interval

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

    By default, the delay for a device to send alarms about MDN neighbor information changes to the NMS is 5 seconds.

  4. Run:

    commit

    The configuration is committed.

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:
  • MDN Neighbor information 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 and lldp mdn 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 lldp [ trap-name { hwlldpmdnremtableschange | lldpremtableschange } ]

    The LLDP trap function is enabled.

    By default, the hwlldpmdnremtableschange trap is disabled, and the lldpremtableschange trap is enabled.

  3. Run:

    commit

    The configuration is committed.

Checking the Configuration

Procedure

  • Run the display snmp-agent trap feature-name lldp 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.
  • Run the display lldp mdn local [ interface interface-type interface-name ] command to view MDN status in the system or on an interface.
Translation
Download
Updated: 2019-08-09

Document ID: EDOC1000041694

Views: 59678

Downloads: 3623

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