Changing Cisco Presence SIP and DNS Domain

I’ve had to go through the process of changing the DNS and SIP Proxy domains on all of our IM&P. Sifting through the documentation can be a bit daunting/confusing. Here is a quick bullet point list on how to go about that exercise. If you are only wanting to change the DNS domain simply skip the step to change the SIP domain.

 

  • Add DNS Records and remove or disable old DNS entries
  • Verify dns from CLI (“utils network host [hostname]” and “utils network host [ip-address]”)
  • Disable HA
  • Delete any inter-cluster peers (“Presence > Inter-Clustering”)
  • Run the following commands from CLI on both Servers: utils service stop Cisco Config Agent
    utils service stop Cisco Intercluster Sync Agent
    utils service stop Cisco Client Profile Agent
    utils service stop Cisco Presence Engine
    utils service stop Cisco OAM Agent
    utils service stop Cisco SIP Proxy
    utils service stop Cisco Sync Agent
    utils service stop Cisco XCP Router
    utils service stop Cisco Presence Datastore
    utils service stop Cisco SIP Registration Datastore
    utils service stop Cisco Login Datastore
    utils service stop Cisco Route Datastore
    utils service stop Cisco XCP Config Manager
  • Change the IM and Presence Domain to newdomain.com (“System > Cluster Topology > Settings”)
  • Update the Node Name from each server to the new FQDN (“System > Cluster Topology” – Select Subcluster and then the node to be changed.)
  • In CUCM Change the application server names to reflect the new FQDN (“System > Application Server”)
  • Change the DNS Domain from the CLI on both servers (“set network domain [new.domain]”)
  • Reboot Pub and wait for all services to start – this can take 30min to an hour (verify services with “utils service list”)
  • Reboot Sub and wait for all services to start – this can take 30min to an hour (verify services with “utils service list”)
  • Verify new domain setting on both servers (“show network eth0”)
  • Reset database replication from pub (“utils dbreplication reset all”)
  • Verify replication re-establishes (“utils dbreplication runtimestate” and utils dbreplication status)
  • Regenerate Certificates ( OS Administration > Security > Generate New)
  • Reset Tomcat on both servers (“utils service reset Cisco Tomcat”)
  • Re-Enable HA (“System > Cluster Topology > Select Subcluster”)
  • Add Inter-Cluster Peer (Presence > Inter-Clustering > New”) Reset any needed services
  • Test Client Connectivity with new server settings ( Should work with server set to Automatic if proper SRV DNS records are deployed)
Advertisements