OverviewSetting up managed systems involves installing the required management agents and configuring the supported protocols to communicate with the HP Systems Insight Manager software. The following steps assume that HP Systems Insight Manager is installed on the central management server (CMS) and the First Time Wizard has been completed. To setup managed systems, there are two overall steps: Installing required and optional managed system software: Configuring the managed system software:
Installing Required and Optional managed system softwareManaged systems must have the VCA installed prior to using the Configure or Repair Agents feature to configure them. Installing the ProLiant Support Pack on Windows systems for the first timeFor Windows systems, install the latest ProLiant Support Pack with the preconfigured components to all managed systems using the HP Systems Insight Manager feature Initial ProLiant Support Pack Install. When you are installing the ProLiant Support Pack for the first time, the Initial ProLiant Support Pack Install process enables you to install a ProLiant Support Pack to a Windows system because you do not have any HP Insight Management Agent, especially HP Version Control Agent, installed. This process also configures the systems to use the trust certificate from the HP Systems Insight Manager and the setting to use the desired HP Version Control Repository Manager. After you have run the Initial ProLiant Support Pack Install tool, then you can use the Install Software and Firmware tool to update systems. The Install Software and Firmware feature in HP Systems Insight Manager requires that the HP Version Control Repository Manager be installed on servers containing a repository. Installing the VCRM is not part of this procedure. For more information regarding installing the VCRM, refer to the HP Version Control Installation Guide at http://h18013.www1.hp.com/products/servers/management/agents/documentation.html. To install a ProLiant Support Pack: Select Deploy Deploy Drivers, Firmware and Agents Initial ProLiant Support Pack Install. The Initial ProLiant Support Pack Install page appears. Select the target systems.
Refer to HP Systems Insight Manager Technical Reference Guide - Managing with Tasks for more information.
Click [Next.]
From the Enter Windows login credentials page: In the User name field, enter the Windows administrator user name for the target system. In the Password field, enter the administrator password for the Windows user name entered above. In the Password (Verify) field, reenter the Windows administrator password exactly as it was entered in the Password field. In the Domain field, enter the Windows domain.
Note: This field can be left blank if the system is not part of a domain.
Click [Next]. The Select a Windows Support Pack page appears. Under Select a Version Control Repository, select a source repository system from which to retrieve the catalog. The following fields display:
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. Refer to Networking and Security - Trusted Certificates for more information.
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 appears, indicating that the user does not have authorization rights on the system. Under Select a Support Pack to Install, select a support pack to install. Click the icon to drill down and view the contents of the Version Control Repository that you selected.
Note: To expand the System Software Baseline to display all contents, click the icon located in the upper left corner of the Select a Support Pack to Install section. Click the icon to collapse the listings. Select Install and initialize SSH (Secure Shell) if you want to install and configure OpenSSH on the target systems. This option is disabled by default. (Optional) Select Force downgrade or re-install the same version if you are installing a ProLiant Support Pack that is older than or the same as the version currently installed. This option is disabled by default. 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. Click [Next]. The Configure Support Pack page appears. If you select a ProLiant Support Pack 7.10, [Configure a Support Pack] appears. For example:
Note: If you select a ProLiant Support Pack that is earlier than 7.10, the following example varies. To configure the 7.10 support pack: Click [Configure Support Pack] to set up the HP Version Control Agent in the selected Support Pack. The VCA Setup page appears.
Note: If the VCA has already been configured, you can omit this step. In the Computer Name field, enter the name of the system where the VCRM is installed. In the Administrator Password field, enter the password associated with the login name specified. Click [Save] to save your settings. Click [Cancel] to discard your settings and close the VCA Setup page. Click [Next]. The Download Support Pack page appears. After the support pack is downloaded, click [Schedule] to create a scheduled task for the Initial ProLiant Support Pack Install to run or click [Run Now] to run the task immediately.
If you select a ProLiant Support Pack 7.20 or later, the following options display. 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:
Refer to Networking and Security - Trusted Certificates for more information on setting up a trust relationship. the trust relationship is established, click Last Update to update the status to trusted. To configure the System Management Homepage: From the Welcome to the Configuration Wizard for the HP System Management Homepage Component page, click [Next]. The Operating Systems Groups page appears. In the Group Name field, enter the name of an operating system group that you want to assign. For example, vcadmin. In the Operating Level field, select the appropriate level for the new group from the dropdown list.
Note: The default Administrators Groups always have administrative access. Click [Add] to assign the group. The new group appears under the operating system group which it was assigned.
Note: You can add up to five entries per operating system group. Click [Next]. You can click Save to save your changes up to this point, or click Cancel to discard the changes and close the wizard.
Local and Anonymous access enables you to select the appropriate settings to include: Anonymous Access. Anonymous Access is disabled by default. Enabling Anonymous Access enables a user to access the System Management Homepage (SMH) without logging in. Select this option to allow anonymous access.
Caution: HP does not recommend the use of anonymous access. Local Access. Local Access is disabled by default. Enabling it means you can locally gain access to the System Management Homepage without being challenged for authentication. This means that any user with access to the local console is granted full access if Administrator is selected. If Anonymous is selected, any local user has access limited to unsecured pages without being challenged for a username and password. Select this option to allow local access.
Caution: HP does not recommend the use of local access unless your management server software enables it.
Click [Next]. You can click Save to save your changes up to this point, or click Cancel to discard the changes and close the wizard. The Trust Mode options enable you to select the security required by your system. There are some situations that require a higher level of security than others. Therefore, you are given the following security options: Trust by Certificate. Sets the System Management Homepage (SMH) to accept configuration changes only from HP Systems Insight Manager servers with trusted certificates. This mode requires the submitted server to provide authentication by means of certificates. This mode is the strongest method of security since it requires certificate data and verifies the digital signature before allowing access. If you do not want to enable any remote configuration changes, leave Trust by Certificate selected, and leave the list of trusted systems empty by avoiding importing any certificates. To trust by certificate: Select Trust by Certificate and click [Next]. In the Certificate Name field, click [Browse] to select the certificate file. After the certificate file is selected, the certificate data is displayed on the screen. Click [Add]. The certificate appears under Certificate Files. You can click Save to save your changes up to this point, or click Cancel to discard the changes and close the wizard. Click [Next]. The IP Binding page appears.
Trust by Name. Sets the System Management Homepage to accept certain configuration changes only from servers with the HP Systems Insight Manager names designated in the Trust By Name field. The Trust By Name option is easy to configure. For example, you might use the trust by name option if you have a secure network with two separate groups of administrators in two separate divisions. It prevents one group from installing software to the wrong system. This option verifies only the HP Systems Insight Manager server name submitted. The server name option must meet the following criteria: Each server name must be less than 64 characters The overall length of the server name list is 1,024 characters Special characters should not be included as part of the server name: ~ ' ! @ # $ % ^ & * ( ) + = \ ": ' < > ? , | Semicolons are used to separate server names
To trust by name: Select Trust by Name and click [Next]. In the Trusted Server Name field, enter the server name to be trusted. Click [Add]. The trusted system name appears under the Trusted Servers list. You can click Save to save your changes up to this point, or click Cancel to discard the changes and close the wizard. Click [Next]. The IP Binding page appears.
Trust All. Sets the System Management Homepage to accept certain configuration changes from any system. To trust all servers: Select Trust All. You can click Save to save your changes up to this point, or click Cancel to discard the changes and close the wizard. Click [Next]. The IP Binding page appears.
IP Binding specifies from which IP addresses the System Management Homepage (SMH) accepts requests from and provides control over which nets and subnets requests are processed. Administrators can configure the System Management Homepage to only bind to addresses specified in the IP Binding page. A maximum of five subnet IP addresses and netmasks can be defined. An IP address on the server is bound if it matches one of the entered IP Binding addresses after the mask is applied. To configure IP Binding: Select IP Binding. The IP Binding page appears. Enter the IP address. Enter the Netmask. Click [Add]. The IP binding configuration is saved and appears under the IP Binding List. Click [Next]. The IP Restricted Login page appears.
The IP Restricted Login enables the System Management Homepage (SMH) to restrict log-in access based on the IP address of a system. You can set address restriction at installation time or by it can be set by administrators from the IP Restricted Login page
If an IP address is excluded, it is excluded even if it is also listed in the included box. If there are IP addresses in the inclusion list, then only those IP addresses are allowed log-in access with the exception of localhost. If no IP addresses are in the inclusion list, then log-in access is allowed to any IP addresses not in the exclusion list.
To include or exclude IP addresses: In the From field, enter the IP addresses to include or exclude. You can enter an IP address range to be included or excluded by entering a beginning IP address in the From field and an ending IP address in the To field. From the Type field, select Include or Exclude. Click [Add] to add the IP address or IP address range to the Inclusion List or Exclusion List below. Click [Save]. The HP System Management Homepage Login page for the System Management Homepage system appears. For more information about System Management Homepage, refer to the System Management Homepage Online Help at http://h18013.www1.hp.com/products/servers/management/agents/documentation.html.
Click [Configure VCA] to set up the HP Version Control Agent in the selected Support Pack.
Note: If the VCA has already been configured, you can skip this step. To configure the VCA: In the Computer Name field, enter the name of the system where the VCRM is installed. In the Login Account field, enter the login name used to connect to the VCRM on the system specified. In the Login Password field, enter the password associated with the login name specified. Click [Save] to save your settings. Click [Cancel] to discard your settings and close the VCA Setup page. Click [Next].
Back in HP Systems Insight Manager, click [Next] to start the ProLiant Support Pack download. The Download Support Pack page appears. After the support pack is downloaded, click [Schedule] to create a scheduled task for the Initial ProLiant Support Pack Install to run or click [Run Now] to run the task immediately.
Installing the ProLiant or Integrity Support Pack on a Linux system for the first timeFor Linux systems, use the Linux Deployment Utility to install the latest support pack with the preconfigured components to the local system. For more information regarding installing a support pack using the Linux Deployment Utility, refer to http://www.hp.com/servers/psp.
Installing the required software on an HP-UX systemUnderstanding the basic managed system software for HP-UX. For HPUX, the following software, shown with minimum recommended versions, is required for essential HP Systems Insight Manager functionality to operate. This software is installed by default as part of the latest HP-UX 11i v2 operating environments, but may need to be installed or updated on HP-UX 11i v1 or older HP-UX 11i v2 systems. T1471AA A.04.00 HP-UX Secure Shell B8465BA A.02.00.05 HP WBEM Services for HP-UX
This WBEM Services bundle contains basic system instrumentation displayed in the HP SIM Property Pages as well as supporting collection and reporting by HP SIM Inventory functionality. To maximize the value of SIM for properties, inventory and events, the following should also be installed, available for HP-UX 11i v2 servers: LVMProvider R11.23 CIM/WBEM Provider for LVM WBEMP-LAN-00 B.11.23 LAN Provider for Ethernet/LAN Interfaces SysFaultMgmt A.02.00 HP-UX System Fault Management
The following, System Management Homepage for HP-UX, does not currently support the same level of functionality found in Windows and Linux servers. It is currently only required to support the latest version of Partition Manager. SysMgmtWeb A.2.2 HP-UX Web Based System Management User Interfaces
Ensuring the managed system software is installed To see if the minimum required software is installed, login to the remote system and run the following command:
$ swlist –l bundle T1471AA B8465BA OpenSSL
To see if the optional providers and System Management Homepage are installed, run commands such as:
$ swlist –l bundle LVMProvider WBEMP-LAN-00 SysFaultMgmt
Acquiring and Installing managed system software The SecureShell, WBEM and OpenSSL bundles are included on the HP-UX Operating Environment and Application Release media, as well as part of the HP Systems Insight Manager HP-UX depot downloaded from http://www.hp.com/go/softwaredepot. For the WBEM providers, several are available from the latest HP-UX Operating Environment and Application Release media. Additionally, the LVMprovider and SysFaultMgmt are available from http://www.hp.com/go/softwaredepot by searching for the keyword provider. Make sure that the OnlineDiag bundle is installed on your computer. To verify that the OnlineDiag bundle is installed, enter the following command:
swlist | grep OnlineDiag
The OnlineDiag bundle is installed on the operating environments, so if you have a recent version of the operating environment, this should already be installed. However, if it is not installed, the OnlineDiagnostic bundle is available from http://www.hp.com/go/softwaredepot by searching for the keyword B6191AAE. After the depots containing the providers have been acquired, they can be installed from the managed system using commands such as:
$ swinstall –s <depot_location> OpenSSL
Note:B8465BA deponds on OpenSSL, so this must be installed first.
$ swinstall –s <depot_location> T1477AA
$ swinstall –s <depot_location> B8465BA
$ swinstall –s <depot_location> LVMProvider WBEMP-LAN-00 SysFaultMgmt
Configuring Serviceguard provider: A WBEM provider for Serviceguard can be optionally installed on HP Serviceguard clusters. This provider helps HP Systems Insight Manager create associations in its system lists between clusters and their members, as well as showing HP Serviceguard cluster status. When using the First Time Wizard from HP Systems Insight Manager, the root user or a non-root user was specified for the WBEM default user. Alternatively a user may have been specifically set for this system. To access the Serviceguard provider from HP Systems Insight Manager if a non-root user is the WBEM user, you must configure Serviceguard to allow that non-root user Serviceguard administrative access. Refer to HP Integrity Essentials Overview - HP Serviceguard Manager Overview for more information about ServiceGuard.
Configuring the Managed System SoftwareThe HP Systems Insight Manager Configure or Repair Agents feature is a quick and easy way to configure managed systems, however it is possible to manually configure Linux and HP-UX systems. Run the Configure or Repair Agents feature from the CMSTo run Configure or Repair Agents remotely against multiple systems simultaneously, you must have authorizations to run the Configure or Repair Agents tool. You must have full CMS configuration privileges to modify the HP Systems Insight Manager community strings in the node security file. In addition, you must have administrator privileges for Windows systems or root privileges for Linux and HP-UX on the target systems to configure or repair the agent settings.
Note: It is recommended that you use like operating system to configure a managed system. For example, use a Linux-based CMS to run Configure or Repair Agents against Linux managed systems and HP-UX CMS to run Configure or Repair Agents against HP-UX managed systems. Windows systems can only be configured from a Windows CMS. To configure agents remotely: Select Configure Configure or Repair Agents from the menu.
Note: The Verify Target Systems page appears if the targets are selected before selecting a tool. To add targets, select a group from the dropdown list. The contents of the selected group appear and can be selected as targets or to select the collection itself, select Select Name of Collection itself. Click [Apply].The targets appear in the Verify Target Systems section.
Note: If the targets selected are not compatible with the tool, the Tool Launch OK? column provides a brief explanation for the problem. To remove a target, select the target and then click [Remove Targets]. Select one of the following options: Click [Add Targets] to add more targets to the Target System List. To remove a target, select the target and then click [Run Targets].
Click [Next] to specify tool parameters and to schedule the task.
From the Enter login credentials page: In the User name field, enter the system administrator user name for the target systems. In the Password field, enter the system administrator password for the user name previously entered. In the Password (Verify) field, reenter the system administrator password exactly as it was entered in the Password field. For Windows managed systems only, in the Domain field, enter the Windows domain.
Note: The credentials used in this step must work for all target systems that have been selected. HP recommends using domain administrator or root credentials.
Click [Next]. Click [Prev] to return to the previous page. The Configure or Repair Settings page appears. The following options are available:
Configure SNMP. Select this option to configure SNMP settings. If this option is selected, the following steps must be considered: Select Set read community string.
Note: If only HP-UX systems with default SNMP installation are being configured at this time, you may deselect this option. HP-UX allows read by default (get-community-name is set to public by default on HP-UX systems).
Note: If this option is selected, the Read Only community string is added to the target systems. If the target system is SuSE Linux or Microsoft Windows 2003, the managed nodes do not always allows SNMP communication between themselves and a remote host. This setting is modified to allow the instance of the HP Systems Insight Manager system to communicate SNMP with these target systems.
Note: Repairing the SNMP settings adds a Read Write community string to the target system only if one does not currently exist. This community string is unique for each system, is composed of over thirty characters to include letters and numbers, and is only visible to the user with administrator privileges for that system. This Read Write community string is required by the Web Agent to perform certain threshold setting capabilities. This community string is only used locally on the target system and is not used by HP Systems Insight Manager over the network. Select Set traps to refer to this instance of HP Systems Insight Manager in the target systems' SNMP Trap Destination List. This allows the target systems to send SNMP traps to this instance of HP Systems Insight Manager.
Trust relationship: Set to "Trust by Certificate". Select this option to require systems to use the Trust by Certificate trust relationship with the System Management Homepage. For System Management Homepage on the target systems, this option sets the trust mode to Trust by Certificate and copies the HP Systems Insight Manager system certificate to the target system's trusted certificate directory. This enables HP Systems Insight Manager users to connect to the System Management Homepage using the certificate for authentication.
Note: If you experience problems later setting the trust status to Linux, refer to the HP Systems Insight Manager Online Help Troubleshooting help file for assistance.
Set administrator password for Insight Management Agents version 7.1 or earlier. Select this option to repair the administrator password on all Insight Management Agents installed on the target systems as applicable for Windows and Linux systems.
Note: Deselect this option if you have Insight Management Agents 7.2 or later installed.
Note: If the remote system is running HP-UX, this option is not executed on the remote system since it is not applicable on HP-UX systems. If only HP-UX target systems are being configured at this time, you can deselect this option. If this option is selected, the following steps must be configured: In the Password field, enter the new administrator password. In the Confirm Password field, re-enter the new administrator password exactly as you entered it previously.
Configure secure shell (SSH) access.
If this option is selected, you must select one of the following options:
Host based authentication for SSH - For more information regarding SSH, refer to Secure Shell (SSH) in HP Systems Insight Manager white paper at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html.
Each user has to be authenticated on the managed system
Note: If the selected systems include Linux or HP-UX systems, and options for Configure SNMP settings, Trust relationships and administrator password for HP Insight Management Agent 7.1 or earlier have been selected, then SSH authentication should be selected now unless already configured earlier.
Note: SSH can be configured only if the OpenSSH service is running on the managed systems. OpenSSH can be installed on Windows systems, by
running the Install Open SSH tool under Deploy Deploy Drivers, Firmware and Agents Install Open SSH.
Create subscriptions for WBEM events.
Note: This option is only applicable to Linux and HP-UX systems. If this option is selected, the target system is configured to send WBEM indications or events to HP Systems Insight Manager.
Note: Subscriptions for WBEM events can be created only if WBEM event providers are installed and running on the managed systems.
Click [Run Now] or you can click [Schedule] to run this task at a later time. Click [Prev] to return to the previous page. The Task Results page appears.
Note: The Configure or Repair Agents tool can be used to update multiple target systems, each of which might potentially have different results. The information is used to display the information on the stdout tab. The results indicate whether the repair attempt was successful.
Note: Repair of SNMP settings, Trust relationships and administrator password for Insight Management Agents 7.1 or earlier on Linux systems is executed by a separate task, which can be viewed in the tasks log menu selection. Repair of SNMP settings, Trust relationships on HP-UX systems is executed by a separate task, which can be viewed in the tasks log menu selection. If Linux and HP-UX systems are selected, there are two Task IDs, one for Linux and one for HP-UX systems. The Task Results page displays the following information:
Status. This field displays the details for each target system within a task instance.
Exit Code. This field represents the success or failure of an executable program. If the return value is zero or positive, the executable ran successfully. If a negative value is returned, the executable failed.
Target Name. This field displays the name/IP address of the target.
The stdout Tab. This tab displays the output text information.
The stderr Tab. This tab displays information if the executable experienced an error.
Files Copied Tab. This tab displays what files are in the process of being copied or have been copied to the target system.
[View Printable Report]. Reports can be printed for the currently selected target system or for all target systems associated with the task instance.
To print a report: Click [View Printable Report]. An Options Message box appears, asking if you want to generate a report containing only the currently selected target system or all systems associated with the task instance. Select which report to print. Click [OK] to print the report, or click [Cancel] to return to the View Task Results page.
If Management HTTP Server is installed on target systems, the login credentials are updated in the Management HTTP Server password file.
Setting Up Managed Systems ManuallyUsing HP Systems Insight Manager's Configure or Repair Agents is the easiest way to configure managed systems. However, the steps to manually configure Linux and HP-UX managed systems are included in the event manual configuration is necessary. The following sections detail how to configure managed systems on: Setting Up HP-UX Managed Systems ManuallyYou can use the HP Systems Insight Manager Configure or Repair Agents tool to configure HP-UX managed systems simultaneously or you can configure each managed system manually. Use these general steps to assist you with configuring an HP-UX system manually: Install SSH (bundle T1471AA) if not previously installed. Install WBEM (bundle B8465BA) if not previously installed. (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). On the CMS: Configure the SSH Keys for this system. Configure the default WBEM user name and password if not previously done. Subscribe to WBEM Indications/Events
On each managed system: 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: Add the full hostname or IP address of the CMS as a trapdest in the following 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
Configure DMI on the managed system by adding the DNS host name of the CMS. Stop the DMI daemon on the managed system:
/sbin/init.d/Dmisp stop
Edit /var/dmi/dmiMachines by adding the host name of the CMS to the end of this file. Save the file. 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 using the mxagentconfig: Use one of the following commands:
mxagentconfig -a -n <hostname> -u root -f <file_with_root_password>
or
mxagentconfig -a -n <hostname> -u root -p <root_password>
Note: Using the -p option exposes the passwd through ps output, so use of the -f option (with a file only readable by root, and containing only the managed system root password) is highly recommended when using mxagentconfig -a. If the -p option is used, enclose the password in single quotes if the password has any special characters, such as & or $. For more information and options, see the mxagentconfig manpage with man mxagentconfig.
Log into the HP Systems Insight Manager GUI. For assistance with this, refer to Getting Started - Signing In.
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. Select Options Protocol Settings Global Protocol Settings. 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. Click [OK].
To subscribe to WBEM Indications/Events:
Note: For more information about OnlineDiagnostic, go to WBEM Subscriptions in HP Systems Insight Manager white paper at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html. From the managed system, make sure WBEM is already installed.
Note: Subscribing to WBEM Indications/Events on managed systems is optional. Verify that SysFaultMgmt provider is installed:
cimprovider –ls
You should see EMSWrapperProviderModule
From the CMS: Verifty that WBEM has root access:
mxnodesecurity –l –p wbem –n <systemname>
To subscribe to WBEM Events, you must have root access. If the Global Protocol Setting does not match the managed system or does not contain root access, the subscription for WBEM Indications fails. You can verify what access WBEM has by running the following command line:
mxnodesecurity –l –p wbem –n <systemname>
If the managed system does not have root access, you can change the individual system.
Note: You can use the Configure or Repair Agents tool to perform this step without permanently recording a root passwd. To change the individual system:
Tools System Information System Page. From the System Page, select Tools & Settings System Protocol Settings.
From the CMS, run the WBEM Indications/Events command line:
mxwbemsub -l -n <systemname>
Refer to Events - Subscribing to WBEM Indications for more information.
Setting Up Linux Managed Systems ManuallyYou can use the HP Systems Insight Manager Configure or Repair Agents tool to configure Linux managed systems simultaneously or you can configure each managed system manually. To manually configure Linux managed systems, perform the following on each managed system: Install and configure SSH. 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. 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.
Launch the Manage SSH Keys dialog box from the CMS command prompt:
mxagentconfig -a -n hostname -u username -p Password
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. Verify that SNMP is installed:
rpm -qa | grep snmp
If it is not installed, refer to your Linux provider for information on installing SNMP. 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. Stop the SNMP daemon:
/etc/init.d/snmpd stop
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
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. 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. 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.
Start the SNMP daemon:
/etc/init.d/snmpd start
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
Getting Started - Signing In.
.
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. Select Options Protocol Settings Global Protocol Settings. 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. Click [OK].
ExamplesSetting up Windows managed systemsThe following example describes how to setup remote Windows systems from a Windows CMS. To configure remote Windows systems from a Windows CMS: Setting up remote Linux systems from a Linux CMSThe following example describes how to setup remote Linux systems from a Linux CMS. To configure remote Linux systems from a Linux CMS: Setting up remote HP-UX systems from an HP-UX CMSThe following example describes how to set up remote HP-UX systems from an HP-UX CMS. To configure remote HP-UX systems from an HP-UX CMS:
Related Topics
|