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

Conference netcad::hub_mgnt

Title:	DEChub/HUBwatch/PROBEwatch CONFERENCE
Notice:	Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7
Moderator:	NETCAD::COLELLADT

Created:	Wed Nov 13 1991
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	4455
Total number of notes:	16761

4332.0. "DEFBA Error Log Question" by ZUR01::FIERZ () Thu Apr 03 1997 03:06

    Can someone please explain what this errorlog entry of a DECbridge900EF
    means and what consequences it migth have to a stable network ?

Thanks
Thomas Fierz, MCS Network Support, Switzerland

-------------------------------------------------
DECswicht900EF:  HW=v1/2, RO=v0.4, SW=1.6.1 
   Uptime: ca. 238 days

Entry #      = 0
Entry Status  = 0   [0=valid, 1=write_error, 2=invalid, 3=empty, 4=crc_error
Entry Id      = 11
Firmware Rev  = 1.6
Reset Count   = 18
Timestamp     =    0   51 57C3
Write Count   = 5
FRU Mask      = 0
Test ID       = 3DB
Error Data    = SR=00002000 PC=0009378A ErrorCode=00000005
Registers     = Phy1Csr     =000003DB ElmBase     =00000000 MacBase    =00000000
                CamCsr      =0000823F CamData15_00=00000000 PmCsr      =00001405
                CamData31_16=00004300 CamData47_32=00008001 PortDataA  =04000000
                RtosTimer   =00000030 RtosTimerVal=00000011 PortDataB  =00000000
                i68k68kInt  =00000000 i68k68kMask =000001FF DmaInt     =0000003F
                i68kForceInt=00000000 DmaMask     =00000000 HostData   =00000000
                HostInt0Mask=00000000 HostInt0    =000000C0 PortStatus =00000500
                PortCtrlMask=00007FFF HostDmaMask =00005000 PortCtrlInt=00000000
                FmcControl  =00000032 FmcStatus   =0000E000 FmcInt     =00000000

T.R Title User Personal
Name Date Lines

4332.1 I've seen this Test ID before recently.... NETCAD::BATTERSBY Thu Apr 03 1997 09:32 28

T.R	Title	User	Personal Name	Date	Lines
4332.1	I've seen this Test ID before recently....	NETCAD::BATTERSBY		`Thu Apr 03 1997 09:32`	28
	I've seen this Test ID=3DB before, but with an error code of 00000003 instead of 00000005. I consulted with a software engineer who was familiar with the FDDI corner 68000 adapter firmware code, and he was able to determine that the Test ID is consistent with an FDDI crash. The previous instance that I've seen this with the error code field of 00000003, it was suggested to me that it had something to do with a CNS code crash reported to the dispatcher. I can't say that the error code 00000005 is also related to the same specific CNS code area within the FDDI adapter firmware. Judging by the PC being identical to what I've seen, it may be an associated error type within the same section of code. So in summary, it has something to do with the FDDI corner firmware, but I have no way of interpreting the consequences it might have on a stable network other than to guess that if the FDDI firmware crashed, then connections must have been lost while the DECbridge reset and restarted. Hope this helps. I will pass this error log on to possibly get further scrutiny, but can't guarantee answers at this time. Also, without further info and details posted here on whether the customer you presumably got this error log from experienced a legitimate network outage and the detailed circumstances under which this error log occured, it would be difficult to speculate further. As has been suggested by NPSS support folks, (and I'm not one of them), you might want to consider logging an IPMT case if your customer had a legitimate outage, or if it occured more than once. Bob

    I've seen this Test ID=3DB before, but with an error code
    of 00000003 instead of 00000005. I consulted with a software
    engineer who was familiar with the FDDI corner 68000 adapter
    firmware code, and he was able to determine that the Test ID
    is consistent with an FDDI crash. The previous instance that
    I've seen this with the error code field of 00000003, it was
    suggested to me that it had something to do with a CNS code
    crash reported to the dispatcher. I can't say that the error
    code 00000005 is also related to the same specific CNS code
    area within the FDDI adapter firmware. Judging by the PC being
    identical to what I've seen, it may be an associated error type
    within the same section of code.
    So in summary, it has something to do with the FDDI corner firmware,
    but I have no way of interpreting the consequences it might have
    on a stable network other than to guess that if the FDDI firmware 
    crashed, then connections must have been lost while the DECbridge
    reset and restarted. Hope this helps.
    I will pass this error log on to possibly get further scrutiny, but
    can't guarantee answers at this time.
    Also, without further info and details posted here on whether the 
    customer you presumably got this error log from experienced a 
    legitimate network outage and the detailed circumstances under which 
    this error log occured, it would be difficult to speculate further. 
    As has been suggested by NPSS support folks, (and I'm not one of them), 
    you might want to consider logging an IPMT case if your customer had 
    a legitimate outage, or if it occured more than once.
    
    Bob