Cheshire Cat Computing

You can set a manual scale for a target, if you want.

routers.cgi*UpperLimit[ezwf]: xxxx
this sets the upper limit (max Y axis) to xxxx. It will still be automatically increased if the max data value is above this value, though, unless you also use:

routers.cgi*Options[ezwf]: rigid
this makes the upper limit of the graph rigid (ie, it wont rescale).

The default for an unscaled graph is to have upperlimit = maxbytes, and not rigid. The default for a scaled graph is to have upperlimit=0 and not rigid.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

Hi!

I tried what you told me. In top of my mrtg cfg file I have:

routers.cgi*UpperLimit[172.16.2.91_1]: 10000
routers.cgi*Options[172.16.2.91_1]: rigid

and the target looks like this:

Target[172.16.2.91_1]: 1:public@172.16.2.91:
SetEnv[172.16.2.91_1]: MRTG_INT_IP="" MRTG_INT_DESCR="1"
MaxBytes[172.16.2.91_1]: 12500000
Title[172.16.2.91_1]: Traffic Analysis for Port 1
PageTop[172.16.2.91_1]: <H1>Traffic Analysis for Port 1</H1>
<TABLE>
<TR><TD>System:</TD> <TD>Device 1</TD></TR>
<TR><TD>Maintainer:</TD> <TD>IT</TD></TR>
<TR><TD>Description:</TD><TD>Device 1</TD></TR>
<TR><TD>ifType:</TD> <TD>ethernetCsmacd (6)</TD></TR>
<TR><TD>ifName:</TD> <TD>1</TD></TR>
<TR><TD>Max Speed:</TD> <TD>12.5 MBytes/s</TD></TR>
</TABLE>

Although, the graph is unchanged with the Maxbytes as top of the y scale..

You will need at least v2.14 of routers2.cgi.

Also, remember that all directives for a target MUST come AFER the Target[] definition, else they are ignored. Don't put it just at the beginning of the file, put it with the other directives for that Target.

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11

thanks!

the placement was the problem!

Does this mean that using the [_]: default for these options won't work?

The special default targets, [_], [^] and [$], will all work, as they are implicitly defined at the beginning.

The 'Target[] first' restriction only applies to *explicit* targetnames.

In the next version of routers2 I will completely rewrite the parser (maybe use the MRTG_lib.pm perl library, although it has slightly different behaviour to the current rules)

Steve

_________________
Steve Shipway
UNIX Systems, ITSS, University of Auckland, NZ
Woe unto them that rise up early in the morning... -- Isaiah 5:11