Conference netcad::hub_mgnt

1938.0. "Terminal servers and Hubwatch Questions" by WKRP::HENRY (A hard-nosed, Displaced Yankee, in OHio) Thu Jan 26 1995 10:59

I am looking for some assitance on the correct way to add terminal
servers so Hubwatch can manage them.  There are a couple of questions at
the bottom of this note that I am hoping to get answered.

Envirnonment:
Hubwatch for VMS 3.1 and Hubwatch for Windows 3.1
All microcode is at current published rev.

4 -    DEChub 900
       mixtire of server 900tm's & repeater 900tm's

9 -     DEChub 90's
       2 Agents for all of theses hubs
       All hubs that do not have an agent have DECbridge 90FL's
       Combination of 90 TL servers and 90T repeaters


 
For the DECserver 900TM's, from reading the documentation I have followed
the following steps:

     - MOP into the server 
     - assign an IP address 
     - enable SNMP - enable SET's 
     - In hubwatch add server under manage table and define this device 
       as "Terminal Server"

This process works without any problem and I can manage my 900 servers from
within Hubwatch 

For the DECserver 90's however, if I follow the >same< procedure, the
servers that are in the hub with the agent work fine but about most of
the servers that are not in the hub managed my an agent cannot be seen
within the hub (though I can click on the server manually to manage it.)

QUESTIONS----

Under configuration menu there is a plaice to add modules into the HUB,
one of the options is a 90TM if I do this Hubwatch complains of an
"internal Error" Why is this available if I cannot do it?  What is this
for?  How and when is this add used?

Do I need to enable SNMP on the 90TM's like I do on the 900's to be able
to manage them?  I thought that is what the bridge was for?  If I do not
need to turn on SNMP on the 90's how to I add/manage and see the modules
in the hub.

On Hub 90's that do NOT have an agent in them, does the community string
for the Servers in one of these HUB's have to match the read/Write
community that was set up when you defined the New community of an agent?

What are the limits of the Agents ability to manage 90 hubs?  i.e how many
hubs/modules can it manage?

Thanks a lot for any help! I am sorry if this is explained in the
manuals but I could not find it .....REALLY!!!!

Gary

The following DECservers must have their own IP addresses assigned and they
must have SNMP enabled to be manageable through HUBwatch:
	DECserver 900GM, DECserver 900TM, DECserver 90TL, DECserver 90M
A DECagent 90 is not required to manage any of these modules.
If you are running NAS in those servers, the community name must be PUBLIC,
although a recent change to NAS allows it to be other than PUBLIC and still
work in a DEChub.  I don't know which NAS version allows this, nor do I know
if it is a released version yet.

The following DECservers require a DECagent 90 to be managed:
	DECserver 90L, DECserver 90L+
You must also add those servers to your HUBwatch agents file with the
following format:
	- name of DECagent 90
	- IP of DECagent 90
	- Community of DECagent 90 containing the server
	- MAC of the server.
If you have a DECserver 90L or an older DECserver 90L+, you must manually
add that DECserver to your hub through HUBwatch's "Add Module" window, because
they are not autodiscovered.

This is all documented in the HUBwatch Installation and Configuration manual.

Tom Hood
HUBwatch

And as for the DECagent's capabilities, you can manage 16 communities containing
up to 64 modules with a single DECagent, so you are certainly not pushing the
limit by having two DECagents manage your nine DEChub 90s.

...Roger...