Communications configuration

The CONFIG_COM file is in charge of establishing system communications. A set of nodes are created to nominate the process that are running on each computer. Moreover, this file defines groups and alias for specific communications and specifies the alias corresponding to each computer in order to be identified correctly.

The network addresses, which are at the head of the file, correspond to the MULTICAST network addresses and mask for the first LAN (NETWORK: 10.160.77 and MULTICAST: 224.1.52) and to the MULTICAST network addresses and mask for the second LAN (if it exists) (NETWORK: 10.161.77 and MULTICAST: 224.1.53) and to the MULTICAST network addresses and mask for the third LAN (if it exists) (NETWORK: 10.162.77 and MULTICAST: 224.1.54)

NETWORK 10.160.77 10.161.77 10.162.77 MULTICAST 224.1.52 224.1.53 ####################### # Seccion 1 # Asociacion numero-nombre #

# Numero Nodo Nodo # --- --- #Ultimo Nodo usado 968

#Grupos libres ... 73 75 97 98 99 ####################### 575 fdps1_301_e 576 fdps2_301_e 573 fdps1_301_mr 577 fdps2_301_mr 578 fdps1_301_r 579 fdps2_301_r Etc… etc…

The most important thing to configure CONFIG_COM is HOSTS part. Those lines explains every node used by each AIRCON application.

The used structure is always the same:

#hostname application_specific_nodes_composing_processes

Where hostname defines the position where the software that referrs subsequent communication nodes is installed.

#<hostname> dbm

############## ___HOSTS___ ########## #

S

SyysstteemmAAddmmiinniissttrraattoorr

U

UsseerrMMaannuuaal l

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

Page A-98 #<hostname>1 tool_node fdps1-1 fdps1_302 fdps1_303 fdps1_304_d fdps1_304_f fdps1_304_s fdps1_305_m fdps1_305_l fdps1_306 fdps1_307 fdps1_309_proc

fdps1_309w_1 fdps1_309w_2 fdps1_309w_3 fdps1_309r_1 fdps1_309r_2 fdps1_309r_3 fdps1_311 fdps1_315 fdps1_399 fdps1_301_e fdps1_301_mr fdps1_301_r fdps1_305_r fdps1_305_e fdps1_316 fdps1_316_e fdps1_308 fdps1_308_e fdps1_310_proc

fdps1_310_1 fdps1_310_2 fdps1_310_3 fdps1_310_4 fdps1_310_5 fdps1_310_6 fdps1_310_7 fdps1_310_8 fdps1_312w fdps1_312r fdps1_312_proc fdps1_313 #<hostname>-2 fdps1-2 # #<hostname> tool_node fdps2-1 fdps2_302 fdps2_303 fdps2_304_d fdps2_304_f fdps2_304_s fdps2_305_m fdps2_305_l fdps2_306 fdps2_307 fdps2_309_proc fdps2_309w_1 fdps2_309w_2 fdps2_309w_3 fdps2_309r_1 fdps2_309r_2 fdps2_309r_3 fdps2_311 fdps2_315 fdps2_399 fdps2_301_e fdps2_301_mr fdps2_301_r fdps2_305_r fdps2_305_e fdps2_316 fdps2_316_e fdps2_308 fdps2_308_e fdps2_310_proc

fdps2_310_1 fdps2_310_2 fdps2_310_3 fdps2_310_4 fdps2_310_5 fdps2_310_6 fdps2_310_7 fdps2_310_8 fdps2_312w fdps2_312r fdps2_312_proc fdps2_313 #<hostname>-2 fdps2-2

#

#<hostname> rdps1 rdps1_presence rdps1_meteo rdps1_conflict rdps1_conflict_mono rdps1_sup rdps1_adr rdps1_grabac rdps1_mosaic

#

#<hostname> rdps2 rdps2_presence rdps2_meteo rdps2_conflict rdps2_conflict_mono rdps2_sup rdps2_adr rdps2_grabac rdps2_mosaic

#

#<hostname> sfns2_decode_cat62 sfns2_db_tracks sfns2_presence sfns2_sup sfns2_man_tracks sfns2_sint_tracks sfns2_flight_plan sfns2_flat_esperas sfns2_conflict sfns2_conflict_mono sfns2_mosaic sfns2_grabac

#

#<hostname> sfns1_decode_cat62 sfns1_db_tracks sfns1_presence sfns1_sup sfns1_man_tracks sfns1_sint_tracks sfns1_flight_plan sfns1_flat_esperas sfns1_conflict sfns1_conflict_mono sfns1_mosaic sfns1_grabac

#

#<hostname> fdd_aftn1_ope fdd_aftn1_presence #

#<hostname> fdd_aftn2_ope fdd_aftn2_presence #

#<hostname> fdd_aftn3_ope fdd_aftn3_presence #

#<hostname> fdd_aftn4_ope sdd1_ope sdd1_atc sdd1 sdd1_pbk sdd1_grabac strip_printer1 ted1_01

#

#<hostname> fdd_aftn5_ope sdd2_ope sdd2_atc sdd2 sdd2_pbk sdd2_grabac strip_printer2 ted2_01

#

#<hostname> tsp1 lan_controler1 prn_controler1 tsp1-1 #<hostname>-2 tsp1-2

#

#<hostname> tsp2 lan_controler2 prn_controler2 tsp2-1 #<hostname>-2 tsp2-2

#

#<hostname> rpp1 rpp1_int rpp1_ope rpp1_atc #

#<hostname> rpp2 rpp2_int rpp2_ope rpp2_atc #

#<hostname> uast1 #

#<hostname> uast2 #

#<hostname> sim_1001_1 sim_1001_2 sim_1002 sim_1003 sim_1004 sim_1005 sim_1006 sim_1008_flt sim_1008_add sim_1009 sim_1010_sup sim_1010_msg sim_1011 sim_1012

S

SyysstteemmAAddmmiinniissttrraattoorr

U

UsseerrMMaannuuaal l

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

Page A-99

sim_1014 sim_1015 sim_1016 sim_1017_rec sim_1017_rep sim_1018 sim_1020 sim_1021 sim_1022 sim_1023 sim_1013_1 sim_1013_2 radar1 radar2 radar3 radar4 radar5 radar6 radar7 radar8 radar9 radar10 radar11 radar12 radar13 radar14 radar15 radar16 radar17 radar18 radar19 radar20 radar21 radar22 radar23 radar24 #<hostname> sim_sp_1

#<hostname>sim_spv_tss_rdr sim_tss_rdr sim_atc_tss_rdr sim_dld_tss_rdr sim_tssrdr_cadp

####################################

In those lines are defined the communication nodes for FDP1 to establish communications among the application processes. This node's name is fdps1. It is required to define node fdpsX-2.

#<hostname> tool_node fdps1-1 fdps1_302 fdps1_303 fdps1_304_d fdps1_304_f fdps1_304_s fdps1_305_m fdps1_305_l fdps1_306 fdps1_307 fdps1_309_proc

fdps1_309w_1 fdps1_309w_2 fdps1_309w_3 fdps1_309r_1 fdps1_309r_2 fdps1_309r_3 fdps1_310 fdps1_311 fdps1_315 fdps1_399 fdps1_301_e fdps1_301_mr fdps1_301_r fdps1_305_r fdps1_305_e fdps1_316 fdps1_316_e fdps1_308 fdps1_308_e fdps1_310 fdps1_310_1 fdps1_310_2 fdps1_310_3 fdps1_310_4 fdps1_310_5 fdps1_310_6

fdps1_310_7 fdps1_310_8 fdps1_312w fdps1_313 #<hostname>-2 fdps1-2

#

In those lines are defined in a similar way the nodes for FDP2, the difference is the node's name, fdps2. It is required to define node fdpsX-2.

# <HOSTNAME>2 tool_node fdps2-1 fdps2_302 fdps2_303 fdps2_304_d fdps2_304_f fdps2_304_s fdps2_305_m fdps2_305_l fdps2_306 fdps2_307 fdps2_309_proc

fdps2_309w_1 fdps2_309w_2 fdps2_309w_3 fdps2_309r_1 fdps2_309r_2 fdps2_309r_3 fdps2_310 fdps2_311 fdps2_315 fdps2_399 fdps2_301_e fdps2_301_mr fdps2_301_r fdps2_305_r fdps2_305_e fdps2_316 fdps2_316_e fdps2_308 fdps2_308_e fdps2_310 fdps2_310_1 fdps2_310_2 fdps2_310_3 fdps2_310_4 fdps2_310_5 fdps2_310_6

fdps2_310_7 fdps2_310_8 fdps2_312w fdps2_313 # <HOSTNAME>1-2 fdps2-2

#

Here is refered the SDP1 position (rdps1) and its hostname is the server machine.

#<hostname> rdps1 rdps1_presence rdps1_meteo rdps1_conflict rdps1_conflict_mono rdps1_sup rdps1_adr rdps1_grabac rdps1_mosaic

For SDP2, rdps2 is the node.

#<hostname> rdps2 rdps2_presence rdps2_meteo rdps2_conflict rdps2_conflict_mono rdps2_sup rdps2_adr rdps2_grabac rdps2_mosaic

For SFN1, sfns1 is the node.

#<hostname> sfns1_decode_cat62 sfns1_db_tracks sfns1_presence sfns1_sup sfns1_man_tracks sfns1_sint_tracks sfns1_flight_plan sfns1_flat_esperas sfns1_conflict sfns1_conflict_mono sfns1_mosaic sfns1_grabac

For SFN2, sfns2 is the node

#<hostname> sfns2_decode_cat62 sfns2_db_tracks sfns2_presence sfns2_sup sfns2_man_tracks sfns2_sint_tracks sfns2_flight_plan sfns2_flat_esperas sfns2_conflict sfns2_conflict_mono sfns2_mosaic sfns2_grabac

S

SyysstteemmAAddmmiinniissttrraattoorr

U

UsseerrMMaannuuaal l

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

Page A-100

Uast1 refers RDCU1 and uast2 refers RDCU2. #<hostname> uast1

For DRF, the used alias is rpp ; rpp1 refers to DRF1 and rpp2 refers to DRF2 #<hostname> rpp1 rpp1_int rpp1_ope rpp1_atc

In CMD tsp1 refers to CMD1 and tsp2 refers to CMD2. It is required to define node tspX-2. #<hostname> tsp1 lan_controler1 prn_controler1 tsp1-1

#<hostname>-2 tsp1-2

FDD requires paying attention, because of watching at first lines, fdd_aftnX is defined, but there are some differences, based in the lines that contains nodes fdd_aftnX_presence, which only include FDD positions. If this node is not defined and displays SDD nodes, the defined position is an SDD with a secondary FDD display.

#<hostname> fdd_aftn1_ope fdd_aftn1_presence

#<hostname> fdd_aftn4_ope sdd1_ope sdd1_atc sdd1 sdd1_pbk sdd1_grabac strip_printer1 ted1_01

REMARK: All the computers connected to the system needs to have the same CONFIG_COM file in the appropriate folder. The modification and distribution of the CONFIG_COM file is necessary if a new computer is added to the system or if a change in this file is carried out.

S

SyysstteemmAAddmmiinniissttrraattoorr

U

UsseerrMMaannuuaal l

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

Page A-101