If they are servers in the same VTP domain, there is no difference. Creating a VLAN on a VTP server, no matter whether the switch is "core" or "edge" results in the same behavior. The VLAN database revision number is incremented on the VTP server where you created the VLAN, and subsequent VTP advertisements will contain the higher revision number and the new VLAN information. All other VTP servers and VTP clients in the same domain will update their VLAN database accordingly when they see the advertisement with the revision number higher than their own.
Assuming both the switches are in the same VTP domain, it is always advisable to add/delete VLAN from core switches, just becasue of better administration , security and control. But you can always make other edge switches in server mode. I dont see any advantage for that. Because some times edge switches are accessible to helpdesk guys.
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
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...