he firmware upgrade is automated by the Ruckus SZ code to limit the
impact to your running network. You really do not have control over
which node is upgraded first.
can upload and start the upgrade from any node on a multinode network.
The "single pane of glass" GUI management means that the GUI page
represents and controls all nodes in the cluster with only the exception
of specific network configurations and some diagnostic scripts.
node will decide to be the leader node. This is just for time
synchronization so that all nodes and AP's are synchronized to the same
time. The leader node also makes sure that data is written to the data
base in a consistent manner, preventing two nodes from writing data at
the same time.
(it changes slightly with newer versions) - the Leader node will
upgrade one Follower node at a time. That node will reboot and become
leader. Newer versions of code will upload the firmware to all nodes
simultaneous (for 3 or 4 node systems) but still only one node will be
upgraded at a time.
will automatically connect to the upgraded node and continue
operating. AP' will only upgrade when you configure the AP zone to use
the new version. When the AP's upgrade then there will be a short
outage on the AP as it reboots with the new code.
just go the the WEB-UI of either node, Administration::Upgrade, upload
the correct version of code for your platform and let the built in
intelligence handle the upgrade. Always check the release notes for the
new version of code before starting to check for version compatibility
and supported AP's..
For more information please see the Knowledge Base Article:
vSCG: Cluster Upgrade
We can upgrade multiple vSCG instances in a cluster
I hope this information is helpful
Thanks for choosing Ruckus Networks - a Commscope Company.