test

Sun N1 System Manager 1.3.1 Troubleshooting Guide

Chapter 9 Common Procedures

This section provides procedures that are used to resolve more than one N1 System Manager problem.

The following topics are discussed:

Downloading ALOM 1.5 Firmware Updates

This section provides detailed information to help you download and prepare the firmware versions that are required to discover Sun servers that use ALOM 1.5.

ProcedureTo Download and Prepare ALOM 1.5 Firmware

  1. Log in as root (su - root) to the N1 System Manager management server.

    The N1–ok prompt appears.

  2. Create directories into which the ALOM firmware update zip files are to be saved.

    Create separate directories for each server type firmware download. For example:


    # mkdir ALOM-firmware

  3. In a web browser, go to http://jsecom16.sun.com/ECom/EComActionServlet?StoreId=8.

    The downloads page appears.

  4. To download the ALOM 1.5 firmware zip file, log in and navigate to ALOM 1.5, All Platforms/SPARC, English, Download.

    Download the file to the directory you created for the ALOM firmware in Step 2.

  5. Change to the directory where you downloaded the ALOM firmware file and unpack the file.


    bash-3.00# tar xvf ALOM_1.5.3_fw.tar
x README, 9186 bytes, 18 tape blocks
x copyright, 93 bytes, 1 tape blocks
x alombootfw, 161807 bytes, 317 tape blocks
x alommainfw, 5015567 bytes, 9797 tape blocks

    The files are extracted.

Next Steps

Downloading V20z and V40z Server Firmware Updates

This section provides detailed information to help you download and prepare the firmware versions that are required to discover Sun Fire V20z and V40z servers.

ProcedureTo Download and Prepare Sun Fire V20z and V40z Server Firmware

  1. Log in as root (su - root) to the management server.

    The N1–ok prompt appears.

  2. Create directories into which the V20z and V40z firmware update zip files are to be saved.

    Create separate directories for each server type firmware download. For example:


    # mkdir V20z-firmware V40z-firmware

  3. In a web browser, go to http://www.sun.com/servers/entry/v20z/downloads.html.

    The Sun Fire V20z/V40z Server downloads page appears.

  4. Download the Sun Fire V20z Server 2.4.0.8 NSV patch file.

    The download Welcome page appears. Type your username and password, and then click Login.

    The Terms of Use page appears. Read the license agreement carefully. You must accept the terms of the license to continue and download the firmware. Click Accept and then click Continue.

    The Download page appears. Several downloadable files are displayed.

  5. To download the V20z firmware zip file, click V20z BIOS and SP Firmware, English (nsv-v20z-bios-fw_V2.4.0.8.zip).

    Save the file to the directory that you created for the V20z firmware in Step 2.

  6. To download the V40z firmware zip file, click V40z BIOS and SP Firmware, English (nsv-v40z-bios-fw_V2.4.0.8.zip).

    Save the file to the directory you created for the V40z firmware in Step 2.

  7. Change to the directory where you downloaded the V20z firmware file and type unzip nsv-v20z-bios-fw_V2.4.0.8.zip to unpack the zip file.

    The sw_images directory is extracted.

    The following files in the sw_images directory are used by the N1 System Manager to update V20z manageable server firmware:

    • Service Processor:

      sw_images/sp/spbase/V2.4.0.8/install.image

    • BIOS

      sw_images/platform/firmware/bios/V1.34.6.2/bios.sp

  8. Change to the directory where you downloaded the V40z firmware zip file and type unzip nsv-v40z-bios-fw_V2.4.0.8.zip to unpack the zip file.

    The sw_images directory is extracted.

    The following files in the sw_images directory are used by the N1 System Manager to update V40z manageable server firmware:

    • Service Processor:

      sw_images/sp/spbase/V2.4.0.8/install.image

    • BIOS:

      sw_images/platform/firmware/bios/V1.34.6.2/bios.sp

Next Steps

Regenerating Common Agent Container Security Keys

This section provides the procedure for regenerating the N1 System Manager security keys.

ProcedureTo Regenerate Common Agent Container Security Keys

  1. Log in as root (su - root) on the management server.

  2. Stop N1 System Manager.

    • On a Solaris OS management server, type svcadm disable -s n1sm.

    • On a Linux management server, type /etc/init.d/n1sminit stop. Wait for all process to stop.

    Wait for all processes to stop before continuing.

  3. Regenerate security keys using the create-keys subcommand.

    If the management server is running Linux:


    # /opt/sun/cacao/bin/cacaoadm create-keys --force

    If the management server is running the Solaris OS:


    # /opt/SUNWcacao/bin/cacaoadm create-keys --force

  4. Restart the N1 System Manager.

    • On a Solaris OS management server, type svcadm enable n1sm.

    • On a Linux management server, type /etc/init.d/n1sminit start.

      Wait for all processes to stop.

Resetting Email Accounts for ALOM-based Managed Servers

If you have configured a separate mail server and account for the N1 System Manager to receive hardware event notifications, and the N1 System Manager is not receiving hardware event notifications from ALOM architecture manageable servers, the following problems might exist:

To resolve the first three issues, log in to the management server as root (su - root) and run the command n1smconfig -A to start the email reconfiguration process. Then do one of the following actions:

To resolve the last issue, proceed as described by To Reset Email Accounts for ALOM-based Managed Servers

ProcedureTo Configure the ALOM Email Alert Settings

  1. Log in as root (su - root) to the management server management server.

  2. Type n1smconfig -A to start the ALOM email alert settings configuration process.

    You are notified that proper settings are required to send email alerts, and the existing values are displayed. You are then asked whether to modify the email alert settings.

  3. Choose whether to modify the email alert settings.

    • Type n to accept the displayed settings. The email alert configuration process exits to the system prompt.

    • Type y to modify the email alert configuration.

      You are prompted for the email alert user name.

  4. Type the account name that is to be used for the email alerts, for example n1smadmin.

    You are prompted for the email alert folder.

  5. Type the name of an email folder for the alert account, for example, inbox.

    You are prompted for the email protocol

  6. Type the name of the email protocol used by the management server.

    Valid entries are pop3 or imap.

    You are prompted for the email alert user account password.

  7. Type the password for the email alert user account.

    You are prompted for the email alert user account email address.

  8. Type the user account email address, for example n1smadmin@company.com.

    You are prompted for the IP address of the email server.

  9. Specify the IP address of the email server.

    • If you have installed and enabled an email server on the management server, type the IP address of the management server management network interface.

    • If you have installed and enabled an email server on a different machine that is accessible by the management server management network interface, type the IP address of that machine.

    The values you have specified are displayed, and you are asked whether you want to use the values.

  10. Choose whether to accept the displayed email alert settings.

    • Type n if the settings are not correct.

      The ALOM email alert settings process is restarted, and you are prompted to specify the email alert user name.

    • Type y to use the displayed email alert settings.

      The settings are displayed again, and you are asked whether you want to apply the settings.

      Type y to apply the settings, or type n to exit to the command prompt.

ProcedureTo Verify ALOM Server Email

This procedure provides the steps required to determine why ALOM server email alerts are not received by N1 System Manager. Failure to receive email alerts from ALOM servers might be caused by the following problems:

  1. Verify that email sent from the ALOM server can be received by the designated email server.

    Configure an independent mail client, such as Mozilla, with the same mail server IP, username and password.

  2. Use the telnet command to access an ALOM server and execute the resetsc -y command to generate a warning message.

    Check if the mail client is able to receive the ALOM warning message. If it is, you do not need to reset the email accounts for the server.

    See SP-Based Discovery in Sun N1 System Manager 1.3 Discovery and Administration Guide for information about default telnet login and passwords for servers.

  3. Verify that the N1 System Manager has access to the designated email server.

    Use the telnet command to access an ALOM server, and execute the showsc command. Make sure the following parameters and values are set as shown:

    • if_emailalerts value is set to true

    • mgt_mailhost variable is set to the designated mail server's IP address.

    • mgt_mailalert(1) variable is set to the email address to which alerts must be sent.

    If you do not see these settings, or if you see incorrect values for the mgt_mailalert email address, reset the email account as described in To Reset Email Accounts for ALOM-based Managed Servers.

ProcedureTo Reset Email Accounts for ALOM-based Managed Servers

This procedure provides the steps required to replace a compromised or corrupt ALOM email account on a managed server. The ALOM email addresses should be reserved for use only by the N1 System Manager.

Before You Begin

Confirm that the problem is related to the fact that email alerts are not being received for the server as described in To Verify ALOM Server Email.

  1. Log in to the N1 System Manager.

    See To Access the N1 System Manager Command Line in Sun N1 System Manager 1.3 Discovery and Administration Guide for details.

  2. Switch off monitoring for ALOM-based manageable servers.

    • For an individual server, set the monitored attribute to false by using the set server command.


      N1-ok> set server server monitored false

      In this example, server is the name of the ALOM-based manageable server for which you want to reset the email account. Executing this command disables monitoring of the server.

    • If the ALOM-based servers are in the same group, use the set group command to switch off monitoring for the server group.


      N1-ok> set group group monitored false

      In this example, group is the name of the group of ALOM-based manageable servers for which you want to reset email accounts. Executing this command disables monitoring of the server group.

  3. Change the email address for the server using the n1smconfig command with the -A option.

    ALOM-based servers support email addresses of up to 33 characters in length.

    Note –

    If you manually configured ALOM-based servers to send event notifications by email to other addresses, using the telnet command and the setsc mgt_mailalert command, those addresses will not be changed by running the n1smconfig command.

  4. Switch on monitoring for the ALOM-based manageable server.

    • For an individual server, set the monitored attribute to true by using the set server command.


      N1-ok> set server server monitored true

    • If the ALOM-based servers are in the same group, use the set group command to switch on monitoring for the server group.


      N1-ok> set group group monitored true

      In this example, group is the name of the group of ALOM-based manageable servers for which you want to reset email accounts. Executing this command enables monitoring of the server group.

Updating Management Server System Files

This section provides the procedures for configuring the management server system files.

ProcedureTo Update the /etc/hosts File

  1. Log in as root (su - root) on the management server.

  2. Edit /etc/hosts and ensure that the entries are similar to the following example:

    # Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1           localhost
111.222.333.44     machine-name loghost

    where 111.222.333.44 is the IP address of the N1 System Manager server, and machine-name is the name of the N1 System Manager management server.

    For example, if the machine name is n1manager, and the assigned IP address for eth0 is 129.123.111.12, then the /etc/hosts file should contain the following settings:

    # Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1          localhost.localdomain localhost
129.123.111.12     n1manager loghost

    You must reboot the system after updating the /etc/hosts file.

ProcedureTo Update the ssh_known_hosts File

The management server /etc/opt/sun/n1gc/ssh_known_hosts file contains the name, IP address, and encrypted access keys for SSH-accessible servers. A stale or obsolete entry for a server in the /etc/opt/sun/n1gc/ssh_known_hosts file prevents SSH access to that server. The solution is to remove the entry for server from the /etc/opt/sun/n1gc/ssh_known_hosts file as follows.

  1. Note the name and IP address of the inaccessible server.

  2. Log in as root (su - root) on the management server.

  3. Edit the /etc/opt/sun/n1gc/ssh_known_hosts file and delete the entry for the inaccessible server.

ProcedureTo Update the /etc/resolv.conf File

    Edit /etc/resolv.conf and ensure that the entries are similar to the following:

    nameserver server 1 IP address
nameserver name server 2 IP address
nameserver name server 3 IP address
domain your-domain-name
search your-domain-name

    For example, assume the IP address of the first DNS server is 129.123.111.12, the second DNS server is 129.123.111.24, and the third DNS server is 129.123.111.36. If your company domain name is mydomain.com, then the /etc/resolv.conf file would contain the following lines.

    nameserver 129.123.111.12
nameserver name 129.123.111.24
nameserver name 129.123.111.36
domain mydomain.com
search mydomain.com

ProcedureTo Disable Managed Server Automatic Configuration

The following procedure disables the automatic configuration of manageable servers during discovery.

  1. Log in as root (su - root) on the management server.

  2. Edit the /etc/opt/sun/n1gc/domain.properties file and add the following line to the file:

    com.sun.hss.domain.internal.discovery.initializeDevice=false

    The N1 System Manager system must be restarted for auto configuration disabling to take effect. Note that once auto configuration is disabled, any servers in a factory default state cannot be discovered until their SSH and IPMI accounts are configured. For further information, see Setting Up Manageable Servers in Sun N1 System Manager 1.3 Site Preparation Guide.

Using a Managed Server to Patch Solaris OS 9 Distributions

Solaris OS 9 update 7 or earlier distributions on the management server must be patched before being deployed to manageable servers. The patches described are necessary to enable N1 System Manager to provision Solaris OS 9 update 7 and earlier versions to managed server. The procedures in this section are not required for Solaris OS 9 update 8.

To patch your Solaris OS 9 update 7 or earlier distributions, you first create either an x86 based or SPARC based Solaris 9 patch server using an available managed server. You then use the patch server to patch your Solaris 9 update 7 distributions on the management server, after which you can provision the patched distributions to managed servers.

This section provides the procedures for creating and using a patch server to patch your Solaris OS 9 update 7 or earlier distributions. The following topics are discussed:

Note –

The procedures in this section require that you have created at least one Solaris OS 9 update 7 or earlier distribution on the management server. For instructions on how to create an OS distribution, 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.

Creating and Using a Solaris OS 9 x86 Patch Server to Patch Solaris OS 9 Update 7 Distributions

This section provides the procedures for creating a Solaris OS 9 x86 patch server, and then using the patch server to patch the Solaris OS 9 distributions on the management server. The following topics are discussed:

Caution – Caution –

The procedures are sequentially dependent, and must be followed in the above order.

ProcedureTo Create a Solaris OS 9 x86 Patch Server

Before You Begin

At least one Solaris OS 9 update 7 or earlier distribution on the management server. For instructions on how to create an OS distribution, 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

  1. Select an unused x86 managed server to become the x86 patch server.

    The following steps refer to the selected managed server as the x86 patch server.

  2. Install the Solaris x86 OS on the x86 patch server.

    If the OS distribution to be provisioned is Solaris x86 OS 9 update 7, then install Solaris x86 OS 9 update 7 on the x86 patch server.

    If the OS distribution is a version earlier than Solaris x86 OS 9 update 7, then install that version of the Solaris OS on the x86 patch server.

  3. Log in as root (su - root) to the x86 patch server.

  4. Create a /patch directory on the x86 patch server.

  5. Download and unzip the patches from http://sunsolve.sun.com to the /patch directory on the x86 patch server as follows:

    • For a Solaris OS 9 on x86 distribution, download and unzip the following patches into the /patch directory: 117172-17 and 117468-02.

    • For a Solaris OS 9 on SPARC distribution, download and unzip the following patches into the /patch directory: 117171-17, 117175-02, and 113318-20. .

Next Steps

Patch the Solaris x86 OS on the patch server as described in the next procedure.

ProcedureTo Patch the Solaris x86 OS on the Patch Server

Before You Begin

Create the Solaris x86 OS patch server as described in To Create a Solaris OS 9 x86 Patch Server.

  1. Log in as root (su - root) on the patch server.

  2. Type reboot -- -s to reboot the Solaris 9 patch server to single-user mode.

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

  4. Install the Solaris x86 OS patches.


    # patchadd -M . 117172-17
# patchadd -M . 117468-02
    Tip –

    Pressing Control+D returns you to multiuser mode.

Next Steps

Configure and restart NFS on the management server as described in the next procedure.

ProcedureTo Configure and Restart NFS on the Management Server

Before You Begin

Patch the Solaris OS on the patch server as described in To Patch the Solaris x86 OS on the Patch Server.

  1. Log in as root (su - root) on the management server server.

  2. Edit the /etc/exports file and change /js *(ro,no_root_squash) to /js *(rw,no_root_squash).

  3. Save and close the /etc/exports file.

  4. Type /etc/init.d/nfs restart to restart NFS.

Next Steps

Patch the Solaris x86 OS distribution on the management server as described in the next procedure.

ProcedureTo Patch the Solaris OS 9 Distribution on the Management Server

Before You Begin

Configure and restart NFS on the management server as described in To Configure and Restart NFS on the Management Server.

  1. Log in as root (su - root) on the management server server.

  2. Type n1sh show os all to list all OS distributions on the management server.

    Note the ID of the Solaris OS 9 update 7 or earlier distribution. The Solaris OS 9 update 7 distribution ID is used in place of DISTRO-ID in the following steps.

  3. Mount the Solaris 9 OS distribution on the management server.

    Type mount -o rw management-server-IP:/js/DISTRO-ID /mnt where management-server-IP is the IP address of the management server, and DISTRO-ID is the ID of the Solaris OS 9 update 7 or earlier distribution that is to be patched.

  4. Patch the distribution on the management server.

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

      • If you are patching an x86 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 SPARC 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.

    2. Type unmount /mnt to unmount the management server.

Next Steps

Reconfigure and restart NFS on the management server as described in the next procedure.

ProcedureTo Reconfigure and Restart NFS on the Management Server

Before You Begin

Patch the Solaris OS 9 distribution on the management server as described in To Patch the Solaris OS 9 Distribution on the Management Server.

  1. Log in as root (su - root) on the management server server.

  2. Edit the /etc/exports file and change /js *(rw,no_root_squash) to /js *(ro,no_root_squash).

    Save and close the file.

  3. Type /etc/init.d/nfs restart to restart NFS.

Next Steps

Update the Solaris 9 OS distribution as described in the next procedure.

ProcedureTo Update the Solaris 9 x86 OS Distribution bootenv.rc File

Before You Begin

Reconfigure and restart NFS on the management server as described in To Reconfigure and Restart NFS on the Management Server.

  1. Log in as root (su - root) on the management server server.

  2. Change directory to /js/distro-id/Solaris_9/Tools/Boot/boot/solaris.

  3. Type ln -s ../../tmp/root/boot/solaris/bootenv.rc . to re-create the bootenv.rc link.

    The Solaris OS 9 on x86 distribution is ready for deployment to x86 manageable server.

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.

This patch is not needed for the Solaris 9 update 8 build 5 OS.

Creating and Using a Solaris OS 9 SPARC Patch Server to Patch Solaris OS 9 Update 7 Distributions

This section provides the procedures for creating a Solaris OS 9 SPARC patch server, and then using the patch server to patch the Solaris OS 9 distributions on the management server. The following topics are discussed:

Caution – Caution –

The procedures are sequentially dependent, and must be followed in the above order.

ProcedureTo Create a Solaris OS 9 SPARC Patch Server

Before You Begin

Create at least one Solaris OS 9 update 7 or earlier distribution on the management server. For instructions on how to create an OS distribution, 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

  1. Select an unused SPARC managed server to become the x86 patch server.

    The following steps refer to the selected managed server as the x86 patch server.

  2. Install the Solaris SPARC OS on the x86 patch server.

    If the OS distribution to be provisioned is Solaris SPARC OS 9 update 7, then install Solaris SPARC OS 9 update 7 on the SPARC patch server.

    If the OS distribution is a version earlier than Solaris SPARC OS 9 update 7, then install that version of the Solaris OS on the SPARC patch server.

  3. Log in as root (su - root) to the SPARC patch server.

  4. Create a /patch directory on the SPARC patch server.

  5. Download and unzip the patches from http://sunsolve.sun.com to the /patch directory on the SPARC patch server as follows:

    • For a Solaris OS 9 on x86 distribution, download and unzip the following patches into the /patch directory: 117172-17 and 117468-02.

    • For a Solaris OS 9 on SPARC distribution, download and unzip the following patches into the /patch directory: 117171-17, 117175-02, and 113318-20. .

Next Steps

Patch the Solaris OS on the patch server as described in To Patch the Solaris SPARC OS on the Patch Server.

ProcedureTo Patch the Solaris SPARC OS on the Patch Server

Before You Begin

Create the Solaris SPARC OS patch server as described in To Create a Solaris OS 9 SPARC Patch Server.

  1. Log in as root (su - root) on the patch server.

  2. Type reboot -- -s to reboot the Solaris 9 patch server to single-user mode.

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

  4. Install the Solaris SPARC OS patches.


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

    Pressing Control+D returns you to multiuser mode.

Next Steps

Configure and restart NFS on the management server as described in the next procedure.

ProcedureTo Configure and Restart NFS on the Management Server

Before You Begin

Patch the Solaris SPARC OS on the patch server as described in To Patch the Solaris SPARC OS on the Patch Server.

  1. Log in as root (su - root) on the management server server.

  2. Edit the /etc/exports file and change /js *(ro,no_root_squash) to /js *(rw,no_root_squash).

  3. Save and close the /etc/exports file.

  4. Type /etc/init.d/nfs restart to restart NFS.

Next Steps

Patch the Solaris OS 9 distribution on the management server as described in the next procedure.

ProcedureTo Patch the Solaris OS 9 Distribution on the Management Server

Before You Begin

Configure and restart NFS on the management server as described in To Configure and Restart NFS on the Management Server.

  1. Log in as root (su - root) on the management server server.

  2. Type n1sh show os all to list all OS distributions on the management server.

    Note the ID of the Solaris OS 9 update 7 or earlier distribution. The Solaris OS 9 update 7 distribution ID is used in place of DISTRO-ID in the following steps.

  3. Mount the Solaris 9 OS distribution on the management server.

    Type mount -o rw management-server-IP:/js/DISTRO-ID /mnt where management-server-IP is the IP address of the management server, and DISTRO-ID is the ID of the Solaris OS 9 update 7 or earlier distribution that is to be patched.

  4. Patch the distribution on the management server.

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

      • If you are patching an x86 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 SPARC 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.

    2. Type unmount /mnt to unmount the OS distribution.

Next Steps

Reconfigure and restart NFS on the management server as described in the next procedure.

ProcedureTo Reconfigure and Restart NFS on the Management Server

Before You Begin

Patch the Solaris OS 9 distribution on the management server as described in To Patch the Solaris OS 9 Distribution on the Management Server.

  1. Log in as root (su - root) on the management server server.

  2. Edit the /etc/exports file and change /js *(rw,no_root_squash) to /js *(ro,no_root_squash).

    Save and close the file.

  3. Type /etc/init.d/nfs restart to restart NFS.

Next Steps

Update the Solaris 9 OS distribution bootenv.rc file as described in the next procedure.

ProcedureTo Update the Solaris 9 SPARC OS Distribution bootenv.rc File

  1. Log in as root (su - root) on the management server server.

  2. Change directory to /js/distro-id/Solaris_9/Tools/Boot/boot/solaris.

  3. Type ln -s ../../tmp/root/boot/solaris/bootenv.rc . to re-create the bootenv.rc link.

    The Solaris OS 9 on x86 distribution is ready for deployment to x86 manageable server.

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.

This patch is not needed for the Solaris 9 update 8 build 5 OS.