With dual-stack implementations, while some hosts have the capability to use both the IPv4 and the IPv6 protocol stacks, they still require some help in deciding when to use the IPv6 protocol stack instead of the IPv4 protocol stack. Fortunately, this is possible using one of the two methods which are described in the following section.
- The first method requires manual configuration by the user. If the user knows the IPv6 address of the destination IPv6 host, they can manually use that to establish an IPv6 session to that host from their dual-stack host. Although this method works well, it can become quite cumbersome to remember IPv4 and IPv6 addresses for multiple hosts
- The second method entails using a naming service, such as DNS. With this method, the Fully Qualified Domain Names such as www.howtonetwork.org are configured using both IPv4 and IPv6 addresses. The FQDN is represented by an A record for the IPv4 protocol stack and an AAAA record for the IPv6 protocol stack, which allows the DNS server to be queried using either IPv4 or IPv6
Implementing Dual-Stack Support in Cisco IOS Software While delving into the different ways in which different types of hosts by different vendors can support dual-stack implementations is beyond the scope of the ROUTE exam, as a future network engineer, it is imperative to understand how to implement dual-stack solutions in Cisco IOS software. In Cisco IOS routers, dual-stack operation is enabled by simply configuring both an IPv4 address and an IPv6 address on the router interface. Multiple IPv4 addresses can be specified by appending the secondary keyword to the end of the ip address [address] [mask] interface configuration command. For IPv6, however, the secondary keyword is not required as multiple prefixes can be configured per interface using the ipv6 address interface configuration command which was described in detail in the previous chapter. The following configuration example illustrates how to configure multiple IPv4 and IPv6 addresses and prefixes on a single router interface:
| R3(config)#ipv6 unicast-routing R3(config)#interface fastethernet 0/0 R3(config-if)#ip address 10.0.0.1 255.255.255.0 R3(config-if)#ip address 10.0.1.1 255.255.255.0 secondary R3(config-if)#ip address 10.0.2.1 255.255.255.0 secondary R3(config-if)#ipv6 address 3fff:1234:abcd:1::3/64 R3(config-if)#ipv6 address 3fff:1234:abcd:2::3/64 R3(config-if)#ipv6 address 3fff:1234:abcd:3::3/64 R3(config-if)#ipv6 enable R3(config-if)#exit |
NOTE: While IPv4 routing is enabled by default in Cisco IOS software, IPv6 routing is disabled by default and must be explicitly enabled. Following the configuration of the IPv4 and IPv6 addresses, you can simply view the router configuration to validate your configuration as illustrated in the following output:
| R3#show running-config interface fastethernet 0/0 Building configuration…Current configuration : 395 bytes ! interface FastEthernet0/0 ip address 10.0.1.3 255.255.255.0 secondary ip address 10.0.2.3 255.255.255.0 secondary ip address 10.0.0.3 255.255.255.0 ipv6 address 3FFF:1234:ABCD:1::3/64 ipv6 address 3FFF:1234:ABCD:2::3/64 ipv6 address 3FFF:1234:ABCD:3::3/64 ipv6 enable end |
To view specific IPv4 and IPv6 interface parameters, simply use the Cisco IOS software show ip interface [name]or the show ipv6 interface [name] commands. Following is the output of the show ip interface command for the FastEthernet0/0 interface:
| R3#show ip interface fastethernet 0/0 | section address Internet address is 10.0.0.3/24 Broadcast address is 255.255.255.255 Helper address is not set Secondary address 10.0.1.3/24 Secondary address 10.0.2.3/24 Network address translation is disabled |
The following shows the information printed by the show ipv6 interface command for the same FastEthernet0/0 interface used in the previous example:
| R3#show ipv6 interface fastethernet 0/0 | section address IPv6 is enabled, link-local address is FE80::213:19FF:FE86:A20 Global unicast address(es): 3FFF:1234:ABCD:1::3, subnet is 3FFF:1234:ABCD:1::/64 3FFF:1234:ABCD:2::3, subnet is 3FFF:1234:ABCD:2::/64 3FFF:1234:ABCD:3::3, subnet is 3FFF:1234:ABCD:3::/64 Joined group address(es): FF02::1 FF02::2 FF02::5 FF02::6 FF02::9 FF02::1:FF00:3 Hosts use stateless autoconfig for addresses. |
Configuring Static IPv4 and IPv6 Host Addresses in Cisco IOS Software Cisco IOS software supports the configuration of both static IPv4 and IPv6 host addresses using the ip host [name] [v4-address] and ipv6 host [name] [v6-address] global configuration commands respectively. The following example illustrates how to configure static IPv4 and IPv6 host names and address in Cisco IOS software:
| R1(config)#ip host TEST-HOST 10.0.0.3 R1(config)#ipv6 host TEST-HOST 3FFF:1234:ABCD:1::3 |
The static IPv4 and IPv6 host configuration can be validated using the show hosts command, the output of which is printed below:
| R1#show hosts[Truncated Output] Host Port Flags Age Type Address(es) TEST-HOST None (perm, OK) 0 IP 10.0.0.3 TEST-HOST None (perm, OK) 0 IPv6 3FFF:1234:ABCD:1::3 |
When the same host is configured with both a static IPv4 and IPv6 address, Cisco IOS software will use the IPv6 address. If DNS is used, the dual-stack host will first search AAAA (IPv6) records and the fall back to the A records (IPv4) when configured with both IPv6 and IPv4 DNS servers. This default behavior can be validated by performing a simple ping to the previously configured static host ‘TEST-HOST’ as follows:
| R1#ping test-host repeat 10Type escape sequence to abort. Sending 10, 100-byte ICMP Echos to 3FFF:1234:ABCD:1::3, timeout is 2 seconds: !!!!!!!!!! Success rate is 100 percent (10/10), round-trip min/avg/max = 0/1/4 ms |
Configuring IPv4 and IPv6 DNS Servers in Cisco IOS Software The configuration of both IPv4 and IPv6 servers in Cisco IOS still uses the ip name-server [address] global configuration command. This same command has now been modified to allow the DNS server IP address to be specified as either an IPv4 or IPv6 address. The following example illustrates how to configure a router to use both an IPv4 and IPv4 DNS server:
| R1(config)#ip name-server ? A.B.C.D Domain server IP address (maximum of 6) X:X:X:X::X Domain server IP address (maximum of 6) R1(config)#ip name-server 3FFF:1234:ABCD:1::2 R1(config)#ip name-server 192.168.1.2 |
NOTE: As was previously mentioned, when IPv6 and IPv4 DNS servers are configured on the same router, the router look for the AAAA records first (i.e. IPv6). However, if AAAA records are not found, the host looks for an A record to communicate with the hostname. Cisco IOS Software IPv6 Application, Tool and Protocol Support In addition to DNS and the ping utility, Cisco IOS software provides dual-stack support for several applications, tools and protocols, which include, but are not limited to the following:
- Telnet
- SSH
- TFTP
- Traceroute
- HTTP
- Frame Relay
- FHRP
NOTE: While IPv6 support for the applications, protocols and tools that are listed above will be briefly described in the following sections, keep in mind that going into specific detail and configuration requirements is beyond the scope of the current ROUTE exam and will not be described or illustrated in this chapter. Cisco IOS supports Telnet the use of either IPv4 or IPv6 addresses on dual-stack internetwork devices. Thetelnet <address> command is still used to establish a Telnet session from the local router to the specified destination host, with the exception that in current Cisco IOS software versions the specified address can either be an IPv4 address or an IPv6 address. The following example illustrates how to Telnet to an IPv6 device:
| R3#telnet 3fff:1234:abcd:1::1 Trying 3FFF:1234:ABCD:1::1 … Open User Access Verification Password: R1# |
Given that SSH is much more secure than Telnet and should be the preferred method used for the remotely accessing devices, Cisco IOS software supports the use of either IPv4 or IPv6 addresses to establish SSH sessions. The following example illustrates how to SSH from a router to another router as user ROUTE, while using an IPv6 address:
| R1#ssh -l ROUTE 3FFF:1234:ABCD:1::3Password: R3# |
Cisco IOS software also allows users to specify either IPv4 or IPv6 addresses when using the Trivial File Transfer Protocol, which is commonly used to copy configuration or software images to internetwork devices. Support for IPv6 addresses when using Traceroute is also integrated into the current Cisco IOS software versions. When using Traceroute, you can directly specify the IPv6 address using the traceroute <v6-address>command or using the traceroute ipv6 <v6-address> commands. The following is an example of Traceroute using IPv6 addresses:
| R1#traceroute 3FFF:1234:ABCD:4::4Type escape sequence to abort. Tracing the route to 3FFF:1234:ABCD:4::4 1 3FFF:1234:ABCD:1::3 0 msec 0 msec 4 msec 2 3FFF:1234:ABCD:2::2 4 msec 4 msec 4 msec 3 3FFF:1234:ABCD:4::4 8 msec 8 msec 8 msec |
In current versions of Cisco IOS software, internetwork devices accept incoming HTTP sessions over both IPv4 and IPv6. There is no explicit configuration to enable or disable one protocol while using another. Cisco IOS software HTTP server functionality is still enabled using the ip http server global configuration command. Frame Relay, in addition to other Layer 2 protocols, such as PPP and HDLC, also supports the IPv6 protocol. In Cisco IOS software, static Frame Relay maps are configured to use IPv6 addresses via the frame-relay map ipv6 [address] [dlci] interface configuration command. When enabling dynamic IPv6 IGPs over Frame Relay, the Link-Local address should be specified in the static Frame Relay configuration as these are the addresses that are used to establish adjacencies and neighbor relationships, and as the next hop addresses. With MP-BGP, global Unicast addresses should be specified if they are used for peering over Frame Relay. The following example illustrates how to configure a static IPv6 Frame Relay map:
| R2(config)#interface serial 0/0 R2(config-if)#frame-relay map ipv6 FE80::205:5EFF:FE6E:5C80 111 broadcast |
And finally, in later versions of Cisco IOS software, 12.4T and later, IPv6 support has now been extended to First Hop Redundancy Protocols, such as the Hot Standby Router Protocol (HSRP) and the Gateway Load Balancing Protocol (GLBP). HSRP and GLBP are Cisco protocols that are used to allow for a transparent failover of the first hop IP router. NOTE: Keep in mind that the different applications, tools and protocols described in this section are only a subset of the entire suite that is supported in Cisco IOS software.