[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::sns

Title:POLYCENTER System Watchdog for VMS OSF/1 ULTRIX HP-UX AIX SunOS
Notice:Wishes:406,FAQ:845,Kits-VMS:1000,UNIX:694 VMS ECO01 FT kit: 521
Moderator:AZUR::HUREZZ
Created:Fri May 15 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1033
Total number of notes:4584

998.0. "ESA0 error not visible in error log" by GIDDAY::REID (David Reid,CSC,Sydney DTN 730-7233) Tue Feb 11 1997 18:51

Greetings,

It appears we are getting a very similar error to what was reported in Note 818
and I was wondering if anyone had a explanation.

MicroVAX 3400
VAX/VMS V5.5-2
Watchdog 1.0-01

Watchdog logfile is reporting the following errors.

***************************** 11-FEB-1997 09:05:46 ****************************
*
Record type  : Message removed
Message type : SNS_C_ETH
Node name    : QV10
Message text :
 11-FEB 07:07 QV10   Ethernet ESA0: error count has increased to 271 from 266

The number of errors seem to be increasing as time goes on and seems to be
related to a lose of connection on the network...but had to pin point.

As with note 818 the numbers of errors match fatal errors as reported in SDA
T.RTitleUserPersonal
Name		DateLines
998.1Output from SDAGIDDAY::REIDDavid Reid,CSC,Sydney DTN 730-7233Tue Feb 11 1997 19:0847
ooppsss...System hung..and note closed...

Output from SDA:


LAN Data Structures
-------------------
              -- ESA Device Information 12-FEB-1997 09:17:05 --

LSB address                 80805180    Active unit count                  6
LAN version        A4000001 05052025    Driver version     00000004 05050016
LAN code address            807FF568    Driver code address         807FD250
Device name                 ES_LANCE    Device type                       24
Device version     00000000 0000000A    DLL type                      CSMACD
Data chaining                     ON    All multicast state              OFF
Controller mode               NORMAL    Promiscuous mode                 OFF
CRC generation mode               ON    Hardware mode                   0000
Physical address   AA-00-04-00-34-A0    Hardware address   08-00-2B-17-3E-E5
Flags:  0000                            Characteristics: 0000
Status: 0013 Inited,Run,Timer

DAT stage                   00000000    DAT xmt status     0000001A 001A0001
DAT number started               127    DAT xmt complete     11-FEB 18:32:19
DAT number failed                  0    DAT rcv found                   None

          -- ESA Device Information (cont) 12-FEB-1997 09:17:05 --

Creation time                   None    Create count                       0
Deletion time                   None    Enable count                       0
Enabled time                    None    Fatal error count    ****>>>>>     126
Disabled time                   None    Excessive collisons                0

Last receive         12-FEB 09:17:05    Last fatal error     11-FEB 18:32:17
Last transmit        12-FEB 09:17:05    Prev fatal error     11-FEB 18:32:11
Last fork sched      12-FEB 09:17:05    Last exc collision   11-FEB 18:33:23
Last fork time       12-FEB 09:17:05

Now....this may be a bit far fetched but could there be any relationship between
the number of "fatal" errors and the number of times DAT started...???
...only a hunch - based on that the connection to the rest of the network
appears to happen at around the same time.

Thanks and regards,

David R

DEC CSC Sydney
998.2Need a system showing that error for tests...AZUR::HUREZConnectivity & Computing Services @VBE. DTN 828-5159Wed Mar 12 1997 11:167
    Would you allow me to log on your node and probe the ECO04 against that
    problem?
    
    Thanks,
    
    	-- Olivier.