Submit a ticketCall us

Webinar: Web Help Desk for HR, Facilities and Accounting Departments
This webinar will focus on use cases for HR, Facilities and Accounting.

Having a unified ticketing and asset management system for all the departments in your company can provide end-users with a seamless experience and make things easier for your IT team. Yet, with different business tasks and objectives, many departments don’t fully understand the capabilities of Web Help Desk and how the software can be customized for effective use in their departments.
Register Now.

Home > Success Center > Server & Application Monitor (SAM) > SolarWinds guide to monitoring Exchange > Monitor Exchange network performance with NPM

Monitor Exchange network performance with NPM

When you add NPM to your comprehensive solution for monitoring Exchange, you can:

  • Monitor network paths from each office location to the load balancer. Make sure that the load balancer is accessible from all locations, and view the paths hop-by-hop to troubleshoot any issues.
  • View the health of the load balancer that splits traffic for your Exchange servers, and view relationships to virtual servers, pools, and individual pool members.

Monitor network paths

Use NetPath to monitor the paths from each local office to the Exchange load balancer. NetPath verifies that the load balancer is accessible from all locations, and helps you identify and troubleshoot any problem areas along the paths. For more information about NetPath, see Discover your network paths.

To monitor a path, you must create a service to define the end of the path (in this case, the Exchange load balancer), and install probes at the beginning of the path (in this case, each office location).

To monitor network paths to the Exchange load balancer, complete the following tasks:

  1. Complete the prerequisites.
  2. Create a service that defines the end of the path (in this case, the load balancer).
  3. Assign a probe from each office location to that service.

After you define the paths, you can monitor them.

NetPath tells you whether a service is reachable. For details about the load and speed, see Monitor the Exchange user experience with WPM.

Optionally, you can create paths between the Orion server and each Exchange server, which you can use to compare performance. The performance on each path should be about the same. This is important if you have a stretch DAG or multiple data centers in different locations and your databases are replicated between them.

Prerequisites for monitoring network paths

To configure NetPath to monitor the paths between office locations and the Exchange load balancer, you must:

  • Install NPM
  • Verify that the system meets the requirements for NetPath
  • Obtain the following information:
    • The IP address or host name of the Exchange load balancer, and the port (typically 443)
    • The IP address and credentials for servers at each office location where you want to install NetPath probes

      The probe is an agent you install in your local office. The probe sends packets to the destination IP address. SolarWinds recommends installing probes at each location where you have end users who consume Exchange services.

Create a NetPath service to the Exchange load balancer

A service defines the location at the end of the path (in this case, the Exchange load balancer). In this example, we create a service to the load balancer using the default NetPath probe, which is installed on the Orion server.

  1. In the Orion Web Console, click My Dashboards > Network > NetPath Services.
  2. Click Create New Service.
  3. Enter the host name or IP address and the port of the Exchange load balancer.

    File:Success_Center/Server_Application_Monitor_(SAM)/MonitoringExchange_MT_CHM/060/exchange-npm-netpath-create-service.png

  4. Enter an alias to identify this service. Click Next.
  5. Select the default probe, which is installed on the Orion server.

    File:Success_Center/Server_Application_Monitor_(SAM)/MonitoringExchange_MT_CHM/060/npm-netpath-select-probe.png

  6. Click Create.

    The NetPath Services view displays the new service.

If you don't have users in the Orion server location, you can remove this probe after you add other probes.

Assign probes from office locations to the service

Assign a probe from each office location to the service created in the previous task. Complete the following steps for each office location.

  1. On the NetPath Services view, click the plus icon for the service.

    File:Success_Center/Server_Application_Monitor_(SAM)/MonitoringExchange_MT_CHM/060/npm-netpath-assign-probe.png

    The Assign Probe dialog opens.

  2. If a probe is not already installed at the office location, click Create New Probe. Then enter the host name or IP address of the computer where you want to install the probe and the credentials to log in to that computer, and click Create.

  3. Select the probe and click Assign.

    File:Success_Center/Server_Application_Monitor_(SAM)/MonitoringExchange_MT_CHM/060/npm-netpath-assign-probe2.png

When the data is polled for the first time, click a probe to display the path.

Monitor a network path

NetPath shows the path from a probe to the destination of your service. You can resolve issues that you find on your network, or inform the node owner if you find issues on other networks.

  1. Click My Dashboards > Network > NetPath Services.
  2. Expand a service, and click a probe. The path is displayed. Use the icons on the left to show more or less detail about nodes on the path.

    File:Success_Center/Server_Application_Monitor_(SAM)/MonitoringExchange_MT_CHM/060/npm-netpath-show-detail.png

  3. In the Network Path graph, examine the hops. Position the cursor over the node to see details. Click a node group to expand the nodes.

    File:Success_Center/Server_Application_Monitor_(SAM)/MonitoringExchange_MT_CHM/060/exchange-npm-netpath-view-path.png

  4. If a node is on your network and you want to see more details, double-click the node.

    A detail panel opens on the left. (If the device is not monitored by the Orion platform, limited information is available.)

    File:Success_Center/Server_Application_Monitor_(SAM)/MonitoringExchange_MT_CHM/060/exchange-npm-netpath-add-to-orion.png

  5. To see details about an issue in the history, find the time of the issue in the Path History (1), and click a problematic time slot. Review the path from the past and locate the issue (2). To return to the current time, click Live Mode (3).

    File:Success_Center/Server_Application_Monitor_(SAM)/MonitoringExchange_MT_CHM/060/exchange-npm-netpath-history.png

Monitor F5 BIG-IP load balancers with Network Insight

If your Exchange configuration uses an F5 BIG-IP load balancer to route traffic to multiple Exchange servers, use Network Insight to monitor the health of elements in the load balancing environment and to see the relationships between these elements.

Prerequisites for monitoring F5 BIG-IP load balancers

Complete the following tasks, if you have not already done so:

Configure Network Insight to monitor BIG-IP load balancers

  1. Click My Dashboards > Network > Load Balancing.
  2. Click an item and select Show Relationships to filter the whole balancing environment and show only items relevant for the element.

    File:Success_Center/Server_Application_Monitor_(SAM)/MonitoringExchange_MT_CHM/060/exchange-npm-balancing-environment.png

    You can see details for all the elements in the hierarchy, down to the servers hosting mailboxes. In the details, you can see their IP addresses.

    File:Success_Center/Server_Application_Monitor_(SAM)/MonitoringExchange_MT_CHM/060/exchange-npm-balancing-environment-servers.png

  3. Drill in to the components with issues. Review the data provided by SolarWinds NPM, such as the status of load balancing components and the reason why they are not up. Use the data to troubleshoot the issues.

See Monitor BIG-IP load balancers for more information.

Next steps

To configure other modules for comprehensive Exchange monitoring, see any of the following topics:

After configuring one or more SolarWinds modules:

Last modified
20:13, 11 Dec 2016

Tags

Classifications

Public