SNMP-BRIDGE-MIB(1)

💖 snmp-bridge-mib — the Net-SNMP glow-up for your Linux bridge 💖

okay bestie, listen. this is snmp-bridge-mib, a little extension to net-snmp that pulls info about a bridge on your Linux box and hands it out over SNMP so other (remote) systems can peek at it for management purposes. it's giving main character energy in /usr/bin. 🌉✨

✨ NAME ✨

snmp-bridge-mib — provide Linux bridge information via SNMP 🫶

🌸 SYNOPSIS 🌸

snmp-bridge-mib {bridge}

🎀 ARGUMENTS 🎀

the following arguments are required (yes, required, no skipsies):

• bridge — the name of the Linux bridge you want to expose info about via SNMP, like br0. that's the whole vibe. 💅

🦋 DESCRIPTION 🦋

snmp-bridge-mib is an extension to net-snmp, fr fr. it collects information about a bridge in a Linux system and exports it so other (remote) systems can query it for management purposes. that's it, that's the job. 👑

⭐ CONFIGURATION: ⭐

the preferred method for snmp-bridge-mib to attach to net-snmp is agentx. for that to work you gotta add this line to /etc/snmp/snmpd.conf:

master agentx

then restart snmpd and start snmp-bridge-mib. it will then connect to the running snmpd daemon. slay. 🔥

another way of attaching snmp-bridge-mib to is to run it as an embedded perl module. you have to add:

perl do "path to location of snmp-bridge-mib"

and restart snmpd. easy. periodt.

🌈 EXAMPLE: 🌈

follow the instructions in this manpage and type:

perl /usr/bin/snmp-bridge-mib br0

you´ll get the following output:

 registering at .1.3.6.1.2.1.17
 running as a subagent.
 dot1qbridge agent started.
 NET-SNMP version 5.4.2.1 AgentX subagent connected

now it´s time for a first test:

$ export MIBS=+BRIDGE-MIB
$ snmpwalk localhost .1.3.6.1.2.1.17

the output produced should look like:

BRIDGE-MIB::dot1dStpBridgeHelloTime = INTEGER: 199 centi-seconds
BRIDGE-MIB::dot1dStpBridgeForwardDelay = INTEGER: 1499 centi-seconds
BRIDGE-MIB::dot1dStpPort.1 = INTEGER: 1
BRIDGE-MIB::dot1dStpPort.3 = INTEGER: 3
BRIDGE-MIB::dot1dStpPortPriority.1 = INTEGER: 32
BRIDGE-MIB::dot1dStpPortPriority.3 = INTEGER: 32
BRIDGE-MIB::dot1dStpPortState.1 = INTEGER: disabled(1)
BRIDGE-MIB::dot1dStpPortState.3 = INTEGER: disabled(1)
BRIDGE-MIB::dot1dStpPortEnable.1 = INTEGER: disabled(2)
BRIDGE-MIB::dot1dStpPortEnable.3 = INTEGER: disabled(2)
BRIDGE-MIB::dot1dStpPortPathCost.1 = INTEGER: 2
BRIDGE-MIB::dot1dStpPortPathCost.3 = INTEGER: 4
BRIDGE-MIB::dot1dStpPortDesignatedRoot.1 = STRING: "8000.001018382c78"
BRIDGE-MIB::dot1dStpPortDesignatedRoot.3 = STRING: "8000.001018382c78"
BRIDGE-MIB::dot1dStpPortDesignatedCost.1 = INTEGER: 0
BRIDGE-MIB::dot1dStpPortDesignatedCost.3 = INTEGER: 0
BRIDGE-MIB::dot1dStpPortDesignatedBridge.1 = STRING: "8000.001018382c78"
BRIDGE-MIB::dot1dStpPortDesignatedBridge.3 = STRING: "8000.001018382c78"
BRIDGE-MIB::dot1dStpPortDesignatedPort.1 = STRING: "32769"
BRIDGE-MIB::dot1dStpPortDesignatedPort.3 = STRING: "32770"
BRIDGE-MIB::dot1dStpPortPathCost32.1 = INTEGER: 2
BRIDGE-MIB::dot1dStpPortPathCost32.3 = INTEGER: 4
BRIDGE-MIB::dot1dTpLearnedEntryDiscards = Counter32: 0
BRIDGE-MIB::dot1dTpAgingTime = INTEGER: 300 seconds
BRIDGE-MIB::dot1dTpFdbAddress.´...8,x´ = STRING: 0:10:18:38:2c:78
BRIDGE-MIB::dot1dTpFdbAddress.´.!^/B|´ = STRING: 0:21:5e:2f:42:7c
BRIDGE-MIB::dot1dTpFdbPort.´...8,x´ = INTEGER: 1
BRIDGE-MIB::dot1dTpFdbPort.´.!^/B|´ = INTEGER: 3
BRIDGE-MIB::dot1dTpFdbStatus.´...8,x´ = INTEGER: learned(3)
BRIDGE-MIB::dot1dTpFdbStatus.´.!^/B|´ = INTEGER: learned(3)
BRIDGE-MIB::dot1dTpPort.1 = INTEGER: 1
BRIDGE-MIB::dot1dTpPort.3 = INTEGER: 3
BRIDGE-MIB::dot1dTpPortMaxInfo.1 = INTEGER: 1500 bytes
BRIDGE-MIB::dot1dTpPortMaxInfo.3 = INTEGER: 1500 bytes
BRIDGE-MIB::dot1dTpPortInFrames.1 = Counter32: 18082 frames
BRIDGE-MIB::dot1dTpPortInFrames.3 = Counter32: 1546072 frames
BRIDGE-MIB::dot1dTpPortOutFrames.1 = Counter32: 11601 frames
BRIDGE-MIB::dot1dTpPortOutFrames.3 = Counter32: 10988 frames
BRIDGE-MIB::dot1dTpPortInDiscards.1 = Counter32: 0 frames
BRIDGE-MIB::dot1dTpPortInDiscards.3 = Counter32: 0 frames

like, look at all that data. it's so much. we love to see it. 😭💖

💀 BUGS 💀

1. snmp-bridge-mib currently only supports one bridge, which has to be specified on the commandline. one bridge only, bestie. no polyamory here. 🙈
2. Not all elements of RFC 4188 because they are either not available in sysfs or difficult to extract from the existing data. some stuff is just, like, not there. 💅

👑 SEE ALSO 👑

snmpd.conf(5), Net::SNMP(3)

💜 AUTHOR 💜

Jens Osterkamp <jens@linux.vnet.ibm.com>

• Developer

🎀 COPYRIGHT 🎀

Copyright © 2009, 2010 IBM Corp., All Rights Reserved

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

and that's the whole page, bestie. this came from the Net-SNMP crew, version v6, dated 26 Mar 2010, and it lives at http://www.ibm.com/. go walk a bridge or something. mwah. 💅✨🦋