Discovered an annoying bug creating vPC FEX-to-Hosts
First of all, thanks a lot Lucien. You are the best!
Well, I´ll be brief:
I thought, that vPC from FEX-to-Hosts work as vPC between N5K-to-FEX does. You create the Port-channel, and you move it to vPC manually.
But it´s not, from FEX-to-Host you gotta configure just the Port-channel, and then, that Port-channel is internally assigned to a vPC. Easier. That´s fine.
PROBLEM: When I removed the vpc commands underneath of the FEX-to-Host Portchannels, I realized that although the internal vPC look healthy now (up and successfull), I can still see old vPC after executing SHOW VPC:
1004 Po1004 up Not Consistency Check Not -
263147 Po1004 up success success 1-2,7-8,10-
If I create new Port-channels, just internal vPC show up.
I believe this is a bug, and there is no easy way to clear up the old/utilized vPC. I tried to #clear vPC and so forth, but no luck.
what can i tell to my customer? any chance to have this fixed?
NX-OS are updated to the last version (1month ago)
kickstart image file is: bootflash:///n5000-uk9-kickstart.5.1.3.N2.1.bin
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...