| System Management Services (SMS) 1.6 Installation Guide |    
|
| System Management Services (SMS) 1.6 Installation Guide |
|
| C H A P T E R 5 |
|
Setting Up and Installing Software on Domains |
This chapter contains the following instruction for installing the Solaris Operating System and additional software packages on Sun Fire high-end system domains:
This section describes the following procedures for creating a new domain:
|
Note - You must have a valid idprom.image file for the domain in the /var/opt/SUNWSMS/data/domain_id directory to create a domain. Contact your Sun service representative if this file is missing. |
|
The examples in this guide use the definitions in TABLE 5-1 for the various system prompts.
The privileges allotted to the user are determined by the platform or domain groups to which the user belongs. In these examples, the sms-user is assumed to have both platform and domain administrator privileges, unless otherwise noted.
1. Log in as a user with platadmn privileges, and create a domain by adding boards.
For example, the following command adds CPU boards in slots 2, 4, and 7 to domain A.
The next example adds I/O boards in slots 3, 5, and 8 to domain A.
2. Use the deleteboard(1M) command if you need to remove boards from an inactive domain.
where location is the board location. The following location forms are accepted.
For example, the following command removes the CPU board in slot 2 from domain A.
The next example removes the I/O board in slot 3 from domain A.
3. Use the addtag(1M) command to add a tag for the domain.
For example, the following command adds the tag for domain A to the platform configuration database (PCD).
4. Use the deletetag(1M) command if you want to remove a tag.
where domain_id is the ID of the domain from which you want to remove a tag (A through R).
For example, the following command deletes the tag for domain A from the PCD.
|
SMS contains a virtual key switch for each domain, which controls the states of the domain. The showkeyswitch(1M) command displays the position of the virtual key switch, and the setkeyswitch(1M) command changes the position of the virtual key switch. The valid positions of the virtual key switch are on, standby, off, diag, and secure. For more information, refer to the System Management Services (SMS) 1.6 Reference Manual.
where domain_id is the ID of the domain (A through R) for which you want to check status.
For example, the following command shows the status of domain A.
2. Activate the domain as a user with domain administrator (dmnaadmn) privileges.
For example, the following command activates domain A.
3. If you need to deactivate a domain, set the position of the virtual keyswitch to off.
For example, the following command deactivates domain A.
|
The conditions required for a network console are:
Open an active console for the domain.
where domain_id is the ID of the domain (A through R) for which you want to open a console.
For example, the following command opens a console for domain A.
In the domain console, vi(1) runs properly and the escape sequences (tilde commands) work as intended only if the environment variable TERM has the same setting as that of the console.
For more information on the domain console, refer to the System Management Services (SMS) 1.6 Administrator Guide and the console man page.
This section describes the recommended procedures for setting up and installing the Solaris OS for the domain
|
Note - If you had the Solaris OS preinstalled on your system or you have run the sys-unconfig(1M) command on the domain, see Configuring Domain Networks before proceeding. |
To be most efficient, create an install server to install the Solaris OS software for a domain over the network. You should be familiar with setting up network install servers before beginning this procedure. Following are sources for more information.
|
After you have created an install server on sc0, you are ready to install the Solaris OS software for the domain over the network. The system needs to identify the name of the domain, and you add this information by using the add_install_client(1M) command.
Refer to the reference manual for your version of the Solaris OS for more information about the add_install_client(1M) and rm_install_client(1M) commands.
1. Obtain the MAN Ethernet address at the OpenBoot PROM prompt by typing the following.
The output displayed is an example only and does not reflect the specific information that appears on your system.
2. As superuser on SC0, set up the host domain as an install client.
sc0: # /install_dir_path/Solaris_9/Tools/add_install_client -e domain_man_etheraddr -s scI1_hostname:/install_dir_path -c scI1_hostname:/install_dir_path domain_hostname sun4u |
You originally defined the domain host name (for example, SC I1) on the worksheet in the site planning guide for your Sun Fire system.
|
1. Display the functioning network interfaces.
If watch-net-all reports a failure on the device associated with man-net, contact your Sun representative.
2. Network boot the domain from the SC using the Management Network (MAN).
Install the Solaris OS for the domain.
Refer to the installation guide for your version of the Solaris OS for detailed installation instructions. Refer to the site planning guide for your Sun Fire high-end system for site-specific and system-dependent information when prompted during installation.
|
Note - You can choose any Solaris OS locale you want for the operating system on the domain. The SCs must have the English locale installed, but the domains do not have the same requirement. |
3. Change the domain node name.
When using the SC as an install server for a domain, change the domain's node name after the installation is complete. This reduces the amount of network traffic generated between the domain and SC over the MAN. Change the node name of the domain to the node name of one of its external network interfaces (for example, qfe0).
To change the domain's node name, do the following.
a. Log in to the domain as superuser.
b. Type the following commands at the prompts, substituting the node name you chose for new_nodename.
4. Remove the domain from the network install server list.
After installing the domain software, take these steps to remove the domain from the install server list.
|
Caution - If you do not remove the domain from the install server list, the domain does not boot from the boot disk or from the network. |
a. Log in to the SC as superuser.
c. In preparation for Step 4 of the next procedure, note the physical disk location.
For example, type the following.
sc0:#ls -la /dev/dsk/c0t17d0s0 lrwxrwxrwx 1 root root 77 Oct 12 17:38 /dev/dsk/c0t17d0s0 -> ../../devices/pci@3c,600000/pci@1/SUNW,qlc@4/fp@0,0/ssd@w21000020370dac0c,0:a |
|
1. At the domain console's ok prompt, remove any duplicate entries in the devalias list.
where duplicate_alias is the alias of the duplicate entry.
|
Note - This sequence must be repeated once per duplication. nvunalias removes only one device alias at a time; it removes the last entry in the list of device aliases. |
2. Display the OpenBoot PROM device tree to use in creating the device aliases.
3. Display the functioning network interfaces.
4. Set the bootdisk_alias so that it refers to the device on which you are installing the Solaris OS.
|
Note - Enter the nvalias command on a single line. In the preceding example, the ssd in the physical disk location changed to disk in the boot string. |
5. Record the newly created NVRAM data.
|
Note - Make sure that the OpenBoot PROM parameter use-nvramrc is set to True so that the new user-defined bootdisk_alias is evaluated during startup. |
6. Use the setenv command to set the default boot device to the correct alias.
where bootdisk_alias is the user-defined alias you established in Step 4. The boot device must correspond to the bootable disk on which you are installing the Solaris OS. Be sure you set this variable correctly, because it is used in case of a panic and autoboot.
7. Now that you have set up an alias for your boot device, boot the disk by typing the following.
If you had the Solaris OS preinstalled on a domain or if you ran the sys-unconfig(1M) command on a domain, you must manually configure the MAN information on that domain.
|
Note - Do not add the domain as an install client on the SC before booting the domain, as described in To Set Up the Domain as an Install Client. |
|
1. Log in to the domain as superuser.
The following is an example of the output displayed.
3. Add or edit a network-i1 entry to /etc/netmasks, using the following format.
4. Create an /etc/hostname.dman0 file with the following content.
5. Ensure that the manc_sc_ipaddr IP address matches the corresponding entry in /etc/syslog.conf.
If the two entries do not match, edit the /etc/syslog.conf file. Save the file and exit.
domain_id:# ifconfig dman0 plumb domain_id:# ifconfig dman0 manc_dom_ipaddr netmask + broadcast + private up |
where manc_dom_ipaddr is the domain IP address listed in /etc/netmasks.
The additional software packages are on separate media. Install the software packages to the domains one at a time.
There is no particular order in which the packages must be installed. Following are additional packages that you might want to install:
Studio 11 tool set and compilers
ClusterTools 5
|
Log in to the SC as superuser.
7. Insert the installation CD for the software you want to install into the CD-ROM drive on the SC.
8. Use the share(1M) command to share the CD across the network.
a. Verify that the nfsd server is running.
b. Add a CD-ROM entry to the /etc/dfs/dfstab file.
c. Propagate the CD-ROM image to NFS.
9. Log in to the domain as superuser.
10. Create and mount the /cdrom directory for the domain.
where SC-I1: is the node name you specified for the SC I1 network.
11. Add the additional software package.
The pkgadd(1M) command might display several messages and ask several installation questions for each package, some relating to space, others asking whether it is OK to continue. Answer these questions, and when asked whether to proceed, answer yes.
13. Log out of the domain and log in to the SC as superuser.
14. Eject the installation CD from the CD-ROM drive on the SC.
| System Management Services (SMS) 1.6 Installation Guide | 819-4659-10 |
|
Copyright © 2006, Sun Microsystems, Inc. All Rights Reserved.
To Build a New Domain on the System Controller
