Upgrading Affinity systems avoiding RSYNC on the private network
If your Affinity has a slow or intermittent network connection, there is a possibility of problems occurring during a firmware upgrade. In rare cases, the system can potentially become unusable when an upgrade takes a significantly long time or is interrupted. To guard against this, it is possible to download a mirror copy of the firmware onto the file-system of the Affinity itself. It can then upgrade itself using this copy as the upgrade source. The process is essentially identical to using a local mirror site with the exception that it uses the device itself as its own mirror server.
The easiest way to do this is using rsync (see the Upgrading Platinum Systems With Unreliable Internet Connections page) but these instructions are specifically aimed at applications where rsync is to be avoided on the private network. Instead, tar and ssh are used to transfer a firmware image to the target NAM using a technique known as a tar-pipe. The source of the image to be transferred can be built using rsync or acquired directly from Güralp Systems on a USB stick.
The target Affinity must have access to the network while the tarpipe is running but it does not need network access while it is actually upgrading. If the download process is interrupted, it can be easily restarted. The operation of the target Affinity is not affected during the download (other than by creating a bandwidth requirement) so this process can safely be repeated until it has completed successfully.
Platinum systems use the rsync protocol to update their firmware to the latest revision. rsync is an extraordinarily flexible tool but it can be rather complex. The upgrade script on the Affinity is a front-end to rsync which is used to hide this complexity and ensure the safe use of the protocol. The source for the rsync transfer is normally the Güralp rsync server; in this instance, it will be a local image in the target device's file-system: i.e. the device will function as its own mirror server. In this way, while the rsync protocol is still used, it is not used over the network.
Upgrading a Platinum system using itself as its own upgrade mirror involves five steps:
- Acquiring the mirror content;
- Transferring the mirror content to the target Affinity;
- Setting up the Affinity as a local rsync server;
- Configuring the Affinity to use itself as its upgrade server; and
- Performing the upgrade.
The procedure is slightly different for systems with different architectures so the instructions have been split into three. This page only covers Affinity systems. If you are attempting to upgrade a DM24SxEAM, a *TDE instrument or an MkⅡ NAM, please select one of the links below:
Acquiring the mirror content
The mirror content must first be transferred to a Linux PC or server. (Windows file-systems do not support the necessary file attributes.) If the Linux server can be connected to the Internet, commands similar to those below can be used to acquire a copy of the firmware.
If, instead, the image has been delivered on a USB stick, mount the stick on, say, /mnt and enter commands like these:
The server created in this step will be referred to as scphost in the commands below. You should substitute the appropriate DNS name or IP address in each command where you encounter this.
Problems?
The most common problems experienced at this stage are:
rsync reports “Temporary failure in name resolution”
If you see error messages like
it means that the Domain Name Service (DNS) client is misconfigured. If you are running DHCP, this may be a problem with your DHCP server not providing the address of a nameserver (or providing an incorrect one). If you are using static addressing, check and correct the nameserver using the net-setup tool.
rsync reports “Network is unreachable”
If you see error messages like
it means that the network routing is misconfigured. If you are running DHCP, this may be a problem with your DHCP server not providing a default route (or providing an incorrect one). If you are using static addressing, check and correct the default route using the net-setup tool.
rsync reports “rsync error”
If you see error messages like
it means that, most probably, a firewall is blocking traffic on the rsync port. Ask your network administrator to permit the Linux PC to open TCP connections to host rsync.guralp.com on port 873.
Transferring the mirror content to the target Affinity
The mirror content occupies a significant amount of disk space, so it is important to check the available space before proceeding. To check the space available, log on to the command line of your target system and type the command
The output consists of a table with several lines of content, such as:
Look for the row where the value in the Mounted on column is /, as highlighted in the example above, where the available space is 212.5 MB.
These systems require around 110 MB of free space to store the upgrade image. Only proceed if you have enough space.
You can either push the content from scphost to the target Affinity or, working on the Affinity, pull the content from scphost. The two steps are equivalent but your firewall rules or network infrastructure may make one option easier than the other.
Pushing the content
We will call the target Affinity target in the commands that follow. Replace target with the IP address or DNS name of your system.
From the command line of the scphost, enter the following command sequence to upload the mirror content:
Pulling the content
From the command line of the target Affinity, enter the following command sequence to download the mirror content, replacing scphost with the IP address or DNS name of your scp host:
Problems?
The most common problems experienced at this stage are:
scp or ssh reports “Name or service not known”
If you see error messages like
this means that the Domain Name Service (DNS) client is misconfigured. If you are running DHCP, this may be a problem with your DHCP server not providing the address of a nameserver (or providing an incorrect one). If you are using static addressing, check and correct the nameserver using the net-setup tool.
In the last resort, replace the DNS name of the server with its IP address.
scp or ssh reports “Network is unreachable”
If you see error messages like
this means that the network routing is misconfigured. If you are running DHCP, this may be a problem with your DHCP server not providing a default route (or providing an incorrect one). If you are using static addressing, check and correct the default route using the net-setup tool on the target system or the ip route command on the scphost.
scp or ssh reports “Connection refused”
If you see error messages like
this means that the ssh server is not configured correctly on the target system or on the scphost. Review the server settings or contact for assistance.
Setting up the target Affinity as an rsync server
The target Affinity's rsync server is configured by creating the file /etc/rsyncd.conf using the following commands:
Once the /etc/rsyncd.conf file is in place, you should start the rsync server with the command
Configuring the target system to use its local server
Create the file /etc/conf.d/upgrade.local using the following commands:
Perform the upgrade
The Affinity can now be upgraded by using the upgrade command. Once the upgrade has completed successfully, the system should be rebooted, either by using the web interface or, from the command-line, with the command reboot
For more information, first contact your local distributor or email .