Hi,
I guess that the SNMP query of your tool tries to connect with another community name. SNMPv3 only is not really necessary.
What does your configuration look like?
Example:
snmpv3 engineid "xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx:xx"
snmpv3 enable
snmpv3 group managerpriv user "TestUser" sec-model ver3
snmpv3 user "TestUser" auth sha "xxxxxxxxxxxxx" priv aes "xxxxxxxxxxxxxxx"
Cheers
Original Message:
Sent: Jun 28, 2022 04:58 AM
From: John Brines
Subject: Setting up SNMPv3 on 2530
Hi Guys,
I have followed Document - 16.10 Aruba 2530 Management and Configuration Guide for ArubaOS-Switch 16.10 | HPE Support to setup SNMPv3 but I am getting "Security access violation from xx.x.x.xxx for the community name or user name : " whenever I setup our Management software (Forescout) to connect to it.
When I use v2C it works
I have added the forescout server as a trap server.
The only difference I can see is that Forescout uses HMAC-MD5 instead of just MD5.
Cheers