Universal Persistence Issue

Thanks hoolio. Will try to do that.

 

 

Right now the flow of request is configured in such a way that client hits the eBigip (which has source addr persistence) first on vip port 443 which contains pool of vips (on port 80) of internal bigips.

 

 

Now the vips (on port 80) on internal bigips (i.e. bigip1 & bigip2) have our iRules, pools and other health monitors. There the request is directed to appropriate pools i.e. channel, presence and nginx.

 

 

It is suspected the request is getting load balanced from external bigips to the internal bigips due to this separate persistence record is getting created for the same orgId.

 

 

Oneconnect is enabled on both the layers of bigips.

 

 

What would you suggest? Could this be a issue?

 

 

Thanks.

 

Narendra