Reference record for OID 1.3.6.1.4.1.4491.2.1.37.1.1.4.1.4

Parent
1.3.6.1.4.1.4491.2.1.37.1.1.4.1 (docsLeakDetTestChannelStatusEntry)
Node code
4
Node name
docsLeakDetTestChannelStatusNumModemsCfg
Numeric OID
1.3.6.1.4.1.4491.2.1.37.1.1.4.1.4
URN notation
urn:oid:1.3.6.1.4.1.4491.2.1.37.1.1.4.1.4
ASN.1 notation

{1 3 6 1 4 1 4491 2 1 37 1 1 4 1 4}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cableLabs(4491) clabProject(2) clabProjDocsis(1) docsLeakDetectMib(37) docsLeakDetObjects(1) docsLeakDetTestObjects(1) docsLeakDetTestChannelStatusTable(4) docsLeakDetTestChannelStatusEntry(1) docsLeakDetTestChannelStatusNumModemsCfg(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) cable-Television-Laboratories-Inc(4491) clabProject(2) clabProjDocsis(1) docsLeakDetectMib(37) docsLeakDetObjects(1) docsLeakDetTestObjects(1) docsLeakDetTestChannelStatusTable(4) docsLeakDetTestChannelStatusEntry(1) docsLeakDetTestChannelStatusNumModemsCfg(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cableLabs(4491) clabProject(2) clabProjDocsis(1) docsLeakDetectMib(37) docsLeakDetObjects(1) docsLeakDetTestObjects(1) docsLeakDetTestChannelStatusTable(4) docsLeakDetTestChannelStatusEntry(1) docsLeakDetTestChannelStatusNumModemsCfg(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) cable-Television-Laboratories-Inc(4491) clabProject(2) clabProjDocsis(1) docsLeakDetectMib(37) docsLeakDetObjects(1) docsLeakDetTestObjects(1) docsLeakDetTestChannelStatusTable(4) docsLeakDetTestChannelStatusEntry(1) docsLeakDetTestChannelStatusNumModemsCfg(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cableLabs(4491) clabProject(2) clabProjDocsis(1) docsLeakDetectMib(37) docsLeakDetObjects(1) docsLeakDetTestObjects(1) docsLeakDetTestChannelStatusTable(4) docsLeakDetTestChannelStatusEntry(1) docsLeakDetTestChannelStatusNumModemsCfg(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) cable-Television-Laboratories-Inc(4491) clabProject(2) clabProjDocsis(1) docsLeakDetectMib(37) docsLeakDetObjects(1) docsLeakDetTestObjects(1) docsLeakDetTestChannelStatusTable(4) docsLeakDetTestChannelStatusEntry(1) docsLeakDetTestChannelStatusNumModemsCfg(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cableLabs(4491) clabProject(2) clabProjDocsis(1) docsLeakDetectMib(37) docsLeakDetObjects(1) docsLeakDetTestObjects(1) docsLeakDetTestChannelStatusTable(4) docsLeakDetTestChannelStatusEntry(1) docsLeakDetTestChannelStatusNumModemsCfg(4)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) cable-Television-Laboratories-Inc(4491) clabProject(2) clabProjDocsis(1) docsLeakDetectMib(37) docsLeakDetObjects(1) docsLeakDetTestObjects(1) docsLeakDetTestChannelStatusTable(4) docsLeakDetTestChannelStatusEntry(1) docsLeakDetTestChannelStatusNumModemsCfg(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cableLabs(4491) clabProject(2) clabProjDocsis(1) docsLeakDetectMib(37) docsLeakDetObjects(1) docsLeakDetTestObjects(1) docsLeakDetTestChannelStatusTable(4) docsLeakDetTestChannelStatusEntry(1) docsLeakDetTestChannelStatusNumModemsCfg(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) cable-Television-Laboratories-Inc(4491) clabProject(2) clabProjDocsis(1) docsLeakDetectMib(37) docsLeakDetObjects(1) docsLeakDetTestObjects(1) docsLeakDetTestChannelStatusTable(4) docsLeakDetTestChannelStatusEntry(1) docsLeakDetTestChannelStatusNumModemsCfg(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cableLabs(4491) clabProject(2) clabProjDocsis(1) docsLeakDetectMib(37) docsLeakDetObjects(1) docsLeakDetTestObjects(1) docsLeakDetTestChannelStatusTable(4) docsLeakDetTestChannelStatusEntry(1) docsLeakDetTestChannelStatusNumModemsCfg(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) cable-Television-Laboratories-Inc(4491) clabProject(2) clabProjDocsis(1) docsLeakDetectMib(37) docsLeakDetObjects(1) docsLeakDetTestObjects(1) docsLeakDetTestChannelStatusTable(4) docsLeakDetTestChannelStatusEntry(1) docsLeakDetTestChannelStatusNumModemsCfg(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) cableLabs(4491) clabProject(2) clabProjDocsis(1) docsLeakDetectMib(37) docsLeakDetObjects(1) docsLeakDetTestObjects(1) docsLeakDetTestChannelStatusTable(4) docsLeakDetTestChannelStatusEntry(1) docsLeakDetTestChannelStatusNumModemsCfg(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) cable-Television-Laboratories-Inc(4491) clabProject(2) clabProjDocsis(1) docsLeakDetectMib(37) docsLeakDetObjects(1) docsLeakDetTestObjects(1) docsLeakDetTestChannelStatusTable(4) docsLeakDetTestChannelStatusEntry(1) docsLeakDetTestChannelStatusNumModemsCfg(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) cableLabs(4491) clabProject(2) clabProjDocsis(1) docsLeakDetectMib(37) docsLeakDetObjects(1) docsLeakDetTestObjects(1) docsLeakDetTestChannelStatusTable(4) docsLeakDetTestChannelStatusEntry(1) docsLeakDetTestChannelStatusNumModemsCfg(4)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) cable-Television-Laboratories-Inc(4491) clabProject(2) clabProjDocsis(1) docsLeakDetectMib(37) docsLeakDetObjects(1) docsLeakDetTestObjects(1) docsLeakDetTestChannelStatusTable(4) docsLeakDetTestChannelStatusEntry(1) docsLeakDetTestChannelStatusNumModemsCfg(4)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/4491/2/1/37/1/1/4/1/4
  • /ISO/Identified-Organization/6/1/4/1/4491/2/1/37/1/1/4/1/4
  • /ISO/3/6/1/4/1/4491/2/1/37/1/1/4/1/4
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/cableLabs/clabProject/clabProjDocsis/docsLeakDetectMib/docsLeakDetObjects/docsLeakDetTestObjects/docsLeakDetTestChannelStatusTable/docsLeakDetTestChannelStatusEntry/docsLeakDetTestChannelStatusNumModemsCfg
  • /iso/identified-organization/dod/internet/private/enterprise/cable-Television-Laboratories-Inc/clabProject/clabProjDocsis/docsLeakDetectMib/docsLeakDetObjects/docsLeakDetTestObjects/docsLeakDetTestChannelStatusTable/docsLeakDetTestChannelStatusEntry/docsLeakDetTestChannelStatusNumModemsCfg
  • /iso/identified-organization/dod/internet/private/enterprises/cableLabs/clabProject/clabProjDocsis/docsLeakDetectMib/docsLeakDetObjects/docsLeakDetTestObjects/docsLeakDetTestChannelStatusTable/docsLeakDetTestChannelStatusEntry/docsLeakDetTestChannelStatusNumModemsCfg
  • /iso/identified-organization/dod/internet/private/enterprises/cable-Television-Laboratories-Inc/clabProject/clabProjDocsis/docsLeakDetectMib/docsLeakDetObjects/docsLeakDetTestObjects/docsLeakDetTestChannelStatusTable/docsLeakDetTestChannelStatusEntry/docsLeakDetTestChannelStatusNumModemsCfg
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/cableLabs/clabProject/clabProjDocsis/docsLeakDetectMib/docsLeakDetObjects/docsLeakDetTestObjects/docsLeakDetTestChannelStatusTable/docsLeakDetTestChannelStatusEntry/docsLeakDetTestChannelStatusNumModemsCfg
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/cable-Television-Laboratories-Inc/clabProject/clabProjDocsis/docsLeakDetectMib/docsLeakDetObjects/docsLeakDetTestObjects/docsLeakDetTestChannelStatusTable/docsLeakDetTestChannelStatusEntry/docsLeakDetTestChannelStatusNumModemsCfg
  • /iso/identified-organization/dod/internet/private/vendor-objects/cableLabs/clabProject/clabProjDocsis/docsLeakDetectMib/docsLeakDetObjects/docsLeakDetTestObjects/docsLeakDetTestChannelStatusTable/docsLeakDetTestChannelStatusEntry/docsLeakDetTestChannelStatusNumModemsCfg
  • /iso/identified-organization/dod/internet/private/vendor-objects/cable-Television-Laboratories-Inc/clabProject/clabProjDocsis/docsLeakDetectMib/docsLeakDetObjects/docsLeakDetTestObjects/docsLeakDetTestChannelStatusTable/docsLeakDetTestChannelStatusEntry/docsLeakDetTestChannelStatusNumModemsCfg
  • /iso/org/dod/internet/private/enterprise/cableLabs/clabProject/clabProjDocsis/docsLeakDetectMib/docsLeakDetObjects/docsLeakDetTestObjects/docsLeakDetTestChannelStatusTable/docsLeakDetTestChannelStatusEntry/docsLeakDetTestChannelStatusNumModemsCfg
  • /iso/org/dod/internet/private/enterprise/cable-Television-Laboratories-Inc/clabProject/clabProjDocsis/docsLeakDetectMib/docsLeakDetObjects/docsLeakDetTestObjects/docsLeakDetTestChannelStatusTable/docsLeakDetTestChannelStatusEntry/docsLeakDetTestChannelStatusNumModemsCfg
  • /iso/org/dod/internet/private/enterprises/cableLabs/clabProject/clabProjDocsis/docsLeakDetectMib/docsLeakDetObjects/docsLeakDetTestObjects/docsLeakDetTestChannelStatusTable/docsLeakDetTestChannelStatusEntry/docsLeakDetTestChannelStatusNumModemsCfg
  • /iso/org/dod/internet/private/enterprises/cable-Television-Laboratories-Inc/clabProject/clabProjDocsis/docsLeakDetectMib/docsLeakDetObjects/docsLeakDetTestObjects/docsLeakDetTestChannelStatusTable/docsLeakDetTestChannelStatusEntry/docsLeakDetTestChannelStatusNumModemsCfg
  • /iso/org/dod/internet/private/ldap-enterprise/cableLabs/clabProject/clabProjDocsis/docsLeakDetectMib/docsLeakDetObjects/docsLeakDetTestObjects/docsLeakDetTestChannelStatusTable/docsLeakDetTestChannelStatusEntry/docsLeakDetTestChannelStatusNumModemsCfg
  • /iso/org/dod/internet/private/ldap-enterprise/cable-Television-Laboratories-Inc/clabProject/clabProjDocsis/docsLeakDetectMib/docsLeakDetObjects/docsLeakDetTestObjects/docsLeakDetTestChannelStatusTable/docsLeakDetTestChannelStatusEntry/docsLeakDetTestChannelStatusNumModemsCfg
  • /iso/org/dod/internet/private/vendor-objects/cableLabs/clabProject/clabProjDocsis/docsLeakDetectMib/docsLeakDetObjects/docsLeakDetTestObjects/docsLeakDetTestChannelStatusTable/docsLeakDetTestChannelStatusEntry/docsLeakDetTestChannelStatusNumModemsCfg
  • /iso/org/dod/internet/private/vendor-objects/cable-Television-Laboratories-Inc/clabProject/clabProjDocsis/docsLeakDetectMib/docsLeakDetObjects/docsLeakDetTestObjects/docsLeakDetTestChannelStatusTable/docsLeakDetTestChannelStatusEntry/docsLeakDetTestChannelStatusNumModemsCfg
  • Additional combinations skipped.

Descriptions

docsLeakDetTestChannelStatusNumModemsCfg — CableLabs official current and historical MIBs

This attribute provides the count of the number of modems that are explicitly configured for this session. When the modems are configured, this value remains static throughout the test. When the CMTS manages the list of modems, this value can change over time as additional modems are assigned the OFDMA channel used for testing in their TCS at registration or via DBC. Modems can be configured in a list but could be offline or in a state that does not allow them to be scheduled for OUDP Leakage Bursts. In these cases, the NumModemsCfg will be larger than NumModemsActive. Explicit MAC Address lists that are written via the management interface and MAC Address list generated by CMTS are each a 'configured list'. Criteria for selecting the list of CM to explicitly configure is outside the scope of the specification.

docsLeakDetTestChannelStatusNumModemsCfg — CableLabs official current and historical MIBs

This attribute provides the count of the number of modems that are configured for this session. When the modems are explicitly configured via the management interface, this value remains static throughout the test. When the CCAP determines and manages the list of modems, this value can change over time as additional modems are assigned the OFDMA channel used for testing in their TCS at registration or via DBC, or as modems are administratively deleted from the system. In the case where additional modems are configured into a session by the CCAP, the modems are added to the end of the grant cycle as soon as is practical. Modems can be configured in a list but could be offline or in a state that does not allow them to be scheduled for OUDP Leakage Bursts. In these cases, the NumModemsCfg will be larger than NumModemsActive. Explicit modem MAC Address lists that are written via the management interface and modem MAC Address lists generated by CCAP are each a 'configured list'. Criteria for selecting the list of modems to configure is outside the scope of the specification. Explicit modem MAC Address lists can be specified in which a given modem appears multiple times. However, in all cases NumModemsCfg only counts each configured modem once.

Source records

docsLeakDetTestChannelStatusNumModemsCfg

Status in source: current.

Names: docsLeakDetTestChannelStatusNumModemsCfg

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "docsLeakDetTestChannelStatusNumModemsCfg",
    "OBJECT-TYPE",
    "SYNTAX",
    "Unsigned32",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This attribute provides the count of the number of modems that are explicitly configured for this session. When the modems are configured, this value remains static throughout the test. When the CMTS manages the list of modems, this value can change over time as additional modems are assigned the OFDMA channel used for testing in their TCS at registration or via DBC. Modems can be configured in a list but could be offline or in a state that does not allow them to be scheduled for OUDP Leakage Bursts. In these cases, the NumModemsCfg will be larger than NumModemsActive. Explicit MAC Address lists that are written via the management interface and MAC Address list generated by CMTS are each a 'configured list'. Criteria for selecting the list of CM to explicitly configure is outside the scope of the specification.\"",
    "REFERENCE",
    "\"Information Model Mapping: CM-SP-CCAP-OSSI LeakageDetectionTestChannelStatus::NumModemsCfg\"",
    "::=",
    "{",
    "docsLeakDetTestChannelStatusEntry",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Unsigned32"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This attribute provides the count of the number of modems that are explicitly configured for this session. When the modems are configured, this value remains static throughout the test. When the CMTS manages the list of modems, this value can change over time as additional modems are assigned the OFDMA channel used for testing in their TCS at registration or via DBC. Modems can be configured in a list but could be offline or in a state that does not allow them to be scheduled for OUDP Leakage Bursts. In these cases, the NumModemsCfg will be larger than NumModemsActive. Explicit MAC Address lists that are written via the management interface and MAC Address list generated by CMTS are each a 'configured list'. Criteria for selecting the list of CM to explicitly configure is outside the scope of the specification."
    ],
    [
      "REFERENCE",
      "Information Model Mapping: CM-SP-CCAP-OSSI LeakageDetectionTestChannelStatus::NumModemsCfg"
    ],
    null,
    null,
    null
  ]
}
  • CableLabs official current and historical MIBs · Publisher's source file: DOCS-LEAK-DETECT-MIB-2022-05-12.txt

    Module: DOCS-LEAK-DETECT-MIB

    Published definition
    docsLeakDetTestChannelStatusNumModemsCfg OBJECT-TYPE
         SYNTAX      Unsigned32
         MAX-ACCESS  read-only
         STATUS      current
         DESCRIPTION
             "This attribute provides the count of the number of modems 
              that are explicitly configured for this session. When the 
              modems are configured, this value remains static throughout
              the test. When the CMTS manages the list of modems, this value
              can change over time as additional modems are assigned the 
              OFDMA channel used for testing in their TCS at registration
              or via DBC. Modems can be configured in a list but could 
              be offline or in a state that does not allow them to be scheduled
              for OUDP Leakage Bursts. In these cases, the NumModemsCfg will 
              be larger than NumModemsActive. Explicit MAC Address lists that
              are written via the management interface and MAC Address list 
              generated by CMTS are each a 'configured list'. Criteria for 
              selecting the list of CM to explicitly configure is outside 
              the scope of the specification."
         REFERENCE      
            "Information Model Mapping: CM-SP-CCAP-OSSI 
             LeakageDetectionTestChannelStatus::NumModemsCfg"
        ::= { docsLeakDetTestChannelStatusEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TruthValue', 'MacAddress', 'DateAndTime'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Counter64'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE'], 'CLAB-DEF-MIB': ['clabProjDocsis'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download DOCS-LEAK-DETECT-MIB-2022-05-12.txt
    Source location: DOCS-LEAK-DETECT-MIB::docsLeakDetTestChannelStatusNumModemsCfg.
    Source version and references

    Downloaded: 2026-10-26T22:49:35.835206+00:00.

docsLeakDetTestChannelStatusNumModemsCfg

Status in source: current.

Names: docsLeakDetTestChannelStatusNumModemsCfg

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "docsLeakDetTestChannelStatusNumModemsCfg",
    "OBJECT-TYPE",
    "SYNTAX",
    "Unsigned32",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This attribute provides the count of the number of modems that are configured for this session. When the modems are explicitly configured via the management interface, this value remains static throughout the test. When the CCAP determines and manages the list of modems, this value can change over time as additional modems are assigned the OFDMA channel used for testing in their TCS at registration or via DBC, or as modems are administratively deleted from the system. In the case where additional modems are configured into a session by the CCAP, the modems are added to the end of the grant cycle as soon as is practical. Modems can be configured in a list but could be offline or in a state that does not allow them to be scheduled for OUDP Leakage Bursts. In these cases, the NumModemsCfg will be larger than NumModemsActive. Explicit modem MAC Address lists that are written via the management interface and modem MAC Address lists generated by CCAP are each a 'configured list'. Criteria for selecting the list of modems to configure is outside the scope of the specification. Explicit modem MAC Address lists can be specified in which a given modem appears multiple times. However, in all cases NumModemsCfg only counts each configured modem once.\"",
    "REFERENCE",
    "\"Information Model Mapping: CM-SP-CCAP-OSSI LeakageDetectionTestChannelStatus::NumModemsCfg\"",
    "::=",
    "{",
    "docsLeakDetTestChannelStatusEntry",
    "4",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Unsigned32"
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This attribute provides the count of the number of modems that are configured for this session. When the modems are explicitly configured via the management interface, this value remains static throughout the test. When the CCAP determines and manages the list of modems, this value can change over time as additional modems are assigned the OFDMA channel used for testing in their TCS at registration or via DBC, or as modems are administratively deleted from the system. In the case where additional modems are configured into a session by the CCAP, the modems are added to the end of the grant cycle as soon as is practical. Modems can be configured in a list but could be offline or in a state that does not allow them to be scheduled for OUDP Leakage Bursts. In these cases, the NumModemsCfg will be larger than NumModemsActive. Explicit modem MAC Address lists that are written via the management interface and modem MAC Address lists generated by CCAP are each a 'configured list'. Criteria for selecting the list of modems to configure is outside the scope of the specification. Explicit modem MAC Address lists can be specified in which a given modem appears multiple times. However, in all cases NumModemsCfg only counts each configured modem once."
    ],
    [
      "REFERENCE",
      "Information Model Mapping: CM-SP-CCAP-OSSI LeakageDetectionTestChannelStatus::NumModemsCfg"
    ],
    null,
    null,
    null
  ]
}
  • CableLabs official current and historical MIBs · Publisher's source file: DOCS-LEAK-DETECT-MIB.mib

    Module: DOCS-LEAK-DETECT-MIB

    Published definition
    docsLeakDetTestChannelStatusNumModemsCfg OBJECT-TYPE
         SYNTAX      Unsigned32
         MAX-ACCESS  read-only
         STATUS      current
         DESCRIPTION
             "This attribute provides the count of the number of modems that are 
              configured for this session. When the modems are explicitly configured 
              via the management interface, this value remains static throughout the test. 
              When the CCAP determines and manages the list of modems, this value can change 
              over time as additional modems are assigned the OFDMA channel used for testing 
              in their TCS at registration or via DBC, or as modems are administratively deleted
              from the system. 
              
              In the case where additional modems are configured into a session by the CCAP, 
              the modems are added to the end of the grant cycle as soon as is practical. 
              Modems can be configured in a list but could be offline or in a state that does not 
              allow them to be scheduled for OUDP Leakage Bursts. In these cases, the NumModemsCfg 
              will be larger than NumModemsActive. 
              Explicit modem MAC Address lists that are written via the management interface and modem 
              MAC Address lists generated by CCAP are each a 'configured list'. 
              
              Criteria for selecting the list of modems to configure is outside the scope of the specification.
              Explicit modem MAC Address lists can be specified in which a given modem appears multiple times. 
              However, in all cases NumModemsCfg only counts each configured modem once."
         REFERENCE      
            "Information Model Mapping: CM-SP-CCAP-OSSI 
             LeakageDetectionTestChannelStatus::NumModemsCfg"
        ::= { docsLeakDetTestChannelStatusEntry 4 }
    Module imports
    {'SNMPv2-TC': ['TruthValue', 'MacAddress', 'DateAndTime'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Unsigned32', 'Counter32', 'Counter64'], 'SNMPv2-CONF': ['OBJECT-GROUP', 'MODULE-COMPLIANCE'], 'CLAB-DEF-MIB': ['clabProjDocsis'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString']}
    · Download DOCS-LEAK-DETECT-MIB.mib
    Source location: DOCS-LEAK-DETECT-MIB::docsLeakDetTestChannelStatusNumModemsCfg.
    Source version and references

    Downloaded: 2026-10-26T22:47:23.305674+00:00.

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.4491)

Ralph Brown

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.4491)

Maria Stachelek

Siblings (9)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.4491.2.1.37.1.1.4.1.1 docsLeakDetTestChannelStatusInterfaceName00
1.3.6.1.4.1.4491.2.1.37.1.1.4.1.2 docsLeakDetTestChannelStatusTestStartFreq00
1.3.6.1.4.1.4491.2.1.37.1.1.4.1.3 docsLeakDetTestChannelStatusTestEndFreq00
1.3.6.1.4.1.4491.2.1.37.1.1.4.1.5 docsLeakDetTestChannelStatusNumModemsActive00
1.3.6.1.4.1.4491.2.1.37.1.1.4.1.6 docsLeakDetTestChannelStatusFirstSubcarrierId00
1.3.6.1.4.1.4491.2.1.37.1.1.4.1.7 docsLeakDetTestChannelStatusLastSubcarrierId00
1.3.6.1.4.1.4491.2.1.37.1.1.4.1.8 docsLeakDetTestChannelStatusBurstIuc00
1.3.6.1.4.1.4491.2.1.37.1.1.4.1.9 docsLeakDetTestChannelStatusCurrCycleTime00
1.3.6.1.4.1.4491.2.1.37.1.1.4.1.10 docsLeakDetTestChannelStatusNumBurstPositions00