Description

Learn how to setup a two node Redundancy in Ignition. The nodes will be assigned as Master and Backup, and only one will be active at any time.

Video recorded using: Ignition 7.9

Transcript

(open in window)

[00:00] When setting up redundancy you need to have two separate gateway systems. You'll notice I have two of them up here. One's installed locally and one's installed on a remote machine. You then need to decide which gateway you want to be the master and which one you want to be the backup. Cause the backup system will take a backup of the master and restore it onto itself. I want this gateway to be the master. So I'm going to go ahead and go into the configure section here and go down to the redundancy page. On this first setting, mode, determines what type of gateway this is going to be. Right now it's set to independent, which means that there is no redundancy and this gateway runs completely by itself. There's also the backup and the master setting. I'm going to set this to master.

[00:59] Next, there's a standby activity level. Which can either be set to cold or warm. This determines at what level the backup gateway runs at. If it is a cold backup, it will reduce the number of operations and connections it has to minimize performance load on the backup server. If it's a warm backup, it will run at full capacity, reducing fail over time but increasing the load on the backup server. I'll leave mine at cold. Next, these two settings determine the amount of time before the backup node takes over and a fail over happens. Then we go onto network settings. First we determine the port that the redundancy is going to be use. By default it's 8750. But you can change this to be whatever you would like. As long as it's not being blocked by a firewall. Next we're going to determine which IP address' we want to use and we want the clients to connect to.

[02:01] By default both of these are set to auto detect. But if you have multiple network interface cards, might be a good idea to hard code these in. Finally we have the master node settings. First, we have the recovery mode. Recovery mode can be either automatic or manual. Automatic means that as soon as the master comes back online it will automatically take over from the backup. Whereas manual, will wait for you to force it to fail back to the master before it takes over. When redundancy is fully set up, the master will send small updates to the backup as they're made on the master system. This run time update buffer size determines how many of those small updates get sent and cued up before a full state transfer will occur and the backup will restore a full system backup. Finally you can set up a connection white list where the master system will only accept incoming backup connections from certain IP addresses.

[03:01] It's not necessary for me, so I'll go ahead and move on. These backup node settings are important. They're only going to be setup on the backup node. I'll go over them later. Now we're going to hit save changes. Now that this is finished, I'm going to the status section. And see that redundancy has been set up and it notices that it's missing a backup node. So let's go ahead and set that up. Let's go to our backup gateway. Go into the configure section. Go down to the redundancy page. For this mode we're going to set it to be backup. We want it to be a cold backup. And we're going to leave all these network settings the same as the master. Since this is the backup, we don't need to setup the master node settings. And so here on the backup node settings, the first setting is the master node address.

[04:02] Which is the IP address of the master system. I'm going to go ahead and enter mine. These settings determine how often the backup and master are going to be communicating with each other. And finally history mode. With history mode you can have it either be full or partial. Full history mode means the backup will start storing history as soon as it takes over, whereas partial history mode means that the backup will start storing history but it will cache it until it's able to confirm when the master went down. I'll leave that set the way it is. Finally we're going to hit save changes. Go ahead and confirm. Now that it's done we're going to go ahead and go up to our status section. You'll notice now that this gateway is our backup gateway. It's connected to our master and it's not just saying that it's out of date. Meaning that it's not the same as the master gateway. So it's going to do a full state transfer and copy the settings and projects of the master gateway so that they're the same.

You are editing this transcript.

Make any corrections to improve this transcript. We'll review any changes before posting them.