You have not given us much to work with here. The problem could be a configuration mistake on the 6513, it could be that the 6513 is not properly configured on the AAA server, it could be that the key used is not the same on both devices.
Posting the AAA configuration of the 6513 would be a good place to start. Also it would help if you would verify that there is IP connectivity between the 6513 and the AAA server. You could also look into the logs on the AAA server under failed attempts and tell us if there is any error message when you attempt AAA from the 6513.
If you can provide us some of the things I have asked for we may be able to find the solution to your problem.
I have looked at the config that you posted. I note that you are specifying local authentication for login to user mode and no authentication for enable mode. That is a slightly unusual combination, but if that is what you want you can do it.
Perhaps we need to clarify what the problem is. Your original post said that AAA was not working. I assumed that you were trying to communicate with an AAA server, but that is not what the config is doing. So perhaps you can clarify what about the AAA is not working.
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...