Just a basic question. We use 9509's and 9513's for our SAN configuration. If I rename either a zone or an active zoneset does this in any way disrupt the connections using the zone or the zoneset. I want to standardize the naming conventions for our systems to better identify what they serve.
I'm not sure you can just rename the zone and zoneset. I think you may have to edit the current zoneset and add in duplicate zones with the new name, then delete the existing zones, with the old name, and then reactivate the current zoneset to push the change out. As long as there is no change in zone membership, no connectivity should be impacted.
As for the zoneset name, you may have to create a duplicate zoneset with the new name, and all the zones...with the new names...then activate the new zoneset name. Again, this should cause no impact to existing connectivity since the zone members will not be changing.
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...