Chapter 5 Installing Solaris Flash Archives on Managed Hosts (Tasks)

Change Manager uses the Solaris Live Upgrade software to perform software update operations on managed hosts. Do not manually run Solaris Live Upgrade commands on managed hosts outside the context of Change Manager.

Running Live Upgrade commands in this way might result in Change Manager's obtaining an inconsistent view of the state of the managed host.

The main task performed by the Change Manager is to deploy software stacks to managed hosts. The Change Manager also performs remote operations on the managed hosts, such as fallback, reboot, and halt.

Change Manager supports the following deployment types:

Initial Installation

Before an initial installation, managed hosts are assumed to have no software installed or have software installed that can be overwritten. To initiate an initial installation, you must manually run the following command on each managed host:

ok> boot net - install

Change Manager provides the network installation services for the managed host. Before you initiate the network boot, you must create custom JumpStart files for each managed host by running the Set Up for Install or changemgr setup operation.

Update

The managed hosts are running a software stack that was installed by Change Manager (and running the Change Manager agent). An update uses the Solaris Live Upgrade feature to deploy software to the inactive boot environment. Initiate an update by running the Update or changemgr update operation.

Reinstallation

This operation is similar to an initial installation because the software installed on managed hosts is overwritten, software is not deployed to another boot environment. Initiate a reinstallation by running the Reinstall or changemgr reinstall operation.

You must perform a Change Manager initial installation on a managed host before you can perform a Change Manager update or reinstallation on that managed host.

To prepare a managed host for future updates, configure your managed host with two boot environments. To prepare a managed host for future reinstallation operations, configure your managed host with one boot environment. See Minimum Set of Parameters to Deploy Software.

The following topics are covered in this chapter:

• Solaris Deployment Technologies Used by Change Manager

• Change Manager Deployment File Types

• Installing Solaris Flash Archives on Managed Hosts by Using the Browser Interface (Task Map)

• Installing Solaris Flash Archives on Managed Hosts by Using the Browser Interface

• Installing Solaris Flash Archives on Managed Hosts by Using the Command-Line Interface (Task Map)

• Installing Solaris Flash Archives on Managed Hosts by Using the Command-Line Interface

Solaris Deployment Technologies Used by Change Manager

Change Manager employs the following deployment technologies for performing initial installation, update, and reinstallation operations:

• Solaris Flash installation

• Solaris Live Upgrade

• Custom JumpStart installation

Solaris Flash Installation

The Solaris Flash installation enables you to create a single reference installation of the Solaris operating environment and other software applications on a system. This system is called the master system. Then, you can replicate that reference installation on a number of systems by using the Change Manager. These systems are called managed hosts. Installing managed hosts with the Solaris Flash archive is a four-part process that involves the following:

1. Installing the master system. Select a system and use any of the Solaris installation methods to install the Solaris operating environment and any other software.

2. Installing the Change Manager agent software on the master system. The agent software is required for Change Manager to remotely control managed hosts once the software stack has been installed.

3. Creating the Solaris Flash archive. The Solaris Flash archive is a single file that contains a software stack. The archive is a copy of all the files on the master system.

4. Installing the Solaris Flash archive on managed hosts. When you install the Solaris Flash archive on a managed host, all of the files in the archive are copied to that managed host. The newly installed managed host now has the same installation configuration as the original master system.

See Chapter 4, Creating a Deployable Solaris Flash Archive (Tasks) for information about creating Solaris Flash archives.

Managed hosts are not updated by adding packages or installing patches. Instead, you update and reconfigure the master system. Then, you create a new Solaris Flash archive that contains the updated software stack. The new archive can be installed on the managed hosts in a single step.

The Solaris Flash archives must be imported to the Change Manager repository before they can be installed on managed hosts.

Solaris Live Upgrade

Solaris Live Upgrade provides a method of upgrading that substantially reduces the usual service outage that is associated with an operating system upgrade. While the active boot environment continues to run, you can install a Solaris Flash archive on the inactive boot environment. The original system configuration remains fully functional and unaffected by the installation of the Solaris Flash archive. When you reboot the system, this boot environment becomes the active boot environment.

If a failure occurs, you have a safety net. You can quickly revert to the original boot environment by performing a fall back. This fall back action eliminates the downtime associated with the normal test and evaluation process.

Change Manager uses Solaris Live Upgrade to perform updates of managed hosts. Before you can perform updates, you must perform an initial installation by using Change Manager. This initial installation must create two boot environments so that an alternate boot environment is available for the update.

For more information about Solaris Live Upgrade, see "Solaris Live Upgrade (Overview)" in Solaris 9 Installation Guide.

Custom JumpStart Installation

Custom JumpStart is a command-line interface that enables you to automatically install several systems, based on JumpStart profiles that you create. These profiles define specific software installation requirements. You can also incorporate shell scripts to include preinstallation tasks and postinstallation tasks. You choose which profile and scripts to use for installation. Custom JumpStart then installs the system.

Change Manager uses the custom JumpStart installation method to perform the initial installations and reinstallations of managed hosts.

See "Preparing Custom JumpStart Installations (Tasks)" in Solaris 9 Installation Guide.

Change Manager Deployment File Types

The Change Manager uses deployment files as input for jobs.

You can use folders to create a hierarchy in which to organize these Change Manager files. These files and folders are stored in the repository. You can organize the folders and files in any way that you want.

Access the repository in the browser user interface by clicking the Files tab. Access the repository with the command-line interface by using the file management subcommands of the changemgr command.

You might organize the folders and files in the following ways:

• Group like file types - For example, store all the Solaris Flash archives in a single folder. Do the same for Solaris boot images, shared profiles, and manifests.

• Group files related to a particular set of managed hosts - Create a folder to hold all the files associated with a particular service's servers.

  For example, a server farm provides web services. Therefore, create a folder named WebServer. In the WebServer folder, store the files used by the web server, such as the archives, boot images, shared profiles, and manifests. Create a separate folder to hold files associated with a mail server.

• Group by user name - Store all files in folders owned by specific users. For example, store all of Joe's files in a folder named joe. Then, Joe can organize his folders and files in the way he wants.

• Group all files associated with a particular archive - Store all files associated with each archive in folders. For example, the archive and associated files for the Apache web server are stored in a folder named apache-web-server. Store the archive, boot image, and shared profile in the same folder.

Files stored in the Change Manager repository have a standard set of properties associated with them. The following properties are shared by all files:

Description

User-supplied string that describes the file.

Owner

Read-only property that names the owner of the file.

State

Read-only property that indicates the state of the file.

When using the browser interface, you must perform the operations on the File Actions drop-down menu while in the appropriate folder.

For example, to create a folder inside an existing folder, go to that folder before choosing New Folder from the File Actions menu.

When using the browser interface, you can select items from a list. To select an item from a list, click the checkbox next to the item name. Then, choose the action to perform from the File Actions drop-down menu.

Shared Profile

A shared profile is a set of Solaris system configuration parameters that are used to install managed hosts in a consistent, repeatable manner. Once created, a shared profile becomes a template that can be applied to one or more managed hosts. A shared profile specifies customizations such as disk slicing, root password, network interfaces, naming service, time zone, and locale. Each profile can specify the Solaris Flash archive to be deployed to the managed host. Every managed host must have a shared profile associated with it.

Once applied to a specific managed host, the shared profile data becomes part of the host properties for that managed host.

Use the changemgr fileset command to change property values for a shared profile in the repository. You can also change property values by making changes to property values on the shared profile's property page. However, when the shared profile is outside of the repository, you manipulate properties by editing the properties and property values contained in the file. See the cmsp(4CM) man page.

The shared profile file name must use the .cmsp suffix.

To create or import shared profiles, see How to Create a Shared Profile (Web Browser) and How to Import a Shared Profile to the Change Manager Repository (Web Browser) or How to Import Shared Profiles to the Change Manager Repository (Command Line).

To deploy software to a managed host, you must import the shared profile to the Change Manager repository. See How to Reinstall, Update, Fall Back, and Reboot Managed Hosts (Web Browser), or How to Perform an Initial Installation (Command Line) and How to Update Managed Hosts (Command Line).

Understanding Shared Profiles and Host Properties

Shared profiles and host properties are used by the Change Manager to describe how one or more managed hosts are to be configured with a software stack. Much of the information specified by shared profiles and host properties is the same as described in a custom JumpStart installation profile.

A shared profile can be used by one or more managed hosts to describe the way managed hosts are configured with the software stack.

Host properties describe exactly one managed host. These properties describe the exact configuration of the software stack on the particular managed host. The host properties point to the shared profile. You can further customize the managed host by doing the following:

• Overriding archive parameter values in the shared profile by providing new values for the same archive parameters

• Overriding parameter values in the shared profile by providing new values for the same parameters

• Providing values not already specified in the shared profile

Solaris Boot Image

A Solaris boot image is a set of files that is used with a matching archive to install and update managed hosts. The Solaris version of the boot image and the archive must be identical for installation tasks and update tasks to succeed. The Solaris boot image is used as input for an installation or an update action and is associated with an archive. A Solaris boot image is also known as a miniroot.

For installations, the boot image boots the Solaris operating environment on the managed host and runs the Solaris Flash installation program. For updates, the boot image runs the Solaris Flash installation program.

A single boot image can support several archives. The Solaris version of the boot image and the archive must match. For example, a Solaris 8 2/02 boot image must be used to deploy archives based on the Solaris 8 2/02 release.

The Solaris boot image file name must use the .miniroot suffix.

In addition to the general file properties, a Solaris boot image is associated with the following property:

OSVersion

User-supplied string that describes the version of the Solaris operating system associated with the boot image.

To deploy software to a managed host, see How to Perform an Initial Installation (Web Browser) and How to Reinstall, Update, Fall Back, and Reboot Managed Hosts (Web Browser), or How to Perform an Initial Installation (Command Line), How to Reinstall Managed Hosts (Command Line), and How to Update Managed Hosts (Command Line).

Solaris Flash Archive

A Solaris Flash archive is a file that contains a software stack. This stack can be deployed to hosts managed by the Change Manager. The Solaris version of the archive must match that of the boot image used for deployment. The archive is used as input for an installation, reinstallation, or update action. The managed host or a shared profile specifies the archive to use.

To deploy an archive, a matching Solaris boot image must already exist in the Change Manager repository.

The Solaris Flash archive file name must use the .flar suffix.

In addition to the general file properties, a Solaris Flash archive is associated with the following property:

BootImage

User-supplied string that describes the Solaris boot image associated with this Solaris Flash archive.

To deploy software to a managed host, see How to Perform an Initial Installation (Web Browser) and How to Reinstall, Update, Fall Back, and Reboot Managed Hosts (Web Browser), or How to Perform an Initial Installation (Command Line), How to Reinstall Managed Hosts (Command Line), and How to Update Managed Hosts (Command Line).

For a description of the archive keywords, see flash_archive(4).

Folder

A folder is a container that can hold files and other folders. Click a folder name to go into that folder. Then, view the folder's contents. Change Manager files can be the following:

• Solaris Flash archive

• Solaris boot image

• Shared profile

• Manifest

• Audit rules file

• Report

Perform the following actions from the folder page:

• Create folders, shared profiles, and audit rules files.

• Import Solaris Flash archives, Solaris boot images, shared profiles, audit rules files, and manifests to the Change Manager repository.

• Rename folders and files.

• Export files.

• Create a copy of a shared profile or an audit rules file in the current folder.

• Move folders and files to another folder.

• Delete folders and files.

To create folders, see How to Create a Folder (Web Browser) or How to Create a Folder (Command Line).

Installing Solaris Flash Archives on Managed Hosts by Using the Browser Interface (Task Map)

The following table identifies the procedures to follow to install Solaris Flash archives on managed hosts by using the browser interface.

Installing Solaris Flash Archives on Managed Hosts by Using the Browser Interface

Initiate deployment jobs from the Hosts section. Click the Hosts tab to go to the Hosts section.

Navigate through the hierarchy of host groups and managed hosts. Host groups can contain managed hosts and other host groups. Perform actions on host groups and managed hosts.

Click a host group name to change to that host group and see its contents. Click a managed host's name to see its properties.

To learn how to create folders and perform management tasks in the Change Manager repository, see Chapter 8, Maintaining the Change Manager Repository (Tasks). None of the procedures described in Chapter 8, Maintaining the Change Manager Repository (Tasks) are required to perform deployment tasks, though you might want to create a hierarchy of folders in the repository.

To learn how to create host groups and perform management tasks on the Change Manager topology, see Chapter 9, Maintaining the Change Manager Topology (Tasks). None of the procedures described in Chapter 9, Maintaining the Change Manager Topology (Tasks) are required to perform deployment tasks, though you might want to create a hierarchy of host groups in the topology.

To learn how to navigate through the browser interface, see Appendix A, Navigating Through the Change Manager Browser Interface (Reference).

How to Access the Files Section and Appropriate Folder (Web Browser)

Note that the top of the Files section hierarchy is a folder.

1. To go to the Files section, click the Files tab in the general links area at the top of the page.

   The top-level Files page shows a table, which can contain files and folders. The table is a file manager.

2. Drill down to the appropriate folder.

   Click a folder name to go into that folder. Then, view the folder's contents. Continue to click folder names until you reach the folder or file you want.

How to Import Solaris Boot Images to the Change Manager Repository (Web Browser)

The Solaris boot image is used to deploy software stacks to managed hosts.

For an initial installation, the managed host boots and mounts a small Solaris root. The root is contained in the boot image. Then, the managed host runs the Solaris installation program. For an update, the managed host runs the Solaris installation program, which is stored on the boot image.

The time required to import a file to the Change Manager repository depends on the size of the file and the speed of the network.

1. If you are not already in the appropriate folder, see How to Access the Files Section and Appropriate Folder (Web Browser).

2. From the File Actions menu, choose Import Boot Image.

3. Supply the pertinent information:

   • Boot image name, which describes the version of Solaris and architecture supported, for example, Solaris8_202_sun4u. Add the .miniroot suffix to complete the boot image name, Solaris8_202_sun4u.miniroot.

   • Path to the boot image. Click Browse to find the boot image.

     The path to the boot image must point to the top directory of the Solaris installation media. The installation media can be on a CD or on another system on the network. The top directory of the Solaris installation media contains the Copyright and installer files, and either the Solaris_8 or Solaris_9 directory. These directories contain the Solaris packages and the Solaris boot image.

     ---

     Note -

     If you import the boot image from a CD, point to the directory named something like /cdrom/Solaris version/s0. For example, the directory for a Solaris 9 boot image would be /cdrom/sol_9_sparc/s0.

     ---

   • Solaris version that the boot image supports, for example Solaris 8 2/02.

4. When the information is complete, click Import to copy the Solaris boot image to the Change Manager repository.

   Click Cancel to return to the previous page.

How to Import Solaris Flash Archives to the Change Manager Repository (Web Browser)

Import a Solaris Flash archive from another system on the network, perhaps the master system on which it was created. This archive is a software stack that can be deployed to managed hosts.

The time required to import a file to the Change Manager repository depends on the size of the file and the speed of the network.

1. If you are not already in the appropriate folder, see How to Access the Files Section and Appropriate Folder (Web Browser).

2. From the File Actions menu, choose Import Archive.

3. Supply the following information:

   • Archive name. Choose a meaningful name. For example, choose a name that describes the software contents or purpose of the archive, such as apache_webserver. Add the .flar suffix to complete the archive name, apache_webserver.flar.

   • Path to the archive outside the Change Manager repository. Click Browse to find the archive.

   • Path to the Solaris boot image in the Change Manager repository that supports the same Solaris version and architecture.

4. When the information is complete, click Import to import the audit rules file.

   Click Cancel to return to the previous page.

How to Create a Shared Profile (Web Browser)

1. If you are not already in the appropriate folder, see How to Access the Files Section and Appropriate Folder (Web Browser).

2. From the File Actions menu, choose New Shared Profile.

   The shared profile property page appears.

3. Use the wizards in each section to create the shared profile.

   Launch each wizard by clicking the Edit button associated with particular properties.

   Each page requires information that is used to create the profile. Return to previous pages by clicking buttons or clicking on the step description links in the left panel.

4. After selecting values for the profile, click Finish to set the property values on the property page.

   Click Cancel to exit the wizard and return to the previous page.

5. When the properties have the values you want, click Save to create the shared profile.

   Click Cancel to exit the shared profile property page without saving changes and to return to the previous page.

How to Import a Shared Profile to the Change Manager Repository (Web Browser)

The shared profile describes how the managed hosts should be configured at deployment time. For a description of the shared profile's format, see Shared Profile.

If the shared profile contains a property with an invalid value, for example the value of base_config_flar_archive does not refer to an existing archive, then the import fails. Check the job queue (see How to View the Job Queue (Web Browser)) to determine whether the import failed. If the import failed, correct the property value and reinitiate the import operation.

The time required to import a file to the Change Manager repository depends on the size of the file and the speed of the network.

1. If you are not already in the appropriate folder, see How to Access the Files Section and Appropriate Folder (Web Browser).

2. From the File Actions menu, choose Import Shared Profile.

3. Supply the following information:

   • Profile name. Choose a meaningful name. For example, choose a profile name that describes the software customizations or the managed host's hardware type, such as webserver_sun4u. Add the .cmsp suffix to complete the shared profile name, webserver_sun4u.cmsp.

   • Path to the shared profile outside the Change Manager repository. Click Browse to find the profile.

4. When the information is complete, click Import to copy the profile file to the Change Manager repository.

   Click Cancel to return to the previous page.

How to Access the Hosts Section and Appropriate Administrative Domain and Host Group (Web Browser)

1. To go to the Hosts section, click the Hosts tab in the general links area at the top of the page.

   • If more than one administrative domain exists, you go to a page showing a table that lists the available administrative domains. Go to Step 2.

   • If only one administrative domain exists, the page shows a table that lists managed hosts and host groups in the default domain. Go to Step 3.

2. (Optional) Click the name of the administrative domain to use.

   ---

   Note -

   Use Sun Management Center to create a new administrative domain. See "Using Sun Management Center Administrative Domains" in Sun Management Center 3.0 Software User's Guide.

   ---

3. Drill down to the appropriate host group.

   Click a host group name to go into that host group. Then, view the host group's contents. Continue to click host group names until you reach the host group or managed host you want.

How to Add a Managed Host (Web Browser)

Managed host properties are the same as those specified for shared profiles. For information about the properties and property values, see Chapter 10, Creating Shared Profiles and Host Properties (Reference).

A managed host can be a client of only one Change Manager server. To change control of a managed host to another Change Manager server, see Internal error: unable to establish probe connection Appears When Running Jobs on Managed Hosts.

1. If you are not already in the appropriate host group, see How to Access the Hosts Section and Appropriate Administrative Domain and Host Group (Web Browser).

2. From the Host Actions menu, choose Add Host.

   The host property page appears.

3. Supply the following information:

   • Host name.

   • Ethernet address of the managed host.

   • Platform group of the managed host.

   • Port number configured on the agent to communicate with the server.

     ---

     Note -

     If you change the value of this property after installing a managed host, the Change Manager server will no longer be able to communicate with it. To reestablish communication with the server by using the new agent port, you must re-initialize the managed host by performing an initial installation on it.

     ---

   • Shared profile to use to install or update the managed host.

   • Parameter values that customize the Solaris Flash archive for the managed host.

   ---

   Note -

   If a shared profile already exists for this managed host, you only need to specify the name of the shared profile. You can override any archive-specific parameter values specified in the shared profile by clicking the Load button. Then, you can update these parameter value fields of the host properties.

   ---

4. Click Add to add the managed host.

   Click Cancel to return to the previous page.

How to Perform an Initial Installation (Web Browser)

To perform an initial installation, you must first set up for initial installation. The setup creates the custom JumpStart files based on information in the shared profile and host properties. Then, you must initiate the initial installation from the console of each managed host to be installed.

1. Make sure that the managed hosts you want to install have been added to the Change Manager server.

   See How to Add a Managed Host (Web Browser).

2. Modify the shared profiles and host properties to reflect the configuration of the managed hosts you want.

   • To configure the managed hosts for reinstallation operations, configure one boot environment.

   • To configure the managed hosts for updates, create two boot environments. See Minimum Set of Parameters to Deploy Software.

3. If you are not already in the appropriate host group, see How to Access the Hosts Section and Appropriate Administrative Domain and Host Group (Web Browser).

4. From the Host Actions menu, choose Set Up for Install.

   This action creates the custom JumpStart files needed to perform the initial installation.

   ---

   Caution -

   If you modify the associated shared profile or host properties again before you perform the initial installation, you must recreate the JumpStart profiles. To recreate the JumpStart profiles, rerun Set Up for Install before performing boot net - install.

   ---

5. Supply a meaningful job name with which to track the job's progress.

6. Click Submit to initiate the action.

   Click Cancel to return to the previous page.

7. From the console of each of the managed hosts to be installed, do the following:

   1. Bring each managed host to the ok> prompt.

      If the managed host is running, press Stop-A.

   2. On each console, type boot net - install and press Return.

      Be sure to include the space between the - and install.

      ---

      Caution -

      Make sure that the managed host is only a network boot client of the Change Manager server.

      The network boot of your managed host might fail with an error message such as Panic: unable to mount file systems. If such a message appears, then your managed host is probably being served by more than one network boot server. See Panic: unable to mount file systems Message Appears While Booting From the Network.

      ---

How to Reinstall, Update, Fall Back, and Reboot Managed Hosts (Web Browser)

1. If you are not already in the appropriate host group, see How to Access the Hosts Section and Appropriate Administrative Domain and Host Group (Web Browser).

2. Perform one of the following actions:

   • To perform a reinstallation, choose Reinstall from the Host Actions menu.

   • To perform an update, choose Update from the Host Actions menu.

     ---

     Note -

     First use the Change Manager to perform an initial installation before using the Solaris Live Upgrade feature on a managed host. The initial installation creates two boot environments by using the lucreate command.

     ---

     Modify the shared profiles and host properties to reflect the configuration of the managed hosts.

   • To fall back to the previous version of the software stack, choose Fall Back from the Host Actions menu.

     The fallback operation "undoes" the last update attempt of a managed host, whether it finished or did not start.

     For example, three managed hosts are updated one at a time. The update operation completes on the first managed host. Then, the update begins on the second managed host. When the first managed host boots the updated boot environment, you notice that there are problems with the system. You cancel the running update.

     Each of the three managed hosts are in a different state. The first managed host completed the update. The second managed host started the update, but did not complete it. The third managed host did not start the update.

     The fallback operation ensures that each of these managed hosts reverts to the boot environment running prior to the update attempt.

     The fallback feature fails if the system cannot boot. In such cases, see " Solaris Live Upgrade (Overview)" in Solaris 9 Installation Guide.

   • To reboot managed hosts, choose Reboot from the Host Actions menu.

3. Supply a meaningful job name.

   For example, the job name might be Update host1 and host2.

4. Determine when you want to run the job, either now or at another time.

   • To initiate the job immediately, click the Start Now radio button.

   • Run the job at a later time by specifying the start date and start time.

     • Start date. Click the date or specify the date in the mm/dd/yyyy format.

       mm and dd are two-digit forms for the month and day. yyyy is the four-digit form for the year.

     • Start time. Choose the start time from the hour and minute pull-down menus.

5. Click Submit to initiate the action.

   Click Cancel to return to the previous page.

Installing Solaris Flash Archives on Managed Hosts by Using the Command-Line Interface (Task Map)

The following table identifies the procedures to follow to install Solaris Flash archives on managed hosts by using the command-line interface. See the changemgr(1MCM) man page.

Installing Solaris Flash Archives on Managed Hosts by Using the Command-Line Interface

The following procedures describe how to perform deployment tasks by using the Change Manager command-line interface. You can use the command-line interface to perform tasks such as importing Solaris Flash archives and performing updates.

To learn how to create folders and perform management tasks in the Change Manager repository, see Chapter 8, Maintaining the Change Manager Repository (Tasks). None of the procedures described in Chapter 8, Maintaining the Change Manager Repository (Tasks) are required to perform deployment tasks, though you might want to create a hierarchy of folders in the repository.

To learn how to create host groups and perform management tasks on the Change Manager topology, see Chapter 9, Maintaining the Change Manager Topology (Tasks). None of the procedures described in Chapter 9, Maintaining the Change Manager Topology (Tasks) are required to perform deployment tasks, though you might want to create a hierarchy of host groups in the topology.

How to Import Solaris Boot Images to the Change Manager Repository (Command Line)

The Solaris boot image is used to deploy software stacks to managed hosts.

The time required to import a file to the Change Manager repository depends on the size of the file and the speed of the network.

For an initial installation, the managed host boots and mounts a small Solaris root. The root is contained in the boot image. Then, the managed host runs the installation program. For an update, the managed host runs the installation program, which is stored on the boot image.

1. Determine where the boot image exists and where to store it.

   For example, copy the boot image from /net/test1/home/suzi/s9fcs to the / folder.

   The path to the boot image must point to the top directory of the Solaris installation media. The installation media can be on a CD or on another system on the network. The top directory of the Solaris installation media contains the Copyright and installer files, and either the Solaris_8 or Solaris_9 directory. These directories contain the Solaris packages and the Solaris boot image.

   ---

   Note -

   If you import the boot image from a CD, point to the directory named something like /cdrom/Solaris version/s0. For example, the directory for a Solaris 9 boot image would be /cdrom/sol_9_sparc/s0.

   ---

2. Import a Solaris boot image to the Change Manager repository by using one of these changemgr import commands.

   • The following command line imports one file at a time. You can also use this command line to rename the file.

     $ changemgr import [ -u username ] [ -p file ] filepath[.type] \ relfilepath.type

   • The following command line imports several files to a folder simultaneously.

     $ changemgr import [ -u username ] [ -p file ] filepath.type ... \ reldirpath

   -u username

   Specify the user name to authenticate. If this option is not specified, the user is the current UNIX user.

   -p file

   file consists of a single line, which contains the password. If file is -, then the user can supply the password as standard input.

   If the -p option is not supplied, then the changemgr command prompts the user for his password.

   filepath

   Specifies an absolute or relative path to a file. This file path is not within the Change Manager repository.

   relfilepath

   Specifies the path to a file, not including a folder, that is relative to the top of the Change Manager repository.

   reldirpath

   Specifies the path to a folder that is relative to the top of the Change Manager repository.

   .type

   Specifies the file name suffix that represents the file type. A Solaris boot image uses the .miniroot suffix.

   Choose a file name that indicates the versions of the Solaris operating environment the boot image supports. For example, create a boot image named Solaris9.miniroot.

Example-Importing a Solaris Boot Image to the Change Manager Repository

Suzi copies the boot image from the /net/test1/home/suzi/Solaris_9 directory to the / folder. She calls the boot image Solaris_9.miniroot.

$ changemgr import /net/test1/home/suzi/Solaris_9 \
/Solaris_9.miniroot

Example-Importing Solaris Boot Images to the Change Manager Repository

Suzi copies the boot images from the /net/test1/home/suzi/Solaris_9 and /net/test1/home/suzi/Solaris_8.202 directories to the /BootImages folder.

$ changemgr import /net/test1/home/suzi/Solaris_9 \
/net/test1/home/suzi/Solaris_8.202 /BootImages

How to Import Solaris Flash Archives to the Change Manager Repository (Command Line)

Import a Solaris Flash archive from another system, typically the master system on which it was created, on the network. This archive contains a software stack that can be deployed to managed hosts.

The time required to import a file to the Change Manager repository depends on the size of the file and the speed of the network.

1. Determine where the archive exists and where to store it.

   For example, copy the archive from /net/test1/home/suzi/apache.flar to the web-server folder.

2. Import a Solaris Flash archive to the Change Manager repository by using one of these changemgr import commands.

   • The following command line imports one file at a time. You can use the command line to rename the file.

     $ changemgr import [ -u username ] [ -p file ] filepath[.type] \ relfilepath.type

   • The following command line imports several files to a folder simultaneously.

     $ changemgr import [ -u username ] [ -p file ] filepath.type ... \ reldirpath

   .type

   Specifies the file name suffix that represents the file type. A shared profile uses the .flar suffix.

   For descriptions of the other options, see How to Import Solaris Boot Images to the Change Manager Repository (Command Line).

   Choose a meaningful name that indicates the type of archive. For example, create an archive named apache.flar.

Example-Importing a Solaris Flash Archive to the Change Manager Repository

Suzi copies the archive called /net/test1/home/suzi/apache.flar to the web-server folder. She renames the file to be Apache.flar.

$ changemgr import /net/test1/home/suzi/apache.flar \
/web-server/Apache.flar

Example-Importing Solaris Flash Archives to the Change Manager Repository

Suzi copies the archives called /net/test1/home/suzi/apache.flar and /net/test1/home/suzi/oracle.flar to the / folder.

$ changemgr import /net/test1/home/suzi/apache.flar \
/net/test1/home/suzi/oracle.flar /

How to Import Shared Profiles to the Change Manager Repository (Command Line)

The shared profile describes how the managed hosts should be configured at deployment time. For a description of the shared profile's format, see Shared Profile.

If the shared profile contains a property with an invalid value, for example the value of base_config_flar_archive does not refer to an existing archive, then the import fails. Check the job queue (see How to View the Job Queue (Web Browser)) to determine whether the import failed. If the import failed, correct the property value and reinitiate the import operation.

The time required to import a file to the Change Manager repository depends on the size of the file and the speed of the network.

1. Determine where the shared profile exists and where to store it.

   For example, copy the shared profile from /net/test1/home/suzi/apache.cmsp to the web-server folder.

2. Import a shared profile to the Change Manager repository by using one of these changemgr import commands.

   • The following command line imports one file at a time. You can also use this command line to rename the file.

     $ changemgr import [ -u username ] [ -p file ] filepath[.type] \ relfilepath.type

   • The following command line imports several files to a folder simultaneously.

     $ changemgr import [ -u username ] [ -p file ] filepath.type ... \ reldirpath

   .type

   Specifies the file name suffix that represents the file type. A shared profile uses the .cmsp suffix.

   For descriptions of the other options, see How to Import Solaris Boot Images to the Change Manager Repository (Command Line).

   Choose a file name that indicates the unique features specified by the shared profile. For example, create a shared profile named apache.cmsp to configure the managed hosts that run the Apache web server.

Example-Importing a Shared Profile to the Change Manager Repository

Suzi copies the shared profile called /net/test1/home/suzi/apache.cmsp to the web-server folder at the top of the repository. She renames the file to be Apache.cmsp.

$ changemgr import /net/test1/home/suzi/apache.cmsp \
/web-server/Apache.cmsp

Example-Importing Shared Profiles to the Change Manager Repository

Suzi copies the shared profiles called /net/test1/home/suzi/apache.cmsp and /net/test1/home/suzi/oracle.cmsp to the /MyProfiles folder.

$ changemgr import /net/test1/home/suzi/apache.cmsp \
/net/test1/home/suzi/oracle.cmsp MyProfiles

How to Add Managed Hosts (Command Line)

To simplify naming of managed hosts, you can make each name match the name of the actual machine.

If you change the value of the AgentPort property after installing a managed host, the Change Manager server will no longer be able to communicate with it. To reestablish communication with the server by using the new agent port, you must re-initialize the managed host by performing an initial installation on it.

A managed host can be a client of only one Change Manager server. To change control of a managed host to another Change Manager server, see Internal error: unable to establish probe connection Appears When Running Jobs on Managed Hosts.

1. Determine where to create the managed host.

   For example, create a managed host in the web-server host group.

2. Use one of these changemgr add commands to add the managed host.

   • The following command adds a managed host to be controlled by the Change Manager. A managed host can be created in a host group that is part of the Change Manager topology. hostpath is the full path name or relative path name to the managed host, which includes the host group hierarchy.

     $ changemgr add [ -u username ] [ -p file ] [ -d domain ] \ hostname hostpath

   • The following command adds the specified hosts to the specified host group. The topology names are the same as the host names.

     $ changemgr add [ -u username ] [ -p file ] [ -d domain ] \ hostname ... grouppath

   -u username

   Specify the user name to authenticate. If this option is not specified, the user is the current UNIX user.

   -p file

   file consists of a single line, which contains the password. If file is -, then the user can supply the password as standard input.

   If the -p option is not supplied, then the changemgr command prompts the user for his password.

   -d domain

   Specify the administrative domain on which to operate. In the context of a session, the default is the domain specified for the session. If no domain is specified, domain is the user's home domain. By default, domain is the user's home domain.

   hostname

   Specifies the network name of a host, for example, host1.yourcompany.com.

   hostpath

   Specifies the path to a managed host that is relative to the top of the selected administrative domain.

   grouppath

   Specifies the path to a host group that is relative to the top of the selected administrative domain.

Example-Adding a Managed Host

Chris creates the host1 managed host in the web-server/apache host group.

$ changemgr add host1 /web-server/apache

Example-Adding a Managed Host and Changing Its Name

Chris adds the host1 managed host to the web-server/apache host group and changes the host name to Host1.

$ changemgr add host1 /web-server/apache/Host1

Example-Adding Managed Hosts to a Host Group

Chris adds the host1 and host2 managed hosts to the web-server/apache host group.

$ changemgr add host1 host2 /web-server/apache

How to Perform an Initial Installation (Command Line)

The initial installation must be initiated from each managed host to be installed.

1. Ensure that the managed hosts you want to install have been added to the Change Manager server.

   See How to Add Managed Hosts (Command Line).

2. Determine which managed hosts you want to install.

   For example, install the /web-server/host1 and /web-server/host2 managed hosts.

3. Modify the shared profiles and host properties to reflect the configuration of the managed hosts.

   • To configure the managed hosts for reinstallation operations, configure one boot environment.

   • To configure the managed hosts for updates, configure two boot environments.

4. Set up the files for installation.

   $ changemgr setup [ -u username ] [ -p file ] [ -d domain ] \ topopath ...

   topopath

   Specifies the path to a managed host or host group. The managed host or host group is relative to the top of the specified administrative domain.

   For descriptions of the other options, see How to Add Managed Hosts (Command Line).

   ---

   Caution -

   If you modify the associated shared profile or host properties again before you perform the initial installation, you must recreate the JumpStart profiles. To recreate the JumpStart profiles, rerun changemgr setup before performing boot net - install.

   ---

5. Go to the console of each of the managed hosts to be installed and do the following:

   1. Bring each managed host to the ok> prompt.

      If the managed host is running, press Stop-A.

   2. On each console, type boot net - install and press Return.

      Be sure to include the space between the - and install.

      ---

      Caution -

      Make sure that the managed host is only a network boot client of the Change Manager server.

      The network boot of your managed host might fail with an error message such as Panic: unable to mount file systems. If such a message appears, then your managed host is probably being served by more than one network boot server. See Panic: unable to mount file systems Message Appears While Booting From the Network.

      ---

How to Reinstall Managed Hosts (Command Line)

First use the Change Manager to perform an initial installation that creates a single boot environment before performing a reinstallation of a managed host.

1. Determine which managed hosts you want to reinstall.

   For example, reinstall the /web-server/host1 and /web-server/host2 managed hosts.

2. Modify the shared profiles and host properties to reflect the configuration of the managed hosts to reinstall.

3. Reinstall the specified managed hosts.

   $ changemgr reinstall [ -u username ] [ -p file ] [ -d domain ] \ topopath ...

   topopath

   Specifies the path to a managed host or host group. The managed host or host group is relative to the top of the specified administrative domain.

   For descriptions of the other options, see How to Add Managed Hosts (Command Line).

Example-Reinstalling Managed Hosts

Suzi reinstalls the /web-server/host1 and /web-server/host2 managed hosts.

$ changemgr reinstall /web-server/host1 /web-server/host2

How to Update Managed Hosts (Command Line)

First use the Change Manager to perform an initial installation before using the Solaris Live Upgrade feature on a managed host. The initial installation creates two boot environments .

1. Determine which managed hosts you want to update.

   For example, update the /web-server/host1 and /web-server/host2 managed hosts.

2. Modify the shared profiles and host properties to reflect the configuration of the managed hosts to update.

3. Update the specified managed hosts.

   $ changemgr update [ -u username ] [ -p file ] [ -d domain ] \ [ -x operation ] topopath ...

   -x operation

   Specify the action to take after the update completes. If operation is reboot, then activate the newly installed software stack and reboot. If operation is halt, then activate the newly installed software stack and halt. The default operation is to reboot.

   topopath

   Specifies the path to a managed host or host group. The managed host or host group is relative to the top of the specified administrative domain.

   For descriptions of the other options, see How to Add Managed Hosts (Command Line).

Example-Updating Managed Hosts

Suzi updates the /web-server/host1 and /web-server/host2 managed hosts. When the update completes, the managed hosts are rebooted to run the newly updated boot environment.

$ changemgr update /web-server/host1 /web-server/host2

Example-Updating Managed Hosts and Halting the Managed Hosts When the Update Completes

Suzi updates the /web-server/host1 and /web-server/host2 managed hosts. When the update completes, the managed hosts are set up to run the newly updated boot environment. Then, the managed hosts are halted.

$ changemgr update -x halt /web-server/host1 \
/web-server/host2

How to Fall Back to the Previous Version of the Software Stack (Command Line)

The fallback operation "undoes" the last update attempt of a managed host, whether it finished or did not start.

For example, three managed hosts are updated one at a time. The update completes on the first managed host. Then, the update begins on the second managed host. When the first managed host boots the updated boot environment, you notice that there are problems with the system. You cancel the running update.

Each of the three managed hosts are in a different state. The first managed host completed the update. The second managed host started the update, but did not complete it. The third managed host did not start the update.

The fallback operation ensures that each of these managed hosts reverts to the boot environment running prior to the update attempt.

The fallback feature fails if the system cannot boot. In such cases, see " Solaris Live Upgrade (Overview)" in Solaris 9 Installation Guide.

1. Determine which managed hosts you want to fall back to the previous active boot environment.

   For example, perform the fallback operation on the /web-server/host1 and /web-server/host2 managed hosts.

2. Fall back to the previous version of the software stack.

   $ changemgr fallback [ -u username ] [ -p file ] [ -d domain ] \ topopath ...

   topopath

   Specifies the path to a managed host or host group. The managed host or host group is relative to the top of the specified administrative domain.

   For descriptions of the other options, see How to Add Managed Hosts (Command Line).

Example-Getting Managed Hosts to Fall Back to the Previous Active Boot Environment

Suzi wants the /web-server/host1 and /web-server/host2 managed hosts to fall back to the previous active boot environment.

$ changemgr fallback /web-server/host1 /web-server/host2

How to Reboot Managed Hosts (Command Line)

1. Determine the managed hosts that you want to reboot.

   For example, you can reboot the /web-server/host1 and /web-server/host2 managed hosts.

2. Reboot the managed hosts.

   $ changemgr reboot [ -u username ] [ -p file ] [ -d domain ] \ topopath ...

   topopath

   Specifies the path to a managed host or host group. The managed host or host group is relative to the top of the specified administrative domain.

   For descriptions of the other options, see How to Add Managed Hosts (Command Line).

Example-Rebooting Managed Hosts

Suzi wants to reboot the /web-server/host1 and /web-server/host2 managed hosts.

$ changemgr reboot /web-server/host1 /web-server/host2

How to Halt Managed Hosts (Command Line)

1. Determine the managed hosts that you want to halt.

   For example, you can halt the /web-server/host1 and /web-server/host2 managed hosts.

2. Halt the managed hosts.

   $ changemgr halt [ -u username ] [ -p file ] [ -d domain ] \ topopath ...

   topopath

   Specifies the path to a managed host or host group. The managed host or host group is relative to the top of the specified administrative domain.

   For descriptions of the other options, see How to Add Managed Hosts (Command Line).

Example-Halting Managed Hosts

Suzi wants to halt the /web-server/host1 and /web-server/host2 managed hosts.

$ changemgr halt /web-server/host1 /web-server/host2