First things first, back up your current configs on the NetScaler's in question, my guide to this is here:
N.b* - if you are upgrading due to a memory leak issue, you are best to reboot both NetScaler’s (one at a time), to make sure all changes are committed to the current configurations.
Once completed the NetScaler’s should be upgraded as
follows:
To avoid issues with an updated NetScaler participating in
HA from automatically taking over the primary role, and subsequently updating
the (now) secondary Node do the following first:
- Test as many different
types of connection as possible, to confirm good working order before you
begin.
- On the secondary node go
to system\high availability and open the secondary node, select stay
secondary in the HA Status, also De-select secondary node will fetch the
config from the primary & Primary node will propagate configuration to
the secondary.
- Once this is done save the
config, and then update the secondary NetScaler.
- Once complete, cold boot
the secondary NetScaler.
- When you are happy the
secondary node has come back to life and everything look as it should,
force a failover to make the secondary NetScaler primary.
- Make sure you set the now
secondary NetScaler with the same above options……..
- Test all the same
connections that were checked as above, confirming these are still working
soundly.
- Now upgrade the secondary
node of the NetScaler, once complete, force the failover, change HA
settings back to enabled in HA, and both other check boxes selected.
- If this has been done
correctly, the NetScaler’s are upgraded!
hopefully an easy, straightforward guide to updating your NetScaler's and keeping the powers that be off your case!
Haines
Haines
No comments:
Post a Comment