The following sections and Chapter 7, Managing Diskless Clients (Tasks) describe how to manage diskless client support in the Solaris Operating System (Solaris OS).
A diskless client is a system that depends on an OS server for its operating system, software, and storage. A diskless
client mounts its root (/
), /usr
, and other file
systems from its OS server. A diskless client has its own CPU and physical
memory and can process data locally. However, a diskless client cannot operate
if it is detached from its network or if its OS server malfunctions. A diskless
client generates significant network traffic because of its continual need
to function across the network.
In the Solaris Express,Solaris 10, and Solaris 9 releases, the diskless client commands, smosservice and smdiskless, enable you to manage OS services and diskless client support. In the Solaris 8 and Solaris 7 releases, diskless clients were managed with the Solstice™ GUI management tools.
The following table describes which Solaris releases and architecture types are supported by the smosservice and smdiskless commands.
Architecture Type |
Solaris 8 |
Solaris 9 |
Solaris 10 and Solaris Express |
---|---|---|---|
SPARC servers |
Supported |
Supported |
Supported |
x86 based servers |
Supported |
Supported |
Supported |
SPARC based clients |
Supported |
Supported |
Supported |
x86 based clients |
Supported (Starting with the Solaris 8 1/01 release) |
Supported |
Supported |
This table describes the combination of OS client-server configurations that are supported by the smosservice and smdiskless commands.
Table 6.3. OS Client-Server Support
Diskless Client OS | |||||
Server OS |
Solaris Express |
Solaris 10 |
Solaris 9 |
Solaris 8 |
Solaris 7 |
Solaris Express |
Supported |
Supported |
Supported |
Supported |
Supported |
Solaris 10 |
Not supported |
Supported |
Supported |
Supported |
Supported |
Solaris 9 |
Not supported |
Not supported |
Supported |
Supported |
Supported |
Solaris 8 |
Not supported |
Not supported |
Not supported |
Supported |
Supported |
Solaris 7 |
Not supported |
Not supported |
Not supported |
Not supported |
Supported |
You can use the smosservice and smdiskless commands to add and maintain diskless client support on a network. By using a name service, you can manage system information in a centralized manner so that important system information, such as host names, do not have to be duplicated for every system on the network.
You can perform the following tasks with the smosservice and smdiskless commands:
Add and modify diskless client support
Add and remove OS services
Manage diskless client information in the LDAP, NIS, NIS+, or files name service environment
If you are performing a GRUB based boot on an x86 system, you need to manually set up the DHCP configuration. See How to Prepare for Adding Diskless Clients in a GRUB Based Boot Environment for more information.
You can only use the diskless client commands to set up diskless
client booting. You cannot use these commands to set up other services, such
as remote installation or profile services. Set up remote installation services
by including diskless client specifications in the sysidcfg
file.
For more information, see
Solaris Express Installation Guide: Custom JumpStart and Advanced Installations
.
By writing your own shell scripts and using the commands shown in the following table, you can easily set up and manage your diskless client environment.
Table 6.4. Diskless Client Commands
Command |
Subcommand |
Task |
---|---|---|
/usr/sadm/bin/smosservice |
add |
Add OS services |
delete |
Delete OS services | |
list |
List OS services | |
patch |
Manage OS service patches | |
/usr/sadm/bin/smdiskless |
add |
Add a diskless client to an OS server |
delete |
Delete a diskless client from an OS server | |
list |
List the diskless clients on an OS server | |
modify |
Modify the attributes of a diskless client |
You can obtain help on these commands in two ways:
Use the
h
option when you type the command,
subcommand, and required options, as shown in the following example.
% /usr/sadm/bin/smdiskless add -p my-password -u my-user-name -- -h
View the smdiskless ( 1M ) and smosservice ( 1M ) man pages.
You can use the smosservice and smdiskless commands as superuser. If you are using role-based access control (RBAC), you can use either a subset of or all of the diskless client commands, according to the RBAC rights to which they are assigned. The following table lists the RBAC rights that are required to use the diskless client commands.
Table 6.5. Required RBAC Rights for Diskless Client Management
RBAC Right |
Command |
Task |
---|---|---|
Basic Solaris User, Network Management |
smosservice list |
List OS services
|
|
smosservice patch |
List OS service patches |
|
smdiskless list |
List diskless clients on an OS server |
Network Management |
smdiskless add |
Add diskless clients |
System Administrator |
All commands |
All tasks |
A Solaris OS server is a server that provides operating system (OS) services to support diskless client systems. You can add support for an OS server or convert a stand-alone system to an OS server by using the smosservice command.
For each platform group and Solaris release that you want to support, you must add the particular OS service to the OS server. For example, if you want to support SPARC sun-4u systems running the Solaris Express release, you must add the Sun-4u/Solaris Express OS services to the OS server. For each diskless client that you support, you must add the OS service for that client to the OS server. For example, you would need to add OS services to support SPARC sun-4m systems or x86 based systems that run the Solaris 10 or Solaris 9 release, because they are different platform groups.
You must have access to the appropriate Solaris software CD or disk image to add OS services.
When adding OS services to an OS server, you might see an error message stating that you have inconsistent versions of the OS running on the server and the OS that you are trying to add. This error message occurs when the installed version of the OS has packages that were previously patched, and the OS services being added do not have those packages patched, because the patches have been integrated into the packages.
For example, you might have a server that is running the Solaris Express or the Solaris 10 release. You might also have additional OS services loaded on this server, including the Solaris 9 SPARC sun-4m OS services that have been patched. If you try to add the Solaris 8 SPARC sun-4u OS services from a CD-ROM to this server, you could get the following error message:
Error: inconsistent revision, installed package appears to have been patched resulting in it being different than the package on your media. You will need to backout all patches that patch this package before retrying the add OS service option.
Before you set up your diskless client environment, ensure that you have the required disk space available for each diskless client directory.
In previous Solaris releases, you were prompted about diskless client
support during the installation process. In the Solaris
Express, Solaris 10, and Solaris 9 releases, you must manually allocate
an /export
file system either during installation or
create it after installation. See the following table for specific disk space
requirements.
Table 6.6. Disk Space Requirements for Solaris OS Servers
Server OS/Architecture Type |
Directory |
Required Disk Space |
---|---|---|
Solaris Express SPARC based OS server |
|
5 Gbytes |
Solaris Express x86 based OS server |
|
5 Gbytes |
Solaris Express SPARC based diskless client |
|
Reserve 200 to 300 Mbytes per diskless client. |
Solaris Express x86 based diskless client |
|
Reserve 200 to 300 Mbytes per diskless client. |