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 nms510DiagBitErrors or nms510DiagBlockErrors
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
nms510DiagTestStatus object on the unit under test. This test can
also be terminated by seting the nms510DiagTestReset object.
Parsed from file nms510.mib.txt
Company: None
Module: NMS510-MIB
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 nms510DiagBitErrors or nms510DiagBlockErrors
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
nms510DiagTestStatus object on the unit under test. This test can
also be terminated by seting the nms510DiagTestReset object.
Parsed from file NMS510-MIB.mib
Module: NMS510-MIB
nms510DiagIntLineloop OBJECT-TYPE SYNTAX INTEGER { lineloopOff(1), lineloopOn(2), blocks1(3), blocks10(4), blocks100(5), blocks500(6), blocks1000(7), blocks5000(8), blocks10000(9), blocks50000(10) } ACCESS read-write STATUS mandatory DESCRIPTION "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 nms510DiagBitErrors or nms510DiagBlockErrors 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 nms510DiagTestStatus object on the unit under test. This test can also be terminated by seting the nms510DiagTestReset object. " ::= { nms510DiagExcEntry 2 }
Vendor: General DataComm, Inc.
Module: NMS510-MIB
[Automatically extracted from oidview.com]
nms510DiagIntLineloop OBJECT-TYPE SYNTAX INTEGER { lineloopOff(1), lineloopOn(2), blocks1(3), blocks10(4), blocks100(5), blocks500(6), blocks1000(7), blocks5000(8), blocks10000(9), blocks50000(10) } ACCESS read-write STATUS mandatory DESCRIPTION "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 nms510DiagBitErrors or nms510DiagBlockErrors 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 nms510DiagTestStatus object on the unit under test. This test can also be terminated by seting the nms510DiagTestReset object. " ::= { nms510DiagExcEntry 2 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.498.8.6.7.1.1 | nms510DiagExcIndex | 0 | 0 | The index value which uniquely identifies the NMS510 to which this entry is applicable. This has the form of a SCinstance which … |
| 1.3.6.1.4.1.498.8.6.7.1.3 | nms510DiagIntDataloop | 0 | 0 | To initiate a Dataloop with Selftest SET this object and specifiy a blocksize. The nms510 (the remote) unit will go into Dataloo… |
| 1.3.6.1.4.1.498.8.6.7.1.4 | nms510DiagEndToEndSelftest | 0 | 0 | To initiate an End to End Selftest(Error Rate Test) SET this object and specifiy a blocksize. Both the remote (nms510) amd maste… |
| 1.3.6.1.4.1.498.8.6.7.1.5 | nms510DiagNetworkDelay | 0 | 0 | To initiate a Network Delay test SET this object and specifiy runDelayTest. Both the remote (nms510) and master (sc5520) units w… |
| 1.3.6.1.4.1.498.8.6.7.1.6 | nms510DiagTestStatus | 0 | 0 | This object gives the current diagonostic test status. noTest indicates that no diagonostic test is currently active. Reading thi… |
| 1.3.6.1.4.1.498.8.6.7.1.7 | nms510DiagExtDataloop | 0 | 0 | To initiate a Dataloop test with no Selftest SET this object and specifiy external, this will allow the data from the DTE attach… |