PT No Peer means that the WAE doesn't see TCP autodiscovery options coming from another WAE at the other end of the link.
Either interception was changed or the Core WAEs are not actively acting on or accelerating traffic they are intercepting. If you are using WCCP, do the WAEs show up as clients to the routers (sh ip wccp) and do the WAEs show that traffic is being forwarded (sh wccp router/gre). Do you see TFO Overload messages in the CM?
Hope that gives you some places to start looking at.
AS I said for some reason the Core WAE had stopped accelerating, nothing in the graphs, and when I did a "sh wccp flows tcp" command and everything was 0, so reloaded the core WAE and it started working. My question was how do I flush the connection statistics of all the "PT no peer" entries when I had the problem? I still see them 24 hours after I corrected the problem
The connections may be long lived CIFS connections and have not re-established since you restarted the cores. Try having the users/adminstrators reset the connections (reload the workstations or reset via server manager) and see if they come back as optimized. If the connection is established before WAAS starts optimizing, then it will pass the connection through until the next 3 way handshake.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
==================== VIC FNIC driver does not support Virtual Volumes (
second level LUN ID ) An enhancement request has been created to track
this feature - CSCux64473 UPDATE - 12-14-2016 We made some traction on
the enhancement request - The Fix is in t...