IPv 6

COPYRIGHT INFORMATION
This publication, CCNA LAB WORKBOOK, was developed by Mohamed Ouamer. All rights
reserved. No part of this publication may be reproduced or distributed in any form or by any
means without the prior written permission of Mohamed Ouamer.
Cisco®, Cisco Systems®, CCDA®, CCNA®, CCDP®, CCNP®, CCIE®, CCSI®, the Cisco
Systems logo and the CCIE logo are trademarks or registered trademarks of Cisco Systems,
Inc. in the United States and certain other countries. All other trademarks are trademarks of
their respective owners.
If you have questions or concerns about our Copyright information, please email us at
contact@networkexperttraining.com.
DISCLAIMER
The following publication, CCNA LAB WORKBOOK, is developed to assist candidates in the
preparation for Cisco Systems’ CCNA exam.
While every effort has been made to ensure that all material is as complete and accurate as
possible, the enclosed material is presented on an “as is” basis. Neither the authors nor
networkexperttraining.com assume any liability or responsibility to any person or entity with
respect to loss or damages incurred from the information contained in this workbook.
If you have questions or concerns about our disclaimer, please email us at

contact@networkexperttraining.com.
ERRATA
Although we have taken every care to ensure the accuracy of our contents, mistakes do
happen. If you find a mistake in this workbook—maybe a mistake in text or configuration—we
would be grateful if you would report this to us. By doing this you can save other readers from
frustration, and help to improve subsequent versions of this workbook. If you find any errata,
report them by contacting us at support@networkexperttraning.com. Once your errata have
been verified, your submission will be accepted and the errata added to the list of existing
errata. . The existing errata can be requested by by contacting us at
support@networkexperttraning.com.
TABLE OF CONTENTS:
BASIC IPV6 ADDRESSING CONFIGURATION……….…………………………………………….. 4

RIPNG..…………………………………..……………………………………………………….. 15
RIPNG OVER FRAME RELAY…….……………………………………………………………….. 28
6TO4 TUNNELING……………..………………………………………...………………………… 43
CCNA LAB WORKBOOK INTERNET PROTOCOL V6
LAB 1: BASIC IPV6 ADDRESSING CONFIGURATION
I. Network diagram:
COPYRIGHT © 2009 MOHAMED OUAMER. ALL RIGHTS RESERVED
HTTP://WWW.NETWORKEXPERTTRAINING.COM
PAGE 1/11
II. Initial Configuration:

R1:
hostname R1
!
!
line con 0
exec-timeout 0 0
logging synchronous
!
line vty 0 4
exec-timeout 0 0
logging synchronous
password cisco
login
!
!
end
R2:
hostname R2
!
line con 0
exec-timeout 0 0
logging synchronous
!
line vty 0 4
exec-timeout 0 0
logging synchronous
password cisco
login
!
!
end
R3:
hostname R3
!
line con 0
exec-timeout 0 0
logging synchronous
!
line vty 0 4
PAGE 2/11
exec-timeout 0 0
logging synchronous
password cisco
login
!
!
end
III. Tasks:
1. Enable IPV6 on the fastethernet interfaces, and activate forwarding of IPv6 packets on the
routers.
2. Configure an IPV6 global address on each fastethernet interface using the IPv6 prefix
2001:1:2:3::/64 and the interface MAC address. R3 should learn the IPv6 address of the
interface F0/0 automatically. Disable RAs on R2’s F0/0 interface.
PAGE 3/11
IV. Solutions:
Task 1:
R1:
R1#configure terminal
R1(config)#ipv6 unicast-routing
R1(config)#interface FastEthernet0/0
R1(config-if)#ipv6 enable
R1(config-if)#end
R1#
R2:
R2(config-if)#end
R2#
R3:
R3(config-if)#end
R3#
Verification
R1:
R1#show ipv6 interface fastEthernet 0/0
FastEthernet0/0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::C000:9FF:FEA8:0
No Virtual link-local address(es):
No global unicast address is configured
Joined group address(es):
FF02::1
FF02::2
FF02::1:FFA8:0
MTU is 1500 bytes
PAGE 4/11
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
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
ND advertised default router preference is Medium
Hosts use stateless autoconfig for addresses.
R1#
R1#debug ipv6 nd
ICMP Neighbor Discovery events debugging is on
R1#
ICMPv6-ND: Sending NS for FE80::C000:9FF:FEA8:0 on FastEthernet0/0
ICMPv6-ND: DAD: FE80::C000:9FF:FEA8:0 is unique.
ICMPv6-ND: Sending NA for FE80::C000:9FF:FEA8:0 on FastEthernet0/0
ICMPv6-ND: Linklocal FE80::C000:9FF:FEA8:0 on FastEthernet0/0, Up
ICMPv6-ND: Address FE80::C000:9FF:FEA8:0/10 is up on FastEthernet0/0
ICMPv6-ND: Received NA for FE80::C001:9FF:FEA8:0 on FastEthernet0/0 from
FE80::C001:9FF:FEA8:0
FE80::C002:9FF:FEA8:0
R2:
FF02::1
FF02::2
FF02::1:FFA8:0
MTU is 1500 bytes
PAGE 5/11

R2#
R2#debug ipv6 nd
R2#
FE80::C002:9FF:FEA8:0
FE80::C000:9FF:FEA8:0
R3:
FF02::1
FF02::2
FF02::1:FFA8:0
MTU is 1500 bytes
R3#
PAGE 6/11
R3#debug ipv nd
R3#
FE80::C000:9FF:FEA8:0
The IPV6 enable command activates the IPV6 protocol on a specific interface. Once Ipv6
is enabled on the interface, a link-local IPV6 address is generated based on the Layer-2
identifier. This IPV6 address is assigned to the interface after its uniqueness is verified and
confirmed via the DAD feature.
The link-local IPv6 address should be unique per link. Multiple interfaces on the same
router can share the same IPv6 link-local address. But two interfaces on the same link cannot
share the same IPV6 link-local address.
Task 2:
R1:
R1(config-if)# ipv6 address 2001:1:2:3::/64 eui-64
R1(config-if)#end
R1#
R2:
R2(config)#interface F0/0
R2(config-if)#ipv6 nd ra suppress
R2(config-if)#ipv6 address 2001:1:2:3::/64 eui-64
R2(config-if)#end
R2#
R3:
R3(config)#interface f0/0
R3(config-if)#ipv6 address autoconfig
R3(config-if)#end
R3#
PAGE 7/11
Verification
R1:
Global unicast address(es):
2001:1:2:3:C000:9FF:FEA8:0, subnet is 2001:1:2:3::/64 [EUI]
FF02::1
FF02::2
FF02::1:FFA8:0
MTU is 1500 bytes
R1#
R2:
2001:1:2:3:C001:9FF:FEA8:0, subnet is 2001:1:2:3::/64 [EUI]
FF02::1
FF02::2
FF02::1:FFA8:0
MTU is 1500 bytes
PAGE 8/11
Hosts use stateless autoconfig for addresses

.
R3:
R3#debug ipv nd
R3#
ICMPv6-ND: Sending RS on FastEthernet0/0
ICMPv6-ND: Received RA from FE80::C000:9FF:FEA8:0 on FastEthernet0/0
ICMPv6-ND: Prefix Information change for 2001:1:2:3::/64, 0x0 -> 0xE0
ICMPv6-ND: Adding prefix 2001:1:2:3::/64 to FastEthernet0/0
ICMPv6-ND: Sending NS for 2001:1:2:3:C002:9FF:FEA8:0 on FastEthernet0/0
ICMPv6-ND: Autoconfiguring 2001:1:2:3:C002:9FF:FEA8:0 on FastEthernet0/0
R3#
ICMPv6-ND: DAD: 2001:1:2:3:C002:9FF:FEA8:0 is unique.
ICMPv6-ND: Sending NA for 2001:1:2:3:C002:9FF:FEA8:0 on FastEthernet0/0
ICMPv6-ND: Address 2001:1:2:3:C002:9FF:FEA8:0/64 is up on FastEthernet0/0

2001:1:2:3:C002:9FF:FEA8:0, subnet is 2001:1:2:3::/64 [EUI/CAL/PRE]
valid lifetime 2591973 preferred lifetime 604773
FF02::1
FF02::2
FF02::1:FFA8:0
MTU is 1500 bytes
PAGE 9/11
Because RAs are disabled on R2’s f0/0 interface, R2 will not respond to R3’s RS
messages. As a result, R3 will receive only RAs generated by R1 as shown in the output of the
debug ipv6 nd command, and It will configure the IPv6 address of the interface F0/0 using the
prefix supplied by R2 which 2001:1:2:3::/64.
PAGE 10/11
V. Links:
For more information about the commands used in this lab, use the following links:
1. debug ipv6 nd
http://www.cisco.com/en/US/docs/ios/ipv6/command/reference/ipv6_03.html#wp203578
3
2. ipv6 address
4
3. ipv6 address autoconfig

3
4. ipv6 address eui-64

0
5. ipv6 nd ra suppress
4
6. ipv6 unicast-routing
8
7. show ipv6 interface

1
PAGE 11/11
LAB 2: RIPNG
I. Network diagram:
http://www.networkexperttraining.com
Page 1/13

R1:
hostname R1
!
!
!
line con 0
exec-timeout 0 0
logging synchronous
line aux 0
line vty 0 4
exec-timeout 0 0
logging synchronous
password cisco
login
!
!
end
R2:
hostname R2
!
!
!
line con 0
exec-timeout 0 0
logging synchronous
line aux 0
line vty 0 4
exec-timeout 0 0
logging synchronous
password cisco
login
!
!
end
Page 2/13
III. Tasks:
1. Configure IPv6 addresses on R1 and R2 according to the network diagram. Make sure the
64-bit host portion of these addresses is calculated automatically.
2. Enable RIPng on R1 and R2’interfaces.
3. Set the maximum path parameter to the value of 2.
4. Configure R1 and R2 to forward RIP12 updates to the UDP port 6666 using the multicast
group FF02::ABCD.
Page 3/13
IV. Solutions:
Task 1:
R1:
ipv6 unicast-routing
interface FastEthernet0/0
ipv6 address 2002::/64 eui-64
!
ipv6 address 2002:1::/64 eui-64
R2:
ipv6 address 2002::/64 eui-64
!
Verification:
R1:
R1#show ipv6 interface brief
FastEthernet0/0 [up/up]
FE80::C000:EFF:FE3C:0
2002::C000:EFF:FE3C:0
2002:1::C000:EFF:FE3C:1
R2:

2002::C001:EFF:FE3C:0
2002:2::C001:EFF:FE3C:1
Page 4/13
Task 2:
Follow these steps to configure RIPng on the network:

1. Create the RIPng process using the command ipv6 router rip tag. Tag is a string used
to distinguish between RIPng processes on the same router. It is locally significant and
does not have to match between routers on the same RIPng domain. Use this
command in the global configuration mode.
2. Enable RIPng per interface using the ipv6 rip tag enable command in the interface
configuration mode. Router’s interfaces belonging to the same RIPng process have to
be configured with same tag as the one used for that RIPng process.
R1 & R2:
ipv6 router rip RIP12
interface f0/0
ipv6 rip RIP12 enable
interface f0/1
Verification:
R1:
R1#show ipv6 route
IPv6 Routing Table - 6 entries
Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route, M - MIPv6
I1 - ISIS L1, I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary
O - OSPF intra, OI - OSPF inter, OE1 - OSPF ext 1, OE2 - OSPF ext 2
ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2
D - EIGRP, EX - EIGRP external
C 2002::/64 [0/0]
via ::, FastEthernet0/0
L 2002::C000:EFF:FE3C:0/128 [0/0]
C 2002:1::/64 [0/0]
L 2002:1::C000:EFF:FE3C:1/128 [0/0]
R 2002:2::/64 [120/2]
via FE80::C001:EFF:FE3C:0, FastEthernet0/0
L FF00::/8 [0/0]
Page 5/13
via ::, Null0
The output of the show ipv6 route command displays the RIPng route learned from R2.
This route points to an IPv6 link-local local address. This is also the case with OSPFv3 and
EIGRP for IPv6.
R1#show ipv6 rip RIP12

RIP process "RIP12", port 521, multicast-group FF02::9, pid 247
Administrative distance is 120. Maximum paths is 16
Updates every 30 seconds, expire after 180
Holddown lasts 0 seconds, garbage collect after 120
Split horizon is on; poison reverse is off
Default routes are not generated
Periodic updates 20, trigger updates 3
Interfaces:
FastEthernet0/1
FastEthernet0/0
Redistribution:
None
The show ipv6 rip RIP12 command displays the characteristics (interfaces, UDP port,
update interval, multicast address…) of the RIPng process “RIP12“.
R1#show ipv6 interface f0/0

IPv6 is enabled, link-local address is FE80::C000:EFF:FE3C:0
2002::C000:EFF:FE3C:0, subnet is 2002::/64 [EUI]
FF02::1
FF02::2
FF02::9
FF02::1:FF3C:0
<omitted output>

2002:1::C000:EFF:FE3C:1, subnet is 2002:1::/64 [EUI]
FF02::1
FF02::2
Page 6/13
FF02::9
<omitted output>
The show ipv6 interface shows that the interfaces F0/0 and F0/1 have joined the
multicast group FF02::9(the reserved address for RIPng updates).
R1#debug ipv6 rip

RIP Routing Protocol debugging is on
R1#
*Mar 1 00:32:18.639: RIPng: Sending multicast update on FastEthernet0/1 for RIP12
*Mar 1 00:32:18.643: src=FE80::C000:EFF:FE3C:1
*Mar 1 00:32:18.643: dst=FF02::9 (FastEthernet0/1)
*Mar 1 00:32:18.647: sport=521, dport=521, length=72
*Mar 1 00:32:18.647: command=2, version=1, mbz=0, #rte=3
*Mar 1 00:32:18.651: tag=0, metric=1, prefix=2002::/64
*Mar 1 00:32:18.651: tag=0, metric=1, prefix=2002:1::/64
R1#
The debug ipv6 rip shows that R1 is sending RIPng updates out of the interfaces F0/0 and
F0/1.
R2:
Interfaces:
FastEthernet0/1
FastEthernet0/0
Redistribution:
None
Page 7/13
R2#show ipv6 route

C 2002::/64 [0/0]
L 2002::C001:EFF:FE3C:0/128 [0/0]
R 2002:1::/64 [120/2]
via FE80::C000:EFF:FE3C:0, FastEthernet0/0
C 2002:2::/64 [0/0]
L 2002:2::C001:EFF:FE3C:1/128 [0/0]
L FF00::/8 [0/0]
via ::, Null0

FF02::1
FF02::2
FF02::9
FF02::1:FF3C:0
<omitted output>

FF02::1
FF02::2
FF02::9
Page 8/13
FF02::1:FF3C:1
<omitted output>
R2#debug ipv6 rip

RIP Routing Protocol debugging is on
R2#
Task 3:
R1 & R2:
maximum-paths 2
Verification:
R1:
Interfaces:
Page 9/13
FastEthernet0/1
FastEthernet0/0
Redistribution:
None
R2:
Interfaces:
FastEthernet0/1
FastEthernet0/0
Redistribution:
None
Task 4
R1 & R2:
port 6666 multicast-group FF02::abcd
Verification:
R1:
RIP process "RIP12", port 6666, multicast-group FF02::ABCD, pid 247
Interfaces:
FastEthernet0/1
FastEthernet0/0
Page 10/13
Redistribution:
None

FF02::1
FF02::2
FF02::ABCD
FF02::1:FF3C:0
<omitted output>

FF02::1
FF02::2
FF02::ABCD
<omitted output>
R2:
RIP process "RIP12", port 6666, multicast-group FF02::ABCD, pid 247
Interfaces:
FastEthernet0/1
FastEthernet0/0
Redistribution:
None
Page 11/13

FF02::1
FF02::2
FF02::ABCD
FF02::1:FF3C:0
<omitted output>

FF02::1
FF02::2
FF02::ABCD
FF02::1:FF3C:1
<omitted output>
Page 12/13
V. Links
1. debug ipv6 rip

6
2. ipv6 address
4
3. ipv6 rip enable

3
4. ipv6 router rip

9
5. maximum-paths
8
6. port
8

1
8. show ipv6 route

6
9. show ipv6 rip

6
Page 13/13
LAB 3: RIPNG OVER FRAME RELAY
I. Network diagram:
Page 1/15
R1:
hostname R1
!
Ipv6 unicast-routing
Interface loopback 0
Ipv6 address 2002:1::1/64
!
line con 0
exec-timeout 0 0
logging synchronous
line aux 0
line vty 0 4
exec-timeout 0 0
logging synchronous
password cisco
login
!
!
end
R2:
hostname R2
!
!
line con 0
exec-timeout 0 0
logging synchronous
line aux 0
line vty 0 4
exec-timeout 0 0
logging synchronous
password cisco
login
!
!
end
Page 2/15
R3:
hostname R3
!
!
!
line con 0
exec-timeout 0 0
logging synchronous
line aux 0
line vty 0 4
exec-timeout 0 0
logging synchronous
password cisco
login
!
!
end
III. Tasks:
1. Configure IPV6 addressing on the frame relay cloud between R1, R2, and R3 according to
the following table:
Router Link-local IPV6 add Global IPv6 Address

R1 Fe80::1 2002:123::1/126
R2 Fe80::2 2002:123::1/126
R3 Fe80::3 2002:123::1/126
Additionally, configure necessary frame relay mappings on R1, R2, and R3 so they can ping
each other frame relay interface.
2. Configure the RIPng process RIP123 on the routers. Make to enable it on all interfaces.
3. Why R2 is unable to ping R3’s loopback interface, and vice-versa?
Page 3/15
IV. Solutions:
Task 1:
To reach R2’s S0/0 and R3’s S0/0 interfaces, R1 has to use the DLCIs 102 and 103
respectively. So we need to map the IPv6 addresses 2002:123::2 and 2002:123::3 to the
DLCIs 102 and 103 respectively.
R1:
interface Serial0/0
encapsulation frame-relay
ipv6 address 2002:123::1/126
ipv6 address FE80::1 link-local
frame-relay map ipv6 2002:123::2 102 broadcast
To reach R1’s S0/0 and R3’s S0/0 interfaces, R2 has to use the DLCI 201. So we need to
map the IPv6 addresses 2002:123::1 and 2002:123::3 to the DLCI 201.
R2:
interface Serial0/0
ipv6 address 2002:123::2/126
To reach R1’s S0/0 and R2’s S0/0 interfaces, R2 has to use the DLCI 301. So we need to
map the IPv6 addresses 2002:123::1 and 2002:123::2 to the DLCI 301.
R3:
interface Serial0/0
ipv6 address 2002:123::3/126
There is no need to disable Inverse ARP because it does not work over IPv6.
Page 4/15
Verification
R1:
R1#show frame-relay map

Serial0/0 (up): ipv6 2002:123::2 dlci 102(0x66,0x1860), static,
broadcast,
CISCO, status defined, active
Serial0/0 (up): ipv6 2002:123::3 dlci 103(0x67,0x1870), static,
broadcast,

Serial0/0 [up/up]
FE80::1
2002:123::1
Serial0/1 [administratively down/down]
unassigned
unassigned
unassigned
Loopback0 [up/up]
FE80::9CD7:2EFF:FEF0:99FA
2002:1::1
R1#ping 2002:123::2
Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 2002:123::2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 36/60/92 ms
R1#ping 2002:123::3

!!!!!
Page 5/15
R2:

Serial0/0 (up): ipv6 2002:123::1 dlci 201(0xC9,0x3090), static,
broadcast,
Serial0/0 (up): ipv6 2002:123::3 dlci 201(0xC9,0x3090), static,
broadcast,

Serial0/0 [up/up]
FE80::2
2002:123::2
unassigned
unassigned
unassigned
Loopback0 [up/up]
2002:2::2
R2#ping 2002:123::1

!!!!!
R2#ping 2002:123::3

!!!!!
R2#
Page 6/15
R3:

Serial0/0 (up): ipv6 2002:123::1 dlci 301(0x12D,0x48D0), static,
broadcast,
Serial0/0 (up): ipv6 2002:123::2 dlci 301(0x12D,0x48D0), static,
broadcast,

Serial0/0 [up/up]
FE80::3
2002:123::3
unassigned
unassigned
unassigned
Loopback0 [up/up]
2002:3::3
R3#ping 2002:123::1

!!!!!
R3#ping 2002:123::2

!!!!!
R3#
Page 7/15
Task 2:
R1, R2, and R3:

interface loopback0
interface serial0/0
Verification
R1:
R1#show ipv6 route
U - Per-user Static route
C 2002:1::/64 [0/0]
via ::, Loopback0
L 2002:1::1/128 [0/0]
via ::, Loopback0
R 2002:2::/64 [120/2]
via FE80::2, Serial0/0
R 2002:3::/64 [120/2]
C 2002:123::/126 [0/0]
via ::, Serial0/0
L 2002:123::1/128 [0/0]
via ::, Serial0/0
L FE80::/10 [0/0]
via ::, Null0
L FF00::/8 [0/0]
via ::, Null0
Page 8/15

Interfaces:
Serial0/0
Loopback0
Redistribution:
None
R1#
R2
R2#show ipv6 route
R 2002:1::/64 [120/2]
C 2002:2::/64 [0/0]
via ::, Loopback0
L 2002:2::2/128 [0/0]
via ::, Loopback0
C 2002:123::/126 [0/0]
via ::, Serial0/0
L 2002:123::2/128 [0/0]
via ::, Serial0/0
L FE80::/10 [0/0]
via ::, Null0
L FF00::/8 [0/0]
via ::, Null0

Page 9/15

Interfaces:
Serial0/0
Loopback0
Redistribution:
None
R2#
R3
Interfaces:
Serial0/0
Loopback0
Redistribution:
None
R3#show ipv6 route

R 2002:1::/64 [120/2]
C 2002:3::/64 [0/0]
via ::, Loopback0
L 2002:3::3/128 [0/0]
via ::, Loopback0
C 2002:123::/126 [0/0]
via ::, Serial0/0
L 2002:123::2/128 [0/0]
via ::, Serial0/0
Page 10/15
L 2002:123::3/128 [0/0]
via ::, Serial0/0
L FE80::/10 [0/0]
via ::, Null0
L FF00::/8 [0/0]
via ::, Null0
Although R1 has routing information about R2’s loopback 0 interface, it cannot ping it as
shown in the output below. This is also the case with R3’s loopback 0 interface.
R1#ping 2002:2::2

.....
Success rate is 0 percent (0/5)
R1#ping 2002:3::3

.....
According to the output of the show ipv6 route rip, the next hop addresses are link-local.
Therefore, you have to configure the necessary frame relay mapping between these IPV6 link-
local addresses and the appropriate DLCIs.
To circumvent this issue configure R1, R2 and R3 as follows:
R1:
interface S0/0
Frame-relay map ipv6 Fe80::2 102 br
R2 & R3
interface s0/0
Page 11/15
After changing the configuration, R1 can ping successfully the IPv6 addresses 2002:2::2
and 2002:3::3 as shown below.
R1#ping 2002:2::2

!!!!!
R1#ping 2002:3::3

!!!!!
R1#
Task 3:
R1:
// Before disabling Split-Horizon
R1#
R1#
*Mar 1 00:41:44.867: RIPng: Sending multicast update on Serial0/0 for RIP123
*Mar 1 00:41:44.871: src=FE80::1
*Mar 1 00:41:44.871: dst=FF02::9 (Serial0/0)
*Mar 1 00:41:44.879: IPV6: source FE80::1 (local)
*Mar 1 00:41:44.879: dest FF02::9 (Serial0/0)
*Mar 1 00:41:44.879: traffic class 224, flow 0x0, len 92+1408, prot 17, hops 255,
originating
Page 12/15
// After disabling Split-Horizon

R1#conf t
Enter configuration commands, one per line. End with CNTL/Z.
R1(config)#ipv6 router rip RIP123
R1(config-rtr)# no split-horizon
*Mar 1 00:42:39.027: RIPng: Sending multicast update on Serial0/0 for RIP123

*Mar 1 00:42:39.031: src=FE80::1
*Mar 1 00:42:39.031: dst=FF02::9 (Serial0/0)
*Mar 1 00:42:39.043: IPV6: source FE80::1 (local)
*Mar 1 00:42:39.043: dest FF02::9 (Serial0/0)
*Mar 1 00:42:39.043: traffic class 224, flow 0x0, len 132+1368, prot 17, hops 255,
originating
*Mar 1 00:42:39.047: IPv6: Sending on Serial0/0
By default, split-horizon (RIPng) is enabled on RIPng instances. You cannot

disable/enable it per interface. It can be disable/enable per RIPng process. Spilt-horizon
prevents the RIPng process from advertising a route out of the interface on which it was
received.
On Hub-and-spoke networks, the spokes cannot share routing information about each
other. To avoid this behavior, disable split-horizon feature on the hub. Do not disable it on the
spokes.
R1:
no split-horizon
Verification
R1:
R1#show ipv rip RIP123
Split horizon is off; poison reverse is off
Page 13/15

Interfaces:
Serial0/0
Loopback0
Redistribution:
None
R2:
R2#ping 2002:3::3
!!!!!
R2#show ipv6 route rip

R 2002:1::/64 [120/2]
R 2002:3::/64 [120/3]
R3:
R3#ping 2002:2::2
!!!!!
R3#show ipv6 route rip

R 2002:1::/64 [120/2]
R 2002:2::/64 [120/3]
Page 14/15
V. Links
1. debug ipv6 rip

6
2. ipv6 address link-local

3
8
4. ipv6 rip enable

3
5. ipv6 router rip

9

1
7. show ipv6 route

6
8. show ipv6 rip

6
9. split-horizon (IPv6 RIP)

4
Page 15/15
LAB 4: 6TO4 TUNNELING
I. Network diagram:
Page 1/11
R1:
hostname R1
!
!
!
!
interface s1/0
clock rate 64000
ip address 193.12.12.1 255.255.255.0
no shutdown
!
interface fastethernet 0/0
no shutdown
!
!
line con 0
exec-timeout 0 0
logging synchronous
line aux 0
line vty 0 4
exec-timeout 0 0
logging synchronous
password cisco
login
!
!
End
R2:
hostname R2
!
!
!
!
interface s1/0
ip address 193.12.12.2 255.255.255.0
Page 2/11
no shutdown
!
interface fastethernet 0/0
no shutdown
!
!
line con 0
exec-timeout 0 0
logging synchronous
line aux 0
line vty 0 4
exec-timeout 0 0
logging synchronous
password cisco
login
!
end
III. Tasks:
1. Create an IPv6 tunnel between R1 & R2 over the IPV4 network using the IPv6 prefix
2001:12:12:12::/126. The tunnel mode is ipv6ip.
2. What do you need to configure on R1 and R2 to enable communication between PC1 and
PC2?
Page 3/11
IV. Solutions:
Task1:
The IPv6 networks 2001:1:1:1::/64 and 2001:2:2:2::/64 are discontiguous because they
are separated by the IPv4 network 193.12.12.0/24.
To enable communication between these two IPv6 networks, you can use different
techniques. One of these techniques is ipv6-over-ipv4 tunneling. Using this technique, every
IPv6 packets sent over the serial link will be encapsulated in an IPV4 packet on one end and
de-encapsulated on the other end of the serial link.
To accomplish this task, configure two tunnel interfaces on R1 & R2 using the following
parameters:
R1’s Tunnel Interface R2’s Tunnel Interface

Source 132.1.12.1 132.1.12.2
Destination 132.12.2 132.2.12.1
Mode IPV6 IP IPV6 IP
Ipv6 2001:12:12:12::1/64 2002:12:12:12::2/64
R1:
interface tunnel0
tunnel source s1/0
tunnel destination 193.12.12.2
tunnel mode ipv6ip
ipv6 address 2001 :12 :12 :12 ::1/126
R1:
interface tunnel12
tunnel source s1/0
tunnel destination 193.12.12.1
tunnel mode ipv6ip
ipv6 address 2001:12:12:12::2/126
Page 4/11
Verification
R1:
R1#show ipv route
C 2001:12:12:12::/126 [0/0]
via ::, Tunnel0
L 2001:12:12:12::1/128 [0/0]
via ::, Tunnel0
C 2002:1::/64 [0/0]
L 2002:1::C000:DFF:FE94:0/128 [0/0]
L FF00::/8 [0/0]
via ::, Null0
R1#show ipv6 interface tunnel 0

Tunnel0 is up, line protocol is up
IPv6 is enabled, link-local address is FE80::C10C:C01
2001:12:12:12::1, subnet is 2001:12:12:12::/126
FF02::1
FF02::2
FF02::1:FF00:1
FF02::1:FF0C:C01
MTU is 1480 bytes
Page 5/11
R1#show interfaces tunnel 0

Hardware is Tunnel
MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation TUNNEL, loopback not set
Keepalive not set
Tunnel source 193.12.12.1 (Serial1/0), destination 193.12.12.2
Tunnel protocol/transport IPv6/IP
<omitted output>
R1#
R1#ping 2001:12:12:12::2

Sending 5, 100-byte ICMP Echos to 2001:12:12:12::2, timeout is 2 seconds:
!!!!!
R1#
R2:
R2#show interfaces tunnel 12

Hardware is Tunnel
MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation TUNNEL, loopback not set
Keepalive not set
Tunnel source 193.12.12.2 (Serial1/0), destination 193.12.12.1
Tunnel protocol/transport IPv6/IP
<omitted output>
R2#show ipv interface tunnel 12

IPv6 is enabled, link-local address is FE80::C10C:C02
2001:12:12:12::2, subnet is 2001:12:12:12::/126
FF02::1
FF02::2
Page 6/11
FF02::1:FF00:2
FF02::1:FF0C:C02
MTU is 1480 bytes
R2#show ipv6 route

C 2001:12:12:12::/126 [0/0]
via ::, Tunnel12
L 2001:12:12:12::2/128 [0/0]
via ::, Tunnel12
C 2002:2::/64 [0/0]
L 2002:2::C001:DFF:FE94:0/128 [0/0]
L FF00::/8 [0/0]
via ::, Null0
R2#
R1#ping 2001:12:12:12::2

Sending 5, 100-byte ICMP Echos to 2001:12:12:12::2, timeout is 2 seconds:
!!!!!
R1#
Page 7/11
Task2:
Before answering the question, let’s ping the R2’s F0/0 interface from R1 and take a look
at the output debug ipv6 packet command shown below.
R1#debug ipv6 packet

IPv6 unicast packet debugging is on
R1#
R1#
R1#ping 2002:2::C001:DFF:FE94:0

Sending 5, 100-byte ICMP Echos to 2002:2::C001:DFF:FE94:0, timeout is 2 seconds:
IPv6: SAS picked source 2002:1::C000:DFF:FE94:0 for 2002:2::C001:DFF:FE94:0

(FastEthernet0/0)
IPV6: source 2002:1::C000:DFF:FE94:0 (local)
dest 2002:2::C001:DFF:FE94:0
traffic class 0, flow 0x0, len 100+0, prot 58, hops 64, Route not found.
(FastEthernet0/0)
dest 2002:2::C001:DFF:FE94:0
<omitted output>
R1 cannot ping R2’s F0/0 interface because it did not find any route to forward the ICMP
echo-request packets. This is illustrated in the output of the debug ipv6 packet command by
the message “Route not found”.
let’s ping the R1’s F0/0 interface from R2 and take at the output debug ipv6 packet
command shown below.
R2#debug ipv6 packet

IPv6 unicast packet debugging is on
R2#
R2#ping 2002:1::C000:DFF:FE94:0

Page 8/11

(FastEthernet0/0)
dest 2002:1::C000:DFF:FE94:0
<omitted output>
R2#
To sum up, R1 and R2 need to add routing information about each other’s connected
IPv6 network. So you have to configure IPv6 routing on R1 & R2 using static IPV6 routes or a
dynamic routing protocol such as RIPng or OSPF v3.
R1:
ipv6 route 2002:2:::/64 tunnel0
R2:
ipv6 route 2002:1::/64 tunnel12
Verification
R1:
R1#ping 2002:2::C001:DFF:FE94:0

!!!!!
R1#show ipv6 route

Page 9/11
C 2001:12:12:12::/126 [0/0]
via ::, Tunnel0
L 2001:12:12:12::1/128 [0/0]
via ::, Tunnel0
C 2002:1::/64 [0/0]
L 2002:1::C000:DFF:FE94:0/128 [0/0]
S 2002:2::/64 [1/0]
via ::, Tunnel0
L FF00::/8 [0/0]
via ::, Null0
R1#
R2:
R2#ping 2002:1::C000:DFF:FE94:0

!!!!!
R2#show ipv6 route

C 2001:12:12:12::/126 [0/0]
via ::, Tunnel12
L 2001:12:12:12::2/128 [0/0]
via ::, Tunnel12
S 2002:1::/64 [1/0]
via ::, Tunnel12
C 2002:2::/64 [0/0]
L 2002:2::C001:DFF:FE94:0/128 [0/0]
L FF00::/8 [0/0]
via ::, Null0
Page 10/11
V. Links
1. ipv6 route
1
8

1
4. show ipv6 route

6
5. tunnel destination
9
6. tunnel mode ipv6ip

0
7. tunnel source
1
Page 11/11

IPv 6

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

IPv 6

Transféré par

Droits d'auteur :

Formats disponibles

COPYRIGHT INFORMATION

If you have questions or concerns about our disclaimer, please email us at

BASIC IPV6 ADDRESSING CONFIGURATION……….…………………………………………….. 4

LAB 1: BASIC IPV6 ADDRESSING CONFIGURATION

II. Initial Configuration:

ICMP error messages limited to one every 100 milliseconds

ND advertised retransmit interval is 0 milliseconds

Hosts use stateless autoconfig for addresses

R3#show ipv6 interface fastEthernet 0/0

3. ipv6 address autoconfig

4. ipv6 address eui-64

7. show ipv6 interface

II. Initial Configuration:

R2#show ipv6 interface brief

Follow these steps to configure RIPng on the network:

via ::, Null0

R1#show ipv6 rip RIP12

R1#show ipv6 interface f0/0

R1#show ipv6 interface f0/1

R1#debug ipv6 rip

R2#show ipv6 route

R2#show ipv6 interface f0/0

R2#show ipv6 interface f0/1

R2#debug ipv6 rip

R1#show ipv6 interface f0/0

R1#show ipv6 interface f0/1

R2#show ipv6 interface f0/0

R2#show ipv6 interface f0/1

1. debug ipv6 rip

3. ipv6 rip enable

4. ipv6 router rip

7. show ipv6 interface

8. show ipv6 route

9. show ipv6 rip

LAB 3: RIPNG OVER FRAME RELAY

II. Initial Configuration:

Router Link-local IPV6 add Global IPv6 Address

3. Why R2 is unable to ping R3’s loopback interface, and vice-versa?

R1#show frame-relay map

R1#show ipv6 interface brief

Type escape sequence to abort.

Type escape sequence to abort.

R2#show frame-relay map

R2#show ipv6 interface brief

Type escape sequence to abort.

Type escape sequence to abort.

R3#show frame-relay map

R3#show ipv6 interface brief

Type escape sequence to abort.

Type escape sequence to abort.

R1, R2, and R3:

R1#show ipv6 rip RIP123

R2#show ipv6 rip RIP123

Holddown lasts 0 seconds, garbage collect after 120

R3#show ipv6 route

Type escape sequence to abort.

Type escape sequence to abort.

To circumvent this issue configure R1, R2 and R3 as follows:

Type escape sequence to abort.

Type escape sequence to abort.

// Before disabling Split-Horizon

// After disabling Split-Horizon

*Mar 1 00:42:39.027: RIPng: Sending multicast update on Serial0/0 for RIP123