Avaya DEFINITY Server CSI Maintenance Manual page 401

save announcements
When MSS devices on both processors in High or Critical Reliability
Systems are specified, the save announcements command saves
announcement data from announcement boards to active MSS devices,
then to standby MSS devices. The system reports the status of each save
operation to users separately. When one save operation fails, the save
operation to another device continues, causing saved announcement data
to be inconsistent between MSS devices.
In case of a failure, technicians make announcement files consistent
across both MSS devices. Files become inconsistent due to hardware
failures or spontaneous processor interchanges. If announcement files are
inconsistent due to hardware failures that occur during save
announcements, error messages display indicating corrective action.
Maintenance software that monitors hardware logs hardware errors to
maintenance. Then, maintenance software invoke tests to diagnose and
attempt corrective action. If maintenance software fails to correct the
problem, an alarm raises displaying corrective action.
The save announcements command writes two time-stamped, identical
copies of announcement data to selected devices. The time-stamp for both
copies is the same. Each copy contains a timestamp and the state of the
copy (good or bad).
If good copies of announcement files are not available, the restore
announcements command cannot execute until save announcements
completes. Announcements on the board are still usable.
Output
The following example shows the output from save announcements on a
simplex SPE system.
save announcements
Processor Command Completion Status
SPE-A Success
Field descriptions
Processor
Command Completion Status
Error Code
555-233-119
Page 1 of 1
SAVE ANNOUNCEMENTS
Displays processors when announcement data writes to
its devices. (spe-a and spe-b)
This field specifies if the command succeeded.
0 = successful save
1 = could not write to active spe device
2 = could not write to standby spe device
SPE A
Error Code
0
Issue 5 October 2002
401