<?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>article Apply OS Updates to DAP Auto-Failover Nodes in Secrets Management Articles</title>
    <link>https://live.paloaltonetworks.com/t5/secrets-management-articles/apply-os-updates-to-dap-auto-failover-nodes/ta-p/1429280</link>
    <description>&lt;H2 dir="auto"&gt;Introduction&lt;/H2&gt;
&lt;P dir="auto"&gt;This how-to guide describes how to apply patches, updates, and perform other routine maintenance on a DAP node in an auto-failover cluster without inadvertently triggering a failover.&lt;/P&gt;
&lt;H2 dir="auto"&gt;&lt;BR /&gt;Background&lt;/H2&gt;
&lt;P dir="auto"&gt;The DAP auto-failover feature detects when the active DAP Master becomes unresponsive and automatically promotes a DAP standby to take its place. However, the conditions caused by failure events (e.g. power outage, network loss, etc.) may also be caused by routine maintenance events that reboot nodes or cause the network to be temporarily unavailable.&lt;/P&gt;
&lt;P dir="auto"&gt;When these routine maintenance events trigger a failover, it requires additional effort to repair the DAP cluster and return it to a state that is resilient to true failures again.&lt;/P&gt;
&lt;H2 dir="auto"&gt;&lt;BR /&gt;Alternative&lt;/H2&gt;
&lt;P dir="auto"&gt;This guide provides a procedure for temporarily disabling auto-failover during maintenance periods. However, many customers have successfully deployed auto-failover clusters with a longer time-to-live (TTL) intended to withstand these short-lived outages. For example, a TTL of 5 minutes (300 seconds) is often sufficient to allow the nodes to reboot without falsely triggering a failover.&lt;/P&gt;
&lt;P dir="auto"&gt;See&amp;nbsp;&lt;A href="https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-DAP/Latest/en/Content/Deployment/HighAvailability/update-cluster-TTL.htm" target="_blank"&gt;Modify Auto-Failover Cluster TTL&lt;/A&gt; &amp;nbsp;for more details on how to accomplish this.&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;Steps&lt;/H3&gt;
&lt;H2 dir="auto"&gt;Procedure for Patching an Auto-failover DAP Cluster&lt;/H2&gt;
&lt;H3 dir="auto"&gt;1. Disable&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;cluster&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;Service on Standbys&lt;/H3&gt;
&lt;P dir="auto"&gt;Disabling the&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;cluster&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;service on the Standbys prevents them from attempting to promote to Master while the active Master is temporarily down for maintenance.&lt;/P&gt;
&lt;P dir="auto"&gt;For each Standby in the auto-failover cluster:&lt;/P&gt;
&lt;OL dir="auto"&gt;&lt;LI&gt;
&lt;P dir="auto"&gt;Connect to the Standby node (e.g. using SSH)&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P dir="auto"&gt;Disable the&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;cluster&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;service with the following command in the DAP container:&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;
sv down cluster&lt;/PRE&gt;
&lt;PRE&gt;
For example:&lt;/PRE&gt;
&lt;PRE class="ckeditor_codeblock"&gt;
$ docker exec dap sv down cluster
&lt;/PRE&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;P dir="auto"&gt;It is not necessary to disable the&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;cluster&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;service on the active Master node.&lt;/P&gt;
&lt;H3 dir="auto"&gt;&lt;BR /&gt;2. Perform Node Maintenance&lt;/H3&gt;
&lt;P dir="auto"&gt;Once the&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;cluster&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;service is disabled on all Standbys, each of the nodes in the Master cluster may be brought offline, rebooted, etc. without triggering a failover from the active Master to a Standby.&lt;/P&gt;
&lt;H3 dir="auto"&gt;&lt;BR /&gt;3. Verify Master is Healthy&lt;/H3&gt;
&lt;P dir="auto"&gt;Once maintenance is complete, verify the Master is currently healthy according to its&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;/health&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;API endpoint:&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;
...
"cluster": {
    "ok": true,
    "status": "running",
    "message": "acting as master"
  },
  "ok": true,
  "role": "master"
&lt;/PRE&gt;
&lt;H3 dir="auto"&gt;&lt;BR /&gt;4. Re-enable the&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;cluster&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;Service on each Standby&lt;/H3&gt;
&lt;P dir="auto"&gt;For each Standby in the auto-failover cluster:&lt;/P&gt;
&lt;OL dir="auto"&gt;&lt;LI&gt;
&lt;P dir="auto"&gt;Connect to the Standby node (e.g. using SSH)&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P dir="auto"&gt;Re-enable the&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;cluster&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;service with the following command in the DAP container:&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;
sv up cluster
&lt;/PRE&gt;
&lt;P dir="auto"&gt;For example:&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;
$ docker exec dap sv up cluster
&lt;/PRE&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;H3 dir="auto"&gt;&lt;BR /&gt;5. Verify Auto-failover Cluster is Healthy&lt;/H3&gt;
&lt;P dir="auto"&gt;Once the&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;cluster&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;service is re-enabled on the Standbys, verify the cluster is healthy.&lt;/P&gt;
&lt;P dir="auto"&gt;Verify the Master is currently healthy according to its&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;/health&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;&amp;nbsp;&lt;/SPAN&gt;API endpoint:&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;
...
"cluster": {
    "ok": true,
    "status": "running",
    "message": "acting as master"
  },
  "ok": true,
  "role": "master"
&lt;/PRE&gt;
&lt;P dir="auto"&gt;Verify each Standby is healthy according to its&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;/health&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;API endpoint:&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;
...
"cluster": {
    "ok": true,
    "status": "standing_by",
    "message": null
  },
  "ok": true,
  "role": "standby"
&lt;/PRE&gt;</description>
    <pubDate>Fri, 21 Apr 2023 15:28:23 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2023-04-21T15:28:23Z</dc:date>
    <item>
      <title>Apply OS Updates to DAP Auto-Failover Nodes</title>
      <link>https://live.paloaltonetworks.com/t5/secrets-management-articles/apply-os-updates-to-dap-auto-failover-nodes/ta-p/1429280</link>
      <description>&lt;H2 dir="auto"&gt;Introduction&lt;/H2&gt;
&lt;P dir="auto"&gt;This how-to guide describes how to apply patches, updates, and perform other routine maintenance on a DAP node in an auto-failover cluster without inadvertently triggering a failover.&lt;/P&gt;
&lt;H2 dir="auto"&gt;&lt;BR /&gt;Background&lt;/H2&gt;
&lt;P dir="auto"&gt;The DAP auto-failover feature detects when the active DAP Master becomes unresponsive and automatically promotes a DAP standby to take its place. However, the conditions caused by failure events (e.g. power outage, network loss, etc.) may also be caused by routine maintenance events that reboot nodes or cause the network to be temporarily unavailable.&lt;/P&gt;
&lt;P dir="auto"&gt;When these routine maintenance events trigger a failover, it requires additional effort to repair the DAP cluster and return it to a state that is resilient to true failures again.&lt;/P&gt;
&lt;H2 dir="auto"&gt;&lt;BR /&gt;Alternative&lt;/H2&gt;
&lt;P dir="auto"&gt;This guide provides a procedure for temporarily disabling auto-failover during maintenance periods. However, many customers have successfully deployed auto-failover clusters with a longer time-to-live (TTL) intended to withstand these short-lived outages. For example, a TTL of 5 minutes (300 seconds) is often sufficient to allow the nodes to reboot without falsely triggering a failover.&lt;/P&gt;
&lt;P dir="auto"&gt;See&amp;nbsp;&lt;A href="https://docs.cyberark.com/Product-Doc/OnlineHelp/AAM-DAP/Latest/en/Content/Deployment/HighAvailability/update-cluster-TTL.htm" target="_blank"&gt;Modify Auto-Failover Cluster TTL&lt;/A&gt; &amp;nbsp;for more details on how to accomplish this.&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;
&lt;H3&gt;Steps&lt;/H3&gt;
&lt;H2 dir="auto"&gt;Procedure for Patching an Auto-failover DAP Cluster&lt;/H2&gt;
&lt;H3 dir="auto"&gt;1. Disable&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;cluster&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;Service on Standbys&lt;/H3&gt;
&lt;P dir="auto"&gt;Disabling the&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;cluster&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;service on the Standbys prevents them from attempting to promote to Master while the active Master is temporarily down for maintenance.&lt;/P&gt;
&lt;P dir="auto"&gt;For each Standby in the auto-failover cluster:&lt;/P&gt;
&lt;OL dir="auto"&gt;&lt;LI&gt;
&lt;P dir="auto"&gt;Connect to the Standby node (e.g. using SSH)&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P dir="auto"&gt;Disable the&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;cluster&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;service with the following command in the DAP container:&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;
sv down cluster&lt;/PRE&gt;
&lt;PRE&gt;
For example:&lt;/PRE&gt;
&lt;PRE class="ckeditor_codeblock"&gt;
$ docker exec dap sv down cluster
&lt;/PRE&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;P dir="auto"&gt;It is not necessary to disable the&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;cluster&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;service on the active Master node.&lt;/P&gt;
&lt;H3 dir="auto"&gt;&lt;BR /&gt;2. Perform Node Maintenance&lt;/H3&gt;
&lt;P dir="auto"&gt;Once the&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;cluster&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;service is disabled on all Standbys, each of the nodes in the Master cluster may be brought offline, rebooted, etc. without triggering a failover from the active Master to a Standby.&lt;/P&gt;
&lt;H3 dir="auto"&gt;&lt;BR /&gt;3. Verify Master is Healthy&lt;/H3&gt;
&lt;P dir="auto"&gt;Once maintenance is complete, verify the Master is currently healthy according to its&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;/health&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;API endpoint:&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;
...
"cluster": {
    "ok": true,
    "status": "running",
    "message": "acting as master"
  },
  "ok": true,
  "role": "master"
&lt;/PRE&gt;
&lt;H3 dir="auto"&gt;&lt;BR /&gt;4. Re-enable the&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;cluster&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;Service on each Standby&lt;/H3&gt;
&lt;P dir="auto"&gt;For each Standby in the auto-failover cluster:&lt;/P&gt;
&lt;OL dir="auto"&gt;&lt;LI&gt;
&lt;P dir="auto"&gt;Connect to the Standby node (e.g. using SSH)&lt;/P&gt;
&lt;/LI&gt;&lt;LI&gt;
&lt;P dir="auto"&gt;Re-enable the&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;cluster&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;service with the following command in the DAP container:&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;
sv up cluster
&lt;/PRE&gt;
&lt;P dir="auto"&gt;For example:&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;
$ docker exec dap sv up cluster
&lt;/PRE&gt;
&lt;/LI&gt;&lt;/OL&gt;
&lt;H3 dir="auto"&gt;&lt;BR /&gt;5. Verify Auto-failover Cluster is Healthy&lt;/H3&gt;
&lt;P dir="auto"&gt;Once the&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;cluster&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;service is re-enabled on the Standbys, verify the cluster is healthy.&lt;/P&gt;
&lt;P dir="auto"&gt;Verify the Master is currently healthy according to its&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;/health&lt;/SPAN&gt;&lt;/CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;&amp;nbsp;&lt;/SPAN&gt;API endpoint:&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;
...
"cluster": {
    "ok": true,
    "status": "running",
    "message": "acting as master"
  },
  "ok": true,
  "role": "master"
&lt;/PRE&gt;
&lt;P dir="auto"&gt;Verify each Standby is healthy according to its&amp;nbsp;&lt;CODE&gt;&lt;SPAN style="background-color: #ecf0f1;"&gt;/health&lt;/SPAN&gt;&lt;/CODE&gt;&amp;nbsp;API endpoint:&lt;/P&gt;
&lt;PRE class="ckeditor_codeblock"&gt;
...
"cluster": {
    "ok": true,
    "status": "standing_by",
    "message": null
  },
  "ok": true,
  "role": "standby"
&lt;/PRE&gt;</description>
      <pubDate>Fri, 21 Apr 2023 15:28:23 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/secrets-management-articles/apply-os-updates-to-dap-auto-failover-nodes/ta-p/1429280</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2023-04-21T15:28:23Z</dc:date>
    </item>
  </channel>
</rss>

