[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

1179.0. "switching between communities" by VNZV01::GONZALEZ () Thu Jun 30 1994 17:50

    
    Hi,
    
    I Have installed and configured HUBWatch for VMS V2.0 succesfully, but
    I have noticed the following situation :
    
    When Hubwatch starts It loads the default community, wich in my case is
    the DECagent module running stand-alone.
    
    If I change the default community to any other one It works also 
    very well, but when I go into the Manage Table option, it comes back 
    with no agent selected, of course no community selected an it displays
    a windows saying something like "NO MIB DATA FOUND FOR...".
    
    Besides, it logs the following message in another windows, which 
    happens to open when I start HUBWatch from PNM 1.3 :
    
    "...
    (W) NO READ ACCESS TO COMMUNITY TABLE FOR COMMUNITY 'COMMUNITY-NAME'
    ..."
    
    After this I have to make de AGENT the current agent, wich opens by
    default againg the Agent community and choose the community I wanted to
    switch to.
    
    Maybe, it is the way it should happen or I forgot something very basic
    here, but that makes it difficult to switch between communities.
    
    Ideas will be appreciated
    
    Regards,
    
    Richard
    
    PS: Of course, I can go to all and every one of the communities
    following the procedure I described, so I don't see any problems with
    the read-only or read-write strings.

T.R Title User Personal
Name Date Lines

1179.1 that's the way it's designed to work. SLINK::HOOD I'd rather be at the Kennebec Thu Jun 30 1994 18:32 11

T.R	Title	User	Personal Name	Date	Lines
1179.1	that's the way it's designed to work.	SLINK::HOOD	I'd rather be at the Kennebec	`Thu Jun 30 1994 18:32`	11
	It works exactly as it's supposed to. The default DECagent 90 community has read access to each of the other DECagent 90 communities. None of the non-default DECagent 90 communities has read access to any other community. btw, the shipping version of HUBwatch for OpenVMS is V3.0. Tom Hood HUBwatch

It works exactly as it's supposed to.

The default DECagent 90 community has read access to each of the other
DECagent 90 communities.  None of the non-default DECagent 90 communities
has read access to any other community.


btw, the shipping version of HUBwatch for OpenVMS is V3.0.

Tom Hood
HUBwatch