BIANCA-BRICK-SERIAL-MIB: View SNMP OID List / Download MIB

VENDOR: BINTEC COMMUNICATIONS GMBH


 Home MIB: BIANCA-BRICK-SERIAL-MIB
Download as:   

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
 org 1.3
     dod 1.3.6
         internet 1.3.6.1
             private 1.3.6.1.4
                 enterprises 1.3.6.1.4.1
                     bintec 1.3.6.1.4.1.272
                             bibo 1.3.6.1.4.1.272.4
                                 serial 1.3.6.1.4.1.272.4.25
                                       serialIfTable 1.3.6.1.4.1.272.4.25.1 no-access
The serialIfTable contains information relating to the interfaces available on the system. Each entry corresponds to an available serial interface. Entries cannot be added or deleted by the user. Creating entries: Entries are created by the system automatically when a new serial module is installed. Deleting entries: Entries are removed by the system after the appropriate serial module is removed.
                                           serialIfEntry 1.3.6.1.4.1.272.4.25.1.1 no-access
                                               serialIfIndex 1.3.6.1.4.1.272.4.25.1.1.1 integer read-only
Unique interface index of the serial interface.
                                               serialIfType 1.3.6.1.4.1.272.4.25.1.1.2 integer read-write
The serial physical interface type none(1) interface disabled x21(2) X.21/V11 (synchronous) v35(3) V.35/V11 (synchronous) v36(4) V.36/V11 (synchronous) x21bis(5) RS232/V.28 (synchronous) Enumeration: 'x21bis': 5, 'none': 1, 'x21': 2, 'v35': 3, 'v36': 4.
                                               serialIfConnector 1.3.6.1.4.1.272.4.25.1.1.3 integer read-write
The physical connector type. When configured as DCE the pins on the output connector act as a DCE interface. If configured as DTE on the output connector act as a DTE interface. dte(1) DTE output pins dce(2) DCE output pins Enumeration: 'dce': 2, 'dte': 1.
                                               serialIfLeads 1.3.6.1.4.1.272.4.25.1.1.4 integer read-write
The value of IfLeads has influence on the state of the physical layer (L1State). When configured as IfLeads=enabled, the state of the physical layer depends on the signals of the control interface pins Indication/Control on X.21 or RTS/CTS on the other protocols. When configured as IfLeads=disabled, the state of the physical layer stays always up. enabled(1) interface pins accepted. disabled(2) ignore interface pins. Enumeration: 'disabled': 2, 'enabled': 1.
                                               serialIfClock 1.3.6.1.4.1.272.4.25.1.1.5 integer read-write
The physical layer (layer 1) clocking mode. When configured as AUTO the clock provided depends what is configured on connector. If connector is configured as DTE clock must provided from external, if the connector is configured as DCE clock is generated and is provided at the output pins. It is possible to configure the clock independed from connector type. EXTERNAL clock means the clock must provided by the external device and INTERNAL clock means the clock is generated by the brick and is provided on the output pins. X.21 on clock line is provided. V.35/V.36 two clock lines are provided. auto(1) connector = DTE = extern, DCE = intern extern(2) clock pins operate as input. intern(3) clock pins operate as output. Enumeration: 'extern': 2, 'auto': 1, 'intern': 3.
                                               serialIfSpeed 1.3.6.1.4.1.272.4.25.1.1.8 integer read-write
The serial interface speed in bits per second. The range is dependant on the type of the line (balanced/unbalanced) and the quality and length of the cable. Over a short distance (about 5 m) and with a shielded cable speeds of up to 8 Mbit/sec are possible.
                                               serialIfL2Mode 1.3.6.1.4.1.272.4.25.1.1.10 integer read-write
The layer 2 mode. This value has influence on the HDLC address field (first byte of a HDCL frame). When configured as DTE the address in a command frame is 0x01, when configured as DCE it is 0x03. For response frames it is vice versa. When configured as AUTO, layer 2 is set to the same as connector is set. dte(1) HDLC address 0x01 dce(2) HDLC address 0x03 auto(3) same as conector = DTE=0x01 DCE=0x03 Enumeration: 'auto': 3, 'dce': 2, 'dte': 1.
                                               serialIfL1State 1.3.6.1.4.1.272.4.25.1.1.15 integer read-only
The serial physical layer state dn(1) physical layer is inactive up(2) physical layer is active Enumeration: 'dn': 1, 'up': 2.
                                               serialIfSpeedReal 1.3.6.1.4.1.272.4.25.1.1.16 integer read-only
In DCE/internal clock mode this is the rounded speed in bits per second, because not every baudrate can exactly be generated. In DTE/external clock mode this is the measured speed, where measurement is possible, or the configured speed in serialIfSpeed.
                                               serialIfRxPackets 1.3.6.1.4.1.272.4.25.1.1.20 counter read-only
Count of received valid Frames.
                                               serialIfRxOctets 1.3.6.1.4.1.272.4.25.1.1.21 counter read-only
Count of received bytes.
                                               serialIfTxPackets 1.3.6.1.4.1.272.4.25.1.1.22 counter read-only
Count of transmitted valid Frames.
                                               serialIfTxOctets 1.3.6.1.4.1.272.4.25.1.1.23 counter read-only
Count of transmitted bytes.
                                               serialIfRxResets 1.3.6.1.4.1.272.4.25.1.1.24 counter read-only
Count of receiver resets. Under rare circumstances it might be necessary to reset the receiver to work properly.
                                               serialIfRxAborts 1.3.6.1.4.1.272.4.25.1.1.25 counter read-only
Count of receiver aborts. The sender of a frame can indicate a frame as aborted with a special Abort sequence.
                                               serialIfRxOverruns 1.3.6.1.4.1.272.4.25.1.1.26 counter read-only
Count of receiver overruns. If the serial port is unable to grant sufficiently soon/often the bus, the RxFIFO may fill up. This leads to loss of data.
                                               serialIfRxCRCErrors 1.3.6.1.4.1.272.4.25.1.1.27 counter read-only
Count of corrupted frames. Errors due to interference on the serial cable.
                                               serialIfRxGiantFrames 1.3.6.1.4.1.272.4.25.1.1.28 counter read-only
Count of received frames with illegal framesize. This can occur if a frame delimiter is destroyed.
                                               serialIfTxResets 1.3.6.1.4.1.272.4.25.1.1.29 counter read-only
Count of transmitter resets. Under rare circumstances it might be necessary to reset the transmitter to work properly.
                                               serialIfTxAborts 1.3.6.1.4.1.272.4.25.1.1.30 counter read-only
Count of transmitter aborts. While sending a frame it might be necessary to indicate this frame as aborted. In this case the receiver regards this frame as illegal.
                                               serialIfTxUnderruns 1.3.6.1.4.1.272.4.25.1.1.31 counter read-only
Count of transmitter underruns. The serial data for the serial port is supplied too slowly.
                                               serialIfTxGiantFrames 1.3.6.1.4.1.272.4.25.1.1.32 counter read-only
Count of transmitted frames with illegal framesize. This can occur if an upper module creates packets with more than the maximum allowed packet size.