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

The installation of the Solaris operating environment on Sun Enterprise 10000 domains involves various tasks that you must perform before and after the actual installation. This chapter provides an overview of the domain installation process and detailed information on the following:

• What you need to start the installation process

• Domain pre-installation tasks

• Domain installation tasks specific to the Sun Enterprise 10000 server

• Domain post-installation tasks

Caution - If you are installing 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, 3.3, 3.4, or 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 SSP Installation Guide and Release Notes for the SSP version to be installed.

The basic installation scenarios for the Sun Enterprise 10000 server consist of the following:

• Creating a new domain running the Solaris 8 10/01 operating environment and establishing the SSP as an install server

  or

• Installing a fresh copy of the Solaris 8 10/01 operating environment on an existing domain using the SSP as an install server

TABLE 8-1 illustrates the tasks involved in installing the Solaris operating environment on a Sun Enterprise 10000 server. Your installation scenario determines where you start the installation process. For example, if you are performing a fresh install of the Solaris operating environment on an existing domain, you do not need to create a new domain.

You must complete the appropriate tasks in the order shown in TABLE 8-1 . The following sections in this chapter provide further information about each task. These tasks can take a considerable amount of time to complete, depending on the configuration of the server and the site in which it resides.

You must be very familiar with your site configuration and the configuration of the server before you start a fresh install. Some of the information can be obtained from the server configuration files.

The following list identifies the information that you must obtain before starting the installation process:

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

This section describes the prerequisite tasks and procedures that you must complete before installing the Solaris operating environment on a Sun Enterprise 10000 domain. Depending on your system configuration and your installation scenario, you may not need to complete all the tasks. In this section you will find how to

• Create a domain by

  • Creating the eeprom.image file for the new domain

  • Creating the new domain on the SSP

• Configure domain network information

• Set up the SSP as an install server

• Bring up the domain to the OpenBoot PROM level

• Set up the OpenBoot PROM environment

1. Obtain the system identification key and the host ID from your Sun service provider.

2. Log in to the SSP as user ssp.

3. When prompted for the SUNW_HOSTNAME variable, use either the platform name or the name of any existing domain.

4. Use the sys_id (1M) command to create the eeprom.image file.

ssp% sys_id -h hostid -k key  \

-f $SSPVAR/.ssp_private/eeprom_save/eeprom.image.domain_name

where:

hostid is the number provided with the key.

key is the EEPROM key number.

domain_name is the hostname of the new domain.

For details on the valid hostid and key numbers, see the sys_id (1M) man page.

5. Execute the following sys_id (1M) command to check the results.

ssp% sys_id -d -f \ 

$SSPVAR/.ssp_private/eeprom_save/eeprom.image.domain_name

In the following example, 49933C54C64C858CD4CF is the key and 0x80a66e05 is the hostid :

ssp% sys_id -h 0x80a66e05 -k 49933C54C64C858CD4CF \

-f $SSPVAR/.ssp_private/eeprom_save/eeprom.image.domain_name

ssp% sys_id -d -f $SSPVAR/.ssp_private/eeprom_save/ \

eeprom.image.domain_name

IDPROM in eeprom.image.domain_name

Format = 0x01

Machine Type = 0x80

Ethernet Address = 0:0:be:a6:6e:5

Manufacturing Date = Wed Dec 31 16:00:00 1997

Serial number (machine ID) = 0xa66e05

Checksum = 0x3f

6. Back up the SSP eeprom.image files to tape or disk where they can be accessed in case of an SSP boot-disk failure.

You are done creating the eeprom.image file for the domain.

7. You can now build the new domain on the SSP, as described in the following section.

1. Log in to the SSP as user ssp .

2. When prompted for the SUNW_HOSTNAME variable, specify the platform name of the domain that you wish to create.

Ensure that the domain name corresponds with the hostname of the domain in which the operating system is to be installed. Platform names must not be longer than 14 characters.

3. Use the domain_create (1M) command to create the domain.

ssp% domain_create -d domain_name -b board_numbers -o \

 5.8 -p platform_name

where:

domain_name is the name of the domain specified in Step 2.

board_numbers is a list of the system boards, delimited by spaces, to be included in the domain.

5.8 (or 5.9 ) is the version of the operating system on the domain.

platform_name is the name of the platform as defined during the SSP package configuration.

For additional information, refer to the Sun Enterprise 10000 SSP User Guide appropriate to the SSP release that you are using.

4. Use the domain_switch (1M) command to switch to the target domain.

ssp% domain_switch domain_name

5. If you have determined that elements of the domain are powered off, power on those elements.

ssp:domain_name% power -on

You are done creating the domain.

6. You can now configure the domain network information, as described in the next section.

If you just created a new domain, update the following on the SSP:

• The /etc/hosts file to include the new domain name and its corresponding IP address

• Optionally, the /etc/ethers file, if you have an Ethernet address for the new domain

1. Log in to the SSP as superuser.

2. Manually edit the /etc/hosts file to include the IP address of the new domain.

You must get the IP address from your network administrator.

The correct entries would look similar to the following /etc/hosts sample. Note that the new entry is tacos :

129.153.49.185     tacos

127.0.0.1          localhost

129.153.49.179     snax-ssp vegetables     loghost

129.153.49.181     snax-cb0

129.153.49.182     snax-cb1

129.153.49.180     pizza

129.153.49.183     chips

129.153.49.1       marvin-49

110.0.0.1          vegetables-priv

110.0.0.5          chips-priv

The /etc/hosts file is actually a link to /etc/inet/hosts .

Caution Caution - If the new domain entry follows any other host or SSP entry, the add_install_client command may not work in Step 4 of the next procedure.

3. If the domain has an Ethernet address, manually edit the /etc/ethers file to include the Ethernet address.

The correct entries would look similar to the following /etc/ethers sample. Note that tacos represents the name of the new domain in this example:

8:0:20:87:58:a5     snax-ssp vegetables

0:0:be:01:00:1e     snax-cb0

0:0:be:01:00:57     snax-cb1

0:0:be:a6:50:2f     pizza

0:0:be:a6:6f:19     chips-priv

0:0:be:a6:6f:23     nachos

0:0:be:a6:6f:2a     tacos

You are done configuring the domain network information.

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

Use the SSP as an install server, from which you install the Solaris software on a Sun Enterprise 10000 domain. You need the Solaris 8 or 9 SPARC Solaris 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.

After inserting the CD, wait for the volume manager to mount the CD-ROM.

2. Log in to the SSP as superuser.

3. Change to the Tools directory on the CD.

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

4. 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 need to 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.

5. 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.

6. If nfsd is not running, type:

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

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

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

8. Exit the superuser level.

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

9. You can now bring up the domain, as explained in the next procedure.

1. As user ssp, use the domain_switch (1M) command to switch to the target domain.

2. 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 continue 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. Review the output of the bringup (1M) command. If errors occurred, you must correct those errors before you proceed. If no errors occurred, continue to the next step.

3. In the SSP window, open a netcon (1M) session.

ssp% netcon -g

The ok prompt is displayed after a few minutes. The duration depends directly on the size of the domain.

You are done bringing up the domain.

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

1. Drop down to the OpenBoot prompt and use the devalias command to check for duplicate devaliases entries in the OpenBoot PROM.

The installation utility, suninstall , may not work properly if you have defined duplicate devaliases in 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

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

The following example removes the last-created net devalias . 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

3. 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.

4. 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.

/SUNW,qfe@0 is the portion of the device name that 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.

5. You can now run boot net to start 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 (explained in To Set up the SSP as an Installation Server ). For general details 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

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. See the following table for details on the information specific to the Sun Enterprise 10000 server that you need to provide during installation.

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 and eject it from the CD-ROM drive.

ssp# unshare /cdrom/cdrom0/s0

ssp# eject cdrom

3. Insert the next CD into 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 installation 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 you must complete after installing the Solaris operating environment on your Sun Enterprise 10000 domains. 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 installation

• License your software

1. If you partitioned your disk during installation (see To boot net the Operating Environment to the Domain ) verify the partitions and their corresponding devices by typing the following in the root directory:

domain_name# df -lk 

2. 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 .

3. Copy the part of the 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 you want to use as the default boot device. At this point in the installation, you can set it to any valid boot disk in the domain.

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

domain_name# ~#

5. Assign the device string to an alias (see Step 3 for the device_string ).

ok nvalias bootdisk_alias device_string

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

6. Store the cache for the device.

ok nvstore  

7. 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 5. 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.

8. 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.

9. 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, then eject the CD in the CDROM drive.

ssp# unshare /cdrom/cdrom0/s0

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.

domain_name# cd /cdrom/install_cd_name

domain_name# pkgadd -d . software_package_name

where:

install_cd_name is the name of the installation CD 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, when asked whether to proceed, answer y .

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 , see Configuring the Network Time Protocol Daemon .

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

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

1. 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

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

3. 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, and proceed to Step 4.

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.

4. 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 64-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"

  
  

5. You are done with the fresh install unless you need to license your software, as described in the following section.

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.