IPv6 Address Types and Format

Why IPv6 is a full HCIA domain

HCIA-Datacom treats IPv6 fundamentals as its own exam weight, not a footnote on IPv4. H12-811 expects you to read and compress addresses correctly, classify an address by type and scope, know that IPv6 has no broadcast, and configure basic addressing on Huawei VRP. Later sections in this chapter build Neighbor Discovery, address assignment (SLAAC/DHCPv6), and IPv6 static routes on top of this vocabulary.

If you still think in IPv4-only habits—broadcasts, ARP for every L3 neighbor, classful first-octet rules—you will miss easy points. Re-anchor on 128-bit addresses, prefix lengths, unicast vs multicast, and link-local always present when IPv6 is enabled.

Address length and written form

An IPv6 address is 128 bits long. That is four times the 32-bit IPv4 address space and is the single highest-frequency length fact on the blueprint.

Canonical writing rules:

Compression rules (exam traps)

1. You may use :: only once in an address. Two compressions create ambiguity about how many zero groups each side represents.
2. Compress the longest run of zero groups when multiple runs exist (tie-break conventions exist; for HCIA, recognize legal single-:: forms).
3. A single zero group is usually written as 0, not forced into ::, unless that is the only zero run you choose to compress.
4. Prefix notation uses address/prefix-length, for example 2001:db8:1::/64. The prefix length counts leading bits of the network, exactly as CIDR does for IPv4.

Worked compressions:

Invalid exam bait: 2001::db8::1 (two :: sequences).

Prefix length habits for HCIA

You do not subtract “network and broadcast” host counts the IPv4 way for ordinary /64 LAN math on HCIA. IPv6 LAN design assumes huge Interface ID space; the exam focus is type, scope, and configuration, not 2^h − 2 tables.

Unicast address types you must classify

IPv6 unicast delivers to a single interface. The major types for HCIA:

Global unicast

Global unicast addresses are the IPv6 analog of public IPv4 addresses: they are intended to be globally unique and routable. Documentation and lab space frequently uses 2001:db8::/32 (reserved for examples—do not treat it as production ISP space). Enterprise dual-stack designs assign GUAs to interfaces that need end-to-end IPv6 reachability.

A common structure you will see in training diagrams:

• Global routing prefix + subnet ID → often totaling 64 bits of network/subnet.
• Interface ID → remaining 64 bits (manual, EUI-64, privacy, or DHCPv6 depending on method).

HCIA does not require ISP allocation math, but it does require you to spot a GUA versus link-local or multicast at a glance.

Unique local addresses (ULA)

Unique local addresses are the IPv6 parallel to RFC 1918 private space—but the prefix rules differ:

• Official block: FC00::/7.
• The bit after fc distinguishes the allocation method; practically deployed ULA is almost always fd00::/8 (locally assigned).
• Example: fd12:3456:789a:1::1/64 on a campus VLANIF.

ULA is not NATed to the Internet the way private IPv4 commonly is in HCIA stories. Treat ULA as internal-only addressing. Do not call ULA “link-local”; link-local is a different prefix and a different scope.

Link-local addresses (highest trap density)

Every IPv6-enabled interface must have a link-local address. Typical auto-generated form is fe80::/10 plus an interface identifier. Properties:

• Valid only on the local link (the L2 segment / VLAN / P2P link).
• Used heavily by Neighbor Discovery, routing protocol hellos on the link, and as next hops in many IPv6 designs.
• Same link-local prefix on every interface (fe80::…) means the address alone is not unique device-wide—VRP and hosts often require a zone/interface context when you ping a link-local target.

Exam trap: “Link-local routes across the campus core.” False. Link-local is not a campus-wide unicast plan. Another trap: treating fe80:: as optional. If IPv6 is enabled and the interface is up, expect link-local presence.

Multicast: the replacement for many broadcasts

Multicast addresses start with FF00::/8. IPv6 does not define a broadcast address type. Functions that used IPv4 limited broadcast or subnet broadcast are redesigned around multicast groups and Neighbor Discovery.

The second nibble/block of an IPv6 multicast address encodes scope (for example, link-local scope 2 in FF02::…). For HCIA, memorize FF00::/8 = multicast, FF02::1, and FF02::2, and remember no broadcast.

Special addresses

Do not confuse :: (unspecified) with “any address is fine as a host assignment.” Interfaces are not configured with :: as their operational unicast identity the way you assign 2001:db8::1.

IPv6 on Huawei VRP: enable and address

IPv6 is not “always on” in the same mental model as basic IPv4 labs. HCIA configuration sequence:

<Huawei> system-view
[Huawei] ipv6
[Huawei] interface GigabitEthernet0/0/0
[Huawei-GigabitEthernet0/0/0] ipv6 enable
[Huawei-GigabitEthernet0/0/0] ipv6 address 2001:db8:1::1/64
[Huawei-GigabitEthernet0/0/0] undo shutdown

You may also see EUI-64 style configuration on training materials:

[Huawei-GigabitEthernet0/0/0] ipv6 address 2001:db8:1::/64 eui-64

That forms the interface ID from the MAC-derived EUI-64 while keeping the configured prefix. Manual /64 host assignment remains the clearest form for static labs.

Verification

<Huawei> display ipv6 interface brief
<Huawei> display ipv6 interface GigabitEthernet0/0/0
<Huawei> display ipv6 routing-table

What “healthy” looks like:

• Interface protocol/IPv6 status up.
• Link-local FE80::… present after ipv6 enable.
• Configured GUA/ULA listed with correct prefix length.
• Connected route for the /64 (or configured prefix) appears in the IPv6 routing table—not only the IPv4 table.

Ping and traceroute have IPv6 forms (for example ping ipv6 / tracert ipv6 depending on VRP train). When testing link-local destinations, specify the outbound interface if the CLI requires a zone.

Classification drill (train like the exam)

If a question asks which type is not a valid IPv6 unicast type, broadcast is the correct answer among common distractors.

Exam traps for address types and format

• Claiming IPv6 addresses are 64 bits (confusing Interface ID length with full address length).
• Using two :: compressions.
• Calling ULA “link-local” or calling FE80::/10 “private like RFC 1918” without scope discipline.
• Expecting an IPv6 broadcast address for all hosts—use FF02::1 (or appropriate multicast) instead.
• Configuring only ipv6 address without ipv6 global and ipv6 enable on the interface (order/presence matters in labs).
• Looking only at display ip routing-table (IPv4) when troubleshooting IPv6—use display ipv6 routing-table.
• Believing link-local next hops are invalid; they are common, but scope/interface context matters.

Mastery checklist

• Expand and compress sample addresses without hesitation.
• Identify GUA, ULA, link-local, multicast, loopback, and unspecified in one glance.
• State that IPv6 has no broadcast and name FF02::1 / FF02::2.
• Configure ipv6 → interface ipv6 enable → ipv6 address on VRP and verify with display ipv6 interface brief.

With types and format solid, Neighbor Discovery (next section) explains how IPv6 finds on-link neighbors without ARP and without broadcasts.