| Skip Navigation Links | |
| Exit Print View | |
|
Installing Oracle Solaris 11 Systems Oracle Solaris 11 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Installing Oracle Solaris 11 Systems Oracle Solaris 11 Information Library |
Part I Oracle Solaris 11 Installation Options
1. Overview of Installation Options
Part II Installing Using Installation Media
2. Preparing for the Installation
5. Automated Installations That Boot From Media
6. Unconfiguring or Reconfiguring an Oracle Solaris instance
Part III Installing Using an Install Server
7. Automated Installation of Multiple Clients
8. Setting Up an Install Server
10. Provisioning the Client System
11. Configuring the Client System
12. Installing and Configuring Zones
13. Running a Custom Script During First Boot
14. Setting Up Oracle Configuration Manager For Use By AI Client Systems
SPARC and x86 Client System Requirements
Additional SPARC Client System Requirements
Boot the client to start the installation. This section shows you exactly how to boot a SPARC or x86 client. This section also describes how you can monitor installation progress remotely.
You can enable network access to an automated install client by using ssh. You can use this access to remotely observe an installation in progress.
Enable remote access by setting the option livessh to enable in the installation configuration file. When this access is enabled, you can log in to the AI client by using the username jack and password jack.
For x86 systems, the menu.lst configuration file is created in the following way:
If you used the installadm create-client command, the filename is /etc/netboot/menu.lst.01MAC_address, where MAC_address is the MAC address that was specified in the installadm create-client command.
If you did not use the installadm create-client command, the filename is /etc/netboot/service_name/menu.lst, where service_name is the name of the install service that was created by the installadm create-service command.
In this file, options are provided as kernel parameters. In the following example, the livessh and install_debug options are set to enable.
kernel$ ... -B install_media=...,livessh=enable,install_debug=enable
For SPARC systems, the system.conf file can be accessed through the service's net image directory mounted under the /etc/netboot directory: /etc/netboot/svcname/system.conf.
In the system.conf file, the options are defined as name-value pairs. In the following example, the livessh option is set to enable.
$ cat /etc/netboot/svc1/system.conf ... livessh=enable ...
Use the following command to boot SPARC clients from the OBP prompt:
ok boot net:dhcp - install
The following events occur during AI boot of a SPARC client:
The client boots and gets an IP address and the location of the wanboot-cgi file from the DHCP server.
The wanboot-cgi program reads wanboot.conf and sends the location of the WAN boot binary to the client.
The WAN boot binary is downloaded using HTTP, and the client boots the WAN boot program.
WAN boot gets the boot_archive file, and the Oracle Solaris OS is booted.
Image archives, solaris.zlib and solarismisc.zlib, are downloaded using HTTP.
The AI manifest and system configuration profiles are downloaded from an AI install service specified either from the mDNS lookup or from the system.conf file.
The AI install program is invoked with the AI manifest to perform the installation of the Oracle Solaris OS to the client.
The following output from the boot sequence is displayed:
{0} ok boot net:dhcp - install
SPARC Enterprise T5120, No Keyboard
Copyright 2008 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.29.1, 16256 MB memory available, Serial #81036844.
Ethernet address 0:14:4f:d4:86:2c, Host ID: 84d4862c.
Boot device: /pci@0/pci@0/pci@1/pci@0/pci@2/network@0:dhcp File and args: - install
1000 Mbps full duplex Link up
Timed out waiting for BOOTP/DHCP reply
<time unavailable> wanboot info: WAN boot messages->console
<time unavailable> wanboot info: configuring /pci@0/pci@0/pci@1/pci@0/pci@2/network@0:dhcp
1000 Mbps full duplex Link up
<time unavailable> wanboot info: Starting DHCP configuration
<time unavailable> wanboot info: DHCP configuration succeeded
<time unavailable> wanboot progress: wanbootfs: Read 368 of 368 kB (100%)
<time unavailable> wanboot info: wanbootfs: Download complete
Fri Aug 26 14:34:53 wanboot progress: miniroot: Read 221327 of 221327 kB (100%)
Fri Aug 26 14:34:53 wanboot info: miniroot: Download complete
SunOS Release 5.11 Version snv_175 64-bit
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
Remounting root read/write
Probing for device nodes ...
Preparing network image for use
Downloading solaris.zlib
--2011-08-26 13:47:31-- http://host1:5555/install/images/sparc_snv175//solaris.zlib
idn_decode failed (9): `System iconv failed'
Resolving host1... 10.80.238.5
idn_decode failed (9): `System iconv failed'
Connecting to host1|10.80.238.5|:5555... connected.
HTTP request sent, awaiting response... 200 OK
Length: 135977984 (130M) [text/plain]
Saving to: `/tmp/solaris.zlib'
100%[======================================>] 135,977,984 22.3M/s in 6.0s
2011-08-26 13:47:37 (21.7 MB/s) - `/tmp/solaris.zlib' saved [135977984/135977984]
Downloading solarismisc.zlib
--2011-08-26 13:47:37-- http://host1:5555/install/images/sparc_snv175//solarismisc.zlib
idn_decode failed (9): `System iconv failed'
Resolving host1... 10.80.238.5
idn_decode failed (9): `System iconv failed'
Connecting to host1|10.80.238.5|:5555... connected.
HTTP request sent, awaiting response... 200 OK
Length: 18826752 (18M) [text/plain]
Saving to: `/tmp/solarismisc.zlib'
100%[======================================>] 18,826,752 21.7M/s in 0.8s
2011-08-26 13:47:37 (21.7 MB/s) - `/tmp/solarismisc.zlib' saved [18826752/18826752]
Downloading .image_info
--2011-08-26 13:47:37-- http://host1:5555/install/images/sparc_snv175//.image_info
idn_decode failed (9): `System iconv failed'
Resolving host1... 10.80.238.5
idn_decode failed (9): `System iconv failed'
Connecting to host1|10.80.238.5|:5555... connected.
HTTP request sent, awaiting response... 200 OK
Length: 82 [text/plain]
Saving to: `/tmp/.image_info'
100%[======================================>] 82 --.-K/s in 0s
2011-08-26 13:47:37 (2.22 MB/s) - `/tmp/.image_info' saved [82/82]
Done mounting image
Configuring devices.
Hostname: solaris
Service discovery phase initiated
Service name to look up: default-sparc
Service discovery finished successfully
Process of obtaining install manifest initiated
Using the install manifest obtained via service discovery
Automated Installation started
The progress of the Automated Installation will be output to the console
Detailed logging is in the logfile at /system/volatile/install_log
Press RETURN to get a login prompt at any time.
solaris console login: 13:48:35 Install Log: /system/volatile/install_log
13:48:35 Using XML Manifest: /system/volatile/ai.xml
13:48:35 Using profile specification: /system/volatile/profile
13:48:35 Using service list file: /var/run/service_list
13:48:35 Starting installation.
13:48:35 0% Preparing for Installation
13:48:36 100% manifest-parser completed.
13:48:36 0% Preparing for Installation
13:48:36 1% Preparing for Installation
13:48:37 2% Preparing for Installation
13:48:37 3% Preparing for Installation
13:48:37 4% Preparing for Installation
13:48:47 7% target-discovery completed.
13:48:47 === Executing Target Selection Checkpoint ==
13:48:48 Selected Disk(s) : c3t0d0
13:48:48 13% target-selection completed.
13:48:48 17% ai-configuration completed.
13:49:01 19% target-instantiation completed.
13:49:02 19% Beginning IPS transfer
13:49:02 Creating IPS image
13:50:58 Installing packages from:
13:50:58 solaris
13:50:58 origin: http://pkg.example.com/solaris/
14:48:40 21% generated-transfer-1491-1 completed.
14:48:41 23% initialize-smf completed.
14:48:43 Installing SPARC bootblk to root pool devices: ['/dev/rdsk/c3t0d0s0']
14:48:43 Setting openprom boot-device
14:48:44 33% boot-configuration completed.
14:48:44 35% update-dump-adm completed.
14:48:45 37% setup-swap completed.
14:48:45 40% set-flush-ips-content-cache completed.
14:48:47 42% device-config completed.
14:48:49 44% apply-sysconfig completed.
14:48:49 46% transfer-zpool-cache completed.
14:49:03 87% boot-archive completed.
14:49:04 89% transfer-ai-files completed.
14:49:04 99% create-snapshot completed.
14:49:05 Automated Installation succeeded.
14:49:05 You may wish to reboot the system at this time.
Automated Installation finished successfully
The system can be rebooted now
Please refer to the /system/volatile/install_log file for details
After reboot it will be located at /var/sadm/system/logs/install_log
Initiate the x86 client installation by using one of the following methods to boot from the network:
Press the appropriate function key. For example, some systems use F12 to boot from the network
Change the boot order in the BIOS.
When the client boots, select the network device to boot from.
The following events occur during AI boot of an x86 client:
The client boots and gets an IP address, and the boot file, pxegrub, is downloaded from the location provided by the DHCP server.
The pxegrub boot file is loaded and reads a menu.lst file.
The pxegrub boot file gets the boot_archive file and the Oracle Solaris OS is booted using TFTP.
The net image archives, solaris.zlib and solarismisc.zlib, are downloaded using HTTP as provided by the GRUB menu.
The AI manifest and system configuration profiles are downloaded from an AI install service specified from an mDNS lookup or from the GRUB menu entry that was booted.
The AI install program is invoked with the AI manifest to perform the installation.
When the system has successfully PXE booted, the following message is briefly displayed before the GRUB menu is displayed:
Intel(R) Boot Agent PXE Base Code (PXE-2.1 build 0.86) Copyright(C) 1997-2007, Intel Corporation CLIENT MAC ADDR 00 14 4F 29 04 12 GUID FF2000008 FFFF FFFF FFFF 7BDA264F1400 CLIENT IP: 10.6.68.29 MASK: 255.255.255.0 DHCP IP: 10.6.68.49 GATEWAY: 10.6.68.1
The GRUB menu appears with two menu entries. Select the second entry to start an automated installation:
Oracle Solaris 11 11/11 Text Installer and command line Oracle Solaris 11 11/11 Automated Install
The default GRUB menu entry, “Text Installer and command line,” boots the image without starting a hands-free automated installation. Select the second entry in the GRUB menu, “Automated Install,” to initiate an automated installation. If you select the first menu entry, then when the client is booted, a menu displays as shown in Start Installation After Booting Without Initiating an Installation. Use this menu to examine or install the system.
Once the image is selected, the following messages are displayed:
Remounting root read/write snv_175 64-bit
Probing for device nodes ...acle and/or its affiliates. All rights reserved.
Preparing network image for use
Downloading solaris.zlib
--2011-08-26 07:35:13-- http://10.80.238.5:5555//install/images/i386_snv175/solaris.zlib
Connecting to 10.80.238.5:5555... connected.
HTTP request sent, awaiting response... 200 OK
Length: 130032128 (124M) [text/plain]
Saving to: `/tmp/solaris.zlib'
100%[======================================>] 130,032,128 16.4M/s in 8.3s
2011-08-26 07:35:22 (14.9 MB/s) - `/tmp/solaris.zlib' saved [130032128/130032128]
Downloading solarismisc.zlib
--2011-08-26 07:35:22-- http://10.80.238.5:5555//install/images/i386_snv175/solarismisc.zlib
Connecting to 10.80.238.5:5555... connected.
HTTP request sent, awaiting response... 200 OK
Length: 18758144 (18M) [text/plain]
Saving to: `/tmp/solarismisc.zlib'
100%[======================================>] 18,758,144 21.7M/s in 0.8s
2011-08-26 07:35:23 (21.7 MB/s) - `/tmp/solarismisc.zlib' saved [18758144/18758144]
Downloading .image_info
--2011-08-26 07:35:23-- http://10.80.238.5:5555//install/images/i386_snv175/.image_info
Connecting to 10.80.238.5:5555... connected.
HTTP request sent, awaiting response... 200 OK
Length: 241 [text/plain]
Saving to: `/tmp/.image_info'
100%[======================================>] 241 --.-K/s in 0s
2011-08-26 07:35:23 (29.3 MB/s) - `/tmp/.image_info' saved [241/241]
Done mounting image
Configuring devices.
Hostname: solaris
Service discovery phase initiated
Service name to look up: default-i386
Service discovery finished successfully
Process of obtaining install manifest initiated
Using the install manifest obtained via service discovery
Automated Installation started
The progress of the Automated Installation will be output to the console
Detailed logging is in the logfile at /system/volatile/install_log
Press RETURN to get a login prompt at any time.
solaris console login: 07:35:35 Install Log: /system/volatile/install_log
07:35:35 Using XML Manifest: /system/volatile/ai.xml
07:35:35 Using profile specification: /system/volatile/profile
07:35:35 Using service list file: /var/run/service_list
07:35:36 Starting installation.
07:35:36 0% Preparing for Installation
07:35:36 100% manifest-parser completed.
07:35:36 0% Preparing for Installation
07:35:36 1% Preparing for Installation
07:35:36 2% Preparing for Installation
07:35:36 3% Preparing for Installation
07:35:37 4% Preparing for Installation
07:35:51 7% target-discovery completed.
07:35:51 === Executing Target Selection Checkpoint ==
07:35:51 Selected Disk(s) : c7t0d0
07:35:51 13% target-selection completed.
07:35:51 17% ai-configuration completed.
07:36:23 19% target-instantiation completed.
07:36:23 19% Beginning IPS transfer
07:36:23 Creating IPS image
07:36:41 Installing packages from:
07:36:41 solaris
07:36:41 origin: http://pkg.example.com/solaris/
07:53:29 21% generated-transfer-1006-1 completed.
07:53:29 23% initialize-smf completed.
07:53:30 Setting console boot device property to ttya
07:53:30 Disabling graphical console in boot loader
07:53:30 Creating Legacy GRUB config directory:
/rpool/boot/grub
07:53:30 Installing boot loader to devices: ['/dev/rdsk/c7t0d0s0']
07:53:31 33% boot-configuration completed.
07:53:31 35% update-dump-adm completed.
07:53:31 37% setup-swap completed.
07:53:31 40% set-flush-ips-content-cache completed.
07:53:32 42% device-config completed.
07:53:46 44% apply-sysconfig completed.
07:53:46 46% transfer-zpool-cache completed.
07:54:08 87% boot-archive completed.
07:54:08 89% transfer-ai-files completed.
07:54:09 99% create-snapshot completed.
07:54:09 Automated Installation succeeded.
07:54:09 You may wish to reboot the system at this time.
Automated Installation finished successfully
The system can be rebooted now
Please refer to the /system/volatile/install_log file for details
After reboot it will be located at /var/sadm/system/logs/install_log
The following messages are common to both SPARC and x86 installations.
If the client is able to successfully boot and download the install files, then the following message is displayed:
Automated Installation started The progress of the Automated Installation will be output to the console Detailed logging is in the logfile at /system/volatile/install_log Press RETURN to get a login prompt at any time.
You can login as root with the password solaris to monitor the installation messages in /system/volatile/install_log. Once the installation of packages from IPS has started, you might not see updates to this log file for an extended period.
If you see the following message, the installation is successful:
Automated Installation finished successfully The system can be rebooted now Please refer to the /system/volatile/install_log file for details After reboot it will be located at /var/sadm/system/logs/install_log
If you have set up automatic reboot in the AI manifest, the system reboots at this time. To specify automatic reboot after successful installation, set the auto_reboot attribute of the <ai_instance> tag to true. The default value is false: The client does not automatically reboot after successful installation.
|