ccna 200 301 dumps free

ccna 200 301 dumps free.64 22:icmp_seq=l ttl=64 time=2.33 msbytesfrom 2001:db8:1111:3 64 22:icmp_seq=2 ttl=64 time=2.59 msbytesfrom 2001:db8:1111:3 64 22:icmp_seq=3 ttl=64 time=2.03 msbytesfrom 2001:db8:1111:3Master@PCl:~$-----2001:db8:1111:3:: 22 ping statistics ---------------------3 packetstransmitted, 3received, 0% packetloss, time 2003 ms rtt min/avg/max/ mdev =2.039/2.321/2.591/0.225 msVerifying IPv6 from the routerCisco routers support the ping and traceroute commands for IPv6. Both commands accept IPv4 or IPv6 addresses or host names, and they can also both be used as standard or extended commands.The extended ping and traceroute commands are powerful enough to allow users to test the reverse route of a LAN host while sitting at the router before CLI. We discussed IPv4 in detail in Chapter 4, "Troubleshooting IPv4 Selective Routing," in the section "Testing Reverse Routes with Extended ping," and the same concepts apply to IPv6. Here is a brief review of the extended IPv6 options of the router ping and traceroute commands that allow you to reverse test route the correct source subnet. As shown in Figure 16-12, an extended ping from R1 to a PC2 IPv6 address will test the forwarding route to PC2. However, if the extended ping uses R1's G0/0 interface as the source, then this command also tests for reverse routes to the IPv6 subnet in PC1.Example 16-5 shows an extended IPv6 ping from R1 to PC2, using Rl's G0/0 interface as the source of the packet. The second command shows a standard IPv6 traceroute from R1 to PC2o