Over Layer 2: If the VSM and the VEM are in the same Layer 2 domain, the best way to connect them is to use the Layer 2 connectivity mode:
Nexus1000V(config-svs-domain)# svs mode L2
• Over Layer 3: If the VSM and the VEM are in different Layer 2 domains, the Layer 3 connectivity mode should be used:
Nexus1000V(config-svs-domain)# svs mode L3
The Layer 3 mode will encapsulate the packet of the Layer 2 mode using Generic Routing Encapsulation (GRE). This process requires configuration of a VMware VMkernel interface on each VMware ESX host. This VMware VMkernel interface will need to be configured and attached to a port profile with the l3control option.
Nexus1000V(config)# port-profile type vethernet L3vmkernel
The l3control configuration tells the VEM that it can use this interface to send Layer 3 packets, so even if the Cisco Nexus 1000V Series is a Layer 2 switch, it can send IP packets.
Regardless of the mode of communication between the VSM and the VEM, after the VSM recognizes the VEM, a new module will be virtually inserted into the Cisco Nexus 1000V Series Switch's virtual chassis. The VSM CLI will notify the network administrator that a new module has powered on, much as with a physical chassis.
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...