HP DL785 Sun Solaris 10 Deployment Guide for HP ProLiant Servers - Page 12

DHCP server, JumpStart server, Install server, Deploying ProLiant servers

Get HP DL785 - ProLiant - G5 PDF manuals and user guides
UPC - 883585262809
View all HP DL785 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 12 highlights

DHCP server A Dynamic Host Configuration Protocol (DHCP) server is required to provide systems with network configuration parameters for use during network deployments. If deployments are booted through PXE, then the DHCP server can also provide boot information. If the HP ProLiant Essentials Rapid Deployment Pack is used, a separate DHCP server for PXE boot is not required. TFTP server When PXE booting is used, a TFTP server must provide the booting systems with the files that are necessary to properly boot. For Solaris this server includes pxegrub, the GRUB menu file menu.lst, the Solaris multiboot program, and a miniroot. The DHCP/PXE server often hosts the TFTP server. If the Rapid Deployment Pack is used, a separate TFTP server is not required. JumpStart server JumpStart consists of a set of files which the Solaris installation software uses to automatically configure a deployment. The JumpStart files included profiles and sysidcfg(4) files. A JumpStart server is a set of directories and files on a networked system that provides JumpStart profiles and sysidcfg(4) files to clients during network deployments. The profile and sysidcfg files can provide the Solaris installation software with all the information necessary to perform an automatic deployment of Solaris. JumpStart files are typically served through an NFS share. For information about setting up a JumpStart server, see "JumpStart preparation." Install server An install server is a networked system that contains a copy of the Solaris installation media that it makes available to other systems on the network through NFS. During a network deployment, a client obtains the Solaris operating environment software from the install server instead of from the physical media such as a CD or DVD. For information about setting up an install server, see "Install server preparation." Deploying ProLiant servers While you can use traditional Solaris deployment mechanisms to deploy ProLiant servers, some requirements are ProLiant-specific. In addition, you can use some HP technologies to enhance Solaris deployments. The following sections provide an overview of these requirements and technologies. Information in the following sections is for use with network-based or other advanced deployment methods. For basic interactive installation information, see "Basic installations." For more information about the tasks, see "Deployment tasks." Architecture of an installation 12

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
Architecture of an installation
12
DHCP server
A Dynamic Host Configuration Protocol (DHCP) server is required to provide systems with network
configuration parameters for use during network deployments. If deployments are booted through
PXE, then the DHCP server can also provide boot information. If the HP ProLiant Essentials Rapid
Deployment Pack is used, a separate DHCP server for PXE boot is not required.
TFTP server
When PXE booting is used, a TFTP server must provide the booting systems with the files that are
necessary to properly boot. For Solaris this server includes
pxegrub,
the GRUB menu file
menu.lst,
the Solaris
multiboot
program, and a miniroot. The DHCP/PXE server often hosts the
TFTP server. If the Rapid Deployment Pack is used, a separate TFTP server is not required.
JumpStart server
JumpStart consists of a set of files which the Solaris installation software uses to automatically
configure a deployment.
The JumpStart files included profiles and
sysidcfg(4)
files.
A JumpStart
server is a set of directories and files on a networked system that provides JumpStart profiles and
sysidcfg(4)
files to clients during network deployments. The profile and
sysidcfg
files can provide
the Solaris installation software with all the information necessary to perform an automatic deployment
of Solaris.
JumpStart files are typically served through an NFS share. For information about setting up
a JumpStart server, see “JumpStart preparation.”
Install server
An install server is a networked system that contains a copy of the Solaris installation media that it
makes available to other systems on the network through NFS. During a network deployment, a client
obtains the Solaris operating environment software from the install server instead of from the physical
media such as a CD or DVD. For information about setting up an install server, see “Install server
preparation.”
Deploying ProLiant servers
While you can use traditional Solaris deployment mechanisms to deploy ProLiant servers, some
requirements are ProLiant-specific. In addition, you can use some HP technologies to enhance Solaris
deployments. The following sections provide an overview of these requirements and technologies.
Information in the following sections is for use with network-based or other advanced deployment
methods. For basic interactive installation information, see “Basic installations.” For more information
about the tasks, see “Deployment tasks.”