Home > Ticket 3 – BGP Neighbor

Ticket 3 – BGP Neighbor

May 4th, 2018 in TSHOOT v2 Go to comments

Configuration of R1:
router bgp 65001
no synchronization
bgp log-neighbor-changes
network 209.65.200.224 mask 255.255.255.252
neighbor 209.56.200.226 remote-as 65002
no auto-summary

check bgp neighborship. **** show ip bgp sum****
The neighbor’s address in the neighbor command is wrong under router BGP. (use ipv4 Layer 3)

Answer: need change on router mode on R1 neighbor 209.65.200.226

Ans1) R1
Ans2) BGP
Ans3) delete the wrong neighbor statement and enter the correct neighbor address in the neighbor command (change “neighbor 209.56.200.226 remote-as 65002″ to “neighbor 209.65.200.226 remote-as 65002″)

Comments (30) Comments
Comment pages
1 3 4 5 6 7 11 32
  1. Tarek
    October 20th, 2013

    Hello @lcisoft and all, do we need to do manual config?

  2. hassan
    October 27th, 2013

    hello im not able to access the ccnp route link any idea????

  3. www.curiousitivity.com/node/2
    November 3rd, 2013
  4. Anonymous
    November 9th, 2013

    Can anybody confirm if all TTs are still valid

  5. Dhinu
    November 15th, 2013

    passed exam today (1000/1000)..
    credit goes to networktut

  6. Alicia
    November 19th, 2013

    Hi All, Just someone to clear something for me. How will I know if a specific question is related to ASW1, DSW1, R4, R2 or even R1? Or how will I know its Allowed Vlan ticket, Port Security ticket, NAT ACL tickets e.t.c. Thank you all.

  7. Ram
    November 21st, 2013

    Hello,
    I have a question, i gave my exam today and surprisingly all of the questions were just stating Client -1 cant ping .241 server. It was the same in 11 out of the 13 tickets. I am confused as to how do we check once the ticket is solved if we can ping the same or not. The configs on all the routers and switches are correct but in MCQs option is given, so for 11 instances of same Client1-cant ping webserver .241 how do we choose which issue will come ?

    Please help.

    Dhinu, can you please tell me how did u go about clearing your exam ?

    Thanks

  8. Dinu Uthaman
    November 22nd, 2013

    Hi Ram,

    Questions were same for all TT. You can only assume the issue and aswer the TT. As per my concern, Check the IP address of the client b4 you do trouleshooting the TT.

  9. Ram
    November 22nd, 2013

    Once if you fail in the exam, and you retake it, are the TTs still the same in the retake exam ?
    Can any one please suggest ?
    Thank you.

  10. Alicia
    November 26th, 2013

    Hello All, Will “Show run” be enough to figure out all issues in the exam? Yes I mean for all 13Tickets. You advise is appreciatede. I’m writing this Friday. Thank you all in advance.

  11. Abhishek Singh
    November 27th, 2013

    Guys i passed Tshoot exam today with 945 marks.
    All the tickets are same and exam is pretty easy to clear
    Thanks a lot to following:
    =================
    Networktut.com
    GNS Talk videos
    Khattak Strategy pdf
    Bulls Eye Strategy videos
    Tshoot Flow Chart by Naren pdf (https://www.dropbox.com/sh/e6tlz9ryb1lm3o9/npe8jf4SJx)
    The new Tshoot flow chart made things more simpler…

  12. Alicia
    November 29th, 2013

    PASSED today 29/11/2013 A BIG thank you to networktut.com and TSHOOT Strategy by Khattak Document.
    My approach to the exam:
    1. Commands I used for All tickets “Ipconfig”, “Ping” and “show run”
    2. First 15min of the exam “tutorial time” I wrote down all 13Tickets in a list format.
    3. I did IPCONFIG on “Client 1” to confirm if I have 169.x.x.x or 10.x.x.x IP for those tickets
    4. Once divided into two group “169.x and 10.x” I concentrated on the 169.x.x tickets first to identify the issues there “refer to this website”
    5. Then followed by IPv6 and HSRP tickets which are very easy to pick up from the “question line” OR you can actually mark this two tickets down before even doing the IPCONFIG to have 11Tickets to work from.
    6. Name all possible issues relating to each group “169.x and 10.x”
    7. When working with 10.x.x.x “Group” have in mind to PING 10.1.1.1 and PING 10.1.1.2
    8. Divide another group of tickets which you can Ping both 10.1.1.1 and 10.1.1.2
    9. Divide another 1 tickets which you can Ping 10.1.1.2 BUT NOT Ping 10.1.1.1
    10. My over message to everyone “group your tickets and you exam will be easy, easy, easy” keep in mind “Ipconfig”, “Ping” and “show run” that’s all you need, know what you’re looking for in a tickets when its VLAN Filter, Port Security, Switchport Trunk e.t.c
    All the best to everyone and another thing just forget about “IP Helper Address ticket” and “EIGRP Wrong AS No ticket” concentrate only on the 13Tickets.

    Regards

  13. Anonymous
    March 4th, 2014

    Base on the layer 2 and 3 diagrams. how do i get to the routers ( r1, r2, r3 r4) to view their configurations. do i use telnet command?

  14. Jim
    April 25th, 2014

    @Anonymous, no there are buttons on bottom in real exam with device names. you can click them to directly access the CLI.

  15. Eray
    May 20th, 2014

    There is a bug in this ticket.
    ‘sh ip bgp sum’ will not produce any output. In reality it would of course show the neighbor address (the one with the typo) in “active” (not established) state.
    So don’t let that confuse you. The answer here is right.

  16. Client 1 CLI
    May 24th, 2014

    Hey guys cleared tshoot exam today 5/24/2014 **All tickets still valid** There are strategies out there, this what I used.
    *************************************************************************

    1- Find 4 tickets for R1. ***OBS*** number in parentheses represent ticket’s order on Networktut.com
    -> If can ping 10.1.1.1 the tickets will be:
    – Nat ACL(4),BGP Neighbor (3) R1 ACL (5)
    -> if can’t ping 10.1.1.1 but can ping 10.1.1.2 ticket will be:
    – OSPF Authentication (1)

    2- find the 2 tickets for HSRP TRACK (2) DSW1 and IPV6 OSPF (12) R2

    3- find 4 tickets 3 for ASW1 and 1 for R4
    -> If client get ip 169.x.x.x or no IP address, tickets will be:
    -Switchport vlan 10 (8)
    -Port security (7) int 1/0/1 shutdown in **error disable** .
    -Switchport trunk (9) All in ASW1
    The other ticket will be in R4
    -DHCP Range (13)

    4- find one ticket where client get ip 10.x.x.x but can’t ping default gateway, ticket willl be:
    -Vlan filter (6) it will be DSW1 or ASW1 check for option port/acl

    5- 2 tickets where client get 10.x.x.x these two tickets will be:
    -OSPF to EIGRP (11) R4
    -EIGRP Passive Interface (14) R4

    I would advice to become premium member to interact with these tickets.

    Good lucky guys!!

  17. Danilo
    June 3rd, 2014

    I just passed my exam with 1000/1000
    I didn’t have drag and drop question by the way…
    All the ticket’s on Networkut are valid!!

    DWS1 – Vlan ACL/ Port ACL ( there is not BUG)
    no vlan filter test1 vlan-list 10 command.

  18. Rami2000
    June 7th, 2014

    Thanks networktut, I passed exam today. and all TTs are valid

  19. Michi
    August 14th, 2014

    14.8.2014 TT still valid

  20. CJ
    August 16th, 2014

    I PASSSSSSSSSSSSSED!!! Got a 986!! ALL PRAISES TO YAHWEH!!
    All TTs are still VALID! every single one IPs and all
    I DID get the eigrp passive interface ticket!!
    No wrong AS ticket
    1 dd (#2) wording a lil different as stated but same answer
    3 multiple choice- wording for FCAPS question and answers are different. “What are 3 levels of the FCAPS model?” Answ: config, fault, security, accounting, backup I didn’t choose config as 1 of the 3 so I got it wrong
    I would HIGHLY suggest getting premium membership! It’s so worth it. All you need is networktut and khattak strategy to pass. Super big thanks to you both. I’m officially CCNP whoop whoooooop!!!!!

  21. JA Spain
    August 29th, 2014

    Passed today 1000/1000. 3 Multichoice, 1 D&D and 13 labs. All from this site. This TT was the same one. Highly recomended become premium. TSHOOT_Strategy_by_Khattak, CBT Nuggets and this site is enought.

  22. abc123
    August 30th, 2014

    On PT ticket#3, somehow I can ping Web Server 209.65.200.241 from the client 1 but cannot ping from the DSW1. I can see the BGP neighbor IP was wrong but why client 1 can ping Web Server with the wrong BGP neighbor IP? Weird…

  23. Buddy
    August 30th, 2014

    @abc123:

    Well, I’ve checked your TT#3 problem out within PT 6.1:

    Thus pls study output from the following (relevant) Verification commands:

    R1#sh ip route bgp

    R1#

    (We have NO BGP Routes within R1 above!!! – Right!?) – and:

    R1#sh ip bgp
    BGP table version is 1, local router ID is 1.1.1.1
    Status codes: s suppressed, d damped, h history, * valid, > best, i – internal,
    r RIB-failure, S Stale
    Origin codes: i – IGP, e – EGP, ? – incomplete

    Network Next Hop Metric LocPrf Weight Path

    R1#

    (Again: NO eBGP routes has been advertised into R1 from the “NON exsisting” (.56) eBGP Neighbor! – Right!?)

    Thus we DON’t have any IPv4 Connectivity into div. Host ressources within indeed BGP AS 65002 from Client 1 or any other internal 65001 IPv4 Devices, as shown here:

    Packet Tracer PC Command Line 1.0

    PC>ping 209.65.200.241

    Pinging 209.65.200.241 with 32 bytes of data:

    Request timed out.
    Reply from 10.1.1.1: Destination host unreachable.
    Reply from 10.1.1.1: Destination host unreachable.
    Reply from 10.1.1.1: Destination host unreachable.

    Ping statistics for 209.65.200.241:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    PC>

    As you can see in output above, Client 1 AIN’t able to ping Web Server: 209.65.200.241 because of the TT#3 eBGP Routing Issue, and thus something indicates, that you’re probably using a “wrong” or “modified” PT Ticket Config, when trying to solve TT#3 within Packet Tracer – I gues!?

    Therefor pls CAREFULLY try Ticket#3 once more, to see if you can then make it work within PT 6.1!? – (TT#3 works just FINE within PT 6.1 here, as you can see within output above!!!)

    Thank You!

  24. Buddy
    September 3rd, 2014

    @abc123:
    Pls use indeed the provided (ORIGINAL) TT#3 .pkt configuration file, when testing TT#3 once more within PT 6.1!!!
    Thank you –
    /Buddy

  25. snooper
    September 4th, 2014

    TT3,

    I needed to redistribute ospf external routes into bgp, to allow ISP to ping client 1… I wonder if that is needed in the actual exam.

  26. Buddy
    September 4th, 2014

    @snooper:

    Nope, that’s probably not needed within the current TSHOOT exam – simply because:

    Within R1 – also external (10.2.x.x/16) ospf routes are being PAT’ed (w. “overload”) into: the “inside global” NAT IP addr: 209.65.200.225/30 – (=> the serial I/F on R1 pointing towards the ISP router).

    Following that – the router bgp 65001 process on R1 is configured with:

    network 209.65.200.224 mask 255.255.255.252 – (among others)

    which excactly redistributes indeed THIS Public (external) transit net (including the above Serial I/F addr.) into eBGP on R1, so eBGP connectivity then gets established between BGP AS: 65001 and 65002.

    Now Client 1 is allowed to ping ISP etc. and vice versa.

    Thus indeed “external” ospf (10.x) routes within R1 does NOT get directly redistributed into bgp on router R1, in order to allow ISP etc. to ping client 1 and vice versa @ the exam.

    Thank you!

  27. Buddy
    September 5th, 2014

    snooper:
    Sorry – just a small addition to the post above:
    Because of the NAT process within R1 – Internal 10.x.x.x Device adresses are “invisible” from the outside world, which means that IP communication with our ISP should be initiated from indeed the “inside” (e.g. Client 1 etc.) – It’s a Security issue!
    Within the unlikely case, that also our ISP should be able to initiate IP comm towards e.g. our Client 1 directly – Our ISP needs to have also specific IP routes within his local routing-table, pointing towards the wanted internal 10.x.x.x subnets within the topolgy – But this is a rather odd and unwanted situation for the actual “NAT’ed” TSHOOT Topolgy.

  28. abc123
    September 7th, 2014

    Thanks Buddy. I tried again and this time it worked properly.

  29. Buddy
    September 7th, 2014

    abc123: Sounds Great!!! – Isn’t just cool, that we can always count on Packet Tracer, when using him properly :-)

  30. GCM Blue
    September 10th, 2014

    Praise d Lord ! I’ve got 945/1000 score today Sep 10, 2014
    Thanks lot Networktut team …. very effective though some questions were confusing but be careful… I used PING & SH RUN commands to check config…. I applied strategy of Khatak & Naren … thanks lot too !
    >>Got 2 MCQ (debug ip packet … & ip tftp instead…); 1 DD & 13 TTs still valid here
    >>No EIGRP wrong AS
    >>No DHCP range
    >>With IP Helper (wrong address @DSW1)

    God bless NETWORKTUT !!!

Comment pages
1 3 4 5 6 7 11 32