Mailing List Archive: Cisco: NSP

automatic bgp route refresh

Index | Next | Previous | View Threaded

jmaimon at ttec

Feb 21, 2012, 7:08 AM

Post #1 of 7 (771 views)
Permalink

automatic bgp route refresh

Hey All,

I would greatly appreciate it if somebody would point me to the release
notes for the change I see in 15.1 where BGP neighbor route-map
configurations happen in real time, without needing any clearing, soft
or otherwise.

Much obliged.

Best,

Joe
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Vinny_Abello at Dell

Feb 21, 2012, 7:57 AM

Post #2 of 7 (736 views)
Permalink

Re: automatic bgp route refresh [In reply to]

I know this "feature" exists in 12.2(33)SXI4, but I believe it was more accurately classified as a bug and I *thought* it was fixed in a later release. I'd also like to hear if this is actually an intended change or just a regression. If intended, I'd like to know how to prevent this behavior as I don't want to trigger soft updates until I've finished modifying a route-map. It's very CPU intensive with a full table.

-Vinny

-----Original Message-----
From: cisco-nsp-bounces [at] puck [mailto:cisco-nsp-bounces [at] puck] On Behalf Of Joe Maimon
Sent: Tuesday, February 21, 2012 10:08 AM
To: cisco-nsp
Subject: [c-nsp] automatic bgp route refresh

Hey All,

I would greatly appreciate it if somebody would point me to the release
notes for the change I see in 15.1 where BGP neighbor route-map
configurations happen in real time, without needing any clearing, soft
or otherwise.

Much obliged.

Best,

Joe
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

sraymond at bluehost

Feb 21, 2012, 7:58 AM

Post #3 of 7 (723 views)
Permalink

Re: automatic bgp route refresh [In reply to]

On Feb 21, 2012, at 8:08 AM, Joe Maimon wrote:
> I would greatly appreciate it if somebody would point me to the release notes for the change I see in 15.1 where BGP neighbor route-map configurations happen in real time, without needing any clearing, soft or otherwise.

I see the same thing in 12.2(33)SRD4. I find it somewhat annoying when trying to make an extensive change when BGP starts to reconverge as you are still pasting in the new route map.

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

p.mayers at imperial

Feb 22, 2012, 1:11 AM

Post #4 of 7 (715 views)
Permalink

Re: automatic bgp route refresh [In reply to]

On 02/21/2012 03:57 PM, Vinny_Abello [at] Dell wrote:
> I know this "feature" exists in 12.2(33)SXI4, but I believe it was
> more accurately classified as a bug and I *thought* it was fixed in a
> later release. I'd also like to hear if this is actually an intended

That is my recollection as well.

> change or just a regression. If intended, I'd like to know how to
> prevent this behavior as I don't want to trigger soft updates until
> I've finished modifying a route-map. It's very CPU intensive with a
> full table.

Even more so, it can be disastrous, causing traffic blackholing, if
you're editing communities or attributes required to "make things go"
and need to do this in a multi-step way e.g.

route map blah 10
! There's no "no set community 1:2", thanks IOS
no set community
! oops a route refresh happens now I've sent all my routes
! with no community, and the community is necessary in this case

! a few seconds later...
set community 1:3
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

nick at foobar

Feb 22, 2012, 2:12 AM

Post #5 of 7 (710 views)
Permalink

Re: automatic bgp route refresh [In reply to]

On 22/02/2012 09:11, Phil Mayers wrote:
> Even more so, it can be disastrous, causing traffic blackholing, if you're
> editing communities or attributes required to "make things go" and need to
> do this in a multi-step way e.g.
>
> route map blah 10
> ! There's no "no set community 1:2", thanks IOS
> no set community
> ! oops a route refresh happens now I've sent all my routes
> ! with no community, and the community is necessary in this case
>
> ! a few seconds later...
> set community 1:3

sigh, yes. This is just one fine example among many of why atomic (or even
pseudo-atomic) edit / commit / revert is a necessary tool on routers.
"reload in 5" still sucks as a means of working around this.

Nick

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

avitkovsky at emea

Feb 22, 2012, 3:12 AM

Post #6 of 7 (743 views)
Permalink

Re: automatic bgp route refresh [In reply to]

Reminds me on old days when acls didn't have numbered lines
During the migrations we had to maintain production and temp acl and change the distribute statements to use temp acl before deleting the production acl and pasting an updated version of it than put the production one back in and update the temp acl
Nightmare and very error prone

adam
-----Original Message-----
From: cisco-nsp-bounces [at] puck [mailto:cisco-nsp-bounces [at] puck] On Behalf Of Nick Hilliard
Sent: Wednesday, February 22, 2012 11:12 AM
To: cisco-nsp [at] puck
Subject: Re: [c-nsp] automatic bgp route refresh

On 22/02/2012 09:11, Phil Mayers wrote:
> Even more so, it can be disastrous, causing traffic blackholing, if you're
> editing communities or attributes required to "make things go" and need to
> do this in a multi-step way e.g.
>
> route map blah 10
> ! There's no "no set community 1:2", thanks IOS
> no set community
> ! oops a route refresh happens now I've sent all my routes
> ! with no community, and the community is necessary in this case
>
> ! a few seconds later...
> set community 1:3

sigh, yes. This is just one fine example among many of why atomic (or even
pseudo-atomic) edit / commit / revert is a necessary tool on routers.
"reload in 5" still sucks as a means of working around this.

Nick

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

jmaimon at ttec

Jul 11, 2012, 7:56 AM

Post #7 of 7 (504 views)
Permalink

Re: automatic bgp route refresh [In reply to]

Joe Maimon wrote:
> Hey All,
>
> I would greatly appreciate it if somebody would point me to the release
> notes for the change I see in 15.1 where BGP neighbor route-map
> configurations happen in real time, without needing any clearing, soft
> or otherwise.
>
> Much obliged.
>
> Best,
>
> Joe

So I opened the TAC case, went through the repro multiple times,
documented it, webexed it, discussed it.

First I am told that there is an undocumented command to turn it off.

"
The feature we are talking about is route refresh capability

this is a bgp hidden command which will not negotiate this capability
and you will have to manually refresh routes after making any
configuration changes.

neighbor x.x.x.x dont-capability-negotiate enhanced-refresh
"

Which does not work.

Then I am told that all IOS have been updated to do this and that there
are no publicly available release notes for this change and if I want
any further help, I need to have my account manager convince them that I
am worthy.

Which seems to be the way they try to resolve all cases these days.

Cisco support has sunk to new levels. You end up paying them to
sadistically torture and tantalize you. Which I am not into.

I remember when they would actually file a bug when you found one (with
a mtrr +-2yrs).

Best,

Joe
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads