no_peer indicates that the TCP Autodiscovery does not detect another WAE at the other end during the syn/syn-ack/ack handshake.
Look for asynchronise routes that are not being intercepted or other back door routes that traffic might be taking. The same WAE needs to see both sides of the TCP connection. It could be something as simple as a typo in a wccp redirect-list acl or missing wccp redirect on an interface.
Dan, thanks for your input, most of the No_peer entries were from IP phones, whose vlans were not included in the wccp redirect
But I do have one remote WAE that seems to stop working after a few days, A lot of no_peer entries in the log, and when i telnet into the WAE and do a "sh wccp flow tcp" all the entries are zero. Reloading the WAE seems to fix this problem and it starts working for a few days ..any ideas what I need to look for to fix this problem?
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...