You can help by commenting or suggesting your edit directly into the transcript. We'll review any changes before posting them. All comments are completely anonymous. For any comments that need a reply, consider emailing firstname.lastname@example.org.
We are experiencing playback issues from our video hosting provider. Please check back shortly.
Setting Up Redundancy
Learn how to configure Redundancy across two different Ignition Gateways.
Transcript(open in window)
[00:00] In this lesson, we'll take a look at configuring redundancy across two different gateways. In my web browser here, I have two tabs with a separate gateway in each tab. I have beta, which is going to be the backup of the redundant pair, and I have alpha, which is going to be the master. Now, redundancy requires that I make some configuration changes on both gateways here. The order you do this in doesn't matter too much, but for the purposes of this example, I'm going to start with the alpha gateway, or the master gateway. So, on alpha here, I'll head over to the config section, and under the system header, I'll click on redundancy. The property that's ultimately responsible for whether or not a gateway is participating in redundancy is this mode property over here. By default, all Ignition gateways, when they're installed, are set with a mode of independent, which means they're not participating in redundancy at all. So, alpha here needs to be set with a mode of master to make it a master in a redundant pair.
[01:04] So I'll click on the dropdown, and select master. I'll scroll down a little bit more on this page. And I did want to point out that there are master node settings and backup node settings. So these settings are only applied to this gateway, depending on the mode of the gateway. So because I'm going to set alpha as the master, the master node settings would be applied to it. The backup node settings would only be applied if this gateway was set to be a backup. But I'm actually not going to make any other changes. I'm just going to scroll on down and click save changes, and then I'll click confirm. And that's actually all we have to do to set up redundancy on the master gateway. It's pretty straightforward. Let's switch over to beta. I'll go to the config section on beta. Again, I'll go to the redundancy page, and I need to tell this gateway that it should be a backup, so I'll change the mode to backup. Now, in a redundant pair, the backup gateway is the one that's responsible for reaching out to the master. So, I need to tell my backup gateway here where the master is located.
[02:00] So I'll scroll down on this page, and under backup node settings, I need to set the master node address. So in this field, I just need the network address of alpha. So I'll switch over to alpha, and I'm going to actually just copy the IP address here. I'll then switch back, and I'll paste the address into this field. Now, as far as the port goes, you may recognize this port if you've looked through our documentation, but the 80/60 port is the primary port our gateway network feature uses. So, the redundant pair will utilize the gateway network to communicate with each other, which is actually going to come up in just a moment.
[03:13] Now, I don't need to make any other changes here. We can scroll on down, and I'll click save changes. Now, before I click confirm here, now would be a good time to back up any work that's on this gateway that's going to become a backup. When synchronization occurs, this backup gateway here is going to lose all of its unique configuration. So if you've been any projects, or anything that you wanted to save, you would want to take either a project export, or go ahead and just take an entire gateway backup, if there are tags, or other gateway-level configurations you wanted to save, and maybe important into another gateway elsewhere. Now, I don't have to worry about that, so I'll just click confirm. And changing a gateway to a backup does require a little bit of time, so I'll just speed this part up here. All right, so, now this gateway is set to be a backup. Now, how can we verify that this gateway is now a backup? Well, we can head over to status here, and on the overview page, once this page finishes loading its information, we can see that this gateway does have a peer. So if we look at those little boxes there, we can see that this is set as a backup, and it's supposed to have a master, but it can't find the master. For some reason, there's a communication problem. You probably also noticed that there's a gateway network connection problem down below. Well, that's because the two gateways can't talk on the gateway network. So, this is a problem you might run into, naturally, but with any sort of gateway network connection, out of the box, you need to approve connections across different gateways.
[04:05] So when you're setting up redundancy, the backup gateway will make an implicit outgoing connection to the master gateway. So I just need to switch over to alpha here, and under config, I will go to gateway network settings, I'll click on incoming connections, and we can see, there is, in fact, a remote connection that's not approved. So, I'll just go ahead and approve this because I do recognize this connection. I'll confirm this, and there we go. So now it's approved. We can switch over to status here on alpha. And if we give it just a moment, and there we are. We now have our redundancy set up. Now, I'm looking at this page on alpha, or the master, but you'll see a similar page on the backup. Now, if I click on the peer box here, it does take us to the status section on the redundancy page, which has information about the redundant state. Now, you'll notice the peer is no longer connected. That's because the backup initiated a gateway restore. It's restarting itself right now, so that it can inherit all of the configurations from the master, which has to happen initially, just so the backup can become in sync with the master.
[05:04] So if I go over to the beta tab here, I can actually refresh this page. This page is actually out of date now because the gateway is restarting. But if I click reload here in my browser, we can see that the gateway is starting. All right, now that we're back online, you're going to notice this gateway changed its name. This gateway, this backup gateway, is now called alpha. It's still considered a backup, but it inherited all of the other settings from the master gateway, except for the redundancy settings, of course. But that about wraps it up for redundancy. Now, any changes that are made to the master are going to be inherited automatically by the backup. And if the master goes down for any reason, the backup is here, ready to take over.