test

Logical Domains 1.3 Administration Guide

Chapter 2 Installing and Enabling Software

This chapter describes how to install or upgrade the different software components required to enable the Logical Domains (LDoms) 1.3 software. Using the LDoms software requires the following components:

The Solaris OS and the system firmware must be installed or upgraded on your server before you install or upgrade the Logical Domains Manager. If your system is already using Logical Domains software, see Upgrading a System Already Using Logical Domains. Otherwise, see Installing Logical Domains Software on a New System.

This chapter covers the following topics:

Note –

The Solaris Security Toolkit software is no longer packaged with the Logical Domains software. If you would like to use the most recent version of the Solaris Security Toolkit software, see the Logical Domains 1.3 Release Notes.

Installing Logical Domains Software on a New System

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.

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

Upgrading the System Firmware

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.

ProcedureUpgrade System Firmware

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.

Refer to the administration guides or product notes for the supported servers for more information about installing and updating system firmware for these servers.

  1. Shut down and power off the host server from either management port connected to the service processor: serial or network.


    # shutdown -i5 -g0 -y

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

    Where:

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

  3. Reset the service processor.


    sc> resetsc -y

  4. Power on and boot the host server.


    sc> poweron -c
ok boot disk

ProcedureUpgrade System Firmware Without an FTP Server

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:

http://sunsolve.sun.com

  1. Run the following commands within the Solaris OS.


    # cd firmware_location
# sysfwdownload system_firmware_file

  2. Shut down the Solaris OS instance.


    # shutdown -i5 -g0 -y

  3. Power off the system and update the firmware.


    sc> poweroff -fy
sc> flashupdate -s 127.0.0.1

  4. Reset the service processor and power on the system.


    sc> resetsc -y
sc> poweron

Downloading the Logical Domains Manager

ProcedureDownload the Software

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

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

Installing the Logical Domains Manager

There are three methods of installing the Logical Domains Manager software:

Note –

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.

Installing the Logical Domains Manager Software Automatically

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 JumpStart to Install the Logical Domains Manager 1.3 Software

See JumpStart Technology: Effective Use in the Solaris Operating Environment for complete information about using JumpStart.

Caution – Caution –

Do not disconnect from the virtual console during a network installation.

ProcedureSet Up a JumpStart Server

Refer to the Solaris 10 10/09 Installation Guide: Custom JumpStart and Advanced Installations for complete information about this procedure.

  1. Refer to the Solaris 10 10/09 Installation Guide: Custom JumpStart and Advanced Installations.

    Perform the following steps.

    1. See Task Map: Preparing Custom JumpStart Installations in Solaris 10 10/09 Installation Guide: Custom JumpStart and Advanced Installations.

    2. Set up networked systems with the procedures in “Creating a Profile Server for Network Systems.”

    3. Create the rules file with the procedure in “Creating the rules File.”

  2. Validate the rules file with the procedure in “Validating the rules File.”

Installing the Logical Domains Manager Software Manually

ProcedureInstall the Logical Domains Manager (LDoms) 1.3 Software Manually

Before You Begin

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.

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

  2. Answer y for yes to all questions in the interactive prompts.

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

Enabling the Logical Domains Manager Daemon

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.

ProcedureEnable the Logical Domains Manager Daemon

Use this procedure to enable the ldmd daemon if it has been disabled.

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

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

Upgrading a System Already Using Logical Domains

This section describes the process of upgrading the Solaris OS, firmware, and Logical Domains Manager components on a system that is already using the Logical Domains software.

If your system is already configured with the Logical Domains software, then the control domain has to be upgraded. The other existing domains also have to be upgraded if you want to be able to use all features of the Logical Domains 1.3 software.

Upgrading the Solaris OS

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 for the different domains. Refer to the Solaris 10 installation guide for complete instructions for upgrading the Solaris OS.

When reinstalling the Solaris OS in the control domain, you need to save and restore the Logical Domains autosave configuration data and the constraints database file, as described in this section.

Saving and Restoring Autosave Configuration Directories

Starting with the Logical Domains 1.2 release, you can save and restore autosave configuration directories prior to reinstalling the operating system on the control domain. Whenever you reinstall the operating system on the control domain, you must save and restore the Logical Domains autosave configuration data, which is found in the /var/opt/SUNWldm/autosave-autosave-name directories.

You can use the tar or cpio command to save and restore the entire contents of the directories.

Note –

Each autosave directory includes a timestamp for the last SP configuration update for the related configuration. If you restore the autosave files, the timestamp might be out of sync. In this case, the restored autosave configurations are shown in their previous state, either [newer] or up to date.

For more information about autosave configurations, see Managing Logical Domains Configurations.

ProcedureSave and Restore Autosave Directories

This procedure shows how to save and restore the autosave directories.

  1. Save the autosave directories.


    # cd /
# tar -cvf autosave.tar var/opt/SUNWldm/autosave-*

  2. (Optional) Remove the existing autosave directories to ensure a clean restore operation.

    Sometimes an autosave directory might include extraneous files, perhaps left over from a previous configuration, that might corrupt the configuration that was downloaded to the SP. In such cases, clean the autosave directory prior to the restore operation as shown in this example:


    # cd /
# rm -rf var/opt/SUNWldm/autosave-*

  3. Restore the autosave directories.

    These commands restore the files and directories in the /var/opt/SUNWldm directory.


    # cd /
# tar -xvf autosave.tar

Saving and Restoring the Logical Domains Constraints Database File

Whenever you upgrade the operating system on the control domain, you must save and restore the Logical Domains constraints database file that can be found in /var/opt/SUNWldm/ldom-db.xml.

Note –

Also, save and restore the /var/opt/SUNWldm/ldom-db.xml file when you perform any other operation that is destructive to the control domain's file data, such as a disk swap.

Preserving the Logical Domains Constraints Database File When Using Live Upgrade

If you are using live upgrade on the control domain, consider adding the following line to the /etc/lu/synclist file:


/var/opt/SUNWldm/ldom-db.xml     OVERWRITE

This causes the database to be copied automatically from the active boot environment to the new boot environment when switching boot environments. For more information about /etc/lu/synclist and synchronizing files between boot environments, refer to Synchronizing Files Between Boot Environments in Solaris 10 10/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning.

Upgrading From Solaris 10 OS Older Than Solaris 10 5/08 OS

If the control domain is upgraded from a Solaris 10 OS version older than Solaris 10 5/08 OS (or without patch 127127-11), and if volume manager volumes were exported as virtual disks, then the virtual disk backends must be re-exported with options=slice after the Logical Domain Manager has been upgraded. See Exporting Volumes and Backward Compatibility for more information.

Upgrading the Logical Domains Manager and the System Firmware

This section shows how to upgrade to Logical Domains 1.3 software.

First download the Logical Domains Manager to the control domain. See Downloading the Logical Domains Manager.

Then stop all domains (except the control domain) running on the platform:

ProcedureStop All Domains Running on the Platform, Except the Control Domain

  1. Bring down each domain to the ok prompt.

  2. Issue the stop-domain subcommand from the control domain for each domain.


    primary# ldm stop-domain ldom

  3. Issue the unbind-domain subcommand from the control domain for each domain.


    primary# ldm unbind-domain ldom

Upgrading to Logical Domains 1.3 Software

This section shows how to upgrade to Logical Domains 1.3 software.

Perform the procedure Upgrade From LDoms 1.0 Software Only in Logical Domains 1.3 Release Notes if you want to use your existing LDoms 1.0 configurations with Logical Domains 1.3 software. Existing LDoms 1.0 configurations do not work with Logical Domains 1.3 software.

If you are upgrading from more recent versions of the Logical Domains software, perform the procedure Upgrade to the Logical Domains 1.3 Software. Such existing LDoms configurations do work with Logical Domains 1.3 software.

ProcedureUpgrade to the Logical Domains 1.3 Software

  1. Flash update the system firmware.

    For the entire procedure, see Upgrade System Firmware or Upgrade System Firmware Without an FTP Server.

  2. Disable the Logical Domains Manager daemon (ldmd).


    # svcadm disable ldmd

  3. Remove the old SUNWldm package.


    # pkgrm SUNWldm

  4. Add the new SUNWldm package.

    Specifying the -d option assumes that the package is in the current directory.


    # pkgadd -Gd . SUNWldm

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


    # ldm list
NAME             STATE    FLAGS   CONS    VCPU  MEMORY   UTIL  UPTIME
primary          active   ---c-   SP      32    3264M    0.3%  19d 9m

Factory Default Configuration and Disabling Logical Domains

The initial configuration where the platform appears as a single system hosting only one operating system is called the factory default configuration. If you want to disable logical domains, you probably also want to restore this configuration so that the system regains access to all resources (CPUs, memory, I/O), which might have been assigned to other domains.

This section describes how to remove all guest domains, remove all Logical Domains configurations, and revert the configuration to the factory default.

ProcedureRemove All Guest Logical Domains

  1. List all the logical domain configurations that are stored on the service processor.


    primary# ldm list-config

  2. Remove all configurations (config-name) previously saved to the service processor (SP) except for the factory-default configuration.

    Use the following command for each such configuration.


    primary# ldm rm-config config-name

    After you remove all the configurations previously saved to the SP, the factory-default domain would be the next one to use when the control domain (primary) is rebooted.

  3. Stop all domains by using the -a option.


    primary# ldm stop-domain -a

  4. Unbind all domains except for the primary domain.


    primary# ldm unbind-domain ldom
    Note –

    You might not be able to unbind an I/O domain in a split-PCI configuration if it is providing services required by the control domain. In this situation, skip this step.

ProcedureRestore the Factory Default Configuration

  1. Select the factory default configuration.


    primary# ldm set-config factory-default

  2. Stop the control domain.


    primary# shutdown -i1 -g0 -y

  3. Powercycle the system so that the factory-default configuration is loaded.


    sc> poweroff
sc> poweron

ProcedureDisable the Logical Domains Manager

  1. Disable the Logical Domains Manager from the control domain.


    primary# svcadm disable ldmd
    Note –

    Disabling the Logical Domains Manager does not stop any running domains, but does disable the ability to create a new domains, change the configuration of existing domains, or monitor the state of the domains.

    Caution – Caution –

    If you disable the Logical Domains Manager, this disables some services, such as error reporting or power management. In the case of error reporting, if you are in the factory-default configuration, you can reboot the sole domain to restore error reporting. However, this is not the case with power management. In addition, some system management or monitoring tools rely on the Logical Domains Manager.

ProcedureRemoving the Logical Domains Manager

After restoring the factory default configuration and disabling the Logical Domains Manager, you can remove the Logical Domains Manager software.

  1. Remove the Logical Domains Manager software.


    primary# pkgrm SUNWldm SUNWldmp2v
    Note –

    If you remove the Logical Domains Manager before restoring the factory default configuration, you can restore the factory default configuration from the service processor as shown in the following procedure.

ProcedureRestore the Factory Default Configuration From the Service Processor

If you remove the Logical Domains Manager before restoring the factory default configuration, you can restore the factory default configuration from the service processor.

  1. Restore the factory default configuration from the service processor.


    -> set /HOST/bootmode config=factory-default

  2. Powercycle the system to load the factory default configuration.