Lists of servers and chassis are incorrect after user credentials change - IBM System x, BladeCenter, Flex System
RETAIN tip: H21700
Configuration Patterns does not function properly after the authorization status of the user account is changed.
Such changes include the account becoming locked, the password expiring, and the password being changed. Resolving the authorization issue does not fix Configuration Patterns. The time it takes after such a change for symptoms to appear varies. Symptoms include the following:
The system is configured with at least one of the following:
This tip is not system specific.
This tip is not option specific.
Note: This does not imply that the network operating system will work under all combinations of hardware and software.
Please see the compatibility page for more information: http://www.ibm.com/systems/info/x86servers/serverproven/compat/us/
This behavior will be corrected in a future release of IBM Flex System Manager (FSM) - Configuration Patterns distributed as part of the FSM update package.
The target date for this release is scheduled for fourth quarter 2013.
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:
Restart the Flex System Manager (FSM). Configuration Patterns will start to use the updated account credentials and will function normally.
A security token is cached by Configuration Patterns and is used after a successful internal call to get inventory information from FSM. Even after the credentials change, that same security token is used by Configuration Patterns, causing the internal call to fail.
Restarting the FSM causes Configuration Patterns to re-fetch credentials and use a correct security token, and function properly again. In the noted release, an FSM restart will not be required.
Applicable countries and regions
Document id: MIGR-5093578