LB type is configured as Sticky By Source IP, users are complaining that they are always routing to same server in pool irrespective of any timeout durations set in LB or server,
My understanding is when they go through proxy all users in that company will be hitting one server because of the Natted proxy IP so the LB table maintains the src IP as proxy NAT IP and thinks it is coming from same client machine and keep sending it to same server in pool.
I am thinking of changing it to arrow point cookie, what is your suggestion on it. Is there any issue if we use arrow point over sticky by src ip.
1. What is the timeout set on stickybysrcIP?
2. How does the timeout work, is it times out when the client session is inactive for the configured timeout limit in LB?
It doesnt make sense to use Source IP based stickiness with Mega Proxies involved. As the ACE will only see the traffic initiated from proxy servers not the client itself.
In case of heavily used proxy the sticky entry will never timeout. Sticky entries only times out when the connection is idle for that particulart SRC IP. If sticky timeout is 60 minute and a connection is attempted by the host at 59th minute then the sticky entry timeout counter will initialized.
Cookie based persistence is recommended when proxies are involved.
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 firstname.lastname@example.org 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...