5255
IS-IT--Management
- Nov 4, 2007
- 4
- 0
- 0
Had a 3300 send a request for huge memory allocation it slowed and rebooted. Anyone else experience this?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
mxe 3300 failure
- Thread starter 5255
- Start date
- Status
TheMitelGuy
IS-IT--Management
Please of the number of active connection you have, I would highly recommend you call technical support on this one.
- Thread starter
- #3
TheMitelGuy
IS-IT--Management
What's your memory like? Have you modified your DIMs?
MitelInMyBlood
Technical User
In the telnet interface turn on debug then (if still supported) run
LLDCLI DSPOOL AUDIT
give the results to Prod Supp.
I'm pretty sure sastats and slopoke are gone, but donno about others. Is the LIST command structure still supported and would any of those help?
Maybe turn on the kernel monitor and then watch the SW logs for an hour or so during peak traffic hours.
KER CO(ontinuous)
KER STOP
I forget the interval the kernel reports are put in the SW log, every 15 mins or so seems I recall. Been awhile
There's some snapshot commands to use for an instantaneous peek at the queue, store and pool, but I would suggest letting PS guide you through those, some commands with a fast ker poll rate can create the same symptom you're trying to diagnose and bring a system to its knees.
LLDCLI DSPOOL AUDIT
give the results to Prod Supp.
I'm pretty sure sastats and slopoke are gone, but donno about others. Is the LIST command structure still supported and would any of those help?
Maybe turn on the kernel monitor and then watch the SW logs for an hour or so during peak traffic hours.
KER CO(ontinuous)
KER STOP
I forget the interval the kernel reports are put in the SW log, every 15 mins or so seems I recall. Been awhile
There's some snapshot commands to use for an instantaneous peek at the queue, store and pool, but I would suggest letting PS guide you through those, some commands with a fast ker poll rate can create the same symptom you're trying to diagnose and bring a system to its knees.
- Status
