Note<\/em> : This example is based on a platform with 2 cores.<\/p>\nConnection 1–> TMM0 –> 192.168.1.1:80
\nConnection 2–> TMM1 –> 192.168.1.1:80
\nConnection 3–> TMM0 –> 192.168.1.2:80
\nConnection 4–> TMM1 –> 192.168.1.2:80<\/p>\n
Here you can see that the first 2 connections are sent to 192.168.1.1, and then the following 2 sent to 192.168.1.2.
\nSo how is traffic distributed when CMP is disabled ?<\/p>\n
Connection 1–> 192.168.1.1:80
\nConnection 2–> 192.168.1.2:80
\nConnection 3–> 192.168.1.1:80
\nConnection 4–> 192.168.1.2:80<\/p>\n
To disable CMP the following bigpipe commands are used,<\/p>\n
[root@f5ltm:Active] config #<\/span> bigpipe virtual VS-172.16.100.10-80 cmp disable<\/pre>\n[root@f5ltm:Active] config #<\/span> bigpipe save
\n\/config\/bigip.conf was renamed to \/config\/bigip.conf.bak (482 lines).<\/span>
\n\/config\/bigip_local.conf was renamed to \/config\/bigip_local.conf.bak (1 lines).<\/span>
\n\/config\/bigip_sys.conf was renamed to \/config\/bigip_sys.conf.bak (29 lines).<\/span><\/p>\n[root@f5ltm:Active] config #<\/span> bigpipe virtual VS-172.16.100.10-80 cmp show
\nVIRTUAL VS-172.16.100.10-80 – CMP: disable<\/span><\/p>\n<\/span>LB::detach
\n<\/strong><\/span><\/h4>\nTo ensure that each request is sent to a different server the LB::detach command is used.
\nThis command detaches the server-side connection from the client-side.<\/p>\n
Based on this create an iRule (using the syntax below) and assign it to your virtual server.<\/p>\n
when HTTP_REQUEST { \r\n\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 LB::detach\r\n}<\/pre>\n