test

Installing and Administering Solaris Container Manager 3.6.1

Setting Up Container Manager

After installation is complete, you must run the Container Manager setup script to configure the server and agent layers. As with installation of the software, you can run the setup process at the time you set up the Sun Management Center 3.6.1 installation or upgrade. You can also set up the software individually, at a later time.

The configuration file changes that occur during the setup process when initiated from the command line are identical to the configuration file changes that occur when using the setup wizard. For more information, see Setting Up Container Manager Software.

ProcedureTo Set Up Container Manager During Sun Management Center Installation or Upgrade

Step

    For more information and detailed steps, see Appendix B, Using the Command Line for Uninstall, Install, and Setup, in Sun Management Center 3.6.1 Installation and Configuration Guide.

ProcedureTo Set Up Container Manager Individually

Note –

This procedure assumes that you chose not to set up Container Manager at the end of the installation process.

Steps

  1. Run the Sun Management Center 3.6.1 setup script as superuser (su –). Choose one of the following options:

    • To run setup on all components that are not yet set up, type:


      # /opt/SUNWsymon/sbin/es-setup

    • To run setup on the Container Manager add-on software only, type:


      # /opt/SUNWsymon/sbin/es-setup -p SCM

      where /opt is the directory in which Sun Management Center 3.6.1 is installed. Substitute the name of the actual directory if it is different on your system.

  2. Review the list of components that must be stopped for the set up process to continue.

  3. Confirm that Container Manager is the product to be set up.

  4. When setting up the agent layer, if processor sets are detected on the system that are not associated with a resource pool, select from the following:

    • Yes – These particular processor sets will be deleted from the system. For Container Manager to function correctly, any processor set that is not associated with a resource pool must be removed as the set might cause problems with pool management. After this selection, these processor sets are automatically deleted, and the setup process continues.

    • No – These particular processor sets will not be deleted from the system. After this selection, the setup script exits and the Container Manager software is not set up on the system. You are unable to use the Container Manager software on any host on which exist processor sets that are not associated with a resource pool.

    • Cancel – The setup script exits. The Container Manager software is not set up on the system.

  5. Type the valid user names separated by commas. These users must already be present in the /var/opt/SUNWsymon/cfg/esusers file on the server machine, and must be assigned to either esadm or esdomadm group.

    These users will be added to the required profiles (Project Management, Pool Management, Zone Management) if both users and profiles are present as expected. The profiles are based on the Solaris version.

    On each agent machine, run the /opt/SUNWsymon/addons/SCM/sbin/scm-poolprof-script.sh script to create the profiles. /opt is the directory in which Container Manager is installed. To run this script, the JAVA_HOME environment variable must have been set to /usr/j2se, or Java must have been installed in /usr/java.

    This script will NOT create any Zone Management or Project Management profiles for S9 and S10. This script will ONLY create Pool Management profile for S9 and S10 and Project Management profile for S8.

    Caution – Caution –

    If any of the predefined Solaris profiles are removed, then Container Manager might not work as expected.

    Note –

    Only the users added in this step will be able to manage zones on S10, resource pools on S9 and S10, and projects on S8, S9, and S10.

  6. If you have previously completed the setup process for other Sun Management Center products, indicate whether you want to run setup again for all software or just the newest add-on software.

  7. When setting up a server layer installation, provide the full path to a directory that has at least 300 Mbytes of free disk space for the database.

  8. Indicate whether you want to start the Sun Management Center agent and server components by answering Y or N.

    You receive confirmation when the software is set up.

    After the setup procedure is complete, you have the option to start the Sun Management Center processes. For more information, see Chapter 8, Starting and Stopping Sun Management Center, in Sun Management Center 3.6.1 Installation and Configuration Guide.

Example A–1 Example Output After Setup Is Complete

The following is an example of the output you see after setup is complete and the Sun Management Center agent and server layers have been started:


Do you want to start Sun Management Center agent and server components now (y|n|q) y

Java server started successfully.
Grouping service started successfully.
Agent started successfully.
Topology service started successfully.
Trap-handler service started successfully.
Configuration service started successfully.
Event-handler service started successfully.
Metadata Service started successfully.
Hardware service started successfully.


Web server started successfully.

Setup of Sun Management Center is complete.
Setup logfile is : /var/opt/SUNWsymon/install/setup_host_name.040408141450.12822

Install logfile is : /var/opt/SUNWsymon/install/install_host_name.040408140547.10929

                        End of Installation


Exiting Sun Management Center installation.

#