HP Matrix Operating Environment 7.0 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.
© Copyright 2006–2012 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Managing logical servers............................................................................6 Using logical servers in Matrix OE visualization............................................................................6 Logical servers in visualization perspectives..................................................................................7 Logical server operations...........................................................................................................9 Activate..
Configuring Integrity VM and HP-UX for cross-technology moves...............................................33 Operations and guidelines..................................................................................................33 Configuration values that are not portable when moving Integrity or Integrity VM servers.................34 Defining portability groups......................................................................................................
Importing an Integrity VM guest with no boot path............................................................77 Catalog storage entries are not displayed in Select Storage Type menu..........................................78 Importing a Microsoft Hyper-V virtual machine with configuration file in default location is not supported..............................................................................................................................78 Recovery after logical server operation failures...
1 Managing logical servers This document provides information about the logical servers features in the HP Matrix OE visualization software. System administrators can use this document as an introduction to visualization and as a guide to using logical servers. For information about using HP Matrix OE visualization, see the HP Matrix Operating Environment 7.0 Getting Started Guide.
• Increases business agility and flexibility by decoupling business processing from physical hardware, allowing you to respond to rapid changes in demand. • Reduces downtime required for physical system maintenance, whether planned or unplanned. • Allows for server consolidation and improved server utilization, which help to maximize limited compute resources.
Figure 1 Example logical server perspective In the logical server compartment, the name next to the check box is the logical server name. An inactive logical server displays Inactive Logical Server in parentheses next to the name. If the logical server is active, the information in parentheses depends on the logical server type. • An active Virtual Connect logical server displays, in parentheses, the server blade serial number, or the host name if an operating system has been provisioned.
Using the drag and drop function is equivalent to using the Tools→Logical Servers→Move... menu selection. Logical server operations You can perform several actions on logical servers from Matrix OE visualization. For a description of the Matrix OE visualization menu options that perform these tasks, see the HP Matrix Operating Environment 7.0 Getting Started Guide. A logical server can be active or inactive.
Deactivate The Tools→Logical Servers→Deactivate... menu selection removes the association between a logical server and a system. The storage configuration remains, maintaining the host name, IP address, and user information on the operating system boot image. • For servers with Virtual Connect, the blade is shut down and the server profile is disassociated from the blade. (The server profile is maintained, however, and can be reactivated elsewhere.
Operating system Operating system on the system on which you are creating the logical server. For a Virtual Connect logical server, the operating system you specify is used by VCEM to set the host mode in the storage array for proper presentation to the logical server.
When you activate a logical server on a virtual machine, the compute resources on the target host must be greater than or equal to the values you specify for number of cores and CPU frequency. When you activate a logical server on a server with Virtual Connect, the compute resources on the target host must be greater than or equal to the values you specify for number of cores, CPU Frequency, and amount of memory.
removes the physical server profile or virtual machine from the compute environment, and removes connectivity to storage and network devices. The Delete→Unmanage Logical Server... menu selection allows you to unmanage an active or inactive logical server. Unmanaging a logical server removes the logical server definition from the management database. The physical server or virtual machine is not modified or deleted; if it is running, it will continue to run.
portability group. A portability group defines the move and portability constraints of a logical server. NOTE: When using portability groups, consider the following: • A portability group member can be removed at any time as log as it belongs to a user-defined portability group, even if there are logical servers using it. (The member that was removed is no longer a suitable target for the logical server.
Modify The Modify→Logical Server... menu selection allows you to modify or view the details of an existing logical server. In general, you can modify only an inactive logical server. However, you can modify the description fields of an active logical server, and you can modify an active Virtual Connect logical server by adding a data volume to an existing SAN storage entry for the logical server.
Servers with Virtual Connect target hosts Target servers with Virtual Connect on which a logical server can be moved are shown in the Target Hosts table. Select one target blade in the Target Hosts table by clicking the radio button to the left of the target. Hover your mouse over the error symbols for more information. • Target hosts with the best fit are sorted to the top of the Target Hosts table. • Target hosts with an acceptable fit are shown with error symbols in the table columns.
Figure 3 Datastore menu selection Moving ESX, Hyper-V, and HP Integrity virtual machine logical servers If you are moving a logical server from one virtual machine to another, the following restrictions apply. • You can move virtual machine logical servers within a set of hypervisors of the same type (ESX, Hyper-V, Integrity VM). You cannot move virtual machine logical servers from one type of hypervisor to another type.
Virtual machine target hosts Target hosts on which a logical server can be moved are shown in the Target Hosts table. Select one target host in the Target Hosts table by clicking the radio button to the left of the target host. Hover your mouse over the error symbols for more information. • Target hosts with the best fit are sorted to the top of the Target Hosts table. • Target hosts with an acceptable fit are shown with error symbols in the table columns.
• Profile Move (Virtual Connect Only) Moves a server connection profile within a BladeSystem enclosure (Virtual Connect Domain Group). • Live Move (ESX VM, Hyper-V, and Integrity VM Only) Also known as Online Move. Moves a running virtual machine, its operating system, and its applications from one VM Host to another VM Host without an operating system reboot or application restart. All I/O connections to storage and networks remain active throughout the move.
Assign Logical Servers to Target Hosts screen. If you select Tools→Logical Servers→Refresh..., then Tools→Logical Servers→Activate..., the new VM Host will be an available target on which you can activate the logical server. The Tools→Logical Servers→Refresh... menu selection also allows you to reassociate all Virtual Connect logical servers from an old domain group to a new domain group. There are several check boxes in the Refresh Logical Servers screen.
Authorizations, requirements, and configuration To use the Logical Servers feature in Matrix OE visualization, you need the following authorizations: • The VSE All Tools authorization is required to operate on a logical server, regardless of the authorization required to operate on a specific host. • The VSE Monitor authorization is required to create and view a logical server, and to view a entry. • The VSE Storage authorization is required to manage storage pools and storage tags.
• Storage: ESX virtual machines whose boot and data storage are files within the hypervisor file system. That file system can be on local disk, FC SAN, HP SVSP, and iSCSI. Also supported are hypervisor file systems on NAS and virtual machines using Raw Device Mapping (RDM) to access a FC LUN directly. For more information, see “VM guest storage options ” (page 24).
– On the 11i v2 guests: PHSS_41415 1.0 HPVM A.04.20.05 vmGuestLib (Patch for A.04.20.05 VMGuestLib) PHSS_41416 1.0 HPVM A.04.20.05 vmTools (Patch for A.04.20.05 HPVM-Guest) – Logical Volume Manager (LVM) software Install LVM B.11.31.1010 on the VM Host. To locate LVM on the software depot website, go to http://software.hp.com and search for the keyword LVM. • Execute the Integrity VM hpvmhostgdev —a command to ensure that all devices are populated in the gdev database.
• ◦ Local storage is not supported for Integrity VM virtual machines. ◦ Suspend/Resume of Integrity VMs is not supported. ◦ For information on VM guest storage options, see “VM guest storage options ” (page 24). Network: ◦ Create an Integrity VM virtual machine logical server using Accelerated Virtual I/O (AVIO) network devices. The Integrity VM Host administrator must create all required virtual switches that will be used by Integrity VM guests before managing the Integrity VM Host.
Logical server management leverages Virtual Connect Enterprise Manager and Virtual Connect Manager to provide Virtual Connect based functionality. HP recommends that you are familiar with these technologies. See http://www.hp.com/go/vcem/ and http://www.hp.com/go/ bladesystem/virtualconnect for more information.
7. 8. On the Discovery page, select the newly created discovery task. Click the Run Now button. It will take a few minutes for the disk array(s) to be discovered into Systems Insight Manager. Configuring Storage Provisioning Manager (SPM) HP Storage Provisioning Manager (SPM) is a software tool that provides a service-centric management interface to storage, allowing storage requests to be fulfilled with available storage services from a storage catalog.
ESA is installed and configured with Matrix OE. This section includes ESA configuration details, so that you can change the default configuration if it is required in your environment. Configuring Operations Orchestration credentials in ESA For ESA to invoke OO workflows (for either server or storage workflows), it is necessary to configure the OO credentials. The assumption is that OO and ESA are installed on same CMS (Central Management Server).
#esa.oo.timeout.workflow – Presently not used. #esa.oo.retry.count – Presently not used. #esa.oo.syncpolling - This property is only for synchronous calls, and can be ignored as of now. #esa.oo.san.replytoURI - URI to which OO should call back for storage workflows. #esa.oo.server.replytoURI - URI to which OO should call back for server workflows. # esa.oo.communication.protocol=https esa.oo.admin.username=Admin esa.oo.admin.password=password esa.oo.host=xx.xx.xx.xx esa.oo.port=16443 esa.oo.service.ws.
2 Managing fluid cross-technology logical servers Heterogeneous server environments (multiple vendors, server types, product generations, and product families) exist in most datacenters. Cross-technology logical servers allow you to choose server configurations that make sense for your environment without having to consider the mechanics of moving images and the underlying technologies.
Table 5 Integrity VM and HP-UX logical server features (continued) Feature Description storage) and supports the following logical server operations: • Create • Modify • Delete • Activate • Deactivate • Import • Copy • Unmanage • Power on • Power off • Move NOTE: During logical server creation you can select SAN-based storage and configure the appropriate SAN ports and volumes the same way a Virtual Connect server would use them.
Installing HP-UX portable Image The HP-UX portable image product is a key component of the Integrity VM and HP-UX cross-technology logical server feature. It provides the necessary operating system support to ensure network configuration information is properly maintained across cross-technology move operations. You must configure this product as part of your HP-UX installation. It is part of the Base OE for 1103, 1109, and future Fusion releases.
Setting up SAN fabrics on the VM Host The following commands must be entered to set a SAN fabric name on Integrity VM Hosts being used for NPIV life cycle operations and cross-technology logical server move operations: NOTE: Before setting up the fabric names on the Integrity VM Hosts, ensure that the names being used match exactly with the names of the VC FC SAN fabric for cross-technology logical server move operations.
Matrix OE logical server management storage LUN format It is critical to ensure that the storage LUN that is configured as part of the Logical Server Creation Wizard be in VSA mode to avoid problems with HP-UX. Figure 4 illustrates where and how to set the LUN. Figure 4 Setting the LUN in VSA mode The LUN number set in Create Storage Entry should be in VSA mode. For example, if the LUN number is 2 then use 4002000000000000. Physical to physical moves will not work properly if this format is not followed.
Table 6 Cross-technology logical server operations (continued) Operations Notes Memory Yes Yes Network Yes No Server WWN Yes No Storage port WWN Yes Yes Delete Unmanage Activate Deactivate Copy Import Import of Integrity VM guests with SAN-based or NPIV-based storage requires that a valid primary boot entry be configured in the VM guest.
◦ Power management settings such as capping and regulation ◦ WOL settings ◦ WSMAN settings ◦ UID LED settings ◦ Network settings (LAN, SSH and web ports) ◦ Access settings (telnet/ssh/web) ◦ Inactivity timeouts ◦ DNS settings ◦ Time and date ◦ Serial port settings ◦ Logs Defining portability groups Use the Modify→Logical Server Portability Groups… screen to define a greater range of mobility for logical servers.
You may want to create a user-defined portability group to: • Enable cross-technology moves of logical servers, for example, from a server with Virtual Connect to an ESX virtual machine. • Limit the number of servers or VM Hosts contained in a portability group.
Figure 7 Manage portability group screen Press the Modify or Create Group button to display the Modify Portability Group screen. On the Modify Portability Group screen, select Virtual Connect domain groups or VM Hosts to include in the portability group from the HP Matrix OE visualization Physical and Virtual perspective. If you do not make any selections, all resources are presented as potential group members.
Figure 9 Modify target attributes menu Types of target systems can be added to or removed from the logical server’s target attributes. Selecting a server from the Target Attributes Available to Add table adds that type of server with its associated resources to the list of most suitable targets for the logical server. Selecting a type of server from the Target Attributes Available to Remove table causes the specified type of server to no longer be considered most suitable.
are potential targets for the logical server. Storage pool entries must be created within the same portability group as the logical server(s) that will use the storage. See “Defining storage for logical servers” (page 41) for more information. Defining a network You create a network definition for a cross-technology logical server in the same way as you do for standard logical servers, using Create→Logical Servers… and specifying information on the Network screen.
c. d. e. Specify the appropriate Architecture and Operating System for a Virtual Connect logical server and click Next. On the Compute Resources screen, specify the appropriate compute resources, and click Next. On the Storage screen, select a pool entry from the drop-down menu and press Insert Pool Entry. (If you have not previously configured a storage pool entry, press Cancel and use the Modify→Logical Server Storage Pools...
3 Defining storage for logical servers This chapter presents underlying concepts to provide a better understanding of how a given storage definition maps into the physical Virtual Connect environment, and explains how to define storage entries and storage pool entries for a logical server. NOTE: For more information about logical server and Matrix infrastructure orchestration storage, including integrating with non-HP servers and HP rack mount servers, see the following white papers at http://www.hp.
bays on its backplane. (For detailed information on this mapping, see the HP BladeSystem c-Class Enclosures documentation.) Storage in a Virtual Connect environment Storage in a Virtual Connect environment is often housed within storage area networks (SANs), which are accessed through Fibre Channel connections. Using SAN storage has many advantages, including allowing a seamless system failover from one server blade to another in the case of a failure.
Logical server storage Matrix OE allows you to logically represent your storage environment in a logical server storage configuration. A logical server completely defines your storage, including all Fibre Channel ports, fabrics, server WWNs, storage WWNs, volumes, and LUNs. For server with Virtual Connect logical server storage, HP recommends Fibre Channel Storage Area Network (SAN) with boot-from-SAN capability.
SAN Pre-populated Catalog Storage Pool Entry (Server with Virtual Connect logical servers only) Allows you to select storage that was preconfigured in HP Storage Provisioning Manager. All volumes are already presented to WWNs, and the WWNs are displayed with the volumes. Add a volume, select a candidate for the volume and a storage port WWN, and the rest of the information is filled in automatically. Use this storage type to ensure that unmanaged arrays in SPM are returned as candidates.
You can select catalog storage for the storage pool entry if you preconfigured storage using HP Storage Provisioning Manager. See “Storage Provisioning Manager” (page 58) for more information. See “Using LSMUTIL with logical server storage” (page 65) for information about using the LSMUTIL database utility to define storage for logical servers. Create a storage entry A storage entry is associated with one logical server.
IMPORTANT: If you configure your Virtual Connect logical server to use a local disk, you cannot move that logical server. Additionally, after you activate the logical server, you cannot reactivate it on a different system. Perform the following steps to define a SAN or RDM storage entry. 1. Enter the “SAN storage entry definition” (page 46) 2. Enter the “Port definition” (page 46) 3. Enter the “Volume and path definition” (page 47) 4.
1. 2. 3. Click the Add Port button to add a row to the Port Selection table. You add a maximum of two ports. Select a value from the Fabric drop-down menu. Select a value from the Speed drop-down menu. For Fibre Channel ports, select 1Gb, 2Gb, 4Gb, or Auto (FC). For Fibre Channel over Ethernet (FCoE) ports, select 1Gb, 2Gb, 4Gb, 8Gb (FCoE) or Custom (FCoE) from the drop-down menu. If you select Custom (FCoE), enter a port speed in the text box. Custom port speed values can be 0.1 through 10.
1. 2. 3. 4. 5. 6. 7. 8. 9. Click the Add Volume button to on the right side of the screen to add a row to the Volume & Path Selection table. Select a value from the Boot Volume drop-down menu. Select Yes if the volume is a boot volume. Select No if the volume is a data volume. Enter the size in GB for the storage volume. (Size is typically 10-30 GB.) Select a RAID Level for the storage volume. The default is None.
Figure 17 Create file (VM) storage entry File (VM) storage entry definition 1. 2. Optional: Change the name of the storage entry by typing in the name box. Each storage entry is given a unique default name. Optional: Enter a description for the storage entry. File (VM) storage selection 1. 2. 3. Click the Add Storage button to on the right side of the screen to add a row to the Storage Selection table. Enter the size in GB for the storage selection.
A logical server can be associated with multiple storage pool entries. Multiple logical servers can share the same storage pool entry. You can configure catalog storage using HP Storage Provisioning Manager. You can then specifying catalog storage options on the Add/Modify Add/Modify Storage Pool Entry: SAN screen. See “Storage Provisioning Manager” (page 58) for more information. To create a storage pool entry before or after you create a logical server, use the Modify→Logical Server Storage Pools...
Figure 18 Manage storage pool screen Associating a storage pool entry with a logical server When you create a logical server, you can select a storage pool entry as the storage configuration for the logical server by performing the following steps from the Create→Logical Server... storage configuration screen. 1. Select a storage pool entry from the drop-down menu. Only entries whose operating system matches the operating system specified for the logical server will be available for selection.
Defining a SAN storage pool entry Whether you are defining a storage entry during logical server creation or defining a storage pool entry, the process of defining and creating storage is essentially the same. An exception is that catalog storage options are displayed only on the storage pool entry screen. Perform the following steps to define a SAN Storage Entry, SAN Catalog Storage Entry, or SAN Pre-populated Catalog Storage Entry. 1. Enter the “Storage pool entry definition” (page 52) 2.
Figure 20 Add storage pool entry definition and tag selection Port definition On the Storage Entry: SAN and Add/Modify Storage Pool Entry: SAN screens, the Port Selection table allows you to define the ports that can be used to access the volume selections for this logical server. Any communication with SAN storage starts with the server’s Fibre Channel ports. Ports are added in sequential order. For each port, you must select the fabric from a drop-down menu with which the port will communicate.
definition. You can also use Storage Provisioning Manager to streamline this process. See “Setting up SPM for use with logical server storage” (page 26) for more information. This information includes: • Storage WWN, uniquely identifying the port used to communicate with the SAN • LUN, uniquely identifying the created volume within the SAN Using these two pieces of information, the path to the LUN is unique within the FC environment.
l. When the value in the Status column is Presentation Completed, press the Modify button on the Manage Storage Pool screen to display this screen. m. Select a Storage Port WWN from the drop-down menu and press Save. 2. For SAN Catalog Storage Entry: a. Click the Add Volume button on the right side of the screen to add a row to the Volume & Path Selection table. b. Optional: Check the Redundancy check box next to a specific volume to implement redundancy for that volume. c.
IMPORTANT: For SAN Catalog Storage Entries and SAN Pre-populated Catalog Storage Entries, the Remove Volume action returns the storage volume to the storage catalog as an available resource. Unmask catalog-based storage volumes before removing the storage volumes. For non-boot volumes, uncheck the Masked check box. For boot volumes, use HP Storage Provisioning Manager to change the presentation state of the storage volume.
IMPORTANT: You must check the Ready check box next to each server WWN before the storage pool entry can be shared by logical servers. The Ready check box is grayed out and checked by default for a SAN Catalog Storage Entry and a SAN Pre-populated Catalog Storage Entry. For a SAN Storage Entry and a SAN Catalog Storage Entry, after presentation is complete, modify the storage pool entry, select a Storage Port WWN from the drop-down menu and press Save.
The following HP storage solutions are required to take advantage of the storage validation feature of Matrix OE: • • MSA1000/1500 and MSA2000fc G2 ◦ Using explicit or default mapping ◦ MSA SMI-S provider version 1.1.2 or later EVA 3000/5000, 4x00/6x00/8x00, P6300/P6500 ◦ Command View versions 9.1, 9.2/9.21, 9.3, 9.
a smaller number of volumes to be pre-provisioned, with Matrix Operating Environment adjusting the host mode as appropriate when a storage pool entry is affiliated with a logical server. LUN masking can be used to ensure a data volume is made invisible prior to operating system deployment, and then made visible again after successful operating system installation without requiring manual intervention by the storage administrator.
Figure 25 Relationships between the applications, servers, and arrays comprising the overall SPM environment NOTE: Modular Smart Arrays (MSAs) are not supported in the current release of SPM. Operations Orchestration workflows The standard Matrix OE solution provides out-of-the-box support for HP BladeSystem c-Class servers using Virtual Connect and the HP EVA storage solution (which can be bundled as part of HP CloudSystem Matrix).
The following sections describe the Extensible Server and Storage Adapter (ESA) component of the Matrix OE solution, configuration steps, and how the server and storage workflows can be customized. Extensible Server & Storage Adapter Extensible Server & Storage Adapter (ESA) provides storage provisioning and server operations for logical servers and HP Insight Orchestration. Matrix OE includes reference implementations which can be customized for specific environments.
4 LSMUTIL database utility LSMUTIL command LSMUTIL is a script that you can run from the command line or from a DOS bat file. LSMUTIL reads information from the logical servers tables in the Matrix OE database. Based on the option you select, the script exports information about logical servers and storage pool entries, or updates the system with information imported from a specified XML file.
Table 8 LSMUTIL options (continued) Option Parameters Description The following list defines the export parameters: • The available parameter—Available storage pool entries are listed. • The vm parameter— Virtual Machine based storage pool entries are exported. • The vc parameter—Virtual Connect based storage pool entries are exported. • The oowf parameter—Operations Orchestration workflow based entries are exported. The parameter [names] can be the names of storage pool entries in a comma separated list.
Table 8 LSMUTIL options (continued) Option Parameters Description • The vc parameter—Virtual Connect based storage pool entries are listed. • The oowf parameter—Operations Orchestration workflow based storage pool entries are listed. If the -details parameter is supplied, a detailed list of storage pool entries is displayed. This listing is best used in conjunction with the names parameter to locate the details of a particular SPE.
LSMUTIL example C:\>lsmutil -list -ls Logical Server List on host labmachine at 2011-01-17 10:05:46 Server Name VCDG Storage WWN testls_esx_inactive Type Arch ESX ProLnt NEW testls_esx_nosan ESX ProLnt NEW testls_hyperv_active HyperV ProLnt ACTIVE testls_hyperv_inactive HyperV ProLnt INACTIVE testls_vc_active Cup1 50:06:0B:00:05:00:00:44 testls_vc_inactive Cup1 50:06:0B:00:05:00:00:3E State VCBlade ProLnt ACTIVE 50:06:0B:00:05:00:00:46 VCBlade ProLnt NEW Using LSMUTIL with logical server s
Table 9 LSMUTIL storage options LSMUTIL option Purpose -export –spe Export storage pool entries into an XML file, which can be modified and then imported. 1 NOTE: The -export –spe only exports a subset of the information concerning a catalog-based (SPM-based) storage pool entries. It exports all of the information as displayed with other storage pool entries, but it does not export the information that is particular to a catalog-based storage pool entry.
in the XML file is used to update the storage pool entry (for example, by adding information such as storage controller port WWN and LUN number, and perhaps defining additional ports and WWNs). An example XML file is shown in Example 2 “Example XML file for storage import and export”.
Example 1 Storage definition XSD file PAGE 69
Example 2 Example XML file for storage import and export PAGE 7140 GB data, 10 GB boot disk 151 razorsaw UNKNOWN false Linux 1 2 40000 GB 0 0 NONE false false
1 false 0 LSA_SAN_A 1 50:xx:xx:xx:xx:xx:xx:xx 1 50:xx:xx:xx:xx:xx:xx:xx 50:xx:xx:xx:xx:xx:xx:xx true false Modifying physical servers with local disk information In a Virtual Connect environment, the Matrix OE software
size of the local disk in MB. If set to a negative number, the local disk is set to default values upon import. The and values can be set as appropriate for the customer environment. Other fields, such as , , and , should be left unspecified. The other properties found in should not be changed (name, uuid, and portabilityGroupID). “Example filename.
3. 4. Browse to the physical servers that you want to change by looking for either the UUID or the server name.
5 Troubleshooting This chapter covers some of the issues that can occur when you are using logical servers, and provides the troubleshooting steps you need to correct the problem. Troubleshooting use of HP-UX portable image Boot path requirements Logical servers experience boot problems when no long form EFI boot path exists. Symptoms include failure to boot and physical to virtual move failures with the following error message: Failed to Update the VM's Resources.
Error: [addVirtualSystemResources] : Failed to Add the VM's Resources. Exception: Unable to add guest resources - Network device add failed.) A message similar to the following also appears in the Integrity VM command.log (/var/opt/hpvm/common/command.log): 09/01/11 10:40:38|ERROR|host|root|Invalid Ethernet MAC Address '0x00215A9B0004' - Linkloop failure. Activation of a logical server on an Integrity VM can fail when performing the following procedure: 1.
The setup consists of an Integrity VM Host in one enclosure (source) and a bare metal server on another enclosure (target). 1. Configure an Integrity VM Host (HP-UX 11.31 1109, HPVM 4.3 PK2) for NPIV functionality (HP-UX PI installed and enabled, vSwitch and FC configured. 2. In HP Systems Insight Manager, license and configure the Integrity VM Host and the bare metal server for Matrix OE and VMM. 3. Create the portability group containing the source and target enclosures, and the Integrity VM Host. 4.
2. Create a new Integrity VM guest using SAN-based storage and a LUN that has been previously provisioned with an OS: a. Create an Integrity VM guest on the VM Host using the hpvmcreate command. b. Start the Guest. c. Boot the OS directly from EFI. d. Import the guest into LSM using the import operation. An error message similar to the following is displayed: Import failed for 16.92.100.170. The HP Integrity VM guest uses NVIP storage but has no boot path configured.
Suggested actions 1. 2. 3. 4. 5. Ensure that the following configurations are set correctly in your environment. Failure to do so can cause various errors.
Table 10 Recovering an inoperable logical server (continued) Possible cause Suggested action the VM Host with Insight Control virtual machine management, or restart the VM Host. Refresh the appropriate logical server resources (Virtual Connect or Virtual Machine) using Tools→Logical Servers→Refresh.... • Unmanage the inoperable logical server. Both the blade and VM guest resources of a cross-technology logical server have been activated and are operating simultaneously.
Table 10 Recovering an inoperable logical server (continued) Possible cause Suggested action virtual machine management\clientapi\bin> 5. Refresh logical server VMM resources using Tools→Logical Servers...→Refresh... 1 VCEM displays a warning when it detects that Matrix OE is installed and you are attempting to perform management operations on a server blade associated with a logical server. Performing these operations using VCEM may lead to inoperable logical servers.
Suggested action Login to the iLO or Onboard Administrator, ensure that all necessary licenses are applied and Systems Insight Manager Single-Sign-On is properly configured. Then rediscover the iLO or Onboard Administrator on the Central Management System. Logical server operations cannot be cancelled After a logical server operation is started, you can view its status on the Report→Logical Server Job Status... screen, but you cannot cancel it. Running jobs do not time out.
1. 2. 3. Modify the configuration file (shown in the default location) at C:\Program Files\HP\ Virtual Server Environment\conf\hp_lsa_service.conf. Increase the value of wrapper.java.maxmemory=1024. HP suggests a value of 2048. Restart the HP Logical Server Automation service. Suggested action 2 To correct the PermGen space error, modify the configuration file to increase permanent generation size, as follows. 1.
IMPORTANT: This error also occurs during the first activation of a logical server if the designated Virtual Connect profile name is assigned to an existing profile. In this case, following the suggested action to delete the underlying profile will result in a loss of data if the profile is in use.
5. 6. 7. Restart the Logical Server Automation Service. This recreates the logical server with the new name. If the logical server was previously activated, then deactivated, reactivate it using Tools→Logical Servers→Activate.... Use the Systems Insight Manager Option→Discovery... menu selection to rediscover the host. Oversubscribing the number of networks It is possible to "over subscribe" the number of networks for a Virtual Connect logical server.
Suggested action 3 Modify the unusable WWNs, entering in new values in their place. HP recommends that you do not use Unmanage Logical Server to unmanage a logical server that has been previously activated. Unmanaging the logical server may result in an inconsistent state, and may render the storage pool entries unusable. An exception to this recommendation is if you plan to manage the profile using VCEM.
a second set of WWNs to the storage pool entry, and allows the storage pool entry to be reused. • If you want to reuse the original WWNs, free them in one of the following ways: 1. Using Virtual Connect Enterprise Manager, unassign and delete the VC profile. 2. Using Tools→Logical Servers→Refresh..., refresh the VCEM GUID Server. This will make the WWNs in the storage pool entry to become available. OR 1.
Suggested actions • Check to see that the VM Host is properly configured and has a UUID. To perform this check, view the Systems Insight Manager system page for the VM Host and look for the UUID field. Perform the following steps if vselog.lsm.log contains the error: 2010-03-05 12:58:41,675 [pool-8-thread-9] WARN app - (LSM) Populate VM Host (15.2.9.3) failed with exception: LSM_ADPT_VMM_ERR_NO_VM_HOST_UUID 1. 2. 3. 4. Identify the system using Systems Insight Manager.
After the failure, the delete job appears to be incomplete, and the logical server is active, but not powered on. Suggested action 1. 2. 3. Refresh Insight Control virtual machine management (VMM) server resources using the Tools→Logical Servers→Refresh... menu selection. Deactivate the logical server using the Tools→Logical Servers→Deactivate... menu selection. Repeat the delete operation using the Delete→Delete Logical Server... menu selection.
VM host operation you want to perform Steps to perform on VM guests Steps to perform for the VM host after performing the steps on the VM guests Tools→Logical Servers→Deactivate. Activate or reassign the VC profile to a different blade Power off or perform a graceful shutdown of all VM guests 1. Unregister the VM host from Insight Control virtual machine management. From HP SIM, select Configure→Virtual Machine→Unregister Virtual Machine Host… 2. Activate the VM host logical server.
6 Support and other resources Contacting HP Information to collect before contacting HP Be sure to have the following information available before you call contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware or software • Technical support registration number (if applicable) How to contact HP technical support Use the following methods to contact HP technical support: • See the Contact HP world
Warranty information HP will replace defective delivery media for a period of 90 days from the date of purchase. This warranty applies to all Insight Management products. HP authorized resellers For the name of the nearest HP authorized reseller, see the following sources: • In the United States, see the HP U.S. service locator website at: http://www.hp.com/service_locator • In other locations, see the Contact HP worldwide website at: http://welcome.hp.com/country/us/en/wwcontact.
http://docs.hp.com/en/windows.html For related HP documentation on the Linux operating system, see http://docs.hp.com/en/linux.html Typographic conventions This document uses the following typographical conventions: Book title The title of a book. On the web, this can be a hyperlink to the book itself. Command A command name or command phrase, for example ls -a. Computer output Information displayed by the computer.
Index A activate logical server, 9 C copy logical server, 12 create logical server, 10 cross-technology logical server, 29 D deactivate logical server, 10 delete logical server, 12 documentation providing feedback, 92 reporting errors in, 92 drag and drop feature, 8 E ESX VM version, 11 Extensible Server & Storage Adapter configuring, 26 using Windows 2008 host mode, 26 Extensible Server & Storage Adapter (ESA), 61 F feedback email address for documentation, 92 H HP authorized resellers, 92 I import l
M manage e logical server target attributes, 14 manage logical server portability groups, 13 manage logical server storage pools, 13 Matrix OE documentation, 92 Matrix OE visualization using Logical Server feature, 6 modify logical server, 15 move logical server, 15 moving cross-technology steps, 39 O Onboard Administrator configuring for logical servers, 25 Operations Orchestration, 61 P port definition for storage pool entry, 53 portable logical server, 29 power logical server, 19 R refresh logical ser
