Implementing Ipv6 in The Enterprise Network: CCNP Route: Implementing Ip Routing

Chapter 8:
Implementing IPv6 in the

Enterprise Network
CCNP ROUTE: Implementing IP Routing
ROUTE v6 Chapter 8
© 2007 – 2013, Cisco Systems, Inc. All rights reserved. Cisco Public 1
Introducing IPv6
Chapter 8
Introducing IPv6
 The ability to scale networks for future demands requires a
limitless supply of IP addresses and improved mobility.
• IPv6 combines expanded addressing with a more efficient and
feature-rich header to meet these demands.
• While it has many similarities to IPv4, IPv6 satisfies the increasingly
complex requirements of hierarchical addressing that IPv4 does not
support.
Chapter 8
The Internet Is Growing …
 In 2009, only 21% of the world population were connected.
• This adoption rate will increase as underdeveloped countries get
connected.
Chapter 8
Explosion of New IP-Enabled Devices
 More and more IP-enabled devices are connecting.
• Devices include cell phones, consumer products (blue ray players,
TVs), etc.
Chapter 8
IP Address Depletion
 All of this growth is causing the Internet to run out of public
IPv4 address.
Chapter 8
IPv4 Issues
 In January 2010, only 10% of the public IPv4 addresses
remained unallocated.
• It is estimated that this pool will have exhausted by the late 2011.
Source: http://www.potaroo.net/tools/ipv4/
Chapter 8
Other IPv4 Issues
 Internet routing table expansion
• The Internet routing tables continue to grow which means Internet
core routers require more processing power, memory, and overhead.
 Lack of true end-to-end model
• IPv4 networks typically use NAT as the solution to address depletion.
• However, NAT hides the true source address of traffic, which can
cause other issues.
Chapter 8
Features of IPv6
 Larger address space
• IPv6 addresses are 128 bits, compared to IPv4’s 32 bits.
• There are enough IPv6 addresses to allocate more than the entire IPv4
Internet address space to everyone on the planet.
 Elimination of public-to-private NAT
• End-to-end communication traceability is possible.
 Elimination of broadcast addresses
• IPv6 now includes unicast, multicast, and anycast addresses.
 Support for mobility and security
• Helps ensure compliance with mobile IP and IPsec standards.
 Simplified header for improved router efficiency
Chapter 8
IPv6 Address Types
Address Type Description Topology
“One to One”
• An address destined for a single interface.
Unicast • A packet sent to a unicast address is delivered to the
interface identified by that address.
“One to Many”
• An address for a set of interfaces (typically belonging
Multicast to different nodes).
• A packet sent to a multicast address will be delivered
to all interfaces identified by that address.
“One to Nearest” (Allocated from Unicast)

• An address for a set of interfaces.
• In most cases these interfaces belong to different
Anycast nodes.
• A packet sent to an anycast address is delivered to
the closest interface as determined by the IGP.
Chapter 8
IPv4 Header vs. IPv6 Header
• The IPv4 header has 20 octets containing • The IPv6 header has 40 octets containing
12 basic header fields. 8 fields.
• Three of these fields are identical in nature.
• Other fields serve similar functions as in IPv4.
• The remaining IPv4 fields no longer exist in IPv6.
Chapter 8
Protocol and Next Header Fields
 In IPv4 the Protocol field is used to identify the next level
protocol (e.g., TCP, UDP, ICMP, …).
 In IPv6, this field is called the "Next Header" field and
serves the same purpose.
Chapter 8
Extension Headers
 The Next Header field
identifies what follows the
Destination Address field:
• Protocols:
• TCP (protocol 6)
• UDP (protocol 17)
• ICMPv6 (protocol 58)
• Extension header
(Optional) Extension Header(s)
 Extension headers make
Data …
the handling of options
more efficient.
Chapter 8
Extension Headers
 Multiple extension headers (called a chain) may be included
in an IPv6 packet.
• The number of extension headers is not fixed, so the total length of the
extension header chain is variable.
 The destination node

examines the first extension
header (if any).
• The contents determine
whether or not the node should
examine the next header.
• Therefore, extension headers
must be processed in the order
they appear in the packet.
Chapter 8
Extension Header Chain Order
Process Next-header value
Extension Header
Order (protocol #)
1 Hop-by-hop options header 0
2 Destination options header 60
3 Routing header 43
4 Fragment header 44
Authentication header (AH) and ESP ESP = 50
5
header AH = 51
Upper-layer header:
TCP = 6
6 TCP
UDP = 17
UDP
Chapter 8
MTU Discovery
 IPv6 routers no longer perform fragmentation.
 A discovery process is used to determine the optimum MTU
to use during a given session.
• In this discovery process, the source IPv6 device attempts to send a
packet at the size that is specified by the upper IP layers, for example,
the transport and application layers.
 If the device receives an Internet Control Message Protocol
(ICMP) “packet too big” message, it retransmits the MTU
discover packet with a smaller MTU; this process is
repeated until the device receives a response that the
discover packet arrived intact.
 The device then sets the MTU for the session.
Chapter 8
New IPv6 Features
 Prefix renumbering
• IPv6 allows simplified mechanisms for address and prefix
renumbering.
 Multiple addresses per interface
• An IPv6 interface can have multiple addresses.
 Link-local addresses
• IPv6 link-local addresses are used as the next hop when IGPs are
exchanging routing updates.
 Stateless autoconfiguration:
• DHCP is not required because an IPv6 device can automatically
assign itself a unique IPv6 link-local address.
 Provider-dependent or provider-independent
addressing
Chapter 8
Is IPv4 Obsolete?
 IPv4 is in no danger of disappearing overnight.
• It will coexist with IPv6 and then gradually be replaced.
 IPv6 provides many transition options including:
• Dual stack:
• Both IPv4 and IPv6 are configured and run simultaneously on the interface.
• IPv6-to-IPv4 (6to4) tunneling and IPv4-compatible tunneling.
• NAT protocol translation (NAT-PT) between IPv6 and IPv4.
Chapter 8
IPv6 Addressing Overview
 IPv6 increases the number of address bits by a factor of 4,
from 32 to 128, providing a very large number of
addressable nodes.
IPv4 = 32 bits
11111111.11111111.11111111.11111111
IPv6 = 128 bits

11111111.11111111.11111111.11111111 11111111.11111111.11111111.11111111 11111111.11111111.11111111.11111111 11111111.11111111.11111111.11111111
Chapter 8
IPv6 Address Allocation Process
 The following displays how IPv6 global unicast addresses
are allocated by the IANA.
• Only a small portion (12.5%) of the IPv6 address space is being
allocated to the Registries in the range of 2001::/16.
Chapter 8
IPv6 Address Specifics
 The 128-bit IPv6 address is written using hexadecimal
numbers.
• Specifically, it consists of 8, 16-bit segments separated with colons
between each set of four hex digits (16 bits).
• Referred to as “coloned hex” format.
• Hex digits are not case sensitive.
• The format is x:x:x:x:x:x:x:x, where x is a 16-bit hexadecimal
field therefore each x is representing four hexadecimal digits.
 An example address is as follows:
• 2035:0001:2BC5:0000:0000:087C:0000:000A
Chapter 8
Abbreviating IPv6 Addresses
 Leading 0s within each set of four hexadecimal digits can
be omitted.
• 09C0 = 9C0
• 0000 = 0
 A pair of colons (“::”) can be used, once within an address,
to represent any number (“a bunch”) of successive 0s.
Chapter 8
IPv6 Address Example
2031:0000:130F:0000:0000:09C0:876A:130B
2031:0000:130F:0000:0000:09C0:876A:130B
2031: 0:130F: 0: 0: 9C0:876A:130B
2031:0:130F:0:0:9C0:876A:130B
2031:0:130F::9C0:876A:130B
Chapter 8
IPv6 Address Example
FF01:0000:0000:0000:0000:0000:0000:1
FF01:0:0:0:0:0:0:1 = FF01::1
E3D7:0000:0000:0000:51F4:00C8:C0A8:6420
= E3D7::51F4:C8:C0A8:6420
3FFE:0501:0008:0000:0260:97FF:FE40:EFAB
= 3FFE:501:8:0:260:97FF:FE40:EFAB
= 3FFE:501:8::260:97FF:FE40:EFAB
Chapter 8
IPv6 Addressing in an Enterprise Network
 An IPv6 address consists of two parts:
• A subnet prefix representing the network to which the interface is
connected.
• Usually 64-bits in length.
• An interface ID, sometimes called a local identifier or a token.
• Usually 64-bits in length.
IPv6 = 128 bits

11111111.11111111.11111111.11111111 11111111.11111111.11111111.11111111 11111111.11111111.11111111.11111111 11111111.11111111.11111111.11111111
Subnet prefix Interface ID
Chapter 8
Subnet Prefix
 IPv6 uses the “/prefix-length” CIDR notation to denote
how many bits in the IPv6 address represent the subnet.
 The syntax is ipv6-address/prefix-length
• ipv6-address is the 128-bit IPv6 address
• /prefix-length is a decimal value representing how many of the
left most contiguous bits of the address comprise the prefix.
For example:
fec0:0:0:1::1234/64
is really
fec0:0000:0000:0001:0000:0000:0000:1234/64
• The first 64-bits (fec0:0000:0000:0001) forms the address prefix.
• The last 64-bits (0000:0000:0000:1234) forms the Interface ID.
Chapter 8
Subnet Prefix
 The prefix length is almost always /64.
• However, IPv6 rules allow for either shorter or longer prefixes
• Although prefixes shorter than /64 can be assigned to a device (e.g., /
60), it is considered bad practice and has no real application.
 Deploying a /64 IPv6 prefix on a device:
• Is pre-subscribed by RFC3177 (IAB/IESG Recommendations on IPv6
Address Allocations to Sites)
• Allows Stateless Address Auto Configuration (SLAAC) (RFC 2462)
Chapter 8
Interface Identifiers
 IPv6 addresses on a link must be unique.
• Although they all share the same 64-bit subnet prefix they are made
unique by the interface ID.
 Because the prefix length is fixed and well-known (64-bits),
IPv6 hosts can automatically create a unique IPv6 address.
 For example, the following Layer 2 protocols can
dynamically create the IPv6 address interface ID:
• Ethernet (using the EUI-64 format discussed later)
• PPP
• HDLC
• NBMA, Frame Relay
Chapter 8
Special IPv6 Addresses
IPv6 Address Description
• All routes and used when specifying a default static
::/0 route.
• It is equivalent to the IPv4 quad-zero (0.0.0.0).
• Unspecified address and is initially assigned to a host
::/128
when it first resolves its local link address.
• Loopback address of local host.
::1/128
• Equivalent to 127.0.0.1 in IPv4.
• Link-local unicast address.
FE80::/10 • Similar to the Windows autoconfiguration IP address of
169.254.x.x.
FF00::/8 • Multicast addresses.
2000::/3 • Global unicast address.
Chapter 8
IPv6 Address Scopes
 Address types have well-defined destination scopes:
• Link-local address
• Global unicast address
• Site-local address
Global Site-Local Link-Local

(Internet)
 Note:
• Site-Local Address are deprecated in RFC 3879.
Chapter 8
Site-Local Addresses - Deprecated
 Site-local addresses allowed devices in the same
organization, or site, to exchange data.
• Site-local addresses start with the prefix FEC0::/10.
 They are analogous to IPv4's private address classes.
• However, using them would also mean that NAT would be required
and addresses would again not be end-to-end.
 Site-local addresses are no longer supported (deprecated)
by RFC 3879.
Chapter 8
Multiple IP Addresses per Interface
 An interface can have multiple IPv6 addresses
simultaneously configured and enabled on it.
• However, it must have a link-local address.
 Typically, an interface is assigned a link-local and one (or
more) global IPv6 address.
• For example, an Ethernet interface can have:
• Link-local address (e.g., FE80::21B:D5FF:FE5B:A408)
• Global unicast address (e.g., 2001:8:85A3:4289:21B:D5FF:FE5B:A408)
 Note:
• An interface could also be configured to simultaneously support IPv4
and IPv6 addresses.
• This creates a “dual-stacked” interface which is discussed later.
Chapter 8
IPv6 Link-Local Address
 Link-local addresses are used for automatic address
configuration, neighbor discovery, router discovery, and by
many routing protocols.
 They are dynamically created using a link-local prefix of
FE80::/10 and a 64-bit interface identifier.
• Unique only on the link, and it is not routable off the link.
128 bits
/10 /64
FE80 Interface ID
1111 1110 1000 0000 0000 0000 ... 0000 0000 0000
FE80::/10
FE8 ou FE9 ou FEA ou FEB
Chapter 8
 Link-local packets are unique only on the link, and are not
routable off the link.
• Packets with a link-local destination must stay on the link where they
have been generated.
• Routers that could forward them to other links are not allowed to do
so because there has been no verification of uniqueness outside the
context of the origin link.
128 bits
/10 /64
FE80 Interface ID
1111 1110 1000 0000 0000 0000 ... 0000 0000 0000
FE80::/10
Chapter 8
 When communicating with a link-local address, the outgoing
interface must be specified because every interface is
connected to FE80::/10.
• For example, if you ping the neighbor’s link-local address, you will be
asked to input the interface from which you wish to ping.
128 bits
/10 /64
FE80 Interface ID
1111 1110 1000 0000 0000 0000 ... 0000 0000 0000
FE80::/10
Chapter 8
IPv6 Link-Local Address Example
R1# show ipv6 interface loopback 100
Loopback100 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::222:55FF:FE18:7DE8
No Virtual link-local address(es):
Global unicast address(es):
2001:8:85A3:4290:222:55FF:FE18:7DE8, subnet is 2001:8:85A3:4290::/64 [EUI]
Joined group address(es):
FF02::1
FF02::2
FF02::1:FF18:7DE8
MTU is 1514 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
ICMP unreachables are sent
ND DAD is not supported
ND reachable time is 30000 milliseconds (using 31238)
Hosts use stateless autoconfig for addresses.
R1#
Chapter 8
IPv6 Global Unicast Address
 A global unicast address is an IPv6 address from the global
public unicast prefix (2001::/16).
• The structure enables aggregation of routing prefixes to reduce the
number of routing table entries in the global routing table.
 Global unicast addresses are aggregated upward through
organizations and eventually to the ISPs.
Chapter 8
 The global unicast address typically consists of:
• A 48-bit global routing prefix
• A 16-bit subnet ID
• A 64-bit interface ID (typically in EUI-64 bit format discussed later).
Subnet
Global Routing Prefix ID Interface ID
/23 /32 /48 /64
2001 0008 21B:D5FF:FE5B:A408

0010
Registry
ISP Prefix
Site Prefix 2000::/3
Subnet Prefix 0010 = 2
0011 = 3
Chapter 8
 The current IANA global routing prefix uses the range that
start with binary 0010 (2000::/3).
• Addresses with a prefix of 2000::/3 (001) to E000::/3 (111)
are required to have 64-bit interface IDs in the extended universal
identifier (EUI)-64 format.
Subnet
/23 /32 /48 /64
2001 0008 21B:D5FF:FE5B:A408

0010
Registry
ISP Prefix
Site Prefix
Subnet Prefix
Chapter 8
 The subnet ID can be used by an organization to create
their own local addressing hierarchy.
• This 16-bit field allows up to 65,536 individual subnets.
Subnet
/23 /32 /48 /64
2001 0008 21B:D5FF:FE5B:A408

0010
Registry
ISP Prefix
Site Prefix
Subnet Prefix
Chapter 8
IPv6 Global Unicast Address Example
FF02::1
FF02::2
FF02::1:FF18:7DE8
MTU is 1514 bytes
R1#
Chapter 8
IPv6 Multicast Address
 Multicasting is at the core of many IPv6 functions and it is a
replacement for the broadcast address.
 They are defined by the prefix FF00::/8.
• An interface may belong to any number of multicast groups.
128 bits
/8 /16
F F 0 0 Group ID
1111 1111 00xx xxxx
FF00::/8
Chapter 8
 The second octet of the address contains the prefix and
transient (lifetime) flags, and the scope of the multicast
address.
128 bits
/8 /16
F F 0 0 Group ID
1111 1111 00xx xxxx
Flags:
• P = Prefix for unicast-based assignments
Flags Scope • T = 0 if permanent, 1 if temporary
0 0 P T xxxx Scope:
• 1 (0001) = Node
8 bits • 2 (0010) = Link
• 5 (0101) = Site
• 8 (1000) = Organization
• E (1110) = Global
Chapter 8
 The multicast addresses FF00:: to FF0F:: have the T
flag set to 0 and are therefore permanent and reserved.
 For example:
• A multicast address starting with FF02::/16 is a permanent address.
128 bits
/8 /16
F F 0 0 Group ID
1111 1111 00xx xxxx
Flags:
• P = Prefix for unicast-based assignments
Flags Scope • T = 0 if permanent, 1 if temporary
0 0 P T xxxx Scope:
• 1 (0001) = Node
8 bits • 2 (0010) = Link
• 5 (0101) = Site
• 8 (1000) = Organization
• E (1110) = Global
Chapter 8
Reserved IPv6 Multicast Addresses
Reserved Multicast
Description
Address
FF02::1 • All nodes on a link (link-local scope).
FF02::2 • All routers on a link.
• All routing information protocol (RIP) routers on a
FF02::9
link.
• All solicited-node multicast addresses used for
host autoconfiguration and neighbor discovery
(similar to ARP in IPv4).
FF02::1:FFxx:xxxx
• The xx:xxxx is the far right 24 bits of the
corresponding unicast or anycast address of the
node.
FF05::101 • All Network Time Protocol (NTP) servers.
Chapter 8
IPv6 Multicast Address Example
FF02::1
FF02::2
FF02::1:FF18:7DE8
MTU is 1514 bytes
R1#
Chapter 8
Solicited-Node Multicast Addresses
 The solicited-node multicast address (FF02::1:FF) is used
for:
• Neighbor discovery (ND) process
• Stateless address autoconfiguration
 The Neighbor discovery (ND) process is used to:
• Determine the local-link address of the neighbor.
• Determine the routers on the link and default route.
• Actively keep track of neighbor reachability.
• Send network information from routers to hosts
Chapter 8
Neighbor Discovery ICMPv6 Packet Types
 Neighbor Discovery uses four ICMPv6 packet types:
• Neighbor Solicitation and Neighbor Advertisement messages
• Router Solicitation and Router Advertisement messages
ICMPv6 Message Type Description
• Sent by a host to determine the link-layer address of a neighbor.
Neighbor 135 • Used to verify that a neighbor is still reachable.
Solicitation (NS) • An NS is also used for Duplicate Address Detection (DAD).
• A response to a NS message.
Neighbor 136 • A node may also send unsolicited NA to announce a link-layer
Advertisement (NA)
address change.
• RAs contain prefixes that are used for on-link determination or
address configuration, a suggested hop limit value, MTU value,
Router 134 etc.
Advertisement (RA) • RAs are sent either periodically, or in response to a RS
message.
• When a host is booting it send s out an RS requesting routers
Router Solicitation 133 to immediately generate an RA rather than wait for their next
(RS)
scheduled time.
Chapter 8
Neighbor Solicitation Example
A B
ICMP type: 135 (NS)

Source: A
Destination: Solicited-node multicast of B (FF02::1:FFxx.xxxx)
Data: Link-layer address of A
Query:What is your link address?
 ICMPv6 Neighbor Solicitation (NS) is similar to IPv4 ARP in that

it is used when resolving an IPv6 address to a MAC address.
 For example, Host A needs to send a packet to Host B but
needs the MAC address of host B.
• Host A sends a Neighbor Solicitation (ICMPv6 message type 135) on the
link.
• The source address is the IPv6 address of the source node.
Chapter 8
Neighbor Advertisement Example
A B
ICMP type: 136 (NA)

Source: B
Destination: A
Data: Link-layer address of B
 Each destination node that receives the NS responds with an ICMPv6

message type 136, NA.
 The source address of this message is the IPv6 address of the
responding node, and the destination address is the IPv6 address of the
original source node (which sent the NS).
 The data portion includes the link-layer address of the destination node
(even though the link-layer address is of course also included in the
frame).
Chapter 8
Solicited-Node Multicast Addresses
A B
A and B can now exchange packets on this link.
 The two devices can now communicate on the link because

they know each other’s link-layer addresses.
Chapter 8
Solicited-Node Multicast Address Example
2001:DB8::500:AAAA:BBBB
R2
2001:DB8::500:1234:5678
R1
R3
 What would happen if R1 wanted to exchange packets with R2?

 In this case R2 and R3 would have the same solicited-node multicast
address of FF02::1:FFAA:BBBB.
• Recall that a solicited-node address is FF02::1:FFxx.xxxx where the
xx:xxxx is the far right 24 bits of the corresponding unicast or anycast
address of the node.
Chapter 8
R2
2001:DB8::500:1234:5678
R1
R3
 When R1 desires to exchange packets with R2, R1 sends an NS

message to the solicited-node multicast address of R2,
(FF02::1:FFAA:BBBB).
 Along with other data, the NS message contains the “target address”
which is the full IPv6 address that R1 is looking for
(2001:DB8::500:AAAA:BBBB).
Chapter 8
R2
2001:DB8::500:1234:5678
R1
R3
 Both R2 and R3 are listening to the same solicited-node multicast

address (FF02::1:FFAA:BBBB)., so they both receive and process the
packet.
• R2 sees that the target address inside the packet is its own and responds with
a neighbor advertisement (NA) that includes its MAC address.
• R3 sees that the target address inside the packet is not its own and does not
respond.
Chapter 8
Stateless Autoconfiguration
A
R1
ICMP type: 133 (RS)

Source: ::
Destination: All routers multicast address (FF02::2)
Query:Please send RA
 Every IPv6 system (other than routers) is able to build its own unicast
global address.
• Enables new devices (e.g., cellular phones, wireless devices, home
appliances, and home networks) to easily connect to the Internet.
 Stateless autoconfiguration uses the information in RA messages to
configure hosts automatically.
 RAs are sent periodically, but a node can send out RS messages when it
boots so that it doesn’t have to wait for the next RA.
Chapter 8
A
R1
ICMP type: 134 (RA)

Source: R1 link-local address
Destination: All nodes multicast address (FF02::1)
Data: Options, prefixes, lifetime, …
 All routers on the network reply to the RS immediately, with an RA sent

to the all-nodes multicast address.
• The prefix included in the RA is used as the /64 prefix for the host address.
• The interface ID used is the EUI-64 format interface ID.
Chapter 8
A B
ICMP type: 135 (NS)

Source: ::
Destination: Solicited-node address of A
Data: Link-layer address of A
Query:What is your link-layer address?
 The host now creates a link-local address and solicited-node address using the
RA supplied by the router.
 Next it needs to verify that it’s new IPv6 address is unique on the link using the
Duplicate Address Detection (DAD) process.
• DAD is used during the autoconfiguration process to ensure that no other device is
using the autoconfiguration address.
 During the DAD phase, Host A sends an NS to query if another node on the link
has the same IPv6 address.
• If a node responds to the request, it means that the IPv6 address is already in use, and
Host A needs to be manually configured.
Chapter 8
Configuring and
Verifying IPv6
Unicast
Addresses
Chapter 8
Verifying IPv6
Command Description
Displays the status of interfaces configured for IPv6.

show ipv6 interface • The brief keyword displays a brief summary.
[brief] [type number] • The prefix keyword displays the IPv6 neighbor
[prefix] discovery prefixes that are configured on a specified
interface.
Displays IPv6 router advertisement information received
show ipv6 routers from on-link routers (those locally reachable on the link).
[interface-type • The conflicts keyword displays information about
interface-number] routers advertising parameters that differ from the
[conflicts] advertisement parameters configured for the specified
interface on which the advertisements are received.
show ipv6 neighbors Displays IPv6 neighbor discovery cache information for
[interface-type the specified neighbors.
interface-number | ipv6-
address | ipv6-hostname • The optional statistics parameter displays
| statistics] neighbor discovery cache statistics.
Chapter 8
Troubleshooting IPv6
Command Description
Displays messages associated with ICMPv6 neighbor

discovery.
debug ipv6 nd
• ICMPv6 neighbor discovery is the IPv6 replacement for
the IPv4 ARP.
Displays information associated with IPv6 packet

processing.
debug ipv6 packet
[access-list access- • When an IPv6 access list is specified, only packets
list-name] [detail] permitted by the ACL are displayed.
• The detail keyword displays more information.
Chapter 8
Enable IPv6 Routing
 Enable the forwarding of IPv6 unicast datagrams.
Router(config)#
ipv6 unicast-routing
 Command is only required before configuring an IPv6

routing protocol.
• Command is not needed before configuring IPv6 interface addresses.
• It is also required for the interface to provide stateless auto-
configuration.
 Configuring no ipv6 unicast-routing disables the
IPv6 routing capabilities of the router and the router acts as
an IPv6 end-station.
Chapter 8
Enable CEF for IPv6
 Enable Cisco Express Forwarding (CEF) for IPv6 (CEFv6).
Router(config)#
ipv6 cef
 An optional command, CEFv6 is an advanced Layer 3 IP

switching technology for the forwarding of IPv6 packets.
• It is required for some other IPv6 features to operate.
• When enabled, network entries in the IPv6 routing table are reflected
in the Forwarding Information Bases (FIBs).
• The IPv6 adjacency tables maintain Layer 2 next-hop addresses for
all entries that are in each FIB.
Chapter 8
Configuring IPv6 Unicast Addresses
IPv6 Unicast
Address Assignment
Link-local (FE80::/10) Global Routable

Address Assignment Address Assignment
Static Dynamic Static Dynamic
Automatically created
(EUI-64 format) if a Stateless
IPv6 Address global unicast IPv6 IPv6 Address
Autoconfiguration
address is configured
IPv6 Unnumbered DHCPv6
Chapter 8
IPv6 Unicast
Address Assignment

IPv6 Address IPv6 Address
global unicast IPv6 Autoconfiguration
Chapter 8
Enable IPv6 on an Interface
 Configure an IPv6 address and prefix.
Router(config-if)#
ipv6 address address/prefix-length [link-local | eui-64]
 Command is used to statically configure an IPv6 address and prefix on

an interface.
• This enables IPv6 processing on the interface.
 The link-local parameter configures the address as the link-local
address on the interface.
 The eui-64 parameter completes a global IPv6 address using an
EUI-64 format interface ID.
Chapter 8
Assigning a Link-Local Address
.2
R1 R2
R1(config)# interface fa0/0

R1(config-if)# ipv6 address FE80::1 ?
link-local use link-local address
R1(config-if)# ipv6 address FE80::1 link-local
R1(config-if)# end
R1#
 Link-local addresses are created:

• Automatically using the EUI-64 format if the interface has IPv6 enabled on it
or a global IPv6 address configured.
• Manually configured interface ID.
• Manually configured interface IDs are easier to remember than EUI -64 generated IDs.
 Notice that the prefix mask is not required on link-local addresses
because they are not routed.
Chapter 8
Assigning a Static Link-Local Address
FE80::1 .2
R1 R2
R1# show ipv6 interface fa0/0

FastEthernet0/0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::1 [TEN]
No global unicast address is configured
FF02::1
FF02::2
FF02::1:FF00:1
MTU is 1500 bytes
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
R1(config-if)#
 The output confirms the link-local address.
Chapter 8
Assigning a Static Global Unicast Address
FE80::1 .2
R1 R2
R1(config)# ipv6 unicast-routing

R1(config-if)# ipv6 address 2001:1::1/64
R1(config-if)#
 Global Unicast IPv6 addresses are assigned by omitting the link-

local parameter.
 For example, IPv6 address 2001:1::1/64 is configured on R1’s Fast
Ethernet 0/0.
• Notice that the entire address is manually configured and that the EUI-64
format was not used.
Chapter 8
FE80::1 .2
R1 R2
R1# config t
R1(config)# int fa0/1
R1(config-if)# ipv6 add 2001::/64 eui-64
R1(config-if)# do show ipv6 interface fa0/1
FastEthernet0/1 is administratively down, line protocol is down
IPv6 is enabled, link-local address is FE80::211:92FF:FE54:E2A1 [TEN]
2001::211:92FF:FE54:E2A1, subnet is 2001::/64 [EUI/TEN]
FF02::1
FF02::2
FF02::1:FF54:E2A1
MTU is 1500 bytes
<output omitted>
 Notice that by simply configuring a global unicast IPv6 address on an

interface also automatically generates a link-local interface (EUI-64)
interface.
Chapter 8
FE80::1
2001:1::1/64 .2
R1 R2

FastEthernet0/0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::1 [TEN]
2001:1::1, subnet is 2001:1::/64 [TEN]
FF02::1
FF02::2
FF02::1:FF00:1
MTU is 1500 bytes
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
R1#
Chapter 8
Assigning Multiple IPv6 Addresses
FE80::1
2001:1::1/64 .2
R1 R2

R1(config-if)# ip address 10.20.20.1 255.255.255.0
R1(config-if)# ip address 10.10.10.1 255.255.255.0
R1(config-if)# end
R1#
 What would happen if we configured 2 different IPv4 addresses and 2

different IPv6 addresses on the same interface?
Chapter 8
Assigning Multiple IPv6 Addresses
10.10.10.1/24
FE80::1
2001:1::1/64
2001:2::1/64 .2
R1 R2
R1# show run interface fa0/0

Building configuration...
Current configuration : 162 bytes
!
interface FastEthernet0/0
ip address 10.10.10.1 255.255.255.0
duplex auto
speed auto
ipv6 address 2001:1::1/64
ipv6 address 2002:1::1/64
ipv6 address FE80::1 link-local
end
R1#
 The second IPv4 entry replaced the first entry.

• However, both IPv6 addresses have been assigned to the Fa0/0 interface.
 Interfaces can have multiple IPv6 addresses assigned to them.
• These addresses can be used simultaneously.
Chapter 8
Ethernet EUI-64 Address
 EUI-64 IPv6 addresses are addresses where the first 64
bits are the network portion of the address and specified,
and the interface ID (second 64-bits) are the host portion of
the address and automatically generated by the router.
 The interface ID on an Ethernet link is based on the 48-bit
MAC address of the interface with an additional 16-bit
0xFFFE inserted in the middle of the MAC address.
• This creates an extended unique identifier referred to as the EUI-64
format.
• The seventh bit in the high-order byte is set to 1 to indicate the
uniqueness of the interface ID.
Chapter 8
EUI-64 to IPv6 Interface Identifier
 The EUI-64 standard explains how it inserts a 16-bit
0xFFFE in the middle at the 24th bit of the MAC address to
create a unique 64-bit interface identifier.
Chapter 8
Configuring an EUI-64 IPv6 Address
R1(config)# interface loopback 100
R1(config-if)# ipv6 address 2001:8:85a3:4289::/64 eui-64
<output omitted>

IPv6 is enabled, link-local address is FE80::21B:D5FF:FE5B:A408
2001:8:85A3:4289:21B:D5FF:FE5B:A408, subnet is 2001:8:85A3:4289::/64 [EUI]
FF02::1
FF02::2
FF02::1:FF5B:A408
MTU is 1514 bytes
Chapter 8
IPv6 Unicast
Address Assignment

Chapter 8
Enable IP Unnumbered
 Enable IPv6 on an interface without an explicit IPv6 address.
Router(config-if)#
ipv6 unnumbered interface-type interface-number
 Enables IPv6 processing on an interface without assigning an explicit

IPv6 address to the interface.
 The unnumbered interface will use the IPv6 address of the interface
specified by the interface-type interface-number
parameters as the source address of traffic from the configured
interface.
• The interface specified in the command must be in the “up” state.
Chapter 8
Assigning IPv6 Unnumbered Interfaces
Lo10: 2001:1::10/64
S0/0/0
R1 R2
R1(config)# interface loopback 10

R1(config-if)# exit
R1(config)#
R1(config)# interface s0/0/0
R1(config-if)# ipv6 unnumbered loopback 10
R1(config-if)# no shut
R1(config-if)#
 IPv6 supports unnumbered interfaces to enable IPv6 processing on an

interface without assigning an explicit IPv6 address to the interface.
 In this example, a loopback interface is created and configured with an
IPv6 address.
• The Serial 0/0/0 interface is then configured to use the IPv6 address of the
loopback interface.
Chapter 8
Assigning IPv6 Unnumbered Interfaces
Lo10: 2001:1::10/64
S0/0/0
R1 R2
R1# show ipv6 interface s0/0/0

Serial0/0/0 is up, line protocol is up
Interface is unnumbered. Using address of Loopback10
No global unicast address is configured
FF02::1
FF02::2
FF02::1:FF18:7DE8
MTU is 1500 bytes
R1#
 The output confirms that the Serial 0/0/0 interface uses the IPv6
address from interface loopback 10.
Chapter 8
IPv6 Unicast
Address Assignment

Chapter 8
Enable Stateless Autoconfiguration
 Enable the automatic configuration of IPv6 addresses.
Router(config-if)#
ipv6 address autoconfig [default]
 Enables stateless autoconfiguration which:

• Automatically configures IPv6 addresses using the interface.
• Enables the IPv6 processing on the interface.
 Addresses are configured depending on the prefixes
received in RA messages.
 (Optional) If the default keyword router is used it causes
a default route to be installed using that default router.
• The keyword can be specified only on one interface.
Chapter 8
Routing IPv6
Traffic
Chapter 8
Configuring Static
Routing
Chapter 8
Static Routing
 Configured in the same way as IPv4.
 There is an IPv6-specific requirement per RFC 2461.
• A router must be able to determine the link-local address of each of its
neighboring routers to ensure that the target address of a redirect
message identifies the neighbor router by its link-local address.
• This requirement basically means that using a global unicast address
as a next-hop address with routing is not recommended.
Chapter 8
Static Routing
 Configure an IPv6 static route.
Router(config)#
ipv6 route ipv6-prefix/prefix-length {ipv6-address |

interface-type interface-number [ipv6-address]}
[administrative-distance] [administrative-multicast-distance
| unicast | multicast] [next-hop-address] [tag tag]
Chapter 8
ipv6 route Command Parameters
Parameter Description
ipv6-prefix/prefix- The IPv6 network that is the destination of the static route, and its prefix
length length.
ipv6-address The IPv6 address of the next hop that can be used to reach the
specified network.
interface-type Specifies interface through which the destination network can be
interface-number reached.
administrative- Administrative distance; the default value is 1, which gives static routes
distance precedence over any other type of route except connected routes.
administrative- The distance used when selecting this route for multicast Reverse Path
multicast-distance Forwarding (RPF).
unicast Specifies a route that must not be used in multicast RPF selection.
multicast Specifies a route that must not be populated in the unicast RIB.
next-hop-address Address of the next hop that can be used to reach the specified network.
tag tag Tag value that can be used as a “match” value for controlling
redistribution via route maps.
Chapter 8
Types of Static Routes
 Directly attached IPv6 static route:
• Created using only the outgoing interface.
• The specified interface must be up and have IPv6 enabled.
• For example, to specify that 2001:CC1E::/32 is reachable via the
Serial 0/0/0 interface:
• ipv6 route 2001:CC1E::/32 serial 0/0/0
 Recursive static route:
• Created using only the next-hop address parameter.
• The router must refer to its routing table a second time to determine
the interface to use to reach the next-hop address.
• For example, to specify that 2001:CC1E::/32 is reachable via the
neighbor with address 2001:12::1:
• ipv6 route 2001:CC1E::/32 2001:12::1
Chapter 8
Types of Static Routes
 Fully specified static route:
• Includes both the outgoing interface and the next hop address.
• Used on multiaccess interfaces (Ethernet) with multiple devices.
• For example, the command to specify that 2001:CC1E::/32 is
reachable out interface Fa0/0 to the neighbor at 2001:12::1 is:
ipv6 route 2001:CC1E::/32 serial 0/0/0 2001:12::1
 Floating static route:

• The route is set with the administrative distance value higher than the
administrative distance of any IGP to reach a particular destination.
• The static route functions as a backup to IGP discovered routes.
• It will only be added to the routing table if the IGP entry is deleted.
Chapter 8
Static Route Example
2001:1::1/64 2001:1::2/64
Lo100: 10::10:1/64 Lo102: 13::13:1/64
R1 S0/1/0 R2
S0/1/0
Lo101: 11::11:1/64
 In this example topology, assume that R1 is the central site router and
R2 is a branch site router.
 A static route to the 13::13:1/64 network must be configured on R1.
 As well, a default static route will be configured on R2 to reach all other
networks.
Chapter 8
2001:1::1/64 2001:1::2/64
Lo100: 10::10:1/64 Lo102: 13::13:1/64
R1 S0/1/0 R2
S0/1/0
Lo101: 11::11:1/64

R1(config)# ipv6 route 13::/64 s0/1/0
R1(config)# exit
R1# show ipv6 route static
IPv6 Routing Table – 9 entries
Codes: C – Connected, L – Local, S – Static, R – RIP, B – BGP
U – Per-user Static route
I1 – ISIS L1, I2 – ISIS L2, IA – ISIS interarea, IS – ISIS summary
O – OSPF intra, OI – OSPF inter, OE1 – OSPF ext 1, OE2 – OSPF ext 2
ON1 – OSPF NSSA ext 1, ON2 – OSPF NSSA ext 2
S 13::/64 [1/0]
via ::, Serial0/1/0
R1#
 A static route to the 13::13:1/64 network is configured on central site

router R1.
Chapter 8
2001:1::1/64 2001:1::2/64
Lo100: 10::10:1/64 Lo102: 13::13:1/64
R1 S0/1/0 R2
S0/1/0
Lo101: 11::11:1/64

R2(config)# ipv6 route ::/0 s0/1/0
R2(config)# exit
R2# show ipv6 route static
IPv6 Routing Table – 9 entries
Codes: C – Connected, L – Local, S – Static, R – RIP, B – BGP
U – Per-user Static route
I1 – ISIS L1, I2 – ISIS L2, IA – ISIS interarea, IS – ISIS summary
O – OSPF intra, OI – OSPF inter, OE1 – OSPF ext 1, OE2 – OSPF ext 2
ON1 – OSPF NSSA ext 1, ON2 – OSPF NSSA ext 2
S ::/0 [1/0]
via ::, Serial0/1/0
R2#
 A default static route as specified by the “::/0” entry, is now configured

on branch office router R2 to reach all other networks.
Chapter 8
2001:1::1/64 2001:1::2/64
Lo100: 10::10:1/64 Lo102: 13::13:1/64
R1 S0/1/0 R2
S0/1/0
Lo101: 11::11:1/64
R1# ping 13::13:1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 13::13:1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/13/16 ms
R1#
R2# ping 10::10:1

!!!!!
R2#
R2# ping 11::11:1
!!!!!
R2#
Chapter 8
RIPng
 Routing Information Protocol next generation (RIPng, RFC
2080) is a distance vector routing protocol for IPv6.
• It’s based on IPv4 RIP version 2 (RIPv2).
 It is similar to RIPv2 because:
• The hop limit is still 15.
• The administrative distance is still 120.
• It still uses split horizon and poison reverse to prevent routing loops.
 Unlike RIPv2, RIPng is:
• Used to transport IPv6 networks and prefixes.
• It uses an IPv6 prefix and a next-hop IPv6 address.
• Uses UDP port 520 (instead of UDP port 521).
• Uses the multicast group FF02::9 (instead of 224.0.0.9).
Chapter 8
Enable RIPng on an Interface
 Enable an IPv6 RIP process on an interface.
Router(config-if)#
ipv6 rip name enable
 The name parameter is the name of the RIPng routing process.

 If the RIPng routing process does not already exist, the
command will create it.
R1(config)# int fa0/0
R1(config-if)# ipv6 rip ?
WORD User selected string identifying this RIP process
R1(config-if)# ipv6 rip RIP ?

default-information Configure handling of default route
enable Enable/disable RIP routing
metric-offset Adjust default metric increment
summary-address Configure address summarization
R1(config-if)# ipv6 rip RIP enable

R1(config-if)#
Chapter 8
Enable RIPng
 Configure the IPv6 RIP routing process.
Router(config)#
ipv6 router rip name
 The name parameter is the name of the RIP routing process.

 Command enters router configuration mode.
R1(config)# ipv6 router rip RIP
R1(config-rtr)#?
default Set a command to its defaults
distance Administrative distance
distribute-list Filter networks in routing updates
exit Exit from IPv6 routing protocol configuration mode
maximum-paths Forward packets over multiple paths
no Negate a command or set its defaults
poison-reverse Poison reverse updates
port Port and multicast address
redistribute Redistribute IPv6 prefixes from another routing protocol
split-horizon Split horizon updates
timers Adjust routing timers
R1(config-rtr)#
Chapter 8
Disable Split Horizon
 Disable the split horizon route loop prevention feature.
Router(config-rtr)#
no split-horizon
 Use the split-horizon router configuration command to re-

enable the feature.
R1(config)# ipv6 router rip RIP
R1(config-rtr)# no ?
distance Administrative distance
distribute-list Filter networks in routing updates
maximum-paths Forward packets over multiple paths
poison-reverse Poison reverse updates
port Port and multicast address
redistribute Redistribute IPv6 prefixes from another routing protocol
split-horizon Split horizon updates
timers Adjust routing timers
R1(config-rtr)# no split-horizon
R1(config-rtr)#
Chapter 8
Verifying and Troubleshooting RIPng
Command Description
Displays the parameters and current state of the active IPv6

show ipv6 protocols routing protocol processes.
[summary] The summary keyword specifies that only the configured
routing protocol process names are displayed.
debug ipv6 rip Displays IPv6 RIPng routing transaction debug messages.
[interface-type The interface-type interface-number option can
interface-number] be used to display interface specific debug messages.
Chapter 8
Configuring RIPng Example
R1
S0/0/0 2001:12::1/64
DLCI: 102 DLCI: 103

Lo102: 2001:22::2/64
2001:12::2/64 2001:12::3/64 Lo103: 2001:33::3/64
Frame Relay
DLCI: 201 DLCI: 301
R2 S1/1.7 S1/1.7
R3
 In this example topology, R1 is the central site router and R2 and R3

are branch site routers configured in a hub-and-spoke topology (star).
• The global unicast addresses displayed have been preconfigured on the indicated
interfaces and are active.
• The loopback interfaces on R2 and R3 have also been configured accordingly.
• Frame Relay maps using the global addresses have also been pre-configured on each
router.
Chapter 8
R1
S0/0/0 2001:12::1/64
DLCI: 102 DLCI: 103

Lo102: 2001:22::2/64
2001:12::2/64 2001:12::3/64 Lo103: 2001:33::3/64
Frame Relay
DLCI: 201 DLCI: 301
R2 S1/1.7 S1/1.7
R3
R1# show run interface s0/0/0

!
interface Serial0/0/0
no ip address
encapsulation frame-relay IETF
ipv6 address 2001:12::1/64
frame-relay lmi-type cisco
frame-relay map ipv6 2001:12::2 102
end
R1#
Chapter 8
R1
S0/0/0 2001:12::1/64
DLCI: 102 DLCI: 103

Lo102: 2001:22::2/64
2001:12::2/64 2001:12::3/64 Lo103: 2001:33::3/64
Frame Relay
DLCI: 201 DLCI: 301
R2 S1/1.7 S1/1.7
R3
R2# show run interface s1/1.7

!
interface Serial1/1.7 multipoint
ipv6 address 2001:12::2/64
cdp enable
end
R2#
Chapter 8
R1
S0/0/0 2001:12::1/64
DLCI: 102 DLCI: 103

Lo102: 2001:22::2/64
2001:12::2/64 2001:12::3/64 Lo103: 2001:33::3/64
Frame Relay
DLCI: 201 DLCI: 301
R2 S1/1.7 S1/1.7
R3
R3# show run interface s1/1.7

!
interface Serial1/1.7 multipoint
ipv6 address 2001:12::3/64
cdp enable
end
R3#
Chapter 8
R1
S0/0/0 2001:12::1/64
DLCI: 102 DLCI: 103

Lo102: 2001:22::2/64
2001:12::2/64 2001:12::3/64 Lo103: 2001:33::3/64
Frame Relay
DLCI: 201 DLCI: 301
R2 S1/1.7 S1/1.7
R3
R1# ping 2001:12::2

Sending 5, 100-byte ICMP Echos to 2001:12::2, timeout is 2 seconds:
!!!!!
R1#
R1# ping 2001:12::3
!!!!!
R1#
Chapter 8
R1
S0/0/0 2001:12::1/64
DLCI: 102 DLCI: 103

Lo102: 2001:22::2/64
2001:12::2/64 2001:12::3/64 Lo103: 2001:33::3/64
Frame Relay
DLCI: 201 DLCI: 301
R2 S1/1.7 S1/1.7
R3
 Although connectivity has been established from site to site, there is no

connectivity for the LANs therefore RIPng will be configured.
 RIPng, like all the IPv6 routing protocols, requires link-local addresses.
• IGPs do not use global unicast addresses.
 Therefore, Frame Relay maps to the link-local addresses must be
configured on all three routers.
• Note that the broadcast keyword must also be configured.
Chapter 8
R1
S0/0/0 2001:12::1/64
DLCI: 102 DLCI: 103

Lo102: 2001:22::2/64
2001:12::2/64 2001:12::3/64 Lo103: 2001:33::3/64
Frame Relay
DLCI: 201 DLCI: 301
R2 S1/1.7 S1/1.7
R3

R1(config-if)# frame-relay map ipv6 FE80::250:73FF:FE3D:6A20 103 broadcast
R1(config-if)# frame-relay map ipv6 FE80::2B0:64FF:FE33:FB60 102 broadcast
R1(config-if)#
R2(config)# interface s1/1.7

R2(config-subif)# frame-relay map ipv6 FE80::219:56FF:FE2C:9F60 201 broadcast
R2(config-subif)#

R3(config-subif)# frame-relay map ipv6 FE80::219:56FF:FE2C:9F60 301 broadcast
R3(config-subif)#
Chapter 8
R1
S0/0/0 2001:12::1/64
DLCI: 102 DLCI: 103

Lo102: 2001:22::2/64
2001:12::2/64 2001:12::3/64 Lo103: 2001:33::3/64
Frame Relay
DLCI: 201 DLCI: 301
R2 S1/1.7 S1/1.7
R3
 The next step is to enable IPv6 routing and then enable the respective
serial interfaces for RIPng.
• The loopback interfaces of R2 and R3 will also have to be configured.
• Configuring the interface for RIPng automatically creates the RIPng process.
 The serial interface of R1 will also require that the split horizon feature
be disabled.
• Otherwise advertisements from R2 would not be propagated to R3, and R3
routes would not be propagated to R2.
Chapter 8
R1
S0/0/0 2001:12::1/64
DLCI: 102 DLCI: 103

Lo102: 2001:22::2/64
2001:12::2/64 2001:12::3/64 Lo103: 2001:33::3/64
Frame Relay
DLCI: 201 DLCI: 301
R2 S1/1.7 S1/1.7
R3

R1(config-if)# ipv6 rip RIPTag enable
R1(config-if)# exit
R1(config)# ipv6 router rip RIPTag
R1(config-rtr)# no split-horizon
R1(config-rtr)#
Chapter 8
R1
S0/0/0 2001:12::1/64
DLCI: 102 DLCI: 103

Lo102: 2001:22::2/64
2001:12::2/64 2001:12::3/64 Lo103: 2001:33::3/64
Frame Relay
DLCI: 201 DLCI: 301
R2 S1/1.7 S1/1.7
R3

R2(config-subif)# ipv6 rip RIPTag enable
R2(config-subif)# exit
R2(config)# interface lo102
R2(config-if)#

R3(config-subif)# ipv6 rip RIPTag enable
R3(config-subif)# exit
R3(config)# interface lo103
R3(config-if)#
Chapter 8
R1
S0/0/0 2001:12::1/64
DLCI: 102 DLCI: 103

Lo102: 2001:22::2/64
2001:12::2/64 2001:12::3/64 Lo103: 2001:33::3/64
Frame Relay
DLCI: 201 DLCI: 301
R2 S1/1.7 S1/1.7
R3
R2# ping 2001:33::3

!!!!!
Success rate is 100 percent (5/5) round-trip min/avg/max = 140/141/144ms
R2#
Chapter 8
Chapter 8

Implementing Ipv6 in The Enterprise Network: CCNP Route: Implementing Ip Routing

Uploaded by

Copyright:

Available Formats

Implementing Ipv6 in The Enterprise Network: CCNP Route: Implementing Ip Routing

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Implementing Ipv6 in The Enterprise Network: CCNP Route: Implementing Ip Routing

Uploaded by

Copyright:

Available Formats

Chapter 8:

Implementing IPv6 in the

CCNP ROUTE: Implementing IP Routing

“One to Nearest” (Allocated from Unicast)

 The destination node

IPv6 = 128 bits

2031: 0:130F: 0: 0: 9C0:876A:130B

IPv6 = 128 bits

Subnet prefix Interface ID

Global Site-Local Link-Local

/23 /32 /48 /64

2001 0008 21B:D5FF:FE5B:A408

/23 /32 /48 /64

2001 0008 21B:D5FF:FE5B:A408

/23 /32 /48 /64

2001 0008 21B:D5FF:FE5B:A408

ICMP type: 135 (NS)

 ICMPv6 Neighbor Solicitation (NS) is similar to IPv4 ARP in that

ICMP type: 136 (NA)

 Each destination node that receives the NS responds with an ICMPv6

A and B can now exchange packets on this link.

 The two devices can now communicate on the link because

 What would happen if R1 wanted to exchange packets with R2?

 When R1 desires to exchange packets with R2, R1 sends an NS

 Both R2 and R3 are listening to the same solicited-node multicast

ICMP type: 133 (RS)

ICMP type: 134 (RA)

 All routers on the network reply to the RS immediately, with an RA sent

ICMP type: 135 (NS)

Displays the status of interfaces configured for IPv6.

Displays messages associated with ICMPv6 neighbor

Displays information associated with IPv6 packet

 Command is only required before configuring an IPv6

 An optional command, CEFv6 is an advanced Layer 3 IP

Link-local (FE80::/10) Global Routable

Static Dynamic Static Dynamic

IPv6 Unnumbered DHCPv6

Link-local (FE80::/10) Global Routable

Static Dynamic Static Dynamic

IPv6 Unnumbered DHCPv6

 Command is used to statically configure an IPv6 address and prefix on

R1(config)# interface fa0/0

 Link-local addresses are created:

R1# show ipv6 interface fa0/0

 The output confirms the link-local address.

R1(config)# ipv6 unicast-routing

 Global Unicast IPv6 addresses are assigned by omitting the link-

R1# show ipv6 interface fa0/1

 Notice that by simply configuring a global unicast IPv6 address on an

R1# show ipv6 interface fa0/0

R1(config)# interface fa0/0

 What would happen if we configured 2 different IPv4 addresses and 2

R1# show run interface fa0/0

 The second IPv4 entry replaced the first entry.

R1# show ipv6 interface loopback 100

Link-local (FE80::/10) Global Routable

Static Dynamic Static Dynamic

IPv6 Unnumbered DHCPv6

 Enables IPv6 processing on an interface without assigning an explicit