| System Management Services (SMS) 1.4 Installation Guide |     |
| System Management Services (SMS) 1.4 Installation Guide | |
| C H A P T E R 6 |
|
SMS 1.4 Software and Domains |
This chapter contains additional instructions for System Management Services (SMS) 1.4 software and domains. These instructions apply to the Sun Fire high-end server systems.
To Set Up OpenBoot PROM Environment Variables for the Domain
To Set up the Network Install Server on the System Controller
To Set Up OpenBoot PROM Environment Variables for the Domain
To Change the Hostname of a Domain or SC
This section describes the recommended procedures for setting up and installing the Solaris operating environment for the domain:
|
Note - If you had the Solaris operating environment pre-installed on your system or you have run the sys-unconfig command on the domain please see Unconfigured Domains before proceeding. |
|
|
We strongly recommend creating an install server to install the Solaris operating environment software for a domain over the network.
You should be familiar with setting up network install servers before beginning this procedure.
For information on configuring network install servers, refer to the Solaris 9 Installation Guide.
Refer to the Solaris 9 Installation Guide for information on setting up the spare SC as an install client.
For partition and Solaris operating system distribution information see SMS 1.4 Software on the SC.
After you have created an install server on sc0, you are ready to install the Solaris operating environment 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.
|
Caution - If you are installing the Solaris OE from more than one jumpstart server, be sure you have only one jumpstart boot server per subnet. If you have more than one jumpstart boot server per subnet, run the rm-install-client command on the extra servers and leave only the SC as the jumpstart boot server. |
Refer to the Solaris 9 12/02 Reference Manual for more information about the add_install_client(1M) and rm-install-client(1M) commands.
1. Obtain the MAN network Ethernet address at the OpenBoot PROM prompt by typing:
The output displayed is an example only and does not reflect the specific information that will appear 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 |
install_dir_path specifies the directory where the CD images were copied.
domain_man_etheraddr is the Ethernet address for the domain.
scI1_hostname is the hostname given to the SC I1 network during the smsconfig -m procedure.
domain_hostname is the name given to the domain I1 network interface assigned during the smsconfig -m procedure.
See "To Configure the Management Network (MAN) Using the smsconfig(1M) Command." The domain host name was originally defined on the worksheet in the Sun Fire 15K/12K System Site Planning Guide.
1. Display the functioning network interfaces.
If watch-net-all reports a failure on the device associated with man-net, you will need to contact your Sun representative.
2. Network boot the domain from the SC using the Management Network. Type:
3. Install the Solaris operating environment for the domain.
Refer to the Solaris 9 Installation Guide for detailed installation instructions. Refer to your Sun Fire 15K/12K System Site Planning Guide for site specific and system dependent information when prompted during installation.
|
Note - You can choose any Solaris locale you wish for the operating environment on the domain. The SC must have the English locale installed but the domains do not. |
4. Change the domain nodename.
When using the SC as an install server for a domain, change the domain's nodename after the installation is complete. This reduces the amount of network traffic generated between the domain and SC over the MAN network. Change the nodename of the domain to the hostname of one of its external network interfaces (for example, qfe0).
To change the domain's nodename do the following:
5. Remove the domain from the network install server list.
After installing the domain software, to remove the domain from the install server list:
|
Caution - If you do not remove the domain from the install server list the domain will not boot from the boot disk or the net! |
Log in to the SC as superuser.
Type:
In preparation for Step 4 of the next procedure, note the physical disk location. For example, type:
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 |
Log out.
|
|
1. At the domain console's ok prompt, remove any duplicate entries in the devalias list.
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; the last one 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.
|
Note -
Note - If the system is using a FastEthernet board with Lucent PHY, an error message claiming the device failed the test may appear. Ignore the error message or set the OpenBoot PROM (OBP) parameter diag-switch? to false. Changing the switch setting will keep the error message from reappearing.
4. Set the bootdisk_alias so that it refers to the device on which you are installing the Solaris operating environment . bootdisk_alias is the alias for the device on which you are installing the Solaris operating environment device_string is the string for the device on which you are installing the Solaris operating environment as displayed in Step 3.
5. Record the newly created NVRAM data. 6. Use the setenv command to set the default boot device to the correct alias. bootdisk_alias is the user-defined alias you established in Step 4. The boot device must correspond to the a bootable disk on which you are installing the operating environment. This variable will be used in case of a panic and auto-boot. It is very important to set this variable correctly. 7. Now that you have set up an alias for your boot device, boot the disk by typing: If you had the Solaris operating environment pre-installed on a domain or have run the sys-unconfig(1M) command on a domain, you must configure the MAN network information on that domain manually.
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 what's in /etc/syslog.conf: If not, edit the /etc/syslog.conf file. Save and exit.
manc_dom_ipaddr is the domain IP address listed in /etc/netmasks. 7. The domain is now configured. Creating a Domain This section describes the following procedures for creating a new domain: For the examples in this guide: 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. domain_id is the ID of the domain (A through R) that you are creating location corresponds to board location. The following location forms are accepted: 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 location is the board location. The following location forms are accepted: For example, the following command removes the CPU board in slot 2 of slot 0 from domain A. The next example removes an I/O board in slot 3 of slot 1 from domain A. domain_id is the ID of the domain (A through R) you are creating. domain_tag is the name of the new tag you are adding for the domain, such as domainA. 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. 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 platform configuration database (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.4 Reference Manual. 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. domain_id is the ID of the domain (A through R) you want to activate position is whether you want the virtual keyswitch in the on (activate), off (deactivate), standby, diag, or secure position. 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 network console are as follows:
1. Bring up an active console window for the domain domain_id is the ID of the domain (A through R) for which you want to bring up a console. For example, the following command brings up a console for domain A. In the domain console window, 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 window. For more information on domain console refer to the System Management Services (SMS) 1.4 Administrator Guide and the console man page. Making Changes to a Domain This section describes how to change the IP address or hostname of a domain or system controller.
1. Update your name service maps with the new IP address(es). 2. Reboot the domain or system controller.
1. Update your name service maps with the new hostname(s). Change the hostname in the following files in the domain: /etc/hostname.interface-card-name Change the hostname in the following files, if applicable: etc/defaultdomain (only if your NIS domain name has changed) etc/hostname.* (only if you hostname is specified in the file) etc/hostname6.* (only if you hostname is specified in the file) If the hostname was changed in the SC, run smsconfig -m.
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.4 Reference Manual. 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. domain_id is the ID of the domain (A through R) you want to activate position is whether you want the virtual keyswitch in the on (activate), off (deactivate), standby, diag, or secure position. 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 network console are as follows:
1. Bring up an active console window for the domain domain_id is the ID of the domain (A through R) for which you want to bring up a console. For example, the following command brings up a console for domain A. In the domain console window, 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 window. For more information on domain console refer to the System Management Services (SMS) 1.4 Administrator Guide and the console man page.
Copyright © 2003, Sun Microsystems, Inc. All rights reserved. |
To Set up the Network Install Server on the System Controller