Overview & Thematic Scope
Tx pre-emphasis and Rx equalization are the two primary signal-integrity tuning controls on 100G switch ports. Pre-emphasis boosts high-frequency components at the transmitter to compensate for channel loss, while Rx equalization (CTLE/DFE) restores the eye at the receiver. This troubleshooting FAQ covers when to adjust each parameter, how to configure them per vendor CLI, how to validate results with eye and FEC metrics, and how to resolve the most common link-flap and CRC errors seen in 100G deployments.

Frequently Asked Questions
- Q1: What is the difference between Tx pre-emphasis and Rx equalization on a 100G switch port?
- Tx pre-emphasis is a transmitter-side boost that pre-distorts the signal to offset channel loss, while Rx equalization is a receiver-side correction that reshapes the incoming waveform. Pre-emphasis is set on the egress port and is usually expressed in dB or as a preset (e.g., 0-6 dB in 0.5 dB steps); Rx equalization is set on the ingress port and typically offers CTLE (continuous time linear equalization) and DFE (decision feedback equalization) modes. In practice, you tune pre-emphasis first to meet the far-end receiver’s requirements, then adjust Rx equalization to open the eye at the local receiver.
- Q2: When should I adjust Tx pre-emphasis on a 100G port?
- Adjust Tx pre-emphasis when the link budget shows excessive insertion loss or when the far-end receiver reports a closed eye or rising pre-FEC BER. Typical triggers include long DAC cables (beyond 3 m passive), high-loss backplanes, or transceivers reporting a receiver power near the sensitivity floor. Start with the vendor default, then increase pre-emphasis in small steps (0.5-1 dB) while monitoring pre-FEC BER and FEC corrected codewords; stop when pre-FEC BER drops below the target (commonly 1E-5 for RS-FEC links).
- Q3: How do I configure Tx pre-emphasis and Rx equalization via CLI on 100G switch ports?
- Configuration is vendor-specific and usually applied per interface under the transceiver or phy tuning context. On many platforms the commands resemble
interface hundredgige 1/1/1followed byphy pre-emphasis tx <value>andphy equalization rx <mode|value>, thencommit. Always check the vendor’s transceiver tuning guide because some optics (e.g., QSFP28 LR4 vs. CR4) expose different register maps. After applying changes, runshow interface hundredgige 1/1/1 transceiverandshow interface ... phyto confirm the new values took effect. - Q4: How do I know if the Rx equalization setting is correct?
- The Rx equalization is correct when the receiver eye margin is positive and pre-FEC BER is stable below the FEC threshold with no uncorrectable codewords. Use DOM/diagnostic reads to check receiver power, then read the eye monitor or histogram if the platform supports it; a well-equalized link shows a clean, open eye with low jitter. If BER worsens as you increase equalization, you are over-equalizing and amplifying noise—back off to the previous step.
- Q5: Why does my 100G link flap after changing pre-emphasis or equalization settings?
- Link flap after a tuning change almost always means the new settings pushed the signal outside the receiver’s tolerance window or triggered a CDR/autoneg renegotiation. Revert to the last known-good values, then change one parameter at a time and wait 60-120 seconds for the link to stabilize. Also verify that both ends use matching FEC mode (RS-FEC vs. BASE-R) and that the transceiver’s coded BER requirements are met; mismatched FEC is a frequent cause of flap that is misattributed to equalization.
- Q6: Which transceiver types require manual pre-emphasis and equalization tuning on 100G ports?
- Manual tuning is most often required for 100G CR4 DAC/AOC links, backplane channels, and long-reach optics where host PCB loss is significant. Optics with integrated DSP or gearbox (e.g., 100G LR4, ER4, ZR) often self-adapt and need only host-side fine-tuning, while passive copper and short-reach multimode links usually run at defaults. Always consult the transceiver datasheet for recommended host tuning values and the switch vendor’s compatibility matrix before overriding defaults.
- Q7: What tools and metrics should I use to validate pre-emphasis and equalization changes?
- Validate with pre-FEC BER, FEC corrected/uncorrected codeword counters, and eye-margin or SNR readings from DOM where available. Use
show interface ... countersandshow interface ... fecto confirm errors stop accumulating, and compare before/after readings over a 15-30 minute soak. For lab work, a scope or BER tester on a tap provides the most reliable eye measurement, but production validation should rely on FEC and CRC counters plus stable link uptime. - Q8: Does adjusting pre-emphasis and equalization affect warranty or transceiver compliance?
- Changing host-side tuning parameters does not void hardware warranty, but operating transceivers outside the vendor’s recommended tuning range can cause premature optical degradation and may affect support eligibility. Keep a record of the applied values and confirm they fall within the switch and optics vendor’s published tuning guidelines. If you use third-party optics, verify the compatibility matrix explicitly supports host tuning adjustments before deploying changes at scale.
Leave a comment