1. Home
  2. Day-to-day Administration
  3. How do I migrate the cmd config to a new install?

How do I migrate the cmd config to a new install?

This article is being updated. Please be aware the content herein, not limited to version numbers and slight syntax changes, may not match the output from the most recent versions of Bright. This notation will be removed when the content has been updated.

Requirements

  • The existing and new installation must run the same major version of Bright Cluster Manager.
  • These instructions will work for Bright 7.3 and < 8.2

Steps

Export the existing cmd configuration:
# service cmd stop; cmd -x /tmp/current-config.xml

Import the configs to the new installation:
# service cmd stop; cmd -i /tmp/current-config.xml; service cmd start

  • For versions greater than 8.2, XMLhas been replaced with JSON

Export the existing cmd configuration:
# service cmd stop; cmd -x json:/tmp/current-config

Import the configs to the new installation:
# service cmd stop; cmd -i json:/tmp/current-config; service cmd start

Please note that CMD and licenses are tied to the headnodes device MAC address configuration. The following may wish to be adjusted prior to the import on the new headnode.

Example:

# pwd
/tmp/current-config/device
# cat headnode.json | grep mac
  "mac": "FA:16:3E:42:A0:A9",

This answer explains how users can be migrated.

Updated on March 7, 2022

Related Articles

Leave a Comment