<?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 Re: Tracing on a CCS 11150 in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/tracing-on-a-ccs-11150/m-p/155866#M1897</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the tips Gilles / Brgds&lt;/P&gt;&lt;P&gt;JC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 15 Jan 2003 15:36:32 GMT</pubDate>
    <dc:creator>jcasqueiro</dc:creator>
    <dc:date>2003-01-15T15:36:32Z</dc:date>
    <item>
      <title>Tracing on a CCS 11150</title>
      <link>https://community.cisco.com/t5/application-networking/tracing-on-a-ccs-11150/m-p/155864#M1895</link>
      <description>&lt;P&gt;I there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am getting lots of session disconnects in W2K servers behind a CCS 11150 from a couple of remote stations. I suspect the cause to be line errors of some kind and therefore I would like to trace the flows and see if packets are being dropped/arrive in error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have seen the doc "packet tracing on the CCS 11000" but I am not sure if with "flow trace-ip" I will be able to do this or if there is othe better way to do it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks/Brgds&lt;/P&gt;&lt;P&gt;jc&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jan 2003 11:52:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/tracing-on-a-ccs-11150/m-p/155864#M1895</guid>
      <dc:creator>jcasqueiro</dc:creator>
      <dc:date>2003-01-14T11:52:15Z</dc:date>
    </item>
    <item>
      <title>Re: Tracing on a CCS 11150</title>
      <link>https://community.cisco.com/t5/application-networking/tracing-on-a-ccs-11150/m-p/155865#M1896</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;jc,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;with flow trace-ip, you can see the TCP or UDP packets coming and going out the CSS. &lt;/P&gt;&lt;P&gt;Also, this command does not display all the packets.&lt;/P&gt;&lt;P&gt;We only see the ones that are process-switched.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A better solution would be to use a sniffer trace in front of the CSS and in the backend side.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can also check the 'sho ether-error' commands to see if any problem is &lt;/P&gt;&lt;P&gt;detected by the CSS.&lt;/P&gt;&lt;P&gt;If there is other switches, like Cisco catalyst, use 'sho interface' or 'sho port&lt;/P&gt;&lt;P&gt; to check for CRC errors.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding your problem, if you have a lot of connections and some of them stays idle for 15 seconds, the CSS might drop them to free resources.&lt;/P&gt;&lt;P&gt;What you usually see in this case is a RESET being sent by the CSS to the client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One solution to this problem is the flow port timeout command to increase the default 15 seconds timer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In conclusion, I would suggest to capture a sniffer trace in front of the CSS and see if you have RST.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this will help.&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, 15 Jan 2003 13:14:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/tracing-on-a-ccs-11150/m-p/155865#M1896</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2003-01-15T13:14:15Z</dc:date>
    </item>
    <item>
      <title>Re: Tracing on a CCS 11150</title>
      <link>https://community.cisco.com/t5/application-networking/tracing-on-a-ccs-11150/m-p/155866#M1897</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for the tips Gilles / Brgds&lt;/P&gt;&lt;P&gt;JC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 15 Jan 2003 15:36:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/tracing-on-a-ccs-11150/m-p/155866#M1897</guid>
      <dc:creator>jcasqueiro</dc:creator>
      <dc:date>2003-01-15T15:36:32Z</dc:date>
    </item>
    <item>
      <title>Re: Tracing on a CCS 11150</title>
      <link>https://community.cisco.com/t5/application-networking/tracing-on-a-ccs-11150/m-p/155867#M1898</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Gilles, just one more question.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I couldn't find any "flow port timeout" command in Cisco CCS documentation or in the Cisco site (the only thing nearer is "flow port-reset"). Is this an undocumented command ??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks/Brgds&lt;/P&gt;&lt;P&gt;JoaoC&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Jan 2003 17:04:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/tracing-on-a-ccs-11150/m-p/155867#M1898</guid>
      <dc:creator>jcasqueiro</dc:creator>
      <dc:date>2003-01-16T17:04:56Z</dc:date>
    </item>
    <item>
      <title>Re: Tracing on a CCS 11150</title>
      <link>https://community.cisco.com/t5/application-networking/tracing-on-a-ccs-11150/m-p/155868#M1899</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;should be documented somewhere.&lt;/P&gt;&lt;P&gt;It is a new command however.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;css(config)# flow port1 ?&lt;/P&gt;&lt;P&gt;  &lt;INTEGER&gt;           Integer value(Range: 0-65535)&lt;/INTEGER&gt;&lt;/P&gt;&lt;P&gt;css(config)# flow port1 80 ?&lt;/P&gt;&lt;P&gt;  timeout             Timeout value in seconds&lt;/P&gt;&lt;P&gt;css(config)# flow port1 80 timeout ?&lt;/P&gt;&lt;P&gt;  &lt;INTEGER&gt;           Integer value(Range: 0-600)&lt;/INTEGER&gt;&lt;/P&gt;&lt;P&gt;css(config)# flow port1 80 timeout &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jan 2003 12:17:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/tracing-on-a-ccs-11150/m-p/155868#M1899</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2003-01-17T12:17:07Z</dc:date>
    </item>
    <item>
      <title>Re: Tracing on a CCS 11150</title>
      <link>https://community.cisco.com/t5/application-networking/tracing-on-a-ccs-11150/m-p/155869#M1900</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Gilles once again / Brgds&lt;/P&gt;&lt;P&gt;Joao&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Jan 2003 18:05:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/tracing-on-a-ccs-11150/m-p/155869#M1900</guid>
      <dc:creator>jcasqueiro</dc:creator>
      <dc:date>2003-01-17T18:05:43Z</dc:date>
    </item>
  </channel>
</rss>

