xntpd & NS_LS disaster

[Sharon Bi]

Dear all,

One of our workstation ( 712) today keep getting the following error on its screen:

NS_LS disaster.

And i got some xntpd messages in the /var/adm/syslog/syslog.log:

xntpd[949]: peer 192.64.161.1 event 84: Peer reachable.
Nov 29 12:44:48 node22 xntpd[949]: system event 4: System new peer or system stratum change.
Nov 29 13:44:14 node22 xntpd[949]: offset -0.000096 freq -20.48671 comp 2

Do anyone give me some help? ( i don't know whether it's related or not. I have tried lanscan, ioscan -fnC lan: claimed, lanadmin to reset... but they still get the same error)

Thanks a lot

[Lasse Knudsen]

It seems like your Network I/F is going up and down.

Could be a problem with switch/hub-settings or the cable - check this.

I think the xntpd messages is related to your problem or maybe your xntp server has changed its configuration.

Have you done anything special with nettl configuration ?

[Steffi Jones_1]

Hi,

for the NS_LS disaster... this is what I found:Checking for parity errors in testmode confirms that these would
increment when a failure occurred.

A new version of code was developed that limited the criteria for
resetting all the ASICs and this will resolve your problem. The
fix is available starting with A.03.01.

and for the xntpd issue:

This could be a path X.X.0 not responding. Causing system interrupts to
the point of system clock drift problems.

Steffi Jones

[Rita C Workman]

Well I'll take a swing at this:

ns_ls disaster is generally indicative of the terminator missing off the device.

The other seems to be nothing more than the messages involved in xntpd where it is trying to time sync the device.

Just a thought,
rcw

[Anthony deRito]

NS_LS is part of a subsystem name that is monitored by the nettl (Network Tracing and Log) facility. A typical subsystem name would be NS_LS_IP or NS_LS_NFS. If logging or tracing is started in nettl, the default is to have all notification of "Disaster" related events to go to the console. There are many levels of events and "Disaster" is one of them.

Run the following command:

/opt/nettladm/bin/nettladm

Check to see if loggin is turned on by looking at the "Logging" field at the top left. You can troubleshoot further by using the "Actions" -> "Monitor Log Files" and "Modify Loggin" menu selections.

My first thought is that you have part of a valid disaster message from nettl and it should be checked out.

I do not believe the ntpd messages are related.

Tony