16 en | Topologies Modular fire panel
07.2019 | 5.9 | F.01U.247.450 Networking guide Bosch Sicherheitssysteme GmbH
Figure4.7: CAN loop with Ethernet segments
4.7 Ethernet backbone with sub-loops (Ethernet/CAN)
An Ethernet backbone is connected to all sub-loops, and therefore a connecting core area with
high data transmission rates. The RSTP switches in the backbone are not superordinate, by
default. Note that with this topology you are required to determine the network diameter.
Panel controllers, remote keypads and the connected external RSTP switches are regarded as
RSTP switches. CAN-networked panels are disregarded when determining the network
diameter.
Consider the settings for loops with more than 20 RSTP switches, see Settings for loops with
more than 20 RSTP switches, page 12.
Notice!
This topology requires additional settings for all RSTP switches in the backbone. More in-
depth knowledge of networks is therefore required.
Notice!
If the panel acts as an interface with a CAN sub-loop, this panel must then also be designed
redundantly according to EN54‑2 if more than 512 detection points are connected in the sub-
loop.
This restriction does not apply in an Ethernet sub-loop, as the switches to connect the 2
loops perform the redundancy.
Additional settings
You must operate the central loop as the backbone. This central loop must be networked via
Ethernet.
Notice!
For all RSTP switches in the backbone, set a higher RSTP priority than in the sub-loops. This
ensures that the RSTP root bridge will always remain in the backbone, even in the event of a
fault.
The RSTP switches to connect the loops are part of the backbone!
Use a RSTP priority of 16384 in the backbone.
Notice!
The lower the set value, the higher the RSTP priority.
To Next Page
Loading...
Need help?
General
