To Patch a Solaris 9 OS Distribution by Using a Solaris 9 OS on a SPARC Patch Server

This procedure describes how to patch a Solaris 9 OS distribution in the N1 System Manager. The steps in this procedure need to be performed on the manageable server and the management server. Consider opening two terminal windows to complete the steps. The following steps first guide you through patching the manageable server and then provide steps for patching the distribution.

Before You Begin

• Create a Solaris 9 OS distribution on the management server. See To Copy an OS Distribution From CDs or a DVD in Sun N1 System Manager 1.3 Operating System Provisioning Guide or To Copy an OS Distribution From ISO Files in Sun N1 System Manager 1.3 Operating System Provisioning Guide. Type show os os-name at the command line to view the ID of the OS distribution. This number is used in place of DISTRO_ID in the instructions.

• Install the Solaris 9 OS on SPARC software on a machine that is not the management server. See To Load an OS Profile on a Server or a Server Group in Sun N1 System Manager 1.3 Operating System Provisioning Guide.

• Create a /patch directory on the Solaris 9 SPARC patch server.

• For a Solaris OS on x86 distribution, download and unzip the following patches into the /patch directory on the Solaris 9 OS on x86 patch server: 117172-17 and 117468-02. You can access these patches from http://sunsolve.sun.com.

• For a Solaris OS on SPARC distribution, download and unzip the following patches into the /patch directory on the Solaris 9 OS on x86 patch server: 117171-17, 117175-02, and 113318-20. You can access these patches from http://sunsolve.sun.com.

Steps

1. Set up and patch the Solaris 9 OS on SPARC machine.

   1. Log in to the Solaris 9 machine as root.

      % su password:password

   2. Reboot the Solaris 9 machine to single-user mode.

      # reboot -- -s

   3. In single-user mode, change to the patch directory.

      # cd /patch

   4. Install the patches.

      # patchadd -M . 117171-17 # patchadd -M . 117175-02 # patchadd -M . 113318–20

      ---

      Tip –

      Pressing Control+D returns you to multiuser mode.

      ---

2. Patch the distribution that you copied to the management server.

   1. Log in to the Solaris 9 machine as root.

      % su password:password

   2. Mount the management server.

      # mount -o rw management-server-IP:/js/DISTRO_ID /mnt

   3. Install the patches by performing one of the following actions:

      • If you are patching a Solaris OS on x86 software distribution, type the following commands:

        # patchadd -C /mnt/Solaris_9/Tools/Boot/ -M /patch 117172-17 # patchadd -C /mnt/Solaris_9/Tools/Boot/ -M /patch 117468-02

      • If you are patching a Solaris OS on SPARC software distribution, type the following commands:

        # patchadd -C /mnt/Solaris_9/Tools/Boot/ -M /patch 117171-17 # patchadd -C /mnt/Solaris_9/Tools/Boot/ -M /patch 117175-02 # patchadd -C /mnt/Solaris_9/Tools/Boot/ -M /patch 113318-20

        ---

        Note –

        You will receive a partial error for the first patch installation. Ignore this error.

        ---

   4. Unmount the management server.

      # unmount /mnt

3. Restart NFS on the management server.

   1. Edit the /etc/exports file.

      # vi /etc/exports

   2. Change /js *(rw,no_root_squash) to /js *(ro,no_root_squash).

   3. Restart NFS.

      # /etc/init.d/nfs restart

      NFS is restarted.

      The Solaris 9 OS on SPARC distribution is ready for deployment to target servers.

4. Fix the Solaris 9 OS on x86 distribution.

   1. Change to /js/<distro_id>/Solaris_9/Tools/Boot/boot/solaris.

      # cd /js/<distro_id>/Solaris_9/Tools/Boot/boot/solaris

   2. Re-create the bootenv.rc link.

      # ln -s ../../tmp/root/boot/solaris/bootenv.rc .

      The Solaris 9 OS on x86 distribution is ready for deployment to target servers.

Troubleshooting

If you want to patch another distribution you might have to delete the /patch/117172-17 directory and re-create it using the unzip 117172-17.zip command. When the first distribution is patched, the patchadd command makes a change to the directory that causes problems with the next patchadd command execution.