
Avaya Media Processing Server Series System Reference Manual
Page 274 # P0602477 Ver: 3.1.11
Installation and Configuration
Create the Secondary Node
The secondary node must have all standard software packages installed to make a
fully functioning MPS (PERIfw, PERIglobl, PERItms, PERImps, etc.). The secondary
node must also have the same number of MPS components installed as the highest
populated primary node. For example, if the largest primary node has four MPS
components, the secondary node must also have four MPS components installed.
After installing all software packages and associated patches, run the script
config_redundant_node.pl to convert the node to a secondary node.
Make sure all Avaya services are not running.
perl $MPSHOME/bin/config_redundant_node.pl
This script performs the following:
• Renames $MPSHOME/common to $MPSHOME/common.standby and
replaces gen.cfg with “minimal” gen.cfg that sets RCD to run in
standby mode. The original gen.cfg is moved to gen.cfg.bak.
• Renames each local component directory $MPSHOME/mpsN to
$MPSHOME/mpsN.standby, replaces vos.cfg with “minimal”
vos.cfg that starts only TCAD and TRIP in standby mode, and removes
ase.cfg and aseLines.cfg. All old configuration files are stored in the
files with .bak extension.
•Creates $MPSHOME/mps0.empty directory.
TMSCOMM Component Configuration
For information about configuring the TMSCOMM component, refer to:
• The MPSHOME/common/etc Directory on page 88.
• The MPSHOME/tmscommN Directory on page 138.
• Configuring the MPS Application Processor in Chapter 3 of Installing MPS
Software on the Solaris Platform.
Comentarios a estos manuales