5.6
Table Of Contents
- VMware vCenter Configuration Manager Advanced Installation Guide
- Contents
- About This Book
- Achieving a Successful VCM Installation
- Hardware Requirements for Collector Machines
- Software and Operating System Requirements for Collector Machines
- Preparing for Installation
- System Prerequisites to Install VCM
- Configure Resources to Install VCM on a Virtual Machine
- Secure Communications Certificates
- Single-Tier Server Installation
- Configure a Single-Tier Installation Environment
- Verify that the Installing User is an Administrator
- Install and Configure a Windows Server 2008 R2 Operating System
- Install the .NET Framework
- Configuring the Database Components of the VCM Collector
- Configure the Web Components
- Configure SSRS on the VCM Collector
- Configure the VCM Collector Components
- Two-Tier Split Installation
- Configuring a Two-Tier Split Installation Environment
- Verify that the Installing User is an Administrator
- Install and Configure a Windows Server 2008 R2 Operating System
- Configuring the VCM Database Server
- Disable the Firewall or Add an Exception for SQL Server Port 1433
- Install SQL Server on the Database Server
- Verify and Configure the SQL Server Properties
- Verify Matching SQL Server and Computer Names
- Verify the SQL Server Agent Service Account is a sysadmin
- Select the SQL Server Agent Service Account
- Establish SQL Server Administration Rights
- Configure the Combined VCM Collector and Web Server
- Three-Tier Split Installation
- Installing VCM
- Configuring SQL Server for VCM
- Upgrading or Migrating VCM
- Upgrading VCM and Components
- Upgrading Virtual Environments Collections
- Migrating VCM
- Prerequisites to Migrate VCM
- Migrate Only Your Database
- Replace Your Existing 32-Bit Environment with a Supported 64-bit Environment
- Migrate a 32-bit Environment Running VCM 5.3 or Earlier to VCM 5.6
- Migrate a 64-bit Environment Running VCM 5.3 or Earlier to VCM 5.6
- Migrate a Split Installation of VCM 5.3 or Earlier to a Single-Tier, Two-Tier...
- How to Recover Your Collector Machine if the Migration is not Successful
- Maintaining VCM After Installation
- Hardware and Operating System Requirements for VCM Managed Machines
- VCM Agent Support on Non-English Windows Platforms
- VCM Managed Machine Requirements
- Windows Custom Information Supports PowerShell 2.0
- Supported OS Provisioning Target Systems
- Software Provisioning Requirements
- UNIX and Linux Patch Assessment and Deployment Requirements
- Support for VMware Cloud Infrastructure
- vCenter Operations Manager Integration Features
- FIPS Requirements
- Agent Sizing Information
- Hardware and Software Requirements for the Operating System Provisioning Server
- Installing, Configuring, and Upgrading the OS Provisioning Server and Components
- Index
n
IP Address: 10.11.12.1
n
Netmask: 255.255.255.0
OS Provisioning Network Port Usage
During the installation of OS distributions, internal application and services must communicate between
the OS Provisioning Server and the target machines. If there are firewalls or routers between the OS
Provisioning Server and the target machines, they must be configured to allow the following ports.
Application or Service Port Description
bootpd/DHCP UDP 68 Provides address and server location
of PXE configuration files.
TFTP UDP69 Downloads initial PXE/kernel.
http TCP 80 Downloads kickstart and package
files.
OS Provisioning Server 21307 Communication with the nodes,
including messages and registration
requests.
OS Provisioning Server 40610 Allows nodes to communicate with
OS Provisioning Server, including
messages and registration requests.
OS Provisioning Server Repository
Server
21307 OS Provisioning Server web service
listening for provisioning requests
from VCM.
OS Provisioning Server Hardware
Discovery
21309 Used by the hardware discovery
program to communicate with the
inventory daemon to add new
machines into the OS Provisioning
Server database.
VCM Linux Agent 26542 Used for communication between
VCM and the VCM Linux Agent.
Table 16–1. OS Provisioning Ports
Provisioning Network Firewall Configuration
As an alternative to setting the specific ports, as specified above, you can add -A RH-Firewall-1-INPUT
-i eth1 -j ACCEPT to the /etc/sysconfig/iptables firewall configuration file to allow traffic on
all ports on the provisioning network.
Configure the OS Provisioning Server Firewall
Configure the firewall on your OS Provisioning Server to allow proper communication on the required
ports.
Hardware and Software Requirements for the Operating System Provisioning Server
VMware, Inc.
172