ASM not working when Implementation Load Balancer (Barracuda) under ASM

Inserting a load balancer between ASM and the origin servers shouldn't cause an issue from ASM's perspective. Are you certain the necessary layer 2/3 configurations are correct between ASM and the Barracuda appliance?

How are you implementing ASM without LTM on the F5? My understanding is that you have to create the objects for LTM before you can apply ASM (Nodes, Pool and VIP). Just FYI for you, F5's implementation of LB is much more stringent. I moved some of my servers from an Alteon LB over to F5. After moving them to the F5, the application was not functioning properly. After some packet capture, we found out that the script (.NET framework) on the application was requesting the file transfer to use HTTP. F5 would not allow that, as the initial session was initiated in HTTPS. The alteon did not mind a new session was created by the script on the back end...

Actually now we use ASM without LTM and its working well. But we have a problem when we put Barracuda Load Balancer between ASM and Origin Server (2 Origin server), the problem is request never display on browser. Any body have experience with implementating ASM and Load Balancer? is there any extra configuration in ASM?

This is our scheme:

Users from outside(internet) -> ASM (10.0.32.200) -> Load Balancer (10.0.32.30)-> Origin Server (10.0.32.10 or 10.0.32.20)

This is the detail:

ASM Self-Ip : 10.0.32.50

Virtual Server(Inside ASM) Ipaddress : 10.0.32.200 pool/node : 10.0.32.30 (load balancer ip)

Load Balancer Ipaddress : 10.0.32.30 *10.0.32.10 service all (origin server 1) *10.0.32.20 service all (origin server 2)

Origin Server1 Ipaddress : 10.0.32.10 subnetmask: 255.255.255.0 gateway : 10.0.32.50 (ASM ip) Origin Server2 Ipaddress : 10.0.32.20 subnetmask: 255.255.255.0 gateway : 10.0.32.50 (ASM ip)

So when user access/request page to the Virtual server ASM (10.0.32.200) directly going to Load Balancer (10.0.32.30) and in Load Balancer will directed to origin server 1(10.0.32.10) or origin server 2(10.0.32.20) and Gateway from my origin server is direct to ASM self-ip (10.0.32.50). but the problem is that request never display on browser.

It appears that you have everything in the same network. I suspect asymmetric routing is causing your issue. Your ASM is routing the traffic through the load balancer to the origin servers, but your origin servers will respond directly back to ASM unless some source NAT is performed on the Barracuda load balancer. Your ASM will see responses from the origin servers when it expects to see them coming from the load balancer, so it drops the traffic.

I'd recommend checking the Barracuda configuration and configuring source NAT for these communications.