HP Insight Control 7.3 Release Notes

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.
Suggested action
Perform one of the following actions:
• Configure the controller in RAID mode and erase all logical volumes, then reconfigure the
controller into non-RAID mode and run the migration again.
• Configure the server to use the RAID mode of the controller and run migration.
Verification of Digitally Signed Application could possibly fail on some Microsoft Windows servers
If the Microsoft Windows server does not contain the VeriSign Class 3 Public Primary Certification
Authority - G5 root certificate, the digital signature verification for the application may fail. The
verification failure occurs on servers that do not have the latest ROOT certificate update from
Microsoft. The latest updates may not be available for reasons such as Windows update has been
disabled and server is not connected to the internet.
Suggested action
Perform the instructions from VeriSign available from the VeriSign website.
Improper behavior of Rediscovery in SIM
After selecting the Rediscovery in SIM option in the Step 6 of the wizard, the process results in
failed discovery logs and the IP address will not get discovered.
Suggested action
From the SMP installation directory, (C:\Program Files (x86)\HP\Insight Control
server migration\bin), edit the hpvmm.conf file by adding the following:
VMwareDisconnectTimeout = 90000.
Issues and suggested actions 13