1. Problem Description
A ring of three SCALANCE X204-2LD managed Industrial Ethernet switches is configured with MRP Manager (Auto) on every device and Diagnostic interrupts enabled. After the configuration is downloaded from STEP 7 (TIA Portal) the following symptoms appear:
- The fault LED (F) lights up steadily on the two switches that should adopt the MRP Client role.
- The selected device that should have become the MRP Manager also reports an error in its diagnostic buffer.
- In STEP 7 Hardware Online > Diagnostics the message "Redundancy manager cannot adopt the configured role" is shown for the affected devices.
- The ring does not function as redundant: traffic is forwarded, but a break on either ring port is not signalled by a diagnostic interrupt, and the second manager candidate does not take over cleanly.
Unchecking Diagnostic interrupts in the device configuration clears the fault, but at the cost of losing the link-down / fiber-break diagnostic that the application code is depending on for alarm handling.
2. System Topology and Components
The reported topology is a single closed ring built from three identical switches:
| Position | Device | Configured Role | Physical Connection |
|---|---|---|---|
| Node 1 | SCALANCE X204-2LD (6GK5 204-2BB10-2AA3) | MRP Manager (Auto) | Fiber ring port 1 → Node 2, copper port → Node 3 |
| Node 2 | SCALANCE X204-2LD (6GK5 204-2BB10-2AA3) | MRP Manager (Auto) | Fiber ring port → Node 3, copper ring port → Node 1 |
| Node 3 | SCALANCE X204-2LD (6GK5 204-2BB10-2AA3) | MRP Manager (Auto) | Fiber ring port → Node 1, copper ring port → Node 2 |
All ring ports are members of the same VLAN. PROFINET IO is running on the same network; an S7-1500 / ET 200SP I/O Controller is connected to the ring and actively exchanges process data with distributed I/O hanging off the same SCALANCE switches.
2.1 SCALANCE X204-2LD Key Specifications
| Parameter | Value |
|---|---|
| Order number (MLFB) | 6GK5 204-2BB10-2AA3 |
| Ports | 4 × RJ-45 (10/100 Mbit/s) + 2 × LC fiber (100 Mbit/s, singlemode or multimode depending on variant) |
| Ring redundancy | MRP (IEC 62439-2), MRP Manager, MRP Client, MRP Auto-Manager |
| Configuration interfaces | STEP 7 / TIA Portal, Web Based Management (WBM), CLI (Telnet/SSH), SNMP |
| Diagnostics | Port status, link monitoring, diagnostic interrupts to PROFINET IO Controller |
| Status / Fault LEDs | Port LEDs, RM (Ring Manager) LED, F (Fault) LED, P (Power) LED |
3. Root Cause Analysis
The error "Redundancy manager cannot adopt the configured role" in combination with a steady fault LED on more than one node has, in practice, three independent contributing causes that are often present at the same time:
3.1 Cause A — STEP 7 / TIA Portal vs. Web Based Management (WBM) parameter conflict
The X-200 family allows MRP parameters to be edited from two independent sources:
- STEP 7 / TIA Portal (HW Config / device properties, layer 2 > ring redundancy). The values are written as PROFINET IO record data by the I/O Controller at startup.
- Web Based Management (WBM) on the device itself (menu Layer 2 > Ring Redundancy). WBM writes to the device's non-volatile parameter set directly.
When the I/O Controller is online, the STEP 7 record data overwrites the WBM parameter set on every restart. As long as the I/O Controller is connected, the "Parameter assignment of the redundancy is not set by STEP 7" checkbox cannot be used to release the switch from STEP 7 control. The two parameter sets can therefore be inconsistent (e.g., different ring ports, different ring ID, different MRP mode) and the device's redundancy state machine enters an undefined intermediate state. This produces the diagnostic buffer entry and the fault LED.
3.2 Cause B — "MRP Manager (Auto)" on more than one device
Per the SCALANCE X-200 Operating Instructions, in the MRP Auto-Manager / Client mode the devices negotiate among themselves to determine which one adopts the manager role. The negotiation rule is: the device with the lowest MAC address wins and becomes the MRP Manager; all other devices become MRP Clients.
If, however, one or more devices still have a residual "MRP Manager" (static) entry in WBM from a previous configuration, the negotiation aborts. Every static manager claims the role and refuses to give it up. The two losing managers then report "Redundancy manager cannot adopt the configured role" and light the fault LED because they are in manager state in their own WBM but not in the role they expected on the wire.
3.3 Cause C — Diagnostic interrupts in combination with an unstable manager election
The Diagnostic interrupts checkbox causes the switch to raise a PROFINET diagnostic alarm every time the ring state changes, every time the local ring port goes link-down, and every time the manager is (re)elected. When the role election is unresolved (Causes A and B above), interrupts are raised continuously while the state machine oscillates. The CPU sees a flood of incoming diagnostic interrupts, marks the device as faulty, and the switch itself asserts the F-LED.
Disabling Diagnostic interrupts in STEP 7 only masks the symptom; it does not fix the underlying state-machine conflict. The moment the ring has a real link event (broken fiber) no alarm reaches the PLC.
4. MRP Role Negotiation Mechanics
MRP (Media Redundancy Protocol) is defined in IEC 62439-2 and is the standard ring-redundancy mechanism used by PROFINET networks based on SCALANCE X switches. Each ring port continuously transmits MRP_Test frames. The manager blocks one of its ring ports (default behavior) and periodically sends MRP_Test frames on the other one. If a client stops receiving test frames it assumes a break and opens its blocked port.
4.1 Role selection algorithm in "MRP Manager (Auto)"
- All switches with Auto mode enabled start in Manager-Candidate state and exchange their MAC addresses via MRP_Test frames with the special Manager-Priority TLV.
- Each candidate compares its own MAC with the MACs advertised by the others.
- The candidate with the lowest MAC address transitions to the Manager state and starts blocking one ring port.
- All other candidates transition to the Client state and forward the test frames on both ring ports.
- The election is repeated whenever a manager is lost (e.g., powered off, ring broken at manager side).
If a non-Auto "MRP Manager" device is present in the same ring, the Auto-Manager behaves as a client relative to that static manager. The static manager keeps priority. Therefore: mixing static "MRP Manager" and "MRP Manager (Auto)" on different nodes of the same ring is a configuration error.
4.2 Ring parameters that must match on every node
| Parameter | Required value | Source |
|---|---|---|
| Ring ID | Identical on all ring members (default 1) | STEP 7 / WBM |
| VLAN ID of ring ports | Identical (typically VLAN 1) | STEP 7 / WBM |
| MRP mode | Exactly one device = Manager (static) or Auto; all others = Client or Auto | STEP 7 / WBM |
| Ring port 1 / Ring port 2 | Same physical port assignment per switch (e.g., port 5 and port 6 on X204-2LD) | STEP 7 / WBM |
| Test interval | Default 20 ms; do not change unless you also change it on all nodes | STEP 7 / WBM |
| Domain name (optional) | Identical when used | STEP 7 / WBM |
5. STEP 7 vs. Web Based Management — Configuration Discipline
The X-200 firmware follows a strict precedence model for layer-2 parameters:
- On startup, the device checks whether a PROFINET IO Controller is connected and whether STEP 7 record data is present.
- If STEP 7 record data is present and the option "Parameter assignment of the redundancy is not set by STEP 7" is not set, the device uses the STEP 7 values and ignores the WBM values.
- If that option is set, the device keeps the WBM values and STEP 7 cannot change them.
- As long as the I/O Controller is online, the option cannot be flipped from the WBM: the WBM page for ring redundancy is read-only and shows the values coming from STEP 7.
This is the practical cause of the symptom in the field: the operator configures the switch in WBM, then the I/O Controller comes online and pushes the STEP 7 values, which differ in the ring port assignment or the manager mode. The device tries to honor both, the role election fails, and the F-LED lights up.
6. Diagnostic Interrupts and the F-LED
The F-LED on the front panel of the X204-2LD has the following meanings, summarized from the SCALANCE X-200 operating instructions:
| F-LED | Meaning | Typical diagnostic buffer text |
|---|---|---|
| Off | No fault, device healthy | — |
| Lit, red | Signaling contact open, channel diagnostics, or redundancy fault | "Redundancy manager cannot adopt the configured role", "Ring port down", etc. |
| Flashing, red | Internal firmware error / stack fault | Various, indicates firmware reload required |
Diagnostic interrupts, when enabled, push the following events to the PROFINET IO Controller:
- Port link change (up ↔ down) on any port, including ring ports
- Ring state change (ring open, ring closed, MRP manager lost, MRP manager re-elected)
- Power supply failure (on devices that support dual 24 V inputs)
- Module / channel diagnostics (e.g., SFP diagnostics on ports with pluggable transceivers)
For the reported application, the value of Diagnostic interrupts is to raise an alarm when a fiber ring is broken before the IO Controller notices the loss of IO devices (which is in the order of several hundred milliseconds). The operator therefore wants the interrupt to remain enabled.
7. Resolution Procedure
Apply the following steps in order. They are written for STEP 7 V18 / TIA Portal V18 or later; the procedure is the same for V16 and V17, only menu labels differ slightly.
7.1 Prerequisites
- STEP 7 / TIA Portal with the SCALANCE X-200 HSP (Hardware Support Package) installed.
- PG/PC with Ethernet access to the I/O Controller subnet.
- Read/write access to the PROFINET IO configuration of the S7 project.
- Default credentials for the WBM of the X-200 (admin / admin on a factory-default device; change after first login).
7.2 Step-by-step
- Pick the manager explicitly. In the project tree, open the device properties of the switch that has the lowest MAC address (this is the one that the Auto-Manager algorithm would pick anyway). Switch from MRP Manager (Auto) to MRP Manager (static).
- Set the remaining two switches to MRP Client. Do not use Auto-Manager on them. The TIA Portal supports a wizard: Devices & Networks → select the ring → Ring redundancy → Assign roles. The wizard sets the chosen node to Manager and the others to Client.
- Assign the ring ports. On the X204-2LD the two LC fiber ports are typically ports 5 and 6. Set them as ring port 1 and ring port 2 respectively. The other four RJ-45 ports remain non-ring.
- Choose the ring ID. Leave at the default (1) unless multiple rings share the same PROFINET subnet, in which case assign a unique 16-bit ring ID per ring.
- Enable diagnostic interrupts on the MRP Manager only. On the two clients you can leave it disabled — clients do not initiate MRP state changes, so the diagnostic value is on the manager.
- Compile and download the HW Config to the I/O Controller. The STEP 7 record data is now the single source of truth.
- Reset the WBM configuration on every switch to remove any leftover static-Manager entry: WBM → System → Restart with Restore Factory Defaults, or use System → Save & Load → Set&Save to overwrite WBM with the values pushed by STEP 7.
- Power-cycle all three switches in the order manager → client 1 → client 2 so that the manager is online first and the clients see a stable manager when they boot.
7.3 Optional: explicitly release the switch from STEP 7 control
If, for operational reasons, the WBM must be the source of truth (e.g., the I/O Controller is not always online), then:
- Disconnect the I/O Controller or take the PROFINET subnet offline.
- In the WBM, open Layer 2 → Ring Redundancy and set the parameters to the desired values.
- Tick the checkbox "Parameter assignment of the redundancy is not set by STEP 7". From this point on, STEP 7 record data for ring parameters is ignored.
- Reconnect the I/O Controller. Note that the checkbox state is not visible in STEP 7 — verify on the device in WBM.
8. Verification
After the corrective download, perform the following checks:
- F-LED check: within 30 seconds of boot, the F-LED on all three switches must be off.
- RM-LED check: the manager switch must show the RM (Ring Manager) LED lit; the two clients must show the RM LED off.
- STEP 7 online diagnostics: in the project tree, right-click each switch → Online & Diagnostics → Diagnostics status. The entry "Redundancy manager cannot adopt the configured role" must be absent. The buffer may still show the historical entry from before the fix; clear the buffer (Online & Diagnostics → Diagnostic buffer → Clear) to verify that no new entry is written.
- WBM consistency check: on each device, navigate to Information → Redundancy. The role shown there must match the role configured in STEP 7 (one manager, two clients).
- Ring break test: physically disconnect one ring fiber. The two switches adjacent to the break must report link down on the affected port. The manager must raise a PROFINET diagnostic interrupt with the text "Ring redundancy: ring open". After re-connecting the fiber, the ring must close automatically and a second diagnostic interrupt "Ring redundancy: ring closed" must be raised.
- Manager failover test: power down the manager. Within the configured test interval (default 20 ms × 3 missed frames ≈ 60 ms plus recovery), one of the clients must take over as the new manager and the RM-LED must migrate accordingly. Power the original manager back up — it must re-join as a client, not reclaim the role, and no fault LED must light.
9. Best Practices for SCALANCE X-200 MRP Deployments
- One static manager per ring. Auto-Manager is convenient during commissioning but should be promoted to a static manager role before the plant is handed over to operations, so that a future reconfiguration in WBM cannot split the election.
- Single source of truth. Decide upfront whether the project (STEP 7) or the device (WBM) owns the ring parameters, and enforce it. Do not allow ad-hoc WBM edits on a running plant.
- Match ring ports to physical layer. For the X204-2LD, use the two fiber ports (ports 5 and 6) as the ring ports; the four copper ports are then available for PROFINET devices and are not affected by ring reconvergence.
- Keep the test interval at 20 ms unless the ring is unusually large (a guideline of < 50 devices and < 100 m of fiber per segment is fine for 20 ms). Larger rings may need 200 ms.
- Enable diagnostic interrupts only on the manager. This minimizes the alarm load on the I/O Controller while still capturing all relevant ring state changes.
- Document the manager. Put a label on the front panel of the switch that is the active manager. The F-LED behavior in the field will be the first thing the maintenance technician checks.
- Do not mix MRP with HRP (High-speed Redundancy Protocol) on the same ring. SCALANCE X-200 supports both, but only one should be active per ring.
10. Related Parameters and Configuration Paths
| Setting | STEP 7 / TIA Portal path | WBM path | CLI command |
|---|---|---|---|
| MRP role | Device properties → Layer 2 → Ring redundancy → Mode | Layer 2 → Ring Redundancy → Mode | ring-redundancy mode {manager|client|auto-manager} |
| Ring ports | Device properties → PROFINET interface → Port assignment → Ring port 1 / Ring port 2 | Layer 2 → Ring Redundancy → Ring port 1 / Ring port 2 | ring-redundancy port 1 P5; ring-redundancy port 2 P6 |
| Ring ID | Device properties → Layer 2 → Ring redundancy → Ring ID | Layer 2 → Ring Redundancy → Ring ID | ring-redundancy id <1-65535> |
| Test interval | Device properties → Layer 2 → Ring redundancy → Test interval | Layer 2 → Ring Redundancy → Test interval | ring-redundancy test-interval <ms> |
| Diagnostic interrupts | Device properties → PROFINET interface → Diagnostics → Diagnostic interrupts | Information → Diagnostics → Configuration | profinet-diag-alarm enable |
| Release from STEP 7 | n/a (set on device) | Layer 2 → Ring Redundancy → "Parameter assignment of the redundancy is not set by STEP 7" | ring-redundancy step7-assignment disable |
10.1 Diagnostic buffer entry reference
| Diagnostic buffer text (English) | Trigger | Cleared by |
|---|---|---|
| Redundancy manager cannot adopt the configured role | MRP manager election failed: more than one device claims the role, or ring parameters mismatch | Correct ring parameter assignment and restart |
| Ring redundancy: ring open | Manager detected a break in the ring | Ring closed (link up on both ring ports) |
| Ring redundancy: ring closed | Ring re-converged after a break | Informational; remains in buffer |
| MRP manager lost | Manager device unreachable for > 3 × test interval | New manager elected |
| Port <x> link down | Physical link change on a non-ring port | Link up on the same port |
11. Quick Diagnostic Matrix
| Symptom | Likely root cause | First check | Fix |
|---|---|---|---|
| F-LED on all three switches, "cannot adopt role" on two | STEP 7 / WBM ring parameter conflict (Cause A) | Compare WBM Layer 2 → Ring Redundancy with STEP 7 project | Reset WBM, reload from STEP 7, or set the "not set by STEP 7" option |
| F-LED on two switches, OK on the third | Static manager entry left in WBM (Cause B) | WBM ring role on each device | Set all to Client, then assign one to Manager |
| F-LED only when fiber is pulled | Diagnostic interrupt storm (Cause C) | CPU diagnostic buffer count | Limit interrupts to the manager; verify ring election is stable |
| RM-LED never lights on any device | No device is set to Manager | WBM → Information → Redundancy → Role | Set one device to static Manager |
| RM-LED toggles between two devices during operation | Flapping link, or two devices set to static Manager | Port counters for late collisions / CRC errors | Replace damaged fiber / SFP; demote one device to Client |
12. FAQ
Why does the F-LED light up on the MRP clients when "MRP Manager (Auto)" is configured on every node?
Because the Auto-Manager algorithm in the SCALANCE X-200 elects the device with the lowest MAC address as the manager and demotes all others to clients. If a residual static "MRP Manager" entry exists on one or more devices (in STEP 7 or in WBM), the election aborts and the devices that expected to be clients raise "Redundancy manager cannot adopt the configured role" in the diagnostic buffer, lighting the F-LED.
Can I keep "MRP Manager (Auto)" on all three nodes if I want redundancy?
Yes, but only if WBM and STEP 7 are fully consistent, no device carries a static Manager entry, and the I/O Controller is not allowed to push conflicting values. In practice it is safer to assign one device as static MRP Manager and the other two as MRP Client to remove any ambiguity in the election.
What does "Parameter assignment of the redundancy is not set by STEP 7" actually do?
It tells the device to ignore the ring-redundancy record data coming from the I/O Controller and to keep the values currently stored in WBM. The option is only settable in WBM, it is not visible in STEP 7, and it cannot be toggled while an I/O Controller is online. Use it when the device must keep its WBM configuration independently of the STEP 7 project.
Will disabling "Diagnostic interrupts" really hide a fiber break from the PLC?
Yes. Without diagnostic interrupts the SCALANCE X-200 will not raise a PROFINET alarm on ring state changes; the PLC only notices the failure through the loss of cyclic IO on the affected devices. The detection time grows from tens of milliseconds (alarm) to several hundred milliseconds (PROFINET watchdog). Use interrupts on at least the manager to keep the alarm path.
How can I confirm which device is currently the active MRP Manager at runtime?
On each switch, read the WBM page Information → Redundancy and look at the RM-LED: it is lit on the active manager and off on clients. From STEP 7, open Online & Diagnostics → Diagnostics status; the buffer entry "This device is the redundancy manager" identifies the active manager. The role migrates automatically after a manager failure.