OID reference

h3cdeNodeConfigSapList

1.3.6.1.4.1.43.45.1.10.2.62.1.1.15

Description

The SAP list indicates which SAPs are allowed. Only SAPs with even numbers are represented, in the form of the most significant bit of the first octet representing the SAP 0, the next most significant bit representing the SAP 2, to the least significant bit of the last octet representing the SAP 254. Data link switchi…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.43.45.1.10.2.62.1.1 (h3cdeNode)
Node code
15
Node name
h3cdeNodeConfigSapList
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.43.45.1.10.2.62.1.1.15
URN notation
urn:oid:1.3.6.1.4.1.43.45.1.10.2.62.1.1.15
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 43 45 1 10 2 62 1 1 15}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cDlswExt(62) h3cDlswExtMIBObjects(1) h3cdeNode(1) h3cdeNodeConfigSapList(15)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cDlswExt(62) h3cDlswExtMIBObjects(1) h3cdeNode(1) h3cdeNodeConfigSapList(15)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cDlswExt(62) h3cDlswExtMIBObjects(1) h3cdeNode(1) h3cdeNodeConfigSapList(15)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cDlswExt(62) h3cDlswExtMIBObjects(1) h3cdeNode(1) h3cdeNodeConfigSapList(15)}
  • {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) h3cDlswExt(62) h3cDlswExtMIBObjects(1) h3cdeNode(1) h3cdeNodeConfigSapList(15)}
  • {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) h3cDlswExt(62) h3cDlswExtMIBObjects(1) h3cdeNode(1) h3cdeNodeConfigSapList(15)}
  • {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) h3cDlswExt(62) h3cDlswExtMIBObjects(1) h3cdeNode(1) h3cdeNodeConfigSapList(15)}
  • {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) h3cDlswExt(62) h3cDlswExtMIBObjects(1) h3cdeNode(1) h3cdeNodeConfigSapList(15)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cDlswExt(62) h3cDlswExtMIBObjects(1) h3cdeNode(1) h3cdeNodeConfigSapList(15)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cDlswExt(62) h3cDlswExtMIBObjects(1) h3cdeNode(1) h3cdeNodeConfigSapList(15)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cDlswExt(62) h3cDlswExtMIBObjects(1) h3cdeNode(1) h3cdeNodeConfigSapList(15)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cDlswExt(62) h3cDlswExtMIBObjects(1) h3cdeNode(1) h3cdeNodeConfigSapList(15)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cDlswExt(62) h3cDlswExtMIBObjects(1) h3cdeNode(1) h3cdeNodeConfigSapList(15)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cDlswExt(62) h3cDlswExtMIBObjects(1) h3cdeNode(1) h3cdeNodeConfigSapList(15)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cDlswExt(62) h3cDlswExtMIBObjects(1) h3cdeNode(1) h3cdeNodeConfigSapList(15)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cDlswExt(62) h3cDlswExtMIBObjects(1) h3cdeNode(1) h3cdeNodeConfigSapList(15)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/43/45/1/10/2/62/1/1/15
  • /ISO/Identified-Organization/6/1/4/1/43/45/1/10/2/62/1/1/15
  • /ISO/3/6/1/4/1/43/45/1/10/2/62/1/1/15
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cDlswExt/h3cDlswExtMIBObjects/h3cdeNode/h3cdeNodeConfigSapList
  • /iso/identified-organization/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cDlswExt/h3cDlswExtMIBObjects/h3cdeNode/h3cdeNodeConfigSapList
  • /iso/identified-organization/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cDlswExt/h3cDlswExtMIBObjects/h3cdeNode/h3cdeNodeConfigSapList
  • /iso/identified-organization/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cDlswExt/h3cDlswExtMIBObjects/h3cdeNode/h3cdeNodeConfigSapList
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cDlswExt/h3cDlswExtMIBObjects/h3cdeNode/h3cdeNodeConfigSapList
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cDlswExt/h3cDlswExtMIBObjects/h3cdeNode/h3cdeNodeConfigSapList
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cDlswExt/h3cDlswExtMIBObjects/h3cdeNode/h3cdeNodeConfigSapList
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cDlswExt/h3cDlswExtMIBObjects/h3cdeNode/h3cdeNodeConfigSapList
  • /iso/org/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cDlswExt/h3cDlswExtMIBObjects/h3cdeNode/h3cdeNodeConfigSapList
  • /iso/org/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cDlswExt/h3cDlswExtMIBObjects/h3cdeNode/h3cdeNodeConfigSapList
  • /iso/org/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cDlswExt/h3cDlswExtMIBObjects/h3cdeNode/h3cdeNodeConfigSapList
  • /iso/org/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cDlswExt/h3cDlswExtMIBObjects/h3cdeNode/h3cdeNodeConfigSapList
  • /iso/org/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cDlswExt/h3cDlswExtMIBObjects/h3cdeNode/h3cdeNodeConfigSapList
  • /iso/org/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cDlswExt/h3cDlswExtMIBObjects/h3cdeNode/h3cdeNodeConfigSapList
  • /iso/org/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cDlswExt/h3cDlswExtMIBObjects/h3cdeNode/h3cdeNodeConfigSapList
  • /iso/org/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cDlswExt/h3cDlswExtMIBObjects/h3cdeNode/h3cdeNodeConfigSapList
  • Additional combinations skipped.

SNMP properties

Value type
OCTET STRING
Maximum access defined by MIB
read-write
Status in MIB
current
Default value
'FF000000000000000000000000000000'h
Allowed size (octets)
16

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.43.45.1.10.2.62.1.1.15.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.

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

Show 2 published definitions

h3cdeNodeConfigSapList · current

h3cdeNodeConfigSapList OBJECT-TYPE
    SYNTAX      OCTET STRING (SIZE (16))
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "The SAP list indicates which SAPs are allowed.
        Only SAPs with even numbers are represented,
        in the form of the most significant bit of the first
        octet representing the SAP 0, the next most significant
        bit representing the SAP 2, to the least significant
        bit of the last octet representing the SAP 254. Data
        link switching is allowed for those SAPs which have
        one in its corresponding bit, not allowed otherwise.
        The whole SAP list has to be changed together. Changing
        the SAP list affects only new circuit establishments
        and has no effect on established circuits.

        This list can be used to restrict specific partners
        from knowing about all the SAPs used by DLSw on all its
        interfaces (these are represented in h3cdeIfSapList for
        each interface). For instance, one may want to run NetBIOS
        with some partners but not others.

        If a node supports sending run-time capabilities exchange
        messages, changes to this object should cause that action.
        When to start the run-time capabilities exchange is
        implementation-specific.

        The DEFVAL below indicates support for SAPs 0, 2, 4, 6, 8, A, C and E."
    DEFVAL      { 'FF000000000000000000000000000000'h }
    ::= { h3cdeNode 15 }

h3cdeNodeConfigSapList · current

h3cdeNodeConfigSapList OBJECT-TYPE
    SYNTAX      OCTET STRING (SIZE (16))
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
        "The SAP list indicates which SAPs are allowed.
        Only SAPs with even numbers are represented,
        in the form of the most significant bit of the first
        octet representing the SAP 0, the next most significant
        bit representing the SAP 2, to the least significant
        bit of the last octet representing the SAP 254. Data
        link switching is allowed for those SAPs which have
        one in its corresponding bit, not allowed otherwise.
        The whole SAP list has to be changed together. Changing
        the SAP list affects only new circuit establishments
        and has no effect on established circuits.

        This list can be used to restrict specific partners
        from knowing about all the SAPs used by DLSw on all its
        interfaces (these are represented in h3cdeIfSapList for
        each interface). For instance, one may want to run NetBIOS
        with some partners but not others.

        If a node supports sending run-time capabilities exchange
        messages, changes to this object should cause that action.
        When to start the run-time capabilities exchange is
        implementation-specific.

        The DEFVAL below indicates support for SAPs 0, 2, 4, 6, 8, A, C and E."
    DEFVAL      { 'FF000000000000000000000000000000'h }
    ::= { h3cdeNode 15 }

Meaning

Descriptions

1 unique

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

The SAP list indicates which SAPs are allowed. Only SAPs with even numbers are represented, in the form of the most significant bit of the first octet representing the SAP 0, the next most significant bit representing the SAP 2, to the least significant bit of the last octet representing the SAP 254. Data link switching is allowed for those SAPs which have one in its corresponding bit, not allowed otherwise. The whole SAP list has to be changed together. Changing the SAP list affects only new circuit establishments and has no effect on established circuits. This list can be used to restrict specific partners from knowing about all the SAPs used by DLSw on all its interfaces (these are represented in h3cdeIfSapList for each interface). For instance, one may want to run NetBIOS with some partners but not others. If a node supports sending run-time capabilities exchange messages, changes to this object should cause that action. When to start the run-time capabilities exchange is implementation-specific. The DEFVAL below indicates support for SAPs 0, 2, 4, 6, 8, A, C and E.

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

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

Status in source: current.

Names: h3cdeNodeConfigSapList

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cdeNodeConfigSapList",
    "OBJECT-TYPE",
    "SYNTAX",
    "OCTET",
    "STRING",
    "(",
    "SIZE",
    "(",
    "16",
    ")",
    ")",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The SAP list indicates which SAPs are allowed. Only SAPs with even numbers are represented, in the form of the most significant bit of the first octet representing the SAP 0, the next most significant bit representing the SAP 2, to the least significant bit of the last octet representing the SAP 254. Data link switching is allowed for those SAPs which have one in its corresponding bit, not allowed otherwise. The whole SAP list has to be changed together. Changing the SAP list affects only new circuit establishments and has no effect on established circuits. This list can be used to restrict specific partners from knowing about all the SAPs used by DLSw on all its interfaces (these are represented in h3cdeIfSapList for each interface). For instance, one may want to run NetBIOS with some partners but not others. If a node supports sending run-time capabilities exchange messages, changes to this object should cause that action. When to start the run-time capabilities exchange is implementation-specific. The DEFVAL below indicates support for SAPs 0, 2, 4, 6, 8, A, C and E.\"",
    "DEFVAL",
    "{",
    "'",
    "FF000000000000000000000000000000",
    "'",
    "h",
    "}",
    "::=",
    "{",
    "h3cdeNode",
    "15",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "OCTET STRING",
      [
        "octetStringSubType",
        [
          [
            16
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The SAP list indicates which SAPs are allowed. Only SAPs with even numbers are represented, in the form of the most significant bit of the first octet representing the SAP 0, the next most significant bit representing the SAP 2, to the least significant bit of the last octet representing the SAP 254. Data link switching is allowed for those SAPs which have one in its corresponding bit, not allowed otherwise. The whole SAP list has to be changed together. Changing the SAP list affects only new circuit establishments and has no effect on established circuits. This list can be used to restrict specific partners from knowing about all the SAPs used by DLSw on all its interfaces (these are represented in h3cdeIfSapList for each interface). For instance, one may want to run NetBIOS with some partners but not others. If a node supports sending run-time capabilities exchange messages, changes to this object should cause that action. When to start the run-time capabilities exchange is implementation-specific. The DEFVAL below indicates support for SAPs 0, 2, 4, 6, 8, A, C and E."
    ],
    null,
    null,
    null,
    [
      "DEFVAL",
      "'FF000000000000000000000000000000'h"
    ]
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.43)

Jeremy Siegel

Siblings (20)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.43.45.1.10.2.62.1.1.1 h3cdeNodeVendorID00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.2 h3cdeNodeIpAddrType00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.3 h3cdeNodeLocalAddr00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.4 h3cdeNodePriority00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.5 h3cdeNodeInitPacingWindow00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.6 h3cdeNodeMaxPacingWindow00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.7 h3cdeNodeKeepAliveInterval00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.8 h3cdeNodePermitDynamic00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.9 h3cdeNodeConnTimeout00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.10 h3cdeNodeLocalPendTimeout00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.11 h3cdeNodeRemotePendTimeout00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.12 h3cdeNodeSnaCacheTimeout00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.13 h3cdeNodeExplorerTimeout00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.14 h3cdeNodeExplorerWaitTimeout00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.16 h3cdeNodeMaxTransmission00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.17 h3cdeNodeMulticastStatus00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.18 h3cdeNodeMulticastAddress00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.19 h3cdeNodeResetTcpAll00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.20 h3cdeNodeStCapTcpNum00
1.3.6.1.4.1.43.45.1.10.2.62.1.1.21 h3cdeNodeTcpQueueMax00