HP

Check your selections

The following steps are customized according to your selections. Check that your selections are correct.

If any selections are not correct, click Change.

Installation Requirements

During installation, the installer performs the following tasks:

Checks if your system meets the disk space requirements. For information on the disk space, see Hardware Requirements.
Checks if your system has any other HP software product installed. For example: HP vPV coexists with HP Operations Agent version 11.14.
Provides a detailed log of the system disk space and other HP software products detected.
Provides a list of components installed.

Note: HP vPV supports only x64-bit version of the Linux operating system.

The location of the following files used for HP Operations agent co-existence has been changed:

File Name	Old Location	New Location
Viserver.properties	/var/opt/perf	/var/opt/OV/conf/PV
VILog4j.xml	/var/opt/perf	/var/opt/OV/conf/PV
pvcd.jar	/opt/perf/bin/java	/opt/OV/lbin/PV/java
log4j-1.2.17.jar	/opt/perf/bin/java	/opt/OV/lbin/PV/java

Note: The common jars are moved to /opt/OV/lbin/PV/java. The jars specific to a technology are part of its SMEPack.

For Example: jars required by VMWARE collector are present in the java folder within the VMWARE SMEPack.

/opt/OV/newconfig/OVPM/smepack/VMWARE/java

Hardware Requirements

Item	Value
CPU	2 vCPU
Memory	4 GB
Disk	66 GB
/opt/	700 MB
/var/opt/OV	50 GB

License	vCPU	RAM	Disk Space	Instances Monitored
Express	2	4 GB	66 GB	2000*
Premium	2	4 GB	66 GB	1000

Supported Browsers

Operating System	Supported Browser
Microsoft Windows	Firefox 24 (ESR) Internet Explorer 10 Internet Explorer 9 (limited support) Google Chrome (latest version)
Linux	Firefox 24 (ESR)

Support Matrix

Deliverable	Platforms/Versions
Linux Installer	RHEL 6.4 (64-bit), 6.5 (64-bit) CentOS 6.4 (64-bit), 6.5 (64-bit) Oracle Enterprise Linux 6.5 (64-bit) (Red Hat compatible kernel) HP vPV does not support the unbreakable kernel (kernels with a uel/uek suffix).
Virtual appliance	CentOS 6.5

Prerequisites

HP vPV requires the following ports to be open on the firewall:

Port	Protocol	Description
8081	HTTP	To make HP vPV accessible from the remote browser, if there is a firewall on the system where HP vPV is installed.
8444	HTTPS	To access HP vPV in Hypertext Transfer Protocol Secure mode.
5480, 5488, and 5489	HTTPS	To access the Virtual Appliance Management Interface (VAMI).
383	HTTPS	For HP vPV internal communication process.
5433	HTTPS	For HP vPV database requirements (HP Vertica).
443	HTTPS	To ensure data collection from VMware vSphere targets.
5671	HTTPS	To ensure data collection from HP OneView targets.
135		To ensure data collection from Hyper-V targets. Port between Windows proxy system and Hyper-V host should be open on Hyper-V host.
22	SSH	To ensure data collection from KVM and Xen targets.
35357 (Admin), 8774 (Nova)	HTTPS	To ensure data collection from OpenStack targets.

Pre-requisites

HP vPV requires the following ports to be open on the firewall:

Port	Protocol	Description
8081	HTTP	To make HP vPV accessible from the remote browser, if there is a firewall on the system where HP vPV is installed.
8444	HTTPS	To access HP vPV in Hypertext Transfer Protocol Secure mode.
5480, 5488, and 5489	HTTPS	To access the Virtual Appliance Management Interface (VAMI).
383	HTTPS	For HP vPV internal communication process.
5433	HTTPS	For HP vPV database requirements (HP Vertica).
443	HTTPS	To ensure data collection from VMware vSphere targets.
5671	HTTPS	To ensure data collection from HP OneView targets.
135		To ensure data collection from Hyper-V targets. Port between Windows proxy system and Hyper-V host should be open on Hyper-V host.
22	SSH	To ensure data collection from KVM and Xen targets.
35357 (Admin), 8774 (Nova)	HTTPS	To ensure data collection from OpenStack targets.

Pre-requisites for Linux-Based Installer

Linux Types	OS Versions
CentOS	6.4 (64-bit) 6.5 (64-bit)
RHEL	6.4 (64-bit) 6.5 (64-bit)
Oracle Enterprise Linux	6.5 (64-bit) (Red Hat compatible kernel) HP vPV does not support the unbreakable kernel (kernels with a uel/uek suffix).

Pre-requisites for HP Vertica

HP vPV Virtual Appliance

You can download the HP vPV virtual appliance from: http://www.hp.com/go/vpv. You can install the HP vPV virtual appliance using the Deploy OVF Template functionality of the VMware vSphere client. To log on to the virtual appliance, the username is root and password is vperf*viewer. For more information, see the VMware documentation.

Deploy the HP vPV Virtual Appliance

HP vPV is available as a Virtual Appliance for easy deployment in vCenter. You can use the VMware vSphere Client user interface to deploy the virtual appliance.

The supported VMware vCenter Server versions are 5.0, 5.1, 5.5, and 6.0.

To deploy the HP vPV virtual appliance, follow these steps:

Open VMware vSphere Client.
Type the credentials and click Login.
Select File > Deploy OVF Template. The Deploy OVF Template window opens.
Click Browse to browse to the location where you have saved the HP vPV virtual appliance file.
Click Next. The window shows the details of virtual appliance.
Click Next. The End User License Agreement details appear.
Click Accept and then click Next.
Type a name for the virtual appliance in the Name field.
Select where to deploy the virtual appliance from the Inventory Location tree. Click Next.
Select the host or cluster where you want the virtual appliance to run. Click Next.
Select the specific host where to run the virtual appliance. Click Next.
Select the storage location where you want to store the virtual machine files. Click Next.
Select the disk format in which you want to store the virtual disks. Click Next.
Type the required Networking Properties and click Next. The window shows the details of the deployment.
Select the Power on after deployment check box.
Click Finish. The deployment task starts. After deployment, the virtual appliance name appears in the tree in the VMware vSphere Client user interface.

Note: For more information, see the VMware documentation. The steps are subject to change based on VMware.

Logging in to the Virtual Appliance

You can log in to the HP vPV Virtual Appliance using the username as root. The default password is vperf*viewer and it is recommended to change the password after logging in.

Upgrading HP vPV from version 2.10 to 2.20 using the Virtual Appliance

Note: You can upgrade HP vPV only from version 2.01 and 2.10 to 2.20. Upgrading HP vPV takes a significant amount of time. You cannot upgrade HP vPV from versions 1.00, 1.10, 1.20, and 2.00 to version 2.20. Also, make sure that you take a snapshot of HP vPV 2.01 or 2.10 machine before upgrading to 2.20 as rollback is not supported.

If you already have HP vPV version 2.10 deployed on the virtual appliance and want to upgrade to version 2.20, you can do it in the following two ways:

Using CDROM Updates (Using .iso)

Using Specified Repository (Using .zip)

Note: The VAMI web server configuration gets modified while upgrading a previous version of HP vPV to the latest version. The original configuration gets backed up before the modification. If you want to revert to the previous VAMI configuration, perform the following steps:

Log on to the HP vPV virtual appliance as root.
Run the following commands:
cp /opt/vmware/etc/lighttpd/lighttpd.conf.vPV cp /opt/vmware/etc/lighttpd/lighttpd.conf
/etc/init.d/vami-lighttp restart

Upgrading HP vPV from version 2.01 to 2.20 using the Virtual Appliance

If you already have HP vPV version 2.01 deployed on the virtual appliance and want to upgrade to version 2.20, you can do it in the following two ways:

Using CDROM Updates (Using .iso)

Using Specified Repository (Using .zip)

Log on to the HP vPV virtual appliance as root.
Run the following commands:
cp /opt/vmware/etc/lighttpd/lighttpd.conf.vPV cp /opt/vmware/etc/lighttpd/lighttpd.conf
/etc/init.d/vami-lighttp restart

Upgrading HP vPV from version 2.00 to 2.20 using the Virtual Appliance

If you already have HP vPV version 2.00 deployed on the virtual appliance and want to upgrade to version 2.20, you can do it in the following two ways:

Using CDROM Updates (Using .iso)

Using Specified Repository (Using .zip)

Removing HP vPV Virtual Appliance

To remove the HP vPV virtual appliance, power off the VM and delete the VM.

Unattended Installation

To perform unattended installation, follow these steps:

Login as a root user.
Download the .tar file. Extract the contents of the .tar file.
Go to the directory where the .tar file is extracted.
Type the following syntax at the command prompt:

./HPPV_2.20.xxx_setup.bin -i silent

Note: If the installer finds a working installation of HP vPV, it will uninstall HP vPV when you run the -i silent command. If not, it will install HP vPV.
To verify the installation, check the log files.

You can view the HP vPV installer log file at /tmp/HPOvInstaller/HPPVInstallLog.txt

Attended Installation using Graphical Interface

Installing HP vPV through Graphical Interface

To install HP vPV using X11 interface, perform the following tasks:

Login as a root user.
Download the .tar file. Extract the contents of the .tar file.
To start installation, if you want to use the X11 terminal window, export the DISPLAY variable to point to an X11 terminal type the following command:

export DISPLAY=<IP_Address/system_name>:0.0

where, <IP_Address/system_name> is the IP address or the system name of the X11 terminal.
Type the following:

<CD/DVD-ROM> HPPV_2.20.xxx_setup.bin

where, <CD/DVD-ROM> is the drive letter of the CD/DVD ROM.

The HP vPV Installation wizard appears. This window displays an introductory message.
Note: If you are installing HP vPV for the first-time on your Linux system, the ovinstallparams.ini file containing the installation parameters is created in the system’s temporary directory. During installation, HP Installer checks for the ovinstallparams.ini file. If HP Installer detects the ovinstallparams.ini file on your system, a message asking if you want to reuse the values in the file appears.
- Click Yes to use the values in the configuration file as default values.
- Click No to overwrite the existing configuration file.
If HP Installer does not find the file, the system creates the ovinstallparams.ini file with default values in the temporary directory. To save the ovinstallparams.ini data, copy the file to an alternate location, before installing other HP products.
If you have configured the locale of the system to one of the following languages: English, Japanese, and Simplified Chinese, the installer prompts you to select the language at the beginning of the installation. You will have the option of choosing the language to which your system locale is set. If the system locale is set to any other language apart from these, the installer displays only ‘English’.
On the HP vPV Installation wizard, click Next. The License Agreement screen appears.
Read the terms of license agreement. To continue with installation, select I accept the terms of License Agreement option. The installation wizard performs install checks.
Click Next. The Pre-Install Summary screen appears. The screen displays the list of components that will be installed.

Note: If HP vPV version 2.01 or 2.10 is present on the system, you would be asked to do a forced re-installation of already installed component packages.
Click Install.

Note: If the installation fails, you can roll back or quit installation. The Roll Back option removes the components which are already installed.

Clicking Quit stops the installation, but does not uninstall the components installed till then.

When you start HP vPV installation next time, the Installer prompts you to confirm if you want to resume the installation or uninstall HP vPV.
Click Details tab and expand the components tree to view the list of components.
To view the log file on your system, click View Log Files.
Click Done to complete the installation.

Note: If the system needs to be restarted, the following message appears after installation is complete: ‘You may need to restart your system for the configuration changes made to the system to take effect. Would you like to quit this installation?’.

It is recommended that you restart your system after installation.

Attended Installation using Command Line Interface

Note: Localization is not supported when installing HP vPV in console mode. As a result, some text may be illegible.

To install HP vPV through Command Line interface, follow these steps:

Login as a root user.
Download the .tar file. Extract the contents of the .tar file.
Run the following command:

If you are installing HP vPV on a stand-alone system:

<Directory where the tar file is extracted>/HPPV_2.20.xxx_setup.bin -i console

If you have configured the locale of the system to one of the following languages: English, Japanese, and Simplified Chinese, the installer prompts you to select the language at the beginning of the installation. You will have the option of choosing the language to which your system locale is set. If the system locale is set to any other language apart from these, the installer displays only ‘English’.
When the prompt, I accept the terms of the License Agreement for the License information appears, type Y to accept the terms and continue installation. The installer checks all the install requirements.
Click Enter to continue. The pre-installation summary appears.

Note: If HP vPV version 2.01 or 2.10 is present on the system, you would asked to do a forced re-installation of already installed component packages. Select Yes to continue.
Click Enter to continue.

When the installation is complete, you will receive a message which states that the installation was completed successfully.

Upgrading HP vPV from version 2.00 to 2.20 using the Installer

If you already have HP vPV version 2.00 installed in your environment and want to upgrade to version 2.20, you can upgrade using .tar or .iso. Download the .tar or .iso on your local machine and install HP vPV on the VM.

Upgrading HP vPV from version 2.01 to 2.20 using the Installer

If you already have HP vPV version 2.01 installed in your environment and want to upgrade to version 2.20, you can upgrade using .tar or .iso. Download the .tar or .iso on your local machine and install HP vPV on the VM.

Upgrading HP vPV from version 2.10 to 2.20 using the Installer

Removing HP vPV from Linux Nodes

To remove HP vPV from a Linux system:

Log on as root user.
Go to /opt/OV/Uninstall/HPPV.
Run the uninstall command:
- To use an X11 interface, export the DISPLAY variable to point to an X11 terminal if necessary. Then run the command:
  
  ./setup.bin
- To use a command line interface, run the command:
  
  ./setup.bin -i console
Select Uninstall.

Verify the Installation

On successful installation:

The Linux systems display the application directory and data directory paths.
To view install log files see the following:

For Linux: /tmp/HPPV_2.xx.xxx_HPPVInstaller.txt

/var/tmp/HPPVInstaller/PerfUtil-mm-dd-yyyy.log.0

In this instance, mm indicates the month, dd indicates the day, and yyyy indicates the year. The file name indicates the time stamp when the install was performed.

Configuring HP vPV to Communicate with Remote HP Vertica

To configure HP vPV to communicate with a remote instance of HP Vertica, perform the following steps:

On the machine where a database instance of HP vPV is to be created:

To create a database instance login to HP Vertica system, run the following command:
su <dbadminuser> -c "/opt/vertica/bin/adminTools -t create_db -s <hostname> -d pv -c <Vertica_DB_Path>/catalog -D <Vertica_DB_Path>/data"
In this instance,
the dbadminuser is the database administrator user.
the hostname is the host name or IP address of HP Vertica system.
the Vertica_DB_Path is the database path of HP Vertica.
For example, su dbadmin -c "/opt/vertica/bin/adminTools -t create_db -s 10.20.10.1 -d pv -c /vertica_disk/catalog -D /vertica_disk/data"
Create HP Vertica user. Run the following commands in sequence to create HP Vertica user with access to public schema:
- su <dbadminuser> /opt/vertica/bin/vsql –c “CREATE USER <UserName> IDENTIFIED BY '<Userpassword>'”
- su <dbadminuser> /opt/vertica/bin/vsql –c “GRANT ALL ON SCHEMA PUBLIC to <UserName>”
In this instance,
the dbadminuser is the database administrator user.
the UserName is the user name for the database instance.
the Userpassword is the password for database instance.

On HP vPV system:

Log on as root user.
Run the following command to stop ovtomcatB and pvcd processes:
/opt/OV/bin/ovc -stop
Run the following command to stop the local HP Vertica instance:
/opt/OV/bin/pv_vertica stop
Go to /var/opt/OV/conf/perf/
Open the PVHibernate.props file. Edit the following attributes in PVHibernate.props file:
1. Set hibernate.connection.url = jdbc:vertica://<IP Address>:<Port Number>/pv
  In this instance,
  the IP Address is the IP address of remote HP Vertica instance
  the Port Number is the port number of remote HP Vertica instance.
2. Set hibernate.connection.username=<User Name>
  In this instance,
  the User Name is the user name of remote HP Vertica instance.
3. Set hibernate.connection.password=<Password>
  In this instance,
  the Password is the encrypted password of remote HP Vertica instance.
  Note: To get the encrypted password, run the following command:
  pvconfig -en <password>
  In this instance, password is the decrypted password of remote HP Vertica instance.
Run the following commands to update the user name, password, and connection string in the configuration database:
1. ovconfchg -ns pvcd.dml -set username "<User Name>"
  In this instance,
  the User Name is the user name of remote HP Vertica instance.
2. ovconfchg -ns pvcd.dml -set password "<Password>"
  In this instance,
  the Password is the encrypted password of remote HP Vertica instance.
  Note: To get the encrypted password, run the following command:
  pvconfig -en <password>
  In this instance, password is the decrypted password of remote HP Vertica instance.
3. ovconfchg -ns pvcd.dml -set ConnectionString "DSN=Vertica;SERVERNAME=<IP Address>;PORT=<Port Number>;"
  In this instance,
  the IP Address is the IP address of remote HP Vertica instance
  the Port Number is the port number of remote HP Vertica instance.
Run the following commands in sequence to create database schema on HP vPV system:
- /opt/OV/bin/pvsql -f /opt/OV/newconfig/OVPM/vertica/CreateTables_Vertica.sql
- /opt/OV/bin/pvsql -f /opt/OV/newconfig/OVPM/vertica/DummyData_Vertica.sql
- /opt/OV/bin/pvsql -f /opt/OV/newconfig/DataDir/conf/PV/Model/DMLMetaMetaSchema
- /opt/OV/bin/pvsql -f /var/opt/perf/syspulse/scripts/createtable.sql
- /opt/OV/bin/pvsql -f /opt/OV/newconfig/OVPM/vertica/Create_Custom_Projections.sql
Run the following command to start HP vPV processes:
• /opt/OV/bin/pvconfig –um
• /opt/OV/bin/ovc –start

Configuring Secure Communication with Tomcat Server

The HTTPS protocol is by default enabled for HP vPV. The default port number for HTTPS is 8444. To access HP vPV in the secure mode, use the following URL:

https://<systemname>:8444/PV

You can also change the default port settings for HTTPS communications.

Changing Port Settings:

The default HTTPS port number to access HP vPV is 8444. All client systems are authorized to connect to HP vPV server. To change the default port number for the HP vPV server, follow these steps:

Check for the availability of the port number you want to use, by running the following commands at the command prompt:
cd <bin_dir>
ovtomcatbctl -checkport <portnumber>
A message indicating if the port is available or in use appears. For example, if you are checking for the availability of the port number 8444, the message, “Port Number 8444 is not in use” appears, if the port number is available. If the Port Number 8444 is not available, a message indicating that the port number is used by another program or service appears.
Stop HP vPV by running the following command at the command prompt:
pv stop
To change https port numbers for HP vPV server, run the following command at the command prompt:
cd <bin_dir>
ovconfchg -ns NONOV.TomcatB -set HTTPPort <port number>
ovconfchg -ns NONOV.TomcatB -set HTTPSPort <port number>
Start the HP vPV server by running the following command at the command prompt:
pv start

Using SSL or HTTPS with the Tomcat Web Server

To use SSL or HTTPS protocols with the Tomcat web server, you need to obtain a server certificate for Tomcat after installing HP vPV. You can replace the certificate obtained after HP vPV installation in the following scenarios:

When you connect to HP vPV using HTTPS protocol, the certificate and name of the system are compared to ensure that the names match. If the names are not similar, most browsers alert the users so that they can decide to either continue or cancel the connection. If the name used by HTTPS users is different from the name used by the HP vPV installation, you must obtain a different certificate.
You may need to obtain a new certificate when you want to fill the fields in the certificate that are left blank during HP vPV installation. The certificate contains many fields to provide information, such as, the issuer of the certificate and other fields that warrant the safety provided by the certificate. The HP vPV installation certificate leaves most of these fields blank.
When you want to change the default certificate password to avoid unauthorized changes, you must replace the existing certificate.

To replace the Tomcat SSL certificate, perform the following steps:

Delete the existing certificate by running the following command at the command prompt.
keytool -delete -alias ovtomcatb -keystore /var/opt/OV/certificates/tomcat/b/tomcat.keystore
The keytool path on Linux is /opt/OV/nonOV/jre/b/bin
Note: The password for deleting the certificate is changeit.
Restart HP vPV.
Create a new certificate. To create a new certificate, run Keytool by entering the following commands at the command prompt:
keytool -genkey -alias ovtomcatb -keyalg RSA -keystore /var/opt/OV/certificates/tomcat/b/tomcat.keystore
Restart HP vPV.

Adding a vCenter server running on a non-default port

vCenter Server system requires port 443, for connections from the vSphere and Software Development Kit (SDK) clients. By default, vCenter collector of HP vPV 2.20 uses port 443 for data collection from vCenter server. If this default port 443 is re-configured in your environment due to any reason, it is recommended to use the iptables to route the traffic.

During the HP vPV 2.20 installation, run the iptables command and setup port forwarding rules for each of the target.

Follow the steps:

Log on as a root user.
Run the following command:

iptables -t nat -A OUTPUT -p tcp -m tcp -d <target vcenter(s) ip> --dport 443 - j DNAT --to-destination <target vcenter(s) ip>:<target port>

In this instance, <target vcenter(s) ip> is the ip address of the target vCenter and <target port> is the port number of the target.

Troubleshooting

Vertica database is filled to near capacity due to the increase in the log file size.

Unable to Access HP vPV

Deployment of HP vPV fails

Unable to view content on HP vPV home page

HTTP Status 404 - /PV Error

What are the log files available with HP vPV?

Component	Description	Location
pvcd (PV Collectio n Daemon)	`pvcd` daemon uses XPL tracing mechanism. A default pvcdXPL.itc (trace configuration) is available in `/opt/OV/support` directory. To start the tracing, run `/opt/OV/support/ovtrccfg -app pvcd -cf /opt/OV/newconfig/conf/xpl/trc/pvc dXPL.itc` The XPL trace files are present at `/tmp/pvcd_*.trc`. To stop tracing, run `/opt/OV/support/ovtrccfg -app pvcd -off`	If tracing is enabled, `/tmp/directory` contains the trace files (use `- ls /tmp/pvcd_*.trc`)
`pvcd` and `pvconfig` tools log important status and error messages, if any, in `System.txt`.	`/var/opt/OV/log/System.txt`
Collectors	vCenter and OpenStack collector status log file `/var/opt/OV/log/status.virtserver`	`/var/opt/OV/log/status.virtserver`
KVM collector status log file	`/var/opt/OV/log/status.kvm`
XEN collector status log file	`/var/opt/OV/log/tmp/status.xen`
Database Transaction	Vertica catalog file to view database transactions	`/var/opt/OV/databases/pv/catal og/pv/v_pv_node0001_ catalog/vertica.log`
User Interface	Local trace and log messages are logged in `pvtrace.0.txt` and `ovpm.0.log`	`/var/opt/OV/log`

Using HP vPV Commands

After you install HP vPV, you can use the following commands to administer the HP vPV workspace through the command prompt.

<bin_dir>/pv <Options>

You can replace <Options> with any of the following variables:

status - To check the HP vPV status.
start - To start HP vPV.

All the applications that use OvTomcatB are started when you run pv start command.
stop - To stop HP vPV.

All the applications that use OvTomcatB are stopped when you run pv stop command.
restart - To stop and then start HP vPV.
trace on - To start generating detailed trace files.
trace off - To stop generating detailed trace files.
version - To display the version of HP vPV installed on your system.

Using HP vPV Licenses

After you install HP vPV, you can purchase the appropriate licenses based on your business requirements. These licenses enable you to access all the features of the product. To purchase the respective license, click You have Evaluation/Community license. Click to buy license link. The link navigates to the Buy License page. Enter your details in the Contact Me tab and click Submit. Make sure email client is configured in your browser.

To access the License option on the HP vPV user interface:

Log on to the HP vPV user interface.
Click the Settings icon.

The Settings page appears.
In the Settings page, click the License option.

The License page appears.

The License page provides information about your HP vPV licenses. You can also use this tab to start using your Evaluation License as well as import a HP vPV license.

Note: If you install an Express license on the HP vPV server which uses a Community license, then the Express license overrides the Community license. If you want to retain the Community license, create a separate HP vPV server to install the Express license. For more information on the difference between the licenses and the features available, see "Types of Licenses"

User Interface

Section	Description
License Status	The License Status section lists the following information about your current HP vPV license: Maximum number of OS instances that are provided by the active licenses Number of OS instances that are currently being monitored by the active licenses Data Retention If you have a Server Instance License enabled, you can see the total Server Instance capacity, the current Server Instance Count, and the OS instances that are covered by the Server license. License alert threshold
Installed License List	The Installed Licenses List section lists the following information regarding the active and all installed licenses for HP vPV. Type of license installed Date of license expiry

Types of Licenses

Feature	Community License	Express License	Premium License	Evaluation License	Monitoring License	Server License
Data Retention	Up to 24 hours	90 days	90 days	60 days	8 days	90 days
License Entitlement Period	Perpetual	Perpetual/Term	Perpetual/Term	60 days	Perpetual	Perpetual
Enterprise Directory Integration	No	Yes	Yes	Yes	No	Yes
Reports	Yes	Yes	Yes	Yes	No	Yes
HP OM, HP OMi, HP PM and HP BSM Integration	No	Yes	Yes	Yes	Yes	Yes
Monitoring	No	Yes	Yes	Yes	Yes	Yes
HP CSA Integration	No	No	Yes	Yes	No	Yes
Business Grouping	No	No	Yes	Yes	No	Yes
HP OneView Integration	No	No	Yes	Yes	No	Yes
Monitoring Physical Servers	No	No	Yes	Yes	No	Yes
Guest Operating System drill down for advanced troubleshooting	No	No	Yes	Yes	No	Yes
Current Capacity Reports (Only for VMware™ vSphere, Microsoft™ HyperV, and KVM)	No	No	Yes	Yes	No	Yes
Best-fit Capacity Optimization (Only for VMware™ vSphere, Microsoft™ HyperV, and KVM)	No	No	Yes	Yes	No	Yes
Virtual Machine Placement (Only for VMware™ vSphere, Microsoft™ HyperV, and KVM )	No	No	Yes	Yes	No	Yes
Capacity Demand Forecast (Only for VMware™ vSphere, Microsoft™ HyperV, and KVM)	No	No	Yes	Yes	No	Yes
Alerting (Only for VMware™ vSphere, Hyper-V, and KVM)	No	Yes	Yes	Yes	No	Yes
Capacity Modeler (Only for VMware™ vSphere and KVM)	No	No	Yes	Yes	No	Yes
Dashboard	No	No	Yes	Yes	No	Yes

Evaluation License

Monitoring Only License

Server License

Currently Active License	License Applied	Behavior
Community/Evaluation/Monitoring Only/Express	Server License	The Server license overrides the existing license. The total licensed instance count equals the OS instances covered by the Server license. Note: The data collection will stop if there are OS instances that are running on the servers not covered by the Server license. To start the data collection, you can install additional licenses with sufficient capacity.
Premium	Server License	The Server license co-exists with the Premium license. The total licensed instance count equals the OS instances covered by the Premium and Server license. Note: The OS instances that are running on the servers covered by the Server license will be deducted from the current OS instance count. This results in additional OS instance capacity.
Server License	Premium	The Server license co-exists with the Premium license. The total licensed instance count equals the OS instances covered by the Premium and Server license.
Server License	Community/Evaluation/Monitoring Only/Express	Not supported.

Importing Licenses

RPMs Packaged with the HP vPV Virtual Appliance

The RPMs packaged with the HP vPV Virtual Appliance are as follows:

setup-2.8.14-20.el6.noarch
basesystem-10.0-4.el6.noarch
tzdata-2012j-1.el6.noarch
glibc-common-2.12-1.107.el6.x86_64
ncurses-libs-5.7-3.20090208.el6.x86_64
libattr-2.4.44-7.el6.x86_64
zlib-1.2.3-29.el6.x86_64
audit-libs-2.2-2.el6.x86_64
popt-1.13-7.el6.x86_64
db4-4.7.25-17.el6.x86_64
nspr-4.9.2-1.el6.x86_64
bzip2-libs-1.0.5-7.el6_0.x86_64
libselinux-2.0.94-5.3.el6.x86_64
sed-4.2.1-10.el6.x86_64
glib2-2.22.5-7.el6.x86_64
gawk-3.1.7-10.el6.x86_64
sqlite-3.6.20-1.el6.x86_64
libxml2-2.7.6-8.el6_3.4.x86_64
libstdc4.4.7-3.el6.x86_64
dbus-libs-1.2.24-7.el6_3.x86_64
grep-2.6.3-3.el6.x86_64
findutils-4.4.2-6.el6.x86_64
cyrus-sasl-lib-2.1.23-13.el6_3.1.x86_64
libblkid-2.17.2-12.9.el6.x86_64
keyutils-libs-1.4-4.el6.x86_64
libgssglue-0.1-11.el6.x86_64
libgpg-error-1.7-4.el6.x86_64
vim-minimal-7.2.411-1.8.el6.x86_64
checkpolicy-2.0.22-1.el6.x86_64
sysvinit-tools-2.87-4.dsf.el6.x86_64
perl-Pod-Escapes-1.04-129.el6.x86_64
perl-Module-Pluggable-3.90-129.el6.x86_64
perl-libs-5.10.1-129.el6.x86_64
pth-2.0.7-9.3.el6.x86_64
keyutils-1.4-4.el6.x86_64
grubby-7.0.15-3.el6.x86_64
upstart-0.6.5-12.el6.x86_64
libusb-0.1.12-23.el6.x86_64
nss-softokn-3.12.9-11.el6.x86_64
xz-lzma-compat-4.999.9-0.3.beta.20091007git.el6.x86_64
MAKEDEV-3.24-6.el6.x86_64
net-tools-1.60-110.el6_2.x86_64
tar-1.23-11.el6.x86_64
pinentry-0.7.6-6.el6.x86_64
e2fsprogs-libs-1.41.12-14.el6.x86_64
which-2.19-6.el6.x86_64
diffutils-2.8.1-28.el6.x86_64
dash-0.5.5.1-4.el6.x86_64
groff-1.18.1.4-21.el6.x86_64
coreutils-libs-8.4-19.el6.x86_64
cracklib-2.8.16-4.el6.x86_64
coreutils-8.4-19.el6.x86_64
module-init-tools-3.9-21.el6.x86_64
redhat-logos-60.0.14-12.el6.centos.noarch
libpciaccess-0.13.1-2.el6.x86_64
rpcbind-0.2.0-11.el6.x86_64
nss-3.14.0.0-12.el6.x86_64
nss-tools-3.14.0.0-12.el6.x86_64
libuser-0.56.13-5.el6.x86_64
pciutils-libs-3.1.10-2.el6.x86_64
mingetty-1.08-5.el6.x86_64
ustr-1.0.4-9.1.el6.x86_64
libffi-3.0.5-3.2.el6.x86_64
newt-0.52.11-3.el6.x86_64
ca-certificates-2010.63-3.el6_1.5.noarch
python-libs-2.6.6-36.el6.x86_64
libssh2-1.4.2-1.el6.x86_64
curl-7.19.7-35.el6.x86_64
rpm-4.8.0-32.el6.x86_64
python-pycurl-7.19.0-8.el6.x86_64
gnupg2-2.0.14-4.el6.x86_64
pygpgme-0.1-18.20090824bzr68.el6.x86_64
yum-metadata-parser-1.1.2-16.el6.x86_64
yum-plugin-fastestmirror-1.1.30-14.el6.noarch
bind-libs-9.8.2-0.17.rc1.el6.x86_64
fipscheck-lib-1.2.0-7.el6.x86_64
kbd-misc-1.15-11.el6.noarch
policycoreutils-2.0.83-19.30.el6.x86_64
iproute-2.6.32-23.el6.x86_64
util-linux-ng-2.17.2-12.9.el6.x86_64
udev-147-2.46.el6.x86_64
plymouth-0.8.3-27.el6.centos.x86_64
dracut-004-303.el6.noarch
rsyslog-5.8.10-6.el6.x86_64
cyrus-sasl-2.1.23-13.el6_3.1.x86_64
cronie-anacron-1.4.4-7.el6.x86_64
crontabs-1.10-33.el6.noarch
nfs-utils-1.2.3-36.el6.x86_64
selinux-policy-3.7.19-195.el6.noarch
kernel-firmware-2.6.32-358.el6.noarch
dhclient-4.1.1-34.P1.el6.centos.x86_64
system-config-firewall-base-1.2.27-5.el6.noarch
bfa-firmware-3.0.3.1-1.el6.noarch
iwl100-firmware-39.31.5.1-1.el6.noarch
b43-openfwwf-5.2-4.el6.noarch
aic94xx-firmware-30-2.el6.noarch
iwl1000-firmware-39.31.5.1-1.el6.noarch
authconfig-6.1.12-13.el6.x86_64
gettext-0.17-16.el6.x86_64
grub-0.97-81.el6.x86_64
wget-1.12-1.8.el6.x86_64
passwd-0.77-4.el6_2.2.x86_64
audit-2.2-2.el6.x86_64
acl-2.2.49-6.el6.x86_64
ql2400-firmware-5.08.00-1.el6.noarch
ql2100-firmware-1.19.38-3.1.el6.noarch
libertas-usb8388-firmware-5.110.22.p23-3.1.el6.noarch
ql2500-firmware-5.08.00-1.el6.noarch
zd1211-firmware-1.4-4.el6.noarch
rt61pci-firmware-1.2-7.el6.noarch
ql2200-firmware-2.02.08-3.1.el6.noarch
ipw2100-firmware-1.3-11.el6.noarch
ipw2200-firmware-3.1-4.el6.noarch
vmware-studio-vami-tools-2.6.0.0-631426.x86_64
vmware-studio-vami-servicebase-2.6.0.0-631426.x86_64
vmware-studio-vami-service-system-2.6.0.0-0.x86_64
vmware-studio-vami-service-system-2.6.0.0-0.x86_64
vmware-studio-vami-service-system-2.6.0.0-0.x86_64
vmware-studio-vami-service-oaconfig-1.0.0.0-0.x86_64
vmware-studio-appliance-config-2.6.0.0-130820235403.noarch
vmware-studio-vami-login-2.6.0.0-631426.x86_64
libgcc-4.4.7-3.el6.x86_64
filesystem-2.4.30-3.el6.x86_64
ncurses-base-5.7-3.20090208.el6.x86_64
nss-softokn-freebl-3.12.9-11.el6.x86_64
glibc-2.12-1.107.el6.x86_64
bash-4.1.2-14.el6.x86_64
libcap-2.16-5.5.el6.x86_64
info-4.13a-8.el6.x86_64
libcom_err-1.41.12-14.el6.x86_64
chkconfig-1.3.49.3-2.el6.x86_64
libacl-2.2.49-6.el6.x86_64
nss-util-3.14.0.0-2.el6.x86_64
libsepol-2.0.41-4.el6.x86_64
shadow-utils-4.1.4.2-13.el6.x86_64
gamin-0.1.10-9.el6.x86_64
readline-6.0-4.el6.x86_64
xz-libs-4.999.9-0.3.beta.20091007git.el6.x86_64
libidn-1.18-2.el6.x86_64
file-libs-5.04-15.el6.x86_64
tcp_wrappers-libs-7.6-57.el6.x86_64
pcre-7.8-6.el6.x86_64
lua-5.1.4-4.1.el6.x86_64
bzip2-1.0.5-7.el6_0.x86_64
libuuid-2.17.2-12.9.el6.x86_64
expat-2.0.1-11.el6_2.x86_64
krb5-libs-1.10.3-10.el6.x86_64
elfutils-libelf-0.152-1.el6.x86_64
libtirpc-0.2.1-5.el6.x86_64
libselinux-utils-2.0.94-5.3.el6.x86_64
cpio-2.10-11.el6_3.x86_64
gdbm-1.8.0-36.el6.x86_64
perl-version-0.77-129.el6.x86_64
perl-Pod-Simple-3.13-129.el6.x86_64
perl-5.10.1-129.el6.x86_64
libgcrypt-1.4.5-9.el6_2.2.x86_64
dbus-glib-0.86-5.el6.x86_64
libnih-1.0.1-7.el6.x86_64
gmp-4.3.1-7.el6_2.2.x86_64
file-5.04-15.el6.x86_64
xz-4.999.9-0.3.beta.20091007git.el6.x86_64
libutempter-1.1.5-4.1.el6.x86_64
procps-3.2.8-25.el6.x86_64
psmisc-22.6-15.el6_0.1.x86_64
db4-utils-4.7.25-17.el6.x86_64
libss-1.41.12-14.el6.x86_64
m4-1.4.13-5.el6.x86_64
libgomp-4.4.7-3.el6.x86_64
binutils-2.20.51.0.2-5.36.el6.x86_64
ncurses-5.7-3.20090208.el6.x86_64
less-436-10.el6.x86_64
gzip-1.3.12-18.el6.x86_64
cracklib-dicts-2.8.16-4.el6.x86_64
pam-1.1.1-13.el6.x86_64
hwdata-0.233-7.9.el6.noarch
plymouth-scripts-0.8.3-27.el6.centos.x86_64
cvs-1.11.23-15.el6.x86_64
logrotate-3.7.8-16.el6.x86_64
nss-sysinit-3.14.0.0-12.el6.x86_64
openldap-2.4.23-31.el6.x86_64
libcap-ng-0.6.4-3.el6_0.1.x86_64
ethtool-3.5-1.el6.x86_64
libevent-1.4.13-4.el6.x86_64
libsemanage-2.0.43-4.2.el6.x86_64
slang-2.2.1-1.el6.x86_64
plymouth-core-libs-0.8.3-27.el6.centos.x86_64
openssl-1.0.0-27.el6.x86_64
python-2.6.6-36.el6.x86_64
libcurl-7.19.7-35.el6.x86_64
rpm-libs-4.8.0-32.el6.x86_64
rpm-python-4.8.0-32.el6.x86_64
python-urlgrabber-3.9.1-8.el6.noarch
gpgme-1.1.8-3.el6.x86_64
newt-python-0.52.11-3.el6.x86_64
python-iniparse-0.3.1-2.1.el6.noarch
yum-3.2.29-40.el6.centos.noarch
mysql-libs-5.1.66-2.el6_3.x86_64
fipscheck-1.2.0-7.el6.x86_64
centos-release-6-4.el6.centos.10.x86_64
iptables-1.4.7-9.el6.x86_64
iputils-20071127-16.el6.x86_64
initscripts-9.03.38-1.el6.centos.x86_64
libdrm-2.4.39-1.el6.x86_64
kbd-1.15-11.el6.x86_64
dracut-kernel-004-303.el6.noarch
openssh-5.3p1-84.1.el6.x86_64
postfix-2.6.6-2.2.el6_1.x86_64
cronie-1.4.4-7.el6.x86_64
nfs-utils-lib-1.1.5-6.el6.x86_64
iptables-ipv6-1.4.7-9.el6.x86_64
dhcp-common-4.1.1-34.P1.el6.centos.x86_64
kernel-2.6.32-358.el6.x86_64
selinux-policy-targeted-3.7.19-195.el6.noarch
openssh-server-5.3p1-84.1.el6.x86_64
iwl5150-firmware-8.24.2.2-1.el6.noarch
iwl6050-firmware-41.28.5.1-2.el6.noarch
iwl6000g2a-firmware-17.168.5.3-1.el6.noarch
iwl6000-firmware-9.221.4.1-1.el6.noarch
bind-utils-9.8.2-0.17.rc1.el6.x86_64
man-1.6f-32.el6.x86_64
libxml2-python-2.7.6-8.el6_3.4.x86_64
gdb-7.2-60.el6.x86_64
efibootmgr-0.5.4-10.el6.x86_64
sudo-1.8.6p3-7.el6.x86_64
e2fsprogs-1.41.12-14.el6.x86_64
attr-2.4.44-7.el6.x86_64
iwl5000-firmware-8.83.5.1_1-1.el6_1.1.noarch
ivtv-firmware-20080701-20.2.noarch
xorg-x11-drv-ati-firmware-6.99.99-1.el6.noarch
atmel-firmware-1.3-7.el6.noarch
iwl4965-firmware-228.61.2.24-2.1.el6.noarch
iwl3945-firmware-15.32.2.9-4.el6.noarch
rt73usb-firmware-1.8-7.el6.noarch
ql23xx-firmware-3.03.27-3.1.el6.noarch
rootfiles-8.1-6.1.el6.noarch
vmware-studio-init-2.6.0.0-130820235404.noarch
vmware-studio-vami-cimom-2.6.0.0-631426.x86_64
vmware-studio-vami-service-core-2.6.0.0-0.x86_64
vmware-studio-vami-service-network-2.6.0.0-0.x86_64
vmware-studio-vami-service-update-2.6.0.0-0.x86_64
vmware-studio-vami-lighttpd-2.6.0.0-631426.x86_64

Verify the Upgrade

You can verify the upgrade to HP vPV version 2.20 by performing either of the following:

In the HP vPV interface, go to the Help icon and click About HP vPV. A dialog box appears with the version information.
Verify the version by running the following command at the command prompt:

pv version

Note: After the upgrade, it is recommended to check the status of HP vPV processes using the following command:

/opt/OV/bin/ovc

If any of the processes are not running, run the following command to restart the processes:

pv restart

Symptom	Unable to access HP vPV through the default network port settings.
Causes	Your system has ovTomcatB configured to run with the non-root user or non-local system account privileges and you have HP vPV installed on such a system. You cannot access HP vPV using the default http (8081) or https (8444) ports if these ports are in use by other applications.
Resolution	Check if ovTomcatB is configured to run with the non-root user or non-local system account privileges. If so, modify the settings to run ovTomcatB with the Administrator or root user privileges. Try accessing HP vPV by using the following URL: `http://<IP address/system name>:<port number>/PV` where, <IP address/system name> is the IP address or the system name of the HP vPV server and <port number> is the port number of the HP vPV server. If the HP vPV Home page does not appear, check if the default ports are in use. To change the port settings, follow these steps: Run the following command at the command prompt to change the port numbers for HTTP, HTTPS, and ShutdownPorts: <bin_dir>ovconfchg -ns NONOV.TomcatB -set HTTPPort <port number> <bin_dir>ovconfchg -ns NONOV.TomcatB -set HTTPSPort <port number> <bin_dir>ovconfchg -ns NONOV.TomcatB -set ShutdownPort <port number> Restart HP vPV.

Symptom	HP vPV is unable to connect to the server through secure communication (HTTPS) protocol.
Causes	The connection times out when HP vPV is not able to connect through the secure client in the default timeout interval of one second.
Resolution	Use the parameter SECURE_CLIENT_CONNECT_TIMEOUT to adjust the timeout interval to connect to HP vPV server depending on your Internet connectivity or infrastructure setup.

Symptom	The deployment of the HP vPV Virtual Appliance fails.
Causes	This may happen when the time on the ESX server is set to a future time.
Resolution	Ensure that the time on the ESX server is set correctly.

Symptom	When trying to access HP vPV, you get the HTTP Status 404 - /PV Error message.
Causes	The message appears if the <INSTALLDIR>/www/webapps/PV directory is empty.
Resolution	Extract the Perf.war file again from <Install_Dir>/newconfig/PV to <Install_ dir>/www/webapps/PV. Run the command pv deploywar.

HP Virtualization Performance Viewer

For the Linux

Software Version: 2.20

vPV Interactive Installation Guide

Legal Notices

Warranty

Restricted Rights Legend

Copyright Notice

Trademark Notices

Documentation Updates

Documentation Updates

Support

Support

vPV Interactive Installation Guide

HP vPV Overview

Choose your Task

Choose your Installation Type

Choose your Upgrade Scenario

Choose your Installation Preference

Choose your Installation Preference

Choose your Configuration Task

Specify Other Installation Tasks

View or print

Check your selections

Installation Requirements

Prerequisites

Pre-requisites

HP vPV Virtual Appliance

Deploy the HP vPV Virtual Appliance

Upgrading HP vPV from version 2.10 to 2.20 using the Virtual Appliance

Upgrading HP vPV from version 2.01 to 2.20 using the Virtual Appliance

Upgrading HP vPV from version 2.00 to 2.20 using the Virtual Appliance

Removing HP vPV Virtual Appliance

Unattended Installation

Attended Installation using Graphical Interface

Attended Installation using Command Line Interface

Upgrading HP vPV from version 2.00 to 2.20 using the Installer

Upgrading HP vPV from version 2.01 to 2.20 using the Installer

Upgrading HP vPV from version 2.10 to 2.20 using the Installer

Removing HP vPV from Linux Nodes

Verify the Installation

Configuring HP vPV to Communicate with Remote HP Vertica

Configuring Secure Communication with Tomcat Server

Adding a vCenter server running on a non-default port

Troubleshooting

Using HP vPV Commands

Using HP vPV Licenses

RPMs Packaged with the HP vPV Virtual Appliance

Verify the Upgrade

Legal Notices

Warranty

Restricted Rights Legend

Copyright Notice

Trademark Notices

Documentation Updates

Documentation Updates

Support

Support