I have a project using a redundant EIOC to run an MCC over Ethernet / IP. The EIOC will directly control the devices on the network (PF525 and E300). What would be the best practice for having this network's high availability. We are using the redundant EIOC. One option would be to set up a network redundancy and use a RedBox Switch; however, the Switch would become my network bottleneck. How to get around this situation? What solutions have been adopted for this situation?It is possible to mount a ring with two redBox switches. One from Lan A and one from Lan B?
Thanks.
Elton,
Currently the only network redundancy supported by the EIOC is PRP (Parallel Redundancy Protocol). When this option is chosen, identical messages are sent out both the A and B ports. Both messages are received by the end devices and one of the messages is discarded. In order to do this the EIOC requires that the A and B ports be on different subnets. The end device must be PRP aware, with connections on both A & B subnets. Neither the E300 or PowerFlex are PRP aware so you will not be able to use the current EIOC network redundancy with these devices.
You can set up a ring network, but it will still only operate from the EIOC's Port A. The Port B will be on a different subnet and therefore unable to communicate with your devices. If you have a small number of devices you could add a Redbox to each one to make it PRP aware. This become complex and cost prohibitive if you have a large number of devices.
We currently have an active, large project with hundreds of E300s, Powerflexes and other devices. We need the same type of redundancy that you are looking for - something similar to how network redundancy is handled in the VIMs. We have an active request with Emerson to add this type of redundancy to the EIOC product. No word yet as to timing of when this capability will be added.
In reply to BRENT DREISBACH:
Andre Dicaire
In reply to Andre Dicaire: