Forum Discussion
NimbostratusMS Exchange in LTM Arm Mode
Hi,
MY F5 LTM deployed in single arm mode. I want to do the load balacing for my MS exchange 2010 through the LTM. But I want to have the client IP visible for the exchange server because exchange team will not white list all the user subnets. They need the client IP visible for them for tracking and to avoid spam.
Please let me know how i can achieve this in single arm.
3 Replies
Lee_Payne_53457Cirrostratus
The easiest way to do this is to set the default gateway of the exchange server to the floating ip of the LTM on the same subnet then make sure you don't have SNAT enabled on the virtual server.
If you used a SNAT you would need to use the x-forwarded-for header in the HTTP profile and install the ISAPI filter on the servers but that only logs the true client IP not present it to the application.
Wasim_Hassan_13Hi,
thanks for the quick reply, but we dont want to have any change on the exchange cluster and in the network. It will be a big change that is why we deployed F5 in single arm mode.
We need to the the load balancing for https://webmail.abc.com
exchange team is facing issue due to client IP invisbility. Request for the help how to make client IP visible in single arm mode F5 without making any changes on the server side. I want to do all the changes in the F5. We are using HTTPS/SSL
Please assist
- Lee_Payne_53457
From my experience (I'm sure others will correct me if I'm wrong) the only way's you can see the true client IP is to either have the default gateway or use npath routing.
http://support.f5.com/kb/en-us/products/big-ip_ltm/manuals/product/ltm_implementations_guide_10_1/sol_npath.html
both of which require changes to the exchange server, if you only wanted to log the true client IP (which I don't think is what you want) then you can use the x-forwarded-for header, but those are your only options.
