@Ayyavaru Typically there is no external steps needed from CM side as CM only needs DB to be up so it depends on your plan honestly. However I would suggest you to take BACKUP of CM database for safe side [1] as well as plan downtime for this activity. You can use mysqldump to back up databases without having to shut them database down (see https://dev.mysql.com/doc/refman/5.7/en/mysqldump-sql-format.html). However, to ensure you get a good back, you should make sure there is no activity. i.e. you can get the back up by stopping the Cloudera manager server or any service for the database you are backing up. We strongly encourage that you consult your DBA or database vendor. After that you have to check the db.properties is rightly pointed to the database configured for CM. Hope this helps.  [1]https://docs.cloudera.com/documentation/enterprise/latest/topics/cm_ag_backup_dbs.html#concept_tyh_rmq_bl ... View more

@Pottie As per my you just have to install the krb packages on the new host rest will be fine and will be taken care by itself while adding host.  ... View more

Thanks for the reply, @GangWar.    The issue is sorted out now. As you said, the issue got fixed after checking the config.ini. The  inter communications between the client and server were made to do over TLS, but we disabled the TLS/SSL in UI and for all agents. This was the main cause, as the heartbeat tried to get a response, but it didnt. Changing the configuration in Cloudera Manager -> Administration -> “Use TLS Encryption for Agents” should be unchecked, and restarting the Cloudera Manager fixed the issue.  ... View more