OID reference
1.3.6.1.4.1.1038.110.100.2.1.11
The path trace is a user string that always follows the vc4. If the value the received path trace does not match this one, a tim (Trail Identifier Mismatch) failure is issued. The value `? ' match all possible received path trace.
Identification
{1 3 6 1 4 1 1038 110 100 2 1 11}
At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.
In SDH-ETS-MIB, the row index vc4TTPIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.1038.110.100.2.1.11.<vc4TTPIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1038.110.100.2.1.11
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.
The displayed source records contain one distinct definition. Compare its source records.
vc4TTPPathTraceExpected OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (16))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The path trace is a user string that always follows the vc4.
If the value the received path trace does not match this one, a
tim (Trail Identifier Mismatch) failure is issued.
The value `? ' match all possible received path trace."
::= { vc4TTPEntry 11 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
The path trace is a user string that always follows the vc4. If the value the received path trace does not match this one, a tim (Trail Identifier Mismatch) failure is issued. The value `? ' match all possible received path trace.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: vc4TTPPathTraceExpected
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vc4TTPPathTraceExpected",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"(",
"SIZE",
"(",
"16",
")",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"The path trace is a user string that always follows the vc4. If the value the received path trace does not match this one, a tim (Trail Identifier Mismatch) failure is issued. The value `? ' match all possible received path trace.\"",
"::=",
"{",
"vc4TTPEntry",
"11",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING",
[
"octetStringSubType",
[
[
16
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"The path trace is a user string that always follows the vc4. If the value the received path trace does not match this one, a tim (Trail Identifier Mismatch) failure is issued. The value `? ' match all possible received path trace."
],
null,
null,
null,
null
]
}Vendor MIB copy from the LibreNMS archive.
Module: SDH-ETS-MIB
See published definition above
{'SNMPv2-TC': ['DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE'], 'SAGEM-DR-MIB': ['sagemDr'], 'EQUIPMENT-MIB': ['SagemBoolean', 'Severity']}Related source files and packages:
Same file in Observium Community.
Registration