How important is it that the addresses stay the same?
Your simplest option might be to put in some GSLB-type appliances (Both Citrix and F5 have Virtual Appliance versions of these). Stick these in front of your app servers, one on each internet connection, and let them handle failover/load balancing using DNS. As a bonus, you also get a load balancer :)
As far as the address space goes, IIRC needing to multihome alone is justification for a /24, as this is the smallest block acceptable for routing. However if you don't want to go directly down the APNIC route you might be able to work with an upstream to get them to lease you a /24 and AS you can re-announce.
Regards,
Chris
On 6 Nov 2013, at 9:30 am, Matthew Poole
A "small company wanting to play big company" question: My employer is investigating options for network redundancy as having a functional internet connection is critical to our operation. We're not in any position to even try applying for PI IPv4 space from APNIC (only using a /28), and are in no way close to being ready to think about going to pure IPv6. Clients push to us, so we need to have functional DNS as well as link fail-over. We also have multiple public-facing servers offering the same services, so moving to *shudder* NAT or some kind of port proxying isn't an easy option (clients' internal bureaucracies to get firewall ports opened, client configuration, blah blah blah).
So, my question, what are our operational course of action for multi-homing when becoming an AS on the global tubes isn't on the cards?
Cheers
-- Matthew Poole "The difference between theory and practice is that practice is easier in theory than theory is in practice" _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog