 |
» |
|
|
|
| | | |  | NOTE: During an upgrade of SCM 3.0 to HP Systems Insight Manager, the existing
database is migrated and the password is preserved in the backup directory.When upgrading SCM 3.0 to HP Systems Insight Manager, new RMI keys and
a keystore are created. The keystore is moved to a backup directory. | | | | |
Steps 7 through 9 are optional: To upgrade SCM 3.0 to HP Systems Insight Manager, first verify that
SCM is running by entering the following: ps -ef | grep mx Wait some time, and if they are not running, start the service: /opt/mx/bin/mxstart Tune the kernel using the Java-out-of-box (JavaOOB) fileset. For information
on this, go to http://www.hp.com/products1/unix/java/java2/outofbox/index.html. This
product may be available for you to install with HP Systems Insight Manager,
either as part of the download depot file containing HP Systems Insight Manager
4.2. 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 upon installation will
reboot the system. | | | | |
Java Out-of-Box Settings | | | | | NOTE: The maxusers parameter is obsolete in HP-UX 11i v2 (B.11.23). | | | | |
Using SAM or the HP-UX Kernel Configuration tool (kcweb), complete the
following manual parameter adjustments. The JOOB file will only set the nfile parameter to 4097. Increase the nfile parameter to at least 12000. This value
might need to be increased to 30000 depending on your environment. If you
get an error that you cannot open a file, increase this value. Set the dbc_max_pct kernel
parameter. This 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%. For proper database operation, set the "semmni" kernel parameter to
a minimum value of 250, and the "semmns" kernel parameter to a minimum value
of 1024. Note: For HP-UX 11i v2 (B.11.23) these
parameters are dynamic and when you modify the parameters a reboot of the
system is not necessary.
Install Java, PostgreSQL, SSH, and WBEM: swinstall -s /directory/depot T1458AAventi
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
T1458AAventi ixPostgreSQL T1471AA B8465BA 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 Verify that the mxagent, mxdomainmgr, and mxdtf daemons are running: ps -ef | grep mx If they are not running, start them: /opt/mx/bin/mxstart Configure SNMP to send traps to the CMS: Add the full hostname or IP address of the CMS as a trapdest in the
file /etc/SnmpAgent.d/snmpd.conf trap-dest: hostname_or_ip_address Stop the SNMP Master agent and all subagents with the command: /sbin/init.d/SnmpMaster stop Restart the SNMP Master agent and all subagents with the command: /usr/sbin/snmpd
Log into the HP Systems Insight Manager GUI. For assistance with this,
refer to Chapter 10 “Using the Graphical User Interface”. If after logging into 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, skip to step
10. IMPORTANT: These steps must be performed
in the order specified. You can, however, skip to 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. 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 is displayed, log into HP Systems
Insight Manager and delete all toolboxes except for All Tools and Monitor
Tools, and repeat this step. 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 into HP Systems
Insight Manager and delete all users except for the user used to log in, and
repeat this step. 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 can display many Cannot add <tool>
because it already exists in the system messages, but these
can be safely ignored. 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 Migrate systems (nodes) by running the following command from
the command line on the Central Management Server. mxnode -af /var/opt/mx/bak/3.0/zzz_mxnode.3_0.xml If mxnode encounters any duplicate
systems (nodes), it will continue properly without displaying any messages. If mxnode encounters a hostname that
cannot be resolved, the following error message is displayed. Unknown host: <node_name>. Node ignored. The
remaining nodes will continue to be processed. However, the missing node might
affect the success of migrating node groups. IMPORTAINT: When the command returns,
log into 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. 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 into HP Systems
Insight Manager 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 into HP Systems Insight Manager and add the node through Manual Discovery,
then repeat this step. 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. 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
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. Select Options Protocol SettingsGlobal Protocol Settings. In the Default WBEM settings section,
ensure that the Enable WBEM checkbox
is selected and add the default WBEM user name and password. 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. |
Printable version
