Preparing to install system maintenance

Considerations and steps must be completed before you install system maintenance.

1. Log in to the system with a user account that has Hardware administration (Full permission) and hardware resource level administration permission.
2. Disable Service and Support Manager (Call Home) to prevent PMRs from being automatically opened during the system maintenance process. Select the Do not collect troubleshooting information and do not open a service request. option from the Service and Support Manager section on the System > System Settings page. For more information, see .
3. From the System > Backup and Restore page, confirm whether or not the system has a backup scheduled. If the system does have a backup scheduled, plan maintenance around the backup schedule or stop the backup job to allow maintenance to complete. Restart the backup job upon maintenance completion.
4. Identify the leader Platform System Manager and collect the IP address of each management node.
   1. Log in to the console, and click Hardware > Management Nodes.
   2. Identify the leader Platform System Manager. The leader is identified as Platform System Manager - Primary when you hover over the management node icon with the green check to the left of the management node name.
   3. Record the IP addresses of the leader and non-leader Platform System Managers. Click System > Network Configuration and expand the System Management IP section to locate the IP addresses for each management node.
5. Follow the steps in this technote to perform a Lite Health Check and Full Health Check on the system: Health Checks and Introduction to Troubleshooting on a Cloud Pak System Software.

   Resolve any major issues before you proceed.

6. Ask the Workload resources administrator to log in to the console and check the status of the virtual images, virtual patterns, and deployed instances. Ensure that no deployment errors or blank pages are displayed. If you see an error, make sure that it is accounted for and is not associated with the upgrade.
   • Use the Catalog menu to check the status of your virtual images and verify the content to confirm that the expected images are there.
   • Use the Patterns menu to check the status of your virtual patterns and virtual machines and verify the content to confirm that the expected virtual patterns and virtual machines are there.
7. Validate the configuration of the external Installation Manager repository.
   1. From the console, click Catalog > System Plug-ins.
   2. From the System Plug-ins page, click the drop down menu and select All in the pattern type drop down list.
   3. Type vsys.im in the Filter field to display a list of vsys.im plug-ins.
   4. Click the plug-in with the last version number to open the details page.
   5. Click Test Connection to validate if the external Installation Manager repository connection information is current. The result displays after the test is complete.
      Note: The following message means that the system does not have an external Installation Manager repository configured and it is not treated as a failed case:

      Cannot connect to the external repository due to missing URL.

   6. If connection fails, click Config to open the external repository configuration page.
   7. Confirm that the External Repository URL, User ID, and Password fields are correct and click Update to save the configuration details.
   8. Verify that the external Installation Manager repository will be up and running during the upgrade process.
      • Ensure that the repository server is on the network.
      • If the server is a HTTP server, ensure that the server is up and running.
      Note: If you are unsure of whether or not the external repository will be up and running during system upgrade, remove the configuration temporarily from the system. You can enter it back to the system again after the upgrade process is complete.