Study guide
AAA with Local, RADIUS, and HWTACACS
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
AAA with Local, RADIUS, and HWTACACS
Key Takeaways Explain This Topic AI
AAA means Authentication (who are you?), Authorization (what may you do?), and Accounting (what did you do?).
Local AAA stores users on the device; RADIUS and HWTACACS centralize credentials on external servers for scalable multi-device control.
RADIUS commonly uses UDP (authentication often associated with port 1812) and encrypts passwords, not the entire packet body; HWTACACS uses TCP and encrypts the full body—a classic compare item.
Local-user configuration sets password, privilege level (0–15), and service-type (terminal, telnet, ssh, ftp, and others).
Device login schemes can prefer local, RADIUS, HWTACACS, or combinations; wrong service-type or missing scheme binding causes “password correct but login fails” symptoms.
Last updated: July 2026
AAA with Local, RADIUS, and HWTACACS
Quick Answer: AAA = Authentication , Authorization , Accounting . On Huawei devices, start with local-user accounts (password, privilege level , service-type ). For centralized control, use RADIUS (UDP-based, password-focused encryption) or HWTACACS (Huawei TACACS+ family: TCP , encrypts the entire body , clean separation of authZ). HCIA tests definitions, local-user attributes, and protocol comparisons more than every RADIUS attribute ID.
Controlling who can log into network devices—and what they can run after login—is as important as filtering data-plane packets with ACLs. AAA is the framework that answers identity questions consistently across console, Telnet, SSH, and sometimes network access services. This section ties local configuration to centralized servers you will see named on H12-811.
The three A’s, without slogans only
- Component Question answered Datacom examples
- Authentication Who is the user? Username/password against local database or RADIUS/HWTACACS
Authorization What is the user allowed to do? Privilege level 15 vs 1; command set; VLAN/service entitlement in broader NAC
Accounting What did the user do, and when? Login/logout records, command accounting (especially strong with TACACS-family)
Exam trap: mixing the words. “Defines what an authenticated user may do” is authorization , not authentication. “Records session start/stop” is accounting . “Validates credentials” is authentication .
Authentication can succeed while authorization still blocks configuration—exactly the symptom when a user has a valid password but privilege level is too low for system-view tasks.
- Local AAA: users on the box
- Local users live in the device configuration under the aaa view. Teaching-pattern commands: [Huawei] aaa
- [Huawei-aaa] local-user netadmin password irreversible-cipher ********
- [Huawei-aaa] local-user netadmin privilege level 15
- [Huawei-aaa] local-user netadmin service-type terminal ssh
- [Huawei-aaa] local-user auditor password irreversible-cipher ********
- [Huawei-aaa] local-user auditor privilege level 1
- [Huawei-aaa] local-user auditor service-type terminal ssh
(Password encoding keywords vary by software train— irreversible-cipher is common in modern materials. Learn the attributes .)
Privilege level
- Level band Typical association on exam
- 0 Visit / extremely limited
- 1 Monitoring-oriented
- 2–9 Partial configuration (policy-dependent)
- 10–15 Management; 15 = full control
Privilege is authorization after authentication . A level-1 user may open an SSH session and run many display commands yet fail to change OSPF or ACLs. That is working as designed, not a mysterious VRP bug.
service-type
service-type lists which access methods may use the account:
- service-type value (examples) Allows
- terminal Console / terminal access
- telnet Telnet logins
- ssh SSH/STelnet logins
- ftp FTP access if used
- combinations e.g. terminal ssh
If an account has service-type telnet only, SSH login fails even with the correct password. Conversely, omitting terminal can block console use of that user depending on authentication mode. Always align service-type with how the engineer will connect.
When local AAA is enough
- Situation Local users fit well
- Lab or small site Few devices, few admins
- Break-glass account Local super user if RADIUS is down (design choice)
- Initial deployment No AAA server reachable yet
Local databases do not scale: twenty routers with the same local password that never rotates is an operational and security problem. That motivates RADIUS/HWTACACS.
Centralized AAA: why leave the box
Centralized servers give one place to create, disable, and audit admin accounts. Benefits HCIA expects you to articulate:
- Consistent credentials across many devices
- Faster offboarding when staff leave
- Stronger accounting and change tracking
- Optional separation of authentication and authorization policy
Devices become AAA clients . They forward authentication requests to a server group and enforce the result (accept/reject, privilege attributes, etc.).
RADIUS essentials
RADIUS (Remote Authentication Dial-In User Service) is widely used for both network access (802.1X, VPN) and device administration .
- Attribute RADIUS exam facts
- Transport UDP
- Auth port (common) 1812 (legacy 1645 may appear in older texts)
- Accounting port (common) 1813 (legacy 1646)
Encryption Encrypts the password field; much of the rest of the packet is not fully encrypted like TACACS-body encryption
- Model Often combines authentication and authorization in the Access-Accept path
- Reliability UDP is connectionless; retransmits are application-driven
On Huawei, you define a RADIUS server template (server IP, shared key, ports) and reference it from an AAA authentication scheme. Exact command trees vary by version; conceptual chain is:
Reachability to the RADIUS server (routing, firewall allowing UDP 1812/1813).
Matching shared key on device and server.
AAA authentication scheme using RADIUS.
Domain or user-interface / login configuration that selects that scheme.
Test login; watch server logs if reject occurs.
Shared-key mismatch is a top real-world failure mode and a fair exam distractor explanation (“server unreachable” vs “key wrong” both yield auth failure from the client’s point of view).
HWTACACS essentials
HWTACACS is Huawei’s TACACS+ family implementation for device management AAA. Compare it carefully with RADIUS—this is a high-value table for H12-811.
- Attribute RADIUS HWTACACS (TACACS+ family)
- Transport UDP TCP (commonly associated with port 49 )
- Encryption scope Password-oriented Entire body encrypted
- Auth vs AuthZ Often tightly coupled in practice Clean separation of authentication, authorization, accounting
Command authorization Less granular historically for device admin Strong fit for per-command authorization/accounting
Typical use Access networks + many NAS cases Device administration excellence
Exam trap: “Which protocol encrypts the entire authentication packet body and uses TCP?” → HWTACACS , not RADIUS. “Which uses UDP 1812 for authentication?” → RADIUS .
HWTACACS configuration conceptual chain mirrors RADIUS: server host, shared key, scheme binding, domain/login method, test. TCP’s connection-oriented nature can make firewall troubleshooting slightly different (stateful TCP 49 vs UDP 1812).
Schemes, domains, and method lists (conceptual)
Huawei AAA separates what protocol to use from when to use it :
- Building block Role
- Local user database On-box identities
- RADIUS/HWTACACS server template How to reach external servers
- Authentication / authorization / accounting schemes Ordered methods (e.g., RADIUS then local)
- Domain Ties user@domain or default domain to schemes
- Access service (SSH/Telnet/console) Triggers AAA for that channel
A common resilient design: authenticate RADIUS first, fall back to local if the server is unreachable—so a WAN outage does not lock every engineer out. Exam stems may ask what happens if only RADIUS is configured and the server is down: remote logins fail unless a local fallback or console break-glass exists.
Local vs RADIUS vs HWTACACS decision table
- Need Prefer
- Single lab switch, two admins Local users
- Many campus devices, one IT identity store RADIUS or HWTACACS
- Strong command-level authorization/accounting for admins HWTACACS
- Wireless/802.1X style access auth (broader eco-system) Often RADIUS
- Encrypt entire TACACS-style body on TCP HWTACACS
- UDP auth to existing RADIUS farm RADIUS
You can run mixed designs: local emergency user + centralized primary authentication.
Tying AAA back to remote management
From earlier VRP basics, remote SSH needs more than a user object:
- Device IP reachability
- SSH/STelnet server enabled and keys present
- VTY user-interface authentication mode set for AAA/scheme as required
- User permitted by service-type ssh
- Privilege high enough for the task
- Optional ACL on VTY limiting source addresses
AAA failures hide inside that stack. Systematic isolation:
- Test Isolates
- Console local login works Local user password/level basics OK
- SSH fails, console works service-type, VTY, SSH server, or route
- RADIUS reject in server log Credential or policy on server
- No packet to server Routing/firewall/DNS/IP of template
- Accept but low privilege Authorization attributes / local level
- Security hygiene at HCIA level
Prefer SSH over Telnet for device admin.
Do not reuse level-15 passwords across all gear without a vault/process.
Disable unused service-types.
Keep a documented break-glass local account with controlled storage.
Align accounting so privileged changes are attributable—especially when multiple engineers share responsibility.
Exam traps
Swapping definitions of authentication, authorization, and accounting.
Claiming RADIUS encrypts the entire packet like HWTACACS.
Assigning TCP 49 to RADIUS or UDP 1812 to HWTACACS.
Creating a local user without service-type ssh then troubleshooting routing for an hour.
Confusing privilege level with VLAN ID, ACL number, or OSPF process ID.
Assuming centralized AAA removes the need for any local emergency access design.
Integrated mini-scenario
Company policy: all SSH logins to campus routers use HWTACACS; if the HWTACACS server is down, a local user breakglass level 15 with service-type ssh terminal may authenticate. RADIUS remains used for 802.1X on switches, not for these router admin logins.
HCIA-style questions drawn from that story:
Which protocol carries router admin auth with full-body encryption? HWTACACS .
What local attributes must breakglass have? Password, level 15 , service-type including ssh.
If HWTACACS is up but the user is only authorized for level 1, can they rewrite ACLs? No —authorization limits them.
What to memorize for exam day
Expand AAA correctly in one sentence each.
Local-user triad: password, privilege, service-type.
RADIUS: UDP, 1812/1813, password encryption scope.
HWTACACS: TCP, full-body encryption, strong admin AuthZ/accounting story.
Centralized AAA needs reachability, shared key, and scheme binding—not only a username on the server.
Combine this chapter with ACLs: data-plane traffic-filter controls packets; AAA controls who drives the CLI that writes those filters. Both are network services weighted topics on HCIA-Datacom—treat them as paired skills for secure operations.