Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Network Performance Monitor (NPM) > 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 on Jul 04, 2016

Views: 35 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
20:20, 3 Jul 2016

Tags

Classifications

Public