Networking

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
  • Taking advantage of route-refresh

    4 answers - 658 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    Hello,
    we have traditionally used "neighbour x.y.z.w soft-reconfiguration inbound"
    for eBGP peers.
    Now I (eventually) realise that I might save some memory by using the route
    refresh capability.
    Questions are:
    1.will I actually save memory? is the "soft-reconfiguration
    inbound" command ignored if the router supports route-refresh?
    2.how do I check that the peer supports route refresh?
    3.how do I remove the "soft-reconfiguration inbound"command without
    breaking anything?
    Thanks in advance,
    Vincent
    cisco-nsp mailing list cisco-nsp (AT) puck (DOT) nether.net
    archive at
  • No.1 | | 802 bytes | |

    Vincent De Keyzer wrote:

    1.will I actually save memory? is the "soft-reconfiguration
    inbound" command ignored if the router supports route-refresh?

    Yes, you'll save memory. No, the command is not ignored if route
    refresh is supported.

    2.how do I check that the peer supports route refresh?

    edge1-ifmt#sh ip b n | i refresh
    Route refresh: advertised and received(new)
    Route refresh: advertised and received(new)
    edge1-ifmt#

    3.how do I remove the "soft-reconfiguration inbound"command without
    breaking anything?

    Just do it. You may need to reload to actually save the memory though -
    YMMV, but I had to reload to claim it back.

    pt

    cisco-nsp mailing list cisco-nsp (AT) puck (DOT) nether.net

    archive at
  • No.2 | | 847 bytes | |

    Vincent De Keyzer wrote:

    1. will I actually save memory? is the "soft-reconfiguration
    inbound" command ignored if the router supports route-refresh?

    Yes, you'll save memory. No, the command is not ignored if route
    refresh is supported.

    2. how do I check that the peer supports route refresh?

    edge1-ifmt#sh ip b n | i refresh
    Route refresh: advertised and received(new)
    Route refresh: advertised and received(new)
    edge1-ifmt#

    3. how do I remove the "soft-reconfiguration inbound"command without
    breaking anything?

    Just do it. You may need to reload to actually save the memory though -
    YMMV, but I had to reload to claim it back.

    pt

    You can also re-enable it at any time for a specific peer should you
    need to view what's in there before it hits your filters
  • No.3 | | 2191 bytes | |

    At 11:26 AM 5/9/2006, Brian Johnson wrote:
    --
    Message
    From: cisco-nsp-bounces (AT) puck (DOT) nether.net
    [mailto:cisco-nsp-bounces (AT) puck (DOT) nether.net] Behalf Pete Templin
    Sent: Tuesday, May 09, 2006 9:59 AM
    To: Vincent De Keyzer; Cisco Nsp
    Subject: Re: [c-nsp] Taking advantage of route-refresh

    Vincent De Keyzer wrote:

    1. will I actually save memory? is the "soft-reconfiguration
    inbound" command ignored if the router supports route-refresh?

    Yes, you'll save memory. No, the command is not ignored if route
    refresh is supported.

    2. how do I check that the peer supports route refresh?

    edge1-ifmt#sh ip b n | i refresh
    Route refresh: advertised and received(new)
    Route refresh: advertised and received(new)
    edge1-ifmt#

    3. how do I remove the "soft-reconfiguration
    inbound"command without
    breaking anything?

    Just do it. You may need to reload to actually save the
    memory though -
    YMMV, but I had to reload to claim it back.
    >
    >Mine indicate
    >

    Route refresh: advertised and received(old & new)
    >
    >for all of my neighbors, but I have the "soft-reconfiguration inbound"
    >configured on all of these neighbors.
    >
    >If I remove that configuration, what configuration lines do I need to add to
    >use the route refresh option? Is it automatic?


    It's automatic. To use it:

    clear ip bgp nei x.x.x.x in

    or

    clear ip bgp nei x.x.x.x out

    Those commands will tear down the BGP session if route refresh is
    supported between the peers.

    Vinny Abello
    Network Engineer
    Server Management
    vinny (AT) tellurian (DOT) com
    (973)300-9211 x 125
    (973)940-6125 (Direct)
    PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0 E935 5325 FBCB 0100 977A

    Tellurian Networks - The Ultimate Internet Connection
    http://www.tellurian.com (888)TELLURIAN

    "Courage is resistance to fear, mastery of fear - not absence of
    fear" -- Mark Twain

    cisco-nsp mailing list cisco-nsp (AT) puck (DOT) nether.net

    archive at
  • No.4 | | 2488 bytes | |

    At 12:38 PM 5/9/2006, Vinny Abello wrote:
    >At 11:26 AM 5/9/2006, Brian Johnson wrote:
    >
    >

    Message
    From: cisco-nsp-bounces (AT) puck (DOT) nether.net
    [mailto:cisco-nsp-bounces (AT) puck (DOT) nether.net] Behalf Pete Templin
    Sent: Tuesday, May 09, 2006 9:59 AM
    To: Vincent De Keyzer; Cisco Nsp
    Subject: Re: [c-nsp] Taking advantage of route-refresh

    Vincent De Keyzer wrote:

    1. will I actually save memory? is the "soft-reconfiguration
    inbound" command ignored if the router supports route-refresh?

    Yes, you'll save memory. No, the command is not ignored if route
    refresh is supported.

    2. how do I check that the peer supports route refresh?

    edge1-ifmt#sh ip b n | i refresh
    Route refresh: advertised and received(new)
    Route refresh: advertised and received(new)
    edge1-ifmt#

    3. how do I remove the "soft-reconfiguration
    inbound"command without
    breaking anything?

    Just do it. You may need to reload to actually save the
    memory though -
    YMMV, but I had to reload to claim it back.
    >
    >Mine indicate
    >

    Route refresh: advertised and received(old & new)
    >
    >for all of my neighbors, but I have the "soft-reconfiguration inbound"
    >configured on all of these neighbors.
    >
    >If I remove that configuration, what configuration lines do I need to add to
    >use the route refresh option? Is it automatic?
    >
    >It's automatic. To use it:
    >
    >clear ip bgp nei x.x.x.x in
    >
    >or
    >
    >clear ip bgp nei x.x.x.x out
    >
    >Those commands will tear down the BGP session if route refresh is
    >supported between the peers.


    Sorry typing too fast. I meant: Those commands will NT tear down
    the BGP session if route refresh is supported between the peers.
    Sorry for any confusion.

    Vinny Abello
    Network Engineer
    Server Management
    vinny (AT) tellurian (DOT) com
    (973)300-9211 x 125
    (973)940-6125 (Direct)
    PGP Key Fingerprint: 3BC5 9A48 FC78 03D3 82E0 E935 5325 FBCB 0100 977A

    Tellurian Networks - The Ultimate Internet Connection
    http://www.tellurian.com (888)TELLURIAN

    "Courage is resistance to fear, mastery of fear - not absence of
    fear" -- Mark Twain

    cisco-nsp mailing list cisco-nsp (AT) puck (DOT) nether.net

    archive at

Re: Taking advantage of route-refresh


max 4000 letters.
Your nickname that display:
In order to stop the spam: 7 + 6 =
QUESTION ON "Networking"

EMSDN.COM