Home/Catalog/BIANCA-BRICK-SERIAL-MIB

BIANCA-BRICK-SERIAL-MIB

AI MIB Summary

Standard SNMP MIB module defining data structures for BIANCA-BRICK-SERIAL-MIB.

33
Objects
Active
Status
2
Dependencies

Imported Objects

Objects

33 total
Object Name
org
OBJECT IDENTIFIER
.1.3
RFC1155-SMI
Unknown
.1.3
dod
OBJECT IDENTIFIER
.1.3.6
internet
OBJECT IDENTIFIER
.1.3.6.1
private
OBJECT IDENTIFIER
.1.3.6.1.4
enterprises
OBJECT IDENTIFIER
.1.3.6.1.4.1
bintec
OBJECT IDENTIFIER
.1.3.6.1.4.1.272
bibo
OBJECT IDENTIFIER
.1.3.6.1.4.1.272.4
serial
OBJECT IDENTIFIER
.1.3.6.1.4.1.272.4.25
serialIfTableThe 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.
SEQUENCE OF SerialIfEntry
.1.3.6.1.4.1.272.4.25.1
serialIfEntry
SerialIfEntry
.1.3.6.1.4.1.272.4.25.1.1
serialIfIndexUnique interface index of the serial interface.ro
INTEGER
.1.3.6.1.4.1.272.4.25.1.1.1
serialIfTypeThe 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)rw
Enumeration
.1.3.6.1.4.1.272.4.25.1.1.2
serialIfConnectorThe 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 pinsrw
Enumeration
.1.3.6.1.4.1.272.4.25.1.1.3
serialIfLeadsThe 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.rw
Enumeration
.1.3.6.1.4.1.272.4.25.1.1.4
serialIfClockThe 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.rw
Enumeration
.1.3.6.1.4.1.272.4.25.1.1.5
serialIfSpeedThe 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.rw
INTEGER
.1.3.6.1.4.1.272.4.25.1.1.8
serialIfL2ModeThe 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=0x03rw
Enumeration
.1.3.6.1.4.1.272.4.25.1.1.10
serialIfL1StateThe serial physical layer state dn(1) physical layer is inactive up(2) physical layer is activero
Enumeration
.1.3.6.1.4.1.272.4.25.1.1.15
serialIfSpeedRealIn 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.ro
INTEGER
.1.3.6.1.4.1.272.4.25.1.1.16
serialIfRxPacketsCount of received valid Frames.ro
Counter
.1.3.6.1.4.1.272.4.25.1.1.20
serialIfRxOctetsCount of received bytes.ro
Counter
.1.3.6.1.4.1.272.4.25.1.1.21
serialIfTxPacketsCount of transmitted valid Frames.ro
Counter
.1.3.6.1.4.1.272.4.25.1.1.22
serialIfTxOctetsCount of transmitted bytes.ro
Counter
.1.3.6.1.4.1.272.4.25.1.1.23
serialIfRxResetsCount of receiver resets. Under rare circumstances it might be necessary to reset the receiver to work properly.ro
Counter
.1.3.6.1.4.1.272.4.25.1.1.24
serialIfRxAbortsCount of receiver aborts. The sender of a frame can indicate a frame as aborted with a special Abort sequence.ro
Counter
.1.3.6.1.4.1.272.4.25.1.1.25
serialIfRxOverrunsCount 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.ro
Counter
.1.3.6.1.4.1.272.4.25.1.1.26
serialIfRxCRCErrorsCount of corrupted frames. Errors due to interference on the serial cable.ro
Counter
.1.3.6.1.4.1.272.4.25.1.1.27
serialIfRxGiantFramesCount of received frames with illegal framesize. This can occur if a frame delimiter is destroyed.ro
Counter
.1.3.6.1.4.1.272.4.25.1.1.28
serialIfTxResetsCount of transmitter resets. Under rare circumstances it might be necessary to reset the transmitter to work properly.ro
Counter
.1.3.6.1.4.1.272.4.25.1.1.29
serialIfTxAbortsCount 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.ro
Counter
.1.3.6.1.4.1.272.4.25.1.1.30
serialIfTxUnderrunsCount of transmitter underruns. The serial data for the serial port is supplied too slowly.ro
Counter
.1.3.6.1.4.1.272.4.25.1.1.31
serialIfTxGiantFramesCount of transmitted frames with illegal framesize. This can occur if an upper module creates packets with more than the maximum allowed packet size.ro
Counter
.1.3.6.1.4.1.272.4.25.1.1.32