I'm seeing a bunch of hits for "Peer received reset from end host" on all of my WAAS devices (mixture of edge NM-502s and WAE-512s, with a core cluster of WAE-612s) when I do a "show stats tfo" in WAAS 4.0.13.
Does anyone know if this is really a problem or a normal statistic? If it's not a problem, any idea what kind of number would constitute a problem?
Attached are a couple of examples from two of my edge 512s immediately after I cleared all counters. I also noticed that the stat "No. of connections closed with error" is always very close to the other "Peer received reset from end host" counter.
Any idea if these would be related? Does Cisco have any WAAS documentation that describes all of these fields?
Any insight would be appreciated (before I open a TAC case)!
These counters simply indicate that a TCP connection was closed using a RST (as opposed to a FIN). This is normal behavior for some applications. For example, Internet Explorer closes its TCP connections using RST. I usually advise customers not to concern themselves with these counters unless they are experiencing some type of problem.
Great! Thanks for the quick response! I'll keep an eye on them in the meantime. Do you know if Cisco has published any documentation that describes all of these counters and what types of network activity can cause them?
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...