You may come across a situation where the newly acquired hosts after installing and configuring Symantec Directory DSAs results in to failure to start.
You have checked everything you can think of (see below example) and still cannot figure out what is causing this.
[dsa@hostname data]$ dxserver -d start <dsaname>
<dsaname> starting
** ALARM **: DSA_E2220 Cannot register address
** ALARM **: DSA_I1240 DSA shutting down
[dsa@hostname data]$ hostname
hostname
[dsa@hostname data]$ hostname -f
hostname.livdmz2.r1.xxx.net
[dsa@hostname data]$ nslookup hostname
Server: 167.xxx.xx.3
Address: 167.xxx.xx.3#53
Name: hostname.livdmz2.r1.xxx.net
Address: 10.xx.xx.29
[dsa@hostname data]$ grep -c "DXserver Administrator" /etc/passwd
0
[dsa@hostname data]$
Release : 14.1
Component : CA Directory
The problem is most probably with the /etc/hosts file that you have on this newly acquired hosts that you are attempting to build and setup.
Make sure the IP address you see with above command(s) in example is present in the /etc/hosts file. If there is a mismatch, the DSA will fail to start with stated error. Adjust your /etc/hosts file accordingly and DSA should start successfully.
Also refer to our product documentation at:
https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/directory/14-1/reference/system-messages-for-ca-directory/dxserver-alarm-messages/error-messages.html#concept.dita_72237dfc69ad1f06e1e5fd62aa5f6eb94dc02d62_DSAE2220Cannotregisteraddress