| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4153.1 | | NETCAD::MILLBRANDT | answer mam | Mon Jan 06 1997 13:38 | 10 |
| 4153.2 | | NETCAD::DOODY | Michael Doody | Mon Jan 06 1997 15:25 | 7 |
| 4153.3 | SNMP trace, not making much sense | KERNEL::FREKES | Like a thief in the night | Fri Jan 10 1997 12:16 | 46 |
| 4153.4 | | NETCAD::DOODY | Michael Doody | Tue Jan 14 1997 11:22 | 40 |
| 4153.5 | Refresh, add failed SNMP trace | KERNEL::FREKES | Like a thief in the night | Thu Jan 16 1997 06:38 | 516 |
| 4153.6 | | NETCAD::DOODY | Michael Doody | Thu Jan 16 1997 10:05 | 23 |
| 4153.7 | NETCAD::SNMP_TRACE.TXT;2. | KERNEL::FREKES | Like a thief in the night | Thu Jan 16 1997 12:09 | 9 |
| 4153.8 | how to get a concise LAN int SNMP trace | NETCAD::MOWER | | Thu Jan 16 1997 20:00 | 29 |
| 4153.9 | port 3 of the slot 8 DECswitch 900EF is broken | NETCAD::MOWER | | Thu Jan 16 1997 20:16 | 59 |
| 4153.10 | Port status "broken" is normal for inactive port... | NETCAD::BATTERSBY | | Fri Jan 17 1997 10:39 | 16 |
| 4153.11 | | NETCAD::DOODY | Michael Doody | Fri Jan 17 1997 17:09 | 8 |
| 4153.12 | Another "broken" indicator....hmmmm | NETCAD::BATTERSBY | | Tue Jan 21 1997 13:42 | 12 |
| 4153.13 | I "C" the error in my analysis now :-) | NETCAD::BATTERSBY | | Tue Jan 21 1997 14:11 | 8 |
| 4153.14 | Dodgy EF, once swapped, all OK | KERNEL::FREKES | Like a thief in the night | Thu Jan 23 1997 14:14 | 11 |
| 4153.15 | If customer happy, that be cool... :-) | NETCAD::BATTERSBY | | Thu Jan 23 1997 15:00 | 7 |
| 4153.16 | EF Error log. | KERNEL::FREKES | Like a thief in the night | Fri Jan 24 1997 06:43 | 70 |
| Bob
I had a look through rather a large pile of faxes, and lo and behold, here
it is.
I guess the first entry is the latest one. There are quite a few so here goes.
Entry = 1
Entry Status = 0
Entry id = 1
Firmware rev = 2.2
Reset Count = 158
Timestamp = 0 0 0
Write count = 110
FRU Mask = 2
Test ID = 921
Error Data = SR=0003 PC=00000073 Error code=00000000 ProcCsr=0000
0:00000003 1:00000073 2:00000000 3:00000000
4:00000000 5:00000000 6:00000000 7:00000000
Entry = 0
Entry Status = 0
Entry id = 10
Firmware Rev = 1.6
Reset Count = 158
Timestamp = 0 0 CFB
Write count = 110
FRU mask = 0
Test Id = DEAD
Error Data = SR=2400 PC=03033262 Error code=000023C0 ProcCSR=176D
Registers = D0=00FE0060 D1=0000AB20 D2=040100FE D3=00000080
D4=0000000E D5=0000FF80 D6=04170800 D7=0000FF80
A0=040002A0 A1=00002080 A2=00028A20 A3=04095082
A4=05028D10 A5=000269F0 A6=00002440 A7=0004BBD4
Entry = 3
Entry Status = 0
Entry id = 1
Firmware rev = 2.2
Reset Count = 157
Timestamp = 0 0 0
Write Count = 109
FRU mask = 2
Test id = 920
Error Data =SR=FFFF PC=00000002 Error Code=000000FF ProCSR=FFFF
0:FFFFFFFF 1:00000002 2:000000FF 3:000020FF
4:00000000 5:00000000 6:00000000 7:00000000
Entry = 2
Entry Status = 0
Entry id = 1
Firmware Rev = 2.2
Reset Count = 157
Timestamp = 0 0 0
Write Count = 109
FRU Mask = 2
Test ID = B01
Error Data = SR=0002 PC=00000004 Error Code=00000002 ProcCSR=0000
0:00000002 1:00000004 2:00000002 3:00000000
4:00000000 5:00000000 6:00000000 7:00000000
There were no more entries in the error log.
Regards
Steven
|
| 4153.17 | The error log indicates problems with an Ethernet port | NETCAD::BATTERSBY | | Fri Jan 24 1997 10:54 | 15 |
| Ok 3 of those 4 error log entries point to a problem with the
Lance ports. Test ID's 920, 921, are related to port 3 (second
Ethernet port on an EF) diagnostic tests. Test B01 is an internal
diagnostic loopback test to test the each of the Ethernet ports.
The Test ID of "DEAD" with an error code 23C0 is a firmware reported
error which might be a second order affect of attempting to do
some backplane operation with that defective Ethernet port.
When one port goes bad, what one should have seen I believe, is
that the module runs its POST on power up, detects a single Ethernet
port failure, but continues and allow eventual hand-over to firmware.
I think too that the Module OK LED might blink on and off indicating a
non-fatal failure. That would have been an indication that all
wasn't fine with the module.
Bob
|
| 4153.18 | | KERNEL::FREKES | Like a thief in the night | Fri Jan 24 1997 12:54 | 9 |
| Bob
This seems to tie up with Carl Mowers response from the SNMP trace
taking during the attempt to add the leg onto the LAN. This indicated
that the problem was a faulty ethernet port (port 3).
Thanks for all the help
Steven
|
| 4153.19 | Yup it makes perfectly good sense now.... | NETCAD::BATTERSBY | | Fri Jan 24 1997 14:00 | 3 |
| I absolutely concur and agree.
Bob
|