Forum Discussion
NimbostratusPriority Group activation with Connection Limit on Member
Hello all,
I found an interesting topic in the 301a Blueprint where I will take the exam. Blueprint: https://www.f5.com/pdf/certification/exams/blueprint-ltm-specialist-a.pdf
Objective 3.03 Describe how priority groups are affected by connection limits
I couldn't find any document by F5 for this topic in combination from Priority Groups AND connection Limites on the pool Member
So for example we have a Pool of 3 Member, Loadbalancing via least connection node 2 Member are in Priority Group 10 1 Member is in Priority Group 5 Activation: less than 2 Each of the 3 member has a connection limit of 100
so everything starts fine and Member 1 of Group 10 has reached his connection limit and Member 2 of Group 10 has 80 connections.
the next connection(181) CAN be loadbalanced to the Member 2 of Group 10 this is clear
BUT does the priority group activation already apply here? so connections could also be assigned to the member of Priority Group 5?
with least connection node this would be the most feasible member I assume.
Have anyone here a Document where this is pointed out? Or have something like this in production?
Hopefully it was clear what I asked :)
Regards Michele
nitass_89166Noctilucent
So for example we have a Pool of 3 Member, Loadbalancing via least connection node 2 Member are in Priority Group 10 1 Member is in Priority Group 5 Activation: less than 2 Each of the 3 member has a connection limit of 100
so everything starts fine and Member 1 of Group 10 has reached his connection limit and Member 2 of Group 10 has 80 connections.
the next connection(181) CAN be loadbalanced to the Member 2 of Group 10 this is clear
i never tested this scenario but i thought the priority group 5 would be activated when connection limit is reached on one member of priority group 10.
Archived - K7127: New connection is not directed to the next priority group when the connection limit is reached
https://support.f5.com/csp/article/K7127
Michele_JetzI think in the same way but like you I never saw it in real and was to late to replay it in my lab
The Article you found is for versions <10 so I think this should work now but a real reference would be great
anyway I passed the exam today so the rush for the 301b begins :)
- nitass
Employee
So for example we have a Pool of 3 Member, Loadbalancing via least connection node 2 Member are in Priority Group 10 1 Member is in Priority Group 5 Activation: less than 2 Each of the 3 member has a connection limit of 100
so everything starts fine and Member 1 of Group 10 has reached his connection limit and Member 2 of Group 10 has 80 connections.
the next connection(181) CAN be loadbalanced to the Member 2 of Group 10 this is clear
i never tested this scenario but i thought the priority group 5 would be activated when connection limit is reached on one member of priority group 10.
Archived - K7127: New connection is not directed to the next priority group when the connection limit is reached
https://support.f5.com/csp/article/K7127- Michele_Jetz
I think in the same way but like you I never saw it in real and was to late to replay it in my lab
The Article you found is for versions <10 so I think this should work now but a real reference would be great
anyway I passed the exam today so the rush for the 301b begins :)
