NMS520-MIB: View SNMP OID List / Download MIB

Identifies the version of the MIB. The format of the version is x.yzT, where 'x' identifies the major revision number, 'y' identifies the minor revision number, 'z' identifies the typographical revision, and T identifies the test revision. Acceptable values for the individual revision components are as follows: x: 1 - 9 y: 0 - 9 z: 0 - 9 T: A - Z Upon formal release, no designation for the test revision will be present.

The NMS520 Unit Configuration table. This table augments the GDC SC5520 Unit Configuration table, providing unit level configuration for each NMS520 device installed. For each entry in the GDC SC Unit Configuration table that represents an NMS520, there is a corresponding entry here whereby the value of the gdcSCunitCfgIndex object is equivalent to the value of the nms520unitCfgIndex object.

The NMS520 Unit Configuration table entry. The information in this entry augments the information in the corresponding entry in the GDC SC Unit Configuration table and provides unit level configuration for the installed NMS520.

The index value which uniquely identifies the NMS520 to which this entry is applicable. This has the form of a SCinstance which defines the slot, line, and drop of the NMS520 with no sub-identifier value.

The NMS510 compatibility mode. This mode allows the NMS520 to behave in a manner compatible with that of the NMS510 in a DDSI multipoint circuit. If this object has the value enabled(2), then the device can be used in conjunction with an NMS510. A value of disabled(1) implies that the device is not backwardly compatible with the NMS510. Enumeration: 'disabled': 1, 'enabled': 2.

The Point to point sentry time nms520PtToPtSentryTime, is used to control the amount of time between unsolicited alarm responses from a remote unit in a point to point application when there are no alarm conditions to report. This unsolicited response maintains the management link between the two units. These alarm responses are intrusive to data. The range is from 1 minute to 127 minutes, with 60 minutes being the default value. The value of 0(zero) minutes will disable remote alarm sentry reporting.

The Alarm hysterysis time nms520AlarmHystTime, is used to control the amount of time a remote must wait between reporting unsolicited alarm conditions. A remote will send an unsolicited alarm response at the time of the first alarm. If second alarm occurs the remote will wait for the time specified by this object before it will send another alarm response. This time applies for both point to point and multipoint applications. The range is from 1 second to 127 seconds, with 10 seconds being the default value.

The multipoint remote response interval nms520MtpointRmRspIntrvl, is used to control the amount of time between unsolicited alarm responses from a remote unit in a multipoint applications when there are no alarm conditions to report. This unsolicited response maintains the management link between the two units. The range is from 1 second to 127 seconds with 10 seconds being the default value. The value of 0(zero) seconds is disable remote alarm sentry reporting. All remotes in a multipoint application must be set the same. These alarm responses are non-intrusive to data.

The value auto(3), indicates that the DTE port is automatically being detected, and set. The rs232(1), will force the DTE port to EIA/TIA-232-E, and v35(2), will force the DTE port to V.35. Enumeration: 'auto': 3, 'rs232': 1, 'v35': 2.

RTS/CTS Delay options ctsOn(1) Forces both RTS and CTS On regardless of the state of the attached business equipment (the transmitter is On regardless of the status of the RTS interface lead). MIB object nms520DteCtsDelayExt is ignored. cts0mSec(2) Provides zero bits of delay between active RTS and CTS being set to active. MIB object nms520DteCtsDelayExt must be set to ext0mSec(1). ctsFix3Char(3) Provides three character bits of delay between active RTS and CTS being set to active. MIB object nms520DteCtsDelayExt must be set to ext0mSec(1). Enumeration: 'ctsFixed3Char': 3, 'ctsOn': 1, 'cts0mSec': 2.

RTS/CTS Delay options extension ext0mSec(1) Used to enable options cts0mSec(2) or ctsFix3Char(3) from MIB object nms520DteCtsDelay. ext30mSec(2) Provides 30 msec of delay between active RTS and CTS being set to active. MIB object nms520DteCtsDelay must be set for either cts0mSec(2) or ctsFix3Char(3). ext60mSec(3) Provides 60 msec of delay between active RTS and CTS being set to active. MIB object nms520DteCtsDelay must be set for either cts0mSec(2) or ctsFix3Char(3). ext90mSec(4) Provides 90 msec of delay between active RTS and CTS being set to active. MIB object nms520DteCtsDelay must be set for either cts0mSec(2) or ctsFix3Char(3). Enumeration: 'ext30mSec': 2, 'ext0mSec': 1, 'ext60mSec': 3, 'ext90mSec': 4.

The version number of the firmware, to allow products to know which revision is installed. The released version number is sequenced from --, A-, ... AA, ... ZZ. Test versions are numerical from 01 to 99.

Indicates the data rate at which the management data is sent/received when the gdcNmsManagementSource is daisyChain(4). Enumeration: 'bps75': 1, 'bps9600': 2.

The DDS Alarm Threshold Alarm Interval. It specifies the amount of time in minutes, 1 to 15 minutes, in which the threshold setting is to be exceeded for the alarm to occur. There is one Alarm Interval for all five alarms that require thresholds: nms520JitterAlm, nms520BpvAlm, nms520FrameLossAlm, nms520SignalToNoiseAlm and nms520RxSignalLowAlm.

This object will cause software reset in dataset. Enumeration: 'reset': 2, 'normal': 1.

Inhibits all front panel test switches. If a test switch is activated while inhibited it will simply be ignored. If enabled via the nms520FrontPanelEnable object the test switch will function as normal. Enumeration: 'fpEnabled': 2, 'execute': 3, 'fpInhibited': 1.

Enables all front panel test switches. If a test switch is activated while inhibited, via the nms520FrontPanelInhibit object, it will simply be ignored. If enabled the test switch will function as normal. Enumeration: 'fpEnabled': 2, 'execute': 3, 'fpInhibited': 1.

Primary data invert option. Will enhance the quality of data when network does not provide B8Z5. Primarily used with DDS II 56k Enumeration: 'invert': 2, 'normal': 1.

If set to 2 then either a Data Rate Adadaptor or 530 card is installed. Enumeration: 'installed': 2, 'not-installed': 1.

with IFP(2) means that the unit has a LCD configurable display. single-height(1) means that the unit does NOT have a LCD configurable display. Enumeration: 'withIFP': 2, 'singleHeight': 1.

This option sets the external output state (on/off) of the current network element and displays the external output. Enumeration: 'on': 1, 'off': 2.

This option sets the external output state (on/off) of the current network element and displays the external output. Enumeration: 'on': 1, 'off': 2.

The DDS Line Statistics table.

An entry in the DDS Line Statistics Table.

The DDS Line Statistics Interval. It specifies the amount of time in minutes (1 to 15 minutes) the unit will use to report statistical information. The unit will record statictics every minute and hold that information for 15 minutes. Past statistics can read from 1 to 15 minutes ago. A time must be specified to read any object in the ms520LineStatsTable.

This object will report the status of the line measurements, for the selected period. If noSignal(2), it will indicate that there is no receive signal availible. If notAvailable(3), it will indicate that the measurements have not completed. And if overRange(4), will indicate that the measurements taken are over measument the range. Enumeration: 'notAvailable': 3, 'overRange': 4, 'noSignal': 2, 'normal': 1.

Will report the transmit Level of the line to be 0dB txLevel0dB(1), or 6dB txLevel6dB(2) as measured by the unit X minutes ago (1 to 15 miniutes) as specified by nms520LineStatsInterval. Enumeration: 'txLevel6dB': 2, 'txLevel0dB': 1.

This object will report the receive level measured at X minutes ago (1 to 15 miniutes) as specified by nms520LineStatsInterval. The range is between the -50dB to +6dB.

This object will the report the signal to noise ratio measured X minutes ago(1 to 15 miniutes) as specified by nms520LineStatsInterval. The range is from 0 to 50, for the selected period. The value is absolute.

This object will the report the signal quality of the line measured X minutes ago (1 to 15 miniutes) as specified by nms520LineStatsInterval. Enumeration: 'bad': 3, 'good': 1, 'fair': 2.

This object will the report the percent jitter of the line measured X minutes ago (1 to 15 miniutes) as specified by nms520LineStatsInterval. The range is 0% to 99% Jitter.

This object will the report the number of bipolar violation that have occured over the last X minutes (1 to 15 minutes). The range is from 0 to 99 violations.

This object will the report the numbrt of frame losses that have occured over the last X minutes (1 to 15 minutes). The range is from 0 to 99 frame losses.

The NMS520 Unit Diagonostic table.

The NMS520 Unit Diagonostic table entry.

The index value which uniquely identifies the NMS520 to which this entry is applicable. This has the form of a SCinstance which defines the slot, line, and drop of the NMS520 with no sub-identifier value.

Configures the selftest pattern to be run during any diagonostic test involving selftest. If option SendOtherPattern is selected, then pattern will default to 15 bit if unit is set for 56k-DDS/sc-multi point else pattern will default to 511 bit for all other conditions Enumeration: 'send15BitPattern': 4, 'sendOtherPattern': 1, 'send2047Pattern': 3, 'send511Pattern': 2.

Indicates exceptions that have occurred that may affect interpretation of the test results. The value of this object is a sum. This sum initially take the value zero. Then, for each exception, the value associated with the exception is added to the sum. The exception values are: value exception 0 No errors 1 bit over range 2 block over range 4 bit and block over range Enumeration: 'blocksOutOfRange': 2, 'bitsOutOfRange': 3, 'blocksAndBitsOutOfRange': 4, 'noExceptions': 1.

The bit errors of the last diagnostic test that involved a Selftest pattern. Reading bit errors while a diagnostic test in running will cause the unit to drop out of test and invalidate the bit errors. Bit errors should be read only after the test is completed. The valid range for bit errors is 0 to 1,023, 65535 will be returned if for any reason the test was terminated early.

The block errors of the last diagnostic test that involved a Selftest pattern. Reading block errors while a diagnostic test in running will cause the unit to drop out of test and invalidate the block errors. Block errors should be read only after the test is completed. The valid range for block errors is 0 to 1,023, 65535 will be returned if for any reason the test was terminated early.

This object will halt the execution of any and all diagnostic test that may be running with the exception of the Network Delay Test. Enumeration: 'resetTest': 3, 'diagnostic': 2, 'normal': 1.

This object reads the results of a Network Delay Test. The results are valid only after the test is completed which takes about 10 seconds. The unit for time delay is in miliseconds. The valid range for delay is 0 to 4096, 16383 will be returned if for any reason the test was terminated early. Reading this object while a test is in progress will terminate the test.

The NMS520 Unit Diagonostic table.

The NMS520 Unit Diagonostic table entry.

The index value which uniquely identifies the NMS520 to which this entry is applicable. This has the form of a SCinstance which defines the slot, line, and drop of the NMS520 with no sub-identifier value.

Lineloop (or Analoop) can be either a Bilaterial or Unilaterial loopback depending on option ddsDteTermaloop. To initiate a Lineloop with no Selftest SET this object and specifiy external, this will allow the data from the DTE to looped back to itself. Emun external(3) is write only. The only valid response to a READ is lineloopOn(2) or lineloopOff(1). To halt this test you must SET the nms520DiagTestReset object. Reading test results via the sc5520DiagBitErrors or nms520DiagBlockErrors objects while the test is running will also cause the test to terminate. There are no test results associated with this test. Enumeration: 'lineloopOn': 2, 'lineloopOff': 1, 'external': 3.

Lineloop (or Analoop) can be either a Bilaterial or Unilaterial loopback depending on option ddsDteTermaloop. To initiate a Lineloop with Selftest SET this object and specifiy a blocksize. The blocksize indicates the number of blocks the Selftest pattern generator will run. There are 1000 bits/block. Emuns 3 through 10 are write only. The only valid responses to a READ are lineloopOn(2) or lineloopOff(1). This test will terminate after the specified number of blocks have been run. Reading test results via the nms520DiagBitErrors or nms520DiagBlockErrors objects while the test is running will cause the test to terminate prematurely and render the results invalid. Test results should be only read after the test is completed. The current Test Status can be obtained by reading this object or the nms520DiagTestStatus object on the unit under test. This test can also be terminated by seting the nms520DiagTestReset object. Enumeration: 'lineloopOn': 2, 'blocks500': 6, 'lineloopOff': 1, 'blocks100': 5, 'blocks50000': 10, 'blocks10000': 9, 'blocks1': 3, 'blocks1000': 7, 'blocks5000': 8, 'blocks10': 4.

To initiate a Dataloop with Selftest SET this object and specifiy a blocksize. The nms520 (the remote) unit will go into Dataloop and the master (the sc5520) unit will go into Selftest. The blocksize indicates the number of blocks the Selftest pattern generator will run. There are 1000 bits/block. Emuns 3 through 10 are write only. The only valid responses to a READ are dataloopOn(2) or dataloopOff(1). This test will terminate after the specified number of blocks have been run. Reading test results via the nms520DiagBitErrors or nms520DiagBlockErrors objects while the test is running will cause the test to terminate prematurely and render the results invalid. Test results should be read only after the test is completed and are available from the master (sc5520) unit. The current Test Status can be obtained by reading the sc5520DiagTestStatus object on the master unit, reading test status on the remote unit may interfere with the diagonostic test pattern and cause errors. This test can also be terminated by seting the nms520DiagTestReset object. Enumeration: 'blocks500': 6, 'blocks100': 5, 'blocks50000': 10, 'blocks10000': 9, 'blocks1': 3, 'blocks1000': 7, 'dataloopOff': 1, 'blocks5000': 8, 'blocks10': 4, 'dataloopOn': 2.

To initiate an End to End Selftest(Error Rate Test) SET this object and specifiy a blocksize. Both the remote (nms520) amd master (sc5520) units will go into Selftest. The blocksize indicates the number of blocks the Selftest pattern generator will run. There are 1000 bits/block. Emuns 3 through 10 are write only. The only valid responses to a READ are selftestOn(2) or selftestOff(1). This test will terminate after the specified number of blocks have been run. Reading test results via the nms520DiagBitErrors or nms520DiagBlockErrors objects while the test is running will cause the test to terminate prematurely and render the results invalid. Test results should be read only after the test is completed and are available from both the remote (nms520) and master (sc5520) units. The current Test Status can be obtained by reading the sc5520DiagTestStatus object on the master unit, reading test status on the remote unit may interfere with the diagonostic test patternand cause errors. This test can also be terminated by seting the nms520DiagTestReset object. Enumeration: 'blocks500': 6, 'blocks100': 5, 'blocks50000': 10, 'blocks10000': 9, 'blocks1': 3, 'endToEndOff': 1, 'endToEndOn': 2, 'blocks1000': 7, 'blocks5000': 8, 'blocks10': 4.

To initiate a Network Delay test SET this object and specifiy runDelayTest. Both the remote (nms520) and master (sc5520) units will go into a test to measure network delay. Emun 3 is write only. The only valid responses to a READ are delayTestOn(2) or delatTestOff(1). This test will terminate after 10 seconds. Reading test results via the nms520DelayTime object while the test is running will cause the test to terminate prematurely and render the results invalid. Test results should be read only after the test is completed and are available from the master (sc5520) unit. The current Test Status can be obtained by reading the sc5520DiagTestStatus object on the master unit, reading test status on the remote unit may interfere with the test and cause errors. This test can not be terminated early once it is started. Enumeration: 'runDelayTest': 3, 'delayTestOn': 2, 'delayTestOff': 1.

This object gives the current diagonostic test status. noTest indicates that no diagonostic test is currently active. Reading this object while in a diagonostic test involing two units may interfere with a selftest pattern and invalidate the test results. Reading the sc5520DiagTestStatus (master unit) object during dagonostic tests involing two unit will not disrupt the test results. Enumeration: 'internalLineloop': 2, 'internalDataloop': 4, 'externalDataloop': 3, 'endToend': 6, 'serviceTestCenterLoop': 5, 'noTest': 1.

To initiate a Dataloop test with no Selftest SET this object and specifiy external, this will allow the data from the DTE attached to the far end unit (sc5520) to looped back to itself. Emun external(3) is write only. The only valid response to a READ is dataloopOn(2) or dataloopOff(1). To halt this test you must SET the nms520DiagTestReset object. Reading test results via the nms520DiagBitErrors or nms520DiagBlockErrors objects while the test is running will also cause the test to terminate. There are no test results associated with this test. Reading test status on the remote unit via nms520DiagTestStatus may interfere with the diagonostic test pattern generated from the terminal equiptment. Enumeration: 'dataloopOff': 1, 'external': 3, 'dataloopOn': 2.

The GDC NMS520 Alarm Configuration Table.

An entry in the GDC NMS520 alarm Configuration table.

This object is the index of the NMS520 Alarm Threshold Configuration table.

The unique alarm identifier assigned to this alarm type. The format of this identifier is an OBJECT IDENTIFIER that has the following format: {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) gdc(498) xxx(x) alarm(z) yyy(y) where xxx(x) is the administratively assigned family object identifier (z) is the object identifier for alarms in the family defined MIB and yyy(y) is the administratively assigned alarm type identifier for this alarm.

This function sets/reads the alarm threashold settings criteria. This threshold is used along with the alarm window to determine the number of instances in a given time frame for an alarm to occur before the alarm is considered active. Alarm Table Entry Threshold Range Defaults ------------------ -------------------- -------------- -------- Jitter nms520JitterAlm 0 to 99 % 9 % Bipolar Violations nms520BpvAlm 0 to 99 Count 10 Frame Loss nms520FrameLossAlm 0 to 99 Count 10 Signal to Noise Ratio nms520SignalToNoiseAlm 0 to 50 0 Receive Level Low nms520RxSignalLowAlm -50 to 6 dB -33 dB