Good morning !
I just configured my switches to do SNMP with an OV2500.
switch side:
aaa local snmp authentication
user snmp-omnivista read-write all password PASSWORD sha+des
snmp station 172.31.0.113 snmp-omnivista v3 enable
snmp authentication-trap enable
OV2500 side:
Discovery Profiles > new profile “snmp-discover” in SNMPv3 with CLI/FTP login/password + username “snmp-omnivista” + protocol SHA+DES with 4 times “PASSWORD” (Auth+Priv)
.
from the first detection all the switches are reassembled in the OV and the CLI scripting > terminal works
.
but I have a lot of “authenticationFailure” alerts:
Trap OID: .1.3.6.1.6.3.1.1.5.5
Synopsis: Authentication failed
Description: An authenticationFailure trap means that the SNMPv2 entity, acting in an agent role, has received a protocol message that is not properly authenticated. While all implementations of the SNMPv2 must be capable of generating this trap, the snmpEnableAuthenTraps object indicates whether this trap will be generated.
.
I obviously checked the password.
An idea ? 
Thanks in advance
Check the advanced settings of the discovery profile in OV2500 and disable the Use GetBulk option?
thank you for your help.
I entered “snmp-omnivista” for Trap Station User Name and deactivated GetBulk. Unfortunately that doesn’t change anything. I’m not very familiar with SNMP… isn’t there a config problem on the switch side?
what switch model are you using?
6900, 6560 et 6360 in version 8.9R04
This is a new installation
You have specified the option snmp authentication-trap enable which means that a trap is sent whenever some process uses snmp and authentication fails, hence the alerts. You would have to check the Trap OID in the MIB file to find out which process is causing the traps and if it can be ignored. You said that you are not familiar with SNMP. I would disable the snmp authentication-trap option. There does not seem to be anything wrong with the snmp configuration. I don’t know the rest of the configuration or requirements so cannot advise on that.
This is a good idea from wifi113, and to add to this, I believe if you add the command
snmp authentication-trap mode private
it will also show you what IP address is failing the login
