IPv6 Hands-on Lab. Faraz Shamim, Technical Leader Harold Ritter, Technical Leader. Toronto, Canada May 30, 2013

Size: px
Start display at page:

Download "IPv6 Hands-on Lab. Faraz Shamim, Technical Leader Harold Ritter, Technical Leader. Toronto, Canada May 30, 2013"

Transcription

1 Toronto, Canada May 30, 2013 IPv6 Hands-on Lab Faraz Shamim, Technical Leader Harold Ritter, Technical Leader Cisco and/or its affiliates. All rights reserved. Cisco Connect 1

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

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

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

5 Lab Topology

6 Lab 1 : IPv6 Addressing & Stateless Address Auto Configuration (SLAAC) 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 6

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

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

9 Lab 1: IPv6 Addressing & SLAAC

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

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

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

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

14 Lab 1 IPv6 Global Unicast Address After successfully pilot testing in site 1, you now want to enable IPv6 in site 2 You asked from your ISP about IPv6 and they gave you a /48 address 2001:db8:1::/48 from their block Instead of removing the unique local address from site 1 you decided to keep it and configured the new global address in site 1 and site 2 This time you want to use manual assignment of last 64 bit so you will not use EUI-64 bit method for global addressing. You want to make sure this is the method you follow from now on For the manual assignment you will use the router number as the last 4 bits out of 64, for e,g. R4 will have ::4 as the last 64 bits You want to test the multiple IPv6 address assignment on a router so you will configure two additional IPv6 global addresses on R5 and R6 Assign IPv6 global unicast address on site 1 and site 2 by using subnetting as shown in the next slide

15 Lab 1b: IPv6 Global Unicast address & SLAAC

16 Lab 1 IPv6 Global Unicast address & SLAAC: Configs R# Configs R4 R5 R4(config)#ipv6 unicast-routing R4(config)#interface loop0 R4(config-if)#ipv6 address 2001:db8:1:1::4/128 R4(config)#interface e0/0 R4(config-if)#ipv6 address 2001:db8:1:41::4/64 R4(config-if)#end R5(config)#ipv6 unicast-routing R5(config)#interface loop0 R5(config-if)#ipv6 address 2001:db8:1:1::5/128 R5(config)#interface e0/0 R5(config-if)#ipv6 address 2001:db8:1:56::5/64 R5(config-if)#ipv6 address 2001:db8:1:57::5/64 R5(config-if)#ipv6 address 2001:db8:1:58::5/64 R5(config-if)#end

17 Lab 1 IPv6 Global Unicast address & SLAAC: Configs R# Configs R6 R4(config)#ipv6 unicast-routing R6(config)#interface loop0 R6(config-if)#ipv6 address 2001:db8:1:1::6/128 R6(config)#interface e0/0 R6(config-if)#ipv6 address 2001:db8:1:56::6/64 R6(config-if)#ipv6 address 2001:db8:1:57::6/64 R6(config-if)#ipv6 address 2001:db8:1:58::6/64 R6(config-if)#end H2 H2(config)#interface e0/0 H2(config-if)#ipv6 enable H2(config-if)#ipv6 address autoconfig H2(config-if)#end

18 Lab 1 IPv6 Global Unicast address: Verification R4 Loopback 0 R4 Ethernet0/0 R4#sh ipv6 int lo 0 Loopback0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5900 No Virtual link-local address(es): Global unicast address(es): 2001:DB8:1:1::4, subnet is 2001:DB8:1:1::4/128 Joined group address(es): FF02::1 FF02::2 FF02::1:FF00:4 FF02::1:FF00:5900 MTU is 1514 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is not supported ND reachable time is milliseconds (using 30000) ND RAs are suppressed (periodic) Hosts use stateless autoconfig for addresses. R4# R4#sh ipv6 int e0/0 Ethernet0/0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5400 No Virtual link-local address(es): Global unicast address(es): 2001:DB8:1:41::4, subnet is 2001:DB8:1:41::/64 FD01:DB8:1:41:A8BB:CCFF:FE00:5400, subnet is FD01:DB8:1:41::/64 [EUI] Joined group address(es): FF02::1 FF02::2 FF02::1:FF00:4 FF02::1:FF00:5400 MTU is 1500 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is enabled, number of DAD attempts: 1 ND reachable time is milliseconds (using 30000) ND advertised reachable time is 0 (unspecified) ND advertised retransmit interval is 0 (unspecified) ND router advertisements are sent every 200 seconds ND router advertisements live for 1800 seconds ND advertised default router preference is Medium Hosts use stateless autoconfig for addresses. R4#

19 Lab 1 IPv6 Global Unicast address: Verification R5 Loopback 0 R5#sh ipv6 int lo 0 Loopback0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5A00 No Virtual link-local address(es): Global unicast address(es): 2001:DB8:1:1::5, subnet is 2001:DB8:1:1::5/128 Joined group address(es): FF02::1 FF02::2 FF02::1:FF00:5 FF02::1:FF00:5A00 MTU is 1514 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is not supported ND reachable time is milliseconds (using 30000) ND RAs are suppressed (periodic) Hosts use stateless autoconfig for addresses. R5# R5 Ethernet0/0 R5#sh ipv6 int e0/0 Ethernet0/0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5A00 No Virtual link-local address(es): Global unicast address(es): 2001:DB8:1:56::5, subnet is 2001:DB8:1:56::/ :DB8:1:57::5, subnet is 2001:DB8:1:57::/ :DB8:1:58::5, subnet is 2001:DB8:1:58::/64 Joined group address(es): FF02::1 FF02::2 FF02::1:FF00:5 FF02::1:FF00:5A00 MTU is 1500 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is enabled, number of DAD attempts: 1 ND reachable time is milliseconds (using 30000) ND advertised reachable time is 0 (unspecified) ND advertised retransmit interval is 0 (unspecified) ND router advertisements are sent every 200 seconds ND router advertisements live for 1800 seconds ND advertised default router preference is Medium Hosts use stateless autoconfig for addresses.

20 Lab 1 IPv6 Global Unicast address: Verification R6 Loopback 0 R6 Ethernet0/0 R6#sh ipv6 int lo 0 Loopback0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5B00 No Virtual link-local address(es): Global unicast address(es): 2001:DB8:1:1::6, subnet is 2001:DB8:1:1::6/128 Joined group address(es): FF02::1 FF02::2 FF02::1:FF00:6 FF02::1:FF00:5B00 MTU is 1514 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is not supported ND reachable time is milliseconds (using 30000) ND RAs are suppressed (periodic) Hosts use stateless autoconfig for addresses. R6# R6#sh ipv6 int e0/0 Ethernet0/0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5B00 No Virtual link-local address(es): Global unicast address(es): 2001:DB8:1:56::6, subnet is 2001:DB8:1:56::/ :DB8:1:57::6, subnet is 2001:DB8:1:57::/ :DB8:1:58::6, subnet is 2001:DB8:1:58::/64 Joined group address(es): FF02::1 FF02::2 FF02::1:FF00:6 FF02::1:FF00:5B00 MTU is 1500 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is enabled, number of DAD attempts: 1 ND reachable time is milliseconds (using 30000) ND advertised reachable time is 0 (unspecified) ND advertised retransmit interval is 0 (unspecified) ND router advertisements are sent every 200 seconds ND router advertisements live for 1800 seconds ND advertised default router preference is Medium Hosts use stateless autoconfig for addresses.

21 Lab 1 IPv6 SLAAC: Verification H1 Ethernet0/0 H2 Ethernet0/0 H1#sh ipv6 int e0/0 Ethernet0/0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5700 No Virtual link-local address(es): Stateless address autoconfig enabled Global unicast address(es): 2001:DB8:1:41:A8BB:CCFF:FE00:5700, subnet is 2001:DB8:1:41::/64 [EUI/CAL/PRE] valid lifetime preferred lifetime FD01:DB8:1:41:A8BB:CCFF:FE00:5700, subnet is FD01:DB8:1:41::/64 [EUI/CAL/PRE] valid lifetime preferred lifetime Joined group address(es): FF02::1 FF02::1:FF00:5700 MTU is 1500 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is enabled, number of DAD attempts: 1 ND reachable time is milliseconds (using 30000) Default router is FE80::A8BB:CCFF:FE00:5400 on Ethernet0/0 H1# H2#sh ipv6 int e0/0 Ethernet0/0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5D00 No Virtual link-local address(es): Stateless address autoconfig enabled Global unicast address(es): 2001:DB8:1:56:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:56::/64 [EUI/CAL/PRE] valid lifetime preferred lifetime :DB8:1:57:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:57::/64 [EUI/CAL/PRE] valid lifetime preferred lifetime :DB8:1:58:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:58::/64 [EUI/CAL/PRE] valid lifetime preferred lifetime Joined group address(es): FF02::1 FF02::1:FF00:5D00 MTU is 1500 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is enabled, number of DAD attempts: 1 ND reachable time is milliseconds (using 30000) Default router is FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0 H2#

22 Lab 1 IPv6 Global Unicast address: Verification R# Verification commands H2 H2#ping 2001:db8:1:56::5 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:DB8:1:56::5, timeout is 2 seconds: Success rate is 100 percent (5/5), round-trip min/avg/max = 0/3/14 ms H2#ping 2001:db8:1:57::5 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:DB8:1:57::5, timeout is 2 seconds: Success rate is 100 percent (5/5), round-trip min/avg/max = 0/4/21 ms H2#ping 2001:db8:1:58::5 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:DB8:1:58::5, timeout is 2 seconds: Success rate is 100 percent (5/5), round-trip min/avg/max = 0/4/19 ms H2#ping 2001:db8:1:56::6 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:DB8:1:56::6, timeout is 2 seconds: Success rate is 100 percent (5/5), round-trip min/avg/max = 1/4/17 ms H2#ping 2001:db8:1:57::6 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:DB8:1:57::6, timeout is 2 seconds: Success rate is 100 percent (5/5), round-trip min/avg/max = 0/3/17 ms H2#ping 2001:db8:1:58::6 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:DB8:1:58::6, timeout is 2 seconds: Success rate is 100 percent (5/5), round-trip min/avg/max = 0/3/14 ms H2#

23 Lab 1 IPv6 SLAAC: Verification R# Verification commands H1 H1#ping 2001:DB8:1:41::4 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:DB8:1:41::4, timeout is 2 seconds: Success rate is 100 percent (5/5), round-trip min/avg/max = 0/3/17 ms H1#

24 Lab 1 IPv6 SLAAC: Debugs R5 & R6 R5#deb ipv6 nd ICMPv6-ND: Request to send RA for FE80::A8BB:CCFF:FE00:5A00 ICMPv6-ND: Setup RA from FE80::A8BB:CCFF:FE00:5A00 to FF02::1 on Ethernet0/0 ICMPv6-ND: MTU = 1500 ICMPv6-ND: prefix = 2001:DB8:1:56::/64 onlink autoconfig ICMPv6-ND: / (valid/preferred) ICMPv6-ND: prefix = 2001:DB8:1:57::/64 onlink autoconfig ICMPv6-ND: / (valid/preferred) ICMPv6-ND: prefix = 2001:DB8:1:58::/64 onlink autoconfig ICMPv6-ND: / (valid/preferred) R5# ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5B00 on Ethernet0/0 ICMPv6-ND: Prefix : 2001:DB8:1:56::, Length: 64, Vld Lifetime: , Prf Lifetime: , PI Flags: C0 ICMPv6-ND: Prefix : 2001:DB8:1:57::, Length: 64, Vld Lifetime: , Prf Lifetime: , PI Flags: C0 ICMPv6-ND: Prefix : 2001:DB8:1:58::, Length: 64, Vld Lifetime: , Prf Lifetime: , PI Flags: C0 R5# R6#deb ipv6 nd ICMPv6-ND: Request to send RA for FE80::A8BB:CCFF:FE00:5B00 ICMPv6-ND: Setup RA from FE80::A8BB:CCFF:FE00:5B00 to FF02::1 on Ethernet0/0 ICMPv6-ND: MTU = 1500 ICMPv6-ND: prefix = 2001:DB8:1:56::/64 onlink autoconfig ICMPv6-ND: / (valid/preferred) ICMPv6-ND: prefix = 2001:DB8:1:57::/64 onlink autoconfig ICMPv6-ND: / (valid/preferred) ICMPv6-ND: prefix = 2001:DB8:1:58::/64 onlink autoconfig ICMPv6-ND: / (valid/preferred) R6# ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0 ICMPv6-ND: Prefix : 2001:DB8:1:56::, Length: 64, Vld Lifetime: , Prf Lifetime: , PI Flags: C0 ICMPv6-ND: Prefix : 2001:DB8:1:57::, Length: 64, Vld Lifetime: , Prf Lifetime: , PI Flags: C0 ICMPv6-ND: Prefix : 2001:DB8:1:58::, Length: 64, Vld Lifetime: , Prf Lifetime: , PI Flags: C0 H2#

25 Lab 1 IPv6 SLAAC: Debugs H2 & H1 H2#deb ipv6 nd ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5B00 on Ethernet0/0 ICMPv6-ND: Prefix : 2001:DB8:1:56::, Length: 64, Vld Lifetime: , Prf Lifetime: , PI Flags: C0 ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:56::/64 eui-64, 2001:DB8:1:56:A8BB:CCFF:FE00:5D :DB8:1:56:A8BB:CCFF:FE00:5D00/64 is existing ICMPv6-ND: Prefix : 2001:DB8:1:57::, Length: 64, Vld Lifetime: , Prf Lifetime: , PI Flags: C0 ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:57::/64 eui-64, 2001:DB8:1:57:A8BB:CCFF:FE00:5D :DB8:1:57:A8BB:CCFF:FE00:5D00/64 is existing H2# ICMPv6-ND: Prefix : 2001:DB8:1:58::, Length: 64, Vld Lifetime: , Prf Lifetime: , PI Flags: C0 ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:58::/64 eui-64, 2001:DB8:1:58:A8BB:CCFF:FE00:5D :DB8:1:58:A8BB:CCFF:FE00:5D00/64 is existing H2# H1#deb ipv6 nd ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5900 on Ethernet0/0 ICMPv6-ND: Prefix : 2001:DB8:1:41::, Length: 64, Vld Lifetime: , Prf Lifetime: , PI Flags: C0 ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:41::/64 eui-64, 2001:DB8:1:41:A8BB:CCFF:FE00:5C :DB8:1:41:A8BB:CCFF:FE00:5C00/64 is existing ICMPv6-ND: Prefix : FD01:DB8:1:41::, Length: 64, Vld Lifetime: , Prf Lifetime: , PI Flags: C0 ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig FD01:DB8:1:41::/64 eui-64, FD01:DB8:1:41:A8BB:CCFF:FE00:5C00 FD01:DB8:1:41:A8BB:CCFF:FE00:5C00/64 is existing H1#

26 Lab 2 : IPv6 Neighbor Discovery 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 26

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

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

29 Lab 2 IPv6 Neighbor discovery: Verification R4 R4#sh ipv6 int e0/0 Ethernet0/0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5900 No Virtual link-local address(es): Global unicast address(es): 2001:DB8:1:41::4, subnet is 2001:DB8:1:41::/64 FD01:DB8:1:41:A8BB:CCFF:FE00:5900, subnet is FD01:DB8:1:41::/64 [EUI] Joined group address(es): FF02::1 FF02::2 FF02::1:FF00:4 FF02::1:FF00:5900 MTU is 1500 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is enabled, number of DAD attempts: 1 ND reachable time is milliseconds (using 30000) ND advertised reachable time is 0 (unspecified) ND advertised retransmit interval is 0 (unspecified) ND router advertisements are sent every 30 seconds ND router advertisements live for 1800 seconds ND advertised default router preference is Medium Hosts use stateless autoconfig for addresses. R4#

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

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

32 Lab 2 IPv6 Neighbor discovery: Configs R# Configs R5 R5(config)#int e0/0 R5(config-if)#ipv6 address 2001:db8:1:59::5/64 R6 R6(config)#int e0/0 R6(config-if)#ipv6 address 2001:db8:1:59::6/64

33 Lab 2 IPv6 Neighbor discovery: Verification R4 R6#sh ipv6 int Ethernet0/0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5B00 No Virtual link-local address(es): Global unicast address(es): 2001:DB8:1:56::6, subnet is 2001:DB8:1:56::/ :DB8:1:57::6, subnet is 2001:DB8:1:57::/ :DB8:1:58::6, subnet is 2001:DB8:1:58::/ :DB8:1:59::5, subnet is 2001:DB8:1:59::/64 Joined group address(es): FF02::1 FF02::2 FF02::1:FF00:5 FF02::1:FF00:6 FF02::1:FF00:5B00 MTU is 1500 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled R5#sh ipv6 int e0/0 i DUP 2001:DB8:1:59::5, subnet is 2001:DB8:1:59::/64 [DUP]

34 Lab 2 IPv6 Neighbor discovery: Debugs R6 R6(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/0 R5(config-if)#ipv6 address 2001:db8:1:59::5/64 *Jan 30 21:48:57.826: ICMPv6-ND: / (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/0

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

36 Lab 2 IPv6 Neighbor discovery: Debugs R5 R5#ping 2001:db8:1:56::6 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:DB8:1:56::6, timeout is 2 seconds: Success rate is 100 percent (5/5), round-trip min/avg/max = 0/1/5 ms R5# *Jan 30 22:15:24.668: ICMPv6-ND: DELETE -> INCMP: 2001:DB8:1:56::6 *Jan 30 22:15:24.668: ICMPv6-ND: Sending NS for 2001:DB8:1:56::6 on Ethernet0/0 *Jan 30 22:15:24.669: ICMPv6-ND: Resolving next hop 2001:DB8:1:56::6 on interface Ethernet0/0 *Jan 30 22:15:24.673: ICMPv6-ND: Received NA for 2001:DB8:1:56::6 on Ethernet0/0 from 2001:DB8:1:56::6 *Jan 30 22:15:24.673: ICMPv6-ND: Neighbour 2001:DB8:1:56::6 on Ethernet0/0 : LLA aabb.cc00.5b00 *Jan 30 22:15:24.673: ICMPv6-ND: INCMP -> REACH: 2001:DB8:1:56::6 R5# *Jan 30 22:15:29.722: ICMPv6-ND: Received NS for 2001:DB8:1:56::5 on Ethernet0/0 from FE80::A8BB:CCFF:FE00:5B00 *Jan 30 22:15:29.722: ICMPv6-ND: Sending NA for 2001:DB8:1:56::5 on Ethernet0/0 *Jan 30 22:15:29.723: ICMPv6-ND: STALE -> DELAY: FE80::A8BB:CCFF:FE00:5B00

37 Lab 2 Neighbor Discovery: Renumbering To test the renumbering behavior of IPv6, you want to change the IPv6 address on R5 & R6 to 2001:db8:1:88::/64 from 2001:db8:1:58::/64 First you configure the new IPv6 address of 2001:db8:1:88::/64 on both R5 & R6 Ethernet interface You also want to set the RA interval to 40 seconds To deprecate the old address you want to configure preferred lifetime of 2001:db8:1:58::/64 to 0 and valid lifetime to 50 on both R5 & R6. (Note, may have to shut no shut E0/0 on H2 to rewrite the old valid & prefer lifetime) You noticed that the old prefix of 2001:db8:1:58::/64 is showing as deprecated on H2. Note DEP may or may not show up during show command To get rid of the address completely, you configure the valid lifetime of 2001:db8:1:58::/64 to 0 on both R5 & R6 You noticed on H2 that the old prefix 2001:db8:1:58::/64 disappeared from the cache To clean up the configs, remove the old IPv6 prefix of 2001:db8:1:58::/64 as well as IPv6 nd prefix command from the Ethernet interfaces of both R5 and R6

38 Lab 2 IPv6 Neighbor discovery: Configs R# Configs R5 R5(config)#interface e0/0 R5(config-if)#ipv6 nd ra interval 40 R5(config-if)#ipv6 address 2001:db8:1:88::5/64 R5(config-if)#ipv6 nd prefix 2001:db8:1:58::/ R5(config-if)#end R6 R6(config)#interface e0/0 R6(config-if)#ipv6 nd ra interval 40 R6(config-if)#ipv6 address 2001:db8:1:88::6/64 R6(config-if)#ipv6 nd prefix 2001:db8:1:58::/ R6(config-if)#end

39 Lab 2 IPv6 Neighbor discovery: Verification H2 H2#sh ipv6 int e0/0 Ethernet0/0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5D00 No Virtual link-local address(es): Stateless address autoconfig enabled Global unicast address(es): 2001:DB8:1:56:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:56::/64 [EUI/CAL/PRE] valid lifetime preferred lifetime :DB8:1:57:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:57::/64 [EUI/CAL/PRE] valid lifetime preferred lifetime :DB8:1:58:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:58::/64 [EUI/CAL] valid lifetime 47 preferred lifetime :DB8:1:88:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:88::/64 [EUI/CAL/PRE] valid lifetime preferred lifetime Joined group address(es): FF02::1 FF02::1:FF00:5D00 MTU is 1500 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent

40 Lab 2 IPv6 Neighbor discovery: Debugs H2 H2#deb ipv6 nd *Jan 31 04:26:01.476: ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0 *Jan 31 04:26:01.476: ICMPv6-ND: Prefix : 2001:DB8:1:56::, Length: 64, Vld Lifetime: , Prf Lifetime: , 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:5D :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: , Prf Lifetime: , 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:5D :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:5D :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: , Prf Lifetime: , 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:5D :DB8:1:88:A8BB:CCFF:FE00:5D00/64 is existing

41 Lab 2 IPv6 Neighbor discovery: Configs R# Configs R5 R5(config)#interface e0/0 R5(config-if)#ipv6 nd prefix 2001:db8:1:58::/ R5(config-if)#end R6 R6(config)#interface e0/0 R6(config-if)#ipv6 nd prefix 2001:db8:1:58::/ R6(config-if)#end

42 Lab 2 IPv6 Neighbor discovery: Verification H2 H2#sh ipv6 int e0/0 Ethernet0/0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5D00 No Virtual link-local address(es): Stateless address autoconfig enabled Global unicast address(es): 2001:DB8:1:56:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:56::/64 [EUI/CAL/PRE] valid lifetime preferred lifetime :DB8:1:57:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:57::/64 [EUI/CAL/PRE] valid lifetime preferred lifetime :DB8:1:88:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:88::/64 [EUI/CAL/PRE] valid lifetime preferred lifetime Joined group address(es): FF02::1 FF02::1:FF00:5D00 MTU is 1500 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is enabled, number of DAD attempts: 1 ND reachable time is milliseconds (using 30000) Default router is FE80::A8BB:CCFF:FE00:5B00 on Ethernet0/0 H2#

43 Lab 2 IPv6 Neighbor discovery: Debugs H2 H2#deb ipv6 nd H2# *Jan 31 04:47:34.486: ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0 *Jan 31 04:47:34.486: ICMPv6-ND: Prefix : 2001:DB8:1:56::, Length: 64, Vld Lifetime: , Prf Lifetime: , 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:5D :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: , Prf Lifetime: , 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:5D :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: , Prf Lifetime: , PI Flags: C0 H2# *Jan 31 04:47:34.487: ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:88::/64 eui-64, 2001:DB8:1:88:A8BB:CCFF:FE00:5D :DB8:1:88:A8BB:CCFF:FE00:5D00/64 is existing

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

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

46 Lab 2 IPv6 Neighbor discovery: Configs R# Configs R5 R5(config)#interface e0/0 R5(config-if)#ipv6 nd router-preference high R5(config-if)#end

47 Lab 2 IPv6 Neighbor discovery: Verification H2 H2#sh ipv6 router Router FE80::A8BB:CCFF:FE00:5B00 on Ethernet0/0, last update 0 min Hops 64, Lifetime 1800 sec, AddrFlag=0, OtherFlag=0, MTU=1500 HomeAgentFlag=0, Preference=Medium Reachable time 0 (unspecified), Retransmit time 0 (unspecified) Prefix 2001:DB8:1:56::/64 onlink autoconfig Valid lifetime , preferred lifetime Router FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0, last update 0 min Hops 64, Lifetime 1800 sec, AddrFlag=0, OtherFlag=0, MTU=1500 HomeAgentFlag=0, Preference=High Reachable time 0 (unspecified), Retransmit time 0 (unspecified) Prefix 2001:DB8:1:56::/64 onlink autoconfig Valid lifetime , preferred lifetime H2#sh ipv6 route ::/0 Routing entry for ::/0 Known via "static", distance 2, metric 0 Route count is 1/1, share count 0 Routing paths: FE80::A8BB:CCFF:FE00:5A00, Ethernet0/0 Last updated 00:04:52 ago Note, if you do not see a default route, type the following command and make sure you have the entry from R5 H2#sho ipv6 router

48 Lab 3 : HSRPv Cisco and/or its affiliates. All rights reserved. Cisco Connect 48

49 Lab 3: HSRPv6

50 Lab 3 HSRPv6 Site 2 is running HSRP for IPv4 between R5 and R6 You decided to follow the same scheme for IPv6 also and enabled HSRPv6 between R5 and R6 You noticed on H2 that the default route received from the HSRP active router is a link local address You turned on the IPv6 neighbor discovery debug on H2 to see if you are receiving any RA msgs from R5 or R6 Your primary router for HSRP in IPv4 was R5. You want to make sure R6 is a primary router for IPv6 and when it goes down and comes back up, it should become primary again Configure HSRPv6 in autoconfig mode so it selects a virtual link local address and advertise it as a virtual IPv6 address to hosts Configure HSRP priority & preempt command on R6 so R6 becomes the primary router even when it goes down and comes back up (See slide 32 for details) Turn on deb ipv6 nd on H2 to see what link local is being advertised as a default

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

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

53 Lab 3 HSRPv6: Verification R5 & R6 R5#sh standby ethernet 0/0 1 Ethernet0/0 - Group 1 (version 2) State is Standby 4 state changes, last state change 00:08:17 Virtual IP address is FE80::5:73FF:FEA0:1 Active virtual MAC address is a Local virtual MAC address is a (v2 IPv6 default) Hello time 3 sec, hold time 10 sec Next hello sent in secs Preemption disabled Active router is FE80::A8BB:CCFF:FE00:5B00, priority 105 (expires in sec) MAC address is aabb.cc00.5b00 Standby router is local Priority 100 (default 100) Group name is "hsrp-et0/0-1" (default) R6#sh standby ethernet 0/0 1 Ethernet0/0 - Group 1 (version 2) State is Active 2 state changes, last state change 00:07:58 Virtual IP address is FE80::5:73FF:FEA0:1 Active virtual MAC address is a Local virtual MAC address is a (v2 IPv6 default) Hello time 3 sec, hold time 10 sec Next hello sent in secs Preemption enabled Active router is local Standby router is FE80::A8BB:CCFF:FE00:5A00, priority 100 (expires in sec) Priority 105 (configured 105) Group name is "hsrp-et0/0-1" (default)

54 Lab 3 HSRPv6: Verification R5 & R6 H2#sh ipv6 route ::/0 Routing entry for ::/0 Known via "static", distance 2, metric 0 Route count is 1/1, share count 0 Routing paths: FE80::5:73FF:FEA0:1, Ethernet0/0 Last updated 00:14:23 ago H2#

55 Lab 3 HSRPv6: Debugs H2 H2#deb ipv6 nd H2# *Feb 2 10:24:20.246: ICMPv6-ND: Received RA from FE80::5:73FF:FEA0:1 on Ethernet0/0 *Feb 2 10:24:20.246: ICMPv6-ND: Prefix : 2001:DB8:1:56::, Length: 64, Vld Lifetime: , Prf Lifetime: , 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:5D :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: , Prf Lifetime: , PI Flags: C0 H2# *Feb 2 10:24:20.247: ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:57::/64 eui-64, 2001:DB8:1:57:A8BB:CCFF:FE00:5D :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: , Prf Lifetime: , 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:5D :DB8:1:88:A8BB:CCFF:FE00:5D00/64 is existing

56 Lab 4 : EIGRPv Cisco and/or its affiliates. All rights reserved. Cisco Connect 56

57 Lab 4: EIGRPv6

58 Lab 4 EIGRPv6 Site 2 is running EIGRP for IPv4 between R5 and R6 You decided to follow the same scheme for IPv6 also and enabled EIGRPv6 between R5 and R6 You noticed that in order to advertise the secondary address on the same interface in EIGRPv4 you had to turn off split horizon but in EIGRPv6 you do not have to do anything. This is because split horizon is turned off by default in EIGRP for IPv6 You also noticed that all the control packets of EIGRP for e.g. hellos are sourced from link local address All other functionalities are very much the same as EIGRP for IPv4 The router ID is picked up as the highest loopback address in IPv4

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

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

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

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

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

64 Lab 5 : IPv6 Static Routing 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 64

65 Lab 5 IPv6 Static Routing: IPv6 Static Default Route After planning and configuring all the addressing scheme for your Site 1 and Site 2, you talked with the ISP and request for IPv6 Service. You found out that your ISP has IPv6 internet connectivity only but they have not enabled IPv6 internally in their network so no Site to Site is possible at this moment but they can enable static routing for Site 1 and advertise Site 1 prefix over the IPv6 Internet The ISP has also asked you to enable IPv6 static default routing on R4 pointing towards the ISP router (R1) Configure the IPv6 interface addresses on the link between ISP and R4 as shown on the next slide (::14 is the ISP router and ::15 is R4) Configure a static default route on R4 using a link local address as a next hop pointing towards R1

66 Lab 5: IPv6 Static Routing

67 Lab 5 IPv6 Static routing: Configs R# Configs R1 R1(config)#int s0/0 R1(config-if)#ipv6 add 2001:db8:14:1::14/127 R1(config)#end R4 R4(config)#int s1/0 R1(config-if)#ipv6 add 2001:db8:14:1::15/127 R1(config-if)#ipv6 route ::/0 Serial 1/0 FE80::4AFF:FEA2:851 R1(config)#end

68 Lab 5 IPv6 Static routing: Verification R4 R4#sh ipv6 route ::/0 Routing entry for ::/0 Known via "static", distance 1, metric 0 Route count is 1/1, share count 0 Routing paths: FE80::4AFF:FEA2:851, Serial1/0 Last updated 00:02:15 ago

69 Lab 5 IPv6 Static Routing: IPv6 Static Route The ISP has configured an IPv6 static routing for the LAN address of 2001:db8:1:41::/64 pointing towards R4 Since ISP is connected to IPv6 Internet, Site 1 should be able to reach any IPv6 address on the internet ISP shared their configs and you noticed that they are using global unicast address as a next hop for the static route 2001:db8:1:41::/64 Configure a static route 2001:db8:1:41::/64 on R1 with next-hop of R4 s global address on Ethernet interface Due to the limited lab environment, we will ping 2004:db8::1 from H1 and upon success we will assume that we are connected to IPv6 Internet Ping 2004:db8::1 from H1 and see if its successful

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

71 Lab 5 IPv6 Static routing: Verification R# Verification R1 R1#sh ipv6 route 2001:db8:1:41::/64 Routing entry for 2001:DB8:1:41::/64 Known via "static", distance 1, metric 0 Route count is 1/1, share count 0 Routing paths: 2001:DB8:14:1::15 Last updated 00:11:42 ago R1# H1 H1>ping 2004:db8::1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2004:DB8::1, timeout is 2 seconds: Success rate is 100 percent (5/5), round-trip min/avg/max = 38/39/44 ms H1>

72 Lab 6 : IPv6 Manual Tunnels 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 72

73 Lab 6 IPv6 Manual Tunnels: IPv6oIP4 Site 2 has two connection to the ISP. You talked to the ISP about providing IPv6 connectivity to Site 2 but you came to know that due to some limitation, the ISP can not do dual stack on those two connections ISP gave you the option of a manual tunnel called IPv6 over IPv4 on the link between ISP and R5 For the tunnel to work, both sides needs to have an IPv4 route of each other (Note, IPv4 routing is already established so no need to worry about that Since there is a directly connected interface between R3 and R5, the tunnel source and destinations can easily be chosen as the outgoing interface A new IPv6 address needs to be configured on both side over the tunnel between R3 and R5 in the range 2001:db8:35:1::16/127 as shown in the next slide (::16 on R3 side and ::17 on R5 side) Ping R5 IPv6 tunnel address from R3 and make sure it is successful to determine that the tunnel is up and running

74 Lab 6: IPv6 Manual Tunnels

75 Lab 6 IPv6 Manual Tunnels: Configs R# Configs R5 R5(config-if)#int tun 0 R5(config-if)#tun source s1/0 R5(config-if)#tun destination R5(config-if)#tun mode ipv6ip R5(config-if)#ipv6 address 2001:db8:35:1::17/127 R5(config-if)#end R3 R3(config-if)#int tun 0 R3(config-if)#tun source s1/0 R3(config-if)#tun destination R3(config-if)#tun mode ipv6ip R3(config-if)#ipv6 address 2001:db8:35:1::16/127 R5(config-if)#end

76 Lab 6 IPv6 Manual Tunnels: Verification R3 Tunnel 0 R5 Tunnel 0 R3#sh ipv6 int tun 0 Tunnel0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::A01:2300 No Virtual link-local address(es): Global unicast address(es): 2001:DB8:35:1::16, subnet is 2001:DB8:35:1::16/127 Joined group address(es): FF02::1 FF02::2 FF02::1:FF00:16 FF02::1:FF01:2300 MTU is 1480 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is enabled, number of DAD attempts: 1 ND reachable time is milliseconds (using 30000) ND RAs are suppressed (periodic) Hosts use stateless autoconfig for addresses. R3# R5#sh ipv6 int tun 0 Tunnel0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::A01:2301 No Virtual link-local address(es): Global unicast address(es): 2001:DB8:35:1::17, subnet is 2001:DB8:35:1::16/127 Joined group address(es): FF02::1 FF02::2 FF02::1:FF00:17 FF02::1:FF01:2301 MTU is 1480 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is enabled, number of DAD attempts: 1 ND reachable time is milliseconds (using 30000) ND RAs are suppressed (periodic) Hosts use stateless autoconfig for addresses. R5#

77 Lab 6 IPv6 Manual Tunnels: Verification R3 R3#ping 2001:db8:35:1::17 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:DB8:35:1::17, timeout is 2 seconds: Success rate is 100 percent (5/5), round-trip min/avg/max = 39/39/39 ms R3#

78 Lab 6 IPv6 Manual Tunnels: GRE The link between R3 and R6 has another issue. It can not pass protocol 41 for some reason Due to this limitation, IPv6oIPv4 tunnel can not be established between R3 and R6 ISP provided you an option of using GRE tunnel instead between R3 and R6 Since there is a directly connected interface between R3 and R6, the tunnel source and destinations can easily be chosen as the outgoing interface A new IPv6 address needs to configured on both side over the tunnel between R3 and R6 in the range 2001:db8:36:1::16/127 as shown in the previous slide Ping R6 IPv6 tunnel address from R3 and make sure it is successful to determine that the tunnel is up and running

79 Lab 6 IPv6 Manual Tunnels: Configs R# Configs R6 R6(config-if)#int tun 0 R6(config-if)#tun source s1/0 R6(config-if)#tun destination R6(config-if)#tun mode gre ip R6(config-if)#ipv6 address 2001:db8:36:1::17/127 R6(config-if)#end R3 R3(config-if)#int tun 1 R3(config-if)#tun source s2/0 R3(config-if)#tun destination R3(config-if)#tun mode gre ip R3(config-if)#ipv6 address 2001:db8:36:1::16/127 R3(config-if)#end

80 Lab 6 IPv6 Manual Tunnels: Verification R3 Tunnel 1 R6 Tunnel 0 R3#sh ipv6 int tun 1 Tunnel1 is up, line protocol is up IPv6 is enabled, link-local address is FE80::4AFF:FEA2:853 No Virtual link-local address(es): Global unicast address(es): 2001:DB8:36:1::16, subnet is 2001:DB8:36:1::16/127 Joined group address(es): FF02::1 FF02::2 FF02::1:FF00:16 FF02::1:FFA2:853 MTU is 1476 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is enabled, number of DAD attempts: 1 ND reachable time is milliseconds (using 30000) ND RAs are suppressed (periodic) Hosts use stateless autoconfig for addresses. R3# R6#sh ipv6 int tun 0 Tunnel0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5600 No Virtual link-local address(es): Global unicast address(es): 2001:DB8:36:1::17, subnet is 2001:DB8:36:1::16/127 Joined group address(es): FF02::1 FF02::2 FF02::1:FF00:17 FF02::1:FF00:5600 MTU is 1476 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ICMP unreachables are sent ND DAD is enabled, number of DAD attempts: 1 ND reachable time is milliseconds (using 30000) ND RAs are suppressed (periodic) Hosts use stateless autoconfig for addresses. R6#

81 Lab 6 IPv6 Manual Tunnels: Verification R3 R3#ping 2001:db8:36:1::17 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:DB8:36:1::17, timeout is 2 seconds: Success rate is 100 percent (5/5), round-trip min/avg/max = 37/38/40 ms R3#

82 Lab 7 : OSPFv Cisco and/or its affiliates. All rights reserved. Cisco Connect 82

83 Lab 7 OSPFv3 ISP has received a request from ABC Inc that they want IPv6 connectivity between Site 1 and Site 2. ISP are also making an effort to make their own network dual stack and enabling IPv6 in their core network ISP has been running OSPFv2 internally in their core. They have decided to run OSPFv3 for IPv6 Assign IPv6 address 2001:db8:172:17::2/127 between R2 & R3. ::2 on R2 side and ::3 on R3 side Assign IPv6 address 2001:db8:172:17::/127 between R1 & R2. :: on R1 side and ::1 on R2 side Configure OSPFv3 area 0 between R1 and R2 and area 1 between R2 and R3 as shown in the next slide Put Loopbacks of R1 and R2 into area 0 Redistribute R2 s loopback into OSPFv3 Ping ipv6 Loopback 0 of R3 from the loopback 0 of R1 Compare the difference between OSPFv2 and OSPFv3 LSAs

84 Lab 7: OSPFv3

85 Lab 7 OSPFv3: Configs R# Area 1 Configs R3 R2 R3(config)#ipv6 unicast-routing R3(config)#int lo 0 R3(config-if)#ipv6 add 2001:db8:172:16::3/128 R3(config)#int e0/0 R3(config-if)#ipv6 add 2001:db8:172:17::3/127 R3(config-if)#ipv6 ospf 1 area 1 R3(config)#ipv6 router ospf 1 R3(config-rtr)#redistribute connected R3(config-if)#end R2(config)#ipv6 unicast-routing R2(config-if)#int e0/0 R2(config-if)#ipv6 add 2001:db8:172:17::2/127 R2(config-if)#ipv6 ospf 1 area 1 R2(config-if)#end

86 Lab 7 OSPFv3: Configs R# Area 0 Configs R2 R2(config)#int lo 0 R2(config-if)#ipv6 add 2001:db8:172:16::2/128 R2(config-if)#ipv6 ospf 1 area 0 R2(config-if)#int s1/0 R2(config-if)#ipv6 add 2001:db8:172:17::1/127 R2(config-if)#ipv6 ospf 1 area 0 R2(config-if)#end R1 R1(config)#ipv6 unicast-routing R1(config)#int lo 0 R1(config-if)#ipv6 add 2001:db8:172:16::1/128 R1(config-if)#ipv6 ospf 1 area 0 R1(config)#int s1/0 R1(config-if)#ipv6 add 2001:db8:172:17::/127 R1(config-if)#ipv6 ospf 1 area 0 R1(config-if)#end

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

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

89 Lab 7 OSPFv3: Verification R1 R1#sh ipv6 ospf Routing Process "ospfv3 1" with ID Supports IPv6 Address Family Event-log enabled, Maximum number of events: 1000, Mode: cyclic Router is not originating router-lsas with maximum metric Initial SPF schedule delay 5000 msecs Minimum hold time between two consecutive SPFs msecs Maximum wait time between two consecutive SPFs msecs Minimum LSA interval 5 secs Minimum LSA arrival 1000 msecs LSA group pacing timer 240 secs Interface flood pacing timer 33 msecs Retransmission pacing timer 66 msecs Number of external LSA 1. Checksum Sum 0x0055EC Number of areas in this router is 1. 1 normal 0 stub 0 nssa Graceful restart helper support enabled Reference bandwidth unit is 100 mbps Area BACKBONE(0) Number of interfaces in this area is 2 SPF algorithm executed 3 times Number of LSA 8. Checksum Sum 0x03F283 Number of DCbitless LSA 0 Number of indication LSA 0 Number of DoNotAge LSA 0 Flood list length 0

90 Lab 7 OSPFv3: Verification R3 R3#sh ipv6 ospf Routing Process "ospfv3 1" with ID Supports IPv6 Address Family Event-log enabled, Maximum number of events: 1000, Mode: cyclic Router is not originating router-lsas with maximum metric Initial SPF schedule delay 5000 msecs Minimum hold time between two consecutive SPFs msecs Maximum wait time between two consecutive SPFs msecs Minimum LSA interval 5 secs Minimum LSA arrival 1000 msecs LSA group pacing timer 240 secs Interface flood pacing timer 33 msecs Retransmission pacing timer 66 msecs Number of external LSA 1. Checksum Sum 0x0055EC Number of areas in this router is 1. 1 normal 0 stub 0 nssa Graceful restart helper support enabled Reference bandwidth unit is 100 mbps Area 1 Number of interfaces in this area is 1 SPF algorithm executed 3 times Number of LSA 8. Checksum Sum 0x02CAB4 Number of DCbitless LSA 0 Number of indication LSA 0 Number of DoNotAge LSA 0 Flood list length 0

91 Lab 7 OSPFv3: Verification Area 0 R2#sh ipv6 ospf data OSPFv3 Router with ID ( ) (Process ID 1) Router Link States (Area 0) ADV Router Age Seq# Fragment ID Link count Bits x None x B Inter Area Prefix Link States (Area 0) ADV Router Age Seq# Prefix x :DB8:172:17::2/127 Inter Area Router Link States (Area 0) ADV Router Age Seq# Link ID Dest RtrID x Link (Type-8) Link States (Area 0) ADV Router Age Seq# Link ID Interface x Se1/ x Se1/0 Intra Area Prefix Link States (Area 0) ADV Router Age Seq# Link ID Ref-lstype Ref-LSID x x x x2001 0

92 Lab 7 OSPFv3: Verification R2 (continued..) Router Link States (Area 1) ADV Router Age Seq# Fragment ID Link count Bits x B x E Net Link States (Area 1) ADV Router Age Seq# Link ID Rtr count x Inter Area Prefix Link States (Area 1) ADV Router Age Seq# Prefix x :DB8:172:16::1/ x :DB8:172:17::/ x :DB8:172:16::2/128 Link (Type-8) Link States (Area 1) ADV Router Age Seq# Link ID Interface x Et0/ x Et0/0 Intra Area Prefix Link States (Area 1) ADV Router Age Seq# Link ID Ref-lstype Ref-LSID x x Type-5 AS External Link States ADV Router Age Seq# Prefix x :DB8:35:1::16/ x :DB8:36:1::16/ x :DB8:172:16::3/128

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

94 Lab 8 : BGPv Cisco and/or its affiliates. All rights reserved. Cisco Connect 94

95 Lab 8: BGPv6

96 Lab 8 BGPv6: ibgp ISP is already receiving IPv6 Internet prefixes on R1, Since there is a requirement of providing IPv6 Internet connectivity to Site 2 as well so ISP has to extend BGP all the way upto site 2 for IPv6 by enabling ibgp in their network and ebgp with Site 2. Note, this BGP extension is already present in IPv4 network ibgp peering in the ISP network is following IPv4 BGP method which is to source the update from loopback and peer between loopbacks ISP is following the similar method that they used in IPv4 BGP which is to make R2 as an RR for R1 and R3 and run ibgp between R2-R1 and R2-R3 Advertise 2004:db8::1/128 from R1 under address-family ipv6 Redistribute static route for Site 1 into BGP so site 2 can learn about this prefix Set next-hop-self towards R2 or static routes won t be installed in AS 109 Enable ibgp between R2-R1 and R2-R3 making R1 and R3 as route-reflector clients for R2. Note, disable ipv4-unicast default peering so it does not activate ipv4 peering by default when ipv6 peering is configured

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

98 Lab 8 BGPv6: ibgp Configs R# Area 0 Configs R2 R2(config)#router bgp 109 R2(config-router)#no bgp default ipv4-unicast R2(config-router)#address-family ipv6 R2(config-router-af)#nei 2001:db8:172:16::1 remote 109 R2(config-router-af)#nei 2001:db8:172:16::1 update loop 0 R2(config-router-af)#nei 2001:db8:172:16::1 route-reflector-client R2(config-router-af)#nei 2001:db8:172:16::3 remote 109 R2(config-router-af)#nei 2001:db8:172:16::3 update loop 0 R2(config-router-af)#nei 2001:db8:172:16::3 route-reflector-client R2(config-router-af)#end

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

100 Lab 8 BGPv6: ibgp Verification R2 R2#sh bgp ipv6 unicast BGP table version is 4, local router ID is Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale, m multipath, b backup-path, x best-external, f RT-Filter, a additional-path Origin codes: i - IGP, e - EGP,? - incomplete Network Next Hop Metric LocPrf Weight Path *>i 2004:DB8::1/ :DB8:172:16:: i *>i 2001:DB8:1:41::/ :DB8:172:16:: ? R2#sh bgp ipv6 unicast 2001:db8:1:41::/64 BGP routing table entry for 2001:DB8:1:41::/64, version 29 Paths: (1 available, best #1, table default) Advertised to update-groups: 2 Refresh Epoch 2 Local, (Received from a RR-client) 2001:DB8:172:16::1 (metric 64) from 2001:DB8:172:16::1 ( ) Origin incomplete, metric 0, localpref 100, valid, internal, best

101 Lab 8 BGPv6: ebgp ISP is now ready to provided end to end connectivity between site 1 and Site 2 for ABC You want to use the similar BGP policies and advertisement that you have for ipv4. Enable ebgp between R3 and R5 over link local address and R3 and R6 over a global address over the tunnel interfaces. Note, make sure to advertise Serial2/0 into OSPFv3 or site 2 routes will not get installed in AS 109 Advertise prefixes that are assigned on the Ethernet segment of R5 and R6 and aggregate 2001:db8:1:56::/64 and 2001:db8:1:57::/64 into one block Make sure that H2 can reach IPv6 Internet. Note, in our case 2004:db8::1 represent IPv6 Internet Verify that Site 2 can reach Site 1 by pinging H1 from H2.

102 Lab 8 BGPv6: ebgp Configs R# Area 0 Configs R5 R5(config)#router bgp 1 R5(config-router)#address-family ipv6 R5(config-router-af)#nei FE80::A01:2300%Tunnel0 remote 109 R5(config-router-af)#net 2001:db8:1:56::/64 R5(config-router-af)#net 2001:db8:1:57::/64 R5(config-router-af)#net 2001:db8:1:88::/64 R5(config-router-af)#aggregate-address 2001:db8:1:56::/63 summary-only R5(config-router-af)#end R3 R3(config)#router bgp 109 R3(config-router)#address-family ipv6 R3(config-router-af)#nei FE80::A01:2301%Tunnel0 remote 1 R3(config-router-af)#

103 Lab 8 BGPv6: ebgp Configs R# Area 0 Configs R6 R6(config)#router bgp 1 R6(config-router)#address-family ipv6 R6(config-router-af)#nei 2001:DB8:36:1::16 remote 109 R6(config-router-af)#net 2001:db8:1:56::/64 R6(config-router-af)#net 2001:db8:1:57::/64 R6(config-router-af)#net 2001:db8:1:88::/64 R6(config-router-af)#aggregate-address 2001:db8:1:56::/63 summary-only R6(config-router-af)#end R3 R3(config)#router bgp 109 R3(config-router)#address-family ipv6 R3(config-router-af)#nei 2001:db8:36:1::17 remote 1 R3(config)#int s2/0 R3(config-if)#ip ospf 1 area 1 R3(config-if)#end

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

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

106 Lab 8 BGPv6: ebgp Verification R3 R3#sh bgp ipv6 uni 2001:db8:1:56::/63 BGP routing table entry for 2001:DB8:1:56::/63, version 22 Paths: (2 available, best #2, table default) Advertised to update-groups: 1 3 Refresh Epoch 1 1, (aggregated by ) 2001:DB8:36:1::17 (FE80::A8BB:CCFF:FE00:5600) from 2001:DB8:36:1::17 ( ) Origin IGP, metric 0, localpref 100, valid, external, atomic-aggregate Refresh Epoch 1 1, (aggregated by ) FE80::A01:2301 (FE80::A01:2301) from FE80::A01:2301%Tunnel0 ( ) Origin IGP, metric 0, localpref 100, valid, external, atomic-aggregate, best R3# 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 ms H2#

107 Lab key 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 107

108 Configs R# Configs R1 ipv6 unicast-routing ipv6 cef interface Loopback0 ip address ipv6 address 2001:DB8:172:16::1/128 ipv6 ospf 1 area 0 interface Loopback1 ip address ipv6 address 2004:DB8::1/128 interface Serial0/0 ip address ipv6 address 2001:DB8:14:1::14/127 interface Serial1/0 ip address ipv6 address 2001:DB8:172:17::/127 ipv6 ospf 1 area 0 router ospf 1 passive-interface Serial0/0 network area 0 network area 0 network area 0 router bgp 109 bgp log-neighbor-changes neighbor 2001:DB8:172:16::2 remote-as 109 neighbor 2001:DB8:172:16::2 update-source Loopback0 neighbor remote-as 109 neighbor update-source Loopback0 address-family ipv4 network mask network mask redistribute static no neighbor 2001:DB8:172:16::2 activate neighbor activate exit-address-family address-family ipv6 redistribute static network 2004:DB8::1/128 neighbor 2001:DB8:172:16::2 activate neighbor 2001:DB8:172:16::2 next-hop-self exit-address-family ip route ipv6 route 2001:DB8:1:41::/ :DB8:14:1::15 ipv6 router ospf 1

109 Configs R# Configs R2 ipv6 unicast-routing ipv6 cef interface Loopback0 ip address ipv6 address 2001:DB8:172:16::2/128 ipv6 ospf 1 area 0 interface Ethernet0/0 ip address ipv6 address 2001:DB8:172:17::2/127 ipv6 ospf 1 area 1 interface Serial1/0 ip address ipv6 address 2001:DB8:172:17::1/127 ipv6 ospf 1 area 0 router ospf 1 network area 0 network area 0 network area 1 router bgp 109 bgp log-neighbor-changes neighbor 2001:DB8:172:16::1 remote-as 109 neighbor 2001:DB8:172:16::1 update-source Loopback0 neighbor 2001:DB8:172:16::3 remote-as 109 neighbor 2001:DB8:172:16::3 update-source Loopback0 neighbor remote-as 109 neighbor update-source Loopback0 neighbor remote-as 109 address-family ipv4 no neighbor 2001:DB8:172:16::1 activate no neighbor 2001:DB8:172:16::3 activate neighbor activate neighbor route-reflector-client neighbor activate neighbor route-reflector-client exit-address-family address-family ipv6 neighbor 2001:DB8:172:16::1 activate neighbor 2001:DB8:172:16::1 route-reflector-client neighbor 2001:DB8:172:16::3 activate neighbor 2001:DB8:172:16::3 route-reflector-client exit-address-family ipv6 router ospf 1

110 Configs R# Configs R3 interface Loopback0 ip address ipv6 address 2001:DB8:172:16::3/128 interface Tunnel0 no ip address ipv6 address 2001:DB8:35:1::16/127 tunnel source Serial1/0 tunnel mode ipv6ip tunnel destination interface Tunnel1 no ip address ipv6 address 2001:DB8:36:1::16/127 tunnel source Serial2/0 tunnel destination interface Ethernet0/0 ip address ipv6 address 2001:DB8:172:17::3/127 ipv6 ospf 1 area 1 interface Serial1/0 ip address interface Serial2/0 ip address ip ospf 1 area 1 router ospf 1 redistribute connected subnets network area 1 router bgp 109 bgp log-neighbor-changes neighbor remote-as 1 neighbor remote-as 1 neighbor 2001:DB8:36:1::17 remote-as 1 neighbor 2001:DB8:172:16::2 remote-as 109 neighbor 2001:DB8:172:16::2 update-source Loopback0 neighbor remote-as 109 neighbor update-source Loopback0 neighbor FE80::A01:2301%Tunnel0 remote-as 1 address-family ipv4 network network neighbor activate neighbor activate no neighbor 2001:DB8:36:1::17 activate no neighbor 2001:DB8:172:16::2 activate neighbor activate no neighbor FE80::A01:2301%Tunnel0 activate auto-summary exit-address-family address-family ipv6 neighbor 2001:DB8:36:1::17 activate neighbor 2001:DB8:172:16::2 activate neighbor FE80::A01:2301%Tunnel0 activate exit-address-family ipv6 router ospf 1 redistribute connected

111 Configs R# Configs R4 ipv6 unicast-routing ipv6 cef interface Loopback0 ip address ipv6 address 2001:DB8:1:1::4/128 interface Ethernet0/0 ip address ipv6 address 2001:DB8:1:41::4/64 ipv6 address FD01:DB8:1:41::/64 eui-64 ipv6 nd ra interval 30 interface Serial1/0 ip address ipv6 address 2001:DB8:14:1::15/127 ip route ipv6 route ::/0 Serial1/0 FE80::4AFF:FEA2:851

112 Configs R# Configs R5 interface Loopback0 ip address ipv6 address 2001:DB8:1:1::5/128 ipv6 eigrp 1 interface Tunnel0 no ip address ipv6 address 2001:DB8:35:1::17/127 tunnel source Serial1/0 tunnel mode ipv6ip tunnel destination interface Ethernet0/0 ip address secondary ip address secondary ip address no ip split-horizon eigrp 1 standby version 2 standby 1 ip standby 1 ipv6 autoconfig ipv6 address 2001:DB8:1:56::5/64 ipv6 address 2001:DB8:1:57::5/64 ipv6 address 2001:DB8:1:88::5/64 ipv6 nd router-preference High ipv6 nd ra interval 40 ipv6 eigrp 1 interface Serial1/0 ip address router eigrp 1 network network network network network router bgp 1 bgp log-neighbor-changes neighbor remote-as 1 neighbor update-source Loopback0 neighbor remote-as 109 neighbor FE80::A01:2300%Tunnel0 remote-as 109 address-family ipv4 network mask network mask network mask aggregate-address summary-only neighbor activate neighbor activate no neighbor FE80::A01:2300%Tunnel0 activate exit-address-family address-family ipv6 network 2001:DB8:1:56::/64 network 2001:DB8:1:57::/64 network 2001:DB8:1:88::/64 aggregate-address 2001:DB8:1:56::/63 summary-only neighbor FE80::A01:2300%Tunnel0 activate exit-address-family ipv6 router eigrp 1

113 Configs R# Configs R6 interface Loopback0 ip address ipv6 address 2001:DB8:1:1::6/128 ipv6 eigrp 1 interface Tunnel0 no ip address ipv6 address 2001:DB8:36:1::17/127 tunnel source Serial1/0 tunnel destination interface Ethernet0/0 ip address secondary ip address secondary ip address no ip split-horizon eigrp 1 standby version 2 standby 1 ip standby 1 ipv6 autoconfig standby 1 priority 105 standby 1 preempt ipv6 address 2001:DB8:1:56::6/64 ipv6 address 2001:DB8:1:57::6/64 ipv6 address 2001:DB8:1:88::6/64 ipv6 nd ra interval 40 ipv6 eigrp 1 interface Serial1/0 ip address router eigrp 1 network network network network network router bgp 1 bgp log-neighbor-changes neighbor remote-as 1 neighbor update-source Loopback0 neighbor remote-as 109 neighbor 2001:DB8:36:1::16 remote-as 109 address-family ipv4 network mask network mask network mask aggregate-address summary-only neighbor activate neighbor activate no neighbor 2001:DB8:36:1::16 activate exit-address-family address-family ipv6 network 2001:DB8:1:56::/64 network 2001:DB8:1:57::/64 network 2001:DB8:1:88::/64 aggregate-address 2001:DB8:1:56::/63 summary-only neighbor 2001:DB8:36:1::16 activate exit-address-family ipv6 router eigrp 1

114 Configs R# Configs H1 interface Ethernet0/0 ip address ipv6 address autoconfig ipv6 enable ip route H2 interface Ethernet0/0 ip address ipv6 address autoconfig ipv6 enable ip route

115 Optional Labs 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 115

116 6PE Lab 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 116

117 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

118

119 6PE Instructions MPLS/LDP is pre configured in AS 109 between R1-R2-R3 OSPFv2 is pre-configured between R1-R2-R3 OSPFv2 is pre-configured between R1-R4(E0/0-E0/0) as a PE-CE protocol (over a VRF interface) BGP for IPv4 is pre-configured between R3-R5(E2/0-E1/0) as a 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 case where ipv4 internet routes or a default routes are received on that interface. IPv6 can be enabled on that interface to receive ipv6 internet prefixes and that will be a dual stack environment but in lab, we are only using that interface for IPv6

120 6PE Lab: Enabling OSPFv3 on PE-CE link Configure OSPFv3 between R1-R4 Why are we configuring ospfv3 on a separate interface? R# OSPFv3 R1 R4 interface Ethernet1/0 ipv6 ospf 1 area 0 router ospfv3 1 router-id interface Loopback0 ipv6 ospf 1 area 0 interface Ethernet1/0 ipv6 ospf 1 area 0 router ospfv3 1 router-id

121 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 the redistribution on R1 R# OSPFv3 and Redistribution R1 router ospfv3 1 address-family ipv6 redistribute bgp 109 router bgp 109 address-family ipv6 redistribute ospf 1

122 6PE Lab: Enabling OSPFv3 on PE-CE link Verify that the peers have been established and that R4 loopback address is received and seen in BGP on R1 R# BGPv6 R1 R1#sh ipv6 ospf nei OSPFv3 Router with ID ( ) (Process ID 1) Neighbor ID Pri State Dead Time Interface ID Interface FULL/BDR 00:00:38 6 Ethernet1/0 R1#sh ipv6 route 2001:db8::4 Routing entry for 2001:DB8::4/128 Known via "ospf 1", distance 110, metric 10, type intra area, bgp 109 Route count is 1/1, share count 0 Routing paths: FE80::A8BB:CCFF:FE00:5401, Ethernet1/0 Last updated 03:17:09 ago R1#sh bgp ipv6 unicast Network Next Hop Metric LocPrf Weight Path *> 2001:DB8::4/128 :: ? R1#

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

124 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 Redistribution R3 router bgp 109 address-family ipv6 neighbor 2001:db8:1:2::5 remote-as 2 R5 router bgp 2 address-family ipv6 neighbor 2001:db8:1:2::3 remote-as 109 network 2001:db8:1:5::3/128

125 6PE Lab: Enabling BGPv6 as a PE-CE protocol Verify that the peers has been established by using appropriate show commands Verify that R5 loopback address is seen on R3 Can we configure the PE-CE BGP session over a IPv4 transport in a 6PE scenario? R# BGPv6 R3 R3#sh bgp ipv6 unicast summ Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd 2001:DB8:1:2:: :08:33 1 R3# R3#sh bgp ipv6 unicast BGP table version is 5, local router ID is Network Next Hop Metric LocPrf Weight Path *> 2001:DB8:1:5::3/ :DB8:1:2:: i R3#

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

127 6PE Lab: Enabling 6PE Configure ibgp between R1-R2 (RR) & R2-R3 IPv4 BGP configs are there for comparison purpose What is the purpose of the send-label keyword in 6PE R# *BGPv4 BGPv6 R1& R3 router bgp 109 neighbor remote-as 109 neighbor update-source L0 address-family ipv4 neighbor act router bgp 109 address-family ipv6 neighbor remote-as 109 neighbor update-source L0 neighbor send-label R2 router bgp 109 neighbor remote-as 109 neighbor update-source L0 neighbor remote-as 109 neighbor update-source L0 address-family ipv4 neighbor activate neighbor route-reflector-client neighbor activate neighbor route-reflector-client router bgp 109 address-family ipv6 neighbor remote-as 109 neighbor update-source L0 neighbor remote-as 109 neighbor update-source L0 neighbor send-label neighbor route-reflector-client neighbor send-label neighbor route-reflector-client

128 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# BGPv6 R2 R2#sh bgp ipv6 unicast summ BGP router identifier , local AS number 109 BGP table version is 1, main routing table version 1 Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd :10: :08:38 0 R2#

129 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# BGPv6 R1 R1#sh bgp ipv6 unicast label Network Next Hop In label/out label 2001:DB8::4/128 :: 16/nolabel 2001:DB8:1:5::3/128 ::FFFF: nolabel/17 R1#sh ip cef /32 nexthop Serial2/0 label 17 R1#sh ipv6 cef 2001:db8:1:5::3 2001:DB8:1:5::3/128 nexthop Serial2/0 label 17 17

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

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

132 Lab Key 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 132

133 6PE Lab: Configs R# Configs R1 ipv6 unicast-routing ipv6 cef interface Loopback0 ip address interface Ethernet1/0 ipv6 address 2001:DB8:1:1::1/64 ipv6 ospf 1 area 0 interface Serial2/0 ip address mpls ip router ospfv3 1 address-family ipv6 unicast redistribute bgp 109 exit-address-family router ospf 1 network area 0 router bgp 109 no bgp default ipv4-unicast neighbor remote-as 109 neighbor update-source Loopback0 neighbor remote-as 109 neighbor update-source Loopback0 address-family ipv6 redistribute ospf 1 neighbor activate neighbor send-label exit-address-family

134 6PE Lab: Configs R# Configs R2 interface Loopback0 ip address interface Ethernet0/0 ip address mpls ip interface Serial1/0 ip address mpls ip router ospf 1 nerwork area 0 router bgp 109 neighbor remote-as 109 neighbor update-source Loopback0 neighbor remote-as 109 neighbor update-source Loopback0 address-family ipv6 neighbor activate neighbor send-label neighbor route-reflection-client neighbor activate neighbor send-label neighbor route-reflection-client

135 6PE Lab: Configs R# Configs R3 ipv6 unicast-routing ipv6 cef interface Loopback0 ip address interface Ethernet0/0 no ip address ipv6 address 2001:DB8:1:2::3/64 interface Ethernet1/0 ip address mpls ip router ospf 1 network area 0 router bgp 109 bgp log-neighbor-changes no bgp default ipv4-unicast neighbor remote-as 109 neighbor update-source Loopback0 neighbor 2001:DB8:1:2::5 remote-as 2 address-family ipv6 neighbor activate neighbor send-label neighbor 2001:DB8:1:2::5 activate exit-address-family

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

137 6PE Lab: Configs R# Configs R5 ipv6 unicast-routing ipv6 cef interface Loopback0 ipv6 address 2001:DB8:1:5::3/128 interface Ethernet0/0 ipv6 address 2001:DB8:1:2::5/64 router bgp 2 neighbor 2001:DB8:1:2::3 remote-as 109 address-family ipv6 network 2001:DB8:1:5::3/128 neighbor 2001:DB8:1:2::3 activate exit-address-family

138 6VPE Lab 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 138

139 6VPE Lab Agenda Enabling static a PE-CE protocol for IPv6 Enabling BGP as a PE-CE protocol for IPv6 Enabling 6VPE

140

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

142 6VPE Lab: Enabling static a PE-CE protocol for IPv6 Enable IPv6 VRF on R1 Configure static route between R1-R4 Redistribute static in BGP R# OSPFv3 and Redistribution R1 R4 vrf upgrade-cli multi-af-mode common-policies vrf 6vpe force vrf definition 6vpe address-family ipv6 ipv6 route vrf 6vpe 2001:db8::/64 201:db8:1:1::4 router bgp 109 address-family ipv6 vrf 6vpe redistribute static ipv6 route ::/0 2001:db8:1:1::1

143 6VPE Lab: Enabling static a PE-CE protocol for IPv6 Verify that static route is installed in the VRF and that it is present in BGP What is the purpose of the vrf upgrade-cli command? R# BGPv6 R4 R4#sh ipv6 route ::/0 Routing entry for ::/0 Known via "static", distance 1, metric 0 Backup from "static [2]" Route count is 1/1, share count 0 Routing paths: 2001:DB8:1:1::1 Last updated 00:01:22 ago R1 R1#sh ipv6 route vrf 6vpe incl 2001:DB8::/64 S 2001:DB8::/64 [1/0] R1#sh bgp vpnv6 unicast all incl 2001:DB8::/64 *> 2001:DB8::/ :DB8:1:1:: ? R1#

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

145 6VPE Lab: Enabling BGP as a PE-CE protocol for IPv6 Enable IPv6 VRF on R3 Configure BGP between R3-R5 R# Static and redistribution for V6 R3 vrf upgrade-cli multi-af-mode common-policies vrf 6vpe force vrf definition 6vpe address-family ipv6 router bgp 109 address-family ipv6 vrf 6vpe neighbor 2001:db8:1:2::5 remote-as 2 R5 router bgp 2 no bgp default ipv4-unicast neighbor 2001:db8:1:2::3 remote-as 109 address-family ipv6 network 2001:db8:1:5::3/128 neighbor 2001:db8:1:2::3 activate

146 6VPE Lab: Enabling BGP as a PE-CE protocol for IPv6 Verify the BGP sessions are up and that the routes are advertised R# Static routes R3 R3#sh bgp vpnv6 uni all summ incl :DB8:1:2:: :48:33 1 R3#sh bgp vpnv6 uni all incl 2001:DB8:1:5::3 *> 2001:DB8:1:5::3/128 R3# R5 R5#sh bgp ipv6 uni summ incl :DB8:1:2:: :50:21 1 R5#sh bgp ipv6 uni incl 2001:DB8::/64 *> 2001:DB8::/ :DB8:1:2:: ? R5#

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

148 6VPE Lab: Enabling 6VPE Configure ibgp between R1-R2 (RR) & R2-R3 Compare difference between IPv4 and IPv6 BGP router bgp 109 router bgp 109 *IPv4 BGP configs are there for comparison purpose R# *BGPv4 BGPv6 R1 & R3 neighbor remote-as 109 neighbor update-source L0 address-family vpnv4 neighbor act R2 router bgp 109 neighbor remote-as 109 neighbor update-source L0 neighbor remote-as 109 neighbor update-source L0 address-family vpnv4 neighbor activate neighbor route-reflector-client neighbor activate neighbor route-reflector-client neighbor remote-as 109 neighbor update-source L0 address-family vpnv6 neighbor activate neighbor send-label router bgp 109 neighbor remote-as 109 neighbor update-source L0 neighbor remote-as 109 neighbor update-source L0 address-family vpnv6 neighbor activate neighbor route-reflector-client neighbor activate neighbor route-reflector-client

149 6VPE Lab: Enabling 6VPE Verify the BGP sessions are up on the RR and that the routes are advertised R# Static routes R2 R2#sh bgp vpnv6 uni all summ Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd :00: :57:40 1 R2#sh bgp vpnv6 uni all BGP table version is 3, local router ID is Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale, m multipath, b backup-path, x best-external, f RT-Filter, a additional-path Origin codes: i - IGP, e - EGP,? - incomplete Network Next Hop Metric LocPrf Weight Path Route Distinguisher: 1:1 *>i 2001:DB8::/64 ::FFFF: ? *>i 2001:DB8:1:5::3/128 ::FFFF: i

150 6VPE Lab: Enabling 6VPE Verify that routes are received and installed in the CEF table R# Static routes R1 R1#sh bgp vpnv6 uni all BGP table version is 4, local router ID is Status codes: s suppressed, d damped, h history, * valid, > best, i - internal, r RIB-failure, S Stale, m multipath, b backup-path, x best-external, f RT-Filter, a additional-path Origin codes: i - IGP, e - EGP,? - incomplete Network Next Hop Metric LocPrf Weight Path Route Distinguisher: 1:1 (default for vrf 6vpe) *> 2001:DB8::/ :DB8:1:1:: ? *>i 2001:DB8:1:5::3/128 ::FFFF: i R1#sh ip cef /32 nexthop Serial1/0 label 17 R1#sh ipv6 cef vrf 6vpe 2001:db8:1:5::3 2001:DB8:1:5::3/128 nexthop Serial1/0 label R1#

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

152 Lab Key 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 152

153 6VPE Lab: Configs R# Configs R1 vrf definition 6vpe rd 1:1 route-target export 1:1 route-target import 1:1 address-family ipv6 exit-address-family ipv6 unicast-routing ipv6 cef interface Loopback0 ip address interface Ethernet0/0 vrf forwarding 6vpe ip address ipv6 address 2001:DB8:1:1::1/64 interface Serial1/0 ip address mpls ip router ospf 1 network area 0 router bgp 109 bgp log-neighbor-changes no bgp default ipv4-unicast neighbor remote-as 109 neighbor update-source Loopback0 address-family vpnv6 neighbor activate neighbor send-community extended exit-address-family address-family ipv6 vrf 6vpe redistribute static exit-address-family

154 6VPE Lab: Configs R# Configs R2 interface Loopback0 ip address interface Ethernet0/0 ip address mpls ip interface Serial1/0 ip address mpls ip router ospf 1 nerwork area 0 router bgp 109 no bgp default ipv4-unicast neighbor remote-as 109 neighbor update-source Loopback0 neighbor remote-as 109 neighbor update-source Loopback0 address-family vpnv6 neighbor activate neighbor route-reflection-client neighbor activate neighbor route-reflection-client

155 6VPE Lab: Configs R# Configs R3 vrf definition 6vpe rd 1:1 route-target export 1:1 route-target import 1:1 address-family ipv6 exit-address-family ipv6 unicast-routing ipv6 cef interface Loopback0 ip address interface Ethernet0/0 vrf forwarding 6vpe ip address ipv6 address 2001:DB8:1:2::3/64 interface Ethernet1/0 ip address mpls ip router ospf 1 network area 0 router bgp 109 bgp log-neighbor-changes no bgp default ipv4-unicast neighbor remote-as 109 neighbor update-source Loopback0 address-family vpnv6 neighbor activate neighbor send-community extended exit-address-family address-family ipv6 vrf 6vpe neighbor 2001:DB8:1:2::5 remote-as 2 neighbor 2001:DB8:1:2::5 activate exit-address-family

156 6VPE Lab: Configs R# Configs R4 ipv6 unicast-routing ipv6 cef interface Ethernet0/0 ipv6 address 2001:DB8:1:1::4/64 interface Ethernet1/0 ipv6 address 2001:DB8::/64 eui-64 ipv6 route ::/0 2001:DB8:1:1::1

157 6VPE Lab: Configs R# Configs R5 ipv6 unicast-routing ipv6 cef interface Loopback0 ipv6 address 2001:DB8:1:5::3/128 interface Ethernet0/0 ipv6 address 2001:DB8:1:2::5/64 router bgp 2 no bgp default ipv4-unicast neighbor 2001:DB8:1:2::3 remote-as 109 address-family ipv6 network 2001:DB8:1:5::3/128 neighbor 2001:DB8:1:2::3 activate exit-address-family

158 IPv6 Multicast Lab 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 158

159 IPv6 Multicast Lab Agenda IPv6 Multicast with static RP IPv6 Multicast with Embedded RP

160

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

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

163 Multicast Lab: IPv6 Multicast with static RP Verify that RP is properly configured with R2 loopback address Verify that MLD join has been received from R5 on R3 Do we need to configure IGMP for IPv6 multicast? R# Multicast configuration R3 R3#sh ipv6 pim group-map ff1e::1 IP PIM Group Mapping Table (* indicates group mappings being used) FF00::/8* SM, RP: 2001:DB8:1:: RPF: Et1/0,FE80::A8BB:CCFF:FE00:5200 Info source: Static Uptime: 00:30:53, Groups: 1 R3#sh ipv6 mld groups MLD Connected Group Membership Group Address Interface Uptime Expires FF1E::1 Ethernet0/0 00:28:50 00:03:22 R3#

164 Multicast Lab: IPv6 Multicast with static RP Verify that PIM neighbor relationships are up (R2) Verify that the PIM join has been received by the RP (R2) Why do we see tunnel4 as RPF interface? R# Multicast configuration R2 R2#sh ipv6 pim nei PIM Neighbor Table Mode: B - Bidir Capable, G - GenID Capable Neighbor Address Interface Uptime Expires Mode DR pri FE80::A8BB:CCFF:FE00:5301 Ethernet0/0 00:36:36 00:01:38 B G DR 1 FE80::A8BB:CCFF:FE00:5100 Serial1/0 00:36:48 00:01:33 B G 1 R2#sh ipv6 mroute Multicast Routing Table Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, (*, FF1E::1), 00:38:08/00:02:39, RP 2001:DB8:1::, flags: S Incoming interface: Tunnel4 RPF nbr: 2001:DB8:1:: Immediate Outgoing interface list: Ethernet0/0, Forward, 00:38:08/00:02:39

165 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 configuration R3 R3#sh ipv6 mroute Multicast Routing Table Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, L - Local, I - Received Source Specific Host Report, P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT Timers: Uptime/Expires Interface state: Interface, State (2001:DB8:1:1::4, FF1E::1), 00:00:03/00:03:28, flags: SJT Incoming interface: Serial2/0 RPF nbr: FE80::A8BB:CCFF:FE00:5100 Inherited Outgoing interface list: Ethernet0/0, Forward, 00:41:26/never R3#

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

167 Multicast Lab: IPv6 Multicast with Embedded RP Make R1 an RP Add MLD Join on Receiver for group FF7E:130:2001:DB8:1::99 to simulate a receiver Can you identify R1 loopback address in the embedded RP multicast address R# Multicast configuration R1 ipv6 pim rp-address 2001:db8:1::1 Receiver interface Ethernet0/0 ipv6 mld join-group FF7E:130:2001:DB8:1::99

168 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 configuration R3 R3#sh ipv6 pim group-map FF7E:130:2001:DB8:1::99 IP PIM Group Mapping Table (* indicates group mappings being used) FF7E:130:2001:DB8:1::/80* SM, RP: 2001:DB8:1::1 RPF: Se2/0,FE80::A8BB:CCFF:FE00:5100 Info source: Embedded Uptime: 00:11:31, Groups: 1 R3#sh ipv6 mroute FF7E:130:2001:DB8:1::99.. (*, FF7E:130:2001:DB8:1::99), 00:09:35/never, RP 2001:DB8:1::1, flags: SCJ Incoming interface: Serial2/0 RPF nbr: FE80::A8BB:CCFF:FE00:5100 Immediate Outgoing interface list: Ethernet0/0, Forward, 00:09:35/never R3#

169 Multicast Lab: IPv6 Multicast with Embedded RP Verify that R1 (RP) has received the join coming from R3 Verify that the PIM join has been received by the RP (R2) Why do we see tunnel3 as RPF interface? R# Multicast configuration R1 R1#sh ipv6 mroute FF7E:130:2001:DB8:1::99 Multicast Routing Table Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, L - Local, I - Received Source Specific Host Report, P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT Timers: Uptime/Expires Interface state: Interface, State (*, FF7E:130:2001:DB8:1::99), 00:16:13/00:03:26, RP 2001:DB8:1::1, flags: S Incoming interface: Tunnel3 RPF nbr: 2001:DB8:1::1 Immediate Outgoing interface list: Serial2/0, Forward, 00:16:13/00:03:26 R1#

170 Multicast Lab: IPv6 Multicast with Embedded RP Ping multicast address FF7E:130:2001:DB8:1::99 from R4 and verify echo replies are received from R5 Verify that R1 has a (S,G) entry for R4 R# Multicast configuration R1 R1#sh ipv6 mroute FF7E:130:2001:DB8:1::99 Multicast Routing Table.. (*, FF7E:130:2001:DB8:1::99), 00:20:43/00:02:56, RP 2001:DB8:1::1, flags: S Incoming interface: Tunnel3 RPF nbr: 2001:DB8:1::1 Immediate 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: SFT Incoming interface: Ethernet0/0 RPF nbr: 2001:DB8:1:1::4 Immediate Outgoing interface list: Serial2/0, Forward, 00:00:02/00:03:27 R1#

171 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 1 preceding 0x30 represents the last 4 bits of the RP address. 0x30 (48 in decimal) is the actual length we use to retrieve the RP address. As stated in RFC4601, Cisco IOS uses a tunnel interface for the PIM register process. On the RP, this tunnel interface is used as the incoming interface for (*,G) entries, as encapsulated multicast packets will be received on that interface.

172 IPv6 Multicast Lab Key

173 Lab Key 2012 Cisco and/or its affiliates. All rights reserved. Cisco Connect 173

174 Multicast Lab: Configs R# Configs R1 ipv6 unicast-routing ipv6 cef ipv6 multicast-routing interface Loopback0 ipv6 address 2001:DB8:1::1/128 ipv6 ospf 1 area 0 interface Ethernet0/0 ipv6 address 2001:DB8:1:1::1/64 ipv6 ospf 1 area 0 interface Serial1/0 ipv6 address 2001:DB8:1::3/127 ipv6 ospf 1 area 0 interface Serial2/0 ipv6 address 2001:DB8::3/64 ipv6 ospf 1 area 0 For static RP exercise ipv6 pim rp-address 2001:db8:1:: (R2 Loopback address) For embedded RP exercise ipv6 pim rp-address 2001:DB8:1::1 (Local Loopback address) ipv6 router ospf 1

175 Multicast Lab: Configs R# Configs R2 ipv6 unicast-routing ipv6 cef ipv6 multicast-routing interface Loopback0 ipv6 address 2001:DB8:1::/128 ipv6 ospf 1 area 0 interface Ethernet0/0 ipv6 address 2001:DB8:1::4/127 ipv6 ospf 1 area 0 interface Serial1/0 ipv6 address 2001:DB8:1::2/127 ipv6 ospf 1 area 0 ipv6 pim rp-address 2001:DB8:1:: ipv6 router ospf 1

176 Multicast Lab: Configs R# Configs R3 ipv6 unicast-routing ipv6 cef ipv6 multicast-routing interface Loopback0 ipv6 address 2001:DB8:1:3::3/128 ipv6 ospf 1 area 0 interface Ethernet0/0 ipv6 address 2001:DB8:1:2::3/64 ipv6 ospf 1 area 0 interface Ethernet1/0 ipv6 address 2001:DB8:1::5/127 ipv6 ospf 1 area 0 interface Serial2/0 ipv6 address 2001:DB8::5/64 ipv6 ospf 1 area 0 ipv6 pim rp-address 2001:DB8:1:: ipv6 router ospf 1

177 Multicast Lab: Configs R# Configs R4(Source) no ipv6 cef interface Ethernet0/0 ipv6 address 2001:DB8:1:1::4/64 R5(Receiver) no ipv6 cef interface Ethernet0/0 ipv6 address 2001:DB8:1:2::5/64 ipv6 mld join-group FF05::1:1 ipv6 mld join-group FF7E:130:2001:DB8:1::99

178 For larger statements and quotes, use this slide layout to format the long references in all of your presentations. Source Name Placement Cisco and/or its affiliates. All rights reserved. Cisco Cisco Confidential Connect 178

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

Chapter 2 Lab 2-2, EIGRP Load Balancing

Chapter 2 Lab 2-2, EIGRP Load Balancing Chapter 2 Lab 2-2, EIGRP Load Balancing Topology Objectives Background Review a basic EIGRP configuration. Explore the EIGRP topology table. Identify successors, feasible successors, and feasible distances.

More information

CertificationKits.com EIGRP Sample CCNA Lab. EIGRP Routing. The purpose of this lab is to explore the functionality of the EIGRP routing protocol.

CertificationKits.com EIGRP Sample CCNA Lab. EIGRP Routing. The purpose of this lab is to explore the functionality of the EIGRP routing protocol. EIGRP Routing The purpose of this lab is to explore the functionality of the EIGRP routing protocol. Hardware & Configuration Required for this Lab Two Cisco routers with two Fast Ethernet interfaces and

More information

Central America Workshop - Guatemala City Guatemala 30 January - 1 February 07. IPv6 Router s Configuration

Central America Workshop - Guatemala City Guatemala 30 January - 1 February 07. IPv6 Router s Configuration Central America Workshop - Guatemala City Guatemala 30 January - 1 February 07 IPv6 Router s Configuration Pedro Lorga (lorga@fccn.pt) Simon Muyal (muyal@renater.pt) Piers O'Hanlon (p.ohanlon@cs.ucl.ac.uk)

More information

Chapter 3 Configuring Basic IPv6 Connectivity

Chapter 3 Configuring Basic IPv6 Connectivity Chapter 3 Configuring Basic IPv6 Connectivity This chapter explains how to get a ProCurve Routing Switch that supports IPv6 up and running. To configure basic IPv6 connectivity, you must do the following:

More information

CCNP CISCO CERTIFIED NETWORK PROFESSIONAL LAB MANUAL

CCNP CISCO CERTIFIED NETWORK PROFESSIONAL LAB MANUAL CCNP CISCO CERTIFIED NETWORK PROFESSIONAL LAB MANUAL VER 2.0 Page 1 of 315 ACKNOWLEDGEMENT We can write a 1000 page book, but we can t find enough words to describe the credit Mr. Siddiq Ahmed deserves

More information

IPv6 over MPLS VPN. Contents. Prerequisites. Document ID: 112085. Requirements

IPv6 over MPLS VPN. Contents. Prerequisites. Document ID: 112085. Requirements IPv6 over MPLS VPN Document ID: 112085 Contents Introduction Prerequisites Requirements Components Used Conventions Configure Network Diagram VRF Configuration Multiprotocol BGP (MP BGP) Configuration

More information

GLBP Gateway Load Balancing Protocol

GLBP Gateway Load Balancing Protocol GLBP Gateway Load Balancing Protocol By MEDDANE Redouane Cisco Instructor 1 How GLBP Works. GLBP works by making use of a single virtual IP address, which is configured as the default gateway on the hosts.

More information

CCIE R&S Lab Workbook Volume I Version 5.0

CCIE R&S Lab Workbook Volume I Version 5.0 Copyright Information, Inc. All rights reserved. The following publication, CCIE R&S Lab Workbook Volume I Version 5.0, was developed by Internetwork Expert, Inc. All rights reserved. No part of this publication

More information

Interconnecting Cisco Networking Devices Part 2

Interconnecting Cisco Networking Devices Part 2 Interconnecting Cisco Networking Devices Part 2 Course Number: ICND2 Length: 5 Day(s) Certification Exam This course will help you prepare for the following exam: 640 816: ICND2 Course Overview This course

More information

IPv6 Diagnostic and Troubleshooting

IPv6 Diagnostic and Troubleshooting 8 IPv6 Diagnostic and Troubleshooting Contents Introduction.................................................. 8-2 ICMP Rate-Limiting........................................... 8-2 Ping for IPv6 (Ping6)..........................................

More information

IPv6 Functionality. Jeff Doyle IPv6 Solutions Manager jeff@juniper.net

IPv6 Functionality. Jeff Doyle IPv6 Solutions Manager jeff@juniper.net IPv6 Functionality Jeff Doyle IPv6 Solutions Manager jeff@juniper.net Copyright 2003 Juniper Networks, Inc. Agenda ICMPv6 Neighbor discovery Autoconfiguration Agenda ICMPv6 Neighbor discovery Autoconfiguration

More information

ASA 9.x EIGRP Configuration Example

ASA 9.x EIGRP Configuration Example ASA 9.x EIGRP Configuration Example Document ID: 91264 Contributed by Dinkar Sharma, Magnus Mortensen, and Prashant Joshi, Cisco TAC Engineers. May 13, 2015 Contents Introduction Prerequisites Requirements

More information

IPv6 Fundamentals: A Straightforward Approach

IPv6 Fundamentals: A Straightforward Approach IPv6 Fundamentals: A Straightforward Approach to Understanding IPv6 Rick Graziani Cisco Press 800 East 96th Street Indianapolis, IN 46240 IPv6 Fundamentals Contents Introduction xvi Part I: Background

More information

IPv6 for Cisco IOS Software, File 2 of 3: Configuring

IPv6 for Cisco IOS Software, File 2 of 3: Configuring IPv6 for Cisco IOS Software, File 2 of 3: Configuring This document provides configuration tasks for the Cisco implementation of IP version 6 (IPv6) in the Cisco IOS software and includes the following

More information

Objectives. Router as a Computer. Router components and their functions. Router components and their functions

Objectives. Router as a Computer. Router components and their functions. Router components and their functions 2007 Cisco Systems, Inc. All rights reserved. Cisco Public Objectives Introduction to Routing and Packet Forwarding Routing Protocols and Concepts Chapter 1 Identify a router as a computer with an OS and

More information

CCNP ROUTE 6.0 Student Lab Manual

CCNP ROUTE 6.0 Student Lab Manual CCNP ROUTE 6.0 Student Lab Manual This document is exclusive property of Cisco Systems, Inc. Permission is granted to print and copy this document for non-commercial distribution and exclusive use by instructors

More information

Example: Advertised Distance (AD) Example: Feasible Distance (FD) Example: Successor and Feasible Successor Example: Successor and Feasible Successor

Example: Advertised Distance (AD) Example: Feasible Distance (FD) Example: Successor and Feasible Successor Example: Successor and Feasible Successor 642-902 Route: Implementing Cisco IP Routing Course Introduction Course Introduction Module 01 - Planning Routing Services Lesson: Assessing Complex Enterprise Network Requirements Cisco Enterprise Architectures

More information

Table of Contents. Cisco How Does Load Balancing Work?

Table of Contents. Cisco How Does Load Balancing Work? Table of Contents How Does Load Balancing Work?...1 Document ID: 5212...1 Introduction...1 Prerequisites...1 Requirements...1 Components Used...1 Conventions...1 Load Balancing...1 Per Destination and

More information

This document is exclusive property of Cisco Systems, Inc. Permission is granted to print and copy this document for non-commercial distribution and

This document is exclusive property of Cisco Systems, Inc. Permission is granted to print and copy this document for non-commercial distribution and This document is exclusive property of Cisco Systems, Inc. Permission is granted to print and copy this document for non-commercial distribution and exclusive use by instructors in the CCNP: Implementing

More information

Sample Configuration Using the ip nat outside source static

Sample Configuration Using the ip nat outside source static Sample Configuration Using the ip nat outside source static Table of Contents Sample Configuration Using the ip nat outside source static Command...1 Introduction...1 Before You Begin...1 Conventions...1

More information

IPv6 Associated Protocols

IPv6 Associated Protocols IPv6 Associated Protocols 1 New Protocols (1) New features are specified in IPv6 Protocol -RFC 2460 DS Neighbor Discovery (NDP) -RFC 4861 DS Auto-configuration : Stateless Address Auto-configuration -RFC

More information

GLBP - Gateway Load Balancing Protocol

GLBP - Gateway Load Balancing Protocol GLBP - Gateway Load Balancing Protocol Gateway Load Balancing Protocol (GLBP) protects data traffic from a failed router or circuit, like Hot Standby Router Protocol (HSRP) and Virtual Router Redundancy

More information

Cisco Certified Network Associate Exam. Operation of IP Data Networks. LAN Switching Technologies. IP addressing (IPv4 / IPv6)

Cisco Certified Network Associate Exam. Operation of IP Data Networks. LAN Switching Technologies. IP addressing (IPv4 / IPv6) Cisco Certified Network Associate Exam Exam Number 200-120 CCNA Associated Certifications CCNA Routing and Switching Operation of IP Data Networks Operation of IP Data Networks Recognize the purpose and

More information

640-816: Interconnecting Cisco Networking Devices Part 2 v1.1

640-816: Interconnecting Cisco Networking Devices Part 2 v1.1 640-816: Interconnecting Cisco Networking Devices Part 2 v1.1 Course Introduction Course Introduction Chapter 01 - Small Network Implementation Introducing the Review Lab Cisco IOS User Interface Functions

More information

Quick Note 20. Configuring a GRE tunnel over an IPSec tunnel and using BGP to propagate routing information. (GRE over IPSec with BGP)

Quick Note 20. Configuring a GRE tunnel over an IPSec tunnel and using BGP to propagate routing information. (GRE over IPSec with BGP) Quick Note 20 Configuring a GRE tunnel over an IPSec tunnel and using BGP to propagate routing information. (GRE over IPSec with BGP) Appendix A GRE over IPSec with Static routes UK Support August 2012

More information

Lab 4.2 Challenge Lab: Implementing MPLS VPNs

Lab 4.2 Challenge Lab: Implementing MPLS VPNs Lab 4.2 Challenge Lab: Implementing MPLS VPNs Learning Objectives Configure Open Shortest Path First (OSPF) and Enhanced Interior Gateway Routing Protocol (EIGRP) on a router Enable MPLS on a router Verify

More information

CCNA 2 v5.0 Routing Protocols Final Exam Answers

CCNA 2 v5.0 Routing Protocols Final Exam Answers CCNA 2 v5.0 Routing Protocols Final Exam Answers 1 Refer to the exhibit. What can be concluded about network 192.168.1.0 in the R2 routing table? This network was learned through summary LSAs from an ABR.*

More information

IPv6 Addressing and Subnetting

IPv6 Addressing and Subnetting APNIC elearning: IPv6 Addressing and Subnetting Contact: training@apnic.net eip602_v1.0 Overview IPv6 Address Text Representation IPv6 Addressing Structure IPv6 Address Management Hierarchy Local Addresses

More information

IPv6 Trace Analysis using Wireshark Nalini Elkins, CEO Inside Products, Inc. Nalini.elkins@insidethestack.com

IPv6 Trace Analysis using Wireshark Nalini Elkins, CEO Inside Products, Inc. Nalini.elkins@insidethestack.com 1 IPv6 Trace Analysis using Wireshark Nalini Elkins, CEO Inside Products, Inc. Nalini.elkins@insidethestack.com Agenda What has not changed between IPv4 and IPv6 traces What has changed between IPv4 and

More information

Configuring Denial of Service Protection

Configuring Denial of Service Protection 24 CHAPTER This chapter contains information on how to protect your system against Denial of Service (DoS) attacks. The information covered in this chapter is unique to the Catalyst 6500 series switches,

More information

Configuring Static and Dynamic NAT Simultaneously

Configuring Static and Dynamic NAT Simultaneously Configuring Static and Dynamic NAT Simultaneously Document ID: 13778 Contents Introduction Prerequisites Requirements Components Used Conventions Configuring NAT Related Information Introduction In some

More information

Configuring a Gateway of Last Resort Using IP Commands

Configuring a Gateway of Last Resort Using IP Commands Configuring a Gateway of Last Resort Using IP Commands Document ID: 16448 Contents Introduction Prerequisites Requirements Components Used Conventions ip default gateway ip default network Flag a Default

More information

Table of Contents. Cisco Configuring a Basic MPLS VPN

Table of Contents. Cisco Configuring a Basic MPLS VPN Table of Contents Configuring a Basic MPLS VPN...1 Introduction...1 Prerequisites...1 Requirements...1 Components Used...2 Related Products...2 Conventions...2 Configure...3 Network Diagram...3 Configuration

More information

BGP DDoS Mitigation. Gunter Van de Velde. Sr Technical Leader NOSTG, Cisco Systems. May 2013. 2012 Cisco and/or its affiliates. All rights reserved.

BGP DDoS Mitigation. Gunter Van de Velde. Sr Technical Leader NOSTG, Cisco Systems. May 2013. 2012 Cisco and/or its affiliates. All rights reserved. BGP DDoS Mitigation Gunter Van de Velde Sr Technical Leader NOSTG, Cisco Systems May 2013 2012 Cisco and/or its affiliates. All rights reserved. 1 A simple DDoS mitigation mechanism explained Bertrand

More information

IP Routing Configuring Static Routes

IP Routing Configuring Static Routes 11 IP Routing Configuring Static Routes Contents Overview..................................................... 11-3 IP Addressing.............................................. 11-3 Networks.................................................

More information

Lab: Basic Router Configuration

Lab: Basic Router Configuration Topology Diagram Addressing Table Device Interface IP Address Subnet Mask Def. Gateway R1 Fa0/0 192.168.1.1 255.255.255.0 N/A S0/0/0 192.168.2.1 255.255.255.0 N/A R2 Fa0/0 192.168.3.1 255.255.255.0 N/A

More information

- IPv6 Addressing - (References: http://cc.uoregon.edu/cnews/spring2001/whatsipv6.html; http://en.wikipedia.org/wiki/ipv6)

- IPv6 Addressing - (References: http://cc.uoregon.edu/cnews/spring2001/whatsipv6.html; http://en.wikipedia.org/wiki/ipv6) 1 IPv6 Basics - IPv6 Addressing - The most widespread implementation of IP currently is IPv4, which utilizes a 32-bit address. Mathematically, a 32-bit address can provide roughly 4 billion unique IP addresses

More information

IPv6 Hardening Guide for Windows Servers

IPv6 Hardening Guide for Windows Servers IPv6 Hardening Guide for Windows Servers How to Securely Configure Windows Servers to Prevent IPv6-related Attacks Version: 1.0 Date: 22/12/2014 Classification: Public Author(s): Antonios Atlasis TABLE

More information

IOS NAT Load Balancing with Optimized Edge Routing for Two Internet Connections

IOS NAT Load Balancing with Optimized Edge Routing for Two Internet Connections IOS NAT Load Balancing with Optimized Edge Routing for Two Internet Connections Document ID: 99427 Contents Introduction Prerequisites Requirements Components Used Conventions Configure Network Diagram

More information

CCNA2 Chapter 11 Practice

CCNA2 Chapter 11 Practice CCNA2 Chapter 11 Practice Two neighbouring routers are configured for OSPF, but they have different hello and dead intervals. What will happen? They will become adjacent as long as they are configured

More information

Neighbour Discovery in IPv6

Neighbour Discovery in IPv6 Neighbour Discovery in IPv6 Andrew Hines Topic No: 17 Email: hines@zitmail.uni-paderborn.de Organiser: Christian Schindelhauer University of Paderborn Immatriculation No: 6225220 August 4, 2004 1 Abstract

More information

Frame Mode MPLS Implementation

Frame Mode MPLS Implementation CHAPTER 4 Frame Mode MPLS Implementation Lab 4-1: Configuring Frame Mode MPLS (4.5.1) In this lab, you learn how to do the following: Configure EIGRP on a router. Configure LDP on a router. Change the

More information

Sample Configuration Using the ip nat outside source list C

Sample Configuration Using the ip nat outside source list C Sample Configuration Using the ip nat outside source list C Table of Contents Sample Configuration Using the ip nat outside source list Command...1 Introduction...1 Before You Begin...1 Conventions...1

More information

Troubleshooting IP Routing

Troubleshooting IP Routing C H A P T E R 7 Troubleshooting IP Routing This troubleshooting chapter has several goals. First, it explains several tools and functions not covered in Chapters 4 through 6 specifically, tools that can

More information

Routing Protocols (RIP, OSPF, BGP)

Routing Protocols (RIP, OSPF, BGP) Chapter 13 Routing Protocols (RIP, OSPF, BGP) INTERIOR AND EXTERIOR ROUTING RIP OSPF BGP 1 The McGraw-Hill Companies, Inc., 2000 1 Introduction Packets may pass through several networks on their way to

More information

How To Learn Cisco Cisco Ios And Cisco Vlan

How To Learn Cisco Cisco Ios And Cisco Vlan Interconnecting Cisco Networking Devices: Accelerated Course CCNAX v2.0; 5 Days, Instructor-led Course Description Interconnecting Cisco Networking Devices: Accelerated (CCNAX) v2.0 is a 60-hour instructor-led

More information

OSPF Configuring Multi-Area OSPF

OSPF Configuring Multi-Area OSPF OSPF Configuring Multi-Area OSPF Objective In this lab configure a multiarea OSPF operation, interarea summarization, external route summarization, and default routing. Scenario International Travel Agency

More information

Lab 5-5 Configuring the Cisco IOS DHCP Server

Lab 5-5 Configuring the Cisco IOS DHCP Server Lab 5-5 Configuring the Cisco IOS DHCP Server Learning Objectives Configure and verify the operation of the Cisco IOS DHCP server Configure an IP Helper address Review the EIGRP configuration Topology

More information

Tomás P. de Miguel DIT-UPM. dit UPM

Tomás P. de Miguel DIT-UPM. dit UPM Tomás P. de Miguel DIT- 15 12 Internet Mobile Market Phone.com 15 12 in Millions 9 6 3 9 6 3 0 1996 1997 1998 1999 2000 2001 0 Wireless Internet E-mail subscribers 2 (January 2001) Mobility The ability

More information

CIRA s experience in deploying IPv6

CIRA s experience in deploying IPv6 CIRA s experience in deploying IPv6 Canadian Internet Registration Authority (CIRA) Jacques Latour Director, Information Technology Ottawa, April 29, 2011 1 About CIRA The Registry that operates the Country

More information

Cisco Configuring Basic MPLS Using OSPF

Cisco Configuring Basic MPLS Using OSPF Table of Contents Configuring Basic MPLS Using OSPF...1 Introduction...1 Mechanism...1 Hardware and Software Versions...2 Network Diagram...2 Configurations...2 Quick Configuration Guide...2 Configuration

More information

Understanding Route Redistribution & Filtering

Understanding Route Redistribution & Filtering Understanding Route Redistribution & Filtering When to Redistribute and Filter PAN-OS 5.0 Revision B 2013, Palo Alto Networks, Inc. www.paloaltonetworks.com Contents Overview... 3 Route Redistribution......

More information

Introduction about cisco company and its products (network devices) Tell about cisco offered courses and its salary benefits (ccna ccnp ccie )

Introduction about cisco company and its products (network devices) Tell about cisco offered courses and its salary benefits (ccna ccnp ccie ) CCNA Introduction about cisco company and its products (network devices) Tell about cisco offered courses and its salary benefits (ccna ccnp ccie ) Inform about ccna its basic course of networking Emergence

More information

Static and Dynamic Network Configuration

Static and Dynamic Network Configuration CHAPTER 6 This chapter describes: Static Networks Dynamic Networks Static Networks The mobile access router can be part of a static network or a dynamic network. A static network supports stub routers

More information

IPv6 Protocols & Standards. ISP/IXP Workshops

IPv6 Protocols & Standards. ISP/IXP Workshops IPv6 Protocols & Standards ISP/IXP Workshops 1 So what has really changed? Expanded address space Address length quadrupled to 16 bytes Header Format Simplification Fixed length, optional headers are daisy-chained

More information

VRRPv3: Object Tracking Integration

VRRPv3: Object Tracking Integration Virtual Router Redundancy Protocol (VRRP) enables a group of devices to form a single virtual device to provide redundancy. The LAN clients then can be configured with the virtual device as the default

More information

How To Understand Bg

How To Understand Bg Table of Contents BGP Case Studies...1 BGP4 Case Studies Section 1...3 Contents...3 Introduction...3 How Does BGP Work?...3 ebgp and ibgp...3 Enabling BGP Routing...4 Forming BGP Neighbors...4 BGP and

More information

Chapter 4. Distance Vector Routing Protocols

Chapter 4. Distance Vector Routing Protocols Chapter 4 Distance Vector Routing Protocols CCNA2-1 Chapter 4 Note for Instructors These presentations are the result of a collaboration among the instructors at St. Clair College in Windsor, Ontario.

More information

19531 - Telematics. 9th Tutorial - IP Model, IPv6, Routing

19531 - Telematics. 9th Tutorial - IP Model, IPv6, Routing 19531 - Telematics 9th Tutorial - IP Model, IPv6, Routing Bastian Blywis Department of Mathematics and Computer Science Institute of Computer Science 06. January, 2011 Institute of Computer Science Telematics

More information

IP Routing Features. Contents

IP Routing Features. Contents 7 IP Routing Features Contents Overview of IP Routing.......................................... 7-3 IP Interfaces................................................ 7-3 IP Tables and Caches........................................

More information

"Charting the Course...

Charting the Course... Description "Charting the Course... Course Summary Interconnecting Cisco Networking Devices: Accelerated (CCNAX), is a course consisting of ICND1 and ICND2 content in its entirety, but with the content

More information

100-101: Interconnecting Cisco Networking Devices Part 1 v2.0 (ICND1)

100-101: Interconnecting Cisco Networking Devices Part 1 v2.0 (ICND1) 100-101: Interconnecting Cisco Networking Devices Part 1 v2.0 (ICND1) Course Overview This course provides students with the knowledge and skills to implement and support a small switched and routed network.

More information

NICS IPv6 Best Practices Guide

NICS IPv6 Best Practices Guide NICS IPv6 Best Practices Guide Recommendations for Deploying IPv6 Version: 1.3 Date: April 22, 2014 scott.hovis@nasa.gov Document Change Log Date Version Change Author Affected Section 1/15/2014 1.0 Scott

More information

IPv4/IPv6 Transition Mechanisms. Luka Koršič, Matjaž Straus Istenič

IPv4/IPv6 Transition Mechanisms. Luka Koršič, Matjaž Straus Istenič IPv4/IPv6 Transition Mechanisms Luka Koršič, Matjaž Straus Istenič IPv4/IPv6 Migration Both versions exist today simultaneously Dual-stack IPv4 and IPv6 protocol stack Address translation NAT44, LSN, NAT64

More information

How To Configure A Cisco Router With A Cio Router

How To Configure A Cisco Router With A Cio Router CHAPTER 1 This chapter provides procedures for configuring the basic parameters of your Cisco router, including global parameter settings, routing protocols, interfaces, and command-line access. It also

More information

Security Assessment of Neighbor Discovery for IPv6

Security Assessment of Neighbor Discovery for IPv6 Security Assessment of Neighbor Discovery for IPv6 Fernando Gont project carried out on behalf of UK Centre for the Protection of National Infrastructure LACNIC XV 15 al 20 de Mayo de 2011. Cancún, México

More information

IOS NAT Load Balancing for Two ISP Connections

IOS NAT Load Balancing for Two ISP Connections IOS NAT Load Balancing for Two ISP Connections Document ID: 100658 Contents Introduction Prerequisites Requirements Components Used Conventions Configure Network Diagram Configurations Verify Troubleshoot

More information

Chapter 7 Lab 7-1, Configuring Switches for IP Telephony Support

Chapter 7 Lab 7-1, Configuring Switches for IP Telephony Support Chapter 7 Lab 7-1, Configuring Switches for IP Telephony Support Topology Objectives Background Configure auto QoS to support IP phones. Configure CoS override for data frames. Configure the distribution

More information

Route Discovery Protocols

Route Discovery Protocols Route Discovery Protocols Columbus, OH 43210 Jain@cse.ohio-State.Edu http://www.cse.ohio-state.edu/~jain/ 1 Overview Building Routing Tables Routing Information Protocol Version 1 (RIP V1) RIP V2 OSPF

More information

Router and Routing Basics

Router and Routing Basics Router and Routing Basics Malin Bornhager Halmstad University Session Number 2002, Svenska-CNAP Halmstad University 1 Routing Protocols and Concepts CCNA2 Routing and packet forwarding Static routing Dynamic

More information

IPv6 Infrastructure Security

IPv6 Infrastructure Security IPv6 Infrastructure Security 2013 North American IPv6 Summit Jeffrey L Carrell Network Conversions Network Security Consultant IPv6 SME/Trainer 1 Agenda IPv6 address fundamentals Operating Systems support

More information

Routing Protocols and Concepts Chapter 2 Conceitos de protocolos de Encaminhamento Cap 2

Routing Protocols and Concepts Chapter 2 Conceitos de protocolos de Encaminhamento Cap 2 Static Routing Routing Protocols and Concepts Chapter 2 1 1 Objectives Define the general role a router plays in networks. Describe the directly connected networks, different router interfaces Examine

More information

Understanding Virtual Router and Virtual Systems

Understanding Virtual Router and Virtual Systems Understanding Virtual Router and Virtual Systems PAN- OS 6.0 Humair Ali Professional Services Content Table of Contents VIRTUAL ROUTER... 5 CONNECTED... 8 STATIC ROUTING... 9 OSPF... 11 BGP... 17 IMPORT

More information

IPv6 Fundamentals, Design, and Deployment

IPv6 Fundamentals, Design, and Deployment IPv6 Fundamentals, Design, and Deployment Course IP6FD v3.0; 5 Days, Instructor-led Course Description The IPv6 Fundamentals, Design, and Deployment (IP6FD) v3.0 course is an instructor-led course that

More information

Cisco Site-to-Site VPN Lab 3 / GRE over IPSec VPNs by Michael T. Durham

Cisco Site-to-Site VPN Lab 3 / GRE over IPSec VPNs by Michael T. Durham Cisco Site-to-Site VPN Lab 3 / GRE over IPSec VPNs by Michael T. Durham In part two of NetCertLabs Cisco CCNA Security VPN lab series, we explored setting up a site-to-site VPN connection where one side

More information

Network Simulator Lab Study Plan

Network Simulator Lab Study Plan The CCNA 640-802 Network Simulator has 300 lab exercises, organized both by type (Skill Builder, Configuration Scenario, Troubleshooting Scenario, and Subnetting Exercise) and by major topic within each

More information

Introduction to Dynamic Routing Protocols

Introduction to Dynamic Routing Protocols CHAPTER 3 Introduction to Dynamic Routing Protocols Objectives Upon completion of this chapter, you should be able to answer the following questions: Can you describe the role of dynamic routing protocols

More information

Joe Davies. Principal Writer Windows Server Information Experience. Presented at: Seattle Windows Networking User Group June 1, 2011

Joe Davies. Principal Writer Windows Server Information Experience. Presented at: Seattle Windows Networking User Group June 1, 2011 Joe Davies Principal Writer Windows Server Information Experience Presented at: Seattle Windows Networking User Group June 1, 2011 2011 Microsoft Corporation IPv6 addressing and DNS review IPv6 subnetting

More information

CCNA Exploration 4.0: (II) Routing Protocols and Concepts. Chapter 1: Introduction to Routing and Packet Forwarding

CCNA Exploration 4.0: (II) Routing Protocols and Concepts. Chapter 1: Introduction to Routing and Packet Forwarding Http://elmaestrodelared.blogspot.com CCNA Exploration 4.0: (II) Routing Protocols and Concepts Chapter 1: Introduction to Routing and Packet Forwarding 1. If a router cannot find a valid configuration

More information

Equipment Configuration: Routers. 6DEPLOY. IPv6 Deployment and Support

Equipment Configuration: Routers. 6DEPLOY. IPv6 Deployment and Support Equipment Configuration: Routers 6DEPLOY. IPv6 Deployment and Support Routing Equipment Cisco Juniper 6WIND Hitachi Huawei FreeBSD Debian Windows Quagga 11th September 2008 Equipment Configuration: Routers

More information

Cisco Networking Academy CCNP Multilayer Switching

Cisco Networking Academy CCNP Multilayer Switching CCNP3 v5 - Chapter 5 Cisco Networking Academy CCNP Multilayer Switching Implementing High Availability in a Campus Environment Routing issues Hosts rely on a router to find the best path Issues with established

More information

Administrative Distance

Administrative Distance RIP is a distance vector routing protocol. It shares routing information through the local broadcast in every 30 seconds. In this tutorial we will explain RIP routing fundamentals with examples such as

More information

Networking. Palo Alto Networks. PAN-OS Administrator s Guide Version 6.0. Copyright 2007-2015 Palo Alto Networks

Networking. Palo Alto Networks. PAN-OS Administrator s Guide Version 6.0. Copyright 2007-2015 Palo Alto Networks Networking Palo Alto Networks PAN-OS Administrator s Guide Version 6.0 Contact Information Corporate Headquarters: Palo Alto Networks 4401 Great America Parkway Santa Clara, CA 95054 www.paloaltonetworks.com/company/contact-us

More information

IPv6 Addressing. Awareness Objective. IPv6 Address Format & Basic Rules. Understanding the IPv6 Address Components

IPv6 Addressing. Awareness Objective. IPv6 Address Format & Basic Rules. Understanding the IPv6 Address Components IPv6 Addressing Awareness Objective IPv6 Address Format & Basic Rules Understanding the IPv6 Address Components Understanding & Identifying Various Types of IPv6 Addresses 1 IPv4 Address SYNTAX W. X.

More information

Troubleshooting Load Balancing Over Parallel Links Using Cisco Express Forwarding

Troubleshooting Load Balancing Over Parallel Links Using Cisco Express Forwarding Page 1 of 16 Troubleshooting Load Balancing Over Parallel Links Using Cisco Express Forwarding Document ID: 18285 Contents Introduction Prerequisites Requirements Components Used Conventions Background

More information

EIGRP Commands. Cisco IOS IP Command Reference, Volume 2 of 3: Routing Protocols IP2R-141

EIGRP Commands. Cisco IOS IP Command Reference, Volume 2 of 3: Routing Protocols IP2R-141 EIGRP Commands Use the commands in this chapter to configure and monitor Enhanced Interior Gateway Routing Protocol (EIGRP). For EIGRP configuration information and examples, refer to the Configuring IP

More information

Network layer: Overview. Network layer functions IP Routing and forwarding

Network layer: Overview. Network layer functions IP Routing and forwarding Network layer: Overview Network layer functions IP Routing and forwarding 1 Network layer functions Transport packet from sending to receiving hosts Network layer protocols in every host, router application

More information

Migration from Cisco GLBP to industry standard VRRPE

Migration from Cisco GLBP to industry standard VRRPE Migration from Cisco GLBP to industry standard VRRPE Technical white paper Table of contents Overview... 2 Gateway load balancing protocols... 2 Introduction to Cisco GLBP... 2 Introduction to VRRPE...

More information

Chapter 2 Lab 2-2, Configuring EtherChannel Instructor Version

Chapter 2 Lab 2-2, Configuring EtherChannel Instructor Version Chapter 2 Lab 2-2, Configuring EtherChannel Instructor Version Topology Objective Background Configure EtherChannel. Four switches have just been installed. The distribution layer switches are Catalyst

More information

Laboratorio 3 Comunicación sincrónica Vía Satélite

Laboratorio 3 Comunicación sincrónica Vía Satélite Laboratorio 3 Comunicación sincrónica Vía Satélite Esquema de la Red WAN 192.168.0.0 /30 192.168.0.1 Router 1 Router 2 10.0.1.1 192.168.0.1 10.0.2.1 Ethernet Ethernet 10.0.1.20 LAN 1 10.0.1.0 /24 LAN 2

More information

Module 12 Multihoming to the Same ISP

Module 12 Multihoming to the Same ISP Module 12 Multihoming to the Same ISP Objective: To investigate various methods for multihoming onto the same upstream s backbone Prerequisites: Module 11 and Multihoming Presentation The following will

More information

Distance Vector Routing Protocols. Routing Protocols and Concepts Ola Lundh

Distance Vector Routing Protocols. Routing Protocols and Concepts Ola Lundh Distance Vector Routing Protocols Routing Protocols and Concepts Ola Lundh Objectives The characteristics of distance vector routing protocols. The network discovery process of distance vector routing

More information

GregSowell.com. Mikrotik Routing

GregSowell.com. Mikrotik Routing Mikrotik Routing Static Dynamic Routing To Be Discussed RIP Quick Discussion OSPF BGP What is Routing Wikipedia has a very lengthy explanation http://en.wikipedia.org/wiki/routing In the context of this

More information

Interconnecting Cisco Network Devices 1 Course, Class Outline

Interconnecting Cisco Network Devices 1 Course, Class Outline www.etidaho.com (208) 327-0768 Interconnecting Cisco Network Devices 1 Course, Class Outline 5 Days Interconnecting Cisco Networking Devices, Part 1 (ICND1) v2.0 is a five-day, instructorled training course

More information

Troubleshooting Tools

Troubleshooting Tools Troubleshooting Tools An overview of the main tools for verifying network operation from a host Fulvio Risso Mario Baldi Politecnico di Torino (Technical University of Turin) see page 2 Notes n The commands/programs

More information

Introduction to Routing and Packet Forwarding. Routing Protocols and Concepts Chapter 1

Introduction to Routing and Packet Forwarding. Routing Protocols and Concepts Chapter 1 Introduction to Routing and Packet Forwarding Routing Protocols and Concepts Chapter 1 1 1 Objectives Identify a router as a computer with an OS and hardware designed for the routing process. Demonstrate

More information

Cisco CCNP 642 901 Optimizing Converged Cisco Networks (ONT)

Cisco CCNP 642 901 Optimizing Converged Cisco Networks (ONT) Cisco CCNP 642 901 Optimizing Converged Cisco Networks (ONT) Course Number: 642 901 Length: 5 Day(s) Certification Exam This course will help you prepare for the following exams: Cisco CCNP Exam 642 901:

More information

MPLS VPN over mgre. Finding Feature Information. Prerequisites for MPLS VPN over mgre

MPLS VPN over mgre. Finding Feature Information. Prerequisites for MPLS VPN over mgre The feature overcomes the requirement that a carrier support multiprotocol label switching (MPLS) by allowing you to provide MPLS connectivity between networks that are connected by IP-only networks. This

More information

Configuring Enhanced Object Tracking

Configuring Enhanced Object Tracking Configuring Enhanced Object Tracking First Published: May 2, 2005 Last Updated: July 1, 2009 Before the introduction of the Enhanced Object Tracking feature, the Hot Standby Router Protocol (HSRP) had

More information