Contents

Setting up a Cyberark HA Vault Cluster - Part 2


1. Preinstalation tasks

This time we’ll be connecting our Quorum and Shared Storage disks to our Vault 1

Let’s check the Network configuration for Vault 1. Let’s make sure we have 2 IPs configured as shown.

/havault2/images/img9.webp
Vault 1 Network config

Start the iSCSI Disk Initiator, we can start the console by running iscsicpl.exe. Here we need to “Discover” a portal so after hitting the Discovery Portal button, we need to provide IP 10.200.10.10 and port 3260. The targets will show as inactive at first.

/havault2/images/img1.webp
iSCSI Initiator - Discovery

Two targets will show in the Discovered Targets tab, those are Shared Storage (safes) and Quorum disks still incative. Our Vault_1 host is not yet connected to the targets

/havault2/images/img2.webp
iSCSI Initiator - Discovered Targets

Select first target and click on Connect » Check the “Add this connection to list of favorite Targets” » Click on advanced :

Advanced Connection Properties
  • Local Adpater: Microsoft iSCSI Initiator
  • Initiator IP: 10.200.10.11 # This is our Vault_1 IP
  • Tartet portal IP: 10.200.10.10/3260 # This is our ADCore server IP and iSCSI port
/havault2/images/img3.webp
iSCSI Initiator - Advanced connection Properties
Advanced Connection Properties
Remember from the last post our connection is IP based. We’re not using chap connection this time.

If we check the disk status @ADCore, it shows as connected

/havault2/images/img5.webp
Disk Status @ADCore

Until this point. we have connected the disk but it need to be initializaed so on Vault_1 go to Disk Manager. Check Disk Status and bring it online

/havault2/images/img10.webp
Vault_1 Disks manager

Initialize it

/havault2/images/img11.webp
Vault_1 Disks manager - disk online

Disk turns blue and waiting for data 🐳

/havault2/images/img12.webp
Vault_1 Disks manager - Initialize disk

Now, we need to do the same for the Quorum disk.

In the next post we’ll be installing the Cyberark Cluster-Node Vault.