Avaya Media Processing Server Series System (Software Release 2.1) Manual de usuario Pagina 182

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 306
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 181
Avaya Media Processing Server Series System Reference Manual
Page 182 # P0602477 Ver: 3.1.11
The zap.networks.cfg file must be placed into the
$MPSHOME/common/etc directory. If the file is built so that every LAN is
its own group, only one MPS on one node in each group is updated directly, with the
remainder in that group being updated by this node remotely. Using the sample file
shown above, and given that ZAP was started on nodeA, one MPS on one node in
group 2 and one MPS on one node in group 3 is updated via network traffic; each of
the other nodes in the groups are updated on a localized basis by this initial MPS.
Group 1 contains the local node (nodeA), and so does not require any network-wide
update; instead, all MPS’ in this group are updated by nodeA. Only the MPS’ listed
in the vpshosts file on nodeA are addressed. If any node in any group contains
MPS’ that are not in this file, those servers are not updated.
Though the vpshosts files on remote nodes can in theory have more MPS’ listed
than that on the reference node (these others do not get updated), in practice they
should never have fewer than those of the vpshosts file on the reference node.
# Start of zap.network.cfg file
[GROUP] #Group 1
nodeA
nodeB
nodeC
[GROUP] #Group 2
nodeD
nodeE #this node is in the middle
nodeF
[GROUP] #Group 3
nodeG
nodeH
nodeJ
#EOF
Vista de pagina 181
1 2 ... 177 178 179 180 181 182 183 184 185 186 187 ... 305 306

Comentarios a estos manuales

Sin comentarios