Issue - Cisco ASA can't communicate between Private and Public Network

[Netty]

Hi There,

I got an issue after migrating the firewall from Cisco ASA 5545 to 5525.

1 of 20 tenants can't communicate to Public Network but can still communicate between Private Network,

but the Public Interface (Gi0/0.5) can ping to the Public Network.

interface GigabitEthernet0/0.5
mac-address 0200.0005.1d00 standby 0200.0005.1d01
nameif INTERNET
security-level 0
ip address 27.254.23.xx 255.255.255.128 standby 27.254.23.xx
!
interface GigabitEthernet0/2.224
nameif IN-01
security-level 30
ip address 10.10.124.xx 255.255.255.224 standby 10.10.124.xx
!
interface GigabitEthernet0/4.123
nameif OUT-01
security-level 0
ip address 10.10.124.xx 255.255.255.224 standby 10.10.124.xx

So, what is pointed to is the NAT table issue.

Did you guy heard about the bug related to NAT table or the issue like this before?

Thank you,

Net

[MHM Cisco World]

you have two interface OUT-01 and INTERNET 
which one you use in 
NAT and Routing traffic ?

[Netty]

I am using NAT for the INTERNET interface
and static routing for OUT-01

[MHM Cisco World]

sorry again 
your Host connect to IN-01 and need to access internet what Interface is egress of traffic ?
are this interface is config with NATing ?

[Netty]

The host behind the IN-01 interface will access the internet through the INTERNET interface.

[MHM Cisco World]

you have default route toward the INTER link and you have NATing to NAT private to public IP 
NOW for OUTside we need statice route to forward traffic via this interface and we need in router or L3SW connect to FW static route also toward the ASA for subnet connect to INside 

you have missing one of route either in ASA or in R/L3SW connect to ASA

[Netty]

Hi Guy
I am sorry for the unclear information.

The problem is the VM behind the private subnet (R3) can't reach the internet (8.8.8.8 behind R1 router)
but able to reach the VM behind another subnet interface with in the firewall.

and the INTER interface on the firewall itself can reach the 8.8.8.8 (behind the 1.1.1.1 or R1 Router in your picture)

Commonly, the issue like this we always point to the NAT configuration, am I correct?

But as I checked, the NAT configuration on the existing firewall and new firewall is totally the same.
So, Did you guy used to facing the problem like this ?

IOS version : 9.14(4)7 on both existing and new firewall

[MHM Cisco World]

Yes it point to NAT 
can you do packet tracer for this traffic and share the result here 
NOTE:- please add detail keyword to packet tracer 
Thanks 
MHM