HP NC373F PCI-E Multifunction 1000SX Gigabit Server Adapter - Manual (Page 6)

Overview 6
• On some blade systems, after the system is booted and the GUI is started, the system console on a
KVM switch may report that it is in an unsupported mode. The iLO2 integrated remote console works
fine. This is a problem with the SLES 10 installation procedure and not with the iSCSI boot
installation procedure.
• After booting a system over iSCSI, if the SmartStart Linux PSP is installed it changes the default boot
kernel in the boot loader conf file /boot/grub/menu.lst. The PSP default kernel does not support
iSCSI boot. Update the /boot/grub/grub.conf to make the default boot kernel point to the entry 0.
• If PXE is used to install the operating system on an iSCSI target for a c-Class BladeSystem, disable
the internal disk controller with RBSU (F9 during POST). After the install is complete, the internal
controller can be re-enabled.
• If the HP StorageWorks SB40c Storage Blade is used with a c-Class BladeSystem, remove the SB40c
before installing the operating system. It can be placed back in the system after the install completes.
System hangs
• In RH5 only, performing a system shutdown on an iSCSI booted system results in a hang and the
system must be reset by using the power button. This defect is fixed in the next version of the RHEL5
iSCSI initiator (U1).
• After a server is booted over iSCSI, do not bring down the network interface that iSCSI is using or a
system hang results.
• Attempting to boot from an iSCSI disk that has no operating system installed on it may result in a
system hang.
• If the system crashes, the diskdump utility that would normally take a system dump will not work on
an iSCSI booted system.
Other
• Multiple LUNs have varying problems depending on the release; therefore, it is recommended that
you add additional LUNs for the data disks after the server is booted over iSCSI.
• In RH4 only, the released iSCSI initiator driver no longer supports limiting the LUNs associated with
a target that are available to the initiator (for example, if you specify LUN=<number> in
/etc/iscsi.conf on RH4, it is ignored). This means that all LUNs configured for a target name will be
visible to the initiator when it connects to the target. This causes problems for iSCSI boot and Direct
Install, since the drive /dev/sda is always used as the boot device. If multiple LUNs are visible to the
initiator, they will be enumerated as /dev/sda, /dev/sdb, etc. and the boot device will be
unknown. Therefore, the iSCSI target configuration has limits on the way it can be configured. Some
iSCSI targets support limiting the LUNs that are visible to the target. In that case, you must configure
the target such that only the LUN for the boot disk is visible to the initiator. If the iSCSI target does
not support that option, you must configure your target with only 1 LUN per target name.
• The ibootcfg utility for updating EVs only works on an iLO running firmware version 1.48 or later. If
you have trouble with the ibootcfg utility, please use the supplied DOS ev utility to update the EVs.
• Errors from the use of the ibootcfg utility are not reported correctly. As a precaution, always use
ibootcfg -P to verify the proper setting of the iSCSI boot parameters after using ibootcfg -i to set them.
If the utility is not setting the iSCSI boot parameters, turn off power to the server and run the ibootcfg
utility again. No problems have been seen when using ibootcfg to set parameters on a machine that
is powered off.