Network Configuration Best Practices

Network Setup

Control networks fail differently from office networks. A dropped frame on a spreadsheet share is invisible; the same loss between a controller and a remote I/O rack shows up as a process trip. The recommendations below keep control traffic predictable rather than merely fast.

Addressing

• Give every controller, HMI and managed switch a static address. Never place control devices on DHCP.
• Reserve a documented address range per panel, so an added device does not collide with an existing one.
• Record every assignment in the project I/O list. An undocumented address is found again only by disconnecting things.

Segmentation

Keep the control network separate from the business network, either physically or with a VLAN per area. The purpose is to bound the traffic a single misbehaving device can generate, and to stop office broadcast storms from reaching a PLC.

• One VLAN per process area, routed deliberately rather than bridged by default.
• Allow only the protocols that are actually needed between segments.
• Where remote access is required, terminate it at a gateway that is monitored, not at the controller itself.

Physical layer

• Use industrial rated cable and connectors. Office patch leads do not survive panel vibration or temperature.
• Keep data runs clear of power cables, crossing at right angles where they must meet.
• Label both ends of every run. An unlabelled cable is a fault that takes hours instead of minutes.

Before handover

Record the final addressing, VLAN layout and switch port assignments in the project documentation, and confirm the network diagram matches what was actually installed. Discrepancies found later are almost always resolved in favour of the installation, not the drawing.