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?
TIA
- Brian J
cisco-nsp mailing list cisco-nsp (AT) puck (DOT) nether.net
archive at

Brian Johnson wrote:

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.

May be an IS version difference or something. I have soft-in enabled
on two EBGP peers on that router, and see nothing different than my IBGP
neighbors who don't have soft-in.

If I remove that configuration, what configuration lines do I need to add to
use the route refresh option? Is it automatic?

It's ready to go; "clear ip b x.x.x.x in" works where it wouldn't if you
didn't have route-refresh capability from the neighbor.

pt

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

archive at