Remanaging a chassis after unmanaging

When the unmanage operation completes, managed endpoints and IBM® Flex System Manager management software information about the endpoints are removed, but endpoint data external to the management node (like the images in the image repository) remain. After you unmanage a chassis, use this information to remanage it and restore remaining endpoint data in the management software.

When you unmanage a chassis, the management software deletes information related to the chassis and its virtual and physical managed endpoints. Any data related to these endpoints that was manually entered and existed only in the management software might need to be re-entered after remanaging the chassis. For example, if you changed the names of endpoints prior to unmanaging the chassis, those names are removed after the chassis is unmanaged.

However, data that is external to the management software is not deleted during an unmanage operation, but the management software might not display it after the initial remanage. If you set up an image repository, then unmanaged and remanaged the chassis, the management software might not recognize the image repository initially, but the actual repository on disk and the images it contains still exist. You can configure the management software to recognize them again.

To remanage the chassis and restore chassis endpoint data that was not deleted during the unmanage operation, use the following information that is applicable to your environment:

Select the chassis and manage it from the Management Domain page. See Selecting chassis for management for more information.
After the chassis is managed on the Management Domain page, allow the management software to finish discovering the components in the remanaged chassis.
Note: Even after the chassis endpoints are discovered, some endpoints might not be fully accessed or configured, and some endpoints might not be displayed at all. See Configuring chassis components for a description of the component-configuration options that are available in the management software.
Resolve error or warning conditions for managed endpoints, if applicable:
- See Access state problems for information about how to correct an access state that is problematic (any access state other than OK).
- See Certificate for a managed compute node is not trusted if a compute node is displayed with the trust state Not Trusted.
- See Connectivity problems if the management software cannot communicate with a managed endpoint.
- See Flex System Manager Types 7955, 8731, and 8734 Software error messages for descriptions of the error messages that can appear in the event logs for the management node.
Important: All error or warning conditions must be resolved before you proceed to the next step.
If you created an image repository for use with VMControl prior to unmanaging the chassis, and it is not displayed in the management software, see Image repository problems.
Note: If you complete the corrective action that is described in "Image repository problems", IBM Power Systems virtual server endpoints are also restored, if applicable.
If you use VMware vCenter, you must discover and collect inventory for the vCenter operating system endpoint; then, the VMware virtual servers that existed before the chassis was unmanaged are restored.