Conference netcad::hub_mgnt

    This is an incomplete error log dump that the customer has
    provided. The complete error log entry must be provided in
    order to analyze it. A complete error log entry looks like
    the following;
    
    
    Entry #       = 1
    Entry Status  = 0   [0=valid, 1=write_error, 2=invalid, 3=empty, 4=crc_error
    Entry Id      = 1
    Firmware Rev  = 2.3
    Reset Count   = 99
    Timestamp     =    0    0    0
    Write Count   = 34
    FRU Mask      = 2
    Test ID       = 730
    Error Data    = SR=0002 PC=050300DA Error Code=00000000 ProcCsr=0000
    
                     0:00000002  1:050300DA  2:00000000  3:0000166C
                     4:00000000  5:00000000  6:00000000  7:00000000
    Dump another entry [Y]/N?
    
    The Test ID and things like the rev of firmware being used are also
    important.
    
    Bob

    
    Bob,
    
    Sorry for the lack of info. Below I explain what the customer has seen
    and the full error log:-
    
    Dechub900 Chassis (FW 4.2)
    7* Portswitch
    1* Decswitch 900EF (FW 1.7)
    The EF is bridging all 6 flexible LANs and the thinwair segment.
    All the Portswitch modules are connected to the dedicated flexible
    backplane LANs, 4 on individual segments, 2 * sharing 1 segment and 1
    connected to the thinwire.
    
    Symtoms:
    
    The problem was reported as loss of lan connectivity from certain users
    when trting to connect Novell/NT and 3.11 clients to servers.
    
    Connectivity was tested using 'ping' which showed that the EF was not
    forwarding frames on the 3 of the backplane segements.
    
    Checking the leds on the front of the EF showed that the module has
    reset itself during the night and had failed its powerup selftest. The
    LEDs showed that the EF was not forwarding on the first 3 flexible
    backplane LANs (including the thinwire).
    Checked the backplane connectivity using MCM, this showed all backplane
    LAN connections intact.
    Replaced the EF with an onsite spare and reconnected all lan segments
    which solved the problem.
    Inserted the outswapped EF into a test hub. The EF took over 35mins to
    go all its powerup self tests and the self test LED was still flashing.
    Issued a reset a reset to the module but this did not change the
    symtoms.
    
    
    Error log.
    
    Entry # = 1 
    Entry Status = 0 [0=valid, 1=write_error,2=invalid,3=empty,4=crc_error
    Entry Id= 1
    firmware Rev = 2.3
    Reset count= 30
    Timestamp= 0 0 0
    write count = 374
    FRU mask = 2
    Test ID =B01
    Error Data = SR=0001 PC=00000002 Error Code=00000002 ProcCsr=0000
    
             0:00000001 1:00000002 2:00000002 3:00000000
             4:00000000 5:00000000 6:00000000 7:00000000
    
    Hope this helps,
    
    Thanks,
    
    Rich

    the Test ID of B01 is a diagnostic test performed on power up
    or when the DECswitch has a warm reset performed on it.
    This diagnostic test is indicating a test failure when running 
    an internal loopback test on the Ethernet port circuitry.
    This diagnostic failure looks to be directly attributable to the 
    problems being seen by the customer's connectivity problem.
    Replacing the DECswitch is the right course of action.
    
    Bob

    Bob,
    
    Thanks for the advice
    
    Rich