Compatible with: Telestra 7.6.0 and later
A Telestra server typically includes two to six network interfaces, depending on the motherboard type and number of ports in the off-board NIC. You can configure a Telestra server in many ways, depending on your system requirements. As with most solutions, no one-size-fits all configuration exists.
This application note discusses common Applications, Protocols and Services (APS) and correlates them to one or more physical interfaces on the system. It also identifies common pitfalls and explains how to minimize system configuration and maintenance using certain design choices.
The following table lists common, supported APSs and maps them to one or more corresponding interface(s).
M = Mandatory: requires the exact APS specified below.
R = Recommended Interface: ASTi recommends a specific APS for reasons described in the interface’s corresponding details section.
X = Operational Interface: the APS can operate on the specified interface(s).
D = Dependent Interface: the APS depends on the configuration of another APS or specific piece of hardware.
| APS | ETH0 | ETH1 | ETH2 | ETH3 | ETH4 | ETH5 |
|---|---|---|---|---|---|---|
| Studio | R | - | X | X | X | X |
| Radio Monitor: Target View | R | - | X | X | X | X |
| Radio Monitor: Online Mode | D | - | D | D | D | D |
| ACENet | - | M | - | - | - | - |
| Telestra web interface | 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 |
| PXE Diskless Booting | D | - | D | D | D | D |
| HLA RTI | X | - | X | X | X | X |
| TDL 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 | D | - | D | D | D | D |
| ASTiNet | R | - | X | X | X | X |
This section briefly describes each APS and serves as a guideline for network topology. If you are unclear on your network topology’s requirements and application, contact support@asti-usa.com.
A single interface may support multiple APSs (e.g., DIS and ASTi HLA Host Control coexist on eth2). Additionally, a single APS may span multiple interfaces (e.g., DIS Exercise 1 is on eth0, while Exercise 2 is on eth2).
Studio is a communications development environment and advanced debugging tool. By default, Studio connects to the Telestra server via the eth0 interface. Earlier Telestra software versions (e.g., 4.X) only display certain Radio Monitor traffic over eth0. However, later software versions allow you to set Studio/Radio Monitor interface as any Telestra server interface. Hence while eth0 is the simplest solution, ASTi can support other interfaces. Multiple interfaces are not required.
Target View in the Radio Monitor lets you view the radios on the network from a certain Telestra Server's perspective.
By default, Target View works on eth0 without any modifications. Other interfaces are compatible but require you to enable and correctly route IPv6. Telestra 4.X and earlier required manual setup outside the scope of this document. Telestra 6.X and later allows you to configure Studio’s Radio Monitor interface in the Telestra web interface. Multiple interfaces are not required.
In Online Mode, the Radio Monitor searches the network for DIS and/or ASTiNet PDUs, which it requires to function. The Studio and Telestra server (i.e., used for DIS) must connect to the same interface. For example, if DIS is enabled on eth0, Studio must also connect to eth0; if DIS is enabled on eth2 while Studio is connected to eth0, Online Mode will not work. ASTi does not support multiple interfaces. To view multiple DIS interfaces, go to Radio Monitor: Target View.
All ACENet traffic must route to the eth1 interface. ACENet processes audio strictly in real time. To avoid audio interference, breakups, and delays, do not route other network traffic to eth1. If your program requires other traffic on eth1, contact support@asti-usa.com. Multiple interfaces are not required.
The Telestra web interface uses a standard web browser to connect to the Telestra server. While ASTi does not recommend a specific web browser or interface, the table above shows operational interfaces. You may configure multiple interfaces if required.
SSH allows you to securely log into a Telestra server and execute LinuxTM commands. ASTi does not recommend a specific interface for SSH. The table above shows operational interfaces. You may configure multiple interfaces if required.
DIS networks radio and intercom communications for multiple Telestra servers or DIS devices. While ASTi does not recommend a specific interface, the above table shows operational interfaces. You may configure multiple interfaces if required.
Manipulate components in a Studio project (e.g., change radio frequencies, adjust a Playsound component’s volume) with UDP host control. The Touch Screen Display (TSD) also fits into this protocol category since it’s a host interface for the Telestra server.
While ASTi does not recommend a specific interface, the table above shows operational interfaces. You may use multiple interfaces if required.
TCP host control works with several of the Telestra server's more advanced features:
Other features may exist, depending on the software version. The required type of TCP connection depends on the feature. The table below shows a list of the currently available features and their uses within Telestra 7.X:
| Feature | TCP Client Role* | TCP Server Role* |
|---|---|---|
| HLA Control | Host computer | Telestra server |
| Speech recognition | Telestra server | Host computer |
*TCP uses a three-way handshake process to connect the server and client. During this process, the client and server exchange synchronization and acknowledgment packets before the data communication begins. Certain features require the Telestra server to act as the TCP client, while others require the Telestra server to act as the TCP server. For more information about HLA, go to the HLA Installation Guide. For more information about speech recognition or TTS, go to the Studio User Guide.
While ASTi does not recommend a specific interface for TCP host control, the table above shows operational interfaces. Multiple interfaces are not required.
ASTi does not recommend a specific interface for PXE, although most customers use eth0. PXE configuration and implementation depends on several factors:
For more information, go to the Telestra Cold Start Guide and Telestra Diskless Installation Guide.
The table above shows operational interfaces with dependencies, given the above statements. Multiple interfaces are not required.
The HLA RTI networks radio and intercom communications for multiple Telestra servers or HLA devices.
While ASTi does not recommend a specific interface, the table above shows operational interfaces. You may use multiple interfaces if required. A third-party RTI Initialization Data (RID) file defines the HLA interface, and not all RTI versions and vendors are alike. Cross-reference this statement with the RTI vendor’s documentation.
The TDL interface sends data transmissions across a networked radio. By design, TDL uses two interfaces to communicate:
ASTi does not recommend a specific interface for TDL. For best results, ensure data from the host matches the UDP host control interface.
Radios use the pathloss interface to “request” attenuation values from another server dedicated to terrain, weather, and/or instructor-added propagation effects.
ASTi does not recommend a specific interface for sending pathloss requests and responses. However, you must dedicate only one interface to pathloss communications.
Radios use the HF interface to send HF propagation requests. These requests are more complicated than pathloss/terrain since they deal with ionospheric propagation, which relies on the time of day, season, and other variables. The concept, however, is largely the same as pathloss. Radios send a request to a server dedicated to HF communications, which respond with a loss amount.
ASTi does not recommend a specific interface for sending HF requests.
In Studio, the cell interface uses a fixed UDP packet with an extra cell-routing header to manipulate components and/or route data among servers. In general, only legacy programs support the cell interface. For requirements, contact support@asti-usa.com.
While ASTi does not recommend a specific interface, the table above shows operational interfaces. You may use multiple interfaces if required.
iSCSI is a transport-layer protocol that defines how you should transport Small Computer System Interface (SCSI) packets over a TCP/IP network. In many ways, iSCSI is similar to a remote hard drive. Instead of locally installing a fixed or removable hard drive in a Telestra server, remotely access a Logical Unit Number (LUN) via TCP/IP. iSCSI is available for cold-start purposes.
Similar to PXE, iSCSI depends on several factors:
The table above displays operational interfaces with dependencies, given the above statements. ASTi recommends using the offboard NIC because it usually supports a TCP Offload Engine (TOE) as well as the latest BOOT ROM options.
Multiple interfaces are not required. For more information, go to the Telestra Cold Start Guide and Telestra Diskless Installation Guide.
The Advanced Simulation Technology inc. Network (ASTiNet) protocol links Telestra server and ASTiNet radio and intercom communications. The ASTiNet may also transport additional control data.
ASTi recommends eth0, the default interface that requires no additional routing modifications. Other interfaces are supported but may require additional IPv6 routing setup. The simplest approach is to use eth0 unless otherwise required.
The table above shows other operational interfaces. ASTi does not require multiple interfaces. For more information, contact support@asti-usa.com.