ZYXEL-OAM-MIB: View SNMP OID List / Download MIB

VENDOR: ZYXEL COMMUNICATIONS CORP.


 Home MIB: ZYXEL-OAM-MIB
Download as:   
SNMPv2-CONF, ZYXEL-ES-SMI, IF-MIB, SNMPv2-SMI, P-BRIDGE-MIB, SNMPv2-TC

Download standard MIB format if you are planning to load a MIB file into some system (OS, Zabbix, PRTG ...) or view it with a MIB browser. CSV is more suitable for analyzing and viewing OID' and other MIB objects in excel. JSON and YAML formats are usually used in programing even though some systems can use MIB in YAML format (like Logstash).
Keep in mind that standard MIB files can be successfully loaded by systems and programs only if all the required MIB's from the "Imports" section are already loaded.
The tree-like SNMP object navigator requires no explanations because it is very simple to use. And if you stumbled on this MIB from Google note that you can always go back to the home page if you need to perform another MIB or OID lookup.


Object Name OID Type Access Info
 zyxelOam 1.3.6.1.4.1.890.1.15.3.56
The subtree for Operations, Administration, and Maintenance (OAM)
       zyxelOamSetup 1.3.6.1.4.1.890.1.15.3.56.1
           zyOamState 1.3.6.1.4.1.890.1.15.3.56.1.1 enabledstatus read-write
Enable/Disable administrative status on the switch.
           zyxelOamPortTable 1.3.6.1.4.1.890.1.15.3.56.1.2 no-access
The table contains OAM (Operations, Administration, and Maintenance) port configuration.
               zyxelOamPortEntry 1.3.6.1.4.1.890.1.15.3.56.1.2.1 no-access
An entry contains OAM port configuration.
                   zyOamPortFunctionsSupported 1.3.6.1.4.1.890.1.15.3.56.1.2.1.1 bits read-write
The OAM functions supported on this Ethernet-like interface. OAM consists of separate functional sets beyond the basic discovery process that is always required. These functional groups can be supported independently by any implementation. These values are communicated to the peer via the local configuration field of Information OAMPDUs. Setting 'unidirectionalSupport(0)' indicates that the OA entity supports the transmission of OAMPDUs on links that are operating in unidirectional mode (traffic flowing in one direction only). Setting 'loopbackSupport(1)' indicates that the OAM entity can initiate and respond to loopback commands. Setting 'eventSupport(2)' indicates that the OAM entity can send and receive Event Notification OAMPDUs. Setting 'variableSupport(3)' indicates that the OAM entity can send and receive Variable Request and Response OAMPDUs. Bits: 'eventSupport': 2, 'unidirectionalSupport': 0, 'variableSupport': 3, 'loopbackSupport': 1.