
Avaya Media Processing Server Series System Reference Manual
Page 280 # P0602477 Ver: 3.1.11
First Startup After Configuration
After the cluster is properly configured and after initial startup, copy the configuration
of all primary nodes to the secondary node:
1. Start up all primary nodes in the cluster. They all must have RCD in their
common component.
2. Setup standby configuration on the secondary node by running the script
setstandby.pl:
perl $MPSHOME/bin/setstandby.pl
Note that on node reboot, this script is automatically run by the
/etc/rc3.d/S17mps.setstandby script.
3. Start SRP on the secondary node. All TRIPs and TCADs should enter the
standby state.
If automatic configuration synchronization is enabled (e.g., the
syncInterval option is set to non-zero), configuration will be
automatically copied from all primary nodes. The first configuration
synchronization is completed when the "Auto Sync Count" field in the
RCD status report increments to non-zero.
If automatic configuration synchronization is disabled (e.g., the
syncInterval option is set to zero), use rcd sync to initiate
configuration synchronization:
vsh> rcd sync all
To monitor the synchronization, enable the rcdu_updates debug
object before using the sync command:
vsh> rcd dlogD/jointfilesconvert/93335/bgOn display,rcdu_updates
The format of the debug records is:
<code> <filename> <optional_text>
where code is one of:
x - File does not exist and will be copied from the primary node
e - Error checking file modification time
s - File exists but is outdated and will be copied from the primary node
- - File exists and is up to date
After the sync command completes, all primary configurations are replicated on the
secondary node and it is ready for failovers. Use the srp -status and rcd
status commands to monitor the status of failover.
Comentarios a estos manuales