nope status showing down

[ericssonvietnam]

Configured around 14000 nodes in which around 200 nodes are still showing down.


1.Only using ping check for monitoring
2.Node is pingable with IP and hostname from the nagios server
3) Trace is also getting completed from nagios to node

Can you share me the troubleshooting steps what else i can check at my end

[mcapra]

Can you post the full configurations for the AP_AP1 and AP_AP2 host objects?

[ericssonvietnam]

Can you post the full configurations for the AP_AP1 and AP_AP2 host objects?

below is the configuration for both the hosts

host_name AP_AP1
alias AP_AP1
address 10.105.1.229
}
define service {
use generic-service
host_name AP_AP1
service_description Service ping
check_command check_nrpe!check_ping
}
#Host 733
define host {
use linux-server
host_name AP_AP2
alias AP_AP2
address 10.105.1.230
}
define service {
use generic-service
host_name AP_AP2
service_description Service ping
check_command check_nrpe!check_ping
}

[tgriep]

The check_command for those 2 hosts show you are running the check_ping command on the remote hosts using the NRPE Agent and the check_nrpe command

Code: Select all

check_command check_nrpe!check_ping

and the command defined on the remote system os where the incorrect status is coming from.

Do you want to run the check_ping command on the remote hosts or from the Nagios server?

If you want to run the check_ping from the Nagios server, you would edit the service check and change the command from

Code: Select all

check_command check_nrpe!check_ping

to

Code: Select all

check_command check_ping!3000.0,80%!5000.0,100%

If you still want to run the check_ping on the remote servers using the NRPE Agent, you would have to post the nrpe.cfg file from both of the failing servers.

[ericssonvietnam]

The check_command for those 2 hosts show you are running the check_ping command on the remote hosts using the NRPE Agent and the check_nrpe command

Code: Select all

check_command check_nrpe!check_ping

and the command defined on the remote system os where the incorrect status is coming from.

Do you want to run the check_ping command on the remote hosts or from the Nagios server?

If you want to run the check_ping from the Nagios server, you would edit the service check and change the command from

Code: Select all

check_command check_nrpe!check_ping

to

Code: Select all

check_command check_ping!3000.0,80%!5000.0,100%

If you still want to run the check_ping on the remote servers using the NRPE Agent, you would have to post the nrpe.cfg file from both of the failing servers.

Yes i am running the check_ping from the nagios server as suggested i have modifide the configuration for the host as shown below :

define host {
use linux-server
host_name AP_AP2
alias AP_AP2
address 10.105.1.230
}
define service {
use generic-service
host_name AP_AP2
service_description Service ping
check_command check_ping!3000.0,80%!5000.0,100%
}

But still will require few details from your side on the issue :

The node IP 10.105.1.230 is not pingable from the nagios server but if i am trying to ping my nagios server IPfrom the remotehost(10.105.1.230) it is reachable.

1. Can u tell me which ports does the Nagios core use for communication with the remote host for the above mentioned check with check_command check_ping!3000.0,80%!5000.0,100% also other required port for the communication to occur.
2. What testing i can perform to check the network reach ability,trace is getting completed from both the ends.

[tgriep]

1. You would have to configure your device at IP address 10.105.1.230 to allow inbound ICMP for the check_ping command to function.
2. The check_ping would test the end to end from the Nagios server to the device.