Resetting CMM to default causes IMM to not be able to login

Troubleshooting

Problem

Users might fail to login to the Integrated Management Module (IMM) when a 'reset to defaults' is issued on the Chassis Management Module (CMM). This occurs only when the cryptomode of the Chassis is set to 'Nist-800 131a', and then a 'reset-to-defaults' on the CMM is issued.

Resolving The Problem

Source

RETAIN tip: H212809

Symptom

Users might fail to login to the Integrated Management Module (IMM) when a 'reset to defaults' is issued on the Chassis Management Module (CMM).

This occurs only when the cryptomode of the Chassis is set to 'Nist-800 131a', and then a 'reset-to-defaults' on the CMM is issued.

Affected configurations

The system can be any of the following IBM servers:

Flex System x220 Compute Node, type 2585, any model
Flex System x220 Compute Node, type 7864, any model
Flex System x220 Compute Node, type 7906, any model

This tip is not software specific.

This tip is not option specific.

The following system firmware level is affected:

Build ID: 1AOO57F

Solution

This behavior will be corrected in a future release of IMM2 Build ID: 1A00XXX (yet to determine what version the fix will be released).

The target date for this release is third quarter 2014.

The file is or will be available by selecting the appropriate Product Group, type of System, Product name, Product machine type, and Operating system on IBM Support's Fix Central web page, at the following URL:

http://www.ibm.com/support/fixcentral/

Workaround

When the 'reset-to-default' is issued on the CMM, the cryptomode is set to 'Nist compatible' on the CMM, and the IMM appears not be set to the same cryptomode, resulting in login failures. Issuing a 'reset-to-defaults' on the IMM from the CMM Command Line Interface (CLI) or Web interface fixes the issue.

Additional information

Because the cryptomode settings are different, the TLS setup needed for LDAP server authentication fails due to non-matching ciphers.

(where TLS = Transport Layer Security, LDAP = Lightweight Directory Access Protocol)

By issuing 'reset-to-defaults' on the IMM, the cryptomode setting is set to match that of the CMM, which will result in the TLS setup session succeeding.

Document Location

Worldwide

Operating System

PureFlex System and Flex System:Operating system independent / None

[{"Type":"HW","Business Unit":{"code":"BU050","label":"BU NOT IDENTIFIED"},"Product":{"code":"QU01GRJ","label":"PureFlex System and Flex System->x220 Compute Node->7906"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"","label":""}},{"Type":"HW","Business Unit":{"code":"BU050","label":"BU NOT IDENTIFIED"},"Product":{"code":"QU91OLT","label":"PureFlex System and Flex System->x220 Compute Node->2585"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Line of Business":{"code":"","label":""}}]

Tips

Resetting CMM to default causes IMM to not be able to login - IBM Flex Systems