Hey All,
probably a simple thing, but I'm not seeing how to do it.
I would like to update firmware to my passive HA security appliance, fail over to the update unit, then update the "primary" unit.
I can't seem to find a place in the dashboard that only allows me to update one particular appliance. Any ideas?
Solved! Go to Solution.
When MX appliances configured to operate in High Availability (HA) (either in NAT/routed mode or when operating as one-armed VPN concentrators), the dashboard will automatically take steps to minimize downtime when upgrades are performed to ensure a zero-downtime MX upgrade. This is achieved through the following automated process:
The Primary MX downloads firmware
The Primary MX stops advertising VRRP
The Secondary MX becomes master
The Primary MX reboots
The Primary MX comes online again
The Primary MX starts advertising VRRP again
The Primary MX becomes Master Again
The Secondary MX downloads firmware (approximately 15 minutes after the original upgrade is scheduled)
The Secondary MX stops advertising VRRP
The Secondary MX reboots and comes back online
Keeping up-to-date on firmware allows administrators to utilize the latest features and ensures that the latest security enhancements are running on their hardware. Admins can upgrade to the latest stable or latest beta firmware. Follow the steps below to schedule a firmware upgrade.
Note: When downgrading from a beta firmware to a stable firmware, a feedback request page will be presented. Please select any options that reflect the downgrade reason before selecting Schedule change for network.
So I guess your point is that there is no option to do it this way? if both of my HA units are in the same network and are the same device type, there is no way to specify a specific unit to be updated?
When MX appliances configured to operate in High Availability (HA) (either in NAT/routed mode or when operating as one-armed VPN concentrators), the dashboard will automatically take steps to minimize downtime when upgrades are performed to ensure a zero-downtime MX upgrade. This is achieved through the following automated process:
The Primary MX downloads firmware
The Primary MX stops advertising VRRP
The Secondary MX becomes master
The Primary MX reboots
The Primary MX comes online again
The Primary MX starts advertising VRRP again
The Primary MX becomes Master Again
The Secondary MX downloads firmware (approximately 15 minutes after the original upgrade is scheduled)
The Secondary MX stops advertising VRRP
The Secondary MX reboots and comes back online