Suggested action – HP Insight Control Software for Linux User Manual
Page 72
Suggested action
You need to modify the following in the /boot/grub/grub.conf file from
root (hd0,0)
kernel /tboot.gz loggingvga,serial,memory
module /vmlinuz-2.6.32-269.el6.x86_64 ro root/dev/mapper/volGroup-lv_rot
intel_iommu=on rd_NO_LUKS LANG-en_US.UTF-8 rd_NO_MD
rd_LVM_LV=VolGroup/lv_swap SYSFONT=latarcyrheb-sun16
rd_LVM_LV=VolGroup/lv_root KEYBOARD=pc KEYTABLE=us crashkernel=auto
rhgb quiet rd_NO_DM ehgb quiet
module /initramfs-2.6.32-269.el6.x86_64.img
to
root (hd0,0)
kernel /vmlinuz-2.6.32-269.el6.x86_64 ro root/dev/mapper/volGroup-lv_rot
intel_iommu=on rd_NO_LUKS LANG-en_US.UTF-8 rd_NO_MD
rd_LVM_LV=VolGroup/lv_swap SYSFONT=latarcyrheb-sun16
rd_LVM_LV=VolGroup/lv_root KEYBOARD=pc KEYTABLE=us crashkernel=auto
rhgb quiet rd_NO_DM ehgb quiet
initrd /initramfs-2.6.32-269.el6.x86_64.img
Failed discovery logs and IP address not discovered.
Failure discovery logs and IP address not discovered in step 6 of the migration wizard, when you
select the rediscover option in SIM.
Suggested Action
To resolve this issue:
1.
Navigate to the following SMP installation directory:
C:\Program Files (x86)\HP\Insight Control server migration\bin
2.
Edit the hpvmm.conf file to add:
VMwareDisconnectTimeout = 90000
Post migration, RHEL 6.2 32 bit takes twenty minutes to boot from HP
CN1000Q Dual Port Converged Network Adapter
When configured in iSCSI mode during boot and post migration, RHEL 6.2 32 bit takes twenty
minutes to boot from the HP CN1000Q Dual Port Converged Network Adapter.
Suggested Action
This is a known issue in HP CN1000Q Dual Port Converged Network Adapter firmware. A future
release of HP CN1000Q Dual Port Converged Network Adapter firmware will fix the issue.
B120i controller is displayed as Intel Lynx storage controller
When migrating to a Gen8 server with intelligent provisioning 1.45 [insert a comma] the B120i
controller is displayed as Intel Lynx storage controller instead of HP Smart Array B120i.
Suggested Action
Ignore the warning message and proceed with the migration.
72
Troubleshooting