Redline Communications Inc. AN100UXA Manuel D’Utilisation
User
AN-100U/UX Base Station
Manual
70-00058-01-04
Proprietary Redline Communications © 2010
Page 122 of 136
April 19, 2010
the upgrade performed. Resetting the base station before activating a new software
upgrade will cause the latest configuration to be loaded.
upgrade will cause the latest configuration to be loaded.
12. When using local synchronization (no GPS clock) and the Master is powered off or
disconnected, rebooting the Backup-Master causes it to enter Slave mode and it
does not generate synchronization pulses. The Backup-Master function is enabled
only when synchronization pulses are detected from a Master (Sync out) or GPS
clock (Sync in). If the Master will be out of service for an extended period, it is
recommended to configure one of the Slave base stations to be a Master (requires a
reboot).
does not generate synchronization pulses. The Backup-Master function is enabled
only when synchronization pulses are detected from a Master (Sync out) or GPS
clock (Sync in). If the Master will be out of service for an extended period, it is
recommended to configure one of the Slave base stations to be a Master (requires a
reboot).
13. Normal classifiers have preference over pass-all classifiers on the same priority
level.
8.1.2 Subscriber
1. When upgrading, do not reset or remove power from the subscriber units
immediately after the initial reboot. The software upgrade may require a minimum of
two minutes to complete the re-programming. If the upgrade process is interrupted
the subscriber may become unmanageable and the unit must be returned to the
factory for repair.
two minutes to complete the re-programming. If the upgrade process is interrupted
the subscriber may become unmanageable and the unit must be returned to the
factory for repair.
2. Upgrading the subscriber from v1.0.x to v2.0.x using the subscriber Ethernet port
may result in the subscriber being unable to reboot. The previous software version
can not be restored. Any subscriber that fails during the upgrade process must be
returned to the factory for reprogramming. It is strongly recommended to use the
RedMAX RMS or the secondary management channel (SMC) from the base station
(CLI over-the-air) to upgrade subscribers from v1.0.x to v2.0. BUG 2351
can not be restored. Any subscriber that fails during the upgrade process must be
returned to the factory for reprogramming. It is strongly recommended to use the
RedMAX RMS or the secondary management channel (SMC) from the base station
(CLI over-the-air) to upgrade subscribers from v1.0.x to v2.0. BUG 2351
3. Loading an earlier software version causes the subscriber to load factory default
parameters (including radio frequency settings). This may cause loss of connectivity
with the base station. Use the CLI 'switch' command to return to the previous
software version (only while the previous version resides in the alternate non-volatile
RAM).
with the base station. Use the CLI 'switch' command to return to the previous
software version (only while the previous version resides in the alternate non-volatile
RAM).
4. If the BsID table is not populated, rebooting the base station may cause the
subscriber to switch to another base station and not return to original base station.
5. Uploading an invalid binary image (e.g., base station binary image) causes the
subscriber to reject subsequent attempts to upload the correct binary file. Reboot the
subscriber and upload the correct binary image file.
subscriber and upload the correct binary image file.
6. Uploading the SUO-U1-001-01-00-117.bin binary image to an SU-I will cause the
unit to become inoperable. The SU-I must be returned to the factory for
reprogramming.
reprogramming.
7. The subscriber does not inform the user that a reboot is required before changes to
RF parameters effective (e.g., channel, CP).
8. Following a power-cycle, the base station may not recognize the radio type for some
early TB3335F7 and TB3436F7 radios. Power-cycle the system to clear the problem.
9. When using CLI to enter frequency ranges, all entries must be manually ordered
from lowest (table entry 0) to highest.
10. Downgrading is possible if the previous version is still located in flash RAM (switch
versions in the configuration screen). Downgrading from v2.0.x to v1.1.x may result
in the subscriber being unable to reboot and the previous software version can not
be restored. Any subscriber that fails during the downgrade process must be
returned to the factory for reprogramming. 2923
in the subscriber being unable to reboot and the previous software version can not
be restored. Any subscriber that fails during the downgrade process must be
returned to the factory for reprogramming. 2923