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

Configuration methods, Software delivery methods, Implementing a PXE boot-based deployment

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 17 highlights

Configuration methods For Solaris deployments, use of JumpStart profiles and sysidcfg(4) files is the recommended method of supplying installation configuration for automated deployments. Software delivery methods • NFS-The traditional method of delivering the Solaris software packages to clients. The packages are provided in the same form as they appear on the Solaris media. Additional packages that are not a part of the Solaris distribution, such as the Smart Array driver, can also be delivered through NFS. Setting up an NFS installation image offers flexibility in the variety of installation configurations that a single image can support. • Flash Archive-A portable, flexible image of a reference installation. A flash archive enables you to clone a master system to any number of additional systems. The clones can be made to mirror not only the Solaris operating environment and configuration of the master system, but also any additional third-party applications that might be necessary. In addition, differential archives can be employed to simplify clone upgrades. Flash archives are useful for environments in which a large number of systems must be almost identically deployed, including software that is not part of the Solaris distribution. For more information, see Solaris 10 11/06: Solaris Flash Archives (Creation and Installation) at http://docs.sun.com/app/docs/doc/819-6398. Flash archives can be used with any of the boot methods previously described. Implementing a PXE boot-based deployment PXE boot-based deployments require the following: • Install server • JumpStart server • Modified miniroot • DHCP/PXE server Use the following procedure outline as a basis for implementing PXE boot-based deployments in the target environment: 1. Prepare the install server as described in "Install server preparation." 2. Prepare the miniroot as described in "Miniroot preparation." 3. Prepare the JumpStart server as described in "JumpStart preparation." 4. Prepare the DHCP/PXE server as described in "DHCP/PXE preparation." 5. To deploy Solaris using PXE boot: a. Add the client to the install server as described in "DHCP/PXE preparation." b. PXE boot the client by booting the server and pressing F12 when prompted during POST. Deployment planning 17

  • 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
Deployment planning 17
Configuration methods
For Solaris deployments, use of JumpStart profiles and
sysidcfg(4)
files is the recommended method of
supplying installation configuration for automated deployments.
Software delivery methods
•
NFS—The traditional method of delivering the Solaris software packages to clients. The
packages are provided in the same form as they appear on the Solaris media. Additional
packages that are not a part of the Solaris distribution, such as the Smart Array driver, can also
be delivered through NFS. Setting up an NFS installation image offers flexibility in the variety of
installation configurations that a single image can support.
•
Flash Archive—A portable, flexible image of a reference installation. A flash archive enables
you to clone a master system to any number of additional systems. The clones can be made to
mirror not only the Solaris operating environment and configuration of the master system, but
also any additional third-party applications that might be necessary. In addition, differential
archives can be employed to simplify clone upgrades.
Flash archives are useful for environments in which a large number of systems must be almost
identically deployed, including software that is not part of the Solaris distribution. For more
information, see
Solaris 10 11/06: Solaris Flash Archives (Creation and Installation) at
Flash archives can be used with any of the boot methods previously described.
Implementing a PXE boot-based deployment
PXE boot-based deployments require the following:
•
Install server
•
JumpStart server
•
Modified miniroot
•
DHCP/PXE server
Use the following procedure outline as a basis for implementing PXE boot-based deployments in the
target environment:
1.
Prepare the install server as described in “Install server preparation.”
2.
Prepare the miniroot as described in “Miniroot preparation.”
3.
Prepare the JumpStart server as described in “JumpStart preparation.”
4.
Prepare the DHCP/PXE server as described in “DHCP/PXE preparation.”
5.
To deploy Solaris using PXE boot:
a.
Add the client to the install server as described in “DHCP/PXE preparation.”
b.
PXE boot the client by booting the server and pressing F12 when prompted during POST.