This command sets
the domain name for the system.
Changing the domain name triggers an automatic regeneration of all Unified Communications Manager certificates, including
any third party signed certificates that have been uploaded. After the server reboots automatically, phones running in secure
(mixed) mode cannot connect to the server until after the CTL client updates the new CTL file to the phones.
Reboot the servers
one at a time in order for the phones to register correctly. For more
information about changing the domain name, see
IP Address and Hostname for Cisco Unified Communications Manager.
set network domain [domain-name]
the system domain that you want to assign.
The system asks whether you want to continue to execute this command.
If you continue,
this command causes a temporary loss of network connectivity.
If you use the
set network domain
domain-name command to change the domain name, you
must manually regenerate all of your security certificates in Cisco Unified
Operating System Administration. The list of certificates depends on your
software release but may include cup.pem, cup-xmpp.pem, cup-xmpp-s2s.pem,
tomcat, ipsec and so on. Note that you must restart the tomcat service after
the tomcat cert is regenerated and you can only restart this service using the
CLI. For more information about regenerating security certificates, see the
Communications Operating System Administration Guide (on Cisco.com).
you regenerate your security certificates, you must reboot all the servers in
the cluster. This will ensure that database replication keeps working
correctly. After the servers have rebooted, confirm that there are no issues
reported on the Cisco Unified Reporting report for Database Replication. After
you reboot the server, we recommend that you manually delete old certificates
that have become disassociated by the domain name change. For every ICSA peer
that exists on the local node, you must either update the ICSA entry for the
peer node with the new FQDN hostname, or delete that entry and add a new ICSA
peer entry with the new FQDN hostname.