Just throwing another concept out there (the cloud solution someone posted earlier inspired it): - Two ISP connections - Two ISP /28's (non PI) - Short DNS TTLs - Failover means --- Change to DNS --- Change to default gateway / outbound router on your edge (or use some sort of appliance to manage this your end). To move to second carrier update the DNS to point at your alternative ISPs, and require your external sources to follow DNS and adhere to TTLs. ? If you can't meet the APNIC requirements for delegation from them, this would seem an easy enough option...? -----Original Message----- From: Matthew Poole [mailto:matt(a)p00le.net] Sent: Wednesday, 6 November 2013 1:29 p.m. To: Mark Foster Cc: 'NZNOG' Subject: Re: [nznog] Multi-homing without PI space I should point out that I'm quite happy to have one ISP delivering over one physical circuit, provided the ISP has demonstrated sufficient historic availability. But the man who pays my salary is interested in having a second link for redundancy purposes, which means I will ask the question and try to provide him some meaningful information. I've already explained about the hurdle of being too small for PI so needing to engage in complicated internal trickery. Unless someone from APNIC wants to pop up and clarify that the rules for PI don't actually mean what they appear to mean, and you can get PI if the entire need is based on multi-homing regardless of how many addresses are actually going to be utilised? Which would seem to be an extraordinarily dangerous policy. On 6/11/2013 12:48, Mark Foster wrote:
If you don't have physical link diversity, why not simply choose an ISP with multiple backhauls and leave it at that? I.e. pay your ISP to provide the Layer 3 diversity for you.
Without layer 1/2 I don't see what advantage you're really getting out of the mucking around.
Mark.
-- Matthew Poole "The difference between theory and practice is that practice is easier in theory than theory is in practice"