<?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 VSX Performance monitoring (indicators) in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Performance-monitoring-indicators/m-p/50343#M9722</link>
    <description>&lt;P&gt;I'm curious to know what are you looking at to tell if your R80.20 VSX gateway performance are ok or not?&lt;/P&gt;&lt;P&gt;What can be monitored to see if performance are fine or not?&lt;/P&gt;&lt;P&gt;How can you tell if you are oversized or undersized?&lt;/P&gt;&lt;P&gt;How do you know if it is time to upgrade to bigger server/model?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
    <pubDate>Tue, 09 Apr 2019 19:52:00 GMT</pubDate>
    <dc:creator>Louis_Poulin</dc:creator>
    <dc:date>2019-04-09T19:52:00Z</dc:date>
    <item>
      <title>VSX Performance monitoring (indicators)</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Performance-monitoring-indicators/m-p/50343#M9722</link>
      <description>&lt;P&gt;I'm curious to know what are you looking at to tell if your R80.20 VSX gateway performance are ok or not?&lt;/P&gt;&lt;P&gt;What can be monitored to see if performance are fine or not?&lt;/P&gt;&lt;P&gt;How can you tell if you are oversized or undersized?&lt;/P&gt;&lt;P&gt;How do you know if it is time to upgrade to bigger server/model?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Tue, 09 Apr 2019 19:52:00 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Performance-monitoring-indicators/m-p/50343#M9722</guid>
      <dc:creator>Louis_Poulin</dc:creator>
      <dc:date>2019-04-09T19:52:00Z</dc:date>
    </item>
    <item>
      <title>Re: VSX Performance monitoring (indicators)</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Performance-monitoring-indicators/m-p/50378#M9723</link>
      <description>&lt;P&gt;First of all look at these documents:&lt;BR /&gt;&lt;A href="https://www.ankenbrand24.de/index.php/articles/articles-check-point/" target="_blank"&gt;https://www.ankenbrand24.de/index.php/articles/articles-check-point/&lt;/A&gt;&lt;BR /&gt;What I use to get a general idea of how a box is doing, my first tool si cpview, it has a lot of different views that will tell you all kind of things like:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;CPU load per core&lt;/LI&gt;
&lt;LI&gt;CPU load per VS&lt;/LI&gt;
&lt;LI&gt;Network load&lt;/LI&gt;
&lt;LI&gt;In pre R80.20: the SecureXL Path load&lt;/LI&gt;
&lt;LI&gt;Memory usage&lt;/LI&gt;
&lt;LI&gt;Software Blades&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;etc&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;One of the nice things of VSX is that, if you run VSLS, you can add members and share the load of VS's over the different boxes. This will however not help if you have 1 VS eating up a complete box.&lt;/P&gt;</description>
      <pubDate>Wed, 10 Apr 2019 05:28:27 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/VSX-Performance-monitoring-indicators/m-p/50378#M9723</guid>
      <dc:creator>Maarten_Sjouw</dc:creator>
      <dc:date>2019-04-10T05:28:27Z</dc:date>
    </item>
  </channel>
</rss>

