HP Matrix Operating Environment Software User Manual
HP Software
HP Matrix Operating Environment 7.2
Logical Server Management User Guide
Abstract
This document provides an overview of the HP Matrix OE logical server management features. System administrators can use
this document as an introduction to logical server management and as a guide to managing systems and workloads in the HP
Matrix Operating Environment.
HP Part Number: T8669-90088a
Published: March 2013
Edition: 2
Table of contents
Document Outline
- HP Matrix Operating Environment 7.2 Logical Server Management User Guide
- Contents
- 1 Managing logical servers
- Using logical servers in Matrix OE visualization
- Logical servers in visualization perspectives
- Logical server operations
- Authorizations, requirements, and configuration
- Logical server requirements
- Configuring and registering Hyper-V and ESX VM Hosts and VMware vCenter
- Configuring VMware vSphere client settings for browsing data store
- Configuring Systems Insight Manager with Onboard Administrator credentials
- Configuring Systems Insight Manager for SAN storage validation
- Configuring Storage Provisioning Manager (SPM)
- Configuring Extensible Servers & Storage Adapter (ESA)
- 2 Managing fluid cross-technology logical servers
- Restrictions on using cross-technology logical servers
- Integrity VM and HP-UX cross-technology logical servers
- Installing HP-UX portable Image
- Turning on HP-UX portable image in the OS
- Powering off HP-UX
- Network setup
- SAN fabric setup
- Setting up SAN fabrics on the VM Host
- Physical server to physical server SAN fabric setup
- HP Matrix OE logical server management storage volume requirements
- Matrix OE logical server management storage LUN format
- Configuring Integrity VM and HP-UX for cross-technology moves
- Operations and guidelines
- Configuration values that are not portable when moving Integrity or Integrity VM servers
- Defining portability groups
- Adding and removing target attributes
- Defining storage
- Defining a network
- Unmanaging a cross-technology logical server
- Moving a cross-technology logical server
- 3 Defining storage for logical servers
- 4 LSMUTIL database utility
- 5 Troubleshooting
- Removing a Hyper-V CSV volume may not remove the volume as an activation target
- Troubleshooting use of HP-UX portable image
- Catalog storage entries are not displayed in Select Storage Type menu
- Importing a Microsoft Hyper-V virtual machine with configuration file in default location is not supported
- Recovery after logical server operation failures
- Recovering an inoperable logical server
- Correcting problems powering on a logical server
- Errors accessing single sign-on iLO or Onboard Administrator
- Logical server operations cannot be cancelled
- Do not stop or restart Logical Server Automation service while operations are in progress
- Logical Server Automation service fails to start if TCP layer ports are in use
- Logical Server Automation service may run out of memory on large scale systems
- Error saving storage pool entry after Logical Server Automation service is restarted
- Restart Logical Server Automation service after VMware vCenter failure
- Profile is created but not associated with a logical server when service is stopped during logical server activation
- Creating VC Domain Groups using Factory-Default as a serial number
- Use portable WWNs and MAC addresses for VC 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 VC 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
- Storage pool entry status is “Presentation Completed with Errors – Inoperable” or “Presentation Completed – Inoperable”
- Logical servers are inoperable if they are associated with guests that use SLVM file-based storage
- Unmanaging a logical server leaves WWNs used by VC profile unavailable
- Synchronize clocks on the CMS, managed systems, and VMware vCenter
- Moving the data store of an ESX VM logical server
- VM Host does not appear on move logical server target screen
- Unable to import an Integrity VM logical server
- Failure during virtual machine deletion leaves active but unpowered logical server
- VM Hosts must be in same vCenter for ESX virtual machine logical server moves
- Performing operations on a logical server running as a VM host
- Moving logical servers when the CMS and vCenter are in different network domains
- 6 Support and other resources
- 7 Documentation feedback
- Index