Considerations and steps must be completed before you install system
maintenance.
Before you begin
You must be assigned Hardware administration (Full permission) and hardware resource level administration permission.
About this task
Before you install system maintenance, disable Service and Support Manager (Call Home), obtain the IP addresses of the
Platform System Managers, and check the status of system
components.
Note: It is recommended that you upgrade
Cloud Pak System Software workload environments to
Version 2.3.2.0 before upgrading to
Cloud Pak System
Version 2.3.2.0 and attaching IPv4 addresses
to compute nodes. If the
Cloud Pak System Software workload environment is
upgraded to
Version 2.3.2.0 first, the only
requirement after the compute nodes are assigned IPv4 addresses is to rediscover compute nodes in
the workload environment.
When you do not upgrade the Cloud Pak System Software workload environment first, the compute nodes with IPv4
addresses display as new compute nodes upon discovery.
The block storage replication relationship between volumes might stop during a
software update in
IBM® Cloud Pak Software. As a
best practice, refer the following information.
- Metro Mirror and Global Mirror relationships
- When you update software on a system that has secondary volumes of running Metro Mirror or
Global Mirror relationships, write performance might be degraded on the primary volumes, and Global
Mirror relationships can be automatically stopped with one or more errors with error code 1920. You
might want to proactively stop such relationships before you update the software to avoid the write
performance degradation, and restart the relationships after the update completes.
Procedure
- Log in to the system with a user account
that has Hardware administration (Full permission) and hardware resource level administration permission.
-
Disable Service and Support Manager (Call Home) to prevent cases 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 page. For more information, see
.
-
From the 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.
- Identify the leader Platform System Manager and
collect the IP address of each management node.
-
Log in to the
console, and click .
- 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.
- Record the IP addresses of the leader and non-leader Platform System Managers.
Click and expand the System
Management IP section to locate the IP addresses for each
management node.
- 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.
Resolve any major issues before you proceed.
- 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.
- Validate the configuration of the external Installation
Manager repository.
- From the console, click .
- From the System Plug-ins page, click the drop down menu and select All in
the pattern type drop down list.
- Type
vsys.im
in the Filter field
to display a list of vsys.im plug-ins.
- Click the plug-in with the last version number to open the details
page.
- 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.
- If connection fails, click Config to open
the external repository configuration page.
- Confirm that the External Repository URL, User
ID, and Password fields are correct
and click Update to save the configuration
details.
- 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.
What to do next
Upload the system maintenance fix pack IFP file.