This values decides whether frames are send without FCS(1), with FCS(2) or wether VC multiplexing is used.
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.272.4.16.22.1.7
This values decides whether frames are send without FCS(1), with FCS(2) or wether VC multiplexing is used.
Identification
{1 3 6 1 4 1 272 4 16 22 1 7}
Notes below names come from selected MIB definitions.
| Value | Name and source notes |
|---|---|
| 1 | bridged-no-fcs without frame checksum (FCS |
| 2 | bridged-fcs with frame checksum (FCS) |
| 3 | vc-multiplexed VC multiplexing |
| 10 | delete |
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: efmoaPvcAtmIfIndex, efmoaPvcDescr.
snmpwalk [connection options] DEVICE .1.3.6.1.4.1.272.4.16.22.1.7
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.
efmoaPvcEncapsulation OBJECT-TYPE
SYNTAX INTEGER {
bridged-no-fcs(1), -- without frame checksum (FCS
bridged-fcs(2), -- with frame checksum (FCS)
vc-multiplexed(3), -- VC multiplexing
delete(10)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"This values decides whether frames are send without FCS(1),
with FCS(2) or wether VC multiplexing is used."
DEFVAL { bridged-no-fcs }
::= { efmoaPvcEntry 7 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
This values decides whether frames are send without FCS(1), with FCS(2) or wether VC multiplexing is used.
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: efmoaPvcEncapsulation
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"efmoaPvcEncapsulation",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"bridged-no-fcs",
"(",
"1",
")",
",",
"bridged-fcs",
"(",
"2",
")",
",",
"vc-multiplexed",
"(",
"3",
")",
",",
"delete",
"(",
"10",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"This values decides whether frames are send without FCS(1), with FCS(2) or wether VC multiplexing is used.\"",
"DEFVAL",
"{",
"bridged-no-fcs",
"}",
"::=",
"{",
"efmoaPvcEntry",
"7",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"bridged-no-fcs",
1
],
[
"bridged-fcs",
2
],
[
"vc-multiplexed",
3
],
[
"delete",
10
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"This values decides whether frames are send without FCS(1), with FCS(2) or wether VC multiplexing is used."
],
null,
null,
null,
[
"DEFVAL",
"bridged-no-fcs"
]
]
}Vendor MIB copy from the Observium Community archive.
Module: BIANCA-BRICK-EFMOATM-MIB
See published definition above
{'RFC-1212': ['OBJECT-TYPE'], 'BINTEC-MIB': ['atm'], 'RFC1155-SMI': ['IpAddress', 'Counter', 'Gauge', 'TimeTicks', 'enterprises'], 'RFC1158-MIB': ['DisplayString'], 'RFC1213-MIB': ['PhysAddress']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.272.4.16.22.1.1 | efmoaPvcIfIndex | 0 | 0 | |
| 1.3.6.1.4.1.272.4.16.22.1.2 | efmoaPvcFilter | 0 | 0 | |
| 1.3.6.1.4.1.272.4.16.22.1.3 | efmoaPvcDescr | 0 | 0 | |
| 1.3.6.1.4.1.272.4.16.22.1.4 | efmoaPvcAtmIfIndex | 0 | 0 | |
| 1.3.6.1.4.1.272.4.16.22.1.5 | efmoaPvcVpi | 0 | 0 | |
| 1.3.6.1.4.1.272.4.16.22.1.6 | efmoaPvcVci | 0 | 0 | |
| 1.3.6.1.4.1.272.4.16.22.1.8 | efmoaPvcPhysAddress | 0 | 0 |