lms052 Ap 01

LMS8000 / LMS4000
Managing the Network
lms052_ap_01
RELEASE 2.0, Jan 2008 Proprietary to Vecima Networks Inc. by Vecima Networks Inc., 2008 Permission to Reproduce Except as otherwise specifically noted, the information in this publication may be reproduced, in part or in whole and by any means, without charge or further permission from Vecima Networks Inc., provided that due diligence is exercised in ensuring the accuracy of the information reproduced; that Vecima Networks Inc. is identified as the source; and that the reproduction is not represented as an official version of the information reproduced. This publication is also available electronically on the World Wide Web at the following address: www.wr.vecimasupport.com Vecima Networks Inc. reserves the right to revise this publication and to make changes in content from time to time without obligation on the part of Vecima Networks Inc. to provide notification of such revision or change. Vecima Networks Inc. provides this guide without warranty of any kind, either implied or expressed, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Vecima Networks Inc. may make improvements or changes in the product(s) described in this manual at any time. Specifications subject to change without notice.
lms052_ap_01
Preface
Conventions
The following conventions are used throughout this document:
WARNING!
Whenever you see this icon and heading, the associated text addresses or discusses a critical safety or regulatory issue. CAUTION: Whenever you see this icon and heading, the associated text discusses an issue, which, if not followed, could result in damage to, or improper use of, the equipment or software. TIP: Whenever you see this icon and heading, the associated text provides a tip for facilitating the installation, testing, or operation of the equipment or software.
Regulatory Notices
LMS8000 / LMS4000 devices have been designed to operate with several different antenna types. The gain of each antenna type must not exceed the maximum antenna system gain given in the installation manuals for your LMS8000 / LMS4000 equipment. Antennas having a higher gain are strictly prohibited by Industry Canada and FCC regulations. The required antenna impedance is 50 ohms.
Industry Canada
LMS8000 / LMS4000 devices have been certified with Industry Canada for operation in Canada. See the installation manual for your LMS8000 / LMS4000 equipment for certification details. Operators must be familiar with IC RSS-210 and RSS-102. The CCU and EUM have been designed and manufactured to comply with IC RSS-210 and RSS-102.
lms052_ap_01
Federal Communications Commission

LMS8000 / LMS4000 devices have been designed and manufactured to comply with FCC Part 15. See the installation manual for your LMS8000 / LMS4000 equipment for certification details. Operators must be familiar with the requirements of the FCC Part 15 Regulations prior to operating any link using this equipment. For installations outside the United States, contact local authorities for applicable regulations.
Warnings and Advisories

Operator and maintenance personnel must be familiar with the related safety requirements before they attempt to install or operate the LMS8000 / LMS4000 equipment. It is the responsibility of the operator to ensure that the public is not exposed to excessive Radio Frequency (RF) levels. The applicable regulations can be obtained from local authorities.
Getting Support
An extensive knowledge base is available at www.wr.vecimasupport.com. Visit the web page to: Get the latest announcements from Vecima Networks. Download product related software, manuals, application notes, or other information about the WaveRider product line. Consult the KnowledgeBase for troubleshooting information. Register and contact technical support to help you with unexpected problems.
Training
Vecima offers a complete training program. Please contact you sales representative for training information.
Priority support
Vecima also offers priority telephone and email support. Please contact your sales representative for details.
ii
lms052_ap_01
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . i 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.1 Document Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.2 LMS8000 / LMS4000 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2 Configuring the CCU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 2.1 Serial Number, MAC Address, and Station ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.2 Setting the CCU Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.3 Configuring the CCU RF Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 2.4 Configuring CCU Protocol Modes and IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.4.1 Configuring Routed Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 2.4.2 Configuring Switched Ethernet Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 2.4.3 Configuring Through Only Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 2.5 Configuring DHCP Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.6 Configuring Port Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.7 Configuring the SNTP UTC Time Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 2.8 Configuring SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.9 Configuring VoIP Detection and Priority Classification . . . . . . . . . . . . . . . . . . . . . . . . 22 2.10 Adding EUMs to the Authorization Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 2.11 Configuring the CCU RADIUS Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 3 Configuring the EUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.1 Setting the EUM Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.2 Configuring the EUM RF Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.3 Configuring EUM IP Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.4 Configuring Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.5 Configuring Port Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.6 Configuring SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.7 Configuring the Customer List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 30 30 33 34 35 35 35
4 Configuring a DHCP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 4.1 CCU DHCP Relay and Relay Agent Information Option. . . . . . . . . . . . . . . . . . . . . . . 38 4.2 EUM DHCP Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 5 Configuring a RADIUS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.1 RADIUS Authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.2 RADIUS and Autoconfiguration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3 RADIUS Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4 RADIUS Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.1 Vecima-Grade-of-Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.2 Vecima-Priority-Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.3 Vecima-Authentication-Key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.4 Vecima-Current-Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.5 Vecima-New-Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.6 Vecima-Radio-Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 40 40 40 41 41 41 42 43 43 44
lms052_ap_01
iii
5.4.7 Vecima-SNMP-Read-Community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.8 Vecima-SNMP-Write-Community . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.9 Vecima-SNMP-Trap-Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.10 Vecima-SNMP-Contact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.11 Vecima-SNMP-Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.12 Vecima-SNMP-Name (and Prompt) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.13 Vecima-Max-Customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.14 Vecima-Rf-Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.15 Vecima-Downlink-Min-Modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.16 Vecima-Downlink-Max-Modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.17 Vecima-Uplink-Min-Modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.18 Vecima-Uplink-Max-Modulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5 RADIUS Server Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.1 RADIUS Packet Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Monitoring the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1 Radio Received Signal Strength and Quality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2 CCU Transmit Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3 CCU Receive Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.4 CCU Watch Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.5 EUM Transmit Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.6 EUM Receive Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.7 User Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.8 Logging CCU or EUM Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.9 CCU Registration (Air) Table Statistics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.10 CCU Radio Meter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
44 45 45 46 46 47 47 48 48 49 49 50 51 53 61 62 64 68 69 70 72 72 73 74 75
6 Spectrum Analyser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
8 Upgrading the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 8.1 Field Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 8.2 FTPing CCU and EUM Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Appendix A Appendix B Appendix C Appendix D Operating Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 CCU/EUM Data Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117 Access Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Windows Ping Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
lms052_ap_01
iv
Tables
Table 1 Table 2 Table 3 Table 4 Table 5 Table 6 Table 7 Table 8 Table 9 Table 10 Table 11 Table 12 Table 13 Table 14 Table 15 Table 16 Table 17 Table 18 Table 19 Table 20 Table 21 Table 22 Table 23 Table 24 Table 25 Table 26 Table 27 Table 28 Table 29 Table 30 Table 31 Table 32 Table 33 Table 34 Table 35 Modulation Scheme Names and Numbers . . . . . . . . . . . . . . . . . . . . . . . . . 24 FreeRADIUS Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 FreeRadius dictionary File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 FreeRadius dictionary.waverider File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 FreeRadius clients File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 FreeRadius users File Example Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Example - RADIUS Access Request . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Example - RADIUS Access Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Radio Analyser Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 57 LMS4000 Signal Quality Troubleshooting Guide . . . . . . . . . . . . . . . . . . . . 63 Possible Transmission Outcomes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 Typical CCU Receive Statistic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 EUM Transmit Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 FTPing Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 Ethernet Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Radio Driver Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 Radio Link Monitor Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 DPMAC Interface Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 LMS8000 Radio RSSI Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 LMS4000 Radio RSSI Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 Received Signal Strength Figure of Merit . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Received Signal Quality Figure of Merit . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Radio Modulation Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Routing/Bridging Protocol Statistics for CCU in Routed Mode . . . . . . . . . . 99 Routing/Bridging Protocol Statistics for CCU in Switched Ethernet or Through Only Mode 99 Routing/Bridging Protocol Statistics for EUM . . . . . . . . . . . . . . . . . . . . . . 100 Common Routing/Bridging Protocol Statistics . . . . . . . . . . . . . . . . . . . . . 101 RADIUS Client Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 Authorization Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Network Interface Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Load Statistics (Radio Meter) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110 CCU Watch Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 System Log Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Port Filter Table Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Basic Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
lms052_ap_01
Table 36 Table 37 Table 38 Table 39 Table 40 Table 41 Table 42 Table 43 Table 44
Routing Table Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Numeric Routing Table Flags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120 Non-numeric Routing Table Flags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 ARP Table Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Registration Table Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 ARP MAP Table Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Bridge Table Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128 Serial Port Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134 Windows Ping Test Command Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
vi
lms052_ap_01
Introduction
The LMS8000/LMS4000 900 MHz Radio Network provides wireless high-speed Internet connectivity to business, SOHO (small office, home office) and residential customers. LMS8000/LMS4000 operates in a point-to-multipoint configuration, with one base station efficiently serving many subscriber stations. LMS8000/LMS4000 transmission is based on a high-performance MAC protocol, and industry-standard IP routing, Ethernet switching and data encryption technology. No radio license is required, since LMS8000/LMS4000 operates in the 900 MHz ISM band. LMS8000/LMS4000 can deliver Internet service over long ranges and often where the radio paths between the base station and subscribers are partially or even totally obscured, that is, non-line-of-sight. Connection between the end-users computer and the subscriber station is through an Ethernet port.
1.1
Document Scope
LMS4000 Managing the Network provides information for the system operator to configure, monitor and manage LMS8000 / LMS4000 900 MHz networks. Related information can be found in the suite of available LMS8000 / LMS4000 manuals, which includes the following: LMS8000/LMS4000 Data Networking Concepts LMS8000/LMS4000 Radio Networking Concepts LMS8000/LMS4000 SNMP Reference Manual LMS8000/LMS4000 CLI Reference Manual LMS8000/LMS4000 Feature Support Matrix NOTE: Individual manuals for hardware elements, including EUMs and CCUs, can be found on Vecimas Web site. This manual describes the LMS8000 / LMS4000 system as of versions 7.0, 11.3, 20.4, 30.1 and 40.1 of the EUM/CCU software. See LMS8000/LMS4000 Feature Support Matrix for which versions apply to which models.
lms052_ap_01
1: Introduction
1.2
LMS8000 / LMS4000 Features

The LMS8000 / LMS4000 900MHz Radio Network offers the following features and benefits: Excellent Propagation Characteristics: LMS 900 MHz radio networks provide excellent coverage to non-line of sight installations using Vecimas integrated outdoor high-gain, active-diversity antennas. The 900 MHz ISM band is more suited to NLOS (non-line of sight) wireless Internet applications than other ISM bands because it has superior propagation performance, demonstrating the following benefits: Lower free-space, cable and foliage loss Better wall and glass penetration More signal recovery from diffraction and reflection
High-speed Channel: The LMS8000 900 MHz Radio Network uses OFDM Modulation schemes at raw channel rates between 1.5 and 13.5 Mbps to provide FTP rates of up to 8 Mbps. The LMS4000 provides a raw channel bit rate of 2.75 Mbps, which translates to sustained FTP rates of 2.0 Mbps. Adaptive Modulation: The LMS8000 will automatically select the optimal modulation scheme to use for each link to each subscriber. Units adapt quickly and independently to changes in channel conditions, changing modulation schemes to improve reliability or to take advantage of increased capacity. High-performance Dynamic Polling MAC: Vecimas patented Dynamic Polling MAC algorithm takes advantage of typical usage patterns found in Internet transactions, such as Web browsing and email, to provide an operating capacity of up to 300 end users per RF channel. Even with large numbers of subscribers, end users generally perceive that they have the entire channel to themselves. Multiple Communication Modes: The LMS 900 MHz radio network includes three different communication modes: Routed ModeIn routed mode, the CCU acts as an IP router between the Ethernet and radio subnets and a switch between EUMs. In routed mode, the CCU supports up to eight IP subnets on the radio side, offering flexibility and high capacity. Switched Ethernet ModeIn this mode, the CCU acts as an Ethernet switch between the Ethernet port and the EUMs. It supports PPPoE (Point-to-Point Protocol over Ethernet) as well as any number of IP subnets on either or both sides of the CCU. This mode provides simplicity of operation. Through Only ModeSimilar to Switched Ethernet mode, except that this mode constrains all traffic to flow only from a radio link to the Ethernet port or vice versa, not from one radio link to another.
Voice Over IP Support: The LMS system will detect, prioritize and guarantee latency for VoIP traffic packets separately from data traffic. Data transfer rates and VoIP packet latency can be separately controlled for each grade of service and VoIP support can be offered on a per EUM basis. VoIP detection and classification is highly configurable. Bundling allows for multiple simultaneous calls per EUM. Grade of Service Support: The Polling MAC supports up to four end-user grades of service, which allows the system operator to segment service offerings for those users that demand and are willing to pay for higher grades of service, and those that are only willing to pay for a more basic grade of service.
lms052_ap_01
1: Introduction
License-free Radio Bands: The main advantage of using the ISM band is that you need not apply to the FCC or Industry Canada for an operating license. This freedom reduces your time to market and the effort and high cost associated with obtaining a license. Secure Authentication and User Data Encryption: For the LMS4000 network, only EUMs authorized by the CCU can access the wireless network. Mutual authentication of EUM and CCU is handled using the secure 4-way handshake mechanism of WPA2. All user data flowing over the air can be encrypted using the industry standard IEEE802.11 TKIP cypher. Traffic to and from each EUM is encrypted using a key specific to that EUM, ensuring message integrity and privacy for each user. RADIUS Support: The LMS system supports RADIUS Authorization and RADIUS Accounting for EUM registration, configuration and accounting. Robust Hardware and Software: LMS hardware and software have been rigorously tested in lab and field environments. The hardware, which is mechanically robust, works over a broad range of temperatures and operating conditions. The software is equally robust and has been designed to recover automatically from unplanned events and abnormal operating conditions. Automatic End-user Modem Configuration: The end-user modem (EUM) can be automatically configured through DHCP and RADIUS. Out of the box, the EUM will discover the best frequency and CCU and obtain IP, SNMP and configuration parameters from the network. Configuration changes can be made centrally, without contacting individual modems. Simple End-user Modem Installation and Operation: It is very easy to install and operate the EUM. The outdoor EUM can be quickly and easily installed by a single person. The EUM uses a standard Ethernet interface which means it can be located up to 100 meters from the end-users PC. Flexible Network Topology: The LMS 900MHz Radio Network has a flexible topology, allowing it to line up with the operators existing Internet points of presence and site facilities. It supports a connection between the end-user modem and the Internet through the network operators gateway router and optionally a direct connection between end-user modems through the LMS 900MHz channel units (CCUs) or connection between end-user modems on different CCUs. Multiple IP Subnets: In routed mode, the CCU supports up to eight IP subnets on the radio side. This capability facilitates the delivery of Open Access applications, where the system operator can support multiple ISPs, each concurrently delivering service to their customers EUMs and PCs over the operators LMS facilities. A mix of public and private IP address ranges can be supported, saving limited public IPs. Bundling: Bundling, or payload aggregation, improves efficiency and allows for multiple simultaneous VoIP calls per EUM as well as error recovery. Multiple small Ethernet frames are bundled together as one radio transmission, reducing overhead and increasing capacity. DHCP Relay: CCUs support DHCP relay, which, once enabled, allows end-user PCs to automatically obtain their IP and DNS server addresses from the network operators DHCP servers. DHCP relay simplifies the EUM installation even further and makes it easier for the modem to be installed by the end user. The CCU supports Relay Agent Information option (RFC3046), which allows operators to assign IP addresses to PCs based on the EUM to which they are attached and facilitates the delivery of Open Access applications.
lms052_ap_01
1: Introduction
VLAN Transparency: The LMS system passes VLAN-tagged Ethernet frames transparently, including packets up to 1522 bytes in length. Port Filtering: The network operator can configure CCUs and EUMs to filter IP packets on specific TCP and UDP ports to improve network performance, security, and privacy. Remote System Configuration and Diagnostics: The network operator can configure and monitor CCUs and EUMs from anywhere. This remote access allows the operator to make configuration changes, download new features, and diagnose problems remotely without having to visit distant network sites or end-user premises. Spectrum Analyser: The CCU and EUM Spectrum Analyser tool is very useful for site surveys, installation and troubleshooting. It provides an indication of signal level and interference from external sources and from frequency re-use. The radio analyse command steps across the 900 MHz ISM frequency band measuring peak, average and noise floor powers. SNMP Support: Using Vecima-supplied SNMP MIBs, network operators can integrate the LMS with their existing network management system to allow monitoring of CCUs and EUMs from an existing and/or centralized SNMP manager. The operator can monitor system events, parameters, and statistics in real time. Statistics can be processed in the SNMP manager to provide alarms, trend data, graphical outputs, and derived performance data. Accurate Time Stamping (SNTP): The CCUs and EUMs can be programmed to synchronize their internal clocks with one or more NTP servers. Time stamping enables all logged events in the CCUs and EUMs to be correlated with events that have taken place at other locations in the network or with events logged by equipment installed outside the network, if this equipment is equipped with accurate timestamping. Accurate time-stamping facilitates diagnosis of complex network problems. Field-replaceable Equipment: In the event of an equipment failure, LMS components are easily replaced with minimal or no disruption to the operation of other components. System Upgradability: The LMS network architecture supports orderly growth from simple installations, through single-CCU CAP (Communication Access Point) sites and multi-CCU CAP sites, to multi-CAP networks. Low Maintenance: CCUs and EUMs require no routine maintenance, other than maintenance of their operating environments within the specified temperature and humidity range.
lms052_ap_01
1: Introduction
Extensive Installation, Maintenance and Diagnostic Support: The CCU and EUM are equipped with a wide range of features and utilities to facilitate unit installation, operation, maintenance, monitoring, and diagnostics: Visual status indicators Simple-to-use command-line interface, offering full unit configuration capability Automatic EUM configuration through DHCP and RADIUS. RSSI (receive signal strength indication) and SQ (receive signal quality) output, to simplify antenna pointing and performance indication. MDB1000 Antenna pointing tool. Ability to remotely FTP files to and from CCUs and EUMs Wide range of operating and performance statistics SNMP support RADIUS authorization and accounting Simple and reliable field-upgrade process Remote download of equipment configuration files to CCUs and EUMs
Your decision to implement an LMS8000 / LMS4000 900MHz Radio Network enables you to deliver high-quality, high-speed wireless Internet service to the business and residential subscribers in your serving area.
lms052_ap_01
This page is intentionally left blank
Configuring the CCU
This section explains the following procedures and topics: Serial Number, MAC Address, and Station ID, on page 8 Setting the CCU Password, on page 8 Configuring the CCU RF Parameters, on page 9 Configuring CCU Protocol Modes and IP Addresses, on page 11 Configuring DHCP Relay, on page 15 Configuring Port Filtering, on page 17 Configuring the SNTP UTC Time Clock, on page 18 Configuring SNMP, on page 20 Configuring VoIP Detection and Priority Classification, on page 22 Adding EUMs to the Authorization Table, on page 23 Configuring the CCU RADIUS Client, on page 26 Before you configure the CCU Familiarize yourself with the CLI commands, syntax and shortcuts, outlined in LMS8000/LMS4000 CLI Reference Manual. This document provides a complete list of the available CCU commands, some of which are not discussed in this section. Start a command line session as outlined in Appendix C. CAUTION: Remember to regularly enter save or commit and press Enter, to save your configuration changes to the file system. As well, some parameters and configuration files (refer to LMS8000/LMS4000 CLI Reference Manual for details) do not take effect until you reboot the unit, specifically the RF frequency and IP addressing.
lms052_ap_01
2: Configuring the CCU
2.1
Serial Number, MAC Address, and Station ID

The product ID, serial number, station ID, and Ethernet and radio MAC addresses, are related: Product ID: The product ID is the 14-character string just below the bar code on the product label, which is affixed to the case of the unit, for example: CCU8000KA01A739510131 Serial Number: The serial number is the last six characters of the product ID. In the above example, the serial number is: 510131 Station (CCU or EUM) ID: The station ID is similar to the serial number, with colons inserted. The most significant bit of the first number is always clear, so if the serial number begins with E then the station ID starts with 6. In the above example, the station ID, in hexadecimal notation, is: 51:01:31 Ethernet MAC Address: The Ethernet MAC address is derived by prefacing the station ID with the characters 00:90:C8. In the above example, the Ethernet MAC address is: 00:90:C8:51:01:31 Radio MAC Address (CCU only): The radio MAC address is derived by prefacing the station ID with the characters 00:90:C8 and setting the most significant bit of the 4th byte. In the above example, the radio MAC address is: 00:90:C8:D1:01:31
2.2
Setting the CCU Password

To Change the CCU Password
1. Type password and press Enter. 2. At the Enter Current Password prompt, type the old password. TIP: Passwords are alphanumeric and case-sensitive. For example, abc is not the same as aBc. The CCU is shipped from the factory with no password - just press Enter. 3. At the Enter New Password prompt, type the new password. 4. At the Verify password prompt, type the new password again. The system displays a message that your password has been successfully changed. Example:
51:00:3f*CCU2> password
lms052_ap_01
Enter Current Password: ******** Enter New Password: ******** Verify password: ******** Saving new password Password Changed 51:00:3f*CCU2>
CAUTION: Remember to record the password. Unlocking the CCU can only be performed by contacting Vecima Technical Support.
2.3
Configuring the CCU RF Parameters

To Set the CCU Operating Frequency
1. Type radio frequency <frequency> and press Enter. <frequency> is the CCU operating frequency in tenths of a MHz. For example, 917.0 MHz is entered as 9170. 2. Type save or commit and press Enter. 3. Before the new radio frequency will take effect, you must reboot the CCU by typing reset and pressing Enter.
To Set the CCU Maximum Transmit Power Level

The power level does not include antenna system gain. 1. Type radio rf <power level> and press Enter. <power level> is the CCU maximum transmit power level, either: the desired power level, in dBm, any integer value in the range 15 - 26 inclusive, high (+26 dBm), or low (+15 dBm). For example, radio rf 22 will set the RF output power to +22 dBm. NOTE: Use the HIGH power level unless your site has unique requirements for which a numerically set power level, or the LOW power level, is more appropriate. For example, the capability to numerically set the power level may be useful in high-density environments, where site-to-site interference is a problem. 2. Type save or commit and press Enter.
To Set the CCU Antenna Diversity Mode

Models that support antenna diversity control1 and a diversity antenna allow setting which antenna will be used to receive and transmit on. You can set it to receive on only one antenna 1. See APCD-LM057 Feature Support Matrix for antenna diversity control support.
lms052_ap_01
or the other (A or B), or, for models that have an active polarization diversity antenna, to select the best antenna to receive on on a per packet basis based on signal quality (diversity). Similarly, you can set it to transmit on only one antenna or the other (A or B) or to transmit on the antenna that last received a good packet (diversity). NOTE: In the case of a CCU which has multiple EUMs registered, transmit should be set to just one antenna, as it is likely that it is transmitting to a different EUM than it just received from. 1. Type radio diversity <rx> <tx> and press Enter. <rx> is A | B | diversity and controls which antenna will be used to receive packets. <tx> is A | B | diversity and controls which antenna will be used to transmit packets.
For example, radio diversity diversity A will use receive diversity, but transmit on antenna A. NOTE: For the integrated high-gain polarization diversity antenna, the A antenna is polarized perpendicular to the long axis of the unit and the B antenna is polarized parallel to the long axis of the unit. Adaptive Modulation control for the CCU is set individually for each EUM or as a default. See Adding EUMs to the Authorization Table, on page 23. The following example Sets the CCU operating frequency to 917 MHz, Sets the transmit power level to high, NOTE: Changes to the transmit power level take effect immediately, they do not require a CCU reboot. Saves the new settings, Reboots the CCU so that the new parameters take effect, and Displays the CCU RF parameters.
51:00:3f*CCU2>radio frequency 9170 Radio Frequency: 9170 51:00:3f*CCU2>radio rf high Max RF Power: 26 dBm 51:00:3f*CCU2>save Basic Config saved Port Filter Config saved Network Configuration saved Authorization Database saved 51:00:3f*CCU2>reset
rebooting ... (... Power On Self Test ...) Password:
10
lms052_ap_01
51:00:3f*CCU2> radio Max RF Power: 26 dBm Radio Frequency: 9170
2.4
Configuring CCU Protocol Modes and IP Addresses

This section explains how to configure the CCU to use Routed, Switched Ethernet, or Through Only mode. In APCD-LM050 LMS4000 Data Networking Concepts, you determined the following: CCU Protocol Mode CCU gateway IP address CCU radio IP address(es) and subnet mask(s) CCU Ethernet IP address and subnet mast (Routed Mode only)
2.4.1 Configuring Routed Mode

NOTE: The CCU gateway IP address must be on either the Ethernet or a radio IP subnet, as explained in APCD-LM050 LMS4000 Data Networking Concepts. CAUTION: All IP addresses should be confirmed when changing protocol modes, otherwise unexpected results may occur.
To Configure the CCU to Operate in Routed Mode

1. Type protocol routed and press Enter to set the CCU to routed mode.
51:00:3f*CCU2> protocol routed Routed Mode
2. Type ip radio <aaa.bbb.ccc.ddd> <net mask> and press Enter to set the CCU primary radio IP address and subnet mask. <aaa.bbb.ccc.ddd> is the CCU radio IP address. <net mask> is the number of bits set in the net mask (1 to 32). CAUTION: The CCU only accepts subnet masks using the shorthand notation; for example, it accepts 16, but not ffff0000 or 255.255.0.0.
51:00:3f*CCU2> ip radio 172.16.6.1 22 Radio:
lms052_ap_01
11
IP Address: 172.16.6.1 / 22 IP Subnet : 172.16.4.0 ( 255.255.252.0 )
3. Type ip add <aaa.bbb.ccc.ddd> <net mask> and press Enter to set each secondary radio IP address and subnet mask. <aaa.bbb.ccc.ddd> is the CCU radio IP address. <net mask> is the number of bits set in the net mask (1 to 32).
51:00:3f*CCU2>ip add 11.1.2.3 26 Added IP Address: 11.1.2.3 / 26 Added IP Subnet : 11.1.2.0 ( 255.255.255.192 )
4. Type ip ethernet <aaa.bbb.ccc.ddd> <net mask> and press Enter to set the CCU Ethernet address. <aaa.bbb.ccc.ddd> is the CCU Ethernet IP address. <net mask> is the number of bits set in the net mask (1 to 32).
51:00:3f*CCU2>ip ethernet 192.168.10.8 24 Ethernet: IP Address: 192.168.10.8 / 24 IP Subnet : 192.168.10.0 ( 255.255.255.0 )
5. Type ip gateway <aaa.bbb.ccc.ddd> <net mask> and press Enter to set the CCU gateway IP address.
51:00:3f*CCU2>ip gateway 192.168.10.9 Gateway Route changed Gateway IP Address: 192.168.10.9
6. Type save and press Enter to save the new settings.

51:00:3f*CCU2>save Basic Config saved Port Filter Config saved Network Configuration saved Authorization Database saved
7. Type reset and press Enter to reboot the CCU.

51:00:3f*CCU2>reset rebooting ...
8. On reset, type protocol and press Enter to display the protocol mode.
51:00:3f*CCU2>protocol Routed Mode
9. Type ip and press Enter to display the ip addresses.

51:00:3f*CCU2>ip Ethernet: IP Address: 192.168.10.8 / 24 IP Subnet : 192.168.10.0 ( 255.255.255.0 ) Radio: IP Address: 172.16.6.1 / 22 IP Subnet : 172.16.4.0 ( 255.255.252.0 ) IP Address: 11.1.2.3 / 26 IP Subnet : 11.1.2.0 ( 255.255.255.192 ) Gateway IP Address: 192.168.10.9
12
lms052_ap_01
You must also configure all EUMs and subscriber PCs connected to the CCU to have IP addresses on the appropriate radio IP subnet, and have the corresponding CCU radio IP address as their gateway. DHCP is an excellent method to do this.
2.4.2 Configuring Switched Ethernet Mode

To Configure Switched Ethernet Mode
1. Type protocol switched and press Enter to set the CCU to Switched Ethernet mode.
51:00:3f*CCU2>protocol switched Switched Ethernet Mode
2. Type ip ethernet <aaa.bbb.ccc.ddd> <net mask> and press Enter to set the CCU IP address. <aaa.bbb.ccc.ddd> is the CCU IP address <net mask> is the CCU IP subnet mask
3. Type ip gateway <aaa.bbb.ccc.ddd> <net mask> and press Enter to set the CCU gateway to be the gateway router. <aaa.bbb.ccc.ddd> is the CCU gateway IP address <net mask> is the CCU gateway IP address subnet mask


51:00:3f*CCU2>protocol Switched Ethernet Mode

51:00:3f*CCU2>ip Modem: IP Address: 192.168.10.8 / 24 IP Subnet : 192.168.10.0 ( 255.255.255.0 ) Gateway IP Address: 192.168.10.9
lms052_ap_01
13
You must also configure all EUMs and subscriber PCs connected to the CCU to have IP addresses on IP subnets corresponding to addresses on the gateway router interface, and have the corresponding gateway router IP address as their gateway. DHCP is an excellent method to do this.
2.4.3 Configuring Through Only Mode

The following procedure demonstrates how to configure Through Only mode.
To Configure Through Only Mode

1. Type protocol through and press Enter to set the CCU to Through Only mode.
51:00:3f*CCU2>protocol through Through Only Mode
2. Type ip ethernet <aaa.bbb.ccc.ddd> <net mask> and press Enter to set the CCU IP address. <aaa.bbb.ccc.ddd> is the CCU radio IP address <net mask> is the CCU radio IP address subnet mask
3. Type ip gateway <aaa.bbb.ccc.ddd> <net mask> and press Enter to set the CCU IP address. <aaa.bbb.ccc.ddd> is the CCU gateway IP address, which is also the IP address of the gateway router <net mask> is the CCU radio IP address subnet mask


51:00:3f*CCU2>protocol Through Only Mode

51:00:3f*CCU2>ip Modem:
14
lms052_ap_01
IP Address: 192.168.10.8 / 24 IP Subnet : 192.168.10.0 ( 255.255.255.0 ) Gateway IP Address: 192.168.10.9
You must also configure all EUMs and subscriber PCs connected to the CCU to have IP addresses on IP subnets corresponding to addresses on the gateway router interface, and have the corresponding gateway router IP address as their gateway. DHCP is an excellent method to do this. Note that in Through Only mode, subscriber to subscriber communication will require special forwarding in the gateway router.
2.5
Configuring DHCP Relay

To configure DHCP relay Determine the DHCP server IP address. Determine the Relay Agent Information Circuit ID for this CCU, if RAI is desired. Enable DHCP Relay. Add the DHCP server(s) to the CCU. Optionally filter Ethernet side requests.
To Enable DHCP Relay

1. Type dhcp enable and press Enter. 2. Type save or commit and press Enter.
To Add a DHCP Server

1. app Series: Type dhcp relay add <aaa.bbb.ccc.ddd> <net mask> [ccuid] ccu Series: Type dhcp relay add <aaa.bbb.ccc.ddd> [ccuid] and press Enter. <aaa.bbb.ccc.ddd> is the IP address of the DHCP server you want to add. <net mask> is the net mask of the DHCP server. This is only used with the app series of executable image - see APCD-LM057 Feature Support Matrix. Omit for all other models. [ccuid] is a string identifying this CCU to the DHCP server. It is used as the Agent Circuit ID in the Relay Agent Information Option. If you leave [ccuid] blank for a particular server, the Relay Agent Information Option is not added when it is relayed to that server. If [ccuid] is filled in, the Relay Agent Information Option is added. Refer to LMS8000/LMS4000 CLI Reference Manual for more information. 2. Repeat step 1 for any alternate DHCP servers in your network. Vecima recommends that your network have at least one alternate DHCP server. 3. Type save or commit and press Enter.
lms052_ap_01
15
To Filter Ethernet Port DHCP Requests

By default, requests received from either the radio or Ethernet ports are relayed to the DHCP servers. If you do not want requests received on the Ethernet port (that is, from hosts on the Ethernet port side of the CCU) to be relayed, you can enable filtering on the Ethernet port. 1. Type dhcp relay filter enable and press Enter. 2. Type save or commit and press Enter. The following example Enables DHCP relay Adds a DHCP server with IP address 192.168.50.1 with no circuit id (RAI will not be added) Adds an alternate DHCP server with IP address 192.168.50.15 and circuit id myCCU Filters out requests from the Ethernet side Saves the new settings Displays the DHCP status
51:00:3f*CCU2>dhcp DHCP Relay Enabled DHCP Relay Enabled 51:00:3f*CCU2>dhcp enable for clients on the Ethernet Interface. for clients on the Radio Interface. relay add 192.168.50.1
DHCP Relay Server Table: IP Address . . . . . : 192.168.50.1 51:00:3f*CCU2>dhcp relay add 192.168.50.15 myCCU DHCP Relay Server Table: IP Address . . . . . : 192.168.50.1 IP Address . . . . . : 192.168.50.15 Circuit Id . . . . . : myCCU 51:00:3f*CCU2>dhcp relay filter enable DHCP Relay Disabled for clients on the Ethernet Interface. DHCP Relay Enabled for clients on the Radio Interface. 51:00:3f*CCU2>save Basic Config saved Port Filter Config saved Network Configuration saved Authorization Database saved 51:00:3f*CCU2>dhcp relay DHCP Relay Disabled for clients on the Ethernet Interface. DHCP Relay Enabled for clients on the Radio Interface. DHCP Relay Server Table: IP Address . . . . . : 192.168.50.1 IP Address . . . . . : 192.168.50.15 Circuit Id . . . . . : myCCU
16
lms052_ap_01
2.6
Configuring Port Filtering

The port filter table is described in Port Filter Table (CCU and EUM) on page 117. To add a port filter Determine the port number you want to filter. Determine whether you want to filter UDP, TCP, or both types of packets. Add the port filter to the CCU.
To Add a Port Filter

1. Type port add <number> <type> and press Enter. <number> is the number of the port you want to filter. <type> is the type of IP packet you want to filter, either udp, tcp, or both. 2. Repeat step 1 for any other ports that you want to filter out. 3. Type save or commit and press Enter. CAUTION: Dont add port 23 TCP or you will block telnet access to the CCU. The following example Configures the CCU to filter both UDP and TCP packets on ports 137, 138, 139, 445 and 1512, Saves the new settings, and Displays the TCP/UDP port filters.
51:00:3f*CCU2>port add 137 both Port added 51:00:3f*CCU2>port add 138 both Port added 51:00:3f*CCU2>port add 139 both Port added 51:00:3f*CCU2>port add 445 both Port added 51:00:3f*CCU2>port add 1512 both Port added 51:00:3f*CCU2>save Basic Config saved Port Filter Config saved Network Configuration saved Authorization Database saved 51:00:3f*CCU2>port PORT FILTERS Port Filter --------------------------------137 both 138 both 139 both 445 both 1512 both
lms052_ap_01
17
----------------------------------
The CCU factory default settings have ports 137, 138, 139, 445, and 1512 filtered out for both TCP and UDP, to prevent Network Neighborhood from seeing other end users computers. NOTE: These factory defaults are stored in the supplied port.cfg file. Windows Vista uses several other ports (UDP 3702, TCP 5357, and TCP 5358), but as these are officially ephemeral ports also used by other protocols, blocking them may have unexpected and difficult to diagnose effects.
2.7
Configuring the SNTP UTC Time Clock

Configuring the SNTP UTC Time Clock involves the following procedures, each of which is explained in detail on the following pages: Add an NTP server, if the one to which you want the CCU to synchronize has not already been added. NTP servers are accessed in the order listed. Enable the SNTP client, to force the CCU to synchronize to an NTP server. Enable the SNTP relay, if you want the EUMs to be synchronized to the CCU.
To Add an NTP Server

1. Type time server add <aaa.bbb.ccc.ddd> and press Enter. <aaa.bbb.ccc.ddd> is the IP address of the NTP server you are adding. 2. Type save or commit and press Enter.
51:00:3f*CCU2>time server add 10.0.0.1 Added NTP Servers: 192.168.0.201 10.0.0.1 51:00:3f*CCU2>save Basic Config saved Port Filter Config saved Network Configuration saved Authorization Database saved
NOTE: It is a good idea to ping the time servers from the CCU before adding them, to ensure you have connectivity. Note that not all NTP servers will respond to pings.
To Enable the SNTP Client

Enabling the time client on the CCU causes the CCU to get the time from the server on a regular basis. 1. Type time client enable and press Enter. 2. Type save or commit and press Enter.
18
lms052_ap_01
51:00:3f*CCU2>time client enable Time Client enabled
To Enable SNTP Relay

Enabling time relay on a CCU causes the CCU to forward the time to the EUMs. 1. Type time relay enable and press Enter. 2. Type save or commit and press Enter.
51:00:3f*CCU2>time relay enable SNTP Relay Enabled : Yes Destination : Primary Radio IP broadcast Period : 240
To Display the SNTP Configuration and NTP Server List

Type time relay and press Enter.
51:00:3f*CCU2>time relay SNTP Client and Relay Configuration ----------------------------------SNTP Relay Enabled : Yes Destination : Primary Radio IP broadcast Period : 240 SNTP Client Configuration Client (fetch only) Enabled: Yes Port: 123 NTP Servers: 192.168.0.201 10.0.0.1
To Display System Time

Type time and press Enter.
51:00:3f*CCU2>time 22-JUL-2004 16:19:01
To Force a Time Update

Type time relay period 0 and press Enter.
51:00:3f*CCU2>time relay period 0 Time relayed SNTP Relay Enabled : Destination : Period :
Yes Primary Radio IP broadcast 240
lms052_ap_01
19
NOTE: A period of 0 does not change the time client period, it just immediately updates the time. Enter a period between 1-10000 in minutes to change the period.
2.8
Configuring SNMP
To fully configure SNMP Set the SNMP contact (name of the Network Operator, for example). Set the SNMP system location (physical location of the CCU, for example). Add an SNMP read community. Add an SNMP write community. Add an SNMP trap community.
To Set the SNMP Contact

1. Type snmp contact <contact> and press Enter. <contact> is text field, often used for a contact name and phone number, a URL, or an email address, from 1-80 characters in length. 2. Type save or commit and press Enter.
To Set the SNMP System Location

1. Type snmp location <location> and press Enter. <location> is the location of the CCU, from 1-80 characters in length. 2. Type save or commit and press Enter.
To Add an SNMP Read Community

1. Type snmp community add <community> read and press Enter. <community> is the name of the read community string. By default, no community strings are entered, so no one has SNMP access. The read community string can be from 1-31 characters in length, but spaces are not allowed. 2. Type save or commit and press Enter.
To Add an SNMP Write Community

1. Type snmp community add <community> write and press Enter. <community> is the name of the write community string. By default, no community strings are entered, so no one has SNMP access. The write community string can be from 1-31 characters in length, but spaces are not allowed. 2. Type save or commit and press Enter.
20
lms052_ap_01
To Add an SNMP Trap Server

1. Type snmp trap add <aaa.bbb.ccc.ddd> <community> and press Enter. <aaa.bbb.ccc.ddd> is the IP address of the trap server <community> is the name of the community on the trap server, from 1-63 characters in length. 2. Type save or commit and press Enter. The following example Sets the SNMP contact as Vecima, Sets the SNMP location as Calgary_South, Adds SNMP read community Vecima_Calgary, Adds SNMP write community Vecima_Calgary, Adds SNMP trap server Vecima_Calgary, IP address 10.0.1.68, Saves the new settings, and Displays the SNMP settings.
Example:
51:00:3f*CCU2>snmp contact Vecima Contact: Vecima 51:00:3f*CCU2>snmp location Calgary_South Location: Calgary_South 51:00:3f*CCU2>snmp community add Vecima_Calgary read SNMP Read Communities: Vecima_Calgary SNMP Write Communities: 51:00:3f*CCU2>snmp community add VC_wr write SNMP Read Communities: Vecima_Calgary SNMP Write Communities: VC_wr 51:00:3f*CCU2>snmp trap add 10.0.1.68 VC_trp SNMP Traps: 10.0.1.68 VC_trp 51:00:3f*CCU2>save Basic Config saved Port Filter Config saved Network Configuration saved Authorization Database saved 51:00:3f*CCU2>snmp Contact: Vecima Location: Calgary_South SNMP Read Communities: Vecima_Calgary SNMP Write Communities: VC_wr SNMP Traps: 10.0.1.68 VC_trp
lms052_ap_01
21
2.9
Configuring VoIP Detection and Priority Classification

Voice over IP detection and priority classification is controlled at the CCU, with the parameters passed on to EUMs as they register. Priority classification can be enabled or disabled for the entire sector. When enabled, it is only applied to traffic for EUMs which have priority classification enabled during authorization. VoIP detection and priority classification is based on three tests, each of which is parameterized.
To Enable Priority Classification for the Sector

1. Type priority enable and press Enter.
To Mark a DiffServ Codepoint as High Priority

1. Type priority diffserv set <codepoint> and press Enter. where codepoint is between 0 and 63 (decimal). Each of the 64 codepoints can be marked as high priority or not. Note that code points are individually enabled, not in ranges. Clear all codepoints to disable this rule.
To Set the VLAN Priority Threshold

1. Type priority vlan <threshold> and press Enter. where threshold is between 0 and 8. Packets with a VLAN tage greater than or equal to this will be marked high priority. Unmarked packets are treated as level 3. Set to 8 to disable this rule.
To Configure RTP Detection

1. Type priority rtp max <length> and press Enter. Packets greater than length bytes are not marked high priority by the RTP rule. Set to 0 to disable this rule. 2. Type priority rtp port set <pair> <start> <end> and press Enter. A UDP packet with source and destination port in one of the five ranges may be marked high priority. Pair, between 0 and 4, indicates which range to define. The range is start to end inclusive. 3. Repeat step 2 for up to 5 ranges. The following example Enables priority classification Sets codepoint 46 (or 0x2e, expedited forwarding) Sets the VLAN threshold to 5 Sets the RTP max length to 250 Sets two RTP port ranges of 10000 to 12000 and 22000 to 30000 Saves the new settings and Displays the new settings
Example:
51:00:3f*CCU2>priority enable
22
lms052_ap_01
Priority Packet processing enabled. 51:00:3f*CCU2>priority diffserv set 46 Enabled Diff Serv Code Points: 46. 51:00:3f*CCU2>priority vlan 5 vlan threshold: 5 51:00:3f*CCU2>priority rtp max 250 RTP maximum packet length: 250 51:00:3f*CCU2>priority rtp port set 0 10000 20000 Prioritized Starting Ending Port Pair Port Number Port Number ----------- ----------- ----------0 10000 20000 1 00000 00000 2 00000 00000 3 00000 00000 4 00000 00000 51:00:3f*CCU2>priority rtp port set 1 22000 30000 Prioritized Starting Ending Port Pair Port Number Port Number ----------- ----------- ----------0 10000 20000 1 22000 30000 2 00000 00000 3 00000 00000 4 00000 00000 51:00:3f*CCU2>save Basic Config saved Port Filter Config saved Network Configuration saved Authorization Database saved 51:00:3f*CCU2>priority Packet Prioritization: Enabled. vlan threshold: 5 Enabled Diff Serv Code Points: 46. RTP maximum packet length: 250 Prioritized Starting Ending Port Pair Port Number Port Number ----------- ----------- ----------0 10000 20000 1 22000 30000 2 00000 00000 3 00000 00000 4 00000 00000
2.10
Adding EUMs to the Authorization Table

EUMs can be authorized either statically in the authorization table or dynamically through a RADIUS server (see Configuring a RADIUS Server on page 39). The authorization includes access to the network, grade of service offered and whether priority classification is applied to traffic to and from that EUM, authentication key policy and possibly an authentication key and, for models supporting OFDM1, the range of transmit modulation schemes permitted to this EUM. An EUM that doesnt appear in the table is given the default grade of service, priority enable and modulation schemes without encryption if RADIUS authorization is not enabled.
1. See LMS8000/LMS4000 Feature Support Matrix for OFDM support.
lms052_ap_01
23
minscheme and maxscheme are either a number or name from Table 1. Table 1 Modulation Scheme Names and Numbers Number 3 4 5 6 7 8 9 10 11 Name CCK2 BPK1 BPK2 QPK1 QPK2 16Q1 16Q2 64Q1 64Q2 Raw Signalling Rate 2.75 Mbps 1.5 Mbps 2.25 Mbps 3 Mbps 4.5 Mbps 6 Mbps 9 Mbps 12 Mbps 13.5 Mbps
Most of the time, the range of transmit modulation schemes can be left at the default of 4 (BPK1) to 11 (64Q2) and adaptive modulation will select the appropriate rate. In this case, the minscheme and maxscheme parameters can just be omitted below. Note that they are ignored anyway for EUMs or CCUs that dont support OFDM and adaptive modulation. To enable secure authentication and user data encryption for an EUM, set the authentication key policy to required and enter the same authentication key (or passphrase) that is configured in the EUM. Note that the security is based on the secrecy of that key. Otherwise authentication is based on the EUM MAC address and encryption is disabled.
To Add an EUM to the CCU Authorization Table Statically with policy none
1. Type auth add <eumid> <gos> <priority> [minscheme] [maxscheme] and press Enter. where gos is the grade of service that you want to assign to the EUM, one of: be (best effort), bronze, silver, gold, or denied. priority is enable or disable to control priority classification of traffic to and from that EUM. minscheme and maxscheme are the minimum and maximum transmit modulation schemes the CCU will use for adaptive modulation for this EUM. They are ignored if the EUM does not support OFDM. Omit them if the CCU does not support OFDM. The defaults (from auth default) are used if they are omitted. The authentication key policy will be set to none. 2. Type save or commit and press Enter. The auth command takes effect immediately. The following example
24
lms052_ap_01
Adds EUM ID 64:12:34 to the Authorization Table and assigns it the gold grade of service, key policy none with priority classification enabled and allows adaptation from BPK2 to 16Q2:
51:00:3f*CCU2>auth add 64:12:34 gold enable bpk2 16q2 Added to authorization table 64:12:34 GOS: gold, Priority Classification enabled, Key policy none Min Scheme 5 (BPK2) Max Scheme 9 (16Q2) (if OFDM capable) 51:00:3f*CCU2>auth Authorization Table EUM ID GOS CLASS PRIORITY MIN MAX KEY POLICY TYPE ---------------------------------------------------------64:00:72 bronze disabled 3 3 none static 64:12:34 gold enabled 5 9 none static Total of 2 entries. MIN/MAX apply if OFDM capable. Default GOS bronze, priority disabled, tx modulation: 3 (CCK2) to 11 (64Q2) Broadcast Traffic is currently not encrypted
To Add an EUM to the CCU Authorization Table Statically with policy required
1. Type auth key <eumid> <gos> <priority> [minscheme] [maxscheme] and press Enter or type auth passphrase <eumid> <gos> <priority> [minscheme] [maxscheme] and press Enter where gos is the grade of service that you want to assign to the EUM, one of: be (best effort), bronze, silver, gold, or denied. priority is enable or disable to control priority classification of traffic to and from that EUM. minscheme and maxscheme are the minimum and maximum transmit modulation schemes the CCU will use for adaptive modulation for this EUM. They are ignored if the EUM does not support OFDM. The defaults (from auth default) are used if they are omitted. 2. auth key will prompt for a 64 hexadecimal character secret authentication key. Type the same key that was entered at the EUM and press Enter. auth passphrase will prompt for an 8 to 63 character secret passphrase. Type the same passphrase that was entered at the EUM and press Enter. Repeat it exactly for verification. The authentication key policy will be set to required. 3. Type save or commit and press Enter. The auth command takes effect immediately. The following example Adds EUM ID 60:12:34 to the Authorization Table, and assigns it the gold grade of service, an authentication key and key policy required with priority classification enabled:
60:00:43> auth key 60:12:34 gold enable Enter Key (64 hex chars) | | | | | | | | :abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890 Added to authorization table 60:12:34 GOS: gold, Priority Classification enabled, Key policy required 60:00:43> auth Authorization Table
lms052_ap_01
25
EUM ID GOS CLASS PRIORITY KEY POLICY TYPE ---------------------------------------------------------60:12:34 gold enabled required static Total of 1 entries Default GOS be, priority disabled
To Set the Default Grade of Service and Priority Enable

1. Type auth default <gos> <priority> [minscheme] [maxscheme] and press Enter. where gos, priority, minscheme and maxscheme can have similar values as above. These values are given to EUMs when they register if no entry is found and RADIUS is not enabled. 2. Type save or commit and press Enter. The defaults change immediately, but EUMs already registered using the previous defaults will continue to get the gos, priority and schemes they registered with. The following example Sets the default grade of service to best effort and disables priority classification and allows the full range of adaptation by default.
51:00:3f*CCU2>auth default be disable 4 11 Default GOS be, priority disabled, tx modulation: 4 (BPK1) to 11 (64Q2)
2.11
Configuring the CCU RADIUS Client

To configure the CCU RADIUS client: 1. Type auth radius enable and press Enter to enable RADIUS Authorization.
51:00:3f*CCU2>auth radius enable Radius Authorization Enabled, Period: 60 minutes Radius Accounting is disabled Radius Primary Server : 0.0.0.0 Radius Secondary Server: 0.0.0.0 Radius Server Ports: Authorization 1812 Accounting 1813
2. Type auth radius primary [addr] and press Enter, then type the RADIUS shared secret password and press Enter. where addr is the primary RADIUS server IP address.
51:00:3f*CCU2>auth radius primary 192.168.10.9 Enter password (up to 16 chars): ********* Radius Authorization Enabled, Period: 60 minutes Radius Accounting is disabled Radius Primary Server : 192.168.10.9 Radius Secondary Server: 0.0.0.0 Radius Server Ports: Authorization 1812 Accounting 1813
NOTE: This password must match the Shared Secret Password entered at the RADIUS server.
26
lms052_ap_01
3. If your network includes a second RADIUS server, set the secondary RADIUS server IP address and Shared Secret Password. Otherwise, set the secondary RADIUS server IP address to none.
51:00:3f*CCU2>auth radius secondary 172.16.10.47 Enter password (up to 16 chars): ********** Radius Authorization Enabled, Period: 60 minutes Radius Accounting is disabled Radius Primary Server : 192.168.10.9 Radius Secondary Server: 172.16.10.47 Radius Server Ports: Authorization 1812 Accounting 1813
4. (Optional) Type auth radius accounting enable to enable RADIUS accounting.

51:00:3f*CCU2>auth radius accounting enable Radius Authorization Enabled, Period: 60 minutes Radius Accounting is enabled (update mode) Radius Primary Server : 192.168.10.9 Radius Secondary Server: 172.16.10.47 Radius Server Ports: Authorization 1812 Accounting 1813
5. (Optional) Type auth radius ports [authport] [acctport] and press Enter to specify authorization and accounting port numbers. The official RADIUS ports are 1812 and 1813 (the defaults), but some older RADIUS servers use 1645 and 1646. where authport is the authorization port and acctport is the accounting port number.
51:00:3f*CCU2>auth radius ports 1812 1813 Ports set Radius Server Ports: Authorization 1812 Accounting 1813
6. Save settings.
NOTE: RADIUS settings take effect immediately. 7. Display the RADIUS settings.
51:00:3f*CCU2>auth radius Radius Authorization Enabled, Period: 60 minutes Radius Accounting is enabled (update mode) Radius Primary Server : 192.168.10.9 Radius Secondary Server: 172.16.10.47 Radius Server Ports: Authorization 1812 Accounting 1813
NOTE: Use the stats auth command to view RADIUS statistics, which are useful for troubleshooting purposes. Also, use sys log to detect if there are any malformed RADIUS packets.
lms052_ap_01
27
Configuring the EUM
For EUMs that support automatic frequency discovery, DHCP client and autoconfiguration1 in networks configured to support them, the EUM needs no configuration before installation - it is ready to go out of the box. EUMs can also be configured manually. Refer to Serial Number, MAC Address, and Station ID on page 8. This chapter covers the following procedures: Setting the EUM Password on page 30 Configuring the EUM RF Parameters on page 30 Configuring EUM IP Parameters on page 33 Configuring Security on page 34 Configuring Port Filtering on page 35 Configuring SNMP on page 35 Configuring the Customer List on page 35
See Configuring a RADIUS Server on page 39 for details on autoconfiguration. Before you configure the EUM Familiarize yourself with the CLI commands, syntax and shortcuts, outlined in LMS8000/LMS4000 CLI Reference Manual. This document provides a complete list of the available EUM commands, some of which are not discussed in this section. Connect to the EUM through a telnet session. See Access Interface on page 131. CAUTION: Remember to regularly enter save or commit and press Enter, to save your configuration changes to memory. As well, some parameters will not take effect until you reboot the unit, specifically the RF frequency and IP addressing.
1. See LMS8000/LMS4000 Feature Support Matrix.
lms052_ap_01
29
3: Configuring the EUM
3.1
Setting the EUM Password

To Change the EUM Password
1. Type password and press Enter. 2. At the Enter Current Password prompt, type the old password. 3. At the Enter New Password prompt, type the new password. TIP: Passwords are alphanumeric and case-sensitive. For example, abc is not the same as aBc. 4. At the Verify password prompt, type the new password again. The system displays a message that your password has been successfully changed.
64:02:6c-myEum>password Enter Current Password: ******** Enter New Password (0-16 characters): ********* Verify password: ********* Saving new password Password Changed
CAUTION: Remember to record the password. Unlocking the EUM can only be performed by contacting Vecima Technical Support.
3.2
Configuring the EUM RF Parameters

The EUM radio frequency can be set manually, or, for EUMs that support it1, the EUM can automatically discover the best available frequency. Optionally, the transmit power level, diversity mode and/or adaptive modulation parameters can be set. All of these can also be done through autoconfiguration, see Configuring a RADIUS Server on page 39 for details.
To Set the EUM Operating Frequency Manually

1. Type radio frequency <frequency> and press Enter. <frequency> is the EUM operating frequency in tenths of a MHz. For example, 917.0 MHz is entered as 9170. 2. Type save or commit and press Enter.
1. See LMS8000/LMS4000 Feature Support Matrix for Auto Frequency Discovery and Nomadic mode support.
30
lms052_ap_01
3. Before the new radio frequency will take effect, you must reboot the EUM by typing reset and pressing Enter.
To Configure Automatic Frequency Discovery

1. Type radio frequency auto <break> or radio frequency nomadic <break> and press Enter. In automatic mode the EUM will discover the best CCU at power up and stay on that frequency unless the CCU goes off for 2 minutes. In nomadic mode1 the EUM will find a new frequency if the packet error rate with the CCU goes above 15% for 15 seconds. Break is a time in seconds that the Ethernet port will be disabled when a new frequency has to be found. With some operating systems, including Windows XP, a directly connected PC will get a new DHCP address when the Ethernet port goes down for more than 5 seconds (use 7). Omit or set to zero to disable this feature. 2. Optionally type radio search recommended or radio search default and press Enter. By default all available frequencies are searched during discovery. Recommended sets the list of frequencies searched to the most commonly used frequencies (905.2, 905.4, 908.2, 908.4, 908.6, 911.4, 911.6, 911.8, 914.8, 915.0, 915.2, 918.2, 918.4, 918.6, 921.4, 921.6, 921.8, 924.6, 924.8 MHz). Use add and delete to set individual frequencies. 3. Optionally type radio search add <frequency> or radio search delete <frequency> and press Enter. This will add or delete a specific frequency. Frequency is specified in tenths of a MHz. For example, 917.0 MHz is entered as 9170. Adding one to the default all frequencies case results in only that frequency being set. 4. Type save or commit and press Enter. 5. To restart the frequency search type radio search start. Take care with this command if connected over the air as you may lose contact with the unit.
To Set the EUM Power Level

This power level does not include antenna system gain. 1. Type radio rf <power level> and press Enter. <power level> is the EUM transmit power level, either: the desired power level, in dBm, any integer value in the range 15 - 26 inclusive, high (+26 dBm), or low (+15 dBm).
NOTE: Use the HIGH power level unless your site has unique requirements for which a numerically set power level, or the LOW power level, is more appropriate. For example, the capability to numerically set the power level may be useful in high-density
1. See LMS8000/LMS4000 Feature Support Matrix for nomadic mode support.
lms052_ap_01
31
environments, where site-to-site interference is a problem. LOW power is recommended in test lab environments. 2. Type save or commit and press Enter. Changes to the transmit power level take effect immediately, they do not require an EUM reboot.
To Set the EUM Antenna Diversity Mode

Models that support antenna diversity control1 and a diversity antenna allow setting which antenna will be used to receive and transmit on. You can set it to receive on only one antenna or the other (A or B), or to automatically select the best antenna to receive on based on signal quality (diversity). Similarly, you can set it to transmit on only one antenna or the other (A or B) or to transmit on the antenna that last received a good packet (diversity). 1. Type radio diversity <rx> <tx> and press Enter. <rx> is A | B | diversity and controls which antenna will be used to receive packets. <tx> is A | B | diversity and controls which antenna will be used to transmit packets.
For example, radio diversity diversity A will use receive diversity, but transmit on antenna A. NOTE: For the integrated high-gain polarization diversity antenna, the A antenna is polarized perpendicular to the long axis of the unit and the B antenna is polarized parallel to the long axis of the unit.
To Set Adaptive Modulation Parameters

For EUMs supporting adaptive modulation2 the range of modulation schemes that the EUM may use to transmit to the CCU can be constrained. By default, the full range of OFDM schemes is used - 4 (BPK1) to 11 (64Q2). 1. Type radio modulation <minscheme> [maxscheme] and press Enter. <minscheme> is the minimum allowed modulation scheme. Either the number or name from Table 1 on page 24 can be entered. [maxscheme] is the maximum allowed modulation scheme, taking the same values. If omitted, it is set the same as minscheme and only that scheme is used, effectively disabling adaptive modulation. 2. Type save or commit and press Enter. For example, radio modulation bpk1 64q2 will set the range to the default full range of OFDM modulations. The following example Sets the EUM operating frequency to 917.2 MHz,
1. See APCD-LM057 Feature Support Matrix for antenna diversity control support. 2. See LMS8000/LMS4000 Feature Support Matrix for Adaptive Modulation support.
32
lms052_ap_01
Sets the transmit power level to high, Enables receive and transmit antenna diversity, Limits the transmit modulation schemes to adapt between bpk2 and 16q2, Reboots the EUM so that the new parameters take effect, and Displays the EUM RF parameters.
64:02:6c-myEum>radio frequency 9172 Radio Search Mode: Fixed 9172 Break on link fail disabled. 64:02:6c-myEum>radio rf high Max RF Power: 26 dBm 64:02:6c-myEum>radio diversity diversity diversity Diversity mode set Rx/Tx Antenna Diversity: diversity / diversity 64:02:6c-myEum>radio modulation bpk2 16q2 Transmit Modulation Limits: 5 (BPK2) to 9 (16Q2) 64:02:6c-myEum>save Basic Config saved Port Filter Config saved 64:02:6c-myEum>reboot rebooting ... 64:02:6c-myEum>radio Max RF Power: 26 dBm Fixed Mode - Locked on 51:00:3f at frequency 9172 (bcf 9172)
3.3
Configuring EUM IP Parameters

The EUM IP address, netmask and gateway can be set manually, or, for EUMs that support a DHCP client1, the EUM can discover them itself from a DHCP server.
To Set the EUM IP Address and Gateway Manually

1. Type ip ethernet <aaa.bbb.ccc.ddd> <net mask> and press Enter. <aaa.bbb.ccc.ddd> is the EUM IP address. <net mask> is the number of bits set in the net mask (1 to 32). CAUTION: The EUM only accepts subnet masks using the shorthand notation; for example, it accepts 16, but not ffff0000 or 255.255.0.0. 2. Type ip gateway <aaa.bbb.ccc.ddd> and press Enter. <aaa.bbb.ccc.ddd> is the EUM gateway IP address. 3. Type save or commit and press Enter. 4. Before the new EUM IP address and gateway will take effect, you must reboot the EUM by typing reset and pressing Enter. 1. See LMS8000/LMS4000 Feature Support Matrix for EUM DHCP Client support.
lms052_ap_01
33
To Enable the EUM to get its IP address automatically with DHCP

1. Type ip ethernet dhcp and press Enter. 2. Type save or commit and press Enter. 3. Before the EUM will get a new IP address and gateway, you must reboot the EUM by typing reset and pressing Enter. The following example Sets the EUM Ethernet IP address to 172.16.6.4 /22, Sets the EUM gateway IP address to 172.16.6.1, Saves the new settings, Reboots the EUM so that the new parameters take effect, and Displays the EUM IP parameters.
64:02:6c-myEum>ip ethernet 172.16.6.4 22 IP Address: 172.16.6.4 / 22 IP Subnet : 172.16.4.0 ( 255.255.252.0 ) 64:02:6c-myEum>ip gateway 172.16.6.1 Gateway Route changed Gateway IP Address: 172.16.6.1 64:02:6c-myEum>save Basic Config saved Port Filter Config saved 64:02:6c-myEum>reboot rebooting ... Password: 64:02:6c-myEum>ip DHCP Enabled : NO IP Address: 172.16.6.4 / 22 IP Subnet : 172.16.4.0 ( 255.255.252.0 ) Gateway IP Address: 172.16.6.1
3.4
Configuring Security
To enable secure authentication and user data encryption on EUMs that support it1, set the authentication key policy to required or allowed and enter an authentication key or passphrase. The same authentication key or passphrase must be configured in the CCU authorization table (see Configuring the CCU on page 7) or RADIUS server for this EUM. If the key policy is none, authentication is based on the EUM MAC address and encryption is disabled.
1. See LMS8000/LMS4000 Feature Support Matrix for Secure Authentication support.
34
lms052_ap_01
To Set the EUM Authentication Key and Key Policy

1. Type auth key <policy> and press Enter OR type auth passphrase <policy> and press Enter. where policy is either required, allowed, or none. 2. auth key will prompt for a 64 hexadecimal character secret authentication key. Type a secret key (with no spaces) and press Enter. auth passphrase will prompt for an 8 to 63 character secret passphrase. Type the passphrase and press Enter. Repeat it exactly for verification. 3. Type save or commit and press Enter. 4. The policy will not take effect until either a reboot or you restart CCU discovery by typing radio enable and pressing Enter. The following example sets the key policy to required and sets the authentication key
60:05:11> auth key required Enter Key (64 hex chars) | | | | | | | | :abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890 Key Set Encryption required
3.5
Configuring Port Filtering

The procedure for configuring port filtering on an EUM is identical to the procedure for a CCU. See Configuring Port Filtering on page 17.
3.6
Configuring SNMP
The procedure for configuring SNMP on an EUM is identical to the procedure for a CCU. See Configuring SNMP on page 35. For EUMs that support it1, this can also be done through autoconfiguration. See Configuring a RADIUS Server on page 39 for details.
3.7
Configuring the Customer List

You can set the maximum number of customers or PCs (customer_max) that can concurrently access the radio link through the EUM, as described in Bridge Table Entries on page 128. For
1. See LMS8000/LMS4000 Feature Support Matrix for autoconfiguration support.
lms052_ap_01
35
EUMs that support it1, this can also be done through autoconfiguration. See Configuring a RADIUS Server on page 39 for details. TIP: When you are locally troubleshooting the EUM installation, if customer_max is set to 1 and you want to substitute and use a known-working PC in place of the end-users PC, you will have to reset the EUM or wait 10 minutes for the Bridge Table to time out before you will be able to access the EUM.
To Set customer_max
1. Type cust max <value> and press Enter. <value> is the maximum number of customers (PCs), from 1-50. 2. Type save or commit and press Enter. The following example Sets customer_max to 3, Saves the new setting, and Displays the value of customer_max.
64:02:6c-myEum>customer max 3 Maximum Number of Customers: 3 64:02:6c-myEum>save Basic Config saved Port Filter Config saved 64:02:6c-myEum>customer max Maximum Number of Customers: 3
1. See LMS8000/LMS4000 Feature Support Matrix for autoconfiguration support.
36
lms052_ap_01
Configuring a DHCP Server
Using a DHCP server to allocate IP address information to subscriber PCs, EUMs and other network elements greatly simplifies network management and is highly recommended in most networks. As there are many different DHCP servers available and in use in networks, configuration of the server itself is beyond the scope of this document. This section presents detailed information about the LMS8000 / LMS4000 system that will assist in configuring a DHCP server to take advantage of the LMS8000 / LMS4000 features. Different DHCP servers provide different levels of support for these features. IP addresses obtained through DHCP can be reconfigured by expiring the DHCP leases and reconfiguring the DHCP pools, the gateway router, and any other equipment on that IP subnet. This makes the network more scalable within limits. In general, it is a good idea to limit lease lengths, in case you have to change the IP plan. If DHCP Relay is not enabled, the DHCP server will need to be in the same Ethernet broadcast domain as the subscribers. In Switched Ethernet mode, this includes the CCU Ethernet segment, but in routed mode, it only includes EUM Ethernet segments. The DHCP server could be attached to an EUM, but this is not recommended.
4.1
CCU DHCP Relay and Relay Agent Information Option

When enabled, the CCU acts as a DHCP relay. DHCP requests broadcast on the radio network (by subscriber PCs and EUMs for example) are intercepted by the CCU and relayed to each of the servers in the list. See Configuring DHCP Relay on page 15 for details on enabling DHCP relay and adding servers to the list. If the entry for a given server includes a CCUID, the CCU appends the Relay Agent Information option (RFC3046) to the packet. The Agent Circuit ID Sub-option is set to the string given as the CCUID for that server. The Agent Remote ID Sub-option is set to the EUMID of the EUM through which the request arrived as a string in the form XX:XX:XX (e.g. 60:12:34).
lms052_ap_01
37
4: Configuring a DHCP Server
Note that unicast packets, such as DHCP renew requests, are directed to the DHCP server and are not relayed, so they will arrive without the relay agent information option.
4.2
EUM DHCP Client

When DHCP client is enabled, the EUM includes several useful pieces of information with each DHCP message that can be used to determine which IP address or pool to allocate from. See Configuring EUM IP Parameters on page 33 for details on enabling DHCP client. As with most Ethernet devices, the Client ID option is set to the Ethernet MAC address. The host name is a string in the form eumXX-XX-XX where XX:XX:XX is the EUMID. Note that this differs from the usual string form of the EUMID because the host name must begin with a letter and may not contain :. The Vendor Class is set to Vecima and the Vendor Specific option with tag 1 is the hardware type as a string (e.g. EUM3006) as shown in the PCF display.
38
lms052_ap_01
Configuring a RADIUS Server
The LMS8000 / LMS4000 system can use RADIUS for EUM authorization, authentication and key management, provision of service parameters and remote EUM configuration. As there are many different RADIUS servers available and in use, configuration of the server itself is beyond the scope of this document. This section presents detailed information about the LMS8000 / LMS4000 system that will assist in configuring RADIUS server and database(s) to take advantage of LMS8000 / LMS4000 features. RADIUS is a standard, robust and secure way for the CCU to access a network operators database(s) of information about individual EUMs. The RADIUS server acts as an interface between the RADIUS protocol and whatever database is being used. The database may reside within the RADIUS server, be a simple text file accessed by the server, or be a fullfledged enterprise database. In the Open Access application where there are multiple service providers, the RADIUS server may access multiple databases maintained by the individual service providers. The choice of database design will depend on the application. The CCU supports a secondary RADIUS server, so if the primary server is unavailable, the backup can respond to maintain service. The CCU allows up to 5 seconds for a response. Upon registration, and periodically thereafter, the CCU makes a RADIUS access-request for each EUM. The RADIUS server can reply with a RADIUS access-reject message, which will cause the EUM to be denied service, or with a RADIUS access-accept message, which can can also contain service level, authentication key and configuration attributes. The accessaccept message must contain a Vecima-Grade-of-Service attribute to be considered valid. The Vecima attributes are detailed in RADIUS Attributes on page 41. Periodically and on deregistration, the CCU may send RADIUS accounting information for each EUM. Note that RADIUS packets are digitally signed for authentication purposes, but not encrypted.
5.1
RADIUS Authorization
For each RADIUS access-request message sent by the CCU, the username is the EUMID, a string in the form of XX:XX:XX (for example, 61:23:45), the NAS IP address is the CCU
lms052_ap_01
39
5: Configuring a RADIUS Server
Ethernet IP address, the NAS port is 1 and the password is the fixed string buywavc (this is different from the shared secret password, which is used to verify that the CCU signed it). Each RADIUS access-accept message must have at least the Vecima-Grade-of-Service attribute (to determine the GOS offered to the EUM) and may contain a VecimaAuthentication-Key or MS-MPPE-Recv-Key attribute (which also sets the key policy to required) the Vecima-Priority-Enable attribute (which determines whether traffic to or from the EUM is priority classifed or not) and autoconfiguration attributes. Attributes are defined in RADIUS Attributes on page 41. TIP: If the RADIUS server does not respond to an initial request, the CCU will assign the default grade of service. Since the default GOS is otherwise unused when RADIUS is enabled, it should be set to the desired GOS to assign when the RADIUS server is down.
5.2
RADIUS and Autoconfiguration

For EUMs that support autoconfiguration1, RADIUS attributes contained in the accessresponse are passed to the EUM to update various configuration parameters such as the password and SNMP community strings. The list of attributes is given in RADIUS Attributes on page 41. To protect the EUM from unauthorized access, the password is required in order for the autoconfiguration attributes to take effect. The current EUM password must be supplied as the Vecima-Current-Password or Vecima-New-Password attribute.
5.3
RADIUS Accounting
On registration, the CCU sends an accounting-start message for each EUM authorized through RADIUS. On a periodic basis, the CCU sends either an accounting-update (update mode), or an accounting-stop followed immediately by another accounting-start (stop/start mode). RADIUS accounting messages from the CCU have the EUMID as the username, CCU Ethernet IP address as the NAS IP Address, 1 as the NAS Port and a session id unique to the EUM and accounting session. A RADIUS accounting-update or accounting-stop message also contains the Input-Octets, Input-Packets, Output-Octets and Output-Packets attributes. Input is from the EUM to the CCU; Output is from the CCU to the EUM. Values are cumulative over the session.
1. See APCD-LM057 LMS4000 Feature Support Matrix for autoconfiguration support.
40
lms052_ap_01
5.4
RADIUS Attributes
The following Vecima (Vendor-Id 2979) vendor specific attributes are defined below. There are two different types. Grade-of-Service, Priority-Enabled, Authentication-Key and Downlink-Min/ Max-Modulation are interpreted by the CCU and affect the service level. The others are forwarded to the EUM and used to set parameters in the EUM. These parameters will only take effect if the correct password for the EUM is given in the Current-Password or NewPassword attribute. If secure authentication is enabled, attributes are passed to the EUM after the link is encrypted so that they are not exposed on the airlink. However, they are signed by not encrypted on the RADIUS server to the CCU link. These attributes are only included in Access-Accept packets.
5.4.1 Vecima-Grade-of-Service
This attribute contains the grade of service assigned to the user. It is a required attribute for all Access-Accept packets. A summary of the Vecima-Grade-of-Service attribute format is shown below. The fields are transmitted from left to right.
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Vendor-Type | Vendor-Length | Value +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Value (cont) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Vendor -Type Vendor -Length Value
1 for Vecima-Grade-of-Service 6 The Value field is a four octet enumeration. 1 - best effort 2 - bronze 3 - silver 4 - gold
5.4.2 Vecima-Priority-Enabled
This attribute determines whether VoIP traffic to and from an EUM will be classified and prioritized ahead of other traffic, and whether the EUM will enter the priority activation level when this traffic is present. When this attribute is disabled, VoIP traffic to and from that EUM is treated as normal traffic. A summary of the Vecima-Priority-Enabled Attribute format is shown below. The fields are transmitted from left to right.
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
lms052_ap_01
41
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Vendor-Type | Vendor-Length | Value +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Value (cont) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
2 for Vecima-Priority-Enabled 6 The Value field is a four octet enumeration. 0 - disabled 1 - enabled
5.4.3 Vecima-Authentication-Key
This attribute contains the 256 bit authentication key for the EUM as 64 hexadecimal characters. If it (or MS-MPPE-Recv-Key) is present, the key policy for this EUM is required (and encryption will be enabled), otherwise it is none. NOTE: This attribute carries the secret key from the RADIUS server to the CCU in clear text. The operator must ensure the privacy of this link. Alternately, the authentication key can be carried in the MS-MPPE-Recv-Key attribute described in RFC2548, which is encrypted using the RADIUS shared secret. A summary of the Vecima-Authentication-Key attribute format is shown below. The fields are transmitted from left to right.
0 1 2 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+| Vendor-Type | Vendor-Length | Text ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
Vendor -Type Vendor -Length Text
3 for Vecima-Authentication-Key. 66 The Text field contains the authentication key as 64 hexadecimal characters.
42
lms052_ap_01
5.4.4 Vecima-Current-Password
If this attribute (or Vecima-New-Password) contains the current password of the EUM as a string, the autoconfiguration parameters will take effect; otherwise they will not. A summary of the Vecima-Current-Password attribute format is shown below. The fields are transmitted from left to right.
5 for Vecima-Current-Password. 2-18 The Text field contains the password as a string of up to 16 characters. Both an empty string and a string containing only spaces are treated as an empty password.
5.4.5 Vecima-New-Password
If this attribute (or Vecima-Current-Password) contains the current password of the EUM as a string, the autoconfiguration parameters will take effect; otherwise they will not. If VecimaCurrent-Password contains the current password of the EUM the password will be changed to this string. A summary of the Vecima-New-Password attribute format is shown below. The fields are transmitted from left to right.
6 for Vecima-New-Password. 2-18 The Text field contains the password as a string of up to 16 characters. Both an empty string and a string containing only spaces are treated as an empty password.
lms052_ap_01
43
5.4.6 Vecima-Radio-Frequency
This attribute assigns either a fixed frequency or a frequency search mode. The setting takes effect immediately on reception, any change causing a frequency change or search. Nothing happens if the setting is the same as current (as will occur on a periodic basis as the CCU queries the RADIUS server). For example, if a unit is in fixed mode and a different frequency is received, it immediately changes to that frequency - note that in fixed mode it will not search if no CCU is found. If a unit is in fixed mode and is set to auto mode, the unit will immediately begin a search. A summary of the Vecima-Radio-Frequency Attribute format is shown below. The fields are transmitted from left to right.
7 for Vecima-Radio-Frequency 6 The Value field is four octets. 1 - auto mode 2 - nomadic mode 9052 to 9248 (even numbers only) - fixed mode frequency in 100 kHz
5.4.7 Vecima-SNMP-Read-Community
This attribute supplies a string to use as an SNMP read community. A total of up to five SNMP read and write communities can be defined through multiple instances of these attributes. The read communities specified will replace any currently defined. A single instance with an empty string or only spaces will clear all read communities; that is, no read SNMP access allowed. A summary of the Vecima-SNMP-Read-Community Attribute format is shown below. The fields are transmitted from left to right.
44
lms052_ap_01
8 for Vecima-SNMP-Read-Community. 2-34 The Text field is 0 to 32 octets to be used as a read community string. A 0 length text field or field with only spaces will clear all read communities..
5.4.8 Vecima-SNMP-Write-Community
This attribute supplies a string to use as an SNMP write community. A total of up to five SNMP read and write communities can be defined through multiple instances of these attributes. The write communities specified will replace any currently defined. A single instance with an empty string or only spaces will clear all write communities; that is, no write SNMP access allowed. A summary of the Vecima-SNMP-Write-Community Attribute format is shown below. The fields are transmitted from left to right.
9 for Vecima-SNMP-Write-Community 2-34 The Text field is 0 to 32 octets to be used as a write community string. A 0 length text field or field with only spaces will clear all write communities.
5.4.9 Vecima-SNMP-Trap-Server
This attribute supplies an IP address and community string to which to send SNMP Traps. A total of 5 trap servers may be defined through multiple instances of this attribute. The trap servers specified will replace any currently defined. A summary of the Vecima-SNMP-Trap-Server Attribute format is shown below. The fields are transmitted from left to right.
lms052_ap_01
45
10 for Vecima-SNMP-Trap-Server. 2-48 The Text field is 0 to 48 octets containing an IP address in the form aaa.bbb.ccc.ddd followed by a ':' followed by a string of up to 32 characters to be used as the trap community associated with the trap server. A 0 length text field or field containing only spaces will clear all trap servers.
5.4.10 Vecima-SNMP-Contact
This attribute supplies a string to use as the SNMP Contact field. A summary of the VecimaSNMP-Contact Attribute format is shown below. The fields are transmitted from left to right.
11 for Vecima-SNMP-Contact. 2-82 The Text field is 0 to 80 octets to be used as the SNMP contact. A 0 length text field or field with only spaces will clear the contact field.
5.4.11 Vecima-SNMP-Location
This attribute supplies a string to use as the SNMP Location field. A summary of the VecimaSNMP-Location Attribute format is shown below. The fields are transmitted from left to right.
46
lms052_ap_01
12 for Vecima-SNMP-Location. 2-82 The Text field is 0 to 80 octets to be used as the SNMP Location. A 0 length text field or field of only spaces will clear the location field.
5.4.12 Vecima-SNMP-Name (and Prompt)

This attribute supplies a string to use in the SNMP Name field and the system prompt. The response to the NAME OID in the SYSTEM MIB will be the EUMID and this field in the form XX:XX:XX-name . A string of only spaces will clear this field. This field will also be used to set the system prompt. The system prompt will be in the form XX:XX:XX-name>. A summary of the Vecima-SNMP-Name Attribute format is shown below. The fields are transmitted from left to right.
13 for Vecima-SNMP-Name. 2 - 22 The Text field is 0 to 20 octets to be used as the SNMP Name and prompt. A 0 length text field or field of only spaces will clear this field.
5.4.13 Vecima-Max-Customers
This attribute contains the maximum number of customers that will be allowed air access from the EUM Ethernet port. A summary of the Vecima-Max-Customers Attribute format is shown below. The fields are transmitted from left to right.
lms052_ap_01
47
14 for Vecima-Max-Customers. 6 The Value field is a four octet integer. Max Customers may be 1 to 50.
5.4.14 Vecima-Rf-Power
This attribute contains the rf transmit power level in dBm. It is only valid if the EUM supports the given power level. A summary of the Vecima-Rf-Power Attribute format is shown below. The fields are transmitted from left to right.
15 for Vecima-Rf-Power 6 The Value field is a four octet integer. RF Power may be 15 to 26 in dBm.
5.4.15 Vecima-Downlink-Min-Modulation
This attribute contains the minimum allowed modulation scheme that the CCU may use to transmit to the EUM. It is interpreted by the CCU only and ignored if adaptive modulation is not supported or if the EUM does not support OFDM. A summary of the Vecima-Downlink-MinModulation Attribute format is shown below. The fields are transmitted from left to right.
48
lms052_ap_01
16 for Vecima-Downlink-Min-Modulation 6 The Value field is a four octet integer. The modulation scheme is one of: 3 - CCK2 4 - BPK1 5 - BPK2 6 - QPK1 7 - QPK2 8 - 16Q1 9 - 16Q2 10 - 64Q1 11 - 64Q2.
5.4.16 Vecima-Downlink-Max-Modulation
This attribute contains the maximum allowed modulation scheme that the CCU may use to transmit to the EUM. It is interpreted by the CCU only and ignored if adaptive modulation is not supported or if the EUM does not support OFDM. A summary of the Vecima-Downlink-MaxModulation Attribute format is shown below. The fields are transmitted from left to right.
17 for Vecima-Downlink-Max-Modulation 6 The Value field is a four octet integer. Same values as Downlink-Min-Modulation.
5.4.17 Vecima-Uplink-Min-Modulation
This attribute contains the minimum allowed modulation scheme that the EUM may use to transmit to the CCU. It is interpreted by the EUM only and ignored if adaptive modulation is not supported. A summary of the Vecima-Uplink-Min-Modulation Attribute format is shown below. The fields are transmitted from left to right.
0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
lms052_ap_01
49
| Vendor-Type | Vendor-Length | Value +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Value (cont) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
18 for Vecima-Uplink-Min-Modulation 6 The Value field is a four octet integer. Same values as Downlink-Min-Modulation.
5.4.18 Vecima-Uplink-Max-Modulation
This attribute contains the maximum allowed modulation scheme that the EUM may use to transmit to the CCU. It is interpreted by the EUM only and ignored if adaptive modulation is not supported. A summary of the Vecima-Uplink-Max-Modulation Attribute format is shown below. The fields are transmitted from left to right.
19 for Vecima-Uplink-Max-Modulation 6 The Value field is a four octet integer. Same values as Downlink-Min-Modulation
50
lms052_ap_01
5.5
RADIUS Server Example

The following entries illustrate a simple configuration of a FreeRADIUS server, a commonly used free, open-source RADIUS software application. The following FreeRADIUS files are modified to support LMS8000 / LMS4000: Table 2 FreeRADIUS Files The Vecima LMS8000 / LMS4000 dictionary file is added to the list of dictionaries to use. This new file provides Vecima specific details such as the vendor ID and Vecima attribute enumeration details. The CCU (RADIUS client) IP address and shared secret password are added to the list of clients. In the simplest case, authorized EUMs are added to this FreeRADIUS file. Each user entry includes the EUMID as user name (XX:XX:XX), authorization type (local), user password (buywavc), Vecima-Grade-of-Service (be, bronze, silver or gold) and any other configuration parameters.
dictionary
dictionary.waverider clients
users
Examples of the above files are shown in Table 3, Table 4, Table 5 and Table 6. Table 3 FreeRadius dictionary File
... $INCLUDE dictionary.waverider ...
lms052_ap_01
51
Table 4
FreeRadius dictionary.waverider File

# # # # # # # Vecima Communications Ltd. http://www.waverider.com/ Copyright 2005 Vecima Communications Ltd. Freely Distributable
VENDOR
Vecima
2979
BEGIN-VENDOR Vecima # ATTRIBUTE ATTRIBUTE ATTRIBUTE #Tag 4 is ATTRIBUTE ATTRIBUTE ATTRIBUTE ATTRIBUTE ATTRIBUTE ATTRIBUTE ATTRIBUTE ATTRIBUTE ATTRIBUTE ATTRIBUTE ATTRIBUTE ATTRIBUTE ATTRIBUTE ATTRIBUTE ATTRIBUTE VALUE VALUE VALUE VALUE
Vecima-Grade-of-Service 1 Vecima-Priority-Enabled 2 Vecima-Authentication-Key 3 reserved Vecima-Current-Password 5 Vecima-New-Password 6 Vecima-Radio-Frequency 7 Vecima-SNMP-Read-Community 8 Vecima-SNMP-Write-Community 9 Vecima-SNMP-Trap-Server 10 Vecima-SNMP-Contact 11 Vecima-SNMP-Location 12 Vecima-SNMP-Name 13 Vecima-Max-Customers 14 Vecima-Rf-Power 15 Vecima-Downlink-Min-Modulation 16 Vecima-Downlink-Max-Modulation 17 Vecima-Uplink-Min-Modulation 18 Vecima-Uplink-Max-Modulation 19 be bronze silver gold disabled enabled auto nomadic
integer integer string string string integer string string string string string string integer integer integer integer integer integer 1 2 3 4 0 1 1 2
Vecima-Grade-of-Service Vecima-Grade-of-Service Vecima-Grade-of-Service Vecima-Grade-of-Service
VALUE Vecima-Priority-Enabled VALUE Vecima-Priority-Enabled VALUE Vecima-Radio-Frequency VALUE Vecima-Radio-Frequency END-VENDOR Vecima
52
lms052_ap_01
Table 5
FreeRadius clients File

... 192.168.10.11 sharedsecret ... (where 192.168.10.11 is the CCU Ethernet address and sharedSecret is the password entered with the auth radius primary/secondary command)
Table 6
FreeRadius users File Example Entry

... 60:12:34 Auth-Type := Local, User-Password == "buywavc" Vecima-Grade-of-Service = gold, Vecima-Priority-Enabled = enabled, Vecima-Authentication-Key = abcdef1234567890abcdef1234567890abcdef1234567890abcdef1234567890, Vecima-Current-Password = "current", Vecima-New-Password = "new", Vecima-Radio-Frequency = auto, Vecima-SNMP-Read-Community = "bob", Vecima-SNMP-Read-Community = "bill", Vecima-SNMP-Write-Community = "frank", Vecima-SNMP-Trap-Server = "10.10.11.14:trap1", Vecima-SNMP-Trap-Server = "10.10.11.15:othertrap", Vecima-SNMP-Contact = "Me", Vecima-SNMP-Location = "Here", Vecima-SNMP-Name = "Subscriber", Vecima-Max-Customers = 13, Vecima-Rf-Power = 26, Vecima-Downlink-Min-Modulation = 5, Vecima-Downlink-Max-Modulation = 9, Vecima-Uplink-Min-Modulation = 7, Vecima-Uplink-Max-Modulation = 11 ...
5.5.1 RADIUS Packet Transmission

Once the CCU RADIUS client and the RADIUS server have been configured and enabled, access and accounting messages will be transmitted between them. The following is an example of the messages that are transmitted between the two. This information can be used for troubleshooting purposes. Access Request (CCU to RADIUS Server) The following is an example of an Access Request, transmitted from a CCU to the RADIUS server.
04:12:14.355196 192.168.10.11.1024 > 192.168.10.10.1812: udp 60 4500 0058 0c20 0000 4011 d90f c0a8 0a0b c0a8 0a0a 0400 0714 0044 f906 0108 003c
lms052_ap_01
53
b9b2 010a 0506 7b4f
ea5e 3630 0000 e35c
c906 3a33 0001 0330
e977 5cbe c884 efae b46d 303a 3031 0406 c0a8 0a0b 0212 436e 759e 9db7 b546 2f1e
Starting at byte 28, the following information is transmitted in the above Access Request: Table 7 Example - RADIUS Access Request Code ID Length Authenticator (encrypted) Username Attribute NAS IP Address Attribute NAS Port Attribute Password Attribute (encrypted)
01 08 003c b9b2 ea5e c906 e977 5cbe c884 efae b46d 010a 3630 3a33 303a 3031 0406 c0a8 0a0b 0506 0000 0001 0212 436e 759e 9db7 b546 7b4f e35c 0330 2f1e
Access Response (RADIUS Server to CCU) The following is an example of an Access Response, transmitted from the RADIUS Server to the CCU.
04:12:14.361636 192.168.10.10.1812 > 192.168.10.11.1024: udp 32 4500 003c 7e8c 0000 4011 66bf c0a8 0a0a c0a8 0a0b 0714 0400 0028 66e6 0208 0020 0df8 7527 66c6 4ee5 252e 3b56 46dd ef30 1a0c 0000 0ba3 0106 0000 0003
Starting at byte 28, the following information is transmitted in the above Access Response: Table 8 Example - RADIUS Access Response Code ID
02 08
54
lms052_ap_01
Length Authenticator (encrypted)
0020 0df8 7527 66c6 4ee5 252e 3b56 46dd ef30 1a0c 0000 0ba3 0106 0000 0003
Vecima-Grade-of-Service Attribute:
(where: 0ba3 is Vecima's vendor number, 01 is the Gradeof-Service attribute number, 06 is the length and 0000 0003 is the integer 3, which corresponds to silver)
lms052_ap_01
55
6
Table 9 Parameter Samples
Spectrum Analyser
On the CCU or EUM, the radio analyse command causes the radio to step across the frequency band. At each frequency, it will measure and report the peak, average and noise floor powers. It will also report the presence and level of any packets received from an LMS8000 / LMS4000 CCU or NCL. The radio analysis is configured using the parameters described in Table 9 (all are optional): Radio Analyser Configuration Parameters Description The number of RSSI and noise floor samples taken at each frequency. Samples affects the accuracy and duration of the measurement. The maximum RSSI reported is the largest of the RSSI samples, the average RSSI reported is the mean of the RSSI samples, and the noise floor reported is the maximum of the noise floor samples. NOTE: Samples are not synchronized to any packet transmissions or receptions. Since many transmission sources, including Vecima systems, transmit intermittently, there is the possibility that sources may not be transmitting when the samples are taken, and that they will consequently be missed. Interval The step size between sample points, in increments of 100 kHz. The default is 2 (200kHz), which is also the minimum step size allowed. The maximum interval is 200 (20MHz). NOTE: Although the step size can be set in 100s of kHz, odd frequencies (9053 and 9057MHz, for example) will always be rounded down (to 9052 and 9056MHz, in the preceding example).
lms052_ap_01
57
6: Spectrum Analyser
Parameter Start
Description The lowest frequency sampled, in 100s of kHz. The default is 9000 (900.0MHz), which is also the minimum allowed. This minimum value is outside the allowed transmit range of the EUM and CCU, which is permitted since the radio does not transmit during spectrum analysis. This provides the operator with information about interference near the band edge, which can aid in the identification of any interferers. The upper boundary on frequencies sampled, also in 100s of kHz. The default is 9300 (930.0MHz), which is also the maximum. Again, this is outside the allowed CCU and EUM transmission range.
Stop
To configure the above parameters, enter the following in the command line: radio analyse <samples> <interval> < start> <stop> For example: radio analyse 200 10 9000 9300 will program the Spectrum Analyser to take 200 samples at every frequency, in 1000 kHz steps, starting at 900.0 MHz and ending at 930.0 MHz. If you leave any parameters off the list, they will be set to the default. In the above example, entering radio analyse 200 10 would have had the same effect, since 9000 is the default value for Start, and 9300 is the default value for Stop. The CCU RSSI that is reported by the Spectrum Analyser is the level of any packets received from an LMS8000 / LMS4000 CCU or NCL. Unlike other measurements, it is synchronized with packet reception. Only the value of the last packet received is shown. NOTE: For each CCU detected, three points may be displayed - one point at the center frequency (the frequency to which the CCU is set), one at the lower band-edge (2.8 MHz below the set frequency), and one at the upper band-edge (2.8 MHz above the set frequency). The center point, which will be the highest level, represents the RSS that the EUM receives from the CCU. A comment can be added to the analysis using the radio comment command. This comment will also be displayed on the graph. For example, entering the following in the command line: radio comment Site 1 Spectral Analysis will display Site 1 Spectral Analysis in the line below the date and time. The command radio analyse last will redisplay the results of the last analysis that was performed:
58
lms052_ap_01
6: Spectrum Analyser
60:02:2b> rad an last Freq maxRSS avgRSS noiseFloor ccuRss 9000 -95 -97 -101 0 9002 -94 -97 -100 0 9004 -92 -97 -100 0 9006 -93 -97 -100 0 9008 -93 -97 -100 0 9010 -93 -97 -100 0 Analysis started at: 01-JAN-1970 04:44:17 200 samples at 200 kHz spacing Comment: Example Radio Analysis
A graphical display of the results is available as a PDF (Adobe Portable Document Format) document called specan.pdf, which can be retrieved from the modem through FTP:
-> ftp 192.168.10.250 Connected to 192.168.10.250. 220 FTP server ready 331 Password required User: s 331 Password required Password:****** 230 User logged in ftp> bi 200 Type set to I, binary mode ftp> get specan.pdf local: specan.pdf remote: specan.pdf 200 Port set okay 150 Opening BINARY mode data connection 226 Transfer complete 6394 bytes received in 0.04 secs (171.3 kB/s) ftp> bye
NOTE: Adobe Reader is available from the Adobe Web site. See LMS8000/LMS4000 900 MHz Radio Networking Concepts for examples and interpretations.
TIP: During the analysis, the radio link is disabled. If you run a spectral analysis from a CCU, no data will flow to, or from, any EUM in that sector during the analysis. Traffic will resume immediately after the analysis is complete. Similarly, if you run an analysis from an EUM, no traffic will flow to, or from, that EUM during the analysis. Other EUMs are not affected. As a result, if you start an analysis from a telnet session that uses the data link, no results will be reported and the session will not respond until the analysis is complete. Once it is complete, all of the results will show up at once. If the radio link is disabled before the analysis is done (with radio disable), it will remain disabled afterwards. NOTE: The LMS8000 Spectrum Analyser saturates at about -60 dBm, so that will be the highest reported signal. Any higher level signal will be clipped at that level.
lms052_ap_01
59
Monitoring the Network
Although there are a large number of detailed statistics available for the various data handling applications in the CCU and EUM, there are only a few that are key for monitoring system performance on an on-going basis. These statistics are described in detail on the following pages. Radio Received Signal Strength and Quality on page 62 CCU Transmit Statistics on page 64 CCU Receive Statistics on page 68 EUM Transmit Statistics on page 70 EUM Receive Statistics on page 72 User Data on page 72 Logging CCU or EUM Statistics on page 73 CCU Registration (Air) Table Statistics on page 74 CCU Radio Meter on page 75
The CCU and EUM collect a wide range of IP, radio, MAC, and network layer statistics, which can be used for measuring system performance and troubleshooting. These statistics can be accessed through the command line interface, outlined in LMS8000/LMS4000 CLI Reference Manual or by using an SNMP manager. A list of available statistics and their meanings can be found in Appendix A on page 81. The function of the LMS8000 / LMS4000 network is largely controlled by various data tables described in Appendix B on page 117. The CCU also includes a watch command, which enables you to monitor link statistics for a single specified EUM. For instructions about using the watch command, refer to CCU Watch Statistics on page 115. NOTE: A subset of all statistics are logged at regular intervals, allowing checks on historical operation. Refer to CCU and EUM System Log Statistics on page 118.
lms052_ap_01
61
7: Monitoring the Network
The CCU and EUM are SNMP-ready. To make use of the CCU and EUM SNMP capabilities, you must obtain the associated Vecima MIBs from the technical support page at www.wr.vecimasupport.com and install them on your SNMP manager (SNMPc, Inter-Mapper or HP OpenView, for example). Once you have obtained and installed these MIBs, you can use an SNMP manager to carry out the following functions for both CCUs and EUMs: Read hardware and software configuration parameters, such as unit serial number, MAC address, and hardware and firmware version. Read operator-configurable parameters, such as IP addresses, radio frequency, transmit power level, and the contents of the CCU Authorization and Registration Tables. Read system operating statistics from the MAC layer, and the radio and Ethernet drivers. Receive trap messages such as CCU or EUM power cycles.
In addition, you can program your SNMP manager to perform the following operations: Generate a warning or alarm whenever an operating statistic falls outside an acceptable range. Perform mathematical calculations on a collection of statistics and generate a warning or an alarm if the result of the calculation falls outside an acceptable range. This calculation is done when a statistic, in isolation, cannot be interpreted; i.e., it can only be interpreted properly when compared with the current value of other statistics. Perform a trend analysis on a statistic or group of statistics and generate a warning or alarm when the statistic or group of statistics is starting to move towards an unacceptable limit.
For more detailed information on how to use SNMP to monitor the performance of your LMS8000 / LMS4000 900 MHz Radio Network, refer to LMS8000/LMS4000 SNMP Reference Manual.
7.1
Radio Received Signal Strength and Quality

Perhaps the most useful statistics for monitoring or troubleshooting radio links between the CCU and EUMs are the Receive Signal Strength Indicator (RSSI), which provides an indication of the receive signal strength in dBm, Receive Signal Quality measure (SQ), which provides an indication of the multipath characteristics of the channel, or the current modulation schemes, which provide an indication of the overall quality of the link, and Receive Signal to Noise (RNA/B), which provides an indication of interference. At the EUM, instantaneous values are available in a continuous display with the radio rssi command, or, for EUMs that support the setup menu1, in a simplified form with the radio link command. Long term measures are available as histograms with the radio rh 1. See LMS8000/LMS4000 Feature Support Matrix for Setup menu support.
62
lms052_ap_01
command. The histograms give a measure of the long term fading characteristics of the channel and provide an indication of link stability. Wide variances in the measures generally indicate either a severely fading enviroment or variable interference. At the CCU, these measures are available for each EUM, as seen by the CCU, in the registration table (See Registration Table Entries on page 124) in the arp map table (See Registration Table (CCU Only) on page 124) or through the watch command (See CCU Watch Statistics on page 69). These measures are also used for aligning the EUM antenna as discussed in more detail in your EUM manual. The MDB1000 hand held installation tool will also provide measures of signal strength and quality with some EUMs1. For the LMS4000 system, Vecima recommends an average RSS of at least -83 dBm, RNA or RNB of at least 24 dB and average SQ of less than 13. This leaves a fade margin of approximately 6 dB for link stability over time. The link margin required may vary depending on the radio propagation environment - see LMS8000/LMS4000 Radio Networking Concepts for details. Interpretations of the values to be used for troubleshooting when high transmit retry rates or other link quality issues are noted are shown in Table 10.
Table 10 Retry Rate High High High High -
LMS4000 Signal Quality Troubleshooting Guide RNA RNB1 < 24 > 24 < 24
SQ
RSS <-83 dBm >-83 dBm >-83 dBm >-83 dBm
Indication Probably Inadequate Signal Strength. Probably interference related. Probably severe multipath related. Either significant interference or some interference and severe multipath.
<11 >11 >11
1. Either RNA or RNB may be zero, indicating that that antenna has not been used for several seconds. For the LMS8000 system, adaptive modulation will adjust the modulation scheme to the optimal rate supported by the link. This means that EUMs with higher RSS and RNA/RNB will generally use less system capacity (for the same traffic load) than those with poorer links, or alternately, have higher peak transfer rates if not limited by GOS provisions. Vecima recommends an average RSS of at least -83 dBm and RNA or RNB of at least 18 dB. Installations will continue to see improvements (in either average modulation scheme or additional fade margin) up to an RSS of about -60 dBm or RNA or RNB up to about 35 dB. Links with RSS over -40 dBm are not recommended - it may be better to turn the antenna away from the CCU. Note that the receive and transmit modulation schemes are only shown when traffic is flowing. SQ is not reported for the LMS8000 system.
1. See LMS8000/LMS4000 Feature Support Matrix for MDB1000 support.
lms052_ap_01
63
7.2
CCU Transmit Statistics

As described in APCD-LM050 LMS4000 Data Networking Concepts, the MAC continuously transmits polls to the EUMs. These polls can contain specific user payloads directed to an EUM or the PC connected to an EUM, control payloads directed to an EUM, broadcast payloads directed to all EUMs, or empty polls, which contain no payload. Note that more than one payload (or Ethernet frame) can be sent or received with a poll - this is called bundling. It is therefore important to note the difference between a payload and a packet, which may contain multiple payloads. In an ideal system, all data transmitted would be received error free by the EUMs, and no retransmissions would be required. In the real world, unfortunately, RF noise, low signal conditions, interferers, system engineering problems, and equipment malfunction can result in the need to retransmit data over the radio link. These retransmissions, which are key to maintaining data integrity for the end user, come with the trade-off of reduced network capacity. In systems with adaptive modulation, transmit retries are a normal occurance as the adaptation attempts to use the highest scheme supported by the channel. Since it may be more efficient to use a higher modulation scheme and retransmit a few packets than to use a lower modulation scheme for all packets, the adaptation may result in a small (<25%) continuous retry rate. In this case, examining the modulation statistics, as described in Radio Modulation Statistics on page 98, will give an idea of the link characteristics. Statistics reported by the CCU stats mac command can assist in identifying when retransmissions are occurring and at what rate they are occurring. They can also be used to troubleshoot the cause of retransmissions. TIP: Remember that CCU statistics are aggregate over all EUMs. To track information about the link for one EUM, refer to CCU Watch Statistics on page 115. The statistic txPayloads gives the total number of transmitted payloads, consisting of user data received by the CCU Ethernet port, and transmitted over the radio network, user data received from an EUM, that is switched to the CCU radio port for transmission to another EUM, MAC control data, broadcast data, and data retransmitted because earlier transmissions were not acknowledged by an EUM and are assumed lost.
Examining this statistic in more detail, txPayloads includes
64
lms052_ap_01
Tx Data Payloads which, in turn, includes data originated by the CCU application and sent to the radio port, data coming from the Ethernet port of the CCU (either end-user data or operator monitoring [SNMP] data), data coming from EUM-originated data payloads that have been switched to the CCU radio port (for transmission to other EUMs), and broadcast data to all EUMs(TxPayloadsBCast).
Tx Ctrl Payloads Control data generated in the CCU, and used to configure, or request status from, the EUMs. Tx Ctrl Payloads are transmitted during specific EUM poll periods. Retransmitted data Data that is not acknowledged after a transmission and is assumed to be lost or corrupted.
Understanding the relationship between these values helps you monitor the integrity of a CCU radio environment. All non-broadcast payloads (hence, directed payloads) are explicitly acknowledged by the EUMs. For these payloads, the result of a transmission during an EUM poll cycle will be one of the following: Table 11 Possible Transmission Outcomes
Reported Statistic A B C D E F txPayloadsBCast txPayloads10k txPayloads20k txPayloads30k txPayloads40k txPayloadsFailRetry Result of Transmission Broadcast payload transmitted by the CCU. Payload is delivered to an EUM and acknowledged on the first poll. Payload is transmitted twice, after which an acknowledgement is received. Payload is transmitted three times, after which an acknowledgement is received. Payload is transmitted four times, after which an acknowledgement is received. No acknowledgement received after four transmissions, and the payload is discarded. Payload is not transmitted at all. Total number of payloads discarded because they are malformed. Sample 445 66,001 1,761 281 91 102
G H
txPayloadsFailAssocDeleted txPayloadsFailBadParam
11 0
lms052_ap_01
65
Reported Statistic J txPayloadsFailAssocFail
Result of Transmission Total number of payloads discarded because an association could not be created. Total number of payloads discarded because of timeout. Total number of payloads discarded because the EUM transmit queue was full.
Sample 0
K L
txPayloadsFailTimeout txPayloadsFailQueueTooLong
0 0
To put these values in perspective, the above samples were taken from a live CCU, using the <stats mac> CLI command: Another statistic of interest is txPayloadsBundled, which is the total number of payloads that were transmitted in a packet with other payloads. The objective of the first level analysis of this data is to determine the relative amount of radio traffic resulting from retransmissions. Ideally, the percentage would be 0. In practice, local engineering limitations result in a certain normal level. Once this normal level is established, the statistics can be used to monitor changes. Since not all of these CCU transmit statistics are independent, you have to be careful when interpreting and using results which are based on these statistics. For example, since broadcast payloads are not acknowledged, the retry data is not relevant to these payloads, and they have to be subtracted from the total. In addition, the txPayloadsFailAssocDeleted and the following payloads are never transmitted and should be subtracted from the total. The calculations to do this are shown below: Net Payloads sent through directed polls = B + C + D + E + F = 68,236 NOTE: Due to real-time issues (at any given time, some packets are being processed or queued), the numbers often differ by the small number of packets that are in queues. The percentage of directed payloads that are delivered on the first transmission = 66,001 / 68,236 = 97% Similarly, the percentage of directed payloads not delivered on the first transmission, but delivered on the second transmission = 1,761 / (68,236 - 66,001) = 79% It is generally a good indication if most payloads that fail on the first try are then successful with only one retry. The percentage of directed payloads that are not able to be delivered = 102 / 68,681 = 0.15%
66
lms052_ap_01
A very low undeliverable payload rate implies that user service has a high level of integrity, and that the radio link is not significantly affecting higher-level TCP/IP applications. The impact of the retransmission can be calculated by looking at the total number of transmissions requiring acknowledgments: = 1xB + 2xC + 3xD + 4xE + 4xF = 71,138. Adding to this value the non-acknowledged broadcast payloads (txPayloadsBCast = 445) results in total txPayloads - 71,583. A simple metric of overall sector link quality is the effective utilization of the channel, which can be readily calculated as desired payloads transmitted/actual payloads transmitted, or: (B + C + D + E +F) / (71,138 - G + H + J + K) = 68,236 / 71,127 = 96% which suggests that 4% of the radio traffic is used to retransmit packets, which is referred to in this document as the Retransmission Rate. From an operational point of view, it is important to keep the retransmission rate to a minimum since they reduce the total air time available and the total network throughput. However, with adaptive modulation, the system will automatically trade off the cost of retransmissions against the cost of a lower modulation scheme. These calculations may appear tedious, but since all of the referenced statistics are available through MIBs, SNMP management tools, such as SNMPc, can directly collect the statistics, calculate the above metric, and track and report its value over time. The stats summary command displays similar calculations, as shown in the following example:
----------------- MAC Summary --------------------------------Transmitted Payloads broadcast 1Ok 2Ok 3Ok 4Ok Fail Retry Fail Q Too Long
: : : : : : :
11538 1027283 806 1 0 0 0
1.1% 98.8% 0.0% 0.0% 0.0% 0.0%
Received and Expected Responses HCRC Error : 148 0.0% Directed : 1742797 100.0% Random Access : 12 0.0% No Reply Received : 6 0.0% No Match : 0 0.0% Received Packets with Payloads FCS Error : 5382 ICV/MIC Error: 0 Duplicate : 253 Too Busy - Discard : 8 Delivered : 853215
0.6% 0.0% 0.0% 0.0% 99.3%
lms052_ap_01
67
For units with adaptive modulation, the stats modulation command displays similar results on a per modulation scheme basis. In general, lower modulation schemes should have very low error rates and higher modulation schemes may have very high error rates, with adaptive modulation selecting the highest scheme with a reasonable failure rate. Radio interference can cause an error rate that is the same across all modulation schemes or even a higher error rate at lower schemes, especially if the source is intermittent. The following example shows the results with one link that is limited to 16Q1 by signal level:
51:00:3f*CCU2>stats mod -------------- Adaptive Modulation Statistics -------------------RxPktsOk RxHCRCFail RxPayloads 0 0 0 0 0 0 2 0 2 3 0 3 3333 2 3016 12596 308 9064 289 103 201 0 35 0 0 18 0 TxPktsDir ReplyTOuts TxPayloads 0 0 0 9 0 9 24 0 24 9 1 9 380 2 299 14472 25 7034 2117 216 1932 72 64 42 48 48 14 RxFCSFail RxFCS% 0 0 0 0 0 0 0 0 1 0 1791 19 59 29 0 0 0 0 TxPay1Ok 0 0 0 0 0 6261 1430 1 0 TxPay20k 0 0 0 0 263 466 12 0 0 TxErr% TOuts% 0 0 0 0 3 0 11 11 8 0 4 0 25 10 97 88 100 100 TxPay3Ok TxPay4Ok 0 0 0 9 21 2 8 0 12 0 14 0 0 0 0 0 0 0
3 4 5 6 7 8 9 10 11
CCK2 BPK1 BPK2 QPK1 QPK2 16Q1 16Q2 64Q1 64Q2
3 4 5 6 7 8 9 10 11
CCK2 BPK1 BPK2 QPK1 QPK2 16Q1 16Q2 64Q1 64Q2
The lower modulation schemes have very low error rates and the higher schemes very high error rates. Note that the CCU has selected 16Q1 most often for the first transmission and that retransmissions (2Ok, 3Ok and 4Ok) occur at lower modulation schemes to decrease the likelihood of multiple retransmissions. The CCU occasionally probes higher schemes. You can also monitor the MAC statistic txPayloadsFailQueueTooLong at the CCU to give an indication of packet discards due to queue overrun. The MAC statistic lastQueueTooLongId at the CCU indicates for which EUM the last packet was discarded. That EUM can then be watched to determine how often discards occur and whether it is a problem. Some discards may occur simply due to multiple concurrent downloads combined with heavy system loading. If more than one EUM is having problems, the lastQueueTooLongId statistic will change as discards occur.
7.3
CCU Receive Statistics

Similar to the case for CCU transmit statistics, there are several key CCU receive statistics that you can use to monitor on-going performance of the CCU radio network. When the CCU sends a directed poll to an EUM, it expects to get an acknowledgement. The following results have been taken from a live CCU using the <stats mac> command:
68
lms052_ap_01
Table 12
Typical CCU Receive Statistic Statistic Description The number of packet headers received correctly from all EUMs. These may contain an ack. Packet received with a corrupted header. Packet received from an EUM, with a corrupted payload. No reply or EUM HCRC errors and missed packets. Does not include FCS (frame check sequence) errors. Note: This statistic also includes EUM receive errors, by virtue of the fact that if an EUM does not receive a poll from the CCU, for any reason, then it will not reply to the CCU. Sample 409,730
rxPktsDirected
B C D
rxPktsHCRCFail rxPktsFCS Fail replyOrRssiTimeouts
2,464 192 22,688
From these statistics: Total number of replies expected = A + B + D = 434,882 and the receive packet error rate which, as noted in Table 12, includes EUM receive errors and errors associated with random access attempts, is given by RxPER = (B + C + D) / (A + B + D) = (2,464 + 192 + 22,688) / 434,882 = 5.8% One other receive statistic that is important in multi-CAP environments where frequency reuse is implemented is rxPktsNoMatch. A high value of rxPktsNoMatch indicates that the two CCU radio environments are interfering with each other. The statistic rxPktsDuplicate measures the number of times the EUM sends the same packet of information more than once. A high value of rxPktsDuplicate indicates that the acknowledgements from the CCU are not being properly received at the EUM. The statistics rxPktsICVFail and rxPktsMICFail indicate that a packet has been received with a payload that failed to decrypt correctly or failed the message integrity check respectively.
7.4
CCU Watch Statistics

CCU statistics monitor the aggregate traffic to all EUMs connected to that CCU. The CCU watch command is available for monitoring a single EUM, which is a very useful tool for troubleshooting individual links. These statistics have the same meaning as the stats mac
lms052_ap_01
69
statistics of the same name, but apply to a single EUM, rather than all EUMs. This command is described in detail in CCU Watch Statistics on page 115.
7.5
EUM Transmit Statistics

In general, the statistics collected at the EUM are the same as those collected at the CCU; however, there are some differences in meaning. EUM statistics are unique to a particular EUM. CCU statistics are an aggregation of CCU interactions with all EUMs. The relationships of the key EUM statistics are the same as those for the CCU. In the case of the EUM, however, no broadcast packets are transmitted, and the value of txPayloadsFailAssocDeleted will always be 0. The key EUM transmit statistics, with sample values, are shown below. Table 13 EUM Transmit Statistics
Statistic Description Sample Total Payload Total Txs
A B
txPayloads Tx Data Payloads
Number of payloads transmitted. Number of data payloads to be transmitted (user data) Number of control payloads to be transmitted. Payload is delivered to the EUM and acknowledged on the first poll. Payload is transmitted twice, then acknowledge received. Payload is transmitted three times, then acknowledge received. Payload is transmitted four times, then acknowledge received. No acknowledge received after four transmissions, packet discarded. Total number of payloads discarded because of timeout.
49,101 45,879
Tx Control Payloads
txPayloads10k
43,153
43,153
x1
43,153
txPayloads20k
2,306
2,306
x2
44,612
txPayloads30k
344
344
x3
1,032
txPayloads40k
47
47
x4
188
txPayloadsFailRetry
29
29
x4
116
txPayloadsFailTime out
0 Sum
45,879
49,101
70
lms052_ap_01
The same combinations used for the CCU case are also included in the table for clarity. As with the CCU transmit statistics, the following sample calculations can be made using the sample data from Table 13: Total number of desired payloads = B + C = 45,879 + 2 = 45,881 This is also equal to: (D + E + F + G + H + I) = (43,153 + 2,306 + 344 + 47 + 29 + 0) = 45,879 NOTE: Due to real-time issues (the fact that at any given time, some packets are being processed or queued), the numbers frequently differ by the number of packets that are in queues. NOTE: In the case of the EUM, most payloads are sent in response to directed polls; however, a small number of payloads are sent in response to random access polls. The percentage of payloads that are delivered on the first transmission (txPayloads10k) = D / (B + C) = 43,153 / 45,881 = 94.1% Similarly, the percentage of payloads that are not delivered on the first transmission but are delivered on the second transmission (txPayloads20k) = E / (B + C - D) = 2,306 / 2,726 = 84.6% The percentage of payloads that are not able to be delivered = (H + I) / (B + C) = 29 /45,881 = 0.06% Since there are no broadcast or control payloads, the calculation of the Retransmission Rate is fairly straightforward: Retransmission Rate = (1 - desired payloads/actual payloads) x 100 = (1 - (B + C) / A) x 100 = (1 - 45,881 / 49,101) x 100 = 6.6%
These calculations are displayed by the stats summary command. As for the CCU, in systems with adaptive modulation, transmit retries are a normal occurance as the adaptation attempts to use the highest scheme supported by the channel. Since it may be more efficient to use a higher modulation scheme and retransmit a few packets than to use a lower modulation scheme for all packets, the adaptation may result in a small (<25%) continuous retry rate. Similar to the CCU, the stats modulation command displays results by modulation scheme.
lms052_ap_01
71
7.6
EUM Receive Statistics

In general, the statistics available with the stats mac command have similar meanings to those of the CCU, however, since the EUM may also receive packets (correctly or not) from neighbouring EUMs, they must be used with care. rxPayloadsFromPeer counts the total number of packets with payloads received with correct headers from the CCU (whether addressed to this EUM or not). rxFCSFailFromPeer indicates how many of these are received with corrupted payloads. The ratio is a very good indication of the quality of the link. rxPktsFCSFail indicates packets received from the CCU addressed to this EUM that had a corrupted payload while rxPktsDelivered is the number received correctly. rxPktsHCRCFail is likely to include packets received incorrectly from other EUMs, so it is not a good indication of the CCU/EUM link. The statistic rxPktsDuplicate measures the number of times the CCU sends the same packet of information more than one time. A high value of rxPktsDuplicate indicates that the acknowledgements from the EUM are not being properly received at the CCU. The statistic rxPktsICVFail is incremented when an encrypted payload fails to decrypt correctly. This could be due to airlink errors (rxPktsICVFail is a small fraction of received payloads and indicates the packet error rate) or having the wrong key (rxPktsICVFail is most or all of received payloads - the radio enable command will restart registration). For units with adaptive modulation, these same statistics are gathered for each modulation scheme and displayed with stats modulation. Note that since the CCU will be using a variety of modulation schemes for different EUMs, you may see a large number of payloads received at each modulation scheme. Note that rxPktsOk is packets TO this EUM - giving a measure of the CCUs adaptation - but rxPayloads and rxFCSFail and rxFCS% are for all payloads FROM the CCU, giving an estimate of the channel quality. rxHCRCFail is again likely to include packets received incorrectly from other EUMs.
7.7
User Data
The total user data is recorded by the MAC statistics Rx Data Payloads, Tx Data Payloads, Rx Data Octets, and Tx Data Octets. These statistics could be viewed as billable data and allow you to monitor total usage at the EUM level. The same statistics are available at the CCU (as measured by the CCU). See CCU Registration (Air) Table Statistics on page 74. The stats radio command includes Send High Priority and Send Low Priority, which are counts of high and low priority payloads transmitted.
72
lms052_ap_01
7.8
Logging CCU or EUM Statistics

The system log is an extremely powerful tool since it has accurate absolute time stamps and can be downloaded very quickly using FTP. The system log has two roles: To assist in troubleshooting unit and network problems. The MAC statistics for the CCU and EUM are recorded hourly and are very useful, especially when an absolute time reference is entered to coordinate the logs. To monitor individual unit traffic after the fact, which is useful if any unit is in trouble. It can also be helpful with billing information. By recording information to the log, events of interest are less likely to be missed, as can happen with real-time monitoring.
The system log records every command you enter, either through the serial console port or through a Telnet session, which can be useful when troubleshooting problems. The system log also saves the statistics defined below at each recording period. Each statistic line is preceded by the date/time stamp and the statN label, where N is the line number. If the statistics are recorded every 15 minutes, then the system log can hold at least 36 hours worth of data. Since not all counters are large numbers, the log can typically contain information for the last 2-3 days. The system logs can be downloaded during quiet hours to avoid affecting system performance during peak periods. Downloading the logs every 2 days should ensure that all statistics are retrieved for each unit. To control system logging, connect to the device with Telnet and use the following commands: stats log <interval>. <interval> is the time interval in minutes between each data sample to log. You may set the interval to any number of minutes between 1 and 65535. After entering this command, the CCU or EUM will begin logging statistics at the specified interval. The default interval is 15 minutes. stats log off stops logging statistics. stats log now records the current statistics in the log without affecting the statistics period or whether it is on or off. stats log shows the logging interval. sys log <number of characters to display> [<offset in log (default=0)>] displays a portion of the system log file. NOTE: If statistics logging is enabled and you use the statistics clear command, the current values are logged before the statistics are cleared.
To Retrieve the System Log File

1. Connect to the unit with FTP. 2. Use the bin command to switch to binary image mode. 3. Use the get log <log_filename> command to transfer the file. NOTE: The <log_filename> is a filename you assign to identify the file on your computer. Vecima recommends including the date and time in the filename. If you do not specify any filename, the received file will be named log.
lms052_ap_01
73
4. Use the quit command to close the FTP session.

C:\TEMP>ftp 10.0.2.253 Connected to 10.0.2.253. 220 FTP server ready User (10.0.2.253:(none)): 331 Password required Password: 230 User logged in ftp> bin 200 Type set to I, binary mode ftp> get log 020808 200 Port set okay 150 Opening BINARY mode data connection 226 Transfer complete ftp: 169939 bytes received in 0.28Seconds 606.92Kbytes/sec. ftp> quit 221 Bye...see you later C:\TEMP>
For more information about CCU and EUM statistics logging, refer to CCU and EUM System Log Statistics on page 118.
7.9
CCU Registration (Air) Table Statistics

The registration table statistics are a useful tool for monitoring Tx/Rx data transfer rates on a particular EUM. You can use it to isolate EUMs that may be using an unreasonably large portion of the network. You can also use the registration table statistics to generate usage billing reports for each EUM. These values are available at the command line, through SNMP or through RADIUS accounting messages. The registration table statistics: provide accumulated octet/packet counts for each registered EUM sorted by EUMID. The Rx- and Tx- directions are from the perspective of the CCU. In other words, RxOctets and Rx-Packets refers to data received by the CCU from the EUM; Tx-Octets and Tx-Packets refers to data transmitted from the CCU to the EUM, may be printed at the command line with the <air> command, may be cleared by CCU reset or using the <air flush> command (which will temporarily interrupt all data flow while EUMs re-register), are available through SNMP, and if RADIUS accounting is enabled, the CCU RADIUS clientperiodically and on special eventssends RADIUS accounting packets to a RADIUS server for each EUM authorized through RADIUS. (For example, this event occurs when an EUM is removed from the registration table.)
74
lms052_ap_01
7.10
CCU Radio Meter

The CCU radio meter is a very useful tool for determining the system load. Given a monitoring interval, the <radio meter> command displays activity over the interval, normalized to per second rates. CCUs supporting extended SNMP MIBs1 make the same information available through SNMP - see LMS8000/LMS4000 SNMP Reference Manual for details. The CCU radio meter displays: current number of EUMs being polled in each activity level and grade of service, data rates transmitted and received, both packets and bytes, average polling intervals (per EUM), number of violations of the grade of service guarantees, and broadcast and random access traffic. The overall fraction of time occupied by transmissions. The overall fraction of time occupied by payload data, that is, user data load.
Keep the following points in mind when using the CCU radio meter: Broadcast Tx Payloads should generally not exceed 10% of the total Tx traffic. Broadcast Rx Payloads should be less than 15% of the broadcast total poll rate to minimize collisions. Max IPS Violations indicates the number of times the CCU has not polled the EUM within the maximum inter-poll space defined by the EUMs grade of service. Ideal IPS Violations indicates the number of times the average poll rate of an EUM has been below that defined by the EUMs grade of service. Occupied Time will quickly rise to near 100% as EUMs become associated and are offered their maximum burst rates. For LMS4000 systems, Payload Load is 73% when a maximum rate (2.0 Mbps) FTP transfer is in progress. It may raise as high as 82% with maximum size packets in both directions, however, consistent rates above 60% indicate a heavily loaded system. For LMS8000 systems, Payload Load depends on the modulation schemes being used, with lower modulation schemes presenting a higher load on the system as they take more time to send the same number of bytes. A system using higher modulation schemes will display a lower Payload Load when full than a system using lower modulation schemes, but the total throughput (Tx Bytes + Rx Bytes) will be much higher. Still, consistent rates above 60% indicate a heavily loaded system.
1. See LMS8000/LMS4000 Feature Support Matrix for extended SNMP MIB support.
lms052_ap_01
75
Upgrading the Network
This chapter covers the following procedures: Field Upgrade Process on page 77 FTPing CCU and EUM Configuration Files on page 78 CAUTION: When entering IP addresses in the CCU or EUM, note that a leading 0 forces the CCU or EUM operating system to interpret the entry as octal rather than decimal. For example, pinging 10.0.2.010 actually pings 10.0.2.8
8.1
Field Upgrade Process

CCU and EUM operating software can be upgraded using FTP. The upgrade mechanism is designed to be robust and reliable. Each software image is signed as a Vecima image and marked with the hardware it supports, so only an appropriate software load will be accepted by the unit. A backup version of the image is always maintained to use if the primary image is overwritten or corrupted. Each time the unit is upgraded, the old image becomes the backup. Each software image also contains an MD5 check sum of the contents. This MD5 check sum is verified after the image has been transferred to the unit but before it is written to the file. If it fails, the FTP transfer is aborted with a failure message. The MD5 check sum is verified again after it has been written to the file. If this check sum fails, the FTP transfer is aborted with a failure message and the old image, now the backup, will be used. A hash code for each file is printed in the <file directory> listing. These are published by Vecima with the upgrade procedure for each release for manual confirmation if desired.
lms052_ap_01
77
8: Upgrading the Network
Different models require different software loads. See LMS8000/LMS4000 Feature Support Matrix to determine which Executable Image belongs on the unit and what the filename is. For example, the CCU8000 uses the ccu4xxx series of executables with the filename ccu.exe while the EUM8000 uses the eum3xxx series of executables with the filename eum.exe. The executable file is listed in the file directory available with the file dir command. See www.wr.vecimasupport.com for the latest available executables.
To Upgrade the Executable Image

1. Change to a directory containing the executable image 2. FTP to the unit 3. Use the bin command to switch to binary image mode. 4. Use the put <from> <to> command to transfer the new executable file to the correct filename. <from> is the name of the new image (e.g. eum301b2.exe). <to> is the image file on the unit (e.g. eum.exe). 5. Wait for completion (it will take 20-30 seconds) and verify completion.
C:\TEMP>ftp 10.0.2.253 Connected to 10.0.2.253. 220 FTP server ready User (10.0.2.253:(none)): 331 Password required Password:***** 230 User logged in ftp> bin 200 Type set to I, binary mode ftp> put eum301b2.exe.eum.exe 200 Port set okay 150 Opening BINARY mode data connection 226 Transfer complete ftp: 169939 bytes received in 0.28Seconds 606.92Kbytes/sec.
8.2
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 unit. 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 grade of service levels.
Some of the configuration files may be the same for all like units in a 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 14 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.
78
lms052_ap_01
8: Upgrading the Network
Table 14
FTPing Configuration Files

Configuration File GOS Configuration File File Name gosbe.cfg gosbronz.cfg gossilve.cfg gosgold.cfg authdb.cfg or auth.cfg dhcp.cfg port.cfg route.cfg basic.cfg network.cfg CCU Yes EUM Reboot Required? No
Authorization Configuration File DHCP Configuration File Port Configuration File Route Configuration File Basic Configuration File Network Configuration File
Yes Yes1 Yes Yes1 Yes Yes2 Yes Yes
No Yes Yes Yes Yes Yes
1. dhcp.cfg and route.cfg apply to app series CCUs only - see APCD-LM057 Feature Support Matrix. 2. network.cfg apply to ccu.exe series of CCUs only - see APCD-LM057 Feature Support Matrix.
CAUTION: Use FTP to transfer configuration files between like units only; for example, from a CCU3000 to another CCU3000, not between a CCU3000 and a CCU3100 or EUM. Ensure the file is transferred using image or binary mode. Configuration files may not be compatible between different models. Libraries of GOS configuration files for different CCU models are provided by Vecima WaveRider support at www.wr.vecimasupport.com. Remember to save any changes made at the CLI before downloading the configuration files from the device.
lms052_ap_01
79
Appendix A
Operating Statistics
The CCU and EUM provide a comprehensive set of operating statistics for each of the following: Ethernet Statistics on page 82 Radio Driver Statistics on page 85 DPMAC Interface Statistics on page 88 Continuous Radio Signal Strength and Quality Display on page 94 EUM Radio Signal Strength and Quality Histograms on page 97 EUM Radio Link Quality Display on page 97 Radio Modulation Statistics on page 98 Routing/Bridging Protocol Statistics on page 100 CCU RADIUS Client Statistics on page 105 Authorization Statistics on page 107 Network Interface Statistics on page 109 CCU System Load Statistics (Radio Meter) on page 112 CCU Watch Statistics on page 115 CCU and EUM System Log Statistics on page 118
These statistics can be used as a diagnostic and troubleshooting tool when system performance is being impaired by interference, radio link degradation, network problems, atypical end-user applications, capacity issues, and so on. All of these statistics are available through the command-line interface. Most of the statistics are also available in the CCU and EUM MIBs, if you want to monitor the LMS8000 / LMS4000 900 MHz radio network from an SNMP manager. See LMS8000/LMS4000 SNMP Reference Manual for MIB definitions.
lms052_ap_01
81
Appendix A: Operating Statistics
CAUTION: Each CCU and EUM statistic is a maximum 32-bit number (maximum 4,294,967,295). If a statistics counter exceeds its maximum value, the counter resets to zero and begins again. When this occurs, you must either take the rollover into account, or reset the statistics to re-synchronize the counters. To reset statistics, type stats clear at the command prompt and press Enter.
To Display (all) Statistics from the CLI

At the command prompt, type stats and press Enter.
The following sections describe each of the statistics in detail and the procedure for obtaining specific sets of statistics (Ethernet, Radio, and so on).
Ethernet Statistics
Ethernet Statistics present operational information about data passing through the CCU and EUM Ethernet ports. These statistics are described in Table 15. All of the Ethernet statistics are available in a Vecima MIB. Table 15 Ethernet Statistics Statistic RX ISR's RX DSR's RX DMA Complete Events RX FIFO Full Events RX Unknown Events RX Status FIFO High Mark Description Number of receive interrupts received by the Ethernet driver interrupt service routine. Number of receive interrupts received by the Ethernet driver deferred service routine. Number of receive complete events Number of times the receive FIFO overflowed due to traffic arriving faster than it could be serviced. Number of unknown receive events. Number of times the Ethernet driver disabled reception due to traffic arriving faster than it could be serviced. Number of receive attempts Number of packets received correctly. Number of times the Ethernet port was disabled, possibly to handle heavy traffic. Number of times the Ethernet port was re-enabled.
RX DMA Starts RX Packets Okay RX Disables RX Enables
82
lms052_ap_01
Statistic RX Epkt Unavailable RX Ring High Mark
Description Number of packets dropped due to lack of buffers. Number of times the Ethernet driver disabled reception due to traffic arriving faster than it could be serviced. Number of packets dropped due to lack of queue space. Number of packets dropped due to internal corruption. Number of packets dropped due to internal corruption. Number of packets dropped due to check sum error corrupted on the wire. Number of packets dropped because they are too small. Number of packets dropped because they are too large. Number of interrupts received with no packet. Number of correctly received packets passed out of the driver. Number of times the receive chain was flushed due to DMA corruption. Number of times reception was slowed due to the system being busy. Number of times reception was slowed due to the system being very busy. Number of transmit interrupts received by the Ethernet driver interrupt service routine. Number of transmit interrupts received by the Ethernet driver deferred service routine. Number of packets transmitted correctly. Number of times a packet failed to transmit and had to be retried. Number of interrupts with unknown reasons Number of packets sent from the transmit queue. Number of attempts to send a packet Number of times a packet was retried due to a failure. Number of packets correctly transmitted. Number of packets sent to the driver with no content.
RX Ring Full RX Length Mismatch Errors RX Errors RX CRC Errors RX Runt Errors RX Giant Errors RX Empty DMA Errors RX Callbacks RX Fifo Flushes RX Watermark 1 RX Watermark 2 TX ISR's TX DSR's TX Packet Complete Events TX Abort Events TX Unknown Event TX Packets TX DMA Starts TX Retries TX Packets Okay TX Null Packets
lms052_ap_01
83
Statistic TX Invalid Packets TX Packets In TX Queue Full
Description Number of packets sent to the driver dropped because they were too big or too small. Number of packets sent to the driver and queued. Number of packets sent to the driver and dropped due to no queue space.
To view the Ethernet statistics:

64:02:6c-myEum>statistics ethernet ----------------- Ethernet Statistics ------------------------Ethernet Hardware Statistics 0 100 Half Duplex Up P RX Bytes : 1718304 RX Packets : 5127 RX FCS Errors : 0 RX Multicasts : 0 RX Broadcasts : 5123 RX Control Frames : 0 RX Pause Frames : 0 RX Unknown Opcodes : 0 RX Alignment Errors : 0 RX Length Mismatches : 0 RX Code Errors : 0 RX False Carrier : 0 RX Undersize Packets : 0 RX Oversize Packets : 0 RX Fragments : 0 RX Jabber Count : 0 RX 64 Byte Packets : 0 RX 65 to 127 Byte Packets : 1 RX 128 to 255 Byte Packets : 0 RX 256 to 511 Byte Packets : 5126 RX 512 to 1023 Byte Packets : 0 RX 1023 to 1518 Byte Packets: 0 TX Bytes : 4298 TX Packets : 62 TX FCS Errors : 0 TX Multicast Packets : 9 TX Broadcast Packets : 52 TX Unicast Packets : 1 TX Pause Frames : 0 TX Single Deferrals : 0 TX Multiple Deferrals : 0 TX Single Collisions : 0 TX Multiple Collisions : 0 TX Late Collisions : 0 TX Excessive Collisions : 0 TX Total Collisions : 0 Ethernet Software Statistics 0 RX ISR's : 5127 RX DSR's : 5127 RX DMA Complete Events : 5127 RX FIFO Full Events : 0 RX Unknown Events : 0 RX Status FIFO High Mark : 0 RX DMA Starts : 5128 RX Packets Okay : 5127 RX Disables : 0 RX Enables : 0
84
lms052_ap_01
RX RX RX RX RX RX RX RX RX RX RX RX RX RX TX TX TX TX TX TX TX TX TX TX TX TX TX
Epkt Unavailable Ring High Mark Ring Full Length Mismatch Errors Errors CRC Errors Runt Errors Giant Errors Empty DMA Errors Callbacks Null Packets Fifo Flushes Watermark 1 Watermark 2 ISR's DSR's Packet Complete Events Abort Events Unknown Event Packets DMA Starts Retries Packets Okay Null Packets Invalid Packets Packets In Queue Full
: : : : : : : : : : : : : : : : : : : : : : : : : : :
0 0 0 0 0 0 0 0 0 5127 0 0 0 0 62 62 62 0 0 62 62 0 62 0 0 62 0
Radio Driver Statistics

Radio Driver Statistics present operational information about data passing through the CCU and EUM radio driver and ports. These statistics are described in Table 16. EUMs that support Automatic Frequency Discovery also present the Radio Link Monitor statistics shown in Table 17. The Radio Driver statistics are available in a Vecima MIB. Table 16 Radio Driver Statistics Statistic Events Rx Complete Event Tx Complete Event Cmd Complete Event Fatal Error Event Description Number of interrupts received (any interrupt) in the radio driver ISR (Interrupt Service Routine) Number of receive complete interrupts received by the radio driver ISR. Number of transmit complete interrupts received by the radio driver ISR. Number of command complete interrupts received by the radio driver ISR. Number of fatal error interrupts received by the radio driver ISR.
lms052_ap_01
85
Statistic Send High Priority Send Q Full High Send Low Priority Send Q Full Low Send Giant Fail Send Not Enabled
Description Number of high priority payloads sent successfully to the radio driver transmit queue. Number of high priority payloads not sent because the high priority radio driver transmit queue was full. Number of low priority payloads sent successfully to the radio driver transmit queue. Number of low priority payloads not sent because the low priority radio driver transmit queue was full. Number of payloads not sent because they were too large. Number of times tried to send packets before the radio driver was started; i.e., before the device was up and working. Number of times a packet was successfully sent to the MAC-layer shared memory for transmission over the air. Number of times a packet was delayed before being placed in the MAC-layer shared memory due to a full transmit queue. Number of times a packet was discarded due to the MAClayer shared memory transmit queue not draining. Number of packets received from the MAC-layer shared memory. Number of times there was a receive interrupt, but nothing available to read out of the MAC-layer shared memory. Number of successfully received packets. Number of times the radio driver could not allocate a receive buffer. Number of times the radio driver received a receive interrupt, but the radio driver was not yet up and running. The received packet is ignored in this case. Number of times reception was slowed due to the system being too busy. Number of times reception was slowed due to the system being very busy.
AMM Put AMM Q Full
AMM Q Full Discard AMM Get AMM Q Empty Receive Receive MBlk Unavailable Receive Not Enabled
Receive Watermark 1 Receive Watermark 2:
86
lms052_ap_01
Table 17
Radio Link Monitor Statistics Statistic Description Number of times search is started or a fixed frequency set. Number of cycles of the link monitoring algorithm. Number of Link Control messages processed. Number of frequencies searched. Number of registration responses received. Number of deregistration requests received denying access. Number of deregistration requests received restarting registration Number of frequencies on which registration was attempted. Number of frequencies on which a registration attempt failed. Number of LLC packets the EUM could not parse Number of secure authentication messages received correctly. Number of secure authentication message received that failed authentication. Number of times the EUM attempted to register and failed because the EUM and CCU key policies were incompatible. Number of cycles where the link monitor declared no signal. Number of times the link monitor declared signal lost and restarted frequency search. Number of cycles the link monitor detected >15% Tx packet error rate. Number of cycles the link monitor detected >15% Rx packet error rate.
Start Events Timeout Events LLC Receive Events Searched Frequencies Registrations Deregistrations Reregistrations Registration Attempts Registration Failures Malformed Llc Packets Key Llc Messages Okay Key Llc Messages Fail Key Policy Mismatch Link Monitor Ticks Link Monitor Timeouts Link Monitor Bad Tx PER Link Monitor Bad Rx PER
To view the radio driver and radio link monitor statistics:

60:03:3a> stats rad ------------------- Radio Driver Statistics --------------------Events Rx Complete Event Tx Complete Event Cmd Complete Event FATAL ERROR Event Send High Priority Send Q Full High Send Low Priority Send Q Full Low Send Giant Fail Send Not Enabled AMM Put AMM Q Full AMM Q Full Discard : : : : : : : : : : : : : : 268206 38163 225660 0 0 192282 0 192293 0 0 0 384575 0 0
lms052_ap_01
87
AMM get : 133286 AMM Q Empty : 214 Receive : 133286 Receive MBlk Unavailable : 0 Receive Not Enabled : 0 Receive Watermark 1 : 0 Receive Watermark 2 : 0 ----------------- Radio Link Monitor Statistics ----------------Start Events Timeout Events LLC Receive Events Searched Frequencies Registrations Deregistrations Registration Attempts Registration Failures Malformed LLC Packets Key Llc Messages Okay Key Llc Messages Fail Key Policy Mismatch Link Monitor Ticks Link Monitor Timeouts Link Monitor Bad Tx PER Link Monitor Bad Rx PER : : : : : : : : : : : : : : : : 1 1739 13 101 1 0 1 0 0 0 0 0 21 0 0 0
DPMAC Interface Statistics

Dynamic Polling MAC Interface Statistics present operational information about data which is processed by the CCU and EUM DPMAC layer. Received refers to packets received over the air by this unit. Transmitted refers to packets transmitted over the air by this unit. These statistics are described in Table 18. The DPMAC interface statistics are available in a Vecima MIB. Table 18 DPMAC Interface Statistics Statistic Rx Data Payloads Rx Data Octets Description Number of data payloads received correctly from the air interface. Number of data octets received correctly from the air interface. This includes Ethernet headers but not DPMAC headers. Number of control payloads received correctly from the air interface. Number of times an unknown type of payload was received from the air interface. Number of times a payload that was too long was received from the air interface, and therefore discarded.
Rx Ctrl Payloads Rx Payload Fail Invalid Type Rx Payload Fail Giant
88
lms052_ap_01
Statistic Rx Payloads Bundled Tx Data Payloads Tx Data Octets Tx Ctrl Payloads Tx Payload Fail Invalid Type Tx Payload Fail Giant Tx Payload Fail Invalid Desc Atmel Tx Buffer full on arrival Command Time Outs Command Missed IRQs False Command IRQs Command Status Errors Atmel Fatal Error rxPktsDirected
Description Number of payloads received from the air interface in packets containing other payloads. Number of data payloads transmitted to the air interface. Number of data octets transmitted to the air interface. This includes Ethernet headers but not DPMAC headers. Number of control payloads transmitted to the air interface. Number of times a payload of an unknown type was discarded. Number of times a payload that was too long was discarded. Number of times the internal MAC transmit interface was corrupted. Number of transmit payloads which had to be queued in the host, waiting for buffer space. Number of times the MAC-layer management message was incomplete. Number of times there was no response to the MAC-layer management message. Number of times a command failed because the previous command was still being processed. Number of times the MAC-layer management message was rejected. Not used. CCU: The number of times a reply from the EUM is received with the correct HCRC (header cyclic redundancy check). EUM: The number of times a poll for the EUM is received from the CCU with the correct HCRC. CCU: The number of times an EUM succeeds in a random access. Note that all EUM packets are directed to the CCU, rather than broadcast to all. EUM: The number of broadcast packets (see note a) received with the correct HCRC. These are also random access opportunities. Number of packets correctly received, but not directed to, this station. Number of duplicate payloads (see note a) received and discarded. Indicates that a MAC layer acknowledgement was lost.
rxPktsBroadcast
rxPktsNoMatch rxPktsDuplicate
lms052_ap_01
89
Statistic rxPktsMICFail
Description Number of encrypted packets received that failed the message integrity check, indicating either an attack or misconfigured keys. Number of packets received that were shorter/longer than the minimum/maximum size. Number of packets received with a MAC header CRC failure (header corrupted). Number of encrypted packets received that did not decrypt correctly. This could be due to either an airlink error (a small fraction of received packets, indicating the packet error rate) or misconfigured keys (all or most of received packets). Number of packets received with a Frame Check Sequence failure (payload corrupted). CCU: Number of times a received packet had to be discarded because too many EUMs were already associated. Number of times the receive DMA for a payload does not complete (internal error). Number of times a received payload has to be discarded because either no receive descriptor was available, or there was not enough buffer space. Number of payloads that this station received correctly. Number of packets received that are directed to this station, but that did not contain a payload. Number of packets transmitted. Number of packets transmitted with no payload. Number of payloads transmitted. CCU: Number of broadcast payloads transmitted. Number of payloads acknowledged after the first transmission. Number of payloads acknowledged after the second transmission. Number of payloads acknowledged after the third transmission. Number of payloads acknowledged after the fourth transmission. Number of payloads that failed to transmit due to the retry limit.
rxPktsLongFail rxPktsHCRCFail rxPktsICVFail
rxPktsFCSFail rxPktsAssocFail
rxPktsIncomplete rxPayloadsFailFull
rxPayloadsDelivered rxPktsEmpty txPkts txPktsEmpty txPayloads txPayloadsBCast txPayloads10k txPayloads20k txPayloads30k txPayloads40k txPayloadsFailRetry
90
lms052_ap_01
Statistic txPayloadsFailAssocDeleted txPayloadsFailBadParam txPayloadsBundled txPayloadsFailAssocFail txPayloadsFailTimeout txPayloadsFailQueueTooLong txPayloadsEmpty replyOrRssiTimeouts
Description CCU: Number of payloads that were discarded because the EUM was unreachable or deauthorized. Number of payloads returned to the host because they are improperly formed (internal error). Number of payloads transmitted in packets together with other payloads. CCU: Number of payloads discarded because too many EUMs were already associated. Number of payloads discarded because of timeout. CCU: Number of payloads discarded because the transmit queue for the EUM was too long (see note b). Not used. CCU: The number of times that no response was received to a directed poll. EUM: The number of times the RSSI timer expired because the EUM had not received anything from the CCU for more than 0.5s. Number of times that the radio MAC layer was reinitialized, usually due to a change in frequency; e.g., during spectral analysis. CCU: The number of registration requests received EUM: The number of registration requests transmitted (see note c). CCU: The number of registration responses transmitted. EUM: The number of registration responses received (see note c). CCU: The number of deregistration requests transmitted. EUM: The number of deregistration requests received (see note c). CCU: Number of times no response was received from an EUM, after multiple polls (see note c). CCU: The number of disassociation requests transmitted. EUM: The number of disassociation requests received (see note d). CCU: Number of times the CCU has determined than an EUM should be disassociated (see note d). CCU: The number of times a new association is created. EUM: The number of transitions to associated state (see note d).
restarts
registrationRequests
registrationResponses
deregistrationRequests
deregistrationInits disassociationRequests
disassociationInits newAssociations
lms052_ap_01
91
Statistic currentAssociations unexpectedEvents txDescAvail lastQueueTooLongEUM rxPktsDivA rxPktsDivB txPktsEncrypted rxPktsEncrypted rxPayloadsFromPeer
Description CCU: Number of EUMs currently associated + 1. The additional association is for broadcast. (see note d) Number of internal unexpected events. Indicates the instantaneous number of transmit buffers that are not in use. CCU: Indicates for which EUM the last packet was discarded. For units with diversity antennas: Number of packets received on the A antenna. For units with diversity antennas: Number of packets received on the B antenna. Number of encrypted packets transmitted. Number of encrypted packets received addressed to this station. CCU: Number of payloads received from an EUM. EUM: Number of payloads received from CCU regardless of destination. CCU: Number payloads received with errors from an EUM. EUM: Number of payloads received with errors from CCU regardless of destination. Number of times transmitter failed to send a packet. Number of times the size of the received packet did not match the encoded length - the packet is discarded. Number of times the packet ended or was lost before the MAC header was received - the packet is discarded. Number of times packet transmission was delayed due to interference. CCU: Number of times the CCU delayed polling due to interference. EUM: Number of times the EUM detected an internal radio lockup and restarted. CCU: Number of times the CCU resumed polling after delaying. EUM: Number of times the EUM detected an internal radio lockup and restarted.
rxFCSFailFromPeer
txOverrune rxOverrun rxHeaderIncompletee txDelayede txToRecovere
txRecovere
a. A packet is the basic unit of transmission. A packet may contain 0, 1 or more payloads. A payload is user data, which may be an Ethernet frame or a logical link layer control message.
92
lms052_ap_01
b. The CCU maintains a transmit queue for each EUM. The length of this queue is limited, to keep one EUM from consuming all the resources and impacting other EUMs. txPayloadsFailQueueTooLong indicates excessive load by one EUM, possibly due to large TCP windows. lastQueueTooLongEUM indicates for which EUM the last packet was discarded. That EUM can then be watched (with the watch command) to determine how often discards occur and whether it is a problem. Some discards may occur simply due to multiple concurrent downloads combined with heavy system loading. c. Registration occurs at boot time or after a frequency search. Deregistration may occur if an EUM is not authorized (a registration/deregistration request pair occurs periodically while that EUM is powered ON) or if the EUM does not respond to multiple consecutive polls, such as when it is powered OFF or changes frequencies. d. Association occurs when there is traffic to send to or from an EUM. Disassociation occurs if there is no traffic to or from an EUM for a short period of time. e. Only applies to models supporting OFDM. See LMS8000/LMS4000 Feature Support Matrix. To view the DPMAC Interface Statistics:
64:02:6c-myEum>stat mac ----------------- MAC Interface Statistics -------------------Rx Data Payloads Rx Data Octets Rx Ctrl Payloads Rx Payload Fail Invalid Type Rx Payload Fail Giant Rx Payloads Bundled Tx Data Payloads Tx Data Octets Tx Ctrl Payloads Tx Payload Fail Invalid Type Tx Payload Fail Giant Tx Payload Fail Invalid Desc Atmel Tx Buffer full on arrival Command time outs Command missed IRQs False Command IRQs Command Status Errors Atmel Fatal Errors rxPktsDirected: rxPktsBroadcast: rxPktsNoMatch: rxPktsDuplicate: rxPktsMicFail: rxPktsLongFail: rxPktsHCRCFail: rxPktsICVFail: rxPktsFCSFail: rxPktsAssocFail: rxPktsIncomplete: rxPktsFailFull: rxPktsDelivered: rxPktsEmpty: txPkts: txPktsEmpty: txPayloads: txPayloadsBCast: txPayloads1Ok: txPayloads2Ok: txPayloads3Ok: txPayloads4Ok: txPayloadsFailRetry: : : : : : : : : : : : : : : : : : : 5926 1858078 439 0 0 10 5738 1853954 1 0 0 0 0 0 0 0 0 0 701949 5880993 4127 0 0 6 4102 0 11 0 0 0 6363 701223 702484 700531 5743 0 5743 0 0 0 0
lms052_ap_01
93
txPayloadsFailAssocDeleted: txPayloadsFailBadParam: txPayloadsBundled: txPayloadsFailAssocFail: txPayloadsFailTimeout: txPayloadsFailQueueTooLong: txPayloadsEmpty: replyOrRssiTimeouts: restarts: registrationRequests: registrationResponses: deregistrationRequests: deregistrationInits: disassociationRequests: disassociationInits: newAssociations: currentAssociations: unexpectedEvents: txDescAvail: lastQueueTooLongId: rxPktsDivA: rxPktsDivB: txPktsEncrypted: rxPktsEncrypted: rxPayloadsFromPeer: rxFCSFailFromPeer: txOverrun: rxOverrun: rxHeaderIncomplete: txDelayed: txToRecover: txRecover:
0 0 5064 0 0 0 0 0 1 1 2 0 0 437 0 438 0 0 0 00:00:00 3468895 3114223 0 0 6774 11 0 0 0 1 0 0
Continuous Radio Signal Strength and Quality Display

The radio rssi command starts a continuous display of signal strength and quality, with a row of values printed every second. The displays differ slightly between LMS8000 and LMS4000. Each row contains the values shown in Table 19 for the LMS8000 or Table 20 for the LMS4000. All of these values are available (or deriveable from) the Vecima MIBs. The EUM includes RSS, SQ or Rx/Tx Mod and RNA/B as measured from the CCU. In the CCU display, these values are blank unless an EUM is being watched, in which case they are displayed for that EUM. RSS and RNA are also available in the CCU registration table for each EUM. RSS, SQ or Rx/Tx Mod and RNA/B are short term averages. The others are the number in the last interval. Modulation scheme numbers are given in Table 1 on page 24. Table 19 LMS8000 Radio RSSI Data Data RSS Description Received radio power in dBm. 0 indicates no signal. CCU: from the EUM under watch, if any. EUM: from the CCU.
94
lms052_ap_01
Data RX pkts
Description The number of packets received CCU: from all EUMs. EUM: from the CCU. (A number between 16 and 700 is normal.) The number of packets with payloads received CCU: from the EUM under watch, if any. EUM: from the CCU. The number of payloads transmitted. Received packet error rate. The number of packets received with errors in the payload CCU: from the EUM under watch, if any. EUM: from the CCU. Percentage of payloads transmitted that were retries. Short term average of the modulation scheme of received packets CCU: from the EUM under watch, if any. EUM: from the CCU to this EUM. Short term average of the modulation scheme of transmitted packets CCU: to the EUM under watch, if any. EUM: to the CCU. RSSI Noise A (RNA) is an estimate of the signal to noise ratio at the A antenna in dB. Values above 24 indicate a good signal to noise ratio, while links with values below 18 are likely to experience significant packet error rates. 0 indicates that antenna A has not be selected to receive a packet for 10 seconds. CCU: from the EUM under watch, if any. EUM: from the CCU. RSSI Noise B (RNB) is the same as RNA above, except it applies to antenna B.
RX pay
TX pay RX PER%
TX % Retry RX Mod
TX Mod
RNA
RNB
Table 20
LMS4000 Radio RSSI Data Data Description Received radio power in dBm. 0 indicates no signal. CCU: from the EUM under watch, if any. EUM: from the CCU. CCU: The number of packets received from all EUMs. EUM: The number of packets received from the CCU. A number between 16 and 700 is normal. The number of payloads transmitted and acknowledged on the first try. This number is 0 if there is no traffic being transmitted.
RSS
RX
TX
lms052_ap_01
95
Data R1
Description The number of payloads transmitted and acknowledged on the second try, implying that the first transmission was not acknowledged (i.e., failed). The number of payloads transmitted and acknowledged on the third try, implying that the first two transmissions were not acknowledged (i.e., both failed). The number of payloads transmitted and acknowledged on the fourth try, implying that the first three transmissions were not acknowledged (i.e., all failed). The number of payloads not acknowledged after the fourth try. The payload was discarded. Total percentage of packet retries over the total number of sent payloads. SQ is a measure of signal quality. The lower the value, the better. For EUM and CCU installations, an average value of 8 or less is good. Occasional values above 11 are acceptable, however, consistent values above 11 suggests the radio has trouble tracking the carrier signal, possibly due to severe multipath or interference, or low signal-to-noise ratio. CCU: from the EUM under watch, if any. EUM: from the CCU. RSSI Noise A (RNA) is an estimate of the signal to noise ratio at the A antenna in dB. Values above 24 indicate a good signal to noise ratio, while links with values below 18 are likely to experience significant packet error rates. 0 indicates that antenna A has not be selected to receive a packet for 10 seconds. CCU: from the EUM under watch, if any. EUM: from the CCU. RSSI Noise B (RNB) is the same as RNA above, except it applies to antenna B.
R2
R3
F Retry % SQ
RNA
RNB
To start the display (LMS8000 shown):

64:02:6c-myEum>radio rssi Press any key to stop... RSS dBm -50 -50 -50 -50 -50 -50 -50 -50 RX pkts 3 1792 1784 1744 1782 1782 1774 1777 RX pay 0 5 3 16 4 3 3 3 TX pay 0 3 3 16 3 3 3 3 RX TX % PER% Retry 0 0 20 0 0 0 0 0 25 0 0 0 0 0 0 0 RX Mod 11.0 11.0 11.0 11.0 11.0 11.0 11.0 11.0 TX Mod 9.0 9.0 9.0 9.0 9.0 9.0 9.0 9.0 RNA dB 48 48 48 49 48 48 48 49 RNB dB 49 48 49 49 47 49 49 48 RX % antA 100 94 52 11 53 43 50 72
RSS: RSS: RSS: RSS: RSS: RSS: RSS: RSS:
96
lms052_ap_01
EUM Radio Signal Strength and Quality Histograms

The EUM records the current value of signal strength, quality and signal to noise floor in histograms several times per second. This provides a long term measure of the fading properties of the link and thus whether the installation has the required fade margin. RSS, SQ and RNA/B are defined in Table 20 above. Note that SQ is only available in LMS4000. The histograms are available in the Vecima MIBs. To display the histograms:
64:02:6c-myEum>radio rh -------------- RSSI History (non-zero counts) ----------------RSSI RSSI RSSI RSSI RSSI RSSI RSSI : : : : : : : -44 -45 -46 -47 -48 -49 -50 Count: Count: Count: Count: Count: Count: Count: 8189 123 17 9 6 8 425
------------ RNA/RNB History (non-zero counts) ---------------RSSI RSSI RSSI RSSI RSSI RSSI RSSI RSSI RSSI RSSI vs vs vs vs vs vs vs vs vs vs Noise: Noise: Noise: Noise: Noise: Noise: Noise: Noise: Noise: Noise: 46 47 48 49 50 51 52 53 54 55 Count Count Count Count Count Count Count Count Count Count A: A: A: A: A: A: A: A: A: A: 1 25 173 207 27 9 112 107 8109 7 Count Count Count Count Count Count Count Count Count Count B: B: B: B: B: B: B: B: B: B: 2 40 176 196 21 17 130 210 7984 1
To clear the histograms (they are not cleared with the stats clear command):
64:02:6c-myEum>radio rc
EUM Radio Link Quality Display

A simplified link quality display, intended primarily for end user self installs through the setup menu, is available in some EUMs1. Once a channel is established, the received signal strength, quality and signal to noise ratio are combined into two figures of merit, shown in
1. See LMS8000/LMS4000 Feature Support Matrix for Setup menu support.
lms052_ap_01
97
Table 21 and Table 22. During installation, the antenna should be adjusted until both figures are at least fair. Table 21 Received Signal Strength Figure of Merit Figure of Merit 0 1-3 4-5 6-8 Description No Signal Poor Fair Good
Table 22
Received Signal Quality Figure of Merit Figure of Merit 0 1-2 3 4-5 Description No Signal Poor Fair Good
To display the link quality from the command line:

64:02:6c-myEum>radio link Press 'R' to continue or any other key to stop Registered at 9170 Signal Strength Signal Quality Poor |Fair | Good Poor | Fair | Good 1 2 3 4 5 6 7 8 1 2 3 4 5 6.0 ****************** 3.0 ****************** 6.0 ****************** 3.2 ****************** 6.0 ****************** 3.3 ******************** 6.0 ****************** 3.2 ******************
In the setup menu, this is selection R. The example would be a marginal installation.
Radio Modulation Statistics

Models supporting OFDM1, record airlink receive and transmit statistics for each modulation scheme. The origin of a packet received with a header error (RxHCRCFail) can not be determined, so these may be from either EUMs or a CCU. On the CCU, the other statistics aggregate over all EUMs. On the EUM, they apply to packets to or from the CCU.
1. See - APCD-LM057 Feature Support Matrix for OFDM support.
98
lms052_ap_01
Table 23
Radio Modulation Statistics Data Description Number of packets received with correct headers. Number of packets received with errors in the header (may be from EUM or CCU). The number of packets received with payloads. The number of packets received with errors in the payloads. Percentage RxFCSFail per RxPayloads. The number of directed packets transmitted (broadcast/random access polls are not counted). CCU Only. Number of directed polls sent at this scheme for which no response (correct or in error) was received from the EUM. The number of directed payloads transmitted. The number of directed payloads acknowledged after the first transmission. The number of directed payloads acknowledged after the second transmission. Note that the second transmission was likely at a lower scheme that the first. The number of directed payloads acknowledged after the third transmisssion. The number of directed payloads acknowledged after the fourth transmission. The percentage of directed payload transmissions that were not acknowledged. CCU Only. Percentage of direct packets transmitted for which no response was received from the EUM.
RxPktsOk RxHCRCFail RxPayloads RxFCSFail RxFCS % TxPktsDir ReplyTOuts TxPayloads TxPay1Ok TxPay2Ok
TxPay3Ok TxPay4Ok TxErr% TOuts%
To display the radio modulation statistics from the command line:

60:05:11> stats modulation -------------- Adaptive Modulation Statistics -------------------RxPktsOk RxHCRCFail RxPayloads RxFCSFail RxFCS% 3 CCK2 1599 0 0 0 0 4 BPK1 4 0 4 0 0 5 BPK2 6 0 6 0 0 6 QPK1 2 0 2 0 0 7 QPK2 65 0 65 0 0 8 16Q1 3764 2 1554 31 1 9 16Q2 431 38 127 44 34 10 64Q1 2 15 0 0 0 11 64Q2 0 17 0 0 0 TxPktsDir TxPayloads TxPay1Ok TxPay2Ok TxPay3Ok TxPay4OkTxErr% 3 CCK2 0 0 0 0 0 0 0 4 BPK1 0 0 0 0 0 0 0 5 BPK2 0 0 0 0 0 0 0 6 QPK1 1 1 0 0 0 1 0
lms052_ap_01
99
7 8 9 10 11
QPK2 16Q1 16Q2 64Q1 64Q2
234 3092 963 29 22
83 1035 24 4 3
0 933 9 0 0
82 14 0 0 0
1 2 0 0 0
0 0 0 0 0
0 8 62 100 100
Routing/Bridging Protocol Statistics

Routing/Bridging Protocol Statistics present operational information about data which is processed by the bridging, switching, and routing layers. Some statistics depend on the protocol mode the CCU is in and are described in Table 24 and Table 25. Others apply to the EUM and are described in Table 26. The rest are described in Table 27. Not all statistics apply to all models. The Routing/Bridging Protocol Statistics are not available in the Vecima MIBs. Table 24 Routing/Bridging Protocol Statistics for CCU in Routed Mode Statistic Description Number of Ethernet frames received on the Ethernet port and... Rx Eth Dst - IP Layer Rx Eth Dst - Radio Rx Eth Dst - Broadcast Rx Eth Dst - Unknown sent to the IP layer (either router or host application). N/A broadcast to the internal router. N/A Number of Ethernet frames received on the Radio port and... Rx Radio Dst - IP Layer Rx Radio Dst - Radio Rx Radio Dst - Eth Rx Radio Dst - Unknown Rx Radio Dst - Broadcast Rx Radio Err - Reflection or Rx Radio Rule - Reflection sent to the IP layer (either router or host application). switched back out through the radio. N/A. N/A. broadcast to the radio and host application. discarded because the source address was itself or invalid.
100
lms052_ap_01
Table 25
Routing/Bridging Protocol Statistics for CCU in Switched Ethernet or Through Only Mode Statistic Description Number of Ethernet frames received on the Ethernet port and...
Rx Eth Dst - IP Layer Rx Eth Dst - Radio Rx Eth Dst - Broadcast Rx Eth Dst - Unknown
sent to the host application. bridged to the radio. broadcast to the radio and host application. for which the destination is unknown and is broadcast to the radio. Number of Ethernet frames received on the Radio port and...
Rx Radio Dst - IP Layer Rx Radio Dst - Radio Rx Radio Dst - Eth Rx Radio Dst - Unknown
sent to the host application. switched back out through the radio. sent to the Ethernet port. for which the destination is unknown and so is sent to the Ethernet port and broadcast to the radio. broadcast to the radio, Ethernet port and host application. discarded because the source address was itself or invalid.
Rx Radio Dst - Broadcast Rx Radio Err - Reflection or Rx Radio Rule - Reflection
Table 26
Routing/Bridging Protocol Statistics for EUM Statistic Description Number of Ethernet frames received on the Ethernet port and...
Rx Eth Dst - App Rx Eth Dst - Radio Rx Eth Dst - Broadcast
sent to the host application. bridged to the radio. sent to both radio and host application. Number of Ethernet frames received on the Radio port and...
Rx Radio Dst - App Rx Radio Dst - Eth
sent to the host application. bridged to the Ethernet port.
lms052_ap_01
101
Statistic Rx Radio Dst - Broadcast Rx Radio Dst - LLC Rx Radio Err - Reflection or Rx Radio Rule - Reflection
Description broadcast to the Ethernet and host application. (not an Ethernet frame) Radio logical link control messages. discarded because the source address was itself, known to be on the Ethernet port or invalid.
Table 27
Common Routing/Bridging Protocol Statistics Statistic Description Number of Ethernet frames received on the Ethernet port discarded because...
Rx Eth Err - Rx Discard or Rx Eth Rule - Rx Discard Rx Eth Err - IP Filter or Rx Eth Rule - IP Filter Rx Eth Err - Mblk or Rx Eth Err - Epkt or Rx Eth Err - Null or Rx Eth Err - Msg Buffer Rx Eth Err - Invalid NetPool Rx Eth Err - Could not Duplicate Rx Eth Err - Queue Full Rx Eth Err - Pkt Size Rx Eth Err - Unknown Ether Type Rx Eth Err - Bridge Table Full Rx Eth Err - Customer Table Error
the destination is known to be on the Ethernet side or the source address is itself or is invalid. they matched an installed port filter. of a specific type of memory allocation error.
the radio send queue or IP layer queue was full. the frame was too large or too small to decode. they were not IP, ARP, RARP, or PPPoE frames (example, IPX frame). the bridge table was full. (CCU Only) the host was not allowed air access or because the bridge table was full. Number of Ethernet frames from the radio port that were discarded because...
Rx Radio Err - IP Filter or Rx Radio Rule - IP Filter Rx Radio Err - Unreg Request or Rx Radio Rule - Unregistered
they matched an installed port filter. they came from an unregistered EUM. (CCU Only)
102
lms052_ap_01
Statistic Rx Radio Err - Mblk or Rx Radio Err - Epkt or Rx Radio Err - Null Rx Radio Err - Msg Buffer Rx Radio Err - Invalid NetPool Rx Radio Err - Could not Duplicate Rx Stack Err - Out of Mbufs Rx Radio Err - Pkt Size Rx Radio Err - Unknown Ether Type Rx Radio Err - Queue Full Rx Radio Err - Unknown Msg Type Rx Radio Err - Address Table Full Rx Radio Err - Duplicate IP address or Rx Radio Rule - Duplicate IP address Last Duplicate IP from EUMID:
Description of a specific type of memory allocation error.
the frame was too large or too small. they were not IP, ARP, RARP, or PPPoE frames (e.g. IPX frame). the radio send queue or IP layer queue was full. of an internal routing error. the address table was full. (CCU Only) they were an ARP packet with the source IP address the same as the CCU radio IP address. (CCU Only) ID of the EUM from which the last duplicate IP address was received. This EUM or an attached PC is badly configured. Number of Ethernet frames that were transmitted through the Ethernet port. Number of Ethernet frames that were transmitted through the radio port. Number of transmit Ethernet frames marked high priority due to the DiffServ Code Point rule. Number of transmit Ethernet frames marked high priority due to the VLAN priority threshold rule. Number of transmit Ethernet frames marked high priority due to the RTP detection rule. (CCU Only) Number of transmit Ethernet frames discarded because the destination address was not in the bridging or address tables. (CCU Only) Number of transmit Ethernet frames discarded because the destination EUM was unregistered.
Tx Dst - Eth Tx Dst - Radio Tx DSCP priority detect
Tx Vlan priority detect
Tx RTP priority detect Tx Dst - Unknown
Tx Dst - Unregistered
lms052_ap_01
103
Statistic Tx Err - Mblk
Description Number of transmit Ethernet frames that had to be discarded because of a specific type of memory allocation error. Number of transmit Ethernet frames that had to be discarded because of a specific type of memory allocation error. Number of transmit Ethernet frames that had to be discarded because the frame was too large or too small to decode. Number of transmit Ethernet frames that had to be discarded because of a specific type of memory allocation error.
Tx Err - Msg Buffer
Tx Err - Pkt Size
Tx Err - Could not Duplicate
To view the Routing or Bridging Protocol Statistics (CCU shown):

51:00:3f*CCU2>stats rp ----------------Routing Protocol Statistics ------------------Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Rx Tx Tx Tx Tx Tx Eth Eth Eth Eth Eth Eth Eth Eth Eth Eth Eth Eth Dst Dst Dst Dst RuleRuleErr Err Err Err Err Err IP Layer : 4741 Radio : 0 Broadcast : 5 Unknown (Radio broadcast) : 0 Rx Discard (Discard) : 0 IP Filter (Discard) : 0 Null (Discard) : 0 Queue Full (Discard) : 0 Pkt Size (Discard) : 0 Unknown Ether Type (Discard) : 0 Bridge Table Full (Discard) : 0 Could not Duplicate (Discard) : 0 : : : : : : : : : : : : : : : : : : : : : : : 687 0 34 0 10730 2870 0 0 1 0 0 0 0 0 0 0 0 0 2923 11897 0 0 0
Radio Dst - IP Layer Radio Dst - Eth Radio Dst - Radio Radio Dst - Unknown (Radio broadcast/Eth) Radio Dst - Broadcast Radio Dst - LLC Radio Rule- Reflection (Discard) Radio Rule- IP Filter (Discard) Radio Rule- Unregistered (Discard) Radio Rule- Duplicate IP address(Discard) Last Duplicate IP from EUMID 00:00:00 Radio Err - Null (Discard) Radio Err - Queue Full (Discard) Radio Err - Pkt Size (Discard) Radio Err - Unknown Ether Type (Discard) Radio Err - Address Table Full (Discard) Radio Err - Could not Duplicate (Discard) Radio Err - Unknown Msg Type (Discard) Stack Err - Out of Mbufs (Discard) Dst - Eth Dst - Radio DSCP priority detect Vlan priority detect RTP priority detect
104
lms052_ap_01
Tx Tx Tx Tx Tx Tx Tx Tx Tx Tx Tx
Dst Err Err Err Err Err Err Err Err Err Err
Unknown Unregistered Null Queue Full Pkt Size Could not Duplicate Unregistered Mblk Msg Buffer Pkt Size Could not Duplicate
(Discard) (Discard) (Discard) (Discard) (Discard) (Discard) (Discard) (Discard) (Discard) (Discard) (Discard)
: : : : : : : : : : :
0 0 0 0 0 0 0 0 0 0 0
CCU RADIUS Client Statistics

RADIUS Client Statistics, described in Table 28, are generated by the RADIUS client resident on the CCU and displayed with the <stats auth> command. RADIUS Client Statistics are available in the Vecima MIBs for models supporting it1. Table 28 RADIUS Client Statistics Description Number of distinct access request messages transmitted (not including retries). Number of distinct accounting start messages transmitted (not including retries). Number of distinct accounting update messages transmitted (not including retries). Number of distinct accounting stop messages transmitted (not including retries). Number of RADIUS packets transmitted, including retries. Number of received RADIUS messages discarded because they were too large. Number of received RADIUS messages discarded because they were too small. Number of received RADIUS messages discarded because they were not from the expected RADIUS server. Number of received RADIUS messages discarded because they did not have the expected message ID. Number of received RADIUS messages discarded because the internal structure did not match the packet length.
Statistic Tx Access Requests Tx Accounting Starts Tx Accounting Updates Tx Accounting Stops Tx Messages (including retries) Rx Errors Rx Runts Rx Invalid Server Address Rx Unmatched Id Rx Unmatched Length
1. See APCD-LM057 Feature Support Matrix for Extended SNMP MIB support.
lms052_ap_01
105
Statistic Rx Authenticator Fail Rx Timeouts Rx Okay Rx Wrong Code Rx Accept, No GOS Rx Accept, Misformed Rx Accept, Unknown GOS Rx Access Reject Okay Rx Access Accept Okay Rx Accounting Response Okay No Access Response (4 attempts) No Accounting Response (4 attempts)
Description Number of received RADIUS messages discarded because the authenticator was incorrect (e.g., wrong shared secret) Number of times an expected response did not arrive within 3 seconds. Number of RADIUS messages received with the correct authenticator. Number of received RADIUS messages of an unsupported type. Number of received RADIUS access accept responses discarded for not containing a Vecima-Grade-of-Service attribute. Number of received RADIUS access accept responses discarded because they were incorrectly formed. Number of received RADIUS access accept responses specifying an unknown grade of service. Number of valid RADIUS access reject responses received (these cause an EUM to be denied). Number of valid RADIUS access accept messages received (these cause an EUM to be registered with the assigned grade of service). Number of valid RADIUS accounting responses received. No response is received to a RADIUS access request message after trying the primary and secondary servers (if configured) twice each. No response is received to a RADIUS accounting request message after trying the primary and secondary servers (if configured) twice each.
To view RADIUS Client statistics:

51:00:3f*CCU2>stats authorization RADIUS Client Tx Access Requests Tx Accounting Starts Tx Accounting Updates Tx Accounting Stops Tx Messages (including retries) Rx Rx Rx Rx Rx Rx Rx Rx Errors Runts Invalid Server Address Unmatched Id Unmatched Length Authenticator Fail Timeouts Okay (discard) (discard) (discard) (discard) (discard) (discard) 6 1 1 0 8 0 0 0 0 0 0 0 8
Rx Wrong Code Rx Accept, No GOS Rx Accept, Misformed
(discard) 0 (discard) 0 (discard) 0
106
lms052_ap_01
Rx Rx Rx Rx
Accept, Unknown GOS (discard) Access Reject Okay Access Accept Okay Accounting Response Okay
0 3 3 2
No Access Response (4 attempts) 0 No Accounting Response (4 attempts) 0 Airlink Request Statistics Unregistered EUMs LLC Messages Received Registration Requests Received Deregistration Inits Received Disassociation Inits Received Key/LLCs Received Association Inits Received Unknown LLCs Received Handle Authorization Changes Handle RADIUS Updates Corrupt Key LLC 1 Received Corrupt Key LLC 3 Received Forced Reregistrations Wait for Radius Response Malformed Reg Requests Station Id Mismatches Frequency Mismatches Message Creation Failures Key Unavailable Failures Station Lookup Failures Registration Responses Sent Deregistration Requests Sent Key/LLC0 Sent Key/LLC2 Sent Send Message Fail Registration Fail Timeout Registration Fail Full Registration Fail Encryption
1 2879 369 0 1195 0 1315 0 0 1 0 0 0 0 0 0 0 0 0 0 4 366 0 0 0 0 0 0
Authorization Statistics
The authorization statistics, shown in Table 29, are generated by the authorization component in the CCU and displayed with the <stats auth> command (see example above). Table 29 Authorization Statistics Description Packets received from an unregistered EUM. May occur after a CCU reboot. Logical link layer packets received from EUM. These packets are used to negotiate authorization and authentication. Requests from EUMs to be registered.
Statistic Unregistered EUMs LLC Messages Received Registration Requests Received
lms052_ap_01
107
Statistic Deregistration Inits Received Disassociation Inits Received Key/LLCs Received Association Inits Received Unknown LLCs Received Handle Authorization Changes Handle RADIUS Updates Corrupt Key LLC 1 Received Corrupt Key LLC 3 Received Forced Reregistrations Wait for Radius Response Malformed Reg Requests Station Id Mismatches Frequency Mismatches Message Creation Failures Key Unavailable Failures Station Lookup Failures Registration Responses Sent Deregistration Requests Sent
Description Number of times MAC layer causes a non-responding EUM to be deregistered. Number of times MAC layer causes an EUM to move from associated to registered state. Number of secure authentication messages received from EUMs. Number of times MAC layer queries registration table about an EUM making a random access. Unknown logical link layer messages received. Number of times the authorization of an EUM (grade of service, encryption, etc.) is changed. Number of RADIUS responses parsed. Number of incorrect secure authentication messages received (step 1). Number of incorrect secure authentication messages received (step 2). Number of times an EUM is deregistered and requested to reregister. Number of times an EUM registration request triggers an initial RADIUS request and the CCU waits for a response before registering the EUM. Number of registration requests received that are not internally consistent. Number of registration requests for the wrong station ID. Number of registration requests received from an EUM on a different frequency. Number of times CCU was unable to allocate memory for a response message. Number of times an authorization key for an EUM was required but not available. Number of times authentication failed because the CCU and the EUM did not agree on the state of the handshake. Number of times an EUM is sent a message allowing it to register. Number of times an EUM is sent a message disallowing registration, or requesting re-registration.
108
lms052_ap_01
Statistic Key/LLC0 Sent Key/LLC2 Sent Send Message Fail Registration Fail Timeout
Description Number of secure authentication messages sent (step 0). Number of secure authentication messages sent (step 2). Number of messages discarded because the radio transmit queue was full. Number of times an EUM attempts to register but does not complete the secure authentication handshake within 30 seconds. This may occur if the authentication keys set in EUM and CCU do not match. Number of times an EUM is unable to register because too many EUMs are registered. Number of times an EUM is unable to register because its authentication key policy does not match the required policy in the CCU. This may also happen if group key is enabled but the EUM is not assigned an authentication key.
Registration Fail Full Registration Fail Encryption
Network Interface Statistics

Network Interface Statistics, described in Table 27, are generated by the IP-protocol suite resident on the CCU and EUM, and are available in the standard MIBs provided. Table 30 Network Interface Statistics Description For information on ICMP, and ICMP-related statistics, refer to RFC729. For information on IP, and IP-related statistics, refer to RFC791. For information on TCP, and TCP-related statistics, refer to RFC793. For information on UDP, and UDP-related statistics, refer to RFC768.
Statistic ICMP IP TCP UDP
To view all network interface statistics:

51:00:3f*CCU2>stats net ----------------- Network Interface Statistics ---------------ARP: 34 packets sent 10 reply packets 24 request packets 391 packets received 13 reply packets 378 valid request packets
lms052_ap_01
109
69 broadcast/multicast packets 0 packet with unknown protocol type 0 packet with bad (short) length 0 packet with null target IP address 0 packet with null source IP address 0 could not be mapped to an interface 0 packet sourced from a local hardware address 0 packet with a broadcast source hardware address 0 duplicate for a local IP address 0 attempt to overwrite a static entry 0 packet received on wrong interface 0 entry overwritten 0 change in hardware address length 17 packets deferred pending ARP resolution 12 sent 0 dropped 230 failures to allocate llinfo ICMP: 0 call to icmp_error 0 error not generated because old message was icmp Output histogram: echo reply: 0 #1: 0 #2: 0 destination unreachable: 0 source quench: 0 routing redirect: 0 alternate host address: 0 #7: 0 echo: 3 router advertisement: 0 router solicitation: 0 time exceeded: 0 parameter problem: 0 time stamp: 0 time stamp reply: 0 information request: 0 information request reply: 0 address mask request: 0 address mask reply: 0 0 message with bad code fields 0 message < minimum length 0 bad checksum 0 message with bad length Input histogram: echo reply: 3 #1: 0 #2: 0 destination unreachable: 0 source quench: 0 routing redirect: 0 alternate host address: 0 #7: 0 echo: 0 router advertisement: 0 router solicitation: 0 time exceeded: 0 parameter problem: 0 time stamp: 0 time stamp reply: 0 information request: 0 information request reply: 0 address mask request: 0 address mask reply: 0
110
lms052_ap_01
0 message response generated IP: 14418 total packets received 0 bad header checksum 0 with size smaller than minimum 0 with data size < data length 0 with length > max ip packet size 0 with header length < data size 0 with data length < header length 0 with bad options 0 with incorrect version number 0 fragment received 0 fragment dropped (dup or out of space) 0 fragment dropped after timeout 0 packet reassembled ok 3838 packets for this host 0 packet for unknown/unsupported protocol 1794 packets forwarded (1725 packets fast forwarded) 4 packets not forwardable 0 redirect sent 2326 packets sent from this host 4 packets sent with fabricated ip header 0 output packet dropped due to no bufs, etc. 0 output packet discarded due to no route 0 output datagram fragmented 0 fragment created 0 datagram that can't be fragmented 0 datagram with bad address in header Active Internet connections PCB Proto Recv-Q Send-Q Local Address 31ccd0 tcp 0 68 172.16.6.1.telnet ESTABLISHED 31cf38 tcp 0 0 172.16.6.1.telnet TIME_WAIT 31d1a0 tcp 0 0 *.ftp 31d408 tcp 0 0 *.telnet 320260 udp 0 0 *.1027 320370 udp 0 0 *.1025 320480 udp 0 0 *.1024 320590 udp 0 0 *.1026 3206a0 udp 0 0 *.snmp TCP: 2109 packets sent 2084 data packets (23363 bytes) 0 data packet (0 byte) retransmitted 25 ack-only packets (0 delayed) 0 URG only packet 0 window probe packet 0 window update packet 1 control packet 3768 packets received 2089 acks (for 23506 bytes) 12 duplicate acks 0 ack for unsent data 1686 packets (2191 bytes) received in-sequence 0 completely duplicate packet (0 byte) 0 old duplicate packet 0 packet with some dup. data (0 byte duped) 0 out-of-order packet (0 byte) 0 packet (0 byte) of data after window 0 window probe 0 window update packet
Foreign Address 192.168.10.9.1072 192.168.10.9.1071 *.* *.* *.* *.* *.* *.* *.*
State
LISTEN LISTEN
lms052_ap_01
111
0 packet received after close 0 discarded for bad checksum 0 discarded for bad header offset field 0 discarded because packet too short 0 connection request 13 connection accepts 13 connections established (including accepts) 11 connections closed (including 0 drop) 0 embryonic connection dropped 2098 segments updated rtt (of 2099 attempts) 0 retransmit timeout 0 connection dropped by rexmit timeout 0 persist timeout 0 keepalive timeout 0 keepalive probe sent 0 connection dropped by keepalive 2055 correct ACK header predictions 1654 correct data packet header predictions 0 bad connection attempt UDP: 91 datagrams received 0 with incomplete header 0 with bad data length field 0 with bad checksum 0 dropped due to no socket 80 broadcast/multicast datagrams dropped due to no socket 0 dropped due to full socket buffers 11 delivered 232 datagrams output
CCU System Load Statistics (Radio Meter)

The radio load meter statistics indicate activity on the radio and can be used to estimate the current or long term load on the system. They are summarized in Table 31. Statistics are collected separately for each grade of service and activity level. These statistics are available through a Vecima MIB for models that support it1. The radio meter commandwithout an argumentprints current totals. The radio meter <interval> commandwith an argumentprints per second averages at the given interval. That is, payloads per second or bytes per second.
1. See APCD-LM057 Feature Support Matrix for Extended SNMP MIB support.
112
lms052_ap_01
Table 31
Load Statistics (Radio Meter) Description Value of the CCUs internal 32-bit microsecond timer at the instant the messages were taken. Time rolls over to 0 about every hour and eleven minutes. Exact interval in milliseconds over which the average was taken. Number of payloads transmitted from the CCU to EUMs in this class/ level, including retries. Number of bytes of payload transmitted from the CCU to EUMs in this class/level, including retries. Number of packets with payloads transmitted from EUMs in this class/ level that are correctly received by the CCU. Number of bytes of payload transmitted from EUMs in this class/level that are correctly received by the CCU. MaxIPS Violations - Number of times the CCU has not polled an EUM in this class/level within the maximum inter-poll space defined by the EUMs grade of service. IdealIPS Violations - Number of times the average inter-poll space for EUMs in this class/level has been more than 25% higher than the ideal inter-poll space defined by the grade of service. Number of EUMs in the class/level at the instant in time the load statistics were collected. The broadcast channel counts as one. Current low-pass average inter-poll space, in microseconds, for the class/level at that instant in time, which corresponds to the current polling rate for EUMs in that class. If no EUMs are currently in the class, it is the average taken at the time the last EUM exited the class. Number of times the CCU has polled an EUM in the class/level. Number of times the CCU has polled an EUM in the class/level and did not either transmit or receive a payload. Fraction of time during which the airlink is occupied by either CCU or EUM transmissions, including polling overhead and empty polls. Fraction of time spent sending or receiving user data. This represents the total user data load presented to the system.
Statistic Time
Interval Tx Pyls Tx Bytes Rx wPyl Rx Bytes Max Vio
Ideal Vio
#EUMs Avg IPS
Total Polls Empty Polls Occupied Time Payload Load
Notes: All counters are continuous; that is, they are never zeroed, except if the unit is reset. Payload and poll counters can roll over after a minimum of 25 days. Byte counters can roll over after a minimum of 1 hour. Violation counters could roll over after 40 seconds if the corresponding parameter was set too small. A steeply climbing violation counter indicates serious problems with either the settings or the system load.
lms052_ap_01
113
To view the load statistics totals:

60:03:3a> radio meter CCU Load Meter Totals Time: 3741320980 us Tx Pyls Tx Bytes Rx wPyl Gold Active 42 2579 29 Gold Inactive 12 694 7 BE Priority 1675923 175431448 639056 BE Active 140562 8692330 30290 BE Inactive 78 3552 14 Broadcast 193 11864 14 Overall 1816809 184142405 669410 #EUMs 0 0 1 0 0 1 2 Avg IPS 22278 54000 2058 1502 54000 56440 1949 Total Polls 752 456 746396 126686 1233 1316926 2192449
Rx Bytes Max Vio Ideal Vio 4462 0 0 472 0 0 130562510 0 0 3956296 0 0 2508 0 0 886 0 0 134527134 0 0 Empty Polls 683 437 199 69122 1156 1316720 1388317
Gold Active Gold Inactive BE Priority BE Active BE Inactive Broadcast Overall 60:03:3a>
To view the running current load:

60:03:3a> radio meter 6 *** CCU Load Meter Rates per second *** Interval 6622 ms ******* Tx Pyls Tx Bytes Rx wPyl Rx Bytes Max Vio Ideal Vio BE Priority 586 61296 495 82429 0 0 Broadcast 0 0 0 0 0 0 Overall 586 61296 495 82429 0 0 #EUMs Avg IPS Total Polls Empty Polls BE Priority 1 2009 495 0 Broadcast 1 56469 17 17 Overall 2 1932 513 17 Occupied Time: 99% Payload Load: 41% *** CCU Load Meter Rates per second *** Interval 6622 ms ******* Tx Pyls Tx Bytes Rx wPyl Rx Bytes Max Vio Ideal Vio BE Priority 585 61230 495 82438 0 0 Broadcast 0 0 0 0 0 0 Overall 585 61230 495 82438 0 0 #EUMs Avg IPS Total Polls Empty Polls BE Priority 1 1974 495 0 Broadcast 1 56386 17 17 Overall 2 1938 513 17 Occupied Time: 99% Payload Load: 41%
Each row on the above tables, except for Overall, corresponds to a grade of service/activity level combination. The last row is the overall totals, which in all cases except IPS, are the sum of the entries in the column. Priority refers to EUMs that have had high priority traffic recently, Active refers to EUMs that have had only low priority traffic recently, and Inactive refers to EUMs that have not had traffic recently but have not yet disassociated. Therefore payload counts for inactive EUMs indicate transitions from inactive to active or priority. The Avg IPS indicates the current polling rate for EUMs of the given class. When compared to the target rates in the GOS configuration, this indicates the level of service being offered. The Payload Load is an indication of the overall system load and is given as a percentage of time occupied by user data symbols.
114
lms052_ap_01
For LMS8000, the time occupied by a user data byte depends on the modulation scheme used, so Payload Load is a function of both the presented load and modulation schemes used. A fully loaded system can range from over 80% for low modulation schemes to under 60% for high modulation schemes. For LMS4000, a maximum rate FTP transfer of 2 Mbps results in a payload load of 73%. Maximum rate FTP transfers in both directions can push this as high as 82%. In both systems, consistent loads over 60% probably indicate a heavily loaded channel; however, due to the bursty nature of Internet traffic, the load will vary widely. Also, the user experience under different loadings will depend on many variables, including the service levels offered and expected, types of traffic and number of subscribers. Broadcast traffic is carried with random access polls. Therefore, forward traffic (CCU-to-EUM) in the broadcast row is broadcast traffic, while reverse traffic is random access traffic. The reverse packet rate should be less than 15% of the total poll rate for the broadcast traffic, since random access attempts can collide. Assuming uncorrelated arrivals, this should ensure that 99.7% of random access attempts succeed (in four retries or less).
CCU Watch Statistics

The CCU includes the <watch> command, which enables you to monitor link statistics for a single specified EUM. watch <xx:xx:xx> clears the watch statistics memory and starts watching the specified EUM. watch displays the results of the watch statistics gathering.
While an EUM is being watched, the watch statistics are incremented only for packets transmitted to or from the specified EUM. If no EUM is under watch, the CCU may begin watching the first EUM to register. As part of installing or troubleshooting an EUM, you should watch the EUM from the CCU. This will give you an indication of the link quality through the transmit retry rate and receive error rate. The latest received signal level (RSS), signal quality (SQ) and signal to noise level (RNA) at the CCU can be used to help determine the source of any problems. The accounting information for the EUM is also shown. If the Fail Q Too Long statistic increments, then the TCP receive window in the users PC is probably set too high, causing packet discards at the CCU, retransmission on the network link, and reduced throughput. Long queues at the CCU can also occur due to multiple concurrent transfers in process.
lms052_ap_01
115
Table 32
CCU Watch Statistics Statistic Description EUM ID of the EUM being watched. Grade of service (GOS) assigned to the EUM under watch. Received radio signal strength from the EUM, measured by the CCU, in dBm. Service Quality, measured at the same time as the RSSI measurement was made. Difference, in dB, between the RSSI and the noise floor. Number of seconds passed since the CCU received the last payload from the EUM. Number of octets received since registration. Number of packets received since registration. Number of octets transmitted since registration. Number of packets transmitted since registration.
The EUMID under watch is Grade of service RSSI [dBm] SQ RNA (dB) Time since last payload Input Octets Input Packets Output Octets Output Packets Transmitted Packets No payload Total Transmitted Payloads 10k 20k 30k 40k Fail Retry Fail Q Too Long Fail Timeout Received and Expected Responses
Number of packets received that did not contain a payload. Number of packets transmitted.
Number of payloads acknowledged after the first transmission. Number of payloads acknowledged after the second transmission. Number of payloads acknowledged after the third transmission. Number of payloads acknowledged after the fourth transmission. Number of payloads that failed to transmit due to the retry limit. Number of payloads returned to the host because the transmit queue for the EUM was too long. Number of payloads returned to the host because of timeout.
116
lms052_ap_01
Statistic HCRC Error Directed Random Access
Description Number of packets received with corrupted headers, in response to polling the EUM. Number of packets received with correct headers, in response to polling the EUM. Number of packets received with correct headers, in response to a random access polling. These are considered successful random accesses. Number of times the EUM did not respond to a directed poll. Number of packets received that are directed to this station, from the EUM, but that did not contain a payload.
No Reply Received No Payload
Received Packets with Payloads FCS Error Duplicate Number of packets received with a Frame Check Sequence failure (payload corrupted). Number of duplicate packets with payloads received and discarded. Indicates that a MAC layer acknowledgement was lost. Number of packets with payloads received correctly.
Delivered
To watch an EUM and then (after an interval to collect data) display the watch statistics:
51:00:3f*CCU2>watch 64:02:6c Watching 64:02:6c 51:00:3f*CCU2>watch The Station under watch is: Grade of service: Encrypted: RSSI [dBm]: SQ: RNA [dB]: Time since last payload: Input Octets: Input Packets: Output Octets: Output Packets: Transmitted Packets No payload : 981649 Total : 983647 Transmitted Payloads 1Ok : 1979 2Ok : 12 3Ok : 1 4Ok : 0 Fail Retry : 1 Fail Q Too Long : 0 Fail Timeout : 0 Received and Expected Responses HCRC Error : 220 Directed : 980687 Random Access : 931
64:02:6 silver no -79 0 16 9 s 3580916 11314 75082 1125 99.7%
99.2% 0.6% 0.0% 0.0% 0.0%
0.0% 99.6% 0.0%
lms052_ap_01
117
No Reply Received : No Payload :
2740 977499
0.2% 99.2%
Received Packets with Payloads FCS Error : 30 Duplicate : 0 Delivered : 5019
0.5% 0.0% 99.4%
NOTE: Input Octets, Input Packets, Output Octets, and Output Packets are measured from the point of EUM registration. All statistics below Output Packets are measured from the point at which the watch <xx:xx:xx> command was entered.
CCU and EUM System Log Statistics

The System Log Statistics are logged using a subset of the SNMP MIB counters in a commadelimited decimal format. Each line in the system log file has eight fields: Date/Time Stamp, which is automatically added to the system log. (e.g., 18-DEC2004 21:24:39,) Line Label, which identifies the statistics line number, so the numbers can be extracted correctly. (e.g., stat2,) If the system log requires more than nine lines of statistics, lines following stat9 are numbered in hexadecimal format. (e.g., stata,) Counters. Each line contains up to six counters, with leading commas. Each counter contains between 2 and 11 characters, including the commas. All counters reset when the device reboots or when you issue the stats clear command.
Sample system log file:

60:03:3a> sys log 1600 22-JUL-2004 21:57:38,time set to 22-JUL-2004 21:57:38 from 132.246.168.148 22-JUL-2004 22:02:45,stat1,446034,1192148,750227,443347,32644966,32704692 22-JUL-2004 22:02:45,stat2,11980819,7,0,0,0,0 22-JUL-2004 22:02:45,stat3,14,0,0,0,0,0 22-JUL-2004 22:02:45,stat4,441485,11539357,415920420,415477917,442503,1422 22-JUL-2004 22:02:45,stat5,440414,332,1,0,0,0 22-JUL-2004 22:02:45,stat6,0,0,0,0,0,0 22-JUL-2004 22:02:45,stat7,9823,1,2,2,2,0 22-JUL-2004 22:02:45,stat8,16,16,18 22-JUL-2004 22:02:45,stat9,0,0,0,0,0,0 22-JUL-2004 22:02:46,stata,0,0,0,26683,0,0
The system log records every command you enter, either through the serial console port or through a Telnet session, which can be useful when troubleshooting problems. The system log also saves the following statistics at each recording period. Each line is preceded by the date/time stamp and the statN label, where N is the line number. The statistics include the time since boot, or system uptime, in centiseconds, several Ethernet statistics (see Ethernet Statistics on page 82) and several DPMAC statistics (see DPMAC Interface Statistics on page 88). The CCU (only) also logs several values from the radio meter
118
lms052_ap_01
(see CCU System Load Statistics (Radio Meter) on page 112). Note that the uptime may roll over in as little as 8 days. Table 33 System Log Statistics Line Heading stat1 stat2 stat3 stat4 stat5 stat6 stat7 stat8 stat9a stataa Statistics Logged SYSUPTIME, Ethernet Interrupts, Ethernet RX Data, Ethernet TX Data, DPMAC RX Data Octets, DPMAC TX Data Octets. rxPktsDirected, rxPktsBroadcast, rxPktsNoMatch, rxPktsDuplicate, rxPktsMICFail, rxPktsLongFail rxPktsHCRCFail, rxPktsICVFail, rxPktsFCSFail, rxPktsAssocFail, rxPktsIncomplete, rxPayloadsFailFull rxPacketsDelivered, rxPktsEmpty, txPkts, txPktsEmpty, txPayloads, txPayloadsBCast txPayloads10k, txPayloads20k, txPayloads30k, txPayloads40k, txPayloadsFailRetry, txPayloadsFailAssocDeleted txPayloadsFailBadParam, txPayloadsBundled, txPayloadsFailAssocFail, txPayloadsFailTimeout, txPayloadsFailQueueTooLong, txPayloadsEmpty replyOrRssiTimeouts, restarts, registrationRequests, registrationResponses, deregistrationRequests, deregistrationInits disassociationRequests, disassociationInits, newAssociations gold active avg IPS, gold active max vio, gold active ideal vio, silver active avg IPS, silver active max vio, silver active ideal vio bronze active avg IPS, bronze active max vio, bronze active ideal vio, be active avg IPS, be active max vio, be active ideal vio
a. CCU only
lms052_ap_01
119
Appendix B
CCU/EUM Data Tables
The CCU and EUM firmware is structured around a set of tables and files, which are discussed in the following sections in the logical order that they are actively involved in the transmission of packets from the Internet to the end-users PC: Port Filter Table (CCU and EUM) on page 117 Routing Table (CCU) on page 118 ARP Table (CCU and EUM) on page 121 Address Translation Table (CCU only) on page 122 Authorization Table (CCU only) on page 123 Registration Table (CCU Only) on page 124 ARP Map Table (CCU only) on page 126 Bridge Table (EUM or CCU in Switched Ethernet or Through Only Mode) on page 127 Basic Configuration File (CCU and EUM) on page 128 Permanent Configuration File (CCU and EUM) on page 128
Port Filter Table (CCU and EUM)

The Port Filter Table provides a list of all port filters that have been enabled. Any IP packet with one of these port numbers will be discarded. The contents of the Port Filter Table are:
lms052_ap_01
117
Appendix B: CCU/EUM Data Tables
Table 34
Port Filter Table Entries Description The number of the port which is to be filtered. For each port listed, the CCU or EUM can be set to filter UDP, TCP, or both UDP and TCP packets.
Table Entry Port Filter
To access the Port Filter Table:

51:00:3f*CCU2>port PORT FILTERS Port Filter --------------------------------137 both 138 both 139 both 445 both 1512 both ----------------------------------
Routing Table (CCU)

The Routing Table is used by the CCU to determine the routing of IP packets. The routes in the Routing Table are either entered by the system operator as static routes, or automatically generated by the CCU. The CCU does not support dynamic routing. NOTE: With a CCU in Switched Ethernet mode or Through Only mode, or with an EUM, these routes apply only to packets originated by the CCU or EUM application. Additional routes can only be added to a CCU in Routed mode. The Routing Table contains the following routes: Table 35 Basic Routes Any packet with a destination not listed in the Routing Table is forwarded to the gateway address defined in the default route. Normally, this is be the IP address of the NAP router. The CCU or EUM generates the default route automatically when you enter the gateway IP address. There will be one radio route for each radio subnet. Any packet with a destination in a radio subnet (EUMs, end-user PCs) is forwarded to the CCU radio port. The CCU or EUM generates this route automatically, using the radio subnet IP address(es). The loopback interface exists (among other reasons) so the operating system can talk to itself without handing the packet to a hardware driver. This route keeps unneeded traffic off the network. The CCU or EUM generates this loopback route automatically.
Default Route
Radio Subnet Route(s)
Loopback Route
118
lms052_ap_01
In addition to these standard routes, the system operator may add other routes; for example, routes to support direct CCU-to-CCU communications, without going back to the NAP router. Each route in the Routing Table has at least the following entries (others may also be present): Table 36 Entry Destination Mask Gateway Flags Routing Table Entries Description The IP address for the destination network. The subnet mask for the destination network. The IP address of the gateway through which to access the destination network. If a number is given refer to Table 37, otherwise refer to Table 38. The CCU interface through which to send packets to the gateway and destination, one of: Interface esmc0 or eth0: CCU Ethernet interface rdr1: CCU radio interface lo0: Loopback
To view the Routing Table:

60:03:3a> route Destination Mask 0.0.0.0 127.0.0.1 192.168.10.0 60:03:3a> 0 0 ffffff00 TOS 0 0 0 Gateway 192.168.1.1 127.0.0.1 192.168.10.1 Flags RefCnt 3 5 101 0 1 0 Use 67 30 0 Interface Proto esmc0 lo0 rdr1 1 0 0
In the above example, the default route is defined by:

Destination 0.0.0.0 Mask 0 TOS 0 Gateway 192.168.1.1 Flags RefCnt 3 0 Use 67 Interface Proto esmc0 1
Any IP packet with a destination that is not listed in the Routing Table will be forwarded through the Ethernet port and on to the NAP router (IP address 192.168.1.1). The radio subnet route is defined by:
Destination 192.168.10.0 Mask TOS ffffff00 0 Gateway 192.168.10.1 Flags RefCnt 101 0 Use 0 Interface Proto rdr1 0
Any IP packet destined for the radio subnet (any IP address starting with 192.168.10.xx) will be forwarded through the CCU radio port (IP address 192.168.10.1) and over the radio link to the EUMs and end-users computers. The loopback route is defined by:
Destination 127.0.0.1 Mask 0 TOS 0 Gateway 127.0.0.1 Flags RefCnt 5 0 Use 24 Interface Proto lo0 0
lms052_ap_01
119
Any IP packet destined for 127.0.0.1, which is an IP address reserved for loopback, will be looped back to the CCU operating system. Table 37 Numeric Routing Table Flags. Description Route usable Destination is a gateway Host entry (net otherwise) Host or net unreachable Created dynamically (by redirect) Modified dynamically (by redirect) Message confirmed Subnet mask present Generate new routes on use External daemon resolves name Generated by ARP or ESIS Manually added Just discard packets (during updates) Protocol specific routing flag Protocol specific routing flag Modified by management protocol
Flag Mask 0x1 0x2 0x4 0x8 0x10 0x20 0x40 0x80 0x100 0x200 0x400 0x800 0x1000 0x2000 0x4000 0x8000
To use Table 37, consider the flag associated with the default route, 803, which is equal to (800 + 2 +1). Referring to Table 37, this route was manually added, the destination is a gateway, and the route is usable. Table 38 Non-numeric Routing Table Flags. Description Route usable Destination is a gateway Host Route Static Entry Dynamic Entry (redirect)
Flag Mask U G H S D
If the static routes are not displayed by the route command with the CCU in routed mode, you can display the network configuration file by entering ncf in the CCU command line:
51:00:3f*CCU2>ncf Network Cfg File: File ID : network.cfg File Version : 1 File Time Stamp: 02-Jan-1970 00:30:36 Routed Radio: IP IP IP Mode Address: 192.168.11.8 / 24 Subnet : 192.168.11.0 ( 255.255.255.0 ) Address: 172.16.6.1 / 22
120
lms052_ap_01
IP IP IP IP IP
Subnet : Address: Subnet : Address: Subnet :
172.16.4.0 ( 255.255.252.0 ) 10.0.1.61 / 24 10.0.1.0 ( 255.255.255.0 ) 11.1.2.3 / 26 11.1.2.0 ( 255.255.255.192 )
Static Routes: Dest 1.2.3.0 NTP Client Enabled NTP Servers: 192.168.0.201 10.0.0.1
Gateway 172.16.6.3
Netmask 255.255.255.0
SNTP Relay Enabled : Yes Destination : Primary Radio IP broadcast Period : 240 DHCP Relay Disabled for clients on the Ethernet Interface. DHCP Relay Enabled for clients on the Radio Interface. DHCP Relay Server Table: IP Address . . . . . : 192.168.50.1 IP Address . . . . . : 192.168.50.15 Circuit Id . . . . . : myCCU Priority Classification Enabled vlan threshold: 5 DSCP map : 0x0000400000000000 RTP max length: 250 Port Ranges 10000 - 20000 22000 - 30000 0 - 0 0 - 0 0 - 0
The above example shows a routing table to which one route has been manually added.
ARP Table (CCU and EUM)

For each host (EUM, PC, or router) in the system, the ARP (Address Resolution Protocol) Table displays at least the following information:
lms052_ap_01
121
Table 39
ARP Table Entries Description Host IP Address Host Ethernet MAC Address Number of processes currently referencing this ARP entry. If a process requires a MAC address, it looks it up in the ARP Table. When the ARP entry is referenced by a process, refcnt will be incremented by one. When the process is done with the ARP entry, refcnt will be decremented by one. Number of times the ARP Table has been accessed for this network element. The type of interface, one of the following:
Table Entry destination gateway
Refcnt
Use
Interface
esmc0 or eth0: Ethernet rdr1: Radio lo0: Loopback
The ARP Table is automatically built by the CCU or EUM based on traffic passing between the Ethernet and Radio ports. This table displays the host IP and MAC addresses. After the CCU or EUM recovers the destination IP address from an IP packet sent to the router layer, it looks in the ARP Table to find the destination Ethernet MAC address. If the IP address does not appear in the ARP Table, the CCU or EUM obtains the MAC address through an ARP request/ reply and adds it to the ARP Table. The only time a host IP address appears in the ARP Table, is if the host has recently (in the past ten minutes or so) sent or received data. This can be forced using a ping, Telnet, SNMP request, or by entering arp map <aaa.bbb.ccc.ddd>, where <aaa.bbb.ccc.ddd> is the host IP address. Refer to ARP Map Table (CCU only) on page 126.
To view the CCU ARP table:

51:00:3f*CCU2>arp LINK LEVEL ARP TABLE destination gateway flags Refcnt Use Interface -------------------------------------------------------------------------172.16.6.3 00:90:c8:64:02:6c 20405 2 1119 rdr1 192.168.10.9 00:d0:b7:69:94:b2 20405 5 3245 eth0 192.168.10.255 ff:ff:ff:ff:ff:ff 420405 0 75 eth0 192.168.11.255 ff:ff:ff:ff:ff:ff 420405 1 5 rdr1
Address Translation Table (CCU only)

The Address Translation Table lists the MAC addresses for: End-user PCs that have been granted air access, if the CCU has sent traffic to, or received traffic from, the PC
122
lms052_ap_01
EUMs, if the CCU has sent traffic to, or received traffic from, the network element. In Switched Ethernet or Through Only mode, hosts that have sent traffic to the CCU Ethernet port.
If no traffic has been sent traffic to, or received traffic from, an end-user PC or EUM host for a 12-hour period, they will be removed from the Address Translation Table. The CCU uses the Address Translation Table, which is built automatically by the CCU, to look up the destination station ID for a particular MAC address. A MAC address associated with the CCU Ethernet port is listed with the CCU station ID. The MAC addresses associated with the EUM, are: EUM Ethernet MAC Address End-user PC MAC Address (one or more)
To view the Address Translation Table:

60:03:3a> add StationID MAC Address Time[s] ------------------------------------60:00:83 00:90:c8:60:00:83 106 60:00:83 00:d0:b7:69:94:b1 40 Total of 2 entries
In the above view, the following MAC addresses are associated with Station ID 60:00:83: 00:90:c8:60:00:83 00:d0:b7:69:94:b1 EUM Ethernet MAC Address End-user PC MAC Address
Authorization Table (CCU only)

The Authorization Table controls the EUMs access to the LMS8000 / LMS4000 900 MHz Radio Network. It contains the grade of service class, authentication key policy, authentication key, whether priority traffic classification is enabled and the range of allowed transmit modulation schemes for each EUM in the system. The contents of the Authorization Table are used to automatically build the Registration Table. The entries in the Authorization Table can be entered at the command line, or can be maintained remotely through a RADIUS server and database (see Configuring a RADIUS Server on page 39). The GOS class entry will be either a grade of service class, or denied (service). Priority will be disabled or enabled. Key policy will be required or none (the key itself is not shown). Min scheme and max scheme are numbers corresponding to modulation schemes as given in Table 1 on page 24. Type indicates whether an entry was made at the command line (static) or through RADIUS (radius). It also indicates when the RADIUS server has not responded to requests (radius fail once and radius fail multiple). Min scheme and Max scheme are ignored for EUMs not supporting OFDM and not present in CCUs not supporting OFDM.
lms052_ap_01
123
If the RADIUS client is not enabled (or not responding when the EUM first registers), the default grade of service, priority-enable and modulation schemes are assigned on registration to any EUM that does not appear in the table. The default GOS can be a grade of service class, or denied, meaning any EUM that does not appear in the table will be denied service. NOTE: The defaults are assigned at registration. If you change the default, EUMs already registered will not be affected until they reregister, which can be triggered by flushing the registration table, address table and ARP table. This will interrupt service briefly.
To view the Authorization Table:

51:00:3f*CCU2>auth Authorization Table EUM ID GOS CLASS PRIORITY MIN MAX KEY POLICY TYPE ---------------------------------------------------------64:00:24 denied disabled 3 3 none radius 64:00:72 bronze disabled 3 3 none static 64:02:6c silver disabled 4 11 none radius 64:12:34 gold enabled 5 9 none static Total of 4 entries. MIN/MAX apply if OFDM capable. Default GOS be, priority disabled, tx modulation: 4 (BPK1) to 11 (64Q2) Broadcast Traffic is currently not encrypted
Registration Table (CCU Only)

The Registration Table contains a list of all registered EUMs. The CCU automatically builds and adds to this table as EUMs communicate with the CCU. Every EUM that registers with the CCU appears in this table. The CCU maintains usage information for each EUM in this table. The EUM will be removed from the Registration Table if the: EUM has not communicated with the CCU for more than 12 hours because: the EUM has been turned off for more than 12 hr., or the EUM has had no traffic to send for more than 12 hr., or the EUM has lost its RF connection to the CCU for more than 12 hr.
EUM does not respond to traffic from the CCU. In this case, the EUM will be removed immediately from the Registration Table.
The Registration table entries shown in Table 40 are also available through SNMP. Table 40 Registration Table Entries Description Station ID or EUM ID If the EUM ID is followed by a *, this EUM has passed secure authentication and user data is encrypted. Grade of Service Class assigned to the EUM
Table Entry EUM ID ENC GOS
124
lms052_ap_01
Table Entry PRI RSSI SQ (LMS4000 only) MAX (LMS8000 only) RNA Time Rx-Octets Rx-Packets Tx-Octets Tx-Packets Maximum Associations Deregistration Count
Description If the GOS is followed by a +, priority traffic classification is enabled for this EUM, otherwise it is not. Radio received signal strength (RSSI) in dBm of the EUM as measured at the CCU on the last packet from the EUM. Signal quality, measured at the same time as the RSSI is recorded. Maximum modulation scheme to use to transmit to this EUM. Difference between the RSSI and the measured noise floor in dB. Time in seconds since the last payload was received from the EUM. Number of octets received from this EUM in data payloads, including Ethernet header but not radio MAC header. Number of Ethernet frames received from this EUM in data payloads. Number of octets sent to this EUM in data payloads, including Ethernet header but not radio MAC header. Number of Ethernet frames sent to this EUM in data payloads. The maximum number of EUMs that can be associated at any one instant in time. An EUM will be de-registered if it does not respond after the CCU has sent it this many consecutive polls.
TIP: The Rx-Octets, Rx-Packets, Tx-Octets, and Tx-Packets statistics are identical to the RADIUS accounting statistics and may be considered the appropriate usage statistics for billing purposes. Any EUMs that are going through the secure authentication process will be listed in a separate 4-way handshake table. EUMs may appear in this table for a short period (<1 minute) if secure authentication fails. If an EUM appears in this table with a time greater than 2 seconds, the authentication key may not be correctly configured at EUM or CCU. Any EUMs that are in the process of being authorized through RADIUS will be listed in a separate RADIUS request in Process table. The end of the air table also prints the total number of EUMs registered.
To view the Registration Table:

51:00:3f*CCU2>air
lms052_ap_01
125
Maximum associations: 70 REGISTERED EUMs EUM ID/ GOS/ RSSI MAX RNA Time Rx-Octets Rx-Packets Tx-Octets Tx-Packets ENC PRI dBm dB s -----------------------------------------------------------------------------64:02:6c silver -79 11 4 0 4124060 12956 75376 1128 1 EUMs registered of 300 allowed
NOTE: The air command has been used to view the Registration Table, because reg is too close to reb (reboot).
ARP Map Table (CCU only)

For each host (EUM or PC) in the system, the ARP Map Table displays the following entries: Table 41 ARP MAP Table Entries Description Host IP address Host Ethernet MAC address Station ID (EUM ID) If the Station ID is followed by a *, this EUM has passed secure authentication and user data is encrypted. EUM Grade of Service If the GOS is followed by a +, priority traffic classification is enabled for this EUM, otherwise it is not. RSS in dBm of the last payload received from the EUM. Maximum allowed transmit modulation scheme for the EUM. Signal quality, measured at the same time as the RSS is recorded. Difference between the RSS and the measured noise floor. Number of seconds since the last payload was received from the EUM.
Table Entry IP Address Ethernet Station ID ENC GOS PRI RSS MAX (LMS8000 only) SQ (LMS4000 only) RNA (dB) Last Rx
The ARP MAP Table is built automatically by the CCU, from information contained in the Address, ARP and Registration Tables. Its primary use is to summarize the information in these tables in a user-friendly format, for presentation to the system operator.
126
lms052_ap_01
The arp map <aaa.bbb.ccc.ddd> command will ARP for the IP address if it is not already in the ARP Table. The arp map <XX:XX:XX> command will reverse ARP for the IP address of the EUM with this Station ID if it is not already in the ARP Table. To view the ARP MAP Table:
51:00:3f*CCU2>arp map 64:02:6c Resolving 64:02:6c...172.16.6.3 IP Address Ethernet StationID GOS RSSI MAX RNA Last Rx ------------------------------------------------------------------------172.16.6.3 00:90:c8:64:02:6c 64:02:6c silver -79 11 7 978
OR:
60:03:3a> arp map ARP MAP TABLE IP Address Ethernet 192.168.10.250 00:90:c8:60:30:01 192.168.10.251 00:90:c8:60:32:ac 192.168.10.252 00:90:c8:60:31:1d 192.168.10.253 00:90:c8:60:29:b3 192.168.10.254 00:90:c8:60:2b:44 EUMID 60:30:01 60:32:ac 60:31:1d 60:29:b3 60:2b:44 GOS be bronze be silver be RSSI SQ RNA -52 4 60 -64 5 44 -76 7 20 -60 4 48 -73 3 31 Last Rx 6 16 151 33 49
Bridge Table (EUM or CCU in Switched Ethernet or Through Only Mode)

The primary purpose of the Bridge Table is to determine which Ethernet destination addresses are on the Ethernet side, ensuring local traffic is kept local. The following points apply to the Bridge Table on an EUM only: The Bridge Table also gives you control over the number of PCs that can access the Internet through the EUM. The Bridge Table presents a list of the end-user computers that are connected to the EUM. If customer_max is set to 1, only one of the computers in the table will have air access. If customer_max is set to n, up to n computers in the Bridge Table will have air access. Air access is assigned on a first come, first served basis. If n=1, the first computer to transmit packets will be granted air access. All other computers will be denied air access. If the computer that has been granted air access, does not transmit traffic for 10 minutes, then his air access will be removed and the next computer that transmits a packet will be granted air access. More generally, for any n, up to customer_max, the first n computers transmitting packets will be granted air access and, if any of them fails to transmit traffic for 10 minutes, their air access will be removed, allowing the next computer without air access to be granted air access as soon as they transmit data.
lms052_ap_01
127
Table 42
Bridge Table Entries Description Computers MAC address Y - computer has been granted air access. N - computer has not been granted air access Time, in seconds, since the last packet was received from a particular end-user computer or device.
Table Entry MAC Address Air Access (EUM Only) Time (s)
NOTE: If customer max is set to 1, and you want to connect a different PC to the EUM, for maintenance purposes, for example, you must clear the Bridge Table, reset the EUM, or wait 10 minutes.
To display the Bridge Table:

64:02:6c-myEum>bridge MAC Address Air Access Time[s] ------------------------------------------00:1b:11:4b:07:39 Y 12 00:d2:12:06:11:3e N 4 Total of: 2 entries Maximum Number of Customers: 1
Basic Configuration File (CCU and EUM)

The Basic Configuration File (BCF) presents a summary of many CCU and EUM configurable parameters, which are either the factory default settings, or those entered by the system operator. The BCF content and display vary between different models. Note that most networking related configuration is not stored in the CCU basic configuration file, but in the networking or routing configuration file. Authorization configuration is stored in the authorization database file.
Permanent Configuration File (CCU and EUM)

The Permanent Configuration File (PCF) is a record of device parameters that are permanently programmed during manufacturing, such as calibration and MAC address. Its content and display varies between models.
128
lms052_ap_01
Appendix C
Access Interface
The CCU and EUM command line interface can be accessed through telnet, either locally through the Ethernet port, or remotely over the Ethernet or radio network. Some units can also be accessed through a serial port. See APCD-LM057 LMS4000 Feature Support Matrix for serial port support. The following topics are covered: Local Link Telnet Connection on page 131 Local or Remote Telnet Connection on page 132 Serial Port Connection on page 133 PC Configuration on page 134
Local Link Telnet Connection

Units that support a local link address1 will respond at a fixed IP address via the Ethernet port whether an IP address has been manually configured or a DHCP lease has been obtained or not. EUM: 169.254.10.250 (netmask 255.255.0.0)2 CCU: 169.254.10.249 (netmask 255.255.0.0)
This allows an operator or user attached to the Ethernet port to telnet to the EUM without knowing the configured IP address. Some features, such as the setup menu, are only available through the local link address.
1. See APCD-LM057 Feature Support Matrix for local link address support. 2. In RFC3330, the block of IP addresses 169.254.x.x is reserved for connections on the local link, that is, these addresses are never routed.
lms052_ap_01
131
Appendix C: Access Interface
To Telnet using the Local Link IP address

1. Connect a crossover Ethernet cable between the PC and the unit. 2. Change the IP address and netmask of the PC to be on the 169.254.0.0 network 169.254.10.1 with a netmask of 255.255.0.0 for example1. For more information about configuring PC IP settings, refer to To Configure PC Network Settings (Windows XP Operating System) on page 134. 3. Open a Command Prompt window. (For instructions on opening a command prompt window, please refer to your operating system documentation.) 4. At the prompt, type telnet 169.254.10.250 (for an EUM) or telnet 169.254.10.249 (for a CCU) and press Enter. 5. At the password prompt, type the device password and press Enter to access the command line interface or type setup and press Enter to access the setup menu2. NOTE: The default password for CCUs and EUMs is blank - just press Enter.
Local or Remote Telnet Connection

If you know the configured IP address of the CCU or EUM, you can use telnet to connect to a CCU or an EUM over either the radio network or the Ethernet network. TIP: If you do not know the IP address of an EUM on the radio network, but you do know the EUMID, telnet to the CCU and ping or telnet to the EUM using its EUMID. The connection may be: LocalThe PC and the target CCU or EUM are on the same Ethernet segment and IP subnet. For example, you may connect an Ethernet cable directly between them. NOTE: With multiple radio IP subnets, the end-user PC and EUM may not be on the same IP subnet, so the session would be remote even though they are on the same Ethernet segment. RemoteThe PC and the target CCU or EUM are connected by an IP network. For example, you may be connecting from a terminal in the NAP or external to the system, or a PC on a different IP subnet within the radio network.
Procedures for both types of Telnet sessions are explained below.
1. Windows and Mac operating systems will default to an address on this network if configured for DHCP and no DHCP server is available during boot. 2. See LMS8000/LMS4000 Feature Support Matrix for Setup menu support.
132
lms052_ap_01
To Connect to a Local CCU or EUM with Telnet

1. Connect a crossover Ethernet cable between the PC and CCU or EUM. 2. Change the IP address and netmask of the PC, so the PC and CCU or EUM are on the same subnet. For more information about configuring PC IP settings, refer to To Configure PC Network Settings (Windows XP Operating System) on page 134. 3. Open a Command Prompt window. (For instructions on opening a command prompt window, please refer to your operating system documentation.) 4. At the prompt, type telnet aaa.bbb.ccc.ddd and press Enter. (aaa.bbb.ccc.ddd is the IP Ethernet address of the CCU or EUM.) 5. At the password prompt, type the device password and press Enter. NOTE: The default password for CCUs and EUMs is blank, so press Enter. You are now connected to the CCU or EUM with a Telnet session, and you may issue CLI commands to the device at the command prompt.
To Connect to a Remote CCU or EUM with Telnet

1. Ensure there is a route between the PC and the target CCU or EUM. This may require adding a route to the PC. For instructions on adding a route to the PC, refer to To Add a Route on a PC on page 135. 2. Open a Command Prompt window. (For instructions on opening a command prompt window, please refer to your operating system documentation.) 3. At the prompt, type telnet aaa.bbb.ccc.ddd and press Enter. (aaa.bbb.ccc.ddd is the IP Ethernet address of the CCU or EUM.) 4. At the password prompt, type the device password and press Enter. NOTE: The default password for CCUs and EUMs is blank, so press Enter. You are now connected to the CCU or EUM with a Telnet session, and you may issue CLI commands to the device at the command prompt.
Serial Port Connection

For units that support a serial port1, the command line can also be accessed through the serial port.
1. See LMS8000/LMS4000 Feature Support Matrix for Serial port support.
lms052_ap_01
133
To Connect Through a Serial Port

1. Connect an RS-232, DB9 male to DB9 female, straight-through cable between the console ports on the CCU or EUM and the PC. 2. Open a terminal emulation program, such as Tera Term Pro or HyperTerminal. 3. Connect to the device using the port settings shown in Table 43. Table 43 Serial Port Settings Bits per second Data bits Parity Stop bits Flow Control 9600 8 None 1 None
4. At the password prompt, type the device password and press Enter. NOTE: The default password for CCUs and EUMs is blank, so press Enter. You are now connected to the CCU or EUM with a Serial Port session, and you may issue CLI commands to the device at the command prompt.
PC Configuration
The following two procedures explain how to configure network settings on a PC running the Windows XP operating system, and how to add a static route to a PC.
To Configure PC Network Settings (Windows XP Operating System)

1. Click the Windows Start button and open Control Panel > Network Connections > Local Area Connection. 2. Click the Properties button. 3. Select Internet Protocol (TCP/IP) and click the Properties button. 4. Select Use the following IP address.
134
lms052_ap_01
5. Fill in the IP address, Subnet mask, and Default gateway fields, so the PC is on the same subnet as the EUM, and click OK.
To Add a Route on a PC
1. On the PC, open a command prompt window. 2. At the prompt, type route add aaa.bbb.ccc.ddd mask eee.fff.ggg.hhh iii.jjj.kkk.lll and press Enter. aaa.bbb.ccc.ddd is the target subnet (eg. 192.168.10.0) eee.fff.ggg.hhh is the target subnet mask (eg. 255.255.255.0) iii.jjj.kkk.lll is the gateway router address for the target subnet (eg. Ethernet IP address of the CCU)
lms052_ap_01
135
Appendix D
Windows Ping Commands
The following table lists the options available for use with a Windows Ping test. This information was obtained from Microsoft Windows 2000 TCP/IP Protocols and Services Technical Reference, pp. 184-185. Table 44 Windows Ping Test Command Options Use Sends Echoes until interrupted. Performs a Domain Name System (DNS) reverse query to resolve the DNS hose name of the specified IP address The number of Echoes to send The size of the Optional Data field up to a maximum of 65,500 Sets the Dont Fragment (DF) flag to 1 Sets the value of the TTL field in the IP header Sets the value of the Type of Service field in the IP header. The TOS value is in decimal Sends the ICMP Echoes using the IP Record Route option and sets the value of the number of slots. Count has a maximum value of 9. Sends the ICMP Echoes using the IP Internet Timestamp option and sets the value of the number of slots. Count has a maximum value of 4. Windows 2000 PING uses the Internet Timestamp FLAG set to 1 (records both the IP addresses of each hop and the timestamp. Default Not set Not set 4 32 Not set 32 0 Not set
Option -t -a -n count -l size -f -I TTL -v TOS -r count
-s count
Not set
lms052_ap_01
137
Appendix D: Windows Ping Commands
Option
-j host-list
Use
Sends the ICMP Echoes using the Loose Source Route option and sets the next hop addresses to the IP addresses in the host list. The host list is made up of IP addresses separated by spaces corresponding to the loose source route. There can be up to nine IP addresses in the lost list. Sends the ICMP Echoes using the Strict Source Route option and sets the next hop addresses to the IP addresses in the host list. The host list is made of IP addresses in the host list. The host list is made of IP addresses separated by spaces corresponding to the loose source route. There can be up to 9 IP addresses in the host list. Waits the specified amount of time, in milliseconds, for the corresponding Echo Reply before displaying a Request Timed Out message.
Default Not set
-k host-list
Not set
-w timeout
1000
138
lms052_ap_01
Index
A access . . . . . . . . . . . . . . . . . . . . . . . . 131 adaptive modulation . . . . . . . . . . 23, 24, 32 address translation table . . . . . . . . . . . 123 antenna diversity . . . . . . . . . . . . . . . . 9, 32 ARP Map table . . . . . . . . . . . . . . . . . . 126 ARP table . . . . . . . . . . . . . . . . . . . . . . 121 authentication key . . . . . . . . . . . 23, 34, 42 authorization . . . . . . . . . . . . . . . . . . . . . 39 authorization table . . . . . . . . . . . . . 23, 123 autoconfiguration . . . . . . . . . . . . . . . . . . 40 automatic frequency discovery . . . . . . . . 30 B basic configuration file . . . . . . . . . . . . . 128 billing information. . . . . . . . . . . . . . . . . 124 bridge table . . . . . . . . . . . . . . . . . . . . . 127 bundling . . . . . . . . . . . . . . . . . . . . . . . . 64 C CCU configuration . . . . . . . . . . . . . . . . . . . 7 configuration files. . . . . . . . . . . . . . . 78 data tables . . . . . . . . . . . . . . . . . . 117 receive statistics . . . . . . . . . . . . . . . 68 transmit statistics . . . . . . . . . . . . . . . 64 command line interface . . . . . . . . . . . . . . 1 configuration CCU . . . . . . . . . . . . . . . . . . . . . . . . . 7 customer list . . . . . . . . . . . . . . . . . . 35 DHCP relay . . . . . . . . . . . . . . . . . . . 15 EUM . . . . . . . . . . . . . . . . . . . . . . . . 29 port filtering . . . . . . . . . . . . . . . . 17, 35 SNMP . . . . . . . . . . . . . . . . . . . . 20, 35 time clock . . . . . . . . . . . . . . . . . . . . 18 VoIP . . . . . . . . . . . . . . . . . . . . . . . . 22 customer list . . . . . . . . . . . . . . . . . . . . . 35 D data tables . . . . . . . . . . . . . . . . . . . . . 117 default grade of service . . . . . . . . . . . . . 25 DHCP client . . . . . . . . . . . . . . . . . . . . . 34, 38 relay . . . . . . . . . . . . . . . . . . . . . 15, 37 server . . . . . . . . . . . . . . . . . . . . . . . 37 DPMAC interface statistics E encryption . . . . . . . . . . . . . . . . . . . . 34, 42 Ethernet MAC address . . . . . . . . . . . . . . . 8 Ethernet statistics . . . . . . . . . . . . . . . . . 82 EUM configuration . . . . . . . . . . . . . . . . . . 29 configuration files . . . . . . . . . . . . . . 78 data tables . . . . . . . . . . . . . . . . . . 117 password . . . . . . . . . . . . . . . . . . . . 30 receive statistics . . . . . . . . . . . . . . . 72 transmit statistics . . . . . . . . . . . . . . . 70 EUMID . . . . . . . . . . . . . . . . . . . . . . . . . . 8 F fading . . . . . . . . . . . . . . . . . . . . . . . . . . 95 feature support matrix . . . . . . . . . . . . . . . 1 field upgrade process. . . . . . . . . . . . . . . 77 frequency CCU . . . . . . . . . . . . . . . . . . . . . . . . . 9 EUM . . . . . . . . . . . . . . . . . . . . . . . . 30 H hostname I IP address. K key policy L link quality . . . . . . local link address . logging statistics . M MAC address . . . . . . . . . . . . . . . . . . . . . 8 MAC.See DPMAC maximum customers . . . . . . . . . . . . . . . 35 modulation scheme . . . . . . . . . . 23, 24, 32 monitoring . . . . . . . . . . . . . . . . . . . . . . . 61
. . . . . . . . . . . . . . 87
. . . . . . . . . . . . . . . . . . . . . . . 38 . . . . . . . . . . . . . . . . . . . . . . 33
. . . . . . . . . . . . . . . . . 23, 34, 42 . . . . . 64, 70, 93, 95, 96 . . . . . . . . . . . . . . . . 131 . . . . . . . . . . . . . 73, 115
lms052_ap_01
139
N network interface statistics monitoring . . . . . . NTP server . . . . . . . . O OFDM . . . . . . . . . . . . . . . . . . . . 23, 24, 32 operating statistics . . . . . . . . . . . . . . 61, 81 P packet error rate . . . . . . . . . . . . . . . . . . 64 password CCU . . . . . . . . . . . . . . . . . . . . . . . . . 8 EUM . . . . . . . . . . . . . . . . . . . . . . . . 30 PC Configuration . . . . . . . . . . . . . . . . . 134 PDF . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 permanent configuration file . . . . . . . . . 129 ping . . . . . . . . . . . . . . . . . . . . . . . . . . 137 port filtering . . . . . . . . . . . . . . . 17, 35, 117 priority classification . . . . . . . . . . . . . . . . 22 protocol mode . . . . . . . . . . . . . . . . . . . . 11 R radio CCU configuration . . . . . . . . . . . . . . . 9 driver statistics . . . . . . . . . . . . . . . . 84 EUM configuration . . . . . . . . . . . . . . 30 link monitor statistics . . . . . . . . . . . . 85 link quality . . . . . . . . . . . . . . . . . . . . 96 load meter . . . . . . . . . . . . . . . . 75, 109 signal strength . . . . . . . . . . . 62, 93, 95 RADIUS accounting . . . . . . . . . . . . . . . . . . . 40 attributes . . . . . . . . . . . . . . . . . . . . . 41 autoconfiguration . . . . . . . . . . . . . . . 40 client . . . . . . . . . . . . . . . . . . . . . . . . 26 database . . . . . . . . . . . . . . . . . . . . . 39 server . . . . . . . . . . . . . . . . . . . . . . . 39 statistics . . . . . . . . . . . . . . . . . . . . 103 receive statistics . . . . . . . . . . . . . . . 68, 72 registration table . . . . . . . . . . . . . . 74, 124 relay agent information. . . . . . . . . . . . . . 37 remote access . . . . . . . . . . . . . . . . . . . 131 RNA . . . . . . . . . . . . . . . . . . . . . 62, 93, 95 routed mode . . . . . . . . . . . . . . . . . . . . . 11 routing protocol statistics . . . . 99, 100, 101 routing table . . . . . . . . . . . . . . . . . . . . 118 RSSI . . . . . . . . . . . . . . . . . . . . . 62, 93, 95 S security .
. . . . . . . . . . . . . 107 . . . . . . . . . . . . . . 61 . . . . . . . . . . . . . . 18
serial number . . . . . . . . . . . . . . . . . . . . . 8 serial port . . . . . . . . . . . . . . . . . . . . . . 133 signal quality . . . . . . . . . . . . . . . . . . 62, 93 signal strength . . . . . . . . . . . . . . . . . 62, 93 SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 configuration . . . . . . . . . . . . . . . 20, 35 SNTP time clock . . . . . . . . . . . . . . . . . . 18 software upgrade . . . . . . . . . . . . . . . . . . 77 spectrum analyser . . . . . . . . . . . . . . . . . 57 SQ . . . . . . . . . . . . . . . . . . . . . . 62, 93, 95 station ID . . . . . . . . . . . . . . . . . . . . . . . . 8 statistics . . . . . . . . . . . . . . . . . . . . . 61, 81 DPMAC . . . . . . . . . . . . . . . . . . . . . 87 Ethernet . . . . . . . . . . . . . . . . . . . . . 82 logging . . . . . . . . . . . . . . . . . . 73, 115 radio driver . . . . . . . . . . . . . . . . . . . 84 radio link monitor . . . . . . . . . . . . . . . 85 RADIUS . . . . . . . . . . . . . . . . . . . . 103 routing protocol . . . . . . . . 99, 100, 101 switched Ethernet mode . . . . . . . . . . . . . 13 system load statistics . . . . . . . . . . . . . . 109 system log file . . . . . . . . . . . . . . . . 73, 115 T telnet . . . . . . . . . . . . . . . . . . . . . . . . . 131 through only mode . . . . . . . . . . . . . . . . . 14 time clock . . . . . . . . . . . . . . . . . . . . . . . 18 transmit statistics . . . . . . . . . . . . . . . 64, 70 U upgrading usage . . . V vendor class . . . . . Vendor-Id . . . . . . . VoIP . . . . . . . . . . . W watch statistics . . . . . . . . Vecima-Grade-of-Service .
. . . . . . . . . . . . . . . . . . . . . . . 77 . . . . . . . . . . . . . . . . . . . . . . 124 . . . . . . . . . . . . . . . . 38 . . . . . . . . . . . . . . . . 41 . . . . . . . . . . . . . . . . 22 . . . . . . . . . . 112 . . . . . . . . . . . 41
. . . . . . . . . . . . . . . . . . 23, 34, 42
140
lms052_ap_01
by
Last Mile Solution

lms052 Ap 01

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

lms052 Ap 01

Uploaded by

Copyright:

Available Formats

LMS8000 / LMS4000

Managing the Network

Federal Communications Commission

Warnings and Advisories

Table 36 Table 37 Table 38 Table 39 Table 40 Table 41 Table 42 Table 43 Table 44

LMS8000 / LMS4000 Features

This page is intentionally left blank

Configuring the CCU

2: Configuring the CCU

Serial Number, MAC Address, and Station ID

Setting the CCU Password

2: Configuring the CCU

Configuring the CCU RF Parameters

To Set the CCU Maximum Transmit Power Level

To Set the CCU Antenna Diversity Mode

2: Configuring the CCU

rebooting ... (... Power On Self Test ...) Password:

2: Configuring the CCU

51:00:3f*CCU2> radio Max RF Power: 26 dBm Radio Frequency: 9170

Configuring CCU Protocol Modes and IP Addresses

2.4.1 Configuring Routed Mode

To Configure the CCU to Operate in Routed Mode

51:00:3f*CCU2> ip radio 172.16.6.1 22 Radio:

2: Configuring the CCU

IP Address: 172.16.6.1 / 22 IP Subnet : 172.16.4.0 ( 255.255.252.0 )

51:00:3f*CCU2>ip ethernet 192.168.10.8 24 Ethernet: IP Address: 192.168.10.8 / 24 IP Subnet : 192.168.10.0 ( 255.255.255.0 )

6. Type save and press Enter to save the new settings.

7. Type reset and press Enter to reboot the CCU.

9. Type ip and press Enter to display the ip addresses.

2: Configuring the CCU

2.4.2 Configuring Switched Ethernet Mode

4. Type save and press Enter to save the new settings.

5. Type reset and press Enter to reboot the CCU.

7. Type ip and press Enter to display the ip addresses.

2: Configuring the CCU

2.4.3 Configuring Through Only Mode

To Configure Through Only Mode

4. Type save and press Enter to save the new settings.

5. Type reset and press Enter to reboot the CCU.

7. Type ip and press Enter to display the ip addresses.

2: Configuring the CCU

IP Address: 192.168.10.8 / 24 IP Subnet : 192.168.10.0 ( 255.255.255.0 ) Gateway IP Address: 192.168.10.9

Configuring DHCP Relay

To Enable DHCP Relay

To Add a DHCP Server

2: Configuring the CCU

To Filter Ethernet Port DHCP Requests

2: Configuring the CCU

Configuring Port Filtering

To Add a Port Filter

2: Configuring the CCU

Configuring the SNTP UTC Time Clock

To Add an NTP Server

To Enable the SNTP Client

2: Configuring the CCU

51:00:3f*CCU2>time client enable Time Client enabled

To Enable SNTP Relay

To Display the SNTP Configuration and NTP Server List

To Display System Time

To Force a Time Update

Yes Primary Radio IP broadcast 240

2: Configuring the CCU

To Set the SNMP Contact