SCALANCE X204-2 to Cisco 2960 Fiber: Wavelength & Speed Mismatch

1. Problem Overview

Engineers integrating Siemens SCALANCE X204-2 (article number 6GK5204-2BB10-2AA3) with a Cisco Catalyst WS-C2960-24TC-L across multimode fiber frequently report a complete absence of link indication even when the patch cable tests good and the same SCALANCE end connects cleanly to a second SCALANCE unit. Configuring speed and duplex on the Cisco port to 100/full does not bring up the link because two physical-layer parameters are fundamentally incompatible between the two devices: line rate and optical wavelength. The SCALANCE X204-2 is a Fast Ethernet (100 Mbit/s) fiber device transmitting at 1310 nm on BFOC (ST) connectors, while the Cisco 2960-24TC-L dual-purpose uplinks accept only 1000Base-X SFP modules (typically 1000Base-SX at 850 nm). The Catalyst 2960 platform does not support 100Base-FX SFP modules, so the optics cannot be made to talk to each other directly.

This reference walks through the affected hardware, the exact optical mismatch, the validated resolution paths, the configuration of both devices, and a complete verification procedure.

2. Affected Hardware

Source documentation: SIMATIC NET SCALANCE X-200 Configuration Manual (Siemens Support), Cisco Catalyst 2960-Plus Series Data Sheet.

3. Symptoms Observed

• Link/activity LED on SCALANCE X204-2 BFOC port remains dark.
• On the Cisco 2960, the SFP uplink status LED is off and show interfaces status reports down/down (or err-disabled if the platform sees an unsupported optics type).
• No MAC learning, no CDP/LLDP exchange across the link.
• Same BFOC patch cord works between two SCALANCE X204-2 units, proving the patch is sound and the SFP on the SCALANCE side is functional.
• Forcing speed 100 and duplex full on the Cisco port still yields no link because the SFP cage has no Fast Ethernet optics option on the 2960 platform.

4. Root Cause Analysis

There are three independent root causes stacked on top of each other. Each one alone is sufficient to prevent the link from coming up.

4.1 Line Rate Mismatch (100 vs. 1000)

The SCALANCE X204-2 fiber ports are Fast Ethernet — 100 Mbit/s, 4B/5B or 8B/10B encoded NRZ at 125 MBd. The Cisco Catalyst 2960-24TC-L dual-purpose uplinks accept Gigabit Ethernet SFPs only (1000Base-SX/LX/ZX/T). The 2960 platform does not list any 100 Mbit/s fiber SFP in its compatibility matrix; therefore the 2960 fiber port can never negotiate or force to 100Base-FX. The PHY clock recovery on each end operates at a different nominal rate, and the 802.3 Clause 37 auto-negotiation pages the two ends exchange will never resolve.

4.2 Optical Wavelength Mismatch (1310 nm vs. 850 nm)

The X204-2 (6GK5204-2BB10-2AA3) uses a Fabry–Pérot or VCSEL-driven 1310 nm transmitter specified for 50/125 µm and 62.5/125 µm multimode fiber (it is the multimode variant; the single-mode -LD version would be 6GK5204-2BD10-2AA3). The Cisco GLC-SX-MM SFP that ships in most 2960 fiber uplinks uses an 850 nm VCSEL. Even if both ends were 1000Base-X, an 850 nm SFP and a 1310 nm SFP cannot establish a working link over a passive patch because the photodetector responsivity band of the SCALANCE receiver is centered on 1310 nm and is essentially deaf at 850 nm, and vice versa.

4.3 Connector / Polarity Mismatch (BFOC vs. LC)

The X204-2 ships with BFOC (ST) bayonet connectors. Cisco SFPs use LC duplex. A patch from SCALANCE to a Cisco SFP also requires the right polarity (A-to-B crossover of TX/RX). Mixing a ST-to-LC patch cord with the wrong polarity or a defective hybrid patch is a third common failure mode. Always verify crossover polarity with a fiber tracer or a reference-known-good patch.

5. Solution Options

Three options are field-proven. Pick based on budget, latency tolerance, and the management story you need to support.

For the original 1.5 km plant-floor distance described in the field report, Option B (fiber media converter) is the right answer when fiber is mandatory, and Option A is the right answer when a short copper jumper can be run between the SCALANCE copper port and the Cisco RJ45 uplink (or a GLC-T in the SFP cage).

6. Recommended Resolution: Media Converter on the Cisco Side

The cleanest industrial implementation is to terminate the SCALANCE X204-2 BFOC fiber at a media converter located inside the control cabinet, and run a copper patch from the converter to the Catalyst 2960 RJ45 uplink (or to a GLC-T copper SFP). This isolates the wavelength issue to a single box, gives you a clean 100Base-FX ↔ 1000Base-T transition, and keeps the Cisco configuration trivial.

6.1 Bill of Materials

Reference: SCALANCE X-200 Configuration Manual, Phoenix Contact FL MC 1000 BASE-T/SC.

6.2 Topology Diagram

7. SCALANCE X204-2 Configuration

Configuration is done from the SCALANCE Web Based Management (WBM). The Primary Setup Tool (PST) only sets the management IP address; the rest of the parameters are exposed in the WBM.

7.1 Assign the Management IP (PST or WBM)

1. Connect a service PC to any of the 4 × RJ45 ports of the X204-2.
2. Set the service PC to the factory default subnet 192.168.1.x / 24 (gateway 192.168.1.1 is the SCALANCE default).
3. Open https://192.168.1.1 in the browser. The default credentials are admin / admin on a factory-fresh unit; change them at first login.
4. Navigate to System > General and set:
   • IP address: e.g. 192.168.10.1
   • Subnet mask: 255.255.255.0
   • Default gateway: 192.168.10.254
   • Management VLAN: 1 (default) or your plant VLAN, e.g. 100
5. Click Set Values and Commit.

Reference: SCALANCE X-200 Configuration Manual, section "Layer 3 > IPv4".

7.2 Fiber Port Settings

The 100Base-FX BFOC ports on the X204-2 are fixed at 100 Mbit/s full duplex with auto-negotiation disabled (FX is a forced configuration per IEEE 802.3, no auto-negotiation on the fiber side). In the WBM the port shows up under Layer 2 > Ports. Verify:

• Port state: enabled
• Speed: 100 Mbit/s (forced, not negotiable)
• Duplex: Full
• Auto-negotiation: disabled (this is normal for 100Base-FX)
• Link trap: enabled (so a break shows up as an SNMP trap)

7.3 VLAN Configuration (if used)

If the plant uses VLANs, tag the SCALANCE fiber port PVID to match the Cisco side. Example: the fiber port is member of VLAN 100 as untagged (access port), the management IP lives in VLAN 100.

1. Layer 2 > VLAN > VLAN Configuration
2. Create VLAN 100 with name PLANT_NET.
3. Assign the BFOC port to VLAN 100 as untagged (PVID 100).
4. Set the management IP under System > General into the VLAN 100 interface.

8. Cisco Catalyst 2960-24TC-L Configuration

The Cisco side requires three settings: speed/duplex hard-set, SVI (VLAN interface) for management, and the correct VLAN tagging to match the SCALANCE.

8.1 IOS Configuration Snippet

! --- Select the uplink port used for the SCALANCE link ---
! Catalyst 2960-24TC-L: dual-purpose ports are Gi1/0/25 (RJ45) and Gi1/0/25 (SFP)
! or Gi1/0/26 depending on stacking. Adjust to your actual port.

interface GigabitEthernet1/0/25
 description Uplink to SCALANCE X204-2 via media converter
 ! Force speed and duplex to match the SCALANCE-side copper output of the converter
 speed 1000
 duplex full
 ! Hard-set, do not auto-negotiate the SFP uplink (default on 2960 is auto)
 no negotiation auto
 ! Access port for VLAN 100 (match SCALANCE PVID)
 switchport mode access
 switchport access vlan 100
 spanning-tree portfast
 spanning-tree bpduguard enable
 no shutdown

! --- Management SVI in VLAN 100 ---
interface Vlan100
 ip address 192.168.10.254 255.255.255.0
 no shutdown

! --- Default route if the management VLAN is the only path ---
ip route 0.0.0.0 0.0.0.0 192.168.10.1

Reference: Catalyst 2960 Software Configuration Guide, 15.0(2)SE.

8.2 Verification Commands

show interfaces status
show interfaces GigabitEthernet1/0/25
show interfaces GigabitEthernet1/0/25 transceiver
show vlan brief
show spanning-tree interface GigabitEthernet1/0/25
show cdp neighbors GigabitEthernet1/0/25 detail

Expected results after a healthy link:

• show interfaces status: connected, 100/full or 1000/full depending on converter hand-off.
• show interfaces GigabitEthernet1/0/25 transceiver: SFP DOM data populated (Tx power, Rx power, temperature, voltage). If DOM is empty, the SFP is not seated or the SFP cage is detecting a media converter in line (in which case DOM is unavailable — that is normal for the GLC-T SFP).
• show cdp neighbors: SCALANCE appears as SCALANCE X204-2 with platform string and management IP.

9. Verification Procedure

1. Confirm the SCALANCE BFOC port LED turns solid green on the SCALANCE.
2. Confirm the media converter's Fiber Link and Copper Link LEDs both go solid green.
3. On the Cisco 2960, show interfaces status | include Gi1/0/25 reports connected.
4. Ping the SCALANCE management IP from the Cisco CLI: ping 192.168.10.1 (5 echoes, expect 5/5 success).
5. Ping the Cisco SVI from a workstation on the SCALANCE side: ping 192.168.10.254.
6. Run a sustained traffic test: from a PC on the SCALANCE side, use iperf3 -c <Cisco-SVI-IP> -t 300 -i 10 if L3 routing is in place, or use a multicast tester (e.g., mrinfo, PROFINET discovery) to confirm PROFINET IO controller visibility if applicable.
7. Disconnect one fiber strand and confirm the link drops and an SNMP trap fires — this proves the link is actually traversing the SCALANCE fiber and not a side path.

10. Troubleshooting Matrix

11. Alternative: Direct SFP Swap (Last Resort, Limited Use)

If a 100Base-FX to 1000Base media converter is not acceptable in the cabinet, the only other way to terminate the X204-2 fiber directly at a Cisco switch is to use a Cisco switch model that supports a 100 Mbit/s fiber SFP — which the 2960-24TC-L does not. Candidates would be a Catalyst 3750/3850 with a GLC-FE-100FX SFP, or a Cisco IE series industrial switch (IE-3300, IE-3400) with the matching FX SFP. None of these are drop-in replacements for the 2960-24TC-L; they are a chassis swap. Verify SFP compatibility on Cisco Transceiver Module Group (TMG) Compatibility Matrix before specifying a swap.

12. Operational Notes

• Always verify the SCALANCE variant is the multimode unit (6GK5204-2BB10-2AA3). The -LD variant (single-mode, 1310 nm, 9 µm) will not pair with a multimode SX SFP and vice versa. See the article-number breakdown in the Siemens catalog under SCALANCE X-200 Configuration Manual.
• When using a media converter, the converter itself becomes a single point of failure. Industrial-grade converters (Siemens SCALANCE X101-1, Phoenix Contact FL MC, Cisco IE extension modules) accept 24 V DC and DIN-rail mount; specify them in the BOM for the cabinet.
• Do not mix 50/125 µm OM2/OM3 with 62.5/125 µm OM1 in the same run. The 200/230 MHz·km modal bandwidth of OM1 vs. 500/2000 MHz·km of OM2/OM3 changes the modal dispersion budget and the achievable reach.
• Power budget check (informational only — confirm against SFP data sheet): 100Base-FX 1310 nm MM into 50/125 µm is typically 11 dB budget at 5 km; GLC-SX-MM 850 nm into 50/125 µm OM2 is 3.5 dB at 550 m. Once a media converter is in the link, each segment is independent and each must be checked against its own SFP/cable budget.

13. Frequently Asked Questions