InfoDoc ID   Synopsis   Date
41246   Booting a domain from the primary ssp's cdrom.   21 Dec 2001

Status Issued

Description

The following procedure is a sample of how to boot a domain off of the primary ssp's cdrom to do an initial OS installation, an upgrade, or just to do maintenance work. The example assumes that Solaris 2.6 5/98 is being loaded on a new domain which contains boards 0-4, and is on a platform called "tenkay". The primary ssp will be set up as the install server. There are 400mhz, 8 meg cache procs on the domain. We're going to call the new domain "newdomain". Notes have been made to show how various differences from my example of Solaris 2.6 can occur if you are installing/upgrading or booting from a different OS.

NOTE: If booting Solaris 2.6 make sure to use the 5/98 version which has the proper qfe driver support allowing the domain to boot off it's qfe cards. The procedure to boot off of Solaris 2.5.1 is an attachment to this document.

As root on the ssp:

  1. Modify /etc/hosts and /etc/ethers to indicate the IP address and ethernet address of the domain you are creating or planning to do maintenance on. Confirm that /etc/nsswitch.conf has files first for all selections.
  2. Insert the Solaris software disk in the ssp's cdrom.
  3. # cd /cdrom/cdrom0/s0/Solaris_2.6/Tools NOTE: Depending on the OS, the path may be slightly different. But, the necessary tool, add_install_client, should be in the Tools directory on the software cd.
  4. If this is a brand new domain, proceed to step 5. If this is an upgrade, and the ssp has previously been used to boot net from, the current domain will already have an install client specified for the domain in question with the old OS version. We have to remove that install client before continuing on to step 5. So, do the following: # ./rm_install_client <current_domain_name>
  5. # ./add_install_client newdomain sun4u1 NOTE: The platform type for Solaris 2.6 and below is sun4u1. For Solaris 7 and above it is sun4u.
  6. # share -F nfs -o ro,anon=0 /cdrom/cdrom0/s0

As ssp on the ssp:

If this is an upgrade of OS or a change of a domain which is currently configured step 1 is necessary. If this is a brand new domain, skip to step 2.

  1. ssp# domain_remove -d <domain name> NOTE: You will be prompted as to whether you wish to save domain specific files or not. If you wish to save the files answer yes, if not, then answer no. See the domain_remove man page for details.
  2. ssp# domain_create -d newdomain -b 0 1 2 3 4 -o 5.6 -p tenkay NOTE: See the domain_create man page for details on the command and options.
  3. ssp# domain_switch newdomain
  4. ssp# bringup -A off

Through the netcon session on newdomain:

  1. ok> setenv auto-boot? false
  2. ok> setenv local-mac-address? false
  3. Set up your net alias.
  4. ok> reset
  5. ok> limit-ecache-size NOTE: This is only necessary for 2.5.1 and 2.6 before the KJP is loaded.
  6. ok> boot net <-install, -s, ...>

NOTE: After the install/upgrade is completed and before rebooting the domain, install patch 105181-15 or higher for Solaris 2.6 to resolve the ecache-size problems in step 5. For Solaris 2.5.1 the patch is 103640-27 or higher. A patch is not necessary for Solaris 7 and above.

INTERNAL SUMMARY:

Internal Summary

SUBMITTER: Joshua Freeman APPLIES TO: Hardware/Ultra Enterprise/Servers/Enterprise 10000, OS Install/Boot, OS Install/Boot/Network Install, OS Install/Boot/OS Install, OS Install/Boot/System Boot, AFO Vertical Team Docs/HAS ATTACHMENTS: 2.5.1_qfeboot


Copyright (c) 1997-2003 Sun Microsystems, Inc.