RRN 08513 SCCP MANAGEMENT-DEFINE/REMOVE/DISP CONCERNED DESTINAT

AL9CD906

Message Triggering Condition

Response on operator request of one of the following MMC-commands :
CRN 08514 DEFINE-SCCP-CONDEST
CRN 08516 REMOVE-SCCP-CONDEST
CRN 08515 DISPLAY-SCCP-CONDEST

Report Layout

 SWA-SUBSEC SCCP
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
   SCCP ORJ AREA
      OPERATOR INPUT :(1)
       AFFNODE  (2) (3)..... (4)............. & (5).............
       AFFSSN   : (6).............
       AFFNODE1 (7) (8)..... (9)............. & (10)............
       AFFSSN1  : (11)............
       AFFNODE2 (12) (13).... (14)............ & (15)............
       AFFSSN2  : (16)............
       AFFNODE3 (17) (18).... (19)............ & (20)............
       AFFSSN3  : (21)............
       AFFNODE4 (22) (23).... (24)............ & (25)............
       AFFSSN4  : (26)............
       AFFNODE5 (27) (28).... (29)............ & (30)............
       AFFSSN5  : (31)............
       CSPL     : (32)............
       CSPL1    : (33)............
       CSPL2    : (34)............
       CSPL3    : (35)............
       CSPL4    : (36)............
       CSPL5    : (37)............
       CONDEST1 (38) (39).... (40)............ & (41)............
       CONSSN1  : (42)............
       CONDEST2 (43) (44).... (45)............ & (46)............
       CONSSN2  : (47)............
       CONDEST3 (48) (49).... (50)............ & (51)............
       CONSSN3  : (52)............
       CONDEST4 (53) (54).... (55)............ & (56)............
       CONSSN4  : (57)............
       CONDEST5 (58) (59).... (60)............ & (61)............
       CONSSN5  : (62)............
       DETAIL   : (63).
       CONTROL  : (64).. & (65) & (66) & (67) & (68)
      --------------------------------------------------------------(69)
      (70)
         LOGNET           SPLIT PC
         -------------------------------(71)
         LOGNET           SPLIT PC       SSN
         ------------------------------------------------(72)
         SSN
         ----------------(73)
       (74) (75)............ (76).......... (77)............
       (78)
       CSPL
       ----------------(79)
       (80)............
       (81)
        LOGNET           SPLIT PC
        -------------------------------(82)
        (83)............ (84)..........
       (85)
        SSN
        ----------------(86)
        (87)............
      ---------------------------------------------------------------(88)
      ERROR INFORMATION :(89)
      (90)
      (91)
  REPORT REFERENCE NUMBER = 8513

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) Input parms header or suppres. value
(2) Input Affected Node or suppression value
(3) Input Affected Node destination point code in hexadecimal form
(4) Input Affected Node exchange name exchange name or split point code
(5) Input Affected Node logical network
(6) Input Affected sub-system mnemonic
ALL all possibilities
AUTHCENTRE authentication centre
BSSAP base station sub-system
application part
BSSOMAP base station sub-system O&M part
EIR equipment identity register
HLR home location register
INALSSF ALCATEL service switching
function (IN)
INERSCF ERICSSON service control function
(IN)
INERSSF ERICSSON service switching
function (IN)
ISUP ISDN user part
MAP mobile application part
MSC mobile service centre
MUP mobile user part
OMAP operation and maintenance
administration part
OMUP operation and maintenance user
part
Q3L4TO7 Q3 level interface 4 to 7 (TMN)
SCCPX25 signalling connection control
part X25 link
SCMG signalling connection part
management
SSNABS absentee
SSNIVPN individual virtual private
numbering
TAXAP taxation application part
UNCHG unchanged
UNKNOWN unknown number
USBS user signalling bearer service
VLR visitor location register
(7) Input Affected Node1 or suppression value
(8) Input Affected Node 1 destination point code in hexadecimal form
(9) Input Affected Node 1 exchange name exchange name or split point code
(10) Input Affected Node 1 logical network
(11) Input Affected sub-system mnemonic 1
see param (6)
(12) Input Affected Node 2 or suppression value
(13) Input Affected Node 2 destination point code in hexadecimal form
(14) Input Affected Node 2 exchange name exchange name or split point code
(15) Input Affected Node 2 logical network
(16) Input Affected sub-system mnemonic 2
see param (6)
(17) Input Affected Node3 or suppression value
(18) Input Affected Node 3 destination point code in hexadecimal form
(19) Input Affected Node 3 exchange name exchange name or split point code
(20) Input Affected Node 3 logical network
(21) Input Affected sub-system mnemonic 3
see param (6)
(22) Input Affected Node4 or suppression value
(23) Input Affected Node 4 destination point code in hexadecimal form
(24) Input Affected Node 4 exchange name exchange name or split point code
(25) Input Affected Node 4 logical network
(26) Input Affected sub-system mnemonic 4
see param (6)
(27) Input Affected Node5 or suppression value
(28) Input Affected Node 5 destination point code in hexadecimal form
(29) Input Affected Node 5 exchange name exchange name or split point code
(30) Input Affected Node 5 logical network
(31) Input Affected sub-system mnemonic 5
see param (6)
(32) Input Concerned Signalling Point List
(33) Input Concerned Signalling Point List 1
(34) Input Concerned Signalling Point List 2
(35) Input Concerned Signalling Point List 3
(36) Input Concerned Signalling Point List 4
(37) Input Concerned Signalling Point List 5
(38) Input Concerned Destination1 or suppress.
(39) Input Concerned Destination 1 point code in hexadecimal form
(40) Input Concerned Destination 1 exchange name exchange name or split point code
(41) Input Concerned Destination 1 logical network
(42) Input Concerned sub-system mnemonic
1
see param (6)
(43) Input Concerned Destination2 or suppress.
(44) Input Concerned Destination 2 point code in hexadecimal form
(45) Input Concerned Destination 2 exchange name exchange name or split point code
(46) Input Concerned Destination 2 logical network
(47) Input Concerned sub-system mnemonic
2
see param (6)
(48) Input Concerned Destination3 or suppress.
(49) Input Concerned Destination 3 point code in hexadecimal form
(50) Input Concerned Destination 3 exchange name exchange name or split point code
(51) Input Concerned Destination 3 logical network
(52) Input Concerned sub-system mnemonic
3
see param (6)
(53) Input Concerned Destination4 or suppress.
(54) Input Concerned Destination 4 point code in hexadecimal form
(55) Input Concerned Destination 4 exchange name exchange name or split point code
(56) Input Concerned Destination 4 logical network
(57) Input Concerned sub-system mnemonic
4
see param (6)
(58) Input Concerned Destination5 or suppress.
(59) Input Concerned Destination 5 point code in hexadecimal form
(60) Input Concerned Destination 5 exchange name exchange name or split point code
(61) Input Concerned Destination 5 logical network
(62) Input Concerned sub-system mnemonic
5
see param (6)
(63) Report detailization
(64) Control parameter
(65) Control parameter : scheduled month
(66) Control parameter : scheduled day
(67) Control parameter : scheduled hour
(68) Control parameter : scheduled minutes
(69) Report separator or suppression
(70) Header or suppression for Affected Node or local/remote sub-system
(71) Report header or suppression value
(72) Report header or suppression value
(73) Report header or suppression value
(74) Empty parameter
(75) Affected Node Logical network field
(76) Affected Node destination point code in split form
(77) Affected sub-system mnemonic
see param (6)
(78) Header or suppression for Concerned Signalling Point List
(79) Title or suppression for Concerned Signalling Point List
(80) Concerned Signalling Point List mnemonic
(81) Header or suppression for Concerned Node or remote sub-system
(82) Report header or suppression value
(83) Concerned Node Logical network field
(84) Concerned Node destination point code in split form
(85) Header or suppression for Concerned local sub-system
(86) Header or suppression for Concerned local sub-system
(87) Concerned sub-system mnemonic
see param (6)
(88) Report separator or suppression value
(89) Error info header suppression field
(90) Comments on the execution result/error indication
(91) Error parameter indication

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(90) AFFECTED ITEM IS ALREADY LINKED TO THE GIVEN CSPL B
(90) AFFECTED ITEM IS LINKED TO CONCERNED ITEM DIRECTLY (NOT VIA CSPL) B
(90) AFFECTED NODE DOES NOT EXIST . . . . . . . . . . . B
(90) AFFECTED NODE IS NOT INCLUDED INTO MANAGEMENT . . B
(90) AFFECTED NODE IS UNKNOWN . . . . . . . . . . . . . B
(90) AFFECTED SUBSYSTEM DOES NOT EXIST . . . . . . . . B
(90) AFFECTED SUBSYSTEM IS NOT INCLUDED INTO MANAGEMENT B
(90) COMMAND ABORTED AS CONFIRM NOT GIVEN WITHIN TIMEOUT B
(90) COMMAND EXECUTION CANCELLED BY OPERATOR . . . . . A
(90) CONCERNED NODE ALREADY DEFINED . . . . . . . . . . B
(90) CONCERNED NODE IS NOT FOUND IN THE LINKED LIST . . B
(90) CONCERNED SIGNALLING POINT LIST (CSPL) DOES NOT EXIST B
(90) CONCERNED SIGNALLING POINT LIST (CSPL) IS IN USE BY AFFECETED ITEM B
(90) CONCERNED SIGNALLING POINT LIST (CSPL) IS NOT FOUND IN THE LINKED LIST B
(90) CONCERNED SUBSYSTEM ALREADY DEFINED . . . . . . . B
(90) CONCERNED SUBSYSTEM IS NOT FOUND IN THE LINKED LIST B
(90) DATA WAS PARTLY REMOVED . . . . . . . . . . . . . A
(90) DATA WAS SUCCESSFULLY REMOVED . . . . . . . . . . A
(90) DESTINATION ALREADY EXISTS . . . . . . . . . . . . B
(90) DESTINATION DOES NOT EXIST . . . . . . . . . . . . B
(90) DESTINATION IS UNKNOWN . . . . . . . . . . . . . . B
(90) LINKED LIST IS EMPTY . . . . . . . . . . . . . . . A
(90) NETWORK IS UNKNOWN . . . . . . . . . . . . . . . . B
(90) NO CONCERNED DESTINATION EXISTS . . . . . . . . . B
(90) NO CONCERNED SUBSYSTEM EXISTS . . . . . . . . . . B
(90) NO DATA UPDATES DONE . . . . . . . . . . . . . . . A
(90) NO INFO FOUND . . . . . . . . . . . . . . . . . . A
(90) NO MANAGEABLE SUBSYSTEMS EXIST FOR THE SPECIFIED NODE B
(90) NO MANAGEMENT DEFINED FOR NODE . . . . . . . . . . B
(90) NO MANAGEMENT DEFINED FOR SUBSYSTEM . . . . . . . B
(90) NO SUBSYSTEM EXISTS . . . . . . . . . . . . . . . B
(90) WRONG DESTINATION POINT CODE GIVEN . . . . . . . . B
(90) WRONG DPC GIVEN FOR AFFECTED NODE . . . . . . . . B
(90) WRONG DPC GIVEN FOR CONCERNED DESTINATION . . . . B

Action Description

Action Meaning
A The error message is given in case of any consistency check failure. It contains the necessary information to allow the operator to identify the problem. Check input data ; If the input data is not correct, then enter the MMC-command again with adapted data. If applicable, see the additional error information related to the invalid input parameter. See also Restrictions part of the corresponding MMC-command. If the input data is correct, then the given result data can be taken as an information only and special fault clearing might be necessary. In that case, see fault reporting procedures.
B 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 the involved input parameter, correct and enter the MMC-command again.