8.3.7. Fatal errors
This type of message indicates a fatal error for which no further reporting is available:
nFast server: Fatal internal error
or
nFast server: Fatal runtime error
If you receive either of these errors, contact Support.
8.4. Utility error messages
8.4.1. BadTokenData error
The PCIe module (not the Solo XC module) is equipped with a rechargeable backup
battery for maintaining Real-Time Clock (RTC) operation when the module is powered
down. This battery typically lasts for two weeks. If the module is without power for an
extended period, the RTC time is lost. When this happens, attempts to read the clock (for
example, using the
ncdate
or
rtc
utilities) return a
BadTokenData
error status.
The correct procedure in these cases is to reset the clock and leave the module powered
up for at least ten hours to allow the battery to recharge. No other nonvolatile data is lost
when this occurs. See the
Solo User Guide
for more about resetting the clock.
The Solo XC module is equipped with a battery with a ten year life for maintaining RTC
operation when the module is powered down. The RTC will not require resetting after the
module has been shut down for extended periods. The battery is not rechargeable.
Solo XC only
: Reboot the Solo XC for the firmware upgrade to take effect.
Linux bare metal environments
: With the module in Maintenance mode, run the
following command to reboot the Solo XC:
nopclearfail -S -m<module_number>
Linux virtual environment hosts and Windows
:
Reboot the system that is hosting the Solo XC.
On all platforms
:
Wait for the Solo XC to reboot. The module has completed rebooting when running
enquiry
no longer shows the module as Offline.
nShield® Solo and nShield® Solo XC Installation Guide
28 of 49
