ipv6 hands on lab hritter kho tài liệu bách khoa

Toronto, Canada May 30, 2013 IPv6 Hands-on Lab Faraz Shamim, Technical Leader Harold Ritter, Technical Leader © 2012 2011 Cisco and/or its affiliates All rights reserved Cisco Connect Prerequisites: Session Abstract This IPv6 basic and advanced lab will provide you an opportunity to configure, troubleshoot, design and implement IPv6 network using IPv6 technologies and features such as; IPv6 addressing, IPv6 neighbor discovery, HSRPv6, static routing, OSPFv3, EIGRPv6 and BGPv6 You will be provided with a scenario made up with an IPv4 network where you will get the opportunity to configure and implement IPv6 based on the requirements and needs on the network For e.g where would you deploy dual stack, where it make sense to tunneling and how to deploy an IPv6 routing protocols without impacting your existing Network infrastructure  Students MUST have a basic understanding of IPv6 Addressing and Routing Protocols  Familiarity with Cisco IOS Agenda  Lab1 : IPv6 Addressing & Stateless Address Auto Configuration (SLAAC)  Lab2 : IPv6 Neighbor Discovery  Lab3 : IPv6 Static Routing  Lab4 : HSRPv6  Lab5 : EIGRPv6  Lab6 : Manual Tunnels (IPv6oIPv4 & GRE)  Lab7 : OSPFv3  Lab8 : BGPv6  Optional Labs(6PE, 6VPE & IPv6 Multicasting) Lab Synopsis  You are a network engineer at ABC Inc You just attended a cool lab session on IPv6 at Cisco Connect in Toronto and you are extremely enthusiastic about deploying IPv6 in your network  Since this is your first time with IPv6, you want to experiment things at your own before talking to your ISP about IPv6 connectivity Your goal is to make your own network IPv6 ready before talking to your ISP about IPv6  You are challenged with multiple task during this exercise Each task will be called a Lab  One thing you learned in the lab session on IPv6 at Cisco Connect Toronto is to go with dual stack as much as possible In the event you can not use dual stack you will use tunneling techniques  IPv4 piece is already up and running in the network and nothing needs to be done on IPv4 side  R1 is connected to IPv6 Internet For this purpose we have assigned a loopback with an ipv6 address of 2004:db8::1/128 So if any router can ping this address, it means it can access IPv6 internet Lab Topology Lab : IPv6 Addressing & Stateless Address Auto Configuration (SLAAC) © 2012 Cisco and/or its affiliates All rights reserved Cisco Connect Lab IPv6 Unique Local Address  The first thing you would like to 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 is the simplest site so you want to pick that site first  Site 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 not run into any issues in Site before you move on with site  Since this is your first site, you are using a private address FD01:DB8::/32 for this purpose Lab IPv6 Stateless Auto-Configuration (SLAAC)  Your plan is to test the plug and play behaviour of IPv6 So you only assigned the IPv6 unique local address on R4 interface facing H1 and see if you get an IPv6 address assigned automatically on H1 from R4 (Refer to Slide 39 for IPv6 addressing example)  You want to see how EUI-64 method works so you are using that on R4 during the address assignment with /64 mask  Assign this unique local address on R4 using subnetting as shown in the next slide  Ping R4’s link local and Unique local IPv6 address from H1 Lab 1: IPv6 Addressing & SLAAC Lab 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 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 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 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: R3#sh ipv6 mroute FF7E:130:2001:DB8:1::99 (*, FF7E:130:2001:DB8:1::99), 00:09:35/never, RP 2001:DB8:1::1, flags: SCJ Incoming interface: Serial2/0 RPF nbr: FE80::A8BB:CCFF:FE00:5100 Immediate Outgoing interface list: Ethernet0/0, Forward, 00:09:35/never R3# Multicast Lab: IPv6 Multicast with Embedded RP  Verify that R1 (RP) has received the join coming from R3  Verify that the PIM join has been received by the RP (R2)  Why 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# 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# 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 preceding 0x30 represents the last bits of the RP address 0x30 (48 in decimal) is the actual length we use to retrieve the RP address  As stated in RFC4601, Cisco IOS uses a tunnel interface for the PIM register process On the RP, this tunnel interface is used as the incoming interface for (*,G) entries, as encapsulated multicast packets will be received on that interface IPv6 Multicast Lab Key Lab Key © 2012 Cisco and/or its affiliates All rights reserved Cisco Connect 173 Multicast Lab: Configs R# Configs R1 ipv6 unicast-routing ipv6 cef ipv6 multicast-routing ! interface Loopback0 ipv6 address 2001:DB8:1::1/128 ipv6 ospf area ! interface Ethernet0/0 ipv6 address 2001:DB8:1:1::1/64 ipv6 ospf area ! interface Serial1/0 ipv6 address 2001:DB8:1::3/127 ipv6 ospf area ! interface Serial2/0 ipv6 address 2001:DB8::3/64 ipv6 ospf area ! ! 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 Multicast Lab: Configs R# R2 Configs ipv6 unicast-routing ipv6 cef ipv6 multicast-routing ! interface Loopback0 ipv6 address 2001:DB8:1::/128 ipv6 ospf area ! interface Ethernet0/0 ipv6 address 2001:DB8:1::4/127 ipv6 ospf area ! interface Serial1/0 ipv6 address 2001:DB8:1::2/127 ipv6 ospf area ! ipv6 pim rp-address 2001:DB8:1:: ipv6 router ospf 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 area ! interface Ethernet0/0 ipv6 address 2001:DB8:1:2::3/64 ipv6 ospf area ! interface Ethernet1/0 ipv6 address 2001:DB8:1::5/127 ipv6 ospf area ! interface Serial2/0 ipv6 address 2001:DB8::5/64 ipv6 ospf area ! ipv6 pim rp-address 2001:DB8:1:: ipv6 router ospf 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 ! “For larger statements and quotes, use this slide layout to format the long references in all of your presentations.” Source Name Placement © 2012 2011 Cisco and/or its affiliates All rights reserved Cisco Cisco Confidential Connect 178 Complete Your Paper “Session Evaluation” Give us your feedback and you could win of fabulous prizes in a random draw Complete and return your paper evaluation form to the room attendant as you leave this session Winners will be announced today You must be present to win! visit them at BOOTH# 100 Thank you © 2012 Cisco and/or its affiliates All rights reserved Cisco Connect 180 ... 30 seconds on R4  You disable the autoconfigs on H1 E0/0 interface and turn on the ipv6 nd debugs and enable autoconfigs again to see the RA/RS  Turn on debug ipv6 nd on R4 and H1 Lab IPv6 Neighbor... discovery: Configs R# Configs R4 R4(config)#interface e0/0 R4(config-if) #ipv6 nd interval 30 R4(config-if)#end H1 H1(config)#interface e0/0 H1(config-if)#no ipv6 address autoconfig H1(config-if)#no ipv6. .. H1(config-if) #ipv6 enable H1(config-if) #ipv6 address autoconfig H1(config-if)#end Lab IPv6 Neighbor discovery: Verification R4 R4#sh ipv6 int e0/0 Ethernet0/0 is up, line protocol is up IPv6