30 likes | 175 Vues
This discussion focuses on the requirements and considerations for configuring LAG uplinks for Enhanced Virtual Bridging (EVB). It covers fundamental terms and concepts related to Virtual End Stations (VEB) and Virtual Ethernet Port Aggregators (VEPA), including how virtual NICs can be tailored for specific MAC addresses or operate in promiscuous mode. It also addresses key questions regarding LLDP requirements and the use of LAG with S-Channels, providing clarity on the implementation of aggregated uplinks in networking environments.
E N D
LAG Uplink for EVB Requirements and Consideration Discussion Rakesh Sharma
Basic VEB/VEPA Anatomy and Terms vNICs can be configured for specific MACsor promiscuous Virtual Machine,Virtual End Station Physical End Station Apps Apps Virtual NIC,Virtual Machine NIC(vNIC, vmnic) GOS GOS Apps Apps Apps Apps Software VEB/VEPA Ingress Egress GOS GOS GOS GOS Virtual Station Interface (VSI) * VEB/VEPA expander Physical NIC(pnic, vmnic) LAG Uplink Adjacent Bridge Bridge Port Bridge VSIs 2
Link Aggregated EVB Uplink • Requirements • EVBs have only one uplink • Uplink may be LAG, formed using multiple physical NICs • LLDP and ECP are required to run on aggregated uplink. • Questions • Q1. Are LLDP agents required to run on individual links of aggregated uplink? • A1: NO • Q2: Can Channels (S-Channels) LAG be used as EVB uplink. • A2: Yes • Q3: Can Channels (S-Channels) created on top of LAG • A3: Yes