Avaya Media Processing Server Series System (Software Release 2.1) Manual do Utilizador descarregar pdf (Página 181)

Common Configuration

# P0602477 Ver: 3.1.11 Page 181

Advanced Implementation (High Volume/Traffic)

By default, ZAP connects from a local (reference) node to all remote (target) nodes

(see Basic Implementation (Low Volume/Traffic) on page 178). Where multiple

LANs exist, which in turn contain multiple nodes that need to be updated by ZAP,

network traffic is further reduced and performance improved by having ZAP function

on a proxy basis. In this case ZAP updates one MPS for a particular node in a group

(LAN): each of the other MPS’ on this node, and one MPS on each of the other nodes

in the group, are updated remotely from this “locally updated” (proxy) server. This

functionality requires the presence of a user-defined zap.networks.cfg file.

The order of nodes in the zap.networks.cfg file determines the order in which

each node acts as a proxy for its group. Analogously, the order of MPS’ in each node’s

vpshosts file determines the order in which each acts as a proxy for that node. If a

node or MPS is unavailable for any reason, ZAP moves to the next one in the

sequence.

The zap.networks.cfg File

The zap.networks.cfg file must contain every node in the network since this

file is used to determine the topography of the network. If a specific series of MPS’

needs to be updated, the update can be instituted through use of the -f option (see

Individual Group Update Option on page 183).

The most commonly suggested format of the zap.networks.cfg file is to have

each LAN defined as a group; however, other arrangements are also possible,

depending on site requirements. In all cases, the following syntax rules must be

followed:

• Groups are defined by using the term [GROUP] on its own line. All nodes

that follow are construed as belonging to that group until ZAP encounters

another [GROUP] tag or the end of the file.

• Only one node is listed per line, and each node must belong to only one group.

• No empty groups are allowed, and no node can appear ahead of the first

group.

• An pound symbol (#) precedes commented data. This symbol must appear at

the beginning of a line (comments entire line) or have at least one space

before it.

• Blank lines are ignored.

With these rules in mind, a sample zap.networks.cfg file might appear as

follows:

1 2 ... 176 177 178 179 180 181 182 183 184 185 186 ... 305 306

Sem comentários

Avaya Media Processing Server Series System (Software Release 2.1) Manual do Utilizador Página 181