Network Interfaces, Transceiver, Optic, and Cable Requirements
Preseem requires one network interface for management and cloud connectivity. Any NIC can be used for this purpose. Interfaces that carry subscriber traffic must use one of the supported chipsets below, running at least the listed firmware and driver versions.
Supported NICs (Preseem 2.x)
|
NIC |
Ports / Speed |
Min. Firmware |
Driver |
|
Intel E810-C for QSFP |
2 × 100G |
4.60 |
ice 1.15.4 |
|
Intel E810-C for SFP |
4 × 25G |
4.60 |
ice 1.15.4 |
|
Intel E810-XXV for SFP |
2 × 25G |
4.60 |
ice 1.15.4 |
|
Intel E823-C for QSFP |
QSFP |
3.42 |
ice 1.15.4 |
|
Intel E823-L for QSFP |
QSFP |
3.42 |
ice 1.15.4 |
|
Intel E822-L (backplane only) |
Backplane |
3.42 |
ice 1.15.4 |
|
Intel E825-C for QSFP |
QSFP |
3.75 |
ice 2.1.0_rc23 |
|
Intel E830-XXVDA2 (OCP) |
2 × 25G |
1.00 |
ice 1.15.4 |
|
Intel E830-CQDA2 |
2 × 100G |
1.00 |
ice 1.15.4 |
|
Intel E610-XT2 |
2 × 10G |
1.00 |
ixgbe 5.21.5 |
|
Intel E610-XT4 |
4 × 10G |
1.00 |
ixgbe 5.21.5 |
|
Intel X710-DA4 |
4 × 10G |
9.52 |
i40e 2.26.8 |
|
Intel X722 for SFP+ |
2 × 10G |
6.50 |
i40e 2.26.8 |
|
Intel XXV710-DA2 |
2 × 25G |
9.52 |
i40e 2.26.8 |
|
Intel XL710-QDA2 |
2 × 40G |
9.52 |
i40e 2.26.8 |
Preseem 1.x: The Intel i210 and i350-T4 (1G copper) are supported on Preseem 1.x only.
Transceiver Compatibility
Transceivers on Preseem interfaces must meet specific encoding requirements. For SFP and SFP+ interfaces, use Intel-encoded or generic-encoded optics. For SFP28, QSFP+, and QSFP28 interfaces, use Intel-encoded optics only. Transceivers on your connected switches and routers should follow that vendor's own requirements.
For full details, including supported range types, cabling, and recommended vendors, see NIC, Transceiver and Cable Requirements.
Transceiver, Optic, and Cable RequirementsThis page covers the transceivers, optics, and cables to use with Preseem, including encoding recommendations, vendor considerations, and guidance on choosing the right optic for your deployment.
NIC Requirements
Preseem appliances ship with supported NICs already installed. If you're running Preseem on your own hardware, the interfaces that carry subscriber traffic must use a supported Intel chipset. See Generic Hardware for the current list of supported NICs, firmware, and driver versions.
To see which optics fit each Preseem appliance module, see NIC Modules.
Transceiver Encoding: Preseem Interfaces
To ensure compatibility and stable throughput, we strongly recommend the following encoding for all transceivers used on Preseem interfaces:
- SFP and SFP+ interfaces: Intel-encoded or generic-encoded transceivers.
- SFP28, QSFP+, and QSFP28 interfaces: Intel-encoded transceivers only.
Transceivers with other encodings may still work, but we can't guarantee link functionality, stability, or consistent traffic performance.
|
Optic Type |
Maximum Speed |
Recommended Encoding |
|
SFP |
1 Gbps |
Intel or generic |
|
SFP+ |
10 Gbps |
Intel or generic |
|
SFP28 |
25 Gbps |
Intel only |
|
QSFP+ |
40 Gbps |
Intel only |
|
QSFP28 |
50 / 100 Gbps |
Intel only |
Transceiver Encoding: Switches and Routers
Transceivers on the devices connected to Preseem, such as switches and routers, should follow that device vendor's requirements. Depending on the vendor, this may mean:
- vendor-encoded transceivers (for example, MikroTik-compatible optics)
- OEM-locked modules
- vendor-approved optics only
In practice, each end of a link may need a differently encoded optic. The Preseem side follows Preseem's recommendations, and the switch or router side follows its vendor's.
Choosing an Optic
Choose an optic that matches your link's speed, distance, and fibre type. For most deployments, short-range (SR) optics over multimode fibre are the preferred choice. Use long-range (LR) optics over single-mode fibre when the run is longer than your SR optic's rated reach.
Typical multimode (SR) reach by speed
|
Optic |
OM3 Fibre |
OM4 Fibre |
|
10G SR |
300 m |
400 m |
|
25G SR |
70 m |
100 m |
|
40G SR4 |
100 m |
150 m |
|
100G SR4 |
70 m |
100 m |
For longer runs, LR optics typically reach up to 10 km over single-mode fibre.
Supported optic and cable types
|
Type |
Media |
Typical Use |
|
SR |
Multimode fibre |
Short-range 10G and 25G links |
|
SR4 |
Multimode fibre |
Short-range 40G and 100G links |
|
LR |
Single-mode fibre |
Long-range 10G and 25G links (up to ~10 km) |
|
LR4 |
Single-mode fibre |
Long-range 40G and 100G links (up to ~10 km) |
|
ER |
Single-mode fibre |
Extended-range links (up to ~40 km) |
|
CR / CR4 |
Direct-attach copper (DAC) |
Very short links within a rack |
|
AOC |
Active optical cable |
Short links where DAC reach isn't enough |
Supported Cables
- Single-mode fibre (OS2): for LR and ER optics.
- Multimode fibre (OM3 or OM4): for SR optics. OM4 is preferred for the best reach and performance.
- Direct-attach copper (active or passive DAC): only where both the Preseem NIC and the connected device support it. DAC encoding should follow the same recommendations as transceivers.
- Active optical cable (AOC): for short links where DAC reach isn't enough.
- Copper Ethernet (Cat6 or better): for RJ-45 data ports. Cat6 is recommended for 2.5G links, such as the onboard ports on the Preseem 15K.
Cabling Guidelines
- Match the cable to the optic. Single-mode optics need single-mode fibre, multimode optics need multimode fibre, and DAC and AOC are self-contained.
- Use the connector type your optics require, for example LC-LC or MTP/MPO, and keep cable lengths within the optic's rated reach.
- Order matching transceivers for both ends of every link, for example Preseem to router and Preseem to switch. Mismatched optics or cable types are a common cause of links not coming up, link flapping, and wire errors.
Recommended Vendor
We use and recommend transceivers from FS.com. These optics are widely used and validated in our lab environments. When ordering from FS.com for SFP28, QSFP+, or QSFP28 interfaces, select Intel-compatible coding.
Serial Console Access
Each appliance is supplied with a USB console cable to facilitate direct serial connectivity. This connection is utilized for initial setup, low-level configuration adjustments, or diagnostic procedures whenever network connectivity is inaccessible. For a complete step-by-step walkthrough on establishing a console connection, refer to Section 4 (Installation & Activation).
Questions?
For specific model numbers or detailed compatibility questions, contact us.