[c-nsp] 12008 GRPB memory problem.

[e ninja]

looking at the log messages, the mallocfails were reported by the RP and not
the linecards.

/eninja



On Mon, Mar 10, 2008 at 11:21 AM, Matt Liotta <mliotta at r337.com> wrote:

> You need to check each line card for memory using attach. Older GSRs
> had line cards with 128M, which will certainly not be enough with full
> tables.
>
> -Matt
>
> On Mar 10, 2008, at 2:00 PM, Troy Beisigl wrote:
>
> > Does anyone know why a 12008 with dual GRPBs with 256M each would
> > run out of
> > memory with a single full BGP feed? We have a 7507 RSP4 with 256M
> > and it
> > runs fine with about 50M free. The GSR runs out of memory and shuts
> > off dCEF
> > and stops functioning when connected in place if the 7507. We are
> > upgrading
> > the RAM in it to 512M, but this seems strange that we would be using
> > more
> > ram in one router than we would in the other.
> >
> >
> >
> >
> >
> >
> >
> > core2#sh ip bgp sum
> >
> > BGP router identifier 66.181.X.X, local AS number 21XXX
> >
> > BGP table version is 231585, main routing table version 231362
> >
> >
> >
> > Mar  8 08:19:04: %SYS-2-MALLOCFAIL: Memory allocation of 65536 bytes
> > failed
> > from 0x502658E8, alignment 16
> >
> > Pool: Processor  Free: 37664  Cause: Not enough free memory
> >
> > Alternate Pool: None  Free: 0  Cause: No Alternate pool
> >
> >
> >
> > -Process= "BGP Router", ipl= 0, pid= 163
> >
> > -Traceback= 5026AB04 5026CF08 502658F0 500E3FD0 501111D8 5011C0F4
> > 50126CCC
> > 5014F6B4 505FD664 505C95D4 505CC42C 508A4630 508A4D84 508A5B0C
> > 50F8DDB0
> > 508A5BD83119 network entries using 352447 bytes of memory
> >
> > 3119 path entries using 162188 bytes of memory
> >
> > 55062/0 BGP path/bestpath attribute entries using 7268184 bytes of
> > memory
> >
> > 35785 BGP AS-PATH entries using 945782 bytes of memory
> >
> > 4 BGP community entries using 96 bytes of memory
> >
> > 696 BGP route-map cache entries using 22272 bytes of memory
> >
> > 0 BGP filter-list cache entries using 0 bytes of memory
> >
> > BGP using 8750969 total bytes of memory
> >
> > BGP activity 231366/231361 prefixes, 231365/231361 paths, scan
> > interval 60
> > secs
> >
> >
> >
> > Neighbor        V    AS MsgRcvd MsgSent   TblVer  InQ OutQ Up/Down
> > State/PfxRcd
> >
> > 38.101.X.X  4   174   41164       8        0    0    0 00:00:28 Idle
> >
> > 38.104.X.X   4   174       9      10        0    1    0 00:00:28
> > Connect
> >
> > core2#
> >
> > Mar  8 08:19:08: %BGP-5-ADJCHANGE: neighbor 38.101.X.X Down No memory
> >
> > Mar  8 08:19:08: %BGP-5-ADJCHANGE: neighbor 38.104.X.X Down No memory
> >
> > Mar  8 08:19:40: %BGP-3-NOTIFICATION: sent to neighbor 38.101.X.X 3/1
> > (update malformed) 0 bytes  FFFF FFFF FFFF FFFF FFFF FFFF FFFF FFFF
> > 0052
> > 0200 0000 3440 0101 0040 0208 0203 00AE 1587 3120 4003 0426 65A1
> > A680 0404
> > 0000 DF0D 4006 00C0 0706 3120 C223 B71C C008 0800 AE52 0840 F703
> > E80E 59C0
> > 1557 ED10
> >
> > Mar  8 08:19:40: %BGP-5-ADJCHANGE: neighbor 38.104.X.X Up
> >
> > Mar  8 08:19:45: %BGP-5-ADJCHANGE: neighbor 38.101.X.X Up
> >
> > Mar  8 08:19:51: %FIB-2-FIBDOWN: CEF has been disabled due to a low
> > memory
> > condition.
> >
> > It can be re-enabled by configuring "ip cef [distributed]"
> >
> > Mar  8 08:20:25: %OSPF-5-ADJCHG: Process 21623, Nbr 66.X.X.X on
> > FastEthernet2/0 from FULL to DOWN, Neighbor Down: Dead timer expired
> >
> >
> >
> >
> >
> >
> >
> > Troy Beisigl
> >
> >
> >
> >
> >
> > _______________________________________________
> > 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 message has been scanned for viruses and
> > dangerous content by One Ring Networks, and is
> > believed to be clean.
> >
>
> _______________________________________________
> 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/
>