Microsoft Exchange Monitoring

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
Locked
austin
Posts: 6
Joined: Tue Jul 31, 2012 4:12 am

Microsoft Exchange Monitoring

Post by austin »

I have added one Microsoft Exchange for monitoring. Below are the results:
-----------------------------------------------------------------------------------------------
Blacklist Status Ok Not black-listed
Exchange Core Services Critical Connection refused
Exchange Web Services Critical Connection refused
IMAP Critical Connection refused
Messages Pending Routing Critical Connection refused
OWA HTTP Warning HTTP WARNING: HTTP/1.1 403 Forbidden
Ping Ok OK - 172.16.1.107: rta 1.673ms, lost 0%
POP Ok POP OK - 0.005 second response time on port 110
Remote Queue Length Critical Connection refused
SMTP Ok SMTP OK - 0.007 sec. response time
------------------------------------------------------------------------------------------------
I need help to understand whether any setting / configuration is required on the Exchange server since for a few items it says "Connection refused". Please guide.
User avatar
nscott
Posts: 1040
Joined: Wed May 11, 2011 8:54 am

Re: Microsoft Exchange Monitoring

Post by nscott »

Have you set up NSClient++ on the Microsoft Exchange server? I took a look at the wizard and it looks like you'll have to get those connection refused metrics by installing NSClient, deleting the Exchange host in Nagios, and then rerunning the wizard.

If you want some guide to reference for installing NSClient, it can be found here:
http://assets.nagios.com/downloads/nagi ... _Agent.pdf

Once you have that installed the agent, make you you snag the password for accessing the agent remotely, as thats the password you will need when running the wizard.
Nicholas Scott
Former Nagios employee
austin
Posts: 6
Joined: Tue Jul 31, 2012 4:12 am

Re: Microsoft Exchange Monitoring

Post by austin »

Thanks Nicholas.

With the help of NSClient++ agent I was able to configure this properly. However I could do this on a different server running the same CAS/HUB role.

I installed NSClient++ agent on the previous host but am not getting the result. You have suggested that I must delete this host in Nagios but I am unable to delete it. Infact for that matter I am unable to delete any other device which gets once configured in Nagios. I have tried doing the same using Core Config Manager but is simply doesnt allow deleting.
yancy
Posts: 523
Joined: Thu Oct 06, 2011 10:12 am

Re: Microsoft Exchange Monitoring

Post by yancy »

austin,

Have a look at this document which describes host removal:

http://assets.nagios.com/downloads/nagi ... gement.pdf

One key idea is you must remove the services first before removing the host.


Regards,

-Yancy
austin
Posts: 6
Joined: Tue Jul 31, 2012 4:12 am

Re: Microsoft Exchange Monitoring

Post by austin »

With the help of the document I was able to delete the asscoiated services and then finally could delete the host too. And I made a point to "apply configuration" before I proceeded.

However after adding the host again in Nagios, the results are the same i.e. for the service items that was stating "connection refused" - continues.
yancy
Posts: 523
Joined: Thu Oct 06, 2011 10:12 am

Re: Microsoft Exchange Monitoring

Post by yancy »

Austin,

It sounds like you have two different exchange servers now with NSClient++ installed running an external script. One of which is working correctly, and one that is not. Right?

Is there any difference in the NSC.ini or NSClient.ini file?


Regards,

-Yancy
austin
Posts: 6
Joined: Tue Jul 31, 2012 4:12 am

Re: Microsoft Exchange Monitoring

Post by austin »

The problem is resolved.

Following were the steps taken:
1) remove the associated services from 'core config manager'
2) remove the host
3) ensure that the .cfg file are deleted (I had to delete it manually) from /usr/local/nagios/etc/hosts and /usr/local/nagios/etc/services
4) uninstall the NSClient agent
5) reconfigure NSClient agent
6) Add the host
Locked