IPv6 LAB 4 Troubleshooting-2 based on the Lab2
Previous Next
Download Lab: GNS3
Image requirements:
Download Lab: GNS3
Image requirements:
Cisco IOSv (vios-adventerprisek9-m.vmdk.SPA.156-2.T)
Introduction:
Now that you know the topology from IPv6 Lab2 General-prefix, its time to test your knowledge, bring all you've learned to this troubleshooting scenario, where users in the LANs off router Office-A interfaces unable to access resources in the ISP's datacenter.
Problem:
Users from all subnets attached to the router Office-A unable to perform their job-related tasks, it appears that PCs in every other LAN failed to communicate with the outside server located in the datacenter, PCs using IPv6 address of the server, which is 2001:DB8:2244:1111::1111. Troubleshoot this issue after all necessary conclusions have been drawn please fix the culprit.
Troubleshooting tasks:
1. Verify connectivity to the server at the datacenter from users' PCs.
2. Determine the cause of the problem.
3. Propose corrective actions.
3. Implement the solution.
4. Again verify connectivity to the server.
5. Successful ping to the server is the validation of your proper troubleshooting effort.
Topology:
Introduction:
Now that you know the topology from IPv6 Lab2 General-prefix, its time to test your knowledge, bring all you've learned to this troubleshooting scenario, where users in the LANs off router Office-A interfaces unable to access resources in the ISP's datacenter.
Problem:
Users from all subnets attached to the router Office-A unable to perform their job-related tasks, it appears that PCs in every other LAN failed to communicate with the outside server located in the datacenter, PCs using IPv6 address of the server, which is 2001:DB8:2244:1111::1111. Troubleshoot this issue after all necessary conclusions have been drawn please fix the culprit.
Troubleshooting tasks:
1. Verify connectivity to the server at the datacenter from users' PCs.
2. Determine the cause of the problem.
3. Propose corrective actions.
3. Implement the solution.
4. Again verify connectivity to the server.
5. Successful ping to the server is the validation of your proper troubleshooting effort.
Topology:
Comments
Post a Comment