Cloudpath Cookie Error During Workflow Redirection in Active-Active Deployment with Load Balancer Using Round Robin
Summary
Customers may encounter cookie-related errors during workflow redirection in RUCKUS Cloudpath when deployed in an Active-Active setup with a load balancer on any vendor. This typically occurs when session persistence is not enabled, causing requests from a single client to be distributed across multiple nodes. This article explains the root cause, symptoms, and required load balancer configuration to resolve the issueQuestion
Why do users experience cookie-related errors during workflow redirection in Cloudpath Active-Active deployments using a load balancer?Process Flow:
- Initial Request:
The client sends a request, and the load balancer selects a backend server using Round Robin - Persistence Mapping:
The load balancer records the client’s IP address and maps it to the selected backend node - Subsequent Requests:
All future requests from the same client IP are directed to the same backend node for a defined timeout period
Key Notes:
-
Session persistence is mandatory for Active-Active Cloudpath deployments
- Vendor terminology may vary:
- Sticky Sessions
- Source IP Affinity
- Persistence IP (PIP)
Article Number:
000015441
Updated:
July 01, 2026 11:29 PM (about 22 hours ago)
Tags:
Configuration, Performance, Cloudpath
Votes:
0
This article is:
helpful
not helpful