After the appliance is booted up, set KeyCustodian PINs to activate the appliance and confirm the functionality.

1. Set KC-PINs by following the steps from 'Setting the KC PIN on the SAKA Server'.
2. Once KC-PINs have been set successfully by minimum number of required KeyCustodians, run pingsaka.sh script to confirm that the appliance has been activated.

   shell> pingsaka.sh <DID>

   Example:

   shell> pingsaka.sh 1

   NOTE:This would prompt for a password and you would need to provide a password for pinguser of the DID provided in the argument.

3. Confirm that replication ports (7001-7003) are connected with other nodes in the cluster.

   shell> zmq

   Example: Using two servers addressed 10.0.2.207 and 10.0.2.208, if all required connections are present the zmq command will output something like this:

   ::ffff:10.0.2.207:43486     ::ffff:10.0.2.208:7001      ESTABLISHED
    
   ::ffff:10.0.2.207:45486     ::ffff:10.0.2.208:7002      ESTABLISHED
    
   ::ffff:10.0.2.207:44612     ::ffff:10.0.2.208:7003      ESTABLISHED
    
   ::ffff:10.0.2.207:7001      ::ffff:10.0.2.208:46458     ESTABLISHED
    
   ::ffff:10.0.2.207:7002      ::ffff:10.0.2.208:42434     ESTABLISHED
    
   ::ffff:10.0.2.207:7003      ::ffff:10.0.2.208:54661     ESTABLISHED
   

   In the first 3 rows you will notice that 10.0.2.207 is connected to 10.0.2.208 on all required ports and the next 3 rows tell you that 10.0.2.208 has connected to 10.0.2.207 on all required ports. Duplicates may be shown and will not cause problems, but missing a port connection will result in replication problems.

4. Confirm replication count is going down on other nodes in the cluster for the appliance that was rebooted.

   shell> repl

   This command displays records currently in the queue. The first column is the Target Server ID (TSID) and the second column displays how many replication records are in queue for that TSID. If this command returns nothing then replication is up to date.