Hands-on Experience with IPv6 Routing and Switching

Hands-on Experience with IPv6 Routing and
Services
Faraz Shamim, Technical Leader
Harold Ritter, Technical Leader

This IPv6 basic and advanced lab will provide you an opportunity to configure,
troubleshoot, design and implement IPv6 network using IPv6 technologies and features
such as; IPv6 addressing, IPv6 neighbor discovery, HSRPv6, static routing, OSPFv3,
EIGRPv6 and BGPv6. You will be provided with a scenario made up with an IPv4 network
where you will get the opportunity to configure and implement IPv6 based on the
requirements and needs on the network. For e.g where would you deploy dual stack,
where it make sense to do tunneling and how to deploy an IPv6 routing protocols without
impacting your existing Network infrastructure.
•  Students MUST have a basic understanding of IPv6 Addressing and Routing Protocols.
•  Familiarity with Cisco IOS.
Prerequisites: Session Abstract
2

Agenda
§  Lab1 : IPv6 Addressing & Stateless Address Auto
Configuration (SLAAC)
§  Lab2 : IPv6 Neighbor Discovery
§  Lab3 : IPv6 Static Routing
§  Lab4 : HSRPv6
§  Lab5 : EIGRPv6
§  Lab6 : Manual Tunnels (IPv6oIPv4 & GRE)
§  Lab7 : OSPFv3
§  Lab8 : BGPv6
3

Lab Synopsis
•  You are a network engineer at ABC Inc. You just attended a cool lab session on IPv6 at
Cisco Connect in Toronto and you are extremely enthusiastic about deploying IPv6 in
your network.
•  Since this is your first time with IPv6, you want to experiment things at your own before
talking to your ISP about IPv6 connectivity. Your goal is to make your own network IPv6
ready before talking to your ISP about IPv6.
•  You are challenged with multiple task during this exercise. Each task will be called a Lab.
•  One thing you learned in the lab session on IPv6 at Cisco Connect Toronto is to go with
dual stack as much as possible. In the event you can not use dual stack you will use
tunneling techniques.
•  IPv4 piece is already up and running in the network and nothing needs to be done on
IPv4 side
•  R1 is connected to IPv6 Internet. For this purpose we have assigned a loopback 1 with
an ipv6 address of 2004:db8::1/128. So if any router can ping this address, it means it
can access IPv6 internet
4

Lab 1 : IPv6 Addressing & Stateless Address Auto
Configuration (SLAAC)

Lab 1 IPv6 Unique Local Address
•  The first thing you would like to do is to make sure your devices are
capable of running IPv6. After you have verified that with your vendor,
now you are ready to deploy IPv6 slowly in your Network.
•  ABC Site 1 is the simplest site so you want to pick that site first
•  Site 1 is running static routing in IPv4 and you want to continue using
static routing when you move to IPv6
•  Your task is to enable IPv6 between R4 and H1. You want to make
sure you do not run into any issues in Site 1 before you move on with
site 2
•  Since this is your first site, you are using a private address
FD01:DB8::/32 for this purpose
7

Lab 1 IPv6 Stateless Auto-Configuration (SLAAC)
•  Your plan is to test the plug and play behavior of IPv6. So you only
assigned the IPv6 unique local address on R4 interface facing H1 and
see if you get an IPv6 address assigned automatically on H1 from R4
(Refer to Slide 39 for IPv6 addressing example)
•  You want to see how EUI-64 method works so you are using that on
R4 during the address assignment with /64 mask.
•  Assign this unique local address on R4 using subnetting as shown in
the next slide
•  Ping R4’s link local and Unique local IPv6 address from H1
8

Lab 1: IPv6 Addressing & SLAAC
9

R# Configs
R4 R4(config)#ipv6 unicast-routing
R4(config)#interface e0/0
R4(config-if)#ipv6 address fd01:db8:1:41::/64 EUI-64
R4(config-if)#end
H1 H1(config)#interface e0/0
H1(config-if)#ipv6 enable
H1(config-if)#ipv6 address autoconfig
H1(config-if)#end
Lab 1 IPv6 Unique Local & SLAAC: Configs
10

R4 H1
R4#sh ipv6 int e0/0
Ethernet0/0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5400
No Virtual link-local address(es):
Global unicast address(es):
FD01:DB8:1:41:A8B8:CCFF:FE00:5400, subnet is FD01:DB8:1:41::/64
[EUI]
Joined group address(es):
FF02::1
FF02::2
FF02::1:FF00:5400
MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
ICMP unreachables are sent
ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds (using 30000)
ND advertised reachable time is 0 (unspecified)
ND advertised retransmit interval is 0 (unspecified)
ND router advertisements are sent every 200 seconds
ND router advertisements live for 1800 seconds
ND advertised default router preference is Medium
Hosts use stateless autoconfig for addresses.
H1#sh ipv6 int e0/0
Stateless address autoconfig enabled
FD01:DB8:1:41:A8BB:CCFF:FE00:5700, subnet is FD01:DB8:1:41::/64
[EUI/CAL/PRE]
valid lifetime 2591861 preferred lifetime 604661
FF02::1
FF02::1:FF00:5700
MTU is 1500 bytes
Default router is FE80::A8BB:CCFF:FE00:5400 on Ethernet0/0
Lab 1 IPv6 Unique Local & SLAAC:
Verification
11

R# Verification commands
H1 H1#ping FE80::A8BB:CCFF:FE00:5400
Output Interface: Ethernet0/0
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to FE80::A8BB:CCFF:FE00:5400, timeout is 2 seconds:
Packet sent with a source address of FE80::A8BB:CCFF:FE00:5700%Ethernet0/0
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/1 ms
H1#
Note: the last 64 bit address may be different from A8BB:CCFF:FE00:5400, verify with show ipv6 interface on
R4 E0/0
H1 H1#ping FD01:DB8:1:41:A8B8:CCFF:FE00:5400
Sending 5, 100-byte ICMP Echos to FD01:DB8:1:41:A8B8:CCFF:FE00:5400, timeout is 2 seconds:
!!!!!
H1#
Note: the last 64 bit address may be different from A8BB:CCFF:FE00:5400, verify with show ipv6 interface on
R4 E0/0
Lab 1 IPv6 Unique Local & SLAAC:
Verification
12

R4 H1
R4#deb ipv6 nd
ICMP Neighbor Discovery events debugging is on
ICMPv6-ND: Request to send RA for FE80::A8BB:CCFF:FE00:5400
ICMPv6-ND: Setup RA from FE80::A8BB:CCFF:FE00:5400 to FF02::1 on
Ethernet0/0
ICMPv6-ND: MTU = 1500
ICMPv6-ND: prefix = FD01:DB8:1:41::/64 onlink autoconfig
ICMPv6-ND: 2592000/604800 (valid/preferred)
ICMPv6-ND: Request to send RA for FE80::A8BB:CCFF:FE00:5400
ICMPv6-ND: Setup RA from FE80::A8BB:CCFF:FE00:5400 to FF02::1 on
Ethernet0/0
ICMPv6-ND: prefix = FD01:DB8:1:41::/64 onlink autoconfig
R4#
H1#deb ipv6 nd
ICMP Neighbor Discovery events debugging is on
ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5400 on
Ethernet0/0
ICMPv6-ND: Prefix : FD01:DB8:1:1::, Length: 64, Vld Lifetime:
2592000, Prf Lifetime: 604800, PI Flags: C0
ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig
FD01:DB8:1:41::/64 eui-64, FD01:DB8:1:41:A8BB:CCFF:FE00:5700
FD01:DB8:1:41:A8BB:CCFF:FE00:5700/64 is existing
ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5400 on
Ethernet0/0
ICMPv6-ND: Prefix : FD01:DB8:1:1::, Length: 64, Vld Lifetime:
2592000, Prf Lifetime: 604800, PI Flags: C0
ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig
FD01:DB8:1:41::/64 eui-64, FD01:DB8:1:41:A8BB:CCFF:FE00:5700
FD01:DB8:1:41:A8BB:CCFF:FE00:5700/64 is existing
H1#
Lab 1 IPv6 SLAAC: Debugs
13

Lab 1 IPv6 Global Unicast Address
•  After successfully pilot testing in site 1, you now want to enable IPv6 in site 2
•  You asked from your ISP about IPv6 and they gave you a /48 address
2001:db8:1::/48 from their block
•  Instead of removing the unique local address from site 1 you decided to keep it
and configured the new global address in site 1 and site 2
•  This time you want to use manual assignment of last 64 bit so you will not use
EUI-64 bit method for global addressing. You want to make sure this is the
method you follow from now on
14

Lab 1 IPv6 Global Unicast Address
•  For the manual assignment you will use the router number as the last 4 bits out
of 64, for e,g. R4 will have ::4 as the last 64 bits
•  You want to test the multiple IPv6 address assignment on a router so you will
configure two additional IPv6 global addresses on R5 and R6
•  Assign IPv6 global unicast address on site 1 and site 2 by using subnetting as
shown in the next slide
15

Lab 1b: IPv6 Global Unicast address & SLAAC
16

R# Configs
R4(config)#interface loop0
R4(config-if)#ipv6 address 2001:db8:1:1::4/128
R4(config-if)#end
R5(config-if)#end
Lab 1 IPv6 Global Unicast address & SLAAC: Configs
17

R# Configs
R6(config-if)#end
H2(config-if)#end
Lab 1 IPv6 Global Unicast address & SLAAC:
Configs
18

R4 Loopback 0
R4#sh ipv6 int lo 0
Loopback0 is up, line protocol is up
2001:DB8:1:1::4, subnet is 2001:DB8:1:1::4/128
FF02::1
FF02::2
FF02::1:FF00:4
FF02::1:FF00:5900
MTU is 1514 bytes
ND DAD is not supported
ND RAs are suppressed (periodic)
R4#
Lab 1 IPv6 Global Unicast address: Verification
19

R4 Ethernet0/0
R4#sh ipv6 int e0/0
2001:DB8:1:41::4, subnet is 2001:DB8:1:41::/64
FD01:DB8:1:41:A8BB:CCFF:FE00:5400, subnet is
FD01:DB8:1:41::/64 [EUI]
FF02::1
FF02::2
FF02::1:FF00:4
FF02::1:FF00:5400
MTU is 1500 bytes
R4#
20

R5 Loopback 0
R5#sh ipv6 int lo 0
IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5A00
2001:DB8:1:1::5, subnet is 2001:DB8:1:1::5/128
FF02::1
FF02::2
FF02::1:FF00:5
FF02::1:FF00:5A00
MTU is 1514 bytes
R5#
21

R5 Ethernet0/0
R5#sh ipv6 int e0/0
IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5A00
2001:DB8:1:56::5, subnet is 2001:DB8:1:56::/64
2001:DB8:1:57::5, subnet is 2001:DB8:1:57::/64
2001:DB8:1:58::5, subnet is 2001:DB8:1:58::/64
FF02::1
FF02::2
FF02::1:FF00:5
FF02::1:FF00:5A00
MTU is 1500 bytes
22

R6 Loopback 0
R6#sh ipv6 int lo 0
IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5B00
2001:DB8:1:1::6, subnet is 2001:DB8:1:1::6/128
FF02::1
FF02::2
FF02::1:FF00:6
FF02::1:FF00:5B00
MTU is 1514 bytes
R6#
23

R6 Ethernet0/0
R6#sh ipv6 int e0/0
2001:DB8:1:56::6, subnet is 2001:DB8:1:56::/64
2001:DB8:1:57::6, subnet is 2001:DB8:1:57::/64
2001:DB8:1:58::6, subnet is 2001:DB8:1:58::/64
FF02::1
FF02::2
FF02::1:FF00:6
FF02::1:FF00:5B00
MTU is 1500 bytes
24

H1 Ethernet0/0
H1#sh ipv6 int e0/0
2001:DB8:1:41:A8BB:CCFF:FE00:5700, subnet is 2001:DB8:1:41::/64 [EUI/CAL/PRE]
FD01:DB8:1:41:A8BB:CCFF:FE00:5700, subnet is FD01:DB8:1:41::/64 [EUI/CAL/PRE]
FF02::1
FF02::1:FF00:5700
MTU is 1500 bytes
Default router is FE80::A8BB:CCFF:FE00:5400 on Ethernet0/0
H1#
Lab 1 IPv6 SLAAC: Verification
25

H2 Ethernet0/0
H2#sh ipv6 int e0/0
IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5D00
2001:DB8:1:56:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:56::/64 [EUI/CAL/PRE]
FF02::1
FF02::1:FF00:5D00
MTU is 1500 bytes
Default router is FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0
26

H2 H2#ping 2001:db8:1:56::5
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:56::5, timeout is 2
seconds:
!!!!!
H2#ping 2001:db8:1:57::5
seconds:
!!!!!
H2#ping 2001:db8:1:58::5
seconds:
!!!!!
H2#ping 2001:db8:1:56::6
seconds:
!!!!!
H2#ping 2001:db8:1:57::6
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:57::6, timeout is 2 seconds:
!!!!!
H2#ping 2001:db8:1:58::6
!!!!!
H2#
27

H1 H1#ping 2001:DB8:1:41::4
!!!!!
H1#
28

R5
R5#deb ipv6 nd
ICMPv6-ND: Request to send RA for FE80::A8BB:CCFF:FE00:5A00
ICMPv6-ND: Setup RA from FE80::A8BB:CCFF:FE00:5A00 to FF02::1 on Ethernet0/0
ICMPv6-ND: prefix = 2001:DB8:1:56::/64 onlink autoconfig
R5#
ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5B00 on Ethernet0/0
ICMPv6-ND: Prefix : 2001:DB8:1:56::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0
R5#
29

R6
R6#deb ipv6 nd
ICMPv6-ND: Request to send RA for FE80::A8BB:CCFF:FE00:5B00
ICMPv6-ND: Setup RA from FE80::A8BB:CCFF:FE00:5B00 to FF02::1 on Ethernet0/0
R6#
ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0
H2#
30

H1
H1#deb ipv6 nd
ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5900 on Ethernet0/0
ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:41::/64 eui-64, 2001:DB8:1:41:A8BB:CCFF:FE00:5C00
2001:DB8:1:41:A8BB:CCFF:FE00:5C00/64 is existing
ICMPv6-ND: Prefix : FD01:DB8:1:41::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0
ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig FD01:DB8:1:41::/64 eui-64, FD01:DB8:1:41:A8BB:CCFF:FE00:5C00
FD01:DB8:1:41:A8BB:CCFF:FE00:5C00/64 is existing
H1#
31

H2
H2#deb ipv6 nd
ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5B00 on Ethernet0/0
ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:56::/64 eui-64, 2001:DB8:1:56:A8BB:CCFF:FE00:5D00
2001:DB8:1:56:A8BB:CCFF:FE00:5D00/64 is existing
H2#
H2#
32

Lab 2 : IPv6 Neighbor Discovery

Lab 2 Neighbor Discovery: RS & RA
•  You already tested plug and play behaviour of IPv6 in Site 1. Now you
want to play with some of the key elements of Neighbor discovery
•  In site 1, you want to study RS and RA msgs.
•  You want to change the RA interval from 200 to 30 seconds on R4
•  You disable the autoconfigs on H1 E0/0 interface and turn on the ipv6
nd debugs and enable autoconfigs again to see the RA/RS.
•  Turn on debug ipv6 nd on R4 and H1
34

R# Configs
R4 R4(config)#interface e0/0
R4(config-if)#ipv6 nd ra interval 30
R4(config-if)#end
H1(config-if)#no ipv6 address autoconfig
H1(config-if)#no ipv6 enable
H1(config-if)#end
Lab 2 IPv6 Neighbor discovery: Configs
35

R4
R4#sh ipv6 int e0/0
2001:DB8:1:41::4, subnet is 2001:DB8:1:41::/64
FD01:DB8:1:41:A8BB:CCFF:FE00:5900, subnet is
FD01:DB8:1:41::/64 [EUI]
FF02::1
FF02::2
FF02::1:FF00:4
FF02::1:FF00:5900
MTU is 1500 bytes
R4#
Lab 2 IPv6 Neighbor discovery: Verification
36

H1
*Jan 30 21:25:07.269: ICMPv6-ND: ND Module startup.
*Jan 30 21:25:07.270: ICMPv6-ND: Initialise OL prefix database
*Jan 30 21:25:07.270: ICMPv6-ND: IPv6 Opr Enabled on Null0
*Jan 30 21:25:07.270: ICMPv6-ND: Allocate ND subblock on Null0 [1]
*Jan 30 21:25:07.271: ICMPv6-ND: L2 came up on Null0
*Jan 30 21:25:07.271: IPv6-Addrmgr-ND: DAD request for FE80::1 on Null0
*Jan 30 21:25:07.271: IPv6-Addrmgr-ND: DAD: FE80::1 is unique.
*Jan 30 21:25:07.271: ICMPv6-ND: L3 came up on Null0
*Jan 30 21:25:07.271: ICMPv6-ND: Linklocal FE80::1 on Null0, Up
*Jan 30 21:25:07.271: ICMPv6-ND: IPv6 Opr Enabled on Ethernet0/0
*Jan 30 21:25:07.271: ICMPv6-ND: Allocate ND subblock on Ethernet0/0 [2]
*Jan 30 21:25:07.271: ICMPv6-ND: L2 came up on Ethernet0/0
*Jan 30 21:25:07.271: IPv6-Addrmgr-ND: DAD request for FE80::A8BB:CCFF:FE00:5C00 on Ethernet0/0
*Jan 30 21:25:07.272: ICMPv6-ND: Sending NS for FE80::A8BB:CCFF:FE00:5C00 on Ethernet0/0
*Jan 30 21:25:08.272: IPv6-Addrmgr-ND: DAD: FE80::A8BB:CCFF:FE00:5C00 is unique.
*Jan 30 21:25:08.272: ICMPv6-ND: Sending NA for FE80::A8BB:CCFF:FE00:5C00 on Ethernet0/0
*Jan 30 21:25:08.272: ICMPv6-ND: L3 came up on Ethernet0/0
*Jan 30 21:25:08.272: ICMPv6-ND: Linklocal FE80::A8BB:CCFF:FE00:5C00 on Ethernet0/0, Up
*Jan 30 21:25:20.231: ICMPv6-ND: Sending RS on Ethernet0/0
*Jan 30 21:25:20.251: ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5900 on Ethernet0/0
Lab 2 IPv6 Neighbor discovery: Debugs
37

Lab 2 Neighbor Discovery: DAD, NS & NA
•  You want to test the DAD, NS & NA mechanism of IPv6. For that you
turned on IPv6 neighbor discovery debug on R5 & R6
•  Assign a new address 2001:db8:1:59::5/64 on both R5 and R6
Ethernet interface
•  The debug will show the algorithm performed for DAD procedure. This
DAD is the first thing that occurs when any IPv6 address is assigned
on an interface
•  After testing the DAD procedure, remove the IPv6 address of
2001:db8:1:59::5/64 from R5 & R6 Ethernet
•  Ping R6’s Ethernet address of 2001:db8:1:56::6 from R5 to see how
NS and NA takes place between them
38

R# Configs
R5 R5(config)#int e0/0
39

R4
R6#sh ipv6 int
2001:DB8:1:56::6, subnet is 2001:DB8:1:56::/64
2001:DB8:1:57::6, subnet is 2001:DB8:1:57::/64
2001:DB8:1:58::6, subnet is 2001:DB8:1:58::/64
2001:DB8:1:59::5, subnet is 2001:DB8:1:59::/64
FF02::1
FF02::2
FF02::1:FF00:5
FF02::1:FF00:6
FF02::1:FF00:5B00
MTU is 1500 bytes
…
R5#sh ipv6 int e0/0 | i DUP
2001:DB8:1:59::5, subnet is 2001:DB8:1:59::/64 [DUP]
Lab 2 IPv6 Neighbor discovery: Verification
40

R6
*Jan 30 21:42:17.678: IPv6-Addrmgr-ND: Received prefix PI-flag change notification: prefix 2001:DB8:1:59::/64 onlink (was not-onlink)
*Jan 30 21:42:17.678: IPv6-Addrmgr-ND: DAD request for 2001:DB8:1:59::5 on Ethernet0/0
*Jan 30 21:42:17.679: ICMPv6-ND: Sending NS for 2001:DB8:1:59::5 on Ethernet0/0
*Jan 30 21:42:18.684: IPv6-Addrmgr-ND: DAD: 2001:DB8:1:59::5 is unique.
*Jan 30 21:42:18.684: ICMPv6-ND: Sending NA for 2001:DB8:1:59::5 on Ethernet0/0
*Jan 30 21:43:11.922: ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0
*Jan 30 21:48:57.826: ICMPv6-ND: 2592000/604800 (valid/preferred)
*Jan 30 21:49:39.078: IPv6-Addrmgr-ND: Received prefix PI-flag change notification: prefix 2001:DB8:1:59::/64 onlink (was not-onlink)
*Jan 30 21:49:39.078: IPv6-Addrmgr-ND: DAD request for 2001:DB8:1:59::5 on Ethernet0/0
*Jan 30 21:49:39.094: ICMPv6-ND: Received NA for 2001:DB8:1:59::5 on Ethernet0/0 from 2001:DB8:1:59::5
*Jan 30 21:49:39.095: %IPV6_ND-4-DUPLICATE: Duplicate address 2001:DB8:1:59::5 on Ethernet0/0
41

R# Configs
R5(config-if)#no ipv6 address 2001:db8:1:59::5/64
R6(config-if)#no ipv6 address 2001:db8:1:59::5/64
42

R5
R5#ping 2001:db8:1:56::6
!!!!!
R5#
*Jan 30 22:15:24.668: ICMPv6-ND: DELETE -> INCMP: 2001:DB8:1:56::6
*Jan 30 22:15:24.669: ICMPv6-ND: Resolving next hop 2001:DB8:1:56::6 on interface Ethernet0/0
*Jan 30 22:15:24.673: ICMPv6-ND: Received NA for 2001:DB8:1:56::6 on Ethernet0/0 from 2001:DB8:1:56::6
*Jan 30 22:15:24.673: ICMPv6-ND: Neighbour 2001:DB8:1:56::6 on Ethernet0/0 : LLA aabb.cc00.5b00
*Jan 30 22:15:24.673: ICMPv6-ND: INCMP -> REACH: 2001:DB8:1:56::6
R5#
*Jan 30 22:15:29.722: ICMPv6-ND: Received NS for 2001:DB8:1:56::5 on Ethernet0/0 from FE80::A8BB:CCFF:FE00:5B00
*Jan 30 22:15:29.722: ICMPv6-ND: Sending NA for 2001:DB8:1:56::5 on Ethernet0/0
*Jan 30 22:15:29.723: ICMPv6-ND: STALE -> DELAY: FE80::A8BB:CCFF:FE00:5B00
43

Lab 2 Neighbor Discovery: Renumbering
•  To test the renumbering behavior of IPv6, you want to change the IPv6
address on R5 & R6 to 2001:db8:1:88::/64 from 2001:db8:1:58::/64
•  First you configure the new IPv6 address of 2001:db8:1:88::/64 on both
R5 & R6 Ethernet interface
•  You also want to set the RA interval to 40 seconds
•  To deprecate the old address you want to configure preferred lifetime
of 2001:db8:1:58::/64 to 0 and valid lifetime to 50 on both R5 & R6.
(Note, may have to shut no shut E0/0 on H2 to rewrite the old valid &
prefer lifetime)
44

Lab 2 Neighbor Discovery: Renumbering
•  You noticed that the old prefix of 2001:db8:1:58::/64 is showing as
deprecated on H2. Note DEP may or may not show up during show
command
•  To get rid of the address completely, you configure the valid lifetime of
2001:db8:1:58::/64 to 0 on both R5 & R6
•  You noticed on H2 that the old prefix 2001:db8:1:58::/64 disappeared
from the cache
•  To clean up the configs, remove the old IPv6 prefix of
2001:db8:1:58::/64 as well as IPv6 nd prefix command from the
Ethernet interfaces of both R5 and R6
45

R# Configs
R5(config-if)#ipv6 nd prefix 2001:db8:1:58::/64 50 0
R5(config-if)#end
R6(config-if)#end
Lab 2 IPv6 Neighbor Discovery: Configs
46

H2
H2#sh ipv6 int e0/0
2001:DB8:1:58:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:58::/64 [EUI/CAL]
FF02::1
FF02::1:FF00:5D00
MTU is 1500 bytes
Lab 2 IPv6 Neighbor Discovery: Verification
47

H2
H2#deb ipv6 nd
*Jan 31 04:26:01.476: ICMPv6-ND: Prefix : 2001:DB8:1:56::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0
*Jan 31 04:26:01.476: ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:56::/64 eui-64, 2001:DB8:1:56:A8BB:CCFF:FE00:5D00
Lab 2 IPv6 Neighbor Discovery: Debugs
48

R# Configs
R5(config-if)#end
R6(config-if)#end
49

H2
H2#sh ipv6 int e0/0
FF02::1
FF02::1:FF00:5D00
MTU is 1500 bytes
Default router is FE80::A8BB:CCFF:FE00:5B00 on Ethernet0/0
H2#
50

H2
H2#deb ipv6 nd
H2#
*Jan 31 04:47:34.486: ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:56::/64 eui-64,
2001:DB8:1:56:A8BB:CCFF:FE00:5D00 2001:DB8:1:56:A8BB:CCFF:FE00:5D00/64 is existing
*Jan 31 04:47:34.487: ICMPv6-ND: Invalid prefix 2001:DB8:1:58::/64
H2#
Lab 2 IPv6 Neighbor Discovery: Debugs
51

R# Configs
R5(config-if)#no ipv6 add 2001:db8:1:58::5/64
R5(config-if)#no ipv6 nd prefix 2001:DB8:1:58::/64
R5(config-if)#end
R6(config-if)#no ipv6 add 2001:db8:1:58::6/64
R6(config-if)#no ipv6 nd prefix 2001:DB8:1:58::/64
R6(config-if)#end
Lab 2 IPv6 Neighbor Discovery: Cleanup Configs
52

Lab 2 Neighbor Discovery: Default Router
Selection
•  In site 2, you want to see how the default router selection
behaves in IPv6
•  You noticed that as soon as you enable IPv6 on H2, it starts
sending RS on the wire, looking for a router.
•  You also noticed in the debugs that both R5 and R6 are sending
RA messages towards H2. H2 looks at RA and configures the
addresses on its interface facing R5 & R6
•  After getting the address on H2, you want to make sure that H2
prefers R5 for sending all the IPv6 traffic outbound
•  (Refer to slide 34-35 for default router selection example)
53

R# Configs
R5(config-if)#ipv6 nd router-preference high
R5(config-if)#end
54

H2
H2#sh ipv6 router
Router FE80::A8BB:CCFF:FE00:5B00 on Ethernet0/0, last update 0 min
Hops 64, Lifetime 1800 sec, AddrFlag=0, OtherFlag=0, MTU=1500
HomeAgentFlag=0, Preference=Medium
Reachable time 0 (unspecified), Retransmit time 0 (unspecified)
Prefix 2001:DB8:1:56::/64 onlink autoconfig
Valid lifetime 2592000, preferred lifetime 604800
Router FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0, last update 0 min
Hops 64, Lifetime 1800 sec, AddrFlag=0, OtherFlag=0, MTU=1500
HomeAgentFlag=0, Preference=High
Reachable time 0 (unspecified), Retransmit time 0 (unspecified)
Prefix 2001:DB8:1:56::/64 onlink autoconfig
Valid lifetime 2592000, preferred lifetime 604800
55

H2
H2#sh ipv6 route ::/0
Routing entry for ::/0
Known via "static", distance 2, metric 0
Route count is 1/1, share count 0
Routing paths:
FE80::A8BB:CCFF:FE00:5A00, Ethernet0/0
Last updated 00:04:52 ago
Note, if you do not see a default route, type the following command and make sure you have the entry from R5
H2#sho ipv6 router
56

Lab 3 HSRPv6
•  Site 2 is running HSRP for IPv4 between R5 and R6
•  You decided to follow the same scheme for IPv6 also and enabled
HSRPv6 between R5 and R6
•  You noticed on H2 that the default route received from the HSRP
active router is a link local address
•  You turned on the IPv6 neighbor discovery debug on H2 to see if you
are receiving any RA msgs from R5 or R6
59

Lab 3 HSRPv6
•  Your primary router for HSRP in IPv4 was R5. You want to make sure
R6 is a primary router for IPv6 and when it goes down and comes back
up, it should become primary again
•  Configure HSRPv6 in autoconfig mode so it selects a virtual link local
address and advertise it as a virtual IPv6 address to hosts
•  Configure HSRP priority & preempt command on R6 so R6 becomes
the primary router even when it goes down and comes back up (See
slide 32 for details)
•  Turn on deb ipv6 nd on H2 to see what link local is being advertised as
a default
60

R# Configs
R5 R5(config-if)#standby ver 2
R5(config-if)#standby 1 ipv6 autoconfig
R5(config-if)#end
R6 R6(config-if)#standby ver 2
R6(config-if)#standby 1 ipv6 autoconfig
R6(config-if)#standby 1 preempt
R6(config-if)#standby 1 priority 105
R6(config-if)#end
Lab 3 HSRPv6: Configs
61

R5 & R6
R5#sh standby brief
P indicates configured to preempt.
|
Interface Grp Pri P State Active Standby Virtual IP
Et0/0 0 105 P Active local 10.1.56.6 10.1.56.1
Et0/0 1 100 Standby FE80::A8BB:CCFF:FE00:5B00
local FE80::5:73FF:FEA0:1
R5#
R6#sh standby brief
P indicates configured to preempt.
|
Interface Grp Pri P State Active Standby Virtual IP
Et0/0 0 100 Standby 10.1.56.5 local 10.1.56.1
Et0/0 1 105 P Active local FE80::A8BB:CCFF:FE00:5A00
FE80::5:73FF:FEA0:1
R6#
Lab 3 HSRPv6: Verification
62

R5
R5#sh standby ethernet 0/0 1
Ethernet0/0 - Group 1 (version 2)
State is Standby
4 state changes, last state change 00:08:17
Virtual IP address is FE80::5:73FF:FEA0:1
Active virtual MAC address is 0005.73a0.0001
Local virtual MAC address is 0005.73a0.0001 (v2 IPv6 default)
Hello time 3 sec, hold time 10 sec
Next hello sent in 0.624 secs
Preemption disabled
Active router is FE80::A8BB:CCFF:FE00:5B00, priority 105 (expires in 11.328 sec)
MAC address is aabb.cc00.5b00
Standby router is local
Priority 100 (default 100)
Group name is "hsrp-Et0/0-1" (default)
63

R6
R6#sh standby ethernet 0/0 1
Ethernet0/0 - Group 1 (version 2)
State is Active
2 state changes, last state change 00:07:58
Virtual IP address is FE80::5:73FF:FEA0:1
Active virtual MAC address is 0005.73a0.0001
Local virtual MAC address is 0005.73a0.0001 (v2 IPv6 default)
Hello time 3 sec, hold time 10 sec
Next hello sent in 2.768 secs
Preemption enabled
Active router is local
Standby router is FE80::A8BB:CCFF:FE00:5A00, priority 100 (expires in 9.216 sec)
Priority 105 (configured 105)
Group name is "hsrp-Et0/0-1" (default)
64

H2
H2#sh ipv6 route ::/0
Routing paths:
FE80::5:73FF:FEA0:1, Ethernet0/0
H2#
65

H2
H2#deb ipv6 nd
H2#
*Feb 2 10:24:20.246: ICMPv6-ND: Received RA from FE80::5:73FF:FEA0:1 on Ethernet0/0
*Feb 2 10:24:20.246: ICMPv6-ND: Prefix : 2001:DB8:1:56::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0
*Feb 2 10:24:20.246: ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:56::/64 eui-64,
H2#
Lab 3 HSRPv6: Debugs
66

Lab 4 EIGRPv6
•  Site 2 is running EIGRP for IPv4 between R5 and R6
•  You decided to follow the same scheme for IPv6 also and enabled
EIGRPv6 between R5 and R6
•  You noticed that in order to advertise the secondary address on the
same interface in EIGRPv4 you had to turn off split horizon but in
EIGRPv6 you do not have to do anything. This is because split horizon
is turned off by default in EIGRP for IPv6
69

Lab 4 EIGRPv6
•  You also noticed that all the control packets of EIGRP for e.g. hellos are
sourced from link local address
•  All other functionalities are very much the same as EIGRP for IPv4
•  The router ID is picked up as the highest loopback address in IPv4
70

R# Configs
R5 R5(config-if)#int loop 0
R5(config-if)#ipv6 eigrp 1
R5(config-if)#int e0/0
R5(config-if)#exit
R5(config-if)#ipv6 router eigrp 1
R5(config-if)#end
R6 R6(config-if)#int loop 0
R6(config-if)#exit
R6(config-if)#ipv6 router eigrp 1
R6(config-if)#end
Lab 4 EIGRPv6: Configs
71

R5 R6
R5#sh ipv6 prot | b EIGRP
EIGRP-IPv6 Protocol for AS(1)
Metric weight K1=1, K2=0, K3=1, K4=0, K5=0
NSF-aware route hold timer is 240
Router-ID: 10.1.1.5
Topology : 0 (base)
Active Timer: 3 min
Distance: internal 90 external 170
Maximum path: 16
Maximum hopcount 100
Maximum metric variance 1
Interfaces:
Loopback0
Ethernet0/0
Redistribution:
None
R6#sh ipv6 prot | b EIGRP
EIGRP-IPv6 Protocol for AS(1)
Metric weight K1=1, K2=0, K3=1, K4=0, K5=0
NSF-aware route hold timer is 240
Router-ID: 10.1.1.6
Topology : 0 (base)
Active Timer: 3 min
Distance: internal 90 external 170
Maximum path: 16
Maximum hopcount 100
Maximum metric variance 1
Interfaces:
Loopback0
Ethernet0/0
Redistribution:
None
Lab 4 EIGRPv6: Verification
72

R5 & R6
R5#sh ipv6 eigrp nei
EIGRP-IPv6 Neighbors for AS(1)
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 Link-local address: Et0/0 10 00:15:15 3 100 0 3
FE80::A8BB:CCFF:FE00:5600
R5#
R6#sh ipv6 eigrp nei
EIGRP-IPv6 Neighbors for AS(1)
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
0 Link-local address: Et0/0 11 00:17:11 4 100 0 3
FE80::A8BB:CCFF:FE00:5500
R6#
73

R5 & R6
R5#sh ipv6 route eigrp
IPv6 Routing Table - default - 9 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, R - RIP, I1 - ISIS L1, I2 - ISIS L2
IA - ISIS interarea, IS - ISIS summary, D - EIGRP, EX - EIGRP external
ND - Neighbor Discovery, l - LISP
O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
D 2001:DB8:1:1::6/128 [90/409600]
via FE80::A8BB:CCFF:FE00:5600, Ethernet0/0
R5#
R6#sh ipv6 route eigrp
IPv6 Routing Table - default - 9 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, R - RIP, I1 - ISIS L1, I2 - ISIS L2
IA - ISIS interarea, IS - ISIS summary, D - EIGRP, EX - EIGRP external
ND - Neighbor Discovery, l - LISP
O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
D 2001:DB8:1:1::5/128 [90/409600]
via FE80::A8BB:CCFF:FE00:5500, Ethernet0/0
R6#
74

R5 & R6
R5#debug ipv6 packet detail
[…]
11:16:23.010: IPV6: source FE80::A8BB:CCFF:FE00:5500 (local)
11:16:23.010: dest FF02::A (Ethernet0/0)
11:16:23.010: traffic class 224, flow 0x0, len 80+0, prot 88, hops 255, originating
R6#debug ipv6 packet detail
11:19:59.830: IPV6: source FE80::A8BB:CCFF:FE00:5500 (Ethernet0/0)
11:19:59.830: dest FF02::A
11:19:59.830: traffic class 224, flow 0x0, len 80+14, prot 88, hops 255, forward to ulp
Lab 4 EIGRPv6: Debugs
75

Lab 5 IPv6 Static Routing: IPv6 Static Default
Route
•  After planning and configuring all the addressing scheme for your Site
1 and Site 2, you talked with the ISP and request for IPv6 Service.
•  You found out that your ISP has IPv6 internet connectivity only but they
have not enabled IPv6 internally in their network so no Site to Site is
possible at this moment but they can enable static routing for Site 1
and advertise Site 1 prefix over the IPv6 Internet
•  The ISP has also asked you to enable IPv6 static default routing on R4
pointing towards the ISP router (R1)
77

Lab 5 IPv6 Static Routing: IPv6 Static Default
Route
•  Configure the IPv6 interface addresses on the link between ISP and
R4 as shown on the next slide (::14 is the ISP router and ::15 is R4)
•  Configure a static default route on R4 using a link local address as a
next hop pointing towards R1
78

R# Configs
R1 R1(config)#int s0/0
R1(config-if)#ipv6 add 2001:db8:14:1::14/127
R1(config)#end
R4 R4(config)#int s1/0
R1(config-if)#ipv6 route ::/0 Serial 1/0
R1(config)#end
Lab 5 IPv6 Static routing: Configs
80

R4
R4#sh ipv6 route ::/0
Routing paths:
FE80::4AFF:FEA2:851, Serial1/0
Lab 5 IPv6 Static routing: Verification
81

Lab 5 IPv6 Static Routing: IPv6 Static Route
•  The ISP has configured an IPv6 static routing for the LAN address of
2001:db8:1:41::/64 pointing towards R4
•  Since ISP is connected to IPv6 Internet, Site 1 should be able to reach
any IPv6 address on the internet
•  ISP shared their configs and you noticed that they are using global
unicast address as a next hop for the static route 2001:db8:1:41::/64
82

Lab 5 IPv6 Static Routing: IPv6 Static Route
•  Configure a static route 2001:db8:1:41::/64 on R1 with next-hop of
R4’s global address on Ethernet interface
•  Due to the limited lab environment, we will ping 2004:db8::1 from H1
and upon success we will assume that we are connected to IPv6
Internet
•  Ping 2004:db8::1 from H1 and see if its successful
83

R# Configs
R1 R1(config)#ipv6 route 2001:db8:1:41::/64 2001:db8:14:1::15
R1(config)#end
Lab 5 IPv6 Static routing: Configs
• Note, no interface needs to be specified when the
next hop is global unicast address
84

R# Verification
R1 R1#sh ipv6 route 2001:db8:1:41::/64
Routing entry for 2001:DB8:1:41::/64
Routing paths:
2001:DB8:14:1::15
R1#
H1 H1>ping 2004:db8::1
Sending 5, 100-byte ICMP Echos to 2004:DB8::1, timeout is 2 seconds:
!!!!!
H1>
Lab 5 IPv6 Static routing: Verification
85

Lab 6 IPv6 Manual Tunnels: IPv6oIP4
•  Site 2 has two connection to the ISP. You talked to the ISP about providing
IPv6 connectivity to Site 2 but you came to know that due to some limitation,
the ISP can not do dual stack on those two connections
•  ISP gave you the option of a manual tunnel called IPv6 over IPv4 on the link
between ISP and R5
•  For the tunnel to work, both sides needs to have an IPv4 route of each other
(Note, IPv4 routing is already established so no need to worry about that”
87

Lab 6 IPv6 Manual Tunnels: IPv6oIP4
•  Since there is a directly connected interface between R3 and R5, the tunnel
source and destinations can easily be chosen as the outgoing interface
•  A new IPv6 address needs to be configured on both side over the tunnel
between R3 and R5 in the range 2001:db8:35:1::16/127 as shown in the next
slide (::16 on R3 side and ::17 on R5 side)
•  Ping R5 IPv6 tunnel address from R3 and make sure it is successful to
determine that the tunnel is up and running
88

R# Configs
R5 R5(config-if)#int tun 0
R5(config-if)#tun source s1/0
R5(config-if)#tun destination 10.1.35.0
R5(config-if)#tun mode ipv6ip
R5(config-if)#end
R3(config-if)#tun mode ipv6ip
R5(config-if)#end
Lab 6 IPv6 Manual Tunnels: Configs
90

R3 Tunnel 0 R5 Tunnel 0
R3#sh ipv6 int tun 0
Tunnel0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::A01:2300
2001:DB8:35:1::16, subnet is 2001:DB8:35:1::16/127
FF02::1
FF02::2
FF02::1:FF00:16
FF02::1:FF01:2300
MTU is 1480 bytes
R3#
IPv6 is enabled, link-local address is FE80::A01:2301
2001:DB8:35:1::17, subnet is 2001:DB8:35:1::16/127
FF02::1
FF02::2
FF02::1:FF00:17
FF02::1:FF01:2301
MTU is 1480 bytes
R5#
Lab 6 IPv6 Manual Tunnels: Verification
91

R3
R3#ping 2001:db8:35:1::17
!!!!!
R3#
92

Lab 6 IPv6 Manual Tunnels: GRE
•  The link between R3 and R6 has another issue. It can not pass
protocol 41 for some reason
•  Due to this limitation, IPv6oIPv4 tunnel can not be established
between R3 and R6
•  ISP provided you an option of using GRE tunnel instead
between R3 and R6
•  Since there is a directly connected interface between R3 and
R6, the tunnel source and destinations can easily be chosen as
the outgoing interface
93

Lab 6 IPv6 Manual Tunnels: GRE
•  A new IPv6 address needs to configured on both side over the tunnel
between R3 and R6 in the range 2001:db8:36:1::16/127 as shown in
the previous slide
•  Ping R6 IPv6 tunnel address from R3 and make sure it is successful to
determine that the tunnel is up and running
94

R# Configs
R6(config-if)#tun mode gre ip
R6(config-if)#end
R3(config-if)#tun mode gre ip
R3(config-if)#end
Lab 6 IPv6 Manual Tunnels: Configs
95

R3 Tunnel 1 R6 Tunnel 0
IPv6 is enabled, link-local address is FE80::4AFF:FEA2:853
2001:DB8:36:1::16, subnet is 2001:DB8:36:1::16/127
FF02::1
FF02::2
FF02::1:FF00:16
FF02::1:FFA2:853
MTU is 1476 bytes
R3#
2001:DB8:36:1::17, subnet is 2001:DB8:36:1::16/127
FF02::1
FF02::2
FF02::1:FF00:17
FF02::1:FF00:5600
MTU is 1476 bytes
R6#
96

R3
R3#ping 2001:db8:36:1::17
!!!!!
R3#
97

Lab 7 OSPFv3
•  ISP has received a request from ABC Inc that they want IPv6
connectivity between Site 1 and Site 2. ISP are also making an effort to
make their own network dual stack and enabling IPv6 in their core
network
•  ISP has been running OSPFv2 internally in their core. They have
decided to run OSPFv3 for IPv6
•  Assign IPv6 address 2001:db8:172:17::2/127 between R2 & R3. ::2 on
R2 side and ::3 on R3 side
•  Assign IPv6 address 2001:db8:172:17::/127 between R1 & R2. :: on
R1 side and ::1 on R2 side
99

Lab 7 OSPFv3
•  Configure OSPFv3 area 0 between R1 and R2 and area 1 between R2
and R3 as shown in the next slide
•  Put Loopbacks of R1 and R2 into area 0
•  ISP has received a request from ABC Inc that they want IPv6
connectivity Redistribute R2’s loopback into OSPFv3
•  Ping ipv6 Loopback 0 of R3 from the loopback 0 of R1
•  Compare the difference between OSPFv2 and OSPFv3 LSAs
10

R# Area 1 Configs
R3(config)#int lo 0
R3(config)#int e0/0
R3(config-if)#ipv6 ospf 1 area 1
R3(config)#ipv6 router ospf 1
R3(config-rtr)#redistribute connected
R3(config-if)#end
R2(config-if)#end
Lab 7 OSPFv3: Configs
10

R# Area 0 Configs
R2 R2(config)#int lo 0
R2(config-if)#int s1/0
R2(config-if)#end
10

R# Area 0 Configs
R1(config)#int lo 0
R1(config)#int s1/0
R1(config-if)#ipv6 add 2001:db8:172:17::/127
R1(config-if)#end
10

R2
R2#sh ipv6 ospf nei
OSPFv3 Router with ID (172.16.1.2) (Process ID 1)
Neighbor ID Pri State Dead Time Interface ID Interface
172.16.1.1 0 FULL/ - 00:00:31 6 Serial1/0
172.16.1.3 1 FULL/DR 00:00:36 2 Ethernet0/0
R2#
R2#sh ipv6 ospf nei detail | i area
In the area 0 via interface Serial1/0
In the area 1 via interface Ethernet0/0
R2#
R2#sh ipv6 ospf int brie
Interface PID Area Intf ID Cost State Nbrs F/C
Se1/0 1 0 6 64 P2P 1/1
Et0/0 1 1 2 10 BDR 1/1
R2#
Lab 7 OSPFv3: Verification
10

R2
R2#sh ipv6 ospf
Routing Process "ospfv3 1" with ID 172.16.1.2
Supports IPv6 Address Family
Event-log enabled, Maximum number of events: 1000,
Mode: cyclic
It is an area border and autonomous system boundary
router
Redistributing External Routes from,
connected
[…]
Number of external LSA 1. Checksum Sum 0x0055EC
Number of areas in this router is 2. 2 normal 0 stub 0 nssa
Graceful restart helper support enabled
Reference bandwidth unit is 100 mbps
Area BACKBONE(0)
Number of interfaces in this area is 2
SPF algorithm executed 7 times
Number of LSA 8. Checksum Sum 0x03F283
Number of DCbitless LSA 0
Number of indication LSA 0
Number of DoNotAge LSA 0
Flood list length 0
Area 1
Number of LSA 8. Checksum Sum 0x02CAB4
Flood list length 0
10

R1
R1#sh ipv6 ospf
Event-log enabled, Maximum number of events: 1000, Mode:
cyclic
Router is not originating router-LSAs with maximum metric
Initial SPF schedule delay 5000 msecs
Minimum hold time between two consecutive SPFs 10000 msecs
Maximum wait time between two consecutive SPFs 10000 msecs
Minimum LSA interval 5 secs
Minimum LSA arrival 1000 msecs
LSA group pacing timer 240 secs
Interface flood pacing timer 33 msecs
Retransmission pacing timer 66 msecs
Area BACKBONE(0)
Number of LSA 8. Checksum Sum 0x03F283
Flood list length 0
107

R3
R3#sh ipv6 ospf
Event-log enabled, Maximum number of events: 1000, Mode:
cyclic
Router is not originating router-LSAs with maximum metric
Initial SPF schedule delay 5000 msecs
Minimum hold time between two consecutive SPFs 10000 msecs
Maximum wait time between two consecutive SPFs 10000
msecs
Minimum LSA interval 5 secs
Minimum LSA arrival 1000 msecs
LSA group pacing timer 240 secs
Interface flood pacing timer 33 msecs
Retransmission pacing timer 66 msecs
Area 1
Number of LSA 8. Checksum Sum 0x02CAB4
Flood list length 0
108

Area 0
R2#sh ipv6 ospf data
OSPFv3 Router with ID (172.16.1.2) (Process ID 1)
Router Link States (Area 0)
ADV Router Age Seq# Fragment ID Link count Bits
172.16.1.1 968 0x80000002 0 1 None
172.16.1.2 967 0x80000002 0 1 B
Inter Area Prefix Link States (Area 0)
ADV Router Age Seq# Prefix
172.16.1.2 963 0x80000001 2001:DB8:172:17::2/127
Inter Area Router Link States (Area 0)
ADV Router Age Seq# Link ID Dest RtrID
172.16.1.2 814 0x80000001 2886729987 172.16.1.3
Link (Type-8) Link States (Area 0)
ADV Router Age Seq# Link ID Interface
172.16.1.1 967 0x80000002 6 Se1/0
172.16.1.2 964 0x80000002 6 Se1/0
Intra Area Prefix Link States (Area 0)
ADV Router Age Seq# Link ID Ref-lstype Ref-LSID
172.16.1.1 968 0x80000002 0 0x2001 0
172.16.1.2 967 0x80000002 0 0x2001 0
109

R2 (continued..)
Router Link States (Area 1)
ADV Router Age Seq# Fragment ID Link count Bits
172.16.1.2 928 0x80000002 0 1 B
172.16.1.3 820 0x80000003 0 1 E
Net Link States (Area 1)
ADV Router Age Seq# Link ID Rtr count
172.16.1.3 929 0x80000001 2 2
Inter Area Prefix Link States (Area 1)
172.16.1.2 963 0x80000001 2001:DB8:172:16::1/128
172.16.1.2 963 0x80000001 2001:DB8:172:17::/127
172.16.1.2 963 0x80000001 2001:DB8:172:16::2/128
Link (Type-8) Link States (Area 1)
ADV Router Age Seq# Link ID Interface
172.16.1.2 968 0x80000002 2 Et0/0
172.16.1.3 968 0x80000002 2 Et0/0
Intra Area Prefix Link States (Area 1)
ADV Router Age Seq# Link ID Ref-lstype Ref-LSID
172.16.1.3 929 0x80000001 2048 0x2002 2
Type-5 AS External Link States
172.16.1.3 819 0x80000001 2001:DB8:35:1::16/127
172.16.1.3 819 0x80000001 2001:DB8:36:1::16/127
172.16.1.3 819 0x80000001 2001:DB8:172:16::3/128
110

R5 & R6
R2#deb ipv6 ospf hello
OSPFv3 hello events debugging is on
19:02:20.240: OSPFv3: Send hello to FF02::5 area 1 on Ethernet0/0 from FE80::A8BB:CCFF:FE00:5200
interface ID 2
19:02:27.100: OSPFv3: Rcv hello from 172.16.1.3 area 1 from Ethernet0/0 FE80::A8BB:CCFF:FE00:5300
interface ID 2
19:02:27.100: OSPFv3: End of hello processing
19:02:28.840: OSPFv3: Send hello to FF02::5 area 0 on Serial1/0 from FE80::A8BB:CCFF:FE00:5200 interface
ID 6
19:02:28.920: OSPFv3: Rcv hello from 172.16.1.1 area 0 from Serial1/0 FE80::4AFF:FEA2:851 interface ID 6
19:02:28.920: OSPFv3: End of hello processing
R2#undeb all
All possible debugging has been turned off
Lab 7 OSPFv3: Debugs
111

Lab 8 BGPv6: iBGP
•  ISP is already receiving IPv6 Internet prefixes on R1, Since there is a
requirement of providing IPv6 Internet connectivity to Site 2 as well so
ISP has to extend BGP all the way upto site 2 for IPv6 by enabling
iBGP in their network and eBGP with Site 2. Note, this BGP extension
is already present in IPv4 network
•  iBGP peering in the ISP network is following IPv4 BGP method which
is to source the update from loopback and peer between loopbacks
•  ISP is following the similar method that they used in IPv4 BGP which is
to make R2 as an RR for R1 and R3 and run iBGP between R2-R1
and R2-R3
114

Lab 8 BGPv6: iBGP
•  Advertise 2004:db8::1/128 from R1 under address-family ipv6
•  Redistribute static route for Site 1 into BGP so site 2 can learn about
this prefix
•  Set next-hop-self towards R2 or static routes won’t be installed in AS
109
•  Enable iBGP between R2-R1 and R2-R3 making R1 and R3 as route-
reflector clients for R2. Note, disable ipv4-unicast default peering so it
does not activate ipv4 peering by default when ipv6 peering is
configured
115

R# Area 0 Configs
R1 R1(config)#router bgp 109
R1(config-router)#no bgp default ipv4-unicast
R1(config-router)#address-family ipv6
R1(config-router-af)#nei 2001:db8:172:16::2 remote 109
R1(config-router-af)#nei 2001:db8:172:16::2 update loop 0
R1(config-router-af)#redistribute static
R1(config-router-af)#neighbor 2001:db8:172:16::2 next-hop-self
R1(config-router-af)#network 2004:db8::1/128
R1(config-router-af)#end
Lab 8 BGPv6: iBGP Configs
116

R# Area 0 Configs
R2(config-router-af)#nei 2001:db8:172:16::1 route-reflector-client
R2(config-router-af)#nei 2001:db8:172:16::3 route-reflector-client
Lab 8 BGPv6: iBGP Configs
117

R2
R2#sh bgp ipv6 unicast sum
BGP router identifier 172.16.1.2, local AS number 109
BGP table version is 4, main routing table version 4
1 network entries using 172 bytes of memory
1 path entries using 88 bytes of memory
1/1 BGP path/bestpath attribute entries using 128 bytes of memory
1 BGP AS-PATH entries using 24 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 412 total bytes of memory
BGP activity 7/0 prefixes, 8/1 paths, scan interval 60 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
2001:DB8:172:16::1
4 109 100 98 4 0 0 0 1:26:26 2
2001:DB8:172:16::3
4 109 95 98 4 0 0 0 1:24:10 0
R2#
Lab 8 BGPv6: iBGP Verification
118

R2
R2#sh bgp ipv6 unicast
BGP table version is 4, local router ID is 172.16.1.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, x best-external, f RT-Filter, a additional-path
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*>i 2004:DB8::1/128
2001:DB8:172:16::1
0 100 0 i
*>i 2001:DB8:1:41::/64
2001:DB8:172:16::1
0 100 0 ?
119

R2
R2#sh bgp ipv6 unicast 2001:db8:1:41::/64
BGP routing table entry for 2001:DB8:1:41::/64, version 29
Paths: (1 available, best #1, table default)
Advertised to update-groups:
2
Refresh Epoch 2
Local, (Received from a RR-client)
2001:DB8:172:16::1 (metric 64) from 2001:DB8:172:16::1 (172.16.1.1)
Origin incomplete, metric 0, localpref 100, valid, internal, best
120

Lab 8 BGPv6: eBGP
•  ISP is now ready to provided end to end connectivity between
site 1 and Site 2 for ABC
•  You want to use the similar BGP policies and advertisement that
you have for iPv4.
•  Enable eBGP between R3 and R5 over link local address and
R3 and R6 over a global address over the tunnel interfaces.
Note, make sure to advertise Serial2/0 into OSPFv3 or site 2
routes will not get installed in AS 109
121

Lab 8 BGPv6: eBGP
•  Advertise prefixes that are assigned on the Ethernet segment of
R5 and R6 and aggregate 2001:db8:1:56::/64 and
2001:db8:1:57::/64 into one block
•  Make sure that H2 can reach IPv6 Internet. Note, in our case
2004:db8::1 represent IPv6 Internet
•  Verify that Site 2 can reach Site 1 by pinging H1 from H2.
122

R# Area 0 Configs
R5(config-router-af)#nei FE80::A01:2300%Tunnel0 remote 109
R5(config-router-af)#net 2001:db8:1:56::/64
R5(config-router-af)#aggregate-address 2001:db8:1:56::/63 summary-only
R3(config-router-af)#nei FE80::A01:2301%Tunnel0 remote 1
R3(config-router-af)#
Lab 8 BGPv6: eBGP Configs
123

R# Area 0 Configs
R6(config-router-af)#nei 2001:DB8:36:1::16 remote 109
R6(config-router-af)#aggregate-address 2001:db8:1:56::/63 summary-only
R3(config)#int s2/0
R3(config-if)#ip ospf 1 area 1
R3(config-if)#end
Lab 8 BGPv6: eBGP Configs
124

R3
R3#sh bgp ipv6 unicast sum | e 109
BGP table version is 26, main routing table version 26
3 network entries using 516 bytes of memory
5 path entries using 440 bytes of memory
4/3 BGP path/bestpath attribute entries using 512 bytes of memory
1 BGP rrinfo entries using 24 bytes of memory
1 BGP AS-PATH entries using 24 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 1516 total bytes of memory
BGP activity 15/6 prefixes, 31/18 paths, scan interval 60 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
2001:DB8:36:1::17
4 1 11 16 26 0 0 00:05:42 2
2001:DB8:172:16::2
FE80::A01:2301%Tunnel0
4 1 11 18 26 0 0 00:05:56 2
Lab 8 BGPv6: eBGP Verification
125

R3
R3#sh bgp ipv6 unicast
BGP table version is 27, local router ID is 172.16.1.3
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, x best-external, f RT-Filter, a additional-path
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*>i 2001:DB8:1:41::/64
2001:DB8:172:16::1
0 100 0 ?
* 2001:DB8:1:56::/63
2001:DB8:36:1::17
0 0 1 i
*> FE80::A01:2301 0 0 1 i
* 2001:DB8:1:88::/64
2001:DB8:36:1::17
0 0 1 i
*> FE80::A01:2301 0 0 1 i
*>i 2004:DB8::1/128 2001:DB8:172:16::1
0 100 0 i
R3#
126

R3
R3#sh bgp ipv6 uni 2001:db8:1:56::/63
BGP routing table entry for 2001:DB8:1:56::/63, version 22
Paths: (2 available, best #2, table default)
Advertised to update-groups:
1 3
Refresh Epoch 1
1, (aggregated by 1 10.1.1.6)
2001:DB8:36:1::17 (FE80::A8BB:CCFF:FE00:5600) from 2001:DB8:36:1::17 (10.1.1.6)
Origin IGP, metric 0, localpref 100, valid, external, atomic-aggregate
Refresh Epoch 1
1, (aggregated by 1 10.1.1.5)
FE80::A01:2301 (FE80::A01:2301) from FE80::A01:2301%Tunnel0 (10.1.1.5)
Origin IGP, metric 0, localpref 100, valid, external, atomic-aggregate, best
R3#
127

R3
H2#ping [H1 IPv6 Global Unicast Address]
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:41:A8BB:CCFF:FE00:5700, timeout is 2 seconds:
!!!!!
H2#
128

Configs
R# Configs
R1 ipv6 unicast-routing!
ipv6 cef!
!!
interface Loopback0!
ip address 172.16.1.1 255.255.255.255!
ipv6 address 2001:DB8:172:16::1/128!
ipv6 ospf 1 area 0!
!!
ip address 1.1.1.1 255.255.255.255!
ipv6 address 2004:DB8::1/128!
!!
interface Serial0/0!
ip address 10.1.37.0 255.255.255.254!
ipv6 address 2001:DB8:14:1::14/127!
!!
ip address 172.17.12.0 255.255.255.254!
ipv6 address 2001:DB8:172:17::/127!
ipv6 ospf 1 area 0!
! !
router ospf 1!
passive-interface Serial0/0!
network 10.1.37.0 0.0.0.1 area 0!
network 172.16.1.1 0.0.0.0 area 0!
network 172.17.12.0 0.0.0.1 area 0 !
router bgp 109!
bgp log-neighbor-changes!
neighbor 2001:DB8:172:16::2 remote-as 109!
neighbor 2001:DB8:172:16::2 update-source Loopback0!
neighbor 172.16.1.2 remote-as 109!
neighbor 172.16.1.2 update-source Loopback0!
!!
address-family ipv4!
network 1.1.1.1 mask 255.255.255.255!
network 10.1.41.0 mask 255.255.255.0!
redistribute static!
no neighbor 2001:DB8:172:16::2 activate!
neighbor 172.16.1.2 activate!
exit-address-family!
!!
redistribute static!
network 2004:DB8::1/128!
neighbor 2001:DB8:172:16::2 activate!
neighbor 2001:DB8:172:16::2 next-hop-self!
!!
ip route 10.1.41.0 255.255.255.0 10.1.37.1!
!!
ipv6 route 2001:DB8:1:41::/64 2001:DB8:14:1::15!
ipv6 router ospf 1! 130

Configs
R# Configs
ipv6 cef!
!!
ip address 172.16.1.2 255.255.255.255!
ipv6 address 2001:DB8:172:16::2/128!
ipv6 ospf 1 area 0!
!!
interface Ethernet0/0!
ip address 172.17.23.0 255.255.255.254!
ipv6 address 2001:DB8:172:17::2/127!
ipv6 ospf 1 area 1!
!!
ip address 172.17.12.1 255.255.255.254!
ipv6 address 2001:DB8:172:17::1/127!
ipv6 ospf 1 area 0!
!!
router ospf 1!
network 172.16.1.2 0.0.0.0 area 0!
network 172.17.12.0 0.0.0.1 area 0!
network 172.17.23.0 0.0.0.1 area 1!
!!
!
router bgp 109!
!!
neighbor 172.16.1.1 route-reflector-client!
neighbor 172.16.1.3 route-reflector-client!
!!
131

Configs
R# Configs
R2 !!
neighbor 2001:DB8:172:16::1 route-reflector-client!
neighbor 2001:DB8:172:16::3 route-reflector-client!
!!
ipv6 router ospf 1!
!
132

Configs
R# Configs
R3 interface Loopback0!
ip address 172.16.1.3 255.255.255.255!
ipv6 address 2001:DB8:172:16::3/128!
!!
interface Tunnel0!
no ip address!
ipv6 address 2001:DB8:35:1::16/127!
tunnel source Serial1/0!
tunnel mode ipv6ip!
tunnel destination 10.1.35.1!
!!
interface Tunnel1!
no ip address!
ipv6 address 2001:DB8:36:1::16/127!
!!
ip address 172.17.23.1 255.255.255.254!
ipv6 address 2001:DB8:172:17::3/127!
ipv6 ospf 1 area 1!
!!
ip address 10.1.35.0 255.255.255.254!
!!
ip address 10.1.36.0 255.255.255.254!
ip ospf 1 area 1!
!!
router ospf 1!
redistribute connected subnets!
network 172.17.23.0 0.0.0.1 area 1!
!!
router bgp 109!
neighbor FE80::A01:2301%Tunnel0 remote-as 1!
!!
!
133

Configs
R# Configs
R3 !!
network 172.16.0.0!
network 172.17.0.0!
no neighbor FE80::A01:2301%Tunnel0 activate!
auto-summary!
!!
neighbor FE80::A01:2301%Tunnel0 activate!
!!
ipv6 router ospf 1!
redistribute connected!
134

Configs
R# Configs
ipv6 cef!
!!
ip address 10.1.1.4 255.255.255.255!
ipv6 address 2001:DB8:1:1::4/128!
!!
ip address 10.1.41.4 255.255.255.0!
ipv6 address 2001:DB8:1:41::4/64!
ipv6 address FD01:DB8:1:41::/64 eui-64!
ipv6 nd ra interval 30!
! !
ip address 10.1.37.1 255.255.255.254!
ipv6 address 2001:DB8:14:1::15/127!
ip route 0.0.0.0 0.0.0.0 10.1.37.0!
!!
ipv6 route ::/0 Serial1/0 FE80::4AFF:FEA2:851!
135

Configs
R# Configs
ip address 10.1.1.5 255.255.255.255!
ipv6 address 2001:DB8:1:1::5/128!
ipv6 eigrp 1!
!!
interface Tunnel0!
no ip address!
ipv6 address 2001:DB8:35:1::17/127!
tunnel mode ipv6ip!
!!
ip address 10.1.57.5 255.255.255.0 secondary!
ip address 10.1.58.5 255.255.255.0 secondary!
ip address 10.1.56.5 255.255.255.0!
no ip split-horizon eigrp 1!
standby version 2!
standby 1 ip 10.1.56.1!
standby 1 ipv6 autoconfig!
ipv6 address 2001:DB8:1:56::5/64!
ipv6 address 2001:DB8:1:57::5/64!
ipv6 address 2001:DB8:1:88::5/64!
ipv6 nd router-preference High!
ipv6 eigrp 1!
!!
ip address 10.1.35.1 255.255.255.254!
!!
router eigrp 1!
network 10.1.1.5 0.0.0.0!
network 10.1.35.0 0.0.0.1!
network 10.1.56.0 0.0.0.255!
network 10.1.57.0 0.0.0.255!
network 10.1.58.0 0.0.0.255!
!!
router bgp 1!
neighbor FE80::A01:2300%Tunnel0 remote-as 109!
!
136

Configs
R# Configs
R5 !!
network 10.1.56.0 mask 255.255.255.0!
network 10.1.57.0 mask 255.255.255.0!
network 10.1.58.0 mask 255.255.255.0!
aggregate-address 10.1.56.0 255.255.254.0 summary-only!
no neighbor FE80::A01:2300%Tunnel0 activate!
!!
network 2001:DB8:1:56::/64!
network 2001:DB8:1:57::/64!
network 2001:DB8:1:88::/64!
aggregate-address 2001:DB8:1:56::/63 summary-only!
neighbor FE80::A01:2300%Tunnel0 activate!
!!
ipv6 router eigrp 1!
137

Configs
R# Configs
ip address 10.1.1.6 255.255.255.255!
ipv6 address 2001:DB8:1:1::6/128!
ipv6 eigrp 1!
!!
interface Tunnel0!
no ip address!
ipv6 address 2001:DB8:36:1::17/127!
!!
ip address 10.1.57.6 255.255.255.0
secondary!
ip address 10.1.58.6 255.255.255.0
secondary!
ip address 10.1.56.6 255.255.255.0!
no ip split-horizon eigrp 1!
standby version 2!
standby 1 ip 10.1.56.1!
standby 1 ipv6 autoconfig!
standby 1 priority 105!
standby 1 preempt!
ipv6 address 2001:DB8:1:56::6/64!
ipv6 address 2001:DB8:1:57::6/64!
ipv6 address 2001:DB8:1:88::6/64!
ipv6 eigrp 1!
!!
ip address 10.1.36.1 255.255.255.254!
!!
router eigrp 1!
network 10.1.1.6 0.0.0.0!
network 10.1.36.0 0.0.0.1!
network 10.1.56.0 0.0.0.255!
network 10.1.57.0 0.0.0.255!
network 10.1.58.0 0.0.0.255!
!!
router bgp 1!
!!
!
138

Configs
R# Configs
R6 address-family ipv4!
network 10.1.56.0 mask 255.255.255.0!
network 10.1.57.0 mask 255.255.255.0!
network 10.1.58.0 mask 255.255.255.0!
aggregate-address 10.1.56.0 255.255.254.0 summary-only!
!!
network 2001:DB8:1:56::/64!
network 2001:DB8:1:57::/64!
network 2001:DB8:1:88::/64!
aggregate-address 2001:DB8:1:56::/63 summary-only!
! !
ipv6 router eigrp 1!
139

Configs
R# Configs
H1 !
ip address 10.1.41.1 255.255.255.0!
ipv6 address autoconfig!
ipv6 enable!
!!
ip route 0.0.0.0 0.0.0.0 10.1.41.4!
!
H2 interface Ethernet0/0!
ip address 10.1.56.2 255.255.255.0!
ipv6 address autoconfig!
ipv6 enable!
!!
ip route 0.0.0.0 0.0.0.0 10.1.56.1!
!
140

Hands-on Experience with IPv6 Routing and Switching

Hands-on Experience with IPv6 Routing and Switching

More Related Content

What's hot (17)

Similar to Hands-on Experience with IPv6 Routing and Switching (20)

More from Cisco Canada (20)

Recently uploaded (20)

Hands-on Experience with IPv6 Routing and Switching