These instructions explain how to use the remote CD-ROM on the System Service Processor to upgrade the Solaris operating environment on Sun Enterprise 10000 domains. Basic instructions for upgrading to the Solaris 8 or 9 operating environment on multidomain servers are provided in the Solaris 8 Advanced Installation Guide in the Solaris 8 Collection or the Solaris 9 Installation Guide in the Solaris 9 Collection.

The upgrade of the Solaris operating environment on Sun Enterprise 10000 domains involves various tasks that you must perform before and after the actual upgrade. This chapter provides:

• Overview of Domain Upgrade Tasks with a table of tasks

• Resources Needed to Start the Domain Upgrade

• Domain Pre-Upgrade Tasks

• Domain Upgrade Tasks specific to the Sun Enterprise 10000 server

• Domain Post-Upgrade Tasks

Caution - If you are upgrading to the Solaris 8 10/01 operating environment on a Sun Enterprise 10000 domain and you want to run DR model 3.0 on that domain, you must run SSP 3.5 software on the System Service Processor. If you run DR model 2.0 on your domain, your SSP can run SSP 3.2, SSP 3.3, SSP 3.4, or SSP 3.5 software. Note that SSP software versions 3.0, 3.1, and 3.1.1 do not support domains running the Solaris 8 10/01 operating environment. For SSP 3.5 software installation instructions, see Chapter 3. For details on installing SSP 3.2, 3.3, or 3.4, refer to the Sun Enterprise 10000 SSP Installation Guide and Release Notes for the SSP version to be installed.

This section provides an overview of the tasks required to upgrade from an earlier version of the Solaris operating environment to the Solaris 8 or 9 operating environment. The upgrade involves the suninstall utility, which merges the new version of the Solaris software with the existing files on the domain's disk, saving as many local modifications as possible.

TABLE 9-1 illustrates the tasks involved in upgrading the Solaris operating environment on a Sun Enterprise 10000 server. You must complete these tasks in the order shown. The following sections provide further details about each task. These tasks can take a considerable amount of time to complete, depending entirely on the configuration of the server and the site in which it resides.

The following list identifies the various items that you must have or information that you must know before starting the upgrade process:

• Floating host name of your SSP

• /usr partition on your boot disk that is 1024 MBs or larger

  If the /usr partition is smaller than 1024 MBs, repartition the drive before you attempt to upgrade the domain. You can use the disk-partition sizes listed in TABLE 8-5 . With the introduction of the 64-bit kernel into the Solaris operating environment, the environment's size has grown significantly; thus, if you are still using a single 2.1-GB disk as your boot disk, you should migrate to a 4.2-GB, or larger, disk at some point in the near future.

• Minimum set of CDs to use during the upgrade. Depending on the locale and distribution that you select during the upgrade, you need to use two to four CDs to perform the upgrade:

  • Solaris 8 or 9 Software 1 of 2 - SPARC Platform Edition

  • Solaris 8 or 9 Software 2 of 2 - SPARC Platform Edition

  • Software Supplements for the Solaris 8 or 9 operating environment - SPARC Platform Edition

  • Solaris 8 or 9 Languages

  
  

  ---

  Caution Caution - Do not use the Solaris 8 or 9 Installation CD to upgrade the Solaris operating environment on Sun Enterprise 10000 domains. Begin the upgrade by using the Solaris 8 or 9 Software 1 of 2 CD as explained in this chapter.

  ---

  
  

• Note the following:

  • Be sure that you have sufficient disk space on the partition to be upgraded.

    You may need to remove selected modules from your partition or possibly repartition the disk to allocate sufficient space.

  • You do not need to back out installed patches before you perform the upgrade.

  • You must be familiar with the software packages on your disk and their dependencies, in case your disk becomes full and you need to delete those packages.

  • During an upgrade, the suninstall utility attempts to preserve local modifications to the server whenever possible. However, local modifications can cause an upgrade to fail or perform differently than you would expect.

    Check the documentation of other software you are running, such as disk volume managers, before you use the upgrade option. There may be additional instructions you need to follow to preserve existing configurations, especially for Alternate Pathing, Solstice DiskSuite, or Veritas Volume Manager.

  • In the Solaris 2.5.1 operating environment, the kernel resides in /platform/sun4u1/kernel/unix . If you override the boot file location by explicitly setting it to kernel/unix , you can successfully upgrade the Solaris software, but you cannot boot the domain.

This section describes the prerequisite tasks and procedures that you must complete before upgrading the Solaris operating environment on a Sun Enterprise 10000 domain. This section describes how to:

• Prepare the domain for upgrade

• Verify the domain network information

• Set up the SSP as an install server

• Bring up the domain to the OpenBoot PROM level

1. Log in to the domain as superuser and back up the domain if you have not already done so.

Use the ufsdump (1M) command to back up all operating-system file systems. The safest backup to perform is a level 0 dump of the file systems connected to the domain being upgraded. If you do not have an established backup procedure, refer to the System Administration Guide in the Solaris System Administration Collection.

2. Preserve symbolic links by replacing those that use absolute paths with ones that use relative paths.

For example, if /usr/openwin is a symbolic link to /export/openwin , change the symbolic link to ../export/openwin

During an upgrade, the suninstall utility cannot reference symbolic links that use absolute paths because the Solaris installation program mounts the root ( / ) file system at /a . For example, a symbolic link to /export/openwin would fail because during an upgrade, /export/openwin is really /a/export/openwin

When the suninstall utility cannot reference a symbolic link, it overwrites the symbolic link and installs the software (the installation program does not know that the software exists). As a result, duplicate software is installed, and the upgrade may fail because of insufficient disk space.

3. Preserve symbolic links to automounted file systems.

Use the Software Manager or the pkgrm (1M) command to remove packages that create files or directories currently automounted. If you cannot remove a package, you can replace the symbolic link after the upgrade is completed.

The automounter is not active during an upgrade, so the suninstall utility installs any package's files or directories that are symbolic links to automounted file systems. If a symbolic link is overwritten, the upgrade may fail because of insufficient disk space.

4. Prevent unneeded file systems from being mounted by commenting out all the file systems in the /etc/vfstab file except root ( / ), /usr , /export,/var , /opt , /proc , /dev/fd , and /tmp ( swap ), if you have not already done so.

During an upgrade, the suninstall utility attempts to mount all of the file systems listed in the /etc/vfstab file on the root file system being upgraded. If the Solaris installation program cannot mount a file system, it reports the failure and exits.

5. Comment out all swap partitions that are not on the same controller as the root disk.

During an upgrade, the suninstall utility attempts to add all of the swap devices listed in the /etc/vfstab file. If the suninstall utility cannot access a swap device, it reports the failure and exits.

6. If any metadevices exist (for example, disk, network, mirrored, striped, or concatenated) for Alternate Pathing, Solstice DiskSuite, Sun Enterprise Volume Manager , or Veritas, refer to the installation instructions for those products and perform the appropriate steps to remove the metadevices.

This step is necessary because the suninstall utility cannot handle metadevices. For more information about these products, refer to their respective user guides.

Caution Caution - Be sure that all metadevices are removed. If any are not, the upgrade fails.

7. If you removed metadevices, reboot the domain to ensure that all of the active metadevices are removed.

domain_name# init 6

8. If the reboot was successful, log in to the domain as superuser.

9. If you are upgrading from Solaris 2.5.1, remove the SUNWxntp packages by using the pkgrm (1M) command.

domain_name# pkgrm SUNWxntp

10. Shut down the domain.

domain_name# shutdown -i0 -g60 -y

11. From the SSP, rename the domain.

ssp% domain_rename -d domain_name -o 5.x

where x is the version of the SunOS, such as 8 or 9. You are done preparing the domain for the upgrade.

12. You can now verify the domain network information, as described in the following section.

For existing machines, the SSP should already be configured with the domain network information; however, to ensure that the information is correct, perform the following steps.

1. Log in to the SSP as superuser.

2. Verify that the Sun Enterprise 10000 host name and IP address are correct in the
/etc/hosts file.

If the information is not correct, see To Configure Domain Network Information for details on updating the domain network information.

3. Verify that the Sun Enterprise 10000 host name and Ethernet address are correct in the /etc/ethers file.

If the information is not correct, see To Configure Domain Network Information for details on updating the domain network information.

4. You can now set up the SSP as an install server, as described in the following section.

Use the SSP as an install server, from which you upgrade the Solaris software on Sun Enterprise 10000 domains. You will need the Solaris 8 or 9 Software 1 of 2 CD to perform this procedure.

1. Insert the Solaris 8 or 9 SPARC Solaris 1 of 2 CD into the CD-ROM drive on the SSP.

Wait for the Volume Manager to mount the CD-ROM.

2. In the SSP window, change to the Tools directory.

ssp# cd /cdrom/cdrom0/s0/Solaris_x/Tools

where x is version of the Solaris operating environment, such as 8 or 9.

3. Set up the host domain as an install client.

ssp# ./add_install_client domain_name sun4u

If the /etc/nsswitch.conf file contains a DNS entry in its host list, you may receive the following warning:

Error: domain_name does not exist in the NIS ethers map.

If you receive this message, you must remove the DNS entry in the /etc/nsswitch.conf file, add the domain_name to the ethers map if the name is not already in the map, and re-run the add_install_client (1M) command.

4. Verify that nfsd (1M) is running on the server.

ssp# ps -ef | grep nfsd

If you see any entry containing /usr/lib/nfs/nfsd , then nfsd is running on your system.

5. If nfsd is not running, type:

ssp# /etc/init.d/nfs.server start

6. Use the share (1M) command to share the CD across the network.

ssp# share -F nfs -o ro,anon=0 /cdrom/cdrom0/s0

7. Exit the superuser level.

You are done setting up the SSP as a boot server.

8. You can now bring up the domain, as described in the next section.

1. In an SSP window, ensure that the SUNW_HOSTNAME variable is set to the proper domain name.

ssp% domain_switch domain_name

2. Use the domain_status (1M) command to verify that the OS version is set to 5.8.

ssp% domain_status -d domain_name

3. Bring up the domain.

ssp% bringup -A off

If this is the first domain to be brought up, you will be prompted to configure the centerplane. Type y to confirm if you are sure that no other domains are running. Responding yes resets the entire platform; therefore, you must be sure that no other domains are running.

This bringup will configure the Centerplane. Please confirm (y/n)? y

After a few minutes the SSP prompt is displayed.

4. At the ssp prompt, open a netcon (1M) session.

ssp% netcon -g

After a few minutes the ok prompt is displayed.

You are done bringing up the domain.

5. You can now set up the OpenBoot PROM, as described in the next section.

1. Drop down to the OpenBoot prompt in the netcon (1M) window:

domain_name# ~#

2. Use the devalias command to check for duplicate device aliases in the OpenBoot PROM.

The installation and upgrade utility, suninstall , may not work properly if you have defined duplicate devaliases in the OpenBoot PROM. Use the devalias command to check the aliases. The output may resemble the following example:

ok devalias

net            /sbus@41,0/qec@0,20000/qe@1,0

ttya           /ssp-serial

ssa_b_example  /sbus@40,0/SUNW,soc@0,0/SUNW,pln@b0000000,XXXXXX/SUNW,ssd@0,0:a

ssa_a_example  /sbus@40,0/SUNW,soc@0,0/SUNW,pln@a0000000,XXXXXX/SUNW,ssd@0,0:a

isp_example    /sbus@40,0/QLGC,isp@0,10000/sd@0,0

net_example    /sbus@40,0/qec@0,20000/qe@0,0

net            /sbus@41,0/qec@0,20000/qe@0,0

ok

3. If any duplicate entries exist in the devalias list, remove them.

The following example removes the last-created net device alias. You may have to issue a second nvunalias command if the second net alias is the incorrect one. Then issue an nvalias command to create the correct net device alias.

ok nvunalias net

4. Run the watch-net-all command to display the functioning network interfaces and determine which device passes all the device tests.

In the following example for a Sun Quad FastEthernet interface, the last network interface is the connection for which all device tests passed. The display on your network may differ from the example below.

ok  watch-net-all

/sbus@4c,0/SUNW,qfe@0,8c30000

Internal loopback test -- succeeded.

Transceiver check  -- failed

/sbus@4c,0/SUNW,qfe@0,8c20000

Internal loopback test -- succeeded.

Transceiver check  -- failed

/sbus@4c,0/SUNW,qfe@0,8c10000

Internal loopback test -- succeeded.

Transceiver check  -- failed

/sbus@4c,0/SUNW,qfe@0,8c00000

Internal loopback test -- succeeded.

Transceiver check  -- passed

Looking for Ethernet Packets.

'.' is a Good Packet.  'X' is a Bad Packet.

Type any key to stop.

5. If a net alias does not exist for the network interface that is on the same subnet as the SSP, create one

ok nvalias net /sbus@xx,0/SUNW,network_interface_card

where:

xx is a hexadecimal value that represents the system board and system I/O slot.

network_interface_card is the device name that defines a network interface installed in the specified slot.

In the following example,

ok nvalias net /sbus@4c,0/SUNW,qfe@0,8c00000

/sbus@4c,0 refers to system board 3 and SBus 0.

The /SUNW,qfe@0 portion of the device name defines a Sun Quad FastEthernet network interface installed in Slot 0. This information is site-specific; thus, your configuration may vary.

The following table contains the SBus numbers used in the devalias file.

6. You can now upgrade the Solaris operating environment, as described in the following section.

This section explains the tasks specific to the installation of the Solaris operating environment on a Sun Enterprise 10000 domain, using the SSP as an install server (for details, see To Set Up the SSP as an Installation Server ). For general instructions on installing the Solaris operating environment from a remote CD-ROM, refer to the Solaris 8 Advanced Installation Guide or the Solaris 9 Installation Guide .

This section describes how to:

• Run boot net to install the Solaris operating environment

• Finish the suninstall process

The steps that follow modify the suninstall procedures. For more details, refer to the Solaris installation instructions in your Solaris Media Kit.

In the netcon (1M) window, boot the system from the network.

ok boot net

The boot net command starts the suninstall utility. This utility prompts you to provide site and platform-specific information. The following table describes the Sun Enterprise 10000-specific information that you need to provide during the upgrade.

For details on changing the installation CDs during the upgrade, see the following section.

As you proceed with the installation process, you will have to change CDs. This process requires that you unshare the CD in the CD-ROM drive and share the next CD to be installed.

1. In another window, log into the SSP as superuser.

2. Unshare the CD, then eject it from the CD-ROM drive.

ssp# unshare /cdrom/cdrom/s0

ssp# eject cdrom

3. Insert the next CD in the CD-ROM drive and share it.

ssp# share -F nfs -o ro, anon=0 /cdrom/cdrom0

4. From the domain installation window, where you are prompted for the installation image, specify the path of the CD image:

sspname: /cdrom/cdrom0

5. Unshare the CD, then eject it from the CD-ROM drive.

ssp# unshare /cdrom/cdrom0

ssp# eject cdrom

6. Repeat Steps 3, 4, and 5 for each CD to be installed.

7. After the last CD is installed, reboot the domain, unless you indicated earlier in the upgrade process to have the domain automatically rebooted.

8. Continue with the domain post-installation tasks, which are described in the next section.

This section describes the tasks that you must complete after installing the Solaris operating environment on a Sun Enterprise 10000 domain. This section describes how to:

• Configure the default boot disk

• Install additional software packages

• Configure the Network Time Protocol (NTP) configuration file

• Verify the domain upgrade

1. After the operating system is loaded and the superuser prompt is displayed, list the devices entry for your boot disk.

domain_name# ls -l /dev/dsk/root_partition_device

where root_partition_device is in the form c x t x d x s x .

If you need a list of the device types for each partition, type the following in the root directory:

domain_name# df -lk 

2. Copy the part of the device string that begins with either /sbus or /pci .

Example:

/sbus@65,0/SUNW,fas@1,8800000/sd@3,0:a .

Record your device string in a place where you can easily refer to it.

Use the device string for the device to be used as the default boot device. At this point in the installation, you can set it to any valid boot disk in the domain.

3. In the netcon (1M) window, drop down to the OpenBoot PROM prompt.

domain_name# ~#

4. Assign the device string to an alias (see Step 2 for the device_string ).

ok nvalias bootdisk_alias device_string

As in this example, the nvalias command should be entered on a single line.

5. Store the cache for the device.

ok nvstore  

6. Use the setenv command to set the default boot-disk alias to the correct device.

ok setenv boot-device bootdisk_alias

where bootdisk_alias corresponds to the user-defined alias you established in Step 4.

The device should correspond to the device that you want to use as the boot disk, which may be different than the device on which you just installed the Solaris operating environment.

7. At the OpenBoot PROM prompt, type go to exit the OpenBoot PROM and return to the domain prompt.

ok go 

You are done configuring the default boot device.

8. You can now install additional software packages, as explained in the next section.

Additional software packages are in separate media. Install the software packages one at a time, from the appropriate media. For example, you can install packages, such as the AnswerBook2 package from the Sun Computer Systems Supplement CD.

1. In an SSP window, use the unshare(1M) command and eject the CD in the CDROM drive.

ssp# unshare /cdrom/cdrom0

ssp# eject cdrom

2. Insert the appropriate installation CD into the CD-ROM drive on the SSP.

3. Log in as superuser on the SSP and share the CD-ROM.

ssp# share -F nfs -o ro,anon=0 /cdrom/cdrom0

4. Log in to the domain as superuser in the netcon (1M) window.

5. Create and mount the /cdrom directory on the domain.

domain_name# mkdir /cdrom

domain_name# mount ssp_name:/cdrom/cdrom0 /cdrom

6. Add the software package. For example,

domain_name# cd /cdrom/install_disk_name

domain_name# pkgadd -d . software_package_name

where:

install_disk_name is the name of the installation disk from which you are installing

software_package_name is the name of the software package you are adding.

The pkgadd (1M) command may display several messages and ask several installation questions for each package, some relating to space, others asking whether it is OK to continue. After answering these questions, and when asked whether to proceed, answer y to indicate yes.

7. In the netcon(1M) window, unmount the CD.

domain_name# cd /

domain_name# umount /cdrom

8. Log in to the SSP as superuser and remove the installation CD from the CD-ROM drive.

ssp# cd /

ssp# unshare /cdrom/cdrom0

ssp# eject cdrom

9. Install and configure any other purchased software packages.

1. After you install any additional software packages, configure the ntp.conf file for each domain, to synchronize clocks between the SSP and its domain.

For details on configuring the domain ntp.conf file, which resides at /etc/inet/ntp.conf , refer to Configuring the Network Time Protocol Daemon .

For more information about NTP commands, refer to the xntp (1M) man page in the man Pages(1M): System Administration Commands section of the Solaris Administration AnswerBook2 Collection.

2. You can now verify the upgrade, as described in the following section.

1. Uncomment all swap partitions that are not on the same controller as the root disk.

2. Check the operating mode.

domain_name# isainfo -k

If you are running in 64-bit mode, you should get the following output:

sparcv9

If you are running in 32-bit mode, you should get the following output:

sparc

3. From the SSP window, use the ps (1) command to ensure that the Event Detector Daemon (EDD) is running and the edd_cmd (1M) command to ensure that the EDD is running in the proper mode before you attempt to reboot the domain (refer to the edd (1M) man page).

4. If you intend to run DR model 3.0 on the domain, consider switching DR models (from model 2.0 to 3.0) at this time, then proceed to Step 5.

If you switch DR models now, you can avoid a reboot of the domain later. For details on how to switch DR models, refer to the Sun Enterprise 10000 Dynamic Reconfiguration User Guide.

5. Reboot the domain with the proper operating mode.

For the Solaris 8 10/01 operating environment, you can use either the 32-bit mode or the 64-bit mode. The 64-bit mode is the default for all sun4u platforms.

• For 32-bit mode, type:

  domain_name# reboot "bootdisk_alias kernel/unix"

  
  

• For 64-bit mode, type one of the following commands.

  If you are already in 32-bit mode, use the following command.

  domain_name# reboot bootdisk_alias

  
  

  If the domain is on the default disk, you do not need to specify the bootdisk_alias .

  If you are switching from the 32-bit mode to the 64-bit mode, use the following command.

  domain_name# reboot "bootdisk_alias kernel/sparcv9/unix"

  
  

  You are done with the upgrade process.

Licensing Your Software

The Sun Enterprise 10000 domain feature requires different approaches to software licensing than systems that cannot be logically partitioned.

FLEXlm-Based Licensing

License management (the license server) is normally tied to a machine host ID. On a Sun Enterprise 10000 system, the license server is tied to the domain host ID. Each domain receives its own domain host ID.

Therefore, if licensing is installed on a Sun Enterprise 10000 system, it must be installed in a domain that will not be removed. Adding or removing processors from the domain will not affect licensing, as long as the domain always has at least one active processor.

If licensing ever needs to be moved from one domain to another, the licenses will need to be regenerated using the new domain host ID. This is identical to the situation when moving the license server from one machine to another. This process is called a server move ; contact the Sun License Center to request a server move .

For more licensing information, use the following Sun License Center URL:

http://www.sun.com/licensing

Type hostid in a shell window.

Other Software Licensing

Other software vendors may have unique software licensing policies for their products running on Sun Enterprise 10000 systems. All major independent service providers have been notified and should have software policies in place. For additional information, contact your Sun service provider.

Sun Enterprise 10000 SSP 3.5 Installation Guide and Release Notes

816-3626-10

Copyright © 2002, Sun Microsystems, Inc. All rights reserved.