test

Sun Management Center 3.5 Installation and Configuration Guide

Setting Up Base Products and Add-ons on the Solaris Platform

You can use the graphical setup wizard es-guisetup to set up, configure, and re-configure your Sun Management Center installation. For information on using the es-setup command-line setup script, see To Set Up Sun Management Center Using the es-setup Script.

To Set Up Sun Management Center 3.5 on the Solaris Platform
Note –

This procedure assumes that you installed Sun Management Center in the default directory /opt. If you installed Sun Management Center in a different directory, replace /opt with the name of the directory you specified in To Install Sun Management Center 3.5 on the Solaris Platform, Step 8.

  1. Open a terminal window, then type the command xhost + in the terminal window.

    Also, ensure that the DISPLAY environment variable is set to the machine's display.

  2. Log in as root on the machine where you installed the Sun Management Center 3.5 base components and add-ons.

  3. Go to the Sun Management Center sbin directory. For example:


    # cd /opt/SUNWsymon/sbin

    If you installed Sun Management Center in a directory other than /opt, go to /installdir/SUNWsymon/sbin, where installdir is the directory you specified in Step 8 in the procedure To Install Sun Management Center 3.5 on the Solaris Platform.

  4. Run the es-guisetup script:


    # ./es-guisetup

    The Welcome screen appears. Ensure that you have the information listed, and then click Next.

  5. Review the information that is required for Sun Management Center setup.

    Ensure that you have the information listed, and then click Next.

    • If you installed only the console, the console is set up, and the setup status screen appears.

      Click Cancel to exit. You can start the Sun Management Center console as described in Starting the Console.

    • If you installed only the agent, or the agent and console, the Generate Security Key screen appears. Go to Step 7.

    • If you installed only the agent or the agent and console, the Store Setup Response Data screen appears.

  6. Store setup response data if desired.

    You are given the opportunity to store all of your setup responses in the file /var/opt/SUNWsymon/install/setup-responses-file. The setup-responses-file file is useful if you need to duplicate the setup on the current machine on other machines.

    • To continue setup without creating the response file, click Next.

    • To create the response file, select Store Response Data and then click Next.

      Your responses to each of the following steps are stored in /var/opt/SUNWsymon/install/setup-responses-file.

    The Generate Security Key screen appears.

  7. Generate the Sun Management Center security key.

    Type a password in both fields and click Next to generate the security keys.

    An encrypted security key is needed for communications between all Sun Management Center processes. The key is generated based on the password you provide, which must be between one and eight characters long and contain no spaces. Entries that are greater than eight characters are truncated to eight characters.

    Note –

    Keep a record of the password you use to generate the security key for this machine in a secure location. You might need to regenerate the key for the machine at a later time. You can also change the security key later, if needed, as described in Regenerating Security Keys.

    The SNMPv1 Community String screen appears.

  8. Specify the SNMPv1 community security string.

    The community string is used for SNMP security, and is set to public by default.

    Set the community string to a value other than public or private to provide better SNMP security.

    Caution – Caution –

    The same SNMP community string must be used on all of the machines on which you install Sun Management Center 3.5. If you use different community strings on each machine, SNMP communications between the machines and Sun Management Center components will not work.

    • If you want to accept the community string default value of public, click Next.

    • If you want to use a custom community string:

      1. Select Use Custom Community String.

        The community string can be up to 255 characters and must not contain any spaces or blanks.

      2. Type the same community string in both fields, and then click Next.

    The setup process checks which base components have been installed.

    • If you installed only the agent or agent and console, the Specify Host Name screen appears. Go to Step 9.

    • If you installed the server, or the server, agent, and console, the setup process checks for a valid UNIX administrator account name for the Sun Management Center esadm and esdomadm groups. See Users, Groups, and Roles Overview for information about groups.

      • If a valid UNIX administrator account name does not exist, the Administrator Account Name screen appears. Go to Step 10.

      • If a valid UNIX administrator account name exists, the setup process checks whether the SNMP port is in use. Go to Step 11.

  9. Specify the Sun Management Center server host name.

    Type the name of the machine on which the Sun Management Center server was installed and click Next.

    The setup process checks whether the SNMP port is in use. Go to Step 11.

  10. Type a valid Solaris user name as the UNIX administrator account.

    A valid Solaris user name is required for Sun Management Center administration. Type a valid Solaris user name.

    The install process checks whether the SNMP port is in use.

    • If the SNMP port is not in use, the install process checks whether the Sun Management Center ports are in use.

      • If you have installed only the agent, or the agent and console, the Confirmation screen appears. Go to Step 16.

      • If you have installed the server and any Sun Management Center port is in use, you must resolve the port conflict. Go to Step 13.

      • If you have installed the server and none of the Sun Management Center ports are in use, the Web Server Security Key screen appears. Go to Step 15.

    • If the SNMP port is in use, the SNMP Port Conflict screen appears.

  11. Resolve the SNMP port conflict.

    You are notified that port 161 is in use by another process. In most cases, port 161 is the default port assigned to and used by the SNMP daemon. However, other processes or daemons could be using port 161. Several third-party replacements and enhancements for the SNMP daemon exist, and could be installed on your system. The Sun Management Center agent is such a daemon.

    You can choose to use port 161 or to use a different port number.

    Caution – Caution –

    If you chose to restore the configuration data from a previous Sun Management Center installation, make sure you use the same port number for the agent as you had in the previous Sun Management Center installation. This advice is applicable for both agent upgrade and server upgrade.

    • To assign a different port number:

      1. Select Use a Different Port Number.

        For instructions on how to find out whether a port is unused, see To Determine Whether a Port Is Used.

      2. Type the port number in the Port ID field and click Next.

        Note –

        Keep a record of this alternate port number. You will need this number if you later install agents using JumpStart, or update the Sun Management Center agents using the agent update-image tools. For more information, see Installing Agents Using JumpStart and Creating Agent Installation and Update Images.

        • If you have installed only the agent or the agent and console, the Confirmation screen appears. Go to Step 16.

        • If you have installed the server, the install process checks whether the Sun Management Center ports are in use.

          If any Sun Management Center port is in use, you must resolve the port conflict. Go to Step 13.

          If none of the Sun Management Center ports are in use, the Web Server Security Key screen appears. Go to Step 15.

    • To use port 161, select Use Port 161 and click Next.

      You are prompted to stop and disable the SNMP daemon snmpdx.

  12. Stop and disable the SNMP daemon snmpdx.

    • To stop and disable the SNMP daemon snmpdx automatically, make sure that Stop and Disable SNMP Daemon snmpdx has been selected, and then click Next.

      Caution – Caution –

      Stopping and disabling the system SNMP daemon does not guarantee that you have stopped the actual process using port 161. To determine the actual daemon process that uses port 161, you must manually review all /etc/rcN and /etc/rcN.d files, where N is 0 through 6 and S. When you have identified the file that defines the process using port 161, you can disable the process by renaming the file. For example, 


      /etc/rc3.d# mv S76snmpdx s76snmpdx

      You must stop all other processes that use port 161 before you can start Sun Management Center.

    • To assign an unused port, click Back and follow the instructions in Step 11.

    The setup process checks whether any Sun Management Center ports are in use.

    • If none of the Sun Management Center ports are in use, the Web Server Security Key screen appears. Go to Step 15.

    • If any Sun Management Center port is in use, you must resolve the port conflict.

  13. Resolve Sun Management Center port conflicts.

    The ports are checked in the following order: trap service, event service, topology service, configuration service, platform agent, cst service, metadata service, database, look-up service, Web server default port, and Web server secure port.

    If any of the ports are in use, you are prompted to provide an unused port number. Type an unused port number in the field, and then click Next.

    • If you have installed Sun Management Center for the first time or if you chose to delete the configuration data from a previous version of Sun Management Center, the Web Server Security Key screen appears. Go to Step 15.

    • If you chose to migrate the configuration data from a previous version of Sun Management Center, you are prompted to restore the previous Sun Management Center configuration data.

  14. Restore previous Sun Management Center configuration data.

    The saved configuration data includes the graphs, topology objects, alarms, and other information that is displayed in the Sun Management Center console.

    Caution – Caution –

    If you do not restore the configuration data from the previous installation of Sun Management Center, you will have to manually re-create the information.

    • To restore the configuration data, select Restore Configuration Data and then click Next.

      The configuration data from the previous Sun Management Center is restored.

    • To discard the configuration data, select Do Not Restore Configuration Data and then click Next.

      The configuration data from the previous Sun Management Center is deleted.

    The Web Server Security Key screen appears..

  15. Generate the Web server security key.

    An encrypted security key is needed for the Sun Management Center Web server. The key is generated based on the name of your organization and the name of your location. The names that you provide must not contain any spaces or blanks.

    Type the name of your organization and the name of your location to generate the Web server security key.

    For example, you could type administration in the Name of Your Organization field, and headquarters in the Name of Your Location field.

    Note –

    Keep a record of the entries you use to generate the security key in a secure location in case you need to regenerate the key for a particular machine at a later time.

    Click Next. The Confirmation screen appears.

  16. Confirm setup selections.

    • If the selections are not correct, click Back to return to previous screens and change your choices.

    • Click Next to accept the choices and start Sun Management Center setup. The Setup Progress panel appears.

      The setup process can take from a few minutes to half an hour or more, depending on the products selected.

    When the setup process completes, the Sun Management Center Core Product Setup Complete panel appears.

  17. Verify the setup status.

    The Sun Management Center Core Product Setup Complete panel lists the setup completion status.

    • If base product setup failed, you are informed that the setup of the base products was not successful. You are directed to see the log file for more details. The name of the log file is provided.

      Click Cancel to return to the system prompt. Review the log file to determine the cause of setup failure.

    • If setup succeeded and you selected only one or more of the base products (console, agent, and server), you are informed that base product setup is complete. A list of the base products that you installed and set up is displayed.

      Click Next. You are informed that there are no add-on products to set up. You can now either start Sun Management Center 3.5, or close the wizard so you can perform other tasks before starting Sun Management Center.

    • If setup succeeded and you selected add-on products, you are informed that Sun Management Center base product setup is complete. If you selected any base products, a list of the base products that you installed and set up is displayed. A list of the add-on components that you selected for installation is also displayed.

      • Click Cancel to exit setup and set up the add-on products later. See the documentation for individual add-on products for setup instructions.

      • Click Next to set up the add-on products. The setup process runs the graphical user interface setup wizard for each add-on product that you selected.

        Some add-on products are included with the Sun Management Center 3.5 installation CDs. These add-ons are the ones listed in the Select Add-on Products panel in Step 13 of To Install Sun Management Center 3.5 on the Solaris Platform. For information on how to set up each add-on, refer to the Sun Management Center supplement for each add-on, which is included in your installation kit. Each supplement provides the setup procedure for the specific add-on. The setup procedure for add-ons is therefore not duplicated here.

        Caution – Caution –

        If you selected the add-on Monitoring and Management of A5x00 and T3 Devices, ensure you apply the necessary patches to the server as described in Sun StorEdge A5x00 Patches. Also, add each T3 IP address, Ethernet address, and name to the server system files, as described in T3 Storage Devices.

        When each add-on setup completes, an add-on setup status panel appears.

        If add-on product setup failed, you are informed that the setup of the add-on products was not successful, and directed to see the log file for more details. The name of the log file is provided. Click Cancel to return to the system prompt, and review the log file to determine the cause of setup failure.

        If all add-on setups succeeded, you are informed that Sun Management Center base product setup is complete. If you selected any base products, a list of the base products that you installed and set up is displayed. A list of the add-on components that you installed and set up is also displayed.

        You are given the opportunity to start Sun Management Center.

  18. Start Sun Management Center 3.5.

    Caution – Caution –

    If your network uses Network Address Translation (NAT), click Close. Use the es-config command-line utility described in To Enable NAT Support to configure the machine for NAT before you start Sun Management Center.