We have mid tiers and our server groups behind virtual IPs and have had no issues because of it. The main drawback that we have seen is in the rare case where we want to know what IP address something came from to try to track something down (e.g., we want to determine where a particular web service call is coming from) - that information just isn't available anymore. That hasn't happened very often, though.
So, basically, the AR Server will function fine, but you will lose some information in logs, since you won't know the real IP address something is coming from. Lyle From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Anderson, Doug Sent: Friday, January 13, 2012 10:37 AM To: arslist@ARSLIST.ORG Subject: Does arserver need true IP of client instead of proxy IP? ** Running ARS 7.1 (yep an oldie but a goodie). Moving to new virtual servers with a "proxy model" such that arserver would, by default, see an IP address associated with the virtual server backend rather than the client's true IP address. Will that work OK or do we need to configure the virtual server to "send the real client IP in another header field if Remedy needs it and can read it from there"? (The quotations above are from an email from our server jockey, so I passed along her terminology.) Thanks for any feedback. Doug Anderson Mayo Clinic Rochester, MN _attend WWRUG12 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
