[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

139.0. "Agent/DOS/Versions queries!" by WOTVAX::HATTOS (I think, Therefore I'm paid less) Sat Jan 30 1993 07:50

    Hi,
    
    I have a 10Base5 network with 16 hubs, each with its own bridge. Am I
    correct in thinking that 4 DECagent 90's will be able to manage these
    16 hubs?
    
    Also on a secondary point, Hubwatch for DOS, allows me to enter the
    four decagents and their respective hubs, however how do I tell it to
    manage another hub, i.e. how do I enter this. If I add the hub and 'use
    an existing Agent' the new hub has the same configuration as the Hub
    which has the Agent. Confused? So am I!
    
    Also what is the definitive answer on what versions of Bridge and Agent
    software allow the Agent to manage the Bridge and thus the repeaters?
    
    Thanks,
    Stuart
T.RTitleUserPersonal
Name		DateLines
139.1Multiple hubs one agent, versions of code EMDS::SEAVERBill Seaver, HUBwatch MktgSun Jan 31 1993 20:1112
    1. correct 4 agents will manage 16 hubs.  Actually they could manage 16
    daisy chained hubs because it is the interaction with the bridge that
    causes most of the traffic.
    
    2. re: Managing multiple hubs with one agent.  Change the community
    string so it is different for each of the multiple hubs (or stand alone
    bridges/ servers) that you want to manage.  If this does not work, you
    have found a bug in HUBwatch.  I will also push on the manual writers
    because this is not in the HUBwatch for Windows manual.
    
    3. To manage repeaters need 3.0 of Bridge and 1.0 of Agent.  1.1 or
    agent (in field test) will manage fiber repeaters.
139.2WOTVAX::HATTOSI think, Therefore I'm paid lessMon Feb 01 1993 11:046
    Thanks Bill,
    
    I will try the community string thing and get back to you!
    
    
    Stuart
139.3bug in adding extra hubs to 1 agent in HUBwatch for WindowsMEMIT::FORRESTThu Feb 18 1993 09:276
	Stuart, a bug in HUBwatch (through Beta4 anyway) keeps you from 
	adding anything to an existing agent. We are about to test Beta5 
	to see if the fix is in there - we've been waiting and waiting ...

	jack
139.4DECrepeater FA and agent version?HGOVC::LILLIANTANGThu May 27 1993 02:593
    re .1)  .3 - agent 1.1 required for managing  fiber modules -
    does this include the DECrepeater FA with the fiber port being used?
    thanks
139.5need 1.1EMDS::SEAVERBill Seaver, HUBwatch MktgWed Jun 02 1993 23:142
    agent 1.1 is required to manage fiber modules including the FA with
    fiber port being used.