Does anybody know the difference between FC aliases, Device Aliases and Global Aliases?
The FC (aka zone?) aliases are held in the running config on the switch and also seem to be specific to a VSAN.
Global Aliases seem to be a Fabric Manager thing - does the Fabric Manager server hold a database of aliases so that they are still recognised if you plug the device into a seperate physical SAN managed by the same FM server? Presumably if you connect via a different FM server to the same switch you would get different global aliases because you are connecting to a different database?
Device aliases seem to be an extension of fc aliases (in that they are stored in the running config) that are not VSAN specific and are not restricted to being used for zoning only.
Is that about right? Which of the above are people using and how do you find it? I'm still using fcaliases, purely because I haven't tried the others, although Device Aliases looks like an interesting option...
A device alias is pretty much the same, but is used in the higher level application functions of the mds.
A great example is that there is a CFS application for distributing device aliases, where I don't think i have seen one for distributing fcaliases. It is also used to reference items in the storage services module.
You are right, global device aliases are a function of fabric manager, but can be used as a tool to migrate from fcaliases to device aliases.
So is it true that there is no advantage to choosing to use fcaliases if device aliases are available (presumably restricted by SAN-0S version, Dev aliases being introduced later..?)? And fcaliases are only there for backward compatibility now?
Device aliases and FMS Global Device Aliases are the same thing (FMS just added the word Global).
The problem with fcaliases (that device aliases solves) is that with fcaliases I could have the same alias defined in two different vsans with a different pwwn in each pwwn. Secondly, fcaliases are only restricted to zoning. Not IVR, not QOS, not CLI output (like with 'show fcns' or 'show flogi'..)
In SANOS 3.1(2), you can make a zone member of type enhanced device alias. This means that now if you swap out the hba you only have to change the device alias database, and not modify the zones. Think of it like updating the dns server with a new IP address, you don't have to tell everyone that your new hostname is www.xyz.com b/c www.abc.com failed.
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...