If you are setting up an EA and failed during lsconfigurationwizard, usually you can narrow down the issues through looking at the cluster_create_xxx logs, cluster_add_xxx logs, cluster_role_create_xxx logs and cluster_dsrole_create_xxx logs to troubleshoot the issue (logs located at e:\nic\<version>\<D-Srv>\logs = %_envision%\logs).

Then you can run specific commands shown below to setup the cluster manually. If you experienced issues in an operative environment and cluster can't run anymore, usually it's an indication of a failure in the NAS.  You will need to fix the NAS first, then you can proceed to recreate the cluster

Before running the commands, please do ensure that all of the nodes (DA and CAs) have got an iscsi channels established with the NAS by checking the iscsi initiator -> Targets, ensuring the status is connected.

Then make sure the DA1 actually has access to the Quorum drive, i.e: The drive is accessible through windows explorer and has an proper state in disk management.  If not, run iscsi-setup.cmd (from c:\windows\installation) on the DA1.

After ensuring above, you can run following commands to re-create cluster.

Firstly open command prompt and go to %_envision%\bin directory.

A. Cleanup existing cluster

Cluster-cleanup <node>
e.g:
cluster-cleanup SIEM7-DA1
cluster-cleanup SIEM7-CA1
cluster-cleanup SIEM7-CA2
cluster-cleanup SIEM7-CA3
cluster-cleanup SIEM7-CA4


B. Create cluster
Cluster-create <cluster name> <cluster IP from config> NIC_EA <nic_ea password> <DA1 node name>
e.g:
cluster-create NICCLSTR.SIEM7.nic 10.203.2.200 NIC_EA Thisis7th@ne SIEM7-DA1


At this point, you can go to Start -> Aadministrative Tools -> Cluster Administrator, and connect to 10.203.2.200 to check if a cluster is created.  You can then observe the rest of the configurations being configured in this UI while running rest of the commands.

C. Add nodes to cluster
cluster-add <cluster name> <CA1 internal IP address> <nic_ea password>
e.g:
cluster-add NICCLSTR.SIEM7.nic 10.203.2.41 Thisis7th@ne
cluster-add NICCLSTR.SIEM7.nic 10.203.2.42 Thisis7th@ne
cluster-add NICCLSTR.SIEM7.nic 10.203.2.43 Thisis7th@ne
cluster-add NICCLSTR.SIEM7.nic 10.203.2.43 Thisis7th@ne


D. Creating LC roles in Cluster
cluster-lsrole-create <Role name> <Virtual server name> <VIP> <Mask for VIP> <phyiscal node name of the role owner> <physical node name of DA1>
e.g:
cluster-lsrole-create LC1 SIEM7-LC1 10.32.28.130 255.255.240 SIEM7-CA1 SIEM7-DA1
cluster-lsrole-create LC2 SIEM7-LC2 10.32.28.131 255.255.240 SIEM7-CA2 SIEM7-DA1
cluster-lsrole-create LC3 SIEM7-LC3 10.32.28.132 255.255.240 SIEM7-CA3 SIEM7-DA1


E. Creating DS roles in Cluster
cluster-dsrole-create <Role name> <Virtual server name> <VIP for SWITCH network> <Mask for VIP on switch network> <VIP for LAN network> <Mask for VIP on LAN network> <physical nodename of CAs>
cluster-dsrole-create DS1 SIEM7-DS1 10.203.2.11 255.255.255.0 10.32.27.129 255.255.255.0 SIEM7-CA1 SIEM7-CA2 SIEM7-CA3 SIEM7-CA4


F. (Optional) Check clusterconfig table in nic.db.  One way to check is by running, %_envision%\database\cmd\dbprinttable cluserterconfig.  If entries are missing for DS1, LCx, run below commands under enVision database\cmd folder.
initial_ea_install <site> <Role type> <role name> <VIP>
e.g:
e:\nic\4100\SIEM7-DA1\database\cmd\initial_ea_install SIEM7 LC LC1 10.32.28.130
e:\nic\4100\SIEM7-DA1\database\cmd\initial_ea_install SIEM7 LC LC2 10.32.28.131
e:\nic\4100\SIEM7-DA1\database\cmd\initial_ea_install SIEM7 DS DS1 10.32.28.129

Reboot all nodes for it to take effect.  Make sure DA1 is completely restarted before moving on to reboot the rest of the nodes.