Specifying node kills cookie persistence

I don't think that using the node command would assume any pool info as the node command could be used to specify an arbitrary destination IP:port.

I tried testing this on 9.4.8 and see what you're describing. When testing with a cookie insert persist profile, using the pool or node command stops LTM from sending a persistence cookie. I'm not sure why this is the case.

Does anyone else have any ideas on this?

Here is a sample iRule which I tried with/without manually calling 'persist cookie insert...' in HTTP_REQUEST and/or HTTP_RESPONSE.

 
 when HTTP_REQUEST { 
  
    if {[HTTP::uri] starts_with "/node1"}{ 
       log local0. "selecting pool test_www_http_pool member 10.41.0.22 80" 
       pool test_www_http_pool member 10.41.0.22 80 
       persist cookie insert persist_cookie 
    } 
 } 
 when LB_SELECTED { 
    log local0. "[IP::client_addr]:[TCP::client_port]: Pool info: [LB::server]" 
 } 
 when SERVER_CONNECTED { 
    log local0. "[IP::client_addr]:[TCP::client_port]: Server info: [IP::server_addr]:[TCP::server_port]" 
 } 
 when HTTP_RESPONSE { 
  
    foreach a_cookie [HTTP::cookie names] { 
       log local0. "$a_cookie: [HTTP::cookie value $a_cookie]" 
    } 
 } 
 

pool member specified and no persist cookie set in the response

Jan 12 18:40:15 : selecting pool test_www_http_pool member 10.41.0.21 80

Jan 12 18:40:15 : 172.31.42.3:2296: Pool info: test_www_http_pool 10.41.0.21 80

Jan 12 18:40:15 : 172.31.42.3:2296: Server info: 10.41.0.21:80

pool member not specified and a persist cookie set in the response

Jan 12 18:40:31 : 172.31.42.3:2297: Pool info: test_www_http_pool 10.41.0.21 80

Jan 12 18:40:31 : 172.31.42.3:2297: Server info: 10.41.0.21:80

Jan 12 18:40:31 : persist_cookie: 352332042.20480.0000

Thanks,

Aaron