| bertControl |
.1.3.6.1.4.1.351.110.6.1.1 |
|
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.
|
| bertResourceStatus |
.1.3.6.1.4.1.351.110.6.1.2 |
|
All of bert resources can be used by only one user at a time.
This gives the status of the resources.
|
| bertOwner |
.1.3.6.1.4.1.351.110.6.1.3 |
|
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 |
|
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 |
|
This variable provides the status of BERT in the shelf.
|
| bertSlotNumber |
.1.3.6.1.4.1.351.110.6.1.6 |
|
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 |
|
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.
|
| bertPort |
.1.3.6.1.4.1.351.110.6.1.8 |
|
specifies the port number for BERT.
|
| bertLine |
.1.3.6.1.4.1.351.110.6.1.9 |
|
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 |
|
specifies the mode, the BERT module is to be
configured for.
|
| bertDeviceToLoop |
.1.3.6.1.4.1.351.110.6.1.11 |
|
This shows the type of the end device and the type of the
loopback used (latching/nonlatching/polynomial).
|
| bertDS0DPIterationCount |
.1.3.6.1.4.1.351.110.6.1.12 |
|
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 |
|
This variable determines BERT pattern to
be transmitted.
|
| bertLoopback |
.1.3.6.1.4.1.351.110.6.1.14 |
|
specifies the type of loopback to be (d)established.
|
| bertLoopbackOperation |
.1.3.6.1.4.1.351.110.6.1.15 |
|
specifies the operation of loopback (up or down).
|
| bertDS0Speed |
.1.3.6.1.4.1.351.110.6.1.16 |
|
represents the ds0 speed of the test running.
|
| bertTimeSlots |
.1.3.6.1.4.1.351.110.6.1.17 |
|
represents the number of ds0s in the test medium chosen.
|
| bertStartTime |
.1.3.6.1.4.1.351.110.6.1.18 |
|
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 |
|
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 |
|
This shows the number of bits transmitted.
|
| bertBitErrorCount |
.1.3.6.1.4.1.351.110.6.1.21 |
|
This shows the number of bits received in error.
|
| bertErrorInjectCount |
.1.3.6.1.4.1.351.110.6.1.22 |
|
This shows the number of times error was injected.
|
| bertCleanupAction |
.1.3.6.1.4.1.351.110.6.1.23 |
|
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.
|
| bertAbortReason |
.1.3.6.1.4.1.351.110.6.1.24 |
|
when the BERT is aborted, this object would give the
reason for that.
|
| bertDDSSeekResultsTableFirstIndex |
.1.3.6.1.4.1.351.110.6.1.25 |
|
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 |
|
Denotes the index of the latest entry in the table.
A value of zero means that there are no entries in
the table.
|
| bertDDSSeekResultsTableEntry |
.1.3.6.1.4.1.351.110.6.1.27.1 |
|
An entry in the detected DDS codes table.
|
| bertSupportedTestsTableEntry |
.1.3.6.1.4.1.351.110.6.1.28.1 |
|
A general supported tests entry.
|
| bertDDSSeekResultsTableIndex |
.1.3.6.1.4.1.351.110.6.1.27.1.1 |
|
Denotes the serial number of the entry in the table.
|
| bertDDSCode |
.1.3.6.1.4.1.351.110.6.1.27.1.2 |
|
Denotes the type of DDS code detected.
|
| bertSupportedTestsTableIndex |
.1.3.6.1.4.1.351.110.6.1.28.1.1 |
|
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 |
|
'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.
|
| bertTestMediumMask |
.1.3.6.1.4.1.351.110.6.1.28.1.3 |
|
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 |
|
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 |
|
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 |
|
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 |
|
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 |
|
Specifies whether a t1 or e1 card.
|
