# Connecting new redundant gateway to EAM **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [August 16, 2024, 4:04pm UTC](https://forum.inductiveautomation.com/t/connecting-new-redundant-gateway-to-eam/94757 "2024-08-16T16:04:37Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![hw79](https://avatars.discourse-cdn.com/v4/letter/h/838e76/32.png) [@hw79](https://forum.inductiveautomation.com/u/hw79)\ **Post date:** [August 16, 2024, 4:04pm UTC](https://forum.inductiveautomation.com/t/connecting-new-redundant-gateway-to-eam/94757/1 "2024-08-16T16:04:37Z")
We have our redundant connected to the master and it's synced and warm. I can see it in the EAM but is showing disconnected. When I try to set up an outgoing connection in the redundant, I can't because it's set as a backup. Does the master gateway push the EAM connection to the backup or do I need to setup the backup's outgoing connection to the EAM before connecting it to the master? ---
**Author:** ![hw79](https://avatars.discourse-cdn.com/v4/letter/h/838e76/32.png) [@hw79](https://forum.inductiveautomation.com/u/hw79)\ **Post date:** [August 16, 2024, 6:00pm UTC](https://forum.inductiveautomation.com/t/connecting-new-redundant-gateway-to-eam/94757/2 "2024-08-16T18:00:07Z")
We've figured it out. 1. Disconnect the Independent Gateway from the EAM 2. Configure the Independent Gateway's redundancy settings to Master 3. Configure the Backup Gateway's redundancy settings to Backup 4. Pair the Master with the new Backup Gateway and approve the connection and certificate on the Master 5. The Backup should synchronize with the Master and will likely restart the service. 6. Connect the Master Gateway to the EAM and approved the connection and certificate on the EAM. 7. After the Master Gateway is connected the EAM will receive an incoming connection request from the Backup. 8. Approve the connection and certificate for the Backup Gateway on the EAM. note: I could not find how to connect a redundant pair to the EAM in the documentation. ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [August 16, 2024, 6:10pm UTC](https://forum.inductiveautomation.com/t/connecting-new-redundant-gateway-to-eam/94757/3 "2024-08-16T18:10:27Z")
@hw79, I'm glad you got it sorted out. I was just compiling some information surrounding ticket IGN-7273 that we have in our system regarding transitioning an existing EAM Agent gateway to a redundant configuration. Currently, there are some manual steps required for this, namely removing the existing EAM Agent configuration from the controller and approving both the new `-master` and `-backup` suffixed agent entries you'll see appearing from the redundant gateway. Basically equivalent to the corrective actions you described. 👍 In the future, we're going to have that aspect of EAM Agent registration (upon transitioning to a redundant pair) happen more gracefully and automatically. Just to clarify a couple other points for others visiting this thread in the future: - Transitioning the soon-to-be-backup gateway from _Independent_ -\> _Backup_ redundancy role will initiate an outbound connection to the defined _Master_ gateway. - Once that gateway network connection is approved on the _Master_ gateway, redundancy will hook up and things will synchronize. Among those things are the EAM agent settings, pointing to the same controller. - The outgoing GAN connections will sync over to the _Backup_, and as such, you'll see a new incoming connection from the _Backup_ gateway on your controller--this needs to be approved before the EAM Agent registration will appear. - This is where the workaround above might be required, you may need to first delete the existing _Independent_ EAM Agent registration now that that gateway is configured as _Master_ role in redundancy. Then re-approve the `xxxx-Master` EAM Agent registration. - Finally, approve the new `xxxx-Backup` EAM Agent registration once you're up and running. ---
**Author:** ![James\_Caudle](https://avatars.discourse-cdn.com/v4/letter/j/5f9b8f/32.png) [@James\_Caudle](https://forum.inductiveautomation.com/u/James_Caudle)\ **Post date:** [October 17, 2025, 10:32am UTC](https://forum.inductiveautomation.com/t/connecting-new-redundant-gateway-to-eam/94757/4 "2025-10-17T10:32:05Z")
Has there been any progress on this EAM issue? ---
**Author:** ![kcollins](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kcollins/32/19646_2.png) [@kcollins](https://forum.inductiveautomation.com/u/kcollins)\ **Post date:** [October 17, 2025, 2:19pm UTC](https://forum.inductiveautomation.com/t/connecting-new-redundant-gateway-to-eam/94757/5 "2025-10-17T14:19:18Z")
The ticket IGN-7273 (titled "EAM: Changing an agent to use redundancy causes an orphaned non-redundancy agent") is still open in our system--at the moment, unless other efforts have improved this situation, you may still need to perform some additional steps (that I outlined above) to transition an agent to a redundant configuration.