System SNMP error - SNMP::get(): No response from

[timreichhart]

Hello
I am having issues with cacti showing one device down (System SNMP error - SNMP::get(): No response from) it was up and running right before I changed the IP address from DHCP to static IP and I am running Proxmox VM on ubuntu 20.04LTS and I had this cacti box at 192.168.85.2 and switched to 10.41.1.3 and I also updated the proxmox ethernet adapter to 10.41.1.4 and after doing that I am getting this error System SNMP error - SNMP::get(): No response from device IP

[TheWitness]

Post a few screen shots, and remember if snmpget works, Cacti should too. Try snmpget from the command line.

[timreichhart]

just type in snmpget?

[timreichhart]

if I just do that command I get this:

tim@cacti:~$ snmpget
No hostname specified.
USAGE: snmpget [OPTIONS] AGENT OID [OID]...

Version: 5.8
Web: http://www.net-snmp.org/
Email: net-snmp-coders@lists.sourceforge.net

OPTIONS:
-h, --help display this help message
-H display configuration file directives understood
-v 1|2c|3 specifies SNMP version to use
-V, --version display package version number
SNMP Version 1 or 2c specific
-c COMMUNITY set the community string
SNMP Version 3 specific
-a PROTOCOL set authentication protocol (MD5|SHA|SHA-224|SHA-256|SHA-384|SHA-512)
-A PASSPHRASE set authentication protocol pass phrase
-e ENGINE-ID set security engine ID (e.g. 800000020109840301)
-E ENGINE-ID set context engine ID (e.g. 800000020109840301)
-l LEVEL set security level (noAuthNoPriv|authNoPriv|authPriv)
-n CONTEXT set context name (e.g. bridge1)
-u USER-NAME set security name (e.g. bert)
-x PROTOCOL set privacy protocol (DES|AES)
-X PASSPHRASE set privacy protocol pass phrase
-Z BOOTS,TIME set destination engine boots/time
General communication options
-r RETRIES set the number of retries
-t TIMEOUT set the request timeout (in seconds)
Debugging
-d dump input/output packets in hexadecimal
-D[TOKEN[,...]] turn on debugging output for the specified TOKENs
(ALL gives extremely verbose debugging output)
General options
-m MIB[:...] load given list of MIBs (ALL loads everything)
-M DIR[:...] look in given list of directories for MIBs
(default: /home/tim/.snmp/mibs:/usr/share/snmp/mibs:/usr/share/snmp/mibs/iana:/usr/share/snmp/mibs/ietf)
-P MIBOPTS Toggle various defaults controlling MIB parsing:
u: allow the use of underlines in MIB symbols
c: disallow the use of "--" to terminate comments
d: save the DESCRIPTIONs of the MIB objects
e: disable errors when MIB symbols conflict
w: enable warnings when MIB symbols conflict
W: enable detailed warnings when MIB symbols conflict
R: replace MIB symbols from latest module
-O OUTOPTS Toggle various defaults controlling output display:
0: print leading 0 for single-digit hex characters
a: print all strings in ascii format
b: do not break OID indexes down
e: print enums numerically
E: escape quotes in string indices
f: print full OIDs on output
n: print OIDs numerically
p PRECISION: display floating point values with specified PRECISION (printf format string)
q: quick print for easier parsing
Q: quick print with equal-signs
s: print only last symbolic element of OID
S: print MIB module-id plus last element
t: print timeticks unparsed as numeric integers
T: print human-readable text along with hex strings
u: print OIDs using UCD-style prefix suppression
U: don't print units
v: print values only (not OID = value)
x: print all strings in hex format
X: extended index format
-I INOPTS Toggle various defaults controlling input parsing:
b: do best/regex matching to find a MIB node
h: don't apply DISPLAY-HINTs
r: do not check values for range/type legality
R: do random access to OID labels
u: top-level OIDs must have '.' prefix (UCD-style)
s SUFFIX: Append all textual OIDs with SUFFIX before parsing
S PREFIX: Prepend all textual OIDs with PREFIX before parsing
-L LOGOPTS Toggle various defaults controlling logging:
e: log to standard error
o: log to standard output
n: don't log at all
f file: log to the specified file
s facility: log to syslog (via the specified facility)

(variants)
[EON] pri: log to standard error, output or /dev/null for level 'pri' and above
[EON] p1-p2: log to standard error, output or /dev/null for levels 'p1' to 'p2'
[FS] pri token: log to file/syslog for level 'pri' and above
[FS] p1-p2 token: log to file/syslog for levels 'p1' to 'p2'
-C APPOPTS Set various application specific behaviours:
f: do not fix errors and retry the request
tim@cacti:~$

[TheWitness]

Read the man pages or documentation. Just follow your nose. Another option, maybe easier is this:

snmpwalk -c public -v2c hostname .1.3

That should spew a lot of data. The -c is the community string and of course the hostname is the hostname of the server.

[timreichhart]

Code: Select all

tim@cacti:~$ ^C
tim@cacti:~$ snmpwalk -c public -v2c hostname .1.3
snmpwalk: Unknown host (hostname) (Invalid argument)
tim@cacti:~$ sudo snmpwalk -c public -v2c hostname .1.3
[sudo] password for tim:
snmpwalk: Unknown host (hostname) (Invalid argument)
tim@cacti:~$

[TheWitness]

Read my post again.

[timreichhart]

I did what you told me to do so

[TheWitness]

hostname is a generic term. It is not the hostname of your host.

[timreichhart]

tim@cacti:~$ snmpwalk -c public -v2c 10.41.1.3 .1.3
Timeout: No Response from 10.41.1.3
tim@cacti:~$


tim@cacti:~$ snmpwalk -c public -v2c 10.41.1.3
Timeout: No Response from 10.41.1.3
tim@cacti:~$

and firewall been turned off

I replaced hostname for where the ip address of the machine is

[TheWitness]

Well, that's where your problem is. Something changed. If you can make snmpwalk or snmpget to work again, then Cacti will work again. Do some research on SNMP. It's not that complicated, it just appears to be that way at first.

[timreichhart]

only thing as changed was changing of the IP address from 192.168.85.4 to 10.41.1.4 noting else as changed

[TheWitness]

You should try the ping tool too. It's very handy. Also, many snmp agents have ACL's as a part of their configuration. So, they only allow certain IP's to gather data.

[timreichhart]

I found out my issue I have ALLOWED_NETWORKS on my tik when I switched it I didnt put that new subnet address in it. Its also in recovering mode right now

[timreichhart]

Its back up and running and thanks for your help