Configuring IPv6 Unicast Addressing on Cisco Routers

The Configuration Goal

Throughout this lesson, we will work with a simple network topology. Imagine you need to configure Router0 to connect two separate IPv6 subnets.

Our goal is to configure the router's interfaces with the first usable address in each subnet, which by convention is ::1.

• Gig0/0: 2001:db8:aaaa:a::1/64
• Gig0/1: 2001:db8:aaaa:b::1/64

Enabling IPv6 Routing: The Essential First Step

Before a Cisco router can forward any IPv6 traffic between different networks, you must explicitly enable this functionality at a global level. Unlike IPv4, which is enabled by default, IPv6 routing is off until you turn it on. The command is ipv6 unicast-routing.

Forgetting this single command is a classic and frequent mistake. Without it, a router can have IPv6 addresses on its interfaces, but it will not build an IPv6 routing table and will not forward packets between its connected subnets.

The following lab video from Jeremy's IT Lab perfectly demonstrates the consequences of forgetting this command. Watching a ping fail and then succeed after the command is entered is a memorable way to cement its importance.

The configuration is straightforward:

Router(config)# ipv6 unicast-routing

You only need to enter this command once in global configuration mode.

Assigning Global Unicast Addresses

With IPv6 routing enabled, you can now configure the interfaces. You have two primary methods for assigning a Global Unicast Address (GUA):

1. Static Manual Configuration: You specify the entire 128-bit address yourself.
2. Static EUI-64 Configuration: You specify the 64-bit prefix, and the router generates the 64-bit interface ID automatically from the interface's MAC address.

The following video by Wendell Odom provides an excellent, in-depth explanation of both methods.

Let's summarize the commands for our topology.

Method 1: Manual Configuration

This method gives you full control and predictability. You decide the exact address. For servers or router interfaces, a simple, memorable address like ::1 is common practice.

Router(config)# interface gigabitethernet 0/0
Router(config-if)# ipv6 address 2001:db8:aaaa:a::1/64
Router(config-if)# no shutdown

Router(config-if)# interface gigabitethernet 0/1
Router(config-if)# ipv6 address 2001:db8:aaaa:b::1/64
Router(config-if)# no shutdown

Method 2: EUI-64 Configuration

This method is more automated. It's useful when you don't need a predictable host address. The address will be unique because it's based on the unique MAC address of the interface.

Router(config)# interface gigabitethernet 0/0
Router(config-if)# ipv6 address 2001:db8:aaaa:a::/64 eui-64
Router(config-if)# no shutdown

In this case, the router would take the MAC address of Gig0/0, perform the EUI-64 process (insert FFFE, flip bit 7), append the result to 2001:db8:aaaa:a, and assign that as the interface's GUA.

A Note on Link-Local Addresses

As we discussed in the last lesson, every IPv6-enabled interface requires a Link-Local Address (LLA) for local segment communication.

When you configure a GUA (or simply enable IPv6 on an interface), the router automatically generates an LLA. By default, Cisco IOS uses the EUI-64 process to create this LLA from the interface MAC address. You will see it appear in the verification commands.

However, these auto-generated addresses are long and difficult to remember. It is often best practice to manually configure a simple, predictable LLA, such as fe80::1. Since LLAs only need to be unique on the local link, you can use the same LLA on every interface of a router.

The command to set a manual LLA on Gig0/0 would be:

Router(config-if)# ipv6 address fe80::1 link-local

Verification: Checking Your Work

After configuration, verification is the most important skill. How do you confirm that the router has accepted your commands and that the interfaces are configured as you expect?

The Packet Tracer guide below walks through a full configuration and verification lab. It provides a great structure for applying all the concepts we've discussed.

Here are the key verification commands you will use most often:

• show ipv6 interface brief: This is your go-to command. It's the direct equivalent of show ip interface brief and gives you a concise summary of all interfaces, their IPv6 addresses, and their status.

  Router# show ipv6 interface brief
  GigabitEthernet0/0     [up/up]
      FE80::1
      2001:DB8:AAAA:A::1
  GigabitEthernet0/1     [up/up]
      FE80::1
      2001:DB8:AAAA:B::1
  

• show ipv6 interface <interface-name>: This provides detailed information about a specific interface, including its full GUA, LLA, the multicast groups it has joined, and parameters for Neighbor Discovery (which we'll cover soon).

• ping ipv6 <destination-address>: The standard connectivity test, adapted for IPv6.

Conclusion

In this lesson, we bridged the gap between IPv6 theory and practice. You now have the fundamental commands and procedures to bring an IPv6 network to life on a Cisco router.

Key Takeaways:

• IPv6 routing is not enabled by default. Always start with ipv6 unicast-routing in global configuration.
• You can assign Global Unicast Addresses manually with ipv6 address <address>/<prefix> for predictable addresses.
• Alternatively, you can use ipv6 address <prefix>::/64 eui-64 to have the router automatically generate the interface ID from its MAC address.
• Link-Local Addresses are automatically generated but can be manually set for simplicity using the link-local keyword (e.g., ipv6 address fe80::1 link-local).
• Your primary verification command is show ipv6 interface brief.

Now that our router interfaces have addresses, the next logical question is: how do devices on the same network learn about each other? In IPv4, this was the job of ARP. In IPv6, this and other critical functions are handled by the Neighbor Discovery Protocol (NDP). In our next lesson, we will explore the mechanisms of NDP, which is the glue that holds local IPv6 segments together.