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

12 Troubleshooting
150 APCD-LM043-4.0
resort. Otherwise, the level and location of the interferer has to be deduced from
measurements available at the CCU and EUM. Several of these measurements are
referenced in the preceding Troubleshooting sections.
Some further clarifications and guidelines are listed here:
• A typical data transmission between the CCU and the EUM requires information
packets to go both ways. For example, a payload transmitted from the EUM to the
CCU will be acknowledged with an ACK packet returned from the CCU. If the
transmission fails, it is difficult to determine directly which direction failed (for an
interferer, the failure will occur at the end of the link which is closer to the interferer).
• With the exception of the received signal level, the CCU radio environment is the
same for all EUMs. If transmissions from one EUM are unreliable, but transmissions
from another EUM with similar received signal strength at the CCU are not, then the
likely problem will be found at the affected EUM. If all EUMs of similar signal strength
are similarly affected, then the problem will likely be found at the CCU.
• If communications exist, the quality of the transmission can be measured by the
transmit retry rate, as indicated in previous sections. This is a powerful diagnostic tool.
• If communications exist, longer packets will suffer more failures (retransmissions)
than shorter packets, which can cause the customer to see some applications work
better than others (e.g. browsing may be less impacted than FTP file transfers). The
ping test, using variable length ping packets, can be a useful device to quantify the
extent of this problem.
• If communications from an EUM to the CCU are not possible, the ARP table can be
used to divide the link into two sections. A ping from the EUM to the CCU that is
received by the CCU will cause the EUM to be entered into the CCU ARP table. Even
if the response from the CCU is lost, verifying the entry in the CCU ARP table will
confirm the EUM-to-CCU link and suggest that the EUM is in a relatively severe
interference environment.
• If the receive signal level at the EUM is above -80dBm, and the EUM has the correct
frequency and valid IP addresses, then if the EUM cannot ping the CCU, it is highly
likely there is an interferer in the vicinity of the EUM.
• A local interferer at the EUM location can usually be managed through proper
placement of the antenna, and if the interferer is in the same residence, judicious
placement of the interfering device.
• For comprehensive diagnosis of an EUM, and determining mitigating actions in severe
cases, a spectrum analyzer may be required.