PRP (Parallel Redundancy Protocol)

What PRP Is

Parallel Redundancy Protocol (IEC 62439-3) provides network redundancy for Ethernet-based protection and control systems by running two independent networks simultaneously. Every frame is sent on both LAN-A and LAN-B. The receiving device keeps the first copy and discards the duplicate using a sequence number in a Redundancy Control Trailer appended to each frame.

The defining characteristic: zero switchover time. Not fast failover. Not sub-millisecond recovery. Zero packet loss during a single network failure. The surviving LAN was already carrying identical traffic.

This distinction matters for protection applications. A network failover measured in milliseconds can still cause a GOOSE subscriber to miss a restraint signal or a trip command to arrive late. PRP eliminates the question entirely.

Why It Matters in Data Centers

Tier III/IV data centers require concurrent maintainability — the ability to perform maintenance on any single component without interrupting critical operations. This requirement extends to the protection and control network. If a switch failure or cable fault can interrupt GOOSE messaging between protective relays, the protection system’s selectivity degrades.

PRP satisfies this requirement at the network layer by design, not by recovery speed. When a LAN-A switch fails during a scheduled maintenance window, LAN-B continues carrying every protection message without interruption. No failover detection, no spanning tree reconvergence, no missed GOOSE frames.

For prime contractors, PRP affects two project phases:

• During design review: the network architecture must demonstrate that no single point of failure can interrupt protection messaging. PRP provides this demonstration structurally — auditors can verify by inspecting the dual-LAN topology.
• During commissioning: PRP validation requires disconnecting one LAN and confirming that every GOOSE subscriber, every IEC 61850 client, and every Modbus TCP poll continues operating without interruption.

How PRP Gets Implemented

A PRP deployment requires dual-attached nodes (DANPs) at each critical endpoint and two physically independent Ethernet switch planes. In practice, this means:

• Two core/distribution switches (independent chassis, independent power) forming the backbone of LAN-A and LAN-B
• Edge switches in pairs — each critical IED connects to one switch on each LAN
• Dual-homed endpoints — protective relays, automation controllers, and HMI stations with two Ethernet ports, one per LAN
• No cross-plane bridging — LAN-A and LAN-B must remain electrically and logically independent

The engineering complexity is in the details: QoS configuration ensuring protection traffic gets priority on both planes, VLAN segmentation matching the protection zone architecture, and fiber routing that keeps the two LAN paths physically separated to avoid common-mode failures.

Designing a Protection Network?

Validate Your PRP Architecture

We review your dual-LAN topology, QoS configuration, and DANP assignments against IEC 62439-3 requirements.

Book a Scoping Call Explore Our Technical Approach

Standards and Related Protocols

• IEC 62439-3 — the normative standard defining PRP and its companion protocol HSR (High-availability Seamless Redundancy)
• IEC 61850 — the application layer carried over PRP networks in protection and control systems
• IEEE 802.1Q — VLAN tagging used alongside PRP for traffic segmentation

PRP vs. RSTP: Rapid Spanning Tree Protocol (IEEE 802.1w) provides network redundancy through reconvergence after detecting a failure. Recovery takes 1-3 seconds in typical configurations. For GOOSE applications with millisecond timing requirements, RSTP’s reconvergence window creates an unacceptable gap. PRP eliminates reconvergence entirely.

Related reading: The PRP protocol wiki page covers the full technical specification including frame format, RedBox architecture, and HSR comparison. Zone-Selective Interlocking explains why the relay-to-relay signaling carried over PRP requires zero-switchover reliability.