[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

604.0. "Problem with different communities" by NPSS::WADE (Network Systems Support) Tue Jan 11 1994 16:42

Can I get a response to this customer query?  Thanks.
                           
    
"The HubWatch software in conjunction with an DecAgent90 and some DecBridge90
 modules can be used to manage up to four DecHubs. The DecAgent resides on the
 primary hub while a DecBridge90 module reside in each of the three secondary
 hubs.
 
 Each of these hubs are configured for different SNMP communities. The target
 hub is selected via its community name. Currently the user interface of
 HubWatch V1.1 does not allow the user to specify the community name of these
 secondary hubs. Therefore in order to manage these secondary hub, the user
 must establish a session with the primary hub and then use the Manage
 Community pull down menu to change to the secondary hubs.

 This limitation is carried over to the DecMcc interface with HubWatch.
 With DecMcc V1.3 and HubWatch V1.1, the user can only register for the
 primary hub.

 I would like to see the following functionality to be made available :

	1. To be able to register the secondary hubs.
	2. To be able to select a secondary hub and acitvate HubWatch
	   targeted towards the select secondary hub via the pulldown menu.
	3. To be able to select either a primary or secondary hub, double click
	   on the icon and launch HubWatch targeted towards the selected hub.
   
     I don't believe that having to solve this problem by either placing a
  DECAgent90 in each hub, or by launching the HubWatch application to select
  the agent and then trying to locate the Hub within the HubWatch application
  is adequate.

  In the short term we will have to duplicate registrations of the Hub equipment
  in both DECMcc and HubWatch as we need the details in DECMcc for documentation
  purpose and HUBWatch for the extra functionality it provides."

T.R Title User Personal
Name Date Lines

604.1 three points SLINK::HOOD I'd rather be surfing Tue Jan 11 1994 17:05 18

T.R	Title	User	Personal Name	Date	Lines
604.1	three points	SLINK::HOOD	I'd rather be surfing	`Tue Jan 11 1994 17:05`	18
	A few things... (1) HUBwatch V1.1 is old. Current SSB version is V2.0.1 (2) No further DECmcc work will be done by anyone from the HUBwatch team. Almost positively guaranteed. Finally, HUBwatch has always allowed the user to select the community string on the command line. For example, I have a DECagent 90 named penobs. The default community shows the DEChub 90 which contains the agent. However, penobs also has another community called "ds90lpp" which contains a DECserver 90L. To directly manage that community through the HUBwatch DCL command line... watch /agent penobs /com="ds90lpp" or the ULTRIX command line... hubwatch -a penobs -c ds90lpp Tom Hood HUBwatch devel

A few things...

(1) HUBwatch V1.1 is old.  Current SSB version is V2.0.1

(2) No further DECmcc work will be done by anyone from the HUBwatch team.
    Almost positively guaranteed.

Finally, HUBwatch has *always* allowed the user to select the community string 
on the command line.  For example, I have a DECagent 90 named penobs.  The
default community shows the DEChub 90 which contains the agent.  However, 
penobs also has another community called "ds90lpp" which contains a DECserver
90L.  To directly manage that community through the HUBwatch DCL command line...
		watch /agent penobs /com="ds90lpp"
or the ULTRIX command line...
		hubwatch -a penobs -c ds90lpp

Tom Hood
HUBwatch devel