Table of Contents
Advertisement
sist, as in
settings aligned. For configuration examples, see
ˆ ECN LAN topology: IEC 61375 standards[12, 15] allows for a set of different
physical ECN topologies, including ring topology which provides redundancy
within the ECN. FRNT
Note
As of WeOS v4.24.1, a WeOS node can only support a single FRNT ring.
Thus, in topologies with multiple ECNs per ETBN, one can either (a)
use VLANs to allow multiple ECNs over a single FRNT ring, or (b) build
multiple separate FRNT rings. In the latter case the ETBNs would be
connected to, but not part of the FRNT rings (placing routing function-
ality and layer-2 redundancy functionality in different units is generally
a good design principle).
ˆ Unit configuration and replacement: For easy deployment and replacement
of WeOS train routers (ETBNs) and vehicle switches, use of the WeOS USB
deployment functionality
43.1.3 A configuration example
In this section we will go through the steps to setup the ETBNs of an example con-
sist, given the bogus consist UUID "1111. . . ". You could then configure another
consist, e.g., with UUID "2222. . . " and connect the two consists together.
ˆ The example assumes the use of RFR-212-FB (Corazon platform).
ˆ The configuration example focus on ETBN #1 in
settings would be the same for ETBN #2.
ˆ This example assumes backbone ID TCMS(0), but could be adapted to other
backbone IDs.
43.1.3.1 Backbone ports and aggregates
The RedFox Rail (RFR-212-FB) router[57] is designed to act as an ETBN with two
redundant links in each direction: X9-X10 in one direction and X11-X12 in the
1086
fig.
43.3b), d) and e), all of the ETBNs must have their Dir1
(chapter
16) is suitable as ring protocol within the ECN.
(section
Westermo OS Management Guide
7.1.7) is recommended.
fig.
© 2018 Westermo Teleindustri AB
Version 4.24.1-0
section
43.1.3.4.
43.4, but most of the
Advertisement
Table of Contents
