Reference record for OID 1.3.6.1.4.1.11.2.14.11.15.2.40.2.2.2

Parent
1.3.6.1.4.1.11.2.14.11.15.2.40.2.2 (hpnicfIfControl)
Node code
2
Node name
hpnicfRTSubIfTable
Numeric OID
1.3.6.1.4.1.11.2.14.11.15.2.40.2.2.2
URN notation
urn:oid:1.3.6.1.4.1.11.2.14.11.15.2.40.2.2.2
ASN.1 notation

{1 3 6 1 4 1 11 2 14 11 15 2 40 2 2 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hp(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfIfExt(40) hpnicfIfExtGroup(2) hpnicfIfControl(2) hpnicfRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hp(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfIfExt(40) hpnicfIfExtGroup(2) hpnicfIfControl(2) hpnicfRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hP(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfIfExt(40) hpnicfIfExtGroup(2) hpnicfIfControl(2) hpnicfRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hP(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfIfExt(40) hpnicfIfExtGroup(2) hpnicfIfControl(2) hpnicfRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hpPrintServer(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfIfExt(40) hpnicfIfExtGroup(2) hpnicfIfControl(2) hpnicfRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hpPrintServer(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfIfExt(40) hpnicfIfExtGroup(2) hpnicfIfControl(2) hpnicfRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hp(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfIfExt(40) hpnicfIfExtGroup(2) hpnicfIfControl(2) hpnicfRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hp(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfIfExt(40) hpnicfIfExtGroup(2) hpnicfIfControl(2) hpnicfRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hP(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfIfExt(40) hpnicfIfExtGroup(2) hpnicfIfControl(2) hpnicfRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hP(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfIfExt(40) hpnicfIfExtGroup(2) hpnicfIfControl(2) hpnicfRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hpPrintServer(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfIfExt(40) hpnicfIfExtGroup(2) hpnicfIfControl(2) hpnicfRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hpPrintServer(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfIfExt(40) hpnicfIfExtGroup(2) hpnicfIfControl(2) hpnicfRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hp(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfIfExt(40) hpnicfIfExtGroup(2) hpnicfIfControl(2) hpnicfRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hp(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfIfExt(40) hpnicfIfExtGroup(2) hpnicfIfControl(2) hpnicfRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hP(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfIfExt(40) hpnicfIfExtGroup(2) hpnicfIfControl(2) hpnicfRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hP(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfIfExt(40) hpnicfIfExtGroup(2) hpnicfIfControl(2) hpnicfRTSubIfTable(2)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/11/2/14/11/15/2/40/2/2/2
  • /ISO/Identified-Organization/6/1/4/1/11/2/14/11/15/2/40/2/2/2
  • /ISO/3/6/1/4/1/11/2/14/11/15/2/40/2/2/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/hp/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfIfExt/hpnicfIfExtGroup/hpnicfIfControl/hpnicfRTSubIfTable
  • /iso/identified-organization/dod/internet/private/enterprise/hp/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfIfExt/hpnicfIfExtGroup/hpnicfIfControl/hpnicfRTSubIfTable
  • /iso/identified-organization/dod/internet/private/enterprise/IMPORTS/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfIfExt/hpnicfIfExtGroup/hpnicfIfControl/hpnicfRTSubIfTable
  • /iso/identified-organization/dod/internet/private/enterprise/IMPORTS/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfIfExt/hpnicfIfExtGroup/hpnicfIfControl/hpnicfRTSubIfTable
  • /iso/identified-organization/dod/internet/private/enterprise/hP/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfIfExt/hpnicfIfExtGroup/hpnicfIfControl/hpnicfRTSubIfTable
  • /iso/identified-organization/dod/internet/private/enterprise/hP/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfIfExt/hpnicfIfExtGroup/hpnicfIfControl/hpnicfRTSubIfTable
  • /iso/identified-organization/dod/internet/private/enterprise/hpPrintServer/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfIfExt/hpnicfIfExtGroup/hpnicfIfControl/hpnicfRTSubIfTable
  • /iso/identified-organization/dod/internet/private/enterprise/hpPrintServer/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfIfExt/hpnicfIfExtGroup/hpnicfIfControl/hpnicfRTSubIfTable
  • /iso/identified-organization/dod/internet/private/enterprises/hp/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfIfExt/hpnicfIfExtGroup/hpnicfIfControl/hpnicfRTSubIfTable
  • /iso/identified-organization/dod/internet/private/enterprises/hp/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfIfExt/hpnicfIfExtGroup/hpnicfIfControl/hpnicfRTSubIfTable
  • /iso/identified-organization/dod/internet/private/enterprises/IMPORTS/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfIfExt/hpnicfIfExtGroup/hpnicfIfControl/hpnicfRTSubIfTable
  • /iso/identified-organization/dod/internet/private/enterprises/IMPORTS/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfIfExt/hpnicfIfExtGroup/hpnicfIfControl/hpnicfRTSubIfTable
  • /iso/identified-organization/dod/internet/private/enterprises/hP/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfIfExt/hpnicfIfExtGroup/hpnicfIfControl/hpnicfRTSubIfTable
  • /iso/identified-organization/dod/internet/private/enterprises/hP/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfIfExt/hpnicfIfExtGroup/hpnicfIfControl/hpnicfRTSubIfTable
  • /iso/identified-organization/dod/internet/private/enterprises/hpPrintServer/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfIfExt/hpnicfIfExtGroup/hpnicfIfControl/hpnicfRTSubIfTable
  • /iso/identified-organization/dod/internet/private/enterprises/hpPrintServer/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfIfExt/hpnicfIfExtGroup/hpnicfIfControl/hpnicfRTSubIfTable
  • Additional combinations skipped.

Descriptions

hpnicfRTSubIfTable — HPE networking MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies

This table contains objects to create or delete sub interfaces. To create a sub interface, a valid parent interface must be specified by hpnicfRTSubIfParentIfIndex and the hpnicfRTSubIfOrdinal must be in the range between hpnicfRTMinSubIfOrdinal and hpnicfRTMaxSubIfOrdinal of the parent interface from hpnicfRTParentIfTable. Sub interfaces are logical virtual interfaces configured on a main interface. The main interface can be either a physical interface (such as a Layer 3 Ethernet interface) or a logical interface (such as an MFR interface). The subinterfaces on a main interface share the physical layer parameters of the main interface but can have link layer and network layer parameters of their own. Disabling or enabling a subinterface does not affect the main interface, but the main interface status change affects the subinterfaces. The subinterfaces cannot operate normally unless the main interface is connected. A single physical interface containing multiple subinterfaces enables you to network in a more flexible way. You can create subinterfaces for the following physical interfaces: Ethernet interface. An Ethernet subinterface associated with no VLAN supports only IPX, while an Ethernet subinterface associated with a VLAN supports both IP and IPX. WAN interfaces with their data link layer protocols being frame relay, whose subinterfaces support IP and IPX. WAN interfaces with their data link layer protocols being X.25, whose subinterfaces support IP and IPX. ATM interface, whose subinterfaces support only IP.

Source records

hpnicfRTSubIfTable

Status in source: current.

Names: hpnicfRTSubIfTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "hpnicfRTSubIfTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "HpnicfRTSubIfEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This table contains objects to create or delete sub interfaces. To create a sub interface, a valid parent interface must be specified by hpnicfRTSubIfParentIfIndex and the hpnicfRTSubIfOrdinal must be in the range between hpnicfRTMinSubIfOrdinal and hpnicfRTMaxSubIfOrdinal of the parent interface from hpnicfRTParentIfTable. Sub interfaces are logical virtual interfaces configured on a main interface. The main interface can be either a physical interface (such as a Layer 3 Ethernet interface) or a logical interface (such as an MFR interface). The subinterfaces on a main interface share the physical layer parameters of the main interface but can have link layer and network layer parameters of their own. Disabling or enabling a subinterface does not affect the main interface, but the main interface status change affects the subinterfaces. The subinterfaces cannot operate normally unless the main interface is connected. A single physical interface containing multiple subinterfaces enables you to network in a more flexible way. You can create subinterfaces for the following physical interfaces: Ethernet interface. An Ethernet subinterface associated with no VLAN supports only IPX, while an Ethernet subinterface associated with a VLAN supports both IP and IPX. WAN interfaces with their data link layer protocols being frame relay, whose subinterfaces support IP and IPX. WAN interfaces with their data link layer protocols being X.25, whose subinterfaces support IP and IPX. ATM interface, whose subinterfaces support only IP.\"",
    "::=",
    "{",
    "hpnicfIfControl",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "HpnicfRTSubIfEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This table contains objects to create or delete sub interfaces. To create a sub interface, a valid parent interface must be specified by hpnicfRTSubIfParentIfIndex and the hpnicfRTSubIfOrdinal must be in the range between hpnicfRTMinSubIfOrdinal and hpnicfRTMaxSubIfOrdinal of the parent interface from hpnicfRTParentIfTable. Sub interfaces are logical virtual interfaces configured on a main interface. The main interface can be either a physical interface (such as a Layer 3 Ethernet interface) or a logical interface (such as an MFR interface). The subinterfaces on a main interface share the physical layer parameters of the main interface but can have link layer and network layer parameters of their own. Disabling or enabling a subinterface does not affect the main interface, but the main interface status change affects the subinterfaces. The subinterfaces cannot operate normally unless the main interface is connected. A single physical interface containing multiple subinterfaces enables you to network in a more flexible way. You can create subinterfaces for the following physical interfaces: Ethernet interface. An Ethernet subinterface associated with no VLAN supports only IPX, while an Ethernet subinterface associated with a VLAN supports both IP and IPX. WAN interfaces with their data link layer protocols being frame relay, whose subinterfaces support IP and IPX. WAN interfaces with their data link layer protocols being X.25, whose subinterfaces support IP and IPX. ATM interface, whose subinterfaces support only IP."
    ],
    null,
    null,
    null,
    null
  ]
}
  • HPE networking MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive. HPE networking support.

    Module: HPN-ICF-IF-EXT-MIB

    Published definition
    hpnicfRTSubIfTable OBJECT-TYPE
        SYNTAX      SEQUENCE OF HpnicfRTSubIfEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
            "This table contains objects to create or delete sub interfaces.
            To create a sub interface, a valid parent interface must be
            specified by hpnicfRTSubIfParentIfIndex and the hpnicfRTSubIfOrdinal
            must be in the range between hpnicfRTMinSubIfOrdinal and
            hpnicfRTMaxSubIfOrdinal of the parent interface from
            hpnicfRTParentIfTable.
    
            Sub interfaces are logical virtual interfaces configured on a
            main interface.  The main interface can be either a physical
            interface (such as a Layer 3 Ethernet interface) or a logical
            interface (such as an MFR interface).  The subinterfaces on a
            main interface share the physical layer parameters of the main
            interface but can have link layer and network layer parameters
            of their own.  Disabling or enabling a subinterface does not
            affect the main interface, but the main interface status change
            affects the subinterfaces.  The subinterfaces cannot operate
            normally unless the main interface is connected.
            A single physical interface containing multiple subinterfaces
            enables you to network in a more flexible way.
    
            You can create subinterfaces for the following physical
            interfaces:
            Ethernet interface.  An Ethernet subinterface associated with no
            VLAN supports only IPX, while an Ethernet subinterface associated
            with a VLAN supports both IP and IPX.
            WAN interfaces with their data link layer protocols being frame
            relay, whose subinterfaces support IP and IPX.
            WAN interfaces with their data link layer protocols being X.25,
            whose subinterfaces support IP and IPX.
            ATM interface, whose subinterfaces support only IP."
        ::= { hpnicfIfControl  2 }
    Module imports
    {'IF-MIB': ['ifIndex', 'ifDescr'], 'HCNUM-TC': ['CounterBasedGauge64'], 'SNMPv2-TC': ['DisplayString', 'RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['Integer32', 'Counter64', 'Unsigned32', 'TimeTicks', 'OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE'], 'HPN-ICF-OID-MIB': ['hpnicfCommon']}

    Related source files and packages:


    Source location: HPN-ICF-IF-EXT-MIB::hpnicfRTSubIfTable.
    Source version and references

    Downloaded: 2026-10-23T19:25:41.109280+00:00.

  • Netdisco MIB archive copies · Publisher's source file: hpnicfIfExt.mib

    Vendor MIB copy from the Netdisco archive.

    Module: HPN-ICF-IF-EXT-MIB

    Published definition
    hpnicfRTSubIfTable OBJECT-TYPE
        SYNTAX      SEQUENCE OF HpnicfRTSubIfEntry
        MAX-ACCESS  not-accessible
        STATUS      current
        DESCRIPTION
            "This table contains objects to create or delete sub interfaces.
            To create a sub interface, a valid parent interface must be
            specified by hpnicfRTSubIfParentIfIndex and the hpnicfRTSubIfOrdinal
            must be in the range between hpnicfRTMinSubIfOrdinal and
            hpnicfRTMaxSubIfOrdinal of the parent interface from
            hpnicfRTParentIfTable.
    
            Sub interfaces are logical virtual interfaces configured on a
            main interface.  The main interface can be either a physical
            interface (such as a Layer 3 Ethernet interface) or a logical
            interface (such as an MFR interface).  The subinterfaces on a
            main interface share the physical layer parameters of the main
            interface but can have link layer and network layer parameters
            of their own.  Disabling or enabling a subinterface does not
            affect the main interface, but the main interface status change
            affects the subinterfaces.  The subinterfaces cannot operate
            normally unless the main interface is connected.
            A single physical interface containing multiple subinterfaces
            enables you to network in a more flexible way.
    
            You can create subinterfaces for the following physical
            interfaces:
            Ethernet interface.  An Ethernet subinterface associated with no
            VLAN supports only IPX, while an Ethernet subinterface associated
            with a VLAN supports both IP and IPX.
            WAN interfaces with their data link layer protocols being frame
            relay, whose subinterfaces support IP and IPX.
            WAN interfaces with their data link layer protocols being X.25,
            whose subinterfaces support IP and IPX.
            ATM interface, whose subinterfaces support only IP."
        ::= { hpnicfIfControl  2 }
    Module imports
    {'IF-MIB': ['ifIndex', 'ifDescr'], 'HCNUM-TC': ['CounterBasedGauge64'], 'SNMPv2-TC': ['DisplayString', 'RowStatus', 'TruthValue'], 'SNMPv2-SMI': ['Integer32', 'Counter64', 'Unsigned32', 'TimeTicks', 'OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE'], 'HPN-ICF-OID-MIB': ['hpnicfCommon']}
    · Archived source file

    Related source files and packages:


    Source location: HPN-ICF-IF-EXT-MIB::hpnicfRTSubIfTable.
    Source version and references

    Downloaded: 2026-10-24T15:28:10.527993+00:00.

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.11)

Peterson Tyler

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.11.2.14.11.15.2.40.2.2.2.1 hpnicfRTSubIfEntry55

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.11.2.14.11.15.2.40.2.2.1 hpnicfRTParentIfTable14
1.3.6.1.4.1.11.2.14.11.15.2.40.2.2.3 hpnicfIfLinkModeTable14