Enable FIPS mode for the NetBackup Authentication Broker service
The NetBackup Authentication Broker (nbatd) service runs only on the NetBackup primary server, therefore you need to enable FIPS mode on the primary server to enable it for the nbatd service.
FIPS mode is disabled by default.
Note:
From version 10.5 and later, for Cloud Scale deployment, the nbatd containerized service is running in a separate Kubernetes Pod cluster server rather than the NetBackup primary server Pod. To enable the FIPS mode for the NetBackup Authentication Broker service, execute the same steps on the nbatd containerized service mentioned in the section Enable FIPS mode for the NetBackup Authentication Broker service.
To enable FIPS mode for the nbatd service or the nbatd containerized service
- Open the following directory on the primary server:
On UNIX: /usr/openv/netbackup/sec/at/bin/
On Windows: install_path\NetBackup\sec\at\bin\
- Run the following command:
On UNIX: run vssregctl -s -f /usr/openv/var/global/vxss/eab/data/root/.VRTSat/profile/VRTSatlocal.conf -b "Security\Authentication\Client" -k FipsMode -t int -v 1
On Windows: run vssregctl -s -f "install_path\NetBackup\var\global\vxss\eab\data\systemprofile\VRTSatlocal.conf" -b "Security\Authentication\Client" -k FipsMode -t int -v 1
For example:
If the install_path is "C:\Program Files\VERITAS" location, run the following command on Windows:
vssregctl -s -f "C:\Program Files\VERITAS\NetBackup\var\global\vxss\eab\data\systemprofile\VRTSatlocal.conf" -b "Security\Authentication\Client" -k FipsMode -t int -v 1 3
Check the nbatd logs.
Location of the nbatd logs:
On UNIX:
/usr/openv/logs/nbatd
On Windows:
install_path\NetBackup\logs\nbatd
The following log lines should be present:
*** Trying to start Broker In FIPS mode ***
*** Broker In FIPS mode already ***
- Restart the NetBackup services.