Forward Proxy Setup is Taking Precedence Over NAT

Sorry but your statements contradict each other. You state VS+PAT for outbound, NAT for inbound then say you expect NAT for outbound but get PAT. Which is it?

Thanks for your response!!

Let me explain you with an example.

10.2.1.0/24 is the customer subnet which is behind LTM.

Forward Proxy(PAT):- VS Type:-Performance Layer 2 SNAP Pool IP-->1.1.1.2

NAT Conf:- Origin IP NAT IP 10.2.1.24---->1.1.1.1

Whenever I initiated a traffic from 10.2.1.24 it is getting PATed to SNAT IP but it supposed to use NATed which is not happening for me. PAT is taking Precedence Over NAT. Inbound connection from internet towards NAT IP is working as excepted. Only outbound connection is having issue.

In my environment, Multiple customers are hosted in Same F5 Box. So we are using Route Domain Concept to differentiate each customer subnets. Each customer is having separate route domain and separate VLAN. External VLAN(Public Subnet-1.1.1.X/24) is same for all the customer.

I hope this would answer your question

Ah. Thanks for that, it's clear now. So, SNAT will always take precedence over NAT in this scenario. You have a few options but I'd suggest an iRule would be best, along with a second SNAT Pool with IP 1.1.1.1. The rule would look like this;

when CLIENT_ACCEPTED {
 if { [IP::addr [IP::client_addr] equals 10.2.1.24] } {
  Select alternative SNAT Pool if this is 10.2.1.24
  snatpool 'name' }
  All other hosts will use the SNAT Pool assigned to the VS (1.1.1.2)
}