Flex nodes can be managed by HMC, IVM or FSM. Only one manager type can be active – dual management by FSM and HMC is not supported.
Resolving the problem
Flex POWER nodes are supported as standalone (no Management Console) or with any of the following Management Consoles: IVM, HMC, or FSM.
|Standalone (1)||y||y||n (2)|
(1) If a FSM manages the chassis then it must manage all POWER nodes in the chassis. Dual management with FSM is not supported.
(2) IBM i requires VIOS and one of the supported MCs.
HMC Support for FlexAnnouncement
- HMC Version 7 Release 7.7.0 Service pack 2 (22.214.171.124.2) or a later service pack.
- Firmware 01AF773_033 or higher recommended.
- Supported Combinations
|Version 7 Release 7.7.0||Service Pack 2||Service Pack 3
Note: HMC does not support TLS 1.2 enablement on this firmware level.
|Version 7 Release 7.8.0||Not supported.||*Service Pack 0
|Version 7 Release 7.9.0||Not supported.||Not supported.||*Supported|
|Version 8 Release 8.1.0||Not supported||Not supported||*Supported|
- All power nodes at EC level 01AF773 must either be powered off or concurrently updated to 773.12 (AF773_056) or later
- to the conversion.
- Dual management with FSM is not supported.
- FSM cannot manage any chassis that contains HMC managed POWER nodes.
- Conversion of existing Nodes from FSM to HMC is supported.
- Conversion of existing Nodes from HMC back to FSM is not supported. The partition configuration must be cleared and recreated.
Converting from FSM to HMC
- Prior to the conversion ensure the Flex Node has been powered on to standby state, or Operating state while no virtual servers were configured to auto-start, at least one time since installing node firmware 01AF773. Failure to perform an ipl to standby will result in the node going to incomplete state after the HMC connects. The HMC will not be able to work with or manage the node or any virtual servers.
- The last power on type can be found in
System Configuration > Edit Host > Power on Parameters
- A current value of User-Initiated indicates the last IPL was to standby. A current value of “Auto-Start for Auto-Recovery” indicates that the last ipl was to standby; assuming it was a normal, and not a crash related, power on IPL. If the current value is “Auto-Start Always” then it is not possible to determine if a standby IPL has been performed. The current value of all virtual server’s “Automatically start with managed system” can be checked however it may of been changed since the last power on. The value can be viewed in the GUI using
- the virtual server
Configuration > Manage Virtual Sever
- task. To view the setting for all virtual servers run the command on the target host(s):
- lssyscfg -m <host name> -r lpar -F name,lpar_id,auto_start | grep ,1$
- 1. Use FSM to Un-manage the chassis
- To Unmanage the chassis see the Information Center section “Remove a Chassis”:
- Ensure you also complete the sub-section “Important: Before you unmanage a chassis, make sure that you complete the procedures that are described in Unmanaging a chassis”
- 2. Remove the FSM node
- If the FSM is installed in the same chassis, the FSM node should be removed to prevent rediscovery of the chassis and nodes.
- 3. Add the POWER node to the HMC(s)
- Use the “add managed System” (mksysconn command) to add the POWER node to the HMC(s).
- The password field requires the Flex Node’s password for USERID. The node authenticates against its ldap server which by default for an unmanaged chassis is CMM. If the CMM is configured to use an external LDAP server, the server must have an account of USERID.
- Add the power node to a second HMC if desired. Dual HMCs are supported; both HMCs must be at the same version an release.
- VIOS 126.96.36.199
- Conversion from HMC or FSM to IVM is not supported. The partition configuration must be cleared and recreated.