The workaround is to create a new certificate using IP address, not hostname before the change of hostname takes place.
Follow the steps below when changing the hostname and creating the certificate before the appliance reboots:
- Generate a new certificate using ip address, not hostname
- Appliance will reboot itself and use the new certificate from now on. Check the new certificate to ensure common name is ip address now.
- Change the hostname from either web management interface or ssh session using simuser account.
- After the reboot, check if console and client are not accessible with “ldap server is unavailable”. If not, follow the next step.
- After the reboot, ssh into the console then run “sesa-setup” again with the new hostname. (sesa-setup –ldap-ip new_hostname –ldap-port 636 –ldap-user administrator –ldap-domain Symantec.ses –db-user symcmgmt –reg-external)
If you have already changed the hostname and rebooted:
- Using DRAC or an ssh session login to the appliance as simuser, if you have already logged as db2admin then type the following:
$ su - simuser
- You will then see the following menu:
***************************************
YOU CAN DO THE FOLLOWING IN THIS SHELL:
****************************************
1) View Network Configuration
2) Modify Network Configuration
3) Modify Speed and Duplex mode for Network Interface
4) Change Unix Password for simuser account
5) Verify Network Connectivity
6) Change Time/Locale Information
7) Generate Self-Signed Certificate
8) Display SSIM Version
9) Logout
Selection:
Select option 7 and create a new certificate.