[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

222.0. "'dead' decagents?!#@% what gives?" by GIDDAY::DRANSFIELD (Mike Dransfield, Sydney RSSG) Mon May 03 1993 03:10

    I have had a couple of DECagents go 'dead' on me.
    The first time was about a month ago and I didn't know much and got
    the hardware changed and it was fine.
    The second happened this morning and I have a bit more info.
    I was running 1.1-77 of the DECagent and started messing around with
    communities. I had three defined public, public1 and iba934. I tried to
    delete public1 from hubwatch and the agent stopped responding.
    I tried reloading 1.1-77 and 1.0 firmware and reset the agent to
    factory settings, but *nothing* would get the agent menu up on the OBM
    port. The only thing I could do was to control-I and reload new
    firmware! The DECagent itself put on the first three leds in sequence
    and then the led next to the console port flashed and all leds went
    off.
    The cycle then repeated with the first three leds coming on and then
    the console led flash and they would all go off.
    I have just got the DECagent replaced but this is not real good as it
    is a demo for a major customer (who have money to spend on decagents!)
    I am going on site again tomorrow but am nervous about what can cause
    the decagent to go into this 'dead' state.
    
    thanks,
    Mike
    P.s I had another site with HUBwatch and decagents go like a dream last
    week!
T.RTitleUserPersonal
Name
DateLines
222.1have you seen this problem with T1.1-1?EMDS::SEAVERBill Seaver, HUBwatch MktgSun Jun 13 1993 23:3358
From:	LEVERS::GALVIN       "Cheryl A. Galvin"  4-JUN-1993 17:11:27.23
To:	EMDS::SEAVER
CC:	GIDDAY::DRANSFIELD,MEMIT::FORREST
Subj:	RE: 222- Cheryl- why should this agent go dead when loading IP?


Yes, we have seen this happen on occassion.  We believe that it is a 
firmware problem.  We have look at this and hope to have it cleaned up in 
T1.1-1 (which we hope to release for testing on Monday...we are doing internal
testing this weekend), although we haven't been able to prove it.  

The only way to recover is to re-loadthe firmware using CCI (2-Step load).

Please let me know if you see this problem with T1.1-1

Thanks,
Cheryl 

=====================================
From:	EMDS::SEAVER "Bill Seaver, HUBwatch Mktg  02-Jun-1993 2145"  2-JUN-1993 21:43:19.27
To:	galvin
CC:	gidday::dransfield,SEAVER
Subj:	222- Cheryl- why should this agent go dead when loading IP?



              <<< EMDS::$1$DUA24:[NOTES$LIBRARY]HUB_MGNT.NOTE;1 >>>
                         -< Hub Management Conference >-
================================================================================
Note 222.0              'dead' decagents?!#@% what gives?             No replies
GIDDAY::DRANSFIELD "Mike Dransfield, Sydney RSSG"    24 lines   3-MAY-1993 02:10
--------------------------------------------------------------------------------
    I have had a couple of DECagents go 'dead' on me.
    The first time was about a month ago and I didn't know much and got
    the hardware changed and it was fine.
    The second happened this morning and I have a bit more info.
    I was running 1.1-77 of the DECagent and started messing around with
    communities. I had three defined public, public1 and iba934. I tried to
    delete public1 from hubwatch and the agent stopped responding.
    I tried reloading 1.1-77 and 1.0 firmware and reset the agent to
    factory settings, but *nothing* would get the agent menu up on the OBM
    port. The only thing I could do was to control-I and reload new
    firmware! The DECagent itself put on the first three leds in sequence
    and then the led next to the console port flashed and all leds went
    off.
    The cycle then repeated with the first three leds coming on and then
    the console led flash and they would all go off.
    I have just got the DECagent replaced but this is not real good as it
    is a demo for a major customer (who have money to spend on decagents!)
    I am going on site again tomorrow but am nervous about what can cause
    the decagent to go into this 'dead' state.
    
    thanks,
    Mike
    P.s I had another site with HUBwatch and decagents go like a dream last
    week!