Devavrat,
It was, to an extent. What I learned was that I can use TCP-State-Bypass to use the ASA to do some asynchronous routing, thought it may not be the best use. What I did was set up the ASA as the default gateway, and configured SLA's on the ASA to monitor link state. WHen that link failed to the internet, I had the ASA divert traffic to the MPLS provider router.
State bypass come in to play because the ASA does not get to see the TCP packets increment sequentially. Basically, when traffic comes out the MPLS provider router, it goes straight to the client, and the ASA doesn't get to see the full flow.
State Bypass just tells the ASA to ignore TCP states for whatever policy you create(class-maps to policy-maps, etc.)
I didn't much like this idea however, and after validating that it worked, embarked on changing the structure to be a bit different. I plugged the internet into the ASA as normal, but I also created another interface that connected to the MPLS provider router. This way, the provider was not local to our LAN, but I could bypass(no pun intended) using the TCP-State-Bypass command. So my LAN sits behond my ASA, and I have a seperate interface for MPLS and Internet.
Since my employer doesn't like to spend money, that's where i sit right now. I believe a much better solution would have been to purchase a router, and set that as the default gateway. Then I could have done routing on a router, and left the ASA to do its' job, to be a firewall.
