Single Network Connection Topologies

The Single Network Connection feature allows AVB Network Interface Card (NIC) to handle all control and media communications. This allows Control NIC to be optionally disconnected. Network connection behavior will reflect and dynamically accommodate the physical connection state of the control and AVB NICs.

On systems with a dual control and AVB connection, disconnecting the Control NIC will cause the system to accept control traffic over the AVB interface. The front panel of the device will be updated to display the IP address of the AVB interface, as control communications may only use this interface.

On systems with a single connection to the AVB port, connecting the Control interface to the network will cause the Control interface to accept control traffic. The front panel of the device will be updated to display the IP address of the Control interface. If the Control Interface has been configured for DHCP, connecting it to a network will begin DHCP negotiation for an IP address.

 

Supported Network Topologies

Converged Network - Dual Network Connections

The original networking topology previously (and currently) supported by Tesira, Converged Network - Dual Network Connections utilize both the control and AVB ports of each server-class device connected to the same network. The new Single Network Connection has no impact on device behavior in this topology.

An example of Converged Network - Dual Network Connection is shown below:

Separated AVB and Control Networks

Another "legacy" topology, the control ports of each server class device must be connected to the control network and the AVB ports to the AVB network.

An example of Separated and Control Networks is shown below:

Any AVB expander device type may be connected to the AVB network. Only control-type remote devices (TEC-1, HD-1, EX-LOGIC, TEC-X) may be connected to the control network or the AVB network. The new Single Network Connection has no impact on device behavior in this topology.

 

Converged Network – Single Network Connections

In this topology only the AVB ports of each server-class device must be connected to the network; the control ports of all server-class devices are left disconnected from the network.

Tesira SW will discover and configure the server-class devices using TCP/IP communications via their AVB ports. Similarly, server-class devices will discover and communicate with each other via their AVB ports.

 

Converged Network - Mixed Network Connections

Tesira devices can optionally use Single or Dual Network Connections on a Converged Network. An example is shown below:

 

Converged Network - "Corporate" Network Isolation

A basic method for isolation may be achieved by deploying a converged AVB and Control Network, creating an external IP route from the corporate network to the AVB and Control Network. An example is below:

 

Hybrid Converged Plus Separated Networks

Isolation from a media network may also be achieved by supporting a hybrid network topology of separate and converged networks. An external IP route between the control and Control & AVB networks is required. Tesira software will discover and communicate directly with all server-class devices.

Tesira server-class devices which have active control and AVB port connections must be prepared to discover other server-class devices on both networks via host table configuration or DNS/DHCP. 

See the illustration below for an example of a hybrid network: