| Skip Navigation Links | |
| Exit Print View | |
|
Oracle Solaris 11 Express Automated Installer Guide Oracle Solaris 11 Express 11/10 |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Oracle Solaris 11 Express Automated Installer Guide Oracle Solaris 11 Express 11/10 |
1. Automated Installer Overview
2. Setting Up an AI Install Server
4. Specifying Installation Instructions
5. Configuring the Client System
SPARC and x86 Client System Requirements
Additional SPARC Client System Requirements
Does My SPARC Client Support WAN Boot?
Deleting a Client From a Service
Using Secure Shell to Remotely Monitor Installations
Monitoring x86 Client Installations
Monitoring SPARC Client Installations
SPARC Client Network Boot Sequence
Sample SPARC Network Boot Output
x86 Client Network Boot Sequence
Sample x86 Network Boot Output
8. Automated Installations That Boot From Media
A. Troubleshooting Automated Installations
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 /tftpboot/ directory with one of the following filename formats.
If you used the installadm create-client command, the filename is 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 menu.lst.service_name, where service_name is the install service name that was specified in 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 install.conf file is populated in the ai_image_dest directory when an install service is created by using an installadm create-service command.
In the install.conf file, the options are defined as name-value pairs. In the following example, the livessh option is set to enable.
$ cat ai_image_dest/install.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 boot file, wanboot-cgi, from the DHCP server.
The wanboot-cgi boot file 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 SMF service uses multicast DNS (mDNS) to contact the HTTP server and get the AI manifest.
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:
{3} ok boot net:dhcp - install
...
OpenBoot 4.23.4, 8184 MB memory available, Serial #69329298.
Ethernet address 0:14:4f:21:e1:92, Host ID: 8421e192.
Rebooting with command: boot net:dhcp - install
Boot device: /pci@7c0/pci@0/network@4:dhcp File and args:
1000 Mbps FDX Link up
1000 Mbps FDX Link up
<time unavailable> wanboot info: WAN boot messages->console
<time unavailable> wanboot info: Starting DHCP configuration
<time unavailable> wanboot info: DHCP configuration succeeded
<time unavailable> wanboot progress: wanbootfs: Read 366 of 366 kB (100%)
<time unavailable> wanboot info: wanbootfs: Download complete
Tue Aug 5 17:12:09 wanboot progress: miniroot: Read 165251 of 165251 kB (100%)
Tue Aug 5 17:12:09 wanboot info: miniroot: Download complete
SunOS Release 5.11 Version snv_151 64-bit
...
Hostname: solaris
Remounting root read/write
Probing for device nodes ...
Preparing automated install image for use
Downloading solaris.zlib archive
--11:09:11-- http://10.6.35.226:5555//export/home \
/images/s11-ai-sparc//solaris.zlib
=> `/tmp/solaris.zlib'
Connecting to 10.6.35.226:5555... connected.
HTTP request sent, awaiting response... 200 OK
Length: 82,679,296 (79M) [text/plain]
100%[====================================>] 82,679,296 33.39M/s
11:09:13 (33.36 MB/s) - `/tmp/solaris.zlib' saved [82679296/82679296]
Downloading solarismisc.zlib archive
--11:09:13-- http://10.6.35.226:5555//export/home/images \
/s11-ai-sparc//solarismisc.zlib
=> `/tmp/solarismisc.zlib'
Connecting to 10.6.35.226:5555... connected.
HTTP request sent, awaiting response... 200 OK
Length: 620,032 (606K) [text/plain]
100%[====================================>] 620,032 --.--K/s
11:09:13 (36.48 MB/s) - `/tmp/solarismisc.zlib' saved [620032/620032]
--11:09:13-- http://10.6.35.226:5555//export/home/images/ \
s11-ai-sparc//install.conf
=> `/tmp/install.conf'
Connecting to 10.6.35.226:5555... connected.
HTTP request sent, awaiting response... 200 OK
Length: 39 [text/plain]
100%[====================================>] 39 --.--K/s
11:09:13 (953.58 KB/s) - `/tmp/install.conf' saved [39/39]
Done mounting automated install image
Configuring devices.
Reading ZFS config: done.
Automated Installation started
The progress of the Automated Installation can be followed by
viewing the logfile at /tmp/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 is downloaded from an HTTP server specified in the GRUB menu or from the mDNS lookup performed by the AI SMF service.
The AI install program is invoked with the AI manifest to perform the installation.
The first screen displays the following message when the client receives the correct DHCP response:
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 Express boot image Oracle Solaris 11 Express Automated Install
The default GRUB menu entry, “Oracle Solaris 11 Express boot image,” boots the image without starting a hands-free automated installation. Select the second entry in the GRUB menu, “Oracle Solaris 11 Express Automated Install,” to initiate an automated installation.
Once the image is selected, the following messages are displayed:
SunOS Release 5.11 Version snv_151 64-bit
...
Hostname: solaris
Remounting root read/write
Probing for device nodes ...
Preparing automated install image for use
Downloading solaris.zlib archive
--11:09:11-- http://10.6.35.226:5555//export/home \
/images/s11-ai-x86//solaris.zlib
=> `/tmp/solaris.zlib'
Connecting to 10.6.35.226:5555... connected.
HTTP request sent, awaiting response... 200 OK
Length: 82,679,296 (79M) [text/plain]
100%[====================================>] 82,679,296 33.39M/s
11:09:13 (33.36 MB/s) - `/tmp/solaris.zlib' saved [82679296/82679296]
Downloading solarismisc.zlib archive
--11:09:13-- http://10.6.35.226:5555//export/home/images \
/s11-ai-x86//solarismisc.zlib
=> `/tmp/solarismisc.zlib'
Connecting to 10.6.35.226:5555... connected.
HTTP request sent, awaiting response... 200 OK
Length: 620,032 (606K) [text/plain]
100%[====================================>] 620,032 --.--K/s
11:09:13 (36.48 MB/s) - `/tmp/solarismisc.zlib' saved [620032/620032]
--11:09:13-- http://10.6.35.226:5555//export/home/images/ \
s11-ai-x86//install.conf
=> `/tmp/install.conf'
Connecting to 10.6.35.226:5555... connected.
HTTP request sent, awaiting response... 200 OK
Length: 39 [text/plain]
100%[====================================>] 39 --.--K/s
11:09:13 (953.58 KB/s) - `/tmp/install.conf' saved [39/39]
Done mounting automated install image
Configuring devices.
Reading ZFS config: done.
Automated Installation started
The progress of the Automated Installation can be followed by
viewing the logfile at /tmp/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 can be followed by viewing the logfile at /tmp/install_log
You can login as root with the password solaris to monitor the installation messages in /tmp/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:
Auto install succeeded. You may wish to reboot the system at this time.
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.
|