VXLAN EVPN ESI multi-homing on Nexus 9000

VXLAN EVPN ESI multi-homing on Nexus 9000

For years, multi-homing in VXLAN BGP/EVPN fabrics with Cisco Nexus switches meant one thing: vPC.  It works very well; two-switch redundancy, familiar operational model, no need to deeply understand EVPN’s native multi-homing details. At the same time, vPC has always carried operational overhead: peer-links, keepalive link, the potential peer-link bandwidth limitation, and the hard ceiling of two switches. With NX-OS 10.6(1), Cisco finally brings full native VXLAN EVPN ESI multi-homing on Nexus 9000!

This post digs into what that means and how it works.

Huawei-Cisco-trunk_topology

Building a LACP port-channel between Cisco and Huawei switch

Configuring a LACP link aggregation, EtherChannel, or port-channel, or Eth-trunk between Huawei and Cisco switch is something very common. But since the configuration syntax between the two vendors is different, it can be confusing.

In this article, I will show how to configure a LACP port-channel – called Eth-trunk on Huawei – properly between a Cisco catalyst switch running IOS or IOS-XE and a Huawei switch, model 6700 in this case.