vSphere Update Manager and the vCenter Support Tools - Mastering VMware vSphere 5.5 - page 133

Avoid Installing VUM on a VM That Sits on a Host That It Remediates

Be wary of installing VUM on a VM running on a host in a cluster that it is responsible for remediat-
ing. If DRS is disabled on the cluster at any stage, or the cluster has a problem migrating this VUM
VM to another host, then to prevent VUM from shutting itself down, the remediation will fail.

Table 4.1 shows the default ports that need to be opened if any of your components are sepa-
rated by a i rewall.

Table 4.1: Firewall requirements for VUM

Port Source Destination Protocol Description

80 VUM vCenter TCP Inter VUM-vCenter

communications

80, 443 VUM Internet TCP Retrieving updates and

metadata

902 VUM Hosts TCP Pushing upgrade fi les

8084 Client plug-in VUM TCP SOAP listening

9084 Hosts VUM TCP HTTP service for patch

downloads

9087 Client plug-in VUM TCP Uploading upgrade fi les

Confi guring VUM's Database
Like vCenter Server, VUM requires its own database. Where vCenter Server uses the database to
store coni guration and performance statistics, VUM uses a database to store patch metadata.

Supported Database Servers

VUM's database support is similar to that of vCenter Server but not identical. In general, most
versions of SQL Server 2005, 2008, and 2012 and Oracle 10 g /11 g are supported by VUM. For the
most up-to-date database compatibility matrix, refer to the latest vSphere compatibility matrixes ,
available from VMware's website.