Filter
Top Products
Server Alarms
68 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
Table 16: FSY Alarm in Media Server on page 68 describes the FSY MO’s alarms and their
troubleshooting procedures.
Back to: Hardware MOs
Server-related alarms
Table 16: FSY Alarm in Media Server
Event
ID
Alarm
Level
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) Verify that the dup link is both “up” and “refreshed”,
either from the:
● Web interface’s Server section, by selecting View Summary Status
● Linux command line, by entering the server command
(Neither side should be “off-line” nor “down”.)
4. (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.
5. (Except
S8500) Check the physical fiber connectivity at each server to
verify that this alarm is not a consequence of other duplication-related
problems.
6. If the problem persists, escalate the problem.