[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

1055.0. "Decserver900TM Community not "PUBLIC"" by KERNEL::WARDJO () Wed Jun 01 1994 11:53

    Hello,
    
    Can anyone tell me if in order to manage the DECserver 900tm from the
    hubwatch main screen the community has to be public.
    
    The reason I ask is that I have configured a hub 900 with a community
    "test" and have then set up the Decserver snmp community as "test" &
    added an entry for the agent in the agent table.
    
    When I make the agent for the Decserver current, I can manage the
    Decserver. If I try and manage the server from the Hub front menu I get
    an error saying "no response from agent". 
    
    A trace reveals that the community PUBLIC is being used - is this a
    bug? - is it fixed in V3.0.
    
    Currently running Hubwatch V2.0.1 on VMS V5.5-2, Network Access SW V1.3
    for DS900TM  BL80-27.
    
    I've searched this coinference for a reference to this but can't find
    one. I've also been trying to understand the problem discussed in 774
    and Toms explanation in 774.11.
    
    Any help appreciated,
    
    Regards,
    
    Jon

T.R	Title	User	Date	Lines
1055.1	Found the answer - public only	KERNEL::WARDJO	`Wed Jun 01 1994 12:00`	8
	Well I thought I'd just check the Hub900 conferense and there is actually an entry in there that sais you can only use the default community or manage the decserver 900 standalone. Does anyone know if V3.0 fixes this restriction? Jon
1055.2	It's a NAS bug	QUIVER::HAROKOPUS	`Wed Jun 01 1994 18:06`	6
	No V3.0 does not fix this problem since the bug is in the DECserver NAS software not in the hub manager. Regards, Bob
1055.3	any more details?	KERNEL::WARDJO	`Thu Jun 02 1994 08:12`	9
	Are there any more details on what the problem is. As far as I could see on the trace the request from hubwatch to the server was useing the community public instead of the one specified. Regards, Jon
1055.4	Gory details.	QUIVER::GALLAGHER	`Thu Jun 02 1994 09:01`	12
	The Management Agent Module (MAM) queries line cards for their communities. The queries are over the backplane channel. The MAM enters these communities is its "Chassis MIB - Entity Table". HubWatch reads the Entity Table to determine how to communicate with the line cards. No matter what the community string of the DECserver900TM is set to, it only reports community string "PUBLIC" to the MAM. The MAM therefore reports community string "PUBLIC" to HubWatch. HubWatch trustingly uses this community. -Shawn
1055.5		4678::SLAWRENCE	`Mon Jun 06 1994 10:56`	2
	There is a new release out or coming soon of NAS - you could ask in TOOK::TERMINAL_SERVERS if they've changed this.