I know for a fact that the keys are the same.. Just to be sure though I changed them both (the one on the ACS and the one on the ANM) to the digit 1 still no go, I'm getting the same Key Mismatch failed login on the ACS box.
Has anyone come across this yet by any chance? All of my searching around the Net has only produced a few things that tell me to ensure the keys are the same.. which they are. I can only assume something is corrupting the key somewhere on the ANM.
The ANM is running on a RHEL 32bit server in a VM ESX environment.
make sure you are using an ACS supported browser when configuring the key on ACS, i've seen before unsupported browsers submit junk as the password into ACS.
to verify if the tacacs+ key is really corrupted by ANM, get a packet capture of the tacacs+ packets. then using wireshark you can decrypt the tacacs packets after providing it with the tacacs+ pre-shared key in preferences-> protocols->tacacs+. if the decryption of the tacacs+ request succeeds and you see the tacacs+ attributes, then verify that the user password attribute is correct, then you know the pre-shared key and user password are correct and matching. otherwise the ANM is not encrypting properly.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...