HP Virtualization Manager 6.0 Software with Logical Server Management User Guide
Table Of Contents
- HP Insight Virtualization Manager 6.0 Software with Logical Server Management: User Guide
- Table of Contents
- 1 Introduction
- 2 Getting started with Virtualization Manager
- 3 Working with logical servers
- Using logical servers in Virtualization Manager
- New features in logical servers
- Understanding logical servers as they appear in visualization perspectives
- Logical server operations
- Authorizations, requirements, and configuration
- Logical server requirements
- Configuring and registering VMware vCenter
- Configuring VMware vSphere client settings for browsing datastore
- Configuring HP SIM with Onboard Administrator credentials
- Configuring HP SIM for SAN storage validation
- Configuring Extensible Server & Storage Adapter (ESA)
- Configuring Storage Provisioning Manager (SPM)
- LSMUTIL database utility
- 4 Defining storage for logical servers
- 5 Troubleshooting
- Navigation tips
- User preferences tips
- Performance tips
- Problems with meters collecting data
- Search button displays error page
- Displaying empty, hidden resource pools
- Errors accessing single sign-on iLO or Onboard Administrator
- Recovery after logical server operation failures
- Troubleshooting an inoperable logical server
- Correcting problems powering on a logical server
- Logical server operations cannot be cancelled
- Logical Server Automation service fails to start if TCP layer ports are in use
- Use portable WWNs and MAC addresses for Virtual Connect domain groups
- Do not use valid host name as logical server name
- Oversubscribing the number of networks
- Insufficient NICs error when activating or moving logical servers (Virtual Connect Flex-10 support)
- Use caution when renaming or moving a Virtual Connect domain group
- Deactivate or move logical servers before replacing blade
- Unmanaging a logical server using a storage pool entry may result in an inconsistent state
- Synchronize clocks on the CMS, managed systems, and VMware vCenter
- Ensure VM Hosts use fully qualified host names
- VM Hosts must be in same vCenter for ESX virtual machine logical server moves
- VM displayed without association in Virtualization Manager perspectives after deactivation
- Moving logical servers when the CMS and vCenter are in different network domains
- Changing the IP address of a VM Host after logical server discovery prevents the VM Host from appearing as an activation and move target
- Creating and managing logical servers on Microsoft Windows Hyper-V Server 2008
- 6 Advanced features
- 7 Support and other resources
- Index
Suggested Action Do not register the VM using the native virtualization console. The virtual
machine will be re-associated with the VM Host and the logical server when it is subsequently
activated.
Moving logical servers when the CMS and vCenter are in different network
domains
If you are moving an ESX virtual machine logical server, there may be a delay in the population
of possible target hosts if the CMS and vCenter are in different network domains (subnets).
Similarly, if you are moving the logical server using drag and drop, there may be a delay before
the hosts appear as valid targets.
Changing the IP address of a VM Host after logical server discovery
prevents the VM Host from appearing as an activation and move target
If the IP address of a VM Host is changed after it has been discovered by logical server
management, the logical server database is not updated with the new IP address. Attempts to
update the VM Host entry in the logical server database using the old IP address will fail, which
prevents the VM Host from appearing as a valid activation and move target. Additionally,
attempts to import virtual machine guests residing on the VM Host will fail.
To correct this problem, perform the following steps to purge the VM Host entry containing the
old IP address from the logical server database, and add a new entry with the new, correct IP
address.
1. Delete the logical server database by entering the following command:
C:\> LSMUTIL – deleteDB
IMPORTANT: This command deletes all logical servers and storage pool entries in the
logical server database. Only compute resources, storage, and networks found in the
datacenter will be rediscovered. Logical servers and storage pool entries must be manually
recreated.
2. Restart the HP Logical Server Automation Windows service.
Creating and managing logical servers on Microsoft Windows Hyper-V
Server 2008
This release includes support for creating and managing logical servers on Microsoft Windows
Hyper-V Server 2008 and Hyper-V Server 2008 R2.
Following are examples of restrictions on using Hyper-V Server 2008 with logical servers.
See the white paper Managing Microsoft Windows Server 2008 Hyper-V with HP Insight
Dynamics for information and restrictions about using logical servers on Hyper-V Server 2008.
• Logical server management does not allow you to create a Hyper-V virtual machine logical
server on a quorum disk or import a virtual machine with storage configured on a quorum
disk.
• After you have enabled High Availability (HA) on a logical server and allocated storage,
you cannot modify the logical server to disable HA. In addition, you cannot modify a non-HA
enabled logical server to enable HA. You enable HA by checking the Enable High Availability
checkbox in Step 1 of the Create Logical Server wizard when you have chosen a portability
group containing a Hyper-V hypervisor. Checking this box allows Hyper-V Quick Move
operations and enables failover clustering.
• When you are moving a High Availability-enabled Hyper-V virtual machine logical server,
only the Quick Move operation type is available. For non-HA enabled Hyper-V virtual
machine logical servers, only Copy Move is available.
Moving logical servers when the CMS and vCenter are in different network domains 87