Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP Insight Dynamics – VSE for ProLiant 4.1 Update 1 Documentation Addendum > Chapter 2 Additional and Corrected Documentation

General VSE Software

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

The following is additional or corrected information for VSE Software.

  • Agentless Data Collection Failures Due to WMI Query Errors  The following information was not included in the HP Insight Dynamics – VSE for ProLiant Installation and Configuration Guide document.

    If agentless data collection fails due to WMI query errors, this may be because the WMI performance classes in Windows have been unregistered on the managed system, either by an inadvertent action by an administrator or a Windows problem. In this case, the error message displayed in the Visualization tab meter popups, and in stdout when running capcollect (either from a command prompt or from the Optimize->Capacity Advisor->Collect Capacity Advisor Data menu) is:

    An error occurred in one or more WBEM/WMI queries to host [hostname]. Some data may be unavailable/unreliable. 
    Verify that the correct version of WBEM/WMI is running on the host, then try restarting the CIM Server/WMI Service on the host.

    Following are corrective actions, any one of which may correct the problem.

    • Ensure that the correct version of WBEM/WMI is running on the managed system.

    • Restart the CIM Server/WMI Service on the managed system, as suggested in the error message.

    • Reboot the managed system.

    • Run the commandwmiadap /f on the managed system. This forces an update of WMI Performance Counter classes in Windows.

  • TCP Port 135 Must be Opened for Agentless Data Collection and WMI Access  The following information was not included in the HP Insight Dynamics – VSE for ProLiant Installation and Configuration Guide document.

    For VSE agentless data collection—and for general WMI access on Windows managed nodes from the CMS—the following port needs to be opened:

    TCP port 135 (WMI/RPC)

    NOTE: Additional ports may need to be opened for WMI/DCOM/RPC access. See the following MSDN article for details:http://msdn.microsoft.com/en-us/library/ms809327.aspx

    In addition, the WMI service (winmgmt) must not be disabled on any Windows systems configured for agentless data collection.

  • Encountered Exceptions on the VSE Integrity and HP 9000 Licensing Screens  If multiple browser windows or tabs are sharing the same user session while performing licensing operations, unexpected exceptions could occur.

    Only use separate browser sessions for the same user while performing licensing tasks on the Central Management System.

    Refer to the Web Browser Considerations help topic for more information.

  • Migrating and Applying Permanent Licenses Can Take a Long Time to Complete  Migrating old license types via the vselicense command and applying permanent licenses via the licensing screen can take a long time to complete.

    Printed statements and a progress bar are presented to indicate an estimated time until completion.

    This updates the information in the HP Insight Dynamics VSE and HP VSE Management Software 4.1 Getting Started Guide, the vselicense(1M) manpage, and theVSE Licenses help topic.

  • Inaccuracies in Related Information Section on Help Assistance Page  The Related Information section provided on the standalone (HP SMH) VM Manager and the VSE Management Software help “Assistance” topic include misinformation about online sources for documentation. The pages refer to a non-existent Product Information link at the following locations:

    • HP Virtual Server Environment (http://hp.com/go/vse)

    • HP Insight Dynamics – VSE (http://www.hp.com/go/insightdynamics)

    This should be corrected to instruct the reader to access the online documentation directly at the following websites:

    NOTE: The list of manuals listed in the Related Information section of these help pages omits the following manual:

    HP Integrity Virtual Machines Manager Version 4.0 Release Notes

  • Corrections to Procedures for Installing VSE agents to Linux Managed Systems  The following are corrections for the VSE Management Software online help “Installing Agents” topic.

    • Menu Changed for Installing Linux Agents  In the VSE Management Software online help “Installing Agents” topic, the reference in “Install Linux VSE Agents” to the menu item Configure->Configure VSE Agents->Install Integrity Linux Agents... should instead be Configure->Configure VSE Agents->Install Linux Agents.... This affects Procedure 3, “Install Linux Managed System Software from the CMS”.

    • Manual Installation of Linux Agents Applies to Both Integrity and ProLiant Linux Systems  In the VSE Management Software online help “Installing Agents” topic, the procedure for installing VSE agents manually to Linux managed systems indicates it applies only to Integrity systems. However, the procedure applies to both Integrity and ProLiant Linux systems. The procedure title should be “Procedure 6 Manual Installation of Linux Agents” (instead of “Procedure 6 Manual Installation of Integrity Linux Agents”).

    • Incorrect Procedure for Installing VSE Agents Manually to Windows Systems  In the VSE Management Software online help “Installing Agents” section, the “Manual Installation of Windows Agents” procedure for installing VSE agents manually to Windows systems is incorrect. To manually install Windows agents, use the following procedure.

      Procedure 2-1 Manual Installation of Windows Agents

      NOTE: To manually install VSE Assist, copy the setupva.exe file from the depot directory on the CMS to the managed system and run it. This is a self-executing installer.
      1. Copy the desired Windows install files (file.msi) from the depot directory on the CMS to C:\ on the managed system.

      2. Install the agents software using the msiexec command, as shown in the following example.

        C:\> c:
        C:\> cd \
        C:\> msiexec /I WMIUtilProvider32.msi /norestart

        This installs the agent interactively using the GUI and will prevent a reboot after installation. To install the agent with no interaction (quiet mode) and no GUI, use the /qn options with the msiexec command.

      3. Repeat the previous steps for each of the agents that you want to install.

  • Limitations for Japanese Online Help  The following limitations exist regarding the Japanese-localized help provided with this release of VSE software:

    • The VSE Management Software help is provided in English and Japanese. However, the help for the iCAP Manager product is not localized for Japanese. Only English help is provided for that component.

    • There are known problems with the search facility in the Japanese help. Using the search field in the Japanese help may not return a correct list of matching help topics.

      Alternatively, HP recommends using the “Index” link included in the left navigation under each product's list of topics, or the “VSE Master Index” link included in the top section of the left navigation.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2007–2009 Hewlett-Packard Development Company, L.P.