Scribd
Upload
4 views4 pages

SNMP Suggested by Support LM

The document discusses issues with SNMP configuration leading to authentication failures and rejected credentials from the portal. It suggests checking device configurations, running specific SNMP commands, and possibly reconfiguring SNMP from scratch. The author recommends collaborating with Cisco support for further validation of the SNMP setup.

Uploaded by

mohsin.risk93
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
4 views4 pages

SNMP Suggested by Support LM

The document discusses issues with SNMP configuration leading to authentication failures and rejected credentials from the portal. It suggests checking device configurations, running specific SNMP commands, and possibly reconfiguring SNMP from scratch. The author recommends collaborating with Cisco support for further validation of the SNMP setup.

Uploaded by

mohsin.risk93
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Suggested by Support LM

1)We are seeing a bad password

So the best place to look in on the device configuration.

You could check, maybe use a "show log | inc snmp" to see if any device changes
were made

We can only see that the credentials are getting rejected from the portal.

You can also run this locally snmpwalk -v 2c -c <community string> <IP address or
hostname> 1.3.6.1.2.1.1.1.0

Can you try to double check adding the community string to the device?
(snmp.community)

It is currently inherited from the root tekscape


Which of the strings in inherited?

There are four different communities

She Suspect:

I don't have the visibility to evaluate that, we can only see that SNMP is failing to
your device. The errors show as authentication failures. And nothing in the portal
indicates it's an issue on the LogicMonitor side.
Some modules alert on No Data because a collection failure, and the metric in failure
are the same.

At this stage, you may need to work internally or with Cisco support to validate your
SNMP configuration.

She said The issue was with SNMP Config

Then, I asked her the questions below:


SFP-EB-IDF this device and SFP-EM-IDF both devices are having same config then
how could it possible that the issue was with snmp config

Fix The Problem:


There were definitely changes to the SNMP configuration for SFP-EM-IDF in the past
month.

What the changes were is hard to tell.

My best suggestion is to configure the SNMP from scratch, and then readd the
properties to your portal.
These are before and after. It is a configuration compare from now to before the
trouble started.

Yes, so they must have been configuration that was overwritten

I'm not sure why it isn't showing, but the device definitely had successful SNMP
collection before

If you have access to the device it will take 5 minutes to configure SNMP on the
device and update the property.
https://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-
protocol-snmp/7282-12.html

You might also like