OID reference

v52CPathTable

1.3.6.1.4.1.5504.4.3.2.5

Description

C-paths consist of a layer 2 data link carrying an associated layer 3 signaling protocol. Layer 3 signaling is defined by the Control, Link Control, PSTN, BCC, and Protection protocols. Therefore, a C-path can exist for the Control protocol, the Link Control protocol, the PSTN protocol, the BCC protocol, and the Prote…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.5504.4.3.2 (zhoneV52)
Node code
5
Node name
v52CPathTable
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.5504.4.3.2.5
URN notation
urn:oid:1.3.6.1.4.1.5504.4.3.2.5
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 5504 4 3 2 5}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CPathTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CPathTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CPathTable(5)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CPathTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CPathTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CPathTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CPathTable(5)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CPathTable(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CPathTable(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CPathTable(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CPathTable(5)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CPathTable(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CPathTable(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CPathTable(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CPathTable(5)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneCommunicationProtocols(4) zhoneVoice(3) zhoneV52(2) v52CPathTable(5)}
OID-IRI notation
  • /1/3/6/1/4/1/5504/4/3/2/5
  • /ISO/Identified-Organization/6/1/4/1/5504/4/3/2/5
  • /ISO/3/6/1/4/1/5504/4/3/2/5
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/5504/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CPathTable
  • /iso/identified-organization/dod/internet/private/enterprise/zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CPathTable
  • /iso/identified-organization/dod/internet/private/enterprise/Zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CPathTable
  • /iso/identified-organization/dod/internet/private/enterprises/5504/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CPathTable
  • /iso/identified-organization/dod/internet/private/enterprises/zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CPathTable
  • /iso/identified-organization/dod/internet/private/enterprises/Zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CPathTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/5504/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CPathTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CPathTable
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/Zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CPathTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/5504/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CPathTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CPathTable
  • /iso/identified-organization/dod/internet/private/vendor-objects/Zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CPathTable
  • /iso/org/dod/internet/private/enterprise/5504/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CPathTable
  • /iso/org/dod/internet/private/enterprise/zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CPathTable
  • /iso/org/dod/internet/private/enterprise/Zhone/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CPathTable
  • /iso/org/dod/internet/private/enterprises/5504/zhoneCommunicationProtocols/zhoneVoice/zhoneV52/v52CPathTable
  • Additional combinations skipped.

SNMP properties

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

The displayed source records contain one distinct definition. Compare its source records.

v52CPathTable OBJECT-TYPE
            SYNTAX SEQUENCE OF V52CPathEntry
            MAX-ACCESS not-accessible
            STATUS current
            DESCRIPTION
                "C-paths consist of a layer 2 data link carrying an 
                associated layer 3 signaling protocol.  Layer 3 
                signaling is defined by the Control, Link Control,
                PSTN, BCC, and Protection protocols.  Therefore, a 
                C-path can exist for the Control protocol, the Link
                Control protocol, the PSTN protocol, the BCC protocol, 
                and the Protection protocol.  In addition, ISDN 
                D-channel data is also carried over C-paths.  Separate
                C-paths exist for ISDN Ds, p, and f-type data. 
                There can only be one of each control, link control, and
                BCC C-Paths whereas multiple PSTN and ISDN C-Paths may
                exist.
                
                A group of C-Paths are associated with a C-channel.  
                The C-path for protection, however, is not carried in 
                a C-channel."
            ::= { zhoneV52 5 }

Meaning

Descriptions

1 unique

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

C-paths consist of a layer 2 data link carrying an associated layer 3 signaling protocol. Layer 3 signaling is defined by the Control, Link Control, PSTN, BCC, and Protection protocols. Therefore, a C-path can exist for the Control protocol, the Link Control protocol, the PSTN protocol, the BCC protocol, and the Protection protocol. In addition, ISDN D-channel data is also carried over C-paths. Separate C-paths exist for ISDN Ds, p, and f-type data. There can only be one of each control, link control, and BCC C-Paths whereas multiple PSTN and ISDN C-Paths may exist. A group of C-Paths are associated with a C-channel. The C-path for protection, however, is not carried in a C-channel.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

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 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

v52CPathTable · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: v52CPathTable

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "v52CPathTable",
    "OBJECT-TYPE",
    "SYNTAX",
    "SEQUENCE",
    "OF",
    "V52CPathEntry",
    "MAX-ACCESS",
    "not-accessible",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"C-paths consist of a layer 2 data link carrying an associated layer 3 signaling protocol. Layer 3 signaling is defined by the Control, Link Control, PSTN, BCC, and Protection protocols. Therefore, a C-path can exist for the Control protocol, the Link Control protocol, the PSTN protocol, the BCC protocol, and the Protection protocol. In addition, ISDN D-channel data is also carried over C-paths. Separate C-paths exist for ISDN Ds, p, and f-type data. There can only be one of each control, link control, and BCC C-Paths whereas multiple PSTN and ISDN C-Paths may exist. A group of C-Paths are associated with a C-channel. The C-path for protection, however, is not carried in a C-channel.\"",
    "::=",
    "{",
    "zhoneV52",
    "5",
    "}"
  ],
  "syntax_tree": [
    [
      "conceptualTable",
      [
        "row",
        "V52CPathEntry"
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "not-accessible"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "C-paths consist of a layer 2 data link carrying an associated layer 3 signaling protocol. Layer 3 signaling is defined by the Control, Link Control, PSTN, BCC, and Protection protocols. Therefore, a C-path can exist for the Control protocol, the Link Control protocol, the PSTN protocol, the BCC protocol, and the Protection protocol. In addition, ISDN D-channel data is also carried over C-paths. Separate C-paths exist for ISDN Ds, p, and f-type data. There can only be one of each control, link control, and BCC C-Paths whereas multiple PSTN and ISDN C-Paths may exist. A group of C-Paths are associated with a C-channel. The C-path for protection, however, is not carried in a C-channel."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.5504)

Goldberg Allen

Direct children (1)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.5504.4.3.2.5.1 v52CPathEntry66

Siblings (11)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.5504.4.3.2.1 v52InterfaceGroupTable129
1.3.6.1.4.1.5504.4.3.2.2 v52InterfaceGroupLapvTable16
1.3.6.1.4.1.5504.4.3.2.3 v52LinkTable110
1.3.6.1.4.1.5504.4.3.2.4 v52CChannelTable19
1.3.6.1.4.1.5504.4.3.2.6 v52UserPortTable112
1.3.6.1.4.1.5504.4.3.2.7 v52StatsCurrentTable19
1.3.6.1.4.1.5504.4.3.2.8 v52StatsIntervalTable110
1.3.6.1.4.1.5504.4.3.2.9 v52StatsTotalTable19
1.3.6.1.4.1.5504.4.3.2.10 v52Traps19
1.3.6.1.4.1.5504.4.3.2.11 v52IgExtensionTable15
1.3.6.1.4.1.5504.4.3.2.12 v52ProtectionCPathTable14