C135 PCS 7 (PCS7)
6C
6 Cielo Ciencia y Tecnología
·Publicada en C135 PCS 7 (PCS7)

How to Resolve CPU 410-5H Maintenance Faults and IP Subnet Conflicts in Redundant Plant Bus Configurations

How to Resolve CPU 410-5H Maintenance Faults and IP Subnet Conflicts in Redundant Plant Bus Configurations

On a redundant SIMATIC PCS 7 fault-tolerant automation system (CPU 410-5H / S7-400H) utilizing CP 443-1 communication processors, a yellow Maintenance Fault (MAINT LED lit) caused by network IP conflicts occurs when redundant network interfaces or redundant CPU nodes are assigned IP addresses within the same logical IP subnet on an interconnected network. In redundant fault-tolerant plant bus architectures, redundant ring segments (Ring 1 / Bus A and Ring 2 / Bus B) must reside on strictly separate IP subnets (e.g., 192.168.1.0/24 for Ring 1 and 192.168.2.0/24 for Ring 2). Correcting the IP ranges in HW Config, downloading hardware configurations, and power-cycling clears the fault.

Table of Contents

CPU 410-5H Redundancy and Maintenance LED Mechanics

The SIMATIC PCS 7 CPU 410-5H Process Automation controller incorporates advanced self-diagnostic firmware that evaluates hardware integrity, communication stack validity, and network topology. The controller features a dedicated yellow MAINT (Maintenance) LED alongside standard RUN, STOP, REDF, and EXTF indicators.

When the MAINT LED illuminates, it signals that the automation system remains fully operational (the CPU executes automation logic and maintains redundancy if configured), but a preventative maintenance condition or configuration violation has been detected.

In network installations involving redundant CPU 410-5H racks equipped with integrated PROFINET ports and auxiliary CP 443-1 Industrial Ethernet communications processors, the diagnostic buffer frequently logs:
* Event ID 16#494D: Maintenance demanded / Maintenance required
* IP address conflict or duplicate network configuration detected on Industrial Ethernet interface

Even after changing an IP address or removing backup batteries, the MAINT LED remains persistently illuminated until the underlying network topology violation is corrected and acknowledged in the system configuration.

IP Subnet Separation Rules in Fault-Tolerant Plant Bus Networks

A critical rule in Siemens fault-tolerant automation design is strict logical subnet separation across redundant network paths:

The Dual-Bus / Dual-Ring Topology

A standard fault-tolerant PCS 7 Plant Bus consists of two independent Industrial Ethernet rings (Ring 1 / Bus A and Ring 2 / Bus B) interconnected via SCALANCE X-400 or X-300 switches:
* Rack 0 Interfaces: CPU 410-5H Rack 0 onboard interface (or CP 443-1 Rack 0) connects to Ring 1.
* Rack 1 Interfaces: CPU 410-5H Rack 1 onboard interface (or CP 443-1 Rack 1) connects to Ring 2.

The IP Conflict and Multi-Homing Violation

If an engineer accidentally assigns IP addresses belonging to the same subnet to both interfaces (e.g., CPU 0 assigned 192.168.1.10/24 and CPU 1 assigned 192.168.1.20/24, or CP 0 assigned 192.168.1.11 and CP 1 assigned 192.168.1.21), while the physical switches share an inter-switch link or spanning-tree protocol:
1. The TCP/IP network stacks of both CPUs detect duplicate broadcast traffic and ARP conflicts on the shared subnet.
2. The controller identifies an illegal multi-homing loop where two redundant default gateways exist on the same subnet segment.
3. The CPU 410-5H firmware flags an IP configuration fault, asserts Maintenance Demanded, and illuminates the MAINT LED.

Step-by-Step Remediation Procedure

To eliminate the IP conflict and clear the CPU 410-5H MAINT LED:

Step 1: Designate Distinct IP Subnets for Redundant Network Rings

Establish two distinct IP address ranges with identical subnet masks:
* Ring 1 (Bus A): Subnet 192.168.1.0, Mask 255.255.255.0
* Ring 2 (Bus B): Subnet 192.168.2.0, Mask 255.255.255.0

Step 2: Configure Subnet Separation in HW Config

  1. In SIMATIC Manager Component View, open the Hardware Configuration (HW Config) for the redundant AS 410-5H station.
  2. Double-click the onboard PROFINET / Ethernet interface of CPU 410-5H in Rack 0:
    * Set IP Address to: 192.168.1.10
    * Subnet Mask: 255.255.255.0
    * Assign Subnet: Subnet_Bus_A
  3. Double-click the onboard PROFINET / Ethernet interface of CPU 410-5H in Rack 1:
    * Set IP Address to: 192.168.2.10
    * Subnet Mask: 255.255.255.0
    * Assign Subnet: Subnet_Bus_B
  4. If utilizing auxiliary CP 443-1 communication processors (e.g., 6ES7443-1EX30-0XE0):
    * Set CP in Rack 0 to: 192.168.1.11 (Subnet Subnet_Bus_A)
    * Set CP in Rack 1 to: 192.168.2.11 (Subnet Subnet_Bus_B)
  5. Save and Compile HW Config (Station -> Save and Compile).

Step 3: Update Network Routing in NetPro

  1. Open NetPro.
  2. Verify that Subnet_Bus_A and Subnet_Bus_B appear as two distinct green Industrial Ethernet networks.
  3. Verify that the S7 Fault-Tolerant Connections (S7-H-Connections) between the AS 410-5H and the OS Servers / Engineering Station span both subnets.
  4. Execute Network -> Save and Compile -> Check and compile all.

Step 4: Download Hardware Configuration and Clear Fault State

  1. In HW Config, select Target system -> Download to module.
  2. Download the updated hardware configuration to the AS 410-5H (in redundant operation, this can be executed via the redundant CPU download wizard).
  3. If the MAINT LED remains latched after download due to cached ARP tables in network switches:
    * Power-cycle the industrial Ethernet switches (SCALANCE X), or
    * Perform an orderly restart of the CPUs (switch to STOP, then RUN sequentially) to refresh the physical MAC-to-IP binding tables.

Redundant Network Configuration and Addressing Matrix

The following table illustrates the required subnet separation scheme for a redundant AS 410-5H and CP 443-1 installation:

Node / InterfaceRack / SlotIP Subnet AssignmentIP Address ExampleSubnet MaskPhysical ConnectionCPU 410-5H MasterRack 0, Slot 3Subnet Ring 1 (Bus A)192.168.1.10255.255.255.0SCALANCE Switch ACPU 410-5H StandbyRack 1, Slot 3Subnet Ring 2 (Bus B)192.168.2.10255.255.255.0SCALANCE Switch BCP 443-1 MasterRack 0, Slot 5Subnet Ring 1 (Bus A)192.168.1.11255.255.255.0SCALANCE Switch ACP 443-1 StandbyRack 1, Slot 5Subnet Ring 2 (Bus B)192.168.2.11255.255.255.0SCALANCE Switch BOS Server 1 (Dual NIC)Rack PC, NIC 1/2Ring 1 / Ring 2192.168.1.101 / 192.168.2.101255.255.255.0Switch A / Switch BOS Server 2 (Dual NIC)Rack PC, NIC 1/2Ring 1 / Ring 2192.168.1.102 / 192.168.2.102255.255.255.0Switch A / Switch B

Strict separation across different third octets prevents ARP collisions and satisfies CPU 410-5H multi-homing rules.

Verification

To verify that the maintenance fault is cleared:
1. Inspect the physical front panel of both CPU 410-5H units (Rack 0 and Rack 1).
2. Confirm that the yellow MAINT LED is completely extinguished.
3. Confirm that the green RUN LEDs are lit solid on both CPUs and the REDF (Redundancy Fault) LED is off, indicating full redundant coupling.
4. In SIMATIC Manager, open the AS 410-5H Module Information -> Diagnostic Buffer.
5. Verify that recent entries report normal synchronization and that no 'Maintenance demanded' or 'IP conflict' events appear.
6. Verify that S7-H Named Connections to the OS Servers report bidirectional data communication across both network rings.

Limitations and Operational Precautions

  • Removing backup batteries from PS 407 power supplies does not reset CPU 410-5H configuration; the CPU 410-5H stores configuration in non-volatile flash memory and does not require batteries.
  • Downloading HW Config changes to Ethernet interfaces on a running AS 410-5H must be performed using the Step 7 Redundant Download procedure to prevent tripping running plant equipment.
  • Never physically bridge cables between Switch A and Switch B unless utilizing a managed trunk or standby redundancy link configured in SCALANCE firmware.
  • Ensure all engineering stations and operator servers connecting to both rings have static IP addresses configured on separate subnets on each respective network adapter.

Engineer FAQ

Does the CPU 410-5H require backup batteries in the power supply?

No. The CPU 410-5H uses retentive FRAM/NVRAM memory for retain data and System Expansion Card (SEC) hardware licensing. Batteries in PS 407/405 are optional and only serve external RTC backup if NTP time synchronization is not used.

Why did the MAINT LED stay on after changing the IP address?

Network switches (such as SCALANCE X) cache ARP entries for up to 300 seconds, and CPU firmware retains diagnostic state until a successful communication cycle confirms zero collisions. A CPU warm restart or switch cache clear is often required.

Can I use MAC-address-based ISO Transport instead of TCP/IP to avoid IP conflicts?

Yes, CP 443-1 communication processors support ISO Transport (Layer 2 MAC addressing), which eliminates IP subnet configuration. However, onboard CPU 410-5H PROFINET ports require TCP/IP and cannot run pure ISO Transport.

Technical References

Related Articles

Related Tags

  • CPU410_5H
  • S7_400H
  • MAINT_Fault
  • Redundant_Plant_Bus
  • IP_Subnet_Conflict
6 respuestas