204
saia-pcd.com
Ethernet 2
Ethernet 1.1
Ethernet 1.2
SCADA 1
SCADA 2
➤
➤
Ethernet
2
Ethernet
1
other
Communication & interaction
Constructing redundant Ethernet networks
Network redundancy is often required by systems with high
demands placed on them with regard to operational availability,
such as tunnel controllers in traffic technology, or on ships,
for example. The two Ethernet connections provide the
PCD3.M6860 with connection redundancy. Standard
components (switches and cables) can be used to construct two
separate, redundant networks. The networks and choice of
interfaces are monitored by the application program.
Together with specific switches and fibre-optic cables,
the network availability can be raise further by creating a fibre
optic ring. The switches automatically identify an interruption
to the ring and reroute the data traffic accordingly.
The automated system network can be divided into several physical networks for
better organisation and increased availability and performance.
Highly available Ethernet with two fibre optic rings. In the event of an interruption,
the switches automatically reroute the data traffic via the ring which is still
functioning. A defective switch or ring can be recognised in the application
program and the data traffic transmitted via the second ring or second interface.
Constructing Ethernet networks separately or redundantly with PCD3.M6860*
The PCD3.M6860 CPU has two independent Ethernet interfaces which are used
to construct physically separate networks (e. g. company or automated system
networks) or redundant networks. The second interface as fitted with an additional
2-port switch.
Properties, functions
`
The technical data of the PCD3.M6860 are identical to those of a PCD3.M5560, apart from the second Ethernet interface (in place
of the serial interfaces)
`
The Ethernet interfaces are separate and both have an independent IP configuration. The IP addresses must not be in the same
subnet. IP routing between the two interfaces is not supported.
`
All IP protocols are supported on both interfaces. This enables access to the automation server and the PCD data via both interfaces.
Access to the PG programming tool is also supported on both interfaces.
`
BACnet and L
ON
IP are only supported on one interface (1 or 2)
`
The S-Bus gateway function between the two Ethernet interfaces is also supported
Separating Ethernet networks
It is worth physically separating networks when:
`
The automation devices and the standard IT devices (PC, server, etc.) must not be operated on the same network for security reasons.
In this instance, the PCD3.M6860 functions like a “firewall” as only S-Bus telegrams can be transmitted from one interface to another.
Other IP telegrams are not routed.
`
The data traffic cannot take place in the same physical network for performance reasons
`
The infrastructure (e. g. network cabling) requires separation
7KH DXWRPDWHG V\VWHP DQG FRPSDQ\ QHWZRUNV DUH SK\VLFDOO\ VHSDUDWH
Company network
Ethernet 2
Ethernet 1
Automated system network
