Forum Discussion
Dev_56330
Cirrus
CirrusSharePoint and WebAcceleration
I have recently configured a SharePoint application service using the latest SharePoint iApp (running Big-IP 11.4 HF 3). The default configuration for Web Acceleration creates a profile using optimized-acceleration. My understanding of the optimized-acceleration profile is that it uses LTM to perform all accelerated functions. Therefore I have selected the webacceleration-wam-enabled profile for this application. However, when accessing the SharePoint portal and viewing the Big-IP Dashboard, I see no optimized web throughput, web optimized transactions, web cache effectiveness or web image optimization. I do however see lots of OWS and WAM errors. I have looked in the wamd.log, pvac.log and others in the wa/ directory though I see none of these errors. I have also validated the wamd service is running using bigstart status wamd. I am also experiencing the same results when modifying the application to use the recommended optimized-acceleration profile. Any information the group can provide is greatly appreciated.
The WAM application stats are really the only thing to look at other than the header. It looks like some of the responses are being cached.
The X-WA-Info header should show you where the content was served from and what node of the acceleration policy it matched. There are explananations on page 77 of this guide:
https://support.f5.com/content/kb/en-us/products/wa/manuals/product/wa_implementations_11_0_0/_jcr_content/pdfAttach/download/file.res/wa_implementations_11_%20%20%20%20%20%20%20%20%20%20%200_0.pdf
If you open the acceleration policy in BIG-IP GUI, and hover over the individual leaf names in the policy tree, it will display a 5 digit number. That number corresponds to the node ID in the X-WA-Info header.
Hi Lyonsson, first off, which version of the iApp template are you using? The most recent is f5.microsoft_sharepoint_2010_2013.v1.0.0.tmpl.
Next, when you say you are selecting the webacceleration-wam-enabled profile, you mean you are selecting "Yes, use BIG-IP AAM" in response to the "Use the BIG-IP Application Acceleration Manager?" question, then choosing that acceleration profile in response to the "Which Web Acceleration profile do you want to use for caching?" question, correct?
Dev_56330I am using f5.microsoft_sharepoint_2013.v1.1.Orc1. And yes you are correct, I select "Yes, use BIG-IP-AAM (recommended)" and then selecting webacceleration-wam-enabled for the question "Which Web Acceleration profile do you want to use for caching?".- Did you previously create an AAM web application and associate the webacceleration-wam-enabled profile with it before running the iApp? In this case we recommend selecting the "Create a profile based on optimized-acceleration" option, as it will create all the necessary configuration for proper web acceleration.
- Dev_56330Mike, I have reverted to the "Recommended" settings and still see more errors than anything in the web acceleration dashboard. I see some entries in the web cache effectiveness and less entries in the web optimized transactions while nothing in optimized web throughput or web image optimization. How can I troubleshoot the OWS and WAM errors?
The WAM application stats are really the only thing to look at other than the header. It looks like some of the responses are being cached.
The X-WA-Info header should show you where the content was served from and what node of the acceleration policy it matched. There are explananations on page 77 of this guide:
https://support.f5.com/content/kb/en-us/products/wa/manuals/product/wa_implementations_11_0_0/_jcr_content/pdfAttach/download/file.res/wa_implementations_11_%20%20%20%20%20%20%20%20%20%20%200_0.pdf
If you open the acceleration policy in BIG-IP GUI, and hover over the individual leaf names in the policy tree, it will display a 5 digit number. That number corresponds to the node ID in the X-WA-Info header.
- Dev_56330Well it all makes sense now. All of the responses I get are S10206 which are "Response was served from the origin web server, because the content cannot be cached."