The IronPort does not offer the same "Failover" that is built into the BlueCoat product (if you are familiar with that one), so a couple of options could be to either use a load balancer or a PAC file to perform that function. I currently use a PAC file with a Return statement of: " PROXY x.x.x.x:8080; PROXY x.x.x.x:8080"; " in order to accomplish a poor man's fail-over. It is not a great solution in that the users’ browser has to time-out in order to utilize the second proxy and as well there are some caching issues... once that time-out occurs the browser must be restarted in order to utilize and or attempt to utilize the first proxy again. There are some custom options for setting IE to not cache in that manner... if you want to tinker under the hood at the registry level. In addition - for systems that can't utilize a PAC file I have a DNS record that round-robins the two proxy ip's... but this has its own caveats as well. Hope that helps!
... View more
Does anyone have any experiences to share regarding the duplication (or more accurately… the over duplication) of log subscriptions? I currently have in place two Access Log subscriptions headed to two different log servers but would like to create third Access Log subscription in order to allow me to utilize the on-box grep option for live support. Anyone have any pros/cons to share?
... View more