ACE: Can I loadbalance based on client Source IP/and client tcp source port?
We recently migrated serving a client from being thick client at the desktop to being served via a citrix farm. Prior to the migration the clients came from about 5000 unique source IP's to their VIP, now they come from only 31 unique source IP's from the citrix servers in the farm. A citrix server can host 400 client sessions, since the default action of the ACE is to loadbalance based on source IP's, the ACE is sending up to 400 sessions from one citrix server to 1 real server in the farm. Is there anyway I can loadbalance based on client source IP and tcp source port so the ACE views the 400 sessions from one citrix server as unique sessions? The application does not require persistence.
Re: ACE: Can I loadbalance based on client Source IP/and client
Thanks, but that solves for sticky, and I am trying to solve for load balancing, the decision as to what rserver to send a new tcp session to. The client only initiates a single tcp session, right now 115 or so client sessions come from a single citrix server, and right now they all go to the same rserver, is that a sticky issue or a load balancing decision? If i sticky on tcp port, will it still distribute the 115 evenly across the rservers?
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...