2 determining the current firmware level – Guralp Systems CMG-DCM build <10,000 User Manual

Page 52

Advertising
background image

Acquisition Modules and Platinum Firmware

Platinum Firmware Upgrades

built using the two different compilers. For this reason, it is important that an
upgrade from build 3801 to build 10,000 or later is not interrupted.

The upgrade mechanism has, until now, been extremely tolerant of
interruptions and it has been normally sufficient to simply restart an

interrupted upgrade process. This will also be true for future upgrades, once
build 10,000 or higher has first been installed.

For upgrades from build 3801 to build 10,000 or later, however, it is highly
recommended that an upgrade to an acquisition module only be carried out in

a situation with a stable power supply, a reliable internet connection and
where you have physical access to the unit.

5.1.3 Procedures for upgrades spanning build 10,000

5.1.3.1 CMG-EAMs

An extra step must be taken when upgrading from build 3801 to the latest
build and special attention must be paid to the amount of free disk space

available. Please see this article on our web site for complete information and
detailed instructions:

www.guralp.com/articles/20110309-EAM-EABI-upgrade

5.1.3.2 CMG-NAMs and CMG-NAM64s

After upgrading from build 3801 to the latest build, you may see several
FATAL: kernel too old messages. In order to resolve this issue, please

log in to the command line as root and run the command:

/sbin/manual-post-upgrade

If, despite all precautions, the upgrade is interrupted at a crucial time, attempt

first to restart the upgrade. If this fails, please follow the recovery instructions
available from our web site at:

www.guralp.com/articles/20110318-NAM-recovery

5.1.3.3 CMG-DCMs

When upgrading a CMG-DCM, the upgrade process should be carried out
twice. The second run will resolve problems with broken symlinks. During

the first upgrade run, you may see several errors about “Directory not
empty”
and references to broken files. These are normal and the second

upgrade invocation is designed to resolve these problems and leave the
system in a consistent state.

5.2

Determining the current firmware level

To determine the current firmware version from the web interface, select:

Summary → System status

MAN-EAM-0003

52

Issue E - February 2014

Advertising
This manual is related to the following products: