--> The concept of persistence is used to send the client traffic to the same pool member once the connection is established.
--> This is mainly used in the case of stateful applications.
--> Each and every Persistence record contains the following information:
1) Client IP address
2) Type of Persistence ( Source/Destination/Hash etc)
3) Pool Member selected under the virtual server
--> We can implement complex persistence requirements by using below methods:
Match Across Service:
--> Match Across Services feature is useful for combined HTTP/HTTPS support for the same website.
--> Client Traffic can be sent to the same pool member for both HTTP/HTTPS under the same virtual server.
Requirements:
1) Same Virtual Server IP address
2) Different Service under Virtual Server ( Port Number)
3) Same Pool Member IP address under Pool
Ex: Website: www.site.com (192.168.1.1)
VS1_HTTP ( 192.168.1.1:80)
Persistence Type: Source Address Affinity
HTTP Pool: Pool_HTTP
Members:
10.0.0.1:80
10.0.0.2:80
10.0.0.3:80
-------------
VS1_HTTPS ( 192.168.1.1:443)
Persistence Type: Source Address Affinity
HTTPS Pool: Pool_HTTPS
Members:
10.0.0.1:443
10.0.0.2:443
10.0.0.3:443
--> In the above Case, Whenever the user tries to access the www.site.com using HTTP/HTTPS then the client traffic will be sent to the same pool member once the connection is established.
Match Across Virtual Server:
--> Match Across virtual server feature is useful for multiple virtual servers being used for the same website.
--> Client Traffic can be sent to the same pool member for all the Virtual servers where Match Across Virtual Servers being implemented.
Requirements:
1) Different Virtual Server IP addresses
2) Different Services/Same Services( Port Number)
3) Same Pool Member IP address under Pool
Ex: Website: www.site.com uses both 192.168.1.1 and 192.168.1.2 virtual servers
VS1_HTTPS ( 192.168.1.1:443)
Persistence Type: Source Address Affinity
HTTPS Pool: Pool_HTTPS
Members:
10.0.0.1:443
10.0.0.2:443
10.0.0.3:443
-------------
VS2_HTTPS ( 192.168.1.2:8443)
Persistence Type: Source Address Affinity
HTTPS Pool: Pool_HTTPS_8443
Members:
10.0.0.1:8443
10.0.0.2:8443
10.0.0.3:8443
--> In the above Case, Whenever the user tries to access the www.site.com then the client traffic will be sent to the same pool member once the connection is established in all the virtual servers configured under match across virtual servers.
Match Across Pools:
--> Match Across pool feature is useful when different URLs under single website need to be sent to different pools in the same virtual server.
--> Sending different URL traffic to different Pools can be achieved by using the concept of IRULES or LTM Policies.
--> It is not recommended to configure Match Across Pools feature under Persistence.
Requirements:
--> Same Virtual Server IP Address
--> Multiple Pools
Ex: Website: www.site.com uses both 192.168.1.1 virtual servers with multiple pools one for mobile and one for desktop traffic.
VS1_HTTPS ( 192.168.1.1:443)
Persistence Type: Source Address Affinity
Mobile Pool: Pool_Mobile
Members:
10.0.0.1:443
10.0.0.2:443
10.0.0.3:443
-------------
Desktop Pool: Pool_Desktop
Members:
10.0.0.4:443
10.0.0.5:443
10.0.0.6:443
--> In the above Case, Whenever the user tries to access the www.site.com then the client traffic will be sent to the same pool member once the connection is established which are configured under match across pools.
--> This is mainly used in the case of stateful applications.
--> Each and every Persistence record contains the following information:
1) Client IP address
2) Type of Persistence ( Source/Destination/Hash etc)
3) Pool Member selected under the virtual server
--> We can implement complex persistence requirements by using below methods:
Match Across Service:
--> Match Across Services feature is useful for combined HTTP/HTTPS support for the same website.
--> Client Traffic can be sent to the same pool member for both HTTP/HTTPS under the same virtual server.
Requirements:
1) Same Virtual Server IP address
2) Different Service under Virtual Server ( Port Number)
3) Same Pool Member IP address under Pool
Ex: Website: www.site.com (192.168.1.1)
VS1_HTTP ( 192.168.1.1:80)
Persistence Type: Source Address Affinity
HTTP Pool: Pool_HTTP
Members:
10.0.0.1:80
10.0.0.2:80
10.0.0.3:80
-------------
VS1_HTTPS ( 192.168.1.1:443)
Persistence Type: Source Address Affinity
HTTPS Pool: Pool_HTTPS
Members:
10.0.0.1:443
10.0.0.2:443
10.0.0.3:443
--> In the above Case, Whenever the user tries to access the www.site.com using HTTP/HTTPS then the client traffic will be sent to the same pool member once the connection is established.
Match Across Virtual Server:
--> Match Across virtual server feature is useful for multiple virtual servers being used for the same website.
--> Client Traffic can be sent to the same pool member for all the Virtual servers where Match Across Virtual Servers being implemented.
Requirements:
1) Different Virtual Server IP addresses
2) Different Services/Same Services( Port Number)
3) Same Pool Member IP address under Pool
Ex: Website: www.site.com uses both 192.168.1.1 and 192.168.1.2 virtual servers
VS1_HTTPS ( 192.168.1.1:443)
Persistence Type: Source Address Affinity
HTTPS Pool: Pool_HTTPS
Members:
10.0.0.1:443
10.0.0.2:443
10.0.0.3:443
-------------
VS2_HTTPS ( 192.168.1.2:8443)
Persistence Type: Source Address Affinity
HTTPS Pool: Pool_HTTPS_8443
Members:
10.0.0.1:8443
10.0.0.2:8443
10.0.0.3:8443
--> In the above Case, Whenever the user tries to access the www.site.com then the client traffic will be sent to the same pool member once the connection is established in all the virtual servers configured under match across virtual servers.
Match Across Pools:
--> Match Across pool feature is useful when different URLs under single website need to be sent to different pools in the same virtual server.
--> Sending different URL traffic to different Pools can be achieved by using the concept of IRULES or LTM Policies.
--> It is not recommended to configure Match Across Pools feature under Persistence.
Requirements:
--> Same Virtual Server IP Address
--> Multiple Pools
Ex: Website: www.site.com uses both 192.168.1.1 virtual servers with multiple pools one for mobile and one for desktop traffic.
VS1_HTTPS ( 192.168.1.1:443)
Persistence Type: Source Address Affinity
Mobile Pool: Pool_Mobile
Members:
10.0.0.1:443
10.0.0.2:443
10.0.0.3:443
-------------
Desktop Pool: Pool_Desktop
Members:
10.0.0.4:443
10.0.0.5:443
10.0.0.6:443
--> In the above Case, Whenever the user tries to access the www.site.com then the client traffic will be sent to the same pool member once the connection is established which are configured under match across pools.
0 comments:
Post a Comment