Recently added item(s) ×

You have no items in your shopping cart.

Fastest Industrial Network Redundancy

For many years, RSTP (Rapid Spanning Tree Protocol) has been widely used across the networking industry to prevent loops on Ethernet networks. RSTP may require around 10 seconds to rectify the cause of disruption. In comparison, Moxa’s network recovery technologies, Turbo Ring and Turbo Chain, can redirect to the backup path in less than 20 ms. For mission-critical applications, Moxa's technologies are extremely beneficial because they help avoid downtime and allow data to be continually passed along the network even when there is an interruption.

Packet Type Protocol Recovery Time
Unicast / Broadcast RSTP Around 20 seconds
Turbo Ring/Chain Less than 50 ms
Multicast with IGMP snooping RSTP Up to 125 seconds
Multicast fast recovery Less than 20 ms

Turbo Ring:

Turbo Ring is a proprietary self-healing technology for industrial Ethernet backbone with following benefits.

  • Fastest self-healing < 20 ms
  • Flexible Ring topologies, Ring Coupling, Dual-Ring and Dual Homing
  • Lower total cost of ownership

Ring Coupling helps you separate distributed devices into different smaller redundant rings, without any control line, but in such a way that the smaller rings at different remote sites will be able to communicate with each other.

Dual-Homing involves coupling two separate rings with a single EDS switch connecting to two independent connection points. The back-up path will be activated if the operating connection (or main path) fails.

Dual-Ring adds reliability by using a single EDS switch to connect two separate rings for applications that present cabling difficulties.

Turbo Chain:

A highly flexible self-healing Ethernet technology designed for distributed and complex industrial networks with following benefits.

  • Flexible, unlimited redundant network expansions
  • Directly interoperate with Turbo Ring or other redundant protocols, such as RSTP, STP or another Turbo Chain.
  • Cost-effective deployment compared with traditional redundancy topology
tutorials_Redundancy1.gif