51st ESB Is Setting the Stage for the Future

By CPT Dustin Marchak

Article published on: September 22, 2024 in the Fall/Winter 2024 edition of Army Communicator

Read Time: < 10 mins

A 51st ESB-E L3 Harris Hawkeye system provides satellite connectivity in the Middle East. (Photo by Capt. John Stoll, 51st ESB-E)

Signal support in CENTCOM

51st Expeditionary Signal Battalion-Enhanced

The 51st Expeditionary Signal Battalion (ESB) completed its conversion to an expeditionary signal battalion-enhanced (ESB-E) in July 2023. The conversion focused on enhancing the expeditionary capabilities of the signal battalion by replacing legacy Warfighter Information Network-Tactical (WIN-T) systems with the modernized Scalable Network Node (SNN) featuring major improvements in the size, weight, and power (SWaP) of the equipment.

Less than a year later, the 51st ESB-E deployed to the U.S. Central Command area of operations to replace 101st ESB as the rotational signal unit supporting Operation Spartan Shield (OSS). Not only was 51st ESB-E still fresh out of its conversion, but the battalion would also face the additional challenge of being the first ESB-E to support this mission, putting them in a position to set the stage for how an ESB-E not only matches an ESB’s capabilities, but exceeds them.

Hailing from Joint Base Lewis McChord (JBLM), Washington, 51st ESB-E spent their time training to support missions in the Pacific under 22nd Corps Signal Brigade (CSB) in support of I Corps. Finding out they would deploy to the Middle East immediately posed many challenges for the newly converted unit. Soldiers were fresh out of their new equipment training (NET) and conversion to the network communication systems specialist (25H) military occupational specialty. The battalion focused on training and validating teams and equipment to ensure its Soldiers had developed proficiency with their new equipment and skillsets. From the technical perspective, battalion network operations was hard at work designing a network that would best meet support requirements while connecting new, unfamiliar equipment to a Regional Hub Node (RHN) that had never supported an ESB-E.

Leading up to the deployment, 22nd CSB conducted a culminating training exercise (CTE) to validate the battalion’s readiness, but it didn’t take long for the 51st to encounter their first of many challenges. To reduce challenges with future theater integration, the battalion utilized the Global Agile Integrated Transport (GAIT) and RF to receive services from RHN Arifjan rather than RHN Roberts, which typically supported the battalion while at JBLM. RHN Arifjan had never supported an ESB-E, so they received detailed technical instructions regarding network configurations that would need to be completed on their equipment to facilitate the connection to SNNs. However, these instructions were out of date, and it took several weeks of coordination between the battalion, RHN, and Project Manager-Tactical Network (PM-TN) personnel to design and implement a working solution. Particularly important was supporting the new unified unclassified enclave (U2E) architecture used by the SNN, allowing it to connect to Non-Classified Internet Protocol Router (NIPR) network without using a physical inline encryption device. Even when that was out of the way, it became apparent that connecting the newly fielded ESB-E equipment to the legacy equipment still in use by the RHN would pose other challenges. The Secret Internet Protocol Router (SIPR) network connection still relied on a physical inline encryption device. Determining how to connect the newer VIASAT KG-250 to the legacy General Dynamics KG-175 ended up being a difficult process that stumped the ESB-E, RHN, and PM-TN personnel at several points.

We modified routes using new “anycast” destination addresses and the order of offered transform sets - something that had never been explicitly taught during the NET - were also modified. Issues between these KG devices continued to plague the battalion during the first month of their deployment.

Once deployed, more issues began to arise. Even though the new equipment enhanced the unit’s ability to rapidly deploy teams, they were still beset by issues related to technical configurations, equipment manufacturing, and unit specific requirements. After resolving the connection between the KG 250 and KG 175, the next task was to determine why users’ phone calls kept failing. This proved more difficult than expected because the ESB-E uses the new Redcom Sigma call manager to provision phone lines while the RHN is still using the Cisco Unified Call Manager (CUCM), so they were unsure how to assist. To complicate matters further, the SNN is not an official program of record and is not supported by U.S. Army Communications-Electronics Command (CECOM) field service representatives (FSR) in theater. Support for the SNN comes from PM-TN tactical network engineers (TNE), but there are none available in theater to support the rotational ESB-E. The impact of this was significant, as it could take days to receive responses to requests for assistance. Even then, in-person support was unavailable, further complicating the situation. To mitigate this problem, PM-TN representatives traveled to Kuwait for the first 30 days of the deployment to assist, which was incredibly helpful but still left the unit to fend for themselves for the remaining eight months. Fortunately, 51st ESB-E had recently been selected for a pilot program to test new commercial capabilities that helped bring systems online quickly while working through these challenges.

The pilot program equipped 51st ESB-E with two proliferated low Earth orbit (pLEO) systems, six SpaceX Starshields, and six Kymeta OneWeb terminals. The battalion was also equipped with six Viasat High Capacity KA modification kits for our L3 Harris Hawkeye satellite systems. While the Viasat system did not perform as expected and was ultimately removed from use, the two pLEO systems proved extremely valuable. In the early days of the deployment when signal support was hampered by efforts to transport equipment between countries, we were able to load SNNs equipped with Starshields on a flight and send them directly to where they were needed within a matter of days. Similarly, the Kymeta systems brought systems online quickly that were waiting for revised configurations from battalion network operations (NETOPs) to support fiber connections. Attempting to move these SNNs with their Hawkeye systems would have been much more difficult as it requires several cases of equipment and would have resulted in reducing the number of SNNs we could deploy as well as a longer setup time for services on site. Both pLEO systems are extremely easy to use and continue to enable signal teams to establish high speed connections within minutes of deployment.

On top of technical configurations between newer, more virtualized SNN systems and the legacy equipment at the RHN, 51st also had to contend with the loss of their larger support system, the Phoenix-E. The SNN is designed to support up to 36 users and is fielded with the L3 Harris Hawkeye satellite system. While the Hawkeye is sufficient for that user count, when larger headquarters require support, the SNN can be configured with a Pheonix-E Quad Band satellite dish that provides a larger dish for a more stable connection, greater power output, and improved data rates. Unfortunately, it did not take long before several of the Pheonix-E systems were damaged by wind speeds far below the rated capabilities listed in the technical manual due to the poor construction of the supporting legs. This fault was so severe that the battalion had to discontinue their use only months into the deployment, leaving the companies to send additional SNNs to locations to fill the capability gap.

This mission also required that the ESB-E support sites with unique signal support requirements. The most notable of which is the requirement to use the Secure Mobile Anti-Jam Reliable Tactical – Terminal (SMART-T) when supporting the Air Defense Artillery (ADA) Ballistic Missile Defense System Theater Interface Node (BTIN). The ADA relies on the SMART-T for its reliable, jam resistant capabilities. However, the SMART-T is a legacy system that is notoriously difficult to bring into operation, and there are few Soldiers that are trained in its use. While 51st ESB-E did succeed in establishing those systems, it took significantly longer than setting up an SNN. From a technical standpoint, the ESB-E could have provided a much more expedient and robust support package if Missile Defense Command would be willing to consider policy change for the use of the SNN to support the BTIN. Battalion NETOPs, in conjunction with ADA personnel validated that the SNN is fully capable of supporting the connection, but the decision ultimately comes down to a matter of policy and risk acceptance.

The importance of a fully staffed and knowledgeable battalion NETOPs became apparent throughout the deployment. Several supported locations require connections for mission command systems, as well as U.S. Army Central (ARCENT) black core fiber connections that needed to be transferred over from the 101st ESB to 51st ESB-E. Due to the new configurations and greater amounts of virtualization in the SNN, this was no small task. Every connection had to be manually broken down and rewritten by a team of only four battalion NETOPs personnel, while also juggling a flood of calls from teams asking for help. To further build relations with the RHN and help solve problems from both ends of the connection, 51st attached a network technician (255N) to the RHN who worked directly on the operations floor and helped coordinate all trouble-shooting efforts specific to the battalion. This effort was instrumental in not only deepening our understanding of how to connect to the RHN but also in building greater trust between the ESB-E and RHN personnel, fostering a relationship that will continue to pay dividends for ESB-Es deploying in the future.

Despite these challenges and setbacks, 51st ESB-E has embodied their motto, “Always Constant,” and never wavered in their determination to succeed. They have overcome every challenge. Looking at their operations now, one would never know that it had ever been so difficult. The team at 51st ESB-E, RHN Arifjan, 22nd CSB, 160th Theater Signal Brigade, and ARCENT have completely redefined the functionality of signal support throughout theater and built a foundation that will ensure the success of future rotational ESB-Es supporting this vital operation.