Feature Requirements |
Series |
Models |
|---|---|---|
The commands used to query information about interfaces do not support offline interfaces. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The interface fixed index function is dependent on device.sys files. When the data in device.sys files is deleted, the interface index may change after the device restart. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
1, A GE electrical interface works at the rate of 1000 Mbit/s and in auto-negotiation mode by default. You can forcibly change the rate but ensure that the rate is the same as that on the peer end, When you set the rate to 10 Mbit/s or 100 Mbit/s, the auto-negotiation mode is automatically canceled. 2, On a GE interface card on which both optical and electrical interfaces can be used, after the Ethernet electrical module is removed and an Ethernet optical module is inserted, the system automatically clears configuration commands on the involved electrical interface. |
NetEngine 8000 F |
NetEngine 8000 F1A |
1, When a physical interface in flexible Ethernet (FlexE) mode joins a FlexE group, services on all the FlexE interfaces in the FlexE group are intermittently interrupted, which lasts 50 ms. 2, When a physical interface in FlexE mode exits from a FlexE group, services on all the FlexE interfaces in the FlexE group are intermittently interrupted. Services on the FlexE interfaces that use timeslots of the physical interface are interrupted for 200 ms. Services on the FlexE interfaces that do not use timeslots of the physical interface are interrupted for 50 ms. |
NetEngine 8000 F |
NetEngine 8000 F2A |
1, Before configuring a working mode (optical or electrical) for a GE interface, delete all the configurations on the interface. 2, After you remove an Ethernet electrical module from an 8-Port 100/1000Base-X-SFP Physical Interface Card and insert an Ethernet optical module, the system automatically clears the command configurations related to the involved electrical interface. |
NetEngine 8000 F |
NetEngine 8000 F1A |
XGE interfaces are under PAF control. A 10GE interface is renamed as an XGE interface after the PAF is installed on the device and the device is restarted. The original 10GE interface configurations are lost, and reconfiguration needs to be performed on the XGE interface. After the AP for interface extension is installed with the PAF and restarted, if the external communication interface is a 10GE interface, the external communication interface needs to be reconfigured. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When an L2VE interface is connected to an L3VE interface and the L2VE interface and Eth-Trunk interface are bound to the same local VSI, you need to manually change the MAC address of the L3VE interface or Eth-Trunk interface to implement Layer 3 communication between the Eth-Trunk interface and L3VE interface. Otherwise, Layer 2 MAC flapping occurs. The configuration method is as follows: Run the "mac-address" <mac-address> command in the VE interface view to change the MAC address of the VE interface. Run the "set access-ve-mac" <mac-address> command in the slot view to change the MAC address of the L3VE interface. Run the "mac-address" <mac-address> command in the Eth-Trunk interface view to change the MAC address of the Eth-Trunk interface. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When SQ-based rate limiting is configured on an eTM subcard and the traffic rate exceeds the SQ bandwidth, statistics about outgoing traffic on the interface are inaccurate. In this case, statistics about outgoing traffic on the sub-interface are greater than the actual traffic statistics after rate limiting. You can run the "display port-queue statistics interface" {<interface-type interface-number> | <interface-name>} [<cos-value>] "outbound" command to obtain the actual statistics about outgoing traffic. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When a router is directly connected to a non-Huawei device, if the router is powered off and then restarted, the router sends signals immediately after interface initialization. In this case, some data may be lost because the configuration restoration of the router is not complete. You can run the "port-tx-enabling-delay" <port-tx-delay-time> command in the interface view to enable the interface to delay sending signals and set the delay. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
When VPN QoS is configured for a VSI or VLL, a channelized sub-interface cannot be created for the VS. After a channelized sub-interface is created, VPN QoS cannot be configured for any VSI or VLL of the VS. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The interface of a channelized sub-interface supports only an Ethernet interface. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
Channelized sub-interfaces support only VLAN-type dot1q sub-interfaces. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
On eTM boards and subcards, when the egress traffic on a channelized sub-interface exceeds the configured bandwidth of the channelized sub-interface, the egress traffic is limited to the bandwidth of the channelized sub-interface. In this case, the number of packets, the number of bytes, and the rate in the outbound direction are incorrect. However, the statistics on unicast, broadcast, multicast, and IPv4/IPv6 dual-stack traffic are the egress traffic before the rate limit. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
The 10G WAN capability of the F1A-8H20Q physical interface is described as follows: (1) 0-27 ports: Every four ports of 0-3, 4-7, 8-11, 12-15, 16-19, 20-23, and 24-27 form a group. The four ports in each group need to be switched at the same time. (2) 28-47 ports: 10G WAN is not supported. |
NetEngine 8000 F |
NetEngine 8000 F1A |
A 50G or 100G interface automatically adapts the FEC mode for the type of the installed optical module to ensure normal service running. If the FEC modes of multiple physical interfaces in FlexE mode in a FlexE group are different, the hwFlexEGrpFecModeMismatch alarm is reported. After the alarm is generated, the FEC configuration remains unchanged on an interface even if its optical module is removed, and the alarm cannot be automatically cleared. Methods to clear the hwFlexEGrpFecModeMismatch alarm: 1. Install an optical module with the same FEC mode. 2. Delete the physical interfaces with inconsistent FEC modes from the FlexE group. 3. Run the fec-eth command to configure the same FEC mode for the physical interfaces. (This command is supported only on 100G interfaces. If the same FEC mode is set for the physical interfaces and the FEC mode of an optical module is different from that of the corresponding 100G interface, services on the interface may be adversely affected.) |
NetEngine 8000 F |
NetEngine 8000 F2A |
The display counters rate command displays only the traffic rate of packets that are sent or received by Up interfaces. The display counters rate command does not display information about Down interfaces. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |
After IP address conflict detection is disabled and the preemption function for conflicting IP addresses is enabled: 1. If the preemption function for conflicting IP addresses is disabled, the same IP address may take effect on a different interface after a device restart. 2. The preemption function for conflicting IP addresses does not take effect for VRRP virtual addresses. 3. If the IP address of the source interface specified for a service takes effect on another interface with a higher priority, the protocol status of the source interface is Down, which may cause service interruption. 4. After a conflicting IP address takes effect on an interface with a higher priority, traffic may be temporarily interrupted due to interface switchover. |
NetEngine 8000 F |
NetEngine 8000 F2A/NetEngine 8000 F1A |