Forum Discussion
Overlapping SNAT Translation Address and Node Address
Hello,
We currently have a F5 with two VLANS: DMZ-Pub as external, DMZ-Priv as internal.
Until now, the F5 was configured with two partitions and two route domains, one for each VLAN. So, as an example, we have some application setup like this:
VS Pub (Partition 1) 8.8.8.8 (SNAT 8.8.8.8) -> Pool Pub (Partition 1) 10.0.0.1
VS Priv (Partition 2) 10.0.0.1 (SNAT 10.0.0.1) -> Pool Priv (Partition 2) 192.168.1.1
I am working on migrating to a single partition/route domain architecture. And I am confronted to the following problem: the SNAT Translation Address (10.0.0.1) and the Pool Pub member (10.0.0.1) overlaps, and because they are now on the same partition, I get and error:
Pool /Common/xxxx member 10.0.0.1 is already a SNAT translation address
Any way to work around that ?
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com