MTU value of bridge. value range:256 to 1500 There can not be relation and it sets, and it refer the number of branch.
Sources for this description
Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)
OID reference
1.3.6.1.4.1.119.2.3.69.5.3.16.1.1.5
MTU value of bridge. value range:256 to 1500 There can not be relation and it sets, and it refer the number of branch.
Identification
{1 3 6 1 4 1 119 2 3 69 5 3 16 1 1 5}
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 IPE-SYSTEM-MIB, the row index ipeCfgBridgeIndex 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.119.2.3.69.5.3.16.1.1.5.<ipeCfgBridgeIndex>. 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.119.2.3.69.5.3.16.1.1.5
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.
ipeCfgBridgeMtu OBJECT-TYPE
SYNTAX Integer32 (256..1500)
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"MTU value of bridge.
value range:256 to 1500
There can not be relation and it sets, and it refer the number of
branch."
::= { ipeCfgBridgeEntry 5 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
MTU value of bridge. value range:256 to 1500 There can not be relation and it sets, and it refer the number of branch.
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: ipeCfgBridgeMtu
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"ipeCfgBridgeMtu",
"OBJECT-TYPE",
"SYNTAX",
"Integer32",
"(",
"256",
".",
".",
"1500",
")",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"MTU value of bridge. value range:256 to 1500 There can not be relation and it sets, and it refer the number of branch.\"",
"::=",
"{",
"ipeCfgBridgeEntry",
"5",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"Integer32",
[
"integerSubType",
[
[
256,
1500
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"MTU value of bridge. value range:256 to 1500 There can not be relation and it sets, and it refer the number of branch."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: IPE-SYSTEM-MIB
See published definition above
{'IF-MIB': ['InterfaceIndex'], 'SNMPv2-TC': ['DateAndTime', 'DisplayString', 'MacAddress', 'RowStatus', 'TEXTUAL-CONVENTION'], 'BRIDGE-MIB': ['BridgeId', 'Timeout'], 'SNMPv2-SMI': ['Counter32', 'enterprises', 'Integer32', 'IpAddress', 'NOTIFICATION-TYPE', 'OBJECT-TYPE', 'Opaque']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.119.2.3.69.5.3.16.1.1.1 | ipeCfgBridgeIndex | 0 | 0 | |
| 1.3.6.1.4.1.119.2.3.69.5.3.16.1.1.2 | ipeCfgBridgeNEAddress | 0 | 0 | |
| 1.3.6.1.4.1.119.2.3.69.5.3.16.1.1.3 | ipeCfgBridgeIpAddress | 0 | 0 | |
| 1.3.6.1.4.1.119.2.3.69.5.3.16.1.1.4 | ipeCfgBridgeNetMask | 0 | 0 |