If your Affinity systems, EAMs, Platinum DCMs or NAM units only have access to a local network, you can create a local mirror of the Güralp software repository and have your systems use this as the source for firmware upgrades. This procedure requires a machine running Linux to host the mirror repository.
Platinum systems use the rsync protocol to update their firmware to the latest revision. rsync is an extraordinarily flexible tool but can be rather complex. The upgrade script on the EAM is a front-end to rsync which is used to hide this complexity and ensure the safe use of the protocol.
Setting up a mirror involves three steps:
The mirror can occupy a significant amount of disk space, depending on the which architectures you need to support. See the sections for each architecture (below) for the current space requirements. You should pick a disk partition with ample space in which to store your own copy. Start with an empty directory each time. If you wish to make a fresh copy after a new firmware release, remove the old copy first, so that you start in an empty directory. You can keep multiple, simultaneous versions of the firmware if you wish and tell each EAM which version to use when upgrading.
The server on which you create the mirror should have access to the Internet during the download step but does not need Internet access while it is acting as an upgrade server. It does, of course, need to be accessible by your networked EAMs. It is possible to create the mirror content on a removable disk attached to an Internet-connected computer and then move the disk to a different computer when it is to be served.
Create the mirror directory and use the cd command to make it your current directory. Enter one or more of the following command sequences to download the mirror content. Each sequence downloads the files for a particular architecture. If you know, for example, that you will never want to upgrade a NAM64, you can omit the commands for this architecture.
This architecture currently requires around 110MB of disk space for the mirror.
Most EAMs should now be running a firmware build greater than 10,000. For these EAMs, use the latest build, which occupies around 70MB of space. Use the following commands:
For more information about upgrading from builds earlier than 3801 to the latest build, please see the EABI upgrade page.
This architecture currently requires around 94MB of disk space for the mirror.
This architecture currently requires around 50MB of disk space for the mirror.
This architecture currently requires around 94MB of disk space for the mirror.
To configure and run an rsync server, the rsync package must be installed on your Linux PC. Most Linux distributions include this as standard but, if not, consult your distribution documentation for instructions to install this package.
Your local rsync server is configured by creating the file /etc/rsyncd.conf. If the serving host already runs an rsync server, you should modify this file (basically, add an extra module) in order to allow access from the EAMs to the mirror directory and we assume that you have the knowledge to do this without further assistance. This section covers setting up a new, dedicated rsync server.
You will need to choose a TCP port number which will not conflict with another service on your network. The port number should be greater than 1024 in order to avoid additional complexity. Consult your network administrator for an available port or simply try 61616 and, if you get an error saying that the port is in use when you attempt to start the server, choose a different random number in the range 49152 – 65535. 61616 will be used in the following example and should be replaced with the port number you have chosen or been allocated. If there are firewalls between your server and the EAMs, you will need to open TCP channels through them for this port.
You will also need to choose a module name for the server. This can be any descriptive string but, for simplicity, it is best to stick to numbers, lower-case letters and hyphens (-). The name platinum-local-mirror has been used in the following example; This is a perfectly good choice but, if you wish to use somethinge else, it should be replaced in the examples below with the module name you have chosen.
Create the file /etc/rsyncd.conf with the following contents:
Consult the manual page for rsyncd.conf(5) for details of further options you can use in this file, including security improvements that you may wish to put in place.
Once the /etc/rsyncd.conf file is in place, you can start the rsync server with the command
If you want to run the rsync server permanently, it is possible to start it via systemd, inetd, xinetd or an rc script. Consult the manual page for rsyncd.conf(5) for further details.
On each EAM, Affinity, NAM or DCM to be upgraded, create the file
/etc/conf.d/upgrade.local with the following
content:
The units can now be updated from the mirror by using the upgrade command. Note that the files /etc/conf.d/upgrade.local on each unit will not be disturbed by the upgrade process and, so, only need to be created once.
rsync is a fascinating and elegant solution to many file transfer problems. Further information is available from the rsync documentation page.
For more information, first contact your local distributor or email .