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

S12700 V200R012C00 Configuration Guide - Ethernet Switching

This document describes the configuration of Ethernet services, including configuring MAC address table, link aggregation, VLANs, VLAN aggregation, MUX VLAN, VLAN termination, Voice VLAN, VLAN mapping, QinQ, GVRP, VCMP, STP/RSTP/MSTP, VBST, SEP, RRPP, ERPS, LBDT, and Layer 2 protocol transparent transmission.
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).
LNP

LNP

Definition

Link-type Negotiation Protocol (LNP) dynamically negotiates the link type of an Ethernet interface. The negotiated link type affects the VLAN the interface joins, which is described as follows:
  • When the link type on an Ethernet interface is negotiated as access, the interface joins VLAN 1 by default.
  • When the link type on an Ethernet interface is negotiated as trunk, the interface joins a VLAN between VLAN 1 and VLAN 4094 by default.

Background

The switch supports the following link types on an Ethernet interface: access, hybrid, trunk, and QinQ. The four link types are applicable to different network positions and are manually specified. When the network topology changes, link types of Ethernet interfaces also need to be reconfigured. If this is done manually, configuration is time-consuming and complex. To simplify the configuration, LNP supports auto-negotiation of the link types on Ethernet interfaces and allows Ethernet interfaces to join VLANs after the auto-negotiation. This eliminates the need to manually configure link types of Ethernet interfaces, reducing the workload.

Implementation

When Layer 2 devices on the network shown in Figure 4-10 are successfully connected, the physical status of interfaces becomes Up. After LNP negotiation is complete, user-side interfaces on Switch4, Switch5, Switch6, and Switch7 join VLAN 1 as access interfaces, and interfaces between switches become trunk interfaces that allow all VLANs.

Figure 4-10  Typical LNP networking
  • After LNP is enabled, LNP negotiation is triggered in the following situations:

    • The local device receives LNP packets from the remote device.
    • The local configuration or interface status changes.

    In addition to access, hybrid, trunk, and Dot1q tunnel, LNP provides the following link types:

    • negotiation-desirable: The local device actively sends LNP packets.
    • negotiation-auto: The local device does not actively send LNP packets.
    NOTE:

    An interface that is negotiated as a trunk interface allows all VLANs by default; therefore, a loop prevention protocol (for example, STP, RSTP, MSTP, or VBST) needs to be deployed to prevent loops.

    If a loop prevention protocol is deployed on a Layer 2 network, LNP negotiation can succeed even on a blocked interface.

  • LNP negotiation

    The link type of the remote Layer 2 Ethernet interface determines the negotiation result. Table 4-3 describes LNP negotiation results on a Layer 2 interface in Up state.

    NOTE:
    • If the two ends of an Eth-Trunk link have different numbers of member interfaces, the LNP negotiation may fail (the link type of an interface will be set to access when the negotiation fails).

    • If the link type of the Layer 2 Ethernet interface is set to access, hybrid, trunk, or Dot1q tunnel, LNP negotiation does not take effect on the interface.
    Table 4-3  LNP negotiation

    Local LNP Negotiation Mode

    Remote Link Type or LNP Negotiation Mode

    Negotiated Local Link Type

    Status of Remote Link Type

    negotiation-desirable/negotiation-auto

    Access (LNP negotiation enabled)

    Access

    Access

    Hybrid (LNP negotiation enabled)

    Trunk

    Hybrid

    Dot1q tunnel (LNP negotiation enabled)

    Access

    Dot1q tunnel

    Trunk (LNP negotiation enabled)

    Trunk

    Trunk

    LNP negotiation not supported or disabled

    Access

    Uncertain

    negotiation-desirable

    negotiation-desirable

    Trunk

    Trunk

    negotiation-desirable

    negotiation-auto

    Trunk

    Trunk

    negotiation-auto

    negotiation-auto

    Access

    Access

    LNP negotiation depends on communication between both ends. When the communication is delayed, the link type may be incorrectly negotiated. After three rounds of communication are complete, the link type is in stable negotiation state. Otherwise, the link type of the interface stays in negotiation state. Before the link type enters the stable negotiation state, the interface in blocking state does not forward packets. This prevents forwarding errors.

    The VLAN Central Management Protocol (VCMP) domain name affects LNP negotiation. The link type can be set to trunk only when domain names at both ends are consistent or the domain name of at least one end is empty; otherwise, the link type is set to access.

Translation
Download
Updated: 2019-01-18

Document ID: EDOC1100038103

Views: 124332

Downloads: 52

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