Appendix B: HA for V6x00 and Virtual Appliances
Configuring High Availability for Network HSM-enabled Nodes
DSM Installation and Configuration Guide
Copyright 2009 - 2020 Thales Group. All rights reserved.
140
Refer to the nShield user documentation for a description of how to configure and deploy the nShield Connect
device and the associated RFS.
3. Add both nShield Connect appliances to each of the DSMs as follows:
a. Add the nShield Connect appliance to the DSM. Open a CLI session on the DSM appliance that is a client of
the nShield Connect appliance.
Note
If the nShield Connect Security World is FIPS 140-2 level 3 compliant, only one card from the associated
ACS is required for this step. The card is only required for the first Connect device to be added to the DSM,
it is not required for any subsequent nShield Connect appliances that are added.
b. Navigate to the HSM category of commands, type the following at the prompt:
0000:dsm$ hsm
0001:hsm$
c. Use the
connect add
command to add the nShield Connect to the DSM. Type the following command at the
prompt,
0001:hsm$ connect add <
nShield_Connect_IP_Address
> <
RFS_IP_Address
>
o
nShield Connect IP Address
: IP address of the nShield Connect appliance
o
RFS IP Address
: IP address of the computer that has the RFS installed
Example
:
0002: hsm$ connect add 192.168.3.18 192.168.3.4
A warning displays, informing you that once this DSM is converted to a network HSM-enabled appliance, it
cannot be rolled back.
d. Type
yes
to continue. The DSM is restarted if the operation is successful.
e. Follow the prompts to add the nShield Connect appliance to the DSM.
f. To view the nShield Connect that has been added, type:
0002: hsm$ connect show
g. If there are more nShield appliances in the same Security World, you can add them now using the
connect
add
command.
Note
The About page of the DSM Web UI also displays the nShield Connect devices that have been configured.
Configure an HA cluster with HSM-enabled nodes
The second method for creating a network HSM-enabled HA cluster is to configure a standalone network HSM-
enabled DSM, as HA node 1. Then join other network HSM-enabled DSM nodes to the HA cluster.
Note
Once a DSM is network HSM-enabled, it must be connected to at least one nShield Connect appliance. If
you remove an nShield appliance from a Security World, you must make sure that any DSM s that were
connected to it, are now connected to another nShield appliance belonging to that same Security World.
In this case, if more than one nShield appliance is available in the Security World, a DSM Administrator
could choose to use any of the available nShield appliances after the DSM has joined the cluster.
See
"Configuring High Availability for Network HSM-enabled Nodes" on the previous page
.
See the
VDS Administrators Guide
for instructions on other HA functions such as: