All MIBs › RFC-1493
Organization: IETF Bridge MIB Working Group
Last Updated: 1993-07-31
Description: Compatibility stub for the hyphenated RFC-1493 form of the classic IEEE 802.1D BRIDGE-MIB, supplying MacAddress, BridgeId, Timeout, and dot1dBasePort to dependent MIBs
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is RFC-1493?
RFC-1493 is a compatibility stub module providing the hyphenated naming form of the classic BRIDGE-MIB (originally published as RFC 1493), which manages IEEE 802.1D transparent bridging. It exists so that other MIB modules importing an "RFC-1493" style module name can resolve, carrying through core bridge textual conventions and objects such as MacAddress, BridgeId, Timeout, and dot1dBasePort. Its underlying subject matter, the real BRIDGE-MIB, covers switch/bridge port status, spanning-tree state, and forwarding-table data, so where those objects are implemented they support monitoring bridge port operational status and Layer-2 topology health, though this stub itself is mainly a naming/compatibility shim. It is directly dependent on, and essentially aliases, the standard IEEE 802.1D BRIDGE-MIB (RFC 1493). It is encountered in MIB repositories and compilers as a dependency resolved when loading vendor MIBs that reference the hyphenated "RFC-1493" import name for bridge objects like dot1dBase and dot1dBridge. Engineers implementing or auditing this functionality typically reference the RFC-1493 RFC/standard documentation for the authoritative specification.
IPNetwork Monitor allows you to monitor SNMP objects defined in RFC-1493. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- vendor-neutral, standards-based MIB, not tied to a specific manufacturer
- IEEE 802.1D transparent bridge/switch
Monitoring Examples
This module is primarily a naming stub rather than a source of its own data; it re-exposes objects like dot1dBasePort (identifying which bridge port a table row concerns) and the dot1dBase/dot1dBridge groups from the real BRIDGE-MIB. In practice a management tool would use the underlying BRIDGE-MIB's dot1dBasePortTable, indexed via dot1dBasePort, to monitor per-port bridging status, but this stub itself contributes no additional monitorable objects beyond making those imports resolvable.
What Can Be Monitored
- bridge port identification (dot1dBasePort)
- bridge base group objects
- compatibility resolution for BRIDGE-MIB imports
Imported Objects
From SNMPv2-SMI
| Integer32 | |
| MODULE-IDENTITY | |
| OBJECT-TYPE | |
| mib-2 |
From SNMPv2-TC
| TEXTUAL-CONVENTION |
OIDs
RFC description
Defined in RFC 1493, the Bridge MIB; manages bridge and spanning tree functionality in network switches.
Start monitoring vendor-neutral, standards-based MIB, IEEE 802.1D transparent bridge/switch (compatibility stub for BRIDGE-MIB) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.