Building Highly Resilient Networks in Network Edge - Part 3 - EVP-LANs

This is the third 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 EVP-LAN connections in Network Edge.

• EVP-LAN is another method to connection Network Edge devices
• EVP-LANs differ from DLGs in that they connect to Network Edge devices and Fabric ports​
• All EVP-LAN connections go to the Fabric, even for devices in the same metro--this is in contrast to DLGs which can be local or remote.​
• As of November 2023, multiple NE devices in the same metro can be part of the same EVP-LAN network, removing the previous restriction of a single NE device per metro.​
• Customers that require maximum resiliency should deploy additional EVP-LANs that span both the Primary and Secondary Fabric networks
• The same logic applies for EVP-LANs such that they should spread across Primary and Secondary Fabric planes​
• The current maximum bandwidth for all EVP-LAN connections in the same metro is 10GB. This may change in the future.

Redundant Devices

• For proper resiliency, each device in the Redundant Device pair will require a single connection to two different EVP-Networks​
• The Primary device on the Primary plane will use the Primary Fabric switch​
• The Secondary device on the Secondary plane will use the Secondary Fabric switch​

 

 

Clustered Devices

• Clustered devices are different in that the workflow allows connections to be built to either the Primary or Secondary Fabric​
• For proper resiliency, each node in the Cluster will require a single connection to two different EVP-Networks​