{"id":789,"date":"2013-08-01T00:00:00","date_gmt":"2013-08-01T00:00:00","guid":{"rendered":"https:\/\/fir3netwp.gmsrrpobkbd.com\/2013\/08\/01\/why-is-the-client-addr-field-within-the-uie-not-populated\/"},"modified":"2023-01-06T16:53:19","modified_gmt":"2023-01-06T16:53:19","slug":"why-is-the-client-addr-field-within-the-uie-not-populated","status":"publish","type":"post","link":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/why-is-the-client-addr-field-within-the-uie-not-populated.html","title":{"rendered":"UIE Persistence Record’s Client Addr field is not Populated"},"content":{"rendered":"
When viewing the UIE persistence records you observe that the Client Addr field is not populated.<\/p>\n
root@f5ltm(Active)(tmos)# show ltm persistence persist-records all-properties\r\nSys::Persistent Connections\r\nuniversal - 172.16.100.200:80 - 192.168.1.31:80\r\n-----------------------------------------------------------\r\nTMM\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\r\nMode\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 universal\r\nKey\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 8ffa6c0012825a76b3b68d10a9c68ad3\r\nAge (sec.)\u00a0\u00a0\u00a0 4\r\nVirtual Name\u00a0 VS-172.16.100.200-80\r\nVirtual Addr\u00a0 172.16.100.200:80\r\nNode Addr\u00a0\u00a0\u00a0\u00a0 192.168.1.31:80\r\nPool Name\u00a0\u00a0\u00a0\u00a0 POOL-172.16.100.200-80\r\nClient Addr\u00a0\u00a0 ::<\/pre>\nReason<\/strong><\/h2>\n
This occurs due to the way in which Client Addr is represented when multiple connections with the same key are processed by the same TMM.<\/p>\n
Consider the following scenario, connection 1 is\u00a0received by the F5, and processed by TMM0. A UIE persistence record is built, with the Client Addr field populated. A\u00a02nd connection is\u00a0then received (containing the same key) and\u00a0processed by TMM1.\u00a0As this is on a different TMM the UIE record from TMM0 is copied and the\u00a0Client Addr field is populated with the client address.<\/p>\n
Connection 1 (1.1.1.1) –> TMM0 –> Key=8ffa6c0012825a76b3b68d10a9c68ad3 Client Addr 1.1.1.1
\nConnection 2 (2.2.2.2) –> TMM1 –> Key=8ffa6c0012825a76b3b68d10a9c68ad3 Client Addr 2.2.2.2<\/p>\nHowever now consider the following, connection 1 is recieved by the F5, and processed by TMM0. A UIE persistence record is built, with the Client Addr field populated. A 2nd connection is then recieved (containing the same key) and processed by the same TMM (TMM0). As the connection has the same key and is on the same TMM the UIE record is not copied, instead\u00a0the Client Addr field is represented by ::<\/p>\n
Connection 1 (1.1.1.1) –> TMM0 –> Key=8ffa6c0012825a76b3b68d10a9c68ad3 Client Addr ::
\nConnection 2 (2.2.2.2) –> TMM0 –> Key=8ffa6c0012825a76b3b68d10a9c68ad3 Client Addr ::<\/p>\nWhy does this matter ?<\/strong><\/p>\n
If non-unique keys are being used this\u00a0can\u00a0lead to a situation where a large amount of connections persist to a single\u00a0host, should each client arrive on the\u00a0same TMM.\u00a0As each client performs a lookup of the single UIE persistence record the Age will be reset back to 0 seconds.<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Issue When viewing the UIE persistence records you observe that the Client Addr field is not populated. root@f5ltm(Active)(tmos)# show ltm persistence persist-records all-properties Sys::Persistent Connections universal – 172.16.100.200:80 – 192.168.1.31:80 ———————————————————– TMM\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0 Mode\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 universal Key\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 8ffa6c0012825a76b3b68d10a9c68ad3 Age (sec.)\u00a0\u00a0\u00a0 4 Virtual Name\u00a0 VS-172.16.100.200-80 Virtual Addr\u00a0 172.16.100.200:80 Node Addr\u00a0\u00a0\u00a0\u00a0 192.168.1.31:80 Pool Name\u00a0\u00a0\u00a0\u00a0 POOL-172.16.100.200-80 Client Addr\u00a0\u00a0 :: … Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[15],"tags":[],"yoast_head":"\n
UIE Persistence Record's Client Addr field is not Populated - Fir3net<\/title>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\t\n