IPv6 Lab

Build Your Topology IPv6 LAN Addressing Basics

Download pre configurations for your pod. On both switches you will
need to issue the command sdm prefer dual-ipv4-and-ipv6 default,
save your configuration, and reload which will allow the switches to
support IPv 6 features.
X in the addressing scheme refers to your pod #.
A sample tcl script is provided at the end to test connectivity this will
need to be modified, where X is replaced with your pod #.


1. Vlan 12 between SW1 and R1
Enable ipv6 routing on both SW1 and R1
Assign global IPv6 unicast addresses per diagram across vlan 12
Configure Loopback 0 on SW1 per diagram.
Add Loopback 0 to R1 with an address of 2001:X:1:1::1/64.
Add Loopback 1 to R1 with an address of 2001:X:11:11::11/64.
What was the link local address assigned to R1 fast0/0?
Ensure you can ping 2001:X:1:1:12::1 from SW1.

Useful commands:
Show ipv6 int brief
Show ipv6 int <interface id>
Show ipv6 neighbors

2. EUI-64
On R1 create a new Loopback 2 interface and assign a global IPv6 address of 1:X:1:10::/64. Manually
determine the interface ID using modified EUI-64 format based on MAC address of fast0/0.

Next, create Loopback3 interface and assign a global IPv6 address of 1:X:1:11::/64 where the host
portion of the address is automatically created from a MAC address.

3. Basic Static Routing
Configure basic IPv6 static routing so you can ping loopback interfaces between SW1 and R1.

Useful commands:
Show ipv6 route

After that is working please remove the static routes.

4. Complete LAN Addressing
Enable IPv6 on remaining devices .
Complete LAN addressing per the diagram and ensure you can ping across directly connected IPv6
and IPv4 segments:
Vlan 15 on R5 and SW2
Vlan 40 between R4 and R5 (note IPv4 only)
Vlan 16 between R3 and R6

Add the following loopbacks:
R2 loopback0 2001:X:2:2::2/64
R2 loopback1 2001:X:22:22::22/64
R3 loopback 0: 2001:X:3:3::3/64
R3 loopback 1 2001:X:33:33::33/64
R4 loopback 0 2001:X:4:4::4/64
R4 loopback 1 2001:X:44:44::44/64
R6 loopback 0 2001:X:6:6::6/64
SW2 loopback 1 2001:X:15:15::15/64

Build Your Topology IPv6 Frame Relay Basics
5. Frame Relay Hub and Spoke
Configure Hub and Spoke Topology between R1, R2, and R3 where R1 is hub, using addressing and
DLCIs per diagram. Test connectivity with ping. Also manually assign link local addressing on R1, R2,
and R3 this is necessary for routing protocols to work.

Useful commands:
Show frame map

6. Frame Relay Point to Point
Configure a point to point FR connection between R1 and R4 per diagram, using 2001:X:1:14::/64.
You must use same physical interface on R1 as in task 5.

Routing - RIPng
7. RIPng basic configuration
Configure a RIPng process named RIPNG on SW2 and R5 on vlan 15. Put loopback1 on SW2 into
RIPng directly. To test this is working correctly make sure R5 can ping loopback1 on SW2.

Useful commands:
Show ipv6 rip
Show ipv6 route rip

Routing OSPFv3
8. OSPFv3 Area 0
Configure R1, R2, and R3 in area 0 per the diagram on 2001:x:1:1:23::/64. You will need to configure
an IPv4 RID on each for OSPFv3 :
R1: 1.1.1.1
R2: 2.2.2.2
R3 : 3.3.3.3
Link local addresses are used as source and destination for OSPFv3 so these must be reachable.
Do not change the OSPFv3 default interface type and given the OSPFv3 default interface type (non
broadcast on serial interface) with the hub and spoke topology choose what router should be DR
and use the appropriate command to set that router to DR and the other two so they never become
DR. Hint: what is required for the OSPF network type to work?

Useful commands:
Show ipv6 ospf neighbor
Show ipv6 route ospf
Show ipv6 ospf database
Show ipv6 ospf interface

9. OSPFv3 Area 0 Loopback interfaces
On R1 put the loopback interfaces into OSPFv3 area 0 by redistributing connected interfaces.
On R2 put the loopback interfaces directly into area 0.
On R3 put the loopback and fast0/0 directly into area 0.

At this point you should be able to ping loopbacks from each other test that R1 can ping loopbacks
of R2 and R3. Ping loopbacks of R1 and R2 from R3. Finally ping loopbacks of R1 and R3 from R2.

10. OSPFv3 Area 12
Configure OSPFv3 area 12 on fast0/0 of R1 (vlan 12) and Vlan 12 of SW1.
SW1 will need a router-id : 12.12.12.12.
Put loopback0 of SW1 directly into area 12.
Test connectivity by pinging 2001:X:12:12::12 from R1, R2, and R3.
Routing EIGRP for IPv6

11. EIGRP AS 100
Configure EIGRP using AS 100 between the FR ptp interface on R1 and R4. Redistribute connected
on R1 into EIGRP AS 100. Also redistribute connected on R4 into EIGRP. Test by ensuring that R1
can ping R4 loopback addresses. EIGRP router id will be required on R4: 4.4.4.4 and R1:1.1.1.1.

Useful commands:
Show ipv6 eigrp neighbor
Show ipv6 eigrp topology
Show ipv6 route eigrp

12. Tunnel
Over the IPv4 network between R4 and R5 configure an IPv6 tunnel. Configure EIGRP for IPV6 AS
100 on each end of the tunnel. On R5 redistributed connected into EIGRP for IPv6 AS 100. EIGRP
router id will be required on R5: 5.5.5.5. Upon successful completion R4 should be able to ping
2001:X:1:15::5.

Useful commands:
Show tunnel

Routing MBGP

13. MBGP
Configure a MBGP session between R3 and R6 over vlan 16. R3 should use AS 33. R6 should use as
66. R3 should be configured to originate default via BGP to R6.

Useful commands:
Show bgp all summary
Show bgp ipv6 unicast

Routing Redistribution

14. Route Redistribution
In order to have full IPv6 connectivity throughout the topology you must perform redistribution as
follows:
R1: mutual redistribution between OSPFv3 and EIGRP for v6.
R5: mutual redistribution between RIPng and EIGRP for v6.
R3: redistribute connected into OSPFv3 in order to get link to R6 in routing table.

At this point you should be able to run tcl script on each device to ping all other devices successfully.

Save your configurations.
Cross Pod MBGP
15. R1 MBGP
On F0/1 on R1 configure IPv6 address of 2001:2001:2001:2001::X/64. You should be able to ping all
of the other pods across this.

Configure an MBGP peering session using AS X to every other pod in class. Announce an aggregate
of 2001:X/32 via MBGP to all of your peers.

Configure R1 to announce default within your topology via OSPFv6 and EIGRP for IPv6.
At this point you should have full connectivity to all of the other pods topology. Test by pinging
various pods loopback addresses:
2001:X:12:12::12
2001:X:2:2::2
2001:X:15:15::15




















Troubleshooting - Download broken configurations into your pod. Topology shown below.


16. OSPFv3 Troubleshooting
There are problems with the OSPFv3 configuration on area 0 between routers R1, R2, and R3. Find
and correct problems. Be sure that each router can ping each others loopback addresses.

17. IPv6 Tunnel Troubleshooting
The connection between R4 and R5 is IPv4 only and therefore an IPv6 tunnel was created this
tunnel is not working properly diagnose and resolve.

18. EIGRP Troubleshooting
The R4 EIGRP neighbor relationships between R1 and R5 are not working properly diagnose and
resolve. After ensure that R4 can ping 2001:1:1:15::5 and 2001:1:1:23::1.

19. MBGP Troubleshooting
R3 is supposed to originate default via MBGP to R6, but this is not occurring properly diagnose and
resolve.

20. Route Redistribution Troubleshooting
Full IPv6 connectivity throughout the topology should be in place (run the tclsh script on each
router), but is not. For example R6 cannot reach loopbacks on R4. Diagnose and resolve tclsh
script should be successfully run on all devices including SW1 and SW2 with everything reachable.

Advanced Topics Time Permitting
Start with working configurations after step 20.
21. OSPFv3 Authentication
Configure OSPFv3 authentication across area 0.

22. Prefix Filtering
On SW2 create a prefix list and apply to outbound RIPng updates to ensure only 2001:15:15:15::/64
is announced.

23. EIGRP stub
Configure R5 to be an EIGRP stub.

24. MBGP
Configure loopback0 on R6 of 2001:X:6:6::6/64. Announce this route via MBGP to R3. Configure R3
to redistribute bgp into OSPFv3. Use a route-map on R3 and prefix list to be sure only
2001:X:6:6::/64 is redistributed. If successful SW1 and SW2 should both be able to ping
2001:X:6:6::6.

25. IPv6 Access Lists
Configure R6 to allow remote telnet access. Test this from R2 and R4.
On R3 create an extended IPv6 ACL to be applied inbound on Serial0/0/0 interface which will allow
telnet access to R6 only via R4 and no other hosts. Be careful to allow any necessary routing
protocol traffic in your ACL as well as ICMPv6 so pings will still work properly. If successful you
should be able to telnet to R6 from R4 but not R2.

TCL Script for verification after Step 15:
tclsh
foreach address {
2001:X:1:12::1
2001:X:1:12::12
2001:X:1:23::1
2001:X:1:23::2
2001:X:1:23::3
2001:X:1:14::1
2001:X:1:14::4
2001:X:1:15::5
2001:X:1:15::15
2001:X:1:16::3
2001:X:1:16::6
2001:X:1:1::1
2001:X:11:11::11
2001:X:2:2::2
2001:X:22:22::22
2001:X:3:3::3
2001:X:33:33::33
2001:X:44:44::44
2001:X:4:4::4
2001:X:15:15::15
2001:X:12:12::12
} {ping $address
}
tclquit
TCL Script for verification after Step 20:
tclsh
foreach address {
2001:1:1:12::1
2001:1:1:12::12
2001:1:1:23::1
2001:1:1:23::2
2001:1:1:23::3
2001:1:1:14::1
2001:1:1:14::4
2001:1:1:15::5
2001:1:1:15::15
2001:1:1:16::3
2001:1:1:16::6
2001:1:1:1::1
2001:11:11:11::11
2001:2:2:2::2
2001:22:22:22::22
2001:3:3:3::3
2001:33:33:33::33
2001:44:44:44::44
2001:4:4:4::4
2001:15:15:15::15
2001:12:12:12::12
} {ping $address
}
tclquit