HP Systems Insight Manager 5.3 Technical Reference Guide

• Operating system name, type, and version
• Associations, such as iLO in server
During identification, remote enclosures have a generic name (format: Encl_SerialNumber) assigned to them
until one server from every enclosure is discovered and identified. Then, the enclosures contain the name of
the enclosure assigned to the enclosure.
HP SIM collects and recognizes the product ID and serial number, and most importantly, how to handle the
server-to-iLO associations using the UUID instead of the serial number. The following processes occur
sequentially for each system that is identified by HP SIM:
1. Identify the type of system, supported protocols, and limited attributes (such as the operating system
type).
2. Filter out systems that do not meet the filter criteria (if the system is new).
3. Obtain additional data, such as license data or Web agents that might be written to the database
directly, and attributes that can be queried (such as CPU and memory data).
4. Run association algorithms based on system type identified in the first step.
For newly found automatically discovered systems, before the system is added to the database , any discovery
filters are applied. If a system does not match the discovery filter, it is not added to the database, and no
additional tasks or requests are made to that system. After the system passes the filter, it is added to the
database. At this time, the system is available to polling tasks, collections, or other operations.
NOTE: Discovery filters do not apply to manually discovered systems.
HP SIM performs initial hardware and software status polling and initial data collection on newly added
systems. See “Hardware status polling example”, “Software status polling example”, and “Data collection”
for more information about each task. The information about the systems is stored in the database.
The time to complete the discovery and identification processes varies with the network size and resources.
All necessary tasks are predefined in HP SIM. Predefined tasks cannot be removed from the system, but they
can be disabled if necessary. You can also create a new identification task and schedule it to run when you
want to update identification information from systems. See “About default system functions” for information
on default tasks.
By default, HP SIM runs the System Identification task once per day and when new systems are discovered.
Most users do not need to schedule identification tasks to run more than once per day.
Note: For automatic identification of virtual machine guests running on a virtual machine host, the IP address
of the guest is required. To acquire the IP address from WBEM Providers, VMWare tools must be installed
on the virtual machine guests.
If VMware tools are installed on the guest, the UUID, host name, and primary IP address of the virtual machine
host are collected. If VMware tools are not installed, only the UUID is collected. In this case, the virtual
machine guest is named as > VMHost_Name <_>Display Name<, where VMHost_Name is the name of the
guest host system, and Display Name is the display name of the guest in VMware Virtual Infrastructure Client.
Initial identification
After a system is newly discovered or rediscovered, HP SIM attempts to identify it. The discovery task is not
100% complete until all the systems have been identified.
Identifying systems
To identify systems between discoveries, select Options→Identify Systems. The Identify Systems page
appears. From this page, select target systems to add. See “Creating a task” for more information about
selecting targets.
120 Discovery and identification