1.2.3 Extended functions

(1) Definition of extended MIB objects

You can implement MIBs defined by hardware vendors or standardization organizations as extended MIB objects. To do so, you must define in a file the MIB object you want to implement as an extended MIB object, according to the ASN.1 encoding rules. You must also define the action that SNMP Agent performs upon receiving an SNMP request for this MIB object. Once you make these definitions, SNMP Agent, upon receiving an SNMP request from a manager, performs the specified action and notifies the manager of the result of the action.

You can use extended MIB objects for the following purposes:

• Managing information specific to your enterprise as MIB objects

• Starting and stopping applications specific to your enterprise

To Page Top

(2) Definition of enterprise-specific traps

SNMP Agent can report user-specific traps to the manager as enterprise-specific traps. The trap number of an enterprise-specific trap is defined by the trap number 6 and a user-specific trap number. For details about trap numbers, see 1.2.2(1) Standard trap numbers of SNMPv1 traps.

SNMP Agent provides the snmptrap and trapsend commands to send notifications. For example, when an important process stops, you can use the snmptrap command to send an enterprise-specific trap to the manager. For details about the snmptrap and trapsend commands, see snmptrap and trapsend in Chapter 5. Commands and Processes.

To Page Top