Manufacturers assign unique system object identifiers 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. Refer to Managing MIBs - Registering a MIB for information on 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 object identifier as well. You can use these object identifiers to determine which system you have and their current behavior by querying these object identifiers.
Adding New DMI Rules (from Windows CMS Only)You can create a new DMI-based rule using the command line utility (mxstm). DMI system information originates in Management Information Format (MIF) files. MIF files contain elements that have attributes and corresponding values. Refer to Getting Started - Using Command Line Interface Commands for information on accessing the mxstm manpage.
Adding New SNMP RulesYou can create a new SNMP-based rule using the command line utility (mxstm) or from the HP SIM user interface by selecting Options Manage System Types. Within the SNMP framework, manageable network systems (routers, bridges, servers, and so on) contain a software component called a management agent. The agent monitors the various subsystems of the network element and stores this information in a MIB. The agents enable the system to generate traps, which can be configured to be sent to a trap destination server that is running HP SIM.
Things You Should Know About DMI Identification
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 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 you supply to STM when you create a rule. STM can request a value from a specific target for a specific attribute.
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."
Access = Read-Only
Storage = Common
Type = String(64)
Value = "Intel Corporation"
End Attribute
Start Attribute
Name = "Product"
ID = 2
Access = Read-Only
Storage = Common
Type = String(64)
Value = "Win32 DMI Service Layer"
End Attribute
Start Attribute
Name = "Version" ID = 3
Description = "Version number of this component."
Access = Read-Only
Storage = Common
Type = String(64)
Value = "2.32" End Attribute
Start Attribute
Name = "Serial Number" ID = 4 Access = Read-Only
Storage = Common Type = String(64)
Value = "unsupported"
End Attribute ...
Related Procedures
Related Topics
|