
Configuration Procedures and Considerations
# P0602477 Ver: 3.1.11 Page 269
Directory Layout on a Secondary (Backup) Node
The secondary node contains standby configurations for local components in the
directories $MPSHOME/mpsN.standby and $MPSHOME/common.standby.
Standby configuration starts a minimal number of processes needed to maintain the
system in the standby mode. MPS components contain only TRIP and TCAD
processes.
The secondary node also stores copies of all remote common and MPS components in
a cluster. MPS component configurations are stored in $MPSHOME/mpsN directories
where N is the ID number of the primary component. Common component
configurations are stored in $MPSHOME/common.<nodename> directories where
nodename is the hostname of a primary node. Miscellaneous files from any particular
node are stored in $MPSHOME/miscfiles.<nodename> directories. Media files
for a particular component are stored in $MEDIAFILEHOME/mpsN directories.
Symbolic links $MPSHOME/common and $MPSHOME/mpsN determine current
configuration of the secondary node. If they point to standby configuration directories,
the node is in the standby mode. If they point to copies of primary components, the
node is in the active mode.
Table 1: Sample Secondary Node MEDIAFILEHOME Directory Layout
(Standby or Active)
(in $MEDIAFILEHOME/)
mps1/digitTable /* Will contain dtmf.mmd and
dtmf.mmi */
mps1/system /* All System wide MMFs for MPS1
will be in this dir */
mps1/system/record /* The system wide record MMF file
for MPS 1 goes in this directory */
mps1/appname1 /* All MMFs specific to appname1
will be in this dir */
mps1/appname1/record /* The appname1 specific record file
goes in this dir */
. . .
. . .
. . .
mps1/appnameN /* All MMFs specific to appnameN
will be in this dir */
mps1/appnameN/record /* The appnameN specific record file
goes in this dir */
mps2/…. /* SAME AS MPS1 */
mps3/…. /* SAME AS MPS1 */
mps4/…. /* SAME AS MPS1 */
Comentarios a estos manuales