All MIBs › NMS510-MIB › nms510DiagIntLineloop
nms510DiagIntLineloop
Module: NMS510-MIB
OID (symbolic): NMS510-MIB::nms510DiagIntLineloop
OID (numeric): 1.3.6.1.4.1.498.8.6.7.1.2
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
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.
What is nms510DiagIntLineloop?
Sets a blocksize (1 to 50000 blocks of 1000 bits each) to start an internal lineloop self-test, or reads back lineloopOn(2)/lineloopOff(1) to check current status; reading the error counters mid-test invalidates the results.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.498.8.6.7.1.2 snmpwalk -v2c -c public <target> NMS510-MIB::nms510DiagIntLineloop
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.498.8.6.7.1.2.1 snmpget -v2c -c public <target> NMS510-MIB::nms510DiagIntLineloop.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.498.8.6.7.1.2.1 i <value>
Start monitoring NMS Communications NMS510 device (DSU/CSU or similar telecom line unit) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the NMS510-MIB::nms510DiagIntLineloop OID value, configure state conditions and alerts, and monitor any NMS Communications NMS510 device (DSU/CSU or similar telecom line unit) from a single console.
OID Breakdown
Upper-level ancestors (8 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.4 | private | AirPair-MIB |
| 1.3.6.1.4.1 | enterprises | AirPair-MIB |
| 1.3.6.1.4.1.498 | gdc | DMA200-MIB |
| 1.3.6.1.4.1.498.8 | dsu | DDS-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.4.1.498.8.6 | nms510 | NMS510-MIB |
| 1.3.6.1.4.1.498.8.6.7 | nms510DiagExcTable | NMS510-MIB |
| 1.3.6.1.4.1.498.8.6.7.1 | nms510DiagExcEntry | NMS510-MIB |
| 1.3.6.1.4.1.498.8.6.7.1.2 | nms510DiagIntLineloop | NMS510-MIB |