Created on ‎11-06-2008 06:19 AM
Created on ‎11-10-2008 08:22 AM
Created on ‎11-11-2008 04:31 AM
Created on ‎11-25-2008 08:21 AM
1- Isolate Master unit (running older firmware) physically from your network (unplug all network cables from internal and external switches and the heartbeat interface) 2 - Connect a laptop to one of the network interface, configure your laptop to match the interface subnet, and access it via GUI. Upgrade the unit from GUI. Make sure that the firmware has been upgraded after the reboot. 3 - Rejoin the Master unit into the network by pluggin all the network cables back in. Both units should sync up again.This worked great. I' ve upgraded my cluster maybe 20 times and it' s always worked as advertised (slave updates, makes itself primary, old primary updates then takes back over from slave). This was the first time it blew up. Great thing is, my users never knew there was a problem.
I have surfed the web while this is happening and experienced no disruption. I do, in most cases attempt to do this during low traffic or preventative maintenance windows, as I do not wish to tempt the techie gods into making my life miserable.I did find one issue and that was with anything that the firewall would issue a certificate for such as SSL VPN connections or user authentication. It will dump that session and the users will have to re-authenticate. At least that' s what I observed.
User | Count |
---|---|
2548 | |
1354 | |
795 | |
646 | |
455 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.