Setting up an HP SIM server 5.x on a Linux-based Serviceguard Cluster 444847-003, March 2009
5
15. Initialization and Database Population ..OK
Status : Unconfigured
Completed all tasks successfully.
This utility should report that all server components are acceptable and that
all tasks
completed
successful
ly.
If
the utility reports an issue, see the
HP Systems Insight Manager 5 Installation and
Configuration Guide for Linux
.
7.
Initialize and configure HP SIM by executing the following command:
#
/opt/mx/bin/mxinitconfig
-
a
Checking Requisites (15):
1. Chec
k Kernel Parameters ..OK
2. Node Security File ..OK
3. Server Property File ..OK
4. Server Authentication Keys ..OK
5. SSH Keys ..OK
6. Status Property File ..OK
7. Task Results Output Cleanup ..OK
8. Database Configuration ..OK
9. Database
Content ..OK
10. Web Server ..OK
11. Setup Property File ..OK
12. JBoss Setup ..OK
13. Agent Configuration ..OK
14. Management Services ..OK
15. Initialization and Database Population ..OK
Requisite scan completed successfully.
Configuring Se
rver Components (15):
1. Check Kernel Parameters ..Done
2. Node Security File ..Done
3. Server Property File ..Done
4. Server Authentication Keys ..Done
5. SSH Keys ..Done
6. Status Property File ..Done
7. Task Results Output Cleanup ..Done
8. Database Configuration ....Done
9. Database Content ..Done
10. Web Server ..Done
11. Setup Property File ..Done
12. JBoss Setup ..Done
13. Agent Configuration ..Done
14. Management Services ..Done
15. Initialization and Database Populatio
n ....
-
Start initialization .....Done
-
Configuring tools and populating tools database
.....................Done
-
Initializing database ..........Done
-
Compiling MIB and populating MIB database ....Done
Completed all tasks successfully
.
Details can be found in the log files at: /var/opt/mx/logs
The initialization of the upgrade
runs
in the background, which takes several minutes. To verify if
the upgrade is 100% complete, view the
log
file by executing the following command:
# cat /var
/opt/mx/logs/initconfig.log
8.
Verify that the
mxdomainmgr
,
mxinventory
, and
mxdtf
daemons are running by executing the
following command:
# ps
–
ef | grep mx