Sysnamechanged; Sysntpnotsynchronized; Thresholdcrossingalertcodingviolation - Fujitsu 1FINITY L100 User Manual

System Maintenance
Trouble Clearing

sysNameChanged

Entity Type
COM

sysNtpNotSynchronized

Entity Type
COM

thresholdCrossingAlertCodingViolation

Entity Type
Ether OSC (BDL1-3R11)
·
Release 19.1.1 Issue 1.1, May 2021
Service
Severity Direction
Affected
warning, non–service- n/a
minor affecting
Probable Cause
The system name is changed.
Service
Severity Direction
Affected
minor non–service- n/a
affecting
Probable Cause
The time is not synced with the NTP server.
Service
Severity Direction
Affected
warning non–service- receive
affecting
Probable Cause
■ Optical path problems exist between
the line-termination nodes.
■ Low or high light levels can be caused by
dirty fiber.
■ The blade has failed.
■ Bit interleaved parity (BIP) errors exceed
a threshold.
Location Description
NEND The system name is changed.
Suggested Corrective Action
Perform a WARM reboot to clear the condition.
Location Description
NEND NTP is not synchronized with the server.
Suggested Corrective Action
No action is required. The alarm automatically clears when
the time synchronizes with the NTP server.
Location Description
NEND The threshold for coding violations is
exceeded for the section.
Suggested Corrective Action
1. Check the optical output level at the upstream
transmitter.
2. Check the optical receive level at the input to the local
blade.
3. Replace the blade.
4. Clean the optical connectors.
5. Check the optical receive level at the input of the local
blade.
6. Clear outstanding lossOfSignal alarms to clear the PM
counts.
Fujitsu and Fujitsu Customer Use Only
334