# Redundant GW and redundant PLC with kepserver - failover opc

**URL:** <https://forum.inductiveautomation.com/t/redundant-gw-and-redundant-plc-with-kepserver-failover-opc/9628>\
**Category:** Ignition\
**Created:** [January 31, 2015, 2:38pm UTC](https://forum.inductiveautomation.com/t/redundant-gw-and-redundant-plc-with-kepserver-failover-opc/9628 "2015-01-31T14:38:58Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [February 2, 2015, 7:34pm UTC](https://forum.inductiveautomation.com/t/redundant-gw-and-redundant-plc-with-kepserver-failover-opc/9628/7 "2015-02-02T19:34:54Z")

</div>

I use kepserver media level redundancy feature to manage connection to redundant PLC  
From Ignition point of view, only one device with no script.  
Main problem is to force master and backup gw to use the kepserver of the master to avoid 2 connection to the same redundant PLC, ie one from the master kepserver and one frsecond.backup kepserver  
So I posted a Feature Request, you can vote for it.  
[ideas.inductiveautomation.com/fo … connection](http://ideas.inductiveautomation.com/forums/255378-ignition-features-and-ideas/suggestions/7034578-driving-failover-mode-for-opc-connection)

---

_[View the full topic](https://forum.inductiveautomation.com/t/redundant-gw-and-redundant-plc-with-kepserver-failover-opc/9628)._