CISCO-BERT-MIB
The MIB module to configure and perform Bit Error Rate Testing
(BERT) on DS3, DS1/E1 and DS0/DS0Bundle interfaces.
Bit error rate testing and loopbacks are used by carriers
and ISPs to aid in problem resolution as well as for
testing the quality of T1/E1 or T3/E3 links. Tests can
be run on a full T1/E1 line or can be run on a fractional
T1/E1 such as single DS0 or a group of DS0s. By using BERT,
poor quality links could be detected early.
BERT enables the user to test the quality of links by directly
comparing a pseudo-random or repetitive test pattern with
an identical locally generated test pattern.
Terminology:
BERT: Bit Error Rate Testing (BERT) involves generating a known
data sequence into a transmission device and examining the
received sequence at the same device or a remote device
for errors.
The use of BERT results in the computation of a bit error rate
(BER), which is
bits received in error
BER = ------------------------
number of bits transmitted
To perform a bit error rate test using one tester,
communications equipment must be placed into a loop-back
mode of operation and the BERT test can then be used to
determine if equipment is operating correctly.
When running a BERT, system expects to receive the same pattern
that is transmitting. To help ensure this, two common options
are available.
- Use loopback somewhere in the link or network. This can
be accomplished by putting the line in loop up mode;
send the pattern; find the BER.
- configure remote testing equipment to transmit the Same BERT
pattern at the same time.
Typical Sequence in Performing Bit Error Rate Test by the
device is given below:
- Loop Up:
The tester issues special code to force the far end (CPE) into
loopback. Upon recognition of the loop activation request code
the CPE enters a loop mode in which it returns the port data
back to the tester.
- Send Pattern:
After a loop has been established, the tester can generate
test pattern toward the CPE and monitor the incoming data.
- Loop Down:
The tester issues a special code (loop down command) to
release the far end from the loopback.
Terminology Used:
CPE - Customer's premise equipment. At CPE, following equipment
is required:
DSU
CSU
Usually DSU and CSU functions are incorporated by vendors
into a single CSU/DSU unit.
OCU - Office Channel Unit
CSU - Channel Service Unit
A CSU contains the last signal regenerator on the line
before DTE and mechanism to put the line into loopback
for testing from the central office.
DSU - Data Service Unit.
- Source file
CISCO-BERT-MIB- Last revised
- Identity
ciscoBertMIB- Base OID
1.3.6.1.4.1.9.9.185
Imported Objects
| CISCO-SMI | ciscoMgmt |
| IF-MIB | ifIndex |
| SNMPv2-CONF | MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page) |
| SNMPv2-SMI | Counter32 Counter64 Integer32 MODULE-IDENTITY (no object page) OBJECT-TYPE (no object page) |
| SNMPv2-TC | DateAndTime RowStatus TEXTUAL-CONVENTION (no object page) |
Net-SNMP examples using the cisco MIB directory Show commands
These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.
Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-BERT-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-BERT-MIB::ciscoBertMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-BERT-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-BERT-MIB::ciscoBertMIB'
Objects (41)
Showing 41 of 41 objects
Object legend
Object type
Icons distinguish tables, entry rows, columns, scalars, and structural nodes.
SNMPv2-TCTruthValue
Syntax
Blue badges identify the value syntax. Connected badges read as defining module and convention.
IF-MIBifIndex
Table index
Green identifies an index object; yellow names its module when the index is defined elsewhere.
r/w
deprecated
obsolete
Access and status
r/w means read-write. Grey labels mark definitions retained for compatibility.
OBS ✓
Observium use
The indicator appears only when Observium directly references that object.
ifOperStatus
.1.3.6.1.2.1…
Names and OIDs
Object names link to their detail pages. Hover or focus a linked name or badge for available definition details.
.1.3.6.1.4.1.9.9.185 |
||
.1.3.6.1.4.1.9.9.185.1 |
||
.1.3.6.1.4.1.9.9.185.1.1 |
||
.1.3.6.1.4.1.9.9.185.1.1.1 |
||
.1.3.6.1.4.1.9.9.185.1.1.1.1 |
||
|
|
.1.3.6.1.4.1.9.9.185.1.1.1.1.1 |
|
|
Enumeration
|
.1.3.6.1.4.1.9.9.185.1.1.1.1.10 |
|
|
Enumeration
|
.1.3.6.1.4.1.9.9.185.1.1.1.1.11 |
|
.1.3.6.1.4.1.9.9.185.1.1.1.1.12 |
||
|
Integer32
|
.1.3.6.1.4.1.9.9.185.1.1.1.1.13 |
|
|
|
.1.3.6.1.4.1.9.9.185.1.1.1.1.14 |
|
|
|
Bits
|
.1.3.6.1.4.1.9.9.185.1.1.1.1.15 |
|
|
OctetString
|
.1.3.6.1.4.1.9.9.185.1.1.1.1.2 |
|
Enumeration
|
.1.3.6.1.4.1.9.9.185.1.1.1.1.3 |
|
|
Enumeration
|
.1.3.6.1.4.1.9.9.185.1.1.1.1.4 |
|
|
Enumeration
|
.1.3.6.1.4.1.9.9.185.1.1.1.1.5 |
|
|
|
Enumeration
|
.1.3.6.1.4.1.9.9.185.1.1.1.1.6 |
|
Enumeration
|
.1.3.6.1.4.1.9.9.185.1.1.1.1.7 |
|
|
Enumeration
|
.1.3.6.1.4.1.9.9.185.1.1.1.1.8 |
|
|
|
secondsInteger32
|
.1.3.6.1.4.1.9.9.185.1.1.1.1.9 |
.1.3.6.1.4.1.9.9.185.1.1.2 |
||
.1.3.6.1.4.1.9.9.185.1.1.2.1 |
||
.1.3.6.1.4.1.9.9.185.1.1.2.1.1 |
||
.1.3.6.1.4.1.9.9.185.1.1.2.1.10 |
||
.1.3.6.1.4.1.9.9.185.1.1.2.1.11 |
||
.1.3.6.1.4.1.9.9.185.1.1.2.1.12 |
||
.1.3.6.1.4.1.9.9.185.1.1.2.1.13 |
||
.1.3.6.1.4.1.9.9.185.1.1.2.1.14 |
||
.1.3.6.1.4.1.9.9.185.1.1.2.1.15 |
||
.1.3.6.1.4.1.9.9.185.1.1.2.1.16 |
||
.1.3.6.1.4.1.9.9.185.1.1.2.1.2 |
||
.1.3.6.1.4.1.9.9.185.1.1.2.1.3 |
||
.1.3.6.1.4.1.9.9.185.1.1.2.1.4 |
||
.1.3.6.1.4.1.9.9.185.1.1.2.1.5 |
||
.1.3.6.1.4.1.9.9.185.1.1.2.1.6 |
||
.1.3.6.1.4.1.9.9.185.1.1.2.1.7 |
||
.1.3.6.1.4.1.9.9.185.1.1.2.1.8 |
||
.1.3.6.1.4.1.9.9.185.1.1.2.1.9 |
||
.1.3.6.1.4.1.9.9.185.8 |
||
.1.3.6.1.4.1.9.9.185.8.1 |
||
.1.3.6.1.4.1.9.9.185.8.2 |
Dependencies (7) 5 direct · 2 transitive Show tree and compile order Hide dependency details
Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.
Dependency tree
Dependency-first compile order
- SNMPv2-SMIrfc
- CISCO-SMIcisco
- SNMPv2-TCrfc
- IANAifType-MIBrfc
- SNMPv2-CONFrfc
- SNMPv2-MIBrfc
- IF-MIBrfc
- CISCO-BERT-MIBciscoselected
Type Definitions (1)
| Enumeration |
allZeros(1)allOnes(2)altOneZero(3)doubleAltOnesZeros(4)oneIn4(5)oneIn8(6)oneIn16(7)threeIn24(8)inbandLoopBackActivate(9)inbandLoopBackDeactivate(10)twoE3MinusOne(11)twoE4MinusOne(12)twoE5MinusOne(13)twoE6MinusOne(14)twoE7MinusOne(15)twoE7MinusOneFT1Loopup(16)twoE7MinusOneFT1Loopdown(17)twoE9MinusOne(18)twoE10MinusOne(19)twoE11MinusOne(20)twoE15MinusOne(21)twoE17MinusOne(22)twoE18MinusOne(23)twoE20MinusOne(24)twoE20MinusOneQRSS(25)twoE21MinusOne(26)twoE22MinusOne(27)twoE23MinusOne(28)twoE25MinusOne(29)twoE28MinusOne(30)twoE29MinusOne(31)twoE31MinusOne(32)dds1pattern(33)dds2pattern(34)dds3pattern(35)dds4pattern(36)dds5pattern(37)userPattern(38) |
Conformance Groups (5)
|
cbTestPattern cbUserPattern cbBertTxPatternInv cbBertRxPatternInv cbSingleBitErrorInsert cbErrorInsertionRate cbDuration cbOperStatus cbFailedReason cbStartDateAndTime cbDS0DPCodeIteration cbRowStatus
Collection of objects related to BERT Configuration and
BERT status. |
.1.3.6.1.4.1.9.9.185.8.2.1
|
|
|
Collection of objects related to Loopback configuration
for the BERT. |
.1.3.6.1.4.1.9.9.185.8.2.2
|
|
|
cbTxBitCountLower cbTxBitCountUpper cbRxBitCountLower cbRxBitCountUpper cbRxBitErrCountLower cbRxBitErrCountUpper cbSyncLossCounts cbPatternLossCounts cbFrameLossCounts cbESsCounts cbSESsCounts cbEFSsCounts cbErrorInjectCounts
Collection of objects related to BERT Statistics.
|
.1.3.6.1.4.1.9.9.185.8.2.3
|
|
|
Statistics objects which can hold Counter64 value.
|
.1.3.6.1.4.1.9.9.185.8.2.4
|
|
|
This group include objects only for DS1 Bert.
|
.1.3.6.1.4.1.9.9.185.8.2.5
|
Compliance Statements (1)
OID
.1.3.6.1.4.1.9.9.185.8.1.1The Compliance statement for cisco BERT management group.
Required groups
| mandatory | ciscoBertConfigGroup | |
| mandatory | ciscoBertStatsGroup | |
| optional | ciscoBertHCStatsGroup |
Implementation of this group is mandatory for SNMP v2/V3 agents. |
| optional | ciscoBertLoopbackGroup |
Implementation of this group is not mandatory when the loopbacks need not be established automatically for the devices involved in BERT. This group need not be implemented if the loopback is established manually. |
| optional | ciscoBertConfigGroupDs1 |
Implementation of this group is not mandatory. This group is needed only if there is special requirment for BERT on DS1. |