Installing and configuring the software

Extract the .rpm files from the .bin file. Set the permissions to include the right to execute the .bin file by executing the following command:

chmod u+x HPSIM-Linux_C.05.*.bin

./HPSIM-Linux_C.05.*.bin --keep --confirm

Note: Refer to Step 8 in the "Installing on Linux - Preparing the System" section for information on setting permissions.

Note: If you receive the error: Creating directory mxserver mkdir: cannot create directory 'mxserver': File exists ./HPSIM-Linux_C.05.00.02.00.bin: line 123: Cannot create target directory: command not found ./HPSIM-Linux_C.05.00.02.00.bin: line 124: you should perhaps try option -target OtherDirectory: command not found remove the directory mxserver and its contents, then rerun the installation.

Respond negatively to the prompt to run scripts for an Automatic install. The extracted files are placed in an mxserver subdirectory.

To change the directory to mxserver, execute the following command:

cd mxserver.

	NOTE: If you are using PostgreSQL as your database, continue with steps 4 through 6. If you are using Oracle as your database, skip to step 7.

Install the PostgreSQL database, using the appropriate .rpm files in the following order.

Note: If you are installing the CMS on a supported 64-bit operating system, you must install the 64-bit version of PostgreSQL supplied with your operating system, even if you plan to use an Oracle database.

Note: The rpm -i Postgresql-*.rpm command installs PostgreSQL on your system.

Verify that the PostgreSQL status reads running.

If you are using PostgreSQL as your database and PostgreSQL is configured properly and running, install HP Systems Insight Manager using the .rpm files by executing the following command:

rpm -ivh hpsim*.rpm

If you are using Oracle as your database, install HP Systems Insight Manager using .rpm files by executing the following command:

rpm -ivh hpsim-C.05*.rpm -nodeps

Note: If you are installing the CMS on a supported 64-bit operating system, you must install the 64-bit version of PostgreSQL supplied with your operating system, even if you plan to use an Oracle database.

Note: After installation is complete, log out of the operating system and log back in to set all the correct file permissions and system environmentals.

If using Oracle as your database, continue with step 2. If you are using PostgreSQL as your database, continue with step 3.

For an Oracle database, run one of the following commands:

mxoracleconfig

located at /opt/mx/bin before proceeding with the following steps. This command can be invoked with or without command line arguments.

mxoracleconfig

You will be prompted for individual information for your Oracle database.

Host: Enter the IP address or host name of the Oracle server.

Port [1521]: Enter the same port number, then press Enter.

Database name: Enter your database name.

Username: Enter the username of your database.

Password: Enter the password of your database.

Oracle driver jar file: Enter the full location of the Oracle jar file.

Force [N]: Press Enter.

Or

You can use the mxoracleconfig command with all parameters as shown below:

mxoracleconfig –h hostname [-n port number] –d database name –u username – p password [–j driver jar file location] [-f ]

–h Hostname

Full DNS name or IP address of the Oracle server.

-n Port number

Port number to be used to connect to the oracle instance. Default port is 1521.

–d Database name

Name of database instance.

–u Username

Database user name.

–p Password

Database password for the corresponding user name.

–j Driver file location

Full path to thin driver .jar file. This is not required if the .jar file is already in the class path for HP Systems Insight Manager and JBoss. Mxoracleconfig reports an error if the driver class cannot be loaded. Mxoracleconfig will not copy over a .jar file if it already exists in the classpath for HP Systems Insight Manager and JBoss.

–f Force flag to force a re-run.

Typically, this command is run only once. This flag is provided if a re-run is required because of some type of user error such as specifying the wrong Oracle server or database instance.

Note: Execute the mxoracleconfig command before the mxinitconfig command so that mxinitconfig will use Oracle as the database.

Test the prerequisites by executing the following command:

/opt/mx/bin/mxinitconfig -l

This utility should report that all server components are OK and that it completed all tasks successfully.

Note: HP recommends resolving any warnings before continuing with the initializing and configuring HP Systems Insight Manager process.

Initialize and configure HP Systems Insight Manager by executing the following command:

/opt/mx/bin/mxinitconfig -a

Note: The initialization of the upgrade is done in the background, which takes several minutes. To verify if the upgrade is 100% complete, view the file by executing the following command:

more /var/opt/mx/logs/initconfig.log

Verify that the mxdomainmgr, mxinventory and mxdtf daemons are running by executing the following command:

ps -ef | grep mx

If they are not running, start them by executing the following command:

/opt/mx/bin/mxstart

Configure the system to send SNMP traps.

Note: These steps might vary slightly, depending on your version of Linux. Refer to your Linux provider for details if these file paths and file names do not exist on your system.

1. Verify that SNMP is installed by executing the following command:

   rpm -qa | grep snmp

   If SNMP is not installed, the previous command does not return a components list. Refer to your Linux provider for information on installing SNMP.

2. Verify if the HP Server Management Drivers and Agents from the ProLiant Support Pack for Linux is installed by executing the following command:

   rpm -qa | grep hpasm

   If the drivers and agents are is not installed, the previous command does not return a components list. If they are installed, verify that the HP Server Management Driver and agent daemon are running by executing the following command:

   /etc/init.d/hpasm status

3. If the the HP Server Management Drivers and Agents daemons are running, stop them using the following command:

   /etc/init.d/hpasm stop

   Note: If the HP Server Management Drivers and Agents daemon is not installed, omit this step and step G.

4. Stop the SNMP daemon:

   /etc/init.d/snmpd stop

5. Edit the snmpd.conf file using any text editor.

   For Red Hat Linux, run the following command for opening this file in the vi editor:

   vi /etc/snmp/snmpd.conf

   For SUSE Linux Enterprise Server 9 Service Pack 3, run the following command for opening this file in the vi editor:

   vi /etc/snmpd.conf

   For SUSE Linux Enterprise Server 10, run the following command for opening this file in the vi editor:

   vi /etc/snmp/snmpd.conf

   1. Remove the comment symbol (#) from the trapsink line, and add the IP address of the CMS. This system has HP Systems Insight Manager application running:

      trapsink IPaddress

      where IPaddress is the IP address of the CMS.

      Note: If snmpd is already installed, type man snmpd and read the manpage to determine how to configure the trapsink parameter.

      Note: If the trapsink entry is not available in the snmpd.conf, enter it manually using the following command:

      trapsink CMS IP

      where CMS IP is the location you want to send the traps from the managed nodes.

   2. If the following line exists in the read-only community:

      community CommunityName IPaddress

      Change it to:

      rocommunityCommunityName IPaddress

      If the line is not present, enter the CMS to the read-only community manually by adding the line:

      rocommunity CommunityName IPaddress

      where CommunityName is the SNMP community string used by the CMS and IPaddress is the IP address of the CMS.

   3. Save the changes to the file. To save and close this file using the vi editor, press the Esc key, enter :wq!, and press the Enter key.

6. Start the SNMP daemon by executing the following command:

   /etc/init.d/snmpd start

7. Start the HP Server Management Drivers and Agents daemon if it is installed on your system:

   /etc/init.d/hpasm start