[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

2569.0. "DECagent 90 Clarification ?" by GIDDAY::STANISLAUS () Thu Jul 27 1995 08:36


 	Confusion on the 16 community issue with the decagent90.
 	--------------------------------------------------------

Say we have a LAN segment with 10 dechub90s on it and a bridge in every hub bar
the one with the decagent90, how do we map the community names generated in the
decagent with the relevant hubs , ie, if I say to the decagent that we have a
community name of "hub10" how does the decagent know which hub I am addressing?

Alphonse
T.RTitleUserPersonal
Name		DateLines
2569.1It's just a Memory location pointerMSDOA::REEDJohn Reed @CBO = Network ServicesThu Jul 27 1995 12:5111
    The agent really does NOT know which hub you are addressing.  I think
    of it as giving the agent a "nonsense" random ascii string of "HUB10" to
    identify a different memory location.
    
    The DECagent will then assign an empty HUB picture for you to populate.
    Once you populate the first DECBRIDGE90 into the hub, (either slot 7 or
    8) then the DECagent will POLL that bridge, and if you are patient you
    will see the modules in that hub begin to populate themselves on your
    screen.
    
    JR