You can also use NetFlow/SFlow foncionalities on your Peering Interface.
And then parse/treat data using tools like ntop/flowscan and such.
Daniel Golding <email@example.com> 01/20 12:04 >>>
Andrew's issue is this - he's got an Ethernet port on a public peering
switch with a bunch of peers. He can see the interface stats just fine but
he's having trouble figuring out how much traffic is going to (or coming
from) each peer. One interface, many peers, confusing problem. There isn't
one VLAN per peer on most public peering switches - its one big Ethernet
segment with each peer getting an IP out of a common subnet. Welcome to the
world of broadcast multi-access peering.
The classical way to do this is mac accounting. This can be pretty rough -
its not really useful for anything more than a ratio, from what I've seen -
the numbers tend to not add up properly.
Another possibility (on Cisco) is using BGP Policy Accounting, although
support can be spotty depending on hardware.
For other platforms, there's some good information here:
The link on that page for Juniper's Destination Class Usage (DCU) is broken.
Try this one instead: