- Hardware Appliance Unboxing
- Initial Set-up
- Restore from Backup
- Connect to Cluster
- Using External CA for Installation
- Basic Hardware Operations
- WebConf - Configurator of Hardware Appliance
- Certificates and Trusted CAs
- Setting up a Validation Authority (VA)
- HA Setup
- PKCS#11 Slot Smart Card Activation
- EJBCA Administration
- Certificate Life Cycle Management
Creating CA Hierarchy
- Step 1: Create the RootCA
- Step 2: Create Certificate Profile for SubCAs
- Step 3: Create End Entity Profile for SubCAs
- Step 4: Import RootCA as External CA in Node A
- Step 5: Create SignCA as SubCA in Node A
- Step 6: Create AuthCA as SubCA in Node A
- Step 7: Create SSLCA as SubCA in Node A
- Step 8: Create Certificate Profiles for End Entities that use the SubCAs
- Step 9: Create End Entity Profiles for SubCAs
- Step 10: Create End Entities that use the SubCAs
- Managing End Entities
- Creating Java Truststore
- Check for Weak Debian Keys
- Hardware Appliance 3.5.4 Release Notes
- Hardware Appliance 3.5.3 Release Notes
- Hardware Appliance 3.5.2 Release Notes
- Hardware Appliance 3.5.1 Release Notes
- Hardware Appliance 3.5.0 Release Notes
- PKI Appliance 3.4.5 Release Notes
- PKI Appliance 3.4.4 Release Notes
- PKI Appliance 3.4.3 Release Notes
PKI Appliance 3.4.2 Release Notes
PKI Appliance 3.4.1 Release Notes
- Release Notes Summary
- Hardware Appliance 3.5.X Upgrade Notes
Cluster Shutdown and Startup
The following describes how to do a controlled shutdown of the whole cluster and get back to a fully running state.
Shutting down the cluster
When shutting down an N node cluster, start with a graceful shutdown of the node with the highest node number (usually number 3) and wait until the node is fully shutdown before proceeding with the next one. This ensures that the quorum is kept as long as possible and in the end node 1 is the most up to date node.
Starting a fully shutdown cluster
After a controlled shutdown as described in Shutting down the cluster, the cluster nodes should automatically become Active starting with the most up to date node after startup.
If the cluster is unable to automatically become Active, the administrator needs to manually bootrap the cluster from the node with the most up to date data set. The administrator can identify the node that had an Active database status last before the shutdown by comparing the Last Transaction ID shown under the Cluster tab in WebConf of all the nodes.
Even after a power outage that seems instantaneous, the Last Transaction ID of all nodes should be compared before selecting a node to Force into Active.
Do the following:
- Power up all nodes.
- Wait a minute after all nodes have started to see if the cluster automatically becomes Active.
- If manual intervention is needed, select the node with the highest Last Transaction ID and use Force into Active on this node (and only this node).
- Wait until all N nodes are fully started, and the database status is Active on each node.