jrhett at svcolo
Dec 12, 2006, 1:23 AM
Post #2 of 2
(607 views)
Permalink
|
You probably filled up the static buffers for local connections.
You'll have to fail over to your backup MSM to recover.
On Dec 12, 2006, at 1:10 AM, Jonathan Ruano wrote:
> Extreme users ;-),
>
> A blackdiamond 6800 is filling up the logs with 'no memory' errors,
> I'm
> trying to identify the cause of them.
>
> Other than that, the switch is behaving normally, except that we can't
> connect to it (we don't even get a connect at the tcp level), although
> it's pingable.
>
> The last thing we were trying to set up was vrrp, but this is disabled
> now and the msgs persist. Have you seen this before? I'm looking for
> corrective measures before resorting to restart the box.
>
> 12/12/2006 09:54:11.64 <Crit:SYST> sbmalloc(58,25). No memory.
> 12/12/2006 09:54:11.25 <Crit:SYST> last message repeated 50 additional
> times
> 12/12/2006 09:53:44.49 <Crit:SYST> sbmalloc(58,25). No memory.
> 12/12/2006 09:53:44.49 <Crit:SYST> last message repeated 50 additional
> times
>
> Extremeware Version 7.1.1 (Build 14)
>
>
> Jon Ruano (jonathan.ruano at interoute.com)
> Data Center Operations
> Interoute Geneva
>
>
> _______________________________________________
> extreme-nsp mailing list
> extreme-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/extreme-nsp
--
Jo Rhett
senior geek
Silicon Valley Colocation
|
