HP Insight Dynamics 6.3 Release Notes

Moving a managed virtual machine guest using Microsoft SCVMM may change BIOS
serial number of logical server
On rare occasions, the BIOS serial number of a VM guest managed by logical server management
is changed if a file copy move operation is performed on the VM guest using Microsoft System
Center Virtual Machine Manager (SCVMM). This may cause operations on the virtual machine
logical server to be unsuccessful, or the virtual machine logical server may become inoperable.
Suggested action
Unmanage the logical server using the Virtualization Manager DeleteUnmanage Logical Server...
menu selection, then import the virtual machine as a logical server using ToolsImportLogical
Server... .
Incorrect hypervisor type assigned when a second hypervisor is installed on a server
If VMware ESX or ESXi is installed on a server where Hyper-V was previously installed, or if Hyper-V
is installed on a server where ESX or ESXi was installed, logical server management assigns an
incorrect hypervisor type to the second (new) hypervisor. This causes the import and activation of
logical servers to fail on the new hypervisor.
Suggested action
Remove the existing hypervisor from logical server management and add a new hypervisor with
the correct virtualization type:
1. In Systems Insight Manager, open the System Property Page of the newly installed hypervisor.
Identify the UUID of the hypervisor.
2. Run the following command (from the default location at C:\Program Files\HP\Virtual
Server Environment\bin):
lsmutil remove cr vm <uuid>
3. Refresh logical server Insight Control virtual machine management resources using
ToolsLogical ServersRefresh....
Cannot activate a virtual machine logical server when it contains multiple networks with
PXE enabled
If you attempt to activate a virtual machine logical server when it contains multiple networks and
at least one network is PXE enabled, the network that is PXE enabled must be the last network in
the network list. If it is not the last network in the list, activation fails at 90% complete, and the
.vmdk file is created but is immediately deleted from the datastore.
Suggested action
Modify the inactive logical server and select the Network tab. Change the values in the PXE
dropdown menu so that the last port is PXE enabled. (This does not affect the logical server.) Retry
the activation.
To prevent this issue from occurring, in Insight Orchestration, make sure that the PXE-enabled
network is listed last in the service template.
Viewing or editing the logical server management properties file may cause failure of the
LSA service
Viewing or editing the lsa.properties file may write lock the file while the HP Logical Server
Automation service is running. This may cause a serious failure of the service.
Suggested action
Use a text editor that does not lock the file, such as Emacs, Notepad, or TextPad.
36 Issues and suggested actions