Monitor Microsoft Exchange Network Listeners

Enable detection and monitoring of Microsoft Exchange Server network listeners

  • Tested with Microsoft Exchange 2007 with SP3
  • Tested with Microsoft Exchange 2010
  • Tested with Microsoft Exchange 2013

A best practice would be to also monitor Microsoft Exchange Windows services – see How to: Monitoring Microsoft Exchange

Default OpenNMS monitors

Monitors for the SMTP, IMAP, and POP3 protocols, along with HTTP and HTTPS, are included in the default polling package in OpenNMS

Monitoring Exchange Specific Protocols

Add the following service definitions in the existing “service” definition section in the “example1” package of $OPENNMS_HOME/etc/poller-configuration.xml

        <!-- Enable ongoing monitoring of an already discovered Microsoft Exchange OWA (Outlook Web Access) site accessed using HTTPS on the default port TCP 443 -->
        <!-- Microsoft Exchange 2007 returns HTTPS error 400 "Bad Request" when OpenNMS does a GET trying to access the usual OWA login page at /owa/auth/logon.aspx but /owa/default.aspx returns 302 "Moved Temporarily" so this seems to be the best option available for Exchange 2007; uncomment if using Exchange 2007 -->
        <!--
        <service name="MicrosoftExchangeOWA2007-HTTPS" interval="300000" user-defined="false" status="on">
            <parameter key="port" value="443" />
            <parameter key="url" value="/owa/default.aspx" />
            <parameter key="response" value="302" />
            <parameter key="timeout" value="5000" />
            <parameter key="retry" value="2" />
        </service>
        -->
        <!-- Exchange 2010 OWA service poller -->
        <service name="MicrosoftExchangeOWA2010-HTTPS" interval="300000" user-defined="false" status="on">
            <parameter key="port" value="443" />
            <parameter key="url" value="/owa/auth/logon.aspx" />
            <parameter key="response" value="200" />  <!-- Exchange 2010: 200 OK is the expected value -->
            <parameter key="response-text" value="Outlook Web" />  <!-- Exchange 2010: "Outlook Web" is expected in returned HTML -->
            <parameter key="timeout" value="5000" />
            <parameter key="retry" value="2" />
        </service>
        <!-- Exchange 2013 OWA service poller -->
        <service name="MicrosoftExchangeOWA-HTTPS" interval="300000" user-defined="false" status="on">
            <parameter key="port" value="443" />
            <parameter key="url" value="/owa/auth/logon.aspx" />
            <parameter key="response" value="200" />  <!-- Exchange 2013: 200 OK is the expected value -->
            <parameter key="response-text" value="Outlook Web" />  <!-- Exchange 2013: "Outlook Web" is expected in returned HTML -->
            <parameter key="timeout" value="5000" />
            <parameter key="retry" value="2" />
        </service>

add these definitions in the existing “monitor” definition section of the same file

    <!-- Enable ongoing monitoring of an already discovered Microsoft Exchange OWA (Outlook Web Access) site accessed using HTTPS on the default port TCP 443 -->
    <!-- uncomment the following line if using Exchange 2007 -->
    <!-- <monitor service="MicrosoftExchangeOWA2007-HTTPS" class-name="org.opennms.netmgt.poller.monitors.HttpsMonitor" /> -->
    <monitor service="MicrosoftExchangeOWA2010-HTTPS" class-name="org.opennms.netmgt.poller.monitors.HttpsMonitor" />
    <monitor service="MicrosoftExchangeOWA-HTTPS" class-name="org.opennms.netmgt.poller.monitors.HttpsMonitor" />

Restart OpenNMS

service opennms restart