HP Insight Control 7.3 Update 1 Release Notes

2. Create a SLES distribution repository in a directory such as in the following example:
/repositories/SLES-11SP2-kISO-x86_64
3. Copy the SLES contents into this repository.
4. Create an addon directory under your new repository directory. For example:
/repositories/SLES-11SP2-kISO-x86_64/addon
5. Copy the kISO contents to the addon directory.
6. Replace the original installation kernel and initrd files with the ones from the kISO addon
directory as follows:
a. Copy
/repositories/SLES-11SP2-kISO-x86_64/addon/boot/x86_64/loader/initrd
to /repositories/SLES-11SP2-kISO-x86_64/boot/x86_64/loader/initrd.
b. Copy
/repositories/SLES-11SP2-kISO-x86_64/addon/boot/x86_64/loader/linux
to /repositories/SLES-11SP2-kISO-x86_64/boot/x86_64/loader/linux.
7. From the appliance, click Save as to create a Build Plan from the existing SLES11 SP 2 Build
Plan that can be edited.
8. Edit the "Set Media Source" step in the new Build Plan and change the parameter to point to
the new directory.
9. Delete the "ProLiant Drivers for the SLES11 SP2 x64" step as the kISO will have all the necessary
drivers.
When the new Build Plan is run, a directory with the name addon, AddOn, or ADDON present in
a SLES repository is auto-detected and the proper kernel parameter addon='path-to-addon-dir
is automatically added to the parameters used for installation. There is no need to specify the
addon= parameter with the kernel_arguments custom attribute.
Unable to detect HP FlexFabric 10Gb 2-port 554FLR-SFP+ Adapter configured as iSCSI disk in
step 5 of migration wizard
When you start an X2P migration of any OS from any server to any supported ProLiant Gen8
servers with HP FlexFabric 10Gb 2-port 554FLR-SFP+ Adapter configured as iSCSI disk and then
start an auto boot in step 3, you will observe that the adapter is not detected in step 5 of migration
wizard and displays the following error message:
HP Insight Control could not find any disks on destination server
Suggested action
Disable IOMMU in RBSU.
Operating system will fail to boot on destination server after migration when existing logical volumes
are not erased on destination disks
After a completed Insight Control server migration, the OS may not boot on the destination server.
This issue occurs if a server is repurposed and the following criteria is met:
This issue may occur if the disks attached to the primary storage controller are not clear of logical
volumes, which may have been created previously with the controller configured in RAID mode.
For example, the server was configured to use Controller in RAID mode and had some logical
volumes created on it. Now, if the same controller is configured in non-RAID mode without erasing
the logical volumes and migration is performed, the OS will fail to boot up. The server will continue
trying to boot from the disk in endless loop.
Issues and suggested actions 13