0029200000000MA07_2-0_ADM-UM

(1)

S

SyysstteemmAAddmmiinniissttrraattoorr

U

UsseerrMMaannuuaal l

Use or Disclosure of this information is subject to the restrictions on the tile page of this document

Page A-1

Supply, Installation, Testing and

Commissioning

of Tower ATS

Automation System

S

y

s

t

e

m

A

d

m

i

n

i

s

t

r

a

t

o

r

U

s

e

r

M

a

n

u

a

l

(

A

D

M

-

U

M

)

Edition:2 Revision: 0

1 November2010

Document Number: 0029200000000MA07

Prepared for:

AIRPORTS AUTHORITY OF INDIA (AAI)

Airports Authority of India,

Rajiv Gandhi Bhawan, Safdarjung Airport, New Delhi - 110

Prepared by:

Indra Sistemas, S.A.

Ctra. de Loeches, 9 28850 Torrejón de Ardoz

Madrid, Spain

Indra Proprietary Information

This document contains proprietary data pertaining to items, or components, or processes or other matter developed or acquired at the private expense of the Indra Sistemas, S.A. and/or any other titular holder and is restricted to use only by Indra or the Customer under the terms of this Proposal. Neither said document nor said data shall be furnished or disclosed to or copied or used by other persons

outside the conditions of this Proposal as applicable without the express written approval of Indra Sistemas and/or any other titular holder.

(2)

S

U

Page A-2

(3)

(4)

S

U

Page A-4

(5)

S

U

Page A-5

PAGE EDITION AND REVISION RECORD

This document contains the following pages in the indicated editions and revisions

PAGE EDITION REVISION PAGE EDITION REVISION PAGE EDITION REVISION

All Draft 0

All 01 0

(6)

S

U

Page A-6

(7)

S

U

Page A-7

REGISTER OF CHANGES TO THE DOCUMENT

EDITION REVISION DATE AFFECTED PAGES REASON FOR CHANGE

1 0 2010-07-30 All First Edition 02 00 2010-11-02 All Second Edition

(8)

S

U

Page A-8

(9)

S

U

Page A-9

Table of Contents

1 Scope ... A-3 1.1 General purpose ... A-3 1.2 General system overview ... A-3 2 Software Components Detailed Description ... A-7

2.1 FDP ... A-7 2.1.1 Files layout ... A-7 2.1.2 FDP processes ...A-12 2.1.3 Backup recovery ...A-13 2.1.4 FDP installation ...A-13 2.1.4.1 User configuration ...A-13 2.1.4.2 Folders configuration ...A-14 2.1.5 Application configuration ...A-15 2.1.6 Backup creation ...A-15 2.2 SDP ...A-16

2.2.1 Files layout ...A-16 2.2.2 SDP processes ...A-19 2.2.3 SDP installation ...A-19 2.2.3.1 User configuration ...A-19 2.2.3.2 Folders configuration ...A-20 2.2.4 Application configuration ...A-21 2.2.5 Backup creation ...A-21 2.3 CMD ...A-22

2.3.1 Files layout ...A-22 2.3.2 CMD processes ...A-26 2.3.3 CMD installation...A-27 2.3.3.1 User configuration ...A-27 2.3.3.2 Folders configuration ...A-28 2.3.4 Application configuration ...A-28 2.3.5 Backup creation ...A-29 2.4 SDD ...A-31 2.4.1 Files layout ...A-31 2.4.2 SDD processes ...A-38 2.4.3 SDD combined with FDD Processes ...A-38 2.4.4 SDD combined with FDD installation...A-38 2.4.4.1 User configuration ...A-38 2.4.4.2 Folders configuration ...A-39 2.4.5 Application configuration ...A-40

(10)

S

U

Page A-10

2.4.5.1 SDD configuration ...A-40 2.4.5.2 SDD with FDD configuration ...A-41 2.4.6 Backup creation ...A-41 2.5 DRF ...A-43

2.5.1 Files layout ...A-43 2.5.2 DRF processes ...A-47 2.5.3 DRF installation ...A-48 2.5.3.1 User configuration ...A-48 2.5.3.2 Folders configuration ...A-49 2.5.3.3 Application configuration ...A-49 2.5.3.4 Deleting recording files in the DRF ...A-49 2.5.4 Backup creation ...A-50 2.6 FDD ...A-51 2.6.1 Files layout ...A-51 2.6.2 FDD processes ...A-53 2.6.3 FDD installation ...A-53 2.6.3.1 User configuration ...A-53 2.6.3.2 Folders configuration ...A-54 2.6.4 Application configuration ...A-54 2.6.5 Backup creation ...A-55 2.7 DBM ...A-57

2.7.1 Files layout ...A-57 2.7.2 DBM processes ...A-59 2.7.3 DBM Software Backup ...A-60 2.7.4 DBM installation ...A-60 2.7.4.1 Postgres user configuration ...A-60 2.7.4.2 Postgres INITIAL configuration ...A-61 2.7.4.3 DBM Software installation ...A-61 2.8 RDCU ...A-62 2.8.1 Files layout ...A-62 2.8.2 RDCU processes ...A-65 2.8.3 RDCU installation ...A-66 2.8.3.1 User configuration ...A-66 2.8.3.2 Folders configuration ...A-67 2.8.3.3 Application configuration ...A-67 2.8.4 Backup creation ...A-79 2.8.5 Adding new radars ...A-79 2.8.5.1 RS-232 ...A-79 2.8.5.2 LAN ...A-79 2.8.5.3 LAN RADAR LANZA ...A-81 2.9 RDCU Transmision (N/A) ...A-82 2.9.1 Files layout ...A-82

(11)

S

U

Page A-11

2.9.2 RDFD processes ...A-83 2.9.3 RDFD installation ...A-83

2.9.3.1 User configuration ...A-83 2.9.3.2 Folders configuration ...A-84 2.9.3.3 Application configuration ...A-85 2.9.4 Backup creation ...A-85 2.10 SFN ...A-85

2.10.1 Files layout ...A-86 2.10.2 SFN processes ...A-88 2.10.3 SFN installation ...A-89 2.10.3.1 User configuration ...A-89 2.10.3.2 Folders configuration ...A-90 2.10.3.3 Application configuration ...A-90 2.10.4 Backup creation ...A-91 2.11 GTI ...A-92 2.11.1 Files layout ...A-92 2.11.2 GTI processes ...A-94 2.11.3 GTI installation...A-94 2.11.3.1 User configuration ...A-94 2.11.3.2 Folders configuration ...A-95 2.11.4 Backup creation ...A-96 2.12 Communications configuration ...A-97 3 Starting and finishing processes concerning the system components ... A-101 3.1 Starting process ... A-101 3.1.1 Switching on the computers... A-101 3.1.2 Starting up the application ... A-101 3.2 Finishing process... A-101

3.2.1 Shutting down the application ... A-101 3.2.2 Shutting down a SDD combined with FDD ... A-101 3.2.3 Shutting down a FDD ... A-102 3.2.4 Shutting down a SDP ... A-102 3.2.5 Shutting down a FDP ... A-102 3.2.6 Shutting down a CMD ... A-102 3.2.7 Shutting down a DRF ... A-102 3.2.8 Shutting down a RDCU ... A-102 3.2.9 Shutting down a RDCU Transmission ... A-102 3.2.10 Shutting down an SFN ... A-102 3.2.11 Complete computer switch off... A-102 4 System installation and maintenance ... A-103

(12)

S

U

Page A-12

4.1 Base Software ... A-103 4.1.1 Red Hat Enterprise Linux operating system... A-103 4.1.1.1 Initial Installation... A-103 4.1.1.1.1 Language Selection ... A-107 4.1.1.1.2 Select Keyboard ... A-108 4.1.1.1.3 Disk Partitioning Setup ... A-109 4.1.1.1.4 Boot Loader Configuration ... A-113 4.1.1.1.5 Network Configuration... A-114 4.1.1.1.6 Time Zone Configuration ... A-115 4.1.1.1.7 Set Root Password ... A-117 4.1.1.1.8 Package Group Selection ... A-118 4.1.1.1.9 Preparing to Install ... A-126 4.1.1.1.10 Installing Packages ... A-126 4.1.1.1.11 Installation Complete ... A-126 4.1.1.2 Application configuration ... A-127 4.1.1.3 Modification of common files ... A-131 4.1.1.3.1 IP address addition ... A-131 4.1.1.3.2 Time synchronization ... A-133 4.1.1.3.3 Users configuration ... A-133 4.1.1.3.4 Bootable applications ... A-133 4.1.1.4 Files and Services Modification ... A-133 4.2 Auxiliary devices ... A-135

4.2.1 Printer configuration and installation ... A-135 4.2.1.1 HP Color LaserJet Printer Installation - Administration ... A-135 4.2.1.2 Install HP Color LaserJet in a computer ... A-135 4.2.2 Digi Neo Card ... A-136 4.2.3 FarSync Card ... A-136 4.2.4 Nvidia Graphic Card ... A-138 4.2.5 Quad Port Network Card ... A-138 4.2.6 PCI334A RS-232 Card ... A-139 4.2.7 Meinberg Configuration. ... A-139 4.2.7.1 Menu: NTP Configuration ... A-139 4.2.7.2 Menu: Stratum of local clock ... A-140 4.2.7.3 Menu: Reset Time ... A-140 4.2.8 IER configuration ... A-140 4.2.9 Configuration to different monitor in all system ... A-143 4.2.9.1 Resolution for to different positions ... A-143 4.3 Software Security ... A-154 4.4 Diagnostics and errors ... A-155 4.4.1 Processes in the components ... A-155 4.4.2 Error messages ... A-155 4.4.2.1 SDD ... A-155 4.4.2.2 FDD ... A-157 4.4.2.3 DRF ... A-159 5 Kickstart Administration Guide ... A-161

(13)

S

U

Page A-13

5.1 Introduction ... A-161 5.2 Procedure to configure a working position as Kickstart server ... A-161 5.2.1 NFS Service ... A-162 5.2.2 DHCP Service ... A-162 5.2.3 TFTP Service ... A-162 5.2.4 Procedure to configure Kickstart to install & create BACkUP of the machines ... A-163 5.2.4.1 Edit INDIA configuration file: ... A-163 5.2.4.2 How to install machines with Kickstart ... A-163 5.3 How to Kickstart Start-up in a Client Machine: ... A-165 5.4 How to Create Backup from Kickstart ... A-165 5.5 Folders and important Kickstart files ... A-167

5.5.1 Folder /image/kickstart/INDIA/BACKUPS/<DD_MM_YY>/[OPERATIONAL] or [SIMULATION]/position ... A-167 5.5.2 Folder /image/kickstart/COMMON ... A-173 5.5.3 File /root/postinstall.log... A-174 5.6 Procedure to inhibit a machine as Kickstart server ... A-174

5.6.1 File /etc/exports ... A-174 5.6.2 DHCP service ... A-175 5.6.3 XINETD service ... A-175 6 Communications Folder ... A-177

6.1 COMMUNICATIONS/india/ Folder ... A-177 Appendix A - ABBREVIATIONS AND GLOSSARY OF TERMS ... A-179

A.1 List of Abbreviations ... A-179 A.2 Glossary of Terms ... A-180

(14)

S

U

Page A-14

(15)

S

U

Page A-15

List of Figures

Figure 1-1: Directories for the Operational proposal I (Servers & Comunications) ... A-4 Figure 1-2: Directories for the Operational proposal II (Workstations & Supervision) ... A-5 Figure 2-1: FDP files layout. ... A-7 Figure 2-2: SDP Files Layout... A-16 Figure 2-3: CMD Files Layout. ... A-22 Figure 2-4: SDD Files Layout. ... A-31 Figure 2-5: DRF Files Layout... A-43 Figure 2-6: FDD Files Layout... A-51 Figure 2-7: DBM Files Layout. ... A-57 Figure 2-8: RDCU Files Layout. ... A-62 Figure 2-9: Radar LAN Connection ... A-80 Figure 2-10: RDFD Files Layout. ... A-82 Figure 2-11: SFN Files Layout. ... A-86 Figure 2-12: GTI Files Layout. ... A-92 Figure 4-1: Installation Red Hat Enterprise Linux ... A-104 Figure 4-2: Testing CD media... A-105 Figure 4-3: Welcome to Red Hat Enterprise Linux ... A-106 Figure 4-4: Language Selection. ... A-107 Figure 4-5: Keyboard Configuration ... A-108 Figure 4-6: Disk Partitioning Setup. ... A-109 Figure 4-7: Disk Setup ... A-110 Figure 4-8: Add Swap Partition ... A-111 Figure 4-9: Add Root Partition ... A-111 Figure 4-10: Disk Setup ... A-112 Figure 4-11: Boot Loader Configuration ... A-113 Figure 4-12: Network Configuration I ... A-114 Figure 4-13: Network Configuration II... A-115 Figure 4-145: Set Root Password ... A-117 Figure 4-156: Package Installation Defaults ... A-118 Figure 4-167: Desktop Environments ... A-119 Figure 4-178: Applications ... A-120 Figure 4-18: Servers ... A-122 Figure 4-19: Legacy Network Package Details ... A-123 Figure 4-20: Base System ... A-124

(16)

S

U

Page A-16

Figure 4-21: Mail Server Package Details ... A-125 Figure 5-1: KickStart Directories ... A-161

(17)

S

U

Page A-17

List of Tables

Table 2-1: /local/india/fdp/exec folder. ... A-9 Table 2-2: FDP User configuration parameters ... A-14 Table 2-3: SDP Folder /local/india/rdp/exec relevant files ... A-18 Table 2-4: /local/india/rdp/exec Subfolder contents ... A-18 Table 2-5: FDP User configuration parameters ... A-20 Table 2-6: CMD relevant folders. ... A-23 Table 2-7: SDD “/local/india/sdd/exec/print” folder relevant files. ... A-36 Table 2-8: DRF Tape types ... A-49 Table 2-9: DBM User configuration parameters ... A-60 Table 2-10: RDCU User configuration parameters... A-66 Table 2-11: RDFD “/local/india/rdfd/exec/dir_exec” folder relevant files. ... A-83 Table 2-12: RDFD User configuration parameters ... A-84 Table 2-13: GTI “/local/india/gti/exec” folder relevant files. ... A-93 Table 2-14: GTI “/local/india/gti/exec/bin” folder relevant process. ... A-94 Table 2-15: GTI User configuration parameters ... A-95 Table 4-1: SDD Error Messages ... A-157 Table 4-2: FDD Error Messages ... A-159 Table 4-3: DRF Error Messages ... A-160

(18)

S

U

Page A-2

(19)

S

U

Page A-3

1 Scope

This Administration Manual guides the user through the Indra’s Air Traffic Management Syste regarding its Administration and Maintenance.

All formation provided in this document is valid for Project: AirCon 2100.

1.1 General purpose

The main aim is to keep working the system correctly and permanently.

To accomplish this objective, the operator must acquire a precise technical and practical acknowledge concerning the different procedures used to satisfy the needs of the system regarding its operation and updating.

This chapter includes the guide to use the directories to configure and maintain the communications between all the computers.

1.2 General system overview

AirCon 2100 Air Traffic Control System is based in a general-purpose system developed by Indra. It is possible to add a simulation environment to emulate the operational system external environment, used for controller instruction and practising. It can be configured creating all purpose exercises and representation of real environments that are useful to check new operational procedures.

ATM system configuration is based in gained experience in other systems development, like open systems used to visualization and treatment of radar data and flight plan process installed in another projects and countries. Indra has been developing systems for Spain (SACTA system), Canada, Germany (VAFORIT system), Norway, Holland (Maastricht UAC-Eurocontrol system) and nowadays is developing systems for different countries from all over the world. One of the most useful characteristic of this system is its availability, very close to 100% (99.9999%) because of the use of redundant servers in a distributed setting and tested and reliable commercial computers. Configuration of software system is determined for its modularity and distribution, and it is sorted by using discrete distributed processes for each component. At the same time, system uses message communications in order to allow the interconnection between tasks and guarantee the synchronism of the system. Communications and tasks are isolated to improve a high-level maintenance.

Software running in this system have been tested in different places and for a long time, so Indra can be sure that it is not needed any other additional progress of any class for the correct and stable operability of the system.

(20)

S

U

Page A-4

(21)

S

U

Page A-5

(22)

S

U

Page A-6

(23)

S

U

Page A-7

2 Software Components Detailed Description

This section includes the description of the files needed for each system component as well as the installation, configuration, backup and recovery procedures for every component.

2.1 FDP

This component manages the Flight Plans. It receive Flight Plans and Flight Plan updates from external systems by means AFTN lines, from controllers through SDD and FDD positions or repetitive flight plans.

The received Flight Plans and later updates are processed and used for hand-over procedures; 4D route calculations, and route based alerts calculations, as is the case of MTCD or RAW functions. Flight plan information is provided to the controller through SDD positions, FDD positions, and strip printing (if applicable).

2.1.1 Files layout

The following diagram shows the location of the folders needed by the system, local/india/fdp/exec folder:

Figure 2-1: FDP files layout.

Folder local/india/fdp/exec, the most significant files are:

/local/India/fdp/exec /local/India/fdp/exec/adap /local/India/fdp/exec/aftn_database

aaa

/local/India/fdp/exec/aftns

aaa

/local/India/fdp/exec/dir_exec

aaa

/local/India/fdp/exec/dir_tools

aaa

/local/India/fdp/exec/files

aaa

/local/India/fdp/exec/record

ggg

/local/India/fdp/exec/historical

aaa

/local/India fdp/exec/dir_posix_fds /local/India/fdp/exec/fdp_messages /local/India/fdp/exec/shm /local/India/fdp/exec/printer /local/India/fdp/exec/log /local/India/fdp/exec/queues /local/India/fdp/exec/sem

(24)

S

U

Page A-8

FILE DESCRIPTION

.openwin-init It keeps the X configuration when the application starts up.

.OUT307 _{This file contains traces.}

.profile It contains the start up characteristics concerning the position.

.xinitrc It creates the adequate environment to start up the position.

adap Folder containing the FDP Adaptation Data

files.

aftn_database Where daily transmission and reception files concerning the AFTN messages are located

aftns Where weekly transmission and reception files for AFTN messages are located

dir_exec _{It contains FDP executable files.}

dir_tools _{This folder contains the FDP tools.}

dir_posix_fds This folder contains file descriptor files of the POSIX queues.

CONFIG_COM It defines network communications for all processes involved in component configurations fdp_messages This folder contains the FDP test messages. It

is useful in Acceptance tests.

files Thos folder contains data files processed by _{the FDP. These files are useful for shared} memory and warm start up.

historical This folder contains daily file containing historic information for each FP.

killapplication That script kills the FDP application. It must _{be used by writing:} # ./killapplication (LINUX or SUN) -rmipcs

log _{Folder of system errors}

remote_startup This script starts up the application from the CMD.

LINE_1 _{Required file for starting up the X25 server.}

m_350_india _linux_fdp_task

Father process. It initiates the rest of the processes and determinates which ones are operative and in reserve. It receives messages from the CMD. It is a link to a file with the

same name that is located in

/local/india/fdp/exec/dir_exec

macros This folder contains utilities and scripts pertaining to the system.

(25)

S

U

Page A-9

printer This folder keeps information that can be printed (RPL lists, PFTs, etc.).

m_varsovia_linux_fdp_to ols

Tools of FDP. This file is link to a file with

the same name that are located in

/local/india/fdp/exec/dir_tools

queues Folder keeping UNIX queues for communications between processes.

record This folder keeps daily files containing _{information related to concluded or not} concluded FPLs.

sem This folder contains UNIX semaphores devoted

to communications between processes.

shm This folder contains shared memory facilities

for the FDP.

startup_fdp.sh _{Script that starts up the FDP.}

Table 2-1: /local/india/fdp/exec folder.

Folder /local/india/fdp/exec/adap.

This folder contains all component adaptation files which extension ends with “.adap”. The ones with extension “.sim.adap” are useful when simulation is running, and the “.fdp.adap” are useful for operational mode.

This folder contains the files that DBM sends to FDP when the data are loaded into the system, and are used to adaptation data of the system:

ads_vdl_m4.sim.adap agdl_control_centers.sim.adap agdl_dir_sita.sim.adap agdl_restricted.sim.adap aircraft_groups.fdp.adap aircraft_performances.sim.adap aircraft_subtypes.sim.adap aircraft_types.fdp.adap airport_lighting.sim.adap airport_navigation_aids.sim.adap airports.fdp.adap airports_runways.sim.adap airspace_mosaic.fdp.adap airways.fdp.adap approach_routes.fdp.adap arrival_procedures.sim.adap config_info.adap control_centers.fdp.adap control_functions.sim.adap control_sectors.fdp.adap coordixpoints.fdp.adap departure_procedures.sim.adap destination_aerodromes.fdp.adap direction_finders.sim.adap external_regions.fdp.adap

(26)

S

U

Page A-10 fixpoints.fdp.adap geographic_regions.fdp.adap geographic_zones.fdp.adap ground_airport.sim.adap ground_endpoints.sim.adap ground_paths.sim.adap ground_routes.sim.adap ground_runways.sim.adap ground_segments.sim.adap ground_standgates.sim.adap ground_waitpoints.sim.adap holding_patterns.sim.adap information_address.fdp.adap instrument_landing_procedures.sim.adap intermediate_approach_speed_area.sim.adap local_addresses.fdp.adap points_pairs.fdp.adap pressure_zones.fdp.adap radars.sim.adap restricted_airspaces.fdp.adap route_elements.fdp.adap ssr_codes.fdp.adap standard_routes.fdp.adap traffic_patterns.sim.adap user_passwords.fdp.adap vehicle_performances.sim.adap wind_zones.fdp.adap working_area.fdp.adap Folder /local/india/fdp/exec/aftn_database

This folder contains the sent and received AFTN messages files using ASCII format.

Folder /local/india/fdp/exec/aftns

This folder contains the sent and received AFTN messages files using ASCII format. These files are kept during 1 month, after this period of time they are automatically deleted.

Folder /local/india/fdp/exec/dir_exec

This folder contains the executable file pertaining to the FDP. The application looks for executable files at /local/india/fdp/exec, where the link to the /local/india/fdp/exec/dir_exec folder are located.

m_350_fdp_task

Folder /local/india/fdp/exec/dir_posix_fds

(27)

S

U

Page A-11

Folder /local/india/fdp/exec/dir_tools

This folder contains the tool pertaining to the FDP. The application looks for tool at /local/india/fdp/exec, where the link to the /local/india/fdp/exec/dir_tools folder are located.

m_varsovia_linux_fdp_tools

Folder /local/india/fdp/exec/files

This folder contains data files processed by the FDP (Flight plans, Meteorological data, etc). These files are characterized by their ending “df” extension and are particularly useful when a warm start up. aai_queue.df AFTN_LINE AFTN_LINE2 aftn_queue.df aftn_sec_number_1.df aftn_sec_number_2.df aftn_tx_queue.df aierport_param.df atis_info.df defer_queue.df fp_queue.df fp_queue_table.df holding_queue.df holding_queue_table.df meteo_data.df meteo_info.df navaids.df notams.df notams_manager.df PAF_PISTA_LINE.df pft_file.df qnh_altimeters.df restricc_fir.df restricc_fix.df restricted_areas.df restricted_areas_manager.df rpl_global_file.df rpl_hfir_ultimo_rpl.df sigmets.df sigmets_manager.df traces.df tx_messages_file.df validated_fcm_queue.df vsps_table.df wind_value.df

Links to serial ports are also included.

Folder /local/india/fdp/exec/historical

This folder contains daily files concerning FPLs historic information. The system removes automatically all files older than 60 days (the oldest file is deleted while a new one is created).

(28)

S

U

Page A-12

Folder /local/india/fdp/exec/macros

In this folder are stored useful macros for the FDP.

Folder /local/india/fdp/exec/printer

This folder contains temporal files (RPLs lists, PFTs, etc) to be printed by the user. After a printing petition, the files are removed immediately.

Folder /local/india/fdp/exec/record

This folder contains information relative to flight plans that have passed from ACTIVE to TERMINATED. This information is particularly important when billing. Each FPL has its own data line.

The syntax corresponding to these files are:

.RECORD. <data_creation> (where data_creation is the date of the flight plans kept).

RECORD for 24-01-05

067,SVA005 , ,X,OEJN, ,B744,450 ,GMME, ,1217,350 ,24-01-05 11:33:31, ,4414,0044,259 ,H,WS ORSUP ,350 ,1133,3345N00416W,310 ,1150,RBT , 5,1217

068,TAR003 , ,X,OEJN, ,B744,450 ,GMMN, ,1239,350 ,24-01-05 11:50:19, ,4412,0048,303 ,H,S ORSUP ,350

,1150,OJD ,350 ,1150,FES ,350 ,1212,DONAS ,233 ,1225,GODAM , 107,1232 069,CNCDF , ,X,GMAD, ,C182,140 ,GMMC, ,1243,105 ,24-01-05 11:00:00, ,4405,0143,142 ,L,S VESEN ,115 ,1139,3206N00829W, 115,1149 070,QTR002 , ,X,OEJN, ,B744,450 ,GMMX, ,1247,350 ,24-01-05 11:50:29, ,4411,0057,372 ,H,WS ORSUP ,350 ,1150,OJD ,350 ,1150,3431N00253W,350 ,1157,MAK , 27,1247 071,TEST1 , ,X,DAAG, ,B734,420 ,GMMN, ,1258,300 ,24-01-05 12:02:32, ,4415,0056,297 ,M,WS ORSUP ,300

,1202,OJD ,300 ,1203,SOVAL ,300 ,1228,FES ,300 ,1234,GODAM , 136,1252

072,SVA001 , , ,AFIL, , ,0 ,GMMN, ,0000,0 ,24-01-05 11:43:56, ,4413, , , ,

073,OEDDV , ,X,GMME, ,C182,140 ,GMAD, ,1337,110 ,24-01-05 11:01:00, ,4400,0236,273 ,L,S ESALA ,65

,1113,CBA ,109 ,1131,CSD ,110 ,1153,VESEN ,110 ,1232,ADM , 110,1323

074,RAM426 , ,X,GMAD, ,B738,425 ,GMMN, ,1135,240 ,24-01-05 11:00:00, ,4403,0035,232 ,M,S MOGBA ,162 ,1100,ESS ,167 ,1100,RALEK ,162 ,1122,BRC , 162,1128

2.1.2 FDP processes

This procedure verifies the adequate execution of processes on all the computers of the system. To do this, user can execute the command ps –ef | grep m_ from the console.

<HOSTNAME>1#ps -ef | grep -i m_

UID PID PPID C STIME TTY TIME CMD

root 23945 1 0 11:30 ? 00:00:00 m_350_fdp_task 0 FDPS1 root 24351 23945 0 11:31 ? 00:00:00 ./m_307_supervisor 0 FDPS1

(29)

S

U

Page A-13 root 8040 24351 0 11:52 ? 00:00:00 m_399_presence 0 root 8041 24351 0 11:52 ? 00:00:00 m_301_init_explorer 0 root 8042 24351 0 11:52 ? 00:00:00 m_301_multiple_retrieve_explorer 0 root 8043 24351 0 11:52 ? 00:00:00 m_301_refresh 0 root 8044 24351 0 11:52 ? 00:00:00 m_301_recalc_sid_star 0 root 8045 24351 0 11:52 ? 00:00:00 m_302_processor 0 root 8046 24351 0 11:52 ? 00:00:00 m_303_events 0 root 8047 24351 0 11:52 ? 00:00:00 m_305_rpl_management 0 root 8048 24351 0 11:52 ? 00:00:00 m_305_rpl_load 0 root 8049 24351 0 11:52 ? 00:00:00 m_305_rpl_explorer 0 root 8050 24351 0 11:52 ? 00:00:00 m_305_rpl_refresh 0 root 8051 24351 0 11:52 ? 00:00:00 m_306_conflict_probe 0 root 8052 24351 0 11:52 ? 00:00:00 m_308_flow_control 0 root 8053 24351 0 11:52 ? 00:00:00 m_308_flow_events 0 root 8054 24351 0 11:52 ? 00:00:00 m_309_line_rw 1 0 root 8055 24351 0 11:52 ? 00:00:00 m_309_line_rw 2 0 root 8056 24351 0 11:52 ? 00:00:00 m_309_processor 0 root 8057 24351 0 11:52 ? 00:00:00 m_310_processor 0 root 8058 24351 0 11:52 ? 00:00:00 m_311_notams 0 root 8059 24351 0 11:52 ? 00:00:00 m_312_line_writer 0 root 8060 24351 0 11:52 ? 00:00:00 m_312_line_reader 0 root 8061 24351 0 11:52 ? 00:00:00 m_312_processor 0 root 8062 24351 0 11:52 ? 00:00:00 m_315_sevents 0 root 8063 24351 0 11:52 ? 00:00:00 m_316_airspace_probe 0 root 8064 24351 0 11:52 ? 00:00:00 m_316_explorer 0 root 8065 24351 0 11:52 ? 00:00:00 m_321_fmtp 0 root 8066 24351 0 11:52 ? 00:00:00 m_310_partner_communication 0 5 X25 root 8067 24351 0 11:52 ? 00:00:00 m_310_partner_communication 0 2 X25 root 8068 24351 0 11:52 ? 00:00:00 m_310_partner_communication 0 1 X25 2.1.3 Backup recovery <HOSTNAME>1# cd /local

<HOSTNAME>1# tar -xvf <name_backup>

Where name_backup is the name of the selected backup to be installed.

2.1.4 FDP installation 2.1.4.1 User configuration

Depending on the system it is necessary create users that are going to access to the application. This procedure configures the user allowed to access to each system, and it could be different for each component.

(30)

S

U

Page A-14

User configuration is located in /etc/passwd file, so it is necessary edit this file and adds the corresponding line or lines.

The user line syntax is the following:

user_name:x:uid:gid:comment folder_access:login_shell

This is a description of each parameter:

user_name It is a user name in the system.

x It indicates that the user has a password (the _{user has an entry in the} /etc/shadow file).

uid It is the user identifier number.

gid It is group identifier number (See _file). /etc/group

comment This string is used to include additional information.

folder_access This _application.parameter includes the path of the

login_shell INDRA application always uses /usr/bin/ksh shell.

Table 2-2: FDP User configuration parameters

Line that user must add to the /etc/passwd file to configure the user for FDP component.

user:x:0:1:User india:/local/india/fdp/exec:/usr/bin/ksh

After adding a user, it is necessary to confirm this step using “pwconv” command, and then enter the password for that user with the command “passwd xxx” where xxx is the user name.

This is the summary of the necessary steps to add a user:

#vi /etc/passwd

Add the corresponding line. #pwconv

#passwd <user>

New Password: <password>

Re-enter new Password: <password>

passwd: password successfully changed for <user>

Where “user” is the user name for who we want change the password and “password” is the new password for the user.

2.1.4.2 Folders configuration

Creation of the /local folder with all the permissions:

(31)

S

U

Page A-15

Alternatively, create a copy of the application from the other FDP: #rsh hostname

# cd /local

# tar -cvf FDPx.indiax.tar india

Where “x” is the FDP number and the computer hostname where the application has been created.

# gzip -9 -v FDPx.indiax.tar

It will compress the file a india FDPx.indiax.tar.gz # rcp FDPx.indiax.tar.gz <host_name>:/local

Where host_name is the hostname corresponding to the computer where the application must be installed).

Decompression and extraction of the application in the computer: # cd /local

# gunzip FDPx.indiax.tar.gz

It will decompress and leave the file FDPx.indiax.tar.

# tar -xvf FDPx.indiax.tar The application will be installed.

Modification and distribution of CONFIG_COM if it is necessary.

2.1.5 Application configuration

The FDP execution folder is /local/india/fdp/exec.

The FDP number (1 or 2) must be indicated in a specific line at the start-up script of each FDP system.

Line affected of the file /local/india/fdp/exec/startup_fdp.sh.

m_350_fdp_task 0 FDPS1 1>> $REPORTS_FILE 2>&1 &

Changing the variable FDPS1 or FDPS2 this script indicates to the system if it is working as FDP1 or as FDP2.

2.1.6 Backup creation

Creation of the Backup file: # cd /local

# tar -cvf FDPx.indiax.tar india

Where “x” is the CMD number and the computer hostname where the application has been created.

# gzip -9 -v FDPx.indiax.tar (It will compress the file to FDPx.indiax.tar.gz) # rcp FDPx.indiax.tar.gz <host_name>:/../FOLDER_BACKUP

(32)

S

U

Page A-16

Where host_name is the computer where the application is going to be installed or saved #exit

2.2 SDP

This component provides tracking functions. It receives the radar information collected by the RDCUs and processes it, rejecting erroneous data, and correcting the systematic radar errors. ADS tracking is performed too, if the ADS is available.

Once the radar data is cleaned, they are correlated with the system Flight plans and used to provide the controller an accurate air traffic situation and alerts for air traffic surveillance.

The SDP alert function includes minimum separation between aircrafts (Short Term Conflict Alert), Minimum Safe Altitude warning, Restricted Area warning, Cleared Level Adherence Monitoring, Route Adherence Monitoring and Heading Alert and Distress Alerts.

The following diagram shows the location of the folders needed by the system; folder /local/india/rdp/exec:

Figure 2-2: SDP Files Layout.

The most relevant files in this folder are:

.openwin-init _{UNIX file with X-Windows parameters.}

/local/ india /rdp/exec/dir_tools /local/ india /rdp/exec/dir_files /local/ india /rdp/exec/dir_posix_fds /local/ india /rdp/exec/dir_shm /local/ india /rdp/exec/tablas_ads /local/ india /rdp/exec/grabacion /local/india/rdp/exec/dir_exec /local/ india /rdp/exec

(33)

S

U

Page A-17

.profile UNIX file containing specifications for starting up the position.

.xinitrc UNIX file containing specifications for starting up the position.

CONFIG_COM This file defines the network communication _{method applied to the processes in charge of} component configuration.

fich_config Link with fich_config.sdp1 or fich_config.sdp2 files. Contains the SDP number.

killapplication_sdp _{This process frees the shared memory.}

LC_TIME Text file containing useful dates for the recording and playback.

m_sdp_adr Process of the SDP for Radar Dynamic Adjustment. _{It is a link to a file with the same name that} is located in /local/india/rdp/exec/dir_exec.

m_sdp_conflict Process of the SDP for safety nets (integrated _{mode) It is a link to a file with the same name} that is located in /local/india/rdp/exec/dir_exec.

m_sdp_conflict_mono Process of the SDP for safety nets (Monoradar _{mode) It is a link to a file with the same name} that is located in /local/india/rdp/exec/dir_exec.

m_sdp_meteo Process of the SDP for meteorological data. It _{is a link to a file with the same name that is} located in /local/india/rdp/exec/dir_exec.

m_sdp_mosaic

Process of the SDP for management of restricted areas. It is in charge of receiving and process data from the FDP. It is a link to a file with

the same name that is located in

/local/india/rdp/exec/dir_exec.

m_sdp_player Process of the SDP for reproduction of radar _{data. It is a link to a file with the same name} that is located in /local/india/rdp/exec/dir_tools.

m_sdp_presence

Process of the SDP for sending presence to CMD and SDDs. It is a link to a file with the same

name that is located in

/local/india/rdp/exec/dir_exec.

m_sdp_recorder Process of the SDP for recording. It is a link _{to a file with the same name that is located in} /local/india/rdp/exec/dir_tools.

m_sdp_supervisor

Process of the SDP for starting up the processes and receiving messages from CMD. It is a link to a file with the same name that is located in /local/india/rdp/exec/dir_exec.

(34)

S

U

Page A-18

m_sdp_traces Traces tool of the SDP. It is a link to a file _{with the same name that is located in} /local/india/rdp/exec/dir_tools.

m_sdp_tracker

Process of the SDP for processing and correlating tracks, including synthetic tracks. It is a link to a file with the same name that is located in /local/india/rdp/exec/dir_exec.

startup.sdp _{Link with}_{startup.sdp.ope}_or_{startup.sdp.sim}_files. killapplication_sdp _{Script for cancelling the SDP (off-line).}

tabla_* These are files generated from the (FICH_*) adaptation data.

Table 2-3: SDP Folder /local/india/rdp/exec relevant files

Subfolders contents:

FOLDER DESCRIPTION

/local/india/rdp/exec/dir_exec

This folder contains files that are linked to the processes contained in the /local/india/rdp/exec folder (m_sdp_* files).

/local/india/rdp/exec/dir_tools

This folder contains

executable files of the SDP system (player, recorder, and traces).

/local/india/rdp/exec/dir_files

This folder contains the file traces.df, which is in charge of keeping the last values of the traces. This file allows the system to

know which traces are

activated.

/local/india/rdp/exec/dir_posix_fds

This folder contains file descriptor files of the POSIX queues.

/local/india/rdp/exec/dir_shm

descriptors of the shared memory tables of the SDP.

/local/india/rdp/exec/grabacion

recording files that player uses while reproduction is running.

/local/india/rdp/exec/tablas_ads

parameters related to the ADS contracts.

(35)

S

U

Page A-19

2.2.2 SDP processes

This procedure verifies the adequate execution of processes on all the computers of the system. To do this, user can execute the command #ps –ef | grep m_ from the console.

In status OPERATIONAL

<HOSTNAME>@<HOSTNAME>3$ ps -ef | grep m_

root 5291 1 0 19:03:18 ? 0:11 ./m_sdp_supervisor root 5408 5291 0 19:03:32 ? 3:01 m_sdp_conflict_mono root 5395 5291 0 19:03:31 ? 20:44 m_sdp_tracker root 5396 5291 0 19:03:31 ? 0:57 m_sdp_adr root 5397 5291 0 19:03:32 ? 0:05 m_sdp_meteo root 5412 5291 0 19:03:32 ? 0:00 m_sdp_mosaic root 5398 5291 0 19:03:32 ? 3:09 m_sdp_conflict root 5413 5291 0 19:03:32 ? 0:08 m_sdp_presence In status SIMULATION

[root@<HOSTNAME>3 ~]# ps -ef | grep -i m_sdp

root 19692 1 0 Mar28 ? 00:00:00 ./m_sdp_supervisor S root 19697 19692 0 Mar28 ? 00:00:17 m_sdp_tracker S root 19698 19692 0 Mar28 ? 00:01:38 m_sdp_adr S root 19719 19692 0 Mar28 ? 00:00:01 m_sdp_meteo S root 19722 19692 0 Mar28 ? 00:00:00 m_sdp_conflict S root 19723 19692 0 Mar28 ? 00:00:00 m_sdp_conflict_mono S root 19734 19692 0 Mar28 ? 00:00:00 m_sdp_mosaic S

root 19742 19692 0 Mar28 ? 00:00:00 m_sdp_presence S

2.2.3 SDP installation 2.2.3.1 User configuration

user_name:x:uid:gid:comment folder_access:login_shell This is a description of each parameter:

x It indicates that the user has a password (the user has an entry in the /etc/shadow file).

gid It is group identifier number (See /etc/group file).

(36)

S

U

Page A-20 comment This string is used to include additional

information.

folder_access This parameter includes the path of the application.

Table 2-5: FDP User configuration parameters

Line that user must add to the /etc/passwd file to configure the user for SDP component.

user:x:0:1:User india:/local/india/rdp/exec:/usr/bin/ksh

After adding a user, it is necessary to confirm this step using “pwconv” command, and then enter the password for that user with the command “passwd xxx” where xxx is the user name.

This is the summary of the necessary steps to add a user:

#vi /etc/passwd

Add the corresponding line.

#pwconv

#passwd <user>

New Password: <password>

Re-enter new Password: <password>

Creation of the /local folder with all the permissions:

# mkdir –m 777 /local

Alternatively, create a copy of the application from the other SDP:

# rsh hotname # cd /local

# tar -cvf SDPx.indiax.tar india

Where “x” is the SDP number and the computer hostname where the application has been created.

# gzip -9 -v SDPx.indiax.tar

# rcp SDPx.indiax.tar.gz <host_name>:/local

Where host_name is the hostname corresponding to the computer on which the application must be installed.

#exit

(37)

S

U

Page A-21 # cd /local

# gunzip SDPx.indiax.tar.gz # tar -xvf SDPx.indiax.tar The application will be installed.

Modification and distribution of CONFIG_COM if it is necessary.

The SDP execution folder is /local/india/rdp/exec.

The SDP number (1 o 2) must be indicated in the boot file: Changing the variable:

File /local/india/rdp/exec/fich_config

ROLE_SUBSYSTEM: SDP1

In the /local/india/rdp/exec/, there is a link named startup.sdp; which, depending of start-up SDP mode, it must point the one that starts in OPERATIONAL or SIMULATION mode.

For OPERATIONAL mode:

<HOSTNAME>3$ ln -fs startup.sdp.ope startup.sdp <HOSTNAME>3$ ls -al st*

lrwxrwxrwx 1 root root 15 Mar 31 10:03 startup.sdp -> startup.sdp.ope -rwxr-xr-x 1 root root 469 Feb 11 18:03 startup.sdp.ope

-rwxr-xr-x 1 root root 466 Feb 11 18:01 startup.sdp.sim For SIMULATION mode:

<HOSTNAME>32$ ln -fs startup.sdp.sim startup.sdp <HOSTNAME>32$ ls -al st*

lrwxrwxrwx 1 root root 15 Mar 31 10:11 startup.sdp -> startup.sdp.sim -rwxr-xr-x 1 root root 469 Feb 11 18:03 startup.sdp.ope

-rwxr-xr-x 1 root root 466 Feb 11 18:01 startup.sdp.sim

Note: In simulation mode, only a SDP position is required.

Modification and distribution of CONFIG_COM.

Creation of the Backup file:

# cd /local

# tar -cvf SDPx.indiax.tar india

Where “x” is the SDP number and the computer hostname where the application has been created.

# gzip -9 -v SDPx.indiax.tar (It will compress the file to SDPx.indiax.tar.gz) # rcp SDPx.indiax.tar.gz <host_name>:/../FOLDER_BACKUP

Where host_name is the computer where the application is going to be installed or saved

(38)

S

U

Page A-22

2.3 CMD

It continuously monitors the whole system and shows its status in real time. When a components fails or is not working correctly, an operator can take the appropriate actions on the CMD console. Some system parameters can be changed trough the CMD to adequate the system configuration to the actual working conditions, as they can be the VSP parameters or active sectorization.

The following diagram shows the location of the folders needed by the system:

Figure 2-3: CMD Files Layout.

The most relevant files are:

Folder /local/india/spv/exec:

.mwmrc

UNIX file for the definition of Windows parameters. It also defines the kind of keyboard and function keys.

.profile UNIX file containing start up characteristics for the position.

.xinitrc UNIX file containing start up characteristics for the position.

CONFIG_COM This file defines network communications between _{the processes that configure the components.} dir_adap This folder contains adaptation files.

/local/ india

/local/ india /spv/exec

/local/india/ctr_lan /local/india/ctr_prn

/local/ india /spv/exec/dir_adap /local/india/spv/exec/dir_aux_file s

/local/india/spv/exec/dir_config /local/ india /spv/exec/dir_exec /local/ india /spv/exec/dir_history /local/india/spv/exec/dir_macros /local/india/spv/exec/dir_resourc es /local/india/spv/exec/dir_sectors /local/india/spv/exec/dir_updated _tables /local/india/spv/exec/dir_users /local/india/spv/exec/fonts /local/india/spv/exec/printer

(39)

S

U

Page A-23

dir_aux_files This folder contains auxiliary files generated by _{the application.} dir_config This folder contains CMD configuration files. dir_exec This folder contains CMD executable files. dir_history This folder contains CMD historic files. dir_macros This folder contains scripts.

dir_resources This file contains resources files. dir_sectors This file contains sectorization files.

dir_updated_tables This file contains tables starting from adaptation files.

dir_users This file contains files concerning user information.

fonts This folder contains the type of fonts used by _{the CMD.}

startup.cmd

This is a link with one of these two files: startup.cmd1.ope, startup.cmd2.ope. The choice depends of the CMD to be started up.

remote_startup This is a link with remote_startup file belonging to the dir_macros folder.

PSSH Link to the PSSH file pertaining to the dir_resources folder.

pssh Link to the pssh file pertaining to the dir_exec folder.

sh-env This file contains the MOTIF environment. supervision_central Link to a CMD process.

Table 2-6: CMD relevant folders.

Folder /local/india/spv/exec/dir_adap:

FICH_* ASCII adaptation files.

user_passwords.fdp.adap

This encrypted adaptation file contains information concerning users, alias, roles, and passwords.

Folder /local/india/spv/exec/dir_aux_files: This Folder contains internal tools for the CMD.

(40)

S

U

Page A-24

f_used_paths.cfg

Configuration file containing all PATH related to configuration files and executable files used by the CMD.

Folder /local/india/spv/exec/dir_exec

pssh.00.00 CMD process. It is the graphical part of the _application.

supervision_central.00.00 CMD process. It is the non-graphical part of the application.

Folder /local/india/spv/exec/dir_history.

This folder contains the historic files corresponding to the CMD of the last 30 days.

They contain the set of warnings, configuration changes and the STCA and RAW alarms produced by the system.

The format of these files is: dd_mm_yy_h

Where "dd" represents the day, "mm" the month, "yy" the year and "h" the locations for historical.

Folder /local/india/spv/exec/dir_macros.

aux_comandos This file sends to the printer the content of the aux_alarmas file.

startup.cmd1.ope This script starts up the CMD1 for the OPERATIONAL string

startup.cmd2.ope This script starts up the CMD2 for the OPERATIONAL _string

remote_startup This script starts up the application from a remote position.

shutdown_system This script shut down all the applications of the system

start_system This script starts up all the applications of the system.

termproc This script cancels any process. The process must be indicated as a parameter.

(41)

S

U

Page A-25

Folder /local/india/spv/exec/dir_resources.

ding.au This file contains the CMD sound alarm.

plaser_*.pix Laser printer pictures for screen designing at the CMD.

*.pix Pixmap files devoted to graphical icons. printer*.pix Printer pictures.

PSSH Resources _{application on the screen.}file (MOTIF) to display the CMD

Folder /local/india/spv/exec/dir_sectors.

SECTORIZATION*_1…10 ASCII files containing predefined sectorizations.

Folder /local/india/spv/exec/dir_updated_tables.

tabla_* Data files generated from adaptation.

Folder /local/india/spv/exec/dir_users.

USER_*

These ASCII files contain all the users who used the system. The information about the users disappears when a new day starts, except for the last user.

Folder /local/india/spv/exec/printer.

ps_lp Postscript file concerning to laser printers. tabla_ps.sh Postscript file concerning to tables printing.

(42)

S

U

Page A-26

Folder /local/india/ctr_lan.

The most relevant files pertaining to the ctr_lan folder are:

CONFIG_COM This files defines the network communication way used _{by processes that configure the components} kill_ctr_lan This file kills the double LAN controller.

m_control_lan This is executable file checks the LAN status and _{sends messages to central supervision.}

The CONFIG_COM file is a link to CONFIG_COM file belonging to the /local/india/spv/exec folder.

Folder /local/india/ctr_prn.

CONFIG_COM

This file defines the network communication processes between processes that configure the components.

p_printer_status This file verifies the printer status. It is a CMD process.

p_send_status_printer

This file sends the printer status to the CMD for a graphical display. It is a process that is triggered by p_printer_status process when it is required.

STATUS_PRINTER_FILE Temporal file that receives the laser printer _status.

PRINTERS This file define the printers associated.

The CONFIG_COM file is a link to the CONFIG_COM file that is located at the /local/india/spv/exec folder.

2.3.2 CMD processes

This procedure verifies the adequate execution of processes on all the computers of the system. To do this, user can execute the command # ps –ef | more from the console.

<hostname>$ ps -ef | more

root 23233 23149 0 22:41:30 ? 0:22 ./m_control_lan tsp2 lan_controler2

root 2757 2724 0 16:43:31 console 0:01 ./pssh OPERATIVO 2

(43)

S

U

Page A-27 root 3064 2724 0 16:43:56 console 0:01 ./p_printer_status prn_controler2

If some environments are available in a system (OPERATIONAL or SIMULATION), processes can be started by using special parameters.

It is important to create the correct link pointing the environment and position to start-up. <hostname>$ ps -ef | more

root 7274 7262 0 Mar27 tty1 00:00:15 ./pssh SIM 2

root 7276 7262 0 Mar27 tty1 00:01:04 ./supervision_central N 2 S root 7693 7262 0 Mar27 tty1 00:01:06 ./m_control_lan tsp2

lan_controler2

2.3.3 CMD installation 2.3.3.1 User configuration

user_name:x:uid:gid:comment folder_access:login_shell This is a description of each parameter:

x It indicates that the user has a password (the _{user has an entry in the} /etc/shadow file).

gid It is group identifier number (See _file). /etc/group

comment This string is used to include additional _information.

folder_access This parameter includes the path of the application.

Line that user must add to the /etc/passwd file to configure the user for CMD component.

user:x:0:1:User india:/local/india/spv/exec:/usr/bin/ksh

After adding a user, it is necessary to confirm this step using “pwconv” command, and then enter the password for that user with the command “passwd xxx” where xxx is the user name.

(44)

S

U

Page A-28 #vi /etc/passwd

Add corresponding line.

#pwconv

#passwd <user>

New Password: < password>

Re-enter new Password: < password>

Creation of the /local folder with all the permissions: # mkdir –m 777 /local

Alternatively, create a copy of the application from the other CMD: # rsh hostname

#cd /local

# tar -cvf CMDx.indiax.tar india

# gzip -9 -v CMDx.indiax.tar (It will compress the file to CMDx.indiax.tar.gz) # rcp CMDx.indiax.tar.gz <host_name>:/local

Where host_name is the hostname corresponding to the computer on which the application must be installed.

#exit

Decompression and extraction of the application in the computer: # cd /local

# gunzip CMDx.indiax.tar.gz # tar -xvf CMDx.indiax.tar The application will be installed.

Modification and distribution of CONFIG_COM if it is necessary.

REMARK: Please, be sure that all the parameters corresponding to the executables are sent

correctly to the /local/india/spv/exec/startup.cmd file.

The execution folder corresponding to the CMD is /local/india/spv/exec.

Attention should be written to the parameters corresponding to the configuration and boot. File /local/india/spv/exec/startup.cmd.

cd /local/india/spv/exec

NODO_COM=tsp1 export NODO_COM

(45)

S

U

Page A-29 PID_APLICATION=$!

./supervision_central N 1 O > spv.log 2>$1 & export PID_APLICATION

sleep 5

cd /local/india/ctr_lan

./m_control_lan tsp1 lan_controler1 > /dev/null &

sleep 2

cd /local/india/ctr_prn

./p_printer_status prn_controler1 > /dev/null &

Parameters that go with the boot of the executable pssh file will be modified (if it is considerate as convenient).

“OPERATIVO” -> it indicates the environment for starting up “OPERATIVO” for OPERATIVE. The parameters corresponding to the supervision_central line are:

“N” -> for the Gonios control, “N” NO or “S” YES. “O”-> It indicate the string, “O” OPERATIONAL.

To configure the CMD number corresponding to the computer:

<hostname># su – india

<hostname>$ vi startup.cmd

Go to the “NODO_COM” line and change the node for tsp1 or tsp2.

Go to the “./pssh OPERATIVO” line and change 1 or 2 and “OPERATIVO”. Go to the “./supervision_central N” line and change 1 or 2 and O.

Go to the “./p_printer_status prn_controller” line (1 or 2). Go to the “./m_control_lan_tsp_controler” line (1 or 2).

These changes are NOT necessary. It will be enough to link startup.cmd1.ope, startup.cmd2.ope to startup.cmd.

Example:

# ln –sf /local/india/spv/exec/dir_macros/startup.cmd1.ope /local/india/spv/exec/startup.cmd

NOTE: The folder dir_macros, contents every script related to different environment to start-up CMD software.

Creation of the Backup file:

# cd /local

(46)

S

U

Page A-30

# gzip -9 -v CMDx.indiax.tar (It will compress the file to CMDx.indiax.tar.gz) # rcp CMDx.indiax.tar.gz <host_name>:/../FOLDER_BACKUP

Where host_name is the computer where the application is going to be installed or saved

(47)

S

U

Page A-31

2.4 SDD

The SDD is based on powerful workstations where the data, radar data, and flight plans presentations are provided. These data are shown on the controller screens and it can show additional information like geographical maps, airways, meteorological data, etc.

The following diagram shows the location of the folders needed by the system:

Figure 2-4: SDD Files Layout.

The most relevant files are:

Folder /local/sdd/exec.

.mwmrc UNIX file for the definition of Windows parameters. .openwin-init UNIX file for the definition of Windows parameters. .openwin-sys UNIX file for the definition of Windows parameters.

/local/india/ sdd/exec/ pos/exec/ auxfonts/ bin/ bitmaps/ bpt/ datos/ fonts/ grabacion/ pendientes/ reproduccion/ macros/ mapas/ files/ online/ reprod/ print/ screen_files/ config/ adap/ fonts/ printer/ AIP/