Re: Kerberos not working with cisco content switching(CSS)
The problem with kerberos is that the user must first sends a request to kerberos server that delivers a token to then contact the destination server. Here the user will use the vip ip to request the token and when contacting the destination the ip is different and the token not accepted.
I had an issue like this in a long time ago and I don't think we ever found a solution.
Did you try to configure loopback ip addresses on the server that would be the same ip as the vip ?
Then configure service of type transparent on the CSS.
Or contact the kerberos admin guy to see if he knows a way to have a token valid on multiple platforms
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...