Although we have implemented the CSS and also it is working , i still doubt about the CSS working :(.
We have used the default round-robin algorithm for load balancing between servers.
In this method does the load balancing takes place session wise ( session initiated by clients ) or does the CSS sends the IP packets coming from outside world to two internal server IP's just in a roung robin manner.
I tried to search on cisco.com but could not get the exact answer.
any link on ciso.com or ant other TCP / IP web link ? Or any book which can give me the correct answer ( Tanenbaum, Komer ,... ) please suggest.
The CSS load balances per flow, unless you tell it to do otherwise (i.e. sticky by source IP). HTTP flows tend to be pretty short. Once the web page has been received all the flows are closed and new flows will be created when the user clicks a link. The CSS cleans up inactive flows (garbage collection) pretty fast.
If you require stateful sessions, where one server must perform all the transactions for a session regardless of the number of flows, you should use the sticky features.
If you want to see if traffic is going both ways, try "show services summary"... you should see hits to both services. Another way would be to check the web server logs to verify hits on both servers.
If the traffic is coming in from the outside world, is it hitting a virtual IP(VIP)? If it is, and its port 80, it should use the round robin load balance per each request. You can configure other types of balancing by using the "advance balance" feature on the content rule.
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...