Administer > SA Provisioning > OS sequence-based provisioning > Booting a Red Hat Enterprise Linux Itanium 64-bit server in a non-DHCP environment using Elilo boot

Booting a Red Hat Enterprise Linux Itanium 64-bit server in a non-DHCP environment using Elilo boot

If you plan to use SA Provisioning in an environment without a DHCP server, you must assign static IP information for the managed server and manually configure that server to resolve the SA Core.

There are several reasons you might need to manually specify the network information for a sever being provisioned:

  • You don’t use DHCP and must manually specify the static IP address the Agent’s IP and Port
  • You must provision a server but DHCP is inactive.
  • You must provision a server but DHCP is blocked by firewall rules.

You can export the Linux Itanium image by logging in to the SA Client and selecting
Library > By Folder > Opsware > Tools > OS Provisioning.

The images are named using the following format:

HPSA_linux_boot_cd_IA64.iso

The following section provides details for provisioning in a non-DHCP environment.

When you boot an unmanaged server in a non-DHCP environment, you will see a boot screen similar to that shown below:

HPE SA Linux Boot CD (<version):

Enter the appropriate Linux service OS

at the ‘Elilo boot:’ prompt.

 

linux5 - RHEL 5.7 based Linux service OS

linux5-txt - RHEL 5.7 based Linux service OS for serial consoles

 

ELILO boot:

After you select the boot method, you will see a Network Configuration dialogue that allows you to enter a static IP address for the server, the subnet mask, the host gateway IP address, and the IP address and default port for the SA Agent Gateway:

Red Hat Linux Itanium 64-bit network configuration dialog

If the operating system you are provisioning is Red Hat Enterprise Linux 3 IA64, you must add the custom attribute kernel_arguments with the value console=ttyS1 to the OS Installation Profile.

You can manually configure the following fields:

  • Interface: the NIC to be used
  • IP Address: static IP address for the server being provisioned
  • Netmask: netmask for the server being provisioned
  • Gateway: Gateway IP address the server being provisioned should use (network level IP router)
  • DNS Suffix: the fully qualified DNS suffix the server being provisioned should use
  • Agent Gateway IP: the default SA Agent Gateway hostname or IP address
  • Agent Gateway Port: the port used for the SA Agent Gateway

After the information in these fields is entered and applied, the server is able to register with the SA Core. You can now start the normal SA Provisioning process.

DHCP custom attribute

After provisioning, servers that have been registered with the SA Core using a static IP specification will display the hpsa_netconfig custom attribute in the server record.