www.howtonetwork.org

CCNA & CCNP Certifcation Training

  • About
  • Contact
  • FAQ
  • Join
  • Home
  • CCNA
    • ICND1
    • ICND2
    • 101 CCNA LABS
  • CCNP
    • ROUTE
    • SWITCH
    • TSHOOT
    • 101 CCNP LABS
  • CompTIA
    • Security+
    • Network+
  • Design
    • CCDA
    • CCDP
You are here: Home / 101 CCNP LABS / CCNP Lab 087: Troubleshooting Lab

CCNP Lab 087: Troubleshooting Lab

Lab Objective:

The focus of this lab is to hone your trouble isolation and resolution skills. This lab will include Layer 2 and Layer 3 technologies which fall within the scope of the current CCNP curriculum.

Lab Topology:

The lab network topology is illustrated below:

department687

 

IMPORTANT NOTE

If you are using the www.howtonetwork.net racks, please download and paste the troubleshooting lab configurations. If you are using your own rack or lab, please modify this configuration to reflect the actual interface types, etc, that you have on your devices. Prior to beginning all labs, apply the pre-lab configuration for each individual device.

When completing these labs, it is important to resolve the trouble tickets in the order in which they are listed because they build on each other. For example, if you begin with Trouble Ticket # 3, you might not get the expected resolution or result if you have not completed Trouble Ticket # 1 and Trouble Ticket # 2. It is very important to follow the order listed.

 

Trouble Ticket # 1

You have received a problem report indicating that switch ALS2 is inaccessible and cannot be reached even from devices residing on the 172.16.1.0/24 subnet. Troubleshoot and resolve this issue. Verify your solution by pinging DLS2 from any device on the 172.16.1.0/24 subnet.

Trouble Ticket # 2

You have received a problem report indicating slow convergence on the switched network. A co-worker has recently implemented 802.1w to speed up convergence, but it appears that the change did not resolve this issue. Troubleshoot and resolve this issue.

Trouble Ticket # 3

You have received a problem report indicating that users connected to the 172.16.1.0/24 and the 150.1.1.0/24 subnets are unable to reach the 150.4.4.0/24 subnet. Troubleshoot and resolve this issue. You are allowed to use only ONE command on any two routers in the network. You are NOT allowed to use any static routes. Verify your solution by pinging between these subnets.

 

Trouble Ticket # 4

You have received a problem report indicating that users are unable to receive Multicast traffic being sent from R4s LAN subnet. The NOC has joined the LAN interface of this router to Multicast group 227.4.4.4 but you cannot ping it from any other router. Troubleshoot and resolve this issue. Test your solution by pinging this address from all other routers.

Prev

Next

About Us

This is a free bonus site for members of www.howtonetwork.com

Copyright

The content on this copyright Reality Press Ltd.
Copyright Reality Press Ltd.