Yes you current configuration will work with UCS, the only thing you have to know every vhba can only be pinned to a single uplink interface which means a single vhba won't be able to talk to both SAN arrays, and that you will have to use static pinning to make sure you assigned each vhba to the correct SAN array.
If you want to have the a single hba have access to both SAN arrays, I would recommend you to connect both SAN arrays to the same SAN switch and make the correct zoning configuration. Take a look at the link below
Designing and Deploying a Cisco Unified Computing System SAN Using Cisco MDS 9000 Family Switches
If I understand correctly, static-pinning will pin the vHBA to the uplink port (or port-channel) but it doesn't modify the "allowed VSANs" on the uplink port. (Atleast, that's what happens to VLANs in LAN). Does it affect operationally, during failure, for example?
I know it can be catastrophic in case of LAN having Disjoint L2 but can be rectified using VLAN Manager or VLAN Group feature. Is a similar feature available for SAN?
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...