Forum Discussion
DM706_346160
Altostratus
AltostratusConnection Reset with Pool in Common Partition and Virtual Server in different Partition
I'm having an issue where if my pool exists in \Common partition and my Virtual Server (VS) exists in \MGMT partition, I will get a connection reset.
If I create a pool in \MGMT part with same member as what was in the \Common pool, then the VS works. And if I create a VS in \Common partition and use the \Common pool, then the that VS works as well.
I can ping the pool member IP address from either part via TMSH.
All pools and VS combinations I've configured all show as available.
Source Address Translation is set to Auto Map. HTTP 80 to HTTP 80. No SSL profiles. In reality, its a simple VS config.
These are F5VE. Each partition has its own route configuration.
Anyone know what I'm doing wrong here?
Let me answer this since I figured it out. This issue was caused because the two partitions involved both had Strict Isolation configured for the Route domain.
Even though the resolution may not be to disable Strict Isolation, that was the reason I was unable to use a pool in \Common from a virtual server in \MGMT.
DM706_346160Let me answer this since I figured it out. This issue was caused because the two partitions involved both had Strict Isolation configured for the Route domain.
Even though the resolution may not be to disable Strict Isolation, that was the reason I was unable to use a pool in \Common from a virtual server in \MGMT.