IP6FD

IPv6 Fundamentals,
Design, and Deployment
Lab Guide

Version 3.1 (Draft)

Table of Contents
Discovery Lab 1: Enabling IPv6 on Hosts.....................................................................
 Task 0: Reset the Router for this Lab....................................................................
 Task 1: Configure IPv4 Addressing and Routing on a PC.....................................
 Task 2: Configure IPv6 Addressing and Routing on a Router.............................
 Task 3: Configure Static IPv6 Addressing and Routing on a PC That Runs
the Windows 10 Operating System......................................................................
 Task 4: Configure Static IPv6 Addressing and Routing on a PC That Runs
the Linux Operating System.................................................................................
Discovery Lab 2: Using Neighbor Discovery.............................................................
 Task 0: Reset the Router for this Lab..................................................................
 Task 1: Configure Router Advertisements...........................................................
 Task 2: Renumber the Local Network..................................................................
Discovery Lab 3: Using Prefix Delegation...................................................................
 Task 0: Reset the Router for this Lab..................................................................
 Task 1: Configure a Prefix Delegation Server and Client.....................................
 Task 2: Configure a Non-Prefix Delegation DHCPv6 Server...............................
Discovery Lab 4: Deploy HSRP for IPv6......................................................................
 Task 0: Reset the Router for this Lab..................................................................
 Task 1: Verify IPv6 Reachability from PC1..........................................................
Discovery Lab 5: Routing with OSPFv3.......................................................................
 Task 0: Reset the Router for this Lab..................................................................
 Task 1: Configure OSPF......................................................................................
 Task 2: Summarize Route Announcements.........................................................
 Task 3: Replace all Routing with OSPFv3...........................................................

Table of Contents | © Cisco Systems, Inc. IP6FD Lab Guide

 Discovery Lab 6: Routing with EIGRP.........................................................................
 Task 0: Reset the Router for this Lab..................................................................
 Task 1: Configure EIGRP for IPv6 Routing..........................................................
 Task 2: Configuring EIGRP for IPv6 Summarization...........................................
 Task 3: Configuring Named EIGRP for IPv6 and IPv4.........................................
Discovery Lab 7: Routing with BGP and MP-BGP....................................................
 Task 0: Reset the Router for this Lab................................................................
 Task 1: Configure IBGP for IPv6........................................................................
 Task 2: Configure EBGP for IPv6......................................................................
 Task 3: Configure IPv6 Prefix Filtering in BGP..................................................
Discovery Lab 8: Troubleshooting Tickets 1 – 9......................................................
 Task 0: Reset the Router for this Lab................................................................
 Trouble Ticket #1: PC2 Cannot Reach 2001:db9:7:7::7....................................
 Trouble Ticket #2: PC2 Not Receiving DHCPv6 Address from R2....................
 Trouble Ticket #3: PC2 Not Receiving DHCPv6 Address from R2....................
 Task 0: Reset the Router for Tickets 4 – 6.........................................................
 Trouble Ticket #4: PC1 Cannot Reach 2001:db9:7:7::7....................................
 Trouble Ticket #5: PC2 Cannot Reach 2001:db9:7:7::7....................................
 Trouble Ticket #6: PC1 Cannot Reach External Networks................................
 Task 0: Reset the Router for Tickets 7 – 9.........................................................
 Trouble Ticket #7: PC1 Cannot Reach 2001:db9:7:7::7....................................
 Trouble Ticket #8: PC1 Cannot Reach 2001:db9:3:3::3....................................
 Trouble Ticket #9: PC1 Cannot Reach 2001:db9:199:199:199::199.................
Discovery Lab 9: Multicasting....................................................................................
 Task 0: Reset the Router for this Lab................................................................
 Task 1: Configure Multicast by Using Static RPs...............................................
 Task 2: Configure Source-Tree Multicast...........................................................
 Task 3: Configure BSR......................................................................................
Discovery Lab 10: Configure NAT64 Services..........................................................
 Task 0: Reset the Router for this Lab................................................................
 Task 1: Configure R1 as an IPv4 Only Router...................................................
 Task 2: Configure R3 for both IPv4 and IPv6.....................................................
 Task 3: Configure R6 as an IPv6 Only Router...................................................
 Task 4: Configure Static NAT64 on R3..............................................................
Discovery Lab 11: Configure NAT64 Dynamic Serivces..........................................

Table of Contents | © Cisco Systems, Inc. IP6FD Lab Guide

  Task 0: Reset the Router for this Lab................................................................
 Task 1: Configure a Static Route on R1.............................................................
 Task 2: Configure Dynamic NAT64 on R3.........................................................
Discovery Lab 12: Configure DNS64 Services..........................................................
 This Lab is still a work in progress. Need to insert.............................................
Discovery Lab 13: Configure Advanced ACLs..........................................................
 Task 0: Reset the Router for this Lab................................................................
 Task 1: Configure a Standard ACL for IPv6 (Layer 3 Address Filtering)...........
 Task 2: Configure an Extended ACL for IPv6 (Layer 3 and Layer 4
Filtering).............................................................................................................
 Task 3: Configure an Extended ACL for IPv6 (Extension Header
Matching)...........................................................................................................
 Task 4: Control Inbound IPv6 Access to a Router.............................................
Discovery Lab 14: Implementing IPsec and IKE.......................................................
 Task 0: Reset the Router for this Lab................................................................
 Task 1: Configure IPsec.....................................................................................
Discovery Lab 15: Troubleshooting Tickets 10-12...................................................
 Task 0: Reset the Router for this Lab................................................................
 Trouble Ticket #10: PC1 Cannot Reach 2001:db9:3:3::3..................................
 Trouble Ticket #11: Multicast Streaming Test Fails..........................................
 Trouble Ticket #12: PC2 Cannot Reach 2001:db9:199:199:199::199..............

Table of Contents | © Cisco Systems, Inc. IP6FD Lab Guide

Discovery Lab 1:
Enabling IPv6 on Hosts
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will enable basic IPv6 connectivity on PCs that are running Windows 10, and Linux,
and on a Cisco IOS router. After completing this activity, you will be able to meet the following
objectives:
 Configure IPv4 addressing and routing on a PC.
 Configure IPv6 addressing and routing on a router.
 Configure static IPv6 addressing and routing on a PC that uses the Windows 10 operating
system.
 Configure static IPv6 addressing and routing on a PC that uses the Linux operating system.

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 1

Visual Objective
The figure illustrates what you will accomplish in this activity.

The lab environment is set up so that IPv4 is already configured on router R1. Configure Windows 10
on PC1 for IPv4 so that you can use Telnet to connect to the router.

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 2

Required Resources
The table lists the resources and equipment that are required to complete this activity.

Device Name Device Role in the Laboratory

R1 WAN access router for PC1; used as a default gateway for IPv4 and IPv6
traffic.

PC1 End user with applications that require both IPv4 and IPv6 support by the
Windows 10 operating system and the network.

PC2 End user with applications that require both IPv4 and IPv6 support by the
Linux operating system and the network.

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 3

Command List
The table describes the commands that are used in this activity.

Cisco IOS Software Commands

Command Description

ipv6 address prefix Configures a static IP address on an interface.

ipv6 enable Enables an interface for IPv6.

ipv6 nd ra suppress Suppresses IPv6 router advertisement

transmissions on a LAN interface.

ipv6 unicast-routing Enables IPv6 routing.

show ip interface brief Shows brief IPv4 interface information.

show ip route Shows the IPv4 routing table.

show ipv6 interface brief Shows brief IPv6 interface information.

show ipv6 route Shows the IPv6 routing table.

Microsoft Windows PC Commands

Command Description

netsh interface ip set address Configures the IPv4 address, mask, and default
int_name static ip_addr net_mask gateway to the interface named int_name.
def_gw 1
netsh interface ipv6 add address Adds an IPv6 address to an interface on
int_name ipv6_address Microsoft Windows 10.

netsh interface ipv6 add route Adds a route for a specified prefix.
route int_name next-hop
netsh interface ipv6 show interface Displays Windows 10 interfaces.
[intf]
ping Enters the ping command from Windows 10.

ping6 Enters the ping6 command from Windows 10.

Note You can get detailed help if you type a question mark at the end of the netsh commands; for
example, netsh interface ipv6 add address ?.

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 4

Linux PC Commands

Command Description

ifconfig Displays all network interface information that

has been configured.

ping Enters the ping command.

ping6 Enters the ping6 command.

Job Aids
These job aids are available to help you complete the lab activity:
 The instructor will provide you with your pod number and other pod-access information. Log this
information in the table.

Pod-Access Information

Parameter Value

Your pod number

Username on router R1 —

Password on router R1 —

Username on PC1 Admin

Password on PC1 ISEisC00L

Username on PC3 root

Password on PC3 ISEisC00L

Note Router R1 is preconfigured to allow access without any credentials. Any Telnet session or console
access will automatically give you access to privileged mode.

 The table illustrates the IPv4 and IPv6 addressing scheme that is used in this lab exercise.

Pod Addressing

Device Interface IPv4 Address and Mask IPv6 Address and Mask

R1 GigabitEthernet1 192.168.1.1/24 2001:db9:1:1::1/64

PC1 LAB 192.168.1.2/24 2001:db9:1:1::f/64

Ubuntu LAB 192.168.1.3/24 2001:db9:1:1::e/64

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 5

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 6
Task 0: Reset the Router for this Lab
In this task, you will reset the router(s) for the beginning of this lab. The process is using a configure
restore option within IOS. There are command aliases already configured as the baseline of the routers
and they reference configurations found in flash.

Activity Procedure
Complete the following steps:
Step 1 Connect to Router 1 (R1) and get to privileged mode.
Step 2 Type lab-2-1 and type Y to confirm.

To confirm, do a show ip interface brief and you should see that there is now
an address on interface GigabitEthernet1.

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 7

Task 1: Configure IPv4 Addressing and Routing on
a PC
In this task, you will confirm that your PC has the necessary IPv4 configuration information to establish
connectivity in the lab topology.

Activity Procedure
Complete the following steps:
Step 1 Connect to PC1 (Win10-1) and log in by using the username and password as
specified in the Job Aids section. Right-click on the Network icon in the lower-
right corner and select Open Network and Sharing Center.

Step 2 Click on Change adapter settings on the left side of the window.

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 8

 Step 3 Right-click the LAB connection and choose Properties.

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 9

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 10
 Step 4 Highlight Internet Protocol (TCP/IP) and click Properties. Verify the IPv4
Configuration to match these parameters:
 IP address: 192.168.1.2
 Subnet mask: 255.255.255.0
 Default gateway: 192.168.1.1

Note The steps show a common end user approach to complete this task. An alternative method is to
execute the netsh int ip set address LAB static 192.168.1.2 255.255.255.0 192.168.1.1 1 CLI
command in the Windows 10 command-prompt window.

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 11

Activity Verification
You have completed this task when you attain these results:
 On PC1, open a command window and run ipconfig /all command.

.
 Ping the IPv4 address of R1. The ping should be successful.
C:\Users\Admin>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:

Reply from 192.168.1.1: bytes=32 time=1ms TTL=255

Reply from 192.168.1.1: bytes=32 time=1ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1ms TTL=255
Reply from 192.168.1.1: bytes=32 time=1ms TTL=255

Ping statistics for 192.168.1.1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 12

Task 2: Configure IPv6 Addressing and Routing on
a Router
In this task, you will configure IPv6 addressing and related parameters on the router.

Note You can connect directly to the console port of the router by clicking the router icon, or you can use
Telnet and connect from your remote desktop session. In either case, you do not need any account
(username and password) to have full access to enable mode.

Activity Procedure
Complete the following steps:
Step 1 On R1, verify the IPv4 interfaces. Your output should match the lab topology.
Step 2 Verify the IPv4 routing table.
Step 3 Verify the IPv6 status of the interfaces and routing table. Nothing should be
assigned at this point.
Step 4 Enable IPv6 unicast routing in global configuration mode.
Step 5 Enable IPv6 on the GigabitEthernet1 interface.
Step 6 Disable neighbor discovery router advertisements on the GigabitEthernet1
interface.
Step 7 Configure an IPv6 address on the GigabitEthernet1 interface. Use the address
that is listed in the Job Aids section.

Activity Verification
You have completed this task when you attain this result:
 On R1, again verify the IPv6 status of the interfaces and routing table. You will see both the
network (/64) and the host (/128) addresses that are assigned to the GigabitEthernet1 interface.
R1#show ipv6 interface brief
GigabitEthernet1 [up/up]
FE80::217:59FF:FE03:19B8
2001:DB9:1:1::1
GigabitEthernet2 [administratively down/down]
unassigned
GigabitEthernet3 [administratively down/down]
unassigned

R1#show ipv6 route

IPv6 Routing Table - 4 entries

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 13

 Codes: C - Connected, L - Local, S - Static, R - RIP, B - BGP
U - Per-user Static route
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 2001:DB9:1:1::/64 [0/0]
via ::, GigabitEthernet1
L 2001:DB9:1:1::1/128 [0/0]
via ::, GigabitEthernet1
L FE80::/10 [0/0]
via ::, Null0
L FF00::/8 [0/0]
via ::, Null0

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 14

Task 3: Configure Static IPv6 Addressing and
Routing on a PC That Runs the Windows 10
Operating System
In this task, you will configure a static IPv6 address on your PC.

Activity Procedure
Complete the following steps:
Step 1 Connect to PC1 and open a command-prompt window. Verify the list of
interfaces.
Step 2 Add a static IPv6 address to the LAB interface. Obtain the address from the Job
Aids section.
Use the netsh interface ipv6 add address “LAB” 2001:db9:1:1::f
Step 3 Add a static default IPv6 route to point to router R1.
Use the netsh interface ipv6 add route ::/0 “LAB” 2001:db9:1:1::1

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 15

Activity Verification
You have completed this task when you attain these results using the command window and using
ipconfig command, alternatively you could use the GUI configuration:
 On PC1, again verify the IPv6 status of the LAB interface.

 Review the IPv6 routing table.

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 16

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 17
  Test the IPv6 connectivity to router R1.
C:\Users\Admin>ping6 2001:db9:1:1::1

Pinging 2001:db9:1:1::1 with 32 bytes of data:

Reply from 2001:db9:1:1::1: bytes=32 time=6ms
Reply from 2001:db9:1:1::1: bytes=32 time<1ms
Reply from 2001:db9:1:1::1: bytes=32 time<1ms
Reply from 2001:db9:1:1::1: bytes=32 time<1ms

Ping statistics for 2001:db9:1:1::1:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

 On R1, test the IPv6 connectivity to PC1.

R1#ping ipv6 2001:db9:1:1::f

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 2001:DB9:1:1::F, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/1/4 ms

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 18

Task 4: Configure Static IPv6 Addressing and
Routing on a PC That Runs the Linux Operating
System
In this task, you will configure a static IPv6 address on your PC.

Activity Procedure
Complete the following steps:
Step 1 Connect to Ubuntu PC and log in by using the username and password that are
specified in the Job Aids section.
Step 2 Open a Terminal window.

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 19

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 20
Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 21
 Step 3 Review the current network interface configuration.
Step 4 Add IPv4 if needed.

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 22

Activity Verification
You have completed this task when you attain these results:
 Examine the network interface configuration:

 Test the IPv4 connectivity to router R1.

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 23

 Step 5 Add an IPv6 addresses to the network interface from the GUI. Review the Job
Aids section for address information.

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 24

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 25
Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 26
 Click the green “Apply” button on the top right corner. This will bring you back to the
settings screen. Click on the gear icon once more.

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 27

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 28
 In the details tab, confirm your settings:

Note that Ubuntu automatically privatizes the IPv6 address.

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 29

  Test the IPv6 connectivity to router R1.

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 30

Discovery Lab 1 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 31
Discovery Lab 2:
Using Neighbor Discovery
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will configure router advertisements and adjust parameters that are associated with
neighbor discovery. After completing this activity, you will be able to meet these objectives:
 Configure a router to send router advertisements.
 Renumber a local network.

Discovery Lab 2 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 32

Visual Objective
The figure illustrates what you will accomplish in this activity.

Required Resources
The table lists the resources and equipment that are required to complete this activity.

Device Name Device Role in the Laboratory

R1 Access router for PC1; used as a default gateway for IPv4 and IPv6 traffic.

PC1 End user with applications that require both IPv4 and IPv6 support by the
operating system and the network.

Discovery Lab 2 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 33

Command List
The table describes the commands that are used in this activity.

Cisco IOS Software Commands

Command Description

debug ipv6 nd Displays debug messages for IPv6 ICMP

neighbor discovery transactions.

ipv6 address ipv6-address Configures an IPv6 address on an interface.

ipv6 nd prefix ipv6-prefix/prefix- Configures an IPv6 prefix advertisement; allows

length [valid-lifetime preferred- control over the individual parameters per prefix.
lifetime]
ipv6 nd ra-interval maximum-secs Configures the interval between IPv6 router
advertisement transmissions on an interface.

ipv6 nd ra suppress Suppresses IPv6 router advertisement

transmissions on a LAN interface.

ping ipv6 ipv6-address Diagnoses basic network connectivity when

using IPv6.

undebug all Disables all debugging processes.

Windows PC Commands

Command Description

netsh interface ipv6 add address Assigns IPv6 address to an interface.

interface ipv6-address
netsh interface ipv6 delete Removes an IPv6 address from a given
address interface ipv6-address interface.

ipconfig Displays interface configuration information.

Job Aids
These job aids are available to help you complete the lab activity:
 The instructor will provide you with your pod number and other pod-access information. Log this
information in the table.

Pod-Access Information

Parameter Value

Your pod number

Discovery Lab 2 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 34

 Parameter Value

Username on router R1 —

Password on router R1 —

Username on PC1 Admin

Password on PC1 ISEisC00L

Note Router R1 is preconfigured to allow access without any credentials. Any Telnet session or console
access will automatically give you access to privileged mode.

 The table illustrates the IPv4 and IPv6 addressing scheme that is used in this lab exercise.

Pod Addressing

Device Interface IPv4 Address and Mask IPv6 Address and Mask

R1 GigabitEthernet 1 192.168.1.1/24 2001:db9:1:1::1/64

2001:db9:1:1001::1/64

PC1 LAB 192.168.1.2/24 2001:db9:1:1::f/64

2001:db9:1:1001::f/64

Discovery Lab 2 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 35

Task 0: Reset the Router for this Lab
In this task, you will reset the router(s) for the beginning of this lab. The process is using a configure
restore option within IOS. There are command aliases already configured as the baseline of the routers
and they reference configurations found in flash.

Activity Procedure
Complete the following steps:
Step 1 Connect to Router 1 (R1) and get to privileged mode.
Step 2 Type lab-2-2 and type Y to confirm.

Discovery Lab 2 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 36

Task 1: Configure Router Advertisements
In this task, you will configure router R1 to start sending router advertisements and to allow the client
PC1 to learn its IPv6 address dynamically.

Activity Procedure
Complete the following steps:
Step 1 Connect to PC1 and log in by using the credentials that are listed in the Job Aids
section. Verify the statically configured IPv6 address.
Step 2 Open the command prompt and remove the static IPv6 address from your PC
(use the LAB interface index and the static prefix).
Step 3 On the GigabitEthernet 1 interface, configure router advertisements by using the
prefix that is assigned to the LAN (refer to the Job Aids section). Because infinite
lifetimes are not desired, use 5 minutes (300 seconds) for the lifetimes (both
preferred and valid).
Step 4 Also set the advertisement interval to 30 seconds.
Step 5 On R1, enable the debugging of IPv6 neighbor discovery events.
Step 6 Stop suppressing the router advertisements, which were disabled in the initial
configuration.

Activity Verification
You have completed this task when you attain these results:
 On R1, observe the debugging output after enabling router advertisements.
04:10:47: ICMPv6-ND: Request to send RA for FE80::217:59FF:FE26:3FE0
04:10:47: ICMPv6-ND: Sending RA from FE80::217:59FF:FE26:3FE0 to FF02::1 on
FastEthernet0/0
04:10:47: ICMPv6-ND: MTU = 1500
04:10:47: ICMPv6-ND: prefix = 2001:DB9:1:1::/64 onlink autoconfig
04:10:47: ICMPv6-ND: 300/300 (valid/preferred)

 On PC1, verify that an IPv6 address was automatically assigned to the PC with the prefix that
you configured. Note that the previously configured static and link-local addresses are still
present and valid.

Note If you want to turn off the temporary address type (the default behavior), apply the netsh interface
ipv6 set privacy state=disabled command before a new IPv6 address is assigned to your PC.
(Disable and re-enable the interface.)

Discovery Lab 2 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 37

  Verify connectivity from R1 to PC1 by using the newly assigned IPv6 autoconfigured address of
the PC.
R1#ping ipv6 2001:db9:1:1:20c:29ff:fee0:651d

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 2001:DB9:1:1:20C:29FF:FEE0:651D,
timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/1/4
ms

Discovery Lab 2 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 38

Task 2: Renumber the Local Network
In this task, you will reconfigure router advertisements to add addresses and adjust prefix parameters
(valid and preferred lifetimes).

Activity Procedure
Complete the following steps:
Step 1 On R1, replace address of the GigabitEthernet 1 interface by using the new
global prefix that is assigned to your pod: 2001:db9:1:1001::1/64.
Step 2 Configure router advertisements by using the new /64 prefix that is identified for
your pod. Use 5 minutes (300 seconds) for both preferred and valid lifetimes.
Step 3 Modify the neighbor advertisements for the original prefix that is advertised, by
setting the preferred lifetime to zero.

Activity Verification
You have completed this task when you attain these results:
 Verify that PC1 now deprecates the use of the former prefix and prefers the new one.

 On R1, verify connectivity to PC1 by using the new autoconfigured address of PC1.
R1#ping ipv6 2001:db9:1:1001:<use workstation suffix>

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 2001:DB9:1:1001:<use workstation suffix>,
timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 0/1/4 ms

 On R1, turn off debugging using the command: u all ( undebug all )

Discovery Lab 2 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 39

  On PC1, reset the IPv6 configuration to the LAB interface to the static configuration provided at
the beginning of the exercise.

Discovery Lab 2 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 40

Discovery Lab 3:
Using Prefix Delegation
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will configure a DHCPv6 server to delegate a prefix to a DHCPv6 client. After
completing this activity, you will be able to meet these objectives:
 Configure the prefix delegation server and client.
 Configure a non-prefix delegation DHCPv6 server.

Discovery Lab 3 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 41

Visual Objective
The figure illustrates what you will accomplish in this activity.

Required Resources
The table lists the resources and equipment that are required to complete this activity.

Device Name Device Role in the Laboratory

R1 Access router in Site 1; used as the default gateway for IPv4 and IPv6 traffic.

R2 Access router in Site 2; used as the default gateway for IPv4 and IPv6 traffic.

PC1 End user with applications that require both IPv4 and IPv6 support by the
operating system and the network.

PC2 End user with applications that require both IPv4 and IPv6 support by the
operating system and the network.

Discovery Lab 3 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 42

Discovery Lab 3 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 43
Command List
The table describes the commands that are used in this activity.

Cisco IOS Software Commands

Command Description

ipv6 dhcp client pd name Enables DHCP for the IPv6 client process and
enables a request for prefix delegation through a
specified interface.

ipv6 dhcp pool name Configures DHCP for IPv6 server configuration-
information pool and enters DHCP for IPv6 pool
configuration mode.

ipv6 dhcp server name Enables DHCP for IPv6 service on an interface.

ipv6 local pool name prefix prefix- Configures a local IPv6 prefix pool.
length hex-string
ipv6 nd other-config-flag Sets the “other stateful configuration” flag in IPv6
router advertisements and indicates to the
attached hosts how they can obtain
autoconfiguration information other than
addresses (dns-server information).

ipv6 route Establishes static IPv6 routes.

prefix-delegation Specifies a manually configured numeric prefix to

be delegated to a specified client and (optionally)
a specified identity association for prefix
delegation (IAPD) for that client.

show ipv6 dhcp Displays the DUID on a specified device.

show ipv6 dhcp binding Displays automatic client bindings from DHCP for
the IPv6 server binding table.

show ipv6 dhcp pool Displays DHCP for IPv6 configuration pool
information.

show ipv6 interface Displays the usability status of interfaces that are
configured for IPv6.

Windows PC Commands

Command Description

netsh interface ipv6 renew Renews the configuration of one or all interfaces.
[intfName]
netsh interface ipv6 show interface Displays a list of interfaces or details for a
[ifix] specific interface.

Discovery Lab 3 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 44

Discovery Lab 3 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 45
Job Aids
These job aids are available to help you complete the lab activity:
 The instructor will provide you with your pod number and other pod-access information. Log this
information in the table.

Pod-Access Information

Parameter Value

Your pod number

Username on router R1 —

Password on router R1 —

Username on router R2 —

Password on router R2 —

Username on PC1 Admin

Password on PC1 ISEisC00L

Username on PC2 Admin

Password on PC2 ISEisC00L

Note Routers R1 and R2 are preconfigured to allow access without any credentials. Any Telnet session
or console access will automatically give you access to privileged mode.

The table illustrates the IPv4 and IPv6 addressing scheme that is used in this lab exercise.

Pod Addressing

Device Interface IPv4 Address and Mask IPv6 Address and Mask

R1 GigabitEthernet 1 192.168.1.1/24 2001:db9:1:1::1/64

R1 GigabitEthernet 2 192.168.101.1/30 2001:db9:1:a::1/64

R2 GigabitEthernet 1 192.168.2.1/24 2001:db9:1:2::1/64

R2 GigabitEthernet 2 192.168.101.2/30 2001:db9:1:a::2/64

PC1 LAB 192.168.1.2/24 2001:db9:1:1::f/64

PC2 LAB 192.168.2.2/24 2001:db9:1:2::f/64

Discovery Lab 3 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 46

Task 0: Reset the Router for this Lab
In this task, you will reset the router(s) for the beginning of this lab. The process is using a configure
restore option within IOS. There are command aliases already configured as the baseline of the routers
and they reference configurations found in flash.

Activity Procedure
Complete the following steps:
Step 1 Connect to Router 1 (R1) and get to privileged mode.
Step 2 Type Lab-3-1 and type Y to confirm.

Step 3 Repeat the action on Router 2 (R2).

Discovery Lab 3 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 47

Task 1: Configure a Prefix Delegation Server and
Client
In this task, you will configure router R1 to be a prefix delegation server. You will also configure router
R2 to be a prefix delegation client and (optionally) a DHCPv6 server for the local LAN in Site 2.

Activity Procedure
Complete the following steps:
Step 1 On R1, configure a local IPv6 prefix pool.
Step 2 Create a DHCPv6 pool named GlobalDHCP for the prefix delegation server by
using the parameters that are listed in the table.

Prefix Delegation Server Parameters

Parameter Value

Prefix for delegation to router R2 2001:db9:1:2::/64

Domain name example.com

DNS server address 2001:db9:1:1::abba

Step 3 Configure the GigabitEthernet 2 interface to act as a DHCPv6 prefix delegation

server.

Discovery Lab 3 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 48

 Step 4 On R2, configure the GigabitEthernet 2 interface as a prefix delegation client.
The interface must be instructed to use DHCPv6 prefix delegation to obtain a
prefix, and you must also give the prefix a logical name (Site2Prefix).
Step 5 Configure the GigabitEthernet 1 interface with IPv6 addresses that are learned
from the DHCPv6 server. Construct both a manually configured address (::1) and
an autoconfigured address. Use the previously defined name Site2Prefix to refer
to the DHCPv6 client that you configured on interface GigabitEthernet 2.
On GigabitEthernet 1, send router advertisements and set the valid lifetime to
1200.

Step 6 In a typical deployment, the DHCPv6 client router will, upon receiving a prefix,
configure local interfaces with new addresses and possibly send router
advertisements to clients that are downstream so that they can configure IPv6
addresses.

Activity Verification
You have completed this task when you attain these results:
 On R2, review the prefix delegation client interface status. The GigabitEthernet 1
interface has taken the network address from the DHCPv6 server-supplied prefix.

Discovery Lab 3 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 49

  Verify the status of the DHCPv6 prefix delegation interface.

 On R1, review the DCHPv6 prefix delegation status. Now that the client has made a prefix
request, the delegated prefix should be listed.

Discovery Lab 3 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 50

  On PC2, check the LAB interface for the new address, and verify that the PC has
autoconfigured an IPv6 address from the advertised prefix. Note that there is another static IPv6
address of 2001:db9:2:1::f on PC2, do not remove it, it is used in later labs.

Note If the Windows 10 machine had a DHCPv6 client, the router advertisement would instruct the PC to
solicit for other configuration information from a DHCPv6 server (not a DHCPv6 prefix delegation
server).

Discovery Lab 3 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 51

  Verify the reachability of PC2 from PC1. Use the dynamically assigned address.

Note Static routes have been preconfigured to enable the reachability between the two sites.

 Verify the path from PC1 to PC2. Use the dynamically assigned address.

Discovery Lab 3 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 52

  Optionally, you may enable DHCPv6 debugging on R1 and R2.

 Trigger a new DHCP reservation on R2.

Discovery Lab 3 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 53

Discovery Lab 3 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 54
Task 2: Configure a Non-Prefix Delegation DHCPv6
Server
DHCPv6 prefix delegation client routers often run, in turn, as DHCPv6 stateless servers for downstream
devices. In this task, the client router will provide that function.

Note The Windows 10 client does not have a DHCPv6 client. Therefore, your PC will not actually make
any requests to your router.

Activity Procedure
Complete the following steps:
Step 1 On R2, configure a DHCPv6 server pool named SITE2 by using the parameters
that are listed in the table.

DHCPv6 Server Pool Parameters

Parameter Value

Domain name site2.example.com

DNS server address 2001:db9:1:2::beef

Step 2 Configure the GigabitEthernet 1 interface as a DHCPv6 stateless server. Send

the other configuration information flag in the router advertisement. Add the
IPv6 address of 2001:db9:2:1::1/64 (note that it is 2:1, rather than 1:2).

Discovery Lab 3 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 55

Activity Verification
You have completed this task when you attain these results:
 On R2, examine the DHCPv6 server running on the GigabitEthernet 1 interface. With no
DHCPv6 client on your PC, there should be no active clients.

 Verify that the interface is in DHCPv6 server mode.

Discovery Lab 3 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 56

  Verify that PC2 is getting the additional information.

Discovery Lab 3 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 57

Discovery Lab 3 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 58
Discovery Lab 4:
Deploy HSRP for IPv6
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will enable HSRP for IPv6 on the Cisco IOS routers R1 and R4. After completing this
activity, you will be able to meet the following objectives:
 Configure IPv6 first hop redundancy using Hot Standby Routing Protocol.
 Configure R1 such that it will be the active router using priority.
 Configure R4 such that it will become the active router in the event of a link failure on R1.
 Configure HSRP IPv6 to use the burnt-in-address (mac) of the current Active Router.

Discovery Lab 4 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 59

Visual Objective
The figure illustrates what you will accomplish in this activity.

Visual Objective for Lab 2-1: Enabling

IPv6 on Hosts ISPv6 (R9)

PC3

PE3 (R6) ISPv4 (R8)

PC2

P (R3) PE1 (R5) A1v4 (R7)

A3v6 (R2) R1
A2v6 (R4)

Static Addressing
PC1 Linux

© 2010 Cisco Systems, Inc. All rights reserved. IP6FD v3.0—LG-2

The lab environment is set up so that IPv4 is already configured on router R1. Configure Windows 10
on PC1 for IPv4 so that you can use Telnet to connect to the router.

Required Resources
The table lists the resources and equipment that are required to complete this activity.

Device Name Device Role in the Laboratory

R1 First point of egress from the network 2001:DB9:1:1::/64.

R4 Second point of egress from the network 2001:DB9:1:1::/64.

Discovery Lab 4 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 60

 Device Name Device Role in the Laboratory

PC1 End user with applications that require IPv6 first hop redundancy for the
gateway 2001:DB9:1:1::1 through either R1 or R4 (preferring R1).

Command List
The table describes the commands that are used in this activity.

Cisco IOS Software Commands

Command Description

ipv6 address prefix Configures a static IP address on an interface.

ipv6 enable Enables an interface for IPv6.

ipv6 nd ra suppress Suppresses IPv6 router advertisement

transmissions on a LAN interface.

ipv6 unicast-routing Enables IPv6 routing.

show ip interface brief Shows brief IPv4 interface information.

show ip route Shows the IPv4 routing table.

show ipv6 interface brief Shows brief IPv6 interface information.

show ipv6 route Shows the IPv6 routing table.

Microsoft Windows PC Commands

Command Description

netsh interface ip set address Configures the IPv4 address, mask, and default
int_name static ip_addr net_mask gateway to the interface named int_name.
def_gw 1
netsh interface ipv6 add address Adds an IPv6 address to an interface on
int_name ipv6_address Microsoft Windows 10.

netsh interface ipv6 add route Adds a route for a specified prefix.
route int_name next-hop
netsh interface ipv6 show interface Displays Windows 10 interfaces.
[intf]
ping Enters the ping command from Windows 10.

ping6 Enters the ping6 command from Windows 10.

Note You can get detailed help if you type a question mark at the end of the netsh commands; for
example, netsh interface ipv6 add address ?.

Discovery Lab 4 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 61

Linux PC Commands

Command Description

ifconfig Displays all network interface information that

has been configured.

ping Enters the ping command.

ping6 Enters the ping6 command.

Job Aids
These job aids are available to help you complete the lab activity:
 The instructor will provide you with your pod number and other pod-access information. Log this
information in the table.

Pod-Access Information

Parameter Value

Your pod number

Username on router R1 & R4 —

Password on router R1 & R4 —

Username on PC1 Admin

Password on PC1 ISEisC00L

Note Router R1 and R4 is preconfigured to allow access without any credentials. Any Telnet session or
console access will automatically give you access to privileged mode.

The table illustrates the IPv4 and IPv6 addressing scheme that is used in this lab exercise.

Pod Addressing

Device Interface IPv4 Address and Mask IPv6 Address and Mask

R1 GigabitEthernet1 192.168.1.1/24 2001:db9:1:1::11/64

R4 GigabitEthernet2 2001:db9:1:1::14/64

PC1 LAB 192.168.1.2/24 2001:db9:1:1::f/64

Discovery Lab 4 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 62

Task 0: Reset the Router for this Lab
In this task, you will reset the router(s) for the beginning of this lab. The process is using a configure
restore option within IOS. There are command aliases already configured as the baseline of the routers
and they reference configurations found in flash.

Activity Procedure
Complete the following steps:
Step 1 Connect to Router 1 (R1), Router 3 (R3), Router 4 (R4) and Router 5 (R5) and
get to privileged mode.
Step 2 Type HSRP and type Y to confirm. The illustration below shows this process on
R1 (you will need to execute the same command on all the routers outline in Step
1).

To confirm, do a show ipv6 interface brief and you should see that there is now
an ipv6 address on interface GigabitEthernet1 that is 2001:DB9:1:1::11/64.

Discovery Lab 4 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 63

Task 1: Verify IPv6 Reachability from PC1
In this task, you will confirm that your PC has the necessary IPv6 configuration information to establish
connectivity in the lab topology.

Activity Procedure
Complete the following steps:
Step 1 Connect to PC1 and open a command-prompt window. Verify the list of
interfaces.
Step 2 Test reachability to both R1 and R6 using there ipv6 addresses.
Use the ping 2001:1:1::11 and ping 2001:1:1::14 command.

Step 3 Now test reachability to the default gateway of 2001:db9:1:1::1.

Use the ping 2001:db9:1:1::1 command.
This ping should fail at this time.

Step 4 Make note of the Physical Addresses for the two tested IPv6 addresses. Also
note that the prospective gateway address 2001:db9:1:1::1 is Unreachable.

Discovery Lab 4 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 64

 Use the netsh interface ipv6 show neighbor command.

Step 5 Open a session to R1 and apply the following configuration.

Step 6 Open a session to R4 and apply the following configuration.

Discovery Lab 4 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 65

 Step 7 Now we will need to validate which device (R1 or R4) is the “Active Router” and
which is the “Standby”.
On R1 execute the “show standby” command.

Step 8 Make note that R1 is the Active Router in this scenario, and it is using the “virtual
MAC” address of 0050.56a0.7370 matching the physical MAC address of this
interface.
Step 9 We will now repeat the “show standby” command on R4.

Discovery Lab 4 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 66

 Step 10 In the output of R4 we see that this device sees itself as the Standby Router, and
it agrees that R1 is the Active router. This is because the priority of R1 is 120 and
the local priority on R4 is the default of 100. This means that the group will prefer
to select R1 as the Active Router.
Now we will verify that PC1 can ping the IPv6 gateway of 2001:db9:1:1::1 where
it could not do so before.

Step 11 Next, using netsh we will verify that the correct MAC address is being learned.
Use the netsh interface ipv6 show neighbor command.

Discovery Lab 4 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 67

 Step 12 Note that the Physical address 2001:db9:1:1::1 is the same as R1 with an ipv6
address of 2001:db9:1:1::11

Discovery Lab 4 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 68

Activity Verification
You have completed this task when you attain these results by shutting down the GigabitEthernet 1 on
R1:
Step 1 Open a console session to R1, navigate to GigabitEthernet 1 and shutdown the
interface.

Step 2 Verify that you see a message like the following which indicates that the device
has transitioned from the Active state to the Init (due to the loss of
communication to R4):

Step 3 Next open console to R4 and validate that this device is indeed the Active
Forwarder now by observing the Syslog Console Messages and by using the
show standby command.

Discovery Lab 4 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 69

 Step 4 Now return to the terminal session running on PC1 and repeat the netsh
interface ipv6 show neighbor command.

Discovery Lab 4 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 70

 Step 5 In the current output you should see that the Physical Address has changed to
the same address used for 2001:db9:1:1:14 which is now the active router in the
HSRP deployment.
Step 6 Lastly, we will test using ping to validate reachability to 2001:db9:1:1::1.

Discovery Lab 4 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 71

Discovery Lab 5:
Routing with OSPFv3
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will configure, operate, and monitor an OSPF routing environment. You will
configure the protocol and examine detailed information about how it works. After completing this
activity, you will be able to meet these objectives:
 Configure OSPF.
 Summarize route announcements.

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 72

Visual Objective
The figure illustrates what you will accomplish in this activity.

Required Resources
The table lists the resources and equipment that are required to complete this activity.

Device Name Device Role in the Laboratory

R1 Access router in the Central Site; used as the default gateway for IPv4 and
IPv6 traffic.

R2 Access router in the Remote Site; used as the default gateway for IPv4 and
IPv6 traffic.

PC1 End user with applications that require both IPv4 and IPv6 support by the
operating system and the network.

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 73

 Device Name Device Role in the Laboratory

PC2 End user with applications that require both IPv4 and IPv6 support by the
operating system and the network.

Command List
The table describes the commands that are used in this activity.

Cisco IOS Software Commands

Command Description

area area-id range ipv6- Configures route summarization at an area

prefix /prefix-length boundary.

clear ipv6 ospf Clears the OSPF state, based on the OSPF
routing process ID.

debug ipv6 ospf Displays important OSPFv3 events for IPv6.

ipv6 ospf process-id area area-id Enables OSPF for IPv6 on an interface.

ipv6 router ospf Enables legacy OSPF router configuration mode.

log-adjacency-changes [detail] Configures the router to send a syslog message

when an OSPF neighbor goes up or down.

router ospfv3 process-id Current syntax for OSPF version 3.

ospv3 process-id {ipv6 | ipv4} area

area-number
router-id ip-address Uses a fixed router ID.

show ipv6 interface [brief] Displays the brief usability status of interfaces
that are configured for IPv6.

show ipv6 ospf Displays information about OSPF routing

processes.

show ipv6 route Displays the current contents of the IPv6 routing
table.

Windows PC Commands

Command Description

ping Sends pings from Windows 10.

tracert Discovers and displays the path that a packet

takes through the network.

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 74

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 75
Job Aids
These job aids are available to help you complete the lab activity:
 The instructor will provide you with your pod number and other pod-access information. Log this
information in the table.

Pod-Access Information

Parameter Value

Your pod number

Username on router R1 —

Password on router R1 —

Username on router R2 —

Password on router R2 —

Username on PC1 Admin

Password on PC1 ISEisC00L

Username on PC2 Admin

Password on PC2 ISEisC00L

Note Routers R1 and R2 are preconfigured to allow access without any credentials. Any Telnet session
or console access will automatically give you access to privileged mode.

The table illustrates the IPv4 and IPv6 addressing scheme that is used in this lab exercise.

Pod Addressing

Device Interface IPv4 Address and IPv6 Address and

Mask Mask

R1 GigabitEthernet1 192.168.1.1/24 2001:db9:1:1::1/64

R1 GigabitEthernet2 192.168.101.1/30 2001:db9:1:a::1/64

R1 Loopback 1 Unassigned 2001:db9:1:100::1/64

R1 Loopback 2 Unassigned 2001:db9:1:200::1/64

R2 GigabitEthernet1 192.168.2.1/24 2001:db9:2:1::1/64

R2 GigabitEthernet2 192.168.101.2/30 2001:db9:1:a::2/64

R2 Loopback 1 Unassigned 2001:db9:2:100::1/64

R2 Loopback 2 Unassigned 2001:db9:2:200::1/64

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 76

 Device Interface IPv4 Address and IPv6 Address and
Mask Mask

PC1 LAB 192.168.1.2/24 2001:db9:1:1::f/64

PC2 LAB 192.168.2.2/24 2001:db9:2:1::f/64

Task 0: Reset the Router for this Lab

In this task, you will reset the router(s) for the beginning of this lab. The process is using a configure
restore option within IOS. There are command aliases already configured as the baseline of the routers
and they reference configurations found in flash.

Activity Procedure
Complete the following steps:
Step 1 Connect to Router 1 (R1) and get to privileged mode.
Step 2 Type lab-4-1 and type Y to confirm.

Step 3 Repeat the action on Router 2 (R2).

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 77

Task 1: Configure OSPF
OSPF is a link-state protocol that is used inside an AS. You will configure OSPF to exchange routes
between the Central Site and the Remote Site.

Activity Procedure
Complete the following step:
Step 1 Configure OSPF on routers R1 and R2 by using the parameters that are listed in
the table. Enable OSPFv3 for IPv6 using the legacy ipv6 router ospf 1 and
ipv6 ospf 1 area x commands.

OSPF Parameters

Parameter R1 R2

Process ID 1 1

Router ID 192.168.1.1 192.168.2.1

Area 0 GigabitEthernet1 —
Loopback 1
Loopback 2

Area 1 GigabitEthernet2 GigabitEthernet1

GigabitEthernet2
Loopback 1
Loopback 2

Activity Verification
You have completed this task when you attain these results:
 On R1, review the OSPF process details. The output should show router R1 as an “area border
router” because two areas are configured.

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 78

  On R2, review the OSPF process details. The output should show router R2 as a regular intra-
area router because all interfaces are in the same area (Area 1).

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 79

  On R1, conduct a more detailed review of the OSPF configuration for IPv6.

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 80

  Review the contents of the IPv6 routing table on R1 and R2. You will notice that R1 sees all R2
routes as intra-area (O) routes, whereas R2 sees all R1 routes as interarea (OI) routes.

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 81

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 82
  Review the OSPF neighbor relationships on R1 and R2.

 Check the OSPF neighbor details on R1 and R2.

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 83

  On PC1, test IPv6 reachability of PC2 (use IPv6 address 2001:db9:2:1::f).

 Verify the IPv6 path between PC1 and PC2.

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 84

  OSPF neighbors send hello messages at intervals to keep track of active neighbors. Display the
exchange of OSPF hello messages.

 OSPF neighbors also exchange LSAs and other information whenever the state of the network
topology changes. Trigger the re-establishment of OSPF neighbor relationships.
R1#debug ipv6 ospf flood
R1#clear ipv6 ospf process
 You can also watch the OSPF adjancies form by running the debug ipv6 ospf adj command.
Once you are done looking at the process, disable all debugging by using the undebug all
command.

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 85

Task 2: Summarize Route Announcements
OSPF supports route summarization: the ability to consolidate the routing information of multiple
networks (which would result in multiple small route entries) into one or a few larger prefixes. In this
task, you will summarize route announcements.

Activity Procedure
Complete the following step:
Step 1 Configure summarization of the address space of Area 0 for other areas. Create
a summary 2001:db9:1::/48 in Area 0 on R1.

Activity Verification
You have completed this task when you attain these results:
 Review the contents of the IPv6 routing table on R2 to determine whether only the summary is
advertised by Area 0 (R1).

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 86

 Note If one of the loopback interfaces is removed, the summary configuration prevents any change to
the OSPF routes that are announced. Also notice that a /48 route is set to Null for the loopback
networks of your pod.

Note In OSPFv3, the router uses the 32-bit IPv4 address to select the router ID for an OSPF process. If
an IPv4 address exists when OSPFv3 is enabled on an interface, then that IPv4 address is used
for the router ID. If more than one IPv4 address is available, a router ID is chosen using the same
rules as for OSPF version 2.

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 87

Task 3: Replace all Routing with OSPFv3
Starting with RFC 5838, OSPFv3 supports address families. OSPFv3 ride over IPv6, but can now
advertise IPv4 routes as well as the IPv6 routes. In this task you will replace RIP for IPv4 and OSPFv3
legacy configuration for the new syntax to support both IPv4 and IPv6. Note that IPv4 address still
needs be in the complete path to pass traffic.

Activity Procedure
Complete the following steps:
Step 1 Remove router rip and ipv6 route ospf on R1 and R2.
Step 2 On interface Loopback 1 of router R1, add the address of 192.168.11.1/24 and
on router R2 add 192.168.22.2/24.
Step 3 Configure router ospfv3 1 on R1 and R2. Enable the process on all the
interfaces as detailed in the following table:

Parameter R1 R2

Process ID 1 1

Router ID 192.168.1.1 192.168.2.1

Area 0 GigabitEthernet1 —
Loopback 1

Area 1 GigabitEthernet2 GigabitEthernet1

GigabitEthernet2
Loopback 1

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 88

Activity Verification
You have completed this task when you attain these results (this can be done on either R1 or R2):

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 89

 Note The command to see the IPv4 routes from OSPFv3 is show ip route ospfv3. The command to see
the IPv6 routes is show ipv6 route ospf.

Verify that PC1 can still ping PC1 for both IPv4 and IPv6.

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 90

Discovery Lab 5 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 91
Discovery Lab 6:
Routing with EIGRP
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will reconfigure the lab environment for EIGRP and examine the operation of the
protocol. After completing this activity, you will be able to meet these objectives:
 Configure EIGRP for IPv6 routing.
 Configure EIGRP for IPv6 summarization.

Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 92

Visual Objective
The figure illustrates what you will accomplish in this activity.

Required Resources
The table lists the resources and equipment that are required to complete this activity.

Device Name Device Role in the Laboratory

R1 Access router in the Central Site; used as the default gateway for IPv4 and
IPv6 traffic.

R2 Access router in the Remote Site; used as the default gateway for IPv4 and
IPv6 traffic.

PC1 End user with applications that require both IPv4 and IPv6 support by the
operating system and the network.

Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 93

 Device Name Device Role in the Laboratory

PC2 End user with applications that require both IPv4 and IPv6 support by the
operating system and the network.

Command List
The table describes the commands that are used in this activity.

Cisco IOS Software Commands

Command Description

eigrp router-id router-id Configures a static router ID for an EIGRP

process.

ipv6 eigrp AS Enables an IPv6 EIGRP routing process on an

interface.

ipv6 router eigrp AS Configures an IPv6 EIGRP routing process.

ipv6 summary-address eigrp AS Summarizes IPv6 EIGRP updates that are sent
prefix out of an interface.

router eigrp name Enables the named version of EIGRP.

passive-interface Disables EIGRP on an interface but inserts the

interface network into the EIGRP topology table.

show ipv6 eigrp interfaces Displays the EIGRP interface status.

show ipv6 eigrp neighbors Displays the EIGRP neighbor relationships.

show ipv6 eigrp topology Displays the EIGRP database.

show ipv6 route Displays the current contents of the IPv6 routing
table.

Windows PC Commands

Command Description

ping Sends pings from Windows 10.

tracert Discovers and displays the path that a packet

takes through the network.

Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 94

Job Aids
These job aids are available to help you complete the lab activity:
 The instructor will provide you with your pod number and other pod-access information.
Log this information in the table.

Pod-Access Information

Parameter Value

Your pod number

Username on router R1 —

Password on router R1 —

Username on router R2 —

Password on router R2 —

Username on PC1 Admin

Password on PC1 ISEisC00L

Username on PC2 Admin

Password on PC2 ISEisC00L

Note Routers R1 and R2 are preconfigured to allow access without any credentials. Any Telnet session
or console access will automatically give you access to privileged mode.

 The table illustrates the IPv4 and IPv6 addressing scheme that is used in this lab exercise.

Pod Addressing

Device Interface IPv4 Address and Mask IPv6 Address and Mask

R1 GigabitEthernet 192.168.1.1/24 2001:db9:1:1::1/64

1

R1 GigabitEthernet 192.168.101.1/30 2001:db9:1:a::1/64

2

R1 Loopback 1 Unassigned 2001:db9:1:100::1/64

R1 Loopback 2 Unassigned 2001:db9:1:200::1/64

R2 GigabitEthernet 192.168.2.1/24 2001:db9:2:1::1/64

1

R2 GigabitEthernet 192.168.101.2/30 2001:db9:1:a::2/64

2

Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 95

 Device Interface IPv4 Address and Mask IPv6 Address and Mask

R2 Loopback 1 Unassigned 2001:db9:2:100::1/64

R2 Loopback 2 Unassigned 2001:db9:2:200::1/64

PC1 LAB 192.168.1.2/24 2001:db9:1:1::f/64

PC2 LAB 192.168.2.2/24 2001:db9:2:1::f/64

Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 96

Task 0: Reset the Router for this Lab
In this task, you will reset the router(s) for the beginning of this lab. The process is using a configure
restore option within IOS. There are command aliases already configured as the baseline of the routers
and they reference configurations found in flash.

Activity Procedure
Complete the following steps:
Step 1 Connect to Router 1 (R1) and get to privileged mode.
Step 2 Type lab-4-3 and type Y to confirm.

Step 3 Repeat the action on Router 2 (R2).

Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 97

Task 1: Configure EIGRP for IPv6 Routing
In this task, you will configure EIGRP for IPv6.

Activity Procedure
Complete the following steps:
Step 1 Configure EIGRP for IPv6 on routers R1 and R2 by using the parameters that are
listed in the table.

EIGRP Parameters

Parameter R1 R2

EIGRP AS 1 1

EIGRP-Enabled GigabitEthernet 1 GigabitEthernet 1

Interfaces
GigabitEthernet 2 GigabitEthernet 2

Passive Interfaces Loopback 1 Loopback 1

Loopback 2 Loopback 2

Router ID 192.168.1.1 192.168.2.1

Step 2 Enable the IPv6 EIGRP process.

Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 98

Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 99
Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 100
Activity Verification
You have completed this task when you attain these results:
 On router R1, examine the EIGRP interface status. You will see that only one EIGRP neighbor
is available via the Gigabitethernet 2 interface.

 Examine the EIGRP neighbor relationship with router R2.

 Examine the EIGRP topology table. You should see all routes: local and remote, including those
that you might not see in the routing table because static and connected routes take
precedence (two LANs, four loopbacks, and the point-to-point link).

Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 101
  Review the IPv6 routing table for EIGRP routes on both routers. You should see three EIGRP
routes (the remote LAN and two loopbacks) on each router.

Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 102
  On PC1, test the reachability of PC2 (use IPv6 address 2001:db9:2:1::f).

 Review the path between PC1 and PC2 (use IPv6 address 2001:db9:2:1::f). Use the -d option to
speed up the response of the traceroute. That disables the reverse DNS lookup from address to
name.

Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 103
Task 2: Configuring EIGRP for IPv6 Summarization
In this task, you will optimize IPv6 EIGRP to send only a summary from the Central Site to the Remote
Site and vice versa.

Activity Procedure
Complete the following steps:
Step 1 On R1, create an EIGRP summary 2001:db9:1::/48 on interface GigabitEthernet2
to propagate only one summary route instead of three more-specific routes.
Step 2 On R2, create an EIGRP summary 2001:db9:2::/48 on interface GigabitEthernet2
to propagate only one summary route instead of three more-specific routes.

Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 104
Activity Verification
You have completed this task when you attain this result:
 Review the IPv6 routing table for EIGRP routes on both routers. You should see only one
EIGRP-learned remote route—the summary—on each router. You will also see an EIGRP route
for the local summary; this route points to the Null interface, to drop packets for unavailable,
more-specific prefixes.

Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 105
Task 3: Configuring Named EIGRP for IPv6 and
IPv4
In this task, you will enable the Named version of EIGRP and configure it to support both IPv4 and
IPv6.

Activity Procedure
Complete the following steps:
Step 1 On R1 and R2, remove router rip for IPv4 and EIGRP for IPv6.
Step 2 On R1 add the following IPv4 addresses to the loopback interfaces:

Loopback 1 192.168.11.1/32

Loopback 2 192.168.12.1/32

Step 3 On R2 add the following IPv4 addresses to the loopback interfaces:

Loopback 1 192.168.21.1/32

Loopback 2 192.168.22.1/32

Step 4 Enable the named version of EIGRP on R1 and R2 using the following
parameters:

EIGRP Parameters

Parameter R1 R2

EIGRP Name Fred Wilma

IPv4 EIGRP AS 4 4

IPv6 EIGRP AS 6 6

EIGRP-Enabled GigabitEthernet 1 GigabitEthernet 1

Interfaces
GigabitEthernet 2 GigabitEthernet 2

Passive Interfaces Loopback 1 Loopback 1

Loopback 2 Loopback 2

Router ID 192.168.1.1 192.168.2.1

Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 106
Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 107
 Note There is no configuration done at the interface level for IPv6, it is automatic with Topology base
(default) to include all interface with IPv6 addressing applied.

Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 108
Activity Verification
You have completed this task when you attain this result:

Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 109
Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 110
Discovery Lab 6 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 111
Discovery Lab 7: Routing with
BGP and MP-BGP
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will configure iBGP and eBGP for IPv6. BGP is used for inter-AS route propagation
throughout the Internet and within large enterprise and ISP networks. iBGP is used between different
parts of the same AS, and eBGP is used between AS networks. After completing this activity, you will
be able to meet these objectives:
 Configure iBGP for IPv6.
 Configure eBGP for IPv6.
 Configure IPv6 prefix filtering in BGP.

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 112
Visual Objective
The figure illustrates what you will accomplish in this activity.

Required Resources
The table lists the resources and equipment that are required to complete this activity.

Device Device Role in the Laboratory

Name

R1 Access router in the Central Site; used as the default gateway for IPv4 and IPv6 traffic.

R2 Access router in the Remote Site; used as the default gateway for IPv4 and IPv6 traffic.

ISP An ISP router that connects end customers.

PC1 End user with applications that require both IPv4 and IPv6 support by the operating
system and the network.

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 113
 Device Device Role in the Laboratory
Name

PC2 End user with applications that require both IPv4 and IPv6 support by its operating
system and the network.

Server Server on the Internet.

Command List
The table describes the commands that are used in this activity.

Cisco IOS Software Commands

Command Description

address-family ipv6 Enters address family configuration mode for

IPv6.

bgp router-id Configures a fixed router ID for a BGP-speaking

router.

ipv6 address ipv6-address link- Configures an IPv6 link-local address for an

local interface, and enables IPv6 processing on the
interface.

ipv6 prefix-list Creates an entry in an IPv6 prefix list.

neighbor IP activate Enables IPv6 exchange with the peer, when used
in the IPv6 address family.

neighbor IP prefix-list PFL {in | Applies a prefix list for inbound or outbound
out} filtering of BGP updates.

neighbor IP remote-as AS Defines a BGP neighbor.

neighbor IP update-source intf Sources a BGP session from the specified

interface.

no bgp default ipv4-unicast Disables the IPv4 unicast address family on all
neighbors.

route-map name {permit | deny} seq Defines the conditions for redistributing routes
match condition [condition]* from one routing protocol into another and
[match condition [condition]*] enables policy routing or filtering routes.

route-map name {permit | deny} seq Sets the origin code within BGP updates.
set origin {egp | igp |
incomplete}
router bgp Configures the BGP routing process.

router bgp AS Starts the BGP process.

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 114
 Command Description

show bgp ipv6 Displays entries in the IPv6 BGP routing table.

show ipv6 interface Displays the usability status of interfaces that are
configured for IPv6.

show ipv6 route Displays the current content of the IPv6 routing
table.

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 115
Windows PC Commands

Command Description

ping Sends pings from Windows 10 client.

tracert Discovers and displays the path that a packet

takes through the network.

Job Aids
These job aids are available to help you complete the lab activity:
 The instructor will provide you with your pod number and other pod-access information.
Log this information in the table.

Pod-Access Information

Parameter Value

Your pod number

Username on router R1 —

Password on router R1 —

Username on router R2 —

Password on router R2 —

Username on ISP —

Password on ISP —

Username on PC1 Admin

Password on PC1 ISEisC00L

Username on PC2 Admin

Password on PC2 ISEisC00L

Username on Server Admin

Password on Server ISEisC00L

Note Routers R1, R2, and ISP are preconfigured to allow access without any credentials. Any Telnet
session or console access will automatically give you access to privileged mode.

The table illustrates the IPv4 and IPv6 addressing scheme that is used in this lab exercise.

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 116
Pod Addressing

Device Interface IPv4 Address and IPv6 Address and

Mask Mask

R1 GigabitEthernet1 192.168.1.1/24 2001:db9:1:1::1/64

R1 GigabitEthernet2 192.168.101.1/30 2001:db9:1:a::1/64

R1 GigabitEthernet3 Unassigned 2001:db9:1:300::2/64

R1 Loopback 1 Unassigned 2001:db9:1:100::1/64

R1 Loopback 2 Unassigned 2001:db9:1:200::1/64

R2 GigabitEthernet1 192.168.2.1/24 2001:db9:2:1::1/64

R2 GigabitEthernet2 192.168.101.2/30 2001:db9:1:a::2/64

R2 Loopback 1 Unassigned 2001:db9:2:100::1/64

R2 Loopback 2 Unassigned 2001:db9:2:200::1/64

ISP GigabitEthernet1 192.168.3.1/24 2001:db9:10:1::1/64

ISP GigabitEthernet2 Unassigned 2001:db9:1:300::1/64

PC1 LAB 192.168.1.2/24 2001:db9:1:1::f/64

PC2 LAB 192.168.2.2/24 2001:db9:2:1::f/64

Server (PC3) LAB 192.168.3.2/24 2001:db9:10:1::f/64

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 117
Task 0: Reset the Router for this Lab
In this task, you will reset the router(s) for the beginning of this lab. The process is using a configure
restore option within IOS. There are command aliases already configured as the baseline of the routers
and they reference configurations found in flash.

Activity Procedure
Complete the following steps:
Step 1 Connect to Router 1 (R1) and get to privileged mode.
Step 2 Type lab-4-4 and type Y to confirm.

Step 3 Repeat the action on Router 2 (R2) and Router 3 (R3).

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 118
Task 1: Configure IBGP for IPv6
In this task, you will enable BGP to exchange IPv6 routing information between two sites that belong to
AS 65001. The two routers R1 and R2 have been preconfigured with loopback addresses, which are
exchanged by using OSPFv3. These two loopbacks will be used to establish an iBGP session between
the two routers.

Activity Procedure
Complete the following step:
Step 1 Configure iBGP between R1 and R2 by using the parameters that are listed in
the table.

IBGP Parameters

Parameter R1 R2

AS 65001 65001

IPv4 Propagation No No
(enabled by default)
IPv6 Propagation Yes Yes
(disabled by default)
Source Address Loopback 1 Loopback 1

Redistribute into BGP n Connected IPv6 routes n Connected IPv6 routes

n Set origin to IGP n Set origin to IGP

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 119
Activity Verification
You have completed this task when you attain these results:
 On R1, review the status of iBGP sessions. A number in the State/PfxRcd column indicates an
established BGP session (in this case the word wrapping has the 4 on the next line).

 Review the details of the established IBGP session on R1.

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 120
  Review the contents of the BGP table for IPv6 on R1.

 Review the content of the IPv6 routing table on R1. Look for the availability of the remote LAN.
Make the same review on R2.

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 121
  Optionally, you might want to monitor the process of BGP session setup and update exchange.
Enable the debugging of BGP events for the IPv6 address family and clear the BGP sessions.
BGP routing information is not exchanged for a stable network; only routing updates are sent.
On your router, turn on debugging (capture the console output as needed) and start BGP
debugging.
R1#debug bgp ipv6 unicast

R1#debug bgp ipv6 unicast updates

BGP debugging is on for address family: IPv6 Unicast

Note Cisco IOS Software might crash if you turn on debugging and clear the IBGP process on the same
router. For that reason, use R2 to clear the IBGP process, and then observe debug output on R1.

 Clear the iBGP process on R2 (the following is an example output, yours may look different).
R2#clear bgp ipv6 unicast *

R1#
03:13:19: BGP: 2001:DB9:2:100::1 remote close, state CLOSEWAIT
03:13:19: BGP: 2001:DB9:2:100::1 -reset the session
03:13:19: BGP(1): no valid path for 2001:DB9:2:1::/64
03:13:19: BGP(1): no valid path for 2001:DB9:2:100::/64
03:13:19: BGP(1): no valid path for 2001:DB9:2:200::/64
03:13:19: BGPNSF state: 2001:DB9:2:100::1 went from nsf_not_active to
nsf_not_active
03:13:19: BGP: 2001:DB9:2:100::1 went from Established to Idle
03:13:19: %BGP-5-ADJCHANGE: neighbor 2001:DB9:2:100::1 Down Peer closed the
session
03:13:19: BGP: 2001:DB9:2:100::1 closing
03:13:19: BGP(1): nettable_walker 2001:DB9:2:1::/64 no best path

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 122
 03:13:19: BGP(1): nettable_walker 2001:DB9:2:100::/64 no best path
03:13:19: BGP(1): nettable_walker 2001:DB9:2:200::/64 no best path
03:13:20: BGP: 2001:DB9:2:100::1 passive open to 2001:DB9:1:100::1
03:13:20: BGP: 2001:DB9:2:100::1 went from Idle to Connect
03:13:20: BGP: 2001:DB9:2:100::1 rcv message type 1, length (excl. header) 26
03:13:20: BGP: 2001:DB9:2:100::1 rcv OPEN, version 4, holdtime 180 seconds
03:13:20: BGP: 2001:DB9:2:100::1 went from Connect to OpenSent
03:13:20: BGP: 2001:DB9:2:100::1 sending OPEN, version 4, my as: 65001, holdtime
180 seconds
03:13:20: BGP: 2001:DB9:2:100::1 rcv OPEN w/ OPTION parameter len: 16
03:13:20: BGP: 2001:DB9:2:100::1 rcvd OPEN w/ optional parameter type 2
(Capability) len 6
03:13:20: BGP: 2001:DB9:2:100::1 OPEN has CAPABILITY code: 1, length 4
03:13:20: BGP: 2001:DB9:2:100::1 OPEN has MP_EXT CAP for afi/safi: 2/1
03:13:20: BGP: 2001:DB9:2:100::1 rcvd OPEN w/ optional parameter type 2
(Capability) len 2
03:13:20: BGP: 2001:DB9:2:100::1 OPEN has CAPABILITY code: 128, length 0
03:13:20: BGP: 2001:DB9:2:100::1 OPEN has ROUTE-REFRESH capability(old) for all
address-families
03:13:20: BGP: 2001:DB9:2:100::1 rcvd OPEN w/ optional parameter type 2
(Capability) len 2
03:13:20: BGP: 2001:DB9:2:100::1 OPEN has CAPABILITY code: 2, length 0
03:13:20: BGP: 2001:DB9:2:100::1 OPEN has ROUTE-REFRESH capability(new) for all
address-families
03:13:20: BGP: 2001:DB9:2:100::1 rcvd OPEN w/ remote AS 65001
03:13:20: BGP: 2001:DB9:2:100::1 went from OpenSent to OpenConfirm
03:13:20: BGP: 2001:DB9:2:100::1 send message type 1, length (incl. header) 45
03:13:20: BGP: 2001:DB9:2:100::1 went from OpenConfirm to Established
03:13:20: %BGP-5-ADJCHANGE: neighbor 2001:DB9:2:100::1 Up
03:13:20: BGP(1): 2001:DB9:2:100::1 send UPDATE (format) 2001:DB9:1:200::/64, next
2001:DB9:1:100::1, metric 0, path Local
03:13:20: BGP(1): 2001:DB9:2:100::1 send UPDATE (prepend, chgflags: 0x0)
2001:DB9:1:100::/64, next 2001:DB9:1:100::1, metric 0, path Local
03:13:20: BGP(1): 2001:DB9:2:100::1 send UPDATE (prepend, chgflags: 0x0)
2001:DB9:1:A::/64, next 2001:DB9:1:100::1, metric 0, path Local
03:13:20: BGP(1): 2001:DB9:2:100::1 send UPDATE (prepend, chgflags: 0x0)
2001:DB9:1:1::/64, next 2001:DB9:1:100::1, metric 0, path Local
03:13:46: BGP(1): 2001:DB9:2:100::1 rcvd 2001:DB9:2:200::/64
03:13:46: BGP(1): 2001:DB9:2:100::1 rcvd 2001:DB9:2:100::/64
03:13:46: BGP(1): 2001:DB9:2:100::1 rcvd 2001:DB9:2:1::/64
03:13:46: BGP(1): 2001:DB9:2:100::1 rcvd 2001:DB9:1:A::/64

R1#undebug all
All possible debugging has been turned off

 On PC1, test the reachability of PC2 (use IPv6 address 2001:db9:2:1::f).

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 123
  Review the path between PC1 and PC2 (use IPv6 address 2001:db9:2:1::f).

 Disable all debugging on router R1.

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 124
Task 2: Configure EBGP for IPv6
In this task, you will configure eBGP for IPv6 towards router ISP.

Activity Procedure
Complete the following step:
Step 1 On R1, configure an eBGP for IPv6 with router ISP. Use the BGP parameters
that are listed in the table. Router ISP has been preconfigured.

EBGP Parameters

Parameter R1 ISP

AS 65001 64512

IPv4 Propagation No No
(enabled by default)
IPv6 Propagation Yes Yes
(disabled by default)
Source Address GigabitEthernet3 GigabitEthernet2

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 125
Activity Verification
You have completed this task when you attain these results:
 On R1, review the status of the BGP sessions. You should now have two functional sessions,
each receiving a few updates.

 Determine which prefixes are being received from router ISP.

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 126
  Determine what prefixes are being sent to the ISP.

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 127
  Review the routing table on R1. Look for the presence of the route for accessing Server at
2001:db9:10:1::f. Also make sure that the routes point to a valid next-hop interface and not to
Null.

 On PC1, test the reachability of Server (use IPv6 address 2001:db9:10:1::f).

 Review the path between PC1 and Server (use IPv6 address 2001:db9:10:1::f).

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 128
Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 129
Task 3: Configure IPv6 Prefix Filtering in BGP
In this task, you will configure prefix filtering of incoming eBGP updates from router ISP.

Activity Procedure
Complete the following steps:
Step 1 On R1, create an IPv6 prefix list named PFL that denies IPv6 prefixes
2001:db9:14::/48, 2001:db9:15::/48, 2001:db9:16::/48, and 2001:db9:17::/48.
All other updates should be permitted.

Step 2 Apply the prefix list PFL to incoming EBGP updates from router ISP.

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 130
Activity Verification
You have completed this task when you attain these results:
 On R1, review the routes that are received from router ISP. You should still see the prefixes that
are denied by the prefix list because you have not yet triggered the resending of updates.

 Clear the EBGP session with router ISP by sending a route refresh (that is, inbound soft
clearing).

R1#clear ip bgp ipv6 unicast 64512 in

 Recheck the routes that are received from router ISP. The prefixes that are denied by the prefix
list should not be seen anymore.

Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 131
Discovery Lab 7 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 132
Discovery Lab 8:
Troubleshooting Tickets 1 – 9
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will enable HSRP for IPv6 on the Cisco IOS routers R1 and R4. After completing this
activity, you will be able to meet the following objectives:
 Correct all proscribed faults provided by the Senior Engineering Team.
 Troubleshoot, remediate, and validate Issues in the Administrative Office (TS1).
 Troubleshoot, remediate, and validate Issues in the Administrative Office associated to shifting
over to Stateful DHCPv6 (TS2).
 Troubleshoot, remediate, and validate Issues in the BVHS Datacenter regarding issues with
reachability to external networks (TS3).

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 133
Visual Objective
The figure illustrates what you will accomplish in this activity.

Visual Objective for Lab 2-1: Enabling

IPv6 on Hosts ISPv6 (R9)

PC3

PE3 (R6) ISPv4 (R8)

PC2

P (R3) PE1 (R5) A1v4 (R7)

A3v6 (R2) R1
A2v6 (R4)

Static Addressing
PC1 Linux

© 2010 Cisco Systems, Inc. All rights reserved. IP6FD v3.0—LG-2

The lab environment is set up so that IPv4 is already configured on router R1. Configure Windows 10
on PC1 for IPv4 so that you can use Telnet to connect to the router.

Required Resources
The table lists the resources and equipment that are required to complete this activity.

Device Name Device Role in the Laboratory

R1-R5, R7

PC1-PC2

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 134
Command List
The table describes the commands that are used in this activity.

Cisco IOS Software Commands

Command Description

ipv6 address prefix Configures a static IP address on an interface.

ipv6 enable Enables an interface for IPv6.

ipv6 nd ra suppress Suppresses IPv6 router advertisement

transmissions on a LAN interface.

ipv6 unicast-routing Enables IPv6 routing.

show ip interface brief Shows brief IPv4 interface information.

show ip route Shows the IPv4 routing table.

show ipv6 interface brief Shows brief IPv6 interface information.

show ipv6 route Shows the IPv6 routing table.

Microsoft Windows PC Commands

Command Description

netsh interface ip set address Configures the IPv4 address, mask, and default
int_name static ip_addr net_mask gateway to the interface named int_name.
def_gw 1
netsh interface ipv6 add address Adds an IPv6 address to an interface on
int_name ipv6_address Microsoft Windows 10.

netsh interface ipv6 add route Adds a route for a specified prefix.
route int_name next-hop
netsh interface ipv6 show interface Displays Windows 10 interfaces.
[intf]
ping Enters the ping command from Windows 10.

ping6 Enters the ping6 command from Windows 10.

Note You can get detailed help if you type a question mark at the end of the netsh commands; for
example, netsh interface ipv6 add address ?.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 135
Linux PC Commands

Command Description

ifconfig Displays all network interface information that

has been configured.

ping Enters the ping command.

ping6 Enters the ping6 command.

Job Aids
These job aids are available to help you complete the lab activity:
 The instructor will provide you with your pod number and other pod-access information. Log this
information in the table.

Pod-Access Information

Parameter Value

Your pod number

Username on router R1 – R5, R7 —

Password on router R1 – R5, R7 —

Username on PC1/PC2 Admin

Password on PC1/PC2 ISEisC00L

Note Router R1-R5 and R7 are preconfigured to allow access without any credentials. Any Telnet
session or console access will automatically give you access to privileged mode.

The table illustrates the IPv4 and IPv6 addressing scheme that is used in this lab exercise.

Pod Addressing

Device Interface IPv4 Address and Mask IPv6 Address and Mask

R1 GigabitEthernet1

R4 GigabitEthernet2

PC1 LAB

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 136
Task 0: Reset the Router for this Lab
In this task, you will reset the router(s) for the beginning of this lab. The process is using a configure
restore option within IOS. There are command aliases already configured as the baseline of the routers
and they reference configurations found in flash.

Activity Procedure
Complete the following steps:
Step 1 Connect to Router 1 (R1), Router 2 (R2), Router 3 (R3), Router 4 (R4), Router 5
(R5), Router 7 (R6) and get to privileged mode.
Step 2 Type TS1-3 and type Y to confirm. The illustration below shows this process on
R1 (you will need to execute the same command on all the routers outlined in
Step 1).

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 137
Trouble Ticket #1:
PC2 Cannot Reach 2001:db9:7:7::7
In this trouble ticket, you will confirm that your PC has the necessary IPv6 configuration information to
establish connectivity to a server located in MOB-1 (simulated by a loopback address).

Activity Procedure
Complete the following steps:
Step 1 Connect to PC2 and open a command-prompt window. Verify that the PC indeed
cannot reach the ip address 2001:db9:7:7::7.

Step 2 Seeing that the IPv6 address is not reachable we have verified that the ticket is
correct (the “server” is not reachable). The next step will be to verify what IPv6
addresses the device is configured to use to communicate to R2. By using the
ipconfig /all command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 138
 Step 3 This gives us a lot of localized information regarding the operation of this
workstation now and previous. But the key data relates to the fact that the device
is using a statically assigned ipv6 address of 2001:db9:2:1::1 and the gateway
of last resort is 2001:db9:2:1::1. It is also noteworthy that this PC has at some
time in the past been configured to use ISATAP tunnels (possibly as part of
previous IPv6 transition mechanisms. Now it is best practice to test reachability
to the default gateway of 2001:db9:2:1::1.
Use the ping 2001:db9:2:1::1 command.
This ping should work provided R2 (the next hop device) is correctly configured
at the interface level.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 139
 Step 4 The ping works. Now we will engage in what should be another revealing
diagnostic test by attempting to do a trace route to the destination IPv6 address
of 2001:db9:7:7::7
Use the tracert 2001:db9:7:7::7 command.

Step 5 The trace-route fails with a Destination Unreachable message, after it is

successfully sent to R2 via the Gateway address 2001:db9:2:1::1. This indicates
that the best place to start would be at R2 the next logical hop from PC2 or R7
which would be the point of origin for this prefix. I will choose to start with R2
Step 6 Open a session to R2 and test to see if the IPv6 address 2001:db9:7:7::7 is
reachable.
Use the ping 2001:db9:7:7::7 command.

Step 7 We can clearly see that R2 has no record of how to reach this prefix so it stands
to reason that the ping will fail once PC2 sends traffic to R2. Looking at the
topology it is very clear that this prefix should be learned on R2 as an OSPF

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 140
 prefix. To see if this happening we will look at the OSPF database for this
specific prefix.
Use the show ipv6 ospf database command.

Step 8 Note that we do not see any mention of an advertising router of 0.0.0.7 (R7) in
this output it is also worth noting that we also do not see any reference to 0.0.0.3
(R3). This is because there is a virtual link running between R1 and R3 to correct
the issue that Area 4 is not physically connected to Area 0. This means that
Routes from R3 and R7 should be “re-originated” by R1 (0.0.0.1) in the OSPF
database. We can see this by looking at the entries for the segments between R3
and R5 (2001:DB9:3535::/64 - Area 0) and R4 and R5 ( 2001:DB9:4545::/64 -
Area 2). All of these prefixes exist as Inter-Area Links State Prefixes inside Area
4 where R2 is located. This is normal and to be expected, however not seeing

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 141
 prefixes in the database for 2001:DB9:5757::0/64 or for 2001:DB9:7:7::0/64 is
surprising. To investigate what is happening we will turn out attention to R7
(where 2001:DB9:7:7::/64 is being originated.

Step 9 Open a session to R7 and test to see if the IPv6 address 2001:db9:7:7::7 is
present.

Step 10 We see that the IPv6 address does exist on R7. Remember the Senior
Engineering team is using this loopback 7 IPv6 address to simulate a DNS server
that will be installed in Medical Office Building One once the transition is
complete. Now we want to see if this interface is participating in OSPF, we will
accomplish this by using the show ipv6 ospf interface brief command.

Step 11 We see clearly that Looback7 is being advertised into Area 3 as expected.
However, we also can clearly see that there are no OSPF Neighbors being
formed. We would expect to see a neighbor out of G1 toward R5. This seems to
be the nature of the issue we are experiencing. With no neighbors we will not
advertise any routes from R7 toward any other OSPF speakers in the topology.
We can confirm this using the show ipv6 ospf database command once more.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 142
 Step 12 Observe that there are no Links being advertised as Type 1 LSAs as we have
discussed. Now we will want to see why we are not forming an adjacency with
R5. We can do that by using a debug ipv6 ospf hello detail.

Step 13 We can see that we are RECEIVING Hello messages from R5 (0.0.0.5) which is
expected but we also see that the Stub/Transit Area Option Bit is mismatched.
Meaning that some variation of Area 3 Stub has been applied. We need to see
what the current OSPF Stub Flag mode on the GigabitEthernet 1.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 143
 Step 14 Note that this router (R7) has one area configured (Area 3) and it is configured as
Stub.
Step 15 If the Stub Flag between devices is mismatched then an adjacency cannot form,
to correct this we need to alter the configuration. Options would include removing
the configuration from this device or adding a matching stub flag on R5. Because
we are here on R7 already I will remove the Area 3 stub command from the
routing process.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 144
 Step 16 Immediately after removing the configuration, we see the Neighbor Adjacency
form. Now I want to verify that routes are being learned. We will do this by
checking the ipv6 ospf database inter-area prefix 2001:db9:2:1::0/64 this is the
specific network being used by PC2 to reach 2001:db9:7:7::7/64.

Step 17 With this we need to return to PC2 and check for reachability.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 145
 Step 18 The ping works to 2001:db9:7:7::7, to see the transit path we will run the tracert
command as well.
This Remediates this Ticket.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 146
Trouble Ticket #2:
PC2 Not Receiving DHCPv6 Address from R2
In this trouble ticket, you will identify why PC2 does not receive an IPv6 ip address from R2 which is
configured as the DHCPv6 Server.

Activity Procedure
Complete the following steps:
Step 1 Connect to PC2 open the “Open Network and Sharing Center”.

Step 2 Select Change adapter settings.

Step 3 Right-click on the Network Interface “LAB”.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 147
 Step 4 Navigate to the “Internet Protocol Version 6 (TCP/IPv6)” and select Properties.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 148
 Step 5 Select the “Obtain an IPv6 address automatically” and “Obtain DNS server
address automatically” radio buttons. Click on OK.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 149
 Step 6 Open a command shell and execute the command ipconfig /renew6.

Step 7 We see that the host does not get an IPv6 address, furthermore it looks like the
device is stuck. To test this, we will execute a control-c operations and see what
the host returns.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 150
 Step 8 In the output we see that we are getting an ipv6 address that corresponds to a
link local address in the range of fe80:: which is a link local address. Additionally,
we are not learning any information other than the link local address of Router
R2’s link local address applied to GigabitEthernet1 on that device. Next, we will
test to see if we have reachability to the test address of 2001:DB9:7:7::7.

Step 9 We see that the pings fail. To determine what is going on we need to investigate
what is happening on R2 in this scenario. R2 should be configured to issue an
IPv6 address using DHCPv6 on interface GigabitEthernet1. To see if this
interface is configured to provide IPv6 addresses to hosts connected on this
segment we will use the command show ipv6 interface GigabitEthernet1. If
configured correctly we should see that the inte

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 151
 Step 10 Notice that the last line says, “Hosts use DHCP to obtain routable addresses”.
This seems to indicate that the interface is configured for dhcpv6 support,
however the configuration may not be correct or complete. To validate the
configuration, we will execute a show run interface GigabitEthernet1
command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 152
 Step 11 Note in the yellow highlighted section we see the engineer has disable auto
configuration on the interface using the no-autoconfig keyword. Second, we can
see that the engineer has applied the managed-config-flag which states that
stateful DHCPv6 should be used. However, we do not see the application of the
DHCPv6 Pool on this interface. So, this is obviously a problem.
Step 12 To identify the name of the DHCPv6 Pool that should be applied on
GigabitEthernet1 we will use the command show run | sec dhcp.

Step 13 We can see the name of the IPv6 DHCP pool is STATEFUL-DHCPv6. This
information will need to be applied to the interface. We will do this via the ipv6
dhcp server STATEFUL-DHCPv6 command.

Step 14 Now we will want to use the command debug ipv6 dhcp detail command so
that we can track what is happening when reinitiate the dhcp request from PC2.

Step 15 We will return to PC2 and we will execute the ipconfig /renew6 command once
more.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 153
 Step 16 Note that the host obtains an IPv6 Address in the correct network
2001:DB9:2:1::/64. Additionally we get the DNS suffix of nterone.local.
Step 17 Next, we will look at R2 to see if the debug has resulted in any output.

Step 18 Lastly, we will check the ipv6 dhcp binding database, using the show ipv6 dhcp
binding database command to check if any IPv6 addresses that have been
issued by R2.

We see the same address appears in the database. An additional check would
be to look at the pool itself using the show ipv6 dhcp pool command.

Step 19 Return to PC2 and test reachability to the address 2001:db9:7:7::7 address that
is assigned for testing.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 154
 Step 20 We can see that the pings are successful now. This concludes the remediation of
this ticket.

Trouble Ticket #3:

PC2 Not Receiving DHCPv6 Address from R2
In this trouble ticket, you will identify why PC1 does not have reachability to networks outside of Big
Valley Health System Datacenter. The PC needs to be configured to support autoconfig on the ethernet
segment and the gateway of last resort is FE80::1. The IPv6 address used for testing external
reachability form the Data Center is 2001:DB9:7:7::7.

Activity Procedure
Complete the following steps:
Step 1 Connect to PC1 open the “Open Network and Sharing Center”.

Step 2 Select Change adapter settings for the “LAB” interface to Obtain IPv6 Address
and DNS address automatically.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 155
 Step 3 Disable and Enable the LAB interface.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 156
 Step 4 Now open a console connection and exec the ipconfig command to validate that
an IPv6 address was assigned.

Step 5 Note that both a link local and a GUA IPv6 address has been assigned, and we
see a Default Gateway address of FE80::1. Now we will test reachability to that
IPv6 Link Local address by using the ping fe80::1 command.

Step 6 We see that the ping is failing. To validate MAC address used to resolve this
IPv6 address. We will use the netsh interface ipv6 show neighbor command.

Step 7 The output shows that the address FE80::1 is Unreachable, it also shows the
MAC address of that IPv6 address as 00-05-73-a0-00-01. Any MAC address in
the 00:05:73:a0:0X:XX is associated with Cisco HSRP for IPv6 protocol. So

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 157
 based on this we should see that HSRP should be configured on R1
(GigabitEthernet1) and R4 (GigiabitEthernet4).
Step 8 Access the console of R1 and verify that HSRP is running and configured
properly by using the show standby command.

Step 9 We see that HSRP for IPv6 is configured, the show command tells us that R1 is
the Active Router meaning it should be hosting the IPv6 address of FE80::1, and
that it is using the virtual mac address of 0005.73a0.0001 as the virtual MAC
address.
Step 10 To validate that this IPv6 address is in service on R1 GigabitEthernet1 we will
use the show ipv6 interface GigabitEthernet1 command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 158
 Step 11 Can R1 reach the test address of 2001:db9:7:7::7 sourcing traffic from
GigabitEthernet1? We will test this by using the ping 2001:db9:7:7::7 source
GigabitEthernet 1 command R1.

Step 12 We clearly see that the destination address is reachable from R1 to R3 to R5 and
ultimately to R7 which tells us that there is nothing wrong in the data path. This
leads the support team to believe that there may be a problem with the HSRP
configuration. After whiteboarding the problem, the decision is made to force R4
to become the active router by shutting down GigabitEthernet1 on R1.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 159
 Step 13 After waiting a few seconds R4 should become the active router as evidenced by
its console output.

Step 14 Now we will repeat the ping test from PC1 to 2001:db9:7:7::7.

Step 15 The ping now works. To test further it is decided to validate neighbors once more
to see what the L2 information associated with the Router is now after the switch
to R4 as the Active Router. This is done with the netsh interface ipv6 show
neighbor command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 160
 Step 16 Note that the FE80::1 entry is Reachable, the Physical Address (MAC) in service
is not the HSRP IPv6 virtual MAC of 00-05-73-a0-00-01 used by R1. This is
interesting and seems to indicate that the is a discrepancy in the configuration of
HSRP between R1 and R4. To investigate this further we will look at the
configuration on R4. Since it is working it seems safe to assume that its
configuration is correct. We will simply use the show run interface
GigabitEthernet2 command on R4.

Step 17 Now we will repeat the command on R1 however we will need to change it to
GigabitEthernet2.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 161
 Step 18 A side-by-side comparison shows that R1 has not been outfitted with the
command standby use-bia command. This command instructs the router that is
hosting the virtual IPv6 address (the active router) to use its local interface
physical burned in address. We will in the spirit of troubleshooting apply the
same configuration to R1 and no shut its GigabitEthernet1 interface and test
again once it is elected as the Active HSRP Router.

Step 19 Now we will return to PC1 and test again by pinging 2001:db9:7:7::7.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 162
 Step 20 Now we want to repeat the netsh interface ipv6 show neighbor command to
see if the Virtual MAC address has changed.

Step 21 Note that the address has change and it is now the physical address of R1 rather
than the virtual address that was being used before.
Step 22 As an additional test we will validate reachability to the IPv6 address
2001:db9:2:1::1 which resides on R2.

Step 23 This ticket has been remediated.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 163
Task 0: Reset the Router for Tickets 4 – 6
In this task, you will reset the router(s) for the beginning of this lab. The process is using a configure
restore option within IOS. There are command aliases already configured as the baseline of the routers
and they reference configurations found in flash.

Activity Procedure
Complete the following steps:
Step 1 Connect to Router 1 (R1), Router 2 (R2), Router 3 (R3), Router 4 (R4), Router 5
(R5), Router 7 (R6) and get to privileged mode.
Step 2 Type TS4-6 and type Y to confirm. The illustration below shows this process on
R1 (you will need to execute the same command on all the routers outlined in
Step 1).

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 164
Trouble Ticket #4:
PC1 Cannot Reach 2001:db9:7:7::7
In this trouble ticket, you will confirm that your PC1 has the necessary IPv6 configuration information to
establish connectivity to a server located in MOB-1 (simulated by a loopback address).

Activity Procedure
Complete the following steps:
Step 1 Connect to PC1 and open a command-prompt window. Verify that the PC indeed
cannot reach the ip address 2001:db9:7:7::7.

Step 2 Seeing that the IPv6 address is not reachable we have verified that the ticket is
correct (the “server” is not reachable). The next step will be to verify what IPv6
addresses the device is configured to use to communicate to R1. By using the
ipconfig /all command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 165
 Step 3 This gives us a lot of localized information regarding the operation of this
workstation now and previous. But the key data relates to the fact that the device
is using autoconfig and has an assigned ipv6 address of
2001:db9:1:1:xxxx:xxxx:xxxx:xxxx and the gateway of last resort is fe80::1.
Now it is best practice to test reachability to the default gateway of fe80::1.
Use the ping fe80::1 command.
This ping should work provided R1 and R4 (the next hop devices running HSRP)
are correctly configured at the interface level.

Step 4 The ping works, now we want to test with a tracert to 2001:db9:7:7::7.

Step 5 The results indicate that the destination is unreachable, and that traffic is being
sent to 2001:db9:1:1::11 which is the GUA IPv6 address assigned to R1s
GigabitEthernet1. We will want to test to be sure this address is reachable as
well using ping 2001:db9:1:1::11.

Step 6 That ping works so the next logical step would be to move to the console of R1
and see if the testing prefix 2001:db9:7:7::7 is reachable. Which we can
reasonably assume will not be the case. However, testing would be prudent.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 166
 Step 7 As expected, the prefix is not reachable, now we need to verify what R1 is
learning via OSPFv3 from its peer R3. The expectation is, given that R3 is the
Area Border Router between Area1 and Area 0 that all prefixes originating in
area 3 (R7) should be advertised to R1 from this ABR. We will validate this
assumption using the show ipv6 route ospf command.

This is a lot of output so we will target specifics. The link between R5 and R7 will
be 2001:db9:5757::/64, the link between R5 and R4 will be 2001:db9:4545::/64.
We will filter the previous command using this information so see if we are
learning routes from Area2 and Area 3 as a further test.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 167
 Step 8 This clearly illustrates that we are learning no prefixes associated with Area 3
(where the destination prefix 2001:db9:7:7::7 is being originated), we used the
same test filter for Area 2 as a further litmus test R5 to see if the issue was facing
Area 0 or facing just Area 3.
Step 9 We will need to move to R7 and validate the configuration of OSPF there.

Step 10 Immediately we see there is indeed an OSPFv3 configuration error. We see that
we have a duplicate OSPFv3 Router-ID. Give that the message says that we are
detecting a duplicate ID on GigabitEthernet1, that means R5 is running the
router-id 0.0.0.5 and the assumption is that we are running the same on R7. We
can validate this by using the show ipv6 protocol command.

Step 11 To remediate this, we will need to change the router-ID on R7 to a systemically

unique value. The pattern used on other devices seems to be 0.0.0.# where #
equals the router number. So logically this device should be 0.0.0.7. We will
apply this change to see if it has desired result.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 168
 Step 12 Immediately we can see the neighbor adjacency with R5 form.
Step 13 To validate we will navigate back to PC1 and repeat the ping to 2001:db9:7:7::7.

Step 14 The ping is now working. This remediates this ticket.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 169
Trouble Ticket #5:
PC2 Cannot Reach 2001:db9:7:7::7
In this trouble ticket, you will confirm that your PC2 has the necessary IPv6 configuration information to
establish connectivity to a server located in MOB-1 (simulated by a loopback address).

Activity Procedure
Complete the following steps:
Step 1 Connect to PC2 and open a command-prompt window. Verify that the PC indeed
cannot reach the ip address 2001:db9:7:7::7.

Step 2 Seeing that the IPv6 address is not reachable we have verified that the ticket is
correct (the “server” is not reachable). The next step will be to verify what IPv6
addresses the device is configured to use to communicate to R2. By using the
ipconfig /all command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 170
 Step 3 This gives us a lot of localized information regarding the operation of this
workstation now and previous. But the key data relates to the fact that the device
is using autoconfig and has an assigned ipv6 address of
2001:db9:2:1:xxxx:xxxx:xxxx:xxxx and the gateway of last resort is fe80::2.
Now it is best practice to test reachability to the default gateway of fe80::2.
Use the ping fe80::2 command.
This ping should work provided R2 (the next hop device) is correctly configured
at the interface level.

Step 4 The ping works, now we want to test with a tracert to 2001:db9:7:7::7.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 171
 Step 5 The results indicate that the destination is unreachable, and that traffic is being
sent to 2001:db9:2:1::1 which is the GUA IPv6 address assigned to R2s
GigabitEthernet1. We will want to test to be sure this address is reachable as
well using ping 2001:db9:2:1::1.

Step 6 That ping works so the next logical step would be to move to the console of R2
and see if the testing prefix 2001:db9:7:7::7 is reachable. Which we can
reasonably assume will not be the case. However, testing would be prudent.

Step 7 As expected, the prefix is not reachable, now we need to verify what R2 is
learning via OSPFv3 from its peer R1. The expectation is, given that R2 is the
Area Border Router between Area 4 and Area 1 that all prefixes originating in all
other areas should be advertised to R2 from this ABR (R1). We will validate this
assumption using the show ipv6 route ospf command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 172
 Step 8 We see that R2 is learning no OSPF prefixes. This begs two questions:
1. Does R2 have a Peering Relationship with R1?
2. Is R1 acting as an Area Border Router?
First, we will address question 1, by executing the show ipv6 ospf neighbor
command.

We see that we have a neighbor, but is that neighbor acting as a ABR? We will
used the command show ipv6 ospf border-routers.

We see that in Area 1 there are no border-routers.

Step 9 Thinking back to our theory regarding OSPF operations, for a router to be
classified as an Area Border Router the device needs to have interfaces in at
least two areas and ONE OF THOSE AREAS MUST BE AREA 0. We see that
R1 has no physical connection to Area 0. The mechanism to fix this issue would
be to provide a logical connection to Area 0 using a virtual-link. We will need to
move to R1 and check its current configuration. We will use the show run | sec
router ospfv3 command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 173
 Step 10 There is no configuration on R1 for any variation of virtual-link. Now we need to
look at the configuration on R3 which does have a physical connection to Area 0.
Again, we will use the show run | sec router ospfv3 command.

Step 11 We see on R3 we one half of the virtual-link configuration directed to 0.0.0.1

which is R1’s Router-ID. To apply the other half of the configuration on R1 we will
return to its console and under address-family ipv6 unicast we will apply the area
1 virtual-link 0.0.0.3 command.

Step 12 Notice that R1 has formed a peering relationship with R3 via Virtual-Link (VL1)
Interface. Now we will see if R1 is now acting as a border-router by repeating the
show ipv6 ospf border-router command on R2.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 174
 Step 13 We see now that we have R1 (0.0.0.1) appearing as an Area Border Router and
R5 (0.0.0.5) appearing as Autonomous System Boundary Router (meaning
redistribution is taking place on that device).
Step 14 We will return to PC2 and retest to see if 2001:db9:7:7::7 is reachable.

Step 15 This remediates this ticket and establishes the desired reachability.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 175
Trouble Ticket #6:
PC1 Cannot Reach External Networks
In this trouble ticket, you will confirm that your PC1 has the necessary IPv6 configuration information to
establish connectivity to an external network running on R5. The Senior Engineering team has
designated the ipv6 test address for this lab as 2001:db9:99:99:99::99 (simulated by a loopback
address on R5).

Note The Senior Engineering Team has mandated that you cannot remove any configuration during the
remediation of this ticket.

Activity Procedure
Complete the following steps:
Step 1 Connect to PC1 and open a command-prompt window. Verify that the PC indeed
cannot reach the ip address 2001:db9:99:99:99::99.

Step 2 Seeing that the IPv6 address is not reachable we have verified that the ticket is
correct (the “server” is not reachable). The next step will be to verify what IPv6
addresses the device is configured to use to communicate to R. By using the
ipconfig /all command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 176
 Step 3 This gives us a lot of localized information regarding the operation of this
workstation now and previous. But the key data relates to the fact that the device
is using autoconfig and has an assigned ipv6 address of
2001:db9:1:1:xxxx:xxxx:xxxx:xxxx and the gateway of last resort is fe80::1.
Now it is best practice to test reachability to the default gateway of fe80::1.
Use the ping fe80::1 command.
This ping should work provided R1 (the current Active Router) is correctly
configured at the interface level.

Step 4 As an alternate, to rule out issues between PC1 and the Core Network resources
we will do an additional ping to the IPv6 address 2001:db9:7:7::7 that we have
used in other labs. This will rule out much of the infrastructure in the network
core.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 177
 Step 5 The ping to 2001:db9:7:7::7 hosted on R7 works as expected. Now we will
perform a traceroute to see the path the traffic will take to that same destination.

Step 6 We see that the traffic to 2001:db9:7:7::7 traversed R1 via R5 (2001:db9:3535::5)

to reach 2001:db9:7:7::7. We know that the route to 2001:db9:99:99:99::99 is
originated on R5 based on the instructions form the Senior Engineering Team.
Given that traffic will transit R5 my next point of validation will be to move to R5
where we will look to see what interfaces originate the target prefix. We will do
this with a show ipv6 interface brief command.

Step 7 We see that Loopback99 I where the IPv6 address 2001:db9:99:99:99::99 is

originated. Now we want to see if that interface is running ospfv3. We will do that
via the show ipv6 ospf interface brief command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 178
 Step 8 The show command indicates that none of the loopback addresses are being
advertised in OSPFv3. That means we need to figure out how to get Loopback
99 to be advertised. First, we will simply apply the correct ospfv3 configuration to
this loopback.

Step 9 Now that this has been done, we will want to ensure that this interface is running
OSPFv3 by redoing the show ipv6 ospf interface brief command.

Step 10 The interface is now participating in OSPFv3 and we will need to see if we have
reachability from PC1 again.

Step 11 This has remediated this ticket.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 179
Task 0: Reset the Router for Tickets 7 – 9
In this task, you will reset the router(s) for the beginning of this lab. The process is using a configure
restore option within IOS. There are command aliases already configured as the baseline of the routers
and they reference configurations found in flash.

Activity Procedure
Complete the following steps:
Step 1 Connect to Router 1 (R1), Router 2 (R2), Router 3 (R3), Router 4 (R4), Router 5
(R5), Router 7 (R6) and get to privileged mode.
Step 2 Type TS7-9 and type Y to confirm. The illustration below shows this process on
R1 (you will need to execute the same command on all the routers outlined in
Step 1).

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 180
Trouble Ticket #7:
PC1 Cannot Reach 2001:db9:7:7::7
In this trouble ticket, you will confirm that your PC2 has the necessary IPv6 configuration information to
establish connectivity to a server located in MOB-1 (simulated by a loopback address).

Activity Procedure
Complete the following steps:
Step 1 Connect to PC2 and open a command-prompt window. Verify that the PC indeed
cannot reach the ip address 2001:db9:7:7::7.

Step 2 Seeing that the IPv6 address is not reachable we have verified that the ticket is
correct (the “server” is not reachable). The next step will be to verify what IPv6
addresses the device is configured to use to communicate to R2. By using the
ipconfig /all command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 181
 Step 3 This gives us a lot of localized information regarding the operation of this
workstation now and previous. But the key data relates to the fact that the device
is using autoconfig and has an assigned ipv6 address of
2001:db9:2:1:xxxx:xxxx:xxxx:xxxx and the gateway of last resort is fe80::2.
Now it is best practice to test reachability to the default gateway of fe80::2.
Use the ping fe80::2 command.
This ping should work provided R2 (the next hop device) is correctly configured
at the interface level.

Step 4 The ping works, now we will need to move to the console of R2 and verify if it has
reachability to the prefix 2001:db9:7:7::7. It is a safe assumption that R2 will not
have that route in its routing table.

Step 5 As expected, this device is not learning the prefix 2001:db9:7:7::7 from its
upstream BGP peer. This could be for many reasons to include a failed TCP
connection with R3 which houses the next Autonomous system (200). To see if
this connection is working, we will using the show bgp ipv6 unicast summary
command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 182
 Step 6 We see that we have a peering relationship with R3 (2001:db9:1313::3) but we
are learning no prefixes from this neighbor at all. We should be expecting to learn
the prefix 2001:db9:7:7:: from R3. We will need to open a console connection to
R3 and verify whether or not it is learning this prefix or not. We will do this using
the show bgp ipv6 unicast summary command.

Step 7 We can see that the TCP Session for BGP Peering between R3 and R7 is in the
Idle state. We obviously want to see this peering up and operational. To see what
is happening we will navigate to the console of R7 and check the configuration
status there. First, we will use the show bgp ipv6 unicast summary command
here.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 183
 Step 8 We see that this device is not able to run BGP because it does not have a router-
id. The device will dynamically choose a router-id from one an interface that has
an IPv4 Address. However, there are no interfaces with IPv4 addresses. This will
require us to either apply an IPv4 address or manually assign a unique router-id
to the BGP process. To remedy this issue, we will choose to set the router-id
manually. We will use the address 192.168.7.1.

Step 9 Note almost immediately the peering with R3 (2001:db9:3535::3) comes up. Now
from this device we will want to see if we are advertising 2001:db9:7:7::7 to R3.
We can do this by using the show bgp ipv6 unicast neighbor
2001:db9:3535::3 advertised-routes command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 184
 Step 10 We see now that we are advertising the 2001:DB9:7:7::7/128 prefix to our
neighbor located at 2001:db9:3535::3. I will return to PC2 and validate that the
address in now reachable.

Step 11 We can see that the prefix is now reachable and have demonstrated that the
ticket is now remediated.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 185
Trouble Ticket #8:
PC1 Cannot Reach 2001:db9:3:3::3
In this trouble ticket, you will confirm that your PC1 has the necessary IPv6 configuration information to
establish connectivity to a server located in Labor and Delivery (simulated by a loopback address).

Activity Procedure
Complete the following steps:
Step 1 Connect to PC1 and open a command-prompt window. Verify that the PC indeed
cannot reach the ip address 2001:db9:3:3::3.

Step 2 Seeing that the IPv6 address is not reachable we have verified that the ticket is
correct (the “server” is not reachable). The next step will be to verify what IPv6
addresses the device is configured to use to communicate to R1. By using the
ipconfig /all command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 186
 Step 3 This gives us a lot of localized information regarding the operation of this
workstation now and previous. But the key data relates to the fact that the device
is using autoconfig and has an assigned ipv6 address of
2001:db9:1:1:xxxx:xxxx:xxxx:xxxx and the gateway of last resort is fe80::1.
Now it is best practice to test reachability to the default gateway of fe80::1.
Use the ping fe80::1 command.
This ping should work provided R1 (the next hop device) is correctly configured
at the interface level.

Step 4 The ping works, now we will need to move to the console of R1 and verify if it has
reachability to the prefix 2001:db9:3:3::3. It is a safe assumption that R1 will not
have that route in its routing table.

Step 5 As expected, this device is not learning the prefix 2001:db9:3:3::3 from its
upstream BGP peer. This could be for many reasons to include a failed TCP
connection with R3 which houses the next Autonomous system (200). To see if
this connection is working, we will be using the show bgp ipv6 unicast
summary command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 187
 Step 6 We see that we have a peering relationship with R3 (2001:db9:1313::3) and we
are learning 1 prefix from this neighbor. We can identify the learned prefix by
using the show bgp ipv6 unicast command.

Step 7 We should be expecting to learn the prefix 2001:db9:3:3::3/128 from R3 where

the prefix is being orginated. We will need to open a console connection to R3
and verify whether advertising the prefix or not. We will do this using the show
bgp ipv6 unicast neighbor 2001:db9:1313::1 advertised-routes command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 188
 Step 8 We can see that R3 is not advertising the prefix. Next, we will look to see if the
prefix appears in the BGP Database by using the command show bgp ipv6
unicast command.

Step 9 Note that the prefix does not appear in the BGP IPv6 unicast routing table on R3.
Which is odd due to the fact that this prefix is being originated on R3 in the form
of a loopback address. We can look to see what loopback interface is originating
this prefix using the show ipv6 route connected command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 189
 Step 10 We can see the address and mask is 2001:DB9:3:3::3/128 which means the
interface is configured, but now we will need to see how the prefix is being
injected into BGP. The easiest way to do this will be to use the show run | sec
router bgp command.

Step 11 We see that the network command is being used to inject the prefix into BGP,
however, closer examination will reveal that the command though using the

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 190
 correct mask of /128 is not specifying the complete network and host
designation. For this to work we will need to modify the network statement to
match the correct format using the network 2001:db9:3:3::3/128 command,
however we will want to remove the previous command syntax first using the no
network 2001:db9:3:3::/128 command.

Step 12 Now we will look to see if the route appears in the routing table using the show
bgp ipv6 unicast command.

Step 13 The prefix is now present, as a final check we will look to see if it is being
advertised to R1 now using the show bgp ipv6 unicast neighbor
2001:db9:1313::1 advertise-routes command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 191
 Step 14 The route is now being advertised. The next logical step will be to go back to
PC1 and see if reachability has been restored.

Step 15 This has resolved this trouble ticket.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 192
Trouble Ticket #9:
PC1 Cannot Reach 2001:db9:199:199:199::199
In this trouble ticket, you will confirm that your PC1 has the necessary IPv6 configuration information to
establish connectivity to a server located in Labor and Delivery (simulated by a loopback address
assigned on R5).

Activity Procedure
Complete the following steps:
Step 1 Connect to PC1 and open a command-prompt window. Verify that the PC indeed
cannot reach the ip address 2001:db9:199:199:199::199.

Step 2 Seeing that the IPv6 address is not reachable we have verified that the ticket is
correct (the “server” is not reachable). The next step will be to verify what IPv6
addresses the device is configured to use to communicate to R1. By using the
ipconfig /all command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 193
 Step 3 This gives us a lot of localized information regarding the operation of this
workstation now and previous. But the key data relates to the fact that the device
is using autoconfig and has an assigned ipv6 address of
2001:db9:1:1:xxxx:xxxx:xxxx:xxxx and the gateway of last resort is fe80::1.
Now it is best practice to test reachability to the default gateway of fe80::1.
Use the ping fe80::1 command.
This ping should work provided R1 (the next hop device) is correctly configured
at the interface level.

Step 4 The ping works, now we will need to move to the console of R1 and verify if it has
reachability to the prefix 2001:db9:199:199:199::199. It is a safe assumption that
R1 will not have that route in its routing table.

Step 5 As expected, this device is not learning the prefix 2001:db9:199:199:199::199

from its upstream BGP peer. This could be for many reasons to include a failed
TCP connection with R3 which houses the next Autonomous system (200). To
see if this connection is working, we will be using the show bgp ipv6 unicast
summary command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 194
 Step 6 We see that we have a peering relationship with R3 (2001:db9:1313::3) and we
are learning 2 prefixes from this neighbor. We can identify the learned prefix by
using the show bgp ipv6 unicast command.

Step 7 We should be expecting to learn the prefix 2001:db9:199:199:199::199/64 from

R3, if it is learning it from R5 where the prefix is being originated. We will need to
open a console connection to R3 and verify whether it is learning the prefix or
not. We will do this using the show bgp ipv6 unicast command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 195
 Step 8 We can see that R3 is learning the prefix and as such it cannot advertising the
prefix to R1. Next we will look to see if the prefix appears in the BGP Database
on R5 by using the command show bgp ipv6 unicast.

Step 9 Note that the prefix does not appear in the BGP IPv6 unicast routing table on R5.
Which is odd since this prefix is being originated on R4 in the form of a loopback
address. We can look to see what loopback interface is originating this prefix
using the show ipv6 route connected command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 196
 Step 10 We can see the address and mask is 2001:DB9:199:199:199::199/64 which
means the interface is configured, but now we will need to see how the prefix is
being injected into BGP. The easiest way to do this will be to use the show run |
sec router bgp command.

Step 11 We see that the network command is not being used to inject the prefix into BGP,
instead we see that we are using a route-map in concert with redistribute
connected to originate the prefix. For this to work we will need to look at the
route-map that is being used. To accomplish this, we will use the show route-
map command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 197
 Step 12 The route-map calls an IPv6 Prefix-list with the name TST-SERVER. We will
need to look at this prefix-list. I want to see if the prefix-list is being “hit” as part of
the match operation of the route-map and at the same time I want to see the
value used in the prefix-list. We will do this using the show ipv6 prefix-list detail
command.

Step 13 In the provide output of the show command we can see in the green square that
the prefix-list is deployed (inside our route-map), in the red square we can see
that the prefix-list is not matching any traffic, in the yellow square we can see
why (the network mask /96 does not match the /64 mask used by the loopback
interface). To fix this we can change the ipv6 prefix-list to match the correct mask
using on loopback 199.

Step 14 With this change we will now want to see if the prefix-list is getting “hits” by using
the show ipv6 prefix-list detail command.

Step 15 Now we see that the prefix-list is matching traffic. Let’s look to see if the prefix
appears in the IPv6 BGP table. We will use the show bgp ipv6 unicast
command.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 198
 Step 16 We see the prefix now appears. The next check will be to see if it is being
advertised to R3 using the show bgp ipv6 unicast neighbor 2001:db9:3535::3
advertised-routes command.

Step 17 The route is being advertised, now we will return to PC1 and see if the issue has
been corrected.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 199
 Step 18 This ticket has been remediated.

Discovery Lab 8 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 200
Discovery Lab 9:
Multicasting
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will learn the important differences between multicast in IPv6 and IPv4. Static RP
assignment will still be common—and supported—but the large IPv6 multicast address space enables
other solutions. Bootstrap Router allows the RP address to be advertised throughout the domain. Both
types of multicast, as well as shared tree configurations and source-tree configurations, are
demonstrated in this lab. After completing this activity, you will be able to meet these objectives:
 Configure multicast by using static RPs.
 Configure source-tree multicast.
 Configure Bootstrap Router to advertise RPs.

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 201
Visual Objective
The figure illustrates what you will accomplish in this activity.

Required Resources
The table lists the resources and equipment that are required to complete this activity.

Device Name Device Role in the Laboratory

R1 Access router in Site 1; used as the default gateway for IPv4 and IPv6 traffic.

R2 Access router in Site 2; used as the default gateway for IPv4 and IPv6 traffic.

R3 Access router in Site 3; used as the default gateway for IPv4 and IPv6 traffic.

PC1 End user with applications that require both IPv4 and IPv6 support by the
operating system and the network.

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 202
 Device Name Device Role in the Laboratory

PC2 End user with applications that require both IPv4 and IPv6 support by the
operating system and the network.

PC3 End user with applications that require both IPv4 and IPv6 support by the
operating system and the network.

Command List
The table describes the commands that are used in this activity.

Cisco IOS Software Commands

Command Description

ipv6 multicast-routing Enables multicast routing, using PIM and MLD,

on all IPv6-enabled interfaces of the router, and
enables multicast forwarding.

ipv6 pim rp-address Configures the address of a PIM RP for a

particular group range.

ipv6 pim spt-threshold infinity Configures when a PIM leaf router joins the SPT
for the specified groups.

ipv6 pim bsr candidate rp address Configures the router to be the RP candidate.

ipv6 pim bsr candidate bsr address Configures the router to be the BSR candidate.

show ipv6 mld groups Displays the multicast groups that are directly
connected to the router and that were learned
through MLD.

show ipv6 mld interface Displays multicast-related information about an

interface.

show ipv6 mld traffic Displays the MLD traffic counters.

show ipv6 pim group-map Displays an IPv6 multicast group mapping table.

show ipv6 pim topology Displays PIM topology table information for a
specific group or all groups.

show ipv6 pim traffic Displays the PIM traffic counters.

show ipv6 pim tunnel Displays information about the PIM register
encapsulation and de-encapsulation tunnels on
an interface.

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 203
Windows PC Commands

Command Description

ipconfig Displays IP information for hosts that run

Windows 10.

ping ipv4-address –t Verifies IPv4 connectivity; continual testing by

using parameter –t.

ping6 ipv6-address –t Verifies IPv6 connectivity; continual testing by

using parameter –t.

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 204
Job Aids
These job aids are available to help you complete the lab activity:
 The instructor will provide you with your pod number and other pod-access information.
Log this information in the table.

Pod-Access Information

Parameter Value

Your pod number

Username on router R1 —

Password on router R1 —

Username on router R2 —

Password on router R2 —

Username on router R3 —

Password on router R3 —

Username on PC1 Admin

Password on PC1 ISEisC00L

Username on PC2 Admin

Password on PC2 ISEisC00L

Username on PC3 Admin

Password on PC3 ISEisC00L

Note Routers R1, R2, and R3 are preconfigured to allow access without any credentials. Any Telnet
session or console access will automatically give you access to privileged mode.

 The table illustrates the IPv4 and IPv6 addressing scheme that is used in this lab exercise.

Pod Addressing

Device Interface IPv4 Address and Mask IPv6 Address and Mask

R1 GigabitEthernet1 192.168.1.1/24 2001:db9:1:1::1/64

R1 GigabitEthernet2 192.168.101.1/30 2001:db9:1:a::1/64

R1 GigabitEthernet3 192.168.101.5/30 2001:db9:1:b::1/64

R1 Loopback 1 Unassigned 2001:db9:1:100::1/64

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 205
 Device Interface IPv4 Address and Mask IPv6 Address and Mask

R1 Loopback 2 Unassigned 2001:db9:1:200::1/64

R2 GigabitEthernet1 192.168.2.1/24 2001:db9:2:1::1/64

R2 GigabitEthernet2 192.168.101.2/30 2001:db9:1:a::2/64

R2 Loopback 1 Unassigned 2001:db9:2:100::1/64

R2 Loopback 2 Unassigned 2001:db9:2:200::1/64

R3 GigabitEthernet1 192.168.3.1/24 2001:db9:3:1::1/64

R3 GigabitEthernet2 192.168.101.6/30 2001:db9:1:b::2/64

R3 Loopback 1 Unassigned 2001:db9:3:100::1/64

R3 Loopback 2 Unassigned 2001:db9:3:200::1/64

PC1 LAB 192.168.1.2/24 2001:db9:1:1::f/64

PC2 LAB 192.168.2.2/24 2001:db9:2:1::f/64

PC3 LAB 192.168.3.2/24 2001:db9:3:1::f/64

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 206
Task 0: Reset the Router for this Lab
In this task, you will reset the router(s) for the beginning of this lab. The process is using a configure
restore option within IOS. There are command aliases already configured as the baseline of the routers
and they reference configurations found in flash.

Activity Procedure
Complete the following steps:
Step 1 Connect to Router 1 (R1) and get to privileged mode.
Step 2 Type lab-5-1 and type Y to confirm.

Step 3 Repeat the action on Router 2 (R2) and Router 3 (R3).

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 207
Task 1: Configure Multicast by Using Static RPs
This task will use static RP multicast, in which the RP is manually configured on all designated routers
in the environment. In this case, you will use only the shared tree.

Activity Procedure
Complete the following steps:
Step 1 Enable IPv6 multicast routing on routers R1, R2, and R3.
Step 2 Configure all routers to remain on the shared tree and to route multicast traffic.

Note The Cisco router must be enabled to route IPv6 traffic for unicast traffic in general; the router must
be explicitly configured to route multicast traffic. In addition, by default, the Cisco PIM
implementation allows the last-hop designated router (the router with attached listeners) to move
immediately to the source tree, after locating the source via the RP.

Step 3 Static RP requires manual configuration of the RP location on all designated

routers. The RP for all streams will be the Loopback 1 interface on router R1.
Configure the RP address on routers R1, R2, and R3.

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 208
 Step 4 Cisco routers construct a PIM tunnel immediately upon configuration of the RP.
Review the PIM tunnel state on each router.

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 209
Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 210
 Step 5 Also review the PIM topology and the multicast routing table on R1. The topology
should be empty because there are no senders or receivers.

Step 6 On PC1, open a command prompt and start a continuous ping to the multicast
address ff15::15. Use the ping -t ff15::15 command, which will simulate a stream
source at the multicast address ff15::15.

Note Videos cannot be multicast in this type of lab because of infrastructure constraints. A simple IPv6
ping will successfully replace the need for video streams. At the moment, there is no receiver, so
the multicast echo requests will go unanswered.

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 211
 Step 7 Review the PIM topology on R1 again.

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 212
 Step 8 On PC2, start the VLC media player and prepare to receive the desired stream.

Step 9 In the VLC media player, choose Media > Open Network Stream. In the dialog
box, choose UDP/RTP Multicast, and enter the multicast address ff15::15.
Click OK. PC2 will issue an MLD join to start receiving the stream.

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 213
Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 214
 Step 10 You may not receive replies to your multicast ping, but that’s ok.
Step 11 Review the PIM topology on R1 again.

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 215
 Step 12 Also review the PIM topology on R2.

Step 13 On router R2, display the multicast addresses for which the router has received
MLD joins, or receivers, signaling an interest in a particular multicast stream.

Step 14 Start another VLC player on PC3 and connect to the same UDP/RTP Multicast
address (ff15::15).

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 216
Activity Verification
You have completed this task when you attain this result:
 If you recheck the PIM topology on router R1, you should see two interfaces that are associated
with receivers.

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 217
Display the multicast routing table on R1.

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 218
Task 2: Configure Source-Tree Multicast
Multicast traffic can travel on the shared tree (sourced at the designated RP), or the last-hop
designated router can obtain the stream directly from the first-hop designated router (near the sender)
via a PIM join. When the stream is initially received via the shared tree, and when the designated router
learns the source router location, the designated router can build a source tree directly to that source.

Activity Procedure
Complete the following steps:
Step 1 During the initial PIM configuration, you set a parameter that caused the Cisco
router to use only the shared tree—never try to build a source tree. Remove that
statement on all routers.
Step 2 Clear the current PIM topology. After a short interruption, both streams should
continue to run. If not, reopen the streams in the VLC viewers on PC2 and PC3.

Activity Verification
You have completed this task when you attain this result:
 On router R1, wait for a moment for the multicast topology to converge, and then examine the
PIM topology.

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 219
 Note Notice that a source tree is now built for the stream. The listed source tree carries the tag SPT.
The original shared-tree topology is also still in the PIM table.

Task 3: Configure BSR

Manual configuration of RPs within a multicast environment requires ongoing administration, because
each designated router must be reconfigured if the RP moves. IPv6 multicast supports BSR (Bootstrap
Router), which allows the IPv6 address of the RP to be dynamically advertised within a multicast
domain.

Activity Procedure
Complete the following steps:
Step 1 On PC1, stop the multicast source by using the <Ctrl>+<C> key combination in
the command prompt with the continuous ping.
Step 2 On PC2 and PC3, stop the receivers by closing the VLC application.
Step 3 On all routers, remove the existing static RP and put back the router restriction to
always stay on the shared multicast tree (never building the source tree).
Step 4 On all routers, verify that the PIM topology is empty by clearing it.

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 220
 Step 5 On R1, configure the router to be the RP candidate by using the ipv6 pim bsr
candidate rp command. Link the process to the Loopback 1 address.
Step 6 On R1, configure the router to also be the BSR candidate by using the ipv6 pim
bsr candidate bsr command. Also linked to its Loopback 1 interface.

Step 7 On PC1, start a continuous ping that uses the ff7e:140:2001:db9:1:1:: address.
Step 8 On PC2 and PC3, use the VLC media player to receive the previous multicast
group.

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 221
Activity Verification
You have completed this task when you attain these results:
 On R1, verify the multicast topology.

 On R2, view the joined listeners that use embedded RP addresses.

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 222
  On R2 and R3, view the view the PIM topology and you should see that the RP is R1’s loopback
interface, but if you look at the configuration for the RP address, there shouldn’t be any
configuration for it.

Discovery Lab 9 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 223
Discovery Lab 10:
Configure NAT64 Services
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will configure a central router to perform NAT64 using static mappings. After
completing this activity, you will be able to meet these objectives:
 Configure a router to perform NAT64 Translations.
 Describe Static NAT64 Operations and communication flows.

Discovery Lab 10 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 224
Visual Objective
The figure illustrates what you will accomplish in this activity.

Need to change
from R6 to R5 for
both lab 10 & 11

Required Resources
The table lists the resources and equipment that are required to complete this activity.

Device Name Device Role in the Laboratory

R1 IPv4 only Router

R3 NAT64 Translator

R5 IPv6 only Router

Discovery Lab 10 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 225
Command List
The table describes the commands that are used in this activity.

Cisco IOS Software Commands

Command Description

debug ipv6 nd Displays debug messages for IPv6 ICMP

neighbor discovery transactions.

ipv6 address ipv6-address Configures an IPv6 address on an interface.

ipv6 nd prefix ipv6-prefix/prefix- Configures an IPv6 prefix advertisement; allows

length [valid-lifetime preferred- control over the individual parameters per prefix.
lifetime]
ipv6 nd ra-interval maximum-secs Configures the interval between IPv6 router
advertisement transmissions on an interface.

ipv6 nd ra suppress Suppresses IPv6 router advertisement

transmissions on a LAN interface.

ping ipv6 ipv6-address Diagnoses basic network connectivity when

using IPv6.

undebug all Disables all debugging processes.

Job Aids
These job aids are available to help you complete the lab activity:
 The instructor will provide you with your pod number and other pod-access information. Log this
information in the table.

Pod-Access Information

Parameter Value

Your pod number

Username on router R1,R3,R5 —

Password on router R1,R3,R5 —

Note Router R1, R3 and R5 are preconfigured to allow access without any credentials. Any Telnet
session or console access will automatically give you access to privileged mode.

 The table illustrates the IPv4 and IPv6 addressing scheme that is used in this lab exercise.

Discovery Lab 10 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 226
Pod Addressing

Device Interface IPv4 Address and Mask IPv6 Address and Mask

R1 GigabitEthernet 3 192.168.13.1/24

R3 GigabitEthernet 2 192.168.13.3/24

GigabitEthernet 3 2001:DB8:3535:3535::3/64

R6 GigabitEthernet 2 2001:DB8:3535:3535::5/64

Task 0: Reset the Router for this Lab

In this task, you will reset the router(s) for the beginning of this lab. The process is using a configure
restore option within IOS. There are command aliases already configured as the baseline of the routers
and they reference configurations found in flash.

Activity Procedure
Complete the following steps:
Step 1 Connect to Router 1 (R1) and get to privileged mode.
Step 2 Type Baseline and type Y to confirm.

Step 3 Repeat this process for R3 and R5.

Discovery Lab 10 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 227
Task 1: Configure R1 as an IPv4 Only Router
In this task, you will configure router R1 with a single IPv4 address on interface GigabitEthernet 3.

Activity Procedure
Complete the following steps:
Step 1 On the GigabitEthernet 3 interface, configure an IPv4 address of 192.168.13.1/24
and “no shut” the interface.

Step 2 Type end.

Activity Verification
You have completed this task when you attain these results:
 On R1, observe the console output.

 As a final verification type show ip interface brief | exc assigned and press enter:

Note that the interface is UP/UP.

Discovery Lab 10 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 228
Task 2: Configure R3 for both IPv4 and IPv6
In this task, you will reconfigure router R3 with a single ipv4 address on GigabitEthernet 2 and a single
ipv6 address on GigabitEthernet 4.

Activity Procedure
Complete the following steps:
Step 1 On R3, apply the IPv4 address 192.168.13.3/24 on GigabitEthernet 2 and no
shut the interface.

Step 2 Apply the IPv6 address of 2001:DB8:3535:3535::3/64 on GigabitEthernet 3 and

no shut the interface.

Step 3 Enable ipv6 unicast routing.

Activity Verification
You have completed this task when you attain these results:
 To verify the applied configuration for IPv4 use the show ip interface brief | exc assigned
command:

Discovery Lab 10 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 229
  To verify the applied configuration for IPv4 use the show ipv6 interface brief | exc assigned
command:

 Note that in both instances the relevant interfaces are up/up

 We will wait until R6 is configured to perform reachability testing.

Discovery Lab 10 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 230
Task 3: Configure R6 as an IPv6 Only Router
In this task, you will configure router R6 with a single IPv6 address on interface GigabitEthernet 1.

Activity Procedure
Complete the following steps:
Step 1 On the GigabitEthernet 2 interface, configure an IPv6 address of
2001:DB8:3535:3535::6/64 and “no shut” the interface.

Step 2 Enable IPv6 unicast routing.

Step 3 Configure a static IPv6 default route on R6:

Activity Verification
You have completed this task when you attain these results:
 On R5, observe the console output.

 As an additional verification type show ipv6 interface brief and press enter:

Discovery Lab 10 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 231
 Note that the interface is UP/UP.
 Verify the static ipv6 default route using the show ipv6 route static command.

 Our final verification will involve executing a ping between the IPv6 enabled interfaces
connection R3 and R5. Run a ping test from R6 toward the ipv6 address assigned to R3
(2001:DB8:3535:3535::3).

Discovery Lab 10 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 232
Task 4: Configure Static NAT64 on R3
In this task, you will configure router R6 with a single IPv6 address on interface GigabitEthernet 1.

Activity Procedure
Complete the following steps:
Step 1 Before we apply the NAT64 configuration on R3 we will want to test reachability.
So we will ping the IPv4 address on R1 (192.168.13.1) and the IPv6 address on
R6 (2001:DBA:3535:3535::6). If your pings are successful move to step 2. If the
pings fail, you will need to validate your configurations on R1 and R6.

Step 2 Given the pings are successful in step 1, it is now safe to configure NAT64 on
both GigabitEthernet 2 and GigabitEthernet 3 on R3.

Step 3 Now we can configure the translation rules for this process. We will need to
create a “fake address” for testing. This address will pretend to be a destination
address that R1 can reach. We will use the address 192.168.13.5 in this lab for
testing. We will also need to allocate an IPv6 prefix that will be used by the
NAT64 translation process. IANA has allocated a reserved prefix of 64:FF9B::/96
for this purpose, but we can define our own. In this instance we will use 3001::/96
for simplicity.

Discovery Lab 10 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 233
 Note The translation rule tells R3 that whenever it receives an IPv4 packet with a destination address of
192.168.13.5 that it must translate and forward that packet to 2001:DB8:3535:3535::5.

Activity Verification
You have completed this task when you attain these results:
 On R1, enable ip icmp debugging.

 On R6, enable ipv6 icmp debugging.

 From R1’s console ping the “fake IPv4” address 192.168.13.6.

 Now that we see that the ping has worked, we want to look closer at the debug output. We can
see that R1 thinks that the packet it received was coming from 192.168.13.5 (the fake address).

 Now we will look at the debug from R5. Here we see that R3 thinks that it is talking with
3001::C0A:D01. The first part of this address is the 3001::/96 prefix we configured on R3.
The last part is the IPv4 address of R1 in hexadecimal format.
— C0 = 192
— A8 = 168
— D = 13
— 1=1

Discovery Lab 10 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 234
  We can further validate that his process works in the reverse direction by initiating a ping from
R5 destined to the NAT64 derived address:

 Furthermore, we can display the Network Address Translation 64 mappings on R3 by using the
show nat64 mappings static command:

 To display the NAT64 packet count statistics use the show nat64 statistics command.

Discovery Lab 10 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 235
Discovery Lab 10 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 236
Remaining output not provided.
 To see the NAT64 Translations use the show nat64 translations command.

Discovery Lab 10 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 237
Discovery Lab 10 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 238
Discovery Lab 11: Configure
NAT64 Dynamic Serivces
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will configure a central router to perform NAT64 using dynamic mappings. After
completing this activity, you will be able to meet these objectives:
 Configure a router to perform dynamic NAT64 Translations.
 Describe the difference between Static and Dynamic NAT64 Operations and communication
flows.

Discovery Lab 11 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 239
Visual Objective
The figure illustrates what you will accomplish in this activity.

Required Resources
The table lists the resources and equipment that are required to complete this activity.

Device Name Device Role in the Laboratory

R1 IPv4 only Router

R3 NAT64 Translator

R5 IPv6 only Router

Discovery Lab 11 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 240
Command List
The table describes the commands that are used in this activity.

Cisco IOS Software Commands

Command Description

debug ipv6 nd Displays debug messages for IPv6 ICMP

neighbor discovery transactions.

ipv6 address ipv6-address Configures an IPv6 address on an interface.

ipv6 nd prefix ipv6-prefix/prefix- Configures an IPv6 prefix advertisement; allows

length [valid-lifetime preferred- control over the individual parameters per prefix.
lifetime]
ipv6 nd ra-interval maximum-secs Configures the interval between IPv6 router
advertisement transmissions on an interface.

ipv6 nd ra suppress Suppresses IPv6 router advertisement

transmissions on a LAN interface.

ping ipv6 ipv6-address Diagnoses basic network connectivity when

using IPv6.

undebug all Disables all debugging processes.

Job Aids
These job aids are available to help you complete the lab activity:
 The instructor will provide you with your pod number and other pod-access information. Log this
information in the table.

Pod-Access Information

Parameter Value

Your pod number

Username on router R1,R3,R5 —

Password on router R1,R3,R5 —

Note Router R1, R3 and R5 are preconfigured to allow access without any credentials. Any Telnet
session or console access will automatically give you access to privileged mode.

The table illustrates the IPv4 and IPv6 addressing scheme that is used in this lab exercise.

Discovery Lab 11 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 241
Pod Addressing

Device Interface IPv4 Address and Mask IPv6 Address and Mask

R1 GigabitEthernet 3 192.168.13.1/24

R3 GigabitEthernet 2 192.168.13.3/24

GigabitEthernet 3 2001:DB8:3535:3535::3/64

R5 GigabitEthernet 2 2001:DB8:3535:3535::5/64

Discovery Lab 11 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 242
Task 0: Reset the Router for this Lab
In this task, you will reset the router(s) for the beginning of this lab. The process is using a configure
restore option within IOS. There are command aliases already configured as the baseline of the routers
and they reference configurations found in flash.

Activity Procedure
Complete the following steps:
Step 1 Connect to Router 1 (R1) and get to privileged mode.
Step 2 Type NAT64-Lab-2 and type Y to confirm.

Step 3 Repeat this process for R3 and R5.

Discovery Lab 11 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 243
Task 1: Configure a Static Route on R1
In this task, you will configure a static route on router R1 for network 27.1.1.0/24 directed toward the
next hop of 192.168.13.3.

Activity Procedure
Complete the following steps:
Step 1 On R1 Configure a static route for 27.1.1.1/24 using the destination
192.168.13.3.

Step 2 Type end and select enter.

Activity Verification
You have completed this task when you attain these results:
 On R1, validate the default router by typing show ip route static.

Discovery Lab 11 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 244
Task 2: Configure Dynamic NAT64 on R3
In this task, you will configure dynamic NAT64 translation on R3 using a NAT64 pool.

Activity Procedure
Complete the following steps:
Step 1 On R3 remove the previous static NAT64 rule. By using the command no nat64
v6v4 static 2001:DB8:3535:3535::6 192.168.13.6.

Step 2 On R3, create an IPv6 ACL that matches the source IPv6 network used on the
link toward R5 (2001:DB8:3535:3535::/64) for any destination.

Step 3 On R3, create a nat64 ipv4 address pool named pool1 ranging from 27.1.1.10 to
27.1.1.11.

Step 4 Create a NAT64 Translation rule that allows a v6 to V4 translation from traffic
that is permitted by the IPv6 ACL and destined to the

Step 5 Now we will specify the stateful prefix range of 3001::/96 as we did before.

Note The translation rule tells R3 that whenever it receives an IPv4 packet with a destination address
matching the pool specified that it must translate and forward that packet to the network
2001:DB8:3535:3535::/64.

Activity Verification
You have completed this task when you attain these results:
 On R1, enable ip icmp debugging.

Discovery Lab 11 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 245
  On R5, enable ipv6 icmp debugging.

 From R5’s console ping the NAT64 translated IPv6 address 3001::C0A8:D01. Note that the ping
was initiated from the IPv6 side of the network and that we get replies.

 Looking at the results of the debug we can see that the Src of the echo reply is the correct
address in IPv6 format.

 Now we will look on R3 to see the translation that took place. We can see that the address
192.168.13.1 was mapped to address 27.1.1.10 in this example. Using this information, we will
ping that address from the console of R1.

Discovery Lab 11 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 246
  From R1 ping the address we found in the NAT64 Translation table on R3

 Furthermore, we can display the Network Address Translation 64 mappings on R3 by using the
show nat64 mappings dynamic command:

Discovery Lab 11 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 247
Discovery

Discovery Lab 11 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 248
Discovery Lab 12:
Configure DNS64 Services
This Lab is still a work in progress. Need to insert.

Discovery Lab 12 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 249
Discovery Lab 13:
Configure Advanced ACLs
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will configure various types of ACLs, to achieve the desired filtering objectives.
After completing this activity, you will be able to meet these objectives:
 Create and apply a standard ACL (matching on source and destination addresses only).
 Create and apply an extended ACL (matching on addresses, ports, and other packet
information).
 Create and apply a reflexive ACL (matching on outgoing packets and creating dynamic inbound
rules).
 Create and apply an extended ACL (matching on IPv6 extension headers).
 Create and apply an ACL to control inbound IPv6 access to a router.

Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 250
Visual Objective
The figure illustrates what you will accomplish in this activity.

Required Resources
The table lists the resources and equipment that are required to complete this activity.

Device Name Device Role in the Laboratory

R1 Access router in the Central Site; used as the default gateway for IPv4 and
IPv6 traffic.

R2 Access router in the Remote Site; used as the default gateway for IPv4 and
IPv6 traffic.

PC1 End user with applications that require both IPv4 and IPv6 support by the
operating system and the network.

Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 251
 Device Name Device Role in the Laboratory

PC2 End user with applications that require both IPv4 and IPv6 support by the
operating system and the network.

Command List
The table describes the commands that are used in this activity.

Cisco IOS Software Commands

Command Description

clear ipv6 access-list [ACL-ID] Resets the IPv6 access-list match counters.

ipv6 access-class ACL-ID Applies restrictions to vty capabilities.

ipv6 access-list ACL-ID filter- Creates an IPv6 ACL on Cisco IOS devices.
rules
ipv6 traffic-filter ACL-ID [in | Applies an IPv6 ACL to an interface.
out]
line vty 0 4 Selects inbound vty connections (such as an
interface on which to apply access restrictions).

show ipv6 access-list Shows existing IPv6 ACLs.

show ipv6 interface brief Shows brief IPv6 interface information.

Windows PC Commands

Command Description

netsh interface ipv6 show interface Displays Windows 10 interfaces.

[interface]
ping6 IPv6-address Sends pings from Windows 10 by using an
[-r] optional routing header.

telnet ip-address Uses Telnet from Windows 10.

Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 252
Job Aids
These job aids are available to help you complete the lab activity:
 The instructor will provide you with your pod number and other pod-access information. Log this
information in this table.

Pod-Access Information

Parameter Value

Your pod number

Username on router R1 admin

Password on router R1 ISEisC00L

VTY Password on router R1 cisco

Username on router R2 admin

Password on router R2 ISEisC00L

Username on PC1 Admin

Password on PC1 ISEisC00L

Username on PC2 Admin

Password on PC2 ISEisC00L

Note Routers R1 and R2 are preconfigured to allow access without any credentials. Any Telnet session
or console access will automatically give you access to privileged mode.

 The table illustrates the IPv4 and IPv6 addressing scheme that is used in this lab exercise.

Pod Addressing

Device Interface IPv4 Address and Mask IPv6 Address and Mask

R1 GigabitEthernet 1 192.168.1.1/24 2001:db9:1:1::1/64

R1 GigabitEthernet 2 192.168.101.1/30 2001:db9:1:a::1/64

R1 Loopback 1 Unassigned 2001:db9:1:100::1/64

R1 Loopback 2 Unassigned 2001:db9:1:200::1/64

R2 GigabitEthernet 1 192.168.2.1/24 2001:db9:2:1::1/64

R2 GigabitEthernet 2 192.168.101.2/30 2001:db9:1:a::2/64

R2 Loopback 1 Unassigned 2001:db9:2:100::1/64

Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 253
 Device Interface IPv4 Address and Mask IPv6 Address and Mask

R2 Loopback 2 Unassigned 2001:db9:2:200::1/64

PC1 LAB 192.168.1.2/24 2001:db9:1:1::f/64

PC2 LAB 192.168.2.2/24 2001:db9:2:1::f/64

Task 0: Reset the Router for this Lab

In this task, you will reset the router(s) for the beginning of this lab. The process is using a configure
restore option within IOS. There are command aliases already configured as the baseline of the routers
and they reference configurations found in flash.

Activity Procedure
Complete the following steps:
Step 1 Connect to Router 1 (R1) and get to privileged mode.
Step 2 Type lab-7-1 and type Y to confirm.

Step 3 Repeat the action on Router 2 (R2).

Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 254
Task 1: Configure a Standard ACL for IPv6 (Layer 3
Address Filtering)
Traffic through the router can be controlled by using a standard ACL, which filters traffic only according
to IP source and destination addresses—no other packet parameters are examined. In this task, you
will explicitly permit traffic between some endpoints while denying all other traffic.

Activity Procedure
Complete the following steps:
Step 1 Check the reachability of R1 interfaces from PC1. Ping the following addresses
(all addresses should be reachable):
 GigabitEthernet 1 (2001:db9:1:1::1)
 Loopback 1 (2001:db9:1:100::1)
 Loopback 2 (2001:db9:1:200::1)
 GigabitEthernet 2 (2001:db9:1:a::1)
Step 2 On R1, create a IPv6 ACL that is named LANin and that allows access only to
Loopback 1 and Loopback 2 from PC1.

Note Depending on version of code, the implicit deny all at the end of the access list will still allow for
neighbor solicitation and neighbor advertisements to function. In our version of the lab, it does not.

Step 3 Apply the new LANin IPv6 ACL in the inbound direction on interface
GigabitEthernet 1.

Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 255
Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 256
Activity Verification
You have completed this task when you attain these results:
 On PC1, repeat the ping tests to all interfaces of R1:
GigabitEthernet 1 (2001:db9:1:1::1)
Loopback 1 (2001:db9:1:100::1)
Loopback 2 (2001:db9:1:200::1)
GigabitEthernet 2 (2001:db9:1:a::1)
This time, only pings to interfaces Loopback 1 and Loopback 2 should succeed.

Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 257
  On R1, review the ACL statistics.

Note An explicit deny at the end of the ACL is needed to collect the statistics of denied packets.

Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 258
Task 2: Configure an Extended ACL for IPv6 (Layer
3 and Layer 4 Filtering)
An extended ACL allows for deeper inspection of packets at the interface on which the ACL is applied.
In this task, you will inspect Layer 4 (TCP/UDP ports and ICMP messages) as well as Layer 3 (IPv6
addresses and protocol numbers) attributes.

Activity Procedure
Complete the following steps:
Step 1 Test connectivity from PC1 to the Loopback 1 interface on R1 for two TCP
services:
 Use IPv6 Telnet to connect to router R1. Password is cisco.
 Use a web browser to connect to the SDM on R1.
Use the https://[2001:db9:1:100::1] URL.

Note IPv6 addresses that are used in URLs should be enclosed in brackets.

Note On router R1, username admin with password ISEisC00L is preconfigured.

Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 259
 Step 2 On R1, create a new IPv6 ACL that is named LANin2 and that implements the
following policy:
 Allow Telnet access from PC1 to the Loopback 1 address of router R1.
 Permit all neighbor-solicitation ICMP messages (nd-ns).
 Permit all neighbor-advertisement ICMP messages (nd-na).
 Explicitly deny all other traffic. (Use sequence number 1000 for this entry.)

Note ICMP neighbor solicitation and advertisement messages are required for resolving link-layer
addresses on a LAN. An implicit deny statement at the end of an ACL permits neighbor discovery
messages by default. An explicit deny statement at the end of an ACL requires these messages to
be permitted.

Step 3 Replace the previous inbound IPv6 ACL on the GigabitEthernet 1 interface with
the new LANin2 ACL.

Activity Verification
You have completed this task when you attain these results:
 Retest connectivity from PC1 to the Loopback 1 interface on R1 for the two TCP services:
— Use IPv6 Telnet to connect to R1. The connection should still be successful.

Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 260
 — Use a web browser to connect to the SDM on R1. Use URL https://[2001:db9:1:100::1].
SDM connectivity should no longer work because it is not specifically permitted. You may
alternatively use the Telnet application to try to connect to port 443.

 On R1, review the ACL statistics.

Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 261
 Note An explicit deny at the end of the new ACL allows you to also see the statistics about denied
packets.

Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 262
Task 3: Configure an Extended ACL for IPv6
(Extension Header Matching)
IPv6 extension header fields are visible to Cisco extended ACLs, and traffic can be filtered based on
header field values. In this task, you will filter traffic that uses the routing extension header.

Activity Procedure
Complete the following step:
Step 1 On R1, add the following entries to the existing IPv6 ACL that is used inbound on
the GigabitEthernet 1 interface. Add the entries before the explicit deny
statement at the end.
 Deny IPv6 packets with the routing extension header.
 Permit ICMP packets from the prefix off of GigabitEthernet 1 interface on R1.

Activity Verification
You have completed this task when you attain these results:
 Start the Wireshark application on PC1. Find the application icon on the desktop.

 Choose Capture > Start.

Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 263
  Send a ping from PC1to the GigabitEthernet 1 interface of R1. The ping should be successful.
You should also see four ICMP echo requests and four ICMP echo replies in the Wireshark
capture window, as shown in the previous figure.

 Send another ping from PC1 to the GigabitEthernet 1 interface of R1, this time using the -R
option, which adds the routing header to the IPv6 packets. The ping should be unsuccessful.
You should also see four new ICMP echo requests and four ICMP unreachable replies in the
Wireshark capture window, as shown in the following figure.

Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 264
 Note If you select one of the echo requests just before an unreachable reply, you should see that the
IPv6 packet has a routing header that should be denied by your ACL, hence the unreachable reply.

 Choose Capture > Stop. Close the Wireshark capture window and close the Wireshark
application.

Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 265
Task 4: Control Inbound IPv6 Access to a Router
Telnet access to the router itself can be controlled for IPv6 like it can be for IPv4, using an access class
on a range of vty lines. In this task, you will create an ACL to control inbound Telnet access to router
R2.

Activity Procedure
Complete the following steps:
Step 1 On R1, add a sequence 50 to permit the prefix from GigabitEthrenet1 to reach
R2 GigabitEthernet2 address via telnet.

Step 2 Connect via Telnet from PC1to the GigabitEthernet 2 interface of R2. This Telnet
session should succeed.

Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 266
 Step 3 Connect via Telnet from PC2 to the GigabitEthernet 1 interface of R2. This Telnet
session should succeed.

Step 4 On R2, create an IPv6 ACL that is named VTY and that allows only remote
administration from R1 GigabitEthernet 1 prefix (2001:db9:1:1::/64) remotely
access any interface address of router R2.
Step 5 Apply the VTY IPv6 ACL as an access class to the 0–4 range of vty.

Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 267
Activity Verification
You have completed this task when you attain these results:
 Connect again via Telnet from PC1 to the GigabitEthernet 2 interface of R2. This Telnet session
should succeed.

 Connect again via Telnet from PC2 to the GigabitEthernet 1 interface of R2. This Telnet session
should fail.

Discovery Lab 13 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 268
Discovery Lab 14:
Implementing IPsec and IKE
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will use cryptography (IPsec) to secure communication between two sites.
After completing this activity, you will be able to meet this objective:
 Secure communications between routers by using IPsec.

Discovery Lab 14 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 269
Visual Objective
The figure illustrates what you will accomplish in this activity.

Required Resources
The table lists the resources and equipment that are required to complete this activity.

Device Name Device Role in the Laboratory

R1 Access router in the Central Site; used as the default gateway for IPv4 and
IPv6 traffic.

R2 Access router in the Remote Site; used as the default gateway for IPv4 and
IPv6 traffic.

PC1 End user with applications that require both IPv4 and IPv6 support by the
operating system and the network.

Discovery Lab 14 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 270
 Device Name Device Role in the Laboratory

PC2 End user with applications that require both IPv4 and IPv6 support by the
operating system and the network.

Command List
The table describes the commands that are used in this activity.

Cisco IOS Software Commands

Command Description

authentication pre-share Configures the authentication method by using

pre-shared keys for an IKE policy.

crypto ipsec transform-set Defines a transform set (a combination of security

transform-set-name transform1 protocols and algorithms).
[transform2 [transform3]]
crypto isakmp key keystring address Configures a pre-shared IKE authentication key.
peer-address
crypto isakmp policy priority- Defines an IKE policy and assigns a priority to the
number policy.

encryption [des | 3des | aes [128 | Specifies the encryption algorithm within an IKE
192 | 256]] policy.

group {1 | 2 | 5} Specifies the Diffie-Hellman group identifier within

an IKE policy.

hash {md5 | sha-1} Selects a hash function to use within an IKE

policy.

interface tunnel inft Static VTI that uses IPv6 for payload and
tunnel mode ipsec ipv6 transport.

ipv6 rip process enable Enables IPv6 RIP on an interface.

ipv6 router rip process Configures an IPv6 RIP process.

lifetime seconds Specifies the lifetime of IKE sessions within an

IKE policy.

mode {transport | tunnel} Selects the IPsec mode within a transform set;
tunnel mode is the default.

show crypto ipsec sa Shows Phase 1 SAs and proxy, encapsulation,

encryption, de-encapsulation, and decryption
information.

show crypto isakmp sa Lists IKE sessions and their main parameters.

show ipv6 route Displays IPv6 routing table.

Discovery Lab 14 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 271
 Command Description

tunnel destination address Specifies the destination address for tunnel

packets.

tunnel protection ipsec profile Selects an IPsec profile to use for protecting the
profile VTI.

tunnel source {intf | address} Specifies the source address for tunnel packets.

Windows PC Commands

Command Description

ping ipv6-address Diagnoses IPv6 connectivity.

tracert ipv6-address Verifies path to the specific IPv6 address.

Job Aids
These job aids are available to help you complete the lab activity:
 The instructor will provide you with your pod number and other pod-access information.
Log this information in this table.

Pod-Access Information

Parameter Value

Your pod number

Username on router R1 —

Password on router R1 —

Username on router R2 —

Password on router R2 —

Username on PC1 Admin

Password on PC1 ISEisC00L

Username on PC2 Admin

Password on PC2 ISEisC00L

Note Routers R1 and R2 are preconfigured to allow access without any credentials. Any Telnet session
or console access will automatically give you access to the privileged mode.

Discovery Lab 14 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 272
  The table illustrates the IPv4 and IPv6 addressing scheme that is used in this lab exercise.

Pod Addressing

Device Interface IPv4 Address and IPv6 Address and

Mask Mask

R1 GigabitEthernet1 192.168.1.1/24 2001:db9:1:1::1/64

R1 GigabitEthernet2 192.168.101.1/30 2001:db9:1:a::1/64

R1 Loopback 1 Unassigned 2001:db9:1:100::1/64

R1 Loopback 2 Unassigned 2001:db9:1:200::1/64

R2 GigabitEthernet1 192.168.2.1/24 2001:db9:2:1::1/64

R2 GigabitEthernet2 192.168.101.2/30 2001:db9:1:a::2/64

R2 Loopback 1 Unassigned 2001:db9:2:100::1/64

R2 Loopback 2 Unassigned 2001:db9:2:200::1/64

PC1 LAB 192.168.1.2/24 2001:db9:1:1::f/64

PC2 LAB 192.168.2.2/24 2001:db9:2:1::f/64

Discovery Lab 14 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 273
Task 0: Reset the Router for this Lab
In this task, you will reset the router(s) for the beginning of this lab. The process is using a configure
restore option within IOS. There are command aliases already configured as the baseline of the routers
and they reference configurations found in flash.

Activity Procedure
Complete the following steps:
Step 1 Connect to Router 1 (R1) and get to privileged mode.
Step 2 Type lab-7-2 and type Y to confirm.

Step 3 Repeat the action on Router 2 (R2).

Discovery Lab 14 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 274
Task 1: Configure IPsec
In this task, you will configure an IPsec tunnel to protect traffic between a pair of remote sites across an
untrusted transport network.

Activity Procedure
Complete the following steps:
Step 1 Configure an IKE policy on R1 and R2. Use the parameters that are listed in the
table.

IKE Policy Parameters

Parameter Value

Encryption AES using 256-bit keys

Hash SHA256

Authentication Pre-shared key

Diffie-Hellman Group 5

Lifetime 1 hr

Step 2 Define a pre-shared key, named tOpSeCrEt, to authenticate IKE peers on the
GigabitEthernet2 addresses (that is, 2001:db9:1:a::1 on R2 and 2001:db9:1:a::2
on R1). Make sure that you use the same key on both routers.
Step 3 Configure an IPsec transform set named TS. Use the parameters that are listed
in the table.

IPsec Transform Set Parameters

Parameter Value

Protocol ESP for encryption and authentication

Encryption AES using 256-bit keys

Authentication and Integrity SHA-1

Mode Tunnel

Lifetime 1 hr

Step 4 Configure an IPsec profile named IP. Use the TS IPsec transform set.

Discovery Lab 14 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 275
 Note With the preshared key, the example shows a specific host with a /128, but it could have been the
prefix with a /64 or all possible neighbors with a /0.

Step 5 Configure a static VTI. Use the parameters that are listed in the table.

Static VTI Parameters

Parameter R1 R2

IPv6 Address 2001:db9:3:1::1/64 2001:db9:3:1::2/64

Tunnel Source GigabitEthernet2 GigabitEthernet2

Tunnel Destination 2001:db9:1:a::2 2001:db9:1:a::1

Tunnel Mode IPsec IPv6 IPsec IPv6

Discovery Lab 14 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 276
 Parameter R1 R2

Tunnel Protection IP IPsec profile IP IPsec profile

Step 6 Create an IPv6 RIP routing process that is named RIP1 on both routers.
Step 7 Enable IPv6 RIP on the following interfaces:
 GigabitEthernet1

Discovery Lab 14 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 277
  Loopback 1
 Loopback 2
 IPsec tunnel

Discovery Lab 14 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 278
Discovery Lab 14 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 279
Activity Verification
You have completed this task when you attain these results:
 IPv6 RIP should trigger the establishment of the IKE session and IPsec SAs. Verify the status of
IKE on either router. You should see an IKE session in the QM_IDLE state that indicates that
the session has reached the Quick Mode phase and is currently idle.

 Verify the status of IPsec SAs on either router. The encryption and decryption statistics should
be non-zero, indicating that packets are being sent and received through the IPsec SAs.

Discovery Lab 14 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 280
  Review the routing table on R1. You should see three routes from R2 that are reachable
through the tunnel interface.

 On PC1, test the reachability of PC2 (use IPv6 address 2001:db9:2:1::f).

Discovery Lab 14 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 281
  Review the IPv6 path between PC1 and PC2.

Discovery Lab 14 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide 282
Discovery Lab 15:
Troubleshooting Tickets 10-12
Complete this lab activity to practice what you learned in the related module.

Activity Objective
In this activity, you will enable HSRP for IPv6 on the Cisco IOS routers R1 and R4. After
completing this activity, you will be able to meet the following objectives:
 Correct all proscribed faults provided by the Senior Engineering Team
 Troubleshoot, remediate, and validate Issues in the Administrative Office (TS1)
 Troubleshoot, remediate, and validate Issues in the Administrative Office associated to
shifting over to Stateful DHCPv6 (TS2)
 Troubleshoot, remediate, and validate Issues in the BVHS Datacenter regarding issues
with reachability to external networks (TS3)

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

Visual Objective
The figure illustrates what you will accomplish in this activity.

Visual Objective for Lab 2-1: Enabling

IPv6 on Hosts ISPv6 (R9)

PC3

PE3 (R6) ISPv4 (R8)

PC2

P (R3) PE1 (R5) A1v4 (R7)

A3v6 (R2) R1
A2v6 (R4)

Static Addressing
PC1 Linux

© 2010 Cisco Systems, Inc. All rights reserved. IP6FD v3.0—LG-2

The lab environment is set up so that IPv4 is already configured on router R1. Configure
Windows 10 on PC1 for IPv4 so that you can use Telnet to connect to the router.

Required Resources
The table lists the resources and equipment that are required to complete this activity.

Device Name Device Role in the Laboratory

R1-R5, R7

PC1-PC2

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide
Command List
The table describes the commands that are used in this activity.

Cisco IOS Software Commands

Command Description

ipv6 address prefix Configures a static IP address on an interface.

ipv6 enable Enables an interface for IPv6.

ipv6 nd ra suppress Suppresses IPv6 router advertisement

transmissions on a LAN interface.

ipv6 unicast-routing Enables IPv6 routing.

show ip interface brief Shows brief IPv4 interface information.

show ip route Shows the IPv4 routing table.

show ipv6 interface brief Shows brief IPv6 interface information.

show ipv6 route Shows the IPv6 routing table.

Microsoft Windows PC Commands

Command Description

netsh interface ip set address Configures the IPv4 address, mask, and default
int_name static ip_addr net_mask gateway to the interface named int_name.
def_gw 1
netsh interface ipv6 add address Adds an IPv6 address to an interface on
int_name ipv6_address Microsoft Windows 10.

netsh interface ipv6 add route Adds a route for a specified prefix.
route int_name next-hop
netsh interface ipv6 show interface Displays Windows 10 interfaces.
[intf]
ping Enters the ping command from Windows 10.

ping6 Enters the ping6 command from Windows 10.

Note You can get detailed help if you type a question mark at the end of the netsh commands;
for example, netsh interface ipv6 add address ?.

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

Linux PC Commands

Command Description

ifconfig Displays all network interface information that

has been configured.

ping Enters the ping command.

ping6 Enters the ping6 command.

Job Aids
These job aids are available to help you complete the lab activity:
 The instructor will provide you with your pod number and other pod-access information.
Log this information in the table.

Pod-Access Information

Parameter Value

Your pod number

Username on router R1 – R5, R7 —

Password on router R1 – R5, R7 —

Username on PC1/PC2 Admin

Password on PC1/PC2 ISEisC00L

Note Router R1-R5 and R7 are preconfigured to allow access without any credentials. Any
Telnet session or console access will automatically give you access to privileged mode.

 The table illustrates the IPv4 and IPv6 addressing scheme that is used in this lab
exercise.

Pod Addressing

Devic Interface IPv4 Address and Mask IPv6 Address and Mask
e

R1 GigabitEthernet1

R4 GigabitEthernet2

PC1 LAB

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide
Task 0: Reset the Router for this Lab
In this task, you will reset the router(s) for the beginning of this lab. The process is using a
configure restore option within IOS. There are command aliases already configured as the
baseline of the routers and they reference configurations found in flash.

Activity Procedure
Complete the following steps:
Step 1 Connect to Router 1 (R1), Router 2 (R2), Router 3 (R3), Router 4 (R4),
Router 5 (R5), Router 7 (R6) and get to privileged mode.
Step 2 Type TS10-12 and type Y to confirm. The illustration below shows this
process on R1 (you will need to execute the same command on all the
routers outlined in Step 1).

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

Trouble Ticket #10:
PC1 Cannot Reach 2001:db9:3:3::3
In this trouble ticket, you will confirm that your PC1 has the necessary IPv6 configuration
information to establish connectivity to a server located in Labor and Delivery (simulated by a
loopback address).

Additional Information: Further testing before this trouble ticket was handed to you mention
that additional prefixes that cannot be reached include 2001:db9:7:7::7 and
2001:db9:199:199:199::199. This represents all of the external prefixes being advertised via
BGP in this lab environment.

Activity Procedure
Complete the following steps:
Step 1 Connect to PC1 and open a command-prompt window. Verify that the PC
indeed cannot reach the ip address 2001:db9:3:3::3, 2001:db9:7:7::7
and 2001:db9:199:199:199::199.

Step 2 Seeing that the IPv6 addresses specified are not reachable we have
verified that the ticket is correct (the “external servers” are not reachable).
The next step will be to verify what IPv6 addresses the device is
configured to use to communicate to R1. By using the ipconfig /all
command.

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

 Step 3 This gives us a lot of localized information regarding the operation of this
workstation now and previous. But the key data relates to the fact that the
device is using a statically assigned ipv6 address of
2001:db9:1:1:xxxx:xxxx:xxxx and the gateway of last resort is FE80::1.
Use the ping FE80::1 command.
This ping should work provided R1 (the next hop device) is correctly
configured at the interface level.

Step 4 The ping works. Now we will engage in what should be another revealing
diagnostic test by attempting to do a trace route to the destination IPv6
address of 2001:db9:7:7::7
Use the tracert 2001:db9:3:3::3 command.

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

 Step 5 The trace-route fails with a Request Timeout message, after it is
successfully sent to R1 via the Gateway address 2001:db9:1:1::1. This
indicates that the best place to start would be at R1 the next logical hop
from PC1 or R3 which would be the point of origin for this prefix. I will
choose to start with R1
Step 6 Open a session to R1 and test to see if the IPv6 address 2001:db9:3:3::3
is reachable.
Use the ping 2001:db9:3:3::3 command.

Step 7 We can clearly see that R1 has reachability to this prefix. This brings a lot
of things into question. First we will need to see how the route is being
learned from the prospective of R1. We will accomplish this using the
show ipv6 route 2001:db9:3:3::3 command.

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

 Step 8 Note that the route is being learned via BGP from the peer
2001:db9:1313::3 (R3). This route is being added to the routing table.
Just as a quick check we will want to determine if the route is valid and
best. We will do this using the show bgp ipv6 unicast command.

Step 9 Note that all the bgp routes are “valid” denoted by the “*” and “best”
denoted by the “>”. Plus, we have reachability to the prefix we tested. So,
this represents an odd situation. After some conversation the
determination is made to specify the source of the ping using the network
2001:db9:1:1::/64. We can do this via the source GigabitEthernet1
keyword and see if the results are the same.

Step 10 This changes things in the scheme of troubleshooting. Note that the
results of the ping seem to indicate that the router is sending data to R3
the next hop neighbor device connected to GigabitEthernet2. The change
was created by specifying the source ipv6 source address. To test to see
what R1 is actually doing with the packets in question I want to debug
ipv6 icmp traffic, and I will test using the ping 2001:db9:3:3::3
command.

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

 Step 11 Note we execute the ping with a repeat count of 2 (to reduce the amount
of debug information) and we see that 2 Echo requests are indeed being
sent to 2001:db9:3:3::3, and we are getting back 2 Echo replies. This
indicates that the ping works as we expect. However, if I repeat the
process specifying the source address of 2001:db9:1:1::1 and look at the
output we should see what is happening from the perspective of how R1
will treat the packets.

Step 12 R1 is sending both echo request packets to 2001:DB9:3:3::3 but note that
no echo replies are coming back from that device. At this point we need
to see what is happening on R3. We will go to the console of that device

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

 and perform a ping test to the source address (2001:db9:1:1::1) we used
on R1.

Step 13 The ping is failing but we see additional information regarding the results
of the ping that we saw on R1. Note we see the “.” which denotes an
“ICMP timeout” which is the same as what we saw on R1, but we also
see an “H” which denotes “host unreachable”. Host unreachable means
we may have a routing issue. To validate this, we will use the show bgp
ipv6 2001:db9:1:1::1 command and look at the results.

Step 14 This output indicates that the prefix 2001:db9:1:1::1/64 which resides on
R1 GigabitEthernet1 is being learned via a “static” entry on R3. Note that
the output shows the backup from “ospf”. We can see the update in the
OSPF database that shows the Inter Area Prefix Link State
Advertisement coming from R3 (0.0.0.3) via the show ipv6 ospf
database inter-area prefix 2001:db9:1:1::1/64 command.

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

 This output indicates that the route is being learned via OSPF but due to the
Administrative Distance of 110 for the OSPF prefix being less preferred than the
Administrative Distance of a Static Route which is 1 R3 is selecting the static route
over the OSPF learned prefix.
Step 15 To take a closer look at this we need to look at the configuration of the
static route on R3. We will do this by using the command show run | inc
ipv6 route.

Step 16 This is breaking out configuration. Since the static route is a valid route
that is installed in the local routing table, BGP can use it as part of the
valid and best computation in BGP. However, this static route is not
configurationally valid and is stopping our pings from working. To correct
this issue, we will remove the static route and allow the OSPF update to
replace it.

Step 17 Now that the static route is removed we will check to see what was
installed in the routing table by using the show ipv6 route
2001:db9:1:1::/64 command.

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

 Step 18 We now see the prefix is learned via “ospf 1” and we see that we are
resolving the link-local IPv6 address of the originating device R1. Now
let’s test to see if R3 can ping the address 2001:db9:1:1::1.

Step 19 The ping works from R3, now we will validate reachability from PC1.

Step 20 A final test would be to ping the other prefixes 2001:db9:7:7::7 and
2001:db9:199:199:199::199.

Step 21 This has remediated this ticket.

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide
Trouble Ticket #11:
Multicast Streaming Test Fails
The network engineering team is testing a multicast deployment scenario. In this scenario the
team has decided to position a multicast streaming server in MOB1 that will stream multicast
traffic using the IPv6 Multicast Address FF07::7. The team has decided during this testing phase
of deployment they will leverage R5 as the Rendezvous Point in the Core Infrastructure.
Currently they are using the Loopback 900 interface on R5 as a statically assigned RP. The
plan is to transition to BSR in a later phase, but the team has encountered issues during testing.
You have been tasked to find the issue in the current deployment where the team is using R2
(loopback 900) to simulate a multicast listener for the test mcast address FF07::7. You have
been told to simulate the multicast flow coming from R7 located in MOB1 for testing.

Activity Procedure
Complete the following steps:
Step 1 Connect to the console of R7 and initiate a test ping to FF07::7 to see if
the issue still exists.

Step 2 Clearly the problem exists. There are many places that we can start
testing but my plan is to first validate the simulated host that wants to
listen to the multicast address FF07::7 on R2. The team said that
interface Loopback 900 to simulate the multicast listener by running the
command show run interface loopback 900.

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

 Step 3 The configuration of Multicast Listener Discovery (MLD) Protocol is used
to signal that this device wants to receive multicast packets for the
Multicast Group Specified. In this case the correct address of FF07::7. So
now we will want to see what the Rendezvous Point is for this group on
R2 specifically. We will use the show ipv6 pim group-map FF07::7
command.

Step 4 We see that for the entire multicast range FF00::/8 R2 is configured to
use R5 2001::5 as the RP, and we see that the configuration was done
statically. As another validation I want to make sure the address of
2001::5 is reachable from R2.

Step 5 The address is reachable. Now we want to see if there is an entry in the
multicast routing table for FF07::7. The expectation is that we will see a
“star” comma “G” entry. This will look like this (*,FF07::7) and can be seen
using the command show ipv6 mroute FF07::7.

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

 Step 6 The output shows clearly that the join for the group FF07::7 from any
multicast source is in the table. Based on the operation of the ipv6 PIM
we can call on our theoretical knowledge to predict how the multicast
routing tables should form. If the MLD Join originates on R2, we can
assume that the (*,FF07::7) entry will appear in all the multicast routing
tables of the devices between the Multicast Listener (R2) and the RP
(R5). This means that we should see the “star comma gee” entry on R2
(ML), R1, R3 and R5 (RP). We will quickly check the entire data path by
using the show ipv6 mroute command on all these devices. If we see the
route we will move to the next device in the list.

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

 Step 7 R5 does not have the (*,G) entry, which is a problem since it is the RP in
our topology. As an additional check we will want to see if R5 knows that
it is the RP for the FF07::7 multicast group. This will be done using the
show ipv6 pim group-map FF07::7 command.

Step 8 According to the output R5 has no idea of the identity of the RP much
less that it is the RP. We can correct this by applying the static rp
configuration using the ipv6 pim rp-address 2001::5 command.

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

 Step 9 Now we will repeat the show ipv6 mroute FF07::7 command.

Step 10 Now we see that the (*,G) entry for FF07::7 exists. As a final test we will
try to ping from R7 one more time.

Step 11 This has remediated this trouble ticket.

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide
Trouble Ticket #12:
PC2 Cannot Reach 2001:db9:199:199:199::199
In this trouble ticket, you will confirm that your PC2 has the necessary IPv6 configuration
information to establish connectivity to a server using the IPv6 Address
2001:db9:199:199:199::199 located in Labor and Delivery (simulated by a loopback address).

Additional Information: The Senior Engineering Team has specified that you are not allowed
to remove any configuration during the remediation of this trouble Ticket.

Activity Procedure
Complete the following steps:
Step 1 Connect to PC2 and open a command-prompt window. Verify that the PC
indeed cannot reach the ip address 2001:db9:199:199:199::199.

Step 2 Seeing that the IPv6 addresses specified are not reachable we have
verified that the ticket is correct (the “external server” located at
2001:db9:199:199:199::199 are not reachable). The next step will be to
verify what IPv6 addresses the device is configured to use to
communicate to R2. By using the ipconfig /all command.

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

 Step 3 This gives us a lot of localized information regarding the operation of this
workstation now and previous. But the key data relates to the fact that the
device is using a statically assigned ipv6 address of
2001:db9:2:1:xxxx:xxxx:xxxx and the gateway of last resort is FE80::2.
Use the ping FE80::2 command.
This ping should work provided R1 (the next hop device) is correctly
configured at the interface level.

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

 Step 4 The ping works. Now we will engage in what should be another revealing
diagnostic test by attempting to do a trace route to the destination IPv6
address of 2001:db9:199:199:199::199
Use the tracert 2001:db9:199:199:199::199 command.

Step 5 The trace-route fails with a Destination net unreachable, after it is

successfully sent to R2 via the Gateway address FE80::2. This indicates
that the best place to start would be at R2 the next logical hop from PC2
to R5 which would be the point of origin for this prefix. I will choose to
start with R2.
Step 6 Open a session to R2 and test to see if the IPv6 address
2001:db9:199:199:199::199 is reachable.
Use the ping 2001:db9:199:199:199::199 command.

Step 7 We can clearly see that R2 lacks reachability to this prefix. The next step
will be to see what routes R2 is learning from R1 via BGP. We will
accomplish this using the show bgp ipv6 unicast command.

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

 Step 8 Note that the route is not being learned via BGP from the peer
2001:db9:1313::3 (R3). This route cannot be added to the routing table if
it is not being learned. Just as a quick check we will want to determine if
the route is being advertised by R3 toward R2. We will do this using the
show bgp ipv6 unicast neighbor 2001:db9:1212::2 advertised-routes
command from the console of R3.

Step 9 Note that the route 2001:db9:199:199:199::/64 is being advertised but

also make note that the prefix is annotated with “?” code, which denotes
the route was originated using redistribution. More significantly the
AS_PATH attribute includes the Autonomous System Number 100. The
only device in the topology that exists on R2, this means based on the lab
infrastructure the prefix has a prepended ASN at its point of origination.
This being the case the prefix is being dropped by BGP as it arrives on

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

 R2 (basic BGP loop prevention). We can visualize the assumption using
the command debug bgp ipv6 unicast updates in command.

Step 10 To initiate a new update process, we will clear the bgp ipv6 neighbor
relationship to R3. We will do this using the clear bgp ipv6 unicast *.

Step 11 We see that the route 2001:db9:199:199:199::199 is being DENIED

because it contains AS 100 in its AS_PATH Attribute. The Senior
Engineering Team has specified that we cannot remove commands to
correct this ticket, so modifying the config on R3 is not a valid solution.
However, we can add configuration to R2 to allow that device to accept
an update containing its own ASN via the allowas-in keyword to the
neighbor statement toward R3 (2001:db9:1313::3). I will disable all
debugging to reduce console information.

Step 12 Now we will check to see if the route is being learned using the show
bgp ipv6 unicast command once more.

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide

 Step 13 The route now appears as expected. The final test will be to see if
reachability has been restored from the perspective of PC2.

Step 14 This remediates this ticket.

Discovery Lab 15 | © 2025 Cisco Systems, Inc. IP6FD Lab Guide