Routing Question

If you have return traffic that goes direct from VLAN 200 to internal hosts, you will need to set up a second forwarding virtual server. The FVS matches destination traffic, and tells it how it is to be treated. With automap enabled, you are essentially talking to the server IP, and hearing back from the Automap address which will never work. Create the second forwarding VS as shown below where 10.x.x.x is your internal management network range. The LTM will match the MOST SPECIFIC virtual server to handle the traffic, therefore internal traffic will not use automap, but external will.

 

VLAN200-Forwarding { destination 10.x.x.x:any ip-forward mask any profiles { fastL4_stateless { } } snat none translate-address disabled translate-port disabled vlans { LAN-VLAN200 } vlans-enabled

 

Alternately, I think you could also set up an iRule to look for the destination address to belong to a group, and disable SNAT when the destination is in your group of internal addresses. That can be applied to the original Forwarding Virtual Server.

 

Here is the issue I can ping the server directly but I am unable to reach the server via Remote Desktop with the current config

 

where is rdp client? is it coming from external vlan 100?

 

what ip does rdp client connect to? is it real server ip (10.200.1.10)?

 

if yes, have you tried to configure network forwarding ip virtual server (e.g. 10.200.1.0:any/0) listening on external vlan 100?

 

Thank you both for your response, I set up the second FVS as mentioned by Chris and this fixed the original issue, however it has introduced yet another issue where where traffic that was destined from a real server on the same internal VLAN using the f5 as the DG destined for VS on the external VLAN VIP side was no longer accessible. So in essence it can hit another internal server but it can get the VIP on the External back in to that server.

 

Thank you both for your responses