11.5. Upgrading an HA Cluster
The NetDefendOS software versions running on the master and slave in an HA cluster should be
the same. When a new NetDefendOS version becomes available and is to be installed on both
units, the upgrade is done one unit at a time.
The central principal in the upgrade process for a cluster is that upgrading the inactive unit will
not affect the operation of the cluster and only momentarily make the inactive unit unavailable.
The overall sequence of steps to follow is:
i.
Identify which unit is inactive and upgrade that first.
ii.
When the inactive unit is once again synchronized with the active unit, cause a failover to
occur so that the inactive becomes the active unit.
iii.
Now upgrade the inactive unit. Both units will then resynchronize and have the new
NetDefendOS version.
These three steps will now be broken down into a more detailed description:
A. Establish which is the inactive unit in the cluster
The currently inactive unit will be upgraded first so it is necessary to identify this. To do this,
connect with a CLI console to one of the cluster units and issue the
ha
command. The typical
output if the unit is active is shown below.
gw-world:/> ha
This device is a HA SLAVE
This device is currently ACTIVE (will forward traffic)
This device has been active: 430697 sec
HA cluster peer is ALIVE
This unit (the slave) is the currently active unit, so the other one (the master) is the inactive unit.
B. Upgrade the inactive unit
Once the inactive unit is identified, upgrade this unit with the new NetDefendOS version. This is
done exactly as though the unit were not in a cluster. For example, the Web Interface can be
used to do the upgrade.
Important: Make sure the inactive unit is ALIVE
Before going to the next step make sure the inactive unit is fully operational and
synchronized with the active unit after the software upgrade completes.
To do this, issue the CLI
ha
command on the inactive unit. The output from the
command should indicate that the status is
ALIVE
.
gw-world:/> ha
This device is a HA SLAVE
This device is currently INACTIVE (won't forward traffic)
This device has been inactive: 2 sec
HA cluster peer is ALIVE
Chapter 11: High Availability
837
Summary of Contents for NetDefendOS
Page 30: ...Figure 1 3 Packet Flow Schematic Part III Chapter 1 NetDefendOS Overview 30 ...
Page 32: ...Chapter 1 NetDefendOS Overview 32 ...
Page 144: ...Chapter 2 Management and Maintenance 144 ...
Page 284: ...Chapter 3 Fundamentals 284 ...
Page 392: ...Chapter 4 Routing 392 ...
Page 419: ... Host 2001 DB8 1 MAC 00 90 12 13 14 15 5 Click OK Chapter 5 DHCP Services 419 ...
Page 420: ...Chapter 5 DHCP Services 420 ...
Page 573: ...Chapter 6 Security Mechanisms 573 ...
Page 607: ...Chapter 7 Address Translation 607 ...
Page 666: ...Chapter 8 User Authentication 666 ...
Page 775: ...Chapter 9 VPN 775 ...
Page 819: ...Chapter 10 Traffic Management 819 ...
Page 842: ...Chapter 11 High Availability 842 ...
Page 866: ...Default Enabled Chapter 13 Advanced Settings 866 ...
Page 879: ...Chapter 13 Advanced Settings 879 ...