Study guide
SSH, Telnet, and Console Access
Huawei Certified ICT Associate - Datacom HCIA-Datacom H12-811 V1.0
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About HCIA-Datacom H12-811 V1.0 Study Strategies and Exam Logistics
2 Chapter 1: Network Models and Ethernet Fundamentals
OSI and TCP/IP Models Ethernet Technology and MAC Addressing Data Forwarding and Campus Network Lifecycle
3 Chapter 2: IPv4 Addressing and Transport Protocols
IPv4 Addressing and Subnetting ARP and ICMP TCP and UDP Principles Common Ports and Application Protocols
4 Chapter 3: Huawei VRP Basics and Device Management
VRP CLI Views and Core Commands Configuration Save, Reset, and File System SSH, Telnet, and Console Access Display Commands and Basic Troubleshooting
5 Chapter 4: Ethernet Switching and VLANs
Switch Forwarding and MAC Address Tables VLAN Concepts and Segmentation Access, Trunk, and Hybrid Link Types VLANIF and Inter-VLAN Routing
6 Chapter 5: STP, RSTP/MSTP, and Link Aggregation
STP Concepts and Election RSTP and MSTP Eth-Trunk Static and LACP Stacking Basics for Campus Switches
7 Chapter 6: IP Routing Fundamentals
RIB, FIB, and Forwarding Decisions Static and Default Routes on VRP Route Preference and Longest Match Floating Static Routes and Blackhole Routes
8 Chapter 7: OSPF Fundamentals
OSPF Areas and Router Types Neighbor States and Adjacency LSA Types and LSDB DR/BDR Election and VRP OSPF Configuration
9 Chapter 8: ACLs and AAA
Basic and Advanced ACLs traffic-filter Application and Matching Order AAA with Local, RADIUS, and HWTACACS
10 Chapter 9: DHCP, NAT, and Network Services
DHCP Server, Relay, and Snooping NAT, Easy IP, and NAT Server FTP, TFTP, DNS, NTP, HTTP Basics
11 Chapter 10: WLAN Basics
WLAN Architecture: AC, AP, and Fit Mode CAPWAP Tunnels and Forwarding Modes WPA2, WPA3, and WLAN Security Basics Basic WLAN Configuration Concepts
12 Chapter 11: WAN Basics
WAN Concepts and Encapsulation PPP Authentication: PAP and CHAP PPPoE Basics and Client Configuration
13 Chapter 12: IPv6 Fundamentals
IPv6 Address Types and Format Neighbor Discovery and ICMPv6 Stateful and Stateless DHCPv6 IPv6 Static Routes on VRP
14 Chapter 13: SDN and NFV Fundamentals
SDN and NFV Fundamentals
15 Chapter 14: Network Management and O&M
Network Management, O&M, and Automation Basics
SSH, Telnet, and Console Access
Key Takeaways Explain This Topic AI
Console provides out-of-band local access via a serial/console cable; Telnet and SSH are in-band remote CLI methods over IP.
SSH (STelnet on Huawei) encrypts management traffic; Telnet sends credentials and session data in clear text and should be avoided on untrusted networks.
Local AAA users define username, password, service type (terminal/telnet/ssh), and privilege level for device access control.
Remote access requires IP reachability to a management interface or VLANIF, enabled server features, user authentication, and often a user-interface (VTY) configuration.
Exam items contrast security and prerequisites: console needs physical access; SSH needs keys/algorithms and stelnet enablement; Telnet is functionally simple but insecure.
Last updated: July 2026
Three Ways to Reach the CLI
HCIA-Datacom expects you to classify management access methods and know when each is appropriate.
Method Path Band Typical use
Console Serial console cable to CON/console port Out-of-band Initial deployment, password recovery, broken IP management
- Telnet TCP session to device IP (commonly port 23) In-band Lab/legacy remote CLI; clear text
- SSH (STelnet) Encrypted remote shell to device IP (commonly port 22) In-band Production remote CLI
Out-of-band means the management channel does not depend on the data-plane IP path you are troubleshooting. Console still works if routing is broken—provided you have physical or terminal-server access. In-band means you reach a device IP address across the network; if that path fails, remote CLI fails with it.
Console Access
Console is the bootstrap path:
Connect RJ45/USB console cable per hardware guide.
Use terminal software (115200/8/N/1 is common on modern Huawei gear—confirm for your model).
Authenticate if a console password or AAA is configured.
Land in user-view and proceed to system-view as needed.
On new or factory-default devices, console may allow access with minimal authentication depending on defaults and software version. Production hardening adds authentication on the console user-interface . Conceptually remember: physical presence (or remote serial concentrator) required .
Console is also how you recover when you lock yourself out of SSH or delete the management IP—another reason labs should never rely only on Telnet mid-reconfiguration.
Telnet: Simple and Insecure
Telnet remote login is easy to demonstrate in a closed lab:
Device needs a reachable IP (management interface, VLANIF, or routed interface).
Telnet server function enabled.
VTY user-interface configured to accept Telnet and an authentication mode.
User credentials exist (local user or AAA server).
From a client: telnet 192.0.2.10
Security problem: Telnet transmits usernames, passwords, and all CLI traffic in clear text . Anyone sniffing the path can capture credentials. For HCIA, the correct security recommendation is prefer SSH ; use Telnet only in isolated labs or legacy constraints.
Exam language may say “Telnet is not recommended on public networks” or ask which protocol encrypts management traffic—answer SSH .
SSH / STelnet on Huawei
Huawei documentation often uses STelnet for SSH-based terminal login. Conceptual enablement chain:
Ensure the device has a management IP and routing/reachability.
Generate or ensure existence of a local RSA/key pair used by SSH (command families such as rsa local-key-pair create appear in training labs).
Enable the SSH/STelnet server ( stelnet server enable style commands).
Configure VTY user-interfaces for SSH protocol inbound.
Create local users (or external AAA) with SSH service permission and a privilege level.
Optionally harden algorithms and idle timeouts per security policy.
Client side: ssh user@192.0.2.10
or platform GUI tools. First connection may require accepting a host key fingerprint—similar to any SSH server.
Compared with Telnet, SSH provides confidentiality and integrity for the management session. That single sentence is enough to answer many security-oriented H12-811 items.
User-Interface Lines (Console and VTY)
VRP models access channels as user-interfaces :
- User-interface Role
- user-interface console 0 Local serial console
- user-interface vty 0 4 (example range) Remote virtual terminals for Telnet/SSH
Under a user-interface you typically set:
- Authentication mode (password vs AAA / scheme—exact keywords vary by version)
- Protocol inbound permissions (Telnet, SSH)
- Idle timeout
- User privilege level for the line (where applicable)
HCIA does not require memorizing every subcommand on every release, but you must know that VTY configuration gates remote access even if a local user exists, and console configuration gates local serial access .
- Local-User AAA Basics
- For associate level, focus on local AAA users stored on the device: [Huawei] aaa
- [Huawei-aaa] local-user admin password irreversible-cipher ********
- [Huawei-aaa] local-user admin privilege level 15
- [Huawei-aaa] local-user admin service-type terminal ssh
(Exact password keyword variants exist across versions— irreversible-cipher is common in modern examples; older materials may show other forms. Learn the attributes , not only one cipher keyword.)
- Attribute Meaning
- Username Login identity
- Password Secret; store with strong encoding when available
- privilege level Command authorization band (0–15; 15 = full management)
- service-type Which access methods may use this user (terminal/console, telnet, ssh, ftp, etc.)
If service-type omits ssh , an SSH login can fail even with a correct password. If privilege is too low, the user may authenticate but cannot enter configuration commands. Both are realistic troubleshooting cases.
External AAA (RADIUS / HWTACACS) appears later in network services chapters. For device management basics, local-user remains the core building block.
Privilege Levels Revisited for Access Control
- Level Typical exam association
- 0 Visit / very limited
- 1 Monitoring-oriented
- 15 Manager / full control
Operators sometimes create a level-1 user for read-mostly staff and a level-15 user for engineers. Remote sessions inherit privileges from the authenticated user (and line settings). Misconfigured level is a reason “login works but system-view commands fail.”
Building Blocks Checklist for Remote Login
Use this checklist when a lab “cannot Telnet/SSH”:
Reachability — ping from client to device management IP; correct VRF/gateway if used.
Interface up / IP correct — display ip interface brief .
Server feature enabled — Telnet or STelnet server on.
ACL on VTY — if present, must permit client (advanced but real).
User-interface protocol — VTY allows the intended protocol.
Authentication — local user or AAA operational.
service-type — user allowed for telnet/ssh/terminal.
Firewall en route — management ports not blocked.
Console bypasses steps that depend on IP, which is why it is the recovery path.
Security Comparison for the Exam
- Criterion Console Telnet SSH
- Needs IP network path No Yes Yes
- Encrypts session Physical security model No Yes
- Best for initial build Yes Lab only Yes (after IP exists)
- Best for production remote N/A (local) No Yes
- Fails if routing broken No Yes Yes
- Common Configuration Intent (Conceptual Sequence)
A teaching-order sequence for secure remote access after basic L3 setup:
Configure management IP / VLANIF.
Create local user level 15 with ssh (and terminal) service-type.
Create RSA key pair.
Enable STelnet server.
Under VTY, set authentication and permit SSH.
Test SSH from a client before disabling console experimentation.
save .
Disabling Telnet after SSH works is a hardening step aligned with best practice, even when the exam mainly tests knowledge rather than a full hardening checklist.
Exam Traps
Claiming Telnet is encrypted.
Forgetting that remote methods need a device IP and routing.
Creating a local user without the correct service-type .
Confusing privilege level with VLAN ID or OSPF process ID.
Assuming console authentication is identical to SSH without checking user-interface console settings.
Leaving default passwords or level-15 open Telnet in “production” scenario questions—prefer SSH and strong local users.
What to Practice
Document the difference between out-of-band console and in-band SSH in one sentence each.
Create a local user with level 15 and restricted service-types in a lab.
Enable SSH, log in, then intentionally break service-type or VTY protocol and observe failure modes.
Always keep console available while changing remote authentication.
Remote management competence is not only a security topic—it is how you will spend most of your career on Huawei gear after the first rack-and-stack day.