This section describes how to migrate the Cluster Manager VM to CPS 18.4.0.
Note |
Diagnostic fails
during migration. This is normal since NTP may be converging, mongo replica
sets are not synced, and so on. If you see HAProxy diagnostics warnings about
Diameter endpoints being down, see
HAProxy Diagnostics Warnings
for a workaround.
|
For VMware based setup, check Configuration.csv under /var/qps/config/deploy/csv/ and confirm whether db_authentication_enabled
parameter is present in the file. For migration to succeed, db_authentication_enabled,FALSE,
must be configured in Configuration.csv file.
-
The migration succeeds:
-
If db_authentication_enabled
is disabled as db_authentication_enabled,FALSE,
OR the parameter is enabled as db_authentication_enabled,TRUE,
-
db_authentication_admin_passwd,<xxxxxxx>,
-
db_authentication_readonly_passwd,<xxxxx>,
-
If the parameter db_authentication_enabled
is not present in the file, you need to configure it as db_authentication_enabled,FALSE,
for migration to succeed.
This is mongo authentication related feature. For more information, see CPS Installation Guide for
VMware.
The following logback files are overwritten with latest files after ISSM. Any modification done to these files, needs to merge
mannually after migration is complete:
/etc/broadhop/logback-debug.xml
/etc/broadhop/logback-netcut.xml
/etc/broadhop/logback-pb.xml
/etc/broadhop/logback.xml
/etc/broadhop/controlcenter/logback.xml
Backup of old logback.xml files is available at /var/tmp/logback_backup on newly deployed Cluster Manager VM after running restore_cluman.py
script. Same files are also available in migrate_cluman_*.tar.gz generated in Step 4.