RE: -v 1 traps

Upon re-reading the tutorials, I see that the original net-snmp tutorial
set does include the destination address immediately after the common
parameters. I think I'm doing it correctly, but obviously I'm not.

Here are the pertinent portions of my MIB:

DELL-RAC-MIB DEFINITIONS ::= BEGIN
     
  IMPORTS
     enterprises
        FROM SNMPv2-SMI
     OBJECT-TYPE
        FROM SNMPv2-SMI
     TRAP-TYPE
        FROM RFC-1215;
[snip]
        dell                          OBJECT IDENTIFIER ::= {
enterprises    674   }
        server3                       OBJECT IDENTIFIER ::= { dell
10892 }
        drsOutofBandGroup             OBJECT IDENTIFIER ::= { server3
2     }
[snip]
        drsCMCAlertGroup              OBJECT IDENTIFIER ::= {
drsOutofBandGroup    20 }
        drsChassisAlertVariables      OBJECT IDENTIFIER ::= {
drsCMCAlertGroup     10 }
        drsChassisAlertGroup          OBJECT IDENTIFIER ::= {
drsCMCAlertGroup   2000 }
[snip]
            alertCMCTestTrap  TRAP-TYPE
                ENTERPRISE 	  drsCMCAlertGroup
                DESCRIPTION   "The CMC has generated a test trap"
                --#TYPE "CMC Test Trap"
                --#SEVERITY INFORMATIONAL
                --#CATEGORY Error Events
               ::= 2000
[snip]
END

Please see the first message for my call. Thanks for any pointers or
two-by-fours!
--
Don Wilde                           512-723-8255
Dell, Incorporated         Austin, Texas, USA


-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of
[email protected]
Sent: Thursday, July 12, 2007 6:33 PM
To: [email protected]
Subject: -v 1 traps


Hi, all -

I'm running into some problems with -v1 traps.

>From my reading, the man page for snmptrap is incorrect.

I've gotten it to send traps with:

    # snmptrap -v 1 -c public \
                        {dest IP}:162 \
                        {ent oid} \
                        {agent IP} \
                        6 \
                        2000 \
                        ''

... but all I can do is get it to show up in -d dumps, not the decoded
traps, and I also can't get it to show up at all in MG-soft's
browser/trap ringer console.

A 2000 trap is defined properly (with no varbinds) in our MIB as
.1.3.6.1.4.674.10892.2.20.2000, and the e-oid I'm using is
.1.3.6.1.4.674.10892.2.20.

Before I switched to -v 1 traps, I could see the decoded trap in -v 2c
format, but we need to support legacy systems which only support -v 1.
What am I missing? The man page doesn't even mention a destination IP,
but it didn't work until I added it in  that location.

Any ideas?

TIA!
--
Don Wilde                           512-723-8255
Dell, Incorporated         Austin, Texas, USA


------------------------------------------------------------------------
-
This SF.net email is sponsored by DB2 Express Download DB2 Express C -
the FREE version of DB2 express and take control of your XML. No limits.
Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users