StoreOnce Backup Storage

Storeonce 5650 Gen4 SNMP V3 SNMPV3 trap not in RFC 3416 standards

 
SOLVED
Go to solution
sergio_rolandi
Occasional Advisor

Storeonce 5650 Gen4 SNMP V3 SNMPV3 trap not in RFC 3416 standards

Hello Gents,

We are having a problem trying to use SNMPV3 trap from our 5650 G4 Storeonce.

We are using the HPE provided MIB, https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX_dc416b3c8e8449c8aaea27a3d6, see below.

It seems that messages are not formatted as for standard RFC 3412 (the same structure as SNMPV2 is used in SNMPV3) in particular:

Variable bind list, the first 2 parameters, should be sysUpTime(position 1) and snmpTrapOID (position 2).

In our case these parameters are respectively in position 7 and 3.

Someone is having the same issue or knows what's the problem or what we are doing wrong?

As usual,  best regards

MIB:

Type: MIB Version: August 2010(14 Oct 2014) Operating System(s): OS Independent   File name: D2D_SNMP_MIB.zip (7.4 KB)

 

 

1 REPLY 1
Ayaaz
HPE Pro
Solution

Re: Storeonce 5650 Gen4 SNMP V3 SNMPV3 trap not in RFC 3416 standards

Hello,

We have seen this issue where SNMP monitoring applications may not process SNMP v3 traps from a StoreOnce system due to the data being in an unexpected format.

As per RFC3412, the SNMPv3 trap uses the SNMPv2 trap PDU structure with added security.

So according to that RFC in the variable binding list the first two parameters should be 'sysUpTime' and 'snmpTrapOID'. But the trap received in 'opctrapi' is having the variables in a different order. Variable 'sysUpTime' is found as the 7th varbind and 'snmpTrapOID' is found as the 3rd varbind.

StoreOnce generated SNMP traps do not adhere to the protocol.

This is fixed in software 4.2.3 and later software versions.


I work for HPE