HP Insight Control Software for Linux User Manual

Page 107

Advertising
background image

Table 17 Source and target deployment requirements

Requirement

Item

The hardware models of the source and target managed systems must be
the same. For example, if you capture an image from an HP ProLiant BL460
Gen8 server, you can only deploy that image to another BL460 Gen8 server.

Server type

Differences in the amount of memory on the source and target managed
systems are permitted.

Memory

Differences in the number of NICs on the source and target managed systems
are permitted. However, NICs must be of the same type.

Number of NICs

Storage controllers must be of the same type on the source and target
managed systems. For example, an image captured from a managed system

Storage controllers

using local storage cannot be deployed to a managed system using Fibre
Channel storage.

The target system needs to have at least as many disks as the source system.

Disks

During image deployment, Insight Control for Linux attempts to recreate the
original partition scheme on the destination system. If the destination system

Disk partition layout

requires a different disk layout, you can use the Partition Wizard to specify
the disk partitioning scheme on the target system. For more information about
the Partition Wizard, see

Section 10.6 (page 116)

.

The target system must have enough space to hold the image.

Disk space

IMPORTANT:

You must ensure that the captured image kernel supports the selected file system

types, including the Logical Volume Manager (LVM). It is especially important that the initial RAM
disk of the captured image (initrd*.img) has file system support for the selected /boot and /
(root) partitions, because the Deploy

→Operating System→Deploy Linux Image... task do not remake

the initial RAM disks. It is possible to remake the initial RAM disk as part of a post-installation
script.

HP recommends that you follow these guidelines before you capture the Linux image from a
managed system:

Do not capture the image on a system that has sensitive information on it.

Before capturing an image from a Xen virtual host, stop all its virtual guests. For information
on the virtual machine operations, see HP Insight Control Virtual Machine Management User
Guide
.

Set up a suitable disk partitioning scheme on the source system during the initial OS installation
and select the Use partition scheme from image option when you deploy the captured image.

Ensure that the system clock on the

CMS

and the managed systems are synchronized before

you capture or deploy a Linux image. For more information about how unsynchronized system
clocks can affect an image deployment, see

Section 1.7 (page 18)

.

When deploying a captured image to a managed system other than the one from which it
was originally captured, HP recommends ensuring that your source node obtains its IP address
and

host name

from DHCP instead of hard-coding those values because Insight Control for

Linux automatically modifies the network configuration of the new managed system to prevent
address and name collisions. These modifications include:

Removing or commenting any hard-coded host name references.

Disabling any network interfaces that were assigned a static IP address.

Replacing the source system's MAC addresses with the target system's MAC addresses
in relevant configuration files.

10.2 Prerequisites to capturing a Linux image 107

Advertising