Chris,
My comment inline.
This is effectivly what we are doing today, on a slightly more sofisticated level.
We produce a report based on netflow statistics that tells us (in percentage terms) which asn's we are sending traffic to. We then look at our current BGP table, which we get from SNMP. We take the asn's which recieve 60% of our traffic.. and make a few descisions.
1) If as path length is shorter via one provider over the other, make sure we prefer the shorter path.
2) If they are equal length, split the list of asn's between the 2 providers based on the input of the script.
So back to the question at hand... to get netflow stats for outgoing traffic.. we need cards in the 12K router which will support netflow on the ingress ports of the router for outgoing traffic(ie Gigabit Ethernet Line Cards)... right?
-Chris
Mike McSpedon wrote:
So back to the question at hand... to get netflow stats for outgoing traffic.. we need cards in the 12K router which will support netflow on the ingress ports of the router for outgoing traffic(ie Gigabit Ethernet Line Cards)... right?
Correct, NetFlow is generated when the packet enters the router. you'll need Engine 3 or 4 cards on your ingress ports (GigE I assume for outbound traffic) in order to do line rate with full Netflow. Engine 0 & 1 cards can do sampled netflow which *may* be enough for your load balancing needs.
-Matt