SAM Question

[Jeffrey F. Goldsmith]

Last week my server decided to reboot itself in the early morning. When I got in that morning I needed to find out what happened. I started SAM and went into the Performance Monitors and then I went into the System Properties.
Here is where my problems started. I was checking the different folders on that screen. When I hit the Network folder to see what information was available and it sat there for a few minutes and then everything started to shutdown.
My Reflection X window closed as did the other Reflection for windows did. I had to go to the console connected to my server to see what happened. It seems that the NIC was turned off. I couldn???t connect with any other server.
What caused it to do that? The only thing that I knew what to do at that time was to reboot the server. Is there a way for me to restart the NIC without having to reboot the server?
I tend to remember another time when I was in SAM and I checked something that had to do with networks that the NIC had stopped responding in the same way. And at that time all I could do was reboot the server. I can???t keep rebooting my server every time that the NIC stops talking.

[Francois Bariselle_3]

Hi,

Check first for the errors messages in /var/adm/syslog.log.

Frank

[Sanjay_6]

Hi,

I think there is a file in /sbin/init.d called net.init

call this file with start option and see if this helps.

/sbin/init.d/net.init start

Hope this helps.

Regds

[Jeff Schussele]

HI,

You want to run
#ifconfig lan(x) up
But you need to determine what's causing the problem. Use teh stm suite - I prefer the GUI xstm to look at the NIC. And definitely check the logs out.

Rgds,
Jeff

[pap · Accepted solution]

Hi,
You can do folloing to restart the netork (LAN)

/sbin/init.d/net stop
/sbin/init.d/net start

By any chance, is this machine configured in a service guard environment?
If it is then it may reboot. Sometimes if the other machine configured in service guard is not receiving heart bit signal from this machine, it reboots the machine.
In this case you need to increase the NODE_TIMEOUT parameter to 8 sec. Normally by default ist is set to 2 sec.

Hope this helps.


Thanks,

-Piyush.

[John Carr_2]

Hi

to physically reset a NIC without booting you can use

lanadmin >> lan >> reset

This will cause the local LAN interface card to reset, causing it to execute its self test. Local access to the network is interrupted during execution of reset.

/sbin/init.d/net stop & start configures the working device it does not reset it..

checkout man page for lanadmin

if you are using an old version of hpux 10.00 or below then the command is landiag.

John.

[Jeffrey F. Goldsmith]

This afternoon I had the chance to perform that test with SAM. I clicked on the Network folder again and was dropped from the network. Here are the results from your suggestions.


Francois,
I checked for error messages in syslog.log and found none.

Sanjay,
I tried what you suggested,
/sbin/init.d/net.init start
It did not help start the NIC.

Jeff,
I couldn't find the information to run what you asked. I am going to look it up this afternoon.

pap,
I also tried what you suggested,
/sbin/init.d/net stop
/sbin/init.d/net start
That didn't wake up the NIC either.

If you have any suggestions for me pass them my way.

Thanks

[Jeffrey F. Goldsmith]

John,

My server is using HPUX 10.20 and I checked the man pages on landiag. So, if I am following this right I would enter this:
lanadmin btlan01 reset
to reset the NIC to get it to start responding again. Let me know if this is correct as I want to give it a try while I have the server to myself this weekend.
Thanks

[John Carr_2]

Hi

just type command lanadmin this is a menu driven utility which is easy to use just select sub menu lan the reset.

cheers have a nice weekend
John