Fieldbus & Industrial Networking


FRNT0, layer 2 network redundancy protocol

May 2006 Fieldbus & Industrial Networking

The Westermo On Time industrial managed switch series is available with redundant ring technology. This eliminates network failure caused by fibre or copper failures on the trunk ports (ring ports). The speed of ring recovery is an essential part of designing a network. The Westermo OnTime FRNT (fast re-configuration of network topology) version 0 protocol can recover from a failure in only 20 ms if such a failure does occur. When used in conjunction with redundant power supplies a very reliable system can be designed.

Standard Ethernet networks would collapse and fail if normal office-based Ethernet switches were formed into a complete ring. This failure is commonly referred to as a 'broadcast storm' as Ethernet Packets have multiple routes on a network to communicate to devices. Usually, an incorrect type of packet broadcasts (or floods) over a network and causes hosts to respond all at once, typically with wrong responses. This starts the process over and over again; hence the network crashes.

The FRNT0 is similar to the IEEE Spanning Tree Protocol (STP) except for the following: each switch in a ring topology has knowledge of the network topology, see Figure 1, ie, not only to its neighbouring switches as is the case for STP.

Figure 1
Figure 1

Event-based principle

An FRNT topology change event packet will be sent directly to the focal point switch in case of a topology change (eg, a link loss or a link establishment), while a STP implementation will only send STP control packets one network hop. The focal point switch will, based on the received topology change event packet from the topology change detecting switches, generate a topology change command. This packet is sent to each member switch in the ring. The time it takes from the occurrence of a topology change until the corresponding topology change event packet is received on the focal point is typically a fraction of a ms or a few ms at the most, even though the number of the switches in the ring is high.

200 switches in a ring

The FRNT0 concept contains in principle no limitation for the maximum number of FRNT0 enabled switches that can be installed in a single ring. The maximum number has been set to 200 switches.

20 ms re-configuration time

A large number of switches in a ring have only a small impact on the re-configuration time of the network topology. Example: 100 switches on the path between the topology change detecting switch and the focal point with a very high network load on the links (eg, 50% of full wire speed).

The switch latency in the no load scenario is 15 microseconds (µs), while a conservative estimate in case of 50% load is 70 microseconds (µs). This gives 3 ms round trip propagation delay in a no load scenario and 14 ms round trip propagation delay in the (conservative) high load scenario.

The most time consuming part in case of a topology change is MAC table update procedure. The MAC tables on each switch must be updated in case of a topology change. This operation takes approximately 10 ms. This gives a re-configuration time of approximately 20 ms.

Connection oriented protocol

The member to focal point communication is based on a connection oriented protocol. This means that the protocol will handle packet loss of FRNT control packets. Packet loss is very unlikely in a normal scenario due to the excellent bit error rate (BER) properties of wired Ethernet (copper or fibre), ie, BER should be better than 10-11. However, one must be able to handle a situation where a trunk link might suffer from poor BER with packet loss as a result. This connection oriented protocol is very fast. An FRNT control packet, generated by the member, will be re-sent after 30 ms if no acknowledgement is received from the focal point.

Full immunity vs any type of network load

The loss of FRNT packets due to a network overload situation is not an issue for the FRNT0 control protocol. Thus, any unicast-, multicast- or broadcast network load can be generated on the network without any FRNT0 packet loss. An overload situation in this context means that the interface to the switch CPU is a network bottleneck, ie, important control packets must compete vs other packet to the CPU. Broadcast load is for all practical purposes the most critical network load in this context. The FRNT0 protocol is, however, protected against such an overload scenario due to the following properties:

* Broadcast bandwidth limitation.

* Unique VLAN configuration for the FRNT control packets.

* FRNT packets defined as packet with highest possible QoS level.

Similar proprietary network redundant protocols from other vendors are in most cases based on polling instead of event controlled handling of a topology change. This will introduce a slower establishment of a new topology. The FRNT0 protocol is also based on polling as a supplementary function to the event-based part of the protocol. This function has only relevance in case of a multiple point of failure (single point of failure is handled by the of event controlled handling of a topology change).

Link qualification based on data link layer protocol, LHP

A major problem with most network redundancy protocols is the probability for having a network loop where a potential storm can be generated only in one direction (not both directions), and where this is not detected by the root (master) switch. This problem can only be handled if the switches support a link layer protocol that is used in order to qualify a link. The FRNT0 protocol has support for such a protocol. This Westermo OnTime protocol is referred to as the Link Health Protocol (LHP). The LHP makes sure that packets can be both sent and received on a trunk port before the link is properly qualified. This protocol is mandatory if the trunk ports are based on fibre.

FRNT0 main properties

* Event-based principle.

* 200 switches in a ring.

* 20 ms re-configuration time.

* Connection oriented protocol.

*p Full immunity vs any type of network load (uni- multi- and broadcast).

* Link qualification based on data link layer protocol, LHP.

For more information contact Throughput Technologies, 011 705 2497, [email protected]



Credit(s)



Share this article:
Share via emailShare via LinkedInPrint this page

Further reading:

EtherCAT interoperability removes industrial networking barriers
Fieldbus & Industrial Networking
Selecting the right communication technology is one of the most important decisions engineers make, and interoperability helps with that decision. Key development tools and standards ensure interoperability among many EtherCAT devices and manufacturers.

Read more...
Condition monitoring to go
Turck Banner Southern Africa Fieldbus & Industrial Networking
Anyone who wants to efficiently monitor the climate in control cabinets will find a comprehensive range of control cabinet monitors for the DIN rail in Turck Banner’s cabinet condition monitoring family.

Read more...
Affordable building management system product range
Fieldbus & Industrial Networking
Schneider Electric has unveiled its EasyLogic Building Management System range, designed for basic building architectures, to the local marketplace. This is a complete and cost-effective range of field controllers and sensors that are both easy to install and scalable.

Read more...
Flexible EtherCAT communication interface for DALI-2
Beckhoff Automation Fieldbus & Industrial Networking
The EL6821 EtherCAT Terminal from Beckhoff allows up to 64 DALI/DALI-2 slaves and 64 DALI-2 input devices to be connected. The TwinCAT 3 System Manager makes it easy to configure and parameterise DALI devices flexibly.

Read more...
EtherCAT-based control technology for building automation
Beckhoff Automation Fieldbus & Industrial Networking
Modern non-residential buildings place many high demands on building automation. This can be optimally implemented with EtherCAT-based control technology from Beckhoff, which provides an efficient central automation architecture thanks to ultra-fast data communication.

Read more...
PC-based control for university studies
Beckhoff Automation Fieldbus & Industrial Networking
The IDEA box developed at Heilbronn University of Applied Sciences is designed to introduce students to the topic of Industry 4.0 in a simple and practical way. At the core of the corresponding demo case is PC-based control from Beckhoff.

Read more...
A new standard in high-speed Ethernet communication
Fieldbus & Industrial Networking
The TXMC897 module from TEWS Technologies supports a range of Ethernet standards and speeds, making it suitable for diverse applications, including the defence, industrial, and IIoT markets.

Read more...
Data-driven battery production
Turck Banner Southern Africa Fieldbus & Industrial Networking
The availability of high-performance batteries at moderate prices is one of the most important factors for the success of electromobility. As a long-standing automation partner to the automotive industry, Turck Banner supports the major battery manufacturers with its know-how.

Read more...
Bring critical temperature data to your condition monitoring system
Turck Banner Southern Africa Fieldbus & Industrial Networking
Data conversion just got easier. Turck Banner converters are compact, simple add-ons that seamlessly fit into your factory applications. You can take various types of signals such as discrete, analogue and many others, and convert them to protocols like IO-link, PICK-IQ, PWM/PFM, and Modbus.

Read more...
Case History 190: Measurement problem ruins level control.
Michael Brown Control Engineering Editor's Choice Fieldbus & Industrial Networking
The widely held belief in many plants that tuning will solve all base layer control problems is completely fallacious. Bad tuning is generally not the main reason for loops to perform badly. It is important when performing optimisation that all elements in a loop are considered, in addition to the control strategy, before even thinking of tuning.

Read more...