Forum Discussion
CirrusXC - geo LB to the origin servers
I have LB where 32 FQDNs are configured. Some of them require GEO LB to the different origins based on the client locations. For example client from US will connect to the origin server in US, client from EU will connect to the EU origin server.
I found follow article: https://community.f5.com/kb/technicalarticles/f5-distributed-cloud-origin-server-subset-rules/323776.
In my LB configuration I do not have any default route under "Origins" defined. Every route is defined in the "Routes" options of the LB.
In generally what I did:
- Created label for geo limits
- Assigned labels to the "Origin Pool" to label specific origin servers under "Origin Pool"
- Configured "Origin Server Subsets" under "Origin Pool"
- Adapted LB under section "Origins" I enabled "Show Advanced Fields" and created config for label created in step "1" to cover clients for US under "Origin Server Subset Rules"
- After click on "Apply" all applications related to the LB reports 503 response code.
Is there any way how to configure geo routing for one or two FQDNs on LB and do not affect remaining applications on the LB?
After many testing to configure GEO LB for application on the route level was result that this feature does not work. Also confirmed with the support that we cannot implement it on the route level.
4 Replies
JaZyRoot cause is that when "Origin Server Subset Rules" is enabled on the LB seems that all origin servers related with LB has to be configured with "Origin Server Subset Rules". Otherwise they are not available. When I enabled such options applications were available however I tried all possible configurations with labels to forward request to correct origin server but with no success.
- Nikoolayy1
MVP
This seems like a bug or RFE https://my.f5.com/manage/s/article/K000147216 If you can't make separate routes that match the host header and have a different origin pool (the same origin server but wit the subset load balancing stuff) then maybe make separate HTTP LB just for those 2 fqdn domain.
- JaZy
After many testing to configure GEO LB for application on the route level was result that this feature does not work. Also confirmed with the support that we cannot implement it on the route level.
- Nikoolayy1
I think it this is official as I have seen this more than a year ago that the subset rules are origin based and not route based even if the GUI creates the confusion that you can configure them under the route as that is just adding subset label to all the origins under that route and nothing more.
Still F5 needs to make it clear in their articles.
