Nagios Support Forum

Posted: **Sat Jan 21, 2017 10:14 am**

Ok the actual problem solved but now at some checks i receive this unknown status

UNKNOWN SNMP::get_request(SubsystemName): Received noSuchName(2) error-status at error-index 1

and to some just

Code: Select all

UNKNOWN

Posted: **Mon Jan 23, 2017 3:10 pm**

We would have to see how the commands and service checks are defined on your system to help out.
Can you post them here?

Posted: **Tue Jan 24, 2017 1:24 am**

Code: Select all

define command {
        command_name                    check_fujitsu_server
        command_line                    $USER1$/check_fujitsu_server.pl -H $HOSTADDRESS$ -A $ARG1$ $ARG2$ $ARG3$
}

The service definition is on previous replies. Nothing changed.

Posted: **Tue Jan 24, 2017 12:41 pm**

Can you run the check from the command line while adding the -v (verbose output) to the command and post the output here?

Code: Select all

./check_fujitsu_server.pl -H Infra1 -A 10.0.5.15 -C public --chkenv-fan

One thing to try is to increase the timeout for the plugin, to do that edit the check_fujitsu_server command and chabge the following from

Code: Select all

command_line $USER1$/check_fujitsu_server.pl -H $HOSTADDRESS$ -A $ARG1$ $ARG2$ $ARG3$

to

Code: Select all

command_line $USER1$/check_fujitsu_server.pl -H $HOSTADDRESS$ -t 59 -A $ARG1$ $ARG2$ $ARG3$

Try this change and see if it fixes the issue.

Posted: **Wed Jan 25, 2017 8:46 am**

Code: Select all

[root@telematics libexec]# ./check_fujitsu_server.pl -H Infra3 -A 10.0.5.17 -C public --chkenv-fan -v 1
UNKNOWN SNMP::get_request(ServerID): Received noSuchName(2) error-status at error-index 1
[root@telematics libexec]# ./check_fujitsu_server.pl -H Infra3 -A 10.0.5.17 -C public --chkenv-fan -v 2
UNKNOWN SNMP::get_request(ServerID): Received noSuchName(2) error-status at error-index 1
[root@telematics libexec]# ./check_fujitsu_server.pl -H Infra3 -A 10.0.5.17 -C public --chkenv-fan
UNKNOWN SNMP::get_request(ServerID): Received noSuchName(2) error-status at error-index 1

Same as web interface.

I tried to add -t 59 at command definition for global appliance but nothing changed

Posted: **Wed Jan 25, 2017 8:50 am**

but to another case i got this:

Code: Select all

[root@telematics libexec]# ./check_fujitsu_server.pl -H Infra2 -A 10.0.5.16 -C public --chkenv-temp
OK TemperatureSensors(ok)
[root@telematics libexec]# ./check_fujitsu_server.pl -H Infra2 -A 10.0.5.16 -C public --chkenv-temp -v 1
UNKNOWN SNMP::get_request(ServerID): Received noSuchName(2) error-status at error-index 1
[root@telematics libexec]# ./check_fujitsu_server.pl -H Infra2 -A 10.0.5.16 -C public --chkenv-temp -v 2
OK TemperatureSensors(ok) 
ID=YLNS015489 Systemname=INFRA2 Description="Primergy iRMC S4 #1 Wed Aug 5 12:38:56 CEST 2015" Location="Unknown" Contact="root@localhost" SpecifiedAddress=Infra2 AdminAddress=10.0.5.16  
* Temperature Sensors:
[root@telematics libexec]#

At web interface i got

Code: Select all

UNKNOWN SNMP::get_request(ServerID): Received noSuchName(2) error-status at error-index 1

Posted: **Wed Jan 25, 2017 2:36 pm**

The noSuchName message usually means that when a device is polled using that OID number and that device doesn't support that specific OID or that is doesn't respond in time , it will output that message.

Can you poll the Fujitsu system directly without using the iRMC address?
If so, remove the -A option from the command and see if that works better for you.

Can you run the following from the Nagios server and see if they generate the same Unknown message?

Code: Select all

./check_fujitsu_server.pl -H Infra3 -A 10.0.5.17 -t 120 -C public --chkenv-fan
./check_fujitsu_server.pl -H Infra2 -A 10.0.5.16 -t 120 -C public --chkenv-temp

Posted: **Wed Jan 25, 2017 2:47 pm**

Code: Select all

[root@telematics ~]# cd /usr/local/nagios/libexec/
[root@telematics libexec]# ./check_fujitsu_server.pl -H Infra3 -A 10.0.5.17 -t 120 -C public --chkenv-fan
UNKNOWN SNMP::get_request(ServerID): Received noSuchName(2) error-status at error-index 1
[root@telematics libexec]# ./check_fujitsu_server.pl -H Infra2 -A 10.0.5.16 -t 120 -C public --chkenv-temp
OK TemperatureSensors(ok)    
 | Ambient=21C;37;42 Systemboard=44C;75;80 VR_CPU1=41C;120;125 VR_MEM_AB=29C;120;125 VR_MEM_CD=39C;120;125 VR_CPU2=31C;120;125 VR_MEM_EF=34C;120;125 VR_MEM_GH=26C;120;125 CPU1=39C;82;83 MEM_A=27C;78;82 PSU1_Inlet=35C;57;61 PSU2_Inlet=36C;57;61 PSU1=61C;102;107 PSU2=61C;102;107
[root@telematics libexec]# ./check_fujitsu_server.pl -H Infra2 -A 10.0.5.16 -t 120 -C public --chkenv-temp
OK TemperatureSensors(ok)

Posted: **Wed Jan 25, 2017 3:45 pm**

From the output you posted, the server at IP address 10.0.5.17 may not support checking the fan.

Posted: **Wed Jan 25, 2017 4:02 pm**

No. The ip 10.0.5.17 is the irmc ip of a fujitsu server. From its web interface i can monitor the fans. Also i can monitor the fans throw nagios to another same server.

If i run more times the same command it will get the correct output.

Code: Select all

[root@telematics libexec]# ./check_fujitsu_server.pl -H Infra3 -A 10.0.5.17 -t 120 -C public --chkenv-fan
OK Cooling(ok)

Nagios Support Forum

Fujitsu servers

Re: Fujitsu servers

Re: Fujitsu servers

Re: Fujitsu servers

Re: Fujitsu servers

Re: Fujitsu servers

Re: Fujitsu servers

Re: Fujitsu servers

Re: Fujitsu servers

Re: Fujitsu servers

Re: Fujitsu servers