[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

1146.0. "How are the trap supposed to be translated" by BACHUS::VANDENBERGHE () Wed Jun 22 1994 13:49

	Hi, 
	Trying to receive traps from decchubs90/900, the oly thing I recieved is
this:

06/22/94 9:21:09
Name: decagent90.bro.dec.com - IP: 16.183.32.38- Community:
 SNMP TRAP: vendor specific from decagent90.bro.dec.com
enterprise:[1.3.6.1.4.1.36.2.15.10.1.1]
specific  : [4]
varbind 1: 1.3.6.1.4.1.36.2.18.10.2.4.1.1 = 1
varbind 2: 1.3.6.1.4.1.36.2.18.10.1.5.1.1 = 1
varbind 3: 1.3.6.1.4.1.36.2.18.10.1.5.1.17 = 1.3.6.1.4.1.36.2.18.11.1.1.12.1.1
etc..

Does it means that HUBWATCH is not able to translate traps regarding its own
modules, and that the we have to dig into the MIB to identify the reason of the
trap.

Thanks,
Robert

T.R Title User Personal
Name Date Lines

1146.1 yes that's what it means NACAD::WILSON Wed Jun 22 1994 14:28 8

T.R	Title	User	Personal Name	Date	Lines
1146.1	yes that's what it means	NACAD::WILSON		`Wed Jun 22 1994 14:28`	8
	This has been discussed before in note 1037. In HUBwatch V3.0 you must look in the MIB (this is one way we'll get you to read them ;^) ) to translate an enterprise specific trap. Only the DECagent 90 and the concentrator implement enterprise specific traps (as discussed in other notes). Karen

This has been discussed before in note 1037.  In HUBwatch V3.0 you
must look in the MIB (this is one way we'll get you to read them ;^) )
to translate an enterprise specific trap.

Only the DECagent 90 and the concentrator implement enterprise specific
traps (as discussed in other notes).

Karen