| CRN 05831 | DISPLAY-N7-NETRES |
| CRN 05952 | ACTIVATE-N7-NETRES |
| CRN 05953 | DEACT-N7-NETRES |
SWA-SUBSEC MTP
(A)....................... (B).................
(C)........................... (D) (E)
-----------------------------------------------------------------
OPERATOR INPUT :
CONTROL = (2)..... & (3) & (4) & (5) & (6)
-----------------------------------------------------------------------
(7)..... (8)
(9).....................................................
OPC
OWN EXCHNAME MOPCAPPL SET DESTINATION LOGICALNETWORK
---------------- -------- --- -------------- ---------------
(11)............ (12).... (13) (14)......... (15)............
REPORT REFERENCE NUMBER = 5510
| Par. No. | Meaning | Remarks |
|---|---|---|
| (A) | Command name | |
| (B) | Main execution result | |
| (C) | Result part type | |
| (D) | Result part number | |
| (E) | Continuation indicator | |
| (2) | Command control | |
| SCHED | schedule command | |
| (3) | Month | 1 to 12 |
| (4) | Day | 1 to 31 |
| (5) | Hour | 0 to 23 |
| (6) | Minute | 0 to 59 |
| (7) | Header indicating result or error | |
| (8) | Header indicating new data, old data or blank | |
| (9) | Comments on the execution result/error indication | see Evaluation |
| (11) | Own exchange name | in ASCII form |
| (12) | Multiple originating pointcode application | |
| CC | capability code | |
| MT16LK | more than 16 links | |
| MT4096TK | more than 4096 trunks | |
| NETRES | network restoration | |
| NORM | normal | |
| RENUMBR | renumbered point code | |
| (13) | Own pointcode indicator that shows the set of originating point codes (OPCs) which is valid for the routeset, in case of multiple OPCs | |
| 1 | first set of OPCs | |
| 2 | second set of OPCs | |
| 3 | third set of OPCs | |
| 4 | fourth set of OPCs | |
| 5 | fifth set of OPCs | |
| 6 | sixth set of OPCs | |
| 7 | seventh set of OPCs | |
| (14) | Splitted destination point code | point code in split form |
| (15) | Logical network | name of the logical network |
| Key Parameter | Contents / Meaning | Action | ||
|---|---|---|---|---|
| 1 | 2 | 3 | ||
| (9) | COMMAND ABORTED . . . . . . . . . . . . . . . . . | A | ||
| (9) | DB ACCESS ERROR . . . . . . . . . . . . . . . . . | B | ||
| (9) | DB INCONSISTENCY . . . . . . . . . . . . . . . . . | B | ||
| (9) | DUT SOT ERROR . . . . . . . . . . . . . . . . . . | B | ||
| (9) | DUT TRANS ERROR . . . . . . . . . . . . . . . . . | B | ||
| (9) | INCORRECT ROUTE SET STATE TO IMITATED NODE . . . . | A | ||
| (9) | LINKS TO IMITATED NODE MUST BE ORJ DEACTIVATED . . | A | ||
| (9) | NETWORK NOT EXISTING . . . . . . . . . . . . . . . | A | ||
| (9) | NETWORK RESTORATION ACTIVE . . . . . . . . . . . . | A | ||
| (9) | NETWORK RESTORATION ALREADY IN WANTED STATE . . . | A | ||
| (9) | NETWORK RESTORATION NOT ACTIVE . . . . . . . . . . | A | ||
| (9) | NO ENTRY IN R-N73NW-PR FOR NETWORK RESTORATION . . | A | ||
| (9) | NO OWN EXCHANGE NAME FOR NETWORK RESTORATION . . . | A | ||
| (9) | NO RESTORED PC IN THE EXCHANGE . . . . . . . . . . | A | ||
| (9) | ROUTING TO IMITATED NODE CAN NOT BE FOUND . . . . | A | ||
| (9) | SNTM NOT READY ( PLEASE RETRY ) . . . . . . . . . | B | ||
| (9) | SNTM TIMER EXPIRED ( PLEASE RETRY ) . . . . . . . | B | ||
| (9) | SNTM UPDATE FAILURE ( PLEASE RETRY ) . . . . . . . | B | ||
| (9) | STILL TAX CENTER SPECIFIED . . . . . . . . . . . . | A | ||
| (9) | SW ERROR - RESULT INFO NOT ADJUGED . . . . . . . . | B | ||
| (9) | TERMINATE ORJ . . . . . . . . . . . . . . . . . . | A | ||
| Action | Meaning |
|---|---|
| A | Semantic error . |
| B | Repeat the command after some time. If the result is still unsuccessful, special fault clearing will be necessary. See fault reporting procedures. Refer to the document FAULT REPORTING PROCEDURES which is part of the Customer Documentation Guide. |