| Title: | Ethernet Volume 3 |
| Moderator: | UPSAR::THOMAS |
| Created: | Thu Oct 08 1992 |
| Last Modified: | Thu May 22 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 914 |
| Total number of notes: | 3047 |
Greetings, This problem has come up out of an issue which I posted on the SNS Notesfile (Watchdog). Watchdog is reporting fatal errors on the ethernet controller (ESA0) which are not showing up in the errorlog or as an issue in the line counters. I have found that the error counts match those reported in SDA as fatal errors. Obviously (one could say) watchdog is doing its job....the question is what is causing these "fatal errors". Based on an earlier entry in the SNS conference (where the ethernet controller was changed to no avail) I have so far not changed the hardware. Apparently these error counts seem to be incrementing at times when certain parts of the network become unavailable. What can cause these fatal errors?? Hunch....Could it have something to do with the DAT restarts which SDA also displays. I know it sounds a bit far fetched (particularly as I have forgotten the meaning of the DAT field [something address translation??] but could these errors be a result of DAT restarts?? I noticed a close relationship between the number of fatal errors and DAT restarts on a numner of machines..... Thanks, David R
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 902.1 | STAR::STOCKDALE | Tue Feb 18 1997 13:00 | 6 | ||
Fatal errors could be caused by cable disconnection, bad hardware, and other failures. You can find out what they are in SDA by doing a SHOW LAN/ERROR or SHOW LAN/FULL (to see everything). And the counters information in SHOW LAN/FULL or SHOW LAN/COUNTER will provide more information. - Dick | |||||