Our network topology is as per the attachement âCSS Topology Diag.jpgâ. The users behind the CORE network will access the application through the VIP address â192.168.10.171â. SSL card has been installed on the CSS's and the SSL gets terminated on the CSS. The traffic between CSS and the physical servers are on âhttpâ.
Now when the users tries to access the application using SSL (https://192.168.10.171) the application response is very slow, however when the users tries to access the application using http (http://192.168.10.171) application response is ok.
Find the attached configurations of the primary and secondary CSS. Any inputs to resolve this issue..??
(Note: It take nearly 20 - 30 seconds to get the page when users initiate a connection through https and however when the users initiate the http connection page gets displayed in 2 - 3 seconds)
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...