OID reference

dlswCircuitTable

1.3.6.1.4.1.43.45.1.2.34.5.1

Description

This table is the circuit representation in the DLSw entity. Virtual data links are used to represent any internal end stations. There is a conceptual row associated with each data link. Thus, for circuits without an intervening transport connection, there are two conceptual rows for each circuit. The table consists o…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.43.45.1.2.34.5 (dlswCircuit)
Node code
1
Node name
dlswCircuitTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.43.45.1.2.34.5.1
URN notation
urn:oid:1.3.6.1.4.1.43.45.1.2.34.5.1
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 43 45 1 2 34 5 1}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) hwproducts(2) dlsw(34) dlswCircuit(5) dlswCircuitTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) hwproducts(2) dlsw(34) dlswCircuit(5) dlswCircuitTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) hwproducts(2) dlsw(34) dlswCircuit(5) dlswCircuitTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) hwproducts(2) dlsw(34) dlswCircuit(5) dlswCircuitTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) hwproducts(2) dlsw(34) dlswCircuit(5) dlswCircuitTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) hwproducts(2) dlsw(34) dlswCircuit(5) dlswCircuitTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) hwproducts(2) dlsw(34) dlswCircuit(5) dlswCircuitTable(1)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) hwproducts(2) dlsw(34) dlswCircuit(5) dlswCircuitTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) hwproducts(2) dlsw(34) dlswCircuit(5) dlswCircuitTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) hwproducts(2) dlsw(34) dlswCircuit(5) dlswCircuitTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) hwproducts(2) dlsw(34) dlswCircuit(5) dlswCircuitTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) hwproducts(2) dlsw(34) dlswCircuit(5) dlswCircuitTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) hwproducts(2) dlsw(34) dlswCircuit(5) dlswCircuitTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) hwproducts(2) dlsw(34) dlswCircuit(5) dlswCircuitTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) hwproducts(2) dlsw(34) dlswCircuit(5) dlswCircuitTable(1)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) hwproducts(2) dlsw(34) dlswCircuit(5) dlswCircuitTable(1)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/43/45/1/2/34/5/1
  • /ISO/Identified-Organization/6/1/4/1/43/45/1/2/34/5/1
  • /ISO/3/6/1/4/1/43/45/1/2/34/5/1
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/a3Com/jv-mib/huawei/hwproducts/dlsw/dlswCircuit/dlswCircuitTable
  • /iso/identified-organization/dod/internet/private/enterprise/a3com/jv-mib/huawei/hwproducts/dlsw/dlswCircuit/dlswCircuitTable
  • /iso/identified-organization/dod/internet/private/enterprises/a3Com/jv-mib/huawei/hwproducts/dlsw/dlswCircuit/dlswCircuitTable
  • /iso/identified-organization/dod/internet/private/enterprises/a3com/jv-mib/huawei/hwproducts/dlsw/dlswCircuit/dlswCircuitTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/hwproducts/dlsw/dlswCircuit/dlswCircuitTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/hwproducts/dlsw/dlswCircuit/dlswCircuitTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/hwproducts/dlsw/dlswCircuit/dlswCircuitTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/hwproducts/dlsw/dlswCircuit/dlswCircuitTable
  • /iso/org/dod/internet/private/enterprise/a3Com/jv-mib/huawei/hwproducts/dlsw/dlswCircuit/dlswCircuitTable
  • /iso/org/dod/internet/private/enterprise/a3com/jv-mib/huawei/hwproducts/dlsw/dlswCircuit/dlswCircuitTable
  • /iso/org/dod/internet/private/enterprises/a3Com/jv-mib/huawei/hwproducts/dlsw/dlswCircuit/dlswCircuitTable
  • /iso/org/dod/internet/private/enterprises/a3com/jv-mib/huawei/hwproducts/dlsw/dlswCircuit/dlswCircuitTable
  • /iso/org/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/hwproducts/dlsw/dlswCircuit/dlswCircuitTable
  • /iso/org/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/hwproducts/dlsw/dlswCircuit/dlswCircuitTable
  • /iso/org/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/hwproducts/dlsw/dlswCircuit/dlswCircuitTable
  • /iso/org/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/hwproducts/dlsw/dlswCircuit/dlswCircuitTable
  • Additional combinations skipped.

SNMP properties

Value type
SEQUENCE OF DlswCircuitEntry
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

dlswCircuitTable · current

dlswCircuitTable  OBJECT-TYPE
    SYNTAX     SEQUENCE OF DlswCircuitEntry
    MAX-ACCESS not-accessible
    STATUS     current
    DESCRIPTION
       "This table is the circuit representation in the DLSw
        entity. Virtual data links are used to represent any internal
        end stations.  There is a conceptual row associated with
        each data link.  Thus, for circuits without an intervening
        transport connection, there are two conceptual rows
        for each circuit.

        The table consists of the circuits being established,
        established, and as an implementation option, circuits that
        have been disconnected.  For circuits carried over
        transport connections, an entry is created after
        the CUR_cs was sent or received.  For circuits between
        two locally attached devices, or internal virtual MAC
        addresses, an entry is created when the equivalent of
        CUR_cs sent/received status is reached.

        End station 1 (S1) and End station 2 (S2) are used to
        represent the two end stations of the circuit.
        S1 is always an end station which is locally attached.
        S2 may be locally attached or remote.  If it is locally
        attached, the circuit will be represented by two rows indexed
        by (A, B) and (B, A) where A & B are the relevant MACs/SAPs.

        The table may be used to store the causes of disconnection of
        circuits.  It is recommended that the oldest disconnected
        circuit entry be removed from this table when the memory
        space of disconnected circuits is needed."
    ::= { dlswCircuit 1 }

dlswCircuitTable · current

dlswCircuitTable  OBJECT-TYPE
    SYNTAX     SEQUENCE OF DlswCircuitEntry
    MAX-ACCESS not-accessible
    STATUS     current
    DESCRIPTION
       "This table is the circuit representation in the DLSw
        entity. Virtual data links are used to represent any internal
        end stations.  There is a conceptual row associated with
        each data link.  Thus, for circuits without an intervening
        transport connection, there are two conceptual rows
        for each circuit.

        The table consists of the circuits being established,
        established, and as an implementation option, circuits that
        have been disconnected.  For circuits carried over
        transport connections, an entry is created after
        the CUR_cs was sent or received.  For circuits between
        two locally attached devices, or internal virtual MAC
        addresses, an entry is created when the equivalent of
        CUR_cs sent/received status is reached.

        End station 1 (S1) and End station 2 (S2) are used to
        represent the two end stations of the circuit.
        S1 is always an end station which is locally attached.
        S2 may be locally attached or remote.  If it is locally
        attached, the circuit will be represented by two rows indexed
        by (A, B) and (B, A) where A & B are the relevant MACs/SAPs.

        The table may be used to store the causes of disconnection of
        circuits.  It is recommended that the oldest disconnected
        circuit entry be removed from this table when the memory
        space of disconnected circuits is needed."
    ::= { dlswCircuit 1 }

Meaning

Descriptions

1 unique

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

This table is the circuit representation in the DLSw entity. Virtual data links are used to represent any internal end stations. There is a conceptual row associated with each data link. Thus, for circuits without an intervening transport connection, there are two conceptual rows for each circuit. The table consists of the circuits being established, established, and as an implementation option, circuits that have been disconnected. For circuits carried over transport connections, an entry is created after the CUR_cs was sent or received. For circuits between two locally attached devices, or internal virtual MAC addresses, an entry is created when the equivalent of CUR_cs sent/received status is reached. End station 1 (S1) and End station 2 (S2) are used to represent the two end stations of the circuit. S1 is always an end station which is locally attached. S2 may be locally attached or remote. If it is locally attached, the circuit will be represented by two rows indexed by (A, B) and (B, A) where A & B are the relevant MACs/SAPs. The table may be used to store the causes of disconnection of circuits. It is recommended that the oldest disconnected circuit entry be removed from this table when the memory space of disconnected circuits is needed.

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

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

Status in source: current.

Names: dlswCircuitTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dlswCircuitTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "DlswCircuitEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This table is the circuit representation in the DLSw entity. Virtual data links are used to represent any internal end stations. There is a conceptual row associated with each data link. Thus, for circuits without an intervening transport connection, there are two conceptual rows for each circuit. The table consists of the circuits being established, established, and as an implementation option, circuits that have been disconnected. For circuits carried over transport connections, an entry is created after the CUR_cs was sent or received. For circuits between two locally attached devices, or internal virtual MAC addresses, an entry is created when the equivalent of CUR_cs sent/received status is reached. End station 1 (S1) and End station 2 (S2) are used to represent the two end stations of the circuit. S1 is always an end station which is locally attached. S2 may be locally attached or remote. If it is locally attached, the circuit will be represented by two rows indexed by (A, B) and (B, A) where A & B are the relevant MACs/SAPs. The table may be used to store the causes of disconnection of circuits. It is recommended that the oldest disconnected circuit entry be removed from this table when the memory space of disconnected circuits is needed.\"",
    "::=",
    "{",
    "dlswCircuit",
    "1",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "DlswCircuitEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This table is the circuit representation in the DLSw entity. Virtual data links are used to represent any internal end stations. There is a conceptual row associated with each data link. Thus, for circuits without an intervening transport connection, there are two conceptual rows for each circuit. The table consists of the circuits being established, established, and as an implementation option, circuits that have been disconnected. For circuits carried over transport connections, an entry is created after the CUR_cs was sent or received. For circuits between two locally attached devices, or internal virtual MAC addresses, an entry is created when the equivalent of CUR_cs sent/received status is reached. End station 1 (S1) and End station 2 (S2) are used to represent the two end stations of the circuit. S1 is always an end station which is locally attached. S2 may be locally attached or remote. If it is locally attached, the circuit will be represented by two rows indexed by (A, B) and (B, A) where A & B are the relevant MACs/SAPs. The table may be used to store the causes of disconnection of circuits. It is recommended that the oldest disconnected circuit entry be removed from this table when the memory space of disconnected circuits is needed."
    ],
    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.2.34.5.1.1 dlswCircuitEntry2222