6.3
Table Of Contents
- vRealize Operations Manager Installation and Configuration Guide for Linux and Windows
- Contents
- About Installation and Configuration for Linux and Windows
- Preparing for Installation
- About Linux and Windows Installation
- Complexity of Your Environment
- Cluster Nodes
- Requirements for IPv6
- Sizing the Cluster
- Custom Certificates
- How vRealize Operations Manager Uses Network Ports
- Platform Requirements for Linux
- Create a Node by Running the Linux Installer
- Platform Requirements for Windows
- Create a Node by Running the Windows Installer
- Creating the Master Node
- Scaling Out by Adding a Data Node
- Adding High Availability
- Gathering More Data by Adding a Remote Collector Node
- Continuing With a New Installation
- Connecting to Data Sources
- VMware vSphere Solution
- Endpoint Operations Management Solution
- Endpoint Operations Management Agent Installation and Deployment
- Prepare to Install the Endpoint Operations Management Agent
- Supported Operating Systems for the Endpoint Operations Management Agent
- Selecting an Agent Installer Package
- Install the Agent on a Linux Platform from an RPM Package
- Install the Agent on a Linux Platform from an Archive
- Install the Agent on a Windows Platform from an Archive
- Install the Agent on a Windows Platform Using the Windows Installer
- Installing an Endpoint Operations Management Agent Silently on a Windows Machine
- Java Prerequisites for the Endpoint Operations Management Agent
- Configuring JRE Locations for Endpoint Operations Management Components
- System Prerequisites for the Endpoint Operations Management Agent
- Configure the Endpoint Operations Management Agent to vRealize Operations Manager Server Communication Properties
- Activate Endpoint Operations Management Agent to vRealize Operations Manager Server Setup Properties
- Specify the Endpoint Operations Management Agent Setup Properties
- Configure an Endpoint Operations Management Agent Keystore
- Configure the Endpoint Operations Management Agent by Using the Configuration Dialog
- Overriding Agent Configuration Properties
- Endpoint Operations Management Agent Properties
- Encrypt Endpoint Operations Management Agent Property Values
- Adding Properties to the agent.properties File
- agent.keystore.alias Property
- agent.keystore.password Property
- agent.keystore.path Property
- agent.listenPort Property
- agent.logDir Property
- agent.logFile Property
- agent.logLevel Property
- agent.logLevel.SystemErr Property
- agent.logLevel.SystemOut Property
- agent.proxyHost Property
- agent.proxyPort Property
- agent.setup.acceptUnverifiedCertificate Property
- agent.setup.camIP Property
- agent.setup.camLogin Property
- agent.setup.camPort Property
- agent.setup.camPword Property
- agent.setup.camSecure
- agent.setup.camSSLPort Property
- agent.setup.resetupToken Property
- agent.setup.unidirectional Property
- agent.startupTimeOut Property
- autoinventory.defaultScan.interval.millis Property
- autoinventory.runtimeScan.interval.millis Property
- http.useragent Property
- log4j Properties
- platform.log_track.eventfmt Property
- plugins.exclude Property
- plugins.include Property
- postgresql.database.name.format Property
- postgresql.index.name.format Property
- postgresql.server.name.format Property
- postgresql.table.name.format Property
- scheduleThread.cancelTimeout Property
- scheduleThread.fetchLogTimeout Property
- scheduleThread.poolsize Property
- scheduleThread.queuesize Property
- sigar.mirror.procnet Property
- sigar.pdh.enableTranslation Property
- snmpTrapReceiver.listenAddress Property
- Managing Agent Registration on vRealize Operations Manager Servers
- Securing Communications with the Server
- Launching Agents from a Command Line
- Managing an Endpoint Operations Management Agent on a Cloned Virtual Machine
- Understanding Agent Uninstallation and Reinstallation Implications
- Install Multiple Endpoint Operations Management Agents Simultaneously
- Roles and Privileges
- Registering Agents on Clusters
- Manually Create Operating System Objects
- Managing Objects with Missing Configuration Parameters
- Mapping Virtual Machines to Operating Systems
- Endpoint Operations Management Agent Upgrade for vRealize Operations Manager 6.3
- Endpoint Operations Management Agent Installation and Deployment
- Installing Optional Solutions
- Migrate a vCenter Operations Manager Deployment into this Version
- Post-Installation Considerations
- Updating Your Software
- Index
Another approach to sizing is through self monitoring. Deploy the cluster based on your best estimate, but
create an alert for when capacity falls below a threshold, one that allows enough time to add nodes or disk
to the cluster. You also have the option to create an email notication when thresholds are passed.
Add Data Disk Space to a vRealize Operations Manager Linux or Windows Node
You add to the data disk of vRealize Operations Manager Linux or Windows nodes when space for storing
the collected data runs low.
The following example is for a Linux system. The Windows process is similar, but with Windows
characteristics such as backward slashes instead of forward slashes.
Prerequisites
Note the disk size of the analytics cluster nodes. When adding disk, you must maintain uniform size across
analytics cluster nodes.
Procedure
1 Add a new disk to the system, and partition and format the disk as needed.
2 Use the vRealize Operations Manager administration interface to take the cluster oine.
3 Stop the vmware-casa service.
4 Move the contents of /storage/db into a directory on the new disk.
5 Create a symbolic link from the new directory back to /storage/db, so that /storage/db now references
the new disk.
6 Start the vmware-casa service.
7 Bring the cluster online.
Custom vRealize Operations Manager Certificates
By default, vRealize Operations Manager includes its own authentication certicates. The default certicates
cause the browser to display a warning when you connect to the vRealize Operations Manager user
interface.
Your site security policies might require that you use another certicate, or you might want to avoid the
warnings caused by the default certicates. In either case, vRealize Operations Manager supports the use of
your own custom certicate. You can upload your custom certicate during initial master node
conguration or later.
Custom vRealize Operations Manager Certificate Requirements
A certicate used with vRealize Operations Manager must conform to certain requirements. Using a custom
certicate is optional and does not aect vRealize Operations Manager features.
Requirements for Custom Certificates
Custom vRealize Operations Manager certicates must meet the following requirements.
n
The certicate le must include the terminal (leaf) server certicate, a private key, and all issuing
certicates if the certicate is signed by a chain of other certicates.
n
In the le, the leaf certicate must be rst in the order of certicates. After the leaf certicate, the order
does not maer.
n
In the le, all certicates and the private key must be in PEM format. vRealize Operations Manager
does not support certicates in PFX, PKCS12, PKCS7, or other formats.
vRealize Operations Manager Installation and Configuration Guide for Linux and Windows
16 VMware, Inc.