OID reference
1.3.6.1.4.1.72.9.6.11
For 2265's and 4660's, the Mac address of both ports is the same, thus rather than use the Mac address field of the ieee8023 group we will define a single element in the bridge group. Should a future bridge have different mac addresses for each port then we can make use of the ieee8023 defined element.
Identification
{1 3 6 1 4 1 72 9 6 11}
Definitions may combine these properties differently.
Numbers refer to source variants above. Each value is shown only for variants that define it. Notes below names come from selected MIB definitions.
| Value | Name and source notes | Source variants |
|---|---|---|
| 3 | revisionC ready to pass packets | 1 |
| 8 | revision8 | 1 |
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.72.9.6.11.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.
Available source records contain 2 distinct definitions; some records may not include a definition.
locbrdgSpatVersion OBJECT-TYPE
SYNTAX INTEGER {
revisionC(3), -- ready to pass packets
revision8(8)
}
ACCESS read-only
STATUS optional
DESCRIPTION ""
::= { locbrdg 11 }locbrdgId OBJECT-TYPE
SYNTAX OCTET STRING (SIZE(6))
ACCESS read-only
STATUS optional
DESCRIPTION
"For 2265's and 4660's, the Mac address of both ports is the same,
thus rather than use the Mac address field of the ieee8023 group we
will define a single element in the bridge group. Should a future
bridge have different mac addresses for each port then we can make
use of the ieee8023 defined element."
::= { locbrdg 11 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
For 2265's and 4660's, the Mac address of both ports is the same, thus rather than use the Mac address field of the ieee8023 group we will define a single element in the bridge group. Should a future bridge have different mac addresses for each port then we can make use of the ieee8023 defined element.
Retix Local Bridge MIB in the historical IETF archive
Evidence
Matching descriptions are grouped; open a group to compare definitions and supporting files.
Status in source: optional.
Names: locbrdgSpatVersion
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"locbrdgSpatVersion",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"revisionC",
"(",
"3",
")",
",",
"revision8",
"(",
"8",
")",
"}",
"ACCESS",
"read-only",
"STATUS",
"optional",
"DESCRIPTION",
"\"\"",
"::=",
"{",
"locbrdg",
"11",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"revisionC",
3
],
[
"revision8",
8
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"optional"
],
[
"DESCRIPTION",
""
],
null,
null,
null,
null
]
}Module: RETIX-LOCAL-ROUTER-MIB
See published definition above
{'RFC1065-SMI': ['mgmt', 'OBJECT-TYPE', 'NetworkAddress', 'IpAddress', 'Counter', 'Gauge', 'TimeTicks']}Source data warning: Historical Retix Local Bridge/Router MIB version 1.0, dated 12 January 1993, preserved in a mirror of the IETF private MIB archive. The archive does not make this vendor file an IETF standard. Its DESCRIPTION clauses are empty. It uses the standard internet root without importing it; this root is supplied from RFC 1065 for this exact reviewed file only.
· Download Retix Local Router MIB version 1.0 — historical IETF archiveRelated source files and packages:
Status in source: optional.
Names: locbrdgId
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"locbrdgId",
"OBJECT-TYPE",
"SYNTAX",
"OCTET",
"STRING",
"(",
"SIZE",
"(",
"6",
")",
")",
"ACCESS",
"read-only",
"STATUS",
"optional",
"DESCRIPTION",
"\"For 2265's and 4660's, the Mac address of both ports is the same, thus rather than use the Mac address field of the ieee8023 group we will define a single element in the bridge group. Should a future bridge have different mac addresses for each port then we can make use of the ieee8023 defined element.\"",
"::=",
"{",
"locbrdg",
"11",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"OCTET STRING",
[
"octetStringSubType",
[
[
6
]
]
]
],
null,
[
"MaxAccessPart",
"read-only"
],
[
"Status",
"optional"
],
[
"DESCRIPTION",
"For 2265's and 4660's, the Mac address of both ports is the same, thus rather than use the Mac address field of the ieee8023 group we will define a single element in the bridge group. Should a future bridge have different mac addresses for each port then we can make use of the ieee8023 defined element."
],
null,
null,
null,
null
]
}Module: RETIX-LOCAL-BRIDGE-MIB
See published definition above
{'RFC1065-SMI': ['mgmt', 'OBJECT-TYPE', 'NetworkAddress', 'IpAddress', 'Counter', 'Gauge', 'TimeTicks']}Source data warning: Historical Retix Local Bridge MIB version 2.0 (1993), preserved in a mirror of the IETF private MIB archive. The archive does not make this vendor file an IETF standard; applicability is limited to the products named in the file. The original omits imports for enterprises, system and interfaces. These three standard roots are supplied from RFC 1065 and RFC 1066 for this exact reviewed file only.
· Download Retix Local Bridge MIB version 2.0 — historical IETF archiveRelated source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.72.9.6.1 | locbrdgNumber | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.2 | locbrdgTable | 1 | 15 | |
| 1.3.6.1.4.1.72.9.6.3 | locbrdgBridgeMode | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.4 | locbrdgDefaultBridgeMode | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.5 | locbrdgFilterMatches | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.6 | locbrdgSpanningTreeMode, locbrdgSpanTreeMode | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.7 | locbrdgDefaultSpanTreeMode | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.8 | locbrdgSpatHelloTimer | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.9 | locbrdgDefaultSpatHelloTimer | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.10 | locbrdgHoldTime | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.12 | locbrdgSpatVersion, locbrdgDefaultSpatVersion | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.13 | locbrdgDefaultSpatVersion, locbrdgMaxAge | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.14 | locbrdgMaxAge, locbrdgDefaultBridgeMaxAge | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.15 | locbrdgDefaultBridgeMaxAge, locbrdgLiveBridgeForwardDelay | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.16 | locbrdgLiveBridgeForwardDelay, locbrdgBridgeForwardDelay | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.17 | locbrdgBridgeForwardDelay, locbrdgDefaultBridgeForwardDelay | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.18 | locbrdgDefaultBridgeForwardDelay, locbrdgTopologyChangeCount | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.19 | locbrdgTopologyChangeCount, locbrdgRangeDataBaseTable | 3 | 11 | |
| 1.3.6.1.4.1.72.9.6.20 | locbrdgRangeDataBaseTable, locbrdgFilterDataBaseTable | 3 | 12 | |
| 1.3.6.1.4.1.72.9.6.21 | locbrdgFilterDataBaseTable, locbrdgLiveSpatHelloTimer | 3 | 9 | |
| 1.3.6.1.4.1.72.9.6.22 | locbrdgLiveMaxAge | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.23 | locbrdgDefaultHoldTime | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.24 | locbrdgLiveSpatHelloTimer, locbrdgPriority | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.25 | locbrdgLiveMaxAge, locbrdgDefaultPriority | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.26 | locbrdgDefaultHoldTime | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.27 | locbrdgPriority | 0 | 0 | |
| 1.3.6.1.4.1.72.9.6.28 | locbrdgDefaultPriority | 0 | 0 |