
Overview 5
Supported hardware
• Servers. ProLiant G6 and later Servers that include an iLO or RILOE management device with a
minimum of 256 MB memory with any of the supported operating systems and with access to an iLO
virtual floppy drive, CD drive, or USB device.
• Adapters. The following HP ProLiant Gigabit Ethernet Multifunction Server Adapters are supported.
o HP NC382T PCI Express Dual Port Multifunction Gigabit Server Adapter
o HP NC382i Integrated Quad Port PCI Express Gigabit Server Adapter
o HP NC382m Dual Port 1 GbE Multifunction BL-c Adapter
iSCSI targets
All iSCSI targets supported by the Linux software initiator are supported by HP. Among HP branded
targets, those supporting iSCSI Boot are as follows:
o AiO family (http://www.hp.com/go/aiostorage)
o MSA SAN Storage Array product line (http://www.hp.com/go/msa)
o EVA4400 with the mpx 100b iSCSI Connectivity Kit (http://www.hp.com/go/eva)
For more information on iSCSI see the iSCSI (http://www.hp.com/go/iscsi
)website.
Limitations and known issues
The following are limitations to iSCSI boot for Linux.
• DNS is not supported
Installation
• 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.
System hangs
• 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
Commentaires sur ces manuels