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

3 Detailed Description
46 APCD-LM043-4.0
All of these charts illustrate that many (LMS4000) users can share the limited bandwidth of
the channel, yet most of the time, each perceives that they have most of the channel to
themselves.
Atypical Applications
The Polling MAC has been optimized for normal user applications. One basic assumption that
has been made in the design of the Polling MAC is that users are only associated for a small
fraction of the time they are sitting in front of their computers. This usage is typified, for
example, by a file transfer (Web page for example) every two minutes or so—each transfer
taking a second or two. The MAC takes advantage of this usage pattern by only associating
with active EUMs.
A second assumption is that EUMs become active independently. If many EUMs
simultaneously attempt to use the random access opportunity, they will collide multiple times
and may not get through.
If the above assumptions are reasonable, then it is also reasonable to assume that a limited
number of EUMs will be associated at any given time, as demonstrated in Performance
Modelling on page 42.
There are several computer applications where usage is not consistent with the above
assumptions. These applications, which are discussed below, can compromise the efficient
operation of the LMS4000 network and may cause the network to slow down.
Broadcast Applications
Some applications broadcast messages to which all or a large number of hosts are expected
to respond. If these applications are running over the system, not only will responses from
disassociated EUMs collide as the random access opportunities are overwhelmed, but those
that do get through will quickly use up all of the available associations. With so many
associated EUMs, polls are farther apart and throughput degrades, even if the newly
associated EUMs have no further traffic to send. As well, EUMs that are not associated are not
able to associate and are therefore be blocked for a few seconds. The following applications
can cause this type of problem:
• Broadcast pings: WaveRider recommends not using broadcast pings.
• SNMP broadcast requests: WaveRider recommends not using SNMP broadcast
requests.
• Windows Network Neighborhood: This traffic can be blocked using port filtering at
the CCU or EUM level, as discussed in Port Filtering on page 49.
Periodic Packet Sources
Some applications send individual packets at fixed, often large, intervals, expecting only a
single packet or small number of packets in response. The direct impact of these applications
is that EUMs that are sent periodic packets remain associated for a longer period of time than
that warranted by their end-user traffic level and continue to be polled unnecessarily. The
atypical applications themselves will function very well; however, they will use up a significant
amount of the channel bandwidth. This group includes the following applications: