CISCO-WAN-SRM-BERT-MIB

OBJECT-IDENTITY

OBJECT-TYPE

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.

OBJECT-TYPE

All of bert resources can be used by only one user at a time. This gives the status of the resources.

OBJECT-TYPE

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.

OBJECT-TYPE

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.

OBJECT-TYPE

This variable provides the status of BERT in the shelf.

OBJECT-TYPE

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.

OBJECT-TYPE

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.

OBJECT-TYPE

specifies the port number for BERT.

OBJECT-TYPE

specifies the line number for BERT. If the test medium is port, this represents the line to which the port belongs.

OBJECT-TYPE

specifies the mode, the BERT module is to be configured for.

OBJECT-TYPE

This shows the type of the end device and the type of the loopback used (latching/nonlatching/polynomial).

OBJECT-TYPE

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.

OBJECT-TYPE

This variable determines BERT pattern to be transmitted.

OBJECT-TYPE

specifies the type of loopback to be (d)established.

OBJECT-TYPE

specifies the operation of loopback (up or down).

OBJECT-TYPE

represents the ds0 speed of the test running.

OBJECT-TYPE

represents the number of ds0s in the test medium chosen.

OBJECT-TYPE

The syntax is hh:mm:ss The time zone is as configured in the shelf.

OBJECT-TYPE

On MGX 8220, the syntax is mm/dd/yy On MGX 8850, the syntax is mm/dd/yyyy.

OBJECT-TYPE

This shows the number of bits transmitted.

OBJECT-TYPE

This shows the number of bits received in error.

OBJECT-TYPE

This shows the number of times error was injected.

OBJECT-TYPE

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.

OBJECT-TYPE

when the BERT is aborted, this object would give the reason for that.

OBJECT-TYPE

Denotes the index of the oldest entry in the table. A value of zero means that there are no entries in the table.

OBJECT-TYPE

Denotes the index of the latest entry in the table. A value of zero means that there are no entries in the table.

OBJECT-TYPE

This table contains all available DDS patterns detected and latched by an interaface(lines,ports etc) configured to detect DDS patterns.

OBJECT-TYPE

An entry in the detected DDS codes table.

OBJECT-TYPE

Denotes the serial number of the entry in the table.

OBJECT-TYPE

Denotes the type of DDS code detected.

OBJECT-TYPE

A list of supported tests for a given SM.

OBJECT-TYPE

A general supported tests entry.

OBJECT-TYPE

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.

OBJECT-TYPE

'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.

OBJECT-TYPE

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.

OBJECT-TYPE

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.

OBJECT-TYPE

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.

OBJECT-TYPE

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.

OBJECT-TYPE

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.

OBJECT-TYPE

Specifies whether a t1 or e1 card.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY