[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

3219.0. "900TM fatal error line 334 file srv.c" by KERNEL::GRIFFITHSJ () Wed Jan 31 1996 10:10

    
    Hello
    
    
    I have a customer who has a problem with Decrepeater 900TM's resetting.
    There are five 900TM's in a hub with a 900EF. Nodes on the repeaters
    lose
    network connectivity. The error log dump for all the 900TM's show
    fatal error line 334 file srv.c at similar but not identical time
    stamps.
    The 900ef does not seem to be affected and the Hub also appears to be
    OK.
    The versions are as follows:-
    900TM  HW V3  R0 V01.04 SW V2.0.0
    900EF  sw v1.5.2
    Hub V4.1.0
    
    The customer upgraded to these versions 4 days ago and has had the
    problem
    four times since then but he also had the problem before the upgrade. I
    don't
    know what versions he was running before.
    The 900TM's are each connected to its own ethernet segment in the
    backplane.
    The 900EF is also connected to each backplane ethernet. The FDDI ports
    are not
    in use yet.
    Only one of the 900TM's has an IP address set.
    
    Can some one decypher the error log entry??
    
    
    Thanks Jim
    CSC
    Basingstoke
    
T.RTitleUserPersonal
Name
DateLines
3219.1Cross ReferenceLEVERS::HERTZBERGHistory: Love it or Leave it!Thu Feb 01 1996 11:264
    Not an answer, but a cross reference.  Note 3136 described a situation
    where repeaters were reporting the same error as these are.
    
    							M
3219.2Now an IPMTKERNEL::GRIFFITHSJThu Feb 15 1996 05:5712
    Thanks Marc
    
    
    I did check out 3136 and have asked the customer to give the 900ef and
    repeaters an IP address and they have had no crashes since but it may be
    too early to tell if this is significant.
    The problem has now been logged as an IPMT.
    
    
    
    Thanks again                             
    Jim