Dilemma: If I provide a L2-Extended DCI solution within a traditional network architecture, how can I limit latency and ensure users at remote sites access compute resources at the correct data center?
For instance, if I have a single subnet stretched between DCs, the prefix would be advertised out both. If I have a server at the 2nd data center but the traffic comes ingress through the 1st, it would then have to route via the DCI and that produces a lot of latency, especially if the data centers are geographically disparate.
LISP doesn't appeal to me. What are some other solutions?
Cisco Champion Radio · S7|E30 Taming Your AI/ ML Workloads with Kubeflow
As organizations increasingly introduce machine learning (ML) capabilities to their existing products, their artificial intelligence (AI) projects and operations complexity grows. A...
Cisco Data Center Networking Demo Series – Assurance and Insights
Live webinar: Cisco Data Center Networking Demo Series – Assurance and InsightsThursday, August 27, 202010:00 AM Pacific Standard Time (San Francisco, GTM -08:00)
With Cisco Data Cen...
The Future of Fast: Introducing Nexus 3550 Series and Nexus SmartNICs
Network Insider Live Webinar
Tuesday, August 25, 202010:00 am Pacific Time(San Francisco, GMT-08:00)
The Nexus 3550 Series and Nexus SmartNIC technology, formerly Exablaze...
Original Blog published @ https://blogs.cisco.com/datacenter/spinning-up-an-nvme-over-fibre-channel-strategy
Every so often there comes a time when we witness a major shift in the networking industry that fundamentally changes the landscap...