Conference netcad::hub_mgnt

2686.0. "Network traffic stopped flowing. Suspect db900mx." by KAOFS::L_PELLAND (Luc Pelland. Hull. DTN 640-7218) Mon Aug 28 1995 16:10

	Here are the error logs from a 900MX bridge that a customer have
	had a network failure on (network traffic stopped flowing, SAA
	sessions dropped). We suspect it may be the bridge causing the 
	problem. Can you please let me know what the error code reported 
	by the DB900mx are and how the error may affect the bridges ability
	to  bridge traffic. The customer is running V1.4.4 of the firmware
	and the network environment uses mainly IPX/SPX and TCP/IP protocols.
	From previous note in here I am incline to ask the customer to upg
	the DB900mx to 1.5 of the firmware. 

	Thank you.
	Luc.

DECbridge 900MX - slot 8
=============================================================================

                                DUMP ERROR LOG
                            Current Reset Count: 7

=============================================================================


Entry #       = 2
Entry Status  = 0   [0=valid, 1=write_error, 2=invalid, 3=empty, 4=crc_error
Entry Id      = 11
Firmware Rev  = 1.4
Reset Count   = 7
Timestamp     =    0   80 D9BF
Write Count   = 24
FRU Mask      = 0
Test ID       = 1FC
Error Data    = SR=000A PC=00000000 Error Code=00000000 ProcCsr=0000

                 0:0000000A  1:00000000  2:00000000  3:00000005
                 4:00000000  5:00000000  6:00000012  7:00000000
Dump another entry [Y]/N? y
Entry #       = 1
Entry Status  = 0   [0=valid, 1=write_error, 2=invalid, 3=empty, 4=crc_error
Entry Id      = 11
Firmware Rev  = 1.4
Reset Count   = 7
Timestamp     =    0   80 D9BE
Write Count   = 24
FRU Mask      = 0
Test ID       = E
Error Data    = SR=A684 PC=00000000 Error Code=00000007 ProcCsr=0004

                 0:0004A684  1:00000000  2:00000007  3:00000015
                 4:040B1823  5:00000015  6:0004A6A0  7:03033558
Dump another entry [Y]/N? y
Entry #       = 0
Entry Status  = 0   [0=valid, 1=write_error, 2=invalid, 3=empty, 4=crc_error
Entry Id      = 11
Firmware Rev  = 1.4
Reset Count   = 7
Timestamp     =    0   80 D9BD
Write Count   = 24
FRU Mask      = 0
Test ID       = E
Error Data    = SR=A684 PC=00000000 Error Code=00000007 ProcCsr=0004

                 0:0004A684  1:00000000  2:00000007  3:00000015
                 4:040B1823  5:00000015  6:0004A6A0  7:03033558
Dump another entry [Y]/N? y
Entry #       = 3
Entry Status  = 0   [0=valid, 1=write_error, 2=invalid, 3=empty, 4=crc_error
Entry Id      = 11
Firmware Rev  = 1.4
Reset Count   = 7
Timestamp     =    0   80 D9BC
Write Count   = 23
FRU Mask      = 0
Test ID       = E
Error Data    = SR=A684 PC=00000000 Error Code=00000007 ProcCsr=0004

                 0:0004A684  1:00000000  2:00000007  3:00000015
                 4:040B1823  5:00000015  6:0004A6A0  7:03033558
Dump another entry [Y]/N? y
==============================================================================

No more Error Log entries.
                       Press Return for Main Menu ...

Alphonse

	Hello all,

	My customer will look into getting the latest firmware version
	for his bridge but he still want to known what these errors code
	are and if they can cause outage on his network. Also he and I
	would like to known if there is any document that give a list
	of error code and the meaning of it.

	Thank you.
	Luc Pelland.
	Hull CSC.

    Luc, the 4 entry log errors seem to suggest that there is an FDDI
    related problem. If you look at the entry ID for each error log,
    you will see an "11". This implies an FDDI related problem. It's
    difficult to say whether it is internally caused (internal to the
    bridge), or whether it is externally caused (by something else on 
    the ring the bridge is connected to). One of the error log entries
    has an error code of "1FC", which in conjunction with the Entry ID
    of 11 says there is something wrong that is FDDI related.
    We have suggested to other sites that have seen this type of error
    log entry to upgrade to the newer 1.5 rev, for the following reason.
    The new image (1.5), has a much more robust error log format. Thus
    one gains much more information from the newer error log format
    afforded by the new wave 3 release (1.5 switch code).
    So the suggestion here is to suggest to your customer to upgrade to
    the new V1.5 rev of switch code. Having done this, the customer can do
    another dump of the existing error log information, and there will be
    more error log fields of data that would be useful to know as a means
    of analyzing what might be wrong. Also suggest to the customer to
    monitor the frequency of which the DECswitch drops off the FDDI ring,
    (and of course the subsequent new error log entry).
    There are 4 error log entries, (numbered 0-3). When the 4th one is
    written, and there is a subsequent error log written it is overwritten
    to entry 0.
    With regard to a "list" of error codes. There is no such document. These
    error codes as such are imbedded in the source code of the operational
    code, and we don't give out source code to customers on a regular
    basis. :-)
    So get the bridge upgraded, dump the error log info again, post it in 
    here, or mail it to me and I'll make sure it gets into the hands of one
    of our guru's of DECswitch firmware to analyze. It may also prove
    useful, to know what other hardware is connected to the FDDI ring
    shared with this DECswitch.
    
    Bob