error message after boot

[george, casanova]

System is up and running since Sunday i got the following error


*******************************LAN/9000 NETWORKING**************************@#%
Tue May 23 EDT 2000 09:28:40.714783 DISASTER Subsys:NS_LS_DRIVER Loc:01029
Network NS_LS_DRIVER Disaster 1029, pid [ICS]
LAN card on interface unit 1 has network problem. Check cable for
possible disconnection.


I am running 11.00HPUX and its a v2200 box
any help would be appreciated

[Berlene Herren]

There are a couple of reasons for this error, the most common being a corrupted nettl.LOG file, the least common a hardware problem.

Ensure you have the latest LAN, ARPA and Streams patches
PHNE_21217 (LAN)
PHNE_20735 (ARPA)
PHNE_20316 (Streams)
PHNE_21433 (Streams/pty)

Issue:

#nettl stop
#rm /var/adm/nettl.LOG00
#nettl start >> this creates a new log

Ensure you do NOT have any backup copies of netconf in /etc/rc.config.d.

Another reason for this error is the network card is not properly terminated or connected.

Let me know,
Berlene

[george, casanova]

in that file it says that there is DISASTERS...

on that particular day there was nfs problems
would that explain theses messages

[Tan Eu Soon]

I'm having the same problem mentioned below and will be grateful if someone could advise me.

I had tried removing & recreate nettl.LOG00 as suggested by Berlene (except s/w patching), changing the lan card & transceiver, used lanadmin to reset lan0. Our network administrator has comfirmed there is nothing wrong with the lan port.

My machine is a HP9000 - 800/H40 server running HP-UX 10.20.

[Tan Eu Soon]

My apologies for sending the same messages thrice because there was an error each time I click "submit" & not knowing that my message was submitted successfully.

[Berlene Herren]

Does anyone have this scenario?

This error message coul be caused when the system checks each lan card and finds that one of them is not connected to a network. In this case the message can either be ignored since the lan card is not being used anyway or
actions can be taken to stop the message altogether.

To stop the messages, either connect a loopback connector to the unused lan
port (which will allow the network tests to pass) or remove the lan cards driver from the kernel (assuming that no other network cards are using this same driver). The command ioscan -fC lan can be used to see all network cards and their drivers in a system.

If this case doesn't apply, then let's try this

1. delete /var/adm/conslog.opts and recreate as follows:
FORMATTER FILTER CLASS !*
FORMATTER FILTER CLASS DISASTER
FORMATTER FILTER TIME_FROM 12:54:50.000000 12/11/96 >>> today's date
2. stop nettl
2. Delete /var/adm/nettl.LOG00
3. Move /etc/nettlgen.conf file to /etc/nettlgen.old, and
then copy a new one from /usr/newconfig/etc/nettlgen.conf
4. Restart nettl as /usr/sbin/nettl -start

Hope one of these helps. You can also try replacing the cable with a known good one.

Berlene

[Bruce Regittko_1]

Hi,

Yes, we get a very similar message on our D220's with an unused EISA lan card. It is always fun to see our student's reactions when they boot and see the "DISASTER" message on the console.

Connecting the card to a powered up hub/switch will prevent the message so from a hardware standpoint, you narrow the problem to either the cable, terminator, or lan card. Of course, if it is a software problem... .

--Bruce