CSM: predictor hash url vs predictor hash address source
I have a CSM set up as a transparent load-balancer for our web caching appliances (bluecoat).
When using predictor hash url, certain web apps break when the client moves between cache engines. It appears the applications are using IP address as the session identifier and when the URL changes significantly the client is balanced over to another cache engine--breaking the session.
In order to work-around poorly written web applications I have had to resort to source-ip hashing. This has resulted in an uneven load distribution across our caches.
Does anyone else do transparent web cache load-balancing and have similar problems? If you are using url hashing, how did you configure your vservers and serverfarms?
Re: CSM: predictor hash url vs predictor hash address source
For URL hash method
url-hash begin-pattern [end-pattern ]
All characters between and include the keywords are included in the hash-value.The CSM looks at the first few bits in the hash-value in order to mapit to a real. If this real is "disabled", the CSM find the nextavailable real in the list.
Verify this bug for predictor hash issue:CSCeh03583
Why do you need native HA: The native HA feature allows two Cisco DCNM
appliances to run as active and standby applications, with their
embedded databases synchronized in real time. Therefore, when the active
DCNM is not functioning, the standby DCNM will...
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...