RRN 05481 HANDLE SCCP MANAGEMENT SUB-SYSTEM

BPS7D906

Message Triggering Condition

Response on operator request of one of the following MMC-commands :
CRN 05785 DEFINE-SCCP-MANSUBS
CRN 05786 DISPLAY-SCCP-MANSUBS
CRN 05787 MODIFY-SCCP-MANSUBS
CRN 05788 REMOVE-SCCP-MANSUBS

Report Layout

 SWA-ORJ-SCCP ORJ
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
   SCCP ORJ AREA
      OPERATOR INPUT :(1)
       DEST     (2) (3)... (4)............. & (5)...
       SSN1     : (6).............
       SSN2     : (7).............
       SSN3     : (8).............
       SSN4     : (9).............
       SSN5     : (10)............
       SSTUSE   : (11).
       STATUS   : (12).
       ALARMTYP : (13)....
       CONTROL  : (14).. & (15) & (16) & (17) & (18)
      ---------------------------------------------------------------------(19)
      (20)
      UNAV1 = Put unavailable by operator
      UNAV2 = Put unavailable by subsystem
      UNAV3 = No CE of the subsystem available (21)
                                        SST ALARM
        SPLIT PC       LOGNET           USE  TYP     STATUS
        -----------------------------------------------------(22)
                                                         SST ALARM
        SPLIT PC       LOGNET           SSN              USE  TYP     STATUS
        ----------------------------------------------------------------------
(previous line continue on next line)
      (23)
                          ALARM
        SSN               TYP     STATUS
        ----------------------------------(24)
      (25) (26).......... (27)............(28)............(29)(30)....(31)....
      --------------------------------------------------------------------(32)
      ERROR INFORMATION :(33)
      (34)
      (35)
      SPLIT PC = (36)
      LOGNET   = (37)
      SSN = (38)
  REPORT REFERENCE NUMBER = 5481

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) Operator input parameters header or suppression value
(2) Dest suppression
(3) Input destination point code in hexadecimal form
(4) Input destination name exchange name or split point code
(5) Input destination logical network
(6) Input sub-system number mnemonic 1
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 sub-system number mnemonic 2
see param (6)
(8) Input sub-system number mnemonic 3
see param (6)
(9) Input sub-system number mnemonic 4
see param (6)
(10) Input sub-system number mnemonic 5
see param (6)
(11) Input sub-system test used indicator
FALSE :SSTUSE flag is reset (no
sub-system test message)
TRUE :SSTUSE flag is set (start a
sub-system test message is case
of receiving of an MTP_RESUME
message)
(12) Input sub-system status
(13) Alarm type
(14) Control parameter
(15) Control parameter : scheduled month
(16) Control parameter : scheduled day
(17) Control parameter : scheduled hour
(18) Control parameter : scheduled minutes
(19) Separator or suppression value
(20) Data title :
(21) Unavailable statuse types
(22) Header or suppression value
(23) Header or suppression value
(24) Header or suppression value
(25) Empty parameter
(26) Splitted destination point code
(27) Logical network field
(28) Sub-system number mnemonic
see param (6)
(29) Sub-system test used flag status
(30) Alarm type
(31) Sub-system status
(32) Report separator or suppression value
(33) Error info header suppression field
(34) Comments on the execution result/error indication
(35) Error parameter indication
(36) Error splitted destination point code
(37) Error Logical network
(38) Failed SSN indication
see param (6)

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(34) COMMAND EXECUTION CANCELLED BY OPERATOR . . . . . A
(34) CONCERNED ITEMS FOR THE LINKED SUBSYSTEMS SHOULD BE REMOVED FIRST B
(34) CONCERNED ITEMS SHOULD BE REMOVED FIRST . . . . . B
(34) DESTINATION ALREADY EXISTS . . . . . . . . . . . . B
(34) DESTINATION DOES NOT EXIST . . . . . . . . . . . . B
(34) MANAGEMENT ALREADY DEFINED FOR SUBSYSTEM . . . . . B
(34) MANAGEMENT ALREADY DEFINED FOR THE NODE . . . . . B
(34) NETWORK IS UNKNOWN . . . . . . . . . . . . . . . . B
(34) NO INFO FOUND . . . . . . . . . . . . . . . . . . A
(34) NO MANAGEABLE SUBSYSTEMS EXIST FOR THE SPECIFIED NODE B
(34) NO MANAGEMENT DEFINED FOR NODE . . . . . . . . . . B
(34) NO MANAGEMENT DEFINED FOR SUBSYSTEM . . . . . . . B
(34) NO SUBSYSTEM EXISTS . . . . . . . . . . . . . . . B
(34) OWN POINT CODE CAN NOT BE USED TO DEFINE A NON-TERMINATING DESTINATION A
(34) SCMG CAN NOT BE REMOVED . . . . . . . . . . . . . A
(34) SPECIFIED DESTINATION IS UNKNOWN . . . . . . . . . B
(34) WRONG DESTINATION POINT CODE GIVEN . . . . . . . . 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 error message is sent to the operator in case of a database error occurrence. In that case, the information collected upto the point where the error occurred is displayed. Special fault clearing is necessary. See fault reporting procedures. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide.