I followed all the required steps :
. Creating a Remote Engine ID : remote IP address / remote host Engine ID
. Creating a SNMPv3 group, like when using SNMPv3 traps
. Creating a SNMPv3 user and make it use our remote Engine ID
. Finally setting the SNMPv3 recipient, like with SNMPv3 traps. The only difference here being that we choose 'Informs' instead of
'Traps'.
There seem to be some problems with the SG-300 10 SNMPv3 informs.
First, the SNMPv3 informs seem to be sent quite erratically. Sometimes, they are sent when rebooting only, no SNMPv3
informs for authentication failures or config save.
Secondly, the SNMPv3 informRequest seem malformed. If they are sent, they
look like this ( Wireshark sample ) :
----------------------------------------------------------
Simple Network Management Protocol
msgVersion: snmpv3 (3)
msgAuthoritativeEngineID: <MISSING>
msgAuthoritativeEngineBoots: 0
msgAuthoritativeEngineTime: 0
msgUserName:
msgAuthenticationParameters: <MISSING>
msgPrivacyParameters: <MISSING>
-----------------------------------------------------------
I tested with the three SNMPv3 security levels ( noAuthNoPriv, AuthNoPriv, AuthPriv ) : same problem
I tested with SNMPv2 informs or SNMPv3 traps : functions OK
( I checked my SNMP receiver, it works OK. )
Somebody to confirm or refute the problem ?
