11. Appendix A: de-OSIfying a MIB module

There has been an increasing amount of work recently on taking MIBs defined by other organizations (e.g., the IEEE) and de-osifying them for use with the Internet-standard network management framework. The steps to achieve this are straight-forward, though tedious. Of course, it is helpful to already be experienced in writing MIB modules for use with the Internet-standard network management framework.

The first step is to construct a skeletal MIB module, as shown earlier in Section 5.8. The next step is to categorize the objects into groups. Optional objects are not permitted. Thus, when a MIB module is created, optional objects must be placed in a additional groups, which, if implemented, all objects in the group must be implemented. For the first pass, it is wisest to simply ignore any optional objects in the original MIB: experience shows it is better to define a core MIB module first, containing only essential objects; later, if experience demands, other objects can be added.

• 11.1. Managed Object Mapping
  • 11.1.1. Mapping to the SYNTAX clause
  • 11.1.2. Mapping to the UNITS clause
  • 11.1.3. Mapping to the MAX-ACCESS clause
  • 11.1.4. Mapping to the STATUS clause
  • 11.1.5. Mapping to the DESCRIPTION clause
  • 11.1.6. Mapping to the REFERENCE clause
  • 11.1.7. Mapping to the INDEX clause
  • 11.1.8. Mapping to the DEFVAL clause
• 11.2. Action Mapping
  • 11.2.1. Mapping to the SYNTAX clause
  • 11.2.2. Mapping to the MAX-ACCESS clause
  • 11.2.3. Mapping to the STATUS clause
  • 11.2.4. Mapping to the DESCRIPTION clause
  • 11.2.5. Mapping to the REFERENCE clause
• 11.3. Event Mapping
  • 11.3.1. Mapping to the STATUS clause
  • 11.3.2. Mapping to the DESCRIPTION clause
  • 11.3.3. Mapping to the REFERENCE clause