ASA 5520 Redundant Links Inbound/Outbound

you do it the same way your primary nat is.

static (inside,outside) netmask

dont forget to apply the acl on the outside2 interface as well.

Thanks Brian I'll give it a go in the Lab environment.

Very welcome, this feature works flawlessly. So far we've got atleast

Brian, in this scenario what happens if traffic comes in one connection on the ASA and the server sends out a response? will it go out the default gateway which is the primary connection at the time or will it go out the way it came in? Thanks.

Correct, it will be asymentrical routing...in one pipe, out the other. Will piss off a lot of things since a different IP will be replying.

Yeah that won't necessarily work for us. We have a web presense and host our own DNS etc. I'll have to find another way. I have a router that I can throw in front to handle the ISP with object tracking and also Policy Based Routing to get it back out the correct pipe. I'm thinking I can try to do something with Policy based routing and only have one "outside" interface going into the ASA from the router this will save me an interface as well. Can you think of a easier/better solution?

You cannot have 2 active ISP connections on a single ASA, you can run in ISP redundancy mode which is active/passive. By 2 active ISP's I mean that default route traffic, ie 0.0.0.0 will go out both pipes. You "could" have site to site VPN tunnels on one, all default traffic go out the other, you could also have the primary default fail over to the secondary. If you want true load balancing look in to something like Radware or similar. Radware Branch is a great box, we've got 100's of them out there at different customers.