Alta Help Center

Ethernet / Fiber Speeds

Matt Baer
Matt Baer
  • Updated

Introduction

Layer 1 of the OSI model — the Physical Layer — is often overlooked because it appears simple: bits moving across wires or fiber. In reality, most real-world network instability, speed limitations, and unexplained connectivity issues originate here.

Understanding the following concepts helps administrators quickly identify physical-layer problems that higher-layer troubleshooting will never resolve.

Crucially, it is important to understand that the physical layer is the foundation of every network. Other layers stack on top of it. Much like a building with a poor foundation, the network will collapse if your physical layer is unstable.


What is Layer 1 (The Physical Layer)?

Layer 1 defines how electrical, optical, or radio signals physically transmit bits between devices. It includes:

  • Cabling (Cat5e, Cat6, fiber types)
  • Connectors and pinouts
  • Signal encoding
  • Voltage/light levels
  • Transceivers (PHYs)
  • Link speed negotiation
Important Note

Alta Labs strongly recommends using Cat6 or better Ethernet cabling to ensure reliable performance, improved signal integrity, and support for modern multi-gigabit networking speeds.

Unlike higher layers, Layer 1 does not understand packets, IP addresses, or protocols — only signal integrity and timing.

At this layer, devices communicate using a PHY (Physical Layer Transceiver).


Ethernet PHY Rates

A PHY rate represents the negotiated signaling speed between two Ethernet interfaces.

Common copper Ethernet PHY rates include:

StandardPHY RateCable Requirements
10BASE-T10 MbpsCat3+
100BASE-TX100 MbpsCat5
1000BASE-T1 GbpsCat5e+ (all 4 pairs required)
2.5GBASE-T2.5 GbpsCat5e+
5GBASE-T5 GbpsCat5e+ (distance dependent)
10GBASE-T10 GbpsCat6A recommended

Note on NBase-T

NBase-T refers to the intermediate multi‑gigabit Ethernet standards (primarily 2.5GBASE‑T and 5GBASE‑T) developed to deliver higher speeds over existing Cat5e cabling without requiring full 10GBASE‑T infrastructure upgrades. These standards are already represented in the table above but are often collectively described as NBase‑T in vendor documentation and industry discussions.

Important Detail: Pair Usage

  • 10/100 Mbps uses 2 wire pairs
  • 1 Gbps and above requires all 4 pairs
  • Any impairment on a single pair can force fallback speeds.

This explains why links frequently drop to 100 Mbps when cabling issues exist.


Fiber PHY Rates

Fiber operates differently but follows the same PHY concept.

Common fiber PHY standards:

StandardSpeedFiber Type
1000BASE-SX1 GbpsMultimode
1000BASE-LX1 GbpsSinglemode
10GBASE-SR10 GbpsMultimode
10GBASE-LR10 GbpsSinglemode
25G/40G/100GDatacenter PHYsVarious

Fiber links rely on:

  • Optical power levels
  • Correct wavelength compatibility
  • Matching transceiver standards
  • Clean connectors

Unlike copper, fiber failures rarely downgrade speed — they typically fail entirely.


Autonegotiation: How Link Speeds Are Chosen

Autonegotiation is a Layer 1 protocol defined in IEEE 802.3 that allows two devices to agree on:

  • Supported speeds
  • Duplex mode
  • Flow control capabilities

How It Works (Simplified)

  1. Devices send Fast Link Pulses (FLPs).
  2. Each side advertises supported PHY capabilities.
  3. Both ends select the highest mutually supported mode.
  4. Link training validates signal quality.
  5. Link becomes active.

Autonegotiation is not optional in modern Ethernet — many PHY features depend on it.


Why Static PHY Rates Often Fail

Administrators sometimes force link speeds assuming it improves stability or believe they are supposed to set the speed equal to or faster than their internet connection. In modern networks, this often creates problems.

Common Failure Causes

1. Duplex Mismatch

If one side autonegotiates and the other is forced:

  • One side may fall back to half-duplex.
  • Collisions and retransmissions occur.
  • Performance collapses despite an “up” link.

2. PHY Training Requirements

Gigabit and multi-gig Ethernet require:

  • Echo cancellation
  • Crosstalk measurement
  • Adaptive equalization

These processes rely on autonegotiation signaling.

3. Incomplete Capability Advertisement

Forced speeds bypass capability exchange, preventing optimal configuration.

4. Cable Marginality

Autonegotiation may intentionally downgrade speed when signal quality is insufficient.

This is not a malfunction — it is protective behavior.

Key principle:

A reduced PHY rate is often a symptom, not the problem.

 


Why Cable Testers Can Be Misleading

Many inexpensive Ethernet testers verify only electrical continuity.

They typically check:

  • Pin 1 connects to pin 1
  • Pin 2 connects to pin 2
  • No shorts between conductors

This confirms the cable is connected — not that it is correct for Ethernet signaling.

What Basic Testers Do NOT Verify

  • Pair twisting integrity
  • Split pairs
  • Impedance consistency
  • Crosstalk performance
  • Signal return loss
  • Proper pair grouping (T568A/B accuracy)

A cable can pass continuity testing yet fail Gigabit Ethernet requirements.

Example: Split Pair Problem

If wires are electrically connected but paired incorrectly:

  • 10/100 Mbps may work
  • 1 Gbps fails or drops to 100 Mbps

Only certification-grade testers validate true Ethernet performance.


Causes of Reduced PHY Speeds

Common real-world causes include:

  • Damaged cable pairs
  • Poor punch-downs
  • Incorrect pinout termination
  • Excessive cable length
  • EMI interference
  • Low-quality patch cables
  • Failing switch ports
  • Dirty or mismatched fiber connectors
  • Unsupported SFP combinations

Always treat reduced PHY speed as a diagnostic clue.


Troubleshooting PHY Rates in the Alta Labs Ecosystem

Alta Labs provides several ways to identify Layer 1 issues directly from the controller interface.

1. Switch Panel View

From the Switch Panel:

  • Select the switch device.
  • View individual ports.
  • Each port displays negotiated link speed.

Use this to quickly identify:

  • 10/100 Mbps fallback links
  • mismatched uplinks
  • degraded endpoints

A port operating below expected speed almost always indicates a Layer 1 issue.


2. Router Panel View

From the Router Panel:

  • Inspect LAN or WAN interfaces.
  • View negotiated PHY rate per interface.

This is particularly useful for diagnosing:

  • ISP uplink limitations
  • modem/router interconnect problems
  • copper SFP negotiation issues

3. Access Point PHY Indicator (Added Early 2026)

In early 2026, Alta Labs introduced a proactive Layer 1 diagnostic feature.

If an Access Point negotiates below 1 Gbps Ethernet, the controller displays:

  • A yellow circle indicator next to the AP’s IP address.

When hovering over the indicator:

  • The currently negotiated Ethernet speed is shown.

Important Behavior

  • The indicator does not appear at 1 Gbps.
  • All AP6 and AP6-series access points have a maximum Ethernet PHY rate of 1 Gbps.
  • Therefore, the indicator highlights only degraded links.

This feature allows administrators to immediately detect cabling or port issues without opening detailed diagnostics.


Recommended Troubleshooting Workflow

  1. Check Controller PHY Rate
    • Switch or router panel
    • AP yellow indicator
  2. Confirm Expected Speed
    • Compare device capability vs negotiated rate.
  3. Replace Patch Cable
    • Fastest elimination step.
  4. Move Switch Port
    • Rule out port damage.
  5. Inspect Terminations
    • Verify T568A/B consistency.
  6. Test With Certified Cable Tester (if available)
  7. Avoid Forcing Speeds
    • Restore autonegotiation.

Key Takeaways

  • Layer 1 issues are the most common cause of unexplained network problems.
  • PHY rate reductions usually indicate physical signal problems.
  • Autonegotiation is essential for modern Ethernet reliability.
  • Basic cable testers cannot validate Ethernet performance.
  • Alta Labs controller tools make Layer 1 diagnostics visible and actionable.
  • The AP Ethernet speed indicator provides immediate detection of degraded links.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.