<?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: FMC shut properly in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/3919712#M927846</link>
    <description>&lt;P&gt;When you restart the FMC server from the hypervisor the necessary processes will all startup automatically.&lt;/P&gt;
&lt;P&gt;FMC puts the necessary startup scripts in&amp;nbsp;/etc/rc.d/init.d so the underlying RHEL knows to start it automatically.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 05 Sep 2019 15:33:28 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2019-09-05T15:33:28Z</dc:date>
    <item>
      <title>FMC shut properly</title>
      <link>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/3188100#M927842</link>
      <description>&lt;P&gt;Hello Guys&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;how can i shut Properly FMC from both CLI and GUI to avoid DB corruption&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;pls see attachment&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 14:20:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/3188100#M927842</guid>
      <dc:creator>Ibrahim Jamil</dc:creator>
      <dc:date>2020-02-21T14:20:59Z</dc:date>
    </item>
    <item>
      <title>Re: FMC shut properly</title>
      <link>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/3188594#M927843</link>
      <description>&lt;P&gt;There was nothing attached but that's OK.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;From the GUI, use the menu choice under Sytem &amp;gt; Configuration &amp;gt; Process to either shutdown, reboot or restart your FMC.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;From the cli, use the console script with the same arguments.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Both are described here (with slightly different GUI menu location for the older Firesight Management Center 5.x):&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/security/firesight-management-center/118594-technote-firesight-00.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/security/firesight-management-center/118594-technote-firesight-00.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 24 Sep 2017 09:01:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/3188594#M927843</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2017-09-24T09:01:59Z</dc:date>
    </item>
    <item>
      <title>Re: FMC shut properly</title>
      <link>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/3189259#M927844</link>
      <description>Thanks</description>
      <pubDate>Mon, 25 Sep 2017 19:11:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/3189259#M927844</guid>
      <dc:creator>Ibrahim Jamil</dc:creator>
      <dc:date>2017-09-25T19:11:39Z</dc:date>
    </item>
    <item>
      <title>Re: FMC shut properly</title>
      <link>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/3919656#M927845</link>
      <description>&lt;P&gt;&lt;a href="https://community.cisco.com/t5/user/viewprofilepage/user-id/326046"&gt;@Marvin Rhoads&lt;/a&gt;&amp;nbsp;If i shutdown FMC from&amp;nbsp;System --&amp;gt; Configuration --&amp;gt; Process --&amp;gt; Shutdown Management Center&amp;nbsp; and then i reboot the VM from vcenter, how the FMC will power on again?&lt;/P&gt;&lt;P&gt;Is there any command that i can run in FMC cli and turn it on or it will turn on by itself ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;</description>
      <pubDate>Thu, 05 Sep 2019 14:30:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/3919656#M927845</guid>
      <dc:creator>anousakisioannis</dc:creator>
      <dc:date>2019-09-05T14:30:24Z</dc:date>
    </item>
    <item>
      <title>Re: FMC shut properly</title>
      <link>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/3919712#M927846</link>
      <description>&lt;P&gt;When you restart the FMC server from the hypervisor the necessary processes will all startup automatically.&lt;/P&gt;
&lt;P&gt;FMC puts the necessary startup scripts in&amp;nbsp;/etc/rc.d/init.d so the underlying RHEL knows to start it automatically.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 05 Sep 2019 15:33:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/3919712#M927846</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2019-09-05T15:33:28Z</dc:date>
    </item>
    <item>
      <title>Re: FMC shut properly</title>
      <link>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/3920034#M927847</link>
      <description>&lt;P&gt;Hello Marvin,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you one more time for your help and your valuable contribution on this community!!&lt;/P&gt;</description>
      <pubDate>Fri, 06 Sep 2019 07:30:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/3920034#M927847</guid>
      <dc:creator>anousakisioannis</dc:creator>
      <dc:date>2019-09-06T07:30:41Z</dc:date>
    </item>
    <item>
      <title>Re: FMC shut properly</title>
      <link>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/4276583#M1077533</link>
      <description>&lt;P&gt;HI What will happen&amp;nbsp; if i directly shut down FMC VM From Console? did it crash the DB&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jan 2021 08:42:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/4276583#M1077533</guid>
      <dc:creator>IT.DC</dc:creator>
      <dc:date>2021-01-21T08:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: FMC shut properly</title>
      <link>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/4276649#M1077537</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have done twice and nothing happened but the appropriate way to do it, as every application, you should shut down FMC via console.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jan 2021 10:01:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/4276649#M1077537</guid>
      <dc:creator>anousakisioannis</dc:creator>
      <dc:date>2021-01-21T10:01:19Z</dc:date>
    </item>
    <item>
      <title>Re: FMC shut properly</title>
      <link>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/4277015#M1077551</link>
      <description>&lt;P&gt;It may or may not come back normally.&lt;/P&gt;
&lt;P&gt;If you watch the messages from console when it restarts, you will see that it realizes it was not shutdown gracefully and it will try to recover from any errors. Usually it is successful but not always. when it fails it can leave you with a non-working server that you will have to restore from backup or - if there's no backup available - rebuild from scratch.&lt;/P&gt;
&lt;P&gt;So:&lt;/P&gt;
&lt;P&gt;1. Always shutdown gracefully if you can&lt;/P&gt;
&lt;P&gt;2. Always have a recent backup available off-box. (or, even better, periodically shutdown gracefully and then snapshot the VM)&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jan 2021 18:57:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/fmc-shut-properly/m-p/4277015#M1077551</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2021-01-21T18:57:43Z</dc:date>
    </item>
  </channel>
</rss>

