Installing service for System Automation for Multiplatforms
Installing service means upgrading System Automation for Multiplatforms from release 4.1. Therefore, release 4.1 must be installed before any service can be applied.
- Product fix packs are always cumulative.
- You must have root authority to install a product fix pack.
- When you downloaded the archives from the System Automation for Multiplatforms support site (see Obtaining fix packs), unpack the product fix pack archive to a temporary directory. For information about how to unpack the archive for your operating system, see Usage instructions for platform-specific archives.
- Back up your system configuration before you install the service fix pack. For more information, see Managing XML automation policies.
- To minimize downtime, you can run a prerequisites check before you start the installation. For more information, see Checking prerequisites.
-
Check whether any resources are online on the node you want to service:
- If resources are online and must be kept available, exclude the node from
automation:
System Automation for Multiplatforms stops the resources on the node and, if possible, restarts them on a different node in the peer domain.samctrl -u a <node>
- If the resources need not to be kept available during service, bring the resource groups offline.
- If resources are online and must be kept available, exclude the node from
automation:
-
Stop the node from another node in the domain, and verify that it is stopped:
stoprpnode <node>; lsrpnode
-
After you received the archives, extract them. They create a directory structure with root directory SAM41
mf
MP, wheremf
stands for modification level and fix level. -
Install the service fix pack with the
installSAM
script. For detailed information about the script, refer to Running the installation. - Start the node:
startrpnode <node>
- If you excluded the node in step 2, include the node to the
automation:
samctrl -u d <node>
-
If you require the resource groups to be online, bring the resource groups online. Otherwise, delay this step until the last node in the peer domain is serviced.
-
After all nodes are serviced, run the steps that are described in Completing the migration. The changes become effective in the entire domain and the correct version is shown.