Interconnect Maximum Effective Data Rates

These tables list the maximum effective data rates, in a single data flow direction, for various data interconnect protocols. A best effort attempt has been made to exclude physical link encoding overheads where appropriate.

PCI Express 5.0Maximum Effective Data Rate (One Direction)
(10242 Bytes) MiB/s(10002 Bytes) MB/s(10003 Bits) Gb/sNotes
x13,7563,93831.5
x27,5127,87763.0NVMe M.2 (M+B Key)
x415,02415,754126NVMe M.2 (M Key)
U.2/U.3 (1x4 or 2x2)
E1.S/E1.L (typical)
E3
x830,04831,508252.1E1.S/E1.L (max)
E3
x1660,09663,015504.1E3 (max)
PCI Express 4.0Maximum Effective Data Rate (One Direction)
(10242 Bytes) MiB/s(10002 Bytes) MB/s(10003 Bits) Gb/sNotes
x11,8781,96915.8
x23,7563,93831.5NVMe M.2 (M+B Key)
x47,5127,87763.0NVMe M.2 (M Key)
U.2/U.3 (1x4 or 2x2)
E1.S/E1.L (typical)
E3
x815,02415,754126.0E1.S/E1.L (max)
E3
x1630,04831,508252.1E3 (max)
PCI Express 3.0Maximum Effective Data Rate (One Direction)
(10242 Bytes) MiB/s(10002 Bytes) MB/s(10003 Bits) Gb/sNotes
x19399857.9
x21,8781,96915.8NVMe M.2 (M+B Key)
x43,7563,93831.5NVMe M.2 (M Key)
U.2/U.3 (1x4 or 2x2)
x87,5127,87763.0
x1615,02415,754126.0
SAS-4 (24 Gb/s)Maximum Effective Data Rate (One Direction)
(10242 Bytes) MiB/s(10002 Bytes) MB/s(10003 Bits) Gb/s
x12,2892,40019.2
x49,1559,60076.8
x818,31119,200153.6
SAS-3 (12 Gb/s)Maximum Effective Data Rate (One Direction)
(10242 Bytes) MiB/s(10002 Bytes) MB/s(10003 Bits) Gb/s
x11,1441,2009.6
x44,5784,80038.4
x89,1529,60076.8
SAS-2 & SATA 3.0 (6 Gb/s)Maximum Effective Data Rate (One Direction)
(10242 Bytes) MiB/s(10002 Bytes) MB/s(10003 Bits) Gb/s
x15726004.8
x42,2892,40019.2
x84,5764,80038.4
EthernetMaximum Effective Data Rate (One Direction)
(10242 Bytes) MiB/s(10002 Bytes) MB/s(10003 Bits) Gb/s
1 GbE1191251.0
10 GbE1,1921,25010.0
25 GbE2,9803,12525.0
40 GbE4,7685,00040.0
100 GbE11,92012,500100.0
200 GbE23,84225,000200.0
400 GbE47,68450,000400.0
Fibre ChannelMaximum Effective Data Rate (One Direction)
(10242 Bytes) MiB/s(10002 Bytes) MB/s(10003 Bits) Gb/s
8 Gb7738106.5
16 Gb1,5451,62013.0
32 Gb3,0913,24125.9
64 Gb6,5436,86154.9

Interface Configuration

TrueNAS supports configuring different types of network interfaces such as a standard interface, network bridge, LAGG, and VLAN interfaces to use as part of the various backup, sharing, and virtualization features in TrueNAS. The tutorials in this section guide you through each of the various network interface configurations.

Why should I use different interface types?

A LAGG (Link Aggregation) optimizes multi-user performance, balances network traffic, and provides network failover protection. In a failover it prevents a network outage by dynamically reassigning traffic to another interface when a physical link, like a cable or NIC, fails.

Read full post gdoc_arrow_right_alt

Managing Network Configurations

Use the Network Configuration Settings widget shows existing general network settings like the default gateway and DNS servers, set services allowed to externally communicate, enter an HTTP proxy, or host name database.

You can lose your TrueNAS connection if you change the network interface that the web interface uses! You might need command line knowledge or physical access to the TrueNAS system to fix misconfigured network settings.

Read full post gdoc_arrow_right_alt

Setting Up a Network Bridge

In general, a bridge refers to various methods of combining (aggregating) multiple network connections into a single aggregate network.

TrueNAS uses bridge(4) as the kernel bridge driver. Bridge(8) is a command for configuring the bridge in Linux. While the examples focus on the deprecated brctl(8) from the bridge-utilities package, we use ip(8) and bridge(8) from iproute2 instead. Refer to the FAQ section that covers bridging topics more generally.

Network bridging does not inherently aggregate bandwidth like link aggregation (LAGG). Bridging is often used for scenarios that require extending a network segment or combining different types of network traffic.

Read full post gdoc_arrow_right_alt

Configuring IPv6

TrueNAS provides the option to configure network interfaces using either IPv4 or IPv6 addresses. IPv4 networks cannot see or communicate with an IPv6 website or network unless a gateway or some other implementation is configured to allow it. See Understanding IPv6 for more information.

Configuring IPv6 Addresses

After configuring your network infrastructure for IPv6, assign the IP addresses for your TrueNAS system. Use the TrueNAS UI to configure your network settings. If setting TrueNAS up for the first time after a clean install, use the Console Setup menu to enter IPv6 addresses.

Read full post gdoc_arrow_right_alt

Configuring Static Routes

TrueNAS does not pre-define static routes by default, but TrueNAS administrators can manually add static routes if they want or need to enter routes to a router to send packets to a destination network.

Static routes are not aliases, they are fixed IP addresses assigned as alternative routes for network traffic sent to a specific destination (server, device) in the network.

You can use the Console Setup menu during installation or any time after the initial system configuration to add a static route through an SSH session or by connecting a monitor and keyboard to the system, but we recommend using the web UI to make changes to the network configuration.

Read full post gdoc_arrow_right_alt

Network Configuration

Network configuration covers global network settings, interface options, and platform-specific configurations.

Contents

Setting Up a Link Aggregation

In general, a link aggregation (LAGG) is a method of combining (aggregating) multiple network connections in parallel to provide additional bandwidth or redundancy for critical networking situations. TrueNAS uses lagg(4) to manage LAGGs.

Before You Begin

Read full post gdoc_arrow_right_alt

Setting Up IPMI

IPMI requires a compatible motherboard with IPMI support. Refer to your hardware documentation to determine compatibility.

Many TrueNAS systems include a built-in out-of-band management port, enabling system access even when the web interface is unavailable.

Intelligent Platform Management Interface (IPMI) allows users to check the log, access the BIOS setup, and boot the system without physical access. IPMI also enables users to remotely access the system to assist with configuration or troubleshooting issues.

Read full post gdoc_arrow_right_alt

TrueNAS Hardware Guide

TrueNAS Enterprise systems use components that are qualified and tested by the TrueNAS team to offer the best storage and performance with TrueNAS Enterprise Edition.

This guide will go over the minimum hardware requirements and offer suggestions for TrueNAS Community Edition users.

Minimum Hardware Requirements

ProcessorMemoryBoot DeviceStorage
Any x86_64 compatible (Intel or AMD) processor8 GB memory20 GB SSD boot deviceTwo identically-sized devices for a single storage pool

Storage Considerations

The heart of any storage system is the symbiotic pairing of the file system and physical storage devices. The ZFS file system in TrueNAS provides the best available data protection of any file system at any cost and makes effective use of spinning-disk storage, all-flash storage, or a mix of both. ZFS is prepared for the eventual failure of storage devices and is highly configurable to achieve the perfect balance of redundancy and performance to meet any storage goal. A properly configured TrueNAS system can tolerate multiple storage device failures and recreate its boot media with a copy of the configuration file.

Read full post gdoc_arrow_right_alt