network based installation

8/6/2019 Network Based Installation

1/278

Solaris 10 10/09 InstallationGuide: Network-BasedInstallations

Sun Microsystems, Inc.4150 Network CircleSanta Clara, CA 95054U.S.A.

PartNo: 821043910October 2009


2/278

Copyright2009 SunMicrosystems, Inc. 4150 Network Circle, Santa Clara,CA 95054 U.S.A. Allrightsreserved.

SunMicrosystems, Inc. hasintellectual property rightsrelatingto technology embodied in theproduct that is describedin this document.In particular, andwithoutlimitation, these intellectualpropertyrights mayinclude oneor more U.S. patents or pending patentapplications in theU.S. andin other countries.

U.S. Government Rights Commercial sotware. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicableprovisionso theFARand itssupplements.

This distribution may include materials developed by thirdparties.Partso theproduct maybe derived rom Berkeley BSDsystems, licensed rom theUniversity o Caliornia. UNIX is a registered trademarkin theU.S. andothercountries, exclusivelylicensed through X/OpenCompany, Ltd.

Sun, SunMicrosystems, theSun logo, theSolaris logo, theJavaCofeeCup logo, docs.sun.com,Sun4U,Power Management,SunOS, Ultra,JumpStart, Java, andSolaris aretrademarks or registered trademarks o SunMicrosystems, Inc. or itssubsidiaries in theU.S. andothercountries. AllSPARC trademarks areused underlicenseand aretrademarks or registered trademarks o SPARC International, Inc. in theU.S. andothercountries. Products bearing SPARCtrademarks arebasedupon an architecture developed by Sun Microsystems, Inc.

The OPENLOOK and SunTM GraphicalUser Interacewas developedby SunMicrosystems, Inc. orits users andlicensees. Sunacknowledges thepioneering efortso Xerox in researching anddeveloping theconcept o visualor graphicaluser interaces orthe computer industry.Sun holds a non-exclusive licenseromXeroxtotheXeroxGraphical UserInterace,whichlicense also coversSun'slicenseeswho implementOPENLOOK GUIs andotherwise complywith Sun's written licenseagreements.

Products covered by andinormationcontained in this publication arecontrolled by U.S. ExportControl laws andmay be subjectto theexport or importlaws inother countries. Nuclear,missile,chemicalor biological weapons or nuclear maritime enduses or endusers,whether director indirect,are strictly prohibited. Exportor reexport to countriessubject to U.S. embargo or to entities identiedon U.S. exportexclusion lists,including, butnot limited to,the deniedpersons andspeciallydesignated nationals lists is strictly prohibited.

DOCUMENTATIONIS PROVIDED AS IS AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANYIMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPTTOTHEEXTENTTHAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.

Copyright2009 SunMicrosystems, Inc. 4150 Network Circle, Santa Clara,CA 95054 U.S.A. Tous droitsrservs.

SunMicrosystems, Inc. dtient lesdroits de propritintellectuellerelatis la technologie incorpore dans le produit quiest dcritdans ce document.En particulier,et ce sans limitation, cesdroits de propritintellectuellepeuvent inclure un ou plusieursbrevets amricains ou desapplications de breveten attente auxEtats-Uniset dans d'autres pays.

Cette distribution peut comprendredes composants dveloppspar des tierces personnes.

Certainescomposants de ce produit peuvent tre drives du logiciel Berkeley BSD, licencispar l'Universitde Caliornie. UNIX estune marquedpose auxEtats-Uniset dans d'autres pays; elle estlicencie exclusivementpar X/OpenCompany,Ltd.

Sun, SunMicrosystems, le logo Sun, le logo Solaris, le logo Java Cofee Cup, docs.sun.com,Sun4U,Power Management, SunOS,Ultra, JumpStart, Java et Solaris sontdesmarques de abrique ou desmarques dposes de SunMicrosystems, Inc., ou sesliales,aux Etats-Unis et dans d'autres pays. Toutesles marques SPARCsontutilisessous licence et sont desmarques de abrique ou desmarques dposes de SPARCInternational,Inc. auxEtats-Uniset dans d'autres pays. Lesproduitsportant lesmarques SPARCsont bass surune architecturedveloppe parSun Microsystems, Inc.

L'interace d'utilisation graphiqueOPENLOOK et Suna tdveloppe parSun Microsystems, Inc. pour ses utilisateurset licencis. Sunreconnat leseforts depionniersde Xerox pour la rechercheet le dveloppement du concept desinteraces d'utilisation visuelle ou graphiquepour l'industrie de l'inormatique.Sun dtientunelicence nonexclusive de Xerox surl'interaced'utilisation graphiqueXerox, cette licence couvrant galementles licencisde Sunqui mettent en place l'interaced'utilisation graphiqueOPENLOOK et qui, en outre,se conorment auxlicencescrites de Sun.

Lesproduitsqui ont l'objet de cette publication et lesinormations qu'il contient sontrgispar la legislation amricaine en matire de contrle desexportations etpeuvent tre soumisau droit d'autres pays dans le domaine desexportations et importations. Lesutilisations nales, ou utilisateursnaux, pour desarmesnuclaires,des missiles, des armeschimiques ou biologiquesou pour le nuclaire maritime, directementou indirectement, sont strictementinterdites. Les exportations ourexportations vers despays sous embargo desEtats-Unis,ou vers desentits gurantsur leslistes d'exclusion d'exportation amricaines, y compris, mais de manirenonexclusive, la liste de personnesqui ontobjet d'un ordre de ne pasparticiper,d'uneaondirecte ou indirecte, auxexportations desproduitsou desservicesquisont rgispar la legislationamricaine en matire de contrle des exportations et la listede ressortissants spciquement designs, sont rigoureusement interdites.

LA DOCUMENTATION EST FOURNIE "EN L'ETAT" ET TOUTES AUTRES CONDITIONS, DECLARATIONS ET GARANTIES EXPRESSES OU TACITESSONT FORMELLEMENTEXCLUES, DANS LA MESUREAUTORISEE PAR LA LOI APPLICABLE, Y COMPRISNOTAMMENT TOUTE GARANTIEIMPLICITE RELATIVE A LA QUALITE MARCHANDE, A L'APTITUDE A UNE UTILISATIONPARTICULIEREOU A L'ABSENCE DE CONTREFACON.

090821@22749


3/278

Contents

Preace .....................................................................................................................................................9

Part I Planningto Install Overthe Network.............................................................................................. 13

1 Where to Find Solaris Installation Planning Inormation ............................................................ 15

Where to Find Planning and System Requirement Inormation .................................................. 15

2 Preconfguring System Confguration Inormation (Tasks) .........................................................17

Advantages o Preconguring System Conguration Inormation .............................................. 17

Preconguring With the sysidcfg File ............................................................................................ 18

To Create a sysidcfg Conguration File ................................................................................. 19

Syntax Rules or the sysidcfg File ............................................................................................. 21

sysidcfg File Keywords .............................................................................................................. 22SPARC: Preconguring Power Management Inormation ............................................................ 36

3 Preconfguring With a Naming Serviceor DHCP ............................................................................ 37

Choosing a Naming Service ............................................................................................................... 37

Preconguring With the Naming Service ........................................................................................ 39

To Precongure the Locale Using NIS ...................................................................................... 40

To Precongure the Locale Using NIS+ .................................................................................... 42

Preconguring System Conguration Inormation With the DHCP Service (Tasks) ............... 43

Creating DHCP Options and Macros or Solaris Installation Parameters ............................ 44

3


4/278

Part II Installing Over a Local AreaNetwork .............................................................................................. 55

4 Installing From theNetwork(Overview) .........................................................................................57

Network Installation Introduction .................................................................................................... 57

Required Servers or Network Installation ............................................................................... 57

x86: Overview o Booting and Installing Over the Network With PXE ........................................ 59

x86: What is PXE? ....................................................................................................................... . 60

x86: Guidelines or Booting With PXE ...................................................................................... 60

5 Installing From theNetworkWith DVDMedia (Tasks) .................................................................. 61

Task Map: Installing From the Network With DVD Media ........................................................... 62

Creating an Install Server With DVD Media ................................................................................... 64

To Create an Install Server With SPARC or x86 DVD Media ................................................. 64

Creating a Boot Server on a Subnet With a DVD Image ................................................................. 67

To Create a Boot Server on a Subnet With a DVD Image ....................................................... 68

Adding Systems to Be Installed From the Network With a DVD Image ...................................... 69

To Add Systems to Be Installed From the Network With add_install_client (DVD) ... 70

Installing the System From the Network With a DVD Image ........................................................ 74

SPARC: To Install the Client Over the Network (DVD) ......................................................... 75

x86: To Install the Client Over the Network With GRUB (DVD) ......................................... 77

6 Installing From theNetworkWith CD Media (Tasks) ..................................................................... 83

Task Map: Installing From the Network With CD Media .............................................................. 84

Creating an Install Server With SPARC or x86 CD Media ............................................................. 86

SPARC: To Create an Install Server With SPARC or x86 CD Media ..................................... 86

Creating a Boot Server on a Subnet With a CD Image .................................................................... 90

To Create a Boot Server on a Subnet With a CD Image .......................................................... 91

Adding Systems to Be Installed From the Network With a CD Image ......................................... 92

To Add Systems to Be Installed From the Network With add_install_client (CDs) ..... 93

Installing the System From the Network With a CD Image ........................................................... 97

SPARC: To Install the Client Over the Network (CDs) ........................................................... 97

x86: To Install the Client Over the Network With GRUB (CDs) ......................................... 100

Contents

Solaris 10 10/09Installation Guide: Network-BasedInstallations October 20094


5/278

7 Patching theMinirootImage(Tasks) .............................................................................................107

Patching the Miniroot Image (Tasks) ............................................................................................. 107

About the Miniroot Image (Overview) ................................................................................... 107How To Patch the Miniroot Image .......................................................................................... 108

Patching the Miniroot Image (Example) ........................................................................................ 109

Patching the Miniroot Image .................................................................................................... 109

8 Installing Over the Network (Examples) .......................................................................................113

Network Installation Over the Same Subnet (Examples) ............................................................. 114

9 Installing From theNetwork(Command Reerence) ................................................................... 123

Network Installation Commands .................................................................................................... 123

x86: GRUB Menu Commands or Installation .............................................................................. 124

Part III InstallingOver a Wide AreaNetwork............................................................................................. 129

10 WAN Boot (Overview) .......................................................................................................................131

What Is WAN Boot? .......................................................................................................................... 131

When to Use WAN Boot .................................................................................................................. 132

How WAN Boot Works (Overview) ............................................................................................... 133

Sequence o Events in a WAN Boot Installation .................................................................... 133Protecting Data During a WAN Boot Installation ................................................................. 135

Security Congurations Supported by WAN Boot (Overview) .................................................. 137

Secure WAN Boot Installation Conguration ....................................................................... 137

Insecure WAN Boot Installation Conguration .................................................................... 138

11 Preparing to Install WithWAN Boot (Planning) ........................................................................... 139WAN Boot Requirements and Guidelines ..................................................................................... 139

Web Server Sotware Requirements and Guidelines ............................................................. 141

Server Conguration Options .................................................................................................. 141

Storing Installation and Conguration Files in the Document Root Directory ................. 142

Storing Conguration and Security Inormation in the /etc/netboot Hierarchy ........... 144

Storing thewanboot-cgi

Program .......................................................................................... 147Digital Certicate Requirements ............................................................................................. 147

Contents

5


6/278

WAN Boot Security Limitations ..................................................................................................... 148

Gathering Inormation or WAN Boot Installations .................................................................... 148

12 Installing WithWAN Boot (Tasks) ....................................................................................................151

Installing Over a Wide Area Network (Task Maps) ...................................................................... 151

Conguring the WAN Boot Server ................................................................................................. 155

Creating the Document Root Directory .................................................................................. 155

Creating the WAN Boot Miniroot ........................................................................................... 156

Veriying WAN Boot Support on the Client .......................................................................... 158Installing the wanboot Program on the WAN Boot Server ................................................... 160

Creating the /etc/netboot Hierarchy on the WAN Boot Server ....................................... 162

Copying the WAN Boot CGI Program to the WAN Boot Server ........................................ 165

(Optional) To Congure the WAN Boot Logging Server ..................................................... 166

(Optional) Protecting Data by Using HTTPS ................................................................................ 167

(Optional) To Use Digital Certicates or Server and Client Authentication .................... 168

(Optional) To Create a Hashing Key and an Encryption Key ............................................... 170

Creating the Custom JumpStart Installation Files ......................................................................... 173

To Create the Solaris Flash Archive ......................................................................................... 173

To Create the sysidcfg File ...................................................................................................... 175

To Create the Prole .................................................................................................................. 176

To Create the rules File ............................................................................................................ 178

(Optional) Creating Begin and Finish Scripts ........................................................................ 180Creating the Conguration Files ..................................................................................................... 181

To Create the System Conguration File ................................................................................ 181

To Create the wanboot.conf File ............................................................................................. 183

(Optional) Providing Conguration Inormation With a DHCP Server ................................... 187

13 SPARC: Installing WithWAN Boot (Tasks) ...................................................................................... 189Task Map: Installing a Client With WAN Boot ............................................................................. 189

Preparing the Client or a WAN Boot Installation ........................................................................ 190

To Check the net Device Alias in the Client OBP .................................................................. 190

Installing Keys on the Client ..................................................................................................... 192

Installing the Client .......................................................................................................................... . 197

To Perorm a Noninteractive WAN Boot Installation .......................................................... 198

To Perorm an Interactive WAN Boot Installation ............................................................... 200

Contents



7/278

To Perorm a WAN Boot Installation With a DHCP Server ................................................ 204

To Perorm a WAN Boot Installation With Local CD Media .............................................. 206

14 SPARC: Installing WithWAN Boot (Examples) .............................................................................. 211

Sample Site Setup ............................................................................................................................... 212

Create the Document Root Directory ............................................................................................. 213

Create the WAN Boot Miniroot ...................................................................................................... 213

Check the Client OBP or WAN Boot Support ...................................................................... 213

Install the wanboot Program on the WAN Boot Server ................................................................ 214

Create the /etc/netboot Hierarchy ............................................................................................... 214

Copy the wanboot-cgi Program to the WAN Boot Server .......................................................... 215

(Optional) Congure the WAN Boot Server as a Logging Server ............................................... 215

Congure the WAN Boot Server to Use HTTPS ........................................................................... 215

Provide the Trusted Certicate to the Client ................................................................................. 215

(Optional) Use Private Key and Certicate or Client Authentication ....................................... 216Create the Keys or the Server and the Client ................................................................................. 217

Create the Solaris Flash Archive ...................................................................................................... 217

Create the sysidcfg File ................................................................................................................... 218

Create the Client's Prole ................................................................................................................. 218

Create and Validate the rules File .................................................................................................. 219

Create the System Conguration File ............................................................................................. 219Create the wanboot.conf File .......................................................................................................... 220

Check the net Device Alias in OBP ................................................................................................. 221

Install Keys on the Client .................................................................................................................. 222

Install the Client .................................................................................................................... ............. 223

15 WAN Boot (Reerence) ......................................................................................................................225WAN Boot Installation Commands ............................................................................................... 225

OBP Commands ..................................................................................................................... ........... 228

System Conguration File Settings and Syntax ............................................................................. 229

wanboot.conf File Parameters and Syntax .................................................................................... 229

Contents

7


8/278

Part IV Appendixes .........................................................................................................................................233

A Troubleshooting (Tasks) ...................................................................................................................235

Problems With Setting Up Network Installations ......................................................................... 235

Problems With Booting a System .................................................................................................... 236

Booting From Media, Error Messages ..................................................................................... 236

Booting From Media, General Problems ................................................................................ 237

Booting From the Network, Error Messages .......................................................................... 238

Booting From the Network, General Problems ...................................................................... 241Initial Installation o the Solaris OS ................................................................................................. 241

x86: To Check IDE Disk or Bad Blocks .................................................................................. 242

Upgrading the Solaris OS ................................................................................................................. 244

Upgrading, Error Messages ...................................................................................................... 244

Upgrading, General Problems .................................................................................................. 245

To Continue Upgrading Ater a Failed Upgrade ................................................................... 247

x86: Problems With Solaris Live Upgrade When You Use GRUB ....................................... 247

System Panics When Upgrading With Solaris Live Upgrade Running Veritas VxVm ..... 249

x86: Service Partition Not Created by Deault on Systems With No Existing ServicePartition ..................................................................................................................................... . 251

To Install Sotware From a Network Installation Image or From the Solaris DVD ........... 251

To Install From the Solaris Sotware - 1 CD or From a Network Installation Image ......... 252

B Installing or Upgrading Remotely(Tasks) .....................................................................................253

SPARC: Using the Solaris Installation Program to Install or Upgrade From a RemoteDVD-ROM or CD-ROM .................................................................................................................. 253

SPARC: To Install or Upgrade From a Remote DVD-ROM and CD-ROM ....................... 253

Glossary .............................................................................................................................................. 257

Index ................................................................................................................................................... 269

Contents



9/278

Preace

This book describes how to install the SolarisTM Operating System (Solaris OS) remotely over a

local area network or a wide area network.

This book does not include instructions about how to set up system hardware or otherperipherals.

Note This Solaris release supports systems that use the SPARC and x86 amilies o processorarchitectures: UltraSPARC, SPARC64, AMD64, Pentium, and Xeon EM64T. The supportedsystems appear in the Solaris OS: Hardware Compatibility Lists at http://www.sun.com/bigadmin/hcl. This document cites any implementation diferences between the platormtypes.

In this document these x86 related terms mean the ollowing:

x86 reers to the larger amily o 64-bit and 32-bit x86 compatible products.

x64 points out specic 64-bit inormation about AMD64 or EM64T systems.

32-bit x86 points out specic 32-bit inormation about x86 based systems.

For supported systems, see the Solaris OS: Hardware Compatibility Lists.

Who Should UseThis BookThis book is intended or system administrators who are responsible or installing the Solaris

sotware. This book provides advanced Solaris installation inormation or enterprise systemadministrators who manage multiple Solaris machines in a networked environment.

For basic installation inormation, see Solaris 10 10/09 Installation Guide: Basic Installations.

9
http://www.sun.com/bigadmin/hclhttp://www.sun.com/bigadmin/hclhttp://docs.sun.com/doc/821-0440http://docs.sun.com/doc/821-0440http://www.sun.com/bigadmin/hclhttp://www.sun.com/bigadmin/hcl


10/278

Related BooksTable P1 lists documentation or system administrators.

TABLE P1 Are You a System Administrator Who is Installing Solaris?

Description Inormation

Do you need system requirements or high-level planning inormation?Or want a high-level overview o Solaris ZFSTM installations, booting,Solaris Zones partitioning technology, or creating RAID-1 volumes?

Solaris 10 10/09 Installation Guide: Planning or Installation

and Upgrade

Do you need to install a single system rom DVD or CDmedia? TheSolaris installation program steps you through an installation.

Solaris 10 10/09 Installation Guide: Basic Installations

Do you need to upgrade or patch your system with almost nodowntime? Save system downtime when upgrading by using SolarisLive Upgrade.

Solaris 10 10/09 Installation Guide: Solaris Live Upgrade andUpgrade Planning

Do you need to install a secure installation over the network or Internet?Use WAN boot to installa remote client. Or, do you need to install overthe network rom a network installation image? The Solaris installation

program steps you through an installation.

Solaris 10 10/09 Installation Guide: Network-Based

Installations

Do you need to install or patch multiple systems quickly? Use SolarisFlashTM sotware to create a Solaris Flash archive and install a copy othe OS on clone systems.

Solaris 10 10/09 Installation Guide: Solaris Flash Archives(Creationand Installation)

Do you need to back up your system? Chapter 23, Backing Up and Restoring UFSFile Systems(Overview), in System Administration Guide: Devices andFile Systems

Do you need troubleshooting inormation, a list o known problems, ora list o patches or this release?

Solaris Release Notes

Do youneed to veriy t hat your system works on Solaris? SPARC: Solaris Sun Hardware Platorm Guide

Do you need to checkon which packages have been added, removed, orchanged in this release?

Solaris Package List

Do you need to veriy that your system and devices work with SolarisSPARC and x86 based systems and other third-party vendors.

Solaris Hardware Compatibility List or x86 Platorms

Documentation, Support, andTrainingThe Sun web site provides inormation about the ollowing additional resources:

Documentation (http://www.sun.com/documentation/)

Support (http://www.sun.com/support/) Training (http://www.sun.com/training/)

Preace

http://docs.sun.com/doc/821-0441http://docs.sun.com/doc/821-0441http://docs.sun.com/doc/821-0440http://docs.sun.com/doc/821-0438http://docs.sun.com/doc/821-0438http://docs.sun.com/doc/821-0439http://docs.sun.com/doc/821-0439http://docs.sun.com/doc/821-0436http://docs.sun.com/doc/821-0436http://docs.sun.com/doc/817-5093http://docs.sun.com/doc/817-5093http://docs.sun.com/doc/817-5093http://docs.sun.com/doc/817-5093http://www.sun.com/bigadmin/hclhttp://www.sun.com/documentation/http://www.sun.com/documentation/http://www.sun.com/documentation/http://www.sun.com/support/http://www.sun.com/support/http://www.sun.com/support/http://www.sun.com/training/http://www.sun.com/training/http://www.sun.com/training/http://www.sun.com/training/http://www.sun.com/support/http://www.sun.com/documentation/http://www.sun.com/bigadmin/hclhttp://docs.sun.com/doc/817-5093http://docs.sun.com/doc/817-5093http://docs.sun.com/doc/817-5093http://docs.sun.com/doc/821-0436http://docs.sun.com/doc/821-0436http://docs.sun.com/doc/821-0439http://docs.sun.com/doc/821-0439http://docs.sun.com/doc/821-0438http://docs.sun.com/doc/821-0438http://docs.sun.com/doc/821-0440http://docs.sun.com/doc/821-0441http://docs.sun.com/doc/821-0441


11/278

Sun Welcomes Your CommentsSun is interested in improving its documentation and welcomes your comments andsuggestions. To share your comments, go to http://docs.sun.com and click Feedback.

Typographic ConventionsThe ollowing table describes the typographic conventions that are used in this book.

TABLE P2 TypographicConventions

Typeace Meaning Example

AaBbCc123 The names o commands, les, and directories,and onscreen computer output

Edit your .login le.

Use ls -a to list all les.

machine_name% you have mail.

AaBbCc123 What you type, contrasted with onscreencomputer output

machine_name% su

Password:

aabbcc123 Placeholder:replacewith a realname orvalue The command toremove a le is rmflename.

AaBbCc123 Book titles,new terms, and terms to beemphasized

Read Chapter 6 in the User's Guide.

A cache isa copythat isstoredlocally.

Do notsave the le.

Note: Some emphasized itemsappear boldonline.

Shell Prompts in Command ExamplesThe ollowing table shows the deault UNIX system prompt and superuser prompt or the Cshell, Bourne shell, and Korn shell.

TABLE P3 ShellPrompts

Shell Prompt

C shell machine_name%

C shell or superuser machine_name#

Preace

11
http://docs.sun.com/http://docs.sun.com/


12/278

TABLE P3 ShellPrompts (Continued)Shell Prompt

Bourne shell and Korn shell$

Bourne shell and Korn shell or superuser #

Preace



13/278

Planning to Install Over the Network

This part describes how to plan your installation over the network.

P A R T I

13


14/278

14


15/278

Where to Find Solaris Installation PlanningInormation

This book describes how to install the Solaris OS remotely over a local area network or a widearea network.

This chapter describes the preparations or completing a successul installation. Manypreparatory tasks are common to all Solaris installations, and so are described in one master

planning document.

Where to Find Planning and System Requirement Inormation

The Solaris 10 10/09 Installation Guide: Planning or Installation and Upgrade provides systemrequirements and high-level planning inormation, such as planning guidelines or le systems,and upgrade planning and much more. The ollowing list describes the chapters in the planningbook.

Chapter Descriptions From the Planning Guide Reerence

This chapter describes new eatures in the Solaris installation programs. Chapter 2, Whats New in Solaris Installation, inSolaris 10 10/09 Installation Guide: Planning or

Installation and Upgrade

This chapter provides you with inormation about decisions you needto makebeore you install or upgrade the Solaris OS. For example, you'll nd inormationon deciding when to use a network installation imageor DVD media anddescriptions o all the Solaris installation programs.

Chapter 3, Solaris Installation and Upgrade(Roadmap), in Solaris 10 10/09 Installation Guide:Planning or Installation and Upgrade

This chapter describes systemrequirements to install or upgrade to the SolarisOS. General guidelines or planning the disk space and deault swap spaceallocation are also provided. Upgrade limitations are also described.

Chapter 4, System Requirements, Guidelines, andUpgrade (Planning), in Solaris 10 10/09Installation Guide: Planning or Installationand

Upgrade

1C H A P T E R 1

15
http://docs.sun.com/doc/821-0441http://docs.sun.com/doc/821-0441/gaufd?a=viewhttp://docs.sun.com/doc/821-0441/gaufd?a=viewhttp://docs.sun.com/doc/821-0441/gaufd?a=viewhttp://docs.sun.com/doc/821-0441/planning-8?a=viewhttp://docs.sun.com/doc/821-0441/planning-8?a=viewhttp://docs.sun.com/doc/821-0441/planning-8?a=viewhttp://docs.sun.com/doc/821-0441/planning-8?a=viewhttp://docs.sun.com/doc/821-0441/diskspace-1?a=viewhttp://docs.sun.com/doc/821-0441/diskspace-1?a=viewhttp://docs.sun.com/doc/821-0441/diskspace-1?a=viewhttp://docs.sun.com/doc/821-0441/diskspace-1?a=viewhttp://docs.sun.com/doc/821-0441/diskspace-1?a=viewhttp://docs.sun.com/doc/821-0441/diskspace-1?a=viewhttp://docs.sun.com/doc/821-0441/diskspace-1?a=viewhttp://docs.sun.com/doc/821-0441/diskspace-1?a=viewhttp://docs.sun.com/doc/821-0441/diskspace-1?a=viewhttp://docs.sun.com/doc/821-0441/planning-8?a=viewhttp://docs.sun.com/doc/821-0441/planning-8?a=viewhttp://docs.sun.com/doc/821-0441/planning-8?a=viewhttp://docs.sun.com/doc/821-0441/gaufd?a=viewhttp://docs.sun.com/doc/821-0441/gaufd?a=viewhttp://docs.sun.com/doc/821-0441/gaufd?a=viewhttp://docs.sun.com/doc/821-0441


16/278

Chapter Descriptions From the Planning Guide Reerence

This chapter contains checklists to help you gather all o the inormation that you

need to install or upgrade your system. This is useul i you are doing aninteractive installation. You'll have all the inormation in the checklist that you'llneed to do an interactive installation.

Chapter 5, Gathering Inormation Beore

Installation or Upgrade (Planning), inSolaris 10 10/09 Installation Guide: Planning orInstallation and Upgrade

This book part includes chapters that provide overviews o several technologiesthat relate to a Solaris OS installation or upgrade. Guidelines and requirementsrelated to these technologies are also included. These chapters includeinormation about ZFS installations, booting, Solaris Zones partitioningtechnology, and RAID-1 volumes that can be created at installation.

Part II, Understanding Installations That Relateto ZFS, Booting, Solaris Zones, and RAID-1Volumes, in Solaris 10 10/09 Installation Guide:Planning or Installation and Upgrade

Whereto FindPlanning and System Requirement Inormation

http://docs.sun.com/doc/821-0441/gatherinfo-1?a=viewhttp://docs.sun.com/doc/821-0441/gatherinfo-1?a=viewhttp://docs.sun.com/doc/821-0441/gatherinfo-1?a=viewhttp://docs.sun.com/doc/821-0441/gatherinfo-1?a=viewhttp://docs.sun.com/doc/821-0441/epucs?a=viewhttp://docs.sun.com/doc/821-0441/epucs?a=viewhttp://docs.sun.com/doc/821-0441/epucs?a=viewhttp://docs.sun.com/doc/821-0441/epucs?a=viewhttp://docs.sun.com/doc/821-0441/epucs?a=viewhttp://docs.sun.com/doc/821-0441/epucs?a=viewhttp://docs.sun.com/doc/821-0441/epucs?a=viewhttp://docs.sun.com/doc/821-0441/epucs?a=viewhttp://docs.sun.com/doc/821-0441/epucs?a=viewhttp://docs.sun.com/doc/821-0441/gatherinfo-1?a=viewhttp://docs.sun.com/doc/821-0441/gatherinfo-1?a=viewhttp://docs.sun.com/doc/821-0441/gatherinfo-1?a=viewhttp://docs.sun.com/doc/821-0441/gatherinfo-1?a=view


17/278

Preconfguring System ConfgurationInormation (Tasks)

This chapter describes how to precongure system inormation by using the sysidcfg le.Preconguration can help you to avoid being prompted or this inormation when you installthe Solaris OS. This chapter also describes how to precongure Power ManagementTM

inormation. This chapter contains the ollowing sections:

Advantages o Preconguring System Conguration Inormation on page 17 Preconguring With the sysidcfg File on page 18 SPARC: Preconguring Power Management Inormation on page 36

Advantages o Preconfguring System Confguration

InormationThe installation methods require conguration inormation about a system, such as peripheraldevices, host name, Internet Protocol (IP) address, and naming service. Beore the installationtools prompt you or conguration inormation, they check or conguration inormation thatis stored elsewhere.

You can choose one o the ollowing ways to precongure system inormation.

TABLE 21 Preconguration Options

Preconfguration File or Service Description Further Inormation

sysidcfg le Preset the domain name, netmask,DHCP, IPv6 and other parametersby using keywords in the sysidcfgle.

Preconguring With thesysidcfg Fileon page 18

2C H A P T E R 2

17


18/278

TABLE 21 Preconguration Options (Continued)Preconfguration File or Service Description Further Inormation

Naming s ervice Preset host name a nd I P addressesby preconguring your systeminormation in your namingservice.

Preconguring With the NamingService on page 39

DHCP DHCP enables host system in aTCP/IP network to be conguredautomatically or the network asthe system boots. DHCP canmanage IP addresses by leasing

them as needed to clients.

Preconguring SystemCongurationInormation Withthe DHCP Service (Tasks) onpage 43

For more detailed inormation about choosing a preconguration method, see Choosing aNaming Service on page 37.

When the Solaris installation program or the custom JumpStartTM installation program detectsprecongured system inormation, the installation program does not prompt you to enter the

inormation. For example, you have several systems and you do not want a time zone promptevery time you install the current Solaris release on one o the systems. You can speciy the timezone in the sysidcfg le or the naming service databases. When you install the current Solarisrelease, the installation program does not prompt you to type a time zone.

Preconfguring With the sysidcfg File

You can speciy a set o keywords in the sysidcfg le to precongure a system. The keywordsare described in sysidcfg File Keywords on page 22.

Note The name_service keyword in the sysidcfg le automatically sets the naming serviceduring installation o the Solaris OS. This setting overrides SMF services previously set up orsite.xml. Thereore, you might need to reset your name service ater installation.

You must create a unique sysidcfg le or every system that requires diferent congurationinormation. You can use the same sysidcfg le to precongure the time zone on a set osystems i you want all the systems to be assigned the same time zone. However, i you want toprecongure a diferent root (superuser) password or each o those systems, you need to createa unique sysidcfg le or each system.

You can place the sysidcfg le in one o the ollowing.

PreconfguringWith the sysidcfg File



19/278

TABLE 22 sysidcfg Locations

NFS le system I you put the sysidcfg le ina sharedNFSle

system, you must use the -p option o theadd_install_client(1M) command when you setup the system to install rom the network. The -poption species where the system can nd thesysidcfg le when you install the current Solarisrelease.

UFS or PCFS diskette Place the sysidcfg leintheroot(/) directory on thediskette.

I you are perorming a customJumpStart installationandyouwanttousea sysidcfg le on a diskette, youmust place the sysidcfg le on the prole diskette. Tocreate a prole diskette, see Creating a ProleDiskette or Standalone Systems in Solaris 10 10/09Installation Guide: Custom JumpStart and Advanced

Installations.

Youcan place only one sysidcfg le in a directory oron a diskette. I you are creating more than onesysidcfg le, you must place each le in a diferentdirectory or on a diferent diskette.

HTTP or HTTPS server I you want to perorm a W AN boot installation, placethe sysidcfg le in the document root directory othe web server.

You can use the naming service or DHCP to precongure your system. For inormation, see

Chapter 3, Preconguring With a Naming Service or DHCP.

To Create a sysidcfg Confguration File

Create a flecalled sysidcfg in a text editor with thekeywords you want.

Make the sysidcfg fleavailable to clients by using oneo thelocations described at Table 22.

SPARC: sysidcfg File

The ollowing is an example o a sysidcfg le or a SPARC based system. The host name, IPaddress, and netmask o this system have been precongured by editing the naming service.Because all o the system conguration inormation is precongured in this le, you can use acustom JumpStart prole to perorm a custom JumpStart installation. In this example, the

1

2

Example 21


Chapter 2 Preconfguring System Confguration Inormation (Tasks) 19

f
http://docs.sun.com/doc/816-5166http://docs.sun.com/doc/816-5166http://docs.sun.com/doc/821-0437/preparecustom-53074?a=viewhttp://docs.sun.com/doc/821-0437/preparecustom-53074?a=viewhttp://docs.sun.com/doc/821-0437/preparecustom-53074?a=viewhttp://docs.sun.com/doc/821-0437/preparecustom-53074?a=viewhttp://docs.sun.com/doc/821-0437/preparecustom-53074?a=viewhttp://docs.sun.com/doc/821-0437/preparecustom-53074?a=viewhttp://docs.sun.com/doc/821-0437/preparecustom-53074?a=viewhttp://docs.sun.com/doc/821-0437/preparecustom-53074?a=viewhttp://docs.sun.com/doc/821-0437/preparecustom-53074?a=viewhttp://docs.sun.com/doc/821-0437/preparecustom-53074?a=viewhttp://docs.sun.com/doc/816-5166


20/278

NFSv4 domain name is automatically derived rom the naming service. Because theservice_profile keyword is not included in this example, conguration is not altered or thenetwork services during installation.

keyboard=US-English

system_locale=en_US

timezone=US/Central

terminal=sun-cmd

timeserver=localhost

name_service=NIS {domain_name=marquee.central.example.com

name_server=nmsvr2(172.31.112.3)}

nfs4_domain=dynamic

root_password=m4QPOWNY

network_interface=hme0 {hostname=host1

default_route=172.31.88.1

ip_address=172.31.88.210

netmask=255.255.0.0

protocol_ipv6=no}

security_policy=kerberos {default_realm=example.com

admin_server=krbadmin.example.com

kdc=kdc1.example.com,kdc2.example.com}

x86: sysidcfg File

The ollowing sample sysidcfg le is or a group o x86 based systems. In this example, theNFSv4 domain name is specied to be example.com. This custom name overrides the deaultdomain name. Also in this example, the network services are disabled or restricted to localconnections only.

keyboard=US-English

timezone=US/Central

timeserver=timehost1

terminal=ibm-pc

service_profile=limited_net


name_server=nmsvr2(172.25.112.3)}nfs4_domain=example.com

root_password=URFUni9

sysidcfg File or Confguring Multiple Interaces

In the ollowing sample sysidcfg le, conguration inormation is specied or both the eri0and eri1 network interaces. The eri0 interace is congured as the primary network interace,and eri1 is congured as a secondary network interace. In this example, the NFSv4 domainname is automatically derived rom the naming service.

Example 22

Example 23



P f i With th id f Fil


21/278

timezone=US/Pacific

system_locale=C

terminal=xterms

timeserver=localhostnetwork_interface=eri0 {primary

hostname=host1

ip_address=192.168.2.7

netmask=255.255.255.0

protocol_ipv6=no

default_route=192.168.2.1}

network_interface=eri1 {hostname=host1-b

ip_address=192.168.3.8netmask=255.255.255.0

protocol_ipv6=no

default_route=NONE}

root_password=JE2C35JGZi4B2

security_policy=none

name_service=NIS {domain_name=domain.example.com

name_server=nis-server(192.168.2.200)}

nfs4_domain=dynamic

Continuing the Installation

I you plan to use the sysidcfg le in an installation over the network, you need to set up aninstallation server and add the system as an installation client. For more inormation, seeChapter 4, Installing From the Network (Overview).

I you plan to use the sysidcfg le in a WAN boot installation, you need to perorm additional

tasks. For more inormation, see Chapter 10, WAN Boot (Overview).

I you plan to use the sysidcfg le in a custom JumpStart installation, you need to create aprole and a rules.ok le. For more inormation, see Chapter 2, Custom JumpStart(Overview), in Solaris 10 10/09 Installation Guide: Custom JumpStart and AdvancedInstallations.

For more inormation about the sysidcfg le, see the man page sysidcfg(4).

Syntax Rules or the sysidcfg File

You can use two types o keywords in the sysidcfg le: independent and dependent.Dependent keywords are guaranteed to be unique only within independent keywords. Adependent keyword exists only when it is identied with its associated independent keyword.

In this example, name_service is the independent keyword, while domain_name andname_server are the dependent keywords:

More Inormation

See Also



http://docs.sun.com/doc/821-0437/jumpstartoverview-4?a=viewhttp://docs.sun.com/doc/821-0437/jumpstartoverview-4?a=viewhttp://docs.sun.com/doc/821-0437/jumpstartoverview-4?a=viewhttp://docs.sun.com/doc/821-0437/jumpstartoverview-4?a=viewhttp://docs.sun.com/doc/816-5174http://docs.sun.com/doc/816-5174http://docs.sun.com/doc/816-5174http://docs.sun.com/doc/816-5174http://docs.sun.com/doc/821-0437/jumpstartoverview-4?a=viewhttp://docs.sun.com/doc/821-0437/jumpstartoverview-4?a=viewhttp://docs.sun.com/doc/821-0437/jumpstartoverview-4?a=view


22/278


name_server=connor(192.168.112.3)}

Syntax Rule Example

Independent keywords can be listed in any order. pointer=MS-Sdisplay=ati {size=15-inch}

Keywords are not case sensitive. TIMEZONE=US/Centralterminal=sun-cmd

Enclose all dependent keywords in curly braces ({}) to tie

them to their associated independent keyword.

name_service=NIS

{domain_name=marquee.central.example.comname_server=connor(192.168.112.3)}

You can optionally enclosedvalues in single () or doublequotes ().

network_interface=none

Forall keywords except the network_interfacekeyword, only one instance o a keyword is valid.However, i you speciy the keyword more than once,only the rst instance o the keyword is used.

name_service=NIS

name_service=DNS

sysidcfg File Keywords

Table 23 lists the keywords you can use to congure system inormation in the sysidcfg le.

TABLE 23 Keywordsto Usein sysidcfg

Confguration Inormation Keyword

Keyboard layout and language keyboard Keyword on page 23

Naming service, domain name, name server name_service Keywordon page 24

Network interace, host name, Internet Protocol (IP) address,netmask, DHCP, IPv6

network_interface Keyword on page 27

Domain name denition or NFSv4 nfs4_domain Keyword on page 32

Root password root_password Keywordon page 33

Security policy security_policy Keywordon page 33

Network security prole service_profile Keywordon page 34

Language in which to display the install program and desktop system_locale Keywordon page 35

Terminal type terminal Keyword on page 35

Time zone timezone Keyword on page 35





23/278

TABLE 23 Keywords to Usein sysidcfg (Continued)Confguration Inormation Keyword

Date and time timeserver Keywordon page 35

The ollowing sections describe the keywords that you can use in the sysidcfg le.

keyboard Keyword

The sysidkdb tool congures your USB language and its corresponding keyboard layout.

The ollowing procedure occurs: I the keyboard is sel-identiying, the keyboard language and layout automatically

congures during installation.

I the keyboard is not sel-identiying, the sysidkdb tool provides you with a list osupported keyboard layouts during installation, so that you can select a layout or keyboardconguration.

Note PS/2 keyboards are not sel-identiying. You will be asked to select the keyboardlayout during the installation.

You can congure the keyboard language and its corresponding keyboard layout inormationby using the keyboard keyword. Each language has its own keyboard layout. Use the ollowingsyntax to select a language and its corresponding layout.

keyboard=keyboard_layout

For example, this entry sets the keyboard language and its corresponding keyboard layout orthe German language:

keyboard=German

The value provided or keyboard_layoutmust be a valid value. Otherwise, an interactiveresponse is required during installation. The valid keyboard_layoutstrings are dened in the

/usr/share/lib/keytables/type_6/kbd_layouts le.

SPARC only Previously, the USBkeyboard assumed a sel-identiying value o 1 during theinstallation. Thereore, all o the keyboards that were not sel-identiying always congured ora U.S. English keyboard layout during installation.

I the keyboard is not sel-identiying and you want to prevent being prompted during yourJumpStart installation, select the keyboard language in your sysidcfg le. For JumpStart





24/278

installations, the deault is or the U.S. English language. To select another language and itscorresponding keyboard layout, set the keyboard entry in your sysidcfg le as in the exampleprovided above.

For urther inormation, see the sysidcfg(4) and sysidtool(1M) man pages.

name_service Keyword

You can use the name_service keyword to congure the naming service, the domain name, andthe name server or the system. The ollowing sample shows the general syntax or thename_service keyword.

name_service=name-service {domain_name=domain-namename_server=name-serveroptional-keyword=value}

Choose only one value or name_service. Includeall or none o the domain_name,name_server, or optional keywords, as needed. I no keywords are used, omit the curly braces{}.

Note The name_service option in the sysidcfg le automatically sets the naming serviceduring installation o the Solaris OS. This setting overrides SMF services that were previouslyset up or site.xml. Thereore, you might need to reset your name service ater installation.

The ollowing sections describe the keyword syntax to congure the system to use a specicnaming service.

NIS Syntax or name_service KeywordUse the ollowing syntax to congure the system to use the NIS naming service.

name_service=NIS {domain_name=domain-namename_server=hostname(ip-address)}

domain-name Species the domain name

hostname Species the host name o the name server

ip-address Species the IP address o the name server

EXAMPLE 24 Speciying a NISServerWith the name_service Keyword

The ollowing example species a NIS server with the domain name west.example.com.Theserver's host name is timber, and the server IP address is 192.168.2.1.

name_service=NIS {domain_name=west.example.com

name_server=timber(192.168.2.1)}

g g y g




25/278

For more inormation about the NIS name service, see System Administration Guide: Namingand Directory Services (DNS, NIS, and LDAP).

NIS+ Syntax or name_service Keyword

Use the ollowing syntax to congure the system to use the NIS name service.

name_service=NIS+ {domain_name=domain-namename_server=hostname(ip-address)}

domain-name Species the domain name

hostname Species the host name o the name serverip-address Species the IP address o the name server

EXAMPLE 25 Speciying a NIS+ Server With the name_service Keyword

The ollowing example species a NIS+ server with the domain name west.example.com.Theserver's host name is timber, and the server IP address is 192.168.2.1.

name_service=NIS+ {domain_name=west.example.comname_server=timber(192.168.2.1)}

For more inormation about the NIS+ name service, see System Administration Guide: Namingand Directory Services (NIS+).

DNS Syntax or name_service Keyword

Use the ollowing syntax to congure the system to use DNS.

name_service=DNS {domain_name=domain-namename_server=ip-address,ip-address,ip-address

search=domain-name,domain-name,domain-name,domain-name,domain-name,domain-name}

domain_name=domain-name Species the domain name.

name_server=ip-address Species the IP address o the DNS server. You can speciyup to three IP addresses as values or the name_serverkeyword.

search=domain-name (Optional) Species additional domains to search ornaming service inormation. You can speciy up to sixdomain names to search. The total length o each searchentry cannot exceed 250 characters.


http://docs.sun.com/doc/816-4556http://docs.sun.com/doc/816-4556http://docs.sun.com/doc/816-4558http://docs.sun.com/doc/816-4558http://docs.sun.com/doc/816-4558http://docs.sun.com/doc/816-4558http://docs.sun.com/doc/816-4558http://docs.sun.com/doc/816-4556http://docs.sun.com/doc/816-4556


26/278

EXAMPLE 26 Speciying a DNSServerWith the name_service Keyword

The ollowing example species a DNS server with the domain name west.example.com.Theserver IP addresses are 10.0.1.10 and 10.0.1.20. example.com and east.example.com are listedas additional domains to search or naming service inormation.

name_service=DNS {domain_name=west.example.com

name_server=10.0.1.10,10.0.1.20

search=example.com,east.example.com}

For more inormation about the DNS name service, see System Administration Guide: Naming

and Directory Services (DNS, NIS, and LDAP).

LDAP Syntax or name_service Keyword

Use the ollowing syntax to congure the system to use LDAP.

name_service=LDAP {domain_name=domain_name

profile=profle_name profile_server=ip_address

proxy_dn="proxy_bind_dn" proxy_password=password}

domain_name Species the domain name o the LDAP server.

profle_name Species the name o the LDAP prole you want to use to congure thesystem.

ip_address Species the IP address o the LDAP prole server.

proxy_bind_dn (Optional) Species the proxy bind distinguished name. You must enclose

theproxy_bind_dnvalue in double quotes.password (Optional) Species the client proxy password.

EXAMPLE 27 Speciying an LDAP Server With the name_service Keyword

The ollowing example species an LDAP server with the ollowing conguration inormation.

The domain name is west.example.com.

The installation program uses the LDAP prole that is named default to congure thesystem.

The IP address o the LDAP server is 172.31.2.1.

The proxy bind distinguished name includes the ollowing inormation.

The common name or the entry is proxyagent. The organizational unit is profile. The proxy domain includes the west, example,and com domain components.

The proxy password is password.


http://docs.sun.com/doc/816-4556http://docs.sun.com/doc/816-4556http://docs.sun.com/doc/816-4556http://docs.sun.com/doc/816-4556http://docs.sun.com/doc/816-4556


27/278

EXAMPLE 27 Speciying an LDAP Server With the name_service Keyword (Continued)

name_service=LDAP {domain_name=west.example.com

profile=defaultprofile_server=172.31.2.1

proxy_dn="cn=proxyagent,ou=profile,

dc=west,dc=example,dc=com"

proxy_password=password}

For more inormation about how to use LDAP, see System Administration Guide: Naming andDirectory Services (DNS, NIS, and LDAP).

network_interface Keyword

Use the network_interface keyword to perorm the ollowing tasks.

Speciy a host name Speciy an IP address Speciy the deault router address Speciy a netmask value Use DHCP to congure the network interace Enable IPv6 on the network interace

The ollowing sections describe how to use the network_interface keyword to congure thesystem interaces.

Syntax or Nonnetworked Systems

To turn of networking or the system, set the network_interfacevalue to none. For example:

network_interface=none

Syntax or Confguring a Single Interace

You can use the network_interface keyword to congure a single interace in the ollowingways.

With DHCP You can use a DHCP server on your network to congure the networkinterace. For more inormation on how to use a DHCP server during your installation, seePreconguring System Conguration Inormation With the DHCP Service (Tasks) onpage 43.

To use the DHCP server to congure a single interace on the system, use the ollowingsyntax or the network_interface keyword.


http://docs.sun.com/doc/816-4556http://docs.sun.com/doc/816-4556http://docs.sun.com/doc/816-4556http://docs.sun.com/doc/816-4556


28/278

network_interface=PRIMARY or value

{dhcp protocol_ipv6=yes-or-no}

PRIMARY Instructs the installation program to congure the rst up,

non-loopback interace that is ound on the system. Theorder is the same as the order that is displayed with theifconfig command. I no interaces are up, then the rstnon-loopback interace is used. I no non-loopbackinteraces are ound, then the system is nonnetworked.

value Instructs the installation program to congure a specicinterace, such as hme0 or eri1.

protocol_ipv6=yes-or-no Instructs the installation program to congure the system touse either IPv6 or to not use IPv6.

For WAN boot installations, you must set the value oprotocol_ipv6=no.

Without DHCP I you do not want to use DHCP to congure the network interace, youcan speciy the conguration inormation in the sysidcfg le. To instruct the installationprogram to congure a single interace on the system without using DHCP, use theollowing syntax.

network_interface=PRIMARY or value

{hostname=host_name

default_route=ip_address

ip_address=ip_address

netmask=netmask

protocol_ipv6=yes_or_no}

PRIMARY Instructs the installation program to congure therst up, non-loopback interace that is ound on thesystem. The order is the same as the order that isdisplayed with the ifconfig command. I nointeraces are up, then the rst non-loopbackinterace is used. I no non-loopback interaces areound, then the system is not networked.

Note Donotusethe PRIMARY keyword value i youwant to congure multiple interaces.

value Instructs the installation program to congure aspecic interace, such as hme0 or eri1.

hostname=host_name (Optional) Species the host name o the system.




29/278

default_route=ip_address or NONE (Optional) Species the IP address o the deaultrouter. I you want the installation program todetect the router by using the ICMP router

discovery protocol, omit this keyword.

Note I theinstallationprogram cannot detect therouter, you are prompted or the routerinormation during the installation.

ip_address=ip_address (Optional) Species the IP address o the system.

netmask=netmask (Optional) Species the netmask value or thesystem.

protocol_ipv6=yes_or_no (Optional) Instructs the installation program tocongure the system to either use IPv6 or to not useIPv6.

Note To perorm an unattended custom JumpStartinstallation, you must speciy a value or theprotocol_ipv6 keyword.

For WAN boot installations, you must set the valueoprotocol_ipv6=no.

Include any combination or none o thehostname

,ip_address

, andnetmask

keywords, asneeded. I you do not use any o these keywords, omit the curly braces ({}).

EXAMPLE 28 Conguring a Single Interace By Using DHCP With the network_interface Keyword

The ollowing example instructs the installation program to use DHCP to congure the eri0network interace. IPv6 support is not enabled.

network_interface=eri0 {dhcp protocol_ipv6=no}

EXAMPLE 29 Conguring a Single Interace By Speciying Conguration Inormation With thenetwork_interface Keyword

The ollowing example congures the interace eri0 with the ollowing settings.

The host name is set to host1. The IP address is set to 172.31.88.100.

The netmask is set to 255.255.255.0.




30/278

EXAMPLE 29 Conguring a Single Interace By Speciying Conguration Inormation With thenetwork_interface Keyword (Continued)

IPv6 support is not enabled on the interace.

network_interface=eri0 {hostname=host1 ip_address=172.31.88.100

netmask=255.255.255.0 protocol_ipv6=no}

Syntax or Confguring Multiple Interaces

You can congure multiple network interaces in your sysidcfg le. For each interace that you

want to congure, include a network_interface entry in the sysidcfg le.You can use the network_interface keyword to congure multiple interaces in the ollowingways.

With DHCP You can use a DHCP server on your network to congure a networkinterace. For more inormation on how to use a DHCP server during your installation, seePreconguring System Conguration Inormation With the DHCP Service (Tasks) onpage 43.

To use the DHCP server to congure a network interace on the system, use the ollowingsyntax or the network_interface keyword.

network_interface=value {primarydhcp protocol_ipv6=yes-or-no}

value Instructs the installation program to congure a specicinterace, such as hme0 or eri1.

primary (Optional) Species value as the primary interace.

protocol_ipv6=yes-or-no Instructs the installation program to congure the system toeither use IPv6 or to not use IPv6.

Note For WAN boot installations, you must set the value oprotocol_ipv6=no.

Without DHCP I you do not want to use DHCP to congure the network interace, youcan speciy the conguration inormation in the sysidcfg le. To instruct the installationprogram to congure multiple interaces without using DHCP, use the ollowing syntax.

network_interface=value {primary hostname=host_namedefault_route=ip_address or NONEip_address=ip_address

netmask=netmask




31/278

protocol_ipv6=yes_or_no}

value Instructs the installation program to congure aspecic interace, such as hme0 or eri1.

primary (Optional) Species value as the primaryinterace.

hostname=host_name (Optional) Species the host name o the system.

default_route=ip_address or NONE (Optional) Species the IP address o the deaultrouter. I you want the installation program todetect the router by using the ICMP router

discovery protocol, omit this keyword.

I you congure multiple interaces in thesysidcfg le, set default_route=NONE or eachsecondary interace that does not use a staticdeault route.

Note I the installation program cannot detectthe router, you are prompted or the routerinormation during the installation.

ip_address=ip_address (Optional) Species the IP address o the system.

netmask=netmask (Optional) Species the netmask value or thesystem.

protocol_ipv6=yes_or_no (Optional) Instructs the installation program tocongure the system to either use IPv6 or to notuse IPv6.

Note To perorm an unattended customJumpStart installation, you must speciy a valueor the protocol_ipv6 keyword.

For WAN boot installations, you must set thevalue oprotocol_ipv6=no.

Include any combination or none o the hostname, ip_address, and netmask keywords, asneeded. I you do not use any o these keywords, omit the curly braces ({}).

In the same sysidcfg le, you can use DHCP to congure certain interaces, while also

speciying the conguration inormation or other interaces in the sysidcfg le.




32/278

EXAMPLE 210 Conguring Multiple Interaces With the network_interface Keyword

In the ollowing example, the network interaces eri0 and eri1 are congured in the ollowingway.

eri0 is congured by using the DHCP server. IPv6 support is not enabled on eri0.

eri1 is the primary network interace. The host name is set to host1, and the IP address is setto 172.31.88.100. The netmask is set to 255.255.255.0. IPv6 support is not enabled on eri1.

network_interface=eri0 {dhcp protocol_ipv6=no}

network_interface=eri1 {primary hostname=host1

ip_address=172.146.88.100

netmask=255.255.255.0protocol_ipv6=no}

nfs4_domain Keyword

To prevent being asked to speciy an NFSv4 domain name during installation, use thenfs4_domain keyword in the sysidcfg le. This keyword suppresses selection o a domainname during the installation process. Use the ollowing syntax:

nfs4_domain=dynamic or custom_domain_name

dynamic This reserved keyword dynamically derives the NFSv4 domainname, based on naming services conguration. For example:

nfs4_domain=dynamic

This example enables the domain name to be derived by the naming

service.

The reserved keyword, dynamic, is not case sensitive.

Note By deault, NFSv4 uses a domain name that is automaticallyderived rom the system's naming services. This domain name issucient or most congurations. In a ew cases, mount points that

cross domain boundaries can cause les to appear to be owned bynobody because no common domain name exists. To prevent thissituation, you can override the deault domain name and select acustom domain name.

custom_domain_name This value overrides the deault domain name.

This value must be a valid custom domain name. A valid domain

name is composed o a combination o alphanumeric characters,




33/278

dots, underscores, and dashes only. The rst character must be analphabetical character. For example:

nfs4_domain=example.com

This example sets the value that is used by the nfsmapid daemon tobe example.com. This selection overrides the deault domain name.

Note In previous releases, scripts enabled users to avoid being prompted or the NFSv4 domainname during installation.

For JumpStart installations in the Solaris 10 OS, you could use the workaround JumpStartsample script, set_nfs4_domain, to suppress the NFSv4 prompt during installation. This scriptis no longer required. Use the sysidcfg keyword, nfs4_domain, instead.

In prior releases, the /etc/.NFS4inst_state.domain le was created by the sysidnfs4program. This le would suppress the prompt or an NFSv4 domain name during installation.This le is no longer created. Use the sysidcfg keyword, nfs4_domain, instead.

root_password Keyword

You can speciy the root password to the system in the sysidcfg le. To speciy the rootpassword, use the root_password keyword with the ollowing syntax.

root_password=encrypted-password

encrypted-passwordis the encrypted password as it appears in the /etc/shadow le.

security_policy Keyword

You can use the security_policy keyword in your sysidcfg le to congure your system touse the Kerberos network authentication protocol. I you want to congure the system to useKerberos, use the ollowing syntax.

security_policy=kerberos {default_realm=FQDN

admin_server=FQDN kdc=FQDN1, FQDN2, FQDN3}

FQDNspecies the ully qualied domain name o the Kerberos deault realm, theadministration server, or key distribution center (KDC). You must speciy at least one, but nomore than three, key distribution centers.

I you do not want to set the security policy or the system, set security_policy=NONE.

For more inormation about the Kerberos network authentication protocol, see System

Administration Guide: Security Services.




34/278

EXAMPLE 211 Conguring the System to UseKerberos With the security_policy Keyword

This example congures the system to use Kerberos with the ollowing inormation.

The Kerberos deault realm is example.com. The Kerberos administration server is krbadmin.example.com. The two key distribution centers are kdc1.example.com and kdc2.example.com.

security_policy=kerberos

{default_realm=example.COM

admin_server=krbadmin.example.com

kdc=kdc1.example.com,

kdc2.example.com}

service_profile Keyword

You can use the service_profile keyword to install a more secure system by restrictingnetwork services. This security option is available only or initial installations. An upgrademaintains all previously set services.

Use one o the ollowing syntaxes to set this keyword.

service_profile=limited_net

service_profile=open

limited_net species that all network services, except or Secure Shell, are either disabled orconstrained to respond to local requests only. Ater installation, any individual network servicecan be enabled by using the svcadm and svccfg commands.

open species that no network service changes are made during installation.

I the service_profile keyword is not present in the sysidcfg le, no changes are made to thestatus o the network services during installation.

The network services can be enabled ater installation by using the netservices opencommand or by enabling individual services by using SMF commands. See Revising SecuritySettings Ater Installation in Solaris 10 10/09 Installation Guide: Planning or Installation and

Upgrade.

For urther inormation about limiting network security during installation, see PlanningNetwork Security in Solaris 10 10/09 Installation Guide: Planning or Installation and Upgrade.See also the ollowing man pages.

netservices(1M) svcadm(1M)

svccfg(1M) commands


http://docs.sun.com/doc/821-0441/gdpfv?a=viewhttp://docs.sun.com/doc/821-0441/gdpfv?a=viewhttp://docs.sun.com/doc/821-0441/gdpfv?a=viewhttp://docs.sun.com/doc/821-0441/gdpfv?a=viewhttp://docs.sun.com/doc/821-0441/gdpfv?a=viewhttp://docs.sun.com/doc/821-0441/gdpgj?a=viewhttp://docs.sun.com/doc/821-0441/gdpgj?a=viewhttp://docs.sun.com/doc/821-0441/gdpgj?a=viewhttp://docs.sun.com/doc/821-0441/gdpgj?a=viewhttp://docs.sun.com/doc/821-0441/gdpgj?a=viewhttp://docs.sun.com/doc/821-0441/gdpgj?a=viewhttp://docs.sun.com/doc/821-0441/gdpfv?a=viewhttp://docs.sun.com/doc/821-0441/gdpfv?a=viewhttp://docs.sun.com/doc/821-0441/gdpfv?a=view


35/278

system_locale Keyword

You can use the system_locale keyword to speciy the language in which to display the installprogram and desktop. Use the ollowing syntax to speciy a locale.

system_locale=locale

locale species the language that you want the system to use to display the installation panelsand screens. For a list o valid locale values, see the /usr/lib/locale directory or InternationalLanguage Environments Guide.

terminalKeywordYou can use the terminal keyword to speciy the terminal type or the system. Use the

ollowing syntax to speciy the terminal type.

terminal=terminal_type

terminal_type species the terminal type or the system. For a list o valid terminal values, seethe subdirectories in the /usr/share/lib/terminfo directory.

timezone Keyword

You can set the time zone or the system with the timezone keyword. Use the ollowing syntax.

timezone=timezone

In the previous example, timezone species the time zone value or the system. The directoriesand les in the /usr/share/lib/zoneinfo directory provide the valid time zone values. The

timezonevalue is the name o the path relative to the /usr/share/lib/zoneinfo directory. Youcan also speciy any valid Olson time zone.

EXAMPLE 212 Conguring the System Time Zone With the timezone Keyword

In the ollowing example, the system time zone is set to mountain standard time in the UnitedStates.

timezone=US/Mountain

The installation program congures the system to use the time zone inormation in/usr/share/lib/zoneinfo/US/Mountain .

timeserver Keyword

You can use the timeserver keyword to speciy the system that sets the date and time on thesystem you want to install.


SPARC:PreconfguringPower ManagementInormation


36/278

Choose one o the ollowing methods to set the timeserver keyword.

To congure the system to serve as its own time server, set timeserver=localhost.Iyouspeciylocalhost as the time server, the system's time is assumed to be correct.

To speciy another system as the time server, speciy either the host name or the IP addresso the time server with the timeserver keyword. Use the ollowing syntax.

timeserver=hostname or ip-address

hostname is the host name o the time server system. ip-address species the IP address othe time server.

SPARC: Preconfguring Power Management InormationYou can use the Power Managementsotware that is provided in the Solaris OS to automaticallysave the state o a system and turn it of ater it is idle or 30minutes. When you install thecurrent Solaris release on a system that complies with version 2 o the EPA's Energy Starguidelines, or example a Sun4UTM system, the Power Management sotware is installed by

deault. I you install with the Solaris installation program GUI, the installation programprompts you to enable or disable the Power Management sotware. The Solaris text installerprompts you to enable or disable the Power Management sotware ater the installation iscomplete and the system reboots.

Note I your system has Energy Star version 3 or later, you are not prompted or thisinormation.

I you are perorming interactive installations, you cannot precongure the Power Managementinormation and avoid the prompt. However, by using a custom JumpStart installation, you canprecongure the Power Management inormation by using a nish script to create an/autoshutdown or /noautoshutdown le on the system. When the system reboots, the/autoshutdown le enables Power Management and the /noautoshutdown le disables PowerManagement.

For example, the ollowing line in a nish script enables the Power Management sotware andprevents the display o the prompt ater the system reboots.

touch /a/autoshutdown

Finish scripts are described in Creating Finish Scripts in Solaris 10 10/09 Installation Guide:Custom JumpStart and Advanced Installations.

http://docs.sun.com/doc/821-0437/optionalcustom-44024?a=viewhttp://docs.sun.com/doc/821-0437/optionalcustom-44024?a=viewhttp://docs.sun.com/doc/821-0437/optionalcustom-44024?a=viewhttp://docs.sun.com/doc/821-0437/optionalcustom-44024?a=viewhttp://docs.sun.com/doc/821-0437/optionalcustom-44024?a=viewhttp://docs.sun.com/doc/821-0437/optionalcustom-44024?a=view


37/278

Preconfguring With a Naming Service or DHCP

This chapter describes procedures about preconguring system inormation with a namingservice or DHCP. This chapter contains the ollowing sections:

Choosing a Naming Service on page 37 Preconguring With the Naming Service on page 39

Preconguring System Conguration Inormation With the DHCP Service (Tasks) onpage 43

Choosing a Naming Service

You can choose one o the ollowing ways to precongure system conguration inormation.

You can add the system conguration inormation to any o the ollowing. A sysidcfg le on a remote system or diskette

Note The name_service option in the sysidcfg le automatically sets the naming serviceduring installation o the Solaris OS. This setting overrides SMF services previously setupor site.xml. Thereore, you might need to reset your name service ater installation.

The naming service database available at your site

I your site uses DHCP, you can also precongure some system inormation in the siteDHCP server. For more inormation about how to use a DHCP server to preconguresystem inormation, see Preconguring System Conguration Inormation With theDHCP Service (Tasks) on page 43.

Use the ollowing table to determine whether to use a sysidcfg le or a naming servicedatabase to precongure system conguration inormation.

3C H A P T E R 3

37

Choosing a Naming Service


38/278

TABLE 31 Methods to Precongure System Conguration Inormation

Preconfgurable System Inormation Preconfgurable With the sysidcfg File? PreconfgurableWiththeNaming Service?

Naming service Yes Yes

Domain name Yes No

Name server Yes No

Network interace Yes No

Host name Yes

Because this inormation is system

specic, edit the naming servicerather than create a diferentsysidcfg le or each system.

Yes

Internet Protocol (IP) address Yes

Because this inormation is systemspecic, edit the naming servicerather than create a diferentsysidcfg le or each system.

Yes

Netmask Yes No

DHCP Yes No

IPv6 Yes No

Deault route Yes No

Root password Yes No

Security policy Yes No

Language (locale) in which to display the installprogram and desktop

Yes Yes, i NIS or NIS+

No, i DNS or LDAP

Terminal type Yes No

Time zone Yes Yes

Date and time Yes Yes

Web proxy No

You can congure this inormationwith the Solaris installationprogram, but not through thesysidcfg le or the naming service.

No

x86: Monitor type Yes No


M h d P S C i I i (C i d)

PreconfguringWith the Naming Service


39/278

TABLE 31 Methods to Precongure System Conguration Inormation (Continued)Preconfgurable System Inormation Preconfgurable With the sysidcfg File? PreconfgurableWiththeNaming Service?

x86: Keyboard language, keyboard layout Yes No

x86: Graphics card, color depth, display resolution,screen size

Yes No

x86: Pointing device, number o buttons, IRQ level Yes No

SPARC: Power Management (autoshutdown)

You cannot precongure Power Management throughthe sysidcfg le or the naming service. SPARC:

Preconguring Power Management Inormation onpage 36 contains details.

No No

Preconfguring With the Naming Service

The ollowing table provides a high-level overview o the naming service databases that you

need to edit and populate to precongure system inormation.

SystemInormationto Preconfgure NamingServiceDatabase

Host name and Internet Protocol (IP)address

hosts

Date and time hosts. Speciy the timehost alias next to the host name o the systemthat will provide the date and time or the systems that are being

installed.

Time zone timezone

Netmask netmasks

You cannot precongure the locale or a system with the DNS or LDAP name service. I you usethe NIS or NIS+ name service, ollow the procedure below to use your naming service to

precongure the locale or a system.

Chapter 3 Preconfguring With a Naming Service or DHCP 39

PreconfguringWith the Naming Service


40/278

Note In order to successully precongure your system locale by using NIS or NIS+, theollowing requirements must be met:

You must boot the system rom the network by using the ollowing command:

ok boot net

You can use options with this command. See details in Step 2 o theSPARC: To Install theClient Over the Network (DVD) on page 75 procedure.

The NIS or NIS+ server must be available to access during the installation.

I these requirements are ullled, the installer uses the precongured settings and does notprompt or the locale during the installation. I either requirement is not ullled, the installerprompts or your locale inormation during the installation.

To Precongure the Locale Using NIS on page 40 To Precongure the Locale Using NIS+ on page 42

To Preconfgure the Locale Using NIS

Become superuseror assumean equivalent role on thename server.

Change /var/yp/Makefile to addthelocale map.

a. Insert this shell procedure ater thelast variable.time shell procedure.locale.time: $(DIR)/locale

-@if [ -f $(DIR)/locale ]; then \

sed -e "/^#/d" -e s/#.*$$// $(DIR)/locale \

| awk {for (i = 2; i


41/278

b. Find the string all: and, at the end o the list o variables, insert the word locale.

all: passwd group hosts ethers networks rpc services protocols \

netgroup bootparams aliases publickey netid netmasks c2secure \

timezone auto.master auto.home locale

c. Near the end o the fle, ater the last entryo its type, insert the string locale:

locale.time onanewline.

passwd: passwd.time

group: group.time

hosts: hosts.time

ethers: ethers.time

networks: networks.timerpc: rpc.time

services: services.time

protocols: protocols.time

netgroup: netgroup.time

bootparams: bootparams.t

network based installation

Documents