TesiraFORTÉ X Network Port Modes

Network Port Modes FW 4.0 and 4.1

In initial releases (firmware 4.0.x, 4.1.x), TesiraFORTÉ X supported a separated network topology only.

• P1: Dedicated to Tesira control and VoIP.
  • VoIP shares the same MAC address and IP address, subnet, and gateway as the Tesira control port unless VoIP VLAN tagging is enabled and a VoIP VLAN ID is assigned.
  • If VoIP VLAN tagging is enabled, VoIP uses a unique MAC address, IP address, subnet, and gateway. This serves as the default gateway for the device and should also be applied to the control port interface in devices using FW 4.0 and 4.1.
• P2-5: Dedicated to media (AVB or Dante).
  • Media connections to 3rd party switches will be either AVB capable or Dante capable, but not both. The presence of AVB MSRP packets determines the port role.
• P2-5 support PoE+.

TesiraFORTÉ X does not support Tesira's "single-cable" network topologies in FW releases 4.0.x or 4.1.x. While single-cable operation via P2-5 might function, it can lead to inconsistencies, making the device undiscoverable or causing unpredictable media network behaviors. Updating to FW 4.2 or later and selecting the Converged Control, VoIP and Media network mode resolves this behavior.

TesiraFORTÉ X (FW 4.0 and 4.1) uses the device's AVB MAC address for LLDP and RSTP negotiations, as well as IGMP. Traffic from the AVB MAC address is seen on all ports. In FW 4.1.2.9, a bug may report the Dante MAC in the media_avb_2 interface; the correct MAC is active and visible in the AVB Settings tab. MAC addresses seen in a Wireshark trace on P1 will be sequential: control using the lowest number, media_avb_2 next, and media_voip_3 following.

A screenshot shows the 'Network Port Mode Settings' dialog with options for 'Dedicated Control and Media', 'Dedicated Control, VoIP and Media', and 'Converged Control, VoIP and Media'.

Network Port Modes FW 4.2 and Later

Tesira software version 4.2 or higher is required for devices running firmware 4.2 or higher. TesiraFORTÉ X supports 3 different network port modes in FW 4.2.x and later, aligning with other Tesira products.

Unique port behaviors include a shared interface for control+VoIP or control+VoIP+AVB, and a common media network that converges AVB and Dante.

Connecting to P1 for Tesira device discovery is safe if the PC and device are in a common IP address range. The default network port mode remains Control and VoIP on port 1, and Media (AVB & Dante) on ports 2-5.

New 4.2 Behavior:

• Introduces a converged port mode, equivalent to single-cable mode in Server-IO or TesiraFORTÉ AVB, carrying Control, VoIP, AVB, and Dante on a single uplink.
• Introduces a dedicated port mode with P1 for Control and P2 for VoIP, similar to Server-IO or TesiraFORTÉ VI/VT. For systems requiring a dedicated VoIP interface and single-cable control/media, the Dedicated Control, VoIP and Media mode can be used, leaving P1 disconnected. Control and discovery are supported on media ports (P3-5), with VoIP allocated to P2.
• Media port connections to 3rd party switches support both AVB and Dante on a shared port.
• A TC-5D can host additional Dante IO with a TesiraFORTÉ X in converged network port mode. In the TC-5D, 3rd party switch connections are either AVB or Dante capable, not both. AVB MSRP packets determine the port role. A TC-5D connected via P1 to a TesiraFORTÉ X passes both AVB and Dante on a shared link, but the TC-5D applies media filter rules. TC-5D should not have media traffic filtering enabled on P1 when connected to TesiraFORTÉ X. Linking stand-alone Dante and AVB networks through a TesiraFORTÉ X or TC-5D bridges these networks.
• Improves default behavior by blocking layer 2 network queries originating from the AVB MAC address across all interfaces; these queries are now restricted to media interfaces.

TesiraFORTÉ X achieves different port modes via rules imposed on the internal switch.

Switching between port modes is allowed. If DHCP addresses have been acquired, changing modes might take up to 10 minutes for the device to release old addresses and fall back to link local if new DHCP servers don't provide new IP information. When changing modes, leave only P1 connected to prevent traffic issues and odd DHCP behaviors. Reboot the device after changing port modes and connect remaining ports as appropriate.

Network settings are accessible via Tesira software for manual configurations or via the web UI for Launch-enabled TesiraFORTÉ X devices. Maintaining unique IP address subnets per network is crucial to prevent accidental misrouting.

The AVB MAC address is the origin for layer 2 LLDP, RSTP, and IGMP discovery traffic, guaranteed to be used in all modes. LLDP and RSTP queries are restricted to media interfaces in firmware 4.2 and higher. TesiraFORTÉ X acts as both an LLDP querier and responder. RSTP is enabled only on media ports. IGMP, if enabled, uses the AVB MAC as its querier.

Gateway, Domain, and DNS Server Set

Control, VoIP, and Media share a common IP stack, meaning there is only one gateway, one domain, and one DNS server set. Tesira software allows specifying different gateway and DNS addresses per interface. In firmware releases 4.2.x and later, if multiple interfaces present valid gateway or DNS addresses, one is selected based on a fixed prioritization scheme:

1. VoIP: (when VoIP VLAN is enabled or Separated Control, VoIP, and Media ports are selected and VoIP line settings are populated)
2. Control: (shares the AVB interface in Converged Control, VoIP, and Media port mode)
3. Media: (Dante)

IP address, net mask (subnet range), gateway, and DNS settings can be assigned statically or provided via DHCP.

A network interface state (up or down) determines its consideration in the prioritization scheme. An "Active" indication next to the "Current Default Gateway" field shows the selected gateway IP across all interfaces. If 802.1x authentication is used, routing to the authentication server via the default gateway must be possible. For DNS settings, manually configured DNS is preferred over DHCP-served DNS.

Tesira follows the Windows network settings model where DNS and gateway can be specified per-interface, using a hierarchy of VoIP, Control, or Media(Dante) for priority. In FW 4.0.x and 4.1.x, this hierarchy was not rigorously applied, potentially causing packet drops if Control and VoIP subnets had different gateways. FW versions 4.2.x and higher resolve this issue. For troubleshooting VoIP gateway priority with DHCP, consider setting the control interface to a static IP/netmask or setting VoIP settings statically.

Port Settings

Changing Port Mode Settings

It is recommended that only port P1 remain connected while reconfiguring device port modes. After changing a device's port mode setting, reboot the device (soft or hard reboot) to ensure new port rules are properly applied and DHCP configuration can take place. Connect other ports in alignment with the new network mode setting.

Dedicated Control and Media (Default)

This is a separated network mode where Control and VoIP share P1, and media is on P2-P5.

• P1: Dedicated to Tesira control and VoIP.
  • VoIP shares the same MAC address and IP address, subnet, and gateway as control unless VoIP VLAN tagging is enabled and a VoIP VLAN ID is assigned.
  • If VoIP VLAN tagging is enabled, VoIP uses a unique MAC address, IP address, subnet, and gateway, serving as the default gateway.
  • Control (P1) supports 802.1x authentication in Dedicated Control and Media mode. For VoIP 802.1x, the Dedicated Control, VoIP and Media mode must be used.
• P2-5: Dedicated to media (AVB and/or Dante).
  • AVB has a unique MAC and IP address.
  • Dante has a unique MAC and IP address.
• P2-5 support PoE+.

Dedicated Control, VoIP and Media

This is a separated network mode where Control uses P1, VoIP uses P2, and media is on P3-P5.

• P1: Dedicated to Tesira control.
  • Control has a unique MAC and IP address.
  • Control (P1) supports 802.1x authentication in Dedicated Control, VoIP and Media mode.
• P2: Dedicated to VoIP.
  • VoIP has a unique MAC and IP address.
  • The VoIP gateway is the default gateway of the device.
  • VoIP can be assigned a VLAN ID.
  • VoIP (P2) supports 802.1x authentication in Dedicated Control, VoIP and Media mode.
• P3-5: Dedicated to media (AVB and/or Dante).
  • AVB has a unique MAC and IP address.
  • Dante has a unique MAC and IP address.
• P2-5 support PoE+.

Systems requiring a dedicated VoIP interface and single-cable mode for control and media are supported by setting the device to Dedicated Control, VoIP and Media network mode, then leaving P1 disconnected. Control and discovery are supported on the media ports (P3-5), and VoIP is allocated to P2. In this single-cable mode, P1 (control) must be left disconnected, similar to Forte AVB devices.

Converged Control, VoIP and Media

This is a single-cable mode (converged network mode) where all ports are capable of all functions. In Converged mode, Control, VoIP, AVB, and Dante are all available on a single network link.

• If multiple links are made from TesiraFORTÉ X to the same network, a loop will form, causing a broadcast storm.
• If multiple links are made from TesiraFORTÉ X to multiple networks (1 link per network), those networks are bridged by TesiraFORTÉ X.
• P1-5 support single-cable AVB and control connections with other Tesira devices. Control MAC and IP address are disabled. The AVB MAC and IP address serve as the Tesira control interface.
• P1-5 support the device's VoIP connection.
  • If VoIP VLAN is not enabled, VoIP MAC and IP address are disabled and VoIP shares the AVB interface.
  • If VoIP VLAN is enabled, VoIP has a unique IP address, subnet, and gateway, which is the default gateway.
• P1-5 support Dante connections with other devices. Dante has a unique MAC and IP address.
• P2-5 support PoE+.
• 802.1x authentication is not supported in the Converged Control, VoIP and Media port mode.

Interface Types

Control

Tesira device discovery and control deal with inter-device Tesira behavior. Tesira DSP hardware is designed to execute large system files across multiple physically separate DSP components as one device. Device discovery and communications use proprietary inter-device protocols on the control channel. AVB media is shared between devices on the AVB interface.

Tesira supports different inter-device network topologies: Separated mode places control on one network and AVB on a logically separated network. Single-cable mode allows Tesira devices to share control and AVB media on a single link. TesiraFORTÉ X also allows Dante and VoIP traffic on the common connection.

3rd party Tesira Text Protocol (TTP) control traffic uses a different protocol than inter-Tesira communications. 3rd party TTP control can be implemented on any of TesiraFORTÉ X's IP addresses using SSH or telnet, if enabled. The TesiraFORTÉ X web UI is similarly available on any of the device's IP addresses.

VoIP

TesiraFORTÉ X VoIP supports the use of a tagged VLAN, definable in the VoIP interface network settings, or can function without a VLAN. When a VoIP VLAN is not enabled, VoIP shares the Control MAC and IP address on P1 (under Dedicated Control and Media mode) or the AVB MAC and IP address visible on all ports P1-P5 (under Converged Control, VoIP and Media mode).

Use of a VLAN enables a dedicated VoIP MAC and IP address on P1 (under Dedicated Control and Media mode) and on all ports P1-P5 (under Converged Control, VoIP and Media mode). VoIP X always has a unique MAC and IP address on P2 when the Dedicated Control, VoIP and Media port mode is selected.

Media (AVB and Dante)

In FW 4.0 and 4.1, TesiraFORTÉ X media ports (P2-5) use "auto" media detection via LLDP to determine if the device at the other end is a Biamp device. If it is a Biamp device, both AVB and Dante traffic are allowed. If not a Biamp device, TesiraFORTÉ X checks for MSRP traffic. If MSRP traffic is received, AVB traffic is allowed but not Dante. If no MSRP traffic is received, Dante traffic is allowed but not AVB.

TC-5 and TC-5D continue to observe LLDP and MSRP based rules for 3rd party switch connections in 4.2 firmware. A 3rd party switch connected to these devices will see AVB or Dante on a link, but not both.

In FW 4.2 and later, the "auto" media detection behavior is deprecated. A single media port connection carries both AVB and Dante to 3rd party switches. Control, VoIP, Dante, and AVB can uplink on a single cable to another switch. Other ports of TesiraFORTÉ X are typically used for local endpoint devices (Dante or AVB). If multiple switches are connected to TesiraFORTÉ X, they will be bridged by it.

Connections from TesiraFORTÉ X to TC-5, TC-5D, or 3rd party switches simultaneously support AVB and Dante, eliminating the need for two cable connections and the possibility of creating loops or bridging different media networks. Using TesiraFORTÉ X with TC-5 or TC-5D allows leveraging legacy port behavior to filter media traffic or use TesiraFORTÉ X ports for AVB and Dante on a common link.

Device Logs

Device logs show network configuration information. An example log entry includes timestamps, device identifiers (e.g., DevioSCX04303078), NOTICE level, and details such as current network configuration, DNS status, domain name, nameservers, interface names (control, media_avb_2, media_voip_3), DHCP status, MAC addresses, IP addresses, netmasks, gateways, hostnames, and switch port modes. Logs also detail network updates, DNS source selection, RSTP port state changes, IP route information, operating environment versions, power-up sequences, link status changes, and media start events.

MAC Addresses

Each TesiraFORTÉ X has five device MAC addresses, visible in Event Logs, the Equipment Table, and Device Maintenance. Port scans reveal up to four MAC addresses in use, specific to the port role. The MAC addresses are sequential:

1. Control (control)
2. AVB (media_avb_2)
3. VoIP (media_voip_3)
4. Dante (DAN Primary[Slot 2])
5. (not implemented)

When port mode settings change, discoverable MAC addresses per port will change. Each active MAC address receives an IP address within unique logical subnets for proper behavior. TesiraFORTÉ X uses the AVB MAC address for LLDP and RSTP negotiations on media ports and for IGMP negotiations on all ports when IGMP is enabled. During its boot sequence, all MAC addresses may briefly appear on all ports before port rules are applied.

Web Interface and TTP Communication

The web UI is accessible via any of the device's IP addresses using a valid port, providing access to Control, AVB, Dante, and VoIP interfaces depending on the port mode. The set of available webpages varies based on whether the device is Launch-capable/configured or manually configured. Network settings are available via the web UI for Launch-capable devices and via Tesira software for manually configured devices.

TTP communication is accessible via any IP address using a valid port. It allows communication via TTP command over respective ports, depending on port mode. TTP is available using SSH by default (can be disabled) and Telnet (disabled by default, can be enabled). 3rd party control systems can interact with TesiraFORTÉ X on any of its connected networks.

LLDP, RSTP, IGMP

LLDP

Link Layer Discovery Protocol (LLDP) is enabled on the media ports, with queries originating from the AVB MAC address. TesiraFORTÉ X acts as both an LLDP querier and responder.

RSTP

Rapid Spanning Tree Protocol (RSTP) is enabled by default and can be disabled in port mode settings, applying to all media ports. RSTP queries originate from the AVB MAC address and are used to prevent broadcast storms if a network loop occurs. RSTP interrupts network traffic for up to 60 seconds during negotiation. It must be enabled on all network devices to function correctly. If a switch with BPDU guard enabled blocks Tesira RSTP queries, disable RSTP on the Tesira device. It is advisable to set the Tesira RSTP state while it is not connected to the other switch.

IGMP

Internet Group Management Protocol (IGMP) is disabled by default but can be enabled in port mode settings for all ports. IGMP (v2) manages multicast traffic. When enabled, TesiraFORTÉ X acts as an IGMP querier using its interface address. When disabled, it responds to IGMP requests but does not act as a querier. If IGMP is used, at least one IGMP querier IP address must be specified in the network; the switch with the lowest querier IP address is the preferred querier. IGMP queries and responses may originate from any of the device's MAC addresses.

DHCP / IP Address Behavior

TesiraFORTÉ X port settings allow multiple interfaces to be part of a common physical network. In dedicated network modes, each network segment (control, VoIP, media) is expected to have a unique logical subnet for IP addressing. In converged mode, all interfaces are in a common network.

DHCP servers present: Interfaces are DHCP-capable by default and default to link local (APIPA) addresses if no DHCP server is present. Static addresses can be set. When ports are part of a common group (e.g., P2-5 media), they belong to a common network, expecting a unique logical subnet. If two separate media networks converge, DHCP addressing is acquired by all connected interfaces unless static IPs or special DHCP rules are used. DHCP allocation can be managed by MAC reservation or exclusion. Allowing DHCP address allocation between converged networks requires careful planning to avoid network disruption.

No DHCP servers present: If no DHCP servers are present and no static IP addresses are applied, all interfaces will take link local (APIPA) addresses. This is not an expected operational condition and must be resolved using DHCP servers or static IP addressing. Each network is expected to have a unique logical subnet.

Device Interconnections

Biamp TesiraFORTÉ X devices are primarily intended for limited scope systems like conference rooms. Up to four devices can be used within a single media network cluster when used with TC-5 and/or TC-5D. When connecting TesiraFORTÉ X, TC-5, or TC-5D to each other, it is critical to connect port 1 (P1) of one device to ports 2-5 (P2-P5) of another device. Never connect P2-P5 of one device to P2-P5 of another, as this can cause internal damage to the Biamp hardware.

When connecting a TC-5, TC-5D, or TesiraFORTÉ X to a third-party network switch, always use port 1 (P1) of the device. If connecting devices via P2-5, only non-PoE-capable network switches can be connected; disabling PoE on a PoE-capable switch is insufficient, and internal damage may occur.

Biamp recommends using only unshielded (UTP) network cabling. If shielded (STP) cabling must be used, an unshielded inline RJ45 coupler is required to lift the shield connection between devices. This coupler can be installed at either end of the cable with a short jumper between the coupler and the endpoint. Internal damage to the Biamp hardware may occur if this restriction is not observed.

STP or UTP Cable

The use of shielded twisted pair (STP) cable is not permitted with TesiraFORTÉ X due to additional ground paths on analog inputs and outputs, USB, and GPIO. If STP wiring must be used, Biamp strongly recommends using an unshielded inline RJ45 coupler to lift the shield connection between devices. This can be placed at either end of the link with a short jumper between the coupler and the endpoint. Internal damage to the Biamp hardware may occur if this restriction is not observed.

PoE+

TesiraFORTÉ X is a network appliance with five 1GB Ethernet ports; four of these ports (2-5) can supply PoE+ to connected peripherals. When linking TesiraFORTÉ X devices together or with TC-5 or TC-5D, always connect port 1 (P1) of one device to ports 2-5 (P2-P5) of another device. Never connect P2-P5 of one device to P2-P5 of another, as this can cause internal damage. When connecting to a third-party network switch, always use port 1 (P1) of the Biamp device. If connecting via P2-5, only non-PoE-capable network switches can be connected; internal damage may occur if this restriction is not observed. For PoE-capable 3rd party switch requirements on P2-5, contact support@biamp.com.

Downgrading Firmware

IMPORTANT: If a TesiraFORTÉ X running FW 4.2 or later is downgraded to 4.0 or 4.1 while in a non-default network port mode, a pinhole reset followed by a hard power cycle will be required to recover the device to a discoverable state. This is because alternate port modes did not exist in the 4.0 and 4.1 FW code, leaving ports in an invalid condition until reset and rebooted. This can be avoided by setting port modes to the default before downgrading or by not downgrading firmware.