XEDIA-ETHERNET-MIB: View SNMP OID List / Download MIB

VENDOR: XEDIA CORPORATION


 Home MIB: XEDIA-ETHERNET-MIB
Download as:   
SNMPv2-CONF, EtherLike-MIB, SNMPv2-SMI, XEDIA-REG, 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
 xediaEthernetMIB 1.3.6.1.4.1.838.3.3
This module defines proprietary objects that extend those in IETF's the Ethernet-Like Interface MIB.
     xdot3Objects 1.3.6.1.4.1.838.3.3.1
         xdot3StatsTable 1.3.6.1.4.1.838.3.3.1.1 no-access
Additional Xedia proprietary statistics for ethernet-like interfaces.
             xdot3StatsEntry 1.3.6.1.4.1.838.3.3.1.1.1 no-access
Additional Xedia proprietary statistics for single ethernet-like interface.
                 xdot3StatsOutUnderflows 1.3.6.1.4.1.838.3.3.1.1.1.1 counter32 read-only
A count of frames not transmitted on a particular interface because of underflow. An underflow occurs when the driver does not keep up with the hardware's transmit speed in providing buffers.
                 xdot3StatsOutNoCarriers 1.3.6.1.4.1.838.3.3.1.1.1.2 counter32 read-only
The number of times that the carrier signal from the transceiver was not present when a frame was to be transmitted.
                 xdot3StatsOutCarrierLosses 1.3.6.1.4.1.838.3.3.1.1.1.3 counter32 read-only
The number of times the carrier was lost during transmission.
                 xdot3StatsOutJabberTimeouts 1.3.6.1.4.1.838.3.3.1.1.1.4 counter32 read-only
The number of times a transmission was aborted because the jabber timer timed out.
                 xdot3StatsOutTotalCollisions 1.3.6.1.4.1.838.3.3.1.1.1.5 counter32 read-only
The total number of collisions that have occurred while transmitting on this interface.
                 xdot3StatsInDescriptorErrors 1.3.6.1.4.1.838.3.3.1.1.1.6 counter32 read-only
The number of frames that were truncated because they did not fit within the current desriptor buffers.
                 xdot3StatsInRunts 1.3.6.1.4.1.838.3.3.1.1.1.7 counter32 read-only
The number of runt frames. A runt frame may have been damaged by collision or premature termination before the collision window had passed.
                 xdot3StatsInTotalCollisions 1.3.6.1.4.1.838.3.3.1.1.1.8 counter32 read-only
The number of collisions detected on incoming frames.
                 xdot3StatsInDribbles 1.3.6.1.4.1.838.3.3.1.1.1.9 counter32 read-only
The number of frames which were not a multiple of 8 bytes.
                 xdot3StatsInOverflows 1.3.6.1.4.1.838.3.3.1.1.1.10 counter32 read-only
The number of frames that were truncated due to FIFO overflow. This indicates a hardware problem (as opposed to MissedFrames which indicates the software did not keep up).
                 xdot3StatsInV1EthFrames 1.3.6.1.4.1.838.3.3.1.1.1.11 counter32 read-only
The number of Ethernet-type (version 1) frames.
                 xdot3StatsInV2Dot3Frames 1.3.6.1.4.1.838.3.3.1.1.1.12 counter32 read-only
The number of 802.3-type (version 2) frames.
                 xdot3StatsInMissedFrames 1.3.6.1.4.1.838.3.3.1.1.1.13 counter32 read-only
The number of frames that were received by the hardware but that were not picked up by the driver.
                 xdot3NegotiatedConfigSpeed 1.3.6.1.4.1.838.3.3.1.1.1.14 integer read-only
The negotiated configured speed of the interface when the auto negotiates mode is enable. Enumeration: 'gbps1': 3, 'unknown': 4, 'mbps100': 2, 'mbps10': 1.
                 xdot3NegotiatedConfigDuplexMode 1.3.6.1.4.1.838.3.3.1.1.1.15 integer read-only
The negotiated configured duplex mode of the interface. Enumeration: 'unknown': 3, 'full': 1, 'half': 2.
                 xdot3NegotiatedFlowControl 1.3.6.1.4.1.838.3.3.1.1.1.16 integer read-only
The negotiated configured flow control parameters. Enumeration: 'disabled': 1, 'enabledXmitAndRcv': 4, 'enabledRcv': 3, 'enabledXmit': 2, 'unknown': 5.
                 xdot3IfOperStatus 1.3.6.1.4.1.838.3.3.1.1.1.17 integer read-only
This is a reference object (from the ifmib.mi2's ifOperStatus) reports the current operational states of the interface for the auto-negotiate configuration purpose. Enumeration: 'dormant': 5, 'lowerLayerDown': 7, 'unknown': 4, 'testing': 3, 'up': 1, 'down': 2, 'notPresent': 6.
         xdot3ConfigTable 1.3.6.1.4.1.838.3.3.1.2 no-access
Xedia proprietary configuration parameters for ethernet-like interfaces.
             xdot3ConfigEntry 1.3.6.1.4.1.838.3.3.1.2.1 no-access
Xedia proprietary configuration parameters for single ethernet-like interface.
                 xdot3ConfigSpeed 1.3.6.1.4.1.838.3.3.1.2.1.1 integer read-write
The configured speed of the interface. This may be set by the administrator or may be the result of auto-negotiation. Enumeration: 'gbps1': 3, 'mbps100': 2, 'mbps10': 1.
                 xdot3ConfigDuplexMode 1.3.6.1.4.1.838.3.3.1.2.1.2 integer read-write
The configured mode of the interface. Enumeration: 'full': 1, 'half': 2.
                 xdot3ConfigMedia 1.3.6.1.4.1.838.3.3.1.2.1.3 integer read-only
The media type of the interface. The value 'tx(1)' indicates copper, 'fx(2)' indicates 850 nm multi-mode fiber, 'sx(3)' indicates 850 nm multi-mode fiber and lx(4) indicates 1300 nm single-mode or multi-mode fiber. Enumeration: 'fx': 2, 'sx': 3, 'lx': 4, 'tx': 1.
                 xdot3ConfigCaptureEffectResol 1.3.6.1.4.1.838.3.3.1.2.1.4 integer read-write
This object controls whether a non-standard backoff algorithm is used for collision handling in order to avoid 'capture effect'. Capture effect occurs when two stations transmit in such a way that, because of collision backoff, one station captures the channel for an unfair amount of time (and the line may remain idle for a long time after that station stops transmitting because of the second station increasing its backoff time.) The value of 'enabled(1)' indicates the enhanced algorithm will be use. The value 'disabled(2)' is the default and indicates the standard backoff algorithm is used. Enumeration: 'disabled': 2, 'enabled': 1.
                 xdot3ConfigAutoNegotiate 1.3.6.1.4.1.838.3.3.1.2.1.5 integer read-write
This object controls whether to negotiate the speed and duplex mode for 10/100 fast ethernet; and negotiate duplex mode and MAC control for gigabit ethernet interface. Enumeration: 'disabled': 2, 'enabled': 1.
     xdot3Conformance 1.3.6.1.4.1.838.3.3.2
         xdot3Compliances 1.3.6.1.4.1.838.3.3.2.1
             xdot3Compliance 1.3.6.1.4.1.838.3.3.2.1.1
The compliance statement for all agents that support this MIB. A compliant agent implements all objects defined in this MIB.
         xdot3Groups 1.3.6.1.4.1.838.3.3.2.2
             xdot3Group 1.3.6.1.4.1.838.3.3.2.2.1
The set of all accessible objects in this MIB.