Basically to make the process as clear as clear you need to deregister the device from both sides.
First go to the CDM and delete the device, make sure it does not show up in the device list.
Then go to the old WAE and run the following command:
WAE-612#cms deregister force
This will delete old the cms information on the WAE and also forces the CDM to clear up the device from the CMS database.
Next go to the new WAE configure the IP and domain-names, you can even use the same hostname the old WAE had, make sure you can ping the CDM and configure the cdm ip and do cms enable
WAE-674(config)#cdm ip X.X.X.X
Go to the CDM and you'll see the device as "inactive", go activate the device and then you can either manually copy the configuration from the old WAE or if you have a device-group using a defined configuration simply add the device and the CDM should replicate the config.
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...