TN-DOT3-OAM-MIB: View SNMP OID List / Download MIB

VENDOR: NOKIA


 Home MIB: TN-DOT3-OAM-MIB
Download as:   
SNMPv2-CONF, IF-MIB, TROPIC-GLOBAL-REG, SNMPv2-SMI, DOT3-OAM-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
 tnDOT3OAMMIBModule 1.3.6.1.4.1.7483.5.1.3.42
This document is the SNMP MIB module to manage and provision Ethernet OAM (802.3ah) functionality for the Nokia 7xxx device. This includes extensions to the DOT3-OAM-MIB defined in IEEE 802.3ah to allow transmit interval configuration and other locally configured modifications. Copyright 2006-2009 Nokia. All rights reserved. Reproduction of this document is authorized on the condition that the foregoing copyright notice is included. This SNMP MIB module (Specification) embodies Nokia's proprietary intellectual property. Nokia retains all title and ownership in the Specification, including any revisions. Nokia grants all interested parties a non-exclusive license to use and distribute an unmodified copy of this Specification in connection with management of Nokia products, and without fee, provided this copyright notice and license appear on all copies. This Specification is supplied 'as is', and Nokia makes no warranty, either express or implied, as to the use, operation, condition, or performance of the Specification.
 tnDot3OamObjs 1.3.6.1.4.1.7483.6.1.2.42
       tnDot3OamEntryObjs 1.3.6.1.4.1.7483.6.1.2.42.1
           tnDot3OamTable 1.3.6.1.4.1.7483.6.1.2.42.1.1 no-access
The tnDot3OamTable is used to store proprietary configuration information on a particular Ethernet like interface (OAM entity) in the system that supports the OAM functions defined in [802.3ah].
               tnDot3OamEntry 1.3.6.1.4.1.7483.6.1.2.42.1.1.1 no-access
An entry in the tnDot3OamTable containing configuration information applicable to an OAM entity.
                   tnDot3OamLastChanged 1.3.6.1.4.1.7483.6.1.2.42.1.1.1.1 timestamp read-only
The value of tnDot3OamLastChanged indicates the sysUpTime value when this row was last modified.
                   tnDot3OamInterval 1.3.6.1.4.1.7483.6.1.2.42.1.1.1.2 unsigned32 read-write
The value of tnDot3OamInterval specifies the number of 100ms time intervals between each periodic OAMPDU transmit and receive. A lower value implies that OAMPDUs will be transmitted more frequently to the peer, and OAMPDUs must be received more frequently from the peer. The default is set to 10, meaning 1 second between transmits and receives.
                   tnDot3OamMultiplier 1.3.6.1.4.1.7483.6.1.2.42.1.1.1.3 unsigned32 read-write
The value of tnDot3OamMultiplier specifies how many receive intervals may expire with no OAMPDU receive. After the configured number of intervals with OAMPDU receive have passed, the OAM negotiation process will restart.
                   tnDot3OamTunneling 1.3.6.1.4.1.7483.6.1.2.42.1.1.1.4 truthvalue read-write
The value of tnDot3OamTunneling specifies if OAMPDUs should be passed transparently through the OAM entity for processing by another OAM entity across the network, or if OAMPDUs should be terminated and processed at the local OAM entity. This object can only be set to 'true' if dot3OamAdminState is set to 'disabled'. Likewise, dot3OamAdminState can only be set to 'enabled' if this object is set to 'false'. It is not valid to try and enable both OAMPDU processing and OAMPDU tunneling on the same OAM entity.
                   tnDot3OamLooped 1.3.6.1.4.1.7483.6.1.2.42.1.1.1.5 truthvalue read-only
The value of tnDot3OamLooped indicates if the OAM entity is receiving OAMPDUs that it transmitted. A value of 'true' indicates that the OAM entity is receiving it's own OAMPDUs while a value of 'false' indicates it is not.
                   tnDot3OamHoldTime 1.3.6.1.4.1.7483.6.1.2.42.1.1.1.6 unsigned32 read-write
The value of tnDot3OamHoldTime specifies the number of seconds the efm-oam protocol should wait after dot3OamOperStatus transitions from 'operational (9)' to a non-operational state before going back to the 'operational (9)' state again. Note that a transition to the 'linkFault (2)' state does not cause tnDot3OamHoldTime to be used if dot3OamOperStatus was previously in the 'operational (9)' state.
       tnDot3OamLoopbackObjs 1.3.6.1.4.1.7483.6.1.2.42.2
           tnDot3OamLoopbackTable 1.3.6.1.4.1.7483.6.1.2.42.2.1 no-access
The tnDot3OamLoopbackTable is used to store proprietary loopback configuration information on a particular Ethernet like interface (OAM entity) in the system that supports the OAM functions defined in [802.3ah].
               tnDot3OamLoopbackEntry 1.3.6.1.4.1.7483.6.1.2.42.2.1.1 no-access
An entry in the tnDot3OamLoopbackTable containing configuration information applicable to an OAM entity.
                   tnDot3OamLoopbackLastChanged 1.3.6.1.4.1.7483.6.1.2.42.2.1.1.1 timestamp read-only
The value of tnDot3OamLoopbackLastChanged indicates the sysUpTime value when this row was last modified.
                   tnDot3OamLoopbackLocalStatus 1.3.6.1.4.1.7483.6.1.2.42.2.1.1.2 integer read-write
The value of tnDot3OamLoopbackLocalStatus indicates the local loopback status of the OAM entity. This attribute allows the user to manually set the local OAM entity loopback mode overriding the 802.3ah protocol for loopback. Setting the value to 'localLoopback' can only be done if dot3OamLoopbackStatus is set to 'noLoopback'. If dot3OamLoopbackStatus is any value other than 'noLoopback', the changes to tnDot3OamLoopbackLocalStatus will have no effect. If dot3OamLoopbackStatus is set to 'localLoopback', the OAM entity will act as if its peer put the OAM entity into local loopback. This entry allows the user to put an OAM entity into local loopback mode, even if dot3OamLoopbackIgnoreRx is set to 'ignore'. Enumeration: 'noLoopback': 1, 'localLoopback': 2.
 tnDot3OamNotifyPrefix 1.3.6.1.4.1.7483.6.1.3.42
       tnDot3OamNotificationsPrefix 1.3.6.1.4.1.7483.6.1.3.42.42
             tnDot3OamNotifications 1.3.6.1.4.1.7483.6.1.3.42.42.0
                 tnDot3OamPeerChanged 1.3.6.1.4.1.7483.6.1.3.42.42.0.1
The tnDot3OamPeerChanged notification is generated when the peer information (specifically the Peer MAC address) changes. Note that this notification will only be sent out if the peer information was previously available and the information changed, and not when the peer information is first learned or becomes unavailable.
                 tnDot3OamLoopDetected 1.3.6.1.4.1.7483.6.1.3.42.42.0.2
The tnDot3OamLoopDetected notification is generated when a port receives an 802.3ah PDU with a source MAC address that matches the MAC address of that port.
                 tnDot3OamLoopCleared 1.3.6.1.4.1.7483.6.1.3.42.42.0.3
The tnDot3OamLoopCleared notification is generated when a port is no longer receiving 802.3ah PDUs with a source MAC address that matches the MAC address of that port.