Placed

CCNP Trouble Tickets GNS3 Labs





So far most of the labs provided on this site have been geared to preparing you for the CCNP routing and switching exams. These exams certify you have a complete understanding of routing and switching technologies, although to be certified as a CCNP you still need to pass the Troubleshooting and Maintaining Cisco IP Networks exam. The exam will certify that the candidate has the knowledge and skills necessary to (1) plan and perform regular maintenance on complex enterprise routed and switched networks and (2) use technology-based practices and a systematic approach to perform network troubleshooting.

Learning Objectives:

  • Use a systematic approach to perform network troubleshooting.
  • Plan and perform regular maintenance on complex enterprise networks.
  • Read and understand trouble tickets.
  • Find and repair break-fix issues.
  • Find and repair performance issues.

The following trouble tickets are provided to help you study for the Troubleshooting and Maintaining Cisco IP Networks exams.

Note: NO change what-so-ever are needed on R6 and R10.

The IP scheme used is very simple, network of 10.1.{Rx-Ry).[x/y] except the NBMA cloud, where its 10.1.0.[X/Y]

Trouble Ticket 1:

R1 is not using the optimal path to reach the network 10.1.24.0 and 10.1.0.0. -If required, two IPs from the range 11.0.0.0/24 can be used. -No changes in BW and cost allowed.

Trouble Ticket 2:

IP sla is configured on R2 to monitor the reachability to 60.1.1.1.  There are packets drops as the track state is going up/down intermittently. Troubles shoot and rectify the problem.

Trouble Ticket 3:

R3 and R1 are receiving the external routes from R6 but the ping is failing.

Trouble Ticket 4:

R8, R4 are still unable to ping 6.6.6.6, No changes on R1 allowed.

Trouble Ticket 5:

R5 can’t reach external networks advertised by R10. (60.1.1.1)

Trouble Ticket 6:

(optional, in case you have made it right in one of the previous ones, for a check, please proceed) Just check if the following IPs are reachable from R3 and R4. To get the idea, the R2 should have two equal cost paths for the external networks advertised from R10. 70.1.1.1 70.1.2.1 70.1.3.1 70.1.4.1 70.1.5.1 60.1.1.1 6.6.6.6

Download this lab now for full details:

  Trouble Tickets (154.7 KiB, 3,146 hits)


Bookmark and Share
You can leave a response, or trackback from your own site.

One Response to “CCNP Trouble Tickets GNS3 Labs”

  1. irom says:

    Ticket 2 : I don’t see ip sla configured on R2 . There is only track 1 for object 1
    R2#sh run | s track
    track 1 rtr 1

    nothing for object 1 ?

Leave a Reply

What is 4 + 10 ?
Please leave these two fields as-is:
IMPORTANT! To be able to proceed, you need to solve the following simple math (so we know that you are a human) :-)

*

Powered by WordPress | Designed by: backlinks | Thanks to internet marketing, etiketten drucken and index backlink