Submit a ticketCall us

Announcing NCM 7.7
With NCM 7.7, you can examine the rules that make up an access control list for a Cisco ASA device. Then you can apply filters to display only rules that meet the specified criteria, order the rules by line number or by the hit count, and much more.
See new features and improvements.

Home > Success Center > Storage Manager (STM) > SRM Profiler Administrator Guide > SRM Profiler system requirements > VMware requirements

VMware requirements

Table of contents
No headers

Updated: June 16, 2017

For SRM Profiler to reliably collect data from VMs, SolarWinds recommens that you do not exceed 300 VMs per 64-bit SRM Profiler proxy agents and 200 VMs per 32-bit SRM Profiler proxy agents. To accommodate failover situations, allow a margin of safety when calculating your VM per SRM Profiler proxy agent limits. If you are monitoring a cluster with more than 300 VMs, consider assigning SRM Profiler proxy agents to monitor specific hosts.

Versions/Models

4.0, 4.0i, 4.1, 4.1i, 5.0, 5.1, 5.5

Features

Asset - (VC, Cluster, ESX, and VM levels)

Storage - (VC, Cluster, ESX, and VM levels)

Performance - (VC, Cluster, ESX, and VM levels)

Capacity Planning

Requires SRM Profiler agent?

No

Prerequisites

Create user on Virtual Center with a role containing the following privileges

  • Datastore.browse
  • Global.Licenses
  • System.view
  • System.Anonymous
  • System.Read

Credentials

  • Run as root user on Unix/Linux
  • Local System account/Domain Account (Windows)
  • Account and password are stored in SRM Profiler database and configuration files on SRM Profiler proxy agent using custom encryption

Read/Write Actions

Read Only

Ports Used

  • Virtual Center: HTTPS Port 443
  • SRM Profiler Agent Ports

Requires SRM Profiler proxy agent?

  • Yes – Windows or Linux
  • SRM Profiler Proxy Agent must not be installed on the Virtual Center server
 
Last modified
15:35, 30 Jun 2017

Tags

Classifications

(not set)