<?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: FTDv Jumbo Frames in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ftdv-jumbo-frames/m-p/4800732#M1098965</link>
    <description>&lt;P&gt;Jumbo support is implemented in the underlying Lina (ASA) code. One of my colleagues faced with a similar issue on ASAv some time ago and found that ASAv doesn't allocate memory blocks during reboot properly on all ASAv variants below ASAv100. For to-the-box traffic (and few other special cases) check "show blocks". If you see "1" in the MAX column for 9344 blocks, the allocation is incorrect and to-the-box ping and OSPF may not work. FAILED counter will increment. For through-the-box traffic also check "show blocks interface". Also check "show jumbo-frame reservation".&lt;/P&gt;&lt;P&gt;Then another issue was found which affects all ASAv including ASAv100: large frames were dropped by ESXi due to MTU Check Enforcement: "In ESXi version 6.7 update 2 and later, the default behavior of the platform is enforced to perform a MTU check on the receiving path and will not allow packets that are larger than the vNIC's MTU size". Not sure if this is relevant for your case though.&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 24 Mar 2023 09:59:42 GMT</pubDate>
    <dc:creator>tvotna</dc:creator>
    <dc:date>2023-03-24T09:59:42Z</dc:date>
    <item>
      <title>FTDv Jumbo Frames</title>
      <link>https://community.cisco.com/t5/network-security/ftdv-jumbo-frames/m-p/4321605#M1079999</link>
      <description>&lt;P&gt;I'm messing around in lab and trying to get the FTDv to do jumbo frames.&amp;nbsp; According to the documentation its pretty simple but I've not had any luck.&amp;nbsp; I set the MTU on the Interface to 9000 and FMC said it was enabling jumbo frames and to reboot.&amp;nbsp; I deployed, rebooted.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ping -l 11484 -f works but anything larger than 1484 fails.&amp;nbsp; Any other hosts on this same vnic/vswitch like my 9800v WLC, windows boxes, etc. all work fine up to 8xxx.&amp;nbsp; Any idea's? Thoughts?&amp;nbsp; I can't find anything to say this doesn't work with the FTDv.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 11 Apr 2021 16:43:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftdv-jumbo-frames/m-p/4321605#M1079999</guid>
      <dc:creator>stamperbrian</dc:creator>
      <dc:date>2021-04-11T16:43:13Z</dc:date>
    </item>
    <item>
      <title>Re: FTDv Jumbo Frames</title>
      <link>https://community.cisco.com/t5/network-security/ftdv-jumbo-frames/m-p/4799954#M1098937</link>
      <description>&lt;P&gt;Have the same issue.. Any reply or suggestions on how to verify would be helpfull..&lt;/P&gt;</description>
      <pubDate>Thu, 23 Mar 2023 12:54:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftdv-jumbo-frames/m-p/4799954#M1098937</guid>
      <dc:creator>a.sizov99</dc:creator>
      <dc:date>2023-03-23T12:54:43Z</dc:date>
    </item>
    <item>
      <title>Re: FTDv Jumbo Frames</title>
      <link>https://community.cisco.com/t5/network-security/ftdv-jumbo-frames/m-p/4800732#M1098965</link>
      <description>&lt;P&gt;Jumbo support is implemented in the underlying Lina (ASA) code. One of my colleagues faced with a similar issue on ASAv some time ago and found that ASAv doesn't allocate memory blocks during reboot properly on all ASAv variants below ASAv100. For to-the-box traffic (and few other special cases) check "show blocks". If you see "1" in the MAX column for 9344 blocks, the allocation is incorrect and to-the-box ping and OSPF may not work. FAILED counter will increment. For through-the-box traffic also check "show blocks interface". Also check "show jumbo-frame reservation".&lt;/P&gt;&lt;P&gt;Then another issue was found which affects all ASAv including ASAv100: large frames were dropped by ESXi due to MTU Check Enforcement: "In ESXi version 6.7 update 2 and later, the default behavior of the platform is enforced to perform a MTU check on the receiving path and will not allow packets that are larger than the vNIC's MTU size". Not sure if this is relevant for your case though.&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Mar 2023 09:59:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ftdv-jumbo-frames/m-p/4800732#M1098965</guid>
      <dc:creator>tvotna</dc:creator>
      <dc:date>2023-03-24T09:59:42Z</dc:date>
    </item>
  </channel>
</rss>

