SCALANCE X204-2 SNMP MIB Download and OID Reference

Overview

The SCALANCE X204-2 is a managed industrial Ethernet switch in the SCALANCE X-200 family from Siemens, typically ordered under MLFB 6GK5204-2BB10-2AA3 or related variants. SNMP-based network management of the switch requires loading the correct Private-MIB into the management station so the vendor-specific object identifiers (OIDs) under the Siemens enterprise OID 1.3.6.1.4.1.4196 are translated into readable symbolic names and trap variable bindings are decoded. The SCALANCE X-200 family uses the enterprise subtree 4196.1.1.5 for standard managed switches, while SCALANCE X-200IRT occupies a parallel subtree for isochronous real-time variants used with PROFINET IRT.

This reference documents three MIB acquisition paths: download from the Siemens Industry Online Support portal (article 22015045), retrieval directly from the device Web-Based Management (WBM) under Information > Save & Load HTTP, and integration into common SNMP managers such as PRTG, Zabbix, Nagios, Net-SNMP, and iReasoning MIB Browser.

Prerequisites

• SCALANCE X204-2 with X-200 family firmware V3.x or later, confirmed via WBM Information > Version.
• Web browser with HTTP/HTTPS access to the switch management IP (default 192.168.0.1 if not configured).
• Admin credentials for WBM (default user admin, password configurable on first login).
• TFTP/FTP/SFTP server reachable for pushing the MIB to a central SNMP manager, or local filesystem access for desktop browsers.
• Optional: MIB browser (iReasoning MIB Browser, MG-SOFT MIB Explorer, Net-SNMP snmptranslate).

Acquisition Path 1: Siemens Industry Online Support

The official version-controlled source for the Private-MIB is the Siemens Industry Online Support entry titled "Private-MIBs: SCALANCE X, SCALANCE W and SNMP OPC Profile", available at Siemens support article 22015045.

1. Open the support entry in a browser and scroll to the Further Information / content download section.
2. Download SN-SCALANCEX200-PRIV-MIB.mib (79 KB) for SCALANCE X204-2. Save to a path without spaces to avoid MIB compiler issues on Windows.
3. Verify file integrity by opening in a text editor and confirming the header line SN-SCALANCEX200-PRIV-MIB DEFINITIONS ::= BEGIN.
4. Confirm the LAST-UPDATED field reads 200811240000Z matching V1.0.9 dated 24/11/2008.

Note that the MIB has not been revised since 24/11/2008. Siemens continues to ship the same revision for X-200 family switches because the OID tree under 4196.1.1.5 is stable across firmware releases. Newer functionality in firmware V4.x is exposed through standard MIB-II, LLDP-MIB, and PROFINET MIBs rather than additions to the private enterprise tree.

Acquisition Path 2: WBM Save & Load HTTP

The Private-MIB can also be retrieved directly from the running device. This method is preferred when the management station is air-gapped from the Internet, or when verifying that the OID tree embedded on the device matches the support portal file.

1. Open the WBM by navigating to https://<switch-ip> (or http:// if TLS is disabled).
2. Log in with admin credentials.
3. Navigate to Information > Save & Load HTTP.
4. Locate the entry labeled MIB or Private-MIB in the file table.
5. Click Save to download the MIB file from the device file system to your local workstation.

The MIB served from the device is byte-identical to the V1.0.9 release on the Siemens support portal because the file is stored in flash and not regenerated at runtime.

OID Structure and snX200FaultValue Mapping

The SCALANCE X-200 Private-MIB defines the following key subtrees under the Siemens enterprise OID 1.3.6.1.4.1.4196:

The OID snX200FaultValue at 1.3.6.1.4.1.4196.1.1.5.2.100.2.1.4 is a per-fault-row Integer32 that returns the current fault state for the indexed fault entry. The SCALANCE X204-2 implements the same OID as the SCALANCE X200 base model because both devices share the X-200 firmware branch and the same MIB definition. If you observe noSuchObject responses on this OID, validate each of the following:

1. Confirm the device is actually an X-200 family switch (X204, X206, X208, X212, X216, X224, X204-2) and not an X-200IRT variant. X-200IRT uses subtree 1.3.6.1.4.1.4196.1.1.7.
2. Load SN-SCALANCEX200-PRIV-MIB.mib into your SNMP manager before walking the enterprise tree. The manager cannot resolve snX200FaultValue symbolically without the MIB loaded, and without resolution many managers will refuse to issue the GET request.
3. Use the correct community string (default public) or SNMPv3 credentials with an MIB view that includes the 4196 subtree.
4. Verify that the SNMP agent is enabled in WBM under Layer 3 > SNMP > General and that the management station IP is permitted.

Loading the MIB into Common SNMP Managers

PRTG Network Monitor

1. Copy the .mib file into %programfiles%\Paessler\PRTG Network Monitor\MIB\.
2. Restart the PRTG core service so the MIB compiler rebuilds the library.
3. Add a new SNMP Library sensor targeting the SCALANCE X204-2 IP address.
4. Browse the OID tree under 4196.1.1.5; snX200FaultValue resolves by symbolic name.

iReasoning MIB Browser

1. File > Load MIBs > select SN-SCALANCEX200-PRIV-MIB.mib.
2. Set SNMP credentials (v1/v2c community or v3 user) and target IP.
3. Use Tools > Walk to enumerate the 4196.1.1.5 subtree and confirm all fault objects resolve.

Net-SNMP (Linux CLI)

# Copy MIB to the Net-SNMP search path
sudo cp SN-SCALANCEX200-PRIV-MIB.mib /usr/share/snmp/mibs/

# Verify MIB parses cleanly
snmptranslate -m +SN-SCALANCEX200-PRIV-MIB -Tp 2>&1 | head

# Resolve symbolic name to dotted OID
snmptranslate -m +SN-SCALANCEX200-PRIV-MIB snX200FaultValue.0

# Walk the entire fault subtree
snmpwalk -v2c -c public 192.168.1.10 1.3.6.1.4.1.4196.1.1.5.2.100

Verification

Confirm successful MIB deployment with the following checks:

1. Symbolic resolution: Query the symbolic name snX200FaultValue from the manager. If it resolves to the dotted OID 1.3.6.1.4.1.4196.1.1.5.2.100.2.1.4, the MIB is loaded correctly.
2. GET test: Perform an SNMP GET on 1.3.6.1.4.1.4196.1.1.5.2.100.2.1.4.1 (index 1). Expected return is an Integer32 corresponding to the first fault row state.
3. WALK test: Run an SNMP WALK on 1.3.6.1.4.1.4196.1.1.5. The manager should return all objects defined in the MIB without noSuchObject or noSuchInstance errors.
4. Trap test: From WBM under Layer 3 > SNMP > Trap Configuration, force a test trap transmission if supported, then verify it arrives at the manager with decoded variable bindings matching the MIB definitions.
5. Poll timing: Verify that polling interval does not exceed the 30-second CPU budget per poll cycle recommended for X-200 firmware.

Troubleshooting Matrix

Related OIDs and Cross-References

For deeper diagnostics on the X204-2, additional OIDs from the same Private-MIB are commonly polled:

• snX200SysName (1.3.6.1.4.1.4196.1.1.5.1.1.0) - System name, returns DisplayString.
• snX200SysLocation (1.3.6.1.4.1.4196.1.1.5.1.2.0) - System location, returns DisplayString.
• snX200SysContact (1.3.6.1.4.1.4196.1.1.5.1.3.0) - System contact, returns DisplayString.
• snX200FaultIndex (1.3.6.1.4.1.4196.1.1.5.2.100.2.1.1) - Fault table row index, Integer32.
• snX200FaultDescr (1.3.6.1.4.1.4196.1.1.5.2.100.2.1.3) - Fault description, DisplayString.
• snX200FaultSeverity (1.3.6.1.4.1.4196.1.1.5.2.100.2.1.5) - Fault severity enumeration.

Cross-reference these against standard IF-MIB port counters (ifInOctets, ifOutErrors, ifOperStatus) under 1.3.6.1.2.1.2.2.1 and LLDP-MIB remote system data under 1.0.8802.1.1.2 for comprehensive link and topology monitoring.

Field Notes and Engineering Caveats

IRT vs non-IRT distinction: If you mistakenly load SN-SCALANCEX200IRT-PRIV-MIB.mib on an X204-2, all queries under 4196.1.1.5 will return noSuchObject because the IRT variant uses a different enterprise subtree (4196.1.1.7). Always confirm the device family (X-200 vs X-200IRT) by checking the MLFB on the device label before MIB selection.

Customized firmware: OEM partners and rebranded Siemens products may ship modified firmware with extended OID trees not present in the public MIB. In those cases, only the WBM extraction method under Save & Load HTTP will produce a complete MIB for monitoring. Compare SHA-256 hashes between portal and device-served files to detect OEM customizations.

SNMP polling frequency: Polling the snX200FaultTable more frequently than once per 30 seconds on the X204-2 is unnecessary and consumes CPU budget on the switch's embedded agent. Recommended polling intervals: 60 seconds for fault table objects, 300 seconds for system identification objects (snX200SysName, snX200SysLocation, snX200SysContact), and 10 seconds for IF-MIB port counters when traffic analytics is required.

Community string security: The default community public permits read-only access to the entire enterprise subtree. For production deployments, configure a write-protected community string under WBM Layer 3 > SNMP > Communities and restrict source IPs via ACL.

Operational Checklist

1. Identify X204-2 MLFB on the device label and confirm X-200 (non-IRT) family.
2. Download SN-SCALANCEX200-PRIV-MIB.mib from Siemens support article 22015045.
3. Optionally cross-verify by retrieving the MIB from the device WBM under Information > Save & Load HTTP and comparing SHA-256 hashes.
4. Load the MIB into the SNMP manager and verify snmptranslate snX200FaultValue resolves to 1.3.6.1.4.1.4196.1.1.5.2.100.2.1.4.
5. Configure SNMP community or v3 user in WBM and on the manager.
6. Walk 1.3.6.1.4.1.4196.1.1.5 and validate returned objects match expected fault and system data.
7. Set polling intervals to 60s for fault objects, 300s for system objects.

FAQ