Reference record for OID 1.3.6.1.4.1.498.8.6.7.1.3



parent
1.3.6.1.4.1.498.8.6.7.1 (nms510DiagExcEntry)
node code
3
node name
nms510DiagIntDataloop
dot oid
1.3.6.1.4.1.498.8.6.7.1.3
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) gdc(498) dsu(8) nms510(6) nms510DiagExcTable(7) nms510DiagExcEntry(1) nms510DiagIntDataloop(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) gdc(498) dsu(8) nms510(6) nms510DiagExcTable(7) nms510DiagExcEntry(1) nms510DiagIntDataloop(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) gdc(498) dsu(8) nms510(6) nms510DiagExcTable(7) nms510DiagExcEntry(1) nms510DiagIntDataloop(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) gdc(498) dsu(8) nms510(6) nms510DiagExcTable(7) nms510DiagExcEntry(1) nms510DiagIntDataloop(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) gdc(498) dsu(8) nms510(6) nms510DiagExcTable(7) nms510DiagExcEntry(1) nms510DiagIntDataloop(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) gdc(498) dsu(8) nms510(6) nms510DiagExcTable(7) nms510DiagExcEntry(1) nms510DiagIntDataloop(3)}
  • iri oid
  • /iso/identified-organization/dod/internet/private/enterprise/gdc/dsu/nms510/nms510DiagExcTable/nms510DiagExcEntry/nms510DiagIntDataloop
  • /iso/identified-organization/dod/internet/private/enterprises/gdc/dsu/nms510/nms510DiagExcTable/nms510DiagExcEntry/nms510DiagIntDataloop
  • /iso/org/dod/internet/private/enterprise/gdc/dsu/nms510/nms510DiagExcTable/nms510DiagExcEntry/nms510DiagIntDataloop
  • /iso/org/dod/internet/private/enterprises/gdc/dsu/nms510/nms510DiagExcTable/nms510DiagExcEntry/nms510DiagIntDataloop
  • /iso/iso-identified-organization/dod/internet/private/enterprise/gdc/dsu/nms510/nms510DiagExcTable/nms510DiagExcEntry/nms510DiagIntDataloop
  • /iso/iso-identified-organization/dod/internet/private/enterprises/gdc/dsu/nms510/nms510DiagExcTable/nms510DiagExcEntry/nms510DiagIntDataloop
  • iri by oid_info
    /ISO/Identified-Organization/6/1/4/1/498/8/6/7/1/3

    Description by mibdepot

    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.

    Parsed from file nms510.mib.txt
    Company: None
    Module: NMS510-MIB

    Description by circitor

    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.

    Parsed from file NMS510-MIB.mib
    Module: NMS510-MIB

    Information by mibdepot

    nms510DiagIntDataloop OBJECT-TYPE SYNTAX INTEGER { dataloopOff(1), dataloopOn(2), blocks1(3), blocks10(4), blocks100(5), blocks500(6), blocks1000(7), blocks5000(8), blocks10000(9), blocks50000(10) } ACCESS read-write STATUS mandatory 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. " ::= { nms510DiagExcEntry 3 }

    Information by oid_info

    Vendor: General DataComm, Inc.
    Module: NMS510-MIB

    [Automatically extracted from oidview.com]

    Information by circitor

    nms510DiagIntDataloop OBJECT-TYPE SYNTAX INTEGER { dataloopOff(1), dataloopOn(2), blocks1(3), blocks10(4), blocks100(5), blocks500(6), blocks1000(7), blocks5000(8), blocks10000(9), blocks50000(10) } ACCESS read-write STATUS mandatory 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. " ::= { nms510DiagExcEntry 3 }

    First Registration Authority (recovered by parent 1.3.6.1.4.1.498)

    Meltzer William

    Brothers (6)

    OIDNameSub childrenSub Nodes TotalDescription
    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.2 nms510DiagIntLineloop 0 0 Lineloop (or Analoop) can be either a Bilaterial or Unilaterial
    loopback depending on option ddsDteTermaloop. To initiate a
    Line…
    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…