This section provides information about how to revert Sentinel and its components to non-FIPS mode.
You can revert a Sentinel server running in FIPS 140-2 mode to non-FIPS mode only if you have taken a backup of your Sentinel server before converting it to run in FIPS 140-2 mode.
NOTE:When you revert a Sentinel server to non-FIPS mode, you will lose the events, incident data, and configuration changes made to your Sentinel server after converting to run FIPS 140-2 mode. The sentinel system will be restored back to the last restoration point of non-FIPS mode. You should take a backup of the current system before reverting to non-FIPS mode for future use.
To revert your Sentinel server to non-FIPS mode:
Log in to the Sentinel server as the root user.
Switch to the novell user.
Browse to the Sentinel bin directory. The default location is /opt/novell/sentinel/bin.
Run the following command to revert your Sentinel server to non-FIPS mode, and follow the on-screen instructions:
./backup_util.sh -f <backup_file_name.tar.gz> -m 'restore'
For example, if non-fips2013012419111359034887.tar.gz is the backup file, run the following command:
./backup_util.sh -f non-fips2013012419111359034887.tar.gz -m 'restore'
Restart the Sentinel server.
You can revert remote Collector Managers or remote Correlation Engines to non-FIPS mode.
To revert a remote Collector Managers or a remote Correlation Engine to non-FIPS mode:
Login to the remote Collector Manager or remote Correlation Engine system.
Switch to novell user:
su novell
Browse to the bin directory. The default location is /opt/novell/sentinel/bin.
Run the revert_to_nonfips.sh script and follow the on-screen instructions.
Restart the remote Collector Manager or remote Correlation Engine.