CA SystemEDGE User Guide › Concepts › Architecture Overview › Create Monitor by Instance

Create Monitor by Instance

When you can create a self monitor on tabular MIB object you need to know the index of the monitored instance. For several important MIB tables, the agent offers a look-up feature (used in above example). This enables the following two options:

• Using sysedge.cf configuration file

  For example, although the devTable has an integer index, the lookup feature allows the monitor for a devTableEntry to be defined using a drive letter. SystemEDGE searches the devTable entries for matches of the drive letter. If devTableEntry has an index entry as 3, the monitor's object identifier is set to this index (devCapacity.3).

• Using SNMP

  SystemEDGE determines the monitor's object identifier when the table name, instance name and attribute name are provided in the monitor's MIB attributes: monObjClass, monObjInstance, monObjAttribute.

  The following example creates a monitor entry with an index of 111 that automatically derives the correct devTable index for the monitored OID using the attributes provided. The monitor is actually created when you set the row status.

  set monObjClass.111 = "devTableEntry"
  set monObjInstance.111 = "C:"
  set monObjAttribute.111 = "devCapacity"
  set monRowStatus.111       = active(1)
  

Note: You can use the snmpset command provided with the SystemEDGE agent to set SNMP values. For more information, see Command Line Utilities chapter.

The only two agent tables that are not indexed using an integer value are the mirrorMonitorTable and the mirrorAggregateTable, which use the object class, instance, and attribute values as indices to allow access for a particular managed object.