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

Administering the Software
Discovery

» 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
»Configuring Automatic Discovery
»Managing Discovery Templates
»Adding a System Manually
»Managing Hosts Files
»Hosts File Extensions
»IP Ranges
»System Types
»Status Polling
»Data Collection
»Protocols
»WMI Mapper Proxy
»Manage System Types
»Version Control Repository
»Troubleshooting
»Printable Version
»Glossary
»Using Help
Content starts here
» Introduction
» Automatic Discovery
» First Discovery
» Subsequent Discoveries
» Manual Discovery
» Related Procedures
» Related Topics

Introduction

Any type of Discovery can only be performed if you have full configuration rights.

There are two types of Discovery:

  • Automatic Discovery. The process that HP Systems Insight Manager uses to find and identify the systems on your network and populate the database with that information. A system must first be discovered to collect data and track system status.

  • Manual Discovery. The process that enables you to bypass a full automatic discovery and add single and multiple systems to the database, create or import the HP Systems Insight Manager database Hosts file, and create or import a generic Hosts file.

Automatic Discovery

A system must first be discovered to collect data and track system status. The Auto-Discover Systems when event received feature is disabled by default and can be enabled by selecting Auto-Discover Systems when event received in the Discovery configuration section on the Automatic Discovery - General Settings page. Auto-Discover Systems when event received does not support IPX based SNMP Traps.

To access the Automatic Discovery - General Settings page, select OptionsDiscoveryAutomatic Discovery, or click Automatic Discovery in the DO THIS NOW to finish the install section of the introductory page.

HP Systems Insight Manager performs Automatic Discovery using the IP and IPX (Windows only) protocols.

You must access the Automatic Discovery - General Settings page at least once after an install and click [OK] to acknowledge the default settings. Otherwise, Automatic Discovery will not run.

HP Systems Insight Manager discovers systems running the Internet Protocol (IP) when it pings systems in a listed range of addresses. It defaults to the local subnet, a range that corresponds to the IP addresses assigned to the system where HP Systems Insight Manager is running. You can change the address list to indicate other systems or segments of the network you want HP Systems Insight Manager to discover.

Web Agents are not discovered unless HTTP is enabled on the Global Protocol Settings page in the HTTP settings (default) section. To enable HTTP, refer to Protocols - Setting Global Protocols for information. To ensure that clusters are discovered in Auto-Discovery, IP range pinging must be selected in the Discovery configuration section and the cluster IP address and all node addresses must be listed in the Ping inclusion ranges section.

HP Systems Insight Manager uses a globally unique system identifier to help identify HP systems with multiple IP addresses.

HP Systems Insight Manager discovers systems running the IPX protocol by listening for SAP broadcasts generated by IPX systems. Novell NetWare 3.x servers automatically make SAP broadcasts. Novell NetWare 4.x or later servers can be configured to make SAP broadcasts.

IPX is only supported on a Windows based central management server (CMS) system.

The following conditions are unique with the IPX protocol:

  • IPX Discovery only discovers one NIC per machine.

  • IPX systems only discover NetWare servers.

Event Based Auto-Discovery is disabled by default. You can enable this feature by selecting Auto-Discover Systems when events received. If selected, Event Based Auto-Discovery adds any systems that send SNMP traps, WBEM indications, or other events to HP Systems Insight Manager that do not have a matching IP address in the database. The Exclusion Ranges option allows the entry of any IP addresses that you want excluded from Event Based Auto-Discovery. If SNMP is disabled on the Global Protocols Settings page under OptionsProtocol SettingsGlobal Protocol Settings, then SNMP traps are ignored. If WBEM is disabled, then WBEM indications are also ignored.

SNMP Authentication failure traps do not trigger an Automatic Discovery. However, any other trap will do so.

Auto-Discovery is enabled by default, but if the feature has been disabled and you want to enable it, you can enable Discovery from the Automatic Discovery - General Settings page. If you disable Automatic Discovery, no new Automatic Discovery is performed until you enable it by visiting the Automatic Discovery - General Settings page and making your selections. You can also perform a Manual Discovery any time that you choose.

Discovery Templates are files that can be used by Automatic Discovery in lieu of typing the addresses directly in to the Ping Inclusion Ranges or Exclusion Ranges fields. They are designed to be used as a quick way to change the scope of Automatic Discovery.

For example, you can configure a Discovery Template with a broad range of addresses that are discovered infrequently when you want to issue a broad range ping. When needed, the template can be used as input in the Ping inclusion ranges section of the Automatic Discovery - General Settings page. The templates also enable you to quickly change the scope of Discovery without having to cut and paste addresses or manually re-type the ranges.

After creating a Discovery Template, to reference it in Automatic Discovery use @template_name in the Ping inclusion ranges or Exclusion Ranges fields. Refer to Discovery - IP Ranges.

A single Discovery Template cannot include both Included and Excluded ranges. You must create a separate template for use in each field of Automatic Discovery. Template files cannot be nested, that is, a template file cannot contain another template file name through the @template_name reference.

The format of a Discovery Template is the same as that used in the Ping Inclusion Ranges and Exclusion Ranges fields when configuring Automatic Discovery.

Access Discovery Templates, by clicking templates under the IP Address Ranges section on the Automatic Discovery - General Settings page. Refer to Discovery - Managing Discovery Templates for information on creating a Discovery Template file.

Use an existing Hosts file, a file created from the HP Systems Insight Manager database, or an HP Systems Insight Manager exported Hosts file as the basis for adding systems. Typically, the file is a listing of the names of systems, their IP addresses, and any alias names that are used on the system.

Importing the Hosts file bypasses the need for an immediate Discovery. For example, in the case of a catastrophic system failure, you could import a backup Hosts file as the basis for reconfiguring your management environment and automatically repopulate a database. Adding the systems using the Hosts file utility does not replace systems in the database. For example, if a system listed in the Hosts file has the same IP address as an existing system, the duplicate is ignored. Any systems that previously existed in the database are not modified.

You can import Hosts files from the following sources:

  • The HP Systems Insight Manager database, which imports the system data, creates a Hosts file, and sorts the data types according to your selection

  • Another system that has an existing Hosts file

To access the Manual Discovery - Hosts File page click host files in the IP Address Ranges section on the Automatic Discovery - General Settings page.

First Discovery

You can start a Discovery in several ways:

  • Wait for the scheduled default Discovery that runs 24 hours after installation. The scheduled next run is based on the server startup time, which might be different than the client time.

  • Execute Discovery now from the Automatic Discovery - General Settings page by clicking [Save and Run]. The discovery process starts immediately. The discovery progress is updated as the systems are discovered, until the discovery process is complete.

  • Allow sufficient time for a complete Discovery and Identification to finish. Times vary, depending on your network, bandwidth, and discovery settings. In most cases, the discovery process finds all systems by pinging the network.

Subsequent Discoveries

You can run Discovery at any time from the Automatic Discovery - General Settings page. For subsequent discoveries, you can specify which subnets or systems to interrogate, which protocols to use, and which schedule to follow. Select IPX as a discovery protocol if your network includes Novell systems.

For the most complete Discovery and Identification, always select SNMP, DMI, WBEM, and HTTP as the protocols on the OptionsProtocol SettingsGlobal Protocol Settings page. Configure default community strings and WBEM passwords on the Global Protocol Settings page. Refer to Protocols - Global Protocols for additional information.

Status Indicators indicate when Discovery is running, the Last Run displays running and the percent complete. In addition, the number of pings attempted and systems processed are displayed. Systems processed means the systems either did not respond to a ping or have completed identification. It does not mean that the system has been added to the database.

Manual Discovery

Manual Discovery enables you to bypass a full Discovery to perform the following tasks:

  • Add a single system to the HP Systems Insight Manager database.

  • Add multiple systems through Hosts files.

  • Create and import an HP Systems Insight Manager Hosts file.

  • Import a Hosts file that was created or exported from Insight Manager (WIN32). The Hosts file automates the process of adding systems or restoring system information.

  • Create or import a generic Hosts files to automate the process of adding systems or restoring system information.

  • Set up systems before they are physically on the network.

    The system is added to the database with the IP address as the system name. After the system is up on the network and identification runs, the system name is updated with the system’s name instead of IP address.

You can access the Manual Discovery - Add System page by:

  • Clicking OptionsDiscoveryManual Discovery.

  • Clicking Manual Discovery in the DO THIS NOW to finish the install section of the introductory page

  • Clicking Add System at the top of the Manual Discovery - Hosts Files page

    or

  • Clicking Add System from the Automatic Discovery - General Settings page

To add a single system to the HP Systems Insight Manager database:

  • Know the IP address or hostname of the system. If you know at least one of these, HP Systems Insight Manager can find the other by validating the information with the Domain Name Service (DNS) for the network.

  • To add a cluster and its nodes, enter each IP address separately.

  • Decide if you want to set the system type.

  • Specify the SNMP settings for this system to be unique or match the global discovery settings. The current system default is displayed. If you change it, you cannot automatically reset the default; you can specify the default that you find in global SNMP settings. You can modify the following settings:

timeoutThe amount of time HP Systems Insight Manager waits for a response when it sends a request to the system. The default timeout value is displayed. If a response is not received within the time interval, HP Systems Insight Manager might determine that the system cannot be tracked. Decreasing this value can result in increased network traffic because the number of attempts is accelerated. Use caution when changing this value.
retriesThe number of times an attempt is made to communicate with a system before attempts stop.
community stringsAuthentication that allows or prohibits communication between the system and the console. The community string of the console must match the community string of the system. Use the read-only community string to read variables. Use the write community string to modify variables. Although only one community is valid for a communication attempt, a system can belong to multiple communities. When you add communities, separate them with a comma (,). After HP Systems Insight Manager communicates with a community string, no other community strings are contacted.

If an IP address is used, it must be properly resolved to a name in order for the name to be displayed in the UI.

Refer to Discovery - Adding a System Manually for the steps to add a single system to the database.

Related Procedures

» Discovery - Configuring Automatic Discovery
» Discovery - Adding a System Manually
» Discovery - Managing Hosts Files
» Discovery - Managing Discovery Templates

Related Topics

» Administering the Software - Identification
» Administering the Software - Filtering
» Administering the Software - Data Collection
» Administering the Software - Status Polling
» Administering the Software - Protocols
» Administering the Software - Discovery