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.
Parsed from file CISCO-WAN-SRM-BERT-MIB.mib
Module: CISCO-WAN-SRM-BERT-MIB
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.
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.
Parsed from file CISCO-WAN-SRM-BERT-MIB.my.txt
Company: None
Module: CISCO-WAN-SRM-BERT-MIB
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.
bertDS0DPIterationCount OBJECT-TYPE SYNTAX Integer32 (1..32) MAX-ACCESS read-write STATUS current DESCRIPTION "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." ::= { bert 12 }
bertDS0DPIterationCount OBJECT-TYPE SYNTAX INTEGER(1..32) ACCESS read-write STATUS mandatory DESCRIPTION "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." ::= { bert 12 }
Vendor: Stratacom
Module: CISCO-WAN-AXIPOP-MIB
[Automatically extracted from oidview.com]
bertDS0DPIterationCount OBJECT-TYPE SYNTAX INTEGER(1..32) ACCESS read-write STATUS mandatory DESCRIPTION "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." ::= { bert 12 }
bertDS0DPIterationCount OBJECT-TYPE SYNTAX Integer32 (1..32) MAX-ACCESS read-write STATUS current DESCRIPTION "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." ::= { bert 12 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.351.110.6.1.12.0 | bertDS0DPIterationCount | 0 | 0 | None |
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.351.110.6.1.1 | bertControl | 1 | 1 | This object controls all the SET operations on this MIB group. acquireBert : Acquire BERT resources. cnfBert : Configure th… |
| 1.3.6.1.4.1.351.110.6.1.2 | bertResourceStatus | 1 | 1 | All of bert resources can be used by only one user at a time. This gives the status of the resources. |
| 1.3.6.1.4.1.351.110.6.1.3 | bertOwner | 1 | 1 | 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 … |
| 1.3.6.1.4.1.351.110.6.1.4 | bertUserId | 1 | 1 | This identifies the user who wants to do a SET operation on this group. This will be compared against bertOwner and access will b… |
| 1.3.6.1.4.1.351.110.6.1.5 | bertStatus | 1 | 1 | This variable provides the status of BERT in the shelf. |
| 1.3.6.1.4.1.351.110.6.1.6 | bertSlotNumber | 1 | 1 | 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 r… |
| 1.3.6.1.4.1.351.110.6.1.7 | bertTestMedium | 1 | 1 | 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 confi… |
| 1.3.6.1.4.1.351.110.6.1.8 | bertPort | 1 | 1 | specifies the port number for BERT. |
| 1.3.6.1.4.1.351.110.6.1.9 | bertLine | 1 | 1 | specifies the line number for BERT. If the test medium is port, this represents the line to which the port belongs. |
| 1.3.6.1.4.1.351.110.6.1.10 | bertMode | 1 | 1 | specifies the mode, the BERT module is to be configured for. |
| 1.3.6.1.4.1.351.110.6.1.11 | bertDeviceToLoop | 1 | 1 | This shows the type of the end device and the type of the loopback used (latching/nonlatching/polynomial). |
| 1.3.6.1.4.1.351.110.6.1.13 | bertPattern | 1 | 1 | This variable determines BERT pattern to be transmitted. |
| 1.3.6.1.4.1.351.110.6.1.14 | bertLoopback | 1 | 1 | specifies the type of loopback to be (d)established. |
| 1.3.6.1.4.1.351.110.6.1.15 | bertLoopbackOperation | 1 | 1 | specifies the operation of loopback (up or down). |
| 1.3.6.1.4.1.351.110.6.1.16 | bertDS0Speed | 1 | 1 | represents the ds0 speed of the test running. |
| 1.3.6.1.4.1.351.110.6.1.17 | bertTimeSlots | 1 | 1 | represents the number of ds0s in the test medium chosen. |
| 1.3.6.1.4.1.351.110.6.1.18 | bertStartTime | 1 | 1 | The syntax is hh:mm:ss The time zone is as configured in the shelf. |
| 1.3.6.1.4.1.351.110.6.1.19 | bertStartDate | 1 | 1 | On MGX 8220, the syntax is mm/dd/yy On MGX 8850, the syntax is mm/dd/yyyy. |
| 1.3.6.1.4.1.351.110.6.1.20 | bertBitCount | 1 | 1 | This shows the number of bits transmitted. |
| 1.3.6.1.4.1.351.110.6.1.21 | bertBitErrorCount | 1 | 1 | This shows the number of bits received in error. |
| 1.3.6.1.4.1.351.110.6.1.22 | bertErrorInjectCount | 1 | 1 | This shows the number of times error was injected. |
| 1.3.6.1.4.1.351.110.6.1.23 | bertCleanupAction | 1 | 1 | 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… |
| 1.3.6.1.4.1.351.110.6.1.24 | bertAbortReason | 1 | 1 | when the BERT is aborted, this object would give the reason for that. |
| 1.3.6.1.4.1.351.110.6.1.25 | bertDDSSeekResultsTableFirstIndex | 1 | 1 | Denotes the index of the oldest entry in the table. A value of zero means that there are no entries in the table. |
| 1.3.6.1.4.1.351.110.6.1.26 | bertDDSSeekResultsTableLastIndex | 1 | 1 | Denotes the index of the latest entry in the table. A value of zero means that there are no entries in the table. |
| 1.3.6.1.4.1.351.110.6.1.27 | bertDDSSeekResultsTable | 1 | 3 | This table contains all available DDS patterns detected and latched by an interaface(lines,ports etc) configured to detect DDS pa… |
| 1.3.6.1.4.1.351.110.6.1.28 | bertSupportedTestsTable | 1 | 9 | A list of supported tests for a given SM. |