![]() ![]() It can very easily integrate with one - indeed, it more or less does so out-of-the-box, typically, with a bit of manual adjustment required - but it doesn't directly listen on port 80 (or indeed any port) itself. If, instead, you're meaning to tell us you can't bring up Nagios in your Web browser, that simply means that your Nagios server is not also running a Web server. From your earlier post, we would have assumed you were talking about a Web server you're trying to monitor via Nagios, and that you were unable to connect to that server on port 80 from your Nagios box (and thus, as per MadeInGermany's earlier reply, the Nagios check_http command would fail for that server). If you're getting "Connection refused" when trying to connect to your Nagios server in a Web browser, this isn't actually directly anything to do with Nagios. Hope this helps ! If not, or if you have any further questions, please let us know and we can take things from there. But that can come later - first, get the hang of setting up basic checks in the manner described above, then go from there. You can get all kinds of information this way on the device's interfaces, its network traffic, CPU load levels, uptime, and so on and so forth. If you do need more information than a simple ping check for a network device such as a router, your best bet for doing that is to carry out the checks via an appropriate Nagios SNMP plugin and command. So all the work is done on the Nagios server, with nothing needing doing on your network device other than ensuring that it will accept ping requests from your Nagios server. You would set up a ping check on your Nagios server by first defining the device to be checked in your hosts.cfg file, and then ensuring that you have an entry for that newly-defined device in your services.cfg file to check the host with the check_ping command. And all the work for doing this is carried out on the Nagios server, with nothing needing to be installed on your network device. ![]() If all you want to know is if it's up or not, you would just do a ping check. ![]() That's exactly correct, yes - you wouldn't use NRPE checks for monitoring a router or other non-server device. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |