[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

1473.0. "90l+ in 900" by HITEKS::PEER () Fri Sep 23 1994 12:11

    I have a 90l+ module in DecHub900 and I can see the module but I cannot
    connect to it with hubwatch. I know that in a DecHub90 you can manage the
    module with DecAgent90 without any problem. I have read the
    configuration manual and it appears to me that you need a DecAgent90 in
    the Dechub900 to manage this module. I'm not sure whether I'm reading
    this correctly or this is how it is done. Could some let me know what
    if I'm missing something. The 90l+ is at BL5.2 with V2.0. I would also
    like to say that I tried this with both Hubwatch for Windows V2.0 and
    V3.0. The error message that I'm getting back is that I don't have a
    hardware address for that slot. Any help would be greatly appreciated.
    
    Still hubbing in NJ,
    
    Regina
T.RTitleUserPersonal
Name
DateLines
1473.1DS90L+ needs to be in the agents file.SLINK::HOODI'd rather be at the PenobscotFri Sep 23 1994 13:0214
You need to add the DS90L+ to your agents file.  (Community->manage table)

Significant fields:
Agent name:	DECagent 90's name
Agent IP:	DECagent 90's IP
Agent Comm:	The DECagent 90 community containing the DS90L+
MAC address:	The MAC of the DECserver

This then ties the MAC of the DECserver with its agent's IP and community name.

Same thing applies for the DECserver 90L, DECbridge 90, and DECbridge 90FL.

Tom Hood
HUBwatch
1473.2I must hav a DecAgent90??HITEKS::PEERFri Sep 23 1994 13:096
    Thanks for the quick response...I guess the answer is that I need a
    DecAgent90 in the DecHub900. I don't have one right now. Therefore I
    can not get access the community table. Just want to make sure that I
    understand the issue correctly.
    
    Thanks Regina
1473.3A DECagent 90 is required to manage a DS90L+SLINK::HOODI'd rather be at the PenobscotFri Sep 23 1994 13:2120
You do need a DECagent 90 to manage DS90L/DS90L+/DB90/DB90FL.

You don't need the DECagent 90 in the DEChub 900. You do need it somewhere
on the LAN.  If you have four DEChub 900's, each with one or more DECserver
90L+'s, you need ONE DECagent 90 somewhere on that same LAN.

For each DEChub 900 containing one or more DS90L's DS90L+'s, DB90's, or 
DB90FL's, you need to create a unique DECagent 90 community (8-slot hub), and
then add the DS90L/DS90L+/DB90/DB90FL's to that community in the DECagent 90.

Then, for each DS90L/DS90L+/DB90/DB90FL, you need to add an entry in your
HUBwatch agents table.

The HUBwatch Installation and Configuration manual explains how to do this.
Refer to Table 3-12 (page 3-23) for more information [Assuming you have the
April version of that manual.  The newer version's table/page numbers may
vary.]

Tom Hood
HUBwatch
1473.4Same LANROGER::GAUDETBecause the Earth is 2/3 waterFri Sep 23 1994 13:238
You don't need a DECagent 90 in the DEChub 900.  But you need one on the same
LAN as the DEChub 900 (presumably in another hub or standalone).  Then you can
add the DECserver 90L+ to the DECagent 90 in a variety of ways; 1) as a
standalone device in its own community, 2) in its correct slot in the DEChub
900.  The DECagent 90 doesn't care whether or not the DECserver is in a hub,
just that it is accessible.

...Roger...
1473.5Notes collisionROGER::GAUDETBecause the Earth is 2/3 waterFri Sep 23 1994 13:253
Man oh man Tom, you're quick with that CONTROL-Z key, aren't ya!  :-)

...Roger...