[nv-l] Problem with SNMP v2 traps with mib2trap.

[Paresh Borkar <paresh@persistent.co.in>]

Hi,

(Resending this message again since the earlier one sent on 11th April
did not appear on the mailing list.)

We are writting an SNMP agent for our application servers. Our agent
would support SNMP version 2. Our traps are not being displayed
formatted in the event browser in NetView. Following is sample trap from
our mib file

<snippet>
--
-- Traps
--
aaaTraps  OBJECT IDENTIFIER ::= { versionOne 0 }
oblixAAAServerDown   NOTIFICATION-TYPE
    OBJECTS   { aaaId, aaaHostname, aaaPort }
    STATUS    current
    DESCRIPTION "This trap is generated whenever the agent detects the
AAA server to be (potentially) down."
    ::= { aaaTraps 7001 }

oblixAAAServerStart  NOTIFICATION-TYPE
    OBJECTS   { aaaId, aaaHostname, aaaPort }
    STATUS    current
    DESCRIPTION "This trap is generated whenever the agent detects the
AAA server to have (re)started."
    ::= { aaaTraps 7002 }

oblixAAAServerFailure  NOTIFICATION-TYPE
    OBJECTS   { aaaId, aaaHostname, aaaPort }
    STATUS    current
    DESCRIPTION "This trap is generated whenever the agent detects the
AAA server has failed."
    ::= { aaaTraps 7003 }
</snippet>

The same mib, when uploaded to HP OpenView NNM works fine, in the sense
that formatted message get displayed from HP OV. The event browser in
NetView displays the trap details in a raw fashion. It does not display
the formatted string configured for the trap.

Following is the script file generated after running mib2trap.

<script>
/usr/OV/bin/addtrap -l oblixAAAServerDown -g 6 -s 7001 \
   -n aaaTraps -i 1.3.6.1.4.1.3831.10.2.1.0 \
   -o A  -c "LOGONLY" -t 0 \
   -S 1  \
   -D "This trap is generated whenever the agent detects the
AAA server to be (potentially) down."  \
   -e oblixAAAServerDown  \
   -F '$E $G $S $# args: $*'
/usr/OV/bin/addtrap -l oblixAAAServerStart -g 6 -s 7002 \
   -n aaaTraps -i 1.3.6.1.4.1.3831.10.2.1.0 \
   -o A  -c "LOGONLY" -t 0 \
   -S 1  \
   -D "This trap is generated whenever the agent detects the
AAA server to have (re)started."  \
   -e oblixAAAServerStart  \
   -F '$E $G $S $# args: $*'
/usr/OV/bin/addtrap -l oblixAAAServerFailure -g 6 -s 7003 \
   -n aaaTraps -i 1.3.6.1.4.1.3831.10.2.1.0 \
   -o A  -c "LOGONLY" -t 0 \
   -S 1  \
   -D "This trap is generated whenever the agent detects the
AAA server has failed."  \
   -e oblixAAAServerFailure  \
   -F '$E $G $S $# args: $*'
</script>

In the event browser, the enterprise is shown as "aaaTraps". However,
aaaTraps is a dummy place-holder OID, that we have defined to comply
with RFC 2578 in section 8.5 (Mapping of the NOTIFICATION-TYPE value).
We noticed that HP-OV NNM displays the enterprise properly as
"versionOne". We think that the event browser is not displaying the
formatted message for the traps because it can't correlate the incoming
trap with the proper enterprise (since the enterprise has been picked up
as "aaaTraps" instead of "versionOne").

We plan to support both HP-OV NNM and IBM Tivoli for our release. Please
let me know if I am missing something over here or there is something
else that needs to be done.

Regards,
Paresh.




---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com

*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)