| Skip Navigation Links | |
| Exit Print View | |
|
Transitioning From Oracle Solaris 10 to Oracle Solaris 11.1 Oracle Solaris 11.1 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Transitioning From Oracle Solaris 10 to Oracle Solaris 11.1 Oracle Solaris 11.1 Information Library |
1. Transitioning From Oracle Solaris 10 to an Oracle Solaris 11 Release (Overview)
2. Transitioning to an Oracle Solaris 11 Installation Method
6. Managing Software and Boot Environments
7. Managing Network Configuration
8. Managing System Configuration
10. Managing Oracle Solaris Releases in a Virtual Environment
11. Managing User Accounts and User Environments
A. SPARC Automated Installation Scenario
The following example illustrates the primary tasks of configuring an AI server to install a SPARC based system on an IPv4 network with a local package repository, and a minimally customized AI manifest.
This example uses the following configuration options:
DNS is configured for name resolution
The AI server provides a local package repository
DHCP is configured for the install service
The install client is a SPARC based system
Configuration steps covered in this task:
Confirm the installation server's static IP and router information.
Identify the DHCP range of IPs addresses to install, if necessary.
When you create the install service, you need to specify the starting address of the IP address range and the number of addresses.
You can specify fixed IP addresses for client systems in the following ways:
Generate a system configuration profile with the sysconfig tool or customize a profile in /usr/share/auto_install/sc_profiles and add it to the install service.
# sysconfig create-profile -o /var/tmp/manifests/client_sc.xml
Include fixed IP addresses in the /etc/inet/dhcpd.conf file. See Example A-3.
Create a customized script that associates client systems' MAC addresses with a specific IP address and install server.
If you want to use DNS for name resolution, make sure the DNS server is accessible.
Example A-1 How to Confirm Network Related Resources Are Available
Confirm the install server has a static IP and router information.
# ipadm show-addr ADDROBJ TYPE STATE ADDR lo0/v4 static ok 127.0.0.1/8 e1000g0/v4static1 static ok 1.2.3.10/24 lo0/v6 static ok ::1/128 e1000g0/v6dhcp addrconf ok fe80::aaa:bbbb:cccc:8988/10 # netstat -nr Routing Table: IPv4 Destination Gateway Flags Ref Use Interface -------------------- -------------------- ----- ----- ---------- --------- default 1.2.3.1 UG 3 115957 net0 1.2.3.64 1.2.3.10 U 4 287300 net0 127.0.0.1 127.0.0.1 UH 2 116 lo0 . . .
Make sure the DNS server is accessible.
# getent hosts daleks 1.2.3.99 daleks
Configuration steps covered in this task:
Download a repository image from pkg.oracle.com and mount the image
Create a file system for the repository and copy the image into the repository file system
Refresh the repository
Enable the package repository service so that it can be available from an http: location
Example A-2 How to Create a Local Package Repository
These steps are performed on the install server or on another system that is accessible over the network.
Copy the repository image by using your favorite tool, such as rsync or tar. Using tar is generally faster than rsync, but the tar operation might take a while.
# mount -F hsfs /tmp/sol-11_1-repo-full.iso /mnt # zfs create rpool/export/s11.1repo # cd /mnt/repo; tar cf - . | (cd /export/s11.1repo; tar xfp - ) # pkgrepo -s /export/s11.1repo refresh Initiating repository refresh.
Next, start the package service so that the package repository is accessible.
# svccfg -s application/pkg/server setprop pkg/inst_root=/export/s11.1repo # svccfg -s application/pkg/server setprop pkg/readonly=true # svcadm refresh application/pkg/server # svcadm enable application/pkg/server # pkg set-publisher -G "*" -g http://tardis.dw.com/ solaris
Configuration steps covered in this task:
Confirm that the installadm package is installed
Create a file system for the image that is created from the local package repository
Start the multicast DNS service
Create the install service
Add the client information to the install service
Example A-3 How to Create an Install Service
The following steps are performed on the install server to create the install service. In Oracle Solaris 11.1, the install service image can be created directly from a local package repository.
Confirm that the install/installadm package is available.
# pkg info installadm
Name: install/installadm
Summary: installadm utility
Description: Automatic Installation Server Setup Tools
Category: System/Administration and Configuration
State: Installed
Publisher: solaris
Version: 0.5.11
Build Release: 5.11
Branch: 0.175.1.0.0.24.1736
Packaging Date: Wed Sep 12 19:32:53 2012
Size: 1.23 MB
FMRI: pkg://solaris/install/installadm@0.5.11,5.11-0.175.1.0.0.24.1736:
20120912T193253Z
If not installed, install it:
# pkg install install/installadm
Create a file system for the image and enable the multicast DNS service. Then, create the install service. In this example, the starting DHCP address is specified with the -i option and the -c option identifies the number of addresses. This syntax creates an ISC DHCP server on the install server if it does not already exist.
# zfs create rpool/export/image # svcadm enable svc:/network/dns/multicast:default # installadm create-service -n sol-11u1-sparc -d /export/image -i 1.2.3.66 -c 20 Creating service from: Creating service from: pkg:/install-image/solaris-auto-install Setting up the image ... DOWNLOAD PKGS FILES XFER (MB) SPEED Completed 1/1 45/45 237.8/237.8 0B/s PHASE ITEMS Installing new actions 187/187 Updating package state database Done Updating image state Done Creating fast lookup database Done Reading search index Done Updating search index 1/1 Creating sparc service: sol-11u1-sparc Image path: /export/image Service discovery fallback mechanism set up Creating SPARC configuration file Starting DHCP server... Adding IP range to local DHCP configuration Creating default-sparc alias Service discovery fallback mechanism set up Refreshing install services
The DCHP configuration information is included in the /etc/inet/dhcpd4.conf file. The range of dynamic IP addresses looks similar to this:
range 1.2.3.66 1.2.3.86
You can also identify fixed addresses for clients by including syntax similar to the following in the /etc/inet/dhcpd4.conf file:
host neo {
hardware ethernet 0:3:3:4:5:2 ;
fixed-address 1.2.3.88 ;
}
Add the client's MAC address to the install service:
# installadm create-client -e 0:3:ba:dd:ff:2 -n sol-11u1-sparc
If you do not specify the DHCP information when the install service is created, the SPARC client boot information is provided on the screen:
# installadm create-service -n sol-11u1-sparc -d /export/image Creating service from: Creating service from: pkg:/install-image/solaris-auto-install Setting up the image ... DOWNLOAD PKGS FILES XFER (MB) SPEED Completed 1/1 45/45 237.8/237.8 0B/s PHASE ITEMS Installing new actions 187/187 Updating package state database Done . . . Creating sparc service: sol-11u1-sparc Image path: /export/image Creating default-sparc alias Service discovery fallback mechanism set up Creating SPARC configuration file No local DHCP configuration found. This service is the default alias for all SPARC clients. If not already in place, the following should be added to the DHCP configuration: Boot file: http://1.2.3.10:5555/cgi-bin/wanboot-cgi
Configuration steps covered in this task:
Create an optional file system for the AI manifest
Export a default manifest template copy that is called sclient.xml
Modify the sclient.xml manifest to match your installation needs
Create the manifest and associate it with the install service
Display the install service and manifest to ensure that it is available
Activate the manifest
Example A-4 How to Configure an AI Manifest
The following example describes how to create a file system for manifests, modify a default manifest, and associate it with the install service.
# zfs create rpool/export/manifests # cd /export/manifests # installadm export -n sol-11u1-sparc -m orig_default -o sclient.xml # vi sclient.xml # installadm create-manifest -n sol-11u1-sparc -f ./sclient.xml -m sclient # installadm list -n sol-11u1-sparc -m # installadm set-service -o default-manifest=sclient sol-11u1-sparc # installadm list -n sol-11u1-sparc -m
The sclient manifest is modified as follows:
Add the auto_reboot keyword so that the client is rebooted automatically.
Include a local package repository (tardis.dw.com) instead of pkg.oracle.com.
The sclient manifest changes are included in bold as follows:
.
.
.
<ai_instance name="orig_default" auto_reboot="true">
.
.
.
<source>
<publisher name="solaris">
<origin name="http://tardis.dw.com"/>
</publisher>
</source>
.
.
.
If you change the manifest after it has been activated, update it so the changes take affect.
# installadm update-manifest -n sol-11u1-sparc -f ./sclient.xml -m sclient
|