[e-nsp] strange behaviour while deleting vlan

[Marcin Kuczera]

Marcin Kuczera wrote:
> hello,
> 
> anybody noticed any strange behaviour when you provide command delete 
> vlan xxx ??
> 
> Vlan in on ports where STP is active, that's all.
> 
> In some cases, connection with switch is interrupted for several (maybe 
> 30) seconds on all vlans. And on "blocked" STP ports I can see some 
> increased numer of broadcasts..
> 
> XOS 12.4 and 12.3.. similar behaviour, but not on all switches (x450)

and... happend this evening:
03/08/2011 18:23:47.65 <Noti:EPM.UnexpctRebootDtect> Booting after 
System Failure.
03/08/2011 18:23:46.36 <Noti:EPM.wd_warm_reset> Changing to watchdog 
warm reset mode
03/08/2011 18:17:30.82 <Crit:HAL.Sys.Critical> Switch low on Memory. OS 
KBytes total 255132 free 5072
03/08/2011 16:53:48.19 <Erro:Kern.Error> async queue is growing (488931)
03/08/2011 14:35:31.88 <Erro:Kern.Error> async queue is growing (289272)
03/08/2011 13:38:29.11 <Warn:STP.FDBFlush> Flushing FDB (Transitioned 
from 0 to 3, starting flush timer for 19)
03/08/2011 13:38:29.11 <Warn:STP.FDBFlush> Flushing FDB (Transitioned 
from 0 to 3, starting flush timer for 21)
03/08/2011 13:38:29.10 <Warn:STP.FDBFlush> Flushing FDB (Transitioned 
from 0 to 3, starting flush timer for 23)
03/08/2011 13:38:29.07 <Warn:STP.FDBFlush> Flushing FDB (Transitioned 
from 0 to 3, starting flush timer for 26)
03/08/2011 13:38:29.07 <Warn:STP.FDBFlush> Flushing FDB (Transitioned 
from 0 to 3, starting flush timer for 16)
03/08/2011 13:38:29.07 <Warn:STP.FDBFlush> Flushing FDB (Transitioned 
from 0 to 3, starting flush timer for 15)
03/08/2011 13:27:30.13 <Warn:STP.FDBFlush> Flushing FDB (Transitioned 
from 0 to 3, starting flush timer for 19)
03/08/2011 13:27:30.13 <Warn:STP.FDBFlush> Flushing FDB (Transitioned 
from 0 to 3, starting flush timer for 21)
03/08/2011 13:27:30.13 <Warn:STP.FDBFlush> Flushing FDB (Transitioned 
from 0 to 3, starting flush timer for 23)
03/08/2011 13:27:30.13 <Warn:STP.FDBFlush> Flushing FDB (Transitioned 
from 0 to 3, starting flush timer for 26)


ExtremeXOS version 12.4.1.7


Is there any method to get information about particular process that 
caused this memleak ?

btw, anyone knows magic debug command to get into unix shell ?

Regards,
Marcin