Hello, On Sat, 14 May 2005 11:54:39 +1000 "Michael Bellears" <[EMAIL PROTECTED]> wrote: > > What do you do with duplicate flows? > > Example: Traffic destined for client xxx.xxx.xxx.1 comes in via Router B > (Internet Feed), which is then routed to client who is connected to > Router A - Both Router A + Router B will have a flow for this traffic, > so there is a chance of double billing? > > As we have multiple upstream connections (All on different routers), > traffic destined for a given destination can potentially come in via any > of these Upstreams(Due to BGP) - How do we ensure that we sift out these > duplicates? Another way is to keep in billing system not only information "what to bill" (Customer networks and ASes), but also "on wich device to bill this customer" (exporter ip address or hostname) . Good practice is to bill customer on device, closest to him. Then you need to build filters/stat definitions/etc for each of your clients, but be accurate to avoid perfomance problems.
For example, you may tag your flows based on exporter, then to "or" it with tag based on customer, then to filter out all you don't need to bill (keep only flows for valid "customer"-"router" pairs), then to use flow-stat to get readable reports of tag (Wich is sinonym of "customer" in this case) aggregation. Also (Depending of flow files volumes, exporter and clients quantity), you may tag clients based on networks only, then generate tag aggregated reports for inbound/outbound traffic for each router, and then to make billing reports based on billing information (network-router-customer trios). You can see anytime how many traffic get your client from each of your POPs, and from each of your upstream channels (if channels connected to different routers), and to bill traffic from different channels by different prices. -- Gennady Abramov, CCNA, CCNP; Demos-Internet NOC [EMAIL PROTECTED], AGV77-RIPE _______________________________________________ Flow-tools mailing list [EMAIL PROTECTED] http://mailman.splintered.net/mailman/listinfo/flow-tools
