Systems Management Empire MIB › Systems Management Empire MIB Overview

Systems Management Empire MIB Overview

The Systems Management Empire MIB modules define a collection of objects for managing host systems. The MIB is organized into groups and tables for monitoring the following types of information:

• System information
• Mounted devices
• Kernel configuration
• Streams
• Users and groups
• Processes
• Remote command execution
• Performance
• Interprocess communications (IPC)
• Buffer statistics for network buffers
• Streams buffers
• I/O buffer cache
• Directory name lookup cache
• Logical partitions
• NFS and RPC statistics
• Windows-specific statistics
• Disk and CPU statistics

The Systems Management Empire MIB also includes monitoring and object aggregation tables.

You can monitor specific objects from the MIB groups and tables by creating self monitoring entries specifying an object OID or the object class, instance, and attribute. The self monitoring functionality lets you monitor any MIB object against a defined thresholds, maintain an object state according to the current retrieved value, and send state change traps when a threshold is breached. For more information, see the chapter "Self Monitoring."

The top-level OID of objects in the Systems Management Empire MIB is 1.3.6.1.4.1.546. Reference the MIB file to derive full OIDs.

This chapter contains the following:

• Descriptions of all Systems Management Empire MIB groups and tables
• Sample illustrations for some tables taken from the SystemEDGE agent running on a Solaris SPARC server
• Example use cases for monitoring groups and tables
• Default class values for MIB groups and tables
• Default instance values for MIB tables

The default class and instance values for each group and table are useful for defining monitoring entries. The syedge.oid file maintains defaults for these values for each attribute that you can use to define a self monitor entry without specifying the OID. This chapter defines the default class for all groups and tables and the default instance for all tables; the instance value is not required when monitoring an attribute in a MIB group. The default attribute value is the name of the MIB attribute.

Note: For more information about the reverse OID lookup feature, see the chapter "Self Monitoring."

For a complete description of the MIB objects, including individual attribute names, see the empire.asn1 file in the mib subdirectory of the agent installation. For information about platform-specific support, see the Release Notes.