[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

2546.0. "DEChub 900 TRAP info" by CSC32::DECKER () Thu Jul 20 1995 16:50

    Customer has a DS900 which he is trying to connect to the OBM port of
    a DEChub 900. The LED display is showing a 
    
    TRAP @ 524
    
    Further info indicates
    
    CATCH VO=0B8 SR=2700 PC=456D34
    
    Might this indicate a problem with the DS900 or the hub? I've
    looked for information on these traps to no avail. If I missed it in
    this notes file, my apologies.
    
    .Ron Decker
    MCI mission critical support
T.RTitleUserPersonal
Name		DateLines
2546.1NETCAD::DOODYMichael DoodyThu Jul 20 1995 17:4215
    	Can I assume the messages you've provided were on the Hub LCD?
        These look like a Hub firmware crash. Can't tell any more without
    	the firmware version of the Hub.   
    
    >TRAP @ 524
    
        There should more to this, like the module name : TRAP @ 524
    							    xyzblah.c
           
    >CATCH VO=0B8 SR=2700 PC=456D34
     	This is a crash.	    
    
    	Look in the Hub's error log and see what it says.
    
    -Mike
2546.2More infoCSC32::DECKERThu Jul 20 1995 17:5013
    The messages were on the hub's LCD. There is no module name after the
    TRAP. The customer was at home when he reported the problem, so will
    look at logs tomorrow morning. He had not had a chance to examine the
    logs.
    
    MAM REV 3.1
    Other modules in the HUB are
    		Decswitch 900
    		Decrepeater 90
    		Decserver 90 
    		4 Decserver 900TM	Three at V1.4
    					One at V1.3
2546.3Module is OBM.CCSC32::DECKERFri Jul 21 1995 13:201
    The customer was incorrect. The module name for the TRAP is OBM.C.
2546.4NETCAD::DOODYMichael DoodyTue Jul 25 1995 09:557
    Can I assume the hub errorlog has nothing to add here? I don't know yet
    why the hub crashed.  However, my guess it that the DECserver port was
    not configured properly - wrong speed or not set up for SLIP. Of course
    that shouldn't cause the hub to crash, we'll be looking into this
    further.
    
    -Mike