I don't like that much replaying to myself, but for the record:
Learning is fun, sometimes It seems that, after all, workstation vswitch is kind of 802.1q capable.
Kind of, because proper term would be transparent. The vswitch in workstation actually does not care of vlan tags, so if your uplink is a trunk, all your vnics are trunks too. I was misslead by the windows driver filtering the tags in a test.
Other thing that is getting in the way is that somehow vmware insist in VLAN1 being native.
And that 1000v VSM assumes access ports into vlans. All this needs some thinking to get control packets get L2 connectivity between VSM and VEM.
But if you have an external switch and 2 real NICs, it can be done. Playing with VLAN1 as control seems to work too. I have not been able to find L3 control documentation...
If anybody cares about all this, please raise your hand (virtually of course) or else, this is it for me here.
This document will provide screenshots to outline the steps to setup
TACACS+ configuration to ACI and also the configuration required on
Cisco ACS server. Please find the official Cisco guide for configuring
TACACS+ Authentication to ACI:
Is it supported or NOT supported? It's a frequently asked question.
Before APIC, release 2.3(1f), transit routing was not supported within a
single L3Out profile. In APIC, release 2.3(1f) and later, you can
configure transit routing with a single L3Out pr...
Cisco Documents are usually accurate, but when it came to the document
on Cisco APIC Signature-Based Transactions it was slightly off the mark.
This document is for those novices to API like me who cant seem to
figure out how to go about performing signat...