Page 1 of 1
ports /config for DMZ servers
Posted: Tue Feb 16, 2016 11:52 pm
by MuraliV
Dear Team
we are in process of adding T1 servers in Nagios for monitoring servers status / health.. etc.. required firewall ports are opened (attached below) and using agent based monitoring..
12489,5666,161,22,5667
can you please let me know if am missing anything as still T1 servers shown as down in Nagios console but server is up & CPU/Disk space of T1 servers shown as green.
we have blocked ICMP port for T1 servers from Nagios but updated passive check for PING status..
regards
Murali V
Re: ports /config for DMZ servers
Posted: Wed Feb 17, 2016 10:26 am
by rkennedy
What OS is the system running that you are monitoring?
can you please let me know if am missing anything as still T1 servers shown as down in Nagios console but server is up & CPU/Disk space of T1 servers shown as green.
we have blocked ICMP port for T1 servers from Nagios but updated passive check for PING status..
If you are blocking ICMP, then the host check will fail as it is usually just a ping check. You can change the host check, or allow ICMP through.
Re: ports /config for DMZ servers
Posted: Thu Feb 18, 2016 5:04 am
by MuraliV
thanks for the reply
ICMP is blocked.. Host server is running on CentOS and T1 servers are in RHEL..
Can you please advice what config to be done for checking hoststatus instead of using Ping... thanks again for the support
Re: ports /config for DMZ servers
Posted: Thu Feb 18, 2016 10:52 am
by rkennedy
You'll need to add a check_command to your definition, see this link for a further explanation -
https://assets.nagios.com/downloads/nag ... .html#host
check_command: This directive is used to specify the short name of the command that should be used to check if the host is up or down. Typically, this command would try and ping the host to see if it is "alive". The command must return a status of OK (0) or Nagios will assume the host is down. If you leave this argument blank, the host will not be actively checked. Thus, Nagios will likely always assume the host is up (it may show up as being in a "PENDING" state in the web interface). This is useful if you are monitoring printers or other devices that are frequently turned off. The maximum amount of time that the notification command can run is controlled by the host_check_timeout option.