I have a question about using Standard OR basic load balancer with multiple front end IP's. I am creating load balancing rules for different front end IP's with session persistence set to client IP. When connections originating for same source IP but going to different destination IP ( i.e. different frontend-ip of LB), i expected load balancer to calculate new hash but i observe they keep going to same VM in backend pool. Following documentation on web, when session persistence is set to client IP , load balancer should look at (SRC_IP and DST_IP) and generate a hash. This does not seem to be happening. My question is how can i test/verify that load balancer calculates new hash when session affinity is set to client IP ? Here are my load balancer details: Standard SKU load balancer 1 backend pool (consisting of 3 VM's - each VM listening on 3 different ports ) 3 Frontend IP 1 health probe (HP1) Rules: IP -------------Port----Backend port ---- Pool --- Health Probe --- session-persistence Frontend IP1 --- 8080 ---- 8080 --- Pool1 ---- HP1 --- Client IP Frontend IP2 --- 8080 ---- 8081---- Pool1 ---- HP1 --- Client IP Frontend IP3 --- 8080 ---- 8082 --- Pool1 ---- HP1 --- Client IP Expected behavior: For rule 1 -- LB sends connections to VM's listening on 8080 - connection originating from new client IP 1 going to Frontend IP 1 --- load balancer sends to VM1 For rule 2 -- LB sends connections to VM's listening on 8081 --- Not OK - connection originating from new client IP 1 going to Frontend IP 2 --- load balancer still sends to VM1 --- It should send to other VM 2 or 3 as new hash is calculated for different Frontend IP For rule 3-- LB sends connections to VM's listening on 8082 --- Not OK - connection originating from new client IP 1 going to Frontend IP 3 --- load balancer still sends to VM1 --- It should send to other VM 2 or 3 as new hash is calculated for different Frontend IP Can you please explain what is wrong in the configuration or what is expected behavior in case multipe frontend IP and session affinity set to client IP ?
7 gr-alert gr_gramm gr_inline_cards gr_run_anim Style multiReplace" data-gr-id="47" id="47">IP ,</g> load balancer should look at (SRC_IP and DST_IP) and generate a hash. This does not seem to be happening.
My question is how can <g class="gr_ gr_38 gr-alert gr_tiny gr_spell gr_inline_cards gr_run_anim ContextualSpelling multiReplace" data-gr-id="38" id="38">i</g> test/verify that load balancer calculates new hash when session affinity is set to client <g class="gr_ gr_41 gr-alert gr_gramm gr_inline_cards gr_run_anim Style multiReplace" data-gr-id="41" id="41">IP ?</g>
Here are my load balancer details:
Standard SKU load balancer
1 backend pool (consisting of 3 VM's - each VM listening on 3 different ports )
3 Frontend IP
1 health probe (HP1)
Rules:
IP -------------Port----Backend port ---- Pool --- Health Probe --- session-persistence
Frontend IP1 --- 8080 ---- 8080 --- Pool1 ---- HP1 --- Client IP
Frontend IP2 --- 8080 ---- 8081---- Pool1 ---- HP1 --- Client IP
Frontend IP3 --- 8080 ---- 8082 --- Pool1 ---- HP1 --- Client IP
Expected behavior:
For rule 1 -- LB sends connections to VM's listening on 8080
- connection originating from <g class="gr_ gr_43 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins replaceWithoutSep" data-gr-id="43" id="43">new</g> client IP 1 going to Frontend IP 1 --- load balancer sends to VM1
For rule 2 -- LB sends connections to VM's listening on 8081 --- Not OK
- connection originating from <g class="gr_ gr_62 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins replaceWithoutSep" data-gr-id="62" id="62">new</g> client IP 1 going to Frontend IP 2 --- load balancer still sends to VM1 --- It should send to other VM 2 or 3 as <g class="gr_ gr_64 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins doubleReplace replaceWithoutSep" data-gr-id="64" id="64">new</g> hash is calculated for different Frontend IP
For rule 3-- LB sends connections to VM's listening on 8082 --- Not OK
- connection originating from <g class="gr_ gr_55 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins replaceWithoutSep" data-gr-id="55" id="55">new</g> client IP 1 going to Frontend IP 3 --- load balancer still sends to VM1 --- It should send to other VM 2 or 3 as <g class="gr_ gr_57 gr-alert gr_gramm gr_inline_cards gr_run_anim Grammar only-ins doubleReplace replaceWithoutSep" data-gr-id="57" id="57">new</g> hash is calculated for different Frontend IP
Can you please explain what is wrong in the configuration <g class="gr_ gr_40 gr-alert gr_gramm gr_inline_cards gr_run_anim Style multiReplace" data-gr-id="40" id="40">or what</g> is expected behavior in case<g class="gr_ gr_39 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="39" id="39">multipe</g> frontend IP and session affinity set to client <g class="gr_ gr_44 gr-alert gr_gramm gr_inline_cards gr_run_anim Style multiReplace" data-gr-id="44" id="44">IP ?</g>
