HP Logical Server Management Best Practices

61
lsmutil -reserve -wwn [WWN | DomainGroupName Number of WWNs] [-help]
Preallocate the supplied WWN or preallocate the specified number of initiator WWNs for the specified Virtual
Connect Domain Group. When only "lsmutil -reserve -wwn" is supplied, the list of available Virtual Domain Groups
on the CMS will be displayed.
lsmutil -unreserve -wwn WWNs [-help]
Unreserve the WWNs listed in comma/semicolon separated list. If a WWN is owned by LSARES it is unreserved. If a
WWN is owned by LSA the user is prompted for permission to unreserve it. If it is owned by neither it is not
unreserved. The list of WWNs can also include spaces along with the comma/semicolon delimiters but must be
enclosed by quotes to do so.
lsmutil -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 numbers may differ.
lsmutil -help
Lists the valid options for the script.
lsmutil [no option]
If no option is supplied, the script defaults to help.
OS deployment
Once a logical server has been defined and activated for the first time on a server blade or virtual machine, a typical
next step for the system administrator is to deploy an operating system. This can be done through tools such as the HP
Insight Control server deployment (formerly HP Rapid Deployment Pack, RDP), Ignite-UX (for HP-UX systems), or HP
Server Automation software.
As noted earlier, logical servers use boot from SAN boot to provide flexibility to migrate from one physical blade to
another. This section captures some of the best practices for using Insight Control server deployment to install an
operating system to a SAN volume. The key aspect when deploying operating systems on logical servers is to ensure
that Insight Control server deployment sees only one path to the LUN where the OS is to be installed.
The challenge is not unique to either Insight Control server deployment or logical servers. Many customers have
established practices for handling OS install to a SAN volume, whether through Insight Control server deployment or
another means. They may choose to physically connect and present all paths, and then adjust the SAN zoning or
HBA configurations for appropriate visibility. They may only present one path initially, adding multi-path and data
access after the OS is installed.
In a logical server environment, the customer can leverage those existing mechanisms (if desired), or use the
techniques outlined in the Insight Control server deployment User Guide. Chapter 1 provides an overview of Insight
Control server deployment, including a knowledge base article with adjustments appropriate for SAN boot
environments. The Create Disk Image and Distribute Disk Image tasks will operate on the first disk, enumerated
through a proprietary algorithm. When multiple disks are visible, the job should be edited to reference the correct
disk (determined through the use of showdisk).
If VMware ESX is to be installed, the installation should be done onto a bare-metal blade using the instructions in the
Insight Control server deployment User Guide. Once it is installed, data volumes can be presented. Once the
VMware ESX environment is created as desired, the system administrator can import it as a logical server.