<?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: regarding for VSXs in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/regarding-for-VSXs/m-p/264426#M51963</link>
    <description>&lt;P&gt;With VSX, a given VLAN on a given physical interface can only go to one VS. That is, you can't have six VSs all sharing one physical interface to a core transit VLAN. This is where you need a virtual switch. If your six VSs will all use different physical interfaces, or different VLANs on the same physical interfaces, you don't need a switch.&lt;/P&gt;
&lt;P&gt;One thing the VSX documentation and introductions don't really cover: use bonds for all of your interfaces. Don't let VSX be aware of any physical interface which isn't in a bond. Stick the physical interface in a bond, then tell VSX to use the bond instead. This helps a &lt;EM&gt;&lt;STRONG&gt;LOT&lt;/STRONG&gt;&lt;/EM&gt; when you eventually want to replace the hardware. Bonds can have a single member, and non-LACP bonds with only one member don't need any special support on the switch side.&lt;/P&gt;</description>
    <pubDate>Thu, 04 Dec 2025 20:58:32 GMT</pubDate>
    <dc:creator>Bob_Zimmerman</dc:creator>
    <dc:date>2025-12-04T20:58:32Z</dc:date>
    <item>
      <title>regarding for VSXs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/regarding-for-VSXs/m-p/264339#M51937</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;Good Afternoon,&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Please help me regarding. i want to create a 6 VSX in checkpoint. i read most if thing but i cant understand how to create and is that compulsory if i create multiple VSX the we must create a Vertual router or verttual switch.&lt;BR /&gt;what command run on gateway for enable the VSX service.&lt;BR /&gt;and what must my management ip and what must my external Ip and internal IP.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;and i also using a one ISP so how to connectivity and configuration done at the point when i create a VSXs.&lt;/P&gt;&lt;P&gt;Thanks, and Regards&lt;/P&gt;&lt;P&gt;Vishal Kumar&lt;/P&gt;</description>
      <pubDate>Thu, 04 Dec 2025 07:28:03 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/regarding-for-VSXs/m-p/264339#M51937</guid>
      <dc:creator>Vishal8002</dc:creator>
      <dc:date>2025-12-04T07:28:03Z</dc:date>
    </item>
    <item>
      <title>Re: regarding for VSXs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/regarding-for-VSXs/m-p/264348#M51941</link>
      <description>&lt;P&gt;Vishal,&lt;BR /&gt;&lt;BR /&gt;When creating a VSX setup, you have two options.&lt;BR /&gt;&lt;BR /&gt;Legacy VSX (R82 and below)&lt;BR /&gt;VSXNext (R82)&lt;BR /&gt;&lt;BR /&gt;You have to investigate which option suits your requirements.&lt;BR /&gt;&lt;BR /&gt;Best is to read all VSX documentation available on the Check Point website.&lt;BR /&gt;&lt;BR /&gt;Martijn&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Dec 2025 10:29:51 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/regarding-for-VSXs/m-p/264348#M51941</guid>
      <dc:creator>Martijn</dc:creator>
      <dc:date>2025-12-04T10:29:51Z</dc:date>
    </item>
    <item>
      <title>Re: regarding for VSXs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/regarding-for-VSXs/m-p/264349#M51942</link>
      <description>&lt;P&gt;In your case, I would recommend attending the CCVS training, as it is really valuable for VSX beginners.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Dec 2025 10:46:14 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/regarding-for-VSXs/m-p/264349#M51942</guid>
      <dc:creator>Vincent_Bacher</dc:creator>
      <dc:date>2025-12-04T10:46:14Z</dc:date>
    </item>
    <item>
      <title>Re: regarding for VSXs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/regarding-for-VSXs/m-p/264351#M51943</link>
      <description>&lt;P&gt;This YouTube playlist may help you:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://youtube.com/playlist?list=PL4Jm1LJEII4ZiVFkjtB1zMyOzn0LUVP21&amp;amp;si=00kTs2AWaENP5slo" target="_blank"&gt;https://youtube.com/playlist?list=PL4Jm1LJEII4ZiVFkjtB1zMyOzn0LUVP21&amp;amp;si=00kTs2AWaENP5slo&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 04 Dec 2025 10:53:19 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/regarding-for-VSXs/m-p/264351#M51943</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2025-12-04T10:53:19Z</dc:date>
    </item>
    <item>
      <title>Re: regarding for VSXs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/regarding-for-VSXs/m-p/264426#M51963</link>
      <description>&lt;P&gt;With VSX, a given VLAN on a given physical interface can only go to one VS. That is, you can't have six VSs all sharing one physical interface to a core transit VLAN. This is where you need a virtual switch. If your six VSs will all use different physical interfaces, or different VLANs on the same physical interfaces, you don't need a switch.&lt;/P&gt;
&lt;P&gt;One thing the VSX documentation and introductions don't really cover: use bonds for all of your interfaces. Don't let VSX be aware of any physical interface which isn't in a bond. Stick the physical interface in a bond, then tell VSX to use the bond instead. This helps a &lt;EM&gt;&lt;STRONG&gt;LOT&lt;/STRONG&gt;&lt;/EM&gt; when you eventually want to replace the hardware. Bonds can have a single member, and non-LACP bonds with only one member don't need any special support on the switch side.&lt;/P&gt;</description>
      <pubDate>Thu, 04 Dec 2025 20:58:32 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/regarding-for-VSXs/m-p/264426#M51963</guid>
      <dc:creator>Bob_Zimmerman</dc:creator>
      <dc:date>2025-12-04T20:58:32Z</dc:date>
    </item>
    <item>
      <title>Re: regarding for VSXs</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/regarding-for-VSXs/m-p/264691#M52043</link>
      <description>&lt;P&gt;To add to all guys have said.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.youtube.com/watch?v=TDEvZ0zVLAY" target="_blank"&gt;https://www.youtube.com/watch?v=TDEvZ0zVLAY&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.checkpoint.com/t5/CheckFlix/ct-p/checkflix" target="_blank"&gt;https://community.checkpoint.com/t5/CheckFlix/ct-p/checkflix&lt;/A&gt;&amp;nbsp;(just search for vsx)&lt;/P&gt;</description>
      <pubDate>Mon, 08 Dec 2025 03:19:14 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/regarding-for-VSXs/m-p/264691#M52043</guid>
      <dc:creator>the_rock</dc:creator>
      <dc:date>2025-12-08T03:19:14Z</dc:date>
    </item>
  </channel>
</rss>

