<?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: HA Cluster - v9.10 - Issue on the second node with the virtual public IP in PAM Self-Hosted Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327679#M25492</link>
    <description>&lt;P&gt;@Lucas LEBRET-MAUFRET​&amp;nbsp;Should the ClusterLogicalName and NodeLogicalName be different on both the nodes?&lt;/P&gt;</description>
    <pubDate>Fri, 08 Nov 2019 07:17:53 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2019-11-08T07:17:53Z</dc:date>
    <item>
      <title>HA Cluster - v9.10 - Issue on the second node with the virtual public IP</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327671#M25484</link>
      <description>&lt;P&gt;Hello, &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried to install the HA Cluster of CyberArk in version 9.10.&lt;/P&gt;&lt;P&gt;Connected to SAN storage using Fibre Channel.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The installation on the node 1 and 2 was fine. The cluster works when I have the node 1 as Master and node 2 as Slave. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But when I tried to perform a switch over between node 1 to node 2 , i have the error below in the ClusterVaultConsole.log file on node 2 :&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;[ERROR]&amp;nbsp;CVMCS094E The cluster virtual IP 192.zz.yy.xx is not owned by the current node.&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;192.zz.yy.xx is the virtual public IP.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ClusterVault.ini is correctly configured on both node. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Looking the ClusterVaultTrace.log on node 1, there is this line: &lt;/P&gt;&lt;P&gt;&lt;B&gt;[INFO]&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;[Active]&amp;nbsp;CVMCS103I The cluster virtual IP 192.zz.yy.xx was released successfully.&lt;/B&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Someone have an idea about what is happening right there?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks, &lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Lucas.&lt;/P&gt;</description>
      <pubDate>Thu, 20 Sep 2018 14:00:11 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327671#M25484</guid>
      <dc:creator>LucasL</dc:creator>
      <dc:date>2018-09-20T14:00:11Z</dc:date>
    </item>
    <item>
      <title>Re: HA Cluster - v9.10 - Issue on the second node with the virtual public IP</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327672#M25485</link>
      <description>&lt;P&gt;What config do you have in the ClusterVault.ini&amp;nbsp; under # Networking&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Sep 2018 03:46:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327672#M25485</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2018-09-21T03:46:06Z</dc:date>
    </item>
    <item>
      <title>Re: HA Cluster - v9.10 - Issue on the second node with the virtual public IP</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327673#M25486</link>
      <description>&lt;P&gt;Hello, &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ClusterVault.ini on node 1 :&lt;/P&gt;&lt;P&gt;[Environment Name]&lt;/P&gt;&lt;P&gt;ClusterLogicalName=Vault-Cluster&lt;/P&gt;&lt;P&gt;LocalNodeLogicalName=Vault-Cluster-01&lt;/P&gt;&lt;P&gt;PeerNodeLogicalName=Vault-Cluster-02&lt;/P&gt;&lt;P&gt;[Networking]&lt;/P&gt;&lt;P&gt;NetworkCardName=PUBLIC&lt;/P&gt;&lt;P&gt;VirtualIP=&lt;B&gt;192.zz.yy.xx&lt;/B&gt;&lt;/P&gt;&lt;P&gt;PeerNodePrivateIP=10.0.0.9&lt;/P&gt;&lt;P&gt;PeerNodePublicIP=&lt;B&gt;192.zz.yy.xxa&lt;/B&gt;&lt;/P&gt;&lt;P&gt;LocalNodePublicIP=&lt;B&gt;192.zz.yy.xxb&lt;/B&gt;&lt;/P&gt;&lt;P&gt;LocalNodePrivateIP=10.0.0.10&lt;/P&gt;&lt;P&gt;[Storage]&lt;/P&gt;&lt;P&gt;StorageIdentifier = ED074F56&lt;/P&gt;&lt;P&gt;QuorumDiskIdentifier = ED074F58&lt;/P&gt;&lt;P&gt;[Advanced Settings]&lt;/P&gt;&lt;P&gt;PeerNodePort=18581&lt;/P&gt;&lt;P&gt;HealthCheckInterval=10&lt;/P&gt;&lt;P&gt;RetryCountOnFailure=1&lt;/P&gt;&lt;P&gt;ResourceControlTimeout=60&lt;/P&gt;&lt;P&gt;QuorumChallengeDuration=10&lt;/P&gt;&lt;P&gt;SharedConfigurationDirectory=D:\PrivateArk\ClusterVault&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;And on node 2:&lt;/P&gt;&lt;P&gt;[Environment Name]&lt;/P&gt;&lt;P&gt;ClusterLogicalName=UAT-Vault-Cluster&lt;/P&gt;&lt;P&gt;LocalNodeLogicalName=UAT-Vault-Cluster-02&lt;/P&gt;&lt;P&gt;PeerNodeLogicalName=UAT-Vault-Cluster-01&lt;/P&gt;&lt;P&gt;[Networking]&lt;/P&gt;&lt;P&gt;NetworkCardName=PUBLIC&lt;/P&gt;&lt;P&gt;VirtualIP=&lt;B&gt;192.zz.yy.xx&lt;/B&gt;&lt;/P&gt;&lt;P&gt;PeerNodePrivateIP=10.0.0.10&lt;/P&gt;&lt;P&gt;PeerNodePublicIP=&lt;B&gt;192.zz.yy.xxb&lt;/B&gt;&lt;/P&gt;&lt;P&gt;LocalNodePublicIP=&lt;B&gt;192.zz.yy.xxa&lt;/B&gt;&lt;/P&gt;&lt;P&gt;LocalNodePrivateIP=10.0.0.9&lt;/P&gt;&lt;P&gt;[Storage]&lt;/P&gt;&lt;P&gt;StorageIdentifier = ED074F56&lt;/P&gt;&lt;P&gt;QuorumDiskIdentifier = ED074F58&lt;/P&gt;&lt;P&gt;[Advanced Settings]&lt;/P&gt;&lt;P&gt;PeerNodePort=18581&lt;/P&gt;&lt;P&gt;HealthCheckInterval=10&lt;/P&gt;&lt;P&gt;RetryCountOnFailure=1&lt;/P&gt;&lt;P&gt;ResourceControlTimeout=60&lt;/P&gt;&lt;P&gt;QuorumChallengeDuration=10&lt;/P&gt;&lt;P&gt;SharedConfigurationDirectory=D:\PrivateArk\ClusterVault&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Sep 2018 07:29:57 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327673#M25486</guid>
      <dc:creator>LucasL</dc:creator>
      <dc:date>2018-09-21T07:29:57Z</dc:date>
    </item>
    <item>
      <title>Re: HA Cluster - v9.10 - Issue on the second node with the virtual public IP</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327674#M25487</link>
      <description>&lt;P&gt;I assume 'NetworkCardName' above is correct for the second server? Also is the VirtualIP directly specified on either of the 2 servers as an additional IP for the NIC (shouldn't be)&lt;/P&gt;</description>
      <pubDate>Fri, 21 Sep 2018 08:15:30 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327674#M25487</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2018-09-21T08:15:30Z</dc:date>
    </item>
    <item>
      <title>Re: HA Cluster - v9.10 - Issue on the second node with the virtual public IP</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327675#M25488</link>
      <description>&lt;P&gt;The name of the Network Card is correct on both servers. &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;There is the additional IP of the VIP on both PUBLIC cards ; but I assumed it's specified by CyberArk Cluster Management when starting ?&lt;/P&gt;&lt;P&gt;I tried to remove this IP, but after a restart of the Cluster, the IP is recreated on the network PUBLIC cards.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Sep 2018 09:25:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327675#M25488</guid>
      <dc:creator>LucasL</dc:creator>
      <dc:date>2018-09-21T09:25:56Z</dc:date>
    </item>
    <item>
      <title>Re: HA Cluster - v9.10 - Issue on the second node with the virtual public IP</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327676#M25489</link>
      <description>&lt;P&gt;Check your ClusterVault.ini file very carefully.  90% of the file should be identical on both sides....(meaning the Storage section.)   &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Make doublely sure your "PeerNode..." and "Local Node..."  public &amp;amp; private node items are flipped between the cluster nodes.  We did not get it right the first time either!!!&lt;/P&gt;</description>
      <pubDate>Tue, 02 Oct 2018 20:32:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327676#M25489</guid>
      <dc:creator>C.Townsend076673</dc:creator>
      <dc:date>2018-10-02T20:32:25Z</dc:date>
    </item>
    <item>
      <title>Re: HA Cluster - v9.10 - Issue on the second node with the virtual public IP</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327677#M25490</link>
      <description>&lt;P&gt;Yes, ClusterVault.ini is correct, it's really identical on both sides. "PeerNode" and "LocalNode" are correctly defined too...&lt;/P&gt;</description>
      <pubDate>Fri, 05 Oct 2018 11:43:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327677#M25490</guid>
      <dc:creator>LucasL</dc:creator>
      <dc:date>2018-10-05T11:43:56Z</dc:date>
    </item>
    <item>
      <title>Re: HA Cluster - v9.10 - Issue on the second node with the virtual public IP</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327678#M25491</link>
      <description>&lt;P&gt;After reseting the PUBLIC network card, using "netsh int ip reset". Reboot is requiered.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Take care of it if using it remotely, you will lost remote access after the reboot because it will clean static IP addresses on all network cards of the server.&lt;/P&gt;</description>
      <pubDate>Fri, 05 Oct 2018 12:21:54 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327678#M25491</guid>
      <dc:creator>LucasL</dc:creator>
      <dc:date>2018-10-05T12:21:54Z</dc:date>
    </item>
    <item>
      <title>Re: HA Cluster - v9.10 - Issue on the second node with the virtual public IP</title>
      <link>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327679#M25492</link>
      <description>&lt;P&gt;@Lucas LEBRET-MAUFRET​&amp;nbsp;Should the ClusterLogicalName and NodeLogicalName be different on both the nodes?&lt;/P&gt;</description>
      <pubDate>Fri, 08 Nov 2019 07:17:53 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/pam-self-hosted-discussions/ha-cluster-v9-10-issue-on-the-second-node-with-the-virtual/m-p/1327679#M25492</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2019-11-08T07:17:53Z</dc:date>
    </item>
  </channel>
</rss>

