9 Monitoring generic SNMP OIDs with
MRTG
9.1 MRTG configuration file
review
MRTG tasks are running based on the options present
in the configuration file. A configuration file is required for each (or
multiple) monitored targets. As mentioned earlier, the MRTG tasks are started
as follows:
> perl mrtg [.cfg file]
As you can observe, the key element here is the configuration
file, which is a collection of MRTG option tags.
The option tags can be generated automatically by
running the CFGMAKER script against a target host. The script will build
the configuration file for that target, but only for the interface bandwidth
OIDs. The CFGMAKER script does not generate a configuration file aimed
to monitor other OIDs than Input/Output bandwidth for a network interface.
MRTG has the ability to monitor any SNMP OID that
a host can deliver. The CFGMKER script has limited action range here and
the configuration file has to be built manually.
The configuration file structure is made of 2 types
of option tags:
- Global options // define the way that MRTG
will handle the data collection for all targets within the file.
- Target options // define specific settings
used to collect the data and construct the graphs for each target.
The key option tag that makes the difference between
the standard MRTG configuration (input/output network bandwidth) and generic
SNMP operation (monitor any SNMP OID) is the <target> option
tag that describes the OIDs that MRTG will ask a target host for.
The format of the <target> option tag is:
> target[target-generic-name]:
OID1&OID2:comunity-name@IP-address
The OID1 and OID2 are the data sources (DS) and they
correspond to the original Input and Output values (the standard MRTG functionality
of Input/Output bandwidth for a network interface).
OID1 & OID2 may have the following values:
- OID1 and OID2 are different OIDs
- if you want to graph two different values per graph.
Example: Collect logical disk C and logical
disk D free space OIDs and draw them on the same graph
> Target[10.0.0.1-disk-cd]:.1.3.6.1.4.1.311.1.1.3.1.1.5.1.4.6.48.58.48.58.67.58&1.3.6.1.4.1.311.1.1.3.1.1.5.1.4.6.48.58.48.58.68.58:public@10.0.0.1
- OID1 and OID2 are one and the same OID -
if you want to graph only one value per graph. In case when you want to
represent a single OID per graph it will be represented by OID1 while OID2
(it is the same as OID1) can be ignored when drawing the graph (see paragraph
9.2)
Example: Collect logical disk C free space only.
> Target[10.0.0.1-disk-c]:.1.3.6.1.4.1.311.1.1.3.1.1.5.1.4.6.48.58.48.58.67.58&1.3.6.1.4.1.311.1.1.3.1.1.5.1.4.6.48.58.48.58.67.58:public@10.0.0.1
The following diagram explains the structure of a configuration
file:
9.2 Configuration
file options
MRTG offers a complex set of option tags to be used
in the configuration file.
Global options
HtmlDir
HtmlDir specifies the directory where
the html (or shtml, but we'll get on to those later,) lives.
NOTE: Workdir overrides the settings
for htmldir, imagedir and logdir
Example: Htmldir:
/www/mrtg/
ImageDir
ImageDir specifies the directory where
the images live, they should be under the html directory.
Example: Imagedir:
/www/mrtg/images
LogDir
LogDir specifies the directory where
the logs are stored. This need not be under htmldir directive.
Example:
Logdir: /www/mrtg/logs
Forks (UNIX only)
An a system that can fork (UNIX for
example) mrtg can fork itself into multiple instances while it is acquiring
data via snmp.
For situations with high latency or
a great number of devices this will speed things up considerably. It will
not make things faster though if you query a single switch sitting next
door.
Example: Forks:
4
Refresh
How many seconds apart should the
browser (Netscape) be instructed to reload the page? If this is not defined,
the default is 300 seconds (5 minutes).
Example: Refresh:
600
Interval
How often do you call mrtg? The default
is 5 minutes. If you call it less often, you should specify it here.
In this example we tell mrtg that
we will be calling it every 10 minutes. If you are calling mrtg every 5
minutes, you can leave this line commented out.
Example: Interval:
10
Note: unless you are using
rrdtool you can not set Interval to less than 5 minutes. If you are using
rrdtool you can set interval down to 1 Minute. Note though, setting the
Interval for an rrdtool/mrtg setup will influence the initial creation
of the database. If you change the interval later, all existing databases
will remain at the resolution they were initially created with.
WriteExpires
With this switch mrtg will generate
.meta files for CERN and Apache servers which contain Expiration tags for
the html and gif files. The *.meta files will be created in the same directory
as the other files, so you will have to set ``MetaDir .'' and ``MetaFiles
on'' in your apache.conf or .htaccess file for this to work
NOTE: If you are running Apache-1.2
or later, you can use the mod_expire to achieve the same effect ... see
the file htaccess.txt
Example: WriteExpires:
Yes
NoMib2
Normally we ask the SNMP device for
'sysUptime', 'sysName' properties some do not have these. If you want to
avoid getting complaints from mrtg about these missing properties, specivy
the nomib2 option. An example of agents which do not implement base mib2
attributes are Computer Associates - Unicenter TNG Agents. CA relies on
using the base OS SNMP agent in addition to its own agents to supplement
the management of a system.
Example: NoMib2:
Yes
SingleRequest
Some SNMP implementations can not
deal with requests asking for multiple snmp variables in one go. Set this
in your cfg file to force mrtg to only ask for one variable per request.
Example: SingleRequest:
Yes
SnmpOptions
Apart form the per target timeout
options, you can also configure the behaviour of the snmpget process on
a more profound level. SnmpOptions accepts a hash of options. The following
options are currently supported:
timeout
=> $default_timeout,
retries
=> $default_retries,
backoff
=> $default_backoff,
default_max_repetitions
=> $max_repetitions,
lenient_source_port_matching
=> 0,
lenient_source_address_matching
=> 1
The values behind the options indicate
the current default value. Note that these settings OVERRIDE the per target
timeout settings.
Example: SnmpOptions:
retries => 2, only_ip_address_matching => 0
Note: AS/400 snmp seems
to be broken in a way which prevents mrtg from working with it unless
SnmpOptions: lenient_source_port_matching
=> 1 is set.
IconDir
If you want to keep the mrtg icons
in some place other than the working (or imagedir) directory, use the IconDir
variable for defining the url to the icons directory.
Example: IconDir: /mrtgicons/
LoadMIBs
Load the MIB file(s) specified and
make its OIDs available as symbolic names. For better efficiancy, a cache
of MIBs is maintained in the WorkDir.
Example: LoadMIBs: /dept/net/mibs/netapp.mib,/usr/local/lib/ft100m.mib
Language
Switch output format to the selected
Language (Check the translate directory to see which languages are supported
at the moment. In this directory you can also find instructions on how
to create new translations).
Currently the following laguages are
supported: big5 brazilian bulgarian catalan chinese croatian czech danish
dutch eucjp french galician gb gb2312 german greek hungarian icelandic
indonesia iso2022jp italian korean lithuanian malay norwegian polish portuguese
romanian russian russian1251 serbian slovak slovenian spanish swedish turkish
ukrainian
Example: Language:
danish
LogFormat
Setting LogFormat to 'rrdtool' in
your mrtg.cfg file enables rrdtool mode. In rrdtool mode, mrtg relies on
rrdtool to do its logging. Graphs and html pages will be generated on the
fly by the 14all.cgi which can be found in the contrib section together
with a short readme ... This feature has been contributed by Rainer Bawidamann
<bawidama@users.sourceforge.net>. Please check his website for more
information: http://www.wh-hms.uni-ulm.de/~widi/14all/
Example:
LogFormat: rrdtool
LibAdd
If you are using rrdtool mode and
your rrdtool Perl module (RRDs.pm) is not installed in a location where
perl can find it on its own, you can use LibAdd to supply an appropriate
path.
Example:
LibAdd: /usr/local/rrdtool/lib/perl/
PathAdd
If the rrdtool executable can not
be found in the normal PATH, you can use this keyword to add a suitable
directory to your path.
Example:
PathAdd: /usr/local/rrdtool/bin/
RunAsDaemon
The RunAsDaemon keyword enables daemon
mode operation. The purpose of daemon mode is that MRTG is launched once
and not at regular basis by cron as in native mode. This behavior saves
computing resourses as loading and parsing of configuration files only
hapens once. Using daemon mode MRTG itself is responible for timing the
measurement intervals. Therfore its important to set the Interval keyword
to an apropiate value. Note that using daemon mode MRTG should no longer
be started from cron by regular basis as each started process runs forever.
Instead MRTG should be started from the command prompt or by a system startup
script.
If you want mrtg to run under a particular
user and group (it is not recomended to run MRTG as root) then you can
use the --user=user_name and --group=group_name options on the mrtg
commandline.
mrtg --user=mrtg_user --group=mrtg_group
mrtg.cfg
Also note that in daemon mode restart
of the process is required in order to activate changes in the config file.
Under UNIX, the Daemon switch causes
mrtg to fork into background after checking its config file. On Windows
NT the MRTG process will detach from the console, but because the NT/2000
shell waits for its children you have to use the special start sequence
when you launch the program:
start /b perl mrtg mrtg.cfg
You may have to add path information
equal to what you add when you run mrtg from the commandline.
Example (MRTG run as a daemon beginning
data collection every 5 minutes)
RunAsDaemon:Yes
Interval:5
Target specific options
Title
Title for the HTML page which gets
generated for the graph.
Example: Title[ezwf]:
Traffic Analysis for Our Nice Company
PageTop
Things to add to the top of the generated
HTML page. Note that you can have several lines of text as long as the
first column is empty.
Note that the continuation lines will
all end up on the same line in the html page. If you want linebreaks in
the generated html use the '\n' sequence.
Example:
PageTop[ezwf]: <H1>Traffic Analysis
for ETZ C95.1</H1>
Our Campus Backbone runs
over an FDDI line\n
with a maximum transfer
rate of 12.5 megabytes per
Second.
RouterUptime
In cases where you calculate the used
bandwidth from several interfaces you normaly don't get the router uptime
and router name displayed on the web page. If these interfaces are on the
same router and the uptime and name should be displayed nevertheless you
have to specify its community and address again with the RouterUptime keyword.
Example:
Target[kacisco.comp.edu]: 1:public@194.64.66.250
+ 2:public@194.64.66.250
RouterUptime[kacisco.comp.edu]:
public@194.64.66.250
MaxBytes1
Same as MaxBytes, for variable 1.
MaxBytes2
Same as MaxBytes, for variable 2.
PageFoot
Things to add to the bottom of the
generated HTML page. Note that you can have several lines of text as long
as the first column is empty. Note that the continuation lines will all
end up on the same line in the html page. If you want linebreaks in the
generated html use the '\n' sequence. The material will be added just before
the </BODY> tag:
Example:
PageFoot[ezwf]: Contact <A HREF="mailto:peter@x.yz";>Peter</A>
if you have questions regarding this
page
AddHead
Use this tag like the PageTop header,
but its contents will be added between </TITLE> and </HEAD>.
Example:
AddHead[ezwf]: <link rev="made"
href="mailto:mrtg@blabla.edu";>
BodyTag
BodyTag lets you supply your very
own <body ...> tag for the generated webpages.
Example:
BodyTag[ezwf]: <BODY LEFTMARGIN="1"
TOPMARGIN="1"
BACKGROUND="/stats/images/bg.neo2.gif">
AbsMax
If you are monitoring a link which
can handle more traffic than the MaxBytes value. Eg, a line which uses
compression or some frame relay link, you can use the AbsMax keyword to
give the absolute maximum value ever to be reached. We need to know this
in order to sort out unrealistic values returned by the routers. If you
do not set AbsMax, rateup will ignore values higher than MaxBytes.
Example: AbsMax[ezwf]:
2500000
Unscaled
By default each graph is scaled vertically
to make the actual data visible even when it is much lower than MaxBytes.
With the Unscaled variable you can suppress this. It's argument is a string,
containing one letter for each graph you don't want to be scaled: d=day
w=week m=month y=year. In the example scaling for the yearly and the monthly
graph are suppressed.
Example: Unscaled[ezwf]:
ym
WithPeak
By default the graphs only contain
the average values of the monitored variables - normally the transfer rates
for incoming and outgoing traffic. The following option instructs mrtg
to display the peak 5 minute values in the [w]eekly, [m]onthly and [y]early
graph. In the example we define the monthly and the yearly graph to contain
peak as well as average values.
Examples: WithPeak[ezwf]:
ym
Suppress
By default mrtg produces 4 graphs.
With this option you can suppress the generation of selected graphs. The
option value syntax is analogous to the above two options. In this example
we suppress the yearly graph as it is quite empty in the beginning.
Example: Suppress[ezwf]: y
Extension
By default, mrtg creates .html files.
Use this option to tell mrtg to use a different extension. For example
you could set the extension to php3, then you will be able to enclose PHP
tags into the output (usefull for getting a router name out of a database).
Example: Extension[ezwf]:
phtml
Directory
By default, mrtg puts all the files
that it generates for each target (the GIFs, the HTML page, the log file,
etc.) in WorkDir.
If the Directory option is specified,
the files are instead put into a directory under WorkDir or Log-, Image-
and HtmlDir). (For example the Directory option below would cause all the
files for a target ezwf to be put into directory /usr/tardis/pub/www/stats/mrtg/ezwf/
.)
The directory must already exist;
mrtg will not create it.
Example:
WorkDir: /usr/tardis/pub/www/stats/mrtg
Directory[ezwf]: ezwf
NOTE: the Directory option must
always be 'relative' or bad things will happen.
XSize and YSize
By default mrtgs graphs are 100 by
400 pixels wide (plus some more for the labels. In the example we get almost
square graphs ...
Note: XSize must be between 20 and
600; YSize must be larger than 20
Example:
XSize[ezwf]: 300
YSize[ezwf]: 300
XZoom and YZoom
If you want your graphs to have larger
pixels, you can ``Zoom'' them.
Example:
XZoom[ezwf]: 2.0
YZoom[ezwf]: 2.0
XScale and YScale
If you want your graphs to be actually
scaled use XScale and YScale. (Beware while this works, the results look
ugly (to be frank) so if someone wants to fix this: patches are welcome.
Example:
XScale[ezwf]: 1.5
YScale[ezwf]: 1.5
YTics and YTicsFactor
If you want to show more than 4 lines
per graph, use YTics. If you want to scale the value used for the YLegend
of these tics, use YTicsFactor. The default value for YTics is 4 and the
default value for YTicsFactor is 1.0 .
Example:
Let's suppose you get values ranging
from 0 to 700. You want to plot 7 lines and want to show
0, 1, 2, 3, 4, 5, 6, 7 instead of 0, 100, 200, 300, 400, 500,
600, 700. You should write then:
YTics[ezwf]: 7
YTicsFactor[ezwf]: 0.01
Factor
If you want to multiply all numbers
shown below the graph with a constant factor, use this directive to define
it ..
Example: Factor[as400]:
4096
Step
Change the default step from 5 * 60
seconds to something else (I have not tested this well ...)
Example: Step[ezwf]:
60
Options
The Options Keyword allows you to
set some boolean switches:
growright
The graph grows to the left by default.
This option flips the direction of growth causing the current time to be
at the right edge of the graph and the history values to the left of it.
bits
All the monitored variable values
are multiplied by 8 (i.e. shown in bits instead of bytes) ... looks much
more impressive :-) It also affects the 'factory default' labeling and
units for the given target.
perminute
All the monitored variable values
are multiplied by 60 (i.e. shown in units per minute instead of units per
second) in case of small values more accurate graphs are displayed. It
also affects the 'factory default' labeling and units for the given target.
perhour
All the monitored variable values
are multiplied by 3600 (i.e. shown in units per hour instead of units per
second) in case of small values more accurate graphs are displayed. It
also affects the 'factory default' labeling and units for the given target.
noinfo
Suppress the information about uptime
and device name in the generated webpage.
nopercent
Don't print usage percentages
transparent
make the background of the generated
gifs transparent ...
integer
Print summary lines below graph as
integers without comma
dorelpercent
The relative percentage of IN-traffic
to OUT-traffic is calculated and displayed in the graph as an additional
line. Note: Only a fixed scale is available (from 0 to 100%). Therefore
for IN-traffic greater than OUT-traffic also 100% is displayed. If you
suspect that your IN-traffic is not always less than or equal to your OUT-traffic
you are urged to not use this options. Note: If you use this option in
combination with the Colours options, a fifth colour-name colour-value
pair is required there.
avgpeak
There are some ISPs who use the average
Peak values to bill their customers. Using this option MRTG displays these
values for each graph. The value is built by averaging the max 5 minute
traffic avarage for each 'step' shown in the graph. For the Weekly graph
this means that it builds the average of all 2 hour intervals 5 minute
peak values. (Confused? Though so!)
gauge
Treat the values gathered from target
as 'current status' measurements and not as ever incrementing counters.
This would be useful to monitor things like disk space, processor load,
temperature, and the like ...
In the absence of 'gauge' or 'absolute'
options, MRTG treats variable as a counter and calculates the difference
between the current and the previous value and divides that by the elapsed
time between the last two readings to get the value to be plotted.
absolute
This is for counter type data sources
which reset their value when they are read. This means that rateup does
not have to build the difference between the current and the last value
read from the data source. The value obtained is still divided by the elapsed
time between the current and the last reading, which makes it different
from the 'gauge' option. Useful for external data gatherers.
unknaszero
Log unknown data as zero instead of
the default behaviour of repeating the last value seen. Be careful with
this, often a flat line in the graph is much more obvious than a line at
0.
withzeroes
Normally we ignore all values which
are zero when calculating the average transfer rate on a line. If this
is not desirable use this option.
noborder
If you are using rateup to log data,
MRTG will create the graph images. Normally these images have a shaded
border around them. If you do not want the border to be drawn, enable this
option. This option has no effect if you are not using rateup.
noarrow
As with the option above, this effects
rateup graph generation only. Normally rateup will generate graphs with
a small arrow showing the direction of the data. If you do not want this
arrow to be drawn, enable this option. This option has no effect if you
are not using rateup.
noi
When using rateup for graph generation,
you can use this option to stop rateup drawing a graph for the 'I' or first
variable. This also removes entries for this variable in the HTML page
MRTG generates, and will remove the peaks for this variable if they are
enabled. This allows you to hide this data, or can be very useful if you
are only graphing one line of data rather than two. This option is not
destructive - any data received for the the variable continued to be logged,
it just isn't shown.
noo
Same as above, except relating to
the 'O' or second variable.
nobanner
When using rateup for graph generation,
this option disables MRTG adding the MRTG banner to the HTML pages it generates.
nolegend
When using rateup for graph generation,
this option will stop MRTG creating a legend at the bottom of the HTML
pages it generates.
Example:
Options[ezwf]: growright, bits
kilo
Use this option to change the multiplier
value for building prefixes. Defaultvalue is 1000. This tag is for the
special case that 1kB = 1024B, 1MB = 1024kB and so far.
Example:
kilo[ezwf]: 1024
kMG
Change the default multiplier prefixes
(,k,M,G,T,P). In the tag ShortLegend define only the basic units. Format:
Comma seperated list of prefixed. Two consecutive commas or a comma at
start or end of the line gives no prefix on this item. Note: If you do
not want prefixes, then leave this line blank.
Example: velocity in nm/s (nanometers
per second) displayed in nm/h.
ShortLegend[ezwf]: m/h
kMG[ezwf]: n,u,m,,k,M,G,T,P
options[ezwf]: perhour
Colours
The Colours tag allows you to override
the default colour scheme. Note: All 4 of the required colours must be
specified here. The colour name ('Colourx' below) is the legend name displayed,
while the RGB value is the real colour used for the display, both on the
graph and in the html doc.
Format is: Col1#RRGGBB,Col2#RRGGBB,Col3#RRGGBB,Col4#RRGGBB
Important: If you use the dorelpercent
options tag a fifth colour name colour value pair is required: Col1#RRGGBB,Col2#RRGGBB,Col3#RRGGBB,Col4#RRGGBB,Col5#RRGGBB
Colour1: First variable (normally
Input) on default graph
Colour2: Second variable (normally
Output) on default graph
Colour3: Max first variable (input)
Colour4: Max second variable (output)
Example:
Colours[ezwf]: GREEN#00eb0c,BLUE#1000ff,DARK
GREEN#006600,VIOLET#ff00ff
Background
With the Background tag you can configure
the background colour of the generated HTML page
Example:
Background[ezwf]: #a0a0a0a
YLegend, ShortLegend, Legend[1234]
The following keywords allow you to
override the text displayed for the various legends of the graph and in
the HTML document
YLegend
The Y-axis label of the graph. Note
that a text which is too long to fit in the graph will be silently ignored.
ShortLegend
The units string (default 'b/s') used
for Max, Average and Current
Legend[1234IO]
The strings for the colour legend
Example:
YLegend[ezwf]:
Bits per Second
ShortLegend[ezwf]: b/s
Legend1[ezwf]: Incoming Traffic
in Bits per Second
Legend2[ezwf]: Outgoing Traffic
in Bits per Second
Legend3[ezwf]: Maximal 5 Minute
Incoming Traffic
Legend4[ezwf]: Maximal 5 Minute
Outgoing Traffic
LegendI[ezwf]: In:
LegendO[ezwf]: Out:
Note, if LegendI or LegendO are set
to an empty string with
LegendO[ezwf]:
The corresponding line below the graph
will not be printed at all.
Timezone
If you live in an international world,
you might want to generate the graphs in different timezones. This is set
in the TZ variable. Under certain operating systems like Solaris, this
will provoke the localtime call to give the time in the selected timezone
...
Example: Timezone[ezwf]:
Japan
The Timezone is the standard Solaris
timezone, ie Japan, Hongkong, GMT, GMT+1 etc etc.
Weekformat
By default, mrtg (actually rateup)
uses the strftime(3) '%W' option to format week numbers in the monthly
graphs. The exact semantics of this format option vary between systems.
If you find that the week numbers are wrong, and your system's strftime(3)
routine supports it, you can try another format option. The POSIX '%V'
option seems to correspond to a widely used week numbering convention.
The week format character should be specified as a single letter; either
W, V, or U.
Example: Weekformat[ezwf]:
V
RRDRowCount
This affects the creation of new rrd
files. By default rrds are created to hold about 1 days worth of high resolution
data. (plus 1 week of 30 minute data, 2 month of 2 hour data and 2 years
of 1 day data). Whith this Keyword you can change the number of base interval
entries configured for new rrds as they get created. Note that you must
take the interval time into account.
Example: RRDRowCount[ezwf]:
1600
When multiple targets share a single configuration
file (multiple interfaces of the same host), the config file can be written
in an efficient manner by specifying the target options that are
the same for all targets immediately after the global options and using
a " _ " as target generic name.
//global options
Workdir: c:\inetpub\mrtg\
Htmldir: c:\inetpub\mrtg\
Imagedir: c:\inetpub\mrtg\
Logdir: c:\inetpub\mrtg\
RunAsDaemon: Yes
Refresh: 300
//target shared options
PageTop[_]: Free RAM
Options[_]: gauge,growright,nopercent,
avgpeak, noo
ShortLegend[_]: Bytes;
YLegend[_]: Free RAM
LegendI[_]: Free RAM
AbsMax[_]: 500000000
MaxBytes[_]: 500000000
//individual target options
Target[10.172.10.106-mem]:.1.3.6.1.4.1.311.1.1.3.1.1.1.1.0&.1.3.6.1.4.1.311.1.1.3.1.1.1.1.0:public@10.172.10.106
Title[10.172.10.106-mem]: Free RAM
Target[10.172.10.26-mem]:.1.3.6.1.4.1.311.1.1.3.1.1.1.1.0&.1.3.6.1.4.1.311.1.1.3.1.1.1.1.0:public@10.172.10.26
Title[10.172.10.26-mem]: Free RAM
9.3 Custom SNMP OID configuration
examples (cpu, memory, disk space)
The following example gets the logical disk free
space (C,D,E drives), free RAM and CPU utilization for a host.
### Global Config Options
Workdir: c:\inetpub\mrtg\
Htmldir: c:\inetpub\mrtg\
Imagedir: c:\inetpub\mrtg\
Logdir: c:\inetpub\mrtg\
Icondir: /mrtg/images
Refresh: 300
RunAsDaemon: Yes
Interval: 5
### CPU Utilization
Target[10.0.0.254-cpu]:.1.3.6.1.4.1.311.1.1.3.1.1.33.9.0&.1.3.6.1.4.1.311.1.1.3.1.1.33.9.0:public@10.0.0.254
AbsMax[10.0.0.254-cpu]: 100
MaxBytes[10.0.0.254-cpu]: 100
Title[10.0.0.254-cpu]: CPU Utilization
(average)
PageTop[10.0.0.254-cpu]: CPU Utilization
Options[10.0.0.254-cpu]: gauge,growright,nopercent,
noo
YLegend[10.0.0.254-cpu]: CPU Utilization
ShortLegend[10.0.0.254-cpu]: %
LegendI[10.0.0.254-cpu]: CPU
Utilization (percentage) 
### Free disk C space
Target[10.0.0.254-diskc]:.1.3.6.1.4.1.311.1.1.3.1.1.5.1.4.6.48.58.48.58.67.58&1.3.6.1.4.1.311.1.1.3.1.1.5.1.4.6.48.58.48.58.67.58:public@10.0.0.254
AbsMax[10.0.0.254-diskc]: 100000
MaxBytes[10.0.0.254-diskc]: 100000
Title[10.0.0.254-diskc]: DISK FREE
SPACE (C)
PageTop[10.0.0.254-diskc]: DISK FREE
SPACE (C)
Options[10.0.0.254-diskc]: gauge,growright,nopercent,
noo
YLegend[10.0.0.254-diskc]: DISK FREE
SPACE (C)
ShortLegend[10.0.0.254-diskc]: MB
LegendI[10.0.0.254-diskc]: DISK
FREE SPACE (C) 
### Free disk D space
Target[10.0.0.254-diskd]:1.3.6.1.4.1.311.1.1.3.1.1.5.1.4.6.48.58.48.58.68.58&1.3.6.1.4.1.311.1.1.3.1.1.5.1.4.6.48.58.48.58.68.58:public@10.0.0.254
AbsMax[10.0.0.254-diskd]: 100000
MaxBytes[10.0.0.254-diskd]: 100000
Title[10.0.0.254-diskd]: DISK FREE
SPACE (D)
PageTop[10.0.0.254-diskd]: DISK FREE
SPACE (D)
Options[10.0.0.254-diskd]: gauge,growright,nopercent,
noo
YLegend[10.0.0.254-diskd]: DISK FREE
SPACE (D)
ShortLegend[10.0.0.254-diskd]: MB
LegendI[10.0.0.254-diskd]: DISK
FREE SPACE (D) 
### Free disk E space
Target[10.0.0.254-diske]:1.3.6.1.4.1.311.1.1.3.1.1.5.1.4.6.48.58.48.58.69.58&1.3.6.1.4.1.311.1.1.3.1.1.5.1.4.6.48.58.48.58.69.58:public@10.0.0.254
AbsMax[10.0.0.254-diske]: 100000
MaxBytes[10.0.0.254-diske]: 100000
Title[10.0.0.254-diske]: DISK FREE
SPACE (E)
PageTop[10.0.0.254-diske]: DISK FREE
SPACE (E)
Options[10.0.0.254-diske]: gauge,growright,nopercent,
noo
YLegend[10.0.0.254-diske]: DISK FREE
SPACE (E)
ShortLegend[10.0.0.254-diske]: MB
LegendI[10.0.0.254-diske]: DISK
FREE SPACE (E) 
### Free RAM
Target[10.0.0.254-mem]:.1.3.6.1.4.1.311.1.1.3.1.1.1.1.0&.1.3.6.1.4.1.311.1.1.3.1.1.1.1.0:public@10.0.0.254
AbsMax[10.0.0.254-mem]: 900000000
MaxBytes[10.0.0.254-mem]: 900000000
Title[10.0.0.254-mem]: FREE RAM
PageTop[10.0.0.254-mem]: FREE RAM
Options[10.0.0.254-mem]: gauge,growright,nopercent,
noo
YLegend[10.0.0.254-mem]: FREE RAM
ShortLegend[10.0.0.254-mem]: B
LegendI[10.0.0.254-mem]: FREE
RAM 
|