25ID KLAS Mobile Data and Services Package White Paper · 25ID KLAS Mobile Data and Services...

UNCLASSIFIED

25ID KLAS Mobile Data and Services Package White Paper

Background: The 25th Infantry Division (25ID) regularly conducts exercises in the Pacific at the tactical and operational levels. 25ID executed a capability proof-of-concept at the U.S. Army Garrison Yongsan, Korea from 20-26 January 2018. As part of this demonstration, 25ID deployed a KLAS Voyager 8 Baseband Data Package and a KLAS Tactical Data Center (TDC) establishing a Division Early Entry Command Post. This document attempts to highlight successes and recommended improvements to mobile data and services packages to capitalize on efforts to close the gap of a rapid and cost efficient deployment of a tactical network to enable fight-tonight mission command at the tactical and operational levels. Problem Statement: 25ID requires the ability to rapidly disseminate mission orders and conduct collaborative mission planning during combined joint operations with Coalition Partners while utilizing a mobile secure, fight-tonight network that enables mission command. 25ID’s current fight-tonight network is provided by Program Executive Office Command Control Communications-Tactical Project Manager (PM) Tactical Network equipment fielding’s. While PM Tactical Network provides a readily deployable baseband and services package in the form of large High Mobility Multipurpose Wheeled Vehicles and Light Medium Tactical Vehicle mounted shelters, they do not meet the rapid and lightweight requirements of a 25th Infantry Division Early Entry Package. PM Tactical Network does provide smaller form factor baseband solutions in the form of a SIPR-NIPR Access Point. However, this solution requires many sub components in the form of transit cases that make it inefficient to transport via civilian/commercial aircraft. None of the PM Tactical Network solutions provide a smaller form factor for the Army Mission Command Services (AMCS) Services component of our Warfighting function or for a Mobile Wireless Tactical Operations Center (TOC). Without smaller form factor solutions, units will continue to have a gap in a truly rapid deployable tactical network to provide fight-tonight mission command. Deployments with traditional PM provided equipment take days to deploy, not hours, and at great financial cost. Proof of Concept Demonstration: During travel to the Republic of Korea, 25ID demonstrated the ability to rapidly deploy a data package for Colorless, NIPRNet, SIPRNet, and CENTRIX-K along with core AMCS CENTRIX-K services. During this demonstration, 25ID tested and validated the following tactical services and capabilities: 1. Services: The KLAS TDC replicated the Battle Command Core Services (BCCS) Enterprise and Warfighter Application (WFA) server environment providing the following services:

Domain Controllers (x2) Exchange Servers (x2) ACAS Adobe Connect SQL Server (6) C2R Command Post of Future (CPOF) BUM CPOF Master


2 UNCLASSIFIED

CPOF Data Bridge CPOF Mid-Tier (x4) CPOF VOIP/RA File Share Microsoft Lync Joint Automated Deep Operations Coordination System (JADOCS) Wide Area Voice Environment (WAVE) WSUS XMPP VMWare vCenter

2. Services Configuration: We evaluated the KLAS TDC by conducting two different system deployments. During the first deployment of the system we replicated the BCCS Enterprise Services and WFA by taking a snapshot of the complete virtual machine to include the additional drives that comes with each machine. The Core baseline was VMware ESX-1 6.0 (Update 3d), vCenter Appliance, with a Virtual Storage Area Network (VSAN). The first host was used to simulate the PM issued Dell Dart Frog Server and the other three were used as the VSAN Storage to create the data store simulating the Dell EqualLogic. In the BCCS configuration each drive is mapped to a Logical Unit Number (LUN) in the EqualLogic via (Internet Small Computer Systems Interface) which we took and aggregated all those drives into one single Virtual Machine as a Virtual Mapped Raw LUN’s. Taking all the drives snapshots was done with the KLAS Systems provided Rubrik software, which is a backup software solution provided by KLAS. In a second deployment we built the BCCS Enterprise Services and WFA manually without taking any snapshots from any previous build. 3. TDC Tech Specifications:

Key Features: ■ Four blades each with Intel® Xeon® D 8-core processor, 10 Gbps networking and 128 GB RAM. ■ 512 GB RAM and 32 physical cores per Voyager TDC system ■ 12-port 10 Gbps uncontended switch ■ Airline carry-on form factor measuring just 22” x 14” x 9” with built-in UPS ■ Removable configuration and storage with Voyager Ignition Key (VIK) ■ Multiple supported and tested Software-Defined Storage architectures: ■ VMware vSAN ■ NetApp ONTAP Select System Components ■ Voyager 8 transit case with integrated chassis/UPS ■ Voyager TDC Sled ■ 4 x Voyager TDC Blade ■ Voyager TDC Switch Voyager TDC Physical Specifications ■ 22” W x 14” D x 9” H (559 mm x 356 mm x 229 mm) ■ 56.6 lb. / 25.7 kg (without batteries) ■ 63 lb. / 28.5 kg (with standard BB-2590 batteries. Lower capacity BB-2590 batteries available for IATA compliance) Voyager 8 Electrical Specifications


3 UNCLASSIFIED

■ 10-36 VDC input up to 400 W with MIL-STD 1275D filter ■ 90-264 VAC input up to 400 W, 50-400Hz ■ Conditioned power provided to Voyager TDC Blades, Sled and Switch ■ 2 x AC outputs available at rear when AC input is present ■ 2 x 12 VDC outputs at rear ■ Uninterrupted failover between AC, DC and battery ■ Space for 2 x BB-2590 batteries (available separately in high capacity for extended operation or lower capacity to comply with IATA regulations) ■ Provides 414 Watts energy of backup Construction ■ Aerospace-grade, carbon fiber monocoque built from single mold structure for maximum strength ■ O-ring seal around front and rear lids ■ Grab handles on top and bottom of case ■ Retractable extension handle ■ Lightweight aluminum chassis with integrated PSU Rack mountable Chassis ■ Voyager 8 chassis may be removed from case for rackmount installations in vehicles ■ 5U 19-inch rack ■ 15.9 lb. / 7.2 kg (without batteries) Voyager TDC Blade Specifications (4x per System) ■ Xeon D-1541 Processor ■ 8 cores, 16 threads ■ 2.1 GHz clock with turbo to 2.7 GHz ■ 12 MB cache ■ 128 GB 2.4 GHz DDR4 Storage ■ Storage caddy supports 1 or 2 SSDs in 2.5” format ■ SSD capacities validated: 1.92TB, 3.84TB ■ VIK removable storage for hypervisor (4 GB to 32 GB) Networking ■ 2 x 10 Gbps Ethernet interfaces ■ 2 x 1 Gbps Ethernet interfaces ■ 1 x 1 Gbps Ethernet management interface Various ■ 2 x USB 3.0 interfaces ■ RJ-45 console port ■ VGA graphics support ■ Web-based IPMI for remote management Mechanical ■ 7.4” W x 7.6” D x 2.4” H (188 mm x 194 mm x 61 mm) ■ 4.41 lb / 2 kg each Voyager TDC Switch Specifications ■ 12 x 10 Gb switch ports, 4 of which are available as copper or fiber using SFP+ ■ 1 Gb management port ■ Cisco-like UI based on KLAS OS ■ 121 Gbps switching backplane


4 UNCLASSIFIED

■ Layer 2 features include VLAN trunking, Port Security, 802.1x ■ Link aggregation and stacking options available Compliance ■ Designed to meet MIL-STD-810G ■ -31 °C to 49 °C ■ FCC Part 15B ■ CE compliant ■ IP65-rated case ■ Meets airline carry-on size requirements

4. Transportability: The KLAS Voyager 8 is custom designed by size and weight to operate as a commercially viable carry-on luggage solution. As such it has been transported through several International and Domestic Airports as both carry-on and checked in luggage without incident. It fits comfortably into all overhead compartments and has a convenient collapsible carrying handle with wheels for ease of transport.

The KLAS Systems Voyager 8 in Carry-On Configuration (pictured left) and with Extended Collapsible Handle (pictured right)


5 UNCLASSIFIED

The KLAS Voyager 8 chassis is powered by a single standard power cord that you would find on any desktop PC. Whether at home, hotel, or anywhere else a standard 110-220v power outlet is all that is needed. The chassis itself also comes with 2x power outlets to provide for additional power strips and equipment. This is a stark contrast to some of the specific power requirements of larger chassis.

The KLAS Systems Voyager 8 Backside (pictured left) and Standard Power Input/Output (pictured right) Alternatively, the Voyager 8 modules are only using the backplane connections of the chassis for power. They can be individually removed from the chassis and independently powered up on their own. This provides great flexibility to take out a network switch and deploy it in the next tent to provide network access.

A KLAS Systems network module removed from Voyager chassis in a standalone configuration with direct power supply.


6 UNCLASSIFIED

As a third power option, each network module contains its own removable battery supply that is charged when connected to the Voyager 8 chassis. Our testing revealed that the router modules would last 3.5 hours while the network switches were still going. This beat out the capacity of our PM fielded larger UPS chassis.

A KLAS Systems network module with independent power supply connected (pictured left) and disconnected (pictured right).

Close-up view of the KLAS Systems independent network module battery interface. Lastly, the Voyager 8 chassis has a housing in the rear for 2x standard Military 5590 batteries that can be resourced by any Supply Office. They are hot swappable, meaning as long as 1x is plugged in you are free to swap out the other. After 8x hours of continuous operation on these batteries without ceasing the testing was concluded.


7 UNCLASSIFIED

The KLAS Systems Voyager 8 Backside with 5590 Bays Closed (pictured left) and with 5590 Bays Open (pictured right).

Standard 5590 batteries that provide over 8x hours of redundant power to the Voyager 8 chassis

The Voyager 8 can be utilized as either a standard 8x module chassis or in a modified configuration to support an enhanced server configuration known as the TDC. When in a typical Voyager 8 setup it can be populated with 8x full size modules ranging from Routers, Switches, VM chassis for Hypervisor installation, Radio mounts, to Type-1 Encryption mounts. Alternatively, the Voyager 8 can be populated with 16x half-size module components such as separate form factor CradlePoints, Routers, Switches, and VM chassis. Of course, with less real estate comes less capacity in the form of port density and various degrees of processing power, drive space, and memory.


8 UNCLASSIFIED

KLAS Systems full-size network module (pictured left) compared to a half-size network module (pictured right). A Voyager 8 chassis can house 8x full-size, 16x half-size, or combination of both to fully populate a chassis.

From our examinations, no other form factor provides comparable power redundancy, and few others can compare to the size, weight, ease of transport, and module flexibility that KLAS Systems has to offer. 5. System Configurability: The KLAS TDC, three different ways to set up the VM environment; 1) Replica of snapshots, 2) PM BCCS scripts, 3) Standard Manual Enterprise & WFA installation. 6. TOC Physical Setup: Upon arrival to Korea we setup the KLAS Voyager 8 Baseband Data Package (the Wide Area Network (WAN), routing, and switching Voyager 8 configuration) and the Voyager 8 TDC (the BCCS Enterprise Services Voyager 8 configuration) in a TOC setup within our Hotel room.

Standard Single Room at the Dragon Hill Lodge located in Yongsan Korea prior to mobile TOC setup. The Voyager 8 Baseband Data Package providing Commercial WAN, Colorless, NIPRNet, SIPRNet, and Coalition routing and switch services can be seen in

the vertical upright position located on the desk next to the lamp.


9 UNCLASSIFIED

We were able to easily resource the power requirements (2x standard outlets) to power both the Voyager 8 Baseband and TDC packages. The setup consisted of both a NIPRNet, SIPRNet, and Coalition “café” style service as well as a full Network Operation Security Center for the accompanying Signal support personnel. Using a combination of physical IP Phones for the “café”, traditional phones using the KLAS OS FXS ports, and Cisco Jabber Collaboration software as a “softphone” voice solution we were able to provide 3x redundant voice solutions. The Cisco Jabber software enabled the TOC to have a full service Voice Teleconferencing solution on SIPRNet and CENTRIX-K which was exercised each morning for a daily update brief to our rear echelon in Schofield Barracks, HI. Utilizing 4x WAN connectivity options (Hotel Wi-Fi, Hotel Wired Business Class, Commercial MiFi 4G mobile “puck”, and a standard Mobile Smart Phone 4G Hotspot we were able to test connectivity speeds and bandwidth availability to properly “tune” the network to optimal levels with failover capabilities. Bringing a military SATCOM solution would have of provided a 5th means of WAN connectivity back to our Home Station Mission Command network. 7. Transport Method: The different module options of Voyager chassis allow for great flexibility on providing a source of WAN connectivity. In our setup we utilized the provided half-size Cisco 5915 router with integrated backplane connections to the onboard CradlePoint module. This allowed us to configure 3x connection points for WAN transport. The CradlePoint itself allows simultaneous connection to a Wireless Access-Point, HotSpot capable mobile device, or direct USB connection to a modem capable mobile device via “tethering.” This means that within the CradlePoint alone we had 3x WAN connectivity options via Hotel Wireless Access-Point, Wireless Connection to a HotSpot enabled Cellular Phone, and direct USB connection to a Modem Capable MiFi device. The CradlePoint can be configured to prioritize one connection over another, or by quality of signal strength. All 3x were successfully tested during our trials. The CradlePoint is also capable to simultaneously push out and provide a wireless Local Area Network (LAN) and bridge access to its external wireless WAN connection. This assists in reducing the division of the wireless WAN spectrum to keep a clean connection out. Alternatively, we connected to the Hotel provided Business Class internet via a direct connection (in this case DSL). This was configured and prioritized within the Cisco router itself to prefer directly connected networks vice the CradlePoint. Lastly, we configured another port to support a DoD SATCOM transport such as a Satellite Transportable Terminal, Ground Antenna Transmit Receive (GATR Antenna), or Tampa Microwave terminal. All have been successfully tested with various Voyager chassis successfully. It is possible to use all the aforementioned methods of transport simultaneously, and depending upon the engineering will dynamically chose the configured best path. Although not specific to KLAS Systems, these off-the-shelf configurable solutions are not provided by any other vendor we have researched in such a small half-module form factor that can be independently powered away from any chassis. Of note, because this is Ethernet-based external connectivity, we can also utilize any Army issued High Capacity Line of Site solution to provide WAN connectivity as well.


10 UNCLASSIFIED

A KLAS Systems ERm half-size Cisco 5915 Router with 2x routed ports, 1x Power Over Ethernet (POE) switchport, 1x console port, and integrated CradlePoint. The CradlePoint can receive a Wireless signal as a WAN connection, redistribute as a local Wireless

LAN, as well as connect to modem capable mobile devices via the USB connection. In a single half-module form factor we have now provided our deployed teams a means to connect to a WAN whether in a commercial environment or an austere tactical environment that requires a military transport solution. Future Capabilities and Recommended Improvements: After demonstrating the capabilities of the Voyager chassis and associated modules, 25ID has identified several recommendations to build upon the success of employing KLAS Systems solutions. 1. Proprietary Operating Systems: The KLAS Systems engineering team has developed its own proprietary Operating System known as KLAS OS for some of its routing and switching module solutions. These custom KLAS OS systems allow for special configurations that allow certain functionality such as the integration of traditional telephone port integration to the switch modules and a key feature known as the Voyager Ignition Key.

The VIK acts as a TFTP storage device that a blank switch and router can boot from. Meaning any secure configurations are stored on these removable VIK’s and when the Voyager modules are powered off contain no sensitive configurations. Once the VIK is inserted and modules are powered on, they pull their configurations from the VIK.

These are nice features, but utilizing a proprietary OS can have its faults. The KLAS OS is structured to be similar to Cisco IOS, however we experienced several glitches and bugs. Such as an issue where we had to restart the switch every time we moved a device from one port to another because the mac-address would not dynamically reassign in the mac-address table. This is the only router and switch combined modules that KLAS Systems currently offers.


11 UNCLASSIFIED

A KLAS Systems 100Mb/s ESR full-size Cisco 5915 Router with 2x routed Ethernet ports, 1x USB tether port, 1x ISDN port, 1x virtual backplane interface to KLAS OS switch, 1x console port, and integrated KLAS OS switch. The KLAS OS switch has 12x

switchports (4x are POE), 1x console port, 2x standard RJ11 telephone FXS ports and the KLAS Systems VIK. We sat down to discuss this issue with the KLAS Engineers and we were able to configure the Voyager kits that excluded KLAS OS modules and go entirely with Cisco IOS routing and switching platforms. However, KLAS Systems does not offer a router and switch combination module that offers both Cisco IOS platforms, nor do they offer an exclusive Cisco IOS based platform that can utilize their VIK feature, or a Cisco solution that still offers the ability to plug in and use standard telephone lines for voice. These would be nice additions to their offerings if they could be done in a Cisco exclusive environment. 2. Configuration: We have noticed some limitations with the provided 100Mb/s Cisco 5915 Router modules as well. When applying a Secure Technical Implementation Guideline (STIG) configuration to the router, we were not able to create Access-Lists that could hold our Division wide requirements. Meaning we could not account for all of our Division, Brigade, and Battalion side management networks for all the different required networks services. The router was not able to save a configuration that large and compressing the configuration was not able to help. We were able to meet STIG compliance but had to trim down some of our security configurations to a few key subnets, rather than configure a Division wide solution that would allow any one of our subordinate units to take ownership of the data package. By no means a hindrance but an observation. The 1GB upgraded KLAS Systems Cisco modules may alleviate this issue. With interfaces between the Cisco Router and KLAS OS we noticed other random issues such as Bridge Virtual Interfaces randomly stop working. We had to alter our configuration to meet our needs but this issue was not consistent across our different modules and would seem to only begin after a certain amount of time. Adjusting our configuration approach solved the issue.

Other small nuances like this were observed but nothing that prevented our successful secure configuration or operation. We are hoping that newer modules will fix this issue whether it be nature of the Cisco IOS platform, KLAS OS, or the hardware changes required to fit the technology in this form factor.


12 UNCLASSIFIED

3. Pins on back of TDC module: For the KLAS TDC we encountered several flaws with the pins on the back of the TDC modules. The pins became week due to over use since this was a demonstration model. We assume that newer equipment would not have this issue.

Employment Considerations: The following are recommendations to those who seek to employ the KLAS Systems solutions at the tactical level in support of operations. 1. Battalion: 25ID has worked with KLAS System personnel to develop a 100Mb/s package that provides routing, switching, commercial and military transport, as well as limited VM environments for voice and secure access services. This Voyager 8 chassis provides a commercial access Cisco IOS Router and CradlePoint (Colorless or Commercial), Colorless VM and Switch, and replicated NIPR, SIPR, and a Coalition Cisco IOS Router, Cisco IOS 24-Port Switch, and 1GB Memory VM environments.

This Battalion configuration is our one-stop shop for any solution at the Battalion and below levels that do not provide their own services. Whether it be a Battalion TOC or a Small Team this package can support both commercial and military WAN transport as well as voice, video, and data for 3x variations of networks. This can provide both Colorless core or NIPR core baseband transport services in garrison, during an exercise, or as an early entry Phase 0 option at the Battalion level.

2. Brigade: At the BDE level, where they have their own services we needed more than a 100mb/s LAN solution. We worked with KLAS to package a 1Gb/s option, but had to sacrifice some of our WAN flexibility regarding commercial transport. The BDE level package is comprised of a Voyager 8 chassis with 8x full size network modules providing 4x 2-port 1GB/s Cisco IOS Routers and 4x 24-port 1GB/s Cisco IOS Switches. These provide XLESS, NIPR, SIPR, and a Coalition enclave baseband services. For Domain services we recommend a Voyager TDC to deploy AMCS services, and a possible 2nd Voyager TDC if a Wireless LAN TOC capability is required.

We designed the 1GB/s package to support a BDE sized TOC element with their own services solutions whether it be the KLAS Voyager TDC or other. The internal requirements of a BDE LAN concerning data file sizes, video requirements, maps, and special Army programs required a higher bandwidth than the previous 100Mb/s packages could support.


13 UNCLASSIFIED

This package can provide the same baseband services as the Battalion package without the commercial WAN options of the CradlePoint. Whether in garrison, expeditionary mission with an accompanying military transport method, or as an early entry deployable package this will meet the needs of any BDE or DIV sized element. 3. Division: The DIV level package is identical to the BDE level package. Although capable of supporting a DIV LAN, we would not recommend using this package to provide a Division SATCOM service to subordinate units. We would recommend this package as an alternative to a Division level baseband package, but not as a replacement for the Division SATCOM hub. A Division level SATCOM hub would require baseband hardware and memory beyond the capability we have seen in a modular form factor thus far. Additionally the DIV level package would easily fill the needs of the DIV Early Entry Command Post. Conclusion: This proof-of-concept demonstrated the ease of transportation and setup that can be housed in such a small form-factor. There are many vendors that provide similar capabilities in small packages, but none have matched the available options of power and form factor that the KLAS System provides. We’ve looked at other small form factor options as well but none have quite the unique form factor that the KLAS System presents in terms of size of the individual components, options of the component chassis to house them in (Voyager ECK, Voyager 2, and Voyager 8 chassis), or forethought put into the ease of transport by having a purpose built commercial carry-on package by size, weight, and in-flight battery restrictions. Cost savings alone for smaller exercises and expeditionary missions is in the millions over traditional PM provided larger baseband and services solutions. Although we have tested these system out at the small team and Expeditionary level, we will do our first test of this system at the Division level in spring 2018 to ensure the system is indeed a viable early entry solution at the BDE and DIV levels.

Prepared by: CW3 Daniel Feldman, 25ID G6 Network Engineer.

Email: [email protected]; Office: 808-787-0301 CW2 Jose Hernandez, 25ID G6 Information Systems Tech.

Email: [email protected]; Office: 808-655-1676 CPT Jason Smith, 25ID Network Operations OIC. Email: [email protected]; Office: 808-655-1981 Approved by: LTC Brian Jorgenson, 25ID ACofS G6.

Email: [email protected]; Office: 808-787-4317

mailto:[email protected]




25ID KLAS Mobile Data and Services Package White Paper · 25ID KLAS Mobile Data and Services...

Documents

Transcript of 25ID KLAS Mobile Data and Services Package White Paper · 25ID KLAS Mobile Data and Services...