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

Configuration Guide - Interface Management

CloudEngine 12800 and 12800E V200R003C00

This document describes the interface management configuration, including basic interface configuration, Ethernet interface configuration, and logical interface configuration.

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).
Licensing Requirements and Limitations for Ethernet Interfaces

Licensing Requirements and Limitations for Ethernet Interfaces

Involved Network Elements

No other NEs are required.

Licensing Requirements

An interface is a basic feature of a switch and is not under license control.

Interface Query Tool

To use the interface query tool for CE series switches, visit http://support.huawei.com/onlinetoolsweb/DC/en/interface_query.html.

You can use this tool to obtain interface attributes such as the default auto-negotiation status, rate, and support for the auto-negotiation and flow control auto-negotiation configuration based on the interface type and connection medium.

Feature Limitations

The interface-related feature dependencies and limitations are as follows:

Auto-Negotiation

Auto-negotiation configuration on an interface includes auto-negotiation of the interface rate, flow control, training function, FEC mode, and duplex mode.

Auto-Negotiation
  • If you configure the negotiation disable command on an interface in Up state, the interface state will change from Up to Down and then to Up. Therefore, exercise caution when deciding to run this command.
  • Electrical interfaces do not support rate decrease auto-negotiation. For example, two GE electrical interfaces are connected using a network cable. If the network cable works only at the rate of 100 Mbit/s, the interfaces cannot negotiate the rate to 1000 Mbit/s and are Down.
  • If the module is replaced after the auto-negotiation mode takes effect on the interface, and the new module does not support the negotiation disable command, for example, the GE copper module is replaced with an SFP+ optical module or the high-speed cable on a 40GE optical interface is replaced with a QSFP+ optical module, the interface status and configuration vary depending on the system software version as follows:
    • In versions earlier than V100R005C00, the interface goes Down. You can run the undo negotiation disable command in the interface view to delete the original non-auto-negotiation mode configuration to make the interface go Up again.
    • In V100R005C00 and later versions, if the device conflict-policy keep-config command is configured, the configuration depends on the pre-configured medium type, the negotiation disable configuration on the interface is saved, and the interface goes Down. Otherwise, the configuration is lost and the interface goes Up. By default, the conflict policy is based on the installed medium type.
  • When a 40GE interface on the CE-L36LQ-EG card is connected to an interface on a Mellanox network adapter using a passive QSFP+ high-speed cable, the two interfaces may fail to go Up due to different 40GBASE-CR4 negotiation mechanisms used on the interfaces. In this case, disable the auto-negotiation function on the 40GE interface so that the two interfaces can go Up and communicate properly.
  • The CE-L48XS-FDA/CE-L48XS-FD cards provide 10GE interfaces 0-47. When GE optical modules are installed, 10GE interfaces 24 to 35 work in non-auto-negotiation mode by default and do not support the auto-negotiation mode configuration. The other interfaces work in auto-negotiation mode by default and support the auto-negotiation mode configuration.

Interface Rate
  • If you configure the speed auto command on an interface in Up state, the interface state will change from Up to Down and then to Up. Therefore, exercise caution when deciding to run this command.
  • After having GE copper modules installed, 10GE optical interfaces 24–35 on the CE-L48XS-FDA and CE-L48XS-FD cards cannot connect to 10M and 100M interfaces, 10GE optical interfaces on CE12800E switches cannot connect to 10M interfaces, and 10GE optical interfaces on the other cards and switches can connect to 10M and 100M interfaces.

  • If the module is replaced after the interface rate takes effect, and the new module does not support the speed configuration, for example, a GE copper module is replaced with an SFP-GE optical module that does not support the speed configuration, the interface status and configuration vary depending on the system software version as follows:
    • In versions earlier than V100R005C00, the interface goes Down. You can run the undo speed command in the interface view to delete the original rate configuration in auto-negotiation mode to make the interface go Up again.
    • In V100R005C00 and later versions, if the device conflict-policy keep-config command is configured, the configuration depends on the pre-configured medium type, the speed configuration on the interface is saved, and the interface goes Down. Otherwise, the configuration is lost and the interface goes Up. By default, the conflict policy is based on the installed medium type.
FEC
  • The default FEC mode on an interface varies according to the device model and connection medium. You can run the display interface command to check the FEC mode of an interface. Interfaces at both ends of a link must work in the same FEC mode; otherwise, the interfaces do not go Up. If their FEC modes are different, configure the same FEC mode on the interfaces when they work in non-auto-negotiation mode.

  • When 25GE interfaces are used for interconnection, you need to simultaneously enable the FEC function on two ends of a physical link to reduce the transmission bit error rate of the link.

  • On 100GE interfaces, FEC is mutually exclusive with auto-negotiation and the speed command configuration. If FEC has been configured, the system automatically deletes the FEC configuration when auto-negotiation is enabled or the speed command is configured.

  • When the negotiation status of interfaces at both ends of a link is not affected, pay attention to the following points:
    • By default, FEC is disabled on interfaces with QSFP28-100G-LR4 optical modules. According to IEEE 802.3, you are not advised to enable FEC.

    • By default, FEC is enabled on interfaces with QSFP28 optical modules excluding the QSFP28-100G-LR4 optical module. You are not advised to disable FEC because error packets may exist.

Flow Control
  • The CE12800E that installed ED-E/EG-E/EGA-E series cards does not support flow control over broadcast packets, multicast packets and unknown unicast packets.

  • Flow control and flow control auto-negotiation cannot be concurrently configured on an Ethernet interface.
  • To prevent stack packet forwarding from being affected, do not configure the flow-control command on stack member ports.

  • When traffic control is configured in a stack and traffic is forwarded between member devices in the stack, traffic control does not take effect because stack interfaces do not support the flow-control command.

  • Flow control does not take effect for traffic on the following loopback interfaces:
    • Loopback interface on the TRILL gateway

    • Loopback interface of VXLAN services

    • Outbound interface configured with MQC (traffic statistics)

    • Outbound interface configured with MQC-based traffic policing

Training Function on an Interface
  • 40GE and QSFP28 interfaces on the ED-E/EG-E/EGA-E/FD/FDA/FG1/SD/FD-X series cards, do not support the training disable configuration.
  • The training function takes effect on an interface only when the interface works in auto-negotiation mode. If you run the negotiation disable command to configure the interface to work in non-auto-negotiation mode after the training function takes effect, the training function will become ineffective.

  • If a 40GE interface is configured as a physical member interface in a stack system, the training function cannot be disabled. In V100R003C10 and earlier versions, if the training function is disabled on a 40GE interface, the 40GE interface cannot be configured as a physical member interface in a stack system. In V100R005C00 and later versions, if a 40GE interface is configured as a physical member interface in a stack system, the training disable configuration will be automatically deleted from the interface.

Duplex Mode

The switch works in full-duplex mode and does not support half-duplex mode.

Interface Split

  • [/manual/task/concept/conbody/section/ul/li/idp:point {""}) (idp:point]After interface split is configured or canceled on an interface, the original configuration on the interface will be lost. You need[/manual/task/concept/conbody/section/ul/li/idp:point {""}) (idp:point] to save configurations and restart the card to make configurations take effect for card models that do not support dynamic interface split. Therefore, exercise caution when deciding to configure or cancel interface split on an interface.
  • On the CE12800E, the interfaces that have been converted from another interface do not support synchronous Ethernet and 1588v2.
  • 10GE optical ports split from 40GE optical ports can be used for stack connections. If 40GE optical ports have been configured as stack member ports, they cannot be split.

  • In V100R003C00 and V100R003C10, 10GE or 40GE optical ports split from 100GE optical ports cannot be used for stack connections. In V100R005C00 and later versions, 10GE, 25GE, or 40GE optical ports split from 100GE optical ports can be used for stack connections.

  • After a QSFP28 interface on the CE-L36CQ-FD, CE-L36CQ-FG, CE-L36CQ-FD1, CE-L36CQ-SD, CE-L16CQ-FD, CE-L12CQ-FD cards or a 40GE interface on the CE-L36LQ-FD/CE-L24LQ-FD card converted into a 100GE interface is split into four 25GE interfaces, the four 25GE interfaces will automatically work at the rate of 10 Gbit/s after a 40GE medium is installed. Four 25GE interfaces split from a QSFP28 interface on the CE-L48XS-FDA card cannot automatically work at the rate of 10 Gbit/s after a 40GE medium is installed.
  • A 40GE uplink optical interface on a CE-L48XS-FDA card can only be split into two 10GE interfaces. Interface split must be enabled or disabled on the two 40GE interfaces of the card simultaneously.
  • If a card with effective 40GE interface split configuration is replaced by another same type card, the original interface split configuration takes effect on corresponding interfaces of the new card and the service configuration on the converted 10GE interfaces is retained. The device automatically delivers the configuration to the new card without manual intervention. However, the new card takes a longer time to start than other cards.

  • After interface split is enabled on a CE-L12LQ-EF card, the twelve 40GE interfaces on the card are split into forty-eight 10GE interfaces. If the CE-L12LQ-EF card is replaced by a 48*10G card (CE-L48XS-BA, CE-L48XS-EA, CE-L48XS-EC, CE-L48XS-ED, CE-L48XS-EF, CE-L48XS-FG, CE-L48XS-FD, CE-L48XS-FD1, and CE-L48XS-FDA), and the dimension numbering rule is used, configurations on the converted 10GE interfaces are not automatically delivered to 10GE interfaces on the new card. If the interface sequence numbering rule is used, configurations on the converted 10GE interfaces are automatically delivered to 10GE interfaces on the new card.

  • A 100GE interface on a CE-L04CF-EF or CE-L04CF-EC card can be split into ten 10GE interfaces. However, if a 100GE interface on the card is split into ten 10GE interfaces, resource entries of the extended TCAM do not take effect.

  • A 40GE or 100GE interface cannot be split if it has been allocated to a virtual system (VS). If you configure interface split on a 40GE or 100GE interface and allocate a converted interface to a VS, the configuration of the converted interface is not affected.
  • If a 40GE interface is not split and is connected to four 10GE interfaces on the remote device using a 1-to-4 cable, the 40GE interface cannot go Up and the interface indicator is off. The four 10GE interfaces on the remote device can go Up and the interface indicators are steady on. However, the interfaces cannot work properly. After interface split is correctly configured, the interfaces can work properly.

  • If a stack member switch with interface split configuration on a 40GE interface is replaced by a switch of the same model and same stack ID and slot ID, the original 40GE interface split configuration takes effect on the new switch and the service configuration on the converted 10GE interfaces is retained. The configuration is automatically delivered to the new member switch without manual intervention. However, the new member switch takes a longer time to start than other member switches.
  • In V100R003C00 and later versions, converted interfaces are numbered by adding a dimension to the original interface number. In versions earlier than V100R003C00, converted interfaces are numbered by interface sequence. If the system software version is downgraded from V100R003C00 or a later version to a version earlier than V100R003C00, the original interface split configuration is lost. You need to reconfigure the interface split function.
  • In V100R003 and earlier versions, an interface is still in Up state after the port split command is executed, and the interface split configuration takes effect after the card restarts. In V100R005 and later versions, an interface is split after the port split command is executed. The converted interfaces are in Offline state and support service configurations. After the card restarts, the converted interfaces go Up and the configurations delivered when the converted interfaces are in Offline state take effect.

Layer 3 Interface

  • Layer 3 interfaces consume chip forwarding resources, reducing the number of VLANs that can be created on the switch. After interfaces are switched to Layer 3 mode, less than 4063 VLANs can be created.
  • The VLAN, VXLAN, carrier VLAN, main interface, and Eth-Trunk where card interoperability mode is set to enhanced share system resources. If system resources are insufficient, the configuration may fail.

  • If internal forwarding resources are insufficient, you can still configure switching between Layer 2 and Layer 3 modes. However, interfaces may not be properly switched between Layer 2 and Layer 3 modes after the switch restarts.
  • Eth-Trunk member interfaces do not support the configuration of switching between Layer 2 and Layer 3 modes.
  • Multicast resources are shared by multiple services including VLAN, MAC, Eth-Trunk, M-LAG, Layer 2 protocol transparent transmission, Layer 3 physical interface, and multicast. If multicast resources in the system are insufficient for any of these services you are configuring, the system will display a configuration failure message. To solve this problem, you can delete some unnecessary service configuration, for example, delete unused VLANs.

Port Isolation

  • In V200R003C00 and later versions, the CE12800E supports Layer 2 port isolation.

  • Layer 2 port isolation can be configured for interfaces on the same switch or on different switches in a stack system. In versions earlier than V200R001C00, Layer 2 port isolation does not take effect for Layer 2 packets that are encapsulated through TRILL and VXLAN tunnels. In V200R001C00 and later versions, Layer 2 port isolation takes effect for Layer 2 packets that are encapsulated at the VXLAN service access side on the CE12800. Layer 2 port isolation for interfaces on different switches in a stack system has been supported since V100R003C10.

  • The Layer 2 port isolation and VPLS functions can be configured on a switch together only when the card interoperability mode is set to enhanced mode.

Traffic Statistics

  • By default, traffic statistics on an interface do not contain the interframe gap (IFG) or preamble in versions earlier than V100R003C10. If a switch is upgraded to V100R003C10 or a later version, traffic statistics on an interface contain the IFG and preamble by default.
For CE12800 series switches,
  • The following services are in descending order of priority: M-LAG unidirectional isolation, MQC (traffic policing, traffic statistics collection, and packet filtering), querying the outbound interface of packets with specified 5-tuple information, source MAC address, and destination MAC address, local VLAN mirroring, sFlow, NetStream, and statistics collection on VLANIF interfaces or Layer 3 sub-interfaces. When the services are configured on an interface in the outbound direction, only the service with the highest priority takes effect. For example, when both packet filtering and statistics on VLANIF interfaces are configured on a VLANIF interface, only packet filtering takes effect.

    For sFlow and NetStream, the preceding limitations apply to all interfaces in V100R005C10 and earlier versions and only to Layer 2 sub-interfaces and Layer 3 sub-interfaces in V100R006C00 and later versions.

Jumbo Frame

  • An interface checks whether the length of a packet exceeds the maximum frame length only in the inbound direction. For the CE12800 and CE12800E equipped with the ED-E, EG-E, or EGA-E series cards, an interface does not check the packet length in the outbound direction. After an interface receives protocol packets such as VXLAN, TRILL, and VLAN packets, the chip encapsulates packet headers containing certain bytes to the packets. As a result, the length of the outgoing packets may exceed that of the incoming packets. Therefore, you need to consider the packet header length when configuring the maximum frame length allowed by an interface, preventing packets from being discarded because the packet length exceeds the maximum frame length.

  • Because switches running V100R005C00 and earlier versions do not support configuration of the minimum length of a jumbo frame, pay attention to the following points during version upgrade or downgrade. (value1 specifies the maximum frame length allowed by an Ethernet interface, value2 specifies the minimum length of a jumbo frame.)
    • If value1 is configured in V100R005C00 or an earlier version and the system software is upgraded to V100R005C10 or a later version, the configuration is retained and the default minimum length of a jumbo frame is used.
    • If value1 and value2 are configured in V100R005C10 or a later version and the system software is downgraded to V100R005C00 or an earlier version, the configuration is lost.
    • If only value1 is configured in V100R005C10 or a later version and the system software is downgraded to V100R005C00 or an earlier version, the configuration is saved because both the old and new versions support this parameter.

Others

  • [/manual/task/concept/conbody/section/ul/li/idp:point {""}) (idp:point]When the interface status changes, for example, the physical configuration (auto-negotiation mode, FEC, and rate) of the interface changes and[/manual/task/concept/conbody/section/ul/li/idp:point {""}) (idp:point] the working mode (ETH/Stack and LAN/WAN) of the interface is switched, there is a possibility that various types of error packets are generated.
  • Single-fiber communication and internal loopback detection cannot be concurrently configured on an interface.
  • The CE12800E supports QSFP+ high-speed cables only in stack or M-LAG scenarios. If QSFP+ high-speed cables are used on interfaces of the switch in other scenarios, the interfaces may enter the Down (Cable for stack port only) status.

  • A 40GE interface on a switch running a version earlier than V100R005C00 and a 40GE interface on a switch running V100R005C00 or a later version cannot be connected using a QSFP+ AOC. You are advised to upgrade the system software of the two switches to the same version or replace the transmission medium.
  • In V100R005C00 and later versions, if you replace the transmission medium on an interface after entering the interface view, some features supported by the new transmission medium may not be configured in the interface view. To solve this problem, exit from the current interface view and run the interface interface-type interface-number command to enter the interface view again. For example, a 40GE optical interface supports the training function only when it connects to a high-speed cable. If you enter the view of a 40GE interface with a 40GE optical module installed and replace the optical module with a 40GE high-speed cable, you cannot configure the training disable command in the current interface view. To configure the training disable command, exit from the current 40GE interface view and enter the interface view again.
  • After 100GE optical modules are installed on 100GE interfaces of a CE-L08CF-FG1 card, only interfaces 0, 2, 4,..., and 14 can be used.

Translation
Download
Updated: 2019-05-05

Document ID: EDOC1100004195

Views: 18868

Downloads: 37

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next