2VAA002993 G en S Control and IO Symphony Plus Ethernet Networking

Technical Description
Symphony Plus Control and I/O

Ethernet Networking Guide
Contents
Overview ....................................................................................................................................................... 3
Summary ................................................................................................................................................... 3
Scope ......................................................................................................................................................... 3
Networking Overview ................................................................................................................................... 3
The Network Stack .................................................................................................................................... 3
Physical Layer ........................................................................................................................................ 4
Data Link Layer ...................................................................................................................................... 4
IP Layer .................................................................................................................................................. 4
Transport Layer ..................................................................................................................................... 5
Application Layer .................................................................................................................................. 5
Putting It All Together ........................................................................................................................... 5
Additional Documentation........................................................................................................................ 5
How INFI-NET concepts and terms translate to PN800 ............................................................................ 5
Symphony Plus Ethernet Networks .............................................................................................................. 6
PN800 Plant Network................................................................................................................................ 6
SynchroNet SOE Time Synchronization Network...................................................................................... 6
Ethernet Foreign Device Interface ............................................................................................................ 7
PN800 Network Redundancy ........................................................................................................................ 7
PRP Functional Overview .......................................................................................................................... 8
PRP Device Types ...................................................................................................................................... 8
Topology Restrictions................................................................................................................................ 9
Other Network Redundancy Methods ...................................................................................................... 9
Network Security .......................................................................................................................................... 9
TCP and UDP Ports Used On PN800........................................................................................................ 11
Other Security Measures ........................................................................................................................ 12

Doc Id: 2VAA002993 Rev. G Date: 11 November 2016 Page 1 of 25
Symphony Plus Control and I/O Ethernet Networking Guide Technical Description
IP Addressing and Subnetting ..................................................................................................................... 12

Overview ................................................................................................................................................. 12
PN800 ...................................................................................................................................................... 12
Hybrid PN800/INFI-NET Systems ............................................................................................................ 12
SynchroNet.............................................................................................................................................. 13
Other Address Restrictions ..................................................................................................................... 13
Equipment Guide ........................................................................................................................................ 14
Types of Ethernet Devices ...................................................................................................................... 14
Switches .............................................................................................................................................. 14
Routers ................................................................................................................................................ 14
Managed vs. Unmanaged Switches ........................................................................................................ 14
Managed Switch Configuration Guidelines......................................................................................... 15
Additional Notes About Managed Switches ....................................................................................... 16
Network Cabling...................................................................................................................................... 16
INFI-NET – PN800 Bridge IEB800 ............................................................................................................ 16
SynchroNet Time Masters....................................................................................................................... 16
Recommended Physical Topologies............................................................................................................ 17
Single Segment........................................................................................................................................ 17
Two Segments ......................................................................................................................................... 18
Several Segments .................................................................................................................................... 19
Expanding INFI-NET ................................................................................................................................. 19
Hybrid INFI-NET/PN800 System .............................................................................................................. 20
Other Topologies..................................................................................................................................... 21
Example Installation .................................................................................................................................... 21
Remote Network Connections .................................................................................................................... 23
Revision History .......................................................................................................................................... 24

Overview
The Symphony Plus Plant Network, PN800, is a dedicated, redundant, TCP/IP Ethernet network that
carries traffic between Symphony Plus Control and I/O (S+ C&I/O) nodes, including Exception Reports,
diagnostic messages, and system time; it is analogous to INFI-NET from Symphony Harmony.
SynchroNet is a dedicated, non-redundant, TCP/IP Ethernet network for distributing highly accurate
time for the purpose of Sequence of Events monitoring; it is analogous to the SynchroLink serial bus
from Symphony Harmony.
The Ethernet Foreign Device Network is a dedicated, non-redundant IP network allowing the connection
of Modbus TCP devices to Symphony Harmony and Symphony Plus distributed control systems (using
the Harmony Gateway Software, or HGS). First added to the Symphony Harmony BRC410 bridge
controller, it is also present in Symphony Plus controllers.
Symphony Plus is not 800xA. The devices and technologies in use in S+ are different from those used in
800xA. Systems and configurations that are optimal for an 800xA-based distributed control system
(DCS) may not be optimal, or may not function at all, for a Symphony Plus-based DCS. Considering the
fact that network topology is specific to each project, and each network in a system, this document
outlines best practices, recommended topologies, and other implementation details and information.
Summary
This document is intended to guide plant engineers who are responsible for the safe and secure
implementation of S+ C&I/O networks, and the devices connected to them. These engineers should
have a basic familiarity with IP Ethernet networking technology and Symphony Harmony. It is not
intended to be a definitive guide of how to configure S+ C&I/O Ethernet networks. It is intended to
serve as a general guide to a qualified industrial network engineer.
Scope
The primary scope of this document covers how to connect and configure S+ C&I/O nodes on the
various networks. E.g., S+ C&I/O communication modules, operator console and engineering servers
and workstations on PN800; controllers and the time synch master on SynchroNet, and controllers on
the Ethernet Foreign Device network. It does not cover configuration of networks dedicated to
Symphony Plus Operations (or any other operator console) or Symphony Plus Engineering.
Networking Overview
The Network Stack

IP Ethernet networking can be considered as a stack, a group of protocols which build upon each other.
Each layer does not need to know about any of the other layers – they only need to be able to remove
any additional overhead they add to a communication packet.

Application Layer
Transport Layer
IP Layer
Data Link Layer
Physical Layer
Figure 1 The Networking Stack
Physical Layer
The physical layer defines the physical media (and its properties) which transmits the data. The media
may be copper (e.g. 100BASE-TX or 1000BASE-TX over CAT5E or CAT6 Ethernet cable) or fiber optic
cable (100BASE-FX, 100BASE-SX, 1000BASE-SX, et al over single- or multi-mode fiber optic cables).
The physical layer of all Ethernet-connected Symphony Plus Control and I/O modules is 100BASE-TX
(using CAT5E at minimum). However, connections between switches may use copper or fiber optic
cable. A minimum speed of 100Mbps is required; 1000Mbps or faster connectivity is recommended for
switch interconnects.
Data Link Layer

The Data Link Layer handles communication between two directly connected devices (e.g. two devices
connected to the same switch). This is the layer at which Ethernet devices’ MAC addresses are added to
the packet. Switches inspect the MAC address information, and only re-transmit the packet on the port
to which the destination device is connected.
IP Layer
The IP layer handles communication between nodes that may not be directly connected together on the
same layer 2 segment. As implied by the name, the IP layer adds IP addressing and subnet information
to the packet. A source module will compare its IP address and subnet mask to those of the destination,
and if they are on the same IP network, it will transmit the packet to the destination’s MAC address.
Otherwise, the source module will transmit the packet to a router (using the router’s MAC address),
which will then repeat this process until the destination node is directly connected to a router, or the
packet times out.
IP routing is currently not supported for PN800.

Transport Layer
The transport layer is responsible for sessions which span multiple messages (for example, a request and
response). Common protocols include Transmission Control Protocol (TCP) or Universal Datagram
Protocol (UDP).
Application Layer
The application layer contains the actual data the running application is trying to communicate (e.g.
process data). The protocol is defined by the individual applications. For example, INFI-NET message
data (exception reports, etc.) is contained at the application layer.
Putting It All Together

Data Data
IP Transport Transport IP
Link Application Data Link
Prefix Prefix Suffix Suffix
Prefix Suffix
Figure 2 Example Ethernet Packet
As illustrated in Figure 2 above, which provides an abstract example of an Ethernet packet, each layer of
the stack encapsulates the higher layer when being transmitted. When the packet is received, each
layer removes its encapsulation before passing the packet to the next layer up, until the application
receives just the data it is expecting, with all the wrappers removed by the lower layers.
Additional Documentation
2VAA002630 S+ Control: SPIEB800 INFI-NET to PN800 Ethernet Bridge User Manual
IEC 62439-3 International Standard, Industrial Communication Networks – High availability

automation networks
Table 1 Additional Documentation
How INFI-NET concepts and terms translate to PN800

The table below lists terms used in Symphony Harmony, and how they translate to Symphony Plus (as
used in this document). It only includes network terms/definitions relevant to this document, and is not
a definitive listing.
INFI-NET Term Symphony Plus Term

INFI-NET PN800
Loop or Ring Segment
Node/PCU Node
SynchroLink SynchroNet
Table 2 INFI-NET Concepts in PN800

Symphony Plus Ethernet Networks
PN800 Plant Network

PN800 is a dedicated, redundant IP Ethernet network that connects Symphony Plus nodes together. It is
functionally equivalent to INFI-NET loops in Symphony Harmony. PN800 must be a dedicated network,
and must not be used for any other purpose (e.g. S+ Operations Client/Server communication,
PC/network device management, etc.). It utilizes active/active redundancy to prevent failures due to
loss of communication, and to provide instantaneous failover in the event of a failure in one of the two
networks.
SynchroNet SOE Time Synchronization Network

SynchroNet is a dedicated, independent, non-redundant IP Ethernet network whose only purpose is to
distribute highly accurate time to controller nodes for the purpose of time stamping sequence of events
(SOE) data. Every Symphony Plus controller has a SynchroNet port, on which it receives time from the
local time master (e.g. a satellite clock) using Simple Network Time Protocol (SNTP). A SNTP client
running in the controller’s firmware connects to and receives time from the SNTP server. Not all
controllers have to be connected to SynchroNet; only those which need highly accurate time for SoE
tracking should be connected.
SynchroNet is not used to provide Symphony Plus system-wide time. Symphony Plus system time
mastership and distribution are managed using a proprietary protocol on PN800, similar to the one used
on INFI-NET for Symphony Harmony. However, a dedicated network interface on one (or more)
console(s) could be connected to SynchroNet. The console’s operating system can then be configured
to use the same time master as the controllers, and the console software (Symphony Plus Operations,
etc.) can then be configured to assume the system time master role, and therefore provide similar time
for Symphony Plus system time. Note that Symphony Plus system time will not be as accurate as
SynchroNet time in this scenario, only similar.
The operating system of the console PCs connected to SynchroNet can also be configured to provide
time to other PCs in the system (e.g. Symphony Plus Engineering servers and workstations). As with S+
system time, this may not be as accurate as the time when distributed on SynchroNet, only similar.
There are no special requirements for the network switches on SynchroNet. However, the number of
switches between the time master and destination nodes must be kept to a minimum to minimize
propagation delay (and therefore clock skew).
The figure below shows an example SynchroNet network. It does not show any other networks.

CTB810 CTB811
A BB F A BB F A BB F A BB F
R R R R
1 1 1 1
2 2 2 2
3 3 3 3
4 4 4 4
5 5 5 5
CTB810 CTB811
6 6 6 6
7 7 7 7
R R R R
8 8 8 8
STOP/RESET STOP/RESET STOP/RESET STOP/RESET

1 1 1 1
2 2 2 2
3 3 3 3
4 4 4 4
5 5 5 5
HN800 CW800 Symphony Plus Symphony Plus Symphony Plus Symphony Plus HN800 CW800
6 6 6 6
7 7 HC800 CP800 HC800 CP800
7 7
8 8 8 8
L+ A A L+ A A
TER800
TER800
TER800
TER800
L- L-
SA SA
HN800 CW800 Symphony Plus Symphony Plus Symphony Plus Symphony Plus HN800 CW800 SB B B SB B B
HC800 CP800 HC800 CP800
EN1 MB810 PN800 COM EN1 MB810 PN800 COM
L+ A A L+ A A
TER800
TER800
TER800
TER800
L- L-
SA SA
SB B B SB B B
Operations
Console
(optional)
(optional)
Operations
Satellite Clock SynchroNet Switch Server
Figure 3 Example SynchroNet Network
Ethernet Foreign Device Interface

All Symphony Plus controllers have a dedicated, independent, non-redundant Ethernet Foreign Device
Interface, which can be used for Modbus TCP. Symphony Plus controllers have no special requirements
for network switches on this connection. Refer to the documentation of other devices on this network
for any special requirements. Such requirements are outside the scope of this document.
The figure below shows an example HPC800 connected to an ABB AC500 PLC over Modbus TCP. It does
not show any other networks.
CTB810 CTB811
A BB F
A BB F
R R
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
STOP/RESET STOP/RESET
HN800 CW800 Symphony Plus Symphony Plus HN800 CW800
HC800 CP800
L+ A A
L-
TER800
TER800
TER800
TER800
SA
SB
B B
EN1 MB810 PN800 COM
Figure 4 Example Foreign Device Network
PN800 Network Redundancy

PN800 uses Parallel Redundancy Protocol (PRP, IEC 62439-3 Clause 4) to provide a redundant
communication network. PRP provides redundancy using two, completely independent, fault isolated
networks. The topology and hardware of the two networks must be identical.

This section is intended to provide a brief overview of PRP. Refer to IEC 62439-3 Clause 4 for the
complete PRP standard used on PN800.
PRP Functional Overview

PRP operates at the device level by transmitting effectively identical packets simultaneously on both
networks, with the destination node discarding the duplicate packet when received. This results in zero
failover time when one network fails, since both are always actively communicating. As such, referring
to the two networks as “primary” and “backup” (or using similar terms) is inaccurate. Therefore, we will
use refer to the networks as “A” and “B” (per the IEC standard).
Each PRP-enabled node has two Ethernet ports and a “Link Redundancy Entity” (LRE, either in
software/firmware or hardware) which coordinates redundancy. Logically, the LRE sits between the
physical Ethernet ports and the operating system on the node, such that the higher layers of the stack
are not aware that the connection is redundant. To facilitate the seamless redundancy, a PRP-enabled
node uses the same MAC address on both networks A and B. Because of this, networks A and B must
not be bridged together.
The figure below shows how the LRE is integrated into the network stack.
Application Layer
Transport Layer
IP Layer
Data Link Layer
PRP Link Redundancy Entity
Physical Layer Physical Layer

A B
Figure 5 PRP LRE in the network stack
PRP Device Types

A device that is PRP-enabled and connected to both networks A and B is called a Doubly Attached Node,
or DAN. A Singly Attached Node, or SAN, is a device that is not PRP-enabled, and is therefore attached
to only one of the networks (either A or B). SANs can only communicate with DANs and SANs on the
same network (e.g. a SAN on network A cannot communicate with a SAN on network B).

All Symphony Plus Control and I/O modules which communicate on PN800 are DANs. PCs and servers
running Symphony Plus Operations and Engineering software are SANs, and will not be fault-tolerant if
there is a failure on the network to which they are connected. With additional network cards and PRP
driver software, PCs may connect to PN800 as DANs. Third-party network drivers are available for PCs
which enable them for PRP, but this configuration has not been tested and, therefore, is not supported.
Topology Restrictions
• PN800 NETWORKS A AND B MUST NEVER BE CONNECTED TOGETHER!
• PN800 NETWORKS A AND B MUST NEVER BE CONNECTED TO A SHARED DEVICE!
PRP operates at the data link layer (layer 2) of the network stack, and is transparent to devices that are
not PRP-enabled. Because PRP uses layer 2 broadcasts to coordinate network redundancy, it is currently
not possible to segment PN800 using layer 3 (IP) routers.
PN800 networks must not be crossed. Only connect ports for PN800 A Ethernet port to switches on
PN800 A, and ports for PN800 B to switches on PN800 B. If the networks are crossed, modules may
indicate errors in their status report, and the resulting behavior may be unpredictable and/or unstable.
Other Network Redundancy Methods

Spanning Tree Protocol (STP) is a feature of many managed network switches. It allows multiple
physical paths to exist between two points of an Ethernet network. It does this by selectively disabling
certain paths such that only one (theoretically optimized) path exists at any given time. When a switch
port in the spanning tree fails or comes online, the tree recalculates, enabling or disabling links, to re-
optimize the network. This recalculation can take up to thirty seconds. The use of STP is untested and,
therefore, is unsupported.
Some managed network switches have additional network redundancy functionality built-in. For
example, certain Hirschmann switches can assist when using other network redundancy protocols. Such
features can disrupt communication on PN800, and must be disabled to ensure proper PN800 operation.
Failure to disable other redundancy functionality will cause network instability and impede
performance.
Some computers have additional network connection redundancy methods, such as Link Aggregation,
NIC failover, or NIC Teaming. Use of any network connection redundancy other than PRP will impair
network performance and stability and is not supported.
Network Security
Do not directly connect PN800 to the public Internet, or to any other public or private network (such
as a corporate Intranet or other office network).

X
XOther Networks Plant Network
Internet
Figure 6 Unacceptable Network Configurations

Plant Network
If it is necessary to connect between PN800 and other networks, a firewall should be implemented as a
minimum safety and security measure. The firewall should, by default, prohibit packets from entering
or exiting PN800, and have explicit rules to allow only the necessary traffic to enter/exit. Connecting
between PN800 and other networks, using a firewall, VPN appliance, or any other device, is neither
recommended nor supported, and, therefore, is outside the scope of this document.
Other Networks Plant Network
Firewall or
VPN Appliance
Figure 7 Acceptable, But Not Recommended, Network Connection
Computers running Symphony Plus Operations, Symphony Plus Engineering, or other software which
needs to communicate on PN800 may be multi-homed (i.e., they may have a network interface on
PN800 and network interfaces on other networks; e.g. the client/server network, computer
management networks, etc.). These computers must not route communications between PN800 and
the other network.

Other Internal Networks
S+ Consoles and
Workstations S+ Servers
PN800 A PN800 B
CTB810 CTB811 CTB810 CTB811

A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F
R R R R Network Interface R R R R R Network Interface R
1 1 1 1 1 1 1 1 1 1
2 2 2 2 2 2 2 2 2 2
3 3 3 3 3 3 3 3 3 3
4 4 4 4 4 4 4 4 4 4
5 5 5 5 5 5 5 5 5 5
6 6 6 6 6 6 6 6 6 6
7 7 7 7 7 7 7 7 7 7
8 8 8 8 8 8 8 8 8 8
STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET
HN800 CW800 Symphony Plus Symphony Plus Symphony Plus Symphony Plus HN800 CW800 Symphony Plus HN800 CW800 Symphony Plus Symphony Plus Symphony Plus Symphony Plus HN800 CW800 Symphony Plus
HC800 CP800 HC800 CP800 PNI800 HC800 CP800 HC800 CP800 PNI800
L+ A A L+ A A A L+ A A L+ A A A
TER800
TER800
TER800
TER800
L+
TER800
TER800
TER800
TER800
L+
L- L- L- L- L- L-
SA SA SA SA SA SA
SB B B SB B B SB B SB B B SB B B SB B
EN1 MB810 PN800 COM EN1 MB810 PN800 COM MB805 PN800 EN1 MB810 PN800 COM EN1 MB810 PN800 COM MB805 PN800
SynchroNet
Satellite Clock
Figure 8 Complete Redundant PN800 Network Overview
Connecting PN800 to any other network, regardless of the bridging technology, is not recommended,
and the end-user assumes all responsibility for safety and security. Such a configuration reduces the
overall security of the PN800 network, and increases the risk of security breaches. ABB strongly
advises against such a configuration.
TCP and UDP Ports Used On PN800

If it is necessary to connect PN800 to outside networks, using any method, communication to TCP ports
502, 2500, 2501, and 3000, and UDP ports 123, 2501, and 2502 must be blocked from entering PN800
from other outside networks.
For optimum security, all incoming traffic should be blocked by default, with only specific paths opened
on an as-needed basis.

Other Security Measures

Implementing other active and/or passive security measures, such as intrusion detection systems, is
outside the scope of this document.
IP Addressing and Subnetting
Overview
IP addresses are composed of a network address and a host address, and are distinguished from one
another by the subnet mask. The network address is determined by performing a bitwise AND of the IP
address and subnet mask, while the host address is calculated using the compliment of the subnet mask
in a similar manner. Boson (http://www.boson.com), a company which provides IT training, has a free
IP subnet calculator that can be used to calculate various attributes of a given IP address and subnet
mask.
PN800
In PN800 IP addresses, the third and fourth octets are used as the INFI-NET Loop and Node number for
legacy compatibility. As such, it is recommended to set aside a /16 network segment for PN800 (e.g.
10.127.0.0 through 10.127.255.255 with a subnet mask of 255.255.0.0). To allow for maximum
expandability, the recommended subnet mask is 255.255.0.0. This creates a single network address
space roughly equivalent to that of INFI-NET. A different network mask can be used to create smaller
networks, but because layer 3 routing within PN800 is not supported, the two different PN800 networks
will not be able to directly communicate with each other. Network masks other than 255.255.0.0 and
255.255.255.0 are not recommended and are unsupported.
In an environment that only implements PN800, there is no restriction on the assignment of loop
numbers. I.e., there is no “central” or “satellite” loop, all valid IP addresses are usable, and all layer 2
network topologies are acceptable.
Though layer 3 routing can be added between PN800 and outside networks, it is neither supported nor
recommended. As such, it is outside the scope of this document.
Hybrid PN800/INFI-NET Systems

In hybrid systems that combine INFI-NET and PN800 (using the SPIEB800), INFI-NET addressing and
physical topology rules must be followed on PN800. These include:
• INFI-NET Loop and PN800 Segment numbers, the third octet of the IP address, must be between
1 and 250 (inclusive). Loop/Segment addresses must be unique within the entire system (e.g.
there cannot be both a PN800 Segment 45.xxx and INFI-NET Loop 45).
• INFI-NET and PN800 Node addresses, the fourth octet of the IP address, must be between 1 and
250 (inclusive). For modules with redundancy capability (e.g. CP800, IPT800), the primary node
address must be even (between 2 and 248 inclusive) because node address + 1 is reserved for
that node’s backup. This requirement is enforced by the modules' firmware. E.g. a CP800

cannot be directly assigned an IP address of 10.192.30.7. Nodes designed without redundancy

(e.g. PNI800) may have any valid node address (even or odd), as long as the selected node
address does not collide with that of any other node (primary or backup, redundant or non-
redundant). For example, if the primary CP800 in a redundant pair has an IP address of
10.192.30.6, its backup module has 10.192.30.7. Or, if the CP800 at 10.192.30.6 is non-
redundant, a PNI800 may have the IP address 10.192.30.7; but, if the non-redundant CP800 is
ever made redundant, the PNI800's IP address must be changed.
• There must be a single “central” network, either INFI-NET Loop 1 or PN800 Segment 1.
• If INFI-NET loop 1 is used as the central network:
o There must be one IEB800 between INFI-NET loop 1 and each satellite PN800 segment.
o Satellite PN800 segments may not be directly connected together.
o Satellite INFI-NET loops continue to function using existing INFI-NET local or remote
bridges.
• If PN800 Segment 1 is used as the central network:
o There must be one IEB800 between PN800 Segment 1 and each satellite INFI-NET loop.
o Satellite INFI-NET loops may not have additional satellite loops.
o Additional PN800 segments follow PN800 physical topology rules.
SynchroNet
Because SynchroNet is completely independent of PN800, its IP address space must be similarly isolated.
This separation allows controllers in different PN800 segments to share one time master. Therefore, the
IP address space must be isolated from the PN800 address space. Though the IP addresses on
SynchroNet can be assigned arbitrarily (i.e. they do not have to correlate to the PN800 IP addresses in
any way), it is recommended to use a similar addressing scheme as PN800 (e.g. the third octet
represents the PN800 segment number, and the fourth octet represents the node number on the
segment).
To allow both the primary and backup controllers to maintain accurate time from the time master, they
must have unique IP addresses. In a redundant controller, the backup’s SynchroNet address is set by the
primary (via the redundancy link). The fourth octet of the IP address depends on the position (right side
or left side) of the base in the controller node. The left side controller always assumes the address
specified, while the controller on the right assumes address N+1 (i.e. the IP address is independent of
the role, primary or backup). Modules must be assigned an even number in the last octet, and they will
automatically calculate the actual address (N or N+1). All modules must use an even value in the fourth
octet (and allow the backup to assume an odd number) - the firmware will adjust as necessary.
For example, if the SynchroNet address entered is 10.25.4.4, then the controller on the left base will
always be 10.25.4.4, and the controller on the right will always be 10.25.4.5.
Other Address Restrictions

IP addresses for PN800, SynchroNet, and the Ethernet foreign device network must all be different from
each other, and must not collide. They cannot be subnets or supernets of each other.

In a hybrid INFI-NET/PN800 systems, loop/segment addresses must be unique in the entire system (e.g.
there cannot be a loop 15 on INFI-NET and segment 15 on PN800).
Equipment Guide
ABB does not recommend any particular network switch or router vendor, as the Symphony Plus
product line adheres to standard Ethernet protocols. However, several vendors’ equipment has been
used during product development and testing, including Cisco, Linksys, Dell, Netgear, D-Link, 3COM, HP,
MOXA, Contemporary Controls CTRLink, Advantech, and others. At minimum, switches must be capable
of 100Mbps Full-Duplex operation.
A hard-wired network (copper or fiber optic Ethernet) must be used for Symphony Plus. Wireless
networks of any type are not supported.
Networking equipment used for PN800 must be dedicated. I.e. PN800 network hardware cannot be
shared with other networks (e.g. HGS, other Ethernet field networks, SynchroNet, etc.).
Types of Ethernet Devices

Switches
A switch is a device which allows two or more devices to communicate with each other over Ethernet. It
inspects each communication packet, and re-transmits the packet (unmodified) on the port to which the
destination device is connected. This means that when a packet is received, the switch inspects the
packet and reads the destination MAC address. It will then re-transmit the packet on the interface
which is connected to the destination device (and no others).
Some managed switches are capable of performing basic IP routing. These are called Layer 3 Switches.
Use of any layer 3 routing is not supported on PN800.
Routers
A router allows an IP Ethernet network to be broken down into smaller Subnets to reduce load on
switches, and reduce the size of MAC address tables in switches. Due to the method with which PRP
coordinates redundancy, installing layer 3 routers between segments of PN800 is not supported.
Managed vs. Unmanaged Switches

PN800 is designed to be fully usable on networks employing only unmanaged switches (i.e. no
functionality relies on the capabilities of managed network switches, such as VLAN tagging, trunking, link
aggregation, etc.). This simplicity reduces the number of possible misconfigurations and security
vulnerabilities on PN800, and keeps the Symphony Plus system cost-effective. In general, unmanaged
switches are strongly recommended for PN800.
Managed switches may be desirable for various reasons, such as larger port count, greater throughput,
additional advanced diagnostic capabilities, and other advanced features. However, implementing

these advanced capabilities can impede network performance and stability. Great care must be taken
when activating such features to ensure that they do not negatively impact the performance and
throughput of PN800.
Managed Switch Configuration Guidelines

Below are some general guidelines when using managed switches, with configuration commands for
Cisco IOS:
• Switch ports must be set to auto-negotiate speed and duplex. All Symphony Plus modules are
designed to auto-negotiate port speed and duplex. Manually configuring the switch port speed
and duplex will impede network performance and stability. In Cisco IOS, the configuration
directives are speed auto and duplex auto in the interface configuration context. Note
that these will not show up when the configuration is displayed, as they are the defaults (i.e.
speed and duplex will only be shown if they are manually set, i.e. misconfigured).
• Switches must be able to pass packets at least 1500 bytes in size. The MTU may be greater
than 1500, but it may not be less than 1500. This is the typical default value for most switches
running Ethernet on a local area network.
• Switches must not be shared with other networks, regardless of segmentation technologies
(e.g. IEEE 802.1q VLANs). Switches must be dedicated to a particular network (PN800 A, PN800
B, SynchroNet, or Ethernet FDI networks).
• Switches should be configured to use Rapid Spanning Tree. IEEE 802.1D Spanning Tree can
take up to 30 seconds to re-calculate and put a newly connected port into forwarding mode,
while IEEE802.1w Rapid Spanning Tree can do so much faster (6 seconds or less). In Cisco IOS,
the configuration directive is spanning-tree mode rapid-pvst in the global
configuration context.
• Switch ports to which C&I/O modules are connected must be excluded from spanning tree.
Known as “portfast,” this setting immediately puts the port into forwarding mode (preventing
delays, sometimes up to 30 seconds, due to spanning tree re-calculation). In Cisco IOS, the
configuration directive is spanning-tree portfast in the interface configuration context.
The portfast setting must be enabled before powering up a new module on a port!
• Switch ports which are connected to other switches must NOT be excluded from spanning
tree. Excluding inter-switch link ports can cause network loops to be created, which can cause a
network failure. This is the default behavior on Cisco IOS. If a switch port connected to another
switch is inadvertently excluded from spanning tree, the command to re-include it is no
spanning-tree portfast in the interface configuration context.
• Unused switch ports should be disabled to prevent inadvertent spanning tree topology changes
and recalculations. In Cisco IOS, the configuration directive is shutdown in the interface
configuration context. Interfaces should only be enabled once all appropriate interface-level
settings have been entered in the switch’s configuration.
• IGMP snooping should be enabled. This allows for devices on these networks to utilize
multicast packet transmissions when appropriate. This is the default setting on Cisco IOS. If

IGMP snooping is disabled, the command to enable it is ip igmp snooping in the global
configuration context.
• Be sure to save the running configuration after making changes. The command to do this in
Cisco IOS is copy running-config startup-config in Enable mode.
Additional Notes About Managed Switches

• Statistics for switch ports may show frames that are larger than expected (“giants” in Cisco
switches). This is due to PRP adding control flags and data to every packet.
Network Cabling
Electrically shielded copper Ethernet cables should be used when wiring S+ C&I/O networks. Refer to
documentation for other devices connected to the Ethernet Foreign Device network to determine if
shielded cables can be used. A minimum of Enhanced Category 5 (“CAT5E”) must be used.
Ethernet cables should also be color-coded to clearly identify a cable’s purpose. Table 3 below has
ABB’s recommended color-coding scheme. Additionally, both ends of the cables should be clearly
labeled with the network identifier and the location of the other end (e.g. a switch identifier and port
number).
Network Cable Color

PN800 A Red*
PN800 B Blue*
SynchroNet Brown
Ethernet Fieldbus Network A Black
Ethernet Fieldbus Network B White
S+ Operations Client/Server Network A Yellow
S+ Operations Client Server Network B Orange
Table 3 Network Cable Color Codes
* Defined in the PRP standard (section 4.2.1.3 of IEC62439-3).
INFI-NET – PN800 Bridge IEB800

The INFI-NET - PN800 Bridge (IEB800) allows existing Symphony Harmony installations to expand by
adding a Symphony Plus PN800 segment. Refer to IP Addressing and Subnetting for configuration
restrictions in such hybrid networks. See Figure 11 (page 20) and Figure 12 (page 21) for example
topologies. Refer to the IEB800 manual for additional implementation details.
SynchroNet Time Masters

ABB does not recommend any particular time master. During product development and testing, a
Symmetricom SyncServer S350 with a GPS antenna was used. But, any time master supporting SNTP can
be used.

Recommended Physical Topologies

Thanks to the efficiencies of network switches compared to hubs, individual packets are only
transmitted on the necessary switch port(s) in order for them to get to their destination (i.e. individual
modules will only see traffic that is destined for them). All modules will still receive broadcast messages,
and subscribed modules will receive multicast messages.
Single Segment
PN800 “A”
Network Switch

A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F
R R R R Network Interface R R R Network Interface R
1 1 1 1 1 1 1 1
2 2 2 2 2 2 2 2
3 3 3 3 3 3 3 3
4 4 4 4 4 4 4 4
5 5 5 5 5 5 5 5
6 6 6 6 6 6 6 6
7 7 7 7 7 7 7 7
8 8 8 8 8 8 8 8
STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET
HN800 CW800 Symphony Plus Symphony Plus Symphony Plus Symphony Plus HN800 CW800 Symphony Plus HN800 CW800 Symphony Plus Symphony Plus
HN800 CW800 Symphony Plus
HC800 CP800 HC800 CP800 PNI800 HC800 CP800 PNI800
L+ A A L+ A A L+ A L+ A A L+ A
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
L- L- L- L- L-
SA SA SA SA SA
SB B B SB B B SB B SB B B SB B
EN1 MB810 PN800 COM EN1 MB810 PN800 COM MB805 PN800 EN1 MB810 PN800 COM MB805 PN800
PN800 “B”
Network Switch
Figure 9 Single Network Segment Topology
In this topology, there is only one network switch on each of the redundant networks, with all PN800
nodes connected to the single switch. It can seamlessly be expanded into a larger two- or multiple-
segment topology. In this topology, an IEB800 can be connected to a spare port on the segment
switches.

Two Segments
CTB810 CTB811
R R R R
1 1 1 1
2 2 2 2
3 3 3 3
4 4 4 4
5 5 5 5
6 6 6 6
7 7 7 7
8 8 8 8
HC800 CP800 HC800 CP800
L+ A A L+ A A
TER800
TER800
TER800
TER800
L- L-
SA SA
SB B B SB B B
PN800 “A” PN800 “B”

Segment 1 Segment 1
A BB F
Network Interface R
1
2
3
4
5
6
7
8
STOP/RESET
Symphony Plus
PNI800
L+ A
L-
CTB810 CTB811
A BB F A BB F SA
R R SB B
MB805 PN800
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
HN800 CW800 Symphony Plus Symphony Plus

HN800 CW800
HC800 CP800
L+ A A
TER800
TER800
TER800
TER800
L-
SA
SB B B
EN1 MB810 PN800 COM
A BB F A BB F
Network Interface R Network Interface R
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
Symphony Plus Symphony Plus

A BB F
PNI800 PNI800 Network Interface R
1
2
L+ A L+ A 3
L- L- 4
SA SA 5
6
SB B SB B 7
8
MB805 PN800 MB805 PN800
STOP/RESET
Symphony Plus
PNI800
L+ A
L-
SA
SB B
MB805 PN800
CTB810 CTB811
A BB F A BB F
R R
1 1
2 2
3 3
4 4
5 5
6 6
7 7
8 8
HN800 CW800 Symphony Plus Symphony Plus

HN800 CW800
HC800 CP800
L+ A A
TER800
TER800
TER800
TER800
L-
SA
SB B B
EN1 MB810 PN800 COM
PN800 “A”
PN800 “B”
Segment 2
CTB810 CTB811
R R R R
Segment 2
1 1 1 1
2 2 2 2
3 3 3 3
4 4 4 4
5 5 5 5
6 6 6 6
7 7 7 7
8 8 8 8
HC800 CP800 HC800 CP800
L+ A A L+ A A
TER800
TER800
TER800
TER800
L- L-
SA SA
SB B B SB B B
Figure 10 Two Segment Topology
In this topology, there are two redundant network switches, one for each redundant segment. Each
network switch is connected to the PN800 nodes assigned to that segment. This ensures that only the
traffic which needs to cross to the other segment goes across the link between the switches. In this
topology, an IEB800 could be connected to either segment switch (preferably the one which will be
communicating with the INFI-NET loop more than the other). Alternatively, the Several Segment
topology could be employed to add an IEB800.

Several Segments
PN800 “A”
Core
Switch
Segment 1 Segment 2 Segment 3 Segment 4
CTB810 CTB811 CTB810 CTB811 CTB810 CTB811 CTB810 CTB811 CTB810 CTB811 CTB810 CTB811
A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F
R R R R R R Network Interface R Network Interface R R R R R Network Interface R Network Interface R Network Interface R R R R R Network Interface R R R R R
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5
6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6
7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7
8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8
STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET
STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET
HN800 CW800 Symphony Plus Symphony Plus Symphony Plus Symphony Plus
HN800 CW800 HN800 CW800 Symphony Plus Symphony Plus
HN800 CW800 Symphony Plus Symphony Plus HN800 CW800 Symphony Plus Symphony Plus Symphony Plus Symphony Plus
HN800 CW800 Symphony Plus Symphony Plus Symphony Plus HN800 CW800 Symphony Plus Symphony Plus
HN800 CW800 HN800 CW800 Symphony Plus Symphony Plus
HN800 CW800 Symphony Plus Symphony Plus Symphony Plus Symphony Plus
HN800 CW800
HC800 CP800 HC800 CP800 HC800 CP800 PNI800 PNI800 HC800 CP800 HC800 CP800 PNI800 PNI800 PNI800 HC800 CP800 HC800 CP800 PNI800 HC800 CP800 HC800 CP800
L+ A A A A A A A L+ A A L+ A A L+ A A A A A
L+ A A L+ A A L+ A A L+ A A L+ L+
TER800
TER800
TER800
TER800
L+ L+ L+ L+
TER800
TER800
TER800
TER800
L+
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
L- L- L- L- L- L- L- L- L- L- L- L- L- L- L-
SA SA SA SA SA SA SA SA SA SA SA SA SA SA SA
SB SB SB SB B SB SB SB B SB B SB B SB B B SB B B SB B SB SB
B B B B B B SB B B B B B B B B B
EN1 PN800 MB805 PN800 MB805 PN800 MB805 PN800 MB805 PN800 MB805 PN800 EN1 PN800 EN1 MB810 PN800 COM MB805 PN800 EN1 PN800
EN1 MB810 PN800 COM EN1 MB810 PN800 COM MB810 COM EN1 MB810 PN800 COM EN1 MB810 PN800 COM MB810 COM EN1 MB810 PN800 COM MB810 COM
Segment 1 Segment 2 Segment 3 Segment 4
PN800 “B”
Core
Switch
Figure 11 Several Segment Topology
In this topology, there is a core switch which is connected to segment switches, with one segment
switch per segment. The segment switches are then connected to PN800 nodes (e.g. CP800, PNI800) on
their respective segments. In this topology, an IEB800 may be connected to the core switch. Refer to
the IEB800 manual for additional information and configuration restrictions.
Expanding INFI-NET
In this scenario, a customer has an existing Symphony Harmony system, which is being expanded (using
the IEB800) to add a PN800 segment.

CTB810 CTB811 CTB810 CTB811 CTB810 CTB811

A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F
R R R R Network Interface R R R R R Network Interface R R R R R
1 1 1 1 1 1 1 1 1 1 1 1 1 1
2 2 2 2 2 2 2 2 2 2 2 2 2 2
3 3 3 3 3 3 3 3 3 3 3 3 3 3
4 4 4 4 4 4 4 4 4 4 4 4 4 4
5 5 5 5 5 5 5 5 5 5 5 5 5 5
6 6 6 6 6 6 6 6 6 6 6 6 6 6
7 7 7 7 7 7 7 7 7 7 7 7 7 7
8 8 8 8 8 8 8 8 8 8 8 8 8 8
STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET
HN800 CW800 Symphony Plus Symphony Plus Symphony Plus Symphony Plus HN800 CW800 Symphony Plus HN800 CW800 Symphony Plus Symphony Plus Symphony Plus Symphony Plus HN800 CW800 Symphony Plus HN800 CW800 Symphony Plus Symphony Plus Symphony Plus Symphony Plus HN800 CW800
HC800 CP800 HC800 CP800 PNI800 HC800 CP800 HC800 CP800 PNI800 HC800 CP800 HC800 CP800
L+ A A L+ A A L+ A L+ A A L+ A A L+ A L+ A A L+ A A
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
L- L- L- L- L- L- L- L-
SA SA SA SA SA SA SA SA
SB B B SB B B SB B SB B B SB B B SB B SB B B SB B B
EN1 MB810 PN800 COM EN1 MB810 PN800 COM MB805 PN800 EN1 MB810 PN800 COM EN1 MB810 PN800 COM MB805 PN800 EN1 MB810 PN800 COM EN1 MB810 PN800 COM
PN800 A PN800 B
PN800
Segment 40
Symphony Plus Symphony Plus Symphony Plus Symphony Plus
NIS21 IPT800 IPT800 NIS21

1 1 1 1
2 2 2 2
3 3 3 3
4 A
5
4
5
CH 1 4
5
CH 1 4 A
5
New Symphony
6 6 6 6
7 7 7 7
8 8 8 8
1 1
2 2
3 3
4 B
5
CH 0 CH 0 4 B
5
6 6
7 7
Plus Additions
8 8
Existing INFI-NET
Installation
INFI-NET
Ring 1
INFI-NET
Ring 10 INFI-NET
Ring 30
Figure 12 Expanding Symphony Harmony with Symphony Plus
Hybrid INFI-NET/PN800 System

The following example shows an existing INFI-NET system where the central loop 1 is replaced by
PN800, with expansion using PN800. Existing satellite loops are connected using the IEB800 (replacing
IIL or IIR bridges).

CTB810 CTB811
A BB F A BB F A BB F A BB F A BB F
R R R R Network Interface R
1 1 1 1 1
2 2 2 2 2
3 3 3 3 3
PN800
4 4 4 4 4
5 5 5 5 5
6 6 6 6 6
7 7 7 7 7
8 8 8 8 8
STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET
Segment 10
HN800 CW800 Symphony Plus Symphony Plus Symphony Plus Symphony Plus HN800 CW800 Symphony Plus
HC800 CP800 HC800 CP800 PNI800
L+ A A L+ A A L+ A
TER800
TER800
TER800
TER800
L- L- L-
SA SA SA
SB B B SB B B SB B
EN1 MB810 PN800 COM EN1 MB810 PN800 COM MB805 PN800

A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F
R R R R Network Interface R R R R R
1 1 1 1 1 1 1 1 1
2 2 2 2 2 2 2 2 2
3 3 3 3 3 3 3 3 3
4 4 4 4 4 4 4 4 4
5 5 5 5 5 5 5 5 5
6 6 6 6 6 6 6 6 6
7 7 7 7 7 7 7 7 7
8 8 8 8 8 8 8 8 8
STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET
PN800 A PN800 B
PN800 HN800 CW800
L+
Symphony Plus
HC800
A
Symphony Plus
CP800
A L+
Symphony Plus
HC800
A
Symphony Plus
CP800
A
PNI800
A
HN800 CW800
L+
Symphony Plus
HC800
A
Symphony Plus
CP800
A L+
Symphony Plus
HC800
A
Symphony Plus
CP800
A
HN800 CW800
Segment 1
L+
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
L- L- L- L- L-
SA SA SA SA SA
SB B B SB B B SB B SB B B SB B B
EN1 MB810 PN800 COM EN1 MB810 PN800 COM MB805 PN800 EN1 MB810 PN800 COM EN1 MB810 PN800 COM
PN800 A PN800 B
Symphony Plus Symphony Plus Symphony Plus Symphony Plus Symphony Plus Symphony Plus Symphony Plus Symphony Plus Symphony Plus Symphony Plus Symphony Plus Symphony Plus
NIS21 IPT800 IPT800 NIS21 NIS21 IPT800 IPT800 NIS21 NIS21 IPT800 IPT800 NIS21
1 1 1 1 1 1 1 1 1 1 1 1
2 2 2 2 2 2 2 2 2 2 2 2
3 3 3 3 3 3 3 3 3 3 3 3
4 A
5
4
5
CH 1 4
5
CH 1 4 A
5
4 A
5
4
5
CH 1 4
5
CH 1 4 A
5
4 A
5
4
5
CH 1 4
5
CH 1 4 A
5
6 6 6 6 6 6 6 6 6 6 6 6
7 7 7 7 7 7 7 7 7 7 7 7
8 8 8 8 8 8 8 8 8 8 8 8
1 1 1 1 1 1
2 2 2 2 2 2
3 3 3 3 3 3
4 B
5
CH 0 CH 0 4 B
5
4 B
5
CH 0 CH 0 4 B
5
4 B
5
CH 0 CH 0 4 B
5
6 6 6 6 6 6
7 7 7 7 7 7
8 8 8 8 8 8
INFI-NET
Ring 20 INFI-NET
INFI-NET
Ring 40
Ring 30
Figure 13 Hybrid INFI-NET/PN800 System
Other Topologies
Many other network topology designs are possible. It is possible to sub-segment PN800 segments, to
further minimize excess traffic passing through and between network switches. However, care must be
taken, as every switch through which a packet passes will add additional latency. It may be better for
performance to replace a smaller switch with a larger one.
Example Installation
Below is an example installation, using four redundant HPC800s, three PNI800s (two for S+ Operations
and one for S+ Engineering), two (redundant) S+ Operations servers, two S+ Operations consoles, a
stand-alone S+ Engineering workstation, and a satellite clock SNTP server for SynchroNet.

Corporate Intranet
Corporate
Firewall
Internet
Management Servers
(Active Directory,
WSUS, etc.)
S+ Operations Network
S+
S+ Operations Engineering
Consoles Workstation
S+
Servers
S+ PC Management Network
PN800 A PN800 B
CTB810 CTB811 CTB810 CTB811 CTB810 CTB811 CTB810 CTB811

A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F A BB F
R R R R Network Interface R R R R R Network Interface R R R R R Network Interface R R R R R
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4
5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5 5
6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6 6
7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7 7
8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8 8
STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET STOP/RESET
HN800 CW800 Symphony Plus Symphony Plus Symphony Plus Symphony Plus HN800 CW800 Symphony Plus HN800 CW800 Symphony Plus Symphony Plus Symphony Plus Symphony Plus HN800 CW800 Symphony Plus HN800 CW800 Symphony Plus Symphony Plus Symphony Plus Symphony Plus HN800 CW800 Symphony Plus HN800 CW800 Symphony Plus Symphony Plus Symphony Plus Symphony Plus HN800 CW800
HC800 CP800 HC800 CP800 PNI800 HC800 CP800 HC800 CP800 PNI800 HC800 CP800 HC800 CP800 PNI800 HC800 CP800 HC800 CP800
L+ A A L+ A A L+ A L+ A A L+ A A L+ A L+ A A L+ A A L+ A L+ A A L+ A A
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
TER800
L- L- L- L- L- L- L- L- L- L- L-
SA SA SA SA SA SA SA SA SA SA SA
SB B B SB B B SB B SB B B SB B B SB B SB B B SB B B SB B SB B B SB B B
EN1 MB810 PN800 COM EN1 MB810 PN800 COM MB805 PN800 EN1 MB810 PN800 COM EN1 MB810 PN800 COM MB805 PN800 EN1 MB810 PN800 COM EN1 MB810 PN800 COM MB805 PN800 EN1 MB810 PN800 COM EN1 MB810 PN800 COM
SynchroNet
Satellite Clock
Figure 14 Example Installation
Table 4 below lists IP addresses for all devices on all networks in the above diagram. PN800,
SynchroNet, and OpsNet subnet masks are 255.255.0.0. Addressing the Management Network and
Corporate Intranet are beyond the scope of this document.

Device PN800 SynchroNet S+

Operations
Network
HPC1 10.127.1.10 10.126.1.10 N/A
10.126.1.11
HPC2 10.127.1.12 10.126.1.12 N/A
10.126.1.13
HPC3 10.127.1.14 10.126.1.14 N/A
10.126.1.15
HPC4 10.127.1.16 10.126.1.16 N/A
10.126.1.17
PNI1 10.127.1.101 N/A N/A
PNI2 10.127.1.102 N/A N/A
PNI3 10.127.1.103 N/A N/A
S+ Operations Server 1 10.127.1.200 10.126.1.200 10.125.1.200
S+ Operations Server 2 10.127.1.201 10.126.1.201 10.125.1.201
S+ Operations Console 1 N/A N/A 10.125.1.202
S+ Operations Console 2 N/A N/A 10.125.1.203
S+ Engineering 10.127.1.111 N/A N/A
Workstation
SNTP Server N/A 10.126.1.2 N/A
Table 4 IP Addresses for Example Installation
Remote Network Connections

IP Ethernet networking technology provides many options for connecting to remote sites (e.g. VPN,
point-to-point or mesh wireless, et al). The only supported PN800 network connection to a remote site
is a dedicated, hard-wired, direct link, which does not utilize any equipment or services owned or
controlled by a third-party (e.g. an Internet service provider). Configurations which extend any
Symphony Plus communication network using a third-party connection are neither recommended nor
supported.

Revision History
Revision Section Description Date Changed
by & Dept.
A All Initial 4 April C. Marks,
2013 PSPG
B IP Addressing Added addressing rules and tool 05 June C. Marks,
information. 2013 PSPG
Network Security Clarified definition of air-gapped network.
All Incremented document revision
Network Cabling Added CAT5E recommendation.
Ethernet Foreign Added example diagram.
Device Interface
C PN800 Plant Added comment that PN800 must be a 25 June C. Marks,
Network dedicated network. 2013 PSPG
PN800 Network Added comments that NIC teaming should
Redundancy not be used on PCs connected to PN800.
IP Addressing Clarified INFI-NET and PN800 node
addressing requirements.
All Incremented document revision.
D Additional Added note to clarify SPIEB800 is an 22 July R. Ogorek,
Documentation unreleased product currently under 2013 PSPG
development
Hybrid Added “currently under development” to
PN800/INFI-NET first paragraph at first mention of
Systems SPIEB800
E Managed vs. Added initial guidelines for using managed 05 March C. Marks,
Unmanaged switches. 2014 PSPG
Switches
Network Cabling Added color code table, changed color
coding to match 800xA guidelines
(3BSE034463-0510).
Additional Removed note that IEB800 is under
Documentation, development and un-released.
Hybrid
PN800/INFI-NET
Systems
Network Security Removed comment about using an air-
gapped network.
Contents Added Table of Contents
F Managed Switch Added procedure to set MTU, section 06 March C. Marks,
Configuration about spanning tree for inter-switch links, 2014 PSPG
Guidelines section about IGMP, and section about
saving switch configuration.

G Managed Switch Changed MTU requirement for the switch 11 July R. Ogorek
Configuration to 1500 bytes, was 1522. Final 2016 PAPG
Guidelines implementation of PN800 network design
was able to reduce the MTU to 1500
(default for many switches).


2VAA002993 G en S Control and IO Symphony Plus Ethernet Networking

Uploaded by

Document Information

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

2VAA002993 G en S Control and IO Symphony Plus Ethernet Networking

Uploaded by

Copyright:

Available Formats

Technical Description

Symphony Plus Control and I/O

IP Addressing and Subnetting ..................................................................................................................... 12

The Network Stack

Data Link Layer

Figure 1 The Networking Stack

Data Link Layer

IP routing is currently not supported for PN800.

Putting It All Together

Figure 2 Example Ethernet Packet

IEC 62439-3 International Standard, Industrial Communication Networks – High availability

How INFI-NET concepts and terms translate to PN800

INFI-NET Term Symphony Plus Term

Symphony Plus Ethernet Networks

PN800 Plant Network

SynchroNet SOE Time Synchronization Network

STOP/RESET STOP/RESET STOP/RESET STOP/RESET

STOP/RESET STOP/RESET STOP/RESET STOP/RESET

EN1 MB810 PN800 COM EN1 MB810 PN800 COM

EN1 MB810 PN800 COM EN1 MB810 PN800 COM

Figure 3 Example SynchroNet Network

Ethernet Foreign Device Interface

HN800 CW800 Symphony Plus Symphony Plus HN800 CW800

EN1 MB810 PN800 COM

Figure 4 Example Foreign Device Network

PN800 Network Redundancy

PRP Functional Overview

Data Link Layer

PRP Link Redundancy Entity

Physical Layer Physical Layer

Figure 5 PRP LRE in the network stack

PRP Device Types

Other Network Redundancy Methods

Figure 6 Unacceptable Network Configurations

Other Networks Plant Network

Figure 7 Acceptable, But Not Recommended, Network Connection

Other Internal Networks

CTB810 CTB811 CTB810 CTB811

Figure 8 Complete Redundant PN800 Network Overview

TCP and UDP Ports Used On PN800

Other Security Measures

IP Addressing and Subnetting

Hybrid PN800/INFI-NET Systems

cannot be directly assigned an IP address of 10.192.30.7. Nodes designed without redundancy

Other Address Restrictions

Types of Ethernet Devices

Managed vs. Unmanaged Switches

Managed Switch Configuration Guidelines

Additional Notes About Managed Switches

Network Cable Color

* Defined in the PRP standard (section 4.2.1.3 of IEC62439-3).

INFI-NET – PN800 Bridge IEB800

SynchroNet Time Masters

Recommended Physical Topologies

CTB810 CTB811 CTB810 CTB811

HC800 CP800 HC800 CP800 PNI800 HC800 CP800 PNI800

Figure 9 Single Network Segment Topology

EN1 MB810 PN800 COM EN1 MB810 PN800 COM

PN800 “A” PN800 “B”

HN800 CW800 Symphony Plus Symphony Plus

EN1 MB810 PN800 COM

Symphony Plus Symphony Plus

HN800 CW800 Symphony Plus Symphony Plus

EN1 MB810 PN800 COM