OID reference
1.3.6.1.4.1.2076.13.11.2.1.1.36
If this entry corresponds to a trace route operation and if it is successful, this object indicates the hopcount to reach to egress node. If the trace route operation has failed, then this count indicates the node till which the connectivity exists correctly. This object is not applicable for ping operations.
Identification
{1 3 6 1 4 1 2076 13 11 2 1 1 36}
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. The index encoding is not inferred here.
Published row index: fsLsppContextId, fsLsppSenderHandle.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.2076.13.11.2.1.1.36
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.
fsLsppActualHopCount OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"If this entry corresponds to a trace route operation and if it is
successful, this object indicates the hopcount to reach to egress
node.
If the trace route operation has failed, then this count indicates
the node till which the connectivity exists correctly.
This object is not applicable for ping operations."
::= { fsLsppPingTraceTableEntry 36 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
If this entry corresponds to a trace route operation and if it is successful, this object indicates the hopcount to reach to egress node. If the trace route operation has failed, then this count indicates the node till which the connectivity exists correctly. This object is not applicable for ping operations.
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)Belden, GarrettCom and Hirschmann IT official standalone MIBs
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: fsLsppActualHopCount
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsLsppActualHopCount",
"OBJECT-TYPE",
"SYNTAX",
"Unsigned32",
"MAX-ACCESS",
"read-only",
"STATUS",
"current",
"DESCRIPTION",
"\"If this entry corresponds to a trace route operation and if it is successful, this object indicates the hopcount to reach to egress node. If the trace route operation has failed, then this count indicates the node till which the connectivity exists correctly. This object is not applicable for ping operations.\"",
"::=",
"{",
"fsLsppPingTraceTableEntry",
"36",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Unsigned32"
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"If this entry corresponds to a trace route operation and if it is successful, this object indicates the hopcount to reach to egress node. If the trace route operation has failed, then this count indicates the node till which the connectivity exists correctly. This object is not applicable for ping operations."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: ARICENT-LSP-PING-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'DisplayString', 'RowPointer', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'enterprises', 'Unsigned32', 'Integer32', 'Counter32']}Related source files and packages:
Module: ARICENT-LSP-PING-MIB
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'RowStatus', 'DisplayString', 'RowPointer', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'enterprises', 'Unsigned32', 'Integer32', 'Counter32']}Related source files and packages:
Registration