test

Sun Management Center 3.5 Installation and Configuration Guide

Setting Up Sun Management Center 3.5 Using es-setup

This section provides the procedure for setting up Sun Management Center. This procedure assumes that you have not specified any of the es-setup parameters.

To Set Up Sun Management Center Using the es-setup Script

  1. Log in as root on the machine where you installed Sun Management Center.

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


    # cd /opt/SUNWsymon/sbin

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

  3. Run the es-setup script.


    # ./es-setup

    • If you installed only the Sun Management Center console, the setup process sets up the console and then runs setup for any add-ons you selected. Go to Step 16.

    • If you installed only the agent, or agent and console, you are prompted to provide a password for security key generation. Go to Step 5.

    • If you installed the Sun Management Center server, the setup process checks for DB listener port conflict.

      • If the DB listener port is not in use and the system has sufficient memory, you are prompted to provide a password for security key generation. Go to Step 5.

      • If the DB listener port is not in use, and the system does not have sufficient memory, the amount of memory that is available and the amount of memory that is needed is displayed. The setup process exits to the system prompt. Take steps to make enough memory available, and then run setup again.

      • If the DB listener port is in use, you are prompted to assign an unused port.

  4. Resolve DB listener port conflict

    Press Return to accept the alternate default port 2522, or type the number of an unused port. To Determine Whether a Port Is Used describes how to determine whether a port is in use. Reconfiguring Sun Management Center Ports describes how to use the es-config command to reassign Sun Management Center ports.

    The setup process checks the available memory.

    • If the system has sufficient memory, you are prompted to provide a password for security key generation. Go to Step 5.

    • If the system does not have sufficient memory, the amount of memory that is available and the amount of memory that is needed is displayed. The setup process exits to the system prompt. Take steps to make enough memory available, and then run setup again.

  5. Generate the Sun Management Center security key.

    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 that you use to generate the security key for this machine in a secure location in case you 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.

    1. Type the password for the seed to generate the security keys.

    2. Type the password again.

    You are prompted for the SNMPv1 community string.

  6. 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. Keep a record of the community string that you used in a secure location in case you need to specify the community string again at a later time.

    • If you want to accept the community string default value of public, press Return when prompted to submit the SNMPv1 community string.

    • If you want to use a custom community string, type the community string text. The community string can be up to 255 characters in length, but must not contain any spaces or blanks.

      You are prompted to retype the SNMPv1 community string to confirm the string. Type the same string. For example:


      This part of setup configures SNMPv1 read-only community string.
Please make sure you use the same string on all the machines you install.
You may like to keep record of this string for future use.

Hit RETURN key to force default value.
Please enter SNMPv1 community string: my-snmp-string
Please re-enter the SNMPv1 community string to confirm:  my-snmp-string

    The setup process checks which base components have been installed.

    • If you installed only the agent, or agent and console, you are prompted for the .Sun Management Center server host name. Go to Step 9.

    • If you installed the server, 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 exists, the setup process checks for server port conflicts. Go to Step 8.

      • If a valid UNIX administrator account name does not exist, you are prompted for the UNIX administrator account name.

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

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

    The setup process checks for server port conflicts.

  8. Resolve server port conflicts.

    The setup process checks the ports needed by the Sun Management Center server to determine whether the ports are in use. If any ports are in use, you must assign an unused port. To Determine Whether a Port Is Used describes how to determine whether a port is in use. Reconfiguring Sun Management Center Ports describes how to use the es-config command to reassign Sun Management Center ports.

    The ports are checked in the following order: topology service, configuration service, event service, cst service, trap service, metadata service, and look-up service.

    • If no ports are in use and you have installed the Sun Management Center server, you are prompted for the information needed to generate the Web server security key. Go to Step 10.

    • If no ports are in use and you have not installed the Sun Management Center server, you are prompted for the Sun Management Center server host name. Go to Step 7.

    • If any ports are in use, you are prompted to either reconfigure the port, or to stop the process that is using the port.

      • To reconfigure a port, type the number of an unused port.

      • To use the default port, press Return.

        Caution – Caution –

        If you chose to use the default port, you must manually review, identify, and then rename the /etc/rcN and /etc/rcN.d files that use the port, and then manually stop the processes that are using the port before you can start Sun Management Center.

      Once all port conflicts are resolved, the setup process checks whether you installed the server.

      • If you installed the Sun Management Center server, you are prompted for the information needed to generate the Web server security key. Go to Step 10.

      • If you have not installed the Sun Management Center server, you are prompted for the Sun Management Center server host name.

  9. Specify the Sun Management Center server host name.

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

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

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

    For example, you could type administration for the organization, and headquarters for the location.

    Note –

    Keep a record of the entries that 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.

    Type the name of your organization at the prompt. For example: 


    An encrypted security key is needed for the Sun Management Center 
Web server. The key is generated based on the organization and location 
you provide.
Please enter the name of your organization : administration

    You are prompted for your geographical location. Type the name of your location at the prompt. For example: 


    Please enter the geographical location of this host : headquarters

    The setup process checks whether the web server ports are in use.

    • If the web server port and the web server secure port are not in use, the setup process checks whether SNMP port 161 is in use. Go to Step 12.

    • If the web server default port or secure port is in use, you are prompted to assign an unused port.

  11. Resolve web server port conflicts.

    Press Return to use the displayed default port, or type the number of a port that is not in use.

    Caution – Caution –

    If you chose to use the default web server port or secure port, you must manually review, identify, and then rename the /etc/rcN and /etc/rcN.d files that use the port, and then manually stop the processes that are using the port before you can start Sun Management Center.

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

    • If SNMP port 161 is not in use, the setup process checks whether configuration data from a previous version of Sun Management Center has been saved. If you saved the configuration data from a previous Sun Management Center installation, you are asked whether you want to restore the data. Go to Step 14.

      If you did not save configuration data from a previous installation, or if this is the first time Sun Management Center has been installed on this machine, then the setup process lists the setup status for the core products you selected. Go to Step 15.

    • If SNMP port 161 is in use, you are prompted to assign an SNMP port number.

  12. Resolve the SNMP port conflict.

    You are notified that port 161 is in use by another process. In most cases, port 161 is the port that is 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 you can assign 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 as you had in the previous Sun Management Center installation for both agent and server upgrades.

    1. To assign a different port number, type an unused port number.

      For example: 


      Enter the port you want to use [ 1100 to 65535 ]: 1161
Updating /var/opt/SUNWsymon/cfg/domain-config.x with new port number.

      Note –

      Keep a record of this alternate port number. You will need this number if you later install agents using the JumpStart software, 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 did not save configuration data from a previous installation, or if this is the first time Sun Management Center has been installed on this machine, the setup process lists the setup status for the core products you selected. Go to Step 15.

    2. To use port 161, press Return.

      You are informed that port 161 will be used by Sun Management Center, and that the SNMP daemon might be set to restart automatically when the system is rebooted.

      You are asked whether you want to stop and disable the SNMPDX daemon.

  13. Stop and disable the SNMP daemon.

    • Type y to stop and disable the SNMP daemon.

      Caution – Caution –

      Stopping and disabling the SNMP daemon is not a guarantee that you have stopped the actual process that is using port 161. If Sun Management Center fails to start after you have completed Sun Management Center setup, another process or daemon could be using port 161. As noted in Step 12, you must manually review, identify, and then rename the /etc/rcN and /etc/rcN.d files that use port 161 to resolve the port conflict.

    • Type n if you do not want to stop and disable the SNMP daemon.

      Caution – Caution –

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

    The setup process checks for configuration data from a previous version of Sun Management Center.

    • If you did not save configuration data from a previous installation, or if this is the first time Sun Management Center has been installed on this machine, the setup process lists the setup status for the core products you selected. Go to Step 15.

    • If you saved the configuration data from a previous Sun Management Center installation, you are asked whether you want to restore the 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, type y and press Return. The configuration data from the previous Sun Management Center is restored.

    • To discard the configuration data, type n and press Return. The configuration data from the previous Sun Management Center is deleted.

    The setup process lists the setup status for the core products you selected.

  15. Finalize the base product setup process.

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

      Review the log file to determine the cause of setup failure.

    • If base product setup succeeded, and you selected one or all of the base products only (console, agent, and server), you are asked whether you want to start the Sun Management Center components. Go to Step 17.

    • If base product setup succeeded and you selected any add-on products, the setup process runs the setup script for each add-on product you selected.

  16. Set up add-on products.

    Some add-on products are included with the Sun Management Center 3.5 installation CDs. These add-ons are the ones listed in Step 13, in the procedure To Install Using the es-inst Script. 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, apply the necessary patches to the server as described in Sun StorEdge A5x00 Patches. Also, add the T3 IP address, Ethernet address and name to the server system files as described in T3 Storage Devices.

    When the add-on setup is completed, the setup process lists the setup status for the add-on products.

    • If add-on product setup failed, you are informed that the setup of the add-on product was not successful. You are then directed to see the log file for more details. The name of the log file is provided. The setup process exits to the system prompt.

      Review the log file to determine the cause of setup failure.

    • If add-on setup succeeded, you are asked whether you want to start the Sun Management Center components.

  17. Start Sun Management Center 3.5.

    Caution – Caution –

    If your network uses Network Address Translation (NAT), type n to exit setup without starting Sun Management Center. 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.