Submit a ticketCall us

Training ClassSign up for Network Performance Monitor (NPM) and Scalability instructor-led classes

Attend our instructor-led classes, provided by SolarWinds® Academy, to discuss the more advanced monitoring mechanisms available in NPM as well as how to tune your equipment to optimize its polling capabilities. NPM classes offered:
NPM Custom Monitoring and Polling
Orion Platform Scalability

Reserve your seat.

Home > Success Center > Virtualization Manager (VMAN) > VMAN - Knowledgebase Articles > Excluding ESX hosts from VMAN monitoring to decrease used sockets

Excluding ESX hosts from VMAN monitoring to decrease used sockets

Table of contents

Updated January 30th, 2018 


This article describes a workaround to decrease the number of sockets used by excluding Hosts from monitoring.

This can be used when you have exceeded the socket count for your license entitlement in VMAN.


All VMAN Appliance versions where the data source is a vCenter.


  1. Open the vSphere Client.
  2. Expand the Host & Clusters until you locate the host you want to exclude.
  3. Right-click the host, and then click Add Permission.
  4. Add the user that VMAN uses for data collection.
  5. Assign a No Access role - this will exclude the selected Host from monitoring and data collection.


Please note, that it takes the VMAN appliance 48 hours by default to phase out objects that we can no longer see via permissions. This can be changed in the appliance web interface under Setup->Advanced Setup->System Properties by adjusting the Stale interval (The values are in hours).


Last modified