Connected: An Internet Encyclopedia
RFC 1452 - 2.2. Trap Definitions

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1452
Up: 2. Management Information
Prev: 2.1. Object Definitions
Next: 2.3. Compliance Statements

### 2.2. Trap Definitions

If a MIB module is changed to conform to the SNMPv2 framework, then each occurrence of the TRAP-TYPE macro must be changed to a corresponding invocation of the NOTIFICATION-TYPE macro:

1. The IMPORTS statement must not reference RFC-1215.

2. The ENTERPRISES clause must be removed.

3. The VARIABLES clause must be renamed to the OBJECTS clause.

4. The STATUS clause must be added.

5. The value of an invocation of the NOTIFICATION-TYPE macro is an OBJECT IDENTIFIER, not an INTEGER, and must be changed accordingly.

Next: 2.3. Compliance Statements

Connected: An Internet Encyclopedia
RFC 1452 - 2.2. Trap Definitions