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
136 APCD-LM043-4.0
B. If only one EUM is affected:
• Verify that you can ping from the gateway router to other EUMs on the same CCU. If
you cannot, go to A. above.
• Ifthistestissuccessful,gotoEUM Troubleshooting on page 136.
12.1 EUM Troubleshooting
The following EUM troubleshooting process can be used at the time of the initial EUM
installation or during follow-up service visits. In the latter case, troubleshooting focusses on
factors that might have changed, using the setup file record from the initial install as a
baseline.
In general, the following items will be verified as part of EUM troubleshooting:
• CCU configuration, particularly as it relates to the affected EUM
• EUM configuration
• Radio link integrity
• User PC configuration
All of these items can be checked out from the end-user’s PC, but it may be better to use a
separate, known PC for the tests outlined in the troubleshooting tables. Then, you can repeat
the tests with the end-user’s PC to make sure the end-user’s PC is configured and working
properly.
When a customer reports a problem, it is usually related to a failure of the browser or email
application on the PC to successfully access the Internet, or it is a report of degraded service
or slowdown. From the problem report, troubleshooting proceeds as follows:
1. To avoid a service call to the end-user’s premises, try to isolate the problem remotely,
using the procedures outlined in Table30onpage138(for problems where the
service is not available) and in Table 31 on page 139 (for problems where the service
is degraded).
2. If you are unable to troubleshoot the problem remotely and must visit the end-user’s
premises, use the procedures outlined in Table32onpage140(service not available)
and in Table 33 on page 142 (service degraded).
Two test utilities are commonly used throughout the troubleshooting process. The term
<ipconfig> generically refers to a utility that verifies IP addresses in the PC, and to force
changes when DHCP is enabled. To force a change through DHCP, use a release and renew
command sequence. The IP set in the end-user’s PC refers to the following addresses:
• PC IP address
• PC subnet mask
• Gateway IP address (same as the CCU IP address)
• DNS server IP address (usually two addresses are provided)