CISCO-WAN-SRM-BERT-MIB: View SNMP OID List / Download MIB

VENDOR: STRATACOM


 Home MIB: CISCO-WAN-SRM-BERT-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
     bert 1.3.6.1.4.1.351.110.6.1
         bertControl 1.3.6.1.4.1.351.110.6.1.1 integer read-write
This object controls all the SET operations on this MIB group. acquireBert : Acquire BERT resources. cnfBert : Configure the required BERT test. startBert : The configured test has to be started. modBert : Modify parameters for the ongoing BERT test. delBert : Running BERT test has to be stopped. The above list shows the sequence in which the SET operations on this group need to be done, ideally. Bert can be operated upon only with bertUserId and bertSlotNumber. The default value is 0, means no action. Enumeration: 'modBert': 5, 'startBert': 4, 'releaseBert': 2, 'delBert': 6, 'cnfBert': 3, 'acquireBert': 1.
         bertResourceStatus 1.3.6.1.4.1.351.110.6.1.2 integer read-only
All of bert resources can be used by only one user at a time. This gives the status of the resources. Enumeration: 'cleanupPending': 3, 'free': 1, 'inUse': 2.
         bertOwner 1.3.6.1.4.1.351.110.6.1.3 displaystring read-only
This refers to the user who owns the BERT resources. If the user is a CLI user, then this is username. If it is SNMP Manager(For example Cisco Wan Manager), then this would be the IP address. For example, this value can be, 192.9.209.157 within quotes.
         bertUserId 1.3.6.1.4.1.351.110.6.1.4 displaystring read-write
This identifies the user who wants to do a SET operation on this group. This will be compared against bertOwner and access will be given only if it matches. Hence, for every SET request, this object should have a valid value. If the user is a CLI user, then this is username. If it is SNMP Manager, then this would be the IP address. For example, this value can be, 192.9.209.157 within quotes. Required for bert operations.
         bertStatus 1.3.6.1.4.1.351.110.6.1.5 integer read-only
This variable provides the status of BERT in the shelf. Enumeration: 'bertOutOfSync': 3, 'portFacilityFifoFault': 7, 'metallicInLoop': 9, 'bertFailed': 10, 'searchingDDSCommands': 4, 'facilityInLoop': 6, 'portFacilityFifoOutOfSync': 8, 'farEndInLoop': 5, 'inactive': 1, 'bertInSync': 2.
         bertSlotNumber 1.3.6.1.4.1.351.110.6.1.6 integer32 read-write
specifies the physical slot number of the Service Module which is to run BERT For MGX 8220, the range is 5-14. For MGX 8850, the range is 1-6, 9-14, 17-22, 25-30. Required for bert operations.
         bertTestMedium 1.3.6.1.4.1.351.110.6.1.7 integer read-write
specifies whether the bert is to test a port or an entire T1/E1 line. No default value for this, it has to be set if bert is configured. Enumeration: 'line': 2, 'port': 1.
         bertPort 1.3.6.1.4.1.351.110.6.1.8 integer32 read-write
specifies the port number for BERT.
         bertLine 1.3.6.1.4.1.351.110.6.1.9 integer32 read-write
specifies the line number for BERT. If the test medium is port, this represents the line to which the port belongs.
         bertMode 1.3.6.1.4.1.351.110.6.1.10 integer read-write
specifies the mode, the BERT module is to be configured for. Enumeration: 'ddsSeek': 2, 'bertPatternTest': 1, 'loopback': 3.
         bertDeviceToLoop 1.3.6.1.4.1.351.110.6.1.11 integer read-write
This shows the type of the end device and the type of the loopback used (latching/nonlatching/polynomial). Enumeration: 'noLatchDSU': 4, 'v54Polynomial': 11, 'latchDS0Line': 6, 'latchDSU': 9, 'smartJackInband': 16, 'latchOCU': 7, 'metallic': 14, 'inband': 12, 'esf': 13, 'noLatchCSU': 3, 'latchDS0Drop': 5, 'latchCSU': 8, 'noLatchOCUwitout1': 2, 'noLatchOCUwith1': 1, 'noDevice': 15, 'latchHL96': 10.
         bertDS0DPIterationCount 1.3.6.1.4.1.351.110.6.1.12 integer32 read-write
The Iteration Register needs to be programmed in SRM when DSO drop loop option is selected in bertDeviceToLoop. The value to be programmed there is minus one of this object value, since the register is 0 based. DSP-OP devices can be cross connected in the centeral office. By this, the user has capablitiy to put any of the devices in the chain in loopback mode. This is done by repeating the latching activation code in a specific manner. The binary number in the iterataion register determines how many times the first portion of a latching loop activation code needs to be repeated as per user request and according to the Bellcore spec. A value of 0 results in no iteration and will cause the very first device in chain to go into loop back. A value of 1 will result into one iteration and will cause the second device to go into loopback and so on. The range of this count is 1 to 32, and it would translate to a range of 0 to 31 for the iteration register.
         bertPattern 1.3.6.1.4.1.351.110.6.1.13 integer read-write
This variable determines BERT pattern to be transmitted. Enumeration: 'allOnes': 2, 'oneInEight': 9, 'elevenBit': 17, 'nineBit': 16, 'twentythreeBit': 8, 'fifteenBit': 5, 'threeIntwentyfour': 10, 'dds-1': 11, 'twentyBit': 6, 'dds-3': 13, 'dds-2': 12, 'alternateONeZero': 3, 'allZeros': 1, 'twentyBitQRSS': 7, 'dds-5': 15, 'doubleOneZero': 4, 'dds-4': 14.
         bertLoopback 1.3.6.1.4.1.351.110.6.1.14 integer read-write
specifies the type of loopback to be (d)established. Enumeration: 'metallicLoopback': 3, 'farEndLoopback': 1, 'facilityLoopback': 2.
         bertLoopbackOperation 1.3.6.1.4.1.351.110.6.1.15 integer read-write
specifies the operation of loopback (up or down). Enumeration: 'loopDown': 2, 'loopUp': 1.
         bertDS0Speed 1.3.6.1.4.1.351.110.6.1.16 integer read-only
represents the ds0 speed of the test running. Enumeration: 'speed64k': 2, 'speed56k': 1.
         bertTimeSlots 1.3.6.1.4.1.351.110.6.1.17 integer32 read-only
represents the number of ds0s in the test medium chosen.
         bertStartTime 1.3.6.1.4.1.351.110.6.1.18 displaystring read-only
The syntax is hh:mm:ss The time zone is as configured in the shelf.
         bertStartDate 1.3.6.1.4.1.351.110.6.1.19 displaystring read-only
On MGX 8220, the syntax is mm/dd/yy On MGX 8850, the syntax is mm/dd/yyyy.
         bertBitCount 1.3.6.1.4.1.351.110.6.1.20 integer32 read-only
This shows the number of bits transmitted.
         bertBitErrorCount 1.3.6.1.4.1.351.110.6.1.21 integer32 read-only
This shows the number of bits received in error.
         bertErrorInjectCount 1.3.6.1.4.1.351.110.6.1.22 integer32 read-only
This shows the number of times error was injected.
         bertCleanupAction 1.3.6.1.4.1.351.110.6.1.23 integer read-only
When the BERT has to be stopped or aborted (due to card state changes), this object would give the exact action to take. The bert related changes to the shelf, then, can be cleaned up. When its value is a Loopdown, it implies smCleanup plus the corresponding Loopdown. Enumeration: 'v54PolynomialLoopdown': 9, 'esfLoopdown': 11, 'facilityLoopdown': 12, 'smartJackInbandLoopdown': 14, 'inbandLoopdown': 10, 'metallicLoopdown': 13, 'noAction': 1, 'latchHL96Loopdown': 8, 'latchDS0LineLoopdown': 4, 'smCleanup': 2, 'latchOCULoopdown': 5, 'latchDSULoopdown': 7, 'latchDS0DropLoopdown': 3, 'latchCSULoopdown': 6.
         bertAbortReason 1.3.6.1.4.1.351.110.6.1.24 integer read-only
when the BERT is aborted, this object would give the reason for that. Enumeration: 'coreCardSwitch': 4, 'ascStateChange': 1, 'srmStateChange': 3, 'smStateChange': 2, 'smRedundancySwitch': 5.
         bertDDSSeekResultsTableFirstIndex 1.3.6.1.4.1.351.110.6.1.25 integer32 read-only
Denotes the index of the oldest entry in the table. A value of zero means that there are no entries in the table.
         bertDDSSeekResultsTableLastIndex 1.3.6.1.4.1.351.110.6.1.26 integer32 read-only
Denotes the index of the latest entry in the table. A value of zero means that there are no entries in the table.
         bertDDSSeekResultsTable 1.3.6.1.4.1.351.110.6.1.27 no-access
This table contains all available DDS patterns detected and latched by an interaface(lines,ports etc) configured to detect DDS patterns.
               bertDDSSeekResultsTableEntry 1.3.6.1.4.1.351.110.6.1.27.1 no-access
An entry in the detected DDS codes table.
                   bertDDSSeekResultsTableIndex 1.3.6.1.4.1.351.110.6.1.27.1.1 integer32 read-only
Denotes the serial number of the entry in the table.
                   bertDDSCode 1.3.6.1.4.1.351.110.6.1.27.1.2 integer read-only
Denotes the type of DDS code detected. Enumeration: 'unnamed': 50, 'mjuAlert': 114, 'loopbackEnable': 86, 'abnormalStationCondition': 30, 'test': 28, 'idle': 126, 'farEndVoice': 90, 'muxOutOfSync': 26, 'transitionInProgress': 58, 'unassignedMuxChannel': 24, 'release': 120, 'ocuLoopback': 42, 'dsuLoopback': 44, 'channelLoopback': 40, 'block': 10, 'testAlert': 108.
         bertSupportedTestsTable 1.3.6.1.4.1.351.110.6.1.28 no-access
A list of supported tests for a given SM.
               bertSupportedTestsTableEntry 1.3.6.1.4.1.351.110.6.1.28.1 no-access
A general supported tests entry.
                   bertSupportedTestsTableIndex 1.3.6.1.4.1.351.110.6.1.28.1.1 integer32 read-only
This index is the physical slot number of the Service Module whose entry it represents in the table. For MGX 8220, the range is 5-14. For MGX 8850, the range is 1-6, 9-14, 17-22, 25-30.
                   bertSupportFlag 1.3.6.1.4.1.351.110.6.1.28.1.2 integer read-only
'yes' if the table entry correctly represents the supported tests for the SM on the corresponding slot. 'no' if no tests at all are supported. Enumeration: 'yes': 1, 'no': 2.
                   bertTestMediumMask 1.3.6.1.4.1.351.110.6.1.28.1.3 integer32 read-only
Every test medium is represented by a bit of mask. Bits 0-1 are valid in this integer. The meaning of the mask can be understood from the example below: -------------------------- TestMedium | SM | support -------------------------- port | 1 line | 1 -------------------------- (Table contents applicable to FRSM-4T1) bertTestMediumMask = 11 binary The column titles represent the variables bertTestMedium depends on. The mask is represented in column major order.
                   bertModeMask 1.3.6.1.4.1.351.110.6.1.28.1.4 integer32 read-only
Every mode is represented by 2 bits of mask. Bits 0-5 are valid in this integer. The meaning of the mask can be understood from the example below: ----------------------------------------------------------- Mode | SM support | Test Medium: | | Multiple | | T1 time slots ----------------------------------------------------------- Pattern test | 1 | 1 DDS seek | 1 | 0 Loopback | 1 | 1 ----------------------------------------------------------- (Table contents applicable to FRSM-4T1) bertModeMask = 101111 binary The column titles represent the variables bertMode depends on. The mask is represented in column major order.
                   bertDeviceToLoopMask 1.3.6.1.4.1.351.110.6.1.28.1.5 integer32 read-only
Every class of devices to loop is represented by 6 bits of mask. Bits 0-29 are valid in this integer. The meaning of the mask can be understood from the example below: ----------------------------------------------------------- | | | Test Medium Class of | SM | MODE |________________________________ devices |supp | Loopback|Line |multiple T1 | 64k | 56k | | | | time slots | | ----------------------------------------------------------- noLatch | 1 0 0 0 0 1 latch | 1 1 0 0 1 1 v54 | 1 1 0 1 1 1 inband/esf| 1 1 1 0 0 0 metallic | 1 0 1 0 0 0 ----------------------------------------------------------- (Table contents applicable to FRSM-4T1) bertDeviceToLoopMask = 001110011000100110000111011111 binary The column titles represent the variables bertDeviceToLoop depends on. The mask is represented in column major order. Due to the limitation on the length of the mask, 'noDevice' option is not represented in this mask. But, the mask for it, is assumed to be a row of ones except for a zero on 'MODE Loopback' column.
                   bertPatternMask 1.3.6.1.4.1.351.110.6.1.28.1.6 integer32 read-only
Every class of patterns is represented by 2 bits of mask. Bits 0-3 are valid in this integer. The meaning of the mask can be understood from the example below: ---------------------------------------------- Class of | SM | Non latching patterns | support |device to loop ---------------------------------------------- Other patterns | 1 | 0 ---------------------------------------------- Patterns | 1 | 1 power 9 and 11 | | ---------------------------------------------- (Table contents applicable to FRSM-4T1) bertPatternMask = 1011 binary The column titles represent the variables bertPattern depends on. The mask is represented in column major order.
                   bertLoopbackMask 1.3.6.1.4.1.351.110.6.1.28.1.7 integer32 read-only
Every loopback is represented by 2 bits of mask. Bits 0-5 are valid in this integer. The meaning of the mask can be understood from the example below: ---------------------------------------------- Loopback | SM | Test Medium | support | Port ---------------------------------------------- Far End Loopback | 1 | 1 Facility Loopback | 1 | 1 Metallic Loopback | 1 | 0 ---------------------------------------------- (Table contents applicable to FRSM-4T1) bertLoopbackMask = 011111 binary The column titles represent the variables bertLoopback depends on. The mask is represented in column major order.
                   bertCardT1E1Type 1.3.6.1.4.1.351.110.6.1.28.1.8 integer read-only
Specifies whether a t1 or e1 card. Enumeration: 'e1': 2, 't1': 1.
 ciscoWanSrmBertMIB 1.3.6.1.4.1.351.150.31
The MIB Module for BERT(Bit Error Rate Testing) using Service Resource Module(SRM). This MIB module is used for BERT on FRSM, AUSM, CESM, VISM modules. This module contains information on results from BERT tests using DDS(Digital Data Service) pattern.
       ciscoWanSrmBertMIBConformance 1.3.6.1.4.1.351.150.31.2
           ciscoWanSrmBertMIBGroups 1.3.6.1.4.1.351.150.31.2.1
               ciscoWanSrmBertConfGroup 1.3.6.1.4.1.351.150.31.2.1.1
The collection of objects which are used for configuring/running BERT on Service modules using SRM module.
               ciscoWanSrmBertTestResultsGroup 1.3.6.1.4.1.351.150.31.2.1.2
The collection of objects which are used for finding the results of running BERT tests.
               ciscoWanSrmBertDDSResultsGroup 1.3.6.1.4.1.351.150.31.2.1.3
The collection of objects which are used for finding the results of running BERT tests using DDS pattern.
           ciscoWanSrmBertMIBCompliances 1.3.6.1.4.1.351.150.31.2.2
               ciscoWanSrmBertCompliance 1.3.6.1.4.1.351.150.31.2.2.1
The compliance statement for objects related to Bert MIB.