EtherNet/IP, CIP and Stratix: The Rockwell Network Layer

The network is the layer plants understand least and depend on most. When it is designed well nobody thinks about it. When it is not, the symptoms appear as controller faults, HMI dropouts and motion errors, and weeks get spent debugging equipment that was never the problem.

EtherNet/IP is not Ethernet

The distinction matters and is routinely missed. EtherNet/IP is the Common Industrial Protocol running over standard Ethernet. The “IP” is Industrial Protocol, not Internet Protocol. CIP is an object model and messaging standard, maintained by ODVA rather than by Rockwell, and the same protocol runs over DeviceNet and ControlNet at the lower layers.

The practical consequence: moving a plant from ControlNet or DeviceNet to EtherNet/IP changes the media, the hardware and the addressing, but the messaging model the controller uses is recognisably the same. That is why these migrations are more predictable than a controller platform migration, and why they are still routinely under-scoped on the physical side.

Implicit and explicit messaging

Two traffic types share the wire and behave completely differently.

Implicit messaging, also called I/O or connected messaging, is cyclic. A connection is established once with an agreed Requested Packet Interval, and data flows on that schedule with no request per packet. This is how controllers talk to I/O and drives. It is deterministic and it is sensitive to interruption.

Explicit messaging is request and response, used for configuration, diagnostics and MSG instructions between controllers. It is tolerant of delay.

Where plants get hurt is loading a network carrying implicit I/O traffic with unmanaged explicit traffic, broadcast storms or, most commonly, multicast traffic that an unmanaged switch floods to every port. Implicit connections start timing out, the controller logs I/O faults, and the investigation goes to the I/O module.

Unmanaged switches are the most common root cause we find

An unmanaged switch cannot do IGMP snooping, so it treats multicast as broadcast and floods it everywhere. It offers no diagnostics, no port statistics, no VLAN separation and no way to see what is happening. On a bench it is fine. On a production network it converts a small problem into an intermittent, plant-wide one that nobody can see.

The failure signature is characteristic: intermittent I/O connection timeouts, no pattern, worse when more devices are added, and every individual device tests fine.

Stratix switches

Stratix is Rockwell’s industrial switch line, built on Cisco hardware and IOS, with a Rockwell configuration layer that integrates with Studio 5000 and FactoryTalk.

Model	Position
Stratix 2000	Unmanaged. Appropriate only where a managed switch genuinely is not needed
Stratix 5700 / 5800	Managed layer 2, the mainstream plant-floor choice. 5800 is the current generation
Stratix 5400 / 5410	Managed, higher port count and layer 3 capability for distribution
Stratix 8000 / 8300	Earlier managed generations, widely installed

The genuine argument for Stratix is not switching performance, which is Cisco’s. It is that the switch appears in the Logix project as a device with diagnostics the controls team can see, rather than as a black box owned by IT. The genuine argument against is cost and that a competently configured industrial switch from another vendor does the same job. We say which is right for a given plant based on who will actually administer it.

The legacy networks

DH+, Remote I/O, DeviceNet and ControlNet still carry production in a lot of plants.

• They work. There is no urgency argument based on function
• The urgency is spares and skills. Media, taps and scanner modules are increasingly hard to source, and the people who can commission a ControlNet segment are retiring
• Migration is usually bundled, done alongside a controller or drive project rather than as a standalone network project, because that is when the machine is already down

What we do here

• Map the physical and logical network as it actually is, including what nobody documented
• Diagnose intermittent faults to their real cause instead of replacing suspected I/O
• Design segmentation that reflects how the plant runs, not an idealised architecture
• Specify managed switching and configure it properly, including IGMP and VLAN design
• Validate performance under production load rather than on a quiet network
• Plan legacy network migration alongside the projects that already require downtime

Deeper

• EtherNet/IP and CIP Explained — implicit and explicit messaging, RPI, and how connection limits actually bite
• Stratix Switches and Network Segmentation — selection, IGMP, VLAN design and where segmentation belongs

Back to the Rockwell Automation hub, or across to Programmable Controllers.