CCNP TSHOOT 300-135 Ticket 011
Previous Next
Download Lab: GNS3 | EVE-NG |
Prerequisites:
Cisco IOSv (vios-adventerprisek9-m.vmdk.SPA.156-2.T)
Cisco IOSvL2 (vios_l2-adventerprisek9-m.03.2017.qcow2)
GNS3 AAA Server Download
Note:
Since prerequisite for these labs are Cisco VIRL images, Frame Relay Cloud in original topology from the Cisco will be replaced by IOSvL2 switch and configured appropriately to imitate sub-interfaces for the point-to-point links. Access to the Cloud not available. All interfaces on the Cloud are configured as 802.1q Trunk, permitting VLAN 12,23,34.
Objective:
Network technician tries to understand how the IPV6 traceroute the command operates, while at his laptop in VLAN 10, he traces to the public Web Server at 2026::B:2019. The result shows that the server is 7 hops away. He thinks that it was shorter another day while investigating this long path issue, he applies new configurations to some routers and ends up with broken connectivity, traceroute now stops at the first hop.
Topology:
Instruction:
Open terminal to the Client1 and verify if it has IPv6 Global address with "show" command, also you can use "ip auto" to obtain IPv6 address.
Use "trace" command to verify the path to Web Server.
Fix connectivity problem first then you can diagnose hops issue.
Validation:
Client1 has to able to ping 2026::B:2019 IPv6 address of the Web server.
The output of traceroute command from Client1 shows you less than 7 hops.
Download Lab: GNS3 | EVE-NG |
Prerequisites:
Cisco IOSv (vios-adventerprisek9-m.vmdk.SPA.156-2.T)
Cisco IOSvL2 (vios_l2-adventerprisek9-m.03.2017.qcow2)
GNS3 AAA Server Download
Note:
Since prerequisite for these labs are Cisco VIRL images, Frame Relay Cloud in original topology from the Cisco will be replaced by IOSvL2 switch and configured appropriately to imitate sub-interfaces for the point-to-point links. Access to the Cloud not available. All interfaces on the Cloud are configured as 802.1q Trunk, permitting VLAN 12,23,34.
Objective:
Network technician tries to understand how the IPV6 traceroute the command operates, while at his laptop in VLAN 10, he traces to the public Web Server at 2026::B:2019. The result shows that the server is 7 hops away. He thinks that it was shorter another day while investigating this long path issue, he applies new configurations to some routers and ends up with broken connectivity, traceroute now stops at the first hop.
Topology:
Instruction:
Open terminal to the Client1 and verify if it has IPv6 Global address with "show" command, also you can use "ip auto" to obtain IPv6 address.
Use "trace" command to verify the path to Web Server.
Fix connectivity problem first then you can diagnose hops issue.
Validation:
Client1 has to able to ping 2026::B:2019 IPv6 address of the Web server.
The output of traceroute command from Client1 shows you less than 7 hops.
Comments
Post a Comment