Operations 31 min read

How to Diagnose and Recover Physical Interface DOWN Issues on Huawei Switches

This guide explains how to check interface status, identify hardware or software causes of a physical DOWN state, and follow a step‑by‑step troubleshooting process—including indicator lights, CLI commands, log analysis, media checks, and environmental factors—to restore interfaces to UP on Huawei networking devices.

Open Source Linux
Open Source Linux
Open Source Linux
How to Diagnose and Recover Physical Interface DOWN Issues on Huawei Switches

Part 1 Introduction

This document describes how to view interface status and, when an interface is in a physical DOWN state, how to locate the cause of the fault and restore the interface to an UP state. Physical DOWN can be caused by hardware failures (local or remote device components such as line cards, ports, optical modules, fibers, cables) or software failures (mismatched configuration such as port negotiation mode, speed, duplex). To analyse the cause precisely, the article uses five fault‑injection points as clues and follows a five‑step troubleshooting order: human‑error‑induced faults, device‑hardware faults, media faults, media‑usage errors, and environmental faults.

This document describes how to view interface status and, when the interface physical state is DOWN, how to locate the cause of the fault and restore the interface to UP. The main reasons for physical DOWN are hardware failures and software configuration mismatches. Hardware failures include local or remote device component failures such as line cards, ports, optical modules, fibers, or cables. Software failures mainly involve inconsistent configuration on both ends of the link, such as mismatched port negotiation mode, speed, or duplex. To precisely analyze the cause, the article uses the possible fault injection points as clues and follows a five‑step troubleshooting order: human‑error‑induced faults, device‑hardware faults, media faults, media‑usage errors, and environmental faults.

Part 2 How to View Interface Status

1. Identify Interface Status via Port Indicator Lights

If you can physically access the device, observing the port LEDs provides the fastest way to recognize the current status. For the S6730‑H48X6C, LED 4 indicates a 10GE optical port, and LED 5 indicates a 40GE/100GE optical port.

Table: Business Interface Indicator Light Meaning

LED Color

LED State

Meaning

-

Off

No connection or the interface is administratively shut down; the interface cannot send/receive packets.

Green

Steady

Interface has a link.

Green

Flashing

Interface is transmitting/receiving data.

Yellow

Flashing

Interface is transmitting/receiving data.

2. View Physical Status with CLI Commands

You can run the command display interface brief in any view to see the physical status of all interfaces (the PHY field in the output).

<HUAWEI> display interface brief<br/>PHY: Physical // indicates the physical status of the interface<br/>*down: administratively down<br/>^down: standby<br/>~down: LDT down<br/>#down: LBDT down<br/>(l): loopback<br/>(s): spoofing<br/>(E): E‑Trunk down<br/>(b): BFD down<br/>(e): ETHOAM down<br/>(dl): DLDP down<br/>(d): Dampening suppressed<br/>(ld): LDT block<br/>(lb): LBDT block<br/>(lp): Loop‑detect block<br/>(ms): MACsec down<br/>(o): Observe‑port forwarding down<br/>InUti/OutUti: input utility / output utility<br/>Interface   PHY   Protocol  InUti  OutUti  inErrors  outErrors<br/>Ethernet0/0/0   up    up    0.01%  0.01%   0   0<br/>GigabitEthernet1/0/0   down  down  0%  0%   0   0<br/>…

Or run display interface <type> <number> to view the current physical state of a specific interface (the "current state" field).

<HUAWEI> display interface gigabitethernet 0/0/12<br/>GigabitEthernet0/0/12 current state : Administratively DOWN<br/>Line protocol current state : DOWN<br/>Description: Switch Port, Link‑type : access(negotiated),<br/>PVID :1, TPID :8100(Hex), The Maximum Frame Length is 9216<br/>IP Sending Frames Format is PKTFMT_ETHNT_2, Hardware address is 000b‑0974‑a475<br/>Last physical up time: 2013‑08‑10 21:09:51<br/>Last physical down time: 2013‑08‑10 21:10:51<br/>Current system time: 2013‑08‑10 21:15:06<br/>Port Mode: COMMON FIBER<br/>Speed : 1000, Loopback: NONE<br/>Duplex: FULL, Negotiation: ENABLE<br/>Mdi: -, Flow‑control: DISABLE<br/>Last 300 seconds input rate 96 bits/sec, 0 packets/sec<br/>Last 300 seconds output rate 96 bits/sec, 0 packets/sec<br/>Input peak rate 15184 bits/sec, Record time: 2013‑08‑10 17:45:05<br/>Output peak rate 15184 bits/sec, Record time: 2013‑08‑10 17:45:05

In the example above, the interface GigabitEthernet0/0/12 shows "Administratively DOWN", meaning the shutdown command was applied. To bring the interface up, execute undo shutdown in the interface view.

Explanation: For a Layer‑2 physical interface (default Ethernet mode), if the current state is UP, the line‑protocol state is also UP. For a Layer‑3 physical interface (after undo portswitch ), the line‑protocol becomes UP only when both the current state is UP and protocol negotiation succeeds.

Additional useful commands for interface configuration or statistics:

Command

Description

display interface counters

Show statistics of packets sent/received on physical interfaces.

display interface ethernet brief

Show brief Ethernet interface info, including physical status, auto‑negotiation, duplex, speed, and recent bandwidth utilization.

display counters error

Show error packet statistics for interfaces.

display error‑down recovery

Show interfaces in Error‑Down state, the cause, recovery delay, and remaining time.

Part 3 Causes of Physical DOWN and Recovery Methods

4. Human‑Error‑Induced Physical DOWN

Cause Description

If an interface changes from UP to physical DOWN, first check whether any recent improper operations occurred, such as unplugging cables incorrectly or accidentally loosening connections. If the cable is fine, investigate possible misconfiguration commands.

Fault Location Method

In any view on both connected devices, run display interface <type> <number> to view the current running state and interface statistics.

<HUAWEI> display interface gigabitethernet 0/0/12<br/>GigabitEthernet0/0/12 current state : DOWN<br/>Line protocol current state : DOWN<br/>Port Mode: COMMON FIBER<br/>Speed : 1000, Loopback: NONE<br/>Duplex: FULL, Negotiation: ENABLE

Fault Recovery Methods

If the "current state" field is "Administratively down", the interface was shut down manually; execute undo shutdown in the interface view.

If the "current state" is "DOWN", verify that speed, duplex, and auto‑negotiation settings match on both ends; adjust as needed.

If the "current state" is "ERROR DOWN (down‑cause)", the interface was shut down by an error event. Use the specific down‑cause information to troubleshoot, then either manually recover (shutdown → undo shutdown or restart) or configure automatic recovery with error‑down auto‑recovery cause … interval ….

5. Device‑Hardware‑Induced Physical DOWN

Cause Description

Failures of line cards, individual ports, or remote device anomalies directly cause physical DOWN. Therefore, checking whether the device hardware itself is faulty is a key step.

Fault Location Method

Run display interface brief in any view to see a concise list of all interfaces and their PHY status.

<HUAWEI> display interface brief<br/>Interface   PHY   Protocol<br/>GigabitEthernet0/0/1  down  down<br/>GigabitEthernet0/0/2  down  down<br/>…

If multiple interfaces go DOWN simultaneously, the cause is likely a line‑card or remote‑device failure. If a single interface goes DOWN, inspect the physical port for bent or missing metal tabs. If the appearance is normal, run loopback internal in the interface view; if the state becomes UP, the internal hardware is fine, otherwise the port hardware is defective.

<HUAWEI> system-view<br/>[HUAWEI] interface gigabitethernet 0/0/1<br/>[HUAWEI-GigabitEthernet0/0/1] loopback internal<br/>[HUAWEI-GigabitEthernet0/0/1] display this interface<br/>GigabitEthernet0/0/1 current state : UP<br/>Line protocol current state : UP

Fault Recovery Methods

Multiple interfaces on the same line card are DOWN: reset the slot with reset slot‑<slot‑id>; if the problem persists, replace the line card.

Multiple interfaces are DOWN because the remote device is in a failover, sleep, or reboot state: wait for the remote device to stabilize; the interfaces will usually recover automatically.

Single interface is DOWN: check the cable for damage and replace if necessary; if the port hardware is faulty, replace the port or use another spare port.

6. Media‑Fault‑Induced Physical DOWN

Cause Description

Physical interfaces can be electrical (RJ45) or optical (SFP). Aging, damage, or abnormal optical power of the media can cause a physical DOWN.

Fault Location Method

Electrical media: verify correct cabling, ensure the same cable is used on both ends, check for improper jumpers, confirm proper cable category and length (≤100 m, at least Cat‑5e for Gigabit), and test pair status with virtual‑cable‑test.

[HUAWEI] interface gigabitethernet 0/0/1<br/>[HUAWEI-GigabitEthernet0/0/1] virtual‑cable‑test<br/>Warning: The command will stop service while, Continue?[Y/N] y<br/>Info: This operation may take a few seconds. Please wait for a moment...done.<br/>Pair A length: 1 meter(s)<br/>Pair B length: 1 meter(s)<br/>Pair C length: 1 meter(s)<br/>Pair D length: 1 meter(s)<br/>Pair A state: Ok<br/>Pair B state: Ok<br/>Pair C state: Ok<br/>Pair D state: Ok

Optical media: verify that the SFP is a Huawei‑certified module, check that the module matches the port type, and confirm that the fiber type matches the module. Use display transceiver interface to view optical parameters (temperature, voltage, bias current, Rx/Tx power) and compare them against normal ranges.

<HUAWEI> display transceiver interface GigabitEthernet 2/0/3 verbose<br/>Diagnostic information: Temperature (°C) :39<br/>Voltage(V):3.32<br/>Bias Current(mA):6.91<br/>Bias High Threshold(mA):33.34<br/>Bias Low Threshold(mA):1.67<br/>Current Rx Power(dBM):-4.59<br/>Default Rx Power High Threshold(dBM):0.00<br/>Default Rx Power Low Threshold(dBM):-16.99<br/>Current Tx Power(dBM):-5.10<br/>Default Tx Power High Threshold(dBM):0.00<br/>Default Tx Power Low Threshold(dBM):-12.50

Table: Normal Ranges for Optical Module Parameters

Parameter

Normal Range

Bias Current (mA)

Between LowThreshold and HighThreshold

Rx Power (dBM)

Between Default Rx LowThreshold and Default Rx HighThreshold

Tx Power (dBM)

Between Default Tx LowThreshold and Default Tx HighThreshold

Fault Recovery Methods

Electrical media: replace the faulty Ethernet cable.

Optical media: replace non‑Huawei‑certified SFPs with certified ones; if Rx/Tx power or bias current is out of range, replace the SFP or the fiber, and verify that the link distance and fiber type meet the design requirements.

7. Media‑Usage‑Error‑Induced Physical DOWN

Cause Description

When connecting devices, ensure that the SFP type matches the port, the SFP matches the fiber type, and the fiber is plugged in correctly. Incorrect usage can cause physical DOWN.

Fault Location Method

Run display device to view device model and slot information, confirming the line‑card name.

Check the SFP model and its compatibility with the port using hardware query tools.

On both ends, run display transceiver interface to compare SFP parameters.

Verify fiber connection polarity (TX ↔ RX) and that the correct fibers are used.

If the interface is a Combo port, check the current work mode (COMBO AUTO, FORCE FIBER, FORCE COPPER) and ensure it matches the physical media.

<HUAWEI> display interface gigabitethernet 1/0/1<br/>GigabitEthernet1/0/1 current state : DOWN<br/>Port Mode: COMBO AUTO<br/>Current Work Mode: COPPER

Fault Recovery Methods

Ensure the SFP matches the port and the fiber type; replace mismatched components.

If SFP parameters differ between ends, replace the mismatched SFPs.

Correct the fiber wiring (TX to RX, RX to TX).

For Combo ports, force the appropriate mode with combo‑port copper or combo‑port fiber so that the work mode aligns with the connected media.

8. Environment‑Induced Physical DOWN

Cause Description

Device deployment environments vary; temperature, humidity, and cable routing can affect interface status.

Fault Location Method

Check the data‑center temperature (0 °C – 45 °C) and relative humidity (5 % – 95 % RH, no condensation).

Inspect cable routing: keep power cables separate from data cables, avoid parallel placement, and verify that cables are not damaged by heat or rack wear.

Fault Recovery Methods

If temperature or humidity is out of range, upgrade the HVAC system, add dehumidifiers or humidifiers as needed. If strong‑weak cable parallelism exists, re‑route cables to separate them. Replace any cables that show damage or aging due to environmental factors.

Original Source

Signed-in readers can open the original source through BestHub's protected redirect.

Sign in to view source
Republication Notice

This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactadmin@besthub.devand we will review it promptly.

network troubleshootinghardware failureHuawei switchesinterface statussoftware configuration
Open Source Linux
Written by

Open Source Linux

Focused on sharing Linux/Unix content, covering fundamentals, system development, network programming, automation/operations, cloud computing, and related professional knowledge.

0 followers
Reader feedback

How this landed with the community

Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.