CCNP Route Lab 8-1 , Configuring OSPF for IPv6

CCNP Route Lab 8-1 , Configuring OSPF for IPv6

Topology

ccnp-route-lab-configuring-ospf-ipv6

Objectives

  • Configure a static IPv6 address on an interface.
  • Change the default link-local address on an interface.
  • Configure an EUI-64 IPv6 address on an interface.
  • Enable IPv6 routing and CEF.
  • Configure and verify single-area OSPFv3 operation.

Background
In this lab, you configure static IPv6 addresses and EUI-64 IPv6 addresses on interfaces. You then configure OSPFv3 to route between the IPv6 networks.

Note: This lab uses Cisco 1841 routers with Cisco IOS Release 12.4(24)T1 and the Advanced IP Services Image c1841 -advipservicesk9-mz.124-24.T1 .bin. The switch is a Cisco WS-C2960-24TT-L with the Cisco IOS image c2960-lanbasek9-mz.122-46.SE.bin. You can use other routers (such as a 2801 or 2811), switches (such as 2950), and Cisco IOS Software versions if they have comparable capabilities and features. Depending on the router or switch model and Cisco IOS Software version, the commands available and output produced might vary from what is shown in this lab.

Required Resources

  • 3 routers (Cisco 1841 with Cisco IOS Release 12.4(24)T1 Advanced IP Services or comparable)
  • 1 switch (Cisco 2960 with the Cisco IOS Release 12.2(46)SE C2960-LANBASEK9-M image or comparable)
  • Serial and Ethernet cables

Step 1: Prepare the routers for the lab.
Cable the network as shown in the topology diagram. Erase the startup configuration, and reload each router to clear the previous configurations.

Step 2: Configuring the hostname and loopback interfaces.
Configure the loopback interface on each router with both the IPv4 address and IPv6 address shown in the diagram. The IPv4 address is configured using the ip address address mask command. The IPv6 address configuration is similar, using the ipv6 address address/mask command. With IPv6 addresses, you can enter
the mask length in bits with a decimal /mask, rather than entering the whole mask out in hexadecimal.

IPv6 addresses consist of eight groups of 16 bits (four hexadecimal characters) separated by colons. You can also enter the IPv6 address in an abbreviated form. For example, you can abbreviate any continuous group of zeros with two colons “::”. However, you can only use this abbreviation once per address. Also, leading zeros in each group can be omitted. For example, FEC0:0:0:0:0:0:12:1 /112 can be shortened to FEC0::12:1 /112.

If you accidentally enter the wrong IPv6 address on an interface, make sure you remove it with the no version of the command that you entered. Unlike IPv4 addresses, where the ip address command overwrites the existing address, multiple IPv6 addresses can exist on an interface. Issuing the ipv6 address command multiple times adds more addresses rather than replacing them.

Notice that both an IPv4 and an IPv6 address are on the same interface, and they do not conflict with each other. This is because they are different Layer 3 protocols, and they run independently.

Step 3: Configure static IPv6 addresses.
a. Configure the two serial links with IPv6 addresses. Use the ipv6 address address/mask command to configure the interfaces with the addresses shown in the diagram. Set the clock rates where appropriate, and bring up the interfaces.

b. Use ping to verify local subnet connectivity.

Step 4: Change the link-local address on an interface.
a. Use the show ipv6 interface command to look at IPv6-related properties of the router interfaces. You can also specify a type/number of an interface to see the output of that interface only.

Notice that in addition to the address that you already configured, there is a link-local address starting with FE80 (your actual address will vary). You can change the addresses on the link between R1 and R2 by putting the link-local address FE80::1 on R1 and FE80::2 on R2. Link-local addresses do not have a subnet mask because they are not routed, hence the term “link-local.”

b. To change the link-local address, use the ipv6 address address link-local command.

c. Verify that you can ping the link-local address on the other side. When pinging link-local addresses, you must specify an outgoing interface because the addresses are not routed and not in the routing table.

Note: When prompted for the output interface with this command, you must use the full interface name without spaces (for example, use serial0/0/0, not s0/0/0).

d. Verify the link-local addresses with the show ipv6 interface command.

Note: Manually modifying a link-local address is seldom needed. It is demonstrated here for the purpose of this lab.

Step 5: Configure EUI-64 addresses.
EUI-64 IPv6 addresses are addresses where the first 64 bits are the network portion of the address and are specified. The second 64 bits are the host portion of the address and are automatically generated by the device. RFC 4921 splits the 48-bit MAC address into two 24-bit segments: the Organizational Unique Identifier (OUI) and the NIC-specific component. The seventh bit of the OUI (bit 7 from the left) is inverted (changed from zero to one or vice versa). The 16-bit hex value 0xFFFE is then inserted between the modified OUI and the NIC-specific component to create the modified EUI-64 address. This can be seen in the highlighted EUI-64 address in Step 5b.

a. Configure IPv6 EUI-64 addresses on an interface using the ipv6 address address/mask eui-64 command. Configure the R2 and R3 Fast Ethernet interfaces with the subnet shown in the diagram, and enable the interfaces.

b. Get the IPv6 addresses of the interfaces with the show ipv6 interface or show ipv6 interface brief command, and then ping the other side of the link.

Note: Your addresses will be different from the addresses displayed in the example because EUI-64 addresses include the MAC address of the interface, which is unique per interface. At this point, you should have local subnet connectivity.

Note: Although not configured in this lab, the ipv6 general-prefix command can simplify the configuration of IPv6 addresses, including the EUI-64. You can use this command to assign a name to an often-used IPv6 prefix and then use the name to configure interfaces.

Step 6: Enable IPv6 routing and CEF.
The Cisco IOS version used with the routers in this lab has IPv6 routing and IPv6 CEF disabled by default. To enable IPv6 routing, use the ipv6 unicast-routing command in global configuration mode. To enable IPv6
EF, use the ipv6 cef command. Enter these commands on all three routers.

Step 7: Configure OSPFv3.
Unlike IPv4 OSPF, where networks are added to the OSPF process using network statements under the routing protocol configuration prompt, IPv6 OSPF uses the interface-level command ipv6 ospf process area area-id to add an interface to an area.

a. Add all interfaces shown in the diagram into OSPF process 1, area 0. After you add the interfaces to the OSPF process, the OSPF process starts automatically. If the adjacencies do not come up after a reasonable period of time, troubleshoot using the debug ipv6 ospf adjacency and debug ipv6 packet commands. Make sure that the packets are being sent to their destination and that adjacencies are forming correctly.

b. Verify that you have OSPFv3 neighbors with the show ipv6 ospf neighbor command.

The router IDs for each router are created the same way that they are in OSPFv2 or BGP. Without any IPv4 addresses on the router, the OSPFv3 process will not start unless you manually set the router IDs. This is why the loopback interfaces have been configured with both IPv4 and IPv6 addresses.

c. View the routing table on all three routers with the show ipv6 route command.

d. You can also look at per-interface OSPF behavior with the show ipv6 ospf interface command.

e. Run the following Tcl script on all routers to verify full connectivity. If these pings are not successful, troubleshoot. Modify the script to include the correct EUI addresses on the FEC0:23:: /64 subnet. The addresses for the router interfaces used in this lab are shown below.

Challenge: Summarize OSPFv3 Areas
The commands available for OSPFv3 are similar to the commands available for OSPFv2. On R2, add in two loopback interfaces, with the addresses FEC0:500::100:1 /112 and FEC0:500::200:1 /112. Add both of these
interfaces to the OSPF process in area 500. Summarize area 500 to FEC0:500:: /64. To enter the OSPF configuration prompt, use the ipv6 router ospf process-id command. Unlike the IPv4 (config-router) prompt, the IPv6 router prompt is (config-rtr). When in the IPv6 router prompt, use the area range command to summarize the address. Use the question mark (?) if you need help.

You would enter the following commands on R2:

Router Interface Summary Table

Router Interface Summary
Router Model Ethernet Interface
#1
Ethernet Interface
#2
Serial Interface
#1
Serial Interface
#2
1700 Fast Ethernet 0
(Fa0)
Fast Ethernet 1
(Fa1)
Serial 0 (S0) Serial 0/0/1
(S0/0/1)
1800 Fast Ethernet 0/0
(Fa0/0)
Fast Ethernet 0/1
(Fa0/1)
Serial 0/0/0
(S0/0/0)
Serial 0/0/1
(S0/0/1)
2600 Fast Ethernet 0/0
(Fa0/0)
Fast Ethernet 0/1
(Fa0/1)
Serial 0/0 (S0/0) Serial 0/1 (S0/1)
2800 Fast Ethernet 0/0
(Fa0/0)
Fast Ethernet 0/1
(Fa0/1)
Serial 0/0/0
(S0/0/0)
Serial 0/0/1
(S0/0/1)
Note: To find out how the router is configured, look at the interfaces to identify the type of router and how many interfaces the router has. Rather than list all combinations of configurations for each router class, this table includes identifiers for the possible combinations of Ethernet and serial interfaces in the device. The table does not include any other type of interface, even though a specific router might contain one. For example, for an ISDN BRI interface, the string in parenthesis is the legal abbreviation that can be used in Cisco IOS commands to represent the interface.

Device Configurations (Instructor version)

Router R1

Router R2

Router R3

More Resources

About the author

Scott

Leave a Comment