TELNET GPONDoctor 9500, Руководство пользователя

Страница: 55 / 105

GPONDoctor 9500
User manual
200080279-00 GPON DOCTOR 9500 user manual EN v0 WEB
55
Figure 28 Context menu on “Capture Tab” for Start/Stop point selection on analysis.

If “ending timestamp” is equal or less than 0 or it is smaller than the “beginning
timestamp”, the engine will analyze the whole capture:
o
Starting in the configured Beginning time stamp
o
Ending at the end of the GPON trace.
Analyze Full Capture checkbox: When checked, forces the engine to ignore the configured
“beginning” and “End” timestamp and analyze the full capture from the first to the last
GPON trace.
3.5.2
“Error Detection” Configuration
Different levels of error detection and analysis can be selected before the engine is
started. In certain scenarios, one issue can be all present around the GPON trace, but it
may be already diagnosed and lack of importance for the current analysis. In such cases,
this feature allows to configure the engine to an “ignore list” of chosen issues so the final
report is only related to the scope/target of current GPON analysis. These are the
configurable error report capacities:
General

FEC Errors: When active all recoverable and non-recoverable FEC errors (if FEC
activated) on both downstream and upstream are reported.

Line Errors: When active the following issues are reported:
o
Continuous lack of downstream signal presence
o
RDI: Remote Defect Indication activated on upstream bursts: The ONT
detects significant errors on downstream frames.

Frame Id: When active, interleaved missing downstream frames are reported by
the engine.

LOFb: Engine reports the presence of uLOFb in traces. LOFb is the
representation in the traces of an “abnormal” upstream event: In a moment where
an upstream burst should have been received, upstream signal was detected but
data was corrupted and delimiter could not be found.

LOSb: Engine reports the present of uLOSb in traces. LOSb is the representation
of a precise upstream event: In a moment where an upstream burst was
expected,
although neither burst was received or upstream optical signal
was detected
. This situation can be perfectly normal: f o r e x a m p l e OLT
expecting upstream responses for a Serial Number request but no new ONT is
present (So no upstream responses arrives, even if expected).