SNMP Trap macro Formulation Process

The use of SNMP has become a default project for many devices. Then, some of the module applications have become the focus of attention. This article mainly introduces the establishment of SNMP Trap. First, let's take a look at the use environment of this Protocol.

Develop Trap macro types

It should be noted that the expansion of the Trap macro occurs in terms of completion, not during running.

Formulate enterprise terms

Enterprise terms must be existing, define enterprise management, and register permissions under it. This Trap is defined. The evaluation is placed in the enterprise item of the SNMP Trap protocol data unit. According to practice, if the evaluation of Enterprise terms is the object identifier in the Simple Network Management Protocol: = {mib-211}, the evaluation of sysObjectID is placed in the enterprise item of the SNMP Trap protocol data unit, this evaluation is not used. This provides a way to use a Trap macro to represent an existing SNMP standard Trap; it is not used to define another SNMP standard Trap method.

Variable clause

Variable clauses, which do not need to be existing, define the ordered sequence of MIB objects, which are contained in each Trap type instance. Each variable is placed in the variable binding domain of the SNMP Trap Protocol Data Unit in order. Note that in the proxy option, additional variables may appear in the variable binding domain. However, if the enterprise clause evaluation is an object identifier in the Simple Network Management Protocol: = {mib-211} as defined in the MIB-II, therefore, the appearance of additional variables will not cause consecutive SNMP messages to exceed 484 bytes.

Define description terms

The description clause does not have to be an existing one. It contains the definition of the original Trap type. Note that in order to comply with the ASN.1 syntax, all evaluations of this clause must be included in double quotation marks, although these evaluations are multithreading. Note that if the MIB module does not contain the original description of Trap elsewhere, the description terms must be existing.

Formulate reference terms

The reference clause does not need to be an existing one. It contains the reference, event, or warning of the original text of a Trap defined in other MIB modules. This is useful when some other organizations generate MIB.

Develop Trap type assessment

The evaluation of the Trap type prayer is an integer. The registration permission indicated by enterprise terms is a unique integer specified by Trap. This evaluation is placed in the dedicated Trap domain of the SNMP Trap protocol data unit, and the common Trap domain is placed in the "enterprise-specific ".

By convention, if the evaluation of Enterprise terms is an object identifier in the Simple Network Management Protocol: = {mib-211} as defined in the MIB-II, therefore, the evaluation of the Trap macro prayer is placed in the common Trap domain of the SNMP Trap protocol data unit, and the dedicated Trap domain is placed in 0. it provides methods that use a Trap macro to represent existing SNMP traps. It is not used to define additional methods for standard SNMP traps.