Sun platforms that support the Logical Domains software come preinstalled with the Solaris 10 OS. Initially, the platform appears as a single system hosting only one operating system. After the Solaris OS, system firmware, and Logical Domains Manager have been installed, the original system and instance of the Solaris OS become the control domain. That first domain of the platform is named primary, and you cannot change that name or destroy that domain. From there, the platform can be reconfigured to have multiple domains hosting different instances of the Solaris OS.
On a brand new system, you may want to reinstall the OS so that it conforms to your installation policy. In that case, refer to Required and Recommended Solaris OS in Logical Domains 1.3 Release Notes to find the Solaris 10 OS that you should use for this version of the Logical Domains software. Refer to your Solaris 10 OS installation guide for complete instructions for installing the Solaris OS. You can tailor your installation to the needs of your system.
If your system is already installed then it needs to be upgraded to the appropriate Solaris 10 OS that should be used for this version of the Logical Domains software. Refer to Required Software and Patches in Logical Domains 1.3 Release Notes to find the Solaris 10 OS that you should use for this version of the Logical Domains software and the required and recommended patches. Refer to the Solaris 10 10/09 Release and Installation Collection for complete instructions for upgrading the Solaris OS.
The following tasks describe how to update system firmware by using the Advanced Lights Out Manager (ALOM) software.
For information about updating the system firmware by using the Integrated Lights Out Manager (ILOM) software, see “Update the Firmware” in Sun SPARC Enterprise T5120 and T5220 Servers Topic Set.
You can find system firmware for your platform at the SunSolve site.
Refer to Required System Firmware Patches in Logical Domains 1.3 Release Notes for required system firmware by supported servers.
This procedure describes how to upgrade system firmware using the flashupdate command on your service processor.
If you do not have access to a local FTP server, see Upgrade System Firmware Without an FTP Server.
If you want to update the system firmware from the control domain, refer to your system firmware release notes.
Refer to the administration guides or product notes for the supported servers for more information about installing and updating system firmware for these servers.
Shut down and power off the host server from either management port connected to the service processor: serial or network.
# shutdown -i5 -g0 -y
Use the flashupdate command to upgrade the system firmware, depending on your server.
Refer to your platform documentation for information about how to update your firmware.
The following shows a sample flashupdate command:
sc> flashupdate -s IP-address -f path/Sun_System_Firmware- x_x_x_build_nn-server-name.bin username: your-userid password: your-password
IP-address is the IP address of your FTP server.
path is the location in SunSolvesm or your own directory where you can obtain the system firmware image.
x_x_x is the version number of the System Firmware.
nn is the number of the build that applies to this release.
server-name is the name of your server. For example, the server-name for the SPARC® Enterprise T5440 server is SPARC_Enterprise_T5440.
Reset the service processor.
sc> resetsc -y
Power on and boot the host server.
sc> poweron -c ok boot disk
If you do not have access to a local FTP server to upload firmware to the service processor, you can use the sysfwdownload utility, which is provided with your system firmware upgrade package on the SunSolve site:
Run the following commands within the Solaris OS.
# cd firmware_location # sysfwdownload system_firmware_file
Shut down the Solaris OS instance.
# shutdown -i5 -g0 -y
Power off the system and update the firmware.
sc> poweroff -fy sc> flashupdate -s 127.0.0.1
Reset the service processor and power on the system.
sc> resetsc -y sc> poweron
Download the zip file (LDoms_Manager-1_3.zip) from the Sun Software Download site.
You can find the software at http://www.sun.com/servers/coolthreads/ldoms/get.jsp.
Unzip the zip file.
$ unzip LDoms_Manager-1_3.zip
See Location of LDoms 1.3 Software in Logical Domains 1.3 Release Notes for details about the structure of the file and what it includes.
There are three methods of installing the Logical Domains Manager software:
Using the installation script to install the packages and patches. This automatically installs the Logical Domains Manager software. See Installing the Logical Domains Manager Software Automatically.
Using JumpStart to install the packages. See Using JumpStart to Install the Logical Domains Manager 1.3 Software.
Installing the package manually. See Installing the Logical Domains Manager Software Manually.
Remember that you need to manually install the LDoms MIB software package after you install the Logical Domains packages. It is not automatically installed with the other packages. Refer to the Logical Domains (LDoms) MIB 1.0.1 Administration Guide for more information about installing and using the LDoms MIB.
If you use the install-ldm installation script, you have several choices to specify how you want the script to run. Each choice is described in the procedures that follow.
Using the install-ldm script with no options does the following automatically:
Checks that the Solaris OS release is Solaris 10 10/09 OS at a minimum
Verifies that the package subdirectories SUNWldm/ and SUNWldmp2v/ are present
Verifies that the prerequisite Solaris Logical Domains driver packages, SUNWldomr and SUNWldomu, are present
Verifies that the SUNWldm and SUNWldmp2v packages have not been installed
Installs the Logical Domains Manager 1.3 software
Verifies that all packages are installed
If the Solaris Security Toolkit (SUNWjass) is already installed, you are prompted to harden the Solaris OS on the control domain.
Determine whether to use the Logical Domains Configuration Assistant (ldmconfig) to perform the installation.
Using the install-ldm script with the -c option automatically runs the Logical Domains Configuration Assistant after the software is installed.
Using the install-ldm script with the -s option skips the running of the Logical Domains Configuration Assistant.
Using the install-ldm script and the following options with the Solaris Security Toolkit software enables you to do the following:
install-ldm -d. Allows you to specify a Solaris Security Toolkit driver other than a driver ending with -secure.driver. This option automatically performs all the functions listed in the preceding choice and hardens the Solaris OS on the control domain with the Solaris Security Toolkit customized driver that you specify; for example, the server-secure-myname.driver.
install-ldm -d none. Specifies that you do not want to harden the Solaris OS running on your control domain by using the Solaris Security Toolkit. This option automatically performs all the functions except hardening listed in the preceding choices. Bypassing the use of the Solaris Security Toolkit is not suggested and should only be done when you intend to harden your control domain using an alternate process.
install-ldm -p. Specifies that you only want to perform the post-installation actions of enabling the Logical Domains Manager daemon (ldmd) and running the Solaris Security Toolkit. For example, you would use this option if the SUNWldm and SUNWjass packages are preinstalled on your server.
See JumpStart Technology: Effective Use in the Solaris Operating Environment for complete information about using JumpStart.
Do not disconnect from the virtual console during a network installation.
Refer to the Solaris 10 10/09 Installation Guide: Custom JumpStart and Advanced Installations for complete information about this procedure.
Perform the following steps.
Set up networked systems with the procedures in “Creating a Profile Server for Network Systems.”
Create the rules file with the procedure in “Creating the rules File.”
Validate the rules file with the procedure in “Validating the rules File.”
Download the Logical Domains Manager 1.3 software, the SUNWldm and SUNWldmp2v packages, from the Sun Software Download site. See Download the Software for specific instructions.
Use the pkgadd command to install the SUNWldm.v and SUNWldmp2v packages.
For more information about the pkgadd command, see the pkgadd(1M) man page.
The -G option installs the package in the global zone only and the -d option specifies the path to the directory that contains the SUNWldm.v and SUNWldmp2v packages.
# pkgadd -Gd . SUNWldm.v SUNWldmp2v
Answer y for yes to all questions in the interactive prompts.
Use the pkginfo command to verify that the Logical Domains Manager 1.3 packages, SUNWldm and SUNWldmp2v, are installed.
For more information about the pkginfo command, see the pkginfo(1) man page.
The revision (REV) information shown below is an example.
# pkginfo -l SUNWldm | grep VERSION VERSION=1.3,REV=2009.12.03.10.20
The install-ldm installation script automatically enables the Logical Domains Manager daemon (ldmd). The ldmd daemon is also automatically enabled when the SUNWldm package is installed. When enabled, you can create, modify, and control the logical domains.
Use this procedure to enable the ldmd daemon if it has been disabled.
Use the svcadm command to enable the Logical Domains Manager daemon, ldmd.
For more information about the svcadm command, see the svcadm(1M) man page.
# svcadm enable ldmd
Use the ldm list command to verify that the Logical Domains Manager is running.
The ldm list command should list all domains that are currently defined on the system. In particular, the primary domain should be listed and be in the active state. The following sample output shows that only the primary domain is defined on the system.
# /opt/SUNWldm/bin/ldm list NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME primary active ---c- SP 64 3264M 0.3% 19d 9m