Mirrors
/
ARDEN-documentation
mirror of https://github.com/aredn/documentation.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update Screenshot Release Number 

Update the release on several screenshots that were overlooked.
This commit is contained in:
Steve Lewis AB7PA 2021-04-12 20:02:44 -07:00 committed by Joe AE6XE
parent c9aea31212
commit ba4f98825f
5 changed files with 6 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
arednGettingStarted/_images/01-setup-nocall.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 95 KiB

After

Width:  |  Height:  |  Size: 95 KiB

BIN
arednGettingStarted/_images/03-node-status.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 89 KiB

After

Width:  |  Height:  |  Size: 88 KiB

BIN
arednGettingStarted/_images/09-admin-upgrade.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 67 KiB

After

Width:  |  Height:  |  Size: 67 KiB

BIN
arednGettingStarted/_images/aam-display.png
View File

Binary file not shown.
Side by Side Swipe Overlay

Before

Width:  |  Height:  |  Size: 35 KiB

After

Width:  |  Height:  |  Size: 35 KiB

15
arednHow-toGuides/firmware_upgrade.rst
View File

@ -4,29 +4,26 @@ Firmware Upgrade Tips
Upgrading an AREDN |trade| node is a straightforward process accomplished using the *Setup > Administration > Firmware Update* feature on the node's web interface. Follow the procedures documented in the **Downloading AREDN Firmware** section to ensure you have the correct firmware version from the AREDN |trade| website to install on your node
The newest firmware versions have a built-in check to verify that the firmware image you selected is appropriate for the device on which you are installing it. Earlier firmware versions (3.16.1.x and 3.18.9.0) do not have these checks, so be sure you selected the correct firmware version for your device before starting the upgrade.
The newest firmware versions have a built-in check to verify that the firmware image you selected is appropriate for the device on which you are installing it. Early firmware versions (3.16.1.x and 3.18.9.0) do not have these checks, so be sure you selected the correct firmware version for your device before starting the upgrade.
Here are some "best practice" tips to assist with the firmware upgrade process. These ensure that memory utilization is at its minimum on the node. The upgrade process can fail due to lack of memory, but such a failure will leave the node unchanged on its previous firmware version.
Use a stepped approach to firmware upgrades
For example, if your node is running version 3.18.9.0 you may want to upgrade to version 3.19.3.0 before attempting to apply a newer version.
Here are some "best practice" tips to assist with the firmware upgrade process. These ensure that memory utilization is at its minimum on the node. The upgrade process can fail due to lack of memory, but such a failure will leave the node running its previous firmware version.
Clear the web browser cache
When using a web browser to perform an upgrade, be sure to clear the browser's cache to remove any cached pages remaining from your node's previous firmware version. A clear cache will help to eliminate confusion when displaying node data in the browser.
Release node resources
Before starting the firmware upgrade, it may be necessary to stop, disable, or uninstall extra packages such as Meshchat, snmp, and tunneling. The goal of this step is to keep those processes from using RAM memory and to free as much RAM as possible before the upgrade. Rebooting the node will ensure that its RAM utilization is at a minimum.
Before starting the firmware upgrade, it may be necessary to stop, disable, or uninstall extra packages such as Meshchat, snmp, and tunneling. The goal of this step is to keep those processes from using RAM memory and to free as much RAM as possible before the upgrade. Rebooting the node before beginning the upgrade will ensure that RAM utilization is at a minimum.
You may also want to stop node programs or services that are not needed during the upgrade. For example, if you can telnet or ssh to the node and type the command ``wifi down`` you can free the memory used by this driver.
You may also want to stop node programs or services that are not needed during the upgrade. For example, you can telnet or ssh to the node and type the command ``wifi down`` to free the memory used by this driver.
Tips for legacy nodes with low memory (32mb)
Legacy equipment with only 32mb of memory will become more difficult to upgrade as the footprint of firmware images continues to grow. Be sure not to use these types of devices at sites which are difficult to access. The sysupgrade process needs around 10mb of free memory to succeed.
Legacy equipment with only 32mb of memory may require more effort to upgrade as the footprint of firmware images continues to grow. Be sure not to use these types of devices at sites which are difficult to access. The sysupgrade process needs around 10mb of free memory to succeed.
* You may need to try the sysupgrade procedure several times before it succeeds. Be patient and keep trying.
* Get everything ready to do the upgrade, then do a fresh reboot of the node and immediately start the sysupgrade process before the node has time to initialize services which use memory.
* Use command line access to copy the *sysupgrade.bin* image to the /tmp directory on the node, then run the sysupgrade process manually from the command line on the node. Note that AREDN |trade| nodes use port 2222 for secure copy/shell access.
* Use command line access to copy the *sysupgrade.bin* image to the /tmp directory on the node, then run the sysupgrade process manually from the command line on the node. Note that AREDN |trade| nodes use port 2222 for secure copy and secure shell access.
Execute the following commands from a Linux computer: