Good Points, but I was just trying to point out that a sniffer
is WAY over kill if all you want is traffic count. Especially if you
have to pay for it. Did I say how much I love tcpdump and snoop?
There seems to be this misconception that a sniffer is a do it all, its not really. Way too cumbersome to do something that simple. I never bring my T-BERD, HP Advisor unless I have to. If all you're doing is polling for traffic count,
snmpget <host> <community> interfaces.ifTable.ifEntry.ifInOctets.1
is all you really need.
"plug your PC in the swtich where your traffic is located" this is not exactly right. You can't sniff on a switched port, or full duplex. You can get around a switched port by making the switch send all traffic to that port too. For full duplex, you can't get around that without special hardware.
What I'm saying is not complicated. Using a sniffer to gather useage is. Provided your sniffer can keepup with the load, you'll still have to tally up the size of the packets you've captured, the figure out the time from the deltas.
So in summary, sniffers are troubleshooting tools. Use it for when you need to look at a certain kind of packet, destination, source. Like why are my bootp messages misconfiguring my device...
SNMP is for Simple Network Management.
I'm not trying take out frustrations on anyone. Just realize that I know a little bit about networking to know that capturing a lot over packets, just to get a bandwidth ultilization is plain silly. Plus the fact that you'd have to open up a port to forward all traffic to it, which will increase the load on your switch. Then if its a full duplex port...
I wouldn't purposely tell you to use something else if it wasn't the right choice.