Yes this is a new install for us. Our senior network engineer is unable to figure it out so I have been beating on it this afternoon and per the couple of strings I see here in the forums, this is a known problem. Let me know if you find out anything from Cisco TAC. I haven't opened a TAC case yet, since this is not a show stopper for us right now.
Just a side note, this morning I removed the DHCP helpers and configured the interface vlan for netflows and I am now receiving netflows in Solarwinds Orion. So I think this supports the fact that the bug is not fixed.
Thanks for the info, I just ran the command you sent in the default vdc and then changed to my production vdc and was able to add the dhcp helpers back to the interface vlan with no issues. Guess I need to keep an eye on it for a while and see if I continue to receive netflows. Thanks again for the info.
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...