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.
© Copyright 2006, 2013 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...............................................34 Operations and guidelines..................................................................................................34 Configuration values that are not portable when moving Integrity or Integrity VM servers.................35 Defining portability groups......................................................................................................
Moving a server blade configured as a VM Host to another server blade..................................79 Importing an Integrity VM guest with no boot path............................................................81 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..........................................................................
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.2 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 shows an example of a Logical Server perspective. 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.
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. For a description of the Matrix OE visualization menu options that perform these tasks, see the HP Matrix Operating Environment 7.2 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.
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.
from the newly created logical server. (The storage pool entries' maximum share count will be incremented if needed.) Delete and unmanage The Delete→Delete Logical Server... menu selection allows you to delete an inactive logical server. Deleting a logical server removes the logical server definition from the management database, 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...
Manage storage pools and tags The Modify→Logical Server Storage Pools... menu selection allows you to manage entries in a preexisting storage pool for a selected portability group. You can select these entries as part of the storage configuration for a Virtual Connect logical server or a virtual machine logical server. You can globally define a storage tag and associate it with storage pool entries by pressing Manage Tags on the Manage Storage Pools screen.
For more information about portability groups, see “Defining portability groups” (page 36). 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.
• If you configure your 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. • You can initiate multiple move operations at the same time, but Virtual Connect Enterprise Manager queues the move operations and performs them serially.
Valid target Datastore selection Each available VM Host includes a valid target Datastore menu selection that can be activated on the logical server. Figure 3 displays the Datastore menu selection. Figure 3 Datastore menu selection IMPORTANT: Multiple datastores are not supported. All storage volumes for a virtual machine logical server must be part of the same datastore. (To import a virtual machine, the virtual machine must be using a single datastore.
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 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.
• Install VMware Tools on the guest operating system (Use the Inventory menu in the VMware Virtual Infrastructure Client, then select Virtual Machine→Install/Upgrade VMware Tools) • 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.
• Configure the Integrity VM Host with Serviceguard (11.19 or 11.20) and Shared Logical Volume Manager (SLVM). (An imported VM with a whole LUN is not required to be in a Serviceguard Package.) See HP-UX vPars and Integrity VM Administrator Guide at www.hp.com/go/hpux-hpvm-docs for more information. • Create the appropriate size SLVM volume group (VG) for the device management database using LVM Version 2.1 or higher. For example: # vgcreate -V 2.
• ◦ 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 the following: – 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. – Direct I/O network devices (DIO).
• HP Integrated Lights-Out (iLO2) for ProLiant 2.00 or higher • Latest available firmware update for your server blade BIOS 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.
6. 7. 8. Click OK. 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.
Configuring Extensible Servers & Storage 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.host - indicates the ip address of the OO server. #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.
EVA_OTHER_WIN2K8_SUPPORTED_VERSIONS=6200,6220,09004000,09006000,09501000, 09501100,09501200,09521000,09522000,09534000 7. 8. Save the file. Restart the ESA service.
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 Feature Description Integrity VM logical server using SAN-based storage Enables full logical server management life cycle support for Integrity VM guests configured with NPIV (or SAN-based 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 approp
Table 5 Integrity VM and HP-UX logical server features (continued) Feature Description • BL8x0c i2 to BL8x0c i2 • BL8x0c to BL8x0c i4 • BL8x0c i2 to BL8x0c i4 • BL8x0c i4 to BL8x0c • BL8x0c i4 to BL8x0c i2 • BL8x0c i4 to BL8x0c i4 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.
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. The FC HBA SAN fabric names must match exactly with the VC FC SAN fabric names that have been defined for the VC Domain Group that is configured in the same portability group as the VM Host. This is conceptually similar to the network naming model where we assign vSwitch names to be consistent with VC Ethernet uplink names.
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 • A set of HP Integrity VM Virtual Machine Hosts • A set consisting of a single Virtual Connect Domain Group and a set of ESX Virtual Machine Hosts 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 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 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 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 42) 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 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.
Use this storage type to ensure that managed arrays in SPM are returned as candidates. 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.
You can select catalog storage for the storage pool entry if you preconfigured storage using HP Storage Provisioning Manager. See “Storage Provisioning Manager” (page 59) for more information. 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.
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 47) 2. Enter the “Port definition” (page 47) 3. Enter the “Volume and path definition” (page 48) 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 59) 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 53) 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.
Storage operations (such as changing operating system mode or adjusting LUN masking) is performed automatically, if appropriately authorized. Changing OS mode automatically enables 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.
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 workflows can be customized. Extensible Server & Storage Adapter Extensible Server & Storage Adapter (ESA) provides 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 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.
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.
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 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. 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.
Typically some changes made to an Integrity VM guest are reflected in the associated logical server on the next refresh of virtual machine management resources. However, this does not include virtual 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.
Figure 26 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 an Integrity VM Host (HP-UX 11.31 1303, HPVM 6.2) 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 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. You can access this portal from the HP Support Center: http://www.hp.
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, 12 create logical server, 10 cross-technology logical server, 30 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 & Storage Adapter configuring, 27 using Windows 2008 host mode, 27 Extensible Server & Storage Adapter (ESA), 62 F feedback email address for documentation, 97 H HP authorized resellers, 95 I import l
M manage e logical server target attributes, 15 manage logical server portability groups, 14 manage logical server storage pools, 14 Matrix OE documentation, 95 Matrix OE visualization using Logical Server feature, 6 modify logical server, 15 move logical server, 15 moving cross-technology steps, 40 O Onboard Administrator configuring for logical servers, 25 Operations Orchestration, 62 P port definition for storage pool entry, 54 portable logical server, 30 power logical server, 19 R refresh logical ser
