Setting up the outgoing connections on my Edge gateway to my central gateway

Ignition
,
1

Hi team,

I am having trouble setting up the outgoing connection between my edge gateway and my central gateway. Both gateways are using version 8.1.20.

On the central gateway, the edge remote certificate is approved and is being used for outgoing connections from central to edge. I run a backup through the EAM agent tasks every 24 hours which is running fine and when i run the gateway network diagnostics, i’m getting a response from the edge gateway. However, when i look at my incoming connections, the connection is approved but all other columns are N/A or unknown.

On the edge gateway, it is the same. remote certificate is approved and incoming connections all approved and running. My outgoing connections are faulted. Host name has been checked and confirmed to be correct and port 8060 is being used for SSL.

For context, I’m trying to setup an alarm pipeline from my edge gateway to my central gateway and as far as i can tell, this is what is hindering me now.

Any assistance would be greatly appreciated. It feels a little like a firewall issue rather than a gateway config issue, but I just thought I’d make sure I’m doing the right things on Ignition to start with.

thank you

2

You should only need to establish the connection once. After that, communication is bidirectional. I speculate that your fault is related to creating an outbound connection when you already have an inbound connection established with same gateway, but -disclaimer- I have never tried this myself.

I recommend that you always create an outbound connection from the Edge --> Full gateway, and have only inbound connections (from Edge gateways) at your central gateway.

Regarding setting up the remote alarm pipeline, verify that you have correct settings configured for Remote Gateway Name under Config > Data Sync > Settings. IIRC, after you set up Edge sync services correctly, you should be able to pick a remote alarm pipeline on any of your tags. If not, you might be blocked due to Service Security settings on the full gateway.