Forum Discussion
NimbostratusClients hitting old pool servers after pool change
hi i am investigating some problem like: I have VIP and 2 pools. After pool was changed server guys can see that external IPs still hitting old pool members
was like VIP POOL1 WEB1 WEB2 was changed to VIP POOL2 WEB3 WEB4
on WEB1 and 2 still was possible see some connections first half day. What can be reason for that.
By the way there are persistence profile configured on VIP Cookie Method:HTTP cookie insert Expiration: Session Cookie
maybe someone could explain how connections moving to new pool in such environment?
thanks
Jad_Tabbara__J1Cirrostratus
Hey Andreey,
Could you share the configuration of the VS using following command :
tmsh list virtual vs_nameMaybe you have an LTM policy or an irule that is always pointing to old pool...
Also you can try using this command to view if old pool member still receives connection and from which source ip :
// replace x.x.x.x by the old server IP addrtmsh show sys connection ss-server-addr x.x.x.xRegards
Henrik_GyllkranOut of curiosity I tested on a lab environment and in my case the Persistence did not send the traffic to a server that's no longer in the Pool. This is on v13 so it might be a different behavior from your version though.
One thing that just might be a case though is if it was existing connections in the connection table, because those aren't deleted even when you delete the objects involved. In fact you can delete the VS and the BIG-IP will still forward traffic that matches those connections. In my experience HTTP connections doesn't stay open for very long but if there's data going all the time I guess it is possible.