IPv6 Fundamentals: Addressing, Neighbor Discovery, Routing, and Migration

 

IPv6 expands the address space and changes several network behaviors, but it does not eliminate the need for careful routing, security, monitoring, or troubleshooting. Administrators should understand how IPv6 addresses are structured, how hosts discover neighbors and routers, how routes are selected, and how dual-stack or transition designs behave when IPv4 and IPv6 coexist.

IPv6 addresses are 128 bits

IPv6 addresses are written in hexadecimal groups separated by colons. Leading zeros in a group can be omitted, and one consecutive run of zero groups can be compressed with :: notation.

IPv6 learning is much easier when IPv4 addressing, routing, gateways, and subnet concepts are already stable. Network+ foundations provides that prerequisite networking foundation.

Prefix length still defines the network boundary

CIDR notation remains central. A prefix such as /64 identifies the network portion used by a subnet in many ordinary LAN designs. IPv6 capacity planning is less about conserving individual host addresses and more about allocating structured, aggregatable prefix space.

Use a consistent hierarchy that leaves room for sites, environments, functions, and summarization.

Global, link-local, and other scopes serve different roles

Interfaces commonly have link-local addresses in addition to other configured addresses. Link-local communication is important for neighbor discovery and many routing relationships because it stays within the local link.

Do not assume every IPv6 address is globally reachable or interchangeable.

Neighbor Discovery replaces several IPv4-era mechanisms

IPv6 Neighbor Discovery uses ICMPv6 for functions such as neighbor resolution, router discovery, reachability information, and duplicate-address detection. It replaces the ARP model used for IPv4 local address-to-link-layer resolution.

Blocking ICMPv6 indiscriminately can therefore break essential network behavior.

Router advertisements help hosts learn the network

Routers can advertise prefix and gateway information that hosts use for automatic configuration. Depending on design, hosts may form addresses through SLAAC, use DHCPv6 for additional configuration, or use a combination.

Understand what each mechanism provides before troubleshooting a client that has an address but lacks other settings.

IPv6 has no broadcast

IPv6 relies on multicast and other mechanisms instead of IPv4-style broadcast. This changes some local-network behavior but does not remove shared-segment considerations or the need to control unwanted traffic.

Routing principles remain familiar

Routers still perform longest-prefix matching, use static or dynamic routes, and require valid return paths. OSPFv3, IS-IS, BGP, and other protocols can carry IPv6 reachability depending on the environment.

Enterprise IPv6 deployments interact with routing, switching, security, and infrastructure services rather than living as a separate protocol island. ENCOR enterprise networking provides that broader enterprise context.

Address planning should support summarization

Large address space does not justify random allocation. Assign prefixes so sites or regions can advertise summaries and so operators can infer purpose from the plan.

Address structure affects summarization, failure domains, policy, and future growth, so IPv6 planning is still a design problem even when address scarcity disappears. CCDE network design places that reasoning inside advanced network architecture.

Security policy must explicitly include IPv6

An organization can have strong IPv4 firewall rules while unintentionally allowing IPv6 traffic through a less mature path. Inventory which systems have IPv6 enabled, where it is routed, what controls apply, and how events are logged.

IPv6 changes addressing and neighbor behavior, but security boundaries still depend on routing, inspection, and policy enforcement. Fortinet network defense provides a practical network-defense context for those controls.

Dual stack creates two possible paths

In a dual-stack environment, applications may prefer IPv6 when it is available. A user can therefore experience failure even when IPv4 tests succeed, or vice versa.

Troubleshooting should record which address family DNS returned, which address the application selected, and which route and policy were used.

DNS supports IPv6 through AAAA records

A hostname can have IPv4 A records, IPv6 AAAA records, or both. Incorrect or unreachable IPv6 records can create delays or failures that disappear when users manually force IPv4.

Always compare name-resolution results with actual reachability for both families.

Migration does not require one universal method

Organizations may use dual stack, translation, tunneling, IPv6-only segments with translation to IPv4 services, or phased deployment depending on requirements. Choose a transition model that the operations team can observe and support.

Migration planning often differs across campus, branch, WAN, data-center, and cloud environments. WAN, LAN, and MAN helps keep those network-scope categories clear when deciding where IPv6 should appear first.

Dynamic routing needs IPv6-specific validation

A routing protocol can have healthy IPv4 adjacency while IPv6 address-family configuration is missing or filtered. Verify neighbors, advertised prefixes, installed routes, and policy for the address family that is actually failing.

IPv6 troubleshooting becomes an advanced routing problem once neighbor state, path selection, summarization, and convergence interact. ENARSI routing provides the route-focused depth needed beyond basic addressing.

Data centers and clouds increase the need for consistency

Virtual networks, overlays, load balancers, container platforms, and cloud services increasingly support IPv6. Inconsistent support across dependencies can create hidden fallback behavior.

Routed fabrics and structured addressing are especially important in large data centers where workload scale and east-west traffic are high. CCNP data center provides that adjacent advanced environment.

A practical IPv6 troubleshooting sequence

Identify the source IPv6 address and prefix, confirm link-local state, inspect router advertisements or DHCPv6 behavior, verify DNS AAAA results, check the routing table, test neighbor discovery, and confirm firewall policy. Compare with the IPv4 path only after documenting the IPv6 evidence.

IPv6 becomes manageable when it is treated as a first-class network path rather than an invisible secondary protocol.