Vecima Networks EUM3003 Wireless LAN end-user modem User Manual LMS4000 900 MHz Guide

Vecima Networks Inc. Wireless LAN end-user modem LMS4000 900 MHz Guide

Contents

Users Manual

LMS4000900 MHz Radio NetworkUser GuideAPCD-LM043-4.0
WaveRider Communications Inc.Software License AgreementThis is a legal agreement between you (either an individual or an entity) and WaveRider Communications Inc.for the use of WaveRider computer software, hereinafter the “LICENSED SOFTWARE”.By using the LICENSED SOFTWARE installed in this product, you acknowledge that you have read thislicense agreement, understand it, and agree to be bound by its terms. You further agree that it is the fulland complete agreement between you and WaveRider Communications Inc., superseding all prior writ-ten or verbal agreements of any kind related to the LICENSED SOFTWARE. If you do not understand ordo not agree to the terms of this agreement, you will cease using the LICENSED SOFTWARE immedi-ately.1. GRANT OF LICENSE—This License Agreement permits you to use one copy of the LICENSEDSOFTWARE.2. COPYRIGHT—The LICENSED SOFTWARE is owned by WaveRider Communications Inc. and isprotected by copyright laws and international treaty provisions; therefore, you must treat the LICENSEDSOFTWARE like any other copyrighted material (e.g., a book or magazine). You may not copy the writtenmaterials accompanying the LICENSED SOFTWARE.3. LIMITS OF FEATURE AVAILABILITY—The LICENSED SOFTWARE is sold with limitations as to certainfeature availability and use. These limits are governed by the terms of the purchase agreement. Anyactions resulting in the exceeding of these limits is not permitted, and can result in unpredictableperformance.4. OTHER RESTRICTIONS—You may not rent or lease the LICENSED SOFTWARE. You may notreverse engineer, decompile, or disassemble the LICENSED SOFTWARE.5. LIMITED WARRANTY—The LICENSED SOFTWARE is provided “as is” without any warranty of any kind,either expressed or implied, including, but not limited to, the implied warranties of merchantability andfitness for a particular purpose. The entire risk as to the quality and performance of the LICENSEDSOFTWARE is with you, the licensee. If the LICENSED SOFTWARE is defective, you assume the riskand liability for the entire cost of all necessary repair, service, or correction.Some states/jurisdictions do not allow the exclusion of implied warranties, so the aboveexclusion may not apply to you. This warranty gives you specific legal rights, and you mayhave other rights, which vary from state/jurisdiction to state/jurisdiction.WaveRider Communications Inc. does not warrant that the functions contained in theLICENSED SOFTWARE will meet your requirements, or that the operation of theLICENSED SOFTWARE will be error-free or uninterrupted.6. NO OTHER WARRANTIES—To the maximum extent permitted by applicable law, WaveRiderCommunications Inc. disclaims all other warranties, either express or implied, including, but not limited to,the implied warranties of merchantability and fitness for a particular purpose, with regard to theLICENSED SOFTWARE and the accompanying written materials.7. NO LIABILITY FOR CONSEQUENTIAL DAMAGES—To the maximum extent permitted by applicable law,in no event shall WaveRider Communications Inc. or its suppliers be liable for any damages whatsoever(including, without limitation, damages for loss of business profits, business interruption, loss of businessinformation, or any other pecuniary loss) arising from the use of or inability to use the LICENSEDSOFTWARE, even if WaveRider Communications Inc. has been advised of the possibility of suchdamages, or for any claim by any other party.Because some states/jurisdictions do not allow the exclusion or limitation of liability forconsequential or incidental damages, the above limitation may not apply to you.In no event will WaveRider’s liability exceed the amount paid for the LICENSEDSOFTWARE.
The following are trademarks or registered trademarks of their respective companiesor organizations:Microsoft Windows NT 4.0 Workstation (with Service Pack 6a), Microsoft Access,Microsoft SQL Server, Microsoft SQL Agent / Microsoft CorporationVircom VOP Radius Server / Vircom Inc.Castlerock SNMPc Server / Castle Rock ComputingAPS PowerChute PLUS / American Power ConversionVeritas Backup Exec / VERITAS Software© 2002 by WaveRider Communications Inc. All rightsreserved. This manual may not be reproduced by any meansin whole or in part without the express written permission ofWaveRider Communications Canada Inc.ISSUE 4.0, April 2002
WarrantyIn the following warranty text, “WaveRider®” shall mean WaveRider Communications Inc.This WaveRider product is warranted against defects in material and workmanship for a period of one (1)year from the date of purchase. During this warranty period WaveRider will, at its option, either repair orreplace products that prove to be defective.For warranty service or repair, the product must be returned to a service facility designated by WaveR-ider. Authorization to return products must be obtained prior to shipment. The WaveRider RMA numbermust be on the shipping documentation so that the service facility will accept the product. The buyer shallpay all shipping charges to WaveRider and WaveRider shall pay shipping charges to return the productto the buyer within Canada or the USA. For all other countries, the buyer shall pay shipping charges aswell as duties and taxes incurred in shipping products to or from WaveRider.WaveRider warrants that the firmware designed by it for use with the unit will execute its programminginstructions when properly installed on the unit. WaveRider does not warrant that the operation of the unitor firmware will be uninterrupted or error-free.Limitation of WarrantyThe foregoing warranty shall not apply to defects resulting from improper or inadequate maintenance bythe buyer, buyer-supplied interfacing, unauthorized modification or misuse, operation outside the envi-ronmental specifications for the product, or improper site preparation or maintenance. No other warrantyis expressed or implied. WaveRider specifically disclaims the implied warranties of merchantability andfitness for any particular purpose.No Liability for Consequential DamagesTo the maximum extent permitted by applicable law, in no event shall WaveRider or its suppliers be liablefor any damages whatsoever (including, without limitation, damages for loss of business profits, businessinterruption, loss of business information, or any other pecuniary loss) arising from the use of or inabilityto use the product, even if WaveRider has been advised of the possibility of such damages, or for anyclaim by any other party.Because some states/jurisdictions do not allow the exclusion or limitation of liability for consequential orincidental damages, the above limitation may not apply to you.In no event will WaveRider’s liability exceed the amount paid for the product.Regulatory NoticesThis equipment has been tested and found to comply with the limits for a Class B Intentional Radiator,pursuant to Part 15 of the FCC Regulations and RSS-210 of the IC Regulations. These limits areintended to provide protection against harmful interference when the equipment is operated in a residen-tial environment.This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used inaccordance with the instruction manual, may cause harmful interference to radio communications. How-ever, there is no guarantee that interference will not occur in a particular installation.Notice to UserAny changes or modifications to equipment that are not expressly approved by the manufacturer mayvoid the user’s authority to operate the equipment.
APCD-LM043-4.0 vContentsContents.................................................................vFigures ..................................................................ixTables...................................................................xiPreface .................................................................xv1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12QuickStartup ...............................................52.1Equipment...........................................................52.2EquipmentSetup .....................................................62.3CCUConfiguration....................................................72.4EUMConfiguration....................................................82.5TestingCCU–EUMCommunications......................................92.6ConnectingtheQuickStartuptotheInternet...............................112.7AddingmoreEUMstotheQuickStartup ..................................123DetailedDescription ........................................133.1LMS4000Overview...................................................133.2CommunicationsAccessPoint..........................................143.2.1KeyComponents...............................................143.2.2OptionalComponents ...........................................173.3Customer-premisesEquipment .........................................183.3.1KeyComponents...............................................183.3.2EUM ........................................................193.4BasicOperation .....................................................223.4.1LMS4000TransmissionConcept ..................................223.4.2CCUandEUMConfiguration .....................................223.4.3LMS4000ProtocolStacks........................................243.4.4BasicDataTransmission ........................................243.5 CCU–EUM Interface — Detailed Technical Description. . . . . . . . ...............283.5.1PhysicalLayer(DSSSRadio) .....................................283.5.2MACLayer(PollingMAC) ........................................363.6CCUandEUMFeatureDescription......................................483.6.1DHCPRelay ..................................................483.6.2PortFiltering ..................................................493.6.3SNTP/UTCTimeClock ..........................................503.6.4CustomerList .................................................513.6.5 SNMP Support . . . . ............................................514IPNetworkPlanning ........................................534.1LMS4000IPAddressing...............................................534.2IPPlanningProcess..................................................55
vi APCD-LM043-4.04.3NetworkAddressTranslation .......................................... 575RadioNetworkPlanning.....................................595.1DesignMethodology................................................. 595.2BasicSystemDesign ................................................ 605.2.1OverviewofBasicSystemDesign..................................605.2.2SpectralSurveyoftheTargetServiceArea ..........................605.2.3In-bandInterference ............................................615.2.4Out-of-bandInterference .........................................615.2.5UsingBandpassFiltersatCAPSites ...............................635.2.6Single-orMulti-CAPImplementation................................645.3Multi-CAPRFNetworkDesignConsiderations............................. 675.3.1Multi-CAPNetworkDesignProcess ................................675.3.2FrequencySelection—StandardFrequencySet ......................675.3.3C/IRequirements...............................................685.3.4DealingwithExternalInterference..................................695.3.5VerifyingtheDesign ............................................695.3.6SummaryofRFDesignGuidelines .................................716 Installation/Diagnostic Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736.1IndicatorsandConnectors ............................................ 746.1.1NetworkLED ..................................................756.1.2RadioLED ....................................................756.1.3PowerLED ...................................................756.1.4EthernetLEDs .................................................766.2Command-lineInterface .............................................. 766.3EUMConfigurationUtility ............................................. 776.4RSSI/TxQuality/AntennaPointing ...................................... 776.5TransferaFiletoorfromaCCUUsingFTP............................... 786.6OperatingStatistics.................................................. 796.7SNMP ............................................................ 806.8FieldUpgradeProcess............................................... 806.9FTPingCCUandEUMConfigurationFiles................................ 817ConfiguringtheCCU........................................837.1CCUandEUMSerialNumber,MACAddress,andStationID................. 847.2SettingtheCCUPassword............................................ 847.3ConfiguringtheCCURFParameters.................................... 857.4ConfiguringCCUIPParameters........................................ 867.5 Configuring DHCP Relay. . . . . . ........................................ 887.6ConfiguringPortFiltering.............................................. 897.7ConfiguringtheSNTP/UTCTimeClock .................................. 907.8ConfiguringSNMP................................................... 937.9AddingEUMstotheAuthorizationTable ................................. 958ConfiguringtheEUM .......................................978.1SettingtheEUMPassword............................................ 988.2ConfiguringtheEUMRFParameters.................................... 988.3ConfiguringEUMIPParameters........................................ 998.4ConfiguringPortFiltering............................................. 101
APCD-LM043-4.0 vii8.5ConfiguringSNMP ..................................................1028.6ConfiguringtheCustomerList .........................................1049 Installing the EUM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1059.1BeforeyouStarttheEUMInstallation....................................1059.2OtherEUMProgrammingConsiderations ................................1069.3InstallationOverview.................................................1069.4InstallationProcedures...............................................1079.4.1OpeningtheBox ..............................................1079.4.2TurningofftheEnd-user’sCordlessPhones ........................1089.4.3ChoosingaLocationfortheEUMandAntenna ......................1089.4.4ConnectingtheEUMComponents ................................1089.4.5ConductingaPreliminaryCheckoftheEUM ........................1109.4.6PositioningtheAntenna ........................................1119.4.7MountingtheAntenna..........................................1129.4.8ConnectingtheEnd-user’sPC ...................................1159.4.9ObtainingValidIPAddressesfortheEnd-user’sPC ..................1169.4.10TestingtheDataLink .........................................1169.4.11ConfiguringtheBrowserApplication ..............................1199.4.12CompletingtheInstallation .....................................1209.4.13BaseliningtheInstallation ......................................1209.4.14 Troubleshooting . . ...........................................12110MaintainingtheNetwork ...................................12511MonitoringtheNetwork....................................12711.1CCUTransmitStatistics.............................................12711.2CCUReceiveStatistics..............................................13111.3EUMStatisticsMonitoring............................................13211.3.1EUMTransmitStatistics .......................................13211.3.2EUMReceiveStatistics........................................13311.3.3UserData ..................................................13412 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13512.1EUMTroubleshooting...............................................13612.2CCUTroubleshooting...............................................14512.3IfYouHaveanInterferer.............................................14912.4GeneralTroubleshootingInformation...................................15113SpecializedApplications...................................15513.1EUMThinRoute...................................................15513.2EUMBackhaul ....................................................156
viii APCD-LM043-4.0Appendix A Specifications .............................................157Appendix B FactoryConfiguration .......................................159Appendix C Command-LineSyntax ......................................163Appendix D AntennaGuidelines.........................................181Appendix E CCU/EUM Data Tables . . . . . . . . . . . . . . . ........................183Appendix F PingCommands ...........................................197Appendix G SNMPMIBDefinitions .......................................199Appendix H OperatingStatistics.........................................223Appendix I IPPlan—Example .........................................241Appendix J AcronymsandGlossary .....................................253Index ..................................................................261
APCD-LM043-4.0 ixFiguresFigure1 QuickStartup—CCUConfiguration...............................6Figure2 QuickStartup—EUMConfiguration ..............................8Figure3 QuickStartup—PingTest(fromconsoleport) ......................9Figure4 QuickStartup—PingTest(fromEUMEthernetport) ................10Figure5 QuickStartup—ConnectingtotheInternet ........................11Figure6 LMS4000System ............................................14Figure7 CCU ......................................................15Figure8 CCUFunctionalBlocks ........................................15Figure9 CCUShelf ..................................................16Figure10 RFSM .....................................................18Figure11 EUM ......................................................19Figure 12 WaveRider Indoor Directional Antenna with Switched-beam Diversity . . . . 20Figure 13 WaveRider Switched-beam Diversity Antenna — Beam Patterns . . . . . . . 21Figure14 LMS4000TransmissionConcept ................................22Figure15 LMS4000ProtocolStacks......................................24Figure16 AddressingofIPPackets ......................................26Figure17 DeterminationofLowestandHighestChannel......................28Figure18 EffectofDespreading .........................................30Figure19 TypicalNLOSPath ...........................................32Figure20 ExamplesofRadioPaths ......................................33Figure21 PathLossCalculation .........................................34Figure22 EUMStateDiagram ..........................................36Figure 23 Net Throughput per EUM — 100 EUMs, 60 kbyte HTTP every 2 minutes . 43Figure 24 Associated EUMs — 100 EUMs, 60 kbyte HTTP every 2 minutes . . . . . . . 44Figure 25 Net Throughput per EUM — 300 EUMs, 60 kbyte HTTP every 2 minutes . 45Figure 26 Associated EUMs — 300 EUMs, 60 kbyte HTTP every 2 minutes . . . . . . . 45Figure 27 DHCP Relay . . . . ............................................49Figure28 SNTP/GMTTimeClock........................................50Figure29 LMS4000Subnets............................................54Figure30 ExampleofaSpectralSweep ...................................62Figure 31 Network Design in the Presence of Out-of-band Interference . . . . . . . . . . 63Figure32 Corner-andCenter-illuminatedcells..............................65Figure33 SectoredCell................................................66
xAPCD-LM043-4.0Figure34 EUMLEDsandConnectors.....................................74Figure35 CCULEDsandConnectors.....................................74Figure36 EthernetLEDs ...............................................76Figure37 EUMComponents ...........................................107Figure 38 Connecting the EUM Components . . . . . . ........................109Figure39 ConnecttheDCPowerCordtotheEUM .........................109Figure40 ConnecttheACPowerCord ...................................110Figure41 EUMLEDs.................................................110Figure 42 Preliminary Orientation of the Antenna (Top View) . . . . . . . ...........111Figure43 RearViewofAntennaBracket..................................112Figure 44 Antenna Bracket Components . . . . . . . . . . ........................113Figure45 MountingtheAntennaintheBracket.............................114Figure46 ConnectingtheEnd-user’sPC .................................115Figure47 SampleConfiguration—TestingtheDataLink.....................117Figure48 EthernetPlug(BottomView) ...................................152Figure49 UsinganEUMforThinRoute ..................................155Figure50 UsinganEUMforBackhaul....................................156Figure51 CCUMIBs .................................................203Figure52 EUMMIBs .................................................213
APCD-LM043-4.0 xiTablesTable1 ConsoleSettings ..............................................6Table2 QuickStartup—EUMAddresses................................12Table3 CCUConfiguration ...........................................23Table4 EUMConfiguration ...........................................23Table5 End-userPCConfiguration .....................................24Table6 LMS4000900MHzRadioNetworkChannelization...................29Table7 TypicalRadioCoverage .......................................35Table8 FactoryDefaultGOSConfigurationFile ...........................41Table9 FactoryConfiguredCommunityStrings ...........................51Table 10 Example — CCU Radio Subnet IP Addressing . . . . . . . ...............56Table 11 Standard Frequency Set . . . . . . . . . . . ............................68Table12 RequiredC/IRatioforMulti-CAPDesign ..........................68Table13 SampleFrequencyPlan—Multi-CAPDesign ......................69Table14 SummaryofRFDesignGuidelines...............................71Table15 NetworkLED ................................................75Table16 RadioLED..................................................75Table17 PowerLED .................................................75Table18 EthernetLEDs...............................................76Table19 ConsoleSettings.............................................77Table20 FTPingConfigurationFiles .....................................81Table21 RadioLEDStatusDisplays ....................................111Table22 AntennaMountGuidelines ....................................112Table23 SurfaceMountingOptionsfortheAntenna ........................113Table24 EthernetLEDStatusDisplays..................................115Table25 TemperatureandHumidityRequirements ........................125Table26 PossibleTransmissionOutcomes...............................128Table27 TypicalCCUTransmitStatistics ................................129Table28 TypicalCCUReceiveStatistic .................................131Table29 EUMTransmitStatistics ......................................132Table 30 Remote Troubleshooting — EUM (Service Not Available) . . . . . . . . . . . . 138Table31 RemoteTroubleshooting—EUM(ServiceDegraded) ...............139Table32 LocalTroubleshooting—EUM(ServiceNotAvailable) ..............140Table33 LocalTroubleshooting—EUM(ServiceDegraded) .................142
xii APCD-LM043-4.0Table 34 Remote Troubleshooting — CCU . . . . . . . ........................146Table35 LocalTroubleshooting—CCU .................................147Table36 GeneralNetworkProblems ....................................151Table37 EthernetCablingProblems ....................................152Table38 RadioSpecifications .........................................157Table39 EthernetInterfaceSpecifications ...............................158Table 40 Power Supply Specifications . . . . . . . . . . ........................158Table41 EnvironmentalSpecifications ..................................158Table42 CCUFactoryConfiguration ....................................159Table43 EUMFactoryConfiguration ....................................160Table44 Command-LineSyntaxConventions .............................164Table45 Command-LineShortcutsandGettingHelp .......................164Table46 CCUCommand-LineSyntax ..................................165Table47 EUMCommand-LineSyntax ...................................174Table 48 CCU, EUM Supported Antennas . . . . . . . . ........................181Table49 PortFilterTableEntries.......................................184Table50 BasicCCURoutes...........................................184Table51 RoutingTableEntries ........................................185Table52 RoutingTableFlags. .........................................186Table53 ARPTableEntries ...........................................187Table54 RegistrationTableEntries .....................................190Table55 ARPMAPTableEntries ......................................191Table56 CustomerTableEntries.......................................192Table57 RSSI/RSSCross-referenceforSampleUnit(at915MHz) ............195Table58 WindowsPingTestCommandOptions...........................197Table59 GroupsinMIB-II.............................................199Table 60 MIB-II Interface List Header MIB . . . . . . . . ........................200Table61 MIB-IIInterfaceListTableMIB .................................200Table62 WaveRiderCCUBaseMIB ....................................203Table63 WaveRiderCCUGeneralInformationEnterpriseMIBs...............204Table64 WaveRiderCCURadioConfigurationEnterpriseMIBs...............204Table65 WaveRiderCCURadioStatisticsMIB............................205Table66 WaveRiderCCURadioGeneralStatisticsGroupMIB ...............205Table67 WaveRiderCCURadioDriverStatisticsGroupMIB .................205Table68 WaveRiderCCURadioMACStatisticsGroupMIB..................206Table69 WaveRiderCCUEthernetStatisticsGroupMIB ....................210Table70 WaveRiderCCUModemInformationMIB.........................211Table71 WaveRiderCCURegistrationInformationMIB .....................211
APCD-LM043-4.0 xiiiTable72 WaveRiderCCURegistrationTableMIB .........................211Table73 WaveRiderCCUAuthorizationTableMIB ........................212Table74 WaveRiderCCUAuthorizationTableMIB ........................212Table75 CCURFCMIB-IITraps .......................................212Table76 WaveRiderEUMBaseMIB....................................213Table77 WaveRiderEUMGeneralInformationEnterpriseMIBs ..............214Table78 WaveRiderEUMRadioConfigurationEnterpriseMIBs ..............214Table79 WaveRiderEUMRadioStatisticsMIB ...........................215Table80 WaveRiderEUMRadioGeneralStatisticsGroupMIB ...............215Table81 WaveRiderEUMRadioDriverStatisticsGroupMIB.................215Table82 WaveRiderEUMRadioMACStatisticsGroupMIB .................216Table83 WaveRiderCCUEthernetStatisticsGroupMIB ....................219Table84 EUMRFCMIB-IITraps .......................................221Table85 EthernetStatistics ...........................................224Table86 RadioDriverStatistics........................................226Table87 MACInterfaceStatistics ......................................228Table88 Routing/BridgingProtocolStatistics .............................233Table89 NetworkInterfaceStatistics....................................236Table90 LoadStatistics(RadioMeter) ..................................239Table91 Example-CCUEthernetSubnetData ...........................241Table92 Example-NAPIPAddressingPlan .............................241Table93 Example-CCUEthernetIPAddressingPlan ......................242Table94 Example-CCURadioSubnetData .............................243Table95 Example-CCURadioIPAddressingPlan ........................243Table96 Example-EUMSubnetData ..................................245Table97 Example-EUMIPAddressingPlan .............................245Table98 Example-SubscriberSubnetData..............................248Table99 Example-SubscriberIPAddressingPlan ........................248Table100 AcronymsandAbbreviations ..................................253Table101 LMS4000NetworkGlossary ...................................256
—This page is intentionally left blank —
APCD-LM043-4.0 xvPrefaceAbout this ManualWaveRider recommends that you read the following sections before proceeding with theinstructions in this guide:•Software License Agreement on page ii•Warranty on page iv•Warnings and Advisories on page xvii•Conventions on page xvNOTE: The information contained in this manual is subject to changewithout notice. The reader should consult the WaveRider website for updates.The procedures in this document are centered around the command-line interface (CLI). Forinformation about configuring and operating the CCU and EUM using the WaveRiderConfiguration Utility refer to the CCU/EUM Configuration Utility User Guide (APCD-LM030).ConventionsThe following conventions are used throughout this document:WARNING!Whenever you see this icon and heading, the associated textaddresses or discusses a critical safety or regulatory issue.CAUTION: Whenever you see this icon and heading, theassociated text discusses an issue, which, if not followed, couldresult in damage to, or improper use of, the equipment orsoftware.TIP: Whenever you see this icon and heading, the associatedtext provides a tip for facilitating the installation, testing, oroperation of the equipment or software
xvi APCD-LM043-4.0Regulatory NoticesThis device has been designed to operate with several different antenna types. The gain ofeach antenna type shall not exceed the maximum antenna system gain as given in AppendixDonpage181. Antennas having a higher gain are strictly prohibited by Industry Canada andFCC regulations. The required antenna impedance is 50 ohms.Industry CanadaCCU and EUMThe IC Certification Number for the CCU and EUM is 3225104140A.Operators must be familiar with IC RSS-210 and RSS-102. The CCU and EUM havebeen designed and manufactured to comply with IC RSS-210 and RSS-102.Federal Communications CommissionCCU and EUMThe CCU and EUM have been designed and manufactured to comply withFCC Part 15.Operators must be familiar with the requirements of the FCC Part 15 Regulations priorto operating any link using this equipment. For installations outside the United States,contact local authorities for applicable regulations.The FCC ID for the CCU and EUM equipment is OOX-LMS3000.The transmitter of this device complies with Part 15.247 of the FCC Rules.The CCU and EUM (with outdoor antenna only) must be professionally installed.Interference EnvironmentOperation is subject to the following conditions:• This device may not cause harmful interference and,• This device must accept any interference received, including interference thatmight cause undesired operation.
APCD-LM043-4.0 xviiOperational RequirementsCCU and EUMIn accordance with the FCC Part 15 regulations:1. The maximum peak power output of the intentional radiator shall not exceedone (1) watt for all spread spectrum systems operating in the 902 to 928MHzband. This power is measured at the antenna port of the CCU or the EUM.2. Stations operating in the 902 to 928MHz band may use transmitting antennasof directional gain greater than 6dBi, provided the peak output power from theintentional radiator is reduced by the amount in dB that the directional gain ofthe antenna exceeds 6dBi.NOTE: The gains referred to in point 2 are with respect to the totalantenna system gain.3. The operator of a spread spectrum system and the user of the radio deviceare each responsible for ensuring that the system is operated in the manneroutlined in Interference Environment on page xvi.Warnings and AdvisoriesGeneral AdvisoryOperator and maintenance personnel must be familiar with the related safety requirementsbefore they attempt to install or operate the LMS4000 equipment.It is the responsibility of the operator to ensure that the public is not exposed to excessiveRadio Frequency (RF) levels. The applicable regulations can be obtained from localauthorities.Do not operate the CCU or EUM without connecting a 50-ohm termination to the antenna port.This termination can be a 50-ohm antenna or a 50-ohm resistive load capable of absorbing thefull RF output power of the transceiver.WARNING!The LMS4000 external antennas must be professionallyinstalled and properly grounded. Antennas and associatedtransmission cable must be installed by qualified personnel.WaveRider assumes no liability for failure to adhere to thisrecommendation or to recognized general safety precautions.
xviii APCD-LM043-4.0WARNING!To comply with FCC RF exposure limits, the antennas for theCCU must be fix-mounted on outdoor permanent structures toprovide a separation distance of 2m or more from all personsto satisfy RF exposure requirements. The distance ismeasured from the front of the antenna to the human body. Itis recommended that the antenna be installed in a locationwith minimal pathway disruption by nearby personnel.The antennas for the EUM must be fix-mounted, indoors oroutdoors, to provide a separation distance of 20cm or morefrom all persons to satisfy RF exposure requirements. Thedistance is measured from the front of the antenna to thehuman body. Again, it is recommended that the antenna beinstalled in a location with minimal pathway disruption bynearby personnel.CAUTION: There is a DC signal of 5-7.5V (current limited to5mA) on the Antenna Output of the EUM. Antennas or RF testequipment must be able to accept this DC signal or have a deviceto block the DC signal. Otherwise, the antenna, test equipment,and/or the EUM may be damaged.Customer SupportIf you have any problems with the instructions in this manual, please contact WaveRiderCommunications Inc.WaveRider offers a complete training program. Please contact your sales representative fortraining information.Telephone: +1 416–502–3161Fax: +1 416–502–2968Email: Customer Services Group:techsupport@waverider.comCustomer Documentation Feedback and Comments:customerdocs@waverider.comURL: www.waverider.com
APCD-LM043-4.0 11IntroductionThe LMS4000 system provides 900MHz and 2.4GHz wireless. high-speed Internetconnectivity to business and residential subscribers. This manual, which is specific to theLMS4000 900MHz Radio Network, provides the following information:• A detailed description of the operation of the hardware and software• Guidelines for planning and designing your network• Instructions for configuring, installing the 900MHz radio modem, monitoring,maintaining and troubleshooting• Support information that you may find useful for operating your networkTIP: The installation of other LMS4000 network equipment isdescribed in LMS4000 Installation Guide, which can be obtainedfrom WaveRider.The LMS4000 900MHz Radio Network, which operates in the 900MHz ISM band, offers thefollowing features and benefits:•Excellent Propagation Characteristics: LMS4000 900MHz radio networks provideexcellent coverage to non-line of sight installations using WaveRider’s proprietaryindoor diversity antenna and extended coverage to installations using external high-gain antennas.The 900MHz ISM band is more suited to NLOS (non-line of sight)wireless Internet applications than other ISM bands because it has superiorpropagation 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 LMS4000 900MHz Radio Network provides a raw channelbit rate of 2.75Mbps, which translates to peak FTP rates of 2Mbps.•High-performance Polling MAC: WaveRider’s patented Polling MAC algorithmtakes advantage of typical usage patterns found in Internet transactions, such as Webbrowsing and email, to provide an operating capacity of up to 300 end users per RF
1 Introduction2APCD-LM043-4.0channel. Even with large numbers of subscribers, end users generally perceive thatthey have the entire channel to themselves.•Grade of Service Support: The Polling MAC supports up to four end-user grades ofservice, which allows the system operator to segment service offerings for those usersthat demand and are willing to pay for higher grades of service, and those that areonly willing to pay for a more basic grade of service.•License-free Radio Bands: The main advantage of using the ISM band is that youneed not apply to the FCC or Industry Canada for an operating license. This freedomreduces your time to market and the effort and high cost associated with obtaining alicense.•Robust Hardware and Software: LMS4000 hardware and software have beenrigorously tested in lab and field environments. The hardware, which is mechanicallyrobust, works over a broad range of temperatures and operating conditions. Thesoftware is equally robust and has been designed to recover automatically fromunplanned events and abnormal operating conditions.•Simple End-user Modem Configuration: The end-user modem is very easy toconfigure. Normally, operators pre-configure the EUM prior to field deployment, sothey can maintain control over their network.•Simple End-user Modem Installation and Operation: It is very easy to install andoperate the EUM. So easy, in fact, that when the installation is based on theWaveRider indoor diversity antenna, the end user should be able to install andoperate the modem with no involvement from the network operator. This simplicitysaves the network operator the cost and inconvenience of having to visit the end-user’s premises. The EUM uses a standard Ethernet interface which means the EUMand the antenna can be located up to 100m from the end-user’s PC.•Flexible Network Topology: The LMS4000 900MHz Radio Network has a flexibletopology, allowing it to line up with the operator’s existing Internet points of presenceand site facilities. As well, LMS4000 supports the following connections:• Connection between the end-user modem and the Internet through thenetwork operator’s gateway router• Direct connection between end-user modems through the LMS4000 900MHzchannel units (CCUs), if the CCU is configured to support this routing• Connection between end-user modems on different, but colocated, CCUs ifthese routes are configured in the CCU routing tables•DHCP Relay: CCUs support DHCP relay, which, once enabled, allows end-user PCsto automatically obtain their IP and DNS server addresses from the network operator’sDHCP servers. DHCP relay simplifies the EUM installation even further and makes iteven easier for the modem to be installed by the end user.•End-user Registration: All end user modems automatically transmit a registrationrequest to the LMS4000 system so they can access the wireless network. They canonly register if the network operator has authorized them in the CCU. This registrationguarantees that only approved subscribers can gain access to LMS4000 wirelessservices.•Remote System Configuration and Diagnostics: The network operator canconfigure and monitor CCUs and EUMs from anywhere. This remote access allowsthe operator to make configuration changes, download new features, and diagnoseproblems remotely without having to visit distant network sites or end-user premises.
1 IntroductionAPCD-LM043-4.0 3•SNMP Support: Using WaveRider-supplied SNMP MIBs, network operators canintegrate the LMS4000 with their existing network management system to allowmonitoring of CCUs and EUMs from an existing and/or centralized SNMP manager.Once SNMP is configured, the operator can monitor system events, parameters, andstatistics in real time. Statistics can be processed in the SNMP manager to providealarms, trend data, graphical outputs, and derived performance data.•Channel Redundancy (optional): Optional CCU redundancy, which can be orderedfrom WaveRider, improves LMS4000 system reliability, and reduces or eliminatesdown time if a CCU fails. This redundancy eliminates interruption of service to the endusers and reduces the urgency for getting to the CCU site to replace the failed CCU.•Accurate Time Stamping (SNTP): The CCUs and EUMs can be programmed tosynchronize their internal clocks with one or more NTP servers. Time stampingenables all logged events in the CCUs and EUMs to be correlated with events thathave taken place at other locations in the network or with events logged by equipmentinstalled outside the network, if this equipment is equipped with accurate time-stamping. Accurate time-stamping facilitates diagnosis of complex network problems.•Field-replaceable Equipment: In the event of an equipment failure, LMS4000components are easily replaced with minimal or no disruption to the operation of othercomponents.•System Upgradability: The LMS4000 network architecture supports orderly growthfrom simple installations, through single-CCU CAP (Communication Access Point)sites and multi-CCU CAP sites, to multi-CAP networks.•Port Filtering: The LMS4000 network operator can configure CCUs and EUMs tofilter IP packets on specific TCP and UDP ports to improve network performance,security, and privacy.•Low Maintenance: CCUs and EUMs require no routine maintenance, other thanmaintenance of their operating environments within the specified temperature andhumidity range.•Extensive Installation, Maintenance and Diagnostic Support: TheCCUandEUMare equipped with a wide range of features and utilities to facilitate unit installation,operation, maintenance, monitoring, and diagnostics:• Visual status indicators on all units• Simple-to-use command-line interface, offering full unit configurationcapability• Windows-based EUM configuration and installation utilities• RSSI (receive signal strength indication) output, to simplify antenna pointingand performance measurement• Ability to remotely FTP files to and from CCUs and EUMs• Wide range of operating and performance statistics• SNMP support• Simple and reliable field-upgrade process• Remote download of equipment configuration files to CCUs and EUMsYour decision to implement an LMS4000 900MHz Radio Network enables you to deliver high-quality, high-speed wireless Internet service to the business and residential subscribers inyour serving area.
—This page is intentionally left blank —
APCD-LM043-4.0 52Quick StartupThis section outlines the procedure for setting up a very simple LMS4000 900 MHz radionetwork consisting of one CCU and one EUM. This simple network, which can be set up in alab environment, helps you become familiar with basic LMS4000 configuration and operation.As you become more confident and are ready to progress to customer installations,WaveRider recommends you read the other sections in the manual.Quick Startup uses static IP addresses for the purpose of simplicity, even though the CCU andEUM support DHCP relay.2.1 EquipmentAs a minimum, the Quick Startup requires the following equipment:one CCU kit, consisting of• CCU• CCU power supply and cable• CCU setup antennaone EUM kit, consisting of•EUM• EUM power supply and cable• 3m CAT5 crossover Ethernet cableone PC, equipped with terminal emulation software such as HyperTerminal and anEthernet network interface cardone WaveRider indoor antenna, complete with mounting bracket and RF cableone Straight-through RS-232 serial cable, DB-9 male to DB-9 female
2 Quick Startup6APCD-LM043-4.02.2 Equipment Setup1. Remove the equipment from the boxes and set up the physical configuration shown inFigure 1. Use this setup procedure to configure the CCU, while keeping the followingpoints in mind:• Maintain the order of installation shown in Figure 1.• Maintain at least 3 to 5 meters of physical separation between CCUs andEUMs.• Ensure the paths between the CCU and EUMs are relatively free fromobstruction.Figure 1 Quick Startup — CCU ConfigurationCAUTION: Always make sure that you connect the antenna tothe CCU or EUM before you apply power to the unit.2. Configure your PC terminal emulation software as shown in Table 1.Table 1 Console SettingsBits per second 9600Data bits 8Parity NoneStop bits 1Flow Control NoneCCU3000RS232 cableCCU set-upantennaCCU powersupplyEUM3000EUM AntennaEUM Power Supply13-5metres234567RadioLink
2QuickStartupAPCD-LM043-4.0 72.3 CCU Configuration1. Start the PC terminal emulation software. You will receive the following prompt:WaveRider Communications, Inc. LMS3000Password:The default password is a carriage return.Console>The default prompt on your CCU is the CCU Ethernet MAC address.2. Type the following commands to configure the CCU:Console> ip ethernet 192.168.10.10 24Console> ip radio 10.0.0.1 22Console> ip gateway 192.168.10.1Console> radio frequency 9150Console>Console> saveBasic Config savedPort Filter Config savedsntp cfg file savedRoute Config savedAuthorization Database savedDHCP Server Config saved3. Reboot the CCU for the changes to take effect.Console> resetrebooting CCU ...(... Power On Self Test ...)WaveRider Communications, Inc. LMS3000Password:TIP: If you want to connect the Quick Setup to the Internet asoutlined in Connecting the Quick Startup to the Internet on page11, obtain the CCU gateway IP address from your networkadministrator. You can then set the CCU Ethernet IP address toany IP address in the subnet.4. Confirm the CCU has been properly configured, as follows:Console> ipEthernet IP Address: 192.168.10.10Ethernet Net Mask : ffffff00Gateway IP Address: 192.168.10.1Radio IP Address: 10.0.0.1Radio Net Mask : fffffc00Console> radioRF Power: HIGHRadio Frequency: 9150Console>
2 Quick Startup8APCD-LM043-4.02.4 EUM Configuration1. Connect the PC to the console port of the EUM, as shown in Figure 2.Figure 2 Quick Startup — EUM Configuration2. Start the terminal emulation software.3. Type the following commands to configure the EUM:WaveRider Communications, Inc. LMS3000Password:Console> ip ethernet 10.0.0.2 22Console> ip gateway 10.0.0.1Console>Console> radio frequency 9150Console>Console> saveBasic Config savedPort Filter Config savedsntp cfg file savedConsole>4. Reboot the EUM for the settings to take effect.Console> resetrebooting EUM ...(... Power On Self Test ...)WaveRider Communications, Inc. LMS3000Password:CCU3000RS232 cableCCU set-upantennaCCU powersupplyEUM3000EUM AntennaEUM Power Supply1RadioLink
2QuickStartupAPCD-LM043-4.0 95. Confirm that the EUM has been properly configured, as follows:Console> ipEthernet/USB IP Address: 10.0.0.2Ethernet/USB Net Mask : fffffc00Gateway IP Address: 10.0.0.1Console> radioRF Power: HIGHRadio Frequency: 9150Console>2.5 Testing CCU–EUM CommunicationsOnce you have completed the configuration of the Quick Startup, you can testcommunications between the CCU and the EUM by pinging the CCU through the EUMconsole port.To Run a Ping Test Through the EUM Console Port1. Connect the PC to the EUM console port, as shown in Figure 3.Figure 3 Quick Startup — Ping Test (from console port)2. From the EUM, ping the CCU radio port (IP address 10.0.0.1), as follows. Press anykey to stop.console>console> ping 10.0.0.1Press any key to stopPING 10.0.0.1: 56 data bytes64 bytes from 10.0.0.1: icmp_seq=1. time=112. ms64 bytes from 10.0.0.1: icmp_seq=2. time=48. ms64 bytes from 10.0.0.1: icmp_seq=3. time=48. ms64 bytes from 10.0.0.1: icmp_seq=4. time=32. ms64 bytes from 10.0.0.1: icmp_seq=5. time=32. msCCU3000CCU set-upantennaCCU powersupplyEUM3000EUM AntennaEUM Power SupplyRadioLink1RS232 cable
2 Quick Startup10 APCD-LM043-4.064 bytes from 10.0.0.1: icmp_seq=6. time=16. ms64 bytes from 10.0.0.1: icmp_seq=7. time=64. ms64 bytes from 10.0.0.1: icmp_seq=8. time=64. ms----10.0.0.1 PING Statistics----8 packets transmitted, 8 packets received, 0% packet lossround-trip (ms) min/avg/max = 16/52/112console>This test verifies the radio link between the EUM and the CCU.To Run a Ping Test Through the EUM Ethernet Port1. Connect the PC to the EUM Ethernet port, as shown in Figure 4.Figure 4 Quick Startup — Ping Test (from EUM Ethernet port)2. Open the TCP/IP Properties window in the PC. If you are not sure how, consult youroperating system manual.3. Select Use the following IP address (or Specify an IP address—the exact wordingdepends on your operating system). Enter the following:• IP Address 10.0.1.2• Subnet Mask 255.255.252.0• Default Gateway10.0.0.14. From the PC, progressively ping the PC Ethernet port (10.0.1.2), the EUM (10.0.0.2),and the CCU radio (10.0.0.1) and Ethernet (192.168.10.10) ports.CCU3000Ethernet crossovercableCCU set-upantennaCCU powersupplyEUM3000EUM AntennaEUM Power Supply1RadioLink
2QuickStartupAPCD-LM043-4.0 112.6 Connecting the Quick Startup to the InternetOnce you have verified that the CCU and EUM are communicating properly, you may want toto connect the Quick Startup system to the Internet.To Connect to the Internet1. Connect the PC to the Ethernet port of the EUM as shown in Figure 5.Figure 5 Quick Startup — Connecting to the InternetTIP: If you want to connect the Quick Setup to the Internet, youmust obtain the CCU gateway IP address from your networkadministrator. The CCU Ethernet IP address can then be set toany IP address in the subnet.2. If you have not already configured the PC IP address as outlined in Testing CCU–EUM Communications on page 9, open the TCP/IP Properties window in the PC. Ifyou are not sure how, consult your operating system manual.3. Select Use the following IP address (or Specify an IP address; the exact wordingdepends on the operating system), and enter the following:• IP Address 10.0.1.2• Subnet Mask 255.255.252.0• Default Gateway10.0.0.1CCU3000Ethernet crossovercableCCU set-upantennaCCU powersupplyEUM3000EUM AntennaEUM Power SupplyGateway RouterInternet12RadioLink
2 Quick Startup12 APCD-LM043-4.04. Select Use the following DNS server address (the exact wording depends on youroperating system), and enter the IP address for the Preferred DNS Server, which isavailable from your Network Administrator.5. Connect the CCU Ethernet port to the appropriate network switch or hub, or directly tothe gateway router of your network.6. From the PC, you should now be able to open your browser and surf the Web.2.7 Adding more EUMs to the Quick StartupYou can add other EUMs and PCs to the Quick Startup system. At all times, try to maintain atleast 3 to 5 m (10 to 15 ft.) separation between the EUMs, and between the EUMs and theCCU.Other EUMs are added in the same way as the first EUM, using the same gateway IP address(10.0.0.1), subnet masks (255.255.252.0), and the following EUM and PC IP addresses:Table 2 Quick Startup — EUM AddressesEUMNumber EUM IP Address PC IP Address2 10.0.0.3 10.0.1.33 10.0.0.4 10.0.1.44 10.0.0.5 10.0.1.55 10.0.0.6 10.0.1.66 10.0.0.7 10.0.1.7
APCD-LM043-4.0 133Detailed DescriptionThis section describes the technologies and features used in the LMS4000 900 MHz RadioNetwork.3.1 LMS4000 OverviewFigure 6 is a high-level schematic of the LMS4000 system, showing the key systemcomponents and interfaces.As shown, each LMS4000 component is associated with one of three major system entities:• End-user Modem (EUM)• Communications Access Point (CAP)• Network Access Point (NAP)End-user Modem or Customer-premises EquipmentThe EUM equipment is installed at the end-user’s premises. It provides an interface to thecustomer’s computer or local area network on one side and wireless access to the LMS4000network on the other.Communications Access Point (CAP)The CAP is the collection and distribution point for data travelling to and from the EUMs. In theEUM-to-network direction, the CAP aggregates the data from the radio channels into a singledata stream, which is passed either directly or over a backhaul facility to the Network AccessPoint.In the Internet-to-EUM direction, the CAP receives data from the Network Access Point anddistributes this data to the appropriate radio channels for transmission to the EUMs over the900 MHz radio link.
3 Detailed Description14 APCD-LM043-4.0Network Access Point (NAP)The NAP provides the Internet connection point for one or more CAPs. An LMS4000 systemcan have more than one NAP. The number of NAPs depends on the geographical layout ofthe LMS4000 system and the location of available Internet access points. A single NAP canprovide Internet connection for one CAP, or several CAPs, each either colocated with the NAPor connected to the NAP over backhaul facilities.Figure 6 LMS4000 SystemThe following sections discuss the operation of the LMS4000 900 MHz Radio Network, ofwhich the CCU and EUM are the key components.3.2 Communications Access Point3.2.1 Key ComponentsThe following are key components of the Communication Access Point:• CCU•Cavityfilters• Lightning arrestorsNMS StationRouterInternetEUMBackhaul (NCL1170,for example)To OtherCAPsNetwork andEquipmentManagement10/100BaseT-SubscriberManagement-Billing Data- Authorization- RegistrationLayer 3-Switching- RoutingNAPCAPRouting to/fromInternetEUM- Authorization- RegistrationUPSRadio Control- Configuration- RedundancyCCUCCUBack-up CCUCCUAntennaAntennaAntennaCavity FiltersRFSMNot part ofLMS4000Switch10BaseTEnd-user PCEUM End-user PCEUM End-user PC
3 Detailed DescriptionAPCD-LM043-4.0 15• Transmission line• Antenna• Ethernet switchEach of the above components is discussed in the following sections.CCUThe CCU, shown in Figure 7, is the wireless access point for up to 300 end-user modems. Thefunctional blocks of the CCU are illustrated in Figure 8.Figure 7 CCUFigure 8 CCU Functional BlocksBasebandControllerRadioBasebandProcessorPowerAmplifier/Low-noiseAmplifierUp/DownConverterMediaAccessControllerEthernet Port10 BaseTConsole PortDB9, RS232CCU3000Antenna7.5 VDCRadioPowerBaseband
3 Detailed Description16 APCD-LM043-4.0The CCU routes IP packets received from the CCU radio port• to internal CCU processes,• through the CCU Ethernet port to any router on the Ethernet network, such as theNetwork Access Point, or• back out the radio port to other EUMs (EUM-to-EUM packets).The CCU routes IP packets that are received from the Network Access Point through theEthernet port• to internal CCU processes, or• through the radio port to the destination EUM.The CCU can be installed in a standalone configuration, or in a CCU shelf, as shown in Figure9, with other operating and backup CCUs. The CCU is powered by an AC/DC power supply,which can also stand alone or be installed in the CCU shelf. The CCU operates independentlyof other CCUs and can be swapped out without interrupting the operation of other CCUs.Figure 9 CCU ShelfUp to four CCUs can be installed at the same CAP, as follows:• Up to three operating CCUs, each with its own cavity filter, lightning protector,transmission line, and antenna.• One backup CCU, if CCU redundancy is provisioned. Since the backup CCU is“switched” into the RF circuit of the failed CCU, by the RFSM, it does not require itsown cavity filter, lightning protector, transmission line or antenna.The CCU comes with a setup antenna, which can be used during CCU configuration and test,prior to deployment.
3 Detailed DescriptionAPCD-LM043-4.0 17Cavity FiltersWaveRider recommends the use of cavity filters with all CCUs and is mandatory if colocatedwith other CCUs. Cavity filters help to isolate the CCU from inband interferers, such ascolocated CCUs or non-WaveRider ISM band equipment, as well as out-of-band interferers,such as cellular base stations and paging transmitters.Lightning ArrestorsSince the CCU antenna is mounted outdoors, lightning arrestors are required with all CCUinstallations. Lightning arrestors divert most of the energy from a lightning strike away from theRF transmission line and equipment, to a bonded ground point. The lightning arrestor isinstalled in series with the RF transmission line, as close as possible to the point where thetransmission line enters the building.Transmission LineA good quality RF transmission line should always be used to connect the CCU to theantenna. “Good quality RF transmission line” means one that is weather resistant and UV-protected, and that has low attenuation characteristics. All connectors in the transmission lineshould be wrapped to prevent water penetration. Connecting the CCU to the transmission linerequires RF jumper cables, available from WaveRider.AntennaEach active CCU requires its own antenna. Antennas can be omnidirectional or have asectored beam pattern (for example, 180, 120, or 90 degrees). The choice of antenna is bebased on site and RF engineering considerations, and FCC and Industry Canada guidelines,which are summarized in Appendix D on page 185.Ethernet SwitchAn Ethernet switch is required at the CAP if it is provisioned with more than one CCU, or tointerface with certain types of backhaul equipment.3.2.2 Optional ComponentsThe following Communications Access Point components are optional:•RFSM• RF Distribution PanelRFSMThe optional RFSM (RF Switch Matrix), shown in Figure 10, is required if CCU redundancy isprovisioned. The RFSM monitors the health of the operating CCUs. If a CCU fails, the RFSMswitches to a provisioned backup CCU, which is automatically programmed with the same
3 Detailed Description18 APCD-LM043-4.0settings as the failed CCU. In this way, the CAP can be provisioned for N+1 redundancy,meaning there is one backup CCU for ‘N’ operating CCUs, up to a maximum of N=3.Figure 10 RFSMRF Distribution PanelThe optional RF Distribution Panel provides• external interface to the antenna subsystem and site ground,• common surge protector mounting point for each external RF interface, and• common ground point for all CAP components.Other Optional CAP EquipmentDepending on your configuration and operational requirements, you may require othercomponents in your LMS4000 CAP, such as a UPS system, CCU Shelf, or free-standing19–inch rack.The CCU Shelf is a standard 19-inch mounting rack with an integrated power supply fan andcooling fans. It contains five CCU slots, for up to three operating CCUs, a backup CCU, andbackhaul CCU.These optional components can be ordered through WaveRider.3.3 Customer-premises Equipment3.3.1 Key ComponentsThe following Customer-premises Equipment components are key:•EUM• EUM antenna• Transmission line• Lightning arrestor
3 Detailed DescriptionAPCD-LM043-4.0 193.3.2 EUMThe EUM, shown in Figure 11, is a wireless modem that connects to the end-user’s computerthrough an Ethernet connection. The EUM, which acts as a network bridge, receives data fromthe CCU over the 900 MHz radio link, and then forwards this data to EUM internal processesor to the end-user’s computer through the Ethernet port. In the other direction, the EUMforwards data received from the end-user’s computer over the radio link to the CCU.Figure 11 EUMThe EUM functional blocks are the same as those of the CCU and are illustrated in Figure 8.
3 Detailed Description20 APCD-LM043-4.0EUM AntennaFor many EUM installations, you can use an indoor antenna. WaveRider recommends theWaveRider directional antenna with switched-beam diversity. This antenna, shown in Figure12, performs very well in cases where the radio path to the CCU is obstructed and/or wherethere is significant multipath. The diversity antenna accepts a DC signal on the antenna cablefrom the EUM, for beam pattern selection. The antenna comes with a mounting bracket and isdesigned to mount vertically on walls or windows (using drywall screws for wall mounting orsuction cups for window mounting), or horizontally (on desks, for example, using the suctioncups).Figure 12 WaveRider Indoor Directional Antenna with Switched-beam Diversity
3 Detailed DescriptionAPCD-LM043-4.0 21The WaveRider diversity antenna contains two vertical antenna elements mounted inside andon either side of the antenna housing. The phasing between these elements, which modifiesthe antenna pattern, is controlled by a DC voltage from the EUM. It produces two patterns, oneperpendicular to the face of the antenna, which has a gain of about 6 dBi, and the other, adual-beam pattern off both sides, offering about 3 dBi gain for each beam. These beampatterns are illustrated in Figure 13.Figure 13 WaveRider Switched-beam Diversity Antenna — Beam PatternsThe EUM samples the signal strength from both antenna patterns during the preamble ofevery received packet and automatically selects the best signal. When the EUM transmits, itsends on the antenna pattern that was last used to receive a signal. Since most of the trafficcomes from the CCU, the EUM samples the signal strength often—typically faster than onceevery 5 ms.The end user must position the switched-beam diversity antenna correctly to receive anadequate signal level. The Radio LED on the EUM, described in Indicators and Connectors onpage 74, can be used to help with the alignment. Since the switched-beam diversity antennahas a good front-to-back ratio, it can be positioned to suppress interference from otherwireless devices at the end-user’s premises.WaveRideralsooffersasimpledipoleantenna,whichcanoftenbeusedwherethepathtotheCCU is very short or relatively unobstructed; i.e., where there is a short line of sight path fromthe EUM to the CCU with no more than a wall or window obstructing the path.Other WaveRider-approved antennas can be used at EUM locations that require outdoorantennas. A professional installer is required to install outdoor EUM antennas to ensure theantenna system is properly installed with lightning protection and consistent with FCC andIndustry Canada guidelines, which are outlined in Appendix D on page 185.Transmission LineIf the WaveRider diversity or dipole antenna is used, it comes equipped with RF cables andconnectors. The connector is a proprietary WaveRider connector, which is mandated by theFCC requirement that the connectors used in ISM band products that are not professionallyinstalled must be unique, or at least not readily available. If an alternate indoor or outdoorantenna is used, the installer must obtain an RF jumper cable to connect the antenna cable tothe EUM. These jumper cables can be obtained from WaveRider.Beam Pattern A Beam Pattern B
3 Detailed Description22 APCD-LM043-4.0Lightning ArrestorA lightning arrestor is required at the EUM only if an outdoor antenna is used.3.4 Basic Operation3.4.1 LMS4000 Transmission ConceptConceptually, the LMS4000 900 MHz Radio Network can be thought of as an Ethernet switchwith a built-in router, as shown in Figure 14.Figure 14 LMS4000 Transmission ConceptIn the above diagram, the “switch” consists of the CCU and EUM physical, MAC, and IPbridging layers, and the 900 MHz link between them. IP packets originating from any host inthe radio subnet (EUM or PC, for example), which are destined for a host that is also in theradio subnet, are “switched” by the CCU directly to that host. IP packets originating from anyhost in the radio subnet, which are destined for a host outside the radio subnet, are “switched”to the CCU router for routing to the destination host.IP packets coming into the CCU Ethernet port, which are destined to a host in the radiosubnet, are routed to the “switch” and “switched” to the host.3.4.2 CCU and EUM ConfigurationWhen CCUs and EUMs are shipped from the factory, they are pre-programmed with a set offactory default settings. Some of these default settings must be modified before the systemcan pass traffic. These basic settings are listed Table 3 and Table 4. Once your system iscarrying traffic, you can configure the more advanced CCU and EUM features and functions,which are also listed in these tables.EUM HostPCEUM HostEnd-userLANPCEUM HostCCU RouterApplicationCCU Ethernet port"Switch"CCU
3 Detailed DescriptionAPCD-LM043-4.0 23Table 3 CCU ConfigurationTable 4 EUM ConfigurationBasic CCU Settings Advanced CCU SettingsBefore the system can pass traffic, input ormodify the following CCU parameters:• CCU Ethernet IP address• CCU radio IP address• Gateway router IP address• Radio frequencyFor instructions on how to set theseparameters, read the following sections:•Quick Startup on page 5•IP Network Planning on page 53•Radio Network Planning on page 59Once the system is passing traffic, you canstart to configure and fine tune the followingCCU features and functions:• Grade of Service• DHCP relay•Portfiltering• SNTP time clock• SNMP communitiesYou can find a technical description of thesefeatures in CCU–EUM Interface — DetailedTechnical Description on page 28. You canfind procedures for configuring thesefeatures in Configuring the CCU on page83.Basic EUM Settings Advanced EUM SettingsBefore the system can is implemented, inputor modify the following EUM parameters:• EUM Ethernet IP address• Gateway (CCU Radio) IP address• Radio frequencyFor instructions on how to set theseparameters, read the following section:•Configuring the EUM on page 97Note: Since the EUM is a wireless bridge, itpasses data without having a unit orgateway IP address assigned. However, tosupport system management (SNMP, forexample) of an EUM, a unique IP addressmust be assigned. The EUMs all ship withthe same default unit and gateway IPaddresses, so if these are not changed youwill experience network IP conflicts.Once the system is passing traffic, you canstart to configure and fine tune the followingEUM features and functions:•Portfiltering• SNMP communities•CustomerlistFor instructions on how to set theseparameters, read the following section:•Configuring the EUM on page 97
3 Detailed Description24 APCD-LM043-4.0Table 5 End-user PC Configuration3.4.3 LMS4000 Protocol StacksThe LMS4000 900 MHz Radio Network is an IP (layer 3) network that provides connectivityfrom the end-user’s computer to the Internet.Figure 15 shows the protocol stacks through which an IP packet traverses as it travelsbetween the end-user’s computer, shown on the left, and the Internet, shown on the right.Figure 15 LMS4000 Protocol Stacks3.4.4 Basic Data TransmissionThis section describes how an EUM registers, and once it is registered, how data traffic flowsfrom the Internet to the end-user PC and from the end-user PC to the Internet. The process inboth directions involves CCU and EUM data tables, which are described in more detail inAppendix E on page 183.Basic End-user PC Settings Advanced End-user PC SettingsIn addition to the above CCU and EUMsettings, the end-user’s PC must beassigned an IP address and subnet, and astatic gateway address. These IP addressescan be statically assigned to the PC, asdescribed in Configuring EUM IPParameters on page 99, or dynamicallyassigned from a DHCP server byconfiguring the CCU for DHCP Relay,described in DHCP Relay on page 48, andConfiguring DHCP Relay on page 88.DHCP10BaseTEthernet MACIPTCP/UDPApplications(email,browser, ftp,telnet, ICQ,VoIP, ...)12345-7OSILayer End-User'sComputer10BaseTEthernetMACIP Port FilteringEUM3000PMACDSSSRadio 10BaseTEthernetMACIP Port FilteringCCU3000DSSSRadioBackhaul10BaseTEthernetMACIP RoutingNAP Router10BaseTEthernetMACInternetConnectionTCP/UDPAuth/RegPMACAuth/RegIP Bridging IP RoutingTCP/UDP TCP/UDPEUM Application CCU Application
3 Detailed DescriptionAPCD-LM043-4.0 25EUM RegistrationEUMs need to register with the CCU before user traffic can pass between the LMS4000 900MHz Radio Network and the end user. The heart of EUM registration is the AuthorizationTable, discussed in Authorization Table (CCU only) on page 189.The EUM registration process is as follows:1. The system operator enters the EUM’s grade of service in the CCU AuthorizationTable, described in Authorization Table (CCU only) on page 189.2. On power up, the EUM sends a registration_request to the CCU.3. The CCU obtains the EUM’s grade of service from the Authorization Table. If the EUMgrade of service is DENIED, the CCU sends a de-registration_response to the EUMand data communications are enabled. The EUM continues to sendregistration_requests to the CCU approximately every 10 minutes.4. If the EUM grade of service is not DENIED, the CCU sends a registration_response tothe EUM, and data communications are enabled. At this point, the CCU adds the EUMto the Registration Table, described in Registration Table (CCU only) on page 190.5. If at some later time, the EUM does not respond to messages from the CCU, the CCUsends a de-registration_request to the EUM and removes the EUM from theRegistration Table. If there has been no traffic to or from the EUM for more than 12hours, the CCU removes the EUM from the Registration Table without sending it a de-registration_request.
3 Detailed Description26 APCD-LM043-4.0Addressing of IP PacketsFigure 16 shows how the source and destination MAC and IP addresses are sent in IPpackets travelling between the end-user’s PC and the Internet network servers.Figure 16 Addressing of IP PacketsAs shown in Figure 16, if NAT is not enabled in the NAP Router, then the source anddestination IP addresses are maintained throughout the route between the end-user PC andnetwork servers. The source and destination MAC addresses, however, change whenever thepacket is passed through a router. This change of MAC addresses also takes place in theCCU router application.Internet to End-user Computer Data Transmission1. Internet traffic comes through the gateway router, and possibly through backhaul andEthernet switches, to the CCU Ethernet port.2. The CCU receives an IP packet through the CCU Ethernet port and checks the TCPor UDP port number. If the port number appears in the CCU Port Filter Table,described in Port Filter Table (CCU and EUM) on page 183, the packet is discarded.3. The CCU reads the destination IP address. If the destination IP address is the sameas either the CCU Radio or Ethernet IP address, the packet is sent to the CCUapplication.4. The CCU checks the Routing Table, described in Routing Table (CCU and EUM) onpage 184. If the route to the destination is through the CCU Ethernet port, then thepacket is discarded, since it is not destined for a host in the CCU’s radio subnet.Network ServerNAP Router(no NAT)EUM CCU BackhaulSwitchEnd-user PCInternet Router(several)Network Server IP AddressEnd-user PC IP AddressEnd-user PC MACAddressCCU Radio MACAddressDestination IPAddressSource IPAddressDestinationMAC AddressSource MACAddressAABBDestination IPAddressSource IPAddressDestinationMAC AddressSource MACAddressDestination IPAddressSource IPAddressDestinationMAC AddressSource MACAddressDestination IPAddressSource IPAddressDestinationMAC AddressSource MACAddressNAP Router MACAAddressCCU Ethernet MAC AddressInternet RouterMACAAddressNetworkServer MACAddressNAP RouterMACBAddressInternetRouter MACBAddressEnd-user PC IP AddressNetwork Server IP AddressCCU Radio MACAddressEnd-user PC MACAddress CCU Ethernet MAC AddressNAP Router MACAAddressNAP RouterMACBAddressInternetRouter MACBAddressInternet RouterMACAAddressNetworkServer MACAddressEnd-user PC to Network ServerNetwork Server to End-user PCBackhaul
3 Detailed DescriptionAPCD-LM043-4.0 275. If the route to the destination is through the CCU Radio Port, then the CCU obtains thedestination Ethernet MAC address from the ARP Table, described in ARP Table (CCUand EUM) on page 187. If the destination is not listed in the ARP Table, the CCUobtains its MAC address by issuing an ARP query. Once it gets the MAC address, itadds the entry to the ARP Table.6. Using the destination Ethernet MAC address, the CCU obtains the EUM ID from theAddress Translation Table, described in Address Translation Table (CCU only) onpage 188.7. Using the EUM ID, the CCU obtains the EUM grade of service from the RegistrationTable, described in Registration Table (CCU only) on page 190.8. The IP packet is then transmitted through the Polling MAC and radio interface to theEUM.9. The EUM receives the packet through the EUM radio port and checks the portnumber. If the port number appears in the EUM Port Filter Table, the packet isdiscarded.10. If the port number does not appear in the EUM Port Filter Table, the EUM checks thedestination MAC address. If the MAC address is the EUM MAC address, then thepacket is forwarded to the EUM application; otherwise, the IP packet is sent outthrough the Ethernet port to the end user’s equipment.End-user Computer to Internet Data Transmission1. The EUM receives IP packets from the end-user’s equipment through the Ethernetport.2. The EUM checks the port number. If the port is listed in the EUM Port Filter Table, thepacket is discarded.3. If it is not already in the list, the EUM adds the source Ethernet address to theCustomer Table, described in Customer Table (EUM only) on page 192. The EUMdetermines whether or not the source is entitled to air access, based on the CustomerTable.4. If the source is not entitled to air access, the packet is discarded.5. The EUM checks the destination MAC address. If the destination MAC addressappears in the Customer Table, meaning the destination is on the Ethernet side, thepacket is discarded.6. If the destination MAC address is the same as the EUM MAC address, then thepacket is forwarded to the EUM application; otherwise, it is forwarded through thepolling MAC and radio link to the CCU.7. The CCU receives the packet through the CCU radio port. The CCU either updates oradds the Ethernet address to the Address Table.8. The CCU checks the port number. If the port number appears in the CCU Port FilterTable, the packet is discarded.9. The CCU checks the destination MAC address. If the destination MAC address is notin the Address Table, the packet is sent to the CCU router application.
3 Detailed Description28 APCD-LM043-4.010. If the IP address is the same as either the CCU radio or Ethernet IP address, thepacket is forwarded to the CCU application; otherwise, the CCU gets the appropriategateway IP address from the Routing Table and the gateway MAC address from theARP Table, and then sends the packet to the gateway (most likely the NAP router)through the Ethernet port.NOTE: The CCU and EUM pass only IP or ARP packets. All otherpackets are discarded so non-IP packets, such as IPX/SPX, arenot passed over the radio link.3.5 CCU–EUM Interface — Detailed Technical DescriptionThis section provides a detailed description of the physical and MAC layers of the interfacebetween the CCU and EUM, depicted in Figure 15 on page 24.3.5.1 Physical Layer (DSSS Radio)Frequency BandThe LMS4000 900 MHz Radio Network operates in the 902-928 MHz Industry, Scientific, andMedical (ISM) frequency band.Channel BandwidthThe channel bandwidth is 6 MHz. This channel bandwidth is used to determine the lowest andhighest allowable channel in the band. As illustrated in Figure 17, the center frequency of thelowest and highest channels have to be set such that the signal power that falls in the bandsadjacent to the ISM band does not exceed FCC and Industry Canada limits.Figure 17 Determination of Lowest and Highest Channel902 - 928 MHz ISM BandFCC limit foremissions inadjacent bandLowestChannel905 MHzHighestChannel925 MHz
3 Detailed DescriptionAPCD-LM043-4.0 29The channel bandwidth also determines the minimum adjacent channel spacing for colocatedCCUs.ChannelsThere are 101 channels in the band, set in 0.2 MHz increments:Table 6 LMS4000 900MHz Radio Network ChannelizationModulationThe CCU-EUM radio channel is based on DSSS (Direct-Sequence Spread Spectrum) signals,modulated with CCK and Barker-coded BPSK and QPSK, similar to that defined in IEEE802.11 for the 2.4 GHz ISM band.DSSS offers the following advantages:•Reduced power spectral density: Spreading over a wider bandwidth reduces thespectral density (power per Hz of bandwidth) of the transmitted signal, allowingsimultaneous operation of many spread-spectrum systems in the same frequencyband and geographic area. The reduced spectral density also allows you to meet theregulatory emissions requirements in the ISM frequency bands.•Transmission security: It is technologically more difficult to recover (or jam, in thecase of military communications systems) spread-spectrum signals than it is torecover conventional narrowband signals.Channel Center FrequencyLowest channel 905.0 MHz... 905.2 MHz... 905.4 MHz... ...... 924.8 MHzHighest channel 925.0 MHz
3 Detailed Description30 APCD-LM043-4.0•Interference suppression: The same mechanism that de-spreads the desired signalin the receiver, spreads undesired signals, which then appear to the receiver as lowerlevels of RF noise. This effect is illustrated in Figure 18.Figure 18 Effect of DespreadingData RateThe raw channel bit rate is 2.75 Mbps. The maximum data rate presented to the MAC layer is2.4 Mbps, which translates to a peak FTP rate of about 2 Mbps.Colocated ChannelsA maximum of four orthogonal (nonoverlapping) channels can be provisioned at a single CAPbut WaveRider recommends a maximum of three. To ensure adequate isolation betweenchannels, a minimum co-channel spacing of 6.6 MHz is recommended, as is the use ofchannel filters and a properly engineered antenna system. A possible frequency set for athree-channel CAP is• 905.0 MHz• 915.0 MHz• 925.0 MHzA separate CCU, channel filter, transmission line, lightning protector, and antenna arerequired for each of the orthogonal channels.DuplexingThe radio channel uses Time Division Duplexing (TDD), which means that the CCU or EUM isin either receive or transmit mode, but does not transmit and receive at the same time.Transmit PowerThe maximum transmit power (HIGH power setting) of the CCU and EUM is +26 dBm,measured at the unit’s RF connector. It does not include gains and losses from antennas,transmission lines, and lightning arrestors, all of which affect the ERP (Effective RadiatedPower) from the CAP or customer’s premise. Refer to Appendix D on page 185 for adiscussion of related FCC and Industry Canada guidelines.Before De-spreadingInterfererDesiredSignalAfter De-spreadingDesired SignalIntefererBecomes
3 Detailed DescriptionAPCD-LM043-4.0 31The CCU and EUM transmit power can each be set to +15 dBm (LOW power setting) toaddress special or regional applications of the LMS4000,or for bench testing.Receive SensitivityThe receive sensitivity (received signal required to attain a raw data BER of 10-5 or betterusing 1000-byte packets) of the CCU and EUM is < -86 dBm, measured at the unit’s RFconnector.Antenna ConnectorThe RF connector used on the CCU and EUM is a WaveRider-proprietary connector. As notedabove, the use of a proprietary antenna connector is mandated by FCC requirements for aunique RF connector on ISM products.Antenna Control (EUM)A DC voltage (5 VDC or 7.5 VDC) is applied to the EUM RF connector for powering andcontrolling the WaveRider diversity antenna. One beam pattern is selected if the voltage is 5VDC. A second beam pattern is selected if the voltage is 7.5 VDC.CAUTION: The EUM sends DC power and control voltagesthrough the RF connector to the switched-beam diversityantenna. You must use WaveRider-approved indoor or outdoorantennas; otherwise, you could inadvertently short out the DCvoltage and damage the EUM. Contact WaveRider TechnicalSupport for a list of approved antennas.Propagation PathCCU and EUM radios and antennas provide the basis for excellent radio propagation in bothline of sight (LOS) and non line of sight (NLOS) EUM installations. Radio propagation in the902 – 928 MHz ISM band is superior to propagation in higher ISM bands for several reasons:• Lower free space loss• Lower cable loss• Lower vegetation loss• Better wall and glass penetration• More signal recovery from diffraction• More signal recovery from reflectionsRadio line of sight exists when there is a clear optical path between the CCU and EUMantennas, as well as adequate clearance of the path over terrain, foliage, and buildings. Thisclearance requirement is called the Fresnel clearance. The required clearance varies alongthe path and reaches a maximum at the path midpoint. If you have a path with Fresnelclearance, the loss between the antennas is generally equivalent to free-space loss and canbe readily calculated.
3 Detailed Description32 APCD-LM043-4.0NLOS exists when the path between the CCU and EUM is obstructed, or partially obstructed,by terrain, buildings, or foliage. NLOS is illustrated in Figure 19. Since radio waves reflect,refract, and diffract, a non line of sight path does not necessarily mean the EUM-CCU radiolink does not have enough signal margin. It simply means that the path loss is be greater thanthe LOS path loss. Within the engineered NLOS coverage range of the CCU, the NLOS path,using an indoor antenna, is acceptable for most EUM installations.Figure 19 Typical NLOS PathIt is difficult to accurately predict NLOS path loss; however, a lot of field data has beencollected and factored into commercially available path-prediction software.LMS4000 900 MHz radio coverage prediction depends on the following:• CCU radio output power, transmission-line losses, and antenna height and gain• Length of the path between the CCU and EUM• Height of terrain, foliage, and buildings along the path between the CCU and EUM,which determines the percentage of the path that is obstructed.• EUM antenna height and gain, transmission-line losses, and receiver sensitivity• If the EUM antenna is installed indoors, location of the EUM antenna within the end-user premises, and the premises building type and wall constructionThe EUM has been designed to work with the WaveRider indoor switched-beam diversityantenna. Where greater range is required, outdoor EUM antennas are also available.Generally, the higher the CCU antenna, the better the range, especially for LOS performance.Ideally, the CCU antenna should be installed well above the average height of trees in thevicinity of the CCU.
3 Detailed DescriptionAPCD-LM043-4.0 33To illustrate the impact that proper siting of the CCU has on the LM4000 radio coverage,consider the three cases shown in Figure 20.Figure 20 Examples of Radio Paths• Case 1 is a clear, unobstructed path between the CCU and the EUM, with full Fresnelclearance.• Case 2 is a clear, unobstructed path, except for the last few hundred meters, which isobstructed by foliage and terrain.• Case 3 is obstructed in the vicinity of the CCU for the first few hundred meters, andthen clear and unobstructed to the EUM.EUM-1EUM-2CCUEUM-3Case 1Unobstructed PathCase 2Path Obstructed inVicinity of EUMCase 3Path Obstructed inVicinity of CCU
3 Detailed Description34 APCD-LM043-4.0You can predict the amount of path loss for each of these cases, as illustrated in Figure 21.Figure 21 Path Loss CalculationAs shown in Figure 21, the path loss for each case is quite different:•Case 1 (Unobstructed Path): Over the length of the path, the signal drops as 1/R2,where R is the distance from the CCU. The range, Rcase1, is determined by thedistance at which the signal reaches threshold plus the desired fade margin.•Case 2 (Path Obstructed in Vicinity of EUM): From the CCU, the signal initiallydrops as 1/R2until it reaches the obstructions in the vicinity of the EUM. Throughthese obstructions, the signal drops more steeply than it does in the unobstructedcase, more like 1/R4. Once again, the range, Rcase2, is determined by the distance atwhich the signal reaches threshold plus the desired fade margin. As shown above,Rcase2 <Rcase1, which intuitively makes sense. If the path to the EUM is unobstructed,you would expect to be able to serve EUMs that are farther from the CCU, and toprovide better fade margin to those that are in closer.•Case 3 (Path Obstructed in Vicinity of CCU): From the CCU, the signal initiallydrops as 1/R4until it leaves the obstructing clutter and terrain in the vicinity of theCCU. Once the signal leaves these obstructions, it drops as 1/R2since the remainderof the path is clear. Once again, the range Rcase3, is determined by the distance atwhich the signal reaches threshold plus the desired fade margin. As shown above,Rcase3 <Rcase1. Although it shows Rcase3 <Rcase2, this may or may not always be thecase; however, it is always true that the margin is greater for Case 2 than Case 3, inthe coverage area indicated by the shading in Figure 21. In this area, the probability ofsuccessful indoor installs is likewise higher for Case 2 than Case 3.RangeCase 1Unobstructed PathFree Space LossCase 2Path Obstructedin Vicinity of EUMCase 3Path Obstructedin Vicinity of CCUTx O/PRx ThresholdFade MarginRcase 3 Rcase 2 Rcase 1Probability of successul indoor installation isgreater for Case 2 than for Case 3, in thisregion
3 Detailed DescriptionAPCD-LM043-4.0 35The following key conclusions that can be drawn from the simple example and analysis shownabove:• Coverage range and fade margins are maximum when paths are clear andunobstructed.• Coverage range and fade margins are reduced for specific EUMs if there isobstructing clutter and terrain in the vicinity of these specific EUMs.• Coverage range and fade margins are reduced for all EUMs if there is obstructingclutter or terrain in the vicinity of the CCU. For this reason, it is critical that the CCUlocation be chosen and the antenna height be sufficient to eliminate local obstructionsfor all possible radio links from the CCU. By local, it is recommended that the radiopaths be obstruction-free between the CCU and halfway to the limit of the coveragerange.Table 7 shows the typical radio coverage (distance from the CCU) that the LMS4000 900 MHzRadio Networks can achieve. Table 7 should be used as a planning guideline only, due to thedifficulty of accurately predicting radio coverage.Table 7 Typical Radio CoverageThe following assumptions have been made in calculating the above ranges:• For practical purposes, assume that typically 80% of the subscribers in the predictedcoverage area will be able to receive service. Higher coverage is possible but oftenrequires more extensive RF engineering.• LOS (line of sight) means optical view and radio Fresnel clearance between the EUMpremise and the CCU antenna.• Typical CCU antenna height of 130 ft. (40 m), at least 10 ft. (3 m) above the trees.• Typical EUM antenna height (for outdoor antennas) of at least 13 ft. (4 m).• The CCU EIRP has been maximized to +36 dBm in all cases. Refer to Appendix D onpage 181 for further guidelines.• The EUM outdoor antenna (Yagi antenna, for example) has a gain of 9 dBi, and theindoor antenna (WaveRider switched-beam diversity antenna) has a gain of 6.6 dBi.• Coverage with the WaveRider indoor switched-beam diversity antenna depends onthe composition of the exterior walls and structure of the end-user’s premises. Forbest results, the EUM antenna should be installed behind a window.Actual results vary significantly due to local conditions. Coverage-area prediction that takesinto account local terrain and clutter factors provides a better estimate of coverage.EUM Installation Typical LOS Range Typical NLOS RangeIndoor Antenna(path to CCU is through awindow) 3mi(5km) 1mi(1.6km)Outdoor Antenna 5 mi (8 km) 2 mi (3.2 km)
3 Detailed Description36 APCD-LM043-4.03.5.2 MAC Layer (Polling MAC)EUM StatesThe LMS4000 900 MHz Radio Network data transmission is based on a WaveRider’spatented polling algorithm, which takes advantage of patterns found in typical Internet usage.Based on the EUM’s subscribed grade of service and current traffic level, the Polling MACcontinuously adjusts the rate at which the EUM is polled. This process is illustrated in the EUMState Diagram in Figure 22.Figure 22 EUM State DiagramWhen an EUM first powers up, it is in an unregistered state.In the unregistered state, the EUM is not being polled and is therefore not passing traffic. Asoutlined in EUM Registration on page 25, an unregistered EUM sends a registration_requestto the CCU. If the EUM is authorized in the CCU Authorization Table, it becomes registered/disassociated.In the registered/disassociated state, the EUM is still not being polled. But if the EUM hastraffic to send, it tries to associate with the CCU through the random access channel. TheEUM may also become associated iftheCCUhasapayloadtosendtotheEUM.Onceassociated, the state of the EUM changes to active/associated.In the active/associated state, the EUM is polled often, at a rate consistent with its subscribedgrade of service. If there is no traffic to or from an active/associated EUM for a defined interval(typically set around 0.5 seconds), the state of the EUM changes to inactive/associated.An inactive/associated EUM is polled less frequently than an active/associated EUM. If trafficis resumed, the state of the EUM changes back to active/associated.Ifthereisnotrafficforalonger defined interval (typically set around 2 seconds), the state of the EUM changes back toregistered/associated.inactive/associated active/associatedunregistered registered/disassociatedRandom access forEUM or payload forEUM arrives at CCUTraffic in eitherdirectionNo traffic for ~0.5sEUM isnot polledEUM ispolledoftenEUM ispolled lessoftenNotrafficfor~2sPowerupEUM isnot polledregRequest/regResponseFrom any state:- deregRequest- extended period with no traffic (~12h)* Parameters are derived from the GOSconfiguration file, and vary with EUMgrade of service.
3 Detailed DescriptionAPCD-LM043-4.0 37If an EUM is issued a deregistration request, for any reason, or if it has no traffic for anextended period of time, 12 hours or so, its state changes back to unregistered.Basic Operation of the Polling MACThe Media Access Control (MAC) layer determines which unit (CCU or EUM) gets to transmitand when it gets to transmit. Through the MAC layer, the CCU determines which associatedEUM gets to transmit next and indicates to the EUM that it can transmit by polling it. Thefrequency with which an EUM is polled is based on its assigned Grade of Service (GOS). TheCCU transmits a directed poll to the EUM, which immediately transmits a response to theCCU. After the response is received from the EUM, the CCU transmits the next poll. In thisway, the inbound (EUM-to-CCU) and outbound (CCU-to-EUM) channels are maintainedcollision free.If the CCU has data to send to an EUM, then that data is sent with the directed poll. If the EUMhas data to send to the CCU, then that data is sent with the EUM response to the poll.EUMs that are not authorized are not polled.To optimize polling efficiency, EUMs that no longer have traffic to send are not polled. EUMsthat are not being polled can submit a request to be polled by responding to a special randomaccess poll transmitted regularly by the CCU. Collisions may sometimes occur on this randomaccess channel; however, since only a small number of users are vying for service through therandom access channel at any one time, the effect on channel performance is negligible.Recovery from these collisions is made possible by random back-off and retry.Once again, if the EUM requesting service through the random access channel has data tosend to the CCU, it will be included with the request message. If the CCU has outstandingbroadcast messages to send, they will be sent to all EUMs with the random access poll.An automatic repeat request (ARQ) scheme, using acknowledgements and retransmissions torecover from message losses due to collisions or radio link errors, provides reliable transport.Each transmitted data payload is numbered in the packet header. Each packet header alsocontains an acknowledgement for the last correctly received payload, by number. If a CCU orEUM does not receive an acknowledgement for a payload that it has transmitted, it retransmitsthat payload with the following poll of, or response from, that EUM. A payload is transmitted amaximum of four times, after which it is discarded. Note that contrary to the 802.11b system,MAC-layer acknowledgements are not transmitted as separate packets, reducing overhead by33%, on average.Network UsageThe design of the Polling MAC has been optimized to allow maximized user capacity fortypical patterns found in Internet usage, which include browsing the world wide web,accessing email, transferring files, and streaming audio and video. The common characteristicof these uses is that they are bursty—data is transferred in bursts, with time in between thebursts when no data is transferred. As a result, not all users will be transferring data at thesame time. In fact, the number of users that are actually transferring data at any one time isgenerally much smaller than the number sitting in front of their computers which, in turn, ismuch smaller than the total number of end users. As a result, many users can share the radiolink and, for the short time they need it, use a significant portion of the link bandwidth. In otherwords, many users share the limited bandwidth of the channel, yet each perceives that they
3 Detailed Description38 APCD-LM043-4.0have most of the channel bandwidth to themselves. This over-subscription model is the basisof Ethernet, DOCSIS cable networks, 802.11 radio networks, Bluetooth, and on a larger scale,the public switched telephone network.If a significant portion of the network traffic does not meet this typical bursty model, the PollingMAC adjusts to maximize the user capacity. In this case, the maximum number of users is lessthan the case where most of the traffic is bursty. As described in Specialized Applications onpage 155, the Polling MAC can also be optimized to support LMS4000 applications, whichhave been designed, for example, to cost-effectively extend the coverage range.AssociationThe Polling MAC has been designed to take advantage of the bursty, intermittent nature ofInternet usage through the concept of association. When users are transferring bursts of data,their EUMs are associated with the CCU, and they are allocated a portion of the pollingsequence. In between bursts, the EUM is disassociated, freeing that part of the pollingsequence for other users. The determination of when to disassociate an EUM is based on thetime that has expired since any data was transferred to or from that EUM. As more and moreEUMs become associated, the bandwidth allocated to each EUM gets smaller and smaller,consistent with the GOS constraints discussed below.When an EUM is not associated but has data to send, it uses the random access mechanismto send the first packet. On receiving this first packet, the CCU considers the EUM associatedand begins to poll it. The EUM remains associated as long as traffic continues to flow, but aftera short period of inactivity it is directed to disassociate.If the CCU has data to send to a disassociated EUM, the status of the EUM changes toassociated, and the data is sent to the EUM the first time it is polled.The maximum number of EUMs that can be associated at any one instant of time is 75. AnyEUMs trying to associate beyond this limit are denied access until the number of associatedEUMs falls below the limit.
3 Detailed DescriptionAPCD-LM043-4.0 39Grade of Service (GOS)In the Polling MAC, the grade of service (GOS) determines how often, and when, anassociated EUM is polled. Since the EUM can only send one packet each time it is polled, thedata rate is related to the polling rate.Operational objectives that are factored into the determination of the basic polling rate includethe following:• Maximize overall user capacity and minimize the overhead related to empty polls.• Accommodate different types of data; for example, short, bursty data, such as emailand browsing, and large file transfers.• Support differentiation of user classes in terms of committed information andmaximum burst rate throughput levels.• Control packet latency to support interactive services such as VoIP and chat.• Support both symmetrical and asymmetrical data applications.• Control unauthorized web hosting or gaming applications.• Support multi-user network applications at a single EUMTo accommodate these often-conflicting operational objectives, WaveRider has designed apatented Polling MAC layer that incorporates an integrated GOS management algorithm.Within this algorithm, a total of 11 GOS parameters (GOS parameter set) are controlled toachieve specific performance objectives.To maximize the performance of the GOS algorithm, and therefore Polling MAC, control of thefollowing factors is key:• Delay between packets transmitted to (or from) an EUM• Relative weighting of different GOS classes• Determination of when an EUM is active or inactive.Manipulating these factors through the GOS parameter set can provide• differentiated levels of service to end-users, which are defined in terms of averagecommitted and maximum burst throughput rates, and• other special service classes.The polling algorithm controls packet rates and timing, which in turn provide varying datathroughput in kbps, depending on the packet sizes for a given application.GOS classes are defined based on particular combinations of the GOS parameter set. Thesystem operator assigns a GOS class to each EUM, and the CCU gets the EUM's pollingparameters from that class.
3 Detailed Description40 APCD-LM043-4.0In determining the order in which to poll the EUMs, the CCU tries to• ensure consecutive polls of an EUM occur within the range defined by the EUM'sgrade of service,• maintain the average time between polls defined by the grade of service, and• divide the total number of polls among EUMs consistent with the grades of service ofthe EUMs being polled.SinceitisinefficienttopollanEUMifthereisnodatatosendeitherway,anEUMcanbepolled less often if it has not recently transmitted or received traffic. The GOS parameter setessentially provides for independent control of the polling characteristics for both active EUMs(those that have recently had traffic) and for inactive EUMs (those that have recently had notraffic), where “recently” is defined by the GOS parameter set.In addition to efficiently managing the usage of the radio link and providing differentiatedservice capabilities, the polling MAC inherently smooths the upstream (EUM-to-CCU) packetarrival times. It also has a smoothing effect on the downstream traffic arrivals, which positivelyimpacts network performance by reducing• surges in data traffic,• transients in queue occupancy, and• packet discards.GOS Configuration FilesEach GOS is defined by configuration files that are stored in the CCU. The CCU can maintainup to five GOS configuration files, consisting of• up to four assignable GOS configuration files, and• one GOS configuration file for broadcast messages.The operator assigns each EUM to one of the four assignable GOS configuration files, whichhave the fixed labels of Gold, Silver, Bronze, and Best Effort. Although the labels are fixed, theactual service level is determined by the configuration file that is associated with label.Although only four assignable GOS configuration files can exist simultaneously in the CCU,each of these files can be readily changed by FTPing a new configuration file to the CCU, toreplace the existing one. This change can be done while the CCU is active and takes effectimmediately.As specific requirements are identified, WaveRider creates and makes available sets ofpredefined configuration files. To illustrate the operation of the GOS configuration files, theperformance of the factory default GOS service levels is summarized in Table 8. This defaultGOS configuration file is tailored for networks consisting of both residential and business-classusers.
3 Detailed DescriptionAPCD-LM043-4.0 41Table 8 Factory Default GOS Configuration FileNOTE: While recognizing that the performance of data transmissionthrough packet radio networks is randomly dependent on manyvariables, typical FTP rates based on empirical data are includedin the table to demonstrate the performance that the operatormight expect on single, large FTP transfers using maximum-sizedpackets.There are several important observations that can be made about the above service-classdescriptions:• All of the default service classes impose a limit on the maximum polling rate.• The Silver and Gold service classes have a lower bound on the polling rate (12 and 22polls per second [pps] respectively). The Polling MAC treats this limit as a minimumcommitted level, which is subject to overall radio link capacity.• In determining the order and frequency with which to poll EUMs, the CCU first tries toensure all associated EUMsarepollednomorefrequentlythanthemaximumserviceclass polling rate, and no less frequently than the minimum service class polling rate.• As the system usage increases, the end-user throughput in all classes decreasesfrom the maximum. Bronze users see the largest reduction, then Gold users, and thenBest Effort users. When all users have been reduced to 256 kbps (the minimumthreshold for Gold), the next reduction will be shared by the Best Effort, Bronze, andSilver class users (Gold will not be reduced further), until the minimum threshold forSilver is reached. After this, if further reductions are required, this reduction would beshared equally between the Best Effort and Bronze users.In practice, the bursty nature of Internet usage is such that this methodical reduction inthroughput is not apparent to the end-user, and these variations in service level tendto be instantaneous and transitory. Overall, end-users tend to see a relatively highaverage throughput consistent with their assigned GOS class, as is shown later indetailed simulation results based on real user data.ServiceClass Polling Rate (polls/second) FTP Rate(see note) OperatorAssignedBestEffort 1-34 0-384kbps YesBronze 1 - 90 0 - 1024 kbps YesSilver 12 - 22 128 - 256 kbps YesGold 22 - 46 256 - 512 kbps YesBroadcast Varies with channel load,from 16 to 935 Not applicable NoDenied 0 0 Yes
3 Detailed Description42 APCD-LM043-4.0Transmit Queue LimitsCCU transmit buffer space is a limited resource shared between the EUMs. If more traffic isreceived at the CCU for transmission to an EUM than can actually be transmitted to it, thatEUM might eventually use up all available CCU buffer space, effectively starving all otherusers. Therefore, the number of packets in each EUM's transmit queue is intentionally limited.Packets arriving beyond this limit are discarded, resulting in retransmission of TCP/IP packetsby the host computer and TCP/IP adjusts by slowing down. The EUM transmit queue lengthlimit, which is never less than the lower bound given in the GOS parameter set, is dynamic andbased on total queue occupancy.EUM transmit queue length limit determines the optimal TCP receive window size (themaximum allowed number of outstanding unacknowledged bytes) used by the hostapplication. Some Internet Speed Boost programs intended for DOCSIS or ADSLconnections, simply increase the receive window size to very large values. This increaseresults in very long queues at the CCU, more discarded packets, increased retransmissions,and reduced throughput. To maximize throughput, WaveRider recommends setting thereceive window size of these applications to between 18000 bytes (~12 packets) and 24000bytes (~16 packets).TIP: Utilities are commercially available for optimizing the TCPreceive window size in the end-user’s computer, throughmanipulation of the Windows registry.Polling MAC StatisticsA wide range of Polling MAC statistics are recorded by the CCU and EUM. These statistics arevery useful, particularly during installation and as an aid to troubleshooting. A complete list ofstatistics provided by entering the <stats mac> command through the CLI can be found inMonitoring the Network on page 127.Performance ModellingThe performance of packet radio systems like the LMS4000 900MHz Radio Network cannoteasily be derived from analytic calculations. However, using computer simulations that aredesigned to accurately reflect the system implementation, and user and network trafficdistributions, it is possible to produce statistical representations of LMS4000 systemperformance.WaveRider has developed a model that simulates LMS4000 system processes, tasks,protocols, propagation delays, and queue sizes. The model can simulate systems with largenumbers of EUMs and wide ranges of user traffic. The inputs to the model include• number and geographical distribution (distance from CCU) of EUMs,• user traffic statistics, and• RF link-quality distributions.These inputs are based on WaveRider’s experience with actual customer installations. Theoutputs of the model are statistical representations of system performance.
3 Detailed DescriptionAPCD-LM043-4.0 43To illustrate the output of the model, consider the following example. First of all, make thefollowing general assumptions:• LMS4000 900 raw channel rate is MHz 2.75 Mbps• There are no channel errors• Servers are fast and do not present a bottleneck• There are no external link or backhaul bottlenecks• TypicalCCUtoEUMrangeis0to3km• GOS is unlimitedFurthermore, assume that typical end-user traffic is Web browsing, averaging one 60 kbyteHTTP transfer every two minutes. This traffic pattern is based on analyses of busy-hour datacollected from LMS systems consisting primarily of residential users. In normal usage, usersrandomly and independently download a file or Web page, take time to process theinformation, and then download another file or Web page. Assuming this type of traffic, theperformance shown in Figure 23 results.Figure 23 Net Throughput per EUM — 100 EUMs, 60 kbyte HTTP every 2 minutesFrom Figure 23, each of the 100 end users can expect a net throughput better than 800 kbps80% of the time, and better than 1.3 Mbps 20% of the time. You can also assess system00.20.40.60.810 500 1000 1500 2000Performance (kbps)Probability that Performance wasExceeded
3 Detailed Description44 APCD-LM043-4.0performance based on the number of EUMs that are associated at any given time, as isillustrated in Figure 24..Figure 24 Associated EUMs — 100 EUMs, 60 kbyte HTTP every 2 minutesOf the 100 EUMs, each is associated at random times and for random intervals, so theprobability of having more than ‘n’ EUMs associated must be determined statistically.From Figure 24, 25% of the time only 2 of the 100 EUMs are associated at the same time.Less than 1% of the time, there are only 7 associated EUMs. Even with 100 EUMs, where endusers are browsing and downloading during the same period, 6% of the time no EUM isassociated.0510152025300123456789Associated EUMsFrequency (%)
3 Detailed DescriptionAPCD-LM043-4.0 45By increasing the number of EUMs to 300 and maintaining the same level of traffic per EUM,the modelled performance becomesFigure 25 Net Throughput per EUM — 300 EUMs, 60 kbyte HTTP every 2 minutesFrom Figure 25, each of the 300 end users can expect a net throughput better than 300 kbps80% of the time, and better than 750 kbps 20% of the time. Once again, you can assesssystem performance based on the number of EUMs that are associated at any given time, asis illustrated in Figure 26.Figure 26 Associated EUMs — 300 EUMs, 60 kbyte HTTP every 2 minutesFrom Figure 26,of300EUMs,eightwereassociated 12% of the time, and 14 were associatedless than 3% of the time. The amount of time 25 or more EUMs were associated was less than0.4%.00.20.40.60.810 500 1000 1500 2000Performance (kbps)Probability that Performancewas Exceeded024681012140246810121416182022Associated EUMsFrequency (%)
3 Detailed Description46 APCD-LM043-4.0All of these charts illustrate that many (LMS4000) users can share the limited bandwidth ofthe channel, yet most of the time, each perceives that they have most of the channel tothemselves.Atypical ApplicationsThe Polling MAC has been optimized for normal user applications. One basic assumption thathas been made in the design of the Polling MAC is that users are only associated for a smallfraction of the time they are sitting in front of their computers. This usage is typified, forexample, by a file transfer (Web page for example) every two minutes or so—each transfertaking a second or two. The MAC takes advantage of this usage pattern by only associatingwith active EUMs.A second assumption is that EUMs become active independently. If many EUMssimultaneously attempt to use the random access opportunity, they will collide multiple timesand may not get through.If the above assumptions are reasonable, then it is also reasonable to assume that a limitednumber of EUMs will be associated at any given time, as demonstrated in PerformanceModelling on page 42.There are several computer applications where usage is not consistent with the aboveassumptions. These applications, which are discussed below, can compromise the efficientoperation of the LMS4000 network and may cause the network to slow down.Broadcast ApplicationsSome applications broadcast messages to which all or a large number of hosts are expectedto respond. If these applications are running over the system, not only will responses fromdisassociated EUMs collide as the random access opportunities are overwhelmed, but thosethat do get through will quickly use up all of the available associations. With so manyassociated EUMs, polls are farther apart and throughput degrades, even if the newlyassociated EUMs have no further traffic to send. As well, EUMs that are not associated are notable to associate and are therefore be blocked for a few seconds. The following applicationscan cause this type of problem:•Broadcast pings: WaveRider recommends not using broadcast pings.•SNMP broadcast requests: WaveRider recommends not using SNMP broadcastrequests.•Windows Network Neighborhood: This traffic can be blocked using port filtering atthe CCU or EUM level, as discussed in Port Filtering on page 49.Periodic Packet SourcesSome applications send individual packets at fixed, often large, intervals, expecting only asingle packet or small number of packets in response. The direct impact of these applicationsis that EUMs that are sent periodic packets remain associated for a longer period of time thanthat warranted by their end-user traffic level and continue to be polled unnecessarily. Theatypical applications themselves will function very well; however, they will use up a significantamount of the channel bandwidth. This group includes the following applications:
3 Detailed DescriptionAPCD-LM043-4.0 47•Pings (interval is typically 1 second): WaveRider recommends the operator avoidrunning applications that generate a lot of pings, such as What’s Up Gold.•Network gaming (interval is typically 0.25 seconds): WaveRider can provide a GOSclass for managing this kind of traffic if specific end users are running this type ofapplication.•SNMP poll (interval is typically 30 seconds): This traffic is usually generated by theoperator. WaveRider recommends increasing the SNMP poll interval to a large value,for example, greater than one hour and, if possible, that the SNMP application not pollall EUMs in the same short interval.TIP: Consult WaveRider for a special GOS Configuration File tolimit the impact of these atypical applications for specific EUMs.Network MonitoringSome applications send packets to each host on the network, usually to determine whetherthe host is accessible and/or functioning. These applications, which may be run by the systemoperator, cause EUMs that otherwise would not be associated to become associated. Often,the additional load from applications of this type can even exceed the end-user traffic load onthe system. Since these applications tend to be periodic, the load is presented to the systemregularly over an indefinite period. Also, with large networks, application polling may soonexceed the maximum number of associations. In this case, the application may not be able toreceive responses from some EUMs, presenting the operator with misleading statusinformation. This group includes the following applications:•SNMP polling: As noted above, WaveRider recommends increasing the SNMP pollinterval to a large value, for example, greater than one hour, and staggering polls togroups of EUMs.•SNMP service discovery: Service discovery is not required for management of theLMS4000 900 MHz Radio Network.•Ping scripts,suchasWhat’s Up Gold: WaveRider recommends obtaining a tool tostagger the pings.Since the network operator controls most of the above applications, WaveRider recommendslimiting or at least delaying their use until non-busy hours.Voice Over IP (VoIP)Voice over IP (as opposed to streaming audio or video) requires small packets to be sent atvery short intervals — usually around 20 ms — with very little latency allowed in eitherdirection. While the LMS4000 900 MHz Radio Network may be able to support this level,either as a guaranteed grade of service class parameter or on a best effort basis, VoIPapplications result in a high per packet overhead on the radio channel. This overhead and therequirement for low latency mean the VoIP call occupies about 10% of the available bandwidthfor the duration of the call. It obviously does not take very many VoIP users to significantlyaffect system performance. Also, unless this grade of service guarantee is given, the quality of
3 Detailed Description48 APCD-LM043-4.0the call may be affected as other users become associated, increasing the polling intervalbeyond 20 ms. Since the grade of service applies to an EUM and not to an individual service,a VoIP user would have to be given a very high grade of service, to the possible detriment ofother end users.3.6 CCU and EUM Feature Description3.6.1 DHCP RelayIP address information for CCUs and EUMs are manually entered. In the case of end-userPCs, IP addresses can be entered manually or obtained automatically from a DHCP server, ifCCU DHCP relay is enabled.Once DHCP Relay is enabled in the CCU, DHCP requests from the end-user’s computer passtransparently through the CCU and EUM to the operator’s DHCP server. Since the IP addressassigned to the end-user’s computer must be on the same subnet as the CCU radio port, theoperator needs to preassign an appropriate block of IP addresses in the DHCP server.TIP: It is helpful to assign meaningful names, such as thecustomer name, to customer computers or home networkrouters. Then, if a DHCP server is implemented, the addressleases pool includes this name with the client IP address,facilitating easier identification.
3 Detailed DescriptionAPCD-LM043-4.0 49The gateway router can provide DHCP server functionality, or you can implement a dedicatedDHCP server, as shown in Figure 27.Figure 27 DHCP Relay3.6.2 Port FilteringThe CCU and EUM both support TCP and UDP port filtering. The IP protocol suite is made upof many subcomponents consisting of ports and protocols. Up-to-date listings of TCP andUDP ports can be obtained off the Web. Some of these ports are required for normal LMS4000operation, but most are not. The system operator can configure the CCU and EUM to filterpackets on specific TCP or UDP ports to improve network performance, security, or privacy.For example, to prevent end-users from having visibility of, and access to, other end-usersthrough Windows Network Neighborhood, filter the following ports at the CCU for both UDPand TCP packets:• Port 137 NETBIOS Name Service• Port 138 NETBIOS Datagram Service• Port 139 NETBIOS Session Service• Port 1512 Microsoft’s Windows Internet Name ServiceCAUTION: The EUM is delivered with port filtering enabled.CAUTION: Do not enable filters to block Telnet (port 23), FTP(ports 20 and 21), or SNMP (ports 161 and 162); otherwise, youwill not be able to manage your network.CCU3000(with DHCP Relay enabled)Antenna EUM3000NMS StationSwitchInternetEnd-user Computer(with DHCP enabled)DHCP ServerDHCPRequestDHCPResponse(layer-2messages)DHCPRequest(UDP)DHCPResponse(UDP)Router
3 Detailed Description50 APCD-LM043-4.03.6.3 SNTP/UTC Time ClockThe Simple Network Time Protocol (SNTP)/UTC feature provides LMS4000 devices with anaccurate clock for time stamping events in the log file.SNTP/UTC Time Clock operation is illustrated in Figure 28.Figure 28 SNTP/GMT Time ClockThe CCU, acting as an SNTP time client, regularly resynchronizes to one of several NTPServers from which it obtains UTC (Universal Coordinated Time). The CCU resynchronizationand retry periods can be set by the operator. The resynchronization period is the time betweena successful CCU resynchronization and the next CCU resynchronization attempt, typicallyset to one hour. The retry period is the time between an unsuccessful resynchronizationattempt and the next resynchronization attempt, typically set to 30 seconds.The operator can configure the CCU to act as an SNTP time server to the EUMs andbroadcast time information to all EUMs after it has synchronized with the NTP server. It alsobroadcasts this information whenever an EUM powers up and registers.UTC, the international time standard, is based on a 24-hour clock. It is the current term forwhat was commonly referred to as Greenwich Mean Time (GMT). Universal time is based ona 24 hour clock. SNTP, specified in RFC1769 and RFC2030, is a simplified version of NTP,which is specified in RFC1305.By default, the CCU SNTP client is disabled.OnceSNTPisenabled, the CCU tries tosynchronize with an NTP server. The operator can configure the CCU to synchronize with• a local router or network device, if the router or network device is configured as anNTP time server,• any open-access NTP server of the operator’s choosing, or• one of the five factory-default open-access NTP servers listed below:• 132.246.168.148 time.nrc.ca stratum 2, Canada• 140.162.8.3 ntp.cmr.gov stratum 2, US• 136.159.2.1 ntp.cpsc.ucalgary.ca stratum 2, Canada• 192.5.5.250 clock.isc.org stratum 1, US• 127.0.0.1 local host (the CCU itself)CCU3000Antenna EUM3000NTP ServerInternetTime RequestTimeTimeBroadcast
3 Detailed DescriptionAPCD-LM043-4.0 51CAUTION: The local host entry, 127.0.0.1, is required to avoidthe problem where the CCU cannot find a real NTP server (i.e., ifthe network is down).3.6.4 Customer ListFor each EUM, the system operator can control the number of end-user computers that canaccess the LMS4000 network for the purpose of controlling network performance or servicedifferentiation. The use of this list is described in Customer Table (EUM only) on page 192.3.6.5 SNMP SupportSimple Network Management Protocol (SNMP) allows a network management server tomonitor, control, and remotely configure LMS4000 network devices. In SNMP, these devicesare also referred to as agents.Community StringsCommunity strings act as passwords to facilitate communication between the SNMP serverand a network device. There are three types of community strings:•Read community strings, which enable SNMP servers to retrieve information from anetwork device•Write community strings, which enable SNMP servers to send information, such asconfiguration commands, to a network device.NOTE: At this time, there are no writable SNMP MIB entries. Allconfiguration is done via the CLI.•Trap server IP address and community strings, which enable SNMP servers toreceive unsolicited messages from a network device. These unsolicited messagesindicate asynchronous events, such as an interface going down or coming up, a unitperforming a cold or warm start, or an operational failure.Each network device monitored by SNMP must have at least one of each type of communitystring defined. Each CCU and EUM can have up to five read or read/write and five trapservers/community strings defined. Non-WaveRider devices may have only one of each typeof community string defined. Community strings are case sensitive.Table 9 Factory Configured Community StringsCommunity String Type Community StringRead publicWrite privateTrap <none>
3 Detailed Description52 APCD-LM043-4.0CAUTION: By convention, most equipment ships with thedefault community strings defined in Table 9. WaveRiderrecommends that you change the community strings before youbring the LMS4000 equipment online, so that outsiders cannot seeinformation about the internal network or configure systemcomponents.Management Information Bases (MIBs)All messages sent between the SNMP server and a network device are based on numbercodes. Each of these number codes corresponds to a specific type of information (such as thequantity of data packets received) associated with a specific type of network device (such as aCCU). These number codes and their meanings are stored in a management information base(MIB). The SNMP server and network devices use these MIBs as lookup tables for translatingmessages sent between them.LMS4000 implements SNMPv2c and includes a number of standard and enterprise MIBs:• RFC1157 (MIB-Il)• RFC1493 (bridging)• WaveRider Enterprise MIB (defined in Appendix G on page 199)You can download WaveRider Enterprise MIBs, which include a comprehensive set of CCUand EUM parameters and statistics, from the technical support page at www.waverider.com.
APCD-LM043-4.0 534IP Network PlanningThis section describes a plan for assigning IP addresses to LMS4000 900 MHz Radio Networkcomponents.4.1 LMS4000 IP AddressingBefore discussing IP planning, there are a few concepts that are worth reviewing. The firstconcept is that in the LMS4000 900 MHz Radio Network, IP addresses are assigned todevices for several reasons:• The device is a router, such as the gateway (NAP) router or the CCU. IP addressesare required for each router port.• The device is a destination or source for user data. End-user PCs and networkservers (such as DHCP servers) fall into this category.• The operator wants to configure, control, or monitor the device. Virtually all LMS4000components fall into this category.
4 IP Network Planning54 APCD-LM043-4.0The second concept is the segmentation of the LMS4000 network into distinct subnets, asillustrated in Figure 29.Figure 29 LMS4000 SubnetsRouters isolate the subnets from each other or from the Internet. The router applicationisolates the CCU radio subnets from the CCU Ethernet subnet, and the gateway (NAP) routerisolates the CCU Ethernet subnet from the public Internet.The number of CAPs that can be supported by one gateway is limited only by the capacity ofthe gateway router. If a system has 15 CAPs, each supporting three CCUs, the systemconsists of 45 radio subnets.The radio subnets extend from the CCU radio port through the EUMs to the end-user PCEthernet ports. Each radio subnet includes the following elements, all of which, from thestandpoint of the LMS4000 network, require a unique, most likely private, IP address:• CCU radio port one per radio subnet• EUM up to 300 per radio subnet• End-user PC (or LAN router)• Ethernet port one per EUM (up to 300 per radio subnet)Based on the above, each radio subnet requires a maximum of 601 IP addresses, whichnecessitates a subnet with a 22-bit subnet mask, which provides 210 = 1024 addresses.The CCU Ethernet subnet extends from the CCU Ethernet port through backhaul facilities andEthernet switches to the gateway (NAP) router Ethernet port. The CCU Ethernet subnetincludes the following elements, all of which, from the standpoint of the LMS4000 network,require a unique IP address:• CCU Ethernet ports• RFSMs,ifprovisionedGateway (NAP)RouterInternetCAPn, CCUmRouter ApplicationCAP01, CCU01Router ApplicationCCU EthernetSubnetCAPn, CCUmRadio SubnetCAP01, CCU01Radio Subnet EndUsersEndUsersPrivate NetworkPublic Network... ... ...... ... ...CAP15, CCU03Router ApplicationCAP15, CCU03Radio SubnetEndUsers
4 IP Network PlanningAPCD-LM043-4.0 55• CAP-NAP backhaul equipment, if provisioned• CAP and NAP UPS, if provisioned• Ethernet switches• SNMP manager, if provisioned• Gateway (NAP) router Ethernet portThe number of CAPs is limited by the capacity of the gateway (NAP) router. WaveRidersuggests allocating a minimum of 256 addresses to the CCU Ethernet subnet, whichaccommodates 15 CAPs and requires a 24-bit subnet mask.4.2 IP Planning ProcessFor reference purposes, an example of an IP Plan is included in Appendix I on page 241.Before you configure and operate your LMS4000 900 MHz Radio Network, you must defineyour IP addressing scheme based upon the following guidelines and recommendations:• WaveRider recommends that LMS4000 subnets use IP addresses that have beenreserved for private networks. WaveRider recommends 192.168.10.0 /24 for the CCUEthernet subnet, and 10.0.0.0 /22 for the CCU radio subnet, since these addressesare quite distinct from each other. If you are already using 10.0.0.0 /22, then you canalternatively use 172.16.0.0 /22.• The IP addressing plan for the CCU Ethernet subnet should allow for growth to amaximally equipped system, as follows:• CCU Gateway IP address one• NAP equipment IP addresses up to 10• CAP equipment Ethernet IP addresses number of CAPs x 16For a 15-CAP system, set aside 251 IP addresses, which requires a subnet with a 24-bit mask, for example 192.168.0.0 /24.In the example shown in Appendix I on page 241, the IP addressing plan for the CCUEthernet subnet is summarized as follows:CCU Ethernet Subnet 192.168.10.0 /24Gateway Router 192.168.10.1 /24NAP Switch 192.168.10.5 /24NAP UPS 192.168.10.6 /24SNMP Manager 192.168.10.7 /24CAP01, CCU01 Ethernet port 192.168.10.11 /24CAP01, CCU02 Ethernet port 192.168.10.12 /24CAP01, CCU03 Ethernet port 192.168.10.13 /24CAP02, CCU01 Ethernet port 192.168.10.27 /24.....CAP15, CCU02 Ethernet port 192.168.10.236 /24
4 IP Network Planning56 APCD-LM043-4.0CAP15, CCU03 Ethernet port 192.168.10.237 /24• As noted above, the IP addressing plan for each CCU radio subnet should allow forgrowth to a maximally equipped system. Providing 601 IP addresses on the samesubnet requires a subnet with a 22-bit mask, for example 172.16.0.0 / 22.In the example shown in Appendix I on page 241, the IP addressing plan for the CCUradio subnets is summarized in Table 10:Table 10 Example — CCU Radio Subnet IP Addressing• The end-user PC Ethernet IP address can be entered statically, or dynamically usingDHCP. If DHCP Relay is enabled in the CCU, which WaveRider recommends, and thesystem operator has installed and properly configured a DHCP server in the network,then the end-user computer can be simply configured to automatically request its IPaddress from the DHCP server. The operation and configuration of DHCP Relay isdiscussed in DHCP Relay on page 48. To use DHCP, the system operator mustallocate, for each CCU radio subnet, a pool of IP addresses from the CCU subnet,such as the contiguous sets of end-user PC IP addresses defined in Table 10.• If you are using unregistered IP addresses for the EUMs and end-user PCs, theseaddresses must be translated to globally unique Internet registered addresses beforethey leave the private domain. Although the CCU functions as a router, it does notprovide address translation.For end users to access the Internet, you must provide NAT (Network AddressTranslation). Normally, NAT is provided in the gateway (NAP) router. Refer to section4.3, Network Address Translation for further information.CCU CCU RadioPort EUM Range End-user PC RangeCAP01, CCU01 172.16.4.1 172.16.4.2 - 172.16.5.47 172.16.6.1 - 172.16.7.46CAP01, CCU02 172.16.8.1 172.16.8.2 - 172.16.9.47 172.16.10.1 - 172.16.11.46CAP01, CCU03 172.16.12.1 172.16.12.2 - 172.16.13.47 172.16.14.1 - 172.16.15.46CAP02, CCU01 172.16.16.1 172.16.16.2 - 172.16.17.47 172.16.18.1 - 172.16.19.46... ... ... ...CAP15, CCU02 172.16.176.1 172.16.176.2 - 172.16.177.47 172.16.178.1 - 172.16.179.46CAP15, CCU03 172.16.180.1 172.16.180.2 - 172.16.181.47 172.16.182.1 - 172.16.183.46
4 IP Network PlanningAPCD-LM043-4.0 574.3 Network Address TranslationThe following address translation alternatives are listed for reference purposes. Choose thebest alternative for your system. Your choice depends on the number of available registeredIP addresses. It also depends on the nature of your subscriber base; for example, static NATmay be required to support some of your business users, but dynamic NAT may be adequatefor most of your home users.Static NATStatic NAT maps an unregistered IP address to a registered IP address on a one-to-one basis.This method of translation is recommended if, for example, end users are using VPN facilitiesto access remote applications.Dynamic NATDynamic NAT maps an unregistered IP address to a registered IP address, taken from a poolof registered IP addresses. This method of translation is useful when you have a large numberof unregistered users who wish to access the Internet. Depending on the traffic pattern, 10registered IP addresses may be able to serve 40 end users.OverloadingOverloading, which is a form of dynamic NAT, maps multiple unregistered IP addresses to asingle registered IP address by using different ports. This technique is also known as portaddress translation (PAT), single-address NAT, or port-level multiplexed NAT. PAT greatlyreduces the number of necessary registered IP addresses. When overloading is configured,the router maintains enough information from higher-level protocols to translate the registeredaddress back to the unregistered address for traffic inbound from the Internet.
—This page is intentionally left blank —
APCD-LM043-4.0 595Radio Network PlanningAn important task in the implementation of LMS4000 900MHz Radio Networks is RF systemplanning and design. Whether you are deploying a single CCU or a complex multi-CAP, multi-CCU network, proper system design is necessary to provide and maintain high-quality serviceto end users in your target serving area.5.1 Design MethodologyThe following sections are not intended to provide detailed system design instructions;instead, they provide system design guidelines. WaveRider used this approach for thefollowing reasons:• Factors affecting system design and implementation vary widely and differ fromsystem to system.• System design and implementation cannot be encapsulated in a simple formula or setof formulas.Each system design is unique and must take into account all of the design factors that caninfluence system operation and performance:• Topography: Hills and valleys that create coverage holes or conversely, areas thatmay be very exposed from an RF standpoint, exposing subscribers in these areas tohigh levels of interference generated from outside the system or by other CAP sites.• Clutter: Obstructions such as trees and buildings, which tend to reduce the desiredsignal level and coverage.• Network Topology: The configuration of the network, implemented to provide optimumservice. Network topology is driven by factors such as the location of the Internet pointof presence, the availability of towers and roof-top locations that can be used toestablish antenna and equipment sites, and the target coverage area.• Interference: The presence of interference, either in-band (in the ISM band) or out-of-band in your target serving area constrains the freedom that you have for determiningthe location of CAP sites and for choosing operating frequencies.
5 Radio Network Planning60 APCD-LM043-4.0In all cases, these wide-ranging factors drive the system design and as a result, no twosystems will be implemented the same way.The design methodology presented in this chapter uses a building-block approach. If thesystem you are designing is based on a single CCU, you need only read and learn about theguidelines presented in Basic System Design on page 60. If you need multiple CCUs or CAPsto satisfy your network requirements, you must perform a much more detailed engineeringdesign based on the general guidelines provided in Multi-CAP RF Network DesignConsiderations on page 67.For purposes of illustration, coverage areas are presented using the popular cellularhexagonal coverage pattern. In practice, radio coverage does not conform to hexagonalshapes; however, hexagons are used to represent radio coverage because graphically, theycan fully cover a plane surface and because they provide an easy-to-understandrepresentation of coverage cells.5.2 Basic System DesignBasic system design guidelines apply to all LMS4000 system implementations, from a simple,single-CCU system, to more complex multi-CCU CAPs and multi-CAP networks.5.2.1 Overview of Basic System DesignThe basic design of the LMS4000 900MHz radio network involves the following procedures:• Conducting a spectral survey to identify, quantify, and assess the impact of existingin-band and out-of-band interference.• Determining single- or multi-CAP system requirements based on RF coverage, CAPlocations, and system loading.5.2.2 Spectral Survey of the Target Service AreaBefore starting the system design, WaveRider recommends conducting a spectral survey ofthe target serving area to determine the radio landscape—that is, to determine if there are anyin-band or out-of-band interferers and how, and to what degree, these interferers constrainyour system design (site location, frequency, equipment).The spectral survey involves travelling to key locations throughout the target serving area,especially to locations that may be potential CAP sites, or where there are significant numbersof potential end users, and recording the radio spectrum (ISM band +/- 10MHz) at each ofthese locations. The survey requires the use of a spectrum analyzer and a trained RFengineer who is capable of interpreting the results. There are a number of independent RFengineering firms that can provide this service, including the WaveRider Professional ServicesGroup. If you have access to the required equipment and in-house skill set, you can alsoconduct this survey yourself.The spectral survey is a critical first step in the system design. Not only does it provide thestarting point for the RF network design, it establishes a baseline for the use and occupancy of
5 Radio Network PlanningAPCD-LM043-4.0 61the spectrum. Keep in mind that one of the major attractions of the ISM band is the fact that itis license free; as such, it is shared spectrum. To regulate the band, regulatory bodies, suchas FCC and Industry Canada, require that new operators in the band take responsibility forresolving interference issues when their newly installed system interferes with systems thatare already in operation. The spectral survey identifies systems that are operating in the ISMband and establishes a documented baseline, which may provide you some protection fromfuture ISM-band installations that interfere with the operation of your system.It cannot be overemphasized that radio communications is, by nature, a non-staticenvironment. As a wireless ISP, the more you know about the RF environment in which youare operating, the better prepared you will be to address future service-affecting changes inthis environment. Given that the RF environment is dynamic, WaveRider recommendsperforming spectral surveys on a regular basis, perhaps every 3-6 months.5.2.3 In-band InterferenceIn-band interference occurs when other wireless systems are operating in the same band andin the same geographical area as your system. The impact of in-band interference may belimited—that is, the unwanted signal level may be so low as to have no impact at all, or it mayonly affect service to a single end user or a small number of end users. In-band interferencemay, however, be system wide, particularly if it is geographically dispersed around yourserving area or it is in close proximity to the CAP. System-wide interference obviously causesthe most impact to system operation since it affects all end-users in the serving area.A primary purpose of the spectral survey is to identify in-band interference so that, if it ispresent, the RF network design can address the interference sources through careful locationof the CAP, equipment configuration, and frequency selection, with the goal of maximizing theratio of the desired to the interfering signals throughout the serving area. If these measuresare not adequate, channel filters can in many cases reduce the interference to levels withinthe operating tolerance of the LMS4000 radio equipment. Channel filters are discussed inUsing Bandpass Filters at CAP Sites on page 63.5.2.4 Out-of-band InterferenceThe radio spectrum is a finite commodity, which in the growing world of wirelesscommunications, means that all users must compete for this limited resource. The implicationis that throughout the service life of your LMS4000 system, you need to be aware of your “RFneighbors” and the impact they may have on your system operation and performance. Asdescribed in Physical Layer (DSSS Radio) on page 28, the LMS4000 900MHz productoperates in the 902–928MHz ISM band. In many areas of the world, including North andSouth America, the 900MHz ISM band is sandwiched between the top end of the cellular radioband and the bottom end of the commercial paging band.Cellular radio and paging systems are common in many regions, so you must take precautionswhen planning your LMS4000 900MHz radio network. Specifically, you need to know thelocation of all cellular and paging transmitters that are in, close by, or planned for, your servingarea, so that you can limit the impact of these potential interferers through proper site location,equipment configuration, and frequency selection.
5 Radio Network Planning62 APCD-LM043-4.0Figure 30 shows an actual spectral sweep, recorded using a spectrum analyzer as part of aspectral survey, which shows the location of the cellular and paging transmitters in relation tothe ISM band. Note the relative levels of the interfering signals.Figure 30 Example of a Spectral SweepCellular and paging systems in the bands adjacent to the ISM band can interfere with yournetwork and need to be addressed as follows:• Identify and quantify all potential sources of interference by conducting and applyingthe results of the spectral survey.• If your CCUs or EUMs are close to cellular or paging sites, their receivers may bedesensitized by the high levels of the interfering transmitters, which can operate atvery high levels (100 W per cellular radio carrier, 1500W for paging transmitters). Toprovide service to these EUMs, choose an operating frequency that is as far fromthese cellular and paging transmitters as possible.Try to assign frequencies that are not adjacent to the cellular or paging channelsidentified in your serving area. Consider the scenario illustrated in Figure 31.Asshown, a cellular tower is located in sector A of the LMS4000 radio network. Sincecellular frequencies are located just below the ISM band, a reasonable designCellular RadioTransmittersPagingTransmittersISM Band
5 Radio Network PlanningAPCD-LM043-4.0 63approach would be to assign a higher frequency to sector A, such as 915MHz or925MHz.Figure 31 Network Design in the Presence of Out-of-band Interference5.2.5 Using Bandpass Filters at CAP SitesWaveRider provides high-quality, specially designed bandpass filters for use with the CCU.These filters reduce the effect of unwanted out-of-band and off-channel in-band interference.As discussed in Propagation Path on page 31, it is highly desirable to locate the CAP site sothat the CCU antennas are high enough to provide clear line of sight paths to the maximumnumber of EUMs in the serving area. The goal is to make sure the CCU can see the maximumnumber of EUMs and conversely, to make sure the maximum number of EUMs can see theCCU.Attaining this goal, however, has a consequence since it may mean the CCU will be in an ideallocation to see interferers in its sector as well. Bandpass filters at the CCU reduce the effect ofinterference from out-of-band or off-channel in-band interferers.On-channel interference may result from• on-channel interferers in the ISM band, or• transmitter phase noise or intermodulation products generated by out-of-bandinterferers.Bandpass filters cannot resolve on-channel interference; instead, you must change to a moresuitable CCU operating frequency.For CAP sites in which multiple CCUs are installed, use of bandpass filters to ensure non-interfering operation of CCUs is mandatory. It is important to remember that in the 900 MHzISM band, the radio transmit and receive occur on the same frequency and use Time DivisionDuplexing (TDD) to switch between the transmit and receive cycles. Multi-CCU installationspose the highest threat of CCU to CCU adjacent channel interference. For the RF networkSector CSector ASector BCellularTransmitterCAP
5 Radio Network Planning64 APCD-LM043-4.0engineer, as specified in Appendix A Specifications, the minimum separation betweencolocated channels is 6.6 MHz (an orthogonal adjacent channel) and requires a C/I ratio of 50dB or better for non-interfering CCU operation. Once the antenna system gains and poweroutput of the CCU radio are accounted for, the only way to practically provide adequateisolation for the required adjacent channel isolation is through the use of bandpass filters.5.2.6 Single- or Multi-CAP ImplementationAn important step in basic system design is to determine if a single CAP site adequatelycovers your target serving area, or if a second CAP site, or multiple CAP sites, will berequired. The main factors that drive this decision are the RF coverage and the systemloading.RF CoverageThe RF coverage of the sector is a function of many different factors.Commercially available radio coverage prediction software calculates radio coverage basedon the following factors:• Propagation characteristics (frequency, distance from the site)• Radio characteristics (transmit power, receiver sensitivity)• Antenna system and height• Topography• ClutterUsing this coverage prediction software, a qualified RF design engineer is able to produce RFcoverage estimates. Again, there are a number of independent RF engineering firms that canprovide this service, including the WaveRider Professional Services Group. If you have therequired software and in-house skill set, you can perform this coverage analysis yourself.
5 Radio Network PlanningAPCD-LM043-4.0 65The location of the CAP site in relation to the serving area determines whether the site will bea corner- or center-illuminated cell. Figure 32 illustrates the difference between these twomethods of illumination.Figure 32 Corner- and Center-illuminated cellsAlthough the difference between the two approaches may seem academic at first, the choiceyou make affects the system design, in particular, the selection of sites, site antennas, and thesystem growth path.Center IlluminationA center-illuminated cell is generally the simplest to implement. In this case, a site isestablished at a suitable location near the middle of the target serving area. An omnidirectionalantenna is usually installed to deliver 360-degree coverage around the site.When system traffic increases beyond the capacity of a single CCU because, for example,many subscribers have been added to the system, more CCUs can be added to the CAP site(up to a total of three operating CCUs per CAP site). The omnidirectional antenna would, inthis case, be replaced with sectored antennas, for example, three 120-degree sectoredantennas. The selection of the sectored antennas would depend on how evenly thesubscribers are distributed throughout the serving area. In this example, the resultingCAPCAPCenter-Illuminated CellCorner-Illuminated CellServing Area
5 Radio Network Planning66 APCD-LM043-4.0configuration would triple the traffic-handling capacity of the site. Figure 33 illustrates thesectoring of a previously center-illuminated omnidirectional cell.Figure 33 Sectored CellCorner IlluminationCorner illumination is generally used when it is not possible to establish a suitable CAP sitenear the middle of the target serving area. Implementation of a corner-illuminated cell requiresmore extensive site and system engineering than does the implementation of a center-illuminated cell. This is particularly true when additional traffic-handling capacity is required,since techniques such as overlay/underlay sectors (adding a second CCU to provide coverageto the same geographical area) may have to be applied.The use of omni-directional antennas at CAP sites, although simple in implementation, is onlyrecommended for simple network installations with low risk of interference and limitedexposure to other sites. Omni-directional antennas, by definition, are designed to providecoverage in all directions (360°) horizontally around the antennas. This wide angle-of-viewprovides for simplicity of an omni-directional antenna installation but also means that the omni-directional antenna is susceptible to any interference in the area. As such, the RF networkdesigner, when faced with interference or system expansion will generally need to replace theomni-directional antenna(s) (and possibly multiple CCUs) in order to serve the same coveragearea and to make use of the directional properties of the antennas to address system issues.System LoadingSometimes, even with well-engineered RF coverage, the user traffic may be so high that youneed to expand the network to a multi-CAP system.The answer to the question “How many subscribers can each CCU support?” is a qualified “Itdepends.” Refer to Performance Modelling on page 42 for a description of the method used byWaveRider to predict the number of end-users that can be supported by the LMS4000network. Total system traffic is very dependent on the usage profile of the end users and thetariff structure that has been implemented by the system operator. For instance, an LMS4000900MHz system that is providing service to a number of small businesses, each supportingCAP
5 Radio Network PlanningAPCD-LM043-4.0 67multiple users, likely generates a lot more daytime traffic than a simple residential serviceused for Web browsing and email.In summary, the network design engineer must be aware of the intended use of the system —the customer profile, tariff rates, and committed grades of service — since these factors allinfluence the traffic demand on the system.5.3 Multi-CAP RF Network Design ConsiderationsOne of the differentiating features of the LMS4000 900MHz radio system is its ability tosupport multi-CAP networks. The design of multi-CAP networks is significantly more complexthan the design of single-CCU or single-CAP systems. WaveRider highly recommends the useof a qualified RF engineering firm, such as the WaveRider Professional Services Group, tocarry out multi-CAP system design. If you are confident that you have the required skill setavailable in house, you can carry out this design yourself.5.3.1 Multi-CAP Network Design ProcessThe process for designing a multi-CAP network can be summarized as follows:1. Conduct a preliminary site survey and selection.2. Apply a frequency grid to the sites that you have selected.3. Determine the site-to-site signal levels by• Determining site-to-site distances,• Calculating site-to-site propagation loss,• Normalizing the signal levels at each site, and• Factoring in the antenna isolation.4. Using the C/I information presented in C/I Requirements on page 68, formulate afrequency plan and channel assignment.5. Perform and apply antenna down-tilt calculations.6. Assess the impact of known in-band and out-of-band interferers.7. Verify and iterate the design as many times as necessary.This chapter does not provide detailed instructions on how to carry out each of the abovetasks as it is beyond the scope of the document. It does, however, provide you with theLMS4000-specific information that you or your RF engineering firm need to be able to carryout the above steps.5.3.2 Frequency Selection — Standard Frequency SetLMS4000 900 MHz equipment (CCUs and EUMs) can operate on all channels from 905 to925 MHz, in increments of 0.2 MHz (refer to Table 6 on page 29 for channelization
5 Radio Network Planning68 APCD-LM043-4.0information). Throughout this manual, however, WaveRider has referred to the standardfrequency set shown in Table 11.Table 11 Standard Frequency SetThe standard frequency set represents a convenient and safe set of frequency assignments.The frequencies are orthogonal in that they do not overlap, and they provide enoughseparation between the frequencies so that one channel does not interfere with either of theother channels, even if they are installed at the same CAP site with appropriate filters. Usingthe standard frequency set, you can implement small systems without much concern for self-generated interference.In the case of a multi-CAP network, however, the standard frequency set may not beinadequate. Instead, you must use other sets of frequencies at neighboring CAP sites. Theselection of these other frequency sets is governed largely by the minimum C/I requirement forthe CCU and EUM radio; i.e., the amount of interference, from within or from outside thesystem, that the LMS4000 radio equipment can tolerate.5.3.3 C/I RequirementsThe CCU/EUM C/I requirements are outlined in Table 12.Table 12 Required C/I Ratio for Multi-CAP DesignAs shown in Table 12, as the frequency separation between the desired LMS4000 signal andan interfering LMS4000 signal increases, the level of an interfering signal that can be toleratedalso increases. Consider the case where the frequency separation between the desiredchannel and an interfering channel from a remote site is 0.2 MHz. To maintain a packet errorrate of 1% in the local cell, you would need to ensure that the EUMs in the local cell arereceiving the desired CCU signal at a level which is at least 22dB higher than the interferingCCU signal, 0.2MHz away.Using this information, and information about the number and location of the required CAPsites, your RF designer should be able to define a frequency plan for your system.905.0MHz915.0MHz925.0MHzC/I Ratio Frequency Separation PER22dB 0.2MHz < 1%19dB 1.6MHz < 1%11dB 3.4MHz < 1%
5 Radio Network PlanningAPCD-LM043-4.0 69As an example, consider the frequency plan shown in Table 13.Table 13 Sample Frequency Plan — Multi-CAP DesignIn Table 13,Frequency Set A uses the minimum frequency spacing that should be consideredfor a single CAP site, 6.6MHz. Frequency Set A’ represents a set of channels which areinterstitial to those in Frequency Set A. The channels in Frequency Set A’ fall midway betweenthe channels in Frequency Set A yet still adhere to the minimum recommended spacingbetween any two colocated channels, 6.6MHz.From Table 12, if two sites have a frequency separation of 3.4 MHz (Frequency Set A toFrequency Set A', for example), a C/I signal margin of 11dB is required.CAUTION: The concept of frequency reuse patterns, commonlyused in the design of cellular radio systems, cannot be directlyapplied in the design of LMS4000 900MHz radio networks.Instead, due to the nature of the Polling MAC, you should neverreuse frequencies in networks where a CCU or EUM can receive asignal from a unit in another sector or coverage area. Theminimum channel separation cannot be less than 0.2MHz s aminimum. When Polling MAC is applied in a multi-CAPenvironment, it is possible for an EUM to inadvertently lock ontothe signal from a remote CCU if that CCU is operating on thesame frequency. This situation does not occur if the remote CCUis offset by 0.2MHz or more from the local CCU, and the requiredC/I ratio is maintained. In summary, no two CCUs in a singlenetwork can be assigned exactly the same frequency .5.3.4 Dealing with External InterferenceUp to this point, the discussion has been concentrating on the effect of self-generatedinterference—that is, interference between CAPs or EUMs in the same network.As indicated in Basic System Design on page 60, you must also account for the effect ofexternal interferers such as cellular and paging systems. The RF system design engineerneeds to make sure external interference sources do not affect system operation. You can usea similar treatment to the one developed above for self-generated interference to assess theeffects of external interference sources.5.3.5 Verifying the DesignNo matter how carefully the system has been designed, you must verify the system in the fieldbefore turning it up to ensure network operation is consistent with the design standards set outby the system design engineer. With this in mind, your system implementation plan mustFrequency Set A 905.0 - 911.6 - 918.4 - 925.0Frequency Set A’ - 908.4 - 915.0 - 921.6 -
5 Radio Network Planning70 APCD-LM043-4.0provide enough time and resources for the engineering team to verify the design in the fieldthrough testing and signal-level measurements.Once you have established your CAP sites on the air, you can verify received signal levelsthroughout the network using a portable spectrum analyzer. You can then compare these withthose predicted by the RF system design. In many cases, discrepancies between predictedand actual results can be corrected, if necessary, through adjustment of antenna azimuthsand/or down-tilting.As the system grows and capacity is added, the frequency plan may have to be adjusted andmore attention given to fine-tuning the isolation between CAP sites.Verification ChecklistWhen reviewing and verifying the design of a multi-CAP network, here is a checklist of itemsthat might be considered:• General system design considerations:• Paging transmitters• Cellular transmitters• In-band interference• Frequency assignments• CAP-to-CAP frequency assignments and isolation, achieved through• Lowering antenna heights,• Antenna mounting, and the use of mounting structures to achieve greaterisolation (building, towers),• Antenna radiation patterns (directionality and side lobes), and• Antenna characteristics, back to front isolation.• CAP-to-EUM propagation must provide coverage to all EUMs from selected sites. Runthe RF model with the specified system parameters to verify thorough propagation.
5 Radio Network PlanningAPCD-LM043-4.0 715.3.6 Summary of RF Design GuidelinesA summary of guidelines presented in this chapter can be found in Table 14.Table 14 Summary of RF Design GuidelinesDO DO NOT• DO read and understand this chapterbefore you start your system designactivity.• DO contact WaveRider ProfessionalServices Group if you need assistancewith spectral surveys, RF coverageanalyses, or system engineering.• As a first step, always DO a spectralsurvey.• DO understand the RF environment inyour serving area, and DO learn asmuch as you can about potentialsources of interference.• DO verify your system design throughfield testing, prior to turning up theservice to end users.• DO try to design your system to takeadvantage of your existing real estateor radio sites.• DO use bandpass filters to reduce theeffect of off-channel in-band and out-of-band interference.• DO use different frequencyassignments or take advantage ofantenna patterns to address on-channel interference.• Wherever you can, DO use thestandard frequency set.• In the design of multi-CAP networks,DO maintain the required C/I ratioshown in Table12onpage68.• In a multi-CAP network, DO use aminimum frequency offset of 0.2MHzbetween CCUs.• DO migrate from an omnidirectional toa sectored cell when your trafficwarrant it, or interference is an issue.• DO NOT assume a static RFenvironment.• DO NOT install the CAP site inproximity to in-band or out-of-bandinterferers.• DO NOT install the CAP site in a lowarea, or area surrounded by clutter andobstructions.• DO NOT use frequencies that are closeto the edges of the ISM band if youhave identified cellular and pagingtransmitters above or below the band.• DO NOT ignore the usage patterns ofyour end users when designing yournetwork.• DO NOT assign the same frequency totwo or more CCUs in your network.
—This page is intentionally left blank —
APCD-LM043-4.0 736Installation/Diagnostic ToolsThe CCU and EUM are equipped with the following features that facilitate unit installation,operation, maintenance, monitoring, and diagnostics:•Indicators and Connectors on page 74•Command-line Interface on page 76•EUM Configuration Utility on page 77•RSSI/Tx Quality/Antenna Pointing on page 77•Transfer a File to or from a CCU Using FTP on page 78•Operating Statistics on page 79•SNMP on page 80•Field Upgrade Process on page 80•FTPing CCU and EUM Configuration Files on page 81CAUTION: When entering IP addresses in the CCU or EUM,note that a leading ‘0’ forces the CCU or EUM operating system tointerpret the entry as octal rather than decimal. For example,pinging 10.0.2.010 actually pings 10.0.2.8
6 Installation/Diagnostic Tools74 APCD-LM043-4.06.1 Indicators and ConnectorsThe CCU and EUM are equipped with LED indicators that provide a visual indication of thestatus of the unit and its interfaces. The EUM LED indicators are illustrated in Figure 34,theCCU LED indicators in Figure 35, and a detail view of the Ethernet connector in Figure 36.Figure 34 EUM LEDs and ConnectorsFigure 35 CCU LEDs and ConnectorsThe LEDs are described below:Network LEDRadio LEDPower LEDEthernet 10BaseTConsole PortPower ConnectorAntenna ConnectorTraffic LEDLink LEDUSB (not used)LEDs (Power, Radioand Network)RF ConnectorUSB (not used)DC PowerConnectorConsole PortEthernetConnector
6 Installation/Diagnostic ToolsAPCD-LM043-4.0 756.1.1 Network LEDTable 15 Network LEDNOTE: A Network LED fast flash flashes at 2.5 Hz,50% duty cycle,about two or three times per second.6.1.2 Radio LEDIn the following table, RSS is the Radio Signal Strength, in dBm.Table 16 Radio LEDNOTE: ARadioLEDslow flash flashes at 0.83 Hz, 33% duty cycle, aboutonce per second. A Radio LED fast flash flashes at 2.5 Hz,50%duty cycle, about two or three times per second.6.1.3 Power LEDTable 17 Power LEDLED State Ethernet Traffic StatusOFF No Ethernet traffic presentON Solid Ethernet traffic present but no radio trafficFast Flash Ethernet and radio traffic presentLED State RSS ValueOFF No radio signal presentSlow Flash Receive Threshold < RSS < -80 dBmFast Flash -80 dBm < RSS < -70 dBmON Solid RSS > -70 dBmLED State Power StatusOFF No powerON Power
6 Installation/Diagnostic Tools76 APCD-LM043-4.06.1.4 Ethernet LEDsThe Ethernet connector used in the CCU and EUM, shown in Figure 36, has two LEDs. TheseLEDs are described in Table 18.Figure 36 Ethernet LEDsTable 18 Ethernet LEDsThe CCU is equipped with the same LEDs as the EUM but in a slightly different physicalconfiguration. As shown in Figure 35, the CCU indicator LEDs are closely grouped and are, inorder left to right: Power LED, Radio LED (not used on CCU), and Network LED.6.2 Command-line InterfaceThe CCU and EUM are equipped with a simple command line interface through which you canmonitor unit status and configure all unit parameters. The command-line syntax is defined inAppendix C on page 123.The command-line interface can be accessed• locally or remotely, using a Telnet session, or• directly, through the DB-9 console port on the CCU and EUM, using a PC equippedwith terminal emulation software, using the console settings specified in Table 19.LED State Ethernet StatusLink LEDIf the Link LED is ON, the Ethernet physical connection isconfigured and working properly. If the Link LED is OFF, then theEthernet physical connection is not working properly, which couldbe because the wrong type of cable was used (a straight-throughcable at the EUM instead of a crossover cable) or there is aproblem with the host or device Ethernet interface.Traffic LED The Traffic LED flashes whenever the link is transferring data.Link LED Traffic LED
6 Installation/Diagnostic ToolsAPCD-LM043-4.0 77Table 19 Console Settings6.3 EUM Configuration UtilityThe EUM can also be configured and monitored using the EUM Configuration Utility, aWindows-based graphical user interface (GUI) running on a PC. The PC connects to the CCUor EUM through the DB-9 console port, the unit Ethernet port, or from anywhere in theLMS4000 900 MHz Radio Network. The Configuration Utility and Configuration Utility UserGuide can be downloaded from the WaveRider Web site at www.waverider.com.6.4 RSSI/Tx Quality/Antenna PointingThe EUM Radio LED and the continuous Receive Signal Strength Indication (RSSI) readingprovide an indication of the level of the signal received from the CCU and an excellent tool forlocating and aligning the EUM antenna. Since the system is based on a polling MAC, there willalways be a signal to receive and monitor from the CCU.The procedure for aligning the EUM antenna, which is discussed in more detail in Positioningthe Antenna on page 111, can be summarized as follows:1. Connect the indoor antenna to the EUM and power up the EUM.2. Once the EUM is fully booted, monitor the Radio LED while moving the antennaaround the room between suitable installation sites until you find the best signal. UseTable 16 on page 75 as a guide.3. If the best location produces a Fast Flash or ON Solid Radio LED, then the receivedsignal level is good to excellent, and this is a good location to install the antenna.4. If the best location produces a Slow Flash Radio LED, then the received signal ismarginal. To attain the best possible signal below the Fast Flash LED level, turn onthe Continuous RSSI through the command-line interface, as follows:Console> radio rssiPress any key to stopRSSI RX; TX; R1; R2; R3; F;Retry%RSSI: 73 0; 0; 0; 0; 0; 0; 0%Bits per second 9600Data bits 8Parity NoneStop bits 1Flow Control None
6 Installation/Diagnostic Tools78 APCD-LM043-4.0RSSI: 73 865; 0; 0; 0; 0; 0; 0%RSSI: 73 932; 0; 0; 0; 0; 0; 0%RSSI: 73 933; 0; 0; 0; 0; 0; 0%RSSI: 74 709; 0; 0; 0; 0; 0; 0%RSSI: 73 743; 0; 0; 0; 0; 0; 0%RSSI: 74 747; 1; 0; 0; 0; 0; 0%Console>Adjust the antenna location and pointing for maximum RSSI. You may need to adjustthe antenna and then step back each time to read the RSSI, so you do not obstructthe signal from the CCU.Note that the RSSI value is only a representation and does not give a true indication ofreceive signal level. A higher RSSI value does, however, indicate a higher receivesignal level, so it can be used to indicate a best antenna placement.To calculate the true receive signal level, use the calibration table contained in thePCF file, described in Permanent Configuration File (CCU and EUM) on page 193.The EUM Configuration Utility can also be used to optimize antenna pointing anddoes provide a true reading of receive signal strength.6.5 Transfer a File to or from a CCU Using FTPYou can run a simple FTP test from the EUM to verify the performance and integrity of thecommunications between the CCU and EUM. The procedure outlined below will get afilefromthe CCU (we suggest using the backup file for the CCU application, sa1110.bak), and then(temporarily) put a file onto the CCU. In both cases, you can record the file transferperformance. WaveRider recommends doing this procedure with a screen capture, so youhave a permanent record to baseline the performance of the link, for example.Before you carry out the FTP test, you may want to baseline the performance of the computeryou are using at the EUM, by first connecting it directly to an FTP server and running an FTPtest back-to-back with the server. This back-to-back FTP test should be at least 3 Mbps, oryou may have a problem with your server or computer setup.To Transfer a File to or from a CCU Using FTP1. From the end-user computer at the EUM, bring up the Windows command lineinterface.2. At the Enter prompt, type ftp <aaa.bbb.ccc.ddd>, where <aaa.bbb.ccc.ddd> isthe CCU radio IP address.3. In the FTP window, enter the following commands to get sa1110.bak from the CCU:Connected to <aaa.bbb.ccc.ddd>.220 FTP server readyUser (<aaa.bbb.ccc.ddd>:(none)): Enter <user name> or <cr> if none set331 Password requiredPassword: Enter <pwd> or <cr> if none set230 User logged inftp> hash
6 Installation/Diagnostic ToolsAPCD-LM043-4.0 79Hash mark printing On ftp: (2048 bytes/hash mark) .ftp> binary200 Type set to I, binary modeftp> get sa1110.bak200 Port set okay150 Opening BINARY mode data connection################################################################################################################################################################################################################################226 Transfer completeftp: 463713 bytes received in 10.80Seconds 42.96Kbytes/sec.ftp>bye221 Bye...See you later.4. Enter the following commands to put the sa1110.bak file to the CCU.Connected to <aaa.bbb.ccc.ddd>.220 FTP server readyUser (<aaa.bbb.ccc.ddd>:(none)):331 Password requiredPassword:230 User logged inftp> hashHash mark printing On ftp: (2048 bytes/hash mark) .ftp> binary200 Type set to I, binary modeftp> put sa1110.bak null200 Port set okay150 Opening BINARY mode data connection##################################################################################################################################################################################################################################226 Transfer completeftp: 463713 bytes sent in 8.30Seconds 55.86Kbytes/sec.ftp>bye221 Bye...See you later.Entering null after the put command ensures the file will not be permanently stored to CCUmemory. If you inadvertently forget to enter null after the put command and save the file toCCU memory, the throughput performance of the CCU may be reduced significantly. You canremove the file using the CCU file services, available through the command line interface. Aslong as you enter null after the put command, any size file can be used.The FTP throughput should correspond to a value slightly less than the maximum allowed bythe GOS, assuming no other traffic is being carried by the CCU.6.6 Operating StatisticsThe CCU and EUM collect a wide range of IP, radio, MAC, and network layer statistics, whichcan be used for measuring system performance and troubleshooting. These statistics can beaccessed through the command line interface, outlined in Appendix C on page 163 or by usingan SNMP manager. A list of available statistics and their meanings can be found in AppendixHonpage223.
6 Installation/Diagnostic Tools80 APCD-LM043-4.06.7 SNMPThe CCU and EUM are SNMP-ready. To make use of the CCU and EUM SNMP capabilities,you must obtain the associated WaveRider MIBs from the technical support page atwww.waverider.com and install them on your SNMP manager (SNMPc, or HP OpenView, forexample).Once you have obtained and installed these MIBs, you will, from the SNMP manager, be ableto carry out the following functions for both CCUs and EUMs:• Read hardware and software configuration parameters, such as unit serial number,MAC address, regulatory domain, 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 RegistrationTables.• Read system operating statistics from the MAC layer, and the radio and Ethernetdrivers.• 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 anacceptable range.• Perform mathematical calculations on a collection of statistics and generate a warningor an alarm if the result of the calculation falls outside an acceptable range. Thiscalculation is done when a statistic, in isolation, cannot be interpreted; i.e., it can onlybe 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 oralarm when the statistic or group of statistics is starting to move towards anunacceptable limit.For more detailed information on how to use SNMP to monitor the performance of yourLMS4000 900 MHz Radio Network, refer to Monitoring the Network on page 127 andAppendix G on page 199.6.8 Field Upgrade ProcessCCU and EUM operating software can be upgraded using FTP. The upgrade mechanism isdesigned to be robust and reliable.Hash codes are generated with each new software image. The new image is FTPed with thehash code to the unit that is being upgraded, and the new software is received and written tomemory. A hash code for the new image is generated locally and compared with the hashcode that was FTPed with the new image.If the hash code comparison is unsuccessful, the downloaded image will not be written to thefile system, and a report will be returned.
6 Installation/Diagnostic ToolsAPCD-LM043-4.0 81If the hash code comparison is successful, then the existing executable software is copied asa backup (.bak file), and the newly downloaded image becomes the unit executable.The unit is automatically rebooted. If the new executable is found to be corrupt for any reason,then the unit reverts to the backed-up, older image.6.9 FTPing CCU and EUM Configuration FilesFTP enables you to transfer configuration files to CCUs and EUMs from anywhere that hasnetwork access to the LMS4000 900MHz Radio Network. FTP is a useful tool for the followingoperations:• 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 GOS.Some of the configuration files may be the same throughout the network (port filterconfiguration file, for example), and others are different for all units. Some configuration filesare loaded instantly (as soon as the file is FTPed), and some require a unit reboot to takeeffect. Table 20 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 unitreboot to take effect.Table 20 FTPing Configuration FilesNOTE: System-wide means that the configuration file in question (forexample, the port configuration file) will normally be the samethroughout your network. Configuration files, such as the routeconfiguration file, vary from CCU to CCU.Configuration File File Name CCU EUM Reboot Required? System-wide?(note 1)GOS Configuration File gosbe.cfggosbronz.cfggossilve.cfggosgold.cfgYes No YesAuthorization Configuration File authdb.cfg Yes No NoDHCP Configuration File dhcp.cfg Yes Yes YesPort Configuration File port.cfg Yes Yes Yes YesRoute Configuration File route.cfg Yes Yes NoSNTP Configuration File port.cfg Yes Yes Yes YesBasic Configuration File basic.cfg Yes Yes Yes No
6 Installation/Diagnostic Tools82 APCD-LM043-4.0CAUTION: Use FTP to transfer configuration files between likeunits only; for example, from a CCU to another CCU. (Ensure thefile is transferred using image or binary mode.) Although portfilters are used in both the CCU and EUM, there may bedifferences between the port configuration file for the CCU and theport configuration file for the EUM.One way of using this feature is to build configuration files using a spare CCU and a spareEUM, both of which have their RF outputs terminated in 50-ohm loads (or they could beconnected to each other through an attenuator), to ensure• the units are not transmitting signals that could interfere with operating CCUs andEUMs, and• the units are not damaged by transmitting into an open circuit.Once the CCU or EUM configuration files are built and saved in the spare units, they can bedownloaded to target CCUs and EUMs, as necessary. GOS configuration files are provided byWaveRider.Alternately, the configuration files could be built and saved in operating units, thendownloaded from these units to other CCUs and EUMs in the system.FTP takes the specified configuration files from CCU or EUM memory, so changes must besavedtoshowupinthedownloadedfiles.UsetheCLI<save> command to ensure they havebeen written to the file system with the proper checksum attached.
APCD-LM043-4.0 837Configuring the CCUThis section explains the following procedures and topics:•CCU and EUM Serial Number, MAC Address, and Station ID on page 84•Setting the CCU Password on page 84•Configuring the CCU RF Parameters on page 85•Configuring CCU IP Parameters on page 86•Configuring DHCP Relay on page 88•Configuring Port Filtering on page 89•Configuring the SNTP/UTC Time Clock on page 90•Configuring SNMP on page 93•Adding EUMs to the Authorization Table on page 95Before you configure the CCU• Familiarize yourself with the CLI commands, syntax and shortcuts, outlined inAppendix C on page 163. This appendix provides a complete list of the available CCUcommands, some of which are not discussed in this section.• Connect a PC to the CCU directly to the console port, or through a Telnet session.See Command-line Interface on page 76 for console settings.CAUTION: Remember to regularly enter save or commit andpress Enter, to save your configuration changes to the file system.As well, some parameters and configuration files (refer to Table 20on page 81 for details) do not take effect until you reboot the unit,specifically the RF frequency, transmit power, and IP addressing.CAUTION: After you have finished making your configurationchanges, remember to disconnect your terminal from the CCU.
7 Configuring the CCU84 APCD-LM043-4.0CAUTION: When entering IP addresses in the CCU or EUM,note that a leading ‘0’ forces the CCU or EUM operating system tointerpret the entry as octal rather than decimal. For example,pinging 10.0.2.010 actually pings 10.0.2.87.1 CCU and EUM Serial Number, MAC Address, and Station IDThe EUM/CCU 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 theproduct label, which is affixed to the case of the unit, for example:• EUM3000AB02A129E00A32•Serial Number: The serial number is the last six characters of the product ID. In theabove example, the serial number is:•E00A32•Station (CCU or EUM) ID: The station ID is derived by prefacing the last fourcharacters of the serial number with ‘60’. In the above example, the station ID, inhexadecimal notation, is:• 60:0A:32•Ethernet MAC Address: The Ethernet MAC address is derived by prefacing theserial number with the characters ‘00:90:c8’. In the above example, the Ethernet MACaddress is:• 00:90:c8:E0:0A:32•Radio MAC Address: The radio MAC address is derived by prefacing the station IDwith the characters ‘00:90:c8’. In the above example, the radio MAC address is:• 00:90:c8:60:0A:327.2 Setting the CCU PasswordTo Change the CCU Password1. 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. Forexample, “abc” is not the same as “aBc”.
7 Configuring the CCUAPCD-LM043-4.0 854. At the Verify password prompt, type the new password again.The system displays a message that your password has been successfully changed.Example:Console> passwordEnter Current Password: ********Enter New Password: ********Verify password: ********Saving new passwordPassword ChangedConsole>CAUTION: Remember to record the password. Unlocking theCCU can only be performed by contacting WaveRider TechnicalSupport.7.3 Configuring the CCU RF ParametersTo set the CCU Operating Frequency1. 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 typingreset and pressing Enter.To set the CCU Power Level1. Type radio rf <power level> and press Enter.• <power level> is the CCU transmit power level, either high (+26 dBm) orlow (+15 dBm). In most cases, the CCU power level should be set to high.NOTE: Use the HIGH power level unless your site has uniquerequirements for which the LOW power level is more appropriate.2. Type save or commit and press Enter.3. Before the new power level will take effect, you must reboot the CCU by typing resetand pressing Enter.Example:The following example• Sets the CCU operating frequency to 917 MHz,• Sets the transmit power level to high,
7 Configuring the CCU86 APCD-LM043-4.0• Saves the new settings,• Reboots the CCU so that the new parameters take effect, and• Displays the CCU RF parameters.Console>Console> radio frequency 9170Console> radio rf highConsole>Console> saveBasic Config savedPort Filter Config savedsntp cfg file savedRoute Config savedAuthorization Database savedDHCP Server Config savedConsole>Console> resetrebooting CCU ...(... Power On Self Test ...)WaveRider Communications, Inc. LMS3000Password:Console>Console> radioRF Power: HIGHRadio Frequency: 9170Console>7.4 Configuring CCU IP ParametersIn IP Network Planning on page 53, you determined the following:• CCU gateway IP address and subnet mask• CCU radio IP address and subnet mask• CCU Ethernet IP address and subnet maskTo set the CCU Ethernet IP address1. Type ip ethernet <aaa.bbb.ccc.ddd> <net mask> and press Enter.• <aaa.bbb.ccc.ddd> is the CCU Ethernet IP address.• <net mask> is the net mask.CAUTION: The CCU only accepts subnet masks using theshorthand notation; for example, it accepts ‘16’, but not‘ffff0000’or‘255.255.0.0’.2. Type save or commit and press Enter.3. Before the new CCU Ethernet IP address will take effect, you must reboot the CCU bytyping reset and pressing Enter.
7 Configuring the CCUAPCD-LM043-4.0 87To set the CCU radio IP address1. Type ip radio <aaa.bbb.ccc.ddd> <net mask> and press Enter.• <aaa.bbb.ccc.ddd> is the CCU radio IP address.• <net mask> is the net mask.2. Type save or commit and press Enter.3. Before the new CCU radio IP address will take effect, you must reboot the CCU bytyping reset and pressing EnterNOTE: The CCU Ethernet and gateway IP addresses must be on thesame subnet, as explained in LMS4000 IP Addressing on page53.To set the CCU gateway IP address1. Type ip gateway <aaa.bbb.ccc.ddd> and press Enter.• <aaa.bbb.ccc.ddd> is the CCU gateway IP address.2. Type save or commit and press Enter.Example:The following example• Sets the CCU Ethernet IP address to 10.0.4.48 / 16,• Sets the CCU radio IP address to 10.5.0.1 / 16,• Sets the CCU gateway IP address to 10.0.0.1,• Saves the new settings,• Reboots the CCU so that the new parameters take effect, and• Displays the CCU IP parameters.Console>Console> ip ethernet 10.0.4.48 16Console> ip radio 10.5.0.1 16Console> ip gateway 10.0.0.1Console>Console> saveBasic Config savedPort Filter Config savedsntp cfg file savedRoute Config savedAuthorization Database savedDHCP Server Config savedConsole>Console> resetrebooting CCU ...(... Power On Self Test ...)WaveRider Communications, Inc. LMS3000Password:Console>Console> ipEthernet IP Address: 10.0.4.48
7 Configuring the CCU88 APCD-LM043-4.0Ethernet Net Mask : ffff0000Gateway IP Address: 10.0.0.1Radio IP Address: 10.5.0.1Radio Net Mask : ffff0000Console>7.5 Configuring DHCP RelayTo configure DHCP relay• Determine the DHCP server IP address.• Enable DHCP Relay.• Add the DHCP server to the CCU.To add a DHCP server1. Type dhcp relay add <aaa.bbb.ccc.ddd> <net mask> 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.2. Repeat step 1 for any alternate DHCP servers in your network. WaveRiderrecommends that your network have at least one alternate DHCP server.3. Type save or commit and press Enter.To enable DHCP Relay1. Type dhcp enable and press Enter.2. Type save or commit and press Enter.Example:The following example• Enables DHCP relay,• Adds a DHCP server with IP address 192.168.50.1 /24,• Adds an alternate DHCP server with IP address 192.168.50.15 /24,• Saves the new settings, and• Displays the DHCP status.Console> dhcp enableConsole>Console> dhcp relay add 192.168.50.1 24Console> dhcp relay add 192.168.50.15 24Console>Console> saveBasic Config savedPort Filter Config savedsntp cfg file savedRoute Config savedAuthorization Database saved
7 Configuring the CCUAPCD-LM043-4.0 89DHCP Server Config savedConsole>Console> dhcp relayDHCP Relay Enabled:DHCP Server Table:DHCP Server Table:IP Address: 192.168.50.1Mask : ffffff00IP Address: 192.168.50.15Mask : ffffff00Console>7.6 Configuring Port FilteringTo 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 filter1. 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, orboth.2. Repeat step 1 for any other ports that you want to filter out.3. Type save or commit and press Enter.Example:The following example• Configures the CCU to filter both UDP and TCP packets on ports 137, 138, 139 and1512,• Saves the new settings, and• Displays the TCP/UDP port filters.Console> port add 137 bothConsole> port add 138 bothConsole> port add 139 bothConsole> port add 1512 bothConsole>Console> saveBasic Config savedPort Filter Config saved
7 Configuring the CCU90 APCD-LM043-4.0sntp cfg file savedRoute Config savedAuthorization Database savedDHCP Server Config savedConsole>Console> portPORT FILTERSPort Filter---------------------------------137 both138 both139 both1512 both----------------------------------Console>NOTE: The EUM factory default settings have ports 137, 138, 139, and1512 filtered out for both TCP and UDP, to prevent NetworkNeighborhood from seeing other end users’ computers.7.7 Configuring the SNTP/UTC Time ClockTo configure the SNTP/UTC clock• Add an NTP server, if the one to which you want the CCU to synchronize has notalready been added. You may want to delete the default NTP servers, to force theCCU to synchronize to the server you are adding.• Set the SNTP client resynchronization period. The factory default setting is3600seconds, and WaveRider recommends not changing this default setting.• Set the SNTP client retry period. The factory default setting is 30seconds, andWaveRider recommends not changing this default setting.• 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 server1. Type time 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.CAUTION: The CCU NTP server list must always contain thelocal host, which is 127.0.0.1. This entry is required for the casewhere the CCU loses connectivity with the other NTP servers inthe list.NOTE: Up to four NTP servers can be configured in the CCU, which isshipped from the factory configured factory-default NTP servers.To add an NTP server, you must delete one of the four defaults.
7 Configuring the CCUAPCD-LM043-4.0 91Once again, do not delete 127.0.0.1. If you inadvertently delete itfrom the list, when you use the flush command, for example, itmust be re-entered.NOTE: It is a good idea to ping the time servers from the CCU beforeadding them, to ensure you have connectivity.To set the SNTP client resynchronization timeThe SNTP client resynchronization period is the time between a successful CCUresynchronization and the next CCU resynchronization attempt, typically set to 3600s (onehour).1. Type time client resync <seconds> and press Enter.• <seconds> is the resync period in seconds.2. Type save or commit and press Enter.To set the SNTP client retry periodThe SNTP client retry period is the time between an unsuccessful resynchronization attemptand the next resynchronization attempt, typically set to 30 seconds.1. Type time client retry <seconds> and press Enter.• <seconds> is the retry period in seconds.2. Type save or commit and press Enter.To enable the SNTP client1. Type time client enable and press Enter.2. Type save or commit and press Enter.To enable SNTP relay1. Type time relay enable and press Enter.2. Type save or commit and press Enter.To display the SNTP configuration and NTP server list•Typetime print and press Enter.To display system time•Typetime and press Enter.Example:The following example• Flushes all existing NTP servers from the CCU,• Adds the local host to the NTP server list (always 127.0.0.1),
7 Configuring the CCU92 APCD-LM043-4.0• Adds a local NTP server, IP address 10.0.0.1,• Sets the resynchronization time to 3600 seconds,• Sets the retry time to 30 seconds,• Enables the SNTP client,• Enables the SNTP relay,• Saves the new entries,• Displays the SNTP configuration and NTP server list, and• Displays the system time.Example:Console> time flushConsole> time add 127.0.0.1Console> time add 10.0.0.1Console> time client resync 3600Console> time client retry 30Console> time client enableConsole> time relay enableConsole>Console> saveBasic Config savedPort Filter Config savedsntp cfg file savedRoute Config savedAuthorization Database savedDHCP Server Config savedConsole>Console> time printSNTP Client and Relay Configuration-----------------------------------RelayEnabled : YesDestination : Default Net Broadcast. (radio IF)Send time on...Boot : YesEUM Registration : YesServer (send/listen)Port : 123Unsynchronized Stratum : 15Synchronized Stratum : Received NTP Stratum +5Client (fetch only)Enabled : YesPort : 123Resync period : 3600 seconds.Retry period : 30 seconds.NTP SERVERS-----------------------------------10.0.0.1127.0.0.1-----------------------------------Console>Console> time28-FEB-2002 17:03:30Console>
7 Configuring the CCUAPCD-LM043-4.0 937.8 Configuring SNMPTo fully configure SNMP• Set the SNMP contact (name of the WISP, 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 contact1. Type snmp contact <contact> and press Enter.• <contact> is text field, often used for a contact name and phone number, aURL, or an email address, from 1-80 characters in length.2. Type save or commit and press Enter.To set the SNMP system location1. 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 community1. Type snmp community add <community> read and press Enter.• <community> is the name of the read community string. The default readcommunity string is “public”. The read community string can be from 1-32characters in length, but spaces are not allowed.2. Type save or commit and press Enter.To add an SNMP write community1. Type snmp community add <community> write and press Enter.• <community> is the name of the write community string. The default writecommunity string is “private”. The write community string can be from 1-32characters in length, but spaces are not allowed.2. Type save or commit and press Enter.To add an SNMP trap server1. 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-64characters in length.2. Type save or commit and press Enter.
7 Configuring the CCU94 APCD-LM043-4.0Example:The following example• Sets the SNMP contact as WaveRider,• Sets the SNMP location as Calgary_South,• Adds SNMP read community WaveRider_Calgary,• Adds SNMP write community WaveRider_Calgary,•AddsSNMPtrapserverWaveRider_Calgary, IP address 10.0.1.68,• Saves the new settings, and• Displays the SNMP settings.Example:Console>Console> snmp contact WaveRiderConsole> snmp location Calgary_SouthConsole> snmp community add WaveRider_Calgary readConsole> snmp community add WaveRider_Calgary writeConsole> snmp trap add 10.0.1.68 WaveRider_CalgaryConsole>Console> saveBasic Config savedPort Filter Config savedsntp cfg file savedRoute Config savedAuthorization Database savedDHCP Server Config savedConsole>Console> snmpContact: WaveRiderLocation: Calgary_SouthName: LMS3000SNMP Read Communities:WaveRider_CalgarySNMP Write Communities:WaveRider_CalgarySNMP Traps:10.0.1.68 WaveRider_CalgaryConsole>
7 Configuring the CCUAPCD-LM043-4.0 957.9 Adding EUMs to the Authorization TableTo add EUMs on the system, enter them in the CCU Authorization Table.To add an EUM to the CCU Authorization Table1. Type auth add <eum id> <gos> and press Enter.• <eum id> is the hexadecimal representation of the EUM ID• <gos> is the grade of service that you want to assign to the EUM, one of:• be (best effort),• bronze,•silver,• gold, or• denied.2. Type save or commit and press Enter.The following example•AddsEUMID60:0a:32 to the Authorization Table, and assigns it the silver gradeof service,• Saves the new settings, and• Displays the Authorization Table.Console>Console> auth add 60:0a:32 silverConsole>Console> saveBasic Config savedPort Filter Config savedsntp cfg file savedRoute Config savedAuthorization Database savedDHCP Server Config savedConsole>Console> authEUM ID GOS CLASS----------------------60:0a:32 silverDefault beTotal of 1 entriesConsole>
—This page is intentionally left blank —
APCD-LM043-4.0 978Configuring the EUMThis chapter covers the following procedures:•Setting the EUM Password on page 98•Configuring the EUM RF Parameters on page 98•Configuring EUM IP Parameters on page 99•Configuring Port Filtering on page 101•Configuring SNMP on page 102•Configuring the Customer List on page 104Before you configure the EUM• Familiarize yourself with the CLI commands, syntax and shortcuts, outlined inAppendix C on page 163.Command-line Syntax provides a complete list of theavailable EUM commands, some of which are not discussed in this section.• Connect a PC directly to the EUM console port, or through a Telnet session. SeeCommand-line Interface on page 76 for console settings.CAUTION: Remember to regularly enter save or commit andpress Enter, to save your configuration changes to memory. Aswell, some parameters will not take effect until you reboot the unit,specifically the RF frequency, transmit power and IP addressing.CAUTION: After you have finished making your configurationchanges, remember to disconnect your PC from the EUM consoleportCAUTION: When entering IP addresses in the CCU or EUM,note that a leading ‘0’ forces the CCU/EUM operating system tointerpret the entry as octal rather than decimal. For example,pinging 10.0.2.010 actually pings 10.0.2.8
8 Configuring the EUM98 APCD-LM043-4.08.1 Setting the EUM PasswordTo Change the EUM Password1. 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. Forexample, “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.Example:Console> passwordEnter Current Password: ********Enter New Password: ********Verify password: ********Saving new passwordPassword ChangedConsole>CAUTION: Remember to record the password. Unlocking theEUM can only be performed by contacting WaveRider TechnicalSupport.8.2 Configuring the EUM RF ParametersTo set the EUM Operating Frequency1. Type radio frequency <frequency> and press Enter.• <frequency> is the EUM operating frequency in tenths of a MHz. Forexample, 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 EUM by typingreset and pressing Enter.To set the EUM Power Level1. Type radio rf <power level> and press Enter.• <power level> is the EUM transmit power level, either high (+26 dBm) orlow (+15 dBm). In most cases, the EUM power level should be set to high.
8 Configuring the EUMAPCD-LM043-4.0 992. Type save or commit and press Enter.3. Before the new power level will take effect, you must reboot the EUM by typing resetand pressing Enter.Example:The following example• Sets the EUM operating frequency to 917 MHz,• Sets the transmit power level to high,• Saves the new settings,• Reboots the EUM so that they new parameters take effect, and• Displays the EUM RF parameters.Console>Console> radio frequency 9170Console> radio rf highConsole>Console> saveBasic Config savedPort Filter Config savedsntp cfg file savedConsole>Console> resetrebooting EUM ...(... Power On Self Test ...)WaveRider Communications, Inc. LMS3000Password:Console>Console> radioRF Power: HIGHRadio Frequency: 9170Console>8.3 Configuring EUM IP ParametersIn IP Network Planning on page 53, you determined the following:• CCU radio IP address and subnet mask• EUM Ethernet IP address and subnet mask• End-user PC Ethernet IP address and subnet maskTo set the EUM Ethernet IP address1. Type ip ethernet <aaa.bbb.ccc.ddd> <net mask> and press Enter.• <aaa.bbb.ccc.ddd> is the CCU Ethernet IP address.• <net mask> is the net mask.
8 Configuring the EUM100 APCD-LM043-4.0CAUTION: The EUM only accepts subnet masks using theshorthand notation; for example, it accepts ‘16’, but not‘ffff0000’or‘255.255.0.0’.2. Type save or commit and press Enter.3. Before the new EUM Ethernet IP address will take effect, you must reboot the EUM bytyping reset and pressing Enter.To set the EUM gateway IP address1. The EUM gateway is the CCU radio, so the EUM gateway IP address is the CCUradio IP address.2. Type ip gateway <aaa.bbb.ccc.ddd> and press Enter.• <aaa.bbb.ccc.ddd> is the CCU radio IP address.3. Type save or commit and press Enter.4. Before the new EUM gateway IP address will take effect, you must reboot the EUM bytyping reset and pressing Enter.Example:The following example• Sets the EUM Ethernet IP address to 10.0.4.48 / 16,• Sets the EUM gateway IP address to 10.5.0.1,• Saves the new settings,• Reboots the EUM so that the new parameters take effect, and• Displays the EUM IP parameters.Console>Console> ip ethernet 10.0.4.48 16Console> ip gateway 10.0.0.1Console>Console> saveBasic Config savedPort Filter Config savedsntp cfg file savedConsole>Console> resetrebooting EUM ...(... Power On Self Test ...)WaveRider Communications, Inc. LMS3000Password:Console> ipEthernet IP Address: 10.0.4.48Ethernet Net Mask : ffff0000Gateway IP Address: 10.0.0.1Radio IP Address: 10.5.0.1Radio Net Mask : ffff0000Console>
8 Configuring the EUMAPCD-LM043-4.0 1018.4 Configuring Port FilteringTo 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 EUM.To add a port filter1. 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, orboth.2. Type save or commit and press Enter.Example:The following example• Configures the EUM to filter both UDP and TCP packets on ports 137, 138, 139 and1512,• Saves the new settings, and• Displays the TCP/UDP port filters.Console> port add 137 bothConsole> port add 138 bothConsole> port add 139 bothConsole> port add 1512 bothConsole>Console> saveBasic Config savedPort Filter Config savedsntp cfg file savedConsole>Console> portPORT FILTERSPort Filter---------------------------------137 both138 both139 both1512 both----------------------------------Console>
8 Configuring the EUM102 APCD-LM043-4.08.5 Configuring SNMPTo fully configure SNMP• Set the SNMP contact (name of the WISP, for example).• Set the SNMP system location (physical location of the EUM, for example).• Add an SNMP read community.• Add an SNMP write community.• Add an SNMP trap server.To set the SNMP contact1. Type snmp contact <contact> and press Enter.• <contact> is a 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 location1. Type snmp location <location> and press Enter.• <location> is the location of the EUM, from 1-80 characters in length.2. Type save or commit and press Enter.To add an SNMP read community1. Type snmp community add <community> read and press Enter.• <community> is the name of the read community string. The default readcommunity string is “public”. The read community string can be from 1-32characters in length, but spaces are not allowed.2. Type save or commit and press Enter.To add an SNMP write community1. Type snmp community add <community> write and press Enter.• <community> is the name of the write community string. The default writecommunity string is “private”. The write community string can be from 1-32characters in length, but spaces are not allowed.2. Type save or commit and press Enter.To add an SNMP trap server1. 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-64characters in length.2. Type save or commit and press Enter.
8 Configuring the EUMAPCD-LM043-4.0 103Example:The following example• Sets the SNMP contact as WaveRider,• Sets the SNMP location as Calgary_South,• Adds the SNMP read community WaveRider_Calgary,• Adds the SNMP write community WaveRider_Calgary,• Adds the SNMP trap server WaveRider_Calgary, IP address 10.0.1.68,• Saves the new settings, and• Displays the SNMP settings.Example:Console>Console> snmp contact WaveRiderConsole> snmp location Calgary_SouthConsole> snmp community add WaveRider_Calgary readConsole> snmp community add WaveRider_Calgary writeConsole> snmp trap add 10.0.1.68 WaveRider_CalgaryConsole>Console> saveBasic Config savedPort Filter Config savedsntp cfg file savedConsole>Console> snmpContact: WaveRiderLocation: Calgary_SouthName: LMS3000SNMP Read Communities:WaveRider_CalgarySNMP Write Communities:WaveRider_CalgarySNMP Traps:10.0.1.68 WaveRider_CalgaryConsole>
8 Configuring the EUM104 APCD-LM043-4.08.6 Configuring the Customer ListYou can set the maximum number of customers or PCs (customer_max) that can concurrentlyaccess the radio link through the EUM, as described in Customer Table (EUM only) on page192.CAUTION: The simulation data presented in PerformanceModelling on page 42 is based on one end user (one PC) perEUM. If customer_max is set to a value greater than ‘1’, and thereis more than one end user per EUM, the throughput performanceof the radio link will be affected.TIP: When you are locally troubleshooting the EUM installation, ifcustomer_max is set to ‘1’ and you want to substitute and use aknown-working PC in place of the end-user’s PC, you will have toreset the EUM or wait for the Customer Table to time out.To set customer_max1. 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.Example:The following example•Setscustomer_max to 3,• Saves the new setting, and• Displays the value of customer_max.Console>Console> cust max 3Maximum customers: 3Console>Console> saveBasic Config savedPort Filter Config savedsntp cfg file savedConsole>Console> cust maxMaximum customers: 3Console>Console>
APCD-LM043-4.0 1059Installing the EUM9.1 Before you Start the EUM InstallationBefore you start the EUM installation, ensure the following points have been addressed:• The EUM has been configured with at least the following settings:• IP address• Subnet mask• Gateway IP address• Radio frequency• The CCU network is installed and verified.• DHCP relay is enabled at the CCU, with network access to a valid DHCP server.• The end-user PC is equipped with an Ethernet interface card, and is configured toobtain its IP address remotely, using DHCP.• The installer knows the direction from the EUM to the CCU (WISP radio site).• The installer has read this chapter.• The installer knows the EUM IP address.• The WISP has authorized the EUM at the CCU (or no communications will bepossible).Procedures are provided below for addressing situations where some of the above itemscould not be taken care of prior to the EUM installation.
9 Installing the EUM106 APCD-LM043-4.09.2 Other EUM Programming ConsiderationsAlthough the IP settings identified above are required for basic EUM operation, you shouldalso consider pre-configuring the following EUM parameters:SNMPSNMP communities can be configured in the EUM to enable remote monitoring of the EUMusing an SNMP manager. Refer to Configuring SNMP on page 102.Customer ListThe factory default configuration allows only one PC to be logically connected to the EUM atany given time. If you want to use a separate PC as an aid to installing and confirming theEUM link prior to connecting the end-user PC, then you will have to reset the EUM whenchanging between the end-user PC and the installation test PC.Port FilteringPort filtering is set in the EUM to filter out Network Neighborhood. You can edit Port filtering intheEUM,ifdesired.RefertoConfiguring Port Filtering on page 101.Output PowerIn most cases, the EUM output power should be set to HIGH.9.3 Installation OverviewInstalling the EUM involves the following procedures:1. Opening the Box on page 1072. Turning off the End-user’s Cordless Phones on page 1083. Choosing a Location for the EUM and Antenna on page 1084. Connecting the EUM Components on page 1085. Conducting a Preliminary Check of the EUM on page 1106. Positioning the Antenna on page 1117. Mounting the Antenna on page 1128. Connecting the End-user’s PC on page 1159. Obtaining Valid IP Addresses for the End-user’s PC on page 11610. Testing the Data Link on page 116
9 Installing the EUMAPCD-LM043-4.0 10711. Configuring the Browser Application on page 11912. Completing the Installation on page 12013. Baselining the Installation on page 1209.4 Installation Procedures9.4.1 Opening the BoxBefore you install the EUM components, verify that the EUM kit is complete.EUM Kit Components• EUM modem• AC/DC power supply with 2-meter DC power cable• 2-meter AC power cable• Crossover Ethernet cableAntenna Kit Components• Indoor antenna with attached 3-meter cable• Flush-mountable antenna bracket• Two antenna-mount suction cups, two drywall plugs, and two screwsRefer to Figure 37 for an illustration of each EUM component.Figure 37 EUM ComponentsNOTE: The antenna-mount suction cups, drywall plugs, and screws arenot shown in Figure 37.EUMEthernetCableAntennaBracketAntenna with attached cableAC Power CableAC/DC adapter withC power cable attached
9 Installing the EUM108 APCD-LM043-4.09.4.2 Turning off the End-user’s Cordless PhonesTurn off all cordless phones in the customer’s premises, and any other equipment that usesthe 900MHz ISM band. Once the installation is complete, turn this equipment back on.9.4.3 Choosing a Location for the EUM and AntennaThe location of the antenna has a significant effect on the performance of the EUM installation.Before you connect the EUM components, follow the guidelines provided below for choosingthe best location for the antenna and the EUM.Choosing the Best Location for the EUMThebestlocationfortheEUMis• indoors,• upright,• on a stable, flat surface, and• in a position where its air vents are unobstructed.NOTE: Avoid placing the EUM in direct sunlight or near other sources ofheat (such as an electric heater).Choosing the Best Location for the AntennaThe best location for the antenna is• indoors,• near an outside entrance or window, preferably in the location with the bestpossible path to the CCU, and• a minimum of 20cm (8in.) from personnel.9.4.4 Connecting the EUM ComponentsNow that you have chosen a suitable location, use the instructions in this section forconnecting the following components to the EUM, in the order shown in Figure 38:• Antenna• EUM AC/DC adaptor (DC cable first, then AC cable)
9 Installing the EUMAPCD-LM043-4.0 109When you have completed the above tasks, connect the EUM AC/DC adaptor to an AC powerbar or outlet.Figure 38 Connecting the EUM ComponentsTo Connect the EUM Components1. Finger-tighten the antenna cable onto the corresponding connector at the back of theEUM (refer to Step 1 in Figure 38). Do not use wrenches or pliers. Do not cross-threador over tighten.WARNING!You must connect the antenna to the modem beforeoperating the system. Failure to do so may result inpermanent equipment damage.2. Connect the AC/DC adaptor to the EUM. To do this, line up the guides in the DCpower cord connector with the notches in the power plug on the EUM and press theconnector firmly into place (refer to Figure 39).Figure 39 Connect the DC Power Cord to the EUMDenotes reserved ports. Do NOT Connect.2AC/DC AdapterPow er BarEUMStep 1Antenna CableStep 3AC Cable Step 2DC CableAntennaBracketAntennaConnectorDC PowerConnectorEthernetConnector1Press firmly at the base ofthe DC connector
9 Installing the EUM110 APCD-LM043-4.0NOTE: The DC power cable features a secure locking connector. Todisconnect the cable, pull the collar back on the connector, thencontinue pulling to detach the DC power cable from the EUM.3. Connect the AC power cord between the AC/DC adaptor and either an AC power bar(preferred) or AC outlet (Figure 40). The EUM immediately powers up since it doesnot have an ON/OFF switch.NOTE: To avoid potential damage to the EUM components in the eventof a power surge, WaveRider recommends using a power barwith surge protection (instead of connecting the AC power corddirectly to an AC outlet).Figure 40 Connect the AC Power Cord9.4.5 Conducting a Preliminary Check of the EUMCheck the LED indicators on the front of the modem to ensure that the EUM is functioningproperly.Figure 41 EUM LEDsTo Verify Proper EUM Function• Check that the Power LED is ON. It takes about 7 or 8 seconds to come on after youhave plugged in the unit.The EUM uses a custom antenna cable and connector. If youneed to extend this cable, contact WaveRider.Power Bar AC Power Cable AC/DC AdaptorNetwork LEDRadio LEDPower LEDEthernet Link LEDEthernet Traffic LEDBack Panel Front Panel
9 Installing the EUMAPCD-LM043-4.0 1119.4.6 Positioning the Antenna1. To begin with, point the antenna in the general direction of the CCU, as shown inFigure 42:Figure 42 Preliminary Orientation of the Antenna (Top View)As illustrated, for maximum signal reception, point the concave surface of the antennatoward the CCU, and ensure your body (including fingers) are not between theantenna and the CCU.2. Monitor the Radio LED, shown in Figure41onpage110and refer to Table 21.Movethe antenna until the Radio LED is flashing quickly, or is ON solidly, indicating that youhave a good to very-good radio signal. After each repositioning or reorientation of theantenna, you may have to step back from the antenna so that you are not interferingwith the received signal.Table 21 Radio LED Status Displays3. If the Radio LED is off or flashes slowly, then the antenna should be moved to a betterlocation. Keep in mind that the antenna and EUM do not have to be located in thesame room as the end-user’s PC since up to 100m (300ft.) of CAT5 data cable canconnect the EUM to the PC.4. If you cannot find an indoor antenna location that provides a solid ON or fast-flashingLED, refer to Troubleshooting on page 121.5. Once you have found a good location, you are ready to mount the antenna, asdescribed in section 9.4.7, Mounting the Antenna.Radio LED Display StatusOff No radio signal present.Slow Flash ON/OFF 1.25 times per second. The signal strengthis poor to marginal.Fast Flash ON/OFF 2.5 times per second. The signal strength isgood.Solid On The signal strength is very good.To Base Station
9 Installing the EUM112 APCD-LM043-4.09.4.7 Mounting the AntennaThe antenna bracket is designed to accommodate the RF cable and act as a strain relief.To Mount the Antenna1. Thread the attached antenna cable through the guides in the back of the antennabracket, as necessary.Figure 43 Rear View of Antenna BracketNOTE: Bending the antenna cable too sharply can degrade EUMperformance. Never allow less than a 1.25 cm (0.5 in.) bendradius. If a quarter (25-cent piece) fits into the curve, the bend isacceptable.The EUM kit includes suction cups, drywall plugs, and screws to allow a variety ofmounting options:Table 22 Antenna Mount Guidelines2. Insert the suction cups or screws into the base of the antenna bracket, then mount thebracket onto the desired surface.NOTE: If you mount your antenna bracket on a vertical surface, orientthe bracket so that the spring clip is closest to the ceiling.Mounting Method GuidelinesSuction Cups Use on flat, smooth surfaces, such as glass, plastic,laminates or metal. Remove all grease, oil, and gritbefore securing the antenna bracket with suctioncups.Drywall Plugs Use on all commercial drywall and other plastersurfaces.Screws Use on hardwood surfaces.Antenna BracketBracket GuidesAntenna Cable
9 Installing the EUMAPCD-LM043-4.0 113Figure 44 shows the location of the spring clip, suction cup holes, and screw holes onthe antenna bracket.Figure 44 Antenna Bracket ComponentsTable 23 Surface Mounting Options for the AntennaSide Mount Mount the antenna on a wall, window, window frame,or solid furniture with spring clip side closest to theceiling.Top MountHang the antenna from a ceiling or the shelf of abookcase.Bottom MountMount the antenna on solid furniture (a desk or shelf)or on a window sill.Spring ClipSuction Cup HoleScrew HoleSuction Cup HoleScrew Hole
9 Installing the EUM114 APCD-LM043-4.0WARNING!The antennas for the EUM must be fix-mounted, indoors oroutdoors, to provide a separation distance of 20cm or morefrom all persons, to satisfy RF exposure requirements. Thedistance is measured from the front of the antenna to thehuman body. WaveRider recommends installing theantenna in a location where personnel are not able to bumpinto it, obstruct the signal from the base station, or trip overantenna cables.3. Position the antenna in the bracket according to one of the configurations illustrated inFigure 45. Click and lock the antenna in place. For maximum signal reception, ensurethe concave surface of the antenna points toward the WISP antenna and the trough ofthe inset wave points towards the floor.Figure 45 Mounting the Antenna in the BracketNOTE: The location, position, and orientation of the antenna affects therobustness of the Internet connection. Pointing the antenna atbuildings or other obstacles often impedes communications, butsome surfaces may provide desirable signal bounce. For optimalreception, try various positions before fix-mounting your antenna.4. Once the antenna is permanently mounted, re-align it for best signal.- Concave surface pointingtowards WISP antenna- Trough of inset wave pointingtowards floor.Inset wave
9 Installing the EUMAPCD-LM043-4.0 1159.4.8 Connecting the End-user’s PC1. Connect the end-user’s PC, shown in Figure 46, by attaching the crossover Ethernetcable that is included with the kit between the Ethernet port on the end-user’scomputer and the Ethernet port on the EUM.Figure 46 Connecting the End-user’s PC2. Check the Ethernet LEDs on the back panel of the EUM to ensure the Ethernetconnection between the EUM and the end-user’s PC is active. Refer to Table 24 for anexplanation of the Ethernet LED status displays.Table 24 Ethernet LED Status Displays3. When attempting to send data to, or receive data from, the Internet, check theEthernet Traffic LED to ensure data transmission is taking place. This LED flashes asdata traffic passes between the end-user’s PC and the EUM. The network LED on thefront of the EUM also flashes and is more accessible than the Traffic LED on the rearof the EUM.Ethernet LED StatusEthernet Link LED This LED is lit when there is a correct connection tothe computer, and both ends are powered ON.Ethernet Traffic LED Flashes when data passes through the Ethernetconnection in either direction.Denotes reserved ports. Do NOT Connect.omputer2AC/DC AdapterPow er BarEUMStep 1Antenna CableStep 4Ethernet CableStep 3AC Cable Step 2DC CableAntennaBracketAntennaConnectorDC PowerConnectorEthernetConnector441
9 Installing the EUM116 APCD-LM043-4.09.4.9 Obtaining Valid IP Addresses for the End-user’s PC1. To obtain IP addresses for the end-user’s PC, including the PC IP address, GatewayIP address, and DNS server address, the PC must request an update from the DHCPserver. This procedure varies depending on which version of Windows operatingsystem is running on the end-user’s PC, but a general method is outlined as follows:For Windows 95, 98:• Using Windows utility winipcfg, select Start >Run,type<winipcfg> inthe command line, and press Enter.•Fromthewinipcfg menu, select Release All,thenRenew All.• Using DOS, select Start >Run,typecmd or command (the exact processmay vary, so consult your operating system manual)•Usingthe<ipconfig> command set, Renew all adaptors.2. If no error messages are returned, the WISP network has successfully provided an IPaddress to the end-user’s PC. You can confirm the success by checking the assignedIP addresses. If the assigned Gateway IP address corresponds to the EUM GatewayIP address, then the operation was successful.3. If a valid IP address cannot be achieved, see Troubleshooting on page 121.9.4.10 Testing the Data LinkThe fact that the IP address was successfully obtained indicates that the data link from the PCto the WISP's network is functioning properly. WaveRider recommends more thorough testingof the EUM-to-CCU data link, as outlined below. These tests can also be used to troubleshootsimple problems if DHCP access is not available.There are several tools available for testing the quality of the link between the end-user PCand the WISP network. The most important tool is the ping utility, which is available in theCCU, EUM, and the end-user PC. The ping command can be used to progressively test thedata link, as follows:•To Test the Data Link from the End-user’s PC to the EUM, on page 116•Testing the Data Link from the End-user’s PC to the Network, on page 118•Testing the Data Link from the End-user’s PC to the Internet, on page 119To Test the Data Link from the End-user’s PC to the EUM1. Ping the EUM’s IP address from the end-user’s PC, as follows:• Open a DOS window in the end-user’s PC.• At the command prompt, type ping <aaa.bbb.ccc.ddd>, where<aaa.bbb.ccc.ddd> is the IP address of the EUM and press Enter.2. If there is no response, check the following:• PC IP address settings.• Ethernet crossover cable between the EUM and the end-user’s PC, to ensurethat the pins have not been damaged and that the pin-outs are consistent withthose shown in General Troubleshooting Information,onpage151.3. If there is a response, but with errors, check the Ethernet crossover cable.
9 Installing the EUMAPCD-LM043-4.0 117To illustrate data link testing between the PC and the EUM, consider the sample configurationshown in Figure 47.Figure 47 Sample Configuration — Testing the Data LinkUsing the sample configuration shown in Figure 47, confirm the connection between the end-user’s PC and the EUM as demonstrated below:This is what successful ping from the end-user’s PC to the EUM looks like:C:\>ping 10.5.4.117Pinging 10.5.4.117 with 32 bytes of data:Reply from 10.5.4.117: bytes=32 time<10ms TTL=64Reply from 10.5.4.117: bytes=32 time<10ms TTL=64Reply from 10.5.4.117: bytes=32 time<10ms TTL=64Reply from 10.5.4.117: bytes=32 time<10ms TTL=64Ping statistics for 10.5.4.117:Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:Minimum = 0ms, Maximum = 0ms, Average = 0msC:\>This is what an unsuccessful ping from the end-user’s PC to the EUM looks like:C:\>ping 10.5.4.116Pinging 10.5.4.116 with 32 bytes of data:Request timed out.Request timed out.Request timed out.Request timed out.Ethernet crossovercableEUM AntennaGateway RouterInternetRadioLinkEnd-user's PremisesEnd-user's PCIP Address 10.5.6.117Net Mask 16Gateway IP 10.5.0.1EUM3000IP Address 10.5.4.117Net Mask 16Gateway IP 10.5.0.1CCU3000Radio IP Address 10.5.0.1Net Mask 16
9 Installing the EUM118 APCD-LM043-4.0Ping statistics for 10.5.4.116:Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),Approximate round trip times in milli-seconds:Minimum = 0ms, Maximum = 0ms, Average = 0msC:\>Ifyouarenotableto<ping> the EUM from the PC, go to Troubleshooting on page 121.Testing the Data Link from the End-user’s PC to the NetworkOnce the connection from the PC to the EUM is confirmed, ping the EUM gateway addressfrom a PC DOS window. Ping with short packets first to confirm function, and then with longpackets (1472 byte packets) to confirm performance. Errors observed on pings with longpackets indicate a high error rate on the channel, caused by low signal levels or interference.To Ping a CCU with the maximum packet size1. Open a DOS window.2. At the command prompt, type ping <aaa.bbb.ccc.ddd> -t -L 1472, where<aaa.bbb.ccc.ddd> is the CCU radio IP address and press Enter.3. Press Ctrl+cto end the test.NOTE: If this test fails, but pinging the CCU with the default packet sizesucceeds, then the connection is working but is not operating atmaximum capacity, possibly due to poor antenna placement ororientation.This following example uses the sample configuration shown in Figure 47:Pinging the CCU from the end-user’s PC (with maximum packet size):C:\>ping 10.5.0.1 -t -l 1472Pinging 10.5.0.1 with 1472 bytes of data:Reply from 10.5.0.1: bytes=1472 time=40ms TTL=64Reply from 10.5.0.1: bytes=1472 time=81ms TTL=64Reply from 10.5.0.1: bytes=1472 time=80ms TTL=64Reply from 10.5.0.1: bytes=1472 time=40ms TTL=64Reply from 10.5.0.1: bytes=1472 time=60ms TTL=64Reply from 10.5.0.1: bytes=1472 time=80ms TTL=64Reply from 10.5.0.1: bytes=1472 time=40ms TTL=64Reply from 10.5.0.1: bytes=1472 time=110ms TTL=64Ping statistics for 10.5.0.1:Packets: Sent = 8, Received = 8, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:Minimum = 40ms, Maximum = 110ms, Average = 66msControl-C^CC:\>More advanced tests and troubleshooting procedures are included in Troubleshooting on page135.
9 Installing the EUMAPCD-LM043-4.0 119Testing the Data Link from the End-user’s PC to the InternetUse the following test to determine whether the end-user’s PC can communicate with theInternet.Pinging an Internet site from the PC using the site’s IP address:C:\>ping 207.23.175.75Pinging 207.23.175.75 with 32 bytes of data:Reply from 207.23.175.75: bytes=32 time=90ms TTL=113Reply from 207.23.175.75: bytes=32 time=80ms TTL=113Reply from 207.23.175.75: bytes=32 time=80ms TTL=113Reply from 207.23.175.75: bytes=32 time=70ms TTL=113Ping statistics for 207.23.175.75:Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:Minimum = 70ms, Maximum = 90ms, Average = 80msC:\>Use the following test to verify that the DNS server IP address is correctly configured in theend-user’s PC and is operating properly:Pinging an Internet site from the PC, using the site’s domain name:C:\>ping www.waverider.comPinging waverider.com [207.23.175.75] with 32 bytes of data:Reply from 207.23.175.75: bytes=32 time=70ms TTL=113Reply from 207.23.175.75: bytes=32 time=90ms TTL=113Reply from 207.23.175.75: bytes=32 time=60ms TTL=113Reply from 207.23.175.75: bytes=32 time=50ms TTL=113Ping statistics for 207.23.175.75:Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:Minimum = 50ms, Maximum = 90ms, Average = 67msC:\>9.4.11 Configuring the Browser ApplicationFollow the manufacturer's instructions for configuring the end-user’s browser, so that itcorrectly uses the PC Ethernet interface. Once you have done this:1. Launch the browser2. Confirm access to sites of interest.3. Monitor the access speed using a test site, such as http://speed-test.net
9 Installing the EUM120 APCD-LM043-4.09.4.12 Completing the Installation1. Configure the remaining PC applications, as required.2. Re-activate the end-user’s cordless phones, and any other 900MHz ISM-bandequipment that was turned off at the beginning of the installation. Note the followingpoints:• Cordless phones operating in the 900MHz ISM band can disrupt service tothe EUM if precautions are not taken.• Browse to http://speed-test.net, and turn on the cordless phones in sequence,while monitoring the downlink throughput. Since there is naturally a widevariation in the downlink speed, for reasons more associated with the networkthan with the performance of the LMS4000 wireless service, repeat the testsseveral times to confirm whether or not the end user’s cordless phones aregoing to affect the EUM performance.• If the cordless phones do affect the performance of the EUM, move thecordless phone base station to a location as far from the antenna as possible.Instruct the end user to avoid using the cordless handset in the proximity ofthe antenna, particularly when the EUM is being used.9.4.13 Baselining the InstallationOnce you have completed the installation, WaveRider recommends recording the followinginformation:• EUM IP addresses• EUM radio settings• RSSI readings• Tx retry rate readings (displayed with the RSSI readings)If you have problems with the EUM at a later date, you can compare the latest site settingsand RSSI readings with the original settings in the site installation record.You can record and save this information in several ways:• using the WaveRider Configuration Utility. Through the Configuration Utility, you canalso upload and store the EUM’s complete configuration file. You can also do thislocally, through a serial connection to the EUM, or remotely through a Telnet session.• through the EUM command-line interface locally, using:• HyperTerminal, with the PC connected to the EUM console port.• a DOS Telnet session, through the EUM Ethernet connection.• through the EUM command-line interface remotely, using:• a DOS Telnet session, over the wireless link between the network and theEUM.Record the information from the following session, and store it to a file.EUM Console>EUM Console> ipEthernet/USB IP Address: 10.5.4.117Ethernet/USB Net Mask : ffff0000
9 Installing the EUMAPCD-LM043-4.0 121Gateway IP Address: 10.5.0.1Console>Console> radioRF Power: HIGHRadio Frequency: 9170Console>Console> ra rssiPress any key to stopRSSI RX; TX; R1; R2; R3; F;Retry%RSSI: 44 0; 0; 0; 0; 0; 0; 0%RSSI: 60 712; 0; 0; 0; 0; 0; 0%RSSI: 59 706; 0; 0; 0; 0; 0; 0%RSSI: 62 812; 0; 0; 0; 0; 0; 0%RSSI: 58 819; 0; 0; 0; 0; 0; 0%RSSI: 60 809; 0; 0; 0; 0; 0; 0%RSSI: 45 829; 0; 0; 0; 0; 0; 0%RSSI: 61 834; 0; 0; 0; 0; 0; 0%RSSI: 60 818; 0; 0; 0; 0; 0; 0%EUM Console>9.4.14 TroubleshootingQ: I cannot receive a good signal, regardless of where I place the antenna. What shouldI do?A: The threshold receive signal level for the fast flashing Radio LED is -80dBm, whichprovides an operating margin of up to 9 dB. In some cases, an installation will not require thismuch margin, and the unit will function at a lower signal level. If the LED is flashing slowly, theamount of receive signal can be determined using the EUM CLI command <ra rssi> or theEUM Configuration Utility. If the signal is above -84dBm, it may be adequate, and detailedtests should be carried out to determine the link robustness under these signal conditions.If it is not possible to obtain an adequate signal level from the indoor antenna, an outdoorantenna may be required. Installation of an outdoor antenna requires the services of aqualified Professional Installer, proficient in the use and installation of ISM-band radioequipment, and knowledgeable about local codes related to the installation of outdoorantennas. Once an appropriate antenna is installed, and an adequate signal level is achieved,the installation can proceed as outlined above.Q: I have found a great location for the antenna but unfortunately, this location is a fairdistance from the end-user’s PC. As a result, I am unable to connect the antenna, EUM,and the end-user’s PC using the cables included in the EUM kit. How can I resolve thisproblem?A: To connect the antenna cable, place the EUM closer to the antenna; then, use a longerEthernet cable to connect the EUM to your PC. Longer Ethernet cables are readily availablefrom local electronics shops.NOTE: The use of a longer Ethernet cable has no effect on networkperformance if you use a good quality cable and the cable lengthis less than 100 meters.Q: I have adequate radio signal strength, but cannot access the network. What should Ido?
9 Installing the EUM122 APCD-LM043-4.0A: There are two conditions that might prevent or compromise Internet access by the end-userthrough the EUM, even when the network is operating properly and the radio signal strength isadequate:Improper PC configurationIf the PC IP address set is incorrect, then communications between the PC and theEUM will not be possible. If the DHCP function does not provide a valid IP address tothe PC, then the PC IP address will have to be entered manually. More advancedtroubleshooting may be required to find out why DHCP is not working properly in thiscase. As well, if the Ethernet card in the PC is not properly configured, you will not beable to communicate through the EUM.A quick, simple test for confirming that there is a radio link between the EUM and theWISP network, which does not rely on having the correct configuration in the end-user’s PC, is to ping the CCU (or some other destination in the WISP network) throughthe EUM console port, using HyperTerminal and the EUM command-line interface. Ifthis test is successful, then the problem is either the PC connection to the EUM, or thePC configuration.InterferenceIf there is a strong radio interferer in the vicinity of the end-user’s premises or, morespecifically, to the EUM installation, this may impact the ability of the EUM tocommunicate over the radio link, either preventing communications, or at least,causing a higher than expected error rate.If the interference originates from inside the end-user’s premises, then it can becontrolled by relocating either the EUM antenna or the source of the interference.If the interference originates from outside the end-user’s premises, the problem maybe addressed by relocating the indoor antenna or, if an outdoor antenna is beingused, by carefully siting the antenna to provide adequate isolation from the interferer.Without the use of special test equipment, such as a spectrum analyzer, interferenceproblems may be difficult to positively diagnose and resolve.
9 Installing the EUMAPCD-LM043-4.0 123Q: DHCP is not available on the network. Is there anything else I can do?A: DHCP is a tool that allows you to re-use IP addresses and simplifies the procedure forconfiguring the end-user PC. If DHCP is not available, the WISP must provide the installer withthe following IP addresses for the end-user’s PC:• PC IP address• Subnet mask• Gateway IP address• DNS IP addressThese addresses can be directly entered into the end user’s PC through the operating system.Once these addresses are entered and activated (which may require re-booting the PC), theinstallation process can proceed as outlined above. To confirm the data link to the WISPnetwork, use the tests outlined in Testing the Data Link on page 116, or configure and activatethe end-user’s browser, as shown in Configuring the Browser Application on page 119.Q: The EUM keeps shutting off automatically. How can I prevent this?A: The EUM may be overheating due to inadequate ventilation. Lightly touch the modem case.If the case is hot, the solution may be to find a new location for the EUM, where it can standupright and away from other objects that may be blocking or interfering with its ventilation. Ifthese measures have no effect, and the EUM is still running hot, unplug it and return it to theWISP for a replacement.Similarly, if the EUM is operating in an environment below 10°C, the EUM may repeatedly shutdown and restart. Moving the EUM to a warmer location resolves this problem.
—This page is intentionally left blank —
APCD-LM043-4.0 12510 Maintaining the NetworkThe LMS4000 900MHz radio network requires virtually no maintenance. This chapterdescribes what you need to do to maintain the CCU and EUM operating environments.The CCU and EUM must be kept in a temperature-controlled and dust-free environment, asdescribed under the following headings:•Maintaining Temperature and Humidity on page 125•Cleaning the Equipment on page 125•Checking the CCU Shelf Cooling Fans on page 126Maintaining Temperature and HumidityMake sure the CCU and EUM sites meet the environmental requirements outlined in Table 25.Table 25 Temperature and Humidity RequirementsCleaning the EquipmentWARNING!Make sure you follow ESD precautions when you touch andclean CCU and EUM components.Equipment OperatingTemperature Non-condensingRelative Humidity StorageTemperatureCCU 0° to +50°C 5% to 95% -40° to +70°CEUM 10° to +40°C 5% to 95% -40° to +70°C
10 Maintaining the Network126 APCD-LM043-4.0When cleaning CCU and EUM components:• Use dry, static-free cloths to wipe dust from the devices.• Make sure you do not disconnect any cables or wires when cleaning.Checking the CCU Shelf Cooling FansWARNING!Exercise caution when you are in close proximity to the CCUShelf cooling fans. Disconnect AC power to the fans prior tohandling.Verify that the cooling fans in the CCU Shelf are rotating freely and at a high speed whenconnected to the power supply to ensure proper cooling of the CCUs.
APCD-LM043-4.0 12711 Monitoring the NetworkAlthough there are a large number of detailed statistics available for the various data handlingapplications in the CCU (refer to Appendix H on page 223 for a complete list), there are only afew that are key for monitoring system performance on an on-going basis. These statistics aredescribed in detail in the material below.11.1 CCU Transmit StatisticsAs described in MAC Layer (Polling MAC) on page 36, the MAC continuously transmits pollsto the EUMs. These polls can contain specific user data directed to the EUM or the PCconnected to the EUM, control data directed to the EUM, broadcast data directed to all EUMs,or empty polls, which containing no information data.In an ideal system, all data transmitted would be received error free by the EUMs, and no re-transmissions would be required. In the real world, unfortunately, low signal conditions,interferers, system engineering problems, and equipment malfunction can result in the need toretransmit data over the radio link. These retransmissions, which are key to maintaining dataintegrity for the end user, come with the trade-off of reduced network capacity.Statistics reported by the CCU can assist in identifying when retransmissions are occurringand at what rate they are occurring. They can also be used to troubleshoot the cause ofretransmissions.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 fortransmissiontoanotherEUM,• MAC control data,• broadcast data, and• data retransmitted because it was not acknowledged by an EUM and is assumed lost.
11 Monitoring the Network128 APCD-LM043-4.0Examining this statistic in more detail, txPayloads includes• Tx Data Payloads which, in turn, includes• data coming from the Ethernet port of the CCU (either end-user data oroperator monitoring [SNMP] data),• data coming from EUM-originated data payloads that have been “switched” tothe CCU radio port (for transmission to other EUMs), and• broadcast data to all EUMs(TxPayloadsBCast).NOTE: The Tx Data Payloads described above are both transmittedduring specific EUM poll periods.• Tx Ctrl Payloads — Control data generated in the CCU, and used to configure, orrequest status from, the EUMs. Tx Ctrl Payloads are transmitted during specific EUMpoll periods.• Retransmitted data — Data that is not acknowledged after a transmission and isassumed to be lost or corrupted.Understanding the relationship between these values helps you monitor the integrity of a CCUradio environment.All non-broadcast payloads (hence, “directed” payloads) are explicitly acknowledged by theEUMs. For these payloads, the result of a transmission during an EUM poll cycle will be one ofthe following:Table 26 Possible Transmission OutcomesTo put these values in perspective, the following samples have been taken from a live CCU,using the <stats mac> CLI command:Result of Transmission Reported StatisticPayload is delivered to an EUM andacknowledged on the first poll. txPayloads1OkPayload is transmitted twice, after which anacknowledgement is received. txPayloads2OkPayload is transmitted three times, afterwhich an acknowledgement is received. txPayloads3OkPayload is transmitted four times, afterwhich an acknowledgement is received. rxPayloads4OkNo acknowledgement received after fourtransmissions, and the payload isdiscarded.txPayloadsFailRetryPayload is not transmitted at all. txPayloadsFailAssocDeleted
11 Monitoring the NetworkAPCD-LM043-4.0 129Table 27 Typical CCU Transmit StatisticsThe objective of the first level analysis of this data is to determine the relative amount of radiotraffic resulting from retransmissions. Ideally, the percentage would be 0. In practice, localengineering 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 wheninterpreting and using results which are based on these statistics. For example, sincebroadcast payloads are not acknowledged, the retry data is not relevant to these payloads,and they have to be netted out of the total. In addition, the txPayloadsFailAssocDeletedpayloads are not actually transmitted. So they also have to be netted out of the total. Thecalculations to do this are shown below:Using this data, the following calculations can be made:Total number of desired payloads = A + B = 68,691Net Payloads sent via EUM polls (see note) =A + B - C - I = 67,790 + 901 - 445 - 11 = 68,235This same result can be calculated as follows:Net Payloads sent via EUM polls (see note) = D + E + F + G + H = 68,236NOTE: Due to real-time issues (at any given time, some packets arebeing processed or queued), the numbers often differ by thesmall number of packets that are in queues.The percentage of payloads that are delivered on the first transmission= 66,001 / 68,235 = 97%Statistic SampleAtx Data Payloads 67,790Btx Ctrl Payloads 901CtxPayloadsBCast 445DtxPayloads1Ok 66,001EtxPayloads2Ok 1,761FtxPayloads3Ok 281GtxPayloads4Ok 91HtxPayloadsFailRetry 102ItxPayloadsFailAssocDeleted 11
11 Monitoring the Network130 APCD-LM043-4.0Similarly, the percentage of payloads not delivered on the first transmission, but delivered onthe second transmission= 1,761 / (68,235 - 66,001) = 78%It is generally a good indication if most payloads that fail on the first try are then successfulwith only one retry.The percentage of payloads that are not able to be delivered= 102 / 68,680 = 0.15%A very low undeliverable payload rate implies that user service has a high level of integrity,and that the radio link is not significantly impacting higher-level TCP/IP applications.The impact of the retransmissions can be calculated by looking at the total number oftransmissions requiring acknowledgments:=1xD+2xE+3xF+4xG+4xH=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 canbe readily calculated as desired payloads transmitted/actual payloads transmitted, or:(Tx Data Payloads +Tx Ctrl Payloads -txPayloadsBCast -txPayloadsFailAssocDeleted)/(TxPayloads -txPayloadsBCast)= (67,790 + 901 - 445 - 11) / (71,583 - 445) = 68,235 / 71,138 = 96%which suggests that 4% of the radio traffic is used to retransmit packets, which is referred to inthis document as the Retransmission Rate.From an operational point of view, it is important to keep the number of retransmissions to aminimum since they reduce the total air time available and the total network throughput.Although these calculations can appear tedious since all of the referenced statistics areavailable through MIBs, SNMP management tools, such as SNMPc can directly collect thestatistics, calculate the above metric, and track and report its value over time.
11 Monitoring the NetworkAPCD-LM043-4.0 13111.2 CCU Receive StatisticsSimilar to the case for CCU transmit statistics, there are several key CCU receive statisticsthat you can use to monitor on-going performance of the CCU radio network. When the CCUsends a directed poll to an EUM, it expects to get an acknowledgement. The following resultshave been taken from a live CCU using the <stats mac> command:Table 28 Typical CCU Receive StatisticFrom these statistics:Total number of replies expected = A + B + D = 434,882and the receive packet error rate which, as noted in Table 28, includes EUM receive errors anderrors associated with random access attempts, is given byRxPER= (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 re-use is implemented is rxPktsNoMatch. A high value of rxPktsNoMatch indicates that the twoCCU radio environments are interfering with each other.The statistic rxPktsDuplicate measures the number of times the EUM sends the same packetof information more than once. A high value of rxPktsDuplicate indicates that theacknowledgements from the CCU are not being properly received at the EUM.Statistic Description SampleArxPktsDirected An acknowledgement from the EUMthat is correctly received by the CCU. 409,730BrxPktsHCRCFail Packet received from an EUM, with acorrupted header.Note: This statistic also includesrandom access packets that havebeen received with corrupted headers.2,464CrxPktsFCS Fail Packet received from an EUM, with acorrupted payload. 192DreplyOrRssiTimeouts No reply.Note: This statistic also includes EUMreceive errors, by virtue of the fact thatif an EUM does not receive a poll fromthe CCU, for any reason, then it willnot reply to the CCU.22,688
11 Monitoring the Network132 APCD-LM043-4.011.3 EUM Statistics MonitoringIn general, the statistics collected at the EUM are the same as those collected at the CCU;however, there are some differences in meaning (see Appendix H). More significantly, ofcourse, is that the EUM statistics are unique to the EUM, as opposed to the CCU statistics,which are a collective of the CCU and all EUM interactions.11.3.1 EUM Transmit StatisticsThe relationships of the key EUM statistics are the same as those for the CCU. In the case ofthe EUM, however, no broadcast packets are transmitted, and the value oftxPayloadsFailAssocDeleted will always be 0. The key EUM transmit statistics, with samplevalues, are shown below.Table 29 EUM Transmit StatisticsThe same combinations used for the CCU case are also included in the table for clarity.Statistic Description Sample TotalPayload TotalPacketsAtxPayloads Number of payloads transmitted. 56,293 - -B Tx Data Payloads Number of data payloads to betransmitted (user data) 44,718 - -C Tx Control Payloads Number of control payloads tobe transmitted. 2- -D txPayloads1Ok Payload is delivered to the EUMand acknowledged on the firstpoll. 36,889 36,889 x1 36,889E txPayloads2Ok Payload is transmitted twice,then acknowledge received. 5,216 5,216 x2 10,432F txPayloads3Ok Payload is transmitted threetimes, then acknowledgereceived. 1,489 1,489 x3 4,467G txPayloads4Ok Payload is transmitted fourtimes, then acknowledgereceived. 553 553 x4 2,212H txPayloadsFailRetry No acknowledge received afterfour transmissions, packetdiscarded. 573 573 x4 2,292Sum 44,720 56,292
11 Monitoring the NetworkAPCD-LM043-4.0 133As with the CCU transmit statistics, the following sample calculations can be made using thesample data from Table 29:Total number of desired payloads = B + C = 44,718 + 2 = 44,720This is also equal to:(txPayloads1Ok +txPayloads2Ok +txPayloads3Ok + txPayloads 4Ok +txPayloadsFailRetry) = (36,889 + 5,216 + 1,489 + 553 + 573) = 44,720NOTE: Due to real-time issues (the fact that at any given time, somepackets are being processed or queued), the numbers frequentlydiffer by the number of packets that are in queues.NOTE: In the case of the EUM, most payloads are sent in response todirected polls; however, a small number of payloads are sent inresponse to random access polls.The percentage of payloads that are delivered on the first transmission=txPayloads1Ok / (B + C) = 36,889 / 44,720 = 82.5%Similarly, the percentage of payloads that are not delivered on the first transmission but aredelivered on the second transmission=txPayloads2Ok / (44,720 - 36,889) = 5,216 / 7,831 = 11.7%The percentage of payloads that are not able to be delivered= 573 / 44,720 = 1.3%Since there are no broadcast or control payloads, the calculation of the Retransmission Rateis fairly straightforward:Retransmission Rate = (1 - desired payloads/actual payloads) x 100=(1-tx Data Payloads /txPayloads) x 100= (1 - 44,718 / 56,293) x 100= 21%11.3.2 EUM Receive StatisticsPerhaps the most important receive statistic is the Receive Signal Strength Indicator (RSSI),which gives a relative indicator of receive signal strength. Using the calibration table in thePCF table, described in Permanent Configuration File (CCU and EUM) on page 193, RSSIcan be used to determine the true receive signal level, in dBm. It is important to monitor thisstatistic.NOTE: Since the EUM can receive packets that are destined for otherEUMs, the EUM receive statistics are not as useful as the CCUreceive statistics. They are useful when the EUM is the only EUMthat is active, which is seldom the case after more than one EUMhave been activated.
11 Monitoring the Network134 APCD-LM043-4.0The statistic rxPktsDuplicate measures the number of times the CCU sends the same packetof information more than one time. A high value of rxPktsDuplicate indicates that theacknowledgements from the EUM are not being properly received at the CCU.11.3.3 User DataThe actual user data is recorded by the statistics Rx Data Payloads and Tx Data Payloads.These statistics could be viewed as billable data and allow the operator to monitor actualusage at the EUM level.
APCD-LM043-4.0 13512 TroubleshootingTroubleshooting an LMS4000 900 MHz radio network problem is an iterative process. First ofall, you need to isolate the general location of the problem, then isolate the problem, andfinally, determine the root cause of the problem. There are five general areas to which anLMS4000 operational problem might be isolated:•End-user’sPC• EUM environment• CCU radio environment• Operator’s network upstream from the CCU (between the CCU and the Internet)• InternetThe key to efficient troubleshooting is first verifying that the network and equipment upstreamfrom the CCU is operational. This upstream network and equipment includes• data path from the CCU to the gateway router,• DNS servers, and• DHCP server, if DHCP is enabled.NOTE: The troubleshooting procedures presented in this section aremost effective if the upstream path and equipment have alreadybeen verified.Problems can generally be divided between those that affect all EUMs on a CCU, and thosethat affect only one EUM.A. If all EUMs are affected• Verify that the path from the gateway router to the Internet is up.• Verify that you can ping the CCU Ethernet port from the gateway router.• If these tests are successful, go to CCU Troubleshooting on page 145.
12 Troubleshooting136 APCD-LM043-4.0B. If only one EUM is affected:• Verify that you can ping from the gateway router to other EUMs on the same CCU. Ifyou cannot, go to A. above.• Ifthistestissuccessful,gotoEUM Troubleshooting on page 136.12.1 EUM TroubleshootingThe following EUM troubleshooting process can be used at the time of the initial EUMinstallation or during follow-up service visits. In the latter case, troubleshooting focusses onfactors that might have changed, using the setup file record from the initial install as abaseline.In general, the following items will be verified as part of EUM troubleshooting:• CCU configuration, particularly as it relates to the affected EUM• EUM configuration• Radio link integrity• User PC configurationAll of these items can be checked out from the end-user’s PC, but it may be better to use aseparate, known PC for the tests outlined in the troubleshooting tables. Then, you can repeatthe tests with the end-user’s PC to make sure the end-user’s PC is configured and workingproperly.When a customer reports a problem, it is usually related to a failure of the browser or emailapplication on the PC to successfully access the Internet, or it is a report of degraded serviceor slowdown. From the problem report, troubleshooting proceeds as follows:1. To avoid a service call to the end-user’s premises, try to isolate the problem remotely,using the procedures outlined in Table30onpage138(for problems where theservice is not available) and in Table 31 on page 139 (for problems where the serviceis degraded).2. If you are unable to troubleshoot the problem remotely and must visit the end-user’spremises, use the procedures outlined in Table32onpage140(service not available)and in Table 33 on page 142 (service degraded).Two test utilities are commonly used throughout the troubleshooting process. The term<ipconfig> generically refers to a utility that verifies IP addresses in the PC, and to forcechanges when DHCP is enabled. To force a change through DHCP, use a release and renewcommand sequence. The IP set in the end-user’s PC refers to the following addresses:• PC IP address• PC subnet mask• Gateway IP address (same as the CCU IP address)• DNS server IP address (usually two addresses are provided)
12 TroubleshootingAPCD-LM043-4.0 137To enable the <ipconfig> capability, you can use the Windows utility, <winipcfg> inWindows 95 and 98 operating systems, and the DOS utility in newer Windows operatingsystems.The <ping> command is used to test data links. A successful short ping test confirmsconnectivity but may not indicate link error rates that would cause failures in tests with longerpackets. A test performed with a long-packet ping provides a better indication of the channelerror rate. If long pings are available, use them in conjunction with the short pings. If longpings are not available, ignore the instructions in the following tables that specify long pings.Instead, if the channel is operational, a PC application such as a browser, can be used togenerate longer packets and, during the transmission of these longer packets, the retry ratecan be monitored. Note that the CCU only originate (using the CLI through the console port)short pings.EUM-specific tests can be carried out through the CLI, or using the EUM Configuration Utility.To verify key EUM settings, use the CLI <ip> and <radio> commands.
138 APCD-LM043-4.012 TroubleshootingTable 30 Remote Troubleshooting — EUM (Service Not Available)What should I do? What is a good result? What does a goodresult mean? What if I do not get a good result?AConfirm EUM status Telnet to the CCU andgo to the CLI prompt.Telnet is successful. Go to Test B. Check the upstream data path andequipment, or go to CCU Troubleshooting onpage 145.BVerify the CCUconfiguration for theaffected EUMCheck the AuthorizationTable in the CCU.Affected EUM ID is notDENIED.The affected EUM isenabled and can transmitand receive data. Go toTest C.If the EUM is DENIED, change its GOS to BE,BRONZE, SILVER or GOLD. Retry Test B.If the affected EUM does not appear in theAuthorization Table, but the default GOS isBE, Bronze, Silver or Gold, then the EUM willactually be enabled, and Test B is a PASS.Go to Test C.CCheck the radio link tothe EUM<ping> the affectedEUM from the CCU. Uselong and short pings.No ping failures or time-outs.The radio link to the EUMis likely good. Go to TestD.If there is no ping response, the radio link maybe down. Go to the local troubleshootingprocedures outlined in Table 32 on page 140.If you are having partial ping failures, theradio link may be poor. Go to Test D.DTelnet to the affectedEUM and, through theCLI prompt, enter <rarssi>.The RSSI value shouldcorrespond to theoriginal installed value. Asignal > -80dBm shouldprovide robust service,with a low transmissionerror rate. Refer toPermanent ConfigurationFile (CCU and EUM) onpage 193 to find out howto convert from RSSI toreceived signal level indBm.The radio link isconfirmed. The reportedproblem will likely be aPC configuration issue.You may be able toresolve this issue withthe end-user on thephone. Alternately, go tothe local troubleshootingprocess outlined in Table32 on page 140.Go to the local troubleshooting processoutlined in Table 32 on page 140.
APCD-LM043-4.0 13912 TroubleshootingTable 31 Remote Troubleshooting — EUM (Service Degraded)What should I do? What is a good result? What does a goodresult mean? What if I do not get a good result?ACheck the gateway toEUM linkFrom the Ethernet side ofthe CCU, <ping> theCCU with short and longpings.No failures or time-outs. The link to the CCU isOK.GotoTestB.Problem is upstream from the CCU, and theupstream data path and equipment need tobe checked out.BFrom the Ethernet side ofthe CCU, <ping> theaffected EUM with shortand long pings.No failures or time-outs. The EUM radio link isprobably OK. Check thePC configuration. Go toTest C.The EUM radio link is poor or down. Go toTest C.CConfirm the status of theaffected EUMTelnet to the CCU andgo to the CLI prompt.Telnet is successful. Go to Test D. Check the radio link to the CCU.DCheck the AuthorizationTable in the CCU. Affected EUM ID is notDENIED.There has been nochange in the subscribedservice level. Go to E.Add the EUM to the Authorization Table, withits subscribed grade of service, or correct theEUM’s GOS setting. Retry Test D.EFrom the CCU, <ping>the affected EUM.No failures or time-outs. Re-confirms Test B. The CCU-to-EUM radio link is suspect ordown. If you get no response, go to the localtroubleshooting procedures outlined in Table32 on page 140. If you get errors, go to Test F.FTelnet to the affectedEUM, go to CLI prompt,and enter <ra rssi>.The RSSI value shouldcorrespond to theoriginal installed value. Areceive signal > -80dBmshould provide robustservice, and atransmission error rateless than 10%. Refer toMonitoring the Networkon page 127.The radio link isconfirmed. The reportedproblem is most likely aPC configuration issue.You may be able toresolve this issue withthe end-user on thephone. Alternately, go toTable 32 on page 140.If the RSSI is too low, go to Table 32 on page140. If the transmission error rate isinconsistent because there are too fewpackets being transmitted, ask the end-userto launch a browser and monitor the errorrate. If the error rate is too high, go to Test Gand/or go to local troubleshooting proceduresoutlined in Table 32 on page 140.
140 APCD-LM043-4.012 TroubleshootingGTIP Record key EUMstatistics from <statsmac> (see Table27onpage 129 and Table 28on page 131), clear thestatistics, then reviewand record the statisticsafter traffic has beenpassed for 10 or 15seconds.The retransmission rate,defined in Monitoring theNetwork on page 127, islow.The slowdown is likelynot due to the radionetwork. Check the PC.Go to the local troubleshooting proceduresoutlined in Table 32 on page 140.Table 32 Local Troubleshooting — EUM (Service Not Available)What should I do? What is a good result? What does a goodresult mean? What if I do not get a good result?TIP When using a substitute PC as part of the troubleshooting procedure, be sure to clear the Customer Table in the EUM, to allow thesubstitute PC to be recognized by the EUM. This can be done through the CLI command, by entering <cust flush>,orbyresetting the EUM.AVerify settings Connect a PC to theEUM console port with aserial cable. Bring up theCLI prompt, and type<ip> <cr>, then<radio> <cr>.The values displayedshould be the operator-assigned parameters.Go to Test B. Input the proper configuration. Check to see ifthe reported problem has been resolved. If ithas not been resolved, go to Test B.BVerify the radio link Check the receivedsignal level.The center LED on theEUM is flashing rapidly,or ON solidly.The received signal is>-80dBm, which shouldprovide enough marginfor stable performance.Go to Test C.• If there is no LED activity, confirm theradio frequency.• Use the RSSI or Configuration Utility tomeasure the received signal strength.• Check the antenna connections.• Improve antenna pointing and/orlocation.Table 31 Remote Troubleshooting — EUM (Service Degraded)What should I do? What is a good result? What does a goodresult mean? What if I do not get a good result?
APCD-LM043-4.0 14112 TroubleshootingCVerify the data link Check the EthernetLEDs on the PC andEUM Ethernetconnectors.The Link LED is ON solidgreen, and the TrafficLED is flashingoccasionally with traffic.Cable connection isgood, and the Ethernetinterfaces are active. Goto Test D.• Check the type of cable. The cablebetween the EUM and PC should be acrossover cable.• Check connector pins. Make sure noneof the pins have been damaged.• Check for a pinched cable.• Check for possible hardware problemsat the PC.• Change to a different PC, with a shortercable.• If none of the above resolves theproblem, you might suspect a defectiveEUM.DVerify the logical dataconnection between thePC and EUMThrough the DOScommand line on theend-user’s PC, <ping>the EUM with short andlong packets.No failures or time-outs. Confirms the physicaland logical connection tothe EUM, and basic IPaddressing. Go to TestE.• Verify the IP address in the PC, byentering <ipconfig> in the DOScommand line. If the IP is bad, enter theappropriate IP set (PC’s IP, gateway IP,and DNS IP).• If using DHCP, renew through<ipconfig>.• If DHCP fails, enter a valid IP set forremaining tests• Change to a different PC, using shortercable.• If none of the above resolve the reportedproblem, you might suspect a defectiveEUM.EThrough the DOScommand line on theend-user’s PC, <ping>the CCU with short andlong packets.No failures or time-outs. Confirms datatransmission over theradio link, and completesthe 900MHz network-specific troubleshooting.Go to Test F.If no pings are successful:• Verify the EUM ID in the CCUAuthorization Table.• Reboot the EUM.• Reboot the PC.• Refer to If You Have an Interferer onpage 149.If pings are successful but have errors:• Refer to If You Have an Interferer onpage 149.Table 32 Local Troubleshooting — EUM (Service Not Available)What should I do? What is a good result? What does a goodresult mean? What if I do not get a good result?
142 APCD-LM043-4.012 TroubleshootingFVerify the dataconnection to theInternetThrough the DOScommand line, <ping>207.23.175.75(WaveRider web site)No failures or time-outs. The data connection tothe Internet is OK. Go toTest G.Verify network status. It is likely that all EUMsare affected.GThrough the DOScommand line, <ping>www.waverider.com.No failures or time-outs. DNS server access(required for browser andemail applications) isworking properly, and sois the EUM installation.The DNS server is unavailable.HIf DHCP failed in Test D Through the DOScommand line, <ping>the DHCP serveraddress.No failures or time-outs. The DHCP server ispresent. Go to Test I.The DHCP server is not available.IEnable auto IP mode inthe PC. Renew IP.Valid IP set assigned. DHCP is operational. Goto Test J.Suspect the PC configuration. Verify DHCPoperation at a different site.JThrough the DOScommand line, <ping>www.waverider.com.No failures or time-outs. Confirms full Internetavailability through thenetwork. EUMinstallation is workingOK.Suspect the PC IP set, or DHCP or DNSserver operation.Table 32 Local Troubleshooting — EUM (Service Not Available)What should I do? What is a good result? What does a goodresult mean? What if I do not get a good result?Table 33 Local Troubleshooting — EUM (Service Degraded)What should I do? What is a good result? What does a goodresult mean? What if I do not get a good result?AVerify the radio link. Check the receivedsignal level.The center LED on theEUM is flashing rapidly,or ON solidly.Received signal isgreater than -80 dBm,which should provideenough margin for stableperformance. Go to B.• If there is no LED activity, confirm theradio frequency.• Use the RSSI or Configuration Utility tomeasure signal strength.• Check antenna connections.• Improve antenna pointing and/orlocation.
APCD-LM043-4.0 14312 TroubleshootingBVerify the logical dataconnection between thePC and EUM.Through the DOScommand line, <ping>the EUM with short andlong packets.No failures or time-outs. Confirms physical andlogical connection to theEUM, and basic IPaddressing. Go to C.• Verify the IP address in the PC, byentering <ipconfig> in the DOScommand line. If the IP is bad, enter theappropriate IP set (PC’s IP, gateway IP,and DNS IP).• If using DHCP, renew through<ipconfig>.• If DHCP fails, enter valid IP set forremaining tests• Change to different PC, using shortercable.• If none of the above, suspect defectiveEUM.CThrough the DOScommand line, <ping>the CCU with short andlong packets.No failures or time-outs. Confirms datatransmission over theradio link, and completesthe 900 MHz network-specific troubleshooting.Go to E.If no pings are successful:• Verify the EUM ID in the CCUAuthorization Table.• Reboot the EUM.• Reboot the PC.• Refer to procedure <In the Case ofInterference>.If pings are successful but have errors:• Refer to procedure <In the Case ofInterference>.DVerify data transferacross the radio link.Through the DOScommand line, FTP tothe CCU, and follow theinstructions set out inTransfer a File to or froma CCU Using FTP onpage 78 (bin, hash, get<file>).The FTP transfer ratevaries depending onsystem loading;however, you should seea resultant transfer ratecorresponding to theassigned GOS for theEUM.Confirms datatransmission over theradio link, and completesthe 900 MHz network-specific troubleshooting.Go to E.If the data transfer rate is poor, or if youobserved severe stalling of the transferprogression (minor stalls can be expectedand are a normal part of the polling process).Table 33 Local Troubleshooting — EUM (Service Degraded)What should I do? What is a good result? What does a goodresult mean? What if I do not get a good result?
144 APCD-LM043-4.012 TroubleshootingEOpen browser to http://speed-test.net,runthedownload and uploadtests.Throughput in bothdirections should beconsistent with thesubscribed service level,with an allowance for theoverall traffic level on theCCU.Customer complaint mayberelatedtothecustomer’s perception ofthe service levelfluctuating with trafficload variation. Go to F.Repeat the test with a different PC and datacable.FThrough the consoleport, enter CLI command<ra rssi>. Repeat thelong upload test fromhttp://speed-test.net.Tx error rate less than10%.Slowdown is likely at thenetwork level.Refer to procedure <In the Case ofInterference>.GTIP If you are still unclear whether the slowdown is local or at the network level, use FTP test between the PC and CCU, and comparewith the speed-test.net result in D. If the results are similar, then the slowdown is likely local. If the FTP between the PC and CCU isfaster, then the slowdown is likely at the network level.Table 33 Local Troubleshooting — EUM (Service Degraded)What should I do? What is a good result? What does a goodresult mean? What if I do not get a good result?
12 TroubleshootingAPCD-LM043-4.0 14512.2 CCU TroubleshootingCCU troubleshooting can be broken down into several areas, based on the working history ofthe CCU, the nature of the reported problem, and the extent of the reported problem. For thepurpose of this troubleshooting section, it is assumed that the CCU has been installedaccording to the guidelines provided by WaveRider and EUMs have been successfullydeployed and operated. Subsequent problems can then be divided into the followingcategories:• Unable to add new EUMs• New EUMs cannot get service• Adding new EUMs causes degraded performance to existing EUMs• Complaints of degraded performance• Customer complaints of slow throughput• Service outages• All customers have no service• Some customers have no service• Key Statistics (refer to Monitoring the Network on page 127) indicate an increase inretransmitted and/or lost packetsThe possible causes for these problems can be identified as follows:• Configuration error at CCU• System congestion• Impacts EUMs depending on their assigned GOS level• Presence of an interferer• Impacting the CCU• Impacting all or most EUMs in the sector• Hardware failure of the CCU system (CCU, power, antenna, etc.)• Impacts all EUMs in the sectorRegardless of the extent of the reported problem, there exist remote and local tests that canbe used to isolate the cause.Since there are so many possible entry levels to a troubleshooting procedure, the followingtroubleshooting guides are intended to provide suggested tests that can be carried out as partof the troubleshooting process. Some tests may not be required in all scenarios and goodjudgement should be used when carrying out the tests.The remote CCU tests outlined in Table34onpage146are generally useful as a starting pointfor all CCU troubleshooting. These tests should be carried out prior to performing the localtests outlined in Table35onpage147, keeping in mind the remote tests can be carried outlocally using the serial port to access the CLI command set.
146 APCD-LM043-4.012 Troubleshooting.Table 34 Remote Troubleshooting — CCUWhat should I do? What is a good result? What does a goodresult mean? What if I do not get a good result?AConfirm the network linkto the CCUTelnet to the CCU. Access to the CCU isavailable.Verifies network accessconnectivity down to theCCU level.Either the network connection to the CCU isdown, or the CCU Ethernet port is notresponding. Confirm the network connectionto the CCU site. If OK, go to the local CCUtests outlined in Table 35 on page 147.BConfirm EUM status atthe CCUEnter the CLI, type<air>.All EUMs for the sectorshould be listed.All EUMs listed havesuccessfullycommunicated with theCCU during the last 12-hour period. The timesince their lasttransmission is listed inthe table. Go to Test C.If only some EUMs are missing, they may beturned off, or may be unable to communicatewith the CCU. Verify that all EUMs areassigned a usable GOS in the AuthorizationTable (enter <auth> in the CLI). If no EUMsare present, all EUMs have been unable tocommunicate with the CCU. Reset the CCU.If no EUMs register, suspect CCU systemfailure, or high level of interference. Go to thelocal CCU tests outlined in Table 35 on page147.CCheck for systemcongestionIn the CLI, type <rameter>.No indication ofviolations indicatingsystem congestion. NoteaveIPS readings for allGOS levels.No violations means allusers are receivingsubscribed levels ofservice. AveIPS valuesthat are significantlylonger than minimum forthe specific GOS mayindicate users are seeing“degraded” service withrespect to their maximumburst rate. This canhappen during busyhour, depending onsystem traffic load andengineering.Violations indicate system congestion - toomany users at too high a service level. Youneed to analyze your user traffic levels.AveIPS canbeusedtomonitorfluctuationinuser-perceived throughput. Slowdowns, evenwithin the bounds of subscribed service, mayresult in customer complaints.
APCD-LM043-4.0 14712 Troubleshooting.DCheck for Key Statisticsdegradationin the CLI, type <statsmac>.Key Statistics, describedin Monitoring theNetwork on page 127,should meet generalcriteria listed, and/or besimilar to past values.No change in theinterference environmentindicated.An increase in retry rates is potentially anindication of an interferer at the CCU. If thenumber of EUMs is small, a specific EUM-linkproblem could be degrading this statistic, sofurther analysis may be warranted at the EUMlink level.Table 34 Remote Troubleshooting — CCUWhat should I do? What is a good result? What does a goodresult mean? What if I do not get a good result?Table 35 Local Troubleshooting — CCUWhat should I do? What is a good result? What does a goodresult mean? What if I do not get a good result?ACheck the CCU Confirm power. Power LED illuminated. CCU has adequatepowering. Go to Test B.Check main AC power to CCU AC-DCadaptor. Check AC-DC adaptor power output.Correct or replace, as required.BAccess the CLI throughthe serial port.-- -CConfirm basicconfiguration (<ip>,<ra>, <auth>)Configuration should beas originally configured.Go to Test D. Correct the configuration and retest. If systemis now functional, review personnel accesspermission to CCU.DPing CCU Ethernet port. Successful pingresponse.Ethernet port circuitryOK.GotoTestE.Suspect CCU hardware.EPing the network. Successful pingresponse.Confirms networkconnection to CCU. Goto Test F.Check cabling, upstream equipment.FPing the CCU radio port. Successful pingresponse.Radio control circuitry isOK.GotoTestG.Suspect CCU hardware.GConfirm links to EUMs Type <air>.All/mostEUMsareregistered.EUMs can communicatewith CCU. Go to Test H.Go to Test K. Verify RF system at the CCU. Ifa captive EUM is available, see TIP I.HPing selected EUMs. EUMs respond withouterrors.Basic CCU network isgood. Go to TIP I.Go to Test K. If a captive EUM is available,see TIP I.
148 APCD-LM043-4.012 TroubleshootingITIP Having a captive EUM at the CCU site can be helpful to isolate problems. With asimple antenna, the captive EUM can be accessed from the CCU to confirm thecommunications capability of the CCU, and the EUM can roughly verify the outputsignal levels from the CCU.If a captive EUM cannot be accessed, evenwhen set up in a high-signal receive area,replace the CCU. If access is still notpossible, replace the CCU antenna systemwith a “test antenna”, located 15’ or so fromthe captive EUM, and repeat Tests G and H.JTIP If only EUMs with high signal levels (i.e., typically those close to the CCU) can beaccessed, suspect an interferer.Go to If You Have an Interferer on page 149.KConfirm CCU RFnetwork output power.Check with other EUMsites and confirm that thereceive signal level is perthe original installedvalue.Receive RF signal is peroriginal installed value.CCU radio networkoutput is normal. Go toTest P.Go to Test L.LVerify RF network andcomponents.Visually inspect all RFconnections.Connectors look OK. Go to Test M. Repair connectors.MUse an RF sweepgenerator test to look fordiscontinuities in the RFpath.No discontinuitiesshown.RF path looks OK. Go toTest N.RF path component is faulty. Repair/replace,as appropriate.NUse a spectrum analyzerto verify the RF systemand CCU output.The CCU transmit powerat the CCU radio portshould be approximately26dBm, using aresolution bandwidth >5MHz.CCU output is OK. Go toTest O.Replace the CCU.OMeasure the CCUreceive power with a testantenna on the spectrumanalyzer. Adjust thereading based on thedistance from the CCUantenna.RF path is OK. Go toTest P.Recheck RF path components.PGo to if you have aninterferer.Table 35 Local Troubleshooting — CCUWhat should I do? What is a good result? What does a goodresult mean? What if I do not get a good result?
12 TroubleshootingAPCD-LM043-4.0 14912.3 If You Have an InterfererThe presence of an interferer can cause a variety of performance problems in the radionetwork. These problems can be quite difficult to positively identify and track down. Typically,the presence of an interferer is first identified by eliminating other potential causes of theobserved symptoms.Interferer problems can be inconsistent, in both the significance of the effect, as well as theduration, since interferers are frequently intermittent.There are two general types of interferers that have to be addressed — those that share theISM band with the LMS4000 900MHz Radio Network, and those that operate adjacent to theISM band.The interferers within the ISM band almost always affect individual EUMs since they aregenerally associated with in-home devices such as cordless phones, baby monitors, and otherconsumer-oriented ISM band devices. However, there are other outdoor 900 MHz ISM bandproducts. These are typically frequency-hopping spread-spectrum devices that can cover awide area; therefore, they could impact EUMs and/or the CCU directly. For these devices, it isunlikely that all EUMs would be impacted unless the CCU is directly affected.Interferers from outside the ISM band include paging signals, which are high power,narrowband transmissions between 929 and 931MHz (above the 900MHz ISM band), andcellular transmissions that extend up to 896MHz (just below the 900MHz ISM band). For CCUradio networks working at the limits of the ISM band, these out-of-band signals can result in aserious desensitization of the CCU receiver. The RF Planning section of this User Guideexplains how the frequency planning process must take these signals into account whenplanning the CCU radio network and how filters are used at the CCU to provide enhancedisolation. If, however, the transmitter sites for these signals are moved after the original CCUdesign, then the impact can be immediate and significant, frequently requiring that the CCUfrequency plan be adjusted. Fortunately, once this problem is diagnosed, changing thefrequency plan is relatively straightforward.In addition to ensuring that the CCU is not impacted by these out-of-band emissions, EUMscan also be impacted if the antenna field of view of the EUMs looks directly at thesetransmitters. Again, diligent planning is essential.Interference troubleshooting is divided into two main categories:• EUM-specific (only one EUM is affected, or a group of EUMs in a small area),suggesting an interferer near these EUMs.• Many, or all EUMS are affected, suggesting an interferer that is most likely impactingthe CCU directly.As mentioned earlier, the typical impact of an interferer is to effectively increase the noise levelat the CCU or EUM, which causes an increased receive error rate. Modems in a CCU networkthat operate at a lower signal level are more vulnerable to interference, and this provides a toolthat can be used to diagnose the problem. For example, if EUMs that normally operate atlower signal levels are seeing higher error levels than those that operate at higher signallevels, then you would suspect an interferer affecting the CCU.Measuring the level of interference is difficult, unless you have access to a spectrum analyzerand are prepared to shut down the system. In severe cases this may be required as a last
12 Troubleshooting150 APCD-LM043-4.0resort. Otherwise, the level and location of the interferer has to be deduced frommeasurements available at the CCU and EUM. Several of these measurements arereferenced in the preceding Troubleshooting sections.Some further clarifications and guidelines are listed here:• A typical data transmission between the CCU and the EUM requires informationpackets to go both ways. For example, a payload transmitted from the EUM to theCCU will be acknowledged with an ACK packet returned from the CCU. If thetransmission fails, it is difficult to determine directly which direction failed (for aninterferer, the failure will occur at the end of the link which is closer to the interferer).• With the exception of the received signal level, the CCU radio environment is thesame for all EUMs. If transmissions from one EUM are unreliable, but transmissionsfrom another EUM with similar received signal strength at the CCU are not, then thelikely problem will be found at the affected EUM. If all EUMs of similar signal strengthare similarly affected, then the problem will likely be found at the CCU.• If communications exist, the quality of the transmission can be measured by thetransmit retry rate, as indicated in previous sections. This is a powerful diagnostic tool.• If communications exist, longer packets will suffer more failures (retransmissions)than shorter packets, which can cause the customer to see some applications workbetter than others (e.g. browsing may be less impacted than FTP file transfers). Theping test, using variable length ping packets, can be a useful device to quantify theextent of this problem.• If communications from an EUM to the CCU are not possible, the ARP table can beused to divide the link into two sections. A ping from the EUM to the CCU that isreceived by the CCU will cause the EUM to be entered into the CCU ARP table. Evenif the response from the CCU is lost, verifying the entry in the CCU ARP table willconfirm the EUM-to-CCU link and suggest that the EUM is in a relatively severeinterference environment.• If the receive signal level at the EUM is above -80dBm, and the EUM has the correctfrequency and valid IP addresses, then if the EUM cannot ping the CCU, it is highlylikely there is an interferer in the vicinity of the EUM.• A local interferer at the EUM location can usually be managed through properplacement of the antenna, and if the interferer is in the same residence, judiciousplacement of the interfering device.• For comprehensive diagnosis of an EUM, and determining mitigating actions in severecases, a spectrum analyzer may be required.
12 TroubleshootingAPCD-LM043-4.0 15112.4 General Troubleshooting InformationTable 36 provides troubleshooting tips related to general problems that you may be havingwith trying to operate over the network.Network Address TranslationIf, from an affected host (PC, EUM, or CCU), you find that you can ping the gateway routerinside or outside addresses, but cannot ping beyond the gateway router, then you may want tohave a look at the operation of the router’s network address translation (NAT). In this case,bring up the router NAT translation table, according to the manufacturer’s instructions, andcheck that the host IP address is being properly translated in accordance with the NATscheme that you have implemented. If it is not being properly translated, then you must resetor clear the NAT translation table in accordance with the manufacturer’s instructions.Table 36 General Network ProblemsSymptom Potential CausesARP table mismatches Network devices maintain an ARP table that matches an IPaddress with a MAC address. Every network device has aunique MAC address. If one network device is replaced byanother, and the new device uses the same IP address asthe old one, all devices on the network will have an incorrectARP table. All the network device ARP tables still have the IPaddress pointing to the MAC address of the old device. Thisis a temporary problem, as ARP tables are regularly flushedand rebuilt. However, when swapping devices, this couldcause a situation where the new device cannot be pinged oraccessed until the ARP tables of other devices on thenetwork have adapted to the new configuration. This couldtake from a few seconds to a few minutes.IP address conflict If two network devices have the same IP address, immediateand critical network problems result. Often, both devices shutdown.Network router not configured correctlyfor new networkWhen adding a wireless network to an existing Ethernetnetwork, some routing changes may be necessary to themain gateway router of the Ethernet network.10 to 100 Mbps mismatch betweennetworking equipmentCCUs and EUMs are forced to 10 Mbps on the Ethernet side.
12 Troubleshooting152 APCD-LM043-4.0Ethernet Cable WiringTable 37 provides troubleshooting tips related to problems that you may be having withEthernet cables.Correct termination of an Ethernet cable is fundamental to preventing problems introduced bycrosstalk or noise. If a cable is incorrectly terminated, packet loss and network problems mayoccur.An Ethernet cable consists of eight wires, four of which are solid colored, and four of whichhave white stripes (called tracers). Each solid-color wire and its corresponding color-stripedwire are twisted together and considered a pair (e.g. the solid-blue and white-blue wiresconstitute one pair). The twisting of the wires prevents cross talk and the introduction of noise.Only two of the four available pairs are actually used in data communications — one pair isused for transmitting data and another pair for receiving data. If you look at the bottom of theEthernet plug (the metal contacts are visible from the bottom). The transmit pair uses pins 1and 2, and the receive pair uses pins 3 and 6 (see Figure 48).Figure 48 Ethernet Plug (Bottom View)For a standard straight-through Ethernet cable, both plugs should be set up as follows:• Pin1=WhiteGreen•Pin2=Green• Pin3=WhiteOrangeTable 37 Ethernet Cabling ProblemsSymptom Potential Causes• Unable to ping across a singlepiece of Ethernet cable.• Lose large-sized ping packetsacrossasinglepieceofEthernet cable.• Ethernet cable wired wrong.• Ethernet cable RJ-45 ends terminated incorrectlyor badly.• Wrong cable type (crossover or straight-through)used.• Ethernet cable longer than 100 meters.• Ethernet cable may be damaged, crimped, orbent sharply.1 2345678
12 TroubleshootingAPCD-LM043-4.0 153•Pin4=Blue• Pin5=WhiteBlue• Pin 6 = Orange• Pin7=WhiteBrown•Pin8=BrownFor a crossover cable, one plug should be assembled as a standard and the other plug asfollows:• Pin1=WhiteOrange• Pin 2 = Orange• Pin3=WhiteGreen•Pin4=Blue• Pin5=WhiteBlue•Pin6=Green• Pin7=WhiteBrown•Pin8=Brown
—This page is intentionally left blank —
APCD-LM043-4.0 15513 Specialized ApplicationsThe advanced capabilities of the LMS4000 900 MHz radio network modems can support avariety of special applications.13.1 EUM Thin RouteIn some cases, it may be cost-effective to use an EUM to extend the reach of the LMS4000900 MHz radio network to small numbers of outlying EUMs, as shown in Figure 49.Figure 49 Using an EUM for Thin RouteCCU3000AntennaCCU3000AntennaStandardEUM3000Thin RouteEUM3000HubStandardEUM3000StandardEUM3000End-user PCEnd-user PCEnd-user PCEnd-user PCRadioChannel "A"RadioChannel "B"
13 Specialized Applications156 APCD-LM043-4.0In this EUM thin-route case, the traffic on the radio channel “b” network traverses two airlinks— the first from the users’ EUMs to the CCU on radio channel “b”, then the second from thethin-route EUM to the CCU on radio channel “a”. This situation reduces the availablethroughput of the CCU on radio channel “a” by the amount of the traffic on the radio channel“b” network. Depending on the number of EUMs in the radio channel “b” network and theirsubscribed grades of service, the thin-route EUM may need to be assigned a special grade ofservice, which can be obtained from WaveRider.13.2 EUM BackhaulIn some cases, it may be cost-effective to use an EUM as the backhaul link as an alternative toa separate wired or wireless link to the CCU, as is illustrated in Figure 50.Figure 50 Using an EUM for BackhaulIn the EUM backhaul case, nearly all traffic traverses two airlinks — the first from the users’EUMs to the CCU then the second from the CCU to the backhaul EUM. This situation reducesthe available throughput of the CCU by half. To ensure that the backhaul EUM gets half thepolls and that no packets are dropped in the transmit queues, a special GOS class definitionstill need to be used for the backhaul EUM, and for no others. This special GOS class isavailable, as an option, from WaveRider.Backhaul EUM3000 CCU3000AntennaEUM3000EUM3000Data path from end-usermodem to network
APCD-LM043-4.0 157Appendix A SpecificationsThis appendix lists the following specifications for the LMS4000 900 MHz Radio Network,specifically the technical specifications for the CCU and EUM, configured for operation in theFCC/IC RF regulatory domain:•Radio Specifications on page 157•Ethernet Interface Specifications on page 158•Power Supply Specifications on page 158•Environmental Specifications on page 158Table 38 Radio SpecificationsMaximum Number of Operational CCUs andOrthogonal Channels 3Maximum Number of EUMs per CCU 300The maximum number of subscribers islimited by the terms of the user licensepurchased from WaveRider.Minimum Channel Center Frequency 905 MHzMaximum Channel Center Frequency 925 MHzChannel Bandwidth 5.5 MHzCenter Frequency Spacing Increment 0.2 MHz (101 channels possible)Minimum Separation Between Co-locatedChannels 6.6 MHzMaximum Co-located Channels 3
158 APCD-LM043-4.0Table 39 Ethernet Interface SpecificationsTable 40 Power Supply SpecificationsTable 41 Environmental SpecificationsCo-located Channel Set CenterFrequencies (standard) 905 MHz, 915 MHz, 925 MHzNote: Other frequencies can be used,depending on site-specific considerations.Call WaveRider for more information.Modulation Scheme Based on DSSS (Direct-Sequence SpreadSpectrum) signals, modulated with CCK(Complementary Code Keying), and Barker-coded BPSK (Binary Phase Shift Keying)and QPSK (Quaternary Phase Shift Keying)Receiver Sensitivity for BER < 10-5 Better than -86 dBmMaximum Over-the-Air, Raw Data Rate 2.75 MbpsMaximum Output Power +26 dBmCCU Physical Interface 10BaseT (Ethernet)EUM Physical Interface 10BaseT (Ethernet)AC Input 110/230 ± 15% VAC, single phaseAC Input Frequency 50/60 ± 3 HzMaximum Input Current 0.2 AOperating Temperature 0°C to +50°C, indoor CCU10°C to +40°C, indoor EUM(10%-80% RH non-condensing)Storage Temperature -40°C to +70°C
APCD-LM043-4.0 159Appendix B Factory ConfigurationThis appendix identifies the factory configuration settings for the CCU and EUM.Table 42 CCU Factory ConfigurationParameter Default ConfigurationConsole Prompt The default console prompt is the station(CCU) ID.Deregistration Count 8DHCP Relay DisabledEthernet IP Address 192.168.10.250Ethernet Netmask 24Gateway IP Address 192.168.10.1GOS Definitions BE (0 - 384 kbps)Bronze (0 - 1024 kbps)Silver (128 - 256 kbps)Gold (256 - 512 kbps)Denied (0 kbps)Note: The above data rates are based onFTP transfers from a single EUM, usingmaximum-sized packets)GOS Default (Authorization Table) BE (Best Effort)Maximum Associations 75Password <cr>Port Filters 137 (both)138 (both)139 (both)1512 (both)Radio Frequency 9050 (905.0MHz)
160 APCD-LM043-4.0Radio IP Address 192.168.11.1Radio Netmask 24Registration Server IP Address 0.0.0.0Registration Server Netmask 0SNMP Contact WaveRider Communications Inc.SNMP Location www.waverider.comSNMP Read Communities publicSNMP Write Communities privateSNMP Traps None enteredSNTP Client Enabled NoSNTP Client Resynchronization Period 3600 secondsSNTP Client Retry Period 30 secondsSNTP Relay Enabled YesSNTP Relay Send Time on Boot YesSNTP Relay Send Time on EUMRegistration YesSNTP Servers 132.246.168.148 (time.nrc.ca)140.162.8.3 (ntp.cmr.gov)136.159.2.1 (ntp.cpsc.ucalgary.ca)192.5.5.250 (clock.isc.org)127.0.0.1 (local host)Transmit Power HIGHTable 43 EUM Factory ConfigurationParameter Default ConfigurationConsole Prompt The default console prompt is the station(EUM) ID.Ethernet IP Address 192.168.10.250Ethernet Netmask 24Gateway IP Address 192.168.10.1Maximum Bridge Table Size 256Maximum Number of Customers 1Password <cr>Table 42 CCU Factory ConfigurationParameter Default Configuration
APCD-LM043-4.0 161.Port Filters 137 (both)138 (both)139 (both)1512 (both)Radio Frequency 9050 (905.0MHz)SNMP Contact WaveRider Communications Ltd.SNMP Location www.waverider.comSNMP Read Communities publicSNMP Write Communities privateSNMP Traps None enteredSNTP Client (listen only) Enabled YesTransmit Power HIGHTable 43 EUM Factory ConfigurationParameter Default Configuration
—This page is intentionally left blank —
APCD-LM043-4.0 163Appendix C Command-Line SyntaxThis appendix describes the various LMS4000 commands and syntax, and consists of thefollowing sections:•Command-line Syntax Conventions and Shortcuts on page 163•CCU Command-line Syntax on page 165•EUM Command-line Syntax on page 174NOTE: The help command on the CCU or EUM may display additionalcommands that are not listed in the following tables. WaveRiderrecommends that you use only commands listed in this Appendix.CAUTION: When entering IP addresses in the CCU or EUM,note that a leading ‘0’ forces the CCU/EUM operating system tointerpret the entry as octal rather than decimal. For example,pinging 10.0.2.010 actually pings 10.0.2.8To Access the Command-line Interface• In the WaveRider Configuration Utility, click the Windows menu and select UseTerminal Screen.Command-line Syntax Conventions and ShortcutsTable 44 shows the typographical conventions used to represent command-line syntax. Table45 provides a list of shortcuts and methods to get help on commands. To execute a command,type the command and press Enter.
164 APCD-LM043-4.0Table 44 Command-Line Syntax ConventionsTable 45 Command-Line Shortcuts and Getting HelpConvention Use ExamplesmonospacedfontIndicates that you must type the text. ip routeEnter Bold face type indicates a keyboard keypress. A plus sign (+) indicates keycombinations. For example, for Ctrl+U,press and hold down the Ctrl key, thenpress the Ukey.EnterEscCtrl+U<variable> Specifies a variable name or otherinformation that you must replace with areal name or value.ip address ethernet<ip_address>boldcharactersIndicates the shortcut characters for acommand. ipethernet canalsobetyped as ie|Separates two mutually exclusive choicesin a command. Type one choice and donot type the vertical bar.exit|quit() Encloses a range of values from whichyou can choose a value. ipethernet<aaa.bbb.ccc.ddd>(0-32)Type To do this...?To display the names of the root commands.<command_name> ? To display the syntax for a command.help To display all the commands, their subcommands andthe parameters and options for each command.help <command_name> To display the parameters and options for thecommand.!! To repeat the last command that was executed.ESC To cancel the command you are typing.
APCD-LM043-4.0 165CCU Command-line SyntaxTable 46 CCU Command-Line SyntaxCommand Syntax (CCU) Command DescriptionaddDisplays the Address Table.addflush Removes all entries from the AddressTable.addrem <eum id> Removes an EUM ID from the AddressTable, where:•<eum id> is the EUM ID, formatted inhexadecimal as XX:XX:XX.airDisplays the Registration Table.airassociations Displays the maximum association count.airdelete <eum id> Deletes an EUM from the RegistrationTable, where:•<eum id> is the EUM ID, formatted inhexadecimal XX:XX:XX.airdereg Displays the deregistration count.airdereg <value> Changes the deregistration count, where:•<value> is the deregistration count,from 1 to 254.airfdereg <eum id> Forces deregistration of an EUM, where:•<eum id> is the EUM ID, formatted inhexadecimal as XX:XX:XX.airflush Flushes the Registration Table.arpDisplays the ARP Table.arpadd <aaa.bbb.ccc.ddd><XX.XX.XX.XX.XX.XX> [flags]Adds an entry to the ARP Table, where.•<aaa.bbb.ccc.ddd> is the IPaddress of the new entry.•<XX:XX:XX:XX:XX:XX> is theEthernet address, in hexadecimalformat.•[flags] is always set to 4, meaningthe entry is permanent and doesn’t timeout, as long as the CCU or EUM is ON.arpdel <aaa.bbb.ccc.ddd> Deletes an entry from the ARP Table:•<aaa.bbb.ccc.ddd> is the IPaddress of the entry being deleted.arpflush Clears the ARP Table.
166 APCD-LM043-4.0arpmap Displays the ARP Map Table.arpmap <aaa.bbb.ccc.ddd> Maps MAC address to IP address<aaa.bbb.ccc.ddd>. The MAC addressis obtained from the ARP Table, or bysending out an ARP request.auth Displays the Authorization Table.auth add <eum id> <gos> Adds an EUM to the Authorization Table,where:•<eum id> is the EUM ID, formatted inhexadecimal as XX:XX:XX.•<gos> is the EUM grade of service, forexample, gold.auth default <gos> Sets the default GOS, which is the GOSassigned to an EUM on registration, where.•<gos> is the default grade of service,for example, bronze.auth del <eum id> Removes an EUM from the AuthorizationTable, where:•<eum id> is the EUM ID, formatted inhexadecimal as XX:XX:XX.auth gos <gos> Displays the GOS definitions, where:•<gos> is the grade of service, forexample, bronze.bcfDisplays the basic configuration file (BCF).dhcp Displays status of CCU DHCP Relay, eitherenabled or disable.dhcp disable Disables DHCP relay.dhcp enable Enables DHCP relay.dhcp relay Displays the CCU DHCP relay status andcontents of the DHCP Server Table.dhcp relay add <aaa.bbb.ccc.ddd><net mask>Adds the DHCP server IP address, where:•<aaa.bbb.ccc.ddd> is the IPaddress of the DHCP server.•<net mask> is the net mask of theDHCP server.dhcp relay del <aaa.bbb.ccc.ddd> Deletes the DHCP server IP address,where:•<aaa.bbb.ccc.ddd> is the IPaddress of the DHCP server.dhcp relay flush Flushes the DHCP server IP addresses.Command Syntax (CCU) Command Description
APCD-LM043-4.0 167exit|quit Exits the current console session andreturns to the password prompt.file ? Lists the file system utilities.file copy|cp <source><destination>Copies a file. Use this command only whenupgrading the firmware.•<source> is the name of the sourcefile.•<destination> isthenameofthedestination file.file delete <filename> Deletes a file, where.•<filename> is the name of the file youwant to delete.file dir|lsLists the file directory.file get <aaa.bbb.ccc.ddd><username> <password> <source><destination>Retrieves a file from a remote location,where.•<aaa.bbb.ccc.ddd> is the IPaddress or hostname of the computerfrom which you are retrieving the file.•<username> is the user name requiredto log on to the remote computer. (Ifthere is no username, as with an EUM,then use the password in place of theusername.)•<password> is the password requiredto log on to the remote computer•<source> isthepathandfilenameofthefilethatisbeingretrievedfromtheremote computer.•<destination> isthepathandfilename to which the file will be copied.file mkboot|makeboot <filename> Makes a new boot file, where:•<filename> is the name of the newboot file.file rename|rn <old file name><new file name>Renames a file, where:•<old file name> is the old file name•<new file name> is the new filename.help Displays the console command structure.ipDisplays the CCU IP address assignments.ipethernet Displays the Ethernet IP address of theCCU.Command Syntax (CCU) Command Description
168 APCD-LM043-4.0ipethernet <aaa.bbb.ccc.ddd>(0-32)Changes the Ethernet IP address of theCCU, where:•<aaa.bbb.ccc.ddd> is the newEthernet IP address of the CCU.•(0-32) is the netmask.ipgateway Displays the IP address of the routerthrough which the CCU connects to theInternet.ipgateway <aaa.bbb.ccc.ddd> Defines the router through which the CCUconnects to the Internet, where:•<aaa.bbb.ccc.ddd> is the newEthernet IP address of the router.ipradio Displays the radio IP address of the CCU.ipradio <aaa.bbb.ccc.ddd> (0-32)Changes the radio IP address of the CCU,where:•<aaa.bbb.ccc.ddd> is the new IPaddress of the CCU radio.•(0-32) is the netmask.password Initiates the process for changing thesystem password.pcfDisplays the permanent configuration file(PCF).ping <aaa.bbb.ccc.ddd> Sends ICMP echo requests to a remotehost, where:•<aaa.bbb.ccc.ddd> is the EthernetIP address of the remote host.Press any key to halt.port Displays the TCP/UDP port filters.port add <port number>tcp|udp|bothAdds or modifies a port filter, where:•<port number> is the number of theport to be filtered.•Oneoftcp|udp|both is selected tofilter TCP or UDP messages, or both.port delete <port number> Deletes a port filter, where:•<port number> istheporttobedeleted.port flush Deletes all port filters.port print Prints port filters.radio Displays the radio attributes of the CCU.Command Syntax (CCU) Command Description
APCD-LM043-4.0 169radio frequency Displays the CCU radio frequency in tenthsof a MHz; for example, 905.0 MHz isdisplayed as 9050.radio frequency <frequency> Changes the CCU radio frequency, where.•<frequency> is the new radiofrequency, in tenths of a MHz; forexample, 905.0 MHz is entered as9050.radio meter Displays the current Polling MAC load. Thisinformation is displayed for each GOS.radio rc Clears the CCU RSSI and transmit powerlevel history.radio rf high|low Displays or sets the power of the CCU radio.Note: The CCU RF level should always beset to high.radio rh Displays the RSSI and transmit power levelhistory.radio rssi Displays continuous RSSI readings. Pressany key to halt.rcfDisplays the contents of the routeconfiguration file (RCF).reset|reboot Reboots the CCU.route Displays the routing table for the CCU.route add <aaa.bbb.ccc.ddd><eee.fff.ggg.hhh> (0-32)Adds a route to the routing table. Thiscommand applies only to the CCU.•<aaa.bbb.ccc.ddd> is the EthernetIP address of the network being addedto the routing table.•<eee.fff.ggg.hhh> is the EthernetIP address of the gateway throughwhich the destination is reached.•(0-32) is the netmask for thedestination network.Command Syntax (CCU) Command Description
170 APCD-LM043-4.0route delete <aaa.bbb.ccc.ddd><eee.fff.ggg.hhh> (0-32)Deletes a route from the routing table.•<aaa.bbb.ccc.ddd> is the EthernetIP address of the network beingremoved from the routing table.•<eee.fff.ggg.hhh> is the EthernetIP address of the gateway throughwhich the destination device isreached.•(0-32) is the netmask for thedestination network.route stats Displays the routing statistics.save|commit Saves configuration changes.snmp Displays the CCU SNMP information.snmp community Displays the SNMP communities.snmp community add <community><read|write>Adds an SNMP community, where.•<community> isthenameoftheSNMP community being added, from 1-32 characters in length.• Enter <read> or <write> to indicatethe type of the community being added.snmp community delete<community>Deletes an SNMP community, where:•<community> isthenameoftheSNMP community being deleted.snmp contact Displays the SNMP system contact.snmp contact <contact> Changes the SNMP system contact, where:•<contact> is the name of the contact(WISP, for example), from 1-80characters in length.snmp interface Displays the SNMP interface MIBs.snmp location Displays the SNMP system location.snmp location <location> Changes the SNMP system location, where:•<location> is the location of theCCU, from 1-80 characters in length.snmp trap Displays the SNMP Trap Server Table.snmp trap add <aaa.bbb.ccc.ddd><community>Adds a trap server community, where:•<aaa.bbb.ccc.ddd> is the EthernetIP address of the trap server.•<community> is the community namefor the trap server, from 1-64characters in length.Command Syntax (CCU) Command Description
APCD-LM043-4.0 171snmp trap delete<aaa.bbb.ccc.ddd> <community>Deletes a trap server community, where:•<aaa.bbb.ccc.ddd> is the EthernetIP address of the trap server.•<community> is the community namefor the trap server being deleted.stats Displays the statistics for all drivers andnetwork protocols. Do not use thiscommand in a Telnet session since doing sowill display only a partial set of stats.stats clear Clears the statistics for all drivers.stats ethernet Displays Ethernet statistics.stats mac Displays MAC driver statistics.stats net Displays network protocol statistics.stats net icmp Displays ICMP statistics.stats net ip Displays IP statistics.stats net tcp Displays TCP statistics.stats net udp Displays UDP statistics.stats radio Displays radio driver statistics.stats rp Displays routing protocol statistics.stats summary Displays a summary of the Atmel MACstatistics.sys? Displays system information commands.syslog <number> <offset> Displays the modem log file, where:•<number> is the number of charactersto print from the log file.•<offset> is the character offset,default is 0.sysmacDisplays the MAC log.sysmemory Displays memory allocation information.sysprompt <new prompt> Changes the system prompt, where:•<new prompt> is the new prompt,from 1-20 characters in length.sysssDisplays the system status file.systask Displays the task list.sysuptime Displays system uptime.sysversion Displays software version information.Command Syntax (CCU) Command Description
172 APCD-LM043-4.0syswlog <text> Writes text to the log file. This command isuseful for adding information to the log forsubsequent analysis:•<text> may be from 1-80 charactersin length.time Displays the system calendar clock time.time add <aaa.bbb.ccc.ddd> Adds an NTP server, where:•<aaa.bbb.ccc.ddd> is the NTPserver address.time client Manages the SNTP client and displays a listof NTP servers.time client disable Disables the SNTP client.time client enable Enables the SNTP client.time client port <port> Changes the SNTP client port number:•<port> is the port number. The defaultport number is 123.time client resync <seconds> Sets the client resync period, where:•<seconds> is the resync period inseconds,time client retry <seconds> Sets the client retry period, where:•<seconds> is the retry period inseconds.time delete <aaa.bbb.ccc.ddd> Deletes an NTP server, where:•<aaa.bbb.ccc.ddd> is the NTPserver address.time flush Deletes all NTP servers.time flush default Deletes all NTP servers and restoresdefaults.time get Displays the system time.time print Prints the SNTP configuration and NTPserver list.time refresh|update Forces an NTP time update.time relay ? Lists SNTP relay commands.time relay enable Enables SNTP relay over the radiointerface.time relay disable Disables SNTP relay over the radiointerface.Command Syntax (CCU) Command Description
APCD-LM043-4.0 173time relay ip|destination<aaa.bbb.ccc.ddd>|broadcastSends NTP messages to a single EUM,where:•<aaa.bbb.ccc.ddd> is the IPaddress of the EUM.or sends NTP messages to all EUMs ifbroadcast is entered.time server ? Displays NTP server utilities.time server port <port> Changes the SNTP server port, where:•<port> is the port number.time server stratum <value> Sets NTP stratum or relative stratum offset,where:•<value> is the NTP offset, from 1-5when sync, and 6-15 when unsync.time set <time>. Sets the system time (Greenwich MeanTime), where:•<time> is formatted [dy-mon-yearhh:mm:ss] or [mm-dd-yy hh:mm:ss}.This command overwrites the local timeobtained from the NTP server. The localtime will be updated on the next refresh fromthe NTP server.time stats Displays time statistics.Command Syntax (CCU) Command Description
174 APCD-LM043-4.0EUM Command-line SyntaxTable 47 EUM Command-Line SyntaxCommand Syntax (EUM) Command DescriptionarpDisplays the ARP Table.arpadd <aaa.bbb.ccc.ddd><XX:XX:XX:XX:XX:XX> [flags]Adds an entry to the ARP table, where.•<aaa.bbb.ccc.ddd> is the IPaddress.•<XX:XX:XX:XX:XX:XX> is theEthernet address, in hexadecimalformat.•[flags] is always set to 4, meaningthe entry is permanent and doesn’t timeout, as long as the CCU or EUM is ON.arpdel <aaa.bbb.ccc.ddd> Deletes an entry from the ARP table, where.•<aaa.bbb.ccc.ddd> is the IPaddress of the entry.arpflush Clears the ARP table.arpmap Displays the ARP Map Table.arpmap <aaa.bbb.ccc.ddd> Maps MAC address to IP address<aaa.bbb.ccc.ddd>. The MAC addressis obtained from the ARP Table, or bysending out an ARP request.bcfDisplays the basic configuration file (BCF).cust Displays the Customer Table.cust flush Removes all entries from the CustomerTable.cust max Displays the maximum number ofcustomers.cust max <value> Sets the maximum number of customers,where:•<value> is the maximum number ofcustomers, from 1-50.exit|quit Exits the current console session andreturns to the password prompt.file ? Lists the file system utilities.
APCD-LM043-4.0 175file copy|cp <source><destination>Copies a file. Use this command only whenupgrading the firmware.•<source> is the name of the sourcefile.•<destination> isthenameofthedestination file.file delete <filename> Deletes a file, where:•<filename> is the name of the file youwant to delete.file dir|lsLists the file directory.file get <aaa.bbb.ccc.ddd><username> <password> <source><destination>Retrieves a file from a remote location,where.•<aaa.bbb.ccc.ddd> is the IPaddress or hostname of the computerfrom which you are retrieving the file.•<username> is the user name requiredto log on to the remote computer. (Ifthere is no username, as with an EUM,then use the password in place of theusername.)•<password> is the password requiredto log on to the remote computer•<source> isthepathandfilenameofthefilethatisbeingretrievedfromtheremote computer.•<destination> isthepathandfilename to which the file will be copied.file mkboot|makeboot <filename> Makes a new boot file, where:•<filename> is the name of the newboot file.file rename|rn <old file name><new file name>Renames a file, where:•<old file name> is the old filename.•<new file name> is the new filename.help Displays the console command structure.ipDisplays the EUM IP address assignments.ipethernet Displays the EUM IP address and netmask,the same for both the radio and Ethernetport.Command Syntax (EUM) Command Description
176 APCD-LM043-4.0ipethernet <aaa.bbb.ccc.ddd>(0-32)Changes the Ethernet IP address of theEUM, where:•<aaa.bbb.ccc.ddd> is the newEthernet IP address of the EUM.•(0-32) is the netmask.ipgateway Displays the IP address of the CCU throughwhich the EUM connects to the Internet.ipgateway <aaa.bbb.ccc.ddd> Changes the CCU through which the EUMconnects to the Internet, where:•<aaa.bbb.ccc.ddd> is the radio IPaddress of the new CCU.password Initiates the process for changing thesystem password.pcfDisplays the permanent configuration file(PCF).ping aaa.bbb.ccc.ddd Sends ICMP echo requests to remote host,where:•<aaa.bbb.ccc.ddd> is the EthernetIP address of the remote host.Press any key to halt.port Displays the TCP/UDP port filters.port add <port number>tcp|udp|bothAdds or modifies a port filter, where:•<port number> is the number of theport to be filtered.•Oneoftcp|udp|both is selected tofilter TCP or UDP messages, or both.port delete <port number> Deletes a port filter, where:•<port number> istheporttobedeleted.port flush Deletes all port filters.port print Prints port filters.radio Displays the radio attributes of the EUM.radio frequency Displays the EUM radio frequency in tenthsof a MHz; for example, 905.0 MHz would bedisplayed as 9050.radio frequency <frequency> Changes the EUM radio frequency.•<frequency> is the radio frequency intenths of a MHz; for example, 905.0MHz would be entered as 9050.Command Syntax (EUM) Command Description
APCD-LM043-4.0 177radio rc Clears the CCU RSSI and transmit powerlevel history.radio rf high|low Displays or sets the power of the EUMradio. Note: The EUM RF level shouldalways be set to high.radio rh Displays the RSSI and transmit power levelhistory.radio rssi Displays continuous RSSI readings. Pressany key to halt.reg eum Forces the EUM to request registration.reset|reboot Reboots the EUM.save|commit Saves configuration changes.snmpDisplays the EUM SNMP information.snmpcommunity Displays the SNMP communities.snmp community add <community><read|write>Adds an SNMP community, where.•<community> isthenameoftheSNMP community being added, from 1-32 characters in length.• Enter <read> or <write> to indicatethe type of the community being added.snmpcommunity delete<community>Deletes an SNMP community, where.•<community> isthenameoftheSNMP community being deleted.snmpcontact Displays the SNMP system contact.snmpcontact <contact> Changes the SNMP system contact, where:•<contact> is name of the EUM SNMPsystem contact (subscriber, forexample), from 1-80 characters inlength.snmpinterface Displays the interface MIBs.snmplocation Displays the SNMP system location.snmplocation <location> Changes the SNMP system location, where:•<location> is the location of theEUM, from 1-80 characters in length.snmptrap Displays the SNMP Trap Server Table.Command Syntax (EUM) Command Description
178 APCD-LM043-4.0snmptrap add <aaa.bbb.ccc.ddd><community>Adds a trap server community, where:•<aaa.bbb.ccc.ddd> is the EthernetIP address of the EUM.•<community> is the community namefor the trap server, from 1-64characters in length.snmptrap delete<aaa.bbb.ccc.ddd> <community>Deletes a trap server community, where:•<aaa.bbb.ccc.ddd> is the EthernetIP address of the EUM.•<community> is the community namefor the trap server being deleted, from1-64 characters in length.stats Displays the statistics for all drivers andnetwork protocols. Do not use thiscommand in a Telnet session since doing sowill display only a partial set of stats.stats clear Clears the statistics for all drivers.stats ethernet Displays Ethernet statistics.stats mac Displays MAC driver statistics.stats net Displays network protocol statistics.stats net icmp Displays ICMP statistics.stats net ip Displays IP statistics.stats net tcp Displays TCP statistics.stats net udp Displays UDP statistics.stats radio Displays radio driver statistics.stats rp Displays routing protocol statistics.stats summary Displays a summary of the Atmel MACstatistics.sys? Displays system information commands.syslog <number> <offset> Displays the modem log file, where:•<number> is the number of charactersto print from the log file.•<offset> is the character offset,default is 0.sysmacDisplays the MAC log.sysmemory Displays memory allocation information.Command Syntax (EUM) Command Description
APCD-LM043-4.0 179sysprompt <new prompt> Changes the system prompt, where:•<new prompt> is the new prompt,from 1-20 characters in length.sysssDisplays the system status file.systask Displays the task list.sysuptime Displays system uptime.sysversion Displays software version information.syswlog <text> Writes text to the log file. This feature isuseful for adding information to the log forsubsequent analysis.•<text> may be from 1-80 charactersin length.time Displays the system calendar clock time.time add <aaa.bbb.ccc.ddd> Adds an NTP server, where:•<aaa.bbb.ccc.ddd> is the NTPserver address.time client Manages the SNTP client and displays a listof NTP servers.time client disable Disables the SNTP client.time client enable Enables the SNTP client.time client port <port> Changes the SNTP client port number,where:•<port> is the port number. The defaultport number is 123.time delete <aaa.bbb.ccc.ddd> Deletes an NTP server, where:•<aaa.bbb.ccc.ddd> is the addressof the NTP server being deleted.time get Displays the system time.time print Prints the SNTP configuration and NTPserver list.time set <time> Set the system time (Greenwich MeanTime), where:• is formatted [dy-mon-year hh:mm:ss] or[mm-dd-yy hh:mm:ss}.This command overwrites the local timeobtained from the NTP server. The localtime will be updated on the next refresh fromthe NTP server.time stats Displays time statistics.Command Syntax (EUM) Command Description
—This page is intentionally left blank —
APCD-LM043-4.0 181Appendix D Antenna GuidelinesWARNING!Antennas and associated transmission cable must beinstalled by qualified personnel, and external antennas mustbe properly grounded. Failure to terminate the antenna portcorrectly can permanently damage the EUM. WaveRiderassumes no liability for failure to adhere to thisrecommendation or to recognized general safety precautions.The CCU and EUM have been certified for use with Omni, Disc, Patch, Yagi, and DipoleReflector antenna types. Table 48 includes examples of each of the recommended antennatypes, as well as their associated maximum antenna system gain.Table 48 CCU, EUM Supported AntennasAntenna system gain is the net gain of the system. In other words, it is the antenna gain minusthe insertion loss due to cabling, connectors, filters, surge protectors, and other hardwarecomponents. During installation, you must verify that the antenna system does not exceed themaximum allowable antenna system gain for that specific antenna type.Antenna Type Maximum Antenna SystemGainOmni 5.1dBiDisc 3.0dBiPatch 8.5dBiYagi 9.1dBiDipole Reflector 10.4dBi
182 APCD-LM043-4.0Calculate the antenna system gain by adding the value of the insertion loss for eachcomponent of the antenna system, excluding the antenna, and subtracting the total of thatsum from the antenna gain. You can measure the insertion loss of the components, and theantenna gain, at the frequency of interest, or obtain it by referencing the manufacturer’ssupplied literature.For example, with a Yagi antenna system, 10m of cable, a surge protector, and a bandpassfilter, you would calculate the following antenna system gain:• Antenna Gain: 9.1dBi• Insertion loss:• Cable/connectors: - 4.0dB• Surge Protector: - 0.2dB• Filter: - 1.1dB• Antenna System Gain: 3.8dBiThe antenna gain (9.1dBi) minus the total insertion loss (5.3dBi), yields an antenna systemgain of 3.8dBi, which is a valid antenna configuration, because the antenna system gain islower than the maximum permissible value of 9.1dBi for a yagi antenna type.WARNING!To prevent equipment damage, you must use the WaveRiderproprietary WCM connector to connect transmission line andantennas to the EUM2000.WARNING!Use of an outdoor antenna with the EUM requires professionalinstallation, in accordance with FCC guidelines.WARNING!Antennas used with the EUM must not present a short toground at the EUM antenna port. Contact the WaveRiderCustomer Support Centre for more information.
APCD-LM043-4.0 183Appendix E CCU/EUM Data TablesThe CCU and EUM firmware is structured around a set of tables and files, which arediscussed in the following sections in the logical order that they are actively involved in thetransmission of packets from the Internet to the end-user’s PC:•Port Filter Table (CCU and EUM) on page 183•Routing Table (CCU and EUM) on page 184•ARP Table (CCU and EUM) on page 187•Address Translation Table (CCU only) on page 188•Authorization Table (CCU only) on page 189•Registration Table (CCU only) on page 190•ARP Map Table (CCU and EUM) on page 191•Customer Table (EUM only) on page 192•Basic Configuration File (CCU and EUM) on page 193•Permanent Configuration File (CCU and EUM) on page 193•System Status File (CCU and EUM) on page 195Port Filter Table (CCU and EUM)The Port Filter Table provides a list of all port filters that have been enabled. Any IP packetwith one of these port numbers will be discarded.The contents of the Port Filter Table are:
184 APCD-LM043-4.0Table 49 Port Filter Table EntriesTo access the Port Filter Table:Console> portPORT FILTERSPort Filter---------------------------------137 both138 both139 both1512 both----------------------------------Console>Routing Table (CCU and EUM)The Routing Table is used by the CCU to determine the routing of IP packets. The routes inthe Routing Table are either entered by the system operator as static routes, or automaticallygenerated by the CCU. The CCU does not support dynamic routing. As a minimum, theRouting Table contains the following three routes:Table 50 Basic CCU RoutesIn 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 the following entries:Table Entry DescriptionPort The number of the port which is to be filtered.Filter For each port listed, the CCU or EUM can be set to filter UDP,TCP, or both UDP and TCP packets.Default RouteAny packet with a destination which is not listed in the RoutingTable is forwarded to the gateway address defined in the defaultroute. Normally, this is be the IP address of the NAP router. Thedefault route is generated automatically by the CCU when youenter the gateway IP address.Radio Subnet RouteAny packet with a destination in the radio subnet (EUMs, end-user PCs) is forwarded to the CCU radio port. This route isautomatically generated by the CCU, using the CCU radio subnetIP address, entered by the system operator.Loopback RouteThe loopback interface exists (among other reasons) so the CCUoperating system can talk to itself without handing the packet to ahardware driver. This route keeps unneeded traffic off thenetwork. This loopback route is automatically generated by theCCU.
APCD-LM043-4.0 185Table 51 Routing Table EntriesTo view the Routing Table:WaveRider Communications, Inc. LMS3000Password:Console> routeDestination Mask TOS Gateway Flags RefCnt Use Interface Proto0.0.0.0 0 0 10.0.0.1 803 0 196587 esmc0 110.5.0.0 ffff0000 0 10.5.0.1 101 0 0 rdr1 0127.0.0.1 0 0 127.0.0.1 5 0 24 lo0 0Console>Entry DescriptionDestination The IP address for the destination network.Mask The subnet mask for the destination network.TOSType of service, for example:• 0000 Default• 0001 Minimize monetary cost• 0010 Maximize reliability• 0100 Maximize throughput• 1000 Minimize delayRFC1700 and RFC1349 recommend TOS settings for variousprotocols, including Telnet, FTP, TFTP, ICMP and SNMP.Gateway The IP address of the gateway through which to access thedestination network.Flags Refer to Table 52.RefCntNumber of processes currently referencing the route. If aprocess requires a route, it looks it up in the Routing Table.When the route is being referenced by a process, refcnt will beincremented by one. When the process is done with the route,refcnt will be decremented by one.Use Initialized to 0 and incremented every time an IP datagramuses this route.InterfaceThe CCU interface through which to send packets to thegateway and destination, one of:• esmc0: CCU Ethernet interface• rdr1: CCU radio interface• lo0: LoopbackProto This entry is an operating system parameter that has nomeaning for CCU configuration and operation.
186 APCD-LM043-4.0In the above example, the default route is defined by:Destination Mask TOS Gateway Flags RefCnt Use Interface Proto0.0.0.0 0 0 10.0.0.1 803 0 196587 esmc0 1Any IP packet with a destination which is not listed in the Routing Table will be forwardedthrough the Ethernet port (IP address 10.0.0.1) and on to the NAP router.The radio subnet route is defined by:Destination Mask TOS Gateway Flags RefCnt Use Interface Proto10.5.0.0 ffff0000 0 10.5.0.1 101 0 0 rdr1 0Any IP packet destined for the radio subnet (any IP address starting with 10.5.xx.xx) will beforwarded through the CCU radio port (IP address 10.5.0.1) and over the radio link to theEUMs and end-user’s computers.The loopback route is defined by:Destination Mask TOS Gateway Flags RefCnt Use Interface Proto127.0.0.1 0 0 127.0.0.1 5 0 24 lo0 0Any IP packet destined for 127.0.0.1, which is an IP address reserved for loopback, will belooped back to the CCU operating system.The Routing Table flags are summarized in Table 52.Table 52 Routing Table Flags.To use Table 52, consider the flag associated with the default route, 803, which is equal to(800 + 2 +1). Referring to Table 52, this route was manually added, the destination is agateway, and the route is usable.Flag Mask Description0x10x20x40x80x100x200x400x800x1000x2000x4000x8000x10000x20000x40000x8000Route usableDestination is a gatewayHost entry (net otherwise)Host or net unreachableCreated dynamically (by redirect)Modified dynamically (by redirect)Message confirmedSubnet mask presentGenerate new routes on useExternal daemon resolves nameGenerated by ARP or ESISManually addedJust discard packets (during updates)Protocol specific routing flagProtocol specific routing flagModified by management protocol
APCD-LM043-4.0 187ARP Table (CCU and EUM)For each host (EUM or PC) in the system, the ARP (Address Resolution Protocol) Tabledisplays the following information:Table 53 ARP Table EntriesThe ARP Table is automatically built by the CCU or EUM based on traffic passing between theEthernet and Radio ports. This table displays the host IP and MAC addresses. After the CCUor EUM recovers the destination IP address from an IP packet sent to the router layer, it looksin the ARP Table to find the destination Ethernet MAC address. If the IP address does notappear 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 beforced 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.To view the CCU ARP table:Console> arpLINK LEVEL ARP TABLEdestination gateway flags Refcnt Use Interface--------------------------------------------------------------------------10.0.0.1 00:30:80:4a:08:a1 405 1 5 esmc010.0.0.2 00:10:4b:6c:fa:54 405 0 4610 esmc0Table Entry Descriptiondestination Host IP Addressgateway Host Ethernet MAC Addressflags Refer to Routing Table (CCU and EUM) on page 184 for a description ofthese flags.RefcntNumber of processes currently referencing this ARP entry. If a processrequires a MAC address, it looks it up in the ARP Table. When the ARPentry is referenced by a process, refcnt will be incremented by one.When the process is done with the ARP entry, refcnt will bedecremented by one.Use Number of times the ARP Table has been accessed for this networkelement.InterfaceThe type of interface, one of the following:• esmc0: Ethernet• rdr1: Radio• lo0: Loopback
188 APCD-LM043-4.010.0.0.3 00:90:27:33:c7:e8 405 0 507 esmc010.0.0.10 00:a0:98:00:9b:26 405 0 1 esmc010.0.0.15 00:10:83:fd:61:a 405 0 781 esmc010.0.0.16 00:10:83:fd:e1:4e 405 0 1839 esmc010.0.0.17 00:b0:d0:e1:04:c0 405 0 155 esmc010.0.1.68 00:00:e8:4d:62:3 405 1 19054 esmc010.5.1.17 00:50:da:bb:d1:de 405 0 135 rdr110.5.2.50 00:50:ba:b3:97:cd 405 0 12 rdr110.5.2.54 00:50:da:b7:25:2f 405 0 8823 rdr1--------------------------------------------------------------------------Console>Address Translation Table (CCU only)The Address Translation Table lists the MAC addresses for:• End-user PC’s that have been granted air access, if the CCU has sent traffic to, orreceived traffic from, the PC• EUMs, if the CCU has sent traffic to, or received traffic from, the network element.If no traffic has been sent traffic to, or received traffic from, an end-user PC or EUM host for a12-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 lookup the EUM ID for a particular MAC address. The MAC addresses associated with the EUM,are:• EUM Radio MAC Address• EUM Ethernet Address• End-user PC MAC Address (one or more)To view the Address Translation Table:Console> addEUM ID MAC Address-----------------------------------60:0a:33 00:90:c8:60:0a:3360:0a:33 00:01:03:04:f7:d860:0a:33 00:90:c8:e0:0a:3360:00:46 00:90:c8:60:00:4660:00:4a 00:50:da:bb:d1:de60:00:4a 00:90:c8:60:00:4a60:03:75 00:90:c8:60:03:7560:02:79 00:90:c8:60:02:7960:02:79 00:50:ba:b3:97:cd60:04:a3 00:90:c8:60:04:a360:00:a9 00:90:c8:60:00:a960:00:ef 00:01:02:2b:b2:9960:00:f5 00:02:44:10:a6:6fTotal of 13 entriesConsole>In the above view, the following MAC addresses are associated with EUM ID 60:0a:33:•00:90:c8:60:0a:33EUM Radio MAC Address
APCD-LM043-4.0 189•00:01:03:04:f7:d8End-user PC MAC Address•00:50:c8:e0:0a:33EUM Ethernet MAC AddressAuthorization Table (CCU only)The Authorization Table controls the EUMs’ access to the LMS4000 900 MHz Radio Network.The Authorization Table contains the grade of service class for each EUM in the system,whether the EUM is active or not.The contents of the Authorization Table are used by the Polling MAC algorithm, and also bythe CCU, to automatically build the Registration Table.The entries in the Authorization Table can be entered directly by the system operator, or thecomplete table can be modified remotely and downloaded to the CCU using FTP. The GOSclass entry will either be a grade of service class, or “denied” (service).The Default entry in the Authorization Table is assigned on registration to any EUM that hasnot been assigned a grade of service class. The Default entry can be a grade of service class,or denied, meaning any EUM that has not been assigned a grade of service class will bedenied service. This rule applies only to newly registered EUMs, and not to EUMs that havebeen previously registered. Once you have changed the default, if you want the defaultchanged for all EUMs, regardless of when they registered, then you must flush theRegistration Table. The new default then takes effect as the EUMs re-register.There are two approaches to managing the Authorization Table:• Approach 1: If the default is set to denied, then EUMs will be denied service unlessthey are explicitly entered in the Authorization Table, with a grade of service.• Approach 2: If the default is set to a grade of service, such as best effort,thenEUMswill be authorized and given a best effort grade of service unless they are explicitlydenied service in the Authorization Table.To view the Authorization Table:Console> authEUM ID GOS CLASS----------------------60:02:79 silver60:00:a9 bronze60:03:77 gold60:04:a3 silver60:0a:33 silverDefault goldTotal of 5 entriesConsole>
190 APCD-LM043-4.0Registration Table (CCU only)The Registration Table contains a list of all registered EUMs. The CCU automatically buildsand adds to this table as EUMs communicate with the CCU. Every EUM that registers with theCCU appears 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• theEUMhashadnotraffictosendformorethan12hr.,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 removedimmediately from the Registration Table.The Registration Table contains the following entries:Table 54 Registration Table EntriesTo view the Registration Table:Console> airMaximum Associations : 75Deregistration Count : 8REGISTERED EUMsEUM ID GOS Level Time[s]--------------------------------60:03:75 gold 2260:0a:33 silver 260:00:ef gold 2960:00:46 gold 160:00:4a gold 060:00:f5 gold 152260:02:79 silver 160:03:f6 gold 160:04:a3 silver 2760:00:a9 bronze 0--------------------------------Table Entry DescriptionEUM ID EUM IDGOS Level Grade of Service ClassTime (s) Time since the last payload was received from the EUM.Maximum Associations The maximum number of EUMs that can be associated atany one instant in time.Deregistration Count An EUM will be de-registered if it does not respond afterthe CCU has sent it this many consecutive polls.
APCD-LM043-4.0 191Console>NOTE: The air command has been used to view the RegistrationTable, because reg is too close to reb (reboot).ARP Map Table (CCU and EUM)For each host (EUM or PC) in the system, the ARP Map Table displays the following entries:Table 55 ARP MAP Table EntriesThe ARP MAP Table is built automatically by the CCU, from information contained in theAddress, ARP and Registration Tables. Its primary use is to summarize the information inthese tables in a user-friendly format, for presentation to the system operator.To view the ARP MAP Table:Console> arp mapARP MAP TABLEIP Address Ethernet EUMID GOS Last Rx10.5.0.10 00:90:c8:60:02:79 60:02:79 silver 2410.5.0.11 00:90:c8:60:04:a3 60:04:a3 silver 1910.5.0.12 00:90:c8:60:03:f6 60:03:f6 gold 2310.5.0.13 00:90:c8:60:00:a9 60:00:a9 bronze 010.5.0.14 00:90:c8:60:0a:33 60:0a:33 silver 2410.5.0.16 00:90:c8:60:00:ef 60:00:ef gold 2110.5.0.17 00:90:c8:60:00:4a 60:00:4a gold 2010.5.0.18 00:90:c8:60:00:46 60:00:46 gold 2310.5.0.31 00:90:c8:60:03:75 60:03:75 gold 1410.5.1.14 00:01:03:04:f7:d8 60:0a:33 silver 2410.5.1.16 00:01:02:2b:b2:99 60:00:ef gold 2110.5.1.17 00:50:da:bb:d1:de 60:00:4a gold 2010.5.2.50 00:50:ba:b3:97:cd 60:02:79 silver 2410.5.2.54 00:50:da:b7:25:2f 60:00:a9 bronze 0Console>Table Entry DescriptionIP Address Host IP addressEthernet Host Ethernet MAC addressEUMID EUM IDGOS EUM Grade of ServiceLast Rx Number of seconds since the last payload was received from theEUM.
192 APCD-LM043-4.0Customer Table (EUM only)The purpose of the Customer Table is to give the system operator control over the number ofPCs that can access the Internet through the EUM. The Customer Table is optimized for thecase where multiple hosts are connected to the EUM, but only one accesses the Internet atany given time. The Customer Table also acts as a bridging table, ensuring local traffic is keptlocal.The Customer 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. Ifcustomer_max is set to “n”, up to “n” computers in the Customer Table will have air access.Air access is assigned on a “first come, first served” basis. If n=1, the first computer to transmitpackets will be granted air access. All other computers will be denied air access. If thecomputer that has been granted air access, does not transmit traffic for 10 minutes, then hisair access will be removed and the next computer that transmits a packet will be granted airaccess.More generally, for any “n”, up to customer_max, the first n computers transmitting packets willbe granted air access and, if any of them fails to transmit traffic for 10 minutes, their air accesswill be removed, allowing the next computer without air access to be granted air access assoon as they transmit data.The contents of the Customer Table are:Table 56 Customer Table EntriesNOTE: If customer max is set to 1, and you want to connect a differentPC to the EUM, for maintenance purposes, for example, youmust clear the Customer Table, reset the EUM, or wait for 10minutes.To display the Customer Table:Console> custMAC Address Air Access Time[s]-------------------------------------------00:50:da:b7:34:f3 Y 10000:50:da:bb:d1:de N 100Total of: 2 entriesConsole>Table Entry DescriptionMAC Address Computer’s MAC addressAir Access Y - computer has been granted air access.N - computer has not been granted air accessTime (s) Time, in seconds, since the last packet was received from aparticular end-user computer or device.
APCD-LM043-4.0 193Basic Configuration File (CCU and EUM)The Basic Configuration File (BCF) presents a summary of CCU and EUM configurableparameters, which are either the factory default settings, or those entered by the systemoperator.To view the BCF for an EUM, for example:Console> bcfBasic Cfg File:File ID : basic.cfgFile Time Stamp:File Version : 3File Notes : Operator updatedFile CRC : 0xC3Ethernet/USB IP Address: 10.5.0.31Ethernet/USB Net Mask : ffff0000Gateway IP Address: 10.5.0.1Contact: WaveRider Communications Inc.Location: www.waverider.comName: LMS3000SNMP Read Communities:publicSNMP Write Communities:privateSNMP Traps:Radio Frequency: 9170RF Power: HIGHCustomer Connection: EthernetMaximum Number of Customers : 50Maximum bridge table size : 256Console>The CCU BCF is similar to the EUM BCF.Permanent Configuration File (CCU and EUM)The Permanent Configuration File (PCF) is a record of device parameters that arepermanently programmed during manufacturing.To view the PCF:Console> pcfPermanent Cfg File:File ID : perm.cfgFile Time Stamp: 17May2001File Version : 002
194 APCD-LM043-4.0File Notes : Based on TN040Customer Port MAC Address: 00:90:c8:e0:03:75Hardware ID: 4BAirlink MAC Address: 00:90:c8:60:03:75Serial Number: E00375Modem Type: EUMRF level +27 dbm +15 dbmLo - 905.0 Mhz -14 20Med - 915.0 Mhz -22 16High - 925.0 Mhz -22 16RSSI level -76 dbm -70 dbm -46 dbmLo - 905.0 Mhz 45 51 77Med - 915.0 Mhz 46 51 78High - 925.0 Mhz 46 51 78POT Settings: Wiper1: 131 Wiper2: 152Console>An RSSI level that falls outside the range of the calibration, or between the calibration points,can be converted to a received signal strength (RSS) reading in dBm, using the followingsimple rules:• If the measured RSSI is ‘x’ below the RSSI level at the lower calibration point, then thereceived signal strength can be calculated as -76dBm - x. Using the above unit as anexample, if you are measuring an RSSI of 42 at a frequency of 915MHz, then thereceived signal strength is -76dBm - (46 - 42) = -80dBm.• Similarly, if the measured RSSI is ‘y’ above the RSSI level at the higher calibrationpoint, then the received signal strength can be calculated as -46dBm + y. Using theabove unit as an example, if you are measuring an RSSI of 80 at a frequency of905MHz, then the received signal strength is -46dBm + (80 - 77) = -43dBm.• For RSSI measurements that fall between two calibration points, you must interpolateup (1dBm for every unit step in RSSI value) from the lower of the two calibrationpoints if the RSSI falls below the midpoint of the two calibration points. Likewise, youmust interpolate down from the higher of the two calibration points if the RSSI fallsabove the midpoint.Using these simple rules, the following RSSI-RSS cross-reference table for the above sampleunit, at 915MHz, can be produced:
APCD-LM043-4.0 195Table 57 RSSI/RSS Cross-reference for Sample Unit (at 915MHz)As shown in Table 57, using these simple rules means that the RSS values midway betweenthe calibration points may not exactly line up, but the results will be within the accuracy of themeasurement. The Configuration Utility automatically calculates and displays the currentreceived signal strength, and a histogram of the received signal strength.System Status File (CCU and EUM)The System Status File is a record of the results of the CCU and EUM POST (Power On SelfTest).To view the System Status File:Console> sys ssPOST Results:-----------------------Registers......PassedTimers.........PassedSDRAM..........PassedWatchdog.......PassedTFFS...........PassedPCMCIA.........Not runEthernet.......PassedMAC............PassedRadio..........Not runUSB............Not runRS232_1........Not runRS232_2........Not runFile Status:-----------------------perm.cfg........Opened-OKbasic.cfg.......Opened-OKroute.cfg.......Test Not Runsa1110.exe......Opened-OKnetdb.cfg.......Test Not RunRSSI RSS RSSI RSS RSSI RSS RSSI RSS RSSI RSS39 -83dBm 48 -74dBm 57 -64dBm 66 -58dBm 75 -49dBm40 -82dBm 49 -72dBm 58 -63dBm 67 -57dBm 76 -48dBm41 -81dBm 50 -71dBm 59 -62dBm 68 -56dBm 77 -47dBm42 -80dBm 51 -70dBm 60 -61dBm 69 -55dBm 78 -46dBm43 -79dBm 52 -69dBm 61 -60dBm 70 -54dBm 79 -45dBm44 -78dBm 53 -68dBm 62 -59dBm 71 -53dBm 80 -44dBm45 -77dBm 54 -67dBm 63 -58dBm 72 -52dBm 81 -43dBm46 -76dBm 55 -66dBm 64 -57dBm 73 -51dBm 82 -42dBm47 -75dBm 56 -65dBm 65 -59dBm 74 -50dBm 83 -41dBm
196 APCD-LM043-4.0IO Connections:-----------------------USB Detected TrueEthernet Detected TrueRS232_1 Detected TrueRS232_2 Detected FalseSystem State:-----------------------System OperationalConsole>
APCD-LM043-4.0 197Appendix F Ping CommandsThe following table lists the options available for use with a Windows Ping test. Thisinformation was obtained from Microsoft Windows 2000 TCP/IP Protocols and ServicesTechnical Reference, pp. 184-185.Table 58 Windows Ping Test Command OptionsOption Use Default-t Sends Echoes until interrupted. Not set-a Performs a Domain Name System (DNS) reverse query toresolve the DNS hose name of the specified IP address Not set-n count The number of Echoes to send 4-l size The size of the Optional Data field up to a maximum of65,500 32-f Sets the Don’t Fragment (DF) flag to 1 Not set-I TTL Sets the value of the TTL field in the IP header 32-v TOS Sets the value of the Type of Service field in the IP header.The TOS value is in decimal 0-r count Sends the ICMP Echoes using the IP Record Route optionand sets the value of the number of slots. Count has amaximum value of 9.Not set-s count Sends the ICMP Echoes using the IP Internet Timestampoption and sets the value of the number of slots. Counthas a maximum value of 4. Windows 2000 PING uses theInternet Timestamp FLAG set to 1 (records both the IPaddresses of each hop and the timestamp.Not set
198 APCD-LM043-4.0-j host-list Sends the ICMP Echoes using the Loose Source Route optionand sets the next hop addresses to the IP addresses in the hostlist. The host list is made up of IP addresses separated by spacescorresponding to the loose source route. There can be up to nineIP addresses in the lost list.Not set-k host-list Sends the ICMP Echoes using the Strict Source Route option andsets 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 listis made of IP addresses separated by spaces corresponding tothe loose source route. There can be up to 9 IP addresses in thehost list.Not set-w timeout Waits the specified amount of time, in milliseconds, for thecorresponding Echo Reply before displaying a Request TimedOut message.1000Option Use Default
APCD-LM043-4.0 199Appendix G SNMP MIB DefinitionsThis appendix defines the MIBs used in the CCU and EUM. These MIBs are organized underthe following headings:•MIB-II Elements Supported from RFC-1213 on page 199•WaveRider CCU Enterprise MIBs on page 203•CCU RFC MIB-II Traps on page 212•WaveRider EUM Enterprise MIBs on page 213•EUM RFC MIB-II Traps on page 221MIB-II Elements Supported from RFC-1213The CCU and EUM support the following MIB-II groups, which are defined in detail inRFC1213.Groups in MIB-IIMIB-II is divided into the following MIBs. All values in Table 59 are prefixed by 1.3.6.1.2.1.Table 59 Groups in MIB-IIMIB Name OID Type Status Descriptionsystem 1 MIB R This group provides information on the general system, such assystem description, contact, system up time.interfaces 2 MIB R This group has one set of values for each interface on the modem.The CCU/EUM has 3 interfaces: 1= loopback, 2 = esmc0(ethernet) and 2 = mdr1 (radio).
200 APCD-LM043-4.0Interfaces Group MIBTable 60 provides the details of the Interfaces group MIB mentioned above. All values in thefollowingtableareprefixedwith1.3.6.1.2.1.2.Table 60 MIB-II Interface List Header MIBAll values in Table 61 are prefixed with 1.3.6.1.2.1.2.2.1, as defined in RFC1213, and are readonly.Table 61 MIB-II Interface List Table MIBat 3 MIB R This group shows the address translation table, mapping Ethernetaddresses to IP addresses. This group is only for MIB-Icompatibility.ip 4 MIB R This group provides all of the statistics on IP traffic that is routedthrough the modem. For EUMs, all traffic from the end-user to theCCU bypass the IP stack in the EUM so these numbers are onlyfor the EUM applications. For the CCU, all IP traffic through theCCU router application, including CCU application traffic.icmp 5 MIB R This groups provides statistics on all ICMP packets processed bythe IP stack.tcp 6 MIB R This provides counters for all TCP packets processed by themodem. Only TCP packets sent or received by the modemapplications are counted (e.g. FTP or Telnet sessions directly tothe modem) since any packets for other hosts are routed by the IPprotocol and never reach the TCP protocol.udp 7 MIB R Counters for all UDP packets processed by the modem'sapplications. Only UDP packets sent or received by the modemapplications are counted (e.g. FTP or Telnet sessions directly tothe modem) since any packets for other hosts are routed by the IPprotocol and never reach the UDP protocol.snmp 11 MIB R Counters for all SNMP packets process by the modem'sapplications.MIB Name OID Type Status DescriptionifIndex 1 Integer R The number of entries in ifTable.ifTable 2MIB Thelistofinterfaces.MIB Name OID Type Status DescriptionMIB Name OID ValueType Accepted Values DescriptionifIndex 1 Integer A unique value for each interface. Its valueranges between 1 and the value of ifNumber.The value for each interface must remainconstant at least from one re-initialization ofthe entity's network management system tothe next re-initialization.
APCD-LM043-4.0 201ifDescr 2 String lo0: loopbackesmc0: ethernetmdr1: radioA textual string containing information aboutthe interface. This string should include thename of the manufacturer, the product nameand the version of the hardware interface.ifType 3 Integer 6:ethernet-csmacd6: radio interface24: softwareLoopbackThe type of interface, distinguished accordingto the physical/link protocol(s) immediately`below' the network layer in the protocolstack. The radio interface and ethernet-csmacd return the same value since they areboth viewed as Ethernet ports by the CCUrouting application.ifMtu 4 Integer The size of the largest datagram which canbe sent/received on the interface, specified inoctets. For interfaces that are used fortransmitting network datagrams, this is thesize of the largest network datagram that canbe sent on the interface.ifSpeed 5 Gauge An estimate of the interface's currentbandwidth in bits per second. For interfaceswhich do not vary in bandwidth or for thosewhere no accurate estimation can be made,this object should contain the nominalbandwidth.ifPhysAddress 6 PhysAddressThe interface's address at the protocol layerimmediately `below' the network layer in theprotocol stack. For interfaces which do nothave such an address (e.g., a serial line), thisobject should contain an octet string of zerolength.ifAdminStatus 7 Integer 1: up2: down3: testingThe desired state of the interface. Thetesting(3) state indicates that no operationalpackets can be passed.ifOperStatus 8 Integer 1: up2: down3: testingThe current operational state of the interface.The testing(3) state indicates that nooperational packets can be passed.ifLastChange 9 TimeTicks The value of sysUpTime at the time theinterface entered its current operational state.If the current state was entered prior to thelast re-initialization of the local networkmanagement subsystem, then this objectcontains a zero value.ifInOctets 10 Counter The total number of octets received on theinterface, including framing characters.ifInUcastPkts 11 Counter The number of subnetwork-unicast packetsdelivered to a higher-layer protocol.ifInNUcastPkts 12 Counter The number of non-unicast (i.e., subnetwork-broadcast or subnetwork-multicast) packetsdelivered to a higher-layer protocol.MIB Name OID ValueType Accepted Values Description
202 APCD-LM043-4.0ifInDiscards 13 Counter The number of inbound packets which werechosen to be discarded even though noerrors had been detected to prevent theirbeing deliverable to a higher-layer protocol.One possible reason for discarding such apacket could be to free up buffer space.ifInErrors 14 Counter The number of inbound packets thatcontained errors preventing them from beingdeliverable to a higher-layer protocol.ifInUnknownProtos 15 Counter The number of packets received via theinterface which were discarded because ofan unknown or unsupported protocol.ifOutOctets 16 Counter The total number of octets transmitted out ofthe interface, including framing characters.ifOutUcastPkts 17 Counter The total number of packets that higher-levelprotocols requested be transmitted to asubnetwork-unicast address, including thosethat were discarded or not sent.ifOutNUcastPkts 18 Counter The total number of packets that higher-levelprotocols requested be transmitted to a non-unicast (i.e., a subnetwork-broadcast orsubnetwork-multicast) address, includingthose that were discarded or not sent.ifOutDiscards 19 Counter The number of outbound packets which werechosen to be discarded even though noerrors had been detected to prevent theirbeing transmitted. One possible reason fordiscarding such a packet could be to free upbuffer space.ifOutErrors 20 Counter The number of outbound packets that couldnot be transmitted because of errors.ifOutQLen 21 Gauge The length of the output packet queue (inpackets).ifSpecific 22 object Not usedMIB Name OID ValueType Accepted Values Description
APCD-LM043-4.0 203WaveRider CCU Enterprise MIBsThe structure of the CCU MIBs is illustrated in Figure 51.Figure 51 CCU MIBsEach of the MIBs in Figure 51 is discussed in the following sections.CCU Base MIBAll values in Table 62, which are read only, are prefixed with 1. 3. 6.1.4.1. 2979.11.Table 62 WaveRider CCU Base MIBMIB Name OID Value Type DescriptionccuGlobal 1 MIB CCU general data.ccuRadioConfig 2MIB CCU configuration and setup data.ccuRadioStats 3MIB CCU radio statistics.ccuEtherStats 4MIB CCU Ethernet statisticsccuModems 5MIB CCU registration and authorization information.WaveRider (2979)waveriderccuGlobalccu3000pmacglobccuRadioConfigccu3000pmacradcfgccuRadioStatsccu3000pmacrsccuEtherStatsccu3000pmacesccuModemccu3000pmacmodemccuRadioStatsGeneralccu3000pmacrsgenccuRadioStatsDriverccu3000pmacrsdrvccuRadioStatsAtmelccu3000pmacrsatmelccuRegistrationccu3000pmacregccuAuthorizationccu3000pmacauthEnterprise (1.3.6.1.4.1)LMS3000 CCUccu3000pmacMIB NameMIB File PrefixLegend
204 APCD-LM043-4.0CCU General Information GroupAll values in Table 63 are prefixed with 1.3.6.1.4.1.2979.11.1.Table 63 WaveRider CCU General Information Enterprise MIBsCCU Radio Configuration GroupAll CCU Radio Configuration Group MIB values are read only. All values in Table 64 areprefixed with 1.3.6.1.4.1.2979.11.2.Table 64 WaveRider CCU Radio Configuration Enterprise MIBsMIB Name OID Value Type Status AcceptedValues DescriptionccuSerialNumber 1 String R CCU hardware serial numberccuSoftwareVersion 2String RCCU firmware version.ccuHardwareVersion 3String RCCU hardware version.ccuExtraFunctions 4Integer R 0 A mask for extra functionality that maybe added at a later date. For now, itreturns ‘0’.ccuGlobalStatus 5Integer R1: startup2: dead3: ok4: suspectCurrent status of the radio interface.For now, this field returns ‘ok’.ccuGlobalSaveCounter 6Counter RA count of the number of times theconfiguration is saved. Initially, this fieldalways returns ‘0’.ccuGlobalConfigFiles 7String RA list of configuration files for the CCU.The list is delimited with a semicolon;i.e., “basic.cfg;route.cfg, ...”ccuGlobalReset 8Integer W1: reset Not functional at this time.ccuGlobalReload 9Integer W1: reload Not functional at this time.MIB Name OID ValueType AcceptedValues DescriptionccuRadioConfigVersion 1 String Radio firmware version.ccuRadioConfigMacAirlinkAddr 2PhysAddressMAC address Radio MAC address.ccuRadioConfigFrequency 3Integer Radio frequency in use (in 1/10ths of aMHz)ccuRadioConfigDomain 4Integer 0: IEEE1: FCC or IC/CanadaCurrent regulatory domain for which theradio is configured.ccuRadioHardwareRevision 5String Radio hardware revision.
APCD-LM043-4.0 205CCU Radio Statistics GroupAll CCU Radio Statistics Group MIB values are read only. All values in Table 65 are prefixedwith 1.3.6.1.4.1.2979.11.3.Table 65 WaveRider CCU Radio Statistics MIBCCU Radio General Statistics GroupAll CCU Radio General Statistics Group MIB values are read only. All values in Table 66 areprefixed with 1.3.6.1.4.1.2979.11.3.1.Table 66 WaveRider CCU Radio General Statistics Group MIBCCU Radio Driver Statistics GroupAll CCU Radio Driver Statistics Group MIB values are read only. All values in Table 67 areprefixed with 1.3.6.1.4.1.2979.11.3.2.Table 67 WaveRider CCU Radio Driver Statistics Group MIBMIB Name OID ValueType DescriptionccuRadioStatsGeneral 1 MIB General radio statistics.ccuRadioStatsDriver 2MIB Radio driver statisticsccuRadioStatsMAC 3MIB Radio MAC statistics.MIB Name OID Value Type DescriptionccuRadioGenRSSI 1 Integer Not used.ccuRadioGenTPI 2Integer Radio transmit power indicator.MIB Name OID Value Type DescriptionccuRadioDrvEvents 1 Counter Number of interrupts received (any interrupt) in the radiodriver ISR (Interrupt Service Routine)ccuRadioDrvRxComplete 2 Counter Number of receive complete interrupts received by theradio driver ISR.ccuRadioDrvTxComplete 3 Counter Number of transmit complete interrupts received by theradio driver ISR.ccuRadioDrvCmdComplete 4 Counter Number of command complete interrupts received by theradio driver ISR.ccuRadioDrvFatalEvent 5 Counter Number of fatal error interrupts received by the radiodriver ISR.ccuRadioDrvTxPowerRailEvent 6 Counter Number of Tx Power alarm interrupts received by theradio driver ISR.
206 APCD-LM043-4.0CCU Radio MAC Statistics GroupAll CCU Radio MAC Statistics Group MIB values are read only. All values in Table 68 areprefixed with 1.3.6.1.4.1.2979.11.3.3.Table 68 WaveRider CCU Radio MAC Statistics Group MIBccuRadioDrvUnknownEvent 7 Counter Number of received an unknown/no event interruptsreceived by the radio driver ISR.ccuRadioDrvSend 8 Counter Number of packets sent successfully by the radio drivertransmit queue.ccuRadioDrvSendQFull 9 Counter Number of packets not sent because the radio drivertransmit queue was full.ccuRadioDrvSendUnavailable 10 Counter Number of times invalid (null) mblks were sent to the radiodriver for transmission.ccuRadioDrvSendNotEnabled 11 Counter Number of times tried to send packets before the radiodriver was started; i.e., before the device was up andworking.ccuRadioDrvAMMPut 12 Counter Number of times a packet was successfully sent to theMAC-layer shared memory for transmission over the air.ccuRadioDrvAMMQFull 13 Counter Number of times a packet could not be sent to the MAC-layer shared memory because there were no transmitdescriptors left. Radio driver tries 5 more times to sendthe packet.ccuRadioDrvAMMQFullDiscard 14 Counter Number of times, after 5 attempts, a packet could not besent to the MAC-layer shared memory because therewere no transmit descriptors left. Packet is discarded.ccuRadioDrvGet 15 Counter Number of packets received from the MAC-layer sharedmemory.ccuRadioDrvQEmpty 16 Counter Number of times there was a receive interrupt, but nothingavailable to read out of the MAC-layer shared memory.ccuRadioDrvRx 17 Counter Number of successfully received packets.ccuRadioDrvRxNotAvailable 18 Counter Number of times the radio driver could not allocate anmblk (memory block) for storing a packet retrieved fromthe MAC-layer shared memory.ccuRadioDrvRxNotEnabled 19 Counter Number of times the radio driver received a receiveinterrupt, but the radio driver was not yet up and running.The received packet is ignored in this case.MIB Name OID Value Type DescriptionMIB Name OID ValueType DescriptionccuRadioMACRxDataPayloads 1 Counter Number of Ethernet frames received correctly fromthe air interface.ccuRadioMACRxCtrlPayloads 2 Counter Number of control payloads received correctly fromthe air interface.
APCD-LM043-4.0 207ccuRadioMACRxPayloadFailInvalidType 3 Counter Number of times an unknown type of payload wasreceived from the air interface.ccuRadioMACRxPayloadFailGiant 4 Counter Number of times a payload that was too long wasreceived from the air interface, and thereforediscarded.CCURadioMACNullRxDesc 5 Counter Number of times the internal MAC receive interfacewas corrupted.ccuRadioMACTxDataPayloads 6 Counter Number of Ethernet frames transmitted to the airinterface.ccuRadioMACTxCtrlPayloads 7 Counter Number of control payloads transmitted to the airinterface.ccuRadioMACTxPayloadFailInvalidType 8 Counter Number of times a payload of an unknown type wasdiscarded.ccuRadioMACTxPayloadFailGiant 9 Counter Number of times a payload that was too long wasdiscarded.ccRadioMACTxPayloadFailInvalidDesc 10 Counter Number of times the internal MAC transmit interfacewas corrupted.ccuRadioMACTxBufferFullOnArrival 11 Counter Number of transmit packets that were queued fordelivery.ccuRadioMACCmdTimeOuts 12 Counter Number of times the MAC-layer managementmessage was incomplete.ccuRadioMACCmdMissedIRQs 13 Counter Number of times there was no response to the MAC-layer management message.ccuRadioMACFalseCmdIRQs 14 Counter Number of times a hardware IRQ was detected withno message associated. This MIB parameter is usedprimarily by software development.ccuRadioMACCmdStatusErrors 15 Counter Number of times the MAC-layer managementmessage was rejected.ccuRadioMACFatalError 16 Counter Number of nonrecoverable MAC-layer errors, eachcausing a CCU reboot.17 Reserved.ccuRadioMACRxPacketsRedirected 18 Counter Number of times a reply from the EUM is receivedwith the correct HCRC (header cyclic redundancycheck).Note: The name of this MIB is an error and should beccuRadioMACRxPacketsDirected.ccuRadioMACRxPktsBroadcast 19 Counter Number of times an EUM succeeds in a randomaccess.ccuRadioMACRxPktsNoMatch 20 Counter Number of packets correctly received, but not directedto, this station.ccuRadioMACRxPktsDuplicate 21 Counter Number of duplicate payloads (see note 1) receivedand discarded. Indicates that a MAC layeracknowledgement was lost.MIB Name OID ValueType Description
208 APCD-LM043-4.0ccuRadioMACRxPktsRuntFail 22 Counter Number of packets received that were shorter thanthe minimum size.ccuRadioMACRxPktsLongFail 23 Counter Number of packets received that were longer than themaximum size.ccuRadioMACRxPktsHCRCFail 24 Counter Number of packets received with a MAC header CRCfailure (header corrupted).ccuRadioMACRxPktsICVFail 25 Counter Number of packets received with an encryption (WEP,wireless equivalent privacy) key mismatch (see note3).ccuRadioMACRxPktsFCSFail 26 Counter Number of packets received with a Frame CheckSequence failure (payload corrupted).ccuRadioMACRxPktsAssocFail 27 Counter Number of times a received packet had to bediscarded because too many EUMs were alreadyassociated.ccuRadioMACRxPktsIncomplete 28 Counter Number of times the receive DMA for a payload doesnot complete (internal error).ccuRadioMACRxPayloadsFailFull 29 Counter Number of times a received payload has to bediscarded because either no receive descriptor wasavailable, or there was not enough buffer space.ccuRadioMACRxPayloadsDelivered 30 Counter Number of payloads that this station receivedcorrectly.ccuRadioMACRxPktsEmpty 31 Counter Number of packets received with no payload.ccuRadioMACTxPkts 32 Counter Number of packets transmitted.ccuRadioMACTxPktsEmpty 33 Counter Number of packets transmitted with no payload.ccuRadioMACTxPayloads 34 Counter Number of payloads transmitted.ccuRadioMACTxPayloadsBroadcast 35 Counter Number of broadcast payloads transmitted.ccuRadioMACTxPayloads1Ok 36 Counter Number of payloads acknowledged after the firsttransmission.ccuRadioMACTxPayloads2Ok 37 Counter Number of payloads acknowledged after the secondtransmission.ccuRadioMACTxPayloads3Ok 38 Counter Number of payloads acknowledged after the thirdtransmission.ccuRadioMACTxPayloads4Ok 39 Counter Number of payloads acknowledged after the fourthtransmission.ccuRadioMACTxPayloadsFailRetry 40 Counter Number of payloads that failed to transmit due to theretry limit.ccuRadioMACTxPayloadsFailDeleted 41 Counter Number of payloads discarded from a queue that wasemptied when an EUM was deregistered due to non-response or deauthorization.ccuRadioMACTxPayloadsBadParam 42 Counter Number of payloads returned to the host becausethey are improperly formed (internal error).ccuRadioMACTxPayloadsVnetInactive 43 Counter Number of payloads returned to the host because thevirtual net was not active (internal error).MIB Name OID ValueType Description
APCD-LM043-4.0 209Notes:•Apacket is the basic unit of transmission. A packet may or may not contain a payload.Apayload is user data, which may be an Ethernet frame or a logical link layer controlmessage.• WEP is not supported in this release.• The CCU maintains a transmit queue for each EUM. The length of this queue islimited, to prevent one EUM from consuming all the resources and impacting serviceto other EUMs. Discards indicate excessive load by one EUM, possibly due to largeTCP windows.• Registration occurs once per EUM and/or CCU boot time. Deregistration may occur ifan EUM is not authorized (a registration/deregistration request pair occurs periodicallywhile that EUM is powered ON) or if the EUM does not respond to multipleconsecutive polls, such as when it is powered OFF.• Association occurs when there is traffic to send to or from an EUM. Disassociationoccurs if there is no traffic to or from an EUM for a short period of time.ccuRadioMACTxPayloadsAssocFail 44 Counter Number of payloads returned to the host because toomany other EUMs were already associated.ccuRadioMACTxPayloadsTimeout 45 Counter Number of payloads returned to the host because oftimeout.ccuRadioMACTxPayloadQueueTooLong 46 Counter Number of payloads returned to the host because thetransmit queue for the EUM was too long (see note 4).47 Counter Not used.ccuRadioMACReplyOrRssiTimeout 48 Counter Number of times that no response was received to adirected poll.ccuRadioMACRestarts 49 Counter Number of times that the MAC layer recovered froman internal error or unexpected event.ccuRadioMACRegRequests 50 Counter Number of registration requests received (see note 5).ccuRadioMACRegResponse 51 Counter Number of registration responses transmitted (seenote 5).ccuRadioMACDeregRequests 52 Counter Number of deregistration requests transmitted (seenote 5).ccuRadioMACDeregInits 53 Counter Number of times no response was received from anEUM, after multiple polls (see note 5). This statisticindicates a poor radio link to one or more EUMs.ccuRadioMACDisassociationRequests 54 Counter Number of disassociation requests transmitted (seenote 6).ccuRadioMACDisassociationInits 55 Counter Number of times the CCU has determined than anEUM should be disassociated (see note 6).MIB Name OID ValueType Description
210 APCD-LM043-4.0CCU Ethernet Statistics GroupAll CCU Ethernet Statistics Group MIB values are read only. All values in Table 69 are prefixedwith 1.3.6.1.4.1.2979.11.4.Table 69 WaveRider CCU Ethernet Statistics Group MIBMIB Name OID ValueType DescriptionccuEtherInterrupts 1 Counter Total number of interrupts received by the Ethernetdriver ISR, interrupt service routine.ccuEtherRxInterrupt 2 Counter Number of receive complete interrupts received by theEthernet driver ISR.ccuEtherRxOverrunInterrupt 3 Counter Number of overrun interrupts received by the Ethernetdriver ISR. An overrun occurs when a received packethas exceeded the packet size, or the processor hasmissed one or more packets.ccuEtherRxInProgressInterrupt 4 Counter Number of times a receive complete interrupt wasreceived by the Ethernet driver ISR before the currentpacket was finished.ccuEtherTxCompleteInterrupt 5 Counter Number of normal transmit interrupts received by theEthernet driver ISR.ccuEtherTxErrorInterrupt 6 Counter Number of transmit error interrupts received by theEthernet driver ISR.ccuEtherTxCarrierLostInterrupt 7 Counter Number of transmit carrier lost interrupts received bythe Ethernet driver ISR.ccuEtherTxAllocInterrupt 8 Counter Number of transmit allocation complete interruptsreceived by the Ethernet driver ISR.ccuEtherTxEPHInterrupt 9 Counter Number of transmit EPH interrupts (Ethernet protocolhandler interrupts) received by the Ethernet driverISR.ccuEtherTxERCVInterrupts 10 Counter Number of transmit ERCV interrupts (early receiveinterrupts) received by the Ethernet driver ISR..ccuEtherRxData 11 Counter Number of packets received and accepted by the IPstack.ccuEtherRxDataError 12 Counter Number of packets received and rejected by the IPstack because of errors.ccuEtherRxDataMblkAllocError 13 Counter Number of packets lost due to insufficient memoryresources.ccuEtherRxDataLenghtError 14 Counter Number of packets received that violate Ethernetpacket length rules.ccuEtherRxDiscards 15 Counter Number of packets discarded because the unit wasnot ready to receive data.ccuEtherTxData 16 Counter Number of packets received and placed on thetransmit queue.ccuEtherTxDataQFull 17 Counter Number of packets discarded because the transmitqueue was full.
APCD-LM043-4.0 211CCU Modem Information MIBAll values in Table 70 are prefixed with 1.3.6.1.4.1.2979.11.5.Table 70 WaveRider CCU Modem Information MIBCCU Registration Information MIBAll CCU Registration MIB values are read only. All values in Table 71 are prefixed with1.3.6.1.4.1.2979.11.5.1Table 71 WaveRider CCU Registration Information MIBCCU Registration TableAll CCU Registration Table Group MIB values are read only. All values in Table 72 are prefixedwith 1.3.6.1.4.1.2979.11.5.1.2.Table 72 WaveRider CCU Registration Table MIBccuEtherTxOk 18 Counter Number of packets sent correctly.ccuEtherTxTimeout 19 Counter Number of times the packet transmit has timed out.ccuEtherTxSemWait 20 Counter Number of times a transmit semaphore could not betaken in the timeout period.MIB Name OID ValueType DescriptionMIB Name OID ValueType DescriptionccuRegistration 1 MIB Registration Table.ccuAuthorization 2MIB Authorization Table.MIB Name OID ValueType DescriptionccuRegistrationCount 1 Integer Number of connections in the Registration Table.ccuRegistrationTable 2MIBMIB Name OID ValueType AcceptedValues DescriptionccuRegistrationIndex 1 Integer Index of entry in Registration Table.ccuRegistrationId 2Integer 000000-FFFFFF Integer representation of the EUM ID,normally displayed in hexadecimal.
212 APCD-LM043-4.0CCU Authorization Information MIBAll CCU Authorization MIB values are read only. All values in Table 73 are prefixed with1.3.6.1.4.1.2979.11.5.2.Table 73 WaveRider CCU Authorization Table MIBCCU Authorization TableAll CCU Authorization Table Group MIB values are read only. All values in Table 74 areprefixed with 1.3.6.1.4.1.2979.11.5.2.2.Table 74 WaveRider CCU Authorization Table MIBCCU RFC MIB-II TrapsRFC MIB-II TrapsTable 75 CCU RFC MIB-II TrapsMIB Name OID ValueType DescriptionccuAuthorizationCount 1 Integer Number of authorized EUMs.ccuAuthorizationTable 2MIBMIB Name OID Type AcceptedValues DescriptionccuAuthorizationIndex 1 Integer Index of entry in Authorization Table.ccuAuthorizationId 2Integer 000000-FFFFFFInteger representation of the EUM ID, normallydisplayed in hexadecimal.ccuAuthorizationGosClass 3Integer 1: Best Effort2: Bronze3: Silver4: Gold5: DeniedThe grade of service associated with the EUM.MIB Name OID DescriptioncoldStart 1.3.6.1.2.1.11.0.0 PowerCycleorPowerOn.authenticationFailure 1.3.6.1.2.1.11.0.4 An SNMP request has failed due to improperauthentication.
APCD-LM043-4.0 213WaveRider EUM Enterprise MIBsThe structure of the EUM MIBs is illustrated in Figure 52.Figure 52 EUM MIBsEach of the MIBs in Figure 52 is discussed in the following sections.EUM Base MIBAll values in Table 76, which are read only, are prefixed with 1. 3. 6.1.4.1. 2979.12.Table 76 WaveRider EUM Base MIBMIB Name OID Value Type DescriptioneumGlobal 1 MIB EUM general data.eumRadioConfig 2MIB EUM configuration and setup data.eumRadioStats 3MIB EUM radio statistics.eumEtherStats 4MIB EUM Ethernet statisticseumModems 5MIB EUM registration and authorization information.WaveRider (2979)waveridereumGlobaleum3000pmacglobeumRadioConfigeum3000pmacradcfgeumRadioStatseum3000pmacrseumEtherStatseum3000pmaceseumRadioStatsGeneraleum3000pmacrsgeneumRadioStatsDrivereum3000pmacrsdrveumRadioStatsAtmeleum3000pmacrsatmelEnterprise (1.3.6.1.4.1)LMS3000 EUMeum3000pmacMIB NameMIB File PrefixLegend
214 APCD-LM043-4.0EUM General Information GroupAll values in Table 77 are prefixed with 1.3.6.1.4.1.2979.12.1.Table 77 WaveRider EUM General Information Enterprise MIBsEUM Radio Configuration GroupAll EUM Radio Configuration Group MIB values are read only. All values in Table 78 areprefixed with 1.3.6.1.4.1.2979.12.2.Table 78 WaveRider EUM Radio Configuration Enterprise MIBsMIB Name OID Value Type Status AcceptedValues DescriptioneumSerialNumber 1 String R EUM hardware serial numbereumSoftwareVersion 2String REUM firmware version.eumHardwareVersion 3String REUM hardware version.eumExtraFunctions 4Integer R 0 A mask for extra functionality that maybe added at a later date. For now, itreturns ‘0’.eumGlobalStatus 5Integer R1: startup2: dead3: ok4: suspectCurrent status of the radio interface.For now, this field returns ‘ok’.eumGlobalSaveCounter 6Counter RA count of the number of times theconfiguration is saved. Initially, this fieldalways returns ‘0’.eumGlobalConfigFiles 7String RA list of configuration files for the EUM.The list is delimited with a semicolon;i.e., “basic.cfg;route.cfg, ...”eumGlobalReset 8Integer W1: reset Not functional at this time.eumGlobalReload 9Integer W1: reload Not functional at this time.MIB Name OID ValueType AcceptedValues DescriptioneumRadioConfigVersion 1 String Radio firmware version.eumRadioConfigMacAirlinkAddr 2PhysAddressMAC address Radio MAC address.eumRadioConfigFrequency 3Integer Radio frequency in use (in 1/10ths of aMHz)eumRadioConfigDomain 4Integer 0: IEEE1: FCC or IC/CanadaCurrent regulatory domain for which theradio is configured.eumRadioHardwareRevision 5String Radio hardware revision.
APCD-LM043-4.0 215EUM Radio Statistics GroupAll EUM Radio Statistics Group MIB values are read only. All values in Table 79 are prefixedwith 1.3.6.1.4.1.2979.12.3.Table 79 WaveRider EUM Radio Statistics MIBEUM Radio General Statistics GroupAll EUM Radio General Statistics Group MIB values are read only. All values in Table 80 areprefixed with 1.3.6.1.4.1.2979.12.3.1.Table 80 WaveRider EUM Radio General Statistics Group MIBEUM Radio Driver Statistics GroupAll EUM Radio Driver Statistics Group MIB values are read only. All values in Table 81 areprefixed with 1.3.6.1.4.1.2979.12.3.2.Table 81 WaveRider EUM Radio Driver Statistics Group MIBMIB Name OID ValueType DescriptioneumRadioStatsGeneral 1 MIB General radio statistics.eumRadioStatsDriver 2MIB Radio driver statisticseumRadioStatsMAC 3MIB Radio MAC statistics.MIB Name OID Value Type DescriptioneumRadioGenRSSI 1 Integer Radio receive signal strength indicator, in dBm. ‘0’indicates no signal present.MIB Name OID Value Type DescriptioneumRadioDrvEvents 1 Counter Number of interrupts received (any interrupt) in the radiodriver ISR (Interrupt Service Routine)eumRadioDrvRxComplete 2 Counter Number of receive complete interrupts received by theradio driver ISR.eumRadioDrvTxComplete 3 Counter Number of transmit complete interrupts received by theradio driver ISR.eumRadioDrvCmdComplete 4 Counter Number of command complete interrupts received by theradio driver ISR.eumRadioDrvFatalEvent 5 Counter Number of fatal error interrupts received by the radiodriver ISR.eumRadioDrvTxPowerRailEvent 6 Counter Number of Tx Power alarm interrupts received by the radiodriver ISR.
216 APCD-LM043-4.0EUM Radio MAC Statistics GroupAll EUM Radio MAC Statistics Group MIB values are read only. All values in Table 82 areprefixed with 1.3.6.1.4.1.2979.12.3.3.Table 82 WaveRider EUM Radio MAC Statistics Group MIBeumRadioDrvUnknownEvent 7 Counter Number of received an unknown/no event interruptsreceived by the radio driver ISR.eumRadioDrvSend 8 Counter Number of packets sent successfully by the radio drivertransmit queue.eumRadioDrvSendQFull 9 Counter Number of packets not sent because the radio drivertransmit queue was full.eumRadioDrvSendUnavailable 10 Counter Number of times invalid (null) mblks were sent to the radiodriver for transmission.eumRadioDrvSendNotEnabled 11 Counter Number of times tried to send packets before the radiodriver was started; i.e., before the device was up andworking.eumRadioDrvAMMPut 12 Counter Number of times a packet was successfully sent to theMAC-layer shared memory for transmission over the air.eumRadioDrvAMMQFull 13 Counter Number of times a packet could not be sent to the MAC-layer shared memory because there were no transmitdescriptors left. Radio driver tries 5 more times to send thepacket.eumRadioDrvAMMQFullDiscard 14 Counter Number of times, after 5 attempts, a packet could not besent to the MAC-layer shared memory because there wereno transmit descriptors left. Packet is discarded.eumRadioDrvGet 15 Counter Number of packets received from the MAC-layer sharedmemory.eumRadioDrvQEmpty 16 Counter Number of times there was a receive interrupt, but nothingavailable to read out of the MAC-layer shared memory.eumRadioDrvRx 17 Counter Number of successfully received packets.eumRadioDrvRxNotAvailable 18 Counter Number of times the radio driver could not allocate anmblk (memory block) for storing a packet retrieved fromthe MAC-layer shared memory.eumRadioDrvRxNotEnabled 19 Counter Number of times the radio driver received a receiveinterrupt, but the radio driver was not yet up and running.The received packet is ignored in this case.MIB Name OID Value Type DescriptionMIB Name OID ValueType DescriptioneumRadioMACRxDataPayloads 1 Counter Number of Ethernet frames received correctly fromthe air interface.eumRadioMACRxCtrlPayloads 2 Counter Number of control payloads received correctly fromthe air interface.
APCD-LM043-4.0 217eumRadioMACRxPayloadFailInvalidType 3 Counter Number of times an unknown type of payload wasreceived from the air interface.eumRadioMACRxPayloadFailGiant 4 Counter Number of times a payload that was too long wasreceived from the air interface, and thereforediscarded.eumRadioMACNullRxDesc 5 Counter Number of times the internal MAC receive interfacewas corrupted.eumRadioMACTxDataPayloads 6 Counter Number of Ethernet frames transmitted to the airinterface.eumRadioMACTxCtrlPayloads 7 Counter Number of control payloads transmitted to the airinterface.eumRadioMACTxPayloadFailInvalidType 8 Counter Number of times a payload of an unknown type wasdiscarded.eumRadioMACTxPayloadFailGiant 9 Counter Number of times a payload that was too long wasdiscarded.ccRadioMACTxPayloadFailInvalidDesc 10 Counter Number of times the internal MAC transmit interfacewas corrupted.eumRadioMACTxBufferFullOnArrival 11 Counter Number of transmit packets that were queued fordelivery.eumRadioMACCmdTimeOuts 12 Counter Number of times the MAC-layer managementmessage was incomplete.eumRadioMACCmdMissedIRQs 13 Counter Number of times there was no response to the MAC-layer management message.eumRadioMACFalseCmdIRQs 14 Counter Number of times a hardware IRQ was detected withno message associated. This MIB parameter is usedprimarily by software development.eumRadioMACCmdStatusErrors 15 Counter Number of times the MAC-layer managementmessage was rejected.eumRadioMACFatalError 16 Counter Number of nonrecoverable MAC-layer errors, eachrequiring an EUM reboot.17 Reserved.eumRadioMACRxPacketsRedirected 18 Counter Number of times a poll for the EUM is received fromthe CCU with the correct HCRC.eumRadioMACRxPktsBroadcast 19 Counter Number of broadcast packets (see note 1) receivedwith the correct HCRC.eumRadioMACRxPktsNoMatch 20 Counter Number of packets correctly received, but not directedto, this station.eumRadioMACRxPktsDuplicate 21 Counter Number of duplicate payloads (see note 1) receivedand discarded. Indicates that a MAC layeracknowledgement was lost.eumRadioMACRxPktsRuntFail 22 Counter Number of packets received that were shorter thanthe minimum size.eumRadioMACRxPktsLongFail 23 Counter Number of packets received that were longer than themaximum size.MIB Name OID ValueType Description
218 APCD-LM043-4.0eumRadioMACRxPktsHCRCFail 24 Counter Number of packets received with a MAC header CRCfailure (header corrupted).eumRadioMACRxPktsICVFail 25 Counter Number of packets received with an encryption (WEP,wireless equivalent privacy) key mismatch (see note3).eumRadioMACRxPktsFCSFail 26 Counter Number of packets received with a Frame CheckSequence failure (payload corrupted).27 Not used. Returns a value of ‘0’.eumRadioMACRxPktsIncomplete 28 Counter Number of times the receive DMA for a payload doesnot complete (internal error).eumRadioMACRxPayloadsFailFull 29 Counter Number of times a received payload has to bediscarded because either no receive descriptor wasavailable, or there was not enough buffer space.eumRadioMACRxPayloadsDelivered 30 Counter Number of payloads that this station receivedcorrectly.eumRadioMACRxPktsEmpty 31 Counter Number of packets received with no payload.eumRadioMACTxPkts 32 Counter Number of packets transmitted.eumRadioMACTxPktsEmpty 33 Counter Number of packets transmitted with no payload.eumRadioMACTxPayloads 34 Counter Number of payloads transmitted.35 Not used. Returns a value of ‘0’.eumRadioMACTxPayloads1Ok 36 Counter Number of payloads acknowledged after the firsttransmission.eumRadioMACTxPayloads2Ok 37 Counter Number of payloads acknowledged after the secondtransmission.eumRadioMACTxPayloads3Ok 38 Counter Number of payloads acknowledged after the thirdtransmission.eumRadioMACTxPayloads4Ok 39 Counter Number of payloads acknowledged after the fourthtransmission.eumRadioMACTxPayloadsFailRetry 40 Counter Number of payloads that failed to transmit due to theretry limit.41 Not used. Returns a value of ‘0’.eumRadioMACTxPayloadsBadParam 42 Counter Number of payloads returned to the host becausethey are improperly formed (internal error).43 Not used. Returns a value of ‘0’.44 Not used. Returns a value of ‘0’.eumRadioMACTxPayloadsTimeout 45 Counter Number of payloads returned to the host because oftimeout.46 Not used. Returns a value of ‘0’.47 Not used. Returns a value of ‘0’MIB Name OID ValueType Description
APCD-LM043-4.0 219Notes:•Apacket is the basic unit of transmission. A packet may or may not contain a payload.Apayload is user data, which may be an Ethernet frame or a logical link layer controlmessage.• WEP is not supported in this release.• Registration occurs once per EUM and/or CCU boot time. Deregistration may occur ifan EUM is not authorized (a registration/deregistration request pair occurs periodicallywhile that EUM is powered ON) or if the EUM does not respond to multipleconsecutive polls, such as when it is powered OFF.• Association occurs when there is traffic to send to or from an EUM. Disassociationoccurs if there is no traffic to or from an EUM for a short period of time.EUM Ethernet Statistics GroupAll EUM Ethernet Statistics Group MIB values are read only. All values in Table 83 are prefixedwith 1.3.6.1.4.1.2979.12.4.Table 83 WaveRider CCU Ethernet Statistics Group MIBeumRadioMACReplyOrRssiTimeout 48 Counter Number of times the RSSI timer expired because theEUM had not received anything from the CCU formore than 0.5s.eumRadioMACRestarts 49 Counter Number of times that the MAC layer recovered froman internal error or unexpected event.eumRadioMACRegRequests 50 Counter Number of registration requests transmitted (see note4).eumRadioMACRegResponse 51 Counter Number of registration responses received (see note4).eumRadioMACDeregRequests 52 Counter Number of deregistration requests received (see note4).53 Not used. Returns a value of ‘0’.eumRadioMACDisassociationRequests 54 Counter Number of disassociation requests received (see note5).55 r Not used. Returns a value of ‘0’.MIB Name OID ValueType DescriptionMIB Name OID ValueType DescriptioneumEtherInterrupts 1 Counter Total number of interrupts received by the Ethernetdriver ISR, interrupt service routine.eumEtherRxInterrupt 2 Counter Number of receive complete interrupts received by theEthernet driver ISR.
220 APCD-LM043-4.0eumEtherRxOverrunInterrupt 3 Counter Number of overrun interrupts received by the Ethernetdriver ISR. An overrun occurs when a received packethas exceeded the packet size, or the processor hasmissed one or more packets.eumEtherRxInProgressInterrupt 4 Counter Number of times a receive complete interrupt wasreceived by the Ethernet driver ISR before the currentpacket was finished.eumEtherTxCompleteInterrupt 5 Counter Number of normal transmit interrupts received by theEthernet driver ISR.eumEtherTxErrorInterrupt 6 Counter Number of transmit error interrupts received by theEthernet driver ISR.eumEtherTxCarrierLostInterrupt 7 Counter Number of transmit carrier lost interrupts received bythe Ethernet driver ISR.eumEtherTxAllocInterrupt 8 Counter Number of transmit allocation complete interruptsreceived by the Ethernet driver ISR.eumEtherTxEPHInterrupt 9 Counter Number of transmit EPH interrupts (Ethernet protocolhandler interrupts) received by the Ethernet driverISR.eumEtherTxERCVInterrupts 10 Counter Number of transmit ERCV interrupts (early receiveinterrupts) received by the Ethernet driver ISR..eumEtherRxData 11 Counter Number of packets received and accepted by the IPstack.eumEtherRxDataError 12 Counter Number of packets received and rejected by the IPstack because of errors.eumEtherRxDataMblkAllocError 13 Counter Number of packets lost due to insufficient memoryresources.eumEtherRxDataLenghtError 14 Counter Number of packets received that violate Ethernetpacket length rules.eumEtherRxDiscards 15 Counter Number of packets discarded because the unit wasnot ready to receive data.eumEtherTxData 16 Counter Number of packets received and placed on thetransmit queue.eumEtherTxDataQFull 17 Counter Number of packets discarded because the transmitqueue was full.eumEtherTxOk 18 Counter Number of packets sent correctly.eumEtherTxTimeout 19 Counter Number of times the packet transmit has timed out.eumEtherTxSemWait 20 Counter Number of times a transmit semaphore could not betaken in the timeout period.MIB Name OID ValueType Description
APCD-LM043-4.0 221EUM RFC MIB-II TrapsRFC MIB-II TrapsTable 84 EUM RFC MIB-II TrapsMIB Name OID DescriptioncoldStart 1.3.6.1.2.1.11.0.0 PowerCycleorPowerOnauthenticationFailure 1.3.6.1.2.1.11.0.4 An SNMP request has failed due to improperauthentication
—This page is intentionally left blank —
APCD-LM043-4.0 223Appendix H Operating StatisticsThe CCU and EUM provide a comprehensive set of operating statistics for each of thefollowing:• Ethernet Port• Radio Driver•MACInterface• Routing/Bridging Protocol• Network Interface• System Load (Radio Meter)These statistics can be used as a diagnostic and troubleshooting tool when systemperformance 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 statisticsare also available in the CCU and EUM MIBs, if you want to monitor the LMS4000 900 MHzradio network from an SNMP manager.CAUTION: Each CCU and EUM statistic is a maximum 32-bitnumber (maximum 4,294,967,296). If a statistics counter exceedsits maximum value, the counter resets to zero and begins again.When this occurs, you must either take the rollover into account, orreset the statistics to re-synchronize the counters. To resetstatistics, type stats clear at the command prompt and press Enter.As a result of the above, the system uptime rolls over about every 8 days. By checking thesystem log file, you can calculate the actual up time, after the unit has been up for more than 8days.
224 APCD-LM043-4.0To 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 obtainingspecific sets of statistics (Ethernet, Radio, and so on).Ethernet StatisticsEthernet Statistics present operational information about data passing through the CCU andEUM Ethernet ports. These statistics are described in Table 85.As indicated in Table 85, all of the Ethernet statistics are available in a WaveRider MIB.Table 85 Ethernet StatisticsStatistic Availablein MIB DescriptionInterrupts 3Total number of interrupts received by theEthernet driver ISR, interrupt service routine.RX Interrupts 3Number of receive complete interruptsreceived by the Ethernet driver ISR.RX Overrun Interrupts 3Number of overrun interrupts received by theEthernet driver ISR. An overrun occurs when areceived packet has exceeded the packetsize, or the processor has missed one or morepackets.RX In Progress Interrupts 3Number of times a receive complete interruptwas received by the Ethernet driver ISRbefore the current packet was finished.TX Complete Interrupts 3Number of normal transmit interrupts receivedby the Ethernet driver ISR.TX Error Interrupts 3Number of transmit error interrupts receivedby the Ethernet driver ISR.TX Carrier Lost Interrupts 3Number of transmit carrier lost interruptsreceived by the Ethernet driver ISR.TX Alloc Interrupts 3Number of transmit allocation completeinterrupts received by the Ethernet driver ISR.TX EPH Interrupts 3Number of transmit EPH interrupts (Ethernetprotocol handler interrupts) received by theEthernet driver ISR.TX ERCV Interrupts 3Number of transmit ERCV interrupts (earlyreceive interrupts) received by the Ethernetdriver ISR.
APCD-LM043-4.0 225To view the Ethernet statistics:CCU> stats ethernet-------------------- Ethernet Statistics -----------------------Interrupts : 288647RX Interrupts : 151103RX Overrun Interrupts : 0RX In Progress Interrupts : 4676TX Complete Interrupts : 133189TX Error Interrupts : 0TX Carrier Lost Interrupts : 0TX Alloc Interrupts : 0TX EPH Interrupts : 0TX ERCV Interrupts : 0RX Data : 158095RX Data Error : 0RX Data Mblk Alloc Error : 0RX Data Length Error : 0RX Discards (No Space Available) : 18TX Data : 133189TX Data Q Full : 0TX'D OK : 133189TX Timeout : 0TX Sem Wait : 0CCU>RX Data 3Number of packets received and accepted bythe IP stack.RX Data Error 3Number of packets received and rejected bythe IP stack because of errors.RX Data Mblk Error 3Number of packets lost due to insufficientmemory resources.RX Data Length Error 3Number of packets received that violateEthernet packet length rules.RX Discards 3Number of packets discarded because the unitwas not ready to receive data.TX Data 3Number of packets received and placed on thetransmit queue.TX Data Q Full 3Number of packets discarded because thetransmit queue was full.TX’D OK 3Number of packets sent correctly.TX Timeout 3Number of times the packet transmit has timedout.TX Sem Wait 3Number of times a transmit semaphore couldnot be taken in the timeout period.Statistic Availablein MIB Description
226 APCD-LM043-4.0Radio Driver StatisticsRadio Driver Statistics present operational information about data passing through the CCUand EUM radio driver and ports. These statistics are described in Table 86.As indicated in Table 86, all of the Radio Driver statistics are available in a WaveRider MIB.Table 86 Radio Driver StatisticsStatistic Availablein MIB DescriptionEvents 3Number of interrupts received (any interrupt)in the radio driver ISR (Interrupt ServiceRoutine)Rx Complete Event 3Number of receive complete interruptsreceived by the radio driver ISR.Tx Complete Event 3Number of transmit complete interruptsreceived by the radio driver ISR.Cmd Complete Event 3Number of command complete interruptsreceived by the radio driver ISR.Fatal Error Event 3Number of fatal error interrupts received bythe radio driver ISR.Tx Power Rail Event 3Number of Tx Power alarm interrupts receivedbytheradiodriverISR.Unknown Event 3Number of received an unknown/no eventinterrupts received by the radio driver ISR.Send 3Number of packets sent successfully by theradio driver transmit queue.Send Q Full 3Number of packets not sent because the radiodriver transmit queue was full.Send End MBlk Unavailable 3Number of times invalid (null) mblks (memoryblocks) were sent to the radio driver fortransmission.Send Not Enabled 3Number of times tried to send packets beforethe radio driver was started; i.e., before thedevice was up and working.AMM Put 3Number of times a packet was successfullysent to the MAC-layer shared memory fortransmission over the air.AMM Q Full 3Number of times a packet was delayed beforebeingplacedintheMAC-layersharedmemorydue to a full transmit queue.
APCD-LM043-4.0 227To view the radio driver statistics:CCU> stats ra------------------- Radio Driver Statistics ---------------------Events : 376194Rx Complete Event : 184886Tx Complete Event : 189052Cmd Complete Event : 0FATAL ERROR Event : 0Tx Power Rail Event : 0Unknown Event : 2348Send : 189143Send Q Full : 0Send MBlk Unavailable : 0Send Not Enabled : 0AMM Put : 189143AMM Q Full : 0AMM Q Full Discard : 0AMM get : 184886AMM Q Empty : 99Receive : 184886Receive MBlk Unavailable : 0Receive Not Enabled : 0CCU>AMM Q Full Discard 3Number of times a packet was discarded dueto the MAC-layer shared memory transmitqueue not draining.AMM Get 3Number of packets received from the MAC-layer shared memory.AMM Q Empty 3Number of times there was a receive interrupt,but nothing available to read out of the MAC-layer shared memory.Receive 3Number of successfully received packets.Receive MBlk Unavailable 3Number of times the radio driver could notallocate an mblk (memory block) for storing apacket retrieved from the MAC-layer sharedmemory.Receive Not Enabled 3Number of times the radio driver received areceive interrupt, but the radio driver was notyet up and running. The received packet isignored in this case.Statistic Availablein MIB Description
228 APCD-LM043-4.0MAC Interface StatisticsMAC Interface Statistics present operational information about data which is processed by theCCU and EUM MAC layer. These statistics are described in Table 87.As noted in Table 87, most of the MAC interface statistics are available in a WaveRider MIB.Table87 MACInterfaceStatisticsStatistic Availablein MIB Description (see note 2)Rx Data Payloads 3Number of data payloads received correctlyfrom the air interface.Rx Ctrl Payloads 3Number of control payloads received correctlyfrom the air interface.Rx Payload Fail InvalidType3Number of times an unknown type of payloadwas received from the air interface.Rx Payload Fail Giant 3Number of times a payload that was too longwas received from the air interface, andtherefore discarded.Null Rx Descriptors 3Number of times the internal MAC receiveinterface was corrupted.Tx Data Payloads 3Number of data payloads transmitted to the airinterface.Tx Ctrl Payloads 3Number of control payloads transmitted to theair interface.Tx Payload Fail InvalidType3Number of times a payload of an unknowntype was discarded.Tx Payload Fail Giant 3Number of times a payload that was too longwas discarded.Tx Payload Fail InvalidDesc3Number of times the internal MAC transmitinterface was corrupted.Atmel Tx Buffer full onarrival3Number of transmit packets that were queuedfor delivery.Command Time Outs 3Number of times the MAC-layer managementmessage was incomplete.Command Missed IRQs 3Number of times there was no response to theMAC-layer management message.False Command IRQs 3Number of times a command failed becausethe previous command was still beingprocessed.Command Status Errors 3Number of times the MAC-layer managementmessage was rejected.
APCD-LM043-4.0 229Atmel Fatal Error Not used.Unused Statistic Not used.rxPktsDirected 3At the CCU, the number of times a reply fromthe EUM is received with the correct HCRC(header cyclic redundancy check). In theEUM, the number of times a poll for the EUMis received from the CCU with the correctHCRC.rxPktsBroadcast 3At the CCU, the number of times an EUMsucceeds in a random access. Note that allEUM packets are directed to the CCU, notbroadcast. At the EUM, the number ofbroadcast packets (see note 1) received withthe correct HCRC. These are also randomaccess opportunities.rxPktsNoMatch 3Number of packets correctly received, but notdirected to, this station.rxPktsDuplicate 3Number of duplicate payloads (see note 1)received and discarded. Indicates that a MAClayer acknowledgement was lost.rxPktsRuntFail 3Number of packets received that were shorterthan the minimum size.rxPktsLongFail 3Number of packets received that were longerthan the maximum size.rxPktsHCRCFail 3Number of packets received with a MACheader CRC failure (header corrupted).rxPktsICVFail 3Number of packets received with anencryption (WEP, wireless equivalent privacy)keymismatch(seenote3).rxPktsFCSFail 3Number of packets received with a FrameCheck Sequence failure (payload corrupted).rxPktsAssocFail 3Number of times a received packet had to bediscarded because too many EUMs werealready associated.[CCUonly]rxPktsIncomplete 3Number of times the receive DMA for apayload does not complete (internal error).rxPayloadsFailFull 3Number of times a received payload has to bediscarded because either no receivedescriptor was available, or there was notenough buffer space.rxPayloadsDelivered 3Number of payloads that this station receivedcorrectly.Statistic Availablein MIB Description (see note 2)
230 APCD-LM043-4.0rxPktsEmpty 3Number of packets received that are directedto this station, but that did not contain apayload.txPkts 3Number of packets transmitted.txPktsEmpty 3Number of packets transmitted with nopayload.txPayloads 3Number of payloads transmitted.txPayloadsBCast 3Number of broadcast payloads transmitted.[CCU only]txPayloads1Ok 3Number of payloads acknowledged after thefirst transmission.txPayloads2Ok 3Number of payloads acknowledged after thesecond transmission.txPayloads3Ok 3Number of payloads acknowledged after thethird transmission.txPayloads4Ok 3Number of payloads acknowledged after thefourth transmission.txPayloadsFailRetry 3Number of payloads that failed to transmit dueto the retry limit.txPayloadsFailAssocDeleted 3Number of payloads that were discardedbecause the EUM was unreachable ordeauthorized. [CCU only]txPayloadsFailBadParam 3Number of payloads returned to the hostbecause they are improperly formed (internalerror).txPayloadsFailVnetInactive 3Number of payloads returned to the hostbecause the virtual net was not active (internalerror). [CCU only]txPayloadsFailAssocFail 3Number of payloads returned to the hostbecause too many other EUMs were alreadyassociated.[CCUonly]txPayloadsFailTimeout 3Number of payloads returned to the hostbecause of timeout.txPayloadsFailQueueTooLong 3Number of payloads returned to the hostbecause the transmit queue for the EUM wastoo long (see note 4). [CCU only]txPayloadsEmpty Not used.Statistic Availablein MIB Description (see note 2)
APCD-LM043-4.0 231Notes:•Apacket is the basic unit of transmission. A packet may or may not contain a payload.Apayload is user data, which may be an Ethernet frame or a logical link layer controlmessage.• WEP is not supported in this release.replyOrRssiTimeouts 3At the CCU, the number of times that noresponse was received to a directed poll. Atthe EUM, the number of times the RSSI timerexpired because the EUM had not receivedanything from the CCU for more than 0.5s.restarts 3Number of times that a PAI (physicalattachment interface) state machine restartoccurred (internal error).registrationRequests 3At the CCU, the number of registrationrequests received (see note 5). At the EUM,the number of registration requeststransmitted (see note 5).registrationResponses 3At the CCU, the number of registrationresponses transmitted (see note 5). At theEUM, the number of registration responsesreceived (see note 5).deregistrationRequests 3At the CCU, the number of deregistrationrequests transmitted (see note 5). At the EUM,the number of deregistration requestsreceived (see note 5).deregistrationInits 3Number of times no response was receivedfrom an EUM, after multiple polls (see note 5).[CCU only]disassociationRequests 3At the CCU, the number of disassociationrequests transmitted (see note 6). At the EUM,the number of disassociation requestsreceived (see note 6).disassociationInits 3Number of times the CCU has determinedthan an EUM should be disassociated (seenote 6). [CCU only]newAssociations 3At the CCU, the number of times a newassociation is created (see note 6). At theEUM, the number of transitions to associatedstate (see note 6).currentAssociations 3Number of EUMs currently associated + 1(see note 6). The one additional association isfor “broadcast”. [CCU only]unexpectedEvents 3Number of internal unexpected events.Statistic Availablein MIB Description (see note 2)
232 APCD-LM043-4.0• The CCU maintains a transmit queue for each EUM. The length of this queue islimited, to keep one EUM from consuming all the resources and impacting otherEUMs. Discards indicate excessive load by one EUM, possibly due to large TCPwindows.• Registration occurs once per EUM and/or CCU boot time. Deregistration may occur ifan EUM is not authorized (a registration/deregistration request pair occurs periodicallywhile that EUM is powered ON) or if the EUM does not respond to multipleconsecutive polls, such as when it is powered OFF.• Association occurs when there is traffic to send to or from an EUM. Disassociationoccurs if there is no traffic to or from an EUM for a short period of time.To view the MAC Interface Statistics:CCU> stats mac----------------- MAC Interface Statistics --------------------Rx Data Payloads : 132323Rx Ctrl Payloads : 5702Rx Payload Fail Invalid Type : 0Rx Payload Fail Giant : 0Null Rx Descriptors : 0Tx Data Payloads : 138245Tx Ctrl Payloads : 5702Tx Payload Fail Invalid Type : 0Tx Payload Fail Giant : 0Tx Payload Fail Invalid Desc : 0Atmel Tx Buffer full on arrival : 0Command time outs : 0Command missed IRQs : 0False Command IRQs : 1766Command Status Errors : 0Atmel Fatal Errors : 0Unused statistic : 0rxPktsDirected: 2765984rxPktsBroadcast: 2163rxPktsNoMatch: 0rxPktsDuplicate: 733rxPktsRuntFail: 0rxPktsLongFail: 0rxPktsHCRCFail: 151rxPktsICVFail: 0rxPktsFCSFail: 23rxPktsAssocFail: 0rxPktsIncomplete: 0rxPayloadsFailFull: 0rxPayloadsDelivered: 138025rxPktsEmpty: 2635068txPkts: 16960762txPktsEmpty: 16804869txPayloads: 155893txPayloadsBCast: 2040txPayloads1Ok: 131286txPayloads2Ok: 9423txPayloads3Ok: 1027txPayloads4Ok: 133txPayloadsFailRetry: 27txPayloadsFailAssocDeleted: 11txPayloadsFailBadParam: 0txPayloadsFailVnetInactive: 0txPayloadsFailAssocFail: 0txPayloadsFailTimeout: 0
APCD-LM043-4.0 233txPayloadsFailQueueTooLong: 0txPayloadsEmpty: 0replyOrRssiTimeouts: 232598restarts: 0registrationRequests: 0registrationResponses: 0deregistrationRequests: 0deregistrationInits: 0disassociationRequests: 5671disassociationInits: 5702newAssociations: 5671currentAssociations: 3unexpectedEvents: 0latestTx: 187latestProg: 9881latestTxPayload: 212latestReply: 9912lateReplyEum: 6294067longestSearch: 127txDescAvail: 74CCU>Routing/Bridging Protocol StatisticsRouting/Bridging Protocol Statistics present operational information about data which isprocessed by the EUM bridging or CCU routing layer. These statistics are described in Table88.The Routing/Bridging Protocol Statistics are not available in the WaveRider MIBs.Table 88 Routing/Bridging Protocol StatisticsStatistic DescriptionRx Eth Dst - App Number of received Ethernet frames transferredfrom the Ethernet port to the EUM application.[EUM only]Rx Eth Dst - Radio Number of received Ethernet frames bridgedfrom the Ethernet port to the radio port. [EUMonly]Rx Eth Dst - To Router Number of received Ethernet frames transferredfrom the Ethernet port to the CCU routerapplication. [CCU only]Rx Eth Err - Mblk Number of Ethernet frames from the Ethernetport that were discarded because of a specifictype of memory allocation error.Rx Eth Err - Msg Buffer Number of Ethernet frames from the Ethernetport that were discarded because of a specifictype of memory allocation error.
234 APCD-LM043-4.0Rx Eth Err - Pkt Size Number of Ethernet frames from the Ethernetport that were discarded because the frame wastoo large or too small to decode.Rx Eth Err - Unknown Ether Type Number of Ethernet frames from the Ethernetport that were discarded because they wereneither IP nor ARP frames (example, IPX frame).Rx Eth Err - Customer Table Error Number of Ethernet frames from the Ethernetport that were discarded because the host wasnot allowed air access. [EUM only]Rx Eth Err - Invalid NetPool Number of Ethernet frames from the Ethernetport that were discarded because of a specifictype of memory allocation error. [EUM only]Rx Eth Dst - Unknown Number of Ethernet frames from the Ethernetport that were discarded because the host isknown to be on the EUM’s Ethernet side. [EUMonly]Rx Eth Err - Could not Duplicate Number of Ethernet frames from the Ethernetport that were discarded because of a specifictype of memory allocation error. [EUM only]Rx Eth Err - IP Filter Number of port-filtered Ethernet frames from theEthernet port.Rx Radio Dst - App Number of Ethernet frames that were transferredfrom the radio to the application layer.Rx Radio Dst - Radio Number of Ethernet frames that were receivedfrom the radio and transmitted back out throughthe radio (i.e., “switched”). [CCU only]Rx Radio Dst - To Router Number of Ethernet frames that were receivedfrom the radio port and forwarded to the CCUrouter application (i.e., destined for the CCUapplication or gateway). [CCU only]Rx Radio Dst - Eth Number of Ethernet frames from the radio portthat were bridged from the radio port to theEthernet port. [EUM only]Rx Radio Err - Mblk Number of Ethernet frames from the radio portthat were discarded because of a specific type ofmemory allocation error.Rx Radio Err - Msg Buffer Number of Ethernet frames from the radio portthat were discarded because of a specific type ofmemory allocation error.Rx Radio Err - Pkt Size Number of Ethernet frames from the radio portthat were discarded because the frame was toolarge or too small to decode.Rx Radio Err - Unknown Ether Type Number of Ethernet frames from the radio portthat were discarded because they were neitherIP nor ARP frames (example, IPX frame).Statistic Description
APCD-LM043-4.0 235To view the Routing Protocol Statistics:Rx Radio Err - Unknown Msg Type Number of Ethernet frames from the radio portthat were discarded because of an internalrouting error.Rx Radio Err - Unreg Request Number of Ethernet frames received from theradio port that were discarded because theycame from an unregistered EUM. [CCU only]Rx Radio Err - Invalid NetPool Number of Ethernet frames received from theradio port that were discarded because of aspecific type of memory allocation error.Rx Radio Err - Could not Duplicate Number of Ethernet frames received from theradio port that were discarded because of aspecific type of memory allocation error.Rx Radio Err - Reflection Number of Ethernet frames received from theradio port that were discarded because thesource address was on the EUM (split-horizonrule). [EUM only]Rx Radio Err - IP Filter Number of port-filtered Ethernet frames from theradio port.Tx Dst - Eth Number of Ethernet frames that were transmittedthrough the Ethernet port.Tx Dst - Radio Number of Ethernet frames that were transmittedthrough the radio port.Tx Err - Mblk Number of transmit Ethernet frames that had tobe discarded because of a specific type ofmemory allocation error.Tx Err - Msg Buffer Number of transmit Ethernet frames that had tobe discarded because of a specific type ofmemory allocation error.Tx Err - Pkt Size Number of transmit Ethernet frames that had tobe discarded because the frame was too large ortoo small to decode.Tx Dst - Unregistered Number of transmit Ethernet frames that had tobe discarded because they were for anunregistered EUM. [CCU only]Tx Dst - Unknown Number of transmit Ethernet frames that had tobe discarded because the Ethernet address didnot appear in the Address Table.Tx Err - Invalid NetPool Number of transmit Ethernet frames that had tobe discarded because of a specific type ofmemory allocation error. [EUM only]Tx Err - Could not Duplicate Number of transmit Ethernet frames that had tobe discarded because of a specific type ofmemory allocation error. [EUM only]Statistic Description
236 APCD-LM043-4.0CCU> stats rp----------------Routing Protocol Statistics -----------------Rx Eth Dst - Radio : 0Rx Eth Dst - To Router : 154396Rx Eth Err - Mblk (Discard) : 0Rx Eth Err - Msg Buffer (Discard) : 0Rx Eth Err - Pkt Size (Discard) : 0Rx Eth Err - Unknown Ether Type (Discard) : 554Rx Eth Err - IP Filter (Discard) : 0Rx Radio Dst - App : 340Rx Radio Dst - Radio : 1268Rx Radio Dst - To Router : 129025Rx Radio Dst - Eth : 0Rx Radio Err - Mblk (Discard) : 0Rx Radio Err - Msg Buffer (Discard) : 0Rx Radio Err - Pkt Size (Discard) : 0Rx Radio Err - Unknown Ether Type (Discard) : 0Rx Radio Err - Unknown Msg Type (Discard) : 0Rx Radio Err - Unreg Request (Discard) : 0Rx Radio Err - Invalid NetPool (Discard) : 0Rx Radio Err - Could not Duplicate (Discard) : 0Rx Radio Err - IP Filter (Discard) : 0Tx Dst - Eth : 131288Tx Dst - Radio : 136286Tx Err - Mblk (Discard) : 0Tx Err - Msg Buffer (Discard) : 0Tx Err - Pkt Size (Discard) : 0Tx Dst - Unregistered (Discard) : 0Tx Dst - Unknown (Discard) : 0CCU>Network Interface StatisticsNetwork Interface Statistics, described in Table 88, are generated by the IP-protocol suiteresident on the CCU and EUM.Network Interface Statistics are not available in the WaveRider MIBs.Table 89 Network Interface StatisticsTo view all network interface statistics:Statistic DescriptionICMP For information on ICMP, and ICMP-related statistics, refer to RFC729.IP For information on IP, and IP-related statistics, refer to RFC791.TCP For information on TCP, and TCP-related statistics, refer to RFC793.UDP For information on UDP, and UDP-related statistics, refer to RFC768.
APCD-LM043-4.0 237CCU> stats netTo view network interface ICMP statistics:CCU> stats net icmpICMP:3133 calls to icmp_error0 error not generated because old message was icmpOutput histogram:destination unreachable: 31330 message with bad code fields0 message < minimum length0 bad checksum0 message with bad lengthInput histogram:destination unreachable: 200 message response generatedCCU>To view network interface IP statistics:CCU> stats net iptotal 2181354badsum 0tooshort 0toosmall 0badhlen 0badlen 0infragments 0fragdropped 0fragtimeout 0forward 1925975cantforward 96917redirectsent 0unknownprotocol 20nobuffers 0reassembled 0outfragments 0noroute 2Active Internet connections (including servers)PCB Proto Recv-Q Send-Q Local Address Foreign Address (state)-------- ----- ------ ------ ------------------ ------------------ -------56d500 TCP 1 0 10.5.0.1.23 10.0.1.50.2687 ESTABLISHE56c8d0 TCP 0 0 0.0.0.0.23 0.0.0.0.0 LISTEN56c6c8 TCP 0 0 0.0.0.0.21 0.0.0.0.0 LISTEN56cad8 UDP 0 0 0.0.0.0.123 0.0.0.0.056cbdc UDP 0 0 0.0.0.0.20001 0.0.0.0.056bb9c UDP 0 0 0.0.0.0.161 0.0.0.0.0CCU>In the above example, the active internet connections were:Port 21 FTPPort 23 Telnet (two sessions open)Port 123 NTPPort 161 SNMPPort 20001 WaveRider private CCU load meter serverTo view network interface TCP statistics;
238 APCD-LM043-4.0CCU> stats net tcpTCP:536 packets sent304 data packets (23557 bytes)0 data packet (0 byte) retransmitted222 ack-only packets (7 delayed)0 URG only packet0 window probe packet0 window update packet10 control packets527 packets received310 acks (for 23571 bytes)7 duplicate acks0 ack for unsent data283 packets (485 bytes) received in-sequence0 completely duplicate packet (0 byte)0 packet with some dup. data (0 byte duped)7 out-of-order packets (0 byte)0 packet (0 byte) of data after window0 window probe0 window update packet0 packet received after close2 discarded for bad checksums0 discarded for bad header offset field0 discarded because packet too short1 connection request7 connection accepts8 connections established (including accepts)7 connections closed (including 0 drop)0 embryonic connection dropped309 segments updated rtt (of 311 attempts)2 retransmit timeouts0 connection dropped by rexmit timeout0 persist timeout0 keepalive timeout0 keepalive probe sent0 connection dropped by keepalive0 pcb cache lookup failedCCU>To view the network interface UDP statisticsCCU> stats net udpUDP:247539 total packets158004 input packets89535 output packets0 incomplete header0 bad data length field0 bad checksum81429 broadcasts received with no ports0 full socket50202 pcb cache lookups failed57 pcb hash lookups failedUDP>
APCD-LM043-4.0 239System Load Statistics (Radio Meter)The radio meter command prints out a table of measurements that indicate the current load onthe system. These statistics are only available at the CCU. The load statistics are summarizedin Table 90. System Load Statistics are not available through the WaveRider MIBs.Table 90 Load Statistics (Radio Meter)Notes:• All counters are continuous; that is, they are never zeroed, except if the unit is reset orpower cycled.• Payload and poll counters can roll over after a minimum of 50 days.• Byte counters can roll over after a minimum of 4 hours.Statistic DescriptionTime Value of the CCU’s internal 32-bit microsecond timer at the instant the messageswere taken. Time rolls over to “0” about every hour and eleven minutes.Fw Pyls Number of payloads transmitted from the CCU to EUMs in this class/level,including retries.Fw Bytes Number of bytes of payload transmitted from the CCU to EUMs in this class/level, including retries.Rev Pyls Number of payloads transmitted from EUMs in this class/level that are correctlyreceived by the CCU.Rev Bytes Number of bytes of payload transmitted from EUMs in this class/level that arecorrectly received by the CCU.Max Vio MaxIPS Violations - Number of times the CCU has not polled an EUM in thisclass/level within the inter-poll space defined by the EUM’s grade of service.Ideal VioIdealIPS Violations - Number of times the average inter-poll space for EUMs inthis class/level has been more than 25% higher than the ideal inter-poll spacedefined by the grade of service.#EUMs Number of EUMs in the class/level at the instant in time the load statistics werecollected. The broadcast channel counts as one.Avg IPSCurrent low-pass average inter-poll space, in microseconds, for the class/level atthat instant in time, which corresponds to the current polling rate for EUMs in thatclass. If no EUMs are currently in the class, it is the average taken at the time thelast EUM exited the class.Total Polls Number of times the CCU has polled an EUM in the class/level.Empty Polls Number of times the CCU has polled an EUM in the class/level and did not eithertransmit or receive a payload.
240 APCD-LM043-4.0• Violation counters could roll over after 70 seconds if the corresponding parameter wasset too small. A steeply climbing violation counter indicates serious problems witheither the settings or the system load.To view the load statistics:Console> radio meterCCU Load Meter Time (us): 2388125184Fw Pyls Fw Bytes Rev Pyls Rev Bytes Max Vio Ideal VioGold Active 261996 117413346 233592 45583692 1 0Gold Inactive 65145 3614618 3038 356335 0 0Silver Active 885135 299817354 795036 131774471 0 2Silver Inactive 50164 2246125 1283 172947 0 0Bronze Active 20847 13538244 17727 2242378 0 0Bronze Inactive 4098 178357 191 25156 0 0BE Active 34294 2380443 3395 356844 0 97BE Inactive 21443 708668 15808 688558 0 0Broadcast 51436 2697875 48070 6848739 0 0Overall 1394558 442595030 1118140 188049120 1 99#EUMs Avg IPS Total Polls Empty PollsGold Active 0 21507 3017826 2577645Gold Inactive 1 45867 2351419 2283292Silver Active 0 1268 30527206 28936895Silver Inactive 0 49800 1549140 1497712Bronze Active 0 11906 257261 224260Bronze Inactive 1 48111 125211 120926BE Active 0 29463 707972 670633BE Inactive 1 50472 1100549 1063487Broadcast 1 1197 376559248 376459966Console>Each row on the above table, except for Overall, corresponds to a grade of service/activitylevel combination. The last row is the overall totals, which in all cases except IPS, are the sumof the entries in the column. Active refers to EUMs that have had traffic within the lastactivePollTimeout, and Inactive refers to EUMs that have not had traffic within the lastactivePollTimeout and have not timed out on disassociationTime. Therefore payload countsfor inactive EUMs indicate transitions from inactive to active.NOTE: Broadcast traffic is carried with random access polls. Therefore,forward traffic (CCU-to-EUM) in the broadcast row is broadcasttraffic, while reverse traffic is random access traffic. The reversepacket rate should be less than 15% of the total poll rate for thebroadcast traffic, since random access attempts can collide.Assuming uncorrelated arrivals, this should ensure that 99.7% ofrandom access attempts succeed (in four retries or less).
APCD-LM043-4.0 241Appendix I IP Plan — ExampleThe following tables provide an example of an IP plan for an LMS4000 system equipped withfifteen 900 MHz CAPs.NAP IP Addressing PlanTable 91 Example - CCU Ethernet Subnet DataTable 92 Example - NAP IP Addressing PlanSubnet 192.168.10.0Subnet Mask Bits 24Subnet Mask 255.255.255.0 (ff.ff.ff.00)NAP Element IP AddressGateway (NAP) Router 192.168.10.1 /24NAP Switch 192.168.10.5 /24NAP UPS 192.168.10.6 /24SNMP Manager 192.168.10.7 /24
242 APCD-LM043-4.0CCU Ethernet IP Addressing PlanTable 93 Example - CCU Ethernet IP Addressing PlanSite CCU CCU EthernetAddress Site CCU CCU EthernetAddressCAP01 CCU01 192.168.10.11 CAP09 CCU01 192.168.10.139CCU02 192.168.10.12 CCU02 192.168.10.140CCU03 192.168.10.13 CCU03 192.168.10.141CAP02 CCU01 192.168.10.27 CAP10 CCU01 192.168.10.155CCU02 192.168.10.28 CCU02 192.168.10.156CCU03 192.168.10.29 CCU03 192.168.10.157CAP03 CCU01 192.168.10.43 CAP11 CCU01 192.168.10.171CCU02 192.168.10.44 CCU02 192.168.10.172CCU03 192.168.10.45 CCU03 192.168.10.173CAP04 CCU01 192.168.10.59 CAP12 CCU01 192.168.10.187CCU02 192.168.10.60 CCU02 192.168.10.188CCU03 192.168.10.61 CCU03 192.168.10.189CAP05 CCU01 192.168.10.75 CAP13 CCU01 192.168.10.203CCU02 192.168.10.76 CCU02 192.168.10.204CCU03 192.168.10.77 CCU03 192.168.10.205CAP06 CCU01 192.168.10.91 CAP14 CCU01 192.168.10.219CCU02 192.168.10.92 CCU02 192.168.10.220CCU03 192.168.10.93 CCU03 192.168.10.221CAP07 CCU01 192.168.10.107 CAP15 CCU01 192.168.10.235CCU02 192.168.10.108 CCU02 192.168.10.236CCU03 192.168.10.109 CCU03 192.168.10.237CAP08 CCU01 192.168.10.123CCU02 192.168.10.124CCU03 192.168.10.125
APCD-LM043-4.0 243CCU Radio IP Addressing PlanTable 94 Example - CCU Radio Subnet DataTable 95 Example - CCU Radio IP Addressing PlanSubnet 172.16.0.0Subnet Mask Bits 22Subnet Mask 255.255.252.0 (ff.ff.fc.00)Site CCU Subnet CCU RadioIP Address CCU Radio Subnet Range BroadcastCAP01 CCU01 172.16.4.0 172.16.4.1 172.16.4.1 - 172.16.7.254 172.16.7.255CCU02 172.16.8.0 172.16.8.1 172.16.8.1 - 172.16.11.254 172.16.11.255CCU03 172.16.12.0 172.16.12.1 172.16.12.1 - 172.16.15.254 172.16.15.255CAP02 CCU01 172.16.16.0 172.16.16.1 172.16.16.1 - 172.16.19.254 172.16.19.255CCU02 172.16.20.0 172.16.20.1 172.16.20.1 - 172.16.23.254 172.16.23.255CCU03 172.16.24.0 172.16.24.1 172.16.24.1 - 172.16.27.254 172.16.27.255CAP03 CCU01 172.16.28.0 172.16.28.1 172.16.28.1 - 172.16.31.254 172.16.31.255CCU02 172.16.32.0 172.16.32.1 172.16.32.1 - 172.16.35.254 172.16.35.255CCU03 172.16.36.0 172.16.36.1 172.16.36.1 - 172.16.39.254 172.16.39.255CAP04 CCU01 172.16.40.0 172.16.40.1 172.16.40.1 - 172.16.43.254 172.16.43.255CCU02 172.16.44.0 172.16.44.1 172.16.44.1 - 172.16.47.254 172.16.47.255CCU03 172.16.48.0 172.16.48.1 172.16.48.1 - 172.16.51.254 172.16.51.255CAP05 CCU01 172.16.52.0 172.16.52.1 172.16.52.1 - 172.16.55.254 172.16.55.255CCU02 172.16.56.0 172.16.56.1 172.16.56.1 - 172.16.59.254 172.16.59.255CCU03 172.16.60.0 172.16.60.1 172.16.60.1 - 172.16.63.254 172.16.63.255CAP06 CCU01 172.16.64.0 172.16.64.1 172.16.64.1 - 172.16.67.254 172.16.67.255CCU02 172.16.68.0 172.16.68.1 172.16.68.1 - 172.16.71.254 172.16.71.255CCU03 172.16.72.0 172.16.72.1 172.16.72.1 - 172.16.75.254 172.16.75.255CAP07 CCU01 172.16.76.0 172.16.76.1 172.16.76.1 - 172.16.79.254 172.16.79.255CCU02 172.16.80.0 172.16.80.1 172.16.80.1 - 172.16.83.254 172.16.83.255CCU03 172.16.84.0 172.16.84.1 172.16.84.1 - 172.16.87.254 172.16.87.255CAP08 CCU01 172.16.88.0 172.16.88.1 172.16.88.1 - 172.16.91.254 172.16.91.255CCU02 172.16.92.0 172.16.92.1 172.16.92.1 - 172.16.95.254 172.16.95.255CCU03 172.16.96.0 172.16.96.1 172.16.96.1 - 172.16.99.254 172.16.99.255
244 APCD-LM043-4.0CAP09 CCU01 172.16.100.0 172.16.100.1 172.16.100.1 - 172.16.103.254 172.16.103.255CCU02 172.16.104.0 172.16.104.1 172.16.104.1 - 172.16.107.254 172.16.107.255CCU03 172.16.108.0 172.16.108.1 172.16.108.1 - 172.16.111.254 172.16.111.255CAP10 CCU01 172.16.112.0 172.16.112.1 172.16.112.1 - 172.16.115.254 172.16.115.255CCU02 172.16.116.0 172.16.116.1 172.16.116.1 - 172.16.119.254 172.16.119.255CCU03 172.16.120.0 172.16.120.1 172.16.120.1 - 172.16.123.254 172.16.123.255CAP11 CCU01 172.16.124.0 172.16.124.1 172.16.124.1 - 172.16.127.254 172.16.127.255CCU02 172.16.128.0 172.16.128.1 172.16.128.1 - 172.16.131.254 172.16.131.255CCU03 172.16.132.0 172.16.132.1 172.16.132.1 - 172.16.135.254 172.16.135.255CAP12 CCU01 172.16.136.0 172.16.136.1 172.16.136.1 - 172.16.139.254 172.16.139.255CCU02 172.16.140.0 172.16.140.1 172.16.140.1 - 172.16.143.254 172.16.143.255CCU03 172.16.144.0 172.16.144.1 172.16.144.1 - 172.16.147.254 172.16.147.255CAP13 CCU01 172.16.148.0 172.16.148.1 172.16.148.1 - 172.16.151.254 172.16.151.255CCU02 172.16.152.0 172.16.152.1 172.16.152.1 - 172.16.155.254 172.16.155.255CCU03 172.16.156.0 172.16.156.1 172.16.156.1 - 172.16.159.254 172.16.159.255CAP14 CCU01 172.16.160.0 172.16.160.1 172.16.160.1 - 172.16.163.254 172.16.163.255CCU02 172.16.164.0 172.16.164.1 172.16.164.1 - 172.16.167.254 172.16.167.255CCU03 172.16.168.0 172.16.168.1 172.16.168.1 - 172.16.171.254 172.16.171.255CAP15 CCU01 172.16.172.0 172.16.172.1 172.16.172.1 - 172.16.175.254 172.16.175.255CCU02 172.16.176.0 172.16.176.1 172.16.176.1 - 172.16.179.254 172.16.179.255CCU03 172.16.180.0 172.16.180.1 172.16.180.1 - 172.16.183.254 172.16.183.255Site CCU Subnet CCU RadioIP Address CCU Radio Subnet Range Broadcast
APCD-LM043-4.0 245EUM IP Addressing PlanTable 96 Example - EUM Subnet DataTable 97 Example - EUM IP Addressing PlanSubnet 172.16.0.0Subnet Mask Bits 22Subnet Mask 255.255.252.0 (ff.ff.fc.00)Site CCU Subnet ID EUM IP Address RangeCAP01 CCU01 EUM001-253 172.16.4.2 - 172.16.4.254EUM254-300 172.16.5.1 - 172.16.5.47CCU02 EUM001-253 172.16.8.2 - 172.16.8.254EUM254-300 172.16.9.1 - 172.16.9.47CCU03 EUM001-253 172.16.12.2 - 172.16.12.254EUM254-300 172.16.13.1 - 172.16.13.47CAP02 CCU01 EUM001-253 172.16.16.2 - 172.16.16.254EUM254-300 172.16.17.1 - 172.16.17.47CCU02 EUM001-253 172.16.20.2 - 172.16.20.254EUM254-300 172.16.21.1 - 172.16.21.47CCU03 EUM001-253 172.16.24.2 - 172.16.24.254EUM254-300 172.16.25.1 - 172.16.25.47CAP03 CCU01 EUM001-253 172.16.28.2 - 172.16.28.254EUM254-300 172.16.29.1 - 172.16.29.47CCU02 EUM001-253 172.16.32.2 - 172.16.32.254EUM254-300 172.16.33.1 - 172.16.33.47CCU03 EUM001-253 172.16.36.2 - 172.16.36.254EUM254-300 172.16.37.1 - 172.16.37.47CAP04 CCU01 EUM001-253 172.16.40.2 - 172.16.40.254EUM254-300 172.16.41.1 - 172.16.41.47CCU02 EUM001-253 172.16.44.2 - 172.16.44.254EUM254-300 172.16.45.1 - 172.16.45.47CCU03 EUM001-253 172.16.48.2 - 172.16.48.254EUM254-300 172.16.49.1 - 172.16.49.47
246 APCD-LM043-4.0CAP05 CCU01 EUM001-253 172.16.52.2 - 172.16.52.254EUM254-300 172.16.53.1 - 172.16.53.47CCU02 EUM001-253 172.16.56.2 - 172.16.56.254EUM254-300 172.16.57.1 - 172.16.57.47CCU03 EUM001-253 172.16.60.2 - 172.16.60.254EUM254-300 172.16.61.1 - 172.16.61.47CAP06 CCU01 EUM001-253 172.16.64.2 - 172.16.64.254EUM254-300 172.16.65.1 - 172.16.65.47CCU02 EUM001-253 172.16.68.2 - 172.16.68.254EUM254-300 172.16.69.1 - 172.16.69.47CCU03 EUM001-253 172.16.72.2 - 172.16.72.254EUM254-300 172.16.73.1 - 172.16.73.47CAP07 CCU01 EUM001-253 172.16.76.2 - 172.16.76.254EUM254-300 172.16.77.1 - 172.16.77.47CCU02 EUM001-253 172.16.80.2 - 172.16.80.254EUM254-300 172.16.81.1 - 172.16.81.47CCU03 EUM001-253 172.16.84.2 - 172.16.84.254EUM254-300 172.16.85.1 - 172.16.85.47CAP08 CCU01 EUM001-253 172.16.88.2 - 172.16.88.254EUM254-300 172.16.89.1 - 172.16.89.47CCU02 EUM001-253 172.16.92.2 - 172.16.92.254EUM254-300 172.16.93.1 - 172.16.93.47CCU03 EUM001-253 172.16.96.2 - 172.16.96.254EUM254-300 172.16.97.1 - 172.16.97.47CAP09 CCU01 EUM001-253 172.16.100.2 - 172.16.100.254EUM254-300 172.16.101.1 - 172.16.101.47CCU02 EUM001-253 172.16.104.2 - 172.16.104.254EUM254-300 172.16.105.1 - 172.16.105.47CCU03 EUM001-253 172.16.108.2 - 172.16.108.254EUM254-300 172.16.109.1 - 172.16.109.47Site CCU Subnet ID EUM IP Address Range
APCD-LM043-4.0 247CAP10 CCU01 EUM001-253 172.16.112.2 - 172.16.112.254EUM254-300 172.16.113.1 - 172.16.113.47CCU02 EUM001-253 172.16.116.2 - 172.16.116.254EUM254-300 172.16.117.1 - 172.16.117.47CCU03 EUM001-253 172.16.120.2 - 172.16.120.254EUM254-300 172.16.121.1 - 172.16.121.47CAP11 CCU01 EUM001-253 172.16.124.2 - 172.16.124.254EUM254-300 172.16.125.1 - 172.16.125.47CCU02 EUM001-253 172.16.128.2 - 172.16.128.254EUM254-300 172.16.129.1 - 172.16.129.47CCU03 EUM001-253 172.16.132.2 - 172.16.132.254EUM254-300 172.16.133.1 - 172.16.133.47CAP12 CCU01 EUM001-253 172.16.136.2 - 172.16.136.254EUM254-300 172.16.137.1 - 172.16.137.47CCU02 EUM001-253 172.16.140.2 - 172.16.140.254EUM254-300 172.16.141.1 - 172.16.141.47CCU03 EUM001-253 172.16.144.2 - 172.16.144.254EUM254-300 172.16.145.1 - 172.16.145.47CAP13 CCU01 EUM001-253 172.16.148.2 - 172.16.148.254EUM254-300 172.16.149.1 - 172.16.149.47CCU02 EUM001-253 172.16.152.2 - 172.16.152.254EUM254-300 172.16.153.1 - 172.16.153.47CCU03 EUM001-253 172.16.156.2 - 172.16.156.254EUM254-300 172.16.157.1 - 172.16.157.47CAP14 CCU01 EUM001-253 172.16.160.2 - 172.16.160.254EUM254-300 172.16.161.1 - 172.16.161.47CCU02 EUM001-253 172.16.164.2 - 172.16.164.254EUM254-300 172.16.165.1 - 172.16.165.47CCU03 EUM001-253 172.16.168.2 - 172.16.168.254EUM254-300 172.16.169.1 - 172.16.169.47Site CCU Subnet ID EUM IP Address Range
248 APCD-LM043-4.0Subscriber IP Addressing PlanTable 98 Example - Subscriber Subnet DataTable 99 Example - Subscriber IP Addressing PlanCAP15 CCU01 EUM001-253 172.16.172.2 - 172.16.172.254EUM254-300 172.16.173.1 - 172.16.173.47CCU02 EUM001-253 172.16.176.2 - 172.16.176.254EUM254-300 172.16.177.1 - 172.16.177.47CCU03 EUM001-253 172.16.180.2 - 172.16.180.254EUM254-300 172.16.181.1 - 172.16.181.47Subnet 172.16.0.0Subnet Mask Bits 22Subnet Mask 255.255.252.0 (ff.ff.fc.00)Site CCU Subnet ID Subscriber IP Address RangeCAP01 CCU01 SUB001-253 172.16.6.1 - 172.16.6.254SUB254-300 172.16.7.1 - 172.16.7.46CCU02 SUB001-253 172.16.10.1 - 172.16.10.254SUB254-300 172.16.11.1 - 172.16.11.46CCU03 SUB001-253 172.16.14.1 - 172.16.14.254SUB254-300 172.16.15.1 - 172.16.15.46CAP02 CCU01 SUB001-253 172.16.18.1 - 172.16.18.254SUB254-300 172.16.19.1 - 172.16.19.46CCU02 SUB001-253 172.16.22.1 - 172.16.22.254SUB254-300 172.16.23.1 - 172.16.23.46CCU03 SUB001-253 172.16.26.1 - 172.16.26.254SUB254-300 172.16.27.1 - 172.16.27.46Site CCU Subnet ID EUM IP Address Range
APCD-LM043-4.0 249CAP03 CCU01 SUB001-253 172.16.30.1 - 172.16.30.254SUB254-300 172.16.31.1 - 172.16.31.46CCU02 SUB001-253 172.16.34.1 - 172.16.34.254SUB254-300 172.16.35.1 - 172.16.35.46CCU03 SUB001-253 172.16.38.1 - 172.16.38.254SUB254-300 172.16.39.1 - 172.16.39.46CAP04 CCU01 SUB001-253 172.16.42.1 - 172.16.42.254SUB254-300 172.16.43.1 - 172.16.43.46CCU02 SUB001-253 172.16.46.1 - 172.16.46.254SUB254-300 172.16.47.1 - 172.16.47.46CCU03 SUB001-253 172.16.50.1 - 172.16.50.254SUB254-300 172.16.51.1 - 172.16.51.46CAP05 CCU01 SUB001-253 172.16.54.1 - 172.16.54.254SUB254-300 172.16.55.1 - 172.16.55.46CCU02 SUB001-253 172.16.58.1 - 172.16.58.254SUB254-300 172.16.59.1 - 172.16.59.46CCU03 SUB001-253 172.16.62.1 - 172.16.62.254SUB254-300 172.16.63.1 - 172.16.63.46CAP06 CCU01 SUB001-253 172.16.66.1 - 172.16.66.254SUB254-300 172.16.67.1 - 172.16.67.46CCU02 SUB001-253 172.16.70.1 - 172.16.70.254SUB254-300 172.16.71.1 - 172.16.71.46CCU03 SUB001-253 172.16.74.1 - 172.16.74.254SUB254-300 172.16.75.1 - 172.16.75.46CAP07 CCU01 SUB001-253 172.16.78.1 - 172.16.78.254SUB254-300 172.16.79.1 - 172.16.79.46CCU02 SUB001-253 172.16.82.1 - 172.16.82.254SUB254-300 172.16.83.1 - 172.16.83.46CCU03 SUB001-253 172.16.86.1 - 172.16.86.254SUB254-300 172.16.87.1 - 172.16.87.46Site CCU Subnet ID Subscriber IP Address Range
250 APCD-LM043-4.0CAP08 CCU01 SUB001-253 172.16.90.1 - 172.16.90.254SUB254-300 172.16.91.1 - 172.16.91.46CCU02 SUB001-253 172.16.94.1 - 172.16.94.254SUB254-300 172.16.95.1 - 172.16.95.46CCU03 SUB001-253 172.16.98.1 - 172.16.98.254SUB254-300 172.16.99.1 - 172.16.99.97CAP09 CCU01 SUB001-253 172.16.102.1 - 172.16.102.254SUB254-300 172.16.103.1 - 172.16.103.46CCU02 SUB001-253 172.16.106.1 - 172.16.106.254SUB254-300 172.16.107.1 - 172.16.107.46CCU03 SUB001-253 172.16.110.1 - 172.16.110.254SUB254-300 172.16.111.1 - 172.16.111.46CAP10 CCU01 SUB001-253 172.16.114.1 - 172.16.114.254SUB254-300 172.16.115.1 - 172.16.115.46CCU02 SUB001-253 172.16.118.1 - 172.16.118.254SUB254-300 172.16.119.1 - 172.16.119.46CCU03 SUB001-253 172.16.122.1 - 172.16.122.254SUB254-300 172.16.123.1 - 172.16.123.46CAP11 CCU01 SUB001-253 172.16.126.1 - 172.16.126.254SUB254-300 172.16.127.1 - 172.16.127.46CCU02 SUB001-253 172.16.130.1 - 172.16.130.254SUB254-300 172.16.131.1 - 172.16.131.46CCU03 SUB001-253 172.16.134.1 - 172.16.134.254SUB254-300 172.16.135.1 - 172.16.135.46CAP12 CCU01 SUB001-253 172.16.138.1 - 172.16.138.254SUB254-300 172.16.139.1 - 172.16.139.46CCU02 SUB001-253 172.16.142.1 - 172.16.142.254SUB254-300 172.16.143.1 - 172.16.143.46CCU03 SUB001-253 172.16.146.1 - 172.16.146.254SUB254-300 172.16.147.1 - 172.16.147.46Site CCU Subnet ID Subscriber IP Address Range
APCD-LM043-4.0 251CAP13 CCU01 SUB001-253 172.16.150.1 - 172.16.150.254SUB254-300 172.16.151.1 - 172.16.151.46CCU02 SUB001-253 172.16.154.1 - 172.16.154.254SUB254-300 172.16.155.1 - 172.16.155.46CCU03 SUB001-253 172.16.158.1 - 172.16.158.254SUB254-300 172.16.159.1 - 172.16.159.46CAP14 CCU01 SUB001-253 172.16.162.1 - 172.16.162.254SUB254-300 172.16.163.1 - 172.16.163.46CCU02 SUB001-253 172.16.166.1 - 172.16.166.254SUB254-300 172.16.167.1 - 172.16.167.46CCU03 SUB001-253 172.16.170.1 - 172.16.170.254SUB254-300 172.16.171.1 - 172.16.170.46CAP15 CCU01 SUB001-253 172.16.174.1 - 172.16.174.254SUB254-300 172.16.175.1 - 172.16.175.46CCU02 SUB001-253 172.16.178.1 - 172.16.178.254SUB254-300 172.16.179.1 - 172.16.179.46CCU03 SUB001-253 172.16.182.1 - 172.16.182.254SUB254-300 172.16.183.1 - 172.16.183.46Site CCU Subnet ID Subscriber IP Address Range
—This page is intentionally left blank —
APCD-LM043-4.0 253Appendix J Acronyms and GlossaryTable 100 Acronyms and AbbreviationsAcronym orAbbreviation DefinitionABWM Advanced Bandwidth ManagerAC Alternating CurrentAPI Application Programming InterfaceARP Address Resolution ProtocolARQ Automatic Retry RequestASCII American Standard Code for Information InterchangeBCF Basic Configuration FileCAP Communications Access PointCCU CAP Channel UnitCIR Committed Information RateCLI Command Line InterfaceCPU Central Processing UnitCSA Canadian Standards AssociationCTS Clear To SenddB decibeldBi decibel—with respect to an isotropic radiatorDCE Data Communication EquipmentDES Data Encryption StandardDHCP Dynamic Host Configuration ProtocolDNS Domain Name Server, Domain Network ServerDRAM Dynamic Random-access Memory
254 APCD-LM043-4.0DSR Data Set ReadyDSSS Direct-sequence Spread SpectrumDTE Data Terminal EquipmentESD Electrostatic DischargeESN Electronic Serial NumberETSI European Telecommunications Standards for IndustryEUM End-user ModemFCC Federal Communications Commission (U.S.A.)FRU Field Replaceable UnitFTP File Transfer ProtocolGHz GigaHertzGMT Greenwich Mean TimeGOS Grade of ServiceHTTP HyperText Transfer ProtocolIC Industry CanadaICMP Internet Control Message ProtocolID Identifier, IdentificationIP Internet ProtocolISM Industrial, Scientific, and Medical (Unlicensed Radio Band)ISP Internet Service ProviderLAN Local Area NetworkLED Light-Emitting DiodeLMDS Local Multipoint Distribution SystemLMS Last Mile Solution®LOS Line Of SightMAC Media Access Control, Medium Access ControllerMbps Megabits per secondMBR Maximum Burst RateMCF MAC Configuration FileMHz MegaHertzMIB Management Information BaseMTU Maximum Transmission Unitn/a not applicableNAP Network Access PointAcronym orAbbreviation Definition
APCD-LM043-4.0 255NAT Network Address TranslationNCL Network Communication LinkNTP Network Time ProtocolOAM Operations, Administration and MaintenanceOID Object IdentifierOS Operating SystemPAT Port Address TranslationPC Personal ComputerPCF Permanent Configuration FilePHY Physical LayerRADIUS Remote Access Dial-in User ServiceRCF Route Configuration FileRF Radio FrequencyRIP Routing Information ProtocolRMA Returned Merchandise AuthorizationRSSI Receive Signal Strength IndicatorRTS Request To SendRx ReceiveSLA Service Level AgreementSNMP Simple Network Management ProtocolSNTP Simple Network Time ProtocolSOHO Small Office/Home OfficeSRAM Static Random Access MemoryTCP Transmission Control ProtocolTCP/IP Transmission Control Protocol/Internet ProtocolTDD Time-Division Duplex (Modulation)TDMA Time-Division Multiple AccessTx TransmitUDP User Datagram ProtocolUL Underwriters LaboratoriesUPS Uninterruptable Power SupplyUTC Universal Time CoordinationWRAP WaveRider Access PointAcronym orAbbreviation Definition
256 APCD-LM043-4.0Table 101 LMS4000 Network GlossaryTerm DefinitionLMS4000 RF Subsystem The RF Equipment associated with an LMS4000, includingCCUs, RFSM, antennas, and transmission lines.Bandwidth Manager The entity in the LMS4000 that uses various algorithms tomanage end-user access to the network interface bandwidth,based on subscribed level of service.Broadcast (Message) A message sent by one network device to all other devicesconnected to the network.Cell Size The nominal radius of the geographic area served by a singleCAP, within which EUMs can reliably receive service.Channel Generally, the medium though which information iscommunicated. In wireless communications, the channel isusually defined by the center frequency, modulation type, andoccupied bandwidth.CLI (Command LineInterface) In contrast to a graphical user interface, a CLI is aconfiguration and control interface based on keyboard-entrycommands and responses.Console Port Typically, the 9–pin RS-232 serial port on an LMS device towhich a terminal or laptop computer is connected, for thepurpose of configuring or controlling the device.Configuration Terminal The configuration terminal is provided for the purpose ofconfiguring or controlling a device directly through its consoleport.DNS (Domain NameSystem) A database system that translates domain names into IPaddresses. For example, waverider.com is converted into207.23.187.242.DSSS (Direct-SequenceSpread Spectrum) A form of spread-spectrum communications that uses a high-speed code sequence, along with the information being sent,to modulate the RF carrier.Ethernet Switch In the context of LMS, the devices that provide data link layerEthernet connection between the router, NMS, UPS, and backhaul equipment at the LMS4000, and the CCUs, RFSM, backhaul equipment and UPS at the CAP.Host Name The common name given to network devices to make themmore easily identifiable by network operators and maintenancepersonnel.Gateway A device connecting two networks that use differentcommunications technologies or protocols; for example, an IP/Telephony Gateway provides a connection between an IPnetwork and a telephone network.
APCD-LM043-4.0 257GOS (Grade of Service) A level of service associated with an EUM, which determineshow often, and when, an EUM will be polled. Since an EUMcan only send one packet each time it is polled, the data rate isrelated to the polling rate.IP (Internet Protocol) The network-layer protocol in the TCP/IP stack (defined byRFC 791).Line of Sight The radio link between a transmitter and receiver is said to beline of sight if the direct path between the two is relatively freefrom physical obstruction.MAC (Medium AccessControl) The mechanism of managing access, by multiple users, to acommon transmission medium.Multicast (Message) A message sent by a network device to a limited set of networkdevices.Orthogonal Channels Communications channels that can operate over a commontransmission medium without significantly interfering with eachother. In the context of LMS, radio frequencies onappropriately spaced frequencies are considered to beorthogonal.OSPF (Open ShortestPath First) A link-state, hierarchical interior gateway routing protocol thatcan provide least-cost routing, multipath routing, and loadbalancing.NAT (Network AddressTranslation) An Internet standard that enables a local area network to useone set of IP addresses for internal traffic and another set ofaddresses for external traffic.PAT (Port AddressTranslation) A feature that lets you number a LAN with inside localaddresses and filter them through one globally routable IPaddress.Point-to-Multipoint A communications architecture in which a central station(CAP, for example) communicates with multiple remotestations (EUMs).POTS (Plain OldTelephone Service) The basic telephone service provided by the public switchedtelephone network (PSTN).Radio Module The device in the EUM (or CCU) that provides the wirelessinterface to the LMS network. The radio module performssignal spreading and modulation, channelization, up-conversion and amplification in the transmit direction, andsignal amplification, down-conversion, channel selection,demodulation, de-spreading and data recovery in the receivedirection.Range The maximum distance that a signal can be reliablytransmitted between a CCU and EUM.Term Definition
258 APCD-LM043-4.0RIP (Routing InformationProtocol) A routing protocol in which network routers periodicallybroadcast their entire current routing database.Router A network device that routes IP messages from one physicalport to another based on a table of routes that are manuallyentered by a crafts person (static routes) or generated by therouter using a routing protocol such as RIP or OSPF.Routing The process of finding a path to a destination host through anIP network.Sectorization An RF engineering technique whereby co-located transceiversare connected to separate antennas with different butgeometrically arranged azimuths, for the purpose of optimizingradio frequency reuse, extending range, and reducinginterference. 120° sectorization is commonly applied in LMSsystems.SNMP (Simple NetworkManagement Protocol) A protocol used to manage nodes in an IP network.SNMP Agent An agent resides on an SNMP-managed device, and performsoperations when requested to do so by an SNMP manager.SNMP Community A grouping of SNMP agents that can be managed by anSNMP manager. An SNMP manager can manage more thanone SNMP community. The community name is used toauthenticate the SNMP manager before allowing it access tothe agent.SNMP MIB (ManagementInformation Base) The information that an SNMP manager, such as the NMS,can request from an SNMP agent.SNMP Trap A message sent by an SNMP agent to an NMS, console, orterminal to indicate the occurrence of a significant event, suchas a specified condition, or a defined threshold that wasreached.SNMP Trap Server The server to which SNMP trap messages are forwarded.SNTP (Simple NetworkTime Protocol) A feature that provides LMS4000 devices with an accuratetime clock for time stamping events in a log file.Spread Spectrum A communication technology in which the transmitted signaloccupies a much greater bandwidth than the informationbandwidth. The benefits of spread spectrum are generallylower spectral power density, and immunity to noise,interference and jamming.Static Route A route that is manually entered into a routing table by a craftsperson or network operator.Subscriber In the context of LMS, it is the individual or entity associatedwith an EUM.Term Definition
APCD-LM043-4.0 259TCP (TransmissionControl Protocol) The connection-oriented transport layer protocol that providesreliable, full-duplex data transmission in TCP/IP networks.Telnet A terminal emulation program for TCP/IP networks.UDP (User DatagramProtocol) Part of the TCP/IP protocol suite, which provides a way forapplications to access the connectionless features of IP. Itprovides for exchange of datagrams withoutacknowledgements or guaranteed delivery.Unicast A message sent by one network device to another networkdevice.User Authentication In LMS, the secure mechanism through which a useridentification is verified.User Authorization The secure mechanism by which a user is approved to useLMS services. To illustrate, an EUM may be authenticated butdenied service because of the delinquent payment of a bill.VoIP (Voice over IP) The ability to carry normal telephony-style voice over an IP-based internet, with POTS-like functionality, reliability andvoice quality.Term Definition
—This page is intentionally left blank —
APCD-LM043-4.0 261IndexAacronyms ......................253antenna ..................... 17,20antenna guidelines ........ 181,241connector ....................31control ......................31Atmel statistics ..................228Bbackhaul .......................156bandpass filters ...................63broadcast applications ..............46CC/I requirements ..................68CAP ...........................14cavity filters ......................17CCU ...........................15configuration ............. 7,22,83data tables ..................183receive statistics ..............131testing communications ...........9transmit statistics..............127CCU Shelf.......................18center illumination .................65channel bandwidth.................28channels ........................29colocated ....................30cleaning .......................125command-line interface .............76command-line syntax..............163community strings .................51connectors ......................74corner illumination .................66customer list .....................51Ddata rate ........................30data tables .....................183data transmission .................24DHCP relay......................48duplexing .......................30Eequipment........................5Ethernetcable wiring..................152statistics ....................224Ethernet switch ...................17EUM ...........................19adding ......................12antenna .....................20backhaul ....................156configuration ............. 8,22,97Configuration Utility .............77data tables ..................183installation...................105registration ...................25statistics ....................132testing communications ...........9thin route....................155external interference ...............69Ffactory configuration ..............159field upgrade process...............80frequency band ...................28frequency selection ................67FTP ........................ 78,81Gglossary .......................253GOS ...........................39Hhumidity .......................125Iin-band interference................61indicators .......................74Internet connection ................11IP addressing ....................53IP planning .....................241Llightning arrestors .............. 17,22MMAC layer.......................36maintenance ....................125cleaning ....................125humidity ....................125
262 APCD-LM043-4.0temperature..................125MDR statistics ...................226MIBs...........................52modulation ......................29NNAT ...........................57network monitoring ............ 47,127Ooperating statistics.................79out-of-band interference.............61Pperformance modelling..............42periodic packet sources .............46ping commands..................197Polling MAC .....................36statistics .....................42port filtering ......................49propagation path ..................31protocol stacks ...................24Rreceive sensitivity .................31receive statistics .................131RF coverage .....................64RF design guidelines ...............71RF distribution panel ...............18RFSM ..........................17routing protocol statistics ...........233SSNMP....................... 51,80community strings ..............51MIBs........................52SNTP time clock ..................50software license agreement ...........iispecifications ............... 157,199spectral survey ...................60statisticsAtmel ......................228Ethernet ....................224MDR.......................226routing protocol ...............233system loading ...................66Ttemperature.....................125testing communications ..............9thin route.......................155time clock .......................50transmission line ............... 17,21transmit power....................30transmit queue limits ...............42transmit statistics.................127troubleshooting ..................135UUPS ...........................18UTC time clock ...................50Vverification checklist................70VoIP ...........................47Wwarranty ........................ iv
—This page is intentionally left blank —
Telephone: +1 416–502–3161Fax: +1 416–502–2968Email: techsupport@waverider.comURL: www.waverider.com

Navigation menu