Attachment 04b - Draft_Relay Acceptance Test Procedures.docx

DISCLAIMER

Sections known to need updates

· 1.2. IPTA 2

· 2.2. Test Setup & Diagrams

· 3.2. Configure the A-Side Interface Panel Network Connectivity Workstation

· 4.2. A-Side Interface Panel Network Connectivity

· 4.3. Automatic Software Initialization Check

· 4.4. PATRIOT Functionality & Alt Media

· 4.5. Sentinel Functionality & HRFU

· 4.6. Software Shutdown and Data Harvest

Integrated Air and Missile Defense (IAMD) Battle Command System (IBCS) Acceptance Test Procedures – Relay – Addendum A

Test and Evaluation Document

This material is based upon work supported by the U.S. Army Aviation and Missile Command under Contract No. W31P4Q-08-C-0418.

Integrated Air and Missile Defense (IAMD) Battle Command System (IBCS) Northrop Grumman Mission Systems Missile Defense and Protective Systems Division

213 Wynn Drive

Huntsville, AL 35805-1928

CAGE Code 9F909

For Official Use Only

IBCS-A248-001

18 April 2018

Copyright 2020 Northrop Grumman Systems Corporation.

IBCS.DM.025.24 (Jan16)

Printed document is reference document only. Verify document date with on-line system.

Copyright 2020 Northrop Grumman Systems Corporation.

For Official Use Only Integrated Air and Missile Defense (IAMD) Battle Command System (IBCS)

Acceptance Test Procedure – Relay IBCS-A249-Addendum A-003 Approval Sheet

SIGNATURES FOR RELEASE:

5/6/19

Keith Huck, IBCS T&E System Test Engineer

Date

5/6/19

Bob Faulkner, IBCS T&E System Test Manager

Date

5/6/19

Robert Mason, IBCS T&E IPT Lead

Date

5/6/19

Lori Tatom, IBCS Mission Assurance Lead

Date

5/6/19

Mark Rutledge, IBCS Chief Engineer

Date

5/6/19

Randy Tylicki, IBCS Program Director

Date

5/6/19

Mark Smith, IBCS Configuration/Data Management

Date

Document Type:

Test and Evaluation

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

Release Number

25 July 2018

Initial release

Fig 2-3 Fig 2-4 Fig 2-5 Incorporate redline from test execution on the first three Relays Updated – PATRIOT test config diagram Updated – Sentinel test config diagram Added – A-Side Interface test config diagram PCCB 528

All Updated – IPTA 3 to IPTA 2 Updated – Procedures from v4.0 to v4.5

Fig 2-3 Fig 2-4 Fig 2-5 Updated – PATRIOT test config diagram Updated – Sentinel test config diagram Updated – A-Side Interface test config diagram

Table of Contents

List of Figures

List of Tables

Copyright 2020 Northrop Grumman Systems Corporation.

Overview The objective of this Acceptance Test Description / Procedure (ATD/P) addendum is to provide the detail test steps necessary demonstrate key functionality of the Integrated Air and Missile Defense (IAMD) Battle Command System (IBCS) Relays and to confirm conformity of integrated hardware and software end items with the qualified baseline. The qualified baseline is the successful integration Major End Item (MEI) hardware and software.

IBCS Mission Assurance (MA) has the overall responsibility for all acceptance activities for the MEIs produced on the IBCS contract. In order to meet overall program milestones, the initial Relays will be acceptance tested with the Plug & Fight Processing Unit (PFPU) and the most current approved 4.5.x version of the IBCS software.

Satisfaction of the following criteria shall constitute successful completion of the Acceptance Test (AT) process:

1. Hardware components shall exhibit no defects during In-process and Functional Check-Out (FCO).

2. After hardware and software integration, Information Assurance (IA) scans and analysis will be conducted to ensure the system is in compliance with applicable Information Assurance Vulnerability Alert (IAVA) and Security Technical Implementation Guide (STIG) requirements to ensure IA hardening and reduce cyber vulnerabilities.

3. Following IA scans MEI hardware initialization, operations, data harvesting, and shutdown shall be completed without functional failure and/or error In Accordance With (IAW) the procedures detailed in this addendum.

IBCS IFCN Relay The Integrated Fire Control Network (IFCN) Relay features common hardware and software in a form factor that is intended to impose minimal impact to Air and Missile Defense (AMD) legacy platforms. The Plug and Fight (P&F) “B-Side” application layer interfaces with the appropriate “A-Side” Component Acquisition Program (CAP) adaptation layer for each particular weapon or sensor in the Army Integrated Air and Missile Defense (AIAMD) System of Systems (ASoS). The IFCN Relay provides a mobile communications node that extends connectivity to remote launcher and sensor deployments by expanding the range of Line-of-Sight (LOS) communications over the horizon and around intervening terrain features.

The IBCS IFCN provides the framework to distribute fire control quality data, commands, and messages among IBCS Engagement Operations Centers (EOCs) and P&F-enabled weapons and sensors. The IFCN consists of network components within the two MEIs and transport media used for voice, data, and video information exchanges between IBCS components.

The IFCN Relay is integrated on the IFCN Relay Platform (IRP) which is an IBCS-modified XM1061E1 Flat Bed Trailer that incorporates Non-Developmental-Items (NDIs), Commercial Off-The-Shelf (COTS), Government Furnished Equipment (GFE), and IBCS-developed CSCIs within software builds (see Figure 11 for an illustration).

Figure 11. IFCN V2 Relay

IPTA 2

An IBCS Production Test Asset (IPTA) will be used in support of AT. Each IPTA includes a pair of equipment racks with a minimal amount of standard MEI equipment needed to be utilized during EOC and IFCM V2 Relay MEI AT. During MEI AT, the IPTA is meant to function such that the Unit Under Test (UUT) perceives the IPTA as a tactical EOC. The UUT will be connected to IPTA using the same connections it would in the field. Using IBCS Test Exerciser (ITEx) software, the IPTA will stimulate the UUT and simulate an engagement scenario. The IPTA will provide weapon and sensor data to the UUT, but the engagement will be controlled and directed from the UUT. The ITEx provides a closed-loop simulation / stimulation execution engine for exercising IBCS components and offers the following capabilities:

1. Provides the truth picture of battle elements (Tactical Ballistic Missiles (TBMs), Cruise Missiles (CMs), Red and Blue aircraft, and direct support ground/sea assets),

1. Models IBCS-integrated components (PATRIOT, Sentinel, etc.) starting at the A-Side, supporting the dialog and functionality expected by the IFCN Relay including health and status, track reporting, sensor tasking, and engagement processing,

1. Models non-IBCS elements and simulates the network messages (Tactical Digital Information Link J (TADIL-J), Variable Message Format (VMF)) from those components,

1. Simulates engagements by flying out launched interceptors, modeling the end-game, and detecting object collisions,

1. Includes battle manager models representing functionality incorporated within IBCS-developed Common Software Configuration Items (CSCIs) to support analysis and testing.

ITEx can be componentized and configured to support all testing, training, and analysis roles for IBCS. ITEx can be executed in self-contained, external, and distributed frameworks and has substitutable component capabilities and algorithms.

The ITEx model software undergoes an evaluation, IAW PP-412, Test Tool Development and Certification, against the allocated model requirements. This procedure validates the ITEx software for use in IBCS testing.

IPTA 2 consists of two server racks. Since the IPTAs contain all communication equipment needed for AT, no Network Enclosure (NE) is needed. The server racks that comprise the IPTA contain the network equipment, communications equipment, and servers need to preform EOC functions required for AT. The IPTA will be loaded with the same software version loaded on the Relay UUT (most current approved v4.5.x version). There are two CWMI operator rackmount workstations with Dell 32” monitors. These workstations will be collocated with their monitors. Workstation 1 (ST1) will be configured to run single node ITEx and ITEx Graphical User Interface. Workstation 2 (ST2) will be configured to run CWMI and will also run the A-Side ping script. The IPTA overview is illustrated below in Figure 12. IPTA 2 Overview.

Figure 12. IPTA 2 Overview

IPTA 2 consist of the following principal components:

a. Classified / Red equipment rack containing the following major sub components (see Error! Reference source not found. below):

1. Air and Missile Defense Work Station (AMDWS) laptop – not present

2. GPS Receiver Antenna

3. Media converter chassis with modules

4. 16-Port Netcommander Keyboard Video and Mouse (KVM) Switch and 19” LCD

5. Spectracom SecureSync Timing Unit

6. Silicon Mechanics Rackform server (multi-node ITEx) – not used

7. Cisco 4321 router

8. Cisco 4351 router

9. Cisco 3850 switch

10. RS113 Crystal CDS server – not present

11. RS112 Crystal servers (quantity 7)

12. 3000VA 2U 120V APC Smart UPS – not used

b. Unclassified / Black equipment rack containing the following major sub components (see Error! Reference source not found. below):

1. Harris VHF antenna – not used

2. GPS Receiver Antenna

3. RF-300M-V150 Harris Radio – not used

4. Baseband Processing Unit (BPU) Harris Radio

5. Status and Coordinate Input Module (SCIM)

6. Integrated GPS Receiver Module (IGRM)

7. HAIPE KG-250X

8. Media converter chassis with modules

9. Cisco 4321 router

10. Cisco 4521 router

11. Smart DC Power Distribution Unit

12. DC Power Supply

13. 3000VA 2U 120V APC Smart UPS – not used

c. HRFU antenna, test stand, and tripod adapter mount

d. Test operator workstations (quantity 2)

1. Crystal RISC System (RS)114 Workstation Server

2. Dell 32” monitor

3. Operator Keyboard W/ Hulapoint, USB

4. Mouse

5. Headset – not present

e. Executive Mobile Video (VTC) – not present

Figure 13. IPTA 2 Red Rack

Figure 14. IPTA 2 Black Rack

Relay Test Equipment Table 11. Relay Test Equipment

Test Organization and Diagrams Table of Test Table 21. IFCN V2 Relay Table of Tests

Test Setup & Diagrams Test Defense Plan / Force Laydown All components in Figure 21. PATRIOT Launcher & Alt Media Force Laydown are part of Test Case 09, however only those in color (EOC Mine 52032, 52032B, PATRIOT RIU Mine A01S01, Beck Relay {UUT}, and PATRIOT launchers A06L20-26) will be emplaced / enabled.

Figure 21. PATRIOT Launcher & Alt Media Force Laydown

All components in Figure 22. Sentinel Radar & HRFU Force Laydown are part of Test Case 09, however only those in color (EOC Mine 52032, 52032B, Sentinel Radar Greasewood A05S02, Greasewood Relay {UUT}) will be emplaced / enabled.

Figure 22. Sentinel Radar & HRFU Force Laydown

IPTA to Relay Test Configuration

Figure 23. PATRIOT Run –Test Configuration (Relay IFCN via Alt Media)

Figure 24. Sentinel Test Configuration (Relay IFCN Connection via HRFU)

Figure 25. A-Side Interface Panel Network Connectivity

Power Sub-System & Battery

Figure 26. Power Sub-System & Battery

Relay Plug & Fight Processing Unit (PFPU)

Figure 27. Relay PFPU

IFCN Network Enclosure

Figure 28. Network Enclosure Exterior View

Figure 29. Network Enclosure Interior View

Figure 210. BPU

Figure 211. Network Enclosure Signal & Power Panels

A-Side Panel

Figure 212. A-Side Interface Panel

IBCS-A249-ADDENDUM A-003

9 May 2019

Pretest Steps Configure the BPU into Test Mode The following steps are taken to put the BPU into test mode. This causes the signal to go to the coax connector instead of radiating out the antenna.

Table 31. Configure BPU Into Test Mode

Power UUT On

Configure BPU and HRFU

· Wait until the 1 PPS light is blinking on the front of the BPU

· Disconnect IGRM interface cable from BPU front panel J3 connector

· Connect W5 cable to port J3 on front of BPU

· Connect W5 cable to laptop console port

· Login to laptop

· Open a terminal window

· Type sudo minicom

· Press enter in Minicom session

See Figure 29. Network Enclosure Interior View for BPU location and Figure 210. BPU for port location.

The Field Support menu is displayed in laptop Minicom session.

With the IFCN Relay Network Enclosure door open, the BPU will show Crypto – green Nav System – green Xmit enable green 1 Link – green Data Xmit – blinking green

Verify the following:

1. IPv6 and IPv4 addresses have been entered as well as their respective gateway addresses.

2. Center frequency is set to 4537 MHz.

3. Inertial Navigation System (INS) present is set to 0

4. ARQ is set to 0

5. version:harris_r2.0.11

6. Antenna Mode is set to 5 NOTE: IP address will be provided separately prior to testing Configuration Summary is displayed

System/radio configuration setting confirmed

Radio prompts for Field Support Password

· Select option 13 (Store Settings)

· Type y to confirm

· Select option 14 (Restart Radio)

· Type y to confirm Settings are saved and radio restarted

Crypto – green Nav System – green Xmit enable green 1 Link – green Data Xmit – blinking green

NOTE: SYSTEM FAIL LED should be extinguished. If it is blinking red ensure Timing Unit is sync’d and IGRM is displaying GPS locked and wait for LED to extinguish. If solid red and SCIM displays GPS locked, reset the BPU and wait for LED to extinguish.

SYSTEM FAIL LED is extinguished

· Disconnect W5 test cable from BPU J3 connector

· Disconnect W5 test cable from laptop

· Turn laptop off Laptop disconnected

Configure the A-Side Interface Panel Network Connectivity Workstation These steps are need so that the connectivity test workstation network interface card has an IP address that can send and receive pings to / from the UUT.

Table 32. A-Side Interface Panel Network Connectivity Workstation

Determine the VLAN 10 IPv6 Address

The A-Side interface uses IPv4 address except for the 2nd TFOCA pair on J1 SENSOR, which is for voice and is IPv6.

· Log on to ST2

Edit Workstation Configuration File

· Right click on desktop

· Click on Open Terminal

· Type cd /etc/sysconfig/network-scripts

· Type sudo vi ifcfg-eth1

· IPADDR= xxxx

· IPV6ADDR=yyyy::25/64

· IPV6INIT=yes

· IPV6_AUTOCONF=no

· Hit the Esc key then type :wq

Replace xxxx above with the IPv4 address.

Replace yyyy above with the VLAN 10 IPv6 address.

NOTE: IP address will be provided separately prior to testing.

· Type sudo /etc/init.d/network restart

Test Procedures Hardware Power Up Table 41. Hardware Power Up

Test Conduct:

Run Name __________________________

Attempt # __________________________

Date of Run _________________________

Test Conductor ______________________

Test Operator _______________________

QA Witness _________________________

Gov Witness _________________________

Other Witness _______________________

IFCN Relay SN ______________________

IFCN Relay PFPU Run Time Meter Start/Stop ____________/_____________

All Network devices are configured IAW most current 4.5.x version of IBCS plus any applicable FECs

Run Name is of the form:

MEI#_Run_[number]_[yyyymmdd]

Test Configuration:

1 Relay UUT

Verify UUT per Hardware Connections for Test Configuration (See Figure 24. Sentinel Test Configuration (Relay IFCN Connection via HRFU))

****CAUTION****

Verify by visual inspection that all equipment has been properly grounded to ensure proper operation and prevent an electrical hazard for the equipment or operator. See grounding steps below.

MEI HW is ground to a common facility ground

NOTE: ESD procedures require the operator to wear a wrist strap with the clip end connected to a ground point. HDD / SDD are to be stored in anti-static bags when not installed. Drives should never have direct contact with a metal safe drawer, even if in an anti-static bag.

· Two grounds from PSS to trailer ground point

· One ground from Generator to trailer ground point

· Switch AC INPUT to ON

· Switch OUTPUT switch to ON

Configure BPU and HRFU

1. Main (CB 5)

2. PDU (CB 1)

3. PFPU (CB 2)

4. HRFU (CB 3)

QA witness

If Spectracom Timing Unit “SYNC” LED remain red or the display does not display “Strat=1 Sync=Y” after 30 minutes do the following on the Timing Unit:

· Press one of the white DIRECTIONAL ARROW keys to enter the menu

· Use white directional arrow key to navigate to SYSTEM then press the GREEN CHECK button

· Use white directional arrow keys to navigate to CMD then press the GREEN CHECK button

· Use white directional arrow keys to change the setting to REBOOT then press the GREEN CHECK button

· An APPLY message will appear, press the GREEN CHECK button to apply

· Wait to verify the Timing Unit starts booting

· Continue waiting until display shows “Strat=1 Sync=Y”

If SCIM displays GPS lock failed or GPS unlocked do the following:

· Cycle power on the IGRM using the Internal Circuit Breaker panel on inside of the Network Enclosure. (It is the 5 amp switch; forth from the left. See figure to the right.)

· On the front panel turn FUNCTION knob to LAT/LON and push (SCIM reads LAT/LON ENTRY)

· Enter coordinates “20000000”

· Turn CHARACTER knob (center) to select character position

· Turn CURSOR knob (left) to change blinking character

· Push CHARACTER knob five (5) times until SUCCESS LOCATION SET is displayed

· Turn FUNCTION knob (right) to OPER and push in

Amp Switches

Spectracom Timing Unit displays “Strat=1 Sync=Y”, SYNC LED is green, and the FAULT LED is extinguished

SCIM displays GPS UNLOCKED then changes to LOCKED after a short period of time QA witness

NOTE: If BPU stays solid red reset the BPU by switching TX-ENABLE-RESET to RESET. Switch will return to original position automatically.

Configure KG-250

****WARNING****

Ensure KG-250X has been loaded with appropriate test keys prior to performing test. Check the latest configuration documentation to verify that the KG-250X has been loaded with the correct keys.

CIK must be provisioned SECRET before use

Insert the correct Crypto Ignition Key (CIK) into the KG-250X and press KG-250X POWER button Wait until the ALARM LED extinguishes and the PWR/READY LED turns green.

Turn PFPU On

1 PPS – blinking at 1 sec intervals

CRYPTO KEY

XMIT ENABLE

1 LINK

NOTE: SYSTEM FAIL LED should be extinguished. If it is blinking red ensure Timing Unit is sync’d and IGRM is displaying GPS locked and wait for LED to extinguish. If solid red and SCIM displays GPS locked, reset the BPU and wait for LED to extinguish.

A-Side Interface Panel Network Connectivity Table 42. A-Side Interface Panel Network Connectivity

Test Conduct:

Attempt # __________________________

Date of Run _________________________

Test Conductor ______________________

Test Operator _______________________

QA Witness _________________________

Gov Witness _________________________

Other Witness _______________________

IFCN Relay SN ______________________

Run Name is of the form:

Test Configuration:

1 Relay UUT

IPTA ST2

Media converter and cables (Ethernet and TFOCA) Figure 25. A-Side Interface Panel Network Connectivity

A-SIDE INTERFACE RED PING TEST

· Log on to ST2

· Execute Table 32. A-Side Interface Panel Network Connectivity

· In the terminal window

· Type cd /usr/bin/sepTest

· Type ls –al

· If redSepResults_Relay(MEI Number).txt or redSepResults_Relay(MEI Number).txt.md5 files exist type rm redSepResults_Relay(MEI Number)*

· Type sudo ./sepTest.sh to start script

· Type MEI number when prompted

J1 SENSOR – RED PORT

NOTE: TFOCA cable colors may vary. The S*-TX* / P*-RX* labels take precedence over cable color.

Then press Enter on keyboard

· Connect P1-RX1 Orange fiber to RX on test media converter

· Connect S1-TX1 Blue fiber to TX on test media converter

Then press Enter on keyboard

NOTE: If the test fails script will prompt the user to check connections then press Enter to repeat this check. The script will only recheck the connection once before continuing to the next step.

press Enter on keyboard

· Connect P2-RX2 Brown fiber to RX on test media converter

· Connect S2-TX2 Green fiber to TX on test media converter

Then press Enter on keyboard

NOTE: If the test fails script will prompt the user to check connections then press Enter to repeat this check. The script will only recheck the connection once before continuing to the next step.

J2 LAUNCHER 1&2 – RED PORT

Then press Enter on keyboard

· Connect P1-RX1 Orange fiber to RX on test media converter

· Connect S1-TX1 Blue fiber to TX on test media converter

Then press Enter on keyboard

NOTE: If the test fails script will prompt the user to check connections then press Enter to repeat this check. The script will only recheck the connection once before continuing to the next step.

press Enter on keyboard

· Connect P2-RX2 Brown fiber to RX on test media converter

· Connect S2-TX2 Green fiber to TX on test media converter

Then press Enter on keyboard

NOTE: If the test fails script will prompt the user to check connections then press Enter to repeat this check. The script will only recheck the connection once before continuing to the next step.

J3 LAUNCHER 3&4 – RED PORT

Then press Enter on keyboard

· Connect P1-RX1 Orange fiber to RX on test media converter

· Connect S1-TX1 Blue fiber to TX on test media converter

Then press Enter on keyboard

NOTE: If the test fails script will prompt the user to check connections then press Enter to repeat this check. The script will only recheck the connection once before continuing to the next step.

press Enter on keyboard

· Connect P2-RX2 Brown fiber to RX on test media converter

· Connect S2-TX2 Green fiber to TX on test media converter

Then press Enter on keyboard

NOTE: If the test fails script will prompt the user to check connections then press Enter to repeat this check. The script will only recheck the connection once before continuing to the next step.

J4 LAUNCHER 5&6 – RED PORT

Then press Enter on keyboard

· Connect P1-RX1 Orange fiber to RX on test media converter

· Connect S1-TX1 Blue fiber to TX on test media converter

Then press Enter on keyboard

NOTE: If the test fails script will prompt the user to check connections then press Enter to repeat this check. The script will only recheck the connection once before continuing to the next step.

press Enter on keyboard

· Connect P2-RX2 Brown fiber to RX on test media converter

· Connect S2-TX2 Green fiber to TX on test media converter

Then press Enter on keyboard

NOTE: If the test fails script will prompt the user to check connections then press Enter to repeat this check. The script will only recheck the connection once before continuing to the next step.

J5 LAUNCHER 7 – RED PORT

Then press Enter on keyboard

· Connect P1-RX1 Orange fiber to RX on test media converter

· Connect S1-TX1 Blue fiber to TX on test media converter

Then press Enter on keyboard

NOTE: If the test fails script will prompt the user to check connections then press Enter to repeat this check. The script will only recheck the connection once before continuing to the next step.

J6 LAUNCHER 8 – RED PORT

Then press Enter on keyboard

· Connect P1-RX1 Orange fiber to RX on test media converter

· Connect S1-TX1 Blue fiber to TX on test media converter

Then press Enter on keyboard

NOTE: If the test fails script will prompt the user to check connections then press Enter to repeat this check. The script will only recheck the connection once before continuing to the next step.

DISCONNECT AND HARVEST RED TEST RESULTS

· Type sudo chmod 775 red*

· Type md5sum redSepResults_Relay(MEI Number).txt > redSepResults_Relay(MEI Number).txt.md5

· Type sudo chmod 775 red*

· Type ls -al

· Type ssh security

· Type cd /mnt/DataTransfer/Data/(MEI Number)

· If this is a test dry run then type ls -al

· If a dryRun subdirectory does not exist then type mkdir dryRun

· Type sudo chmod 775 dryRun

· Type cd dryRun

· Type exit

· Type cd /usr/bin/sepTest

· Type scp redSepResults_Relay(MEI Number)* username@security: /mnt/DataTransfer/Data/(MEI Number)</dryRun> if test is a dry run

· Type ssh security

· Type cd /mnt/DataTransfer/Data/(MEI Number) </dryRun> if test is a dry run

· Type ls -al Verify redSepResults_Relay(MEI Number).txt and redSepResults_Relay(MEI Number).md5 files exist

QA witness

· Type md5sum –c redSepResults_Relay(MEI Number).md5

Automatic Software Initialization Check Table 43. Automatic Software Initialization Check

Test Conduct:

Attempt # __________________________

Date of Run _________________________

Test Conductor ______________________

Test Operator _______________________

QA Witness _________________________

Gov Witness _________________________

Other Witness _______________________

IFCN Relay SN ______________________

Run Name is of the form:

Test Configuration:

1 IPTA / EOC

1 IFCN Relay (The UUT)

Check OpenSAF Status on IFCN Relay

· Right click on desktop

· Click on Open Terminal

· Type ssh localadmin@<IPv6 address of relay>

· Enter password

NOTE: UUT IPv6 addresses and passwords are unique and will be provided separately prior to testing.

· Type cd /opt/integ/tools

· Type./statusIBCS All services show INSTANTIATED / IN-SERVICE / ENABLED

IBCS software is running. Record initial IBCS status.

IBCS Status

QA witness

· Type ./stopIBCS

· Type watch ./statusIBCS

· Type ctrl + c after services have stopped

· Type ./startIBCS

· Type watch ./statusIBCS

· Type ctrl + c after services have started All services show INSTANTIATED / IN-SERVICE / ENABLED

OpenSAF is now running QA witness

PATRIOT Functionality & Alt Media Table 44. PATRIOT Functionality & Alt Media

Test Conduct:

Attempt # __________________________

Date of Run _________________________

Test Conductor ______________________

Test Operator _______________________

QA Witness _________________________

Gov Witness _________________________

Other Witness _______________________

IFCN Relay SN ______________________

Run Name is of the form:

Test Configuration:

1 IBCS Relay (controlling 7 PATRIOT Launchers connected to the IFCN via Alt Media TFOCA. See Figure 21. PATRIOT Launcher & Alt Media Force Laydown) Figure 23. PATRIOT Run –Test Configuration (Relay IFCN via Alt Media) 1 EOC with PATRIOT RIU (IPTA simulated) 1 PATRIOT Launcher attached to UUT (IPTA simulated)

Models & Simulations:

ITEx simulates all sensors and launchers. A multi-threat, multi-launcher dynamic test case scenario is used in which hostile threats are tracked by ASoS PATRIOT, and which incorporates PAC-2 missiles types (GEM, GEM-C, GEM-T) as well as PAC-3 missile types (PAC-3, MSE) using all TBM subclasses and ABT subclasses from the CIE events.

Distributed engagement authority, Auto Command Processing Control set to OFF for all the EOC, the EOC has Identification Authority. AIR is semi-automatic and SPACE is Automatic. Method of fire is Ripple for TBM and Shoot-Look-Shoot-Look-Shoot for ABT.

Test Case Number: TC09 TC Common Name: Multi-Threat Multi-Launcher Dynamic Defense Plan: TC09.xml.idd ITEx XML File and Path Location: input/scenarios/IBCS/Root/Dynamic/Root.xml

NOTE: TC09 has multiple EOC, Relays, PATRIOT RIUs, PATRIOT Launchers, and Sentinel Radars, but only EOC 52032 (simulated) with PATRIOT RIU (simulated), the Relay under test, and PATRIOT launchers (simulated) will be used.

Connect Relay to IPTA (IFCN Alt Media via TFOCA)

· Connect one end of the TFOCA cable to J7 Alt Media 1 on the UUT A-Side Panel (Note that J8 Alt Media 2 functions identically)

· Connect the other end of TFOCA cable to the IPTA Alt Media 1

NOTE: Alt Media 2 works identical to Alt Media 1 and is a suitable substitution on the IPTA

· Open front panel door to Relay Network Enclosure

· Set BPU switch to STBY (see Figure 210. BPU)

Connect Relay to Simulated PATRIOT Launcher

· Connect P1-RX1 Orange fiber to RX on test media converter

· Connect S1-TX1 Blue fiber to TX on test media converter

Configure Black Routers for Alt Media Connections

Disable IPTA Black Router Tunnels & Enable Alt Media Ports

· Connect Cisco interface cable from serial port on Black / unclassified laptop to “CON” port on Black Router maintenance port (see Figure 29. Network Enclosure Interior View)

· Log onto laptop

· Open a terminal windows and type sudo minicom

· Hit enter until Black Router requests User ID

· Type User ID then password

NOTE: IPTA User ID and passwords will be provided separately prior to testing.

· Open the “IPTA_Alt_Media_Enable.txt” file on the laptop

· Select all the contents of the file and type Ctrl + c to copy them

· Left click on Minicom window

· Right click in the Mincom window to paste the file contents in and execute them

Note: the following commands were issued above to close the Black Router tunnels:

· conf t

· int tunn10

· shut

· exit

· int tunn11

· shut

· exit The following commands were issued above to open Alt Media ports 1 & 2:

· int gig 0/0/1

· ipv6 pim

· no ipv6 ospf 2 area 0

· ipv6 ospf 1 area 0

· ipv6 traffic-filter IBCS_Black in

· ipv6 traffic-filter IBCS_Black out

· no shut

· exit

· int gig 0/0/2

· ipv6 pim

· no ipv6 ospf 2 area 0

· ipv6 ospf 1 area 0

· ipv6 traffic-filter IBCS_Black in

· ipv6 traffic-filter IBCS_Black out

· no shut

· end gig 0/1 corresponds to Gigabit Ethernet Alt Media 1 and gig 0/2 to Gigabit Ethernet Alt Media 2 on the Relay Black Router

These commands are not committed to memory, so a router reboot / power cycle sets the routers back to the original settings.

· sh int tun 10

· sh int tun 11 The following responses are received:

· Administratively Down

· Administratively Down QA witness

· Close the “IPTA_Alt_Media_Enable.txt” file

· Close the Minicom window

· Disconnect the Cisco cable from the Black Router

Disable Relay Black Router Tunnels & Enable Alt Media Ports