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
effect 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
C. Cause a failover to occur
Now, connect to the active unit (which is still running the old NetDefendOS version) with a CLI
11.5. Upgrading an HA Cluster
Chapter 11. High Availability
500
Summary of Contents for NetDefend DFL-260E
Page 27: ...1 3 NetDefendOS State Engine Packet Flow Chapter 1 NetDefendOS Overview 27...
Page 79: ...2 7 3 Restore to Factory Defaults Chapter 2 Management and Maintenance 79...
Page 146: ...3 9 DNS Chapter 3 Fundamentals 146...
Page 227: ...4 7 5 Advanced Settings for Transparent Mode Chapter 4 Routing 227...
Page 241: ...5 4 IP Pools Chapter 5 DHCP Services 241...
Page 339: ...6 7 Blacklisting Hosts and Networks Chapter 6 Security Mechanisms 339...
Page 360: ...7 4 7 SAT and FwdFast Rules Chapter 7 Address Translation 360...
Page 382: ...8 3 Customizing HTML Pages Chapter 8 User Authentication 382...
Page 386: ...The TLS ALG 9 1 5 The TLS Alternative for VPN Chapter 9 VPN 386...
Page 439: ...Figure 9 3 PPTP Client Usage 9 5 4 PPTP L2TP Clients Chapter 9 VPN 439...
Page 450: ...9 7 6 Specific Symptoms Chapter 9 VPN 450...
Page 488: ...10 4 6 Setting Up SLB_SAT Rules Chapter 10 Traffic Management 488...
Page 503: ...11 6 HA Advanced Settings Chapter 11 High Availability 503...
Page 510: ...12 3 5 Limitations Chapter 12 ZoneDefense 510...
Page 533: ...13 9 Miscellaneous Settings Chapter 13 Advanced Settings 533...