Technical System Overview

BUSINESS UNIT ATMAS UNCLASSIFIED E292-01-04739OH
Issue: A
Date: 03/08/06
Terminal Radar Approach Control (TRACON)

Project at the
DIOSDADO MACAPAGAL
International Airport CLARK
TECHNICAL SYSTEM OVERVIEW
CDRL No. :
SSDD Rev 03
ISSUED BY :
SELEX SISTEMI INTEGRATI S.p.A.

Via Tiburtina Km 12.400 - Roma
ITALY
The copyright in this document is the property of SELEX

SISTEMI INTEGRATI S.p.A. The document is supplied on the
express understanding that it is to be treated as confidential and
that it may not be copied, used or disclosed to others in whole or
in part for any purpose except as authorized in writing by
This document contains a total of 60 pages
UNCLASSIFIED Page 1
Issue: A
Date: 03/08/06
DOCUMENT SECURITY CLASSIFICATION:
Any person others the authorised holder upon obtaining possession of this document, by finding or
otherwise, should forward it by registered post, together with his name and address, in a sealed envelope to:
Ufficio Sicurezza
Via Tiburtina 12.400
00131 Rome
ITALY
Any questions arising from this document shall be addressed to:
Andrea Piscitelli
Air Traffic Management & Airport Systems
Via Tiburtina, Km 12.400 - 00131 Roma
ITALY
Telephone +39-06 4150-2408

Fax +39-06 4131133 / 4131436 / 4131091
UNCLASSIFIED Page 2
Issue: A
Date: 03/08/06
Issue Authority
Prepared by: ......................................................

Date:
(ILS Manager) (Andrea Piscitelli)
Approved by:
......................................................
(ILS Responsible) Date:
(L. Minicozzi)
Approved by:
......................................................
(Project Leader) Date:
(E. Luison)
UNCLASSIFIED Page 3
Issue: A
Date: 03/08/06
REVISIONS RECORD SHEET
This sheet is a record of revisions to this document.
Document Change Note

Issue/AL Date Revised Pages
(DCN)
A 03/08/06 First Issue N.A.
UNCLASSIFIED Page 4
Issue: A
Date: 03/08/06
LIST OF ABBREVIATIONS
ABBR. DESCRIPTION
ACO Automatic Change Over
APP Approach
ATC Air Traffic Control
BIT built-in test
COTS Commercial Off The Shelf
CWP Controller Working Position
DAIW Minimum Safe Altitude Warning
DARD Direct Access Radar Data
DPC Digital Pulse Compression
EXE Executive Controller Role
FAN False Alarm Normalization
FDP Flight Data Processor
FDPS Flight Data Processing System
FPDH Flight Progress Data Handling
GPS Global Positioning System
HCI Human Computer Interface
IFDH Initial Flight Data Handling
ISLS interrogation side lobe suppression
LAN Local Area Network
LCMS Local Control and Monitoring System
LCP Radar Local Control Panel
LVA Large Vertical Aperture
MRT Multi Radar Tracking
MSAW Dangerous Area Infringement Warning
MTCD Medium Term Conflict Detection
ONL On line
ORCAM Originating Region Code Assignment Method
PLB Playback
PLN Planner Controller Role
PSR Primary Surveillance Radar
RCMS Remote Control and Monitoring System
RHP Radar Head Processor
RMM Radar Maintenance Monitor
RPB Recording and Playback Processing
RSLS receiver side lobe suppression
SFPL System Flight Plan
SIR Secondary Surveillance Radar
SRT Single Radar Tracking
SSR Secondary Surveillance Radar
STCA Short Term Conflict Alert
TCA Traffic Conflict Alert
TWR Tower
UTC Universal Time Code
UNCLASSIFIED Page 5
Issue: A
Date: 03/08/06
TABLE OF CONTENTS
1. SYSTEM CONFIGURATION AND GENERAL PROVISION........................................3
1.1 SYSTEM ARCHITECTURE.............................................................................................................................3

1.1.1 RADAR SENSORS ...............................................................................................................................................6
1.1.2 DATA PROCESSING SUBSYSTEM ........................................................................................................................6
1.1.3 OPERATOR SUPPORT SUBSYSTEM ......................................................................................................................7
1.1.4 MONITORING, CONTROL & MAINTENANCE SUBSYSTEM ...................................................................................7
1.1.5 COMMUNICATION AND DATA NETWORK ...........................................................................................................7
1.2 RADAR HEAD EQUIPMENT .........................................................................................................................8

1.2.1 ANTENNA GROUP...............................................................................................................................................8
1.2.1.1 G-33 Antenna ................................................................................................................................................................... 8
1.2.1.2 ALE-9 LVA antenna......................................................................................................................................................... 9
1.2.1.3 Antenna Base.................................................................................................................................................................... 9
1.2.2 PRIMARY SURVEILLANCE RADAR (PSR) ...........................................................................................................9
1.2.3 SIR–S SECONDARY RADAR (MSSR)..............................................................................................................11
1.2.4 RADAR HEAD PROCESSOR (RHP)....................................................................................................................13
1.2.5 DGITAL CLOCK SYSTEM ..................................................................................................................................13
1.2.6 BIG DIP............................................................................................................................................................14
1.2.7 RADAR MAINTENANCE MONITOR (RMM) ......................................................................................................15
1.2.8 LOCAL CONTROL MONITORING SYSTEM (LCMS)...........................................................................................16
1.3 EOB TRACON EQUIPMENT ........................................................................................................................17

1.3.1 RADAR DATA CONTROLLER CONSOLE (TYPE A).............................................................................................17
1.3.2 CLEARANCE DELIVERY CONSOLE TYPE B .......................................................................................................18
1.3.3 FLIGHT DATA COORDINATOR CONSOLE TYPE C..............................................................................................18
1.3.4 MAINTENANCE POSITION CONSOLE TYPE E.....................................................................................................18
1.3.5 FOBS FDD TYPE F .........................................................................................................................................19
1.3.6 TOWER CONSOLE TYPE D.................................................................................................................................19
1.3.7 GENERAL NOTES ..............................................................................................................................................19
1.3.8 CONSOLE ITEMS DESCRIPTION ........................................................................................................................20
1.3.8.1 CDS-2000 Controller Working Position (CWP)............................................................................................................. 20
1.3.8.2 CDS-1000 Controller Working Position (CWP)............................................................................................................. 22
1.3.8.3 Communication Control Panel........................................................................................................................................ 22
1.3.8.4 Weather Instrument Display ........................................................................................................................................... 22
1.3.8.5 Digital Clock Display ..................................................................................................................................................... 22
1.3.8.6 Runway in use Indicator ................................................................................................................................................. 22
1.3.8.7 VFR/IFR Indicator.......................................................................................................................................................... 22
1.3.8.8 NAVAIDS Status Indicator ............................................................................................................................................ 23
1.3.8.8.1 ILS status indicator:..................................................................................................................................................... 23
1.3.8.8.2 DVOR, DME, NDB..................................................................................................................................................... 23
1.3.8.9 Illuminated Map Chart Display Panel............................................................................................................................. 23
1.3.8.10 Alarm Panel .................................................................................................................................................................. 23
1.3.8.11 VHF/UHF Aero Band Transceiver with battery back-up ............................................................................................. 24
1.3.8.12 VHF/UHF Commercial Band Transceiver with battery back-up.................................................................................. 24
1.3.8.13 Flight Data Plan Entry Terminal & Display ................................................................................................................. 24
1.3.8.14 Silent Strip Printer ........................................................................................................................................................ 24
1.3.8.15 Remote Control and Monitoring System ...................................................................................................................... 24
1.3.9 FLIGHT DATA PROCESSOR (FDP) ....................................................................................................................25
1.3.10 SAFETY NETS ................................................................................................................................................26
1.3.11 RECORDING AND PLAYBACK SYSTEM ...........................................................................................................26
UNCLASSIFIED Page 1
Issue: A
Date: 03/08/06
1.3.12 EVAPLOTTER ...............................................................................................................................................26

1.3.13 DIGITAL VOICE RECORDER ...........................................................................................................................27
1.3.14 RELOCATED VCSS ........................................................................................................................................27
2. SOFTWARE MAINTENANCE..........................................................................................28
2.1 INTRODUCTION ...........................................................................................................................................28
2.2 UNIX SYSTEM BACKUP..............................................................................................................................28

2.2.1 ACTIONS REQUIRED BEFORE BACKUP FOR UNIX NODES................................................................28
2.2.2 UNIX SYSTEM PARTITIONS DUMP .........................................................................................................28
2.3 UNIX SYSTEM RESTORE ............................................................................................................................30

2.3.1 ACTIONS REQUIRED BEFORE INSTALLATION FOR UNIX NODES...................................................30
2.3.2 SETTING FIRMWARE FLAGS....................................................................................................................30
2.3.3 UNIX INSTALLATION PROCEDURE IN THE TERMINAL SERIAL ENVIRONMENT ........................31
2.3.4 UNIX INSTALLATION PROCEDURE IN THE GRAPHICAL ENVIRONMENT.....................................45
2.3.5 FINAL STEPS ................................................................................................................................................45
2.3.6 RESTORING DATA FROM VDUMP FILES ...............................................................................................46
2.4 CORE FILES TRANSPORT ...........................................................................................................................48

2.4.1 UNIX PROCEDURE FOR CORE FILE TRANSPORT ................................................................................49
2.4.1.1 PROCEDURE 1: SCRIPT FILE..................................................................................................................................... 49
2.4.1.2 PROCEDURE 2: MANUAL COPY............................................................................................................................... 50
3. DOCUMENTATION CROSS REFERENCE TABLE.....................................................53
UNCLASSIFIED Page 2
Issue: A
Date: 03/08/06
1. SYSTEM CONFIGURATION AND GENERAL PROVISION
1.1 SYSTEM ARCHITECTURE
The system provided in the frame of the contract between “CDC and SELEX-SI for the Supply and
Installation of Terminal Radar Approach Control (TRACON) Project at the DIOSDADO MACAPAGAL
International Airport CLARK Special Economic Zone, PAMPANGA”, is based on an extremely
distributed architectural solution, where the most effective solution in terms of system performances and
modularity is joined by the deployment of all the main functionalities and requested services on separated
and distributed equipment.
The diagram of the proposed Radar System is shown in figure 1.2-1 and 1.2-2, where the radar site and
the operational site are shown. Five macroscopic functional blocks can be highlighted:
• Radar Sensors
• Data Processing Subsystem
• Operator Support Subsystem
• Monitoring, Control & Maintenance Subsystem
• Communication and Data Network
UNCLASSIFIED Page 3
Issue: A
Date: 03/08/06
ALE-9
Mode S Test
Transponder
DIESEL DUAL UPS
GENERATOR
ANTENNA BASE
Dual Dual
Encoder ROTARY Motor
Drive
AMDU JOINT
ATCR-33S DPC PSR

SIR-S SSR
9,5 KW C/OVER
PDA PDA
REDUNDANT RECEIVER
SOLID STATE RPCM RPCM
DUAL SIGNAL PROCESSOR TRANSMITTER RX RX
DUAL EXTRACTOR
TX TX
Radar LANs
12:25:40
PC PC
RMM RAW GPS Clock DIP
VIDEO
ATCR-33S SIR-S SSR

LCMS LCP LCP
Spare Outputs
RHP RHP for future
} transmission to
Manila ACC
VDU
Optical Link to DMIA

TRACON Facility
(Executive Office Building)
FIG 1.2-1 - RADAR HEAD BLOCK DIAGRAM
UNCLASSIFIED Page 4
BUSINESS UNIT ATMAS UNCLASSIFIED E292-xxx-xxx
Issue: A
Date: 03/08/06
Radar Data & CMS

froms Radar
DMIA TRACON in Executive Office
Radar Controller
Clearance Delivery Flight Data/Coordinator Maintainance Position FOBS FDD
2000x2000
Weather
PC PC Weather
1K x 1K PC PC
Instrument Strip Strip Instrument
Display Printer Printer Display
Radar Data Display
Flight Plan Terminal Flight Plan Terminal Radar Data Display RCMS VCSS & DVR Terminal Flight Plan Terminal
compa compa compa compa

12:25:40
PC
CD-ROM CD-ROM CD-ROM CD-ROM
12:25:40
DAT DAT
GPS Clock VRC VCSS
Digital Voice Recorder Relocated VCSS
DUAL UPS
Flight Data Processor Recording and Playback EVA Plotter
& TCA
Optical Link between Optical Link between VCSS
VCSS and VHF/UHF and VFR Room Remote LAN
Transmitters Communication Control Panel to Control
TWR
Remote LANs
1K x 1K PC
Strip
Printer
Relocated VHF/UHF
Transmitters DUAL UPS Radar Data Display Flight Plan Terminal
VFR Room Radar Controller
RAPCON Control TWR
FIG. 1.2-2 - EOB TERMINAL RADAR APPROACH CONTROL FACILITY BLOCK DIAGRAM
UNCLASSIFIED Page 5
Issue: A
Date: 03/08/06
1.1.1 RADAR SENSORS
According to the specific performances specified in the relevant radar equipment annexes, the Radar
Sensors detect targets and disseminate relevant information to a local radar head processing units that
produces primary, secondary or combined radar plots and weather information that are transmitted to
Controller Working Positions in the Approach and Control Tower facilities in order to be displayed in a
integrated picture together with all the related information that have been manually correlated to them by
the Controllers.
To achieve this task, five sub-block can be identified:
• Primary Surveillance Radar Antenna (G-33)

• Secondary Surveillance Radar Antenna (ALE-9)
• Antenna Base with Dual Motor Drive and Dual Encoder
• Solid State Primary Surveillance Radar (ATCR 33S-DPC 9,5 KW)
• Mono-Pulse Secondary Surveillance Radar (SIR-S)
1.1.2 DATA PROCESSING SUBSYSTEM
The main task of the Data Processing is to process all received data and to present them to the Air traffic
Controllers and technicians in order to be fully supported in attending their tasks respectively.
Four main processing applications are available:
• Tracking Processing function hosted by Dual Radar Head Processor (RHP) nodes that produces
local tracks from the primary, secondary and combined plots and makes available weather data as
extracted by the weather channel.
• Flight Data Processing function hosted by the Dual Flight Data Processor (FDP) nodes that is in
charge of receiveing ATS messages and to produce and disseminate System Flight Plans towards
Controller Working Positions for relevant manual actions;
• Data Recording and Playback Processing function hosted by the RPB/TCA nodes that captures all
the events available on the System Local area network and reproduces on request the same
integrated scenario as it was available at the time of the recording;
• Traffic Conflict Alerting function hosted by the RPB/TCA nodes that is in charge of processing
surveillance data and tot provide relevant predicted and actual separation infringement warnings
Moreover a GPS Clock provide time messages distribute in the system for relevant synchronization and
in particular to provide referenced time stamping of radar data.
UNCLASSIFIED Page 6
Issue: A
Date: 03/08/06
1.1.3 OPERATOR SUPPORT SUBSYSTEM
The Operator Support Subsystem is responsible of the graphical Human Computer Interface towards
Controllers.
This task is accomplished by:
• Controller Working Position (CWP) mainly providing radar data display;

• Flight Data Operator Position (FDP Client) mainly presenting flight plan information;
1.1.4 MONITORING, CONTROL & MAINTENANCE SUBSYSTEM
The Monitoring, Control & Maintenance Subsystem receives Status Messages from all system units and
is responsible of their presentation in a graphical way, in order to support the User in monitoring and
controlling (where applicable) the whole system. Moreover it allows the calibration of Radar Sensors and
their preventive and corrective maintenance.
Four sub-blocks are conceived for this purpose:
• Local Control and Monitoring System (LCMS)

• Remote Control and Monitoring System (RCMS)
• Radar Maintenance Monitor (RMM)
• Radar Local Control Panel (LCP)
In order to collect all the signals (ON/OFF Relay signals only) available from the equipment such as Air
Conditioning, UPS, Fire Alarms and temperature sensor, a data concentrator (namely BIG-DIP) is
provided and connected with the Radar Head Processors that process them and format specific messages
for the LCMS and the RCMS.
1.1.5 COMMUNICATION AND DATA NETWORK
The Communication and Data Network allows a fast and reliable exchange of information between all
system units.
The Radar Head and the Executive Office Building are connected via a Fiber Optical Link as to avoid any
delay or electromagnetic interference in radar data transmission.
The internal connections at both sites are achieved through a Fast Ethernet (nominal bandwidth of 100
Mb/s) Local Area Network. This LAN is fully redundant (dual) in order to guarantee the highest
availability and it is based upon a professional layer 3 Switch to avoid any delay or loss of information.
Furthermore the Dual System LAN is remoted by means of a Fiber Optical Link in order to connect the
equipment located in the VFR Room to the Control Tower.
UNCLASSIFIED Page 7
Issue: A
Date: 03/08/06
Moreover, two external links are foreseen to interface the new communication panels to the VCSS
(relocated in the Executive Office Building) and the VHF/UHF Transmitters (relocated in the RAPCON
Building):
• One Fiber Optical Link between the Executive Office Building and the RAPCON Building. This
link will provide the needed connection between the existing VHF/UHF Transmitters relocated in
the RAPCON building and the existing VCSS relocated in the Executive Office Building.
• One Fiber Optical Link between the Executive Office Building and the VFR Room (Control
Tower). This link will connect the existing VCSS (relocated in the Executive Office Building) to
the new communication panels (VFR Room in the Control Tower).
Please refer to Annex 1.23 for further details about System communication devices and about VCSS
communication System.
1.2 RADAR HEAD EQUIPMENT
The block diagram of the proposed radar head is shown in figure 1.2-1.
The main components are described in the following paragraphs.
1.2.1 ANTENNA GROUP
The antenna and turning gear group consists of the following:

• G-33 Antenna for the PSR
• ALE9 LVA Antenna for the MSSR
• Antenna Base
• Azimuth Motor Drive Unit
1.2.1.1 G-33 Antenna
TheATCR-33S DPC is a medium range radar, in S-band, designed to be employed in “ATC” centers of
the Terminal area. The apparatus is realized with the concept of operative redundancy for the majority of
the units, with the exception of the transmitter, entirely solid-state, where redundancy is obtained with the
concept of the degraded condition of operation (Fail Soft Philosophy).
The key features of the antenna group are:
• Proven Higher reliability.

• Vertical elevation pattern with high roll-off below the horizon to eliminate the effects of ground
multipath reflection on detection, accuracy and resolution.
• Modified cosecant-squared pattern with enhanced high-angle coverage to maintain high sig-
nal/clutter level for short range targets.
• Narrow azimuth beamwidth to improve azimuth resolution and accuracy and to reduce clutter
cells.
• Low median azimuth sidelobes for reduced ECM and EMI effects (both active and passive).
• Narrow azimuth beamwidth at all elevation angles.
• Multipolarization radar capability against rain, ECM, and various clutter conditions, with high
UNCLASSIFIED Page 8
Issue: A
Date: 03/08/06
circular polarization ellipticity.
The antenna structure is mechanically rigid so as to prevent any abnormal vibration which may cause
undesired phase shifts of clutter returns, and thus ensure excellent MTD performance.
The G-33 antenna has provision for the top-mounting of an MSSR LVA antenna.
1.2.1.2 ALE-9 LVA antenna
The provided MSSR antenna is the SELEX ALE-9, a monopulse high gain Large Vertical Aperture
(LVA) antenna that provides a directional Sum pattern (Σ), an integral Side Lobe Suppression pattern (Ω)
and a Difference pattern (∆).
The directional pattern has a sharp underside cutoff to control ground lobing, while the Ω pattern matches
the phase center height of the directional pattern in order to assure that lobing characteristics of the
directional and Ω patterns are the same.
The purpose of the monopulse (∆) pattern is to provide single-pulse estimate of the azimuth positions of
transponders within the main lobe of the directional pattern. The purpose of the directional (Σ) pattern is
to provide the triggering of the airborne transponders, while the purpose of the SLS (Ω) pattern is to
provide the interrogation side lobe suppression (ISLS) operation at a transmitter frequency of 1030 MHz
and the receiver side lobe suppression (RSLS) operation at a receiver frequency of 1090 MHz.
1.2.1.3 Antenna Base
The Antenna Base is composed by a dual motor drive, a dual encoder and a eight channel rotary joint,
together with a slip ring system for the transmission of the electrical signals from the rotating part to the
fixed part of the antenna group.
The encoder is shielded for optimum electromagnetic compatibility.
The turnable is designed around one big ball bearing, the inner ring of which is the rotating part and to
which the gear motor and antenna data pick-up systems are connected, the latter by means of an
antiblacklash tooth wheel.
The main ball bearings with connected tooth wheels run in oil bath.
1.2.2 PRIMARY SURVEILLANCE RADAR (PSR)
The ATCR-33S DPC (Digital Pulse Compression) 9,5 KW is an S-band Air Traffic Control Radar,
designed to operate in conjunction with modern automated ATC systems based on highly sophisticated
data processing. Therefore, high quality radar signals is ensured even in presence of unwanted echoes
such as ground clutter, weather clutter and interferences.
UNCLASSIFIED Page 9
Issue: A
Date: 03/08/06
The ATCR-33S DPC 9,5 KW, makes use of the latest extraction techniques and ensures advanced
performance such as the ability to operate at unmanned sites, the remote control of parameters, the use of
built-in radar data extractors, radar data tracking at the radar site, narrow-band data transmission, high
MTBF obtained by using solid state components in all the units.
The radar surveys the surrounding environment and reacts continuously to any changing condition. A
wide range of techniques are employed which are automatically selected to ensure at all times, under any
external condition, maximum operational performance and protection from overloads of transmission
lines to the operations site.
The radar is able to recognize the following radar returns:

• Clutter-free areas.
• Ground clutter.
• Second-time-around echoes from large-size targets.
• Weather clutter (rain).
• Slowly moving point echoes and angel echoes.
• Interference from other radars and asynchronous pulses.
After recognizing the type of echo, the radar will automatically select the configuration most suited to the
operational environment within the area surveyed. The selection of the most appropriate technique from
those available is controlled by a system based on geographical maps and by a computer used in the plot
extractor which is integrated into the radar.
The main features of the ATCR-33S DPC are:
• High-gain antenna, with well-designed beSelex in order to obtain maximum performance in clear
and in clutter.
• Very small antenna azimuth beam width.
• High-stability solid state transmitter.
• Very low system noise figure.
• Range/Azimuth adaptive STC.
• Adaptive detection of moving echoes (AMTD) including:
− Range/azimuth adaptive cancellation of ground clutter.
− Adaptive range/azimuth thresholds, one for each Doppler filter, to prevent detection of angel
echoes (birds, insects, automobiles, etc.).
− Adaptive thresholds, one for each Doppler filter, in presence of rain.
UNCLASSIFIED Page 10
Issue: A
Date: 03/08/06
• Loading of range/azimuth adaptive maps, to perform the following functions:

− Antenna beam selection.
− Selection of filter bank to optimize notch width in the AMTD filter bank response according to
ground clutter intensity.
− Angel suppression (False Alarm Normalization, FAN).
− Rain echo suppression.
− Selection of threshold for low Doppler velocity echoes (ground clutter).
− STC.
• Different waveforms for short range and long range coverage.
• Asynchronous interference blanking.
• Capability of operating in Fixed Frequency or Frequency Diversity mode.
• Suppression of echoes due to anomalous propagation.
• Rainfall contour extraction with weather state updating scan by scan.
• Integrated Weather Channel capable of detecting up to 6 different rainfall levels.
• Advanced radar Data Extractor for:
− Range/azimuth coordinate extraction.
− Radial velocity estimate.
− Control of all radar functions.
• Data exchange with remote site with possibility of controlling all radar parameters and the built-in
test (BIT) device.
• Modular structure of all the units to allow easy maintenance.
• High MTBF.
• Low MTTR.
1.2.3 SIR–S SECONDARY RADAR (MSSR)
The SIR-S is the SELEX Monopulse Secondary Surveillance Radar compliant with ICAO ANNEX 10
and with STANAG 4197 Specifications.
It is able to interrogate in all the civilian (3/A, C, D) and military (1, 2, 3) modes with an interlacing
pattern selectable among Single, Double and Triple on scan-to-scan or sector-to-sector basis. The
resolution of the SIR-S equipment is compliant to specifications reported in Ref. Doc. Eurocontrol
SNR.ET1.ST01.1000-STD-01-01 “Eurocontrol Standard Document for Radar Surveillance in En-route
Airspace and Major Terminal Areas” (RSET Standard) and it may be easily expanded in order to upgrade
its basic capabilities to Mode S interrogation.
The SIR-S is a dual channel system with an automatic changeover unit; each channel is provided with an
integrated controller and extractor.
The equipment is very easy to install, and is intended for virtually maintenance free operation; an
extensive Built-in Test Equipment is included to control the correct operation of its sub-units.
Issue: A
Date: 03/08/06
The following design solutions have been taken up:
• Full monopulse receiver.

• All solid-state equipment.
• Programmable integrated controller/extractor.
• Advanced automatic changeover, selecting best channel based on BIT and on-line diagnostics.
• Integrated plot extractor with "confidence mask".
• Auto matched logarithmic receivers.
• Extensive Built In Test Equipment (BITE) and on-line diagnostics, remotely reported.
• Interrogator Side Lobe Suppression (ISLS).
• Receiver Side lobe Suppression (RSLS).
Furthermore the system has been provided with the following capabilities:
• Programmable power output in azimuth.

• Independently programmable output power for each transmitting channel (Omni, Sum).
• Range-azimuth programmable STC.
• Fully programmable mode interlacing.
• Automatic adoption of plot extraction algorithms to solve beam shaping and multipath problems.
• Remote control.
• Maintenance performed by replacement of plug-in units.
The adopted solutions allow the achievement of the following performances:
• High accuracy in azimuth and range.

• Good resolution in azimuth and range.
• Sophisticated adaptive degarbling and defruiting.
• Powerful on-and off-line diagnostics.
• Unmanned operation.
• High MTBF (the system is virtually maintenance free).
• Low MTTR.
Issue: A
Date: 03/08/06
1.2.4 RADAR HEAD PROCESSOR (RHP)
The RHP consists of two COMPAQ DS15 Alpha Servers. The I/O console, connected to each channel,
allows to enter orders to the RHP during the maintenance phase and to monitor the diagnostic messages.
Each RHP has an hard disk and a mass memory device. The Operating System, the applications programs
and the parameters settings are stored in the Hard Disk.
The RHP receives data from the primary and secondary radar through the radar LANs, performs the
combining function and the tracking function and sends local tracks and uncorrelated plots (i.e. plots
which have not been associated with any local track) to the Operational Site. These data are also
transmitted to the Radar Maintenance Monitor (RMM) for maintenance purposes. The RHP includes also
the capability of radar data filtering according to geographical criteria.
The RHP manages and processes the telesignals and telecontrols for the local and/or remote control and
monitoring of the radar system, receiving from each device information about its status and activating all
the warnings and control signals. Diagnostics messages are sent to the Operational Site by means of the
same lines of the radar data lines, allowing a remote control of the whole radar head.
The RHP can also receive and process meteorological data coming from the primary extractor.
The RHP works in a redundant configuration (Master/Slave) in order to ensure the continuity of service in
case of fault of a single processor. RHPs Master and Slave exchange data between them and with the
other apparatus to perform the automatic switching in case of failure in very short time and to ensure the
alignment of the output data.
1.2.5 DGITAL CLOCK SYSTEM
A digital clock system consisting of a Master Unit, a GPS Receiver and many display slave units are
provided. The Master unit is a multipurpose self timed clock, whose time base is provided by a quartz
oscillator, connected to a GPS receiver, which provides UTC synchronizing signals. An output pulse is
transmitted every second to the slave displays so that they are always with the same indication (hours,
minutes, seconds) of the Master Unit.
Six Digital Clock Displays (including 2 spares) are installed in consoles type A,B,D,E.
Nine Wall Mounted Digital Clock Displays are placed in the following locations:
a) NAVCOMM (RAPCON Building)
b) PAGASA (Executive Office Building)
c) PAGASA (RAPCON Building)
d) FOBS
e) IFR Room
f) VFR Room
g) Operations Control Center (EOB)
h) CFR
i) Maintenance Room of Approach Control Facility (EOB)
Two Digital Electronic Clock Units will be provided and installed in Radar Site and in the Executive
Office Building.
Issue: A
Date: 03/08/06
The DEC.9G Digital Electronic Clock is a Unit which allows to:

• handle Local Time with respect to the UTC (Universal Time Code);
• send Time and Date to RHP;
• detect and locally advice bthrough a buzzer internal alarm.
The master unit is a multipurpose self-timed clock, which time base is provided by a quartz oscillator.
The master unit operates in connection with a GPS receiver (via RS422 line) which provides UTC
synchronizing signals. The synchronizing signal is also provided to host units through a V24 line.
System Timing Synchronization
The handling of the Master External Clock and the synchronization of the clocks of the network-
connected devices represents two fundamental tasks of the System Message Dispatcher components
integrated into the system as a distributed application.
The clock alignment is provided in a asynchronous way. In fact as soon as the XSD function receives the
GPS time message from the external Master Timing Unit (the Reference Time), compares its internal
time with the reference time. In the case that the difference is below the second, the node aligns its
internal time to the Reference Time and then sends via network a synchronization message to all the
system nodes.
1.2.6 BIG DIP
BIG-DIP is the basic element for the implementation of processing systems which manage site
equipments such as air conditioning, fire alarms, Uninterruptible Power Supply and Diesel Generator.
It represents a linkage element between computer structures and peripheral elements, by warranting a
modular and flexible integration.
The purpose of BIG-DIP is to acquire signals coming from generic sensors and uniform the acquired
information to be sent to the control unit, which is relieved from any task of management and
interpretation of the signal coming from the sensors.
It also executes actions on the site imposed by the control unit or according to the local processing logic.
Issue: A
Date: 03/08/06
1.2.7 RADAR MAINTENANCE MONITOR (RMM)
The ground station local display is composed by the CDS-1000/M equipment which consists in a
COMPAQ DS15 Alpha Server and an high resolution color monitor.
The RMM allows a visual inspection of the radar operational capability and performance in the
environmental conditions in which the radar sensor works, including primary and secondary radar target
detection, plot extraction and Mono-radar Tracking algorithm performance.
In order to provide a complete monitoring the RMM function shows on a display plots coming from both
the SSR and the PSR and combined-plots/tracks coming from the Radar Head Processor (RHP).
Furthermore, the RMM is able to manage the integrated graphic presentation of raw and synthetic videos
on the same monitor, man-machine interactions and target control functions.
The display has a completely graphic interface. By means of windows, icons, buttons and choice menu
the operator can enter orders simply using a mouse. The technician can enter orders and data into the
RMM by a pointer device or a keyboard, and can also watch the system status and data coming from
radars and RHP on a dedicated display. Different data types are displayed using different symbols and
different colors in order to improve readability.
Under suitable commands the RMM allows to display also geographic or weather maps.
The RMM can manage, at the same time, more than one raw video. The synthetic data and raw video
signals may be displayed overlapped in a mixed presentation, achieving a comparison between target
detection (video) and plot position extraction (synthetic data). Nevertheless, it can also display only
synthetic videos, disabling the raw videos.
The maintenance monitor receives local synthetic radar data (tracks and plots) from RHP and raw video
signals (including triggers and North Report/Azimuthal control pulses), plots and, eventually, meteo maps
directly from the PSR and the Automatic Change Over (ACO) unit of the Secondary Radar.
The disconnection of the RMM does not create any interruption in the normal operational service of the
system.
Issue: A
Date: 03/08/06
1.2.8 LOCAL CONTROL MONITORING SYSTEM (LCMS)
The proposed configuration for the LCMS Equipment is based on a COMPAQ DS15 Alpha Server,
associated with an high resolution color monitor.
The Local Control and Monitoring System receives system status and outputs controls via the dual Radar
Site LAN. The disconnection of the LCMS does not create any interruption in the normal operational
service of the system.
The LCMS system is based on distributed architecture. It accomplishes the control and monitoring
function which operates in the following default states/session:
• WATCHER
• MAINTENANCE
• OPERATIVE
• TECHNICAL
• GLOBAL
There is a super user, named “Administrator” that through a login and a password accesses to the
“Administrator” CMS session. The Administrator can enable all users to specific CMS sessions: Global,
Technical, Operative, Maintenance. The users enabled to specific CMS sessions cannot access to other
sessions.
The Administrator can also modify runtime the CMS users; he can enable them to other sessions or
disable them to some sessions. He can also cancel or add CMS users.
The CMS provides facilities to:
• Logging available diagnostics, alarms and acknowledged operator issued commands

• Select, display, and print or backup logged data
The user interface is based on the X-windowing concept. The status of the system is presented by using a
main graphical picture and providing more detailed information through deeper navigation accessed by
selection of the specific graphical objects among those presented on the screen.
The system is operated through the use of mouse and keyboard.
The CMS allows to select a command and to send it to the system through a graphical windowing-based
man-machine-interface:
• giving commands at any time through a dialog area

• selecting a command from a menu
• selecting a command through on-screen keys
The equipment is able to present the system status in graphical form on the monitor and to present
diagnostic messages coming from the whole system.
Issue: A
Date: 03/08/06
All the status information, related to both the hardware and the software, and coming from each function,
are converted into graphical information and displayed on the monitor in synoptic frames using different
colors.
On the CMS display it is possible to verify the correct running of the whole system and in case of
defective LRU detected by the On-Line BITE included in the equipment it is immediately notified on the
screen.
Status messages are periodically generated and transmitted by the all the equipment. The frequency of
transmission is a configurable site parameter (typically 1 sec).
The diagnostic messages are grouped in priority levels. The system provides three criticality levels for the
various errors and alarms. A filtering for the presentation can be applied based on the priority level class.
A fault of the CMS does not have effect on the Air Traffic Control.
1.3 EOB TRACON EQUIPMENT
The proposed configuration for the Terminal Radar Approach Control System to be installed at EOB is
shown in figure 1.2-2.
The system consists of six consoles, a Flight Data Processor, an advanced Recording and Playback &
TCA system, a Digital Voice Recorder and two GPS clock systems.
The provision of the three communication and data links via optical fiber between the executive office
building, the Control TWR Building and the RAPCON building is also included.
1.3.1 RADAR DATA CONTROLLER CONSOLE (TYPE A)
The console type A contains two main equipment:

• One radar data display (CWP equipped with Barco monitor 2Kx2K)
• One Weather instruments display
Futhermore this consolle will support:

• All necessary input devices (mouse;headphones;keyboard);
• Strip holder;
• Communication control panel (radio and telephone/intercom);
• Digital clock display;
• Illuminated map chart display panel
• Speaker panel;
• VHF/UHF Aero Band Transceiver with battery back-up.
• NAVAIDS Panel Indicator (ILS,VOR).
Issue: A
Date: 03/08/06
1.3.2 CLEARANCE DELIVERY CONSOLE TYPE B
The consolle type B contains two main equipment:

• One flight plan terminal
• One Weather instruments display
Futhermore this consolle supports:

• Strip holder and strip printer;
• Illuminated map chart display panel
• Speaker panel;
1.3.3 FLIGHT DATA COORDINATOR CONSOLE TYPE C
The console type C contains:

• One flight plan terminal
Futhermore this console supports:

• Strip holder and strip printer;
• Speaker panel;
1.3.4 MAINTENANCE POSITION CONSOLE TYPE E
The consolle type E contains three main equipment:

• One radar data display (CWP 1600 x 1200)
• One VCSS supervisor
• One RCMS (Remote Control Monitor System)
Futhermore this console supports:

• Speaker panel;
• NAVAIDS Panel Indicator (ILS,VOR).
Issue: A
Date: 03/08/06
1.3.5 FOBS FDD TYPE F
The consolle type F contains only:

• One Flight Plan terminal
Futhermore this consolle supports:

• All necessary input devices (mouse;keyboard).
1.3.6 TOWER CONSOLE TYPE D
The existing tower console in the Visual room will be refurbished in order to:
• host the Radar Data Display (1600 x 1200 monitor) and the Flight Plan Terminal Position.
• relocate the following equipment:
1. The Old VAISALA equipment and VHF/UHF radio rack
2. The VAISALA terminal
Finally this console supports:

• All necessary input devices (mouse,headphones,keyboard);
• Strip printer;
• Speaker panel;
1.3.7 GENERAL NOTES
• Two computer tables will be provided to allocate the I/O console for the FDP and REC/PLB
Processor and EVA Plotter (PC and printer).
• Single console will be provided with one armchair, while the two position consoles will be
provided with two armchair plus two armchair for the control tower. The total number of the
armchairs is 10 (ten).
Issue: A
Date: 03/08/06
1.3.8 CONSOLE ITEMS DESCRIPTION
1.3.8.1 CDS-2000 Controller Working Position (CWP)
The configuration for the Controller Working Position installed in the Radar Controller Console is based
on the CDS-2000 equipment.
The CWP has been designed as the key element of the Human-Computer-Interface (HCI) in the Air
Traffic Control (ATC) operational environment.
The CWP covers the operational requirements for single controller positions and “sector suite”.
A sector suite is composed of one or several CWPs as well as communications and other minor systems
and is in charge of an airspace control sector (a sector is an elementary volume of airspace with horizontal
and vertical borders).
Within the suite, every CWP is basically to be manned by one controller; for this purpose, it is
characterized by a unique set of input/output devices, which interacts with the graphical display and is
able to take one (or more) specific role.
The CWP adopts an “Open System Architecture”, making extensive use of Commercial Off The Shelf
(COTS) hardware and software elements.
The following capabilities are provided:
1. User friendly Human Computer Interface using multiple windowing techniques;
2. Integrated radar / procedural working position;
3. Radar data presentation (plots, tracks and weather maps);
4. Flight data list presentation

Flight list are table windows that provides the controller with all available information on flight
plan managed by the system;
5. Electronic strips
The CWP is able to generate and display electronic lists related to the flight in a dedicated display
windows.
6. Fixed and Dynamic maps presentation:

The CWP displays static geographic maps on the radar picture windows. A dedicate map editor
allows to generate on-line single local map on the CWP.
On the basis of weather data continuously received from the RHP system, a composite radar picture
of the area of potentially hazardous weather phenomena is displayed if enabled through map
presentation command. Weather radar data are presented as dynamic maps, one for each rain level.
Issue: A
Date: 03/08/06
7. Warning and Alarm Presentation:

Diagnostics and warning are displayed in dedicated windows. Emergency codes are immediately
notified on the screen. STCA, MSAW and DAIW predicted alert are displayed through dedicated
presentation of the label (e.g. changing the current colour associated to the tracks) with relevant
information displayed in a dedicated window . Alarms are notified to controllers by means of:
¾ Acoustic buzzer
¾ Automatic Notification on Alarm List
¾ Highlighting of tracks involved in the dangerous situation.
Deviation alerts notifing the divergence between the computed trajectory and the actual radar track
position is displayed in the Eletronic strips only and finally MTCD conflict related to two flight
trajectories that somewhere in a specific time horizon will come in a separation infringement are
listed in dedicated list and relevant tracks if any correlation has been established, highlighted.
8. Operational Supervisor order management

The Operational Supervisor is a privileged task enabled by an appropriate order, allowed to enter
orders relevant to special settings and configuration management.
9. Display and system settings data presentation:

a table window is dedicated to the presentation of the current settings of the system, radar mode
status, the status and the actual configuration of the CWP.
10. FDP system absence management:

When the FDP system is down, a degraded flight plan management function is available. In fact the
original flight plan to track correlation is maintained. The flight plan insertion/update orders allows
to insert reduced flight plans.
11. On-line Operational reconfiguration of control sectors:

The association between control sector and suite can be changed during current ATC control
operation.
Depending on traffic load, sectors (i.e., volumes of airspace) can be "combined" to build a larger
volume of airspace, still assigned to one suite. These combined sectors can be "split" again, and
everyone controlled by a specific suite.
12. Dynamic reallocation among real, simulation and playback presentation capability:
The ATC centre is provided with different processing environments : On line that allows to provide
ATM services to the operational positions, Playback that allows to provide playback services.
Any CWP can be converted to another task without loosing information (dynamic change of
processing environment).
Issue: A
Date: 03/08/06
1.3.8.2 CDS-1000 Controller Working Position (CWP)
The proposed configuration for the Controller Working Position to be installed in the VFR Room Radar
Controller Console (type D) and in the Maintenance Console (type E) is based on the CDS-1000
equipment.
The CDS-1000 provides the same functionalities described in the paragraph above for the CDS-2000
equipment but with a different HW supply; see the annex outilining scope of supply for more details.
1.3.8.3 Communication Control Panel
Three communication control panels (for radio and telephone/interphone) will be installed in the consoles
type A,B,D.
An additional communication control panel (for telephone/interphone only) will be installed in console
type C.
All of these will be interfaced to the existing VCCS system (relocated in the new approach control facility
in the executive office building).
1.3.8.4 Weather Instrument Display
Two Weather Instruments Displays will be integrated in the consoles type A and B and interfaced with
the existing meteorological system at EOB. A pair of Modems will be provided in order to interface the
serial lines carrying Weather Data from meteorological system at EOB.
1.3.8.5 Digital Clock Display
A digital clock display is integrated in consoles type A,B,D,E and interfaced with the reference signal
from the provided GPS clock.
1.3.8.6 Runway in use Indicator
The “Runway in Use” can be manually inserted in the CWP (order protected by supervisor password).
The actual Runway in Use information is displayed on CWP. See the CWP annex for more details.
1.3.8.7 VFR/IFR Indicator
The VFR/IFR status indicator is an FDP function and will be visualized on the FDP client display.
See the FDP annex for more details.
Issue: A
Date: 03/08/06
1.3.8.8 NAVAIDS Status Indicator
The NAVAIDS status indicator shall be provided for the console type A and B. Selex will integrate this
panel in the Maintenance console.
The NAVAIDS provides indication related to the ILS status and to the DVOR,DME and NDB status.
1.3.8.8.1 ILS status indicator:
For the 20L and 20R runway it is installed:

• One LOCALIZER panel
• One GLIDE SLOPE panel
• One DME panel
Each panel shows the following status

• ON
• OFF
• Maintenance Alert
1.3.8.8.2 DVOR, DME, NDB
A panel with an ON/OFF led and Alarm signal is installed to visualize the VOR status indicator. The
Audio Alarm signal is available only in the maintenance position.
1.3.8.9 Illuminated Map Chart Display Panel
An illuminated map chart display panel with light intensity control is integrated in consoles type A & B.
1.3.8.10Alarm Panel
The Controller Working Positions included in type A and D consoles provide an aural and/or visual
indicator for the following conditions:
• SSR emergency alarm (e.g. highjack, communication failure, emergency)
• RDPS alarm;
• MSAW alarm;
• STCA alarm.
Issue: A
Date: 03/08/06
The Remote Control and Monitoring System (RCMS) included in console type E provides an aural and/or
visual alarm indicator for the following conditions:
1. Radar head general alarm (e.g. burglar alarm, fire alarm, temperature alarm, air conditioning status)
2. Power failure alarm (e.g. generators, UPS, mains)
1.3.8.11VHF/UHF Aero Band Transceiver with battery back-up
A pair of Marconi GTR 100 Transceivers (covering the VHF and UHF band respectively) are installed in
consoles type A, B and D in order to guarantee communications over both the VHF and UHF aeronautical
bands. The transceivers are equipped with a battery back-up system that guarantees a minimum of 4 hours
of back-up time. These VHF/UHF Aero Band Transceivers will be interfaced to the existing VCSS
relocated in the Executive Office Building.
1.3.8.12VHF/UHF Commercial Band Transceiver with battery back-up
A pair of commercial band Transceivers (covering the VHF and UHF band respectively) are installed in
the maintenance console (type E) in order to guarantee communications over both the VHF and UHF
commercial bands. The transceivers are provided with a battery back-up system that guarantees a
minimum of 4 hours of back-up time.
1.3.8.13Flight Data Plan Entry Terminal & Display
Four flight data plan entry terminals (FDP Clients) are installed in consoles type B, C, D & F.
The terminal is composed of a PC and its associated display.
1.3.8.14Silent Strip Printer
Three IER 512 silent strip printers are installed in consoles type B, C and D.
1.3.8.15Remote Control and Monitoring System
A Remote Control and Monitoring System is installed in the maintenance console (type E) configured
exactly as the LCMS described above and providing the same functionalities.
Issue: A
Date: 03/08/06
1.3.9 FLIGHT DATA PROCESSOR (FDP)
The Flight Data Processing System (FDPS) is a dual server system based on an open architecture which
provides the processing of flight plan data and other related information to support air traffic controllers
during the planning and progress phases of flights, in accordance with the referenced ICAO PANS-RAC
4444 rules. It is supplied with two processing units in Master/Stand-by configuration, in order to ensure
the continuity of service in case of single fault of the processor.
The following core functions are realized by the FDP System:
1. Environmental Data Processing

The FDP System has a database where all environment data (both geographic and aircraft
performance data) are stored. This information constitutes the scenario for the progress of all the
other services.
2. Initial Flight Data Handling

The Initial Flight Data Handling (IFDH) function is concerned with the creation and the early
modifications of a SFPL, before it turns to the “active” state after an inbound/departure clearance is
issued into the system.
3. Flight Progress Data Handling

The Flight Progress Data Handling (FPDH) function is concerned with the modifications of SFPL’s
data after its transition to the “active” state and until its termination.
4. Trajectory Prediction
The aim of the Trajectory Prediction function is to predict the full trajectory that a flight will follow
within the boundaries of the Controlled Airspace.
5. Distribution
The Distribution function is concerned with the delivery of the SFPL data to all Flight Plan
Terminals (FDP Clients) and Controller Working Positions (CWPs).
6. SSR Codes Management and Correlation Between Tracks and Flights.

The purpose of the SSR Codes Management and Assignment function is to handle SSR codes in
accordance with ICAO Originating Region Code Assignment Method (ORCAM).
Issue: A
Date: 03/08/06
1.3.10 SAFETY NETS
The Safety Nets function is designed to give controllers a tool able to provide visual and audible warnings
when conflicts are present or predicted. Conflicts are dangerous conditions declared if aircraft tracks are
either separated less than minimum separation thresholds or infringing protected airspace or flying below
minimum safe altitude.
Safety Nets perform calculation to detect actual or predicted conflict within a period of time, the length of
which depends on a parameter that is properly tuned to obtain not too many unnecessary warnings and to
give controllers and pilots, enough time to eventually react and manoeuvre in time.
1.3.11 RECORDING AND PLAYBACK SYSTEM
The Centralised Recording & Playback Subsystem (RPB) performs the recording of all the data passing
through the Local Area Network (LAN), the storing of the recorded data on the Hard Disk for short
period backup (15 days, 30 days, etc..) and on the storage devices for long period backup, and allows the
restore and playback of the recorded data.
The RPB includes basically the following three individual functions:
• Recording
• Backup
• Playback
The three functions can be operated contemporarily.
1.3.12 EVAPLOTTER
The Selex EVAPLOTTER (Evaluator and Plotter System) is a statistical software running on a PC used
to perform the following functions:
• acquire radar data saved by the recording and playback system directly from the DLT tape
• make radar data analysis
• present on a printing device an air traffic image related to a defined time interval and a selected
geographic area, along with the lat-long grid
Issue: A
Date: 03/08/06
1.3.13 DIGITAL VOICE RECORDER
The Digital Voice Recording & Replay System represents a complete recording and replay system with
enhanced functionality to increase safety, efficiency and save operator time.
It utilises open architecture software design and features a user friendly Replay Control Panel, with a
unique visualisation of the recorded data.
Conformity to standards and recommendations, imposed by ICAO and implementation of industry

standards like TCP/IP, SNMP, PCI and ODBC, enables the system to accommodate design changes for
future requirements.
1.3.14 RELOCATED VCSS
The existing VCSS will be relocated from the RAPCON Building to the Executive Office Building inside
of the Equipment room.
Issue: A
Date: 03/08/06
2. SOFTWARE MAINTENANCE
2.1 INTRODUCTION
This section is intended for the personnel assigned to system service, operation and supervision. This
chapter has the purpose to complete the information relevant to the interactive action onto the system,
operational facilities, operative controls, and fault identification that are already provided in the USER
MANUAL for each subsystem composing the System.
2.2 UNIX SYSTEM BACKUP
This procedure has the purpose to realize a backup of each partition on each node of the system, having a
complete set of backups of the whole system. For UNIX nodes the vdump command will be used.
2.2.1 ACTIONS REQUIRED BEFORE BACKUP FOR UNIX NODES
Before to proceed with all the maintenance operations, all the running software must be stopped, in order
to put the system in maintenance mode. For UNIX nodes, the steps to follow to stop the applications are
the following:
• In the node supervisor window, at the input: cursor type F18 <Enter>.
• Open a session as root, and shutdown the system with the following command:
# shutdown –h now
• The node will now enters in the firmware environment, and the following cursor will appears:
>>>
• Boot now the system in single-user mode with the following firmware command:
>>> boot –fl s
• The system will now boot and the root user will be automatically logged in, without any
password request.
• Mount now all the partitions with the following UNIX command:
# mount -a
• It is now possible to proceed with the node partitions dump.
2.2.2 UNIX SYSTEM PARTITIONS DUMP
The vdump command will be used to create a backup on files, which can be easily burned on a CD.
Issue: A
Date: 03/08/06
The first recommendation is to check the all partitions free space with the following order:
# df -h
For the following procedure the super user privilege are required.
The vdump command has the following syntax:
# vdump -0 -C -v -f /backups/usr.bck /filesystem_name
Where the directory /backups/ can be any directory previously created for backup and usr.bck is the
name decided for the backup file.
For a complete backup of the system, filesystems named “/” (root file system), “/usr” (UNIX users
default filesystem) and “/usr2” (Selex-SI users and applications filesystem) must be saved.
The parameters specified for the vdump command represents:
• 0: the vdump command can perform an incremental backup of the files. By the -0 flag, an entire
backup will be done.
• C: the C (capital letter) specify that the files have to be compressed.
• v: the v flag is for the verbose, by which all the file names being backed up will be displayed.
• f: the f flag is to specify the destination saveset device or file, and so it will be followed by the
name of the file that will be generated after the backup operation.
What follows is an example of backup of all partitions. Note that for the root and usr partitions the
operator can save the relevant backup files on the usr2 partition that is sized with more free space (see the
above example). Two recommendations are needed before proceeding with the usr2 dump:
1. The previous has to be removed

2. The relevant usr2 backup file has to be saved in a different partition (i.e. /usr)
# vdump -0 –C –v -f /usr2/backups/root.bck /
# vdump -0 –C –v -f /usr2/backups/usr.bck /usr
# vdump -0 -C -v -f /usr/backups/usr2.bck /usr2
a b g h
/ (root) swap /usr /usr2
Now 3 files will be present in the directory /backups. This files represents one node complete backup.
Issue: A
Date: 03/08/06
Full backup example:

# mkdir /usr2/backups
# vdump -0 –C –v -f /usr2/backups/root.bck /
# vdump -0 –C –v -f /usr2/backups/usr.bck /usr
# mv /usr2/backups /usr
# vdump -0 -C -v -f /usr/backups/usr2.bck /usr2
2.3 UNIX SYSTEM RESTORE

This section of the manual provides instructions for installing, booting and restoring UNIX based Selex-SI
nodes. For this purposes, the vrestore command will be used, after a UNIX installation.
2.3.1 ACTIONS REQUIRED BEFORE INSTALLATION FOR UNIX NODES
• The disk’s partitions on the spare server/workstation must have same or bigger size as the
server/workstation to be replaced. Take note also of the system disk .
• Take note of network configuration and hostnames of the original node.
• Plug the cards in the same slots as the original node.
2.3.2 SETTING FIRMWARE FLAGS
Before starting the UNIX installation procedure, in graphical or in serial environment, complete the
following steps:
• Switch on the node and then abort the automatic boot entering in the firmware environment by
pressing <CTRL+C> during the hardware test phase, namely before the end of the following
diagnostic:
ff.fe.fd.fc.fb.fa.f9.f8.f7.f6.f5.
ef.df.ee.ed.ec.
f4.eb.
ea.e9.e8.e7.e6.....e5.
• The monitor will display a text line describing the firmware version, and then the following prompt:
>>>
• Enter the following command to determine the unit number of the drive for node devices:
>>> show dev
This command displays an output similar to the following
Issue: A
Date: 03/08/06
dKa0.0.0.8.0 DKA0 COMPAQ BD03695CC8 HPB6

dqa0.0.0.13.0 DQA0 HL-DT-ST RW/DVD GCC-4480 2.06
dva0.0.0.0.1 DVA0
ewa0.0.0.13.0 EWA0 . . . . . . . . . .
pka0.7.0.6.0 PKA0 . . . . . . . . . .
The second column shows the name assigned to each drive; the letters DQ refer to a SCSI disk or
CDROM device. The third letter (A, B, C, D, or E) refers to the SCSI bus designation. The number
refers to the drive number.
Please refer to hardware owner’s guide for more details.
Note that, in this example, DQA0 is the CDROM drive name; this information will be used in the
next section.
• Set the content of the auto_action firmware variable to HALT, in order to stop the system at the
firmware after reboot.
>>> set auto_action HALT <Enter>
• Clear the content of the boot_osflags firmware variable.
>>> set boot_osflags “” <Enter>
• Clear the content of the boot_file firmware variable.
>>> set boot_file <Enter>
At this point, it is possible to move directly to the desired section, in order to proceed with the UNIX O.S.
installation procedure in a serial or in a graphical environment.
2.3.3 UNIX INSTALLATION PROCEDURE IN THE TERMINAL SERIAL

ENVIRONMENT
In order to install UNIX in the terminal serial environment, proceed as follows:
• Set the content of the console firmware variable to SERIAL. This will enable the terminal
environment.
>>> set console SERIAL <Enter>
• Clear the content of the bootdef_dev firmware variable:
>>> set bootdef_dev "" <Enter>
Issue: A
Date: 03/08/06
• Store and apply all the firmware variable changes:
>>> init <Enter>
• Insert the UNIX Operating System - Volume 1 CDROM.
• Boot the node from the generic kernel, using the CDROM drive name previously obtained with the
show dev command (DQA0 in our example):
>>> boot -fl fa -fi "GENERIC" DQA0 <Enter>
Messages similar to the following will appear:
boot dqa0.0.1.16.0 -file GENERIC -flags fa)

block 0 of dqa0.0.1.16.0 is a valid boot block
reading 15 blocks from dqa0.0.1.16.0
bootstrap code read in
base = 200000, image_start = 0, image_bytes = 1e00
initializing HWRPB at 2000
initializing page table at 3ff48000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code
4–8 NHD for Version 5.1B Installation Instructions
UNIX boot - Wednesday, April 12, 2006
Loading GENERIC ...

Loading at fffffc0000250000
Enter all Foreign Hardware Kit Names.

Device Names are entered as console names (e.g. dkb100).
The message to enter foreign kit names starts the phase of the process where it is possible to specify
kits and their locations. Do not enter a kit name here. Look at the actual prompt and enter the device
name where the NHD-7 kit is located
• Enter the console device name of the CDROM drive at the prompt and press <Enter> (DQA0 for
this example):
Enter Device Name, or <return> if done: DQA0 <Enter>
• The following prompt will be displayed:
Enter Hardware Kit Name, or <return> if done with DQA0:
• Remove the Tru64 UNIX Operating System CDROM, insert the New Hardware Delivery
CDROM and type the path:
Issue: A
Date: 03/08/06
/540/usr/sys/hardware/base.kit <Enter>
• The following message will appear:
Insert media for kit ’DQA0:/540/usr/sys/hardware/base.kit’

hit <return> when ready, or ’q’ to quit this kit: <Enter>.
• Press <Enter> at each of the following two prompts:
Enter Hardware Kit Name, or <return> if done with DQA0: <Enter>
Enter Device Name, or <return> if done: <Enter>
• When a prompt similar to the following will appear:

Insert boot media, hit <return> when ready:
remove the New Hardware Delivery CDROM, insert the Tru64 UNIX Operating System CDROM,
and press <Enter>.
• When a prompt similar to the following will appear:
Linking 207 objects: 207

Hit <return> when ready or ‘q’ to quit:
• Remove the Tru64 UNIX Operating System CDROM, insert the New Hardware Delivery CDROM,
and press <Enter>. A message similar to the following will appear:

Insert boot media, hit <return> when ready:
• Remove the New Hardware Delivery CDROM, insert the Tru64 UNIX Operating System CDROM,
and press <Enter>. The following messages will appear:
205 204 203 202 201 200 199 198 197

hit <Return> when ready or ’q’ to quit:
196
Insert boot media, hit <Return> when ready:
and press <Enter>. The following messages will appear:
195 194 193 192 191 190 189 188 187 186 185 184
Issue: A
Date: 03/08/06
183
and press <Enter>. Messages similar to the following will appear:
182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167 166
165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149
...
50 49 48 47 46 45 44 43 42
41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18
17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
and press <Enter>. Messages similar to the following will appear:
Sizes:
text = 8359680
data = 2152080
bss = 2433488
Starting at 0xfffffc0000262430
...
1) U.S. English Installation

2) Installation with Worldwide Language Support
3) Exit Installation
Enter your choice: 3 <Enter>
• Reset the content of the hard disk by entering this command:
# disklabel -z DISK <Enter>

(ex. # disklabel -z dsk0 <Enter>)
where DISK is the logical name of the system disk.
Do not care about the diagnostic following this order, for instance: Disk is unlabeled or, /dev/rrsk0a
does not start at block 0 of the disk.
• Label the disk in read/write mode:
Issue: A
Date: 03/08/06
# disklabel -rw -t advfs DISK DISK <Enter>

(ex. # disklabel –rw –t advfs dsk0 dsk0 <Enter>)
• Edit the hard disk partitions:
# disklabel -e DISK <Enter>

1046
During the partition editing no prompt is displayed.
• Show the hard disk parameters and the present partitions:
1,$p <Enter>
A table similar to the following will appear:
# size offset fstype [fsize bsize cpg]

a: 1048576 0 AdvFS 0 0 # (Cyl.0 - 412*)
b: 3145728 1048576 swap 0 0 # (Cyl.412*-1236*)
c: 71132000 0 unused 0 0 # (Cyl. 0 - 3211*)
d: 0 0 unused 0 0 # (Cyl. 0 - -1)
e: 0 0 unused 0 0 # (Cyl. 0 - -1)
f: 10000 14680064 unused 0 0 # (Cyl. 0 - -1)
g: 10485760 4194304 AdvFS 0 0 # (Cyl.1236*7224*)
h: 56441936 14690064 AdvFS 0 0 # (Cyl.7224*-3211*)
Using the following order it is possible to change the position close to the first partition:
/size <Enter>
To move from a line to the following one press <Enter>. I n order to be positioned on a specific
partition, the following order can be used:
/partition_name: <Enter>
where partition_name is the partition to modify.

In order to modify the values of size and/or offset and/or fstype of the selected partition, use the
order:
s/xxxxxx/++++++/p <Enter>
where xxxxxx is the value to change and ++++++ is new value.
• Using all this commands, it is possible to edit the disk partitions in order to obtain the desired
configuration. The partitions a, g and h must be assigned to AdvFS, the partition b to Swap and the
partition f (if present) to LSMsimp.
Issue: A
Date: 03/08/06
• Once finished, write the partitions with the order:
w <Enter>
q <Enter>
To the question write new label?: answer with Y <Enter>
• Restart the system and start again the installation procedure from CDROM with the following order:
# restart <Enter>
Issue: A
Date: 03/08/06
PARTITION EDITING EXAMPLE
The aim of this example, is to modify the values of the default table to the values of the target table. The
default table can be obtained entering 1,$p after the order
# disklabel –e dsk0 <Enter>
Default table:
partitions:
a: 131072 0 unused 0 0 # (Cyl.0 - 412*)
b: 262144 131072 unused 0 0 # (Cyl.412*-1236*)
c: 17773524 0 unused 0 0 # (Cyl. 0 - 3211*)
d: 0 0 unused 0 0 # (Cyl. 0 - -1)
e: 0 0 unused 0 0 # (Cyl. 0 - -1)
f: 0 0 unused 0 0 # (Cyl. 0 - -1)
g: 8690154 393216 unused 0 0 # (Cyl.1236*7224*)
h: 8690154 9083370 unused 0 0 # (Cyl.7224*-3211*)
Target table:
partitions:
a: 500000 0 AdvFS # (Cyl. 0 -148*)
b: 1500000 500000 swap # (Cyl. 148*-595*)
c: 17773524 0 unused 0 0 # (Cyl. 0 -289*)
d: 0 0 unused 0 0 # (Cyl. 0 - -1)
e: 0 0 unused 0 0 # (Cyl. 0 - -1)
f: 0 0 unused 0 0 # (Cyl. 0 - -1)
g: 3000000 2000000 AdvFS # (Cyl. 595*-488*)
h: 12773524 5000000 AdvFS # (Cyl. 1488*-289*)
The target partitions table can be obtained by entering the following commands:
/size <Enter> (set the position at the beginning of the table)

/a: <Enter> (search for the first partition to modify)

a: 131072 0 unused 0 0 # (Cyl.0 - 412*)
s/131072/500000/p <Enter> (replace the old value with the new one)
a: 500000 0 unused 0 0 # (Cyl.0 - 412*)
s/unused/ AdvFS/p <Enter>

a: 500000 0 AdvFS 0 0 # (Cyl.0 - 412*)
/b: <Enter>
b: 262144 131072 unused 0 0 # (Cyl.412*- 1236*)
s/262144/1500000/p <Enter>
Issue: A
Date: 03/08/06
b: 1500000 131072 unused 0 0 # (Cyl.412*- 1236*)
s/131072/500000/p <Enter>
b: 1500000 500000 unused 0 0 # (Cyl.412*- 1236*)
s/unused/ swap/p <Enter>

b: 1500000 500000 swap 0 0 # (Cyl.412*- 1236*)
/c: <Enter>
c: 17773524 0 unused 0 0 # (Cyl. 0 - 13211*)
/d: <Enter>
d: 0 0 unused 0 0 # (Cyl. 0 - -1)
/e: <Enter>
e: 0 0 unused 0 0 # (Cyl. 0 - -1)
/f: <Enter>
f: 0 0 unused 0 0 # (Cyl. 0 - -1)
/g: <Enter>
g: 8690154 393216 unused 0 0 # (Cyl.1236*-7224*)
s/8690154/3000000/p <Enter>
g: 3000000 393216 unused 0 0 # (Cyl.1236*-7224*)
s/ 393216/2000000/p <Enter>
g: 3000000 2000000 unused 0 0 # (Cyl.1236*-7224*)

g: 3000000 2000000 AdvFS 0 0 # (Cyl.1236*-7224*)
/h: <Enter>
h: 8690154 9083370 unused 0 0 #(Cyl.7224*-13211*)
s/8690154/12773524/p <Enter>
h: 12773524 9083370 unused 0 0 #(Cyl.7224*-13211*)
s/9083370/5000000/p <Enter>
h: 12773524 5000000 unused 0 0 #(Cyl.7224*-13211*)

h: 12773524 5000000 AdvFS 0 0 #(Cyl.7224*-13211*)
Verify the target table with the order:
1,$p <Enter>
...
partitions:

a: 500000 0 AdvFS # (Cyl. 0 -148*)
b: 1500000 500000 swap # (Cyl. 148*-595*)
c: 17773524 0 unused 0 0 # (Cyl. 0 -289*)
d: 0 0 unused 0 0 # (Cyl. 0 - -1)
Issue: A
Date: 03/08/06
e: 0 0 unused 0 0 # (Cyl. 0 - -1)

f: 0 0 unused 0 0 # (Cyl. 0 - -1)
g: 3000000 2000000 AdvFS # (Cyl. 595*-488*)
h: 12773524 5000000 AdvFS # (Cyl. 1488*-289*)
In order to write the new settings, enter the followings orders:
w <Enter>
q <Enter>
write new label? [y]: Y <Enter>
# restart <Enter>
END EXAMPLE
Issue: A
Date: 03/08/06
• After the restart, follow this procedure to continue with installation:
...
1) U.S. English Installation

2) Installation with Worldwide Language Support
3) Exit Installation
• Enter (two times, and without any output) the root user password.
Enter root password: Alenia <Enter>
Enter root password: Alenia <Enter>
• Choose a hostname for this system.
Enter the hostname for this system: HOST-NAME <Enter>
• Select as location the UTC zone reference (Greenwich – London).

1) Africa 7) Australia 13) Etc 19) MST
2) America 8) CET 14) Europe 20) MST7MDT
3) Antarctica 9) CST6CDT 15) Factory 21) Pacific
4) Arctic 10) EET 16) HST 22) System V
5) Asia 11) EST 17) Indian 23) WET
6) Atlantic 12) EST5EDT 18) MET
1) Amsterdam 14) Gibraltar 27) Moscow 40) Stockholm

2) Andorra 15) Helsinki 28) Nicosia 41) Tallinn
3) Athens 16) Istanbul 29) Oslo 42) Tirane
4) Belfast 17) Kaliningrad 30) Paris 43) Tiraspol
5) Belgrad 18) Kiev 31) Prague 44) Uzhgorod
6) Berlin 19) Lisbon 32) Riga 45) Vaduz
7) Bratislava 20) Ljubljana 33) Rome 46) Vatican
8) Brussels 21) London 34) Samara 47) Vienna
9) Bucharest 22) Luxemburg 35) San_Marino 48) Vilnius
10) Budapest 23) Madrid 36) Sarajevo 49) Warsaw
11) Chisinau 24) Malta 37) Simferopol 50) Zagred
12) Copenhague 25) Minsk 38) Skopje 51) Zaporozhye
13) Dublin 26) Monaco 39) Sofia 52) Zurich
Enter the current date (as mm/dd/[cc]yy): mm/dd/yy <Enter>
Enter the current time, in 24 hour format (as hh:mm): hh:mm <Enter>
is this correct (y/n): y <Enter>
• Continue the installation procedure following the instructions:
*** Software selection***
Issue: A
Date: 03/08/06
. . .
The following options are available:

1) All Software
2) Mandatory Only
3) Customize
. . .
Space required in (root/usr/var): 108 MB/816 MB/11.7 MB

Are these the software subsets that should be loaded (y/n) ? y <Enter>
. . .
**Kernel Options Selection**
. . .
The following options are available:
1) All Options
2) Mandatory Only
3) Customize
**File System Selection**
. . .
Enter “Help” for more information about LSM.
Would you like to use LSM (y/n)? n <Enter>
Choose your file system layout:
. . .
1) Default file system layout

2) Custom file system layout
. . .
Select the file system type for the root file system.
1) UFS —- UNIX File System

2) AdvFS —- Advanced File System
Select the dsk0 partition where the /usr file system will reside.
This partition must be at least 816MB in order to fit the software that
you have selected. However a size of 700 MB or greater is recommended to
Issue: A
Date: 03/08/06
allow for additional layered software and future upgrade considerations.
Start End
Partition Size Block Block Overlaps
1) b 732MB 500000 1999999 c
2) g 1.4GB 2000000 4999999 c
3) h 17.0GB 5000000 40718159 c
Select the file system type for the /usr file system:
1) UFS —- UNIX File System

2) AdvFS —- Advanced File System
Select the dsk0 partition where the first swapping area (swap1) will
reside.
Start End
Partition Size Block Block Overlaps
1) b 732MB 500000 1999999 c
2) h 17.0GB 5000000 40718159 c
You may choose to have a second swapping area (swap2).

Do you want a second swapping area (y/n) ? n <Enter>
You can make /var a separate file system, or you can have it
share space on the /usr file system.
Should /var be a separate file system (y/n) ? n <Enter>
You have requested this file system layout:
* root file system on dsk0a, type AdvFS

* /usr file system on dsk0g, type AdvFS
* var will be a directory in the /usr file system
* first swapping area (swap1) will be on dsk0b
* no second swapping area (swap2)
Is this the correct file system layout (y/n) ? y <Enter>
You have now answered all questions needed to install

the operating system. Press CTRL/C to cancel the
installation; or type "history" to modify your earlier
answers; or press RETURN to proceed with installation: <Enter>
Continuing installation. . .
. . .
• Now the installation procedure will continue loading the selected subsets. This operation will take a
while, and at the end the system will reboot. Then, finally, the following message will appear:
Issue: A
Date: 03/08/06
. . .
Enter Device Name, or <return> if done: DQA0 <Enter>
• The following prompt will be then displayed:
Enter Hardware Kit Name, or <return> if done with DQA0:
• Remove the Tru64 UNIX Operating System CDROM, insert the New Hardware Delivery
CDROM (and don’t change it again up to the end of the installation procedure) and type the path:
/540/usr/sys/hardware/base.kit <Enter>
• The following message will appear:

hit <return> when ready, or ’q’ to quit this kit: <Enter>.
Enter Hardware Kit Name, or <return> if done with DQA0: <Enter>
Enter Device Name, or <return> if done: <Enter>
• Again, because there are no other kits to install, press Return. The following prompt will appear:
Insert boot media, hit <return> when ready: <Enter>
• Note that although this prompt asks to insert the boot media, don’t insert the Tru64 UNIX
Operating System CDROM. At this point, the installation process will boot from the system disk,
and no media change is necessary. So, after pressing <Enter>, the following prompt will appear:
...
Insert media for kit ’dka400:/540/usr/sys/hardware/base.kit’
hit <return> when ready or ’q’ to quit: <Enter>
• Press <Enter>. The following message will appear:
206
Insert boot media, hit <return> when ready: <Enter>
205 204 203 202 201 200 199 198 197

Insert media for kit ’dqa0:/540/usr/sys/hardware/base.kit’
hit <Return> when ready or ’q’ to quit: <Enter>

196
Insert boot media, hit <Return> when ready: <Enter>
Issue: A
Date: 03/08/06
195 194 193 192 191 190 189 188 187 186 185 184
183
Insert boot media, hit <Return> when ready or ’q’ to quit: <Enter>
182 181 180 179 178 177 176 175 174 173 172 171 170 169 168 167
...
61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42
41 40 39 38 37 36 35 34 33 32 31 29 28 27 26 25 24 23 22 21 20 …..
…3 2 1
Insert boot media, hit <Return> when ready or ’q’ to quit: <Enter>

Sizes:
text = 8359680
data = 2151232
bss = 2433568
Starting at 0xfffffc0000262430
. . .
• Common system configuration messages will now be listed on the screen; then the system will boot
one more time, and the installation procedure will continue. After a while, the procedure will ask to
select the desired kernel option; so all the possible options will be listed and the following message
will finally appear:
. . .
Enter your choices.
Choices (for example, 1 2 4-6) [21]: 21 <Enter>
• Simply be sure to select the option corresponding to “None of the above”, that is generally
proposed as default option, and then confirm again the selection as follows:
You did not select any kernel options.
Is that correct? (y/n) [y]: y <Enter>
• Next question will be the following:

Do you want to edit the configuration file? (y/n) [n]: n <Enter>
Issue: A
Date: 03/08/06
• Select to don’t edit the configuration file, and the procedure will then continue performing the
kernel building. At the end the node will reboot running the new Operating System.
2.3.4 UNIX INSTALLATION PROCEDURE IN THE GRAPHICAL ENVIRONMENT
If the system console to be installed has graphics capability, the X-Server is started and the Installation Setup
window will be displayed. In this case, the graphical environment will guide the user through the installation
process. In order to install UNIX in the graphical environment, proceed as follows:
• Set the content of the console firmware variable to GRAPHICS. This will enable the terminal
environment.
>>> set console GRAPHICS <Enter>
• Clear the content of the bootdef_dev firmware variable, and store all this changes:
>>> set bootdef_dev "" <Enter>

>>> init <Enter>
• Click on the fields in the Installation Setup window to enter the responses to the installation
procedure.
• With the exception of the Root Password and Date and Time fields, it is possible to enter the
information on the Installation Setup window in any sequence. When the password in the Root
Password field is specified, it is required to validate it immediately by entering it again. When either
a date or a time is specified, it is required to enter the other as well.
• The graphical user interface contains extensive online help. To display the online help, click on the
Help button.
• For ease of use, it is possible to click on the Setup Done button as soon as the Installation Setup
window displays because default responses have been provided in all fields where an entry is
required. Keep in mind that doing this, only the mandatory software subsets are installed and the
installation will occur on the default disk that is chosen by the installation procedure.
• If certain essential site-specific information (such as root password, system’s host name, the date
and time, and location and time zone) are not provided, the system will prompt to enter that
information during the configuration phase of the installation process.
2.3.5 FINAL STEPS
After UNIX installation procedure, the original value of some firmware variable must be resumed:
Issue: A
Date: 03/08/06
• Switch on the node and then abort the automatic boot entering in the firmware environment by
pressing <CTRL+C> during the hardware test phase, namely before the end of the following
diagnostic:
ef.df.ee.ed.ec.
f4.eb.
ea.e9.e8.e7.e6.....e5.
• The monitor will display a text line describing the firmware version, and then the following prompt:
>>>
• Change the content of the auto_action firmware variable to RESTART, in order to automatically
run UNIX after node switch on:
>>> set auto_action RESTART <Enter>
• Change the content of the boot_osflags firmware variable to A:
>>> set boot_osflags A <Enter>
• Set the content of the console firmware variable to GRAPHICS. This will enable the graphical
environment.
>>> set console GRAPHICS <Enter>
• Store and apply all the firmware variable changes:
>>> init <Enter>
• It is now finally possible to boot the node:
>>> boot <Enter>
2.3.6 RESTORING DATA FROM VDUMP FILES
In order to restore a previous backup on a new node, the vrestore UNIX command will be used. This
procedure will be executed running the system in single-user mode as follows:
• If the system is still running, login as root user and run the shutdown command:
# shutdown –h now <Enter>
The monitor will display a text line describing the firmware version, and then the following prompt:
Issue: A
Date: 03/08/06
>>>
• If the system is not running, switch it on and then abort the automatic boot entering in the firmware
environment by pressing <CTRL+C> during the hardware test phase, namely before the end of the
following diagnostic:
ef.df.ee.ed.ec.
f4.eb.
ea.e9.e8.e7.e6.....e5.
The monitor will display a text line describing the firmware version, and then the following prompt:
>>>
• Boot now the system in single-user mode with the next firmware command:
>>> boot –fl s
The system will now boot in single-user mode and the root user will automatically log-in, without
any password requires:
• Mount all the partitions:
# mount –a <Enter>
• Insert the CDROM containing the dump of root and usr partitions of the node to be restored, and
then mount the CDROM in the /mnt directory, entering the following command:
# vrestore -xvmount –rt cdfs –o noversion /dev/CDROM-DEVICE /mnt <Enter>
Where CDROM-DEVICE is generally /dev/disk/cdrom0a.
• Restore the root and usr partitions:
# vrestore -x -f /mnt/ROOT-FILEDUMP -D / <Enter>

# vrestore -x -f /mnt/USR-FILEDUMP -D /usr <Enter>
• Reboot the node:
# shutdown -r now <Enter>
• After the reboot, login as root:
Compaq Tru64 UNIX V5.1B (Rev. 2650) (HostName) console
login: root <Enter>

Password: Alenia <Enter>
Issue: A
Date: 03/08/06
• Insert the CDROM containing the dump file of the usr2 partitions, and mount it in the /mnt
directory entering the following order:
# mount –rt cdfs –o noversion /dev/CDROM-DEVICE /mnt <Enter>

• Before starting with the usr2 partition restore, a domain for this file system must be created and
mounted on the empty partition, and mapped in the /usr2 directory. (Note that this part could be
skipped if the hard disk has been previously formatted. If this is not the case, the following steps
may produce warning messages that can be simply ignored.) Create the users_dmn domain in the h
partition:
# mkfdmn –o -F /dev/USERS-PARTITION-DEVICE USERS-DOMAIN <Enter>

(Ex. # mkfdmn –o –F /dev/disk/dsk0h users_dmn <Enter>)
• Create the file set users_fs in the users_dmn domain with the following command:
# mkfset USERS-DOMAIN USERS-FS <Enter>

(Ex. # mkfset users_dmn users_fs <Enter>)
• Create the /usr2 directory:
# mkdir /usr2 <Enter>
• Mount the users_fs in the /usr2 directory with the AdvFS file system:
# mount -t advfs USERS-DOMAIN#USERS-FS /usr2 <Enter>

(Ex. # mount –t advfs users_dmn#users_fs /usr2 <Enter>)
• Insert now the CDROM containing the dump of usr2 partitions of the node to be restored, and then
mount the CDROM in the /mnt directory, entering the following command:
# mount –rt cdfs –o noversion /dev/CDROM-DEVICE /mnt <Enter>

• Restore the usr2 partition:
# vrestore -x -f /mnt/USR2-FILEDUMP -D / <Enter>
• Reboot the node:
# shutdown -r now <Enter>
2.4 CORE FILES TRANSPORT

Transporting core files is usually necessary to debug a core file on a system other than that which has
Issue: A
Date: 03/08/06
produced it. In this examples, “a.out” is the name of the executable and “core.dmp” is the name of the
generated core file.
2.4.1 UNIX PROCEDURE FOR CORE FILE TRANSPORT
The following procedure shows how to transport the core files in UNIX environment. In this case, the user
needs to collect a variety of files from the original system. These include the executable file, the core file,
shared libraries used by the executable, and /usr/shlib/libpthreaddebug.so if the POSIX Threads Library is
involved.
In order to collect all the information to be sent, two different procedures will be illustrated; both this
procedures will produce exactly the same result.
2.4.1.1 PROCEDURE 1: SCRIPT FILE
Do the following steps on the original node:
• Determine the executable program that have generated the core file:
% file core.dmp
• Determine the shared objects in use:

% ladebug a.out core
(ladebug) listobj
(ladebug) quit
Example of the listobj command result:
-----------------------------------------------------------
/usr/shlib/libpthread.so
. text 0x24060000 0x24061fff
. data 0x63c36000 0x63c3ffff
. bss 0x63c40000 0x63c44cff
-----------------------------------------------------------
/usr/shlib/librt.so
. text 0x24062000 0x2406ffff
. data 0x63442000 0x63445fff
-----------------------------------------------------------
/usr/shlib/libots.so
. text 0x24070000 0x24079fff
• Copy the result into a list of file names. Most will probably begin with /usr/shlib/. If
/usr/shlib/libpthread.so is one of the files, add /usr/shlib/libpthreaddebug.so too to the list:
% vi ListLib
cp sharedObjects_1 .
...
cp sharedObjects_n .
Issue: A
Date: 03/08/06
• Close ListLib file:
:wq
• Create a new sub-directory directory named container:

% mkdir container
• Move to this directory and transfer into it the a.out, core and ListLib:
% cd container
% mv ../ListLib .
% mv ../core .
% cp ../a.out .
• Assign the execution privilege to the ListLib file:

% chmod +x ListLib
• Execute the script ListLib:

% ./ListLib
• Verify that all library files are now in container dir:

% ls –l
• Move one directory up from container:

% cd ..
• Package the content of the container directory into a tar file named xxxdebug (where xxx is the node
hostname):
% tar -czhvf xxxdebug.tz container
• This new file is now ready to be sent to Selex-SI for debug operations.
2.4.1.2 PROCEDURE 2: MANUAL COPY
Do the following steps on the original system:
• Determine the executable program that have generated the core file:
% file core
• Determine the shared objects in use:

% ladebug a.out core
(ladebug) listobj
Issue: A
Date: 03/08/06
(ladebug) quit
Example of the listobj command result:
-----------------------------------------------------------
/usr/shlib/libpthread.so
. text 0x24060000 0x24061fff
. data 0x63c36000 0x63c3ffff
. bss 0x63c40000 0x63c44cff
-----------------------------------------------------------
/usr/shlib/librt.so
. text 0x24062000 0x2406ffff
. data 0x63442000 0x63445fff
-----------------------------------------------------------
/usr/shlib/libots.so
. text 0x24070000 0x24079fff
• Open a new window, and create a new sub-directory named container:
% mkdir container
• Move to this directory and transfer into it the a.out, core and ListLib:
% cd container
% mv ../core .
% cp ../a.out .
• Copy now manually all the listed files in the container directory. Remember that if
/usr/shlib/libpthread.so is one of the files, also add /usr/shlib/libpthreaddebug.so to the list:
...
cp sharedObjects_n .
• Verify that all library files are now in container dir:
% ls –l
• Move one directory up from container:
% cd ..
• Package the content of the container directory into a tar file named xxxdebug (where xxx is the node
hostname):
% tar -czhvf xxxdebug.tz container
Issue: A
Date: 03/08/06
• This new file is now ready to be sent to Selex-SI for debug operations.
Issue: A
Date: 03/08/06
3. DOCUMENTATION CROSS REFERENCE TABLE
NUM. OF
ITEM REF. NUMBER DESCRIPTION DOCUMENTATION DOCUMENTATION ID. VOLUME
S
1 EB020010001 RADAR HEAD SUBSYSTEM AS BUILT SYSTEM MANUAL EB020010001PI 1
ALE-9 SSR ANTENNA TECHNICAL
2 353861A2 ALE9 LVA ANTENNA ---- 1
MANUAL
G33 ANTENNA GROUP TECHNICAL
3 02R-060/B G33 ANTENNA TM-RS/8910-2 1
MANUAL
ANTENNA PEDESTAL TECHNICAL
4 03R-060/C PEDESTAL UNIT TM-RS/9201-3 1
MANUAL
5 EU660011703 PWR SWITCHBOARD AS BUILT SYSTEM MANUAL EB020010001PI 1
6 EU330002301 JUNCTION BOX AS BUILT SYSTEM MANUAL EB020010001PI 1
7 EG030011001 AUX CABINET AS BUILT SYSTEM MANUAL EB020010001PI 1
8 EU730009101 DISTRIBUTION UNIT DIS RACK USER MANUAL COD.7D1001 1
AZIMUTH MOTOR DRIVE UNIT
9 A82435511 AMDU TM_A82435511_01 - CL1 1
TECHNICAL MANUAL
DIGITAL PULSE COMPRESSION 10
10 C10000171A ATCR 33S - DPC EQUIPMENT (TX 10KW) TM-RS/2000_02-1 1
KW
10.1 ------------- ------------- 10KWP SOLID STATE TRANSMITTER TM-RS/2000_03-1 2
10.2 ------------- ------------- ATCR 33S - DPC RECEIVER TM TM-RS/9905-1 4
SIR-S SECONDARY INTERROGATOR
11 C1006 SIR-S GROUP TM-RS/9907-2 2
RECEIVER SELECTIVE
12 EE110017001 RMM RMM UM E292-02-04215UM 1
HP ALPHASERVER DS15 - H9AXX
12.1 ------------- ------------- EK-D15H9-RM.B01 1
RACKMOUNT INSTALLATION GUIDE
PVS SERIES TECHNICAL
12.2 ------------- ------------- 072395A 1
SPECIFICATION
12.3 ------------- ------------- PVS SERIES USER MANUAL 072317C 1
12.4 ------------- ------------- RSC SERVER - USER MANUAL 072424L 1
12.5 ------------- ------------- RSC SERVER - USER MANUAL 072390C 1
Issue: A
Date: 03/08/06
NUM. OF
S
HP L1755 17” & L1955 19” FLAT PANEL
12.6 ------------- ------------- 370798-003 1
MONITORS USER GUIDE
12.7 ------------- ------------- PM292 - RADAR DISPLAY UNIT PM292 - RDU 1
13 EE100017901 RHP RHP UM E292-02-04213UM 1
13.1 ------------- ------------- EK-D15H9-RM.B01 1
VIDEO TERMINAL TECHNICAL
13.2 ------------- ------------- ------------- 1
MANUAL
SERIAL IMPACT DOT MATRIX PRINTER
13.3 ------------- ------------- ------------- 1
USER GUIDE
14 EE110017002 LCMS LCMS USER MANAUL E292-02-04211UM 1
14.1 ------------- ------------- EK-D15H9-RM.B01 1
14.2 ------------- ------------- SYNCMASTER 213T USER MANUAL BN59-00361A-08ENG 1
DUPLICATED CLOCK SYSTEM FOR
15 C3/DEC9G/M.809 DEC SYSTEM MANUAL M.470Q 1
RADAR HEAD
SWITCH FOR ETHERNET SYSTEM
16 ------------- INSTALLATION GUIDE 9033948-05 1
LAN 100BASET
B2 48-PORT L2 10/100 ETHERNET
16.1 ------------- ------------- 9033948 1
SWITCH INSTALLATION GUIDE
17 AS0509-01/B BIG DIP BIG-DIP - USER MANUAL BIG-DIP/SUM.01/01.01 1
18 EE100017902 LCP FOR PSR HARDWARE REFERENCE GUIDE 360225-061 1
HP L1740 17” & L1940 19” FLAT PANEL
18.1 ------------- ------------- 372837-001 1
MONITORS USER GUIDE
19 EE100017903 LCP FOR SSR HARDWARE REFERENCE GUIDE 360225-061 1
HP L1740 17” & L1940 19” FLAT PANEL
19.1 ------------- ------------- 372837-001 1
MONITORS USER GUIDE
20 31102/100 TEST TRANSPONDER MOD S2 TECHNICAL MANUAL 1
RAD FOM- INSTALLATION AND OPERATION
21 FIBER OPTICAL INTERFACE 312-200-08/05 1
20/230/SC13L/V24 MANUAL
DUAL UPS AT RADAR HEAD GALAXY PW™ 20 - 200 KVA USER
22 PW60 E-51028230XT/BF 1
SUBSYSTEM MANUAL
Issue: A
Date: 03/08/06
NUM. OF
S
23 EM010001501 TRACON SYSTEM AS BUILT SYSTEM MANUAL EM010001501PI 1
24 EB010012301 EOB TRACON SUBSYSTEM AS BUILT SYSTEM MANUAL EM010001501PI 1
25 EE110017003 CDS-2000 CWP (CONSOLE A) CWP USER MANUAL E292-02-04209UM 1
25.1 ------------- ------------- EK-D15H9-RM.B01 1
28-INCH 2KX2K MAIN DISPLAY PANEL
25.2 ------------- ------------- V599109-06 1
USER MANUAL
26 EE110017004 CDS-1000 CWP (CONSOLE E) CWP USER MANUAL E292-02-04209UM 1
26.1 ------------- ------------- EK-D15H9-RM.B01 1
27 EE110017006 RCMS CMS USER MANUAL E292-02-04217UM 1
27.1 ------------- ------------- EK-D15H9-RM.B01 1
28 EE100017904 FDP FDP USER MANUAL E292-02-04207UM 1
28.1 ------------- ------------- EK-D15H9-RM.B01 1
28.2 ------------- ------------- ------------- 1
MANUAL
29 EE100017905 RPB/TCA RPB/TCA USER MANUAL E292-02-04205UM 1
29.1 ------------- ------------- EK-D15H9-RM.B01 1
29.2 ------------- ------------- ------------- 1
MANUAL
30 EE100017907 DIGITAL VOICE RECORDER TECHNICAL MANUAL MA.0005.C5 1
30.1 ------------- ------------- USER MANUAL MA.0046.A 1
REPLAY CONTROL PANEL USER
30.2 ------------- ------------- MA.0003.B3 1
MANUAL
30.3 ------------- ------------- RLU TECHNICAL MANUAL MA.0029.A1 1
FP731 LCD 17.0" MONITOR USER
30.4 ------------- ------------- --- 1
MANUAL
Issue: A
Date: 03/08/06
NUM. OF
S
31 EE110017007 PC FLIGHT PLAN TERMINAL HARDWARE REFERENCE GUIDE 360225-061 1
HP L1740 17” & L1940 19” FLAT PANEL
31.1 ------------- ------------- 372837-001 1
MONITORS USER GUIDE
32 EE110017007 PC VCSS S.I.T.T.I. HARDWARE REFERENCE GUIDE 360225-061 1
HP L1740 17” & L1940 19” FLAT PANEL
32.1 ------------- ------------- 372837-001 1
MONITORS USER GUIDE
IER 512C PRINTER TECHNICAL
33 IER 512 SILENT STRIP PRINTER N06112A 1
MANUAL
34 EE110017008 WEATHER INSTR. DISPLAY 1
34.1 ------------- ------------- HARDWARE REFERENCE GUIDE 360225-061 1
HP L1740 17” & L1940 19” FLAT PANEL
34.2 ------------- ------------- 372837-001 1
MONITORS USER GUIDE
SWITCH FOR ETHERNET EOB
35 EU7300084A1 INSTALLATION GUIDE 9033924-05 1
SYSTEM LAN 100BASET
35.1 ------------- ------------- 9033948 1
36 EU660011701 POWER SWITCHBOARD AS BUILT SYSTEM MANUAL EM010001501PI 1
RAD FOM- FIBER OPTICAL INTERFACE FROM INSTALLATION AND OPERATION
37 312-200-08/05 1
20/230/SC13L/V24 RADAR HEAD MANUAL
FIBER OPTICAL INTERFACE FROM INSTALLATION AND OPERATION
38 MEGAPLEX-2100 764-202-11/02 1
RAPCON MANUAL
39 C3/DEC9G/M.809 DUPLICATED CLOCK SYSTEM DEC SYSTEM MANUAL M.470Q 1
TECHNICAL DOCUMENTATION
40 M600/33.352 UPGRADING VCSS 05119 2
M600/33/3520 UPGRADE 809
BACKUP TRANSCEIVER VHF AND
41 ------------- 1
UHF AERO-BAND TRANSCEIVER
42 EE100017906 PC EVA PLOTTER HARDWARE REFERENCE GUIDE 360225-061 1
HP L1740 17” & L1940 19” FLAT PANEL
42.1 ------------- ------------- 372837-001 1
MONITORS USER GUIDE
DUAL UPS AT EOB TRACON AND GALAXY PW™ 20 - 200 KVA USER
43 PW40 E-51028230XT/BF 1
CONTROL TOWER MANUAL
Issue: A
Date: 03/08/06
NUM. OF
S
SYSTEM PRINTER - HP COLOR HP COLOR LASERJET 5550 SERIES USER
44 Q3714A Q3713-90913 1
LASERJET 5550N GUIDE
45 EU730009101 DISTRIBUTION UNIT DIS RACK USER MANUAL 7D1001 1
46 EB010012302 CONTROL TOWER SUBSYSTEM AS BUILT SYSTEM MANUAL EM010001501PI 1
47 EE110017005 CDS-1000 CWP (CONSOLE D) CWP USER MANUAL E292-02-04209UM 1
47.1 ------------- ------------- EK-D15H9-RM.B01 1
SWITCH FOR ETHERNET TOWER
48 ------------- INSTALLATION GUIDE 9033948-05 1
SYSTEM LAN 100BASET
48.1 ------------- ------------- 9033948 1
49 EE110017007 PC FLIGHT PLAN TERMINAL HARDWARE REFERENCE GUIDE 360225-061 1
HP L1740 17” & L1940 19” FLAT PANEL
49.1 ------------- ------------- 372837-001 1
MONITORS USER GUIDE
50 EU660011702 POWER SWITCHBOARD AS BUILT SYSTEM MANUAL EM010001501PI 1
51 EU730009101 DISTRIBUTION UNIT DIS RACK USER MANUAL 7D1001 1
FIBER OPTICAL INTERFACE FROM INSTALLATION AND OPERATION
52 FOM-E1-T1/SC13L/230 284-200-07/05 1
EOB TRACON MANUAL

Technical System Overview

Uploaded by

Copyright:

Available Formats

Technical System Overview

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Technical System Overview

Uploaded by

Copyright:

Available Formats

BUSINESS UNIT ATMAS UNCLASSIFIED E292-01-04739OH

Terminal Radar Approach Control (TRACON)

TECHNICAL SYSTEM OVERVIEW

SELEX SISTEMI INTEGRATI S.p.A.

The copyright in this document is the property of SELEX

This document contains a total of 60 pages

DOCUMENT SECURITY CLASSIFICATION:

Any questions arising from this document shall be addressed to:

Telephone +39-06 4150-2408

Prepared by: ......................................................

REVISIONS RECORD SHEET

This sheet is a record of revisions to this document.

Document Change Note

1. SYSTEM CONFIGURATION AND GENERAL PROVISION........................................3

1.1 SYSTEM ARCHITECTURE.............................................................................................................................3

1.2 RADAR HEAD EQUIPMENT .........................................................................................................................8

1.3 EOB TRACON EQUIPMENT ........................................................................................................................17

1.3.12 EVAPLOTTER ...............................................................................................................................................26

2.1 INTRODUCTION ...........................................................................................................................................28

2.2 UNIX SYSTEM BACKUP..............................................................................................................................28

2.3 UNIX SYSTEM RESTORE ............................................................................................................................30

2.4 CORE FILES TRANSPORT ...........................................................................................................................48

3. DOCUMENTATION CROSS REFERENCE TABLE.....................................................53

1. SYSTEM CONFIGURATION AND GENERAL PROVISION

1.1 SYSTEM ARCHITECTURE

ATCR-33S DPC PSR

ATCR-33S SIR-S SSR

Optical Link to DMIA

FIG 1.2-1 - RADAR HEAD BLOCK DIAGRAM

Radar Data & CMS

compa compa compa compa

VFR Room Radar Controller

RAPCON Control TWR

1.1.1 RADAR SENSORS

To achieve this task, five sub-block can be identified:

• Primary Surveillance Radar Antenna (G-33)

1.1.2 DATA PROCESSING SUBSYSTEM

Four main processing applications are available:

1.1.3 OPERATOR SUPPORT SUBSYSTEM

This task is accomplished by:

• Controller Working Position (CWP) mainly providing radar data display;

1.1.4 MONITORING, CONTROL & MAINTENANCE SUBSYSTEM

Four sub-blocks are conceived for this purpose:

• Local Control and Monitoring System (LCMS)

1.1.5 COMMUNICATION AND DATA NETWORK

1.2 RADAR HEAD EQUIPMENT

1.2.1 ANTENNA GROUP

The antenna and turning gear group consists of the following:

1.2.1.1 G-33 Antenna

• Proven Higher reliability.

circular polarization ellipticity.

1.2.1.2 ALE-9 LVA antenna

1.2.1.3 Antenna Base

The encoder is shielded for optimum electromagnetic compatibility.

1.2.2 PRIMARY SURVEILLANCE RADAR (PSR)

The radar is able to recognize the following radar returns:

The main features of the ATCR-33S DPC are:

• Loading of range/azimuth adaptive maps, to perform the following functions:

1.2.3 SIR–S SECONDARY RADAR (MSSR)

The following design solutions have been taken up: