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

Rapid Deployment Pack, Example: JumpStart preparation

Page 24 highlights

Rapid Deployment Pack When deploying Solaris using Rapid Deployment Pack, a small, non-Solaris partition is created on the boot volume to facilitate booting the installation. By default, Solaris avoids disks with existing partitions, so this temporary partition must be deleted. This deletion can be accomplished using the fdisk profile keyword to delete all type 0x83 partitions. You must create a new Solaris partition to replace the 0x83 partitions. For example: fdisk rootdisk 0x83 delete fdisk rootdisk solaris all Example: JumpStart preparation This section provides a complete JumpStart example. In this example, the profile is named "proliant," and the entire Solaris distribution is installed, along with the CPQary3 package. Optional configuration for use with Rapid Deployment Pack is also listed. If installing to disks attached to a Smart Array controller, the root disk must be SCSI target 0, LUN 0 (that is, cxt0d0). NOTE: The example sysidcfg(4) file contains entries that are new as of Solaris 10 11/06 and might not be supported by previous releases. 1. Prepare the configuration files as follows: ○ Contents of the directory structure: /jumpstart/ /jumpstart/rules /jumpstart/proliant /jumpstart/sysidcfg ○ Contents of the rules file: arch i386 - proliant - ○ Contents of the proliant file: install_type initial_install system_type standalone partitioning default cluster SUNWCXall package CPQary3 add nfs://jssip/jumpstart/pkg where jssip is the IP address of the JumpStart server. If using Rapid Deployment Pack, also include the following lines: fdisk rootdisk 0x83 delete fdisk rootdisk solaris all Deployment tasks 24

  • 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 tasks 24
Rapid Deployment Pack
When deploying Solaris using Rapid Deployment Pack, a small, non-Solaris partition is created on the
boot volume to facilitate booting the installation. By default, Solaris avoids disks with existing
partitions, so this temporary partition must be deleted. This deletion can be accomplished using the
fdisk
profile keyword to delete all type 0x83 partitions. You must create a new Solaris partition to
replace the 0x83 partitions. For example:
fdisk rootdisk 0x83 delete
fdisk rootdisk solaris all
Example: JumpStart preparation
This section provides a complete JumpStart example. In this example, the profile is named “proliant,”
and the entire Solaris distribution is installed, along with the
CPQary3
package. Optional
configuration for use with Rapid Deployment Pack is also listed. If installing to disks attached to a
Smart Array controller, the root disk must be SCSI target 0, LUN 0 (that is,
cxt0d0
).
NOTE:
The example
sysidcfg(4)
file contains entries that are new as of Solaris 10 11/06 and might
not be supported by previous releases.
1.
Prepare the configuration files as follows:
Contents of the directory structure:
/jumpstart/
/jumpstart/rules
/jumpstart/proliant
/jumpstart/sysidcfg
Contents of the
rules
file:
arch i386 - proliant -
Contents of the
proliant
file:
install_type initial_install
system_type standalone
partitioning default
cluster SUNWCXall
package CPQary3 add nfs://
jssip
/jumpstart/pkg
where
jssip
is the IP address of the JumpStart server.
If using Rapid Deployment Pack, also include the following lines:
fdisk rootdisk 0x83 delete
fdisk rootdisk solaris all