The hsm_not_logged_in alarms that were triggered during the reboot should now
be cleared from the active alarm list, after the successful login to both HSM cards.
The ASA 310-FIPS is now ready to process SSL traffic again.
Resetting HSM Cards on the ASA 310-FIPS
When removing an ASA 310-FIPS device from a cluster, you have the option to reset (or de-
initialize) the HSM cards.
When an ASA 310-FIPS device that has been removed from a cluster is installed in a new
cluster, or added to an existing cluster, the cards will be initialized again. This is done by
performing a series of steps as part of the setup procedure of the ASA 310-FIPS device itself.
If the Setup utility detects that the cards have not been reset, you will be prompted to reset the
HSM cards at that time. The HSM cards must be reset before they can be initialized. You may
therefore choose to reset the cards already when removing the ASA 310-FIPS device from the
cluster. Resetting the HSM cards will clear all sensitive cryptographic information stored on
the cards. Until the cards are initialized again, they will remain in that state.
To reset the HSM cards, you need the following:
• The two pairs of HSM-SO and HSM-USER iKeys, where each pair is associated with a
particular HSM card on the ASA 310-FIPS device you want to delete from the cluster
• The HSM-SO password associated with each HSM-SO iKey
• Log in as the admin user to the particular ASA 310-FIPS device you want to delete
If the ASA 310-FIPS device will be used in a different department or organization after it has
been deleted from the cluster, you may want to change the current password for the HSM-SO
iKey and the HSM-USER iKey before you reset the HSM cards. The user who performs the
initial setup of the ASA 310-FIPS device must then provide the "transient" passwords known
by both parties when initializing the HSM cards, but can directly change to new HSM-SO and
HSM-USER passwords within the normal initialization procedure.
To change the current password for the HSM-SO iKey before resetting the HSM cards, use
the
/maint/hsm/changepass
command. For more information about this command, see
the "HSM Menu " section under Maintenance Menu in the
Command Reference
.
Note:
When moving the ASA 310-FIPS device to a different location, make sure to maintain the
connection between each pair of HSM-SO and HSM-USER iKeys and the particular HSM
card to which they are associated. To initialize the HSM cards when installing or adding the
device in a cluster, the correct HSM-SO and HSM-USER iKeys are required, as well as the
corresponding HSM-SO and HSM-USER passwords.
1. Log in to the ASA 310-FIPS ASA 310-FIPS that you want to delete from the
cluster.
In this step it is important that you connect to the particular ASA 310-FIPS ASA 310-
FIPS that you want to delete from the cluster. To do that, you can use either a
console connection, or a remote connection (through Telnet or SSH) using the IP
address assigned to the specific ASA 310-FIPS ASA 310-FIPS device. Do not
Resetting HSM Cards on the ASA 310-FIPS
User Guide
April 2013 139
Summary of Contents for 3050-VM
Page 1: ...User Guide Avaya VPN Gateway Release 9 0 NN46120 104 Issue 04 04 April 2013 ...
Page 4: ...4 User Guide April 2013 Comments infodev avaya com ...
Page 12: ...12 User Guide April 2013 ...
Page 20: ...New in this release 20 User Guide April 2013 Comments infodev avaya com ...
Page 30: ...Introducing the VPN Gateway 30 User Guide April 2013 Comments infodev avaya com ...
Page 36: ...Introducing the ASA 310 FIPS 36 User Guide April 2013 Comments infodev avaya com ...
Page 74: ...Upgrading the AVG Software 74 User Guide April 2013 Comments infodev avaya com ...
Page 86: ...Managing Users and Groups 86 User Guide April 2013 Comments infodev avaya com ...
Page 130: ...The Command Line Interface 130 User Guide April 2013 Comments infodev avaya com ...
Page 162: ...Supported Ciphers 162 User Guide April 2013 Comments infodev avaya com ...
Page 212: ...Syslog Messages 212 User Guide April 2013 Comments infodev avaya com ...
Page 242: ...Definition of Key Codes 242 User Guide April 2013 Comments infodev avaya com ...
Page 259: ...Creating a Port Forwarder Authenticator User Guide April 2013 259 ...
Page 266: ...Using the Port Forwarder API 266 User Guide April 2013 Comments infodev avaya com ...
Page 274: ...X 509 274 User Guide April 2013 Comments infodev avaya com ...