OID reference

h3cRTSubIfTable

1.3.6.1.4.1.43.45.1.10.2.40.2.2.2

Description

This table contains objects to create or delete sub interfaces. To create a sub interface, a valid parent interface must be specified by h3cRTSubIfParentIfIndex and the h3cRTSubIfOrdinal must be in the range between h3cRTMinSubIfOrdinal and h3cRTMaxSubIfOrdinal of the parent interface from h3cRTParentIfTable. Sub inte…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.43.45.1.10.2.40.2.2 (h3cIfControl)
Node code
2
Node name
h3cRTSubIfTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.43.45.1.10.2.40.2.2.2
URN notation
urn:oid:1.3.6.1.4.1.43.45.1.10.2.40.2.2.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 43 45 1 10 2 40 2 2 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cIfExt(40) h3cIfExtGroup(2) h3cIfControl(2) h3cRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cIfExt(40) h3cIfExtGroup(2) h3cIfControl(2) h3cRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cIfExt(40) h3cIfExtGroup(2) h3cIfControl(2) h3cRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cIfExt(40) h3cIfExtGroup(2) h3cIfControl(2) h3cRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cIfExt(40) h3cIfExtGroup(2) h3cIfControl(2) h3cRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cIfExt(40) h3cIfExtGroup(2) h3cIfControl(2) h3cRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cIfExt(40) h3cIfExtGroup(2) h3cIfControl(2) h3cRTSubIfTable(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cIfExt(40) h3cIfExtGroup(2) h3cIfControl(2) h3cRTSubIfTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cIfExt(40) h3cIfExtGroup(2) h3cIfControl(2) h3cRTSubIfTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cIfExt(40) h3cIfExtGroup(2) h3cIfControl(2) h3cRTSubIfTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cIfExt(40) h3cIfExtGroup(2) h3cIfControl(2) h3cRTSubIfTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cIfExt(40) h3cIfExtGroup(2) h3cIfControl(2) h3cRTSubIfTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cIfExt(40) h3cIfExtGroup(2) h3cIfControl(2) h3cRTSubIfTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cIfExt(40) h3cIfExtGroup(2) h3cIfControl(2) h3cRTSubIfTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cIfExt(40) h3cIfExtGroup(2) h3cIfControl(2) h3cRTSubIfTable(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cIfExt(40) h3cIfExtGroup(2) h3cIfControl(2) h3cRTSubIfTable(2)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/43/45/1/10/2/40/2/2/2
  • /ISO/Identified-Organization/6/1/4/1/43/45/1/10/2/40/2/2/2
  • /ISO/3/6/1/4/1/43/45/1/10/2/40/2/2/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cIfExt/h3cIfExtGroup/h3cIfControl/h3cRTSubIfTable
  • /iso/identified-organization/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cIfExt/h3cIfExtGroup/h3cIfControl/h3cRTSubIfTable
  • /iso/identified-organization/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cIfExt/h3cIfExtGroup/h3cIfControl/h3cRTSubIfTable
  • /iso/identified-organization/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cIfExt/h3cIfExtGroup/h3cIfControl/h3cRTSubIfTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cIfExt/h3cIfExtGroup/h3cIfControl/h3cRTSubIfTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cIfExt/h3cIfExtGroup/h3cIfControl/h3cRTSubIfTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cIfExt/h3cIfExtGroup/h3cIfControl/h3cRTSubIfTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cIfExt/h3cIfExtGroup/h3cIfControl/h3cRTSubIfTable
  • /iso/org/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cIfExt/h3cIfExtGroup/h3cIfControl/h3cRTSubIfTable
  • /iso/org/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cIfExt/h3cIfExtGroup/h3cIfControl/h3cRTSubIfTable
  • /iso/org/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cIfExt/h3cIfExtGroup/h3cIfControl/h3cRTSubIfTable
  • /iso/org/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cIfExt/h3cIfExtGroup/h3cIfControl/h3cRTSubIfTable
  • /iso/org/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cIfExt/h3cIfExtGroup/h3cIfControl/h3cRTSubIfTable
  • /iso/org/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cIfExt/h3cIfExtGroup/h3cIfControl/h3cRTSubIfTable
  • /iso/org/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cIfExt/h3cIfExtGroup/h3cIfControl/h3cRTSubIfTable
  • /iso/org/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cIfExt/h3cIfExtGroup/h3cIfControl/h3cRTSubIfTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF H3cRTSubIfEntry
Maximum access defined by MIB
not-accessible
Status in MIB
current

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

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

h3cRTSubIfTable · current

h3cRTSubIfTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF H3cRTSubIfEntry
    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 h3cRTSubIfParentIfIndex and the h3cRTSubIfOrdinal
        must be in the range between h3cRTMinSubIfOrdinal and
        h3cRTMaxSubIfOrdinal of the parent interface from
        h3cRTParentIfTable.

        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."
    ::= { h3cIfControl  2 }

h3cRTSubIfTable · current

h3cRTSubIfTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF H3cRTSubIfEntry
    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 h3cRTSubIfParentIfIndex and the h3cRTSubIfOrdinal
        must be in the range between h3cRTMinSubIfOrdinal and
        h3cRTMaxSubIfOrdinal of the parent interface from
        h3cRTParentIfTable.

        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."
    ::= { h3cIfControl  2 }

Meaning

Descriptions

1 unique

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

This table contains objects to create or delete sub interfaces. To create a sub interface, a valid parent interface must be specified by h3cRTSubIfParentIfIndex and the h3cRTSubIfOrdinal must be in the range between h3cRTMinSubIfOrdinal and h3cRTMaxSubIfOrdinal of the parent interface from h3cRTParentIfTable. 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.

Sources for this description

3Com MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies

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 13Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies1 record · 2 sources

Description 1

h3cRTSubIfTable · current3Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies2 sources

Status in source: current.

Names: h3cRTSubIfTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cRTSubIfTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "H3cRTSubIfEntry",
    "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 h3cRTSubIfParentIfIndex and the h3cRTSubIfOrdinal must be in the range between h3cRTMinSubIfOrdinal and h3cRTMaxSubIfOrdinal of the parent interface from h3cRTParentIfTable. 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.\"",
    "::=",
    "{",
    "h3cIfControl",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "H3cRTSubIfEntry"
      ]
    ],
    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 h3cRTSubIfParentIfIndex and the h3cRTSubIfOrdinal must be in the range between h3cRTMinSubIfOrdinal and h3cRTMaxSubIfOrdinal of the parent interface from h3cRTParentIfTable. 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
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.43)

Jeremy Siegel

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.43.45.1.10.2.40.2.2.2.1 h3cRTSubIfEntry55

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.43.45.1.10.2.40.2.2.1 h3cRTParentIfTable14
1.3.6.1.4.1.43.45.1.10.2.40.2.2.3 h3cIfLinkModeTable14