CCNP Tshoot Tickets

Lab Diagram:

 

 

Please Logon for more Real Exam Level Tickets.

Lab setup:

  1. Install GNS3
  2. Download IOS images from Cisco
  3. Download the Configs Below
  4. Load it as a Project

Free Tickets:

A troubleshooting ticket reports that PC1 can not ping the external server at 209.65.69.2

Ticket 1: Download the Config Files
Ticket 2: Download the Config Files
Ticket 3: Download the Config Files
Ticket 4: Download the Config Files
Ticket 5: Download the Config Files
Ticket 6: Download the Config Files
Ticket 7: Download the Config Files
Ticket 8: Download the Config Files
Ticket 9: Download the Config Files
Ticket 10: Download the Config Files
Ticket 11: Download the Config Files
Ticket 12: Download the Config Files
Ticket 13: Download the Config Files
Ticket 14: Download the Config Files
Ticket 15: Download the Config Files
Ticket 16: Download the Config Files
Ticket 17: Download the Config Files
Ticket 18: Download the Config Files
Ticket 19: Download the Config Files
Ticket 20: Download the Config Files

 

 

 

 

 

 

42 thoughts on “CCNP Tshoot Tickets”

  1. Ticket 1. You should remove the “Frame-relay interface-dlci 324″ command on the S1/0.322 sub-interface of R3 and replace it with “Frame-relay interface-dlci 322″. An you should replace the “Frame-relay interface-dlci 332 with “Frame-relay interface-dlci 324″ on the s1/0.324 sub-interface of R3.

    You can ping from PC1 to see where the problem lies. PC1 can ping the S1/0.223 sub-interface on R2 but cannot ping the S1/0.322 on R3 (note: Frame-relay is configured so that the path of a packet going from R2 to R5 is, R2>R3>R4>R5). Therefore the problem is most likely located on R2 and beyond. After you determine where the problem is you can begin to trouble shoot.

    The partial output from “show interface S1/0, S1/0.322, S1/0.324″ on R3 show that the interface is up and line protocol is up.

    R3#show int S1/0
    Serial1/0 is up, line protocol is up
    !
    !
    R3#show int s1/0.322
    Serial1/0.322 is up, line protocol is up
    !
    !
    R3#show int S1/0.324
    Serial1/0.324 is up, line protocol is up
    !
    !

    From this output, we can assume the problem is most likely on layer 3.

    R3
    !
    router eigrp 9
    redistribute ospf 1 metric 1 1 1 1 1
    network 172.17.1.17 0.0.0.0
    auto-summary
    !
    router ospf 1
    log-adjacency-changes
    redistribute eigrp 9 metric 100 metric-type 1 subnets
    network 172.17.1.14 0.0.0.0 area 0
    default-information originate always
    !

    However the ospf and eigrp configurations on R3 match with the Ospf/eigrp configurations on R2 and R4.

    R2
    !
    router ospf 1
    router-id 172.17.1.10
    log-adjacency-changes
    area 1 virtual-link 172.17.1.9
    network 172.17.1.10 0.0.0.0 area 1
    network 172.17.1.13 0.0.0.0 area 0
    !

    R4
    !
    router eigrp 9
    redistribute connected
    network 172.17.1.18 0.0.0.0
    network 172.17.1.21 0.0.0.0
    auto-summary
    !

    From this output we can confirm that the ospf and eigrp configurations are correct.

    Order the “show run” command on R3 and you will receive a partial output.

    interface Serial1/0.322 point-to-point
    ip address 172.17.1.14 255.255.255.252
    frame-relay interface-dlci 324
    !
    interface Serial1/0.324 point-to-point
    ip address 172.17.1.17 255.255.255.252
    frame-relay interface-dlci 322
    !

    From this output we see a mismatch in the sub-interfaces. To fix the problem, simply replac the frame-relay interface-dlci commands with corresponding dlci numbers.

    • Ticket 1. You should remove the “Frame-relay interface-dlci 324″ command on the S1/0.322 sub-interface of R3 and replace it with “Frame-relay interface-dlci 322″. An you should replace the “Frame-relay interface-dlci

      322* not 332

      with “Frame-relay interface-dlci 324″ on the s1/0.324 sub-interface of R3.

    • hi….Thank you very much for such great knowledge. still i hv not crtified any cisco exam.i m planning for same .plz guide me.and need your help everytime so plz plz share such type of data on my email id…once again thank you so much and love u.. tc

  3. Nevermind, my GNS3 will just messing up :) . I found the cause early on, but that didn’t fix it. Once I restarted the lab and changed the route it worked perfectly.

  4. Ticket 2. I Found found where the problem is. It’s either on R1 or R2, because i cannot ping R2 and on from R1 and i cant pint R1 and on from R2. Also all the interfaces are up. But i cant seem to find the problem… Some help?

  5. Hey guys,
    Have you got any idea about Ticket#3.
    I am not sure, but I have realized there is something wrong with eigrp hello interval. Any idea?
    Thanks a lot.
    Cheers

    • I found the issue for ticket#3 :)
      The issue is about nat configuration on R5.
      You have to change “ip nat inside” and “ip nat outside” for two interfaces “fastethernet 0/0 and serial 1/0″
      Cheers.

  8. ticket #8

    I take out the “area 1 stub” on R1 , it’s work

    And I take out the vitual link on all R1 andR2 , add “area 1 stub ” on R1 andR2 , it doesn’t work.

    Question—how do I config a stub as this situation in area 1

  9. I am unable to ping from pc1. On checking the switch config, nothing is configured on ASW1 or DSW1. Should the configuration be present or are we meant to configure it as part of troubleshooting. I have checked labs 1 – 5. However routers are all configured. Please help.

    • Open the .net file in notepad and see what is the path required

      Make sure you have the same paths for the folders like working , images , etc

      And also get the same iOS images and put them I’m the correct folders

      • Dear David,

        Thanks for support,
        Now my Labs Tickets are opening and working fine but i don’t have questions to perform the labs. I check in the folder there is no task to trouble shoot the labs ticket.

        Please help me, if you have a scenario to perform the lab tickets.

        Regards,
        Ashfaq

  13. Thanks for support,
    Now my Labs Tickets are opening and working fine but i don’t have questions to perform the labs. I check in the folder there is no task to trouble shoot the labs ticket.

    Please help me, if you have a scenario to perform the lab tickets.

    Regards,
    Ashfaq

  14. Dear,

    For Ticket no 3 i changed nat inside and outside on both interface but the R1 cannot ping 209.65.69.2.
    From R1 can ping 9.6.209.246 but not 9.6.209.241 and 209.65.69.2
    i add redistribute cammand in R5
    Router bgp 65001
    redistribute eigrp 9
    and
    Router eigrp 9
    redistribute bgp 65001 11111
    it was working fine. i can ping from pc1 to server 209.65.69.2
    Please advice it’s ok or not
    Regards,
    Ashfaq Ahmed

    Please advise.

      • Dear Taskie,
        I try first switch nat inside outside but can’t work. after redistribute it was working fine. Please advice is there required any redistribute route or not when on border router hanve BGP and Eigrp.

        can you give me idea about Ticket 9
        from PC i can ping R5 but not server
        i checked all but not successed.

        Regards,

  15. Dear,
    I read Mr. David comment.
    Now i can ping R5 in Ticket 9
    i just command in R3 default-information originate always
    after this it is working fine.

    Thanks Mr. David

  16. am doing the tickets and cant seem to see the problem with number 15
    Can ping R1 int ip address 172.17.1.1 but not the .9 address on the same router. Have checked ospf and is working fine. Also check the default route on the pc which is fine. Can asnyone point me in the right direction?

  17. DSW1#sh ip ospf nei

    Neighbor ID Pri State Dead Time Address Interface
    192.168.99.130 1 FULL/BDR 00:00:31 192.168.99.130 Vlan99
    172.17.1.9 1 FULL/BDR 00:00:36 172.17.1.1 FastEthernet1/0
    DSW1#sh ip route
    Codes: C – connected, S – static, R – RIP, M – mobile, B – BGP
    D – EIGRP, EX – EIGRP external, O – OSPF, IA – OSPF inter area
    N1 – OSPF NSSA external type 1, N2 – OSPF NSSA external type 2
    E1 – OSPF external type 1, E2 – OSPF external type 2
    i – IS-IS, su – IS-IS summary, L1 – IS-IS level-1, L2 – IS-IS level-2
    ia – IS-IS inter area, * – candidate default, U – per-user static route
    o – ODR, P – periodic downloaded static route

    Gateway of last resort is not set

    C 192.168.10.0/24 is directly connected, Vlan10
    172.17.0.0/30 is subnetted, 2 subnets
    O 172.17.1.4 [110/2] via 192.168.99.130, 00:11:53, Vlan99
    [110/2] via 172.17.1.1, 00:12:19, FastEthernet1/0
    C 172.17.1.0 is directly connected, FastEthernet1/0
    192.168.99.0/27 is subnetted, 1 subnets
    C 192.168.99.128 is directly connected, Vlan99
    C 192.168.20.0/24 is directly connected, Vlan20

  19. R1#sh ip ospf virtual-links
    Virtual Link OSPF_VL0 to router 172.17.1.10 is up
    Run as demand circuit
    DoNotAge LSA allowed.
    Transit area 1, via interface Ethernet1/0, Cost of using 10
    Transmit Delay is 1 sec, State POINT_TO_POINT,
    Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
    Hello due in 00:00:01
    Adjacency State FULL (Hello suppressed)
    Index 1/4, retransmission queue length 0, number of retransmission 0
    First 0×0(0)/0×0(0) Next 0×0(0)/0×0(0)
    Last retransmission scan length is 0, maximum is 0
    Last retransmission scan time is 0 msec, maximum is 0 msec

    R2#sh ip ospf virtual-links
    Virtual Link OSPF_VL0 to router 172.17.1.9 is up
    Run as demand circuit
    DoNotAge LSA allowed.
    Transit area 1, via interface FastEthernet0/0, Cost of using 1
    Transmit Delay is 1 sec, State POINT_TO_POINT,
    Timer intervals configured, Hello 10, Dead 40, Wait 40, Retransmit 5
    Hello due in 00:00:00
    Adjacency State FULL (Hello suppressed)
    Index 1/2, retransmission queue length 0, number of retransmission 0
    First 0×0(0)/0×0(0) Next 0×0(0)/0×0(0)
    Last retransmission scan length is 0, maximum is 0
    Last retransmission scan time is 0 msec, maximum is 0 msec

    DSW1#ping 172.17.2.9
    Type escape sequence to abort.
    Sending 5, 100-byte ICMP Echos to 172.17.2.9, timeout is 2 seconds:
    …..
    Success rate is 0 percent (0/5)
    DSW1#

Leave a Reply