RRN 06262 HANDLE SWITCH PLANE ORJ

FVJ5AY07

Message Triggering Condition

Response in case of successful / unsuccessful result of the execution, on operator request, of one of the following MMC commands:
CRN 06732 TEST PLANE CONNECT
CRN 06733 INIT PLANE
CRN 06734 DISABLE PLANE

Report Layout

 SWA-BB DEFENCE
    (A).......................                   (B).................
                                 (C)........................... (D) (E)
    -----------------------------------------------------------------
        (1)
        PLANENBR = (2)
        WTC = (3)
        ==> (4)
        VALIDATION RESULT = (5)
        TEX MAIN CODE = (6)
        TEX ERROR KEY = (7)
        TEX SUB CODE = (8)
        TEX SUB CODE = (9)
        TEX SUB CODE = (10)
        MPSR RESULT = (11)
        FAULT CAUSE = (12)
        FMM ID      = (13)
        DB REL ID   = (14)
        DB STATUS   = (15) / (16)
        DB COM ID   = (17)
        DB COM OP   = (18)
        DB LCE ID   = (19)
        ERROR POINT = (20)
        FAULTY ACCESS SWITCHES: (21)
          NETADDR = (22)..
          TEX MAIN CODE = (23)..............
          TEX SUB CODE = (24)...............
          TEX SUB CODE = (25)...............
          TEX SUB CODE = (26)...............
          TEX ERROR KEY = (27)
        RELATED SBLS: (28)
          SBLTYPE  = (29)
          NETADDR  = (30)..
          SBLNBR   = (31)
          SBLSTATE = (32).
          DEVTYPE  = (33)....
          CEFUNC   = (34)....
        RELATED RITS: (35)
          ROW      = (36)
          RACK     = (37)
          SHELF    = (38)
          SLOT     = (39)
          RITTYPE  = (40)....
          RITSTATE = (41).
  REPORT REFERENCE NUMBER = 6262

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) Action specification
(2) Plane number
(3) Wait for Traffic Clear
(4) Global result message see Evaluation
(5) Validation result from CDR FMM
(6) Test Execution FMM main code
(7) Test Execution FMM error key
(8) Test Execution FMM sub code test result successful
termination
(9) Test Execution FMM sub code test result premature termination
(10) Test Execution FMM sub code test result hardware failure
(11) MPSR result
(12) Fault cause
(13) Identity of the FMM where the error occured
(14) Database relation identity
(15) Database status edition 2 see SI 057
(16) Database status edition 2 see SI 057
(17) Database command type
GET get
MODIFY modify
(18) Database command option
IN SEQUENCE in sequence
NO OPTION no option
(19) Database logical control element identity in hexadecimal form
(20) Error point indicator where fault occurred in
the code
(21) Data header
(22) Network Address in hexadecimal form
(23) Test Execution FMM main code
(24) Test Execution FMM sub code test result successful
termination
(25) Test Execution FMM sub code test result premature termination
(26) Test Execution FMM sub code test result hardware failure
(27) Test Execution FMM error key
(28) Data header
(29) Security block type see SI 006
(30) Network address in hexadecimal form
(31) Security block number
(32) Security block status see SI 017
(33) Device type see SI 009
(34) Control element function see SI 019
(35) Data header
(36) Row identification
(37) Rack identification
(38) Shelf number
(39) Slot number
(40) Replaceable item type see SI 010
(41) Status of replaceable item
EQ equipped
EQALW equip allowed
NEQ not equipped
REPLACE replaced

Evaluation

Key Parameter Contents / Meaning Action
1 2 3
(4) COMMAND HANDLER BUSY . . . . . . . . . . . . . . . A
(4) DATABASE ERROR . . . . . . . . . . . . . . . . . . D
(4) MESSAGE OUT OF SEQUENCE . . . . . . . . . . . . . A
(4) MPSR RESULT NOT SUCCESSFUL . . . . . . . . . . . . B
(4) NO RESPONSE FROM CDR . . . . . . . . . . . . . . . A
(4) NO RESPONSE FROM HMC . . . . . . . . . . . . . . . A
(4) NO RESPONSE FROM MTP . . . . . . . . . . . . . . . A
(4) NO RESPONSE FROM NEM . . . . . . . . . . . . . . . A
(4) NO RESPONSE FROM NTE . . . . . . . . . . . . . . . A
(4) TEST ABORTED . . . . . . . . . . . . . . . . . . . A
(4) TEST EXECUTION FMM NOT DOWNLOADED . . . . . . . . A
(4) TEST NOT SUCCESSFUL . . . . . . . . . . . . . . . A
(4) UNEXPECTED REPLY FROM CDR . . . . . . . . . . . . A
(4) VALIDATION NOT SUCCESSFUL . . . . . . . . . . . . A
(5) INVOLVED S12 PLANE BUSY . . . . . . . . . . . . . C
(5) INVOLVED S12 PLANE IN SERVICE . . . . . . . . . . C
(5) INVOLVED S12 PLANE IS A DSN PLANE . . . . . . . . C
(5) INVOLVED S12 PLANE IS AN MPSR PLANE . . . . . . . C
(5) INVOLVED S12 PLANE NOT EQUIPPED . . . . . . . . . C
(5) INVOLVED S12 PLANE OUT OF SERVICE . . . . . . . . C
(5) NETWORK RIT IN OTHER PLANE BUSY . . . . . . . . . C
(5) NETWORK SBL IN OTHER PLANE BUSY . . . . . . . . . C
(5) NO DSN MPSR SWITCH . . . . . . . . . . . . . . . . C
(5) RELATED RIT BUSY . . . . . . . . . . . . . . . . . A
(5) RELATED SBL BUSY . . . . . . . . . . . . . . . . . A
(5) RELATED SBL BUSY . . . . . . . . . . . . . . . . . A
(5) RELATED SBL BUSY . . . . . . . . . . . . . . . . . A
(5) REPLY OUT OF SEQUENCE . . . . . . . . . . . . . . A
(5) RIT OF INV HW UNIT BUSY . . . . . . . . . . . . . A
(5) SAME ACTION ON SAME RIT ONGOING . . . . . . . . . A
(5) SAME ACTION ON SAME SBLTYPE ONGOING . . . . . . . A
(5) SBL BUSY . . . . . . . . . . . . . . . . . . . . . A
(5) SOFTWARE FAULT . . . . . . . . . . . . . . . . . . D
(5) S12 NETWORK BUSY . . . . . . . . . . . . . . . . . C
(5) S12 NETWORK IS MPSR NETWORK . . . . . . . . . . . C
(5) S12 NETWORK NOT EQUIPPED . . . . . . . . . . . . . C
(5) S12 PLANE 1 BUSY . . . . . . . . . . . . . . . . . C
(5) S12 PLANE 1 IS A DSN PLANE . . . . . . . . . . . . C
(5) S12 PLANE 1 OUT OF SERVICE . . . . . . . . . . . . C
(5) S12 PLANE 2 BUSY . . . . . . . . . . . . . . . . . C
(5) S12 PLANE 2 IS A DSN PLANE . . . . . . . . . . . . C
(5) S12 PLANE 2 OUT OF SERVICE . . . . . . . . . . . . C
(5) S12 PLANE 3 BUSY . . . . . . . . . . . . . . . . . C
(5) S12 PLANE 3 IS A DSN PLANE . . . . . . . . . . . . C
(5) S12 PLANE 3 OUT OF SERVICE . . . . . . . . . . . . C
(5) S12 PLANE 4 BUSY . . . . . . . . . . . . . . . . . C
(5) S12 PLANE 4 IS A DSN PLANE . . . . . . . . . . . . C
(5) S12 PLANE 4 OUT OF SERVICE . . . . . . . . . . . . C
(5) TUNNEL NOT ACCESSIBLE . . . . . . . . . . . . . . D
(5) TUNNEL RIT BUSY . . . . . . . . . . . . . . . . . A
(5) TUNNEL SBL BUSY . . . . . . . . . . . . . . . . . A
(6) EXTERNAL FAULT . . . . . . . . . . . . . . . . . . A
(6) HARDWARE FAULT . . . . . . . . . . . . . . . . . . A
(6) MINOR HARDWARE FAULT . . . . . . . . . . . . . . . A
(6) PREMATURE TERMINATION . . . . . . . . . . . . . . A
(23) EXTERNAL FAULT . . . . . . . . . . . . . . . . . . A
(23) HARDWARE FAULT . . . . . . . . . . . . . . . . . . A
(23) MINOR HARDWARE FAULT . . . . . . . . . . . . . . . A
(23) PREMATURE TERMINATION . . . . . . . . . . . . . . A

Action Description

Action Meaning
A Repeat the command after some time. If the result is still unsuccessful, special fault clearing will be necessary. See fault reporting procedures.
B Special fault clearing is necessary. See fault reporting procedures. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide.
C The result data is given as an error message, when inconsistent data is detected during the check of the operation, which is specified by the specific input parameters, who are valid and in conflict with the existing data. Check input data, correct and enter the MMC-command again. See also the Restrictions part of the corresponding MMC-command. If the input data is correct, the given result data can be taken as an information only and it is possible that, the sequence of the maintenance was not executed correctly and the commands, to be entered previously, are forgotten. In that case, enter the necessary MMC- commands first.
D Special fault clearing is necessary. See fault reporting procedures. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide. See also relation identity, database main and sub-status and additional error information. If any error point indication is given, this error point refers in the source listing to a specific point where the database failure occurred. See the error point and check the contents of the relation.