Lab: Introducing Global Unicast Addresses CIS 116 IPv6 Fundamentals Enter your answers to the questions in this lab using Canvas Quiz “Ch.5 Global Unicast Address + Lab”. Additional questions are included in the quiz. Step 1. Setup a. Log into NetLab: ccnp.bayict.cabrillo.edu b. Schedule IPv6 Pod 1: “no configs loaded (clean)” c. Configure each router with the following commands: Router> enable Router# conf t Router(config)# hostname <R1, R2 or R2> R1(config)# no ip domain-lookup R1(config)# line con 0 R1(config-line)# logging synchronous R1(config-line)# exec-timeout 0 0 R1(config-line)# exit Topology

IPv6 address schema

• Your ISP has given you the IPv6 global routing prefix 2001:db8:cab::/48 • R1 LAN has the subnet 2001:db8:cab:828::/64 • R3 LAN has the subnet 2001:db8:cab:829::/64 • The link between R1 and R2 has the subnet 2001:db8:cab:1000::/64 • The link between R2 and R3 has the subnet 2001:db8:cab:2000::/64

Step 2. Manual GUA Configuration on R1 and R3 a. Configure a GUA address on R1’s G0/0 interface using 2001:db8:cab:828::1/64 R1# config t R1(config)# interface g 0/0 R1(config-if)# ipv6 address 2001:db8:cab:828::1/64 R1(config-if)# no shutdown R1(config-if)# end b. Verify the GUA address assignment using the following commands:

• show ipv6 interface brief • show ipv6 interface <g0/0 and g01> • show running-config

c. Configure a GUA address on R1’s G0/1 interface using 2001:db8:cab:1000::1/64 R1(config)# interface g 0/1 R1(config-if)# ipv6 address 2001:db8:cab:1000::1/64 R1(config-if)# no shutdown R1(config-if)# end Question 1: What type of unicast address was automatically created on R1’s G0/0 interface when the GUA address was configured? Question 2: What method did IOS use to create the address referred to in question 1? Question 3: Does R1 have the same link-local address on both of its interfaces?

Question 4: Could we configure R1 to have the same link-local address both of its interfaces? d. Configure R3 G0/0 interface to have the GUA address: ipv6 address 2001:db8:cab:829::1/64 e. Configure R3 G0/1 interface to have the GUA address: ipv6 address 2001:db8:cab:2000::1/64 f. Verify the GUA address assignment using the following commands:

• show ipv6 interface brief • show ipv6 interface <g0/0 and g01> • show running-config

Step 3. Manual GUA Configuration on R2 using EUI-64 Option In this section you will configure R2’s GUA addresses using the EUI-64 option. a. Configure R2’s G0/1 and G0/0 interface using the EUI-64 option: R2(config)# inter g 0/1 R2(config-if)# ipv6 address 2001:db8:cab:1000::/64 ? anycast Configure as an anycast eui-64 Use eui-64 interface identifier <cr> R2(config-if)# ipv6 address 2001:db8:cab:1000::/64 eui-64 R2(config-if)# no shutdown R2(config-if)# exit R2(config)# inter g 0/0 R2(config-if)# ipv6 address 2001:db8:cab:2000::/64 eui-64 R2(config-if)# no shutdown R2(config-if)# end Question 5: Why is <cr> (carriage return or the enter key) an option? b. Verify the GUA addresses on R2 using the show ipv6 interface brief and show interface commands: R2# show ipv6 interface brief GigabitEthernet0/0 [up/up] FE80::662:73FF:FE5E:F960 2001:DB8:CAB:2000:662:73FF:FE5E:F960 GigabitEthernet0/1 [up/up]

FE80::662:73FF:FE5E:F961 2001:DB8:CAB:1000:662:73FF:FE5E:F961 R2# Notice that R2 used the Ethernet MAC address and EUI-64 to create its GUA addresses: R2# show interface g0/0 GigabitEthernet0/0 is up, line protocol is up Hardware is CN Gigabit Ethernet, address is 0462.735e.f960 (bia 0462.735e.f960) <output omitted for brevity> We can use a filter to output only those lines that include “Hardware” R2# show interface g0/1 | include Hardware Hardware is CN Gigabit Ethernet, address is 0462.735e.f961 (bia 0462.735e.f961) R2# Question 6: What part of the IPv6 GUA address suggests that this address was derived using EUI-64? Step 4. Configuring a GUA and Default Gateway Address on a Windows PC Note: The current NetLab configuration may show the incorrect VM. This is in the process of being corrected. a. Select Windows PC 1 b. Select: Start > Network > Network Sharing Center > Change Adapter Settings > Local Area Connection > Properties > Internet Protocol Version 6 > Properties c. Select “Use the following IPv6 address:” and enter:

• IPv6 address: 2001:db8:cab:828::100 • Subnet prefix length: 64 • Default gateway: 2001:db8:cab:828::1 • Select “OK” and “Close”

Note: The address of the default gateway is typically the link-local address of the local router. However, for now we will use the router’s GUA address. d. Verify your address configuration using the ipconfig command. Notice that the Windows PC has also created itself a link-local unicast address.

Start > type “cmd” in the search area > type ipconfig at the Windows command prompt e. Verify Windows IPv6 connectivity with the local router (R1) using the ping command: C> ping 2001:db8:cab:828::1

f. Verify IOS IPv6 connectivity with Windows PC using the ping command: R1# ping 2001:db8:cab:828::100 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:DB8:CAB:828::100, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms R1#

Step 5. Configuring a GUA and Default Gateway Address on a Linux PC a. Select Linux PC. Login as “administrator” using the password “Cabri11o”. b. Select the terminal icon (second from the top on the left)

Configure the GUA address using the following command: IPv6-Linux:~$ sudo ifconfig eth0 inet6 add 2001:db8:cab:829::222/64 Note: If prompted for a password use “Cabri11o” Configure the default gateway address using the following command: IPv6-Linux:~$ sudo route –A inet6 add default gw 2001:db8:cab:829::1

c. Verify the configuration using the ifconfig command and the default gateway using the ip -6 route show command:

IPv6-Linux:~$ ifconfig

IPv6-Linux:~$ ip -6 route show

d. Verify reachability to the default gateway using ping6. Linux and Unix (including Mac OS) using the ping6 command instead of ping for sending ICMPv6 Echo Requests.

IPv6-Linux:~$ ping6 –c 4 2001:db8:cab:829::1 Step 6: Providing End-to-End Reachability with IPv6 Static Routes Note: IPv6 static routes will be covered in more detail in a later lab. Currently, our devices, including routers and hosts, can reach other devices on their own network but not on another network. This is because we have not yet configured the routers to forward IPv6 packets to other networks.

a. Reconfigure R2’s GUA address with IPv6 address that are easier to remember and more recognizable. First we remove any GUA addresses using the no ipv6 address command. R2(config)# interface g0/1 R2(config-if)# no ipv6 address R2(config-if)# ipv6 address 2001:db8:cab:1000::2/64 R2(config-if)# exit R2(config)# interface g 0/0 R2(config-if)# no ipv6 address R2(config-if)# ipv6 address 2001:db8:cab:2000::2/64 R2(config-if)# end R2# show ipv6 inter brief GigabitEthernet0/0 [up/up] FE80::662:73FF:FE5E:F960 2001:DB8:CAB:2000::2 GigabitEthernet0/1 [up/up] FE80::662:73FF:FE5E:F961 2001:DB8:CAB:1000::2 R2# b. Verify connectivity on the same network: R2# ping 2001:db8:cab:1000::1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:DB8:CAB:1000::1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/8 ms R2# ping 2001:db8:cab:2000::1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:DB8:CAB:2000::1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms R2# R1# ping 2001:db8:cab:828::100 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:DB8:CAB:828::100, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms R1#

c. Verify no connectivity on another network: R1# ping 2001:db8:cab:829::1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:DB8:CAB:829::1, timeout is 2 seconds: % No valid route for destination Success rate is 0 percent (0/1) R1# Question 7: Why are the pings to remote networks failing? d. Configure a default IPv6 static routes on R1 and R3 to forward all packets not on a directly connected network to R2. The ipv6 unicast-routing command is required to forward IPv6 packets transiting the router. R1# conf t R1(config)# ipv6 unicast-routing R1(config)# ipv6 route ::/0 2001:db8:cab:1000::2 R1(config)# exit R3# conf t R3(config)# ipv6 unicast-routing R3(config)# ipv6 route ::/0 2001:db8:cab:2000::2 R3(config)# exit e. Configure two IPv6 static routes on R2. R2 will send packets to R1’s LAN via R1 and R3’s LAN via R3. Again, the ipv6 unicast-routing command is required to forward IPv6 packets transiting the router. R2# conf t R2(config)# ipv6 unicast-routing R2(config)# ipv6 route 2001:db8:cab:828::/64 2001:db8:cab:1000::1 R2(config)# ipv6 route 2001:db8:cab:829::/64 2001:db8:cab:2000::1 R2(config)# exit

f. Verify connectivity from R1’s G0/1 interface: R1# ping 2001:db8:cab:829::1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:DB8:CAB:829::1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms R1# g. Verify end-to-end reachability from R1’s G0/0 interface to R3’s G0/0 interface: R1# ping 2001:db8:cab:829::1 source g0/0 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 2001:DB8:CAB:829::1, timeout is 2 seconds: Packet sent with a source address of 2001:DB8:CAB:828::1 !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms R1# h. Verify end-to-end reachability using ping on Windows PC 1 and ping6 on Linux PC. C> ping 2001:db8:cab:829::222 IPv6-Linux:~$ ping6 –c 4 2001:db8:cab:828::100 Step 7. Another Look at ipconfig on Windows a. Select Windows PC 1 again and look at the output of the ipconfig command.

Question 8: What looks different from the output in the ipconfig used in Step 4? Notice there are additional GUA addresses in the output. (I just gave you the answer to the previous question.) When we configured the local router (R1) with the ipv6 unicast-routing command, the enabled R1 as an IPv6 router. Besides having the capability to forward IPv6 packets, R1 is now sending ICMPv6 Router Advertisement (RA) messages. The Windows PC 1 host is used the RA message to create another GUA address and a temporary GUA address. This will be discussed in great detail in a later chapter when we discuss SLAAC.