[c-nsp] BGP Advertised Prefixes

Jason Lixfeld jason at lixfeld.ca
Tue Apr 9 16:21:15 EDT 2013


The message is pretty clear.  x.x.x.x is announcing more prefixes than what your max prefix setting is configured for.  Either the uplink side is misconfigured or your max prefix setting is too small.

On 2013-04-09, at 4:13 PM, Ahmed Hilmy <hilmy.aa at gmail.com> wrote:

> Dear Friends,
> 
> Recently i have faced a strange issue, BGP session with my UP Links goes
> down due this log at UP Link side:
> ---------------------------------------------------
> 
> RP/0/RSP0/CPU0:Apr  8 13:10:54.818 : bgp[1044]: %ROUTING-BGP-4-MAXPFXEXCEED
> : No. of IPv4 Unicast prefixes received from x.x.x.x: 401 exceed limit 400
> 
> RP/0/RSP0/CPU0:Apr  8 13:10:54.818 : bgp[1044]: %ROUTING-BGP-5-ADJCHANGE :
> neighbor x.x.x.x Down - Peer exceeding maximum prefix limit (CEASE
> notification sent - maximum n           umber of prefixes reached) (VRF:
> default)
> 
> 
> -------------------------------------------------------------
> 
> # sh bgp neighbor x.x.x.x detail | i Prefix advertised
> 
>  Prefix advertised 2735, suppressed 0, withdrawn 1855, maximum limit 524288
> #sh bgp neighbor  x.x.x.x advertised-routes
> 
> i count the number of advertised prefixes are only 215
> 
> So what Prefix advertised 2735 does it mean ?
> Why i faced this issue with my UP Links , it happened sometime , if i have
> configured BGP filter in wrong way so i have to face this
> issue continuously.
> 
> Any suggest plan to check ?
> _______________________________________________
> 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/




More information about the cisco-nsp mailing list