Display Commands and Basic Troubleshooting

Visibility Before Change

On Huawei gear, skilled operators look before they type. display commands reveal interface health, IP addressing, MAC/ARP bindings, VLAN membership, routes, software version, and hardware presence. H12-811 items often paste shortened outputs and ask what is wrong or which command produced the view.

Most display commands work in user-view and also from system-view. Prefer verifying from user-view during exams and labs so you do not accidentally enter configuration mode under stress.

Core display Commands for HCIA

Memorize the six-pack that appears constantly in associate materials:

1. display ip interface brief
2. display ip routing-table
3. display arp
4. display vlan
5. display version
6. display device

Interpreting display ip interface brief

This is often the first command after login. Mentally scan:

If physical is down, fix Layer 1/admin state before blaming OSPF. If physical is up but protocol is down, think about Layer 2/3 dependencies (for example PPP, or address conflicts depending on context).

Admin-down interfaces often result from shutdown. Bring them up with undo shutdown in interface-view—linking back to CLI view skills.

Routing Table Quick Read

display ip routing-table shows how the device will forward. For HCIA static and OSPF chapters you will refine this skill, but the management chapter already needs:

• Is there a route to the destination network?
• Is there a default route?
• Does the next hop look sane?
• Did your new static route appear after configuration (and after save if rebooting later)?

No route → packet will not leave correctly even if the local interface IP is perfect.

ARP and VLAN Displays

display arp answers: “Does this device know the MAC for a given next hop or host IP?” Incomplete ARP can mean:

• Host is off or firewalled
• Wrong VLAN / gateway
• Layer 2 path broken
• Addressing mismatch

display vlan answers: “Is the port in the VLAN I think it is?” Combined with access/trunk knowledge from later chapters, it is the switching counterpart to the routing table.

When inter-VLAN routing fails, a productive trio is:

1. display vlan
2. display ip interface brief (VLANIF up/up with correct IP)
3. display arp / ping

Version and Device Hardware

display version confirms you are on the expected VRP release before following version-specific lab notes. Uptime can hint at unexpected reloads.

display device (and related hardware displays) confirm cards/modules are registered—useful on chassis or modular platforms and for “is the interface hardware even present?” questions.

ping and tracert on VRP

Connectivity tools run from user-view:

<Huawei> ping 192.0.2.1
<Huawei> tracert 192.0.2.1

Notes for exam and lab:

• Ping success proves reachability under current ICMP rules, not that every application port works.
• Ping failure is a symptom, not a root cause—follow with interface, ARP, VLAN, and routing displays.
• Extended ping options exist on many platforms (source IP, count, size); HCIA mainly expects standard usage and interpretation of success vs failure.
• tracert (Huawei spelling) is the counterpart to traceroute; recognize the keyword form used on VRP.

Source-interface awareness matters when multiple interfaces exist: pinging from the “wrong” source can fail ACL or reverse-path expectations in advanced designs. At HCIA, start with simple pings between directly connected subnets, then across a gateway.

A Simple Troubleshooting Flow

Use the same storyline for almost every ticket:

1. Clarify symptom — “PC cannot reach gateway” vs “OSPF down” vs “cannot SSH.”
2. Local device health — display version / display device if hardware or reload is suspected.
3. Interface layer — display ip interface brief, then detailed display interface if errors matter.
4. Switching context — display vlan, MAC table as needed.
5. L3 adjacency context — display arp, display ip routing-table.
6. Path test — ping, then tracert if multi-hop.
7. Config evidence — display current-configuration for the feature under suspicion.
8. Change minimally — fix the proven fault only.
9. Re-verify with the same displays and ping.
10. save if the fix must survive reboot.

This flow prevents the classic mistake of redistributing OSPF because a port was administratively down.

Mapping Symptoms to First Commands

Display vs Configuration Mental Model

Exam distractors mix these families. “Which command shows the routing table?” → display ip routing-table, not ip route-static.

Worked Mini-Scenario

Problem: From Switch A you cannot ping 10.1.1.2 on Switch B.

1. On A: display ip interface brief — confirm source interface IP and up/up.
2. On A: display vlan — confirm the connecting port is in the expected VLAN if Layer 2 switched.
3. On A: ping 10.1.1.2 — document failure.
4. On A: display arp — is there an incomplete entry for 10.1.1.2?
5. On A: display ip routing-table — is 10.1.1.0/24 connected or routed?
6. On B: repeat interface and VLAN checks.
7. Only after evidence, fix the actual fault (for example undo shutdown, correct access VLAN, or correct IP/mask).
8. Ping again; save.

Exam Traps

• Choosing a configuration command when the question asks for verification.
• Ignoring protocol down while celebrating a configured IP address in the text of the question.
• Using Cisco show ip route wording instead of Huawei display ip routing-table.
• Assuming ping success means the running config is saved.
• Troubleshooting routing before confirming the interface is not shut down.
• Forgetting Huawei tracert spelling in multiple-choice stems.

Practice Goals

After this section you should, without notes, list the six-pack of display commands and state what failure each best exposes. You should also narrate a five-step troubleshoot for “cannot ping across VLANs” using only VRP keywords. Those habits transfer directly into VLAN, STP, OSPF, ACL, and NAT chapters where deeper feature displays are added on top of this foundation.

Device management on HCIA is not a soft introductory topic—it is the language the rest of the exam speaks. Views, save discipline, secure access, and display-driven troubleshooting are how Huawei expects an associate engineer to work every day.