Hi all,

Some additional information relating to this.

If I do:

# snmptranslate -m ALL -T l | grep cabletime | grep -i started

I get:

.iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).cabletime(5838).
cabletimeTrapGroup(2).cabletimeTraps(1).evoTraps(10).evoEndpointTraps(1).evo
EndpointTraps#(0).endpointStarted(1)

Where is the 'evoEndpointTraps#' bit coming from?

Andy

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of Andy
> Hawkins
> Sent: 15 December 2005 11:31
> To: [email protected]
> Subject: Traps fired with wrong OIDs
>
>
> Hi,
>
> We've just started using net-snmp to fire traps from an
> embedded device
> we're developing. However, when we fire a trap (using
> snmptrap) the OID that
> is received by the manager appears to have a couple of extra
> elements that
> we're not expecting.
>
> The relevant sections of the MIBs are below (I can provide
> full copies of
> them if necessary):
>
> -- cabletime.mib --
>
> CABLETIME-MIB DEFINITIONS ::= BEGIN
>
>
> IMPORTS
>       enterprises
>               FROM RFC1155-SMI
>       OBJECT-TYPE
>               FROM RFC-1212;
>
>
> -- CORE STUFF
> cabletime                             OBJECT IDENTIFIER ::= {
> enterprises 5838 }            -- 1.3.6.1.4.1.5838
>
> cabletimeDevices              OBJECT IDENTIFIER ::= {
> cabletime 1 }                 -- 5838.1
>
>
> -- TRAPS
> cabletimeTrapGroup            OBJECT IDENTIFIER ::= {
> cabletime 2 }                 -- 5838.2
>
> cabletimeTraps                        OBJECT IDENTIFIER ::= {
> cabletimeTrapGroup 1 }        -- 5838.2.1
> cabletimeGenericTraps OBJECT IDENTIFIER ::= { cabletimeTraps
> 1 }           --
> 5838.2.1.1
>
> cabletimeTrapVars             OBJECT IDENTIFIER ::= {
> cabletimeTrapGroup 2 }        --
> 5838.2.2
> cabletimeGenericTrapVars OBJECT IDENTIFIER ::= {
> cabletimeTrapVars 1 } --
> 5838.2.2.1
>
> -- VARIABLES
> cabletimeVars                 OBJECT IDENTIFIER ::= {
> cabletime 3 }                 -- 5838.3
> cabletimeGenericVars  OBJECT IDENTIFIER ::= { cabletimeVars 1
> }             -- 5838.3.1
>
>
> -- cabletime_evo.mib --
>
> CABLETIME-EVO-MIB DEFINITIONS ::= BEGIN
>
> IMPORTS
>       cabletime, cabletimeVars, cabletimeTraps, cabletimeTrapVars
>               FROM CABLETIME-MIB
>       enterprises
>               FROM RFC1155-SMI
>       OBJECT-TYPE
>               FROM RFC-1212;
>
>
> evoVars               OBJECT IDENTIFIER ::= { cabletimeVars
> 10 }  -- 5838.3.10
> evoTraps      OBJECT IDENTIFIER ::= { cabletimeTraps 10 }
> -- 5838.2.1.10
> evoTrapVars   OBJECT IDENTIFIER ::= { cabletimeTrapVars 10 }
> -- 5838.2.2.10
>
>
> END
>
> -- cabletime_evo_endpoint.mib --
>
> CABLETIME-EVO-ENDPOINT-MIB DEFINITIONS ::= BEGIN
>
> IMPORTS
>       evoVars, evoTraps, evoTrapVars
>               FROM CABLETIME-EVO-MIB
>       enterprises
>               FROM RFC1155-SMI
>       OBJECT-TYPE
>               FROM RFC-1212;
>
>
> evoEndpointVars               OBJECT IDENTIFIER ::= { evoVars
> 1 }   -- 5838.3.10.1
> evoEndpointTraps      OBJECT IDENTIFIER ::= { evoTraps 1 }
> -- 5838.2.1.10.1
> evoEndpointTrapVars   OBJECT IDENTIFIER ::= { evoTrapVars  }
> -- 5838.2.2.10.1
>
>
> -- VARIABLES
> evoEndpointUpdate OBJECT-TYPE
>       SYNTAX INTEGER
>       ACCESS read-only
>       STATUS mandatory
>       DESCRIPTION
>               "The number of seconds this endpoint has been running"
>               ::= {evoEndpointVars 1}
>
>
> -- TRAP VARIABLES
>
> evoEndpointUnitNumber OBJECT-TYPE
>       SYNTAX INTEGER
>       ACCESS read-only
>       STATUS mandatory
>       DESCRIPTION
>               "The unit number"
>               ::= {evoEndpointTrapVars 1}
>
>
>
> -- TRAPS
>
> endpointStarted TRAP-TYPE
>       ENTERPRISE evoEndpointTraps
>       VARIABLES { evoEndpointUnitNumber }
>       DESCRIPTION
>               "The Evo Endpoint has started"
>               ::= 1
>
> END
>
> ----
>
> When I fire the 'endpointStarted' trap using the following
> command line:
>
> snmptrap -M /usr/share/snmp/mibs -d -v 1 -c public -m ALL 191.53.51.21
> endpointStarted 191.53.22.22 36 1 '' 'evoEndpointUnitNumber' 'i' '5'
>
> I would expect a trap to be fired with the OID
> 1.3.6.1.4.1.5838.2.1.10.1 and
> a trap number of 1
>
> However, we actually get a trap fired with the OID
> 1.3.6.1.4.1.5838.2.1.10.1.0.1 and a trap number of 1.
>
> Can anyone explain why the extra '.0.1' is being put into the OID?
>
> Thanks for any help you can provide, and I can obviously give more
> information if requested.
>
> Andy
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep
> through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.
> DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> _______________________________________________
> 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: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
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

Reply via email to