Notable Replies

  1. question:

    why we need “R2#clear ip bgp 192.168.12.1 in” here to make R2 sent Route-refresh? it should send automatically if route-refresh is supported and negotiated, thanks

  2. 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

  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

Continue the discussion forum.networklessons.com

7 more replies!

Participants