User's Manual
Table Of Contents
- Contents
- Contents v
- Figures ix
- Tables xi
- Preface xv
- Appendix A Specifications 157
- Appendix B Factory Configuration 159
- Appendix C CommandLine Syntax 163
- Appendix D Antenna Guidelines 181
- Appendix E CCU/EUM Data Tables 183
- Appendix F Ping Commands 197
- Appendix G SNMP MIB Definitions 199
- Appendix H Operating Statistics 223
- Appendix I IP Plan — Example 241
- Appendix J Acronyms and Glossary 253
- Index 261
- Figures
- Tables
- Preface
- 1 Introduction
- 2 Quick Startup
- 3 Detailed Description
- 4 IP Network Planning
- 5 Radio Network Planning
- 6 Installation/Diagnostic Tools
- 7 Configuring the CCU
- 7.1 CCU and EUM Serial Number, MAC Address, and Station ID
- 7.2 Setting the CCU Password
- 7.3 Configuring the CCU RF Parameters
- 7.4 Configuring CCU IP Parameters
- 7.5 Configuring DHCP Relay
- 7.6 Configuring Port Filtering
- 7.7 Configuring the SNTP/UTC Time Clock
- 7.8 Configuring SNMP
- 7.9 Adding EUMs to the Authorization Table
- 8 Configuring the EUM
- 9 Installing the EUM
- 9.1 Before you Start the EUM Installation
- 9.2 Other EUM Programming Considerations
- 9.3 Installation Overview
- 9.4 Installation Procedures
- 9.4.1 Opening the Box
- 9.4.2 Turning off the End-user’s Cordless Phones
- 9.4.3 Choosing a Location for the EUM and Antenna
- 9.4.4 Connecting the EUM Components
- 9.4.5 Conducting a Preliminary Check of the EUM
- 9.4.6 Positioning the Antenna
- 9.4.7 Mounting the Antenna
- 9.4.8 Connecting the End-user’s PC
- 9.4.9 Obtaining Valid IP Addresses for the End-user’s PC
- 9.4.10 Testing the Data Link
- 9.4.11 Configuring the Browser Application
- 9.4.12 Completing the Installation
- 9.4.13 Baselining the Installation
- 9.4.14 Troubleshooting
- 10 Maintaining the Network
- 11 Monitoring the Network
- 12 Troubleshooting
- 13 Specialized Applications
- Appendix A Specifications
- Appendix B Factory Configuration
- Appendix C CommandLine Syntax
- Appendix D Antenna Guidelines
- Appendix E CCU/EUM Data Tables
- Appendix F Ping Commands
- Appendix G SNMP MIB Definitions
- MIB-II Elements Supported from RFC-1213
- WaveRider CCU Enterprise MIBs
- CCU Base MIB
- CCU General Information Group
- CCU Radio Configuration Group
- CCU Radio Statistics Group
- CCU Radio General Statistics Group
- CCU Radio Driver Statistics Group
- CCU Radio MAC Statistics Group
- CCU Ethernet Statistics Group
- CCU Modem Information MIB
- CCU Registration Information MIB
- CCU Registration Table
- CCU Authorization Information MIB
- CCU Authorization Table
- CCU RFC MIB-II Traps
- WaveRider EUM Enterprise MIBs
- EUM RFC MIB-II Traps
- Appendix H Operating Statistics
- Appendix I IP Plan — Example
- Appendix J Acronyms and Glossary
- Index

6 Installation/Diagnostic Tools
APCD-LM043-4.0 81
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.
The unit is automatically rebooted. If the new executable is found to be corrupt for any reason,
then the unit reverts to the backed-up, older image.
6.9 FTPing CCU and EUM Configuration Files
FTP enables you to transfer configuration files to CCUs and EUMs from anywhere that has
network access to the LMS4000 900MHz Radio Network. FTP is a useful tool for the following
operations:
• Restoring a unit to an earlier working state.
• Restoring configuration files that have been corrupted.
• Configuring replacement CCUs and EUMs when units have failed.
• Changing default configurations, such as GOS.
Some of the configuration files may be the same throughout the network (port filter
configuration file, for example), and others are different for all units. Some configuration files
are loaded instantly (as soon as the file is FTPed), and some require a unit reboot to take
effect. Table 20 provides a summary of the configuration files used in the CCUs and EUMs,
whether they are typically the same throughout the system, and whether they require a unit
reboot to take effect.
Table 20 FTPing Configuration Files
NOTE: System-wide means that the configuration file in question (for
example, the port configuration file) will normally be the same
throughout your network. Configuration files, such as the route
configuration file, vary from CCU to CCU.
Configuration File File Name CCU EUM Reboot Required?
System-wide?
(note 1)
GOS Configuration File gosbe.cfg
gosbronz.cfg
gossilve.cfg
gosgold.cfg
Yes No Yes
Authorization Configuration File authdb.cfg Yes No No
DHCP Configuration File dhcp.cfg Yes Yes Yes
Port Configuration File port.cfg Yes Yes Yes Yes
Route Configuration File route.cfg Yes Yes No
SNTP Configuration File port.cfg Yes Yes Yes Yes
Basic Configuration File basic.cfg Yes Yes Yes No