To follow up to my own post, PowerConnect 5324s only have 32 bit counters. Hence they wrap around to zero too frequently for the standard every 5 minutes poll from mrtg.   Needed to poll more than once per minute to get accurate graphing (now done).   Owen
Hi,   we have 4 linux servers each with 4x1 Gb RR bonded nics going into 4 LAGs on a Powerconnect 5324. From here we have another 7 port LAG going into a 7 port port channel on a Cisco 6500 We are using MRTG to graph the traffic on both the cisco and the Dell router. The graphs for the LAGs on the Dell switch do not display the total throughput. e.g. if we add together the traffic for the 4 server lags it is a fraction of what the Cisco is reporting from it's port channel. It would appear that if we add together the traffic for the 16 server ports, this is a lot closer to what the Cisco is reporting.   Is there something obvious I'm missing here, or are there any known issues? I can provide example graphs and configs from any/all of the above if it would help anyone to point me in the right direction.   I have also tried cacti in case it was MRTG that was to blame, but that gives the same results.   Thanks, Owen
Powerconnect 5324, LAGs and mrtg