Exactly 1 MRM per ring
2 MRMs cause continuous ring oscillation. Zero MRMs means no protection. Configure exactly 1 MRM.
The previous chapter covered TSN, the future of deterministic Ethernet. Today’s industrial networks rely on a proven, simpler mechanism for redundancy: MRP. This chapter explains how MRP works at the protocol level, from normal operation through detected inoperability and recovery.
STP and RSTP were designed for arbitrary mesh topologies. On a ring, RSTP converges in 1 to 2 seconds. This convergence time is too slow for industrial automation.
| Protocol | Topology | Convergence | Suitable for OT? |
|---|---|---|---|
| STP (802.1D) | Mesh | 30 to 50 s | No |
| RSTP (802.1w) | Mesh / Ring | 1 to 2 s | Marginal |
| MRP (IEC 62439-2) | Ring | < 200 ms | Yes |
A 1-second outage causes PLCs to fault. A 200 ms outage is within the watchdog tolerance of most industrial controllers. MRP (Media Redundancy Protocol), defined in IEC 62439-2, is purpose-built for ring topologies. MRP achieves sub-200 ms recovery.
An MRP ring is a closed loop of switches. Exactly 1 switch is the MRM (Media Redundancy Manager). The remaining switches are MRC (Media Redundancy Client) nodes.
Under normal operation, the MRM blocks the secondary port. The ring is logically open at that point. Traffic flows in 1 direction around the ring. The MRM sends MRP_Test frames every 10 to 20 ms to verify ring integrity. If the MRM receives the test frames back, the ring is intact.
The switches in the same ring share a Domain UUID. The ring ports on every switch belong to the MRP VLAN. These 2 settings identify the ring and carry the control frames.
The MRM sends test frames on both ports. The secondary port is blocked. Test frames arriving at the secondary port are discarded. The MRM acts only when test frames stop arriving on the primary port.
When a link becomes inoperable, the adjacent MRC sends an MRP_LinkDown frame to the MRM immediately (less than 1 ms). The MRM unblocks the secondary port and sends MRP_TopologyChange to ring members. MRP_TopologyChange triggers a MAC table flush.
When the inoperable link is repaired, the MRC sends MRP_LinkUp. The MRM blocks the secondary port again and sends another MRP_TopologyChange. Normal operation resumes.
MRP control frames travel in the MRP VLAN. Every ring port on every switch belongs to this VLAN. A ring port outside the MRP VLAN silently breaks the ring. The MRM reports the ring as open even though cables are connected.
Navigate to Switching → L2-Redundancy → MRP and configure:
| Parameter | Value |
|---|---|
| Domain UUID | Same on ring switches |
| MRP VLAN | Same on ring switches |
| Role | Manager (1 switch only) / Client (remaining switches) |
| Ring Port 1 | First ring port |
| Ring Port 2 | Second ring port |
After configuration, verify: the MRM shows Ring state: Closed.
Exactly 1 MRM per ring
2 MRMs cause continuous ring oscillation. Zero MRMs means no protection. Configure exactly 1 MRM.
Ring ports need the MRP VLAN
A ring port outside the MRP VLAN silently breaks the ring.
Same Domain UUID on ring switches
The UUID identifies the ring. Mismatched UUIDs cause switches to ignore MRP frames from each other.
This chapter explained how MRP works at the protocol level. The next chapter goes deeper: the wire format of every MRP frame type, the MRM state machine, and Python tools for parsing MRP frames and monitoring ring health in real time.