Working SF MEP reference - max. 100-1 - min. 0. During get 100 indicate no reference
Sources for this description
FS.COM official Documentation Hub native MIB packages
OID reference
1.3.6.1.4.1.52642.9.45.1.2.4.1.2
Working SF MEP reference - max. 100-1 - min. 0. During get 100 indicate no reference
Identification
{1 3 6 1 4 1 52642 9 45 1 2 4 1 2}
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 VTSS-EPS-MIB, the row index vtssEpsConfigMepId 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.52642.9.45.1.2.4.1.2.<vtssEpsConfigMepId>. 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.52642.9.45.1.2.4.1.2
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.
Product context
The FS.COM catalogue lists MIB packages containing this definition for these models:
A definition in a model's MIB package does not establish that the device implements it or permits access.
The displayed source records contain one distinct definition. Compare its source records.
vtssEpsConfigMepWorkingMep OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Working SF MEP reference - max. 100-1 - min. 0. During get 100 indicate
no reference"
::= { vtssEpsConfigMepEntry 2 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Working SF MEP reference - max. 100-1 - min. 0. During get 100 indicate no reference
FS.COM official Documentation Hub native MIB packages
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: current.
Names: vtssEpsConfigMepWorkingMep
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"vtssEpsConfigMepWorkingMep",
"OBJECT-TYPE",
"SYNTAX",
"Unsigned32",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Working SF MEP reference - max. 100-1 - min. 0. During get 100 indicate no reference\"",
"::=",
"{",
"vtssEpsConfigMepEntry",
"2",
"}"
],
"syntax_tree": [
[
"ApplicationSyntax",
"Unsigned32"
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Working SF MEP reference - max. 100-1 - min. 0. During get 100 indicate no reference"
],
null,
null,
null,
null
]
}Module: VTSS-EPS-MIB
See published definition above
{'VTSS-TC': ['VTSSInterfaceIndex', 'VTSSRowEditorState'], 'VTSS-SMI': ['vtssSwitchMgmt'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'Integer32', 'Unsigned32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.52642.9.45.1.2.4.1.1 | vtssEpsConfigMepId | 0 | 0 | |
| 1.3.6.1.4.1.52642.9.45.1.2.4.1.3 | vtssEpsConfigMepProtectingMep | 0 | 0 | |
| 1.3.6.1.4.1.52642.9.45.1.2.4.1.4 | vtssEpsConfigMepApsMep | 0 | 0 |