Server Alarms - Avaya Support

Server Alarms
FSY (File Synchronization)
The File Synchronization (FSY) process uses TCP-based communication over 100BaseT
Ethernet links to provide synchronized duplication of critical data files, including translations and
important Linux files.
Note:
Note: This set of files is separate from the data shadowed between each server’s
DAJ1/DAL1/DAL2 (Duplication Memory Board).
Table 13: FSY Alarm in Server describes the FSY alarms and their troubleshooting procedures.
Table 13: FSY Alarm in Server
Event
ID
Alarm
Level
Back to: Linux Server Alarms
Alarm Text, Cause/Description, Recommendation
1 MIN “File sync failed” — File synchronization operation failed.
1. See if the filesyncd (file sync daemon) process is up, either from the:
- Web interface, by selecting View Process Status
- Linux command line, by entering statapp
2. Check the trace log for more granular information. (The file sync daemon can
report failures of synchronizing one or more files.)
Access the trace log, either from the:
- Web interface, by:
a. Selecting the View System Logs diagnostic and
Logmanager Debug trace
b. Specifying the Event Range for the appropriate time frame
c. Matching the “file sync failed” pattern
- Linux command line, by entering logv -t ts
3. (Except S8500) Make sure that the Ethernet duplication link is up, either from
the:
- Web interface, by selecting the Execute Pingall diagnostic
- Linux command line, by entering pingall -a
If not, check each side of this failed link, and make any necessary repairs.
4. (Except S8500) Check the physical fiber connectivity at each server to verify
that this alarm is not a consequence of other duplication-related problems.
5. If the problem persists, escalate the problem.
78 Maintenance Alarms for Avaya Communication Manager, Media Gateways and Servers