Alas if you put the 300 into AG mode and you have targets (storage arrays) in the VSAN and you have Qlogic HBA's, that causes much drama as well. Its all to do with OUI ID's. Its not a simple exercise to fix that and I would not consider it worth while. A MDS 9124 is so well priced that why would you muck about with Brocades? If they don't want to play the interop game with other vendors, its their own fault.
Nexus 5010 is connected to the MDS via the expansion modules so that provides the storage as such to the 5010.
The servers have Converged Network Adaptors (CNA) that connect to the Nexus 5010. That means that the server uses FCoE to at least the Nexus and then the Nexus uses Fibre Channel to the storage array.
Brocade also has a solution (the 8000 has a similar ability to the Nexus 5010/5020) and you still need the Brocade switching hardware such as the 300.
So far, the 8000 has 8 Gpbs abilities and the Nexus is still only 4 Gpbs. Vendors are producing Storage ports now that run at 8 Gpbs so Brocade actually have the jump on Cisco in this respect. The FC devices that are connected to the Nexus would most likely be targets not initiators.
FCoE has distance limitations.
FCoE is not FCIP. There is no IP protocol in FCoE.
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...