Configuring the compute node

Use this information to configure the compute node.

1. Configure the Unified Extensible Firmware Interface (UEFI) firmware for the compute node by using the Setup utility (see Using the Setup utility or the Advanced Setup Utility (ASU) (see the Advanced Settings Utility (ASU) for Lenovo x86 servers website).

   For more information about firmware configuration options, see Introducing UEFI-Compliant Firmware on Lenovo System x and BladeCenter Servers.

2. Set the boot protocol by using the Setup utility (see Setting the boot protocol to boot from legacy devices using the Setup utility).

   You can temporarily redefine the boot order by using the Boot Selection menu program (see Using the Boot Selection Menu program).

3. Configure the RAID array.

   You can install up to two hard disk drives in the compute node and implement RAID level-0 (striping) or RAID level-1 (mirror) arrays in operating systems that are listed on the ServerProven list at the Lenovo ServerProven website. For the compute node, you must configure the RAID by using the LSI Configuration Utility program (see Using the LSI Logic Configuration Utility).

   If an optional RAID expansion adapter is installed, you can use it to control all the hard disk drives that are installed in the compute node. See the documentation that comes with the expansion adapter for information about how to configure the RAID array.

   Important: You must create the RAID array before you install the operating system on the compute node.

4. Configure the integrated management module II (IMM2) using either the Setup utility or the Advanced Settings Utility (ASU).
5. Update the compute node firmware (see Updating firmware and device drivers).
   Notes:

   1. If you use Flex System Manager Update Manager to update the firmware, you can optionally start the operating-system installation while the firmware updates are installed. It is normal operation for the initial firmware updates to take an unusual length of time.
   2. If the Chassis Management Module (CMM) and the compute nodes are set up to use DHCP and the CMM loses connectivity to the network, the CMM attempts to acquire a new IP address when network connectivity is restored. The compute nodes will not attempt to acquire an IP address again; they will continue to use their original IP addresses. Therefore, if you experience network problems on compute nodes after connectivity between the CMM and the network is restored, you might have to reset the system-management processor in each of the compute nodes in the chassis (including the management node).