Here's the complete text for both fields:

Your idea (one sentence summary):

Add per-subset fallback priority chains and simplify geo-based origin routing configuration in HTTP Load Balancer

Please add more details:

We are a payments company (Nayax) operating production infrastructure across three datacenters (IL, DE, US) serving 56+ production domains via F5 XC HTTP Load Balancers. We attempted to implement geo-based origin routing with automatic and manual failover using Origin Server Subset Rules. This process exposed two significant gaps in the current F5 XC feature set:

1. Geo routing is extremely difficult to configure correctly

Setting up geo-based origin routing requires labels to be configured consistently across four separate layers simultaneously: origin server labels, pool metadata labels, route endpoint subsets, and subset rule actions. Any mismatch in casing or placement across these layers causes silent routing failures that are very hard to diagnose. We spent weeks troubleshooting inconsistent routing behavior before F5 Advanced Engineering confirmed the correct architecture (single pool with Subset Load Balancing enabled per article K000146658).

Additionally, the current documentation does not clearly explain the interaction between these four layers, which PoP-level propagation delays affect label changes, and how to verify that a configuration change has taken effect across all nodes in a PoP.

Suggested improvement: Provide a guided geo routing configuration wizard or a validated reference architecture in the console, and expose per-node subset state visibility in the request logs or a dedicated health dashboard.

2. Subset fallback policy is global — per-region fallback chains are not supported

The Subset Fallback Policy is a single global setting for the entire origin pool. This means it is impossible to define different fallback targets per user region. Our requirements are:
- When IL is unavailable → Middle East users should fall back to DE
- When DE is unavailable → European users should fall back to IL
- When US is unavailable → Americas users should fall back to DE

With the current implementation, the fallback policy applies to all users regardless of their region. Setting the fallback to DC=DE breaks DE closure (503 errors when DE is also unavailable). Setting it to "Select Any Origin Server" results in non-deterministic fallback — users may land on any remaining DC rather than the geographically preferred one.

This limitation makes it impossible to implement a production-grade geo routing and failover solution using F5 XC subset rules alone without external DNS-layer involvement.

Suggested improvement: Allow subset fallback chains to be defined per subset rule, so each geo region can have its own ordered fallback sequence. For example:
- Middle East rule: IL → DE → US
- Europe rule: DE → IL → US
- Americas rule: US → DE → IL

This would make F5 XC Origin Server Subset Rules a complete and self-contained solution for geo routing with regional failover, which is a common enterprise requirement.

This feature request is related to active support case 01216901 — "Inconsistent origin pool selection with subset rules across multiple nodes at same PoP" — where these limitations were identified and confirmed by F5 Advanced Engineering during hands-on testing.