Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Network Performance Monitor (NPM) > NPM - Knowledgebase Articles > SNMP discovery with @ postfix after community string

SNMP discovery with @ postfix after community string

Table of contents
Created by Andy Ng, last modified by Karen Valdellon_ret on Jul 04, 2016

Views: 860 Votes: 0 Revisions: 3

Updated July 4, 2016

Overview

This article explains authentication errors where the community string is appending with @ at the end of the string when performing network discovery. For example, public@1.

Environment

All NPM versions

Detail

  • This behavior is expected as designed by Cisco and no changes are required to be performed.
  • Bridge MIB was designed with no support for VLANs, thus it is just a table of records without a column such as VLAN ID.
  • As a workaround, Cisco invented a technique that allows you to pass the additional context information to the agent by appending @context to the community string.
  • This is used to pass VLAN ID, so the agent is able to return VLAN-specific information that is held within the Bridge MIB.
  • Topology in Orion uses two versions of pollers: One which appends @VLANID at the back of the community string, and another which does not.
  • During discovery, Orion first tries to use the @VLANID postfix and if it fails, it will fall back to using the poller without the @VLANID.
 

 

Last modified

Tags

Classifications

Public