[3Com 3300] Number of GB's used

[S2S-Robert]

Hi,

I am looking for a script that allows me to view the actual number of GB's that a switch port uses on a monthly basis. Now I'm quite positive cacti can do the trick, but to be honest, I have no clue whatsoever where to start looking.

Now I believe cacti can pull the data off the switch using SNMP, but will this be done every minute? And will it automatically put it in a graph that I and my users can view?

Then my final question, I know this is like swearing in church with GPL based scripts, but if I'm unable to figure it out myself, is there anybody who can help install it for me? I am more than happy to give a donation to further help this script develop.

Regards

Robert

[Phobos182]

If GB = GigaByte, then Cacti has built in graphs that can grab this information for you.

Follow the documentation to install the software. Create a new device for your 3Com switch (choose the template Cisco Router). If you click on the device, it will return all ports on the switch that you can graph. Check the ones you are interested in, and then create a graph for it which is called (TRAFFIC BITS/SECOND). This will create a graph for you letting you know how much bandwidth in bits is being used for each interface on the switch.

[S2S-Robert]

Ok, I got quite far actually. I was able to install cacti and I am able to create some graphs.

Now the 'funny' thing is that the data sources with the ports don't quite seem to match:

[edit : pix gone]

As you can see the total traffic of port 1 & port 2 seem to match as well as the total traffic on the last 2 graphs (bits / second) match as well. Port 1 is the actual port the switch is on, so only management traffic goes there (zero to none), while the 2nd port actually has a computer attached to it that I pushed around 3GB through to test cacti.


It seems that I numbered the ports wrong, but that's odd, since I added them one at a time. The switch gives me back that I'm checking Port 1, I created all the graphs given port 1 and somehow they seemed to get mixed up?!

Any thoughts? Should I remove everything and just recreate them all step by step?

[S2S-Robert]

Ok, I figured out what was doing this, I used Port 1 as uplink port, so all traffic coming in & out of port 2 had to come through 1 as well.

But now I'm stuck with Port 3, I added Port 3 as a graph, but it seems I got 2 data sources to choose from (but I've got only 1 in the data sources for port 3).

[edit : pix gone]

Which one should I choose, or how can I make sure I've only got 1 data source to choose from?

[edit]
Besides that, the graph cannot be made either:
RRDTool Says:

ERROR: opening '/var/www/html/cacti/rra/3com_3300_traffic_in_12.rrd': No such file or directory

[S2S-Robert]

I checked further into this, and I turned on the data source debug mode:

/usr/bin/rrdtool create \
/var/www/html/cacti/rra/3com_3300_traffic_in_14.rrd \
--step 300 \
DS:traffic_out:COUNTER:600:0:100000000 \
DS:traffic_in:COUNTER:600:0:100000000 \
DS:traffic_out:COUNTER:600:0:100000000 \
DS:traffic_in:COUNTER:600:0:100000000 \
RRA:AVERAGE:0.5:1:600 \
RRA:AVERAGE:0.5:6:700 \
RRA:AVERAGE:0.5:24:775 \
RRA:AVERAGE:0.5:288:797 \
RRA:MAX:0.5:1:600 \
RRA:MAX:0.5:6:700 \
RRA:MAX:0.5:24:775 \
RRA:MAX:0.5:288:797 \

When I try to recreate it using shell xs I get:

[root@beijing rra]# /usr/bin/rrdtool create \
> /var/www/html/cacti/rra/3com_3300_traffic_in_14.rrd \
> --step 300 \
> DS:traffic_out:COUNTER:600:0:100000000 \
> DS:traffic_in:COUNTER:600:0:100000000 \
> DS:traffic_out:COUNTER:600:0:100000000 \
> DS:traffic_in:COUNTER:600:0:100000000 \
> RRA:AVERAGE:0.5:1:600 \
> RRA:AVERAGE:0.5:6:700 \
> RRA:AVERAGE:0.5:24:775 \
> RRA:AVERAGE:0.5:288:797 \
> RRA:MAX:0.5:1:600 \
> RRA:MAX:0.5:6:700 \
> RRA:MAX:0.5:24:775 \
> RRA:MAX:0.5:288:797 \
>
ERROR: Duplicate DS name: traffic_out

So there seems to be a duplice DS name, any thoughts?

[TheWitness]

The infamous "duplice DS name" bug. Please post your database to my email. larryjadams@comcast.net. I will only look for the solution to this bug if you are using 0.8.6b. To dump your DB to a file use the following:

\mysql\bin\mysqldump --user=root --password cacti > cactidump.sql

TheWitness

p.s. I realy want to fix this bug.

[S2S-Robert]

Yes I'm using the 0.8.6b, I've e-mailed you the sql file so let's just hope the bug can be fixed!

[TheWitness]

Robert,

Did you modify the Interface - Traffic data template at all? I have verified that your do have this problem in your database. It is quite easy to correct, just need to understand if you had done anything with the template at any time.

Thanks in Advance,

Larry

[S2S-Robert]

No, not that I'm aware of. I looked at it now, and I'm quite sure that's a page I've never seen before.

I removed the entire database and reimported it all from the setup file. Now I'm following the steps to correctly create new graphs, should I be concerned or pay attention to something? I'm just testing, so I don't need to keep the old data files.

[TheWitness]

Let me know if with the new database you have any problems along these same lines.

Larry

[TheWitness]

Robert,

I have looked into your problem some more. Tell me, what version of Cacti were you using when you first added the 3Com device?

Thanks,

Larry

[S2S-Robert]

Uhm... I firstly installed the 0.8.6, but then I removed that one completely (rpm -e) and then reinstalled 0.8.6b. I removed all files and all databases related to 0.8.6, so I think that means I was running 0.8.6b.

I do however want to confirm the thing raX pointed out in http://forums.cacti.net/viewtopic.php?t=4820, I was indeed using the first (and apperently wrong) way of adding the graphs. I must say that it's very confusing to have the graph template there if you're not allowed to use it. I sincethen added everything the correct way (or at least the described way) and there hasn't been a problem since.

[TheWitness]

Yes, Ian was correct. In addition, we have to add some details in the code to NOT allow a Data Query based graph template to be selected from the Host Edit UI or some other redesign element.

TheWitness