Ipv6 Hands On Lab Hritter

Toronto, Canada
May 30, 2013
IPv6 Hands-on Lab

Faraz Shamim, Technical Leader
Harold Ritter, Technical Leader
2012
2011 Cisco and/or its affiliates. All rights reserved.
Cisco Connect
Prerequisites: Session Abstract

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.
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
Optional Labs(6PE, 6VPE & IPv6 Multicasting)
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
Lab Topology
Lab 1 : IPv6
Addressing &
Stateless Address
Auto Configuration
(SLAAC)
Cisco Connect
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
Lab 1 IPv6 Stateless Auto-Configuration (SLAAC)

Your plan is to test the plug and play behaviour 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 R4s link local and Unique local IPv6 address from H1
Lab 1: IPv6 Addressing & SLAAC
Lab 1 IPv6 Unique Local & SLAAC: Configs

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: Verification

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
Global unicast address(es): 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

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 SLAAC: Debugs

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
ICMPv6-ND:
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 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
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
Lab 1b: IPv6 Global Unicast address & SLAAC
Lab 1 IPv6 Global Unicast address & SLAAC: Configs

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

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

R4 Loopback 0
R4 Ethernet0/0
R4#sh ipv6 int lo 0

Loopback0 is up, line protocol is up
IPv6 is enabled, link-local address is
FE80::A8BB:CCFF:FE00:5900
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#
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#

R5 Loopback 0
R5 Ethernet0/0
R5#sh ipv6 int lo 0

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#
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

R6 Loopback 0
R6 Ethernet0/0
R6#sh ipv6 int lo 0

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#
R6#sh ipv6 int e0/0

IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5B00
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
Lab 1 IPv6 SLAAC: Verification

H1 Ethernet0/0
H2 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#
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]
[EUI/CAL/PRE]
[EUI/CAL/PRE]
FF02::1
FF02::1:FF00:5D00
MTU is 1500 bytes
Default router is FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0
H2#

R#
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
!!!!!
H2#ping 2001:db8:1:58::5
!!!!!
H2#ping 2001:db8:1:56::6
!!!!!
H2#ping 2001:db8:1:57::6
!!!!!
H2#ping 2001:db8:1:58::6
!!!!!
H2#
Lab 1 IPv6 SLAAC: Verification

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

R5 &
R6
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
ICMPv6-ND:
ICMPv6-ND:
ICMPv6-ND:
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
ICMPv6-ND:
ICMPv6-ND:
ICMPv6-ND:
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#
R6#
ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0
H2#

H2 & H1
H2#deb ipv6 nd
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
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#
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#
Lab 2 : IPv6 Neighbor

Discovery
Cisco Connect
26
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
Lab 2 IPv6 Neighbor discovery: Configs

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

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: Debugs

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 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 R6s Ethernet address of 2001:db8:1:56::6 from R5 to see how NS and NA
takes place between them

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

R4
R6#sh ipv6 int
IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5B00
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]

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:
*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

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

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
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)
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

R#
Configs
R5
R5(config-if)#ipv6 nd prefix 2001:db8:1:58::/64 50 0
R5(config-if)#end
R6
R6(config-if)#end

H2
H2#sh ipv6 int e0/0
FF02::1
FF02::1:FF00:5D00
MTU is 1500 bytes
[EUI/CAL/PRE]
[EUI/CAL/PRE]
[EUI/CAL]
[EUI/CAL/PRE]

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

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

H2
H2#sh ipv6 int e0/0
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:5B00 on Ethernet0/0
H2#

H2
H2#deb ipv6 nd
H2#
*Jan 31 04:47:34.487: ICMPv6-ND: Invalid prefix 2001:DB8:1:58::/64
H2#
Lab 2 IPv6 Neighbor discovery: Cleanup Configs

R#
Configs
R5
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
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 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)

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

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
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
Lab 3 : HSRPv6
Cisco Connect
48
Lab 3: HSRPv6
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
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
Lab 3 HSRPv6: Configs

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: Verification

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#

R5 & R6
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)
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)

R5 & R6
H2#sh ipv6 route ::/0
Routing paths:
FE80::5:73FF:FEA0:1, Ethernet0/0
H2#
Lab 3 HSRPv6: Debugs

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, 2001:DB8:1:56:A8BB:CCFF:FE00:5D00
H2#
Lab 4 : EIGRPv6
Cisco Connect
56
Lab 4: EIGRPv6
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
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
Lab 4 EIGRPv6: Configs

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: Verification

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
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
Interfaces:
Loopback0
Ethernet0/0
Redistribution:
None

R5 & R6
R5#sh ipv6 eigrp nei
EIGRP-IPv6 Neighbors for AS(1)
H Address
Interface
0 Link-local address: Et0/0
R5#
R6#sh ipv6 eigrp nei
EIGRP-IPv6 Neighbors for AS(1)
H Address
Interface
0 Link-local address: Et0/0
R6#
Hold Uptime SRTT RTO Q Seq

(sec)
(ms)
Cnt Num
10 00:15:15 3
100 0 3
Hold Uptime SRTT RTO Q Seq

(sec)
(ms)
Cnt Num
11 00:17:11 4
100 0 3

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#
Lab 4 EIGRPv6: Debugs

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 5 : IPv6 Static

Routing
Cisco Connect
64
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)
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
Lab 5: IPv6 Static Routing
Lab 5 IPv6 Static routing: Configs

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 FE80::4AFF:FEA2:851
R1(config)#end
Lab 5 IPv6 Static routing: Verification

R4
R4#sh ipv6 route ::/0
Routing paths:
FE80::4AFF:FEA2:851, Serial1/0
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
Configure a static route 2001:db8:1:41::/64 on R1 with next-hop of R4s 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
Lab 5 IPv6 Static routing: Configs

R#
Configs
R1
R1(config)#ipv6 route 2001:db8:1:41::/64 2001:db8:14:1::15

R1(config)#end
Note, no interface needs to be specified when the next hop is global unicast
address
Lab 5 IPv6 Static routing: Verification

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 6 : IPv6 Manual

Tunnels
Cisco Connect
72
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
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
Lab 6: IPv6 Manual Tunnels
Lab 6 IPv6 Manual Tunnels: Configs

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
R3(config-if)#tun mode ipv6ip
R5(config-if)#end
Lab 6 IPv6 Manual Tunnels: Verification

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#

R3
R3#ping 2001:db8:35:1::17
!!!!!
R3#
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
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
Lab 6 IPv6 Manual Tunnels: Configs

R#
Configs
R6
R6(config-if)#tun mode gre ip
R6(config-if)#end
R3
R3(config-if)#tun mode gre ip
R3(config-if)#end

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#

R3
R3#ping 2001:db8:36:1::17
!!!!!
R3#
Lab 7 : OSPFv3
Cisco Connect
82
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
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
Redistribute R2s loopback into OSPFv3
Ping ipv6 Loopback 0 of R3 from the loopback 0 of R1
Compare the difference between OSPFv2 and OSPFv3 LSAs
Lab 7: OSPFv3
Lab 7 OSPFv3: Configs

R#
Area 1 Configs
R3
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
R2(config-if)#end
Lab 7 OSPFv3: Configs

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

R2
R2#sh ipv6 ospf nei
OSPFv3 Router with ID (172.16.1.2) (Process ID 1)

Neighbor ID
172.16.1.1
172.16.1.3
R2#
Pri State
0 FULL/ 1 FULL/DR
Dead Time Interface ID Interface

00:00:31
6
Serial1/0
00:00:36
2
Ethernet0/0
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
Se1/0
1
0
Et0/0
1
1
R2#
Intf ID
6
2
Cost State Nbrs F/C

64 P2P 1/1
10 BDR 1/1

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

R1
R1#sh ipv6 ospf
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

R3
R3#sh ipv6 ospf
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

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

ADV Router
172.16.1.1
172.16.1.2
Age
968
967
Seq#
Link ID
0x80000002 0
0x80000002 0
Ref-lstype Ref-LSID
0x2001
0
0x2001
0

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

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#un all
All possible debugging has been turned off
Lab 8 : BGPv6
Cisco Connect
94
Lab 8: BGPv6
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
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 wont 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
Lab 8 BGPv6: iBGP Configs

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
R3

Lab 8 BGPv6: iBGP Configs

R#
Area 0 Configs
R2

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 Verification

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

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?
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
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
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.
Lab 8 BGPv6: eBGP Configs

R#
Area 0 Configs
R5
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

R3(config-router-af)#nei FE80::A01:2301%Tunnel0 remote 1
R3(config-router-af)#
Lab 8 BGPv6: eBGP Configs

R#
Area 0 Configs
R6
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

R3(config)#int s2/0
R3(config-if)#ip ospf 1 area 1
R3(config-if)#end
Lab 8 BGPv6: eBGP Verification

R3
R3#sh bgp ipv6 unicast sum | e 109
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
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
R3#

R3
Network
Next Hop
*>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
01i
*>
FE80::A01:2301
0
01i
* 2001:DB8:1:88::/64
2001:DB8:36:1::17
0
01i
*>
FE80::A01:2301
0
01i
*>i 2004:DB8::1/128 2001:DB8:172:16::1
0 100
0i
R3#

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#
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#
Lab key
Cisco Connect
107
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
!
interface Loopback1
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
!
interface Serial1/0
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
!
address-family ipv6
redistribute static
network 2004:DB8::1/128
neighbor 2001:DB8:172:16::2 activate
neighbor 2001:DB8:172:16::2 next-hop-self
exit-address-family
!
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
Configs
R#
Configs
R2
ipv6 cef
!
interface Loopback0
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
!
interface Serial1/0
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

!
address-family ipv4
neighbor 172.16.1.1 route-reflector-client
exit-address-family
!
address-family ipv6
neighbor 2001:DB8:172:16::1 route-reflector-client
neighbor 2001:DB8:172:16::3 route-reflector-client
exit-address-family
!
ipv6 router ospf 1
Configs
Configs
R3
R#
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
!
interface Serial1/0
ip address 10.1.35.0 255.255.255.254
!
interface Serial2/0
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
!
address-family ipv4
network 172.16.0.0
network 172.17.0.0
no neighbor FE80::A01:2301%Tunnel0 activate
auto-summary
exit-address-family
!
address-family ipv6
neighbor FE80::A01:2301%Tunnel0 activate
exit-address-family
!
ipv6 router ospf 1
redistribute connected
Configs
R#
Configs
R4
ipv6 cef
!
interface Loopback0
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
!
interface Serial1/0
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
Configs
R#
Configs
R5
interface Loopback0
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
!
interface Serial1/0
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
!
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
no neighbor FE80::A01:2300%Tunnel0 activate
exit-address-family
!
address-family ipv6
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
exit-address-family
!
ipv6 router eigrp 1
Configs
R#
Configs
R6
interface Loopback0
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
!
interface Serial1/0
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
!
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
exit-address-family
!
address-family ipv6
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
exit-address-family
!
ipv6 router eigrp 1
Configs
R#
H1
H2
Configs
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
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
Optional Labs
Cisco Connect
115
6PE Lab
Cisco Connect
116
6PE Lab Agenda
Enabling OSPFv3 as a PE-CE protocol on a non vrf based interface

Enabling BGPv6 as a PE-CE protocol on a non vrf based interface
Enabling 6PE
6PE Instructions
MPLS/LDP is pre configured in AS 109 between R1-R2-R3
OSPFv2 is pre-configured between R1-R2-R3
OSPFv2 is pre-configured between R1-R4(E0/0-E0/0) as a PE-CE
protocol (over a VRF interface)
BGP for IPv4 is pre-configured between R3-R5(E2/0-E1/0) as a PECE protocol (over a VRF interface)
IPv6 address are pre-configured between R1-R4(E1/0-E1/0) & R3R5(E0/0-E0/0)
Note, a separate interface is used for 6PE. This is usually a case
where ipv4 internet routes or a default routes are received on that
interface. IPv6 can be enabled on that interface to receive ipv6 internet
prefixes and that will be a dual stack environment but in lab, we are
only using that interface for IPv6
6PE Lab: Enabling OSPFv3 on PE-CE link

Configure OSPFv3 between R1-R4
Why are we configuring ospfv3 on a separate interface?
R#
OSPFv3
R1
ipv6 ospf 1 area 0
!
router ospfv3 1
router-id 10.1.0.1
R4
interface Loopback0
ipv6 ospf 1 area 0
!
ipv6 ospf 1 area 0
!
router ospfv3 1
router-id 10.0.0.1

Configure mutual redistribution between OSPFv3 and BGP
In which routing table (global or VRF) do you see the V6 routes after the
redistribution on R1
R#
OSPFv3 and Redistribution
R1
router ospfv3 1
address-family ipv6
redistribute bgp 109
!
router bgp 109
address-family ipv6
redistribute ospf 1

Verify that the peers have been established and that R4 loopback address is received and
seen in BGP on R1
R#
BGPv6
R1
R1#sh ipv6 ospf nei

Neighbor ID
10.0.0.1
Pri State
Dead Time Interface ID
1
FULL/BDR 00:00:38 6
Interface
Ethernet1/0
R1#sh ipv6 route 2001:db8::4

Routing entry for 2001:DB8::4/128
Known via "ospf 1", distance 110, metric 10, type intra area, bgp 109
Routing paths:
FE80::A8BB:CCFF:FE00:5401, Ethernet1/0
Network
Next Hop
*> 2001:DB8::4/128 ::
R1#

10
32768 ?

Answers
We are getting global IPv4 and IPv6 routes on a separate interface
and l3vpn routes over another interface.
6PE installs the routes in the global routing table
Note that although OSPFv3 is enabled under the interface itself, the
redistribution is enabled under the ospfv3 router process
As 6PE uses the global routing table, configuring OSPFv3 in the
context of 6PE does not require anything special
6PE Lab: Enabling BGPv6 as a PE-CE protocol

Configure BGPv6 between R3-R5
Advertise R5 loopback address in BGPv6
Why dont we need to configure redistribution?
R#
BGPv6 and Redistribution
R3
router bgp 109

!
address-family ipv6
neighbor 2001:db8:1:2::5 remote-as 2
R5
router bgp 2
!
address-family ipv6
network 2001:db8:1:5::3/128

Verify that the peers has been established by using appropriate show commands
Verify that R5 loopback address is seen on R3
Can we configure the PE-CE BGP session over a IPv4 transport in a 6PE scenario?
R#
BGPv6
R3
R3#sh bgp ipv6 unicast summ

Neighbor
V
2001:DB8:1:2::5 4
2
14
14
5
0 0
00:08:33
1
R3#
Network
Next Hop
*> 2001:DB8:1:5::3/128
2001:DB8:1:2::5
0
0
2i
R3#

Redistribution is not required for BGP routes received from the CE
as the routes will be propagated automatically to the 6PE peers via
separate iBGP session exclusively for 6PE
The PE-CE BGP session in 6PE is just like any other IPv6 eBGP
session. It could be configured over an IPv4 or IPv6 transport. The
normal restrictions would apply. For example, a route-map would be
required to change the BGP next hop.
6PE Lab: Enabling 6PE

Configure iBGP between R1-R2 (RR) & R2-R3
IPv4 BGP configs are there for comparison purpose
What is the purpose of the send-label keyword in 6PE
R#
*BGPv4
BGPv6
R1&
R3
router bgp 109

neighbor 10.1.0.0 update-source L0
address-family ipv4
neighbor 10.1.0.0 act
router bgp 109

address-family ipv6
neighbor 10.1.0.0 send-label
R2
router bgp 109

address-family ipv4
router bgp 109

address-family ipv6

Verify that the peers has been established by using appropriate show commands
*Only R2 (RR) peering is shown as it covers all peering
Why dont we have ipv6 neighbors?
R#
BGPv6
R2
R2#sh bgp ipv6 unicast summ

BGP router identifier 10.1.0.0, local AS number 109
Neighbor
10.1.0.1
10.1.3.1
R2#
V
4
4

109
15
15
1 0 0 00:10:04
0
109
13
11
1 0 0 00:08:38
0
Verify that R5 loopback is received on R1 and what label is advertised for it

What is the next hop for it and why?
Look at R5 loopback address in cefv6
Why do we see 2 labels for this ipv6 prefix?
R#
BGPv6
R1
R1#sh bgp ipv6 unicast label

Network
Next Hop
In label/Out label
2001:DB8::4/128 ::
16/nolabel
2001:DB8:1:5::3/128
::FFFF:10.1.3.1 nolabel/17
R1#sh ip cef 10.1.3.1
10.1.3.1/32
nexthop 10.1.0.2 Serial2/0 label 17
R1#sh ipv6 cef 2001:db8:1:5::3
2001:DB8:1:5::3/128
nexthop 10.1.0.2 Serial2/0 label 17 17
6PE Lab: Enabling 6PE Answers

6PE requires configuring the BGP session over an IPv4 transport as
the core is not IPv6 enabled
This is done by activating a neighbor with an IPv4 peer address
under address-family ipv6
The send-label statement under address-family ipv6 is really what
enables 6PE
6PE uses an IGP label to get the ipv6 packet from the ingress to the
egress PE. It is the LDP label learnt for the BGP next hop (IPv4
address).
It also uses a service label on the egress PE to forward the packet
through the proper egress interface. The service label is learnt via
BGP as a result of the send-label keyword.
6PE Lab: Enabling BGPv6 Answers

The BGP next hop for R5 loopback address is actually R3 loopback
IPv4 address. It is displayed as an IPv4 mapped IPv6 address. The
first 80 bits are all zero followed by 0xFFFF and then the IPv4 next
hop address of the egress PE in dotted decimal format
Redistribution is not required for BGP routes received from the CE
as the routes will be propagated automatically to the 6PE peers.
Lab Key
Cisco Connect
132
6PE Lab: Configs

R#
Configs
R1
ipv6 cef
!
interface Loopback0
ip address 10.1.0.1 255.255.255.255
!
ipv6 address 2001:DB8:1:1::1/64
ipv6 ospf 1 area 0
!
interface Serial2/0
ip address 10.1.0.3 255.255.255.254
mpls ip
!
router ospfv3 1
!
address-family ipv6 unicast
redistribute bgp 109
exit-address-family
!
router ospf 1
network 0.0.0.0 255.255.255.255 area 0
!
router bgp 109
no bgp default ipv4-unicast
!
address-family ipv6
redistribute ospf 1
exit-address-family
6PE Lab: Configs

R#
Configs
R2
interface Loopback0
ip address 10.1.0.0 255.255.255.255
!
ip address 10.1.0.4 255.255.255.254
mpls ip
!
interface Serial1/0
ip address 10.1.0.2 255.255.255.254
mpls ip
!
router ospf 1
nerwork 0.0.0.0 255.255.255.255 area 0
!
router bgp 109
!
address-family ipv6
neighbor 10.1.0.1 route-reflection-client
6PE Lab: Configs

R#
Configs
R3
ipv6 cef
!
interface Loopback0
ip address 10.1.3.1 255.255.255.255
!
no ip address
ipv6 address 2001:DB8:1:2::3/64
!
ip address 10.1.0.5 255.255.255.254
mpls ip
!
router ospf 1
network 0.0.0.0 255.255.255.255 area 0
!
router bgp 109
!
address-family ipv6
exit-address-family
6PE Lab: Configs

R#
R4
Configs
!
interface Loopback0
ipv6 address 2001:db8::4/128
ipv6 oapf 1 area 0
!
ipv6 address 2001:DB8:1:1::1/64
ipv6 ospf 1 area 0
6PE Lab: Configs

R#
R5
Configs
ipv6 cef
!
interface Loopback0
ipv6 address 2001:DB8:1:5::3/128
!
ipv6 address 2001:DB8:1:2::5/64
!
router bgp 2
!
address-family ipv6
network 2001:DB8:1:5::3/128
exit-address-family
6VPE Lab
Cisco Connect
138
6VPE Lab Agenda

Enabling static a PE-CE protocol for IPv6
Enabling BGP as a PE-CE protocol for IPv6
Enabling 6VPE
6VPE Instructions
MPLS/LDP is pre configured in AS 109 between R1-R2-R3
OSPFv2 is pre-configured between R1-R2-R3
IPv6 address are pre-configured between R1-R4 & R3-R5
PE-CE protocol between R1-R4 is static for IPv4 and is
preconfigured
PE-CE protocol between R3-R5 is BGP for IPv4 and is
preconfigured
6VPE Lab: Enabling static a PE-CE protocol for

IPv6
Enable IPv6 VRF on R1
Configure static route between R1-R4
Redistribute static in BGP
R#
OSPFv3 and Redistribution
R1
vrf upgrade-cli multi-af-mode common-policies vrf 6vpe force

!
vrf definition 6vpe
address-family ipv6
!
ipv6 route vrf 6vpe 2001:db8::/64 201:db8:1:1::4
!
router bgp 109
address-family ipv6 vrf 6vpe
redistribute static
R4
ipv6 route ::/0 2001:db8:1:1::1

IPv6
Verify that static route is installed in the VRF and that it is present in BGP
What is the purpose of the vrf upgrade-cli command?
R#
BGPv6
R4
R4#sh ipv6 route ::/0

Backup from "static [2]"
Routing paths:
2001:DB8:1:1::1
R1
R1#sh ipv6 route vrf 6vpe | incl 2001:DB8::/64

S 2001:DB8::/64 [1/0]
R1#sh bgp vpnv6 unicast all | incl 2001:DB8::/64

*> 2001:DB8::/64 2001:DB8:1:1::4
0
32768 ?
R1#

IPv6 Answers
The vrf upgrade-cli command converts the IPv4 centric VRF CLI to
a multi address family VRF CLI. There are several option with this
command. For example, only one VRF can be converted into new
format at a time. force command will not prompt for the verification.
Common policies will keep the same policies as IPv4 vrf
Note that the VRF configuration as been slightly modified to
accommodate multiple address families
Static routes in the context of 6VPE are very similar to any other
static routes. They just need to be configured as part of the VRF
configuration on the PE
6VPE Lab: Enabling BGP as a PE-CE protocol for

IPv6
Enable IPv6 VRF on R3
Configure BGP between R3-R5
R#
Static and redistribution for V6
R3
vrf upgrade-cli multi-af-mode common-policies vrf 6vpe force

!
vrf definition 6vpe
address-family ipv6
!
router bgp 109
R5
router bgp 2
address-family ipv6
network 2001:db8:1:5::3/128
neighbor 2001:db8:1:2::3 activate

IPv6
Verify the BGP sessions are up and that the routes are advertised
R#
Static routes
R3
R3#sh bgp vpnv6 uni all summ | incl 2001

2001:DB8:1:2::5 4
2
57
59
0 00:48:33
R3#sh bgp vpnv6 uni all | incl 2001:DB8:1:5::3

*> 2001:DB8:1:5::3/128
R3#
R5
R5#sh bgp ipv6 uni summ | incl 2001

2001:DB8:1:2::3 4
109
61
59
R5#sh bgp ipv6 uni | incl 2001:DB8::/64
*> 2001:DB8::/64 2001:DB8:1:2::3
R5#
0 00:50:21
0 109 ?

IPv6 Answers
The BGP session on the PE is in the VRF context, where as it is a
simple BGP session on the CE
Note that just as for IPv4 BGP in a VRF context, the neighbor
address only needs to be configured under the appropriate addressfamily for the specific VRF
Just like any IPv6 BGP session, you can either use an IPv6 or IPv4
transport address when you configure the BGP session in the VRF
context
6VPE Lab: Enabling 6VPE

Configure iBGP between R1-R2 (RR) & R2-R3
Compare
difference between
IPv4 and IPv6 BGP
R#
*BGPv4
BGPv6
R1
router bgp 109
router bgp 109
*IPv4
BGP
configs
are
there
for 10.1.0.0
comparison
&
neighbor
remote-as 109purpose
R3

address-family vpnv4
neighbor 10.1.0.0 act

R2
router bgp 109

router bgp 109


Verify the BGP sessions are up on the RR and that the routes are
advertised
R#
Static routes
R2
R2#sh bgp vpnv6 uni all summ

Neighbor
10.1.0.1
10.1.3.1
V
4
4

109
72
71
3
0 0
01:00:42
1
109
68
66
3
0 0
00:57:40
1
R2#sh bgp vpnv6 uni all

Network
Next Hop
Route Distinguisher: 1:1
*>i 2001:DB8::/64 ::FFFF:10.1.0.1
*>i 2001:DB8:1:5::3/128
::FFFF:10.1.3.1

0
100
100
2i

Verify that routes are received and installed in the CEF table
R#
Static routes
R1
R1#sh bgp vpnv6 uni all

Network
Next Hop
Route Distinguisher: 1:1 (default for vrf 6vpe)
*> 2001:DB8::/64 2001:DB8:1:1::4
0
32768 ?
*>i 2001:DB8:1:5::3/128
::FFFF:10.1.3.1
0 100
02i
R1#sh ip cef 10.1.3.1
10.1.3.1/32
nexthop 10.1.0.2 Serial1/0 label 17
R1#sh ipv6 cef vrf 6vpe 2001:db8:1:5::3
2001:DB8:1:5::3/128
nexthop 10.1.0.2 Serial1/0 label 17 20
R1#
6VPE Lab: Enabling 6VPE Answers

Just like 6PE and L3VPN for IPv4, 6VPE uses a label stack to
forward traffic through the MPLS core.
The IGP label is learnt via LDP and correspond to the BGP next hop
(loopback address of the egress PE).
The service label is learnt via the VPNv6 session which is
configured between the two PE
Lab Key
Cisco Connect
152
6VPE Lab: Configs

R#
Configs
R1
vrf definition 6vpe

rd 1:1
route-target export 1:1
route-target import 1:1
!
address-family ipv6
exit-address-family
!
ipv6 cef
!
interface Loopback0
ip address 10.1.0.1 255.255.255.255
!
vrf forwarding 6vpe
ip address 10.1.1.1 255.55.255.0
ipv6 address 2001:DB8:1:1::1/64
!
interface Serial1/0
ip address 10.1.0.3 255.255.255.254
mpls ip
!
router ospf 1
network 0.0.0.0 255.255.255.255 area 0
!
router bgp 109
!
neighbor 10.1.0.0 send-community extended
exit-address-family
!
redistribute static
exit-address-family
6VPE Lab: Configs

R#
R2
Configs
interface Loopback0
ip address 10.1.0.0 255.255.255.255
!
ip address 10.1.0.4 255.255.255.254
mpls ip
!
interface Serial1/0
ip address 10.1.0.2 255.255.255.254
mpls ip
!
router ospf 1
nerwork 0.0.0.0 255.255.255.255 area 0
!
router bgp 109
!
6VPE Lab: Configs

R#
Configs
R3
vrf definition 6vpe

rd 1:1
route-target export 1:1
route-target import 1:1
!
address-family ipv6
exit-address-family
!
ipv6 cef
!
interface Loopback0
ip address 10.1.3.1 255.255.255.255
!
vrf forwarding 6vpe
ip address 10.1.1.2 255.255.255.0
ipv6 address 2001:DB8:1:2::3/64
!
ip address 10.1.0.5 255.255.255.254
mpls ip
!
router ospf 1
network 0.0.0.0 255.255.255.255 area 0
!
router bgp 109
!
neighbor 10.1.0.0 send-community extended
exit-address-family
!
exit-address-family
6VPE Lab: Configs

R#
R4
Configs
ipv6 cef
!
ipv6 address 2001:DB8:1:1::4/64
!
ipv6 address 2001:DB8::/64 eui-64
!
ipv6 route ::/0 2001:DB8:1:1::1
6VPE Lab: Configs

R#
R5
Configs
ipv6 cef
!
interface Loopback0
ipv6 address 2001:DB8:1:5::3/128
!
ipv6 address 2001:DB8:1:2::5/64
!
router bgp 2
!
address-family ipv6
network 2001:DB8:1:5::3/128
exit-address-family
IPv6 Multicast Lab
Cisco Connect
158
IPv6 Multicast Lab Agenda

IPv6 Multicast with static RP
IPv6 Multicast with Embedded RP
IPv6 Multicast Instructions

OSPFv2 is enabled and preconfigured on all the devices
IPv4 multicasting is pre-configured on all the devices with PIM
R2 is RP for IPv6 Multicast static RP lab and R1 is the RP for IPv6
Multicast Embedded RP lab
OSPFv3 is enabled and pre-configured on all the devices
All the devices are in area 0
Multicast Lab: IPv6 Multicast with static RP

Enable IPv6 Multicast routing on R1, R2 and R3
Configure static RP on R1, R2 and R3
Configure MLD Join on Receiver for group FF1E::1 to simulate a receiver
R#
Multicast configuration
R1
ipv6 multicast-routing
!
ipv6 pim rp-address 2001:db8:1::
R2
!
R3
!
Receiver
ipv6 mld join-group FF1E::1

Verify that RP is properly configured with R2 loopback address
Verify that MLD join has been received from R5 on R3
Do we need to configure IGMP for IPv6 multicast?
R#
R3
R3#sh ipv6 pim group-map ff1E::1

IP PIM Group Mapping Table
(* indicates group mappings being used)
FF00::/8*
SM, RP: 2001:DB8:1::
RPF: Et1/0,FE80::A8BB:CCFF:FE00:5200
Info source: Static
Uptime: 00:30:53, Groups: 1
R3#sh ipv6 mld groups
MLD Connected Group Membership
Group Address
Interface
FF1E::1
Ethernet0/0
R3#
Uptime Expires
00:28:50 00:03:22

Verify that PIM neighbor relationships are up (R2)
Verify that the PIM join has been received by the RP (R2)
Why do we see tunnel4 as RPF interface?
R#
R2
R2#sh ipv6 pim nei

PIM Neighbor Table
Mode: B - Bidir Capable, G - GenID Capable
Neighbor Address
Interface
Uptime
FE80::A8BB:CCFF:FE00:5301 Ethernet0/0
FE80::A8BB:CCFF:FE00:5100 Serial1/0
Expires Mode DR pri
00:36:36 00:01:38 B G DR 1
00:36:48 00:01:33 B G
1
R2#sh ipv6 mroute

Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group,
(*, FF1E::1), 00:38:08/00:02:39, RP 2001:DB8:1::, flags: S

Incoming interface: Tunnel4
RPF nbr: 2001:DB8:1::
Immediate Outgoing interface list:
Ethernet0/0, Forward, 00:38:08/00:02:39

Ping multicast address FF1E::1 from R4 and verify echo replies are received from R5
Verify that R3 has a (S,G) entry with an incoming interface towards R1 (first hop router)
R#
R3
R3#sh ipv6 mroute

C - Connected, L - Local, I - Received Source Specific Host Report,
P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set,
J - Join SPT
Timers: Uptime/Expires
Interface state: Interface, State
(2001:DB8:1:1::4, FF1E::1), 00:00:03/00:03:28, flags: SJT

Incoming interface: Serial2/0
RPF nbr: FE80::A8BB:CCFF:FE00:5100
Inherited Outgoing interface list:
Ethernet0/0, Forward, 00:41:26/never
R3#

Answers
IGMP has been replaced with MLD in IPv6 multicast. MLDv2 is
required for SSM support.
As stated in RFC4601, Cisco IOS uses a tunnel interface for the
PIM register process. On the RP, this tunnel interface is used as the
incoming interface for (*,G) entries, as encapsulated multicast
packets will be received on that interface.
Multicast Lab: IPv6 Multicast with Embedded RP

Make R1 an RP
Add MLD Join on Receiver for group FF7E:130:2001:DB8:1::99 to simulate a
receiver
Can you identify R1 loopback address in the embedded RP multicast address
R#
R1
ipv6 pim rp-address 2001:db8:1::1
Receiver
ipv6 mld join-group FF7E:130:2001:DB8:1::99

Verify that group is seen as embedded RP group
Verify that PIM join is sent towards embedded RP (R1)
R#
R3
R3#sh ipv6 pim group-map FF7E:130:2001:DB8:1::99

IP PIM Group Mapping Table
(* indicates group mappings being used)
FF7E:130:2001:DB8:1::/80*
SM, RP: 2001:DB8:1::1
RPF: Se2/0,FE80::A8BB:CCFF:FE00:5100
Info source: Embedded
Uptime: 00:11:31, Groups: 1
R3#sh ipv6 mroute FF7E:130:2001:DB8:1::99
..
(*, FF7E:130:2001:DB8:1::99), 00:09:35/never, RP 2001:DB8:1::1, flags: SCJ
Incoming interface: Serial2/0
RPF nbr: FE80::A8BB:CCFF:FE00:5100
Ethernet0/0, Forward, 00:09:35/never
R3#

Verify that R1 (RP) has received the join coming from R3
Verify that the PIM join has been received by the RP (R2)
Why do we see tunnel3 as RPF interface?
R#
R1

C - Connected, L - Local, I - Received Source Specific Host Report,
P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set,
J - Join SPT
Timers: Uptime/Expires
Interface state: Interface, State
(*, FF7E:130:2001:DB8:1::99), 00:16:13/00:03:26, RP 2001:DB8:1::1, flags: S

RPF nbr: 2001:DB8:1::1
Serial2/0, Forward, 00:16:13/00:03:26
R1#

Ping multicast address FF7E:130:2001:DB8:1::99 from R4 and verify echo replies are
received from R5
Verify that R1 has a (S,G) entry for R4
R#
R1

..
(*, FF7E:130:2001:DB8:1::99), 00:20:43/00:02:56, RP 2001:DB8:1::1, flags: S
RPF nbr: 2001:DB8:1::1
Serial2/0, Forward, 00:20:43/00:02:56
(2001:DB8:1:1::4, FF7E:130:2001:DB8:1::99), 00:00:02/00:03:27, flags: SFT
Incoming interface: Ethernet0/0
RPF nbr: 2001:DB8:1:1::4
Serial2/0, Forward, 00:00:02/00:03:27
R1#
FF7E:130:2001:DB8:1::99. The first 48 bits of the RP address

(2001:db8:1::/48) can be identified after 0x30. The value of 1
preceding 0x30 represents the last 4 bits of the RP address. 0x30
(48 in decimal) is the actual length we use to retrieve the RP
address.
As stated in RFC4601, Cisco IOS uses a tunnel interface for the
PIM register process. On the RP, this tunnel interface is used as the
incoming interface for (*,G) entries, as encapsulated multicast
packets will be received on that interface.
IPv6 Multicast Lab Key
Lab Key
Cisco Connect
173
Multicast Lab: Configs

R#
Configs
R1
ipv6 cef
!
interface Loopback0
ipv6 address 2001:DB8:1::1/128
ipv6 ospf 1 area 0
!
ipv6 address 2001:DB8:1:1::1/64
ipv6 ospf 1 area 0
!
interface Serial1/0
ipv6 ospf 1 area 0
!
interface Serial2/0
ipv6 ospf 1 area 0
!
! For static RP exercise
!
ipv6 pim rp-address 2001:db8:1:: (R2 Loopback address)
!
! For embedded RP exercise
!
ipv6 pim rp-address 2001:DB8:1::1 (Local Loopback address)
!
ipv6 router ospf 1

R#
R2
Configs
ipv6 cef
!
interface Loopback0
ipv6 address 2001:DB8:1::/128
ipv6 ospf 1 area 0
!
ipv6 ospf 1 area 0
!
interface Serial1/0
ipv6 ospf 1 area 0
!
ipv6 pim rp-address 2001:DB8:1::
ipv6 router ospf 1

R#
Configs
R3
ipv6 cef
!
interface Loopback0
ipv6 address 2001:DB8:1:3::3/128
ipv6 ospf 1 area 0
!
ipv6 address 2001:DB8:1:2::3/64
ipv6 ospf 1 area 0
!
ipv6 ospf 1 area 0
!
interface Serial2/0
ipv6 ospf 1 area 0
!
ipv6 pim rp-address 2001:DB8:1::
ipv6 router ospf 1

R#
Configs
R4(Source)
no ipv6 cef
!
ipv6 address 2001:DB8:1:1::4/64
!
R5(Receiver)
no ipv6 cef
!
ipv6 address 2001:DB8:1:2::5/64
ipv6 mld join-group FF05::1:1
ipv6 mld join-group FF7E:130:2001:DB8:1::99
!
For larger statements and

quotes, use this slide layout to
format the long references in all
of your presentations.
Source Name Placement
2012
Cisco
Cisco
Confidential
Connect
178
Complete Your Paper

Session Evaluation
Give us your feedback and you could win
1 of 2 fabulous prizes in a random draw.
Complete and return your paper
evaluation form to the room attendant
as you leave this session.
Winners will be announced today.
You must be present to win!
..visit them at BOOTH# 100
Thank you.
Cisco Connect
180

Ipv6 Hands On Lab Hritter

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Ipv6 Hands On Lab Hritter

Caricato da

Copyright:

Formati disponibili

Toronto, Canada

May 30, 2013

IPv6 Hands-on Lab

Prerequisites: Session Abstract

2012 Cisco and/or its affiliates. All rights reserved.

Lab 1 IPv6 Unique Local Address

Lab 1 IPv6 Stateless Auto-Configuration (SLAAC)

Lab 1: IPv6 Addressing & SLAAC

Lab 1 IPv6 Unique Local & SLAAC: Configs

Lab 1 IPv6 Unique Local & SLAAC: Verification

R4#sh ipv6 int e0/0

H1#sh ipv6 int e0/0

Lab 1 IPv6 Unique Local & SLAAC: Verification

Lab 1 IPv6 SLAAC: Debugs

Lab 1 IPv6 Global Unicast Address

Lab 1b: IPv6 Global Unicast address & SLAAC

Lab 1 IPv6 Global Unicast address & SLAAC: Configs

Lab 1 IPv6 Global Unicast address & SLAAC:

Lab 1 IPv6 Global Unicast address: Verification

R4#sh ipv6 int lo 0

R4#sh ipv6 int e0/0

Lab 1 IPv6 Global Unicast address: Verification

R5#sh ipv6 int lo 0

R5#sh ipv6 int e0/0

Lab 1 IPv6 Global Unicast address: Verification

R6#sh ipv6 int lo 0

R6#sh ipv6 int e0/0

Lab 1 IPv6 SLAAC: Verification

H1#sh ipv6 int e0/0

H2#sh ipv6 int e0/0

Lab 1 IPv6 Global Unicast address: Verification

Lab 1 IPv6 SLAAC: Verification

Lab 1 IPv6 SLAAC: Debugs

Lab 1 IPv6 SLAAC: Debugs

Lab 2 : IPv6 Neighbor

2012 Cisco and/or its affiliates. All rights reserved.

Lab 2 Neighbor Discovery: RS & RA

Lab 2 IPv6 Neighbor discovery: Configs

Lab 2 IPv6 Neighbor discovery: Verification

Lab 2 IPv6 Neighbor discovery: Debugs

Lab 2 Neighbor Discovery: DAD, NS & NA

Lab 2 IPv6 Neighbor discovery: Configs

Lab 2 IPv6 Neighbor discovery: Verification

R5#sh ipv6 int e0/0 | i DUP

Lab 2 IPv6 Neighbor discovery: Debugs

R5(config-if)#ipv6 address 2001:db8:1:59::5/64

Lab 2 IPv6 Neighbor discovery: Configs

Lab 2 IPv6 Neighbor discovery: Debugs

Lab 2 Neighbor Discovery: Renumbering

Lab 2 IPv6 Neighbor discovery: Configs

Lab 2 IPv6 Neighbor discovery: Verification

Lab 2 IPv6 Neighbor discovery: Debugs

Lab 2 IPv6 Neighbor discovery: Configs

Lab 2 IPv6 Neighbor discovery: Verification

Lab 2 IPv6 Neighbor discovery: Debugs

Lab 2 IPv6 Neighbor discovery: Cleanup Configs

Lab 2 Neighbor Discovery: Default Router

Lab 2 IPv6 Neighbor discovery: Configs

Lab 2 IPv6 Neighbor discovery: Verification

2012 Cisco and/or its affiliates. All rights reserved.

Lab 3 HSRPv6: Configs

Lab 3 HSRPv6: Verification

Lab 3 HSRPv6: Verification