HP Systems Insight Manager 5.2 Update 2 Technical Reference Guide

Deleting STM rules
1. Select Options→Manage System Types. The Manage System Types page appears.
2. Select the rule to delete.
3. Click Delete. A confirmation box is displayed.
4. Click OK to delete the rule, or click Cancel to cancel the deletion process.
Related procedures
• Creating STM rules
• Editing STM rules
Related topics
• Managing system types
• About System Type Manager
• Navigating the Manage System Types page
Additional information for creating STM rules
Manufacturers assign unique system Object Identifiers (OIDs) to their SNMP-instrumented products. In addition,
systems supply information about themselves using variables described in files called Management Information
Bases (MIBs). These values are enumerated using an industry-standard structure. MIBs are provided by
vendors for their systems and must be registered with HP Systems Insight Manager (HP SIM) to be accessible
and usable from System Type Manager (STM). HP preregisters all HP MIBs and many third-party MIBs. You
can register the remaining MIBs using the MIB compiler, if you have the related systems on your network.
See “Registering a MIB” for information about registering MIBs. If you examine a MIB, you will find modules,
or groups of variables. Some variables have multiple values. Each of these values has an OID as well. You
can use these OIDs to determine which system you have and its current behavior by querying these OIDs.
Things you should know about DMI identification
Desktop Management Interface (DMI) identification is based on how a system responds to a DMI request.
Systems supply information about themselves as defined in files called MIFs. MIFs are vendor-specific. Simply
having a Management Information Format (MIF) file on a target system does not guarantee DMI identification.
MIFs cannot be registered the way MIBs are registered in HP SIM. If you examine a MIF (for example, the
generic Win32sl.MIF), you will find groups of attributes. The values returned in response to requests for
MIF attributes can be used to determine which system you have and its current behavior.
For example, the following extract is part of the Win32sl.MIF. Notice the group named Component ID ,
followed by several attributes that identify one aspect of a DMI system (such as Manufacturer, Product,
Version, and Serial Number). Other MIFs have different groups and specify other aspects of a system. The
information in the MIFs is the information supplied to STM when you create a rule. STM can request a value
from a specific target for a specific attribute.
NOTE: DMI identification is only supported on Windows and HP-UX-based Central Management Server
(CMS) installations. In addition, only like operating systems can be identified. For example, a Windows-based
CMS can identify a Windows-based DMI, while HP-UX-based Central Management Server can only identify
HP-UX-based DMI systems.
Start Group
Name = "ComponentID"
ID = 1 Class = "DMTF|ComponentID|001"
Description = "This group defines the attributes common to
all components. This group is required."
Start Attribute
Name = "Manufacturer"
ID = 1 Description = "Manufacturer of this system."
132 Discovery and identification