IPv6 Static Routes 1

certskills
By certskills April 26, 2016 10:15

Ever get tired of sifting through the details of seemingly random IPv6 addresses? Well, today’s lab gives you yet another quick config exercise while using very easy-to-remember IPv6 addresses and prefixes. The task today: configuring static IPv6 routes. All the IPv6 addresses and subnets are purposefully short (when abbreviated). Enjoy!

Requirements

The network shown in the figure uses IPv6. However, it will not use a routing protocol at all. This lab begins with all the IPv6 addresses configured. Your job: add static IPv6 routes so that each device can ping each other. The specific rules for this lab are:

  • None of the routers use a dynamic routing protocol
  • Configure your static routes to use global unicast addresses as next-hop addresses, rather than link local addresses.
  • Assumptions:
    • All router interfaces shown in the lab are up, working
    • All routers and hosts have correct IPv6 addresses assigned
    • All routers have IPv6 routing enabled

 

Figure 1: Simple Hub and Spoke Topology

 

Initial Configuration

Examples 1, 2, 3 and 4 show the beginning configuration state of Core, Branch1, Branch2 and Branch3.

 

Example 1: Core Config

 

Example 2: Branch1 Config

 

Example 3: Branch2 Config

 

Example 4: Branch3 Config

 

Answer on Paper, or Maybe Test in Lab

Next, write your answer on paper. Or if you have some real gear, or other tools, configure the lab with those tools.

To test your solution if you happen to try it with VIRL or real gear, you can check by going to each of the PCs and attempt to ping the other PCs. If each of the static routes was configured correctly everyone should have connectivity to each other. You can also issue a traceroute6 command on each PC, referencing another PC’s address, to see the various next-hop IPv6 addresses.

 

Do this Lab with Cisco’s VIRL

You can do these labs on paper and still get a lot out of the lab. As an extra help, we have added files for the Virtual Internet Routing Lab (VIRL) software as well. The .VIRL file found here is a file that when used with VIRL will load a lab topology similar to this lab’s topology, with the initial configuration shown in the lab as well. This section lists any differences between the lab exercise and the .VIRL file’s topology and configuration.

Download this lab’s VIRL file!

All interfaces in topology match the lab figure.

Network Device Info:

The switch used in the lab is a Cisco IOS layer 2 switch. Note that if you happen to have a layer 3 switch, to use the initial configurations as shown in this lab, issue to no ip routing command on the switch. This command will disable the routing of IPv4 packets, making the layer 3 switch act only as a layer 2 switch.

Host device info:

This table lists host information pre-configured in VIRL, information that might not be required by the lab but may be useful to you.

Device IP Address User/password
PC1 2000::100 cisco/cisco
PC2 2001::100 cisco/cisco
PC3 2002::100 cisco/cisco

 

Handy Host Commands:

To see PC IP address: ifconfig eth1

Ping example: ping6 -c 4 2000::1

Trace example: traceroute6 2000::1

To connect to another node within the topology: telnet 2000::1

GRE Tunnel 1
Answers: GRE Tunnel 1
certskills
By certskills April 26, 2016 10:15
Write a comment

No Comments

No Comments Yet!

Let me tell You a sad story ! There are no comments yet, but You can be first one to comment this article.

Write a comment
View comments

Write a comment

Comment; Identify w/ Social Media or Email

Subscribe

Subscribe to our mailing list and get interesting stuff and updates to your email inbox.

Thank you for subscribing.

Something went wrong.

Search

Categories