Who said they've gone away?
Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
Processor 60AEB910 122767088 103214012 19553076 204112 673896
Fast 60ACB910 131072 43864 87208 87208 87180
mardigras uptime is 16 weeks, 2 days, 19 hours, 10 minutes
Cisco Internetwork Operating System Software
IOS (tm) GS Software (RSP-PV-M), Version 11.1(31)CC, EARLY DEPLOYMENT
RELEASE SOFTWARE (fc1)
V111_31_CC_THROTTLE_BRANCH Synced to mainline version: 11.1(31)CA
Deepak Jain
AiNET
On Fri, 2 Jun 2000, Matthew White wrote:
> Hi Dave-
>
> A few of the 11.1.xCC images had problems with memory fragmentation.
> It got pretty bad around 23 (couldn't go for much more than 4 or 5 days
> without running into MALLOC failures) and really didn't clear up until
> around 26.
>
> -mtw
>
> Dave Curado (davec@navipath.com) wrote:
> > We saw a signficant routing flap tonight, that resulted in some
> > of our ebgp speaking routers running out of memory.
> > On closer inspection, the routers all have enough memory
> > (128M, with 40M or so free) but the largest free contiguous
> > block is very small on routers that have been up for a year
> > or so. Has anyone seen this?
> >
> > I've always believed that cisco routers do not require a
> > "theraputic" reboot, but the data I'm looking at now suggests
> > otherwise. (I rebooted one of these routers that had run out
> > of memory, and it's largest contiguous block is much larger
> > now.)
> >
> > Here's one of the more unhealthy routers that ran out of memory:
> >
> > --------------------
> > 11.1.25cc
> > show mem
> > Head Total(b) Used(b) Free(b) Lowest(b) Largest(b)
> > Processor 60AD9EE0 122839328 82389772 40449556 145788 4194368
> > Fast 60AB9EE0 131072 115000 16072 16072 16028
> >
> > router uptime is 43 weeks, 17 hours, 46 minutes
> > --------------------
> >
> > Thanks,
> > davec
> >
>
> --
> :wq
>
>
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:13 EDT