Ccna routing and Switching Complete Study Guide

ping fe80::21a:6dff:fe37:a44e

 

---

Troubleshooting IPv6 Network Connectivity 

853

Pinging fe80:21a:6dff:fe37:a44e with 32 bytes of data:

Reply from fe80::21a:6dff:fe37:a44e: time<1ms

Reply from fe80::21a:6dff:fe37:a44e: time<1ms

Reply from fe80::21a:6dff:fe37:a44e: time<1ms

Reply from fe80::21a:6dff:fe37:a44e: time<1ms

Next, we’ll ping the global address on Fa0/0:

C:\Users\Todd Lammle>

ping 2001:db8:3c4d:3:21a:6dff:fe37:a44e

 

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

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

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

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

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

Okay—looks like PC1 is configured and working on the local LAN to the R1 router, so 

we’ve confirmed the Physical, Data Link, and Network layers between the PC1 and the R1 

router Fa0/0 interface.

Our next move is to check the local connection on Server1 to the R2 router to verify that 

LAN. First we’ll ping the link-local address of the router from Server1:

C:\Users\Server1>