21. Log onto the WMI of the redundant APM as “admin” and select: “System” tab > “Cluster Settings” > “Heartbeat” tab.The rest of the fields in the form will become active. The default settings for “Fail Over Time,” “Message-Period,” and “Dead Ping Timeout” can remain as they are.This password must be the same as when you entered it in the “Shared Secrets Key” field for the primary APM (step 10.).This is an IP address for the APM web service. It must be a static address and it must be the same IP address used when you configured the Service IP for the primary APM (step 11.).
27. Fill in the “Ping Nodes List” field with IP addresses to ping in order to detect when primary APM has lost connectivity to the network. It is recommended that this field includes the default gateway IP address and the router IP address. Be sure to separate the IP addresses with commas and no spaces.
28. Enter an alias in the “Node Name” field for the redundant APM in the column for the current system.
29. Enter the IP address for the redundant APM in the “IP Address” field in the column for the current system.
30. Enter an alias in the “Node Name” field for the primary APM in the column for the mated system.
31. Enter the IP address for the primary APM in the “IP Address” field in the column for the mated system.
32. You should be able to leave the default settings as they are in the form under the “Synchronization” tab.Caution: All settings for time, synchronization, authentication, and shared secrets must be identical entries for both APMs.
36. Reboot the primary APM and then reboot the redundant APM. This is necessary to activate the heartbeat configuration.Caution: Rebooting the primary and redundant APM will start up the synchronization. The heartbeat, redundancy, data synchronization, and failover support will not be activated until synchronization completes.Check the status of the synchronization by logging onto the console of either APM as root and entering the command:
# /etc/init.d/drbd statusWhen the synchronization of the two APMs is complete, the display be similar to the following:Note: This information can also be viewed from the WMI of either APM. Log onto the WMI as admin, and go to “System” > “Status” > “Sync Status” tab. A screen similar to the following appears:
1. Log onto the WMI of the primary APM as admin and select:
“System” tab > “Cluster Settings” > “Heartbeat” tab > “Status” drop-down box > “Disable”
2. Log onto the WMI of the redundant APM as admin and select:
“System” tab > “Cluster Settings” > “Heartbeat” tab > “Status” drop-down box > “Disable”The heartbeat and network RAID signals will now be stopped. When the APMs reboot, they will be running as individual APMs
4. After the APMs reboot, upgrade the firmware on each APM. See “To Upgrade the APM Firmware” in Chapter 5 of the AlterPath Manager Installation, Configuration, and User’s Guide.Caution: You can mix APM hardware platforms, but you must be sure the APM 5000 has APM 5000 firmware and the APM 2500 has APM 2500 firmware. Both APMs must have firmware of the same build number and date.
6. Log onto the WMI of the primary APM as admin and select:
“System” tab > “Cluster Settings” > “Heartbeat” tab > “Status” drop-down box > “Enable”
7. Log onto the WMI of the redundant APM as admin and select:
“System” tab > “Cluster Settings” > “Heartbeat” tab > “Status” drop-down box > “Enable”
8. Reboot the primary APM and then reboot the secondary APM. This is necessary to activate the heartbeat configuration.Caution: Rebooting the primary and redundant APM will start up the synchronization. The heartbeat, redundancy, data synchronization, and failover support will not be activated until synchronization completes.
# /etc/init.d/drbd status
b. or by logging onto the WMI of either APM as admin and going to “System” > “Status” > “Sync Status” tab.After the synchronization completes, the heartbeat and network RAID signals will start up and the fault tolerant configuration will be active.