Hi,
We're trying to configure Lexmark printer SNMP monitoring. We loaded Lexmark1.mib in Nagios and went through the wizard.
However, it complained that "No results were returned from a scan of the device".
Any insight about this? The screenshot is attached for reference.
Thanks.
Nagiosxi SNMPWALK issue
Nagiosxi SNMPWALK issue
You do not have the required permissions to view the files attached to this post.
- jmichaelson
- Posts: 118
- Joined: Wed Aug 23, 2023 1:02 pm
Re: Nagiosxi SNMPWALK issue
Let's see if the printer is accessible. first try pinging it, or going to its web interface in a browser. Assuming that works, install a port scanning tool (temporarily if you need to due to policies) on your XI server. My personal choice is nmap, and it is what I'll use for the example. Scan port 161 on the printer to see if it is accessible.
With nmap, the command for the printer's IP address is:
nmap -sU -p 161 10.0.64.14
You have to use something like nmap, as using telnet to test it won't work since SNMP used UDP.
If it is accessible, we'll have to take a closer look into the SNMP results, and why they're not correlating with the MIB.
With nmap, the command for the printer's IP address is:
nmap -sU -p 161 10.0.64.14
You have to use something like nmap, as using telnet to test it won't work since SNMP used UDP.
If it is accessible, we'll have to take a closer look into the SNMP results, and why they're not correlating with the MIB.
Please let us know if you have any other questions or concerns.
-Jason
-Jason
Re: Nagiosxi SNMPWALK issue
Thanks for your reply!
I confirm nmap command is working as expected as below from nagiosxi host.
Also snmpwalk is working as well.
Please advise. Thanks!
I confirm nmap command is working as expected as below from nagiosxi host.
Code: Select all
[root@nagiosxi services]# nmap -sU -p 161 10.0.64.14
Starting Nmap 6.47 ( http://nmap.org ) at 2024-04-09 09:22 EDT
Nmap scan report for oa-e109-prn1.internal (10.0.64.14)
Host is up (0.00059s latency).
PORT STATE SERVICE
161/udp open snmp
Nmap done: 1 IP address (1 host up) scanned in 0.08 second
Code: Select all
[root@nagiosxi services]# snmpwalk -c public -v1 10.0.64.14 | head
SNMPv2-MIB::sysDescr.0 = STRING: Lexmark XM7155 version NH8.TU.N235 kernel 3.0.0 All-N-1
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.641.2.71107141
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (154777327) 17 days, 21:56:13.27
SNMPv2-MIB::sysContact.0 = STRING:
SNMPv2-MIB::sysName.0 = STRING: oa-e109-prn1
SNMPv2-MIB::sysLocation.0 = STRING: oa-e109-prn1 outside e108
SNMPv2-MIB::sysServices.0 = INTEGER: 72
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (193) 0:00:01.93
SNMPv2-MIB::sysORID.1 = OID: IF-MIB::ifMIB
SNMPv2-MIB::sysORID.2 = OID: IP-MIB::ip
Re: Nagiosxi SNMPWALK issue
Hi @bongbi,
I think it's clear from your post that you're able to form a connection, snmpwalk is finding results, and that it's successfully filtering results based on your MIB file. The last one I'd want to check on is the command timeout. Since you've already run snmpwalk from the command line, how long does that take to complete? If you let it run to completion, does the last line of output match the output from your first screenshot?
I think it's clear from your post that you're able to form a connection, snmpwalk is finding results, and that it's successfully filtering results based on your MIB file. The last one I'd want to check on is the command timeout. Since you've already run snmpwalk from the command line, how long does that take to complete? If you let it run to completion, does the last line of output match the output from your first screenshot?
As of May 25th, 2018, all communications with Nagios Enterprises and its employees are covered under our new Privacy Policy
Re: Nagiosxi SNMPWALK issue
Hi,
Actually, it does timeout at the end of snmpwalk.
Actually, it does timeout at the end of snmpwalk.
Code: Select all
SNMPv2-MIB::snmpProxyDrops.0 = Counter32: 0
HOST-RESOURCES-MIB::hrSystemUptime.0 = Timeticks: (156223666) 18 days, 1:57:16.66
HOST-RESOURCES-MIB::hrSystemDate.0 = STRING: 2024-4-9,13:46:49.8,-4:0
HOST-RESOURCES-MIB::hrSystemInitialLoadDevice.0 = INTEGER: 2
HOST-RESOURCES-MIB::hrSystemInitialLoadParameters.0 = ""
HOST-RESOURCES-MIB::hrSystemNumUsers.0 = Gauge32: 0
HOST-RESOURCES-MIB::hrSystemProcesses.0 = Gauge32: 1
HOST-RESOURCES-MIB::hrSystemMaxProcesses.0 = INTEGER: 1
HOST-RESOURCES-MIB::hrMemorySize.0 = INTEGER: 1048576 KBytes
HOST-RESOURCES-MIB::hrStorageIndex.1 = INTEGER: 1
HOST-RESOURCES-MIB::hrStorageIndex.2 = INTEGER: 2
HOST-RESOURCES-MIB::hrStorageIndex.3 = INTEGER: 3
HOST-RESOURCES-MIB::hrStorageIndex.4 = INTEGER: 4
HOST-RESOURCES-MIB::hrStorageType.1 = OID: HOST-RESOURCES-TYPES::hrStorageRam
HOST-RESOURCES-MIB::hrStorageType.2 = OID: HOST-RESOURCES-TYPES::hrStorageOther
HOST-RESOURCES-MIB::hrStorageType.3 = OID: HOST-RESOURCES-TYPES::hrStorageOther
HOST-RESOURCES-MIB::hrStorageType.4 = OID: HOST-RESOURCES-TYPES::hrStorageFixedDisk
HOST-RESOURCES-MIB::hrStorageDescr.1 = STRING: RAM
HOST-RESOURCES-MIB::hrStorageDescr.2 = STRING: %rom%
HOST-RESOURCES-MIB::hrStorageDescr.3 = STRING: NVRAM
HOST-RESOURCES-MIB::hrStorageDescr.4 = STRING: %disk%
HOST-RESOURCES-MIB::hrStorageAllocationUnits.1 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.2 = INTEGER: 1024 Bytes
HOST-RESOURCES-MIB::hrStorageAllocationUnits.3 = INTEGER: 1024 Bytes
Timeout: No Response from 10.0.64.14
- jmichaelson
- Posts: 118
- Joined: Wed Aug 23, 2023 1:02 pm
Re: Nagiosxi SNMPWALK issue
Let's try the snmpwalk again and increase the timeout. Add the -t parameter to it like so:
The number after the t is the number of seconds. Per https://linux.die.net/man/1/snmpcmd, the default is 1 second.
Code: Select all
snmpwalk -t 5 -c public -v1 10.0.64.14
Please let us know if you have any other questions or concerns.
-Jason
-Jason
Re: Nagiosxi SNMPWALK issue
Yup. 5 seconds worked.
Code: Select all
IPV6-MIB::ipv6AddrAddress.8 = STRING: 0:0:0:0:0:0:0:0
IPV6-MIB::ipv6AddrPfxLength.1 = INTEGER: 64 bits
IPV6-MIB::ipv6AddrPfxLength.2 = INTEGER: 64 bits
IPV6-MIB::ipv6AddrPfxLength.3 = INTEGER: 64 bits
IPV6-MIB::ipv6AddrPfxLength.4 = INTEGER: 64 bits
IPV6-MIB::ipv6AddrPfxLength.5 = INTEGER: 64 bits
IPV6-MIB::ipv6AddrPfxLength.6 = INTEGER: 64 bits
IPV6-MIB::ipv6AddrPfxLength.7 = INTEGER: 64 bits
IPV6-MIB::ipv6AddrPfxLength.8 = INTEGER: 64 bits
IPV6-MIB::ipv6AddrType.1 = INTEGER: unknown(3)
IPV6-MIB::ipv6AddrType.2 = INTEGER: unknown(3)
IPV6-MIB::ipv6AddrType.3 = INTEGER: unknown(3)
IPV6-MIB::ipv6AddrType.4 = INTEGER: unknown(3)
IPV6-MIB::ipv6AddrType.5 = INTEGER: unknown(3)
IPV6-MIB::ipv6AddrType.6 = INTEGER: unknown(3)
IPV6-MIB::ipv6AddrType.7 = INTEGER: unknown(3)
IPV6-MIB::ipv6AddrType.8 = INTEGER: unknown(3)
IPV6-MIB::ipv6AddrAnycastFlag.1 = INTEGER: false(2)
IPV6-MIB::ipv6AddrAnycastFlag.2 = INTEGER: false(2)
IPV6-MIB::ipv6AddrAnycastFlag.3 = INTEGER: false(2)
IPV6-MIB::ipv6AddrAnycastFlag.4 = INTEGER: false(2)
IPV6-MIB::ipv6AddrAnycastFlag.5 = INTEGER: false(2)
IPV6-MIB::ipv6AddrAnycastFlag.6 = INTEGER: false(2)
IPV6-MIB::ipv6AddrAnycastFlag.7 = INTEGER: false(2)
IPV6-MIB::ipv6AddrAnycastFlag.8 = INTEGER: false(2)
IPV6-MIB::ipv6AddrStatus.1 = INTEGER: preferred(1)
IPV6-MIB::ipv6AddrStatus.2 = INTEGER: invalid(3)
IPV6-MIB::ipv6AddrStatus.3 = INTEGER: invalid(3)
IPV6-MIB::ipv6AddrStatus.4 = INTEGER: invalid(3)
IPV6-MIB::ipv6AddrStatus.5 = INTEGER: invalid(3)
IPV6-MIB::ipv6AddrStatus.6 = INTEGER: invalid(3)
IPV6-MIB::ipv6AddrStatus.7 = INTEGER: invalid(3)
IPV6-MIB::ipv6AddrStatus.8 = INTEGER: invalid(3)
[root@nagiosxi services]#