Appendix F: Troubleshooting
Chassis Issues
DSM Installation and Configuration Guide
Copyright 2009 - 2020 Thales Group. All rights reserved.
178
Module 1 slot 2:- no passphrase specified - overwriting card
Card writing complete.
security world generated on module #0; hknso = 781eb7d9ae3abad631bfc4c7487279eadbcef4a8
Do NOT remove the smart card from the reader yet.
Creating CA keys and signer certificates...done.
Generating server private key...
done.
You may now remove the smart card from the reader.
Creating and signing the server certificates...
done.
CA and Server certificates have been generated successfully.
JBoss vault keystore password have been completed successfully.
Self test in progress: passed
SUCCESS: The CA and security certificates are re-generated and the Security Server software
is restarted.
00053:system$
The DSM appliance is now ready to use with the new Security World. For procedures to restore a backup of your
previous configuration, refer to the
DSM Administrators Guide
.
CAUTION
Restoring a backup of the previous configuration will restore the old Security World
and the new one just created will be destroyed.
Chassis Issues
If the Chassis intrusion message indicates that the unit’s lid is open, try the following solutions:
In the CLI, try to clear the chassis intrusion:
1. Log on to the CLI menu for the DSM.
2. Change to the IPMI menu, type:
$ IPMI
3. Use the Clear IPMI chassis intrusion command, type:
$ clearint
4. If you are logged into the system with root access and you are not in the CLI menu, type:
# /usr/sbin/sdt -r "chassis intrusion”
Alternatively, from the IPMI GUI:
1. Navigate to
server health > sensor reading
.
2. Change the category to
Physical Security
.