Attachment 0004b - Relay Acceptance Test Procedures_FINAL.docx

For Official Use Only Attachment 1 Integrated Battle Command System (IBCS) Integrated Fire Control Network Relay (IFCN) Acceptance Test Procedures – IFCN Relay 14 Jul 2020

For Official Use Only

IBCS-A248-001

18 April 2018

For Official Use Only Printed document is reference document only. Verify document date with on-line system.

Copyright 2020 Northrop Grumman Systems Corporation.

For Official Use Only Table of Contents

List of Figures

List of Tables

Table 5-1. Test Tools and Associated Documentation ………………………………………… 24

For Official Use Only Scope The objective of this Acceptance Test Procedure (ATP) is to provide the detailed test steps necessary to demonstrate key functionality of the Integrated Fire Control Network Relay and to confirm conformity of integrated hardware and software end items with the qualified baseline. The qualified baseline is the successful integration of the IFCN Relay’s hardware and 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, the IFCN Relay’s 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 ATP.

IBCS IFCN Relay The 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 Fires Mission Command (AIFMC) 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 Plug & Fight enabled weapons and sensors. The IFCN consists of network components within the two Major End Items (MEIs), the EOC and IFCN Relay, 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 Computer Software Configuration Items (CSCIs) within software builds (see Figure 1‑1 for an illustration).

Figure 1‑1. IFCN V2 Relay

The power distribution box on an IFCN relay (see Figure 1-2. Power Sub-System (PSS) & Battery) includes an A/C In circuit breaker that, when off, allows for connecting power to the Relay without putting power into the system. The D/C Out circuit breaker will also keep power from running to the system.

Figure 1-2. Power Sub-System (PSS) & Battery

The IFCN Network enclosure and the Plug & Fight Processing Unit (PFPU) are the heart of the IFCN relay. The network enclosure (see Figure 1-3. Network Enclosure Exterior View and Figure 1-4. Network Enclosure Interior View) contains the network equipment including switches, the Baseband Processing Unit (BPU) radio, the encryption device, and the GPS timing unit that drive the relay.

Figure 1‑3. Network Enclosure Exterior View

Figure 1‑4. Network Enclosure Interior View

During normal operations, the network enclosure remains closed due to environmental concerns. Thus there are signal entry panels for the network enclosure. The BPU radio connects to the Highband RF Unit (HRFU) on the mast of the EOC via an RF cable, a data/control cable, a power cable, and a ground back to the relay trailer (see Figure 1-5). Network Enclosure & Signal Entry Panel). These panels also house the PFPU connections.

Figure 1‑5. Network Enclosure Signal & Power Panels

The A-Side interface panel (see Figure 1-6. A-Side Interface Panel) contains the connections from the network enclosure to the different A-Sides that talk to IBCS. There is one sensor and eight launcher ports along with the black side Alt. Media Ports.

Figure 1‑6. A-Side Interface Panel

EOC Lite An EOC Lite (see Figure 1-7. EOC Lite) will be used as the C2 to test A-Side to A-Side communications during the Acceptance Test. An EOC Lite is operationally equivalent to an IBCS EOC but does not include tactical radios. Therefore, it cannot be used to test radio to radio communications nor does it check functionality of all the hardware components.

Figure 1-7. EOC Lite

Additional Test Equipment In addition to the EOC Lite, the following items are needed in order to meet the AT requirements as identified in the document.

Table 1-1. Additional Test Equipment

Test Configurations Test Diagrams

Figure 2-8. FT3 via Alt. Media

Pretest Setup Grounding The following steps should be taken prior to powering up any equipment to ensure proper a common ground is established to prevent any harm to equipment damage.

Table 3-2. Grounding of Test Articles

Verify Test Articles Grounding

****CAUTION****

Prior to connecting commercial shore power or applying power to the EOC systems, verify by visual inspection that all equipment has been properly grounded and thresholds are IAW MIL-STD-464A, dated, 19 December 2002, to ensure proper operation and prevent an electrical hazard for the equipment or operator. The thresholds are 10 mOhms or less for inside the shelter and 20 mOhms or less for outside the shelter.

Relay HW is ground to a common facility ground

Relay is grounded to common ground

Test Procedures Power On

Table 4-3. Hardware Power Up

Verify UUT per Hardware Connections for Test Configuration (See Error! Reference source not found.)

****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.

Relay 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 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

Automatic Software Initialization Checkout

Table 4-4. Automatic Software Initialization Check

Test Configuration:

Figure 2-3. FT3 via Alt Media

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

Air Defense Acceptance Test

Table 4-5. Air Defense Functionality

Test Configuration: Figure 2-8 FT3 via Alt Media

Start FT3 Test

NOTE: IBCS software must be installed to complete this test.

NOTE: Operator Procedures needed for Test Tools are listed in Reference Section

QA witness

QA witness

QA witness

Software Shutdown and Data Harvest Table 4-6. Software Shutdown and Data Harvest

SHUTDOWN – Shutdown IBCS Software on IFCN Relay

· Right click on desktop

· Click on Open Terminal

· Type ssh –X –o ‘ServerAliveInterval=60’ localadmin@<IPv6 address of relay>

· Enter password

· Type cd /opt/integ/tools

· Type ./stopIBCS

· Type watch ./statusIBCS

· Type ctrl + c after services have stopped

Harvest Logs on Relay

· Type ssh –X –o ‘ServerAliveInterval=60’ localadmin@<RelayIPv6Address>

· Enter password

· Type cd /opt/integ/tools

· Type ./runHarvester –A –d <relay_harvest_archive_name>

· Type cd /data_local/logs

· Type ls –al

· Type cd <relay harvest archive directory name>

· Type ls –al

· Type md5sum <relay_harvest_archive_name.tar> > <relay_harvest_archive_name.tar.md5>

NOTE: Replace <relay_harvest_archive_name> with “MEI#_ Relay_[yyyymmdd]_ATP#”

UUT data is harvested and md5 checksum created

Message “Harvest has completed successfully and is stored at, <archive_name>” received QA witness

Archive Relay Test Results

· Type ssh –X –o ‘ServerAliveInterval=60’ bs1

· Type cd /data_local/logs/

· Type scp -r localadmin@[<relay IP address>]:/data_local/logs/<MEI Archive Name> .

· Type ssh –X –o ‘ServerAliveInterval=60’ security

· Type cd /mnt/DataTransfer/Data/<MEInumber> (add “/dryRun” if harvest is from a dry run)

· Type scp -r username@bs1:/data_local/logs/<MEI#_Acceptance_Test Relay_[yyyymmdd]_Run#> .

· Type cd /mnt/DataTransfer/Data/<MEInumber> (add “/dryRun” if harvest is from a dry run)

· Type cd <relay_harvest_archive_name>

· Type sudo chmod 775 *

· Type md5sum –c <relay_harvest_archive_name>.md5

Clean Logs on Relay

· Type ssh –X –o ‘ServerAliveInterval=60’ localadmin@<RelayIPv6Address>

· Enter password

· Type cd /opt/integ/tools

· Type ./cleanLogs –b

· Close terminal window

NOTE: At the completion of the harvest, the script will indicate if the harvest was successful and the clean may be performed, or if errors occurred that require attention.

Shutdown IBCS Software on EOC Lite

· Type ssh bs1

· Type cd /opt/integ/tools

· Type ./stopIBCS

· Type watch ./statusIBCS

· Type ctrl + c after services have stopped

· Type ssh bs1

· Type cd /opt/integ/tools

· Type ./stopBside

· Type watch ./statusBside

· Type ctrl + c after services have stopped

Harvest Logs on EOC LITE

· Right click on desktop

· Click on Open Terminal

· Type cd /data_local/logs/ibcs/ui/iuicli

· Type sudo chmod 775 *.png

· Type sudo chown root:ibcs *.png

· Type ls –al

· Type ssh –X –o ‘ServerAliveInterval=60’ bs1

· Type cd /opt/integ/tools

· Type ./runHarvester –d <EOC LITE_harvest archive name>

· Type ./runHarvester –A –d <EOC LITE_harvest archive name>

NOTE: Replace <EOC LITE_harvest archive name> with “MEI#_EOC LITE_[yyyymmdd]_ATP#

NOTE: At the completion of the harvest, the script will indicate if the harvest was successful and the clean may be performed, or if errors occurred that require attention.

· Type cd /data_local/logs/<EOC LITE_harvest archive name>

· Type md5sum –c <EOC LITE_harvest archive name>.tar.md5

Archive EOC LITE Test Results

· Right click on desktop

· Click on Open Terminal

· Type ssh –X –o ‘ServerAliveInterval=60’ 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 cd dryRun

· Type scp –r username@bs1/data_local/logs/<EOC LITE_harvest archive name> .

· Type ssh security

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

· If this is a test dry run then type cd dryRun

· Type cd <EOC LITE_harvest archive name>

· Type md5sum <EOC LITE_harvest archive name>.tar> > <EOC LITE_harvest archive name>.tar.new.md5

· Type diff <EOC LITE_harvest archive name>.tar.md5 <EOC LITE_harvest archive name>.tar.new.md5

Clean Logs on EOC LITE

· Type cd /opt/integ/tools

· Type ./cleanLogs –b

Hardware Shutdown

Table 4-7. Hardware Shutdown

SHUTDOWN

1- PFPU (CB2)

2- HRFU (CB3)

3- Power Distribution Unit (PDU)(CB1)

4- MAIN (CB5)

UUT is powered OFF

QA witness

· Remove SSD hard drives from the PFPU

· CIK from KG-250X in Network Enclosure

· Secure material in safe

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.

Supporting Documentation for Relay ATP Execution Operator Instructions for Test Tools The IFCN Relay ATP uses test tools during its execution. The test tools simulate components (e.g., radars and sensors) that are in the IFMC architecture. The document that explains how to set up and operate these test tools is named Operator Procedures For the Integrated Fires Mission Command (IFMC) Government System Integration Laboratory (GSIL) and will be provided as an attachment named “Operator Procedures For IFMC GSIL”.

image2.png image3.png image4.png image5.png image6.png image7.emf image8.PNG image9.PNG image1.wmf