0029200000000ma07 2-0 Adm-Um

DOCUMENT N: 0029200000000MA07
Edition:2 Revision:0 Date: 1 November2010
Supply, Installation, Testing and Commissioning of Tower ATS Automation System

System Administrator User Manual (ADM-UM)
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 Torrejn 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.
System Ad mi nist rato r User M a nua l
Use or Disclosure of this information is subject to the restrictions on the tile page of this document
Page A-1
DOCUMENT N: 0029200000000MA07
This page left intentionally blank
Page A-2
DOCUMENT N: 0029200000000MA07
Page A-4
DOCUMENT N: 0029200000000MA07
PAGE EDITION AND REVISION RECORD
This document contains the following pages in the indicated editions and revisions PAGE All All All EDITION Draft 01 02 REVISION 0 0 0 PAGE EDITION REVISION PAGE EDITION REVISION
Page A-5
DOCUMENT N: 0029200000000MA07
Page A-6
DOCUMENT N: 0029200000000MA07
REGISTER OF CHANGES TO THE DOCUMENT
EDITION 1 02
REVISION 0 00
DATE 2010-07-30 2010-11-02
AFFECTED PAGES All All First Edition Second Edition
REASON FOR CHANGE
Page A-7
DOCUMENT N: 0029200000000MA07
Page A-8
DOCUMENT N: 0029200000000MA07
Table of Contents 1 Scope .............................................................................................................................. A-3 1.1 1.2 2 2.1 General purpose ........................................................................................................ A-3 General system overview ........................................................................................... A-3 FDP .......................................................................................................................... A-7 Files layout ....................................................................................................... A-7 FDP processes ................................................................................................A-12 Backup recovery ..............................................................................................A-13
Software Components Detailed Description ....................................................................... A-7 2.1.1 2.1.2 2.1.3
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 2.1.6 2.2 2.2.1 2.2.2 Application configuration ..................................................................................A-15 Backup creation ...............................................................................................A-15 Files layout ......................................................................................................A-16 SDP processes ................................................................................................A-19
SDP .........................................................................................................................A-16
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 2.2.5 2.3 2.3.1 2.3.2 Application configuration ..................................................................................A-21 Backup creation ...............................................................................................A-21 Files layout ......................................................................................................A-22 CMD processes ...............................................................................................A-26
CMD ........................................................................................................................A-22
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 2.3.5 2.4 2.4.1 2.4.2 2.4.3 Application configuration ..................................................................................A-28 Backup creation ...............................................................................................A-29 Files layout ......................................................................................................A-31 SDD processes ................................................................................................A-38 SDD combined with FDD Processes .................................................................A-38
SDD .........................................................................................................................A-31
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
Page A-9
DOCUMENT N: 0029200000000MA07
2.4.5.1 2.4.5.2 2.4.6 2.5 2.5.1 2.5.2
SDD configuration .....................................................................................A-40 SDD with FDD configuration ......................................................................A-41
Backup creation ...............................................................................................A-41 Files layout ......................................................................................................A-43 DRF processes ................................................................................................A-47
DRF .........................................................................................................................A-43
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 2.6 2.6.1 2.6.2 Backup creation ...............................................................................................A-50 Files layout ......................................................................................................A-51 FDD processes ................................................................................................A-53 FDD .........................................................................................................................A-51
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 2.6.5 2.7 2.7.1 2.7.2 2.7.3 Application configuration ..................................................................................A-54 Backup creation ...............................................................................................A-55 Files layout ......................................................................................................A-57 DBM processes ...............................................................................................A-59 DBM Software Backup .....................................................................................A-60
DBM ........................................................................................................................A-57
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 Files layout ......................................................................................................A-62 RDCU processes .............................................................................................A-65 2.8.1 2.8.2
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 Files layout ......................................................................................................A-82
Use or Disclosure of this information is subject to the restrictions on the tile page of this document Page A-10
2.9.1
DOCUMENT N: 0029200000000MA07
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 2.10.1 2.10.2 Backup creation ...............................................................................................A-85 Files layout ......................................................................................................A-86 SFN processes ................................................................................................A-88 2.10 SFN .........................................................................................................................A-85
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 2.11.1 2.11.2 Backup creation ...............................................................................................A-91 Files layout ......................................................................................................A-92 GTI processes .................................................................................................A-94 2.11 GTI ..........................................................................................................................A-92
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 3 Backup creation ...............................................................................................A-96 2.12 Communications configuration ..................................................................................A-97 Starting and finishing processes concerning the system components .............................. A-101 3.1 Starting process ..................................................................................................... A-101 Switching on the computers............................................................................ A-101 Starting up the application .............................................................................. A-101 Shutting down the application ......................................................................... A-101 Shutting down a SDD combined with FDD ...................................................... A-101 Shutting down a FDD ..................................................................................... A-102 Shutting down a SDP ..................................................................................... A-102 Shutting down a FDP ..................................................................................... A-102 Shutting down a CMD .................................................................................... A-102 Shutting down a DRF ..................................................................................... A-102 Shutting down a RDCU .................................................................................. A-102 Shutting down a RDCU Transmission ............................................................. A-102 Shutting down an SFN ................................................................................... A-102 Complete computer switch off......................................................................... A-102 3.1.1 3.1.2 3.2 3.2.1 3.2.2 3.2.3 3.2.4 3.2.5 3.2.6 3.2.7 3.2.8 3.2.9 3.2.10 3.2.11 4
Finishing process.................................................................................................... A-101
System installation and maintenance ............................................................................. A-103
Page A-11
DOCUMENT N: 0029200000000MA07
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 4.2.3 4.2.4 4.2.5 4.2.6 Digi Neo Card ................................................................................................ A-136 FarSync Card ................................................................................................ A-136 Nvidia Graphic Card ....................................................................................... A-138 Quad Port Network Card ................................................................................ A-138 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 4.4 Software Security ................................................................................................... A-154 Diagnostics and errors ............................................................................................ A-155 Processes in the components ......................................................................... A-155
4.4.1
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
Page A-12
DOCUMENT N: 0029200000000MA07
5.1 5.2
Introduction ............................................................................................................ A-161 Procedure to configure a working position as Kickstart server ................................... A-161 NFS Service .................................................................................................. A-162 DHCP Service ............................................................................................... A-162 TFTP Service ................................................................................................ A-162
5.2.1 5.2.2 5.2.3
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 5.4 5.5 How to Kickstart Start-up in a Client Machine: .......................................................... A-165 How to Create Backup from Kickstart ...................................................................... A-165 Folders and important Kickstart files ........................................................................ A-167 Folder /image/kickstart/INDIA/BACKUPS/<DD_MM_YY>/[OPERATIONAL] or [SIMULATION]/position .................................................................................. A-167 Folder /image/kickstart/COMMON .................................................................. A-173 File /root/postinstall.log................................................................................... A-174 File /etc/exports ............................................................................................. A-174 DHCP service ................................................................................................ A-175 XINETD service ............................................................................................. A-175
5.5.1 5.5.2 5.5.3 5.6 5.6.1 5.6.2 5.6.3 6 6.1 A.1 A.2
Procedure to inhibit a machine as Kickstart server ................................................... A-174
Communications Folder ................................................................................................. A-177 COMMUNICATIONS/india/ Folder ........................................................................... A-177 List of Abbreviations ............................................................................................... A-179 Glossary of Terms .................................................................................................. A-180
Appendix A - ABBREVIATIONS AND GLOSSARY OF TERMS ............................................. A-179
Page A-13
DOCUMENT N: 0029200000000MA07
Page A-14
DOCUMENT N: 0029200000000MA07
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
System Ad mi nist rato r User M a nua l Use or Disclosure of this information is subject to the restrictions on the tile page of this document Page A-15
DOCUMENT N: 0029200000000MA07
Figure 4-21: Mail Server Package Details ............................................................................ A-125 Figure 5-1: KickStart Directories .......................................................................................... A-161
Page A-16
DOCUMENT N: 0029200000000MA07
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
Page A-17
DOCUMENT N: 0029200000000MA07
Page A-2
DOCUMENT N: 0029200000000MA07
1 Scope
This Administration Manual guides the user through the Indras 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. Operative System used in this system is Red Hat Enterprise Linux 5.
Page A-3
DOCUMENT N: 0029200000000MA07
Figure 1-1: Directories for the Operational proposal I (Servers & Comunications)
Page A-4
DOCUMENT N: 0029200000000MA07
Figure 1-2: Directories for the Operational proposal II (Workstations & Supervision)
Page A-5
DOCUMENT N: 0029200000000MA07
Page A-6
DOCUMENT N: 0029200000000MA07
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:
/local/India/fdp/exec /local/India/fdp/exec/adap /local/India/fdp/exec/aftn_database /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 aaa /local/India/fdp/exec/historical ggg /local/India fdp/exec/dir_posix_fds aaa /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
Figure 2-1: FDP files layout.
Folder local/india/fdp/exec, the most significant files are:

DOCUMENT N: 0029200000000MA07
FILE
.openwin-init .OUT307 .profile .xinitrc adap aftn_database aftns dir_exec dir_tools dir_posix_fds CONFIG_COM fdp_messages
DESCRIPTION It keeps the X configuration application starts up. This file contains traces. It contains the start concerning the position. up characteristics when the
It creates the adequate environment to start up the position. Folder files. containing the FDP Adaptation Data
Where daily transmission and reception files concerning the AFTN messages are located Where weekly transmission and reception files for AFTN messages are located It contains FDP executable files. This folder contains the FDP tools. This folder contains file descriptor files of the POSIX queues. It defines network communications for all processes involved in component configurations This folder contains the FDP test messages. It is useful in Acceptance tests. Thos folder contains data files processed by the FDP. These files are useful for shared memory and warm start up. This folder contains daily file historic information for each FP. containing
files
historical
killapplication log remote_startup LINE_1
That script kills the FDP application. It must be used by writing:

# ./killapplication (LINUX or SUN) -rmipcs
Folder of system errors This script starts up the application from the CMD. Required file for starting up the X25 server. 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
m_350_india _linux_fdp_task
macros
This folder contains utilities pertaining to the system.
and
scripts
Page A-8
DOCUMENT N: 0029200000000MA07
FILE
printer m_varsovia_linux_fdp_to ols queues
DESCRIPTION This folder keeps information that printed (RPL lists, PFTs, etc.). can be
Tools of FDP. This file is link to a file with the same name that are located in
/local/india/fdp/exec/dir_tools
Folder keeping UNIX queues for communications between processes. This folder keeps daily files containing information related to concluded or not concluded FPLs. This folder contains UNIX semaphores devoted to communications between processes. This folder contains shared memory facilities for the FDP. Script that starts up the FDP. Table 2-1: /local/india/fdp/exec folder.
record
sem shm startup_fdp.sh
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
Page A-9
DOCUMENT N: 0029200000000MA07
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 This folder contains file descriptor files of the POSIX queues.
Page A-10
DOCUMENT N: 0029200000000MA07
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).
Page A-11
DOCUMENT N: 0029200000000MA07
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, 11:33:31, ,4414,0044,259 ,H,WS ,1133,3345N00416W,310 ,1150,RBT , 5,1217 068,TAR003 , ,X,OEJN, ,B744,450 ,GMMN, 11:50:19, ,4412,0048,303 ,H,S ,1150,OJD ,350 ,1150,FES ,350 ,1212,DONAS , 107,1232 069,CNCDF , ,X,GMAD, ,C182,140 ,GMMC, 11:00:00, ,4405,0143,142 ,L,S ,1139,3206N00829W, 115,1149 070,QTR002 , ,X,OEJN, ,B744,450 ,GMMX, 11:50:29, ,4411,0057,372 ,H,WS ,1150,OJD ,350 ,1150,3431N00253W,350 ,1157,MAK 071,TEST1 , ,X,DAAG, ,B734,420 ,GMMN, 12:02:32, ,4415,0056,297 ,M,WS ,1202,OJD ,300 ,1203,SOVAL ,300 ,1228,FES , 136,1252 072,SVA001 , , ,AFIL, , ,0 ,GMMN, 11:43:56, ,4413, , , , 073,OEDDV , ,X,GMME, ,C182,140 ,GMAD, 11:01:00, ,4400,0236,273 ,L,S ,1113,CBA ,109 ,1131,CSD ,110 ,1153,VESEN , 110,1323 074,RAM426 , ,X,GMAD, ,B738,425 ,GMMN, 11:00:00, ,4403,0035,232 ,M,S ,1100,ESS ,167 ,1100,RALEK ,162 ,1122,BRC
,1217,350 ,24-01-05 ORSUP ,350 ,1239,350 ,24-01-05 ORSUP ,350 ,233 ,1225,GODAM ,1243,105 ,24-01-05 VESEN ,115 ,1247,350 ,24-01-05 ORSUP ,350 , 27,1247 ,1258,300 ,24-01-05 ORSUP ,300 ,300 ,1234,GODAM ,0000,0 ,24-01-05
,1337,110 ,24-01-05 ESALA ,65 ,110 ,1232,ADM ,1135,240 ,24-01-05 MOGBA ,162 , 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
root root 23945 1 0 11:30 ? 0 11:31 ? 24351 23945
TIME CMD
00:00:00 m_350_fdp_task 0 FDPS1 00:00:00 ./m_307_supervisor 0 FDPS1
Page A-12
DOCUMENT N: 0029200000000MA07
root root root root root root root root root root root root root root root root root root root root root root root root root root root root root
8040 24351 8041 24351 8042 24351 8043 24351 8044 24351 8045 24351 8046 24351 8047 24351 8048 24351 8049 24351 8050 24351 8051 24351 8052 24351 8053 24351 8054 24351 8055 24351 8056 24351 8057 24351 8058 24351 8059 24351 8060 24351 8061 24351 8062 24351 8063 24351 8064 24351 8065 24351 8066 24351 8067 24351 8068 24351
0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ? 0 11:52 ?
00:00:00 m_399_presence
0 0 0
00:00:00 m_301_init_explorer
00:00:00 m_301_multiple_retrieve_explorer 00:00:00 m_301_refresh 0 0
00:00:00 m_301_recalc_sid_star 00:00:00 m_302_processor 00:00:00 m_303_events 0 0
00:00:00 m_305_rpl_management 00:00:00 m_305_rpl_load 0 0
00:00:00 m_305_rpl_explorer 00:00:00 m_305_rpl_refresh 0
00:00:00 m_306_conflict_probe 00:00:00 m_308_flow_control 00:00:00 m_308_flow_events 00:00:00 m_309_line_rw 00:00:00 m_309_line_rw 00:00:00 m_309_processor 00:00:00 m_310_processor 00:00:00 m_311_notams 0 0 0 0 0 1 2 0 0 0 0 0 0
00:00:00 m_312_line_writer 00:00:00 m_312_line_reader 00:00:00 m_312_processor 00:00:00 m_315_sevents
00:00:00 m_316_airspace_probe 00:00:00 m_316_explorer 00:00:00 m_321_fmtp 0 0
00:00:00 m_310_partner_communication 00:00:00 m_310_partner_communication 00:00:00 m_310_partner_communication
0 0 0
5 X25 2 X25 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.
Page A-13
DOCUMENT N: 0029200000000MA07
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 x uid gid comment folder_access login_shell
It is a user name in the system. It indicates that the user has a password (the user has an entry in the /etc/shadow file). It is the user identifier number. It is file). group identifier is used number to (See
/etc/group
This string information.
include the path
additional of the
This parameter application.
includes
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:
# mkdir m 777 /local
Page A-14
DOCUMENT N: 0029200000000MA07
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
Page A-15
DOCUMENT N: 0029200000000MA07
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.
2.2.1 Files layout

The following diagram shows the location of the folders needed by the system; folder /local/india/rdp/exec:
/local/ india /rdp/exec /local/india/rdp/exec/dir_exec /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
Figure 2-2: SDP Files Layout. The most relevant files in this folder are: FILE
.openwin-init
DESCRIPTION UNIX file with X-Windows parameters.
Page A-16
DOCUMENT N: 0029200000000MA07
FILE
.profile .xinitrc
DESCRIPTION UNIX file containing specifications for starting up the position. UNIX file containing specifications for starting up the position. This file defines the network method applied to the processes component configuration. Link with fich_config.sdp1 or files. Contains the SDP number. Text file containing recording and playback. useful communication in charge of
fich_config.sdp2
CONFIG_COM
fich_config killapplication_sdp LC_TIME
This process frees the shared memory. dates for the
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. 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. 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. 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. 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. 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. 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. 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. 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.
m_sdp_conflict
m_sdp_conflict_mono
m_sdp_meteo
m_sdp_mosaic
m_sdp_player
m_sdp_presence
m_sdp_recorder
m_sdp_supervisor
Page A-17
DOCUMENT N: 0029200000000MA07
FILE
m_sdp_traces
DESCRIPTION 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. 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. Link with startup.sdp.ope or startup.sdp.sim files. Script for cancelling the SDP (off-line). These are files adaptation data. generated from the ( FICH_*)
m_sdp_tracker
startup.sdp killapplication_sdp tabla_*
Table 2-3: SDP Folder /local/india/rdp/exec relevant files Subfolders contents: FOLDER DESCRIPTION This folder contains files that are linked to the processes contained in the /local/india/rdp/exec folder (m_sdp_* files). This folder contains executable files of the SDP system (player, recorder, and traces). 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. This folder contains descriptor files of POSIX queues. file the
/local/india/rdp/exec/dir_exec
/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
This folder contains descriptors of the shared memory tables of the SDP. This folder contains recording files that player uses while reproduction is running. This folder contains parameters related to the ADS contracts.
/local/india/rdp/exec/grabacion
/local/india/rdp/exec/tablas_ads
Table 2-4: /local/india/rdp/exec Subfolder contents
Page A-18
DOCUMENT N: 0029200000000MA07
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_ UID PID PPID C STIME TTY root 5291 1 0 19:03:18 ? root 5408 5291 0 19:03:32 ? root 5395 5291 0 19:03:31 ? root 5396 5291 0 19:03:31 ? root 5397 5291 0 19:03:32 ? root 5412 5291 0 19:03:32 ? root 5398 5291 0 19:03:32 ? root 5413 5291 0 19:03:32 ? TIME 0:11 3:01 20:44 0:57 0:05 0:00 3:09 0:08 CMD ./m_sdp_supervisor m_sdp_conflict_mono m_sdp_tracker m_sdp_adr m_sdp_meteo m_sdp_mosaic m_sdp_conflict m_sdp_presence
In status SIMULATION
[root@<HOSTNAME>3 ~]# root 19692 1 root 19697 19692 root 19698 19692 root 19719 19692 root 19722 19692 root 19723 19692 root 19734 19692 root 19742 19692 ps -ef | grep -i m_sdp 0 Mar28 ? 00:00:00 ./m_sdp_supervisor S 0 Mar28 ? 00:00:17 m_sdp_tracker S 0 Mar28 ? 00:01:38 m_sdp_adr S 0 Mar28 ? 00:00:01 m_sdp_meteo S 0 Mar28 ? 00:00:00 m_sdp_conflict S 0 Mar28 ? 00:00:00 m_sdp_conflict_mono S 0 Mar28 ? 00:00:00 m_sdp_mosaic S 0 Mar28 ? 00:00:00 m_sdp_presence S
2.2.3 SDP installation 2.2.3.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. 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
It is a user name in the system. It indicates that the user has a password (the user has an entry in the /etc/shadow file). It is the user identifier number. It is file). group identifier number (See
/etc/group
Page A-19
DOCUMENT N: 0029200000000MA07
comment folder_access login_shell
is
used
to
include the path
additional of the
includes
INDRA application always uses /usr/bin/ksh shell. 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
#vi /etc/passwd

#pwconv #passwd <user> New Password: <password> Re-enter new Password: <password> passwd: password successfully changed for <user>

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
Decompression and extraction of the application in the computer:
Page A-20
DOCUMENT N: 0029200000000MA07
# cd /local # gunzip SDPx.indiax.tar.gz # tar -xvf SDPx.indiax.tar

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 startup 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$ <HOSTNAME>32$ lrwxrwxrwx 1 -rwxr-xr-x 1 -rwxr-xr-x 1 ln -fs startup.sdp.sim startup.sdp ls -al st* root root 15 Mar 31 10:11 startup.sdp -> startup.sdp.sim root root 469 Feb 11 18:03 startup.sdp.ope 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.

# 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
#exit
Page A-21
DOCUMENT N: 0029200000000MA07
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.
2.3.1 Files layout

The following diagram shows the location of the folders needed by the system:
/local/ india /local/ india /spv/exec /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 /local/india/ctr_lan /local/india/ctr_prn
Figure 2-3: CMD Files Layout. The most relevant files are: Folder /local/india/spv/exec: FILE
.mwmrc
DESCRIPTION
UNIX file for the definition of Windows parameters. It also defines the kind of keyboard and function keys. UNIX file containing start up characteristics for the position. UNIX file containing start up characteristics for the position. This file defines network communications between the processes that configure the components. This folder contains adaptation files.
.profile .xinitrc CONFIG_COM dir_adap
Page A-22
DOCUMENT N: 0029200000000MA07
FILE
dir_aux_files dir_config dir_exec dir_history dir_macros dir_resources dir_sectors dir_updated_tables dir_users fonts
DESCRIPTION This folder contains auxiliary files generated by the application. This folder contains CMD configuration files. This folder contains CMD executable files. This folder contains CMD historic files. This folder contains scripts. This file contains resources files. This file contains sectorization files. This file contains adaptation files. This file contains information. tables files starting concerning from user
This folder contains the type of fonts used by the 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. This is a link with remote_startup file belonging to the dir_macros folder. Link to the PSSH dir_resources folder. file pertaining to the
startup.cmd
remote_startup PSSH pssh sh-env supervision_central
Link to the pssh file pertaining to the dir_exec folder. This file contains the MOTIF environment. Link to a CMD process. Table 2-6: CMD relevant folders.
Folder /local/india/spv/exec/dir_adap: FILE

FICH_* user_passwords.fdp.adap
DESCRIPTION ASCII adaptation files. 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. Folder /local/india/spv/exec/dir_config.
Page A-23
DOCUMENT N: 0029200000000MA07
FILE
f_used_paths.cfg
DESCRIPTION Configuration file containing all PATH related to configuration files and executable files used by the CMD.
Folder /local/india/spv/exec/dir_exec FILE

pssh.00.00 supervision_central.00.00
DESCRIPTION CMD process. It is the graphical part of the application. 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. FILE
aux_comandos startup.cmd1.ope startup.cmd2.ope remote_startup shutdown_system start_system termproc
DESCRIPTION This file sends to the printer the content of the aux_alarmas file. This script starts up the CMD1 for the OPERATIONAL string This script starts up the CMD2 for the OPERATIONAL string This script starts up the application from a remote position. This script shut down all the applications of the system This script starts up all the applications of the system. This script cancels any process. The process must be indicated as a parameter. .
Page A-24
DOCUMENT N: 0029200000000MA07
Folder /local/india/spv/exec/dir_resources. FILE

ding.au plaser_*.pix *.pix printer*.pix PSSH
DESCRIPTION This file contains the CMD sound alarm. Laser printer pictures for screen designing at the CMD. Pixmap files devoted to graphical icons. Printer pictures. Resources file (MOTIF) application on the screen. to display the CMD
Folder /local/india/spv/exec/dir_sectors. FILE

SECTORIZATION*_110
DESCRIPTION ASCII files sectorizations. containing predefined
Folder /local/india/spv/exec/dir_updated_tables. FILE

tabla_*
DESCRIPTION Data files generated from adaptation.
Folder /local/india/spv/exec/dir_users. FILE

USER_*
DESCRIPTION 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. FILE

ps_lp tabla_ps.sh
DESCRIPTION Postscript file concerning to laser printers. Postscript file concerning to tables printing.
Page A-25
DOCUMENT N: 0029200000000MA07
Folder /local/india/ctr_lan. The most relevant files pertaining to the ctr_lan folder are: FILE DESCRIPTION
CONFIG_COM kill_ctr_lan m_control_lan
This files defines the network communication way used by processes that configure the components This file kills the double LAN controller. 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. FILE
CONFIG_COM
DESCRIPTION This file defines the network communication processes between processes that configure the components. This file verifies the printer status. It is a CMD process.
p_printer_status
This file sends the printer status to the CMD for a graphical display. It is a process that p_send_status_printer is triggered by p_printer_status process when it is required.
STATUS_PRINTER_FILE PRINTERS
Temporal file that receives the laser printer status. This file define the printers associated. to the
CONFIG_COM
CONFIG_COM file is a link /local/india/spv/exec folder.
The
file that
is
located
at
the
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 UID PID PPID C STIME TTY root 23233 23149 0 22:41:30 ? lan_controler2 root 2757 2724 0 16:43:31 console root 2758 2724 0 16:43:31 console TIME CMD 0:22 ./m_control_lan tsp2 0:01 ./pssh OPERATIVO 2 0:06 ./supervision_central N 2 O
Page A-26
DOCUMENT N: 0029200000000MA07
root 3064 prn_controler2
2724
0 16:43:56 console
0:01 ./p_printer_status
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 UID PID root root root lan_controler2 -ef | PPID 7274 7276 7693 more C 7262 7262 7262 STIME TTY 0 Mar27 tty1 0 Mar27 tty1 0 Mar27 tty1 TIME CMD 00:00:15 ./pssh SIM 2 00:01:04 ./supervision_central N 2 S 00:01:06 ./m_control_lan tsp2
2.3.3 CMD installation 2.3.3.1 User configuration


/etc/group
include the path
additional of the
includes
INDRA application always uses /usr/bin/ksh shell.
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
Page A-27
DOCUMENT N: 0029200000000MA07
#vi /etc/passwd
Add corresponding line.

#pwconv #passwd <user> New Password: < password> Re-enter new Password: < password> passwd: password successfully changed for <user>

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
#exit

# cd /local # gunzip CMDx.indiax.tar.gz # tar -xvf CMDx.indiax.tar
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 ./pssh OPERATIVO 1 > pssh.log 2>&1 &

DOCUMENT N: 0029200000000MA07
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.

# cd /local # tar -cvf CMDx.indiax.tar india
Page A-29
DOCUMENT N: 0029200000000MA07
# 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
#exit
Page A-30
DOCUMENT N: 0029200000000MA07
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.
2.4.1 Files layout

/local/india/ sdd/exec/ auxfonts/ bin/ bitmaps/ bpt/ datos/ fonts/ grabacion/ pendientes/ reproduccion/ macros/ mapas/ files/ online/ reprod/ print/ screen_files/ config/ pos/exec/ adap/ fonts/ printer/
Figure 2-4: SDD Files Layout. The most relevant files are: Folder /local/sdd/exec. FILE
.mwmrc .openwin-init .openwin-sys
AIP/
DESCRIPTION
UNIX file for the definition of Windows parameters. UNIX file for the definition of Windows parameters. UNIX file for the definition of Windows parameters.
DOCUMENT N: 0029200000000MA07
FILE
.profile
DESCRIPTION This UNIX file contains start up characteristics concerning the position. It is a link to /local/india/sdd/exec/macros. This UNIX file contains start up characteristics concerning the position. It is a link to /local/india/sdd/exec/macros. This folder contains auxiliary set of fonts used by the SDD. This folder contains executables related to the SDD application. This folder contains bitmap files relative to the pictures by the SDD. This folder contains executables concerning monoradar processing (BYPASS) and the necessary adaptation tables. This Folder contains colour parameters concerning the SDD display. This folder contains the set of fonts used by the SDD. This folder carries out the SDD 24 h. recordings. File that contains entries with an action: process format. It is used as a parameter when the SDD starts up. This script starts up the application in a remote mode. Hour format file This folder contains the maps to be visualized at the SDD. X-Windows resources file. This folder contains all the parameters concerning the SDDs configurations. This folder is PLAYBACK mode. used when the SDD operates in
.xinitrc
auxfonts bin bitmaps
bpt
datos fonts grabacion inictab
remote_startup LC_TIME mapas Mwm online
reprod/reprod24h
The Aplicacion.gen equivalent to the mode is active.
and Aplicacion.24h files are Aplicacion.pos file when normal
sh-env tabla_*
This file contains the MOTIF environment. These tables are generated starting from adaptation tables.
Folder /local/india/sdd/exec/bin.
Page A-32
DOCUMENT N: 0029200000000MA07
Process description: PROCESS

m_sdd_inic m_sdd_graf
DESCRIPTION
This process creates and initiates shared memory (local database). The size of this shared memory is determined by the off-line configuration. It displays the information presented on the SITs.
This process creates and upgrades all windows produced by the application (except for SIT windows). At the same time, this process receives and processes all the actions produced by the operator on these windows (SIT windows included). All the actions carried out by m_sdd_interac interac are due to external events like ATC messages or actions executed by the operator. One exception is the periodic activation (timeout) that performs the XXXXX of the tabular lists devoted to flight plans starting from messages received from the ATC process.
m_sdd_grabac
This process performs slow recording actions like files compression and fragmentation, files number control on disks etc. This process receives external information (tracks, Flight Plans, Alerts...) and save it on the local database. PCV actions that are not kept on a database get external communication by means of the interac process. In addition, the atc process manages Flight Plans tabulars (ordinations, FP insertions, and extractions from the list). This process starts up the rest of the processes. It reads the inictab file that contains entries with an action: process format. This process is used to move the windows This process is used to playback mode. This process is used to playback mode. This process is used to playback mode.
m_sdd_atc
m_sdd_monitor m_sdd_iwm m_sdd_pbk m_sdd_tape1 m_sdd_tape2
Utilities description: TOOL
DESCRIPTION It erases shared memories. The parameter defines the user so If it is used with no parameters, it will erase all memories belonging to the $USER user and if used with a specific parameter it will erase all memories belonging to this defined user taking into account that the user who executes this command must have the requisite authorisation otherwise it will not be executed.
./bin/rmipcs
Page A-33
DOCUMENT N: 0029200000000MA07
TOOL
./bin/termproc
DESCRIPTION The monitor processes by kill 15. uses this command to stop means of sending to them a sending to the
./bin/killproc
Similar to termproc but processes a kill 9.
This file mixes adaptation data with the off-line configuration file of the application. It is executed before starting up or rebooting the application, so that changes concerning adaptation data will be accepted when rebooting the system.
./macros/m_sdd_confadapt
This file also reads the file FICH_GONIOS and creates the file FICH_GONIOS.sdd reads the file FICH_DATOS_GEOGRAFICOS and creates the file FICH_DATOS_GEOGRAFICOS.sdd reads the file FICH_RADAR and creates the file FICH_RADAR.sdd Is executed before starting up the application so, if adaptation data are modified, it is only necessary to restore the application to assume these changes.
./bin/tdrlocal
By-pass process. It works as an intermediary between SDP and CMD messages.
Folder /local/india/sdd/exec/adap. FILE

FICH_*
DESCRIPTION Required adaptation monoradar processing. files for
Folder /local/india/sdd/exec/bpt FILE

m_sdp_bypass m_sdp_bypass_??.??
DESCRIPTION Link to the m_sdp_bypass_??.?? file. Monoradar processing version.
Folder /local/india/sdd/exec/datos. This folder contains the colour configuration files mapas.rgb and pistas.rgb. Folder /local/india/sdd/exec/grabacion. This folder keeps all files related to recording. Folder /local/india/sdd/exec/grabacion/pendientes.
Page A-34
DOCUMENT N: 0029200000000MA07
This folder stores the recorded files before being sent to the DRF system. Once they are sent, the files are deleted automatically. Folder /local/india/sdd/exec/grabacion/reproduccion. This folder stores recorded files that are going to be reproduced on the SDD whilst Playback Mode (not Playback 24 hours mode). Folder /local/india/sdd/exec/config FILE
Aplicacion.sdd colores CONFIG_COM
DESCRIPTION
Resources and parameters used by the SDD in case of standard way of working (CONTROL). Colours definitions for pistas.rgb file. It defines network communications for all processes involved in component configurations.
Folder /local/india/sdd/exec/macros. This folder contains the SDD macros: m_sdd_confadapt Folder /local/india/sdd/exec/mapas. This folder keeps the folder /local/india/sdd/exec/mapas/files (that stores all the FIR maps) and the user maps stored in the local maps allocated in SDDs.
files MapaLocal MapaLocal1 MapaLocal2 MapaLocal3 MapaLocal4 MapasLocales
Folder /local/india/sdd/exec/online. This folder keeps user configurations for personalizing their desks. It is possible to save the configuration stored in Conf1 as the configuration by default just executing the following commands
# cpp /local/india/sdd/exec/online/Conf1 /local/india/sdd/exec/online/defecto.
Cab1
Cab2 Cab3 Conf1 Conf2 Conf3 Conf4

Defecto
Page A-35
DOCUMENT N: 0029200000000MA07
Folder /local/india/sdd/exec/print. FILE

lp_cabecera lp_final macro_lp
DESCRIPTION
Postscript file concerning laser printing. Postscript file concerning laser printing. Postscript file concerning laser printing. Table 2-7: SDD /local/india/sdd/exec/print folder relevant files.
Folder /local/india/sdd/exec/playb This folder keeps all the information and files related to the SDD playback function. It is the root folder whilst Playback mode. Usually, this folder is the execution path for playb user. Folder /local/india/sdd/exec/playb24h This folder keeps all the information and files related to the SDD playback 24 hour function. It is the root folder whilst Playback 24 hour mode. Usually, this folder is the execution path for playb24h user. Folder /local/india/sdd/exec/screen_files This folder keeps a copy of the images that the user wants to save on the Playback or Playback 24 hour mode when the option save image to file is selected. NOTE: If the position is SDD with FDD there are a folder named
Folder /local/india/pos/exec FILE

.mwmrc
DESCRIPTION
UNIX file for the definition of Windows parameters. It also defines the kind of keyboard and function keys. UNIX file for parameters. UNIX file for parameters. the the definition definition of of Windows Windows produced up to
.openwin-init .openwin-sys .OUT507 .profile adap AIP
This output file keeps messages during the lifetime of the system.
This UNIX file contains start characteristics concerning the position. This folder contains links
/local/india/sdd/exec/bpt.
This folder contains all the files related to the AIP. This file defines the network communication processes between processes that configure the components. This FDD. folder contains the fonts used by the
CONFIG_COM
fonts
Page A-36
DOCUMENT N: 0029200000000MA07
FILE
killapplication LC_TIME
DESCRIPTION This script shut down the FDD application. Hour format files FDD application process. It manages the interaction with the server. It is a link to a file with the same name but with the version name added. X-Windows resources file. FDD resources file. This file file. is a link to
PCV_with_sdd<version>
m_502_pos
mwm PCV PCV_fdd printer sh-env
This folder contains useful printer files. This file contains the MOTIF environment.
File /local/india/pos/exec/pos1
#!/bin/sh DISPLAY=:0.1 export DISPLAY #necessary resources to configure the HTML widget xset +fp /local/india/sdd/exec/pos/fonts fp rehash if [ -f /usr/bin/ps_lp ] then rm -f /usr/bin/ps_lp fi /usr/lib/lp/local/lpsched ln -s /local/india/sdd/exec/pos/printer/ps_lp /usr/bin/ps_lp cd /local/india/sdd/exec/pos XAPPLRESDIR=. export XAPPLRESDIR cat ./PCV_fdd ./adap/FICH_PRINTERS > ./PCV m_502_pos FDD_AFTN1 WITH_SDD
Folder /local/india/pos/exec/printer This folder contains temporary files for printings. Folder /local/india/pos/exec/AIP This folder contains all the files and folders related to the AIP. They are shown on the FDD as the option PIP (Paged Information Publication). There are two compulsory folders: FOLDER DESCRIPTION
Page A-37
DOCUMENT N: 0029200000000MA07
FOLDER
DESCRIPTION
This folder contains several files *.html that the system /local/india/sdd/exec/pos/AIP/aip.php_fil uses to perform the tree es folder that is shown on the FDD. This folder contains the file
documents/instructions.html /local/india/sdd/exec/pos/AIP/others
that the user must read in order to add more documents to the PIP.
2.4.2 SDD 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>@<HOSTNAME>$ ps -ef | grep m_ UID PID PPID C STIME TTY root 2243 2238 0 16:44:29 ? root 2167 2130 0 16:44:24 ? root 2249 1 7 16:44:39 ? root 2294 1 0 16:44:41 ? root 2333 1 1 16:45:02 ? root 2262 1 1 16:44:39 ? root 2275 1 0 16:44:40 ? TIME CMD 0:10 m_sdp_bypass 2 0:00 m_sdd_monitor inictab 1:09 m_sdd_graf 0:00 m_sdd_iwm 0:08 m_sdd_atc 0:07 m_sdd_interac 0:00 m_sdd_grabac
2.4.3 SDD combined with FDD Processes

<HOSTNAME>@<HOSTNAME>14$ UID PID PPID C root 2243 2238 0 root 2167 2130 0 root 2249 1 7 root 2188 2165 0 root 2294 1 0 root 2333 1 1 root 2262 1 1 root 2275 1 0 ps -ef | STIME 16:44:29 16:44:24 16:44:39 16:44:25 16:44:41 16:45:02 16:44:39 16:44:40 grep m_ TTY ? ? ? ? ? ? ? ? TIME 0:10 0:00 1:09 0:02 0:00 0:08 0:07 0:00 CMD m_sdp_bypass 2 m_sdd_monitor inictab m_sdd_graf m_502_pos FDD_AFTN4 WITH_SDD m_sdd_iwm m_sdd_atc m_sdd_interac m_sdd_grabac
2.4.4 SDD combined with FDD installation 2.4.4.1 User configuration

Page A-38
DOCUMENT N: 0029200000000MA07

/etc/group
include the path
additional of the
includes
Line that user must add to the /etc/passwd file to configure the user for SDD and SDD with FDD component.
user:x:0:1:User india:/local/india/sdd/exec:/usr/bin/ksh
playb24h:x:0:1:User india:/local/india/sdd/exec/reprod:/usr/bin/ksh
In this component, it is necessary adding the playb24h and playb users that are the users of the SDD reproduction mode, playb24h for local reproduction and playb for reproduction combined with DRF.
playb:x:0:1:User india:/local/india/sdd/exec/reprod:/usr/bin/ksh
playb24h:x:0:1:User india:/local/india/sdd/exec/reprod24h:/usr/bin/ksh
After adding a user or users, it is necessary to confirm this step using pwconv command, and then enters the password for each 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

#pwconv #passwd <user> New Password: < password> Re-enter new Password: < password> passwd: password successfully changed for <user>

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

#rsh hostname
Page A-39
DOCUMENT N: 0029200000000MA07
#cd /local # tar -cvf SDDx.indiax.tar india
Where x is the SDD number and the computer hostname where the application has been created.
# gzip -9 -v SDDx.indiax.tar (It will compress the file to SDDx.indiax.tar.gz) # rcp SDDx.indiax.tar.gz <host_name>:/local
Where host_name is the hostname corresponding to the computer where the application must be installed.
#exit

# cd /local # gunzip SDDx.indiax.tar.gz # tar -xvf SDDx.indiax.tar
2.4.5 Application configuration 2.4.5.1 SDD configuration

Configuration to the resolution in SDD position: When the backup, from which the application was obtained, does not match the monitor resolution, the Cab1, Cab2, Cab3, Conf1, Conf2, Conf3, Conf4, defecto differences must be taken into account in the files belonging to the /local/india/sdd/exec/online folder. The resolution corresponding to a EIZO 22 is 1680x1050+0+0, for a EIZO HB 20" is 1280x1024+0+0 and for a TECH SOURCE monitor 2048x2048+0+0 These resolutions must be specified in the /local/india/sdd/exec/online folder. Example: /local/india/sdd/exec/online/Cab1 file corresponding to a EIZO 22" monitor:
sit1 1 3 1680x1050+0+0 283093 1848 1199 submapa1 1 submapa2 1
..
Example: /local/india/sdd/exec/online/Cab1 file corresponding to a EIZO HB 20" monitor:

sit1 1 3 1280x1024+0+0 283093 1848 1199 submapa1 1 submapa2 1
..
Operational Supervision SDD configuration:

# # Type of position: SUPERVISOR_RP SUPERVISOR_ST UCS # planificador =0:one sdd, one UCS, planificador =1: two sdd, one UCS Aplicacion*misc.planificador: 1 Aplicacion*misc.tipoPosicion: SUPERVISOR_RP
Page A-40
DOCUMENT N: 0029200000000MA07
Depending of the type of position to be installed, the line *misc.tipoPosicion: must be modified; If the position belongs to a UCS, add the UCS value SUPERVISOR_RP in this line (for the Operative Supervision position). Printer configuration strips (if it is applicable): In this file is the activate to executable for start to controller printing in the SDD positions.
cat $HOME/CONFIG_COM | nawk -v HOSTNAME=`hostname` '{ if($1=="#"HOSTNAME) { for(i=2;i<=NF;i++) { sw=0; for(j=1;j<=length($i);j++) { if(substr($i,j,1)=="_") { sw=1; } } if(!sw) { print $i; break; } } } }' > $HOME/nodo_com echo Aplicacion*misc.idSistema: `cat $HOME/nodo_com | nawk '{print substr($0,4);}'` > $HOME/Aplicacion.pos # Controller printing strip if [ -x IFV ]; then rm IFV fi #ln -s /dev/term/a IFV #/local/india/sdd/exec/m_510_strips $HOME/Aplicacion.pos > /dev/null 2>&1 &
Printer configuration for function in mode playback (Capture): In folder /local/india/sdd/exec/adap, Strip printer configuration for SDD printing options must be done by file FICH_SDD_PRINTERS, which defines for every SDD position its printing server. The file is generated by DBM (see DBM User Manual) and it is read by the application in its start-up. (if it is applicable) In the folder /local/india/sdd/exec/print is generated to file:
vgeo.ps (This file is temporary, when capture another picture is erased and generated another
file with the same name).
2.4.5.2 SDD with FDD configuration

The /local/india/pos/exec/pos/PCV must be a link to PCV_with_sdd.<version>. The /local/india/sdd/exec/m_502_pos must be a link to m_502_pos.<version>.

Creation of the backup file:
DOCUMENT N: 0029200000000MA07
# cd /local # tar -cvf SDDx.indiax.tar india
Where X is the SDD number and the computer hostname where application has been created.
# gzip -9 -v SDDx.indiax.tar (It will compress the file to SDDx.indiax.tar.gz) # rcp SDDx.indiax.tar.gz <host_name>:/../FOLDER_BACKUP
Page A-42
DOCUMENT N: 0029200000000MA07
2.5
DRF
This component records continuously all the data related to the tracks data, flight plans data, and the controller actions to allow later playback and analysis.
2.5.1 Files layout

/local/india/ sdd/exec/ auxfonts/ fonts/ bitmaps/ adap/ bin/ grabacion/ pendientes/ reproduccion/ directorios1/ directorios2/ cinta/ de_cinta/ prereproducidos/ pregrabados/ archiv/ macros/ print/ config/ keymaps/
Figure 2-5: DRF Files Layout.
Page A-43
DOCUMENT N: 0029200000000MA07
The most relevant files are: Folder /local/india/sdd/exec. FILE

.mwmrc .openwin-init .openwin-sys .profile .xinitrc auxfonts bin bitmaps fonts grabacion
DESCRIPTION This is a UNIX parameters. This is a UNIX parameters. This is a UNIX parameters. file file file that that that defines defines defines Windows Windows Windows for for
UNIX file containing specifications starting up the position. UNIX file containing specifications starting up the position.
This folder contains auxiliary set of fonts used by the DRF. This folder contains executable concerning the DRF application. files
This folder contains bitmap files relative to the pictures by the DRF. This folder contains the fonts used by the DRF. This folder performs recordings concerning to all SDD within the DRF. File that contains entries with an action: process format. It is used as a parameter when the DRF starts up. This script starts up the application in a remote mode. Hour format file X-Windows resources file. This file contains the MOTIF environment. Useful DRF adaptation tables. Encrypted adaptation file that contains information about users, alias, roles, and password.
inictab
remote_startup LC_TIME mwm sh-env tabla_* user_passwords.fdp.adap
Folder /local/sdd/exec/config FILE

CONFIG_COM
DESCRIPTION
This file defines the network communication processes between processes that configure the components.
DOCUMENT N: 0029200000000MA07
FILE
colores aplicacion.sdd
DESCRIPTION Colours definitions for pistas.rgb file. Resources and parameters.
Folder /local/india/sdd/exec/grabacion FILE

directorios1 directorios2 de_cinta
DESCRIPTION auxiliary auxiliary files files for for
This folder contains controlling the tapes. This folder contains controlling the tapes.
This is the folder that contains the tape files when they are extracted. This folder contains the files that the SDDs send to the DRF and are not still recorded into the tapes. When a file is recorded on a tape, this is deleted automatically from this folder. If the tapes are not working, then the files in this folder will be kept until the tapes are OK or there is no more space available in the drive disk. This folder is not applicable for the DRF system.
pregrabados
prerreproducidos
File /local/india/sdd/exec/inictab:
off:graf off:interac off:grabac off:atc off:cinta1 off:cinta2 off:m_sdp wait:rmipcs root wait:confadapt wait:inic init:tdrlocal > /dev/null 2> /dev/null init:interac init:grabac init:cinta1 init:cinta2 init:atc exit:termproc_total m_sdp exit:rmipcs root
REMARK: All the subfolders concerning the DRF application have the same functionality and content as those of the SDD application, the only exception is the /local/india/sdd/exec/grabacion folder.
Page A-45
DOCUMENT N: 0029200000000MA07
Folder /local/india/sdd/exec/bin. Process description: PROCESS

m_drf_inic
DESCRIPTION
This process creates and initiates shared memory (local database). The size of this shared memory is determined by the off-line configuration.
This process creates and upgrades all windows produced by the application (except for SIT windows). At the same time, this process receives and processes all the actions produced by the operator on these windows (SIT windows included). All the actions carried out by m_drf_interac interac are due to external events like ATC messages or actions executed by the operator. One exception is the periodic activation (timeout) that performs the XXXXX of the tubular lists devoted to flight plans starting from messages received from the ATC process. This process receives external information (tracks, Flight Plans, Alerts...) and save it on the local database. PCV actions that are not kept on a database get external communication by means of the interac process. In addition, the atc process manages Flight Plans tabulars (ordinations, FP insertions, and extractions from the list). This process starts up the rest of the processes. It reads the inictab file that contains entries with an action: process format. This process is used to move the windows This process manages the tapes status, SDD recording files, and folders, progression when a message changes from pending to pre-recorded, etc. This process also sends messages to the SDDs so they can send files to DRF corresponding to a specific hour or immediately recording. This process does exactly the same as m_drf_tape1 but relative to tape2.
m_drf_atc
m_drf_monitor m_drf_iwm
m_drf_tape1
m_drf_tape2
Page A-46
DOCUMENT N: 0029200000000MA07
Utilities description: TOOL
DESCRIPTION It erases shared memories. The parameter defines the user so If it is used with no parameters, it will erase all memories belonging to the $USER user and if used with a specific parameter it will erase all memories belonging to this defined user taking into account that the user who executes this command must have the requisite authorisation otherwise it will not be executed. The monitor uses this command to stop processes by means of sending to them a kill 15. Similar to termproc processes a kill 9. but sending to the
rmipcs
termproc
killproc
This file mixes adaptation data with the offline configuration file of the application. It is executed before starting up or rebooting the application, so that changes concerning adaptation data will be accepted when rebooting the system.
macros/m_sdd_confadapt
This file also reads the file FICH_GONIOS and creates the file FICH_GONIOS.sdd reads the file FICH_DATOS_GEOGRAFICOS and creates the file FICH_DATOS_GEOGRAFICOS.sdd reads the file FICH_RADAR and creates the file FICH_RADAR.sdd Is executed before starting up the application so, if adaptation data are modified, it is only necessary to restore the application to assume these changes.
2.5.2 DRF 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>@<HOSTNAME>9$ ps -ef | grep m_ UID PID PPID C STIME TTY root 3551 1 0 17:40:56 ? root 3492 3459 0 17:40:55 ? root 3579 1 0 17:40:57 ? root 3566 1 0 17:40:56 ? root 3594 1 0 17:40:57 ? root 3609 1 0 17:40:57 ? TIME 0:00 0:00 0:00 0:00 0:00 0:00 CMD m_drf_interac m_drf_monitor inictab m_drf_tape1 m_drf_atc m_drf_tape2 m_drf_iwm
Page A-47
DOCUMENT N: 0029200000000MA07
2.5.3 DRF installation 2.5.3.1 User configuration


/etc/group
include the path
additional of the
includes
Line that user must add to the /etc/passwd file to configure the user for DRF component.
user:x:0:1:User india:/local/india/sdd/exec:/usr/bin/ksh
ftp_copy:x: 0:1:User FTP:/local/india/sdd/exec/grabacion/pregrabacion:/usr/bin/ksh
For DRF position, always must be included a generic user which allows the rest of SDD positions to perform the copy via FTP protocol. A new user must be created, which name and passwords must be " ftp_copy" (this password should never be changed). 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

#pwconv #passwd <user> New Password: <password> Re-enter new Password: <password> passwd: password successfully changed for user
Page A-48
DOCUMENT N: 0029200000000MA07

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

#rsh hostname #cd /local # tar -cvf DRFx.indiax.tar india
Where x is the DRF number and the computer hostname where the application has been created.
# gzip -9 -v DRFx.indiax.tar (It will compress the file to DRFx.indiax.tar.gz) # rcp DRFx.indiax.tar.gz <host_name>:/local
#exit

# cd /local # gunzip DRFx.indiax.tar.gz # tar -xvf DRFx.indiax.tar
The application will be installed. Modification and distribution of CONFIG_COM if it is necessary. The component DRF knows if a computer is running as DRF or DRF checking this automatically from the CONFIG_COM file.
2.5.3.3 Application configuration

Tapes creates character special files in the /dev folder named st0, st1, nst0 and nst1. The tapes command searches the kernel device tree to see what tape devices are attached to the system. The different tape types are: TAPE TYPE NATIVE CAPACITY DDS 2 Gb DDS2 4 Gb DDS3 12 Gb DDS4 20 Gb DAT72 36 Gb DAT160 80 Gb COMPRESSED CAPACITY 4 Gb 8 Gb 24 Gb 40 Gb 72 Gb 160 Gb
Table 2-8: DRF Tape types
2.5.3.4 Deleting recording files in the DRF

# pwd /local/india/sdd/exec # rm -rf tar1.tmp tar2.tmp # cd grabacion
Page A-49
DOCUMENT N: 0029200000000MA07
# pwd /local/india/sdd/exec/grabacion # rm encurso2 or encurso1
# # # #
rm rm mt mt
*/* -rf directorios directorios2 -f /dev/nst0 erase -f /dev/nst1 erase

# cd /local # tar -cvf DRFx.indiax.tar india
Where x is the DRF number and the computer hostname where application has been created.
# gzip -9 -v DRFx.indiax.tar (It will compress the file to DRFx.indiax.tar.gz) # rcp DRFx.indiax.tar.gz <host_name>:/../FOLDER_BACKUP
Page A-50
DOCUMENT N: 0029200000000MA07
2.6
FDD
This component presents information about flight plans ignoring their air situations. It allows the operators to manage the flight plans and related meaningful data like activation of restricted areas, manage repetitive flight plans, AFTN message corrections, air flow managemeny, Paged Information Pagination visualization, etc.
2.6.1 Files layout

/local/india/pos/exec //adap //fonts //printer //AIP
Figure 2-6: FDD Files Layout. The most relevant files are: Folder /local/india/pos/exec: FILE
.mwmrc
DESCRIPTION
UNIX file for the definition of Windows parameters. It also defines the kind of keyboard and function keys. UNIX file for parameters. UNIX file for parameters. the the definition definition of of Windows Windows produced up
.openwin-init .openwin-sys .OUT507 .profile adap AIP
This output file keeps messages during the lifetime of the system.
This UNIX file contains start characteristics concerning the position. This folder contains FDD adaptation data.
This folder contains all the files related to the AIP. This file defines the network communication processes between processes that configure the components. This FDD. folder contains the fonts used by the
CONFIG_COM
fonts killapplication remote_startup startup_fdd.sh
This script shut down the FDD application. This script starts remote mode. up the application in a
Script that starts the FDD position.

DOCUMENT N: 0029200000000MA07
FILE
LC_TIME
DESCRIPTION Hour format files FDD application process. It is a link to a file with the same name but with the version name added. This process is used to move the windows (windows manager). FDD application process. It manages the interaction with the server. It is a link to a file with the same name but with the version name added. FDD application process. It shows the presence in the CMD position. It is a link to a file with the same name but with the version name added. X-Windows resources file. FDD resources file. This file is a link to PCV_without_sdd<version> file. Link to the serial port used by the printer (if it exists), (/dev/term/a). This file contains the MOTIF environment. Tally
m_502_iwm
m_502_pos
m_599_presence
mwm PCV PCV_fdd PRINTER printer sh-env
This folder contains useful printer files.
Folder /local/india/pos/exec/printer. This folder contains temporary files for printings. Folder /local/india/pos/exec/AIP. This folder contains all the files and folders related to the AIP, and are shown on the FDD as the option PIP (Paged Information Publication). There are two compulsory folders: FOLDER DESCRIPTION This folder contains several files *.html that the system uses to perform the tree folder that is shown on the FDD. This folder contains the file document.html that the user must read in order to add more documents to the PIP.
/local/india/pos/exec/AIP/aip.php_files
/local/india/pos/exec/AIP/others
Page A-52
DOCUMENT N: 0029200000000MA07
2.6.2 FDD processes

<HOSTNAME>20# ps -ef | grep m_ UID PID PPID C STIME TTY root 1257 1195 0 16:44:17 ? WITHOUT_SDD root 1263 1195 0 16:44:18 ? root 1260 1195 0 16:44:18 ? TIME CMD 0:01 m_502_pos FDD_AFTN1 0:00 m_502_iwm 0:00 m_599_presence FDD_AFTN1
2.6.3 FDD installation 2.6.3.1 User configuration


/etc/group
include the path
additional of the
includes
Line that user must add to the /etc/passwd file to configure the user for FDD component.
user:x:0:1:User india:/local/india/pos/exec:/usr/bin/ksh
#vi /etc/passwd
Page A-53
DOCUMENT N: 0029200000000MA07
#pwconv #passwd user New Password: (type password) Re-enter new Password: (re-type password) passwd: password successfully changed for user

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

# cd /local # tar -cvf FDDx.indiax.tar india
Where x is the FDD number and the computer hostname where the application has been created.
# gzip -9 -v FDDx.indiax.tar (It will compress the file a FDDx.indiax.tar.gz) # rcp FDDx.indiax.tar.gz <host_name>:/local
#exit

# cd /local # gunzip FDDx.indiax.tar.gz # tar xvf FDDx.indiax.tar

The FDD execution folder will be /local/india/pos/exec. File /local/india/pos/exec/startup_fdd.sh. Depending of the type of position to be installed, the line m_502_pos FDD_AFTN2 must be modified in the /local/india/pos/exec/startup_fdd.sh file. Depending of the type of position to be installed, the line m_599_presence FDD_AFTN2 must be modified in the /local/india/pos/exec/startup_fdd.sh file. The line m_502_pos must have /local/india/pos/exec/startup_fdd.sh file.
REPORTS_FILE=.REPORTS export REPORTS_FILE mv $REPORTS_FILE $REPORTS_FILE.old touch $REPORTS_FILE FICH_REPORTS=.OUT507 export FICH_REPORTS mv $FICH_REPORTS $FICH_REPORTS.old touch $FICH_REPORTS
the
string
WITHOUT_SDD
in
the
DOCUMENT N: 0029200000000MA07
echo "output to file $FICH_REPORTS" echo "\n\n\n\nSTARTING APPLICATTION\n\n\n\n" >> $FICH_REPORTS APLICATION_FATHER=0 #If the application was running, it is killed # killapplication #eliminate possible old core # rm core > /dev/null 2>&1 rm /usr/bin/ps_lp > /dev/null 2>&1 # /usr/lib/lp/lpsched #Necessary resources to configure the HTML widget xset fp default xset +fp /local/india/pos/exec/fonts fp rehash if [ ! -d printer ] then echo "ERROR : folder printer does not exists " >> $FICH_REPORTS fi ln -s /local/india/pos/exec/printer/ps_lp /usr/bin/ps_lp #Application is started # cat ./PCV_fdd ./adap/FICH_PRINTERS > ./PCV m_502_pos FDD_AFTN1 WITHOUT_SDD >> $REPORTS_FILE m_599_presence FDD_AFTN1 >> $REPORTS_FILE 2>&1 m_502_iwm & APLICATION_FATHER=$! export APLICATION_FATHER 2>&1 & &
The /local/india/sdd/exec/pos/PCV must be a link to PCV_without_sdd.<version>

# cd /local # tar -cvf FDDx.indiax.tar india
Where x is the FDD number and the computer hostname where application has been created.
# gzip -9 -v FDDx.indiax.tar (It will compress the file to FDDx.indiax.tar.gz) # rcp FDDx.indiax.tar.gz
<host_name>:/../FOLDER_BACKUP
Page A-55
DOCUMENT N: 0029200000000MA07
Page A-56
DOCUMENT N: 0029200000000MA07
2.7
DBM
It provides the system with the necessary data for the creation and modification of the database adaptation data locating the system in its geographical environment and optimizing the system performance.
2.7.1 Files layout

/var/lib/pgsql /local/india/adap/exec /map_files /files /tcl_tk /databases /databases/* /program
Figure 2-7: DBM Files Layout. Where * is the data base name. The most relevant files are: Folder /var/lib/pgsql. This is the folder that contains the macros that controls the status of user postgres. This is the database user. FILE DESCRIPTION
pgsql_start pgsql_status pgsql_stop .bash_profile
Script that starts up the database server. Script that shows the database server status. Script that shutdowns the database server. User profile file.
Folder /var/lib/pgsql/data. This is the folder that contains the database internal files. FILE DESCRIPTION
pg_hba.conf
PostgreSQL Client Authentication configuration file.
Folder /local/india/adap/exec/files. This is the folder where all the *.adap files are created when there is a generation of FDP files. After this generation, all this files are automatically copied to /local/india/adap/exec/tcl_tk/databases/*/adap_files. Folder /local/india/adap/exec/map_files. This is the folder where all the map files are created when there is a generation of MAP files. After this generation, all this files are automatically copied to /local/india/adap/exec/tcl_tk/databases/*/map_files.
Page A-57
DOCUMENT N: 0029200000000MA07
Folder /local/india/adap/exec/program. This is the folder where all the SDP files are created when there is a generation of SDP files. After this generation, all this files are automatically copied to /local/india/adap/exec/tcl_tk/databases/*/rdp_files. This folder also contains the executable files that are used to generate all the files. The executable files are the followings: FILE DESCRIPTION
m_314_generate_ascii_spv_sdp.exe
This is a link to an executable file in charge of generating SDP, CMD, and SDD adaptation data.
This is a link to an executable file in charge of m_314_generate_adaptation_data_files.exe generating FDP and SIM adaptation data.
m_314_generate_map_files.exe
This is a link to an executable file in charge of generating maps for the system. This is a link to an executable file in charge of converting SDP adaptation data into tabla* files. This is a link to an executable file in charge of generating DLS adaptation data. This is a link to an executable file in charge of converting DLS adaptation data into t_dls* files.
m_sdp_generacion_ficheros_local.exe
m_008_generar_datos_dls.exe
m_1118_generar_datos.exe
Folder /local/india/adap/exec/tcl_tk. FILE

dbsman.tcl *_db.tcl *_ed.tcl
DESCRIPTION
Executable File in charge of starting up the database devoted to india. These files allow the access sections of the database. These files allow editing pertaining to the database. to same
information
*.tcl *.gif *.sql *.map
These files contain the main screen in the database and corresponding to a particular section. These files are necessary in order to have a correct functionality of the system (graphics, links to sql, etc.)
Page A-58
DOCUMENT N: 0029200000000MA07
FILE
DESCRIPTION This file is the last backup that the user requested (it does not matter the database you select to create a backup, and it is updated when the user requests a new backup). It is also copied to
/local/Supply and Installation of Equipment for/adap/exec/tcl_tk/databases/*/backup the
database.bck
load_fdp_adaptation_data.sh load_adaptation_maps.sh
It loads the operational data into the Operational string. It loads the adaptation Operational string. maps into the
CONFIG_COM
This file defines the network communication processes between processes that configure the components.
Folder /local/india/adap/exec/tcl_tk/databases. This folder will contain as many folders as databases are in the DBM. These folders have the database names. Folder /local/india/adap/exec/tcl_tk/databases/*/: FOLDER DESCRIPTION
adap_files map_files
This folder keeps necessary files for the FDP (*.adap). This folder keeps necessary files for maps displaying. They are loaded at the SDDs and Pilot or Session Manager (if simulation string is installed) This folder keeps necessary files for the SDP and the CMD and for monoradar belonging to the SDDs. This folder loads files that have been generated executing a report.file action at the DBM application. This folder keeps necessary files for the DLS. This folder stores database.bck file that is a backup of the database. It is copied from /local/india/adap/exec/tcl_tk and it is updated when the user requests a new backup. when
rdp_files reports dls_files backup
2.7.2 DBM 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 psql from the console. On this computer, no one process is running except database server process.
# ps ef | grep pgsql UID PID PPID C STIME TTY TIME CMD
Page A-59
DOCUMENT N: 0029200000000MA07
postgres 19484 1 0 18:25:48 pts/9 0:00 /usr/local/pgsql/bin/postmaster -i -D /usr/local/pgsql/data
2.7.3 DBM Software Backup

The steps to follow are: Stop the Database operation to avoid inconsistence about data. (Stop the application). Execute the following commands to create the Backup files:
# # # # cd /var/lib tar -cvf DBM.indiax.pgsql.tar pgsql cd /local/india tar -cvf DBM.indiax.tar adap
Once these 2 steps are accomplished, all the application of the DBM_MTO subsystem will be kept in two files.
2.7.4 DBM installation 2.7.4.1 Postgres user configuration


/etc/group
include the path
additional of the
includes
INDRA application always uses /usr/bin/ksh shell. Table 2-9: DBM User configuration parameters
Line that user must add to the /etc/passwd file to configure the user for DBM component.
postgres:x:26:26:/var/lib/pgsql:/bin/bash
Page A-60
DOCUMENT N: 0029200000000MA07
#vi /etc/passwd

#pwconv #passwd postgres New Password: postgres Re-enter new Password: postgres passwd: password successfully changed for postgres
2.7.4.2 Postgres INITIAL configuration

When PostgreSQL is first installed (only when there is any other database created), its necessary to initialize the database cluster with the following commands:
# # # # su postgres /usr/bin/initdb -D /var/lib/pgsql/data --lc-collate=C --lc-ctype=C /usr/bin/postmaster -D /var/lib/pgsql/data >/var/lib/pgsql/logfile 2>&1 & /usr/bin/createdb template
2.7.4.3 DBM Software installation

Copy the backup of the application in /local folder (a previous backup is necessary):
# cp p DBM.indiax.tar.gz /local
Extract the application in the computer:

# cd /local # tar zxvf DBM.indiax.tar.gz
Copy the backup of the PostgreSQL in /var/lib folder (if there is a backup):
# cp p DBM.indiax.pgsql.tar.gz /var/lib
Extract the PostgreSQL backup in the computer:

# cd /var/lib # tar zxvf DBM.indiax.pgsql.tar.gz
The application will be installed. To startup the database graphic tool ( DBM ) we will do:
# su postgres (delete /var/lib/pgsql/data/postmaster.pid if exist) #./pqsql_start #cd /local/india/adap/exec/tcl_tk/ #export DISPLAY=hostname:0.0 (computer name where we want to use the tool) #./dbsman.tcl
Page A-61
DOCUMENT N: 0029200000000MA07
2.8
RDCU
The processor centralizes the radar data reception from the radar antennas. It can work in Main mode or in Alternate Mode (By-Pass) if the other one fails. This component is designed in redundant configuration in the radar line reception, so it is easy to change the operative or reserve line manually or automatically.
2.8.1 Files layout

Each of them runs in its own computer, but both of them have the same folder tree. The following scheme shows the set of folders where critical file system are located.
/local/India/rdcu/exec /dir_exec /grabacion /cinta
Figure 2-8: RDCU Files Layout. The most relevant files are: Folder /local/india/rdcu/exec. FILE
.openwin-init .profile .xinitrc
DESCRIPTION UNIX file with Windows parameters. UNIX file containing specifications for starting up the position. UNIX file containing specifications for starting up the position. File where is stored all communication channel as reception as transmission. This files defines network communications between the type of processes that configure the components This file contains all the parameters concerning the internal configurations of application. This file establish which and order it must start-up the different processes of application This file contains connection specifications for LAN radars (only when radars connected by LAN).
COM_CANALES.CFG
CONFIG_COM
internal_configuration.cfg
task_configuration.cfg
lan_configuration.cfg
Page A-62
DOCUMENT N: 0029200000000MA07
FILE
FILE_RDCU_RADARS.CFG LC_TIME
DESCRIPTION This file contains all the parameters concerning each radar configuration. Time format file. RDCU process. This process receives information from gestors and reception tasks and generates message packs of the same category. It is a link to the
./dir_exec/m_rdcu_empaquetador.xx.xx
m_rdcu_empaquetador
file RDCU process. This process generates all the periodic messages that are sent from the RDCU. It is a link to the
./dir_exec/m_rdcu_envio_mens_periodico .xx.xx file
m_rdcu_envio_mens_periodico
m_rdcu_envio_mens_peticion
RDCU process. This process generates external requested messages. It is a link to the
./dir_exec/m_rdcu_envio_mens_peticion.x x.xx file
m_rdcu_gest_XXXX
RDCU process. This process converts XXXX format into Asterix format, which is the internal format of the system. It is a link to the ./dir_exec/m_rdcu_gest_XXXX.xx.xx file (where XXXX is the name of the radar format) RDCU process. Demon process that manages PCI-334A card lines. It is a link to the ./dir_exec/rdrd file RDCU process. This process receives external system messages. It is a link to the ./dir_exec/ m_rdcu_rx_lan.xx.xx. RDCU process. This process starts up the other processes and it is in charge of starts-up again the processes if they fail. It is a link to the ./dir_exec/m_rdcu_supervisor.xx.xx file RDCU process. This process manages tape units if it exists. It is a link to the ./dir_exec/m_rdcu_tcinta.xx.xx file
m_rdcu_rdrd_x
m_rdcu_rx_lan
m_rdcu_supervisor
m_rdcu_tcinta
Page A-63
DOCUMENT N: 0029200000000MA07
FILE
DESCRIPTION RDCU process. This receiver process is in charge of the connection of PCI-334A card through demons. It is a link to the ./dir_exec/m_rdcu_tserie.xx.xx file RDCU process. This process sends processed information to the SDP system. There is one process by radar. Any of them is a link to the
./dir_exec/m_rdcu_tx_asterix.xx.xx
m_rdcu_tserie
m_rdcu_tx_asterix_x
file RDCU process. This process sends all the generated messages from the RDCU to the other systems except radar information. It is a link to the ./dir_exec/m_rdcu_tx_lan.xx.xx file RDCU process. This process receives the LAN radar information. It is a link to the ./dir_exec/m_rdcu_vigilancia.xx.xx file RDCU process. This process calculates the number of targets per turn. That is radar statistics. It kills every process of the RDCU This process memory. frees the shared
m_rdcu_tx_lan
m_rdcu_vigilancia_rx
m_rdcu_vueltas_antena kill.rdcu killapplication_rdcu startup.rdcu *old *out
It starts up the main process Temporal output files Temporal output files
The application will be automatically loaded as user india with this file unless this already was loaded. Folder /local/india/rdcu/exec/dir_exec: This folder stores all the versioned executables that will be call through the links from /local/india/rdcu/exec or from the playback folder. FILE DESCRIPTION
m_rdcu_empaquetador.xx.xx m_rdcu_envio_mens_periodico.xx.xx m_rdcu_envio_mens_peticion.xx.xx
File linked for of application. File linked for of application. File linked for of application.
operation operation operation
Page A-64
DOCUMENT N: 0029200000000MA07
FILE
m_rdcu_gest_XXXX.xx.xx m_rdcu_rx_lan.xx.xx m_rdcu_supervisor.xx.xx m_rdcu_tcinta.xx.xx m_rdcu_tserie.xx.xx m_rdcu_tx_asterix.xx.xx m_rdcu_tx_lan.xx.xx m_rdcu_vigilancia_rx.xx.xx m_rdcu_vueltas_antena.xx.xx m_rdcu_rdrd.xx.xx
DESCRIPTION File linked for of application. File linked for of application. File linked for of application. File linked for of application File linked for of application File linked for of application. File linked for of application. File linked for of application. File linked for of application. File linked for of application. operation operation operation operation operation operation operation operation operation operation
Folder /local/india/rdcu/exec/grabacion: This folder stores radar data files recorded in the last 24 hours. Folder /local/india/rdcu/exec/grabacion/cinta: This folder stores the radar data files pending of being sent to the tape (if system has capability to record data in tapes)
2.8.2 RDCU 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.
[root@<HOSTNAME>7 /root]# ps -ef |more UID PID PPID C STIME TTY daemon 476 1 0 Sep24 ? root 490 1 0 Sep24 ? root 508 1 0 Sep24 ? root 522 1 0 Sep24 ? root 559 1 0 Sep24 ? xfs 608 1 0 Sep24 ? root 26776 1 0 Oct15 ? TIME 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 00:00:00 CMD /usr/sbin/atd crond inetd [lpd] gpm -t ps/2 xfs -droppriv -daemon -port -1
00:00:00 ./m_rdcu_supervisor
Page A-65
DOCUMENT N: 0029200000000MA07
root root root root root root root root root root root
26778 26776 26779 26776 26780 26776 26781 26776 26782 26776 26783 26776 26784 26776 26785 26776 26786 26776 26787 26776 26788 26776
0 Oct15 ? 0 Oct15 ? 0 Oct15 ? 0 Oct15 ? 0 Oct15 ? 0 Oct15 ? 0 Oct15 ? 0 Oct15 ? 0 Oct15 ? 0 Oct15 ? 0 Oct15 ?
00:00:09 m_rdcu_tserie_rx 00:00:00 m_rdcu_gest_dde 00:00:00 m_rdcu_tx_lan 00:00:00 m_rdcu_rx_lan 00:00:00 m_rdcu_vueltas_antena 00:00:00 m_rdcu_empaquetador 00:00:00 m_rdcu_envio_mens_periodico 00:00:00 m_rdcu_envio_mens_peticion 00:00:00 m_rdcu_tx_asterix_1 00:00:00 m_rdcu_tx_asterix_2 00:00:00 m_rdcu_tx_asterix_3
2.8.3 RDCU installation 2.8.3.1 User configuration


/etc/group
include the path
additional of the
includes
INDRA application always uses /usr/bin/ksh shell. Table 2-10: RDCU User configuration parameters
Line that user must add to the /etc/passwd file to configure the user for RDCU1 and RDCU2 components.
DOCUMENT N: 0029200000000MA07
user:x:0:1:User <HOSTNAME>:/local/india/rdcu/exec:/usr/bin/ksh
#vi /etc/passwd

#pwconv #passwd <user> New Password: < password> Re-enter new Password: <password> passwd: password successfully changed for <user>

Alternatively, create a copy of the application from other RDCU1 or RDCU2:

#rsh hostname cd /local # tar -cvf RDCUx.indiax.tar india
Where x is the RDCU number and to the computer where the application has been created.
# gzip -9 -v RDCUx.indiax.tar (It will compress the file to RDCUx.indiax.tar.gz)
# rcp RDCUx.indiax.tar.gz <host_name>:/local
#exit

# cd /local # gunzip RDCUx.indiax.tar.gz # tar -xvf RDCUx.indiax.tar

The RDCU 1, 2 execution folder will be /local/india/rdcu/exec. In the /local/india/rdcu/exec/startup.rdcu NODO_COM=rdcu1 to NODO_COM=rdcu2.
file,
change
the
parameters
in
line
Page A-67
DOCUMENT N: 0029200000000MA07
NODO_COM=(rdcu1, rdcu2)
If RDCU has PCI334 cards installed for radar serial lines treatment, the starting script is the following: File /local/india/rdcu/exec/startup.rdcu:
#!/usr/bin/ksh # /opt/pti/RP334SO/bin/commload /opt/pti/RP334SO/bin/commload /opt/pti/RP334SO/bin/commload /opt/pti/RP334SO/bin/commload ./kill.rdcu . ./.profile NODO_COM=uast2 export NODO_COM ./m_rdcu_supervisor &
/opt/pti/RP334SO/Cmdfile.rdr_pci334.0 /opt/pti/RP334SO/Cmdfile.rdr_pci334.1 /opt/pti/RP334SO/Cmdfile.rdr_pci334.2 /opt/pti/RP334SO/Cmdfile.rdr_pci334.3
If RDCU don't use PCI334 cards and the radar serial lines treatment is MPS1000, the used script is the following:
#!/bin/ksh # ulimit -q unlimited ulimit -c unlimited ./kill.rdcu . ./.profile NODO_COM=uast2 export NODO_COM ./m_rdcu_supervisor &
If we want to startup manually the RDCU as Replay Mode

#cat startup.rdcu
# /opt/pti/RP334SO/bin/commload /opt/pti/RP334SO/bin/commload /opt/pti/RP334SO/bin/commload /opt/pti/RP334SO/bin/commload ./kill.rdcu . ./.profile
/opt/pti/RP334SO/Cmdfile.rdr_pci334.0 /opt/pti/RP334SO/Cmdfile.rdr_pci334.1 /opt/pti/RP334SO/Cmdfile.rdr_pci334.2 /opt/pti/RP334SO/Cmdfile.rdr_pci334.3
NODO_COM=uast2 ( or uast1 depends of the RDCU) export NODO_COM ./m_rdcu_supervisor -d -r
Page A-68
DOCUMENT N: 0029200000000MA07
If we want to shutdown manually the RDCU, we can use this macro. File /local/india/rdcu/exec/kill.rdcu:
for PID in `ps do kill -9 $PID done for PID in `ps do kill -9 $PID done -ef | grep m_rdcu_supervisor | cut -c9-14` > /dev/null 2>&1 -ef | grep m_rdcu | cut -c9-14` > /dev/null 2>&1
./killapplication_rdcu SUN -rmipcs
The /local/india/rdcu/exec/configuracion_interna.cfg file has owned characteristics of the Software and RDCU cards. File /local/india/rdcu/exec/configuracion_interna.cfg:
// Compressor Number. Logic Value NU_UDDE 1 // Asterix messages packing time TIME_AST 200 // Maximum number of white spaces allowed BLANC_AST 5 // UADR Mode MODO_FUNC NORMAL // Delay use CALC_DEM NO // Tape use TAPE NO
The most relevant parameters belonging to this file are:

NU_UDDE: It is the number of the RDCU (logic value). TIEMPO_ASTERIX: It is the ASTERIX packaging time (in milliseconds). BLANCOS_ASTERIX: It is the maximum number of plots that can be packaged together. MODO_FUNC: Working mode of the RDCU. CALC_DEM: It indicates if delay is to be calculated. TAPE: It indicates if the tape is to be used.
The /local/india/rdcu/exec/FILE_RDCU_RADARS.CFG archive is a file of configuration, which establishes the data type the radar receives, the physicals characteristics, and its configuration.
Page A-69
DOCUMENT N: 0029200000000MA07
File /local/india/rdcu/exec/FILE_RDCU_RADARS.CFG:
#Fichero para la unidad UADR# *versDatAdap: 1_103_1_487_0001 *sacP1: 50 uast: 1 - uast: 2 uast: 2 - uast: 1 *entRad.numRad: 6 *entRad.rad1.num: 1 *entRad.rad1.tipo: ASTERIX *entRad.rad1.tipoAst: P01 *entRad.rad1.sic: 1 *entRad.rad1.uadr1: 1 *entRad.rad1.c1_uadr1: 1 *entRad.rad1.c2_uadr1: *entRad.rad1.uadr2: 2 *entRad.rad1.c2_uadr1: *entRad.rad1.c2_uadr2: 1 *entRad.rad1.name: LAH *entRad.rad1.per_ant: 8000 *entRad.rad1.trat_plots: s *entRad.rad1.trat_pist: s *entRad.rad1.calc_dem: n *entRad.rad1.ut_sac_sic: n *entRad.rad2.num: 2 *entRad.rad2.tipo: ASTERIX *entRad.rad2.tipoAst: P01 *entRad.rad2.sic: 2 *entRad.rad2.uadr1: 1 *entRad.rad2.c1_uadr1: 2 *entRad.rad2.c2_uadr1: *entRad.rad2.uadr2: 2 *entRad.rad2.c2_uadr1: *entRad.rad2.c2_uadr2: 2 *entRad.rad2.name: ISL *entRad.rad2.per_ant: 8000 *entRad.rad2.trat_plots: s *entRad.rad2.trat_pist: n *entRad.rad2.calc_dem: n *entRad.rad2.ut_sac_sic: s *entRad.rad3.num: 3 *entRad.rad3.tipo: ASTERIX *entRad.rad3.tipoAst: P01 *entRad.rad3.sic: 3 *entRad.rad3.uadr1: 1 *entRad.rad3.c1_uadr1: 3 *entRad.rad3.c2_uadr1: *entRad.rad3.uadr2: 2 *entRad.rad3.c2_uadr1: *entRad.rad3.c2_uadr2: 3 *entRad.rad3.name: KAR *entRad.rad3.per_ant: 8000 *entRad.rad3.trat_plots: s
Page A-70
DOCUMENT N: 0029200000000MA07
*entRad.rad3.trat_pist: n *entRad.rad3.calc_dem: n *entRad.rad3.ut_sac_sic: s *entRad.rad4.num: 4 *entRad.rad4.tipo: ASTERIX *entRad.rad4.tipoAst: P01 *entRad.rad4.sic: 4 *entRad.rad4.uadr1: 1 *entRad.rad4.c1_uadr1: 4 *entRad.rad4.c2_uadr1: *entRad.rad4.uadr2: 2 *entRad.rad4.c2_uadr1: *entRad.rad4.c2_uadr2: 4 *entRad.rad4.name: PSN *entRad.rad4.per_ant: 8000 *entRad.rad4.trat_plots: s *entRad.rad4.trat_pist: n *entRad.rad4.calc_dem: n *entRad.rad4.ut_sac_sic: s *entRad.rad5.num: 5 *entRad.rad5.tipo: ASTERIX *entRad.rad5.tipoAst: P01 *entRad.rad5.sic: 5 *entRad.rad5.uadr1: 1 *entRad.rad5.c1_uadr1: 5 *entRad.rad5.c2_uadr1: *entRad.rad5.uadr2: 2 *entRad.rad5.c2_uadr1: *entRad.rad5.c2_uadr2: 5 *entRad.rad5.name: LPK *entRad.rad5.per_ant: 8000 *entRad.rad5.trat_plots: s *entRad.rad5.trat_pist: n *entRad.rad5.calc_dem: n *entRad.rad5.ut_sac_sic: s *entRad.rad6.num: 6 *entRad.rad6.tipo: ASTERIX *entRad.rad6.tipoAst: P01 *entRad.rad6.sic: 6 *entRad.rad6.uadr1: 1 *entRad.rad6.c1_uadr1: 6 *entRad.rad6.c2_uadr1: *entRad.rad6.uadr2: 2 *entRad.rad6.c2_uadr1: *entRad.rad6.c2_uadr2: 6 *entRad.rad6.name: ROJ *entRad.rad6.per_ant: 8000 *entRad.rad6.trat_plots: s *entRad.rad6.trat_pist: n *entRad.rad6.calc_dem: n *entRad.rad6.ut_sac_sic: s
PARAMETER
DESCRIPTION
Page A-71
DOCUMENT N: 0029200000000MA07
PARAMETER
sacAl rdcu: 1 rdcu: 2 entRadar.numRad entRadar.radx.num entRadar.radx.tipo
DESCRIPTION This parameter shows the sac of the country which the radar belongs to. Pair of RDCUs (operative - reserve). Number of Radars. Radar number. Data format we receive from the radar. There is only one type of radar, ASTERIX. Asterix data type. Types are Indra Asterix and Alenia Asterix.
entRadar.radx.tipoAst
Indra Asterix: There are 10 possible countries from P01 to P10, successively. Alenia Asterix: The value will be equal to NIAX, where X is the number corresponding to Alenia type, which is defined on the top of the file.
enRadar.radx.sic entRadar.radx.uadr1 entRadar.radx.c1_uadr1 entRadar.radx.c2_uadr1 entRadar.radx.uadr2 entRadar.radx.c1_uadr2 entRadar.radx.c2_uadr2 entRadar.radx.name entRadar.radx.per_ant
Sic of radar. Number of the first RDCU that is connected to the x radar. Input data channel of the first RDCU. Always white spaces. Number of the second RDCU that is connected to the x radar. Always white spaces. Input data channel of the second RDCU. Acronym of the radar name. Rotational period (in milliseconds). There are two options: s x, the RDCU sends them to the system. n x, the system. RDCU does not send them to the
entRadar.radx.trat_plots
There are two options.

entRadar.radx.trat_pist
s x, the RDCU sends them to the system. n x, the system. RDCU does not send them to
adar
the
Page A-72
DOCUMENT N: 0029200000000MA07
PARAMETER s
entRadar.radx.calc_dem
DESCRIPTION There are two options:

configuracion_interna.cfg
file,
then
the
calculated delay is sent. n There are two options. s sac and sic of this message are compared with the sac and sic of radar configuration. entRadar.radx.ut_sac_sic If they equals to each other the message will be interpreted, otherwise the message will be rejected. n with the configured sac and sic. For RDCU starts-up, it is required to modify the host. The host must be always the same in the all the system, excepting RDCU positions; so there is a generic host for the system and an specific host for each RDCU position. The difference is based in: File /etc/hosts in RDCU1
# india LAN1 10.160.77.1 <HOSTNAME>1 10.160.77.2 <HOSTNAME>2 10.160.77.3 <HOSTNAME>3 10.160.77.4 <HOSTNAME>4 10.160.77.5 <HOSTNAME>5 uast1 radar1 radar2 radar3 radar4 radar5 radar6 radar7 radar8 radar9 radar10 radar11 radar12 radar13 radar14 radar15 radar16 10.160.77.6 <HOSTNAME>6 uast2 10.160.77.7 <HOSTNAME>7 10.160.77.8 <HOSTNAME>8 10.160.77.9 <HOSTNAME>9 10.160.77.10 <HOSTNAME>10 10.160.77.11 <HOSTNAME>11 10.160.77.12 <HOSTNAME>12 10.160.77.13 <HOSTNAME>13 10.160.77.14 <HOSTNAME>14 10.160.77.15 <HOSTNAME>15 10.160.77.16 <HOSTNAME>16 10.160.77.17 <HOSTNAME>17 10.160.77.18 <HOSTNAME>18 10.160.77.19 <HOSTNAME>19 10.160.77.20 <HOSTNAME>20 10.160.77.21 <HOSTNAME>21 10.160.77.22 <HOSTNAME>22 # india LAN2 10.161.77.1 10.161.77.2 <HOSTNAME>1-2 <HOSTNAME>2-2
Page A-73
DOCUMENT N: 0029200000000MA07
10.161.77.3 10.161.77.4 10.161.77.5 10.161.77.6 10.161.77.7 10.161.77.8 10.161.77.9 10.161.77.10 10.161.77.11 10.161.77.12 10.161.77.13 10.161.77.14 10.161.77.15 10.161.77.16 10.161.77.17 10.161.77.18 10.161.77.19 10.161.77.20 10.161.77.21 10.161.77.22 # india LAN3 10.162.77.1 10.162.77.2 10.162.77.3 10.162.77.4 10.162.77.5 10.162.77.6 10.162.77.7 10.162.77.8 10.162.77.9 10.162.77.10 10.162.77.11 10.162.77.12 10.162.77.13 10.162.77.14 10.162.77.15 10.162.77.16 10.162.77.17 10.162.77.18 10.162.77.19 10.162.77.20 10.162.77.21 10.161.77.22 # NTP india 10.160.77.250 10.161.77.250 10.162.77.250 # PRINTERS 10.160.77.101 10.160.77.102 # SWITCHES
<HOSTNAME>3-2 <HOSTNAME>4-2 <HOSTNAME>5-2 <HOSTNAME>6-2 <HOSTNAME>7-2 <HOSTNAME>8-2 <HOSTNAME>9-2 <HOSTNAME>10-2 <HOSTNAME>11-2 <HOSTNAME>12-2 <HOSTNAME>13-2 <HOSTNAME>14-2 <HOSTNAME>15-2 <HOSTNAME>16-2 <HOSTNAME>17-2 <HOSTNAME>18-2 <HOSTNAME>19-2 <HOSTNAME>20-2 <HOSTNAME>21-2 <HOSTNAME>22-2
<HOSTNAME>1-3 <HOSTNAME>2-3 <HOSTNAME>3-3 <HOSTNAME>4-3 <HOSTNAME>5-3 <HOSTNAME>6-3 <HOSTNAME>7-3 <HOSTNAME>8-3 <HOSTNAME>9-3 <HOSTNAME>10-3 <HOSTNAME>11-3 <HOSTNAME>12-3 <HOSTNAME>13-3 <HOSTNAME>14-3 <HOSTNAME>15-3 <HOSTNAME>16-3 <HOSTNAME>17-3 <HOSTNAME>18-3 <HOSTNAME>19-3 <HOSTNAME>20-3 <HOSTNAME>21-3 <HOSTNAME>22-3
ntp_server1 ntp_server2 ntp_server3
lp1 lp2
Page A-74
DOCUMENT N: 0029200000000MA07
10.160.77.100 10.161.77.100 # INDIA SIMULATION 10.160.77.31 10.160.77.32 10.160.77.33 10.160.77.34 10.160.77.35 10.160.77.36 10.160.77.37 10.160.77.38
switch1_<HOSTNAME> switch2_<HOSTNAME>
<HOSTNAME>31 <HOSTNAME>32 <HOSTNAME>33 <HOSTNAME>34 <HOSTNAME>35 <HOSTNAME>36 <HOSTNAME>37 <HOSTNAME>38
# SWITCH SIMULATION 10.160.77.150 switch_sim_<HOSTNAME>
File /etc/hosts in RDCU2
#--# Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost
# india LAN1 10.160.77.1 <HOSTNAME>1 10.160.77.2 <HOSTNAME>2 10.160.77.3 <HOSTNAME>3 10.160.77.4 <HOSTNAME>4 10.160.77.5 <HOSTNAME>5 uast1 10.160.77.6 <HOSTNAME>6 uast2 radar1 radar2 radar3 radar4 radar5 radar6 radar7 radar8 radar9 radar10 radar11 radar12 radar13 radar14 radar15 radar16 10.160.77.7 <HOSTNAME>7 10.160.77.8 <HOSTNAME>8 10.160.77.9 <HOSTNAME>9 10.160.77.10 <HOSTNAME>10 10.160.77.11 <HOSTNAME>11 10.160.77.12 <HOSTNAME>12 10.160.77.13 <HOSTNAME>13 10.160.77.14 <HOSTNAME>14 10.160.77.15 <HOSTNAME>15 10.160.77.16 <HOSTNAME>16 10.160.77.17 <HOSTNAME>17 10.160.77.18 <HOSTNAME>18 10.160.77.19 <HOSTNAME>19 10.160.77.20 <HOSTNAME>20 10.160.77.21 <HOSTNAME>21 10.160.77.22 <HOSTNAME>22 10.160.77.23 <HOSTNAME>23 10.160.77.24 <HOSTNAME>24
DOCUMENT N: 0029200000000MA07
10.160.77.25 10.160.77.26 10.160.77.27 10.160.77.28 10.160.77.29 10.160.77.30 # india LAN2 10.161.77.1 10.161.77.2 10.161.77.3 10.161.77.4 10.161.77.5 10.161.77.6 10.161.77.7 10.161.77.8 10.161.77.9 10.161.77.10 10.161.77.11 10.161.77.12 10.161.77.13 10.161.77.14 10.161.77.15 10.161.77.16 10.161.77.17 10.161.77.18 10.161.77.19 10.161.77.20 10.161.77.21 10.161.77.22 10.161.77.23 10.161.77.24 10.161.77.25 10.161.77.26 10.161.77.27 10.161.77.28 10.161.77.29 10.161.77.30 # NTP india 10.160.77.210 10.161.77.210 # PRINTERS 10.160.77.201 10.160.77.202 10.160.77.203 # SWITCHES 10.160.77.100 10.161.77.100
<HOSTNAME>25 <HOSTNAME>26 <HOSTNAME>27 <HOSTNAME>28 <HOSTNAME>29 <HOSTNAME>30
<HOSTNAME>1-2 <HOSTNAME>2-2 <HOSTNAME>3-2 <HOSTNAME>4-2 <HOSTNAME>5-2 <HOSTNAME>6-2 <HOSTNAME>7-2 <HOSTNAME>8-2 <HOSTNAME>9-2 <HOSTNAME>10-2 <HOSTNAME>11-2 <HOSTNAME>12-2 <HOSTNAME>13-2 <HOSTNAME>14-2 <HOSTNAME>15-2 <HOSTNAME>16-2 <HOSTNAME>17-2 <HOSTNAME>18-2 <HOSTNAME>19-2 <HOSTNAME>20-2 <HOSTNAME>21-2 <HOSTNAME>22-2 <HOSTNAME>23-2 <HOSTNAME>24-2 <HOSTNAME>25-2 <HOSTNAME>26-2 <HOSTNAME>27-2 <HOSTNAME>28-2 <HOSTNAME>29-2 <HOSTNAME>30-2
ntp_server1 ntp_server2
lp1 lp2 lp3
# INDIA SIMULATION 10.160.77.31 10.160.77.32

<HOSTNAME>31 <HOSTNAME>32
DOCUMENT N: 0029200000000MA07
10.160.77.33 10.160.77.34 10.160.77.35 10.160.77.36 10.160.77.37 10.160.77.38
<HOSTNAME>33 <HOSTNAME>34 <HOSTNAME>35 <HOSTNAME>36 <HOSTNAME>37 <HOSTNAME>38
# SWITCH SIMULATION 10.160.77.150 switch_sim_<HOSTNAME>
File /etc/hosts in the rest of the system

# Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 localhost.localdomain localhost
# india LAN1 10.160.77.1 10.160.77.2 10.160.77.3 10.160.77.4 10.160.77.5 10.160.77.6 10.160.77.7 10.160.77.8 10.160.77.9 10.160.77.10 10.160.77.11 10.160.77.12 10.160.77.13 10.160.77.14 10.160.77.15 10.160.77.16 10.160.77.17 10.160.77.18 10.160.77.19 10.160.77.20 10.160.77.21 10.160.77.22 10.160.77.23 10.160.77.24 10.160.77.25 10.160.77.26 10.160.77.27 10.160.77.28 10.160.77.29 10.160.77.30 # india LAN2 10.161.77.1 <HOSTNAME>1-2 <HOSTNAME>1 <HOSTNAME>2 <HOSTNAME>3 <HOSTNAME>4 <HOSTNAME>5 <HOSTNAME>6 <HOSTNAME>7 <HOSTNAME>8 <HOSTNAME>9 <HOSTNAME>10 <HOSTNAME>11 <HOSTNAME>12 <HOSTNAME>13 <HOSTNAME>14 <HOSTNAME>15 <HOSTNAME>16 <HOSTNAME>17 <HOSTNAME>18 <HOSTNAME>19 <HOSTNAME>20 <HOSTNAME>21 <HOSTNAME>22 <HOSTNAME>23 <HOSTNAME>24 <HOSTNAME>25 <HOSTNAME>26 <HOSTNAME>27 <HOSTNAME>28 <HOSTNAME>29 <HOSTNAME>30
Page A-77
DOCUMENT N: 0029200000000MA07
10.161.77.2 10.161.77.3 10.161.77.4 10.161.77.5 10.161.77.6 10.161.77.7 10.161.77.8 10.161.77.9 10.161.77.10 10.161.77.11 10.161.77.12 10.161.77.13 10.161.77.14 10.161.77.15 10.161.77.16 10.161.77.17 10.161.77.18 10.161.77.19 10.161.77.20 10.161.77.21 10.161.77.22 10.161.77.23 10.161.77.24 10.161.77.25 10.161.77.26 10.161.77.27 10.161.77.28 10.161.77.29 10.161.77.30 # NTP india 10.160.77.210 10.161.77.210 # PRINTERS 10.160.77.201 10.160.77.202 10.160.77.203 # SWITCHES 10.160.77.100 10.161.77.100
<HOSTNAME>2-2 <HOSTNAME>3-2 <HOSTNAME>4-2 <HOSTNAME>5-2 <HOSTNAME>6-2 <HOSTNAME>7-2 <HOSTNAME>8-2 <HOSTNAME>9-2 <HOSTNAME>10-2 <HOSTNAME>11-2 <HOSTNAME>12-2 <HOSTNAME>13-2 <HOSTNAME>14-2 <HOSTNAME>15-2 <HOSTNAME>16-2 <HOSTNAME>17-2 <HOSTNAME>18-2 <HOSTNAME>19-2 <HOSTNAME>20-2 <HOSTNAME>21-2 <HOSTNAME>22-2 <HOSTNAME>23-2 <HOSTNAME>24-2 <HOSTNAME>25-2 <HOSTNAME>26-2 <HOSTNAME>27-2 <HOSTNAME>28-2 <HOSTNAME>29-2 <HOSTNAME>30-2
ntp_server1 ntp_server2
lp1 lp2 lp3
# india SIMULATION 10.160.77.31 10.160.77.32 10.160.77.33 10.160.77.34 10.160.77.35 10.160.77.36 10.160.77.37 10.160.77.38 <HOSTNAME>31 <HOSTNAME>32 <HOSTNAME>33 <HOSTNAME>34 <HOSTNAME>35 <HOSTNAME>36 <HOSTNAME>37 <HOSTNAME>38
# SWITCH SIMULATION 10.160.77.150

switch_sim_<HOSTNAME>
DOCUMENT N: 0029200000000MA07
If drivers or radar lines controller are not installed, install them. Depending of used hardware, see AUXILIARY DEVICES chapter.

# cd /local # tar -cvf RDCUx.indiax.tar india
Where x is the RDCU number and the computer hostname where the application has been created.
# gzip -9 -v RDCUx.indiax.tar (It will compress the file to RDCUx.indiax.tar.gz) # rcp RDCUx.indiax.tar.gz <host_name>:/../FOLDER_BACKUP
Where host_name is the computer where the application is going to be installed or saved.
#exit
2.8.5 Adding new radars

There are two different options to physically connect a radar to the system. These two options are RS-232 connection (serial port) or LAN connection (Local Area Network connection).
2.8.5.1 RS-232
The steps to add a new Radar that is going to be connected via RS-232 interface to the RDCUs is described at the DBM manual, in the section Radars of the SDP Adaptation Data section. The main idea of this procedure is just add a radar at the DBM Application (setting all the parameters of the radar and the physical port that connects the radar with the RDCU), generate all the data, load data into the system and restart the system. It is not needed any other action.
2.8.5.2 LAN
The procedure to add a new radar connected by LAN to the system is the same of the connection by serial port but choosing port number 0 for that radar in the Radar Table of the SDP Adaptation Data belonging to the DBM component (Port 0 means radar connection by LAN. Otherwise means the number of the physical -not logical- port at the RDCU where the radar is connected). Moreover, there is a file in /local/india/rdcu/exec/ called configuracion_vigilancia.cfg that the user must configure property in the RDCU1 and RDCU2 components: /local/india/rdcu/exec/configuracion_vigilancia.cfg file:
HOSTNAME>3$ more configuracion_vigilancia.cfg
// File used for assignment of net to each radar // RADAR 1 MULTICAST_GROUP 224.0.0.1 INTERFACE 192.168.72.3 DEVICE eth1 PORT 4001
Page A-79
DOCUMENT N: 0029200000000MA07
Parameters concerning this file: PARAMETER

RADAR
DESCRIPTION
Number of the radar (given by DBM). User can check this number in the FILE_RDCU_RADAR.CFG file located in the folder /local/india/rdcu/exec/ (do it after the load of operational adaptation data) Multicast group. People in charge of installation must give this address. IP address of the RDCU. People installation must give this address. Device of the component. People installation must give this address. in in charge charge of of
MULTICAST_GROUP INTERFACE DEVICE
PORT
Logical port (UDP) where the radar sends the data. People in charge of installation must give this address. .
It
is
necessary
to
add
a new
line
per
new
LAN
connected
radar
to
the
file
configuracion_vigilancia.cfg. It is possible that more than one radar could be connected
through the same multicast group and the same port to the same RDCU, because this components can differentiate each radar checking the SAC (Source Area Code) and SIC (Source Identifier Code) from each one. Lines that the user must check in the /local/india/rdcu/exec/FILE_RDCU_RADAR.CFG file to know the number of the radar (parameter RADAR):
*entRad.radX.num: X *entRad.radX.name: RAD_X
Where X is the number of the radar, which name is RAD_X. This is a scheme of the LAN connection of a radar:
LAN 192.168.72.100
MULTICAST: 224.0.0.1 PORT (UDP): 4001 RDCU

eth1: IP 192.168.72.3
Figure 2-9: Radar LAN Connection

DOCUMENT N: 0029200000000MA07
2.8.5.3 LAN RADAR LANZA

The procedure to add new radar connected by LAN to the system is the same of the connection by serial port but choosing port number 0 for that radar in the Radar Table of the SDP Adaptation Data belonging to the DBM component (Port 0 means radar connection by LAN. Otherwise means the number of the physical -not logical- port at the RDCU where the radar is connected). Moreover, there is a file in /local/india/rdcu/exec/ called configuracion_vigilancia_lanza.cfg that the user must configure property in the RDCU1 and RDCU2 components: /local/india/rdcu/exec/configuracion_vigilancia_lanza.cfg file:
Supply and Installation of the Equipment for7$ more
configuracion_vigilancia_lanza.cfg
// File used for assignment of net to each radar // RADAR MULTICAST_GROUP INTERFACE 1 224.0.0.1 192.168.72.3
DEVICE eth1
PORT 4001
Parameters concerning this file: PARAMETER

RADAR
DESCRIPTION
Number of the radar (given by DBM). User can check this number in the FILE_RDCU_RADAR.CFG file located in the folder /local/india/rdcu/exec/ (do it after the load of operational adaptation data) Multicast group. People in charge of installation must give this address. IP address of the RDCU. People in charge of installation must give this address. Device of the component. People in charge of installation must give this address. Logical port (UDP) where the radar sends the data. People in charge of installation must give this address.
MULTICAST_GROU P INTERFACE DEVICE PORT
A new line in file configuracion_vigilancia_lanza.cfg has to be added per new LAN connected radar. More than one radar could be connected through the same multicast group and the same port to the same RDCU, because this components can differentiate each radar checking the SAC (Source Area Code) and SIC (Source Identifier Code) from each one. Lines that the user must check in the /local/india/rdcu/exec/FILE_RDCU_RADAR.CFG file to know the number of the radar (parameter RADAR):
*entRad.radX.num: X *entRad.radX.name: RAD_X
Where X is the number of the radar, which name is RAD_X.
Page A-81
DOCUMENT N: 0029200000000MA07
2.9
RDCU Transmision (N/A)
2.9.1 Files layout

The following scheme shows the set of folders where critical file system are located.
/local/india/rdfd/exec /dir_exec /grabacion /cinta
Figure 2-10: RDFD Files Layout. The most relevant files are: Folder /local/india/rdfd/exec FILE
DESCRIPTION UNIX file with Windows parameters. UNIX file containing specifications starting up the position. UNIX file containing specifications starting up the position. for for
CONFIG_COM
This files defines network communications between the type of processes that configure the components RDCU process. It is a link to the ./dir_exec/m_rdfd_cat62_linux.xx.xx file. RDFD process. It is a link to the ./dir_exec/m_rdfd_graphic_ascii_linux.xx.xx file. It kills every process of the RDFD This process frees the shared memory. It starts up the main process Temporal output files Temporal output files
m_rdfd_cat62
m_rdfd_graphic_ascii kill.rdfd killapplication_rdfd_cat62 startup.rdfd *old *out
Page A-82
DOCUMENT N: 0029200000000MA07
The application will be automatically loaded as user india with this file unless this already was loaded. Folder /local/india/rdfd/exec/dir_exec: This folder stores all the versioned executables that will be call through the links from /local/india/rdfd/exec. FILE DESCRIPTION
m_rdfd_cat62_linux.xx.xx m_rdfd_graphic_ascii_linux.xx.xx
File linked for of application. File linked for of application.
operation operation
Table 2-11: RDFD /local/india/rdfd/exec/dir_exec folder relevant files.
2.9.2 RDFD 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.
[root@<HOSTNAME>7 /root]# ps -ef | more
UID daemon root root root root xfs root
PID 476 490 508 522 559 608 6897
PPID 1 1 1 1 1 1 6877
C STIME TTY 0 Sep24 ? 0 Sep24 ? 0 Sep24 ? 0 Sep24 ? 0 Sep24 ? 0 Sep24 ? 0 Sep24 ?
TIME CMD 00:00:00 /usr/sbin/atd 00:00:00 crond 00:00:00 inetd 00:00:00 [lpd] 00:00:00 gpm -t ps/2 00:00:00 xfs -droppriv -daemon -port -1 00:00:01 ./m_rdfd_cat62
2.9.3 RDFD installation 2.9.3.1 User configuration

Page A-83
DOCUMENT N: 0029200000000MA07
It is a user name in the system. It indicates that the user has a password (the user has an entry in the /etc/shadow file). It is the user identifier number. It is file). group identifier is used number to (See /etc/group additional of the
include the path
includes
INDRA application always uses /usr/bin/ksh shell. Table 2-12: RDFD User configuration parameters
Line that user must add to the /etc/passwd file to configure the user for RDFD component
user:x:0:1:User <HOSTNAME>:/local/india/rdfd/exec:/usr/bin/ksh
#vi /etc/passwd

#pwconv #passwd <user> New Password: < password> Re-enter new Password: <password> passwd: password successfully changed for <user>

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

#rsh hostname #cd /local # tar -cvf RDFDx.indiax.tar india # gzip -9 -v RDFDx.indiax.tar (It will compress the file a RDFDx.indiax.tar.gz)
Page A-84
DOCUMENT N: 0029200000000MA07
# rcp RDFDx.indiax.tar.gz <host_name>:/local
#exit

# cd /local # gunzip RDFDx.indiax.tar.gz # tar -xvf RDFDx.indiax.tar
The application will be installed.

Modification and distribution of CONFIG_COM if it is necessary.

# cd /local # tar -cvf RDFDx.indiax.tar india
Where x is the RDCU number and the computer hostname where the application has been created.
# gzip -9 -v RDFDx.indiax.tar (It will compress the file to RDFDx.indiax.tar.gz) # rcp RDFDx.indiax.tar.gz <host_name>:/../FOLDER_BACKUP
Where host_name is the computer where the application is going to be installed or saved.
#exit
2.10 SFN
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 SFN 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.
Page A-85
DOCUMENT N: 0029200000000MA07
2.10.1 Files layout

The following diagram shows the location of the folders needed by the system; folder /local/india/sfn/exec:
/local/india /directorios2/ sdirectorios1/ fn/exec
/sfn/exec/dir_exec /sfn/exec/dir_tools /sfn/exec/dir_files /sfn/exec/dir_posix_fds /sfn/exec/dir_shm /sfn/exec/tablas_ads /sfn/exec/grabacion
Figure 2-11: SFN Files Layout. The most relevant files in this folder are: FILE
DESCRIPTION UNIX file with X-Windows parameters. UNIX file containing specifications for starting up the position. UNIX file containing specifications for starting up the position. This file defines the network method applied to the processes component configuration. Text file containing SFN number. This process frees the shared memory. Text file containing recording and playback. Process of the SFN. Process of the SFN. It is a link to a file with the same name that is located in /local/india/sfn/exec/dir_exec. Process of the SFN. It is a link to a file with the same name that is located in /local/india/sfn/exec/dir_exec. useful dates for the communication in charge of
CONFIG_COM fich_config Killapplication_sfn LC_TIME m_sdp_tabla_pc_lost m_sdp_traces
m_sdp_tz
Page A-86
DOCUMENT N: 0029200000000MA07
FILE
m_sfn_conflict
DESCRIPTION Process of the SFN. It is a link to a file with the same name that is located in /local/india/sfn/exec/dir_exec. Process of the SFN. It is a link to a file with the same name that is located in /local/india/sfn/exec/dir_exec. Process of the SFN. It is a link to a file with the same name that is located in /local/india/sfn/exec/dir_tools. Process of the SFN. It is a link to a file with the same name that is located in /local/india/sfn/exec/dir_exec. Process of the SFN. It is a link to a file with the same name that is located in /local/india/sfn/exec/dir_tools. Process of the SFN. It is a link to a file with the same name that is located in /local/india/sfn/exec/dir_exec. Traces tool of the SFN.It is a link to a file with the same name that is located in /local/india/sfn/exec/dir_tools. Process of the SFN. It is a link to a file with the same name that is located in /local/india/sfn/exec/dir_exec. Process of the SFN. It is a link to a file with the same name that is located in /local/india/sfn/exec/dir_exec. Process of the SFN. It is a link to a file with the same name that is located in /local/india/sfn/exec/dir_exec. Link with startup.sfn.ope or startup.sfn.sim files. The link with one of these files depends of the SFN to be started up. Script for cancelling the SFN (off-line). These are files adaptation data. generated from the ( FICH_*)
m_sfn_db_tracks
m_sfn_decode_cat62
m_sfn_flat_esperas
m_sfn_flight_plan
m_sfn_man_tracks
m_sfn_mosaic
m_sfn_presence
m_sfn_sinthetic_tra cks
m_sfn_supervisor
startup.sfn killapplication_sfn tabla_*
Subfolders contents: FOLDER DESCRIPTION This folder contains files that are linked to the processes contained in the /local/india/sfn/exec folder (m_sfn_* files).
/local/india/sfn/exec/dir_exec
Page A-87
DOCUMENT N: 0029200000000MA07
FOLDER
/local/india/sfn/exec/dir_tools
DESCRIPTION This folder contains executable files of the SFN system (player, recorder, and traces). 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. This folder contains descriptor files of POSIX queues. file the
/local/india/sfn/exec/dir_files
/local/india/sfn/exec/dir_posix_fds
/local/india/sfn/exec/dir_shm
This folder contains descriptors of the shared memory tables of the SFN. This folder contains parameters related to the ADS contracts.
/local/india/sfn/exec/tablas_ads
2.10.2 SFN 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$ root 27401 1 0 root 27821 27401 0 root 27822 27401 0 root 27823 27401 0 root 27827 27401 0 root 27828 27401 0 root 27829 27401 0 root 27830 27401 0 root 27832 27401 1 root 27833 27401 0 ps -ef | grep m_ 09:24 ? 00:00:00 09:24 ? 00:00:01 09:24 ? 00:00:00 09:24 ? 00:00:00 09:24 ? 00:00:00 09:24 ? 00:00:00 09:24 ? 00:00:00 09:24 ? 00:00:01 09:24 ? 00:00:35 09:24 ? 00:00:00 ./m_sfn_supervisor m_sfn_conflict 0 m_sfn_mosaic m_sfn_flight_plan m_sfn_flat_esperas m_sfn_sinthetic_tracks m_sfn_man_tracks m_sfn_db_tracks m_sfn_decode_cat62 m_sfn_presence
In status SIMULATION
[root@<HOSTNAME>3 ~]# root 27401 1 root 27821 27401 root 27822 27401 root 27823 27401 root 27827 27401 root 27828 27401 root 27829 27401 root 27830 27401
ps -ef | grep -i m_sfn 0 09:24 ? 00:00:00 ./m_sfn_supervisor S 0 09:24 ? 00:00:01 m_sfn_conflict S 0 0 09:24 ? 00:00:00 m_sfn_mosaic S 0 09:24 ? 00:00:00 m_sfn_flight_plan S 0 09:24 ? 00:00:00 m_sfn_flat_esperas S 0 09:24 ? 00:00:00 m_sfn_sinthetic_tracks S 0 09:24 ? 00:00:00 m_sfn_man_tracks S 0 09:24 ? 00:00:01 m_sfn_db_tracks S
Page A-88
DOCUMENT N: 0029200000000MA07
root root
27832 27401 27833 27401
1 09:24 ? 0 09:24 ?
00:00:35 m_sfn_decode_cat62 S 00:00:00 m_sfn_presence S
2.10.3 SFN installation 2.10.3.1 User configuration

/etc/group
include the path
additional of the
includes
Line that user must add to the /etc/passwd file to configure the user for SFN component.
user:x:0:1:User india:/local/india/sfn/exec:/usr/bin/ksh
#vi /etc/passwd

#pwconv #passwd <user>
Page A-89
DOCUMENT N: 0029200000000MA07
New Password: <password> Re-enter new Password: <password> passwd: password successfully changed for <user>
2.10.3.2
Folders configuration

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

# cd /local # tar -cvf SFNx.indiax.tar india
Where x is the SFN number and the computer hostname where the application has been created.
# gzip -9 -v SFNx.indiax.tar (It will compress the file to SFNx.indiax.tar.gz) # rcp SFNx.indiax.tar.gz <host_name>:/local
#exit

# cd /local # gunzip SFNx.indiax.tar.gz # tar -xvf SFNx.indiax.tar
2.10.3.3
Application configuration
The SFN execution folder is /local/india/sfn/exec. The SFN number (1 o 2) must be indicated in the boot file: Changing the variable: File /local/india/sfn/exec/fich_config
ROLE_SUBSYSTEM: SFN1
In the /local/india/sfn/exec/, there is a link named startup.sfn; which, depending of start-up SFN mode, it must point the one that starts in OPERATIONAL or SIMULATION mode. For OPERATIONAL mode:
<HOSTNAME>3$ ln -fs startup.sfn.ope startup.sfn <HOSTNAME>3$ ls -al st* lrwxrwxrwx 1 root root 15 Mar 31 10:03 startup.sfn -> startup.sfn.ope -rwxr-xr-x 1 root root 469 Feb 11 18:03 startup.sfn.ope -rwxr-xr-x 1 root root 466 Feb 11 18:01 startup.sfn.sim
For SIMULATION mode:

<HOSTNAME>32$ ln -fs startup.sfn.sim startup.sfn
Page A-90
DOCUMENT N: 0029200000000MA07
<HOSTNAME>32$ lrwxrwxrwx 1 -rwxr-xr-x 1 -rwxr-xr-x 1
ls -al st* root root 15 Mar 31 10:11 startup.sfn -> startup.sfn.sim root root 469 Feb 11 18:03 startup.sfn.ope root root 466 Feb 11 18:01 startup.sfn.sim
Note: In simulation mode, only a SFN position is required.
Modification and distribution of CONFIG_COM.

# cd /local # tar -cvf SFNx.indiax.tar india
Where x is the SFN number and the computer hostname where the application has been created.
# gzip -9 -v SFNx.indiax.tar (It will compress the file to SFNx.indiax.tar.gz) # rcp SFNx.indiax.tar.gz <host_name>:/../FOLDER_BACKUP
#exit
Page A-91
DOCUMENT N: 0029200000000MA07
2.11 GTI
This off-line configuration tool allows the configuration of colours and data formats (tracks datablock, tabulars, weather intensity, etc.) shown on the SDD positions.
2.11.1 Files layout

/local/india/gti/exec /fonts /bin /bitmaps /auxfonts /versiones_SEI /instalables
Figure 2-12: GTI Files Layout. The most relevant files are: Folder /local/india/gti/exec. FILE
.mwmrc .openwin-init .openwin-sys
DESCRIPTION for for for the the the definition definition definition of of of Windows Windows Windows
UNIX file parameters. UNIX file parameters. UNIX file parameters.
.profile
This UNIX file contains start up characteristics concerning the position. It is a link to /local/india/sdd/exec/macros. This UNIX file contains start up characteristics concerning the position. It is a link to /local/india/sdd/exec/macros. This folder contains executables and tools related to the GTI application. This file converts GTI read resources format files into SDD format files. This file converts SDD read resources format files into GTI format files.
.xinitrc
bin formatoSDD formatoSEI
Page A-92
DOCUMENT N: 0029200000000MA07
FILE
inictab
DESCRIPTION File that contains entries with an action: process format. It is used as a parameter when the GTI starts up. This macro installs all the GTI files into the SDD and DRF systems. Link to a GTI process. Link to a GTI process. Link to a GTI process. Link to a GTI process. Link to a GTI process. Link to a GTI process. Link to a GTI process. Link to a GTI process. This file must contain the system configuration about UCS, Technical Supervisors, Operational Supervisors, Towers and DRF components. Text files containing information configure the sdd_units file. about how to
install_sdd.sh m_sei_bloque m_sei_colores m_sei_editor m_sei_listaBloque m_sei_listaTabPV m_sei_monitor m_sei_paleta m_sei_wmenu sdd_units
setup.txt versiones_SEI
Folder containing version configuration files (GTI format). Table 2-13: GTI /local/india/gti/exec folder relevant files.
Folder /local/india/gti/exec/bin. PROCESS

m_sei_bloque m_sei_colores m_sei_editor m_sei_listaBloque m_sei_listaTabPV
DESCRIPTION
It shows a preview of the selected item. This process shows the colour palette in edition mode. This palette is used to select the colours included in the palette for later use. This process manages the GTI edition menu window. This process shows the format text description of the track datablock (right upper blue window). This process shows the format text description of the flight list (right upper blue window). Main engine. This process starts up the rest of the processes. It reads the inictab file that contains entries with an action process format. It shows the colour palette in selection mode. This palette is used to assign a colour to a graphical object. Base process windows holder. Main window, root for the other windows. This process is used to move the windows
m_sei_monitor
m_sei_paleta
m_sei_wmenu
Page A-93
DOCUMENT N: 0029200000000MA07
Table 2-14: GTI /local/india/gti/exec/bin folder relevant process. UTILITIES

termproc usr1proc usr2proc ms_kill_gti
DESCRIPTION The monitor uses this command to stop processes, sending to them a kill 15 command. It manages the inter-process communication. It manages the inter-process communication. It stops the GTI processes.
Folder /local/india/gti/exec/versiones_SEI/instalables. This folder contains version configuration files (SDD format) and GTI non-configurable resources files that are useful for SDD and DRF systems.
2.11.2 GTI 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.
Supply and Installation of the Equipment for21# ps -ef | grep m_ UID root root root root root root root root root PID 1055 1107 1125 1137 1176 1119 1131 1139 1662 PPID 1053 1 1 1 1 1 1 1 1 C 0 0 0 0 0 0 0 0 0 STIME 16:30:51 16:30:52 16:30:52 16:30:53 16:31:03 16:30:52 16:30:53 16:30:53 16:33:06 TTY pts/6 pts/6 pts/6 pts/6 pts/6 pts/6 pts/6 pts/6 pts/6 TIME 0:02 0:02 0:02 0:02 0:09 0:02 0:02 0:03 0:02 CMD m_sei_monitor inictab m_sei_pistas m_sei_lCmpsPista m_sei_lCmpsTabPV m_sei_editor m_sei_listaBloque m_sei_listaTabPV m_sei_wmenu m_sei_bloque
2.11.3 GTI installation 2.11.3.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. User configuration is located in /etc/passwd file, so it is necessary edit this file and adds the corresponding line or lines. Line that user must add to the /etc/passwd file to configure the user for GTI component.
gti:x:0:1:User india:/local/india/gti/exec:/usr/bin/ksh
The user line syntax is the following:

Page A-94
DOCUMENT N: 0029200000000MA07

/etc/group
include the path
additional of the
includes
INDRA application always uses /usr/bin/ksh shell. Table 2-15: GTI User configuration parameters
#vi /etc/passwd

#pwconv #passwd gti New Password: (type password) Re-enter new Password: (re-type password) passwd: password successfully changed for gti
2.11.3.2
Folders configuration

# mkdir m 777 /local #rsh hostname ( Computer that contents the GTI Backup ) #rcp GTIx.indiax.tar.gz hostname:/local/
Where x is the SFN number and the computer hostname where the application has been created. Where host_name is the hostname corresponding to the computer where the application must be installed.
#exit

# cd /local # gunzip GTIx.indiax.tar.gz # tar -xvf GTIx.indiax.tar
The application will be installed.

DOCUMENT N: 0029200000000MA07
#exit
After the application is compilated and decompressed in the machine, sdd_units file must be configured. This file connect the hostnames of different machines with the rol that will have in the system. The final objective is perform an specific adaptation charge for the correct working of DRF, UCS, Technical Supervisors and Operative Supervisors. File setup.txt
UNITS REGISTER FOR THE INSTALLATION: -----------------------------------The configuration of the units is located in the "sdd_units" file. The first line shall contain (in this order): - Project name. - SDDs path to install (DRFs have the same path). Apart from this first line, the file will have another line for every unit to be installed. These lines will have the next format: - Unit type: UCS, OP_SUP, TECH_SUP, TWR or DRF, adding "#WN" if the unit has wordnet capacity. - Unit type order number. - SDD number (SDD#). - Machine name. - Name. Only for towers, otherwise fill with "-". - Sector. Only for towers, otherwise fill with "-". It has two alphanumeric characters.
File sdd_units Change sdd_units file, following the procedure described in setup.txt.
vi /local/india/gti/exec/sdd_units UCS 1 SDD1 <HOSTNAME>11 UCS 1 SDD2 <HOSTNAME>12 UCS 2 SDD3 <HOSTNAME>13 UCS 3 SDD6 <HOSTNAME>19 UCS 4 SDD7 <HOSTNAME>17 OP_SUP 1 SDD4 <HOSTNAME>20 TECH_SUP 1 SDD5 <HOSTNAME>9 TWR 1 SDD8 <HOSTNAME>14 TWR 1 SDD9 <HOSTNAME>15 DRF 1 DRF1 <HOSTNAME>7 DRF 2 DRF2 <HOSTNAME>8

Page A-96
DOCUMENT N: 0029200000000MA07
# cd /local # tar -cvf GTI.indiax.tar india
Where x is the computer hostname where the application has been created.
# gzip -9 -v GTI.indiax.tar (It will compress the file to GTI.indiax.tar.gz) # rcp GTI.indiax.tar.gz <host_name>:/../FOLDER_BACKUP
#exit
2.12 Communications configuration

The CONFIG_COM file is in charge of establishing system communications. A set of nodes are created to nominate the process that are running on each computer. Moreover, this file defines groups and alias for specific communications and specifies the alias corresponding to each computer in order to be identified correctly. The network addresses, which are at the head of the file, correspond to the MULTICAST network addresses and mask for the first LAN (NETWORK: 10.160.77 and MULTICAST: 224.1.52) and to the MULTICAST network addresses and mask for the second LAN (if it exists) (NETWORK: 10.161.77 and MULTICAST: 224.1.53) and to the MULTICAST network addresses and mask for the third LAN (if it exists) (NETWORK: 10.162.77 and MULTICAST: 224.1.54)
NETWORK 10.160.77 10.161.77 10.162.77 MULTICAST 224.1.52 224.1.53 ####################### # Seccion 1 # Asociacion numero-nombre # # Numero Nodo Nodo # --------------#Ultimo Nodo usado 968 #Grupos libres ... 73 75 97 98 99 ####################### 575 fdps1_301_e 576 fdps2_301_e 573 fdps1_301_mr 577 fdps2_301_mr 578 fdps1_301_r 579 fdps2_301_r Etc etc
The most important thing to configure CONFIG_COM is HOSTS part. Those lines explains every node used by each AIRCON application. The used structure is always the same: #hostname application_specific_nodes_composing_processes Where hostname defines the position where the software that referrs subsequent communication nodes is installed.
#<hostname> dbm ############## ___HOSTS___ ########## # #####################################
Page A-97
DOCUMENT N: 0029200000000MA07
#<hostname>1 tool_node fdps1-1 fdps1_302 fdps1_303 fdps1_304_d fdps1_304_f fdps1_304_s fdps1_305_m fdps1_305_l fdps1_306 fdps1_307 fdps1_309_proc fdps1_309w_1 fdps1_309w_2 fdps1_309w_3 fdps1_309r_1 fdps1_309r_2 fdps1_309r_3 fdps1_311 fdps1_315 fdps1_399 fdps1_301_e fdps1_301_mr fdps1_301_r fdps1_305_r fdps1_305_e fdps1_316 fdps1_316_e fdps1_308 fdps1_308_e fdps1_310_proc fdps1_310_1 fdps1_310_2 fdps1_310_3 fdps1_310_4 fdps1_310_5 fdps1_310_6 fdps1_310_7 fdps1_310_8 fdps1_312w fdps1_312r fdps1_312_proc fdps1_313 #<hostname>-2 fdps1-2 # #<hostname> tool_node fdps2-1 fdps2_302 fdps2_303 fdps2_304_d fdps2_304_f fdps2_304_s fdps2_305_m fdps2_305_l fdps2_306 fdps2_307 fdps2_309_proc fdps2_309w_1 fdps2_309w_2 fdps2_309w_3 fdps2_309r_1 fdps2_309r_2 fdps2_309r_3 fdps2_311 fdps2_315 fdps2_399 fdps2_301_e fdps2_301_mr fdps2_301_r fdps2_305_r fdps2_305_e fdps2_316 fdps2_316_e fdps2_308 fdps2_308_e fdps2_310_proc fdps2_310_1 fdps2_310_2 fdps2_310_3 fdps2_310_4 fdps2_310_5 fdps2_310_6 fdps2_310_7 fdps2_310_8 fdps2_312w fdps2_312r fdps2_312_proc fdps2_313 #<hostname>-2 fdps2-2 # #<hostname> rdps1 rdps1_presence rdps1_meteo rdps1_conflict rdps1_conflict_mono rdps1_sup rdps1_adr rdps1_grabac rdps1_mosaic # #<hostname> rdps2 rdps2_presence rdps2_meteo rdps2_conflict rdps2_conflict_mono rdps2_sup rdps2_adr rdps2_grabac rdps2_mosaic # #<hostname> sfns2_decode_cat62 sfns2_db_tracks sfns2_presence sfns2_sup sfns2_man_tracks sfns2_sint_tracks sfns2_flight_plan sfns2_flat_esperas sfns2_conflict sfns2_conflict_mono sfns2_mosaic sfns2_grabac # #<hostname> sfns1_decode_cat62 sfns1_db_tracks sfns1_presence sfns1_sup sfns1_man_tracks sfns1_sint_tracks sfns1_flight_plan sfns1_flat_esperas sfns1_conflict sfns1_conflict_mono sfns1_mosaic sfns1_grabac # #<hostname> fdd_aftn1_ope fdd_aftn1_presence # #<hostname> fdd_aftn2_ope fdd_aftn2_presence # #<hostname> fdd_aftn3_ope fdd_aftn3_presence # #<hostname> fdd_aftn4_ope sdd1_ope sdd1_atc sdd1 sdd1_pbk sdd1_grabac strip_printer1 ted1_01 # #<hostname> fdd_aftn5_ope sdd2_ope sdd2_atc sdd2 sdd2_pbk sdd2_grabac strip_printer2 ted2_01 # #<hostname> tsp1 lan_controler1 prn_controler1 tsp1-1 #<hostname>-2 tsp1-2 # #<hostname> tsp2 lan_controler2 prn_controler2 tsp2-1 #<hostname>-2 tsp2-2 # #<hostname> rpp1 rpp1_int rpp1_ope rpp1_atc # #<hostname> rpp2 rpp2_int rpp2_ope rpp2_atc # #<hostname> uast1 # #<hostname> uast2 # #<hostname> sim_1001_1 sim_1001_2 sim_1002 sim_1003 sim_1004 sim_1005 sim_1006 sim_1008_flt sim_1008_add sim_1009 sim_1010_sup sim_1010_msg sim_1011 sim_1012
DOCUMENT N: 0029200000000MA07
sim_1014 sim_1015 sim_1016 sim_1017_rec sim_1017_rep sim_1018 sim_1020 sim_1021 sim_1022 sim_1023 sim_1013_1 sim_1013_2 radar1 radar2 radar3 radar4 radar5 radar6 radar7 radar8 radar9 radar10 radar11 radar12 radar13 radar14 radar15 radar16 radar17 radar18 radar19 radar20 radar21 radar22 radar23 radar24 #<hostname> sim_sp_1 #<hostname>sim_spv_tss_rdr sim_tss_rdr sim_atc_tss_rdr sim_dld_tss_rdr sim_tssrdr_cadp ####################################
In those lines are defined the communication nodes for FDP1 to establish communications among the application processes. This node's name is fdps1. It is required to define node fdpsX-2.
#<hostname> tool_node fdps1-1 fdps1_302 fdps1_303 fdps1_304_d fdps1_304_f fdps1_304_s fdps1_305_m fdps1_305_l fdps1_306 fdps1_307 fdps1_309_proc fdps1_309w_1 fdps1_309w_2 fdps1_309w_3 fdps1_309r_1 fdps1_309r_2 fdps1_309r_3 fdps1_310 fdps1_311 fdps1_315 fdps1_399 fdps1_301_e fdps1_301_mr fdps1_301_r fdps1_305_r fdps1_305_e fdps1_316 fdps1_316_e fdps1_308 fdps1_308_e fdps1_310 fdps1_310_1 fdps1_310_2 fdps1_310_3 fdps1_310_4 fdps1_310_5 fdps1_310_6 fdps1_310_7 fdps1_310_8 fdps1_312w fdps1_313 #<hostname>-2 fdps1-2 #
In those lines are defined in a similar way the nodes for FDP2, the difference is the node's name, fdps2. It is required to define node fdpsX-2.
# <HOSTNAME>2 tool_node fdps2-1 fdps2_302 fdps2_303 fdps2_304_d fdps2_304_f fdps2_304_s fdps2_305_m fdps2_305_l fdps2_306 fdps2_307 fdps2_309_proc fdps2_309w_1 fdps2_309w_2 fdps2_309w_3 fdps2_309r_1 fdps2_309r_2 fdps2_309r_3 fdps2_310 fdps2_311 fdps2_315 fdps2_399 fdps2_301_e fdps2_301_mr fdps2_301_r fdps2_305_r fdps2_305_e fdps2_316 fdps2_316_e fdps2_308 fdps2_308_e fdps2_310 fdps2_310_1 fdps2_310_2 fdps2_310_3 fdps2_310_4 fdps2_310_5 fdps2_310_6 fdps2_310_7 fdps2_310_8 fdps2_312w fdps2_313 # <HOSTNAME>1-2 fdps2-2 #
Here is refered the SDP1 position (rdps1) and its hostname is the server machine.
#<hostname> rdps1 rdps1_presence rdps1_meteo rdps1_conflict rdps1_conflict_mono rdps1_sup rdps1_adr rdps1_grabac rdps1_mosaic
For SDP2, rdps2 is the node.

#<hostname> rdps2 rdps2_presence rdps2_meteo rdps2_conflict rdps2_conflict_mono rdps2_sup rdps2_adr rdps2_grabac rdps2_mosaic
For SFN1, sfns1 is the node.

#<hostname> sfns1_decode_cat62 sfns1_db_tracks sfns1_presence sfns1_sup sfns1_man_tracks sfns1_sint_tracks sfns1_flight_plan sfns1_flat_esperas sfns1_conflict sfns1_conflict_mono sfns1_mosaic sfns1_grabac
For SFN2, sfns2 is the node

#<hostname> sfns2_decode_cat62 sfns2_db_tracks sfns2_presence sfns2_sup sfns2_man_tracks sfns2_sint_tracks sfns2_flight_plan sfns2_flat_esperas sfns2_conflict sfns2_conflict_mono sfns2_mosaic sfns2_grabac
Page A-99
DOCUMENT N: 0029200000000MA07
Uast1 refers RDCU1 and uast2 refers RDCU2.

#<hostname> uast1
For DRF, the used alias is rpp ; rpp1 refers to DRF1 and rpp2 refers to DRF2
#<hostname> rpp1 rpp1_int rpp1_ope rpp1_atc
In CMD tsp1 refers to CMD1 and tsp2 refers to CMD2. It is required to define node tspX-2.
#<hostname> tsp1 lan_controler1 prn_controler1 tsp1-1 #<hostname>-2 tsp1-2
FDD requires paying attention, because of watching at first lines, fdd_aftnX is defined, but there are some differences, based in the lines that contains nodes fdd_aftnX_presence, which only include FDD positions. If this node is not defined and displays SDD nodes, the defined position is an SDD with a secondary FDD display.
#<hostname> fdd_aftn1_ope fdd_aftn1_presence #<hostname> fdd_aftn4_ope sdd1_ope sdd1_atc sdd1 sdd1_pbk sdd1_grabac strip_printer1 ted1_01
REMARK: All the computers connected to the system needs to have the same CONFIG_COM file in the appropriate folder. The modification and distribution of the CONFIG_COM file is necessary if a new computer is added to the system or if a change in this file is carried out.
Page A-100
DOCUMENT N: 0029200000000MA07
3 Starting and finishing processes concerning the system components

3.1 Starting process
3.1.1 Switching on the computers

Once the computer is powered on, the Operating System is loaded, and the Boot process starts. During this process a set of tests are performed in order to verify the hardware integrity and, if they are successful, the system either, request a user login and password or to start the application process loading. If the /etc/rc3.d/S99start file exists, the application will be automatically loaded. The content of this file is:
#!/bin/sh su india
If this file does not exist, the computer will remain in console login status.
3.1.2 Starting up the application

It can be performed in two ways: Manually, when the computer has a console login status, type the system login and password (india:india). From any CMD (See User Manual concerning the CMD).
3.2
Finishing process
3.2.1 Shutting down the application

The finishing process can be performed in two different ways: From any CMD (See User Manual concerning the CMD). In general, applications will be shut down by the means of stopping their processes. Calling a script located at the execution folder or using a hotkey will perform this stopping process. The procedures for finishing the processes that constitute every component are:
# ps ef grep i process
To get the PID.

# kill 9 PID
Were PID is the process identifier.
3.2.2 Shutting down a SDD combined with FDD

By means of an accelerator: Press <Alt>+<Shift>+<S> on the SDD. From any other computer, open a terminal and connect to the SDD as a india user and type termproc monitor and termproc m_. With this, the computer goes to console-login screen. Both applications run on the same computer so, stopping the processes running on it the SDD goes to console login status and the application is killed.
Page A-101
DOCUMENT N: 0029200000000MA07
3.2.3 Shutting down a FDD

By calling the script: killapplication rmipcs
3.2.4 Shutting down a SDP

By calling the script killapplication_sdp LINUX -rmipcs
3.2.5 Shutting down a FDP

By calling the script: killapplication LINUX rmipcs
3.2.6 Shutting down a CMD

The supervision_central: termproc supervision_central process must be stopped. The pssh: termproc pssh process must be stopped.
3.2.7 Shutting down a DRF

The same as SDD.
3.2.8 Shutting down a RDCU

By calling the script: kill_rdcu.
3.2.9 Shutting down a RDCU Transmission

By calling the script: kill.rdfd.
3.2.10 Shutting down an SFN

By calling the script killapplication_sfn LINUX -rmipcs
3.2.11 Complete computer switch off

The process to follow to get a complete switch off is: When the computer has assumed the console login status, introduce the login: password root:root. Once this is carried out, execute:
# shutdown -h now
Page A-102
DOCUMENT N: 0029200000000MA07
4 System installation and maintenance

4.1 Base Software
The next paragraphs described the standard installation process. The Operating System can be installed on any computer through of the Kickstart method, as described on the Table 4-3: DRF Error Messages Kickstart Administration Guide section, or manually method.
4.1.1 Red Hat Enterprise Linux operating system.

The complete installation will be performed in 3 consecutive steps: Initial installation. 1. This step explains the standard Operating System installation in order to get an adequate work environment. Application configuration. 2. This step describes the suitable computer network configuration in order to establish the appropriate communications between computers. Modification of common and specific Files. 3. This last step clarifies the way of configuring a set of mandatory options (communications, hour synchronization, users, etc.) to keep the equipment in good working order.
4.1.1.1 Initial Installation

The following steps show how to achieve this standard installation: To install Red Hat Enterprise Linux from a CD-ROM, when the machine starts, choose the CD/DVD boot option and select OK. When prompted, insert the Red Hat Enterprise Linux DVD into your CD/DVD drive (if you did not boot from the CD). Once the DVD is in the DVD drive, select OK, and press Enter.
Page A-103
DOCUMENT N: 0029200000000MA07
Figure 4-1: Installation Red Hat Enterprise Linux Press "enter" button to start installation. Note: The first CD-ROM is required when booting the installation program, and again after subsequent CD-ROMs have been processed.
Page A-104
DOCUMENT N: 0029200000000MA07
Figure 4-2: Testing CD media We must move with the cursor, select "Skiip button" and press "enter" button. The installation program then probes your system and attempts to identify your CD-ROM drive. It starts by looking for an IDE (also known as an ATAPI) CD-ROM drive. If found, continue to the next stage of the installation process.
Page A-105
DOCUMENT N: 0029200000000MA07
Figure 4-3: Welcome to Red Hat Enterprise Linux The Welcome screen does not prompt you for any input. Read over the help text in the left panel for additional instructions and information on where to register your Red Hat Enterprise Linux product. Click on the "Next" button to continue.
Page A-106
DOCUMENT N: 0029200000000MA07
4.1.1.1.1 Language Selection

Using your mouse, select a language to use for the installation. Selecting the appropriate language also helps target your time zone configuration later in the installation. The installation program tries to define the appropriate time zone based on what you specify on this screen.
Figure 4-4: Language Selection. Once you select the appropriate language, click "Next" to continue.
Page A-107
DOCUMENT N: 0029200000000MA07
4.1.1.1.2 Select Keyboard
Figure 4-5: Keyboard Configuration Choose "U.S. International" and press "Next" button.
Page A-108
DOCUMENT N: 0029200000000MA07
4.1.1.1.3 Disk Partitioning Setup

Partitioning allows you to divide your hard drive into isolated sections, where each section behaves as its own hard drive. Partitioning is particularly useful if you run multiple operating systems. On this screen, you can choose to perform automatic partitioning, or manual partitioning using Create custom layout. Choose the create custom layout "option and press "Next" button.
Figure 4-6: Disk Partitioning Setup.
Page A-109
DOCUMENT N: 0029200000000MA07
Figure 4-7: Disk Setup In the screen appears the disks availables, remove all slices of the disks, using "Delete" button. Select one disk and press "New" button to create the swap slice.
Page A-110
DOCUMENT N: 0029200000000MA07
Figure 4-8: Add Swap Partition Select free space of the disk and press "new" button to create the root slice:
Figure 4-9: Add Root Partition
Page A-111
DOCUMENT N: 0029200000000MA07
Figure 4-10: Disk Setup Press "next" button to continue with the installation.
Page A-112
DOCUMENT N: 0029200000000MA07
4.1.1.1.4 Boot Loader Configuration
Figure 4-11: Boot Loader Configuration Press "next" button in this screen
Page A-113
DOCUMENT N: 0029200000000MA07
4.1.1.1.5 Network Configuration

If you do not have a network device, this screen does not appear during your installation.
Figure 4-12: Network Configuration I Choose "manually" hostname, and type the name of the machine. Then select a network device, click Edit. From the Edit Interface pop-up screen, you can choose to configure the IP address and Netmask of the device and you can choose to activate the device at boot time. If you select Activate on boot, your network interface is started when you boot.
Page A-114
DOCUMENT N: 0029200000000MA07
Figure 4-13: Network Configuration II
In Gateway and DNS fields is not necessary put nothing. Once you have the configuration press "next" button, and then press "Continue" two times.
4.1.1.1.6 Time Zone Configuration

Set Casablanca time zone by selecting the city in the map or scroll through the list at the bottom of the screen to select "Casablanca". Select System Clock uses UTC. Press "Next button".
Page A-115
DOCUMENT N: 0029200000000MA07
Figure 4-14: Time Zone Selection
Page A-116
DOCUMENT N: 0029200000000MA07
4.1.1.1.7 Set Root Password

Setting up a root account and password is one of the most important steps during your installation. Your root account is similar to the administrator account used on Windows NT machines. The root account is used to install packages, upgrade RPMs, and perform most system maintenance. Logging in as root gives you complete control over your system.
Figure 4-145: Set Root Password Use the root account only for system administration. To become root, type su - root at the shell prompt in a terminal window and then press Enter. Then, enter the root password and press Enter.
Page A-117
DOCUMENT N: 0029200000000MA07
4.1.1.1.8 Package Group Selection

Select Customize the set of packages to be installed option on the screen. Clicking Next takes you to the Package Group Selection screen.
Figure 4-156: Package Installation Defaults
Page A-118
DOCUMENT N: 0029200000000MA07
Figure 4-167: Desktop Environments Desktop Enviroments: GNOME Desktop Environment -- 43/43 KDE (K Desktop Environment) -- 11/11
Page A-119
DOCUMENT N: 0029200000000MA07
Figure 4-178: Applications Applications: Select All (except Games and Entertainment)
Page A-120
DOCUMENT N: 0029200000000MA07
Figure 4-19: Development Development: Select All
Page A-121
DOCUMENT N: 0029200000000MA07
Figure 4-18: Servers
Servers: FTP Server. Legacy Network Server 7/7 (look figure 22). Network Servers 2/2. PostgreSQL Database 12/12 Printing Support 8/8 Server Configuration Tools 6/6 Web Server 4/4 Windows File Server 1/1
Page A-122
DOCUMENT N: 0029200000000MA07
Figure 4-19: Legacy Network Package Details
Page A-123
DOCUMENT N: 0029200000000MA07
Figure 4-20: Base System Base System: Administration Tools 12/12 Base 124/124 Legacy Software Support 11/11 System Tools 40/40 X Window System 35/35
Page A-124
DOCUMENT N: 0029200000000MA07
Figure 4-21: Mail Server Package Details
Page A-125
DOCUMENT N: 0029200000000MA07
4.1.1.1.9 Preparing to Install

A screen preparing you for the installation of Red Hat Enterprise Linux now appears.
Press "Next" button, and then press "Continue" button. REMARK: The software you have selected to install will require a DVD to RHEL 5
4.1.1.1.10
Installing Packages
At this point there is nothing left for you to do until all the packages have been installed. How quickly this happens depends on the number of packages you have selected and your computer's speed.
4.1.1.1.11
Installation Complete
Red Hat Enterprise Linux installation is now complete. The installation program prompts you to prepare your system for reboot. The first time you start your Red Hat Enterprise Linux system in run level 5 (the graphical run level), the Setup Agent is presented, which guides you through the Red Hat Enterprise Linux configuration. Using this tool, you can set your system time and date, install software, register your machine with Red Hat Network, and more. The Setup Agent lets you configure your environment at the beginning, so that you can get started using your Red Hat Enterprise Linux system quickly.
Page A-126
DOCUMENT N: 0029200000000MA07

The next paragraphs will explain how to establish the computer basic configuration and how to prepare them in order to manage the application. The system, after being rebooted, presents a windows environment and asks for a user: Press "root+ <Intro> When a session is started with a root user: Open the Terminal. To do this, first press the right button of the mouse and select Open Terminal. Once the Terminal is opened, execute the following instructions:
# pwconv # passwd root root root
Later on:
# vi /etc/inittab :/id:5:initdefault: <dd> <i> id:3:initdefault: <ESC> :wq!
Later on:
# echo "rsh" >> /etc/securetty # echo "rexec" >> /etc/securetty # echo "rlogin" >> /etc/securetty # echo "kernel.shmall = 4294967296" >> /etc/sysctl.conf # echo "kernel.sem = 1250 32000 32 1280" >> /etc/sysctl.conf
# echo "net.ipv4.icmp_echo_ignore_broadcasts = 0" >> /etc/sysctl.conf # echo "net.core.wmem_default = 44126976" >> /etc/sysctl.conf # echo "net.core.rmem_default = 44126976" >> /etc/sysctl.conf # echo "net.core.rmem_max = 44131071" >> /etc/sysctl.conf # echo "net.core.wmem_max = 44131071" >> /etc/sysctl.conf
In the /etc/pam.d directory must modify the "rsh, rexec, rlogin" files. rsh
#%PAM-1.0 # For root login to succeed here with pam_securetty, "rsh" must be # listed in /etc/securetty. auth required pam_nologin.so
Page A-127
DOCUMENT N: 0029200000000MA07
auth auth auth account session session
sufficient required sufficient include optional include
pam_securetty.so pam_env.so pam_rhosts_auth.so system-auth pam_keyinit.so force revoke system-auth
rexec
#%PAM-1.0 # For root login to succeed here with pam_securetty, "rexec" must be # listed in /etc/securetty. auth auth auth auth account session session required sufficient required include include optional include pam_nologin.so pam_securetty.so pam_env.so system-auth system-auth pam_keyinit.so force revoke system-auth
rlogin
#%PAM-1.0 # For root login to succeed here with pam_securetty, "rlogin" must be # listed in /etc/securetty. auth auth auth auth auth account password session session required sufficient required sufficient include include include optional include pam_nologin.so pam_securetty.so pam_env.so pam_rhosts_auth.so system-auth system-auth system-auth pam_keyinit.so system-auth force revoke
Also, in the /etc/xinetd.d/ directory must modify the "rsh, rexec, rlogin and gssftp" files. rsh
# default: on # description: The rshd server is the server for the rcmd(3) routine and, \ # # consecuently for the rsh(1) program. The server provides \ remote execution facilities with authentication based on \
DOCUMENT N: 0029200000000MA07
privileged port numbers from trusted hosts.
service shell { disable = no flags socket_type wait user log_on_success log_on_failure server } = REUSE = stream = no = root = = +=USERID +=USERID
= /usr/sbin/in.rshd
rexec
# default: off # description: Rexec is the server is the server for the rexec(3) routine. The server \ # # provides remote execution facilities with authentication based \ on user names and passwords.
service exec { disable = no flags socket_type wait user log_on_success log_on_failure server } = REUSE = stream = no = root = = +=USERID +=USERID
= /usr/sbin/in.rexecd
rlogin
# default: on # description: rlogind is the server is the server for the rlogin(1) program.The server \ # # provides a remote login facility with authentication based on \ privileged port numbers from trusted hosts.
service login { disable = no flags socket_type wait = REUSE = stream = no
Page A-129
DOCUMENT N: 0029200000000MA07
user log_on_success log_on_failure server }
= root = = +=USERID +=USERID
= /usr/sbin/in.rlogind
gssftp
# default: off # description: The kerberized FTP server accepts FTP connections \ # service ftp { disable = no flags socket_type wait user server server_args log_on_failure } = REUSE = stream = no = root = /usr/kerberos/sbin/ftpd = -l += USERID that can be authenticated with Kerberos 5.
To this changes take effect you must reload xinetd service, to do execute:
# /sbin/service xinetd restart
Is necessary, in the /etc/profile file ulimit core files:

ulimit S c unlimited > /dev/null 2>&1
Is necessary, in the /etc/nsswitch.conf file delete the word dns in this line:
hosts: files dns
Is necessary a file called "crypt" to the application works correctly. In a terminal execute:
# vi /usr/bin/crypt <i> #!/usr/bin/perl -w
$pass = shift or die "Usage: ", $0 =~ /([^\/]*$)/, " passwd < file\n";
Page A-130
DOCUMENT N: 0029200000000MA07
undef $/; @file = split //, <>;
# Set "slurp mode" # Make a 'character' array from file
@pass = map{ $x = ord; $y = ( $x + 10 ) ** 2 % 256; $z = ( $x - 10 ) ** 2 % 256; chr ( $y ^ $z ) } split //, $pass;
print chr( ord $file[$_] ^ ord $pass[$_ % scalar @pass] ) for 0 .. $#file <ESC> :wq!
Copy ISODE libraries from KICKSTART server to the FDP application works correctly:
# cd /image/kickstart/COMMON # rcp p isode.RHEL5.tar.gz <hostname>:/opt # rsh <hostname> # cd /opt # tar zxvf isode.RHEL5.tar.gz
REMARK: The startup_fdp.sh FDP script must contain the line: export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/opt/isode/lib
Is necessary that we install 3 additionals packets: ksh, page and openmotif. ksh
# rpm -ivh ksh-20080202-2.el5.x86_64.rpm
page
# rpm -ivh mpage-2.5.4-7.1.x86_64.rpm
openmotif
# rpm -ivh openmotif-2.3.0-0.3.el5.i386.rpm # rpm -ivh openmotif-2.3.0-0.3.el5.x86_64.rpm
4.1.1.3 Modification of common files 4.1.1.3.1 IP address addition

/etc/hosts File.
Page A-131
DOCUMENT N: 0029200000000MA07
The /etc/hosts file contains the IP addresses that have been assigned to every computer during the Operating System installation process. Additionally it is mandatory to assign, for every address, its corresponding hostname. The /etc/hosts must be the same for all the computers, less in the RDCU's, that the file must have one line more near to the hostname of the RDCU. The lines are: RDCU1 uast1 radar1 radar2 radar3 radar4 radar5 radar6 radar7 radar8 radar9 radar10 radar11 radar12 radar13 radar14 radar15 radar16 uast2 RDCU2 uast1 uast2 radar1 radar2 radar3 radar4 radar5 radar6 radar7 radar8 radar9 radar10 radar11 radar12 radar13 radar14 radar15 radar16 The content of the file /etc/hosts is:
######## LAN 1 ############################################### 10.160.77.1 10.160.77.2 10.160.77.3 10.160.77.4 Etc.. ######## LAN 2 ############################################### 10.161.77.1 10.161.77.2 10.161.77.3 Etc.. ######## LAN 3 ############################################### 10.162.77.1 10.162.77.2 10.162.77.3 Etc.. ####### PRINTERS ####################### 10.160.77.151 10.160.77.152 lp1 lp2 <hostname>-3 <hostname>-3 <hostname>-3 <hostname>-2 <hostname>-2 <hostname>-2 <hostname> <hostname> <hostname> <hostname>
####### SWITCHES ####################### 10.160.77.225 switch_1
####### NTP SERVER #################### 10.160.77.230 ntp_server1
####### NTP SLAVE ####################
Page A-132
DOCUMENT N: 0029200000000MA07
10.160.77.231
ntp_slave1
If there are two different Neptune computers, it is necessary to have three different host files.
4.1.1.3.2 Time synchronization

File /etc/ntp.conf. This application allows to the system to configure its own time with the GPS time.
restrict default nomodify notrap noquery restrict 127.0.0.1 fudge 127.127.1.0 stratum 5 driftfile /var/lib/ntp/drift server ntp_server1 prefer server ntp_server2 server ntp_server1-2 server ntp_server2-2 server ntp_server2
To enable ntp service: Folder /etc/init.d. It is possible "start" or "stop" this process. For instance:
# /sbin/chkconfig --level 2345 ntpd on # /sbin/service ntpd start
For search the specific process:

# ps ef | grep -i ntp ntp 9944 1 0 Mar07 ? 00:00:00 ntpd -u ntp:ntp -p /var/run/ntpd.pid g
Note: We have one special utility to synchronize & check the time of all the computers in the network. (see: point 8. COMMUNICATIONS FOLDER of this manual)
4.1.1.3.3 Users configuration

Refer to the Installation subsection of each component.
4.1.1.3.4 Bootable applications

/etc/rc3.d/S99start file.
This file will be in charge of the bootable application once the computer has been rebooted.
4.1.1.4 Files and Services Modification

Kickstart modifies automatically files and services that should be inhibited and activated for a correct way of working of the system. Anyway, if the installation is carried out from Kickstart, CD, or DVD, these files must be checked:
DOCUMENT N: 0029200000000MA07
# /sbin/service autofs stop # /sbin/service iscsid stop # /sbin/service acpid stop # /sbin/service bluetooth stop # /sbin/service arptables_jf stop # /sbin/service isdn stop # /sbin/service yum-updatesd stop # /sbin/chkconfig --level 2345 autofs off # /sbin/chkconfig --level 2345 iscsi off # /sbin/chkconfig --level 2345 iscsid off # /sbin/chkconfig --level 2345 acpid off # /sbin/chkconfig --level 2345 arptables_jf off # /sbin/chkconfig --level 2345 isdn off # /sbin/chkconfig --level 2345 yum-updatesd off # /sbin/chkconfig --level 12345 cpuspeed off # /sbin/chkconfig --level 2345 sendmail off # /sbin/chkconfig --level 345 kudzu off # /sbin/chkconfig --level 345 rhnsd off # /sbin/chkconfig --level 2345 rexec on # /sbin/chkconfig --level 2345 rlogin on # /sbin/chkconfig --level 2345 rsh on # /sbin/chkconfig --level 2345 gssftp on # /sbin/service rexec start # /sbin/service rlogin start # /sbin/service rsh start # /sbin/service gssftp start
Page A-134
DOCUMENT N: 0029200000000MA07
4.2
Auxiliary devices
The auxiliary devices to be considered are:
4.2.1 Printer configuration and installation 4.2.1.1 HP Color LaserJet Printer Installation - Administration
First step to configure HP Color LaserJet printer is configure IP Address and SUBNET MASK in the menu of the printer. Configuration IP ADDRESS and SUBNET MASK. First we must open the menu of printer by pressing the button OK. For configure IP address, we need to enter in this menu: CONFIGURE DEVICE I/O EMBEDDED JETDIRECT MENU TCP/IP IPV4 SETTINGS MANUAL SETTINGS IP ADDRES Put a first available ip to the printer from the same range of the network. For configure SUBNET MASK, we need to enter in this menu: CONFIGURE DEVICE I/O EMBEDDED JETDIRECT MENU TCP/IP IPV4 SETTINGS MANUAL SETTINGS SUBNET MASK Put the subnet mask to 255.255.255.0, because we are working within a local network. REMARK: In case of changing the IP range in the local area network or accessing to the printer from a computer in other family range of IP codes, after viewing this previous page it would not be possible to access to the printer (network would be unreachable).
After this, the laser printer is connected to the LAN, and next step is adding the IP and hostname to the /etc/hosts file of all the computers. Note: Printer hostnames should be seven characters at most and it is recommended to set <hostname>_lpX as the name of the printer (where <hostname> are the three first characters of the name of the project, and X is the printer number in the net).
Once the printer is configured, next step is the installation of a queue in the computer to use it.
4.2.1.2 Install HP Color LaserJet in a computer

First, we must to be sure that the ppd file of the printer is in /usr/share/cups/model/ directory.
# ls -la /usr/share/cups/model/*ppd -rw-r--r-1 root root 92386 Feb 15 09:45 /opt/HP_Color_LaserJet_3000.ppd
Page A-135
DOCUMENT N: 0029200000000MA07
-rw-r--r--rw-r--r--rw-r--r--
1 root root 92386 Feb 15 09:45 /opt/HP_Color_LaserJet_3800.ppd 1 root root 92386 Feb 15 09:45 /opt/HP_Color_LaserJet_4700.ppd 1 root root 92386 Feb 15 09:45 /opt/HP_Color_LaserJet_CP.ppd
Also, we need to be sure that the configuration file named beh is present in /usr/lib64/cups/backend/ and in /usr/lib/cups/backend/ directories.
-rw-r--r--rw-r--r-1 root root 92386 Feb 15 09:45 /usr/lib64/cups/backend/beh 1 root root 92386 Feb 15 09:45 /usr/lib/cups/backend/beh
Then, we must to execute the next command:

# lpadmin p <hostname_lp> E v beh:/1/3/5/socket://<hostname>_lpX:9100 P /usr/share/cups/model/HP _Color_LaserJet_XXXX.ppd
4.2.2 Digi Neo Card

To install drivers we will do: Copy DigiNeo.1.3-15_2.6.18-128.el5.tar.gz file from KICKSTART server to /opt directory.
# cd /opt # gunzip DigiNeo.1.3-15_2.6.18-128.el5.tar.gz # tar -xvf DigiNeo.1.3-15_2.6.18-128.el5.tar # cd DigiNeo.1.3-15_2.6.18-128.el5 # rpm -ivh dgnc-1.3-15_2.6.18-128.el5.x86_64.rpm # rpm -ivh dgnc-debuginfo-1.3-15_2.6.18-128.el5.x86_64.rpm # /sbin/chkconfig --add dgnc
To start and stop de DGNC driver:

# /etc/rc.d/init.d/dgnc start # /etc/rc.d/init.d/dgnc stop
4.2.3 FarSync Card

To install drivers we will do: Copy FarSite.3.03-09_RHEL5.tar.gz file from KICKSTART server to /opt directory.
# cd /opt # gunzip FarSite.3.03-09_RHEL5.tar.gz # tar xvf FarSite.3.03-09_RHEL5.tar.gz # cd FarSite.3.03-09_RHEL5 # mkdir -m 777 /usr/src/redhat # echo "brewbuilder:x:0:0:root:/root:/bin/bash" >> /etc/passwd # echo "brewbuilder:x:0:root" >> /etc/group # rpm -ivh elfutils-libs-0.125-3.el5.x86_64.rpm # rpm -ivh elfutils-0.125-3.el5.x86_64.rpm # rpm -ivh rpm-build-4.4.2-47.el5.x86_64.rpm
Page A-136
DOCUMENT N: 0029200000000MA07
# rpm -ivh unifdef-1.171-5.fc6.x86_64.rpm # rpm -ivh kernel-2.6.18-53.el5.src.rpm # rpmbuild -bp --target=x86_64 /usr/src/redhat/SPECS/kernel-2.6.spec # tar zxvf fsx25-3.03.09.tar.gz # cd fsx25-3.03.09 # ln -s /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.x86_64 /usr/src/linux # ./install # cd oem/farsync-1.08.09/kernel2.6-oem # cp -p /usr/src/redhat/BUILD/kernel-2.6.18/linux-2.6.18.x86_64/drivers/net/wan/syncppp.c . # mv Makefile Makefile.ORIG # ln -s Makefile-with-syncppp Makefile # make clean # make # make install # cd # gawk '{ > if($1=="DEV_MODE=600") > { > printf("%s\n","DEV_MODE=777"); > } > else if($1=="NCB_MODE=600") > { > printf("%s\n","NCB_MODE=777"); > } > else print $0; > }' /etc/init.d/fsx25 > /etc/init.d/fsx25.tmp # mv -f /etc/init.d/fsx25.tmp /etc/init.d/fsx25 # chmod 755 /etc/init.d/fsx25 # gawk ' BEGIN {sw_ins=0;sw_rm=0} > { > if($1=="DEV_MODE=600") > { > printf("%s\n","DEV_MODE=777"); > } > else if((!sw_ins) && ($1" "$2=="#/sbin/insmod $MODULE_DIR/syncppp.ko")) > print " > sw_ins=1; > } > else if((!sw_rm) && ($1" "$2=="#/sbin/rmmod $MODULE_DIR/syncppp.ko")) /sbin/insmod $MODULE_DIR/syncppp.ko";
Page A-137
DOCUMENT N: 0029200000000MA07
> { > print " > sw_rm=1; > } > else > { > print $0; > } > }' /etc/init.d/farsync > /etc/init.d/farsync.tmp # mv -f /etc/init.d/farsync.tmp /etc/init.d/farsync # chmod 755 /etc/init.d/farsync # /sbin/service fshcx25 start # cp -p /opt/FarSite.3.03-09_RHEL5/jre-6u13-linux-amd64.rpm /opt # cd /opt # rpm -ivh jre-6u13-linux-amd64.rpm # rm -f /opt/jre-6u13-linux-amd64.rpm # gawk ' { > if ($0=="/usr/bin/java -classpath fsmgmt.jar:jhbasic.jar fsmgmt 127.0.0.1 8530") > { > print "/usr/java/jre1.6.0_13/bin/java -classpath fsmgmt.jar:jhbasic.jar fsmgmt 127.0.0.1 8530"; > } > else print $0; > }' /usr/local/fsx25d/config/x25Config.sh > /usr/local/fsx25d/config/x25Config.sh.tmp # mv -f /usr/local/fsx25d/config/x25Config.sh.tmp /usr/local/fsx25d/config/x25Config.sh # chmod 755 /usr/local/fsx25d/config/x25Config.sh /sbin/rmmod $MODULE_DIR/syncppp.ko";
4.2.4 Nvidia Graphic Card

To install drivers we will do: Shutdown the X server:
# init 3
Copy NVIDIA-Linux-x86_64-190.53-pkg2.run file from KICKSTART server to /opt directory.

# cd /opt # sh NVIDIA-Linux-x86_64-190.53-pkg2.run -a -q -n -N --ui=none -X
4.2.5 Quad Port Network Card

To install drivers we will do: Copy e1000-7.6.15a-1.x86_64.rpm file from KICKSTART server to /opt directory.
# cd /opt # rpm -ivh e1000-7.6.15a-1.x86_64.rpm
Page A-138
DOCUMENT N: 0029200000000MA07
# /sbin/insmod /lib/modules/2.6.18-53.el5/kernel/drivers/net/e1000/e1000.ko
4.2.6 PCI334A RS-232 Card

To install drivers: Copy PCI334A.7.4_RHEL5.tar.gz file from KICKSTART server to /opt directory.
# cd /opt # gunzip PCI334A.7.4_RHEL5.tar.gz # tar -xvf PCI334A.7.4_RHEL5.tar # cd PCI334A.7.4_RHEL5 # sh ./INSTALL # cd # echo "#!/bin/bash" > /etc/rc3.d/S99pci334a # echo "" >> /etc/rc3.d/S99pci334a # echo "/opt/RP334UN/pti/drivers/mps/load_mps" >> /etc/rc3.d/S99pci334a # chmod 777 /etc/rc3.d/S99pci334a
4.2.7 Meinberg Configuration.

For first time installation enter TCP/IP address, netmask and default gateway. To get an overview of the current configuration press F2 from main menu. Press F2 again to enter SETUP configuration page. Please ask your administrator for proper TCP/IP configuration:
Then press 3 times the OK button to change to IPV4 ETH0 configuration page to enter the IP address, netmask and the default gateway:
After this all further settings can be done via network interface, either by using a WEB browser or a Telnet Session.
4.2.7.1 Menu: NTP Configuration

The NTP configuration page is used to set up the additional NTP parameters needed for a more specific configuration of the NTP subsystem.
Page A-139
DOCUMENT N: 0029200000000MA07
The first page will reflect the current state of the NTP. The line Offset PPS: 1 ms shows the current offset between the system time and the reference time (GPS).
To enter the following sub menu press the OK or right arrow button. The following menu is displayed.
4.2.7.2 Menu: Stratum of local clock

The local clock is only chosen as the NTP time reference after the GPS clock lost its synchronization. The stratum level of this local clock is set to 12, this ensures that clients recognize the switchover to the local clock and are able to eventually take further actions. The local clock can be disabled if the timeserver should not answer anymore when the reference clock is out of order. The field Stratum of local clock is used to change the stratum level of the local clock, default is 12.
4.2.7.3 Menu: Reset Time

If the time of the reference clock has changed (e.g. while testing with different times) the system time has to bet set with the time of the reference clock and the NTP has to be restarted.
Done this, the ntp server is configured. It can be connected to the switch. NOTE: The ntp server IP should appear in the /etc/hosts file in all machines.
4.2.8 IER configuration

Connect a laptop to IER with an UTP cable. Configure 192.168.0.50 IP address in the laptop. Connect to IER via http. The IER IP address is 192.168.0.100.
Page A-140
DOCUMENT N: 0029200000000MA07
One time connected to IER enter the user "admin" and password "13542" on your browser. Step 1. Go to Connection Configuration -> Rs232 com settings and change Number of data bits value to 8 and Parity value to None. Press Apply all modifications
Step 2. Go to Configuration and Adjustements -> Emulation Parameters and change Possible values: value to Main transitions. Press Apply all modifications
Step 3 Go to Configuration and Adjustements -> Printer Parameters and change Vertical global offset (1/10 mm) value to -10, and change Print pos global offset (1/10 mm) value to 5. Press Apply all modifications
Page A-141
DOCUMENT N: 0029200000000MA07
Done this, the printer is configured. It can be connected to the RS232 port of the machine. NOTE: The printer port is set to COM2
Page A-142
DOCUMENT N: 0029200000000MA07
4.2.9 Configuration to different monitor in all system 4.2.9.1 Resolution for to different positions
SDD, FDD, CMD Tower (EIZO HB 20): 1280x1024 DBM, FDD, CMD, DRF (EIZO 22" monitor): 1680X1050 SDD (Tech Source 28 monitor): 2048x2048 FDP, SDP, RDCU (KVM monitor): 1024x768 Position SDD, FDD, CMD Tower - EIZO HB 20
# nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 1.0 (buildmeister@builder26) Thu Dec 13
# Xorg configuration created by pyxf86config Section "ServerLayout" Identifier "Default Layout" Screen 0 InputDevice InputDevice EndSection Section "Files" RgbPath ModulePath FontPath FontPath EndSection Section "Module" Load Load Load Load Load Load Load EndSection Section "ServerFlags"
"Screen0" 0 0 "Mouse0" "CorePointer" "Keyboard0" "CoreKeyboard"
"/usr/share/X11/rgb" "/usr/lib64/xorg/modules" "unix/:7100" "built-ins"
"glx" "dbe" "extmod" "fbdevhw" "record" "freetype" "type1"
DOCUMENT N: 0029200000000MA07
Option Option EndSection
"DontZap" "yes" "DontVTSwitch" "yes"
Section "InputDevice" Identifier "Mouse0" Driver Option Option Option Option EndSection Section "InputDevice" Identifier "Keyboard0" Driver "kbd" Option Option Option EndSection Section "Monitor" Identifier VendorName ModelName HorizSync VertRefresh Option EndSection Section "Device" Identifier Driver EndSection Section "Screen" Identifier Device Monitor DefaultDepth "XkbModel" "pc105" "XkbLayout" "us_intl" "XkbVariant" "intl" "mouse" "Protocol" "auto" "Device" "/dev/input/mice" "Emulate3Buttons" "yes" "ZAxisMapping" "4 5"
"Monitor0" "Unknown" "Unknown" 30.0 - 110.0 50.0 - 150.0 "DPMS"
"Videocard0" "nvidia"
"Screen0" "Videocard0" "Monitor0" 8
Page A-144
DOCUMENT N: 0029200000000MA07
Option SubSection Viewport Depth Modes EndSubSection EndSection
"NoRenderExtension" "TRUE" "Display" 0 0 8 "1280x1024
Position DBM, FDD, CMD - EIZO 22" # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: 18:55:42 PST 2007 version 1.0 (buildmeister@builder26) Thu Dec 13
# XFree86 4 configuration created by pyxf86config Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice InputDevice EndSection Section "Files" # RgbPath is the location of the RGB database. the Note, this is the name of There is normally "Mouse0" "CorePointer" "Keyboard0" "CoreKeyboard"
# file minus the extension (like ".txt" or ".db"). # no need to change the default.
# Multiple FontPath entries are allowed (they are concatenated together) # By default, Red Hat 6.0 and later now use a font server independent of # the X server to render fonts. RgbPath FontPath EndSection Section "Module" Load Load Load Load "dbe" "extmod" "fbdevhw" "glx" "/usr/X11R6/lib/X11/rgb" "unix/:7100"
Page A-145
DOCUMENT N: 0029200000000MA07
Load Load Load EndSection
"record" "freetype" "type1"
Section "InputDevice" # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) # Option "Xleds" "1 2 3" # To disable the XKEYBOARD extension, uncomment XkbDisable. # Option "XkbDisable" # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: # Option "XkbModel" "pc102" # If you have a US Microsoft Natural keyboard, you can use: # Option "XkbModel" "microsoft" # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # Option "XkbLayout" "de" # or: # # Option Option "XkbLayout" "XkbVariant" "de" "nodeadkeys"
# # If you'd like to switch the positions of your capslock and # control keys, use: # Option "XkbOptions" "ctrl:swapcaps" # Or if you just want both to be control, use: # # Option Identifier Driver Option Option EndSection "XkbOptions" "ctrl:nocaps"
"Keyboard0" "kbd" "XkbModel" "pc105" "XkbLayout" "us_intl"
Section "InputDevice" Identifier "Mouse0" Driver Option

"mouse" "Protocol" "IMPS/2"

DOCUMENT N: 0029200000000MA07
Option Option Option EndSection Section "Monitor" Identifier VendorName ModelName HorizSync VertRefresh Option EndSection Section "Device" Identifier Driver VendorName BoardName EndSection Section "Screen" Identifier Device Monitor DefaultDepth SubSection Viewport Depth Modes EndSubSection EndSection
"Device" "/dev/input/mice" "ZAxisMapping" "4 5" "Emulate3Buttons" "yes"
"Monitor0" "Monitor Vendor" "LCD Panel 1600x1200" 31.5 - 67.0 50.0 - 75.0 "dpms"
"Videocard0" "nvidia" "Videocard vendor" "NVIDIA Unknown (generic)"
"Screen0" "Videocard0" "Monitor0" 8 "Display" 0 0 8 "1680x1050"
Position SDD - Tech Source 28 # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 1.0 (buildmeister@builder26) Thu Dec 13 18:55:42 PST 2007 # nvidia-settings: X configuration file generated by nvidia-settings # nvidia-settings: version 1.0 (buildmeister@builder26) Thu Dec 13 18:56:19 PST 2007
DOCUMENT N: 0029200000000MA07
# Xorg configuration created by system-config-display Section "ServerLayout" Identifier "Default Layout" Screen 0 InputDevice InputDevice EndSection Section "Files" RgbPath ModulePath FontPath FontPath EndSection Section "Module" Load Load Load Load Load Load Load EndSection "Screen0" 0 0 "Mouse0" "CorePointer" "Keyboard0" "CoreKeyboard"
"/usr/share/X11/rgb" "/usr/lib64/xorg/modules" "unix/:7100" "built-ins"
"dbe" "extmod" "fbdevhw" "glx" "record" "freetype" "type1"
Section "ServerFlags" Option "DontZap" "yes" Option EndSection "DontVTSwitch" "yes"
Section "InputDevice" # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) # Option "Xleds" "1 2 3" # To disable the XKEYBOARD extension, uncomment XkbDisable. # Option "XkbDisable" # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use:
Page A-148
DOCUMENT N: 0029200000000MA07
Option
"XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use: # Option "XkbModel" "microsoft" # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # Option # or: # # # Option Option "XkbLayout" "XkbLayout" "XkbVariant" "de" "de" "nodeadkeys"
# If you'd like to switch the positions of your capslock and # control keys, use: # Option "XkbOptions" "ctrl:swapcaps" # Or if you just want both to be control, use: # Option "XkbOptions" "ctrl:nocaps" # Identifier Driver Option Option EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option Option Option Option EndSection Section "Monitor" Identifier VendorName ModelName HorizSync VertRefresh "Monitor0" "Unknown" "DFP-1" 31.5 - 150.0 50.0 - 90.0 "Protocol" "IMPS/2" "Device" "/dev/input/mice" "ZAxisMapping" "4 5" "Emulate3Buttons" "yes" "Keyboard0" "kbd" "XkbModel" "pc105" "XkbLayout" "us_intl"
ModeLine "2048x2048" 327.2 2048 2088 2408 2816 2048 2051 2054 2114 +hsync +vsync Option
"UseEDID" "FALSE"
DOCUMENT N: 0029200000000MA07
Option Option EndSection Section "Device" Identifier Driver VendorName BoardName Screen EndSection Section "Screen" Identifier Device Monitor DefaultDepth Option Option Option Option Option Option SubSection Depth EndSubSection EndSection
"ExactModeTimingsDVI" "TRUE" "UseEdidFreqs" "false"
"Videocard0" "nvidia" "NVIDIA Corporation" "Quadro FX 3700" 0
"Screen0" "Videocard0" "Monitor0" 8 "UseDisplayDevice" "DFP-1" "TwinViewOrientation" "LeftOf" "NoRenderExtension" "TRUE" "Dac8Bit" "TRUE" "TwinView" "0" "Metamodes" "DFP-1: 2048x2048 +0+0" "Display" 8
FDP, SDP, RDCU, DRF - KVM monitor # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: 18:55:42 PST 2007 version 1.0 (buildmeister@builder26) Thu Dec 13
# XFree86 4 configuration created by pyxf86config Section "ServerLayout" Identifier "Default Layout" Screen 0 InputDevice InputDevice "Screen0" 0 0 "Mouse0" "CorePointer" "Keyboard0" "CoreKeyboard"
Page A-150
DOCUMENT N: 0029200000000MA07
EndSection Section "Files" # RgbPath is the location of the RGB database. Note, this is the name of the # file minus the extension (like ".txt" or ".db"). There is normally # no need to change the default. # Multiple FontPath entries are allowed (they are concatenated together) # By default, Red Hat 6.0 and later now use a font server independent of # the X server to render fonts. RgbPath "/usr/X11R6/lib/X11/rgb" FontPath "unix/:7100" EndSection Section "Module" Load Load Load Load Load Load Load EndSection
"dbe" "extmod" "fbdevhw" "glx" "record" "freetype" "type1"
Section "InputDevice" # Specify which keyboard LEDs can be user-controlled (eg, with xset(1)) # Option "Xleds" "1 2 3" # To disable the XKEYBOARD extension, uncomment XkbDisable. # Option "XkbDisable" # To customise the XKB settings to suit your keyboard, modify the # lines below (which are the defaults). For example, for a non-U.S. # keyboard, you will probably want to use: # Option "XkbModel" "pc102" # If you have a US Microsoft Natural keyboard, you can use: # Option "XkbModel" "microsoft" # # Then to change the language, change the Layout setting. # For example, a german layout can be obtained with: # Option
"XkbLayout"
"de"
Page A-151
DOCUMENT N: 0029200000000MA07
# or: # Option
"XkbLayout"
"de"
# Option "XkbVariant" "nodeadkeys" # # If you'd like to switch the positions of your capslock and # control keys, use: # Option "XkbOptions" "ctrl:swapcaps"
# Or if you just want both to be control, use: # Option "XkbOptions" "ctrl:nocaps" # Identifier Driver Option Option EndSection Section "InputDevice" Identifier Driver Option Option Option Option EndSection Section "Monitor" Identifier VendorName ModelName HorizSync VertRefresh Option EndSection Section "Device" Identifier Driver VendorName BoardName EndSection "Mouse0" "mouse" "Protocol" "IMPS/2" "Device" "/dev/input/mice" "ZAxisMapping" "4 5" "Emulate3Buttons" "yes" "Keyboard0" "kbd" "XkbModel" "pc105" "XkbLayout" "us_intl"
"Monitor0" "Monitor Vendor" "LCD Panel 1024x768" 31.5 - 67.0 50.0 - 75.0 "dpms"
"Videocard0" "nvidia" "Videocard vendor" "NVIDIA Unknown (generic)"
Page A-152
DOCUMENT N: 0029200000000MA07
Section "Screen" Identifier Device Monitor DefaultDepth SubSection Viewport Depth Modes EndSubSection EndSection
"Screen0" "Videocard0" "Monitor0" 8 "Display" 0 0 8 "1024x768
Page A-153
DOCUMENT N: 0029200000000MA07
4.3
Software Security
The objective is to get a backup of each component using a clear notation and keeping the necessary information to restore their functionality when necessary. From the folder /local/india/****/exec, get a copy of each component. The name of the component will be considered when defining the backup. For instance, to carry out the backup corresponding to the SDD1:
<hostname># cd /local <hostname># tar -cvf FDPx.indiax.tar india
OPE for the case of Operational and x is the FDP number corresponding to the computer on which
the application has been copied.

<hostname># gzip -9 -v FDPx.indiax.tar
It compresses the file and gives the extension .gz: FDPx.indiax.tar.gz. At the same time, it contains: Get a copy of /etc/passwd for every type of computer:
<hostname># rcp p /etc/passwd <hostname or IP>:/etc
Get a copy of /etc/hosts.

<hostname># rcp p /etc/hosts <hostname or IP>:/etc
There is one case for which more than one backup must be carried out; this special case is DBM_MTO. The steps to follow are: Stop the Database operation to avoid inconsistence about data. (Stop the application). Execute the following commands:
<hostname># tar -cvf DBM.indiax.pgsql.tar /var/lib/pgsql <hostname># tar -cvf DMB.indiax.tar /local/india
Once these four steps are accomplished, all the application of the DBM_MTO subsystem will be kept in two files.
Page A-154
DOCUMENT N: 0029200000000MA07
4.4
Diagnostics and errors
4.4.1 Processes in the components

To check the processes, refer to the detailed description of software elements chapter and for each component.
4.4.2 Error messages 4.4.2.1 SDD

Messages on the SYSTEM MSG window. Next, the whole set of diagnostic and error messages, together with their meaning, concerning to the SDD will be shown. By pressing the [SYS MSG] button of the SDD messages will appear: , the window displaying all these
Diagnostic and Error messages: REMARK: When the text of a message is self-explained, the MEANING column does not offer any repetitive information.
MESSAGE Minimum Range %d Nm Maximum Range %d Nm Decentering Limit Reached Error Activating Aid (HFS) Extrapolation Time Out Of Range (HFS) Error Activating Aid (VFS) Extrapolation Time Out Of Range (VFS) Number Maximum Areas Exceeded
DESCRIPTION Minimum Range (in nautical miles) Maximum Range (in nautical miles)
Activation error concerning Horizontal Future Situation window (HFS) Time out of Range: the HFS cannot be opened Activation error concerning Vertical Future Situation window (VFS) Time out of Range: the VFS cannot be opened The number of areas have been exceeded
Page A-155
DOCUMENT N: 0029200000000MA07
MESSAGE LMG Operation Not Allowed Maximum Offline Line Fpcp Not Active Time-Out Expired Off Route Point Off Airspace Point Route Modification Error RBL Alarm Function Disabled Actual Request Cursor (HFS) Track Not Hooked (VFS) Inactive Primary Not Hooked Activation Not Position Lower Than Number Of
DESCRIPTION Forbidden operation concerning the creation of local maps Points Excessive number of points concerning the LMG (its maximum value is 512) Line off The Flight Plan Conflict Probe function is not activated Out of time The point does not belong to the route The point is out of the FIR Modification error concerning Flight Plans The LAD alarm is not activated
Exceeded (LMG)
Possible Position error concerning the cursor on the HFS window The track to present the VFS window is not selected
The primary track is not selected
Interconsole Marker Activation Not The activation of the inter-console marker is not possible Possible QNH/Tl Changed RDP Down RDP Up FDP Down Atis Info Changed Airmet Info Changed Metar Info Changed Sigmet Info Changed Speci Info Changed Taf Info Changed AITS modified QNH/Transition Level is changed
Page A-156
DOCUMENT N: 0029200000000MA07
MESSAGE Area Rest Cancel Area Rest Activated Clear Zone Met Make Zone Met Impossible Manual Correlation Manual Distribution Error LMG Operation Cancellation Cancelled Restricted Area Activated Restricted Area Operation Not Finished Meteoradar Lack Not Primary Track
DESCRIPTION Cancellation of restricted area Activation of restricted area Erasure of meteorological zone Creation of meteorological zone
The creation process concerning local maps is cancelled
Data from the meteorological radar does not arrive
Table 4-1: SDD Error Messages
4.4.2.2 FDD
Next, the whole set of diagnostic and error messages, together with their meaning, concerning to the FDD will be shown. Meaning of Diagnostic and Error messages: REMARK: When the text of a message is perfectly understandable, the MEANING column does offer any repetitive information.
MESSAGE Compulsory Syntactic New Call Sign in Use Rank Error Unknown Element Error Field Element Not Accessible Incoherence Discontinuity
DESCRIPTION Mandatory field Syntactic error
There is an error in a field
Incoherence concerning a route Discontinuity concerning a route
Page A-157
DOCUMENT N: 0029200000000MA07
MESSAGE FIR Time Not Computable Boundary Point Expected Validate Boundary Point Impossible Modify ETD Too Segments Too Points Extraction Error Too Sectors Message Not Allowed Incoherent FP Date Incoherent PPL Date Already in Use Area Not Found Area Already Existing Error in Field Flight Plan Already Exist Full File Inaccessible FP Tx msg not permitted Error: Line is Offline Queuing Not Allowed Error: Queue is Full None Found No Response Notam already exist Notam not exist Unknown Message Type Illegal Shape Printer Unavailable
DESCRIPTION The FIR time is not correct
Too many segments Too many points
Too many sectors
Transmission not allowed Error: The line is off
The shape of the area is not allowed
Page A-158
DOCUMENT N: 0029200000000MA07
MESSAGE No Data Available Exceeded Capacity Illegal Modify of Active Area Restriction not exist Erroneous flow element Range error No exists fp Fp not unique Fp already assigned to slot Unknown element flow Not element overflown flow Fp without slot Different flow elements for each fp Times overlapping Restriction already exists Error in beginning and end Error in channel information Times are overlapped There is no flight plan
DESCRIPTION
The modification of the active area is not allowed There is no restriction Erroneous flight element
The flight is already assigned to a slot The flow element is unknown No flight element is overflied The flight plan has no slot
There is an error at the beginning and at the end There is an error in the information channel
Received number more than The AFTN message was received with a SORTING NUMBER that is bigger (in ten units) than excepted 10 from expected Received number less than The AFTN message was received with a SORTING NUMBER that is lower than excepted expected Unknown address Error originator indicator AFTN no exists Mistake in address Table 4-2: FDD Error Messages There is an indicator about the origin of the error There is Network no Aeronautical Fixed Telecommunications
4.4.2.3 DRF
Next, the whole set of diagnostic and error messages, together with their meaning, concerning to the DRF will be shown.
DOCUMENT N: 0029200000000MA07
Diagnostic and Error messages: REMARK: When the text of a message is perfectly understandable, the MEANING column does not offer any repetitive information.
MESSAGE Data Losing Formatting Tape Start Record Process Tape Not Loaded, Insert Tape Protected Tape Type Formatting Error Data in Tape Tape Play Error Full Tape Tape Writing Error Beginning/End Record Error No Data in Disk Not Formatted Tape No Data in DAT Not Available Data in DAT DAT Recovery Error Too Files Beginning/End Load Error Data Discontinuity Playback Error Playback End Data Not Available in Disk
DESCRIPTION There is a loss of data
The recording process is starting
Error concerning the format process
Error concerning playback process on tape
Error concerning the writing process on tape Error at the beginning or ending of the recording process There is no data on the disc The tape is not conveniently formatted There is no data on the DAT tape
Error concerning the recovery process on the DAT tape Too many files Error at the beginning or ending of the loading process There is a discontinuity concerning data
The playback process is finished There is no data available in the disk. Table 4-3: DRF Error Messages
Page A-160
DOCUMENT N: 0029200000000MA07
5 Kickstart Administration Guide

5.1 Introduction
Kickstart is an installation process of Red Hat Enterprise Linux by nfs net. At server, the structure of KICKSTART starts in /KICKSTART_INDIA/ folder. The most important directories in this folder are:
/KICKSTART_INDIA/CONFIG, it contains the applications to install and create backup of the
machines. In this folder there is also a configuration file for kickstart process. Normally, the name of this file will be INDIA (it contains all the machines of the network and the role of each one).
/KICKSTART_INDIA/kickstart_RHEL5_U1/kickstart/, this directory contains the drivers of all
the machines and the backup files that we had created, Kickstart will use the backup to install the application after linux installation. ++ /KS_SERVER
/KS_SERVER/CONFIG CONFIG.exe BKP_APP.exe war COMMON war To install machines To create backups File contain machines list Drivers Folder Contains Backup & Instalation files BACKUPS Folder created by BKP_APP.exe <DD_MM_YY> Backup Date OPERATIONAL
kickstart_RHEL5_U1 kickstart
war
OPERATIONAL SIMULATION
SIMULATION Folder created by CONFIG.exe
Figure 5-1: KickStart Directories
5.2
Procedure to configure a working position as Kickstart server
To configure a working position as a Kickstart server, it is required that compress the backup folder /KICKSTART_INDIA, and copy the compressed folder to the desire machine.
[root<hostname>]# tar cf KICKSTART_INDIA.tar /KICKSTART_INDIA [root@<hostname>]# gzip -9 v KICKSTART_INDIA.tar [root@<hostname>]# rcp p KICKSTART_INDIA.tar.gz <hostname>:/
In the destination machine, we need to uncompress the backup, and create the following links.
[root@<hostname>]# gunzip KICKSTART_INDIA.tar.gz [root@<hostname>]# tar -xvf KICKSTART_INDIA.tar
Page A-161
DOCUMENT N: 0029200000000MA07
Now, we need to install the services from /KICKSTART_INDIA/CONFIG/SERVICES folder, which kickstart server must required to work. Before this, we must uninstall some preinstalled services.
[root@<HOSTNAME>12 /]# cd /KICKSTART_INDIA/CONFIG/SERVICES/ [root@<HOSTNAME>12 SERVICES]# rpm qa | grep i dhclient dhclient-3.0.5-7.el5 [root@<HOSTNAME>12 SERVICES]# rpm e -nodeps dhclient-3.0.5-7.el5 [root@<HOSTNAME>12 SERVICES]# rpm ivh dhcp-3.0.1-58.EL4.x86_64.rpm [root@<HOSTNAME>12 SERVICES]# rpm ivh dhcp-devel-3.0.1-58.EL4.x86_64.rpm [root@<HOSTNAME>12 SERVICES]# rpm ivh dhcpv6-0.10-14_EL4.x86_64.rpm
[root@<HOSTNAME>12 SERVICES]# rpm qa | grep i tftp tftp-0.42-3.1 [root@<HOSTNAME>12 SERVICES]# [root@<HOSTNAME>12 SERVICES]# [root@<HOSTNAME>12 SERVICES]# rpm e tftp-0.42-3.1 rpm ivh tftp-0.39-1.x86_64.rpm rpm ivh tftp-server-0.39-1.x86_64.rpm
After installing all the required services, we need to active the following services to be init by default when the machine starts-up.
5.2.1 NFS Service

Entitle the service for the machine is active as a server, sharing the resource /image
[root@<HOSTNAME>12 ~]# chkconfig --list | grep -i nfs nfs 0:off 1:off 2:off 3:off 4:off [root@<HOSTNAME>12 ~]# chkconfig --level 2345 nfs on [root@<HOSTNAME>12 ~]# chkconfig --list | grep -i nfs nfs 0:off 1:off 2:on 3:on 4:on 5:off 5:on 6:off 6:off
5.2.2 DHCP Service

[root@<HOSTNAME>12 ~]# chkconfig --list | grep -i dhcpd dhcpd 0:off 1:off 2:off 3:off 4:off 5:off [root@<HOSTNAME>12 ~]# chkconfig --level 0123456 dhcpd on [root@<HOSTNAME>12 ~]# chkconfig --list | grep -i dhcpd dhcpd 0:on 1:on 2:on 3:on 4:on 5:on 6:off 6:on
5.2.3 TFTP Service

[root@<HOSTNAME>12 ~]# chkconfig --list | grep -i tftp tftp: off [root@<HOSTNAME>12 ~]# chkconfig --level 0123456 tftp on [root@<HOSTNAME>12 ~]# chkconfig --list | grep -i tftp tftp: on
Above procedures are the steps to prepare a machine as a kicktstart server, but it will not work until we execute the installation application (i.e. CONFIG.exe) for the first time, after this whenever we start the server all the services will be start automatically and all the machines can be installed from this kickstart server, because we already add all the required services in the startup of machine.
Page A-162
DOCUMENT N: 0029200000000MA07
5.2.4 Procedure to configure Kickstart to install & create BACkUP of the machines
It is required to perform the following steps in Kickstart server:
5.2.4.1 Edit INDIA configuration file:

Goto the the directory /KICKSTART_INDIA/CONFIG/ and create a new file with name INDIA with the following format: <MAC ADDRESS> <hostname> <LOCATION>/<ROLE> <S/W> <LANGUAGE> 00:22:64:F9:24:5E <hostname> OPERATIONAL/FDP1 S US
<MAC_ADDRESS> Physical address of eth0 card of the machine. <hostname> Name to give the machine. <LOCATION> Working area of the machine (OPERATIONAL or SIMULATION). <ROLE> Role of the machine in the network. <S/W> Type of machine partition (S) Raid (W) non Raid. <LANGUAGE> Language for machine and keyboard.
[root@<hostname>~]# cd /KICKSTART_INDIA/CONFIG/ [root@<hostname>CONFIG]# vi INDIA
00:22:64:F9:24:5E <hostname> OPERATIONAL/FDP1 S US 00:1E:0B:76:93:36 <hostname> 00:1E:0B:76:A8:9C <hostname> 00:21:5A:F4:BB:D8 <hostname> 00:22:64:2A:0B:06 <hostname> 00:22:64:F9:25:00 <hostname> 00:10:18:48:17:5C <hostname> 00:10:18:48:17:6A <hostname> 00:1E:0B:76:A8:E8 <hostname> 00:10:18:34:66:16 <hostname> 00:10:18:48:17:A4 <hostname> 00:10:18:48:18:94 <hostname> 00:10:18:48:17:7A <hostname> OPERATIONAL/FDP2 S US OPERATIONAL/RDP1 S US OPERATIONAL/RDP2 S US OPERATIONAL/RDCU1 S US OPERATIONAL/RDCU2 S US OPERATIONAL/DRF1 S US OPERATIONAL/DRF2 S US OPERATIONAL/TDR S US OPERATIONAL/DBM_GTI S US OPERATIONAL/SDD1 S US OPERATIONAL/SDD2 S US SIMULATION/DBM_GTI W US
This file is necessary for kickstart process to install or take backup of the machines.
5.2.4.2 How to install machines with Kickstart

We have done all the necessary jobs to make a complete and working Kickstart server, and now we have to execute the installation file to install operating system and ATM application from the backup if exist.
[root@<HOSTNAME>12 /]# cd /KICKSTART_INDIA/CONFIG/ [root@<HOSTNAME> CONFIG]# ./CONFIG.exe INDIA The installation procedure will be under Red Hat Enterprise Linux 5 Update 1 Do you want continue?? (y/n)
Page A-163
DOCUMENT N: 0029200000000MA07
Checking INDIA file... ----------------------------File INDIA correct ----------------------------File /etc/dhcpd.conf saved as /etc/dhcpd.conf.old Do you want to do a BACKUP of all POSITIONS before the installation destroy all data on disk? (y/n): (Type [q] to abort the installation) n -----------------------------------------------------------------The BACKUP file will be installed from <DD_MM_YY> directory if exists the position. -----------------------------------------------------------------Do you want continue with the configuration kickstart? (y/n): y Cleaning Files and Directories... -------------------------------Generating dhcpd.conf in <hostname>... --------------------------------------------------------------Generanting ks.cfg for <hostname> -------------------------------Generating pxelinux.cfg for INDIA proyect to india1 -------------------------------Generanting ks.cfg for <hostname> -------------------------------Generating pxelinux.cfg for INDIA proyect to <HOSTNAME>2 -------------------------------Generanting ks.cfg for <hostname> -------------------------------Generating pxelinux.cfg for INDIA proyect to <HOSTNAME>3 Etc -------------------Starting Services... ------------------------------------------Starting TFTP service ... -------------------------------------------------Re-starting NFS service ... ------------------------------------------------------Re-starting dhcpd service ... -----------------------------
Page A-164
DOCUMENT N: 0029200000000MA07
5.3
How to Kickstart Start-up in a Client Machine:
After those steps are performed, reset the client machine and start-up by LAN card for the automatic installation. It is recommended that always use eth0 as a default card for installation. For Servers ProLiant DL380 G5, DL380 G6 or DL580 G5 Reset the server. Press F12 to start-up through PXE. (take eth0 automatically). For Workstations xw4600, xw6600, Z400 or Z200 Reset the workstation. Press F12 to start-up through PXE. Select First Selection to eth0 After operating system installation, if we have a backup in kickstart server for this position then it will install ATM application also. If we dont have backup of the AIRCON application for this position then first we must to create backup from the kickstart backup tool or manually from an other computer.
5.4
How to Create Backup from Kickstart
This procedure is to create a complete backup of AIRCON application of all the machines through kickstart backup tool. Following example is a part of complete backup process, showing only the information of first machine, but the backup is for all systems, because we used the INDIA file which contains all the machines.
[root@<HOSTNAME> /]# cd /KICKSTART_INDIA/CONFIG/ [root@<HOSTNAME> CONFIG]# ./BKP_APP.exe INDIA Do you want to do a BACKUP of all POSITIONS before the installation destroy all data on disk? [y/n]: y Checking INDIA file... --------------------INDIA file correct --------------------Starting... --------------------------------------Starting Backup of <HOSTNAME>X... MESSAGE : The /etc/rc3.d/S99start file of <hostname> were copied to /image/kickstart/INDIA/BACKUPS/<DD_MM_YY>/OPERATIONAL/FDP1 directory MESSAGE : The /etc/hosts file of <hostname> were copied to /image/kickstart/INDIA/BACKUPS/<DD_MM_YY>/OPERATIONAL/FDP1 directory
Page A-165
DOCUMENT N: 0029200000000MA07
MESSAGE : The /etc/passwd file of <hostname> were copied to /image/kickstart/INDIA/BACKUPS/<DD_MM_YY>/OPERATIONAL/FDP1 directory MESSAGE : The /etc/shadow file of <hostname> were copied to /image/kickstart/INDIA/BACKUPS/<DD_MM_YY>/OPERATIONAL/FDP1 directory MESSAGE : The /etc/ntp.conf file of <hostname> were copied to /image/kickstart/INDIA/BACKUPS/<DD_MM_YY>/OPERATIONAL/FDP1 directory MESSAGE : The /etc/licenses.df file of <hostname> were copied to /image/kickstart/INDIA/BACKUPS/<DD_MM_YY>/OPERATIONAL/FDP1 directory MESSAGE : The /etc/X11/xorg.conf file of <hostname> were copied to /image/kickstart/INDIA/BACKUPS/<DD_MM_YY>/OPERATIONAL/FDP1 directory MESSAGE : File FDP1.<HOSTNAME>1.tar.gz changed as FDP1.<HOSTNAME>1.tar.gz.old MESSAGE : saving /local directory to <hostname>... 82.3% 36509+1 records in 36509+1 records out 18693097 bytes (19 MB) copied, 13.2873 seconds, 1.4 MB/s FDP1 to <hostname> saved as /image/kickstart/INDIA/BACKUPS/<DD_MM_YY>/OPERATIONAL/FDP1/FDP1.<HOSTNAME>1.tar. gz --------------------------------------Linking to CURRENT_VERSION
If we want to take a backup of one machine or some machines then we must create another file like INDIA and put only the information of those machines which we want to crearte backup.
Page A-166
DOCUMENT N: 0029200000000MA07
5.5 Folders and important Kickstart files 5.5.1 Folder /image/kickstart/INDIA/BACKUPS/<DD_MM_YY>/[OPERATIONAL] [SIMULATION]/position
All the backups contains the following files: hosts, passwd, shadow, ntp.conf, xorg.cong, S99start, FDP1.<HOSTNAME>1.tar.gz hosts file: The hosts file is used to connect the client machine with other machine without the destination machine IP (this file relates hostnames and machine IPs).
Example:
or
# Do not remove the following line, or various programs # that require network functionality will fail. 127.0.0.1 ::1 localhost.localdomain localhost localhost6.localdomain6 localhost6
######## LAN 1 ############################################### 10.160.77.1 10.160.77.2 10.160.77.3 10.160.77.4 . . . . 10.160.77.###
<hostname> <hostname> <hostname> <hostname>
<hostname> X
######## LAN 2 ############################################### 10.161.77.1 10.161.77.2 10.161.77.3 10.161.77.4
<hostname> <hostname> <hostname> <hostname>
. . .
. . 10.161.77.XX### indiaX-2
####### PRINTERS #######################
Page A-167
DOCUMENT N: 0029200000000MA07
10.160.77.151
<hostname_lp>
####### SWITCHES ####################### 10.160.77.225 10.160.77.230 ####### NTP SLAVE 10.160.77.231 switch_1 ntp_server1 #################### ntp_slave1 ####### NTP SERVER ####################
xorg.conf file: This file is used for X-Windows configuration.

Example: # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 1.0 (buildmeister@builder26) Thu Dec 13 18:55:42 PST 2007 # Xorg configuration created by pyxf86config Section "ServerLayout" Identifier Screen InputDevice InputDevice EndSection Section "Files" RgbPath ModulePath FontPath FontPath EndSection Section "Module" Load Load Load Load Load Load Load EndSection "glx" "dbe" "extmod" "fbdevhw" "record" "freetype" "type1" "/usr/share/X11/rgb" "/usr/lib64/xorg/modules" "unix/:7100" "built-ins" 0 "Default Layout" "Screen0" 0 0 "Mouse0" "CorePointer" "Keyboard0" "CoreKeyboard"
Page A-168
DOCUMENT N: 0029200000000MA07
Section "ServerFlags" Option "DontZap" "yes" Option EndSection Section "InputDevice" Identifier Driver Option Option Option Option EndSection Section "InputDevice" Identifier "Keyboard0" Driver Option Option Option EndSection Section "Monitor" Identifier VendorName ModelName HorizSync VertRefresh Option EndSection Section "Device" Identifier Driver EndSection Section "Screen" Identifier Device Monitor DefaultDepth Option SubSection Viewport "Screen0" "Videocard0" "Monitor0" 8 "NoRenderExtension" "TRUE" "Display" 0 0 "Videocard0" "nvidia" "Monitor0" "Unknown" "Unknown" 30.0 - 110.0 50.0 - 150.0 "DPMS" "kbd" "XkbModel" "pc105" "XkbLayout" "us_intl" "XkbVariant" "intl" "Mouse0" "mouse" "Protocol" "auto" "Device" "/dev/input/mice" "Emulate3Buttons" "yes" "ZAxisMapping" "4 5" "DontVTSwitch" "yes"
Page A-169
DOCUMENT N: 0029200000000MA07
Depth EndSubSection EndSection
passwd file: This file is required to install the users in client machine.
Example: root:x:0:0:root:/root:/bin/bash bin:x:1:1:bin:/bin:/sbin/nologin daemon:x:2:2:daemon:/sbin:/sbin/nologin adm:x:3:4:adm:/var/adm:/sbin/nologin lp:x:4:7:lp:/var/spool/lpd:/sbin/nologin sync:x:5:0:sync:/sbin:/bin/sync shutdown:x:6:0:shutdown:/sbin:/sbin/shutdown halt:x:7:0:halt:/sbin:/sbin/halt mail:x:8:12:mail:/var/spool/mail:/sbin/nologin news:x:9:13:news:/etc/news: uucp:x:10:14:uucp:/var/spool/uucp:/sbin/nologin operator:x:11:0:operator:/root:/sbin/nologin games:x:12:100:games:/usr/games:/sbin/nologin gopher:x:13:30:gopher:/var/gopher:/sbin/nologin ftp:x:14:50:FTP User:/var/ftp:/sbin/nologin nobody:x:99:99:Nobody:/:/sbin/nologin dbus:x:81:81:System message bus:/:/sbin/nologin nscd:x:28:28:NSCD Daemon:/:/sbin/nologin vcsa:x:69:69:virtual console memory owner:/dev:/sbin/nologin rpc:x:32:32:Portmapper RPC user:/:/sbin/nologin amanda:x:33:6:Amanda user:/var/lib/amanda:/bin/bash apache:x:48:48:Apache:/var/www:/sbin/nologin sshd:x:74:74:Privilege-separated SSH:/var/empty/sshd:/sbin/nologin rpcuser:x:29:29:RPC Service User:/var/lib/nfs:/sbin/nologin nfsnobody:x:4294967294:4294967294:Anonymous NFS User:/var/lib/nfs:/sbin/nologin pcap:x:77:77::/var/arpwatch:/sbin/nologin avahi:x:70:70:Avahi daemon:/:/sbin/nologin ident:x:98:98::/home/ident:/sbin/nologin mailnull:x:47:47::/var/spool/mqueue:/sbin/nologin smmsp:x:51:51::/var/spool/mqueue:/sbin/nologin ntp:x:38:38::/etc/ntp:/sbin/nologin haldaemon:x:68:68:HAL daemon:/:/sbin/nologin rpm:x:37:37::/var/lib/rpm:/sbin/nologin hsqldb:x:96:96::/var/lib/hsqldb:/sbin/nologin pegasus:x:66:65:tog-pegasus OpenPegasus WBEM/CIM services:/var/lib/Pegasus:/sbin/nologin xfs:x:43:43:X Font Server:/etc/X11/fs:/sbin/nologin gdm:x:42:42::/var/gdm:/sbin/nologin
india:x:0:1:User india:/local/india/<SUBSYSTEM>/exec/:/usr/bin/ksh
shadow file: This file keeps every user's password in the client machine.
Example: root:$1$8kIfzi56$j.N9v0U8y0EjYP0uVX72S.:14151:0:99999:7:::
Page A-170
DOCUMENT N: 0029200000000MA07
bin:*:14151:0:99999:7::: daemon:*:14151:0:99999:7::: adm:*:14151:0:99999:7::: lp:*:14151:0:99999:7::: sync:*:14151:0:99999:7::: shutdown:*:14151:0:99999:7::: halt:*:14151:0:99999:7::: mail:*:14151:0:99999:7::: news:*:14151:0:99999:7::: uucp:*:14151:0:99999:7::: operator:*:14151:0:99999:7::: games:*:14151:0:99999:7::: gopher:*:14151:0:99999:7::: ftp:*:14151:0:99999:7::: nobody:*:14151:0:99999:7::: dbus:!!:14151:0:99999:7::: nscd:!!:14151:0:99999:7::: vcsa:!!:14151:0:99999:7::: rpc:!!:14151:0:99999:7::: amanda:!!:14151:0:99999:7::: apache:!!:14151:0:99999:7::: sshd:!!:14151:0:99999:7::: rpcuser:!!:14151:0:99999:7::: nfsnobody:!!:14151:0:99999:7::: pcap:!!:14151:0:99999:7::: avahi:!!:14151:0:99999:7::: ident:!!:14151:0:99999:7::: mailnull:!!:14151:0:99999:7::: smmsp:!!:14151:0:99999:7::: ntp:!!:14151:0:99999:7::: haldaemon:!!:14151:0:99999:7::: rpm:!!:14151:0:99999:7::: hsqldb:!!:14151:0:99999:7::: pegasus:!!:14151:0:99999:7::: xfs:!!:14151:0:99999:7::: gdm:!!:14151:0:99999:7::: india:$1$XtyJ2Vnn$E1WiGoyyHlf5WCE6ZXr/F1:14152:0:99999:7:::
ntp.conf file File required for time synchronization of every machine. There are two cases: a machine is the NTP server, or an external GPS clock is connected to the net. With a machine being NTP server, there must be a file ntp.conf for server, and another one for the clients. In client machines, server's IP or hostnames are specified. With an external GPS clock, it is required that every machine has file ntp.conf in client version, where specify the clock's IP. Example of file ntp.conf for client machine.
Example: restrict default nomodify notrap noquery restrict 127.0.0.1 fudge 127.127.1.0 stratum 5 driftfile /var/lib/ntp/drift server ntp_server1 prefer
DOCUMENT N: 0029200000000MA07
server ntp_server2
Example of file ntp.conf for server machine (if available)

Example
# Permit time synchronization with our time source, but do not # permit the source to query or modify the service on this system. restrict default nomodify notrap noquery # Permit all access over the loopback interface. This could
# be tightened as well, but to do so would effect some of # the administrative functions. restrict 127.0.0.1
# -- CLIENT NETWORK ------# Permit systems on this network to synchronize with this # time service. Do not permit those systems to modify the Also, do not use those
# configuration of this service.
# systems as peers for synchronization. # restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap # --- OUR TIMESERVERS ----# --- NTP MULTICASTCLIENT --#multicastclient # listen on default 224.0.1.1
# restrict 224.0.1.1 mask 255.255.255.255 nomodify notrap # restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap # --- GENERAL CONFIGURATION --# # Undisciplined Local Clock. This is a fake driver intended for backup # and when no outside source of synchronized time is available. The # default stratum is usually 3, but in this case we elect to use stratum # 0. Since the server line does not have the prefer keyword, this driver # is never used for synchronization, unless no other other # synchronization source is available. In case the local host is # controlled by some external source, such as an external oscillator or # another protocol, the prefer keyword would cause the local host to # disregard all other synchronization sources, unless the kernel # modifications are in use and declare an unsynchronized condition. # server 127.127.1.0
Page A-172
DOCUMENT N: 0029200000000MA07
fudge 127.127.1.0 stratum 10 # # Drift file. Put this in a directory which the daemon can write to.
# No symbolic links allowed, either, since the daemon updates the file # by creating a temporary in the same directory and then rename()'ing # it to the file. # driftfile /var/lib/ntp/drift broadcastdelay # # Keys file. If you want to diddle your server at run time, make a 0.008
# keys file (mode 600 for sure) and define the key number to be # used for making requests. # # PLEASE DO NOT USE THE DEFAULT VALUES HERE. Pick your own, or remote # systems might be able to reset your clock at will. Note also that # ntpd is started with a -A flag, disabling authentication, that # will have to be removed as well. # keys /etc/ntp/keys
broadcastclient
S99start file: This file contains the necessary commands for automatic startup when machine starts.
#!/bin/sh cd /local/india /local/india/m_search_keys cd su - india
FDP1.<HOSTNAME>1.tar.gz file File that contains a backup of INDRA's application.
5.5.2 Folder /image/kickstart/COMMON

Contains the drivers and files required to finish and configure the machines after the Kickstart has finished the installation of the Operative System.
Drivers: crypt: File that de-encrypts the user files of INDRA's application. nsswitch.conf:
Page A-173
DOCUMENT N: 0029200000000MA07
FarSite.3.03-09_RHEL5.tar.gz: Driver for Farsite X.25 card. DigiNeo.1.3.-15_RHEL5.tar.gz: Driver for RS-232 Digi Neo card. PCI334A.7.4_RHEL5.tar.gz: Driver for PCI334A card. NVIDIA-Linux-x86_64-190.07-pkg2.run: Driver for NVIDIA. CUPS_SFW: Driver of Laser printer. isode.RHEL5.tar.gz: libraries for FDP. POSTGRESQL: Libraries for POSTGRES user. RPMs: e1000-7.6.15a-1.x86_64.rpm: e1000 package. Scripts: S05disable-services: Inhibit the unnecessary services. S05enable-services: S99enable-NTP: S99FarSync-driver:
Active the necessary services. Active the ntp. Script used to install the driver for Farsite X.25 card. It requires the file FarSite.3.03-09_RHEL5.tar.gz.
S99DigiNeo-driver: S99PCI334A-driver:
Script used to install the driver for RS-232 Digi Neo card. It requires the file DigiNeo.1.3.-15_RHEL5.tar.gz. Script used to install the driver for PCI334A card. It requires the file PCI334A.7.4_RHEL5.tar.gz.
S99MPS1000-driver: S99NVIDIA-driver:
Script used to install the driver for MPS1000 server. It requires the file MPS1000_LINUX_DRIVER_KS.tar.gz. Script used to install the driver for NVIDIA. It requires the file NVIDIALinux-x86_64-169.07-pkg2.run
5.5.3 File /root/postinstall.log

This file is created in client machine after the installation is finished, and it includes every error and incidents relative to installed packages (as drivers and additional software). If file is empty, it means that the installation finished correctly and with no incidents.
5.6
Procedure to inhibit a machine as Kickstart server
If some machines are configured as Kickstart server, it may cause conflicts when a client is installed. It is recommended that only a position is the Kickstart server. For this propose, inhibit certain services and deinstall additional packages (specific packages to configure the position as Kickstart).
5.6.1 File /etc/exports

Edit the file /etc/exports and remove the following line:
/image *(ro,sync,no_root_squash)
This will erase the shared resource /image from the net. The following sentences must be executed to restart the nfs service:
DOCUMENT N: 0029200000000MA07
[root@<hostname>
Shutting Shutting Shutting Shutting
down down down down
NFS NFS NFS NFS
~]# service nfs stop mountd: daemon: quotas: services:
[ [ [ [
OK OK OK OK
] ] ] ]
Inhibit the service for the machine never try to share any net resource.
[root@<HOSTNAME>1 ~]# chkconfig --list | grep -w nfs nfs 0:off 1:off 2:on 3:on 4:on [root@<HOSTNAME>1 ~]# chkconfig --level 2345 nfs off [root@<HOSTNAME>1 ~]# chkconfig --list | grep -w nfs nfs 0:off 1:off 2:off 3:off 4:off 5:on 5:off 6:off 6:off
5.6.2 DHCP service

By default every machine is installed without dhcp server, and it is recommended to restore a machine to its original status. First stop dhcp services and after deinstall every package for configurate the Kickstart server. Manually stop the service performing the following line:
[root@<hostname>
~]# service dhcpd stop Shutting down dhcpd:
[OK]
Inhibit the permanent service in the start-up of the machine.

[root@<hostname> ~]# chkconfig --list | grep -w dhcpd
dhcpd 0:on 1:on 2:on 3:on 4:on 5:on [root@<hostname> ~]# chkconfig --level 0123456 dhcpd off [root@<hostname> ~]# chkconfig --list | grep -w dhcpd dhcpd 0:off 1:off 2:off 3:off 4:off 5:off
6:on 6:off
Optionally, proceed to deinstall:

[root@<hostname> ~]# rpm -qa | grep -i dhcp
dhcpv6-0.10-14_EL4 dhcp-devel-3.0.1-58.EL4 dhcp-3.0.1-58.EL4 dhcpv6_client-0.10-14_EL4 [root@<hostname> ~]# rpm -e dhcp-devel-3.0.1-58.EL4 [root@<hostname> ~]# rpm -e dhcp-3.0.1-58.EL4 Warning: /var/lib/dhcp/dhcpd.leases saved as /var/lib/dhcp/dhcpd.leases.rpmsave Warning: /etc/dhcpd.conf saved as /etc/dhcpd.conf.rpmsave [root@<hostname> ~]# rpm -e dhcpv6-0.10-14_EL4 [root@<hostname> ~]# rpm -qa | grep -i dhcp dhcpv6_client-0.10-14_EL4
5.6.3 XINETD service

Inhibit the service for it never starts the service by default.
[root@<hostname> tftp: [root@<hostname> [root@<hostname> tftp: on ~]# chkconfig --level 0123456 tftp off ~]# chkconfig --list | grep -i tftp off ~]# chkconfig --list | grep -i tftp
Page A-175
DOCUMENT N: 0029200000000MA07
Optionally, deinstall the system's tftp.

[root@<hostname> tftp-server-0.39-1 tftp-0.39-1 ~]# rpm -qa | grep -i tftp
[root@<hostname>
~]# rpm -e tftp-server-0.39-1
Warning: /etc/xinetd.d/tftp saved as /etc/xinetd.d/tftp.rpmsave
[root@<hostname> tftp-0.39-1
~]# rpm -qa | grep -i tftp
Manually restart the service to charge new data.

[root@<hostname> Stopping xinetd: Starting xinetd: ~]# service xinetd restart [ [ OK OK ] ]
Page A-176
DOCUMENT N: 0029200000000MA07
6 Communications Folder
In the same machine that we have kickstart server, we also have a directory named COMMUNICATIONS which contains two very useful directories to configure and maintain the communications between all the computers.
o /COMMUNICATIONS/INDIA/
6.1
/COMMUNICATIONS/india/ Folder
In this folder we have a very important file which is using all the computers for communication of AIRCON subsystems. The name of this file is CONFIG.COM and the tool which is used to distribute the new version and update the existing version is copy_CONFIG_COM.sh. # sh copy_CONFIG_COM.sh <CONFIG_COM file to copy> <project directory name>
[root@<hostname> ~]# cd /COMMUNICATIONS/INDIA/ [root@<hostname>]# sh copy_CONFIG_COM.sh CONFIG_COM.INDIA.v00.01 india
This is the procedure to install CONFIG_COM file on just OPERATIONAL systems. In DBM, we need to update CONFIG_COM manually. following are the steps:
[root@<hostname> [root@<hostname> ~]# cd /local/india/adap/exec/tcl_tk/ tcl_tk]# rm rf CONFIG_COM; ls n CONFIG_COM.INDIA.v00.01 CONFIG_COM
To verify that CONFIG.COM file is updated successfully in all the systems, we have another tool to check either CONFIG.COM is updated or not. # sh check_CONFIG_COM.sh <CONFIG_COM file to check> <project directory name>
[root@<hostname> [root@<hostname> ~]# cd /COMMUNICATIONS/INDIA/ india]# sh check_CONFIG_COM.sh CONFIG_COM.INDIA.v00.01 india
The CONFIG_COM file for SIMULATION system is different than CONFIG_COM file of OPERATIONAL. In SIMULATION machines we need session files also, SIMULATOR can not work without these sessions. The copy_CONFIG_COM.sh script will generate these files, before executing the script we must check the following things: Previous session files should not exist. In case they do exist, they must be deleted manually. The copy_CONFIG_COM.sh script requires an additional script in the same folder named m_change_CONFIG_COM.sh to create sessions, we dont need to execute this script but copy_CONFIG_COM.sh need this script to generate sessions automatically.
Page A-177
DOCUMENT N: 0029200000000MA07
Page A-178
DOCUMENT N: 0029200000000MA07
Appendix A - ABBREVIATIONS AND GLOSSARY OF TERMS A.1

AFTN ATC ATCC BYP RCC CMD CPL CPU DBM DRF FDD FDPS FIR FL FP FPL HMI LAN PCH PCN Plt PPL PSR RDP RDR RPL SDD SDP SSR TSP UTC VSP
List of Abbreviations
DEFINITION Aeronautical Fixed Telecommunications Network Air Traffic Control Air Traffic Control Centre BY-Pass operational mode Radar Communications Compressor Control and Monitoring Display Current Flight Plan Central Processing Unit Data Base Management Data Recording Facility Flight Data Display Flight Data Processing System Flight Information Region Flight Level Flight Plan Flight Plan Human Machine Interface Local Area Network Preliminary Flight Plan Change (AFTN message type) Preliminary Flight Plan Cancel (AFTN message type) Plot Preliminary Flight Plan Primary Surveillance Radar Radar Data Processing Radar Repetitive Flight Plan Situation Data Display Surveillance Data Processor Secondary Surveillance Radar Technical Supervisor Universal Time Coordinated Variable Parameter System
ABBREVIATIONS
Page A-179
DOCUMENT N: 0029200000000MA07
A.2
Glossary of Terms
Adaptation Set of data that are adapted and used by the system. Controller It is a person with an education and training adequate able to provide aerial transit services. Correlation It is the Assignation process (manual or automatic) of a flight plan to a track. This assignation is base on predefined criteria. Adaptation Data Set of values introduced in the system in order to control different types of processes (like the insertion of a flight plan in the PV list, alarms activation and inhibition, etc). Flight Plan Information provided to air traffic services relative to an intended flight, or fraction of it. Recording Coherent keeping process of data relative to general information concerning the system and local information concerning every SDD for a specific time period. Operative By-pass mode Operative mode that indicates that the radar data processing, which allows the presentation of the SDD, is performed by means of monoradar tracking in combination with the SDD processor. The information coming from the TPV is ignored. Variable Parameter of the System Configuration parameters the system can change on runtime. Plot Information relative to an aircraft that is received from a radar position. Plot of Test Radar information corresponding to a fix transponder. Workstation Combination of terminals working together and, usually, located in the same room. Radar A radio detection device that provides information about the distance, azimuth, and elevation of objects. Primary Surveillance Radar (PSR) This type of radar employs reflected radio signals for the detection of aircrafts. Secondary Surveillance Radar (SSR) This type of radar employs ground interrogators and airborne transponders to determine the position of an aircraft (range and azimuth). If codes and modes are used, the radar can determine identity and height as well.
DOCUMENT N: 0029200000000MA07
Playback This process allow a coherent access and display of any previously recorded data, any information provided to the Controller Positions (SDD) as well as the status of the configuration supplied to the same SDD. Monoradar Tracking Amount of information used by a computer for aircraft tracking purposes. This information is upgraded regularly and comes from a solely radar. Multiradar Tracking An amount of information used by a computer for aircraft tracking purposes. This information is the result of the combination of all monoradar tracks that represent the aircraft. Situation Data Display (SDD) Display on computer thanks to which the controllers can visualize both, the aircrafts and the radar pulses. Terminal The combination of a computer and a software application. A consistent union of several terminals makes up a workstation. Transponder On board electronic device that receives signals coming from ground interrogators and responds, when codes and modes are common, with a set of pulses. UNIX Operating System used by the system.
Page A-181
DOCUMENT N: 0029200000000MA07
This page left intentionally blank THIS IS THE LAST PAGE OF DOCUMENT
Page A-182

0029200000000ma07 2-0 Adm-Um

Diunggah oleh

Informasi Dokumen

Deskripsi Asli:

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

0029200000000ma07 2-0 Adm-Um

Diunggah oleh

Hak Cipta:

Format Tersedia

DOCUMENT N: 0029200000000MA07

Edition:2 Revision:0 Date: 1 November2010

Supply, Installation, Testing and Commissioning of Tower ATS Automation System

Indra Sistemas, S.A.

System Ad mi nist rato r User M a nua l

Edition:2 Revision:0 Date: 1 November2010

This page left intentionally blank

System Ad mi nist rato r User M a nua l

Edition:2 Revision:0 Date: 1 November2010

This page left intentionally blank

System Ad mi nist rato r User M a nua l

Edition:2 Revision:0 Date: 1 November2010

PAGE EDITION AND REVISION RECORD

System Ad mi nist rato r User M a nua l

Edition:2 Revision:0 Date: 1 November2010

This page left intentionally blank

System Ad mi nist rato r User M a nua l

Edition:2 Revision:0 Date: 1 November2010

REGISTER OF CHANGES TO THE DOCUMENT

DATE 2010-07-30 2010-11-02

AFFECTED PAGES All All First Edition Second Edition

REASON FOR CHANGE

System Ad mi nist rato r User M a nua l

Edition:2 Revision:0 Date: 1 November2010

This page left intentionally blank

System Ad mi nist rato r User M a nua l

Edition:2 Revision:0 Date: 1 November2010

Software Components Detailed Description ....................................................................... A-7 2.1.1 2.1.2 2.1.3

System Ad mi nist rato r User M a nua l

Edition:2 Revision:0 Date: 1 November2010

2.4.5.1 2.4.5.2 2.4.6 2.5 2.5.1 2.5.2

SDD configuration .....................................................................................A-40 SDD with FDD configuration ......................................................................A-41

System Ad mi nist rato r User M a nua l

Edition:2 Revision:0 Date: 1 November2010

RDFD processes .............................................................................................A-83

Finishing process.................................................................................................... A-101

System installation and maintenance ............................................................................. A-103

System Ad mi nist rato r User M a nua l

Edition:2 Revision:0 Date: 1 November2010

Base Software ........................................................................................................ A-103

System Ad mi nist rato r User M a nua l

Edition:2 Revision:0 Date: 1 November2010

5.2.1 5.2.2 5.2.3

Procedure to inhibit a machine as Kickstart server ................................................... A-174

Appendix A - ABBREVIATIONS AND GLOSSARY OF TERMS ............................................. A-179

System Ad mi nist rato r User M a nua l

Edition:2 Revision:0 Date: 1 November2010

This page left intentionally blank

System Ad mi nist rato r User M a nua l

Edition:2 Revision:0 Date: 1 November2010

Edition:2 Revision:0 Date: 1 November2010

System Ad mi nist rato r User M a nua l

Edition:2 Revision:0 Date: 1 November2010

System Ad mi nist rato r User M a nua l

Edition:2 Revision:0 Date: 1 November2010

This page left intentionally blank

System Ad mi nist rato r User M a nua l

Edition:2 Revision:0 Date: 1 November2010

General system overview

System Ad mi nist rato r User M a nua l

Edition:2 Revision:0 Date: 1 November2010

System Ad mi nist rato r User M a nua l