<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic inbound packet loss TCP SYNs in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/inbound-packet-loss-tcp-syns/m-p/233134#M3274</link>
    <description>&lt;P&gt;You'll be fed up of me soon!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a CSS 11800 running ap0500063 (old I know but there are political reasons making an upgrade awkward) that seems to ignore some TCP SYNs for no apparent reason.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The symptoms are that occasionally part of a website (odd that it is normally one of 2 images) fails to display.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looking at a sniffer trace (I only have one near the client, it has been reported to be seen adjacent to the CSS) where I can see traffic going backwards and forwards, but one SYN is ignored, even when it is retried. The llama debug set to:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;flow trace-ip 80.40.30.182 (client IP)&lt;/P&gt;&lt;P&gt;flow options 0x00000131&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(advice from &lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/contnetw/ps789/products_tech_note09186a0080094ebf.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/contnetw/ps789/products_tech_note09186a0080094ebf.shtml&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;shows no sign of the inbound syn.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It just seems to be syns that get ignored...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thoughts?&lt;/P&gt;</description>
    <pubDate>Tue, 10 Aug 2004 13:03:20 GMT</pubDate>
    <dc:creator>paul.matthews</dc:creator>
    <dc:date>2004-08-10T13:03:20Z</dc:date>
    <item>
      <title>inbound packet loss TCP SYNs</title>
      <link>https://community.cisco.com/t5/application-networking/inbound-packet-loss-tcp-syns/m-p/233134#M3274</link>
      <description>&lt;P&gt;You'll be fed up of me soon!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a CSS 11800 running ap0500063 (old I know but there are political reasons making an upgrade awkward) that seems to ignore some TCP SYNs for no apparent reason.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The symptoms are that occasionally part of a website (odd that it is normally one of 2 images) fails to display.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Looking at a sniffer trace (I only have one near the client, it has been reported to be seen adjacent to the CSS) where I can see traffic going backwards and forwards, but one SYN is ignored, even when it is retried. The llama debug set to:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;flow trace-ip 80.40.30.182 (client IP)&lt;/P&gt;&lt;P&gt;flow options 0x00000131&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(advice from &lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/contnetw/ps789/products_tech_note09186a0080094ebf.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/contnetw/ps789/products_tech_note09186a0080094ebf.shtml&lt;/A&gt;)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;shows no sign of the inbound syn.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It just seems to be syns that get ignored...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thoughts?&lt;/P&gt;</description>
      <pubDate>Tue, 10 Aug 2004 13:03:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/inbound-packet-loss-tcp-syns/m-p/233134#M3274</guid>
      <dc:creator>paul.matthews</dc:creator>
      <dc:date>2004-08-10T13:03:20Z</dc:date>
    </item>
    <item>
      <title>Re: inbound packet loss TCP SYNs</title>
      <link>https://community.cisco.com/t5/application-networking/inbound-packet-loss-tcp-syns/m-p/233135#M3275</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Paul,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;would be good to know what type of content rule you are  using as it makes a big difference.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;About flow trace-ip on the 11800, do you see the other syn's ? or nothing at all ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 10 Aug 2004 15:24:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/inbound-packet-loss-tcp-syns/m-p/233135#M3275</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2004-08-10T15:24:57Z</dc:date>
    </item>
    <item>
      <title>Re: inbound packet loss TCP SYNs</title>
      <link>https://community.cisco.com/t5/application-networking/inbound-packet-loss-tcp-syns/m-p/233136#M3276</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The sanitised version of the rule is below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am pretty sure I saw other SYNS, but as I was seeing other traffic on the connection, I was not specially looking for the SYNs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  content &lt;RULE name=""&gt;&lt;/RULE&gt;&lt;/P&gt;&lt;P&gt;    protocol tcp&lt;/P&gt;&lt;P&gt;    port 80&lt;/P&gt;&lt;P&gt;    url "//www.&lt;WEBSITE&gt;.info/*"&lt;/WEBSITE&gt;&lt;/P&gt;&lt;P&gt;    no persistent&lt;/P&gt;&lt;P&gt;    add service serv01_http&lt;/P&gt;&lt;P&gt;    add service serv02_http&lt;/P&gt;&lt;P&gt;    balance aca&lt;/P&gt;&lt;P&gt;    vip address 172.19.111.56&lt;/P&gt;&lt;P&gt;    active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Aug 2004 06:52:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/inbound-packet-loss-tcp-syns/m-p/233136#M3276</guid>
      <dc:creator>paul.matthews</dc:creator>
      <dc:date>2004-08-11T06:52:45Z</dc:date>
    </item>
    <item>
      <title>Re: inbound packet loss TCP SYNs</title>
      <link>https://community.cisco.com/t5/application-networking/inbound-packet-loss-tcp-syns/m-p/233137#M3277</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Paul,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this is standard config.&lt;/P&gt;&lt;P&gt;A L5 rule, so the SYN should be answered by the CSS itself and you should see it with the flow trace-ip command.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Unfortunately, there is no bug clearly matching your problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you see any error messages in the log ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All I could recommend is an upgrade to 6.10 to get the new queueing system to will solve a lot of unecessary packet drops.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Aug 2004 14:28:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/inbound-packet-loss-tcp-syns/m-p/233137#M3277</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2004-08-11T14:28:43Z</dc:date>
    </item>
    <item>
      <title>Re: inbound packet loss TCP SYNs</title>
      <link>https://community.cisco.com/t5/application-networking/inbound-packet-loss-tcp-syns/m-p/233138#M3278</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No messages in the log. I have started the political side of things to perform thr upgrade...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the help.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Aug 2004 19:20:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/inbound-packet-loss-tcp-syns/m-p/233138#M3278</guid>
      <dc:creator>paul.matthews</dc:creator>
      <dc:date>2004-08-11T19:20:51Z</dc:date>
    </item>
  </channel>
</rss>

