<?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 Large sequence numbers on FWSM in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820777#M491594</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thankk you so much for all your help and explaining everything have a great day. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 09 Dec 2011 18:51:34 GMT</pubDate>
    <dc:creator>ALIAOF_</dc:creator>
    <dc:date>2011-12-09T18:51:34Z</dc:date>
    <item>
      <title>Large sequence numbers on FWSM</title>
      <link>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820767#M491579</link>
      <description>&lt;P&gt;We recently installed a 6509 with FWSM and noticing pretty large sequence numbers like this:&lt;/P&gt;&lt;P&gt;" %FWSM-6-302016: Teardown UDP connection 144551535502653717"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is that normal?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:00:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820767#M491579</guid>
      <dc:creator>ALIAOF_</dc:creator>
      <dc:date>2019-03-11T22:00:02Z</dc:date>
    </item>
    <item>
      <title>Large sequence numbers on FWSM</title>
      <link>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820768#M491580</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Mohammad,&lt;/P&gt;&lt;P&gt;That may not be the seq. nos used by the end hosts in the connection. It is just a connection ID that the FWSM uses to identify that particular UDP connection. It is sequentially assigned. It is an 8 byte integer made out of xlate ID and sequence counter (4 bytes each).&amp;nbsp; How long has the unit been up? Did you all increase the xlate timeout from the default 3 hours? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Kureli&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Dec 2011 21:33:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820768#M491580</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2011-12-08T21:33:59Z</dc:date>
    </item>
    <item>
      <title>Large sequence numbers on FWSM</title>
      <link>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820769#M491582</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for the reply sorry about the wording yes it is the connection ID not the sequence number I said it wrong.&amp;nbsp; Xlate is still default of 3 hours and unit has been up since september 2011.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the connection ID's that long are normal on FWSM?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Dec 2011 21:51:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820769#M491582</guid>
      <dc:creator>ALIAOF_</dc:creator>
      <dc:date>2011-12-08T21:51:47Z</dc:date>
    </item>
    <item>
      <title>Large sequence numbers on FWSM</title>
      <link>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820770#M491584</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes it is normal. Although this one is a a lot longer than the ones that I see usually &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Kureli&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Dec 2011 22:02:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820770#M491584</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2011-12-08T22:02:16Z</dc:date>
    </item>
    <item>
      <title>Large sequence numbers on FWSM</title>
      <link>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820771#M491586</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you again so should this be a concern?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Dec 2011 22:11:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820771#M491586</guid>
      <dc:creator>ALIAOF_</dc:creator>
      <dc:date>2011-12-08T22:11:30Z</dc:date>
    </item>
    <item>
      <title>Large sequence numbers on FWSM</title>
      <link>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820772#M491588</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No. Don't worry about it. Get me the &lt;/P&gt;&lt;P&gt;sh xlate count&lt;/P&gt;&lt;P&gt;sh conn count&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;output from the FWSM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Kureli&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Dec 2011 22:16:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820772#M491588</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2011-12-08T22:16:13Z</dc:date>
    </item>
    <item>
      <title>Large sequence numbers on FWSM</title>
      <link>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820773#M491590</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;# show xlate count&lt;/P&gt;&lt;P&gt;355 in use, 1310 most used&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;# show conn count&lt;/P&gt;&lt;P&gt;215 in use, 365939 most used&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you again here is the output.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Dec 2011 22:43:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820773#M491590</guid>
      <dc:creator>ALIAOF_</dc:creator>
      <dc:date>2011-12-08T22:43:59Z</dc:date>
    </item>
    <item>
      <title>Large sequence numbers on FWSM</title>
      <link>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820774#M491591</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Interesting. So at some point the blade has seen 365939 connections when at present there are only 215. &lt;/P&gt;&lt;P&gt;So, that explains the very high sequential connection ID increase. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Kureli&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Dec 2011 16:24:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820774#M491591</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2011-12-09T16:24:55Z</dc:date>
    </item>
    <item>
      <title>Large sequence numbers on FWSM</title>
      <link>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820775#M491592</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ok so once the xlate times out shouldn't the connection ID's get smaller ?&amp;nbsp; or will the device reboot can only accomplish that?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Dec 2011 18:00:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820775#M491592</guid>
      <dc:creator>ALIAOF_</dc:creator>
      <dc:date>2011-12-09T18:00:08Z</dc:date>
    </item>
    <item>
      <title>Re: Large sequence numbers on FWSM</title>
      <link>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820776#M491593</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN&gt;Yes. Either a reload or after its hits the maximum decimal integer made up of these 8 bytes(64 bits), I believe 20 digits is&lt;/SPAN&gt;&lt;SPAN&gt; hit it will reset back to the smaller number.&lt;/SPAN&gt; So according to all 1s 64 digits the max decimal number is &lt;/P&gt;&lt;P&gt;18446744073709551615 (20 digits). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I used this site to convert binary to decimal: &lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.exploringbinary.com/binary-converter/"&gt;http://www.exploringbinary.com/binary-converter/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Kureli&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Dec 2011 18:44:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820776#M491593</guid>
      <dc:creator>Kureli Sankar</dc:creator>
      <dc:date>2011-12-09T18:44:52Z</dc:date>
    </item>
    <item>
      <title>Large sequence numbers on FWSM</title>
      <link>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820777#M491594</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thankk you so much for all your help and explaining everything have a great day. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Dec 2011 18:51:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/large-sequence-numbers-on-fwsm/m-p/1820777#M491594</guid>
      <dc:creator>ALIAOF_</dc:creator>
      <dc:date>2011-12-09T18:51:34Z</dc:date>
    </item>
  </channel>
</rss>

