moving M$ SharePoint Portal Server 2003 from BIG-IP v4.x to v9.x

F5 Field System Engineer Andrew Braverman said, it might be a bug in BIG-IP 9.4.5 Build 1049.10 Final and showed a simple workaround.

 

 

I’m still reading BIG-IP 9.X documentation, so my understanding may not be 100% correct.

 

If you see a mistake in my explanation, feel free to correct me. :-)

 

 

Basically, once a HTTP Profile is assigned to a virtual server, default OneConnect Profile is assigned to the same virtual server too. It is there, even if you see it set to None in GUI.

 

 

The (partial?) workaround will be to create custom OneConnect Profile with Source Mask 255.255.255.255.

 

This way a connection from one IP will never be shared/reused to serve requests from another IP.

 

 

Obviously, you might get unexpected results if you have two or more people coming from same IP (because of NAT) using different credentials.

 

Namely, one person request might be server with another person credentials.

 

I guess it would be quite difficult to troubleshoot... :-(