mtu(8) System Manager's Manual mtu(8)NAME
mtu - POLYCENTER Common Agent MIB Translator Utility
SYNOPSIS
/usr/sbin/mtu [-ccode] [-i] [-l] file.mib [file.mib]...
OPTIONS
Specify the EMA entity code to be assigned to the root entity. Produce an informational parameter file for input to the POLYCENTER Common
Agent momgen utility (file.par). Produce a listing file containing the MIB information from the file.mib file and a summary of the mapping
to EMA hierarchical structures in the file.lis file.
DESCRIPTION
The mtu utility translates MIB specification files (.mib) into EMA Management Specification files (.ms). The management specifications can
be loaded into the POLYCENTER Common Agent Management Information Repository (MIR) by the /usr/sbin/mirc utility.
The MIB structure and syntax is described by Concise MIB Definitions (RFC-1212). The EMA Management Specification Language is described by
the DECmcc System Reference Manual.
If the Common Agent Developer's Toolkit layered product is installed, the mtu utility can also produce momgen information files (file.par)
from the MIB specification.
EXAMPLES
The following example translates the superbox.mib MIB file into the MSL file superbox.msl (named by derivation), specifying 1000 as the EMA
root entity. An information parameter superbox.par is created that can be use with the momgen utility. # mtu -c 1000 -i superbox.mib The
following example translates all of the MIB files in the current working directory into MSL files. For each MIB file, mtu produces the MSL
file (.msl), a listing file (.lis), and a momgen informational parameter file (.par). # mtu -i -l *.mib The following example translates
the tinybox.mib MIB file into the MSL file tinybox.msl, specifying 500 as the EMA root entity. A momgen informational parameter file
(tinybox.par) is also generated. The smallbox.mib MIB file is translated into the MSL file smallbox.msl, specifying 1000 as the EMA root
entity. A momgen informational parameter file (smallbox.par) is also generated. # mtu -c 500 -i tinybox.mib -c 1000 -i smallbox.mib
FILES
A listing file that contains a numbered version of the MIB input file followed by a hierarchical management specification summary. If
errors are encountered, this file contains the diagnostic at the line where the error occurred. MIB input file. MSL output file. The
momgen informational parameter file. It contains class, parent, and prefix information used by the momgen utility when generating a Man-
aged Object Module.
SEE ALSO
Concise MIB Definition (RFC 1212)
Convention for Defining Traps (RFC 1215)
DECmcc System Reference Manual
mtu(8)
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)