sysNameChanged
Enty Type Severity
Service
Aected
Direcon Locaon Descripon
COM warning,
minor
non–service-
aecng
n/a NEND The system name is changed.
Probable Cause Suggested Correcve Acon
The system name is changed. Perform a WARM reboot to clear the condion.
sysNtpNotSynchronized
Enty Type Severity
Service
Aected
Direcon Locaon Descripon
COM minor non–service-
aecng
n/a NEND NTP is not synchronized with the server.
Probable Cause Suggested Correcve Acon
The me is not synced with the NTP server. No acon is required. The alarm automacally clears when
the me synchronizes with the NTP server.
thresholdCrossingAlertCodingViolation
Enty Type Severity
Service
Aected
Direcon Locaon Descripon
Ether OSC (BDL1-3R11) warning non–service-
aecng
receive NEND The threshold for coding violaons is
exceeded for the secon.
Probable Cause Suggested Correcve Acon
■Opcal path problems exist between
the line-terminaon nodes.
â– Low or high light levels can be caused by
dirty ber.
â– The blade has failed.
â– Bit interleaved parity (BIP) errors exceed
a threshold.
1. Check the opcal output level at the upstream
transmier.
2. Check the opcal receive level at the input to the local
blade.
3. Replace the blade.
4. Clean the opcal connectors.
5. Check the opcal receive level at the input of the local
blade.
6. Clear outstanding lossOfSignal alarms to clear the PM
counts.
System Maintenance
Trouble Clearing
334
Release 19.1.1 · Issue 1.1, May 2021
Fujitsu and Fujitsu Customer Use Only