We're Sorry, Full Content Access is for Members Only...

If you like to keep on reading, Become a Member Now! Here is Why:

  • Learn any CCNA, CCNP and CCIE R&S Topic. Explained As Simple As Possible.
  • Try for Just $1. The Best Dollar You've Ever Spent on Your Cisco Career!
  • Full Access to our 618 Lessons. More Lessons Added Every Week!
  • Content created by Rene Molenaar (CCIE #41726)

 

390 New Members signed up the last 30 days!

satisfaction-guaranteed

100% Satisfaction Guaranteed!
You may cancel your monthly membership at any time.
No Questions Asked!


Forum Replies

  1. Hi Xin,

    Using the clear ip bgp in command is a nice way to manually request a route refresh from your neighbor.

    Once you do this, you can see it in the debug that R2 is requesting R1 for a refresh:

    R2#
    BGP: 192.168.12.1 sending REFRESH_REQ(5) for afi/safi: 1/1
    

    Rene

  2. Hi Rene,

    In summary …

    HARD RESET : It will tear down TCP session as well as BGP session.Establishing new BGP session, will send Route refresh request to neighbor and learn all prefix again also network interuption will occured.

    Soft Reconfiguration : Need More Memory due to store RAW Prefix in seperate table. No network interuption and will not send any Route refresh request.

    Route Refresh : This is the most suitable method.No network interuption , no extra memory needed.Just send a Route refresh request.

    Please correct me if I am wrong with my understanding .Thx

    br/zaman

  3. Hi NL Team,

    If using the route refresh option inbound, I assume any filters we have Inbound will be processed before routes are installed in the actual routing table? Is there any reason one would use soft reconfiguration over route refresh apart from it either being supported / not supported on the platform?
    Lastly, for route refresh to work do we need the peer router to be able to support this or only our own local router?
    Thanks :grin:

  4. Hello Robert,

    That’s right. When you receive a refreshed route, filters are applied and then it gets installed in the BGP table, and in the routing table.

    Today, there is no reason to use soft reconfiguration instead of route refresh. Soft reconfiguration was a bit of a workaround so you didn’t have to do a hard reset. Nowadays, all routers support route refresh so there’s no reason not to use it. Both peers need to support this.

    Rene

  5. Thanks Rene,

    Do we have a way of checking if the remote peer supports route refresh by any commands? Or would it be a case of having to ask the Provider of the peer link if their device supports route refresh?
    Thanks
    Robert

7 more replies! Ask a question or join the discussion by visiting our Community Forum