NimbostratusHi All,
The current setup :-
Users ==> F5 ( in HA ) ==> 9 Bluecoat Proxies
The client wants source address persistence to be configured on F5. Can someone help with the configuration setup ? What should be the timeout ? On what basis should the timeout be kept ?
Cumulonimbus
AltostratusPlease use destination persistence for proxies (Cache servers) not source persistence.
CumulonimbusHello,
It's not Wildcard VS so if you use Destination Persistence (In fact, the same VS IP) you will be redirect in the same node/proxy for all users...
Can you details your response please.
Regards.
CumulonimbusPlease use destination persistence for proxies (Cache servers) not source persistence.
CumulonimbusHello,
It's not Wildcard VS so if you use Destination Persistence (In fact, the same VS IP) you will be redirect in the same node/proxy for all users...
Can you details your response please.
Regards.
Cumulonimbusit works same as source-based persistence but in this case, it will be using destination IP instead of source IP. With destination persistence, you will increase the speed of contents because of cache.
CumulonimbusThank fof your feed back, but i am not sure that destination IP was the good choice in this case. If you have 6 nodes/blucoat, you will Forward (because of destination peristence) on the same bluecoat for all user request.
In general we use destination address persistence in case of Wildcard VS (When you user F5 as default GW).
But I think in this case source persistence is the best alternative...
Altostratusit works same as source-based persistence but in this case, it will be using destination IP instead of source IP. With destination persistence, you will increase the speed of contents because of cache.
CumulonimbusThank fof your feed back, but i am not sure that destination IP was the good choice in this case. If you have 6 nodes/blucoat, you will Forward (because of destination peristence) on the same bluecoat for all user request.
In general we use destination address persistence in case of Wildcard VS (When you user F5 as default GW).
But I think in this case source persistence is the best alternative...
CumulonimbusHello,
So I advise you to set "Source Address" persistence. As you can notice in this different post it's work perfectly with bluecoat:
https://www.reddit.com/r/networking/comments/72qwmf/bluecoat_proxy_loadbalance_f5/
https://devcentral.f5.com/questions/bluecoat-proxy-loadbalancing
Regards
AltostratusWe are managing lot of bluecoat proxies which are behind F5 devices and configured with destination persistence without any issues.
CumulonimbusDefinition for destination persistence: Destination address affinity persistence You can optimize your server array with destination address affinity persistence. Destination address affinity persistence, also known as sticky persistence, directs requests for a certain destination IP address to the same server, regardless of which client made the request.
This type of persistence provides the most benefits when load balancing caching servers. A caching server intercepts web requests and returns a cached web page if it is available. In order to improve the efficiency of the cache on these servers, it is necessary to send similar requests to the same server repeatedly. You can use the destination address affinity persistence type to cache a given web page on one server instead of on every server in an array. This saves the other servers from having to duplicate the web page in their cache, wasting memory.
Cumulonimbushello Raghavendra,
Indeed if you set src address or dest address persistence it will work. however you can not advise someone without taking into account his intrastructure. When you set up LB for you proxy, you want to spread the load on all your nodes/bluecoat. In this cas destination address persistence will send all user request to the same node/bluecot, indead is benefit for caching (blucoat is done caching) because you send all User request to the same Proxy. but if you do not take into account the number of users and the capacity of the equipment you may have problems of load since the requests are sent to a single proxy.
The capacity of the equipment and the number of users must be taken into account in order to set the good peristence.
but as far as I'm concerned I share the load on different proxy avoiding saturated 1 and possibly provoked latencies due to the load.
Akhil_dev all all the information to determine the best for him. Let it decide depending his infrastructure.
Regards and thank you for your feedback
AltostratusDefinition for destination persistence: Destination address affinity persistence You can optimize your server array with destination address affinity persistence. Destination address affinity persistence, also known as sticky persistence, directs requests for a certain destination IP address to the same server, regardless of which client made the request.
This type of persistence provides the most benefits when load balancing caching servers. A caching server intercepts web requests and returns a cached web page if it is available. In order to improve the efficiency of the cache on these servers, it is necessary to send similar requests to the same server repeatedly. You can use the destination address affinity persistence type to cache a given web page on one server instead of on every server in an array. This saves the other servers from having to duplicate the web page in their cache, wasting memory.
Cumulonimbushello Raghavendra,
Indeed if you set src address or dest address persistence it will work. however you can not advise someone without taking into account his intrastructure. When you set up LB for you proxy, you want to spread the load on all your nodes/bluecoat. In this cas destination address persistence will send all user request to the same node/bluecot, indead is benefit for caching (blucoat is done caching) because you send all User request to the same Proxy. but if you do not take into account the number of users and the capacity of the equipment you may have problems of load since the requests are sent to a single proxy.
The capacity of the equipment and the number of users must be taken into account in order to set the good peristence.
but as far as I'm concerned I share the load on different proxy avoiding saturated 1 and possibly provoked latencies due to the load.
Akhil_dev all all the information to determine the best for him. Let it decide depending his infrastructure.
Regards and thank you for your feedback
AltostratusYes. You are absolutely right.My intention here is for cache servers destination persistence is the best one. Depends on requirement Akhil can decide.