Picture a factory floor with a ring of industrial Ethernet switches linking PLCs, remote I/O, HMIs and drives. What happens if one Ethernet link in the ring fails? Without redundancy, part of the network may lose communication. Redundancy protocols manage alternate paths so connectivity can continue after certain failures. Two common options are RSTP (Rapid Spanning Tree Protocol) and MRP (Media Redundancy Protocol). This guide explains RSTP vs MRP, how each works, and how to choose.
What Is the Difference Between RSTP and MRP?
RSTP is a general Ethernet Layer 2 protocol designed to prevent loops and provide path redundancy, while MRP is an industrial ring redundancy protocol standardised under IEC 62439-2.
Both can keep an Ethernet ring usable after a link failure. They differ in operating model, typical environment, and device support.
What Is RSTP?
Rapid Spanning Tree Protocol (RSTP) is defined in IEEE 802.1w. It prevents Layer 2 loops while allowing redundant physical paths.
Consider four switches: A → B → C → D → A. Wired as a physical ring, Ethernet frames could circulate endlessly. RSTP prevents this by having switches exchange information, elect a root bridge, and assign port roles. Some ports forward traffic, and some are blocked, which produces a loop-free logical topology.
When the active path fails, RSTP recalculates and can move a previously blocked port into forwarding. RSTP is not limited to rings or to industrial use. It works in general Ethernet networks, including tree and mixed topologies.
What Is MRP?
Media Redundancy Protocol (MRP) is a ring redundancy protocol for industrial Ethernet, standardised in IEC 62439-2.
In an MRP ring, one device acts as the MRP Manager and the others are MRP Clients. The Manager monitors the ring and keeps one path logically open for a loop-free topology. If a link fails, the Manager detects it and opens the alternate path so traffic can flow the other way around the ring.
MRP is designed around ring topologies. Not every industrial Ethernet device supports it, so always verify support on the actual hardware.
How RSTP and MRP Work
These are simplified conceptual diagrams, not exact protocol behaviour.
RSTP: redundant physical path → topology calculation → one path logically blocked → link failure → alternate path becomes active
Switch A → Switch B → Switch C
↖───────────────↙
One redundant path logically blockedMRP: industrial ring → MRP Manager/Clients → ring monitoring → link failure → alternate path opened
Switch A → Switch B → Switch C → Switch D
↑───────────────────────↓After a link failure, the ring remains available through the alternate direction. In both cases, the physical ring exists at all times. The protocol creates the logical, loop-free behaviour on top of it.
RSTP vs MRP: Key Differences
| Feature | RSTP | MRP |
|---|---|---|
| Full Name | Rapid Spanning Tree Protocol | Media Redundancy Protocol |
| Standard | IEEE 802.1w | IEC 62439-2 |
| Primary Purpose | Layer 2 loop prevention and redundancy | Industrial ring redundancy |
| Typical Network | General Ethernet and industrial networks | Industrial Ethernet rings |
| Ring Support | Yes | Yes |
| Network Architecture | More general | Ring-focused |
| Configuration Model | Spanning-tree roles/topology | MRP Manager/Client |
| Industrial Association | Broad | Commonly associated with industrial Ethernet/PROFINET |
| Equipment Support | Depends on device | Depends on device |
In plain English: RSTP is a flexible, general-purpose tool that handles rings, trees, and mixed layouts. MRP is purpose-built for ring designs, with a simpler role model (one Manager, the rest Clients). Neither is universally faster or more reliable. Results depend on the implementation and network conditions. MRP is not simply “a faster RSTP.”
RSTP vs MRP Recovery and Network Behaviour
Recovery time is not a fixed number for either protocol. It depends on:
- The protocol and its configuration
- Network topology and number of devices
- Switch implementation
- Network traffic
- The type of failure
Avoid assuming a universal figure. Check the switch vendor’s documented specifications, and compare them against your application’s tolerance for interruption. If you see numbers quoted, confirm they come from a documented implementation or standard, and that the conditions match your network.
MRP and PROFINET
MRP is commonly encountered in PROFINET networks that use ring topologies. A typical design uses MRP-capable switches or devices, with one acting as MRP Manager and the rest as Clients. This adds resilience against certain link failures.
PROFINET supports several topologies, including line, star, tree, and ring. MRP becomes relevant when you choose a ring redundancy architecture. Not every PROFINET network requires MRP, and it is not the only redundancy mechanism available.
When Should You Use RSTP?
RSTP may fit when:
- You have mixed Ethernet environments.
- You need standards-based Layer 2 redundancy.
- The network spans IT and OT segments.
- Many switches are interconnected in non-ring layouts.
- Installed equipment already supports RSTP.
The decision should follow network architecture and equipment compatibility.
When Should You Use MRP?
MRP may fit when:
- You are building an industrial Ethernet ring
- A PROFINET environment supports MRP
- An automation system requires ring redundancy
- The network is designed around an industrial ring architecture
Select MRP when the relevant devices support it, and it suits the intended architecture.
How to Choose Between RSTP and MRP
Use this checklist:
- Industrial protocol: Which protocol does the network use?
- Topology: Is it a ring, tree, or mixed layout?
- Switch support: Do the switches support RSTP, MRP, or both?
- Controller/device compatibility: Does the automation system support your choice?
- Recovery requirements: How fast must communication recover?
- Network size: How many switches and nodes are involved?
- Management: How will redundancy be configured and monitored?
- Vendor/standard requirements: Does the project specify a mechanism?
Choose the redundancy mechanism based on the actual network architecture and application requirements, not simply because one protocol has a more industrial-sounding name.
Common Mistakes When Designing an Industrial Ring
- Building a physical ring without configuring redundancy correctly.
- Mixing incompatible redundancy protocols.
- Assuming every switch supports MRP.
- Skipping switch configuration.
- Not verifying recovery requirements.
- Creating unintended Layer 2 loops.
- Leaving the network undocumented.
- Running redundant paths without monitoring them
Remember that redundancy protects against certain network failures, not every failure mode. It does not eliminate all downtime.
Frequently Asked Questions
What is the difference between RSTP and MRP?
RSTP is a general Layer 2 loop-prevention and redundancy protocol (IEEE 802.1w). MRP is an industrial ring redundancy protocol (IEC 62439-2).
Is MRP faster than RSTP?
Not universally. Recovery depends on implementation, topology, configuration, and network size. Check vendor specifications for your devices.
Can MRP and RSTP be used in the same network?
Sometimes, in separate segments or with careful design, but compatibility depends on the equipment. Avoid mixing them on the same ring without verified support.
Is MRP required for PROFINET?
No. PROFINET supports multiple topologies, and MRP is relevant only when a ring redundancy design is used.
Which switches support MRP?
Support varies by model. Verify it in the datasheet or manual of each managed industrial Ethernet switch.
What is the purpose of ring redundancy in industrial Ethernet?
It provides an alternate path so communication can continue after certain link failures, improving network availability.
Conclusion
RSTP is a general Layer 2 spanning-tree redundancy mechanism. MRP is an industrial ring redundancy protocol standardised under IEC 62439-2. Both provide redundancy, but their operating models and contexts differ. Choose based on topology, industrial protocol, device support, and recovery requirements. When selecting managed industrial Ethernet switches, Comxus can help you match hardware to the redundancy technology your network needs.
Read Also: What Is IEEE 802.1Qbv? A Simple Guide to Time-Aware Shaper in TSN
Read Also: Multi-Vendor TSN Interoperability in 2026: What the Latest Test Results Actually Reveal
