transaction logging on waas 4.1.1c no_peer

Unanswered Question
Dec 3rd, 2008

started doing transaction logging

where do i find the decode, I don't understand no_peer when both devices are accessible

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
dstolt Thu, 12/04/2008 - 08:09

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.

Hope that helps,

Dan

Dan

Richard Bradfield Sat, 12/06/2008 - 15:44

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?

Actions

This Discussion