forked from luck/tmp_suning_uos_patched
f421436a59
High-availability Seamless Redundancy ("HSR") provides instant failover
redundancy for Ethernet networks. It requires a special network topology where
all nodes are connected in a ring (each node having two physical network
interfaces). It is suited for applications that demand high availability and
very short reaction time.
HSR acts on the Ethernet layer, using a registered Ethernet protocol type to
send special HSR frames in both directions over the ring. The driver creates
virtual network interfaces that can be used just like any ordinary Linux
network interface, for IP/TCP/UDP traffic etc. All nodes in the network ring
must be HSR capable.
This code is a "best effort" to comply with the HSR standard as described in
IEC 62439-3:2010 (HSRv0).
Signed-off-by: Arvid Brodin <arvid.brodin@xdin.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
28 lines
1.0 KiB
Plaintext
28 lines
1.0 KiB
Plaintext
#
|
|
# IEC 62439-3 High-availability Seamless Redundancy
|
|
#
|
|
|
|
config HSR
|
|
tristate "High-availability Seamless Redundancy (HSR)"
|
|
---help---
|
|
If you say Y here, then your Linux box will be able to act as a
|
|
DANH ("Doubly attached node implementing HSR"). For this to work,
|
|
your Linux box needs (at least) two physical Ethernet interfaces,
|
|
and it must be connected as a node in a ring network together with
|
|
other HSR capable nodes.
|
|
|
|
All Ethernet frames sent over the hsr device will be sent in both
|
|
directions on the ring (over both slave ports), giving a redundant,
|
|
instant fail-over network. Each HSR node in the ring acts like a
|
|
bridge for HSR frames, but filters frames that have been forwarded
|
|
earlier.
|
|
|
|
This code is a "best effort" to comply with the HSR standard as
|
|
described in IEC 62439-3:2010 (HSRv0), but no compliancy tests have
|
|
been made.
|
|
|
|
You need to perform any and all necessary tests yourself before
|
|
relying on this code in a safety critical system!
|
|
|
|
If unsure, say N.
|