Jump to content English
hp.com home
HP Systems Insight Manager  |  Administering the Software  |  Managed Systems

Administering the Software
Managed Systems

» HP Systems Insight Manager

»Table of Contents
»Index
»Product Overview
»Getting Started
»Monitoring Systems, Events, and Clusters
»Using Tasks
»Using Default Tools
»Reporting
»Administering the Software
»Users and Authorizations
»Users
»Backing Up and Restoring the Database
»Toolboxes
»System Groups
»Authorizations
Managed Systems
»Audit Log
»Clusters
»Events
»Networking and Security
»Server Certificates
»Trusted Certificates
»Identification
»Filtering
»Discovery
»Status Polling
»Data Collection
»Protocols
»WMI Mapper Proxy
»Manage System Types
»Version Control Repository
»Troubleshooting
»Printable Version
»Glossary
»Using Help
Content starts here
» Setting Up HP-UX Managed Systems
» Setting Up Linux Managed Systems
» Setting Up Windows Managed Systems
» Related Topics

Setting up managed systems involves installing the required management agents and configuring the supported protocols to communicate with the HP Systems Insight Manager software. Follow the appropriate procedure below based on the managed system's operating system. Refer to:

Setting Up HP-UX Managed Systems

Repeat these steps for each managed system.

To set up an HP-UX managed system:

  1. Install and configure SSH.

    1. Install the SSH software on the managed system:

      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

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

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

        mxagentconfig -g

      2. Enter the managed system's Hostname.

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

      4. Click [Connect].

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

    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

  3. Configure the managed system to send SNMP traps.

    1. Stop the SNMP daemon on the managed system:

      /sbin/init.d/SnmpMaster stop

    2. Edit /etc/SnmpAgent.d/snmpd.conf by removing the comment symbol and adding the IP address of the CMS:

      trap-dest address

      where address is the IP address for the CMS.

    3. Start the SNMP daemon:

      /sbin/init.d/SnmpMaster start

  4. Log into the HP Systems Insight Manager GUI. For assistance with this, refer to Getting Started - Logging In

  5. 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].

Setting Up Linux Managed Systems

Repeat these steps for each managed system.

To set up a Linux managed system:

  1. Install and configure SSH.

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

      rpm -qa | grep sshd

      If it isn't 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).

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

        mxagentconfig -g

      2. Enter the managed system's Hostname.

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

      4. Click [Connect].

  2. Configure the system to send SNMP traps.

    Note: These steps may vary slightly depending on your version of Linux. Refer to your Linux provider for details if these file paths and file names don't exist on your system.

    1. Verify that SNMP is installed:

      rpm -qa | grep snmp

      If it isn't installed, refer to your Linux provider for information on installing SNMP.

    2. Stop the HP Server Management Drivers and Agents daemon on the managed system if it is installed:

      /etc/init.d/hpasm stop

      Note: If the HP Server Management Drivers and Agents daemon isn't installed, skip this step.

    3. Stop the SNMP daemon:

      /etc/init.d/snmpd stop

    4. Edit the /etc/snmp/snmpd.conf file using any text editor. The command for opening this file in the vi editor is:

      vi /etc/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 ESC, type :wq!, and press Enter.

    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

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

  4. Log into the HP Systems Insight Manager GUI. For assistance with this, refer to Getting Started - Logging In .

  5. 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].

Setting Up Windows Managed Systems

Repeat these steps for each managed system.

To set up a Windows managed system:

  1. Install and configure SSH.

    1. Install SSH on the managed system. Using the HP Management CD or the installation files that you downloaded for the CMS installation, navigate to the openssh folder and execute OpenSSH_3.7.1p1-1.exe. Accept all the default prompts.

    2. Configure SSH on the managed system.

      1. Open a Command Prompt window and navigate to the following directory:

        cd C:\Program Files\OpenSSH\etc

        This command assumes OpenSSH was installed in the default location.

      2. Execute the following command to see which users are registered with OpenSSH:

        type passwd

        If the execute-as user for your CMS (root or administrator) is not listed, you need to add them. Otherwise, you can skip to the next step of copying the SSH generated public key.

      3. Navigate to the bin directory:

        cd C:\Program Files\OpenSSH\bin

      4. Add the user.

        • For a domain account:

          mkpasswd -d -u login domain >> C:\Program Files\OpenSSH\etc\passwd

          where login is the login name of the execute-as user and domain is the user domain.

        • For a local account:

          mkpasswd -l -u login >> C:\Program Files\OpenSSH\etc\passwd

          where login is the login name of the execute-as user.

    3. 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).

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

        mxagentconfig -g

      2. Enter the managed system's Hostname.

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

      4. Click [Connect].

  2. 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] and click [Apply] to save the changes and [OK] to close the dialog box.

  3. Log into the HP Systems Insight Manager GUI. For assistance with this, refer to Getting Started - Logging In .

  4. Using the GUI, install the ProLiant Support Pack on the managed system. Select DeployDeploy Drivers, Firmware and AgentsInitial ProLiant Support Pack Install, and refer to Version Control - Initial ProLiant Support Pack Install for more information.

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

  5. 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].

Related Topics

» Using Default Tools - Version Control