You need to register a Symantec Security Information Manager (SSIM) appliance to itself or to another SSIM appliance
The easiest way to accomplish this is to Secure Shell (SSH) into the SSIM. Login as db2admin and run the two commands below.
Answer the questions prompted. Clarification of these questions are;
Enter external SESA directory ip/hostname and press [ENTER]: <this is the SSIM you want to register too. If you are registering to itself enter its own IP/hostname>
Enter external SESA directory port (636) and press [ENTER]: <this the default port, do not change this unless you know it was changed during setup>
Enter external SESA domain username (administrator) and press [ENTER]: <by default this is administrator, do not change this unless you know it was changed. See NOTE below if you just restored an LDAP backup.>
Enter external SESA domain password and press [ENTER]: < This is the administrator account password. Usually the same password as in question 3, but see NOTE below if you just restored an LDAP backup.>
Enter external SESA directory domain (Symantec.SES) and press [ENTER]: < by default this is Symantec.SES but is almost always changed during install>
Enter external Directory Administrator password and press [ENTER]: <It is the password of the ldap admin account. the user by default is cn=root >
Enter the local SESA database user (symcmgmt) and press [ENTER]: < Just hit enter, this is not changed >
Enter the local SESA database user password and press [ENTER]: <this password is the password used during installation.>
Also please note that the simserver service must be running if you are trying to register the SSIM to itself.
I you have any problem during the registration, you can check the following log file:/opt/Symantec/simserver/logs/dirreg.log' because dirreg.log file is created while directory registration and we can find the errors here if any.
NOTE: If you just restored an LDAP backup and are re-registering due to LDAP connection issues , the SESA domain username and password can be different than the local administrator account and it's password. (This would also be the case if that username and/or password were changed manually.) In this case use the credentials for that account that would have been imported by the LDAP backup (or that they were changed to).
Imported Document ID: TECH148370
Subscribing will provide email updates when this Article is updated. Login is required.