Telestra App Note

Designing the Network Configuration for your Target (#81)

Background

The Telestra Target platform may have between three (3) and six (6) network interfaces depending on the motherboard type and number of ports contained in the off-board NIC. Given a number of available interfaces there are various ways to setup the Telestra Target depending on the requirements of the system. This application note attempts to clarify the network configuration for your Telestra Target by covering the most common Applications, Protocols and Services (APS) and tie them to one or more physical interfaces available on the system. As with any solution there is no one size fits all configuration. There are, however, things you should avoid and be aware of. Additionally, the system configuration and maintenance can be minimized if certain choices are made during the design phase.

Telestra Target Application, Protocol and Service Connections

The table below lists the most common APSs supported on the Telestra Target platform and maps them to a corresponding interface(s).

Decode Keys

M = Mandatory
R = Recommended Interface
X = Operational Interface
D = Dependent Interface

Application, Protocol or Service ETH0 ETH1 ETH2 ETH3 ETH4 ETH5
ACE Studio R - X X X X
Radio Monitor Target View Mode R - X X X X
Radio Monitor Online Mode D - D D D D
ACENet - M - - - -
RMS X - X X X X
SSH X - X X X X
DIS X - X X X X
UDP Host Control X - X X X X
TCP Host Control X - X X X X
Diskless Boot (PXE) R - X X X X
HLA RTI X - X X X X
TDL Link Control X - X X X X
Pathloss/Terrain X - X X X X
HF X - X X X X
Cell X - X X X X
iSCSI - - X - X X
ASTiNet R - X X X X

If flagged as "Mandatory," the interface should be used for the specified Application, Protocol, or Service (APS). If flagged as "Recommended," it is ASTi's general recommendation to run that APS on the specified interface for the specific reasons mentioned in the details section below. If flagged as "Operational," the APS can run on the specified interface(s). If flagged as "Dependent," the APS is dependent on the configuration of another APS.

Example Telestra Target Network Configuration
Ethernet Diagram

Application, Protocol and Service Connection Details

This section has a brief description of each APS. Note that this application note is designed to serve as a guideline for network topology. If you are unclear on the requirements and application of your network topology, please contact ASTi support. Also note that a single interface may support multiple APSs if it is a desired topology. For example, DIS and host control can co-exist on interface eth2.

ACE Studio

ACE Studio is a communications development environment and advanced debug tool. ACE Studio generally connects via the eth0 interface. ASTi recommends eth0 because Radio Monitor is also a part of ACE Studio. See "Radio Monitor - Target View" below for rationale. If Radio Monitor is not a concern, ACE Studio can run on any of the operational interfaces shown above.

Interface eth0 is the recommended interface and the operational interfaces are shown above. Multiple interfaces are not required.

Radio Monitor - Target View Mode

The Target view mode in Radio Monitor allows a user to select a specific Target and view the radios on the network from the perspective of that Target. For this view mode to function, IPv6 must be enabled and routed correctly. By default, Target view will work on interface eth0 without any routing modifications. Other interfaces can be used, but additional IPv6 routing setup is required. The simple approach is to use eth0 unless there is a driving requirement to do otherwise.

Interface eth0 is the recommended interface and the operational interfaces are shown above. Multiple interfaces are not required.

Radio Monitor - Online Mode

The online mode will cause Radio Monitor to 'sniff' the network for DIS and/or ASTiNet PDUs. This application is flagged as "D" for dependent because you must have DIS or ASTiNet PDUs on that Network for online mode to function. For example, if you have DIS enabled on eth2, but Studio is connected on eth0, online mode will not work. However, if DIS was enabled on eth0 and Studio was connected on eth0, online mode would function correctly.

If online mode support is required, you must match the DIS interface configured on the Target platform. Multiple interfaces are not supported. To view multiple DIS interfaces, use the Target View Mode shown above.

ACENet

ACENet devices must be connected to the Target via eth1. ACENet requires strict realtime timing for the audio processing so no other traffic should be routed on the eth1 interface. Mixing ACENet traffic with other network traffic may cause audio interference, breakup, and delays. If this is an issue for your application, please contact ASTi.

Interface eth1 is the mandatory interface for ACENet. Multiple interfaces are not required.

Remote Management System (RMS)

RMS allows a user to connect to the Target via a standard web browser.

There is no recommended interface. Operational interfaces are shown above. Multiple interfaces can be used if required.

Secure Shell (SSH)

SSH allows a user to securely login to the Target platform and execute LinuxTM commands.

There is no recommended interface. Operational interfaces are shown above. Multiple interfaces can be used if that is required.

DIS

Distributed Interactive Simulation (DIS) allows a user to network the radio and intercom communications for multiple Target platforms or DIS devices.

There is no recommended interface. Operational interfaces are shown above. Multiple interfaces can be configured if required.

UDP Host Control

User Data Protocol (UDP) host control is used within the ACE project/model simulation to manipulate components. For example, you can use the host interface to change the frequency of a radio or the volume of a playsound component. The Touch Screen Display (TSD) is also a host interface for the Target, so the TSD fits into this category of protocol.

There is no recommended interface and the operational interfaces are shown above. Multiple interfaces can be configured if that is a requirement.

TCP Host Control

Transport Control Protocol (TCP) host control is used with several of the more advanced features available on the Target platform. These include text-to-speech (TTS), speech recognition, and HLA control of a federation.

There is no recommended interface. Operational interfaces are shown above. Multiple interfaces are not required.

Diskless Boot (PXE)

There is not a mandatory interface for PXE. The recommended interface is eth0. The eth3 interface is also operational because it is on-board. The interfaces eth2, eth4, and eth5 are optional as well but require running an Intel utility to enable the boot ROM. Contact ASTi for support.

Interface eth0 is the recommended interface. Operational interfaces are shown above. Multiple interfaces are not required.

HLA RTI

The High Level Architecture (HLA) Runtime Infrastructure (RTI) allows a user to network the radio and intercom communications for multiple Target platforms or HLA devices.

There is no recommended interface. Operational interfaces are shown above. Multiple interfaces are not required. However, please note that the HLA interface is defined through a non-ASTi RTI Initialization Data (RID) file and not all RTI versions and vendors are alike. This statement should be cross-referenced with the RTI vendor's documentation.

Tactical Data Link

The TDL interface allows users to send data across a networked radio in addition to voice transmissions. By design, TDL uses two interfaces for complete communication. First, data is generated by a host computer and sent to the Telestra. The data is then relayed across a radio using the DIS interface.

No specific interface is recommended for TDL, but it is suggested that data from the host matches the UDP Host Control interface.

Pathhloss/Terrain

The Pathloss interface allows radios to send "requests" for an amount of loss to another server. This server can be for terrain, weather, or other instructor-added propagation affects.

There is no recommended interface for sending pathloss requests and responses. One interface must be used for sending requests and receiving responses.

HF

The HF interface is used for radios to send requests for HF propagation. These requests are more complicated than pathloss/terrain since they deal with ionospheric propagation, which relies on time-of-day, season, and other variables. The concept, however, is largely the same as pathloss. Radios send a request to an "HF server" and the server responds with an amount of loss.

There is no recommended interface for sending HF requests.

Cell

The Cell interface can be used within the ACE project/model simulation to manipulate components and/or route data from one platform to another in a fixed UDP packet with an additional cell routing header. In general, the cell interface is only supported on legacy programs. If you have a cell interface requirement, contact ASTi support.

There is no recommended interface. Operational interfaces are shown above. Multiple interfaces can be configured if that is a requirement.

iSCSI

The optional interfaces that support iSCSI booting are eth2, eth4, and eth5. This requires running an Intel utility to enable the boot ROM. Contact ASTi for support.

ASTiNet

The Advanced Simulation Technology Inc. Network (ASTiNet) protocol allows a user to network the radio and intercom communications for multiple Target platforms or ASTiNet devices. Additional control data can also be transported over ASTiNet.

For ASTiNet to function, IPv6 must be enabled and routed correctly. By default, this will work on interface eth0 without any routing modifications. Other interfaces can be used. However additional IPv6 routing setup is required. The simple approach is to use eth0 unless there is a driving requirement to do otherwise.

Interface eth0 is the recommended interface. Operational interfaces are shown above. Multiple interfaces are not required but can be supported if necessary. Contact ASTi if this is a requirement.


Note: This Application Note was revised during ACE software version 4.28. Contact ASTi if you have specific network configuration questions.

Linux is a trademark of Linus Torvalds.