Dynamic workload movement with BladeSystem Matrix: Fluid movement between physical and virtual resources for flexibility and cost-effective recovery
15
Command Line Interface
Enter /usr/bin/hppint -i to remove the migrate.cfg file and to then re-create the migrate.cfg
file.
Enter /usr/bin/hppint -u to update the migrate.cfg file.
Enter /usr/bin/hppint -m to move the network configurations using the PINT move algorithm.
Red Hat only-Enter /usr/bin/hppint -s to save the operating system network configurations to
the /etc/sysconfig/hppint/ifcfg-save directory as ifcfg-ethx.bak files.
Red Hat only-Enter /usr/bin/hppint -r to restore the saved network configurations to the
/etc/sysconfig/network-scripts directory as ifcfg-ethx.bak files.
[Note]:
CLI is mainly for PINT internal use and the recommended usage is to use the script
as described:
1. Red Hat only-/etc/init.d/hp-pint start
2. SUSE only-/etc/init.d/hp-pint start
Configuring and Managing Cross-technology Logical
Servers
Increasingly platform independence and ease of mobility are critical for load balancing and routine
maintenance within the data center. Heterogeneous server environments (multiple vendors, server
types, product generations, and product families) exist in most datacenters. Portable logical servers
allow you to choose server configurations that make sense for your environment without having to
consider the mechanics of moving images.
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, e.g. Virtual Connect server or VM hypervisor within that portability
group. Logical server resource constraints, e.g. 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.
ID-VSE provides default portability groups depending on the resources found within your data center.
The Default portability groups include: