I've attached a document for everyone's review to get your thoughts on it.
A rough summary is that I've got a load balancer that all of our internet connections come into. I need to have a plan in place to be able to throw something up quickly to get our internet back up.
A couple of questions:
I think I'm going to have to NAT the traffic for the 126.96.36.199 and the 188.8.131.52 traffic for the 184.108.40.206 subnet. Is this configuration that I've come up with feasible for an interim fix should the load balancer go down?
Does anyone else have a better suggestion (aside from redundancy). I don't think we can get another load balancer.
Okay then yes your solution seems a good one as as intermediate until you get a new fatpipe although it is worth discussing with your boss that you will not be able to fully utilise all the links and that the cost of a fatpipe might well be covered by the amount of money you lose by not being able to utilise all the links. I realise i could be talking rubbish here depending on the cost of a fatpipe (no idea) and how you pay for bandwidth on your links.
One thing to be aware of. If you are going to NAT to 2.2.2.x and 3.3.3.x you obviously can't use the "ip nat inside source list interface fa0/0 overload as it will use the primary address of the interface ie. 220.127.116.11 so you will need to define a pool for the 18.104.22.168 and the 22.214.171.124.
Other than that it should be fine. Would be interested to hear if you ever have to use it ?