+stick the client to a server based on the configured string found in the HTTP cookie header
+stick a client to a server based on a configured string found in the URL of the HTTP request.
+The CSS selects a Server (selected from a serverfarm using the configured Loadbalance policy) and transparently generates the cookie for a client (on server's behalf), the client stores it and returns it in subsequent requests. The CSS later uses it to maintain the client-server stickiness.
ACLs are supported to control access to resources.
within 'agent' & 'customer' chat/cobrowse application, 'agent' is interecting to more than one customer at the same time. The chat sessions are running on different servers behind the loadbalancer (but single VIP). The 'agent' response need to go to respective server's chat session as and when he interects with multiple chat/cobrowse session with other individuals.
So there could be a script running at CSS which will insert/inspect a typical identification cookie and foward packets. And thus 'agent' packets can selectively go to one server for one packet and different server for another packet.
I hope you got the idea.
Is this doable with CSS? It is doable with F5 loadbalancer using its iRule.
Usually, we can access ESXi Shell by pressing Alt+F1 from ESXi DCUI (Direct Console User Interface).
But on HyperFlex system, it just shows black window.
This is expected behavior because HyperFlex redirects ESXi Shell output to SoL...
Configuring an Export Policy Using the GUI
This procedure explains how to configure an Export policy using the APIC GUI. Follow these steps to trigger a backup of your data:
On the menu bar, choose Admi...
RBAC users like email@example.com may fail HX Connect login. At that time, "Incorrect user name or password(100005)" is shown as a failure reason.
RBAC users can login to vCenter server. So, RBAC username and passwo...