Um XSD Es010006101um11 B

UNCLASSIFIED
Doc N. ES010006101UM11 Iss.
PROGRAM: Romania Upgrade - Phase 1

USER MANUAL For
System Message Dispatcher (XSD)

Program No.: Contract Identification Code : E401
ISSUED BY : SELEX Sistemi Integrati Via Tiburtina km 12,4 - Roma ITALY
The copyright in this document is the property of SELEX Sistemi Integrati S.p.A. The document is supplied on the express understanding that it is to be treated as confidential and that it may not be copied, used or disclosed to others in whole or in part for any purpose except as authorised in writing by SELEX Sistemi Integrati S.p.A.
UNCLASSIFIED
Page 1
UNCLASSIFIED
The total number of pages, included the eventual Appendixes and Annexes, is 79 pages.
UNCLASSIFIED
Page 2
UNCLASSIFIED
SECURITY CLASSIFICATION
The following are the military classification levels for the documents from lowest to highest.
NON CLASSIFICATO CONTROLLATO RISERVATO RISERVATISSIMO SEGRETO SEGRETISSIMO
UNCLASSIFIED RESTRICTED CONFIDENTIAL SECRET TOP SECRET
NC R RR S SS
Editing, issue, custody, reproduction, diffusion and disposal of Classified documents must be done in conformity to the Internal Security Rules (Regolamento Interno di Sicurezza).
UNCLASSIFIED
Page 3
UNCLASSIFIED
Issue Authority
Approved by: (Project Leader)
...................................................... (Valter Ciaraffo)
Date:
14/11/2008
Approved by: (Program Manager)
...................................................... (Sergio Arceri)
Date:
14/11/2008
UNCLASSIFIED
Page 4
UNCLASSIFIED
REVISIONS RECORD SHEET This sheet is a record of revisions to this document.

Issue Rev. A Rev. B Date 20/05/05 12/11/08 Revised Paragraphs First Issue Revised all pages; added Annex B, C and D Document Change Note
UNCLASSIFIED
Page 5
UNCLASSIFIED
ABBREVIATIONS LIST
CODE ACC ACD ACK ACL ACR AFTN AIS ALV APP ARR ASF ASQ ASS ATA ATC ATD ATI ATM ATO ATS ATW BRW CNL CoMap CSCI CWP DAIW DARD DCL DCR Area Control Centre Advanced Common Database Acknowledge Arrival CLearance Arrival Clearance with Re-routing Aeronautical Fixed Traffic Network Aeronautical Information Service Authorization LeVel APProach control ARRival Assistant function Arrival SeQuencing Assistant Controller Actual Time of Arrival Air Traffic Control Actual Time of Departure Actual Time of Inbound Air Traffic Management Actual Time Over Air Traffic Service Auxiliary Working Position BroWse CaNceL Coordination Maps display Computer Software Configuration Item Controller Working Position Danger Area Infringement Warning Direct Access Radar Data Departure CLearance Departure Clearance with Re-routing DESCRIPTION
UNCLASSIFIED
Page 6
UNCLASSIFIED
CODE DEP DIS DLA DMD EMG EST ETA ETD ETI ETL ETO EXE FCK FCN FDM FDP FIR FL FLD FLDA FLDI FPLM FTR GlobMap I/O ICAO INBFIX INI LND LRW LSV LVA MET MIL DEParture list DISabled DeLAy departure Dangerous area Map Display EmerGency ESTimate
DESCRIPTION
Estimated Time of Arrival / Estimated Exit Time from the feeding fix (in ACL order) Estimated Time of Departure Estimated Time of Inbound Estimated Time of Landing Estimated Time Over EXEcutive function Formality ChecK Flight data CaNcellation Flight Data Management Flight Data Processing Flight Information Region Flight Level FLDA Displaying FLight DAta page list FLight DIrectory list Flight Plan Message list File TeRmination Global Mps display Input/Output International Civil Aviation Organization INBound (entry) FIX INItialize LANding report Landing RunWay LaSt leVel planned/cleared LeVel Assignment METeorological MILitary
UNCLASSIFIED
Page 7
UNCLASSIFIED
CODE
DESCRIPTION
MNG MPG MRT MSAW NAVAID NM NOTAM NVS OBT ODS ONL OP OPRSUP PCN PEN PKB PLB PLC PLN QNH RCL RCR RDP REC REG REP REV RFB RHP RNG RWY SBY SID
MaNaGement Map Generation System Multi Radar Tracking Minimum Safe Altitude Warning NAVigational AID Nautical Miles NOtice to AirMan NaVigator aid Off Block Time Operator input and Display System ON Line Operational OpeRational SUPervisor Planning Cancellation PENding tracks ParKing Bay allocation PlayBack Planning Controller PlaNning function Barometric pressure / enter QNH en-Route CLearance en-Route Clearance with Re-routing Radar Data Processing RECording REGistration number Position REport estimate REVision Radar Fall Back Radar Head Processor RaNGe scale RunWaY Stand-BY Standard Instrumental Departure
UNCLASSIFIED
Page 8
UNCLASSIFIED
CODE
DESCRIPTION
SIG SMD SRL SSR STAR SUM SUP SW TAS TBD TCA TKF TMA TMS TRW TXT TWR VDU VFR WTC
fir SIGmet System Messages Dispatching (CSCI) SSR code ReLease Secondary Surveillance Radar / SSR code assignment STandard Approaching Route Software User Manual SuPerVisor SoftWare True Air Speed / change True Air Speed To Be Defined Traffic Conflict Alert TaKe-oFf report TerMinal Area Terminal Area management departure RunWay free TeXT control ToWeR Video Display Unit Visual Flight Rule WaTCher
UNCLASSIFIED
Page 9
UNCLASSIFIED
TABLE OF CONTENTS
1. SCOPE..................................................................................................................................13 1.1 IDENTIFICATION ...............................................................................................................13 1.2 SYSTEM OVERVIEW.........................................................................................................13 1.3 DOCUMENT OVERVIEW...................................................................................................14 2. REFERENCED DOCUMENTS..............................................................................................15 3. CONVENTIONS....................................................................................................................16 4. INTERFACES DESCRIPTION...............................................................................................18 4.1 INTERFACES TOWARD SYSTEM COMPONENTS..........................................................18 4.2 INTERFACES TOWARD THE OPERATOR.......................................................................18 5. FUNCTIONALITY ..................................................................................................................20 5.1 SETTING OF PRIVILEGES................................................................................................20 5.1.1 VIDEO PRESENTATIONS..................................................................................................22 5.1.2 ORDERS............................................................................................................................23 5.1.2.1 ORDERS DESCRIPTION.............................................................................................................23 5.1.2.1.1 SPW - Set Node Password............................................................................................23 5.1.2.1.2 CPW - Change Node Password....................................................................................24 5.1.2.1.3 RPW - Reset Node Password........................................................................................25 5.1.2.1.4 DBR - Disable Privileges of Own Node.........................................................................26 5.1.3 VIDEO PRESENTATIONS..................................................................................................27 5.1.4 ORDERS............................................................................................................................28 5.1.4.1 ORDERS DESCRIPTION.............................................................................................................28 5.1.4.1.1 MST - Set Node Role to Master.....................................................................................28 5.1.4.1.2 SLV - Set Node Role to Slave........................................................................................29 5.2 SETTING OF SYSTEM TIME.............................................................................................30 5.2.1 VIDEO PRESENTATIONS..................................................................................................30 5.2.2 ORDERS............................................................................................................................31 5.2.2.1 ORDERS DESCRIPTION.............................................................................................................31 5.2.2.1.1 STT - Set System Time..................................................................................................31 5.2.2.2 ORDERS SEQUENCES..............................................................................................................32 5.2.2.3 ORDER EXAMPLES ABOUT SETTING OF SYSTEM TIME......................................................................32 5.2.3 MASKS................................................................................................................................32 5.2.4 PRINTING............................................................................................................................32 5.2.5 EXAMPLES ABOUT SETTING OF SYSTEM TIME...........................................................32 5.3 FILTERING AND DISPATCHING OF DIAGNOSTIC MESSAGES....................................33 5.3.1 VIDEO PRESENTATIONS..................................................................................................33 5.3.2 ORDERS............................................................................................................................34 5.3.2.1 ORDERS DESCRIPTION.............................................................................................................34 5.3.2.1.1 CDL - Change Node(s) Diagnostic Level.......................................................................34
UNCLASSIFIED
Page 10
UNCLASSIFIED
5.3.2.1.2 DL0 - Request Node(s) Diagnostic Level 0...................................................................36 5.3.2.1.3 UDL - Change CSCI(s) Diagnostic Level.......................................................................37 5.3.2.1.4 SUL - Show CSCI(s) Diagnostic Level..........................................................................38 5.3.2.1.5 DLD - Change Diagnostic Dissemination of RDS Node(s)............................................39 5.3.2.1.6 SDL - Show Diagnostic Dissemination of RDS Nodes..................................................40 5.3.2.2 ORDERS SEQUENCES..............................................................................................................41 5.3.2.3 ORDER EXAMPLES ABOUT FILTERING AND DISPATCHING OF DIAGNOSTIC MESSAGES...............................41 5.3.3 MASKS................................................................................................................................42 5.3.4 PRINTING............................................................................................................................42 5.3.5 EXAMPLES ABOUT FILTERING AND DISPATCHING OF DIAGNOSTIC MESSAGES. 42 5.4 PRESENTATION OF NODE INFORMATION.....................................................................43 5.4.1 VIDEO PRESENTATIONS..................................................................................................43 5.4.2 ORDERS............................................................................................................................44 5.4.2.1 ORDERS DESCRIPTION.............................................................................................................44 5.4.2.1.1 SNI - Immediately Show Node Status............................................................................44 5.4.2.1.2 SNR - Repeatedly Show Nodes Status.........................................................................48 5.4.2.1.3 VER - Show CSCI(s) Version.........................................................................................49 5.4.2.1.4 IEP - Enable SMD Self-Diagnosis..................................................................................51 5.4.2.2 ORDERS SEQUENCES.............................................................................................................52 5.4.2.3 ORDER EXAMPLES ABOUT PRESENTATION OF NODE INFORMATION......................................................52 5.4.3 MASKS................................................................................................................................52 5.4.4 PRINTING............................................................................................................................52 5.4.5 EXAMPLES ABOUT PRESENTATION OF NODE INFORMATION..................................52 6. OPERATIVE EXAMPLES.....................................................................................................53 7. ORDERS LIST.......................................................................................................................54 8. GENERAL MESSAGES, ERRORS AND ALARMS..............................................................55 8.1 INTRODUCTION ................................................................................................................55 8.2 DIAGNOSTIC MESSAGES................................................................................................57 8.3 ERROR MESSAGES..........................................................................................................61 8.3.1 EXCEPTIONS.....................................................................................................................61 8.3.2 SMD SOFTWARE ERRORS..............................................................................................63 8.3.3 OTHER SOFTWARE ERRORS..........................................................................................68 8.3.4 OPERATORS ERRORS.....................................................................................................69 8.3.5 ALARM MESSAGES...........................................................................................................71 9. DEGRADED WORKING........................................................................................................72 10. START-UP OPERATIVE PROCEDURE...........................................................................72 11. APPENDIXES......................................................................................................................74 11.1 APPENDIX A: DESCRIPTION OF SMD STATUS MESSAGE.........................................74
UNCLASSIFIED
Page 11
UNCLASSIFIED
................................................................................................................................................76 11.2 APPENDIX B: BUCHAREST SMD NODES LIST............................................................77 11.3 APPENDIX C: ARAD SMD NODES LIST........................................................................78 11.4 APPENDIX C: CONSTANTA SMD NODES LIST............................................................79
UNCLASSIFIED
Page 12
UNCLASSIFIED
1. 1.1
SCOPE IDENTIFICATION Within the ALENIA (former SELENIA) Air Traffic Control Automatic System (SATCAS), the identifier of the Advanced System Messages Dispatcher (ASD) Computer Software Configuration Item (CSCI) is: E000ASD0 In this Software User Manual (SUM) the ASD CSCI will be shortly referred as System Messages Dispatcher (SMD).
1.2
SYSTEM OVERVIEW Within the SATCAS, monitor and control messages (i.e. BITE messages) are dispatched by SMD CSCI:
locally, i.e. among (up to 256) nodes belonging to the same Radar (RDS) or Operative (OPS) site remotely, i.e. between one or more (up to 8) RDSs and one or more (up to 8) OPSs The nodes inside each OPS and RDS site are interconnected through Local Area Network (LAN), usually redundant; SMD CSCI supports LAN communication through standard UDP protocol or the ALENIA-proprietary Fast Data Transmission System (FDTS) protocol. The remote RDS OPS communication is provided by serial line, usually redundant; SMD CSCI supports serial line communication through standard High-level Data Link Control (HDLC) protocol (LAP-B or Datagram) or its ALENIA-modified version (MOD-M). When using standard HDLC protocol, SMD can use ASTERIX Category 253 for messages formatting. Inside the SATCAS, SMD is a server CSCI whose capabilities accessible to the operator are: 1) Setting of Privileges 2) 3) 4) 5) Setting of Node Role and Operative Mode Setting of System Time Filtering and Dispatching of Diagnostic Messages Presentation of Node Information
UNCLASSIFIED
Page 13
UNCLASSIFIED
1.3
DOCUMENT OVERVIEW This document describes the operative procedures to use the SMD CSCI; it contains the following chapters:
1) 2) 3)
Scope: it identifies the purpose and the contents of this document Referenced documents: it contains the list of referenced documents Conventions: it contains the alphabetical listing of all acronyms and abbreviations used in this document; the conventional orders syntax representation is described too Interfaces description: it contains the list and the characteristic of interfaces toward the operator Functionality: it contains the video presentation, operative orders and video masks for input information, in a detailed format Operative examples: it contains some useful operative examples to use SMD CSCI Orders list: it contains the alphabetical list of all SMD orders General messages, error and alarms: it contains the detailed list of all messages issued by SMD CSCI to the operator, to signal error situations, alarms, and so on Degraded working: it describes the possible cases of SMD degraded situations, due to external faults Start-up operative procedure: it contains the procedure to start-up the SMD CSCI Appendixes: they provide supplementary information
4) 5)
6) 7) 8)
9) 10) 11)
UNCLASSIFIED
Page 14
UNCLASSIFIED
2.
REFERENCED DOCUMENTS The documents referred in this Software User Manual are: [1] - AUTHOR TITLE
: :
ALENIA S.p.A. E000ASD0-01IRS INTERFACE REQUIREMENTS SPECIFICATION for the ADVANCED SYSTEM MESSAGE DISPATCHER of SATCAS 80-M
DOCUMENT ID. :
[2] AUTHOR TITLE : : ALENIA S.p.A. E000ASD0-01IDD INTERFACE DESIGN DOCUMENT for the ADVANCED SYSTEM MESSAGE DISPATCHER of SATCAS 80-M DOCUMENT ID. :
UNCLASSIFIED
Page 15
UNCLASSIFIED
3.
CONVENTIONS
Acronyms and Abbreviations:

ASD ASTERIX BITE CSCI CDL CPW DBR DLD DL0 FDTS HDLC HWCI IDD IEP IRS LAN MST NSV OPM OPS RDS RPW SATCAS SDL SLV SMD SMR SNI SNR SPW SRS STT SUL SUM UDL UDP VER VT Advanced System Message Dispatcher CSCI All purpose STructured Eurocontrol Radar Information eXchange data format Built-In Test Equipment Computer Software Configuration Item SMD order "Change Node(s) Diagnostic Level" SMD order "Change Node Password" SMD order "Disable Privileges of Own Node" SMD order "Change Diagnostic Dissemination of RDS Node(s)" SMD order "Request Node(s) Diagnostic Level 0" Fast Data Transmission System protocol High-level Data Link Control protocol HardWare Configuration Item Interface Design Document SMD order "Enable SMD Self-Diagnosis" Interface Requirements Specification document Local Area Network HWCI SMD order "Set Node Role to Master" Node SuperVisor CSCI Operational Mode OPerative Site RaDar Site SMD order "Reset Node Password" ALENIA (former SELENIA) Air Traffic Control Automatic System SMD order "Show Diagnostic Dissemination of RDS Nodes" SMD order "Set Node Role to Slave" System Message Dispatcher CSCI System Message Router CSCI SMD order "Immediately Show Node Status" SMD order "Repeatedly Show Nodes Status" SMD order "Set Node Password" Software Requirements Specification document SMD order "Set System Time" SMD order "Show CSCI(s) Diagnostic Level" Software User Manual document SMD order "Change CSCI(s) Diagnostic Level" User Datagram Protocol SMD order "Show CSCI(s) Version" Video Terminal HWCI
UNCLASSIFIED
Page 16
UNCLASSIFIED
Orders syntax conventions:

The syntax of each order is described using the following rules: The three-literal of the order and the values of the parameters are written in uppercase characters. The fields of the order are written in lowercase italic characters; the only exception is represented by the month identifier in the date string, which is actually written in uppercase characters (e.g. dd/MM/yy) to highlight its difference with respect to the minutes in the time-ofday string (e.g. hh:mm:ss). Square brackets "[ ]" mark an optional field. Round brackets "( )" mark a list of alternative values, separated by slashes "|". A sequence of a given number of identical characters is a fixed length identifier. (e.g. "yyyy" is used for a four-literal year identifier). A sequence of parameters of the same type is identified by the first and the last field separated by two points (e.g. num1..num3); the number of allowed parameters is shown by the digit associated to the last field.
Message syntax conventions:

The syntax of each message to the operator is described using the following rules: Each whole message string, with all its fields, is included in quotation marks " ". Italic marks variable fields. Square brackets "[ ]" mark fields which are optional in the message. Round brackets "( )" mark a list of alternative values, separated by slashes "|". "min-value..max-value" notation marks a variability range.
Other conventions:
The expression "own node" means: the node the order is input from. The expression "own site" means: the site own node belongs to. A system node is called visible by the other nodes according to the following rules: a node in RDS is visible by all nodes belonging to own site and by all nodes belonging to all connected Operative sites a node in OPS is visible by all nodes belonging to own site A system site is called visible by the other nodes according to the following rules: a radar site is visible by all nodes belonging to own site and by all nodes belonging to all connected Operative sites an operative site is visible by all nodes belonging to own site
UNCLASSIFIED
Page 17
UNCLASSIFIED
4. 4.1
INTERFACES DESCRIPTION INTERFACES TOWARD SYSTEM COMPONENTS SMD CSCI interfaces with the following system components (refer to [1] and [2]): CSCIs (including NSV) allocated on own node, through Path Manager service external clock, through local serial interface SMD CSCIs allocated on own site, through Local Area Network SMD CSCIs allocated on another (remote) site, through remote serial interface
4.2
INTERFACES TOWARD THE OPERATOR SMD CSCI has not direct interfaces toward the operator, but it uses the following man-machine interfaces to exchange data with him:
I/O Console interface

Interface description: SMD CSCI has an indirect interface toward the I/O Console of own node (if any), used to input the operators orders and to output alphanumeric strings and presentations. The I/O Console is handled by NSV CSCI, which passes to SMD CSCI all operators orders which are not directly handled by itself. Interface type: This interface is made by a VT100-like alphanumeric video and by a standard keyboard. Terminal input characteristics: Each operator input is made by a characters string, always ending with a Carriage Return.
Graphic WorkStation interface

Interface description: The indirect graphic workstation interface is handled by CMS, which performs a graphical and friendly man-machine interface, supporting SMD CSCI in the following tasks: alphanumeric presentation of diagnostic messages (including diagnostics, acknowledges, alarms, notifies)
graphical presentation of the BITE Status of all the nodes of the system; through BITE Status messages, SMD CSCI notifies all changes in the system status, which is represented by CMS using graphical attributes of elements (colours, strings, shapes) on synoptic drawings - helped input of operators orders Interface type: The graphic workstation interface is usually made by a colour graphic video, a keyboard and a buzzer. Terminal input characteristics: SMD CSCI uses the friendly facilities supported by CMS to input operators orders. Acoustic interface:
UNCLASSIFIED
Page 18
UNCLASSIFIED
SMD CSCI uses the buzzer interface supported by CMS to signal the presence of system alarms.
UNCLASSIFIED
Page 19
UNCLASSIFIED
5.
5.1
FUNCTIONALITY
SETTING OF PRIVILEGES
System Orders Syntax

System orders can be originated by: a system operator, using a Graphic WorkStation a maintenance operator, using an I/O console a nodal CSCI, without operators intervention The orders syntax accepted by SMD CSCI is:
[ site | node <blank> ] [ class <blank> ] order [ <blank> params ]

where: site | node optional identifier of the addressed site or node; the allowed values are: sss three-literal of a visible system site (site-addressing) nnn three-literal of a visible system node (node-addressing) omitted (noaddressing) class optional identifier of the addressed class of orders; the allowed values are: ccc three-literal identifier of a defined class of orders omitted the default class (3 blanks) is associated by SMD compulsory three-literal identifier of the order optional order parameter(s), usually separated by blanks
order params
System Orders Dispatching

The way SMD dispatches each order inside the system depends on: the way the order is addressed when produced the way the order has been declared by the addressed CSCI (in its Order_List, refer to [2]) An order with node-addressing is dispatched only toward the addressed node (in own or other site); if on that node there are CSCIs which have declared the given order as internal, then the order is forwarded to them, otherwise the order will be declared lost by SMD. An order with site-addressing is dispatched toward all nodes belonging to the addressed (own or other) site; if on these nodes there are CSCIs which have declared the given order as external, then the order is forwarded to them, otherwise the order will be declared lost by SMD. When an order with no-addressing is input, firstly SMD searches whether there are CSCIs on the own node which have declared the given order as internal: if there are such CSCIs, then the order is forwarded to them
UNCLASSIFIED
Page 20
UNCLASSIFIED
otherwise the order is dispatched toward all nodes belonging to own site; if on these nodes there are CSCIs which have declared the given order as external, then the order is forwarded to them, otherwise the order will be declared lost by SMD
UNCLASSIFIED
Page 21
UNCLASSIFIED
Checks on Orders
Apart some customisable exceptions, each system order must go through the following checks, before being forwarded by SMD(s) to the CSCI that will execute it: password check
Password Check
In order to be able to send orders, the operator must request SMD to: open a job session, entering the correct password of own node at the end of the job session, he can request SMD to close the job session, disabling the access privileges The operator can request SMD to:
change / reset the password of any other node in the system; this will automatically close all open sessions (if any) on the addressed node. It is possible to off-line customise a list of orders that can be input independently of the password setting; through Graphical WorkStation the operator can request SMD to: change this list at run-time, defining orders to be / not to be checked by password It is also possible to off-line customise a list of CSCIs which are enabled by default to generate orders, without opening a job session. By default, orders can be exchanged between all CSCIs running on the same node (but NSV CSCI) without opening a job session. 5.1.1 VIDEO PRESENTATIONS Please refer to 5.1.2.1
UNCLASSIFIED
Page 22
UNCLASSIFIED
5.1.2
ORDERS This paragraph describes all orders executed by SMD CSCI relevant to the functionality Setting of Privileges.
5.1.2.1
Orders description
5.1.2.1.1 SPW - Set Node Password Purpose: This order allows the operator to open a job session on own node, typing the node password. Syntax: SPW [ <blank> password ] where: passwordcurrent password of own node: it is an alphanumeric string long from 3 to 14 characters; it has no echo The I/O Console operator can omit on own node the parameter password; in this case NSV CSCI will display on the I/O Console the string "PASSWORD : ", to prompt the operator to type the current password of own node. Effect: SMD on own node replies the following acknowledge: "hh:mm:ss nnn SPW : ORDER ACCEPTED" where nnn is the three-literal identifier of own node, and then: the job session is opened, therefore the operator can input system orders from own node Constrains: The order is not executed by SMD if: password is not the current password of own node
UNCLASSIFIED
Page 23
UNCLASSIFIED
5.1.2.1.2 CPW - Change Node Password Purpose: This order allows the operator to change the current password of a visible node. Syntax: [ nnn <blank> ] CPW [ <blank> old_psw <blank> new_psw <blank> new_psw ] where: nnn optional three-literal identifier of the node whose password has to be changed (own node, if omitted)
old_psw current password of the addressed node; it is an alphanumeric string long from 3 to 14 characters: it has no echo new_psw new password for the addressed node; it is an alphanumeric string long from 3 to 14 characters; it has no echo and must be repeated twice for confirmation The I/O Console operator can omit on own node the parameters old_psw and new_psw; in this case NSV CSCI will display: once the string "OLD PASSWORD : ", to prompt the operator to type the current password of the addressed node twice the string "NEW PASSWORD : ", to prompt the operator to enter and confirm the new password for the addressed node Effect: SMD on the addressed node replies the following acknowledge: "hh:mm:ss nnn CPW : ORDER ACCEPTED" and then: the current password of node nnn becomes equal to the string new_psw all open job sessions on node nnn are closed (unless enabled by default) Constrains: The order is not executed by SMD if: nnn is the identifier of a node not visible by own node old_psw is not the current password of node nnn the second instance of the string new_psw is not equal to the first one
UNCLASSIFIED
Page 24
UNCLASSIFIED
5.1.2.1.3 RPW - Reset Node Password Purpose: This order allows the operator to close all job sessions on a visible node, disabling all system access authorisations. Syntax: [ nnn <blank> ] RPW where: nnn Effect: SMD on the addressed node replies the following acknowledge: "hh:mm:ss nnn RPW : ORDER ACCEPTED" and then: all system access authorisations on node nnn are disabled After the execution of this order, every operator who wants to input system orders from node nnn has to set again the password of that node. Constrains: The order is not executed by SMD if: nnn is the identifier of a node not visible by own node It is possible to customise a list of CSCIs which are enabled by default to send orders; in this case, RPW order doesnt disable their authorisation. optional three-literal identifier of the node whose password must be reset
UNCLASSIFIED
Page 25
UNCLASSIFIED
5.1.2.1.4 DBR - Disable Privileges of Own Node Purpose: This order allows the operator to close his job session on own node, disabling his previous system access authorisation. Syntax: DBR Effect: SMD on own node replies the following acknowledge: "hh:mm:ss nnn DBR : ORDER ACCEPTED" where nnn is the three-literal identifier of own node, and then: the system access authorisation on own node is reset After the execution of this order, every operator who wants to input system orders from the node has to set again its password. Constrains: None. Setting of Node Role and Operative Mode The status of each system node is defined by two attributes: its Role and its Operative Mode.
Node Role
The possible values for the Role of a node are: SINGLE MASTER the when a node is not in redundant configuration when a node belongs to a matched pair of nodes, currently it is Master, and partner node is available (in Slave role)
MASTER ALONE when a node belongs to a matched pair of nodes, currently it is Master and the partner node is not available SLAVE Slave; when a node belongs to a matched pair of nodes and currently it is SMD on whatever Slave node is not allowed to perform the following operations: take of lock RDS reception of time information from the external clock (except for North data) dissemination of message from RDS to OPS (except for the messages which are produced by the Slave node itself). The operator can request SMD to: change Master Slave the Role of a matched pair of nodes
UNCLASSIFIED
Page 26
UNCLASSIFIED
5.1.3
VIDEO PRESENTATIONS None.
UNCLASSIFIED
Page 27
UNCLASSIFIED
5.1.4
ORDERS This paragraph describes all orders executed by SMD CSCI relevant to the functionality Setting of Node Role and Operative Mode.
5.1.4.1
Orders description
5.1.4.1.1 MST - Set Node Role to Master Purpose: This order allows the operator to exchange the roles in a matched pair of nodes: the node addressed by the order becomes Master the partner node becomes Slave (Stand-By) Syntax: [ nnn <blank> ] MST where: nnn Effect: SMD on the addressed node replies the following acknowledge: "hh:mm:ss nnn MST : BEGIN SWITCH STANDBY -> MASTER" and sends the order to the NSV CSCI, which is the real performer of MST order. Therefore the operator has to wait for NSV messages, to check the complete execution of this order. Constrains: The order is not executed by SMD if: nnn is the identifier of a node not visible by own node the addressed node has not Slave role the addressed node is in Maintenance (Enable or Locked) mode, while the partner (Master) node is in Operational mode optional three-literal identifier of the node to become Master (own node, if omitted)
UNCLASSIFIED
Page 28
UNCLASSIFIED
5.1.4.1.2 SLV - Set Node Role to Slave Purpose: This order allows the operator to exchange the roles in a matched pair of nodes: the node addressed by the order becomes Slave (Stand-By) the partner node becomes Master Syntax: [ nnn <blank> ] SLV where: nnn Effect: SMD on the addressed node replies the following acknowledge: "hh:mm:ss nnn SLV : BEGIN SWITCH MASTER -> STANDBY" and sends the order to the NSV CSCI, which is the real performer of SLV order. Therefore the operator has to wait for NSV messages, to check the complete execution of this order. Constrains: The order is not executed by SMD if: nnn is the identifier of a node not visible by own node the addressed node has not Master role the addressed node is in Operational mode, while the partner node is in Maintenance (Enable or Locked) mode optional three-literal identifier of the node to become Slave (own node, if omitted)
UNCLASSIFIED
Page 29
UNCLASSIFIED
5.2
SETTING OF SYSTEM TIME SMD is the system time authority; it can receive time information from an external clock, usually redundant, or from the operator; when redundant, one of the clock is considered main, the other one reserve. The operator can request SMD to:
set the system time (only if no clock is available and synchronised by the external radio antenna)
External Clock
An external clock can be in one of the following operative status: synchronised (main, available, synchronised) not synchronised (main, available) logical off (main, available, no input) fault (main or reserve, not available) reserve (reserve, available) not diagnosable (main or reserve, start-up phase) The status of an external clock changes after: node start-up logical OFF status, i.e. no reception or wrong reception of time information from the clock fault of the peripheral board the clock is connected to reception of first synchronised time information from the clock reception of first not synchronised time information from the clock
Time Information
SMD updates the system time on all nodes in the following cases:
the last time read on the external clock differs from the system time more than a customisable threshold; SMD will align asynchronously all connected nodes (sending its BITE Status message) the time is set by the operator; SMD will align immediately all connected nodes (sending a designed message) 5.2.1 VIDEO PRESENTATIONS None.
UNCLASSIFIED
Page 30
UNCLASSIFIED
5.2.2
ORDERS This paragraph describes all orders executed by SMD CSCI relevant to the functionality Setting of System Time.
5.2.2.1
Orders description
5.2.2.1.1 STT - Set System Time Purpose: This order allows the operator to set the system time and, optionally, the system date. Syntax: STT <blank> hh del mm del ss [ <blank> MM del dd del yy ] where: hh mm ss dd MM yy del Effect: SMD on own node replies the following acknowledge: "hh:mm:ss nnn STT hh del mm del ss [ MM del dd del yy] : ORDER ACCEPTED" where nnn is the three-literal identifier of own node, and then: Constrains: The order is not executed by SMD if: in a node of the system there is a synchronised clock the date has never been set before in the system, and the STT order doesnt provide it a (customisable) amount of time is not elapsed since previous STT order the current time and/or the time set by the operator is around midnight set the system time (and date, if necessary) on all connected nodes are two digits for the hours are two digits for the minutes are two digits for the seconds are two digits for the day are two digits for the month are the last two figures of the year is one of the following delimiter characters: / - : ;
UNCLASSIFIED
Page 31
UNCLASSIFIED
5.2.2.2
Orders sequences No specific orders sequence applies to this functionality.
5.2.2.3
Order examples about Setting of System Time STT 12:25:33 05:23:96 STT 09:14:00 the operator set the system time and date the operator set only the system time
5.2.3
MASKS Not applicable.
5.2.4
PRINTING The SMD messages scrolling on I/O console can be printed in hard-copy.
5.2.5
EXAMPLES ABOUT SETTING OF SYSTEM TIME The operator is allowed to set the system time only when no clock is available and synchronised by the external radio antenna.
UNCLASSIFIED
Page 32
UNCLASSIFIED
5.3
FILTERING AND DISPATCHING OF DIAGNOSTIC MESSAGES
Diagnostic Messages
Diagnostic messages are ASCII strings produced by the CSCIs (including SMD itself) to notify a meaningful event (e.g. an anomaly) to the operator. In order to allow diagnostics selection, the producer CSCI must associate to each diagnostic message a severity level in the range [0 , 7]; while the level 0 is usually used for non-operational diagnostics (e.g. notifications for internal testing of CSCIs), the levels from 1 to 7 are hierarchical (1 = heaviest severity). SMD receives the diagnostic messages from the producer CSCIs running on own node and dispatch them, through other SMDs, to all diagnostic users CSCIs running on whatever visible node. The operator can request SMD to:
select the diagnostic levels to display, in order to filter out all undesired messages select the highest diagnostic level to be produced by one / all CSCI(s) on a node show the highest diagnostic level to be produced by each CSCI of a node select the highest diagnostic level to be sent from an RDS node towards an OPS show the highest diagnostic level sent from all nodes of an RDS towards a connected OPS
Alarm Messages
Each producer CSCIs can associate to a diagnostic message the acoustic attribute, to signal through buzzer activation the occurrence of an alarm in the system.
5.3.1
VIDEO PRESENTATIONS Please refer to 5.4.2.1.4 and 5.4.2.1.6 .
UNCLASSIFIED
Page 33
UNCLASSIFIED
5.3.2
ORDERS This paragraph describes all orders executed by SMD CSCI relevant to the functionality Filtering and Dispatching of Diagnostic Messages.
5.3.2.1
Orders description
5.3.2.1.1 CDL - Change Node(s) Diagnostic Level Purpose: This order allows the operator to define up to which level the diagnostic messages produced by one / all visible node(s) have to be displayed on own node. The CDL order provides a diagnostic filtering on presentation, not on production; it acts on the diagnostic messages having level between 1 and 7. Syntax: CDL <blank> lev [ <blank> nnn ] where: lev highest level of diagnostic messages the operator wants to display on own node from the addressed node(s); its allowed values are: 1.. 7 if diagnostic messages up to the given level 1..7 have to be displayed I if no diagnostic messages and broadcast notifies have to be displayed at all nnn optional three-literal identifier of the addressed node(s) (own node, if omitted); its allowed values are: ALL LOC nnn Effect: SMD on own node replies the following acknowledge: "hh:mm:ss ooo CDL lev [ nnn] : ORDER ACCEPTED" where ooo is the three-literal identifier of own node, and then: if lev is in the range from 1 to 7, all diagnostic messages produced by the addressed node(s) having level greater than lev will not be displayed on own node if lev is equal to "I", no diagnostic and broadcast notify messages produced by the addressed node(s) will be displayed at all on own node Constrains: if the order applies to all visible nodes if the order applies to all nodes of own site if the order applies to the node nnn
UNCLASSIFIED
Page 34
UNCLASSIFIED
The order is not executed by SMD if: nnn is the identifier of a node not visible by own node
UNCLASSIFIED
Page 35
UNCLASSIFIED
5.3.2.1.2 DL0 - Request Node(s) Diagnostic Level 0 Purpose: This order allows the operator to request the presentation on own node of all diagnostic messages having level 0 produced by one / all visible node(s). The DL0 order provides a diagnostic filtering on presentation, not on production; it acts on the diagnostic messages having level equal to 0 (non operational diagnostics). Syntax: DL0 <blank> flag [ <blank> nnn ] where: flag flag indicating whether the diagnostic level 0 presentation must be enabled; its allowed values are: nnn "ON" if the presentation of diagnostic level 0 must be enabled "OFF"if the presentation of diagnostic level 0 must be disabled
optional three-literal identifier of the addressed node(s) (own node, if omitted); its allowed values are: ALL LOC nnn if the order applies to all visible nodes if the order applies to all nodes of own site if the order applies to the node nnn
Effect: SMD on own node replies the following acknowledge: "hh:mm:ss ooo DL0 flag [ nnn] : ORDER ACCEPTED" where ooo is the three-literal identifier of own node, and then: if flag is equal to ON, all diagnostic messages having level 0 produced by the addressed node(s) will be displayed on own node if flag is equal to OFF, no diagnostic messages having level 0 produced by the addressed node(s) will be displayed on own node Constrains: The order is not executed by SMD if: nnn is the identifier of a node not visible by own node
UNCLASSIFIED
Page 36
UNCLASSIFIED
5.3.2.1.3 UDL - Change CSCI(s) Diagnostic Level Purpose: This order allows the operator to define up to which level the diagnostic messages from one / all CSCI(s) on a visible node have to be produced toward the system. The UDL order provides a filtering on production, not on presentation; it acts on diagnostic messages having level included between 0 and 7. Syntax: [ nnn <blank> ] UDL <blank> lev <blank> ccc where: nnn lev optional three-literal identifier of the addressed node (own node, if omitted) highest level of diagnostic messages the addressed CSCI(s) is / are allowed to produce toward the system; its allowed values are: 0.. 7 if diagnostic messages up to the given level 0..7 have to be produced I if no diagnostic messages have to be produced at all ccc three-literal identifier of the addressed CSCI(s); its allowed values are: ALL ccc Effect: SMD on node nnn replies the following acknowledge: "hh:mm:ss nnn UDL lev ccc : ORDER ACCEPTED" and then: if lev is in the range from 0 to 7, all diagnostic messages having level greater than lev will not be produced by the addressed CSCI(s) toward the system if lev is equal to "I", no diagnostic messages at all will be produced by the addressed CSCI(s) toward the system Constrains: The order is not executed by SMD if: nnn is the identifier of a node not visible by own node ccc is the identifier of a CSCI which is unknown by SMD on the addressed node if the order applies to all CSCIs in the addressed node if the order applies to the CSCI ccc
UNCLASSIFIED
Page 37
UNCLASSIFIED
5.3.2.1.4 SUL - Show CSCI(s) Diagnostic Level Purpose: This order allows the operator to display which is / are the maximum diagnostic level(s) to be produced by one / all CSCIs on a visible node. Syntax: [ nnn <blank> ] SUL <blank> ccc where: nnn ccc optional three-literal identifier of the addressed node (own node, if omitted) three-literal identifier of the addressed CSCI(s); its allowed values are: ALL ccc Effect: SMD on node nnn (own node, if omitted) replies the following acknowledge: "hh:mm:ss nnn SUL ccc : ORDER ACCEPTED" and then shows to the operator, in a table like the following one, the maximum level of diagnostic to be produced by the addressed CSCI(s) on the given node: if the order applies to all CSCIs in the addressed node if the order applies to the CSCI ccc
USERS LEVEL Func ccc . . . ccc

where: ccc name of the CSCI on the addressed node lev Constrains: The order is not executed by SMD if: nnn is the identifier of a node not visible by own node ccc is the identifier of a CSCI which is unknown by SMD on the addressed node maximum diagnostic level to be produced by the CSCI ccc; it can assume a value from 0 to 7, or the value no level if no diagnostic at all have to be produced by it
Level lev . . . lev
UNCLASSIFIED
Page 38
UNCLASSIFIED
5.3.2.1.5 DLD - Change Diagnostic Dissemination of RDS Node(s) Purpose: This order allows the operator to limit the diagnostic to be sent by the nodes in a visible radar site toward own operative site. The DLD order provides a diagnostic filtering on production, not on presentation; it acts on diagnostic messages having level included between 0 and 7. Syntax: rrr <blank> DLD <blank> lev <blank> nnn where: rrr lev compulsory three-literal of the addressed radar site highest level of diagnostic messages the addressed node(s) must send toward own operative site; its allowed values are: 0.. 7 if diagnostic messages up to the given level 0..7 have to be produced I if no diagnostic messages have to be produced at all nnn three-literal identifier of the addressed node(s) in the radar site rrr; its allowed values are: ALL nnn Effect: SMD on the bridge node of the radar site rrr replies the following acknowledge: "hh:mm:ss hhh rrr DLD lev nnn: ORDER ACCEPTED" where hhh is the three-literal identifier of the bridge node of the radar site rrr, and then: if lev is in the range from 0 to 7, all diagnostic messages having level greater than lev will not be produced by the addressed node(s) toward own operative site if lev is equal to "I", no diagnostic messages at all will be produced by the addressed node(s) toward own operative site Constrains: The order is not executed by SMD if: rrr is the identifier of a radar site not visible by own node nnn is the identifier of a node not belonging to the radar site rrr own site is not an operative site if the order applies to all nodes in the radar site rrr if the order applies to the node nnn in the radar site rrr
UNCLASSIFIED
Page 39
UNCLASSIFIED
5.3.2.1.6 SDL - Show Diagnostic Dissemination of RDS Nodes Purpose: This order allows the operator to display which is the maximum diagnostic level to be produced by each node of a visible radar site toward a connected operative site. Syntax: rrr <blank> SUL <blank> ooo where: rrr ooo Effect: SMD on the bridge node of the radar site rrr replies the following acknowledge: "hh:mm:ss hhh rrr SDL ooo : ORDER ACCEPTED" where hhh is the three-literal identifier of the bridge node of the radar site rrr, and then shows to the operator, in a table like the following one, the maximum level of diagnostic to be produced by each node of radar site rrr toward the operative site ooo: compulsory three-literal of the addressed radar site compulsory three-literal of the operative site the order refers to
DIAGNOSTIC LEVEL Node nnn . . . nnn

where: nnn name of each node belonging to the radar site rrr lev maximum diagnostic level which can be produced by the node nnn; it can assume a value from 0 to 7, or the value no level if no diagnostic at all have to be produced toward the operative site ooo
Level lev . . . lev
Constrains: The order is not executed by SMD if: rrr is the identifier of a radar site not visible by own node ooo is the identifier of an operative site not connected to radar site rrr
UNCLASSIFIED
Page 40
UNCLASSIFIED
5.3.2.2
5.3.2.3
Order examples about Filtering and Dispatching of Diagnostic Messages CDL 7 ALL CDL 3 LOC CDL 4 OT1 CDL I CDL I ALL DL0 ON DL0 ON ALL DL0 ON OT1 DL0 OFF LOC DL0 OFF OT2 UDL 5 ALL the operator requests to display all diagnostic messages produced by all visible system nodes (excluding diagnostic messages with level 0) the operator requests to display all diagnostic messages having level equal to 1, 2 or 3 produced by all nodes of own site the operator requests to display all diagnostic messages having level from 1 to 4 produced by the node OT1 the operator requests to stop the presentation of all the diagnostic messages produced by own node (excluding diagnostic messages with level 0) the operator requests to stop the presentation of all the diagnostic messages produced by all visible system nodes (excluding diagnostic messages with level 0) the operator requests to display all diagnostic messages having level equal to 0 produced by own node the operator requests to display all diagnostic messages having level equal to 0 produced by all visible system nodes the operator requests to display all diagnostic messages having level equal to 0 produced by the node OT1 the operator requests to stop the presentation of the diagnostic messages having level equal to 0 produced by all nodes of own site the operator requests to stop the presentation of the diagnostic messages having level equal to 0 produced by the node OT2 the operator requests to limit all CSCI on own node to produce diagnostic messages up to level 5.
OT1 UDL 2 TTM the operator requests to inhibit TTM CSCI on OT1 node to produce diagnostic messages having level greater than 2. OT2 UDL I TRH the operator requests to inhibit TRH CSCI on OT2 node to produce any diagnostic messages. UDL I ALL the operator requests to inhibit all CSCI of own node to produce any diagnostic messages
UNCLASSIFIED
Page 41
UNCLASSIFIED
OT1 SUL TRH OT2 SUL ALL
the operator requests to display the diagnostic level produced by TRH CSCI on OT1 node the operator requests to display the diagnostic level produced by all CSCI on OT2 node
OTR DLD 3 OT1 the operator requests to the of site OTR to disseminate toward own site diagnostic messages produced by the node OT1 up to level 3 OTR DLD 5 ALL the operator requests to the of site OTR to disseminate toward own site diagnostic messages produced by all OTR nodes up to level 5 OTR SDL LBO the operator requests to display the diagnostic level disseminates by the radar site OTR towards the operative site LBO
5.3.3
5.3.4
5.3.5
EXAMPLES ABOUT FILTERING AND DISPATCHING OF DIAGNOSTIC MESSAGES The Diagnostics with Level 0 are mainly used for internal testing of SMD and other CSCIs. The Diagnostic Dissemination is used to limit on OPS LAN the traffic of RDS diagnostic.
UNCLASSIFIED
Page 42
UNCLASSIFIED
5.4
PRESENTATION OF NODE INFORMATION
BITE Status of Nodes

SMD produces the BITE Status of own node using the information sent from the CSCIs running on the same node: NSV CSCI sends information about the status of the peripherals and devices of the node the other CSCIs send information about their logical status SMD collects these data in order to send the whole BITE Status message of the node, periodically only or at each variation too, toward all visible system nodes. The operator on the I/O console can request SMD to:
dump immediately the Status message of a visible node dump repeatedly each Status message of all nodes
Version of CSCIs
SMD memorises the version of a CSCI every time: the CSCI opens a Path with SMD the CSCI sends a version message (start-up) (run-time)
Please refer to [2] for more information; the operator can request SMD to: display the version of one / all CSCI(s) of a visible node
Self-Diagnosis of SMD
In case of recoverable software error (refer to 8), SMD CSCI can produce a diagnostic message, to inform the operator about the occurrence of an internal software error. The operator can request SMD to:
5.4.1
enable / disable SMD self-diagnosis on own node VIDEO PRESENTATIONS Please refer to 5.4.2.1.1 and 5.4.2.1.3 .
UNCLASSIFIED
Page 43
UNCLASSIFIED
5.4.2
ORDERS This paragraph describes all orders executed by SMD CSCI relevant to the functionality Presentation of Node Information.
5.4.2.1
Orders description
5.4.2.1.1 SNI - Immediately Show Node Status Purpose: This order allows the operator to immediately display on the I/O console of own node the BITE Status of a visible node. Syntax: SNI [ <blank> nnn ] where: nnn Effect: SMD on own node replies the following acknowledge: "hh:mm:ss ooo SNI [ nnn] : ORDER ACCEPTED" where ooo is the three-literal identifier of own node, and then: shows on own I/O Console the BITE Status of the addressed node, in an hexadecimal dump like the following one: optional three-literal identifier of the addressed node (own node, if omitted)
UNCLASSIFIED
Page 44
UNCLASSIFIED
UNCLASSIFIED
Page 45
UNCLASSIFIED
Status message from nnn Time hh:mm:ss Date dd/mm/yyyy FUNCTION SMD ID XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX FUNCTION NSV Status status Node role role ID XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX FUNCTION ID . . . FUNCTION ID XX ccc XX XX XX XX XX XX XX XX XX XX XX XX XX
ccc XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
UNCLASSIFIED
Page 46
UNCLASSIFIED
where: nnn hh:mm:ss three-literal identifier of the node whose BITE Status is dumped hours, minutes and seconds of time as set on node nnn
dd/mm/yyyy day, month and year of date as set on node nnn ccc ID XX three-literal identifier of the CSCI (here called function) on node nnn whose logical status is dumped in the following bytes set hexadecimal value of the system unique identifier of the CSCI on node nnn whose logical status is dumped in the following bytes set hexadecimal value of a byte belonging to a bytes set containing codified information relative to the logical status of the given CSCI ccc; please refer to Appendix A for detailed information about SMD logical status node status according to NSV CSCI; this field can assume the following values: role ON FAULT DEGRADED
status
node role according to NSV CSCI; this field can assume the following values: MASTER STANDBY (i.e. SLAVE) MASTER ALONE SINGLE
Constrains: The order is not executed by SMD if: nnn is the identifier of a node not visible by own node This order is meaningful only when input on I/O console.
UNCLASSIFIED
Page 47
UNCLASSIFIED
5.4.2.1.2 SNR - Repeatedly Show Nodes Status Purpose: This order allows the operator to repeatedly display on the I/O console of own node the BITE Status sent by all nodes visible by own node. Syntax: SNR [ <blank> END ] Effect: SMD on own node replies the following acknowledge: "hh:mm:ss nnn SNR [ END] : ORDER ACCEPTED" where nnn is the three-literal identifier of own node, and then: if the parameter "END" is omitted, all BITE Status messages sent by all visible nodes will be displayed on own I/O Console, with the same format as described in 5.4.2.1.1 if the parameter "END" is present, BITE Status messages sent by all visible nodes will be no more displayed on own I/O Console Constrains: This order is meaningful only when input on I/O console.
UNCLASSIFIED
Page 48
UNCLASSIFIED
5.4.2.1.3 VER - Show CSCI(s) Version Purpose: This order allows the operator to display the software version of one / all CSCI(s) allocated on a visible node. Syntax: [ nnn <blank> ] VER <blank> ccc where: nnn ccc optional three-literal identifier of the addressed node (own node, if omitted) three-literal identifier of the addressed CSCI(s); its allowed values are: ALL ccc Effect: SMD on node nnn (own node, if omitted) replies the following acknowledge: "hh:mm:ss nnn VER ccc : ORDER ACCEPTED" and then shows to the operator, in a table like the following one, the software version of the addressed CSCI(s) on the given node: if the order applies to all CSCIs in the addressed node if the order applies to the CSCI ccc
FUNCTIONS RELEASES FUN ccc . . . ccc

where: ccc VV.rr three-literal of the CSCI (here called function) software version and release numbers of the CSCI ccc
VERSION VV.rr dd-MMM-yyyy [site] . . . VV.rr dd-MMM-yyyy [site]
dd-MMM-yyyy software date of the CSCI ccc site Constrains: optional site identifier of CSCI ccc
UNCLASSIFIED
Page 49
UNCLASSIFIED
The order is not executed by SMD if: nnn is the identifier of a node not visible by own node ccc is the identifier of a CSCI which is unknown by SMD on the addressed node
UNCLASSIFIED
Page 50
UNCLASSIFIED
5.4.2.1.4 IEP - Enable SMD Self-Diagnosis Purpose: This order allows the operator to enable or disable the self-diagnosis of SMD CSCI on own node, i.e. the presentation of all occurrences of SMD internal software errors (refer to 8.3). Syntax: IEP <blank> flag where: flag flag indicating whether the SMD self-diagnosis must be enabled; its allowed values are: Effect: SMD on own node replies the following acknowledge: "hh:mm:ss nnn IEP flag : ORDER ACCEPTED" where nnn is three-literal identifier of own node, and then: if flag is equal to ON, enable the presentation of SMD self-diagnosis if flag is equal to OFF (default), disable the presentation of SMD self-diagnosis Constrains: None. "ON" if the presentation of SMD internal errors must be enabled "OFF"if the presentation of SMD internal errors must be disabled
UNCLASSIFIED
Page 51
UNCLASSIFIED
5.4.2.2
5.4.2.3
Order examples about Presentation of Node Information SNI SNI OT2 SNR SNR END OT2 VER ALL VER SMD IEP ON IEP OFF the operator requests to display immediately on the I/O console the status message of own node the operator requests to display immediately on the I/O console the status message of node OT2 the operator requests to enable the periodical display on the I/O console all status messages of visible nodes, including own node the operator requests to disable the periodical display on the I/O console of all status message the operator requests to display the software versions of all CSCIs allocated on the node OT2 the operator requests on own node to display the software version of SMD CSCI the operator requests SMD CSCI to display its self-diagnosis messages the operator requests SMD CSCI not to display its self-diagnosis messages
5.4.3
5.4.4
5.4.5
EXAMPLES ABOUT PRESENTATION OF NODE INFORMATION The Immediate Presentation of Node status on I/O console and SMD self-diagnosis are used mainly for internal testing of SMD and other CSCIs; please refer to: Appendix A for the description of SMD status message 8.3.2 for the list of internal error messages
The Repeated Presentation of Node status is used mainly by internal CSCIs, e.g. to graphically represent the present status information.
UNCLASSIFIED
Page 52
UNCLASSIFIED
6.
OPERATIVE EXAMPLES The following orders sequence shows a typical working session of the operator: 1) 2) 3) 4) "SPW OT2" typed on OT2 node: the operator sets the password on own node "CDL 4 OT1" typed on OT2 node: the operator requests SMD to display on own node (OT2) all diagnostic messages produced by OT1 node having level greater then 0 and less or equal than 4 "VER ALL" typed on OT2 node: the operator requests to display the software versions of all CSCIs on own node (OT2) "DBR "typed on OT2 node: the operator closes his job session
UNCLASSIFIED
Page 53
UNCLASSIFIED
7.
ORDERS LIST The following table provides, for each order executed by SMD CSCI: its three-literal mnemonic its syntax its possible restrictions
orde r
CDL CPW DBR DL0 DLD IEP MST RPW SDL SLV SNI SNR SPW SUL STT UDL VER
syntax
CDL lev [nnn] [nnn] CPW new_psw] DBR DL0 flag [nnn] rrr DLD lev nnn IEP flag [nnn] MST [nnn] RPW rrr SDL ooo [nnn] SLV SNI [nnn] SNR [END] SPW password [nnn] SUL ccc STT hh del mm del ss [MM del dd del yy] [nnn] UDL lev ccc [nnn] VER ccc [old_psw new_psw
restrictions
only on own node only on own node meaningful only from I/O console meaningful only from I/O console only on own node -
UNCLASSIFIED
Page 54
UNCLASSIFIED
8. 8.1
GENERAL MESSAGES, ERRORS AND ALARMS INTRODUCTION The general messages produced by SMD toward the operator are: diagnostic messages (including alarms and software errors) acknowledges to orders
All diagnostic messages produced by SMD have the following pattern: "hh:mm:ss nnn l SMD : diagnostic_text" where: hh:mm:ss nnn l time when SMD has produced the diagnostic three-literal identifier of the node which has produced the diagnostic diagnostic level in the range 0..7
diagnostic_text text which informs about the event to be notified to the operator Please refer to 8.2 for the list of all diagnostic messages which can be produced by SMD CSCI, and to 8.4 for the list of all SMD alarm messages. SMD also produces a particular diagnostic message with level one, whose diagnostic_text has the following pattern: "INTERNAL ERROR xxxxH : yyyyH" where: xxxx yyyy code associated to the routine in which the software error has been detected sub-code which differentiates software errors inside the same routine
Please refer to 8.3.2 for the list of all internal error messages which can be produced by SMD CSCI.
All acknowledges to orders produced by SMD have the following pattern: "hh:mm:ss nnn ord [params] : ack_text" where: hh:mm:ss time when SMD has produced the acknowledge nnn ord three-literal identifier of the node which has produced the acknowledge three-literal identifier of the acknowledged order
params optional order parameters
UNCLASSIFIED
Page 55
UNCLASSIFIED
ack_text text which informs about the result of order execution; it is equal to the string ORDER ACCEPTED if the order has been correctly executed by SMD CSCI
UNCLASSIFIED
Page 56
UNCLASSIFIED
8.2
DIAGNOSTIC MESSAGES SMD CSCI produces diagnostic messages whose diagnostic_text, with relative level and explanations, are the following: BUFFER BOUNCED FROM XXXX RESULTCODE YYYY = 1) SMD has received a buffer bounced from the communication path XXXX (lev.
BUFFER LOST CAUSED BY DETACH PATH WITH EXTERNAL CLOCK X (lev. = 1) SMD received a detach path message from the external clock, therefore the buffer used for the read operation is lost CREATE$PATH FROM FUNCTION UNKNOWN = 1) an unknown CSCI requested to open the communication path with SMD DISS. NOTIFY MSG NOT EXECUTABLE = 1) SMD received a dissemination request which cannot be executed DISS. NOTIFY MSG WITH ILLEGAL PARAMETER SMD received a dissemination request containing incorrect parameters END DISS. NOTIFY MSG WITH ILLEGAL PARAMETER SMD received an end dissemination request containing incorrect parameters END OF DISPATCHING SITE XXX (lev. = 1) SMD stopped to dispatch messages from the site XXX ERROR IN CONFIGURATION OF NETWORKS = 1) SMD detected a difference on own node name between NSV and LAN driver information GETPATHSTATUS FROM XXXX : DRIVER NOT READY the status of LAN peripheral XXXX is not OK (lev. (lev. = 1) (lev. = 1) (lev.
(lev.
(lev. = 1) (lev.
MY LINE AND PARTNER NODE LINE NOT OK = 1) SMD couldnt switch the role between two nodes because both lines of slave node are faulted NO BUFFER AVAILABLE FOR STATUS DECODING = 1) SMD had no more buffers to send the BITE Status message of own node NODE XXX STATUS VARIATION ON YYYY - STATUS WWWWWWWWWW (lev. = 1) SMD notified a change in the status of a node on the LAN NOT MODM IN SMD CONFIGURATION = 1)
(lev.
(lev.
UNCLASSIFIED
Page 57
UNCLASSIFIED
SMD received a request to dispatch messages through lines which aren't in SMD PU_List OPEN$PATH REPLY NOT OK FROM MASTER CLOCK = 1) SMD failed to open the communication path with the external clock READ FROM EXTERNAL CLOCK X : WRONG DATA RECEIVED the read operation on the external clock X returned to SMD with wrong data (lev.
(lev. = 1)
RESPONDPATH FROM XXXX WITH RESULTCODE YYYY (lev. = 1) SMD failed (with resultcode YYYY) to open the communication path with the peripheral XXXX SELECT REPLY FROM XXXX WITH RESULTCODE YYYY (lev. = 1) SMD failed (with resultcode YYYY) to perform the messages selection from the peripheral XXXX
UNCLASSIFIED
Page 58
UNCLASSIFIED
SMD TO XXX PATH OVERFLOW RECOVERY (lev. = 1) the number of messages sent to CSCI XXX and not replied by it is now below a customisable limit SMD TO XXX: PATH OVERFLOW (lev. = 1) the number of messages sent to CSCI XXX and not replied by it has exceeded a customisable limit START DISPATCHING SITE XXX PU MAIN YYYY = 1) SMD begun to dispatch messages from the site XXX by means of the line YYYY THE STARTUP PHASE IS FINISHED : THE NODE IS OPERATIVE SMD notified that its start-up phase has finished (lev. = 1) (lev.
UNKNOWN MSG: OPCODE XXXX STATUS YYYY USERREF ZZZZ DATADISP WWWW MSGTYPE HHHH FUNCTION FFF (lev. = 1) SMD received from the CSCI FFF an unknown message whose code is HHHH XXXXX --> FAULT: EXTERNAL CLOCK X IS IN FAULT SMD notified that the external clock X is in fault XXXXX --> LO_OF: BUFFER BOUNCED FROM EXTERNAL CLOCK X SMD received a buffer bounced from the external clock X XXXXX --> LO_OF: EXTERNAL CLOCK X IS IN LOGICAL OFF SMD notified that the external clock X is in logical off (no messages received) XXXXX --> NT_SY: EXTERNAL CLOCK X IS NOT SYNCHRONIZED SMD notified that the external clock X is not synchronised (lev. = 1) (lev. = 1) (lev. = 1) (lev. = 1)
XXXXX --> NT_SY: EXTERNAL CLOCK X IS ON AND NOT SYNCHRONIZED (lev. = 1) SMD has notified that the external clock X is ON and not synchronised XXXXX --> NT_SY: READ FROM EXTERNAL CLOCK X : WRONG DATA RECEIVED (lev. = 1) the read operation on the external clock X returned to SMD with wrong data XXXXX --> RECOV: EXTERNAL CLOCK X HAS BEEN RECOVERED SMD has notified that the external clock X has been recovered. XXXXX --> RECOV: READ FROM EXTERNAL CLOCK X NOT OK the read operation on external clock X returned with a negative result (lev. = 1) (lev. = 1)
XXXXX --> SYNCR: EXTERNAL CLOCK X HAS RECOVERED THE SYNCHRONISM (lev. = 1) SMD has notified that the external clock X has recovered the synchronism XXXXX --> SYNCR: EXTERNAL CLOCK X IS ON AND SYNCHRONIZED SMD has notified that the external clock X is ON and synchronised XXXXX --> SYNCR: EXTERNAL CLOCK X IS SYNCHRONIZED SMD notified that the external clock X is synchronised (lev. = 1) (lev. = 1)
XXXXX --> WA_SY: EXTERNAL CLOCK X HAS LOST THE SYNCHRONISM (lev. = 1)
UNCLASSIFIED
Page 59
UNCLASSIFIED
SMD notified that the external clock X has lost the synchronism
UNCLASSIFIED
Page 60
UNCLASSIFIED
8.3
ERROR MESSAGES SMD can detect the following four types of errors, ordered by their severity: 1) Exceptions (Fatal Errors) 2) SMD Software Errors 3) Other Software Errors 4) Operators Errors with consequent HALT of the node caused by SMD CSCI itself caused by other interfacing CSCIs caused by wrong operators requests
8.3.1
EXCEPTIONS The Exceptions that can be raised by SMD are the following:
hex code 0101 0102 0103 0104 0105 0106 0107 0108 0109 010A 010B 010C 010D 010E 010F 0110 0111 0112
explanation of the fatal error SMD has requested a mailbox creation to Operating System but this service was not successful during SMD pool creation the Operating System has rejected a buffer request SMD has requested a path creation towards NSV but Operating System has rejected the request SMD has requested a path creation towards NSV but this CSCI has rejected the request SMD has requested a Timer creation to Operating System but this service was not successful SMD is not present in the table which describes the nodal CSCIs NSV is not present in the table which describes the nodal CSCIs the Go Message does not contain own node name SMD cannot open the path with a peripheral because the UCB List is full SMD has requested a path creation with a device but Operating System has rejected this service SMD has on-line requested a data segment to Operating System but the service was not successful SMD has to use too many devices than maximum number of handled devices NSV has assigned a peripheral type to SMD that does not handle it SMD cannot open the path with a peripheral because the Devices Table is full the Go Message assigns a peripheral to SMD that does not find it into own configuration the Go Message assigns too many LANs to SMD than maximum number of handled LANs the Go Message assigns too many Lines to SMD than maximum number of handled Lines the Operating System has rejected an on-line SMD buffer request due to end of memory
UNCLASSIFIED
Page 61
UNCLASSIFIED
0113 0114 0115 0116 0117
the Go Message assigns too many Clocks to SMD than maximum number of handled Clocks SMD has requested a Process creation to Operating System but this service was not successful SMD has requested a Semaphore creation to Operating System but the service was not successful SMD has requested a do case operation to Operating System but an error occurs SMD has requested a data copy operation to Operating System but an overflow occurs
UNCLASSIFIED
Page 62
UNCLASSIFIED
8.3.2
SMD SOFTWARE ERRORS All SMD Software Errors are signalled by SMD with a diagnostic message with level one, whose diagnostic_text has the following pattern: "INTERNAL ERROR xxxxH : yyyyH" The Software Errors that can be issued by SMD are the following:
xxxx 0014 001E 0037 003C 003C 0041 0046 005A 005A 005A 005A 005A 0064 006E 0078 0082 0082 0082 008C 00A0 00AA
yyyy yyyy yyyy 0064 000A yyyy yyyy yyyy 000A
un 00AA 0032 ack_from_executor_f un 00AA 0046 ack_from_executor_f un 00AA 0078 ack_from_executor_f un 00AA 006E ack_from_executor_f un 00AA 0064 ack_from_executor_f un 00AA yyyy ack_from_executor_f un 00B4 yyyy order_disp 00BE yyyy notify_ack_fun 00CA yyyy notify_lan_message_fun 00CB yyyy lan_msg_request_fun 00CC 0001 insert_maint_node 00CD 0005 receive_lan_status_f
the pointer of the message coming from a nodal CSCI or from NSV is NIL the origin and/or the operation code of a Diagnostic Notify message is erroneous the origin and/or the operation code of a Diagnostic Message is erroneous the origin and/or the operation code of a CDL order is erroneous the site name received in a message coming from network isn't equal to own site name 0014 cons_table_fun the site name received is not present into the table 001E cons_table_fun the site name received in a message coming from line isn't equal to own site name 0028 cons_table_fun the site name received is not present in the table yyyy cons_table_fun the origin and/or the operation code of a user table is erroneous yyyy prod_table_fun the origin and/or the operation code of a producer table is erroneous yyyy diag_req_pas_fun the origin and/or the operation code of a CDP order is erroneous 0001 smista_diag_msg SMD received a Diagnostic Message from a node belonging to an unknown site 0014 order_msg_fun SMD received a wrong message from network 0064 order_msg_fun SMD received a wrong message from line yyyy order_msg_fun the origin and/or the operation code of a Order Message is erroneous yyyy order_req_fun the origin and/or the operation code of a Order Request Message is erroneous yyyy ack_to_function_fun the origin and/or the operation code of a Ack to Function Message is erroneous 0028 ack_from_executor_f SMD received an Acknowledge from CSCI with Ack Type field = 0 (erroneous) SMD received an Acknowledge from CSCI with Ack Type field > 3 (erroneous) SMD received from LAN an Acknowledge From Executor with Ack Type field = 0 SMD received from LAN an Acknowledge From with Ack Type field > 3 SMD received from Line an Acknowledge From Executor with Ack Type field = 0 SMD received from Line an Acknowledge From Executor with Ack Type field > 3 the origin and/or the operation code of an Acknowledge From Executor is erroneous the Order module received an unexpected message the origin and/or the operation code of a Notify Ack Message is erroneous the origin and/or the operation code of a Notify LAN Message is erroneous the origin and/or the operation code of a LAN Message Request is erroneous the node is already present into the Maintenance Nodes table the text length is wrong
procedure diag_disp level_modify_fun dispatch_this_messa ge diag_notify_fun diag_notify_fun diag_msg_fun diag_req_fun cons_table_fun
explanation of the internal error the Diag module received an unexpected message the origin and/or the operation code of a Level Modify message is erroneous SMD cannot elaborate the message because it cannot have the needful buffer
UNCLASSIFIED
Page 63
UNCLASSIFIED
un 00CD 0006 receive_lan_status_f the text length is wrong un 00CD yyyy receive_lan_status_f the origin and/or the operation code of a Receive LAN Status is erroneous un 00D2 0001 smd_order_disp the order has been refused, then it will not be sent toward the other CSCIs which 00D2 00DC 00DE 00E0 00E4 00F0 00FA 0104 0002 yyyy yyyy yyyy yyyy yyyy yyyy 0005 smd_order_disp clock_disp settime_msg_fun time_reass_fun time_sync_msg_fun visual_ver_fun dis_order_fun ack_to_pass_cons_fu n ack_to_pass_cons_fu n ack_to_pass_cons_fu n ack_to_pass_cons_fu n ack_to_pass_cons_fu n ack_to_pass_cons_fu n lok_ord_fun receive_lok_tab_fun receive_lok_tab_fun node_mode node_mode notify_request_fun notify_request_fun notify_request_fun notify_ack_pass_fun notify_ack_pass_fun notify_ack_pass_fun notify_ack_pass_fun notify_ack_pass_fun notify_ack_pass_fun notify_ack_pass_fun
uses it SMD received an irregular Order to be executed by SMD itself the Clock module received an unexpected message the origin and/or the operation code of a SetTime message is erroneous the origin and/or the operation code of a TimeReassigned message is erroneous the origin and/or the operation code of a TimeSynchronism message is erroneous the origin and/or the operation code of a VER order is erroneous the origin and/or the operation code of a DIS order is erroneous ( ref. to [2] ) site number not found into the table SMD received Acknowledge to diagnostic passive users from LAN with Ack Type = 0 SMD received Acknowledge to diagnostic passive users from LAN with Ack Type > 3 SMD received Acknowledge to diagnostic passive users from Line with Ack Type = 0 SMD received Acknowledge to diagnostic passive users from Line with Ack Type > 3 the origin and/or the op. code of Acknowledge to diagnostic passive users is erroneous the origin and/or the operation code of a RDS Lock order is erroneous the LOK order is requested but own node isn't in lock enable the origin and/or the operation code of the Table of RDS lock owners is erroneous SMD received an Operative Mode Notify which contains an erroneous field mode the node is already present into the Maintenance Nodes Table SMD received a Notify Ack Request from CSCI with Ack Type = 0 SMD received a Notify Ack Request from CSCI with Ack Type > 3 the origin and/or the operation code of a Notify Ack Request Message is erroneous site number not found into the table SMD received a Notify Ack to diagnostic passive users from LAN with Ack Type = 0 SMD received a Notify Ack to diagnostic passive users from LAN with Ack Type = 3 SMD received a Notify Ack to diagnostic passive users from LAN with Ack Type > 3 SMD received a Notify Ack to diagnostic passive users from Line with Ack Type = 0 SMD received a Notify Ack to diagnostic passive users from Line with Ack Type > 3 the origin and/or the op code of a Notify Ack to diagnostic passive users is erroneous the origin and/or the operation code of a MST order is erroneous the origin and/or the operation code of a SLV order is erroneous lock request refused because the sender node is not present into the lock priority table site number not found into the table site number not found into the table the origin and/or the operation code of a MEM order is erroneous the origin and/or the operation code of a MLM order is erroneous the value of the pointer that must be released to the internal pool is NIL the syntax of the input order isn't correct the syntax of the requested command isn't correct
0104 0046 0104 0078 0104 006E 0104 0064 0104 yyyy 010E 0118 0118 011D 011D 011E 011E 011E 011F 011F 011F 011F 011F 011F 011F yyyy 0007 yyyy 000A 0014 0014 0032 yyyy 0005 0064 000A 005A 0050 0028 yyyy
0120 yyyy mst_order_fun 0121 yyyy slv_order_fun 0123 0064 lok_ord_disp 0123 0123 012C 0136 014A 014F 015F 006E 0078 yyyy yyyy 0064 012C 0064 lok_ord_disp lok_ord_disp mem_order_fun mlm_order_fun put_pool lff_order_fun sul_diag_fun
UNCLASSIFIED
Page 64
UNCLASSIFIED
0160 012C iep_diag_fun the syntax of the requested command isn't correct 0161 yyyy dld_tbl_management_fu the origin and/or the operation code of a DLD Table Management is erroneous
n
0162 yyyy global_prod_tab_fun the origin and/or the operation code of Global Production Table is erroneous 0168 yyyy diag_pass_cons_fun the origin and/or the operation code of a Diagnostic To Passive Message is 0172 0172 018B 018D 018E 018E 018E 018F 0190 019A 019A 019A 019A 000A yyyy yyyy yyyy 00C8 0064 012C 0064 yyyy 0001 0002 0003 0004
01A4 000A 01A4 yyyy 01AE yyyy 01B8 yyyy 01C2 yyyy 01C2 000A 01C2 000B 01C2 000C 01CC yyyy 01D6 01E0 01F4 01FE 0208 yyyy yyyy yyyy yyyy yyyy
n 0212 yyyy disable_request_fun 021C yyyy enable_request_fun 0226 0001 disp_open_path
erroneous the pointer of the message coming from a nodal CSCI or from NSV is NIL the origin and/or the operation code of a Alarm Message is erroneous the origin and/or the operation code of a DL0 order is erroneous the origin and/or the operation code of a UDL order is erroneous apparatus not present into the table site name not present into the table the message coming from a RDS node the message isn't of line type the Init module received an unexpected message SMD received a path request from a CSCI which already has the path with SMD SMD cannot open a path with a user because the UCB List is full SMD cannot open a path with a user because the Version Table is full A CSCI has already sent to SMD its version by means of a Version Notify Message and therefore the version included in the present Path Request cannot be used diss_notify_fun SMD received a Dissemination Notify not congruent with SMD configuration data diss_notify_fun the origin and/or the operation code of a Dissemination Notify message is erroneous end_diss_fun the origin and/or the operation code of an End Dissemination Notify is erroneous select_main_fun the origin and/or the operation code of a Selection of Main LAN message is erroneous iosp_select_fun the origin and/or the operation code of a Selection Reply message is erroneous iosp_select_fun SMD received a Selection Reply but doesn't find the item of UCB List of the peripheral iosp_select_fun SMD received a Selection Reply but doesn't find the item of Devices Table of peripheral iosp_select_fun SMD received a Selection Reply message but the operation is failed path_status_fun the origin and/or the operation code of a Get Path Status Reply message is erroneous lan_status_fun the origin and/or the operation code of a LAN Status message is erroneous him_fault_fun the origin and/or the operation code of a HIM Fault message is erroneous go_message_fun the origin and/or the operation code of a Go Message is erroneous terminate_msg_fun the origin and/or the operation code of a Node Terminate message is erroneous console_message_fu the origin and/or the operation code of a Console Message is erroneous
alarm_msg_fun alarm_msg_fun level_zero_req_fun udl_order_fun dld_diag_fun dld_diag_fun dld_diag_fun sdl_diag_fun init_disp create_path_fun create_path_fun create_path_fun create_path_fun
the origin and/or the operation code of a DBR order is erroneous the origin and/or the operation code of a SPW order is erroneous SMD received a Create Path Reply but doesn't find the item of UCB List of peripheral 0226 0002 disp_open_path SMD received a Create Path Reply but doesn't find the item of Devices Table 0230 0000 open_path_fun the origin and/or the operation code of a Open Reply from external clock is erroneous 0244 yyyy resetta_password_fu the origin and/or the operation code of a RPW order is erroneous
n 024E yyyy cambia_password_fu the origin and/or the operation code of a CPW order is erroneous n 0253 000A pu_status_fun the information length about the node status isn't correct 0253 yyyy pu_status_fun the origin and/or the operation code of a PU Status Message is erroneous
UNCLASSIFIED
Page 65
UNCLASSIFIED
0254 yyyy status_pl_fun 0255 yyyy version_msg_fun 0255 000A version_msg_fun 0255 0256 0258 0262 026C 026C 0014 0064 yyyy yyyy 0014 001E
026C yyyy 0276 000A
n 0276 yyyy status_immediate_fu n 0280 yyyy status_repeated_fun 028A 000A node_status_msg_fu n 028A yyyy node_status_msg_fu n 0294 yyyy status_reset_fun 02BC 000A dispatcher 02C1 0001 bounce$main 02C1 0002 bounce$main 0320 yyyy interface_disp 032A yyyy rebuild_msg_fun 0334 033E 033E 0348 yyyy 0001 0002 0001
the origin and/or the operation code of a Status PL Message is erroneous the origin and/or the operation code of a Version Notify Message is erroneous the Versions Table is full and therefore SMD must reject the received Version Notify version_msg_fun a CSCI already sent its version to SMD therefore the Version Notify cannot be used syntax_control the syntax of SLO order isn't correct stat_disp SMD error, the Stat module received an unexpected message status_msg_fun the origin and/or the operation code of a Status Message is erroneous status_notify_fun the buffer containing the node status is full status_notify_fun a CSCI has sent to SMD a Status Message whose length is different from previous Status status_notify_fun the origin and/or the operation code of a Status Notify Message is erroneous status_immediate_fu site number not present into the table the origin and/or the operation code of a SNI order is erroneous the origin and/or the operation code of a SNR order is erroneous site number not present into the table the origin and/or the operation code of a Node Status Message is erroneous the origin and/or the operation code of a Status Reset is erroneous SMD received an unexpected reply without corresponding SMD send operation SMD received an unexpected reply without corresponding SMD send operation number of message = 0 (send operation without incrementing the counter NUM$MG) the Interface module received an unexpected message the origin and/or the operation code of a message subdivided in packets is erroneous the origin and/or the operation of the service messages is erroneous the message is addressed to own node but the sender is not the twin node own node is not a node of a matched pair SMD received the question about his line, but it isn't the twin node of the sender node the Nonstand module received an unexpected message SMD received a Non Standard Message from LAN with Ack Type = 0 SMD received a Non Standard Message from LAN with Ack Type = 0 or the Message Type of a Non Standard Message is not in the range of the types A, B SMD received a Non Standard Message from Line with Ack Type = 0 SMD received a Non Standard Message from with Ack Type > 2 or the Message Type of a Non Standard Message is not in the range of the types A, B SMD received a Non Standard Message from CSCI with Ack Type = 0 SMD received a Non Standard Message from with Ack Type > 2 or the Message Type of a Non Standard Message is not in the range of the types A, B the origin and/or the operation code of a Non Standard Message is erroneous the origin and/or the operation code of a TCR order is erroneous ( ref. to [2] ) the origin and/or the operation code of a North Message is erroneous
service_dispatching_fun
line_commutation line_commutation prepare_question
0384 yyyy nonstand_disp 038E 000A nonstand_msg_fun 038E 0014 nonstand_msg_fun
038E 001E nonstand_msg_fun 038E 0028 nonstand_msg_fun
038E 0032 nonstand_msg_fun 038E 003C nonstand_msg_fun
038E yyyy nonstand_msg_fun 0398 yyyy tcr_order_fun 03A2 yyyy functional_north_msg_fu

n un
03AC yyyy clock_status_variation_f the origin and/or the operation code of a Clock Status Variation is erroneous 03B6 yyyy clock_handler
the origin and/or the operation code of a Clock Handler is erroneous
UNCLASSIFIED
Page 66
UNCLASSIFIED
03E8 0001 invia_msg 03E8 0002 invia_msg 05DD yyyy slo_order_fun
SMD doesn't find the pointer of the UCB item of output message addressee SMD, during the output of a message, finds erroneous the field UCB the origin and/or the operation code of a SLO order is erroneous
UNCLASSIFIED
Page 67
UNCLASSIFIED
8.3.3
OTHER SOFTWARE ERRORS The negative Result-Codes that can be returned by SMD to the other CSCIs are the following: hex. code 1 2 3 4 5 6 7 8 0A 0B 0C 0D 11 12 13 14 15 16 17 explanation of the error SMD produced a codified diagnostic of Internal Error type a CSCI sent to SMD an order with wrong syntax, and therefore the order was rejected a CSCI sent an Order List to SMD but the number of orders class exceeds its maximum value a CSCI has notified own Logical Status to SMD but the Node Status buffer is already full a CSCI has sent a request to SMD but this cannot be executed SMD has received an order to be dispatched to user CSCIs, but the order time-out expired a CSCI already sent its version to SMD, therefore the received Version Notify cannot be used the CSCI Versions Table is full, therefore SMD must reject the received Version Notify an SMD order is in progress and only at its end SMD will be able to execute other orders SMD has received an order to dispatch to user CSCIs but the order got lost a CSCI has attempted to enter in the system without setting the password a CSCI has attempted to send an order towards RDS but own node is not the lock owner SMD has received an unknown message SMD has received a request before receiving the Go Message from NSV SMD has received a notify ack having a size greater than the size of SMD buffers SMD has received the lock request for an unknown radar site SMD has received the request to send out a local order SMD has received an order inconsistent with the role of the node the typed string is not correct
UNCLASSIFIED
Page 68
UNCLASSIFIED
8.3.4
OPERATORS ERRORS The negative acknowledges that can be returned by SMD after operators orders are the following: EXECUTOR NOT FOUND the operator has typed an order but SMD does not find any executor CSCI ILLEGAL PARAMETER the operator has typed an SMD order using a wrong syntax, therefore the order is rejected by SMD ILLEGAL PASSWORD the operator has attempted to enter a wrong password IMPOSSIBLE TO SWITCH SMD has received a MST or SLV order, but the role of the node is master alone INCONSISTENCE ORDER WITH MASTER STATUS OF NODE SMD has received a MST order, but the role of the node is already master INCONSISTENCE ORDER WITH STANDBY STATUS OF NODE SMD has received a SLV order but the role of the node is already slave LOCK BELONGS TO ANOTHER NODE the operator requested own node to become the RDS lock owner, but another node already owns the lock MAINTENANCE ENABLED MODE : ORDER NOT ACCEPTED the operator has produced an order which cannot be accepted by SMD, because it would set the matched pair of nodes in an inconsistent status MAINTENANCE LOCKED MODE : ORDER NOT ACCEPTED the operator has produced an order which cannot be accepted by SMD, because it would set the matched pair of nodes in an inconsistent status NO ORDERS CLASS IS LOCKED the order can't be executed because no orders class is locked NODE NAME NOT IN MATCHED PAIRS TABLE SMD does not find the name of the own node into the table of matched pair nodes, therefore cannot know the name of the partner node NODE WITHOUT LOCK : ORDER NOT EXECUTED the operator has attempted to send an order towards an RDS, or he has attempted to release the RDS lock, but own node is not the lock owner OPERATIONAL MODE: ORDER NOT ACCEPTED the operator has produced an order which cannot be accepted by SMD, because it would set the matched pair of nodes in an inconsistent status ORDER ALREADY IN PROGRESS a previous order is in progress, thus only after its completion SMD will be able to execute next order ORDER NOT ACCEPTED: AN STT ORDER IS ALREADY IN EXECUTION the operator has requested an STT order, but the execution of previous STT order is still in progress ORDER NOT ACCEPTED: NODE IN STARTUP PHASE the operator has requested an order that the node in start-up phase can't accept ORDER NOT ACCEPTED: SYSTEM ALREADY SYNCHRONIZED
UNCLASSIFIED
Page 69
UNCLASSIFIED
the operator has requested the STT order, but the system is already synchronised by external clock ORDER NOT ACCEPTED: THE INHIBITION TIME IS ACTIVE the operator requested an STT order with the hour near midnight, or the system time is near midnight ORDER NOT ACCEPTED: THE STATUS OF XXX SITE NODES IS UNKNOWN the lock order is refused because the nodes status of the referred site is not OK ORDER NOT ACCEPTED: UNKNOWN SITE the operator has request the lock of an unknown radar site ORDER NOT ACCEPTED: WRONG INFORMATION ABOUT SENDER NODE the lock request is refused because the sender node is not present into the lock-priority table ORDER NOT EXECUTED: UNKNOWN FUNCTION the typed order is referred to an unknown CSCI ORDER NOT SENT: NODE DISCONNECTED the typed order is refused because the node is not connected on LAN or it is in fault ORDER NOT SENT: XXX SITE DISCONNECTED the typed order is refused because the addressed site is not connected with own site ORDER TIMEOUT EXPIRED the operator has typed an order but no CSCI has executed it within a customisable time-out RDS LOCK IS NOT ENABLED ON THIS NODE the RDS lock request is refused because lock service is not enabled on the addressed node THE OBJECT NODE HAS THE LOCK : ORDER NOT ACCEPTED the node addressed by the request is the RDS lock owner, therefore cannot go to an operative status which is not congruent with lock possession THE OBJECT NODE IS NOT ENABLED TO MAINTENANCE MODE MEM order cannot be accepted because the maintenance service is not enabled on the addressed node THE OBJECT SITE IS OPS: LOCK NOT ACCEPTED the operator has requested the lock of an Operative Site instead of a Radar Site THE RECEIVED ORDER IS LOCAL FOR XXX NODE: ORDER NOT ACCEPTED the typed order is local for another node THE STT ORDER IS REFUSED BECAUSE IT NOT CONTAINS THE DATE the date has never been set before in the system, and the STT order doesnt provide it THE TYPED ORDER IS LOCAL FOR XXX NODE: ORDER NOT ACCEPTED the operator has attempted to send out an order, but this order is local for own node XXX YOUR NODE ALREADY OWNS RDS LOCK : ORDER NOT ACCEPTED the LOK order is useless because own node is already the RDS lock owner YOUR NODE HAS NOT NEEDFUL PRIORITY : ORDER NOT ACCEPTED another node has higher lock-priority than own node, which therefore cannot become RDS lock owner YOUR NODE ROLE IS SINGLE: ORDER NOT ACCEPTED the operator has requested a masterslave commutation, but the role of own node is single YOUR NODE ROLE IS SLAVE : ORDER NOT ACCEPTED the role of own node is slave, therefore own node cannot become RDS lock owner
UNCLASSIFIED
Page 70
UNCLASSIFIED
8.3.5
ALARM MESSAGES The format of the SMD alarm messages is the same of SMD diagnostic messages (refer to 8.1); the only alarm that can be issued by SMD is the following: "THE COMMUNICATION WITH LOCK HANDLER WAS INTERRUPT - THE LOCK IS LOST" (lev. 2) the lock owner node is no more connected with the lock handler node, and therefore it releases the RDS lock; this can happen only if the lock owner was an OPS node, otherwise in this case the lock owner becomes itself lock handler
UNCLASSIFIED
Page 71
UNCLASSIFIED
9.
DEGRADED WORKING During its operation SMD uses the following devices: LAN, usually redundant, for the communication among nodes in own site (RDS and OPS) serial line, usually redundant, for the communication between radar and operative sites external clock, usually redundant, for system time alignment The possible degraded situations for SMD are consequently the following:
one of the two LANs of a site are faulted: SMD transmits and receives data to / from both LANs, therefore this degraded situation does not cause any loss of messages for SMD all the LANs of a site are faulted: the SMDs on own site can no more communicate each other, therefore the operator can not obtain on a node information about the other nodes of own site, and can not send orders towards them; moreover, if the LANs fault occurs in a radar site, the communication between the given RDS and the connected OPS(s) is stopped, with the exception of the RDS bridge nodes
the serial line between a (bridge) node of an RDS and a connected OPS is faulted: SMD on the given bridge node is no more able to use its line to send messages to the given OPS, therefore it will send them, through the RDS LAN, to the partner bridge node, which will forward them, through its undamaged line, to the given OPS; the node in OPS which is in charge of the SMD dissemination of the given RDS will detect the line fault, and will switch, if necessary, the role MAINRESERVE of the RDS lines; therefore, this degraded situation does not cause any loss of messages for SMD both serial lines between the (bridge) nodes of an RDS and a connected OPS are faulted: the SMDs on all nodes of the given RDS can no more communicate with the SMDs on the nodes of the given OPS, therefore the operator on whatever node of the given OPS can no more send orders / receive information to / from all nodes of the given RDS one external clock is faulted or no more synchronised: SMD is able to receive time information from both external clocks, therefore this degraded situation does not cause any loss of messages for SMD both external clocks are faulted or no more synchronised: SMD can no more receive synchronised time information from the external clocks, therefore the system time is extrapolated by the internal clock of the computer having higher priority in the system; the nodal CSCIs are no more able to perform Time Stamping operations START-UP OPERATIVE PROCEDURE When a node starts, there is a period of time during which SMD does not know the status of the other connected nodes which are already started; during this start-up phase, SMD cannot perform the following critical activities, because they require the knowledge of the status of the connected nodes: receiving orders from other nodes sending orders towards other nodes executing the orders STT, MST, SLV performing the bridge node service between RDS and OPS
10.
UNCLASSIFIED
Page 72
UNCLASSIFIED
SMD carries out its start-up phase when it has received at least one BITE Status message from each LAN of own site (or after a customisable period of time).
UNCLASSIFIED
Page 73
UNCLASSIFIED
11. 11.1
APPENDIXES APPENDIX A: DESCRIPTION OF SMD STATUS MESSAGE 1 byte 1 byte Identifier of the sender CSCI 00 = SMD CSCI Operative Mode of sender node 07 = operational 04 = maintenance (enabled or locked) Lock property 03 = sender node is lock owner of an RDS in the system 07 = sender node is not lock owner of any RDS Lock owner site (meaningful only for lock handler node in RDS) 0 = RDS not locked <> 0 = number of the site locking the RDS FFH = information not available to the sender node
1 byte
1 byte
2 bytes spare 1 byte for every node connected to first LAN of sender site (if any) 03 = the given node is present on first LAN 02 = the given node is absent on first LAN FFH = information not available to the sender node for every node connected to second LAN of sender site (if any) 03 = the given node is present on second LAN 02 = the given node is absent on second LAN FFH = information not available to the sender node
1 byte
4 bytes for every serial line connected to the sender node (if any, and if to be diagnosed by SMD): 1 byte 1 byte Line Identifier Line Tx Status 01 = RESERVE 02 = FAULT 03 = ON 04 = OFF 06 = UNKNOWN Line Rx Status 01 = RESERVE 02 = FAULT 03 = ON 04 = OFF 06 = UNKNOWN Line role 00 = main 01 = reserve (no logical connection) (no physical connection) (last message correctly transmitted) (last message not correctly transmitted) (no messages ever transmitted) (no logical connection) (no physical connection) (messages are continuously received by SMD) (messages are no more received by SMD) (no messages ever received)
1 byte
1 byte
UNCLASSIFIED
Page 74
UNCLASSIFIED
FFH
= information not available (dummy line)
UNCLASSIFIED
Page 75
UNCLASSIFIED
5 bytes for every external clock connected to sender node (if any): 1 byte 1 byte Clock Identifier Clock 00 02 03 04 05 Status = START-UP = FAULT = SYNCHRONISED (synchronised messages received by SMD) = LOGICAL OFF (no messages received by SMD) = NOT SYNCHRONISED (unsynchr. messages received by SMD)
2 bytes spare set to FFH 1 byte Clock 00 01 FFH Role = main = reserve = information not available
1 byte
Clocks Synthesis (if any clock is connected to sender node) 03 = at least one clock is SYNCHRONISED 04 = both clocks are OFF or FAULTED 05 = no clock is SYNCHRONISED but at least one clock is NOT SYNCHRONISED (i.e. it is neither OFF nor FAULTED)
4 bytes for every serial line connected to the sender node and handled by SMR CSCI(if present on the sender node); same fields and values as for SMD lines 1 byte for SMR status on first LAN (if SMR is present on the sender node) 02 = the connection of the sender node on first LAN is OK 03 = the connection of the sender node on first LAN is NOT OK FFH = information not available
If the SMD status message is sent to a phase 1 site, the format of the message remains almost the same except for: the field Lock property is replaced by the field Diag_Level, which represents the maximum diagnostic level to be produced by the sender node, plus one the field Lock owner site and the two subsequent spare bytes are missing
UNCLASSIFIED
Page 76
UNCLASSIFIED
11.2 "RD1", "RF1", "MN1", "D17", "D26", "D35", "D44", "D53", "D62", "D71", "D79", "T06", "L06", "L14", "L22",
APPENDIX B: BUCHAREST SMD NODES LIST "RD2", "RF2", "MN2", "D18", "D27", "D36", "D45", "D54", "D63", "D72", "D80", "T07", "L07", "L15", "L23", "RD3", "RF3", "D11", "D19", "D28", "D37", "D46", "D55", "D64", "D73", "L29", "T08", "L08", "L16", "L24", "RD4", "RF4", "D12", "D21", "D29", "D38", "D47", "D56", "D65", "D74", "T01", "L01", "L09", "L17", "L25", "RP1", "CM1", "D13", "D22", "D31", "D39", "D48", "D57", "D66", "D75", "T02", "L02", "L10", "L18", "L26", "RP2", "CM2", "D14", "D23", "D32", "D41", "D49", "D58", "D67", "D76", "T03", "L03", "L11", "L19", "L27", "FP1", "MT1", "D15", "D24", "D33", "D42", "D51", "D60", "D68", "D77", "T04", "L04", "L12", "L20", "L28" "FP2", "MT2", "D16", "D25", "D34", "D43", "D52", "D61", "D69", "D78", "T05", "L05", "L13", "L21", /* /* /* /* /* /* /* /* /* /* /* /* /* /* /* 01..08 */ 09..16 */ 17..24 */ 25..32 */ 33..40*/ 41..48 */ 49..56 */ 57..64 */ 65..72 */ 73..80 */ 81..88 */ 89..96 */ 97..104 */ 105..112 */ 113..119 */
UNCLASSIFIED
Page 77
UNCLASSIFIED
11.3
APPENDIX C: ARAD SMD NODES LIST
"RD1", "MT2", "D06", "D14", "L13", "D33", "D41", "L29", "L33", "L07",
"RD2", "MN1", "D07", "D15", "L14", "D34", "D42", "L30", "L34", "L08",
"FP1", "MN2", "D08", "D16", "L15", "L19", "D43", "D51", "L01", "L09",
"FP2", "D01", "D09", "D17", "L16", "L20", "D44", "D52", "L02", "L10",
"RF1", "D02", "D10", "D21", "L17", "L21", "L25", "D53", "L03", "L11",
"RF2", "D03", "D11", "D22", "L18", "L22", "L26", "D54", "L04", "L12"
"CM1", "D04", "D12", "D23", "D31", "L23", "L27", "L31", "L05",
"MT1", "D05", "D13", "D24", "D32", "L24", "L28", "L32", "L06",
/* /* /* /* /* /* /* /* /* /*
01..08 09..16 17..24 25..32 33..40 41..48 49..56 57..64 65..72 73..78
*/ */ */ */ */ */ */ */ */ */
UNCLASSIFIED
Page 78
UNCLASSIFIED
11.4
APPENDIX C: CONSTANTA SMD NODES LIST
"RD1", "MT2", "D06", "D26", "L04", "L12",
"RD2", "MN1", "D07", "D27", "L05", "D43",
"FP1", "MN2", "D08", "D28", "L06", "D44",
"FP2", "D01", "D09", "D29", "L07", "D45",
"RF1", "D02", "D10", "D30", "L08", "D46"
"RF2", "D03", "D11", "L01", "L09",
"CM1", "D04", "D12", "L02", "L10",
"MT1", "D05", "D25", "L03", "L11",
/* /* /* /* /*
01..08 09..16 17..24 25..32 33..40
*/ */ */ */ */
UNCLASSIFIED
Page 79

Um XSD Es010006101um11 B

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Um XSD Es010006101um11 B

Uploaded by

Copyright:

Available Formats

UNCLASSIFIED

Doc N. ES010006101UM11 Iss.

PROGRAM: Romania Upgrade - Phase 1

System Message Dispatcher (XSD)

ISSUED BY : SELEX Sistemi Integrati Via Tiburtina km 12,4 - Roma ITALY

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

NON CLASSIFICATO CONTROLLATO RISERVATO RISERVATISSIMO SEGRETO SEGRETISSIMO

UNCLASSIFIED RESTRICTED CONFIDENTIAL SECRET TOP SECRET

Doc N. ES010006101UM11 Iss.

...................................................... (Valter Ciaraffo)

Approved by: (Program Manager)

...................................................... (Sergio Arceri)

Doc N. ES010006101UM11 Iss.

REVISIONS RECORD SHEET This sheet is a record of revisions to this document.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Acronyms and Abbreviations:

Doc N. ES010006101UM11 Iss.

Orders syntax conventions:

Message syntax conventions:

Doc N. ES010006101UM11 Iss.

I/O Console interface

Graphic WorkStation interface

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

System Orders Syntax

[ site | node <blank> ] [ class <blank> ] order [ <blank> params ]

System Orders Dispatching

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

VIDEO PRESENTATIONS None.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Orders sequences No specific orders sequence applies to this functionality.

MASKS Not applicable.

Doc N. ES010006101UM11 Iss.

FILTERING AND DISPATCHING OF DIAGNOSTIC MESSAGES

VIDEO PRESENTATIONS Please refer to 5.4.2.1.4 and 5.4.2.1.6 .

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

Doc N. ES010006101UM11 Iss.

USERS LEVEL Func ccc . . . ccc