My organization is expanding to a new DC with a new, independent transit connection to ISP "C" (for the sake of argument). They've also offered to give us a /24 that we could do with as we please. I don't know if it's portable (if they'd allow us to announce it from our own AS) or not at this point, but initially, they said they'd announce it via their AS and just give us a single static route to get the machines at the new DC on the net.
During the build-out and eventual linking of this new DC to our existing DC (where we announce our three existing prefixes via ISPs "A" and "B" with our own ASN), we plan to run a metro-ether link between the two locations and start announcing all our old and newly-assigned prefixes out through both locations. Would it be desirable to let ISP "C" at the new DC announce the prefix they're giving us from the start, and then plan to migrate it to our AS when we get the DC-to-DC link up? Or better to set up our own edge router at the new DC to announce the new prefix from our own AS? Would this even be possible from a BGP routing perspective, to have one router announce a prefix from our AS in one location, and another router announce our other prefixes (mutually exclusive of the prefix announced at the new DC) at another location, and not have those two locations linked internally?
What are the limitations of announcing one prefix via two AS's and having two EBGP speakers (that aren't connected via an IGP) using the same AS announce different sets of prefixes?
No comments:
Post a Comment