CCNA 200-301 Chapter 3 IP Connectivity Lab 029 Configure & verify IPv6 Network & Host Route

Watch Full Demo on YouTube:

Lab Objective:

This lab builds on Lab 027, but instead of focusing on IPv4. We will learn how to configure and verify IPv6 network and host routes on Cisco routers. Specifically, you will:

– Configure static network routes to enable communication between different subnets.

– Configure static host routes to direct traffic to a specific host.

– Verify the configured routes using various Cisco IOS commands. – Understand and interpret the routing table to troubleshoot and ensure correct route configuration.

Lab Topology:

Equipment Required:

• 3x Cisco Router (e.g., Cisco ISR4331/K9)
• 3 x Cisco Switches (e.g., WS-C2960-24TT-L)
• 4 x Laptops with Ethernet Interface Card
• 2 x Servers with Ethernet interface
• Console Cable
• Ethernet Cable for connections between devices
• Computer with Terminal emulation software e.g. PuTTY

IPv6 Address Table:

A. IPv6 Address Table:

Device Name	Interface ID	IPv6 Address	Subnet-Mask
HQ_R1	Gig0/0/0	2024:2000:1000::1	126
HQ_R1	Gig0/1/0	2024:2023::1	126
HQ_R1	Gig0/1	2024:1000::10	64
HQ_R1	Gig0/0	2025:1000::10	64
Branch1_R1	Gig0/0/0	2024:2000:1000::2	126
Branch1_R1	Gig0/0/2	2024:2000::10	64

B. Hosts IP Address Table:

Device Name	Interface ID	IPv6 Address/Subnet-Mask	Default Gateway
PC1	Fa0	2024:2000::1/64	2024:2000::10
PC2	Fa0	2024:2000::2/64	2024:2000::10
PC3	Fa0	2024:1000::3/64	2024:1000::10
PC4	Fa0	2024:1000::4/64	2024:1000::10
Internal_Server1	Fa0	2025:1000::100	2025:1000::10
Internal_Server2	Fa0	2025:1000::101	2025:1000::10

List of Command Summary:

Command	Command Description
enable	enters privileged EXEC mode.
configure terminal	enters global configuration mode from privileged EXEC mode.
hostname [hostname]	assign a device name to router.
Ipv6 route [Destination prefix] [Destination prefix mask] [Forwarding router’s address]	is used on a Cisco router to manually configure a static route for IPv6 traffic. Here’s a brief explanation of each part: ipv6 route: This is the command used to create a static route for IPv6 traffic. [Destination prefix]: This specifies the IPv6 network or host address to which the traffic is destined. It could be a specific network (e.g., 2001:db8:1::) or a single host (e.g., 2001:db8:1::1). [Destination prefix mask]: This defines the network portion of the destination address, similar to a subnet mask in IPv4. For example, /64 specifies that the first 64 bits are the network portion. [Forwarding router’s address]: This is the IPv6 address of the next-hop router to which the traffic should be forwarded. The router uses this address to send the packet towards its final destination.
show ipv6 route [ipv6-prefix]	used on Cisco routers to display the routing table entries specific to a given IPv6 prefix. When you provide an IPv6 prefix as an argument, the router will filter the routing table and show only the routes that match the specified prefix. This command is useful for verifying the presence of a route to a specific IPv6 network or address and for troubleshooting routing issues related to that particular prefix. The output will include details such as the route source, administrative distance, metric, and the next-hop address or interface used to reach the destination.
show ipv6 route	is used on Cisco routers and Layer 3 switches to display the current IP routing table. Here’s what this command provides and its significance: 1. Routing Table: The main purpose of show ip route is to show the IP routing table maintained by the device. This table contains information about networks and subnets that the device knows about and how to reach them. It includes entries for directly connected networks, routes learned dynamically through routing protocols (such as OSPF or EIGRP), and static routes configured manually. 2. Routing Information: Each entry in the routing table typically includes: a. Destination network or subnet (e.g., 192.168.1.0/24) b. Next-hop IP address or exit interface to reach the destination c. Administrative distance (a metric used to determine the reliability of the route) d. Route type (e.g., connected, static, or learned via a routing protocol) e. Metric or cost associated with the route 3. Routing Decisions: The show ip route command helps network administrators troubleshoot connectivity issues and verify the routing paths configured on the device. By examining the routing table, administrators can determine how traffic will be forwarded based on destination IP addresses and make adjustments as needed. 4. Dynamic Updates: If routing protocols are enabled on the device, such as OSPF (Open Shortest Path First) or EIGRP (Enhanced Interior Gateway Routing Protocol), show ip route will display routes learned dynamically from neighboring routers participating in the same routing domain.
ip address [IPv6]/[Subnetmask]	used to assign a specific IPv6 address and subnet mask to a network interface on a device such as a router or Layer 3 switch. This configuration allows the interface to participate in the specified IP network, enabling it to communicate with other devices in that network and perform routing functions.
ipv6 unicast-routing	This command is essential for any Cisco router that needs to route IPv6 traffic between different networks. Without it, the router will only be able to process IPv6 packets locally, but not route them to other networks.
ipv6 enable	This command is applied to an interface and enables IPv6 processing on that interface. It allows the interface to communicate using IPv6 and perform basic IPv6 operations
show ipv6 interface brief	used on a Cisco router or switch to display a summary of the IPv6 configuration on all interfaces. This command provides a quick overview of each interface’s IPv6 status, including any IPv6 addresses assigned, and the status of the interface itself.
ipconfig /all	used in Windows operating systems to display detailed information about all network interfaces and their configurations.
no shutdown	enables an interface.
show running-config	save the running configuration to the startup-configuration file.
show running-config | section interface GigabitEthernet0/*	used to display the configuration details of a specific GigabitEthernet interface (interface GigabitEthernet0/) within the running configuration of a Cisco device. This command allows you to view the configuration settings related to the specified interface only, filtering out other configuration sections. It provides a focused view of the configuration parameters associated with the specified interface, including its IP address, VLAN membership, trunking settings, and any other relevant configuration details. The asterisk (*) is a wildcard character that matches any character or sequence of characters. In this context, it is used to match any subinterface under GigabitEthernet0.
show running-config | section interface FastEthernet0/1$	The “show running-config | section interface FastEthernet0/1$” command is similar to the previous one, but it focuses specifically on the FastEthernet0/1 interface. The “$” symbol at the end of the interface name indicates that the command will match only the interface that ends with “FastEthernet0/1”. This command is helpful when you want to view the configuration details of a specific FastEthernet interface without displaying configurations for other interfaces.
copy running-config startup-config	used to save the currently running configuration (stored in the RAM) to the startup configuration (stored in the NVRAM)
end	exit configuration mode.
exit	exits one level in the menu structure command.

Lab Task:

1. Ensure all interfaces connected to end devices are configured with the following:
   1. Appropriate VLAN
   2. Appropriate interface description
   3. Interface mode set to Access
2. Branch1_R1 basic configuration:
   1. Configure interface GigabitEthernet0/1 with the appropriate IPv6 address, interface description, and enable the interface. This link connects to the Branch1_SW1 switch.
   2. Configure interface GigabitEthernet0/0/0 with the appropriate IPv6 address, interface description, and enable the interface. This link connects to the HQ_R1 router.
   3. Enable IPv6 Unicast Routing on all routers
   4. Perform in-flight checks.
   5. Check local connectivity between PC1 and PC2 and the default gateway. Is the ping successful? If not, troubleshoot the problem.
3. HQ_R1 basic configuration:
   1. Configure interface GigabitEthernet0/0 with the appropriate IPv6 address, interface description, and enable the interface. This link connects to the HQ_SW2 switch.
   2. Configure interface GigabitEthernet0/1 with the appropriate IPv6 address, interface description, and enable the interface. This link connects to the HQ_SW1 switch.
   3. Configure interface GigabitEthernet0/0/0 with the appropriate IPv6 address, interface description, and enable the interface. This link connects to the Branch1_R1 router.
   4. Configure interface GigabitEthernet0/1/0 with the appropriate IPv6 address, interface description, and enable the interface. This link connects to the ISP router.
   5. Enable IPv6 Unicast Routing on all routers
   6. Perform in-flight checks.
   7. Ping Branch1_R1 from HQ_R1 using the 2024:2000::2 IP address. Is the ping successful?
   8. Ping the ISP IPv6 address from HQ_R1. Is the ping successful?
   9. Check local connectivity between PC3 and PC4 and the default gateway. Is the ping successful? If not, troubleshoot the problem.
4. On Branch1_R1, configure a static route for the network 2024:1000::/64.
5. On Branch1_R1, configure a host static route for the IP address 2025:1000::100/128.
6. Initiate a ping as follow:
   1. From PC1 to PC3
   2. From PC1 to Internal_Server1
   3. From PC1 to Internal_Server2
7. On HQ_R1, configure a static route for the network 2024:2000::/64.
8. Initiate a ping as follow:
   1. From PC1 to PC3
   2. From PC1 to Internal_Server1
   3. From PC1 to Internal_Server2
   4. Is the ping successful? Why?
9. On Branch1_R1, configure a host static route for the IP address 2025:1000::101/128.
10. Initiate a ping from PC1 to Internal_Server2. The ping should be successful.
11. On HQ_R1, configure a default route with the next-hop address set to the ISP IP address 2024:2023::2.
12. Display the routing table and examine the output.
13. To reach those servers from the internet, you need to configure additional host static routes on Branch1_R1. Issue the appropriate commands to configure only host static routes for those two external servers.
14. Initiate a ping from PC1, PC2, PC3, and PC4 to Server1 and Server2. If the pings are successful, save your configuration. If not, troubleshoot the issue and try again.

Lab Solution:

1- Ensure all interfaces connected to end devices are configured with the following:
a. Appropriate VLAN
b. Appropriate interface description
c. Interface mode set to Access

Issue this command to check all interfaces status:

To check VLAN assignment, you can issue this command “show vlan brief”

To check current config issue “show running-config”

To check interface layer 2 information, you can issue this command “show interface fa0/1 switchport”

To check that each interface is in the Forward state we can issue this command “show spanning-tree vlan 100”

Now that we configured PC3 and PC4 to be part of the same VLAN they should be able to ping each other:

You can repeat the same commands for the HQ_SW2 and Branch1_SW1 Switches

2- Branch1_R1 basic configuration:
a. Configure interface GigabitEthernet0/1 with the appropriate IPv6 address, interface description, and enable the interface. This link connects to the Branch1_SW1 switch.
b. Configure interface GigabitEthernet0/0/0 with the appropriate IPv6 address, interface description, and enable the interface. This link connects to the HQ_R1 router.
c. Enable IPv6 Unicast Routing on all routers

Branch1_R1:
Branch1_R1#configure terminal
Branch1_R1(config)#interface gigabitEthernet 0/1
Branch1_R1(config-if)#description “Link to Branch1_SW1”
Branch1_R1(config-if)#ipv6 enable
Branch1_R1(config-if)#ipv6 address 2024:2000::10/64
Branch1_R1(config-if)#no shut
Branch1_R1(config-if)#exit

Branch1_R1(config)#interface gigabitEthernet 0/0/0
Branch1_R1(config-if)#description “Link to HQ_R1”
Branch1_R1(config-if)#ipv6 enable
Branch1_R1(config-if)#ipv6 address 2024:2000:1000::2/126
Branch1_R1(config-if)#no shut
Branch1_R1(config-if)#exit

Branch1_R1(config)#ipv6 unicast-routing

d. Perform in-flight checks.

e. Check local connectivity between PC1 and PC2 and the default gateway. Is the ping successful? If not, troubleshoot the problem.

Yes, there is connectivity between PC1 and PC2 and the default gateway for IPv6:

3- HQ_R1 basic configuration:
a. Configure interface GigabitEthernet0/0 with the appropriate IPv6 address, interface description, and enable the interface. This link connects to the HQ_SW2 switch.
b. Configure interface GigabitEthernet0/1 with the appropriate IPv6 address, interface description, and enable the interface. This link connects to the HQ_SW1 switch.
c. Configure interface GigabitEthernet0/0/0 with the appropriate IPv6 address, interface description, and enable the interface. This link connects to the Branch1_R1 router.
d. Configure interface GigabitEthernet0/1/0 with the appropriate IPv6 address, interface description, and enable the interface. This link connects to the ISP router.
e. Enable IPv6 Unicast Routing on all routers

HQ_R1#confi
HQ_R1#configure ter
HQ_R1#configure terminal

HQ_R1(config)#interface gigabitEthernet 0/0
HQ_R1(config-if)#description “Link to HQ_SW2”
HQ_R1(config-if)#ipv6 enable
HQ_R1(config-if)#ipv6 address 2025:1000::10/64
HQ_R1(config-if)#no sh

HQ_R1(config-if)#inter gig 0/1
HQ_R1(config-if)#description “Link to HQ_SW1”
HQ_R1(config-if)#ipv6 enable
HQ_R1(config-if)#ipv6 address 2024:1000::10/64
HQ_R1(config-if)#no sh

HQ_R1(config)#interface gigabitEthernet 0/0/0
HQ_R1(config-if)#description “Link to Branch1_R1”
HQ_R1(config-if)#ipv6 enable
HQ_R1(config-if)#ipv6 address 2024:2000:1000::1/126
HQ_R1(config-if)#no sh

HQ_R1(config)#inter gig 0/1/0
HQ_R1(config-if)#description “Link to ISP”
HQ_R1(config-if)#ipv6 enable
HQ_R1(config-if)#ipv6 address 2024:2023::1/126
HQ_R1(config-if)#no sh
HQ_R1(config-if)#

HQ_R1(config)#ipv6 unicast-routing
HQ_R1(config)#

f. Perform in-flight checks.

g. Ping Branch1_R1 from HQ_R1 using the 2024:2000::2 IP address. Is the ping successful?
h. Ping the ISP IPv6 address from HQ_R1. Is the ping successful?

Yes, ping was successful:

i. Check local connectivity between PC3 and PC4 and the default gateway. Is the ping successful? If not, troubleshoot the problem.

Yes, there is local connectivity between PC3 and PC4 and the default gateway as well as internal server1 and server2.

4- On Branch1_R1, configure a static route for the network 2024:1000::/64.

Branch1_R1:
Branch1_R1#configure ter
Branch1_R1#configure terminal
Branch1_R1(config)#ipv6 route 2024:1000::/64 2024:2000:1000::1
Branch1_R1(config)#

5- On Branch1_R1, configure a host static route for the IP address 2025:1000::100/128.

Branch1_R1(config)#ipv6 route 2025:1000::100/128 2024:2000:1000::1
Branch1_R1(config)#

6- Initiate a ping as follow:
a. From PC1 to PC3
b. From PC1 to Internal_Server1
c. From PC1 to Internal_Server2
Is the ping successful? Why?

Test 6.A and 6.B have failed because HQ_R1 doesn’t have a route to return the packet to PC1.

If we issue the “show ipv6 route” command on HQ_R1, you will not be able to see PC1’s network listed. Therefore, HQ_R1 will not be able to forward the packet to Branch1_R1 and will drop the packet as a result.

Please note that when we tested the connectivity between PC1 and internal_server2 we received a reply “Destination host unreachable”, this is Brnach1_R1 doesn’t have a route to reach the network. In addition, HQ_R1 doesn’t have a route to return the traffic to 2024:2000::/64 network.

7- On HQ_R1, configure a static route for the network 2024:2000::/64.

HQ_R1(config)#ipv6 route 2024:2000::/64 2024:2000:1000::2
HQ_R1(config)#

8- Initiate a ping as follow:
a. From PC1 to PC3
b. From PC1 to Internal_Server1
c. From PC1 to Internal_Server2
Is the ping successful? Why?

Ping from PC1 to PC3 and Internet_Server1 was successful however the ping from PC1 to Internet_Server2 still failed due to the fact that Branch1_R1 doesn’t have a clue how to get to the server.

9- On Branch1_R1, configure a host static route for the IP address 2025:1000::101/128.

Branch1_R1(config)#ipv6 rout
Branch1_R1(config)#ipv6 route 2025:1000::101/128 2024:2000:1000::1
Branch1_R1(config)#end
Branch1_R1#

10- Initiate a ping from PC1 to Internal_Server2. The ping should be successful.

Yes, it is:

11- On HQ_R1, configure a default route with the next-hop address set to the ISP IP address 2024:2023::2.

HQ_R1(config)#ipv6 route ::/0 2024:2023::2

12- Display the routing table and examine the output.

13- To reach those servers from the internet, you need to configure additional host static routes on Branch1_R1. Issue the appropriate commands to configure only host static routes for those two external servers.

Branch1_R1:
Branch1_R1(config)#ipv6 route 2024:8000::1/128 2024:2000:1000::1
Branch1_R1(config)#ipv6 route 2024:9000::1/128 2024:2000:1000::1
Branch1_R1(config)#end
Branch1_R1#

14- Initiate a ping from PC1, PC2, PC3, and PC4 to Server1 and Server2. If the pings are successful, save your configuration. If not, troubleshoot the issue and try again.

Conclusion:

In this lab, you have successfully configured and verified IPv6 network and host routes on Cisco routers. You learned how to assign IP addresses to interfaces, create static routes, and verify them using various IOS commands. Understanding these concepts is essential for managing and troubleshooting network traffic effectively, ensuring that data is correctly routed between different networks and hosts. This foundational knowledge prepares you for more advanced routing protocols and configurations in your networking career.

Packet Tracer Lab (Pre/Post configuration):

Download the file below and open the word document to access the Packet Tracer labs.