In FM,server tab, I did a "purge down elements," however, the old source ports still turn up if I do a end to end analysis, described as "not in fabric." The wwns still show up in the config under fcdomain fcid database. They do no show up in FM end devices. I can't find fcdomain anywhere in FM.
This is where the difference between 'dynamic' and 'static' persistent FCIDs comes into play.
When you 'purge the fcid database' all dynamic elements get removed and none of the static ones are removed.
Any FCID that is learned by the switch and populated into the FCID database that way is always considered a 'dynamic' FCID. However, if you enter the FCID in by hand you can specify it to be static or dynamic.
Note that static and dynamic FCIDs are both persistent, only difference is the behavior when you 'purge' the FCID database.
Interesting. I did not enter the database entries. The switch "learned them" and I the switch config says they are dynamic:
vsan 600 wwn 21:00:00:e0:8b:8e:35:11 fcid 0x310000 area dynamic
and yet the don't go away after that system is removed at the physical layer.
Do I need to "no" this entries in the fcid database at the cmdline? Is there no way to do this at FM. Maybe this is a bug, if I purge the downed items, don't see why they, being dynamic, don't leave the config. Comments?
Good, the FM task you described did remove the persistant fcids tab and they left the config.
However, I saved the changes, closed the FM, restarted FM, but when I run the end-to-end connectivity analysis they still show up as "not in fabric." Where else are they "stuck" in FM? They don't show in the config anymore at all, so it must be some FM cache.
The "not in fabric" your seeing in the End to End Connectivity Analysis output is most probably nothing to do with persistent FCIDs. Please check the output of the analysis report again. You will most likely see that it is reporting an active zone that contains a member that is currently not logged into the switch.
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...