This part describes how to plan your installation over the network.
This chapter describes new features in the Solaris installation programs. To view features for all of the Solaris OS, see Solaris 10 What’s New.
What's New in the Solaris 10 1/06 Release For Solaris Installation
What's New in the Solaris 10 3/05 Release For Solaris Installation
This section describes the following new installation features in the Solaris 10 1/06 release.
Starting with the Solaris 10 1/06 release, Solaris Zones partitioning technology provides the ability to configure non-global zones in a single instance of Solaris, the global zone. A non-global zone is an application execution environment in which processes are isolated from all other zones. If you are running a system with non-global zones installed, you can use standard Solaris upgrade programs to upgrade to the Solaris 1/06 release. You can use either the Solaris interactive installation program or custom JumpStart to upgrade. There are some limitations to upgrading with non-global zones installed.
A limited number of custom JumpStart keywords are supported. For a list of supported custom JumpStart keywords, see Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.
CD-ROMs are not distributed, but you can upgrade with a DVD-ROM or a network installation image.
On a system with non-global zones installed, do not use Solaris Live Upgrade to upgrade your system. While you can create a boot environment with the lucreate command, the luupgrade command cannot upgrade a boot environment that has non-global zones installed. In that case, the upgrade fails and an error message is displayed.
For details on using the Solaris interactive installation program, see Solaris 10 Installation Guide: Basic Installations
Starting with the Solaris 10 1/06 release, the open source GNU GRand Unified BootLoader (GRUB) has been adopted in the Solaris OS for x86 based systems. GRUB is responsible for loading a boot archive into the system's memory. A boot archive is a collection of critical files that is needed during system startup before the root (/) file system is mounted. The boot archive is used to boot the Solaris OS.
The most notable change is the replacement of the Solaris Device Configuration Assistant with the GRUB menu. The GRUB menu facilitates booting the different operating systems that are installed on your system. The GRUB menu is displayed when you boot an x86 based system. From the GRUB menu, you can select an OS instance to install by using the arrow keys. If you do not make a selection, the default OS instance is booted.
The GRUB based boot feature provides the following improvements:
Faster boot times
Installation from USB CD or DVD drives
Ability to boot from USB storage devices
Simplified DHCP setup for PXE boot (no vendor-specific options)
Elimination of all realmode drivers
Ability to use Solaris Live Upgrade and the GRUB menu to quickly activate and fall back to boot environments.
For more information about GRUB refer to the following sections.
Task |
GRUB Task |
For More Information |
---|---|---|
Installation |
Overview information about GRUB based booting | |
Installation planning for GRUB based booting | ||
How to boot and install over the network with the GRUB menu |
Booting and Installing the System From the Network With a DVD Image |
|
How to boot and install with the GRUB menu and the Custom JumpStart installation method | ||
How to use the GRUB menu and Solaris Live Upgrade to activate and fall back to boot environments | ||
Locating the GRUB menu's menu.lst file | ||
System Administration |
How to perform system administration tasks with the GRUB menu |
GNU is a recursive acronym for “GNU's Not UNIX.” For more information, go to http://www.gnu.org.
Starting with the Solaris 1/06 release, you can upgrade the Solaris OS from the Solaris 8, 9, or 10 releases. Upgrades from the Solaris 7 release are not supported.
This section describes the following new installation features in the Solaris 10 3/05 release.
Starting with the Solaris 10 3/05 release, several changes in the installation of the Solaris OS provide a more simplified and unified installation experience.
The changes include the following:
This release has one installation DVD and several installation CDs. The Solaris Operating System DVD includes the content of all the installation CDs.
Solaris Software 1 – This CD is the only bootable CD. From this CD, you can access both the Solaris installation graphical user interface (GUI) and the console-based installation. This CD also enables you to install selected software products from both the GUI and the console-based installation.
Other Solaris Operating System CDs – These CDs contain the following:
Solaris packages that the software prompts you to install if necessary
ExtraValue software that includes supported and unsupported software
Installers
Localized interface software and documentation
The Solaris Installation CD no longer exists.
For both CD and DVD media, the GUI installation is the default (if your system has enough memory). However, you can specify a console-based installation with the text boot option.
The installation process has been simplified, enabling you to select the language support at boot time, but select locales later.
The (noninteractive) Solaris custom JumpStartTM installation method has not changed.
To install the OS, simply insert the Solaris Software - 1 CD or the Solaris Operating System DVD and type one of the following commands.
For the default GUI installation (if system memory permits), type boot cdrom.
For the console-based installation, type boot cdrom - text.
For instructions about how to install the Solaris OS by using CD or DVD media with the new text boot option | |
For changes to setting up an installation server with CD media |
Starting with the Solaris 10 3/05 release, you can choose to install the software with a GUI or with or without a windowing environment. If the memory is sufficient, the GUI is displayed by default. If the memory is insufficient for the GUI, other environments are displayed by default. You can override defaults with the nowin or text boot options. However, you are limited by the amount of memory in your system or by installing remotely. Also, if the Solaris installation program does not detect a video adapter, the program is automatically displayed in a console-based environment.
For specific memory requirements, see System Requirements and Recommendations.
Starting with the Solaris 10 3/05 release, when you install and upgrade the Solaris OS by using the custom JumpStart installation method, new customizations enable the following:
A Solaris Flash installation with additional packages
The custom JumpStart profile package keyword has been enhanced to enable installing a Solaris Flash archive with additional packages. For example, you can install the same base archive on two machines, but add a different set of packages to each machine. These packages do not have to be a part of the Solaris OS distribution.
An installation with additional packages that might not be part of the Solaris distribution
The package keyword has also been enhanced to enable an installation with a package that is not part of the Solaris distribution. You no longer need to write a postinstallation script to add extra packages.
An installation with the ability to install Solaris OS patches
The new custom JumpStart profile patch keyword enables the installation of Solaris OS patches. This feature allows the installation of a list of patches that are specified in a patch file.
For further information, see Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.
Starting with the Solaris 10 3/05 release, the Solaris installation programs enable you to configure multiple interfaces during your installation. You can preconfigure these interfaces in the sysidcfg file for your system. Or you can configure multiple interfaces during the installation. For more information, see the following documents:
In previous Solaris releases, the Solaris software was delivered in separate packages for 32-bit components and 64-bit components. Starting with the Solaris 10 3/05 release, packaging has been simplified with the delivery of most 32-bit components and 64-bit components in a single package. The combined packages retain the names of the original 32-bit packages, and the 64-bit packages are no longer delivered.
The removal of the 64-bit packages simplifies installation and increases performance:
Reduces the number of packages, which simplifies Custom JumpStart scripts that contain lists of packages
Simplifies the packaging system with only one package that groups software functions
Reduces installation time because fewer packages are installed
The 64-bit packages are renamed with the following conventions:
If a 64-bit package has a 32-bit counterpart, the 64-bit package is named with the 32-bit package name. For example, a 64-bit library such as /usr/lib/sparcv9/libc.so.1 previously would have been delivered in SUNWcslx, but now is delivered in SUNWcsl. The 64-bit SUNWcslx package is no longer delivered.
If a package does not have a 32-bit counterpart, the “x” suffix is removed from the name. For example, SUNW1394x becomes SUNW1394.
This change means that you might need to modify your custom JumpStart script or other package installation scripts to remove references to the 64-bit packages.
Starting with the Solaris 10 3/05 release, you can now use the JumpStart installation method to create an empty boot environment when you install the Solaris Operating System. The empty boot environment can then be populated with a Solaris Flash archive for later use.
For further information, see Chapter 11, Custom JumpStart (Reference), in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.
Starting with the Solaris 10 3/05 release, you can now create a more secure system with fewer enabled network services by selecting or specifying the Reduced Networking software group (SUNWCrnet) during your installation. The Reduced Networking software group provides system administration utilities and a multiuser text-based console. SUNWCrnet enables the system to recognize network interfaces. During the installation, you can customize your system's configuration by adding software packages and by activating network services as needed.
For further information, see Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.
Starting with the Solaris 10 3/05 release, the Solaris installation program now enables you to load existing slices from the virtual table of contents (VTOC.) You can now preserve and use the system's existing disk slice tables during your installation, rather than use the installer's default disk layout.
Starting with the Solaris 10 3/05 release, a new feature in the Solaris installation program is a boot-disk partition layout. This layout, by default, accommodates the Service partition on Sun x86 based systems. This installation program enables you to preserve an existing Service partition.
The new default includes the following partitions.
First partition – Service partition (existing size on system)
Second partition – x86 boot partition (approximately 11 Mbytes)
Third partition – Solaris Operating System partition (remaining space on the boot disk)
If you want to use this default layout, select Default when the Solaris installation program asks you to choose a boot-disk layout.
If you install the Solaris OS for x86 based systems on a system that does not currently include a Service partition, the Solaris installation program does not create a new Service partition. If you want to create a Service partition on your system, first use your system's diagnostic CD to create the Service partition. After the Service partition is created, then install the Solaris Operating System.
For information about how to create the Service partition, see your hardware documentation.
For more information, see Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.
This chapter provides you with information about decisions you need to make before you install or upgrade the Solaris Operating System (Solaris OS). This chapter contains the following sections:
This book uses the term slice, but some Solaris documentation and programs might refer to a slice as a partition.
x86: To avoid confusion, this book distinguishes between x86 fdisk partitions and the divisions within the Solaris fdisk partition. The x86 fdisk divisions are called partitions. The divisions within the Solaris fdisk partition are called slices.
The following task map is an overview of the steps necessary to install or upgrade the Solaris OS when using any installation program. Use this task map to identify all of the decisions that you need to make to complete the most efficient installation for your environment.
Table 2–1 Task Map: Installing or Upgrading the Solaris Software
Task |
Description |
For Instructions |
---|---|---|
Choose initial installation or upgrade. |
Decide if you want to perform an initial installation or an upgrade. | |
Choose an installation program. |
The Solaris OS provides several programs for installation or upgrade. Choose the installation method that is most appropriate for your environment. | |
(Solaris interactive installation program) Choose a default or custom installation. |
Decide which type installation is suitable for your environment:
|
For information on the Solaris installation program's choices, see Chapter 5, Gathering Information Before Installation or Upgrade (Planning) |
Review system requirements. Also, plan and allocate disk space and swap space. |
Determine if your system meets the minimum requirements to install or upgrade. Allocate disk space on your system for the components of the Solaris OS that you want to install. Determine the appropriate swap-space layout for your system. | |
Choose to install a system from local media or from the network. |
Decide on the most appropriate installation media for your environment. | |
Gather information about your system. |
|
|
(Optional) Set system parameters. |
You can preconfigure system information to avoid being prompted for the information during the installation or upgrade. |
Chapter 6, Preconfiguring System Configuration Information (Tasks). |
(Optional) Prepare to install the Solaris software from the network. |
If you chose to install the Solaris software from the network, complete the following tasks.
|
To install over a local area network, see Chapter 9, Preparing to Install From the Network With CD Media (Tasks). To install over a wide area network, see Chapter 13, Preparing to Install With WAN Boot (Tasks). |
(Upgrade only) Perform tasks prior to upgrade. |
Back up your system and determine if you can upgrade with disk space reallocation. | |
Perform an installation or upgrade. |
Use the Solaris installation method that you chose to install or upgrade the Solaris software. |
The chapter or chapters that provide detailed instructions for the installation programs. |
Troubleshoot installation problems |
Review the troubleshooting information when you encounter problems with your installation. |
The Solaris software is distributed on DVD or CD media so that you can install or upgrade systems that have access to a DVD-ROM or CD-ROM drive.
You can set up the systems to install from the network with remote DVD or CD images. You might want to set up systems this way for the following reasons:
If you have systems that do not have local DVD-ROM or CD-ROM drives
If you are installing several systems and do not want to insert the discs into every local drive to install the Solaris software
You can use all of the Solaris installation methods to install a system from the network. However, by installing systems from the network with the Solaris Flash installation feature or with a custom JumpStart installation, you can centralize and automate the installation process in a large enterprise. For more details about the different installation methods, refer to Choosing a Solaris Installation Method.
Installing the Solaris software from the network requires initial setup. For information about preparing to install from the network, choose one of the following options.
For detailed instructions about preparing to install from a local area network |
Chapter 9, Preparing to Install From the Network With CD Media (Tasks) |
For instructions about preparing to install over a wide area network | |
For instructions about how to install x86 based clients over the network by using PXE |
x86: Overview of Booting and Installing Over the Network With PXE |
You can choose to perform an initial installation or, if your system is already running the Solaris OS, you can upgrade your system.
An initial installation overwrites the system's disk with the new version of the Solaris OS. If your system is not running the Solaris OS, you must perform an initial installation.
If the system is already running the Solaris OS, you can choose to perform an initial installation. If you want to preserve any local modifications, before you install, you must back up the local modifications. After you complete the installation, you can restore the local modifications.
You can use any of the Solaris installation methods to perform an initial installation. For detailed information about the different Solaris installation methods, refer to Choosing a Solaris Installation Method.
You can upgrade the Solaris OS by using two upgrade methods: standard and Solaris Live Upgrade. A standard upgrade maintains as many existing configuration parameters as possible of the current Solaris OS. Solaris Live Upgrade creates a copy of the current system. This copy can be upgraded with a standard upgrade. The upgraded Solaris OS can then be switched to become the current system by a simple reboot. If a failure occurs, you can switch back to the original Solaris OS with a reboot. Solaris Live Upgrade enables you to keep your system running while you upgrade and enables you to switch back and forth between Solaris OS releases.
For more information about upgrading and the list of upgrade methods, see Upgrade.
The Solaris OS provides several programs for installation or upgrade. Each installation technology offers different features that are designed for specific installation requirements and environments. Use the following table to help you decide which installation method to use.
Table 2–2 Choosing Your Installation Method
The Sun Java System Application Server Platform Edition 8 provides for broad deployment of application services and web services. This software is automatically installed with the Solaris OS. You can find documentation for the server in the following areas:
For documentation about starting the server |
See Sun Java System Application Server Platform Edition 8 QuickStart Guide in the installation directory at /docs/QuickStart.html |
For the full Application Server documentation set | |
For a tutorial |
This chapter describes system requirements to install or upgrade to the Solaris OS. General guidelines for planning the disk space and default swap space allocation are also provided. This chapter contains the following sections:
SPARC Based System |
Size |
---|---|
Memory to install or upgrade |
256 MB is the recommended size. 128 MB is the minimum size. Note – Some optional installation features are enabled only when sufficient memory is present. For example, if you install from a DVD with insufficient memory, you install through the Solaris installation program's text installer, not through the GUI. For more information about these memory requirements, see Table 3–3. |
Swap area |
512 MB is the default size. Note – You might need to customize the swap space. Swap space is based on the size of the system's hard disk. |
Processor requirements |
200–MHz or faster processor is required. |
Table 3–2 x86: Memory, Swap, and Processor Recommendations
x86 Based System |
Size |
---|---|
Memory to install or upgrade |
Note – Some optional installation features are enabled only when sufficient memory is present. For example, if you install from a DVD with insufficient memory, you install through the Solaris installation program's text installer, not through the GUI. For more information about these memory requirements, see Table 3–3. |
Swap area |
512 MB is the default size. Note – You might need to customize the swap space. Swap space is based on the size of the system's hard disk. |
Processor requirements |
120–MHz or faster processor is recommended. Hardware floating-point support is required. |
You can choose to install the software with a GUI or with or without a windowing environment. If there is sufficient memory, the GUI is displayed by default. Other environments are displayed by default if memory is insufficient for the GUI. You can override defaults with the nowin or text boot options. But, you are limited by the amount of memory in your system or by installing remotely. Also if the Solaris installation program does not detect a video adapter, it automatically displays in a console-based environment. Table 3–3 describes these environments and lists minimal memory requirements for displaying them.
Table 3–3 SPARC: Memory Requirements for Display Options
SPARC: Memory |
Type of Installation |
Description |
---|---|---|
128–383 MB |
Text-based |
Contains no graphics, but provides a window and the ability to open other windows. If you install by using the text boot option and the system has enough memory, you are installing in a windowing environment. If you are installing remotely through a tip line or using the nowin boot option, you are limited to the console-based installation. |
384 MB or greater |
GUI-based |
Provides windows, pull-down menus, buttons, scrollbars, and iconic images. |
Table 3–4 x86: Memory Requirements for Display Options
Before you install the Solaris software, you can determine if your system has enough disk space by doing some high-level planning.
Planning disk space is different for everyone. Consider allocating space for the following conditions, depending on your needs.
Table 3–5 General Disk Space and Swap Space Planning
Conditions for Space Allocations |
Description |
---|---|
File systems |
For each file system that you create, allocate an additional 30 percent more disk space than you need to enable you to upgrade to future Solaris versions. By default, the Solaris installation methods create only root (/) and /swap. When space is allocated for OS services, the /export directory is also created. If you are upgrading to a major Solaris release, you might need to reslice your system or allocate double the space that you need at installation time. If you are upgrading to an update, you could prevent having to reslice your system by allocating extra disk space for future upgrades. A Solaris update release needs approximately 10 percent more disk space than the previous release. You can allocate an additional 30 percent of disk space for each file system to allow space for several Solaris updates. |
The /var file system |
If you intend to use the crash dump feature savecore(1M), allocate double the amount of your physical memory in the /var file system. |
Swap |
The Solaris installation program allocates a default swap area of 512 Mbytes under the following conditions:
By default, the Solaris installation programs allocate swap space by placing swap so that it starts at the first available disk cylinder (typically cylinder 0 on SPARC based systems). This placement provides maximum space for the root (/) file system during the default disk layout and enables the growth of the root (/) file system during an upgrade. If you think you might need to expand the swap area in the future, you can place the swap slice so that it starts at another disk cylinder by using one of the following methods.
For an overview of the swap space, see Chapter 21, Configuring Additional Swap Space (Tasks), in System Administration Guide: Devices and File Systems. |
A server that is providing home directory file systems |
By default, home directories are usually located in the /export file system. |
The Solaris software group you are installing |
A software group is a grouping of software packages. When you are planning disk space, remember that you can add or remove individual software packages from the software group that you select. For information about software groups, see Disk Space Recommendations for Software Groups. |
Upgrade |
|
Language support |
For example, Chinese, Japanese, or Korean. If you plan to install a single language, allocate approximately 0.7 Gbytes of additional disk space for the language. If you plan to install all language supports, you need to allocate up to approximately 2.5 Gbytes of additional disk space for the language supports, depending on the software group you install. |
Printing or mail support |
Allocate additional space. |
Additional software or third-party software |
Allocate additional space. |
The Solaris software groups are collections of Solaris packages. Each software group includes support for different functions and hardware drivers.
For an initial installation, you select the software group to install, based on the functions that you want to perform on the system.
For an upgrade, you must upgrade to a software group that is installed on the system. For example, if you previously installed the End User Solaris Software Group on your system, you cannot use the upgrade option to upgrade to the Developer Solaris Software Group. However, during the upgrade you can add software to the system that is not part of the currently installed software group.
When you are installing the Solaris software, you can choose to add or remove packages from the Solaris software group that you selected. When you are selecting which packages to add or remove, you need to know about software dependencies and how the Solaris software is packaged.
The following figure shows the grouping of software packages. Reduced Network Support contains the minimal number of packages and Entire Solaris Software Group Plus OEM Support contains all the packages.
Table 3–6 lists the Solaris software groups and the recommended amount of disk space that you need to install each group.
The disk space recommendations in Table 3–6 include space for the following items.
Swap space
Patches
Additional software packages
You might find that the software groups require less disk space than the amount that is listed in this table.
Software Group |
Description |
Recommended Disk Space |
---|---|---|
Entire Solaris Software Group Plus OEM Support |
Contains the packages for the Entire Solaris Software Group plus additional hardware drivers, including drivers for hardware that is not on the system at the time of installation. |
6.8 Gbytes |
Entire Solaris Software Group |
Contains the packages for the Developer Solaris Software Group and additional software that is needed for servers. |
6.7 Gbytes |
Developer Solaris Software Group |
Contains the packages for the End User Solaris Software Group plus additional support for software development. The additional software development support includes libraries, include files, man pages, and programming tools. Compilers are not included. |
6.6 Gbytes |
End User Solaris Software Group |
Contains the packages that provide the minimum code that is required to boot and run a networked Solaris system and the Common Desktop Environment. |
5.3 Gbytes |
Core System Support Software Group |
Contains the packages that provide the minimum code that is required to boot and run a networked Solaris system. |
2.0 Gbytes |
Reduced Network Support Software Group |
Contains the packages that provide the minimum code that is required to boot and run a Solaris system with limited network service support. The Reduced Network Support Software Group provides a multiuser text-based console and system administration utilities. This software group also enables the system to recognize network interfaces, but does not activate network services. |
2.0 Gbytes |
You can upgrade a system by using one of three different upgrade methods: Solaris Live Upgrade, the Solaris installation program, and custom JumpStart.
Table 3–7 Solaris Upgrade Methods
Issue |
Description |
---|---|
Upgrading to a different software group |
You cannot upgrade your system to a software group that is not installed on the system. For example, if you previously installed the End User Solaris Software Group on your system, you cannot use the upgrade option to upgrade to the Developer Solaris Software Group. However, during the upgrade you can add software to the system that is not part of the currently installed software group. |
Starting with the Solaris 10 1/06 release: Upgrading when non-global zones are installed |
When you are upgrading the Solaris OS, you can upgrade a system that has non-global zones installed. The Solaris interactive installation program and custom JumpStart programs enable an upgrade. For limitations when upgrading, see Upgrading When Non-Global Zones Are Installed. |
You can perform a standard interactive upgrade with the Solaris installation program or an unattended upgrade with the custom JumpStart installation method. Solaris Live Upgrade enables you to upgrade a running system.
Upgrade Program |
Description |
For More Information |
---|---|---|
Solaris Live Upgrade |
Enables you to create a copy of the currently running system. The copy can be upgraded and then a reboot switches the upgraded copy to become the currently running system. Using Solaris Live Upgrade reduces the downtime that is required to upgrade the Solaris OS. Also, Solaris Live Upgrade can prevent problems with upgrading. An example is the ability to recover from an upgrade if the power fails, because the copy being upgraded is not the currently running system. |
To plan for disk space allocation when using Solaris Live Upgrade, see Solaris Live Upgrade Requirements in Solaris 10 Installation Guide: Solaris Live Upgrade and Upgrade Planning. |
The Solaris installation program |
Guides you through an upgrade with an interactive GUI. | |
Custom JumpStart program |
Provides an automated upgrade. A profile file and optional preinstallation and postinstallation scripts provide the information required. When creating a custom JumpStart profile for an upgrade, specify install_type upgrade. You must test the custom JumpStart profile against the system's disk configuration and currently installed software before you upgrade. Use the pfinstall -D command on the system that you are upgrading to test the profile. You cannot test an upgrade profile by using a disk configuration file. |
|
The Solaris Flash installation feature provides a method of creating a copy of the whole installation from a master system that can be replicated on many clone systems. This copy is called a Solaris Flash archive. You can install an archive by using any installation program.
A Solaris Flash archive cannot be properly created when a non-global zone is installed. The Solaris Flash feature is not compatible with Solaris Zones partitioning technology. If you create a Solaris Flash archive, the resulting archive is not installed properly when the archive is deployed under these conditions:
The archive is created In a non-global zone
The archive is created in a global zone that has non-global zones installed
For information about installing an archive, see the following table.
Solaris Live Upgrade | |
Custom JumpStart | |
Solaris interactive installation | |
WAN boot installation method |
The upgrade option in the Solaris installation program and the upgrade keyword in the custom JumpStart program provide the ability to reallocate disk space. This reallocation automatically changes the sizes of the disk slices. You can reallocate disk space if the current file systems do not have enough space for the upgrade. For example, file systems might need more space for the upgrade for the following reasons:
The Solaris software group that is currently installed on the system contains new software in the new release. Any new software that is included in a software group is automatically selected to be installed during the upgrade.
The size of the existing software on the system has increased in the new release.
The auto-layout feature attempts to reallocate the disk space to accommodate the new size requirements of the file system. Initially, auto-layout attempts to reallocate space, based on a set of default constraints. If auto-layout cannot reallocate space, you must change the constraints on the file systems.
Auto-layout does not have the ability to “grow” file systems. Auto-layout reallocates space by the following process:
Backing up required files on the file systems that need to change.
Repartitioning the disks on the basis of the file system changes.
Restoring the backup files before the upgrade happens.
If you are using the Solaris installation program, and auto-layout cannot determine how to reallocate the disk space, you must use the custom JumpStart program to upgrade.
If you are using the custom JumpStart method to upgrade and you create an upgrade profile, disk space might be a concern. If the current file systems do not contain enough disk space for the upgrade, you can use the backup_media and layout_constraint keywords to reallocate disk space. For an example of how to use the backup_media and layout_constraint keywords in a profile, refer to Profile Examples in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.
Backing up your existing file systems before you upgrade to the Solaris OS is highly recommended. If you copy file systems to removable media, such as tape, you can safeguard against data loss, damage, or corruption. For detailed instructions to back up your system, refer to Chapter 24, Backing Up and Restoring File Systems (Overview), in System Administration Guide: Devices and File Systems.
To see the version of Solaris software that is running on your system, type either of the following commands.
$ uname -a |
The cat command provides more detailed information.
$ cat /etc/release |
As a part of your installation, you can preconfigure the locale that you want the system to use. A locale determines how online information is displayed in a specific language and specific region. A language might also include more than one locale to accommodate regional differences, such as differences in the format of date and time, numeric and monetary conventions, and spelling.
You can preconfigure the system locale in a custom JumpStart profile or in the sysidcfg file.
Setting the locale in a profile |
Creating a Profile in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations |
Setting the locale in the sysidcfg file | |
List of locale values |
When you are adding clients for a network installation, you must know your system architecture (platform group). If you are writing a custom JumpStart installation rules file, you need to know the platform name.
Some examples of platform names and groups follow. For a full list of SPARC based systems, see Solaris Sun Hardware Platform Guide at http://docs.sun.com/.
Table 3–8 Example of Platform Names and Groups
System |
Platform Name |
Platform Group |
---|---|---|
Sun Fire |
T2000 |
sun4v |
Sun BladeTM |
SUNW,Sun-Blade-100 |
sun4u |
x86 based |
i86pc |
i86pc |
On a running system, you can also use the uname -i command to determine a system's platform name or the uname -m command to determine a system's platform group.
The following introduction provides high-level planning information for global and non-global zones. For overview and planning information and specific procedures, see Chapter 16, Introduction to Solaris Zones, in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.
After the Solaris OS is installed, you can install and configure zones. The global zone is the single instance of the operating system that is running and is contained on every Solaris system. The global zone is both the default zone for the system and the zone that is used for system-wide administrative control. A non-global zone is a virtualized operating system environment.
Solaris Zones are a software partitioning technology used to virtualize operating system services and provide an isolated and secure environment for running applications. When you create a zone, you produce an application execution environment in which processes are isolated from all other zones. This isolation prevents processes that are running in one zone from monitoring or affecting processes that are running in any other zones. Even a process running in a non-global zone with superuser credentials cannot view or affect activity in any other zones. A process running in the global zone with superuser credentials can affect any process in any zone.
The global zone is the only zone from which a non-global zone can be configured, installed, managed, or uninstalled. Only the global zone is bootable from the system hardware. Administration of the system infrastructure, such as physical devices, routing, or dynamic reconfiguration (DR), is only possible in the global zone. Appropriately privileged processes running in the global zone can access objects associated with any or all other zones. The following table summarizes the characteristics of both global and non-global zones.
Global Zone |
Non-Global Zone |
---|---|
Is assigned ID 0 by the system |
Is assigned a zone ID by the system when the zone is booted |
Provides the single instance of the Solaris kernel that is bootable and running on the system |
Shares operation under the Solaris kernel booted from the global zone |
Contains a complete installation of the Solaris system software packages |
Contains an installed subset of the complete Solaris Operating System software packages |
Can contain additional software packages or additional software, directories, files, and other data not installed through packages |
Contains Solaris software packages shared from the global zone |
Provides a complete and consistent product database that contains information about all software components installed in the global zone |
Can contain additional installed software packages not shared from the global zone Can contain additional software, directories, files, and other data created on the non-global zone that are not installed through packages or shared from the global zone |
Holds configuration information specific to the global zone only, such as the global zone host name and file system table |
Has configuration information specific to that non-global zone only, such as the non-global zone host name and file system table |
Is the only zone that is aware of all devices and all file systems |
Has a complete and consistent product database that contains information about all software components installed on the zone, whether present on the non-global zone or shared read-only from the global zone |
Is the only zone with knowledge of non-global zone existence and configuration |
Is not aware of the existence of any other zones |
Is the only zone from which a non-global zone can be configured, installed, managed, or uninstalled |
Cannot install, manage, or uninstall other zones, including itself |
For more information, see the following:
TAfter the Solaris OS is installed, you can install and configure zones. The global zone is the single instance of the operating system that is running and is contained on every Solaris system. The global zone is both the default zone for the system and the zone that is used for system-wide administrative control. A non-global zone is a virtualized operating system environment.
Any command that accepts an alternate root (/) file system by using the -R option or equivalent must not be used if the following are true:
The command is run in the global zone.
The alternative root (/) file system refers to any path within a non-global zone.
An example is the -R root_path option to the pkgadd utility run from the global zone with a path to the root (/) file system in a non-global zone.
For a list of utilities that accept an alternate root (/) file system and more information about zones, see Restriction on Accessing A Non-Global Zone From the Global Zone in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.
When the Solaris OS is installed, the software group installed in the global zone is the set of packages that is shared by all the non-global zones. For example, if you install the Entire software group, all zones contain these packages. By default, any additional packages installed in the global zone also populate the non-global zones. You can segregate into non-global zones any applications, namespaces, servers, and network connections such as NFS and DHCP as well as other software. Each non-global zone is unaware of other non-global zones and each can operate independently. For example, you might have installed the Entire software group on the global zone and have running on separate non-global zones the Java Enterprise System Messaging Server, a database, DHCP, and a web server. When installing non-global zones remember the performance requirements of the applications running in each non-global zone.
A Solaris Flash archive cannot be properly created when a non-global zone is installed. The Solaris Flash feature is not compatible with Solaris Zones partitioning technology. If you create a Solaris Flash archive, the resulting archive is not installed properly when the archive is deployed under these conditions:
The archive is created In a non-global zone
The archive is created in a global zone that has non-global zones installed
Starting with the Solaris 10 1/06 release, when you are upgrading the Solaris OS, you can upgrade a system that has non-global zones installed. The Solaris interactive installation program and custom JumpStart programs enable an upgrade.
With the Solaris interactive installation program, you can upgrade a system with non-global zones by selecting the Upgrade Install on the Select Upgrade or Initial Install panel. The installation program then analyzes your system to determine if your system is upgradable, and provides you a summary of the analysis. The installation program then prompts you to continue the upgrade. You can use this program with the following limitations:
You cannot customize your upgrade. For example, you cannot install additional software products, install additional locale packages, or modify the disk layout.
You must use the Solaris 10 DVD or a DVD-created network installation image. You cannot use the Solaris 10 Software CDs to upgrade a system. For more information about installing with this program, see Chapter 2, Installing With the Solaris Installation Program (Tasks), in Solaris 10 Installation Guide: Basic Installations.
With the custom JumpStart installation program, you can upgrade by using only the install_type and root_device keywords.
Because some keywords affect non-global zones, some keywords cannot be included in a profile. For example, using keywords that add packages, reallocate disk space, or add locales would affect non-global zones. If you use these keywords, they are ignored or cause the JumpStart upgrade to fail. For a list of these keywords, see Limiting Profile Keywords When Upgrading With Non-Global Zones in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.
You cannot use Solaris Live Upgrade to upgrade a system when non-global zones are installed. You can create a boot environment with the lucreate command, but if you use the luupgrade command, the upgrade fails. An error message is displayed.
When installing the global zone, be sure to reserve enough disk space for all of the zones you might create. Each non-global zone might have unique disk space requirements. The following description is a brief overview of planning information. For complete planning requirements and recommendations, see Chapter 18, Planning and Configuring Non-Global Zones (Tasks), in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.
No limits are placed on how much disk space can be consumed by a zone. The global zone administrator is responsible for space restriction. Even a small uniprocessor system can support a number of zones running simultaneously.
The characteristics of the packages installed in the global zone affect the space requirements of the non-global zones that are created. The number of packages and space requirements are factors. The following are general disk space guidelines.
Approximately 100 Mbytes of free disk space is suggested when the global zone has been installed with all of the standard Solaris packages. Increase this amount if additional packages are installed in the global zone. By default, any additional packages installed in the global zone also populate the non-global zones. The directory location in the non-global zone for these additional packages is specified through the inherit-pkg-dir resource.
Add 40 Mbytes of RAM per zone if the system has sufficient swap space. This addition is recommended to make each zone operational. When planning your system size, consider this addition of RAM.
In previous Solaris releases, the Solaris OS was delivered in separate packages for 32-bit and 64-bit components. In the Solaris 10 OS, packaging has been simplified with the delivery of most 32-bit and 64-bit components in a single package. The combined packages retain the names of the original 32-bit packages, and the 64-bit packages are no longer delivered. This change reduces the number of packages and simplifies installation. This change means that you might need to modify your custom JumpStart script or other package installation scripts to remove references to the 64-bit packages.
The 64-bit packages are renamed with the following conventions:
If a 64-bit package has a 32-bit counterpart, the 64-bit package is named with the 32-bit package name. For example, a 64-bit library such as /usr/lib/sparcv9/libc.so.1 previously would have been delivered in SUNWcslx, but now is delivered in SUNWcsl. The 64-bit SUNWcslx package is no longer delivered.
If a package does not have a 32-bit counterpart, the “x” suffix is removed from the name. For example, SUNW1394x becomes SUNW1394.
When using the Solaris OS on x86 based systems, follow these guidelines for partitioning your system.
The Solaris installation program uses a default boot-disk partition layout. These partitions are called fdisk partitions. An fdisk partition is a logical partition of a disk drive that is dedicated to a particular operating system on x86 based systems. To install the Solaris software, you must set up at least one Solaris fdisk partition on an x86 based system. x86 based systems allow up to four different fdisk partitions on a disk. These partitions can be used to hold individual operating systems. Each operating system must be located on a unique fdisk partition. A system can only have one Solaris fdisk partition per disk.
Table 3–9 x86: Default Partitions
The Solaris installation program uses a default boot-disk partition layout to accommodate the diagnostic or service partition. If your system currently includes a diagnostic or service partition, the default boot-disk partition layout enables you to preserve this partition.
If you install the Solaris OS on an x86 based system that does not currently include a diagnostic or service partition, the installation program does not create a new diagnostic or Service partition by default. If you want to create a diagnostic or service partition on your system, see your hardware documentation.
This chapter describes the GRUB based booting on x86 based systems that relates to Solaris installation. This chapter contains the following sections:
Starting with the Solaris 10 1/06 release, GRUB, the open source boot loader, has been adopted as the default boot loader in the Solaris OS.
GRUB based booting is not available on SPARC based systems.
The boot loader is the first software program that runs after you power on a system. After you power on an x86 based system, the Basic Input/Output System (BIOS) initializes the CPU, the memory, and the platform hardware. When the initialization phase has completed, the BIOS loads the boot loader from the configured boot device, and then transfers control of the system to the boot loader.
GRUB is an open source boot loader with a simple menu interface that includes boot options that are predefined in a configuration file. GRUB also has a command-line interface that is accessible from the menu interface for performing various boot commands. In the Solaris OS, the GRUB implementation is compliant with the Multiboot Specification. The specification is described in detail at http://www.gnu.org/software/grub/grub.html.
Because the Solaris kernel is fully compliant with the Multiboot Specification, you can boot a Solaris x86 based system by using GRUB. With GRUB, you can more easily boot and install various operating systems. For example, on one system, you could individually boot the following operating systems:
Solaris OS
Microsoft Windows
GRUB detects Microsoft Window partitions but does not verify that the OS can be booted.
A key benefit of GRUB is that it is intuitive about file systems and kernel executable formats, which enables you to load an operating system without recording the physical position of the kernel on the disk. With GRUB based booting, the kernel is loaded by specifying its file name, and the drive, and the partition where the kernel resides. GRUB based booting replaces the Solaris Device Configuration Assistant and simplifies the booting process with a GRUB menu.
After GRUB gains control of the system, a menu is displayed on the console. In the GRUB menu, you can do the following:
Select an entry to boot your system
Modify a boot entry by using the built-in GRUB edit menu
Manually load an OS kernel from the command line
A configurable timeout is available to boot the default OS entry. Pressing any key aborts the default OS entry boot.
To view an example of a GRUB menu, see Description of the GRUB Main Menu.
The device naming conventions that GRUB uses are slightly different from previous Solaris OS versions. Understanding the GRUB device naming conventions can assist you in correctly specifying drive and partition information when you configure GRUB on your system.
The following table describes the GRUB device naming conventions.
Table 4–1 Naming Conventions for GRUB Devices
Device Name |
Description |
---|---|
(fd0), (fd1) |
First diskette, second diskette |
(nd) |
Network device |
(hd0,0), (hd0,1) |
First and second fdisk partition of first bios disk |
(hd0,0,a), (hd0,0,b) |
Solaris/BSD slice 0 and 1 on first fdisk partition on the first bios disk |
All GRUB device names must be enclosed in parentheses. Partition numbers are counted from 0 (zero), not from 1.
For more information about fdisk partitions, see Guidelines for Creating an fdisk Partition in System Administration Guide: Devices and File Systems.
For more information about these changes, see the following references:
Table 4–2 Where to Find Information on GRUB Based Installations
Topic |
GRUB Menu Tasks |
For More Information |
---|---|---|
Installation |
To install from the Solaris OS CD or DVD media | |
To install from a network installation image | ||
To configure a DHCP server for network installations |
Preconfiguring System Configuration Information With the DHCP Service (Tasks) |
|
To install with the Custom JumpStart program | ||
To activate or fall back to a boot environment by using Solaris Live Upgrade | ||
System Administration |
For more detailed information about GRUB and for administrative tasks |
Chapter 11, GRUB Based Booting (Tasks), in System Administration Guide: Basic Administration |
This section describes the basics of GRUB based booting and describes the GRUB menu.
When you install the Solaris OS, two GRUB menu entries are installed on the system by default. The first entry is the Solaris OS entry. The second entry is the failsafe boot archive, which is to be used for system recovery. The Solaris GRUB menu entries are installed and updated automatically as part of the Solaris software installation and upgrade process. These entries are directly managed by the OS and should not be manually edited.
During a standard Solaris OS installation, GRUB is installed on the Solaris fdisk partition without modifying the system BIOS setting. If the OS is not on the BIOS boot disk, you need to do one of the following:
Modify the BIOS setting.
Use a boot manager to bootstrap to the Solaris partition. For more details, see your boot manager.
The preferred method is to install the Solaris OS on the boot disk. If multiple operating systems are installed on the machine, you can add entries to the menu.lst file. These entries are then displayed in the GRUB menu the next time you boot the system.
For additional information on multiple operating systems, see How Multiple Operating Systems Are Supported in the GRUB Boot Environment in System Administration Guide: Basic Administration.
Performing a GRUB based network boot requires a DHCP server that is configured for PXE clients and an install server that provides tftp service. The DHCP server must be able to respond to the DHCP classes, PXEClient and GRUBClient. The DHCP response must contain the following information:
IP address of the file server
Name of the boot file (pxegrub)
rpc.bootparamd, which is usually a requirement on the server side for performing a network boot, is not required for a GRUB based network boot.
If no PXE or DHCP server is available, you can load GRUB from CD-ROM or local disk. You can then manually configure the network in GRUB and download the multiboot program and the boot archive from the file server.
For more information, see x86: Overview of Booting and Installing Over the Network With PXE.
When you boot an x86 based system, the GRUB menu is displayed. This menu provides a list of boot entries to choose from. A boot entry is an OS instance that is installed on your system. The GRUB menu is based on the menu.lst file, which is a configuration file. The menu.lst file is created by the Solaris installation program and can be modified after installation. The menu.lst file dictates the list of OS instances that are shown in the GRUB menu.
If you install or upgrade the Solaris OS, the GRUB menu is automatically updated. The Solaris OS is then displayed as a new boot entry.
If you install an OS other than the Solaris OS, you must modify the menu.lst configuration file to include the new OS instance. Adding the new OS instance enables the new boot entry to appear in the GRUB menu the next time that you boot the system.
In the following example, the GRUB main menu shows the Solaris and Microsoft Windows operating systems. A Solaris Live Upgrade boot environment is also listed that is named second_disk. See the following for descriptions of each menu item.
GNU GRUB version 0.95 (616K lower / 4127168K upper memory) +-------------------------------------------------------------------+ |Solaris | |Solaris failsafe | |second_disk | |second_disk failsafe | |Windows | +-------------------------------------------------------------------+ Use the ^ and v keys to select which entry is highlighted. Press enter to boot the selected OS, 'e' to edit the commands before booting, or 'c' for a command-line. |
Specifies the Solaris OS.
Specifies a boot archive that can be used for recovery if the Solaris OS is damaged.
Specifies a Solaris Live Upgrade boot environment. The second_disk boot environment was created as a copy of the Solaris OS. It was upgraded and activated with the luactivate command. The boot environment is available for booting.
Specifies the Microsoft Windows OS. GRUB detects these partitions but does not verify that the OS can be booted.
The GRUB menu.lst file lists the contents of the GRUB main menu. The GRUB main menu lists boot entries for all the OS instances that are installed on your system, including Solaris Live Upgrade boot environments. The Solaris software upgrade process preserves any changes that you make to this file.
Any revisions made to the menu.lst file are displayed on the GRUB main menu, along with the Solaris Live Upgrade entries. Any changes that you make to the file become effective at the next system reboot. You can revise this file for the following reasons:
To add to the GRUB menu entries for operating systems other than Solaris
To customize booting behavior such as specifying the default OS on the GRUB menu
Do not use the GRUB menu.lst file to modify Solaris Live Upgrade entries. Modifications could cause Solaris Live Upgrade to fail.
Although you can use the menu.lst file to customize booting behavior such as booting with the kernel debugger, the preferred method for customization is to use the eeprom command. If you use the menu.lst file to customize, the Solaris OS entries might be modified during a software upgrade. Changes to the file would then be lost.
For information about how to use the eeprom command, see How to Set Solaris Boot Parameters by Using the eeprom Command in System Administration Guide: Basic Administration.
Here is a sample of a menu.lst file:
default 0 timeout 10 title Solaris root (hd0,0,a) kernel /platform/i86pc/multiboot -B console=ttya module /platform/i86pc/boot_archive title Solaris failsafe root (hd0,0,a) kernel /boot/multiboot -B console=ttya -s module /boot/x86.miniroot.safe #----- second_disk - ADDED BY LIVE UPGRADE - DO NOT EDIT ----- title second_disk root (hd0,1,a) kernel /platform/i86pc/multiboot module /platform/i86pc/boot_archive title second_disk failsafe root (hd0,1,a) kernel /boot/multiboot kernel/unix -s module /boot/x86.miniroot-safe #----- second_disk -------------- END LIVE UPGRADE ------------ title Windows root (hd0,0) chainloader -1 |
Specifies which item to boot if the timeout expires. To change the default, you can specify another item in the list by changing the number. The count begins with zero for the first title. For example, change the default to 2 to boot automatically to the second_disk boot environment.
Specifies the number of seconds to wait for user input before booting the default entry. If no timeout is specified, you are required to choose an entry.
Specifies the name of the operating system.
If this is a Solaris Live Upgrade boot environment, OS name is the name you gave the new boot environment when it was created. In the previous example, the Solaris Live Upgrade boot environment is named second_disk.
If this is a failsafe boot archive, this boot archive is used for recovery when the primary OS is damaged. In the previous example, Solaris failsafe and second_disk failsafe are the recovery boot archives for the Solaris and second_disk operating systems.
Specifies on which disk, partition, and slice to load files. GRUB automatically detects the file system type.
Specifies the multiboot program. The kernel command must always be followed by the multiboot program. The string after multiboot is passed to the Solaris OS without interpretation.
For a complete description of multiple operating systems, see How Multiple Operating Systems Are Supported in the GRUB Boot Environment in System Administration Guide: Basic Administration.
You must always use the bootadm command to locate the GRUB menu's menu.lst file. The list-menu subcommand finds the active GRUB menu. The menu.lst file lists all the operating systems that are installed on a system. The contents of this file dictate the list of operating systems that is displayed on the GRUB menu. If you want to make changes to this file, see x86: Locating the GRUB Menu's menu.lst File (Tasks).
Starting with the Solaris 10 1/06 release, the GRUB menu can be updated. For example, you might want to change the default time for how fast the default OS is booted. Or, you might want to add another OS to the GRUB menu.
Typically, the active GRUB menu's menu.lst file is located at /boot/grub/menu.lst. In some situations, the GRUB menu.lst file resides elsewhere. For example, in a system that uses Solaris Live Upgrade, the GRUB menu.lst file might be on a boot environment that is not the currently running boot environment. Or if you have upgraded a system with an x86 boot partition, the menu.lst file might reside in the /stubboot directory. Only the active GRUB menu.lst file is used to boot the system. In order to modify the GRUB menu that is displayed when you boot the system, the active GRUB menu.lst file must be modified. Changing any other GRUB menu.lst file has no effect on the menu that is displayed when you boot the system. To determine the location of the active GRUB menu.lst file, use the bootadm command. The list-menu subcommand displays the location of the active GRUB menu. The following procedures determine the location of the GRUB menu's menu.lst file.
For more information about the bootadm command, see bootadm(1M) man page.
In the following procedure, the system contains two operating systems: Solaris and a Solaris Live Upgrade boot environment, second_disk. The Solaris OS has been booted and contains the GRUB menu.
Become superuser or assume an equivalent role.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
To locate the menu.lst file, type:
# /sbin/bootadm list-menu |
The location and contents of the file are displayed.
The location for the active GRUB menu is: /boot/grub/menu.lst default 0 timeout 10 0 Solaris 1 Solaris failsafe 2 second_disk 3 second_disk failsafe |
In the following procedure, the system contains two operating systems: Solaris and a Solaris Live Upgrade boot environment, second_disk. In this situation, the menu.lst file does not exist in the currently running boot environment. The second_disk boot environment has been booted. The Solaris boot environment contains the GRUB menu. The Solaris boot environment is not mounted.
Become superuser or assume an equivalent role.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
To locate the menu.lst file, type:
# /sbin/bootadm list-menu |
The location and contents of the file are displayed.
The location for the active GRUB menu is: /dev/dsk/device_name(not mounted) The filesystem type of the menu device is <ufs> default 0 timeout 10 0 Solaris 1 Solaris failsafe 2 second_disk 3 second_disk failsafe |
Because the file system containing the menu.lst file is not mounted, mount the file system. Specify the UFS file system and the device name.
# /usr/sbin/mount -F ufs /dev/dsk/device_name /mnt |
Where device_name specifies the location of the root (/) file system on the disk device of the boot environment that you want to mount. The device name is entered in the form of /dev/dsk/cwtxdysz. For example:
# /usr/sbin/mount -F ufs /dev/dsk/c0t1d0s0 /mnt |
You can access the GRUB menu at /mnt/boot/grub/menu.lst
Unmount the filesystem
# /usr/sbin/umount /mnt |
If you mount a boot environment or a file system of a boot environment, ensure that the file system or file systems are unmounted after use. If these file systems are not unmounted, future Solaris Live Upgrade operations on that boot environment might fail.
In the following procedure, the system contains two operating systems: Solaris and a Solaris Live Upgrade boot environment, second_disk. The second_disk boot environment has been booted. The Solaris boot environment contains the GRUB menu. The Solaris boot environment is mounted at /.alt.Solaris.
Become superuser or assume an equivalent role.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
To locate the menu.lst file, type:
# /sbin/bootadm list-menu |
The location and contents of the file are displayed.
The location for the active GRUB menu is: /.alt.Solaris/boot/grub/menu.lst default 0 timeout 10 0 Solaris 1 Solaris failsafe 2 second_disk 3 second_disk failsafe |
Since the boot environment containing the GRUB menu is already mounted, then you can access the menu.lst file at /.alt.Solaris/boot/grub/menu.lst.
In the following procedure, the system contains two operating systems: Solaris and a Solaris Live Upgrade boot environment, second_disk. The second_disk boot environment has been booted. Your system has been upgraded and an x86 boot partition remains. The boot partition is mounted at /stubboot and contains the GRUB menu. For an explanation of x86 boot partitions, see x86: Partitioning Recommendations.
Become superuser or assume an equivalent role.
Roles contain authorizations and privileged commands. For more information about roles, see Configuring RBAC (Task Map) in System Administration Guide: Security Services.
To locate the menu.lst file, type:
# /sbin/bootadm list-menu |
The location and contents of the file are displayed.
The location for the active GRUB menu is: /stubboot/boot/grub/menu.lst default 0 timeout 10 0 Solaris 1 Solaris failsafe 2 second_disk 3 second_disk failsafe |
You can access the menu.lst file at /stubboot/boot/grub/menu.lst.
This chapter contains checklists to help you gather all of the information that you need to install or upgrade your system.
Use the following checklist to gather the information that you need to install the Solaris OS. You do not need to gather all of the information that is requested on the worksheet. You only need to collect the information that applies to your system.
Table 5–1 Installation Checklist
Information for Installation |
Description or Example |
Answer — Defaults are noted with an asterisk (*) |
||
---|---|---|---|---|
Network connection |
Is the system connected to a network? |
Networked/Non-networked |
||
DHCP |
Can the system use Dynamic Host Configuration Protocol (DHCP) to configure its network interfaces? DHCP provides the network parameters that are necessary for installation. |
Yes/No* |
||
If you are not using DHCP, note the network address. |
IP Address |
If you are not using DHCP, supply the IP address for the system. Example: 172.31.255.255 To find this information on a running system, type the following command.
| ||
Subnet |
If you are not using DHCP, is the system part of a subnet? If yes, what is the netmask of the subnet? Example: 255.255.255.0 To find this information on a running system, type the following command.
| |||
IPv6 |
Do you want to enable IPv6 on this machine? IPv6 is a part of the TCP/IP Internet protocol that facilitates IP addressing by adding better security and increasing Internet addresses. |
Yes/No* |
||
Host Name |
Host name that you choose for the system. To find this information on a running system, type the following command.
| |||
Kerberos |
Do you want to configure Kerberos security on this machine? |
Yes/No* |
||
Default Realm: Administration Server: First KDC: (Optional) Additional KDCs: | ||||
The Kerberos service is a client-server architecture that provides secure transactions over networks. | ||||
If the system uses a name service, provide the following information. |
Name Service |
Which name service should this system use? To find this information on a running system, type the following command.
A naming service stores information in a central place, which enables users, machines, and applications to communicate across the network. Examples of information that is stored are host names and addresses or user names and passwords. |
NIS+/NIS/DNS/ LDAP/None |
|
Domain Name |
Provide the name of the domain in which the system resides. To find this information on a running system, type the following command.
| |||
NIS+ and NIS |
Do you want to specify a name server or let the installation program find one? If you want to specify a name server, provide the following information. |
Specify One/Find One* |
||
Server's host name: | ||||
| ||||
Server's IP Address: | ||||
Network Information Service (NIS) makes network administration more manageable by providing centralized control over a variety of network information, such as machine names and addresses. | ||||
DNS |
Provide IP addresses for the DNS server. You must enter at least one IP address, but you can enter up to three addresses. | |||
Server's IP Address: | ||||
To display the server's IP address, type the following command.
| ||||
You can enter a list of domains to search when a DNS query is made. | ||||
Search Domain: Search Domain: Search Domain: | ||||
The domain name system (DNS) is the name service that the Internet provides for TCP/IP networks. DNS provides host names to the IP address service. DNS simplifies communication by using machine names instead of numerical IP addresses. DNS also serves as a database for mail administration. | ||||
LDAP |
Provide the following information about your LDAP profile. | |||
Profile Name: | ||||
Profile Server: | ||||
If you specify a proxy credential level in your LDAP profile, gather this information. | ||||
Proxy-bind distinguished name: | ||||
Proxy-bind password: | ||||
Lightweight Directory Access Protocol (LDAP) defines a relatively simple protocol for updating and searching directories that are running over TCP/IP. | ||||
Default Route |
Do you want to specify a default route IP address or let the Solaris installation program find one? The default route provides a bridge that forwards traffic between two physical networks. An IP address is a unique number that identifies each host on a network. You have the following choices:
|
Detect one*/Specify one/None |
||
Time Zone |
How do you want to specify your default time zone? |
Geographic region* Offset from GMT Time zone file |
||
Root Password |
Provide the root password for the system. | |||
Locales |
For which geographic regions do you want to install support? | |||
SPARC: Power Management (only available on SPARC systems that support Power Management) |
Do you want to use Power Management? Note – If your system has Energy Star version 3 or later, you are not prompted for this information. |
Yes*/No |
||
Automatic reboot or CD/DVD ejection |
Reboot automatically after software installation? Eject CD/DVD automatically after software installation? |
Yes*/No Yes*/No |
||
Default or Custom Install |
Do you want to perform a default installation, or customize the installation?
Note – The text installer does not prompt you to select a Default or Custom Installation. To perform a default installation, accept the default values that are provided in the text installer. To perform a custom installation, edit the values in the text installer screens. |
Default installation*/Custom installation |
||
Software Group |
Which Solaris Software Group do you want to install? |
Entire Plus OEM Entire* Developer End User Core Reduced Networking |
||
Custom Package Selection |
Do you want to add or remove software packages from the Solaris Software Group that you install? Note – When you select which packages to add or remove, you need to know about software dependencies and how Solaris software is packaged. | |||
Select Disks |
On which disks do you want to install the Solaris software? Example: c0t0d0 | |||
x86: fdisk partitioning |
Do you want to create, delete, or modify a Solaris fdisk partition? Each disk that is selected for file system layout must have a Solaris fdisk partition. If your system currently has a service partition, the Solaris installation program preserves the service partition by default. If you do not want to preserve the service partition, you must customize the fdisk partitions. For more information about preserving a service partition, see Default Boot-Disk Partition Layout Preserves the Service Partition. | |||
Select Disks for fdisk Partition Customization? |
Yes/No* |
|||
Customize fdisk partitions? |
Yes/No* |
|||
Preserve Data |
Do you want to preserve any data that exists on the disks where you are installing the Solaris software? |
Yes/No* |
||
Auto-layout File Systems |
Do you want the installation program to automatically lay out file systems on your disks? If yes, which file systems should be used for auto-layout? Example: /, /opt, /var If no, you must provide file system configuration information. Note – The Solaris installation GUI lays out file systems automatically by default. |
Yes*/No |
||
Mount Remote File Systems |
Does this system need to access software on another file system? If yes, provide the following information about the remote file system. |
Yes/No* |
||
Server: | ||||
IP Address: | ||||
Remote File System: | ||||
Local Mount Point: | ||||
If you are installing through a tip line, follow these instructions. |
Ensure that your window display is at least 80 columns wide and 24 rows long. For more information, see tip(1). To determine the current dimensions of your tip window, use the stty command. For more information, see the man page, stty(1). | |||
Check your Ethernet connection. |
If the system is part of a network, verify that an Ethernet connector or similar network adapter is connected to your system. | |||
Review the planning chapter and other relevant documentation. |
|
Use the following checklist to gather the information that you need to upgrade the Solaris OS. You do not need to gather all of the information that is requested on the checklist. You only need to collect the information that applies to your system. If you are performing the upgrade over the network, the installation program provides the information for you, based on the current system configuration.
You cannot change basic system identification, such as host name or IP address. The installation program might prompt you for basic system identification, but you must enter the original values. If you use the Solaris installation program to upgrade, the upgrade fails if you attempt to change any of the values.
Table 5–2 Upgrade Checklist
Information for Upgrade |
Description or Example |
Answer – Defaults are noted with an asterisk (*) |
|||
---|---|---|---|---|---|
Network connection |
Is the system connected to a network? |
Networked/Nonnetworked |
|||
DHCP |
Can the system use Dynamic Host Configuration Protocol (DHCP) to configure its network interfaces? DHCP provides the network parameters that are necessary for installation. |
Yes/No* |
|||
If you are not using DHCP, note the network address. |
IP Address |
If you are not using DHCP, supply the IP address for the system. Example: 172.31.255.255 To find this information on a running system, type the following command.
| |||
Subnet |
If you are not using DHCP, is the system part of a subnet? If yes, what is the netmask of the subnet? Example: 255.255.255.0 To find this information on a running system, type the following command.
| ||||
IPv6 |
Do you want to enable IPv6 on this machine? IPv6 is a part of the TCP/IP Internet protocol that facilitates IP addressing by adding better security and increasing Internet addresses. |
Yes/No* |
|||
Host Name |
Host name that you choose for the system. To find this information on a running system, type the following command.
| ||||
Kerberos |
Do you want to configure Kerberos security on this machine? |
Yes/No* |
|||
Default Realm: Administration Server: First KDC: (Optional) Additional KDCs: | |||||
The Kerberos service is a client-server architecture that provides secure transactions over networks. | |||||
If the system uses a name service, provide the following information. |
Name Service |
Which name service should this system use? To find this information on a running system, type the following command.
A naming service stores information in a central place, which enables users, machines, and applications to communicate across the network. Examples of information that is stored are host names and addresses or user names and passwords. |
NIS+/NIS/DNS/ LDAP/None |
||
Domain Name |
Provide the name of the domain in which the system resides. To find this information on a running system, type the following command.
| ||||
NIS+ and NIS |
Do you want to specify a name server or let the installation program find one? If you want to specify a name server, provide the following information. |
Specify one/Find one* |
|||
Server's host name: | |||||
| |||||
Server's IP Address: | |||||
Network Information Service (NIS) makes network administration more manageable by providing centralized control over a variety of network information, such as machine names and addresses. | |||||
DNS |
Provide IP addresses for the DNS server. You must enter at least one IP address, but you can enter up to three addresses. | ||||
Server's IP Address: | |||||
To display the server's IP address, type the following command.
| |||||
You can enter a list of domains to search when a DNS query is made. | |||||
Search Domain: Search Domain: Search Domain: | |||||
The domain name system (DNS) is the name service that the Internet provides for TCP/IP networks. DNS provides host names to the IP address service. DNS simplifies communication by using machine names instead of numerical IP addresses. DNS also serves as a database for mail administration. | |||||
LDAP |
Provide the following information about your LDAP profile. | ||||
Profile Name: | |||||
Profile Server: | |||||
If you specify a proxy credential level in your LDAP profile, gather this information. | |||||
Proxy-bind distinguished name: | |||||
Proxy-bind password: | |||||
Lightweight Directory Access Protocol (LDAP) defines a relatively simple protocol for updating and searching directories that are running over TCP/IP. | |||||
Default Route |
Do you want to specify a default route IP address or let the Solaris installation program find one? The default route provides a bridge that forwards traffic between two physical networks. An IP address is a unique number that identifies each host on a network. You have the following choices:
|
Detect one*/Specify one/None |
|||
Time Zone |
How do you want to specify your default time zone? |
Geographic region* Offset from GMT Time zone file |
|||
Root Password |
Provide the root password for the system. | ||||
Upgrading a system with non-global zones |
Starting with the Solaris 10 1/06 release, you can use the Solaris 10 DVD or a DVD-based network installation image to upgrade a system that has non-global zones installed. If you choose to upgrade a system with non-global zones installed, you cannot customize your upgrade. Note – In the Solaris 10 1/06 release, you cannot upgrade a system with non-global zones installed with the Solaris 10 Software - 1 CD or the Solaris Live Upgrade installation method. If your system has more than one root (/) partition or disk, the installation program prompts you to select a root partition to upgrade. |
Yes/No |
|||
Root (/) to upgrade: | |||||
Default or Custom Install |
Do you want to perform a default installation, or customize the installation?
Note – The text installer does not prompt you to select a Default or Custom Installation. To perform a default installation, accept the default values that are provided in the text installer. To perform a custom installation, edit the values in the text installer screens. |
Default installation*/Custom installation |
|||
Locales |
For which geographic regions do you want to install support? | ||||
SPARC: Power Management (only available on SPARC systems that support Power Management) |
Do you want to use Power Management? Note – If your system has Energy Star version 3 or later, you are not prompted for this information. |
Yes/No |
|||
Automatic reboot or CD/DVD ejection |
Reboot automatically after software installation? Eject CD/DVD automatically after software installation? |
Yes*/No Yes*/No |
|||
Disk space reallocation |
Do you want the installation program to automatically re-layout the systems on your disks? If yes, which file system should be used for auto-layout? Example: /, /opt, /var If no, you must provide information for the system configuration. |
Yes/No* |
|||
If you are installing through a tip line, follow these instructions. |
Ensure that your window display is at least 80 columns wide and 24 rows long. For more information, see tip(1). To determine the current dimensions of your tip window, use the stty command. For more information, see the man page, stty(1). | ||||
Check your Ethernet connection. |
If the system is part of a network, verify that an Ethernet connector or similar network adapter is connected to your system. | ||||
Solaris Live Upgrade use |
| ||||
Check the system for the existence of Prestoserve software. |
If you begin the upgrade process by shutting down the system with the init 0 command and you're using Prestoserve software, you might lose data. Refer to the Prestoserve documentation for shutdown instructions. | ||||
Check for patches needed. |
The most recent patch list is provided at http://sunsolve.sun.com. | ||||
Review the planning chapter and other relevant documentation. |
|
This chapter describes how to preconfigure system information. Preconfiguration can help you to avoid being prompted for this information when you install the Solaris OS. This chapter also describes how to preconfigure Power ManagementTM information. This chapter contains the following sections:
Advantages of Preconfiguring System Configuration Information
Preconfiguring System Configuration Information With the DHCP Service (Tasks)
The installation methods require configuration information about a system, such as peripheral devices, host name, Internet Protocol (IP) address, and name service. Before the installation tools prompt you for configuration information, they check for the information in the sysidcfg file and then in the name service databases.
When the Solaris installation program or the custom JumpStart installation program detects preconfigured system information, the installation program does not prompt you to enter the information. For example, you have several systems and you do not want a time zone prompt every time you install the Solaris 10 software on one of the systems. You can specify the time zone in the sysidcfg file or the name service databases. When you install the Solaris 10 software, the installation program does not prompt you to type a time zone.
You can choose one of the following ways to preconfigure system configuration information. You can add the system configuration information to either of the following.
A sysidcfg file on a remote system or diskette
The name service database available at your site
If your site uses DHCP, you can also preconfigure some system information in the site DHCP server. For more information about how to use a DHCP server to preconfigure system information, see Preconfiguring System Configuration Information With the DHCP Service (Tasks).
Use the following table to determine whether to use a sysidcfg file or a name service database to preconfigure system configuration information.
Table 6–1 Methods to Preconfigure System Configuration Information
Preconfigurable System Information | ||
---|---|---|
Yes |
Yes |
|
Yes |
No |
|
Yes |
No |
|
Yes |
No |
|
Yes Because this information is system specific, edit the name service rather than create a different sysidcfg file for each system. |
Yes |
|
Yes Because this information is system specific, edit the name service rather than create a different sysidcfg file for each system. |
Yes |
|
Yes |
No |
|
Yes |
No |
|
Yes |
No |
|
Yes |
No |
|
Yes |
No |
|
Yes |
No |
|
Language (locale) in which to display the install program and desktop |
Yes |
Yes, if NIS or NIS+ No, if DNS or LDAP |
Yes |
No |
|
Yes |
Yes |
|
Yes |
Yes |
|
No You can configure this information with the Solaris installation program, but not through the sysidcfg file or the name service. |
No |
|
Yes |
No |
|
Yes |
No |
|
x86: Graphics card, color depth, display resolution, screen size |
Yes |
No |
Yes |
No |
|
SPARC: Power Management (autoshutdown) You cannot preconfigure Power Management through the sysidcfg file or the name service. SPARC: Preconfiguring Power Management Information contains details. |
No |
No |
You can specify a set of keywords in the sysidcfg file to preconfigure a system. The keywords are described in sysidcfg File Keywords.
You must create a unique sysidcfg file for every system that requires different configuration information. You can use the same sysidcfg file to preconfigure the time zone on a set of systems if you want all the systems to be assigned the same time zone. However, if you want to preconfigure a different root (superuser) password for each of those systems, you need to create a unique sysidcfg file for each system.
You can place the sysidcfg file in one of the following.
NFS file system – If you put the sysidcfg file in a shared NFS file system, you must use the -p option of the add_install_client(1M) command when you set up the system to install from the network. The -p option specifies where the system can find the sysidcfg file when you install the Solaris 10 software.
UFS or PCFS diskette – Place the sysidcfg file in the root (/) directory on the diskette.
HTTP or HTTPS server – If you want to perform a WAN boot installation, place the sysidcfg file in the document root directory of the web server.
If you are performing a custom JumpStart installation and you want to use a sysidcfg file on a diskette, you must place the sysidcfg file on the profile diskette. To create a profile diskette, see Creating a Profile Diskette for Standalone Systems in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.
You can place only one sysidcfg file in a directory or on a diskette. If you are creating more than one sysidcfg file, you must place each file in a different directory or on a different diskette.
You can use two types of keywords in the sysidcfg file: independent and dependent. Dependent keywords are guaranteed to be unique only within independent keywords. A dependent keyword exists only when it is identified with its associated independent keyword.
In this example, name_service is the independent keyword, while domain_name and name_server are the dependent keywords:
name_service=NIS {domain_name=marquee.central.example.com name_server=connor(192.168.112.3)} |
Table 6–2 lists the keywords you can use to configure system information in the sysidcfg file.
Table 6–2 Keywords You Can Use in sysidcfg
Configuration Information |
Keyword |
---|---|
Name service, domain name, name server | |
Network interface, host name, Internet Protocol (IP) address, netmask, DHCP, IPv6 | |
Root password | |
Security policy | |
Language in which to display the install program and desktop | |
Terminal type | |
Time zone | |
Date and time | |
x86: Monitor type | |
x86: Keyboard language, keyboard layout | |
x86: Graphics card, screen size, color depth, display resolution | |
x86: Pointing device, number of buttons, IRQ level |
The following sections describe the keywords that you can use in the sysidcfg file.
You can use the name_service keyword to configure the name service, the domain name, and the name server for the system. The following sample shows the general syntax for the name_service keyword.
name_service=name-service {domain_name=domain-name name_server=name-server optional-keyword=value} |
Choose only one value for name_service. Include all or none of the domain_name,name_server, or optional keywords, as needed. If no keywords are used, omit the curly braces {}.
The following sections describe the keyword syntax to configure the system to use a specific name service.
Use the following syntax to configure the system to use the NIS name service.
name_service=NIS {domain_name=domain-name name_server=hostname(ip-address)} |
Specifies the domain name
Specifies the host name of the name server
Specifies the IP address of the name server
The following example specifies a NIS server with the domain name west.example.com. The server'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)} |
For more information about the NIS name service, see System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).
Use the following syntax to configure the system to use the NIS name service.
name_service=NIS+ {domain_name=domain-name name_server=hostname(ip-address)} |
Specifies the domain name
Specifies the host name of the name server
Specifies the IP address of the name server
The following example specifies a NIS+ server with the domain name west.example.com. The server'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)} |
For more information about the NIS+ name service, see System Administration Guide: Naming and Directory Services (NIS+).
Use the following syntax to configure the system to use DNS.
name_service=DNS {domain_name=domain-name name_server=ip-address,ip-address,ip-address search=domain-name,domain-name,domain-name, domain-name,domain-name,domain-name} |
Specifies the domain name.
Specifies the IP address of the DNS server. You can specify up to three IP addresses as values for the name_server keyword.
(Optional) Specifies additional domains to search for name service information. You can specify up to six domain names to search. The total length of each search entry cannot exceed 250 characters.
The following example specifies a DNS server with the domain name west.example.com. The server IP addresses are 10.0.1.10 and 10.0.1.20. example.com and east.example.com are listed as additional domains to search for name service information.
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 information about the DNS name service, see System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).
Use the following syntax to configure the system to use LDAP.
name_service=LDAP {domain_name=domain_name profile=profile_name profile_server=ip_address proxy_dn="proxy_bind_dn" proxy_password=password} |
Specifies the domain name of the LDAP server.
Specifies the name of the LDAP profile you want to use to configure the system.
Specifies the IP address of the LDAP profile server.
(Optional) Specifies the proxy bind distinguished name. You must enclose the proxy_bind_dn value in double quotes.
(Optional) Specifies the client proxy password.
The following example specifies an LDAP server with the following configuration information.
The domain name is west.example.com.
The installation program uses the LDAP profile that is named default to configure the system.
The IP address of the LDAP server is 172.31.2.1.
The proxy bind distinguished name includes the following information.
The common name for 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.
name_service=LDAP {domain_name=west.example.com profile=default profile_server=172.31.2.1 proxy_dn="cn=proxyagent,ou=profile, dc=west,dc=example,dc=com" proxy_password=password} |
For more information about how to use LDAP, see System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).
Use the network_interface keyword to perform the following tasks.
Specify a host name
Specify an IP address
Specify a netmask value
Use DHCP to configure the network interface
Enable IPv6 on the network interface
The following sections describe how to use the network_interface keyword to configure the system interfaces.
To turn off networking for the system, set the network_interface value to none. For example:
network_interface=none |
You can use the network_interface keyword to configure a single interface in the following ways.
With DHCP – You can use a DHCP server on your network to configure the network interface. For more information on how to use a DHCP server during your installation, see Preconfiguring System Configuration Information With the DHCP Service (Tasks).
To use the DHCP server to configure a single interface on the system, use the following syntax for the network_interface keyword.
network_interface=PRIMARY or value {dhcp protocol_ipv6=yes-or-no} |
Instructs the installation program to configure the first up, non-loopback interface that is found on the system. The order is the same as the order that is displayed with the ifconfig command. If no interfaces are up, then the first non-loopback interface is used. If no non-loopback interfaces are found, then the system is nonnetworked.
Instructs the installation program to configure a specific interface, such as hme0 or eri1.
Instructs the installation program to configure the system to either use IPv6 or to not use IPv6.
For WAN boot installations, you must set the value of protocol_ipv6=no.
Without DHCP – If you do not want to use DHCP to configure the network interface, you can specify the configuration information in the sysidcfg file. To instruct the installation program to configure a single interface on the system without using DHCP, use the following syntax.
network_interface=PRIMARY or value {hostname=host_name default_route=ip_address ip_address=ip_address netmask=netmask protocol_ipv6=yes_or_no} |
Instructs the installation program to configure the first up, non-loopback interface that is found on the system. The order is the same as the order that is displayed with the ifconfig command. If no interfaces are up, then the first non-loopback interface is used. If no non-loopback interfaces are found, then the system is not networked.
Do not use the PRIMARY keyword value if you want to configure multiple interfaces.
Instructs the installation program to configure a specific interface, such as hme0 or eri1.
(Optional) Specifies the host name of the system.
(Optional) Specifies the IP address of the default router. If you want the installation program to detect the router by using the ICMP router discovery protocol, omit this keyword.
If the installation program cannot detect the router, you are prompted for the router information during the installation.
(Optional) Specifies the IP address of the system.
(Optional) Specifies the netmask value for the system.
(Optional) Instructs the installation program to configure the system to either use IPv6 or to not use IPv6.
To perform an unattended custom JumpStart installation, you must specify a value for the protocol_ipv6 keyword.
For WAN boot installations, you must set the value of protocol_ipv6=no.
Include any combination or none of the hostname, ip_address, and netmask keywords, as needed. If you do not use any of these keywords, omit the curly braces ({}).
The following example instructs the installation program to use DHCP to configure the eri0 network interface. IPv6 support is not enabled.
network_interface=eri0 {dhcp protocol_ipv6=no} |
The following example configures the interface eri0 with the following 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.
IPv6 support is not enabled on the interface.
network_interface=eri0 {hostname=host1 ip_address=172.31.88.100 netmask=255.255.255.0 protocol_ipv6=no} |
You can configure multiple network interfaces in your sysidcfg file. For each interface that you want to configure, include a network_interface entry in the sysidcfg file.
You can use the network_interface keyword to configure multiple interfaces in the following ways.
With DHCP – You can use a DHCP server on your network to configure a network interface. For more information on how to use a DHCP server during your installation, see Preconfiguring System Configuration Information With the DHCP Service (Tasks).
To use the DHCP server to configure a network interface on the system, use the following syntax for the network_interface keyword.
network_interface=value {primary dhcp protocol_ipv6=yes-or-no} |
Instructs the installation program to configure a specific interface, such as hme0 or eri1.
(Optional) Specifies value as the primary interface.
Instructs the installation program to configure the system to either use IPv6 or to not use IPv6.
For WAN boot installations, you must set the value of protocol_ipv6=no.
Without DHCP – If you do not want to use DHCP to configure the network interface, you can specify the configuration information in the sysidcfg file. To instruct the installation program to configure multiple interfaces without using DHCP, use the following syntax.
network_interface=value {primary hostname=host_name default_route=ip_address or NONE ip_address=ip_address netmask=netmask protocol_ipv6=yes_or_no} |
Instructs the installation program to configure a specific interface, such as hme0 or eri1.
(Optional) Specifies value as the primary interface.
(Optional) Specifies the host name of the system.
(Optional) Specifies the IP address of the default router. If you want the installation program to detect the router by using the ICMP router discovery protocol, omit this keyword.
If you configure multiple interfaces in the sysidcfg file, set default_route=NONE for each secondary interface that does not use a static default route.
If the installation program cannot detect the router, you are prompted for the router information during the installation.
(Optional) Specifies the IP address of the system.
(Optional) Specifies the netmask value for the system.
(Optional) Instructs the installation program to configure the system to either use IPv6 or to not use IPv6.
To perform an unattended custom JumpStart installation, you must specify a value for the protocol_ipv6 keyword.
For WAN boot installations, you must set the value of protocol_ipv6=no.
Include any combination or none of the hostname, ip_address, and netmask keywords, as needed. If you do not use any of these keywords, omit the curly braces ({}).
In the same sysidcfg file, you can use DHCP to configure certain interfaces, while also specifying the configuration information for other interfaces in the sysidcfg file.
In the following example, the network interfaces eri0 and eri1 are configured in the following way.
eri0 is configured by using the DHCP server. IPv6 support is not enabled on eri0.
eri1 is the primary network interface. The host name is set to host1, and the IP address is set to 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.0 protocol_ipv6=no} |
You can specify the root password to the system in the sysidcfg file. To specify the root password, use the root_password keyword with the following syntax.
root_password=encrypted-password |
encrypted-password is the encrypted password as it appears in the /etc/shadow file.
You can use the security_policy keyword in your sysidcfg file to configure your system to use the Kerberos network authentication protocol. If you want to configure the system to use Kerberos, use the following syntax.
security_policy=kerberos {default_realm=FQDN admin_server=FQDN kdc=FQDN1, FQDN2, FQDN3} |
FQDN specifies the fully qualified domain name of the Kerberos default realm, the administration server, or key distribution center (KDC). You must specify at least one, but no more than three, key distribution centers.
If you do not want to set the security policy for the system, set security_policy=NONE.
For more information about the Kerberos network authentication protocol, see System Administration Guide: Security Services.
The following example configures the system to use Kerberos with the following information.
The Kerberos default 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} |
You can use the system_locale keyword to specify the language in which to display the install program and desktop. Use the following syntax to specify a locale.
system_locale=locale |
locale specifies the language that you want the system to use to display the installation panels and screens. For a list of valid locale values, see the /usr/lib/locale directory or International Language Environments Guide.
You can use the terminal keyword to specify the terminal type for the system. Use the following syntax to specify the terminal type.
terminal=terminal_type |
terminal_type specifies the terminal type for the system. For a list of valid terminal values, see the subdirectories in the /usr/share/lib/terminfo directory.
You can set the time zone for the system with the timezone keyword. Use the following syntax.
timezone=timezone |
In the previous example, timezone specifies the time zone value for the system. The directories and files in the /usr/share/lib/zoneinfo directory provide the valid time zone values. The timezone value is the name of the path relative to the /usr/share/lib/zoneinfo directory. You can also specify any valid Olson time zone.
In the following example, the system time zone is set to mountain standard time in the United States.
timezone=US/Mountain |
The installation program configures the system to use the time zone information in /usr/share/lib/zoneinfo/US/Mountain.
You can use the timeserver keyword to specify the system that sets the date and time on the system you want to install.
Do not set timeserver=hostname or ip-address if you are running a name service.
Choose one of the following methods to set the timeserver keyword.
To configure the system to serve as its own time server, set timeserver=localhost. If you specify localhost as the time server, the system's time is assumed to be correct.
To specify another system as the time server, specify either the host name or the IP address of the time server with the timeserver keyword. Use the following syntax.
timeserver=hostname or ip-address |
hostname is the host name of the time server system. ip-address specifies the IP address of the time server.
For x86 based systems, you can configure the monitor information with the monitor keyword. Use the following syntax with the monitor keyword.
monitor=monitor_type |
To set the value for the monitor keyword, run the kdmconfig -d command on the system you want to install. Copy the line of output that includes the monitor keyword, and include this line in the sysidcfg file.
For more information, see the kdmconfig(1M)
For x86 based systems, you can configure the keyboard language and layout information with the keyboard keyword. Use the following syntax with the keyboard keyword.
keyboard=keyboard_language {layout=value} |
To set the value for the keyboard keyword, run the kdmconfig -d command on the system you want to install. Copy the line of output that includes the keyboard keyword, and include this line in the sysidcfg file.
For more information, see the kdmconfig(1M)
For x86 based systems, you can configure the following information with the display keyword.
Graphics card
Screen size
Color depth
Display resolution
Use the following syntax with the display keyword.
display=graphics_card {size=screen_size depth=color_depth resolution=screen_resolution} |
To set the appropriate values for the display keyword, run the kdmconfig -d command on the system you want to install. Copy the line of output that includes the display keyword, and include this line in the sysidcfg file.
For more information, see the kdmconfig(1M)
For x86 based systems, you can configure the following mouse information with the pointer keyword.
Pointing device
Number of buttons
IRQ level
Use the following syntax with the pointer keyword.
pointer=pointing_device {nbuttons=number_buttons irq=value} |
To set the value for the pointer keyword, run the kdmconfig -d command on the system you want to install. Copy the line of output that includes the pointer keyword, and include this line in the sysidcfg file.
For more information, see the kdmconfig(1M)
Create a file called sysidcfg in a text editor.
Type the sysidcfg keywords you want.
Save the sysidcfg file.
If you create more than one sysidcfg file, you must save each file in a separate directory or on a separate diskette.
Make the sysidcfg file available to clients through the following:
A shared NFS file system. Use add_install_client(1M) with the -p option to set up the system to install from the network.
The root (/) directory on a UFS diskette or PCFS diskette.
The following is an example of a sysidcfg file for a SPARC based system. The host name, IP address, and netmask of this system has been preconfigured by editing the name service. Because all of the system configuration information is preconfigured in this file, you can use a custom JumpStart profile to perform a custom JumpStart installation.
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)} 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} |
The following sample sysidcfg file is for a group of x86 based systems that all use the same type of keyboard, graphics cards, and pointing devices. The device information (keyboard, display, and pointer) was obtained by running the kdmconfig(1M) command with the -d option. If the following example sysidcfg file is used, a prompt that asks you to select a language (system_locale) is displayed before installation can proceed.
keyboard=ATKBD {layout=US-English} display=ati {size=15-inch} pointer=MS-S timezone=US/Central timeserver=timehost1 terminal=ibm-pc name_service=NIS {domain_name=marquee.central.example.com name_server=nmsvr2(172.25.112.3)} root_password=URFUni9 |
In the following sample sysidcfg file, configuration information is specified for both the eri0 and eri1 network interfaces. The eri0 interface is configured as the primary network interface, and eri1 is configured as a secondary network interface.
timezone=US/Pacific system_locale=C terminal=xterms timeserver=localhost network_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.8 netmask=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)}
If you plan to use the sysidcfg file in an installation over the network, you need to set up an installation server and add the system as an installation client. For more information, see Chapter 7, Preparing to Install From the Network (Overview).
If you plan to use the sysidcfg file in a WAN boot installation, you need to perform additional tasks. For more information, see Chapter 11, WAN Boot (Overview).
If you plan to use the sysidcfg file in a custom JumpStart installation, you need to create a profile and a rules.ok file. For more information, see Chapter 5, Custom JumpStart (Overview), in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.
For more information about the sysidcfg file, see the man page sysidcfg(4).
The following table provides a high-level overview of the name service databases that you need to edit and populate to preconfigure system information.
System Information to Preconfigure |
Name Service Database |
---|---|
Host name and Internet Protocol (IP) address |
hosts |
Date and time |
hosts. Specify the timehost alias next to the host name of the system that will provide the date and time for the systems that are being installed. |
Time zone |
timezone |
Netmask |
netmasks |
You cannot preconfigure the locale for a system with the DNS or LDAP name service. If you use the NIS or NIS+ name service, follow the procedure for your name service to preconfigure the locale for a system:
Become superuser on the name server.
Change /var/yp/Makefile to add the locale map.
Insert this shell procedure after the last 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<=NF; i++) print $$i, $$0}' \ | $(MAKEDBM) - $(YPDBDIR)/$(DOM)/locale.byname; \ touch locale.time; \ echo "updated locale"; \ if [ ! $(NOPUSH) ]; then \ $(YPPUSH) locale.byname; \ echo "pushed locale"; \ else \ : ; \ fi \ else \ echo "couldn't find $(DIR)/locale"; \ fi |
Find the string all: and, at the end of the list of 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 |
Near the end of the file, after the last entry of its type, insert the string locale: locale.time on a new line.
passwd: passwd.time group: group.time hosts: hosts.time ethers: ethers.time networks: networks.time rpc: rpc.time services: services.time protocols: protocols.time netgroup: netgroup.time bootparams: bootparams.time aliases: aliases.time publickey: publickey.time netid: netid.time passwd.adjunct: passwd.adjunct.time group.adjunct: group.adjunct.time netmasks: netmasks.time timezone: timezone.time auto.master: auto.master.time auto.home: auto.home.time locale: locale.time |
Save the file.
Create the file /etc/locale and make one entry for each domain or specific system:
locale domain_name |
Or
locale system_name |
International Language Environments Guide contains a list of valid locales.
For example, the following entry specifies that French is the default language that is used in the example.com domain:
fr example.com |
And the following entry specifies that Belgian French is the default locale that is used by a system named myhost:
fr_BE myhost |
Locales are available on the Solaris 10 DVD or Solaris 10 Software - 1 CD.
# cd /var/yp; make |
Systems that are specified by domain or individually in the locale map are now set up to use the default locale. The default locale that you specified is used during installation and by the desktop after the system is rebooted.
If you plan to use the NIS name service in an installation over the network, you need to set up an installation server and add the system as an installation client. For more information, see Chapter 7, Preparing to Install From the Network (Overview).
If you plan to use the NIS name service in a custom JumpStart installation, you need to create a profile and a rules.ok file. For more information, see Chapter 5, Custom JumpStart (Overview), in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.
For more information about the NIS name service, see Part III, NIS Setup and Administration, in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).
The following procedure assumes the NIS+ domain is set up. Setting up the NIS+ domain is documented in the System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP).
Log in to a name server as superuser or as a user in the NIS+ administration group.
# nistbladm -D access=og=rmcd,nw=r -c locale_tbl name=SI,nogw= locale=,nogw= comment=,nogw= locale.org_dir.`nisdefaults -d` |
Add needed entries to the locale.
# nistbladm -a name=namelocale=locale comment=comment locale.org_dir.`nisdefaults -d` |
Either the domain name or a specific system name for which you want to preconfigure a default locale.
The locale you want to install on the system and use on the desktop after the system is rebooted. International Language Environments Guide contains a list of valid locales.
The comment field. Use double quotation marks to begin and end comments that are longer than one word.
Locales are available on the Solaris 10 DVD or Solaris 10 Software - 1 CD.
Systems that are specified by domain or individually in the locale table are now set up to use the default locale. The default locale you specified is used during installation and by the desktop after the system is rebooted.
If you plan to use the NIS+ name service in an installation over the network, you need to set up an installation server and add the system as an installation client. For more information, see Chapter 7, Preparing to Install From the Network (Overview).
If you plan to use the NIS+ name service in a custom JumpStart installation, you need to create a profile and a rules.ok file. For more information, see Chapter 5, Custom JumpStart (Overview), in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.
For more information about the NIS+ name service, see System Administration Guide: Naming and Directory Services (NIS+).
The Dynamic Host Configuration Protocol (DHCP) enables host systems in a TCP/IP network to be configured automatically for the network as they boot. DHCP uses a client and server mechanism. Servers store and manage configuration information for clients, and provide that information on a client's request. The information includes the client's IP address and information about network services available to the client.
A primary benefit of DHCP is its ability to manage IP address assignments through leasing. Leasing allows IP addresses to be reclaimed when not in use and reassigned to other clients. This ability enables a site to use a smaller pool of IP address than would be needed if all clients were assigned a permanent address.
You can use DHCP to install the Solaris OS on certain client systems on your network. All SPARC based systems that are supported by the Solaris OS and x86 based systems that meet the hardware requirements for running the Solaris OS can use this feature.
The following task map shows the high-level tasks that must be performed to enable clients to obtain installation parameters by using DHCP.
Table 6–3 Task Map: Preconfiguring System Configuration Information With the DHCP Service
Task |
Description |
Instructions |
---|---|---|
Set up an install server. |
Set up a Solaris server to support clients that must install the Solaris OS from the network. | |
Set up client systems for Solaris installation over the network by using DHCP. |
Use add_install_client -d to add DHCP network installation support for a class of client (of a certain machine type, for example) or a particular client ID. |
Using Solaris DVD: Adding Systems to Be Installed From the Network With a DVD Image Using Solaris CD: Adding Systems to Be Installed From the Network With a CD Image |
Prepare your network to use the DHCP service. |
Decide how you want to configure your DHCP server. |
Chapter 13, Planning for DHCP Service (Tasks), in System Administration Guide: IP Services |
Configure the DHCP server. |
Use DHCP Manager to configure your DHCP server |
Chapter 14, Configuring the DHCP Service (Tasks), in System Administration Guide: IP Services |
Create DHCP options for installation parameters and macros that include the options. |
Use DHCP Manager or dhtadm to create new Vendor options and macros that the DHCP server can use to pass installation information to the clients. |
Creating DHCP Options and Macros for Solaris Installation Parameters |
When you add clients with the add_install_client -d script on the install server, the script reports DHCP configuration information to standard output. This information can be used when you create the options and macros that are needed to pass network installation information to clients.
You can customize the options and macros in your DHCP service to perform the following types of installations.
Class-specific installations - You can instruct the DHCP service to perform a network installation for all clients of a specific class. For example, you can define a DHCP macro that performs the same installation on all Sun Blade systems on the network. Use the output of the add_install_client -d command to set up a class-specific installation.
Network-specific installations – You can instruct the DHCP service to perform a network installation for all clients in a specific network. For example, you can define a DHCP macro that performs the same installation on all systems in the 192.168.2 network.
Client-specific installations - You can instruct the DHCP service to perform a network installation for a client with a specific Ethernet address. For example, you can define a DHCP macro that performs a specific installation on the client with the Ethernet address 00:07:e9:04:4a:bf. Use the output of the add_install_client -d -e ethernet_address command to set up a client-specific installation.
For more information on setting up clients to use a DHCP server for a network installation, see the following procedures.
For network installations that use DVD media, see Adding Systems to Be Installed From the Network With a DVD Image.
For network installations that use CD media, see Adding Systems to Be Installed From the Network With a CD Image.
To install DHCP clients from the network, you must create Vendor category options to pass information that is needed to install the Solaris OS. The following tables describe common DHCP options that you can use to install a DHCP client.
Starting with the Solaris 10 1/06 release, you can use the standard DHCP options that are listed in Table 6–4 to configure and install x86 based systems. These options are not platform specific, and can be used to install the Solaris OS on a variety of x86 based systems. Use these options to install the Solaris 10 1/06 release on x86 based systems by using DHCP. For a complete list of standard options, see dhcp_inittab(4).
Table 6–5 lists options that you can use to install Sun client systems. The vendor client classes that are listed in this table determine what classes of client can use the option. Use these options to install the Solaris 10 OS on SPARC based systems, or to install the Solaris 10 3/05 release on x86 based systems. Vendor client classes that are listed here are examples only. You should specify client classes that indicate the actual clients in your network that you need to install from the network. See Working With DHCP Options (Task Map) in System Administration Guide: IP Services for information about how to determine a client's vendor client class.
For detailed information on DHCP options, see DHCP Option Information in System Administration Guide: IP Services.
Table 6–4 Values for Standard DHCP Options
Option Name |
Code |
Data Type |
Granularity |
Maximum |
Description |
---|---|---|---|---|---|
BootFile |
N/A |
ASCII |
1 |
1 |
Path to the client's boot file |
BootSrvA |
N/A |
IP address |
1 |
1 |
IP address of boot server |
DNSdmain |
15 |
ASCII |
1 |
0 |
DNS domain name |
DNSserv |
6 |
IP address |
1 |
0 |
List of DNS name servers |
NISdmain |
40 |
ASCII |
1 |
0 |
NIS domain name |
NISservs |
41 |
IP address |
1 |
0 |
IP address of NIS server |
NIS+dom |
64 |
ASCII |
1 |
0 |
NIS+ domain name |
NIS+serv |
65 |
IP address |
1 |
0 |
IP address of NIS+ server |
Router |
3 |
IP address |
1 |
0 |
IP addresses of network routers |
Table 6–5 Values for Creating Vendor Category Options for Solaris Clients
Name |
Code |
Data Type |
Granularity |
Maximum |
Vendor Client Classes * |
Description |
---|---|---|---|---|---|---|
The following Vendor category options are required to enable a DHCP server to support Solaris installation clients. The options are used in the Solaris client's startup scripts. Note – Vendor client classes that are listed here are examples only. You should specify client classes that indicate the actual clients in your network that you need to install from the network. The SUNW.i86pc vendor client class is only valid for the Solaris 10 3/05 release and compatible versions. |
||||||
SrootIP4 |
2 |
IP address |
1 |
1 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
IP address of root server |
SrootNM |
3 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Host name of root server |
SrootPTH |
4 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Path to the client's root directory on the root server |
SinstIP4 |
10 |
IP address |
1 |
1 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
IP address of JumpStart install server |
SinstNM |
11 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Host name of install server |
SinstPTH |
12 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Path to installation image on install server |
The following options can be used by the client startup scripts, but are not required by the scripts. Note – Vendor client classes that are listed here are examples only. You should specify client classes that indicate the actual clients in your network that you need to install from the network. The SUNW.i86pc vendor client class is only valid for the Solaris 10 3/05 release and compatible versions. |
||||||
SrootOpt |
1 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
NFS mount options for the client's root file system |
SbootFIL |
7 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Path to the client's boot file |
SbootRS |
9 |
NUMBER |
2 |
1 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
NFS read size used by standalone boot program when loading the kernel |
SsysidCF |
13 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Path to sysidcfg file, in the format server:/path |
SjumpsCF |
14 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Path to JumpStart configuration file in the format server:/path |
16 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Path to the standalone boot file or path to the WAN boot file. For the standalone boot file, use the following format. tftp://inetboot.sun4u For the WAN boot file, the format is http://host.domain/path-to-file This option can be used to override BootFile and siaddr settings in order to retrieve a standalone boot file. Supported protocols: tftp (inetboot), http (wanboot). For example, use the following format. tftp://inetboot.sun4u |
|
17 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
IP address and port number of the proxy server that is used on your network. This option is needed only when a client is booting across a WAN, and the local network uses a proxy server. For example, use the following format: 198.162.10.5:8080 |
|
The following options are not currently used by the Solaris client startup scripts. You can use them only if you edit the startup scripts. Note – Vendor client classes that are listed here are examples only. You should specify client classes that indicate the actual clients in your network that you need to install from the network. The SUNW.i86pc vendor client class is only valid for the Solaris 10 3/05 release and compatible versions. |
||||||
SswapIP4 |
5 |
IP address |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
IP address of swap server |
SswapPTH |
6 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Path to the client's swap file on the swap server |
Stz |
8 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Time zone for client |
Sterm |
15 |
ASCII text |
1 |
0 |
SUNW.Sun-Blade-1000, SUNW.Sun-Fire-880, SUNW.i86pc |
Terminal type |
When you have created the options, you can create macros that include those options. The following table lists sample macros you can create to support Solaris installation for clients.
Table 6–6 Sample Macros to Support Network Installation Clients
Macro Name |
Contains These Options and Macros |
---|---|
Solaris |
SrootIP4, SrootNM, SinstIP4, SinstNM |
sparc |
SrootPTH, SinstPTH |
sun4u |
Solaris and sparc macros |
sun4v |
Solaris and sparc macros |
i86pc |
Solaris macro, SrootPTH, SinstPTH, SbootFIL |
SUNW.i86pc |
i86pc macro Note – The SUNW.i86pc vendor client class is only valid for the Solaris 10 3/05 release and compatible versions. |
SUNW.Sun-Blade-1000 |
sun4u macro, SbootFIL |
SUNW.Sun-Fire-880 |
sun4u macro, SbootFIL |
PXEClient:Arch:00000:UNDI:002001 |
BootSrvA, BootFile |
xxx.xxx.xxx.xxx network address macros |
BootSrvA option could be added to existing network address macros. The value of BootSrvA should indicate the tftboot server. |
01client-MAC-address client-specific macros (for example, 010007E9044ABF) |
BootSrvA, BootFile |
The macro names that are listed in the previous table match the Vendor client classes of the clients that must install from the network. These names are examples of clients you might have on your network. See Working With DHCP Options (Task Map) in System Administration Guide: IP Services for information about determining a client's vendor client class.
You can create these options and macros by using the following methods.
Create the options and macros in DHCP Manager. See Using DHCP Manager to Create Install Options and Macros for instructions about how to create options and macros in DHCP Manager.
Write a script that creates the options and macros by using the dhtadm command. See Writing a Script That Uses dhtadm to Create Options and Macros for information bout how to write scripts that create these options and macros.
Note that the total size of the vendor options that are provided to a particular client must not exceed 255 bytes, including the option codes and length information. This is a limitation of the current Solaris DHCP protocol implementation. Generally, you should pass the minimum amount of vendor information needed. You should use short path names in options that require path names. If you create symbolic links to long paths, you can use the shorter link names.
You can use DHCP Manager to create the options that are listed in Table 6–5 and the macros that are listed in Table 6–6.
Perform the following tasks before you create DHCP macros for your installation.
Add the clients that you want to install with DHCP as install clients of your network installation server. For information about how to add a client to an install server, see Chapter 7, Preparing to Install From the Network (Overview).
Configure your DHCP server. If you have not configured your DHCP server, see Chapter 13, Planning for DHCP Service (Tasks), in System Administration Guide: IP Services.
Become superuser on the DHCP server system.
Start the DHCP Manager.
# /usr/sadm/admin/bin/dhcpmgr & |
The DHCP Manager window is displayed.
Select the Options tab in DHCP Manager.
Choose Create from the Edit menu.
The Create Option dialog box opens.
Type the option name for the first option, then type values appropriate for that option.
Use the output of the add_install_client command , Table 6–4, and Table 6–5 to check the option names and values for options you must create. Notice that the vendor client classes are only suggested values. You should create classes to indicate the actual client types that need to obtain Solaris installation parameters from the DHCP service. See Working With DHCP Options (Task Map) in System Administration Guide: IP Services for information about how to determine a client's vendor client class.
Click OK when you have entered all the values.
In the Options tab, select the option you just created.
Select Duplicate from the Edit menu.
The Duplicate Option dialog box opens.
Type the name of another option, then modify other values appropriately.
The values for code, data type, granularity, and maximum are most likely to need modification. See Table 6–4 and Table 6–5 for the values.
Repeat Step 7 through Step 9 until you have created all the options.
You can now create macros to pass the options to network installation clients, as explained in the following procedure.
You do not need to add these options to a Solaris client's /etc/dhcp/inittab file because they are already included in that file.
Perform the following tasks before you create DHCP macros for your installation.
Add the clients that you want to install with DHCP as install clients of your network installation server. For information about how to add a client to an install server, see Chapter 7, Preparing to Install From the Network (Overview).
Configure your DHCP server. If you have not configured your DHCP server, see Chapter 13, Planning for DHCP Service (Tasks), in System Administration Guide: IP Services.
Create the DHCP options that you want to use in your macro. For instructions about how to create DHCP options, see How to Create Options to Support Solaris Installation (DHCP Manager).
Select the Macros tab in DHCP Manager.
Choose Create from the Edit menu.
The Create Macro dialog box opens.
Type the name of a macro.
See Table 6–6 for macro names you might use.
Click the Select button.
The Select Option dialog box opens.
Select Vendor in the Category list.
The Vendor options you created are listed.
Select an option you want to add to the macro and click OK.
Type a value for the option.
See Table 6–4 and Table 6–5 for the option's data type and refer to the information that add_install_client -d reports.
Repeat Step 6 through Step 7 for each option you want to include.
To include another macro, type Include as the option name and type the macro name as the option value.
Click OK when the macro is complete.
If you plan to use DHCP in an installation over the network, you need to set up an installation server and add the system as an installation client. For more information, see Chapter 7, Preparing to Install From the Network (Overview).
If you plan to use DHCP in a WAN boot installation, you need to perform additional tasks. For more information, see Chapter 11, WAN Boot (Overview).
If you plan to use DHCP in a custom JumpStart installation, you need to create a profile and a rules.ok file. For more information, see Chapter 5, Custom JumpStart (Overview), in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.
For more information about DHCP, see Part III, DHCP, in System Administration Guide: IP Services.
You can create a Korn shell script by adapting the example in Example 6–13 to create all the options listed in Table 6–4 and Table 6–5 and some useful macros. Be sure to change all IP addresses and values contained in quotes to the correct IP addresses, server names, and paths for your network. You should also edit the Vendor= key to indicate the class of clients you have. Use the information that add_install_client -d reports to obtain the data that you need to adapt the script.
# Load the Solaris vendor specific options. We'll start out supporting # the Sun-Blade-1000, Sun-Fire-880, and i86 platforms. Note that the # SUNW.i86pc option only applies for the Solaris 10 3/05 release. # Changing -A to -M would replace the current values, rather than add them. dhtadm -A -s SrootOpt -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,1,ASCII,1,0' dhtadm -A -s SrootIP4 -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,2,IP,1,1' dhtadm -A -s SrootNM -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,3,ASCII,1,0' dhtadm -A -s SrootPTH -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,4,ASCII,1,0' dhtadm -A -s SswapIP4 -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,5,IP,1,0' dhtadm -A -s SswapPTH -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,6,ASCII,1,0' dhtadm -A -s SbootFIL -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,7,ASCII,1,0' dhtadm -A -s Stz -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,8,ASCII,1,0' dhtadm -A -s SbootRS -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,9,NUMBER,2,1' dhtadm -A -s SinstIP4 -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,10,IP,1,1' dhtadm -A -s SinstNM -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,11,ASCII,1,0' dhtadm -A -s SinstPTH -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,12,ASCII,1,0' dhtadm -A -s SsysidCF -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,13,ASCII,1,0' dhtadm -A -s SjumpsCF -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,14,ASCII,1,0' dhtadm -A -s Sterm -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,15,ASCII,1,0' dhtadm -A -s SbootURI -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,16,ASCII,1,0' dhtadm -A -s SHTTPproxy -d \ 'Vendor=SUNW.Sun-Blade-1000 SUNW.Sun-Fire-880 SUNW.i86pc,17,ASCII,1,0' # Load some useful Macro definitions. # Define all Solaris-generic options under this macro named Solaris. dhtadm -A -m Solaris -d \ ':SrootIP4=10.21.0.2:SrootNM="blue2":SinstIP4=10.21.0.2:SinstNM="red5":' # Define all sparc-platform specific options under this macro named sparc. dhtadm -A -m sparc -d \ ':SrootPTH="/export/sparc/root":SinstPTH="/export/sparc/install":' # Define all sun4u architecture-specific options under this macro named sun4u. # (Includes Solaris and sparc macros.) dhtadm -A -m sun4u -d ':Include=Solaris:Include=sparc:' # Solaris on IA32-platform-specific parameters are under this macro named i86pc. # Note that this macro applies only for the Solaris 10 3/05 release. dhtadm -A -m i86pc -d \ ':Include=Solaris:SrootPTH="/export/i86pc/root":SinstPTH="/export/i86pc/install"\ :SbootFIL="/platform/i86pc/kernel/unix":' # Solaris on IA32 machines are identified by the "SUNW.i86pc" class. All # clients identifying themselves as members of this class will see these # parameters in the macro called SUNW.i86pc, which includes the i86pc macro. # Note that this class only applies for the Solaris 10 3/05 release. dhtadm -A -m SUNW.i86pc -d ':Include=i86pc:' # Sun-Blade-1000 platforms identify themselves as part of the # "SUNW.Sun-Blade-1000" class. # All clients identifying themselves as members of this class # will see these parameters. dhtadm -A -m SUNW.Sun-Blade-1000 -d \ ':SbootFIL="/platform/sun4u/kernel/sparcv9/unix":\ Include=sun4u:' # Sun-Fire-880 platforms identify themselves as part of the "SUNW.Sun-Fire-880" class. # All clients identifying themselves as members of this class will see these parameters. dhtadm -A -m SUNW.Sun-Fire-880 -d \ ':SbootFIL="/platform/sun4u/kernel/sparcv9/unix":Include=sun4u:' # Add our boot server IP to each of the network macros for our topology served by our # DHCP server. Our boot server happens to be the same machine running our DHCP server. dhtadm -M -m 10.20.64.64 -e BootSrvA=10.21.0.2 dhtadm -M -m 10.20.64.0 -e BootSrvA=10.21.0.2 dhtadm -M -m 10.20.64.128 -e BootSrvA=10.21.0.2 dhtadm -M -m 10.21.0.0 -e BootSrvA=10.21.0.2 dhtadm -M -m 10.22.0.0 -e BootSrvA=10.21.0.2 # Make sure we return host names to our clients. dhtadm -M -m DHCP-servername -e Hostname=_NULL_VALUE_ # Create a macro for PXE clients that want to boot from our boot server. # Note that this macro applies for the Solaris 10 3/05 release. dhtadm -A -m PXEClient:Arch:00000:UNDI:002001 -d \ :BootFile=nbp.i86pc:BootSrvA=10.21.0.2: # Create a macro for PXE clients that want to boot from our boot server. # Note that this macro applies for the Solaris 10 2/06 release. dhtadm -A -m PXEClient:Arch:00000:UNDI:002001 -d \ :BootFile=i86pc:BootSrvA=10.21.0.2: # Create a macro for the x86 based client with the Ethernet address 00:07:e9:04:4a:bf # to install from the network by using PXE. dhtadm -A -m 010007E9044ABF -d :BootFile=010007E9044ABF:BootSrvA=10.21.0.2: # The client with this MAC address is a diskless client. Override the root settings # which at the network scope setup for Install with our client's root directory. dhtadm -A -m 0800201AC25E -d \ ':SrootIP4=10.23.128.2:SrootNM="orange-svr-2":SrootPTH="/export/root/10.23.128.12":' |
As superuser, execute dhtadm in batch mode. Specify the name of the script to add the options and macros to your dhcptab. For example, if your script is named netinstalloptions, type the following command.
# dhtadm -B netinstalloptions |
Clients that have vendor client classes that are listed in the Vendor= string can now use DHCP to install over the network.
For more information about how to use the dhtadm command, see dhtadm(1M). For more information about the dhcptab file, see dhcptab(4).
You can use the Power Management software that is provided in the Solaris OS to automatically save the state of a system and turn it off after it is idle for 30 minutes. When you install the Solaris 10 OS on a system that complies with version 2 of the EPA's Energy Star guidelines, for example a sun4u system, the Power Management software is installed by default. If you install with the Solaris installation program GUI, the installation program prompts you to enable or disable the Power Management software. The Solaris text installer prompts you to enable or disable the Power Management software after the installation is complete and the system reboots.
If your system has Energy Star version 3 or later, you are not prompted for this information.
If you are performing interactive installations, you cannot preconfigure the Power Management information and avoid the prompt. However, by using a custom JumpStart installation, you can preconfigure the Power Management information by using a finish script to create an /autoshutdown or /noautoshutdown file on the system. When the system reboots, the /autoshutdown file enables Power Management and the /noautoshutdown file disables Power Management.
For example, the following line in a finish script enables the Power Management software and prevents the display of the prompt after the system reboots.
touch /a/autoshutdown |
Finish scripts are described in Creating Finish Scripts in Solaris 10 Installation Guide: Custom JumpStart and Advanced Installations.