The following topic describes how to install the Fix Pack in a high availability cluster deployment.
When installing the Fix Pack in a high availability cluster environment, install the Fix Pack only on the primary (active) cluster node.
You do not require to install the Fix Pack on the secondary (standby) cluster node. After the Fix Pack installation completes on the primary cluster node, the appropriate files are updated on the secondary cluster node.
install.cmd -J INSTALL_TYPE=PRIMARY
pw system start
hostname <logicalHostName>
hostname <primaryHostName>
In the OS-level high availability (HA) mode, you must install the Fix Pack for the BMC ProactiveNet Integration Service on both primary and secondary servers.
Note
Log on to the virtual node (assuming that the cluster service is started on both the primary and secondary servers).
Access the BPPMAgent\Windows folder and extract the contents of the BPPMAgent file. From the extracted BPPMAgent folder, access the Disk1 folder.
install.cmd -J INSTALL_TYPE=PRIMARY
Log on to the virtual node (assuming that the cluster service is started on both the primary and secondary servers).
Access the BPPMAgent\Windows folder and extract the contents of the BPPMAgent file. From the extracted BPPMAgent folder, access the Disk1 folder.
Generate the options file from the primary server installation log and modify the value of INSTALL_TYPE=PRIMARY
to INSTALL_TYPE=SECONDARY
.
Run the following command:
install.cmd -DOPTIONS_FILE=<options file generated using primary install log>
install.cmd -i silent -DOPTIONS_FILE=<options file generated using primary install log>
The installation is performed on the shared drive.
After the Integration Service is installed on both the primary and secondary servers, a “ProNetAgent” resource is created on the cluster.
If this resource is not created automatically, you may receive warnings. To create the resource, perform the following steps:
Go to the <installation directory>\Agent directory and execute the following file:
(Windows Server 2008) GenericService.bat
(Windows Server 2012) GenericService.ps1
Execute the following command with the Run as administrator option to enable the ProNetAgent cluster resource:
(Windows Server 2008)
(Windows Server 2012) cluster.exe resource
ProNetAgent
/ONLINE /WAIT:
5
00
powershell.exe Start-ClusterResource -Name
-Wait 500ProNetAgent
Stop the BMC ProactiveNet Integration Service using Services.msc.
Go to Start > All Programs > Administrative Tools > Failover Cluster Manager and click on the cluster name.
Click the Dependencies tab in the ProNetAgent Properties window and click Insert to add a resource.
Restart the BMC ProactiveNet Integration Service using Services.msc.
Perform the following steps on the secondary node to start or stop the cell automatically during failover:
Go to the <installation directory>\Agent directory and make a copy of the following file:
(Windows Server 2008) GenericService.bat
(Windows Server 2012) GenericService.ps1
Edit the copied file:
Replace the cluster resource value from "ProNetAgent" to"ProNetCell".
Modify the ServiceName value from "ProNetAgent" to the Cell service name (you can obtain the cell service name from services.msc).
Execute the modified file with the Run as administrator option to create the new cluster resource as "ProNetCell".
Create the similar dependencies for ProNetCell as of ProNetAgent.
Execute the following command with the Run as administrator option to enable the ProNetCell cluster resource:
(Windows Server 2008)
(Windows Server 2012)cluster.exe resource
ProNetCell
/ONLINE /WAIT:
5
00
powershell.exe Start-ClusterResource -Name
-Wait 500ProNetCell
mgetinfo -n <cell name> -v activity
Install the Fix Pack on the Integration Services. For more information, see Installing or upgrading the remote Integration Service and remote cell.