
Common Configuration
# P0602477 Ver: 3.1.11 Page 193
• The following examples are not meant to construe limitations
on or required use of ZAP or any of its options either
individually or in combination.
• Each example assumes that synchronization occurs for all
active instances of the files dtmf.mmi and dtmf.mmd
residing on all MPS’ configured in the vpshosts file of the
reference node, and that no zap.network.cfg files exist
(see Advanced Implementation (High Volume/Traffic) on page
181).
Examples: zap /mmf/peri/dtmf
Synchronization operation begins immediately.
zap -A -C /mmf/peri/dtmf
Generates an alarm upon completion of synchronization on each
MPS and consolidates all related individual log files.
zap -d 11 -r 7 /mmf/peri/dtmf
If a synchronization fails, ZAP waits 11 minutes before retrying,
up to a maximum of 7 times.
zap -t 11pm /mmf/peri/dtmf
The synchronization operation takes place either today or
tomorrow, whenever 11 p.m. occurs next.
zap -t 5am march 11 /mmf/peri/dtmf
The synchronization operation takes place on March 11 at 5 a.m.
zap -L -m /home/run/ball /mmf/peri/dtmf
Synchronization occurs from the local node across the network
by using the MAC file named ball located in the directory
/home/run.
zap [ -A -C
-d <delay> -e <@ EAP# | "Element Name">
-E <filename> -f <alt_file> -G <group#> -L
-m <mac> -n <node> -r <retries>
-t <time> -v <mps#> ] <mmf_name>
Comentarios a estos manuales