It has been a while sine I've done ISLs between two MDS switches. Here is the question I have.
We have two sites A & B, the VSANs are as follows:
Site A: VSAN40, VSAN80, VSAN100
Site B: VSAN40, VSAN80, VSAN100
As soon as the FCIP tunnel was created, all of the VSANs tried to merge, but appeared as segmented. We don't want any VSANs to merge. To my knowledge the only way to prevent the VSANs from merging is by making sure that all VSANs have unique VSAN IDs. However, since we're using FCIP & IVR, I would have thought that only the VSAN that contains the FCIP interface would have tried to merge. For example, the fcip interface is in VSAN100, I would have thought that only VSAN100 would have tried to merge and the rest of the VSANs would have remained untouched. Trunking is disabled on for the fcip interface.
Our goal is to not merge the fabrics, but simply share some resources from site A to site B using FCIP and IVR.
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...