You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Of all things SNMP, the BRIDGE-MIB is one of the most useful features. With #1651 merged, the BRIDGE-MIB is closer than ever. Checking what statd already publishes, most of it is there:
dot1qVlanCurrentTable / VlanStaticTable and dot1qPortVlanTable — VLAN membership and PVID: present
dot1dBasePortTable — falls out of every port being a netdev with an if-index
What's genuinely missing is the FDB (dot1dTpFdbTable, dot1qTpFdbTable) and dot1dTpAgingTime. Neither infix-if-bridge.yang nor statd has any notion of a forwarding database.
Read-only SNMP support is in flight: an agent configured from ietf-snmp
(RFC 7407), serving SNMPv2-MIB, IF-MIB, HOST-RESOURCES-MIB, UCD-SNMP-MIB and
LLDP-MIB. Notes on what BRIDGE-MIB needs on top of that, so this can be
scheduled.
The agent is no longer the hard part
confd starts snmpd with master agentx and lldpd already attaches to it to
serve LLDP-MIB, so a subagent registering the bridge subtrees has somewhere to
plug in. net-snmp ships neither BRIDGE-MIB nor Q-BRIDGE-MIB in any build
configuration, and the three implementations linked above are unmaintained, so
this is ours to write regardless.
Most of the data is already in the operational datastore
MIB object
Status
dot1dBasePortTable
derivable, every port is a netdev with an if-index
dot1dStp*
have it: state, role, port-id, designated bridge, topology changes
dot1qVlanCurrentTable, dot1qVlanStaticTable
have it, per-port VLAN membership
dot1qPortVlanTable (PVID)
have it
dot1dTpFdbTable, dot1qTpFdbTable
missing
dot1dTpAgingTime
missing
So the prerequisite is the forwarding database
There is no FDB in infix-if-bridge or in the operational datastore today. bridge -j fdb show gives it directly and nothing reads it yet, so the
plumbing is small. The open question is modelling: we import ieee802-dot1q-types but not ieee802-dot1q-bridge, which carries filtering-database/filtering-entry. Worth deciding whether to adopt that
subtree or put the FDB in infix-if-bridge.
That is worth having on its own merits, independent of SNMP. A MAC table over
NETCONF/RESTCONF and a show bridge fdb in the CLI get asked for regularly.
Suggest splitting it into its own issue and making this one depend on it.
Suggested order
FDB in the operational datastore, plus bridge ageing time, as its own issue
AgentX subagent serving BRIDGE-MIB and Q-BRIDGE-MIB from operational data
Activity
troglobit commentedon Sep 22, 2026
Read-only SNMP support is in flight: an agent configured from
ietf-snmp(RFC 7407), serving SNMPv2-MIB, IF-MIB, HOST-RESOURCES-MIB, UCD-SNMP-MIB and
LLDP-MIB. Notes on what BRIDGE-MIB needs on top of that, so this can be
scheduled.
The agent is no longer the hard part
confd starts snmpd with
master agentxand lldpd already attaches to it toserve LLDP-MIB, so a subagent registering the bridge subtrees has somewhere to
plug in. net-snmp ships neither BRIDGE-MIB nor Q-BRIDGE-MIB in any build
configuration, and the three implementations linked above are unmaintained, so
this is ours to write regardless.
Most of the data is already in the operational datastore
dot1dBasePortTableif-indexdot1dStp*dot1qVlanCurrentTable,dot1qVlanStaticTabledot1qPortVlanTable(PVID)dot1dTpFdbTable,dot1qTpFdbTabledot1dTpAgingTimeSo the prerequisite is the forwarding database
There is no FDB in
infix-if-bridgeor in the operational datastore today.bridge -j fdb showgives it directly and nothing reads it yet, so theplumbing is small. The open question is modelling: we import
ieee802-dot1q-typesbut notieee802-dot1q-bridge, which carriesfiltering-database/filtering-entry. Worth deciding whether to adopt thatsubtree or put the FDB in
infix-if-bridge.That is worth having on its own merits, independent of SNMP. A MAC table over
NETCONF/RESTCONF and a
show bridge fdbin the CLI get asked for regularly.Suggest splitting it into its own issue and making this one depend on it.
Suggested order
ietf-hardware, which overlaps Add system resource monitoring RESTCONF/NETCONF notifications (CPU, memory, disk, ...) #1102show bridge fdb#1653