I agree, that the best option would be an article http://www.cisco.com/c/en/us/support/docs/ip/network-address-translation-nat/100658-ios-nat-load-balancing-2isp.html
At the same time it's missing EEM script to flush NAT translation table on failover (this might be needed in some scenario).
PS1: Per-packet load-balancing is just impossible approach here - I would not recommend to use it.
PS2: PFR is not an option, as PFRv2 support along with NAT is questionable.
PS3: BGP could be an option if you do routing based on public IP-addresses.
PS4: please change your passwords on the device, as you had published your public IP-addresses along with the passwords to access the device.
PS5: your IP SLA configuration does not work as you expect it, as traffic for both of them [normally] leaves G0/0 interface; to fix the behaviour, the best would be to use local PBR. Please let me know if you want me to change the configuration appropriately (the passwords to access the box are available).
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...