Submit a ticketCall us

Bridging the ITSM Divide
Integrated help desk and remote support software for faster resolution

Join us on Wednesday, November 29, 2017 at 11 a.m. CT, as we discuss the benefits of effectively integrating your help desk software with remote support solutions to help increase the efficiency of IT administration, improve communication, and decrease mean time to resolution (MTTR) for IT issues of all sizes. This directly impacts end-user satisfaction and your business’ bottom line. Register Now.

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

Excluding ESX hosts from VMAN monitoring to decrease used sockets

Table of contents
Created by Mark Aliola, last modified by christopher.roy on Nov 08, 2017

Views: 236 Votes: 2 Revisions: 10

Overview

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.

Environment

All VMAN versions where the data source is a vCenter.

Steps

  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 years 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

Tags

Classifications

Public