Forum Discussion

Glenn_Nummy_134's avatar
Glenn_Nummy_134
Icon for Nimbostratus rankNimbostratus
Jan 06, 2014

Unexpected UIE entries in persistence table ; Client Addr = Node Addr

I have configured a number of VIPs on our BipIP v 11.4.0 using UIE cookie persistence with an iRule that checks cookie value for a number of web applications.

 

Testing persistence seems to work fine but when I check the persistence table I see a number of records where the source address is matching one of the node addresses and not the source address of the client. The value matches the cookie value in the browser of the real client. Is this expected behavior or is something else going on here? there are no proxy servers in this mix.

 

show ltm persistence persist-records virtual /Common/WEBMAIL-80 all-properties

 

TMM 0 Mode universal Value d89de239a4c8fc756594bab767dd3b3d4d7449 Age (sec.) 120 Virtual Name /Common/WEBMAIL-80 Virtual Addr 192.168.8.200:80 Node Addr 192.168.8.201:80 Pool Name /Common/pool-WEBMAIL-80 Client Addr 192.168.8.201 Local entry

 

application delivery
devops
iRules
TMSH

2 Replies

Sort By
  • nitass's avatar
    nitass
    Icon for Employee rankEmployee
    Jan 06, 2014

    Testing persistence seems to work fine but when I check the persistence table I see a number of records where the source address is matching one of the node addresses and not the source address of the client.

     

    is it possible that server (node) has accessed the virtual server?

     

  • Glenn_Nummy_134's avatar
    Glenn_Nummy_134
    Icon for Nimbostratus rankNimbostratus
    Jan 06, 2014

    Hi, thanks for your quick reply. I tested again while checking the connection table: 'show sys connection cs-server-addr 192.168.8.200' And it shows connections only from the client as expected, so I cant see any reason for the persistence record to show source address to be the node address.

     

    Also I tested the same rule using Source Address persistence instead of UIE and it shows the correct client address in the persistence records.

     

    We need to continue use cookie persistence as the clients will soon be behind a secure gateway so their real source address will not be visible from the BigIP.