our VMware Server are connected to multiple networks. To each network we use port-channels for load-balancing and availability and we use 802.1q links to each customer/network. Also sometimes different customers use same VLAN-ID`s and we could not avoid this.
With VMware vNDS we have no problems with this requierment, because we can create seperate vNetwork Distributed Switches to each network/customer.
But Nexus1000V knows only one Switch per Host, so we can not seperate identical VLAN-ID´s from different customers.
I read some documents about Pinning, but this Feature is only for load-balancing with port-channels and not for selection of Uplinks.
Does anybody knows, if Cisco will implement switching instances in Nexus 1000V or Q-in-Q ( double tagging ) ??
This has also come up a few times. We are working on a solution to allow you to have the same VLAN but different paths. It should be possible when we release Virtual Security Gateway to provide a solution but as far as a native solution with just Nexus 1000V we are working on it.
I believe the solution is called Network Segmentaion along with VXLAN, vShield Manager and vCloud Director. Maybe an implementation like vDS where you could provide the same VLAN-ID on different physical interfaces is just to easy.
Much more easier and standardised could be a solution with Q-in-Q. With a support of multiple S-VLAN´s per interface it should be possible to provide the services to multiple customers also via one interface. Then a customer aggregation switch could push and pop the outer vlan tag.
Regarding your question about multiple VEM, until now I have never heard about it. And maybe there is a disadvantage with the scaling limit of 64 VEM per VSM.
Any ideas why Cisco doesn´t provide Q-in-Q on N1K?
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
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...