Web Acceleration Not Caching Content
Hi,
I have 2 environments running F5s with as far as I can tell identical configurations.
Farm1 is running BIG-IP 11.5.1 Build 3.0.131 Hotfix HF3.
Farm2 is running BIG-IP 11.5.2 Build 0.0.141 Final.
Both configurations have identical web acceleration policy profiles that I would expect to do the same thing, however, caching does not appear to be working as expected on Farm2.
Farm1 F5 Response Headers(style.css)
Accept-Ranges:none
Age:10
Cache-Control:public, max-age=172800, s-maxage=14400
Connection:Keep-Alive
Content-Type:text/css
Date:Tue, 19 Jan 2016 20:15:18 GMT
ETag:W/"WAe0a9d0e2672ee330"
Expires:Thu, 01 Dec 1994 16:00:00 GMT
Last-Modified:Sat, 16 Jan 2016 01:06:10 GMT
Persistent-Auth:true
Set-Cookie:MRHSession=09d...; expires=Tue, 19 Jan 2016 20:30:18 GMT;path=/;secure
Set-Cookie:LastMRH_Session=09d...; expires=Tue, 19 Jan 2016 20:30:18 GMT;path=/;secure
Farm2 F5 Response Headers(style.css)
HTTP/1.1 200 OK
Cache-Control: public
Content-Type: text/css
Expires: Wed, 18 Jan 2017 20:21:35 GMT
Last-Modified: Wed, 13 Jan 2016 16:53:28 GMT
Persistent-Auth: true
Date: Tue, 19 Jan 2016 20:21:34 GMT
Content-Length: 3582
Set-Cookie: persistA=335937546.47873.0000; expires=Tue, 19-Jan-2016 22:21:35 GMT; path=/
Connection: Keep-Alive
Set-Cookie: MRHSession=b99...; expires=Tue, 19 Jan 2016 20:36:35 GMT;path=/;secure
Set-Cookie: LastMRH_Session=b99...; expires=Tue, 19 Jan 2016 20:36:35 GMT;path=/;secure
It seems like Farm2 F5 is not processing anything with web acceleration and the response headers behind the F5s are identical on both farms.
I've reviewed /var/log/wa/ logs and could not find anything that seemed suspicious.
Is there someway to tell why web acceleration would be bypassing content?
Thanks!
This actually turned out to be a licensing issue.
Apparently we were given the wrong license(AAM was included, but must have been the wrong VE type), but the module could still be provisioned and configured, it just wouldn't process traffic.
Crazy.