Yes. I am seeing all of these requests going to the same pool member. For my testing, I am sending a small number of requests from different devices on the same persistent connection. Given that my pool has 2 members in it and is configured as Round Robin, I expected that I would see these different requests spread across both members.
One thing to note is that the nodes in my new pool also belong to another pool that is being used by a different VS at the same time. The other VS is for any TCP traffic and uses source addr persistence, where as my VS is only capturing HTTP traffic on port 80. In addition, the other VS does not have a OneConnect profile whereas my VS does. Could that other VS be affecting how my VS is processing traffic?
My VS is using source address persistence as the fallback persistence method. However, when I send 4 requests from different devices and do "persist all show all", I see 4 universal entries in addition to other entries for requests to the other pool.
I've attached a small file with the "persist all show all" output for the nodes in my pool. You'll see other source addr entries for these nodes in there, due to these nodes being actively used by another pool. Before I ran "persist all show all", I had just send 4 requests with different device ids on the same connection. In this output, you can see 4 universal entries that correspond with those requests. So that makes me think that my persist rule is triggering correctly. However, they are all mapped to the same member.