Conference 7.286::fddi

    test bridge xx-xx-xx-xx-xx-xx diag block=true
    
    to write to a file:
    
    test bridge xx-xx-xx-xx-xx-xx diag block=true, to file x.x
    
    ken

    Thanks Ken
    
    
    Now the next question. Can someone tell me where the crash code is in
    the following diagnostic block. This customer is running v1.3 and I
    suspect he may have the 1500 byte ping problem that was fixed in V1.5
    They have recently installed Cabletron Spectrum and the bridges have
    started to crash. 
    He is reluctant to upgrade to V1.5 as the bridges have been very
    reliable on this version, so I would like to confirm the crash reason.
    
    
     Thanks Jim
    
    
                                        
    
    
    Bridge PFIZER_NS:.sandwich.mcc_db.fbpcna_180c_elms
    AT  7-AUG-1996 08:45:10
    
    Examination of attributes shows:
                           Diagnostic Block = (
    
    %X000D000F00000000000000030000DEAD,
    %X00002304001AF2320000207C00000000,
    %X00000000000000020000000000000002,
    %X00000001000000000000000900200FD0,
    %X3FFFFFFF20001780003DC968003E9324,
    %X003DC968001884BA000004FC00200F20,
    %X00000000003DCB96A9156ACD00000001,
    %X00000007000000070000000000000000,
    %X00000107003D675E0018B61C00201800,
    %X0000006400000037FFFFFFFD5B5430DF,
    %X100D001000000000000D00030000DEAD,
    %X00002300001AEFA60000207C00000000,
    %X000000000000000300000000003E9C03,
    %X00000001000004010000210000000000,
    %X3FFFFFFF200017B8003DC96800000004,
    %X003E958C003E9B6C000004FC002000C4,
    %X00000000003DCB96A9156ACD00000001,
    %X00000007000000070000000000000000,
    %X00000107003D675E0018B61C00201800,
    %X0000006400000008FFFFFFFDA17F58AF,
    %X100D0013000000BA34C100030000DEAD,
    %X00002000001B88960000100000000000,
    %X00000000000010000000000000006000,
    %X00200000000060000000FFFF00000000,
    %X00000000003EBFAE003EBFAE003EBF8A,
    %X003E91C620003E28000004FC002017EC,
    %X002017BC003DCB96A9156A8D00000001,
    %X00000007000000070000000000000000,
    %X00000107003D675E0018B61C00201800,
    %X0000006400000048FFFFFFFDC2B02B38,
    %X100D001400000001D42D00030000DEAD,
    %X000021000018A2FA0000014400000000,
    %X0000000008002B7500002100FFFF0000,
    %X00201800000000400000FFFF00000000,
    %X0000000020071836003D6E6C2007182A,
    %X2000189820001820000004FC002017FC )
    
    
    
    
    Bridge PFIZER_NS:.sandwich.mcc_db.fbpcna_380a_elms
    AT  7-AUG-1996 09:02:27
    
    Examination of attributes shows:
                           Diagnostic Block = (
    %X000D001A000000000008002D0000DEAD,
    %X00002300001AECA00000207C00000000,
    %X000000000000000100000001003E9C01,
    %X00000001000000000000210000200FD0,
    %X3FFFFFFF2000174E003DC968003E9324,
    %X003DC9680018849A000004FC00200EC0,
    %X00000000003DCB96A5EDD8D200000001,
    %X00000007000000070000000000000000,
    %X00000107003D675E0018B61800201800,
    %X0000006400000045FFFFFFFD33E33836,
    %X100D001B000000000007002D0000DEAD,
    %X00002300001AECD00000207C00000000,
    %X00000000000000160000000200000002,
    %X00000001000000000000000100200FD0,
    %X3FFFFFFF20001780003DC96820001700,
    %X003DC9680018849A000004FC00200020,
    %X00000000003DCB96A5EDD8D200000001,
    %X00000007000000070000000000000000,
    %X00000107003D675E0018B61800201800,
    %X000000640000001FFFFFFFFD934CE95E,
    %X100D001C000000000011002D0000DEAD,
    %X00002304001AF2340000207C00000000,
    %X000000000000000000000003003E9F03,
    %X00000000000000000000210000000000,
    %X3FFFFFFF200017F0003DC96800000102,
    %X003E958C003E9B6C000004FC00201730,
    %X00000000003DCB96A5EDD8D200000001,
    %X00000007000000070000000000000000,
    %X00000107003D675E0018B61800201800,
    %X0000006400000023FFFFFFFDFC7BB7AB,
    %X100D001F000000BB6F63002D0000DEAD,
    %X00002000001B88060000100000000000,
    %X0000000000001000000084040000FFFE,
    %X002000000000FFFE0000FFFF00000000,
    %X00000000003EBFAE003EBFAE003EBF8A,
    %X003E91C620003E28000004FC002017EC )

    There is a program in note 825.* that will decode the error log.

    In this case you are seeing 3 crash codes:

    207C -> watchdog timer expired (firmware gets hung, crashes & restarts)
    1000 -> missing address in database (we are currently working on this)
     144 -> there is a fix for this problem in V1.5

    
    
    Thanks very much for the info.
    Could you clarify if the crash code 1000 is the same problem that was
    reportedly fixed in V1.5.
    
    
    From the V1.5 release notes
    
    14)   Unsolicted resets caused by repeatedly issuing SNMP requests to
    read the forwarding address database.  The crash code in the error
    log ranged from 1000 (hex) to 1005.
    
    The customer is running V1.3.
    
    Thanks again
    
    Jim
       

    Jim, yes, V1.5 will fix your crash for code 1000 but from what I have
    seen at a very *few* sites, there maybe another problem, which we are
    currently working on.  only for the 6xx bridge.
    ken

    Thanks for the info.
    
    The customer is now happy to upgrade.
    
    
    cheers Jim