HA Cluster - v9.10 - Issue on the second node with the virtual public IP

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

HA Cluster - v9.10 - Issue on the second node with the virtual public IP

L2 Linker

Hello,

 

I tried to install the HA Cluster of CyberArk in version 9.10.

Connected to SAN storage using Fibre Channel.

 

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.

 

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 :

 

[ERROR] CVMCS094E The cluster virtual IP 192.zz.yy.xx is not owned by the current node.

 

  • 192.zz.yy.xx is the virtual public IP.

 

The ClusterVault.ini is correctly configured on both node.

 

Looking the ClusterVaultTrace.log on node 1, there is this line:

[INFO]      [Active] CVMCS103I The cluster virtual IP 192.zz.yy.xx was released successfully.

 

Someone have an idea about what is happening right there?

 

Thanks,

Regards,

Lucas.

1 accepted solution

Accepted Solutions

L2 Linker

After reseting the PUBLIC network card, using "netsh int ip reset". Reboot is requiered.

 

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.

View solution in original post

8 REPLIES 8

L0 Member

What config do you have in the ClusterVault.ini  under # Networking

 

L2 Linker

Hello,

 

ClusterVault.ini on node 1 :

[Environment Name]

ClusterLogicalName=Vault-Cluster

LocalNodeLogicalName=Vault-Cluster-01

PeerNodeLogicalName=Vault-Cluster-02

[Networking]

NetworkCardName=PUBLIC

VirtualIP=192.zz.yy.xx

PeerNodePrivateIP=10.0.0.9

PeerNodePublicIP=192.zz.yy.xxa

LocalNodePublicIP=192.zz.yy.xxb

LocalNodePrivateIP=10.0.0.10

[Storage]

StorageIdentifier = ED074F56

QuorumDiskIdentifier = ED074F58

[Advanced Settings]

PeerNodePort=18581

HealthCheckInterval=10

RetryCountOnFailure=1

ResourceControlTimeout=60

QuorumChallengeDuration=10

SharedConfigurationDirectory=D:\PrivateArk\ClusterVault

 

And on node 2:

[Environment Name]

ClusterLogicalName=UAT-Vault-Cluster

LocalNodeLogicalName=UAT-Vault-Cluster-02

PeerNodeLogicalName=UAT-Vault-Cluster-01

[Networking]

NetworkCardName=PUBLIC

VirtualIP=192.zz.yy.xx

PeerNodePrivateIP=10.0.0.10

PeerNodePublicIP=192.zz.yy.xxb

LocalNodePublicIP=192.zz.yy.xxa

LocalNodePrivateIP=10.0.0.9

[Storage]

StorageIdentifier = ED074F56

QuorumDiskIdentifier = ED074F58

[Advanced Settings]

PeerNodePort=18581

HealthCheckInterval=10

RetryCountOnFailure=1

ResourceControlTimeout=60

QuorumChallengeDuration=10

SharedConfigurationDirectory=D:\PrivateArk\ClusterVault

 

 

L4 Transporter

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)

L2 Linker

The name of the Network Card is correct on both servers.

 

There is the additional IP of the VIP on both PUBLIC cards ; but I assumed it's specified by CyberArk Cluster Management when starting ?

I tried to remove this IP, but after a restart of the Cluster, the IP is recreated on the network PUBLIC cards.

L3 Networker

Check your ClusterVault.ini file very carefully. 90% of the file should be identical on both sides....(meaning the Storage section.)

 

Make doublely sure your "PeerNode..." and "Local Node..." public & private node items are flipped between the cluster nodes. We did not get it right the first time either!!!

L2 Linker

Yes, ClusterVault.ini is correct, it's really identical on both sides. "PeerNode" and "LocalNode" are correctly defined too...

L2 Linker

After reseting the PUBLIC network card, using "netsh int ip reset". Reboot is requiered.

 

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.

@Lucas LEBRET-MAUFRET​ Should the ClusterLogicalName and NodeLogicalName be different on both the nodes?

  • 1 accepted solution
  • 749 Views
  • 8 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!