Without knowing how your appliaction is supposed to work, it's very hard to give you an answer, but it could be that the application needs to be modified so that the address of the VIP instead of the real address of the server is returned on the link to the report.
Anyway, to really see what is going on, I would recommend you to get traffic captures on both sides of the ACE while doing a test connection. Since these captures will be encrypted, you can either use the SSL private key from the ACE and server to decrypt the connections, or, assuming your applciation supports it, disabling the SSL part of the configuration during the test (to get the captures in plain HTTP)
thank you for the answer. I finally got the answer from the programmers yesterday. There really were problems with fixed (not relative) references in the code. Since corrections have been made, everything works fine.
I was not sure, if there are not some obstacles (in ACE) when opening new connection (popup window). Now I see the ACE config was correct.
Moquery is the command line cousin of Vizore, it's very helpful and efficient sometimes during the troubleshooting. This article aims to provide moquery cheat sheet to the users for some most common seen scenarios.
Here is the checklist before customers/partners contact Cisco TAC:
Firmware Version of APIC and Switch
Download Switch and APIC techsupport logs
Problem description (Symptoms with details)
Business impact (eg, what kind of services...
moquery usageAPIC moquerySwitchmoquery
This document discuss a common issue observed during the VMM integration & VM workload migration to ACI fabric.
VMware Virtual machines are hosted in Cisco UCS-B seri...