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 VSE Management Software 4.1 Update 1 Release Notes for HP-UX > Chapter 3 Known Issues

General VSE Software

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

For additional information not included in the online help and documentation for VSE Management Software, see VSE Management Software 4.1 Update 1 Documentation Addendum.

Major Issues

No general major issues have been reported for VSE software.

Minor Issues

  • Systems on the Workload Tab can Erroneously be Displayed as Unlicensed After Initial HP SIM Discovery  This occurs when systems initially get discovered by HP SIM horizontally (for example, via the enclosure for a blade, or via the management processor for a partitionable system). When the system (blade, nPartition, VM guest, etc.) is later explicitly added and fully discovered (hostname is now known), the Workload tab can lose the workload's association with the proper host. As a result, utilization data will not be displayed and the system will be incorrectly identified as not being licensed.

    Workaround  Even though utilization data is not displayed on the Workload tab, it is correctly displayed on the Visualization tab. After an HP SIM restart, data is properly displayed on the Workload tab as well.

  • Watch workload method failed” Message When Creating Sub-OS Workload Definitions for SELinux Managed Systems  

    Workaround  

    NOTE: To make sure the cause of the issue is related to write permission in /var/adm/util, check /var/log/messages for the following message (or similar):
    SELinux is preventing /usr/sbin/cimserver (pegasus_t) "write" access to util (var_t). For complete SELinux messages (...)
    Make sure that OpenPegasus has write access to /var/adm/util directory. If you are using SELinux execute the following command:
    # chcon -t pegasus_data_t /var/adm/util
    If you are using another security package, such as AppArmor, follow the specific rules for that tool to give OpenPegasus write access to this directory.

  • A Utilization Provider Running on the CMS May Fail with “CIM_ERR_FAILED” after an Upgrade or Reinstall of VSE  The HP Utilization WBEM Provider may fail to return utilization data for the CMS node (local host) after upgrading the CMS to VSE 4.1/ICM 3.0, or after uninstalling then reinstalling VSE on the CMS. The error displayed in the Visualization tab meter popup and/or output from capcollect command (or Collect Capacity Advisor Data menus) in this case, is:

    CIM_ERR_FAILED: [getObject] general

    Workaround  Restart the Utilization Provider service (WMIUtilProvider), or reboot the CMS.

    IMPORTANT: Wait at least five minutes after restarting the Utilization Provider service/rebooting the CMS before attempting to collect utilization data for the CMS node, otherwise collection may fail with a CIM_ERR_FAILED message.
  • Attempting to Migrate or Scan for HP-UX LTU's for Already Licensed Systems Can Fail  If a purchased permanent license is assigned to an HP-UX node and you subsequently run the vselicense -m command on this node (or press the Scan for HP-UX Licenses button in the VSE Management for Integrity software license screen or other variants), the command can fail because of the mix of purchased and migrated licenses.

    Workaround  If you wish to migrate or scan licenses from the node, do not assign licenses from a purchased key.

  • Some Messages from vselicense Command Point to Old Licensing Menu Items  When using the vselicense command, certain error messages that should refer the user to the Deploy->License Manager menu item in HP SIM, instead refer to the old menu items (Deploy->VSE Management for Integrity software...).

    Workaround  Use the Deploy->License Manager menu.

  • Running the vseassist Command Can “Lock” Capacity Advisor Consolidation Software licenses  When an HP Insight Capacity Advisor Consolidation Software license is assigned to a system, it should not be moved to the “used” state until the Capacity Advisor product is used to collect data from that node. Once Capacity Advisor is run against the system, the license can no longer be unassigned and reassigned to a different system; the license is locked to the system.

    Running the vseassist command for a system in this state likewise has the side-effect of locking the license to the system (and the clock starts ticking).

    Workaround  Do not assign a Consolidation Software license to a system until you are ready to use the license.

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