OID reference
1.3.6.1.4.1.1411.102.102.13.1
Setting this value to clear-master(2) clears the entire master FDB, Setting this value to clear-static(3) clears the entire static FDB.
Identification
{1 3 6 1 4 1 1411 102 102 13 1}
| Value | Name |
|---|---|
| 1 | ok |
| 2 | clear-master |
| 3 | clear-static |
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.1411.102.102.13.1.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.
fdbClear OBJECT-TYPE
SYNTAX INTEGER {
ok(1),
clear-master(2),
clear-static(3)
}
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"Setting this value to clear-master(2) clears the entire master FDB,
Setting this value to clear-static(3) clears the entire static FDB."
::= { fdb 1 }
Meaning
Identical descriptions are grouped. Different wording and device-specific notes are retained.
Setting this value to clear-master(2) clears the entire master FDB, Setting this value to clear-static(3) clears the entire static FDB.
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: fdbClear
{
"smi_kind": "OBJECT-TYPE",
"definition": [
"fdbClear",
"OBJECT-TYPE",
"SYNTAX",
"INTEGER",
"{",
"ok",
"(",
"1",
")",
",",
"clear-master",
"(",
"2",
")",
",",
"clear-static",
"(",
"3",
")",
"}",
"MAX-ACCESS",
"read-write",
"STATUS",
"current",
"DESCRIPTION",
"\"Setting this value to clear-master(2) clears the entire master FDB, Setting this value to clear-static(3) clears the entire static FDB.\"",
"::=",
"{",
"fdb",
"1",
"}"
],
"syntax_tree": [
[
"SimpleSyntax",
"INTEGER",
[
"enumSpec",
[
[
"ok",
1
],
[
"clear-master",
2
],
[
"clear-static",
3
]
]
]
],
null,
[
"MaxAccessPart",
"read-write"
],
[
"Status",
"current"
],
[
"DESCRIPTION",
"Setting this value to clear-master(2) clears the entire master FDB, Setting this value to clear-static(3) clears the entire static FDB."
],
null,
null,
null,
null
]
}Vendor MIB copy from the Observium Community archive.
Module: EX2500-BASE-MIB
See published definition above
{'IF-MIB': ['ifIndex', 'InterfaceIndex', 'InterfaceIndexOrZero'], 'SNMPv2-TC': ['TEXTUAL-CONVENTION', 'TruthValue', 'DisplayString', 'PhysAddress', 'MacAddress', 'RowStatus', 'TimeInterval', 'TimeStamp'], 'BRIDGE-MIB': ['BridgeId', 'dot1dTp', 'dot1dTpPort', 'dot1dBridge', 'dot1dBasePortEntry', 'dot1dBasePort'], 'SNMPv2-SMI': ['OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'OBJECT-IDENTITY', 'enterprises', 'Integer32', 'Unsigned32', 'Counter32', 'Gauge32', 'Counter64', 'TimeTicks', 'IpAddress', 'mib-2'], 'RFC1213-MIB': ['sysName', 'sysLocation', 'sysContact', 'ifIndex'], 'SNMPv2-CONF': ['MODULE-COMPLIANCE', 'OBJECT-GROUP', 'NOTIFICATION-GROUP'], 'P-BRIDGE-MIB': ['EnabledStatus'], 'Q-BRIDGE-MIB': ['PortList'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString', 'SnmpEngineID', 'SnmpMessageProcessingModel', 'SnmpSecurityModel', 'SnmpSecurityLevel'], 'SNMP-USER-BASED-SM-MIB': ['usmNoAuthProtocol', 'usmNoPrivProtocol']}Related source files and packages:
Registration
| OID | Name | Direct children | Descendants | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.1411.102.102.13.2 | fdbStatsCurrent | 0 | 0 | |
| 1.3.6.1.4.1.1411.102.102.13.3 | fdbStatsHiwat | 0 | 0 | |
| 1.3.6.1.4.1.1411.102.102.13.4 | fdbStatsClear | 0 | 0 | |
| 1.3.6.1.4.1.1411.102.102.13.5 | fdbTable | 1 | 12 | |
| 1.3.6.1.4.1.1411.102.102.13.6 | fdbDisableAging | 0 | 0 | |
| 1.3.6.1.4.1.1411.102.102.13.7 | fdbNewCfgStaticTable | 1 | 6 | |
| 1.3.6.1.4.1.1411.102.102.13.8 | fdbAgingTime | 0 | 0 |