Submit a ticketCall us

Looking to compare latest NPM features with previous versions of NPM?
The NPM new feature summary offers a comparison of new features and improvements offered with this release.

 

Home > Success Center > Virtualization Manager (VMAN) > VMAN 7.1 Administrator Guide > Minimum requirements of Virtualization Manager > Port requirements for VMAN

Port requirements for VMAN

Created by Caroline Juszczak, last modified by MindTouch on Jun 23, 2016

Views: 10 Votes: 0 Revisions: 4

Review the following port requirements for the VMAN appliance, the Orion server, Federated Collectors, virtual environments, and additional systems. These ports are required for data collection and management actions.

Features and components affecting the port requirements of the Virtualization Manager appliance include:

  • VMware data collection
  • Hyper-V data collection
  • Active Directory and LDAP authentication
  • Sending email notifications (in alerting and reporting)
  • Sending SNMP traps (in alerting)
  • Orion integration
  • Federated collectors

Port requirements of the master appliance

Inbound ports on the master appliance

inbound port usage
443 or 80 Performing auto-upgrade or version upgrade on federated collectors, if federated collectors are configured.
8983 Access from federated collectors to the master appliance during initial setup.
443 HTTPS access to the Virtualization Manager user interface.
5480 HTTPS access to the Management Console.
61616 Active MQ master-collector communication.
22 SSH access to the virtual appliance.

Outbound ports on the master appliance

outbound Port Usage
162 Sending SNMP traps.
25 Sending emails through SMTP.
389 Active Directory authentication.
3268 LDAP authentication.
17778

Communication with the SolarWinds Orion server if the integration with Orion is enabled.

If you use Virtualization Manager integrated with NPM or SAM in an environment with multiple polling engines and federated collectors, open TCP port 17778 from the primary collector to every polling engine that is used to poll virtualization data.

123 Using the NTP service.

Port requirements of the federated collector

Inbound ports on the federated collector

Port Usage
5480 HTTPS access to the federated collector.
22 SSH access to the federated collector.

Outbound ports on the federated collector

Port Usage
61616 Active MQ master-collector communication.
443 or 80 Performing auto-upgrade or version upgrade.
8983 Access from federated collectors to the master appliance during initial setup.

Port requirements for data collection

Configure the following outbound ports on the master or the collector for data collection.

Port Usage
443 Data collection from ESX hosts and vCenters.
7 Access to Hyper-V hosts that were added by using a fully qualified domain name.
135 WMI data collection from Hyper-V hosts or VMs.
Dynamic RCP ports WMI communication. You can configure the available ports on the WMI target or policy.
 
Last modified
04:15, 23 Jun 2016

Tags

Classifications

Public