OID reference
1.3.6.1.4.1.2076.26.1.1.3
Setting this object to with-CRC(1) expects all LAN frames to be received with CRC, and transmits through WAN and LAN interface with the same CRC without regeneration.
Identification
{1 3 6 1 4 1 2076 26 1 1 3}
| Value | Name |
|---|---|
| 1 | withCRC |
| 2 | withoutCRC |
At least one MIB declaration places this object in a scalar group. A scalar instance uses the suffix .0.
snmpget [connection options] DEVICE .1.3.6.1.4.1.2076.26.1.1.3.0
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.
dot1dBaseBridgeCRCStatus OBJECT-TYPE
SYNTAX INTEGER{
withCRC(1),
withoutCRC(2)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Setting this object to with-CRC(1) expects all LAN
frames to be received with CRC, and transmits through
WAN and LAN interface with the same CRC without
regeneration."
DEFVAL { withoutCRC }
::= { dot1dFutureBase 3 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Setting this object to with-CRC(1) expects all LAN frames to be received with CRC, and transmits through WAN and LAN interface with the same CRC without regeneration.
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: dot1dBaseBridgeCRCStatus
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"dot1dBaseBridgeCRCStatus",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"withCRC",
"(",
"1",
")",
",",
"withoutCRC",
"(",
"2",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Setting this object to with-CRC(1) expects all LAN frames to be received with CRC, and transmits through WAN and LAN interface with the same CRC without regeneration.\"",
"DEFVAL",
"{",
"withoutCRC",
"}",
"::=",
"{",
"dot1dFutureBase",
"3",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"withCRC",
1
],
[
"withoutCRC",
2
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Setting this object to with-CRC(1) expects all LAN frames to be received with CRC, and transmits through WAN and LAN interface with the same CRC without regeneration."
],
null,
null,
null,
[
"DEFVAL",
"withoutCRC"
]
]
}Vendor MIB copy from the Observium Community archive.
Module: ARICENT-BRIDGE-MIB
See published definition above
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'MacAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'OBJECT-IDENTITY', 'enterprises', 'Integer32', 'Counter32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP']}Related source files and packages:
Module: ARICENT-BRIDGE-MIB
{'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'MacAddress'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'OBJECT-IDENTITY', 'enterprises', 'Integer32', 'Counter32'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.2076.26.1.1.1 | dot1dBridgeSystemControl | 0 | 0 | |
| 1.3.6.1.4.1.2076.26.1.1.2 | dot1dBaseBridgeStatus | 0 | 0 | |
| 1.3.6.1.4.1.2076.26.1.1.4 | dot1dBaseBridgeDebug | 0 | 0 | |
| 1.3.6.1.4.1.2076.26.1.1.5 | dot1dBaseBridgeTrace | 0 | 0 | |
| 1.3.6.1.4.1.2076.26.1.1.6 | dot1dBaseBridgeMaxFwdDbEntries | 0 | 0 | |
| 1.3.6.1.4.1.2076.26.1.1.7 | dot1dFutureBasePortTable | 1 | 9 |