[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

719.0. "Agent 2.0, Bridge 90 - can't manage?" by WOTVAX::64021::Tim_Banks (Stealth Marketing :-)) Thu Feb 10 1994 10:55

	I am having a problem managing a DECbridge 90 in a HUB 90 with a 
T2.0.2 Agent 90.  With HUBwatch 2.0.1 VMS, when I click on the bridge I get a 
message in the startup window

	(E) Failed to get IF Interface

From the port on the agent, when I show community option 13 I see all the 
modules, but the bridge is flagged as unreachable.

I have tried toggling the bridge parameter

	set bridge hub_management enable

	but it made no difference, enabled or disbaled.

Any suggestions?

Also, with the 2.0 agent, how do you tell it to manage a remote hub with a 
bridge in?

	Thanks
		Tim
T.RTitleUserPersonal
Name		DateLines
719.1Can you upgrade? I can't reproduce the problem.ROGER::GAUDETBecause the Earth is 2/3 waterThu Feb 10 1994 12:4513
First, T2.0.2 is quite old.  T2.0.10 is the latest.  The kits are available on
QUIVER::PROJ$722:[ONEHUB.RELEASE.DENMA.T2_0].  Please upgrade to this version
and tell us if you are still having a problem.

Second, you should be able to add a remote community with a bridge in it the
same as you always have.  The one thing that will be different with 2.0 agents
is that they default to being the hub master, so if a remote community has a 2.0
agent in it the bridge will not be the hub master.  You have to turn off
backplane management (console option 9) on the agent in the remote hub, then the
bridge will become the hub master and respond to the managing agent.

Roger Gaudet
DECagent 90 devo
719.2DECagent T2.0.10, missing things.CGOS01::DMARLOWEdsk dsk dsk (tsk tsk tsk)Thu Feb 10 1994 19:0017
    Roger,
    
    I finally had some time to run up Agent (Version Information  :
    HW=D01 ROM=BL05.00 SW=T2.0.10).  I had tried a pre-FT version and
    well, what can you say, not so good.  Even had trouble with T2.0.8
    or something like that.
    
    This version seems stable but there's something missing.  If you
    do not have HUBWATCH how do you go about adding things like DS90L+'s
    or DS90TL's?  What about deleting communities?  I have an old DEChub
    900 community in it prior to upgrading from V1.1.
    
    Has the DA90 console port become a setup port just like the DEChub
    900?
    
    Regards,
    dave
719.3And the reason is ......WOTVAX::STUS::Stuart HattoACB actually means A Cold BeerFri Feb 11 1994 04:5015
Hi,

I asked this same question of Bill Seaver.

As I surmised the reason why you cannot add communities
to manage remote hubs with bridges, from the DENMA console,
is a marketing issue.

You should be using Hubwatch for xxx to manage multiple 
communities.

Actually this seems reasonable to me, if not a trifle 
inconvenient to have this taken away....

Stuart
719.4V2.0.10 no differenceWOTVAX::64021::Tim_BanksStealth Marketing :-)Fri Feb 11 1994 09:2312
Back to my original note;

I upgraded to T2.0.10 no problem.  Yet the bridge FPROM V1.5 stills shows as 
unreachable.  I have the hub management disabled in the bridge, and I can 
connect to it via MOP.

The error message is the same as the one I mentioned in the base note.

Is the bridge too old?

	Thanks
		Tim
719.5The Phone is quicker than the Note!WOTVAX::HATTOSI think, Therefore I'm paid lessFri Feb 11 1994 10:155
    Tim,
    
    I have WGB V3.0 available.... I will see you about it.
    
    Stuart
719.6LEVERS::SWEETMon Feb 14 1994 14:224
    You really want V3.1 of the bridge, but 3.0 will get you off the
    ground.
    
    Bruce
719.7QUIVER::PROJ$722:[ONEHUB.RELEASE.WGB.V3_1]WGB_FLASH_V31.TSKROGER::GAUDETBecause the Earth is 2/3 waterMon Feb 14 1994 14:380