RRN 04877 <NETWORK MANAGEMENT : BAD RESULTS REPORT>

A3R3XT02

Message Triggering Condition

Response in case of unsuccessful result of the execution, on operator request, of one of the following MMC-commands :
CRN 01525 NM-CONTROL-OVERRIDE
CRN 01527 ASSIGN-DOCTRL-THRESHLD
CRN 04056 CREATE-TRAFFIC-CATEGORY
CRN 04366 ASSIGN-NM-TIME
CRN 04369 DEFINE-CONTROL-TABLE
CRN 04991 DEST-ALARM-LEVEL
CRN 05366 LOG-NM-ACTIONS
CRN 05886 MC-ALARM
CRN 07675 ASSIGN-NM-REPORT
CRN 07691 DEFINE-NM-MASK

Report Layout

 SWA-NETW MNGR COM HNDLR
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
      RESULT = (1)
      REASON = (2)
      RELATION         = (3)
      DATABASE COMMAND = (4)
      DATABASE STATUS  = (5)
      POSSIBLE ACTIONS = (6)
  REPORT REFERENCE NUMBER = 4877

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) Result of the network management action see Evaluation
(2) Reason for failure see Evaluation
(3) Relation responsible for the bad result(identity)
(4) Database command type
(5) Database status see SI 057
(6) Possible actions that should be performed

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(1) ACTIVATION FAILED . . . . . . . . . . . . . . . . A
(1) ALERT FAILED . . . . . . . . . . . . . . . . . . . A
(1) ASSIGN FAILED . . . . . . . . . . . . . . . . . . A
(1) CLEANUP FAILED . . . . . . . . . . . . . . . . . . A
(1) COPY FAILED . . . . . . . . . . . . . . . . . . . A
(1) CREATION FAILED . . . . . . . . . . . . . . . . . A
(1) DEACTIVATION FAILED . . . . . . . . . . . . . . . A
(1) DISPLAY FAILED . . . . . . . . . . . . . . . . . . A
(1) MACHINE CONGESTION ALARM ACTION FAILED . . . . . . A
(1) MODIFICATION FAILED . . . . . . . . . . . . . . . A
(1) REMOVE FAILED . . . . . . . . . . . . . . . . . . A
(1) UPDATE RELATION FAILED . . . . . . . . . . . . . . A
(2) ACC ACTIVE . . . . . . . . . . . . . . . . . . . . BE
(2) ACC CRRC ACTIVE . . . . . . . . . . . . . . . . . BE
(2) ACC CRRC INACTIVE . . . . . . . . . . . . . . . . BE
(2) ACC INACTIVE . . . . . . . . . . . . . . . . . . . BE
(2) ADR ACTIVE . . . . . . . . . . . . . . . . . . . . BE
(2) ADR INACTIVE . . . . . . . . . . . . . . . . . . . BE
(2) ALL COMBINATIONS USED, NO CLEANUP PERFORMED . . . BE
(2) ANN ACTIVE . . . . . . . . . . . . . . . . . . . . BE
(2) ANN INACTIVE . . . . . . . . . . . . . . . . . . . BE
(2) CALL GAP ACTIVE . . . . . . . . . . . . . . . . . BE
(2) CALL GAP INACTIVE . . . . . . . . . . . . . . . . BE
(2) CANF ACTIVE . . . . . . . . . . . . . . . . . . . BE
(2) CANF INACTIVE . . . . . . . . . . . . . . . . . . BE
(2) CANT ACTIVE . . . . . . . . . . . . . . . . . . . BE
(2) CANT INACTIVE . . . . . . . . . . . . . . . . . . BE
(2) CANTRESV ACTIVE . . . . . . . . . . . . . . . . . BE
(2) CANTRESV INACTIVE . . . . . . . . . . . . . . . . BE
(2) CAR ACTIVE . . . . . . . . . . . . . . . . . . . . BE
(2) CAR INACTIVE . . . . . . . . . . . . . . . . . . . BE
(2) CATEGORY IS IN USE, MAY NOT BE DELETED . . . . . . BE
(2) CATID NOT EXISTING . . . . . . . . . . . . . . . . BE
(2) CLBC ALREADY ACTIVE . . . . . . . . . . . . . . . BE
(2) CLBC ALREADY INACTIVE . . . . . . . . . . . . . . BE
(2) CODE BLOCK ACTIVE . . . . . . . . . . . . . . . . BE
(2) CODE BLOCK INACTIVE . . . . . . . . . . . . . . . BE
(2) COMBINATION ALREADY EXISTS . . . . . . . . . . . . BE
(2) COMBINATION OF PARAMETERS IS NOT DEFINED . . . . . BE
(2) CRRC ACTIVE . . . . . . . . . . . . . . . . . . . BE
(2) CRRC INACTIVE . . . . . . . . . . . . . . . . . . BE
(2) DATABASE ERROR . . . . . . . . . . . . . . . . . . CDE
(2) DELAY PERIOD OUT OF RANGE . . . . . . . . . . . . BE
(2) DELETE ALL IMPOSSIBLE . . . . . . . . . . . . . . BE
(2) DIFFERENT ALARM TYPES . . . . . . . . . . . . . . BE
(2) DUT ERROR : EOT . . . . . . . . . . . . . . . . . CDE
(2) DUT ERROR : ROT . . . . . . . . . . . . . . . . . CDE
(2) DUT ERROR : SOT . . . . . . . . . . . . . . . . . CDE
(2) DUT ERROR : SOT, CAT MNEMONIC NOT DELETED . . . . CDE
(2) ETC ACTIVE . . . . . . . . . . . . . . . . . . . . BE
(2) ETC INACTIVE . . . . . . . . . . . . . . . . . . . BE
(2) HTRA ACTIVE . . . . . . . . . . . . . . . . . . . BE
(2) HTRA INACTIVE . . . . . . . . . . . . . . . . . . BE
(2) LINK FOUND, IMPOSSIBLE TO DELETE . . . . . . . . . BE
(2) LOGGING ACTIVATED . . . . . . . . . . . . . . . . BE
(2) LOGGING DEACTIVATED . . . . . . . . . . . . . . . BE
(2) MASK IS IN USE, MAY NOT BE DELETED . . . . . . . . BE
(2) MASKID NOT EXISTING . . . . . . . . . . . . . . . BE
(2) MEANINGLESS DATA . . . . . . . . . . . . . . . . . BE
(2) NAME ALREADY USED . . . . . . . . . . . . . . . . BE
(2) NAME NOT DELETED . . . . . . . . . . . . . . . . . BE
(2) NM CDC ITF ERROR . . . . . . . . . . . . . . . . . C
(2) NM SCHED ITF ERROR . . . . . . . . . . . . . . . . BCE
(2) NM TRUNK MONITOR IS NOT INFORMED . . . . . . . . . BE
(2) NO CLBC AVAILABLE IN THIS EXCHANGE . . . . . . . . BE
(2) NO COMBINATION ASSIGNED . . . . . . . . . . . . . BE
(2) NO COMBINATION REMOVED . . . . . . . . . . . . . . BE
(2) NO SCHEDULING . . . . . . . . . . . . . . . . . . BE
(2) NO SPACE IN R_CATMNEM . . . . . . . . . . . . . . BDE
(2) NO SPACE IN R_MASKMNEM . . . . . . . . . . . . . . BDE
(2) NOT EXISTING REFERENCE CATID . . . . . . . . . . . BE
(2) PERCENTAGE NOK . . . . . . . . . . . . . . . . . . BE
(2) PERIOD ALREADY EXISTS . . . . . . . . . . . . . . BE
(2) RESERVATION ACTIVE . . . . . . . . . . . . . . . . BE
(2) RESERVATION INACTIVE . . . . . . . . . . . . . . . BE
(2) SCANNING FAILED . . . . . . . . . . . . . . . . . BE
(2) SCHEDULE ALREADY EXISTS . . . . . . . . . . . . . BE
(2) SCR ANAL ACTIVE . . . . . . . . . . . . . . . . . BE
(2) SCR ANAL INACTIVE . . . . . . . . . . . . . . . . BE
(2) SKIP ACTIVE . . . . . . . . . . . . . . . . . . . BE
(2) SKIP INACTIVE . . . . . . . . . . . . . . . . . . BE
(2) SKIPRESV ACTIVE . . . . . . . . . . . . . . . . . BE
(2) SKIPRESV INACTIVE . . . . . . . . . . . . . . . . BE
(2) TAR ACTIVE . . . . . . . . . . . . . . . . . . . . BE
(2) TAR INACTIVE . . . . . . . . . . . . . . . . . . . BE
(2) TDC MEAS ACTIVE . . . . . . . . . . . . . . . . . BE
(2) TDC MEAS INACTIVE . . . . . . . . . . . . . . . . BE
(2) THE NEW TRAFCAT IS IDENTICAL TO THE OLD TRAFCAT . BE
(2) THE REFERENCE CATID IS IDENTICAL TO THE CATID . . BE

Action Description

Action Meaning
A See reason (parameter 2) and depending on the failure reason, continue with the necessary action.
BCE Check input data : - if correct: given result data can be taken as information only. - if faulty : correct your input data and repeat MMC-command. or Repeat the command after some time. If the result is still unsuccessful, special fault clearing will be necessary. See fault reporting procedures. or See possible actions (parameter 6) about the next action that should be performed.
BDE Check input data : - if correct: given result data can be taken as information only. - if faulty : correct your input data and repeat MMC-command. or Special fault clearing is necessary. See fault reporting procedures. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide. In case of a database error, check the contents of the given relation (parameter 4), see database status (parameter 6) and see also possible actions (parameter 7) about the next action that should be performed. or See possible actions (parameter 6) about the next action that should be performed.
BE Check input data : - if correct: given result data can be taken as information only. - if faulty : correct your input data and repeat MMC-command. or See possible actions (parameter 6) about the next action that should be performed.
C Repeat the command after some time. If the result is still unsuccessful, special fault clearing will be necessary. See fault reporting procedures.
CDE Repeat the command after some time. If the result is still unsuccessful, special fault clearing will be necessary. See fault reporting procedures. or Special fault clearing is necessary. See fault reporting procedures. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide. In case of a database error, check the contents of the given relation (parameter 4), see database status (parameter 6) and see also possible actions (parameter 7) about the next action that should be performed. or See possible actions (parameter 6) about the next action that should be performed.