How To Use MRTG With Trango Broadband Products: April 30th, 2004
How To Use MRTG With Trango Broadband Products: April 30th, 2004
How To Use MRTG With Trango Broadband Products: April 30th, 2004
MRTG is a very useful graphing tool used mainly for showing network usage statistics.
But as shown within this document, it can useful for graphing RSSI values over time.
References:
MRTG Home Page:
http://people.ee.ethz.ch/~oetiker/webtools/mrtg/
MRTG Command Reference:
http://people.ee.ethz.ch/~oetiker/webtools/mrtg/mrtg-reference.html
GLOBAL SECTION
Copy this global section to your mrtg.cfg file to help the MRTG operation go smoothly.
You may change the working directory if needed.
WorkDir: /var/www/html/mrtg
Options[_]: bits, growright
NoMib2: Yes
SingleRequest: Yes
The following is a typical entry in a mrtg.cfg file for the purpose of recording
bandwidth usage at the Ethernet Port of a M5830S-AP. This means the graph will show
all of the traffic coming in and going out of the Ethernet Port for that particular
M5830S AP. This works for M5830S-AP only.
### Interface 8 >> Descr: 'DualBand AP' | Name: '' | Ip: '' | Eth: '00-00-00-
00-00-00' ###
Target[10.8.1.185_1]:1.3.6.1.4.1.5454.1.20.1.15.5&1.3.6.1.4.1.5454.1.20.1.15.
6:[email protected]:
SetEnv[10.8.1.185_1]: MRTG_INT_IP="10.8.1.185" MRTG_INT_DESCR="ETHERNET"
The following is a typical entry in a mrtg.cfg file for the purpose of recording
bandwidth usage at the RF Port of a M5830S-AP. This means the graph will show all
the traffic coming in and going out for that particular M5830S AP. This works for
M5830S-AP only.
### Interface 9 >> Descr: 'DualBand AP' | Name: '' | Ip: '' | Eth: '00-00-00-
00-00-00' ###
Target[10.8.1.185_2]: 1.3.6.1.4.1.5454.1.20.1.15.7&1.3.6.1.4.1.5454.1.20.1.15
.8:[email protected]:
SetEnv[10.8.1.185_2]: MRTG_INT_IP="10.8.1.185" MRTG_INT_DESCR="RF"
Directory[10.8.1.185_2]: TrangoAP_10.8.1.185
MaxBytes[10.8.1.185_2]: 1250000
Title[10.8.1.185_2]: Traffic Analysis for -- Trango M5830S AP-10.8.1.185 -RF
PageTop[10.8.1.185_2]: <H1>Traffic Analysis -- Trango M5830S AP-10.8.1.185 -
RF</H1>
<TABLE>
<TR><TD>System:</TD> <TD>Trango M5830S-AP</TD></TR>
<TR><TD>Maintainer:</TD> <TD>Name</TD></TR>
<TR><TD>Description:</TD><TD>RF Port </TD></TR>
<TR><TD>ifType:</TD> <TD>ethernetCsmacd (6)</TD></TR>
<TR><TD>ifName:</TD> <TD>Ethernet </TD></TR>
<TR><TD>Max Speed:</TD> <TD>10 mbits/s</TD></TR>
</TABLE>
Target[10.8.1.185_2]: 1.3.6.1.4.1.5454.1.10.1.15.5&1.3.6.1.4.1.5454.1.10.1.15
.6:[email protected]:
Title[10.8.1.185_2]: Traffic Analysis for -- Trango M5800S AP-10.8.1.185 -Eth
PageTop[10.8.1.185_2]: <H1>Traffic Analysis -- Trango M5800S AP-10.8.1.185 -
Eth</H1>
Target[10.8.1.185_2]: 1.3.6.1.4.1.5454.1.10.1.15.7&1.3.6.1.4.1.5454.1.10.1.15
.8:[email protected]:
Title[10.8.1.185_2]: Traffic Analysis for -- Trango M5800S AP-10.8.1.185 -RF
PageTop[10.8.1.185_2]: <H1>Traffic Analysis -- Trango M5800S AP-10.8.1.185 -
RF</H1>
Target[10.8.1.185_2]: 1.3.6.1.4.1.5454.1.22.1.9.1&1.3.6.1.4.1.5454.1.22.1.9
.2:[email protected]:
Title[10.8.1.185_2]: Traffic Analysis for -- Trango T-Link10 MU-10.8.1.185 -
Eth
PageTop[10.8.1.185_2]: <H1>Traffic Analysis -- Trango T-Link10 MU-10.8.1.185
-Eth</H1>
Target[10.8.1.185_2]: 1.3.6.1.4.1.5454.1.24.1.9.1&1.3.6.1.4.1.5454.1.24.1.9
.2:[email protected]:
Title[10.8.1.185_2]: Traffic Analysis for -- Trango T-Link10 RU-10.8.1.185 -
RF
PageTop[10.8.1.185_2]: <H1>Traffic Analysis -- Trango T-Link10 RU-10.8.1.185
-RF</H1>
The following is a typical entry in mrtg.cfg file for the purpose of recording
bandwidth usage at the RF Port of a subscriber. This means the graph will show all the
traffic coming in and going out the RF port for that particular subscriber. This works
for M5830S-AP only.
In your application you would change all instances of "4077" to the SUID number of the
SU you wish to graph. The variable "bw" is added below to the Target name to
differentiate it from other variables we are monitoring from that same SU. ( bw =
"bandwidth" )
### Interface 11 >> Descr: 'Traffic for SU 4077' | Name: '' | Ip: '' | Eth:
'00-00-00-00-00-00' ###
Target[10.8.1.185_4077_bw]: 1.3.6.1.4.1.5454.1.20.3.6.1.22.4077&1.3.6.1.4.1.
5454.1.20.3.6.1.23.4077:[email protected]
Options[10.8.1.185_4077_bw]: growright, bits
NoMib2: Yes
SingleRequest: Yes
YLegend[10.8.1.185_4077_bw]: bits/s
ShortLegend[10.8.1.185_4077_bw]: bps
Legend1[10.8.1.185_4077_bw]: To SU
Target[10.8.1.185_4077_bw]: 1.3.6.1.4.1.5454.1.10.3.6.1.22.4077&1.3.6.1.4.1.
5454.1.10.3.6.1.23.4077:[email protected]
The following is a typical entry in mrtg.cfg file for the purpose of recording RSSI from
and to a particular SU unit that has an SUID of 4077. This means the graph will show
the RSSI at the AP (blue line) and the RSSI at the SU (green line). This works for
M5830S-AP only.
In this example the AP has an IP address or 10.8.1.185. RSSI is monitored through the
AP. RSSI can not be monitored using the SU's IP address. It must the APs IP address.
In your application you would change all instances of "4077" to the SUID number of the
SU you wish to graph. The variable "rs" is added below to the Target name to
differentiate it from other variables we are monitoring from that same SU.
( rs = "RSSI" )
### Interface 10 >> Descr: 'RSSI for SU 4077' | Name: '' | Ip: '' | Eth: '00-
00-00-00-00-00' ###
Target[10.8.1.185_4077_rs]: 1.3.6.1.4.1.5454.1.20.3.6.1.16.4077&1.3.6.1.4.1.
5454.1.20.3.6.1.15.4077:[email protected] + 100
Target[10.8.1.185_4077]: 1.3.6.1.4.1.5454.1.10.3.6.1.16.4077&1.3.6.1.4.1.
5454.1.10.3.6.1.15.4077:[email protected] + 100
To perform RSSI monitoring for a TrangoLINK-10 Master (Point-to-Point radio), use the
above entry but change the ".20..." in the Target line to ".22.2.1" as shown here. You
may also want to change the Title line as shown also. This entry will now only work
for a TrangoLINK-10 Master Unit.
! NOTE: For this graph, both the blue and green line will show the same value.
This is because the TrangoLINK-10 Master does not store the RSSI from the
Remote radio. Instead you must generate another graph just for the Remote side
as shown in the next section.
Target[10.8.1.185_4077]: 1.3.6.1.4.1.5454.1.22.2.1&1.3.6.1.4.1.5454.1.22.2.1:
[email protected] + 100
Target[10.8.1.185_4077]: 1.3.6.1.4.1.5454.1.24.2.1&1.3.6.1.4.1.5454.1.24.2.1:
[email protected] + 100