Is there a way to see SAN luns from the UCS fabric interconnect.
I have recently added a 3rd and 4th vHBA to a B440 running RHEL5.
Originally I had 2 vHBAs', and each created a path to 172 luns. (I was multipathed to 172 luns)
Now I have added two additional vHBA's and my SAN admin assures me he has mapped, zoned and masked all 172 luns to the 2 new vHBA's.
So, at this time I should have 4 paths to 172 luns....but I don't.
What I see is 4 paths to 71 luns.
I still see 2 paths to all 172 luns, but only see 4 paths on 71 of them.
Its almost like my SAN admin either mapped or masked only 71 of the 172 luns to my 3rd and 4th path.
Via the RHEL5 OS I have rescaned the FC paths, rebooted, done lsscsi, looked in the lowest level places for what devices are present on my FC channels, always I see 172 devices on the 2 original FC paths and 71 devices on the 2 new FC paths.
My question is....is there a way to see all devices (luns) accociated with an vHBA from the command line in the Fabric Interconnect?
My configuration is UCS w 2 FI's, using 8Gb FC connections to Cisco 9500 directors, to an EMC DMX4.
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...