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

Booting Solaris from GRUB, Synopsis, Options, HPQnetstrategy

Page 31 highlights

Booting Solaris from GRUB This section provides an overview of and describes the options for booting Solaris from GRUB. Synopsis • • • kernel pathtomultiboot kerneltoboot [options] module pathtominiroot pathtomultiboot-Path to the multiboot program. This path is relative to the boot media, either CD or network (TFTP). When booting from CD, this must be a full path. pathtominiroot-Path to the miniroot. This path is relative to the boot media, either CD or network (TFTP). When booting from CD, this must be a full path. kerneltoboot-Path to the kernel that multiboot should load. Unlike the other paths, this path is relative to the miniroot (multiboot loads the kernel from the miniroot, not the boot media). When booting a miniroot, the value of kerneltoboot is usually kernel/unix. Options The options take this form: [- install] [-B param1=value1[,param2=value2[...]]] The - install option must be specified for noninteractive JumpStart installations. The following parameters can be specified following -B: • install_media-Specifies an NFS mount path to the installation media root directory. For example, "10.10.10.10:/export/home/install." This path must map to the same directory that was passed to setup_install_server(1M) when the media was copied to disk. • install_config-Specifies an NFS mount path to a JumpStart configuration directory. For example, a parameter value of 10.10.10.10:/jumpstart instructs the installer to use the rules and profiles found in /jumpstart on an NFS server with IP address 10.10.10.10. • sysid_config-Specifies an NFS mount path to a directory containing the sysidcfg(4) file to use (which must itself be named sysidcfg). For example, a parameter value of 10.10.10.10:/jumpstart instructs the installer to use the file /jumpstart/sysidcfg from the NFS server with IP address 10.10.10.10. HPQnetstrategy The HPQnetstrategy package, when installed in the miniroot, is used to direct the Solaris installation to configure the network even when the miniroot is not booted from the network, such as when booting from an ISO image or when using Rapid Deployment Pack. To instruct HPQnetstrategy on the desired network configuration, specify a netstrategy boot parameter in the same manner as the installation parameters described previously. Parameter usage takes the following form: netstrategy=if:strategy • if-The network interface that must be used, such as bnx0. The if interface can also be the value any to instruct HPQnetstrategy to search for a network interface that can be configured using DHCP. • strategy-The configuration method that must be used. The only supported value for strategy is dhcp. Deployment tasks 31

  • 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 31
Booting Solaris from GRUB
This section provides an overview of and describes the options for booting Solaris from GRUB.
Synopsis
kernel
pathtomultiboot
kerneltoboot
[
options
]
module
pathtominiroot
pathtomultiboot
—Path to the multiboot program. This path is relative to the boot media,
either CD or network (TFTP). When booting from CD, this must be a full path.
pathtominiroot
—Path to the miniroot. This path is relative to the boot media, either CD or
network (TFTP). When booting from CD, this must be a full path.
kerneltoboot
—Path to the kernel that multiboot should load. Unlike the other paths, this path
is relative to the miniroot (multiboot loads the kernel from the miniroot, not the boot media).
When booting a miniroot, the value of
kerneltoboot
is usually
kernel/unix.
Options
The
options
take this form:
[- install] [-B
param1
=
value1
[,
param2
=
value2
[...]]]
The
- install
option must be specified for noninteractive JumpStart installations.
The following parameters can be specified following
-B
:
install
_
media
—Specifies an NFS mount path to the installation media root directory. For
example, “
10.10.10.10:/export/home/install
.” This path must map to the same
directory that was passed to
setup_install_server(1M)
when the media was copied to disk.
install
_
config
—Specifies an NFS mount path to a JumpStart configuration directory. For
example, a parameter value of
10.10.10.10:/jumpstart
instructs the installer to use the
rules
and profiles found in
/jumpstart
on an NFS server with IP address 10.10.10.10.
sysid
_
config
—Specifies an NFS mount path to a directory containing the
sysidcfg(4)
file to
use (which must itself be named
sysidcfg
). For example, a parameter value of
10.10.10.10:/jumpstart
instructs the installer to use the file
/jumpstart/sysidcfg
from the NFS server with IP address 10.10.10.10.
HPQnetstrategy
The
HPQnetstrategy
package, when installed in the miniroot, is used to direct the Solaris
installation to configure the network even when the miniroot is not booted from the network, such as
when booting from an ISO image or when using Rapid Deployment Pack.
To instruct
HPQnetstrategy
on the desired network configuration, specify a
netstrategy
boot
parameter in the same manner as the installation parameters described previously. Parameter usage
takes the following form:
netstrategy=
if
:
strategy
if
—The network interface that must be used, such as bnx0. The
if
interface can also be the
value
any
to instruct
HPQnetstrategy
to search for a network interface that can be configured
using DHCP.
strategy
—The configuration method that must be used. The only supported value for
strategy
is
dhcp.