When using dynamic vNICs you can't define more than one physical NIC (eth0 and eth1). If you try to create more than two vNICs (using a single VIC) with a Dynamic vNIC policy, it should error out on you during association.
The vCon connection policy is really only used for full width blades with dual mezz cards populated. This gives you some control as to which mezz card and interface vNIC/vHBAs are placed on.
With a B200, the only virtual PCI slots you'll have will be 1 and 2. To my understanding you need the vHBA's as the lowest PCI device # - is that correct?
For your placement policy, set slot 1 to be "Assigned Only", and leave the rest set as "All". Next assign your vHBAs both to Slot 1, and click ok. Associate the Service Profile to the blade and report the results.
This should set the desired placement and ordering for your vHBAs as the lowest.
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...