Nagios Support Forum

Hello Team,

We were having an ongoing issue with IBM XGS devices with the SNMP results as we are not getting the expected results with the OID. So we have tried to change the SNMP v3 settings of Nagios user from MD5 to SHA and DES to AES in the IBM XGS device. After making those changes, few services started reporting as expected but there are few services that are triggering the error as shown in the snippet.
Please let me know where I am doing the mistake or where I should make changes in order to get the expected result.

In your command, you are missing the authproto option.

See this.

-a, --authproto=[MD5|SHA]
SNMPv3 auth proto

If your authproto is using MD5, you would add this to the check_snmp plugin's options.
Or if it is using SAH, add this.
Try adding the option and see if that allows the plugin to connect.

Thank you.

Hello @tgriep,

Thanks for your response and the suggestion given by you has solved the problem partially. I have a total of 225 devices that were monitored through SNMP protocol. After adding the "authproto option", few devices started responding without any issues, however, there were few devices that still triggers the alerts as shown below.

./protection_interfaces_up_down.sh 10.175.34.40 1.1 2
snmpwalk: Authentication failure (incorrect password, community or key)
snmpwalk: Authentication failure (incorrect password, community or key)

This custom script uses the snmpwalk to get the desired output.
For security reasons, I have hashed the passwords.

Kindly let me know of any suggestions to sort out this issue.

The only thing left to to is to login to the IBM XGS devices and verify that the username, passwords, and the protocols are set to what the custom plugin is using.
Also verify that they are enabled to use SNMP version 3.

If they do not match, the snmpwalk would fail with that message.

Thank you.