[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cisco-nsp
Subject:    [nsp] RES: [nsp] RES: [nsp] BGP advertisement
From:       "Loureiro, Rodrigo" <rodrigo.loureiro () netstream ! com ! br>
Date:       2000-06-27 18:22:04
[Download RAW message or body]

Congratulations, you got the problem!

I run a "sh ip bgp filter-list" over the output filter-list that is in
production and it didn´t match the route. I rewrite the list using another
number and run the command again. This time it worked, i mean, it matched
the route. I didn´t change the list yet but i have no doubt it will work.


Thanks for all,
--

Rodrigo Loureiro
Netstream Telecom (AT&T)


-----Mensagem original-----
De: Martin, Christian [mailto:CMartin@mercury.balink.com]
Enviada em: Terça-feira, 27 de Junho de 2000 13:12
Para: 'Loureiro, Rodrigo'; 'Martin Cooper'
Cc: cisco-nsp@puck.nether.net
Assunto: RE: [nsp] RES: [nsp] BGP advertisement


Try rewriting your as-path list.  I have often seen corruption after
reloads, as if the reg-exp compiler added a space or something.  This is
quite a common occurence with Cisco's nowadays.  Create an access-list
against the network in question and run a 'deb ip bgp up <acl#>.'  You
should see a message indicating the cause.  Also, try and run a 'show ip bgp
filter <as-path-list#> to see if the reg-exp is written correctly.

chris

> -----Original Message-----
> From: Loureiro, Rodrigo [mailto:rodrigo.loureiro@netstream.com.br]
> Sent: Tuesday, June 27, 2000 10:23 AM
> To: 'Martin Cooper'; Loureiro, Rodrigo
> Cc: cisco-nsp@puck.nether.net
> Subject: [nsp] RES: [nsp] BGP advertisement
> 
> 
> It was already done.
> 
> -----Mensagem original-----
> De: Martin Cooper [mailto:mjc@cooper.org.uk]
> Enviada em: Terça-feira, 27 de Junho de 2000 11:25
> Para: Loureiro, Rodrigo
> Cc: cisco-nsp@puck.nether.net
> Assunto: Re: [nsp] BGP advertisement
> 
> 
> "Loureiro, Rodrigo" <rodrigo.loureiro@netstream.com.br> writes:
> 
> > I'm receiving a IBGP advertisement on my core router, but it's
> > not advertising the route to its EBGP peers, as were expected.
> > I checked the route with sh ip route it was OK. Then i checked
> > with sh ip bgp and the router returned that it was the best one,
> > but "Not advertised to any peer". 
> > 
> > Finally, I checked my output filter-list and the AS number
> > corresponding to the the advertisement was OK, i mean, it
> > should be matching and then advertising the route. I cleared
> > the EBGP peer but it didn't solve the problem. The only thing
> > i didn't do was to turn-off the output filter-list, because
> > it would be critical if we consider the number of routes that
> > will be advertised. 
> > 
> > Has anyone dealed with a common situation before? Any
> > suggestions?
> 
> router#conf t
> Enter configuration commands, one per line.  End with CNTL/Z.
> router(config)#router bgp <your_as>
> router(config-r)#no synchronization
> router(config-r)#^Z
> 
> M
> 

[prev in list] [next in list] [prev in thread] [next in thread]