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
You can globally define a storage tag and associate it with storage pool entries by pressing
Manage Tags on the Manage Storage Pools screen. This allows you to group storage pool entries
together, which becomes more important as the number of pool entries increases.
Virtual Connect logical servers are supported using shared (SAN) storage only. Virtual machine
logical servers are supported using file storage.
See “Defining storage for logical servers” (page 61) for more information.
Manage portability groups
The Modify→Logical Server Portability Groups... menu selection allows you to select systems
from the Virtualization Manager Physical and Virtual perspective that you want to include in
a user-defined portability group. A portability group defines the move and portability constraints
of a logical server.
Default portability groups are:
• Each Virtual Connect domain group
• All ESX hypervisors
• All Hyper-V hypervisors
• All Integrity VM hypervisors
NOTE: Default portability groups cannot be modified.
(Optional) User-defined portability groups are:
• A single Virtual Connect domain group
• A set of ESX hypervisors
• A set of Hyper-V hypervisors
NOTE: In this release, you cannot create a user-defined portability group containing HP Integrity
virtual machine hypervisors. If you import an Integrity VM, the imported logical server is placed
into the default “All Integrity VM hypervisors” portability group.
You may want to create a user-defined portability group to limit the number of servers or
hypervisors contained in a portability group. For example, if the default “All ESX hypervisors”
portability group contains a large number of virtual machines, you can create a portability group
that contains a smaller number of ESX virtual machines within which logical servers can move.
This may have the additional benefit of reducing the number of rejected targets when you move
the logical server.
You select a portability group for a logical server using the Create→Logical Server… menu
selection. The first screen, Create Logical Server Identity, displays a drop-down menu containing
all default and user-defined portability groups in the enclosure, with the exception of the default
“All Integrity VM hypervisors” group.
To create a user-defined portability group using the Modify→Logical Server Portability
Groups… menu selection:
• Select Virtual Connect domain groups or hypervisors to include in the portability group
from the Virtualization Manager Physical and Virtual perspective. If you do not make any
selections, all resources are presented as potential group members.
• The name that you select for your user-defined portability group is included in the drop-down
menu of available portability groups on the Create Logical Server Identity screen.
• The appropriate group types are checked automatically after you select the systems in the
Selectable Targets table that you want to move to the portability group, and you press the
Add Selection button.
46 Working with logical servers