Re-managing a CMM after restoring its configuration
Use this information to return a CMM to an externally managed state after restoring its configuration.
When a CMM is managed by an external management device, user management for CMM accounts is performed by that management device. User accounts and certificates on the CMM are locked, and the necessary management certificates are not included in the CMM backup image, which will cause communications between the management device and the CMM to fail.
After a CMM is restored from a saved configuration, you must re-enable the CMM to be managed by an external management device. Complete the following steps to return the CMM to a managed state after restoring its configuration:
- Restore the saved CMM configuration (see Restoring a saved CMM configuration).
- If you are using a backup image that was created while the CMM was in an unmanaged state, go to step 4.
- If you are using a CMM configuration backup that was created while the CMM was in a managed state, complete the following steps to re-initializing the management certificates:
- Access the CMM CLI via SSH, using the Recovery ID and password from the management device.
- Set the primary CMM as the command target using the env -t mm[p] command (see env command for information about command use).
- Disable centralized management using the fsmcm -off command (see fsmcm command for information about command use). The SSH session will end immediately, as disabling centralized management deletes the Recovery ID from the CMM.
- Access the CMM CLI via SSH using the CMM restore password; then, change the password as required during initial login.
- Re-manage the CMM using the external management device. See the documentation for your management device for instructions.
Give documentation feedback