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 (12) Comments
Comment pages
1 5 6 7 32
  1. vti2003
    June 29th, 2018

    Hi @Boss,

    can I check with you are all the tickets at networktut coming out from the real exam?

  2. CCNP Boy
    August 3rd, 2018

    TIP

    Client 1 : can ping DSW1, R1
    cannot ping web server

    DSW1 : Traceroute to web server is not complete

    R1 : sh run and check the bgp config
    issue is with the wrong BGP IP

  3. a7med
    September 3rd, 2018

    hellllllllllllllllllo everyone

    plz help I need tshoot dumps

  4. Anonymous
    October 4th, 2018

    Went to R1 and pinged the server. show ip bgp summary checked ip address both sides. IP address wrong. Corrected bgp config, state established message and able to ping webserver. Ping from client worked. 2 mins.

  5. Anonymous
    January 20th, 2019

    Same answer applies to PT LAB.

  6. Marcus
    January 26th, 2019

    My remarks:
    Meaningless BGP commands on R1:
    network 209.65.200.224 mask 255.255.255.252
    no auto-summary

    We do not have own network to announce it to BGP peer. Besides, the network above already presents on BGP peer as “connected” network.

  7. routerninja
    February 5th, 2019

    Guys I had this question on an exam last week and failed unfortunately. I was able to trace/ping all the way to 209.65.200.226 but when I checked bgp neighbors the neighbor was 209.65.200.226, it through me off because everything worked except I could not ping the Web server. I also checked the access-list on R1 and they were good. Allowing 10.1.0.0 0.0.255.255 and 10.2.0.0 255.255.0.0. Any advice will be helpful.

  8. narna
    February 6th, 2019

    801 smh today

  9. Dany1
    February 18th, 2019

    For routerninja:

    1. Output to show ip bgp summary is showing time till BGP TCP is established or is Idle?

    2. If output is ok, what about show ip route bgp on R1?It show
    B 209.65.200.240/29 [20/0] via 209.65.200.226 ?

    3. If it is not shown that, you check show ip bgp?
    You see ” *> ” like below?
    Network Next Hop Metric LocPrf Weight Path
    *> 209.65.200.240/29
    209.65.200.226 0 0 65002 i

  10. Anonymous
    March 7th, 2019

    For routerninja:
    I also checked the access-list on R1 and they were good. Allowing 10.1.0.0 0.0.255.255 and 10.2.0.0 255.255.0.0.
    Dude the access list 10.2.0.0 0.0.255.255 didnt allow 10.2.1.0/24 network in answer was access-list technology and fix was to config access-list 1 permit 10.2.1.0 0.0.0.255

  11. Anonymous
    March 7th, 2019

    wait scrap that last tweet my fault
    danny is right for the BGP tix u will get Output to show ip bgp summary is showing Idle thats the clue, but u probably didnt notice that but when you checked bgp neighbors the neighbor was 209.56.200.226 NOT 209.65.200.226 easy to overlook
    R1
    # router BGP 65001
    # neighbor 209.65.200.226 remote-AS 65002

  12. Anonymous
    March 22nd, 2019

    Guys these dumps still alive for 2019 ?!!
    plz answer me

    Thnaks

Comment pages
1 5 6 7 32