ID05180024_Section_J_Attach_2_-_Existing_Equip_Plans-Checklist.pdf

STINGRAY BASEBAND OPERATIONAL CHECK TEST PLAN

INVENTORY

o Open the baseband rack case and the baseband support case – complete a full inventory based on the included vendor packing list and/or the company order sheet

Missing Items (list any missing items) Notes (damage, scratches, etc)

TEST SETUP

o Remove the baseband rack from the transit case o Remove the upper router and power supply to install the selected KG for testing o If test key is available, install KG that is to be delivered - follow “Online KG Test” o If no test key is available, install preconfigured lab KG and follow “Offline KG Test” o Apply prime power via the attached power strip – verify it is switched to the “ON” position o Power on all devices - verify that they power up correctly o Noting the power level of the UPS, remove power and verify the network gear remains powered o Restore input power and proceed

Notes/Issues

PHYSICAL CONFIGURATION

o Connect green CAT5 from “DISA Black” router to the upper router STINGRAY FA 0/1 o Connect green CAT5 from FA 0/2 on the upper router to the CT side of the KG o Connect red CAT5 from the PT side of the KG to FA 0/0 on the lower router o Connect red CAT5 from FA1/1 on the lower switch to the ACE Encoder Eth2 (lower port) o Connect red CAT5 from FA1/2 on the lower switch to the Server Enp2s0 (right port) o Connect red CAT5 from FA1/3 on the lower switch to the Kraken Eth1 (right port) o The remaining “RED” switch ports can be used to connect a host for device configuration

Section J Attachment 2 - Existing Equipment Plans & Checklists **Provided for INFORMATIONAL PURPOSES ONLY**

500 Corporate Point, Warner Robins, Georgia, 31088

AISRT-PLN-007 v1.0 26OCT2016

ONLINE KG TEST

o If test key is available, follow these procedures to configure the KG for operation o Power on KG to be tested – if the preconfigured lab KG is being used, skip to router config o Using a CAT5 cable, connect a host to the PT side of the KG o Verify that the configuration host is in the same subnet as the default/configured KG address o Using the default username/login, create web browser session with the KG 192.168.1.1 o login: admin PW: changeme – this will require the PW to change after login o Using the IWKS file, associate the CIK with the KG at the classification you intend to use o Configure the interface addresses to the test lab configuration o PT 45.45.2.5 / CT 45.45.1.5 / Mask 255.255.255.0 o Configure the KG to respond to ICMP/Pings o Configure the KG to “Copy” the fragment flag –prevents multicast packets from fragmenting o Load test key to “bat0” location o Create Security Association by inputting the multicast destination into the CT field o Create Tunnels for connection o There should be a single green light on the KG when it is ready to operate

OFFLINE KG TEST

o If no test key is available, follow these procedures to verify the KG is functioning at a basic level o Power on KG to be tested o Using a CAT5 cable, connect a host to the PT side of the KG o Verify that the configuration host is in the same subnet as the default/configured KG address o Using the default username/login, open an https web browser session with the KG (192.168.1.1) o Verify that the device has no faults

ROUTER/SWITCH CONFIGURATION

o Using lab laptop, connect the USB-serial adapter to the console port of the device o Using lab laptop, create a console connection for the device that is to be configured o Login to the device – the vendor default username is cisco / PW cisco o Perform a “write erase” command at the enabled prompt to erase the vendor test configuration o Type “reload” to reboot the router, replying “no” if the device asks you to save the configuration o During the reboot, answer “no” when asked to enter configuration mode o After reboot, load the appropriate router/switch configurations from the lab laptop (Red/Black) o Config files are on the desktop: Manual and Device Software/3. Network/Router and Switch Test Configs/Black or Red Test Configs (whichever is being configured) o Configuration loading is accomplished by pasting the text file into the console window o Enter “copy run start” to verify config is saved o Perform these steps on all devices to load the correct file (Red/Black, Router/Switch) o Verify “Black” connectivity by pinging the “DISA” Router and the CT side of the KG o Sim DISA Black is 14.14.1.1 / CT side of the KG is 45.45.1.5 (after KG configuration) o Verify Layer 1 and 2 connectivity to the “DISA” router (ESEMs / or hardwire CAT5) o Verify PIM neighbors on the black router using the “show ip PIM neighbor” – if not, Tshoot - the Stingray black router should have formed a neighborship with 14.14.1.1 o Verify “Red” connectivity by pinging the PT side of the KG o From the red router ping the PT side of the KG is 45.45.2.5 (after KG configuration) o From the lab laptop command prompt, ping the SVI on the router at 40.40.2.4 o If this ping is not successful, verify trunk and SVI status on the router o This deficiency has been corrected by assigning router fa0/3 to vlan40 o This configuration should allow multicast traffic to flow out of the STINGRAY o This completes the network setup for the test lab

MULTICAST SOURCE SETUP

o Using an HDMI source (laptop with HDMI, for example), connect to the ACE HDMI port o Play a video on the source device – if it is a short video, make sure to place the video in loop o Video source setup is complete

ACE ENCODER CONFIGURATION

o Using the lab laptop, directly connect laptop to Ethernet #1 port in the rear of the ACE o Configure lab laptop to 192.168.1.100 / Mask 255.255.255.0 o Open a web browser to connect to the default IP of the ACE - Port #1 is set to IP address https://192.168.1.1 - you will see the MGW Ace Login o If device is not accessible, press the reset button on the front panel to baseline (8 seconds) o Reconnect and proceed with configuration via the default IP and PW o The default password is 1qaz!QAZ o Using the “System” tab, config Ethernet 2 as 40.40.2.12/Mask 255.255.255.0/Gateway 40.40.2.4 o Click “APPLY” to save o CHANGE THE LAPTOP IP TO 40.40.2.100 o Connect laptop back to the Red Switch - reestablish connectivity to the ACE o Open a web browser to the new ACE Ethernet 1 IP of 40.40.2.12 o Provide an HDMI source to the rear panel of the ACE – any HDMI video source will work o See Multicast Source Setup for more detailed instructions o Using the “Channels” tab – Select Channel 1 at the top of the page – dark highlight is selected o Source=HDMI o Stream rate=2 Mbps o Video Codec Profile=4:2:2 o Encoding Format=1280X720@29.97 o Ethernet Interface=2, o Target 225.4.4.1 o Port 8208 o APPLY TO SAVE o Using the “Channels” tab – Select Channel 2 at the top of the page – dark highlight is selected o Source=HDMI o Stream rate=2 Mbps o Video Codec Profile=Main profile o Encoding Format=1280X720@29.97 o Interface Ethernet=2 o Target 225.4.4.2 o Port 8208 o APPLY TO SAVE o Using the “Channels” tab, play both Channel 1 and Channel 2 o The power, video, and STREAM light should be lit on the ACE front panel o If you intend on removing power, the configuration can be saved under the configuration tab o Using the lab laptop, verify feeds by running VLC and using Multicast Viewer Setup guide below o This complete the ACE encoder setup

MULTICAST VIEWER SETUP (LAN Viewer) o Using a lab laptop, connect to the “Red UVDS” Enclave o Start an instance of VLC Player o Under the Media Tab, click on Open Network Stream o Under network protocol enter udp://@225.4.4.1:8208 o This sets VLC to view the 225.4.4.1 stream from ACE Channel 1, Ethernet 1 o Start a second instance of VLC Player o Under the Media Tab, click on Open Network Stream o Under network protocol enter udp://@225.4.4.2:8208 o This sets VLC to view the 225.4.4.2 stream from ACE Channel 2, Ethernet 2 o Video viewer setup is complete o If video was started after VLC setup, restart VLC with the above configurations o If video is not seen, check stream light is green and stream is playing on the ACE o If the ACE is functioning properly, look for traffic indication on the switch lights o If video is still not seen, troubleshoot network routing/switching/PIM neighbors etc.

KRAKEN CONFIGURATION

o Verify power is enabled to the Kraken – if not, press the recessed power button on the front panel o Connect the lab laptop directly to Ethernet 0 (management port) o Configure the lab laptop IP to 10.5.1.100 Mask 255.255.0.0 (default Kraken network/mask) o Open a web browser on Internet Explorer to https://10.5.1.2 – the Kraken default IP address o Login with the default username of haiadmin and PW of manager o Warning: May have to power kraken off then on again to access 10.5.1.2 via browser o Navigate to Settings via the gear icon at the top of the page – o In Settings, select Licensing - verify validity is >10 years and allows HEVC/KLV and 4 Feeds o If license shows any errors, contact the vendor to reissue a valid license o Select network, and then Ethernet 1 o Configure the Ethernet 1 address on the Kraken to 40.40.2.11 / Mask 255.255.255.0 o Verify port is enabled (checked) and DHCP is disabled (unchecked) – APPLY TO SAVE o Either reboot or power cycle the Kraken to apply the new settings o Occasionally, the soft reboot button does not apply the new configuration o Reconnect laptop to the Red Switch port o Configure laptop NIC back to 40.40.2.100 / Mask 255.255.255.0 o After reboot, open a web browser to 40.40.2.11 and login with the above default information o Navigate to the Streaming icon (looks like SS) at the top of the main page o Navigate to the Input tab – add a new input – name the input Test Input o Set the source MPEG, the URL as udp://225.4.4.1:8208, and the interface as Eth1 o Apply to save o Navigate to the Transcoders tab – add a new transcoder – name the transcoder Test Transcoder o Select Format H.264 – this flips the H.265 input stream to H.264 (for the UV Server) o Apply to save o Navigate to the Output tab – add a new output – name the output Test Output o Set the output URL as udp://225.4.4.3:8208 o Set the interface output to Eth 1 to force it out of the correct interface o Apply to save o Navigate to the Streams tab – add a new stream – name the stream Test Stream o Set the stream parameters to build from Test Input, Output, and Transcoder built earlier o Apply to save o Start the feed and verify the status light for the feed on the GUI turns green o Kraken setup is complete – video should be at 225.4.4.3 on the UV Server (when configured)

UV SERVER CONFIGURATION

o Power up the M3 Server chassis – press the circular power button to boot the OS o For initial configuration, attempt to access the UV Web Portal via the web browser o Connect laptop directly to eno1 interface (left interface) for initial setup o Configure the lab laptop to 192.168.11.100 / Mask 255.255.255.0 o Open a web browser to 192.168.11.158 o When prompted, login with the admin@company user and PW in bold below o User admin@company.com and the PW of ZN3^prpmA66hlU}} o If the account is locked, use the “super user” section below o If UV Web Server is accessible, navigate to admin/appliances/NIC settings to change IPs o If UV server is not accessible, proceed to the bold “Alternative” options o DO NOT change eno1 interface address o Change enp2s0 interface to 40.40.2.10 Mask 255.255.255.0 – Save o Proceed to the “Using the lab laptop” portion in bold below o Alternatively, attempt to connect via a Putty SSH session to the default IP of 192.168.11.158 o Alternatively, you can connect using a VGA monitor and USB keyboard via the front panel o Using a VGA monitor, verify that the default DoD banner is loaded o Using a USB keyboard enter the username of “admin” and a PW of e.Ujys8eX^ttp00 o This accesses the back-end of the server for address interfacing o Type: sudo /apps/uvds/scripts/configure_ip_settings.sh Press enter o At the “Enter which interface” option, enter “enp2s0” – enter - This is the right Ethernet port o At the “Is this your primary interface” option, enter “Y” – press enter o At the “Enter IP address” enter the lab IP of 40.40.2.10 – press enter o Enter “Y” again to confirm when prompted o At the “Enter netmask” option, enter 255.255.255.0 – press enter o Enter “Y” again to confirm when prompted o You will see “IP change successful” and you should be able to ping the interface at 40.40.2.10 o Using the lab laptop, configure the laptop IP to be 40.40.2.100 (in the “Red” network subnet) o Open a web browser to https://40.40.2.10 o You should see the UVDS portal web page if the server is functioning normally o Select “Anonymous” on the upper right, and the “Login” o Consent to the DoD login banner o Enter the username of admin@company.com and the PW of ZN3^prpmA66hlU}} o Configure Feeds and Setup: On the admin side of the site, select feeds o Configure feeds udp://225.4.4.2:8208 and udp://225.4.4.3:8208 o The .2 feed should be named “Native 264” as it is directly from the ACE o The .3 feed should be named “Transcoded 265” as it is fed from the Kraken Transcoder o The .3 transcoded feed will not be available until the Kraken is setup o Logout and navigate to the Portal side of the site – verify feed tiles seen – play the feed to verify o The admin@company.com account does not show feeds

UV SERVER CONFIGURATION (continued)

UV SERVER FRONT END (WEB) “SUPER USER”

o Used to unlock admin@company.com account if it is inaccessible from the vendor o Warning: Can be used to make modifications that are not available to normal admin account o Access the portal via the default 192.168.11.158 IP address via a web browser o User: admin@teralogics.com o PW: 6NLzj.f.0cFk{qB

UV SERVER LINUX BACKEND GUIDE AND TOOLS

o Root Linux User – used to access feed (stream) analyzer, deactivate ports/firewall :

o User: teralogics PW: UGg7JBV4VbkyQR^[ o Type sudo su to access super user login prompt o Enter the same PW from the teralogics account to access root o After pressing enter, the prompt should change to “root” o Feed analyzer – troubleshoot streams - /app/utes/feedanalyzer/feedanalyzer/ -nDv [address] [port] o Enter analyzed multicast address, then port with a space and no colon between o Firewall Stop/Start (if firewall is suspected of blocking MC traffic) o service firewalld [enter for options or stop or start or restart] o Ethernet 2 Disable (right port - if traffic is only wanted on port 1) o /etc/sysconfig/network-scripts/if down enp2s0 o ifconfig command shows all interfaces and their assigned configurations o route command shows all routes assigned

UV SERVER ITEMS TO LOOK FOR

o enp2s0/Port 2 (right port) active – multicast traffic prefers this port when active o If this is not desired, perform port shutdown procedures under guide and tools section o User account “hotfix” to correct initial account login justification field – see hot fix procedures o Incorrect PW for admin@company.com account – use teralogics admin account to set/unlock

AISRT-PLN-008 v1.0 19MAY2017

STINGRAY FDMA CASE OPERATIONAL CHECK/TEST PLAN

o Open the FDMA rack case and the FDMA/ECU support case – complete a full inventory based on the included vendor packing list and/or the company order sheet

TEST SETUP

o Remove the front and rear storage covers for the FDMA case o If the test occurs outdoors, the ECU will need to be installed – this is optional for indoor lab use o Open top cover of case if operating indoors to permit cooling o When performing L-Band loop, configure the rear panel for H3H KA – max TX attenuation o Select maximum attenuation on the L-Band Distro front panel – max RX attenuation o This prevents overdriving the EBEM receive o When performing over-the-air test, configure rear panel for antenna that is in use o Connect primary power to UPS or wall outlet o Apply power to the FDMA case via the switch above J1 on the rear panel o Power on all devices - verify that they all power up correctly o Keep in mind that only 1 EBEM and one Novra is in use at a time (rear panel selectable)

CABLING CONFIGURATION

o For an over the air test, configure FDMA J7 and J8 to the antenna to be tested o For an L-Band loop or FDMA-FMDA test, connect J8 on one case to J7 on the other (TX to RX) o Connect J7 to J8 on the other case (RX to TX) o For final ESEM testing, either connect the J5/ESEM port to the baseband gear or to a lab laptop o For Novra/GBS testing, a dedicated Ethernet cable will need to connect to J9 or J10 (Novra LAN) o A DVB L-Band/RF source is also needed to feed the Novra

EBEM CONFIGURATION

o Verify primary power to the EBEM to be tested o If the modem is zeroized (active, bypass, fault lights blinking) you will need to bypass/enable encryption to proceed with configuration o If encryption is bypassed, it is recommended to enable encryption for the following procedures o Note: The test can proceed in bypass – this setting must to be the same on the remote modem o Note: Encryption is not required, but it is recommended to test the encryption functionality

ENABLE or BYPASS ENCRYPTION FROM ZEROIZED STATE o Place the modem in local mode by pressing the remote/local button - enables front panel o To bypass/enable encryption from a zeroized state, login to the Admin profile – PW 123456 o Change the Admin PW to 654321 o Change the User PW to 654321 o Input a new RNG Seed of all “1” until “100 percent” is seen – press enter – LAB RNG o Record EDC after entry o Input a new SMA Token of all “A” until the screen is filled – press enter – LAB SMAT o Record EDC output after entry – MUST MATCH DISTANT END!!!

o The SMA Token change will prompt a reboot o After the reboot login to the Admin profile, navigate to Encryption Control o Enable = Encryption ON, Disable = Encryption OFF o This will prompt another reboot – after reboot, the encryption bypass LED is lit if disabled o This will stay lit as long as encryption is bypassed o If encryption was enabled, all encryption LEDs are extinguished

ENABLE ENCRYPTION FROM BYPASSED STATE

o To enable encryption from bypassed state, login to the Admin profile – PW 654321 o Input a new RNG Seed of all “1” until “100 percent” is seen – press enter – LAB RNG o Record EDC after entry o Input a new SMA Token of all “A” until the screen is filled – press enter – LAB SMAT o Record EDC output after entry – MUST MATCH DISTANT END!!!

o The SMA Token change will prompt a reboot o After reboot login to the Admin profile, navigate to Encryption Control – verify Enable o After reboot, the encryption active LED is extinguished – it will blink when TX is enabled o This will go solid green when the encryption is active with another EBEM

MODEM CONFIGURATION

o Note: If encryption is enabled, login as the User with the new PW of 654321 to configure o Any changes to encryption will require a reboot to access the Admin profile o Note: If encryption is bypassed, login is not required to configure the modem

ESEM STATUS CHECK

o Modem power corresponds to cabling on rear panel – EBEM1 is the lower modem o Using the left/right arrows, navigate to the Monitor Local option – press down to access the menu o Press the left/right arrows until Expansion displays – press down to access the menu o Verify Expansion Type = ESEM o Verify Expansion Status = Ready o Verify ESEM Status = Online o If all these are valid, the ESEM is installed and ready for configuration in the following steps o Press Up arrows several times to navigate to the top menu

LOCAL CONTROL TERMINAL SETUP (LCT, EBEM GUI)

EBEM SETUP FOR LCT

o Verify primary power is applied to the FDMA case and the EBEM o Verify the M&C laptop (black laptop) is connected to the FDMA case LAN (rear panel J5 or J6) o Retrieve the current IP and serial address of the EBEM o Place EBEM into Local Mode via the front panel button o The IP of the EBEM M&C interface can be changed by the GUI once operational o To retrieve IP - Scroll left/right until Monitor Local is seen – press down 1x o Scroll left/right until interface is seen – press down 1x o Scroll left/right until TCP/IP is seen – press down 1x o Record IP address and Subnet Mask – this will be input to the LCT GUI – press up 1x o Scroll left/right until Serial is seen – press down 1x o Scroll left/right until Modem address is seen o Record Serial address – this will be input to the LCT GUI modem profile o Place the modem into Remote mode using the front panel remote/local button

M&C LAPTOP SETUP FOR LCT

o Download/install Java 1.6u23 32bit -jre-6u23-windows-i586– 64bit Java WILL NOT WORK o Locate/install Setup-EBEM_LCT_020104 – this is found in the Manuals Folder on the Desktop o Manuals and Device Software\RF Equipment\ViaSat EBEM\LCT GUI 02.01.04\LCT 02.01.04\Setup-EBEM_LCT_020104 o Double-click to install – follow prompts to install in default location o Choose to create a desktop icon o If the program starts, close it until the follow steps are complete o Locate the file C:\EBEM_LCT\system\run_ebem_lct_020104 o This is the batch file that points to the Java folder – it will need to be modified o Right-click and select edit – a text editor will open o Delete the current text in the file and insert the following:

PathTemp=%Path% Path=C:\Program Files (x86)\Java\jre6\bin;%Path% @title EBEM LCT 02.01.04 java -classpath .\EBEM_LCT_020104.jar;comm.jar ebem_lct.system.LCT_Client Path=%PathTemp% PathTemp= exit o Save the file and close the editor o Launch the LCT GUI from the desktop short, or by double-clicking the file that was edited o If the LCT fails to launch, the LCT installation and Batch file modification will need to be accomplished again using Windows 10 compatibility mode (right click on the LCT installer and select Troubleshoot Compatibility – Windows 7 compatibility mode should work

M&C LAPTOP SETUP FOR LCT…continued o On the LCT, locate the System tab – select TCP/IP for Control Interface – Apply and click OK o On the LCT, locate the Modem tab – Input any modem name/the previously recorded EBEM IP address and Serial Address, and the PW of the User PW of the modem – should be 654321 o Select Telnet as the Control Interface and then OK to apply and save the new profile o The newly created modem profile should be seen under the dropdown on the left of the LCT o Double-click on the modem to open an LCT session for the EBEM

CHANGING EBEM IP USING THE LCT

o Select the Configuration tab o Select Edit on the upper right radio button (options are Edit/Monitor) o Using the dropdown menu on the upper left of the window, select Interfaces o Under TCP/IP properties, input the desired TCP/IP parameters o The modem will require a new configuration to be saved (Save Config at bottom) o To apply the settings, click Load – this will apply the IP (and other) changes made o If the IP parameters are changed, the modem profile must be updated to reestablish connectivity

CHANGING EBEM SETTINGS USING THE LCT

o Select the Configuration tab o Select Edit on the upper right radio button (options are Edit/Monitor) o Using the dropdown menu on the upper left of the window, select the desired parameter to edit o Service affecting parameters will require a configuration save/load process to apply new settings

MODEM CONFIGURATION – MODULATOR

Note: The following parameters / verbiage follow the front panel – LCT parameters are identical, but input field verbiage may vary slightly (Ex. Ethernet Rate vice ESEM rate) o Modem 1 or 2 power corresponds to cabling on rear panel – EBEM1 is the lower modem o Navigate to Configuration by pressing the left/right arrow – press down to access the menu o Press the left/right arrows to Edit – press down to access the menu o Navigate to Modulator – press down to access the menu o Input or verify the following parameters:

o TX Mode: EBEM o TX Sub Mode: Turbo o TX Modulation: OQPSK o TX Serial Rate: 0.000 kbps (this disables serial data – ESEM data only) o TX Ethernet Rate: 5000.000 kbps (this sets the ESEM rate) o TX Inner Code: Turbo ½ o TX Outer Code: None o TX Intlvr: 0 o TX Diff Encoder: OFF o TX Scrambler: Sync o TX O/H Chan: Off o TX Freq: 1500MHz o TX Power: -35dBm o TX Data Loss: Maintain Sync o TX Embed Chan: On o TX Timing Source: Internal o TX Enable: On (TX will enable after configuration is saved/applied) o TX setup is complete - Press Up arrow once to prepare for RX setup if using front panel configuration method.

MODEM CONFIGURATION –DEMODULATOR

Note: The following parameters / verbiage follow the front panel – LCT parameters are identical, but input field verbiage may vary slightly (Ex. Ethernet Rate vice ESEM rate) o Navigate to Demodulator by pressing the left/right arrow – press down to access the menu o Using the left/right arrows, navigate through the menu for configuration o Input or verify the following parameters:

o RX Mode: EBEM o RX Sub Mode: Turbo o RX Modulation: OQPSK o RX Serial Rate: 0.000 kbps (this disables serial data – ESEM data only) o RX Ethernet Rate: 5000.000 kbps (this sets the ESEM rate) o RX Inner Code: Turbo ½ o RX Outer Code: None o RX Intlvr: 0 o RX Diff Encoder: OFF o RX Scrambler: Sync o RX O/H Chan: Off o RX Freq: 1500MHz o RX Embed Chan: On o RX Buffer Operation: On o RX Buffer Size: 200000 o RXB RECTR Time: 0 o RX Timing Source: Internal o Equalizer: Off o RX Enable: On (TX will enable after configuration is saved/applied) o RX setup is complete - Press Up arrow twice to prepare for saving/applying configuration if using front panel configuration method.

FRONT PANEL MODEM CONFIGURATION SAVING AND LOADING

o Navigate from the Demodulator menu to the Configuration menu by pressing the Up Arrow o If the modem prompts “Lose Changes”, press the Down arrow to return to the lower Menu o Under the Configuration menu (Edit, Load, Save. Recall) – scroll to Save o Access the Save option by pressing the Down arrow o Save the modified configuration to any configuration other than the current (current has a * by it) o Note: The modem will not permit saving over the active configuration o Note: The following action will overwrite all existing data in the selected save position o Scroll to an offline configuration that is not needed and press enter o This will allow naming the configuration (will be named “Temp” if no name is input) o Once the configuration is named, press enter to save o To apply the newly created configuration, navigate to the Load option on the Configuration menu o Press Down to enter the load menu o Scroll the newly created configuration o Press Enter to apply o The Edit/Save/Load procedures must be accomplished for any configuration change o The EBEM is now configured for operation – the front panel TX On light should be lit

EBEM and ESEM TEST o Verify both FDMA cases have been configured with the above procedures o The active EBEM in each case should show:

o TX On o IF Lock (indicates modem TX/RX parameters match) o Data Lock (indicates ESEM and encryption parameters match) o Encryption Active light is now solid (indicates end-to-end encryption is valid) o The ESEMs in each FDMA are now connected and communicating o The test can proceed by connecting a host to the FDMA ESEM port to ping, or by integrating the

ESEMs into the lab topology between the Stingray black router and simulated DISA enclave (one ESEM to DISA enclave, one ESEM to Stingray black router) o If the modems are not communicating, run the following troubleshooting:

o No IF Lock – remove front panel attenuation in 1dB increments until 10 dB have been removed. If IF lock is still not seen after 10dB are removed, return the attenuation to its original level and verify Modulator and Demodulator configuration on each EBEM o IF Lock, but no data lock – This indicates modems are communicating at the RF/IF level, but there is likely an issue with encryption settings – input SMAT from the encryption setup o If all these setting have been verified, the modem TX power may need to be raised. Perform this function by referencing the Modulator configuration section. Change Modem power to -20dBm. Edit/Save/Load to apply. Perform the “NO IF Lock” Section again

**Proceed to Novra Setup on the next page

NOVRA SETUP

o Verify primary power is applied to the FDMA case and to the Novra that is to be tested o The Novra receivers are configured as cold spares – only one is powered at a time o The online Novra is selected via the Novra Unit Select Switch on the rear panel o From the front of the case, the left Novra is powered with the switch in the “O” position o The left Novra is interfaced with using the lower Novra LAN port on the rear panel o From the front of the case, the right Novra is powered with the switch in the “I” position o The right Novra is interfaced with using the upper Novra LAN port on the rear panel o Locate the Novra discovery software in the soft Manuals library under the video devices folder o While connected to the Novra LAN port, run the discovery software – Novra Mgmt V6 o Once the Novra IP is discovered, match the configuration laptop to the Novra IP/Subnet o Run the software again and click on the device – a password prompt will be displayed o Click on the discovered device to open the configuration for the device o Login with the default PW of Novra-S2 o This completes the Novra ops check if no GBS network data is available o Further testing and configuration requires satellite access or a DVB encoder o The device IP can be changed by selecting the Network Interface Icon o If the IP information is changed modify the M&C laptop IP and reconnect o Select the Satellite option on the Interfaces menu o Verify Automatic is selected for Symbol rate o Verify LNB Power is disabled (LNB receives power from the MeODU) o Select LNB Parameter – modify the L.O. to be 0 (this allows L-Band frequency input) o Input RF Frequency at L-Band in the RF Freq. field (L.O. at 0 permits this o The L-Band frequency will be cutsheet o Select DVB-S as the Search Mode o Select Apply to save settings o If Satellite parameters are correct and the antenna is setup, the Signal/Data lights are lit o Under the IP Data menu, select Content o In the PID field (Packet Identification code), input the PID from the GBS cutsheet o Click Add – the new PID(s) will be displayed in the window o Select Apply to save the configuration o This completes NOVRA setup o Keymat AND KG routes will need to be configured for viewing of video data

AVCOM SETUP

o Verify primary power is applied to the FDMA case and to the L-Band Distribution Assembly o Connect M&C laptop to ESEM or EBEM interface (FDMA LAN) o Start AVCOM software o When software boots for the first time, select control method as Ethernet, click next o If software has been previously setup, select “Configure” and then “Ethernet Connection” o Skip to Select Scan for Devices o Select Ethernet Direct, as the M&C laptop is on the same LAN as the AVCOM analyzer o Select Scan for Devices or Configure/Ethernet/Scan for devices o This will take a moment to display the current AVCOM IP address o If IP change is required, use the recommended IP or enter new address into the “Change IP” field o Select change o Select “Update” to place the new device IP into the device list o Edit (if required) and/or record the “Connecting Port” number o Select “Save Setting to Analyzer” o Exit the Configure Ethernet utility o Select Configure/Spectrum Analyzer List o Input the desired name for the Analyzer profile into the “New SA List name” field o Select “LAN” as the connection method o Input the IP that was selected o Input the port number that was saved to the device o Select “Add” to create/save the profile o Close the Spectrum Analyzer List utility o From the main GUI page, locate the Spectrum Analyzer List on the right side o Click on the field to select the profile that input o Select “Run” to start the analyzer – this may take 2 or 3 Run/Stop cycles o Once the indicator is green, the SA is operational – if not, verify settings

AISRT-PLN-009 v0.1 19MAY2017

STINGRAY ANTENNA OPERATIONAL CHECK/TEST PLAN

o Open the antenna and all support cases – complete a full inventory based on the included vendor packing list and/or the company order sheet

PRE-TEST REVIEW

o During the antenna operational check, locate the vendor antenna test data and review to verify everything is “Pass” and that there are not outstanding issues with the system.

o For Hawkeye systems, send an email to the L3-GCS Engineer (scott.mccombs@L-3com.com) to request the data for Hawkeye Systems if the test result data is not located on the share drive o For GATR systems, send an email to the GATR PM Cyrus Wilson (cwilson@gatr.com) to request the data for Hawkeye Systems if this file is not located on the share drive o This file should also come on the antenna disc that is delivered with the antenna

TEST SETUP

o Follow the vendor manual to setup, deploy and acquire the satellite.

o Each antenna has a quick deploy card inside the antenna case to assist o The antenna will be setup in the open lot to the south of building 100 (if test is in Warner Robins) o Install antenna with clear line of site to 132 degrees azimuth and elevation of 39.5 degrees mailto:scott.mccombs@L-3com.com

AISRT-PLN-009 v0.1 19MAY2017

ANTENNA TEST

o The test relies on vendor test data to determine if the antenna is technically sound o This test check high level operational status of the antenna o Verify no fault lights and that everything powers up normally o With antenna at appropriate azimuth (GATR) or facing due south (Hawkeye), acquire satellite o This receive test will look for the WGS beacon at 1500MHz (L-Band) o The GATR will be acquired manually o The Hawkeye will auto acquire – use Reference tuning and Beacon Tuning for WGS5 @ -52.5 o Verify peak on the spectrum analyzer o Verify antenna radiation zone is clear o Rotate antenna toward cold sky (i.e 65 degrees) and enable TX power o GATR will need Wavestream software installed on the laptop o Provide a low power L-Band feed to drive the BUC/SSPA o This will verify basic operation of the SSPA/BUC o Disable TX o Antenna motion has been tested on the Hawkeye by using auto acquire o Following the included vendor procedures, tear down the antenna o This concludes the antenna operational test

AISRT-PLN-014 Draft

STINGRAY LAPTOP OPERATIONAL CHECK TEST PLAN

o Open the GETAC S410 laptop box and ensure all items are present to include laptop, battery pack, and power cord.

Missing Items (list any missing items) Notes (damage, scratches, etc)

Physical Inspection o Remove the laptop from box and insert battery and plug ac cord into outlet.

o Allow 4 hours for battery to fully charge before turning on laptop.

o Ensure laptop will properly power up.

o Is the Screen free from disfigurement, scratches, and damage?

o Are there any visible scratches, dents, or damage to the casing?

o Does the keyboard work properly?

o Any frays or damage to the AC charger?

Notes/Issues

Operating System o Verify GETAC S410 has Windows 10 Pro Installed o Verify that the Windows license is activated. (In some instances, you will need to connect to the internet to finish the Windows licensing activation)

AISRT-PLN-014 Draft

Software Installation and setup o Install “Manuals and Device Software” folder onto the laptop desktop. This folder of manuals and software was created specifically for the Stingray laptop and is maintained and updated in the lab.

o Go to “Manuals and Device software\6. Laptop Software o Install 7zip by double clicking on the 7z1602-x64 application file and follow basic setup procedures.

o Install “Mozilla Firefox” by double clicking on the Firefox Setup 48.0.2 file and follow basic setup procedures to include a desktop shortcut.

o Copy and paste “Putty” application to your desktop o Install “VLC player” by double clicking on the vlc-2.2.4-win32 application and follow basic setup procedures to include a desktop shortcut o Install “Flash player” by first ensuring you are online and double click the flashplayer23_xa_install application and follow basic setup procedures

Laptop “desktop background” and “lock screen” o Change desktop background by right clicking on the desktop and selecting “Personalize” o From the “settings” page select “background” then “Picture” to “Choose your picture” to

“Browse”

Setup AVCOMM Software

Setup EBEM LCT Software

//UNCLASSIFIED//

AISRT-FORM-036 v1.0 26MAY2017 //UNCLASSIFIED//

STINGRAY ANTENNA OPERATIONAL

CHECKILIST

Developed by: Sigma Defense Systems Inc.

500 Corporate Pointe

Warner Robins, GA 31088

STINGRAY ANTENNA OPERATIONAL CHECKILIST

Task Order #:

Testers:

Operational check date:

Description: This checklist verifies steps taken and purpose of operationally checking Stingray laptops IAW AISRT-PLN- 009 v1.0. A check under “Yes” or “No” will be placed accordingly to indicate status in each section. Any deviations, additional or integrated testing will be documented in the comments section.

1. Inventory

Yes (x) No (x) Comments Are there missing items (list any missing items)

Any damage, scratches

2. Pretest Review

Verified vendor antenna test data Requested missing test data from vendors

3. Test setup

Followed vendor manual to setup antenna

Antenna setup in open lot

4. Antenna test

Antenna powered on correctly Any fault lights Satellite acquired Receive test successful Peak verified on spectrum analyzer Antenna radiation zone clear Transmit power enabled Antenna motion tested Antenna torn down in accordance with vendor procedures

Total Ops check time (hours): __________________________________________________________

Testers/Engineers: ___________________________________________________________________

Program Manager Printed Name and Date: _______________________________________________

Program Manager Signature: ___________________________________________________________

AISRT-FORM-037 v1.0 26MAY2017 //UNCLASSIFIED//

STINGRAY BASEBAND OPERATIONAL

STINGRAY BASEBAND OPERATIONAL CHECKILIST

Operational check date:

Description: This checklist verifies steps taken and purpose of operationally checking Stingray laptops IAW AISRT- PLN-007 v1.0. A check under “Yes” or “No” will be placed accordingly to indicate status in each section.

Any deviations, additional or integrated testing will be documented in the comments section.

2. Test setup

All items removed for test setup KG installed/key configured Prime power applied All devices powered up correctly UPS power noted Input power restored

3. Physical configuration

Green Cat 5 from DISA Black connected

Green CAT5 from FA/02 on upper router connected to KG

Red CAT5 from PT side of KG connected on lower router

Red CAT5 from FA1/1 on switch connected to ACE Encoder

Red CAT5 from FA1/2 on switch connected to Server

Red CAT5 from FA1.31 on switch connected to Kraken

4. Online KG Test

Test Key available KG powered on Web browser login session successful

IP interface addresses configured Correct CIK associated with KG IP addresses configured on laptop Test key “fill” successful ICMP configured on KG Routes configured on KG Green operational light showing

5. Router/Switch Configuration

USB-serial adapter connected to the console port of the device

Console connection created for device to be configured

White erase command complete Reload on router complete Appropriate router/switch configurations loaded

Black connectivity verified Red connectivity verified

6. Multicast Source Setup

HDMI source connected to ACE HDMI port

SDI source connected to ACE SDI port

Video successfully played on loop to source device

7. ACE/Makito X Encoder Configuration

Lab laptop connected to port E1 on ACE (IP configured)

Ethernet 2 configured Laptop IP changed Laptop connected to red switch HDMI/SDI source provided to rear panel of ACE/Makito X

Channels selected and saved Streams successfully played Feeds verified using VLC

8. Multicast Viewer setup

Red UVDS Enclave connected Instance of VLC player successfully started

9. Kraken Configuration

Power enable to the Kraken Laptop connected to Ethernet 0 Laptop IP configured License verified Ethernet 1 configured on Kraken Laptop reconnected to red switch port

Laptop NIC configured and rebooted

Streaming source correctly set Transcoder added

Output URL set Stream parameters set

10. UV server configuration

M3 Server successfully powered on Initial configuration complete via UV Web Portal

Connection successful via Putty Successful connection using VGA monitor and USB keyboard via the front panel

Laptop IP configured Successful access to UVDS portal web page

Configured feeds and setup Logged out and verified feed tiles seen via Portal side of the site

Verified super user access Verified Linux backend guide and tools

Verified UV server justification hotfix

Total Ops check time (hours): ___________________________________________________________

Testers/Engineers: ____________________________________________________________________

AISRT-FORM-038 v1.0 26MAY2017 //UNCLASSIFIED//

STINGRAY FDMA OPERATIONAL

STINGRAY FDMA CASE OPERATIONAL CHECKILIST

Operational check date:

Description: This checklist verifies steps taken and purpose of operationally checking Stingray laptops IAW AISRT-PLN- 008 v1.0. A check under “Yes” or “No” will be placed accordingly to indicate status in each section. Any deviations,

2. Test setup

Front and rear storage covers removed

Was test conducted outdoors ECU installed L-Band loop configured on rear panel

Primary power connected to UPS or wall outlet

All devices powered up correctly

3. Cabling configuration

FDMA J7 and J8 configured Appropriate connections in accordance with test performed made for J7 and J8

J5/ESEM port connected to the baseband gear or to a lab laptop

Ethernet cable connected to J9 or J10 (Novra LAN) for NOVRA/GBS testing

Power verified for EBEM

4. EBEM configuration

Primary power verified Bypass/enable encryption required Bypass/enable encryption successful

Configuration complete ESEM Status check successful

5. Local Control Terminal Setup (LCT, EBEM, GUI) EBEM Setup for LCT

Power verified to FDMA case and the EBEM

M&C laptop (black laptop) is connected to the FDMA case LAN

Current IP and serial address of the EBEM retrieved

Modem correctly placed into Remote mode

6. M&C Laptop Setup for LCT

Java downloaded and installed EBEM install files located and installed

LCT GUI successfully launched from desktop

TCP/IP selected for Control Interface

Modem name and IP input Telnet selected as Control Interface

Newly created modem profile available on dropdown

LCT session opens for EBEM

7. Changing EBEM IP using the LCT

TCP/IP selected for parameters New configuration applied/saved Connectivity reestablished

8. Changing EBEM settings using the LCT

Desired parameters selected to edit Configuration saved/loaded

9. Modem configuration – Modulator

Modem placed in local mode Modulator configured (TX)

10. Modem configuration – Demodulator

Demodulator menu accessed Parameters verified Demodulator configured (RX)

11. Front panel Modem Configuration Saving and Loading

Configuration module accessed Modified configuration saved and loaded

EBEM successfully configured

12. EBEM and ESEM test

Both FDMA cases verified as configured

Host connected to the FDMA ESEM port to ping

ESEM integrated into the lab topology between the Stingray black router and simulated DISA enclave Modems communicating Primary power applied to FDMA case and Novra

Novra discovery software ran Device IP changed Satellite options selected PID information input Keymat and KG routes configured

12. EBEM and ESEM test

Both FDMA cases verified as configured

Host connected to the FDMA ESEM port to ping

ESEM integrated into the lab topology between the Stingray black router and simulated DISA enclave

Modems communicating case and Novra

Novra discovery software ran Device IP changed Satellite options selected PID information input Keymat and KG routes configured

13. AVCOM setup and L-Band Distribution Assembly

Ethernet selected as control method Ethernet Direct selected Scan for Devices selected Update selected to update new device IP in device list

Edit required Configure/Spectrum Analyzer List selected

Desired name for the Analyzer profile input Desired name located in list

Total Ops check time (hours): _________________________________________________________

Testers/Engineers: __________________________________________________________________

AISRT-RPT-001 v1.0

MEMORANDUM FOR

FROM: Sigma Defense Systems, Inc.

SUBJECT: STINGRAY Test Report Summary version#

1. Overview:

This Test Report and Summary documents testing of Stingray v# at SigDef Lab.

a. Event Type: Stingray Capability Test

b. Environment: Sigma Defense Lab

2. Participants: (Add names of all participants)

Participant Organization Participant Role Participant Name

3. Events: Stingray Capability Test

Tasks Dates Install & Test Document Verification Functional Test Integration Test

4. Product Description: The Stingray system provides an integrated, modular suite of equipment for forward deployed entities, allowing them to backhaul multiple high-definition (HD) Full Motion Video (FMV) feeds and other sensor data, while simultaneously providing a backhaul transport capability to bring theater intelligence data directly to strategic, operational and tactical customers. Expanded capabilities include, but are not limited to, (GBS Rebroadcast for disadvantaged users, Two-way Sensor Control, etc.) via small, add-on Enclaves.

5. Objectives: (List all test objectives and whether they were or were not met)

Met / Not Met

1. Verify install/power on each component using the Installation Procedures

2. Install/Configure components using set-up procedures

3. Execute Test Procedures

• AISRT-PROC-009

v1.0_Baseband Test Procedures

Tested: Failed:

• AISRT-PROC-010 v1.0_GETAC Laptop Configuration Proedures

Tested: Failed:

4. Redline and make updates to Installation and Test Procedures as required

6. Results and Issues: (List test results and issues)

a. BASEBAND TEST PROCEDURES:

1. Issue:

2. Issue:

3. Issue:

b. LAPTOP CONFIGURATION PROCEDURES:

1. Issue:

7. Documentation: What was reviewed and were there issues?

Documentation Name Results N/A

8. Summary:

What tests were completed? Are results acceptable? Major problems noted?

9. For additional information please contact Razina Tolbert, STINGRAY Project Lead, Sigma Defense Systems, Inc., 478-273-8633.

Bennett Campbell, CTR, SigDef

Stingray Project Manager

AISRT-FORM-039 v1.0 26MAY2017 //UNCLASSIFIED//

STINGRAY LAPTOP OPERATIONAL

STINGRAY LAPTOP OPERATIONAL CHECKILIST

Operational check date:

Description: This checklist verifies steps taken and purpose of operationally checking Stingray laptops IAW AISRT-PLN- 009 v1.0. A check under “Yes” or “No” will be placed accordingly to indicate status in each section. Any deviations,

2. Pretest Review

Verified vendor antenna test data Requested missing test data from vendors

3. Test setup

Followed vendor manual to setup antenna

Antenna setup in open lot

4. Antenna test

Antenna powered on correctly Any fault lights Satellite acquired Receive test successful Peak verified on spectrum analyzer Antenna radiation zone clear Transmit power enabled Antenna motion tested Antenna torn down in accordance with vendor procedures

Total Ops check time (hours): __________________________________________________________

Testers/Engineers: ___________________________________________________________________

2. Physical Inspection

Laptop battery attached Battery fully charged Laptop powers on Any disfigurement, scratches or damage to screen

Visible scratches, dents, or damage the casing

Keyboard functions Any frays or damage to charger

3. Operating System

Windows 10 Pro Installed Windows license activated Configuration files on desktop Configuration loaded to desktop Black connectivity verified Red connectivity verified

4. Multicast Source Setup

HDMI source connected to ACE HDMI port

Video available on source Video placed in loop

5. Ace Encoder Configuration

Laptop connected to Red UVDS

First instance of VLC player started Second instance of VLC player

Video viewer successfully complete

6. Kraken Configuration

7. UV Server Configuration

Total Ops check time (hours): ___________________________________________________________

Testers/Engineers: ____________________________________________________________________

AISRT-FORM-035 v1.0 //UNCLASSIFIED//

T2SDT-to-Stingray

Conversion Checklist

T2SDT-TO- STINGRAY CONVERSION CHECKLIST

SITE:

NODE:

Conversion Date:

Description: This report outlines the steps taken and purpose of converting all existing T2SDT kits into a baseline Stingray kit.

Currently, the T2SDT is configured with all devices loose loaded into transit cases. The Stingray conversion will change this loadout to rack-mount all devices and modify the transit case configuration to reduce the amount of network cases from three to two. The only remaining case from the T2SDT configuration will be the Media case (converted to Stingray Baseband Support).

Another task to be accomplished during the conversion is the swap out of the End-of-Life Kraken Mini transcoder to the more modern Kraken CR.

Finally, the T2SDT M&C laptop baseline configuration will be modified from the current SOFTACS image to that of the Stingray. This will aid in consistent software loads and IA related changes (patches, software updates, etc.). This conversion is complete in six stages.

*** The Kraken Mini will be returned to the vendor. All other spare material from the install will be returned to the owner, unless disposition is requested.

1. Preparation

IAW AISRT-PROC-015, section 1, check yes or no for each inspection question. Describe any problems found in comments. Include non-conforming serial numbers in the comments.

Yes (x)

No (x) Comments

T2SDT Inventoried Serial numbers recorded Any damage, missing items?

2. Rack Conversion

IAW AISRT-PROC-015, section 2, check yes or no for each inspection question. Describe any problems found in comments.

Yes (x)

No (x) Comments

Black stack staged for installation Mounts loosen with no issues Screws removed from upper mount UPS properly installed in mount tray M3-SE3 properly installed on top of UPS Power cable routed Black gear secured with thumbscrews and installed

Front and rear panels removed from lower gear mount

T2SDT KG mount removed UPS properly installed in mount tray M3 Server properly installed on top of UPS Second piece of mount placed on M3 Server…