[c-nsp] BGP routing table !!

Thu Jun 17 07:46:12 EDT 2010

Raheel,

I'm not sure about RSP720 models available ad hoc, but based on Sup720 the basic hardware only allows for 256k routes at most. Only having a -XL version allows for 1m of (v4) routes. 

Your output only shows 'PFC-3C mode' - which tells the current operational limit is 256k, but doesn't tell about maximum capacity possible in hardware.

If you do have a XL deployed (look for PFC-3CXL in 'sh mod') just follow the hint given in the error message: use 'mls cef maximum-routes' to increase the number of forwarding entries allowed in hardware.

Should you have got a non-XL and RSP720 being equal to Sup720 in regards to capacity (that's the 256k max) you'll need to swap RSP to handle a full BGP table.

Also pay attention to the combination of RSP and DFC's equipped. A XL-RSP will operate in non-XL-mode as soon as even a single non-XL-DFC is installed in the chassis.

regards,

Marcus

> -----Ursprüngliche Nachricht-----
> Von: cisco-nsp-bounces at puck.nether.net 
> [mailto:cisco-nsp-bounces at puck.nether.net] Im Auftrag von 
> Raheel Muhammad
> Gesendet: Donnerstag, 17. Juni 2010 13:18
> An: Phil Mayers
> Cc: cisco-nsp at puck.nether.net
> Betreff: Re: [c-nsp] BGP routing table !!
> 
> Hi,
> 
> Got the issue, but what would be the work around for this?  
> Mqaximum i am
> allowed is 223K.
> 
> 
> 12:44:10.257: %MLSCEF-SP-4-FIB_EXCEPTION_THRESHOLD: Hardware 
> CEF entry usage
> is at 95% capacity for MPLS protocol.
> 12:44:09.650: %MLSCEF-SP-STDBY-4-FIB_EXCEPTION_THRESHOLD: 
> Hardware CEF entry
> usage is at 95% capacity for MPLS protocol.
> 12:44:13.182: %CFIB-SP-STDBY-3-CFIB_EXCEPTION: FIB TCAM 
> exception for IPv4
> unicast. Packets through some routes will be dropped.
> Use "mls cef maximum-routes" to modify the FIB TCAM partition or/and
> consider a hardware upgred.
> Examine your network and collect the necessary information 
> from this setup.
> The only way to recover from this state is by reload the  router.
> 12:44:12.913: %CFIB-SP-3-CFIB_EXCEPTION: FIB TCAM exception for IPv4
> unicast. Packets through some routes will be dropped.
> Use "mls cef maximum-routes" to modify the FIB TCAM partition or/and
> consider a hardware upgred.
> Examine your network and collect the necessary information 
> from this setup.
> The only way to recover from this state is by reload the  router.
> 
> 
> 
> Regards,
> Raheel
> 
> 
> On Thu, Jun 17, 2010 at 1:51 PM, Raheel Muhammad
> <raheel.muhammad at gmail.com>wrote:
> 
> >
> > Hi,
> >
> > Cisco CISCO7606-S (M8500) processor (revision 1.0) with 
> 851968K/65536K
> > bytes of memory.
> > Processor board ID FOX1310G2VB
> >  BASEBOARD: RSP720
> >  CPU: MPC8548_E, Version: 2.0, (0x80390020)
> >  CORE: E500, Version: 2.0, (0x80210020)
> >  CPU:1200MHz, CCB:400MHz, DDR:200MHz,
> >  L1:    D-cache 32 kB enabled
> >         I-cache 32 kB enabled
> >
> > Last reset from s/w reset
> > 2 SIP-400 controllers (5 GigabitEthernet)(5 POS).
> > 1 Virtual Ethernet interface
> > 9 Gigabit Ethernet interfaces
> > 5 Packet over SONET interfaces
> > 3964K bytes of non-volatile configuration memory.
> > 507024K bytes of Internal ATA PCMCIA card (Sector size 512 bytes).
> > Configuration register is 0x2102
> >
> > #sh platform hardware pfc mode
> > PFC operating mode : PFC3C
> >
> > No i am not using AS path access-list, its just a straight forward
> > configuration with route-maps having prefix-lists in it.
> >
> > Regards,
> > Raheel
> >
> >
> >
> >
> > On Thu, Jun 17, 2010 at 1:36 PM, Phil Mayers 
> <p.mayers at imperial.ac.uk>wrote:
> >
> >> On 17/06/10 00:08, Raheel Muhammad wrote:
> >>
> >>> Hi guys,
> >>>
> >>> Might be a basic question but i couldnt find anything, i 
> have cisco 7606
> >>> i
> >>> just had a new peering with our upstream provider, but 
> router rebooted
> >>> when
> >>> routes reached 300k, router is not running anything else 
> as well. Any
> >>> idea?
> >>>
> >>
> >> That's pretty vague.
> >>
> >> Did the router log anything before rebooting? I assume you 
> have syslog
> >> setup? Did you have anything attached to the serial 
> console, and if so did
> >> it output anything?
> >>
> >> What does "sh ver" say with regards the last reload reason? e.g.
> >>
> >> ac-core#sh ver
> >> <snip>
> >>
> >> System returned to ROM by  power cycle at 07:01:04 BST Tue 
> Jun 8 2010 (SP
> >> by power on)
> >> System restarted at 07:12:11 BST Tue Jun 8 2010
> >> System image file is "..."
> >> Last reload reason: Reason unspecified
> >>
> >> Are there any crashinfo files? Try:
> >>
> >> dir bootflash:
> >> dir sup-bootflash:
> >>
> >> You say "routes reached 300k" - are you running XL PFC & 
> DFCs? What does:
> >>
> >> sh platform hardware pfc mode
> >>
> >> ...say?
> >>
> >> _______________________________________________
> >> 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/
> >>
> >
> >
> _______________________________________________
> 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/
> 