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 IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

6.5 Intermittent Reboot

Status
Not open for further replies.

tmattson

IS-IT--Management
Jul 3, 2001
125
US
We have been experiencing intermittent system reboots for no apparent reason. No error messages or abend dump was produced. This has happened three times in the last six months. I assume it is something hardware related but I've run diagnostics on the server and they come back clean.

Is there anyway Netware could be the culprit? I am running 6.5 sp4 on a Compaq Proliant ML350.

Any advice on what to look for would be greatly appreciated.
 
Here's what I suspect. Something on the server is running the processor up really high, and it sits there for 10 minutes. Maybe it's the backup.

The Compaq ASR thinks it's a windows box and this behaviour means that the system is Fubar'd. So it automatically reboots the system. (ASR=Automatic System Reboot).

You can verify that this has happened by looking in the Compaq system logs. If you have the Compaq agents installed (you should), run CPQIML.NLM and it will show you any system generated events. If this happened you'll see an ASR event.

You need to turn off the ASR in the BIOS. Then, if you continue to have any problems, you should be able to get some sort of Novell system log.

Usually this happens during a backup when the processor is working hard, but its nothing critical.

Marvin

Marvin Huffaker, MCNE
 
make sure you have the latest support packs as well

original 350's had a cosmetic bug on i think it was around the 6.4 pack
you want 7.51 on it
 
I had a very similar issue on a DL360 G4 that turned out to be related to a memory leak in tsafs.nlm. Memory would not be released and after a couple of months the server would cough and die.

Go to server monitor, memory, and look at the amount of memory allocated to tsafs.nlm. If it seems to be steadily increasing, that is a problem. My issue went away after I updated to the latest tsafs.nlm.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top