
Avaya Media Processing Server Series System Reference Manual
Page 184 # P0602477 Ver: 3.1.11
Using Multiple zap.network.cfg Files
In general the zap.network.cfg file exists only on the reference node. This
requires that the initial update for each group travel over network pathways. If slow or
ineffective links exist within these paths, overall system performance can be adversely
affected. To circumvent these deficient links, additional zap.network.cfg files
are defined on the remote nodes.
The additional zap.network.cfg files must be defined differently from those on
the reference node. If the remote nodes contain the exact same file as that of the
reference node, ZAP behaves the same way as if the additional configuration files did
not exist.
This functionality is illustrated in the following example. The network topography
contains three LANs with two slow links between them.
In this example there are two zap.network.cfg files: one is located on nodeA,
the reference node, and the other on nodeD, nodeE, and nodeF. There is no file on
the remaining nodes. (This format should not be construed as a requirement; rather,
further customization can be made by using various file location configurations.) The
files are defined as follows:
nodeA nodeD, nodeE, and nodeF
[GROUP] #reference node
nodeA
nodeB
nodeC
[GROUP]
nodeD
nodeE
nodeF
nodeG
nodeH
nodeJ
[GROUP] #secondary zap file
nodeD
nodeE
nodeF
[GROUP] #other group
nodeG
nodeH
nodeJ
nodeA
(reference node)
nodeB
nodeC
Ethernet
nodeD
nodeE
nodeF
Ethernet
nodeG
nodeH
nodeJ
Ethernet
Slow Link
Slow Link
Comentarios a estos manuales