Designing - Reliable - Industrial Ethernet PDF

Designing Reliable
Industrial Ethernet
Infrastructures
Industry Best Practices
Mark Wylie
November 2014
© 2014 Belden Inc. | belden.com | @BeldenInc

1956 – the US Interstate Highway “network” is born
• The Interstate System has been called the Greatest Public Works
Project in History.
• From the day President Dwight D. Eisenhower signed the Federal
Aid Highway Act of 1956, the Interstate System has been a part of
our culture—as construction projects, as transportation in our daily
lives, and as an integral part of the American way of life.
• Every citizen has been touched by it, if not directly as motorists,
then indirectly because every item we buy has been on the
Interstate System at some point.
• The infrastructure was critical to the success of the Interstate.
© 2014 Belden Inc. | belden.com | @BeldenInc 2

Pre-Interstate US Highway System - 1955

US Interstate Highway System – “Infrastructure”

Consider the Interstate infrastructure
• Segments of roads
• Connections from city to city
• Sometimes “private” or toll roads
• Controlled (secure) ingress and egress
• Provision for parallel routes through or around
• Provision for crossing rivers, mountains, valleys
• Standards of construction
• Documented maps and routes
• Established rules and norms

Structure and order from potential chaos

Structure and order from potential chaos

Building an Industrial Ethernet Infrastructure
1. Segment communications into groups (subnet)
2. Segment communications into groups (vLAN)
3. Create a network infrastructure – connecting to the Enterprise (IT)
4. Other switch requirements (PoE – Power over Ethernet)
5. Specify traffic control for performance
6. Other switch requirements (IP ratings)
7. Security
8. Redundancy
9. Environment (corrosive, industrial protocols, electrical noise, temp. extremes)
10. Cables, cordsets, connectors
11. Network Management Tools
12. Infrastructure Lifecycle Needs – the Checklist

The Application - Manufacturing
Make 1
Receiving
Dock 1
Make 2
Control Room
HMI
HMI
Engineer
WorkStation
Shipping
Line 1
Dock 2
Line 2
Line 3

Receiving Make 1
Dock 1
Make 2
“ad-hoc network,
evolved without design”
Control Room
HMI
HMI
Move toward Ethernet ?

Move toward a well designed infrastructure ?
Engineer
“islands of small networks
WorkStation
-some connected via

Controller
Shippingor PC” Line 1
PLC
Dock 2
P
Line 2
C
“fieldbuses
Line 3 - migrate to
Ethernet”

An “ad-hoc” network may work…

…but consider maintaining or expanding it…

Polling Question
Do you worry that your networks are:

• Somewhat ad hoc
• Too large to manage
• Unreliable as they continue to expand
• Unmanageable as they continue to expand
• All of the above

Tool for our use
Switch / Router List - Network Design
Project
Project Engineer
Time (corrosive,
Sync moisture) Accessory
10G 1G 10/100 PoE PoE (1588, 2x Redun USB Conformal Ether- Profi- special Catalog
Use Location /Name L2 L3 ports ports ports ports Watts SNTP) IP-67 power nets memory Coating Net/IP net requirements Model Catalog Number Accessories Numbers

Segment communications into groups
(subnets)
Best
Practice 1
Subnet: As your network grows, break a large
network into smaller ones connected by
routers or layer 3 switches Layer 3 Switch / Router
Subnet A Subnet B
Device Device
Layer 2 Layer 2
Switch Switch
Device Device
Device Device
Device Layer 2 Layer 2 Device

Switch Switch
Device Device
Device Device
Layer 2 Layer 2
Switch Switch
Device Device
Device Device

(subnets)
Best
Practice 1
Subnet A Subnet B
Device Device
Layer 2 Layer 2
Switch Switch
Device Device
Device Device
Devices on the
same subnet Layer 2 Layer 2
Device Device
easily talk Switch Switch
Device Device
Device Device
Layer 2 Layer 2
Switch Switch
Device Device
Device Device

(subnets)
Best
Practice 1
Layer 3 Switch / Router Subnet A Subnet B

• Connects subnets
• Limits data in/out of each subnet Device Device
Layer 2 Layer 2
• Provides security Switch Switch
Device Device
Rule of thumb
Device Device
80% traffic stays in subnet
20% traffic travels in/out
Devices on the Layer 2 Layer 2

Device Device
same subnet Switch Switch
easily talk Device Device
Device Device
Layer 2 Layer 2
Switch Switch
Device Device
Device Device

(subnets)
Best
Practice 1

Layer 2 Layer 2
• provides security Switch Switch
Device Device
Rule of thumb
Device Device
80% traffic stays in subnet
Devices on the Layer 2 Layer 2

Device Device
Reliability, Management,
Maintenance
One subnet can be stopped without
Device Device
affecting others Layer 2 Layer 2
Switch Switch
Device Device
Device Device

(subnets)
Best
Practice 1

Layer 2 Layer 2
• Provides security Switch Switch
Device Device
Rule of thumb
80% traffic stays in subnet Device Device
Devices on the
easily talk
Device Device
Reliability, Management,
Maintenance
One subnet can be stopped without
Device Device
affecting others Layer 2 Layer 2
Switch Switch
Device Device
Device Device
Subnets are great for isolating:
• High performance
• High bandwidth traffic (video,
motion control)

(subnets) Example 1
Receiving Make 1
Dock 1
Make 2
Control Room
HMI
HMI
Engineer
WorkStation
Shipping Line 1
Dock
Line 2
2
Line 3

(subnets)
Example 1
Receiving Make 1
Dock 1
Make 2
Control Room
HMI A – Create physical groups based on function
and location for maintenance ease and security
HMI
Devices in a physical group

(these will become SUBNETS)
Engineer
WorkStation
Shipping Line 1
Dock
Line 2
2
Line 3

(subnets) Example 1
Receiving Make 1
Dock 1
Make 2
Control Room
HMI
HMI
Engineer
WorkStation
What would you do?

Shipping Line 1 This application could be:
• 1 subnet
Dock
Line 2 • 2 subnets – process and the rest

2
• Several subnets
Line 3
For this example, we’ll do it as follows…
(subnets)
Example 1
to Enterprise
Receiving Make 1
Dock 1
Make 2
Control Room
HMI
HMI
Engineer
WorkStation
Shipping Line 1
Dock
Line 2
2
Line 3

Segment Communications into Groups
(vLANs – Virtual LANs)
Best
Practice 2
VLAN 1
VLAN: Create LOGICAL groups of devices that VLAN 2

cannot be easily physically grouped Layer 3 Switch / Router
Subnet A Subnet B
Device Device
Layer 2 Layer 2
Switch Switch
Device Device
Device Device

Switch Switch
Device Device
Device Device
Layer 2 Layer 2
Switch Switch
Device Device
Device Device

Best
Practice 2
VLAN 1

Subnet A Subnet B
Device Device
Layer 2 Layer 2
Switch Switch
Device Device
Device Device

Switch Switch
Device Device
Devices in the
same VLAN can
Layer 2 Layer 2
Switch Switch
Device Device
Device Device

Best
Practice 2
VLAN 1
VLAN: Create LOGICAL groups of devices that
VLAN 2
cannot be easily physically grouped
Layer 3 Switch / Router
Subnet A Subnet B
Layer 3 Switch / Router are used
• To configure VLANs Device Device
Layer 2 Layer 2
• Limits data in/out of VLAN Switch Switch
• Provides security to VLAN Device Device
Device Device
Rule of thumb
80% traffic stays in VLAN

Switch Switch
Device Device
Devices in the
same VLAN can
Layer 2 Layer 2
Switch Switch
Device Device
Device Device

Best
Practice 2
VLAN 1
VLAN: Create LOGICAL groups of devices that
VLAN 2
Layer 3 Switch / Router are used Subnet A Subnet B

• To configure VLANs
Device Device
• Limits data in/out of VLAN Layer 2 Layer 2
• Provides security to VLAN Switch Switch
Device Device
Rule of thumb Device Device

OK for devices from Device Layer 2 Layer 2 Device

Switch Switch
multiple VLANs to connect
to a switch Device Device
Devices in the
same VLAN can
Layer 2 Layer 2
Switch Switch
Device Device
Device Device

Best
Practice 2
VLAN 1
Subnet A Subnet B
Layer 3 Switch / Router are used
• To configure VLANs Device Device
Layer 2 Layer 2
• Limits data in/out of VLAN Switch Switch
• Provides security to VLAN Device Device
Device Device
Rule of thumb
OK for devices from Device Layer 2 Layer 2 Device

Switch Switch
multiple VLANs to connect
to a switch Device Device
Devices in the
same VLAN can
Layer 2 Layer 2
Switch Switch
Device Device
VLANs are great for isolating Device Device

• High bandwidth traffic (video)
• Distributed groups of data

Example 2
Receiving Make 1
Dock 1
Make 2
Control Room B – Create logical groups based on function

(regardless of location) for maintenance ease
HMI
Devices in Logical group 1
Inventory Control
HMI
(VLAN - 1)

Quality Control
Engineer (VLAN - 2)
WorkStation
Physical Security
(VLAN - 3)
Shipping Line 1
These groups will become VLANs
Dock 2
Line 2
Line 3

Example 2
Receiving Make 1
Dock 1
Make 2

HMI
Inventory Control
HMI
(VLAN - 1)

Quality Control
Engineer (VLAN - 2)
WorkStation
Physical Security
(VLAN - 3)
Shipping Line 1
Dock 2
Line 2
Line 3

Example 2
Receiving Make 1
Dock 1
Make 2

HMI
Inventory Control
HMI
(VLAN - 1)

Quality Control
Engineer (VLAN - 2)
WorkStation
Physical Security
(VLAN - 3)
Shipping Line 1
Dock 2
Line 2
Line 3

Example 2
Receiving Make 1
Dock 1
Make 2

HMI
Inventory Control
HMI
(VLAN - 1)

Quality Control
Engineer (VLAN - 2)
WorkStation
Physical Security
(VLAN - 3)
Shipping Line 1
Dock 2
Line 2
Line 3

Example 2
to Enterprise
Receiving Make 1
Dock 1
Make 2
Control Room
HMI
HMI
Engineer
WorkStation
Shipping Line 1
Dock 2
Line 2
Line 3

Create a Network Infrastructure - Connect to Enterprise
(add routers and switches)
Best
Practice 3
Network Infrastructure: Layout switches, routers and cabling to support
control and information throughput, easy management and expansion
Backbone Switch
to Enterprise
Subnet A Subnet B
Device Device
Layer 2 Layer 2
Device Switch Switch Device
Device Device

Switch Switch
Device Device
Device Device
Layer 2 Layer 2
Device Device

Best
Practice 3
Backbone Switch
to Enterprise
Backbone Layer 3 Switch / Router

• Use very fast switches and fiber (10G or 1G typical)
• Carry traffic across industrial space to/from
Subnet A Subnet B
enterprise
Device Device
Layer 2 Layer 2
Device Device

Switch Switch
Device Device
Device Device
Layer 2 Layer 2
Device Device

Best
Practice 3
Backbone Switch
to Enterprise

Subnet A Subnet B
enterprise
Device Device
Layer 2 Layer 2
Layer 3 Switch / Router Device Device
• Connect subnets & configure VLANs
• 1G up to backbone (typical)

Switch Switch
Device Device
Device Device
Layer 2 Layer 2
Device Device

Best
Practice 3
Backbone Switch
to Enterprise

Subnet A Subnet B
enterprise
Device Device
Layer 2 Layer 2
Layer 3 Switch / Router Device Device
• Connect subnets & configure VLANs
• 1G up to backbone (typical)

Switch Switch
Device Device
Layer 2 Switches
• Connect to end devices and each other
• 100M (typical)
Device Device
Layer 2 Layer 2
Device Device

Example 3
Devices
to Enterprise Devices
Make 1 Devices
Receiving
Dock 1
Devices
Devices Devices
Devices Devices
Make 2
Devices Devices
Devices
Devices
Control Room
Devices Devices
MI
H
Devices
MI
H
Devices
Devices
Engineer
WorkStation
Devices
Devices Devices Devices
Shipping Line 1
Devices

Dock 2
Line 2
Devices
Devices Devices
Devices Devices
Devices Devices
Devices
Line 3
Devices

Example 3
Devices
Make 1 Devices
Receiving
L2
Dock 1
L2 L2
Devices
Devices Devices
Devices Devices
L2 L2 Devices
Make 2
Devices
Devices
Devices
Control Room L2 L2
Devices Devices
MI
H
Devices
MI
H
L2
Devices
Devices
Engineer
L2 WorkStation
Devices
Shipping Line 1
Devices L2 L2 L2
Devices Devices
L2 Devices
Dock 2
Line 2
Devices
L2 L2 L2
Devices Devices
Devices Devices
Devices Devices
L2 Line 3
Devices
L2 – Use layer 2 switches inside a
Devices
L2 L2 L2 subnet to connect to all of that
Devices Devices Devices subnet’s Ethernet devices. OK to
connect layer 2 switches together.

Example 3
Devices
Make 1 Devices
Receiving
L2
Dock 1
L2 L2
Devices
Devices Devices
Devices Devices
L2 Make 2 L3
L2 Devices Devices
Devices
Devices
Control Room L2 L2
Devices Devices
MI
H
Devices
MI
H
L2 L3
Devices L3 – Use layer 3 switches
Devices
Engineer (routers) to connect physical
L2 WorkStation groups (subnets) together.
Devices
Shipping Line 1
Devices L2 L2 L2
Devices Devices
L2 Devices
Dock 2
Line 2
Devices
L2 L2 L2 L3
Devices Devices
Devices Devices
Devices Devices
L2 Line 3
Devices
Devices

Example 3
BB – Create a
Devices
Make 1 Devices Communications
Receiving
Backbone using
L2
Dock 1
L2 L2 high-speed/high
Devices
Devices Devices
Devices Devices throughput
L3 switches -
L2 L2 Devices
Make 2
Devices
BB including
Devices
Devices connections to
Control Room L2 L2 Enterprise and
Devices Devices
other facilities on
MI
campus
H
Devices
MI
BB
H
L2 L3
Devices L3 – Use layer 3 switches
Devices
Engineer (routers) to connect physical
L2 WorkStation groups (subnets) together.
Devices
Shipping Line 1
Devices L2 L2 L2
Devices Devices
L2 Devices
Dock 2
Line 2
Devices
L2 L2 L2 L3 BB
Devices Devices
Devices Devices
Devices Devices
L2 Line 3
Devices
Devices

Power over Ethernet (PoE) Best
Practice 4
Power over Ethernet (PoE) : use a single industrial Ethernet cable to provide
power and Ethernet communications to devices
Traditional Approach
Line Power Power Power In
Source
Coax Cable Signal Out
Pan/Tilt/Zoom Signals – Serial Cable

Practice 4
Traditional Approach
Source
Coax Cable Signal Out
Pan/Tilt/Zoom Signals – Serial Cable
PoE Approach
• Fewer pieces/lower cost

• Mix in existing network
infrastructure
Switch
• Low voltage with isolation
With
PoE
Industrial Ethernet Cable
(4-pair copper)

Practice 4
Traditional Approach 1. Identify PoE devices you will use

(cameras, telephones, etc.)
Source and the switch it will connect to
Coax Cable Signal Out 2. Identify the power consumption (in watts) of each
device and total the power for all PoE devices wired
to one PoE switch
• Most devices are “standard” PoE – up to 13 Watts
Pan/Tilt/Zoom Signals – Serial Cable • Some devices are “PoE+” - up to 25.5 Watts.
PoE Approach
Common Examples of PoE Devices
• Fewer pieces/lower cost
• Mix in existing network
infrastructure
Switch
• Low voltage with isolation
With
PoE
Industrial Ethernet Cable
(4-pair copper)

Power over Ethernet (PoE) Example 4
Receiving
1.Make
Identify
1 each PoE device you will use
Dock 1
sw
and the switch it will connect to:
PoE Devices
Make 2
sw Switches
Control Room
HMI
HMI
sw
Engineer
WorkStation
Shipping
Line 1
Dock 2
Line 2
sw Line 3

Power over Ethernet (PoE) Example 4
Receiving
1.Make
Identify
1 each PoE device you will use
Dock 1
sw
and the switch it will connect to:
PoE Devices
Make 2
sw Switches
Control Room
HMI
2. Identify the power consumption (in watts) of each
device and total the power for all PoE devices wired
to one PoE switch
HMI
sw • Most devices are “standard” PoE – up to 13 Watts

• Some devices are “PoE+” - up to 25.5 Watts.
Engineer
WorkStation
MACH1000
MACH4000
Shipping
Line 1
MACH100
Magnum 10KTS
Dock 2
Line 2
RS 20/30/40
MS 20/30
Spider II
sw Line 3 Octopus IP67
Hirschmann and Garrettcom switches with PoE support

Polling Question
Describe your use of PoE:

• I do not use it
• I want to use it and will investigate further
• I use it today
• I have evaluated PoE and don't choose to use it

Specify Traffic Control and Time Synchronization for
Performance
Best
Practice 5
Considerations for traffic control
• Specify the proper port speeds (see Best Practice 3)
• Choose managed switches with these features:
• Establish the proper priority (QoS, Quality of Service)
• Properly handle multicast and broadcast traffic (IGMP Snooping and Querier)
• If necessary, consider “time synchronization” (as in IEEE 1588)
What is 1588?
• IEEE 1588 is designed for devices on a LAN requiring extremely precise timing accuracy
(<1 microsecond). These signals often are synchronized to a GPS or another master clock.
Typical Applications for IEEE1588
• Motion control / automation
• First-fault detection – consider PT & D applications
• Measurement and Testing
Without QoS
With QoS

Choose IP Ratings for your switches and routers Best
Practice 6
What?
• IP ratings describe a device’s protection against solids and liquids
Why?
• Ensure industrial network infrastructure devices will survive in their environments
• Ratings can enable installation without control cabinets, reducing cost and space

Choose IP Ratings for your switches and routers Best
Practice 6
If your switch
If your switch will be inside is exposed to washdown
an enclosure: or submerged in water:
IP20, NEMA 1 or 2 IP66, 67 or 68, NEMA 4,
4X, 6, or 6P
IP54 and 67 IP52
Magnum 6KM
Octopus On-Machine Ethernet Switches
Ethernet Connectors Ethernet Switches Our other switches are IP20
and Cordsets
Hirschmann and GarrettCom switches with extreme IP ratings

Polling Question
Do you specify environmental requirements carefully for switches,

cables & connectors to fit your environment?
• Yes
• No

Securing the “network”




Add network security Best
Practice 7
Add Network Security (based on risk assessment)
Configure subnets & vLANs
Subnet A Subnet B

Switch Switch
Device Device
Device Device
Layer 2 Layer 2
Switch Switch
Device Device
Device Device

Practice 7

Enable security features in
Layer 3 switches & routers
Subnet A Subnet B

Switch Switch
Device Device
Enable switch security features in

layer 2 switches
Device Device
Layer 2 Layer 2
Switch Switch
Device Device
Device Device

Practice 7
Perimeter
Protection

Subnet A Subnet B
Add firewalls to protect: Zone
• Perimeters (EAGLE30) Zone
Protection
Protection
• Zones (EAGLE Tofino)
• Remote Access (EAGLE20)
(some products are combination
security devices + routers + switches
to enable you to use fewer boxes) Layer 2 Layer 2
Device Device
Switch Switch
Device Device

layer 2 switches
Device Device
Layer 2 Layer 2
Switch Switch
Device Device
Device Device
Remote
Access
Protection
Remote
Access HERE
Practice 7
Perimeter
Protection

Subnet A Subnet B
Add firewalls to protect: Zone
• Perimeters (EAGLE30) Zone
Protection
Protection
• Zones (EAGLE Tofino)
• Remote Access (EAGLE20)
(some products are combination
security devices + routers + switches
to enable you to use fewer boxes) Layer 2 Layer 2
Device Device
Switch Switch
Device Device

layer 2 switches
Device Device
Layer 2 Layer 2
Network Security is part of Switch Switch
Defense in Depth: Device Device
• Policies & procedures
Device Device
• Physical security
Remote
• Network security Access
• Computer security Protection
Remote
• Device security Access HERE
Add Network Security
Add network security Example 7
Receiving
Make 1
L2
Dock 1
L2 L2
L2 Make 2 L3 BB
L2
Control Room L2 L2
MI
H
MI
H
L2 L3 A
BB
Enginee
L2 r
WorkSt
ation
Shipping Line 1
L2 L2 L2
L2
Dock 2
Line 2
L2 L2 L2 L3 BB
L2 Line 3
L2 L2What would you
L2 do?
• Eagle20 is a router and security device (remote access)
• Eagle30 is a router, security device & 4-port switch (perimeter security)
• Eagle Tofino is a security device only (zone security)
…here is one option
1. Enable security features in
layer 3 switches & routers
Receiving 2. Configure subnets & vLANs
Make 1
L2 3. Enable switch security features
Dock 1
L2 L2 in layer 2 switches
L2 Make 2 L3 BB
L2
Control Room L2 L2
MI
H
MI
H
L2 L3 A
BB
Enginee
L2 r
WorkSt
ation
Shipping Line 1
L2 L2 L2
L2
Dock 2
Line 2
L2 L2 L2 L3 BB
L2 Line 3
L2 L2What would you
L2 do?
• Eagle Tofino is a security device only (zone security)
…here is one option
Make 1
Dock 1
L2 Make 2 L3 BB
L2
E30
Control Room L2 L2
Protect the perimeter
MI
E30
H
Protect other remote access

MI
H
L2 L3 A
BB
Enginee
L2 r
WorkSt
ation
E20 Shipping Line 1
L2 L2 L2
L2 E30
Dock 2
Line 2
L2 L2 L2 L3 BB
L2 Line 3
L2 L2What would you
L2 do?
E20 • Eagle Tofino is a security device only (zone security)
External points of entry …here is one option
Make 1
Dock 1
T
L2 Make 2 L3 BB
L2
T E30
T Room
Control L2 L2
MI
E30
H

MI
T
H
L2 L3 A
BB
Protect Zones
Enginee (next slide for another example)
L2 r
WorkSt
T ation
E20 Shipping Line 1
L2 L2 L2
L2 T E30
Dock 2
Line 2
L2 L2 L2 T L3 BB
L2 Line 3 T
L2 L2 L2
E20
External points of entry
Make 1
Dock 1
L2 Make 2 E30
L3 BB
L2
E30
Control Room L2 L2
MI
E30
H

MI
H
L2 E30
L3 A
BB
Protect Zones
Enginee Replace Layer 3 with EAGLE 30
L2 r Alternate Solution (combination Firewall + Router + 4
WorkSt port switch)
ation
E20 Shipping Line 1
L2 L2 L2
L2 E30
Dock 2
Line 2
L2 L2 L2 L3
E30 BB
L2 Line 3
L2 L2 L2
E20
External points of entry
Polling Question
How confident are you that the industrial security you have today
will reasonably protect your company from today's threats?
• Very
• Somewhat
• Not confident
• Not sure

Let’s talk redundancy

Evaluate Redundancy Needs Best
Practice 8
Identify the largest needs for uptime – Rank and Assess Impact
Receiving to Enterprise Make 1
Dock 1
Make 2
BB
A
Control Room
C
Losing the backbone affects
MI
H
all production!
MI
H
C A
BB
Enginee
C r
WorkSt
ation
Shipping Line 1
Dock 2
Line 2
BB
A
Line 3

Practice 8
Dock 1
C
Many expensive chemicals destroyed BB
A
Make 2
if we lose communications here
Control Room
C
Losing the backbone affects
MI
H
all production!
MI
H
C A
BB
Enginee
C r Lose the control room and we lose our “eyes”
WorkSt
ation
Shipping Line 1
Dock 2
Line 2
BB
A
Line 3

Practice 8
Dock 1
C
A
Make 2
Control Room
C
Things that move (motors, pumps, robots, conveyors, etc.) Losing the backbone affects
MI
H
all production!
MI
H
C A
BB
Enginee Power Supplies

WorkSt
ation
Shipping Line 1
Dock 2
Line 2
BB
A
Line 3

Practice 8
Dock 1
C
A
Make 2
Control Room
C
Things that move (motors, pumps, robots, conveyors, etc.) Losing the backbone affects
MI
H
all production!
MI
H
C A
BB
Enginee Power Supplies

WorkSt
ation
Shipping Line 1
Electronics (overheating due to internal fans that stop running)
Dock 2
Line 2
BB
A
WhateverLinethe
3 forklift runs into!

Practice 8
Math you can do to justify an investment in redundancy
• Unplanned downtime calculator
• How long will production be impacted?
• Will product be lost?
• How much effort is needed to recover and restart your process?
• Calculate your downtime cost per minute, per hour, per day

Practice 8
Redundant • ACA for any
(backup) Hirschmann switch
Configuration

Practice 8
(backup) Hirschmann switch
Configuration
Power Supply #1
Input Power #1
Redundant • Power Supply
Power options for any
Supplies Hirschmann switch
Input Power #2
Power Supply #2

Practice 8
(backup)
Configuration Hirschmann switch
Power Supply #1
Input Power #1
Redundant • Power Supply
Power options for any
Supplies Hirschmann switch
Input Power #2
Redundant Power Supply #2

Ethernet • Ring or Tree
Network
Tree
MACH 100/1000/4000
MS 20/30
RS 20/30/40
BAT wireless
Octopus IP67
“Ring”
MACH 100/10004000
RS 20/30/40

Polling Question
What is your current situation regarding redundancy?

• Don't need it
• Have some and it’s adequate
• Have some but need more/better
• Don't have it today but need it
• Don't know so I need to investigate further

Add any additional standards, specifications, concerns Best
Practice 9
Switch / Router List ‐ Network Design
Project My Factory
Project Engineer David Adams Make Area includes corrosive
(corrosive,
gasses & extreme moisture
moisture)
10G 1G 10/100 PoE PoE 2x Redun USB Conformal Ether‐ Profi‐ special
Use Location /Name L2 L3 ports ports ports ports Watts 1588 IP‐67 power nets memory Coating Net/IP net requirements
Backbone Control Room / Ship / Receive x 3 x ring 1 x

Make Area x 3 x ring 1 x
Packaging Area x 3 x ring 1 x
Firewalls Control Room FW ? x ring 2 x EtherNet/IP and PROFINET I/O

Shipping FW ?
Receiving FW ?
Make Area 1 FW ?
Make Area 2 FW ?
Line 1 FW ?
Line 2 FW ?
Line 3 FW ?
Enterprise Edge FW x
NorthEast Edge FW x Expecting electrical noise near
SouthEast Edge FW x
some very large drives in these
L2 Make 1 East x 8 x x x x x areas
Make 1 West x 8 x x x x
Make 2 East x 16 1 7 x x x x x
Make 2 West x 6 x x x x
Line 1 East x 6 x
Line 1 Central x 10 x electrical noise?
Line 1 West x 20 x x
Line 2East x 10 x
Line 2Central x 10 x electrical noise?
Line 2 West x 20 x x
Line 3 East x 12 x
Line 3 Central x 12 x electrical noise?
Expecting huge temp extremes
Line 3 West x 20 x x in dock areas
Control Room North x 20 x ring 2 x x x
Control Room South x 20 3 21 x ring 2 x x x
Receiving West x 12 x temp extremes
Receiving NorthEast x 12 3 21 x temp extremes
Receiving SouthEast x 12 x temp extremes
Shipping North x 10 x temp extremes
Shipping South x 10 2 8 x temp extremes

Consider the cable

For Cable - Specify Copper / Fiber Requirements Best
Practice 10
Industrial Copper, ALWAYS spec:

• Bonded Pair (see “9 tests” data)
• CAT5e or higher
Nonbonded Bonded-
-Pair Pair

For Cable - Specify Jacket Requirements Best
Practice 10

For Cable - Specify Standards, Connector Type, and
Buy vs. Build
Best
Practice 10
or Washdown

Consider options for Physical Media layout Best
Practice 10
Traditional Hardwired Cable
• Point‐to‐point wiring
• Detailed electrician work
• Lowest hardware cost
• Challenges:
• Wiring in the field
• Testing
• System expansion

Practice 10
Connectorized (Pre‐built) and Distributed Cabling
• Panel to actuator cables
• Can incorporate patch panels
• Challenges:
• May still involve field wiring
• System expansion

Practice 10
Active Fieldbus Solution
• Eliminates terminal blocks with prefabricated cordsets
• Enhanced troubleshooting and diagnostics
• Lowest installation time
• Drawbacks:
• Increased cost for pre‐fabricated cables
• Increased cost for I/O blocks

Polling Question
Who specifies your physical media today?

• I do
• Someone in my group does
• A 3rd party integrator or panel shop does
• The installer does
• Our trusted vendor/distributor does

Visibility is key

Network Management tools to manage your
infrastructure
Best
Practice 11
• Configure and monitor network ‐
• All Belden products
• Many other manufacturers
• Automatically create network maps
• Benefits:
• See everything from one window
• Consistent network infrastructure
configurations easily
• Complete network design and
status at one spot

Keys to project and operations success Best
Practice 12
Industrial Networking Infrastructure Checklist
How Belden Can Help Price
Manage Manage my entire project Provide a dedicated resource to work as customer staff Quote
Design Review my design & highlight areas of risk Fax & phone consultation FREE
Assist with my design in a few key areas Fax & phone consultation FREE
Assess my situation & create my design Onsite meeting & comprehensive network design Quote
Install Preconfigure switches / routers Variable
Provide industrial installation guidelines FREE
Create custom installation instructions & drawings Recommend experienced Belden System Integrator or partner via SI
Peform the installation Recommend experienced Belden System Integrator or partner via SI
Peform security vulnerability testing Onsite testing and assesment Quote
Peform network validation Onsite testing and assesment Quote
Startup Perform startup Recommend experienced Belden System Integrator or partner via SI
Provide troubleshooting Onsite troubleshooting
Operate Dedicated onsite engineering service Quote
Maintain Stock spares We review your application & needs & provide recommendations FREE
Stock preconfigured spares Quote
Firmware Keep your hardware current Variable
Switch warranty Lifetime Warranty FREE
Industrial HiVision Service Contract Keep your software current Variable
Advanced replacement for faulty devices FREE
Remote troubleshooting Quote
Dedicated technical support contact Get help from someone that knows you and your application Quote
On‐site troubleshooting Quote
Troubleshooting procedures FREE
Troubleshooting tools Variable
Training for maintenance team Variable
Upgrade Assess planned network changes & highlight areas of risk Fax & phone consultation Variable
Onsite visit if needed Variable

Polling Question
Which of these parts of your project lifecycle would you benefit most
from outside help ... check all that apply?
• Plan
• Design
• Install
• Configure
• Startup
• Upgrade

Your infrastructure is critical for success

Your infrastructure is critical for success

Thank You!
Mark Wylie
Global Vertical Market Manager
Phone: 414-573-6720
Email: Mark.Wylie@Belden.com
Belden: www.belden.com
Belden’s Blog: www.belden.com/blog

Belden.com | @BeldenInc
© 2014 Belden

Designing - Reliable - Industrial Ethernet PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Designing - Reliable - Industrial Ethernet PDF

Uploaded by

Copyright:

Available Formats

Designing Reliable

Industry Best Practices

© 2014 Belden Inc. | belden.com | @BeldenInc

© 2014 Belden Inc. | belden.com | @BeldenInc 2

© 2014 Belden Inc. | belden.com | @BeldenInc 3

© 2014 Belden Inc. | belden.com | @BeldenInc 4

© 2014 Belden Inc. | belden.com | @BeldenInc 5

© 2014 Belden Inc. | belden.com | @BeldenInc 6

© 2014 Belden Inc. | belden.com | @BeldenInc 7

© 2014 Belden Inc. | belden.com | @BeldenInc 8

© 2014 Belden Inc. | belden.com | @BeldenInc 9

Move toward Ethernet ?

-some connected via

© 2014 Belden Inc. | belden.com | @BeldenInc 10

© 2014 Belden Inc. | belden.com | @BeldenInc 11

© 2014 Belden Inc. | belden.com | @BeldenInc 12

Do you worry that your networks are:

© 2014 Belden Inc. | belden.com | @BeldenInc 13

© 2014 Belden Inc. | belden.com | @BeldenInc 14

Device Layer 2 Layer 2 Device

© 2014 Belden Inc. | belden.com | @BeldenInc 15

© 2014 Belden Inc. | belden.com | @BeldenInc 16

Layer 3 Switch / Router Subnet A Subnet B

Devices on the Layer 2 Layer 2

© 2014 Belden Inc. | belden.com | @BeldenInc 17

Layer 3 Switch / Router Subnet A Subnet B

Devices on the Layer 2 Layer 2

© 2014 Belden Inc. | belden.com | @BeldenInc 18

Layer 3 Switch / Router Subnet A Subnet B

© 2014 Belden Inc. | belden.com | @BeldenInc 19

© 2014 Belden Inc. | belden.com | @BeldenInc 20

Devices in a physical group

© 2014 Belden Inc. | belden.com | @BeldenInc 21

What would you do?

Line 2 • 2 subnets – process and the rest

© 2014 Belden Inc. | belden.com | @BeldenInc 23

VLAN: Create LOGICAL groups of devices that VLAN 2

Device Layer 2 Layer 2 Device

© 2014 Belden Inc. | belden.com | @BeldenInc 24

VLAN: Create LOGICAL groups of devices that VLAN 2

Device Layer 2 Layer 2 Device

© 2014 Belden Inc. | belden.com | @BeldenInc 25

Device Layer 2 Layer 2 Device

© 2014 Belden Inc. | belden.com | @BeldenInc 26

Layer 3 Switch / Router are used Subnet A Subnet B

Rule of thumb Device Device

OK for devices from Device Layer 2 Layer 2 Device

© 2014 Belden Inc. | belden.com | @BeldenInc 27

OK for devices from Device Layer 2 Layer 2 Device

VLANs are great for isolating Device Device

© 2014 Belden Inc. | belden.com | @BeldenInc 28

Control Room B – Create logical groups based on function

Devices in Logical group 2

© 2014 Belden Inc. | belden.com | @BeldenInc 29

Control Room B – Create logical groups based on function

Devices in Logical group 2

© 2014 Belden Inc. | belden.com | @BeldenInc 30

Control Room B – Create logical groups based on function

Devices in Logical group 2

© 2014 Belden Inc. | belden.com | @BeldenInc 31

Control Room B – Create logical groups based on function

Devices in Logical group 2

© 2014 Belden Inc. | belden.com | @BeldenInc 32