This project is read-only.

Features

  • The MP monitors Kemp LoadMaster devices trough SNMP v2
  • Discover Kemp LoadMaster devices and their main properties
  • Discover Kemp LoadMaster Virtual Services and their main properties
  • Discover Kemp LoadMaster Real Servers and their main properties
  • Monitor State of Virtual Services and raise alerts upon failures
  • Monitor State of Real Servers and raise alerts upon failures
  • Gather performance data for Virtual Services
  • Gather performance data for Real servers
  • Knowledge base articles for monitors
  • added memory and processor monitoring
  • added a new dashboard view
  • fixed the discovery process
  • included Dashboard for squaredup console http://www.squaredup.com

Beware of the dependencies:

 

Tested environment:

  • Tested with Kemp LoadMaster devices with version 7.1-16 and higher
  • Tested with Kemp Virtual LoadMaster devices
  • Tested with Kemp LoadMaster clusters
  • Tested with SCOM 2012 R2 UR2

 

Guide to deploy

After importing the Kemp LoadMaster Monitoring MP please create override MP for storing your overrides also:

Kemp Override MP

Than you need to discover the Kemp LoadMaster devices with discovery rule in SCOM:

Discovery Rule

On the Kemp devices you have to configure SNMP and enable 161 and 162 port to SCOM Management Server/s.

If you have passive and active node of Kemp LoadMaster clusters you need to discover them trough the IPs on their management interfaces. Other way would be to discover only the VIP address but you would not be able to monitor individually as devices.

After around 10 minutes you will start seeing you Kemp LoadMaster devices discovered in Kemp views:

Kemp devices view

Kemp LoadMaster Virtual Services and Real Servers should also be discovered later:

Virtual Services View

 Real Servers View

You will also find performance Views and Active Alerts view. The following performance data is being gathered for Real Servers and Virtual Services:

  •  the total number of connections for Virtual Service
  •  the total number of incoming packets to Virtual Service
  •  the total number of outgoing packets from  Virtual Service
  •  the total number of incoming bytes to Virtual Service
  •  the total number of outgoing bytes from Virtual Service
  •  the current number of connections for Virtual Service
  •  the total number of connections for  Real Server
  •  the total number of incoming packets to Real Server
  •  the total number of outgoing packets from Real Server
  •  the total number of incoming bytes from Real Server
  •  the total number of outgoing bytes from Real Server
  •  the number of active connection for  Real Server
  •  the number of inactive connection for Real Server

If you want you can lower the time interval for detecting the states of Virtual Services and Real servers:

Virtual Service State Monitor

Real Server State

 

Known Issues

1. LoadMaster Virtual Services configured with sub Virtual services will be reported with State value 2 which is designated for out of service (unhealthy). In LoadMaster web interface those Virtual services will be show as healthy. This is identified bug by Kemp and it will be fixed in 7.1-20 release. I would recommend to disable the state monitors for those Virtual services or disable generating alerts for them as workaround. Should be fixed in v7.1-21.

2. Sometimes Virtual Services and Real Servers states are not synchronized between active and passive node of Kemp cluster. You will see alerts for states for one of the nodes but not for the other. In LoadMaster web interface those real servers and virtual services will be shown as healthy. After restart of the LoadMaster nodes states are synchronized. Case is logged to Kemp support and they are able to reproduce it. This is probably a bug in Kemp LoadMaster software. I would expect once they identify it as bug to fix it in upcoming release. Will be fixed in v7.1-24.

3. Upon initial discovery you may see some of these errors and warnings being logged on the SCOM Management Server/s:


Initialization of a module of type "SnmpDataSource" (CLSID "{0E6AF9F6-754A-42C8-A5D9-0AE71A53F96E}") failed with error code Unspecified error causing the rule "QND.NetworkDevice.LoadBalancer.Kemp.RSVS.TotalConnections.Rule" running for instance ".1.3.6.1.4.1.12196.13.2.1.1.73" with id:"{A7BCAC37-8636-DC74-5161-4E8D614F2AD5}" in management group "SCOM_MG".



Summary: 1 rule(s)/monitor(s) failed and got unloaded, 1 of them reached the failure limit that prevents automatic reload. Management group "CP_OM_D". This is summary only event, please see other events with descriptions of unloaded rule(s)/monitor(s).

 

Initialization of a module of type "SnmpAsyncProbe" (CLSID "{2B72C326-CDBB-421A-ACC3-A1994DBD52BB}") failed with error code Unspecified error causing the rule "QND.NetworkDevice.LoadBalancer.Kemp.RSVS.Details.3.Discovery" running for instance ".1.3.6.1.4.1.12196.13.2.1.1.87" with id:"{9F446EED-10F3-02FC-BB57-90772D4A672A}" in management group "SCOM_MG".

Ignore them. We are looking in fixing this issue in future release. Not applicable for v2

4. Kemp IP Virtual Service Optional Properties discovery is not working in this release. Do not enable it. Not applicable for v2

Last edited Oct 26, 2014 at 8:59 PM by slavizh, version 6