Submit a ticketCall us

AnnouncementsAre You “Flying Blind?”

When it comes to your complex IT infrastructure, you want to ensure you have a good grasp of what’s going on to avoid any fire drills that result from guesswork. Read our white paper to learn how proactively monitoring your IT environment can help your organization while giving you peace of mind.

Get your free white paper.

Home > Success Center > Network Performance Monitor (NPM) > NPM Documentation > NPM 12.4 Administrator Guide > Network Insight for F5 BIG-IP load balancers > Monitor load balanced services

Monitor load balanced services

Table of contents
No headers
Created by Caroline Juszczak, last modified by Magdalena.Markova on Nov 03, 2016

Views: 1,248 Votes: 0 Revisions: 5

A load-balanced service is comprised of many components that work together. The Balancing Environment resource allows you to browse all of these components and their relationships and status.

The page shows an overview of your load balancing environment.

At the top, you can see your load balanced services. Below Services, there are Global Traffic Managers (GTMs) that host the services. The GTMs send users to your Local Traffic Managers (LTM). Your LTMs present virtual servers which are made up of pools, and individual pool members hosting the content.


Dotted rectangles highlight high availability (H/A) clusters.

  1. Go to My Dashboards > Network > Load Balancing.
  2. Point to a service to review the tooltip.
  3. To see more detailed information about the component, such as the number of concurrent connections and the load balancing algorithm, click the service and select Display Details Page.


    The light blue square in the Balancing Environment resource indicates your current position.

  4. The relational view of the load balancing environment sticks with us on the details page so we can continue to explore around. Select a virtual server, and click Display Details Page. This shows us the number of active connections for each pool member. We can see the load balancing algorithm and how evenly it is distributing load.


  5. Navigate through the load balancing environment to view the health of individual components.
  6. 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.
Last modified