RRN 04281 QUALITY SURVEILLANCE GLOBAL RESULTS

ATP2XI05

Message Triggering Condition

Inmediate or periodic response to command DISPLAY-QSBLOGAL-RESULTS (CRN: 4501)

Report Layout

 SWA-ORJ-TT COMMND HANDL
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
        REASON = (1)..........
        CURRENT DATE : (2).-(3)-(4)          TIME : (5):(6):(7) (8)
        MOD ID = (9).    PCM ID = (10).    LOOP ID = (11)    RSU ID = (12)
        REASON = (13).........
        TOTAL BER RESULTS PREVIOUS DAY
           INCOMING : EFS=(14)%(15) ES=(16)%(17) SES=(18)%(19) DM=(20)%
(previous line continue on next line)
        (21) UT=(22)%(23)
                      AT =(24)%(25)
           OUTGOING : EFS=(26)%(27) ES=(28)%(29) SES=(30)%(31) DM=(32)%
(previous line continue on next line)
        (33) UT=(34)%(35)
                      AT =(36)%(37)
        SLIP REPORT
           PREVIOUS DAY  : F INT < F EXT : (38)
                           F INT > F EXT : (39)
        LER REPORT
             (40)..............................
  REPORT REFERENCE NUMBER = 4281

Parameter Identification

Par. No. Meaning Remarks
(A) Command name
(B) Main execution result
(C) Result part type
(D) Result part number
(E) Continuation indicator
(1) General failure reason see Evaluation
(2) Current year
(3) Current month
(4) Current day
(5) Current hour
(6) Current minute
(7) Current second
(8) Suppress code 1
(9) Network address
(10) Link identity
(11) Loop identity
(12) RSU identity
(13) Link failure reason see Evaluation
(14) Prev. day, inc. BER results: error free seconds
(15) Suppress code 2
(16) Prev. day, inc. BER results: errored seconds
(17) Suppress code 3
(18) Prev. day, inc. BER res.: severely errored sec.
(19) Suppress code 4
(20) Prev. day, inc. BER results: degraded minutes
(21) Suppress code 5
(22) Prev. day, inc. BER results: unavailable time
(23) Suppress code 6
(24) Prev. day, incoming BER results: available time
(25) Suppress code 7
(26) Prev. day, otg. BER results: error free seconds
(27) Suppress code 8
(28) Prev. day, otg. BER results: errored seconds
(29) Suppress code 9
(30) Prev. day, otg. BER res.: severely errored sec.
(31) Suppress code 10
(32) Prev. day, otg. BER results: degraded minutes
(33) Suppress code 11
(34) Prev. day, otg. BER results: unavailable time
(35) Suppress code 12
(36) Prev. day, outgoing BER results: available time
(37) Suppress code 13
(38) Prev. day slip results, int. freq. < ext. freq.
(39) Prev. day slip results, int. freq. > ext. freq.
(40) Last period LER rate

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(1) ALREADY PREPROGRAMMED BER . . . . . . . . . . . . A
(1) BER MONITORING IS ALREADY ACTIVE . . . . . . . . . A
(1) BER MONITORING IS ALREADY NOT ACTIVE . . . . . . . A
(1) BER MONITORING NOT ACTIVE . . . . . . . . . . . . A
(1) BER NOT PREPROGRAMMED . . . . . . . . . . . . . . A
(1) CANCEL REQUEST NOT ACCEPTED . . . . . . . . . . . A
(1) CE IS NOT AVAILABLE. PLEASE TRY AGAIN LATER . . . C
(1) CE RELOAD. PLEASE RETRY ACT_HDB3 REQUEST . . . . . C
(1) COMMON LOGIC NOT IN TRAFFIC . . . . . . . . . . . A
(1) CRC4 NOT ACTIVE . . . . . . . . . . . . . . . . . A
(1) DB ACCESS ERROR . . . . . . . . . . . . . . . . . B
(1) DELAYED REQUEST ACTIVATED . . . . . . . . . . . . A
(1) DELAYED REQUEST ALREADY EXISTS . . . . . . . . . . A
(1) DTM WITH PCMID=2 NOT POSSIBLE . . . . . . . . . . A
(1) ERSU-MD ONLY WITH LOOPID=A . . . . . . . . . . . . A
(1) IR NOT ALLOWED . . . . . . . . . . . . . . . . . . A
(1) ITB IS NOT EQUIPPED . . . . . . . . . . . . . . . A
(1) ITM-IPTM NEED AT LEAST ACCURACY=STANDARD . . . . . A
(1) LCV ALREADY ACTIVE . . . . . . . . . . . . . . . . A
(1) LCV NOT OBTAINED . . . . . . . . . . . . . . . . . A
(1) LCV REQUEST IS RUNNING . . . . . . . . . . . . . . A
(1) LER MONITORING IS ALREADY ACTIVE . . . . . . . . . A
(1) LER MONITORING IS ALREADY NOT ACTIVE . . . . . . . A
(1) LER MONITORING IS NOT ACTIVE . . . . . . . . . . . A
(1) LER NOT OBTAINED . . . . . . . . . . . . . . . . . A
(1) LERRPERD INCORRECT FOR SADH: MUST BE 100,200,ETC. A
(1) LTM STARTED . . . . . . . . . . . . . . . . . . . A
(1) MOD ID IS NOT A RIM . . . . . . . . . . . . . . . A
(1) NO INQUIRED REPORT FOUND . . . . . . . . . . . . . A
(1) NO ITB CHANNELS EQUIPPED . . . . . . . . . . . . . A
(1) NO LAYER 2 ERRORS FOUND . . . . . . . . . . . . . A
(1) NO PERIODIC REQUEST EXISTS . . . . . . . . . . . . A
(1) NO SCHEDULED BER MONITORING EXISTS . . . . . . . . A
(1) ONLY ONE PCM LINK ALLOWED WITH PREPROGRAMMED BER . A
(1) PCM ID NEEDED . . . . . . . . . . . . . . . . . . A
(1) PCM ID OUT OF RANGE FOR TCE . . . . . . . . . . . A
(1) PCM LINK ALREADY PREPROGRAMMED . . . . . . . . . . A
(1) PCM LINKS WITH NSC REPORTING ACTIVE LIMITED TO 10 A
(1) PERIODIC REQUEST ALREADY EXISTS . . . . . . . . . A
(1) PREPROGRAMMED BER NOT ALLOWED . . . . . . . . . . A
(1) PREPROGRAMMED BER NOT STARTED . . . . . . . . . . A
(1) QS NSC REPORTING IS ALREADY ACTIVE . . . . . . . . A
(1) QS NSC REPORTING IS ALREADY NOT ACTIVE . . . . . . A
(1) QUALITY SUPERVISION ALREADY EXISTS . . . . . . . . A
(1) QUALITY SUPERVISION FULL . . . . . . . . . . . . . A
(1) QUALITY SUPERVISION NOT ACTIVE . . . . . . . . . . A
(1) QUALITY SUPERVISION NOT FOUND . . . . . . . . . . A
(1) QUARTER BER NOT OBTAINED . . . . . . . . . . . . . A
(1) REQUEST CANCELLED SUCCESSFULLY . . . . . . . . . . A
(1) RIM SD ONLY WITH LOOPID=A . . . . . . . . . . . . A
(1) RIM SD WITHOUT RSUID . . . . . . . . . . . . . . . A
(1) RIM TCE NEED LOOP ID . . . . . . . . . . . . . . . A
(1) RIM TCE NEEDS AT LEAST ACCURACY=DEFAULT . . . . . A
(1) RIM TCE ONLY ACCEPTS INCOMING BER RESULTS . . . . A
(1) SCHEDULER REQUEST NOT ACCEPTED . . . . . . . . . . A
(1) SLIP NOT ACTIVE FOR RIM TCE . . . . . . . . . . . A
(1) SLIP NOT OBTAINED . . . . . . . . . . . . . . . . A
(1) TCE HAVE NOT PCM LINK INTERFACES . . . . . . . . . A
(1) TCE IS NOT EQUIPPED . . . . . . . . . . . . . . . A
(1) TEN PCM LINKS ALREADY PREPROGRAMMED . . . . . . . A
(1) TRANSLATION ERROR . . . . . . . . . . . . . . . . B
(1) UNAVAILABLE DATA. PLEASE TRY AGAIN LATER . . . . . C
(1) UNKNOWN MOD ID . . . . . . . . . . . . . . . . . . A
(1) WRONG RANGE . . . . . . . . . . . . . . . . . . . A
(13) ALREADY PREPROGRAMMED BER . . . . . . . . . . . . A
(13) BER MONITORING IS ALREADY ACTIVE . . . . . . . . . A
(13) BER MONITORING IS ALREADY NOT ACTIVE . . . . . . . A
(13) BER MONITORING NOT ACTIVE . . . . . . . . . . . . A
(13) BER NOT PREPROGRAMMED . . . . . . . . . . . . . . A
(13) CANCEL REQUEST NOT ACCEPTED . . . . . . . . . . . A
(13) CE IS NOT AVAILABLE. PLEASE TRY AGAIN LATER . . . C
(13) CE RELOAD. PLEASE RETRY ACT_HDB3 REQUEST . . . . . C
(13) COMMON LOGIC NOT IN TRAFFIC . . . . . . . . . . . A
(13) CRC4 NOT ACTIVE . . . . . . . . . . . . . . . . . A
(13) DB ACCESS ERROR . . . . . . . . . . . . . . . . . B
(13) DELAYED REQUEST ACTIVATED . . . . . . . . . . . . A
(13) DELAYED REQUEST ALREADY EXISTS . . . . . . . . . . A
(13) DTM WITH PCMID=2 NOT POSSIBLE . . . . . . . . . . A
(13) ERSU-MD ONLY WITH LOOPID=A . . . . . . . . . . . . A
(13) IR NOT ALLOWED . . . . . . . . . . . . . . . . . . A
(13) ITB IS NOT EQUIPPED . . . . . . . . . . . . . . . A
(13) ITM-IPTM NEED AT LEAST ACCURACY=STANDARD . . . . . A
(13) LCV ALREADY ACTIVE . . . . . . . . . . . . . . . . A
(13) LCV NOT OBTAINED . . . . . . . . . . . . . . . . . A
(13) LCV REQUEST IS RUNNING . . . . . . . . . . . . . . A
(13) LER MONITORING IS ALREADY ACTIVE . . . . . . . . . A
(13) LER MONITORING IS ALREADY NOT ACTIVE . . . . . . . A
(13) LER MONITORING IS NOT ACTIVE . . . . . . . . . . . A
(13) LER NOT OBTAINED . . . . . . . . . . . . . . . . . A
(13) LERRPERD INCORRECT FOR SADH: MUST BE 100,200,ETC. A
(13) LTM STARTED . . . . . . . . . . . . . . . . . . . A
(13) MOD ID IS NOT A RIM . . . . . . . . . . . . . . . A
(13) NO INQUIRED REPORT FOUND . . . . . . . . . . . . . A
(13) NO ITB CHANNELS EQUIPPED . . . . . . . . . . . . . A
(13) NO LAYER 2 ERRORS FOUND . . . . . . . . . . . . . A
(13) NO PERIODIC REQUEST EXISTS . . . . . . . . . . . . A
(13) NO SCHEDULED BER MONITORING EXISTS . . . . . . . . A
(13) ONLY ONE PCM LINK ALLOWED WITH PREPROGRAMMED BER . A
(13) PCM ID NEEDED . . . . . . . . . . . . . . . . . . A
(13) PCM ID OUT OF RANGE FOR TCE . . . . . . . . . . . A
(13) PCM LINK ALREADY PREPROGRAMMED . . . . . . . . . . A
(13) PCM LINKS WITH NSC REPORTING ACTIVE LIMITED TO 10 A
(13) PERIODIC REQUEST ALREADY EXISTS . . . . . . . . . A
(13) PREPROGRAMMED BER NOT ALLOWED . . . . . . . . . . A
(13) PREPROGRAMMED BER NOT STARTED . . . . . . . . . . A
(13) QS NSC REPORTING IS ALREADY ACTIVE . . . . . . . . A
(13) QS NSC REPORTING IS ALREADY NOT ACTIVE . . . . . . A
(13) QUALITY SUPERVISION ALREADY EXISTS . . . . . . . . A
(13) QUALITY SUPERVISION FULL . . . . . . . . . . . . . A
(13) QUALITY SUPERVISION NOT ACTIVE . . . . . . . . . . A
(13) QUALITY SUPERVISION NOT FOUND . . . . . . . . . . A
(13) QUARTER BER NOT OBTAINED . . . . . . . . . . . . . A
(13) REQUEST CANCELLED SUCCESSFULLY . . . . . . . . . . A
(13) RIM SD ONLY WITH LOOPID=A . . . . . . . . . . . . A
(13) RIM SD WITHOUT RSUID . . . . . . . . . . . . . . . A
(13) RIM TCE NEED LOOP ID . . . . . . . . . . . . . . . A
(13) RIM TCE NEEDS AT LEAST ACCURACY=DEFAULT . . . . . A
(13) RIM TCE ONLY ACCEPTS INCOMING BER RESULTS . . . . A
(13) SCHEDULER REQUEST NOT ACCEPTED . . . . . . . . . . A
(13) SLIP NOT ACTIVE FOR RIM TCE . . . . . . . . . . . A
(13) SLIP NOT OBTAINED . . . . . . . . . . . . . . . . A
(13) TCE HAVE NOT PCM LINK INTERFACES . . . . . . . . . A
(13) TCE IS NOT EQUIPPED . . . . . . . . . . . . . . . A
(13) TEN PCM LINKS ALREADY PREPROGRAMMED . . . . . . . A
(13) TRANSLATION ERROR . . . . . . . . . . . . . . . . B
(13) UNAVAILABLE DATA. PLEASE TRY AGAIN LATER . . . . . C
(13) UNKNOWN MOD ID . . . . . . . . . . . . . . . . . . A
(13) WRONG RANGE . . . . . . . . . . . . . . . . . . . A

Action Description

Action Meaning
A Check input data:
  • if exact: given result data can be taken as information only,
  • if faulty: correct your input data and repeat the MMC-command
B Special fault clearing is necessary. See fault reporting procedures. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide.
C Repeat the command after some time. If the result is still unsuccessful, special fault clearing will be necessary.