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
APCD-LM043-4.0 51
CAUTION: The local host entry, 127.0.0.1, is required to avoid
the problem where the CCU cannot find a real NTP server (i.e., if
the network is down).
3.6.4 Customer List
For each EUM, the system operator can control the number of end-user computers that can
access the LMS4000 network for the purpose of controlling network performance or service
differentiation. The use of this list is described in Customer Table (EUM only) on page 192.
3.6.5 SNMP Support
Simple Network Management Protocol (SNMP) allows a network management server to
monitor, control, and remotely configure LMS4000 network devices. In SNMP, these devices
are also referred to as agents.
Community Strings
Community strings act as passwords to facilitate communication between the SNMP server
and a network device. There are three types of community strings:
• Read community strings, which enable SNMP servers to retrieve information from a
network device
• Write community strings, which enable SNMP servers to send information, such as
configuration commands, to a network device.
NOTE: At this time, there are no writable SNMP MIB entries. All
configuration is done via the CLI.
• Trap server IP address and community strings, which enable SNMP servers to
receive unsolicited messages from a network device. These unsolicited messages
indicate asynchronous events, such as an interface going down or coming up, a unit
performing a cold or warm start, or an operational failure.
Each network device monitored by SNMP must have at least one of each type of community
string defined. Each CCU and EUM can have up to five read or read/write and five trap
servers/community strings defined. Non-WaveRider devices may have only one of each type
of community string defined. Community strings are case sensitive.
Table 9 Factory Configured Community Strings
Community String Type Community String
Read public
Write private
Trap <none>