<?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 OS Patching Process in Installation</title>
    <link>https://community.splunk.com/t5/Installation/OS-Patching-Process/m-p/411041#M10227</link>
    <description>&lt;P&gt;Will the following process work for allowing our SPLUNK environment to be patched (Linux patching and not SPLUNK patching).  We have an Indexing Cluster with a CM and a single search head and deployment / license server.  I have read through the procedures and wanted to clarify in case I incorrectly do this:&lt;/P&gt;

&lt;P&gt;Step 1 --&amp;gt; Perform patching on the Cluster Manager&lt;/P&gt;

&lt;P&gt;a.  Run splunk stop to stop the SPLUNK process&lt;BR /&gt;
b.  Perform the update and restart&lt;BR /&gt;
c.  Post reboot the Cluster Manager will be back online&lt;/P&gt;

&lt;P&gt;Step 2 --&amp;gt; Perform patching on the Search Head&lt;/P&gt;

&lt;P&gt;a.  Run splunk stop to stop the SPLUNK process&lt;BR /&gt;
b.  Perform the update and restart&lt;BR /&gt;
c.  Post reboot the Search head will be back online&lt;/P&gt;

&lt;P&gt;Step 3 --&amp;gt; Perform patching on the Deployment / License server&lt;/P&gt;

&lt;P&gt;a.  Run splunk stop to stop the SPLUNK process&lt;BR /&gt;
b.  Perform the update and restart&lt;BR /&gt;
c.  Post reboot the Search head will be back online&lt;/P&gt;

&lt;P&gt;Step 4 --&amp;gt; Perform patching on the Indexer peers&lt;/P&gt;

&lt;P&gt;a.  Run splunk enable maintenance-mode on the CM&lt;BR /&gt;
b.  Run splunk stop on Indexer 1&lt;BR /&gt;
c.  Perform the update and restart&lt;BR /&gt;
d.  Post reboot Indexer 1 will be back online&lt;BR /&gt;
e.  Run splunk stop on Indexer 2&lt;BR /&gt;
f.  Perform the update and restart&lt;BR /&gt;
g.  Post reboot Indexer 2 will be back online&lt;BR /&gt;
h.  Run splunk disable maintenance-mode on the CM&lt;BR /&gt;
i.  Confirm with splunk show maintenance-mode on the CM&lt;/P&gt;

&lt;P&gt;Does this look right?&lt;/P&gt;</description>
    <pubDate>Wed, 31 Jul 2019 02:55:01 GMT</pubDate>
    <dc:creator>willadams</dc:creator>
    <dc:date>2019-07-31T02:55:01Z</dc:date>
    <item>
      <title>OS Patching Process</title>
      <link>https://community.splunk.com/t5/Installation/OS-Patching-Process/m-p/411041#M10227</link>
      <description>&lt;P&gt;Will the following process work for allowing our SPLUNK environment to be patched (Linux patching and not SPLUNK patching).  We have an Indexing Cluster with a CM and a single search head and deployment / license server.  I have read through the procedures and wanted to clarify in case I incorrectly do this:&lt;/P&gt;

&lt;P&gt;Step 1 --&amp;gt; Perform patching on the Cluster Manager&lt;/P&gt;

&lt;P&gt;a.  Run splunk stop to stop the SPLUNK process&lt;BR /&gt;
b.  Perform the update and restart&lt;BR /&gt;
c.  Post reboot the Cluster Manager will be back online&lt;/P&gt;

&lt;P&gt;Step 2 --&amp;gt; Perform patching on the Search Head&lt;/P&gt;

&lt;P&gt;a.  Run splunk stop to stop the SPLUNK process&lt;BR /&gt;
b.  Perform the update and restart&lt;BR /&gt;
c.  Post reboot the Search head will be back online&lt;/P&gt;

&lt;P&gt;Step 3 --&amp;gt; Perform patching on the Deployment / License server&lt;/P&gt;

&lt;P&gt;a.  Run splunk stop to stop the SPLUNK process&lt;BR /&gt;
b.  Perform the update and restart&lt;BR /&gt;
c.  Post reboot the Search head will be back online&lt;/P&gt;

&lt;P&gt;Step 4 --&amp;gt; Perform patching on the Indexer peers&lt;/P&gt;

&lt;P&gt;a.  Run splunk enable maintenance-mode on the CM&lt;BR /&gt;
b.  Run splunk stop on Indexer 1&lt;BR /&gt;
c.  Perform the update and restart&lt;BR /&gt;
d.  Post reboot Indexer 1 will be back online&lt;BR /&gt;
e.  Run splunk stop on Indexer 2&lt;BR /&gt;
f.  Perform the update and restart&lt;BR /&gt;
g.  Post reboot Indexer 2 will be back online&lt;BR /&gt;
h.  Run splunk disable maintenance-mode on the CM&lt;BR /&gt;
i.  Confirm with splunk show maintenance-mode on the CM&lt;/P&gt;

&lt;P&gt;Does this look right?&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2019 02:55:01 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/OS-Patching-Process/m-p/411041#M10227</guid>
      <dc:creator>willadams</dc:creator>
      <dc:date>2019-07-31T02:55:01Z</dc:date>
    </item>
    <item>
      <title>Re: OS Patching Process</title>
      <link>https://community.splunk.com/t5/Installation/OS-Patching-Process/m-p/411042#M10228</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/79922"&gt;@willadams&lt;/a&gt;,&lt;BR /&gt;there isn't any rule in OS patcing process, the rules you described are to upgrade Splunk.&lt;BR /&gt;Anyway, the main rule is to upgrade systems one by one.&lt;BR /&gt;I suggest to add only a step, after each restart, to check that Splunk is correctly running.&lt;/P&gt;&lt;P&gt;Only one thing in your environment, it isn't a best practice to have the License Master on the same server of the the Deployment Server (if it manage many Forwarders).&lt;BR /&gt;It's better to have a dedicated server or to put it on the Master Node, never on Deployment Server that, if you have more than 50 Forwarders, must be a dedicated server.&lt;/P&gt;&lt;P&gt;Bye.&lt;BR /&gt;Giuseppe&lt;/P&gt;</description>
      <pubDate>Tue, 26 Jan 2021 07:37:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Installation/OS-Patching-Process/m-p/411042#M10228</guid>
      <dc:creator>gcusello</dc:creator>
      <dc:date>2021-01-26T07:37:23Z</dc:date>
    </item>
  </channel>
</rss>

