DESCRIPTION

This manual page describes the syntax and semantics used to write MIB annotations. A MIB annotation file is used to modify the behavior of certain MIB objects without having to edit the original MIB file.

MIB annotations are separate file with a .miba suffix, and is applied to to a MIB when a YANG module is generated and when the MIB is compiled. See confdc(1).

SYNTAX

Each line in a MIB annotation file has the following syntax:

<MIB Object Name> <modifier> [= <value>]
    

where modifier is one of max_access, display_hint, behavior, unique, or operational.

Blank lines are ignored, and lines starting with # are treated as comments and ignored.

If modifier is max_access, value must be one of not_accessible or read_only.

If modifier is display_hint, value must be a valid DISPLAY-HINT value. The display hint is used to determine if a string object should be treated as text or binary data.

If modifier is behavior, value must be one of noSuchObject or noSuchInstance. When a YANG module is generated from a MIB, objects with a specified behavior are not converted to YANG. When the SNMP agent responds to SNMP requests for such an object, the corresponding error code is used.

If modifier is unique, value must be a valid YANG "unique" expression, i.e., a space-separated list of column names. This modifier must be given on table entries.

If modifier is operational, there must not be any value given. A writable object marked as operational will be translated into a non-configuration YANG node, marked with a tailf:writable true statement, indicating that the object represents writable operational data.

EXAMPLE

An example of a MIB annotation file.

# the following object does not have value
ifStackLastChange behavior = noSuchInstance

# this deprecated table is not implemented
ifTestTable behavior = noSuchObject
      

SEE ALSO