Filter
Top Products
Rolling-reboot firmware upgrade
Page 44 | How to Configure and Use AMF on Allied Telesis Switches
Rolling-reboot firmware upgrade
The Rolling-reboot firmware upgrade feature allows nodes within an AMF network to be
rebooted and upgraded in a rolling sequence in order to minimize downtime and reduce the
management overhead. First specify a set of nodes within the AMF network using the
working-set command, then use the atmf rolling-reboot command so all nodes in the
specified working-set will be rebooted and upgraded one by one starting with the nodes
furthest from the core domain, and ending with nodes closest to or in the core domain.
Once the rebooted node has finished running its configuration and has brought its ports up it
re-joins the AMF network and the next node in the working-set is rebooted and upgraded.
Note: The atmf rolling-reboot command can also be used to reboot a set of nodes
without upgrading the firmware.
To upgrade firmware, a download URL can be selected from any media location.
Supported media locations include:
flash:
card:
usb:
tftp:
scp:
http:
The latest compatible release for a node will be selected from this location. Several checks
are performed to ensure the upgrade will succeed. This includes checking the current node
release boots from Flash and that there is enough space in Flash on this node. The new
release name is updated using the boot system <release-name> command. The old
release will become the backup release file.
Note: If the release file is to be copied from a remote location (e.g. via TFTP, HTTP, etc.),
then the URL should specify the exact release filename without using wild card
characters.
The node is rebooted and the new software version will be used. On boot up, the software
release is verified. Should an upgrade fail, the upgrading unit will fail back to old software. At
the completion of this command, a report is run showing the release upgrade status of each
node.
Supported units include SBx8100, SBx908, x900, x610, and x510.
The force command enforces a node reboot, even though the node may not be suitable for
upgrading software. This command can take a significant amount of time to complete.
Note: Rolling reboot firmware upgrades can be performed on a working-set which includes
the controlling node, although in this instance the user will not be presented with a
summary report upon completion.