HP Matrix Operating Environment 7.3 and 7.3 Update 1 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, 2014 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..................................................................................8 Logical server operations...........................................................................................................9 Activate..
Configuration values that are not portable when moving Integrity or Integrity VM servers.................36 Defining portability groups......................................................................................................37 Adding and removing target attributes.......................................................................................39 Defining storage.....................................................................................................................
Catalog storage entries are not displayed in Select Storage Type menu..........................................81 Importing a Microsoft Hyper-V virtual machine with configuration file in default location is not supported..............................................................................................................................82 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 Getting Started Guide. A logical server is a set of configuration information that you create, activate, and move across physical and virtual machines.
Using logical servers within the Matrix OE visualization provides the following benefits: • Allows you to use a common interface and management tools for both virtual machines and servers with Virtual Connect. • Allows you to deploy resources only when needed. For example, some applications are needed only during parts of a business cycle. • Increases business agility and flexibility by decoupling business processing from physical hardware, allowing you to respond to rapid changes in demand.
Logical servers in visualization perspectives To see the Logical Server perspective, navigate to the HP Matrix OE visualization→Visualization. On the upper, blue menu-bar, select Tools→HP Matrix OE visualization.... The Visualization tab is displayed. Select Logical Server from the Perspective drop-down menu. The Logical Server perspective within the HP Matrix OE visualization→Visualization tab graphically represents all logical servers, regardless of their state (active or inactive).
Unavailable hosts are grayed out. Before the move is complete, you have the opportunity to confirm or cancel the drag and drop move operation. The available target host can be a server with Virtual Connect or a hypervisor. 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.
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.
Logical server architecture Architecture type of the system on which you are creating the logical server. Can be HP ProLiant or HP Integrity. Virtual machine type Integrity vPar (Dedicated) or Integrity VM (Shared) 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.
on the Move: Assign Logical Servers to Target Hosts screen. • Compute Resources Allows you to set the compute resources for a logical server, including number of CPU cores, CPU frequency, and amount of memory 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.
Figure 3 Create Logical Server NOTE: Logical servers requiring this capability cannot activate in environments without such support (for example, any blade servers with Virtual Connect on earlier firmware versions will be filtered out as targets). Copy The Tools→Logical Servers→Copy... menu selection copies a previously created logical server. This results in a new logical server with a different name. You can copy an active or inactive logical server.
After unmanaging a logical server with a shared storage pool entry, the logical server may be automatically re-imported in a subsequent refresh unless the associated storage pool entry is deleted. Immediately after unmanaging a logical server, optionally modify the shared storage pool entry to remove the unmanaged logical server's WWNs (if not using SPM). This step is optional since the WWNs will be considered in use by an Unknown logical server; another logical server will not be able to re-use those WWNs.
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. See “Defining storage for logical servers” (page 43) for more information. NOTE: The storage tags apply at the level of the storage pool entry for all volumes within that storage pool entry.
For more information about portability groups, see “Defining portability groups” (page 37). Manage target attributes The Modify→Logical Server Target Attributes.. menu selection allows you to add and remove target attributes to and from a logical server. Target attributes track the systems on which a logical server has been successfully activated or moved, and allow you to create a richer set of targets without warnings.
Moving Virtual Connect logical servers If you are moving a logical server from one server with Virtual Connect to another, the following restrictions apply. • You can move Virtual Connect logical servers within a VC Domain Group. You cannot move logical servers from one VCDG to another. • If the VM Tools are installed in the virtual machine, a graceful shutdown can be done automatically prior to the move.
Table 1 Servers with Virtual Connect filter criteria (continued) Servers with Virtual Connect filter criteria • Mezzanine cards in the same mezzanine slots • Blade state (not running) Classifiable Soft Errors • Compute resources on the target blade are not greater than or equal to the values you specified when you created or modified the logical server. These values include Number of Cores, CPU Frequency, and Amount of Memory.
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.
Figure 4 Assigning logical servers to VM Hosts during Move NOTE: Multiple datastores are supported for a variety of VMware ESXi and Hyper-V environments. All storage volumes for an Integrity VM virtual machine must use the same datastore, and Hyper-V Linked Clone disks must use the same datastore. A Copy Move operation for a VM using multiple data stores will result in all files on the one chosen data store. If you do not select an operation, the best match is selected automatically.
• Quick Move (Hyper-V VM Only) Saves the state of a running guest virtual machine (memory of original server to disk/shared storage), moves the storage connectivity from one physical server to another, and then restores the guest virtual machine onto the second server (disk/shared storage to memory on the new server).
There are several check boxes in the Refresh Logical Servers screen. Use the following combinations to refresh resources. To refresh... Select...
Authorizations, requirements, and configuration To use the Logical Servers feature in Matrix OE visualization, you need the following authorizations: • The Matrix OE All Tools authorization is required to operate on a logical server, regardless of the authorization required to operate on a specific host. • The Matrix OE Monitor authorization is required to create and view a logical server, and to view a entry. • The Matrix OE Storage authorization is required to manage storage pools and storage tags.
on a hypervisor that was moved to a new location (for example, from one blade to another), a VMware message appears, asking you if you want to create a new UUID for the virtual machine, or keep the UUID that was generated for the virtual machine when the logical server was activated. Select Always Keep, then click OK to continue powering on the virtual machine. If you do not select Always Keep or Keep, the moved logical server will not operate correctly.
# hpvmdevmgmt -a gdev:/dev/slvm_v22:attr:VIRTPTYPE=container_volume_SLVM,PRESERVE=YES NOTE: For a virtual machine created with SLVM Logical Volume, the SLVM volume group must be part of container_volume_SLVM in order for the virtual machine to be imported as a logical server.
VM guest storage options Table 4 VM guest storage options Microsoft Hyper-V VM VMware VM Storage type Fibre channel iSCSI2 VM file system (VMFS) ✓ Raw disk mapping (RDM) Network file system (NFS) ✓ ✓ ✓4 DAS ✓4 ✓4 SAS ✓4 ✓4 1 2 3 4 1, 4 NT file system SLVM with (NTFS) Serviceguard ✓3, 4 Network attached storage (NAS) HP-UX vPars and Integrity VMs NPIV ✓ ✓ ✓4 Integrity VM virtual machine guests must have an HP-UX operating system type. Windows and Linux guests are not supported.
Configuring Systems Insight Manager with Onboard Administrator credentials The user Administrator of the Onboard Administrator for each c-Class enclosure that is managed by Virtual Connect Enterprise Manager must be configured into Systems Insight Manager for the CMS on which logical server management in Matrix OE visualization is running. Onboard Administrator credentials are obtained using the Systems Insight Manager System Sign In credentials.
By default, SPM will create host entries on the storage solutions using a prefix “LSM”. This can be customized by adding or modifying the property SPM_HOSTNAME_PREFIX within the lsa.properties file. This prefix can be five characters or less due to host name limitations on the storage arrays. If not selected, the default prefix used is “LSM”. The rest of the host name will be the initiator WWN defined within the host definition to guarantee name uniqueness.
Configuring Extensible Server Adapter (ESA) ESA provides server operations for logical servers and HP Matrix Operating Environment infrastructure orchestration. 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, it is necessary to configure the OO credentials.
#esa.oo.port - Port number of the OO Server # #esa.oo.service.ws.path - Path to the OO service. #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.
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 provides a summary of the Integrity VM and HP-UX cross-technology logical server features added to logical server management.
Table 5 Integrity VM and HP-UX logical server features (continued) Feature Description are automatically moved and properly reconfigured on the target blade.
“Sitelan,” then the vSwitch defined on the VM Host must be named “Sitelan” in order to properly perform cross-technology logical server move operations. SAN fabric setup For HP Matrix OE logical server management, Integrity VM Hosts introduce a new concept that requires all supported FC HBA devices to be named with a SAN fabric name.
HP Matrix OE logical server management storage volume requirements HP Matrix OE logical server management only requires a storage volume entry for the primary boot port during the logical server storage creation process. When importing an Integrity VM Host, logical server management only populates the storage volume information for the primary boot port.
Table 6 Cross-technology logical server operations (continued) Operations Notes NOTE: File storage pool entries are not supported when configuring Integrity VM logical servers in a cross-technology logical server portability group (for example, a portability group that includes both Integrity VM and a VC Domain Group). • Only File or SAN-based storage can be added to an Integrity VM logical server. Modify The logical server has to be deactivated to modify the resources.
• All hardware deallocation information • iLO User Configuration Settings including: ◦ Security settings such as certificates or failed login ◦ User settings (username, password for example) ◦ LDAP settings ◦ Licence settings ◦ Power on restore settings ◦ 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 ◦
• A set of Hyper-V Virtual Machine Hosts • HP vPars and Integrity VM VSP's • A set consisting of a single Virtual Connect Domain Group and a set of VM Hosts (either ESX, Hyper-V, or Integrity Virtual Machines). A logical server created in this type of portability group is a cross-technology logical server. Specify a unique name for your user-defined portability group.
Figure 8 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 VC Domain Group 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 10 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 and clicking the Add button adds that type of server with its associated resources to the list of most suitable targets for the logical server.
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 43) 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.
d. e. 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... screen to add a storage pool entry that you can select as the storage configuration for the logical server.
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 HP rack-mount servers, see the following white papers at http:// www.hp.
The Fibre Channel and network connections within an enclosure are hardwired through a midplane which physically maps the blade’s Fibre Channel and network ports to the enclosure’s connection 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.
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.
Use this storage type to ensure that pre-provisioned and pre-presented volumes from SPM are returned as candidates. NOTE: This type of storage pool entry cannot be used by Matrix infrastructure orchestration. Table 7 Storage types If your logical server will be active on... And your storage configuration is...
See “Using LSMUTIL with logical server storage” (page 68) 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. To create a new storage entry during logical server creation, use the Create→Logical Server... menu selection. Complete the required information on the Identity and Compute Resources screens.
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. When creating logical servers from Matrix OE visualization, local disk is not supported. However, if using Matrix infrastructure orchestration, there is a mechanism for local disk support via manual file edits to provide local disk information.
assigned to it. This WWN, like a MAC address for NICs, is used to uniquely identify this FC port to the SAN. The storage administrator provides access to these ports when pre-presenting LUNs. 1. Click the Add Port button to add a row to the Port Selection table. You add a maximum of two ports. 2. Select a value from the Fabric drop-down menu. 3. Select a value from the Speed drop-down menu. For Fibre Channel ports, select 1Gb, 2Gb, 4Gb, or Auto (FC).
The Volume & Path Selection table allows you to enter the storage volume attributes for this logical server. 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. Select a RAID Level for the storage volume. The default is None.
Figure 18 File (VM) storage selection 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.
the Manage Storage Pool screen. You can also create a storage pool entry when you create a logical server by inserting the newly created storage entry into the storage pool. Matrix OE allocates enough server WWNs so that each logical server that shares a storage definition is assigned a unique server WWN. The number of allocated server WWNs is determined by the Maximum Number of Sharers.
Figure 19 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 54) 2.
Figure 21 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 “Storage Provisioning Manager” (page 60) 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 fulfilled with existing storage, the Remove Volume action returns the storage volume to the storage catalog as an available resource. If SPM had created the volume through on-demand provisioning, it will be automatically deleted by SPM.
The number of server WWNs allocated to each port of a storage pool entry is based on the number of allowed sharers specified by pool entry’s Maximum Number of Sharers field. One server WWN is allocated per port for each allowed sharer. As logical servers share this pool entry, they are assigned one specific server WWN per port.
Matrix OE logical server capabilities, including storage validation and integration with the HP Storage Provisioning Manager (SPM), supports HP P6000 Command View Software versions 9.4, 9.4.1, 10.0, 10.1, 10.2, 10.3, and 10.3.1. Validation is not available for SAN Catalog Storage Entries and SAN Pre-populated Catalog Storage Entries. Catalog-based storage is validated when presentation is complete.
Pre-populated Catalog Storage Entry storage type, and clicking Add Entry. The server administrator can then select the appropriate volume service(s) to fulfill the storage requests. For information about configuring SPM, see “Configuring Storage Provisioning Manager (SPM)” (page 27). By default, SPM will create storage volumes with the prefix “SPM_”. The storage architect can specify custom prefixes when defining SPM storage templates.
Figure 26 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. Matrix OE is able to gather information regarding servers and perform power operations through Virtual Connect.
servers not using Virtual Connect or rack-mount servers. The power operations are performed directly through iLO using Operations Orchestration workflows which can be customized for specific environments. Operations Orchestration, as used in ESA, is in an embedded form called the OO engine. The OO engine defines and utilizes the work flows for extending the features of Insight Management.
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 parameter [names] can be the names of managed resource entries in a comma separated list. -spe [-available | -vm | -vc | -oowf] [-names names] -file filename Exports storage pool entities into an XML file. You must specify an output file name. The following list defines the export parameters: • The available parameter—Available storage pool entries are listed.
Table 8 LSMUTIL options (continued) Option Parameters Description The parameter [names] can be the names of logical servers in a comma separated list. -spe [-available | -vm | -vc | -oowf] [-details] [-xml] [-names names][-file filename] Prints a short list in ASCII format for all available, vm, vc, or oowf storage pool entries. If the -xml parameter is supplied, a long list of storage pool entries in XML form will be sent to sysout.
Table 8 LSMUTIL options (continued) Option Parameters Description -deactivate -names names [-force] Deactivates the named logical servers. If force is used, no verification checks are performed before attempting the deactivation. The parameter [names] can be the names of logical servers in a comma separated list. -delete -names names [-force] Deletes the named logical servers. If force is used, no verification checks are performed before attempting the deletion.
Table 8 LSMUTIL options (continued) Option Parameters Description WARNING! This operation can result in losing compute resources and references to it from other objects within the LSM database. -version Displays the current version of Matrix OE and also the version of the logical server tables in the Matrix OE database to standard output. These version numbers may match or may not match.
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.
When the lsmutil –import –spe command is entered, Matrix OE matches the storage pool entries in the XML file based on the element. When a matching is found, the information 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 72
Example 2 Example XML file for storage import and export PAGE 7440 GB data, 10 GB boot disk 151 razorsaw UNKNOWN false Linux 1 2 40000 MB 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 O
set to LOCAL set to false set to MB set to NONE 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.
1. 2. 3. 4. Execute an lsmutil -export –an to an XML file of you choice as specified with the –file filename parameter. Edit the XML file with your favorite editor. 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. Removing a Hyper-V CSV volume may not remove the volume as an activation target In a Hyper-V cluster environment with clustered shared volumes (CSV), if a CSV volume is removed from the environment, Matrix OE visualization may still show the volume as an available datastore during logical server activation.
Fibre Channel HBA (NPIV also known as VMSAN devices), so as a result the logical server and the Integrity VM guest will be unsynchronized which can result in problems if the logical server is subsequently moved to a server with Virtual Connect. Suggestion action To avoid this situation, do not manage an Integrity VM guest’s virtual Fibre Channel HBA using tools external to logical server management when the guest is associated with a logical server.
Figure 27 Device is unavailable message Moving a server blade configured as a VM Host to another server blade can fail when performing the following procedure: The setup consists of an Integrity VM Host in one enclosure (source) and a bare metal server on another enclosure (target). 1. Configure HP-UX vPars and Integrity VM VSP for NPIV functionality (HP-UX PI installed and enabled, vSwitch and FC configured. 2.
Suggested action To resolve this situation, adjust the above steps so that the following is done directly after the physical to physical move (Step 7) of the VM Host and before the reactivation of the VM logical server (Step 9) as follows: 1. After the physical to physical move of the VM Host, edit the portability group of the logical server and remove the VM Host that was moved. 2. Rediscover and re-license the VM Host that was moved. 3. Edit the portability group and add the VM Host again.
If the SPM service stops running or the default storage template is no longer available while on the page, and the you attempt to add a Catalog Storage option, a message is displayed with instructions on how to resolve it.
4. 5. If the above steps do not correct the problem, unmanage the logical server. From the HP Matrix OE visualization screen, select Delete→Unmanage Logical Server.... Import the server with Virtual Connect or virtual machine as a logical server when the resource is available. Recovering an inoperable logical server You cannot perform operations on an inoperable logical server except to delete or unmanage it. Click on the logical server icon (or use the Report→View Logical Server Details...
Table 10 Recovering an inoperable logical server (continued) Possible cause Suggested action C:\Program Files\HP\Insight Control virtual machine management\clientapi\bin>adminlogin.cmd Login successful. 3. Find the VM URI or configuration path “cli getVmIds” C:\Program Files\HP\Insight Control virtual machine management\clientapi\bin> cli getVmIds vm://15.1.50.205/C:\VSE_VirtualMachines\vsels_ls-hyperv-01\ Virtual Machines\880401BA-5024-4E76-9CD3-AA5F706F3332.xml 4.
User Guide at http://bizsupport.austin.hp.com/bc/docs/support/SupportManual/c00705292/ c00705292.pdf. Suggested action: Check disk space When you create a Hyper-V virtual machine logical server, if the amount of free disk space on the VM Host is smaller than the amount of memory chosen for the logical server, the logical server cannot be powered on. This occurs infrequently, because free disk space is usually larger than memory size.
Suggested action Modify lsaclient.properties and replace the port in use with a free port, and restart the service. To determine a free port, use the command netstat -A. Logical Server Automation service may run out of memory on large scale systems On large scale systems, with large numbers (1000+) of managed nodes and/or large numbers (1000+) of logical servers on a 64-bit CMS, the HP Logical Server Automation service may run out of memory and display out of memory errors in the /logs/hp_lsa_service.
Suggested action After vCenter is restarted, use the Report→Logical Server Job Status... menu selection to make sure that there are no logical server operations in progress. Then, restart the Logical Server Automation service.
5. 6. Select the VCEM and the Change Logical Server Associations check boxes and insert the VC Domain Group name in both fields and click Refresh. Try provisioning again. Use portable WWNs and MAC addresses for VC Domain Groups VCEM VC Domain Groups that use hardware default settings for WWNs and MAC addresses are not supported in logical servers. Logical servers require portable WWNs and MAC addresses that can be moved from blade to blade.
Suggested action If you know that the target enclosure and blade support Flex-10, check that the error message concerns insufficient NICs. In these cases, you can ignore the message and select the target. Use caution when renaming or moving a VC Domain Group Use caution when renaming or moving a VC Domain Group, which is accomplished by checking Change Logical Server Associations using the Tools→Logical Servers→Refresh... menu selection. Do not use this functionality to merge VC Domain Groups.
1. 2. 3. 4. Start SPM by pointing a browser to https://localhost:8000 where “localhost” is the name of the CMS. Right click on an array and select Change Security Group. Select the Matrix User Security Group. In Matrix OE, refresh storage pool entries on the Tools→Logical Servers→Refresh or Modify→Logical Server Storage Pools screen. The status of the inoperable storage pool entry will change to “Presentation Completed – Available”.
Synchronize clocks on the CMS, managed systems, and VMware vCenter Ensure that time synchronization has been performed among the CMS, managed systems (including VM Hosts), and VMware vCenter. Failure to do so results in errors in both vCenter and Matrix OE software. Suggested action Use clock synchronization software such as the Windows Time Service or the Network Time Protocol.
• Integrity VM targets: To enable secure communication between the source and target hosts, generate SSH keys on both systems. You need root privileges to generate and set up the SSH keys required for guest migration. Use the secsetup script provided by Integrity VM. Execute the following command on both the source and target hosts: # /opt/hpvm/bin/secsetup -r otherhost See HP-UX vPars and Integrity VM Administrator Guide at www.hp.com/go/hpux-hpvm-docs for more information.
Then refer to the following table for the appropriate steps to prevent VM guests and VM logical servers from becoming inoperable. 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 Move VC profile to another blade Power off or perform a graceful shutdown of all VM guests 1. Unregister the VM host from virtual machine management. From HP SIM, select Configure→Virtual Machine→Unregister Virtual Machine Host… 2.
6 Support and other resources 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 Use the following methods to contact HP technical support: • In the United States, see the Customer Service / Contact
Registration for this service takes place following online redemption of the license certificate. How to use your software technical support and update service As HP releases updates to software, the latest versions of the software and documentation are made available to you. The Software Updates and Licensing portal gives you access to software, documentation and license updates for products on your HP software support agreement.
For related HP documentation on the Windows operating system, see 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. 96 Command A command name or command phrase, for example ls -a. Computer output Information displayed by the computer.
7 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback docsfeedback@hp.com. Include the document title and part number, version number, or the URL when submitting your feedback.
Index A activate logical server, 9 C copy logical server, 13 create logical server, 10 cross-technology logical server, 31 D deactivate logical server, 10 delete logical server, 13 documentation providing feedback, 97 reporting errors in, 97 drag and drop feature, 8 E ESX VM version, 11 Extensible Server Adapter configuring, 29 using Windows 2008 host mode, 29 Extensible Server Adapter (ESA), 62 F feedback email address for documentation, 97 H HP authorized resellers, 95 I import logical server, 14 in
M manage e logical server target attributes, 16 manage logical server portability groups, 15 manage logical server storage pools, 14 Matrix OE documentation, 95 Matrix OE visualization using Logical Server feature, 6 modify logical server, 16 move logical server, 16 moving cross-technology steps, 41 O Onboard Administrator configuring for logical servers, 27 Operations Orchestration, 62 P port definition for storage pool entry, 55 portable logical server, 31 power logical server, 21 R refresh logical ser
