User's Manual Part 1

6: Installation & Diagnostic Tools
APCD-LM043-8.0 (DRAFT C) 107
Once you have obtained and installed these MIBs, you will, from the SNMP manager, be able
to carry out the following functions for both CCUs and EUMs:
• Read hardware and software configuration parameters, such as unit serial number,
MAC address, regulatory domain, and hardware and firmware version.
• Read operator-configurable parameters, such as IP addresses, radio frequency,
transmit power level, and the contents of the CCU Authorization and Registration
Tables.
• Read system operating statistics from the MAC layer, and the radio and Ethernet
drivers.
• Receive trap messages such as CCU or EUM power cycles.
In addition, you can program your SNMP manager to perform the following operations:
• Generate a warning or alarm whenever an operating statistic falls outside an
acceptable range.
• Perform mathematical calculations on a collection of statistics and generate a warning
or an alarm if the result of the calculation falls outside an acceptable range. This
calculation is done when a statistic, in isolation, cannot be interpreted; i.e., it can only
be interpreted properly when compared with the current value of other statistics.
• Perform a trend analysis on a statistic or group of statistics and generate a warning or
alarm when the statistic or group of statistics is starting to move towards an
unacceptable limit.
For more detailed information on how to use SNMP to monitor the performance of your
LMS4000 900 MHz Radio Network, refer to
Monitoring the Network on page 165 and
Appendix I on page 251.
6.11 Field Upgrade Process
CCU and EUM operating software can be upgraded using FTP. The upgrade mechanism is
designed to be robust and reliable.
Hash codes are generated with each new software image. The new image is FTPed with the
hash code to the unit that is being upgraded, and the new software is received and written to
memory. A hash code for the new image is generated locally and compared with the hash
code that was FTPed with the new image.
If the hash code comparison is unsuccessful, the downloaded image will not be written to the
file system, and a report will be returned.
If the hash code comparison is successful, then the existing executable software is copied as
a backup (.bak file), and the newly downloaded image becomes the unit executable.
If the new executable is found to be corrupt for any reason, then the unit reverts to the backed-
up, older image.