2.4 Interface Management
2.4.1 Why Does the Status of the Connected Ethernet Interfaces Change Between Up and Down?
This problem occurs because auto-negotiation is enabled on one interface but disabled on the other interface. Configure both interfaces to work in the same auto-negotiation mode. When auto-negotiation is enabled on one interface but disabled on the other interface, packet loss may occur even when both interfaces are in the Up state.
This problem may also occur when the network cable is loose.
2.4.2 Is the MTU of an Interface Configurable?
The maximum transmission unit (MTU) of Layer 3 interfaces is configurable. The MTU of Layer 2 interfaces is not configurable.
2.4.3 Does a Layer 2 Eth-Trunk Interface Belong to VLAN 1 by Default?
By default, an Eth-Trunk interface is in hybrid mode, and is added to VLAN 1 in untagged mode. You can run undo port hybrid vlan 1 command in the interface view to delete the Eth-Trunk interface from VLAN 1.
2.4.4 How Many Eth-Trunks Can Be Created?
Version |
AR150 Series |
AR160 Series |
AR100 Series AR120 Series |
AR200 Series AR1200 Series |
AR2201-48FE AR2202-48FE |
AR2204-48GE-P AR2204-51GE-P AR2204-51GE-R AR2204-51GE AR2204-27GE-P AR2204-27GE AR2204-24GEAR2204E AR2204E-D |
AR2204 |
AR2220E |
AR2220 AR2240 AR3200 Series |
AR2240C |
AR3600 Series |
---|---|---|---|---|---|---|---|---|---|---|---|
V200R002 and earlier versions | - | - | - | 8 | - | - | - | - | 64 | - | - |
V200R003 and V200R005 versions | 4 | 4 | - | 8 | 8 | - | 15 | - | 64 | - | - |
V200R006 versions | 4 | 8 | 8 | 8 | 8 | - | 15 | 15 | 64 | - | 64 |
V200R007 and later versions | 4 | 8 | 8 | 8 | 8 | 8 | 15 | 15 | 64 | 64 | 64 |
2.4.5 Why Does an Ethernet Subinterface Fail to Forward Packets?
The arp broadcast enable command is not executed on this subinterface.
2.4.6 How Do I View and Clear Traffic Statistics on an Interface?
To view traffic statistics on an interface, run the display interface [ interface-type [ interface-number [.subnumber ] ] ] command in any view, or run the display this interface command in the interface view.
To clear the traffic statistics on an interface, run the reset counters interface [ interface-type [ interface-number ] ] command in the user view.
2.4.7 How to check the virtual port of the device?
The virtual port (VPORT) connects to an open virtual switch (OVS) in a virtualized environment and is named GigabitEthernet0/0/x. In the display interface brief command output, the GE interface with the largest interface number is the VPORT. The information "description VirtualPort" is displayed for the VPORT.
2.4.8 Why the Physical Interface Status of a 3G Cellular Interface Is Down?
If the physical status of a 3G cellular interface (cellular interface) is Down, no 3G link is established and data service has not been transmitted yet. That is, no dialup is triggered or dialup fails on the 3G link.

If no dialup is triggered or dialup fails on a 3G link, the physical interface status is still Down even if a 3G data card (3G modem) is installed.
2.4.9 Can a Static IP Address Be Configured for a 3G Cellular Interface?
Configuring a static IP address for a 3G cellular interface may cause dialup to fail. In most cases, a network-side device dynamically allocates an IP address to a 3G cellular interface.
2.4.10 Is the UIM/SIM Card on a 3G Data Card (3G Modem) Hot Swappable?
The USIM/SIM card on a 3G data card (3G modem) is not hot swappable.
2.4.11 What Is the Difference Between the SIM and USIM Cards?
The SIM card supports only the 2G services, while the USIM card supports both 2G and 3G services.
2.4.13 Why Does Dialup Often Fail on a 3G Cellular Interface?
The possible causes are as follows:
- The 3G data card cannot be identified on the current network or is not supported on the AR.
- The 3G data card does not match the current network. For example, authentication or service required on the current network is not enabled on the data card or USIM/SIM card. As a result, authentication or negotiation fails in dialup.
- The 3G data card is not registered with available networks, due to weak signal strength or other reasons. Run the display cellular command to check information about 3G signals. The Current Service Status field must be displayed as "Service available", and the signal strength must be in the allowed range.
- An incorrect connection mode is configured on the 3G data card. For example, the 3G data card has a SIM card installed but its connection mode is set to WCDMA-only.
- The USIM/SIM card is not properly installed.
- The 2G/3G services are not enabled on the USIM/SIM card.
- The account balance of the USIM/SIM card is insufficient.
- The USIM/SIM card works incorrectly. Run the display cellular command to check whether the USIM/SIM card is in correct state. The status of the USIM/SIM card must be Ok not Not insert.
- Check whether 3G configurations, including the dialer number are correct. Check whether PPP authentication is required when the 3G cellular interface accesses a CDMA2000 network.
- No profile is configured or a profile is incorrectly configured.
- The 3G cellular interface is shut down using the shutdown command.
2.4.14 How Do I Identify the 3G Data Card Indicator?
For a WCDMA data card:
- If the indicator blinks green twice at short intervals, the data card has not registered with the network.
- If the indicator blinks blue once every 2s (0.5 Hz), the data card has registered with the network.
- If the indicator is steady blue, dialup succeeds but the data card is not transmitting data services.
- If the indicator is steady light blue, dialup succeeds and the data card is transmitting data services.
For a CDMA2000 data card:
- If the indicator blinks blue once every 2s (0.5 Hz), the data card has not registered with the network.
- If the indicator blinks blue twice at short intervals, the data card has registered with the network.
- If the indicator blinks blue once every 0.25s (4 Hz), dialup succeeds and the data card is transmitting data services.
2.4.15 How Do I Determine the Signal Strength?
Run the display cellular command to view the Current RSSI field. If the Current RSSI field displays a value smaller than -85 dBm, the signal strength is weak and the data service rate is low and unstable. If the Current RSSI field displays a value smaller than -100 dBm, data cards may fail to register with or dial in to the network.
2.4.16 Do All Interfaces Have MAC Addresses?
Each Layer 3 Ethernet interface has a MAC address.
A VLANIF interface obtains the device MAC address as its own MAC address. This MAC address is fixed.
A Bridge-if interface obtains the device MAC address as its own MAC address. This MAC address can be changed using the CLI.
The MAC address of a Layer 2 interface has no function on the device.

-
To change the device MAC address, run the set system-mac { current | default } command in the diagnosis view, save the configuration, and restart the device.
-
The system MAC address to be modified cannot be a multicast MAC address.
2.4.17 What Is a Fractional Channelized Board?
Currently, the fractional channelized board refers to the 1E1T1-F/2E1T1-F/4E1T1-F/8E1T1-F board.
The 1E1T1-F/2E1T1-F/4E1T1-F/8E1T1-F board line contains 32 timeslots that are numbered from 0 to 31. In fractional channelized mode, timeslot 0 is used to transmit synchronous information, and other timeslots can be bundled into a channel set.
2.4.18 VDSL Interconnection List
V200R007 and later versions: For details about how to connect VDSL interfaces of the AR129, AR169, AR169EW, AR169CVW, AR169EGW-L, AR169CVW-4B4S, AR169G-L, AR169-P-M9, routers to other Huawei devices, see the AR Series Router VDSL Interconnection List. You can log in to Huawei enterprise support website (http://support.huawei.com/enterprise) to obtain the list based the product model and version.
2.4.19 How Do I Solve the G.SHDSL Board Connection Failure Problem?
Table 2-37 lists G.SHDSL board connection problems and solutions.
Connected Device Vendor |
Connected Device Model |
Connected G.SHDSL Board Software Version |
Connected Device Board Type |
Connected Device G.SHDSL Chip Type |
Problem |
Solution |
---|---|---|---|---|---|---|
Alcatel |
ASAM 7301 |
5.1.18c(51.354) |
SMLT-C (3EC37140AB) |
Conexant |
The G.SHDSL interface that has the line probing function configured cannot be activated. |
Upgrade the version to V200R002C00SPC100 or later. |
HUAWEI |
UA5000 |
162 |
H601SDLB |
Conexant |
When two virtualized interfaces are bound, the G.SHDSL interface cannot be activated. |
Run the shdsl bind m-pair 2 pairs enhanced command on the G.SHDSL interface working in ATM mode to set the binding mode to enhanced. |
HUAWEI |
MA5600 |
Unknown |
SHEA |
Conexant |
When two virtualized interfaces are bound, the G.SHDSL interface cannot be activated. |
Run the shdsl bind m-pair 2 pairs enhanced command on the G.SHDSL interface working in ATM mode to set the binding mode to enhanced. |
HUAWEI |
MA5600T |
Earlier versions of 754 |
SHLB/SHLM |
Infineon |
When two virtualized interfaces of the G.SHDSL interface working in PTM mode are bound, several the G.SHDSL board cannot connect to the peer device. |
|
HUAWEI |
MA5100 |
E326/E360.1 |
H511SHLA |
Conexant |
The interface cannot be activated in ATM mode. |
|
OverTure |
HN408S |
Unknown |
- |
Infineon |
The interface works in PTM binding mode and is forced to go offline 2 minutes after being activated. The remote end incorrectly displays the message hnbdp_timeout. |
Hatteras Network Bonding Discovery Protocol (HNBDP) is a proprietary protocol of Overture. Disable HNBDP on the remote end to solve this problem. |
OverTure |
HN4000E/I |
Unknown |
- |
Infineon |
The interface cannot be activated in PTM mode. |
|
Siemens |
HiX 5300 |
1.2.2.106 |
SUSHDSL:32 |
Infineon |
The G.SHDSL board cannot connect to the peer device working in G.SHDSL mode. |
Run the shdsl capability g-shdsl command on the G.SHDSL interface working in ATM mode to configure the G.SHDSL board to work in G.SHDSL mode. |
Siemens |
Unknown |
Unknown |
- |
- |
The interface cannot be activated in ATM mode. |
In V200R006, the default modulation mode of a G.SHDSL interface is 128 PAM. The remote end does not support the 128 PAM modulation mode. Run the shdsl pam { 16 | 32 } command on the interface. The interface will go Up after the device restarts. |
ZTE |
9800 |
Unknown |
- |
- |
When two virtualized interfaces are bound, the G.SHDSL interface cannot be activated. |
Run the shdsl bind m-pair 2 pairs enhanced command on the G.SHDSL interface working in ATM mode to set the binding mode to enhanced. |
ZTE |
5200 |
Unknown |
- |
- |
When two virtualized interfaces are bound, the G.SHDSL interface cannot be activated. |
Run the shdsl bind m-pair 2 pairs enhanced command on the G.SHDSL interface working in ATM mode to set the binding mode to enhanced. |
2.4.20 Can the Combo Interface on the SRU Connect to the 100M Optical Module?
Yes, the combo interface on the SRU can connect to the 100M optical module. When the combo interface on the SRU connects to the 100M optical module, it does not support auto-negotiation mode, so the peer device must use the 100M optical module and the peer interface must be manually configured to work in full duplex mode.
2.4.21 When an SA Card Connects to an E1 Card, the Protocol Status Cannot Become Up. How Do I Solve the Problem?
When an SA card connects to an E1 card through a protocol converter such as CHANNEL-BANK, the protocol converter and E1 interface must be configured to work in unchannelized mode before the protocol status becomes up.
2.4.22 Can the E1-F Card Communicate with the E1-M Card?
The E1-F card can communicate with the E1-M card in the following scenarios:
- The E1-M card works in E1 mode and the E1-F card works in unframed mode.
- The E1-M card works in CE1 mode and the E1-F card works in framed mode. Only one channel set is created on the E1-M card and binds the same timeslots as the E1-F card.
2.4.23 On a GSM Network, Large Downstream Traffic Bursts Cause Errors in 3G Data Card Encryption and Decryption, and Services Are Interrupted. How Can I Solve This Problem?
To solve this problem, configure configure an NQA test instance to detect the 3G link status.
- Run the interface cellular interface-number command to enter the 3G cellular interface view.
- Run the modem auto-recovery track nqa admin-name test-name [ probe-cycle period ] command to configure the device to use an NQA test instance to detect the 3G link status.
- Run the modem auto-recovery track action modem-reboot fail-times times command to set the maximum number of 3G link detection failures in an NQA test instance. When the number of consecutive 3G link detection failures in an NQA test instance reaches the maximum value, the device restarts the 3G data card.
2.4.24 After a Huawei AR Router Configured with the 8E1/T1-F Card Replaces a Cisco Device Configured with the 8E1/T1-F Card and Is Connected to the Remote Device, Why Do Connected Interfaces Alternate Between Up and Down States?
In framed mode, an E1-F interface supports two frame formats: CRC4 and non-CRC4.
By default, E1-F interfaces on Huawei devices use the non-CRC4 frame format and E1-F interfaces on Cisco devices use the CRC4 frame format. If the local and remote interfaces use different frame formats, the interfaces alternate between Up and Down states after being connected. To solve this problem, run the fe1 frame-format { crc4 | no-crc4 } command on the E1/T1-F card to set the frame format of E1-F interfaces first to ensure that the local and remote interfaces use the same frame format.
2.4.25 How Do I Handle a Service Exception on an E1-F Link?
If a service exception occurs on an E1-F link, the possible cause is that the local and remote interfaces are configured with different CRC modes. By default, AR routers use 16-bit CRC mode. Devices from many other vendors may use 32-bit CRC mode. As a result, the local and remote devices cannot communicate.
Run the crc { 16 | 32 | none } command to configure the local interface to work in the same CRC mode as the remote interface. In addition, ensure that both the local and remote devices are grounded using ground cables.
Ground points on AR routers have the same appearance. The ground point on the AR151 is taken as an example, as shown in Figure 2-5.