Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > Security access violation from xx.xx.xx.xx for the community name or user name

Security access violation from xx.xx.xx.xx for the community name or user name

Created by Malik Haider, last modified by Aileen de Lara_ret on Jul 01, 2016

Views: 1,653 Votes: 2 Revisions: 4

Updated July 1, 2016


This article provides brief information and a resolution to the issue when you have noticed the Orion server is sending in correct SNMP community string to the devices and been rejected by the device with below message:

Security access violation from Orion_IP_ADDRESS  for the community name or user name : abcd@1  



When you checked in Orion, you have not entered any @sign in SNMP community string in the node, however, you are unsure why the @ sign is sent by the Orion.





All Orion Core products



Since you are monitoring VLAN for this device, the root cause is that VLAN has been selected for monitoring.


The @ symbol is used as a delimiter between the community string and the context in which it is used. For example, specific VLAN information in BRIDGE-MIB may be polled using community@VLAN_ID (for example, public@100) where 100 is the VLAN number. Avoid using the @ symbol as part of the SNMP community string when configuring this command.


Cisco has more information about Community String Indexing:


Some standard MIBs assume that a particular SNMP entity contains only one instance of the MIB. Thus, the standard MIB does not have any index that allows you to directly access an instance of the MIB. In these cases, a community string indexing is provided to access each instance of the standard MIB. The syntax is [community string]@[instance number].


If you use @ in your community strings, you might find that the switch gets confused about what you’re trying to poll. You won’t be able to get data for any VLAN other than 1, and you’ll probably find that you get SNMP authentication failure traps from your managed devices.



Go to the Node page > List Resources > Uncheck the VLAN.





Correct the issue into the device to allow the VLAN access to monitor with same community string so you do not have such violation alerts.


Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment.  You elect to use third party content at your own risk, and you will be solely responsible for the incorporation of the same, if any.



Last modified