RRN 07542 SCCP MEASUREMENTS - STATISTICS : TABLE 9 BIS COUNTERS

ALQVD901

Message Triggering Condition

Response in case of successful result of the execution, on operator request, of one of the following MMC commands :
CRN 07663 ACTIVATE-SCCP-MEAS
CRN 07664 DEACT-SCCP-MEAS

Report Layout

 SWA-#7 MEASUREMENTS
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
        -----------------------------------------------------------------------
        SCCP MEASUREMENT RESULTS
        -----------------------------------------------------------------------
        DATE :  (1)..-(2)-(3)
        OUTPUT PERIOD :  (4):(5) - (6):(7)
        RECORD PERIOD :  (8):(9) - (10):(11)
        RESULTS FOR (12)....... (13)
         TB09BC01  *  TB09BC02  *  TB09BC03  *  TB09BC04  *  TB09BC05 (14)
         ZSNTUDT   *  ZSNTUDTS  *  ZRCVUDT   *  ZRCVUDTS  *  ZSNTCR   (15)
        -----------*------------*------------*------------*------------
        (16)...... * (17)...... * (18)...... * (19)...... * (20)......
         TB09BC06  *  TB09BC07  *  TB09BC08  *  TB09BC09  *  TB09BC10 (21)
         ZSNTCREF  *  ZRCVCR    *  ZRCVCREF  *  ZSNTRSR   *  ZRCVRSR  (22)
        -----------*------------*------------*------------*------------
        (23)...... * (24)...... * (25)...... * (26)...... * (27)......
         TB09BC11  *  TB09BC12  *  TB09BC13  *  TB09BC14  *  TB09BC15 (28)
         ZSNTERR   *  ZRCVERR   *  ZSNTXUDT  *  ZSNXUDTS  *  ZRCVXUDT (29)
        -----------*------------*------------*------------*------------
        (30)...... * (31)...... * (32)...... * (33)...... * (34)......
         TB09BC16  *  TB09BC17  *  TB09BC18  *  TB09BC19  *  TB09BC20 (35)
         ZRCXUDTS  *  ZSNTLUDT  *  ZSNLUDTS  *  ZRCVLUDT  *  ZRCLUDTS (36)
        -----------*------------*------------*------------*------------
        (37)...... * (38)...... * (39)...... * (40)...... * (41)......
         ERROR FOR CDC (42)
  REPORT REFERENCE NUMBER = 7542

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) Date of issue (measurement recording date) year
(2) month
(3) day
(4) Start time of output period (hour:minute) An output period, being the
complete or partial part of the
recording period, is the period
wherein the results of the
TABLE9B measurement will be
recorded and taken as output
(5) see (4)
(6) Stop time of output period (hour:minute) An output period, being the
complete or partial part of the
recording period, is the period
wherein the results of the
TABLE9B measurement will be
recorded and taken as output
(7) see (6)
(8) Start time of recording period (hour:minute) A recording period is the
activation period of the TABLE9B
measurements during which the
results will be recorded
(9) see (8)
(10) Stop time of recording period (hour:minute) A recording period is the
activation period of the TABLE9B
measurements during which the
results will be recorded
(11) see (10)
(12) TABLE 9 BIS or SCCPQSRV )
(13) Error information (if applicable) see Evaluation
(14) format of output: ITU-T OR ANSI)
(15) format of output: ITU-T OR ANSI)
(16) Value of counter 9B-1, being the number of UDT (Unit Data) messages sent to MTP (Message Transfer Part) - Treated on exchange basis
(17) Value of counter 9B-2, being the number of UDTS (Unit Data Service) messages sent to MTP (Message Transfer Part) - Treated on exchange basis
(18) Value of counter 9B-3, being the number of UDT (Unit Data) messages received from MTP (Message Transfer Part) - Treated on exchange basis
(19) Value of counter 9B-4, being the number of UDTS (Unit Data Service) messages received from MTP (Message Transfer Part) - Treated on exchange basis
(20) Value of counter 9B-5, being the number of CR (Connection Request) messages sent to MTP (Message Transfer Part) plus the ISDN (Integrated Services Digital Network) User Part embedded connection requests - Treated on exchange basis - The
counters 9B-5 and 9B-7 represent
the SCCP occupancy level - In
order to count the ISDN User Part
embedded connection requests for
this counter, the N_REPLY
messages in the terminating node
will be counted
(21) format of output: ITU-T OR ANSI)
(22) format of output: ITU-T OR ANSI)
(23) Value of counter 9B-6, being the number of CREF (Connection Refusal) messages sent to MTP (Message Transfer Part) - Treated on exchange basis
(24) Value of counter 9B-7, being the number of CR (Connection Request) messages received from MTP (Message Transfer Part) plus the ISDN (Integrated Services Digital Network) User Part embedded connection requests - Treated on exchange basis - The
counters 9B-7 and 9B-5 represent
the SCCP occupancy level - In
order to count the ISDN User Part
embedded connection requests for
this counter, the N_REQ_TYP2
(intermediate or terminating)
messages will be counted
(25) Value of counter 9B-8, being the number of CREF (Connection Refusal) messages received from MTP (Message Transfer Part) - Treated on exchange basis
(26) Value of counter 9B-9, being the number of RSR (Reset Request) messages sent to MTP (Message Transfer Part) - Treated on exchange basis
(27) Value of counter 9B-10, being the number of RSR (Reset Request) messages received from MTP (Message Transfer Part) - Treated on exchange basis
(28) format of output: ITU-T OR ANSI)
(29) format of output: ITU-T OR ANSI)
(30) Value of counter 9B-11, being the number of error messages sent to MTP (Message Transfer Part) - Treated on exchange basis
(31) Value of counter 9B-12, being the number of error messages received from MTP (Message Transfer Part) - Treated on exchange basis
(32) Value of counter 9B-13, being the number of XUDT (Extended Unit Data) messages sent - Treated on exchange basis
(33) Value of counter 9B-14, being the number of XUDTS (Extended Unit Data Service) messages sent - Treated on exchange basis
(34) Value of counter 9B-15, being the number of XUDT (Extended Unit Data) messages received - Treated on exchange basis
(35) format of output: ITU-T OR ANSI)
(36) format of output: ITU-T OR ANSI)
(37) Value of counter 9B-16, being the number of XUDTS (Extended Unit Data Service) messages received - Treated on exchange basis
(38) Value of counter 9B-17, being the number of LUDT (Extended Unit Data) messages sent - Treated on exchange basis
(39) Value of counter 9B-18, being the number of LUDTS (Extended Unit Data Service) messages sent - Treated on exchange basis
(40) Value of counter 9B-19, being the number of LUDT (Extended Unit Data) messages received - Treated on exchange basis
(41) Value of counter 9B-20, being the number of LUDTS (Extended Unit Data Service) messages received - Treated on exchange basis
(42) Central Data Collector (CDC) module error information (if applicable) see Evaluation

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(13) - FAILURE: DB ERROR ON R-SCCP-T9B . . . . . . . . A
(42) - INCORRECT RESULTS RECEIVED FROM CDC . . . . . . B
(42) - NO RESULTS RECEIVED FROM CDC . . . . . . . . . . A

Action Description

Action Meaning
A Special fault clearing will be necessary.

If applicable, see fault reporting procedures (refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide).

B
  • The given result data can be taken as an information only.
  • The result data is given as an error message, when an inconsistent data is detected during the check of the operation, which is specified by the specific input parameters, whether is valid and in conflict with the existing data. Check input data. If applicable, see also Restrictions part of the corresponding MMC-command.
    • If the input data is correct :
    • The given result data can be taken as an information only.
    • The result data is given as an error message, when an inconsistent data is detected during the check of the operation, which is specified by the specific input parameters, whether is valid and in conflict with the existing data.
    • Special fault clearing will be necessary.
    • If applicable, see fault reporting procedures (refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide).
    • If the input data is not correct, repeat the MMC-command with adapted data.