OID reference
1.3.6.1.4.1.29601.2.45.1.1.4.1.1
A 32-bit unique context identifier for each entry. Each virtual context will be able to run PTP protocol individually and this distinguishes mutiple virtual contexts present in the switch/router.
Identification
{1 3 6 1 4 1 29601 2 45 1 1 4 1 1}
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 ARICENT-PTP-MIB, the row index fsPtpContextId is declared as Integer32. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.29601.2.45.1.1.4.1.1.<fsPtpContextId>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.
A query example is omitted because the source variants do not establish compatible read access.
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.
fsPtpContextId OBJECT-TYPE
SYNTAX Integer32 (0..255)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A 32-bit unique context identifier for each entry. Each virtual
context will be able to run PTP protocol individually and this
distinguishes mutiple virtual contexts present in the switch/router."
::= { fsPtpEntry 1 }fsPtpContextId OBJECT-TYPE
SYNTAX Integer32 (0..255)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"A 32-bit unique context identifier for each entry. Each virtual
context will be able to run PTP protocol individually and this
distinguishes multiple virtual contexts present in the switch/router."
::= { fsPtpEntry 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Description 1
A 32-bit unique context identifier for each entry. Each virtual context will be able to run PTP protocol individually and this distinguishes mutiple virtual contexts present in the switch/router.
Belden, GarrettCom and Hirschmann IT official standalone MIBs
Description 2
A 32-bit unique context identifier for each entry. Each virtual context will be able to run PTP protocol individually and this distinguishes multiple virtual contexts present in the switch/router.
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: fsPtpContextId
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsPtpContextId",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"0",
".",
".",
"255",
")",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"A 32-bit unique context identifier for each entry. Each virtual context will be able to run PTP protocol individually and this distinguishes mutiple virtual contexts present in the switch/router.\"",
"::=",
"{",
"fsPtpEntry",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"A 32-bit unique context identifier for each entry. Each virtual context will be able to run PTP protocol individually and this distinguishes mutiple virtual contexts present in the switch/router."
],
null,
null,
null,
null
]
}Module: ARICENT-PTP-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus', 'TimeStamp', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'enterprises', 'NOTIFICATION-TYPE']}Related source files and packages:
Status in source: current.
Names: fsPtpContextId
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fsPtpContextId",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"0",
".",
".",
"255",
")",
"MAX-ACCESS",
"not-accessible",
"STATUS",
"current",
"DESCRIPTION",
"\"A 32-bit unique context identifier for each entry. Each virtual context will be able to run PTP protocol individually and this distinguishes multiple virtual contexts present in the switch/router.\"",
"::=",
"{",
"fsPtpEntry",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
0,
255
]
]
]
],
null,
[
"MaxAccessPart",
"not-accessible"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"A 32-bit unique context identifier for each entry. Each virtual context will be able to run PTP protocol individually and this distinguishes multiple virtual contexts present in the switch/router."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: ARICENT-PTP-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'RowStatus', 'TimeStamp', 'DisplayString'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32', 'enterprises', 'NOTIFICATION-TYPE']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.29601.2.45.1.1.4.1.2 | fsPtpAdminStatus | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.45.1.1.4.1.3 | fsPtpTraceOption | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.45.1.1.4.1.4 | fsPtpContextType | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.45.1.1.4.1.5 | fsPtpPrimaryDomain | 0 | 0 | |
| 1.3.6.1.4.1.29601.2.45.1.1.4.1.6 | fsPtpContextRowStatus | 0 | 0 |