<?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: high memory of physical in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/high-memory-of-physical/m-p/169631#M30751</link>
    <description>&lt;P&gt;So you clearly can see in cpview that there is much free memory on both.&lt;/P&gt;</description>
    <pubDate>Mon, 30 Jan 2023 14:50:07 GMT</pubDate>
    <dc:creator>G_W_Albrecht</dc:creator>
    <dc:date>2023-01-30T14:50:07Z</dc:date>
    <item>
      <title>high memory of physical</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/high-memory-of-physical/m-p/167753#M30675</link>
      <description />
      <pubDate>Wed, 05 Apr 2023 08:31:28 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/high-memory-of-physical/m-p/167753#M30675</guid>
      <dc:creator>umar7</dc:creator>
      <dc:date>2023-04-05T08:31:28Z</dc:date>
    </item>
    <item>
      <title>Re: high memory of physical</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/high-memory-of-physical/m-p/167756#M30676</link>
      <description>&lt;P&gt;What is shown in cpview ?&lt;/P&gt;</description>
      <pubDate>Fri, 13 Jan 2023 11:55:46 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/high-memory-of-physical/m-p/167756#M30676</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2023-01-13T11:55:46Z</dc:date>
    </item>
    <item>
      <title>Re: high memory of physical</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/high-memory-of-physical/m-p/167764#M30677</link>
      <description>&lt;P&gt;What is solarwinds using for the SNMP OID here?&lt;/P&gt;
&lt;P&gt;Compare it with those in&amp;nbsp;&lt;SPAN&gt;sk32206 / sk90860...&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;TABLE id="System_counters_Memory_Counters_Table" border="1" width="900" cellpadding="4"&gt;
&lt;TBODY&gt;
&lt;TR&gt;
&lt;TD width="150"&gt;Required&lt;BR /&gt;Information&lt;/TD&gt;
&lt;TD width="250"&gt;Object Name,&lt;BR /&gt;Object ID&lt;/TD&gt;
&lt;TD width="100"&gt;OID&lt;BR /&gt;Format&lt;/TD&gt;
&lt;TD width="200"&gt;OID&lt;BR /&gt;Description&lt;/TD&gt;
&lt;TD width="200"&gt;Notes for&lt;BR /&gt;VSX mode&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR valign="top"&gt;
&lt;TD&gt;RAM - Real Total&lt;/TD&gt;
&lt;TD&gt;&lt;CODE&gt;.iso.org.dod.internet.private.enterprises.checkpoint.products.svn.svnPerf.svnMem64.&lt;STRONG&gt;memTotalReal64&lt;/STRONG&gt;&lt;/CODE&gt;&lt;BR /&gt;.1.3.6.1.4.1.2620.1.6.7.4.3&lt;/TD&gt;
&lt;TD&gt;String&lt;/TD&gt;
&lt;TD&gt;Total real memory in bytes.&lt;BR /&gt;Memory used by applications.&lt;/TD&gt;
&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR valign="top"&gt;
&lt;TD&gt;RAM - Real Active&lt;/TD&gt;
&lt;TD&gt;&lt;CODE&gt;.iso.org.dod.internet.private.enterprises.checkpoint.products.svn.svnPerf.svnMem64.&lt;STRONG&gt;memActiveReal64&lt;/STRONG&gt;&lt;/CODE&gt;&lt;BR /&gt;.1.3.6.1.4.1.2620.1.6.7.4.4&lt;/TD&gt;
&lt;TD&gt;
&lt;UL&gt;
&lt;LI&gt;Counter64 (R80.20 and higher)&lt;/LI&gt;
&lt;LI&gt;String (R80.10 and lower)&lt;/LI&gt;
&lt;/UL&gt;
&lt;/TD&gt;
&lt;TD&gt;Active real memory in bytes (memory used by applications that is not cached to the disk).&lt;/TD&gt;
&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR valign="top"&gt;
&lt;TD&gt;RAM - Real Free&lt;/TD&gt;
&lt;TD&gt;&lt;CODE&gt;.iso.org.dod.internet.private.enterprises.checkpoint.products.svn.svnPerf.svnMem64.&lt;STRONG&gt;memFreeReal64&lt;/STRONG&gt;&lt;/CODE&gt;&lt;BR /&gt;.1.3.6.1.4.1.2620.1.6.7.4.5&lt;/TD&gt;
&lt;TD&gt;String&lt;/TD&gt;
&lt;TD&gt;Free memory in bytes available for applications.&lt;/TD&gt;
&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR valign="top"&gt;
&lt;TD&gt;RAM - Virtual Total&lt;/TD&gt;
&lt;TD&gt;&lt;CODE&gt;.iso.org.dod.internet.private.enterprises.checkpoint.products.svn.svnPerf.svnMem64.&lt;STRONG&gt;memTotalVirtual64&lt;/STRONG&gt;&lt;/CODE&gt;&lt;BR /&gt;.1.3.6.1.4.1.2620.1.6.7.4.1&lt;/TD&gt;
&lt;TD&gt;String&lt;/TD&gt;
&lt;TD&gt;The size in bytes of the virtual-memory working segment pages.&lt;/TD&gt;
&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR valign="top"&gt;
&lt;TD&gt;RAM - Virtual Active&lt;/TD&gt;
&lt;TD&gt;&lt;CODE&gt;.iso.org.dod.internet.private.enterprises.checkpoint.products.svn.svnPerf.svnMem64.&lt;STRONG&gt;memActiveVirtual64&lt;/STRONG&gt;&lt;/CODE&gt;&lt;BR /&gt;.1.3.6.1.4.1.2620.1.6.7.4.2&lt;/TD&gt;
&lt;TD&gt;String&lt;/TD&gt;
&lt;TD&gt;The size in bytes of the virtual-memory working segment pages that have actually been touched.&lt;/TD&gt;
&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR valign="top"&gt;
&lt;TD&gt;Hmem fails&lt;/TD&gt;
&lt;TD&gt;&lt;CODE&gt;.iso.org.dod.internet.private.enterprises.checkpoint.products.fw.fwPerfStat.fwHmem.&lt;STRONG&gt;fwHmem-failed-alloc&lt;/STRONG&gt;&lt;/CODE&gt;&lt;BR /&gt;.1.3.6.1.4.1.2620.1.1.26.1.21&lt;/TD&gt;
&lt;TD&gt;Integer&lt;/TD&gt;
&lt;TD&gt;Hash memory allocation failures.&lt;/TD&gt;
&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;
&lt;/TR&gt;
&lt;TR valign="top"&gt;
&lt;TD&gt;System Kmem fails&lt;/TD&gt;
&lt;TD&gt;&lt;CODE&gt;.iso.org.dod.internet.private.enterprises.checkpoint.products.fw.fwPerfStat.fwKmem.&lt;STRONG&gt;fwKmem-failed-alloc&lt;/STRONG&gt;&lt;/CODE&gt;&lt;BR /&gt;.1.3.6.1.4.1.2620.1.1.26.2.15&lt;/TD&gt;
&lt;TD&gt;Integer&lt;/TD&gt;
&lt;TD&gt;System Kernel memory (SMEM) allocation failures.&lt;/TD&gt;
&lt;TD&gt;&amp;nbsp;&lt;/TD&gt;
&lt;/TR&gt;
&lt;/TBODY&gt;
&lt;/TABLE&gt;</description>
      <pubDate>Fri, 13 Jan 2023 13:48:46 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/high-memory-of-physical/m-p/167764#M30677</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2023-01-13T13:48:46Z</dc:date>
    </item>
    <item>
      <title>Re: high memory of physical</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/high-memory-of-physical/m-p/169386#M30678</link>
      <description>&lt;P&gt;Better contact TAC !&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2023 09:25:24 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/high-memory-of-physical/m-p/169386#M30678</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2023-01-27T09:25:24Z</dc:date>
    </item>
    <item>
      <title>Re: high memory of physical</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/high-memory-of-physical/m-p/169441#M30679</link>
      <description>&lt;P&gt;Yes this is expected behavior, the 25 GB allocated to buffering and caching (which is caching access to the hard disk) which can be reallocated at a moment's notice if required for code execution.&amp;nbsp; So that memory is available if actually needed, but is currently utilized to make the system run more efficiently.&amp;nbsp; You are 444Mbytes into swap space but weighed against 32GB of total RAM I wouldn't worry about it.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Jan 2023 20:57:17 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/high-memory-of-physical/m-p/169441#M30679</guid>
      <dc:creator>Timothy_Hall</dc:creator>
      <dc:date>2023-01-27T20:57:17Z</dc:date>
    </item>
    <item>
      <title>Re: high memory of physical</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/high-memory-of-physical/m-p/169598#M30740</link>
      <description>&lt;P&gt;hello&lt;/P&gt;</description>
      <pubDate>Wed, 05 Apr 2023 09:03:24 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/high-memory-of-physical/m-p/169598#M30740</guid>
      <dc:creator>umar7</dc:creator>
      <dc:date>2023-04-05T09:03:24Z</dc:date>
    </item>
    <item>
      <title>Re: high memory of physical</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/high-memory-of-physical/m-p/169631#M30751</link>
      <description>&lt;P&gt;So you clearly can see in cpview that there is much free memory on both.&lt;/P&gt;</description>
      <pubDate>Mon, 30 Jan 2023 14:50:07 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/high-memory-of-physical/m-p/169631#M30751</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2023-01-30T14:50:07Z</dc:date>
    </item>
    <item>
      <title>Re: high memory of physical</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/high-memory-of-physical/m-p/170722#M30918</link>
      <description>&lt;P&gt;So what did you find out using the supplied information ?&lt;/P&gt;</description>
      <pubDate>Wed, 08 Feb 2023 13:24:43 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/high-memory-of-physical/m-p/170722#M30918</guid>
      <dc:creator>G_W_Albrecht</dc:creator>
      <dc:date>2023-02-08T13:24:43Z</dc:date>
    </item>
  </channel>
</rss>

