Attachment 0005 - Software Installation Instructions.docx

Integrated Air and Missile Defense (IAMD) Battle Command System (IBCS)

Software Installation Instructions (SWII) V4.5.1.2.3

Internal Document

Prepared by:

Northrop Grumman Mission Systems Missile Defense and Protective Systems Division 213 Wynn Drive Huntsville, AL 35805-1928

CAGE Code 9F909

Integrated Air and Missile Defense (IAMD) Battle Command System (IBCS)

Software Installation Instructions (SWII) Approval Sheet

SIGNATURES FOR RELEASE:

Broderick Andrews, IBCS Code Management

Date

Kimberly Robbins, IBCS CHS IPT Lead

Date

Lori Tatom, IBCS Mission Assurance Manager

Date

Mark Rist, IBCS Program Director

Date

Kristi Fugit, IBCS Configuration/Data Management

Date

Document Type:

Internal Document

Notes or Comment:

N/A

Northrop Grumman Mission Systems Missile Defense and Protective Systems Division IAMD Battle Command System (IBCS) 213 Wynn Drive Huntsville, Alabama 35805-1928

CHANGE RECORD

Table of Contents

List of Tables Table 1: External Reference Documents 26

W31P4Q-20-R-0015

ATTACHMENT 0005

For Official Use Only D-IAT-008, Rel 003 10 March, 2020

Copyright 2020 Northrop Grumman Systems Corporation.

IBCS.DM.079.11 (Jan16)

Copyright 2020 Northrop Grumman Systems Corporation.

ii

Scope This section provides a system overview of the Integrated Air and Missile Defense (IAMD) Battle Command System (IBCS) and an overview of this document.

Identification The Software Installation Instructions (SWII) describes how to install and configure the Integrated Air and Missile Defense (IAMD) Battle Command System (IBCS) executables on IBCS hardware after it has been assembled.

System Overview The Army Integrated Air and Missile Defense (AIAMD) System of Systems (ASoS) integrates current and future sensors, weapons, and their respective Command and Control (C2) into a networked Air and Missile Defense (AMD) system. The materiel solution for the ASoS C2 is the IAMD Battle Command System (IBCS).

IBCS provides the net-centric, Plug and Fight (P&F), System of Systems (SoS) Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance (C4ISR) capability of the IAMD architecture. IBCS consists of two Major End Items (MEIs): the Engagement Operations Center (EOC) and the IBCS Integrated Fire Control Network (IFCN) Relay. The IBCS EOC provides C4ISR functions at battalion (BN) and battery (BTRY) echelons within the AMD Task Force (TF). Both the IBCS EOC and the IBCS IFCN Relay have a P&F B-Kit that enables IAMD weapon and sensor components to fight in the net-centric ASoS. Components to be integrated on the IFCN develop an A-Kit to connect to the IBCS B-Kit. The A-Kit provides the component specific details needed to adapt the sensor or weapon to the A/B Interface specification. Northrop Grumman produces the IBCS EOC and the IBCS IFCN Relay which draw from a set of common software modules that provide track management, engagement operations, interface services (both human and machine), planning, training and supporting software infrastructural needs. IAMD weapon and sensor program offices provide the unique hardware and software items used for integration of their system’s A-Kit with the B-Kit. In addition, Northrop Grumman is developing the IFCN that integrates IBCS MEIs and ASoS-enabled sensors and weapons into a cohesive, network-centric task force.

Copyright 2020 Northrop Grumman Systems Corporation.

For Official Use Only

The OV1- High Level Operational Concept, as defined by the Training and Doctrine Command (TRADOC) Capability Manager (TCM), is shown in Figure 1 1, and includes IBCS, Lower Tier Project Office (LTPO) sensors and weapons, Cruise Missile Defense Systems (CMDS) Project Office sensors and weapons, as well as the IFCN.

Figure 1: OV1- High Level Operational Concept

The IBCS architecture enhances the Warfighter’s ability to execute AMD battle command. By modernizing command and control, the kinematic capabilities of all weapons and detection and tracking envelopes of all sensors can be fully utilized. By establishing and invoking the common standards sought by the Joint IAMD, the vision of a truly joint IAMD is realized. This innovative approach at modernization reduces manpower, enhances training, and reduces operation and support cost while at the same time providing a more robust and effective AMD.

IBCS Software Installation This section describes the installation of IBCS software on an EOC and Relay. The install can be performed by any user in the ibcs group with sudo privileges. Before beginning the install, ensure that the user has ibcs set as his or her default group and that the user is also included in the domain_admins group. Additionally, the /opt/ibcs, /opt/integ, and /data_local/logs directories must have permission for members of the ibcs group to read, write, and execute.

The installation media will consist of the following media:

EOC Software Installation An EOC includes BS1, BS2, BS3, STANDIN1, STANDIN2, STANDIN3, IDD, and up to 12 laptops (ST1 … ST12).

Use the following procedures to install IBCS software on an EOC.

Pre-Requisites

1. Open a terminal window on laptop

2. Remove user modifications to the command prompt if any have been applied.

3. Configure the terminal as follows:

a. Select ”Edit” from the Terminal Window toolbar

b. Select “Profiles …” from the drop-down

c. Click the “Edit” button on left panel to edit the Default Profile

d. Click the “Scrolling” tab on top row

e. Verify that the checkbox for” Unlimited” is checked

f. Click “Close”

g. Click “Close”

Shut Down IBCS Software Before beginning the install, verify the IBCS software has shut down. Execute the following command:

If the tools directory, /opt/integ/tools, exists, you can use the following command:

# ssh bs1 # /opt/integ/tools/Opensaf –a stop Otherwise, use the command below:

# ssh bs1 # for i in idd standin2 standin1 bs2 bs1; do ssh –o UserKnownHostsFile=/dev/null –o StrictHostKeychecking=no -qt $i “sudo /etc/init.d/opensafd stop;”; done;

To shutdown standin3 on S280 only If the tools directory, /opt/integ/tools, exists, you can use the following command:

# ssh –l localadmin standin3 # sudo /etc/init.d/opensafd stop Upgrade the MySql product:

# ssh bs1 # mysql_upgrade -u root # sudo service mysqld restart # ssh bs2 # mysql_upgrade –u root # sudo service mysqld restart # sudo service httpd restart Also, perform the following commands to clear the current repo:

# ssh fs1 # cd /data_local/repo # sudo rm –rf ./ibcs_sw/* # sudo rm –rf ./repodata # sudo createrepo .

# exit

Verify Disk Insert the media labelled (U) IBCS V4.5.0.14.2-SP2.3 Executables into the laptop disk tray.

If the system auto-mounts the cd, perform the following commands:

# cd /media/<disc name> Note: <disc name> is usually a date/time string If the system fails to auto-mount the cd, perform the following commands:

# sudo mount /dev/sr0 /media # cd /media/<disc name> Scan the disk:

# sudo /usr/local/uvscan/uvscan --RECURSIVE --VERBOSE * Exit and remove the disk if it fails the scan.

# sudo mkdir /share/V4.5.0.14.2-SP2.3 # sudo chmod 775 /share/V4.5.0.14.2-SP2.3 # sudo chown root:ibcs /share/V4.5.0.14.2-SP2.3 Copy the software from source to the new directory in /share.

Note: Your location on the system should be at the contents of the <cd /media/discname>.

# sudo cp –r * /share/ V4.5.0.14.2-SP2.3 # sudo chmod 775 –R /share/ V4.5.0.14.2-SP2.3 # sudo chown -R root:ibcs /share/ V4.5.0.14.2-SP2.3 You are ready to perform the EOC installation.

New EOC Installation Perform the following steps:

# ssh –Xqt fs1 # cd /share/ V4.5.0.14.2-SP2.3 # ./install.sh A status regarding connectivity of resources is obtained. If any resources are not available, the user will be provided with an option to abort the installation and mitigate the issue. If all resources are available, the next prompt will NOT appear. Choose the appropriate action if prompted:

# Type ‘Y’ and press ‘Enter’ to continue <case sensitive input> or # Type ‘n’ and press ‘Enter’ to abort <case sensitive input> The following assumes a positive result from previous actions and a desire to continue the installation:

# Type your password and press ‘Enter’ <Although user account screen prompts appear, the program is executing. Except for the following prompt, please do not respond until the Verification script has completed.> Another prompt, not the standard user prompt, will ask the user to continue or exit the installation. Please review the data presented, it corresponds to the actions that are to be performed, and answer accordingly. Again, this document is assuming a positive result:

# Type ‘Y’ and press ‘Enter’ <case sensitive input> The program will continue and a Verification script will conclude the installation. Should the Verification script indicate failures, please execute the install.sh script a second time. If the failures continue, please contact your IBCS support representative.

Eject and secure the installation disk:

# cd / # eject

New Standin3 Installation Perform the following steps from BS1:

# scp –r /share/ V4.5.0.14.2-SP2.3 localadmin@standin3:/data_local/logs/share # ssh –l localadmin standin3 # cd /data_local/logs/share/V4.5.0.13.2-SP2.3/executables # ./install.sh A status regarding connectivity of resources is obtained. If any resources are not available, the user will be provided with an option to abort the installation and mitigate the issue. If all resources are available, the next prompt will NOT appear. Choose the appropriate action if prompted:

Perform the following steps:

# Type ‘Y’ and press ‘Enter’ to continue <case sensitive input> or # Type ‘n’ and press ‘Enter’ to abort <case sensitive input> The following assumes a positive result from previous actions and a desire to continue the installation:

# Type your password and press ‘Enter’ <Although user account screen prompts appear, the program is executing. Except for the following prompt, please do not respond until the Verification script has completed.> Another prompt, not the standard user prompt, will ask the user to continue or exit the installation. Please review the data presented, it corresponds to the actions that are to be performed, and answer accordingly. Again, this document is assuming a positive result:

# Type ‘Y’ and press ‘Enter’ <case sensitive input> The program will continue and a Verification script will conclude the installation. Should the Verification script indicate failures, please execute the install.sh script a second time. If the failures continue, please contact your IBCS support representative.

Eject and secure the installation disk:

# cd / # eject

Set Permission and Ownership of EOC logging directories The following commands ensure the logging directories have the proper settings:

From BS1 of the EOC.

NOTE - All EOCs may not have all laptops, adjust the ‘for loop’ as it applies to the EOC receiving the Software Install.

# sudo chmod 2775 –R /data_local/logs # sudo chown root:ibcs –R /data_local/logs # for i in BS2 STANDIN1 STANDIN2 IDD ST1 ST2 ST3 ST4 ST5 ST6 ST7 ST8 ST9 ST10 ST11 ST12; do ssh –o UserKnownHostsFile=/dev/null –o StrictHostKeychecking=no -qt $i “sudo chmod 2775 –R /data_local/logs; sudo chown root:ibcs –R /data_local/logs;”; done;

Set Permission and Ownership of STANDIN3 logging directories The following commands ensure the logging directories have the proper settings for STANDIN3:

Relay Software Installation A Relay includes c1, c2, c3, c4, c5, c6 and STANDIN4 servers.

Use the following procedures to install IBCS software on a Relay.

Pre-Requisites

1. Open a terminal window on laptop

2. Remove user modifications to the command prompt if any have been applied.

3. Configure the terminal as follows:

a. Select ”Edit” from the Terminal Window toolbar

b. Select “Profiles …” from the drop-down

c. Click the “Edit” button on left panel to edit the Default Profile

d. Click the “Scrolling” tab on top row

e. Verify that the checkbox for” Unlimited” is checked

f. Click “Close”

g. Click “Close”

Relay Connectivity (Direct connection) Obtain a classified Linux laptop, cat5 network cable, and PFPU Milspec adapter cable, modified with an RJ45 female connector, from your IBCS support representative.

Configure the laptop to support a VLAN 1 IPv4 connection using the following steps:

# sudo vim /etc/sysconfig/network-script/ifcfg-eth0.1 # insert the following text:

# DEVICE=eth0.1 # TYPE=Ethernet # ONBOOT=yes # BOOTPROTO=none # USERCTL=no # NM_CONTROLLED=no # IPV6INIT=no # VLAN=yes

# IPADDR=192.168.1.25

# save the file by typing the following # :wq # sudo ifup eth0.1 Connect the PFPU Milspec adapter cable to the front of the PFPU. Install the cat 5 network cable between the PFPU Milspec adapter cable and then to the laptop.

Open a terminal window and enter the following command:

# ssh –qt 192.168.1.1

Relay Connectivity (Network connection) Login to a terminal or laptop of an operational EOC that has network connectivity with the desired Relay.

Insert the media labelled (U) IBCS V4.5.0.14.2-SP2.3 Executables into the laptop disk tray.

If the system auto-mounts the cd, perform the following commands:

# cd /media/<disc name> Note: <disc name> is usually a date/time string If the system fails to auto-mount the cd, perform the following commands:

# sudo mount /dev/sr0 /media # cd /media/<disc name> Scan the disk:

# sudo /usr/local/uvscan/uvscan --RECURSIVE --VERBOSE * Exit and remove the disk if it fails the scan.

Create a directory on the Relay, future references in this section will be <dir name>, and name it something that would be recognizable as the current release; for example:

Note: If this installation is occurring in the field, the username must be localadmin, otherwise, it is not required.

# ssh –qt <username>@<address of relay> # sudo mkdir /data_local/logs/ V4.5.0.14.2-SP2.3 # sudo chmod 775 /data_local/logs/ V4.5.0.14.2-SP2.3 # sudo chown root:ibcs /data_local/logs/ V4.5.0.14.2-SP2.3 # exit Copy the software from source to the new directory in /data_local/logs.

Note: Your location on the laptop should be at the contents of the cd.

Also, again, if this installation is occurring in the field, the username must be localadmin, otherwise, it is not required.

# scp –r * <username>@<address of relay>:/data_local/logs/ V4.5.0.14.2-SP2.3 # ssh –qt <username>@<address of relay> # sudo chmod 775 –R /data_local/logs/ V4.5.0.14.2-SP2.3 # sudo chown -R root:ibcs /data_local/logs/ V4.5.0.14.2-SP2.3 # sudo cp /data_local/logs/ V4.5.0.14.2-SP2.3/RPMs/ibcsINTTOOLS_MEI* /diskless/root/data_local/logs/ You are ready to perform the Relay installation.

If the Relay address is not known, see your IBCS support representative.

Shut Down IBCS Software Verify that a connection to the Relay has been established using the instructions from one of the previous two sections.

Note: And again, if this installation is occurring in the field, the username must be localadmin, otherwise, it is not required.

# ssh –qt <username>@<address of relay> # hostname –f Note: Result of the command above should be c1.<MEIID>.IBCS

Before beginning the install, verify the IBCS software has shut down. Execute the following command:

If the tools directory, /opt/integ/tools, exists, you can use the following command:

# /opt/integ/tools/Opensaf –a stop Otherwise, use the command below:

# for i in c6 c5 c4 c3 c2 c1; do ssh –o UserKnownHostsFile=/dev/null –o StrictHostKeychecking=no -qt $i “sudo /etc/init.d/opensafd stop;”; done;

# exit ‘Exit’ will return you to the local laptop where the install media will be located.

Relay Installation Perform the following steps:

# cd /diskless/root/data_local/repos # sudo rm –rf ./ibcs_sw/* # sudo rm –rf ./repodata # sudo createrepo .

# cd /data_local/logs/ V4.5.0.14.2-SP2.3 # ./install.sh --noxterm A status regarding connectivity of resources is obtained. If any resources are not available, the user will be provided with an option to abort the installation and mitigate the issue. If all resources are available, the next prompt will NOT appear. Choose the appropriate action if prompted:

# Type ‘Y’ and press ‘Enter’ to continue <case sensitive input> or # Type ‘n’ and press ‘Enter’ to abort <case sensitive input>

Another prompt, not the standard user prompt, will ask the user to continue or exit the installation. Please review the data presented, it corresponds to the actions that are to be performed, and answer accordingly. Again, this document is assuming a positive result:

# Type ‘Y’ and press ‘Enter’ <case sensitive input> The program will continue and a Verification script. Should the Verification script indicate failures, please execute the install.sh script a second time. If the failures continue, please contact your IBCS support representative.

Follow the steps below:

These steps assume the copy of the ibcsINTTOOLS rpm occurred in Section 2.2.3. If it did not, and the installation has been successful thus far, this rpm can be copied from /diskless/root/data_local/repos/ibcs_sw to /diskless/root/data_local/logs/.

From c1 of the Relay:

# sudo chroot /diskless/root # cd /data_local/logs

Verify that /opt/integ/exists, create this directory if it does not.

# ls /opt/integ

If directory does NOT exist, create it and set owner, group and permissions.

# sudo mkdir /opt/integ # sudo chmod 775 /opt/integ # sudo chown root:ibcs /opt/integ

Check if INTTOOLS is already installed # rpm –qa | grep –i ibcsINTTOOLS

If a version of ibcsINTTOOLS is found, remove it # sudo rpm –e <rpm name of version found>

Install the new ibcsINTTOOLS # sudo rpm –ivh ibcsINTTOOLS<press tab>

Verify installation was successfully # rpm –qa | grep –i ibcsINTTOOLS

Cleanup the directory #sudo rm –f ibcsINTTOOLS*

Leave the chroot environment #exit

Eject and secure the installation disk.

New Standin4 Installation Insert the media, if not already inserted, into the Standin4 disk tray # login as root If the system auto-mounts the cd, perform the following commands:

# cd /media/<disc name> # sudo mkdir /data_local/logs/ # sudo chmod 775 /data_local/logs/ # sudo chown root:ibcs /data_local/logs/ # scp –r * /data_local/logs/ # sudo chmod 775 –R /data_local/logs/ # sudo chown -R root:ibcs /data_local/logs/ # cd /data_local/logs

If the system fails to auto-mount the cd, perform the following commands:

# sudo mount /dev/sr0 /media # cd /data_local/logs Perform the following steps:

· Modify conf/installVariables.sh to change FS1 to STANDIN4

# sed –i s/FS1/STANDIN4/ conf/installVariables.sh Perform the following step to install the software:

# ./install.sh --noxterm --nouninstall Since this document assumes a positive result, choose the appropriate action of ‘Y’ if prompted:

# Type ‘Y’ and press ‘Enter’ <case sensitive input> Repeat these above steps for each install folder in OTHER/IBCS* (like TestData, Recorder*…) Exit and remove the disk when steps are completed.

Create/Modify the logging directories The Relay is delivered missing one of the harvest directories. Use the following commands to create this directory:

# sudo mkdir /data_local/logs/harvested_data # sudo chmod 2775 /data_local/logs/harvested_data # sudo chown root:ibcs /data_local/logs/harvested_data

Set Permission and Ownership of Relay logging directories The following commands ensure the logging directories have the proper settings:

From c1 of the Relay:

# sudo chmod 2775 –R /data_local/logs # sudo chown root:ibcs –R /data_local/logs # for i in c2 c3 c4 c5 c6; do ssh –o UserKnownHostsFile=/dev/null –o StrictHostKeychecking=no -qt $i “sudo chmod 2775 –R /data_local/logs; sudo chown root:ibcs –R /data_local/logs;”; done;

# ls /data_local/c2_logs If the folder exists and is readable, confirm the /opt/integ/tools/harvest.cfg file is pointing to the correct location Open the harvest.cfg file in vim At the end of the file there are two entries for c1:CILogs. One is commented out with a “#”. If /data_local/c2_logs folder exists and the c1:CILogs containing c2_logs entry is commented out, remove the comment “#” character and comment out the other.

Save the file by entering :wq!

Exit vim

Relay Installation Cleanup If the Direct Connection option was used, perform the following steps:

· Disconnect the PFPU Milspec adapter cable from the Relay and the laptop.

· Remove the VLAN 1 laptop installation using the following commands:

# sudo ifdown eth0.1

# sudo rm –f /etc/sysconfig/network-scripts/ifcfg-eth0.1

Network Manager Installation The type of equipment for the NMSBLK machine varies with regards to location. Most of the field locations will be a stand-alone single device while some locations could be a rack-mount server. These instructions target the stand-alone single device installation but the rack-mount servers can apply the same steps, as they are applicable.

The NMSBLK stand-alone single device will require root login. The servers will probably have multiple accounts. The account used for this installation must have elevated privileges allowing commands to be executed through ‘sudo’.

Obtain the (U) V4.5.0.14.2-SP2.3 ISSNMB Executable disk and a portable USB CD/DVD player Login into the BLKNMS machine as root or an account with elevated privileges.

In case it is running, stop the ISSNMB process:

# sudo initctl stop issnmb

Enable USB functionality USB privileges will need to be enabled if using an external CD/DVD player. Perform the following steps on the BLKNMS machine to provide USB services.

If this file exists:

# sudo vi /etc/modprobe.d/DISA_blacklist.conf

· Comment the entry install usb-storage /bin/true by inserting “#” in the first column:

Before:

install usb-storage /bin/true After:

#install usb-storage /bin/true

· Save the file:

:wq!

· Connect the USB device and power on

· Reboot the machine Verify Disk Mount the portable USB CD/DVD player:

# sudo mkdir /media # sudo mount /dev/sr1 /media If another device is using /dev/sr1, the above method will fail. If that is the case, use the following.:

# sudo mkdir /issnmb # sudo mount /dev/sr0 /issnmb Scan the Disk:

# sudo /usr/local/uvscan/uvscan --RECURSIVE --VERBOSE * McAfee Linux 64 version 6.0.3.356

Exit and remove the disk if scan fails.

Install the software Copy the media to the local machine:

# sudo mkdir /data_local/INSTALL # sudo cp –r * /data_local/INSTALL # sudo chmod 775 –R /data_local/INSTALL # sudo chown root:ibcs –R /data_local/INSTALL # cd /data_local/INSTALL Execute the following command to install the software:

# ./localInstall.sh The expected nodename for Network Manager software is BLKNMS. A hostname verification is performed to verify this is correct. If the nodename is not as expected, you will be prompted to enter a new nodename, preferably the nodename of the current target for installation:

Would you like to install this system like another system? (Y/n) # Type “Y”

Type in the name of the system to install like.

# Type [System Name] The operator will be prompted to continue with the installation as presented:

# Would you like to continue with these changes? (Y/n)

· Type ‘Y’ and press ‘Enter’ <case sensitive input> The program will continue and a Verification script will conclude the installation Should the Verification script indicate failures, please execute the localInstall.sh script a second time. If failures continue, please contact your IBCS support representative.

Set Permission and Ownership of NMB logging directories The following commands ensure the logging directories exist and have the proper settings:

# sudo mkdir /data_local/logs/harvested_data # sudo mkdir /data_local/logs/ibcs # sudo chmod 775 –R /data_local/logs # sudo chown root:ibcs –R /data_local/logs Cleanup the installation directories and files # cd / (important step, do not skip over) # sudo rm –rf /data_local/INSTALL # sudo initctl status issnmb Status should indicate the service is running # sudo umount /issnmb # sudo rm –rf /issnmb

Disable USB functionality If necessary, perform the following steps:

# sudo vi /etc/modprobe.d/DISA-blacklist.conf

· Remove the comment for entry install usb-storage /bin/true by deleting the “#” in the first column:

Before:

#install usb-storage /bin/true After:

install usb-storage /bin/true

· Save the file:

:wq!

· Reboot the machine

AMDWS Software INstallatioN Install Plugins

Verify Disk Insert the media labelled (U) IBCS V4.5.* Executables into the laptop disk tray.

If the system auto-mounts the cd, perform the following commands:

# cd /media/ If the system fails to auto-mount the cd, perform the following commands:

# sudo mount /dev/sr0 /media # cd /media Scan the disk:

# sudo /usr/local/uvscan/uvscan --RECURSIVE --VERBOSE * Exit and remove the disk from the tray if the scan fails.

# cd ./OTHER The following sequence of steps will install and verify the Fires software.

Prepare share drive content for Windows access # mkdir /share/FIRES # cp FirePlugins_deployall*.zip /share/FIRES/.

# cp FiresGwyCIB*.tgz /share/FIRES/.

# cp JIIM_MTFMessageProcessor.dll /share/FIRES/.

# cd /share/FIRES # tar –xvzf FiresGwyCIB*.tgz # cd - # sudo chmod 775 –R /share/FIRES # sudo chown root:ibcs –R /share/FIRES

Access the Fires Windows VM Throughout the Windows installation, User Account Control will often be required. Please respond to the User Account Control popup window as required.

1. # xfreerdp –g 1200x900 -u <username> -d <eoc[MEIID]> FIRES

2. Login to the Fires Windows VM

Verify Host Name

1. Right Click on the “Configuration Admin Tool” shortcut on the Desktop.

2. Click “Run as Administrator”.

3. Click the Host File tab.

4. Verify IP address for Host Name “amdws” is 192.168.51.12

5. Verify IP address for Host Name “fires.fg.amdws” is 192.168.60.79

Stop AMDWS services

1. Click the “Services” tab.

2. Click “Stop all”. Wait until all services show status of “Stopped”.

Install Fires Plugins

1. Open a “Windows Explorer” box

2. Navigate to “S:/FIRES”

3. Right Click on “FiresPlugins_deployall*.zip”

4. Click “Extract All”

5. Click “Extract”

6. When the extraction is complete, Copy the “deploy” folder to the Desktop

7. In the Windows Search box, type “CMD”

8. Right click on the CMD icon

9. Click “Run as Administrator”

10. In the CMD Window, type “cd C:\Users\<USERNAME>\Desktop\deploy”

11. Type “install.bat”

12. Type “D” and press Enter Modify activemq.xml

1. Navigate to C:\Program Files\AMDWSSuite\broker\conf\

2. Right-click on activemq.xml and select edit.

3. Scroll down towards the bottom and find

4. <transportConnector name="aiamd-ssl" uri="ssl://amdws:61678 ?......> and change the amdws to 0.0.0.0 so that it looks like

5. <transportConnector name="aiamd-ssl" uri="ssl://0.0.0.0:61678 ?......>

6. Save and close.

Modify environment variable ACTIVEMQ_BROKER

1. From the Desktop, click on the windows icon.

2. Right-click on “This PC” and select Properties.

3. On the left menu-bar select Advanced System Settings

4. On the bottom right, select Environment Variables

5. Highlight by clicking once - ACTIVEMQ_BROKER

6. Select Edit button and modify from “failover: (ssl://amdws:61678)” to“failover: (ssl://127.0.0.1:61678)” without the quotes.

Install CIB Plugin

1. Copy all files in the “S:/FIRES/CIB/data” folder into “C:\Program Files\AMDWSSuite\CIB\data”

2. Copy all other files from the “S:/FIRES/CIB” folder into “C:\Program Files\AMDWSSuite\CIB” Start AMDWS services Click “Start all” on the Services tab. Wait for all services to show status as “Running”.

Set Banner

1. Click on the Unclassified Green Banner in the top center of main window

2. In the pull down menu select: “US: Secret”

3. Click the “Apply” Button

4. Click “Yes” Verify FIRES Address Book Entries

1. Double-click the “FG Config Page” shortcut on the Desktop

2. Enter the Username:User0 and Password :OIV Build Password found on IBCS-MIS-2599 OIV 4.5.2 Extras DVD on the Fires Gateway Login menu

3. Click the “Login” button

4. Select “Military Messaging”

5. Select “Address Book”.

Verify FIRES Node

1. Select “FIRES (Local Node)”.

2. Click “View Node” and verify the fields of the Node Properties panel.

NOTE: If “FIRES (Local Node)” is missing, click “Add Node” and set the fields of the Node Properties panel.

3. Click “Cancel” (or “OK” if adding a new Node)

4. Click “Save” at the bottom of the page

5. Click “Set as Local Node”

6. Verify Network Interface: 192.168.60.79 (vmxnet3 Ethernet Adapter #5)

7. Click “OK”

8. Click “Save” at the bottom of the page

Verify HEU Node

1. Select “HEU”

2. Click “View Node” and verify the fields of the Node Properties panel:

NOTE: If “HEU” is missing, click “Add Node” and set the fields of the Node Properties panel.

User Name: ada@HEU

3. Click “Cancel” (or “OK” if adding a new Node)

4. Click “Save” at the bottom of the page Verify CIXS-36-DD-PROVIDER Node

1. Select “CIXS-36-DD-PROVIDER”

2. Click “View Node” and verify the fields of the Node Properties panel.

NOTE: If “CIXS-36-DD-PROVIDER” is missing, click “Add Node” and set the fields of the Node Properties panel.

User Name: ada@ CIXS-36-DD-PROVIDER Data Format: CIXS_36_DD_PROVIDER Data Header: NONE Xmit Mode: NONE WSDL Context: http://10.90.90.3:22351/axis/services/Cixs36Service

3. Click “Cancel” (or “OK” if adding a new Node)

4. Click “Save” at the bottom of the page Verify CIXS-36-VALIDATION-PROVIDER Node

1. Select “CIXS-36-VALIDATION-PROVIDER “

2. Click “View Node” and verify the fields of the Node Properties panel.

NOTE: If “CIXS-36-VALIDATION-PROVIDER” is missing, click “Add Node” and set the fields of the Node Properties panel.

3.

VMF Protocol: TCP

Xmit Mode: NONE WSDL Context: http://10.90.90.3:22351/axis/services/Cixs36Service

4. Click “Cancel” (or “OK” if adding a new Node)

5. Click “Save” at the bottom of the page Verify CLIENT Node

1. Select “CLIENT”

2. Click “View Node” and verify the fields of the Node Properties panel.

NOTE: If “CLIENT” is missing, click “Add Node” and set the fields of the Node Properties panel.

VMF Protocol: TCP

Data Header: MIL-STD-2045-47001C Xmit Mode: GTCS

3. Click “Cancel” (or “OK” if adding a new Node)

4. Click “Save” at the bottom of the page Verify BFT Node

1. Select “BFT”

2. Click “View Node” and verify the fields of the Node Properties panel.

NOTE: If “BFT” is missing, click “Add Node” and set the fields of the Node Properties panel.

VMF Protocol: UDP Multicast Network: 192.168.60.79 (vmxnet3 Ethernet Adapter#5) Source Port: 1581 Destination Port: 1581

· Join Group (this box must be checked) User Name:

Data Format: MIL_STD_6017A_PLUS Data Header: MIL-STD-2045-47001D Change 1 Xmit Mode: GTCS

3. Click “Cancel” (or “OK” if adding a new Node)

4. Click “Save” at the bottom of the page Verify BFT2 Node

1. Select “BFT2”

2. Click “View Node” and verify the fields of the Node Properties panel.

NOTE: If “BFT2” is missing, click “Add Node” and set the fields of the Node Properties panel.

VMF Protocol: UDP Multicast Network: 192.168.60.79 (vmxnet3 Ethernet Adapter#5) Source Port: 1582 Destination Port: 1582

· Join Group (this box must be checked) User Name:

Data Format: MIL_STD_6017A_PLUS Data Header: MIL-STD-2045-47001D Change 1 Xmit Mode: GTCS

3. Click “Cancel” (or “OK” if adding a new Node)

4. Click “Save” at the bottom of the page

Verify FIRES Message Handling

1. Select “Message Handling” on the left menu panel.

2. Click “Message Type” column header to sort alphabetically.

3. Locate Message Type = ACO (F756/F011).

4. Verify that Post and Validate boxes are checked and the others are not.

5. Locate Message Type “Air Tasking Order”.

6. Verify that Post and Validate boxes are checked and the others are not.

7. Locate Position Report (K05.1) Air.

8. Verify that Post and Validate boxes are checked and the others are not.

9. Click “Save” on the bottom of page.

Verify CIX3.6 Settings

1. Select the “CIX3.6” tab on the left menu panel

2. Verify the following Local Settings:

URL: /axis/services/Cixs36Service Port: 443

· Allow legacy unencrypted access (this box must be checked) Unencrypted Port: 22351

3. Click “Save” on the bottom of page.

Configure CIB Settings

1. Select “CIB” tab on the left menu panel.

2. Verify the following settings:

Connection Settings

Serial Link Settings

TCP Link Settings

Subscription Settings

· Receive TBM Start or Stop Service

· Run Service (Radio button selected)

3. Click “Save” on the bottom of page.

Configure the AMDWS-WFWS Client Workstation

1. Right-click on the desktop and select “Display settings”.

2. Set the monitor resolution to 1920x1080

3. Right-click on the desktop and choose “NVDIA Control Panel”.

4. Select “NVDIA Control Panel/3D Settings/Adjust Image Settings with Preview”.

5. Select the “Use my preference emphasizing” radio button and move the slider to “Performance”.

6. Select “NVDIA Control Panel/3D Settings/Manage 3D Settings”.

7. Set the Global presets to 3D App - Visual Simulation.

Verify Map Server Configuration Access Map Server Windows VM

1. Open a Linux terminal window

2. Enter the following command:

# xfreerdp –g 1200x900 -u <username> -d <eoc[MEIID]> geoserver

3. Log in to the Map Server Windows VM Verify Map Data is on the VM

1. Open Windows Explorer

2. Navigate to D:\AppData\data\mapData\data_dir\data

3. Verify that the following folders are there:

a. KOREA_DTED2

b. NELLIS_DTED2

c. RSA_DTED2

d. WSMR_FTBLISS_DTED2

e. YUMA_DTED2

Verify Map Server Services Running

1. On the Windows desktop, double-click the Configuration Admin Tool icon

2. On the left hand side, select Services

3. Verify AMDWS Map Server and Geoserver services are set to “running”

4. Close out of everything

5. Log out of the VM

Check IDD Logs for Layer Data

1. In the Linux terminal, type and execute the following:

a. ssh idd

b. cd /data_local/logs/ibcs/ss/issidd

c. grep –i TerrainDataProvider safComp\=IDD\,safSu\=ISSIDD\,safApp\=SS.log

2. Verify that the geoserver_wms_url is set to https://AMDWS:8090/geoserver/wms

3. Verify that the geoserver_wcs_url is set to https://AMDWS:8090/geoserver/wcs

4. Verify that there are Layer entries for:

a. KOREA_DTED2

b. NELLIS_DTED2

c. RSA_DTED2

d. WSMR_FTBLISS_DTED2

e. YUMA_DTED2

ADSI Installation Instructions

Master Media List Obtain the following installation/configuration media from Configuration Management(CM):

Figure 2: Media List

Reference Documents The documents in the following tables are used for reference in supporting this document.

Installation and Configuration Guide — For the Integrated Air Missile Defense Battle Command System (IBCS) 9/2018

Table 1: External Reference Documents

Pre-install ADSI – “Cloned Drives” In order to reduce the time required to install and configure new ADSI instances, pre-installed ADSI drives may be provided. These “Cloned Drives” will have the Linux OS, Windows OS, IAVA, and ADSI software already installed. This alleviates the need for field support personnel to install the ADSI software. However, the ADSI configuration proceedures specified in this document must be executed in order for the ADSI instance to be configured for operations.

This procedure indentifies the steps necessary to configure an ADSI instance with “Cloned Drives” to be operational. Most of the configuration steps refers to other sections in this document.

NOTE: If multiple “Cloned Drive” sets of drives has been received, these proceedures must be execute for each set of drives.

1. Execute section 4.6 Configure the Network (6 minutes)

1. Execute secton 4.7 Configure System Manager with a Base Config (5 minutes)

1. Execute secton 4.9 Final Configuration (10 minutes)

1. Execute section 4.10 Final Configuration – Continued

1. Execute section 4.11 DxViewer Configuration (5 minutes)

1. Execute section 4.12 TacView Configuration

1. Execute section 4.14 Verify ADSI Installation

Build ADSI This procedure builds an ADSI system which encompasses a Windows operating system and a Linux operating system. Once this procedure is completed the ADSI will be in a completely configured state according to IBCS standards. The Windows host of the ADSI will be referred to as the TW and the Linux host will be referred to as the C2 side.

Preparation

1. Locate the CD delivered with the ADSI Hardware : Windows 10 Secure Host Baseline Installation DVD.

1. Obtain the media listed in the Master Media table above from Configuration Obtain the media listed in the Master Media table above from Configuration Management.

Prerequisites

1. Obtain a copy of the Version 15 Air Defense Systems Integrator (ADSI) Installation and Configuration Guide – Version 15.4.3 for the Integrated Air Missile Defense Battle Command System (IBCS).

1. You are able to access the BIOS for both the C2H and the TW hosts of the ADSI using Version 15 Air Defense Systems Integrator (ADSI) Installation and Configuration Guide – Version 15.4.3 for the Integrated Air Missile Defense Battle Command System (IBCS) located in chapter 2.

1. Determine the steps for each bios type GE/DTI/XES.

1. Configure the BIOS according to Version 15 Air Defense Systems Integrator (ADSI) Installation and Configuration Guide – Version 15.4.3 for the Integrated Air Missile Defense Battle Command System (IBCS) located in chapter 2.

1. The optical drive tray is opened and the ADSI is powered off using the power switch on the front of the ADSI.

1. The C2H/TDLG hard drives are removed from the ADSI

System Installation Windows OS Installation – TW (45 Minutes)

1. Insert Windows 10 Secure Host Baseline Installation media(delivered with ADSI hardware) into the optical drive

1. Power on the ADSI by flipping the power switch on the front of the ADSI

1. If the kvm does not display the bios key instructions in time, hit <F2> until BIOS is displayed.

1. See Appendix A, B or C depending on the ADSI system. Follow the direction in the Appendix section to enter the BIOS

a. Verify the date and time is correct on the main screen

b. Select “Boot Order” and hit ENTER

c. Select 1st Boot Device option listed and hit ENTER

d. Select “CD/DVD” and hit ENTER

e. Hit Esc

f. Hit Esc

g. Select “YES” or “OK” to save changes and exit

19. Press any key when the message is displayed “Press any key to boot from cd/dvd” Note: Windows OS will begin installation Note: Windows may automatically begin installation process. If so, skip to instruction step 18

20. “Install Windows” window will display

21. Verify “Language to install:” is English, “Time and current format:” is English, and “Keyboard or input method:” is US

22. Click “Next”

23. Click “Install now”

24. “Setup is starting” window will display

25. Check the box “I accept the license terms” and Click “Next”

26. Click “Custom (advanced)” from the “Which type of installation do you want” window

27. Click “Drive options (advanced)” from the “Where do you want to install Windows?” window

28. Click “Delete”

29. Click “OK”

30. Repeat steps 13 and 14 for all partitions listed until “Disk 0 Unallocated Space” is all that remains.

31. Once all partitions are deleted, Click “Next” Note: Installation will begin and the system will reboot multiple times during the installation Note: Do not press a key during any reboot to prevent from booting from the cd/dvd during the installation process Note: After the installation is complete, about 30 minutes, personalization will begin

32. When the Classification Level screen appears, enter “SECRET” for Classification Level, leave default value for FpCon, leave default value for InfoCon

33. Enter “admin” in the textbox labeled “Type a username (for example, John):”

34. Enter a temporary password, do not use the final password at this time, in the textbox labeled “Type a password (recommended)”

35. Enter the same temporary password in the textbox labeled “Retype your password”

36. The BitLocker password screen appears

37. Enter a BitLocker password

38. Enter the same BitLocker password in the textbox labeled “Please confirm password” field

39. A message screen appears showing the 48-digit string than can be used to recover the system. Record and store the 48-digit recovery string

40. Click “OK” to close the BitLocker screen (Note: System may reboot. If so, enter the BitLocker password when prompted.)

41. Click the clock at the bottom right hand side of the screen

42. Select “Data and Time Settings” link on the lower left hand side of the Time/Calendar window

43. Select “UTC (Coordinated Universal Time) from the drop down box labeled “Set Time Zone”

44. Click “Next”

45. Click “Work network” from the “Select you computer’s current location” window

46. Open the “Control Panel” by clicking the “Start” and selecting “Control Panel” on the right side of the start menu.

47. Select “Hardware and Sound” “Power Options,” “Additional Plans,” and click the “High Performance” radio button on the “Select a power plan” screen.

48. Click “Change plan settings” on the right of High performance power plan..

49. Set both the “Turn off the display” and “Put the computer to sleep” options to “Never”

50. Click “Change Advanced Power Settings” and select “Hard disk” “Turn off hard disk after” and scroll up until you see “Never”

51. Click “Apply” and “OK”

52. Click “Save Changes” at the bottom and close the control panel.

53. Click on the Window’s icon on the bottom left

54. Type “admin” in the search bar and press enter key

55. In the new window, double click on “Component Services”

56. In the Component Services window, click “Services (local)”

57. Click “Windows Time” from the list

58. Right click and select “Properties”

59. For the Startup type pull down menu, select “Automatic (Delayed Start)”

60. Click “OK”

61. Remove the Windows installation media from the optical drive

Install Windows ADSI Software (2 hours)

1. Insert the SW for Windows disk, please reference the Master Media list in Section 4.1, into the optical drive

1. An AutoPlay popup window will display, Click “Run autorun.bat” Note: If AutoPlay popup does not display, execute V15xxx.exe from installation disk as administrator user Note: Click “Yes” in UAC window (Unknown Publisher) Note: The system will begin installing various prerequisite software.

1. When the openSSH window opens it should say “Welcome to the OpenSSH Setup Wizard”- click “Next”. See Figure below.

Figure 3: OpenSSH Setup Wizard

a. In the openSSH Setup window it should say Select Installation Folder – click “Next”. See Figure below.

Figure 4: Select Installation Folder

b. In the openSSH Setup window it should say ready to install – click “Install”

Figure 5: Install

c. In the openSSH Setup window it should say “Completing the OpenSSH Setup Wizard” – click “Finish”. See Figure below

Figure 6: Completing the OpenSSH Setup Wizard Note: Dependencies will automatically begin to install, wait for this process to complete before continuing

65. Click “Next” in the “Version 15 Installation Wizard” window

66. Uncheck “TacViewC2” checkbox in the “Select Products to Install” window

67. Click “Next”

68. Select the radio button labeled “I accept the terms in the license agreement”

69. Click “Next”

70. Verify USTMF Editor and SADL Control checkboxes are unchecked in the “Install Other Applications” window

71. Click “Next”

72. Click “Install” from the “Completing the Version 15 Windows Software Installation Wizard” window or “Ready to Install” screen Note: ADSI Windows application will begin installation

73. Click “Finish”

74. Click “Yes” to restart Windows

75. After restart has completed remove the media from the optical drive Install TacViewC2 (20 minutes)

1. Insert the ADSI TacViewC2 11.8.0.11 disk, please reference the Master Media…