Study guide

Stateful and Stateless DHCPv6

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

Stateful and Stateless DHCPv6

Key Takeaways Explain This Topic AI

SLAAC lets hosts build their own IPv6 addresses from RA-advertised prefixes (typically /64) plus an interface identifier, often learning the default router from RA.

Stateful DHCPv6 assigns IPv6 addresses (and can provide other options) with server-tracked leases, analogous to classic DHCPv4 address assignment.

Stateless DHCPv6 does not assign addresses; hosts still autoconfigure via SLAAC and use DHCPv6 only for other parameters such as DNS.

RA M and O flags guide hosts: M points to managed/stateful address config; O points to other configuration via DHCPv6.

HCIA scenarios hinge on knowing which method supplies the address versus which supplies DNS and related options—not on memorizing every DHCPv6 message name.

Last updated: July 2026

Three ways hosts get IPv6 configuration

IPv4 campus designs often funnel almost everything through DHCP : address, mask, gateway, DNS. IPv6 splits responsibilities more cleanly among Router Advertisements , SLAAC , and DHCPv6 . HCIA-Datacom expects you to distinguish three patterns:

Method Who forms the address? Who tracks leases? Typical extra info (DNS, etc.)

SLAAC only Host, from RA prefix + interface ID No DHCPv6 address lease May be limited unless RA options or manual config supply them

Stateful DHCPv6 DHCPv6 server assigns address Yes —server state Can include DNS and other options

Stateless DHCPv6 Host via SLAAC No address lease on server DHCPv6 provides other configuration (especially DNS)

The exam loves one crisp contrast: stateful DHCPv6 assigns addresses; stateless DHCPv6 does not—it only provides other parameters while SLAAC handles addressing.

SLAAC: Stateless Address Autoconfiguration

SLAAC allows a host to configure one or more IPv6 addresses without a DHCPv6 server handing out the host identifier.

High-level steps:

Interface enables IPv6 and obtains a link-local address (with DAD).

Host sends RS (optional but common) and/or receives periodic RA .

RA carries a prefix (typically /64 ) with the A (autonomous) flag set, meaning “you may autoconfigure from this prefix.”

Host builds an address: prefix + interface identifier (EUI-64, privacy extension, stable private, or OS policy).

Host runs DAD on the new address.

Host installs an on-link route for the prefix and often a default route via the advertising router (from RA router lifetime).

  • SLAAC piece Source
  • Network prefix RA prefix information
  • Interface ID Host algorithm (not DHCPv6 in pure SLAAC)
  • Default gateway RA (router’s link-local as next hop)
  • DNS Not guaranteed by classic SLAAC alone—often needs RA DNS options (where used) or stateless DHCPv6
  • Why /64 matters

SLAAC as commonly taught assumes a 64-bit interface identifier space. Advertising odd prefix lengths for SLAAC LANs is a design smell and a troubleshooting clue. HCIA static labs may still configure manual /64 s without SLAAC, but when the question says “autoconfiguration from RA,” think /64 + A flag .

SLAAC strengths and limits

  • Strength Limit
  • No address-server dependency for basic connectivity Address inventory/tracking is harder for operators
  • Fast bring-up on well-configured links DNS and other options may be missing without DHCPv6/RA options
  • Scales for large numbers of hosts Policy control over exact addresses is weaker than stateful pools
  • Stateful DHCPv6

Stateful DHCPv6 is the model closest to classic DHCPv4 address assignment:

The DHCPv6 server allocates an IPv6 address (or prefix, in prefix-delegation stories beyond pure HCIA host focus) to the client.

The server maintains state (bindings/leases).

The client uses DHCPv6 message exchanges (Solicit/Advertise/Request/Reply family—know the idea, not necessarily every timer).

The server can also supply DNS servers , domain search lists, and other options.

Hosts are steered toward managed configuration when RAs set the M (Managed address configuration) flag. Conceptual reading of flags:

  • Flag Meaning for hosts (exam-level)
  • M = 1 Use stateful DHCPv6 to obtain addresses
  • O = 1 Use DHCPv6 for other configuration (stateless DHCPv6 pattern when addresses still come from SLAAC)
  • A = 1 on prefix SLAAC allowed for that prefix

Real networks combine flags carefully. For HCIA multiple-choice, map:

Need server-assigned address + tracking → stateful DHCPv6 (M-managed model).

Need DNS but addresses from RA/SLAAC → stateless DHCPv6 (O-other model).

Default gateway remains an ND/RA concern in many designs even when DHCPv6 is present—do not assume every DHCPv6 server must hand out a gateway the IPv4 way unless the scenario says so.

Stateless DHCPv6

Stateless DHCPv6 means the DHCPv6 server does not assign addresses and does not keep per-address lease state for those hosts. Instead:

Hosts form addresses with SLAAC from RA prefixes.

Hosts still contact DHCPv6 to request other configuration parameters .

The most exam-famous “other” parameter is DNS server addresses (and related name-service options).

  • Question Stateful DHCPv6 Stateless DHCPv6
  • Does the server assign the host’s IPv6 address? Yes No
  • Does the server track address leases for those hosts? Yes No (no address binding to track)
  • Can DNS be provided? Yes Yes—that is a primary reason to run it
  • Who builds the GUA/ULA on the host? Server assignment SLAAC

If an item says: “Hosts autoconfigure addresses but still need DNS from a server,” the answer is stateless DHCPv6 (SLAAC + DHCPv6 for other info), not “stateful only,” and not “ARP.”

Side-by-side decision table

  • Design goal Prefer
  • Simple plug-and-play LAN, RA-managed prefixes, minimal services SLAAC (+ RA DNS options if available)
  • Central address inventory, fixed pools, audit of assignments Stateful DHCPv6
  • Autoconfigured addresses but enterprise DNS control Stateless DHCPv6
  • Dual-stack campus already invested in DHCP operations Often stateful or hybrid with careful RA flags
  • Lab with only static ipv6 address on routers/hosts Manual addressing; DHCPv6 optional
  • Interaction with ND (do not isolate the protocols)

Even with perfect DHCPv6, hosts still need ND:

Link-local formation and DAD .

NS/NA to reach the default router and on-link peers.

RS/RA for prefixes, flags, and router discovery.

DHCPv6 does not replace Neighbor Discovery. Saying “DHCPv6 replaces ARP” is still wrong— ND replaces ARP; DHCPv6 replaces or supplements parts of IPv4 DHCP’s configuration role.

Huawei / campus perspective for HCIA

At associate level, Huawei materials emphasize the concepts and how they fit dual-stack campus design more than a full DHCPv6 server CLI lab for every platform feature. Still, connect to VRP skills you already have:

Interfaces need ipv6 enable and addressing (manual, or host SLAAC toward a router sending RAs).

Routers participating as default gateways must run IPv6 on the client-facing interface and advertise appropriately (RA behavior is router-side).

Verification remains display ipv6 interface brief , neighbor tables, and connectivity tests ( ping ipv6 ).

For infrastructure devices in labs, static ipv6 address is common even when clients use SLAAC/DHCPv6.

When troubleshooting “host has no IPv6 DNS” versus “host has no IPv6 address,” branch correctly:

  • Symptom Likely layer of the model
  • No link-local / IPv6 disabled Interface enablement
  • No GUA, RA missing Router RA / L2 path to router
  • No GUA, RA present, A flag off, M off Flags prevent SLAAC and stateful
  • Has GUA via SLAAC, no DNS Need O-flag path / stateless DHCPv6 or RA DNS options
  • No GUA, M=1, no DHCPv6 server Stateful path broken
  • Address present, cannot reach off-link Default router/RA lifetime or routing beyond the link
  • Worked scenario A — SLAAC only

RA advertises 2001:db8:10::/64 with A=1, M=0, O=0, router lifetime > 0.

Host builds 2001:db8:10::<iid> , DAD succeeds.

Default route points to the router’s link-local.

DNS might be missing unless another mechanism exists—exam may call that out as a limitation.

Worked scenario B — Stateless DHCPv6

RA advertises the same prefix with A=1, M=0, O=1.

Host SLAAC-builds its address as before.

Host queries DHCPv6 for other config and learns DNS 2001:db8:dns::53 .

Server does not hand out the host’s GUA.

Worked scenario C — Stateful DHCPv6

RA has M=1 (and design may clear A or combine per policy).

Host obtains address from DHCPv6 pool, for example 2001:db8:10::100 .

Server records the binding.

DNS can be included in the same DHCPv6 answers.

ND still resolves the gateway MAC when sending off-link.

Comparison to IPv4 DHCP (exam language)

  • Topic IPv4 DHCP common habit IPv6 model
  • Address DHCP or static SLAAC, stateful DHCPv6, or static
  • Gateway Often DHCP option Often RA
  • DNS DHCP option DHCPv6 options and/or RA options
  • Lease tracking DHCP server Only in stateful DHCPv6 for addresses
  • L2 resolution ARP ND
  • Exam traps for DHCPv6 and SLAAC

Defining stateless DHCPv6 as “DHCPv6 without a server.” Stateless still uses a server for options; it is stateless regarding address leases .

Claiming stateful DHCPv6 is the only way to get a default gateway.

Saying SLAAC requires DHCPv6.

Mixing M and O flag meanings (M → managed addresses; O → other config).

“DHCPv6 replaces Neighbor Discovery.” False.

Assuming every host with a GUA automatically has DNS.

Forgetting DAD still runs on SLAAC and DHCPv6-assigned addresses.

Mastery checklist

Draw the three-column table: SLAAC / stateful / stateless.

Explain one sentence each for M and O flags.

Answer “who assigns the address?” and “who provides DNS?” for any scenario stem.

Keep ND in the picture for gateway and L2 resolution.

With address assignment models clear, the final section applies VRP configuration to IPv6 static routes —the control-plane tool for reachability beyond connected prefixes when dynamic IPv6 routing is not yet in play.