the Trap receiver does not support SNMPv2 traps, only SNMPv1 traps.
http://www.ietf.org/rfc/rfc1908.txt
2.2. Trap Definitions
...
(5) The value of an invocation of the NOTIFICATION-TYPE macro is an
OBJECT IDENTIFIER, not an INTEGER, and must be changed accordingly.
Specifically, if the value of the ENTERPRISE clause is not 'snmp'
then the value of the invocation is the value of the ENTERPRISE
clause extended with two sub-identifiers, the first of which has
the value 0, and the second has the value of the invocation of the
TRAP-TYPE.
e.g.
bgpBackwardTransition NOTIFICATION-TYPE
OBJECTS { bgpPeerLastError,
bgpPeerState }
STATUS current
DESCRIPTION
"The BGPBackwardTransition Event is generated
when the BGP FSM moves from a higher numbered
state to a lower numbered state."
::= { bgpTraps 2 }
bgptraps != snmp
so the SNMPv1 trap BGP4-MIB:bgpTraps.2 (bgpBackwardTransition) becomes the SNMPv2 trap BGP4-MIB:bgpTraps.0.2 (bgpBackwardTransition )
