Nagios Support Forum

hi,

I need to integrate Nagios with netcool(monitoring system), so does there any MIBs for that, so I want netcool to send alarms if Nagios system is down.

thanks,

We don't have any documents, guides, etc. in regards to nagios-netcool integration. I would recommend contacting necool, and asking them about this.

Ok, but does there any MIBs special for Nagios itself, so if nagios stop or down ,nagios snmp send traps

There are no special MIBs for Nagios. Nagios does not itself generate snmp alerts. You are going to need to roll your own alerts and use net-snmp to generate snmp alerts.

Nagios XI has a monitoring wizard to setup monitoring a remote Nagios XI server.

regards nagios linux server, does there special traps if linux server down

Can you define what the "down" criteria would be please.

If the Nagios Linux server goes down, then it won't be sending any traps!
At the risk of "highjacking" this thread , this is an interesting question - Who/what monitors the Monitoring server ?

It would be *good* if Nagios had a solution - a very simple monitor - that runs on one or two servers and checks that the Nagios service is running on a Nagios Server.
That way, if the Nagios server dies or Nagios service stops, we would at least get some email notification that it was down?

I suppose I could run up another VM but I want to avoid running up yet another monitoring server for such a simple task.

Has anyone scripted something like this?

regards... Fred

At the risk of "highjacking" this thread , this is an interesting question - Who/what monitors the Monitoring server ?

Hopefully you have an operations staff that is actively using/ watching the monitor. Although if you were in a lights-out remote monitoring solution, you would need a high-availability, fail-over solution instead of relying on a "monitor server down" message that you could possible not ever receive (due to a massive power failure or network outage).

You would maybe use hardware/ software watchdog timers in the kernel, and use a out-of-band server hardware alert to signal fail-over.

Regarding checking a Nagios server from your 3rd party monitoring system hanya.radwan:

Fred is correct, if the Linux server hosting Nagios dies it cannot send a trap. In order to properly monitor that server from your 3rd party monitoring server I recommend an aggressive active host check. My experience with that particular system lends me knowledge that it is able to monitor for processes in its default configuration. You can simply monitor for the Nagios Core process /usr/local/nagios/bin/nagios to verify that the system is functioning. This is not going to help in a scenario where the 2 systems become segmented or both systems go down of course, which is more likely than any actual failure scenario.

Fred Kroeger wrote:If the Nagios Linux server goes down, then it won't be sending any traps!
At the risk of "highjacking" this thread , this is an interesting question - Who/what monitors the Monitoring server ?

It would be *good* if Nagios had a solution - a very simple monitor - that runs on one or two servers and checks that the Nagios service is running on a Nagios Server.
That way, if the Nagios server dies or Nagios service stops, we would at least get some email notification that it was down?

I suppose I could run up another VM but I want to avoid running up yet another monitoring server for such a simple task.

Has anyone scripted something like this?

regards... Fred

Fred,
My solution previously has been to run up another XI server using the free license. I run the "Nagios XI Server" monitoring wizard on it for the production server. Now alerts get sent if production monitoring goes down. On the production server I also run the "Nagios XI Server" monitoring wizard for the XI server with the free license. So now I know if the server monitoring XI goes down, production will alert about it.

I know this means you are running up another VM for a simple task, but this solution gives some confidence that everything is working. Keep in mind now you must ensure these two VM's are kept separate from each other (Virtualization Host, SAN, Switch, Rack) etc.