There will be two routes installed in the routing table. The actual traffic sharing will depend on the IOS switching method in effect (process, fast, CEF,) either per-packet, per-destination or per flow.
By default the traffic will be load shared per destination in any switching method. You can enable per packet load sharing under each interface when using process switching or cef. Once you have cef enabled on the interface, the sharing will be a derivation of destination sharing, what's normally called per flow load sharing. That's what you should have. I'm not a fan of per packet sharing as there are issues with that, especially with packets arriving out of order.
You can turn on per packet with CEF, but you can't do per destination with process--it's not possible, because of the way the ip input process (which does the actual switching in the process path) and the routing table interact. Fast is per destination only, but we don't care about fast any longer, since unicast fast is gone/dead.
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.