topic Re: Reboot immediately in Operating System - HP-UX

Reboot immediately

Cahyo Tri Nugroho — Tue, 25 Mar 2003 02:00:04 GMT

Dear all,

Why does my machine (HP-9000,K260;HPUX 11.00) reboot immediately if there any problem with it's network equipment like cable or switch which the machine connect to?

Re: Reboot immediately

Steven E. Protter — Tue, 25 Mar 2003 02:26:30 GMT

That could be an issue with the network hardware itself.

It could be your driver for the NIC card is out of date.

I'd check dmesg and /var/adm/syslog/syslog.log for messages.

This is absolutely unacceptable.

Check the switch settings. If its a Cisco switch turn off autonegotitate and have the administrator and have them hard code the proper setttings in the switch.

Check your systems /etc/rc.config.d/hpbtlanconf file for setting, and make them match the switch settings. If you need examples, I can provide them in the morning.

SEP

Re: Reboot immediately

Michael Tully — Tue, 25 Mar 2003 02:30:26 GMT

Other than checking for entries in the syslog, you might also see if there are any entries in /etc/shutdownlog. Are there distinct entries in the tombstone directory, /var/tombstones, i.e. is ts99 different to ts98 etc.

Re: Reboot immediately

Michael Steele_2 — Tue, 25 Mar 2003 02:51:01 GMT

This is a system panic and its serious. Also check these sources for information:

netfmt -LN -f /var/adm/nettl.LOG* > /tmp/file

search file for:

disaster
cable
error, etc.

Also check LOGTOOL:

STM > TOOLS > UTILITY > RUN > LOGTOOL > FILE > VIEW > RAW SUMMARY.

Note the first and last dates of transactions and calculate the difference. If the difference is short, like 4 hours, then this is important to note. Now read down the report of hardware addresses and observe the integer numbers in parenthesis. Anything over 150 in this 4 hour period should be called into HP for replacement.

Cross reference your NIC's HW address in LOGTOOL. Use ioscan to obtain it.

ioscan -fknC lan

Re: Reboot immediately

Cahyo Tri Nugroho — Tue, 25 Mar 2003 08:44:26 GMT

There is nothing in syslog.log

- /etc/shutdownlog :
19:05 Wed Mar 12 2003. Reboot after panic: , isr.ior = 0'9227ffff.c0000000'e8331030
17:47 Thu Mar 13, 2003. Reboot: (by ediijkt1!root)
14:24 Mon Mar 17 2003. Reboot after panic: , isr.ior = 0'9227ffff.c0000000'e8331030

- result of netfmt command :
Timestamp : Mon Mar 17 wib 2003 14:15:34.041347
Process ID : [ICS] Subsystem : NS_LS_DRIVER
User ID ( UID ) : -1 Log Class : DISASTER
Device ID : -1 Path ID : 0
Connection ID : 0 Log Instance : 0
Location : 01029
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Network NS_LS_DRIVER Disaster 1029, pid [ICS]
LAN card on interface unit 1 has network problem. Check cable for
possible disconnection.

*******************************LAN/9000 NETWORKING**************************@#%
Timestamp : Mon Mar 17 wib 2003 14:16:07.641448
Process ID : [ICS] Subsystem : NS_LS_DRIVER
User ID ( UID ) : -1 Log Class : DISASTER
Device ID : -1 Path ID : 0
Connection ID : 0 Log Instance : 0
Location : 01029
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Network NS_LS_DRIVER Disaster 1029, pid [ICS]
LAN card on interface unit 1 has network problem. Check cable for
possible disconnection.

Re: Reboot immediately

Robert-Jan Goossens — Tue, 25 Mar 2003 09:11:48 GMT

Hi,

One other thing, ask your network guy's to change the port on their switch. Maybe the port is giving you the error.

Hope it helps,

Robert-Jan.

Re: Reboot immediately

Trond Haugen — Tue, 25 Mar 2003 10:05:58 GMT

Is the system part of a ServiceGuard cluster? If so it's a feature of the system loosing the heartbeat. Not to say it should. In that case I would reccomend investing network problems and increasing the timeout.

Regards,
Trond

Re: Reboot immediately

Michael Steele_2 — Tue, 25 Mar 2003 11:39:42 GMT

Check /var/adm/crash for a dump. If it's not there then try to take one but first check /etc/rc.config.d/savecrash for an alternate dump directory. If a dump is found then verify the time stamp with "...who -b...", if not found then locate a spot with 400 plus megabytes and:

savecrash -rf /new_spot/file

Obtain a copy of q4 analysis instructions and send it in to HP.

In the meantime check your LAN drivers and patches.

swlist -l product | grep -i -e 100 -e lan -e btlan.

Re: Reboot immediately

Duncan Galbraith — Wed, 26 Mar 2003 07:50:26 GMT

You may wish to check if you have patch PHNE_22814.
This is meant to fix this problem.
I'll try adding the link:
http://www4.itrc.hp.com/service/patch/patchDetail.do?patchid=PHNE_22814&context=hpux:800:11:04