OID reference

arrisNpmSetupNetLatencyTestRunTime

1.3.6.1.4.1.4115.1.3.13.4.2

Description

This MIB indicates to the modem to run the Network Latency test. The supplied time is used as a countdown timer, indicating the number of seconds to wait before running the test. A value of 0 means run immediately. The test results for the Network Latency Test are made available once the test has completed. Given that…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.4115.1.3.13.4 (arrisNpmNetLatencyTest)
Node code
2
Node name
arrisNpmSetupNetLatencyTestRunTime
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.4115.1.3.13.4.2
URN notation
urn:oid:1.3.6.1.4.1.4115.1.3.13.4.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 4115 1 3 13 4 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisNetPerfMonitorMib(13) arrisNpmNetLatencyTest(4) arrisNpmSetupNetLatencyTestRunTime(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisNetPerfMonitorMib(13) arrisNpmNetLatencyTest(4) arrisNpmSetupNetLatencyTestRunTime(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisNetPerfMonitorMib(13) arrisNpmNetLatencyTest(4) arrisNpmSetupNetLatencyTestRunTime(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisNetPerfMonitorMib(13) arrisNpmNetLatencyTest(4) arrisNpmSetupNetLatencyTestRunTime(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisNetPerfMonitorMib(13) arrisNpmNetLatencyTest(4) arrisNpmSetupNetLatencyTestRunTime(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisNetPerfMonitorMib(13) arrisNpmNetLatencyTest(4) arrisNpmSetupNetLatencyTestRunTime(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisNetPerfMonitorMib(13) arrisNpmNetLatencyTest(4) arrisNpmSetupNetLatencyTestRunTime(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisNetPerfMonitorMib(13) arrisNpmNetLatencyTest(4) arrisNpmSetupNetLatencyTestRunTime(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisNetPerfMonitorMib(13) arrisNpmNetLatencyTest(4) arrisNpmSetupNetLatencyTestRunTime(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisNetPerfMonitorMib(13) arrisNpmNetLatencyTest(4) arrisNpmSetupNetLatencyTestRunTime(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisNetPerfMonitorMib(13) arrisNpmNetLatencyTest(4) arrisNpmSetupNetLatencyTestRunTime(2)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisNetPerfMonitorMib(13) arrisNpmNetLatencyTest(4) arrisNpmSetupNetLatencyTestRunTime(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisNetPerfMonitorMib(13) arrisNpmNetLatencyTest(4) arrisNpmSetupNetLatencyTestRunTime(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisNetPerfMonitorMib(13) arrisNpmNetLatencyTest(4) arrisNpmSetupNetLatencyTestRunTime(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisNetPerfMonitorMib(13) arrisNpmNetLatencyTest(4) arrisNpmSetupNetLatencyTestRunTime(2)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) arris(4115) arrisProducts(1) arrisProdIdCM(3) arrisNetPerfMonitorMib(13) arrisNpmNetLatencyTest(4) arrisNpmSetupNetLatencyTestRunTime(2)}
OID-IRI notation
  • /1/3/6/1/4/1/4115/1/3/13/4/2
  • /ISO/Identified-Organization/6/1/4/1/4115/1/3/13/4/2
  • /ISO/3/6/1/4/1/4115/1/3/13/4/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/4115/arrisProducts/arrisProdIdCM/arrisNetPerfMonitorMib/arrisNpmNetLatencyTest/arrisNpmSetupNetLatencyTestRunTime
  • /iso/identified-organization/dod/internet/private/enterprise/arris/arrisProducts/arrisProdIdCM/arrisNetPerfMonitorMib/arrisNpmNetLatencyTest/arrisNpmSetupNetLatencyTestRunTime
  • /iso/identified-organization/dod/internet/private/enterprises/4115/arrisProducts/arrisProdIdCM/arrisNetPerfMonitorMib/arrisNpmNetLatencyTest/arrisNpmSetupNetLatencyTestRunTime
  • /iso/identified-organization/dod/internet/private/enterprises/arris/arrisProducts/arrisProdIdCM/arrisNetPerfMonitorMib/arrisNpmNetLatencyTest/arrisNpmSetupNetLatencyTestRunTime
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/4115/arrisProducts/arrisProdIdCM/arrisNetPerfMonitorMib/arrisNpmNetLatencyTest/arrisNpmSetupNetLatencyTestRunTime
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/arris/arrisProducts/arrisProdIdCM/arrisNetPerfMonitorMib/arrisNpmNetLatencyTest/arrisNpmSetupNetLatencyTestRunTime
  • /iso/identified-organization/dod/internet/private/vendor-objects/4115/arrisProducts/arrisProdIdCM/arrisNetPerfMonitorMib/arrisNpmNetLatencyTest/arrisNpmSetupNetLatencyTestRunTime
  • /iso/identified-organization/dod/internet/private/vendor-objects/arris/arrisProducts/arrisProdIdCM/arrisNetPerfMonitorMib/arrisNpmNetLatencyTest/arrisNpmSetupNetLatencyTestRunTime
  • /iso/org/dod/internet/private/enterprise/4115/arrisProducts/arrisProdIdCM/arrisNetPerfMonitorMib/arrisNpmNetLatencyTest/arrisNpmSetupNetLatencyTestRunTime
  • /iso/org/dod/internet/private/enterprise/arris/arrisProducts/arrisProdIdCM/arrisNetPerfMonitorMib/arrisNpmNetLatencyTest/arrisNpmSetupNetLatencyTestRunTime
  • /iso/org/dod/internet/private/enterprises/4115/arrisProducts/arrisProdIdCM/arrisNetPerfMonitorMib/arrisNpmNetLatencyTest/arrisNpmSetupNetLatencyTestRunTime
  • /iso/org/dod/internet/private/enterprises/arris/arrisProducts/arrisProdIdCM/arrisNetPerfMonitorMib/arrisNpmNetLatencyTest/arrisNpmSetupNetLatencyTestRunTime
  • /iso/org/dod/internet/private/ldap-enterprise/4115/arrisProducts/arrisProdIdCM/arrisNetPerfMonitorMib/arrisNpmNetLatencyTest/arrisNpmSetupNetLatencyTestRunTime
  • /iso/org/dod/internet/private/ldap-enterprise/arris/arrisProducts/arrisProdIdCM/arrisNetPerfMonitorMib/arrisNpmNetLatencyTest/arrisNpmSetupNetLatencyTestRunTime
  • /iso/org/dod/internet/private/vendor-objects/4115/arrisProducts/arrisProdIdCM/arrisNetPerfMonitorMib/arrisNpmNetLatencyTest/arrisNpmSetupNetLatencyTestRunTime
  • /iso/org/dod/internet/private/vendor-objects/arris/arrisProducts/arrisProdIdCM/arrisNetPerfMonitorMib/arrisNpmNetLatencyTest/arrisNpmSetupNetLatencyTestRunTime
  • Additional combinations skipped.

SNMP properties

Value type
Unsigned32
Units
Seconds
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
0
Allowed ranges
0–4294967295

Using this OID with SNMP

At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.

snmpget [connection options] DEVICE .1.3.6.1.4.1.4115.1.3.13.4.2.0

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

arrisNpmSetupNetLatencyTestRunTime OBJECT-TYPE
    SYNTAX Unsigned32 (0..4294967295)
    UNITS "Seconds"
    MAX-ACCESS read-write
    STATUS current
    DESCRIPTION
        "This MIB indicates to the modem to run the Network Latency test. The
         supplied time is used as a countdown timer, indicating the number of 
         seconds to wait before running the test. A value of 0 means run 
         immediately. The test results for the Network Latency Test are
         made available once the test has completed. Given that there can 
         be multiple test servers configured for this test, the SNMP manager 
         should wait for at least 5 minutes before attempting to retrieve the
         test results.
 
         If arrisNpmSetupNetLatencyRunUnderLoadEnable is enabled, then setting
         this MIB will not result in a test being run, as the tests are tied
         into the operation of the Web Page Download test.
   
         The Network Latency test relies on test serveres being configured 
         within the arrisNpmSetupNetLatencyServerTable. The test will not run
         if there are no entries present in that table. 

         For every server configured in that table, the CM is required to issue
         a UDP ping request and measure the time it takes to transmit and 
         receive the UDP ping response. If the 
         arrisNpmSetupNetLatencyTestPingCount has been modified then the CM 
         must repeat the UDP ping requests that number of times. The CM must 
         wait arrisNpmSetupNetLatencyTestPingInterval between UDP Ping requests.

         When performing multiple UDP Ping requests in a row, the CM must 
         maintain statistics related to the network performance of each 
         configured test server. These statistics include minimum, maximum,
         mean, mode and standard deviation, along with successful and failed
         ping attempts. All failed UDP Ping requests are excluded from the 
         generation of statisctics. A failed UDP Ping request occurs when the
         UDP Ping response is not received back from the remote server within 
         arrisNpmSetupNetLatencyTestPingTimeout seconds. " 
    DEFVAL { 0 }
    ::= { arrisNpmNetLatencyTest 2 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

This MIB indicates to the modem to run the Network Latency test. The supplied time is used as a countdown timer, indicating the number of seconds to wait before running the test. A value of 0 means run immediately. The test results for the Network Latency Test are made available once the test has completed. Given that there can be multiple test servers configured for this test, the SNMP manager should wait for at least 5 minutes before attempting to retrieve the test results. If arrisNpmSetupNetLatencyRunUnderLoadEnable is enabled, then setting this MIB will not result in a test being run, as the tests are tied into the operation of the Web Page Download test. The Network Latency test relies on test serveres being configured within the arrisNpmSetupNetLatencyServerTable. The test will not run if there are no entries present in that table. For every server configured in that table, the CM is required to issue a UDP ping request and measure the time it takes to transmit and receive the UDP ping response. If the arrisNpmSetupNetLatencyTestPingCount has been modified then the CM must repeat the UDP ping requests that number of times. The CM must wait arrisNpmSetupNetLatencyTestPingInterval between UDP Ping requests. When performing multiple UDP Ping requests in a row, the CM must maintain statistics related to the network performance of each configured test server. These statistics include minimum, maximum, mean, mode and standard deviation, along with successful and failed ping attempts. All failed UDP Ping requests are excluded from the generation of statisctics. A failed UDP Ping request occurs when the UDP Ping response is not received back from the remote server within arrisNpmSetupNetLatencyTestPingTimeout seconds.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

arrisNpmSetupNetLatencyTestRunTime · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: arrisNpmSetupNetLatencyTestRunTime

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "arrisNpmSetupNetLatencyTestRunTime",
    "OBJECT-TYPE",
    "SYNTAX",
    "Unsigned32",
    "(",
    "0",
    ".",
    ".",
    "4294967295",
    ")",
    "UNITS",
    [
      "literal",
      "225365636f6e647322"
    ],
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This MIB indicates to the modem to run the Network Latency test. The supplied time is used as a countdown timer, indicating the number of seconds to wait before running the test. A value of 0 means run immediately. The test results for the Network Latency Test are made available once the test has completed. Given that there can be multiple test servers configured for this test, the SNMP manager should wait for at least 5 minutes before attempting to retrieve the test results. If arrisNpmSetupNetLatencyRunUnderLoadEnable is enabled, then setting this MIB will not result in a test being run, as the tests are tied into the operation of the Web Page Download test. The Network Latency test relies on test serveres being configured within the arrisNpmSetupNetLatencyServerTable. The test will not run if there are no entries present in that table. For every server configured in that table, the CM is required to issue a UDP ping request and measure the time it takes to transmit and receive the UDP ping response. If the arrisNpmSetupNetLatencyTestPingCount has been modified then the CM must repeat the UDP ping requests that number of times. The CM must wait arrisNpmSetupNetLatencyTestPingInterval between UDP Ping requests. When performing multiple UDP Ping requests in a row, the CM must maintain statistics related to the network performance of each configured test server. These statistics include minimum, maximum, mean, mode and standard deviation, along with successful and failed ping attempts. All failed UDP Ping requests are excluded from the generation of statisctics. A failed UDP Ping request occurs when the UDP Ping response is not received back from the remote server within arrisNpmSetupNetLatencyTestPingTimeout seconds. \"",
    "DEFVAL",
    "{",
    "0",
    "}",
    "::=",
    "{",
    "arrisNpmNetLatencyTest",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Unsigned32",
      [
        "integerSubType",
        [
          [
            0,
            4294967295
          ]
        ]
      ]
    ],
    [
      "UNITS",
      "Seconds"
    ],
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This MIB indicates to the modem to run the Network Latency test. The supplied time is used as a countdown timer, indicating the number of seconds to wait before running the test. A value of 0 means run immediately. The test results for the Network Latency Test are made available once the test has completed. Given that there can be multiple test servers configured for this test, the SNMP manager should wait for at least 5 minutes before attempting to retrieve the test results. If arrisNpmSetupNetLatencyRunUnderLoadEnable is enabled, then setting this MIB will not result in a test being run, as the tests are tied into the operation of the Web Page Download test. The Network Latency test relies on test serveres being configured within the arrisNpmSetupNetLatencyServerTable. The test will not run if there are no entries present in that table. For every server configured in that table, the CM is required to issue a UDP ping request and measure the time it takes to transmit and receive the UDP ping response. If the arrisNpmSetupNetLatencyTestPingCount has been modified then the CM must repeat the UDP ping requests that number of times. The CM must wait arrisNpmSetupNetLatencyTestPingInterval between UDP Ping requests. When performing multiple UDP Ping requests in a row, the CM must maintain statistics related to the network performance of each configured test server. These statistics include minimum, maximum, mean, mode and standard deviation, along with successful and failed ping attempts. All failed UDP Ping requests are excluded from the generation of statisctics. A failed UDP Ping request occurs when the UDP Ping response is not received back from the remote server within arrisNpmSetupNetLatencyTestPingTimeout seconds."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      0
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.4115)

Wynn Robert

Siblings (6)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.4115.1.3.13.4.1 arrisNpmSetupNetLatencyTestRunUnderLoadEnable00
1.3.6.1.4.1.4115.1.3.13.4.3 arrisNpmSetupNetLatencyTestPingCount00
1.3.6.1.4.1.4115.1.3.13.4.4 arrisNpmSetupNetLatencyTestPingInterval00
1.3.6.1.4.1.4115.1.3.13.4.5 arrisNpmSetupNetLatencyTestPingTimeout00
1.3.6.1.4.1.4115.1.3.13.4.6 arrisNpmSetupNetLatencyServerTable15
1.3.6.1.4.1.4115.1.3.13.4.7 arrisNpmResultNetLatencyTestTable12