User Manual

Chapter 11 ● Updating node software
140 Release 2.0, 910056 Rev01d
Understanding the software update process
The process explains how to check the version of the node’s currently executing software release, how to
transfer a new release to the node, and how to reboot the node using the new release.
1. Checking the current release and free disk space
This is optional and may not need to be performed during installation for some nodes. Consult your
network planner.
See Checking the active release and free disk space
on page 140.
2. Transferring the new release to the node
The new release is transferred over the IP/Ethernet connection using FTP.
See Transferring the node software from the laptop to the node
on page 142.
3. Activating the new release
The node is reset using the new release.
See Activating the release
on page 144.
This procedure is complete. This process is complete. Go to Running the commissioning script
on page 145.
Checking the active release and free disk space
This procedure explains how to use the CLI to check the currently active software release on the node, how
to check the amount of free disk space on the node, and how to delete files if more free space is needed
before transferring a new release to the node. It is assumed you have an active CLI session. This procedure is
unnecessary if you are not intending to update the node’s software release version.
Requirements
A CLI/serial connection to the node.
See Establishing CLI connections
on page 131.
NOTE
The node’s software release version can be updated later from a
centralized location using AirVista or CLI/telnet.