All MIBs › NMS510-MIB › nms510DiagIntDataloop
nms510DiagIntDataloop
Module: NMS510-MIB
OID (symbolic): NMS510-MIB::nms510DiagIntDataloop
OID (numeric): 1.3.6.1.4.1.498.8.6.7.1.3
Node type: OBJECT-TYPE
Type: INTEGER
Access: read-write
Description: To initiate a Dataloop with Selftest SET this object and specifiy a blocksize. The nms510 (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 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 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 nms510DiagTestReset object.
What is nms510DiagIntDataloop?
Sets a blocksize (1 to 50000 blocks) to start an internal dataloop self-test between this remote unit and the master, or reads back dataloopOn(2)/dataloopOff(1); results are read from the master unit once the test completes.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.4.1.498.8.6.7.1.3 snmpwalk -v2c -c public <target> NMS510-MIB::nms510DiagIntDataloop
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.4.1.498.8.6.7.1.3.1 snmpget -v2c -c public <target> NMS510-MIB::nms510DiagIntDataloop.1
Set instance 1 (SNMPv2c):
snmpset -v2c -c private <target> 1.3.6.1.4.1.498.8.6.7.1.3.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::nms510DiagIntDataloop 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.3 | nms510DiagIntDataloop | NMS510-MIB |