Tags

Well, it’s quite easy to implement MRTG on Allot Bandwidth Manager. It can be done on the ehternet (typical), or on the pipes or on the virtual channel. First download the MIBs from Allot GUI. Copy NE-STAT-MIB.txt, PIPE-MIB.txt, QID-PIPE-MIB.txt, QID-VC-MIB.txt, VC-MIB.txt, COMPANY-MIB.txt to /etc/mrtg folder (hope you are using linux).

Create a file, say mrtg.allot under /etc/mrtg folder. Write the follwoing lines:

Options[_]: bits,growright
LoadMIBs: /etc/mrtg/COMPANY-MIB.txt,/etc/mrtg/NE-STAT-MIB.txt,/etc/mrtg/QID-PIPE-MIB.txt,/etc/mrtg/QID-VC-MIB.txt
workdir:/var/www/html/allot
Target[pipe_name]: .1.3.6.1.4.1.2603.1.2.1.1.1.4.5.0&.1.3.6.1.4.1.2603.1.2.1.1.1.5.5.0:PubliC@192.169.1.1:::::2
Title[pipe_name]: Traffic Analysis of PipeName
MaxBytes[pipe_name]: 100000
PageTop[pipe_name]:

QoS device Traffic Analysis

n PipeName

First three lines are quite easy. Just difine the option, MIB files location and the working directory. Fourth line is very interesting and important. As we are doing the MRTG on pipes of the Allot, 1.3.6.1.4.1.2603.1.2.1.1.1.4 represents the PipeByteCountIn and 1.3.6.1.4.1.2603.1.2.1.1.1.5 represents PipeByteCountOut. Last two degit represents the pipe name. Here 5.0 is my pipe name on which I am doing my MRTG.

So how do I know the pipe name? 🙂 . Login to the Allot in text mode (ssh or telnet). Run the following command: snmpwalk -c -v 1  PIPE-MIB::pipeStatTable|more

This will list the pipe name and their no. For example:

enterprises.allotCom.neStatistics.pipeStatMIB.pipeStat.pipeStatTable.pipeEntry.pipeName.1.0 = WordPress

Here WordPress pipe has the pipe no 1.0

Next parts are easy. Run the mrtg command and the indexmaker. It’s DONE!!