This text was hidden. Now it is visible. Click the link to hide the text.
This document is an overview of the features in HP Operations Smart Plug-in for Virtualization Infrastructure (Virtualization Infrastructure SPI). It contains important information that is not included in the manual or the online help. You can find information about the following in this document:
In This Version
Installation Notes
Verified Environments
Product Documentation
Known Problems, Limitations, and Workarounds
Documentation Updates
Local Language Support
Support
Legal Notices
To simplify navigation, individual Enhancement and Fix items are hidden until you click the link to expand the collapsed text.
Hidden text example
This text was hidden. Now it is visible. Click the link to hide the text.
Hidden text does not print. To print this document, you can expand selected links before you print or click the Show All button to expand all links. If you use Assistive Technology Tools, activate the Show All button to display all text.
HP Operations Smart Plug-in for Virtualization Infrastructure version 1.50 monitors the virtual infrastructure such as VMware ESX/ ESXi servers and Microsoft Hyper-V servers and the virtual machines hosted on them. It monitors the performance capacity utilization, availability, and resource consumption of the hosts and the guest virtual machines. The features provided by the SPI are detailed below:
When you add the VMware ESX/ ESXi servers or Microsoft Hyper-V nodes to the HPOM Nodes folder, first the Systems Infrastructure service discovery policy runs on it automatically. If it identifies the nodes as VMware vMA or microsoft Hyper-V, it initiates the deployment of Virtualization Infrastructure discovery policy on the nodes. The Virtualization Infrastructure discovery automatically adds the ESX/ESXi servers and guest virtual machines to the HPOM node bank.
For existing nodes, Virtualization Infrastructure discovery is not deployed automatically. You must manually deploy the following policies before you manually deploy the discovery policy.
Deploy the following policies on managed node:
• InfraSPI-Messages policy. To access this policy select Policy management >Policy groups> SPI for Infrastructure > en > Messages
• SI-SystemDiscovery policy. To access this policy select Policy management > Policy groups > SPI for Infrastructure > en > Systems Infrastructure > AutoDiscoveryDeploy the following policy on management server:
InfraSPI-ServerSetting policy. To access this policy select Policy management > Policy groups > SPI for Infrastructure > Settings and Thresholds > Server Settings
To access these policies select Policy management > Policy groups > SPI for Infrastructure > Settings and Thresholds > Agent Settings
Instructions for installing the Smart Plug-in for Virtualization Infrastructure are documented in the following guide provided in PDF (.pdf) format:
Before installing the Virtualization Infrastructure SPI, make sure that the following requirements are met. For the installation requirements for the management server, refer to the HP Operations Manager Release Notes.
HPOM management server requirements:
HPOM managed node requirements:
Disable Autodeployment on DCE agents
If you add a new node running DCE agent in the HPOM for Windows node bank, ensure that auto-deployment is disabled for the node. To disable autodeployment on DCE agents, follow these steps:
Repeat step 1 to step 5 for all managed nodes running DCE agents.
Verified HPOM versions on Management Server:
Verified operating systems on Managed/ Monitored Nodes:
| Operating System | Version |
| VMware ESX | 3.5, 4 |
| VMware ESXi | 3i, 4i |
| Microsoft Hyper-V server | 2008 |
To know about the supported operating system architectures, supported operating system release versions, and for recent updates, go to the support matrix URL:HP Software Support Matrix.
The following documentation is available for Virtualization Infrastructure SPI:
The following documentation is available for Virtualization Infrastructure SPI:
- HP Operations Virtualization Infrastructure Smart Plug-in User Guide
- HP Operations Infrastructure Smart Plug-ins Installation Guide
- HP Operations Infrastructure Smart Plug-ins Concepts Guide
Open issues in this release:
Guest virtual machines hosted on Hyper-V server do not get automatically added in the node bank during or post discovery (CR ID: QCCR1A95864) .
This happens due to unavailability of IP address of the guest virtual machines in WMI ( Microsoft Hyper-V limitation).
Workaround: Add the guests manually as SNMP/ Message-Allowed/ Managed nodes.
Advanced Monitoring policies modified in HPOM for UNIX Admin GUI fail to run after deployment to managed nodes.
When advanced monitoring policies are edited in GUI mode in HPOM for UNIX policy editor, syntax errors are induced into the Perl code module (CR ID: QCCR1A96995). This causes the policy to fail to execute. Errors such as the following appear:
"An error occurred in the processing of the policy 'SI-LinuxSshdProcessMonitor'. Please check the following errors and take corrective actions. (OpC30-797)
Error during evaluation of threshold level "Processes - Fill Instance list" (OpC30-728)
Execution of instance filter script failed. (OpC30-714)
Perl Script execution failed: syntax error at PerlScript line 11, near "1
#BEGIN_PROCESSES_LIST
#ProcName=/usr/sbin/sshd
#Params=
#Params=
#MonMode=>=
#ProcNum=1
#END_PROCESSES_LIST
@ProcNames"
Missing right curly or square bracket at PerlScript line 17, within string
syntax error at PerlScript line 17, at EOF
. (OpC30-750)"The un-edited advanced monitoring policies (Measurement Threshold type) work fine when deployed from HPOM for UNIX.
Workaround: To edit the settings in the Measurement Threshold policy, use ‘Edit in Raw mode’ feature of the HPOM for UNIX Admin GUI to change the policy contents. This requires you to know the syntax of the policy data file.
Infrastructure SPIs Measurement Threshold policies that use perl modules like OvTrace.pm, OvPrum.pm, etc do not work on x64 systems.
Workaround : Use the HP Operations Agent configuration setting MSG_NODE_INSTRUMENTATION_DIR to set the agent instrumentation directory location. For example:
[eaagt]
OPC_BUFLIMIT_SEVERITY=major
OPC_BUFLIMIT_SIZE=10000
OPC_HBP_INTERVAL_ON_AGENT=-1
OPC_INSTALLATION_TIME=7/9/2009 2:38:14 AM
OPC_INSTALLED_VERSION=08.60.005
OPC_IP_ADDRESS=192.168.0.0
OPC_NODENAME=YexampleY.com
OPC_NODE_CHARSET=utf8
OPC_PERL_LIB_DIR=C:\Program Files\HP\HP BTO Software\\nonOV\perl\a\lib
OPC_PERL_INCLUDE_INSTR_DIR=TRUE
MGD_NODE_INSTRUMENTATION_DIR=C:\ProgramData\HP\HP BTO Software\bin\instrumentation
Alert Messages while the Virtualization Discovery automatically does not automatically add nodes
The virtual machines are not added in the HPOM node bank by default during virtualization discovery although messages to add guests hosted by the ESX and ESXi systems are generated. You can ignore these messages. The auto-addition of virtual machines in the node bank is disabled to prevent a large number of virtual machines getting added in batch causing poor performance at the time of discovery. By default the XPL configuration setting on the HPOM management server infraspi.AutoAdd_Guests is set to false. You can set the value to true and re-run the action to enable the auto-addition feature. A convenient time may be chosen for running the auto-action.
HPOM Monitor Agent’s memory usage is constantly increasing to the point where the system runs out of memory and the monitor agent aborts
The root-cause for this problem is described in CR ID QCCR1A95505: opcmona has memory leak while processing policies with embedded Perl script. The issue is more prone to occur when you deploy many (30 or more) advanced monitoring policies using embedded Perl scripts. To check the status of this issue, see QCCR1A95505.
Non-root user support
Virtualization Infrastructure SPI supports policies and tools for alternative, non-root user on HTTPS agents running on the vMA systems, when the user is configured to run as vi-admin.
HP Operations Agent Certificates not installing on the vMA system
The iptable firewall runs on the vMA system by default blocking the communication over the network.
Workaround: Follow these steps for installing HP Operations Agent Certificates on the vMA system:
1. Open the TCP port (383) for HTTPS communication both ways (inward and outward).
2. Re-run the request to get certificates (ovcert –certreq) and bestow the certificate from the server.
For more information on port 383 and how to enable it, see HP Operations Manager Firewall Concepts and Configuration Guide.
The first page of this release notes document contains the following identifying information:
To check for recent updates or to verify that you are using the most recent edition, visit this URL: HP Software Product Manuals
To retrieve a document, select the:
You must have Adobe Reader installed to view files in PDF format (*.pdf). To download Adobe Reader, go to the Adobe web site.
The Smart Plug-in for Virtualization Infrastructure software and documentation are not provided in localized languages. However the SPI can be installed successfully and deployed on non-English HP Operations Manager for Windows, UNIX, and Linux servers.
This web site provides contact information and details about the products, services, and support that HP Software offers. For more information, visit the HP Support web site at: HP Software Support Online.
HP Software support provides customer self-solve capabilities. It provides a fast and efficient way to access interactive technical support tools needed to manage your business. As a valued support customer, you can benefit by being able to:
To access the Self-solve knowledge base, visit the Self-solve knowledge search home page.
Note: Most of the support areas require that you register as an HP Passport user and sign in. Many also require an active support contract. To find more information about support access levels, go to: Access levels.
To register for an HP Passport ID, go to: HP
Passport Registration.
©Copyright 2009 Hewlett-Packard Development Company, L.P.
Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license.
The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
The information contained herein is subject to change without notice.
Trademark Notices
Adobe® is a trademark of Adobe Systems Incorporated.
Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.
All other product names are the property of their respective trademark or service mark holders and are hereby acknowledged.
©Copyright 2009 Hewlett-Packard Development Company, L.P.