For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

wowchens's avatar
wowchens
Icon for Nimbostratus rankNimbostratus
Jun 17, 2008

Design Issues with F5 LTM for IIS and .Net Remoting

Please help with a design issue that I am having.     At one of my client here we have a requirement to setup F5 LTM for load balancing a couple of .Net Remoting Application Servers. These ...
config
design
wowchens's avatar
wowchens
Icon for Nimbostratus rankNimbostratus
Jun 17, 2008
Denny: Appreciate your response.

 

 

For your option 1, we will not be able to segment application and sys admin traffic and also I have to route all traffic through LTM. The network team here wouldn't like that at all. Also making a route on the CORE Routers to the Floating IP will void the private vlan thing completely, as it won't be private anymore. In short, you are recommending to use a single NIC configuration instead of Dual.

 

 

For Option 2, I did explore the option of using ISAPI filters, but that only helps for IIS Logging. Any sniffing or QOSing on Layer 3 would still not be possible as the client IP Address always remains the SNATed one.

 

 

If there is no other way, then I guess I have to live with what I have but I just can't convince myself that there are no other options of achieving this. I am sure a number of other companies want to preserve source IP for various reasons.

 

 

I have a similar situation for our data center in Swiss, there I am using the nPath configuration with just one NIC and One VLAN and it works great.