[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

281.0. "Agent 1.1 make bridge not hub manager" by GIDDAY::DRANSFIELD (Mike Dransfield, Sydney RSSG) Wed Jun 23 1993 01:14

    What is going on with V1.1 DECagent code?
    
    I just tried the FT1.1-2 with a DECbridge 90 BL 3.0 (and 3.1) and
    when you plug the agent in the hub, suddenly the DECbridge thinks it
    isn't the bus master any more and you can't manage any repeaters!
    
    Since I didn't get a response to my note asking when V1.1 DECagent was
    going to ship, I take it that everyone is busy trying to make this
    stuff work. This is a good thing, because I am getting beaten to death
    by customers who want to manage their hubs.....:-)
    
    thanks,
    Mike
T.RTitleUserPersonal
Name		DateLines
281.1Try released codeNAC::SEAVERBill Seaver, HUBwatch MktgMon Jul 05 1993 19:134
    If you still have this problem with V1.1 (see
    NAC::MANAGMENT:AGENT_LOAD.TXT) contact LEVERS::GALVIN and
    LEVERS::BENSON.  I think there are some special isntructions about how
    to insert an agent into a working hub, but I'm not the expert here.
281.2wrong pointer, problem seen with 1.1?LEVERS::BENSONDTN 227-3555Fri Jul 16 1993 12:0718
    The pointer should be: NAC::MANAGEMENT:AGENT_LOAD.TXT.
    
    If anyone experiences this sort of behavior with V1.1, I would like to
    know about it.  Please send mail to LEVERS::BENSON and include as much
    specific information as possible including sequence of operations, etc.
    
    The solution to such behavior would be to perform a factory reset.
    
    We know that it is possible to induce an inadvertant factory reset by
    plugging the DC power cord into the DENMA AFTER applying AC power to
    the supply.  (We placed a warning in the V1.1 release notes that AC
    should be applied LAST.)  It is possible that this could also cause a
    partial corruption of the non-volatile RAM, which could account for the
    behavior described in the base note.  So be careful when using those
    stand alone supplies with DENMAs.
    
    Dave.
281.3Got the same problemNBOFS1::HKLEINHermann Klein "strangers in the art"Sat Sep 26 1992 05:2426
The scenario:

There are three hubs in that Network.
each one has a DB90, one has an agent in slot 7.

The Agent was shiped with SW V1.0.
And we got problems to manage the repeaters of one remote Hub.
So I did the Upgrate to SW V1.1 of the Agent.

It worked the remote hub's Repeaters were manageble,
but a new problem occured, the bridge nearest to the hub timed out on
doubleclick. Connecting to the bridge console showed that the bridge is not 
the hubmanager. The Hub manager enable switch is set to 1, I think that is
enable.

Now we are going to perform a factory reset.

Here are the Versions.

Agent: HW 001; ROM BL05.00; SW V1.1
DB90 (nearest to the Agent Slot 8):	V1.14; Fprom 3.0
DB90 ( out inthe Hubs)			V1.0 ; Fprom 3.0

Hope the factory reset will work.

Ciao Hermann
281.4Re .3 Factory reset solved the problemNBOFS1::HKLEINHermann Klein "strangers in the art"Mon Oct 04 1993 08:080