Sun Fire E6900 Server
 
Solaris Operating System
 

PLA-Support>Sun Systems>SAND>Operating System>SN-SND: Sun OS Install and Upgrade
 
_KM>Content>Video
 
_Old GCS Categories>Sun Microsystems>Operating Systems>Solaris Operating System
 

Applies to:

Goal

Solution

The hostname for this demo is displayed as proto145 and the working directory is set to /etc.

Step 2:

The vi editor is used to add an entry in the /etc/ethers file. The ethernet address is taken from output on another screen and the hostname, proto146 is added to the file before the vi commands to force a write and quit.

Step 3:

The more command is used on the /etc/hosts file to display that the necessary client information exists.

Step 4:

The more command is used on the /etc/netmasks file to verify that the necessary network values are present for the client.

Step 5:

The Solaris 10 Software 1 of 4 CD-ROM for SPARC platform is inserted into the CD-ROM drive of the JumpStart server (proto145).

Step 6:

A directory called /export/config is created with the mkdir command. With the CD-ROM in the drive, the current working directory is set to /cdrom/cdrom0/s0 and the contents of this directory are listed.

Note the contents.

Step 7:

The current working directory is set to Solaris_10/Misc and the contents are listed. Note the directory called jumpstart_sample. The current working directory is then set to the jumpstart_sample directory and the contents listed again.

Step 8:

The contents of the jumpstart_sample directory are copied to the new /export/config directory so that sample configuration files will be located locally. Once copied, the new working directory is set to /export/config.

Step 9:

The mv command is used to rename the original rules file to rules.orig for safekeeping. Next, a new /export/config/rules file is created with the vi command and the necessary JumpStart client information inserted.

Step 10:

The /export/config/host_class file is edited with the vi command. The file is edited to specify the following; an initial install, a standalone system type, explicit partitioning, the End User software cluster, and partitions for root (/), /usr and /swap. Partition size and device names appropriate for the JumpStart client are also inserted.

Step 11:

The /export/config/finish_script file is edited with the vi command. The file is configured for the JumpStart client to avoid using the autoshutdown power-saving feature. Next, the permissions on the finish_script file is changed to 755 with the chmod command.

Step 12:

The check program is run to verify there are no problems with the new JumpStart client configuration. Note the output indicates no problems with the host_class and that the JumpStart configuration is okay.

Step 13:

A file called /export/config/sysidcfg is created using the vi command and the necessary information inserted. The 13-character encrypted root_password value is copied and pasted from the /etc/shadow file from another window.

Step 14:

The current working directory is set to /etc/dfs and the dfstab file is edited with the vi command. A line is inserted to share the /export/config directory.

Step 15:

The svcs command is executed to see if the NFS service is currently online. The output indicates the service is disabled.

Step 16:

The svcadm command is used to enable the NFS service and the svcs command is executed again to verify it has been started. Note the output states that the NFS service is online.

Step 17:

The shareall command is entered to read and execute the share statements in the /etc/dfs/dfstab file. The share command verifies the correct configuration.

Step 18:

Next, the current working directory is set to /cdrom/cdrom0/s0/Solaris_10/Tools and the add_install_client program within that directory is executed to add support for the JumpStart client. In another terminal window, the JumpStart client is given the boot command. Afterwards, the JumpStart client successfully boots to a console login prompt.

End:

This solution has no attachment