MasonHarris
11 months agoEquinix Product Manager
Building Highly Resilient Networks in Network Edge - Part 4 - Virtual Connections
This is the fourth and final part of a series of posts highlighting the best practices for customers who require highly resilient networks in Network Edge. This entry highlights how to build resilient Fabric Virtual Connections.
- Virtual connections allow NE devices to connect to CSPs, NSPs and ISPs as well as co-location
- The same logic still applies: the NE device plane determines which Fabric switch is used
- The VC connection workflow is very similar to the EVP-LAN workflow with some differences
- Customers that require VC link resiliency should create two or more VCs to their NE devices with each connection traversing the Primary and Secondary fabric switch
- Some CSPs like Azure require resiliency but most do not
- The Fabric portal allows connections to be created as redundant or single-legged
- The workflow is highlighted in the next few slides for both Redundant and Clustered devices
Redundant Devices
Clustered Devices
This concludes a four part series on building Highly Resilient Networks in Equinix Network Edge. You can read the first part of this series here.
For more helpful resources please visit:
- Architecting for Resiliency https://docs.equinix.com/en-us/Content/Interconnection/NE/deploy-guide/NE-architecting-resiliency.htm
- NE Geo-Redundancy Options https://docs.equinix.com/en-us/Content/Interconnection/NE/deploy-guide/NE-geo-redund-options.htm
- NE Device Link Resiliency https://docs.equinix.com/en-us/Content/Interconnection/NE/deploy-guide/NE-device-link-resiliency.htm