test

Sun Management Center Change Manager 1.0 Administration Guide

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

Note -

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.

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