Professional Documents
Culture Documents
© 2012
2011 Cisco and/or its affiliates. All rights reserved. Cisco Connect 1
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
Lab4 : HSRPv6
Lab5 : EIGRPv6
Lab7 : OSPFv3
Lab8 : BGPv6
© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 6
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 R4’s 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 H1#sh ipv6 int e0/0
Ethernet0/0 is up, line protocol is up Ethernet0/0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5400 IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5700
No Virtual link-local address(es): No Virtual link-local address(es):
Global unicast address(es): Stateless address autoconfig enabled
FD01:DB8:1:41:A8B8:CCFF:FE00:5400, subnet is FD01:DB8:1:41::/64 Global unicast address(es): FD01:DB8:1:41:A8BB:CCFF:FE00:5700,
[EUI] subnet is FD01:DB8:1:41::/64 [EUI/CAL/PRE]
Joined group address(es): valid lifetime 2591861 preferred lifetime 604661
FF02::1 Joined group address(es):
FF02::2 FF02::1
FF02::1:FF00:5400 FF02::1:FF00:5700
MTU is 1500 bytes MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled ICMP redirects are enabled
ICMP unreachables are sent ICMP unreachables are sent
ND DAD is enabled, number of DAD attempts: 1 ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds (using 30000) ND reachable time is 30000 milliseconds (using 30000)
ND advertised reachable time is 0 (unspecified) Default router is FE80::A8BB:CCFF:FE00:5400 on Ethernet0/0
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.
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
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to FD01:DB8:1:41:A8B8:CCFF:FE00:5400, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/3/17 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
Lab 1 IPv6 SLAAC: Debugs
R4 H1
R4#deb ipv6 nd H1#deb ipv6 nd
ICMP Neighbor Discovery events debugging is on ICMP Neighbor Discovery events debugging is on
ICMPv6-ND: Request to send RA for FE80::A8BB:CCFF:FE00:5400 ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5400 on
ICMPv6-ND: Setup RA from FE80::A8BB:CCFF:FE00:5400 to FF02::1 on Ethernet0/0
Ethernet0/0 ICMPv6-ND: Prefix : FD01:DB8:1:1::, Length: 64, Vld Lifetime: 2592000,
ICMPv6-ND: MTU = 1500 Prf Lifetime: 604800, PI Flags: C0
ICMPv6-ND: prefix = FD01:DB8:1:41::/64 onlink autoconfig ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig
ICMPv6-ND: 2592000/604800 (valid/preferred) FD01:DB8:1:41::/64 eui-64, FD01:DB8:1:41:A8BB:CCFF:FE00:5700
ICMPv6-ND: Request to send RA for FE80::A8BB:CCFF:FE00:5400 FD01:DB8:1:41:A8BB:CCFF:FE00:5700/64 is existing
ICMPv6-ND: Setup RA from FE80::A8BB:CCFF:FE00:5400 to FF02::1 on ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5400 on
Ethernet0/0 Ethernet0/0
ICMPv6-ND: MTU = 1500 ICMPv6-ND: Prefix : FD01:DB8:1:1::, Length: 64, Vld Lifetime: 2592000,
ICMPv6-ND: prefix = FD01:DB8:1:41::/64 onlink autoconfig Prf Lifetime: 604800, PI Flags: C0
ICMPv6-ND: 2592000/604800 (valid/preferred) ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig
R4# 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)#ipv6 unicast-routing
R4(config)#interface loop0
R4(config-if)#ipv6 address 2001:db8:1:1::4/128
R4(config)#interface e0/0
R4(config-if)#ipv6 address 2001:db8:1:41::4/64
R4(config-if)#end
R5 R5(config)#ipv6 unicast-routing
R5(config)#interface loop0
R5(config-if)#ipv6 address 2001:db8:1:1::5/128
R5(config)#interface e0/0
R5(config-if)#ipv6 address 2001:db8:1:56::5/64
R5(config-if)#ipv6 address 2001:db8:1:57::5/64
R5(config-if)#ipv6 address 2001:db8:1:58::5/64
R5(config-if)#end
Lab 1 IPv6 Global Unicast address & SLAAC:
Configs
R# Configs
R6 R4(config)#ipv6 unicast-routing
R6(config)#interface loop0
R6(config-if)#ipv6 address 2001:db8:1:1::6/128
R6(config)#interface e0/0
R6(config-if)#ipv6 address 2001:db8:1:56::6/64
R6(config-if)#ipv6 address 2001:db8:1:57::6/64
R6(config-if)#ipv6 address 2001:db8:1:58::6/64
R6(config-if)#end
H2 H2(config)#interface e0/0
H2(config-if)#ipv6 enable
H2(config-if)#ipv6 address autoconfig
H2(config-if)#end
Lab 1 IPv6 Global Unicast address: Verification
R4 Loopback 0 R4 Ethernet0/0
R4#sh ipv6 int lo 0 R4#sh ipv6 int e0/0
Loopback0 is up, line protocol is up Ethernet0/0 is up, line protocol is up
IPv6 is enabled, link-local address is IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5400
FE80::A8BB:CCFF:FE00:5900 No Virtual link-local address(es):
No Virtual link-local address(es): Global unicast address(es):
Global unicast address(es): 2001:DB8:1:41::4, subnet is 2001:DB8:1:41::/64
2001:DB8:1:1::4, subnet is 2001:DB8:1:1::4/128 FD01:DB8:1:41:A8BB:CCFF:FE00:5400, subnet is FD01:DB8:1:41::/64 [EUI]
Joined group address(es): Joined group address(es):
FF02::1 FF02::1
FF02::2 FF02::2
FF02::1:FF00:4 FF02::1:FF00:4
FF02::1:FF00:5900 FF02::1:FF00:5400
MTU is 1514 bytes MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled ICMP redirects are enabled
ICMP unreachables are sent ICMP unreachables are sent
ND DAD is not supported ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds (using 30000) ND reachable time is 30000 milliseconds (using 30000)
ND RAs are suppressed (periodic) ND advertised reachable time is 0 (unspecified)
Hosts use stateless autoconfig for addresses. ND advertised retransmit interval is 0 (unspecified)
R4# 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.
R4#
Lab 1 IPv6 Global Unicast address: Verification
R5 Loopback 0 R5 Ethernet0/0
R5#sh ipv6 int lo 0 R5#sh ipv6 int e0/0
Loopback0 is up, line protocol is up Ethernet0/0 is up, line protocol is up
IPv6 is enabled, link-local address is IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5A00
FE80::A8BB:CCFF:FE00:5A00 No Virtual link-local address(es):
No Virtual link-local address(es): Global unicast address(es):
Global unicast address(es): 2001:DB8:1:56::5, subnet is 2001:DB8:1:56::/64
2001:DB8:1:1::5, subnet is 2001:DB8:1:1::5/128 2001:DB8:1:57::5, subnet is 2001:DB8:1:57::/64
Joined group address(es): 2001:DB8:1:58::5, subnet is 2001:DB8:1:58::/64
FF02::1 Joined group address(es):
FF02::2 FF02::1
FF02::1:FF00:5 FF02::2
FF02::1:FF00:5A00 FF02::1:FF00:5
MTU is 1514 bytes FF02::1:FF00:5A00
ICMP error messages limited to one every 100 milliseconds MTU is 1500 bytes
ICMP redirects are enabled ICMP error messages limited to one every 100 milliseconds
ICMP unreachables are sent ICMP redirects are enabled
ND DAD is not supported ICMP unreachables are sent
ND reachable time is 30000 milliseconds (using 30000) ND DAD is enabled, number of DAD attempts: 1
ND RAs are suppressed (periodic) ND reachable time is 30000 milliseconds (using 30000)
Hosts use stateless autoconfig for addresses. ND advertised reachable time is 0 (unspecified)
R5# 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.
Lab 1 IPv6 Global Unicast address: Verification
R6 Loopback 0 R6 Ethernet0/0
R6#sh ipv6 int lo 0 R6#sh ipv6 int e0/0
Loopback0 is up, line protocol is up Ethernet0/0 is up, line protocol is up
IPv6 is enabled, link-local address is IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5B00
FE80::A8BB:CCFF:FE00:5B00 No Virtual link-local address(es):
No Virtual link-local address(es): Global unicast address(es):
Global unicast address(es): 2001:DB8:1:56::6, subnet is 2001:DB8:1:56::/64
2001:DB8:1:1::6, subnet is 2001:DB8:1:1::6/128 2001:DB8:1:57::6, subnet is 2001:DB8:1:57::/64
Joined group address(es): 2001:DB8:1:58::6, subnet is 2001:DB8:1:58::/64
FF02::1 Joined group address(es):
FF02::2 FF02::1
FF02::1:FF00:6 FF02::2
FF02::1:FF00:5B00 FF02::1:FF00:6
MTU is 1514 bytes FF02::1:FF00:5B00
ICMP error messages limited to one every 100 milliseconds MTU is 1500 bytes
ICMP redirects are enabled ICMP error messages limited to one every 100 milliseconds
ICMP unreachables are sent ICMP redirects are enabled
ND DAD is not supported ICMP unreachables are sent
ND reachable time is 30000 milliseconds (using 30000) ND DAD is enabled, number of DAD attempts: 1
ND RAs are suppressed (periodic) ND reachable time is 30000 milliseconds (using 30000)
Hosts use stateless autoconfig for addresses. ND advertised reachable time is 0 (unspecified)
R6# 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.
Lab 1 IPv6 SLAAC: Verification
H1 Ethernet0/0 H2 Ethernet0/0
H1#sh ipv6 int e0/0 H2#sh ipv6 int e0/0
Ethernet0/0 is up, line protocol is up Ethernet0/0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5700 IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5D00
No Virtual link-local address(es): No Virtual link-local address(es):
Stateless address autoconfig enabled Stateless address autoconfig enabled
Global unicast address(es): Global unicast address(es):
2001:DB8:1:41:A8BB:CCFF:FE00:5700, subnet is 2001:DB8:1:41::/64 2001:DB8:1:56:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:56::/64
[EUI/CAL/PRE] [EUI/CAL/PRE]
valid lifetime 2591845 preferred lifetime 604645 valid lifetime 2591989 preferred lifetime 604789
FD01:DB8:1:41:A8BB:CCFF:FE00:5700, subnet is FD01:DB8:1:41::/64 2001:DB8:1:57:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:57::/64
[EUI/CAL/PRE] [EUI/CAL/PRE]
valid lifetime 2591845 preferred lifetime 604645 valid lifetime 2591989 preferred lifetime 604789
Joined group address(es): 2001:DB8:1:58:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:58::/64
FF02::1 [EUI/CAL/PRE]
FF02::1:FF00:5700 valid lifetime 2591989 preferred lifetime 604789
MTU is 1500 bytes Joined group address(es):
ICMP error messages limited to one every 100 milliseconds FF02::1
ICMP redirects are enabled FF02::1:FF00:5D00
ICMP unreachables are sent MTU is 1500 bytes
ND DAD is enabled, number of DAD attempts: 1 ICMP error messages limited to one every 100 milliseconds
ND reachable time is 30000 milliseconds (using 30000) ICMP redirects are enabled
Default router is FE80::A8BB:CCFF:FE00:5400 on Ethernet0/0 ICMP unreachables are sent
H1# ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds (using 30000)
Default router is FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0
H2#
Lab 1 IPv6 Global Unicast address: Verification
R# Verification commands
H2 H2#ping 2001:db8:1:56::5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:56::5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/3/14 ms
H2#ping 2001:db8:1:57::5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:57::5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/4/21 ms
H2#ping 2001:db8:1:58::5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:58::5, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/4/19 ms
H2#ping 2001:db8:1:56::6
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:56::6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/4/17 ms
H2#ping 2001:db8:1:57::6
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:57::6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/3/17 ms
H2#ping 2001:db8:1:58::6
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:58::6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/3/14 ms
H2#
Lab 1 IPv6 SLAAC: Verification
R# Verification commands
H1 H1#ping 2001:DB8:1:41::4
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:41::4, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/3/17 ms
H1#
Lab 1 IPv6 SLAAC: Debugs
R5 & R6
R5#deb ipv6 nd R6#deb ipv6 nd
ICMPv6-ND: Request to send RA for FE80::A8BB:CCFF:FE00:5A00 ICMPv6-ND: Request to send RA for FE80::A8BB:CCFF:FE00:5B00
ICMPv6-ND: Setup RA from FE80::A8BB:CCFF:FE00:5A00 to FF02::1 on ICMPv6-ND: Setup RA from FE80::A8BB:CCFF:FE00:5B00 to FF02::1 on
Ethernet0/0 Ethernet0/0
ICMPv6-ND: MTU = 1500 ICMPv6-ND: MTU = 1500
ICMPv6-ND: prefix = 2001:DB8:1:56::/64 onlink autoconfig ICMPv6-ND: prefix = 2001:DB8:1:56::/64 onlink autoconfig
ICMPv6-ND: 2592000/604800 (valid/preferred) ICMPv6-ND: 2592000/604800 (valid/preferred)
ICMPv6-ND: prefix = 2001:DB8:1:57::/64 onlink autoconfig ICMPv6-ND: prefix = 2001:DB8:1:57::/64 onlink autoconfig
ICMPv6-ND: 2592000/604800 (valid/preferred) ICMPv6-ND: 2592000/604800 (valid/preferred)
ICMPv6-ND: prefix = 2001:DB8:1:58::/64 onlink autoconfig ICMPv6-ND: prefix = 2001:DB8:1:58::/64 onlink autoconfig
ICMPv6-ND: 2592000/604800 (valid/preferred) ICMPv6-ND: 2592000/604800 (valid/preferred)
R5# R6#
ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5B00 on Ethernet0/0 ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0
ICMPv6-ND: Prefix : 2001:DB8:1:56::, Length: 64, Vld Lifetime: 2592000, Prf ICMPv6-ND: Prefix : 2001:DB8:1:56::, Length: 64, Vld Lifetime: 2592000, Prf
Lifetime: 604800, PI Flags: C0 Lifetime: 604800, PI Flags: C0
ICMPv6-ND: Prefix : 2001:DB8:1:57::, Length: 64, Vld Lifetime: 2592000, Prf ICMPv6-ND: Prefix : 2001:DB8:1:57::, Length: 64, Vld Lifetime: 2592000, Prf
Lifetime: 604800, PI Flags: C0 Lifetime: 604800, PI Flags: C0
ICMPv6-ND: Prefix : 2001:DB8:1:58::, Length: 64, Vld Lifetime: 2592000, Prf ICMPv6-ND: Prefix : 2001:DB8:1:58::, Length: 64, Vld Lifetime: 2592000, Prf
Lifetime: 604800, PI Flags: C0 Lifetime: 604800, PI Flags: C0
R5# H2#
Lab 1 IPv6 SLAAC: Debugs
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
ICMPv6-ND: Prefix : 2001:DB8:1:57::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0
ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:57::/64 eui-64, 2001:DB8:1:57:A8BB:CCFF:FE00:5D00
2001:DB8:1:57:A8BB:CCFF:FE00:5D00/64 is existing
H2#
ICMPv6-ND: Prefix : 2001:DB8:1:58::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0
ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:58::/64 eui-64, 2001:DB8:1:58:A8BB:CCFF:FE00:5D00
2001:DB8:1:58:A8BB:CCFF:FE00:5D00/64 is existing
H2#
H1#deb ipv6 nd
ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5900 on Ethernet0/0
ICMPv6-ND: Prefix : 2001:DB8:1:41::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0
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
© 2012 Cisco and/or its affiliates. All rights reserved. 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)#interface e0/0
R4(config-if)#ipv6 nd ra interval 30
R4(config-if)#end
H1 H1(config)#interface e0/0
H1(config-if)#no ipv6 address autoconfig
H1(config-if)#no ipv6 enable
H1(config-if)#ipv6 enable
H1(config-if)#ipv6 address autoconfig
H1(config-if)#end
Lab 2 IPv6 Neighbor discovery: Verification
R4
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:5900
No Virtual link-local address(es):
Global unicast address(es):
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]
Joined group address(es):
FF02::1
FF02::2
FF02::1:FF00:4
FF02::1:FF00:5900
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 30 seconds
ND router advertisements live for 1800 seconds
ND advertised default router preference is Medium
Hosts use stateless autoconfig for addresses.
R4#
Lab 2 IPv6 Neighbor discovery: Debugs
H1
H1(config-if)#ipv6 enable
*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
H1(config-if)#ipv6 address autoconfig
*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 R6’s Ethernet address of 2001:db8:1:56::6 from R5 to see how NS and NA
takes place between them
Lab 2 IPv6 Neighbor discovery: Configs
R# Configs
R5 R5(config)#int e0/0
R5(config-if)#ipv6 address 2001:db8:1:59::5/64
R6 R6(config)#int e0/0
R6(config-if)#ipv6 address 2001:db8:1:59::6/64
Lab 2 IPv6 Neighbor discovery: Verification
R4
R6#sh ipv6 int
Ethernet0/0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5B00
No Virtual link-local address(es):
Global unicast address(es):
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
Joined group address(es):
FF02::1
FF02::2
FF02::1:FF00:5
FF02::1:FF00:6
FF02::1:FF00:5B00
MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
…
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
Lab 2 IPv6 Neighbor discovery: Debugs
R5
R5#ping 2001:db8:1:56::6
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:56::6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/1/5 ms
R5#
*Jan 30 22:15:24.668: ICMPv6-ND: DELETE -> INCMP: 2001:DB8:1:56::6
*Jan 30 22:15:24.668: ICMPv6-ND: Sending NS for 2001:DB8:1:56::6 on Ethernet0/0
*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
Lab 2 IPv6 Neighbor discovery: Configs
R# Configs
R5 R5(config)#interface e0/0
R5(config-if)#ipv6 nd ra interval 40
R5(config-if)#ipv6 address 2001:db8:1:88::5/64
R5(config-if)#ipv6 nd prefix 2001:db8:1:58::/64 50 0
R5(config-if)#end
R6 R6(config)#interface e0/0
R6(config-if)#ipv6 nd ra interval 40
R6(config-if)#ipv6 address 2001:db8:1:88::6/64
R6(config-if)#ipv6 nd prefix 2001:db8:1:58::/64 50 0
R6(config-if)#end
Lab 2 IPv6 Neighbor discovery: Verification
H2
H2#sh ipv6 int e0/0
Ethernet0/0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5D00
No Virtual link-local address(es):
Stateless address autoconfig enabled
Global unicast address(es):
2001:DB8:1:56:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:56::/64 [EUI/CAL/PRE]
valid lifetime 2591994 preferred lifetime 604794
2001:DB8:1:57:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:57::/64 [EUI/CAL/PRE]
valid lifetime 2591994 preferred lifetime 604794
2001:DB8:1:58:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:58::/64 [EUI/CAL]
valid lifetime 47 preferred lifetime 0
2001:DB8:1:88:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:88::/64 [EUI/CAL/PRE]
valid lifetime 2591994 preferred lifetime 604794
Joined group address(es):
FF02::1
FF02::1:FF00:5D00
MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
ICMP unreachables are sent
Lab 2 IPv6 Neighbor discovery: Debugs
H2
H2#deb ipv6 nd
*Jan 31 04:26:01.476: ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0
*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
2001:DB8:1:56:A8BB:CCFF:FE00:5D00/64 is existing
*Jan 31 04:26:01.476: ICMPv6-ND: Prefix : 2001:DB8:1:57::, 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:57::/64 eui-64, 2001:DB8:1:57:A8BB:CCFF:FE00:5D00
2001:DB8:1:57:A8BB:CCFF:FE00:5D00/64 is existing
*Jan 31 04:26:01.476: ICMPv6-ND: Prefix : 2001:DB8:1:58::, Length: 64, Vld Lifetime: 50, Prf Lifetime: 0, PI Flags: C0
*Jan 31 04:26:01.476: ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:58::/64 eui-64, 2001:DB8:1:58:A8BB:CCFF:FE00:5D00
2001:DB8:1:58:A8BB:CCFF:FE00:5D00/64 is existing
*Jan 31 04:26:01.476: ICMPv6-ND: Prefix : 2001:DB8:1:88::, 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:88::/64 eui-64, 2001:DB8:1:88:A8BB:CCFF:FE00:5D00
2001:DB8:1:88:A8BB:CCFF:FE00:5D00/64 is existing
Lab 2 IPv6 Neighbor discovery: Configs
R# Configs
R5 R5(config)#interface e0/0
R5(config-if)#ipv6 nd prefix 2001:db8:1:58::/64 0 0
R5(config-if)#end
R6 R6(config)#interface e0/0
R6(config-if)#ipv6 nd prefix 2001:db8:1:58::/64 0 0
R6(config-if)#end
Lab 2 IPv6 Neighbor discovery: Verification
H2
H2#sh ipv6 int e0/0
Ethernet0/0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5D00
No Virtual link-local address(es):
Stateless address autoconfig enabled
Global unicast address(es):
2001:DB8:1:56:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:56::/64 [EUI/CAL/PRE]
valid lifetime 2591986 preferred lifetime 604786
2001:DB8:1:57:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:57::/64 [EUI/CAL/PRE]
valid lifetime 2591986 preferred lifetime 604786
2001:DB8:1:88:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:88::/64 [EUI/CAL/PRE]
valid lifetime 2591986 preferred lifetime 604786
Joined group address(es):
FF02::1
FF02::1:FF00:5D00
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)
Default router is FE80::A8BB:CCFF:FE00:5B00 on Ethernet0/0
H2#
Lab 2 IPv6 Neighbor discovery: Debugs
H2
H2#deb ipv6 nd
H2#
*Jan 31 04:47:34.486: ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0
*Jan 31 04:47:34.486: ICMPv6-ND: Prefix : 2001:DB8:1:56::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0
*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.486: ICMPv6-ND: Prefix : 2001:DB8:1:57::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0
*Jan 31 04:47:34.486: ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:57::/64 eui-64, 2001:DB8:1:57:A8BB:CCFF:FE00:5D00
2001:DB8:1:57:A8BB:CCFF:FE00:5D00/64 is existing
*Jan 31 04:47:34.487: ICMPv6-ND: Prefix : 2001:DB8:1:58::, Length: 64, Vld Lifetime: 0, Prf Lifetime: 0, PI Flags: C0
*Jan 31 04:47:34.487: ICMPv6-ND: Invalid prefix 2001:DB8:1:58::/64
*Jan 31 04:47:34.487: ICMPv6-ND: Prefix : 2001:DB8:1:88::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0
H2#
*Jan 31 04:47:34.487: ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:88::/64 eui-64, 2001:DB8:1:88:A8BB:CCFF:FE00:5D00
2001:DB8:1:88:A8BB:CCFF:FE00:5D00/64 is existing
Lab 2 IPv6 Neighbor discovery: Cleanup Configs
R# Configs
R5 R5(config)#interface e0/0
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)#interface e0/0
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)
Lab 2 IPv6 Neighbor discovery: Configs
R# Configs
R5 R5(config)#interface e0/0
R5(config-if)#ipv6 nd router-preference high
R5(config-if)#end
Lab 2 IPv6 Neighbor discovery: Verification
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
Note, if you do not see a default route, type the following command and make sure you have the entry from R5
© 2012 Cisco and/or its affiliates. All rights reserved. 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#
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
2001:DB8:1:56:A8BB:CCFF:FE00:5D00/64 is existing
*Feb 2 10:24:20.246: ICMPv6-ND: Prefix : 2001:DB8:1:57::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0
H2#
*Feb 2 10:24:20.247: ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:57::/64 eui-64, 2001:DB8:1:57:A8BB:CCFF:FE00:5D00
2001:DB8:1:57:A8BB:CCFF:FE00:5D00/64 is existing
*Feb 2 10:24:20.247: ICMPv6-ND: Prefix : 2001:DB8:1:88::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0
*Feb 2 10:24:20.247: ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:88::/64 eui-64, 2001:DB8:1:88:A8BB:CCFF:FE00:5D00
2001:DB8:1:88:A8BB:CCFF:FE00:5D00/64 is existing
Lab 4 : EIGRPv6
© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 56
Lab 4: EIGRPv6
Lab 4 EIGRPv6
R# Configs
R5 R5(config-if)#int loop 0
R5(config-if)#ipv6 eigrp 1
R5(config-if)#int e0/0
R5(config-if)#ipv6 eigrp 1
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)#ipv6 eigrp 1
R6(config-if)#int e0/0
R6(config-if)#ipv6 eigrp 1
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 R6#sh ipv6 prot | b EIGRP
EIGRP-IPv6 Protocol for AS(1) EIGRP-IPv6 Protocol for AS(1)
Metric weight K1=1, K2=0, K3=1, K4=0, K5=0 Metric weight K1=1, K2=0, K3=1, K4=0, K5=0
NSF-aware route hold timer is 240 NSF-aware route hold timer is 240
Router-ID: 10.1.1.5 Router-ID: 10.1.1.6
Topology : 0 (base) Topology : 0 (base)
Active Timer: 3 min Active Timer: 3 min
Distance: internal 90 external 170 Distance: internal 90 external 170
Maximum path: 16 Maximum path: 16
Maximum hopcount 100 Maximum hopcount 100
Maximum metric variance 1 Maximum metric variance 1
Interfaces: Interfaces:
Loopback0 Loopback0
Ethernet0/0 Ethernet0/0
Redistribution: Redistribution:
None None
Lab 4 EIGRPv6: Verification
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#
© 2012 Cisco and/or its affiliates. All rights reserved. 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 add 2001:db8:14:1::15/127
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 entry for ::/0
Known via "static", distance 1, metric 0
Route count is 1/1, share count 0
Routing paths:
FE80::4AFF:FEA2:851, Serial1/0
Last updated 00:02:15 ago
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 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
Lab 5 IPv6 Static routing: Configs
R# Configs
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
Known via "static", distance 1, metric 0
Route count is 1/1, share count 0
Routing paths:
2001:DB8:14:1::15
Last updated 00:11:42 ago
R1#
H1 H1>ping 2004:db8::1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2004:DB8::1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 38/39/44 ms
H1>
Lab 6 : IPv6 Manual
Tunnels
© 2012 Cisco and/or its affiliates. All rights reserved. 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)#ipv6 address 2001:db8:35:1::17/127
R5(config-if)#end
R3 R3(config-if)#int tun 0
R3(config-if)#tun source s1/0
R3(config-if)#tun destination 10.1.35.1
R3(config-if)#tun mode ipv6ip
R3(config-if)#ipv6 address 2001:db8:35:1::16/127
R5(config-if)#end
Lab 6 IPv6 Manual Tunnels: Verification
R3 Tunnel 0 R5 Tunnel 0
R3#sh ipv6 int tun 0 R5#sh ipv6 int tun 0
Tunnel0 is up, line protocol is up Tunnel0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::A01:2300 IPv6 is enabled, link-local address is FE80::A01:2301
No Virtual link-local address(es): No Virtual link-local address(es):
Global unicast address(es): Global unicast address(es):
2001:DB8:35:1::16, subnet is 2001:DB8:35:1::16/127 2001:DB8:35:1::17, subnet is 2001:DB8:35:1::16/127
Joined group address(es): Joined group address(es):
FF02::1 FF02::1
FF02::2 FF02::2
FF02::1:FF00:16 FF02::1:FF00:17
FF02::1:FF01:2300 FF02::1:FF01:2301
MTU is 1480 bytes MTU is 1480 bytes
ICMP error messages limited to one every 100 milliseconds ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled ICMP redirects are enabled
ICMP unreachables are sent ICMP unreachables are sent
ND DAD is enabled, number of DAD attempts: 1 ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds (using 30000) ND reachable time is 30000 milliseconds (using 30000)
ND RAs are suppressed (periodic) ND RAs are suppressed (periodic)
Hosts use stateless autoconfig for addresses. Hosts use stateless autoconfig for addresses.
R3# R5#
Lab 6 IPv6 Manual Tunnels: Verification
R3
R3#ping 2001:db8:35:1::17
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:35:1::17, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 39/39/39 ms
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)#int tun 0
R6(config-if)#tun source s1/0
R6(config-if)#tun destination 10.1.36.0
R6(config-if)#tun mode gre ip
R6(config-if)#ipv6 address 2001:db8:36:1::17/127
R6(config-if)#end
R3 R3(config-if)#int tun 1
R3(config-if)#tun source s2/0
R3(config-if)#tun destination 10.1.36.1
R3(config-if)#tun mode gre ip
R3(config-if)#ipv6 address 2001:db8:36:1::16/127
R3(config-if)#end
Lab 6 IPv6 Manual Tunnels: Verification
R3 Tunnel 1 R6 Tunnel 0
R3#sh ipv6 int tun 1 R6#sh ipv6 int tun 0
Tunnel1 is up, line protocol is up Tunnel0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::4AFF:FEA2:853 IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5600
No Virtual link-local address(es): No Virtual link-local address(es):
Global unicast address(es): Global unicast address(es):
2001:DB8:36:1::16, subnet is 2001:DB8:36:1::16/127 2001:DB8:36:1::17, subnet is 2001:DB8:36:1::16/127
Joined group address(es): Joined group address(es):
FF02::1 FF02::1
FF02::2 FF02::2
FF02::1:FF00:16 FF02::1:FF00:17
FF02::1:FFA2:853 FF02::1:FF00:5600
MTU is 1476 bytes MTU is 1476 bytes
ICMP error messages limited to one every 100 milliseconds ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled ICMP redirects are enabled
ICMP unreachables are sent ICMP unreachables are sent
ND DAD is enabled, number of DAD attempts: 1 ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds (using 30000) ND reachable time is 30000 milliseconds (using 30000)
ND RAs are suppressed (periodic) ND RAs are suppressed (periodic)
Hosts use stateless autoconfig for addresses. Hosts use stateless autoconfig for addresses.
R3# R6#
Lab 6 IPv6 Manual Tunnels: Verification
R3
R3#ping 2001:db8:36:1::17
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:36:1::17, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 37/38/40 ms
R3#
Lab 7 : OSPFv3
© 2012 Cisco and/or its affiliates. All rights reserved. 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 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
Lab 7: OSPFv3
Lab 7 OSPFv3: Configs
R# Area 1 Configs
R3 R3(config)#ipv6 unicast-routing
R3(config)#int lo 0
R3(config-if)#ipv6 add 2001:db8:172:16::3/128
R3(config)#int e0/0
R3(config-if)#ipv6 add 2001:db8:172:17::3/127
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)#ipv6 unicast-routing
R2(config-if)#int e0/0
R2(config-if)#ipv6 add 2001:db8:172:17::2/127
R2(config-if)#ipv6 ospf 1 area 1
R2(config-if)#end
Lab 7 OSPFv3: Configs
R# Area 0 Configs
R2 R2(config)#int lo 0
R2(config-if)#ipv6 add 2001:db8:172:16::2/128
R2(config-if)#ipv6 ospf 1 area 0
R2(config-if)#int s1/0
R2(config-if)#ipv6 add 2001:db8:172:17::1/127
R2(config-if)#ipv6 ospf 1 area 0
R2(config-if)#end
R1 R1(config)#ipv6 unicast-routing
R1(config)#int lo 0
R1(config-if)#ipv6 add 2001:db8:172:16::1/128
R1(config-if)#ipv6 ospf 1 area 0
R1(config)#int s1/0
R1(config-if)#ipv6 add 2001:db8:172:17::/127
R1(config-if)#ipv6 ospf 1 area 0
R1(config-if)#end
Lab 7 OSPFv3: Verification
R2
R2#sh ipv6 ospf nei
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
© 2012 Cisco and/or its affiliates. All rights reserved. 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 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
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 R3(config)#router bgp 109
R3(config-router)#no bgp default ipv4-unicast
R3(config-router)#address-family ipv6
R3(config-router-af)#nei 2001:db8:172:16::2 remote 109
R3(config-router-af)#nei 2001:db8:172:16::2 update loop 0
R3(config-router-af)#end
Lab 8 BGPv6: iBGP Configs
R# Area 0 Configs
R2 R2(config)#router bgp 109
R2(config-router)#no bgp default ipv4-unicast
R2(config-router)#address-family ipv6
R2(config-router-af)#nei 2001:db8:172:16::1 remote 109
R2(config-router-af)#nei 2001:db8:172:16::1 update loop 0
R2(config-router-af)#nei 2001:db8:172:16::1 route-reflector-client
R2(config-router-af)#nei 2001:db8:172:16::3 remote 109
R2(config-router-af)#nei 2001:db8:172:16::3 update loop 0
R2(config-router-af)#nei 2001:db8:172:16::3 route-reflector-client
R2(config-router-af)#end
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
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 bgp 1
R5(config-router)#address-family ipv6
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)#net 2001:db8:1:57::/64
R5(config-router-af)#net 2001:db8:1:88::/64
R5(config-router-af)#aggregate-address 2001:db8:1:56::/63 summary-only
R5(config-router-af)#end
R3 R3(config)#router bgp 109
R3(config-router)#address-family ipv6
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 bgp 1
R6(config-router)#address-family ipv6
R6(config-router-af)#nei 2001:DB8:36:1::16 remote 109
R6(config-router-af)#net 2001:db8:1:56::/64
R6(config-router-af)#net 2001:db8:1:57::/64
R6(config-router-af)#net 2001:db8:1:88::/64
R6(config-router-af)#aggregate-address 2001:db8:1:56::/63 summary-only
R6(config-router-af)#end
R3 R3(config)#router bgp 109
R3(config-router)#address-family ipv6
R3(config-router-af)#nei 2001:db8:36:1::17 remote 1
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
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
R3#
Lab 8 BGPv6: eBGP Verification
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
© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 107
Configs
R# Configs
R# Configs
ipv6 unicast-routing
R4 ipv6 cef
!
interface Loopback0
ip address 10.1.1.4 255.255.255.255
ipv6 address 2001:DB8:1:1::4/128
!
interface Ethernet0/0
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
interface Loopback0 router eigrp 1
R5 ip address 10.1.1.5 255.255.255.255 network 10.1.1.5 0.0.0.0
ipv6 address 2001:DB8:1:1::5/128 network 10.1.35.0 0.0.0.1
ipv6 eigrp 1 network 10.1.56.0 0.0.0.255
! network 10.1.57.0 0.0.0.255
interface Tunnel0 network 10.1.58.0 0.0.0.255
no ip address !
ipv6 address 2001:DB8:35:1::17/127 router bgp 1
tunnel source Serial1/0 bgp log-neighbor-changes
tunnel mode ipv6ip neighbor 10.1.1.6 remote-as 1
tunnel destination 10.1.35.0 neighbor 10.1.1.6 update-source Loopback0
! neighbor 10.1.35.0 remote-as 109
interface Ethernet0/0 neighbor FE80::A01:2300%Tunnel0 remote-as 109
ip address 10.1.57.5 255.255.255.0 secondary !
ip address 10.1.58.5 255.255.255.0 secondary address-family ipv4
ip address 10.1.56.5 255.255.255.0 network 10.1.56.0 mask 255.255.255.0
no ip split-horizon eigrp 1 network 10.1.57.0 mask 255.255.255.0
standby version 2 network 10.1.58.0 mask 255.255.255.0
standby 1 ip 10.1.56.1 aggregate-address 10.1.56.0 255.255.254.0 summary-only
standby 1 ipv6 autoconfig neighbor 10.1.1.6 activate
ipv6 address 2001:DB8:1:56::5/64 neighbor 10.1.35.0 activate
ipv6 address 2001:DB8:1:57::5/64 no neighbor FE80::A01:2300%Tunnel0 activate
ipv6 address 2001:DB8:1:88::5/64 exit-address-family
ipv6 nd router-preference High !
ipv6 nd ra interval 40 address-family ipv6
ipv6 eigrp 1 network 2001:DB8:1:56::/64
! network 2001:DB8:1:57::/64
interface Serial1/0 network 2001:DB8:1:88::/64
ip address 10.1.35.1 255.255.255.254 aggregate-address 2001:DB8:1:56::/63 summary-only
neighbor FE80::A01:2300%Tunnel0 activate
exit-address-family
!
ipv6 router eigrp 1
R#
Configs
Configs
interface Loopback0 !
R6 ip address 10.1.1.6 255.255.255.255 router eigrp 1
ipv6 address 2001:DB8:1:1::6/128 network 10.1.1.6 0.0.0.0
ipv6 eigrp 1 network 10.1.36.0 0.0.0.1
! network 10.1.56.0 0.0.0.255
interface Tunnel0 network 10.1.57.0 0.0.0.255
no ip address network 10.1.58.0 0.0.0.255
ipv6 address 2001:DB8:36:1::17/127 !
tunnel source Serial1/0 router bgp 1
tunnel destination 10.1.36.0 bgp log-neighbor-changes
! neighbor 10.1.1.5 remote-as 1
interface Ethernet0/0 neighbor 10.1.1.5 update-source Loopback0
ip address 10.1.57.6 255.255.255.0 neighbor 10.1.36.0 remote-as 109
secondary neighbor 2001:DB8:36:1::16 remote-as 109
ip address 10.1.58.6 255.255.255.0 !
secondary address-family ipv4
ip address 10.1.56.6 255.255.255.0 network 10.1.56.0 mask 255.255.255.0
no ip split-horizon eigrp 1 network 10.1.57.0 mask 255.255.255.0
standby version 2 network 10.1.58.0 mask 255.255.255.0
standby 1 ip 10.1.56.1 aggregate-address 10.1.56.0 255.255.254.0 summary-only
standby 1 ipv6 autoconfig neighbor 10.1.1.5 activate
standby 1 priority 105 neighbor 10.1.36.0 activate
standby 1 preempt no neighbor 2001:DB8:36:1::16 activate
ipv6 address 2001:DB8:1:56::6/64 exit-address-family
ipv6 address 2001:DB8:1:57::6/64 !
ipv6 address 2001:DB8:1:88::6/64 address-family ipv6
ipv6 nd ra interval 40 network 2001:DB8:1:56::/64
ipv6 eigrp 1 network 2001:DB8:1:57::/64
! network 2001:DB8:1:88::/64
interface Serial1/0 aggregate-address 2001:DB8:1:56::/63 summary-only
ip address 10.1.36.1 255.255.255.254 neighbor 2001:DB8:36:1::16 activate
exit-address-family
!
ipv6 router eigrp 1
Configs
R# Configs
H1 interface Ethernet0/0
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
Optional Labs
© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 115
6PE Lab
© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 116
6PE Lab Agenda
R1 router ospfv3 1
address-family ipv6
redistribute bgp 109
!
router bgp 109
address-family ipv6
redistribute ospf 1
6PE Lab: Enabling OSPFv3 on PE-CE link
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
R5 router bgp 2
!
address-family ipv6
neighbor 2001:db8:1:2::3 remote-as 109
network 2001:db8:1:5::3/128
6PE Lab: Enabling BGPv6 as a PE-CE protocol
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 AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
2001:DB8:1:2::5 4 2 14 14 5 0 0 00:08:33 1
R3#
R3#sh bgp ipv6 unicast
BGP table version is 5, local router ID is 10.1.3.1
Network Next Hop Metric LocPrf Weight Path
*> 2001:DB8:1:5::3/128
2001:DB8:1:2::5 0 0 2i
R3#
6PE Lab: Enabling BGPv6 as a PE-CE protocol
R# *BGPv4 BGPv6
R1& router bgp 109 router bgp 109
R3 neighbor 10.1.0.0 remote-as 109 address-family ipv6
neighbor 10.1.0.0 update-source L0 neighbor 10.1.0.0 remote-as 109
address-family ipv4 neighbor 10.1.0.0 update-source L0
neighbor 10.1.0.0 act neighbor 10.1.0.0 send-label
Verify that the peers has been established by using appropriate show commands
*Only R2 (RR) peering is shown as it covers all peering
Why don’t we have ipv6 neighbors?
R# BGPv6
R2 R2#sh bgp ipv6 unicast summ
BGP router identifier 10.1.0.0, local AS number 109
BGP table version is 1, main routing table version 1
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
© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 132
6PE Lab: Configs
R# Configs
ipv6 unicast-routing
R1 ipv6 cef
!
interface Loopback0
ip address 10.1.0.1 255.255.255.255
!
interface Ethernet1/0
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
neighbor 10.1.0.0 remote-as 109
neighbor 10.1.0.0 update-source Loopback0
neighbor 10.1.3.1 remote-as 109
neighbor 10.1.3.1 update-source Loopback0
!
address-family ipv6
redistribute ospf 1
neighbor 10.1.0.0 activate
neighbor 10.1.0.0 send-label
exit-address-family
6PE Lab: Configs
R# Configs
R2 interface Loopback0
ip address 10.1.0.0 255.255.255.255
!
interface Ethernet0/0
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
neighbor 10.1.0.1 remote-as 109
neighbor 10.1.0.1 update-source Loopback0
neighbor 10.1.3.1 remote-as 109
neighbor 10.1.3.1 update-source Loopback0
!
address-family ipv6
neighbor 10.1.0.1 activate
neighbor 10.1.0.1 send-label
neighbor 10.1.0.1 route-reflection-client
neighbor 10.1.3.1 activate
neighbor 10.1.3.1 send-label
neighbor 10.1.3.1 route-reflection-client
6PE Lab: Configs
R# Configs
R3 ipv6 unicast-routing
ipv6 cef
!
interface Loopback0
ip address 10.1.3.1 255.255.255.255
!
interface Ethernet0/0
no ip address
ipv6 address 2001:DB8:1:2::3/64
!
interface Ethernet1/0
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
bgp log-neighbor-changes
no bgp default ipv4-unicast
neighbor 10.1.0.0 remote-as 109
neighbor 10.1.0.0 update-source Loopback0
neighbor 2001:DB8:1:2::5 remote-as 2
!
address-family ipv6
neighbor 10.1.0.0 activate
neighbor 10.1.0.0 send-label
neighbor 2001:DB8:1:2::5 activate
exit-address-family
6PE Lab: Configs
R# Configs
ipv6 unicast-routing
R4 !
interface Loopback0
ipv6 address 2001:db8::4/128
ipv6 oapf 1 area 0
!
interface Ethernet1/0
ipv6 address 2001:DB8:1:1::1/64
ipv6 ospf 1 area 0
6PE Lab: Configs
R# Configs
ipv6 unicast-routing
R5 ipv6 cef
!
interface Loopback0
ipv6 address 2001:DB8:1:5::3/128
!
interface Ethernet0/0
ipv6 address 2001:DB8:1:2::5/64
!
router bgp 2
neighbor 2001:DB8:1:2::3 remote-as 109
!
address-family ipv6
network 2001:DB8:1:5::3/128
neighbor 2001:DB8:1:2::3 activate
exit-address-family
6VPE Lab
© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 138
6VPE Lab Agenda
R# BGPv6
R4 R4#sh ipv6 route ::/0
Routing entry for ::/0
Known via "static", distance 1, metric 0
Backup from "static [2]"
Route count is 1/1, share count 0
Routing paths:
2001:DB8:1:1::1
Last updated 00:01:22 ago
R1 R1#sh ipv6 route vrf 6vpe | incl 2001:DB8::/64
S 2001:DB8::/64 [1/0]
R# Static routes
R3 R3#sh bgp vpnv6 uni all summ | incl 2001
2001:DB8:1:2::5 4 2 57 59 4 0 0 00:48:33 1
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
© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 152
6VPE Lab: Configs
R# Configs
vrf definition 6vpe
R1 rd 1:1
route-target export 1:1
route-target import 1:1
!
address-family ipv6
exit-address-family
!
ipv6 unicast-routing
ipv6 cef
!
interface Loopback0
ip address 10.1.0.1 255.255.255.255
!
interface Ethernet0/0
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
bgp log-neighbor-changes
no bgp default ipv4-unicast
neighbor 10.1.0.0 remote-as 109
neighbor 10.1.0.0 update-source Loopback0
!
address-family vpnv6
neighbor 10.1.0.0 activate
neighbor 10.1.0.0 send-community extended
exit-address-family
!
address-family ipv6 vrf 6vpe
redistribute static
exit-address-family
6VPE Lab: Configs
R# Configs
R2 interface Loopback0
ip address 10.1.0.0 255.255.255.255
!
interface Ethernet0/0
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
no bgp default ipv4-unicast
neighbor 10.1.0.1 remote-as 109
neighbor 10.1.0.1 update-source Loopback0
neighbor 10.1.3.1 remote-as 109
neighbor 10.1.3.1 update-source Loopback0
!
address-family vpnv6
neighbor 10.1.0.1 activate
neighbor 10.1.0.1 route-reflection-client
neighbor 10.1.3.1 activate
neighbor 10.1.3.1 route-reflection-client
6VPE Lab: Configs
R# Configs
vrf definition 6vpe
R3 rd 1:1
route-target export 1:1
route-target import 1:1
!
address-family ipv6
exit-address-family
!
ipv6 unicast-routing
ipv6 cef
!
interface Loopback0
ip address 10.1.3.1 255.255.255.255
!
interface Ethernet0/0
vrf forwarding 6vpe
ip address 10.1.1.2 255.255.255.0
ipv6 address 2001:DB8:1:2::3/64
!
interface Ethernet1/0
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
bgp log-neighbor-changes
no bgp default ipv4-unicast
neighbor 10.1.0.0 remote-as 109
neighbor 10.1.0.0 update-source Loopback0
!
address-family vpnv6
neighbor 10.1.0.0 activate
neighbor 10.1.0.0 send-community extended
exit-address-family
!
address-family ipv6 vrf 6vpe
neighbor 2001:DB8:1:2::5 remote-as 2
neighbor 2001:DB8:1:2::5 activate
exit-address-family
6VPE Lab: Configs
R# Configs
ipv6 unicast-routing
R4 ipv6 cef
!
interface Ethernet0/0
ipv6 address 2001:DB8:1:1::4/64
!
interface Ethernet1/0
ipv6 address 2001:DB8::/64 eui-64
!
ipv6 route ::/0 2001:DB8:1:1::1
6VPE Lab: Configs
R# Configs
ipv6 unicast-routing
R5 ipv6 cef
!
interface Loopback0
ipv6 address 2001:DB8:1:5::3/128
!
interface Ethernet0/0
ipv6 address 2001:DB8:1:2::5/64
!
router bgp 2
no bgp default ipv4-unicast
neighbor 2001:DB8:1:2::3 remote-as 109
!
address-family ipv6
network 2001:DB8:1:5::3/128
neighbor 2001:DB8:1:2::3 activate
exit-address-family
IPv6 Multicast Lab
© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 158
IPv6 Multicast Lab Agenda
R# Multicast configuration
R1 ipv6 multicast-routing
!
ipv6 pim rp-address 2001:db8:1::
R2 ipv6 multicast-routing
!
ipv6 pim rp-address 2001:db8:1::
R3 ipv6 multicast-routing
!
ipv6 pim rp-address 2001:db8:1::
Receiver interface Ethernet0/0
ipv6 mld join-group FF1E::1
Multicast Lab: IPv6 Multicast with static RP
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# Multicast configuration
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#
Multicast Lab: IPv6 Multicast with static RP
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# Multicast configuration
R2 R2#sh ipv6 pim nei
PIM Neighbor Table
Mode: B - Bidir Capable, G - GenID Capable
Neighbor Address Interface Uptime Expires Mode DR pri
R# Multicast configuration
R3 R3#sh ipv6 mroute
Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group,
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#
Multicast Lab: IPv6 Multicast with static RP
Answers
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# Multicast configuration
R1 ipv6 pim rp-address 2001:db8:1::1
R# Multicast configuration
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
Immediate Outgoing interface list:
Ethernet0/0, Forward, 00:09:35/never
R3#
Multicast Lab: IPv6 Multicast with Embedded RP
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# Multicast configuration
R1 R1#sh ipv6 mroute FF7E:130:2001:DB8:1::99
Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group,
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
R1#
Multicast Lab: IPv6 Multicast with Embedded RP
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# Multicast configuration
R1 R1#sh ipv6 mroute FF7E:130:2001:DB8:1::99
Multicast Routing Table
..
© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 173
Multicast Lab: Configs
R# Configs
R1 ipv6 unicast-routing
ipv6 cef
ipv6 multicast-routing
!
interface Loopback0
ipv6 address 2001:DB8:1::1/128
ipv6 ospf 1 area 0
!
interface Ethernet0/0
ipv6 address 2001:DB8:1:1::1/64
ipv6 ospf 1 area 0
!
interface Serial1/0
ipv6 address 2001:DB8:1::3/127
ipv6 ospf 1 area 0
!
interface Serial2/0
ipv6 address 2001:DB8::3/64
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
Multicast Lab: Configs
R# Configs
ipv6 unicast-routing
R2 ipv6 cef
ipv6 multicast-routing
!
interface Loopback0
ipv6 address 2001:DB8:1::/128
ipv6 ospf 1 area 0
!
interface Ethernet0/0
ipv6 address 2001:DB8:1::4/127
ipv6 ospf 1 area 0
!
interface Serial1/0
ipv6 address 2001:DB8:1::2/127
ipv6 ospf 1 area 0
!
ipv6 pim rp-address 2001:DB8:1::
ipv6 router ospf 1
Multicast Lab: Configs
R# Configs
R3 ipv6 unicast-routing
ipv6 cef
ipv6 multicast-routing
!
interface Loopback0
ipv6 address 2001:DB8:1:3::3/128
ipv6 ospf 1 area 0
!
interface Ethernet0/0
ipv6 address 2001:DB8:1:2::3/64
ipv6 ospf 1 area 0
!
interface Ethernet1/0
ipv6 address 2001:DB8:1::5/127
ipv6 ospf 1 area 0
!
interface Serial2/0
ipv6 address 2001:DB8::5/64
ipv6 ospf 1 area 0
!
ipv6 pim rp-address 2001:DB8:1::
ipv6 router ospf 1
Multicast Lab: Configs
R# Configs
R4(Source) no ipv6 cef
!
interface Ethernet0/0
ipv6 address 2001:DB8:1:1::4/64
!
© 2012
2011 Cisco and/or its affiliates. All rights reserved. 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.
© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 180