10 Aviat Networks
An unlocked demodulator will activate downstream path failure and path warning
alarms.
ESR Threshold Exceeded
G.826 ESR threshold exceeded. This is a path warning alarm.
Probable Cause
Path conditions, interference, or equipment malfunction.
Recommended Actions
• Check for other alarms, particularly those that indicate a total LOS due to a
component failure, or a complete path failure:
- Component failure or Rx path failure alarms must be checked before
investigating an RSL Below Threshold alarm.
- If the only other alarms are Demodulator Not Locked, and its downstream path
failure and path warning alarms, a path failure is indicated, which may be caused
by a complete path fade or a remote Tx failure.
- If ESR Threshold Exceeded is the only alarm, or the only other alarms are also
path warning alarms, check G.826 and RSL measurements at both ends using
the Portal Performance screen:
- If low RSL and G.826 alarms are present at both ends of the link, a path
problem is indicated, which most likely will be caused by a degraded path due to
rain, diffraction or multipath fading. Check recommended actions for BER
alarms.
- If an ESR alarm is present at just the local end and RSL is normal, interference
from another link should be suspected. Use the Portal History and Event
Browser screens to track the onset of ESR alarms, which for a newly installed
interfering link should show a repetition of G.826 alarm occurrences as the new
link is installed and commissioned.
Additional Information
An ES (errored second) is a one-second period with one or more errored blocks or at
least one defect.
ESR (errored second ratio) is the ratio of ES to total seconds in available time during
a fixed measurement interval. For Eclipse the measurement interval is 60 seconds,
and the ESR alarm threshold is set at 20%.
FPGA Software Load Failure
The software loading of the Field Programmable Gate Array has failed. This is a
critical alarm.
Probable Cause
Equipment or process malfunction.
Recommended Actions
1. If the alarm is raised on initial power-on, retry (reboot) the terminal by switching
the 48 Vdc power off, pausing, and then powering on.
2. If the alarm is raised after a new SW load, reload the previous SW version and
re-check the alarm. If cleared, retry the SW load.
3. If the alarm is raised after a capacity reconfiguration, revert to the previous
To Next Page
Loading...
Need help?
General