Configuring Ipv6 Unicast Routing
Configuring Ipv6 Unicast Routing
Configuring Ipv6 Unicast Routing
This chapter describes how to configure IPv6 unicast routing on the Catalyst 3750 switch.
For information about configuring IPv6 Multicast Listener Discovery (MLD) snooping, see Chapter 40,
“Configuring IPv6 MLD Snooping.” For information on configuring IPv6 access control lists (ACLs),
see Chapter 41, “Configuring IPv6 ACLs.” For information about configuring IPv4 unicast routing, see
Chapter 38, “Configuring IP Unicast Routing.”
To use this feature, the stack master must be running the IP services image.
To enable IPv6 routing, you must configure the switch to use the a dual IPv4 and IPv6 switch database
management (SDM) template. See the “Dual IPv4 and IPv6 Protocol Stacks” section on page 39-5.
Unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.
Note For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS
documentation referenced in the procedures
Understanding IPv6
IPv4 users can move to IPv6 and receive services such as end-to-end security, quality of service (QoS),
and globally unique addresses. The IPv6 address space reduces the need for private addresses and
Network Address Translation (NAT) processing by border routers at network edges.
For information about how Cisco Systems implements IPv6, go to this URL:
http://www.cisco.com/en/US/products/ps6553/products_ios_technology_home.html
For information about IPv6 and other features in this chapter
• See the Cisco IOS IPv6 Configuration Library at this URL:
http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/12_4t/ipv6_12_4t.html
• Use the Search field to locate the Cisco IOS software documentation. For example, if you want
information about static routes, you can enter Implementing Static Routes for IPv6 in the search field
to get this document about static routes:
http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/ip6-stat_routes_ps6441_TSD_Pro
ducts_Configuration_Guide_Chapter.html
This section describes IPv6 implementation on the switch. These sections are included:
• IPv6 Addresses, page 39-2
• Supported IPv6 Unicast Routing Features, page 39-2
• Unsupported IPv6 Unicast Routing Features, page 39-8
• Limitations, page 39-8
• IPv6 and Switch Stacks, page 39-9
IPv6 Addresses
The switch supports only IPv6 unicast addresses. It does not support site-local unicast addresses, anycast
addresses, or multicast addresses.
The IPv6 128-bit addresses are represented as a series of eight 16-bit hexadecimal fields separated by
colons in the format: n:n:n:n:n:n:n:n. This is an example of an IPv6 address:
2031:0000:130F:0000:0000:09C0:080F:130B
For easier implementation, leading zeros in each field are optional. This is the same address without
leading zeros:
2031:0:130F:0:0:9C0:80F:130B
You can also use two colons (::) to represent successive hexadecimal fields of zeros, but you can use this
short version only once in each address:
2031:0:130F::09C0:080F:130B
For more information about IPv6 address formats, address types, and the IPv6 packet header, see the
“Implementing IPv6 Addressing and Basic Connectivity” chapter of Cisco IOS IPv6 Configuration
Library on Cisco.com.
In the “Implementing Addressing and Basic Connectivity” chapter, these sections apply to the
Catalyst 3750 switch:
• IPv6 Address Formats
• IPv6 Address Type: Unicast
• IPv6 Address Output Display
• Simplified IPv6 Packet Header
ICMPv6
The Internet Control Message Protocol (ICMP) in IPv6 generates error messages, such as ICMP
destination unreachable messages, to report errors during processing and other diagnostic functions. In
IPv6, ICMP packets are also used in the neighbor discovery protocol and path MTU discovery.
Neighbor Discovery
The switch supports NDP for IPv6, a protocol running on top of ICMPv6, and static neighbor entries for
IPv6 stations that do not support NDP. The IPv6 neighbor discovery process uses ICMP messages and
solicited-node multicast addresses to determine the link-layer address of a neighbor on the same network
(local link), to verify the reachability of the neighbor, and to keep track of neighboring routers.
The switch supports ICMPv6 redirect for routes with mask lengths less than 64 bits. ICMP redirect is
not supported for host routes or for summarized routes with mask lengths greater than 64 bits.
Neighbor discovery throttling ensures that the switch CPU is not unnecessarily burdened while it is in
the process of obtaining the next hop forwarding information to route an IPv6 packet. The switch drops
any additional IPv6 packets whose next hop is the same neighbor that the switch is actively trying to
resolve. This drop avoids further load on the CPU.
IPv6 Applications
The switch has IPv6 support for these applications:
• Ping, traceroute, Telnet, TFTP, and FTP
• Secure Shell (SSH) over an IPv6 transport
• HTTP server access over IPv6 transport
• DNS resolver for AAAA over IPv4 transport
• Cisco Discovery Protocol (CDP) support for IPv6 addresses
For more information about managing these applications, see the “Managing Cisco IOS Applications
over IPv6” chapter and the “Implementing IPv6 Addressing and Basic Connectivity” chapter in the
Cisco IOS IPv6 Configuration Library on Cisco.com.
IPv4
10.1.1.1
122379
IPv6
3ffe:yyyy::1
Use the dual IPv4 and IPv6 switch database management (SDM) template to enable IPv6 routing. For
more information about the dual IPv4 and IPv6 SDM template, see Chapter 8, “Configuring SDM
Templates.”
The dual desktop and aggregator IPv4 and IPv6 templates allow the switch to be used in dual stack
environments.
• If you try to configure IPv6 without first selecting a dual IPv4 and IPv6 template, a warning message
appears.
• In IPv4-only environments, the switch routes IPv4 packets and applies IPv4 QoS and ACLs in
hardware. IPv6 packets are not supported.
• In dual IPv4 and IPv6 environments, the switch routes both IPv4 and IPv6 packets and applies IPv4
QoS in hardware.
• Full IPv6 QoS is not supported. IPv6 QoS trust is supported.
• If you do not plan to use IPv6, do not use the dual stack template because this template results in
less TCAM capacity for each resource.
For more information about IPv4 and IPv6 protocol stacks, see the “Implementing IPv6 Addressing and
Basic Connectivity” chapter of Cisco IOS IPv6 Configuration Library on Cisco.com.
For information about syslog over IPv6, including configuration procedures, see the “Implementing IPv6
Addressing and Basic Connectivity” chapter in the Cisco IOS IPv6 Configuration Library on Cisco.com.
Limitations
Because IPv6 is implemented in switch hardware, some limitations occur due to the IPv6 compressed
addresses in the TCAM. These hardware limitations result in some loss of functionality and limits some
features.
These are feature limitations.
• ICMPv6 redirect functionality is not supported for IPv6 host routes (routes used to reach a specific
host) or for IPv6 routes with masks greater than 64 bits. The switch cannot redirect hosts to a better
first-hop router for a specific destination that is reachable through a host route or through a route
with masks greater than 64 bits.
• Load balancing using equal cost and unequal cost routes is not supported for IPv6 host routes or for
IPv6 routes with a mask greater than 64 bits.
Note There is a similar limitation for IPv4 SNAP-encapsulated packets, but the packets are
dropped at the switch and are not forwarded.
• The switch routes IPv6-to-IPv4 and IPv4-to-IPv6 packets in hardware, but the switch cannot be an
IPv6-to-IPv4 or IPv4-to-IPv6 tunnel endpoint.
• Bridged IPv6 packets with hop-by-hop extension headers are forwarded in software. In IPv4, these
packets are routed in software, but bridged in hardware.
• In addition to the normal SPAN and RSPAN limitations defined in the software configuration guide,
these limitations are specific to IPv6 packets:
– When you send RSPAN IPv6-routed packets, the source MAC address in the SPAN output
packet can be incorrect.
– When you send RSPAN IPv6-routed packets, the destination MAC address can be incorrect.
Normal traffic is not affected.
• The switch cannot apply QoS classification or policy-based routing on source-routed IPv6 packets
in hardware.
• The switch cannot generate ICMPv6 Packet Too Big messages for multicast packets.
Note To route IPv6 packets in a stack, all switches in the stack must be running the IP services image.
If a new switch becomes the stack master, it recomputes the IPv6 routing tables and distributes them to
the member switches. While the new stack master is being elected and is resetting, the switch stack does
not forward IPv6 packets. The stack MAC address changes, which also changes the IPv6 address. When
you specify the stack IPv6 address with an extended unique identifier (EUI) by using the ipv6 address
ipv6-prefix/prefix length eui-64 interface configuration command, the address is based on the interface
MAC address. See the “Configuring IPv6 Addressing and Enabling IPv6 Routing” section on
page 39-11.
If you configure the persistent MAC address feature on the stack and the stack master changes, the stack
MAC address does not change for approximately 4 minutes. For more information, see the “Enabling
Persistent MAC Address” section on page 5-19 in Chapter 5, “Managing Switch Stacks.”
These are the functions of IPv6 stack master and members:
• Stack master:
– runs IPv6 routing protocols
– generates routing tables
– distributes CEFv6 routing tables to stack members that use dCEFv6
– runs IPv6 host functionality and IPv6 applications
Note IPv6 packets are routed in hardware across the stack if the packet does not have exceptions
(IPv6Options) and the switches in the stack have not run out of hardware resources.
Configuring IPv6
These sections contain this IPv6 forwarding configuration information:
• Default IPv6 Configuration, page 39-10
• Configuring IPv6 Addressing and Enabling IPv6 Routing, page 39-11
• Configuring Default Router Preference, page 39-13
• Configuring IPv4 and IPv6 Protocol Stacks, page 39-13
• Configuring DHCP for IPv6 Address Assignment, page 39-15
• Configuring IPv6 ICMP Rate Limiting, page 39-18
• Configuring CEF and dCEF for IPv6, page 39-18
• Configuring Static Routes for IPv6, page 39-19
• Configuring RIP for IPv6, page 39-20
• Configuring OSPF for IPv6, page 39-21
• Configuring EIGRP for IPv6, page 39-23
• Configuring HSRP for IPv6, page 39-23
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 sdm prefer dual-ipv4-and-ipv6 {default | Select an SDM template that supports IPv4 and IPv6.
routing | vlan} [desktop]
• default—Set the switch to the default template to balance
system resources.
• routing—Set the switch to the routing template to support
IPv4 and IPv6 routing, including IPv4 policy-based routing.
• vlan—Maximize VLAN configuration on the switch with
no routing supported in hardware.
• desktop—Supported only on Catalyst 3750-12S aggregator
switches to set the switch to one of the desktop templates. If
not selected on an aggregator switch, an aggregator template
is automatically selected.
Step 3 end Return to privileged EXEC mode.
Step 4 reload Reload the operating system.
Step 5 configure terminal Enter global configuration mode after the switch reloads.
Command Purpose
Step 6 interface interface-id Enter interface configuration mode, and specify the Layer 3
interface to configure. The interface can be a physical interface,
a switch virtual interface (SVI), or a Layer 3 EtherChannel.
Step 7 no switchport Remove the interface from Layer 2 configuration mode (if it is a
physical interface).
Step 8 ipv6 address ipv6-prefix/prefix length eui-64 Specify a global IPv6 address with an extended unique identifier
(EUI) in the low-order 64 bits of the IPv6 address. Specify only
the network prefix; the last 64 bits are automatically computed
from the switch MAC address. This enables IPv6 processing on
or the interface.
ipv6 address ipv6-address link-local Specify a link-local address on the interface to be used instead
of the link-local address that is automatically configured when
IPv6 is enabled on the interface. This command enables IPv6
or processing on the interface.
ipv6 enable Automatically configure an IPv6 link-local address on the
interface, and enable the interface for IPv6 processing. The
link-local address can only be used to communicate with nodes
on the same link.
Step 9 exit Return to global configuration mode.
Step 10 ip routing Enable IP routing on the switch.
Step 11 ipv6 unicast-routing Enable forwarding of IPv6 unicast data packets.
Step 12 end Return to privileged EXEC mode.
Step 13 show ipv6 interface interface-id Verify your entries.
Step 14 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove an IPv6 address from an interface, use the no ipv6 address ipv6-prefix/prefix length eui-64
or no ipv6 address ipv6-address link-local interface configuration command. To remove all manually
configured IPv6 addresses from an interface, use the no ipv6 address interface configuration command
without arguments. To disable IPv6 processing on an interface that has not been explicitly configured
with an IPv6 address, use the no ipv6 enable interface configuration command. To globally disable IPv6
routing, use the no ipv6 unicast-routing global configuration command.
This example shows how to enable IPv6 with both a link-local address and a global address based on the
IPv6 prefix 2001:0DB8:c18:1::/64. The EUI-64 interface ID is used in the low-order 64 bits of both
addresses. Output from the show ipv6 interface EXEC command shows how the interface ID
(20B:46FF:FE2F:D940) is appended to the link-local prefix FE80::/64 of the interface.
Switch(config)# sdm prefer dual-ipv4-and-ipv6 default
Switch(config)# ipv6 unicast-routing
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# no switchport
Switch(config-if)# ipv6 address 2001:0DB8:c18:1::/64 eui 64
Switch(config-if)# end
Switch# show ipv6 interface gigabitethernet1/0/1
GigabitEthernet1/0/1 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::20B:46FF:FE2F:D940
Global unicast address(es):
2001:0DB8:c18:1:20B:46FF:FE2F:D940, subnet is 2001:0DB8:c18:1::/64 [EUI]
Joined group address(es):
FF02::1
FF02::2
FF02::1:FF2F:D940
MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds
ND advertised reachable time is 0 milliseconds
ND advertised retransmit interval is 0 milliseconds
ND router advertisements are sent every 200 seconds
ND router advertisements live for 1800 seconds
Hosts use stateless autoconfig for addresses.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and enter the Layer 3 interface on
which you want to specify the DRP.
Step 3 ipv6 nd router-preference {high | Specify a DRP for the router on the switch interface.
medium | low}
Step 4 end Return to privileged EXEC mode.
Step 5 show ipv6 interface Verify the configuration.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no ipv6 nd router-preference interface configuration command to disable an IPv6 DRP.
This example shows how to configure a DRP of high for the router on an interface.
Switch# configure terminal
Switch(config)# interface gigabitethernet1/0/1
Switch(config-if)# ipv6 nd router-preference high
Switch(config-if)# end
For more information about configuring DRP for IPv6, see the “Implementing IPv6 Addresses and Basic
Connectivity” chapter in the Cisco IOS IPv6 Configuration Library on Cisco.com.
Beginning in privileged EXEC mode, follow these steps to configure a Layer 3 interface to support both
IPv4 and IPv6 and to enable IPv6 routing.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ip routing Enable routing on the switch.
Step 3 ipv6 unicast-routing Enable forwarding of IPv6 data packets on the switch.
Step 4 interface interface-id Enter interface configuration mode, and specify the Layer 3
interface to configure.
Step 5 no switchport Remove the interface from Layer 2 configuration mode (if it is a
physical interface).
Step 6 ip address ip-address mask [secondary] Specify a primary or secondary IPv4 address for the interface.
Step 7 ipv6 address ipv6-prefix/prefix length eui-64 Specify a global IPv6 address. Specify only the network prefix;
the last 64 bits are automatically computed from the switch
MAC address.
or
Specify a link-local address on the interface to be used instead
ipv6 address ipv6-address link-local of the automatically configured link-local address when IPv6 is
or enabled on the interface.
To disable IPv4 routing, use the no ip routing global configuration command. To disable IPv6 routing,
use the no ipv6 unicast-routing global configuration command. To remove an IPv4 address from an
interface, use the no ip address ip-address mask interface configuration command. To remove an IPv6
address from an interface, use the no ipv6 address ipv6-prefix/prefix length eui-64 or no ipv6 address
ipv6-address link-local interface configuration command. To remove all manually configured IPv6
addresses from an interface, use the no ipv6 address interface configuration command without
arguments. To disable IPv6 processing on an interface that has not been explicitly configured with an
IPv6 address, use the no ipv6 enable interface configuration command.
This example shows how to enable IPv4 and IPv6 routing on an interface.
Switch(config)# sdm prefer dual-ipv4-and-ipv6 default
Switch(config)# ip routing
Switch(config)# ipv6 unicast-routing
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# no switchport
Switch(config-if)# ip address 192.168.99.1 244.244.244.0
Switch(config-if)# ipv6 address 2001:0DB8:c18:1::/64 eui 64
Switch(config-if)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ipv6 dhcp pool poolname Enter DHCP pool configuration mode, and define the name
for the IPv6 DHCP pool. The pool name can be a symbolic
string (such as Engineering) or an integer (such as 0).
Step 3 address prefix IPv6-prefix lifetime {t1 t1 | infinite} (Optional) Specify an address prefix for address assignment.
This address must be in hexadecimal, using 16-bit values
between colons.
lifetime t1 t1—Specify a time interval (in seconds) that an
IPv6 address prefix remains in the valid state. The range is 5
to 4294967295 seconds. Specify infinite for no time interval.
Command Purpose
Step 4 link-address IPv6-prefix (Optional) Specify a link-address IPv6 prefix.
When an address on the incoming interface or a link-address
in the packet matches the specified IPv6 prefix, the server
uses the configuration information pool.
This address must be in hexadecimal, using 16-bit values
between colons.
Step 5 vendor-specific vendor-id (Optional) Enter vendor-specific configuration mode and
enter a vendor-specific identification number. This number is
the vendor IANA Private Enterprise Number. The range is 1
to 4294967295.
Step 6 suboption number {address IPv6-address | ascii (Optional) Enter a vendor-specific suboption number. The
ASCII-string | hex hex-string} range is 1 to 65535. Enter an IPv6 address, ASCII text, or a
hex string as defined by the suboption parameters.
Step 7 exit Return to DHCP pool configuration mode.
Step 8 exit Return to global configuration mode.
Step 9 interface interface-id Enter interface configuration mode, and specify the interface
to configure.
Step 10 ipv6 dhcp server [poolname | automatic] Enable DHCPv6 server function on an interface.
[rapid-commit] [preference value] [allow-hint]
• poolname—(Optional) User-defined name for the IPv6
DHCP pool. The pool name can be a symbolic string
(such as Engineering) or an integer (such as 0).
• automatic—(Optional) Enables the system to
automatically determine which pool to use when
allocating addresses for a client.
• rapid-commit—(Optional) Allow two-message
exchange method.
• preference value—(Optional) The preference value
carried in the preference option in the advertise message
sent by the server. The range is from 0 to 255. The
preference value default is 0.
• allow-hint—(Optional) Specifies whether the server
should consider client suggestions in the SOLICIT
message. By default, the server ignores client hints.
Step 11 end Return to privileged EXEC mode.
Step 12 show ipv6 dhcp pool Verify DHCPv6 pool configuration.
or
show ipv6 dhcp interface Verify that the DHCPv6 server function is enabled on an
interface.
Step 13 copy running-config startup-config (Optional) Save your entries in the configuration file.
To delete a DHCPv6 pool, use the no ipv6 dhcp pool poolname global configuration command. Use the
no form of the DHCP pool configuration mode commands to change the DHCPv6 pool characteristics.
To disable the DHCPv6 server function on an interface, use the no ipv6 dhcp server interface
configuration command.
This example shows how to configure a pool called engineering with an IPv6 address prefix:
Switch# configure terminal
Switch(config)# ipv6 dhcp pool engineering
Switch(config-dhcpv6)#address prefix 2001:1000::0/64
Switch(config-dhcpv6)# end
This example shows how to configure a pool called testgroup with three link-addresses and an IPv6
address prefix:
Switch# configure terminal
Switch(config)# ipv6 dhcp pool testgroup
Switch(config-dhcpv6)# link-address 2001:1001::0/64
Switch(config-dhcpv6)# link-address 2001:1002::0/64
Switch(config-dhcpv6)# link-address 2001:2000::0/48
Switch(config-dhcpv6)# address prefix 2001:1003::0/64
Switch(config-dhcpv6)# end
This example shows how to configure a pool called 350 with vendor-specific options:
Switch# configure terminal
Switch(config)# ipv6 dhcp pool 350
Switch(config-dhcpv6)# address prefix 2001:1005::0/48
Switch(config-dhcpv6)# vendor-specific 9
Switch(config-dhcpv6-vs)# suboption 1 address 1000:235D::1
Switch(config-dhcpv6-vs)# suboption 2 ascii "IP-Phone"
Switch(config-dhcpv6-vs)# end
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and specify the interface
to configure.
Step 3 ipv6 address dhcp [rapid-commit] Enable the interface to acquire an IPv6 address from the
DHCPv6 server.
rapid-commit—(Optional) Allow two-message exchange
method for address assignment.
Step 4 ipv6 dhcp client request [vendor-specific] (Optional) Enable the interface to request the vendor-specific
option.
Step 5 end Return to privileged EXEC mode.
Step 6 show ipv6 dhcp interface Verify that the DHCPv6 client is enabled on an interface.
To disable the DHCPv6 client function, use the no ipv6 address dhcp interface configuration command.
To remove the DHCPv6 client request, use the no ipv6 address dhcp client request interface
configuration command.
This example shows how to acquire an IPv6 address and to enable the rapid-commit option:
Switch(config)# interface gigabitethernet2/0/1
Switch(config-if)# ipv6 address dhcp rapid-commit
This document describes only the DHCPv6 address assignment. For more information about configuring
the DHCPv6 client, server, or relay agent functions, see the “Implementing DHCP for IPv6” chapter in
the Cisco IOS IPv6 Configuration Library on Cisco.com.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ipv6 icmp error-interval interval [bucketsize] Configure the interval and bucket size for IPv6 ICMP error
messages:
• interval—The interval (in milliseconds) between tokens
being added to the bucket. The range is from 0 to
2147483647 milliseconds.
• bucketsize—(Optional) The maximum number of tokens
stored in the bucket. The range is from 1 to 200.
Step 3 end Return to privileged EXEC mode.
Step 4 show ipv6 interface [interface-id] Verify your entries.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To return to the default configuration, use the no ipv6 icmp error-interval global configuration
command.
This example shows how to configure an IPv6 ICMP error message interval of 50 milliseconds and a
bucket size of 20 tokens.
Switch(config)#ipv6 icmp error-interval 50 20
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ipv6 route ipv6-prefix/prefix length Configure a static IPv6 route.
{ipv6-address | interface-id [ipv6-address]}
• ipv6-prefix—The IPv6 network that is the destination of the
[administrative distance]
static route. It can also be a hostname when static host routes are
configured.
• /prefix length—The length of the IPv6 prefix. A decimal value
that shows how many of the high-order contiguous bits of the
address comprise the prefix (the network portion of the address).
A slash mark must precede the decimal value.
• ipv6-address—The IPv6 address of the next hop that can be used
to reach the specified network. The IPv6 address of the next hop
need not be directly connected; recursion is done to find the
IPv6 address of the directly connected next hop. The address
must be specified in hexadecimal using 16-bit values between
colons.
• interface-id—Specify direct static routes from point-to-point
and broadcast interfaces. With point-to-point interfaces, there is
no need to specify the IPv6 address of the next hop. With
broadcast interfaces, you should always specify the IPv6
address of the next hop, or ensure that the specified prefix is
assigned to the link, specifying a link-local address as the next
hop. You can optionally specify the IPv6 address of the next hop
to which packets are sent.
Note You must specify an interface-id when using a link-local
address as the next hop (the link-local next hop must also be
an adjacent router).
Command Purpose
Step 4 show ipv6 static [ipv6-address | Verify your entries by displaying the contents of the IPv6 routing
ipv6-prefix/prefix length] [interface table.
interface-id] [recursive] [detail]
• interface interface-id—(Optional) Display only those static
routes with the specified interface as an egress interface.
or • recursive—(Optional) Display only recursive static routes. The
recursive keyword is mutually exclusive with the interface
keyword, but it can be used with or without the IPv6 prefix
show ipv6 route static [updated] included in the command syntax.
• detail—(Optional) Display this additional information:
– For valid recursive routes, the output path set, and
maximum resolution depth.
– For invalid routes, the reason why the route is not valid.
Step 5 copy running-config startup-config (Optional) Save your entries in the configuration file.
To remove a configured static route, use the no ipv6 route ipv6-prefix/prefix length {ipv6-address |
interface-id [ipv6-address]} [administrative distance] global configuration command.
This example shows how to configure a floating static route with an administrative distance of 130 to an
interface:
Switch(config)# ipv6 route 2001:0DB8::/32 gigabitethernet2/0/1 130
For more information about configuring static IPv6 routing, see the “Implementing Static Routes for
IPv6” chapter in the Cisco IOS IPv6 Configuration Library on Cisco.com.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ipv6 router rip name Configure an IPv6 RIP routing process, and enter router
configuration mode for the process.
Step 3 maximum-paths number-paths (Optional) Define the maximum number of equal-cost routes
that IPv6 RIP can support. The range is from 1 to 64, and the
default is 4 routes.
Step 4 exit Return to global configuration mode.
Step 5 interface interface-id Enter interface configuration mode, and specify the Layer 3
interface to configure.
Step 6 ipv6 rip name enable Enable the specified IPv6 RIP routing process on the interface.
Command Purpose
Step 7 ipv6 rip name default-information {only | (Optional) Originate the IPv6 default route (::/0) into the RIP
originate} routing process updates sent from the specified interface.
Note To avoid routing loops after the IPv6 default route (::/0)
is originated from any interface, the routing process
ignores all default routes received on any interface.
To disable a RIP routing process, use the no ipv6 router rip name global configuration command. To
disable the RIP routing process for an interface, use the no ipv6 rip name interface configuration
command.
This example shows how to enable the RIP routing process cisco with a maximum of eight equal-cost
routes and to enable it on an interface:
Switch(config)# ipv6 router rip cisco
Switch(config-router)# maximum-paths 8
Switch(config)# exit
Switch(config)# interface fastethernet2/0/11
Switch(config-if)# ipv6 rip cisco enable
For more information about configuring RIP routing for IPv6, see the “Implementing RIP for IPv6”
chapter in the Cisco IOS IPv6 Configuration Library on Cisco.com
Beginning in privileged EXEC mode, follow these required and optional steps to configure IPv6 OSPF:
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 ipv6 router ospf process-id Enable OSPF router configuration mode for the process. The
process ID is the number administratively assigned when
enabling the OSPF for IPv6 routing process. It is locally
assigned and can be a positive integer from 1 to 65535.
Step 3 area area-id range {ipv6-prefix/prefix length} (Optional) Consolidate and summarize routes at an area
[advertise | not-advertise] [cost cost] boundary.
• area-id—Identifier of the area about which routes are to be
summarized. It can be specified as either a decimal value or
as an IPv6 prefix.
• ipv6-prefix/prefix length—The destination IPv6 network and
a decimal value that shows how many of the high-order
contiguous bits of the address comprise the prefix (the
network portion of the address). A slash mark (/) must
precede the decimal value.
• advertise—(Optional) Set the address range status to
advertise and to generate a Type 3 summary link-state
advertisement (LSA).
• not-advertise—(Optional) Set the address range status to
DoNotAdvertise. The Type 3 summary LSA is suppressed,
and component networks remain hidden from other
networks.
• cost cost—(Optional) Metric or cost for this summary route,
which is used during OSPF SPF calculation to determine the
shortest paths to the destination. The value can be 0 to
16777215.
Step 4 maximum paths number-paths (Optional) Define the maximum number of equal-cost routes to
the same destination that IPv6 OSPF should enter in the routing
table. The range is from 1 to 64, and the default is 16.
Step 5 exit Return to global configuration mode.
Step 6 interface interface-id Enter interface configuration mode, and specify the Layer 3
interface to configure.
Step 7 ipv6 ospf process-id area area-id [instance Enable OSPF for IPv6 on the interface.
instance-id] instance instance-id—(Optional) Instance identifier.
Step 8 end Return to privileged EXEC mode.
Step 9 show ipv6 ospf [process-id] [area-id] interface Display information about OSPF interfaces.
[interface-id]
or
show ipv6 ospf [process-id] [area-id] Display general information about OSPF routing processes.
Step 10 copy running-config startup-config (Optional) Save your entries in the configuration file.
To disable an OSPF routing process, use the no ipv6 router ospf process-id global configuration
command. To disable the OSPF routing process for an interface, use the no ipv6 ospf process-id area
area-id interface configuration command.
For more information about configuring OSPF routing for IPv6, see the “Implementing OSPF for IPv6”
chapter in the Cisco IOS IPv6 Configuration Library on Cisco.com.
Note If EIGRP for IPv6 is not in shutdown mode, EIGRP might start running before you enter the EIRGP
router-mode commands to configure the router and the interface.
Note Before configuring an HSRP for IPv6 group, you must enable the forwarding of IPv6 packets by using
the ipv6 unicast-routing global configuration command and enable IPv6 on the interface on which you
will configure an HSRP for IPv6 group.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and enter the
Layer 3 interface on which you want to specify the
standby version.
Step 3 standby version {1 | 2} Enter 2 to change the HSRP version. The default is 1.
Step 4 end Return to privileged EXEC mode.
Step 5 show standby Verify the configuration.
Step 6 copy running-config startup-config (Optional) Save your entries in the configuration file.
Command Purpose
Step 1 configure terminal Enter global configuration mode.
Step 2 interface interface-id Enter interface configuration mode, and enter the Layer 3
interface on which you want to enable HSRP for IPv6.
Step 3 standby [group-number] ipv6 {link-local-address Create (or enable) the HSRP for IPv6 group.
| autoconfig}
• (Optional) group-number—The group number on the
interface for which HSRP is being enabled. The range is 0
to 4095. The default is 0. If there is only one HSRP group,
you do not need to enter a group number.
• Enter the link-local address of the Hot Standby router
interface, or enable the link-local address to be generated
automatically from the link-local prefix and a modified
EUI-64 format interface identifier, where the EUI-64
interface identifier is created from the relevant HSRP
virtual MAC address.
Command Purpose
Step 4 standby [group-number] preempt [delay Configure the router to preempt, which means that when the
{minimum seconds | reload seconds | sync local router has a higher priority than the active router, it
seconds}] assumes control as the active router.
• (Optional) group-number—The group number to which the
command applies.
• (Optional) delay—Set to cause the local router to postpone
taking over the active role for the shown number of seconds.
The range is 0 to 3600 (1 hour). The default is 0 (no delay
before taking over).
• (Optional) reload—Set the preemption delay, in seconds,
after a reload. The delay period applies only to the first
interface-up event after the router reloads.
• (Optional) sync—Set the maximum synchronization
period, in seconds, for IP redundancy clients.
Use the no form of the command to restore the default values.
Step 5 standby [group-number] priority priority Set a priority value used in choosing the active router. The
range is 1 to 255; the default priority is 100. The highest number
represents the highest priority.
Use the no form of the command to restore the default values.
Step 6 end Return to privileged EXEC mode.
Step 7 show standby [interface-id [group-number]] Verify the configuration.
Step 8 copy running-config startup-config (Optional) Save your entries in the configuration file.
Use the no standby [group-number] ipv6 interface configuration command to disable HSRP for IPv6.
This example shows how to activate HSRP for IPv6 for group 1 on a port. The IP address used by the
hot standby group is learned by using HSRP for IPv6.
Note This procedure is the minimum number of steps required to enable HSRP for IPv6. Other configurations
are optional.
For more information about configuring HSRP for IPv6, see the “Configuring First Hop Redundancy
Protocols in IPv6” chapter in the Cisco IOS IPv6 Configuration Library on Cisco.com.
Displaying IPv6
For complete syntax and usage information on these commands, see the Cisco IOS command reference
publications.
Table 39-2 shows the privileged EXEC commands for monitoring IPv6 on the switch.
Command Purpose
show ipv6 access-list Display a summary of access lists.
show ipv6 cef Display Cisco Express Forwarding for IPv6.
show ipv6 interface interface-id Display IPv6 interface status and configuration.
show ipv6 mtu Display IPv6 MTU per destination cache.
show ipv6 neighbors Display IPv6 neighbor cache entries.
show ipv6 ospf Display IPv6 OSPF information.
show ipv6 prefix-list Display a list of IPv6 prefix lists.
show ipv6 protocols Display IPv6 routing protocols on the switch.
show ipv6 rip Display IPv6 RIP routing protocol status.
show ipv6 route Display the IPv6 route table entries.
show ipv6 routers Display the local IPv6 routers.
show ipv6 static Display IPv6 static routes.
show ipv6 traffic Display IPv6 traffic statistics.
Table 39-3 shows the privileged EXEC command for displaying EIGRP IPv6 information.
Command Purpose
show ipv6 eigrp [as-number] interface Displays information about interfaces configured for EIGRP IPv6.
show ipv6 eigrp [as-number] neighbor Displays the neighbors discovered by EIGRP IPv6.
show ipv6 eigrp [as-number] traffic Displays the number of EIGRP IPv6 packets sent and received.
show ipv6 eigrp topology [as-number | ipv6-address] Displays EIGRP entries in the IPv6 topology table.
[active | all-links | detail-links | pending | summary |
zero-successors]
Table 39-4 shows the privileged EXEC commands for displaying information about IPv4 and IPv6 address
types.
Table 39-4 Commands for Displaying IPv4 and IPv6 Address Types
Command Purpose
show ip http server history Display the previous 20 connections to the HTTP server, including the IP
address accessed and the time when the connection was closed.
show ip http server connection Display the current connections to the HTTP server, including the local and
remote IP addresses being accessed.
show ip http client connection Display the configuration values for HTTP client connections to HTTP
servers.
show ip http client history Display a list of the last 20 requests made by the HTTP client to the server.
This is an example of the output from the show ipv6 interface privileged EXEC command:
Switch# show ipv6 interface
Vlan1 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::20B:46FF:FE2F:D940
Global unicast address(es):
3FFE:C000:0:1:20B:46FF:FE2F:D940, subnet is 3FFE:C000:0:1::/64 [EUI]
Joined group address(es):
FF02::1
FF02::2
FF02::1:FF2F:D940
MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds
ND advertised reachable time is 0 milliseconds
ND advertised retransmit interval is 0 milliseconds
ND router advertisements are sent every 200 seconds
ND router advertisements live for 1800 seconds
<output truncated>
This is an example of the output from the show ipv6 cef privileged EXEC command:
Switch# show ipv6 cef
::/0
nexthop 3FFE:C000:0:7::777 Vlan7
3FFE:C000:0:1::/64
attached to Vlan1
3FFE:C000:0:1:20B:46FF:FE2F:D940/128
receive
3FFE:C000:0:7::/64
attached to Vlan7
3FFE:C000:0:7::777/128
attached to Vlan7
3FFE:C000:0:7:20B:46FF:FE2F:D97F/128
receive
3FFE:C000:111:1::/64
attached to FastEthernet1/0/11
3FFE:C000:111:1:20B:46FF:FE2F:D945/128
receive
3FFE:C000:168:1::/64
attached to FastEthernet2/0/43
3FFE:C000:168:1:20B:46FF:FE2F:D94B/128
receive
3FFE:C000:16A:1::/64
attached to Loopback10
3FFE:C000:16A:1:20B:46FF:FE2F:D900/128
receive
<output truncated>
This is an example of the output from the show ipv6 protocols privileged EXEC command:
Switch# show ipv6 protocols
IPv6 Routing Protocol is “connected”
IPv6 Routing Protocol is “static”
IPv6 Routing Protocol is “rip fer”
Interfaces:
Vlan6
FastEthernet2/0/4
FastEthernet2/0/11
FastEthernet1/0/12
Redistribution:
None
This is an example of the output from the show ipv6 rip privileged EXEC command:
Switch# show ipv6 rip
RIP process "fer", port 521, multicast-group FF02::9, pid 190
Administrative distance is 120. Maximum paths is 16
Updates every 30 seconds, expire after 180
Holddown lasts 0 seconds, garbage collect after 120
Split horizon is on; poison reverse is off
Default routes are not generated
Periodic updates 9040, trigger updates 60
Interfaces:
Vlan6
FastEthernet2/0/4
FastEthernet2/0/11
FastEthernet1/0/12
Redistribution:
None
This is an example of the output from the show ipv6 static privileged EXEC command:
Switch# show ipv6 static
IPv6 Static routes
Code: * - installed in RIB
* ::/0 via nexthop 3FFE:C000:0:7::777, distance 1
This is an example of the output from the show ipv6 neighbor privileged EXEC command:
Switch# show ipv6 neighbors
IPv6 Address Age Link-layer Addr State Interface
3FFE:C000:0:7::777 - 0007.0007.0007 REACH Vl7
3FFE:C101:113:1::33 - 0000.0000.0033 REACH Fa1/0/13
This is an example of the output from the show ipv6 route privileged EXEC command:
Switch# show ipv6 route
IPv6 Routing Table - Default - 1 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
L FF00::/8 [0/0]
via Null0, receive
This is an example of the output from the show ipv6 traffic privileged EXEC command.
Switch# show ipv6 traffic
IPv6 statistics:
Rcvd: 1 total, 1 local destination
0 source-routed, 0 truncated
0 format errors, 0 hop count exceeded
0 bad header, 0 unknown option, 0 bad source
0 unknown protocol, 0 not a router
0 fragments, 0 total reassembled
0 reassembly timeouts, 0 reassembly failures
Sent: 36861 generated, 0 forwarded
0 fragmented into 0 fragments, 0 failed
0 encapsulation failed, 0 no route, 0 too big
0 RPF drops, 0 RPF suppressed drops
Mcast: 1 received, 36861 sent
ICMP statistics:
Rcvd: 1 input, 0 checksum errors, 0 too short
0 unknown info type, 0 unknown error type
unreach: 0 routing, 0 admin, 0 neighbor, 0 address, 0 port
parameter: 0 error, 0 header, 0 option
0 hopcount expired, 0 reassembly timeout,0 too big
0 echo request, 0 echo reply
UDP statistics:
Rcvd: 0 input, 0 checksum errors, 0 length errors
0 no port, 0 dropped
Sent: 26749 output
TCP statistics:
Rcvd: 0 input, 0 checksum errors
Sent: 0 output, 0 retransmitted