Ipv6 Technology: Cisco Public

IPv6 Technology
RST-1300 12394_04_2006_c2
2006 Cisco Systems, Inc. All rights reserved.
Cisco Public
10
IPv6 Features
Larger address space enabling:
Global reachability, flexibility, aggregation, multihoming, autoconfiguration, plug and play and renumbering
Simpler header enabling:

Routing efficiency, performance and forwarding rate scalability
Improved option support Mandated security (global key yet to be defined) Transition richness
RST-1300 12394_04_2006_c2
Cisco Public
11
IPv4 and IPv6 Header Comparison

IPv4 Header
Version IHL Type of Service Total Length Flags Fragment Offset Version Identification Time to Live Protocol
IPv6 Header
Traffic Class Flow Label
Header Checksum
Payload Length
Next Header
Hop Limit
Source Address Destination Address Options Padding
Source Address
Legend
Fields Name Kept from IPv4 to IPv6 Fields Not Kept in IPv6 Name and Position Changed in IPv6 New Field in IPv6
Destination Address
RST-1300 12394_04_2006_c2
Cisco Public
12
IPv6 Header Format

Version Traffic Class Payload Length Flow Label Next Header Hop Limit
Source Address
40 octets
Destination Address
Next Header
Extension Header info
variable length
32 bits
RST-1300 12394_04_2006_c2 2006 Cisco Systems, Inc. All rights reserved.
Cisco Public
13
The Chain of Pointers Formed by the Next Header Field

IPv6 Header Next Header = 6 (TCP) TCP Segment
IPv6 Header Next Header = 43 (Routing)
Routing Header Next Header = 6 (TCP)
TCP Segment
IPv6 Header Next Header = 43 (Routing)
Routing Header Next Header = 51 (AH)
Authentication Header
TCP Segment
Next Header = 6 (TCP)
RST-1300 12394_04_2006_c2
Cisco Public
14
IPv6 Protocol
New field Flow label (RFC3697)
Sequence of packets for which a source desires to label a flow Flow classifiers have been based on 5-tuple: source/destination address, protocol type and port numbers of transport Some of these fields may be unavailable due to fragmentation, encryption or locating them past extension headers. In IPv6: Only 3 tuple, flow label, source/destination address
RST-1300 12394_04_2006_c2
Cisco Public
15
MTU Issues
Minimum link MTU for IPv6 is 1280 octets (vs. 68 octets for IPv4)
=> on links with MTU < 1280, link-specific fragmentation and reassembly must be used
Implementations are expected to perform path MTU discovery to send packets bigger than 1280 Minimal implementation can omit PMTU discovery as long as all packets kept 1280 octets A hop-by-hop option supports transmission of jumbograms with up to 232 octets of payload
RST-1300 12394_04_2006_c2
Cisco Public
16
Addressing
RST-1300 12394_04_2006_c2
Cisco Public
17
Larger Address Space

IPv4 = 32 Bits
IPv6 = 128 Bits
IPv4
32 bits =~ 4,200,000,000 possible addressable nodes
IPv6
128 bits = 340,282,366,920,938,463,463,374,607,431,768,211,456 nodes
RST-1300 12394_04_2006_c2
Cisco Public
18
Addressing
Representation
16-bit hexadecimal numbers Numbers are separated by (:) Hex numbers are not case sensitive Abbreviations are possible
Leading zeros in contiguous block could be represented by (::) Example: 2001:0db8:0000:130F:0000:0000:087C:140B 2001:0db8:0:130F::87C:140B Double colon only appears once in the address
RST-1300 12394_04_2006_c2
Cisco Public
19
Addressing
Prefix Representation
Representation of prefix is just like CIDR In this representation you attach the prefix length Like v4 address:
198.10.0.0/16
V6 address is represented the same way:

2001:db8:12::/40
RST-1300 12394_04_2006_c2
Cisco Public
20
IPv6Addressing Model
Addresses are assigned to interfaces
Change from IPv4 mode:
Interface expected to have multiple addresses Addresses have scope

Link Local Unique Local Global Global Unique Local Link Local
Addresses have lifetime

Valid and preferred lifetime
RST-1300 12394_04_2006_c2
Cisco Public
21
Addressing
Some special addresses
Type Binary Hex
Aggregatable Global Unicast Address Link Local Unicast Address Unique Local Unicast Address Multicast Address
0010 1111 1110 10 1111 1100 1111 1101 1111 1111
2 FE80::/10 FC00::/8 FD00::/8 FF00::/16
RST-1300 12394_04_2006_c2
Cisco Public
22
Types of IPv6 Addresses

Unicast
Address of a single interface. One-to-one delivery to single interface
Multicast
Address of a set of interfaces. One-to-many delivery to all interfaces in the set
Anycast
Address of a set of interfaces. One-to-one-of-many delivery to a single interface in the set that is closest
No more broadcast addresses
RST-1300 12394_04_2006_c2
Cisco Public
23
Aggregatable Global Unicast Addresses

Provider 3 45 Bits
Global Routing Prefix
001
Site 16 Bits
SLA
Host 64 Bits
Interface ID
Aggregatable Global Unicast Addresses Are:

Addresses for generic use of IPv6 Structured as a hierarchy to keep the aggregation
RST-1300 12394_04_2006_c2
Cisco Public
24
Hierarchical Addressing and Aggregation

Subnet Prefix 65,536 Subnets 2001:0DB8:0001:0002::/64 Site Prefix 65,536 Sites 2001:0DB8:0001::/48 ISP Prefix 512 ISPs 2001:0DB8::/32 2001 0DB8 0001 0002 Interface ID (64 Bits)
2001 0 0 0 0 1 1 0 1 1 0 1 1 1 0 0 0
Registry 2001:0C00::/23
Cisco Public
25
Hierarchical Addressing and Aggregation

Site 1 2001:DB8:0001:/48
2001:DB8:0001:0001:/64 2001:DB8:0001:0002:/64
Announces the /48 Prefix Announces the /64 Prefix
ISP 2001:DB8::/32
Announces the /32 Prefix
2001:DB8:0002:0001:/64 2001:DB8:0002:0002:/64
IPv6 Internet
Announces the /48 Prefix
2001::/16
Site 2 2001:DB8:0002:/48
RST-1300 12394_04_2006_c2
Cisco Public
26
IPv6 Interface Identifier

Lowest-Order 64-Bit Field of Unicast Address May Be Assigned in Several Different Ways:
Auto-configured from a 64-bit EUI-64, or expanded from a 48-bit MAC address (e.g. Ethernet address) Auto-generated pseudo-random number (to address privacy concerns) Assigned via DHCP Manually configured
RST-1300 12394_04_2006_c2
Cisco Public
27
IPv6 Interface Identifier

Cisco uses the EUI-64 format to do stateless autoconfiguration This format expands the 48 bit MAC address to 64 bits by inserting FFFE into the middle 16 bits To make sure that the chosen address is from a unique Ethernet MAC address, the universal/local (u bit) is set to 1 for global scope and 0 for local scope
RST-1300 12394_04_2006_c2
Cisco Public
28
IEEE EUI-64 Addresses

Extended Unique Identifier (EUI) Company ID - Extension ID U/L bit (u)
Universally (=0)/Locally (=1) Administered
U/G bit (g)

Unicast (=0)/Group (=1) Address
24 bits
40 bits
ccccccug cccccccc cccccccc

IEEE-administered company ID
RST-1300 12394_04_2006_c2
xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx

Manufacturer-selected extension ID
Cisco Public 29
Conversion of an IEEE 802 Address to an EUI-64 Address

IEEE-administered company ID
24 bits
Manufacturer-selected extension ID
24 bits
IEEE 802 Address
xxxxxxxx xxxxxxxx xxxxxxxx
11111111
11111110
xxxxxxxx xxxxxxxx xxxxxxxx
EUI-64 Address
0xFF
0xFE
RST-1300 12394_04_2006_c2
Cisco Public
30
Aggregatable Global Unicast Addresses
EUI-64
Ethernet MAC Address (48 Bits) 00
00 90
90 27
27
17
FC 17
0F FC 0F
FF 64-Bits Version Uniqueness of the MAC Eui-64 Address 00 90 27 FF
FE FE 17 FC 0F
000000U0 U=1 02 90
Where U= FF
1 = Unique 0 = Not Unique FE 17 FC 0F
27
Eui-64 address: Insert FFFE in middle Invert U bit to identify uniqueness of MAC
Cisco Public
31
Unique-Local
128 Bits Global ID 40 Bits
1111 110 FC00::/7
Interface ID Subnet ID 16 Bits
7 Bits
Unique-Local Addresses Used For:

Local communications Inter-site VPNs Not routable on the Internet
RST-1300 12394_04_2006_c2
Cisco Public
32
Link-Local
128 Bits Remaining 54 Bits
1111 1110 10 FE80::/10
Interface ID
10 Bits Link-Local Addresses Used For:

Mandatory Address for Communication between two IPv6 device (Like ARP but at Layer 3) Automatically assigned by Router as soon as IPv6 is enabled Also used for Next-Hop calculation in Routing Protocols Only Link Specific scope Remaining 54 bits could be Zero or any manual configured value
RST-1300 12394_04_2006_c2
Cisco Public
33
IPv6 Multicast Address

IP multicast address has a prefix FF00::/8 (1111 1111). The second octet defines the lifetime and scope of the multicast address.
8-bit 4-bit 4-bit 112-bit
1111 1111 Lifetime

0 1
Lifetime
Scope
Group-ID
Scope
If Permanent If Temporary
1 2 5 8 E
Node Link Site Organization Global

Cisco Public 34
RST-1300 12394_04_2006_c2
IPv6 Multicast Address

The multicast address AllSPFRouters is FF02::5 note that 02 means that this is a permanent address and has link scope The multicast address ALLDRouters is FF02::6
RST-1300 12394_04_2006_c2
Cisco Public
35
Solicited-Node Multicast Address

For each unicast and anycast address configured there is a corresponding solicited-node multicast This address is link local significance only This is specially used for two purpose, for the replacement of ARP, and DAD
RST-1300 12394_04_2006_c2
Cisco Public
36
Solicited-Node Multicast Address
Used in neighbor solicitation messages Multicast address with a link-local scope Solicited-node multicast consists of prefix + lower 24 bits from unicast, FF02::1:FF:
RST-1300 12394_04_2006_c2
Cisco Public
37
Router Interface
R1#sh ipv6 int e0 Ethernet0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::200:CFF:FE3A:8B18 No global unicast address is configured Joined group address(es): FF02::1 FF02::2 Solicited-Node Multicast Address FF02::1:FF3A:8B18 MTU is 1500 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ND DAD is enabled, number of DAD attempts: 1 ND reachable time is 30000 milliseconds ND advertised reachable time is 0 milliseconds ND advertised retransmit interval is 0 milliseconds ND router advertisements are sent every 200 seconds ND router advertisements live for 1800 seconds Hosts use stateless autoconfig for addresses. R1#
RST-1300 12394_04_2006_c2
Cisco Public
38
Anycast
Anycast Address Assignment
Routers along the path to the destination just process the packets based on network prefix Routers configured to respond to anycast packets will do so when they receive a packet send to the anycast address Anycast allows a source node to transmit IP datagrams to a single destination node out of a group destination nodes with same subnet id based on the routing metrics
RST-1300 12394_04_2006_c2
Cisco Public
39
ICMPv6 and Neighbor Discovery
RST-1300 12394_04_2006_c2
Cisco Public
40
ICMPv6
Internet Control Message Protocol version 6 RFC 2463 Modification of ICMP from IPv4 Message types are similar (but different types/codes)
Destination unreachable (type 1) Packet too big (type 2) Time exceeded (type 3) Parameter problem (type 4) Echo request/reply (type 128 and 129)
Cisco Public
41
ICMPv6 Message Fields

Typeidentifies the message or action needed Codeis a type-specific sub-identifier. For example, Destination Unreachable can mean no route, port unreachable, administratively prohibited, etc. Checksumcomputed over the entire ICMPv6 message Next Header value of 58
Neighbor Discovery
Replaces ARP, ICMP (redirects, router discovery) Reachability of neighbors Hosts use it to discover routers, auto configuration of addresses Duplicate Address Detection (DAD)
RST-1300 12394_04_2006_c2
Cisco Public
43
Neighbor Discovery
Neighbor discovery uses ICMPv6 messages, originated from node on link local with hop limit of 255 Consists of IPv6 header, ICMPv6 header, neighbor discovery header, and neighbor discovery options Five neighbor discovery messages
1. Router solicitation (ICMPv6 type 133) 2. Router advertisement (ICMPv6 type 134) 3. Neighbor solicitation (ICMPv6 type 135) 4. Neighbor advertisement (ICMPv6 type 136) 5. Redirect (ICMPV6 type 137)
Cisco Public
44
Neighbor Discovery
Router Solicitation
Host send to inquire about presence of a router on the link Send to all routers multicast address of FF02::2 (all routers multicast address) Source IP address is either link local address or unspecified IPv6 address (::)
RST-1300 12394_04_2006_c2
Cisco Public
45
Router Solicitation and Advertisement
1. RS
2. RA
1ICMP Type = 133 (RS) Src = link-local address (FE80::/10) Dst = all-routers multicast address (FF02::2) Query = please send RA
2ICMP Type = 134 (RA) Src = link-local address (FE80::/10) Dst = all-nodes multicast address (FF02::1) Data = options, subnet prefix, lifetime, autoconfig flag
Router solicitations (RS) are sent by booting nodes to request RAs for configuring the interfaces
Cisco Public
46
Neighbor Solicitation
Send to discover link layer address of IPv6 node For Layer 2 it is set to multicast for address resolution, unicast for node reachability IPv6 header, source address is set to unicast address of sending node, or :: for DAD Destination address is set to the unicast address for reachability and solicited node multicast for DAD
RST-1300 12394_04_2006_c2
Cisco Public
47
Neighbor Advertisement
Response to neighbor solicitation message Also send to inform change of link layer address
RST-1300 12394_04_2006_c2
Cisco Public
48
Neighbor Solicitation and Advertisement

A B
Neighbor Solicitation: ICMP type = 135 Src = A Dst = Solicited-node multicast address of B Neighbor Advertisement: Data = link-layer address of A ICMP type = 136 Query = what is your link-layer address? Src = B Dst = A Data = link-layer address of B A and B Can Now Exchange Packets on This Link
Cisco Public
49
Viewing Neighbors in the Cache
Neighbors are only considered reachable for 30-seconds. Stale indicates that, before we contact this neighbor, we will need to send a ND packet.
RST-1300 12394_04_2006_c2
Cisco Public
50
Redirect
A B R2
R1
Src = A Dst IP = 2001:db8:C18:2::1 Dst Ethernet = R2 (default router)
2001:db8:C18:2::/64
Redirect: Src = R2 Dst = A Data = good router = R1
Redirect is used by a router to signal the reroute of a packet to a better router

Cisco Public
51
Autoconfiguration
Mac Address: 00:2c:04:00:FE:56 Host Autoconfigured Address Is: Prefix Received + Link-Layer Address Sends Network-Type Information (Prefix, Default Route, )
Larger Address Space Enables:

The use of link-layer addresses inside the address space Autoconfiguration with no collisions Offers plug and play
Cisco Public
52
Renumbering
Mac Address: 00:2c:04:00:FE:56 Host Autoconfigured Address Is: New Prefix Received + Link-Layer Address Sends New Network-Type Information (Prefix, Default Route, )
Larger Address Space Enables:

Renumbering, using autoconfiguration and multiple addresses
RST-1300 12394_04_2006_c2
Cisco Public
53
IPv6 Configurations
RST-1300 12394_04_2006_c2
Cisco Public
54
IPv6 Configuration
In order to enable IPv6 the following global command should be entered
Router( config ) # ipv6 unicast-routing
To configure a global IPv6 or unique local IPv6 the following command should be entered
Router (config-if)# ipv6 address X:X::/prefix
Note that by configuring an IPV6 address you will have a global or unique-local IPv6 address and a link-local IPv6 address which is
FE80::interface-id
RST-1300 12394_04_2006_c2
Cisco Public
55
IPv6 Configuration
The local-link IPv6 address is constructed automatically by concatenating FE80 with Interface ID as soon as IPv6 is enabled on the interface either by assigning an IPv6 address or simply by entering the command
Router(config-if)# ipv6 enable
RST-1300 12394_04_2006_c2
Cisco Public
56
IPv6 Configuration
Router#conf t Router(config)#int fastEthernet 0/0 Router(config-if)#ipv6 enable Router#show ipv6 interface fastEthernet 0/0 FastEthernet0/0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::205:5FFF:FED3:6808 No global unicast address is configured Joined group address(es): FF02::1 FF02::2 FF02::1:FFD3:6808 M TU is 1500 bytes ICM P error m essages lim ited to one every 100 m illiseconds ICM P redirects are enabled ND DAD is enabled, num ber of DAD attem pts: 1 ND reachable tim e is 30000 m illiseconds ND advertised reachable tim e is 0 m illiseconds ND advertised retransm it interval is 0 m illiseconds ND router advertisem ents are sent every 200 seconds ND router advertisem ents live for 1800 seconds Hosts use stateless autoconfig for addresses.
RST-1300 12394_04_2006_c2
Cisco Public
57
IPv6 Configuration
R1E#sh ipv6 interface Ethernet0/0 is up, line protocol is up IPv6 is enabled, link-local address is FE80::A8BB:CCFF:FE00:1E00 Global unicast address(es): 2001:DB8::A8BB:CCFF:FE00:1E00, subnet is 2001:DB8::/64 [EUI] Joined group address(es): FF02::1 FF02::2 FF02::1:FF00:1E00 MTU is 1500 bytes ICMP error messages limited to one every 100 milliseconds ICMP redirects are enabled ND DAD is enabled, number of DAD attempts: 1 ND reachable time is 30000 milliseconds ND advertised reachable time is 0 milliseconds ND advertised retransmit interval is 0 milliseconds ND router advertisements are sent every 200 seconds ND router advertisements live for 1800 seconds Hosts use stateless autoconfig for addresses.
Cisco Public
58
Routing
RST-1300 12394_04_2006_c2
Cisco Public
62
Static Routing
RST-1300 12394_04_2006_c2
Cisco Public
63
Static Routing
ipv6 route ipv6-prefix/prefix-length {ipv6-address | interface-type interface-number} [administrativedistance]
Router(config)# ipv6 route 7fff::0/32 2001:1100:0:CC00::1 110
The following example routes packets for network 7fff::0/32 to a networking device at 2001:1100:0:CC00::1 with an administrative distance of 110:
RST-1300 12394_04_2006_c2
Cisco Public
64
Default Routing Example

Router2
IPv6 Internet
Ethernet0
Ethernet0 Router1 Ethernet1
LAN1: 2001:db8:c18:1::/64 LAN2: 2001:db8:c18:2::/64

ipv6 unicast-routing
interface Ethernet0 ipv6 address 2001:db8:c18:1::a/64 ipv6 nd prefix-advertisement 2001:db8:c18:1::/64 43200 43200 onlink autoconfig interface Ethernet1 ipv6 address 2001:db8:c18:2::a/64 ipv6 nd prefix-advertisement 2001:db8:c18:2::/64 43200 43200 onlink autoconfig ipv6 route ::/0 <address of R2 ethernet0>
Default Route to Router2

Cisco Public 65
RIPng (RFC 2080)
RST-1300 12394_04_2006_c2
Cisco Public
66
Enhanced Routing Protocol Support RIPng Overview

RIPng for IPv6, RFC 2080 Same as IPv4:
Distance-vector, radius of 15 hops, split-horizon and etc. Based on RIPv2
Updated features for IPv6

IPv6 prefix, next-hop IPv6 address Uses the multicast group FF02::9, the all-rip-routers multicast group, as the destination address for RIP updates Uses IPv6 for transport
RST-1300 12394_04_2006_c2
Cisco Public
67
Enhanced Routing Protocol Support RIPng Configuration and Display

::/0 Router 2 Ethernet0 = 2001:db8:c18:1:260:3eff:fe47:1530 LAN1: 2001:db8:c18:1::/64 Ethernet0 Router 1 Ethernet1 LAN2: 2001:db8:c18:2::/64
Router1# ipv6 router rip RT0 interface Ethernet0 ipv6 address 2001:db8:c18:1::/64 eui-64 ipv6 rip RT0 enable Interface Ethernet1 ipv6 address 2001:db8:c18:2::/64 eui-64 ipv6 rip RT0 enable Router2# ipv6 router rip RT0 interface Ethernet0 ipv6 address 2001:db8:c18:1::/64 eui-64 ipv6 rip RT0 enable ipv6 rip RT0 default-information originate
Router2# debug ipv6 rip RIPng: Sending multicast update on Ethernet0 for RT0 src=FE80::260:3eff:fe47:1530 dst=FF02::9 (Ethernet0) sport=521, dport=521, length=32 command=2, version=1, mbz=0, #rte=1 tag=0, metric=1, prefix=::/0
Multicast All RIP-Routers

Link-Local src Address

Cisco Public 68
Deployment
RST-1300 12394_04_2006_c2
Cisco Public
69
IPv4-IPv6 Transition/Coexistence
A wide range of techniques have been identified and implemented, basically falling into three categories:
1. Dual-stack techniques, to allow IPv4 and IPv6 to co-exist in the same devices and networks 2. Tunneling techniques, to avoid order dependencies when upgrading hosts, routers, or regions 3. Translation techniques, to allow IPv6-only devices to communicate with IPv4-only devices
Expect all of these to be used, in combination
RST-1300 12394_04_2006_c2
Cisco Public
70
Dual Stack Approach

Application IPv6-Enable Application
TCP
UDP
TCP
UDP
Preferred Method on Applications Servers Frame Protocol ID
IPv4
IPv6
IPv4
IPv6
0x0800
0x86dd
0x0800
0x86dd
Data Link (Ethernet)
Data Link (Ethernet)
Dual Stack Node Means:

Both IPv4 and IPv6 stacks enabled Applications can talk to both Choice of the IP version is based on name lookup and application preference
Cisco Public
71
Host Running Dual Stack
www.a.com =*? 2001:db8::1 10.1.1.1 DNS Server
IPv4
IPv6 2001:db8::1
In a Dual Stack Case, an Application that:

Is IPv4 and IPv6-enabled Asks the DNS for all types of addresses Chooses one address and, for example, connects to the IPv6 address
RST-1300 12394_04_2006_c2
Cisco Public
72
Cisco IOS Dual Stack Configuration

router# ipv6 unicast-routing
Dual-Stack Router IPv6 and IPv4 Network

IPv4: 192.168.99.1
interface Ethernet0 ip address 192.168.99.1 255.255.255.0 ipv6 address 2001:db8:213:1::/64 eui-64
IPv6: 2001:db8:213:1::/64 eui-64
Cisco IOS Is IPv6-Enable:

If IPv4 and IPv6 are configured on one interface, the router is dual-stacked Telnet, Ping, Traceroute, SSH, DNS client, TFTP, etc.
RST-1300 12394_04_2006_c2
Cisco Public
73
Tunneling
RST-1300 12394_04_2006_c2
Cisco Public
74
Tunneling
Many Ways to Do Tunneling
Some ideas same as before
GRE, MPLS, IP
Native IP over data link layers

ATM PVC, dWDM Lambda, Frame Relay PVC, Serial, Sonet/SDH, Ethernet
Some new techniques

Automatic tunnels using IPv4 , compatible IPv6 address, 6to4, ISATAP
RST-1300 12394_04_2006_c2
Cisco Public
75
Manually Configured GRE Tunnel Configuration

Dual-Stack Router1 IPv6 Network Dual-Stack Router2 IPv6 Network IPv4: 192.168.30.1 IPv6: 2001:db8:800:1::2
IPv4
IPv4: 192.168.99.1 IPv6: 2001:db8:800:1::3
router1# interface Tunnel0 ipv6 enable ipv6 address 2001:db8:c18:1::3/128 tunnel source 192.168.99.1 tunnel destination 192.168.30.1 tunnel mode gre ipv6
router2# interface Tunnel0 ipv6 enable ipv6 address 2001:db8:c18:1::2/128 tunnel source 192.168.30.1 tunnel destination 192.168.99.1 tunnel mode gre ipv6
RST-1300 12394_04_2006_c2
Cisco Public
76
IPv6 over IPv4 Tunnels

IPv6 Header Dual-Stack Host
IPv4
IPv6 Data IPv6 Host
Dual-Stack Router
IPv6 Network
Tunnel: IPv6 in IPv4 Packet IPv4 Header IPv6 Header IPv6 Data
Tunneling can be used by routers and hosts
RST-1300 12394_04_2006_c2
Cisco Public
77
Manually Configured Manual Tunnel Configuration

Dual-Stack Router1
IPv6 network
IPv4
Dual-Stack Router2
IPv6 network
IPv4: 192.168.99.1 IPv6: 2001:db8:800:1::3
IPv4: 192.168.30.1 IPv6: 2001:db8:800:1::2
router1# interface Tunnel0 ipv6 enable ipv6 address 2001:db8:c18:1::3/127 tunnel source 192.168.99.1 tunnel destination 192.168.30.1 tunnel mode ipv6ip
router2# interface Tunnel0 ipv6 enable ipv6 address 2001:db8:c18:1::2/127 tunnel source 192.168.30.1 tunnel destination 192.168.99.1 tunnel mode ipv6ip
RST-1300 12394_04_2006_c2
Cisco Public
78
Automatic 6to4 Tunnels

Automatic 6to4 tunnel allows isolated IPv6 domains to connect over an IPv4 network Unlike the manual 6to4 the tunnels are not point-topoint, they are multipoint tunnels IPv4 network is treated like a virtual NBMA network IPv4 is embedded in the IPv6 address is used to find the other end of the tunnel Address format is 2002:<IPv4 address>::
RST-1300 12394_04_2006_c2
Cisco Public
79
Automatic 6to4 Tunnel (RFC 3056)

IPv6 Host IPv6 Network Network Prefix: 2002:db8:6301::/48 = = 192.168.99.1 6to4 Router 6to4 Router IPv6 Host
IPv6 Network
IPv4
192.168.30.1
Network Prefix: 2002:db8:1e01::/48
6to4:
Is an automatic tunnel method Gives a prefix to the attached IPv6 network
2002
/16
RST-1300 12394_04_2006_c2
Public IPv4 Address

/48
SLA
/64
Interface ID
Cisco Public
80
Automatic 6to4 Tunnel (RFC 3056)

S=2002:db8:6301::1 D=2002:db8:1e01::2 S=2002:db8:6301::1 D=2002:db8:1e01::2
IPv6 Header IPv6 Host
IPv6 Data
6to4 Router
IPv6 Header 6to4 Router
IPv6 Data IPv6 Host
IPv6 Network
IPv4
IPv6 Network 192.168.30.1 2002:db8:1e01::2
2002:db8:6301::1
192.168.99.1 IPv6 Header
Tunnel: IPv6 in IPv4 Packet
IPv4 Header
IPv6 Data
S(v4)=192.168.99.1 D(v4)=192.168.30.1 S(v6)=2002:db8:6301::1 D(v6)=2002:db8:1e01::2

Cisco Public
81
Automatic 6to4 Configuration

6to4 Router1
IPv6 Network
Network Prefix: 2002:db8:6301::/48
E0
IPv4
6to4 Router2
E0
IPv6 Network Network Prefix: 2002:db8:1e01::/48
192.168.99.1
192.168.30.1
=
router1# interface Ethernet0 ipv6 address 2002:db8:6301:1::/64 eui-64 Interface Ethernet1 ip address 192.168.99.1 255.255.0.0 interface Tunnel0 ipv6 unnumbered Ethernet0 tunnel source Ethernet1 tunnel mode ipv6ip 6to4 ipv6 route 2002::/16 Tunnel0
=
router2# interface Ethernet0 ipv6 address 2002:db8:1e01:1::/64 eui-64 Interface Ethernet1 ip address 192.168.30.1 255.255.0.0 interface Tunnel0 ipv6 unnumbered Ethernet0 tunnel source Ethernet1 tunnel mode ipv6ip 6to4 ipv6 route 2002::/16 Tunnel0
RST-1300 12394_04_2006_c2
Cisco Public
82
Automatic 6to4 Relay

IPv6 Internet
6to4 Router1
IPv6 Network
IPv4
6to4 Relay
IPv6 Site Network
192.168.99.1
192.168.30.1
Network Prefix: 2002:db8:1e01::/48
6to4 Relay:
Is a gateway to the rest of the IPv6 Internet Is a default router
RST-1300 12394_04_2006_c2
Cisco Public
83
Automatic 6to4 Relay Configuration

6to4 Router1
IPv6 Network
E0
IPv4
6to4 Relay
IPv6 Internet
IPv6 Network
192.168.99.1 =
IPv6 Address: 2002:db8:1e01::1
router1# interface Ethernet0 ipv6 address 2002:db8:6301:1::/64 eui-64 Interface Ethernet1 ip address 192.168.99.1 255.255.0.0 interface Tunnel0 no ip address ipv6 unnumbered Ethernet0 tunnel source Ethernet1 tunnel mode ipv6ip 6to4 ipv6 route 2002::/16 Tunnel0 ipv6 route ::/0 2001:db8:1e01::1
RST-1300 12394_04_2006_c2
Cisco Public
84
Automatic 6to4 Tunnels

Requirements for 6to4
Border router must be dual stack with a global IPv4 address Interior routing protocol for IPv6 is required DNS for IPv6
RST-1300 12394_04_2006_c2
Cisco Public
85
Intrasite Automatic Tunnel Address Protocol

RFC 4214 This is for enterprise networks such as corporate and academic networks Scalable approach for incremental deployment ISATAP makes your IPv4 infratructure as transport (NBMA) network
RST-1300 12394_04_2006_c2
Cisco Public
86

To deploy a router is identified that carries ISATAP services ISATAP routers need to have at least one IPv4 interface and 0 or more IPv6 interface DNS entries are created for each of the ISATAP routers IPv4 addresses Hosts will automatically discover ISATAP routers and can get access to global IPv6 network Host can apply the ISATAP service before all this operation but there interface will only have a link local v6 address until the first router appears
Cisco Public
87

Use IANAs OUI 00-00-5E and Encode IPv4 Address as Part of EUI-64
64-bit Unicast Prefix 0000:5EFE:
32-bit
IPv4 Address
32-bit
Interface Identifier (64 bits)
ISATAP is used to tunnel IPv4 within as administrative domain (a site) to create a virtual IPv6 network over a IPv4 network Supported in Windows XP Pro SP1 and others
RST-1300 12394_04_2006_c2
Cisco Public
88
Automatic Advertisement of ISATAP Prefix

ISATAP Host A
IPv4 Network
ISATAP Tunnel
ISATAP Router 1 E0
IPv6 Network
ICMPv6 Type 133 (RS) IPv4 Source: 206.123.20.100 IPv4 Destination: 206.123.31.200 IPv6 Source: fe80::5efe:ce7b:1464 IPv6 Destination: fe80::5efe:ce7b:1fc8 Send me ISATAP Prefix
ICMPv6 Type 134 (RA) IPv4 Source: 206.123.31.200 IPv4 Destination: 206.123.20.100 IPv6 Source: fe80::5efe:ce7b:1fc8 IPv6 Destination: fe80::5efe:ce7b:1464 ISATAP Prefix: 2001:db8:ffff :2::/64
RST-1300 12394_04_2006_c2
Cisco Public
89
Automatic Address Assignment of Host and Router

ISATAP Host A
IPv4 Network
ISATAP Tunnel
ISATAP Router 1 E0
IPv6 Network
206.123.20.100 fe80::5efe:ce7b:1464 2001:db8:ffff:2::5efe:ce7b:1464
206.123.31.200 fe80::5efe:ce7b:1fc8 2001:db8:ffff:2::5efe:ce7b:1fc8
ISATAP host A receives the ISATAP prefix 2001:db8:ffff:2::/64 from ISATAP Router 1 When ISATAP host A wants to send IPv6 packets to 2001:db8:ffff:2::5efe:ce7b:1fc8, ISATAP host A encapsulates IPv6 packets in IPv4. The IPv4 packets of the IPv6 encapsulated packets use IPv4 source and destination address.
RST-1300 12394_04_2006_c2
Cisco Public
90
Automatic Configuring ISATAP

ISATAP Host A IPv4 Network
ISATAP Tunnel 206.123.20.100 fe80::5efe:ce7b:1464 2001:db8:ffff:2::5efe:ce7b:1464
ISATAP-router1# ! interface Ethernet0 ip address 206.123.31.200 255.255.255.0 ! interface Tunnel0 ipv6 address 2001:db8:ffff:2::/64 eui-64 no ipv6 nd suppress-ra tunnel source Ethernet0 tunnel mode ipv6ip isatap
ISATAP Router 1 E0
IPv6 Network
206.123.31.200 fe80::5efe:ce7b:1fc8 2001:db8:ffff:2::5efe:ce7b:1fc8

The tunnel source command must point to an interface with an IPv4 address configured Configure the ISATAP IPv6 address, and prefixes to be advertised just as you would with a native IPv6 interface The IPv6 address has to be configured as an EUI-64 address since the last 32 bits in the interface identifier is used as the IPv4 destination address
RST-1300 12394_04_2006_c2
Cisco Public
91
IPv6 MULTICAST
RST-2300 12443_04_2006_X2
Cisco Public
66
IPv4 and IPv6 Multicast Comparison
Service Addressing Range
IPv4 Solution 32-bit, Class D Protocol Independent, All IGPs and MBGP PIM-DM, PIM-SM, PIM-SSM, PIM-bidir, PIM-BSR IGMPv1, v2, v3 Boundary, Border
IPv6 Solution 128-bit (112-bit Group) Protocol Independent, All IGPs and MBGP with v6 mcast SAFI PIM-SM, PIM-SSM, PIM-bidir, PIM-BSR MLDv1, v2 Scope Identifier
Routing
Forwarding
Group Management Domain Control Interdomain Solutions

RST-2300 12443_04_2006_X2
MSDP Across Single RP Within Globally Independent PIM Domains Shared Domains
Cisco Public
67
IPv6 Multicast Addresses (RFC 3513)

128 bits Group ID (112 bits)
1111 1111
Flags P T Scope
FLAGS =
F 8 bits
T or Lifetime, 0 if Permanent, 1 if Temporary P Proposed for Unicast-Based Assignments Others Are Undefined and Must Be Zero 1 = Interface-local 2 = Link 4 = Admin-local 5 = Site-local 8 = Organization E = Global
8 bits
SCOPE =
RST-2300 12443_04_2006_X2
Cisco Public
68
IPv6 Unicast-Based Multicast Addresses (RFC3306)

Solves the old IPv4 address assignment problem: How can I get global IPv4 multicast addresses? In IPv6, if you own an IPv6 unicast address prefix you implicitly own an RFC3306 IPv6 multicast address prefix:
64
32
FF | Flags| Scope |Rsvd| Plen | Network Prefix | Group ID
FF3E:0040:2001:0DB8:C003:1109:0000:1111
3 hex Uni-pfx E hex Global
RST-2300 12443_04_2006_X2
40 hex Prefix=64 Flags = 00PT, P = 1, T = 1=> Unicast-based address (0011 = 3)

Cisco Public
69
Multicast Listener Discovery: MLD

Multicast Host Membership Control
MLD is equivalent to IGMP in IPv4 MLD messages are transported over ICMPv6 MLD uses link local source addresses MLD packets use Router Alert in extension header (RFC2711) Version number confusion:
MLDv1 (RFC2710) like IGMPv2 (RFC2236) MLDv2 (RFC3810) like IGMPv3 (RFC3376)
Host Multicast Control via MLD
Only MIB available today is for MLDv1 MLD snooping
RST-2300 12443_04_2006_X2
Cisco Public
70
Multicast Interdomain Options

With and Without Rendezvous Points (RP)
SSM, No RPs R
DR
ASM Across Multiple Separate PIM Domains, Each With RP, MSDP Peering
R
DR RP RP RP
ASM Across Single Shared PIM Domain, One RP S

DR RP
RST-2300 12443_04_2006_X2
Cisco Public
71
SSM-Mapping
Delay in SSM deployment (both IPv4 and IPv6) is based mainly on lack of IGMPv3 and MLDv2 availability on the endpoints SSM-Mapping allows for the deployment of SSM in the network infrastructure without requiring MLDv2 (for IPv6) on the endpoint SSM-Mapping enabled router will map MLDv1 reports to a source (which do not natively include the source like with MLDv2)
Range of groups can be statically defined or used with DNS Wildcards can be used to define range of groups
RST-2300 12443_04_2006_X2 2005 Cisco Systems, Inc. All rights reserved.
Cisco Public
73
SSM-Mapping
core-1#show ipv6 mroute | begin 2001:DB8:CAFE:11::11 (2001:DB8:CAFE:11::11, FF33::DEAD), 00:01:20/00:03:06, flags: sT Incoming interface: GigabitEthernet3/3 RPF nbr: FE80::20E:39FF:FEAD:9B00 Immediate Outgoing interface list: GigabitEthernet5/1, Forward, 00:01:20/00:03:06 2001:DB8:CAFE:11::11 FF33::DEAD
Corporate Network
Source
Static Mapping:
ipv6 multicast-routing ! ipv6 mld ssm-map enable ipv6 mld ssm-map static MAP 2001:DB8:CAFE:11::11 no ipv6 mld ssm-map query dns ! ipv6 access-list MAP permit ipv6 any host FF33::DEAD
SSM
DNS Mapping (the default):

ipv6 multicast-routing ! ipv6 mld ssm-map enable ! ip domain multicast ssm-map.cisco.com ip name-server 10.1.1.1
RST-2300 12443_04_2006_X2 2005 Cisco Systems, Inc. All rights reserved.
MLDv1
Cisco Public
74
Rendezvous Point (RP) Deployment Types

Static RP
For PIM-SM and Bidir-PIM Provides group-to-RP mapping, no RP redundancy (yet)
Boot Strap Router (BSR)

Provides group-to-RP mapping AND RP redundancy
Embedded-RP
Easy to deploy Group-to-RP mapping only, no RP redundancy (yet) PIM-SM only (today), no Bidir-PIM
RST-2300 12443_04_2006_X2
Cisco Public
75
IPv6 Multicast Static RP

Easier than before as PIM is auto-enabled on every interface
Source ipv6 multicast-routing ! interface Loopback0 description IPV6 IPmc RP no ip address ipv6 address 2001:DB8:C003:110A::1/64 ! ipv6 pim rp-address 2001:DB8:C003:110A::1/64 ipv6 multicast-routing ! ipv6 pim rp-address 2001:DB8:C003:110A::1/64
L0
Corporate Network
RP IP WAN
RST-2300 12443_04_2006_X2
Cisco Public
76
Embedded-RP Addressing Overview

RFC 3956 Relies on a subset of RFC3306IPv6 unicastprefix-based multicast group addresses with special encoding rules:
Group address carries the RP address for the group! 8 4 4 4 4 8 64 32
FF | Flags| Scope |Rsvd | RPaddr| Plen | Network Prefix | Group ID New Address format defined : Flags = 0RPT, R = 1, P = 1, T = 1=> RP address embedded (0111 = 7) Example Group: FF7E:0140:2001:0DB8:C003:111D:0000:1112 Embedded RP: 2001:0DB8:C003:111D::1
RST-2300 12443_04_2006_X2
Cisco Public
77
Embedded-RP
PIM-SM protocol operations with embedded-RP: Intradomain transition into embedded-RP is easy: Non-supporting routers simply need to be configured statically or via BSR for the embedded-RPs! Embedded-RP is just a method to learn ONE RP address for a multicast group: It can not replace RP-redundancy as possible with BSR or MSDP/Anycast-RP Embedded-RP does not (yet) support Bidir-PIM
Embedded-RP Configuration Example

RP to be used as an Embedded-RP needs to be configured with address/group range All other non-RP routers require no special configuration
Corporate Network
Source
L0
RP
IP WAN
ipv6 pim rp-address 2001:DB8:C003:111D::1 ERP ! ipv6 access-list ERP permit ipv6 any FF7E:140:2001:DB8:C003:111D::/96
RST-2300 12443_04_2006_X2
Cisco Public
79
Using IPv6 with OSPF and EIGRP
OSPF Version 3 (OSPFv3) (RFC 2740)

Similar to IPv4
Same mechanisms, but a major rewrite of the internals of the protocol
Updated features for IPv6

Every IPv4-specific semantic removed Carry IPv6 addresses Link-local addresses used as source IPv6 transport OSPF for IPv6 currently an IETF proposed standard
OSPFv3Hierarchical Structure
Topology of an area is invisible from outside of the area: LSA flooding is bounded by area. SPF calculation is performed separately for each area. Backbones must be contiguous. All areas must have a connection to the backbone: Otherwise a virtual link must be used to connect to the backbone.
OSPFv3Similarities with OSPFv2

OSPFv3 is OSPF for IPv6 (RFC 2740) Based on OSPFv2, with enhancements Distributes IPv6 prefixes Runs directly over IPv6 OSPFv3 and OSPFv2 can be run concurrently, because each address family has a separate SPF (ships in the night). OSPFv3 uses the same basic packet types as OSPFv2: Hello Database description (DBD) Link state request (LSR) Link state update (LSU) Link state acknowledgment (ACK)
OSPFv3Similarities with OSPFv2

Neighbor discovery and adjacency formation mechanism are identical. RFC-compliant NBMA and point-to-multipoint topology modes are supported. Also supports other modes from Cisco, such as point-to-point and broadcast, including the interface. LSA flooding and aging mechanisms are identical.
Enhanced Routing Protocol Support Differences from OSPFv2

OSPF packet type OSPFv3 has the same five packet types, but some fields have been changed.
All OSPFv3 packets have a 16-byte header vs. the 24-byte header in OSPFv2.
OSPFv3 Differences from OSPFv2

OSPFv3 protocol processing is per link, not per subnet
IPv6 connects interfaces to links. Multiple IPv6 subnets can be assigned to a single link. Two nodes can talk directly over a single link, even though they do not share a common subnet. The terms network and subnet are being replaced with link. An OSPF interface now connects to a link instead of to a subnet.
OSPFv3 Differences from OSPFv2 (Cont.)

Multiple OSPFv3 protocol instances can now run over a single link
This structure allows separate autonomous systems, each running OSPF, to use a common link. A single link could belong to multiple areas. Instance ID is a new field that is used to allow multiple OSPFv3 protocol instances per link. In order to have two instances talk to each other, they need to have the same instance ID. By default, it is 0, and for any additional instance it is increased.
OSPFv3 Differences from OSPFv2 (Cont.)

Multicast addresses:
FF02::5Represents all SPF routers on the link-local scope; equivalent to 224.0.0.5 in OSPFv2 FF02::6Represents all DR routers on the link-local scope; equivalent to 224.0.0.6 in OSPFv2
Removal of address semantics

IPv6 addresses are no longer present in OSPF packet header (part of payload information). Router LSA and network LSA do not carry IPv6 addresses. Router ID, area ID, and link-state ID remain at 32 bits. DR and BDR are now identified by their router ID and not by their IP address.
Security
OSPFv3 uses IPv6 AH and ESP extension headers instead of variety of the mechanisms defined in OSPFv2.
LSA Overview
LSA Function Code Router LSA Network LSA Interarea prefix LSA Interarea router LSA AS external LSA Group membership LSA Type 7 LSA Link-LSA Intra-area prefix LSA 1 2 3 4 5 6 7 8 9
LSA Type 0x2001 0x2002 0x2003 0x2004 0x2005 0x2006 0x2007 0x2008 0x2009
Larger Address Space Enables Address Aggregation
Aggregation of prefixes announced in the global routing table Efficient and scalable routing Improved bandwidth and functionality for user traffic
Configuring OSPFv3 in Cisco IOS Software

Similar to OSPFv2 Prefixes existing interface and EXEC mode commands with ipv6 Interfaces configured directly Replaces network command Native IPv6 router mode Not a submode of router ospf command
Enabling OSPFv3 Globally
ipv6 unicast-routing ! ipv6 router ospf 1 router-id 2.2.2.2
Enabling OSPFv3 on an Interface
interface Ethernet0/0 ipv6 address 3FFE:FFFF:1::1/64 ipv6 ospf 1 area 0 ipv6 ospf priority 20 ipv6 ospf cost 20
Cisco IOS OSPFv3-Specific Attributes

Configuring area range: area area-id range prefix/prefix length [advertise | notadvertise] [cost cost] Showing new LSAs: show ipv6 ospf [process-id] database link show ipv6 ospf [process-id] database prefix
OSPFv3 Configuration Example

Router1# interface S1/1 ipv6 address 2001:410:FFFF:1::1/64 ipv6 ospf 100 area 0 interface S2/0 ipv6 address 3FFE:B00:FFFF:1::2/64 ipv6 ospf 100 area 1 ipv6 router ospf 100 router-id 10.1.1.3
Router2# interface S3/0 ipv6 address 3FFE:B00:FFFF:1::1/64 ipv6 ospf 100 area 1 ipv6 router ospf 100 router-id 10.1.1.4
Verifying Cisco IOS OSPFv3

Router2#show ipv6 ospf int s 3/0 S3/0 is up, line protocol is up Link Local Address 3FFE:B00:FFFF:1::1, Interface ID 7 Area 1, Process ID 100, Instance ID 0, Router ID 10.1.1.4 Network Type POINT_TO_POINT, Cost: 1 Transmit Delay is 1 sec, State POINT_TO_POINT, Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5 Hello due in 00:00:02 Index 1/1/1, flood queue length 0 Next 0x0(0)/0x0(0)/0x0(0) Last flood scan length is 3, maximum is 3 Last flood scan time is 0 msec, maximum is 0 msec Neighbor Count is 1, Adjacent neighbor count is 1 Adjacent with neighbor 10.1.1.3 Suppress hello for 0 neighbor(s)
show ipv6 ospf
R7#show ipv6 ospf Routing Process ospfv3 1 with ID 75.0.7.1 It is an area border and autonomous system boundary router Redistributing External Routes from, connected SPF schedule delay 5 secs, Hold time between two SPFs 10 secs Minimum LSA interval 5 secs. Minimum LSA arrival 1 secs LSA group pacing timer 240 secs Interface floor pacing timer 33 msecs Retransmission pacing timer 33 msecs Number of external LSA 3. Checksum Sum 0x12B75
show ipv6 ospf (Cont.)

Number of areas in this router is 2. 1 normal 0 stub 1 nssa Area BACKBONE(0) Number of interfaces in this area is 1 SPF algorithm executed 23 times Number of LSA 14. Checksum Sum 0x760AA Number of DCbitless LSA 0 Number of Indication LSA 0 Number of DoNotAge LSA 0 Flood list length 0 Area 2 Number of interfaces in this area is 1 It is a NSSA area Perform type-7/type-5 LSA translation SPF algorithm executed 17 times Number of LSA 25. Checksum Sum 0xE3BF0 Number of DCbitless LSA 0 Number of Indication LSA 0 Number of DoNotAge LSA 0 Flood list length 0
show ipv6 ospf neighbor detail
Router2#show ipv6 ospf neighbor detail Neighbor 10.1.1.3 In the area 0 via interface S2/0 Neighbor: interface-id 14, link-local address 3FFE:B00:FFFF:1::2 Neighbor priority is 1, State is FULL, 6 state changes Options is 0x63AD1B0D Dead timer due in 00:00:33 Neighbor is up for 00:48:56 Index 1/1/1, retransmission queue length 0, number of retransmission 1 First 0x0(0)/0x0(0)/0x0(0) Next 0x0(0)/0x0(0)/0x0(0) Last retransmission scan length is 1, maximum is 1 Last retransmission scan time is 0 msec, maximum is 0 msec
show ipv6 ospf database

Router Link States (Area 1) ADV Router 26.50.0.1 26.50.0.2 Age 1812 1901 Seq# 0x80000048 0x80000006 Fragment ID 0 0 Link count 1 1 Bits None B
Net Link States (Area 1) ADV Router 26.50.0.1 Age 57 Seq# 0x8000003B Link ID 3 Rtr count 4
Inter-Area Prefix Link States (Area 1) ADV Router 26.50.0.2 26.50.0.2 Age 139 719 Seq# 0x80000003 0x80000001 Prefix 3FFE:FFFF:26::/64 3FFE:FFF:26::/64
Inter-Area Router Link States (Area 1) ADV Router 26.50.0.2 26.50.0.4 Age 772 5 Seq# 0x80000001 0x80000003 Link ID 1207959556 1258292993 Dest RtrID 72.0.0.4 75.0.7.1
show ipv6 ospf database (Cont.)

Link (Type-8) Link States (Area 1) ADV Router 26.50.0.1 26.50.0.2 Age 1412 238 Seq# 0x80000031 0x80000003 Link ID 3 3 Interface Fa0/0 Fa0/0
Intra-Area Prefix Link States (Area 1) ADV Router 26.50.0.1 26.50.0.1 26.50.0.2 Age 1691 702 1797 Seq# Link ID 0x8000002E 0 0x80000031 1003 0x80000002 0 Ref-Istype 0x2001 0x2002 0x2001 Ref-LSID 0 3 0
Type-5 AS External Link States ADV Router 72.0.0.4 72.0.0.4 75.0.7.1 Age 287 38 162 Seq# 0x80000028 0x80000027 0x80000007 Prefix 3FFE:FFFF:A::/64 3FFE:FFFF:78::/64 3FFE:FFFF:8::/64
show ipv6 ospf database database-summary

R3#show ipv6 ospf database database-summary Area 0 database summary LSA Type Count Delete Router 3 0 Network 0 0 Link 3 0 Prefix 3 0 Inter-area Prefix 6 0 Inter-area Router 0 0 Type-7 External 0 0 Subtotal 15 0 Process 1 database summary LSA Type Count Router 7 Network 1 Link 7 Prefix 8 Inter-area Prefix 14 Inter-area Router 2 Type-7 External 0 Type-5 Ext 3 Total 42 Maxage 0 0 0 0 0 0 0 0
Delete 0 0 0 0 0 0 0 0 0
Maxage 0 0 0 0 0 0 0 0 0
EIGRP for IPv6

EIGRP for IPv6 is directly configured on the interfaces over which it runs. There is no network statement in EIGRP for IPv6. An EIGRP for IPv6 protocol instance requires a router ID before it can start running. EIGRP for IPv6 has a shutdown feature. The routing process should be in no shutdown mode in order to start running. When a user uses passive-interface configuration, EIGRP for IPv6 does not need to be configured on the interface that is made passive.
Cisco EIGRP for IPv6 Implementation

Increased network widththe largest possible width is 224 hops. Fast convergenceThe DUAL algorithm allows routing information to converge as quickly as any other routing protocol Partial updates Neighbor discovery mechanism Arbitrary route summarization ScalingEIGRP scales to large networks.
EIGRP has the following four basic components:

Neighbor discovery - EIGRP neighbor discovery is achieved with low overhead by periodically sending small hello packets. As long as hello packets are received, the Cisco IOS software can determine that a neighbor is alive and functioning. Reliable transport protocol - The reliable transport protocol is responsible for guaranteed, ordered delivery of EIGRP packets to all neighbors. DUAL finite state machine - The DUAL finite state machine embodies the decision process for all route computations. Protocol-dependent modules - The protocol-dependent modules are responsible for network layer protocol-specific tasks. An example is the EIGRP module, which is responsible for sending and receiving EIGRP packets that are encapsulated in IPv4 or IPv6.
Enabling EIGRP for IPv6
ipv6 unicast-routing ! ipv6 router eigrp 1 router-id 2.2.2.2
Enabling EIGRP on an Interface
interface Ethernet0/0 ipv6 enable ipv6 address 3FFE:FFFF:1::1/64 ipv6 eigrp 1
Configuring the Percentage of Link Bandwidth Used

Configuring bandwidth: Router(config-if)# bandwidth kbps Configuring the Percentage of Link Bandwidth Used: Router(config-if)# ipv6 bandwidth-percent eigrp as-number percent
Configuring Other features

Configuring Summary Aggregate Addresses: Router(config-if)# ipv6 summary-address eigrp as-number ipv6-address [admin-distance] Adjusting the timers in EIGRP for IPv6 Router(config-if)#ipv6 hello-interval eigrp as-number seconds Router(config-if)#ipv6 hold-time eigrp as-number seconds Disabling Split Horizon in EIGRP for IPv6 Router(config-if)# no ipv6 split-horizon eigrp as-number Configuring a Router for EIGRP Stub Routing Router(config-router)# stub [receive-only | connected | static |summary | redistributed]
RST-1300 12394_04_2006_c2
Cisco Public
97

Ipv6 Technology: Cisco Public

Uploaded by

Copyright:

Available Formats

Ipv6 Technology: Cisco Public

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ipv6 Technology: Cisco Public

Uploaded by

Copyright:

Available Formats

IPv6 Technology

2006 Cisco Systems, Inc. All rights reserved.

Simpler header enabling:

2006 Cisco Systems, Inc. All rights reserved.

IPv4 and IPv6 Header Comparison

Source Address Destination Address Options Padding

2006 Cisco Systems, Inc. All rights reserved.

IPv6 Header Format

Extension Header info

The Chain of Pointers Formed by the Next Header Field

IPv6 Header Next Header = 43 (Routing)

Routing Header Next Header = 6 (TCP)

IPv6 Header Next Header = 43 (Routing)

Routing Header Next Header = 51 (AH)

Next Header = 6 (TCP)

2006 Cisco Systems, Inc. All rights reserved.

2006 Cisco Systems, Inc. All rights reserved.

2006 Cisco Systems, Inc. All rights reserved.

2006 Cisco Systems, Inc. All rights reserved.

Larger Address Space

IPv6 = 128 Bits

2006 Cisco Systems, Inc. All rights reserved.

2006 Cisco Systems, Inc. All rights reserved.

V6 address is represented the same way:

2006 Cisco Systems, Inc. All rights reserved.

Interface expected to have multiple addresses Addresses have scope

Addresses have lifetime

2006 Cisco Systems, Inc. All rights reserved.

0010 1111 1110 10 1111 1100 1111 1101 1111 1111

2 FE80::/10 FC00::/8 FD00::/8 FF00::/16

2006 Cisco Systems, Inc. All rights reserved.

Types of IPv6 Addresses

No more broadcast addresses

2006 Cisco Systems, Inc. All rights reserved.

Aggregatable Global Unicast Addresses

Aggregatable Global Unicast Addresses Are:

2006 Cisco Systems, Inc. All rights reserved.

Hierarchical Addressing and Aggregation

Hierarchical Addressing and Aggregation

Announces the /48 Prefix Announces the /64 Prefix

Announces the /32 Prefix

2006 Cisco Systems, Inc. All rights reserved.

IPv6 Interface Identifier

2006 Cisco Systems, Inc. All rights reserved.

IPv6 Interface Identifier

2006 Cisco Systems, Inc. All rights reserved.

IEEE EUI-64 Addresses

U/G bit (g)

ccccccug cccccccc cccccccc

xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx xxxxxxxx

2006 Cisco Systems, Inc. All rights reserved.

Conversion of an IEEE 802 Address to an EUI-64 Address

IEEE 802 Address

ccccccug cccccccc cccccccc

xxxxxxxx xxxxxxxx xxxxxxxx

ccccccug cccccccc cccccccc

xxxxxxxx xxxxxxxx xxxxxxxx

2006 Cisco Systems, Inc. All rights reserved.

Aggregatable Global Unicast Addresses