Skip to main content
Kemp LoadMaster (now Progress Kemp LoadMaster) is the load balancer in front of many of your clients’ web, Exchange and application servers. Connect it for those clients, and Neo agents read which virtual services and real servers are up, check the appliance’s health and licence, and disable a real server for maintenance, then enable it again.

​
What Neo can do with Kemp LoadMaster

  • Read every virtual service and its real servers, with their status, and the up, down and disabled totals
  • Read statistics: connections per virtual service, CPU, memory, disk, network, RAID and the HA state
  • Read the licence, its type and end date, and the support end date
  • Disable a real server on one virtual service or on all of them, so it takes no new connections and its sessions drain, then enable it again
  • Enable or disable a virtual service
  • Ping or traceroute a real server from the LoadMaster
With the matching permission groups on, agents can also change virtual services, SubVSs and real servers, content rules, health checks, certificates, WAF, GEO, the network, HA, users and system settings. See Kemp LoadMaster API for the permission groups and profiles.

​
One connection per client

Each client’s LoadMaster has its own address and its own users, so you connect it once for each client that uses one, and the connection belongs to that client’s company in Neo. An HA pair is one connection, at its shared address. On a ticket that belongs to a company, the agent reaches only that company’s LoadMaster. Otherwise (a chat, a scheduled agent, or a ticket with no company) it names the client it works for, and Neo accepts only a company on your Companies tab.

​
Next steps

Connect Kemp LoadMaster

Turn on the LoadMaster’s API, make an API key for Neo and save it in Neo.