[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

2306.0. "Unsupported agent type error message" by ISIDRO::AMBROSIO () Tue May 23 1995 03:46

Hello,

I'm in a customer and i'm just having problems between HUBwatch and a
BRrouter 90 T2. When Trying to manage a DEC Brouter 90 T2 in Stand-alone
i got an "unsupported agent" error message.

Versions:
VMS 5.5-2
HUBWATCH 3.1.3
BRouter 90T2	6140K/2048K, Version 10.0(6),
		Release Software (fc1)

Error Message:
(E) Unsupported agent type at 15.228.20.1 (sysObjectID= 1.3.6.1.4.1.9.1.10) 

Comments:
1.- The Brouter is in Stand-Alone and i defined it in the Community Table this way:

		IP Address		15.228.20.1
		Agent Name		bvrou2	
		Community 		public
		Timeout			5
		Retries			2
		MAC Address		08-00-2B-2B-72-C6
		Comments		--
		Agent Type		Brouter

2.- In the LAN there is another Brouter 90 T2 but mounted in a HUB90 (in which there
is a DECAgent 90 ) and with different Software version (9.14). It is deffined in the 
Community Table in the same  way as the above. But the difference is that it is Manageable
through the DECAgent 90 (managing the Hub) or invoking directly the Brouter.


QUESTIONS:

1.- Is there a PROBLEM  or it simply shuldn't work because it is not a supported
configuration?

2.- Would be the problem the Software version ( 9.14 VS 10.0) or because the Brouter
is in Stand-Alone?

I am new in HUBwatch that's why the questions. Thanks in advance for your help.


Best regards,
Juan Andr�s.
IM&T Spain.

T.R Title User Personal
Name Date Lines

2306.1 Fixed in HUBwatch V4.0 SLINK::HOOD Maine state bird: The black fly Tue May 23 1995 11:16 8

T.R	Title	User	Personal Name	Date	Lines
2306.1	Fixed in HUBwatch V4.0	SLINK::HOOD	Maine state bird: The black fly	`Tue May 23 1995 11:16`	8
	That is fixed (as of yesterday) in HUBwatch V4.0. Cisco was nice enough to change the sysObjectID when they changed firmware versions. The work-around is to manage it as part of a hub. In a hub, the DENMA and the MAM see that it is a DECbrouter, so it returns the older sysObjectID. Tom Hood HUBwatch

That is fixed (as of yesterday) in HUBwatch V4.0.  Cisco was nice enough to
change the sysObjectID when they changed firmware versions.

The work-around is to manage it as part of a hub.  In a hub, the DENMA and
the MAM see that it is a DECbrouter, so it returns the older sysObjectID.

Tom Hood
HUBwatch