Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

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: 65 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

Port Protocol Service/
Process
Direction Description
22 TCP SSH

Inbound

SSH access to the virtual appliance

25 TCP   Outbound Sends emails through SMTP
123 UDP NTP Outbound Uses the Network Time Protocol (NTP) service
162 UDP   Outbound Sends SNMP traps
389 TCP, UDP   Outbound Active Directory authentication
443 HTTPS   Inbound HTTPS access to the VMAN user interface
443 or 80 TCP   Inbound Performs auto-upgrade or version upgrade on federated collectors if federated collectors are configured
3268 TCP   Outbound LDAP authentication and requests
5480 HTTPS   Inbound HTTPS access to the Management Console
8983     Inbound Access from federated collectors to the master appliance during initial setup
17777 TCP SolarWinds Information Service Bidirectional The port used for communication from your polling engine to the Orion Web Console, and from the Orion Web Console to your polling engine.
17778 HTTPS and TCP SSL Outbound

Communicates with the SolarWinds Orion server and SolarWinds Information Service 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.

61616 TCP   Inbound Active MQ master-collector communication

Port requirements of the federated collector

Port Protocol Service/
Process
Direction Description
22 TCP SSH

Inbound

SSH access to the federated collector

443 or 80 TCP   Outbound Performing auto-upgrade or version upgrade
5480 HTTPS   Inbound HTTPS access to the federated collector
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 Protocol Service/
Process
Direction Description
7    

Outbound

Access to Hyper-V hosts that were added by using a fully qualified domain name

135 TCP   Outbound WMI data collection from Hyper-V hosts or VMs
443 TCP   Outbound Data collection from ESX hosts and vCenters
Dynamic RCP ports     Outbound WMI communication. You can configure the available ports on the WMI target or policy.
 
Last modified
04:15, 23 Jun 2016

Tags

Classifications

Public