Faraz Shamim, Technical Leader and Harold Ritter, Technical Leader discussed hands-on experience with IPv6 Routing and Services at Cisco Connect Toronto.
Hands on Experience with IPv6 Routing and Switching ServicesCisco Canada
This lab provides hands-on experience with configuring and implementing IPv6 networking using various IPv6 technologies and features. Students will be given a scenario with an existing IPv4 network and will deploy IPv6 according to requirements, determining where to use dual stack, tunneling, and IPv6 routing protocols without impacting the existing IPv4 infrastructure. The lab covers topics like IPv6 addressing, neighbor discovery, static routing, OSPFv3, EIGRPv6, BGPv6, and more.
The “Hands on Experience with IPv6 Routing and Services” Techtorial will provide attendees an opportunity to configure, troubleshoot, design and implement an IPv6 network using IPv6 technologies and features such as: IPv6 addressing, IPv6 neighbor discovery, HSRPv6, static routing, OSPFv3, EIGRPv6 and BGPv6. You will be provided with a scenario made up of an IPv4 network where you will get the opportunity to configure and implement IPv6 based on the requirements on the network, i.e., where would you deploy dual stack, where it make sense to do funneling and how to deploy IPv6 routing protocols without impacting your existing Network infrastructure.
How to set up an IPv6 LAN with Linux. Using IPv6 requires two steps, firstly setting up the local LAN to support IPv6 and secondly connecting to the internet. The exact mechanism to connect to the Internet depends on your ISP. If you have an IPv4 address of IPv6 and whether you trying to access an IPv4 or IPv6 host.
Jumping Bean offers IPv6 training for businesses (http://www.jumpingbean.co.za/ipv6-training)
IPv6 Autoconfig full process from initial configuration of IPV6 Node. Refreshment of IPv6 Addresses using RA or DHCPv6. How to keep your home config everywhere you go and only logout when you want to, not when you move to a new access point.
Overview of RARP, BOOTP, DHCP and PXE protocols for dynamic IP address assignment.
Dynamic IP address assignment to a host (or interface) is a common problem in TCP/IP based networks.
Manual and static assignment of IP addresses does not scale well and becomes a labor intensive task with a growing number of hosts.
An early approach for dynamic IP address assignment was RARP (Reverse ARP) which ran directly on the Ethernet protocol layer.
The many problems of RARP such as the inability to be routed between subnets were solved with BOOTP (Bootstrap Protocol).
BOOTP, however, ended to have its own set of limitations like lack of a lease time for IP addresses.
DHCP (Dynamic Host Configuration Protocol) was therefore defined as an extension to BOOTP.
DHCP is backward compatible with BOOTP thus allowing some degree of interoperability between the 2 protocols.
The state-of-the-art protocol for dynamic IP address assignment is, however, is DHCP.
DHCPv6 is an adaption of DHCP for IPv6 based networks.
Cisco CCNA Training/Exam Tips that are helpful for your Certification Exam!
To be Cisco Certified please Check out:
http://asmed.com/information-technology-it/
CodiLime Tech Talk - Adam Kułagowski: IPv6 - introductionCodiLime
IPv6 was created to address the limited address space of IPv4 as global IPv4 address allocation was running out. Some of the key differences between IPv4 and IPv6 include IPv6's significantly larger 128-bit address space compared to IPv4's 32-bit addresses, as well as changes to areas like packet headers, fragmentation, and neighbor discovery. Transition technologies like dual stack, NAT64, and DS-Lite were developed to help transition from IPv4 to IPv6, while ensuring IPv6 connectivity even for networks and devices that still use IPv4. Fully enabling IPv6 requires changes to network infrastructure like firewalls, routers, and switches to support the new protocol.
How to configure static nat on cisco routersIT Tech
This document provides instructions for configuring static network address translation (NAT) on a Cisco router to map a private IP address to a public IP address. It explains that NAT allows private IP addresses on an internal network to be represented by public IP addresses on the external network. It then outlines the steps to configure static NAT on a Cisco router by defining the inside and outside interfaces, and using commands like "ip nat inside" and "ip nat outside" to identify the interfaces and "ip nat inside source static" to define the address mapping. It verifies the NAT configuration is working properly using show commands.
Hands on Experience with IPv6 Routing and Switching ServicesCisco Canada
This lab provides hands-on experience with configuring and implementing IPv6 networking using various IPv6 technologies and features. Students will be given a scenario with an existing IPv4 network and will deploy IPv6 according to requirements, determining where to use dual stack, tunneling, and IPv6 routing protocols without impacting the existing IPv4 infrastructure. The lab covers topics like IPv6 addressing, neighbor discovery, static routing, OSPFv3, EIGRPv6, BGPv6, and more.
The “Hands on Experience with IPv6 Routing and Services” Techtorial will provide attendees an opportunity to configure, troubleshoot, design and implement an IPv6 network using IPv6 technologies and features such as: IPv6 addressing, IPv6 neighbor discovery, HSRPv6, static routing, OSPFv3, EIGRPv6 and BGPv6. You will be provided with a scenario made up of an IPv4 network where you will get the opportunity to configure and implement IPv6 based on the requirements on the network, i.e., where would you deploy dual stack, where it make sense to do funneling and how to deploy IPv6 routing protocols without impacting your existing Network infrastructure.
How to set up an IPv6 LAN with Linux. Using IPv6 requires two steps, firstly setting up the local LAN to support IPv6 and secondly connecting to the internet. The exact mechanism to connect to the Internet depends on your ISP. If you have an IPv4 address of IPv6 and whether you trying to access an IPv4 or IPv6 host.
Jumping Bean offers IPv6 training for businesses (http://www.jumpingbean.co.za/ipv6-training)
IPv6 Autoconfig full process from initial configuration of IPV6 Node. Refreshment of IPv6 Addresses using RA or DHCPv6. How to keep your home config everywhere you go and only logout when you want to, not when you move to a new access point.
Overview of RARP, BOOTP, DHCP and PXE protocols for dynamic IP address assignment.
Dynamic IP address assignment to a host (or interface) is a common problem in TCP/IP based networks.
Manual and static assignment of IP addresses does not scale well and becomes a labor intensive task with a growing number of hosts.
An early approach for dynamic IP address assignment was RARP (Reverse ARP) which ran directly on the Ethernet protocol layer.
The many problems of RARP such as the inability to be routed between subnets were solved with BOOTP (Bootstrap Protocol).
BOOTP, however, ended to have its own set of limitations like lack of a lease time for IP addresses.
DHCP (Dynamic Host Configuration Protocol) was therefore defined as an extension to BOOTP.
DHCP is backward compatible with BOOTP thus allowing some degree of interoperability between the 2 protocols.
The state-of-the-art protocol for dynamic IP address assignment is, however, is DHCP.
DHCPv6 is an adaption of DHCP for IPv6 based networks.
Cisco CCNA Training/Exam Tips that are helpful for your Certification Exam!
To be Cisco Certified please Check out:
http://asmed.com/information-technology-it/
CodiLime Tech Talk - Adam Kułagowski: IPv6 - introductionCodiLime
IPv6 was created to address the limited address space of IPv4 as global IPv4 address allocation was running out. Some of the key differences between IPv4 and IPv6 include IPv6's significantly larger 128-bit address space compared to IPv4's 32-bit addresses, as well as changes to areas like packet headers, fragmentation, and neighbor discovery. Transition technologies like dual stack, NAT64, and DS-Lite were developed to help transition from IPv4 to IPv6, while ensuring IPv6 connectivity even for networks and devices that still use IPv4. Fully enabling IPv6 requires changes to network infrastructure like firewalls, routers, and switches to support the new protocol.
How to configure static nat on cisco routersIT Tech
This document provides instructions for configuring static network address translation (NAT) on a Cisco router to map a private IP address to a public IP address. It explains that NAT allows private IP addresses on an internal network to be represented by public IP addresses on the external network. It then outlines the steps to configure static NAT on a Cisco router by defining the inside and outside interfaces, and using commands like "ip nat inside" and "ip nat outside" to identify the interfaces and "ip nat inside source static" to define the address mapping. It verifies the NAT configuration is working properly using show commands.
The document discusses IPv6 and the transition from IPv4 to IPv6. It provides details about:
- The author who manages the IIT Kanpur campus network and internet services.
- Reasons for adopting IPv6 like shortage of IPv4 addresses and new features in IPv6.
- Elements of IPv6 including the 128-bit address format, address types and scopes, stateless and stateful address autoconfiguration, routing, and neighbor discovery.
- Transition mechanisms from IPv4 to IPv6 like dual stack, tunnels, and translation.
- Current status of IPv6 deployment and recommended steps for migration including checking IPv6 compliance and planning IPv6 addressing.
This document summarizes network address translation (NAT). It defines key NAT terminology like inside/outside addresses and translations. It provides examples of static and dynamic NAT configuration using access lists, pools, and overload. It also covers port address translation, troubleshooting, and tuning NAT translations.
Network address translation (NAT) allows remapping of one IP address space to another. Types of NAT include static NAT, dynamic NAT, and port address translation (PAT). NAT provides benefits like IP address conservation, security, and flexibility. On Cisco routers, NAT operations follow an order of inside-to-outside and outside-to-inside translation. NAT can be deployed in scenarios involving MPLS VPNs, IP multicast, high availability, and application-level gateways. Configuration of NAT varies between Cisco routers and ASA firewalls.
This document summarizes several technology updates related to IPv6 that are being discussed and standardized within the IETF. It covers issues and proposals regarding core IPv6 protocols like site-local addressing and prefix delegation. It also discusses routing protocol issues, DNS considerations, transition mechanisms, neighbor discovery security, and the IPv6 firewall architecture. The document provides an overview of the status and remaining issues for each topic.
This document provides an overview of IPv6 provisioning and interface startup. It discusses stateless address autoconfiguration, router advertisements, DHCPv6, and the steps an interface takes at startup to acquire a link-local address and check for router advertisements. These include generating an interface identifier to build a link-local address, performing duplicate address detection, soliciting router advertisements, checking for address prefixes, and determining if DHCPv6 needs to be called. Diagrams illustrate concepts like DHCPv6 client-server communication, identity associations, and address states.
This document provides an overview of Network Address Translation (NAT) including:
- Why NAT is used to connect networks with private IP addresses to the Internet and during network mergers.
- NAT implementation considerations such as advantages of address conservation and flexibility but disadvantages of delays and incompatible applications.
- Common NAT configurations like dynamic NAT, dynamic NAT with overloading, and static NAT.
This document describes network address translation (NAT) and different NAT types. It includes a course on Cisco CCNA about NAT taught at Tehran Institute of Technology. The course covers introduction to NAT and private vs public addresses. It then describes static NAT, dynamic NAT, and port address translation. The document provides examples of configuring static and dynamic NAT on routers to allow internal hosts to access the internet using public IP addresses.
This document discusses Network Address Translation (NAT) and Port Address Translation (PAT). It defines key NAT terms and private IP address ranges. It then describes the main features of NAT and PAT, including static and dynamic NAT mappings and how PAT uses port numbers to map multiple private IPs to a single public IP. The document provides examples for configuring static NAT, dynamic NAT, and PAT. It also discusses troubleshooting NAT and changing dynamic NAT configurations.
Cisco CCNA/CCNP Training/Exam Tips that are helpful for your Certification Exam!
To be Cisco Certified please Check out:
http://asmed.com/information-technology-it/
This document provides an overview of IPv6 including its history, addressing formats, integration strategies with IPv4, application development considerations, and troubleshooting tips. IPv6 was developed to address the limited address space of IPv4 and enable new features. It uses a 128-bit address space compared to 32-bits in IPv4. Popular transition technologies like dual-stack, 6to4 tunnels, and Teredo tunnels are discussed for integrating IPv6 into existing IPv4 networks. Application developers need to support both address families using new socket functions and data structures.
Cisco CCNA/CCNP Training/Exam Tips that are helpful for your Certification Exam!
To be Cisco Certified please Check out:
http://asmed.com/information-technology-it/
Cisco CCNA Training/Exam Tips that are helpful for your Certification Exam!
To be Cisco Certified please Check out:
http://asmed.com/information-technology-it/
This document discusses various techniques for transitioning from IPv4 to IPv6 and enabling their coexistence, grouped into three categories: dual stack, tunnels, and translation. Dual stack allows simultaneous support of IPv4 and IPv6, while tunnels encapsulate IPv6 packets in IPv4 and translation converts between the two protocols. Common tunneling methods include 6in4, 6to4, Teredo and Softwires. Translation via NAT-PT is discouraged due to imperfections requiring ALG support. CGNAT/NAT444 allows sharing IPv4 addresses but breaks many applications. Fully deploying IPv6 is preferable to work around IPv4 exhaustion issues.
This document discusses strategies for deploying IPv6 in cellular networks given the impending exhaustion of IPv4 addresses and increasing number of internet-connected devices. The best long-term solution is dual-stack (IPv4 and IPv6), but alternatives like IPv6-only with NAT64 and 464XLAT can work as well by allowing IPv6-only devices to access IPv4 content. NAT64 and DNS64 enable IPv6-only clients to reach IPv4 servers, while 464XLAT provides a more efficient solution that works for applications using literal IPv4 addresses. Large-scale deployments by mobile carriers demonstrate the viability of IPv6-only networks with NAT64 or 464XLAT.
The document discusses IPv6 over MPLS on Cisco routers, including:
- 6PE allows IPv6 connectivity over an IPv4/MPLS backbone by using MPLS labels between PE routers to tunnel IPv6 packets. Configuration on Cisco routers is straightforward, requiring IPv6 BGP neighbor configuration and the "neighbor send-label" command.
- 6VPE extends the concept of VPNs to IPv6 using scoped addressing architecture. It allows dual-stacked VRFs for consistent IPv4 and IPv6 VPN services. Configuration requires defining VRFs and associating interfaces using "vrf forwarding".
The document provides configuration examples for IPv6 routing on Cisco, Juniper, FreeBSD, and RedHat routers and hosts. It includes configurations for interfaces, routing protocols like BGP and RIPng, router advertisements, and show commands.
Creating a Collaborative Workplace Culture Webinar SeriesCisco Canada
To increase innovation and productivity, organizations recognize that they have to get better at creating more “collaborative cultures” to leverage the collective knowledge, expertise and experience from within. View the slides from Part 1 of the series: Is it time for a Chief Collaboration Officer? Listen to the recording today: http://bit.ly/1L1SFow
Managing Unprecedented Change with Business TransformationCisco Canada
This presentation will discuss how to manage change with business transformation, including: the shifting landscape, business imperatives and technology transformations, as well as, IT implications.
The document discusses IPv6 and the transition from IPv4 to IPv6. It provides details about:
- The author who manages the IIT Kanpur campus network and internet services.
- Reasons for adopting IPv6 like shortage of IPv4 addresses and new features in IPv6.
- Elements of IPv6 including the 128-bit address format, address types and scopes, stateless and stateful address autoconfiguration, routing, and neighbor discovery.
- Transition mechanisms from IPv4 to IPv6 like dual stack, tunnels, and translation.
- Current status of IPv6 deployment and recommended steps for migration including checking IPv6 compliance and planning IPv6 addressing.
This document summarizes network address translation (NAT). It defines key NAT terminology like inside/outside addresses and translations. It provides examples of static and dynamic NAT configuration using access lists, pools, and overload. It also covers port address translation, troubleshooting, and tuning NAT translations.
Network address translation (NAT) allows remapping of one IP address space to another. Types of NAT include static NAT, dynamic NAT, and port address translation (PAT). NAT provides benefits like IP address conservation, security, and flexibility. On Cisco routers, NAT operations follow an order of inside-to-outside and outside-to-inside translation. NAT can be deployed in scenarios involving MPLS VPNs, IP multicast, high availability, and application-level gateways. Configuration of NAT varies between Cisco routers and ASA firewalls.
This document summarizes several technology updates related to IPv6 that are being discussed and standardized within the IETF. It covers issues and proposals regarding core IPv6 protocols like site-local addressing and prefix delegation. It also discusses routing protocol issues, DNS considerations, transition mechanisms, neighbor discovery security, and the IPv6 firewall architecture. The document provides an overview of the status and remaining issues for each topic.
This document provides an overview of IPv6 provisioning and interface startup. It discusses stateless address autoconfiguration, router advertisements, DHCPv6, and the steps an interface takes at startup to acquire a link-local address and check for router advertisements. These include generating an interface identifier to build a link-local address, performing duplicate address detection, soliciting router advertisements, checking for address prefixes, and determining if DHCPv6 needs to be called. Diagrams illustrate concepts like DHCPv6 client-server communication, identity associations, and address states.
This document provides an overview of Network Address Translation (NAT) including:
- Why NAT is used to connect networks with private IP addresses to the Internet and during network mergers.
- NAT implementation considerations such as advantages of address conservation and flexibility but disadvantages of delays and incompatible applications.
- Common NAT configurations like dynamic NAT, dynamic NAT with overloading, and static NAT.
This document describes network address translation (NAT) and different NAT types. It includes a course on Cisco CCNA about NAT taught at Tehran Institute of Technology. The course covers introduction to NAT and private vs public addresses. It then describes static NAT, dynamic NAT, and port address translation. The document provides examples of configuring static and dynamic NAT on routers to allow internal hosts to access the internet using public IP addresses.
This document discusses Network Address Translation (NAT) and Port Address Translation (PAT). It defines key NAT terms and private IP address ranges. It then describes the main features of NAT and PAT, including static and dynamic NAT mappings and how PAT uses port numbers to map multiple private IPs to a single public IP. The document provides examples for configuring static NAT, dynamic NAT, and PAT. It also discusses troubleshooting NAT and changing dynamic NAT configurations.
Cisco CCNA/CCNP Training/Exam Tips that are helpful for your Certification Exam!
To be Cisco Certified please Check out:
http://asmed.com/information-technology-it/
This document provides an overview of IPv6 including its history, addressing formats, integration strategies with IPv4, application development considerations, and troubleshooting tips. IPv6 was developed to address the limited address space of IPv4 and enable new features. It uses a 128-bit address space compared to 32-bits in IPv4. Popular transition technologies like dual-stack, 6to4 tunnels, and Teredo tunnels are discussed for integrating IPv6 into existing IPv4 networks. Application developers need to support both address families using new socket functions and data structures.
Cisco CCNA/CCNP Training/Exam Tips that are helpful for your Certification Exam!
To be Cisco Certified please Check out:
http://asmed.com/information-technology-it/
Cisco CCNA Training/Exam Tips that are helpful for your Certification Exam!
To be Cisco Certified please Check out:
http://asmed.com/information-technology-it/
This document discusses various techniques for transitioning from IPv4 to IPv6 and enabling their coexistence, grouped into three categories: dual stack, tunnels, and translation. Dual stack allows simultaneous support of IPv4 and IPv6, while tunnels encapsulate IPv6 packets in IPv4 and translation converts between the two protocols. Common tunneling methods include 6in4, 6to4, Teredo and Softwires. Translation via NAT-PT is discouraged due to imperfections requiring ALG support. CGNAT/NAT444 allows sharing IPv4 addresses but breaks many applications. Fully deploying IPv6 is preferable to work around IPv4 exhaustion issues.
This document discusses strategies for deploying IPv6 in cellular networks given the impending exhaustion of IPv4 addresses and increasing number of internet-connected devices. The best long-term solution is dual-stack (IPv4 and IPv6), but alternatives like IPv6-only with NAT64 and 464XLAT can work as well by allowing IPv6-only devices to access IPv4 content. NAT64 and DNS64 enable IPv6-only clients to reach IPv4 servers, while 464XLAT provides a more efficient solution that works for applications using literal IPv4 addresses. Large-scale deployments by mobile carriers demonstrate the viability of IPv6-only networks with NAT64 or 464XLAT.
The document discusses IPv6 over MPLS on Cisco routers, including:
- 6PE allows IPv6 connectivity over an IPv4/MPLS backbone by using MPLS labels between PE routers to tunnel IPv6 packets. Configuration on Cisco routers is straightforward, requiring IPv6 BGP neighbor configuration and the "neighbor send-label" command.
- 6VPE extends the concept of VPNs to IPv6 using scoped addressing architecture. It allows dual-stacked VRFs for consistent IPv4 and IPv6 VPN services. Configuration requires defining VRFs and associating interfaces using "vrf forwarding".
The document provides configuration examples for IPv6 routing on Cisco, Juniper, FreeBSD, and RedHat routers and hosts. It includes configurations for interfaces, routing protocols like BGP and RIPng, router advertisements, and show commands.
Creating a Collaborative Workplace Culture Webinar SeriesCisco Canada
To increase innovation and productivity, organizations recognize that they have to get better at creating more “collaborative cultures” to leverage the collective knowledge, expertise and experience from within. View the slides from Part 1 of the series: Is it time for a Chief Collaboration Officer? Listen to the recording today: http://bit.ly/1L1SFow
Managing Unprecedented Change with Business TransformationCisco Canada
This presentation will discuss how to manage change with business transformation, including: the shifting landscape, business imperatives and technology transformations, as well as, IT implications.
This presentation will discuss cloud computing at Cisco Canada, including an overview of Cloud Computing, Cisco’s cloud strategy, the unified Data Center, Cisco Solution, Cloud Case study, and advances in technology and platforms.
Cisco ONE Enterprise Cloud (UCSD) Hands-on LabCisco Canada
Pre-Requisites: As this is a hands-on lab, students should bring their laptop to take full advantage of the labs throughout the day sessions.
Learn how to configure network, compute, storage and virtualization components then use UCS Director to orchestrate, provision, automate and manage the solution.
IT transformation is a long journey that requires a close, sustained collaboration across the IT organization. For IT organizations that are transitioning to a private cloud architecture, the measure of success isn’t whether they’ve implemented an IT architecture that “works better”—it’s whether IT makes the business work better. By simplifying the design, build, and operational processes for private and hybrid clouds, Cisco ONE Enterprise Cloud Suite (ECS) helps you focus your time and energy on ensuring that your platform remains closely aligned with business requirements.
Labs
• UCS Director Concepts (vDC, Pod, etc.)
• Managing Physical Resources,
• Managing Virtual Infrastructure,
• UCS Director Extensibility
Hands-on Experience with IPv6 Routing and ServicesCisco Canada
This document provides an agenda and overview for a hands-on lab session on IPv6 routing and services. The lab session will consist of 8 exercises that provide experience with IPv6 addressing, neighbor discovery, static routing, HSRP, EIGRPv6, tunnels, OSPFv3, and BGPv6. The first lab focuses on configuring IPv6 addressing and stateless address autoconfiguration on routers and hosts in a simple site using unique local addresses. Subsequent labs introduce global unicast addressing across multiple sites and additional labs cover various IPv6 routing protocols.
1. The host will automatically generate a link-local address starting with fe80::.
2. It will perform duplicate address detection to ensure the address is unique on the local link.
3. If the address is unique, it is assigned to the interface.
4. The host will send a router solicitation to discover network prefixes advertised by routers.
5. Upon receiving a router advertisement with network prefixes, the host will autoconfigure an IPv6 address by combining the prefix with its interface ID.
This document provides information about IPv6 addressing and describes a lab exercise to help identify different types of IPv6 addresses. The lab has three parts: 1) Identify types of IPv6 addresses based on address prefixes, 2) Examine a host's IPv6 network settings to find its link-local address, 3) Practice abbreviating IPv6 addresses using defined rules. Key points covered include the structure of IPv6 addresses, common address types like link-local and global unicast, and how to compress addresses using techniques like omitting leading zeros and replacing runs of zeros with "::".
IPv6 addresses are 128 bits long, providing more than 3.4 x 10^38 unique addresses, with addresses written in groups of 4 hexadecimal characters. IPv6 headers include a Flow Label field that can prioritize packets sent from a particular source to a specific unicast, anycast, or multicast destination. IPv6 supports various address types including link-local for layer 2, unique/site-local for an organization, and global for internet communication.
This chapter discusses IPv6, the next-generation Internet protocol. IPv6 was created to address the impending exhaustion of IPv4 addresses as the number of internet-connected devices grows rapidly. IPv6 uses 128-bit addresses compared to 32-bit addresses in IPv4. It supports various address types including unicast, multicast, and anycast. IPv6 also introduces mechanisms for address autoconfiguration and supports tunneling techniques for transitioning to IPv6, such as 6to4 tunnels.
This chapter discusses IPv6, the next-generation Internet protocol. IPv6 was created to address the impending exhaustion of IPv4 addresses as the number of internet-connected devices grows rapidly. IPv6 uses 128-bit addresses compared to 32-bit addresses in IPv4. It supports various address types including unicast, multicast, and anycast. IPv6 also introduces mechanisms for address autoconfiguration and tunneling to support transition from IPv4 to IPv6.
This document describes a group project to build a NAT64 server that connects IPv4 clients to IPv6 servers and vice versa. The project involves implementing IPv4 to IPv6 and IPv6 to IPv4 conversion algorithms and combining them into a NAT64 module. Key steps include implementing a tri-mode Ethernet MAC wrapper, mapping IPv4 and IPv6 header fields, and using a static NAT table to map IPv4 and IPv6 addresses. The project was developed on a Virtex-5 FPGA board and debugged using ChipScope Pro and Wireshark due to limitations of available simulators.
The document discusses various topics related to IPv6 addressing and configuration. It includes questions about:
- How IPv6 global unicast addresses are assigned (RIRs assign blocks to ISPs)
- Valid abbreviation of an IPv6 address using double colons
- Identifying multicast vs unicast IPv6 addresses
- Methods for hosts to dynamically learn IPv6 addresses (stateless autoconfiguration, NDP)
- IPv6 routing protocols (RIPng, OSPFv3)
- Forming the link-local address based on MAC address
- Configuring RIPng on an interface
- IPv4-IPv6 transition methods (NAT-PT)
The questions cover a wide
basic standard acl-lab
set pcname pc1
ip 192.168.1.2/24 192.168.1.1
set pcname pc2
ip 192.168.1.3/24 192.168.1.1
set pcname pc3
ip 10.10.10.2/24 10.10.10.1
set pcname pc4
ip 10.10.20.2/24 10.10.20.1
hostname sw1
---------------------------------------
r1
---------------------------------------
hostname r1
interface e0/1
ip address 192.168.1.1 255.255.255.0
no shutdown
exit
interface e0/0
ip address 172.16.1.1 255.255.255.0
no shutdown
exit
router ospf 1
network 192.168.1.0 0.0.0.255 area 0
network 172.16.1.0 0.0.0.255 area 0
exit
---------------------------------------
r2
---------------------------------------
hostname r2
interface e0/1
ip address 10.10.10.1 255.255.255.0
no shutdown
exit
interface e0/2
ip address 10.10.20.1 255.255.255.0
no shutdown
exit
interface e0/0
ip address 172.16.1.2 255.255.255.0
no shutdown
exit
router ospf 1
network 10.10.10.1 0.0.0.255 area 0
network 10.10.20.1 0.0.0.255 area 0
network 172.16.1.0 0.0.0.255 area 0
exit
access-list 1 permit 192.168.1.0 0.0.0.255
access-list 2 permit host 192.168.1.2
interface e0/1
ip access-group 1 out
exit
interface e0/2
ip access-group 2 out
exit
show access-lists
This document discusses various techniques for transitioning from IPv4 to IPv6, including dual stacking, tunneling, and translation services. It provides examples of configuring dual stacking and manual IPv6 tunnels on Cisco routers to connect isolated IPv6 networks over an IPv4 infrastructure. Dual stacking allows hosts and devices to run both IPv4 and IPv6 simultaneously, while tunneling encapsulates IPv6 packets in IPv4 to enable connectivity across non-IPv6 networks. The document demonstrates establishing an IPv6 tunnel between two routers and routing IPv6 packets over the tunnel using RIPng.
The document describes a set of exercises to configure basic routing and OSPF routing on routers. It includes instructions on configuring interfaces, static routing, and OSPF routing. Participants will work in groups to configure three routers and four switches with a common IP addressing scheme and network topology. The exercises progress from basic router configuration to static routing and finally dynamic routing using OSPF.
AutoIP -A mechanism for IPv6 migration and IPv4 sunsetting by Shishio Tsuchiy...APNIC
AutoIP is a mechanism for IPv6 migration and IPv4 sunsetting that dynamically creates an overlay tunnel topology using native IGPs to discover tunnel endpoints. It allows networks to transition from IPv4 to IPv6 in phases, first deploying IPv6 over IPv4 tunnels, then IPv4 over IPv6, before finally transitioning to a native IPv6 network. Cisco has implemented AutoIP in early field trial code that establishes OSPFv3-based tunnels for IPv6 and IPv4 routing using GRE tunnels.
The document discusses IPv4 and IPv6 addressing. It notes that IPv4 provides 4.3 billion addresses while IPv6 provides 3.4 undecillion addresses. It then outlines some limitations of IPv4 including limited addresses and lack of built-in security. Improvements in IPv6 are discussed such as built-in security, more efficient routing, and vastly increased address space. Examples of IPv4 and IPv6 addresses are provided. The document also discusses IPv6 addressing formats, types of IPv6 addresses including unicast, anycast and multicast, and IPv6 transition technologies.
IPv6 - Jozi Linux User Group PresentationJumping Bean
The document provides an overview of IPv6 including its address notation, allocation, classes, scopes, and network configuration. It discusses IPv6 goals of expanding the IP address space and simplifying network administration. It also covers IPv6 implementations for home and small office networks, including stateless address autoconfiguration (SLAAC) and DHCPv6.
what/why/how of IPv6 || 2002:3239:43c3::1Anshu Prateek
IPv6 is the successor to IPv4 and was developed to address the problem of IPv4 running out of addresses. IPv6 implements a new 128-bit addressing system that provides many more addresses than IPv4. Transitioning to IPv6 is important for businesses to allow for personalized content, targeted advertising, and to avoid issues with widespread network address translation. Individuals and organizations can obtain IPv6 access through their ISP's native implementation, by using tunneling services like Tunnelbroker.net, or via protocols like 6to4 and Teredo that tunnel IPv6 traffic over IPv4 networks.
This document discusses various techniques for IPv6 transition and coexistence with IPv4, including:
- Dual-stack which allows simultaneous support of both IPv4 and IPv6.
- Tunnels which encapsulate IPv6 packets in IPv4 packets to provide IPv6 connectivity through IPv4 networks.
- Translation techniques like NAT64 which allow communication between IPv4-only and IPv6-only nodes.
This document provides a lightning fast introduction to IPv6, including:
- IPv6 was created to replace IPv4 due to the internet running out of IPv4 addresses. It features 128-bit addresses and other improvements.
- IPv6 adoption has been slow partly due to the emergence of Network Address Translation (NAT).
- Stateless Address AutoConfiguration (SLAAC) and Stateful DHCPv6 are common methods for IPv6 hosts to obtain addresses and configuration.
- IPv6 supports features like mobility, where a device can keep the same IP address when moving networks.
- Developers need to update code to support the new IPv6 addressing and libraries.
This document provides an overview of IPv6 including:
- The expanded 128-bit addressing scheme and different address types like unicast, multicast, etc.
- Simplified header format compared to IPv4 and removal of checksumming at the network layer.
- Transition mechanisms between IPv4 and IPv6 like 6to4 and ISATAP addressing.
- Hierarchical and aggregatable global address allocation policies and interface identifier assignments.
- IPv6 header options and their processing model compared to IPv4.
Cisco CCNA Training/Exam Tips that are helpful for your Certification Exam!
To be Cisco Certified please Check out:
http://asmed.com/information-technology-it/
Similar to Hands-on Experience with IPv6 Routing and Services (20)
Cisco connect montreal 2018 - Network Slicing: Horizontal VirtualizationCisco Canada
The document discusses network slicing, which is the next step in virtualization for 4G/5G mobile networks. Network slicing allows the core network to be partitioned into multiple logical networks or "slices", each with its own network functions to support the requirements of different services. This approach enables network resources and functions to be allocated to specific services or customer segments in a flexible manner. It reduces complexity compared to existing networks that must support many different services and customers on a single common infrastructure. The key benefits of network slicing include improved network agility and the ability to support diverse service requirements.
The document summarizes a Cisco presentation on next-generation datacenter security. It discusses how the majority of security teams' time is spent securing servers and data in the datacenter. It then covers challenges such as budget constraints, product overload, and complexity of threats. The presentation introduces Cisco's architectural approach to datacenter security focusing on threat prevention, visibility, segmentation, threat intelligence, automation, and analytics. It provides examples of Cisco solutions that integrate to deliver firewall, access control, analytics, and other capabilities.
Cisco connect montreal 2018 vision mondiale analyse localeCisco Canada
The document discusses Cisco's multi-cloud strategy and products. It introduces Cisco Container Platform (CCP) as a solution that automates deploying, running, and operating containers on physical or virtual machines. CCP is based on Kubernetes and provides integrated networking, management, security and analytics capabilities while allowing containers to run in hybrid cloud environments across VM, bare metal, Cisco HyperFlex, ACI and public clouds.
Cisco Connect Montreal 2018 Securité : Sécuriser votre mobilité avec CiscoCisco Canada
The document discusses Cisco's solutions for securing mobility, including Meraki SM, Cisco AMP for Endpoint, Cisco Umbrella, Cisco Cloudlock, Cisco Cloud Email Security, Cisco Threat Response, Identity Service Engine, and Cisco DUO Security. Representatives from Cisco provide overviews of each solution for securing users, data, and applications across SaaS, PaaS, and IaaS environments.
Cisco connect montreal 2018 collaboration les services webex hybridesCisco Canada
Cisco Connect Montreal provided information on Cisco's Webex Hybrid Services which allow for integration between on-premises and cloud collaboration solutions. The key services discussed included Hybrid Directory Service for user synchronization, Hybrid Calendar Service for calendaring integration, Hybrid Call Service for calling capabilities, Hybrid Message Service for messaging interoperability, and the new Cisco Webex Edge service for enhanced audio, video mesh, and media experiences.
Integration cisco et microsoft connect montreal 2018Cisco Canada
The document discusses Cisco and Microsoft integrations for collaboration. It describes major areas of integration including calling, messaging, meetings, email/calendar, content management, and instant messaging. It provides details on Cisco and Microsoft integrations for meetings, with examples of joining internal and external participants. The document also discusses Cisco Spark and Webex capabilities for open collaboration across organizations and platforms.
Cisco connect montreal 2018 saalvare md-program-xr-v2Cisco Canada
This document summarizes a presentation on model-driven programmability for Cisco IOS XR. The presentation covers data models, management protocols like NETCONF and gRPC, the YANG Development Kit (YDK) SDK, and telemetry. It defines key concepts like model-driven manageability, native and open data models, protocol operations, and the benefits of the YDK for simplifying application development through model-driven abstractions. Example code demonstrates basic YDK usage and a potential peering configuration use case is outlined. Resources for further information are also provided.
Cisco connect montreal 2018 sd wan - delivering intent-based networking to th...Cisco Canada
The document discusses Cisco SD-WAN and its advantages over traditional and legacy WAN architectures. It highlights how Cisco SD-WAN uses a centralized control plane and software-defined intelligence to provide automated, predictive, and intent-based networking. This allows for flexible, scalable, and secure connectivity across hybrid WAN transports in a way that is simpler to manage and operate than hardware-centric WAN solutions.
Cisco Connect Toronto 2018 DNA automation-the evolution to intent-based net...Cisco Canada
The document discusses Cisco's DNA Center and its capabilities for automating network management. It covers:
- Why intent-based networking is needed to reduce costs and errors from manual network changes
- How DNA Center supports intent-based networking by allowing administrators to define policies and have them automatically implemented across the network
- Key automation use cases DNA Center addresses like onboarding new devices, managing software upgrades, creating configuration templates, and deploying wireless networks
- Demonstrations of DNA Center's capabilities for plug-and-play deployment, software management, template configuration, and wireless provisioning
Cisco Connect Toronto 2018 an introduction to Cisco kineticCisco Canada
Robert Barton from Cisco presented on Cisco Kinetic, an IoT analytics platform. Cisco Kinetic consists of three modules: the Gateway Management Module for onboarding and managing IoT gateways at scale, the Edge and Fog Processing Module for analyzing IoT data in real-time at the edge, and the Data Control Module for securely routing IoT data between edge, fog, and cloud according to data policies. Cisco Kinetic aims to enable end-to-end IoT analytics across the entire network from device to cloud.
Cisco Connect Toronto 2018 DevNet OverviewCisco Canada
Hank Preston, a Cisco engineer, gave a presentation on DevNet and how it is helping developers. He discussed how DevNet has grown significantly, now with over 100,000 members and 500,000 learning labs completed. DevNet provides resources like APIs, sandboxes, and training to help developers build applications and automate networks. Preston emphasized that networks are becoming more programmable and automated through DevNet tools and platforms.
Cisco Connect Toronto 2018 DNA assuranceCisco Canada
The document discusses Cisco's DNA Assurance solution. It provides an agenda that covers business requirements, context, learning, user requirements, technology requirements, and the various components of DNA Assurance including client assurance, network assurance, application assurance, and machine learning. It discusses challenges around network operations including time spent troubleshooting and replicating issues. It also covers how DNA Assurance uses concepts like context, learning, and design thinking to provide insights and automate remediation.
Cisco Connect Toronto 2018 network-slicingCisco Canada
The document discusses network slicing, which is the partitioning of network resources and functions to run selected applications, services, or connections in isolation from each other for specific business purposes. This allows mobile operators to offer virtual private networks on a common infrastructure through network slicing on an end-to-end basis across access, transport, and core networks. Slicing enables new revenue opportunities through network slices optimized for different vertical industries while simplifying service delivery and management.
Cisco Connect Toronto 2018 the intelligent network with cisco merakiCisco Canada
The document discusses Cisco Meraki's intelligent network and SD-WAN capabilities. It highlights that Meraki has over 14,000 customers using its SD-WAN, it has a renewal rate over 95%, and its newest product is WAN assurance. The presentation provides an overview of Meraki's cloud-managed solutions for wireless, switching, security, and other IT functions. It demonstrates Meraki's network monitoring and troubleshooting tools through examples and a demo of its capabilities.
Cisco Connect Toronto 2018 sixty to zeroCisco Canada
The document discusses automating security tasks through various solutions from Cisco. It introduces the Cisco Advanced Malware Protection (AMP) solution, which uses machine learning to detect known and unknown malware across endpoints, networks, and email. It also introduces Cisco Cognitive Threat Analytics, which analyzes web traffic using machine learning to detect anomalous and malicious activity inside organizations. The document provides examples of how these solutions can automate tasks like hunting for threats, detecting anomalies, and attributing suspicious activity to specific entities. It includes demos of the AMP and Cognitive Intelligence user interfaces.
"Scaling RAG Applications to serve millions of users", Kevin GoedeckeFwdays
How we managed to grow and scale a RAG application from zero to thousands of users in 7 months. Lessons from technical challenges around managing high load for LLMs, RAGs and Vector databases.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
QA or the Highway - Component Testing: Bridging the gap between frontend appl...zjhamm304
These are the slides for the presentation, "Component Testing: Bridging the gap between frontend applications" that was presented at QA or the Highway 2024 in Columbus, OH by Zachary Hamm.
The Department of Veteran Affairs (VA) invited Taylor Paschal, Knowledge & Information Management Consultant at Enterprise Knowledge, to speak at a Knowledge Management Lunch and Learn hosted on June 12, 2024. All Office of Administration staff were invited to attend and received professional development credit for participating in the voluntary event.
The objectives of the Lunch and Learn presentation were to:
- Review what KM ‘is’ and ‘isn’t’
- Understand the value of KM and the benefits of engaging
- Define and reflect on your “what’s in it for me?”
- Share actionable ways you can participate in Knowledge - - Capture & Transfer
LF Energy Webinar: Carbon Data Specifications: Mechanisms to Improve Data Acc...DanBrown980551
This LF Energy webinar took place June 20, 2024. It featured:
-Alex Thornton, LF Energy
-Hallie Cramer, Google
-Daniel Roesler, UtilityAPI
-Henry Richardson, WattTime
In response to the urgency and scale required to effectively address climate change, open source solutions offer significant potential for driving innovation and progress. Currently, there is a growing demand for standardization and interoperability in energy data and modeling. Open source standards and specifications within the energy sector can also alleviate challenges associated with data fragmentation, transparency, and accessibility. At the same time, it is crucial to consider privacy and security concerns throughout the development of open source platforms.
This webinar will delve into the motivations behind establishing LF Energy’s Carbon Data Specification Consortium. It will provide an overview of the draft specifications and the ongoing progress made by the respective working groups.
Three primary specifications will be discussed:
-Discovery and client registration, emphasizing transparent processes and secure and private access
-Customer data, centering around customer tariffs, bills, energy usage, and full consumption disclosure
-Power systems data, focusing on grid data, inclusive of transmission and distribution networks, generation, intergrid power flows, and market settlement data
In our second session, we shall learn all about the main features and fundamentals of UiPath Studio that enable us to use the building blocks for any automation project.
📕 Detailed agenda:
Variables and Datatypes
Workflow Layouts
Arguments
Control Flows and Loops
Conditional Statements
💻 Extra training through UiPath Academy:
Variables, Constants, and Arguments in Studio
Control Flow in Studio
This talk will cover ScyllaDB Architecture from the cluster-level view and zoom in on data distribution and internal node architecture. In the process, we will learn the secret sauce used to get ScyllaDB's high availability and superior performance. We will also touch on the upcoming changes to ScyllaDB architecture, moving to strongly consistent metadata and tablets.
Must Know Postgres Extension for DBA and Developer during MigrationMydbops
Mydbops Opensource Database Meetup 16
Topic: Must-Know PostgreSQL Extensions for Developers and DBAs During Migration
Speaker: Deepak Mahto, Founder of DataCloudGaze Consulting
Date & Time: 8th June | 10 AM - 1 PM IST
Venue: Bangalore International Centre, Bangalore
Abstract: Discover how PostgreSQL extensions can be your secret weapon! This talk explores how key extensions enhance database capabilities and streamline the migration process for users moving from other relational databases like Oracle.
Key Takeaways:
* Learn about crucial extensions like oracle_fdw, pgtt, and pg_audit that ease migration complexities.
* Gain valuable strategies for implementing these extensions in PostgreSQL to achieve license freedom.
* Discover how these key extensions can empower both developers and DBAs during the migration process.
* Don't miss this chance to gain practical knowledge from an industry expert and stay updated on the latest open-source database trends.
Mydbops Managed Services specializes in taking the pain out of database management while optimizing performance. Since 2015, we have been providing top-notch support and assistance for the top three open-source databases: MySQL, MongoDB, and PostgreSQL.
Our team offers a wide range of services, including assistance, support, consulting, 24/7 operations, and expertise in all relevant technologies. We help organizations improve their database's performance, scalability, efficiency, and availability.
Contact us: info@mydbops.com
Visit: https://www.mydbops.com/
Follow us on LinkedIn: https://in.linkedin.com/company/mydbops
For more details and updates, please follow up the below links.
Meetup Page : https://www.meetup.com/mydbops-databa...
Twitter: https://twitter.com/mydbopsofficial
Blogs: https://www.mydbops.com/blog/
Facebook(Meta): https://www.facebook.com/mydbops/
Dandelion Hashtable: beyond billion requests per second on a commodity serverAntonios Katsarakis
This slide deck presents DLHT, a concurrent in-memory hashtable. Despite efforts to optimize hashtables, that go as far as sacrificing core functionality, state-of-the-art designs still incur multiple memory accesses per request and block request processing in three cases. First, most hashtables block while waiting for data to be retrieved from memory. Second, open-addressing designs, which represent the current state-of-the-art, either cannot free index slots on deletes or must block all requests to do so. Third, index resizes block every request until all objects are copied to the new index. Defying folklore wisdom, DLHT forgoes open-addressing and adopts a fully-featured and memory-aware closed-addressing design based on bounded cache-line-chaining. This design offers lock-free index operations and deletes that free slots instantly, (2) completes most requests with a single memory access, (3) utilizes software prefetching to hide memory latencies, and (4) employs a novel non-blocking and parallel resizing. In a commodity server and a memory-resident workload, DLHT surpasses 1.6B requests per second and provides 3.5x (12x) the throughput of the state-of-the-art closed-addressing (open-addressing) resizable hashtable on Gets (Deletes).
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectorsDianaGray10
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
inQuba Webinar Mastering Customer Journey Management with Dr Graham HillLizaNolte
HERE IS YOUR WEBINAR CONTENT! 'Mastering Customer Journey Management with Dr. Graham Hill'. We hope you find the webinar recording both insightful and enjoyable.
In this webinar, we explored essential aspects of Customer Journey Management and personalization. Here’s a summary of the key insights and topics discussed:
Key Takeaways:
Understanding the Customer Journey: Dr. Hill emphasized the importance of mapping and understanding the complete customer journey to identify touchpoints and opportunities for improvement.
Personalization Strategies: We discussed how to leverage data and insights to create personalized experiences that resonate with customers.
Technology Integration: Insights were shared on how inQuba’s advanced technology can streamline customer interactions and drive operational efficiency.
High performance Serverless Java on AWS- GoTo Amsterdam 2024Vadym Kazulkin
Java is for many years one of the most popular programming languages, but it used to have hard times in the Serverless community. Java is known for its high cold start times and high memory footprint, comparing to other programming languages like Node.js and Python. In this talk I'll look at the general best practices and techniques we can use to decrease memory consumption, cold start times for Java Serverless development on AWS including GraalVM (Native Image) and AWS own offering SnapStart based on Firecracker microVM snapshot and restore and CRaC (Coordinated Restore at Checkpoint) runtime hooks. I'll also provide a lot of benchmarking on Lambda functions trying out various deployment package sizes, Lambda memory settings, Java compilation options and HTTP (a)synchronous clients and measure their impact on cold and warm start times.
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
What is an RPA CoE? Session 2 – CoE RolesDianaGray10
In this session, we will review the players involved in the CoE and how each role impacts opportunities.
Topics covered:
• What roles are essential?
• What place in the automation journey does each role play?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
Northern Engraving | Modern Metal Trim, Nameplates and Appliance PanelsNorthern Engraving
What began over 115 years ago as a supplier of precision gauges to the automotive industry has evolved into being an industry leader in the manufacture of product branding, automotive cockpit trim and decorative appliance trim. Value-added services include in-house Design, Engineering, Program Management, Test Lab and Tool Shops.
Leveraging the Graph for Clinical Trials and Standards
Hands-on Experience with IPv6 Routing and Services
1. Hands-on Experience with IPv6 Routing and
Services
Faraz Shamim, Technical Leader
Harold Ritter, Technical Leader
2. 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.
Prerequisites: Session Abstract
2
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
4
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
7
8. Lab 1 IPv6 Stateless Auto-Configuration (SLAAC)
• Your plan is to test the plug and play behavior 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
8
11. R4 H1
R4#sh ipv6 int e0/0
Ethernet0/0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5400
No Virtual link-local address(es):
Global unicast address(es):
FD01:DB8:1:41:A8B8:CCFF:FE00:5400, subnet is FD01:DB8:1:41::/64
[EUI]
Joined group address(es):
FF02::1
FF02::2
FF02::1:FF00:5400
MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
ICMP unreachables are sent
ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds (using 30000)
ND advertised reachable time is 0 (unspecified)
ND advertised retransmit interval is 0 (unspecified)
ND router advertisements are sent every 200 seconds
ND router advertisements live for 1800 seconds
ND advertised default router preference is Medium
Hosts use stateless autoconfig for addresses.
H1#sh ipv6 int e0/0
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 2591861 preferred lifetime 604661
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 30000 milliseconds (using 30000)
Default router is FE80::A8BB:CCFF:FE00:5400 on Ethernet0/0
Lab 1 IPv6 Unique Local & SLAAC:
Verification
11
12. R# Verification commands
H1 H1#ping FE80::A8BB:CCFF:FE00:5400
Output Interface: Ethernet0/0
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to FE80::A8BB:CCFF:FE00:5400, timeout is 2 seconds:
Packet sent with a source address of FE80::A8BB:CCFF:FE00:5700%Ethernet0/0
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/0/1 ms
H1#
Note: the last 64 bit address may be different from A8BB:CCFF:FE00:5400, verify with show ipv6 interface on
R4 E0/0
H1 H1#ping FD01:DB8:1:41:A8B8:CCFF:FE00:5400
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to FD01:DB8:1:41:A8B8:CCFF:FE00:5400, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/3/17 ms
H1#
Note: the last 64 bit address may be different from A8BB:CCFF:FE00:5400, verify with show ipv6 interface on
R4 E0/0
Lab 1 IPv6 Unique Local & SLAAC:
Verification
12
13. R4 H1
R4#deb ipv6 nd
ICMP Neighbor Discovery events debugging is on
ICMPv6-ND: Request to send RA for FE80::A8BB:CCFF:FE00:5400
ICMPv6-ND: Setup RA from FE80::A8BB:CCFF:FE00:5400 to FF02::1 on
Ethernet0/0
ICMPv6-ND: MTU = 1500
ICMPv6-ND: prefix = FD01:DB8:1:41::/64 onlink autoconfig
ICMPv6-ND: 2592000/604800 (valid/preferred)
ICMPv6-ND: Request to send RA for FE80::A8BB:CCFF:FE00:5400
ICMPv6-ND: Setup RA from FE80::A8BB:CCFF:FE00:5400 to FF02::1 on
Ethernet0/0
ICMPv6-ND: MTU = 1500
ICMPv6-ND: prefix = FD01:DB8:1:41::/64 onlink autoconfig
ICMPv6-ND: 2592000/604800 (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:
2592000, Prf Lifetime: 604800, PI Flags: C0
ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig
FD01:DB8:1:41::/64 eui-64, FD01:DB8:1:41:A8BB:CCFF:FE00:5700
FD01:DB8:1:41:A8BB:CCFF:FE00:5700/64 is existing
ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5400 on
Ethernet0/0
ICMPv6-ND: Prefix : FD01:DB8:1:1::, Length: 64, Vld Lifetime:
2592000, Prf Lifetime: 604800, PI Flags: C0
ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig
FD01:DB8:1:41::/64 eui-64, FD01:DB8:1:41:A8BB:CCFF:FE00:5700
FD01:DB8:1:41:A8BB:CCFF:FE00:5700/64 is existing
H1#
Lab 1 IPv6 SLAAC: Debugs
13
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
14
15. Lab 1 IPv6 Global Unicast Address
• 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
19. R4 Loopback 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 30000 milliseconds (using 30000)
ND RAs are suppressed (periodic)
Hosts use stateless autoconfig for addresses.
R4#
Lab 1 IPv6 Global Unicast address: Verification
19
20. R4 Ethernet0/0
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 30000 milliseconds (using 30000)
ND advertised reachable time is 0 (unspecified)
ND advertised retransmit interval is 0 (unspecified)
ND router advertisements are sent every 200 seconds
ND router advertisements live for 1800 seconds
ND advertised default router preference is Medium
Hosts use stateless autoconfig for addresses.
R4#
Lab 1 IPv6 Global Unicast address: Verification
20
21. 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 30000 milliseconds (using 30000)
ND RAs are suppressed (periodic)
Hosts use stateless autoconfig for addresses.
R5#
Lab 1 IPv6 Global Unicast address: Verification
21
22. 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::/64
2001:DB8:1:57::5, subnet is 2001:DB8:1:57::/64
2001:DB8:1:58::5, subnet is 2001:DB8:1:58::/64
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 30000 milliseconds (using 30000)
ND advertised reachable time is 0 (unspecified)
ND advertised retransmit interval is 0 (unspecified)
ND router advertisements are sent every 200 seconds
ND router advertisements live for 1800 seconds
ND advertised default router preference is Medium
Hosts use stateless autoconfig for addresses.
Lab 1 IPv6 Global Unicast address: Verification
22
23. R6 Loopback 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 30000 milliseconds (using 30000)
ND RAs are suppressed (periodic)
Hosts use stateless autoconfig for addresses.
R6#
Lab 1 IPv6 Global Unicast address: Verification
23
24. R6 Ethernet0/0
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::/64
2001:DB8:1:57::6, subnet is 2001:DB8:1:57::/64
2001:DB8:1:58::6, subnet is 2001:DB8:1:58::/64
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 30000 milliseconds (using 30000)
ND advertised reachable time is 0 (unspecified)
ND advertised retransmit interval is 0 (unspecified)
ND router advertisements are sent every 200 seconds
ND router advertisements live for 1800 seconds
ND advertised default router preference is Medium
Hosts use stateless autoconfig for addresses.
Lab 1 IPv6 Global Unicast address: Verification
24
25. H1 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 2591845 preferred lifetime 604645
FD01:DB8:1:41:A8BB:CCFF:FE00:5700, subnet is FD01:DB8:1:41::/64 [EUI/CAL/PRE]
valid lifetime 2591845 preferred lifetime 604645
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 30000 milliseconds (using 30000)
Default router is FE80::A8BB:CCFF:FE00:5400 on Ethernet0/0
H1#
Lab 1 IPv6 SLAAC: Verification
25
26. H2 Ethernet0/0
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 2591989 preferred lifetime 604789
2001:DB8:1:57:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:57::/64 [EUI/CAL/PRE]
valid lifetime 2591989 preferred lifetime 604789
2001:DB8:1:58:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:58::/64 [EUI/CAL/PRE]
valid lifetime 2591989 preferred lifetime 604789
Joined group address(es):
FF02::1
FF02::1:FF00:5D00
MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
ICMP unreachables are sent
ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds (using 30000)
Default router is FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0
Lab 1 IPv6 SLAAC: Verification
26
27. R# Verification commands
H2 H2#ping 2001:db8:1:56::5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:56::5, timeout is 2
seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/3/14 ms
H2#ping 2001:db8:1:57::5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:57::5, timeout is 2
seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/4/21 ms
H2#ping 2001:db8:1:58::5
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:58::5, timeout is 2
seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/4/19 ms
H2#ping 2001:db8:1:56::6
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:56::6, timeout is 2
seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/4/17 ms
H2#ping 2001:db8:1:57::6
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:57::6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/3/17 ms
H2#ping 2001:db8:1:58::6
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:58::6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/3/14 ms
H2#
Lab 1 IPv6 Global Unicast address: Verification
27
28. R# Verification commands
H1 H1#ping 2001:DB8:1:41::4
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:41::4, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/3/17 ms
H1#
Lab 1 IPv6 SLAAC: Verification
28
29. R5
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: 2592000/604800 (valid/preferred)
ICMPv6-ND: prefix = 2001:DB8:1:57::/64 onlink autoconfig
ICMPv6-ND: 2592000/604800 (valid/preferred)
ICMPv6-ND: prefix = 2001:DB8:1:58::/64 onlink autoconfig
ICMPv6-ND: 2592000/604800 (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: 2592000, Prf Lifetime: 604800, PI Flags: C0
ICMPv6-ND: Prefix : 2001:DB8:1:57::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0
ICMPv6-ND: Prefix : 2001:DB8:1:58::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0
R5#
Lab 1 IPv6 SLAAC: Debugs
29
30. R6
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: 2592000/604800 (valid/preferred)
ICMPv6-ND: prefix = 2001:DB8:1:57::/64 onlink autoconfig
ICMPv6-ND: 2592000/604800 (valid/preferred)
ICMPv6-ND: prefix = 2001:DB8:1:58::/64 onlink autoconfig
ICMPv6-ND: 2592000/604800 (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: 2592000, Prf Lifetime: 604800, PI Flags: C0
ICMPv6-ND: Prefix : 2001:DB8:1:57::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0
ICMPv6-ND: Prefix : 2001:DB8:1:58::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0
H2#
Lab 1 IPv6 SLAAC: Debugs
30
31. H1
H1#deb ipv6 nd
ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5900 on Ethernet0/0
ICMPv6-ND: Prefix : 2001:DB8:1:41::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0
ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig 2001:DB8:1:41::/64 eui-64, 2001:DB8:1:41:A8BB:CCFF:FE00:5C00
2001:DB8:1:41:A8BB:CCFF:FE00:5C00/64 is existing
ICMPv6-ND: Prefix : FD01:DB8:1:41::, Length: 64, Vld Lifetime: 2592000, Prf Lifetime: 604800, PI Flags: C0
ICMPv6-ND: %Ethernet0/0: OK: IPv6 Address Autoconfig FD01:DB8:1:41::/64 eui-64, FD01:DB8:1:41:A8BB:CCFF:FE00:5C00
FD01:DB8:1:41:A8BB:CCFF:FE00:5C00/64 is existing
H1#
Lab 1 IPv6 SLAAC: Debugs
31
34. 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
34
36. R4
R4#sh ipv6 int e0/0
Ethernet0/0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5900
No Virtual link-local address(es):
Global unicast address(es):
2001:DB8:1:41::4, subnet is 2001:DB8:1:41::/64
FD01:DB8:1:41:A8BB:CCFF:FE00:5900, subnet is
FD01:DB8:1:41::/64 [EUI]
Joined group address(es):
FF02::1
FF02::2
FF02::1:FF00:4
FF02::1:FF00:5900
MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
ICMP unreachables are sent
ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds (using 30000)
ND advertised reachable time is 0 (unspecified)
ND advertised retransmit interval is 0 (unspecified)
ND router advertisements are sent every 30 seconds
ND router advertisements live for 1800 seconds
ND advertised default router preference is Medium
Hosts use stateless autoconfig for addresses.
R4#
Lab 2 IPv6 Neighbor discovery: Verification
36
37. H1
H1(config-if)#ipv6 enable
*Jan 30 21:25:07.269: ICMPv6-ND: ND Module startup.
*Jan 30 21:25:07.270: ICMPv6-ND: Initialise OL prefix database
*Jan 30 21:25:07.270: ICMPv6-ND: IPv6 Opr Enabled on Null0
*Jan 30 21:25:07.270: ICMPv6-ND: Allocate ND subblock on Null0 [1]
*Jan 30 21:25:07.271: ICMPv6-ND: L2 came up on Null0
*Jan 30 21:25:07.271: IPv6-Addrmgr-ND: DAD request for FE80::1 on Null0
*Jan 30 21:25:07.271: IPv6-Addrmgr-ND: DAD: FE80::1 is unique.
*Jan 30 21:25:07.271: ICMPv6-ND: L3 came up on Null0
*Jan 30 21:25:07.271: ICMPv6-ND: Linklocal FE80::1 on Null0, Up
*Jan 30 21:25:07.271: ICMPv6-ND: IPv6 Opr Enabled on Ethernet0/0
*Jan 30 21:25:07.271: ICMPv6-ND: Allocate ND subblock on Ethernet0/0 [2]
*Jan 30 21:25:07.271: ICMPv6-ND: L2 came up on Ethernet0/0
*Jan 30 21:25:07.271: IPv6-Addrmgr-ND: DAD request for FE80::A8BB:CCFF:FE00:5C00 on Ethernet0/0
*Jan 30 21:25:07.272: ICMPv6-ND: Sending NS for FE80::A8BB:CCFF:FE00:5C00 on Ethernet0/0
*Jan 30 21:25:08.272: IPv6-Addrmgr-ND: DAD: FE80::A8BB:CCFF:FE00:5C00 is unique.
*Jan 30 21:25:08.272: ICMPv6-ND: Sending NA for FE80::A8BB:CCFF:FE00:5C00 on Ethernet0/0
*Jan 30 21:25:08.272: ICMPv6-ND: L3 came up on Ethernet0/0
*Jan 30 21:25:08.272: ICMPv6-ND: Linklocal FE80::A8BB:CCFF:FE00:5C00 on Ethernet0/0, Up
H1(config-if)#ipv6 address autoconfig
*Jan 30 21:25:20.231: ICMPv6-ND: Sending RS on Ethernet0/0
*Jan 30 21:25:20.251: ICMPv6-ND: Received RA from FE80::A8BB:CCFF:FE00:5900 on Ethernet0/0
Lab 2 IPv6 Neighbor discovery: Debugs
37
38. 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
38
40. R4
R6#sh ipv6 int
Ethernet0/0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5B00
No Virtual link-local address(es):
Global unicast address(es):
2001:DB8:1:56::6, subnet is 2001:DB8:1:56::/64
2001:DB8:1:57::6, subnet is 2001:DB8:1:57::/64
2001:DB8:1:58::6, subnet is 2001:DB8:1:58::/64
2001:DB8:1:59::5, subnet is 2001:DB8:1:59::/64
Joined group address(es):
FF02::1
FF02::2
FF02::1:FF00:5
FF02::1:FF00:6
FF02::1:FF00:5B00
MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
…
R5#sh ipv6 int e0/0 | i DUP
2001:DB8:1:59::5, subnet is 2001:DB8:1:59::/64 [DUP]
Lab 2 IPv6 Neighbor discovery: Verification
40
41. 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: 2592000/604800 (valid/preferred)
*Jan 30 21:49:39.078: IPv6-Addrmgr-ND: Received prefix PI-flag change notification: prefix 2001:DB8:1:59::/64 onlink (was not-onlink)
*Jan 30 21:49:39.078: IPv6-Addrmgr-ND: DAD request for 2001:DB8:1:59::5 on Ethernet0/0
*Jan 30 21:49:39.079: ICMPv6-ND: Sending NS for 2001:DB8:1:59::5 on Ethernet0/0
*Jan 30 21:49:39.094: ICMPv6-ND: Received NA for 2001:DB8:1:59::5 on Ethernet0/0 from 2001:DB8:1:59::5
*Jan 30 21:49:39.095: %IPV6_ND-4-DUPLICATE: Duplicate address 2001:DB8:1:59::5 on Ethernet0/0
Lab 2 IPv6 Neighbor discovery: Debugs
41
43. R5
R5#ping 2001:db8:1:56::6
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:1:56::6, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/1/5 ms
R5#
*Jan 30 22:15:24.668: ICMPv6-ND: DELETE -> INCMP: 2001:DB8:1:56::6
*Jan 30 22:15:24.668: ICMPv6-ND: Sending NS for 2001:DB8:1:56::6 on Ethernet0/0
*Jan 30 22:15:24.669: ICMPv6-ND: Resolving next hop 2001:DB8:1:56::6 on interface Ethernet0/0
*Jan 30 22:15:24.673: ICMPv6-ND: Received NA for 2001:DB8:1:56::6 on Ethernet0/0 from 2001:DB8:1:56::6
*Jan 30 22:15:24.673: ICMPv6-ND: Neighbour 2001:DB8:1:56::6 on Ethernet0/0 : LLA aabb.cc00.5b00
*Jan 30 22:15:24.673: ICMPv6-ND: INCMP -> REACH: 2001:DB8:1:56::6
R5#
*Jan 30 22:15:29.722: ICMPv6-ND: Received NS for 2001:DB8:1:56::5 on Ethernet0/0 from FE80::A8BB:CCFF:FE00:5B00
*Jan 30 22:15:29.722: ICMPv6-ND: Sending NA for 2001:DB8:1:56::5 on Ethernet0/0
*Jan 30 22:15:29.723: ICMPv6-ND: STALE -> DELAY: FE80::A8BB:CCFF:FE00:5B00
Lab 2 IPv6 Neighbor discovery: Debugs
43
44. 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)
44
45. Lab 2 Neighbor Discovery: Renumbering
• 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
45
47. H2
H2#sh ipv6 int e0/0
Ethernet0/0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5D00
No Virtual link-local address(es):
Stateless address autoconfig enabled
Global unicast address(es):
2001:DB8:1:56:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:56::/64 [EUI/CAL/PRE]
valid lifetime 2591994 preferred lifetime 604794
2001:DB8:1:57:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:57::/64 [EUI/CAL/PRE]
valid lifetime 2591994 preferred lifetime 604794
2001:DB8:1:58:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:58::/64 [EUI/CAL]
valid lifetime 47 preferred lifetime 0
2001:DB8:1:88:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:88::/64 [EUI/CAL/PRE]
valid lifetime 2591994 preferred lifetime 604794
Joined group address(es):
FF02::1
FF02::1:FF00:5D00
MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
ICMP unreachables are sent
Lab 2 IPv6 Neighbor Discovery: Verification
47
50. H2
H2#sh ipv6 int e0/0
Ethernet0/0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:5D00
No Virtual link-local address(es):
Stateless address autoconfig enabled
Global unicast address(es):
2001:DB8:1:56:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:56::/64 [EUI/CAL/PRE]
valid lifetime 2591986 preferred lifetime 604786
2001:DB8:1:57:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:57::/64 [EUI/CAL/PRE]
valid lifetime 2591986 preferred lifetime 604786
2001:DB8:1:88:A8BB:CCFF:FE00:5D00, subnet is 2001:DB8:1:88::/64 [EUI/CAL/PRE]
valid lifetime 2591986 preferred lifetime 604786
Joined group address(es):
FF02::1
FF02::1:FF00:5D00
MTU is 1500 bytes
ICMP error messages limited to one every 100 milliseconds
ICMP redirects are enabled
ICMP unreachables are sent
ND DAD is enabled, number of DAD attempts: 1
ND reachable time is 30000 milliseconds (using 30000)
Default router is FE80::A8BB:CCFF:FE00:5B00 on Ethernet0/0
H2#
Lab 2 IPv6 Neighbor Discovery: Verification
50
53. Lab 2 Neighbor Discovery: Default Router
Selection
• In site 2, you want to see how the default router selection
behaves in IPv6
• You noticed that as soon as you enable IPv6 on H2, it starts
sending RS on the wire, looking for a router.
• You also noticed in the debugs that both R5 and R6 are sending
RA messages towards H2. H2 looks at RA and configures the
addresses on its interface facing R5 & R6
• After getting the address on H2, you want to make sure that H2
prefers R5 for sending all the IPv6 traffic outbound
• (Refer to slide 34-35 for default router selection example)
53
55. H2
H2#sh ipv6 router
Router FE80::A8BB:CCFF:FE00:5B00 on Ethernet0/0, last update 0 min
Hops 64, Lifetime 1800 sec, AddrFlag=0, OtherFlag=0, MTU=1500
HomeAgentFlag=0, Preference=Medium
Reachable time 0 (unspecified), Retransmit time 0 (unspecified)
Prefix 2001:DB8:1:56::/64 onlink autoconfig
Valid lifetime 2592000, preferred lifetime 604800
Router FE80::A8BB:CCFF:FE00:5A00 on Ethernet0/0, last update 0 min
Hops 64, Lifetime 1800 sec, AddrFlag=0, OtherFlag=0, MTU=1500
HomeAgentFlag=0, Preference=High
Reachable time 0 (unspecified), Retransmit time 0 (unspecified)
Prefix 2001:DB8:1:56::/64 onlink autoconfig
Valid lifetime 2592000, preferred lifetime 604800
Lab 2 IPv6 Neighbor Discovery: Verification
55
56. H2
H2#sh ipv6 route ::/0
Routing entry for ::/0
Known via "static", distance 2, metric 0
Route count is 1/1, share count 0
Routing paths:
FE80::A8BB:CCFF:FE00:5A00, Ethernet0/0
Last updated 00:04:52 ago
Note, if you do not see a default route, type the following command and make sure you have the entry from R5
H2#sho ipv6 router
Lab 2 IPv6 Neighbor Discovery: Verification
56
59. 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
59
60. Lab 3 HSRPv6
• 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
60
62. R5 & R6
R5#sh standby brief
P indicates configured to preempt.
|
Interface Grp Pri P State Active Standby Virtual IP
Et0/0 0 105 P Active local 10.1.56.6 10.1.56.1
Et0/0 1 100 Standby FE80::A8BB:CCFF:FE00:5B00
local FE80::5:73FF:FEA0:1
R5#
R6#sh standby brief
P indicates configured to preempt.
|
Interface Grp Pri P State Active Standby Virtual IP
Et0/0 0 100 Standby 10.1.56.5 local 10.1.56.1
Et0/0 1 105 P Active local FE80::A8BB:CCFF:FE00:5A00
FE80::5:73FF:FEA0:1
R6#
Lab 3 HSRPv6: Verification
62
63. R5
R5#sh standby ethernet 0/0 1
Ethernet0/0 - Group 1 (version 2)
State is Standby
4 state changes, last state change 00:08:17
Virtual IP address is FE80::5:73FF:FEA0:1
Active virtual MAC address is 0005.73a0.0001
Local virtual MAC address is 0005.73a0.0001 (v2 IPv6 default)
Hello time 3 sec, hold time 10 sec
Next hello sent in 0.624 secs
Preemption disabled
Active router is FE80::A8BB:CCFF:FE00:5B00, priority 105 (expires in 11.328 sec)
MAC address is aabb.cc00.5b00
Standby router is local
Priority 100 (default 100)
Group name is "hsrp-Et0/0-1" (default)
Lab 3 HSRPv6: Verification
63
64. R6
R6#sh standby ethernet 0/0 1
Ethernet0/0 - Group 1 (version 2)
State is Active
2 state changes, last state change 00:07:58
Virtual IP address is FE80::5:73FF:FEA0:1
Active virtual MAC address is 0005.73a0.0001
Local virtual MAC address is 0005.73a0.0001 (v2 IPv6 default)
Hello time 3 sec, hold time 10 sec
Next hello sent in 2.768 secs
Preemption enabled
Active router is local
Standby router is FE80::A8BB:CCFF:FE00:5A00, priority 100 (expires in 9.216 sec)
Priority 105 (configured 105)
Group name is "hsrp-Et0/0-1" (default)
Lab 3 HSRPv6: Verification
64
65. H2
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#
Lab 3 HSRPv6: Verification
65
69. 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
69
70. Lab 4 EIGRPv6
• 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
70
77. 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)
77
78. Lab 5 IPv6 Static Routing: IPv6 Static Default
Route
• 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
78
81. R4
R4#sh ipv6 route ::/0
Routing entry for ::/0
Known via "static", distance 1, metric 0
Route count is 1/1, share count 0
Routing paths:
FE80::4AFF:FEA2:851, Serial1/0
Last updated 00:02:15 ago
Lab 5 IPv6 Static routing: Verification
81
82. 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
82
83. Lab 5 IPv6 Static Routing: IPv6 Static Route
• 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
83
84. R# Configs
R1 R1(config)#ipv6 route 2001:db8:1:41::/64 2001:db8:14:1::15
R1(config)#end
Lab 5 IPv6 Static routing: Configs
• Note, no interface needs to be specified when the
next hop is global unicast address
84
85. R# Verification
R1 R1#sh ipv6 route 2001:db8:1:41::/64
Routing entry for 2001:DB8:1:41::/64
Known via "static", distance 1, metric 0
Route count is 1/1, share count 0
Routing paths:
2001:DB8:14:1::15
Last updated 00:11:42 ago
R1#
H1 H1>ping 2004:db8::1
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2004:DB8::1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 38/39/44 ms
H1>
Lab 5 IPv6 Static routing: Verification
85
87. 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”
87
88. Lab 6 IPv6 Manual Tunnels: IPv6oIP4
• 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
88
91. 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 30000 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 30000 milliseconds (using 30000)
ND RAs are suppressed (periodic)
Hosts use stateless autoconfig for addresses.
R5#
Lab 6 IPv6 Manual Tunnels: Verification
91
92. R3
R3#ping 2001:db8:35:1::17
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:35:1::17, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 39/39/39 ms
R3#
Lab 6 IPv6 Manual Tunnels: Verification
92
93. 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
93
94. Lab 6 IPv6 Manual Tunnels: GRE
• 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
94
95. R# Configs
R6 R6(config-if)#int tun 0
R6(config-if)#tun source s1/0
R6(config-if)#tun destination 10.1.36.0
R6(config-if)#tun mode gre ip
R6(config-if)#ipv6 address 2001:db8:36:1::17/127
R6(config-if)#end
R3 R3(config-if)#int tun 1
R3(config-if)#tun source s2/0
R3(config-if)#tun destination 10.1.36.1
R3(config-if)#tun mode gre ip
R3(config-if)#ipv6 address 2001:db8:36:1::16/127
R3(config-if)#end
Lab 6 IPv6 Manual Tunnels: Configs
95
96. 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 30000 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 30000 milliseconds (using 30000)
ND RAs are suppressed (periodic)
Hosts use stateless autoconfig for addresses.
R6#
Lab 6 IPv6 Manual Tunnels: Verification
96
97. R3
R3#ping 2001:db8:36:1::17
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 2001:DB8:36:1::17, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 37/38/40 ms
R3#
Lab 6 IPv6 Manual Tunnels: Verification
97
99. 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
99
100. Lab 7 OSPFv3
• 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
• ISP has received a request from ABC Inc that they want IPv6
connectivity 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
10
103. 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
Lab 7 OSPFv3: Configs
10
104. R# Area 0 Configs
R1 R1(config)#ipv6 unicast-routing
R1(config)#int lo 0
R1(config-if)#ipv6 add 2001:db8:172:16::1/128
R1(config-if)#ipv6 ospf 1 area 0
R1(config)#int s1/0
R1(config-if)#ipv6 add 2001:db8:172:17::/127
R1(config-if)#ipv6 ospf 1 area 0
R1(config-if)#end
Lab 7 OSPFv3: Configs
10
105. R2
R2#sh ipv6 ospf nei
OSPFv3 Router with ID (172.16.1.2) (Process ID 1)
Neighbor ID Pri State Dead Time Interface ID Interface
172.16.1.1 0 FULL/ - 00:00:31 6 Serial1/0
172.16.1.3 1 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/0 1 0 6 64 P2P 1/1
Et0/0 1 1 2 10 BDR 1/1
R2#
Lab 7 OSPFv3: Verification
10
106. R2
R2#sh ipv6 ospf
Routing Process "ospfv3 1" with ID 172.16.1.2
Supports IPv6 Address Family
Event-log enabled, Maximum number of events: 1000,
Mode: cyclic
It is an area border and autonomous system boundary
router
Redistributing External Routes from,
connected
[…]
Number of external LSA 1. Checksum Sum 0x0055EC
Number of areas in this router is 2. 2 normal 0 stub 0 nssa
Graceful restart helper support enabled
Reference bandwidth unit is 100 mbps
Area BACKBONE(0)
Number of interfaces in this area is 2
SPF algorithm executed 7 times
Number of LSA 8. Checksum Sum 0x03F283
Number of DCbitless LSA 0
Number of indication LSA 0
Number of DoNotAge LSA 0
Flood list length 0
Area 1
Number of 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
Lab 7 OSPFv3: Verification
10
107. R1
R1#sh ipv6 ospf
Routing Process "ospfv3 1" with ID 172.16.1.1
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 10000 msecs
Maximum wait time between two consecutive SPFs 10000 msecs
Minimum LSA interval 5 secs
Minimum LSA arrival 1000 msecs
LSA group pacing timer 240 secs
Interface flood pacing timer 33 msecs
Retransmission pacing timer 66 msecs
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
Lab 7 OSPFv3: Verification
107
108. R3
R3#sh ipv6 ospf
Routing Process "ospfv3 1" with ID 172.16.1.3
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 10000 msecs
Maximum wait time between two consecutive SPFs 10000
msecs
Minimum LSA interval 5 secs
Minimum LSA arrival 1000 msecs
LSA group pacing timer 240 secs
Interface flood pacing timer 33 msecs
Retransmission pacing timer 66 msecs
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
Lab 7 OSPFv3: Verification
108
109. Area 0
R2#sh ipv6 ospf data
OSPFv3 Router with ID (172.16.1.2) (Process ID 1)
Router Link States (Area 0)
ADV Router Age Seq# Fragment ID Link count Bits
172.16.1.1 968 0x80000002 0 1 None
172.16.1.2 967 0x80000002 0 1 B
Inter Area Prefix Link States (Area 0)
ADV Router Age Seq# Prefix
172.16.1.2 963 0x80000001 2001:DB8:172:17::2/127
Inter Area Router Link States (Area 0)
ADV Router Age Seq# Link ID Dest RtrID
172.16.1.2 814 0x80000001 2886729987 172.16.1.3
Link (Type-8) Link States (Area 0)
ADV Router Age Seq# Link ID Interface
172.16.1.1 967 0x80000002 6 Se1/0
172.16.1.2 964 0x80000002 6 Se1/0
Intra Area Prefix Link States (Area 0)
ADV Router Age Seq# Link ID Ref-lstype Ref-LSID
172.16.1.1 968 0x80000002 0 0x2001 0
172.16.1.2 967 0x80000002 0 0x2001 0
Lab 7 OSPFv3: Verification
109
110. R2 (continued..)
Router Link States (Area 1)
ADV Router Age Seq# Fragment ID Link count Bits
172.16.1.2 928 0x80000002 0 1 B
172.16.1.3 820 0x80000003 0 1 E
Net Link States (Area 1)
ADV Router Age Seq# Link ID Rtr count
172.16.1.3 929 0x80000001 2 2
Inter Area Prefix Link States (Area 1)
ADV Router Age Seq# Prefix
172.16.1.2 963 0x80000001 2001:DB8:172:16::1/128
172.16.1.2 963 0x80000001 2001:DB8:172:17::/127
172.16.1.2 963 0x80000001 2001:DB8:172:16::2/128
Link (Type-8) Link States (Area 1)
ADV Router Age Seq# Link ID Interface
172.16.1.2 968 0x80000002 2 Et0/0
172.16.1.3 968 0x80000002 2 Et0/0
Intra Area Prefix Link States (Area 1)
ADV Router Age Seq# Link ID Ref-lstype Ref-LSID
172.16.1.3 929 0x80000001 2048 0x2002 2
Type-5 AS External Link States
ADV Router Age Seq# Prefix
172.16.1.3 819 0x80000001 2001:DB8:35:1::16/127
172.16.1.3 819 0x80000001 2001:DB8:36:1::16/127
172.16.1.3 819 0x80000001 2001:DB8:172:16::3/128
Lab 7 OSPFv3: Verification
110
111. R5 & R6
R2#deb ipv6 ospf hello
OSPFv3 hello events debugging is on
19:02:20.240: OSPFv3: Send hello to FF02::5 area 1 on Ethernet0/0 from FE80::A8BB:CCFF:FE00:5200
interface ID 2
19:02:27.100: OSPFv3: Rcv hello from 172.16.1.3 area 1 from Ethernet0/0 FE80::A8BB:CCFF:FE00:5300
interface ID 2
19:02:27.100: OSPFv3: End of hello processing
19:02:28.840: OSPFv3: Send hello to FF02::5 area 0 on Serial1/0 from FE80::A8BB:CCFF:FE00:5200 interface
ID 6
19:02:28.920: OSPFv3: Rcv hello from 172.16.1.1 area 0 from Serial1/0 FE80::4AFF:FEA2:851 interface ID 6
19:02:28.920: OSPFv3: End of hello processing
R2#undeb all
All possible debugging has been turned off
Lab 7 OSPFv3: Debugs
111
114. 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
114
115. Lab 8 BGPv6: iBGP
• 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
115
118. R2
R2#sh bgp ipv6 unicast sum
BGP router identifier 172.16.1.2, local AS number 109
BGP table version is 4, main routing table version 4
1 network entries using 172 bytes of memory
1 path entries using 88 bytes of memory
1/1 BGP path/bestpath attribute entries using 128 bytes of memory
1 BGP AS-PATH entries using 24 bytes of memory
0 BGP route-map cache entries using 0 bytes of memory
0 BGP filter-list cache entries using 0 bytes of memory
BGP using 412 total bytes of memory
BGP activity 7/0 prefixes, 8/1 paths, scan interval 60 secs
Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down State/PfxRcd
2001:DB8:172:16::1
4 109 100 98 4 0 0 0 1:26:26 2
2001:DB8:172:16::3
4 109 95 98 4 0 0 0 1:24:10 0
R2#
Lab 8 BGPv6: iBGP Verification
118
119. R2
R2#sh bgp ipv6 unicast
BGP table version is 4, local router ID is 172.16.1.2
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, x best-external, f RT-Filter, a additional-path
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*>i 2004:DB8::1/128
2001:DB8:172:16::1
0 100 0 i
*>i 2001:DB8:1:41::/64
2001:DB8:172:16::1
0 100 0 ?
Lab 8 BGPv6: iBGP Verification
119
120. R2
R2#sh bgp ipv6 unicast 2001:db8:1:41::/64
BGP routing table entry for 2001:DB8:1:41::/64, version 29
Paths: (1 available, best #1, table default)
Advertised to update-groups:
2
Refresh Epoch 2
Local, (Received from a RR-client)
2001:DB8:172:16::1 (metric 64) from 2001:DB8:172:16::1 (172.16.1.1)
Origin incomplete, metric 0, localpref 100, valid, internal, best
Lab 8 BGPv6: iBGP Verification
120
121. 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
121
122. Lab 8 BGPv6: eBGP
• 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.
122
125. 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::17
4 1 11 16 26 0 0 00:05:42 2
2001:DB8:172:16::2
FE80::A01:2301%Tunnel0
4 1 11 18 26 0 0 00:05:56 2
Lab 8 BGPv6: eBGP Verification
125
126. R3
R3#sh bgp ipv6 unicast
BGP table version is 27, local router ID is 172.16.1.3
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, x best-external, f RT-Filter, a additional-path
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*>i 2001:DB8:1:41::/64
2001:DB8:172:16::1
0 100 0 ?
* 2001:DB8:1:56::/63
2001:DB8:36:1::17
0 0 1 i
*> FE80::A01:2301 0 0 1 i
* 2001:DB8:1:88::/64
2001:DB8:36:1::17
0 0 1 i
*> FE80::A01:2301 0 0 1 i
*>i 2004:DB8::1/128 2001:DB8:172:16::1
0 100 0 i
R3#
Lab 8 BGPv6: eBGP Verification
126
127. R3
R3#sh bgp ipv6 uni 2001:db8:1:56::/63
BGP routing table entry for 2001:DB8:1:56::/63, version 22
Paths: (2 available, best #2, table default)
Advertised to update-groups:
1 3
Refresh Epoch 1
1, (aggregated by 1 10.1.1.6)
2001:DB8:36:1::17 (FE80::A8BB:CCFF:FE00:5600) from 2001:DB8:36:1::17 (10.1.1.6)
Origin IGP, metric 0, localpref 100, valid, external, atomic-aggregate
Refresh Epoch 1
1, (aggregated by 1 10.1.1.5)
FE80::A01:2301 (FE80::A01:2301) from FE80::A01:2301%Tunnel0 (10.1.1.5)
Origin IGP, metric 0, localpref 100, valid, external, atomic-aggregate, best
R3#
Lab 8 BGPv6: eBGP Verification
127
128. 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#
Lab 8 BGPv6: eBGP Verification
128