• Save
IPV6 Hands on Lab
 

IPV6 Hands on Lab

on

  • 2,037 views

The “Hands on Experience with IPv6 Routing and Services” Techtorial will provide attendees an opportunity to configure, troubleshoot, design and implement an IPv6 network using IPv6 technologies ...

The “Hands on Experience with IPv6 Routing and Services” Techtorial will provide attendees an opportunity to configure, troubleshoot, design and implement an 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 of an IPv4 network where you will get the opportunity to configure and implement IPv6 based on the requirements on the network, i.e., where would you deploy dual stack, where it make sense to do funneling and how to deploy IPv6 routing protocols without impacting your existing Network infrastructure.

Statistics

Views

Total Views
2,037
Views on SlideShare
2,037
Embed Views
0

Actions

Likes
4
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

IPV6 Hands on Lab IPV6 Hands on Lab Presentation Transcript

  • © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Connect 11© 2012 Cisco and/or its affiliates. All rights reserved.Toronto, CanadaMay 30, 2013IPv6 Hands-on LabFaraz Shamim, Technical LeaderHarold Ritter, Technical Leader
  • Prerequisites: Session AbstractThis 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; IPv6addressing, IPv6 neighbor discovery, HSRPv6, static routing, OSPFv3, EIGRPv6 andBGPv6. You will be provided with a scenario made up with an IPv4 network where you willget the opportunity to configure and implement IPv6 based on the requirements and needson the network. For e.g where would you deploy dual stack, where it make sense to dotunneling and how to deploy an IPv6 routing protocols without impacting your existingNetwork 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 atCisco Connect in Toronto and you are extremely enthusiastic about deploying IPv6 in yournetwork. Since this is your first time with IPv6, you want to experiment things at your own beforetalking to your ISP about IPv6 connectivity. Your goal is to make your own network IPv6ready 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 withdual stack as much as possible. In the event you can not use dual stack you will usetunneling techniques. IPv4 piece is already up and running in the network and nothing needs to be done on IPv4side R1 is connected to IPv6 Internet. For this purpose we have assigned a loopback 1 with anipv6 address of 2004:db8::1/128. So if any router can ping this address, it means it canaccess IPv6 internet
  • Lab Topology
  • © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 6Lab 1 : IPv6Addressing &Stateless AddressAuto Configuration(SLAAC)
  • Lab 1 IPv6 Unique Local Address The first thing you would like to do is to make sure your devices are capable ofrunning IPv6. After you have verified that with your vendor, now you are readyto 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 staticrouting when you move to IPv6 Your task is to enable IPv6 between R4 and H1. You want to make sure you donot 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 forthis purpose
  • Lab 1 IPv6 Stateless Auto-Configuration (SLAAC) Your plan is to test the plug and play behaviour of IPv6. So you only assignedthe IPv6 unique local address on R4 interface facing H1 and see if you get anIPv6 address assigned automatically on H1 from R4 (Refer to Slide 39 for IPv6addressing example) You want to see how EUI-64 method works so you are using that on R4 duringthe address assignment with /64 mask. Assign this unique local address on R4 using subnetting as shown in the nextslide Ping R4’s link local and Unique local IPv6 address from H1
  • Lab 1: IPv6 Addressing & SLAAC
  • R# ConfigsR4 R4(config)#ipv6 unicast-routingR4(config)#interface e0/0R4(config-if)#ipv6 address fd01:db8:1:41::/64 EUI-64R4(config-if)#endH1 H1(config)#interface e0/0H1(config-if)#ipv6 enableH1(config-if)#ipv6 address autoconfigH1(config-if)#endLab 1 IPv6 Unique Local & SLAAC: Configs
  • R4 H1R4#sh ipv6 int e0/0Ethernet0/0 is up, line protocol is upIPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5400No 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::1FF02::2FF02::1:FF00:5400MTU is 1500 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabledICMP unreachables are sentND DAD is enabled, number of DAD attempts: 1ND 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 secondsND router advertisements live for 1800 secondsND advertised default router preference is MediumHosts use stateless autoconfig for addresses.H1#sh ipv6 int e0/0Ethernet0/0 is up, line protocol is upIPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5700No Virtual link-local address(es):Stateless address autoconfig enabledGlobal 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 604661Joined group address(es):FF02::1FF02::1:FF00:5700MTU is 1500 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabledICMP unreachables are sentND DAD is enabled, number of DAD attempts: 1ND reachable time is 30000 milliseconds (using 30000)Default router is FE80::A8BB:CCFF:FE00:5400 on Ethernet0/0Lab 1 IPv6 Unique Local & SLAAC: Verification
  • R# Verification commandsH1 H1#ping FE80::A8BB:CCFF:FE00:5400Output Interface: Ethernet0/0Type 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 msH1#Note: the last 64 bit address may be different from A8BB:CCFF:FE00:5400, verify with show ipv6interface on R4 E0/0H1 H1#ping FD01:DB8:1:41:A8B8:CCFF:FE00:5400Type 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 msH1#Note: the last 64 bit address may be different from A8BB:CCFF:FE00:5400, verify with show ipv6interface on R4 E0/0Lab 1 IPv6 Unique Local & SLAAC: Verification
  • R4 H1R4#deb ipv6 ndICMP Neighbor Discovery events debugging is onICMPv6-ND: Request to send RA for FE80::A8BB:CCFF:FE00:5400ICMPv6-ND: Setup RA from FE80::A8BB:CCFF:FE00:5400 to FF02::1 onEthernet0/0ICMPv6-ND: MTU = 1500ICMPv6-ND: prefix = FD01:DB8:1:41::/64 onlink autoconfigICMPv6-ND: 2592000/604800 (valid/preferred)ICMPv6-ND: Request to send RA for FE80::A8BB:CCFF:FE00:5400ICMPv6-ND: Setup RA from FE80::A8BB:CCFF:FE00:5400 to FF02::1 onEthernet0/0ICMPv6-ND: MTU = 1500ICMPv6-ND: prefix = FD01:DB8:1:41::/64 onlink autoconfigICMPv6-ND: 2592000/604800 (valid/preferred)R4#H1#deb ipv6 ndICMP Neighbor Discovery events debugging is onICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5400 onEthernet0/0ICMPv6-ND: Prefix : FD01:DB8:1:1::, Length: 64, Vld Lifetime: 2592000,Prf Lifetime: 604800, PI Flags: C0ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address AutoconfigFD01:DB8:1:41::/64 eui-64, FD01:DB8:1:41:A8BB:CCFF:FE00:5700FD01:DB8:1:41:A8BB:CCFF:FE00:5700/64 is existingICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5400 onEthernet0/0ICMPv6-ND: Prefix : FD01:DB8:1:1::, Length: 64, Vld Lifetime: 2592000,Prf Lifetime: 604800, PI Flags: C0ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address AutoconfigFD01:DB8:1:41::/64 eui-64, FD01:DB8:1:41:A8BB:CCFF:FE00:5700FD01:DB8:1:41:A8BB:CCFF:FE00:5700/64 is existingH1#Lab 1 IPv6 SLAAC: Debugs
  • 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 address2001:db8:1::/48 from their block Instead of removing the unique local address from site 1 you decided to keep itand 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 useEUI-64 bit method for global addressing. You want to make sure this is themethod you follow from now on For the manual assignment you will use the router number as the last 4 bits outof 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 willconfigure two additional IPv6 global addresses on R5 and R6 Assign IPv6 global unicast address on site 1 and site 2 by using subnetting asshown in the next slide
  • Lab 1b: IPv6 Global Unicast address & SLAAC
  • R# ConfigsR4 R4(config)#ipv6 unicast-routingR4(config)#interface loop0R4(config-if)#ipv6 address 2001:db8:1:1::4/128R4(config)#interface e0/0R4(config-if)#ipv6 address 2001:db8:1:41::4/64R4(config-if)#endR5 R5(config)#ipv6 unicast-routingR5(config)#interface loop0R5(config-if)#ipv6 address 2001:db8:1:1::5/128R5(config)#interface e0/0R5(config-if)#ipv6 address 2001:db8:1:56::5/64R5(config-if)#ipv6 address 2001:db8:1:57::5/64R5(config-if)#ipv6 address 2001:db8:1:58::5/64R5(config-if)#endLab 1 IPv6 Global Unicast address & SLAAC: Configs
  • R# ConfigsR6 R4(config)#ipv6 unicast-routingR6(config)#interface loop0R6(config-if)#ipv6 address 2001:db8:1:1::6/128R6(config)#interface e0/0R6(config-if)#ipv6 address 2001:db8:1:56::6/64R6(config-if)#ipv6 address 2001:db8:1:57::6/64R6(config-if)#ipv6 address 2001:db8:1:58::6/64R6(config-if)#endH2 H2(config)#interface e0/0H2(config-if)#ipv6 enableH2(config-if)#ipv6 address autoconfigH2(config-if)#endLab 1 IPv6 Global Unicast address & SLAAC:Configs
  • R4 Loopback 0 R4 Ethernet0/0R4#sh ipv6 int lo 0Loopback0 is up, line protocol is upIPv6 is enabled, link-local address isFE80::A8BB:CCFF:FE00:5900No Virtual link-local address(es):Global unicast address(es):2001:DB8:1:1::4, subnet is 2001:DB8:1:1::4/128Joined group address(es):FF02::1FF02::2FF02::1:FF00:4FF02::1:FF00:5900MTU is 1514 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabledICMP unreachables are sentND DAD is not supportedND reachable time is 30000 milliseconds (using 30000)ND RAs are suppressed (periodic)Hosts use stateless autoconfig for addresses.R4#R4#sh ipv6 int e0/0Ethernet0/0 is up, line protocol is upIPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5400No Virtual link-local address(es):Global unicast address(es):2001:DB8:1:41::4, subnet is 2001:DB8:1:41::/64FD01:DB8:1:41:A8BB:CCFF:FE00:5400, subnet is FD01:DB8:1:41::/64 [EUI]Joined group address(es):FF02::1FF02::2FF02::1:FF00:4FF02::1:FF00:5400MTU is 1500 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabledICMP unreachables are sentND DAD is enabled, number of DAD attempts: 1ND 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 secondsND router advertisements live for 1800 secondsND advertised default router preference is MediumHosts use stateless autoconfig for addresses.R4#Lab 1 IPv6 Global Unicast address: Verification
  • R5 Loopback 0 R5 Ethernet0/0R5#sh ipv6 int lo 0Loopback0 is up, line protocol is upIPv6 is enabled, link-local address isFE80::A8BB:CCFF:FE00:5A00No Virtual link-local address(es):Global unicast address(es):2001:DB8:1:1::5, subnet is 2001:DB8:1:1::5/128Joined group address(es):FF02::1FF02::2FF02::1:FF00:5FF02::1:FF00:5A00MTU is 1514 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabledICMP unreachables are sentND DAD is not supportedND reachable time is 30000 milliseconds (using 30000)ND RAs are suppressed (periodic)Hosts use stateless autoconfig for addresses.R5#R5#sh ipv6 int e0/0Ethernet0/0 is up, line protocol is upIPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5A00No Virtual link-local address(es):Global unicast address(es):2001:DB8:1:56::5, subnet is 2001:DB8:1:56::/642001:DB8:1:57::5, subnet is 2001:DB8:1:57::/642001:DB8:1:58::5, subnet is 2001:DB8:1:58::/64Joined group address(es):FF02::1FF02::2FF02::1:FF00:5FF02::1:FF00:5A00MTU is 1500 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabledICMP unreachables are sentND DAD is enabled, number of DAD attempts: 1ND 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 secondsND router advertisements live for 1800 secondsND advertised default router preference is MediumHosts use stateless autoconfig for addresses.Lab 1 IPv6 Global Unicast address: Verification
  • R6 Loopback 0 R6 Ethernet0/0R6#sh ipv6 int lo 0Loopback0 is up, line protocol is upIPv6 is enabled, link-local address isFE80::A8BB:CCFF:FE00:5B00No Virtual link-local address(es):Global unicast address(es):2001:DB8:1:1::6, subnet is 2001:DB8:1:1::6/128Joined group address(es):FF02::1FF02::2FF02::1:FF00:6FF02::1:FF00:5B00MTU is 1514 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabledICMP unreachables are sentND DAD is not supportedND reachable time is 30000 milliseconds (using 30000)ND RAs are suppressed (periodic)Hosts use stateless autoconfig for addresses.R6#R6#sh ipv6 int e0/0Ethernet0/0 is up, line protocol is upIPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5B00No Virtual link-local address(es):Global unicast address(es):2001:DB8:1:56::6, subnet is 2001:DB8:1:56::/642001:DB8:1:57::6, subnet is 2001:DB8:1:57::/642001:DB8:1:58::6, subnet is 2001:DB8:1:58::/64Joined group address(es):FF02::1FF02::2FF02::1:FF00:6FF02::1:FF00:5B00MTU is 1500 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabledICMP unreachables are sentND DAD is enabled, number of DAD attempts: 1ND 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 secondsND router advertisements live for 1800 secondsND advertised default router preference is MediumHosts use stateless autoconfig for addresses.Lab 1 IPv6 Global Unicast address: Verification
  • H1 Ethernet0/0 H2 Ethernet0/0H1#sh ipv6 int e0/0Ethernet0/0 is up, line protocol is upIPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5700No Virtual link-local address(es):Stateless address autoconfig enabledGlobal unicast address(es):2001:DB8:1:41:A8BB:CCFF:FE00:5700, subnet is 2001:DB8:1:41::/64[EUI/CAL/PRE]valid lifetime 2591845 preferred lifetime 604645FD01:DB8:1:41:A8BB:CCFF:FE00:5700, subnet is FD01:DB8:1:41::/64[EUI/CAL/PRE]valid lifetime 2591845 preferred lifetime 604645Joined group address(es):FF02::1FF02::1:FF00:5700MTU is 1500 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabledICMP unreachables are sentND DAD is enabled, number of DAD attempts: 1ND reachable time is 30000 milliseconds (using 30000)Default router is FE80::A8BB:CCFF:FE00:5400 on Ethernet0/0H1#H2#sh ipv6 int e0/0Ethernet0/0 is up, line protocol is upIPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5D00No Virtual link-local address(es):Stateless address autoconfig enabledGlobal unicast address(es):2001:DB8:1:56:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:56::/64[EUI/CAL/PRE]valid lifetime 2591989 preferred lifetime 6047892001:DB8:1:57:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:57::/64[EUI/CAL/PRE]valid lifetime 2591989 preferred lifetime 6047892001:DB8:1:58:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:58::/64[EUI/CAL/PRE]valid lifetime 2591989 preferred lifetime 604789Joined group address(es):FF02::1FF02::1:FF00:5D00MTU is 1500 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabledICMP unreachables are sentND DAD is enabled, number of DAD attempts: 1ND reachable time is 30000 milliseconds (using 30000)Default router is FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0H2#Lab 1 IPv6 SLAAC: Verification
  • R# Verification commandsH2 H2#ping 2001:db8:1:56::5Type 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 msH2#ping 2001:db8:1:57::5Type 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 msH2#ping 2001:db8:1:58::5Type 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 msH2#ping 2001:db8:1:56::6Type 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 msH2#ping 2001:db8:1:57::6Type 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 msH2#ping 2001:db8:1:58::6Type 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 msH2#Lab 1 IPv6 Global Unicast address: Verification
  • R# Verification commandsH1 H1#ping 2001:DB8:1:41::4Type 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 msH1#Lab 1 IPv6 SLAAC: Verification
  • R5 & R6R5#deb ipv6 ndICMPv6-ND: Request to send RA for FE80::A8BB:CCFF:FE00:5A00ICMPv6-ND: Setup RA from FE80::A8BB:CCFF:FE00:5A00 to FF02::1 onEthernet0/0ICMPv6-ND: MTU = 1500ICMPv6-ND: prefix = 2001:DB8:1:56::/64 onlink autoconfigICMPv6-ND: 2592000/604800 (valid/preferred)ICMPv6-ND: prefix = 2001:DB8:1:57::/64 onlink autoconfigICMPv6-ND: 2592000/604800 (valid/preferred)ICMPv6-ND: prefix = 2001:DB8:1:58::/64 onlink autoconfigICMPv6-ND: 2592000/604800 (valid/preferred)R5#ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5B00 on Ethernet0/0ICMPv6-ND: Prefix : 2001:DB8:1:56::, Length: 64, Vld Lifetime: 2592000, PrfLifetime: 604800, PI Flags: C0ICMPv6-ND: Prefix : 2001:DB8:1:57::, Length: 64, Vld Lifetime: 2592000, PrfLifetime: 604800, PI Flags: C0ICMPv6-ND: Prefix : 2001:DB8:1:58::, Length: 64, Vld Lifetime: 2592000, PrfLifetime: 604800, PI Flags: C0R5#R6#deb ipv6 ndICMPv6-ND: Request to send RA for FE80::A8BB:CCFF:FE00:5B00ICMPv6-ND: Setup RA from FE80::A8BB:CCFF:FE00:5B00 to FF02::1 onEthernet0/0ICMPv6-ND: MTU = 1500ICMPv6-ND: prefix = 2001:DB8:1:56::/64 onlink autoconfigICMPv6-ND: 2592000/604800 (valid/preferred)ICMPv6-ND: prefix = 2001:DB8:1:57::/64 onlink autoconfigICMPv6-ND: 2592000/604800 (valid/preferred)ICMPv6-ND: prefix = 2001:DB8:1:58::/64 onlink autoconfigICMPv6-ND: 2592000/604800 (valid/preferred)R6#ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0ICMPv6-ND: Prefix : 2001:DB8:1:56::, Length: 64, Vld Lifetime: 2592000, PrfLifetime: 604800, PI Flags: C0ICMPv6-ND: Prefix : 2001:DB8:1:57::, Length: 64, Vld Lifetime: 2592000, PrfLifetime: 604800, PI Flags: C0ICMPv6-ND: Prefix : 2001:DB8:1:58::, Length: 64, Vld Lifetime: 2592000, PrfLifetime: 604800, PI Flags: C0H2#Lab 1 IPv6 SLAAC: Debugs
  • H2 & H1H2#deb ipv6 ndICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5B00 on Ethernet0/0ICMPv6-ND: Prefix : 2001:DB8:1:56::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:56::/64 eui-64, 2001:DB8:1:56:A8BB:CCFF:FE00:5D002001:DB8:1:56:A8BB:CCFF:FE00:5D00/64 is existingICMPv6-ND: Prefix : 2001:DB8:1:57::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:57::/64 eui-64, 2001:DB8:1:57:A8BB:CCFF:FE00:5D002001:DB8:1:57:A8BB:CCFF:FE00:5D00/64 is existingH2#ICMPv6-ND: Prefix : 2001:DB8:1:58::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:58::/64 eui-64, 2001:DB8:1:58:A8BB:CCFF:FE00:5D002001:DB8:1:58:A8BB:CCFF:FE00:5D00/64 is existingH2#H1#deb ipv6 ndICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5900 on Ethernet0/0ICMPv6-ND: Prefix : 2001:DB8:1:41::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:41::/64 eui-64, 2001:DB8:1:41:A8BB:CCFF:FE00:5C002001:DB8:1:41:A8BB:CCFF:FE00:5C00/64 is existingICMPv6-ND: Prefix : FD01:DB8:1:41::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig FD01:DB8:1:41::/64 eui-64, FD01:DB8:1:41:A8BB:CCFF:FE00:5C00FD01:DB8:1:41:A8BB:CCFF:FE00:5C00/64 is existingH1#Lab 1 IPv6 SLAAC: Debugs
  • © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 26Lab 2 : IPv6 NeighborDiscovery
  • Lab 2 Neighbor Discovery: RS & RA You already tested plug and play behaviour of IPv6 in Site 1. Now you want toplay 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 nddebugs and enable autoconfigs again to see the RA/RS. Turn on debug ipv6 nd on R4 and H1
  • R# ConfigsR4 R4(config)#interface e0/0R4(config-if)#ipv6 nd ra interval 30R4(config-if)#endH1 H1(config)#interface e0/0H1(config-if)#no ipv6 address autoconfigH1(config-if)#no ipv6 enableH1(config-if)#ipv6 enableH1(config-if)#ipv6 address autoconfigH1(config-if)#endLab 2 IPv6 Neighbor discovery: Configs
  • R4R4#sh ipv6 int e0/0Ethernet0/0 is up, line protocol is upIPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5900No Virtual link-local address(es):Global unicast address(es):2001:DB8:1:41::4, subnet is 2001:DB8:1:41::/64FD01:DB8:1:41:A8BB:CCFF:FE00:5900, subnet is FD01:DB8:1:41::/64 [EUI]Joined group address(es):FF02::1FF02::2FF02::1:FF00:4FF02::1:FF00:5900MTU is 1500 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabledICMP unreachables are sentND DAD is enabled, number of DAD attempts: 1ND 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 secondsND router advertisements live for 1800 secondsND advertised default router preference is MediumHosts use stateless autoconfig for addresses.R4#Lab 2 IPv6 Neighbor discovery: Verification
  • H1H1(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, UpH1(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/0Lab 2 IPv6 Neighbor discovery: Debugs
  • Lab 2 Neighbor Discovery: DAD, NS & NA You want to test the DAD, NS & NA mechanism of IPv6. For that you turned onIPv6 neighbor discovery debug on R5 & R6 Assign a new address 2001:db8:1:59::5/64 on both R5 and R6 Ethernetinterface The debug will show the algorithm performed for DAD procedure. This DAD isthe first thing that occurs when any IPv6 address is assigned on an interface After testing the DAD procedure, remove the IPv6 address of2001: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 NAtakes place between them
  • R# ConfigsR5 R5(config)#int e0/0R5(config-if)#ipv6 address 2001:db8:1:59::5/64R6 R6(config)#int e0/0R6(config-if)#ipv6 address 2001:db8:1:59::6/64Lab 2 IPv6 Neighbor discovery: Configs
  • R4R6#sh ipv6 intEthernet0/0 is up, line protocol is upIPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5B00No Virtual link-local address(es):Global unicast address(es):2001:DB8:1:56::6, subnet is 2001:DB8:1:56::/642001:DB8:1:57::6, subnet is 2001:DB8:1:57::/642001:DB8:1:58::6, subnet is 2001:DB8:1:58::/642001:DB8:1:59::5, subnet is 2001:DB8:1:59::/64Joined group address(es):FF02::1FF02::2FF02::1:FF00:5FF02::1:FF00:6FF02::1:FF00:5B00MTU is 1500 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabled…R5#sh ipv6 int e0/0 | i DUP2001:DB8:1:59::5, subnet is 2001:DB8:1:59::/64 [DUP]Lab 2 IPv6 Neighbor discovery: Verification
  • R6R6(config-if)#ipv6 address 2001:db8:1:59::5/64*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/0R5(config-if)#ipv6 address 2001:db8:1:59::5/64*Jan 30 21:48:57.826: ICMPv6-ND: 2592000/604800 (valid/preferred)*Jan 30 21:49:39.078: IPv6-Addrmgr-ND: Received prefix PI-flag change notification: prefix 2001:DB8:1:59::/64 onlink (was not-onlink)*Jan 30 21:49:39.078: IPv6-Addrmgr-ND: DAD request for 2001:DB8:1:59::5 on Ethernet0/0*Jan 30 21:49:39.079: ICMPv6-ND: Sending NS 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/0Lab 2 IPv6 Neighbor discovery: Debugs
  • R# ConfigsR5 R5(config)#int e0/0R5(config-if)#no ipv6 address 2001:db8:1:59::5/64R6 R6(config)#int e0/0R6(config-if)#no ipv6 address 2001:db8:1:59::5/64Lab 2 IPv6 Neighbor discovery: Configs
  • R5R5#ping 2001:db8:1:56::6Type 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 msR5#*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::6R5#*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:5B00Lab 2 IPv6 Neighbor discovery: Debugs
  • 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 Ethernetinterface 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::/64to 0 and valid lifetime to 50 on both R5 & R6. (Note, may have to shut no shut E0/0 on H2to rewrite the old valid & prefer lifetime) You noticed that the old prefix of 2001:db8:1:58::/64 is showing as deprecated on H2. NoteDEP 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::/64to 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 IPv6nd prefix command from the Ethernet interfaces of both R5 and R6
  • R# ConfigsR5 R5(config)#interface e0/0R5(config-if)#ipv6 nd ra interval 40R5(config-if)#ipv6 address 2001:db8:1:88::5/64R5(config-if)#ipv6 nd prefix 2001:db8:1:58::/64 50 0R5(config-if)#endR6 R6(config)#interface e0/0R6(config-if)#ipv6 nd ra interval 40R6(config-if)#ipv6 address 2001:db8:1:88::6/64R6(config-if)#ipv6 nd prefix 2001:db8:1:58::/64 50 0R6(config-if)#endLab 2 IPv6 Neighbor discovery: Configs
  • H2H2#sh ipv6 int e0/0Ethernet0/0 is up, line protocol is upIPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5D00No Virtual link-local address(es):Stateless address autoconfig enabledGlobal 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 6047942001:DB8:1:57:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:57::/64 [EUI/CAL/PRE]valid lifetime 2591994 preferred lifetime 6047942001:DB8:1:58:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:58::/64 [EUI/CAL]valid lifetime 47 preferred lifetime 02001:DB8:1:88:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:88::/64 [EUI/CAL/PRE]valid lifetime 2591994 preferred lifetime 604794Joined group address(es):FF02::1FF02::1:FF00:5D00MTU is 1500 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabledICMP unreachables are sentLab 2 IPv6 Neighbor discovery: Verification
  • H2H2#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:5D002001: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:5D002001: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:5D002001: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:5D002001:DB8:1:88:A8BB:CCFF:FE00:5D00/64 is existingLab 2 IPv6 Neighbor discovery: Debugs
  • R# ConfigsR5 R5(config)#interface e0/0R5(config-if)#ipv6 nd prefix 2001:db8:1:58::/64 0 0R5(config-if)#endR6 R6(config)#interface e0/0R6(config-if)#ipv6 nd prefix 2001:db8:1:58::/64 0 0R6(config-if)#endLab 2 IPv6 Neighbor discovery: Configs
  • H2H2#sh ipv6 int e0/0Ethernet0/0 is up, line protocol is upIPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5D00No Virtual link-local address(es):Stateless address autoconfig enabledGlobal 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 6047862001:DB8:1:57:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:57::/64 [EUI/CAL/PRE]valid lifetime 2591986 preferred lifetime 6047862001:DB8:1:88:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:88::/64 [EUI/CAL/PRE]valid lifetime 2591986 preferred lifetime 604786Joined group address(es):FF02::1FF02::1:FF00:5D00MTU is 1500 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabledICMP unreachables are sentND DAD is enabled, number of DAD attempts: 1ND reachable time is 30000 milliseconds (using 30000)Default router is FE80::A8BB:CCFF:FE00:5B00 on Ethernet0/0H2#Lab 2 IPv6 Neighbor discovery: Verification
  • H2H2#deb ipv6 ndH2#*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:5D002001: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:5D002001: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: C0H2#*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:5D002001:DB8:1:88:A8BB:CCFF:FE00:5D00/64 is existingLab 2 IPv6 Neighbor discovery: Debugs
  • R# ConfigsR5 R5(config)#interface e0/0R5(config-if)#no ipv6 add 2001:db8:1:58::5/64R5(config-if)#no ipv6 nd prefix 2001:DB8:1:58::/64R5(config-if)#endR6 R6(config)#interface e0/0R6(config-if)#no ipv6 add 2001:db8:1:58::6/64R6(config-if)#no ipv6 nd prefix 2001:DB8:1:58::/64R6(config-if)#endLab 2 IPv6 Neighbor discovery: Cleanup Configs
  • Lab 2 Neighbor Discovery: Default RouterSelection 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 thewire, looking for a router. You also noticed in the debugs that both R5 and R6 are sending RA messagestowards H2. H2 looks at RA and configures the addresses on its interfacefacing R5 & R6 After getting the address on H2, you want to make sure that H2 prefers R5 forsending all the IPv6 traffic outbound (Refer to slide 34-35 for default router selection example)
  • R# ConfigsR5 R5(config)#interface e0/0R5(config-if)#ipv6 nd router-preference highR5(config-if)#endLab 2 IPv6 Neighbor discovery: Configs
  • H2H2#sh ipv6 routerRouter FE80::A8BB:CCFF:FE00:5B00 on Ethernet0/0, last update 0 minHops 64, Lifetime 1800 sec, AddrFlag=0, OtherFlag=0, MTU=1500HomeAgentFlag=0, Preference=MediumReachable time 0 (unspecified), Retransmit time 0 (unspecified)Prefix 2001:DB8:1:56::/64 onlink autoconfigValid lifetime 2592000, preferred lifetime 604800Router FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0, last update 0 minHops 64, Lifetime 1800 sec, AddrFlag=0, OtherFlag=0, MTU=1500HomeAgentFlag=0, Preference=HighReachable time 0 (unspecified), Retransmit time 0 (unspecified)Prefix 2001:DB8:1:56::/64 onlink autoconfigValid lifetime 2592000, preferred lifetime 604800H2#sh ipv6 route ::/0Routing entry for ::/0Known via "static", distance 2, metric 0Route count is 1/1, share count 0Routing paths:FE80::A8BB:CCFF:FE00:5A00, Ethernet0/0Last updated 00:04:52 agoNote, if you do not see a default route, type the following command and make sure you have the entry from R5H2#sho ipv6 routerLab 2 IPv6 Neighbor discovery: Verification
  • © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 48Lab 3 : HSRPv6
  • 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 HSRPv6between R5 and R6 You noticed on H2 that the default route received from the HSRP active routeris a link local address You turned on the IPv6 neighbor discovery debug on H2 to see if you arereceiving any RA msgs from R5 or R6 Your primary router for HSRP in IPv4 was R5. You want to make sure R6 is aprimary router for IPv6 and when it goes down and comes back up, it shouldbecome primary again Configure HSRPv6 in autoconfig mode so it selects a virtual link local addressand advertise it as a virtual IPv6 address to hosts Configure HSRP priority & preempt command on R6 so R6 becomes theprimary router even when it goes down and comes back up (See slide 32 fordetails) Turn on deb ipv6 nd on H2 to see what link local is being advertised as adefault
  • R# ConfigsR5 R5(config-if)#standby ver 2R5(config-if)#standby 1 ipv6 autoconfigR5(config-if)#endR6 R6(config-if)#standby ver 2R6(config-if)#standby 1 ipv6 autoconfigR6(config-if)#standby 1 preemptR6(config-if)#standby 1 priority 105R6(config-if)#endLab 3 HSRPv6: Configs
  • R5 & R6R5#sh standby briefP indicates configured to preempt.|Interface Grp Pri P State Active Standby Virtual IPEt0/0 0 105 P Active local 10.1.56.6 10.1.56.1Et0/0 1 100 Standby FE80::A8BB:CCFF:FE00:5B00local FE80::5:73FF:FEA0:1R5#R6#sh standby briefP indicates configured to preempt.|Interface Grp Pri P State Active Standby Virtual IPEt0/0 0 100 Standby 10.1.56.5 local 10.1.56.1Et0/0 1 105 P Active local FE80::A8BB:CCFF:FE00:5A00FE80::5:73FF:FEA0:1R6#Lab 3 HSRPv6: Verification
  • R5 & R6R5#sh standby ethernet 0/0 1Ethernet0/0 - Group 1 (version 2)State is Standby4 state changes, last state change 00:08:17Virtual IP address is FE80::5:73FF:FEA0:1Active virtual MAC address is 0005.73a0.0001Local virtual MAC address is 0005.73a0.0001 (v2 IPv6 default)Hello time 3 sec, hold time 10 secNext hello sent in 0.624 secsPreemption disabledActive router is FE80::A8BB:CCFF:FE00:5B00, priority 105 (expires in 11.328 sec)MAC address is aabb.cc00.5b00Standby router is localPriority 100 (default 100)Group name is "hsrp-Et0/0-1" (default)R6#sh standby ethernet 0/0 1Ethernet0/0 - Group 1 (version 2)State is Active2 state changes, last state change 00:07:58Virtual IP address is FE80::5:73FF:FEA0:1Active virtual MAC address is 0005.73a0.0001Local virtual MAC address is 0005.73a0.0001 (v2 IPv6 default)Hello time 3 sec, hold time 10 secNext hello sent in 2.768 secsPreemption enabledActive router is localStandby 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)Lab 3 HSRPv6: Verification
  • R5 & R6H2#sh ipv6 route ::/0Routing entry for ::/0Known via "static", distance 2, metric 0Route count is 1/1, share count 0Routing paths:FE80::5:73FF:FEA0:1, Ethernet0/0Last updated 00:14:23 agoH2#Lab 3 HSRPv6: Verification
  • H2H2#deb ipv6 ndH2#*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:5D002001: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: C0H2#*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:5D002001: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:5D002001:DB8:1:88:A8BB:CCFF:FE00:5D00/64 is existingLab 3 HSRPv6: Debugs
  • © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 56Lab 4 : EIGRPv6
  • 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 EIGRPv6between R5 and R6 You noticed that in order to advertise the secondary address on the sameinterface in EIGRPv4 you had to turn off split horizon but in EIGRPv6 you donot have to do anything. This is because split horizon is turned off by default inEIGRP for IPv6 You also noticed that all the control packets of EIGRP for e.g. hellos aresourced 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
  • R# ConfigsR5 R5(config-if)#int loop 0R5(config-if)#ipv6 eigrp 1R5(config-if)#int e0/0R5(config-if)#ipv6 eigrp 1R5(config-if)#exitR5(config-if)#ipv6 router eigrp 1R5(config-if)#endR6 R6(config-if)#int loop 0R6(config-if)#ipv6 eigrp 1R6(config-if)#int e0/0R6(config-if)#ipv6 eigrp 1R6(config-if)#exitR6(config-if)#ipv6 router eigrp 1R6(config-if)#endLab 4 EIGRPv6: Configs
  • R5 R6R5#sh ipv6 prot | b EIGRPEIGRP-IPv6 Protocol for AS(1)Metric weight K1=1, K2=0, K3=1, K4=0, K5=0NSF-aware route hold timer is 240Router-ID: 10.1.1.5Topology : 0 (base)Active Timer: 3 minDistance: internal 90 external 170Maximum path: 16Maximum hopcount 100Maximum metric variance 1Interfaces:Loopback0Ethernet0/0Redistribution:NoneR6#sh ipv6 prot | b EIGRPEIGRP-IPv6 Protocol for AS(1)Metric weight K1=1, K2=0, K3=1, K4=0, K5=0NSF-aware route hold timer is 240Router-ID: 10.1.1.6Topology : 0 (base)Active Timer: 3 minDistance: internal 90 external 170Maximum path: 16Maximum hopcount 100Maximum metric variance 1Interfaces:Loopback0Ethernet0/0Redistribution:NoneLab 4 EIGRPv6: Verification
  • R5 & R6R5#sh ipv6 eigrp neiEIGRP-IPv6 Neighbors for AS(1)H Address Interface Hold Uptime SRTT RTO Q Seq(sec) (ms) Cnt Num0 Link-local address: Et0/0 10 00:15:15 3 100 0 3FE80::A8BB:CCFF:FE00:5600R5#R6#sh ipv6 eigrp neiEIGRP-IPv6 Neighbors for AS(1)H Address Interface Hold Uptime SRTT RTO Q Seq(sec) (ms) Cnt Num0 Link-local address: Et0/0 11 00:17:11 4 100 0 3FE80::A8BB:CCFF:FE00:5500R6#Lab 4 EIGRPv6: Verification
  • R5 & R6R5#sh ipv6 route eigrpIPv6 Routing Table - default - 9 entriesCodes: C - Connected, L - Local, S - Static, U - Per-user Static routeB - BGP, R - RIP, I1 - ISIS L1, I2 - ISIS L2IA - ISIS interarea, IS - ISIS summary, D - EIGRP, EX - EIGRP externalND - Neighbor Discovery, l - LISPO - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2D 2001:DB8:1:1::6/128 [90/409600]via FE80::A8BB:CCFF:FE00:5600, Ethernet0/0R5#R6#sh ipv6 route eigrpIPv6 Routing Table - default - 9 entriesCodes: C - Connected, L - Local, S - Static, U - Per-user Static routeB - BGP, R - RIP, I1 - ISIS L1, I2 - ISIS L2IA - ISIS interarea, IS - ISIS summary, D - EIGRP, EX - EIGRP externalND - Neighbor Discovery, l - LISPO - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2D 2001:DB8:1:1::5/128 [90/409600]via FE80::A8BB:CCFF:FE00:5500, Ethernet0/0R6#Lab 4 EIGRPv6: Verification
  • R5 & R6R5#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, originatingR6#debug ipv6 packet detail11:19:59.830: IPV6: source FE80::A8BB:CCFF:FE00:5500 (Ethernet0/0)11:19:59.830: dest FF02::A11:19:59.830: traffic class 224, flow 0x0, len 80+14, prot 88, hops 255, forward to ulpLab 4 EIGRPv6: Debugs
  • © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 64Lab 5 : IPv6 StaticRouting
  • Lab 5 IPv6 Static Routing: IPv6 Static DefaultRoute After planning and configuring all the addressing scheme for your Site 1 andSite 2, you talked with the ISP and request for IPv6 Service. You found out that your ISP has IPv6 internet connectivity only but they havenot enabled IPv6 internally in their network so no Site to Site is possible at thismoment but they can enable static routing for Site 1 and advertise Site 1 prefixover the IPv6 Internet The ISP has also asked you to enable IPv6 static default routing on R4 pointingtowards the ISP router (R1) Configure the IPv6 interface addresses on the link between ISP and R4 asshown 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 hoppointing towards R1
  • Lab 5: IPv6 Static Routing
  • R# ConfigsR1 R1(config)#int s0/0R1(config-if)#ipv6 add 2001:db8:14:1::14/127R1(config)#endR4 R4(config)#int s1/0R1(config-if)#ipv6 add 2001:db8:14:1::15/127R1(config-if)#ipv6 route ::/0 Serial 1/0 FE80::4AFF:FEA2:851R1(config)#endLab 5 IPv6 Static routing: Configs
  • R4R4#sh ipv6 route ::/0Routing entry for ::/0Known via "static", distance 1, metric 0Route count is 1/1, share count 0Routing paths:FE80::4AFF:FEA2:851, Serial1/0Last updated 00:02:15 agoLab 5 IPv6 Static routing: Verification
  • Lab 5 IPv6 Static Routing: IPv6 Static Route The ISP has configured an IPv6 static routing for the LAN address of2001:db8:1:41::/64 pointing towards R4 Since ISP is connected to IPv6 Internet, Site 1 should be able to reach anyIPv6 address on the internet ISP shared their configs and you noticed that they are using global unicastaddress 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 globaladdress on Ethernet interface Due to the limited lab environment, we will ping 2004:db8::1 from H1 and uponsuccess we will assume that we are connected to IPv6 Internet Ping 2004:db8::1 from H1 and see if its successful
  • R# ConfigsR1 R1(config)#ipv6 route 2001:db8:1:41::/64 2001:db8:14:1::15R1(config)#endLab 5 IPv6 Static routing: Configs Note, no interface needs to be specified when the next hop is global unicastaddress
  • R# VerificationR1 R1#sh ipv6 route 2001:db8:1:41::/64Routing entry for 2001:DB8:1:41::/64Known via "static", distance 1, metric 0Route count is 1/1, share count 0Routing paths:2001:DB8:14:1::15Last updated 00:11:42 agoR1#H1 H1>ping 2004:db8::1Type 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 msH1>Lab 5 IPv6 Static routing: Verification
  • © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 72Lab 6 : IPv6 ManualTunnels
  • Lab 6 IPv6 Manual Tunnels: IPv6oIP4 Site 2 has two connection to the ISP. You talked to the ISP about providing IPv6connectivity to Site 2 but you came to know that due to some limitation, the ISPcan not do dual stack on those two connections ISP gave you the option of a manual tunnel called IPv6 over IPv4 on the linkbetween 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 tunnelsource and destinations can easily be chosen as the outgoing interface A new IPv6 address needs to be configured on both side over the tunnelbetween R3 and R5 in the range 2001:db8:35:1::16/127 as shown in the nextslide (::16 on R3 side and ::17 on R5 side) Ping R5 IPv6 tunnel address from R3 and make sure it is successful todetermine that the tunnel is up and running
  • Lab 6: IPv6 Manual Tunnels
  • R# ConfigsR5 R5(config-if)#int tun 0R5(config-if)#tun source s1/0R5(config-if)#tun destination 10.1.35.0R5(config-if)#tun mode ipv6ipR5(config-if)#ipv6 address 2001:db8:35:1::17/127R5(config-if)#endR3 R3(config-if)#int tun 0R3(config-if)#tun source s1/0R3(config-if)#tun destination 10.1.35.1R3(config-if)#tun mode ipv6ipR3(config-if)#ipv6 address 2001:db8:35:1::16/127R5(config-if)#endLab 6 IPv6 Manual Tunnels: Configs
  • R3 Tunnel 0 R5 Tunnel 0R3#sh ipv6 int tun 0Tunnel0 is up, line protocol is upIPv6 is enabled, link-local address is FE80::A01:2300No Virtual link-local address(es):Global unicast address(es):2001:DB8:35:1::16, subnet is 2001:DB8:35:1::16/127Joined group address(es):FF02::1FF02::2FF02::1:FF00:16FF02::1:FF01:2300MTU is 1480 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabledICMP unreachables are sentND DAD is enabled, number of DAD attempts: 1ND reachable time is 30000 milliseconds (using 30000)ND RAs are suppressed (periodic)Hosts use stateless autoconfig for addresses.R3#R5#sh ipv6 int tun 0Tunnel0 is up, line protocol is upIPv6 is enabled, link-local address is FE80::A01:2301No Virtual link-local address(es):Global unicast address(es):2001:DB8:35:1::17, subnet is 2001:DB8:35:1::16/127Joined group address(es):FF02::1FF02::2FF02::1:FF00:17FF02::1:FF01:2301MTU is 1480 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabledICMP unreachables are sentND DAD is enabled, number of DAD attempts: 1ND reachable time is 30000 milliseconds (using 30000)ND RAs are suppressed (periodic)Hosts use stateless autoconfig for addresses.R5#Lab 6 IPv6 Manual Tunnels: Verification
  • R3R3#ping 2001:db8:35:1::17Type 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 msR3#Lab 6 IPv6 Manual Tunnels: Verification
  • Lab 6 IPv6 Manual Tunnels: GRE The link between R3 and R6 has another issue. It can not pass protocol 41 forsome reason Due to this limitation, IPv6oIPv4 tunnel can not be established between R3 andR6 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 tunnelsource and destinations can easily be chosen as the outgoing interface A new IPv6 address needs to configured on both side over the tunnel betweenR3 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 todetermine that the tunnel is up and running
  • R# ConfigsR6 R6(config-if)#int tun 0R6(config-if)#tun source s1/0R6(config-if)#tun destination 10.1.36.0R6(config-if)#tun mode gre ipR6(config-if)#ipv6 address 2001:db8:36:1::17/127R6(config-if)#endR3 R3(config-if)#int tun 1R3(config-if)#tun source s2/0R3(config-if)#tun destination 10.1.36.1R3(config-if)#tun mode gre ipR3(config-if)#ipv6 address 2001:db8:36:1::16/127R3(config-if)#endLab 6 IPv6 Manual Tunnels: Configs
  • R3 Tunnel 1 R6 Tunnel 0R3#sh ipv6 int tun 1Tunnel1 is up, line protocol is upIPv6 is enabled, link-local address is FE80::4AFF:FEA2:853No Virtual link-local address(es):Global unicast address(es):2001:DB8:36:1::16, subnet is 2001:DB8:36:1::16/127Joined group address(es):FF02::1FF02::2FF02::1:FF00:16FF02::1:FFA2:853MTU is 1476 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabledICMP unreachables are sentND DAD is enabled, number of DAD attempts: 1ND reachable time is 30000 milliseconds (using 30000)ND RAs are suppressed (periodic)Hosts use stateless autoconfig for addresses.R3#R6#sh ipv6 int tun 0Tunnel0 is up, line protocol is upIPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5600No Virtual link-local address(es):Global unicast address(es):2001:DB8:36:1::17, subnet is 2001:DB8:36:1::16/127Joined group address(es):FF02::1FF02::2FF02::1:FF00:17FF02::1:FF00:5600MTU is 1476 bytesICMP error messages limited to one every 100 millisecondsICMP redirects are enabledICMP unreachables are sentND DAD is enabled, number of DAD attempts: 1ND reachable time is 30000 milliseconds (using 30000)ND RAs are suppressed (periodic)Hosts use stateless autoconfig for addresses.R6#Lab 6 IPv6 Manual Tunnels: Verification
  • R3R3#ping 2001:db8:36:1::17Type 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 msR3#Lab 6 IPv6 Manual Tunnels: Verification
  • © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 82Lab 7 : OSPFv3
  • Lab 7 OSPFv3 ISP has received a request from ABC Inc that they want IPv6 connectivitybetween Site 1 and Site 2. ISP are also making an effort to make their ownnetwork dual stack and enabling IPv6 in their core network ISP has been running OSPFv2 internally in their core. They have decided torun OSPFv3 for IPv6 Assign IPv6 address 2001:db8:172:17::2/127 between R2 & R3. ::2 on R2 sideand ::3 on R3 side Assign IPv6 address 2001:db8:172:17::/127 between R1 & R2. :: on R1 sideand ::1 on R2 side Configure OSPFv3 area 0 between R1 and R2 and area 1 between R2 and R3as 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
  • R# Area 1 ConfigsR3 R3(config)#ipv6 unicast-routingR3(config)#int lo 0R3(config-if)#ipv6 add 2001:db8:172:16::3/128R3(config)#int e0/0R3(config-if)#ipv6 add 2001:db8:172:17::3/127R3(config-if)#ipv6 ospf 1 area 1R3(config)#ipv6 router ospf 1R3(config-rtr)#redistribute connectedR3(config-if)#endR2 R2(config)#ipv6 unicast-routingR2(config-if)#int e0/0R2(config-if)#ipv6 add 2001:db8:172:17::2/127R2(config-if)#ipv6 ospf 1 area 1R2(config-if)#endLab 7 OSPFv3: Configs
  • R# Area 0 ConfigsR2 R2(config)#int lo 0R2(config-if)#ipv6 add 2001:db8:172:16::2/128R2(config-if)#ipv6 ospf 1 area 0R2(config-if)#int s1/0R2(config-if)#ipv6 add 2001:db8:172:17::1/127R2(config-if)#ipv6 ospf 1 area 0R2(config-if)#endR1 R1(config)#ipv6 unicast-routingR1(config)#int lo 0R1(config-if)#ipv6 add 2001:db8:172:16::1/128R1(config-if)#ipv6 ospf 1 area 0R1(config)#int s1/0R1(config-if)#ipv6 add 2001:db8:172:17::/127R1(config-if)#ipv6 ospf 1 area 0R1(config-if)#endLab 7 OSPFv3: Configs
  • R2R2#sh ipv6 ospf neiOSPFv3 Router with ID (172.16.1.2) (Process ID 1)Neighbor ID Pri State Dead Time Interface ID Interface172.16.1.1 0 FULL/ - 00:00:31 6 Serial1/0172.16.1.3 1 FULL/DR 00:00:36 2 Ethernet0/0R2#R2#sh ipv6 ospf nei detail | i areaIn the area 0 via interface Serial1/0In the area 1 via interface Ethernet0/0R2#R2#sh ipv6 ospf int brieInterface PID Area Intf ID Cost State Nbrs F/CSe1/0 1 0 6 64 P2P 1/1Et0/0 1 1 2 10 BDR 1/1R2#Lab 7 OSPFv3: Verification
  • R2R2#sh ipv6 ospfRouting Process "ospfv3 1" with ID 172.16.1.2Supports IPv6 Address FamilyEvent-log enabled, Maximum number of events: 1000, Mode: cyclicIt is an area border and autonomous system boundary routerRedistributing External Routes from,connected[…]Number of external LSA 1. Checksum Sum 0x0055ECNumber of areas in this router is 2. 2 normal 0 stub 0 nssaGraceful restart helper support enabledReference bandwidth unit is 100 mbpsArea BACKBONE(0)Number of interfaces in this area is 2SPF algorithm executed 7 timesNumber of LSA 8. Checksum Sum 0x03F283Number of DCbitless LSA 0Number of indication LSA 0Number of DoNotAge LSA 0Flood list length 0Area 1Number of interfaces in this area is 1SPF algorithm executed 3 timesNumber of LSA 8. Checksum Sum 0x02CAB4Number of DCbitless LSA 0Number of indication LSA 0Number of DoNotAge LSA 0Flood list length 0Lab 7 OSPFv3: Verification
  • R1R1#sh ipv6 ospfRouting Process "ospfv3 1" with ID 172.16.1.1Supports IPv6 Address FamilyEvent-log enabled, Maximum number of events: 1000, Mode: cyclicRouter is not originating router-LSAs with maximum metricInitial SPF schedule delay 5000 msecsMinimum hold time between two consecutive SPFs 10000 msecsMaximum wait time between two consecutive SPFs 10000 msecsMinimum LSA interval 5 secsMinimum LSA arrival 1000 msecsLSA group pacing timer 240 secsInterface flood pacing timer 33 msecsRetransmission pacing timer 66 msecsNumber of external LSA 1. Checksum Sum 0x0055ECNumber of areas in this router is 1. 1 normal 0 stub 0 nssaGraceful restart helper support enabledReference bandwidth unit is 100 mbpsArea BACKBONE(0)Number of interfaces in this area is 2SPF algorithm executed 3 timesNumber of LSA 8. Checksum Sum 0x03F283Number of DCbitless LSA 0Number of indication LSA 0Number of DoNotAge LSA 0Flood list length 0Lab 7 OSPFv3: Verification
  • R3R3#sh ipv6 ospfRouting Process "ospfv3 1" with ID 172.16.1.3Supports IPv6 Address FamilyEvent-log enabled, Maximum number of events: 1000, Mode: cyclicRouter is not originating router-LSAs with maximum metricInitial SPF schedule delay 5000 msecsMinimum hold time between two consecutive SPFs 10000 msecsMaximum wait time between two consecutive SPFs 10000 msecsMinimum LSA interval 5 secsMinimum LSA arrival 1000 msecsLSA group pacing timer 240 secsInterface flood pacing timer 33 msecsRetransmission pacing timer 66 msecsNumber of external LSA 1. Checksum Sum 0x0055ECNumber of areas in this router is 1. 1 normal 0 stub 0 nssaGraceful restart helper support enabledReference bandwidth unit is 100 mbpsArea 1Number of interfaces in this area is 1SPF algorithm executed 3 timesNumber of LSA 8. Checksum Sum 0x02CAB4Number of DCbitless LSA 0Number of indication LSA 0Number of DoNotAge LSA 0Flood list length 0Lab 7 OSPFv3: Verification
  • Area 0R2#sh ipv6 ospf dataOSPFv3 Router with ID (172.16.1.2) (Process ID 1)Router Link States (Area 0)ADV Router Age Seq# Fragment ID Link count Bits172.16.1.1 968 0x80000002 0 1 None172.16.1.2 967 0x80000002 0 1 BInter Area Prefix Link States (Area 0)ADV Router Age Seq# Prefix172.16.1.2 963 0x80000001 2001:DB8:172:17::2/127Inter Area Router Link States (Area 0)ADV Router Age Seq# Link ID Dest RtrID172.16.1.2 814 0x80000001 2886729987 172.16.1.3Link (Type-8) Link States (Area 0)ADV Router Age Seq# Link ID Interface172.16.1.1 967 0x80000002 6 Se1/0172.16.1.2 964 0x80000002 6 Se1/0Intra Area Prefix Link States (Area 0)ADV Router Age Seq# Link ID Ref-lstype Ref-LSID172.16.1.1 968 0x80000002 0 0x2001 0172.16.1.2 967 0x80000002 0 0x2001 0Lab 7 OSPFv3: Verification
  • R2 (continued..)Router Link States (Area 1)ADV Router Age Seq# Fragment ID Link count Bits172.16.1.2 928 0x80000002 0 1 B172.16.1.3 820 0x80000003 0 1 ENet Link States (Area 1)ADV Router Age Seq# Link ID Rtr count172.16.1.3 929 0x80000001 2 2Inter Area Prefix Link States (Area 1)ADV Router Age Seq# Prefix172.16.1.2 963 0x80000001 2001:DB8:172:16::1/128172.16.1.2 963 0x80000001 2001:DB8:172:17::/127172.16.1.2 963 0x80000001 2001:DB8:172:16::2/128Link (Type-8) Link States (Area 1)ADV Router Age Seq# Link ID Interface172.16.1.2 968 0x80000002 2 Et0/0172.16.1.3 968 0x80000002 2 Et0/0Intra Area Prefix Link States (Area 1)ADV Router Age Seq# Link ID Ref-lstype Ref-LSID172.16.1.3 929 0x80000001 2048 0x2002 2Type-5 AS External Link StatesADV Router Age Seq# Prefix172.16.1.3 819 0x80000001 2001:DB8:35:1::16/127172.16.1.3 819 0x80000001 2001:DB8:36:1::16/127172.16.1.3 819 0x80000001 2001:DB8:172:16::3/128Lab 7 OSPFv3: Verification
  • R5 & R6R2#deb ipv6 ospf helloOSPFv3 hello events debugging is on19:02:20.240: OSPFv3: Send hello to FF02::5 area 1 on Ethernet0/0 from FE80::A8BB:CCFF:FE00:5200 interfaceID 219:02:27.100: OSPFv3: Rcv hello from 172.16.1.3 area 1 from Ethernet0/0 FE80::A8BB:CCFF:FE00:5300 interfaceID 219:02:27.100: OSPFv3: End of hello processing19:02:28.840: OSPFv3: Send hello to FF02::5 area 0 on Serial1/0 from FE80::A8BB:CCFF:FE00:5200 interface ID619:02:28.920: OSPFv3: Rcv hello from 172.16.1.1 area 0 from Serial1/0 FE80::4AFF:FEA2:851 interface ID 619:02:28.920: OSPFv3: End of hello processingR2#un allAll possible debugging has been turned offLab 7 OSPFv3: Debugs
  • © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 94Lab 8 : BGPv6
  • Lab 8: BGPv6
  • Lab 8 BGPv6: iBGP ISP is already receiving IPv6 Internet prefixes on R1, Since there is arequirement of providing IPv6 Internet connectivity to Site 2 as well so ISP hasto extend BGP all the way upto site 2 for IPv6 by enabling iBGP in their networkand eBGP with Site 2. Note, this BGP extension is already present in IPv4network iBGP peering in the ISP network is following IPv4 BGP method which is tosource the update from loopback and peer between loopbacks ISP is following the similar method that they used in IPv4 BGP which is to makeR2 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-reflectorclients for R2. Note, disable ipv4-unicast default peering so it does not activateipv4 peering by default when ipv6 peering is configured
  • R# Area 0 ConfigsR1 R1(config)#router bgp 109R1(config-router)#no bgp default ipv4-unicastR1(config-router)#address-family ipv6R1(config-router-af)#nei 2001:db8:172:16::2 remote 109R1(config-router-af)#nei 2001:db8:172:16::2 update loop 0R1(config-router-af)#redistribute staticR1(config-router-af)#neighbor 2001:db8:172:16::2 next-hop-selfR1(config-router-af)#network 2004:db8::1/128R1(config-router-af)#endR3 R3(config)#router bgp 109R3(config-router)#no bgp default ipv4-unicastR3(config-router)#address-family ipv6R3(config-router-af)#nei 2001:db8:172:16::2 remote 109R3(config-router-af)#nei 2001:db8:172:16::2 update loop 0R3(config-router-af)#endLab 8 BGPv6: iBGP Configs
  • R# Area 0 ConfigsR2 R2(config)#router bgp 109R2(config-router)#no bgp default ipv4-unicastR2(config-router)#address-family ipv6R2(config-router-af)#nei 2001:db8:172:16::1 remote 109R2(config-router-af)#nei 2001:db8:172:16::1 update loop 0R2(config-router-af)#nei 2001:db8:172:16::1 route-reflector-clientR2(config-router-af)#nei 2001:db8:172:16::3 remote 109R2(config-router-af)#nei 2001:db8:172:16::3 update loop 0R2(config-router-af)#nei 2001:db8:172:16::3 route-reflector-clientR2(config-router-af)#endLab 8 BGPv6: iBGP Configs
  • R2R2#sh bgp ipv6 unicast sumBGP router identifier 172.16.1.2, local AS number 109BGP table version is 4, main routing table version 41 network entries using 172 bytes of memory1 path entries using 88 bytes of memory1/1 BGP path/bestpath attribute entries using 128 bytes of memory1 BGP AS-PATH entries using 24 bytes of memory0 BGP route-map cache entries using 0 bytes of memory0 BGP filter-list cache entries using 0 bytes of memoryBGP using 412 total bytes of memoryBGP activity 7/0 prefixes, 8/1 paths, scan interval 60 secsNeighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd2001:DB8:172:16::14 109 100 98 4 0 0 0 1:26:26 22001:DB8:172:16::34 109 95 98 4 0 0 0 1:24:10 0R2#Lab 8 BGPv6: iBGP Verification
  • R2R2#sh bgp ipv6 unicastBGP table version is 4, local router ID is 172.16.1.2Status 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-pathOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight Path*>i 2004:DB8::1/1282001:DB8:172:16::10 100 0 i*>i 2001:DB8:1:41::/642001:DB8:172:16::10 100 0 ?R2#sh bgp ipv6 unicast 2001:db8:1:41::/64BGP routing table entry for 2001:DB8:1:41::/64, version 29Paths: (1 available, best #1, table default)Advertised to update-groups:2Refresh Epoch 2Local, (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, bestLab 8 BGPv6: iBGP Verification
  • Lab 8 BGPv6: eBGP ISP is now ready to provided end to end connectivity between site 1 and Site 2for ABC You want to use the similar BGP policies and advertisement that you have foriPv4. Enable eBGP between R3 and R5 over link local address and R3 and R6 overa global address over the tunnel interfaces. Note, make sure to advertiseSerial2/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 andaggregate 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::1represent IPv6 Internet Verify that Site 2 can reach Site 1 by pinging H1 from H2.
  • R# Area 0 ConfigsR5 R5(config)#router bgp 1R5(config-router)#address-family ipv6R5(config-router-af)#nei FE80::A01:2300%Tunnel0 remote 109R5(config-router-af)#net 2001:db8:1:56::/64R5(config-router-af)#net 2001:db8:1:57::/64R5(config-router-af)#net 2001:db8:1:88::/64R5(config-router-af)#aggregate-address 2001:db8:1:56::/63 summary-onlyR5(config-router-af)#endR3 R3(config)#router bgp 109R3(config-router)#address-family ipv6R3(config-router-af)#nei FE80::A01:2301%Tunnel0 remote 1R3(config-router-af)#Lab 8 BGPv6: eBGP Configs
  • R# Area 0 ConfigsR6 R6(config)#router bgp 1R6(config-router)#address-family ipv6R6(config-router-af)#nei 2001:DB8:36:1::16 remote 109R6(config-router-af)#net 2001:db8:1:56::/64R6(config-router-af)#net 2001:db8:1:57::/64R6(config-router-af)#net 2001:db8:1:88::/64R6(config-router-af)#aggregate-address 2001:db8:1:56::/63 summary-onlyR6(config-router-af)#endR3 R3(config)#router bgp 109R3(config-router)#address-family ipv6R3(config-router-af)#nei 2001:db8:36:1::17 remote 1R3(config)#int s2/0R3(config-if)#ip ospf 1 area 1R3(config-if)#endLab 8 BGPv6: eBGP Configs
  • R3R3#sh bgp ipv6 unicast sum | e 109BGP table version is 26, main routing table version 263 network entries using 516 bytes of memory5 path entries using 440 bytes of memory4/3 BGP path/bestpath attribute entries using 512 bytes of memory1 BGP rrinfo entries using 24 bytes of memory1 BGP AS-PATH entries using 24 bytes of memory0 BGP route-map cache entries using 0 bytes of memory0 BGP filter-list cache entries using 0 bytes of memoryBGP using 1516 total bytes of memoryBGP activity 15/6 prefixes, 31/18 paths, scan interval 60 secsNeighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd2001:DB8:36:1::174 1 11 16 26 0 0 00:05:42 22001:DB8:172:16::2FE80::A01:2301%Tunnel04 1 11 18 26 0 0 00:05:56 2R3#Lab 8 BGPv6: eBGP Verification
  • R3R3#sh bgp ipv6 unicastBGP table version is 27, local router ID is 172.16.1.3Status 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-pathOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight Path*>i 2001:DB8:1:41::/642001:DB8:172:16::10 100 0 ?* 2001:DB8:1:56::/632001:DB8:36:1::170 0 1 i*> FE80::A01:2301 0 0 1 i* 2001:DB8:1:88::/642001:DB8:36:1::170 0 1 i*> FE80::A01:2301 0 0 1 i*>i 2004:DB8::1/128 2001:DB8:172:16::10 100 0 iR3#Lab 8 BGPv6: eBGP Verification
  • R3R3#sh bgp ipv6 uni 2001:db8:1:56::/63BGP routing table entry for 2001:DB8:1:56::/63, version 22Paths: (2 available, best #2, table default)Advertised to update-groups:1 3Refresh Epoch 11, (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-aggregateRefresh Epoch 11, (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, bestR3#H2#ping [H1 IPv6 Global Unicast Address]Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 2001:DB8:1:41:A8BB:CCFF:FE00:5700, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 119/123/139 msH2#Lab 8 BGPv6: eBGP Verification
  • © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 107Lab key
  • ConfigsR# ConfigsR1 ipv6 unicast-routingipv6 cef!interface Loopback0ip address 172.16.1.1 255.255.255.255ipv6 address 2001:DB8:172:16::1/128ipv6 ospf 1 area 0!interface Loopback1ip address 1.1.1.1 255.255.255.255ipv6 address 2004:DB8::1/128!interface Serial0/0ip address 10.1.37.0 255.255.255.254ipv6 address 2001:DB8:14:1::14/127!interface Serial1/0ip address 172.17.12.0 255.255.255.254ipv6 address 2001:DB8:172:17::/127ipv6 ospf 1 area 0!router ospf 1passive-interface Serial0/0network 10.1.37.0 0.0.0.1 area 0network 172.16.1.1 0.0.0.0 area 0network 172.17.12.0 0.0.0.1 area 0router bgp 109bgp log-neighbor-changesneighbor 2001:DB8:172:16::2 remote-as 109neighbor 2001:DB8:172:16::2 update-source Loopback0neighbor 172.16.1.2 remote-as 109neighbor 172.16.1.2 update-source Loopback0!address-family ipv4network 1.1.1.1 mask 255.255.255.255network 10.1.41.0 mask 255.255.255.0redistribute staticno neighbor 2001:DB8:172:16::2 activateneighbor 172.16.1.2 activateexit-address-family!address-family ipv6redistribute staticnetwork 2004:DB8::1/128neighbor 2001:DB8:172:16::2 activateneighbor 2001:DB8:172:16::2 next-hop-selfexit-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::15ipv6 router ospf 1
  • ConfigsR# ConfigsR2 ipv6 unicast-routingipv6 cef!interface Loopback0ip address 172.16.1.2 255.255.255.255ipv6 address 2001:DB8:172:16::2/128ipv6 ospf 1 area 0!interface Ethernet0/0ip address 172.17.23.0 255.255.255.254ipv6 address 2001:DB8:172:17::2/127ipv6 ospf 1 area 1!interface Serial1/0ip address 172.17.12.1 255.255.255.254ipv6 address 2001:DB8:172:17::1/127ipv6 ospf 1 area 0!router ospf 1network 172.16.1.2 0.0.0.0 area 0network 172.17.12.0 0.0.0.1 area 0network 172.17.23.0 0.0.0.1 area 1!router bgp 109bgp log-neighbor-changesneighbor 2001:DB8:172:16::1 remote-as 109neighbor 2001:DB8:172:16::1 update-source Loopback0neighbor 2001:DB8:172:16::3 remote-as 109neighbor 2001:DB8:172:16::3 update-source Loopback0neighbor 172.16.1.1 remote-as 109neighbor 172.16.1.1 update-source Loopback0neighbor 172.16.1.3 remote-as 109!address-family ipv4no neighbor 2001:DB8:172:16::1 activateno neighbor 2001:DB8:172:16::3 activateneighbor 172.16.1.1 activateneighbor 172.16.1.1 route-reflector-clientneighbor 172.16.1.3 activateneighbor 172.16.1.3 route-reflector-clientexit-address-family!address-family ipv6neighbor 2001:DB8:172:16::1 activateneighbor 2001:DB8:172:16::1 route-reflector-clientneighbor 2001:DB8:172:16::3 activateneighbor 2001:DB8:172:16::3 route-reflector-clientexit-address-family!ipv6 router ospf 1
  • ConfigsR# ConfigsR3 interface Loopback0ip address 172.16.1.3 255.255.255.255ipv6 address 2001:DB8:172:16::3/128!interface Tunnel0no ip addressipv6 address 2001:DB8:35:1::16/127tunnel source Serial1/0tunnel mode ipv6iptunnel destination 10.1.35.1!interface Tunnel1no ip addressipv6 address 2001:DB8:36:1::16/127tunnel source Serial2/0tunnel destination 10.1.36.1!interface Ethernet0/0ip address 172.17.23.1255.255.255.254ipv6 address 2001:DB8:172:17::3/127ipv6 ospf 1 area 1!interface Serial1/0ip address 10.1.35.0 255.255.255.254!interface Serial2/0ip address 10.1.36.0 255.255.255.254ip ospf 1 area 1!router ospf 1redistribute connected subnetsnetwork 172.17.23.0 0.0.0.1 area 1router bgp 109bgp log-neighbor-changesneighbor 10.1.35.1 remote-as 1neighbor 10.1.36.1 remote-as 1neighbor 2001:DB8:36:1::17 remote-as 1neighbor 2001:DB8:172:16::2 remote-as 109neighbor 2001:DB8:172:16::2 update-source Loopback0neighbor 172.16.1.2 remote-as 109neighbor 172.16.1.2 update-source Loopback0neighbor FE80::A01:2301%Tunnel0 remote-as 1!address-family ipv4network 172.16.0.0network 172.17.0.0neighbor 10.1.35.1 activateneighbor 10.1.36.1 activateno neighbor 2001:DB8:36:1::17 activateno neighbor 2001:DB8:172:16::2 activateneighbor 172.16.1.2 activateno neighbor FE80::A01:2301%Tunnel0 activateauto-summaryexit-address-family!address-family ipv6neighbor 2001:DB8:36:1::17 activateneighbor 2001:DB8:172:16::2 activateneighbor FE80::A01:2301%Tunnel0 activateexit-address-family!ipv6 router ospf 1redistribute connected
  • ConfigsR# ConfigsR4 ipv6 unicast-routingipv6 cef!interface Loopback0ip address 10.1.1.4 255.255.255.255ipv6 address 2001:DB8:1:1::4/128!interface Ethernet0/0ip address 10.1.41.4 255.255.255.0ipv6 address 2001:DB8:1:41::4/64ipv6 address FD01:DB8:1:41::/64 eui-64ipv6 nd ra interval 30!interface Serial1/0ip address 10.1.37.1 255.255.255.254ipv6 address 2001:DB8:14:1::15/127ip route 0.0.0.0 0.0.0.0 10.1.37.0!ipv6 route ::/0 Serial1/0 FE80::4AFF:FEA2:851
  • ConfigsR# ConfigsR5 interface Loopback0ip address 10.1.1.5 255.255.255.255ipv6 address 2001:DB8:1:1::5/128ipv6 eigrp 1!interface Tunnel0no ip addressipv6 address 2001:DB8:35:1::17/127tunnel source Serial1/0tunnel mode ipv6iptunnel destination 10.1.35.0!interface Ethernet0/0ip address 10.1.57.5 255.255.255.0 secondaryip address 10.1.58.5 255.255.255.0 secondaryip address 10.1.56.5 255.255.255.0no ip split-horizon eigrp 1standby version 2standby 1 ip 10.1.56.1standby 1 ipv6 autoconfigipv6 address 2001:DB8:1:56::5/64ipv6 address 2001:DB8:1:57::5/64ipv6 address 2001:DB8:1:88::5/64ipv6 nd router-preference Highipv6 nd ra interval 40ipv6 eigrp 1!interface Serial1/0ip address 10.1.35.1 255.255.255.254router eigrp 1network 10.1.1.5 0.0.0.0network 10.1.35.0 0.0.0.1network 10.1.56.0 0.0.0.255network 10.1.57.0 0.0.0.255network 10.1.58.0 0.0.0.255!router bgp 1bgp log-neighbor-changesneighbor 10.1.1.6 remote-as 1neighbor 10.1.1.6 update-source Loopback0neighbor 10.1.35.0 remote-as 109neighbor FE80::A01:2300%Tunnel0 remote-as 109!address-family ipv4network 10.1.56.0 mask 255.255.255.0network 10.1.57.0 mask 255.255.255.0network 10.1.58.0 mask 255.255.255.0aggregate-address 10.1.56.0 255.255.254.0 summary-onlyneighbor 10.1.1.6 activateneighbor 10.1.35.0 activateno neighbor FE80::A01:2300%Tunnel0 activateexit-address-family!address-family ipv6network 2001:DB8:1:56::/64network 2001:DB8:1:57::/64network 2001:DB8:1:88::/64aggregate-address 2001:DB8:1:56::/63 summary-onlyneighbor FE80::A01:2300%Tunnel0 activateexit-address-family!ipv6 router eigrp 1
  • ConfigsR# ConfigsR6 interface Loopback0ip address 10.1.1.6 255.255.255.255ipv6 address 2001:DB8:1:1::6/128ipv6 eigrp 1!interface Tunnel0no ip addressipv6 address 2001:DB8:36:1::17/127tunnel source Serial1/0tunnel destination 10.1.36.0!interface Ethernet0/0ip address 10.1.57.6 255.255.255.0secondaryip address 10.1.58.6 255.255.255.0secondaryip address 10.1.56.6 255.255.255.0no ip split-horizon eigrp 1standby version 2standby 1 ip 10.1.56.1standby 1 ipv6 autoconfigstandby 1 priority 105standby 1 preemptipv6 address 2001:DB8:1:56::6/64ipv6 address 2001:DB8:1:57::6/64ipv6 address 2001:DB8:1:88::6/64ipv6 nd ra interval 40ipv6 eigrp 1!interface Serial1/0ip address 10.1.36.1 255.255.255.254!router eigrp 1network 10.1.1.6 0.0.0.0network 10.1.36.0 0.0.0.1network 10.1.56.0 0.0.0.255network 10.1.57.0 0.0.0.255network 10.1.58.0 0.0.0.255!router bgp 1bgp log-neighbor-changesneighbor 10.1.1.5 remote-as 1neighbor 10.1.1.5 update-source Loopback0neighbor 10.1.36.0 remote-as 109neighbor 2001:DB8:36:1::16 remote-as 109!address-family ipv4network 10.1.56.0 mask 255.255.255.0network 10.1.57.0 mask 255.255.255.0network 10.1.58.0 mask 255.255.255.0aggregate-address 10.1.56.0 255.255.254.0 summary-onlyneighbor 10.1.1.5 activateneighbor 10.1.36.0 activateno neighbor 2001:DB8:36:1::16 activateexit-address-family!address-family ipv6network 2001:DB8:1:56::/64network 2001:DB8:1:57::/64network 2001:DB8:1:88::/64aggregate-address 2001:DB8:1:56::/63 summary-onlyneighbor 2001:DB8:36:1::16 activateexit-address-family!ipv6 router eigrp 1
  • ConfigsR# ConfigsH1 interface Ethernet0/0ip address 10.1.41.1 255.255.255.0ipv6 address autoconfigipv6 enable!ip route 0.0.0.0 0.0.0.0 10.1.41.4H2 interface Ethernet0/0ip address 10.1.56.2 255.255.255.0ipv6 address autoconfigipv6 enable!ip route 0.0.0.0 0.0.0.0 10.1.56.1
  • © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 115Optional Labs
  • © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 1166PE Lab
  • 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-CEprotocol (over a VRF interface) BGP for IPv4 is pre-configured between R3-R5(E2/0-E1/0) as a PE-CE protocol (over a VRF interface) IPv6 address are pre-configured between R1-R4(E1/0-E1/0) & R3-R5(E0/0-E0/0) Note, a separate interface is used for 6PE. This is usually a casewhere ipv4 internet routes or a default routes are received on thatinterface. IPv6 can be enabled on that interface to receive ipv6 internetprefixes and that will be a dual stack environment but in lab, we areonly 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# OSPFv3R1 interface Ethernet1/0ipv6 ospf 1 area 0!router ospfv3 1router-id 10.1.0.1R4 interface Loopback0ipv6 ospf 1 area 0!interface Ethernet1/0ipv6 ospf 1 area 0!router ospfv3 1router-id 10.0.0.1
  • 6PE Lab: Enabling OSPFv3 on PE-CE link Configure mutual redistribution between OSPFv3 and BGP In which routing table (global or VRF) do you see the V6 routes after theredistribution on R1R# OSPFv3 and RedistributionR1 router ospfv3 1address-family ipv6redistribute bgp 109!router bgp 109address-family ipv6redistribute ospf 1
  • 6PE Lab: Enabling OSPFv3 on PE-CE link Verify that the peers have been established and that R4 loopback address is received andseen in BGP on R1R# BGPv6R1 R1#sh ipv6 ospf neiOSPFv3 Router with ID (10.1.0.1) (Process ID 1)Neighbor ID Pri State Dead Time Interface ID Interface10.0.0.1 1 FULL/BDR 00:00:38 6 Ethernet1/0R1#sh ipv6 route 2001:db8::4Routing entry for 2001:DB8::4/128Known via "ospf 1", distance 110, metric 10, type intra area, bgp 109Route count is 1/1, share count 0Routing paths:FE80::A8BB:CCFF:FE00:5401, Ethernet1/0Last updated 03:17:09 agoR1#sh bgp ipv6 unicastNetwork Next Hop Metric LocPrf Weight Path*> 2001:DB8::4/128 :: 10 32768 ?R1#
  • 6PE Lab: Enabling OSPFv3 on PE-CE linkAnswers We are getting global IPv4 and IPv6 routes on a separate interfaceand l3vpn routes over another interface. 6PE installs the routes in the global routing table Note that although OSPFv3 is enabled under the interface itself, theredistribution is enabled under the ospfv3 router process As 6PE uses the global routing table, configuring OSPFv3 in thecontext 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 don’t we need to configure redistribution?R# BGPv6 and RedistributionR3 router bgp 109!address-family ipv6neighbor 2001:db8:1:2::5 remote-as 2R5 router bgp 2!address-family ipv6neighbor 2001:db8:1:2::3 remote-as 109network 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# BGPv6R3 R3#sh bgp ipv6 unicast summNeighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd2001:DB8:1:2::5 4 2 14 14 5 0 0 00:08:33 1R3#R3#sh bgp ipv6 unicastBGP table version is 5, local router ID is 10.1.3.1Network Next Hop Metric LocPrf Weight Path*> 2001:DB8:1:5::3/1282001:DB8:1:2::5 0 0 2 iR3#
  • 6PE Lab: Enabling BGPv6 as a PE-CE protocol Redistribution is not required for BGP routes received from the CEas the routes will be propagated automatically to the 6PE peers viaseparate iBGP session exclusively for 6PE The PE-CE BGP session in 6PE is just like any other IPv6 eBGPsession. It could be configured over an IPv4 or IPv6 transport. Thenormal restrictions would apply. For example, a route-map would berequired 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 6PER# *BGPv4 BGPv6R1&R3router bgp 109neighbor 10.1.0.0 remote-as 109neighbor 10.1.0.0 update-source L0address-family ipv4neighbor 10.1.0.0 actrouter bgp 109address-family ipv6neighbor 10.1.0.0 remote-as 109neighbor 10.1.0.0 update-source L0neighbor 10.1.0.0 send-labelR2 router bgp 109neighbor 10.1.0.1 remote-as 109neighbor 10.1.0.0 update-source L0neighbor 10.1.3.1 remote-as 109neighbor 10.1.3.1 update-source L0address-family ipv4neighbor 10.1.0.1 activateneighbor 10.1.0.1 route-reflector-clientneighbor 10.1.3.1 activateneighbor 10.1.3.1 route-reflector-clientrouter bgp 109address-family ipv6neighbor 10.1.0.1 remote-as 109neighbor 10.1.0.1 update-source L0neighbor 10.1.3.1 remote-as 109neighbor 10.1.3.1 update-source L0neighbor 10.1.0.1 send-labelneighbor 10.1.0.1 route-reflector-clientneighbor 10.1.3.1 send-labelneighbor 10.1.3.1 route-reflector-client
  • 6PE Lab: Enabling 6PE 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# BGPv6R2 R2#sh bgp ipv6 unicast summBGP router identifier 10.1.0.0, local AS number 109BGP table version is 1, main routing table version 1Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd10.1.0.1 4 109 15 15 1 0 0 00:10:04 010.1.3.1 4 109 13 11 1 0 0 00:08:38 0R2#
  • 6PE Lab: Enabling 6PE 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# BGPv6R1 R1#sh bgp ipv6 unicast labelNetwork Next Hop In label/Out label2001:DB8::4/128 :: 16/nolabel2001:DB8:1:5::3/128::FFFF:10.1.3.1 nolabel/17R1#sh ip cef 10.1.3.110.1.3.1/32nexthop 10.1.0.2 Serial2/0 label 17R1#sh ipv6 cef 2001:db8:1:5::32001:DB8:1:5::3/128nexthop 10.1.0.2 Serial2/0 label 17 17
  • 6PE Lab: Enabling 6PE Answers 6PE requires configuring the BGP session over an IPv4 transport asthe core is not IPv6 enabled This is done by activating a neighbor with an IPv4 peer addressunder address-family ipv6 The send-label statement under address-family ipv6 is really whatenables 6PE 6PE uses an IGP label to get the ipv6 packet from the ingress to theegress PE. It is the LDP label learnt for the BGP next hop (IPv4address). It also uses a service label on the egress PE to forward the packetthrough the proper egress interface. The service label is learnt viaBGP as a result of the send-label keyword.
  • 6PE Lab: Enabling BGPv6 Answers The BGP next hop for R5 loopback address is actually R3 loopbackIPv4 address. It is displayed as an IPv4 mapped IPv6 address. Thefirst 80 bits are all zero followed by 0xFFFF and then the IPv4 nexthop address of the egress PE in dotted decimal format Redistribution is not required for BGP routes received from the CEas the routes will be propagated automatically to the 6PE peers.
  • © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 132Lab Key
  • 6PE Lab: ConfigsR# ConfigsR1 ipv6 unicast-routingipv6 cef!interface Loopback0ip address 10.1.0.1 255.255.255.255!interface Ethernet1/0ipv6 address 2001:DB8:1:1::1/64ipv6 ospf 1 area 0!interface Serial2/0ip address 10.1.0.3 255.255.255.254mpls ip!router ospfv3 1!address-family ipv6 unicastredistribute bgp 109exit-address-family!router ospf 1network 0.0.0.0 255.255.255.255 area 0!router bgp 109no bgp default ipv4-unicastneighbor 10.1.0.0 remote-as 109neighbor 10.1.0.0 update-source Loopback0neighbor 10.1.3.1 remote-as 109neighbor 10.1.3.1 update-source Loopback0!address-family ipv6redistribute ospf 1neighbor 10.1.0.0 activateneighbor 10.1.0.0 send-labelexit-address-family
  • 6PE Lab: ConfigsR# ConfigsR2 interface Loopback0ip address 10.1.0.0 255.255.255.255!interface Ethernet0/0ip address 10.1.0.4 255.255.255.254mpls ip!interface Serial1/0ip address 10.1.0.2 255.255.255.254mpls ip!router ospf 1nerwork 0.0.0.0 255.255.255.255 area 0!router bgp 109neighbor 10.1.0.1 remote-as 109neighbor 10.1.0.1 update-source Loopback0neighbor 10.1.3.1 remote-as 109neighbor 10.1.3.1 update-source Loopback0!address-family ipv6neighbor 10.1.0.1 activateneighbor 10.1.0.1 send-labelneighbor 10.1.0.1 route-reflection-clientneighbor 10.1.3.1 activateneighbor 10.1.3.1 send-labelneighbor 10.1.3.1 route-reflection-client
  • 6PE Lab: ConfigsR# ConfigsR3 ipv6 unicast-routingipv6 cef!interface Loopback0ip address 10.1.3.1 255.255.255.255!interface Ethernet0/0no ip addressipv6 address 2001:DB8:1:2::3/64!interface Ethernet1/0ip address 10.1.0.5 255.255.255.254mpls ip!router ospf 1network 0.0.0.0 255.255.255.255 area 0!router bgp 109bgp log-neighbor-changesno bgp default ipv4-unicastneighbor 10.1.0.0 remote-as 109neighbor 10.1.0.0 update-source Loopback0neighbor 2001:DB8:1:2::5 remote-as 2!address-family ipv6neighbor 10.1.0.0 activateneighbor 10.1.0.0 send-labelneighbor 2001:DB8:1:2::5 activateexit-address-family
  • 6PE Lab: ConfigsR# ConfigsR4ipv6 unicast-routing!interface Loopback0ipv6 address 2001:db8::4/128ipv6 oapf 1 area 0!interface Ethernet1/0ipv6 address 2001:DB8:1:1::1/64ipv6 ospf 1 area 0
  • 6PE Lab: ConfigsR# ConfigsR5ipv6 unicast-routingipv6 cef!interface Loopback0ipv6 address 2001:DB8:1:5::3/128!interface Ethernet0/0ipv6 address 2001:DB8:1:2::5/64!router bgp 2neighbor 2001:DB8:1:2::3 remote-as 109!address-family ipv6network 2001:DB8:1:5::3/128neighbor 2001:DB8:1:2::3 activateexit-address-family
  • © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 1386VPE Lab
  • 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 ispreconfigured PE-CE protocol between R3-R5 is BGP for IPv4 and ispreconfigured
  • 6VPE Lab: Enabling static a PE-CE protocol forIPv6 Enable IPv6 VRF on R1 Configure static route between R1-R4 Redistribute static in BGPR# OSPFv3 and RedistributionR1 vrf upgrade-cli multi-af-mode common-policies vrf 6vpe force!vrf definition 6vpeaddress-family ipv6!ipv6 route vrf 6vpe 2001:db8::/64 201:db8:1:1::4!router bgp 109address-family ipv6 vrf 6vperedistribute staticR4 ipv6 route ::/0 2001:db8:1:1::1
  • 6VPE Lab: Enabling static a PE-CE protocol forIPv6 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# BGPv6R4 R4#sh ipv6 route ::/0Routing entry for ::/0Known via "static", distance 1, metric 0Backup from "static [2]"Route count is 1/1, share count 0Routing paths:2001:DB8:1:1::1Last updated 00:01:22 agoR1 R1#sh ipv6 route vrf 6vpe | incl 2001:DB8::/64S 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#
  • 6VPE Lab: Enabling static a PE-CE protocol forIPv6 Answers The “vrf upgrade-cli” command converts the IPv4 centric VRF CLI toa multi address family VRF CLI. There are several option with thiscommand. For example, only one VRF can be converted into newformat 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 toaccommodate multiple address families Static routes in the context of 6VPE are very similar to any otherstatic routes. They just need to be configured as part of the VRFconfiguration on the PE
  • 6VPE Lab: Enabling BGP as a PE-CE protocol forIPv6 Enable IPv6 VRF on R3 Configure BGP between R3-R5R# Static and redistribution for V6R3 vrf upgrade-cli multi-af-mode common-policies vrf 6vpe force!vrf definition 6vpeaddress-family ipv6!router bgp 109address-family ipv6 vrf 6vpeneighbor 2001:db8:1:2::5 remote-as 2R5 router bgp 2no bgp default ipv4-unicastneighbor 2001:db8:1:2::3 remote-as 109address-family ipv6network 2001:db8:1:5::3/128neighbor 2001:db8:1:2::3 activate
  • 6VPE Lab: Enabling BGP as a PE-CE protocol forIPv6 Verify the BGP sessions are up and that the routes are advertisedR# Static routesR3 R3#sh bgp vpnv6 uni all summ | incl 20012001:DB8:1:2::5 4 2 57 59 4 0 0 00:48:33 1R3#sh bgp vpnv6 uni all | incl 2001:DB8:1:5::3*> 2001:DB8:1:5::3/128R3#R5 R5#sh bgp ipv6 uni summ | incl 20012001:DB8:1:2::3 4 109 61 59 3 0 0 00:50:21 1R5#sh bgp ipv6 uni | incl 2001:DB8::/64*> 2001:DB8::/64 2001:DB8:1:2::3 0 109 ?R5#
  • 6VPE Lab: Enabling BGP as a PE-CE protocol forIPv6 Answers The BGP session on the PE is in the VRF context, where as it is asimple BGP session on the CE Note that just as for IPv4 BGP in a VRF context, the neighboraddress only needs to be configured under the appropriate address-family for the specific VRF Just like any IPv6 BGP session, you can either use an IPv6 or IPv4transport address when you configure the BGP session in the VRFcontext
  • 6VPE Lab: Enabling 6VPE Configure iBGP between R1-R2 (RR) & R2-R3 Compare difference between IPv4 and IPv6 BGP *IPv4 BGP configs are there for comparison purposeR# *BGPv4 BGPv6R1&R3router bgp 109neighbor 10.1.0.0 remote-as 109neighbor 10.1.0.0 update-source L0address-family vpnv4neighbor 10.1.0.0 actrouter bgp 109neighbor 10.1.0.0 remote-as 109neighbor 10.1.0.0 update-source L0address-family vpnv6neighbor 10.1.0.0 activateneighbor 10.1.0.0 send-labelR2 router bgp 109neighbor 10.1.0.1 remote-as 109neighbor 10.1.0.0 update-source L0neighbor 10.1.3.1 remote-as 109neighbor 10.1.3.1 update-source L0address-family vpnv4neighbor 10.1.0.1 activateneighbor 10.1.0.1 route-reflector-clientneighbor 10.1.3.1 activateneighbor 10.1.3.1 route-reflector-clientrouter bgp 109neighbor 10.1.0.1 remote-as 109neighbor 10.1.0.1 update-source L0neighbor 10.1.3.1 remote-as 109neighbor 10.1.3.1 update-source L0address-family vpnv6neighbor 10.1.0.1 activateneighbor 10.1.0.1 route-reflector-clientneighbor 10.1.3.1 activateneighbor 10.1.3.1 route-reflector-client
  • 6VPE Lab: Enabling 6VPE Verify the BGP sessions are up on the RR and that the routes areadvertisedR# Static routesR2 R2#sh bgp vpnv6 uni all summNeighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd10.1.0.1 4 109 72 71 3 0 0 01:00:42 110.1.3.1 4 109 68 66 3 0 0 00:57:40 1R2#sh bgp vpnv6 uni allBGP table version is 3, local router ID is 10.1.0.0Status 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-pathOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight PathRoute Distinguisher: 1:1*>i 2001:DB8::/64 ::FFFF:10.1.0.1 0 100 0 ?*>i 2001:DB8:1:5::3/128::FFFF:10.1.3.1 0 100 0 2 i
  • 6VPE Lab: Enabling 6VPE Verify that routes are received and installed in the CEF tableR# Static routesR1 R1#sh bgp vpnv6 uni allBGP table version is 4, local router ID is 10.1.0.1Status 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-pathOrigin codes: i - IGP, e - EGP, ? - incompleteNetwork Next Hop Metric LocPrf Weight PathRoute 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 0 2 iR1#sh ip cef 10.1.3.110.1.3.1/32nexthop 10.1.0.2 Serial1/0 label 17R1#sh ipv6 cef vrf 6vpe 2001:db8:1:5::32001:DB8:1:5::3/128nexthop 10.1.0.2 Serial1/0 label 17 20R1#
  • 6VPE Lab: Enabling 6VPE Answers Just like 6PE and L3VPN for IPv4, 6VPE uses a label stack toforward 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 isconfigured between the two PE
  • © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 152Lab Key
  • 6VPE Lab: ConfigsR# ConfigsR1 vrf definition 6vperd 1:1route-target export 1:1route-target import 1:1!address-family ipv6exit-address-family!ipv6 unicast-routingipv6 cef!interface Loopback0ip address 10.1.0.1 255.255.255.255!interface Ethernet0/0vrf forwarding 6vpeip address 10.1.1.1 255.55.255.0ipv6 address 2001:DB8:1:1::1/64!interface Serial1/0ip address 10.1.0.3 255.255.255.254mpls ip!router ospf 1network 0.0.0.0 255.255.255.255 area 0!router bgp 109bgp log-neighbor-changesno bgp default ipv4-unicastneighbor 10.1.0.0 remote-as 109neighbor 10.1.0.0 update-source Loopback0!address-family vpnv6neighbor 10.1.0.0 activateneighbor 10.1.0.0 send-community extendedexit-address-family!address-family ipv6 vrf 6vperedistribute staticexit-address-family
  • 6VPE Lab: ConfigsR# ConfigsR2 interface Loopback0ip address 10.1.0.0 255.255.255.255!interface Ethernet0/0ip address 10.1.0.4 255.255.255.254mpls ip!interface Serial1/0ip address 10.1.0.2 255.255.255.254mpls ip!router ospf 1nerwork 0.0.0.0 255.255.255.255 area 0!router bgp 109no bgp default ipv4-unicastneighbor 10.1.0.1 remote-as 109neighbor 10.1.0.1 update-source Loopback0neighbor 10.1.3.1 remote-as 109neighbor 10.1.3.1 update-source Loopback0!address-family vpnv6neighbor 10.1.0.1 activateneighbor 10.1.0.1 route-reflection-clientneighbor 10.1.3.1 activateneighbor 10.1.3.1 route-reflection-client
  • 6VPE Lab: ConfigsR# ConfigsR3 vrf definition 6vperd 1:1route-target export 1:1route-target import 1:1!address-family ipv6exit-address-family!ipv6 unicast-routingipv6 cef!interface Loopback0ip address 10.1.3.1 255.255.255.255!interface Ethernet0/0vrf forwarding 6vpeip address 10.1.1.2 255.255.255.0ipv6 address 2001:DB8:1:2::3/64!interface Ethernet1/0ip address 10.1.0.5 255.255.255.254mpls ip!router ospf 1network 0.0.0.0 255.255.255.255 area 0!router bgp 109bgp log-neighbor-changesno bgp default ipv4-unicastneighbor 10.1.0.0 remote-as 109neighbor 10.1.0.0 update-source Loopback0!address-family vpnv6neighbor 10.1.0.0 activateneighbor 10.1.0.0 send-community extendedexit-address-family!address-family ipv6 vrf 6vpeneighbor 2001:DB8:1:2::5 remote-as 2neighbor 2001:DB8:1:2::5 activateexit-address-family
  • 6VPE Lab: ConfigsR# ConfigsR4ipv6 unicast-routingipv6 cef!interface Ethernet0/0ipv6 address 2001:DB8:1:1::4/64!interface Ethernet1/0ipv6 address 2001:DB8::/64 eui-64!ipv6 route ::/0 2001:DB8:1:1::1
  • 6VPE Lab: ConfigsR# ConfigsR5ipv6 unicast-routingipv6 cef!interface Loopback0ipv6 address 2001:DB8:1:5::3/128!interface Ethernet0/0ipv6 address 2001:DB8:1:2::5/64!router bgp 2no bgp default ipv4-unicastneighbor 2001:DB8:1:2::3 remote-as 109!address-family ipv6network 2001:DB8:1:5::3/128neighbor 2001:DB8:1:2::3 activateexit-address-family
  • © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 158IPv6 Multicast Lab
  • 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 IPv6Multicast 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 receiverR# Multicast configurationR1 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/0ipv6 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 configurationR3 R3#sh ipv6 pim group-map ff1E::1IP PIM Group Mapping Table(* indicates group mappings being used)FF00::/8*SM, RP: 2001:DB8:1::RPF: Et1/0,FE80::A8BB:CCFF:FE00:5200Info source: StaticUptime: 00:30:53, Groups: 1R3#sh ipv6 mld groupsMLD Connected Group MembershipGroup Address Interface Uptime ExpiresFF1E::1 Ethernet0/0 00:28:50 00:03:22R3#
  • 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 configurationR2 R2#sh ipv6 pim neiPIM Neighbor TableMode: B - Bidir Capable, G - GenID CapableNeighbor Address Interface Uptime Expires Mode DR priFE80::A8BB:CCFF:FE00:5301 Ethernet0/0 00:36:36 00:01:38 B G DR 1FE80::A8BB:CCFF:FE00:5100 Serial1/0 00:36:48 00:01:33 B G 1R2#sh ipv6 mrouteMulticast Routing TableFlags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group,…(*, FF1E::1), 00:38:08/00:02:39, RP 2001:DB8:1::, flags: SIncoming interface: Tunnel4RPF nbr: 2001:DB8:1::Immediate Outgoing interface list:Ethernet0/0, Forward, 00:38:08/00:02:39
  • Multicast Lab: IPv6 Multicast with static RP 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# Multicast configurationR3 R3#sh ipv6 mrouteMulticast Routing TableFlags: 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 SPTTimers: Uptime/ExpiresInterface state: Interface, State…(2001:DB8:1:1::4, FF1E::1), 00:00:03/00:03:28, flags: SJTIncoming interface: Serial2/0RPF nbr: FE80::A8BB:CCFF:FE00:5100Inherited Outgoing interface list:Ethernet0/0, Forward, 00:41:26/neverR3#
  • Multicast Lab: IPv6 Multicast with static RPAnswers IGMP has been replaced with MLD in IPv6 multicast. MLDv2 isrequired for SSM support. As stated in RFC4601, Cisco IOS uses a tunnel interface for thePIM register process. On the RP, this tunnel interface is used as theincoming interface for (*,G) entries, as encapsulated multicastpackets 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 areceiver Can you identify R1 loopback address in the embedded RP multicast addressR# Multicast configurationR1 ipv6 pim rp-address 2001:db8:1::1Receiver interface Ethernet0/0ipv6 mld join-group FF7E:130:2001:DB8:1::99
  • Multicast Lab: IPv6 Multicast with Embedded RP Verify that group is seen as embedded RP group Verify that PIM join is sent towards embedded RP (R1)R# Multicast configurationR3 R3#sh ipv6 pim group-map FF7E:130:2001:DB8:1::99IP PIM Group Mapping Table(* indicates group mappings being used)FF7E:130:2001:DB8:1::/80*SM, RP: 2001:DB8:1::1RPF: Se2/0,FE80::A8BB:CCFF:FE00:5100Info source: EmbeddedUptime: 00:11:31, Groups: 1R3#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: SCJIncoming interface: Serial2/0RPF nbr: FE80::A8BB:CCFF:FE00:5100Immediate Outgoing interface list:Ethernet0/0, Forward, 00:09:35/neverR3#
  • 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 configurationR1 R1#sh ipv6 mroute FF7E:130:2001:DB8:1::99Multicast Routing TableFlags: 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 SPTTimers: Uptime/ExpiresInterface state: Interface, State(*, FF7E:130:2001:DB8:1::99), 00:16:13/00:03:26, RP 2001:DB8:1::1, flags: SIncoming interface: Tunnel3RPF nbr: 2001:DB8:1::1Immediate Outgoing interface list:Serial2/0, Forward, 00:16:13/00:03:26R1#
  • Multicast Lab: IPv6 Multicast with Embedded RP Ping multicast address FF7E:130:2001:DB8:1::99 from R4 and verify echo replies arereceived from R5 Verify that R1 has a (S,G) entry for R4R# Multicast configurationR1 R1#sh ipv6 mroute FF7E:130:2001:DB8:1::99Multicast Routing Table..(*, FF7E:130:2001:DB8:1::99), 00:20:43/00:02:56, RP 2001:DB8:1::1, flags: SIncoming interface: Tunnel3RPF nbr: 2001:DB8:1::1Immediate Outgoing interface list: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: SFTIncoming interface: Ethernet0/0RPF nbr: 2001:DB8:1:1::4Immediate Outgoing interface list:Serial2/0, Forward, 00:00:02/00:03:27R1#
  • Multicast Lab: IPv6 Multicast with Embedded RP 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 1preceding 0x30 represents the last 4 bits of the RP address. 0x30(48 in decimal) is the actual length we use to retrieve the RPaddress. As stated in RFC4601, Cisco IOS uses a tunnel interface for thePIM register process. On the RP, this tunnel interface is used as theincoming interface for (*,G) entries, as encapsulated multicastpackets will be received on that interface.
  • IPv6 Multicast Lab Key
  • © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 173Lab Key
  • Multicast Lab: ConfigsR# ConfigsR1 ipv6 unicast-routingipv6 cefipv6 multicast-routing!interface Loopback0ipv6 address 2001:DB8:1::1/128ipv6 ospf 1 area 0!interface Ethernet0/0ipv6 address 2001:DB8:1:1::1/64ipv6 ospf 1 area 0!interface Serial1/0ipv6 address 2001:DB8:1::3/127ipv6 ospf 1 area 0!interface Serial2/0ipv6 address 2001:DB8::3/64ipv6 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: ConfigsR# ConfigsR2ipv6 unicast-routingipv6 cefipv6 multicast-routing!interface Loopback0ipv6 address 2001:DB8:1::/128ipv6 ospf 1 area 0!interface Ethernet0/0ipv6 address 2001:DB8:1::4/127ipv6 ospf 1 area 0!interface Serial1/0ipv6 address 2001:DB8:1::2/127ipv6 ospf 1 area 0!ipv6 pim rp-address 2001:DB8:1::ipv6 router ospf 1
  • Multicast Lab: ConfigsR# ConfigsR3 ipv6 unicast-routingipv6 cefipv6 multicast-routing!interface Loopback0ipv6 address 2001:DB8:1:3::3/128ipv6 ospf 1 area 0!interface Ethernet0/0ipv6 address 2001:DB8:1:2::3/64ipv6 ospf 1 area 0!interface Ethernet1/0ipv6 address 2001:DB8:1::5/127ipv6 ospf 1 area 0!interface Serial2/0ipv6 address 2001:DB8::5/64ipv6 ospf 1 area 0!ipv6 pim rp-address 2001:DB8:1::ipv6 router ospf 1
  • Multicast Lab: ConfigsR# ConfigsR4(Source) no ipv6 cef!interface Ethernet0/0ipv6 address 2001:DB8:1:1::4/64!R5(Receiver) no ipv6 cef!interface Ethernet0/0ipv6 address 2001:DB8:1:2::5/64ipv6 mld join-group FF05::1:1ipv6 mld join-group FF7E:130:2001:DB8:1::99!
  • © 2011 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 178Cisco ConfidentialCisco Connect 178© 2012 Cisco and/or its affiliates. All rights reserved.“For larger statements andquotes, use this slide layout toformat the long references in allof your presentations.”Source Name Placement
  • Complete Your Paper“Session Evaluation”Give us your feedback and you could win1 of 2 fabulous prizes in a random draw.Complete and return your paperevaluation form to the room attendantas you leave this session.Winners will be announced today.You must be present to win!..visit them at BOOTH# 100
  • © 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 180Thank you.