HP Matrix Operating Environment 7.0 Recovery Management User Guide

The command line interface for PISA is described below. The options are mutually exclusive.
PISA will run on supported versions of Windows only, and requires that the user be a member of
the Administrator user group.
Usage: hppisa
-h, -?, -help Show this information
-e, -enable Enable the LSI driver
-d, -disable Disable the LSI driver
Once these changes are made, the OS image can be moved back and forth between physical
servers and virtual machines.
Portable Images Network Tool (PINT)
PINT is used to resolve networking issues when you move an OS image from one physical server
to another, or from a physical server to a VMware ESX virtual machine.
PINT maintains a network configuration file where it gathers information on each network interface
and it's configuration on a server. PINT remains in a suspended state, running only when it receives
one of the following events:
• IP configuration change event
PINT considers any changes made while the server is up and running to be intentional changes
made by the user. PINT records the changes and updates its configuration file.
• Stop event
If the user stops the PINT service PINT receives an event that lets it know to shutdown.
• User command event
If a user makes any changes via the PINT command line PINT is notified and acts accordingly.
NOTE: If a NIC in the destination server requires a different set of drivers than those on the source
server, you must install the new drivers before using PINT on the destination server.
For more information on PINT including installation and operating instructions, see the Portable
Images Network Tool (PINT) Windows readme available in the PINT directory on the HP Insight
Control DVD at: C:\Program Files\HP\Insight Control server migration\PI\
PINT
Configuring and managing cross-technology logical servers
This section explains configuration tasks and management of cross-technology logical servers in a
Matrix OE envirionment.
Portability groups
When you create a logical server, you must specify the portability of the logical server. You do
this by selecting a Portability Group from within the Identity Page of the logical server configuration
wizard. Once a logical server is associated with a particular portability group, it can potentially
be moved to any target system (HP Virtual Connect physical server or virtual machine hypervisor)
within that portability group. Logical server resource constraints, such as CPU/memory requirements
and network/SAN connectivity, are evaluated solely within the context of the portability group
that the logical server is associated with. Portability Groups come in two classes: Default and User
Defined. The HP Matrix Operating Environment provides default portability groups depending on
the resources found within your data center. The Default portability groups include:
• ESX - All ESX Hypervisors
• HYPERV - All HyperV Hypervisors
• Each Virtual Connect Domain Group – each VCDG will have its own default portability group.
Configuring and managing cross-technology logical servers 33