can't access the web application through F5 LTM

Hi, maybe the connections are traversing the mgmt gateway instead of the self ip network or maybe it have some issue when some profile breaking the SSL requests.

Could you share the VS, pool and route here? e.g.

tmsh
list /ltm virtual VIRTUAL_SERVER_NAME
list /ltm pool POOL_NAME
show /net route lookup 10.20.20.4
show /net route lookup 10.20.30.4

Plus, have the port 8543 a SSL traffic?

Thanks Cjunior for response...here are the below details \

1) ltm virtual abc.app/abc_vs { app-service /Common/abc.app/abc destination 10.10.10.3:https fallback-persistence abc.app/abc_source-addr-persistence ip-protocol tcp mask 255.255.255.255 persist { abc.app/abc_cookie-persistence { default yes } } pool abc.app/abc_pool profiles { abc.app/abc_client-ssl { context clientside } abc.app/abc_http { } abc.app/abc_oneconnect { } abc.app/abc_optimized-caching { } abc.app/abc_server-ssl { context serverside } abc.app/abc_tcp-lan-optimized { context serverside } abc.app/abc_tcp-wan-optimized { context clientside } } source 0.0.0.0/0 translate-address enabled translate-port enabled vs-index 24

2)ltm pool abc.app/abc_pool { app-service /Common/abc.app/abc load-balancing-mode least-connections-member members { 10.20.20.4:8543 { address 10.20.20.4 app-service /Common/abc.app/abc session monitor-enabled state up } 10.20.30.4:8543 { address 10.20.30.4 app-service /Common/abc.app/abc session monitor-enabled state up } } monitor abc.app/abc_https_monitor slow-ramp-time 300 }

3)show /net route lookup 10.20.20.4

Net::Routes

10.20.20.4/32 10.20.20.4/32 interface /Common/internal static

4) same as 3..but after adding static route pool member is marked as down

5) SSL handshake is getting finished

It looks fine when you have deployed from an app.

create net route 10.20.20.4/32 interface /Common/internal

Did you try to create a route to a gateway on internal vlan? e.g.

create net route 10.20.20.4/32 gw 192.168.1.1

If possible, share the internal selfip addresses here. (e.g. tmsh list net self)

Regards.

you mean gateway is selfip ? if yes while adding static route and giving gateway as self it..it does not accept. internal is my extended vlan

No, I didn't. I mean the gateway for the internal vlan that reaches the 10.20.20.4 network.

appreciate for your quick response and help!!! i was trying to add that vlan gateway for 10.20.20.4 since beginning it is not working now too.i dont see any connection/hit to this pool member. added the gateway for 10.20.30.4 --application is working but request only coming to this node.

Now, If monitor is running and it's OK, and a client request isn't work, you may need to do a SNAT or review the route back to BIG-IP. I think you can try to SNAT first. Have this option on iApp you used?