[c-nsp] BGP doesn't advertise prefixes

[Adam Vitkovsky]

Hi Samol,

Alright the config seems ok so I think now's the time to simplify things a bit.
Can you get a rid of all the config and just try to push that one prefix across to see if it works with just a simplest config possible?
Then try to build the config backwards by adding more and more elements to it to possibly see what the culprit is.
If possible try to reset the peer every time you add an element to make sure the prefix gets advertised even after a peer reset.  

adam
> -----Original Message-----
> From: cisco-nsp [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of
> Samol
> Sent: 30 April 2015 16:24
> To: Gert Doering
> Cc: cisco-nsp at puck.nether.net
> Subject: Re: [c-nsp] BGP doesn't advertise prefixes
> 
> Thanks Gert for the clues. I went thru rule again and below is the rules
> applied to our peer.
> 
>   neighbor EQUINIX-TRANSIT prefix-list BOGON in
>   neighbor EQUINIX-TRANSIT route-map EQUINIX-TRANSIT-IN in
>   neighbor EQUINIX-TRANSIT route-map *EQUINIX-TRANSIT-OUT* out
> 
> 
> rtr#sh route-map *EQUINIX-TRANSIT-OUT*
> route-map EQUINIX-TRANSIT-OUT, permit, sequence 5
>   Match clauses:
>     ip address prefix-lists: *CP-M21-PREPEND*
>   Set clauses:
>     as-path prepend 123 123 123
>   Policy routing matches: 0 packets, 0 bytes
> route-map EQUINIX-TRANSIT-OUT, permit, sequence 10
>   Match clauses:
>     community (community-list filter): 500
>   Set clauses:
>   Policy routing matches: 0 packets, 0 bytes
> 
> rtr#sh ip prefix-list *CP-M21-PREPEND*
> ip prefix-list CP-M21-PREPEND: 6 entries
>    seq 5 permit 123.0.73.0/24
>    seq 10 permit x.x.a.0/24
>    seq 15 permit x.x.b.0/24
>    seq 16 permit x.x.c.0/24
>    seq 20 permit x.x.d.0/24
>    seq 25 permit x.x.e.0/24
> 
> rtr#sh ip community-list 500
> Community (expanded) access list 500
>      permit *123:123*
> 
> rtr#sh ip bgp 123.0.73.0 | in Com
>       Community: *123:123* 65501:24115
> 
> 
> As per this rule, the route 123.0.73.0/24 ( sorry for the change of IP and
> hidden,but this would be preferred), should match with route-map seq 5
> with
> prefix-list seq 5 as well. We have no other rules attached to this peer in
> the outbound direction.
> 
> Regards,
> 
> 2015-04-30 21:56 GMT+07:00 Gert Doering <gert at greenie.muc.de>:
> 
> > Hi,
> >
> > On Thu, Apr 30, 2015 at 09:49:33PM +0700, Samol wrote:
> > > thanks for advice. I will double check. probably need the fresh eyes to
> > > look into it. but by using the command as below, could we say that the
> > rule
> > > is correctly matched?
> >
> > Yes, but it is not the only criteria - you could have a filter-list,
> > prefix-list or anything else on the peer that prevents announcement.
> >
> > gert
> > --
> > USENET is *not* the non-clickable part of WWW!
> >                                                            //
> > www.muc.de/~gert/
> > Gert Doering - Munich, Germany
> > gert at greenie.muc.de
> > fax: +49-89-35655025
> > gert at net.informatik.tu-muenchen.de
> >
> 
> 
> 
> --
> Samol Khoeurn
> (855) 077 55 64 02 / (855) 070 52 53 46
> Network Engineer
> Cisco: CCNA/CCNP SP/CCIP/
> Juniper: JNCIA/JTNOC/JNCIS-ENT,SP,SEC/JNCIP-ENT,SP
> Blog: http://thesaltedegg.net
> www.linkedin.com/in/samolkhoeurn
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
---------------------------------------------------------------------------------------
 This email has been scanned for email related threats and delivered safely by Mimecast.
 For more information please visit http://www.mimecast.com
---------------------------------------------------------------------------------------