| CRN 07663 | ACTIVATE-SCCP-MEAS |
| CRN 07664 | DEACT-SCCP-MEAS |
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)
GLOBAL COUNTERS
---------------
TAB09C03 * TAB09C04 * TAB09C05 (14)
ZMSGHDLD * ZMSGTOSS * ZMSGRQGT (15)
-----------*------------*------------
(16)...... * (17)...... * (18)......
COUNTERS PER SSN
----------------
SSN : (20)....
COUNTER 9-6 * COUNTER 9-7 (21)
----------- * ----------- (22)
CLASS 0 * CLASS 1 * CLASS 0 * CLASS 1 (23)
ZSNTUDT0 * ZSNTUDT1 * ZRCVUDT0 * ZRCVUDT1 (24)
-------------*--------------*--------------*-------------
(25)...... * (26)...... * (27)...... * (28)......
TAB09C08 * TAB09C09 * TAB09C10 * TAB09C11 * TAB09C12 (29)
ZMSGBUSS * ZRCVDT1 * ZSNTDT1 * ZRCVDT2 * ZSNTDT2 (30)
-----------*------------*------------*------------*------------
(31)...... * (32)...... * (33)...... * (34)...... * (35)......
TAB09C13 * TAB09C14 (36)
ZSNTED * ZRCVED (37)
-----------*------------
(38)...... * (39)......
ERROR FOR CDC (40)
REPORT REFERENCE NUMBER = 7543
| 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 TABLE9 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 TABLE9 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 TABLE9 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 TABLE9 measurements during which the results will be recorded |
| (11) | see (10) | |
| (12) | TABLE 9 or SCCPUTIL ) | |
| (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 9-3, being the total number of messages handled (from local or remote sub-systems) | - Treated on exchange basis 0000
- As counted messages for the TABLE9 measurements, the N7 Message Signalling Units are assumed |
| (17) | Value of counter 9-4, being the total number of messages intended for local sub-systems | - Treated on exchange basis 0000
- As counted messages for the TABLE9 measurements, the N7 Message Signalling Units are assumed |
| (18) | Value of counter 9-5, being the total number of messages requiring global title translation | - Treated on exchange basis 0000
- As counted messages for the TABLE9 measurements, the N7 Message Signalling Units are assumed 000000000000000000000000 - Counter 9-5 is only required at SCCP nodes with global translation capabilities |
| (20) | Sub-system number (node) identification | see SI 190 - If the SSN
(Sub-System Number) is not known, a dummy value will be used |
| (21) | format of output: ITU-T OR ANSI) | |
| (22) | format of output: ITU-T OR ANSI) | |
| (23) | format of output: ITU-T OR ANSI) | |
| (24) | format of output: ITU-T OR ANSI) | |
| (25) | Value of counter 9-6, being the total number of messages originating (for connectionless class 0 only) per source SSN (Sub-System Number) | - Treated on exchange basis 0000
- As counted messages for the TABLE9 measurements, the N7 Message Signalling Units are assumed 000000000000000000000000 - With source SSN, the originating user is indicated 00 - Counter 9-6 is only counted in originating node |
| (26) | Value of counter 9-6, being the total number of messages originating (for connectionless class 1 only) per source SSN (Sub-System Number) | - Treated on exchange basis 0000
- As counted messages for the TABLE9 measurements, the N7 Message Signalling Units are assumed 000000000000000000000000 - With source SSN, the originating user is indicated 00 - Counter 9-6 is only counted in originating node |
| (27) | Value of counter 9-7, being the total number of messages received (for connectionless class 0 only) per sink SSN (Sub-System Number) | - Treated on exchange basis 0000
- As counted messages for the TABLE9 measurements, the N7 Message Signalling Units are assumed 000000000000000000000000 - With sink SSN, the terminating user (which is determined after called address translation) is indicated 00 - Counter 9-7 is only counted in terminating node |
| (28) | Value of counter 9-7, being the total number of messages received (for connectionless class 1 only) per sink SSN (Sub-System Number) | - Treated on exchange basis 0000
- As counted messages for the TABLE9 measurements, the N7 Message Signalling Units are assumed 000000000000000000000000 - With sink SSN, the terminating user (which is determined after called address translation) is indicated - Counter 9-7 is only counted in terminating node |
| (29) | format of output: ITU-T OR ANSI) | |
| (30) | format of output: ITU-T OR ANSI) | |
| (31) | Value of counter 9-8, being the number of messages sent to a backup sub-system | - Treated on exchange basis 0000
- As counted messages for the TABLE9 measurements, the N7 Message Signalling Units are assumed |
| (32) | Value of counter 9-9, being the number of Data Type 1 messages received from MTP (Message Transfer Part) per sink SSN (Sub-System Number) | - Treated on exchange basis 0000
- As counted messages for the TABLE9 measurements, the N7 Message Signalling Units are assumed 000000000000000000000000 - With sink SSN, the terminating user (which is determined after called address translation) is indicated - Counter 9-9 is implemented, but since in an intermediate node no sub-system node is used, as source SSN and sink SSN, the SSN value equal to zero will be used |
| (33) | Value of counter 9-10, being the number of Data Type 1 messages sent to MTP (Message Transfer Part) per source SSN (Sub-System Number) | - Treated on exchange basis 0000
- As counted messages for the TABLE9 measurements, the N7 Message Signalling Units are assumed 000000000000000000000000 - With source SSN, the originating user is indicated - Counter 9-10 is implemented, but since in an intermediate node no sub-system is used, as source SSN and sink SSN, the SSN value equal to zero will be used |
| (34) | Value of counter 9-11, being the number of Data Type 2 messages received from MTP (Message Transfer Part) per sink SSN (Sub-System Number) | - Treated on exchange basis 0000
- As counted messages for the TABLE9 measurements, the N7 Message Signalling Units are assumed 000000000000000000000000 - With sink SSN, the terminating user (which is determined after called address translation) is indicated - Counter 9-11 is implemented, but since in an intermediate node no sub-system is used, as source SSN and sink SSN, the SSN value equal to zero will be used |
| (35) | Value of counter 9-12, being the number of Data Type 2 messages sent to MTP (Message Transfer Part) per source SSN (Sub-System Number) | - Treated on exchange basis 0000
- As counted messages for the TABLE9 measurements, the N7 Message Signalling Units are assumed 000000000000000000000000 - With source SSN, the originating user is indicated - Counter 9-12 is implemented, but since in an intermediate node no sub-system is used, as source SSN and sink SSN, the SSN value equal to zero will be used |
| (36) | format of output: ITU-T OR ANSI) | |
| (37) | format of output: ITU-T OR ANSI) | |
| (38) | Value of counter 9-13, being the number of Expanded Data messages sent to MTP (Message Transfer Part) per source SSN (Sub-System Number) | - Treated on exchange basis 0000
- As counted messages for the TABLE9 measurements, the N7 Message Signalling Units are assumed 000000000000000000000000 - With source SSN, the originating user is indicated - Counter 9-13 is implemented, but since in an intermediate node no sub-system is used, as source SSN and sink SSN, the SSN value equal to zero will be used |
| (39) | Value of counter 9-14, being the number of Expanded Data messages received from MTP (Message Transfer Part) per sink SSN (Sub-System Number) | - Treated on exchange basis 0000
- As counted messages for the TABLE9 measurements, the N7 Message Signalling Units are assumed 000000000000000000000000 - With sink SSN, the terminating user (which is determined after called address translation) is indicated - Counter 9-14 is implemented, but since in an intermediate node no sub-system is used, as source SSN and sink SSN, the SSN value equal to zero will be used |
| (40) | Central Data Collector (CDC) module error information (if applicable) | see Evaluation |
| Key Parameter | Contents / Meaning | Action | ||
|---|---|---|---|---|
| 1 | 2 | 3 | ||
| (13) | - ALLOCATE FAILURE: DB ERROR ON R-SCCP-T9 . . . . | A | ||
| (13) | - ALLOCATE FAILURE: DB ERROR ON R-TABLE-9 . . . . | A | ||
| (13) | - ALLOCATE FAILURE: ERROR IN CDC INTERFACE . . . . | A | ||
| (13) | - ALLOCATE FAILURE: MAX NBR OF SSNS ALLOCATED . . | B | ||
| (40) | - INCORRECT RESULTS RECEIVED FROM CDC . . . . . . | B | ||
| (40) | - NO RESULTS RECEIVED FROM CDC . . . . . . . . . . | A | ||
| 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 |
|