HP SIM V5.1 User Guide (356920-009, January 2007)

NOTE: All traps, except the SNMP Authentication Failure trap, trigger an automatic discovery.
Discovery templates
Discovery templates are files that can be used by automatic discovery instead of typing the addresses directly
in to the Ping inclusion ranges, templates and/or hosts files or Ping exclusion ranges, templates
and/or hosts files fields. They are designed to be used as a quick way to change the scope of automatic
discovery and are used each time discovery runs. To access the discovery template section, click the
Automatic tab from the Discovery page and then click Manage templates.
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, templates and/or hosts files field of the Edit Discovery section. To access
this section, select Options→Discovery, click the Automatic tab, and click Edit. The templates also enable
you to quickly change the scope of discovery without having to cut and paste addresses or manually reenter
the ranges.
After creating a discovery template, to reference it in automatic discovery, use @template_name in the
Ping inclusion ranges, templates and/or hosts files or Exclusion ranges, templates and/or hosts
files fields. See “IP ranges” for more information.
NOTE: Because discovery now supports multiple schedules and configurations (ranges), the need for
templates is significantly reduced. HP recommends that you leverage several different discovery schedules
and configurations instead of utilizing discovery templates.
NOTE: 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, templates and/or
hosts files and Ping exclusion ranges, templates and/or hosts files fields when configuring automatic
discovery.
Access discovery templates by clicking Manage templates under the For all automatic discoveries section
on the Discovery page. See “Managing discovery templates” for information on creating a discovery
template file.
First discovery
You can start a discovery in several ways:
• Execute discovery immediately from the Discovery→Automatic page, select the discovery task, click
Edit to configure the discovery task for your environment, and then click Run Now. 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 Discovery→Automatic page. For subsequent discoveries, you
can specify which subnets or systems to interrogate and which schedule to follow.
For the most comprehensive discovery and identification, always select SNMP, DMI , WBEM, and HTTP as
the protocols on the Options→Protocol Settings→Global Protocol Settings page. Configure default
community strings and WBEM passwords on the Global Protocol Settings page. See “Global protocols”
for additional information.
Status indicators indicate when discovery is running, and the column, Last Run, displays running, the
percent complete, the number of pings attempted, and systems processed are displayed. A processed
system is one whose IP address has been identified or found to be unresponsive. A processed system is not
necessarily added to the database.
88 Discovery and identification