s11 implementation bootcamp

1 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Insert Information Protection Policy Classification from Slide 7



Solaris 11 Implementation Specialist Bootcamp

rev 2 – January 2013



Overview

• Two day Solaris 11 Implementation Engineer training bootcamp

• Recommended for previously certified individuals or highly experienced with Solaris.

• Prepare for Oracle Solaris 11 Implementation and Configuration essentials exam

• Lecture + Labs• Requires a Laptop with VirtualBox



Program Agenda

• Introduction• Solaris 11 Overview• Installation• Advanced Installation• Boot and Shutdown• File Systems and Storage• Software Management• Networking• Virtualization



Labs

• Advanced Installation• File Systems and Storage• Software Management• Networking• Virtualization



Module 1 - Introduction



Solaris 11 Bootcamp Logistics• 2 days

• 9:00 am – 5:00 pm

• 15 minute breaks

• 1 hour lunch

• Lecture

• Self directed labs– Brief overview– Self directed lab – complete at your own pace– Instructor to facilitate issues or questions

• Lab workbook

• All files necessary available on flash disks– Please return flash disks to instructor!

• Sign in Sheet



Why are we here?

• To pass the Implementation and Installation Specialist Exam for Oracle Solaris 11

• Oracle Solaris 11 Implementation Specialist– Valuable certification that counts towards Specialization

• Exam – 1Z0-580 – Oracle Solaris 11 Installation and Configuration Essentials– 120 minutes– 74 questions – multiple choice– 67% passing score– Purchase a voucher– Register your voucher at Pearson VUE for an exam time



What does the exam cover?

• Learner level vs Practitioner level questions

• Not a beginners test

• Exam Coverage Topics– Overview of Solaris 11– Basic and advanced installation– System boot and shutdown – x86 and SPARC– File systems and storage management– Virtualization– Networking

• Download the exam study guide

• Exam guide has pointers to study resources like on-line trainings and documentation



How do I pass the exam?

• Know Oracle Solaris 11

• Have a solid foundation in Solaris or Unix

• Prior Solaris certification is a big plus

• Use the Installation Essentials Exam Study Guide

• Focus is mainly on what’s new in Solaris 11

• Use the GLP (Guide Learning Path)– More courses being added soon – all on-line

• Use VirtualBox/Solaris 11 to Practice! Practice Practice

• Take a class if you can– OU – Transition to Oracle Solaris 11 – 5 day ILT– OU – Advanced Systems Administration – 5 day ILT



Other training information

• Sales and Presales GLP– On-line training with on-line exam– Presales GLP is a prerequisite for this bootcamp– Counts towards Specialization

• How-to’s and HOL’s online on Oracle.com

• Specialization for Partners– Take the OU exam for Oracle Solaris 11 classes– Associate or Professional– Take the OPN Certified Implementation Specialist exam

• OU offers ILT, LVT, and custom courses– Continue to improve your skills and stay marketable in the

industry



Module 2 – What’s New in Solaris 11



Module 3 - Oracle Solaris 11 Installation Basics



Module Agenda

• Preinstallation• LiveCD Overview• Installing with the Text Installer• AI Installs that boot from Media• AI Installs of Multiple Clients• SCI Utility

Pre Installation



Obtain Oracle Solaris 11 Software

• Access the Oracle Solaris 11.1 Downloads page• http://www.oracle.com/technetwork/server-storage/solaris11/downloads/index.html?ssSourceSiteId=ocomen

• Accept the OTN License Agreement

• LiveCD, TextInstall, AI, VirtualMachine, Repositories

• Copy the ISO to removable media– CD– DVD– Flash Drive

• Save the ISO and run it in a virtual machine

• Make sure your system meets the minimum requirements– http://docs.oracle.com/cd/E23824_01/html/E23811/glmru.html#glmuu

http://www.oracle.com/technetwork/server-storage/solaris11/downloads/index.html?ssSourceSiteId=ocomen

http://docs.oracle.com/cd/E23824_01/html/E23811/glmru.html



Setting Up Partitions

• Use the entire disk or a partition

• X86 Installer uses GRUB

• Boot multiple operating systems– Supports Multiboot Specification

• For GUI or Text Installations– You can select, create, or modify partitions during install

• For Text Install only– You can also select, create, or modify VTOC slices



Partitioning the Hard Disk

Partitioning Option DescriptionUse existing Solaris partition Installs on the existing Solaris partition

Create new Solaris partition Select a primary partition and change it’s type to Solaris. Erases the existing contents

Increase space for Solaris partition If space is available, you can increase the size that is allocated to a Solaris partition before installing

Install on different primary partition Change existing Solaris partition to ‘unused’, then select another partition and change it’s type to Solaris. Both partitions will be erased.

Create new Solaris partition in extended partition

Change existing Solaris partition to unused then create an ‘extended’ partition labeled as a Solaris partition

Delete an existing partition Delete an existing partition by changing its type to Unused. The partition will be destroyed and it’s space made available to the system.



Device Drivers

• Are your devices supported?– Check out the HCL– http://www.oracle.com/webfolder/technetwork/hcl/index.html

– Oracle Device Detection Tool– http://www.oracle.com/webfolder/technetwork/hcl/hcts/device_detect.html

– Device Driver Utility• Run from the LiveCD

http://www.oracle.com/webfolder/technetwork/hcl/index.html

http://www.oracle.com/webfolder/technetwork/hcl/index.html

http://www.oracle.com/webfolder/technetwork/hcl/hcts/device_detect.html

http://www.oracle.com/webfolder/technetwork/hcl/hcts/device_detect.html

Mini LabLiveCD Install



Starting Your LiveCD Installation - Overview

• Default settings:– Automatic DHCP and DNS– Automatic networking enables IPv6 auto configuration– NFSv4 domain is dynamically derived

• Insert media and boot the system

• GRUB menu will be displayed– If your graphics card isn’t supported, you’ll automatically go to a

text based install

• Asked for login? User = jack, password = solaris

• Make keyboard and language selections

• Double click the ‘Install Oracle Solaris’ icon



Installation Selections - Overview

• In the Welcome panel, select ‘Next’

• Choose your disk or modify the partition layout

• Select the target time zone

• Adjust date and time

• Enter a user name and password– This user account will have administrative privileges– The root password will default to the above user password

• Type a computer name

• Screens will present a summary

• Installation begins

• Do not interrupt an installation in progress. Indeterminate state may result.


Insert Information Protection Policy Classification from Slide 749 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.


Installing with LiveCD• LiveCD Start Screen




Installing with LiveCD• Choose your keyboard layout …




Installing with LiveCD• Choose your language …




Installing with LiveCD• Solaris running in memory …




Installing with LiveCD• Device Driver Utility …




Installing with LiveCD• GParted, partition your disk if necessary …




Installing with LiveCD• Choose the ‘Install Oracle Solaris’ icon …




Installing with LiveCD• Ready to start the installation …




Installing with LiveCD• Check the release notes first …




Installing with LiveCD• Disk discovery …




Installing with LiveCD• Choosing where to install Solaris 11 …




Installing with LiveCD• Choose your time zone, date, and time …




Installing with LiveCD• Add a user, and name your system …




Installing with LiveCD• Register for support …




Installing with LiveCD• Review the settings …




Installing with LiveCD• Copying files, wait just a bit …




Installing with LiveCD• Install complete …




Installing with LiveCD• Check the install log in case there are any issues …




Installing with LiveCD• Our instance is ready after a reboot …




Installing with LiveCD• Fresh install, ready to login …




Installing with LiveCD• First login, ready to get to work …

Mini Lab Text based Install



Installing with the Text Installer - Overview

• LiveCD appropriate for desktop or laptop

• Text Install appropriate for general purpose Server– No Gnome/Desktop environment

• Networking with Text Installer– Automatic – automatic NCP similar to LiveCD method– Manually – DefaultFixed NCP – static IPv4 configuration– None – DefaultFixed NCP – loopback interface only

• Familiar steps to install …– Download the image– Copy it to media– Check your system requirements– Insert the media and boot the system




Installing with the Text Installer• Choose your keyboard layout …




Installing with the Text Installer• Choose your language …




Installing with the Text Installer• Choose 1 to install Oracle Solaris 11 …




Installing with the Text Installer• Welcome screen, hit F2 to continue …




Installing with the Text Installer• Disk discovery method




Installing with the Text Installer• Partition your disk …




Installing with the Text Installer• Entire disk or partition selection …




Installing with the Text Installer• System name and network selection …




Installing with the Text Installer• Manual network configuration …




Installing with the Text Installer• Name services selection




Installing with the Text Installer• Name services selection details …




Installing with the Text Installer• Further name services selections …




Installing with the Text Installer• Time zone …




Installing with the Text Installer• System time and date …




Installing with the Text Installer• Add root password and default user …




Installing with the Text Installer• Sign up for support




Installing with the Text Installer• Review your settings …




Installing with the Text Installer• Install proceeding …




Installing with the Text Installer• Success!




Installing with the Text Installer• Instance ready to boot …




Installing with the Text Installer• Log in and get to work …

Automated Installs (AI) booting from media



Installing using AI Media - Overview

• Initiate installation on SPARC or x86 by using media rather than booting over the network if that’s not desirable for whatever reason.

• Utilize CD, DVD, or USB media

• Hands free installation of that particular system

• Don’t need to set up an install server or service

• Don’t need to boot over the network

• System will need network access to retrieve required software from the repo



Installing using AI Media



Installing using AI Media

• Check your requirements – Solaris 11 Release Notes

• Access to following resources:– DHCP server for network configuration info– IPS repository containing the necessary packages– If using a custom manifest, an http server to house it

• Download the AI boot image

• Review the default manifest

• Create bootable media– SPARC and x86 ISO images – burn the image to a CD or DVD– X86 USB images – use the usbcopy utility

• Boot from the media

• Provide info via the SCI Tool panels



Using a Custom AI Manifest

• Use the default or create your own

• Store it on an http server

• Provide the location when you boot the system to be installed

• Don’t need to specify if using the default manifest

100

Copyright © 2012, Oracle and/or its affiliates. All rights reserved.



• SPARC System example:– ok boot cdrom – install aimanifest=prompt– Enter the URL for the AI manifest [HTTP, default]:– You type – http://example.com/custom.xml

• X86 will boot from the GRUB menu

101






Automated Install (AI) multiple clients

103





AI With Multiple Clients - Overview

• AI can install Oracle Solaris 11 on multiple client systems over a network

• Hands free installation of both SPARC and x86

• Clients can be customized– Disk layout– Software selection– Hostname, network config, user accounts

• Scaled for large environments

104



AI With Multiple Clients

• Client boots over the network

• Install Server provides boot image to the client

• Installation instructions followed according to type of client

• Oracle Solaris 11 is installed on the client

• Packages are pulled from the repository according to instructions provided in the AI Install Service

What is an Automated Installation?

105




• DHCP

• AI Install service on an AI server– DHCP and AI server can be on the same machine

• Available repository– Net boot install image is not complete, will need to access a repo

to install a full image

• Each type of machine needs it’s own service– SPARC vs x86

• AI Manifests can be used to differentiate client details in similar OS installs

Requirements

106






• For parameters like time zone, user accounts, and networking

• Use an SMF system configuration profile– sysconfig create-profile –o sc.xml

• Use installadm create-profile to validate the profile

System Configuration Instructions

107




• Local repository will improve performance

• Make a local copy– pkgrecv -s http://pkg.oracle.com/solaris/release/ -d /export/repoSolaris11 '*'

• Customize the AI Manifest to specify the new repo as the default

• Customize the default-arch install service

Provide a local IPS Package Repository

108




• Custom First Boot Script

• To add configuration options that can’t be expressed in an AI Manifest or System Configuration profile

• Script runs at first boot of client– Create a script– Create a run-once SMF Service to run the script– Create an IPS package for the service and the script– Add the package to the local IPS Repository– Make the repository accessible to client systems– Customize the AI Manifest to specify the new repository and

specify the new package to be installed– Run the installadm update-manifest command to

replace the default AI manifest

Using the SCI Utility

110






• The interface for configuring, unconfiguring, and reconfiguring a Solaris instance

• Interactive or noninteractive

• Use for newly created non-global zones or unconfigured systems

• # sysconfig– unconfigure– configure– create-profile –o <profile_name.extension>

111






112






113






114






115






116






117






118






119






120






121






122






123



What We Learned

• LiveCD Overview

• Installing with the Text Installer

• AI Installs that boot from Media

• AI Installs of Multiple Clients

• SCI Utility

Next Steps

• Advanced Installation Lab

124



Module 4 – Advanced Installation Lab Overview

125



Module Agenda

• System Shakedown

• Section 4 lab overview

• Lab

126



System Shakedown

• Take a few minutes to make sure everyone is up and running according to plan!

• 15-30 Minutes allotted – we’ll get started as soon as everyone is up and running.

• Requirements outlined on the next 3 slides

127



Hardware System Requirements

• Laptop that supports Virtualization– Intel VT-x– AMD – AMD-v– Usually needs to be enabled via the systems BIOS– Check your BIOS to be sure

• At least 3GB of memory please!

• 30 GB or more diskspace

• USB port

• No external networking required

128





Software System Requirements

• VirtualBox 4.2 Windows

• Oracle VM Extension Pack 4.2

• Solaris ISO Images

File Type File Name

Automated Install (AI) sol-11_1-ai-x86.iso

Text Install sol-11_1-text-x86.iso

VM pre-built Image OracleSolaris11_1-11_VM.gzSolaris Repository sol-11_1-repo-full.iso

• Pre-built image = OracleSolaris11_1.ova

• Repository = two files .iso-a and .iso-b

• You will need to concatenate these files into one iso

• All files available from Instructor on USB Flash Disk

• Please return the Flash Disk!

129



VirtualBox Install and Image Install

• VirtualBox Hypervisor installation and configuration– Starts on page 3 of the lab guide– Exercise 5.1

• Install VirtualBox

• Install and configure the text based Solaris 11 instance– Sol-11_1-text-x86.iso– Page 7

• Start the server once it’s installed – page 9

• Basic configuration – page 10

• Boot from hard disk – page 17

• Start the lab– Exercise 5.4 – page 17

Let’s get started!

131



Advanced Installation Lab

• Automated Installation (AI) basics

• System Configuration Tool (SCI Tool)

• System Configuration Profiles

• Boot environments

• Image Packaging System (IPS)

What you’ll be learning

132



Lab Overview

• Set up Oracle Solaris 11 in VirtualBox

• Configure an IPS Repository

• Install software from the IPS repository

• Create boot environments as backups

• Configure the IPS repository as a network service

• Create an Install Service on your server

• Install a client from your install server

• Customizing the AI Manifest

• Boot the client with a customized AI Manifest

• Further client customizations

• Log file locations

133



Oracle Solaris 11 Commands Used In This Lab

• svcadm– Issues requests for actions on services within SMF

• pkg– Image Packaging System retrieval client

• beadm– User interface for managing ZFS Boot Enviroments (BE)

• dladm– Administer network data-links

• svccfg– Manipulates data in the service configuration repository

• installadm– Automated Installer configuration utility

• sysconfig– Interface for configuring and unconfiguring a Solaris instance

134



Logistics

• Lab should take approximately 3 hours• Ask questions!• Feel free to experiment once you’ve completed the lab• Make sure you’ve done a backup before you change

anything major. – beadm create backup1

• We’ll do a wrap up after the lab

135



Module 5 - Oracle Solaris 11 Boot and Shutdown

136



Module Agenda

• Introduction• SPARC OBP Overview• X86 BIOS Overview• Boot phases• GRUB Menu• Booting the System• Troubleshooting Boot• Q&A

Introduction

138



System Overview

• OBP = Open Boot Prom

• BIOS = Basic Input Output System

• OBP and BIOS is where the OS interacts with the hardware.

Modern Sun CPU Architecture names for referenceName DescriptionSun-4u 64-bit UltraSPARC (V9)

First used in Sun Ultra SeriesSun-4u1 E10K (starfire) 64 way multiproc architectureSun-4us Variant of 4u specific to Fujitsu PrimepowerSun-4v Variant of 4u which includes hypervisor virtualization

SPARC OBP

140



Features of OpenBoot Prom

• Test and initialize system hardware

• Determine the hardware configuration

• Boot the operating system– Mass storage– Network

• Interactive debugging facilities

• Processor independent design

141



OpenBoot Prom Features

• Plug in device drivers– Used to boot the O/S from a specific device– Enables devices to change without prom changes

• FCode interpreter– Machine independent language– Drivers written in Fcode

• Device tree– Data structure describing the devices

• Programmable user interface– Forth code

142



Device Path Overview

• Device tree overview– Data structure describing the hardware devices attached to the

system– Users and the O/S can determine the hardware configuration from

inspecting the device tree– Representation of the physical interconnected busses on a system– Ex: pci@1f,0/network@c,1

• Device path names– Device name

• Human readable string

– @• Must precede the address parameter

– Unit address• Physical address of the device

– Device arguments

143



Device Aliases

• Shorthand representation of a device path

• Systems usually have predefined aliases for commonly used devices– disk– net

• devalias command– Examine, create, and change device aliases

• Display all current device aliases– devalias

• Display the device path corresponding to an alias– devalias alias

• Define an alias– devalias alias device

144



Mini Lab

• Login to the service processor (SP) to take a look at some basic parameters.

ok printenv

BootPROM Overview

145



• Check basic information contained in the boot prom.ok printenv auto-boot?ok printenv boot-deviceok printenv boot-command

• Auto-boot? – Checks whether the system will boot automatically or not

• Boot-device – Which device the system will boot to

• Boot-command– The default boot command and any provided options

Mini LabBootPROM Overview

146



• Set the parameters to boot from the network..ok show-devs /pci/


147



• Devices are tedious• Change device names to something easy with

‘devalias’ command


148



• Look at specific devices# devalias net3

• Use this command to alias a device name to a usable device in the system

# nvalias net3 /pci@7c0/pci@0/pci@2/network@0,1:dhcp

# devalias net3


149



• Check the boot device orderok printenv boot-deviceok disk net

• Run devalias and identify the boot devices

ok devalias

• Which ones are the boot devices?


X86 BIOS

151



X86 BIOS Main (X2-8 / X4800)

152



X86 BIOS Boot (X2-8/ X4800)

153



X86 BIOS Boot Settings (X2-8/ X4800)

154



X86 BIOS Boot Device Priority (X2-8/ X4800)

155



X86 BIOS Overview

• Access BIOS Setup by pressing F2 key during POST– Use left, right, and tab keys to navigate– Contains help menus

• BIOS can be upgraded through ILOM

Boot phases

157



Booting Your System

• Main function of OpenBoot is to boot your system

• Process controlled by a number of configuration variables– auto-boot? – whether or not to boot automatically– boot-command – which command should be executed?– diag-switch - sets whether to run diagnostic mode– boot-device – name of the default boot device– boot-file – boot arguments when not in diagnostic mode– diag-device – default diagnostic mode boot device– diag-file – diagnostic mode boot arguments

158



SPARC Boot Phases

• Open Boot PROM phase– OBP– Boot block is loaded into system memory

• Boot phase– Boot archive is read and executed– Relies on boot file system format (disk, NFS, http)

• Ramdisk phase– Contains kernel modules and components to boot Solaris 11

• Kernel phase– Final stage of the boot process– Root filesystem is mounted on the ramdisk– For installation, the ramdisk remains mounted– If not, it extracts the remaining primary modules from the boot

archive and mounts the real root filesystem

159



X86 Boot Phases

• BIOS phase: – BIOS initializes the CPU, memory, and platform hardware

• Boot Loader phase– First software that runs when you turn on a system– Loads from the configured boot device– Starts the boot process

• GRUB is the boot loader on Oracle Solaris– Grand Unified Boot Loader– Responsible for loading a boot archive into system memory.– Boot archive is a collection of critical files needed during system

startup– Run from configuration file – menu.lst– Solaris kernel is fully compliant with the Multiboot Specification.

160



• To watch the boot process of a SPARC system you can use the boot –v option from the OpenBoot prom console.

ok boot -v

SPARC Boot Phase Example

161



SPARC Boot Phase Example

• You can also get the information after the system has booted by using the dmesg command

# /usr/sbin/dmesg | more

162



x86 Boot Phase Example

• Here’s an example from an x86 system

# /usr/sbin/dmesg | more

• The information contained in the boot –v and dmesg output is several pages long, these are shortened examples.

• Pipe the output to a file and use your favorite editor to look for information in this file.

GRUB Menu

164



GRUB Menu

• Grand Unified Bootloader

• Developed and supported by the Free Software Foundation

• Highly Portable

• Variety of user interfaces

• Supports O/S’s that don’t support Multi-Boot by ‘chain-loading’

• Default boot loader on Solaris x86

• Loads boot-archive into system memory

• Solaris specific GRUB utilities– Bootadm – manage the boot archive and change GRUB– Installgrub – loads the boot program from disk

165



GRUB Components

• Stage1 – image on the first sector of the fdisk partition.

• Stage2 – image installed in the reserved area of the fdisk partition

• Menu.lst file - /pool-name/boot/grub directory.

• Menu.lst is read by stage2.

166



GRUB Menu Example

167



Mini-Lab

• Locate the GRUB menu on your system

• # bootadm list-menu

Using bootadm to change the GRUB menu

168



View the current contents of menu.lst# cat /rpool/boot/grub/menu.lst (output truncated)

Mini-LabUsing bootadm to change the GRUB menu

169



• Create a new boot environment and call the new environment ‘solaris2’

# beadm create solaris2# bootadm list-menu

• The second entry (1) was added automatically by the beadm command


170



• Use the bootadm command to change the menu default from (0) ‘Oracle Solaris’ to (1) ‘solaris2’

# bootadm set-menu default=1# bootadm list-menu

• Note the number by the default item has changed from 0 to 1


171



• Using bootadm has also influenced the current boot order. We can verify this by using the beadm list command:

# beadm list

• Note that solaris is the current environment ‘N’ and solaris2 will be active on reboot ‘R’

• You can change it back to the default with # beadm activate solaris


Booting the system

173



Boot Commands

• Default boot– boot – (options – init level or milestone)– boot –m milestone=milestone

• System reset– ok boot –r– ok reset-all– # sync; reboot– # init 6

• Useful milestones– none (Useful for debugging – manual service start)– all – single-user– multi-user– multi-user-system

174



Fast Reboot - SPARC

• Managed by SMF on SPARC systems• svc:/system/boot-config

– fastreboot_default=true

• Default = false• Only available on certain systems• On sun4v systems fast reboot is unnecessary

– Hypervisor restart not involving POST

175



Fast Reboot – x86

• Managed by SMF on x86 systems• svc:/system/boot-config

– fastreboot_default=true

• Default is true• Bypasses the firmware and boot loader processes• Utilized by the ‘init 6’ command• To boot a system normally when fast boot is

enabled– reboot -p

176



uadmin command

• Helpful command for admins is uadmin• Uses numbered options and can drop the system

directly into the ok prompt.• Ex: # uadmin 2 0

– Syncs the file system and brings you to the ok prompt

uadmin 2 0 sync the filesystems and drops system to ok promptuadmin 2 1 sync the filesystems and reboots to multi-user modeuadmin 2 2 sync the filesystems and reboots interactivelyuadmin 2 3 sync the filesystems and reboots to single-user modeuadmin 2 6 sync the filesystems and powers off the systemuadmin 1 0 do not sync filesystems and drops system to ok promptuadmin 1 1 do not sync filesystems and reboots to multi-user modeuadmin 1 2 do not sync filesystems and reboots interactivelyuadmin 1 3 do not sync filesystems and reboots to single-user modeuadmin 1 6 do not sync filesystems and powers off the system

177



Run Levels and Milestones

• Both describe what services and resources are available to users

• Move to SMF encourages use of milestones vs run-levels

• Run levels are based on init• Milestones are based on SMF

178



Milestones

179



Run Levels

Run Level

Init State Type Purpose

0 Power Down Power-Down Shut down the O/S, safe to turn off power

S or S Single User Single-user Some file systems mounted and accessible

1 Administrative Single-user All file systems available, user logins disabled

2 Multiuser Multiuser Normal operations, all daemons running except NFS

3 Multiuser NFS shared Multiuser Normal operations, NFS shared. Default run level

4 Alternative Multiuser Multiuser Available for customer use

5 Power-Down Power-down Shut down the O/S, safe to power off. Auto power off

6 Reboot Reboot Shut down system to run level 0, then reboot to default run level

180



Run Levels vs SMF Milestones

Run Level MilestoneS Milestone/single-user:default2 Milestone/multi-user:default3 Milestone/multi-user-server:default

• The table below shows which milestones correspond to which run-levels

181



Network Boot

• Client knows it’s MAC but needs an IP address• Uses TFTP to transfer from the network via …

– dhcp– bootp– Rarp

• Bootprom uses bootparams file to obtain boot parameters

• ok boot <full_path_to_network_device>

• Ex: ok boot /pci@7c0/pci@0/pci@2/network@0,1

• DHCP offers the most flexibility

• For network boot you can supply options directly …– boot - <path> :dhcp|bootp server=ip, boot filename, client-ip,

router-ip, boot-retries,tftp-retries, subnet-mask

Boot Troubleshooting

183



Boot Process Hangs

• ok boot –m milestone=none– Manually start services and see if you can figure out which one’s

causing the problem

• ok boot –m verbose– Will print a line of information when each service is started

• Run svcs –a to determine service state

• Check /var/svc/log for error messages

184



Single User Mode

• Resolve a bad root shell• Resolve password problems• Troubleshoot driver failures• Troubleshoot application issues• Troubleshoot network issues

185



Mini Lab

• Stop or reboot the system

• Select the boot item from the GRUB menu

Bringing an x86 system to single user

186



• Type ‘e’ to edit the menu item

Mini LabBringing an x86 system to single user

187



• Type ‘e’ to again to edit the kernel line item

• Enter ‘-s’ at the end of the kernel line


188



• Type ‘b’ to boot the system in single user mode


189



Boot From Media – Live Media

• Boot and use a GNOME terminal for recovery

190



Boot From Media – Text Install

• Select option 3 – text shell from the GRUB boot menu

191



Boot From Media - AI

• Automated Installation– PXE boot from the network, then select a shell

192



Recover the Root Password (1)

• Import the root pool# zpool import –f rpool

• Create a mount point# mkdir /a

• Mount the boot environment# beadm mount solaris-2 /a

• Set the TERM type# TERM=vt100# export TERM

• Edit the shadow file# cd /a/etc# vi shadow

Mini Lab

193



• Update the boot archive# bootadm update-archive /R /a

• Unmount the boot environment# beadm unmount solaris-2

• Halt the system# halt

• Reboot into single user mode• Reset the root password# passwd –r files rootNew password: xxxxxxRe-enter new Password: xxxxxxx

• Reboot the system

Recover the Root Password (1)Mini Lab

194



Correct Problems With menu.lst File

• Import the root pool# zpool import –f rpool

• Examine the menu.lst file– # cd /rpool/boot/grub– # vi menu.lst

• Update the boot archive# bootadm update-archive /R /a

• Exit the shell and reboot the system

195



Force a Crash Dump

• Kernel Debugger– Kmdb prompt from F1-A

• or

• # halt -d

196



AI Client Boot Load Failure

• AI Client fails when downloading the boot archive• Indicates that DHCP client is incorrectly configured• Error can occur if another DHCP server interferes• Use in.dhcpd –dv to run dhcp daemon in debug

mode# /usr/lib/inet/in.dhcpd -dv

Rebooting with command: boot net:dhcp - install Boot device: /pci@7c0/pci@0/network@4:dhcp File and args: 1000 Mbps FDX Link up HTTP: Bad Response: 500 Internal Server Error Evaluating: Boot load failed

197



Module Agenda

• Introduction• SPARC OBP Overview• X86 BIOS Overview• Boot phases• GRUB Menu• Booting the System• Troubleshooting Boot• Q&A

198



Module 6 – File Systems and Storage Lab Overview

199



File Systems and Storage What you’ll be learning

• The ZFS File System

• Zpools

• Vdevs

• Datasets

• Snapshots and clones

• ZFS Properties

• ZFS Updates

200



Lab Overview

• VirtualBox should be running already– Import and configure the pre-built Oracle Solaris 11 VM Image– Configure virtual SAS disks in your VM Image– Configure Solaris 11.1

• Create and destroy ZFS pools

• Add capacity to a pool

• Import and export pools

• Exploring pool properties

• Upgrading pools

201



Lab Overview

• Split ZFS mirrors using the split command

• Working with Datasets– Hierarchical datasets– Properties

• Quotas and reservations

• Zvols

• Snapshots and clones

• Compression

202




• format– Format, label, repair, and analyze disks on your system

• zpool– Configures ZFS storage pools. Pool is a collection of devices that

provide physical storage

• zfs– Configures datasets within a ZFS storage pool.

203



Logistics

• Lab should take approximately 1 and ½ hours

• Don’t forget to create the virtual disks in VirtualBox

• Ask questions!

• Feel free to experiment once you’ve completed the lab• Make sure you’ve done a backup before you change



204



Module 7 – Software Management Lab Overview

205



Solaris 11 Software ManagementWhat you’ll be learning

• Image Packaging System Basics

• IPS command line overview

• How to configure a repository

• Installing and uninstalling packages

• Getting information about packages

• Searching for packages

• Package manifest basics

206



Lab Overview

• Use AIServer instance– This lab will use the AIServer VirtualBox instance created in

module 4, the first hands on lab– sol-11_1-text.x86.iso– Oracle Solaris Repository file

• sol-11_1-repo-full.iso

• Repository basics

• Install and uninstall packages

• Getting information about packages

• Updating the system

• Package Dependencies

207




• pkg– Retrieval client for the Image Packaging System

• pkgrepo– Provides the ability to create and manage package repositories

• beadm– User interface for managing ZFS boot environments.

208



Logistics

• Lab should take approximately 1 hour

• Ask questions!




209



Module 8 – Networking Lab Overview

210



Oracle Solaris 11 NetworkingWhat you’ll be learning

• Network Configuration Profiles

• Manual network configuration in Solaris 11

• SMF network services configuration

211



Lab Overview

• VirtualBox should be running– This lab will use the pre-configured Oracle Solaris 11 VM Image– OracleSolaris11_1.ovf– Create 4 virtual network interfaces

• Planning the network deployment

• Network command basics

• Network configuration profiles

• Displaying and configuring link interfaces

• Configuring Name services using SMF

212



Oracle Solaris Commands Used In This Lab

• netadm– Administers network profiles and interacts with the NWAM daemon

• dladm– Administers data-links

• ipadm– Manages network interfaces, addresses, and TCP/IP protocol properties

• svccfg – Manipulates data in the service configuration repository. Can be

invoked interactively, with a single command, or within a script

• svcadm– Issues requests for actions on services within SMF

213



Logistics


• Ask questions!




214



Section 9 – Virtualization Lab Overview

215



Oracle Solaris 11 VirtualizationWhat you’ll be learning

• Basics of zones

• How to set up a zone

• How to install a zone

• How to set up a zone with a single command

• How to set up a zone by cloning another zone

• How to destroy a zone

216



Lab Overview

• VirtualBox should be running– This lab will use the Text Image that we installed in Lab 4– sol-11_1-text-x86.iso– We will also utilize the installed Repository

• Create a zone called ‘testzone’– Configure and install ‘testzone’

• Create another zone called ‘webzone-1’– Using a single command– Configure and install ‘webzone-1’

• Create another zone called ‘webzone-2’ – Using ZFS cloning technology

• Optionally – Uninstall the zones

217




• zonecfg– Creates, modifies, and lists the configuration of a zone

• zoneadm– Administers system zones.

• zlogin– Used to enter an operating system zone.

218



Logistics


• Ask questions!




219



Section 10 - Wrap Up

220



Thank you!

• Bootcamp Overview

• Technical Overview

• Installation

• Lab Intro – System Shakedown

• Lab – Advanced Installation

• Boot and Shutdown

• Lab - File Systems and Storage

• Lab – Software Management

• Lab – Networking

• Lab – Virtualization

• Take Exam!

221



Oracle Solaris 11Practice and Study

• Continue to use the VirtualBox image to practice and study

• Utilize the Oracle Solaris 11 Documentation for reference

• Utilize the exam study guide

• Use the Implementation GLP for on-line courses

• Take the practice exam webinar or on-line

222



Oracle Solaris 11

• Please fill out the feedback form before you leave!

• We appreciate your suggestions for making this a better experience.

•Thank you and good luck!

223



s11 implementation bootcamp

Technology

oracle solaris

oracle andor

day solaris

installation specialist

ou exam

exam study guide exam

exam time

training information