Somebody know the best way (with steps) to connect two productives fabrics???
Here the scenario, the fabric 1 is one MDS 9506 with only one VSAN , the fabric 2 are 3 switch MDS 6513 in a Core-Edge topology and 3 VSANs, I need connect the single switch to the Core-Switch keeping the configuration without merge, at end get a one Fabric with 4 VSANs and use the MDS 9506 like edge-storage and be able to reach the storage connected at Edge-Storage Switch.
Are there some important considerations that I have to take???
If the switch with 1 VSAN is not a common VSAN with the other fabric, then there should be no issue. Simply create the VSAN on the core and trunk it to the other Fabric. If the VSAN is one of your currently deployed VSAN's, then you need to pay careful attention to parameters that should match within the VSAN, such as timers, zones (zoneset members should be identical for like zones), etc.
Which scenerio is it, is it its own VSAN or is it a VSAN that is in common with the other Fabric?
I would point you to the MDS Configuration Guide, as there is no substitute for thorough knowledge. The short of it is, you could setup VSAN 2 on both fabrics, connect them with a TE port and you should be fine with little to no risk of disrupting either fabric.
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...