I have been asked to enable 802.1q trunking from our core switches to a VmWare ESX server. The server does not support spanning-tree protocol and they recommend turning off spanning-tree all together or using portfast on the trunks. The server manufacturer says that loops are not formed; but I am not finding any info on how they do not form loops if they do not use spanning-tree.
Has anyone around here seen this sort of thing before?
First of all, unless you really are using alot of vlans on the ESX boxes, its typically better to just put additional network cards as that will also improve vmware performance. It is not that unusual to have 2-3 NICS assigned to each virtual switch. Using VLAN's is more efficient from a network engineering perspective, but vmware systems are meant to use heavy duty hardware and I frequently see systems configured with 8 NIC ports + FiberChannel or iSCSI.
Certainly from a network engineer perspective, this seems to be highly inefficient and thats where the request for 802.1q trunking usually comes in. I believe vmware's reference to loops is really w/ regard to their own virtual switches. Since virtual switches dont connect between each other and virtual machines have their nics virtualized so that there is only one/vlan per vm, there really isnt any way for loops to form inside vmware. That said, I would not turn it off on physical switches. Just use portfast.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...