HP Virtual Server Environment Management for Integrity Version 4.0 Release Notes

• Performing name changes on already licensed systems can cause them to disappear from
Virtualization Manager.
Workaround Rediscover the system using Option→Identify Systems.
• In order to perform operations on active logical servers such as an SMP migration, you must
select the physical blade or VM system from the Physical and Virtual perspective. Selecting
items on the Logical Servers perspective and invoking tools from the HP SIM tools menu
will not function properly in this release.
• For any HP SIM event that causes a per-node event to be generated for a virtual machine
(like creating or identifying a virtual machine), Virtualization Manager can temporarily fail
to display this virtual machine, and indicate it is unlicensed in the error popup—even if its
host is licensed.
Workaround Click the Refresh data icon.
• Performing an identify of a VM Guest (virtual machine) can temporarily cause the VM Guest
to not be displayed in Virtualization Manager.
Workaround Click the Refresh data icon in the Virtualization Manager tool bar to resolve
the issue.
• Occasionally, an error will appear in the mxdomainmgr.log file, beginning with the
following:
16:37:20,359 ERROR [[vmanview]] Servlet.service() for servlet vmanview threw exception
java.lang.IllegalStateException: Current state = FLUSHED, new state = CODING_END
...
This error may be safely ignored. It usually occurs when a connection from a web browser
is abruptly terminated during a transfer, such as when a user closes the browser window
while the page is being updated.
• Errors such as “Specified Vm Guest or Host [hostname] does not exist within VMM” and/or
“Could not initialize collector for system [hostname]” may be reported when using the
Virtualization Manager Visualization tab or the Capacity Advisor Tools→Collect Capacity
Advisor Data... menu to collect utilization data for systems that have been migrated from
an ESX Virtual Machine to either Microsoft Virtual Server (V2V) or to a physical/ProLiant
system (V2P).
These errors may be due to the "VMware ESX Guest" system subtype attribute persisting in
SIM after the migration.
Workaround In HP SIM, remove the “VMware ESX Guest” subtype for these systems.
1. Open the System Page for the system in HP SIM (for example, click the system name
from the All Systems view), select the Tools & Links tab, then click the Edit System
Properties link.
2. From the Edit System Properties page, change the “VMware ESX Guest” subtype to
“<make selection>”(this will remove the subtype).
NOTE: Uncheck the “Prevent the Discovery, Identification and Data Collection
processes from changing these system properties” checkbox before clicking OK to save
the change.
3. Reidentify the system in HP SIM after the subtype has been removed
Use the Quick Launch link from the System Page or use the HP SIM Options→Identify
Systems... menu.
If a node licensed for VSE is deleted and re-added with a different name, its license
state will not be reused. Workarounds for this include:
— For HP Integrity and HP 9000 systems, select the re-added system and use the
appropriate VSE Management for Integrity Licenses menu option to migrate
General 29