Recovering a Chassis Management Module (CMM) after removing the management node

Use the following procedure to recover and configure a Chassis Management Module (CMM) only if you removed the Flex System Manager Types 7955, 8731, and 8734 hardware without first unmanaging the Chassis Management Module (CMM) on the Management Domain page.

Procedure

  1. Through an SSH session, open a CMM command-line interface and log in with the RECOVERY_ID account.
    Note: The password for the RECOVERY_ID account was set when you selected the chassis for management on the Management Domain page. If this is the first time that you have used the RECOVERY_ID account to log in to the CMM, you must change the password.
  2. If you are prompted, type the new password for the RECOVERY_ID account.
  3. Run the following five commands, in the order shown:
    1. env -T mm[p]
    2. sslcfg -client disabled -tc1 remove
    3. accseccfg -am local
    4. ldapcfg -i1 -p1 -rd "" -usa "" -gsa "" -lpa ""
    5. fsmcm -off

      For more information, see fsmcm command in the CMM documentation. This command disables centralized user account management from the IBM® Flex System Manager management software, and allows you to use local CMM user accounts to authenticate to the CMM and any management processor that is installed in the chassis.

      After you run the fsmcm -off command, the RECOVERY_ID account is removed from the CMM user registry. You can now authenticate to the CMM and other chassis components with local CMM credentials.

  4. Make sure that local registry is included in the CMM user authentication options by using the CMM users command (see Management software user registry for more information about user registries). You can choose remote, local, remote then local, or local then remote. After the management node is removed, you must log in to the CMM using one of the IDs from the CMM local registry; then, either set the user authentication to use local or point to another external or remote user repository.
  5. Verify that Electronic Service Agent™ (ESA) is configured properly. The CMM will not allow service requests to be made if it is being managed by the management software. After the management node is removed, the CMM will initiate the service request.
  6. Check the location settings of the NTP server. If you removed the management node without first unmanaging the CMM, you must access the CMM and specify a different NTP server by using either the CMM web interface or the ntp CLI command (see ntp command for more information).
  7. Verify the security policy on the CMM. There are several security settings on the CMM (for example, secured servers and account authentication). The security policy that was implemented on the management node remains on the CMM after the management node is removed. If necessary, you can log in to the CMM and change the security settings by using either the CMM web interface or the security CLI command (see security command for more information).