The big idea is to support the same IP address in multiple locations, but to NOT have fate-sharing, where a problem like a bridging loop and resulting broadcast storm at one site would take down the other site. That means we can’t just throw up a tagged VLAN link (trunk) between the DCs. Instead, we have to divide the L2 broadcast domain (the VLAN) into different L2 domains separated by a routed segment. This way we’ve created two failure domains that will not share fate.
This is one of a multi-part series on the Ethernet switching landscape I wrote to support a 2-hour presentation I made at Interop Las Vegas 2014. Part 1 of this written series appeared on NetworkComputing.com. Search for the rest of this series. Ethernet fabric is one of those terms that has been co-opted by media […]
Arista Networks sells low-latency, high-density, merchant-silicon based Ethernet switches that run a modular OS called Extensible Operating System (EOS). While the hardware is certainly commendable, I feel that software is Arista’s differentiator. From my network engineer’s perspective, EOS was built to make my life easier. The idea is that EOS can be used to get […]
Cisco Application Centric Infrastructure (ACI) Overview. This is the visionary video…the pure marketing video. It’s worth watching because it’s a good framing of the way Cisco sees the challenge of provisioning IT services, and how ACI addresses that challenge. http://www.youtube.com/watch?v=VZWwjNAiUpI Common Platform: Two Operational Models. Soni Jiandani walks through the ACI value proposition, including […]