Setting Up Managed Systems

Install and configure SSH (bundle T1471AA)

Install and configure WBEM (bundle B8465BA)

(Optional) Configure SNMP to send traps to the CMS

(Optional) Configure DMI on HPUX 11.11 systems (this step is not needed if WBEM installed)

SSH and WBEM are installed on HPUX 11.23 systems by default. For 11.11 systems, check if installed with this command:

swlist B8465BA T1471AA

Install SSH on the managed system if not previously installed.

swinstall -s /directory/depot T1471AA

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 T1471AA

Install WBEM on the managed system if not previously installed.

swinstall -s /directory/depot 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 B8465BA

Configure SNMP to send traps to the CMS:

1. 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

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

   /sbin/init.d/SnmpMaster stop

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

   /usr/sbin/snmpd

Configure DMI on the managed system by adding the DNS host name of the CMS.

	NOTE: DMI only needs to be configured for HP-UX 11.11 and only if WBEM is not installed.

1. Stop the DMI daemon on the managed system:

   /sbin/init.d/Dmisp stop

2. Edit /var/dmi/dmiMachines by adding the host name of the CMS to the end of this file. Save the file.

3. Start the DMI daemon:

   /sbin/init.d/Dmisp start

On the CMS, copy the SSH-generated public key from the CMS to the managed system, and place it in the authorized keys file of the execute-as user (root or administrator).

Important: If the CMS is not an HP-UX system: On a non-English CMS, ensure that an administrator account (spelled exactly as follows, administrator) exists on the CMS, and that mxagentconfig has been run on the CMS for the created administrator account.

1. Launch the Manage SSH Keys dialog box from the CMS command prompt:

   mxagentconfig -g

2. Enter the Hostname of the managed system.

3. Enter root or administrator for the Username and the associated Password.

   Note: If the password for the mxagentconfig command contains a special character like & or $, it fails unless the password is contained by single quotation marks.

4. Click Connect.

Alternatively you can configure SSH via the command line version of mxagentconfig. On the CMS, type "mxagentconfig -?" for usage.

	NOTE: Using the -p option will make the passwd available in "ps" output, so use of the -f option (with a file only readable by root) is highly recommended when using mxagentconfig -a. If the -p using option is used, enclose the password in single quotes if the password has any special characters like & or $

Log into the HP Systems Insight Manager GUI. For assistance with this, refer to . Chapter 10 “Using the Graphical User Interface” 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 each managed system.

Note: This step can be performed once for all the managed systems you are setting up.

1. Select OptionsProtocol SettingsGlobal Protocol Settings.

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

3. Click OK.

	NOTE: An account for at least one of the WBEM user name and password combinations must exist on each managed system. If the user in the Global Protocol Settings does not exist on the managed node you can set per-system WBEM user names and passwords from the System Protocol Settings page.

Install and configure SSH.

1. Verify that SSH is installed on the managed system:

   rpm -qa | grep ssh

   If it is not installed, refer to your Linux provider for information on installing SSH.

2. On the CMS, copy the SSH generated public key from the CMS to the managed system and place it in the authorized keys file of the execute-as user (root or administrator).

   Important: On a non-English CMS, ensure that an administrator account (spelled exactly as follows, administrator) exists on the CMS, and that mxagentconfig has been run on the CMS for the created administrator account.

   1. Launch the Manage SSH Keys dialog box from the CMS command prompt:

      mxagentconfig

   2. Enter the Hostname of the managed system.

   3. Enter root or administrator for the Username and the associated Password.

      Note: If the password for the mxagentconfig command contains a special character like & or $, it fails unless the password is contained by single quotation marks.

   4. Click Connect.

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:

   rpm -qa | grep snmp

   If it is not installed, refer to your Linux provider for information on installing SNMP.

2. If you have not installed the HP Server Management Drivers and Agents from the ProLiant Support Pack for Linux, omit this step. Otherwise, stop the HP Server and Management Drivers and Agents daemons on the platform where you are installing HP Systems Insight Manager 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 F.

3. Stop the SNMP daemon:

   /etc/init.d/snmpd stop

4. 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 SLES 8 run the following command for opening this file in the vi editor: vi /usr/share/snmp/snmpd.conf

   1. Remove the comment symbol (#) from the trapsink line, and add the IP address of the CMS:

      trapsink IPaddress

      where IPaddress is the IP address of the CMS.

   2. Add the CMS to the read only community 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.

5. Start the SNMP daemon:

   /etc/init.d/snmpd start

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

   /etc/init.d/hpasm start

Install the Linux ProLiant Support Pack. To download this software and access installation information, go to http://www.hp.com/support/files.

Log into the HP Systems Insight Manager GUI. For assistance with this, refer to . Chapter 10 “Using the Graphical User Interface” 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 each managed system.

Note: This step can be performed once for all the managed systems you are setting up.

1. Select OptionsProtocol SettingsGlobal Protocol Settings.

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

3. Click OK.

	NOTE: An account for at least one of the WBEM user name and password combinations must exist on each managed system. If the user in the Global Protocol Settings does not exist on the managed node you can set per-system WBEM user names and passwords from the System Protocol Settings page.

Add the default WBEM user name and password to the Global Protocol Settings page in the HP Systems Insight Manager GUI.

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

Note: This step can be performed once for all the managed systems you are setting up.

1. Select OptionsProtocol SettingsGlobal Protocol Settings.

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

3. Click OK.

Install and configure SSH.

1. Select DeployDeploy Drivers, Firmware and AgentsInitial ProLiant Support Pack Install. The Initial ProLiant Support Pack Install page is displayed.

2. Select the target systems.

3. Click Next.

4. From the Enter Windows login credentials page:

   1. In the User name field, enter the Windows administrator user name.

   2. In the Password field, enter the administrator password for the Windows user name entered above.

   3. In the Password (Verify) field, reenter the Windows administrator password exactly as it was entered in the Password field.

   4. In the Domain field, enter the Windows domain.

5. Click Next. The Select a Windows Support Pack page is displayed.

6. Under Select a Version Control Repository, select a source repository system from which to retrieve the catalog.

   The following fields are displayed:

   • Name. This field displays the name of the system.

   • Status. This field displays the status of the system.

   • Product Name. This field displays the name of the product.

   • Trusted?. This field indicates whether the system trust relationship has been configured. To configure a trust relationship, click configure.

   Note: This section displays systems that are authorized by the current user name. If the current user is not authorized to view the systems, a message is displayed, indicating that the user does not have authorization rights on the system.

7. Under Select a Support Pack to Install, select a support pack to install. Click the

   Note: To expand the System Software Baseline to display all contents, click the

8. Select Install and initialize SSH (Secure Shell) if you want to install OpenSSH on the target systems. This option is disabled by default.

9. Optional. Select Force downgrade if necessary if you are installing a ProLiant Support Pack that is older than the version currently installed. This option is disabled by default.

10. By default, Reboot systems if necessary after successful install is selected. You can deselect this option if you do not want to reboot after the installation. However, the system must be rebooted for the new ProLiant Support Pack to be available.

11. Click Next. The Configure Support Pack page is displayed.

    • If you selected a ProLiant Support Pack 7.10 or earlier, Configure a Support Pack is displayed.

      To configure the support pack:

      1. Click Configure Support Pack to set up the HP Version Control Agent in the selected Support Pack. The Version Control Agent Setup page is displayed.

         Note: If the Version Control Agent has already been configured, you can skip this step.

      2. In the Computer Name field, enter the name of the system where the Version Control Repository Manager is installed.

      3. In the Login Account field, enter the login name used to connect to the Version Control Repository Manager on the system specified.

      4. In the Login Password field, enter the password associated with the login name specified.

      5. Click Save to save your settings. Click Cancel to discard your settings and close the Version Control Agent Setup page.

      6. Click Next.

    • If you selected a ProLiant Support Pack 7.20 or later, the following options are displayed.

      • Click Configure System Management Homepage to setup the Support Pack to establish a trust relationship with System Management Homepage when it is installed on target systems.

        Note: If the Support Pack has already been configured, you can skip this step.

        Note: After the trust relationship is established, click Last Update to update the status to trusted.

        To configure the System Management Homepage:

        1. In the Computer Name field, enter the name of the system on which the HP Version Control Repository Manager is installed.

        2. In the Administrator Password field, enter the password associated with the system you entered.

        3. Click System Management Homepage Setup. In the Password field, enter the administrator password.

        4. Click HP Systems Insight Manager Trust on the left. Set up the trust information as necessary.

        5. Click Save. A message box is displayed, indicating whether the updates were saved.

        6. Click Close.

        7. Click Next.

    • Click Configure Version Control Agent to set up the HP Version Control Agent in the selected Support Pack.

      Note: If the Version Control Agent has already been configured, you can skip this step.

      To configure the Version Control Agent:

      1. In the Computer Name field, enter the name of the system where the Version Control Repository Manager is installed.

      2. In the Login Account field, enter the login name used to connect to the Version Control Repository Manager on the system specified.

      3. In the Login Password field, enter the password associated with the login name specified.

      4. Click Save to save your settings. Click Cancel to discard your settings and close the Version Control Agent Setup page.

      5. Click Next.

12. Back in HP Systems Insight Manager, click Next to start the ProLiant Support Pack download

Configure the managed system to send SNMP traps.

1. Select StartProgramsAdministrative ToolsServices.

   On Windows 2003 and Windows XP, the Programs submenu is All Programs.

2. Scroll down the list, and right-click SNMP Service.

3. Select Properties from the pop-up menu.

4. On the Security tab, either click Add to add a new community string or click Edit to modify an existing one.

5. Enter the information for the CMS, and click Apply to save the changes.

6. On the Traps tab, enter a Community Name, and click Add to List.

7. Click Add to add the Trap Destination.

8. Enter the IP address of the CMS, and click Add.

9. Click Apply to save the changes, and click OK to close the dialog box.

Log into the HP Systems Insight Manager GUI. For assistance with this, refer to . Chapter 10 “Using the Graphical User Interface” 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 each managed system.

Note: This step can be performed once for all the managed systems you are setting up.

1. Select OptionsProtocol SettingsGlobal Protocol Settings.

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

3. Click OK.

	NOTE: An account for at least one of the WBEM user name and password combinations must exist on each managed system. If the user in the Global Protocol Settings does not exist on the managed node you can set per-system WBEM user names and passwords from the System Protocol Settings page.

Using the GUI, install the ProLiant Support Pack on the managed system. Select DeployDeploy Drivers, Firmware and AgentsInstall Software and FirmwareInitial ProLiant Support Pack Install, and refer to the Use Default Tools section of the on-line help for more information.

Note: This step can be performed once for all the Windows managed systems you are setting up.

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 each managed system.

Note: This step can be performed once for all the managed systems you are setting up.

1. Select OptionsProtocol SettingsGlobal Protocol Settings.

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

   Note: The user name must include the domain. For example: domain\user

3. Click OK.