HOT CROSS-REFERENCE SEARCHES All Products
HR911105A Cisco GLC-LH-SMD Pulse J1011F21PNL LPJG0926HENL TE 2170704-1 SFP-10G-SR
POPULAR CATEGORIES
Matched Parts (Real-time ES) Use ↑ ↓ to select, Enter to open
EMBEDDED MAIN BOARDS · BOARD-LEVEL ETHERNET

Board-Level Ethernet Design for Embedded and Industrial Motherboards

Design multi-LAN copper and fiber interfaces from the host controller to the physical port. LINK-PP supports the board-level portion of the path with integrated RJ45 magnetics, discrete LAN transformers, modular jacks, SFP/SFP+ cages and transceiver options selected around the exact PHY, speed, pinout, thermal and mechanical requirements.

INDUSTRIAL MOTHERBOARD · ETHERNET SIGNAL PATHS CPU / SoC MAC · PCIe ROOT · SERDES SoC MAC → EXTERNAL PHY RMII / RGMII / SGMII 1G / EMBEDDED COPPER PCIe NIC MULTI-LAN 2.5G / 5G / 10G SERDES / FIBER HOST SFP / SFP+ CAGE PLUGGABLE OPTICAL I/O MDI PHYSICAL CHANNEL PHY → MAGNETICS → RJ45 IMPEDANCE · CMRR · ISOLATION PORT DENSITY RJ45 × N LAN 1 · 2 · 3 · 4 PLUGGABLE PATH HOST → CAGE → MODULE POWER · I2C · EMI · THERMAL SCHEMATIC → LAYOUT → PHY MATCH → EMC → PRODUCTION VALIDATION
BOARD-LEVEL ETHERNET CONNECTIVITY PHY-MATCHED / LAYOUT-AWARE / SECOND-SOURCE READY

Quick answer: a reliable motherboard Ethernet port is a complete channel, not a connector choice. Start with the CPU/SoC or PCIe Ethernet controller, define the MAC-to-PHY interface, select the PHY, then qualify MDI routing, magnetics, RJ45 or SFP host hardware, power rails, shielding, protection and thermal conditions together. A part can match the footprint and still be electrically wrong for the selected PHY.

100M–10G

Board-Level Ethernet

RMII · RGMII · SGMII

MAC-to-PHY Paths

RJ45 · SFP

Copper & Fiber I/O

PHY → Port

Signal / EMI / Thermal

BOARD FORM FACTORS

Industrial Motherboard Ethernet Requirements Vary by Board Architecture

Mini-ITX, MicroATX, SBC and carrier-board designs can all use the same Ethernet standards while presenting very different lane budgets, I/O density, connector mechanics and thermal constraints.

MINI-ITX

Compact Multi-LAN Mainboards

Often combine integrated CPU/SoC connectivity with one or more PCIe Ethernet controllers. Front-panel density and limited thermal area make controller placement, RJ45 height and adjacent-port heat important.

2.5GbEMulti-LANCompact
MICROATX

Higher I/O and Expansion Density

More PCIe resources can support multiple Ethernet controllers, add-in networking and higher-rate copper. Lane allocation must still coexist with storage, GPU and other expansion requirements.

PCIe2.5G10G
SBC / EMBEDDED BOARD

SoC MAC + External PHY

Embedded processors commonly expose MAC interfaces that connect to external PHYs through RMII, RGMII or SGMII. Clocking, straps, MDIO/MDC, reset and MDI routing become central design tasks.

MACPHYRGMII
CARRIER / CUSTOM BOARD

Application-Specific Ethernet I/O

Carrier boards may mix modular compute with custom RJ45, PoE and SFP interfaces. The designer owns the physical-layer BOM, grounding boundary, protection network and connector mechanics.

RJ45PoESFP
HOST-TO-PORT ARCHITECTURE

Choose the Ethernet Architecture Before Choosing the Connector

The same RJ45 can sit behind very different host paths. Compare SoC MAC, PCIe multi-LAN, 10G copper and SFP/SFP+ fiber architectures before freezing the physical interface.

SoC MAC + EXTERNAL PHY CPU / SoC MAC RGMII / SGMII ETHERNET PHY MAGNETICS / RJ45 DESIGN CHAIN MAC → RGMII/SGMII → PHY → MDI → MAGNETICS → RJ45

SoC MAC + External PHY

Common embedded-board path for 10/100/1000 Ethernet

  • DIGITAL SIDEMAC-to-PHY InterfaceValidate RMII/RGMII/SGMII timing, voltage levels, clocking, reset, straps and MDIO/MDC behavior against the processor and PHY reference designs.
  • ANALOG SIDEPHY-to-Magnetics MDITreat the MDI as a controlled differential path with the PHY vendor's recommended placement, reference planes, termination and magnetic characteristics.
  • BOARD EDGEMagnetics + RJ45Qualify pin mapping, OCL, turns ratio, return loss, shield, LEDs, height, temperature and optional PoE requirements together.
CONTROLLER / PHY / PORT MAPPING

Map Every LAN Port Back to Its Host Controller

A multi-LAN motherboard should be documented from the CPU or SoC outward. Controller topology determines PCIe usage, PHY implementation, power, software support and ultimately which magnetics or pluggable interface can be used.

Board Port
Host Path
Line-Side Architecture
Physical I/O
LAN 1
SoC MAC
RGMII / SGMII1G PHY
MagJack or transformer + RJ45
LAN 2
PCIe Controller
2.5G PHY
Multi-gigabit copper RJ45
LAN 3
PCIe Controller
5G / 10G PHY
High-speed copper RJ45 where supported
Fiber Port
NIC / SerDes
SFP HostSFP+ Host
Cage + pluggable optical module
This is an architecture template, not a universal motherboard topology. The exact controller/PHY partition depends on the CPU/SoC, NIC, BIOS/firmware and board design.
MULTI-LAN HOST RESOURCES

PCIe Lane Budget Comes Before Multi-Port Ethernet Density

On x86 and higher-performance embedded motherboards, 2.5G/5G/10G Ethernet controllers often consume PCIe resources that also compete with NVMe, GPU, wireless, fieldbus and expansion interfaces.

CPU / SoC PCIe Root Complex
→
Lane Budget Generation + Width
→
NIC Controllers 1G / 2.5G / 10G
→
PHY / Port RJ45 / SFP
Reserve lanes for the complete platform. Adding another Ethernet controller can affect storage or expansion resources even when the front-panel connector has physical room.

Lane Count

Confirm how many PCIe lanes each controller requires at the target generation and whether the platform exposes those lanes independently or through a shared switch.

Aggregate Throughput

Multiple high-rate ports can exceed the practical bandwidth of the host interconnect. Validate real simultaneous traffic rather than summing connector labels.

Competing I/O

NVMe, GPU, M.2, wireless and industrial expansion may share the same finite PCIe resources. Freeze the system resource map before committing to a multi-LAN BOM.

Controller Thermals

Each additional NIC or multi-gig PHY adds power and heat. Place controllers with the enclosure airflow and copper-spreading strategy in mind.

MAC-TO-PHY INTERFACE

RMII, RGMII, SGMII and PCIe Solve Different Board-Level Problems

The digital host interface ends at the PHY. The copper MDI begins on the other side. Treat those two routing domains separately and follow the selected processor, controller and PHY documentation.

Host Interface
Typical Role
Main Board Check
Physical-Layer Boundary
RMII
10/100 embedded
Clocking, voltage level, pin count and timing
PHY converts digital host traffic to Ethernet MDI
RGMII
1G SoC → PHY
Timing, skew, clock delay strategy and I/O voltage
PHY drives four-pair 1000BASE-T through magnetics
SGMII
Serial MAC / PHY
SerDes compatibility, clocking and PHY mode
PHY provides line-side copper or another media interface
PCIe
Standalone multi-gig NIC
Lane budget, generation, BIOS/driver and controller power
Controller/PHY implementation feeds copper or pluggable port
Do not copy generic trace-length numbers between unrelated processors or PHYs. The device vendor's reference schematic and layout guide take precedence.
100M → 10G BOARD DESIGN

What Changes as Motherboard Ethernet Speed Increases?

Higher speed affects the host controller, PHY, magnetics bandwidth, channel margin, power and thermal budget. A connector footprint carried forward from a 1G design is not proof of 2.5G/5G/10G capability.

Ethernet Rate
Common Host Path
Physical Interface
Board-Level Priority
10/100M
MCU / SoC + PHY
RMII / MIIRJ45
Basic timing, magnetics match, isolation, EMC and protection
1G
SoC MAC / PCIe NIC
RGMIISGMIIRJ45
Four-pair magnetics, digital timing, MDI routing and return loss
2.5G
PCIe / Integrated NIC
Multi-Gig PHYRJ45
Magnetics bandwidth, channel loss, cable support and PHY thermal
5G
PCIe NIC
Multi-Gig PHYRJ45
Signal margin, magnetics qualification, power and layout discipline
10GBASE-T
PCIe NIC + high-speed PHY
10G PHYRJ45
DSP power, heat, channel margin, connector/magnetics performance
10G Fiber
NIC / SerDes
SFP+
High-speed host channel, cage, module power, I2C, EMI and thermal
PHY-TO-MAGNETICS MATCHING

Match the Magnetics to the Exact Ethernet PHY

The PHY vendor's reference design defines the starting point. Compare electrical parameters, pin assignment and center-tap architecture before approving an integrated MagJack, discrete LAN transformer or replacement part.

PHY Requirements

  • PHY vendor and exact model
  • Supported Ethernet rate and mode
  • Reference schematic / BOM
  • Termination architecture
  • PoE center-tap requirements where applicable

Magnetics Parameters

  • Turns ratio
  • Open-circuit inductance (OCL)
  • Insertion and return loss
  • Crosstalk / common-mode rejection
  • Isolation and center-tap construction

Port Integration

  • Pin assignment and footprint
  • LED configuration
  • Shield and chassis strategy
  • Operating temperature
  • Connector height / tab orientation
Read the RJ45 Magnetics Design Guide →
MDI PCB ROUTING

Route PHY → Magnetics → RJ45 as One Controlled Analog Channel

The MDI side is not the same routing problem as RGMII or PCIe. Preserve differential behavior, reduce discontinuities and maintain the intended isolation/grounding boundary from the PHY to the cable interface.

Ethernet PHY MDI Driver / Receiver
→
Differential Pairs Controlled Impedance
→
Magnetics Isolation / CMRR
→
RJ45 Cable Interface
Use the selected PHY vendor's layout guide for actual spacing, skew, placement and reference-plane limits. Generic Internet dimensions are not a substitute for device-specific guidance.

Differential Impedance

Keep MDI pairs controlled and symmetric through layer changes, connector transitions and component pads. Avoid routing that introduces large discontinuities or long stubs.

Pair Matching

Maintain appropriate intra-pair symmetry and pair organization as required by the PHY and Ethernet rate. Do not apply digital-bus matching rules blindly to the analog MDI.

Reference Planes

Keep return paths and isolation boundaries consistent with the PHY/reference design and chassis strategy. Do not route cable-side traces through noisy digital or power regions without review.

Placement

Minimize unnecessary vias and cable-side trace length where practical, while respecting the PHY vendor's magnetics-placement and isolation recommendations.

MAGJACK OR DISCRETE MAGNETICS

Choose the Copper-Port Architecture Around the Board, Not a Habit

Integrated RJ45 magnetics can reduce BOM and placement complexity. Discrete transformers provide more freedom over component location and connector sourcing. Both still require PHY and system-level validation.

Integrated RJ45 MagJack

Combines the connector and Ethernet magnetics in one board-edge assembly. It can simplify BOM management and reduce separate cable-side routing, especially in compact multi-LAN designs.

Verify: PHY match · footprint · LEDs · shield · height · temperature · PoE

LAN Transformer + Modular RJ45

Separates the magnetic function from the connector. This can improve mechanical flexibility, support independent sourcing and allow the designer to place the magnetic stage around board constraints.

Verify: OCL · ratio · CMRR · routing · isolation boundary · connector pinout
MULTI-PORT COPPER

Design Multi-LAN RJ45 as a Port-Density Problem, Not Four Copies of One Port

Adjacent Ethernet controllers, PHYs, magnetics and connectors create shared thermal, EMC and mechanical constraints. Port count should be qualified as an integrated front-panel subsystem.

Controller Mapping

Document which MAC/NIC/PHY owns each front-panel port. This prevents firmware and production teams from treating electrically different ports as equivalent.

Port-to-Port Crosstalk

Evaluate magnetic and PCB coupling between adjacent channels, especially as port density and line rate increase.

Thermal Density

Multiple controllers and multi-gig PHYs can create localized hot spots behind a dense RJ45 bank. Measure board temperature under simultaneous traffic.

Mechanical Alignment

Keep connector pitch, shield tabs, chassis apertures, LED locations and cable insertion forces consistent with the enclosure design and assembly process.

POWER · SHIELD · EMI · PROTECTION

PHY Power Integrity, EMI and Board-Edge Protection

Industrial motherboards place Ethernet beside switching regulators, memory, storage and high-current I/O. PHY power integrity, chassis-current control, protection and thermal placement should be treated as one board-level system rather than independent checklist items.

PHY Power Rails

Follow the PHY/controller reference design for analog, core and I/O rails, sequencing, filtering and decoupling. Switching-regulator noise can surface as link instability or EMC problems.

RJ45 Shield / Chassis

Define the shield-to-chassis strategy as part of the enclosure EMC design. Do not assume the cable shield should always be tied directly to digital signal ground.

Isolation Boundary

Maintain the intended separation between PHY-side circuitry and the cable/chassis side of the Ethernet magnetic interface, including the cable-side routing and board-edge region.

ESD / EFT / Surge

Choose protection and placement appropriate to the Ethernet rate and selected PHY/application guidance. Coordinate TVS devices, discharge path, shield, magnetics and chassis return, then validate the finished board/system against the required immunity targets.

Thermal Placement

Keep higher-power NICs, PHYs and 10G copper sections away from heat-sensitive parts where possible and validate temperatures inside the actual enclosure under sustained traffic and worst-case port population.

PoE BOARD-LEVEL INTERFACE

PoE Changes the Magnetics and Copper-Power Design

For motherboards that source or receive power over Ethernet, the physical Ethernet channel must support the relevant center-tap, current, thermal and isolation requirements in addition to data signaling.

Ethernet PHY Data Path
→
PoE-Capable Magnetics Center Taps
→
RJ45 Contacts / Shield
+
PoE Power Path PSE / PD Circuitry
LINK-PP supplies Ethernet magnetics and connector components within a PoE design. The PSE/PD controller, system power budget and complete safety/thermal implementation belong to the motherboard/system design.

Electrical

  • Center-tap arrangement
  • Current capability
  • Transformer saturation margin
  • PHY / PoE reference design

Thermal

  • Connector contact heating
  • Magnetics temperature rise
  • PCB copper / current path
  • Worst-case port population

Mechanical / Safety

  • RJ45 contact construction
  • Shielding
  • Creepage / isolation as applicable
  • System-level compliance targets
PLUGGABLE FIBER I/O

Board-Level SFP / SFP+ Interfaces Need More Than a Cage Footprint

A pluggable optical port combines a host SerDes/NIC path, high-speed PCB channel, connector, cage, power, management signals and the selected transceiver. Mechanical MSA fit alone does not prove host compatibility.

Host Electrical Interface

Confirm the NIC/SerDes line rate and electrical host specification before selecting the cage and module class.

Management Signals

Plan I2C management plus host control/status signals such as transmit disable or loss-of-signal behavior as required by the implementation.

Cage / EMI / Mechanics

Evaluate cage footprint, connector, bezel opening, retention, shielding and grounding as a single mechanical/EMI assembly.

Power & Thermal

Budget module power and local airflow/heat spreading for the intended optic or copper module rather than assuming all SFP/SFP+ devices dissipate the same heat.

SECOND SOURCE / EOL

Qualify RJ45 Magnetics Replacements Beyond Pin-to-Pin Fit

Long-life embedded platforms frequently outlive one connector or magnetics supplier. Pin-to-pin compatibility is not the same as PHY compatibility: the replacement must preserve form, fit, electrical function and environmental requirements on the actual motherboard.

01

Identify Original PN

Collect the original MagJack, transformer or modular-jack part number and current motherboard revision.

02

Check Form & Fit

Compare footprint, dimensions, pinout, shield tabs, LEDs, height and connector orientation.

03

Check Electrical Function

Compare ratio, OCL, loss, CMRR, center taps, isolation, PoE requirements and PHY reference design.

04

Validate Prototype

Run link, packet, EMC, temperature and production-relevant tests before releasing the alternate source.

PROTOTYPE / PRODUCTION TRIAGE

Why Ethernet Works on One Board Revision and Fails on the Next

Use the failure signature to isolate digital-host, PHY, magnetic, MDI, power or EMC causes before swapping parts at random.

Failure
Likely Area
Check First
Common Mistake
No link after PCB respin
Digital / bring-up
PHY straps, reset, clocks, MDIO/MDC, MAC mode and pin mapping
Blaming the connector before confirming PHY initialization
100M works, 1G fails
MDI / magnetics
All four pairs, routing, transformer parameters, soldering and cable
Assuming two-pair success proves four-pair Gigabit integrity
1G works, 2.5G fails
Channel margin
PHY mode, magnetics bandwidth, channel loss, cable and auto-negotiation
Reusing a 1G magnetic part without multi-gig qualification
Random CRC errors
Signal / power / EMI
MDI layout, common-mode noise, PHY rails, shield strategy and thermal state
Treating software as the only cause because the link stays up
EMC test fails
Common-mode / chassis
RJ45 shield, magnetics, chassis current path, cable-side routing and regulator noise
Changing one TVS value without reviewing the full return path
Alternate MagJack fails
Cross-reference mismatch
Turns ratio, OCL, center taps, pinout, isolation and PHY reference design
Approving replacement from footprint and datasheet headline only
BOARD-LEVEL VALIDATION

Validate the Ethernet Port from Schematic Review to Production Lot

The exact test plan depends on speed, PHY, end-product standards and deployment environment, but every motherboard benefits from separating bring-up, electrical, EMC, thermal and manufacturing checks.

Schematic / Bring-Up

PHY straps, reset, clocks, MDIO/MDC, MAC mode, controller configuration, power rails, pin mapping and auto-negotiation behavior.

Goal: deterministic initialization and expected link modes

Signal / Magnetics

Review MDI impedance, OCL, insertion/return loss, crosstalk and common-mode behavior using the PHY and Ethernet-rate requirements.

Goal: sufficient physical-layer margin

EMC / Protection

Validate emissions/immunity, ESD/EFT/surge targets, chassis current paths, shield termination and protection behavior on the finished board/system.

Goal: system-level compliance and robustness

Thermal / Production

Run hot/cold link tests, sustained traffic, port-population stress and lot-level checks that can detect assembly or component variation.

Goal: repeatable production performance
OEM DESIGN INPUT

What to Send LINK-PP for PHY-Matched RJ45 or Magnetics Selection

A useful RFQ contains the host and physical-layer context. “Need a Gigabit RJ45” leaves too much room for pin, electrical and mechanical mismatch.

Host / PHY

  • CPU / SoC / Ethernet controller
  • PHY vendor and exact model
  • MAC-to-PHY mode
  • Ethernet speed(s)
  • Reference schematic or magnetics BOM

Port / Mechanical

  • Integrated or discrete magnetics
  • Original part number if cross-referencing
  • PCB footprint / drawing
  • Tab direction, height and LEDs
  • Shield / chassis requirements

Environment / Supply

  • Operating temperature
  • PoE requirement
  • EMC / ESD / surge targets
  • Prototype quantity / annual volume
  • Lifecycle / second-source requirement
Submit Motherboard Ethernet Requirements →
PRODUCTS & ENGINEERING RESOURCES

LINK-PP Components for Board-Level Ethernet Connectivity

Start with the PHY, speed and mechanics, then choose the product family. A family page narrows the search; the exact part still requires electrical and environmental qualification.

COPPER PORT

Integrated RJ45 Connectors

RJ45 interfaces with integrated Ethernet magnetics for compact board-edge designs. Options vary by rate, LEDs, shield, orientation, temperature and PoE capability.

DISCRETE MAGNETICS

LAN Transformers

Discrete transformer options for designs that need independent magnetic and connector placement around the PHY and enclosure.

MECHANICAL I/O

Modular RJ45 Jacks

RJ45 connector options for motherboard architectures using discrete Ethernet magnetics.

PLUGGABLE I/O

SFP Cages & Connectors

Board-level SFP host hardware for fiber-capable embedded and industrial Ethernet interfaces.

10G PLUGGABLE I/O

SFP+ Cages & Connectors

SFP+ host hardware for 10GbE pluggable interfaces where the NIC/SerDes and PCB channel support the required electrical specification.

PLUGGABLE MEDIA

Optical Transceivers

Optical modules selected around the exact host, speed, fiber, reach, temperature and compatibility requirements.

Ethernet MAC vs PHY

Review how MAC logic, PHY signaling and the physical medium divide responsibilities in an Ethernet design.

Read MAC vs PHY →

RJ45 Integrated Magnetics Design Guide

Use the detailed magnetics resource for OCL, isolation, EMI, integrated-vs-discrete decisions and RFQ checks.

Read Magnetics Guide →

SFP / QSFP Cage Architecture

Review cage, connector, shielding, mechanical and thermal considerations for pluggable host interfaces.

Read Cage Architecture →

Industrial Ethernet Parent Solution

See how embedded boards, IPCs, controllers, gateways and switches fit into the broader industrial Ethernet application layer.

Explore Industrial Ethernet →
FAQ

Embedded and Industrial Motherboard Ethernet Design Questions

Short answers to the board-level questions that most often affect PHY, magnetics, RJ45 and multi-LAN qualification.

How do I choose Ethernet magnetics for a specific PHY?

Start with the exact PHY vendor and model, then compare the reference schematic and recommended magnetic characteristics with the candidate MagJack or transformer. Check turns ratio, OCL, loss, common-mode behavior, center taps, pin assignment, isolation, temperature and any PoE requirements before approval.

Can I replace a MagJack just because the PCB footprint matches?

No. Matching footprint and pin count establish only part of form and fit. Electrical function can still differ in turns ratio, OCL, center taps, common-mode behavior, LEDs, shielding, isolation or PoE implementation. Validate the replacement against the exact PHY and motherboard.

What is the difference between RGMII routing and Ethernet MDI routing?

RGMII is a digital MAC-to-PHY interface with device-specific timing requirements. MDI is the analog Ethernet line-side connection between the PHY and magnetics/cable. They have different routing objectives, so the processor and PHY vendor layout guides should be followed separately.

Why can 1G work while 2.5G Ethernet fails on the same RJ45 port?

A link can have enough margin for 1G while the PHY mode, magnetics bandwidth, channel loss, cable quality, power integrity or auto-negotiation is insufficient for 2.5G. The entire PHY-to-cable channel must be qualified for the higher rate.

How should I plan multiple Ethernet controllers on an industrial motherboard?

Map each port back to its CPU/SoC or PCIe controller, then budget PCIe lanes, aggregate throughput, controller power, PHY heat, front-panel space and software/driver support. Multi-LAN density is a system-resource problem as well as a connector problem.

When should a motherboard use SFP/SFP+ instead of native RJ45?

Pluggable fiber can be useful when the target system needs optical media, longer reach or a fiber backbone. The motherboard must support the required host electrical interface, cage/connector, management signals, power and thermal conditions, and the selected module must match the far-end optical interface.

What information is needed for a second-source RJ45 or LAN transformer cross-reference?

Provide the original part number, PHY model, Ethernet rate, reference schematic, PCB footprint, pinout, LED/shield configuration, PoE requirement, operating temperature and qualification targets. Form-fit-function and PHY compatibility should all be checked before release.

NEXT STEP

Move from Motherboard Schematic to a Qualified Ethernet Component

Send the PHY and board context first. That makes cross-reference and new-design selection substantially more useful than starting with a generic request for “a 1G RJ45.”

FOR HARDWARE ENGINEERS

Review PHY & Magnetics Compatibility

Share the PHY, reference schematic, Ethernet rate, board constraints and EMC/environmental targets for technical review.

Contact Engineering →
FOR PROCUREMENT

Qualify a Second-Source Part

Provide the original MagJack, LAN transformer, RJ45 or cage part number with volume and lifecycle requirements.

Request Cross-Reference →
FOR OEM / INTEGRATORS

Submit the Ethernet BOM

Share the controller/PHY map, current BOM and mechanical drawing for form-fit-function and sourcing review.

Submit BOM →