03-30-2012 04:55 PM
Hi guys, I'm having a lot of Total Requests for UUID not in Policy Engine Map.
Is there any to find what UUIDs the WAAS are missing ??
Here the output
show statistics accelerator epm
EPM:
Global Statistics
-----------------
Time Accelerator was started: Sun Mar 4 10:04:31 2012
Time Statistics were Last Reset/Cleared: Sun Mar 4 10:04:31 2012
Total Handled Connections: 180735
Total Optimized Connections: 180734
Total Connections Handed-off with Compression Policies Unchanged: 0
Total Dropped Connections: 1
Current Active Connections: 1
Current Pending Connections: 0
Maximum Active Connections: 71
Total Requests: 174891
Total Requests Successfuly Parsed: 174891
Total Request Errors: 0
Total Responses: 174402
Total Responses Successfully Parsed: 174763
Total Service-unavailable Responses: 1809
Total Requests for UUID not in Policy Engine Map: 27501
Total Response Errors: 0
Thanks in Advanced
My Best Regards,
Andre Lomonaco
Solved! Go to Solution.
04-11-2012 05:18 AM
Hello Andre,
Probably replies comes a little bit late, but here is some explanation.
This counter does not neccessarily mean that there is some problem with WAAS/EPM engine - usually if this counter is incrementing this indicates that there is some [custom] application in the network which is using non-standard (custom) MS-RPC UUID which WAAS does not know.
We generally use EPM on WAAS to properly accelerate MAPI (Exchange) connections - so, in this MS-RPC Endpoint Mapper flow (TCP/135) we need to "catch" TCP ports which will be later used for MAPI connections so we could accelerate them.
The only method to catch full information about those non-standard-UUID streams (client/server IP, etc) is to enable debugging for EPM accelerator engine on WAAS. Again, this should be done if there are any other visible symptoms of MAPI/EPM malfunction - this counter alone does not neccessarily indicate this.
HTH,
Amir
04-11-2012 05:18 AM
Hello Andre,
Probably replies comes a little bit late, but here is some explanation.
This counter does not neccessarily mean that there is some problem with WAAS/EPM engine - usually if this counter is incrementing this indicates that there is some [custom] application in the network which is using non-standard (custom) MS-RPC UUID which WAAS does not know.
We generally use EPM on WAAS to properly accelerate MAPI (Exchange) connections - so, in this MS-RPC Endpoint Mapper flow (TCP/135) we need to "catch" TCP ports which will be later used for MAPI connections so we could accelerate them.
The only method to catch full information about those non-standard-UUID streams (client/server IP, etc) is to enable debugging for EPM accelerator engine on WAAS. Again, this should be done if there are any other visible symptoms of MAPI/EPM malfunction - this counter alone does not neccessarily indicate this.
HTH,
Amir
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide