Veeam Home | Support | Downloads
Veeam Management Pack 8.0 for VMware User Guides

Veeam Management Pack Help Center  > Veeam MP for VMware Guides >  Installation Guide > Security Considerations > Network Protocols and Ports

Network Protocols and Ports

Previous page Next page Print this Topic

Table of contents

Data flows are shown in the architecture diagram in the Architecture Overview Guide. Connectivity is generally required between all Veeam MP for VMware components, and between Veeam MP for VMware components and vCenter Server. For considerations on using each method, refer to the Architecture Overview Guide. Typical connection settings are described below.

From

To

Protocol

Port

Notes

Veeam Collector

vCenter

HTTPS

443

Required for Veeam Collector to gather monitoring data. To check the current API port open in vCenter, see the VMware documentation.

VE Service

vCenter

HTTPS

443

Required to connect to vCenter from the Veeam UI.

Veeam Collector

VE Service

Secured TCP

8084

Required for VE Service to authenticate the Collectors, receive heartbeats, and to distribute licenses and other configuration. (port number can be chosen during setup).

Veeam UI

VE Service

Secured TCP

8084

Required for communications between VE Service and Veeam UI (port number can be chosen during setup).

Workstation Web browser

Veeam UI

HTTP

4430

Required to use Veeam UI from remote web browser (port number can be chosen during setup).

Veeam Collector

ESXi host

HTTPS

443

This port is optional; use it only if you need to connect the Collector directly to a vSphere host (see the Architecture Overview Guide).

VE Service

ESXi host

HTTPS

443

This port is optional; use it only if you need to connect VE Service directly to a vSphere host (see the Architecture Overview Guide).

Veeam Collector

ESXi host

UDP

514

This port is optional; use it only if Syslog is required. To allow outgoing syslog traffic, open this port on the ESXi host firewall.

Also make sure MTU settings on all ESXi hosts match MTU settings on the network hardware. Otherwise, VE Service and Veeam Collectors may not be able to correctly connect to the hosts.

If you want to monitor state of host hardware sensors using the CIM-XML method, follow the instructions in the Veeam MP for System Center Resource Kit Guide, Veeam VMware Advanced ESXi Hardware Monitoring (CIM-based) section, and open port 5989:

From

To

Protocol

Port

Notes

Veeam Collector

ESXi host

HTTP

5989

Required for gathering of SMASH hardware sensors via CIM-XML. Connection though proxy server is not supported, this must be a direct connection.

In addition, the following types of communication are used between the VE Service and Collector:

From

To

Communication Type

Notes

VE Service

Veeam Collector

Windows share

This communication type is used to create log bundle for the Veeam support, if required. Read permissions should be available.

VE Service

Veeam Collector

RPC

RPC is used for the remote control of the Collector service (start/stop/restart).

Table of contents