SNMP_BRIDGE(3) BSD Library Functions Manual SNMP_BRIDGE(3)NAME
snmp_bridge -- bridge module for snmpd
LIBRARY
(begemotSnmpdModulePath."bridge" = /usr/lib/snmp_bridge.so)
DESCRIPTION
The snmp_bridge module implements the BRIDGE-MIB as standardized in RFC 4188, the RSTP-MIB standardized in RFC4318 and a private BEGEMOT-
BRIDGE-MIB, which allows management of multiple bridge interfaces. Most of the objects defined in the private BEGEMOT-BRIDGE-MIB are dupli-
cates of the original objects defined by the standard BRIDGE-MIB, but the private MIB also defines additional objects which make the func-
tionality of snmp_bridge similar to ifconfig(8) for configuring bridge interfaces. Therefore one should consider adding write communities or
loading the snmp_bridge module on systems where security is crucial.
IMPLEMENTATION NOTES
The additional objects to configure a bridge are:
begemotBridgeBaseStatus
Bridge interfaces can be created and destroyed via this object. SNMP SET operations with the following values are allowed:
createAndWait will attempt to create a bridge interface with the name given by the table index.
createAndGo will attempt to create a bridge interface with the name given by the table index and set the status of the inter-
face to "active/up".
destroy will attempt to destroy the bridge interface.
begemotBridgeBaseSpanEnabled
A SNMP SET operation on this object is only successful if the corresponding port has not been added as member of the bridge inter-
face on the system.
begemotBridgeBasePortStatus
SNMP SET operations with the following values are allowed:
createAndWait will create a new row for the bridge member in the SNMP begemotBridgeBasePortTable but will not try to commit the
information to the system.
active will attempt to commit the information to the system and will be successful only if a value for
begemotBridgeBaseSpanEnabled has been SET already.
destroy will attempt to remove the interface from the system bridge interface.
begemotBridgeBasePortPrivate
This object controls a bridge interface flag called PRIVATE where any private port can not communicate with another private port.
RESTRICTIONS
Not all information in the MIBs is currently available in FreeBSD. The following variables carry no information:
dot1dBasePortCircuit
dot1dBasePortDelayExceededDiscards
dot1dBasePortMtuExceededDiscards
begemotBridgeBasePortDelayExceededDiscards
begemotBridgeBasePortMtuExceededDiscards
FILES
/usr/share/snmp/defs/bridge_tree.def
The description of the MIB tree implemented by snmp_bridge.
/usr/share/snmp/mibs/BRIDGE-MIB.txt
This is the BRIDGE-MIB that is implemented by this module.
/usr/share/snmp/mibs/RSTP-MIB.txt
This is the RSTP-MIB implemented by this module.
/usr/share/snmp/mibs/BEGEMOT-BRIDGE-MIB.txt
This is the private BEGEMOT-BRIDGE-MIB that is implemented by this module.
SEE ALSO bsnmpd(1), gensnmptree(1), snmpmod(3), if_bridge(4), ifconfig(8)AUTHORS
Shteryana Shopova <syrinx@FreeBSD.org>
BSD August 6, 2007 BSD
Check Out this Related Man Page
SNMP-BRIDGE-MIB(1) Net-SNMP SNMP-BRIDGE-MIB(1)NAME
snmp-bridge-mib - provide Linux bridge information via SNMP
SYNOPSIS
snmp-bridge-mib {bridge}
ARGUMENTS
The following arguments are required:
bridge
The name of the Linux bridge for which you want to provide information via SNMP, e.g. br0.
DESCRIPTION
The snmp-bridge-mib is an extension to net-snmp. It collects information about a bridge in a Linux system and exports them for query from
other (remote) systems for management purposes.
CONFIGURATION :
The preferred method of snmp-bridge-mib to attach to net-snmp is agentx. For this to work, you will have to add the following line to
/etc/snmp/snmpd.conf,
master agentx
restart snmpd and start snmp-bridge-mib. snmp-bridge-mib will then connect to the running snmpd daemon.
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.
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
BUGS
1. snmp-bridge-mib currently only supports one bridge which has to be specified on the commandline.
2. Not all elements of RFC 4188 because they are either not available in sysfs or difficult to extract from the existing data.
SEE ALSO snmpd.conf(5), Net::SNMP(3)AUTHOR
Jens Osterkamp <jens@linux.vnet.ibm.com>
Developer
COPYRIGHT
Copyright (C) 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.
http://www.ibm.com/ v6 26 Mar 2010 SNMP-BRIDGE-MIB(1)