<?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: How to stop  only a virtual system  in a R80.40  VSX box running other  VS's in Firewall and Security Management</title>
    <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-stop-only-a-virtual-system-in-a-R80-40-VSX-box-running/m-p/160431#M28275</link>
    <description>&lt;P&gt;You do not need to stop it. You can unload the policy on it, and disconnect it from the networks during migration. Once you moved traffic to a physical box, and it is proven to work well, you can just delete that VS, to finish the migration. You do not really need to stop a VS, though.&lt;/P&gt;</description>
    <pubDate>Wed, 26 Oct 2022 09:44:31 GMT</pubDate>
    <dc:creator>_Val_</dc:creator>
    <dc:date>2022-10-26T09:44:31Z</dc:date>
    <item>
      <title>How to stop  only a virtual system  in a R80.40  VSX box running other  VS's</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-stop-only-a-virtual-system-in-a-R80-40-VSX-box-running/m-p/160390#M28271</link>
      <description>&lt;P&gt;Hello&amp;nbsp; checkmates....&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm afraid that it's not possible but I would like to ask you for this subject...&lt;/P&gt;&lt;P&gt;I have&amp;nbsp; to migrate a R80.40 VSX VS box (EoS) to a new hardware and inside this box there are running 5 VS. My intention is to do a one by one migration but&amp;nbsp; I need to stop only the migrated VS .&amp;nbsp; Is&amp;nbsp; it possible? I don't find any vsx command to stop only one VS.&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Manel&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Oct 2022 16:54:00 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-stop-only-a-virtual-system-in-a-R80-40-VSX-box-running/m-p/160390#M28271</guid>
      <dc:creator>Maller</dc:creator>
      <dc:date>2022-10-25T16:54:00Z</dc:date>
    </item>
    <item>
      <title>Re: How to stop  only a virtual system  in a R80.40  VSX box running other  VS's</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-stop-only-a-virtual-system-in-a-R80-40-VSX-box-running/m-p/160398#M28272</link>
      <description>&lt;P&gt;&lt;a href="https://community.checkpoint.com/t5/user/viewprofilepage/user-id/49265"&gt;@Maller&lt;/a&gt;&amp;nbsp;cpstop/cpstart in the context of a VS stops and starts this virtual system. In the past (older R77.x releases) you could do that with script vs_stop.sh vs_start.sh, but these are no longer available.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 25 Oct 2022 17:55:55 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-stop-only-a-virtual-system-in-a-R80-40-VSX-box-running/m-p/160398#M28272</guid>
      <dc:creator>Wolfgang</dc:creator>
      <dc:date>2022-10-25T17:55:55Z</dc:date>
    </item>
    <item>
      <title>Re: How to stop  only a virtual system  in a R80.40  VSX box running other  VS's</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-stop-only-a-virtual-system-in-a-R80-40-VSX-box-running/m-p/160409#M28273</link>
      <description>&lt;P&gt;sk169472 is relevant here.&lt;/P&gt;
&lt;P&gt;Depending on the connectivity others might shutdown/disable interfaces on the network side.&lt;/P&gt;</description>
      <pubDate>Tue, 25 Oct 2022 23:04:05 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-stop-only-a-virtual-system-in-a-R80-40-VSX-box-running/m-p/160409#M28273</guid>
      <dc:creator>Chris_Atkinson</dc:creator>
      <dc:date>2022-10-25T23:04:05Z</dc:date>
    </item>
    <item>
      <title>Re: How to stop  only a virtual system  in a R80.40  VSX box running other  VS's</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-stop-only-a-virtual-system-in-a-R80-40-VSX-box-running/m-p/160420#M28274</link>
      <description>&lt;P&gt;Another idea will be changing the VLAN IDs of the interfaces in the old VS before the new VS are started. With this you have a quick way to switch back.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Oct 2022 04:59:57 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-stop-only-a-virtual-system-in-a-R80-40-VSX-box-running/m-p/160420#M28274</guid>
      <dc:creator>Wolfgang</dc:creator>
      <dc:date>2022-10-26T04:59:57Z</dc:date>
    </item>
    <item>
      <title>Re: How to stop  only a virtual system  in a R80.40  VSX box running other  VS's</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-stop-only-a-virtual-system-in-a-R80-40-VSX-box-running/m-p/160431#M28275</link>
      <description>&lt;P&gt;You do not need to stop it. You can unload the policy on it, and disconnect it from the networks during migration. Once you moved traffic to a physical box, and it is proven to work well, you can just delete that VS, to finish the migration. You do not really need to stop a VS, though.&lt;/P&gt;</description>
      <pubDate>Wed, 26 Oct 2022 09:44:31 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-stop-only-a-virtual-system-in-a-R80-40-VSX-box-running/m-p/160431#M28275</guid>
      <dc:creator>_Val_</dc:creator>
      <dc:date>2022-10-26T09:44:31Z</dc:date>
    </item>
    <item>
      <title>Re: How to stop  only a virtual system  in a R80.40  VSX box running other  VS's</title>
      <link>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-stop-only-a-virtual-system-in-a-R80-40-VSX-box-running/m-p/211753#M40157</link>
      <description>&lt;P&gt;Old thread, but still applicable.&amp;nbsp; Consult&amp;nbsp;&lt;A href="https://support.checkpoint.com/results/sk/sk169472" target="_blank"&gt;https://support.checkpoint.com/results/sk/sk169472&lt;/A&gt;&amp;nbsp;(How to restart a specific VSX Virtual System in R80.30 and higher)&lt;/P&gt;</description>
      <pubDate>Thu, 18 Apr 2024 14:38:15 GMT</pubDate>
      <guid>https://community.checkpoint.com/t5/Firewall-and-Security-Management/How-to-stop-only-a-virtual-system-in-a-R80-40-VSX-box-running/m-p/211753#M40157</guid>
      <dc:creator>ThomasGro</dc:creator>
      <dc:date>2024-04-18T14:38:15Z</dc:date>
    </item>
  </channel>
</rss>

