Part II Managing Server and Client Support

This part provides instructions for managing server and client support in the Solaris environment. This part contains these chapters.

Chapter 3 Managing Server and Client Support (Overview)

This chapter describes managing server and client support on a network, and it provides overview information about each system configuration (referred to as a system type) supported in the Solaris environment. This chapter also includes guidelines for selecting the appropriate system type to meet your needs.

This is a list of the overview information in this chapter.

• "Where to Find Server and Client Tasks"

• "What Are Servers and Clients"

• "What Does Support Mean"

• "Overview of System Types"

• "Guidelines for Choosing System Types"

• "Tools for Managing Server and Client Support"

• "What You Can Do With Host Manager"

• "What You Can't Do With Host Manager"

For step-by-step instructions about how to add and maintain server and client support, see Chapter 4, Managing Server and Client Support (Tasks).

For overview information on setting up a name service policy, see the Solstice AdminSuite 2.3 Administration Guide.

Where to Find Server and Client Tasks

Use this reference to find step-by-step instructions for setting up server and client services.

• Chapter 4, Managing Server and Client Support (Tasks)

What Are Servers and Clients

Systems on the network can usually be described as one of the following:

• Server - A system that provides services to other systems in its network. There are file servers, boot servers, database servers, license servers, print servers, installation servers, and even servers for particular applications. This chapter uses the term server to mean a system that provides file systems and installation software for other systems on the network.

• Client - A system that uses remote services from a server. Some clients have limited disk storage capacity, or perhaps none at all, and they have to rely on remote file systems from a server to function. Diskless, AutoClient(TM) and JavaStation(TM) systems are examples of this type of client.

  Other clients may use remote services (such as installation software) from a server, but they don't rely on a server to function. A standalone system, which has its own hard disk containing the root (/), /usr, and /export/home file systems and swap space, is a good example of this type of client.

What Does Support Mean

Providing support for a system means providing software and services to help another system function. Support can include:

• Making a system known to the network (i.e., host name and ethernet address information)

• Providing installation services to remotely boot and install a system

• Providing operating system (OS) services to a system with limited or no disk space

Overview of System Types

System types are basically defined by how they access the root (/) and /usr file systems, including the swap area. For example, standalone and server systems mount these file systems from a local disk, while other clients mount the file systems remotely, relying on servers to provide these services. Table 3-1 lists these and other differences for each system type.

Servers

A server system has the following file systems:

• The root (/) and /usr file systems, plus swap space

• The /export, /export/swap, and /export/home file systems, which support client systems and provide home directories for users

• The /opt directory or file system for storing application software

Servers can also contain the following software to support other systems:

• Operating system (OS) services for diskless, JavaStation, or AutoClient systems that are running a different release or are a different platform than the server

• Solaris CD image and boot software for networked systems to perform remote installations

• JumpStart(TM) directory for networked systems to perform custom JumpStart installations

Standalone Systems

A networked standalone system can share information with other systems in the network, but it could continue to function if detached from the network.

A standalone system can function autonomously because it has its own hard disk containing the root (/), /usr, and /export/home file systems and swap space. The standalone system thus has local access to operating system software, executables, virtual memory space, and user-created files.

A standalone system requires sufficient disk space to hold the four necessary file systems.

A non-networked standalone system is a standalone system with all the characteristics listed above except it is not connected to a network.

Diskless Clients

A diskless client has no disk and depends on a server for all its software and storage area. A diskless client remotely mounts its root (/), /usr, and /home file systems from a server.

A diskless client generates significant network traffic due to its continual need to procure operating system software and virtual memory space from across the network. A diskless client cannot operate if it is detached from the network or if its server malfunctions.

JavaStation Client

The JavaStation is a client designed for zero administration. This client optimizes Java(TM); the JavaStation client takes full advantage of the network to deliver everything from Java applications and services to complete, integrated system and network management. The JavaStation has no local administration; booting, administration, and data storage are handled by servers.

AutoClient Systems

An AutoClient system is nearly identical to a diskless client in terms of installation and administration. It has the following characteristics:

• Requires a minimum of a 100-Mbyte local disk for swapping and for caching its individual root (/) file system and the /usr file system from a server

• Can be set up so that it can continue to access its cache when the server is unavailable

• Relies on a server to access other file systems and software applications

• Contains no permanent data, making it a field replaceable unit (FRU)

You must obtain a license for each AutoClient system you want to add to your network. See the Solstice AdminSuite 2.3 Installation and Product Notes for licensing information.

Guidelines for Choosing System Types

Determining which system types are appropriate for your environment can be done by comparing each type based on the following characteristics:

• Centralized Administration

  • Can the system be treated as a field replaceable unit (FRU)? This means that a broken system can be quickly replaced with a new system without any lengthy backup/restore operations and no loss of system data.

  • Does the system need to be backed up? Large costs in terms of time and resources can be associated with backing up a large number of desktop systems.

  • Can the system's data be modified from a central server?

  • Can the system be installed from a centralized server, quickly and easily without handling the client system's hardware?

• Performance

  • Does this configuration perform well in desktop usage?

  • Does the addition of systems on a network affect the performance of other systems already on the network?

• Disk Usage

  • How much disk space is required to effectively deploy this configuration?

Table 3-2 describes how each system type scores in terms of each of these categories. A ranking of 1 is most efficient; a ranking of 4 is least efficient.

Tools for Managing Server and Client Support

In previous Solaris releases, you may have used Administration Tool to manage server and client support. In the Solaris 2.5 and later releases, you must use the Solstice Host Manager tool, which offers ease of use and provides support for the following name services:

• NIS+ tables

• NIS maps

• Local /etc files

What You Can Do With Host Manager

Host Manager is a graphical user interface that enables you to add and maintain server and client support on a network. With a name service like NIS+, you can manage system information in a centralized manner so that important system information, such as host names, does not have to be duplicated on every system in the network.

Host Manager enables you to:

• Add and modify support

• Update system types

• Convert system types

• Add and remove OS services

• Set up remote installation services

• Queue tasks

Add and Maintain Support

Host Manager enables you to add and modify support for the following Solaris system types:

• Solaris AutoClient systems

• Solaris diskless clients

• Solaris standalone systems

• Solaris OS servers

• JavaStations (modify support only)

Table 3-3 describes the server-client configurations that are supported by the Solstice AdminSuite 2.1 release of Host Manager.

The SunOS 4.x release is only supported on SPARC systems with the Sun4, Sun4c, and Sun4m platform groups. Support for the SunOS 4.x release will be removed in a later version of the Solstice AdminSuite software.

Update System Types

Host Manager initially marks the system types of previously added systems as generic. However, you can choose Update System Types from the File menu to probe previously added systems and attempt to automatically determine their system types. If Host Manager cannot determine the system type (for example, the system is not running the Solaris software) the systems will stay marked as generic.

Previously added systems running Solaris 2.5 or later must also have the Solstice AdminSuite software installed for Host Manager to automatically update their system type.

The system type information is stored in the bootparams file in the local /etc files or a name service database. Host Manager will either modify an existing bootparams entry or add a new one such as the following for a Solaris standalone system named mars:

mars boottype=:st

Convert System Types

Host Manager enables you to convert one system type to another. Table 3-4 shows what conversions you can make.

You can add Solaris 2.x OS services during the standalone system to OS server conversion.

Add OS Services

A Solaris OS server is a server that provides operating system (OS) services to support client systems. By using Host Manager, you can add support for an OS server or convert a standalone system to an OS server.

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 Sun4m systems running the Solaris 2.4 release, you must add Sun4m/Solaris 2.4 OS services to the OS server. You would also still need to add OS services to support SPARC Sun4c systems or x86 systems running the Solaris 2.4 release, because they are different platform groups.

You must have access to the appropriate Solaris CD image to add OS services.

Although Host Manager enables you to add support for diskless clients running the Sun4.x release, you cannot add SunOS 4.x OS services using Host Manager. You must use the install4x commands to add OS services to an OS server, and then use Host Manager to add support for the SunOS 4.x client.

Adding OS Services to a Server When the OS Services Have Been Patched

When adding OS services to an OS server, you may see error messages saying that you have inconsistent versions of the OS running on the server and the OS that you are trying to add. This 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 may have a server that is running the Solaris 2.5.1 release; you may also have additional OS services loaded on this server, including the Solaris 2.5 SPARC Sun4m OS services that have been patched. If you try to add the Solaris 2.5 SPARC Sun4c 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.
 

Remove OS Services

OS services can be removed from an OS server using Host Manager. For instance, if you no longer want to support SPARC Sun4m systems running the Solaris 2.4 release, you can remove these OS services from the server using Host Manager.

Set Up Remote Installation Services

Host Manager enables you to set up systems to provide Solaris 2.x installation services for other systems on the network. You can set up the following types of installation services on a system:

• An install server - A system on the network that provides a Solaris CD image (either from a CD-ROM drive or the copy on the hard disk) for other systems to install from.

• A boot server - A system that provides boot information to other systems on the network. The boot server and the install server are usually the same system.

• A profile server - A system that contains Jumpstart files for systems to perform a custom JumpStart installation.

A boot server and install server are typically the same system. However, if the system to be installed is on a different subnet than the install server, a boot server is required on that subnet.

Queue Tasks

Host Manager enables you to queue tasks such as converting system types and adding OS services. Since these tasks may require several minutes to process, Host Manager enables you to set up tasks to be performed without requiring you to wait for each task to be completed. After setting up the tasks, choose Save Changes from the File menu. Host Manager's progress is displayed in the message bar located at the bottom of the window as each task is processed.

Set Root Passwords

When adding a Solstice AutoClient or Solaris diskless client using Host Manager, you can now set the root password using the GUI just as you do when setting the group or user password.

Enable Scripts

When you add a Solstice AutoClient using Host Manager, you have the option to enable scripts to run on the server before or after you add the AutoClient to the server, or run on the client before or after the cache is configured on the AutoClient.

These scripts are those that you have created to customize the addition or deletion of AutoClient systems; these scripts need to be located in the /opt/SUNWadmd/Scripts directory in order for the AdminSuite software to read them.

Add a Multihomed Host

Host Manager enables you to add a multihomed host alias for servers with multiple network interfaces. For instance, if a server has more than one IP address because it is on multiple networks, it is considered a multihomed host. With Host Manager, you can specify more than one IP address for a host to make it a multihomed host.

What You Can't Do With Host Manager

Table 3-5 shows the limitations of Host Manager and their suggested workarounds.

Running Host Manager as Superuser

When running host manager as superuser, you will see slightly different behavior. The following list describes the limitations of running host manager as superuser.

• When Host Manager is started as superuser, you will see a dialog box describing the constraints that you will encounter.

• The name service selection dialog is forced to the local host and the text field is not editable.

• When adding a host, the file server is forced to the local host and can not be edited.

• When Remote Install is enabled in the Add, Modify, or Convert windows, the boot server is forced to the local host and can not be edited; also, the Install Server is forced to the local host and can not be edited.

Chapter 4 Managing Server and Client Support (Tasks)

This chapter describes how to set up and maintain server and client support using the Solstice Host Manager.

This is a list of the step-by-step instructions in this chapter.

• "How to Start Solstice Host Manager"

• "How to Update System Types"

• "How to Set Defaults for Adding Support"

• "How to Add Support for a Standalone System or OS Server"

• "How to Convert a System to an OS Server"

• "How to Add SunOS 4.x OS Services to an OS Server"

• "How to Add Solaris 2.x OS Services to an OS Server"

• "How to Add Support for an AutoClient System"

• "How to Add Support for a Diskless Client"

• "How to Modify Support for a System"

• "How to Delete Support for a System"

For overview information about managing server and client support, see Chapter 3, Managing Server and Client Support (Overview). For more information on using Solstice Host Manager, see the Solstice AdminSuite 2.3 Administration Guide.

Adding Server and Client Support Task Map

How to Start Solstice Host Manager

1. Verify that the following prerequisites are met. To use Solstice Host Manager, you must have:

   • Solstice AdminSuite installed.

   • A bit-mapped display monitor. The Solstice AdminSuite software can be used only on a system with a console that has a bit-mapped screen such as a standard display monitor that comes with a Sun workstation.

   • If you want to perform administration tasks on a system with an ASCII terminal as the console, use Solaris commands instead.

   • An X Window system installed and running.

   • Superuser (root) privilege or membership in the sysadmin group (group 14) and the required access privileges for managing the NIS or NIS+ database.

     ---

     Note -

     If your name service is NIS+, you must be a member of the NIS+ admin group.

     ---

2. Start the Solstice Launcher.

   $ solstice &

   The Solstice Launcher Menu is displayed.

3. Click on the Host Manager icon.

   

   The Load window is displayed.

4. Select the name service used in your network.

5. Check that the domain or host name is correct.

   If not, type the domain or host name you need to access.

6. Click on OK.

   The Solstice Host Manager main window is displayed.

Example--Host Manager Main Window

How to Update System Types

This procedure attempts to determine the system types for systems marked as generic.

1. Start Solstice Host Manager from the Solstice Launcher and select the name service, if not done already.

   See "How to Start Solstice Host Manager" for more information.

2. Select Update System Types from the File menu on the Solstice Host Manager Window.

   The Update Systems Types window is displayed.

3. Click on Update to update the systems marked as generic.

4. Verify the system has been converted to generic in the Solstice Host Manager Window.

How to Set Defaults for Adding Support

1. Start Solstice Host Manager from the Solstice Launcher and select the name service, if not done already.

   See "How to Start Solstice Host Manager" for more information.

2. Choose Set Defaults from the Edit menu.

   The Set Defaults window is displayed.

3. Fill in the Set Defaults window.

   The defaults you select will be the initial defaults values in the Add window. If you need information to complete a field, click on the Help button to see field definitions for this window.

4. Click on OK.

How to Add Support for a Standalone System or OS Server

The high-level steps in this procedure are:

• Adding information about the system

• (Optional) Setting up remote install capabilities for the system

• (Optional) Installing the system

1. Start Solstice Host Manager from the Solstice Launcher and select the name service, if not done already.

   See "How to Start Solstice Host Manager" for more information.

2. Select Add from the Edit menu on the Solstice Host Manager Window.

   The Add window is displayed.

3. Fill in the system information, selecting Solaris Standalone or OS Server as the system type.

   The system information includes all the fields from the host name through the timezone. If you need information to complete a field, click on the Help button to see field definitions for this window.

4. If you want to set up remote install capabilities for the system, continue to Step 5. If not, skip to Step 10.

5. Click on Enable Remote Install.

6. Select an Install Server.

   The Install Server defaults to the current host. Select Other from the Install Server menu to specify another host as the install server.

7. Click on Set Path to identify the path to the Solaris CD image on the install server.

   If the install server is a remote system, note that it must be minimally set up as a managed system.

   If You Are Using ...	And ...	Then Enter the Path ...
   The Solaris CD as the Solaris CD image	The Solaris CD is managed by Volume Management	/cdrom/cdrom0 or/cdrom/cdrom0/s0 or /cdrom/cdrom0/s2
   	The Solaris CD is not managed by Volume Management	Where you mounted the Solaris CD
   A copy of the Solaris CD on the install server's hard disk (by using setup_install_server)		To the Solaris CD image

8. Select the system's architecture type and OS release from the OS Release menu.

   The architecture type must match the system's architecture and the OS release should match the Solaris release you want to remotely install on the system.

9. If necessary, specify a boot server or profile server.

   To specify another server other than the default, select Other from the menu. Select a Profile Server from the Profile Server pull-down menu. You must also specify a path to the boot software on the boot server or the custom JumpStart directory on the profile server.

   To set up the other components of a custom JumpStart installation and preconfiguring network and system information, see SPARC: Installing Solaris Software or x86: Installing Solaris Software.

10. Click on OK on the Add window.

11. Select Save Changes from the File menu to add support for the standalone system or OS server.

    The standalone system or OS server is displayed in the Host Manager main window.

12. Verify the OS server information is correct in the Host Manager main window.

13. (Optional) Boot and install the standalone system or OS server.

    For more information about booting and installing, see SPARC: Installing Solaris Software for SPARC systems or x86: Installing Solaris Software for x86 systems.

    ---

    Note -

    If you are installing an OS server, you must allocate space in /export and /export/swap for the desired number of clients.

    ---

Example--Completed Host Manager Add Window for a Standalone System

The following example shows a completed Add window for the standalone system venus.

Where to Go From Here

If you want to add OS services after you install an OS server, see "How to Add Solaris 2.x OS Services to an OS Server".

How to Convert a System to an OS Server

1. Start Solstice Host Manager from the Solstice Launcher and select the name service, if not done already.

   See "How to Start Solstice Host Manager" for more information.

2. Select a host entry from Solstice Host Manager's main window.

   You can convert a standalone system and generic system to an OS server.

3. Select Convert to OS Server from the Edit Menu.

   The Convert window is displayed, and the selected system is displayed in the host name field.

4. Click on the Add button in the OS Services window to add services.

5. Click on Set Path to identify the path to the Solaris CD image from which to add the client services.

   The Install Server defaults to the current host. Select Other from the Install Server menu to specify another host as the install server. Note that a remote system must be minimally set up as a managed system.

   If You Are Using ...	And ...	Then Enter the Path ...
   The Solaris CD as the Solaris CD image	The Solaris CD is managed by Volume Management	/cdrom/cdrom0/s0 or /cdrom/cdrom0/s2 on SPARC platforms,/cdrom/cdrom0 on x86 platforms
   	The Solaris CD is not managed by Volume Management	Where you mounted the Solaris CD
   A copy of the Solaris CD on the Install Server's hard disk (by using setup_install_server)		Where you specified setup_install_server to copy the Solaris CD

6. Specify the type of services you want to add and click on Add.

   The OS service is added to the OS Services list and marked with a plus sign (+), which means it will be added when you save changes. You can use the Delete button to delete an OS service from the list before you save changes.

7. Click on OK on the Convert window.

8. Select Save Changes from the File menu to convert the system to an OS Server.

   The converted system is displayed as an OS server in the Host Manager main window.

9. Verify the host type has been updated in the Host Manager main window.

Example--Completed Host Manager Convert Window

How to Add SunOS 4.x OS Services to an OS Server

Sun plans to remove support for the SunOS 4.x release in a later version of the Solstice AdminSuite software. Also, you cannot add SunOS 4.x services to x86 OS servers.

The high-level steps in this procedure are:

• Determining the OS server to which you want to add SunOS 4.x OS services for diskless clients

• Installing the required SunOS 4.x release software (install4x command)

1. Log in as superuser on the OS server to which you want to add SunOS 4.x OS services for diskless clients.

2. Insert the Solstice AdminSuite 2.3 CD into your CD-ROM drive.

   This step assumes that your system is running Volume Management.

3. Change directory to the location of the software.

   # cd /cdrom/Solstice_sysmgt_2.3/4.x

4. Install the SunOS 4.x heterogeneous install software.

   # pkgadd -d `pwd` SUNWhinst

5. Eject the Solstice AdminSuite 2.3 CD.

   # cd # eject cd

6. Insert the SunOS 4.x release CD into your CD-ROM drive.

   This step assumes that your system is running Volume Management, and the CD-ROM drive is directly attached to the server. Volume Management automatically mounts the CD directory on /cdrom/volume1/s0.

7. Start the SunOS 4.x release software installation program.

   # /usr/sbin/install4x -m /cdrom/volume1/s0 -e /export

   The main menu is displayed.

   *** 4.1* Install Main Menu *** Choose an Architecture (then select modules to load): Modules Loaded Selected [a] sun4.sun4c.sunos.4.1.2 0 0 [b] sun4.sun4.sunos.4.1.2 0 0 [c] sun4.sun4m.sunos.4.1.2 0 0 or begin the loading process for all selected modules: [L] Load selected modules or abort without loading any modules: [Q] Quit without loading +-------------------+ | Disk Usage: | | 0K Selected | | 53634K Free | +-------------------+ Type any bracketed letter to select that function. Type ? for help.

8. On the main menu, specify the architecture you want to support by typing the associated character that is shown in brackets.

   The Module Selection menu is displayed.

   Select sun4.sun4c.sunos.4.1.2 modules: +[a] R proto root............240K | [o] User_Diag..............6352K +[b] R usr.................26240K | [p] Manual.................7456K +[c] R Kvm..................4832K |+[q] D TLI..................... 48K +[d] R Install...............936K | [r] D RFS.................... 912K [e] D Networking...........1040K | [s] D Debugging..............2928K [f] D System_V.............4008K | [t] SunView_Programmers....1840K [g] D Sys..................5288K | [u] Shlib_Custom...........1376K [h] C SunView_Users........2664K | [v] Graphics...............1784K [i] SunView_Demo..........512K |+[w] uucp....................608K+ [j] Text..................712K |+[x] Games.............. ...3136K [k] Demo.................4264K | [y] Versatec...............5960K [l] C OpenWindows_Users...25936K | [z] Security................312K [m] C OpenWindows_Demo.....4288K | [A] OpenWindows_Programmers.10200K [n] C OpenWindows_Fonts ...7840K | Module + = already loaded R = Required C= Common Legend: ** = selected for loading D = Desirable Others are optional Select [a-A] or a Quick-Pick Option: +-------------------+ [1] All Required Modules [4] All Optional Modules | Disk Usage: | [2] All Desirable Modules[5] All Modules | 0K Selected | [3] All Common Modules | 53634K Free | or [D] (done) to return to the main screen +-------------------+

9. Select modules to load by typing the associated character that is shown in brackets.

   The Module Selection screen readily enables you to pick groups of modules to be loaded. When you enter a 1, it marks all required modules for loading. When you enter a 2, it marks all recommended modules. When you enter a 3, it marks all commonly loaded modules. When you enter a 4, it marks all optional modules. When you enter a 5, it marks all modules shown on the Module Selection screen.

10. Return to the main menu by typing D.

    The main menu is displayed.

    *** 4.1* Install Main Menu *** Choose an Architecture (then select modules to load): Modules Loaded Selected [a] sun4.sun4c.sunos.4.1.2 0 4 [b] sun4.sun4.sunos.4.1.2 0 3 [c] sun4.sun4m.sunos.4.1.2 0 1 or begin the loading process for all selected modules: [L] Load selected modules or abort without loading any modules: [Q] Quit without loading +-------------------+ | Disk Usage: | | 0K Selected | | 53634K Free | +-------------------+ Type any bracketed letter to select that function. Type ? for help.

11. Type L to install the software.

    The modules you previously selected are installed.

    Installing module `proto root' [size: 248K] in directory /export/exec/proto.root.sunos.4.1.2 ... Updating server databases ... Press any key to continue:

12. After the modules are installed, press any key to return to the main menu.

    The loaded modules are displayed in the main menu.

13. If you want to add support for other architectures, repeat Step 8 through Step 11. Otherwise, type Q to exit.

    ---

    Note -

    There is no command-line equivalent for adding SunOS 4.x services to an OS server.

    ---

14. Verify the SunOS 4.x services have been added by listing the contents of the /export/SunOS_4.x directory.

Where to Go From Here

If you want to add SunOS 4.x support for a diskless client, see "How to Add Support for a Diskless Client".

How to Add Solaris 2.x OS Services to an OS Server

1. Start Solstice Host Manager from the Solstice Launcher and select the name service, if not done already.

   See "How to Start Solstice Host Manager" for more information.

2. Select an OS server to modify from the Host Manager main window.

3. Select Modify from the Edit menu on the Solstice Host Manager Window.

   The Modify window is displayed.

4. Click on the Add button in the OS Services window to add services.

5. Click on Set Path to identify the path to the Solaris CD image from which to add the client services.

   The Install Server defaults to the current host. Select Other from the Install Server menu to specify another host as the install server. Note that a remote system must be minimally set up as a managed system.

   If You Are Using ...	And ...	Then Enter the Path ...
   The Solaris CD as the Solaris CD image	The Solaris CD is managed by Volume Management	/cdrom/cdrom0/s0 or/cdrom/cdrom0/s2 on SPARC platforms,/cdrom/cdrom0 on x86 platforms
   	The Solaris CD is not managed by Volume Management	Where you mounted the Solaris CD
   A copy of the Solaris CD on the Install Server's hard disk (by using setup_install_server)		Where you specified setup_install_server to copy the Solaris CD

6. Specify the type of services you want to add and click on Add.

   The OS service is added to the OS Services list and marked with a plus sign (+), which means it will be added when you save changes. You can use the Delete button to delete an OS service from the list before you save changes.

7. Click on OK on the Add window.

8. Select Save Changes from the File menu to add services.

9. Verify that the OS services directories are available by listing the contents of the /export/Solaris_2.6 directory.

Example--Completed Add OS Services Window

The following example adds the Solaris 2.6 SPARC sun4c service to the OS server venus.

How to Add Support for an AutoClient System

This procedure assumes that the AutoClient server is already set up as an OS server and is already installed with the kernel architectures of the AutoClient system(s) to be added. For information on adding an OS Server or converting an existing system to an OS Server, see the online help or the Solstice AdminSuite 2.3 Administration Guide.

1. Start Host Manager from the Solstice Launcher and select the name service, if not done already.

   See "How to Start Solstice Host Manager" for more information.

2. Choose Add from the Edit menu. The Add window is displayed. Note that the default system type is Solaris Standalone.

3. Choose Solstice AutoClient from the System Type menu.

   The Add window for a Solstice AutoClient system is displayed.

4. Fill in the system information for the AutoClient system.

5. Click on OK after entering the required information.

   If you have not enabled licensing for the Solstice AutoClient feature, you will see a message saying that the software was unable to check out a license. For information on enabling licensing, see Solstice AutoClient 2.1 Installation and Product Notes.

   The AutoClient system becomes part of the list of AutoClient systems to add, and it is displayed on the Host Manager main window with a plus sign (+) next to it. The + means that the system is a "pending add."

6. Repeat Step 2 through Step 5 to add subsequent AutoClient systems to your "batch" of pending changes.

   The "Total Changes Pending" status will be incremented each time you add a system.

7. Choose Save Changes from the File menu when you are ready to confirm addition of all the AutoClient systems listed in the window.

   The Saving Changes message window appears. All of the AutoClient systems are added when you choose Save Changes from the File menu.

   Adding each client takes several minutes, depending on server speed, current load, and the number and type of patches that will be automatically added.

   As each AutoClient system is successfully added (as shown in the Saving Changes window), its corresponding entry no longer appears as a pending add in the Host Manager main window (that is, the + no longer appears next to the host name).

   ---

   Caution -

   For the AutoClient system to work properly, it needs superuser access to its /export/root directory. If Host Manager displays a message that the /export directory is already shared and has different share options than required, you need to allow superuser access to the client root area before the AutoClient system will function properly. The access mode for the client root is normally rw=clientname, root=clientname.

   If Host Manager displays a message that the /usr directory is already shared, it is because it tried to share /usr read-only. If you have it shared with read-write permissions, then /usr is set up correctly, and you do not have to make any modifications.

   ---

8. Boot your AutoClient system(s) from the network.

   For more information about booting your AutoClient systems, see Solstice AutoClient 2.1 Administration Guide.

9. Provide system configuration information for the AutoClient system during the initial boot process, if prompted.

10. Create a superuser password when prompted.

Example--Completed Host Manager Add Window for an AutoClient System

The following example shows a completed Add window for the Solstice AutoClient system mars.

How to Add Support for a Diskless Client

The high-level steps in this procedure are:

• Adding system information about the diskless client

• Selecting OS services for the diskless client

• Booting the diskless client

  ---

  Note -

  This procedure assumes the system providing the services (the file server) has already been configured as an OS server.

  ---

1. Start Solstice Host Manager from the Solstice Launcher and select the name service, if not done already.

   See "How to Start Solstice Host Manager" for more information.

2. Select Add from the Edit menu on the Solstice Host Manager main window.

   The Add window is displayed.

3. Fill in the system information, selecting Solaris Diskless as the system type.

   The system information includes all the fields from the host name through the time zone. If you need information to complete a field, click on the Help button to see field definitions for this window.

4. Select a File Server.

   The File Server defaults to the current host. Select Other from the Install Server menu to specify another host as the install server.

5. Select the client's architecture type and the OS release from the OS Release menu.

   The architecture type must match the diskless client's architecture, and the OS release should match the Solaris release you want the diskless client to run.

6. Identify the system's root path, swap path, and swap size.

7. Click on OK on the Add window.

8. Select Save Changes from the File menu to add support for the diskless client.

   The diskless client is displayed in the Host Manager main window. It takes several minutes to add the diskless client support, particularly to create the system's root and swap areas and apply any applicable patches with the admclientpatch(1M) command.

   ---

   Caution -

   For the diskless client to work properly, it needs superuser access to its /export/root directory. If Host Manager displays a message that the /export directory is already shared and has different share options than required, you need to allow superuser access to the client root area before the diskless client will function properly. The access mode for the client root is normally rw=clientname, root=clientname.

   If Host Manager displays a message that the /usr directory is already shared, it is because it tried to share /usr read-only. If you have it shared with read-write permissions, then /usr is set up correctly, and you do not have to make any modifications.

   ---

9. Verify that the system has been added as a diskless client in the Host Manager Main Window.

10. Boot the diskless client.

11. Provide the following system configuration information for the diskless client during the initial boot process, if prompted.

    • Geographic region

    • Time zone

    • Date and time

12. Create a superuser password when prompted.

Example--Completed Host Manager Add Window for a Diskless Client

The following example shows a completed Add window for the diskless client neptune.

Maintaining Server and Client Support

How to Modify Support for a System

1. Start Host Manager from the Solstice Launcher and select the name service, if not done already.

   See "How to Start Solstice Host Manager" for more information.

2. Select a system entry to modify from the Host Manager main window.

3. Choose Modify from the Edit menu.

   The Modify window contains the selected system entry.

4. Modify support for the system.

   If you need information to change a field, click on the Help button to see field definitions for this window.

5. Click on OK on the Modify window.

6. Select Save Changes from the File menu to modify support for the system.

7. Verify that the system entry has been modified in the Host Manager main window.

How to Delete Support for a System

1. Start Solstice Host Manager from the Solstice Launcher and select the name service, if not done already.

   See "How to Start Solstice Host Manager" for more information.

2. Select a system entry to delete from the Solstice Host Manager main window.

3. Select Delete from the Edit menu.

   A window is displayed asking you to confirm the deletion.

4. Click on OK.

5. Select Save Changes from the File menu to delete support for the system.

   The system entry is deleted from the Host Manager main window.

6. Verify that the system entry is deleted from the Host Manager main window.

Using the Host Manager Command-Line Interface to Automate Setup Tasks

Using the Host Manager command-line equivalents allows you to automate many of the setup tasks associated with creating new diskless and AutoClient systems. This automation is similar to what can be done when using the JumpStart product to install Solaris on standalone systems. By writing your own shell scripts and using the command-line equivalents, you can automatically customize the client environment in one operation.

Table 4-3 summarizes the equivalent Host Manager commands that can be used instead of the Solstice AdminSuite l to perform administration tasks.