[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

524.0. "Packetprobe traps to DECmcc" by ZUR01::SCHNEIDERR () Fri Nov 26 1993 06:17

Hello,

It seems that the RMON MIB in DECmcc is not the same one like implemented in the
Packetprobe. We can't receive the traps from the Packetprobe. So we can't create
alarm rules or notification on the different traps. 
The problem is, that in the RMON description are no traps implemented. IAre the
RMON traps from the Packetprobe90 DEC implementations? Can we copy the RMON MIB
with the traps implemented from somewhere to compile it into DECmcc?

Could someone explain the behaviour??


Roland
T.RTitleUserPersonal
Name
DateLines
524.1Traps didn't make it into rfc1271.QUIVER::GALLAGHERSun Nov 28 1993 19:2648
Roland,

I cut the following from the November-93 IETF RMON working group minutes:

>11. Page 76 of RFC 1271 refers to the Trap Document:
>   The RMON Trap Document (I-D) expired but is referred to in RFC 1271.  It
>seemed that most vendors had implemented the traps from the Trap Document and
>there seemed to be general consensus that it should be added to RFC 1271.  A
>consensus on this will be referred to the RMON mail list.

So, I expect that the PacketProbe implements the defunct traps.  

I can't find the old draft rmon trap document anywhere.  When I retrieve
draft-ietf-rmon-trap-00.txt from the archives it says:

>This Internet Draft was deleted.  For more information, send a message to
>
>        [email protected].
>

If you can't find the old definitions anywhere, and you're desperate enough,
you can start with these (warning, these are constructed from my notes, not 
from the old document):

>risingEvent TRAP-TYPE
>    ENTERPRISE     rmon      -- the oid path to 'rmon'.
>    VARIABLES      { alarmIndex, alarmVariable, alarmSampleType,
>                     alarmValue, alarmRisingThreshold }
>    DESCRIPTION    
>        "Sent when a rising event occurs."
>    ::= 1
>
>fallingEvent TRAP-TYPE
>    ENTERPRISE     rmon
>    VARIABLES      { alarmIndex, alarmVariable, alarmSampleType,
>                     alarmValue, alarmFallingThreshold }
>    DESCRIPTION    
>        "Sent when a falling event occurs."
>    ::= 2
>
>packetMatch TRAP-TYPE
>    ENTERPRISE     rmon
>    VARIABLES      -- I don't recall.
>    DESCRIPTION    
>        "Sent when a packet match occurs."
>    ::= 3

						-Shawn