Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP Systems Insight Manager 5.0 Installation and User Guide > Chapter 7 Upgrading from HP Servicecontrol Manager to HP Systems Insight Manager

Upgrading from SCM 3.0 to HP Systems Insight Manager 4.2

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Glossary

 » Index

NOTE: During an upgrade of SCM 3.0 to HP SIM, the existing database is migrated and the password is preserved in the back up directory.When upgrading SCM 3.0 to HP SIM, new Remote Method Invocation (RMI) keys and a keystore are created. The keystore is moved to a back up directory.
  1. Verify that SCM is running by entering the following:

    ps -ef | grep mx

    Wait some time, and if SCM is not running, start the service:

    /opt/mx/bin/mxstart

  2. Tune the kernel using the Java Out-of-Box fileset. For more information, go to http://www.hp.com/products1/unix/java/java2/outofbox/index.html. This product can be available for you to install with HP SIM, either as part of the download depot file containing HP SIM 5.0 or from the Application Release media. The kernel parameter values it adjusts are listed in the following table.

    NOTE: Java Out-of-Box is a stand-alone bundle that reboots the system after it is installed.

    Java Out-of-Box settings

    Java Out-of-Box settingsKernel parameter values

    max_thread_proc

    3000

    maxdsiz

    2063835136

    maxfiles

    2048

    maxfiles_lim

    2048

    maxusers

    512

    nfile

    4097

    nkthread

    6000

    nproc

    2048

    tcp_conn_request_max

    2048

    NOTE: The maxusers parameter is obsolete in HP-UX 11i v2 (September 2004 or later) (B.1 1 .23).
  3. Using SAM or the HP-UX Kernel Configuration tool (kcweb), complete the following manual parameter adjustments.

    1. Set the dbc_max_pct kernel parameter, which is the percentage of physical memory that can be dynamically allocated for the data buffer cache. It defaults to 50%, which is usually too high. Set this variable to the percentage of your system physical memory that equals approximately 200 MB. For example, a server with 1 GB of RAM should have this value set at 20%.

      Note: This value cannot be less than dbc_min_pct, which cannot be less than 1% of your system physical memory.

    2. Increase the nfile parameter to at least 12000. This value might be increased to 30000 depending on your environment. If you get an error that you cannot open a file, increase this value.

    3. For proper database operation, set the "semmns" kernel parameter to a minimum value of 2048 and the semmni kernel parameter to a minimum value of 1024.

      Note: For HP-UX 11i v2 (September 2004 or later) (B.11.23), these parameters are dynamic, and when you modify the parameters, a reboot of the system is not necessary.

  4. Install PostgreSQL, SSH, and WBEM:

    swinstall -s /directory/depot ixPostgreSQL T1471AA B8465BA

    where directory is the path to the depot file and depot is the name of the depot file. For example:

    swinstall -s /tmp/HPSIM_download.depot ixPostgreSQL T1471AA B8465BA

    NOTE: To verify that the WBEM (cimserver, cimserverd) and SSH (sshd) daemons are running, enter the following commands:

    psef | grep wbem

    psef | grep ssh

  5. Install HP Systems Insight Manager:

    swinstall -s /directory/depot T2414BA

    where directory is the path to the depot file and depot is the name of the depot file. For example:

    swinstall -s /tmp/HPSIM_download.depot T2414BA

  6. Verify that the mxdomainmgr and mxdtf daemons are running:

    ps -ef | grep mx

    If they are not running, start them:

    /opt/mx/bin/mxstart

  7. (Optional) Configure SNMP to send traps to the CMS:

    1. Add the full host name or IP address of the CMS as a trapdest in the file /etc/SnmpAgent.d/snmpd.conf.

      trap-dest: hostname_or_ip_address

    2. Stop the SNMP Master agent and all subagents with the following command:

      /sbin/init.d/SnmpMaster stop

    3. Restart the SNMP Master agent and all subagents with the following command:

      /usr/sbin/snmpd

  8. Log in to the HP Systems Insight Manager GUI. For assistance with this, refer to Chapter 10 “Using the Graphical User Interface”.

  9. If, after logging in to HP Systems Insight Manager, you find that some items (toolboxes, users, tools, systems, system groups, or authorizations) did not upgrade correctly, perform the following. Otherwise, continue to step 10.

    IMPORTANT: These steps must be performed in the order specified. You can, however, start with the first step that applies to you. For example, if node groups and authorizations failed to migrate, but everything else migrated properly, start with step e.

    1. Migrate toolboxes (roles) by running the following command from the command line on the CMS:

      mxtoolbox -af /var/opt/mx/bak/3.0/zzz_mxrole.3_0.xml

      If the message A toolbox named <toolbox> already exists in the system appears, log in to HP Systems Insight Manager and delete all toolboxes except for All Tools and Monitor Tools, and repeat this step.

    2. Migrate users by running the following command from the command line on the CMS.

      mxuser -af /var/opt/mx/bak/3.0/zzz_mxuser.3_0.xml

      If the message A user named <user> already exists in the system is displayed, log in to HP SIM and delete all users except for the user used to log in, and repeat this step.

    3. Migrate tools by running the following command from the command line on the CMS:

      mxtool -af /var/opt/mx/bak/3.0/zzz_mxtool.3_0.xml

      This command can display many Cannot add <tool> because it already exists in the system messages, but these messages can be safely ignored.

    4. Migrate updated definition of tools and ensure all the tools are displayed correctly within the HP Systems Insight Manager tool menu by running the following command from the command line:

      sh fixmenu.sh scmtdefs.data /var/opt/mx/bak/3.0/tools /var/opt/mx/tools

    5. Migrate systems (nodes) by running the following command from the command line on the CMS:

      mxnode -af /var/opt/mx/bak/3.0/zzz_mxnode.3_0.xml

      If mxnode encounters any duplicate systems (nodes), it continues without displaying any messages.

      If mxnode encounters a host name that cannot be resolved, the following error message appears. Unknown host: <node_name>. Node ignored. The remaining nodes continue to be processed. However, the missing node might affect the success of migrating node groups.

      IMPORTAINT: When the command returns, log in to HP Systems Insight Manager, display the All Systems list, and wait for all of the expected nodes to appear in the list before proceeding to the next step. The amount of time varies based on system performance and the number of nodes being added.

    6. Migrate system groups (node groups) by running the following command from the command line on the CMS:

      mxngroup -af /var/opt/mx/bak/3.0/zzz_mxngroup.3_0.xml

      If the message A node group named <group> already exists in this system is displayed, log in to HP SIM and delete all node groups except for All Managed Systems and CMS, and repeat this step.

      If the message The name <node_name> does not represent a node in this system is displayed, then a node in the node group is missing, and processing on the file stops. Add the node using mxnode -a <node_name> or log in to HP SIM and add the node through Manual Discovery, then repeat this step.

    7. Migrate authorizations by running the following command from the command line on the CMS.

      mxauth -af /var/opt/mx/bak/3.0/zzz_mxauth.3_0.xml

      If this command encounters any duplicate authorizations, it continues properly without displaying any messages.

      Note: If the names contain characters such as underscore, space, and symbols, they might not be migrated because these characters are not supported.

    8. If after taking the previous steps, items such as menus are still missing or out of place, run the following command:

      sh /opt/mx/bin/fixmenu.sh scmtdefs.data /var/opt/mx/bak/3.0/tools /var/opt/mx/tools

  10. Using the GUI, add the default WBEM user name and password to the Global Protocol Settings page.

    Note: An account for at least one of the WBEM user name and password combinations must exist on the CMS.

    1. Select Options->Protocol Settings->Global Protocol Settings.

    2. In the Default WBEM settings section, ensure that the Enable WBEM checkbox is selected and add the default WBEM user name and password.

    3. Click OK.

Note: After upgrading to HP Systems Insight Manager, you must run identification for all network devices, racks, and enclosures to be displayed on the System Overview page.

In order to upgrade a SCM 3.0 to HP Systems Insight Manager 5.0, SCM must be upgraded to HP Systems Insight Manager 4.2 first. After this initial upgrade, follow the procedure to upgrade HP Systems Insight Manager 4.2 to 5.0. Refer to Chapter 8 “Upgrading HP SIM 4.x to HP SIM 5.0 ” for more information.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 2003-2005 Hewlett-Packard Development Company, L.P.