Ccna routing and Switching Complete Study Guide

ping fe80::21a:6dff:fe64:9b2

 

Pinging fe80::21a:6dff:fe64:9b2  with 32 bytes of data:

Reply from fe80::21a:6dff:fe64:9b2: time<1ms

Reply from fe80::21a:6dff:fe64:9b2: time<1ms

Reply from fe80::21a:6dff:fe64:9b2: time<1ms

Reply from fe80::21a:6dff:fe64:9b2: time<1ms

And next, we’ll ping the global address of Fa0/0 on R2:

C:\Users\Server1>

ping 2001:db8:3c4d:1:21a:6dff:fe37:a443

 

Pinging 2001:db8:3c4d:1:21a:6dff:fe37:a443 with 32 bytes of data:

Reply from 2001:db8:3c4d:1:21a:6dff:fe37:a443: time<1ms

Reply from 2001:db8:3c4d:1:21a:6dff:fe37:a443: time<1ms

Reply from 2001:db8:3c4d:1:21a:6dff:fe37:a443: time<1ms

Reply from 2001:db8:3c4d:1:21a:6dff:fe37:a443: time<1ms

Let’s quickly summarize what we know at this point:

1.

  By using the 

ipconfig /all

 command on PC1 and Server1, I was able to document 

their global and link-local IPv6 addresses.

2.

  We know the IPv6 link-local addresses of each router interface.

3.

  We know the IPv6 global address of each router interface.

---

854

 

Chapter 20 

■

  Troubleshooting IP, IPv6, and VLANs

4.

  We can ping from PC1 to router R1’s Fa0/0 interface.

5.

  We can ping from Server1 to router R2’s Fa0/0 interface.

6.

  We can eliminate a local problem on both LANs.

From here, we’ll go to PC1 and see if we can route to Server1:

C:\Users\Todd Lammle>