Nagios Support Forum

Hi,

Based on your output of the command:
snmpwalk -v2c -c XXXXX 10.80.60.12

The four OIDs you are looking for are NOT available: This could be because they don't exist or it could be that we don't have access to them.

In the command "snmpwalk -v2c -c XXXXX 10.80.60.12", did you type it exactly like that?
The XXXXX needs to be the SNMP Community Name assigned to that device, consider it like a password.
This is described in https://www.audiocodes.com/media/14595/ ... ver-72.pdf
starting on page 8.

On page 9 is this: That tells me that you can probably find the value we need for XXXXX in this "snmpwalk -v2c -c XXXXX 10.80.60.12" command
by looking at the .ini file for that device. When you get that value please re-run that "snmpwalk -v2c -c XXXXX 10.80.60.12" command
again with the XXXXX replaced by the SNMPREADONLYCOMMUNITYSTRING_<x> you determined from the .ini file and post
the output here please.

You can examine the file yourself and look for the four OIDs you are looking for.

Thanks

Hi Team,

Due to some security reason we have changed the community string with XXXX while providing the update to you.

Yes, we are giving the right community due to this only we are getting the data like "No Such Object available on this agent at this OID". Otherwise we will get communication issue error.

the below is the output if we give XXXX instead of community string.
[root@ittestnagiosxi libexec]# snmpwalk -v2c -c XXXXX 10.80.60.12 .1.3.6.1.4.1.5003.10.8.2.54.69.1.3
Timeout: No Response from 10.80.60.12
You have new mail in /var/spool/mail/root

The below is the output if we give right community we just removed password and provided to you due to some security reason.
[root@ittestnagiosxi libexec]# snmpwalk -v2c -c ddbos20 10.80.60.12 .1.3.6.1.4.1.5003.10.8.2.54.69.1.3
SNMPv2-SMI::enterprises.5003.10.8.2.54.69.1.3 = No Such Object available on this agent at this OID.

--------------------
Vendor has shown to us like they have used virtual appliance with same device model and shown to us with output of above OID. They were able to get the data.

Please let us know if you need more details on this.

Hi,

Thanks for that information. I just want to summarize what the issue is:

• 1. You connect to the device using a password 'XXXXX' and the snmpwalk works, however for
  the four OIDs you are interested in, you get a result of "No Such Object"
  
  2. The device vendor has shown that these four OIDs do exist

Does that sound correct?

Another thing to check is what version of SNMP is the vendor using?

Thanks

Hi Team,

1. You connect to the device using a password 'XXXXX' and the snmpwalk works, however for
the four OIDs you are interested in, you get a result of "No Such Object" -- yes

2. The device vendor has shown that these four OIDs do exist -- yes we could the output when he was shown to us. it means OID exists right.

Vendor is using SNMP V2 to get the OID.

HI @informatica,

Let's move this over to a support ticket, and we'll set up a remote session to further troubleshoot the error you are getting.

Please open a support ticket at the link below and reference this post.

https://support.nagios.com/tickets/

Best Regards,
Benjamin

If the base snmpwalk command is saying:
That means the remote device is not serving those OIDs. Considering you're using the numbers for the OIDs instead of the names the MIBs on the XI server don't have any impact on this. There is nothing we can do from our end for this, you would need to reach out to the manufacturer of your device and ask them why it's not serving those OIDs and what you need to do to get it to serve the OIDs you're looking to monitor.

Your screenshots are of you browsing the MIB file, it will show everything in the MIB, I do not see any values listed in your screenshot though so it's likely just showing you what the MIB allows, not that the OID exists on the remote system.

Hi,

After reviewing this issue further, this is likely an issue with the remote device. Please try testing the SNMP walk command from another server to rule out any connection issue between the remote device and the XI system and let us know if you're getting the same message.

Thanks,
Benjamin

as you suggested we have tried in prodservers. the below is the update

[nagios@in-nagios-a root]$ snmpwalk -v2c -c passwd 10.80.50.2 .1.3.6.1.4.1.5003.10.8.2.54.65.1.3.0
SNMPv2-SMI::enterprises.5003.10.8.2.54.65.1.3.0 = No Such Object available on this agent at this OID
[nagios@in-nagios-a root]$ snmpwalk -v2c -c passwd 10.80.50.2 .1.3.6.1.4.1.5003.10.8.2.54.67.1.3.0
SNMPv2-SMI::enterprises.5003.10.8.2.54.67.1.3.0 = No Such Object available on this agent at this OID
[nagios@in-nagios-a root]$ snmpwalk -v2c -c passwd 10.80.50.2 .1.3.6.1.4.1.5003.10.8.2.54.69.1.3
SNMPv2-SMI::enterprises.5003.10.8.2.54.69.1.3 = No Such Object available on this agent at this OID
[nagios@in-nagios-a root]$ snmpwalk -v2c -c passwd 10.80.50.2 .1.3.6.1.4.1.5003.10.8.2.54.71.1.3
SNMPv2-SMI::enterprises.5003.10.8.2.54.71.1.3 = No Such Object available on this agent at this OID
[nagios@in-nagios-a root]$ snmpwalk -v2c -c passwd 10.80.50.2 1.3.6.1.4.1.5003.10.8.2.54.71.1.3
SNMPv2-SMI::enterprises.5003.10.8.2.54.71.1.3 = No Such Object available on this agent at this OID
[nagios@in-nagios-a root]$ cd /usr/share/snmp/mibs/
[nagios@in-nagios-a mibs]$ ll AC-PM
AC-PMCONTROL-MIB.my AC-PMPSTN-MIB.my

The below is the MIB path.

[nagios@in-nagios-a mibs]$ ll AC-PMCONTROL-MIB.my
-rw-rw-r-- 1 apache nagios 860989 Apr 21 14:25 AC-PMCONTROL-MIB.my
You have new mail in /var/spool/mail/root
[nagios@in-nagios-a mibs]$
------------------------------------------------------------------------------------------
I have tried removing by dot as below

[nagios@in-nagios-a mibs]$ snmpwalk -v2c -c passwd 10.80.50.2 1.3.6.1.4.1.5003.10.8.2.54.71.1.3
SNMPv2-SMI::enterprises.5003.10.8.2.54.71.1.3 = No Such Object available on this agent at this OID
[nagios@in-nagios-a mibs]$


-------------------------------------------------------------------------------------------
the below is the communication happening from nagios servers. we don't see any communication issue.
We would like to prove that device is having any issue with OID or nagios does not have capability to bring the OID details or we are doing any mistake ??
[nagios@in-nagios-a mibs]$ snmpwalk -v2c -c passwd 10.80.50.2
SNMPv2-MIB::sysDescr.0 = STRING: Cisco NX-OS(tm) nxos.9.2.1.bin, Software (nxos), Version 9.2(1), RELEASE SOFTWARE Copyright (c) 2002-2018 by Cisco Systems, Inc. Compiled 7/17/2018 16:00:00
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::enterprises.9.12.3.1.3.1812
DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (577356301) 66 days, 19:46:03.01
SNMPv2-MIB::sysContact.0 = STRING: [email protected]
SNMPv2-MIB::sysName.0 = STRING: BLNX9K01.informatica.com
SNMPv2-MIB::sysLocation.0 = STRING:
SNMPv2-MIB::sysServices.0 = INTEGER: 70
SNMPv2-MIB::sysORLastChange.0 = Timeticks: (1271) 0:00:12.71
SNMPv2-MIB::sysORID.1 = OID: SNMPv2-MIB::snmpMIB
SNMPv2-MIB::sysORID.2 = OID: SNMP-VIEW-BASED-ACM-MIB::vacmBasicGroup
SNMPv2-MIB::sysORID.3 = OID: SNMP-FRAMEWORK-MIB::snmpFrameworkMIBCompliance
SNMPv2-MIB::sysORID.4 = OID: SNMP-MPD-MIB::snmpMPDCompliance
SNMPv2-MIB::sysORID.5 = OID: SNMP-USER-BASED-SM-MIB::usmMIBCompliance
SNMPv2-MIB::sysORDescr.1 = STRING: The MIB module for SNMPv2 entities
SNMPv2-MIB::sysORDescr.2 = STRING: View-based Access Control Model for SNMP.
SNMPv2-MIB::sysORDescr.3 = STRING: The SNMP Management Architecture MIB.
SNMPv2-MIB::sysORDescr.4 = STRING: The MIB for Message Processing and Dispatching.
SNMPv2-MIB::sysORDescr.5 = STRING: The management information definitions for the SNMP User-based Security Model.
SNMPv2-MIB::sysORUpTime.1 = Timeticks: (1271) 0:00:12.71
SNMPv2-MIB::sysORUpTime.2 = Timeticks: (1271) 0:00:12.71
SNMPv2-MIB::sysORUpTime.3 = Timeticks: (1271) 0:00:12.71
SNMPv2-MIB::sysORUpTime.4 = Timeticks: (1271) 0:00:12.71
SNMPv2-MIB::sysORUpTime.5 = Timeticks: (1271) 0:00:12.71
IF-MIB::ifNumber.0 = INTEGER: 111
IF-MIB::ifIndex.83886080 = INTEGER: 83886080
IF-MIB::ifIndex.151060481 = INTEGER: 151060481
IF-MIB::ifIndex.151060482 = INTEGER: 151060482
IF-MIB::ifIndex.151060484 = INTEGER: 151060484
IF-MIB::ifIndex.151060488 = INTEGER: 151060488
IF-MIB::ifIndex.151060492 = INTEGER: 151060492
IF-MIB::ifIndex.151060495 = INTEGER: 151060495
IF-MIB::ifIndex.151060500 = INTEGER: 151060500
IF-MIB::ifIndex.151060502 = INTEGER: 151060502
IF-MIB::ifIndex.151060504 = INTEGER: 151060504
IF-MIB::ifIndex.151060508 = INTEGER: 151060508
IF-MIB::ifIndex.151060512 = INTEGER: 151060512
IF-MIB::ifIndex.151060530 = INTEGER: 151060530
IF-MIB::ifIndex.151060532 = INTEGER: 151060532
IF-MIB::ifIndex.151060534 = INTEGER: 151060534
IF-MIB::ifIndex.151060537 = INTEGER: 151060537
IF-MIB::ifIndex.151060539 = INTEGER: 151060539
IF-MIB::ifIndex.151060540 = INTEGER: 151060540
IF-MIB::ifIndex.151060542 = INTEGER: 151060542
IF-MIB::ifIndex.151060544 = INTEGER: 151060544
IF-MIB::ifIndex.151060546 = INTEGER: 151060546
IF-MIB::ifIndex.151060548 = INTEGER: 151060548
IF-MIB::ifIndex.151060550 = INTEGER: 151060550
IF-MIB::ifIndex.151060552 = INTEGER: 151060552
IF-MIB::ifIndex.151060554 = INTEGER: 151060554
IF-MIB::ifIndex.151060556 = INTEGER: 151060556
IF-MIB::ifIndex.151060558 = INTEGER: 151060558

Hi,

Thanks for testing that from another device, so when you see the error, No Such Object available, that means that this device is not serving this OID because it's not enabled or not offered ( or the OID string is incorrect).

There are multiple IP addresses. The initial screenshot was a Cisco device but then it was pointed out that the device is an AudioCodes Mediant 800C. For this support issue, let's narrow the focus to one device.

Can you run the following command from the prod server so we can see the system info for the following device?

Hi Team,
Instead of OID we are using snmptrap method. we found snmp trap OID and based on that we have configured OID in snmp trap interface.


challenge is here is we are getting the traps when we have critical but when alerts is cleared in status information showing as alert cleared but in state its showing still critical.

I am giving the output screenshot and traps output and snmp traps interface configuration setting.

I can give two scenario .

When the alert is critical: The highlighted OID is the critical where you can observed Trunk Los alarm. This is critical we are getting. In nagios also we can see critical with below information.


Fri May 21 09:16:32 2021 .1.3.6.1.4.1.5003.9.10.1.21.2.0.49 Critical "SBC - Trunk LOS Alarm" TK-SBC1 - Received trap "TrunkLOSAlarm" with variables "enterprises.5003.9.10.1.21.1.1.0:48 enterprises.5003.9.10.1.21.1.2.0:Trunk LOS Alarm. enterprises.5003.9.10.1.21.1.3.0:Interface#0/trunk#0 enterprises.5003.9.10.1.21.1.4.0:5 enterprises.5003.9.10.1.21.1.5.0:50 enterprises.5003.9.10.1.21.1.6.0:1 enterprises.5003.9.10.1.21.1.7.0:29 enterprises.5003.9.10.1.21.1.8.0: enterprises.5003.9.10.1.21.1.9.0:TK-SBC1 enterprises.5003.9.10.1.21.1.10.0: enterprises.5003.9.10.1.21.1.11.0:07 E5 05 14 13 2E 1F 00 enterprises.5003.9.10.1.21.1.12.0:5 enterprises.5003.9.10.1.21.1.13.0:0 enterprises.5003.9.10.1.21.1.14.0:0 enterprises.5003.9.10.1.21.1.15.0:0 enterprises.5003.9.10.1.21.1.16.0:12628895"


When alert is cleared or OK: The same OID is showing alert is cleared but in nagios console we are getting alert is cleared output but state is not changing, its in still Critical. Please find the attachment

Fri May 21 09:18:03 2021 .1.3.6.1.4.1.5003.9.10.1.21.2.0.49 Critical "SBC - Trunk LOS Alarm" TK-SBC1 - Received trap "TrunkLOSAlarm" with variables "enterprises.5003.9.10.1.21.1.1.0:48 enterprises.5003.9.10.1.21.1.2.0:Alarm cleared: Trunk LOS Alarm. enterprises.5003.9.10.1.21.1.3.0:Interface#0/trunk#0 enterprises.5003.9.10.1.21.1.4.0:0 enterprises.5003.9.10.1.21.1.5.0:52 enterprises.5003.9.10.1.21.1.6.0:1 enterprises.5003.9.10.1.21.1.7.0:29 enterprises.5003.9.10.1.21.1.8.0: enterprises.5003.9.10.1.21.1.9.0:TK-SBC1 enterprises.5003.9.10.1.21.1.10.0: enterprises.5003.9.10.1.21.1.11.0:07 E5 05 14 13 30 01 00 enterprises.5003.9.10.1.21.1.12.0:4 enterprises.5003.9.10.1.21.1.13.0:0 enterprises.5003.9.10.1.21.1.14.0:0 enterprises.5003.9.10.1.21.1.15.0:0 enterprises.5003.9.10.1.21.1.16.0:12628895"