To configure existing remote Collector Managers and Correlation Engines to communicate with a Sentinel server running in FIPS 140-2 Mode, you can either convert the remote system in FIPS 140-2 mode or you can update the Sentinel server certificate to the remote system and leave the Collector Manager or Correlation Engine in non-FIPS mode. Remote Collector Managers in FIPS mode may not work with event sources that do not support FIPS or that require one of the Sentinel Connectors that are not yet FIPS-enabled.
If you do not plan to enable FIPS 140-2 mode on the remote Collector Manager or Correlation Engine, you must copy the latest Sentinel server certificate to the remote system, so that the Collector Manager or Correlation Engine, can communicate with the Sentinel server.
To update the Sentinel server certificate in the remote Collector Manager or Correlation Engine:
Log in to the remote Collector Manager or Correlation Engine computer.
Switch to novell user (su novell).
Browse to the bin directory. The default location is /opt/novell/sentinel/bin.
Run the updateServerCert.sh script and follow the on-screen instructions.