FCC ID: QSX5400UNII Motorola Canopy compatible Wireless Internet Acces

 

Cascade Networks Cyclone System Release 8 User Guide, Issue 2 November 2007 Release 8.2 Features Cyclone OFDM Sections:

Planning Guide Installation and Configuration Guide Operations Guide Reference Information Draft5forRegulatoryReview Notices See the following information:

important regulatory and legal notices in Section 36 on Page 493. personal safety guidelines in Section 15 on Page 169. Trademarks,ProductNames,andServiceNames LAST MILE GEAR, the stylized Cyclone Logo and all other trademarks indicated as such herein are trademarks of Cascade Networks, Inc(DBA Last Mile Gear). Reg. U.S. Pat &

Tm. Office. Cyclone is a registered trademark of Cascade Networks, Inc. All other product or service names are the property of their respective owners. Adobe Reader is a registered trademark of Adobe Systems Incorporated. Java and all other Java-based marks are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Microsoft and Windows are registered trademarks of Microsoft Corporation, and Windows XP is a trademark of Microsoft Corporation. 2007 Last Mile Gear, Inc. All rights reserved. Draft5forRegulatoryReview TABLEOFSECTIONS GuideToThisUserGuide OverviewofCycloneNetworks PlanningGuide InstallationandConfigurationGuide OperationsGuide ReferenceInformation Glossary 31 43 127 167 367 489 509 Draft5forRegulatoryReview Draft5forRegulatoryReview TABLEOFCONTENTS GGUUIIDDEETTOOTTHHIISSUUSSEERRGGUUIIDDEE.................................................................................................................................333111 1 New in This Issue ...................................................................................................... 33 1.1 New Products and Features Described in Issue 2 ........................................... 33 1.2 New Descriptions and Revisions in Issue 2 ..................................................... 33 1.3 CycloneWi4 Portfolio ........................................................................................ 33 1.4 Products Covered by This User Guide ............................................................ 33 1.5 Products Not Covered by This User Guide ...................................................... 34 1.6 Software Compatibility Described in This User Guide ..................................... 34 2 Using This User Guide .............................................................................................. 35 2.1 Finding the Information You Need ................................................................... 35 2.1.1 Becoming Familiar with This User Guide ........................................................ 35 2.1.2 Searching This User Guide ............................................................................. 38 2.1.3 Finding Parameter and Field Definitions for Module Web Pages ................... 38 2.2 Interpreting Typeface and Other Conventions ................................................. 41 2.3 Getting Additional Help .................................................................................... 42 2.4 Sending Feedback ........................................................................................... 42 OOOVVVEEERRRVVVIIIEEEWWWOOOFFFCCCYYYCCCLLLOOONNNEEENNNEEETTTWWWOOORRRKKKSSS..........................................................................................444333 3 Advancing from Research to Implementation ........................................................ 45 4 Realizing a Wireless Backhaul Network ................................................................. 47 5 Exploring the Scope of Solutions ............................................................................ 49 5.1 Components ..................................................................................................... 49 5.1.1 Cyclone Access Point Module and Cyclone OFDM Access Point Module ..... 49 5.1.2 Advantage Access Point Module .................................................................... 49 5.1.3 Cyclone Access Point Cluster and Cyclone OFDM Access Point Cluster ...... 50 5.1.4 Canopy Subscriber Module ............................... Error! Bookmark not defined. 5.1.5 Advantage Subscriber Module ........................................................................ 51 5.1.6 Cyclone Lite Subscriber Module ..................................................................... 51 5.1.7 900-MHz AP and SM ....................................................................................... 52 5.1.8 Cyclone .............................................................. Error! Bookmark not defined. 5.1.9 Backhaul Module ............................................................................................. 53 5.1.10 Radio Adjustable Power Capabilities ............................................................ 53 5.1.11 Cluster Management Module-2 (Part 1008CK-2) .......................................... 53 5.1.12 Cluster Management Module micro (Part 1070CK) ...................................... 54 5.1.13 GPS Antenna ................................................................................................. 55 5.1.14 Surge Suppressor (Part 600SS) .................................................................... 55 5.1.15 Accessory Components ................................................................................ 55 5.2 Frequency Band Ranges ................................................................................. 60 5.3 Cyclone Product Comparisons ........................................................................ 60 5.3.1 Cyclone Product Applications.......................................................................... 60 5.3.2 Link Performance and Encryption Comparisons ............................................. 61 5.3.3 Cluster Management Product Comparison ..................................................... 63 5.4 Antennas for Connection to 900-MHz Modules ............................................... 64 5.4.1 Certified Connectorized Flat Panel Antennas ................................................. 64 5.4.2 Third-party Certified Connectorized Flat Panel Antenna ................................ 65 5.5 Adjunctive Software Products .......................................................................... 65 5.6 Bandwidth and Authentication Manager .......................................................... 66 5.7 Prizm ................................................................................................................ 67 5.7.1 Network Definition and Element Discovery ..................................................... 67 5.7.2 Monitoring and Fault Management ................................................................. 68 5.7.3 Element Management ..................................................................................... 68 5.7.4 BAM Subsystem in Prizm ................................................................................ 68 5.7.5 Northbound Interface ....................................................................................... 69 5.8 License Management ....................................................................................... 69 5.9 Specifications and Limitations .......................................................................... 71 5.9.1 Radios ............................................................................................................. 71 5.9.2 Cluster Management Products ........................................................................ 72 5.9.3 300SS and 600SS Surge Suppressors ........................................................... 73 6 Differentiating Among Components ....................................................................... 75 6.1 Interpreting Model (Part) Number .................................................................... 75 6.2 Sorted Model Numbers .................................................................................... 78 6.3 Interpreting Electronic Serial Number (ESN) ................................................... 79 6.4 Finding the Model (Part) Number and ESN ..................................................... 79 Draft5forRegulatoryReview 7 Cyclone Link Characteristics ................................................................................... 81 7.1 Understanding Bandwidth Management .......................................................... 81 7.1.1 Downlink Frame Contents ............................................................................... 81 7.1.2 Uplink Frame Contents .................................................................................... 81 7.1.3 Default Frame Structures ................................................................................ 82 7.1.4 Media Access Control and AP Capacity ......................................................... 83 7.1.5 Cyclone Slot Usage ......................................................................................... 83 7.1.6 Data Transfer Capacity ................................................................................... 83 7.1.7 Maximum Information Rate (MIR) Parameters ............................................... 84 7.1.8 Committed Information Rate ........................................................................... 86 7.1.9 Bandwidth from the SM Perspective ............................................................... 86 7.1.10 Interaction of Burst Allocation and Sustained Data Rate Settings ................ 86 7.1.11 High-priority Bandwidth ................................................................................. 86 7.1.12 Hardware Scheduling .................................................................................... 88 7.1.13 2X Operation ................................................................................................. 90 7.1.14 3X Operation (Cyclone OFDM modules only) ............................................... 93 7.2 Understanding Synchronization ....................................................................... 93 7.2.1 GPS Synchronization ...................................................................................... 93 7.2.2 Passing Sync in a Single Hop ......................................................................... 95 7.2.3 Passing Sync in an Additional Hop ................................................................. 95 8 Meeting Link Requirements ..................................................................................... 99 8.1 AP-SM Links .................................................................................................... 99 8.2 BH-BH Links .................................................................................................. 101 9 Previewing Network Configurations ..................................................................... 103 9.1 Viewing Typical Layouts ................................................................................ 103 9.2 Viewing Case Studies .................................................................................... 105 10 Accessing Features .............................................................................................. 107 10.1 Activating Features....................................................................................... 114 10.1.1 Fixed License Keys ..................................................................................... 114 10.2 Enabling Features ........................................................................................ 115 11 Acquiring Proficiencies ........................................................................................ 117 11.1 Understanding RF Fundamentals ................................................................ 117 11.2 Understanding IP Fundamentals .................................................................. 117 Draft5forRegulatoryReview 11.3 Acquiring a Cyclone Demonstration Kit ........................................................ 117 11.3.1 900-MHz with Integrated Antenna and Band-pass Filter Demonstration Kit117 11.3.2 900-MHz with Connectorized Antenna Demonstration Kit .......................... 118 11.3.3 2.4-GHz with Adjustable Power Set to Low Demonstration Kit .................. 118 11.3.4 2.4-GHz with Adjustable Power Set to High Demonstration Kit .................. 118 11.3.5 5.1-GHz Demonstration Kit ......................................................................... 119 11.3.6 5.2-GHz Demonstration Kit ......................................................................... 119 11.3.7 5.4-GHz Demonstration Kit ......................................................................... 119 11.3.8 5.7-GHz with Integrated Antenna Demonstration Kit .................................. 120 11.3.9 5.7-GHz with Connectorized Antenna and Adjustable Power Set to Low .. 120 11.3.10 Demonstration Kit Part Numbers ................................................................. 121 11.4 Acquiring a Cyclone Starter Kit .................................................................... 121 11.4.1 900-MHz with Integrated Antenna and Band-pass Filter Starter Kit ........... 121 11.4.2 900-MHz with Connectorized Antenna Starter Kit ....................................... 122 11.4.3 2.4-GHz with Adjustable Power Set to Low Starter Kit ............................... 122 11.4.4 2.4-GHz with Adjustable Power Set to High Starter Kit .............................. 122 11.4.5 5.1-GHz Starter Kit ...................................................................................... 123 11.4.6 5.2-GHz Starter Kit ...................................................................................... 123 11.4.7 5.4-GHz Starter Kit ...................................................................................... 123 11.4.8 5.7-GHz with Integrated Antenna Starter Kit ............................................... 124 11.4.9 5.7-GHz with Connectorized Antenna and Adjustable Power Set to Low .. 124 11.4.10 Starter Kit Part Numbers ............................................................................. 124 11.5 Evaluating Cyclone Training Options ........................................................... 125 11.6 Attending On-line Knowledge Sessions ....................................................... 125 PPPLLLAAANNNNNNIIINNNGGGGGGUUUIIIDDDEEE.................................................................................................................................................................................111222777 12 Engineering Your RF Communications .............................................................. 129 12.1 Anticipating RF Signal Loss ......................................................................... 129 12.1.1 Understanding Attenuation .......................................................................... 129 12.1.2 Calculating Free Space Path Loss .............................................................. 129 12.1.3 Calculating Rx Signal Level ......................................................................... 129 12.1.4 Calculating Fade Margin ............................................................................. 130 12.2 Analyzing the RF Environment ..................................................................... 131 12.2.1 Mapping RF Neighbor Frequencies ............................................................ 131 Draft5forRegulatoryReview 12.2.2 Anticipating Reflection of Radio Waves ...................................................... 132 12.2.3 Noting Possible Obstructions in the Fresnel Zone ...................................... 132 12.2.4 Radar Signature Detection and Shutdown .................................................. 133 12.3 Using Jitter to Check Received Signal Quality (Cyclone FSK Only) ............ 134 12.4 Using Link Efficiency to Check Received Signal Quality .............................. 135 12.4.1 Comparing Efficiency in 1X Operation to Efficiency in 2X Operation .......... 135 12.4.2 When to Switch from 2X to 1X Operation Based on 60% Link Efficiency ... 135 12.5 Considering Frequency Band Alternatives ................................................... 136 12.5.1 900-MHz Channels ...................................................................................... 137 12.5.2 2.4-GHz Channels ....................................................................................... 137 12.5.3 5.2-GHz Channels ....................................................................................... 138 12.5.4 5.4-GHz Channels ....................................................................................... 138 12.5.5 5.4-GHz OFDM Channels ........................................................................... 139 12.5.6 5.7-GHz Channels ....................................................................................... 140 12.5.7 Channels Available for PTP 400 and PTP 600 radios ................................ 140 12.5.8 Example Channel Plans for AP Clusters ..................................................... 140 12.5.9 Multiple Access Points Clusters .................................................................. 142 12.6 Selecting Sites for Network Elements .......................................................... 143 12.6.1 Resources for Maps and Topographic Images ........................................... 144 12.6.2 Surveying Sites............................................................................................ 144 12.6.3 Assuring the Essentials ............................................................................... 145 12.6.4 Finding the Expected Coverage Area ......................................................... 145 12.6.5 Clearing the Radio Horizon ......................................................................... 146 12.6.6 Calculating the Aim Angles ......................................................................... 146 12.7 Collocating Cyclone Modules ....................................................................... 147 12.8 Deploying a Remote AP ............................................................................... 148 12.8.1 Remote AP Performance ............................................................................ 149 12.8.2 Example Use Case for RF Obstructions ..................................................... 149 12.8.3 Example Use Case for Passing Sync ......................................................... 150 12.8.4 Physical Connections Involving the Remote AP ......................................... 151 12.9 Diagramming Network Layouts .................................................................... 152 12.9.1 Accounting for Link Ranges and Data Handling Requirements .................. 152 12.9.2 Avoiding Self Interference ........................................................................... 152 12.9.3 Avoiding Other Interference ........................................................................ 154 13 Engineering Your IP Communications ................................................................ 155 Draft5forRegulatoryReview 13.1.1 13.1 Understanding Addresses ............................................................................ 155 IP Address ................................................................................................... 155 13.2 Dynamic or Static Addressing ...................................................................... 155 13.2.1 When a DHCP Server is Not Found ............................................................ 155 13.3 Network Address Translation (NAT) ............................................................. 156 13.3.1 NAT, DHCP Server, DHCP Client, and DMZ in SM .................................... 156 13.3.2 NAT and VPNs ............................................................................................ 161 13.4 Developing an IP Addressing Scheme ......................................................... 162 13.4.1 Address Resolution Protocol ....................................................................... 162 13.4.2 Allocating Subnets ....................................................................................... 162 13.4.3 Selecting Non-routable IP Addresses ......................................................... 163 14 Engineering VLANs ............................................................................................... 165 14.1 SM Membership in VLANs ........................................................................... 165 14.2 Priority on VLANs (802.1p) ........................................................................... 166 IIINNNSSSTTTAAALLLLLLAAATTTIIIOOONNNAAANNNDDDCCCOOONNNFFFIIIGGGUUURRRAAATTTIIIOOONNNGGGUUUIIIDDDEEE....................................111666777 15 Avoiding Hazards .................................................................................................. 169 15.1 Exposure Separation Distances ................................................................... 169 15.1.1 Details of Exposure Separation Distances Calculations and Power Compliance Margins .................................................................................... 169 15.2 Grounding Cyclone Equipment .................................................................... 171 15.2.1 Grounding Infrastructure Equipment ........................................................... 171 15.2.2 Grounding SMs............................................................................................ 172 15.3 Conforming to Regulations ........................................................................... 174 15.4 Protecting Cables and Connections ............................................................. 174 16 Testing the Components ...................................................................................... 177 16.1 Unpacking Components ............................................................................... 177 16.2 Configuring for Test ...................................................................................... 177 16.2.1 Configuring the Computing Device for Test ................................................ 177 16.2.2 Default Module Configuration ...................................................................... 178 16.2.3 Component Layout ...................................................................................... 178 16.2.4 Diagnostic LEDs .......................................................................................... 179 16.2.5 CMM2 Component Layout .......................................................................... 180 Draft5forRegulatoryReview 16.2.6 CMMmicro Component Layout .................................................................... 180 16.2.7 Standards for Wiring .................................................................................... 182 16.2.8 Best Practices for Cabling ........................................................................... 182 16.2.9 Recommended Tools for Wiring Connectors .............................................. 182 16.2.10 Wiring Connectors ....................................................................................... 182 16.2.11 Alignment ToneTechnical Details ............................................................ 184 16.3 Configuring a Point-to-Multipoint Link for Test ............................................. 184 16.3.1 Quick Start Page of the AP ......................................................................... 185 16.3.2 Time Tab of the AP ..................................................................................... 191 16.3.3 Session Status Tab of the AP ..................................................................... 193 16.3.4 Beginning the Test of Point-to-Multipoint Links ........................................... 197 16.3.5 Remote Subscribers Tab of the AP ............................................................. 197 16.3.6 General Status Tab of the SM ..................................................................... 198 16.3.7 Continuing the Test of Point-to-Multipoint Links .......................................... 201 16.3.8 General Status Tab of the AP ..................................................................... 202 16.3.9 Concluding the Test of Point-to-Multipoint Links ......................................... 204 16.4 Configuring a Point-to-Point Link for Test .................................................... 204 16.4.1 Quick Start Page of the BHM ...................................................................... 205 16.4.2 Time Tab of the BHM .................................................................................. 207 16.4.3 Beginning the Test of Point-to-Point Links .................................................. 211 16.4.4 Continuing the Test of Point-to-Point Links ................................................. 213 16.4.5 General Status Tab of the BHM .................................................................. 214 16.4.6 Concluding the Test of Point-to-Point Links ................................................ 216 16.5 Configuring a CMMmicro for Test ................................................................ 217 16.5.1 Setting up a CMMmicro ............................................................................... 217 16.5.2 Status Page of the CMMmicro .................................................................... 222 16.5.3 Configuration Page of the CMMmicro ......................................................... 225 16.5.4 Configuring Modules for Connection to CMMmicro .................................... 232 16.5.5 Event Log Page of the CMMmicro .............................................................. 232 16.5.6 GPS Status Page of the CMMmicro ............................................................ 232 16.5.7 Port MIB Page of the CMMmicro ................................................................. 233 17 Preparing Components for Deployment ............................................................. 235 17.1 Correlating Component-specific Information ................................................ 235 17.2 Ensuring Continuing Access to the Modules ................................................ 235 18 Configuring for the Destination ........................................................................... 237 Draft5forRegulatoryReview 18.1 Configuring an AP for the Destination .......................................................... 237 18.1.1 General Tab of the AP ................................................................................. 237 18.1.2 IP Tab of the AP .......................................................................................... 241 18.1.3 Radio Tab of the AP .................................................................................... 243 18.1.4 SNMP Tab of the AP ................................................................................... 248 18.1.5 Quality of Service (QoS) Tab of the AP ...................................................... 251 18.1.6 Security Tab of the AP ................................................................................ 253 18.1.7 VLAN Tab of the AP .................................................................................... 256 18.1.8 VLAN Membership Tab of the AP ............................................................... 258 18.1.9 DiffServe Tab of the AP ............................................................................... 259 18.1.10 Unit Settings Tab of the AP ......................................................................... 261 18.2 Configuring an SM for the Destination ......................................................... 262 18.2.1 General Tab of the SM ................................................................................ 263 18.2.2 NAT and IP Tabs of the SM with NAT Disabled .......................................... 265 18.2.3 NAT and IP Tabs of the SM with NAT Enabled .......................................... 271 18.2.4 Radio Tab of the SM ................................................................................... 276 18.2.5 SNMP Tab of the SM .................................................................................. 279 18.2.6 Quality of Service (QoS) Tab of the SM ...................................................... 282 18.2.7 Security Tab of the SM ................................................................................ 285 18.2.8 VLAN Tab of the SM ................................................................................... 287 18.2.9 VLAN Membership Tab of the SM............................................................... 289 18.2.10 DiffServe Tab of the SM .............................................................................. 290 18.2.11 Protocol Filtering Tab of the SM .................................................................. 292 18.2.12 NAT Port Mapping Tab of the SM ............................................................... 293 18.2.13 Unit Settings Tab of the SM ........................................................................ 294 18.3 Setting the Configuration Source ................................................................. 295 18.4 Configuring a BH Timing Master for the Destination .................................... 297 18.4.1 General Tab of the BHM ............................................................................. 298 18.4.2 IP Tab of the BHM ....................................................................................... 301 18.4.3 Radio Tab of the BHM ................................................................................. 303 18.4.4 SNMP Tab of the BHM ................................................................................ 306 18.4.5 Security Tab of the BHM ............................................................................. 309 18.4.6 DiffServe Tab of the BHM ........................................................................... 311 18.4.7 Unit Settings Tab of the BHM ...................................................................... 313 18.5 Configuring a BH Timing Slave for the Destination ...................................... 315 18.5.1 General Tab of the BHS .............................................................................. 315 Draft5forRegulatoryReview 19 18.5.2 IP Tab of the BHS ....................................................................................... 318 18.5.3 Radio Tab of the BHS ................................................................................. 320 18.5.4 SNMP Tab of the BHS ................................................................................ 323 18.5.5 Quality of Service (QoS) Tab of the BHS .................................................... 325 18.5.6 Security Tab of the BHS .............................................................................. 326 18.5.7 DiffServe Tab of the BHS ............................................................................ 328 18.5.8 Unit Settings Tab of the BHS ...................................................................... 329 18.6 Adjusting Transmitter Output Power ............................................................ 330 19.5 Installing Components ......................................................................................... 333 19.1 PDA Access to Cyclone Modules ................................................................. 333 19.2 Installing an AP ............................................................................................ 337 Installing a Connectorized Flat Panel Antenna ............................................ 337 19.3 19.4 Installing a GPS Antenna ............................................................................. 338 19.4.1 Recommended Materials for Cabling the GPS Antenna ............................. 339 19.4.2 Cabling the GPS Antenna ........................................................................... 339 Installing a CMM2......................................................................................... 339 19.5.1 CMM2 Installation Temperature Range ...................................................... 339 19.5.2 Recommended Tools for Mounting a CMM2 .............................................. 340 19.5.3 Mounting a CMM2 ....................................................................................... 340 19.5.4 Cabling a CMM2 .......................................................................................... 341 19.5.5 Verifying CMM2 Connections ...................................................................... 345 Installing a CMMmicro .................................................................................. 345 19.6.1 CMMmicro Temperature Range .................................................................. 346 19.6.2 Recommended Tools for Mounting a CMMmicro ........................................ 346 19.6.3 Mounting a CMMmicro ................................................................................ 346 19.6.4 Installing the Power Supply for the CMMmicro ........................................... 346 19.6.5 Cabling a CMMmicro ................................................................................... 348 19.6.6 Verifying CMMmicro Connections ............................................................... 349 19.7 Installing an SM ............................................................................................ 349 19.8 Verifying an AP-SM Link .............................................................................. 353 Installing a Reflector Dish............................................................................. 356 19.9 19.9.1 Both Modules Mounted at Same Elevation ................................................. 356 19.9.2 Modules Mounted at Different Elevations ................................................... 357 19.9.3 Mounting Assembly ..................................................................................... 357 19.10 Installing a BH Timing Master ...................................................................... 358 19.6 Draft5forRegulatoryReview 19.11 Installing a BH Timing Slave ........................................................................ 360 19.12 Upgrading a BH Link to BH20 ...................................................................... 361 19.13 Verifying a BH Link ....................................................................................... 361 20 Verifying System Functionality ............................................................................ 365 OOOPPPEEERRRAAATTTIIIOOONNNSSSGGGUUUIIIDDDEEE.....................................................................................................................................................................333666777 21 Growing Your Network ......................................................................................... 369 21.1 Monitoring the RF Environment .................................................................... 369 21.1.1 Spectrum Analyzer (Not available for Cyclone OFDM) .............................. 369 21.1.2 Graphical Spectrum Analyzer Display (Not available for Cyclone OFDM) . 370 21.1.3 Using the AP as a Spectrum Analyzer (Not available for Cyclone OFDM) 370 21.2 Considering Software Release Compatibility ............................................... 372 21.2.1 Designations for Hardware in Radios .......................................................... 372 21.2.2 CMMmicro Software and Hardware Compatibility ...................................... 373 21.2.3 MIB File Set Compatibility ........................................................................... 373 21.3 Redeploying Modules ................................................................................... 373 21.3.1 Wiring to Extend Network Sync ................................................................... 374 22 Securing Your Network ........................................................................................ 375 22.1 Isolating APs from the Internet ..................................................................... 375 22.2 Encrypting Cyclone Radio Transmissions .................................................... 375 22.2.1 DES Encryption ........................................................................................... 375 22.2.2 AES Encryption ........................................................................................... 375 22.2.3 AES-DES Operability Comparisons ............................................................ 376 22.3 Managing Module Access by Passwords ..................................................... 377 22.3.1 Adding a User for Access to a Module ........................................................ 377 22.3.2 Overriding Forgotten IP Addresses or Passwords on AP, SM, or BH ........ 379 22.3.3 Overriding Forgotten IP Addresses or Passwords on CMMmicro .............. 381 22.4 Requiring SM Authentication ........................................................................ 382 22.5 Filtering Protocols and Ports ........................................................................ 382 22.5.1 Port Filtering with NAT Enabled .................................................................. 382 22.5.2 Protocol and Port Filtering with NAT Disabled ............................................ 383 22.6 Encrypting Downlink Broadcasts .................................................................. 384 22.7 Isolating SMs ................................................................................................ 384 Draft5forRegulatoryReview 22.8 Filtering Management through Ethernet ....................................................... 385 22.9 Allowing Management from Only Specified IP Addresses ........................... 385 22.10 Configuring Management IP by DHCP ......................................................... 385 23 Managing Bandwidth and Authentication .......................................................... 387 23.1 Managing Bandwidth without BAM ............................................................... 387 23.2 Bandwidth and Authentication Manager (BAM) Services and Features ...... 387 23.2.1 Bandwidth Manager Capability .................................................................... 387 23.2.2 Authentication Manager Capability.............................................................. 389 24 Managing the Network From a Management Station (NMS) ............................. 391 24.1 Roles of Hardware and Software Elements ................................................. 391 24.1.1 Role of the Agent ......................................................................................... 391 24.1.2 Role of the Managed Device ....................................................................... 391 24.1.3 Role of the NMS .......................................................................................... 391 24.1.4 Dual Roles for the NMS ............................................................................... 391 24.1.5 Simple Network Management Protocol (SNMP) Commands ..................... 391 24.1.6 Traps from the Agent ................................................................................... 392 24.1.7 AP SNMP Proxy to SMs .............................................................................. 392 24.2 Management Information Base (MIB) .......................................................... 392 24.2.1 Cascading Path to the MIB .......................................................................... 392 24.2.2 Object Instances .......................................................................................... 393 24.2.3 Management Information Base Systems and Interface (MIB-II) ................. 393 24.2.4 Cyclone Enterprise MIB ............................................................................... 394 24.3 Configuring Modules for SNMP Access ....................................................... 395 24.4 Objects Defined in the Cyclone Enterprise MIB ........................................... 395 24.4.1 AP, SM, and BH Objects ............................................................................. 396 24.4.2 AP and BH Timing Master Objects.............................................................. 398 24.4.3 SM and BH Timing Slave Objects ............................................................... 402 24.4.4 CMMmicro Objects ...................................................................................... 405 24.5 Objects Defined in the PTP 400 and PTP 600 series Bridges MIB .............. 408 24.6 Objects Supported in the Cyclone 30/60-Mbps BH ...................................... 409 24.7 Objects Supported in the Cyclone 150/300-Mbps BH .................................. 409 24.8 Interface Designations in SNMP .................................................................. 409 24.9 Traps Provided in the Cyclone Enterprise MIB ............................................ 410 24.10 Traps Provided in the PTP 400 Series Bridge MIB ...................................... 410 Draft5forRegulatoryReview 24.11 Traps Provided in the PTP 600 Series Bridge MIB ...................................... 410 24.12 MIB Viewers ................................................................................................. 411 25 Using the Cyclone Network Updater Tool (CNUT) ............................................. 413 25.1 CNUT Functions ........................................................................................... 413 25.2 Network Element Groups ............................................................................. 413 25.3 Network Layers ............................................................................................ 413 25.4 Script Engine ................................................................................................ 414 25.5 Software Dependencies for CNUT ............................................................... 414 25.6 CNUT Download .......................................................................................... 414 26 Using Informational Tabs in the GUI ................................................................... 415 26.1 Viewing General Status (All) ........................................................................ 415 26.2 Viewing Session Status (AP, BHM) .............................................................. 415 26.3 Viewing Remote Subscribers (AP, BHM) ..................................................... 416 Interpreting Messages in the Event Log (All) ............................................... 416 26.4 26.4.1 Time and Date Stamp ................................................................................. 416 26.4.2 Event Log Data Collection ........................................................................... 416 26.4.3 Messages that Flag Abnormal Events ........................................................ 419 26.4.4 Messages that Flag Normal Events ............................................................ 419 26.5 Viewing the Network Interface Tab (All) ....................................................... 420 26.6 Interpreting Radio Statistics in the Scheduler Tab (All) ................................ 421 26.7 Viewing the List of Registration Failures (AP, BHM) .................................... 422 26.8 Interpreting Data in the Bridging Table (All) ................................................. 423 26.9 Translation Table (SM) ................................................................................. 424 26.10 Interpreting Data in the Ethernet Tab (All) .................................................... 424 26.11 Interpreting RF Control Block Statistics in the Radio Tab (All) ..................... 427 26.12 Interpreting Data in the VLAN Tab (AP, SM) ................................................ 428 26.13 Data VC (All) ................................................................................................ 430 26.14 Filter (SM)..................................................................................................... 431 26.15 NAT Stats (SM) ............................................................................................ 432 26.15.1 NAT DHCP Statistics (SM) .......................................................................... 433 26.15.2 Interpreting Data in the GPS Status Page (AP, BHM) ................................ 434 27 Using Tools in the GUI .......................................................................................... 435 27.1 Using the Spectrum Analyzer Tool (SM, BHS) ............................................. 435 Draft5forRegulatoryReview 27.2 Using the Alignment Tool (SM, BHS) ........................................................... 435 27.3 Using the Link Capacity Test Tool (All) ........................................................ 438 27.4 Using the AP Evaluation or BHM Evaluation Tool (SM, BHS) ..................... 440 27.5 Using the Frame Calculator Tool (All) .......................................................... 444 27.6 Using the SM Configuration Tool (AP, BHM) ............................................... 449 27.7 Using the BER Results Tool (SM, BHS) ....................................................... 450 28 Maintaining Your Cyclone Software .................................................................... 451 28.1 History of System Software Upgrades ......................................................... 451 28.1.1 Cyclone Release 8 Features ....................................................................... 451 28.1.2 Cyclone Release 8 Fixes ............................................................................. 451 28.2 History of CMMmicro Software Upgrades .................................................... 451 28.3 Typical Contents of Release Notes .............................................................. 451 28.4 Typical Upgrade Process ............................................................................. 452 28.4.1 Downloading Software and Release Notes ................................................. 452 29 Rebranding Module Interface Screens ................................................................ 453 30 Toggling Remote Access Capability ................................................................... 457 30.1 Denying All Remote Access ......................................................................... 457 30.2 Reinstating Remote Access Capability ........................................................ 457 31 Setting Up a Protocol Analyzer on Your Cyclone Network ............................... 459 31.1 Analyzing Traffic at an SM ........................................................................... 459 31.2 Analyzing Traffic at an AP or BH with No CMM ........................................... 460 31.3 Analyzing Traffic at an AP or BH with a CMM .............................................. 460 31.4 Example of a Protocol Analyzer Setup for an SM ........................................ 461 32 Troubleshooting .................................................................................................... 469 32.1 General Planning for Troubleshooting .......................................................... 469 32.2 General Fault Isolation Process ................................................................... 469 32.3 Questions to Help Isolate the Problem ......................................................... 470 32.4 Secondary Steps .......................................................................................... 470 32.5 Procedures for Troubleshooting ................................................................... 471 32.5.1 Module Has Lost or Does Not Establish Connectivity ................................. 471 32.5.2 NAT/DHCP-configured SM Has Lost or Does Not Establish Connectivity . 472 32.5.3 SM Does Not Register to an AP .................................................................. 474 Draft5forRegulatoryReview 32.5.4 BHS Does Not Register to the BHM ........................................................... 475 32.5.5 Module Has Lost or Does Not Gain Sync ................................................... 476 32.5.6 Module Does Not Establish Ethernet Connectivity ...................................... 477 32.5.7 Module Does Not Power Up ........................................................................ 478 32.5.8 Power Supply Does Not Produce Power .................................................... 478 32.5.9 CMM2 Does Not Power Up ......................................................................... 479 32.5.10 CMM2 Does Not Pass Proper GPS Sync to Connected Modules .............. 479 32.5.11 Module Software Cannot be Upgraded ....................................................... 480 32.5.12 Module Functions Properly, Except Web Interface Became Inaccessible .. 480 33 Obtaining Technical Support ............................................................................... 481 34 Getting Warranty Assistance ............................................................................... 487 RRREEEFFFEEERRREEENNNCCCEEEIIINNNFFFOOORRRMMMAAATTTIIIOOONNN....................................................................................................................................444888999 35 Administering Modules through telnet Interface ............................................... 491 36 Regulatory and Legal Notices .............................................................................. 493 36.1 Important Note on Modifications................................................................... 493 36.2 National and Regional Regulatory Notices ................................................... 493 36.2.1 U.S. Federal Communication Commission (FCC) Notification ................... 493 36.2.2 Industry Canada (IC) Notification ................................................................ 495 36.2.3 Regulatory Requirements for CEPT Member States (www.cept.org) ......... 496 36.2.4 European Union Notification for 5.7 GHz Product ....................................... 497 36.2.5 Equipment Disposal .................................................................................... 498 36.2.6 EU Declaration of Conformity for RoHS Compliance .................................. 498 36.2.7 UK Notification ............................................................................................. 498 36.2.8 Belgium Notification ..................................................................................... 498 36.2.9 Luxembourg Notification .............................................................................. 498 36.2.10 Czech Republic Notification ........................................................................ 499 36.2.11 Norway Notification ..................................................................................... 499 36.2.12 Greece Notification ...................................................................................... 499 36.2.13 Brazil Notification ......................................................................................... 499 36.2.14 Australia Notification .................................................................................... 500 36.2.15 Labeling and Disclosure Table for China .................................................... 500 36.3 RF Exposure ................................................................................................ 501 Draft5forRegulatoryReview 36.4 Legal Notices ............................................................................................... 501 36.4.1 Software License Terms and Conditions .................................................... 501 36.4.2 Hardware Warranty in U.S. ........................................................................ 503 36.4.3 Limit of Liability ............................................................................................ 503 37 Additional Resources ........................................................................................... 505 38 History of Documentation .................................................................................... 507 GGGLLLOOOSSSSSSAAARRRYYY........................................................................................................................................................................................................................555000999 Draft5forRegulatoryReview LISTOFFIGURES Figure 1: Cyclone Advantage Platform GUI logo .............................................................. 49 Figure 2: Pole-mounted AP cluster ................................................................................... 50 Figure 3: OFDM AP - Antenna and Radio ......................................................................... 50 Figure 4: Structure-mounted SM ....................................................................................... 50 Figure 5: OFDM SM, front and side views ........................................................................ 51 Figure 6: Examples of flat panel antennas with 900-MHz modules .................................. 52 Figure 7: Dish-mounted 10- or 20-Mbps BH ..................................................................... 53 Figure 8: CMM2 enclosure ................................................................................................ 54 Figure 9: CMM2 pole-mounted ......................................................................................... 54 Figure 10: Last Mile Gear GPS antenna ........................................................................... 55 Figure 11: 600SS surge suppressor ................................................................................. 55 Figure 12: ACPS110-03A power supply ........................................................................... 56 Figure 13: ACPSSW-09A power supply ............................................................................ 56 Figure 14: 27RD with mounted module ............................................................................. 56 Figure 15: SMMB1 SM support bracket ............................................................................ 57 Figure 16: ACATHS-01 alignment headset ....................................................................... 59 Figure 17: HSG-01 Housing .............................................................................................. 59 Figure 18: Uplink data slot usage ...................................................................................... 83 Figure 19: TDD dividing Cyclone frames .......................................................................... 84 Figure 20: Uplink and downlink rate caps adjusted to apply aggregate cap ..................... 85 Figure 21: Uplink and downlink rate cap adjustment example .......................................... 85 Figure 22: Cyclone frame structure ................................................................................... 88 Figure 23: One unsynchronized AP in cluster ................................................................... 94 Figure 24: GPS timing throughout the Cyclone network (Cyclone FSK shown) ............... 95 Figure 25: Additional link to extend network sync, Design 3 ............................................. 96 Figure 26: Additional link to extend network sync, Design 4 ............................................. 96 Figure 27: Additional link to extend network sync, Design 5 ............................................. 97 Figure 28: Typical network layout with no BH ................................................................. 103 Figure 29: Typical network layout with BH ...................................................................... 104 Figure 30: Typical multiple-BH network layout ................................................................ 104 Figure 31: Determinants in Rx signal level ...................................................................... 130 Draft5forRegulatoryReview Figure 32: Example layout of 7 Access Point clusters .................................................... 143 Figure 33: Fresnel zone .................................................................................................. 145 Figure 34: Variables for calculating angle of elevation (and depression) ........................ 146 Figure 35: Double-hop backhaul links ............................................................................. 147 Figure 36: Remote AP deployment ................................................................................. 148 Figure 37: Example 900-MHz remote AP behind 2.4-GHz SM ....................................... 150 Figure 38: Remote AP wired to SM that also serves a customer .................................... 151 Figure 39: Remote AP wired to SM that serves as a relay ............................................. 152 Figure 40: NAT Disabled implementation ....................................................................... 157 Figure 41: NAT with DHCP Client and DHCP Server implementation ............................ 158 Figure 42: NAT with DHCP Client implementation .......................................................... 159 Figure 43: NAT with DHCP Server implementation ........................................................ 160 Figure 44: NAT without DHCP implementation ............................................................... 161 Figure 45: Example of IP address in Class B subnet ...................................................... 162 Figure 46: Cyclone base cover, attached and detached ................................................. 178 Figure 47: Cyclone CMM2, bottom view ......................................................................... 180 Figure 48: Cluster Management Module micro ............................................................... 181 Figure 49: RJ-45 pinout for straight-through Ethernet cable ........................................... 183 Figure 50: RJ-45 pinout for crossover Ethernet cable ..................................................... 183 Figure 51: RJ-11 pinout for straight-through sync cable ................................................. 184 Figure 52: Quick Start tab of AP, example ...................................................................... 186 Figure 53: Radio Frequency Carrier tab of AP, example ................................................ 187 Figure 54: Synchronization tab of AP, example .............................................................. 188 Figure 55: LAN IP Address tab of AP, example .............................................................. 189 Figure 56: Review and Save Configuration tab of AP, example ..................................... 190 Figure 57: Time tab of AP, example ................................................................................ 191 Figure 58: Session Status tab data from AP, example ................................................... 193 Figure 59: Remote Subscribers tab of AP, example ....................................................... 197 Figure 60: General Status tab of SM, example ............................................................... 198 Figure 61: General Status tab of AP, example ................................................................ 202 Figure 62: Quick Start tab of BHM, example ................................................................... 206 Figure 63: Time tab of BHM, example ............................................................................ 208 Figure 64: Remote Subscribers tab of BHM, example .................................................... 210 Figure 65: General Status tab of BHS, example ............................................................. 211 Draft5forRegulatoryReview Figure 66: General Status tab of BHM, example ............................................................ 214 Figure 67: CMMmicro layout ........................................................................................... 217 Figure 68: CMMmicro door label ..................................................................................... 219 Figure 69: CMMmicro circuit board ................................................................................. 220 Figure 70: CMMmicro connections ................................................................................. 221 Figure 71: Status page of CMMmicro, example .............................................................. 222 Figure 72: Configuration page of CMMmicro, example ................................................... 225 Figure 73: GPS Status page of CMMmicro, example ..................................................... 232 Figure 74: Port MIB page of CMMmicro, example .......................................................... 233 Figure 75: General tab of AP, example ........................................................................... 238 Figure 76: IP tab of AP, example .................................................................................... 241 Figure 77: Radio tab of AP (900 MHz), example ............................................................ 243 Figure 78: SNMP tab of AP, example ............................................................................. 248 Figure 79: Quality of Service (QoS) tab of AP, example ................................................. 251 Figure 80: Security tab of AP, example ........................................................................... 253 Figure 81: VLAN tab of AP, example .............................................................................. 256 Figure 82: VLAN Membership tab of AP, example ......................................................... 258 Figure 83: DiffServe tab of AP, example ......................................................................... 259 Figure 84: Unit Settings tab of AP, example ................................................................... 261 Figure 85: General tab of SM, example .......................................................................... 263 Figure 86: NAT tab of SM with NAT disabled, example .................................................. 266 Figure 87: IP tab of SM with NAT disabled, example ...................................................... 269 Figure 88: NAT tab of SM with NAT enabled, example .................................................. 271 Figure 89: IP tab of SM with NAT enabled, example ...................................................... 275 Figure 90: Radio tab of SM, example .............................................................................. 276 Figure 91: SNMP tab of SM, example ............................................................................. 279 Figure 92: Quality of Service (QoS) tab of SM, example ................................................ 282 Figure 93: Security tab of SM, example .......................................................................... 285 Figure 94: VLAN tab of SM, example .............................................................................. 288 Figure 95: VLAN Membership tab of SM, example ......................................................... 289 Figure 96: DiffServe tab of SM, example ........................................................................ 290 Figure 97: Protocol Filtering tab of SM, example ............................................................ 292 Figure 98: NAT Port Mapping tab of SM, example ......................................................... 293 Figure 99: Unit Settings tab of SM, example ................................................................... 294 Draft5forRegulatoryReview Figure 100: General tab of BHM, example ...................................................................... 298 Figure 101: IP tab of BHM, example ............................................................................... 301 Figure 102: Radio tab of BHM, example ......................................................................... 303 Figure 103: SNMP tab of BHM, example ........................................................................ 306 Figure 104: Security tab of BHM, example ..................................................................... 309 Figure 105: DiffServe tab of BHM, example .................................................................... 311 Figure 106: Unit Settings tab of BHM, example .............................................................. 313 Figure 107: General tab of BHS, example ...................................................................... 315 Figure 108: IP tab of BHS, example ................................................................................ 318 Figure 109: Radio tab of BHS, example .......................................................................... 320 Figure 110: SNMP tab of BHS, example ......................................................................... 323 Figure 111: Quality of Service (QoS) tab of BHS, example ............................................ 325 Figure 112: Security tab of BHS, example ...................................................................... 326 Figure 113: DiffServe tab of BHS, example .................................................................... 328 Figure 114: Unit Settings tab of BHS, example ............................................................... 329 Figure 115: PDA Quick Status tab, example ................................................................... 334 Figure 116: PDA Spectrum Analyzer tab of SM, example .............................................. 334 Figure 117: PDA Spectrum Results tab of SM, example ................................................ 335 Figure 118: PDA Information tab of SM, example ........................................................... 335 Figure 119: PDA AP Evaluation tab of SM, example ...................................................... 336 Figure 120: PDA Aim tab of SM, example ...................................................................... 336 Figure 121: Detail of GPS antenna mounting ................................................................. 339 Figure 122: Detail of pole mounting ................................................................................ 340 Figure 123: Location of 115-/230-volt switch .................................................................. 341 Figure 124: Layout of logical connections in CMM2 ....................................................... 343 Figure 125: Cyclone CMM2, front view ........................................................................... 344 Figure 126: Port indicator LED on Ethernet switch ......................................................... 345 Figure 127: SM attachment to reflector arm .................................................................... 350 Figure 128: SM grounding per NEC specifications ......................................................... 350 Figure 129: Internal view of Cyclone 300SS Surge Suppressor ..................................... 351 Figure 130: Audible Alignment Tone kit, including headset and connecting cable ......... 352 Figure 131: AP/SM link status indications in the AP Session Status tab ........................ 355 Figure 132: Correct mount with reflector dish ................................................................. 356 Figure 133: Incorrect mount with reflector dish ............................................................... 357 Draft5forRegulatoryReview Figure 134: Mounting assembly, exploded view ............................................................. 358 Figure 135: BH attachment to reflector arm .................................................................... 359 Figure 136: Session Status tab of BHM .......................................................................... 363 Figure 137: Spectrum Analyzer tab of SM, example ....................................................... 370 Figure 138: General Status tab view for GUEST-level account ...................................... 378 Figure 139: Add User tab of SM, example ...................................................................... 379 Figure 140: RJ-11 pinout for the override plug ................................................................ 380 Figure 141: Categorical protocol filtering ........................................................................ 383 Figure 142: Session Status tab data, example ............................................................... 415 Figure 143: Event Log tab data, example ....................................................................... 418 Figure 144: Network Interface tab of AP, example ......................................................... 420 Figure 145: Network Interface tab of SM, example ......................................................... 420 Figure 146: Scheduler tab of SM, example ..................................................................... 421 Figure 147: SM Registration Failures tab of AP, example .............................................. 422 Figure 148: Bridging Table tab of AP, example .............................................................. 423 Figure 149: Translation Table tab of SM, example ......................................................... 424 Figure 150: Ethernet tab of AP, example ........................................................................ 425 Figure 151: Radio tab of Statistics page in SM, example ............................................... 427 Figure 152: VLAN tab of AP, example ............................................................................ 429 Figure 153: Data VC tab of SM, example ....................................................................... 430 Figure 154: Filter tab on SM, example ............................................................................ 432 Figure 155: Nat Stats tab on SM, example ..................................................................... 433 Figure 156: NAT DHCP Statistics tab in SM, example ................................................... 433 Figure 157: Alignment tab of BHS, example ................................................................... 435 Figure 158: Link Capacity Test tab with 1522-byte packet length, example ................... 438 Figure 159: Link Capacity Test tab with 64-byte packet length, example ....................... 439 Figure 160: AP Evaluation tab of SM, example .............................................................. 441 Figure 161: Frame Calculator tab, example .................................................................... 445 Figure 162: Calculated Frame Results section of Frame Calculator tab, example ......... 448 Figure 163: SM Configuration tab of AP, example .......................................................... 449 Figure 164: BER Results tab of SM, example ................................................................. 450 Figure 165: Example ftp session to transfer custom logo file .......................................... 454 Figure 166: Example telnet session to activate custom logo file ..................................... 455 Figure 167: Example telnet session to clear custom files ............................................... 456 Draft5forRegulatoryReview Figure 168: Protocol analysis at SM ............................................................................... 459 Figure 169: Protocol analysis at AP or BH not connected to a CMM .............................. 460 Figure 170: Protocol analysis at AP or BH connected to a CMM .................................... 461 Figure 171: IP tab of SM with NAT disabled and local accessibility ................................ 462 Figure 172: Local Area Connection Properties window .................................................. 463 Figure 173: Internet Protocol (TCP/IP) Properties window ............................................. 463 Figure 174: Ethereal Capture Options window ............................................................... 464 Figure 175: Ethereal Capture window ............................................................................. 465 Figure 176: <capture> - Ethereal window, Packet 1 selected ......................................... 466 Figure 177: <capture> - Ethereal window, Packet 14 selected ....................................... 467 Figure 178: NAT Table tab of SM, example .................................................................... 473 Figure 179: NAT DHCP Statistics tab of SM, example ................................................... 474 Figure 180: Event Log tab of SM, example ..................................................................... 476 Draft5forRegulatoryReview LISTOFTABLES Table 1: Cyclone User Guide organization scheme .......................................................... 36 Table 2: Examples of where to find information in this user guide .................................... 37 Table 3: Locations of screen captures and associated documentation ............................ 38 Table 4: Font types ........................................................................................................... 41 Table 5: Admonition types ................................................................................................. 41 Table 6: Essential user guide elements for new backhaul network implementation ......... 47 Table 7: Power supply descriptions .................................................................................. 55 Table 8: Recommended outdoor UTP Category 5E cables .............................................. 57 Table 9: Recommended indoor UTP Category 5E cables ................................................ 58 Table 10: Recommended antenna cables ........................................................................ 58 Table 11: Product applications per frequency band range ................................................ 60 Table 12: Products with encryption options available per frequency band, PTMP links ... 61 Table 13: Typical range and throughput per frequency band, PTMP links ....................... 62 Table 14: Typical range and throughput per frequency band, PTP links .......................... 63 Table 15: Cluster management product similarities and differences ................................ 63 Table 16: Cyclone applications and tools .......................................................................... 65 Table 17: Correct placement of license keys .................................................................... 70 Table 18: CMM2 specifications and limitations ................................................................. 72 Table 19: CMMmicro specifications and limitations .......................................................... 73 Table 20: Cyclone model numbers ................................................................................... 78 Table 21: Labels and locations of model (part) numbers and ESNs ................................. 79 Table 22: Characteristics of hardware scheduling ............................................................ 89 Table 23: Effect of 2X operation on throughput for the SM ............................................... 91 Table 24: Effects of network conditions on PTMP throughput ........................................ 100 Table 25: Comparison of SM products with Cyclone Advantage AP .............................. 100 Table 26: Cyclone features ............................................................................................. 107 Table 27: Demonstration Kit part numbers ..................................................................... 121 Table 28: Starter Kit part numbers .................................................................................. 124 Table 29: Signal quality levels indicated by jitter ............................................................. 134 Table 30: Recommended courses of action based on Efficiency in 2X operation .......... 135 Table 31: Example 900-MHz channel assignment by sector .......................................... 141 Draft5forRegulatoryReview Table 32: Example 2.4-GHz channel assignment by sector ........................................... 141 Table 33: Example 5.2-GHz channel assignment by sector ........................................... 141 Table 34: Example 5.4-GHz channel assignment by sector ........................................... 142 Table 35: Example 5.7-GHz channel assignment by sector ........................................... 142 Table 36: VLAN filters in point-to-multipoint modules ..................................................... 166 Table 37: Exposure separation distances ....................................................................... 169 Table 38: Calculated exposure distances and power compliance margins .................... 170 Table 39: Statistical incidence of current from lightning strikes ...................................... 172 Table 40: LEDs in AP and BHM ...................................................................................... 179 Table 41: LEDs in SM and BHS ...................................................................................... 179 Table 42: Port Configuration selections for CMMmicro ................................................... 227 Table 43: When changes become effective in CMMmicro .............................................. 231 Table 44: Control slot settings for all APs in cluster ........................................................ 245 Table 45: Recommended combined settings for typical operations ................................ 296 Table 46: Where feature values are obtained for an SM with authentication required ... 296 Table 47: Where feature values are obtained for an SM with authentication disabled ... 297 Table 48: Total gain per antenna .................................................................................... 331 Table 49: Patch antenna and reflector gain ........................ Error! Bookmark not defined. Table 50: Transmitter output power settings, example cases ......................................... 332 Table 51: Wire size for CMMmicro power runs of longer than 9 feet (2.8 m) .................. 347 Table 52: Hardware series by MAC address .................................................................. 372 Table 53: Hardware series differences ........................................................................... 372 Table 54: AP/BH compatibility with CMMmicro ............................................................... 373 Table 55: Ports filtered per protocol selections ............................................................... 384 Table 56: Example times to download for typical tiers of service with Cyclone AP ........ 388 Table 57: Example times to download for typical tiers of service with Advantage AP .... 389 Table 58: Categories of MIB-II objects ............................................................................ 393 Table 59: Cyclone Enterprise MIB objects for APs, SMs, and BHs ................................ 396 Table 60: Cyclone Enterprise MIB objects for APs and BH timing masters .................... 398 Table 61: Cyclone Enterprise MIB objects for SMs and BH timing slaves ...................... 402 Table 62: Cyclone Enterprise MIB objects for CMMmicros ............................................. 405 Table 63: PTP 400 and PTP 600 series bridge MIB objects ........................................... 408 Table 64: Event Log messages for abnormal events ...................................................... 419 Table 65: Event Log messages for normal events .......................................................... 419 Draft5forRegulatoryReview Table 66: Basic site information for technical support ..................................................... 482 Table 67: Supported telnet commands for module administration .................................. 491 Table 68: US FCC IDs and Industry Canada Certification Numbers and Covered Configurations .......................................................................................................... 494 Table 69: Disclosure Table ............................................................................................. 501 Draft5forRegulatoryReview LISTOFPROCEDURES Procedure 1: Modifying a fixed license key for a module IP address .............................. 114 Procedure 2: Analyzing the spectrum ............................................................................. 131 Procedure 3: Reducing transmitter output power ............................................................ 153 Procedure 4: Wrapping the cable .................................................................................... 175 Procedure 5: Setting up the AP for Quick Start ............................................................... 184 Procedure 6: Bypassing proxy settings to access module web pages ........................... 185 Procedure 7: Using Quick Start to configure a standalone AP for test ........................... 187 Procedure 8: Setting up the SM for test .......................................................................... 192 Procedure 9: Retrying to establish a point-to-multipoint link ........................................... 193 Procedure 10: Verifying and recording information from SMs ........................................ 201 Procedure 11: Verifying and recording information from the AP ..................................... 204 Procedure 12: Setting up the BH for Quick Start ............................................................ 205 Procedure 13: Using Quick Start to configure the BHs for test ....................................... 207 Procedure 14: Setting up the BHS for test ...................................................................... 209 Procedure 15: Verifying and recording information from the BHS .................................. 213 Procedure 16: Verifying and recording information from the BHM .................................. 216 Procedure 17: Setting up a CMMmicro ........................................................................... 218 Procedure 18: Setting CMMmicro parameters for test .................................................... 226 Procedure 19: Installing the AP ....................................................................................... 337 Procedure 20: Mounting the GPS antenna ..................................................................... 338 Procedure 21: Mounting the CMM2 ................................................................................ 340 Procedure 22: Cabling the CMM2 ................................................................................... 341 Procedure 23: Verifying CMM2 connections ................................................................... 345 Procedure 24: Mounting the CMMmicro ......................................................................... 346 Procedure 25: Installing the Power Supply for the CMMmicro ........................................ 347 Procedure 26: Cabling the CMMmicro ............................................................................ 348 Procedure 27: Verifying CMMmicro connections ............................................................ 349 Procedure 28: Installing the SM ...................................................................................... 349 Procedure 29: Verifying performance for an AP-SM link ................................................ 353 Procedure 30: Installing the BHM ................................................................................... 358 Procedure 31: Installing the BHS .................................................................................... 360 Draft5forRegulatoryReview Procedure 32: Verifying performance for a BH link ......................................................... 361 Procedure 33: Verifying system functionality .................................................................. 365 Procedure 34: Using the Spectrum Analyzer in AP feature ............................................ 371 Procedure 35: Extending network sync ........................................................................... 374 Procedure 36: Fabricating an override plug .................................................................... 380 Procedure 37: Regaining access to a module ................................................................ 381 Procedure 38: Using the override switch to regain access to CMMmicro ....................... 381 Procedure 39: Installing the Cyclone Enterprise MIB files .............................................. 394 Procedure 40: Performing a Link Capacity Test ............................................................. 439 Procedure 41: Using the Frame Calculator ..................................................................... 447 Procedure 42: Replacing the Cyclone logo on the GUI with another logo ...................... 453 Procedure 43: Changing the URL of the logo hyperlink .................................................. 455 Procedure 44: Returning a module to its original logo and hyperlink .............................. 455 Procedure 45: Denying all remote access ...................................................................... 457 Procedure 46: Reinstating remote access capability ...................................................... 457 Procedure 47: Setting up a protocol analyzer ................................................................. 462 Procedure 48: Troubleshooting loss of connectivity ........................................................ 471 Procedure 49: Troubleshooting loss of connectivity for NAT/DHCP-configured SM ....... 472 Procedure 50: Troubleshooting SM failing to register to an AP ...................................... 474 Procedure 51: Troubleshooting BHS failing to register to a BHM ................................... 475 Procedure 52: Troubleshooting loss of sync ................................................................... 476 Procedure 53: Troubleshooting loss of Ethernet connectivity ......................................... 477 Procedure 54: Troubleshooting failure to power up ........................................................ 478 Procedure 55: Troubleshooting failure of power supply to produce power ..................... 478 Procedure 56: Troubleshooting CMM2 that malfunctions ............................................... 479 Procedure 57: Troubleshooting CMM2 not passing sync ............................................... 479 Procedure 58: Troubleshooting an unsuccessful software upgrade ............................... 480 Procedure 59: Restoring the web interface to a module ................................................. 480 Draft5forRegulatoryReview Release8 GuideToThisUserGuide GGUUIIDDEETTOOTTHHIISS UUSSEERRGGUUIIDDEE Issue2,November2007 Draft5forRegulatoryReview 31 Release8 1 NEWINTHISISSUE GuideToThisUserGuide 1.1 NEWPRODUCTSANDFEATURESDESCRIBEDINISSUE2 Issue 2 adds the following products and features Release 8.2 features, including US and Canada DFS (Dynamic Frequency Selection) support for 5.4 GHz modules Cyclone OFDM in the 5.4 GHz band 1.2 NEWDESCRIPTIONSANDREVISIONSINISSUE2 This section is a placeholder where other new descriptions, as wells as clarifications and corrections, will be listed in future issues. 1.3 CYCLONEWi4PORTFOLIO The CYCLONE Wi4 portfolio of wireless broadband solutions provides a range of flexible, mix-and-match options including wi4 Fixed

Cyclone unlicensed point-to-multipoint solutions

Point-to-point solutions, including

PTP 100 series Cyclone backhauls

PTP 400 and PTP 600 series bridges

Expedience licensed point-to-multipoint solutions wi4 Indoor

Broadband over Powerline (BPL) solutions

Enterprise Wireless LAN (WLAN) solutions wi4 Mesh, including the CYCLONE MESH series of products wi4 WiMAX, including infrastructure, CPE and devices, services, and IP core 1.4 PRODUCTSCOVEREDBYTHISUSERGUIDE Products covered by this user guide include

Cyclone Access Points (APs), Subscriber Modules (SMs), and Backhauls (BHs) in the following frequency bands:

900 MHz 2.4 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.7 GHz

Cyclone OFDM APs and SMs in the 5.4 GHz band

Cluster Management Module micro (CMMmicro)

Surge Suppressor

Cyclone 900 MHz Indoor SMs Issue2,November2007 Draft5forRegulatoryReview 33 Release8 1.5 PRODUCTSNOTCOVEREDBYTHISUSERGUIDE GuideToThisUserGuide Cyclone products with their own user guides include

Cluster Management Module 4 (CMM4)

Cyclone LENS All the non-Cyclone wi4 products and solutions are covered by their own user guides and documentation. 1.6 SOFTWARECOMPATIBILITYDESCRIBEDINTHISUSERGUIDE The following sections of this document provide details and caveats about the compatibility of Cyclone products:

Designations for Hardware on Page 372

CMMmicro Software and Hardware Compatibility on Page 373

MIB File Set Compatibility on Page 373 Issue2,November2007 Draft5forRegulatoryReview 34 Release8 2 USINGTHISUSERGUIDE GuideToThisUserGuide This document should be used with Cyclone features through Software Release 8.2, Cyclone OFDM, and CMMmicro Release 2.2.1. The audience for this document includes system operators, network administrators, and equipment installers. 2.1 2.1.1 FINDINGTHEINFORMATIONYOUNEED BecomingFamiliarwithThisUserGuide This is a guide to the guide. A high-level overview of the guide and some examples of where to look provide insight into how information is arranged and labeled. The Table of Contents provides not only a sequential index of topics but also a visual glance at the organization of topics in this guide. A few minutes spent with the Table of Contents in either the paper or the electronic version of this guide can save much more time in finding information now and in the future. The List of Procedures may be especially useful in the paper version of this guide, particularly where you mark those procedures that you wish to frequently see. In contrast, the List of Figures and List of Tables are most useful for automated searches on key words in the electronic version of this guide. If a match is present, the match is the first instance that the search finds. Issue2,November2007 Draft5forRegulatoryReview 35 Release8 GuideToThisUserGuide Quick Reference The Cyclone User Guide comprises six sections, as described in Table 1. Section Guide to This User Guide

(this section) Table 1: Cyclone User Guide organization scheme Identifies Purpose products covered by this user guide. products covered by their own separate user guides. how this user guide is organized.

where to find module web pages and parameter descriptions. Overview of Cyclone Networks

what the various typefaces and admonitions indicate.

how to contact Cyclone. Provides

references to RF and networking theory. a list of sections to see if you are building only a backhaul network. overviews and comparisons of Cyclone products and how they communicate. descriptions of data handling and synchronization. a review of Cyclone optional features. resources for developing familiarity and proficiencies with Cyclone networks. Planning Guide Provides essential information for

evaluating an area for a Cyclone network. specifying the IP addresses and frequency band ranges to use for each type of link. Installation and Configuration Guide Provides systematic approaches for

avoiding hazards from RF and natural causes. testing, storing, and deploying Cyclone equipment. Operations Guide Provides guidance for expanding network coverage. improving the security of Cyclone wireless links. distributing bandwidth resources.

monitoring and changing variables through SNMP. Reference Information Provides supplemental information such as

authorizations, approvals, and notices. a bibliography of adjunctive information sources. a history of changes in Cyclone documentation. Glossary Defines terms and concepts that are used in this user guide. Issue2,November2007 Draft5forRegulatoryReview 36 Release8 GuideToThisUserGuide Examples A list of common tasks and references to information that supports each task is provided in Table 2. Table 2: Examples of where to find information in this user guide If you want to know then see what the Spectrum Analyzer in SM and BHS feature does what types of slots compose the Cyclone frame how to calculate whether an object will interfere with a signal how long a cable you can use from the GPS antenna to the CMM how to react to a WatchDog Event Log message what beam angle the passive reflector dish produces how to aim the passive reflector dish how to set Differentiated Services values so that traffic with original ToS byte formatting continues to be prioritized as it was before DSCP fields. Avoiding Self Interference on Page 152 Monitoring the RF Environment on Page 369 Understanding Bandwidth Management on Page 81 Noting Possible Obstructions in the Fresnel Zone on Page 132 Cables on Page 35 Procedure 20 on Page 338 or Procedure 24 on Page 346 Messages that Flag Abnormal Events on Page 419 and Messages that Flag Normal Events on Page 419 Specifications and Limitations on Page 70, then downward to a table for a Cyclone Part Number that includes RF. Installing a Reflector Dish on Page 356 High-priority Bandwidth on Page 86 because this topic is important to RF planning. this topic is also important to managing the network. this information is helpful for understanding Cyclone networks. this topic is important to RF planning. cables are accessory components. the advisory applies to mounting GPS antennas and CMMs. together, these two sections document all significant Event Log messages. the beam angle is a specification. aiming is associated with Backhaul Module installation. DSCP fields specify the level of priority that the device is requesting for the packet. Issue2,November2007 Draft5forRegulatoryReview 37 Release8 2.1.2 GuideToThisUserGuide SearchingThisUserGuide To search this document and the software release notes of supported releases, look in the Table of Contents for the topic and in the Adobe Reader search capability for keywords that apply.1 These searches are most effective when you begin the search from the cover page because the first matches may be in titles of sections, figures, tables, or procedures. 2.1.3 FindingParameterandFieldDefinitionsforModuleWebPages Because this user guide is sequentially arranged to support tasks, and various tasks require different settings and readings, parameter and field definitions are scattered according to the tasks that they support. The locations of these are provided in Table 3. Table 3: Locations of screen captures and associated documentation Tab or Web Page Displayed Add User tab of SM, example Alignment tab of BHS, example AP Evaluation tab of SM, example BER Results tab of SM, example Bridging Table tab of AP, example Calculated Frame Results section of Frame Calculator tab, example Configuration page of CMMmicro, example DiffServe tab of AP, example DiffServe tab of BHM, example DiffServe tab of BHS, example DiffServe tab of SM, example Ethernet tab of AP, example Event Log tab data, example Event Log tab of SM, example Frame Calculator tab, example General Status tab of AP, example General Status tab of BHM, example General Status tab of BHS, example General Status tab of SM, example General Status tab view for GUEST-level account General tab of AP, example General tab of BHM, example General tab of BHS, example 1 Reader is a registered trademark of Adobe Systems, Incorporated. Page 379 435 441 450 423 448 225 259 311 328 290 425 418 476 445 202 214 211 198 378 238 298 315 Issue2,November2007 Draft5forRegulatoryReview 38 Release8 GuideToThisUserGuide Tab or Web Page Displayed General tab of SM, example GPS Status page of CMMmicro, example IP tab of AP, example IP tab of BHM, example IP tab of BHS, example IP tab of SM with NAT disabled and local accessibility IP tab of SM with NAT disabled, example IP tab of SM with NAT enabled, example LAN IP Address tab of AP, example Link Capacity Test tab with 1522-byte packet length, example Link Capacity Test tab with 64-byte packet length, example NAT DHCP Statistics tab of SM, example NAT Port Mapping tab of SM, example NAT tab of SM with NAT disabled, example NAT tab of SM with NAT enabled, example NAT Table tab of SM, example PDA Aim tab of SM, example PDA AP Evaluation tab of SM, example PDA Information tab of SM, example PDA Quick Status tab, example PDA Spectrum Analyzer tab of SM, example PDA Spectrum Results tab of SM, example Port MIB page of CMMmicro, example Protocol Filtering tab of SM, example Quality of Service (QoS) tab of AP, example Quality of Service (QoS) tab of BHS, example Quality of Service (QoS) tab of SM, example Quick Start tab of AP, example Quick Start tab of BHM, example Radio Frequency Carrier tab of AP, example Radio tab of AP (900 MHz), example Radio tab of BHM, example Radio tab of BHS, example Radio tab of SM, example Page 263 232 241 301 318 462 269 275 189 438 439 474 293 266 271 473 336 336 335 334 334 335 233 292 251 325 282 186 206 187 243 303 320 276 Issue2,November2007 Draft5forRegulatoryReview 39 Release8 GuideToThisUserGuide Tab or Web Page Displayed Remote Subscribers tab of AP, example Remote Subscribers tab of BHM, example Review and Save Configuration tab of AP, example Scheduler tab of SM, example Security tab of AP, example Security tab of BHM, example Security tab of BHS, example Security tab of SM, example Session Status tab data from AP, example Session Status tab data, example SM Configuration tab of AP, example SM Registration Failures tab of AP, example SNMP tab of AP, example SNMP tab of BHM, example SNMP tab of BHS, example SNMP tab of SM, example Spectrum Analyzer tab of SM, example Status page of CMMmicro, example Synchronization tab of AP, example Time tab of AP, example Time tab of BHM, example Unit Settings tab of AP, example Unit Settings tab of BHM, example Unit Settings tab of BHS, example Unit Settings tab of SM, example VLAN Membership tab of AP, example VLAN Membership tab of SM, example VLAN tab of AP, example VLAN tab of SM, example Page 197 210 190 421 253 309 326 285 193 415 449 422 248 306 323 279 370 222 188 191 208 261 313 329 294 258 289 256 288 Issue2,November2007 Draft5forRegulatoryReview 40 Release8 2.2 GuideToThisUserGuide INTERPRETINGTYPEFACEANDOTHERCONVENTIONS This document employs distinctive fonts to indicate the type of information, as described in Table 4. Table 4: Font types Font Type of Information variable width bold constant width regular constant width italic constant width bold constant width bold italic Selectable option in a graphical user interface or settable parameter in the web-based interface to a Cyclone component. Literal system response in a command-line interface. Variable system response in a command-line interface. Literal user input in a command-line interface. Variable user input in a command-line interface. This document employs specific imperative terminology as follows:

Type means press the following characters.

Enter means type the following characters and then press Enter. This document also employs a set of consistently used admonitions. Each of these types of admonitions has a general purpose that underlies the specific information in the box. These purposes are indicated in Table 5. Admonition Label Table 5: Admonition types General Message NOTE:

informative content that may

defy common or cursory logic. describe a peculiarity of the Cyclone implementation. add a conditional caveat. provide a reference. explain the reason for a preceding statement or provide prerequisite background for what immediately follows. RECOMMENDATION:

suggestion for an easier, quicker, or safer action or practice. Issue2,November2007 Draft5forRegulatoryReview 41 GuideToThisUserGuide General Message IMPORTANT!

informative content that may

identify an indication that you should watch for. advise that your action can disturb something that you may not want disturbed. reiterate something that you presumably know but should always remember. CAUTION!

a notice that the risk of harm to equipment or service exists. WARNING!

a notice that the risk of harm to person exists. Release8 Admonition Label 2.3 GETTINGADDITIONALHELP Help is available for problems with supported products and features. Obtaining Technical Support on Page 481 provides the sequence of actions that you should take if these problems arise. 2.4 SENDINGFEEDBACK We welcome your feedback on Cyclone system documentation. This includes feedback on the structure, content, accuracy, or completeness of our documents, and any other comments you have. Send your comments to technical-documentation@Cyclonewireless.com. Issue2,November2007 Draft5forRegulatoryReview 42 Release8 OverviewofCycloneNetworks OOOVVVEEERRRVVVIIIEEEWWWOOOFFF CCCYYYCCCLLLOOONNNEEE NNNEEETTTWWWOOORRRKKKSSS Issue2,November2007 Draft5forRegulatoryReview 43 Release8 3 ADVANCINGFROMRESEARCHTO OverviewofCycloneNetworks IMPLEMENTATION Before you begin to research a possible Cyclone implementation, you should have both

basic knowledge of RF theory. See

Understanding RF Fundamentals on Page 117.

Engineering Your RF Communications on Page 129. network experience. See

Cyclone Link Characteristics on Page 81.

Understanding IP Fundamentals on Page 117.

Engineering Your IP Communications on Page 155. Issue2,November2007 Draft5forRegulatoryReview 45 Release8 4 REALIZINGAWIRELESSBACKHAULNETWORK OverviewofCycloneNetworks Cyclone backhaul modules (BHs) can connect Cyclone access point clusters to the point of presence or be the backbone of a Metro WiFi mesh network. In other applications, the backhaul modules can be used to provide connectivity for cell sites, in lieu of leased T1/E1 telecommunications lines. buildings in corporate or institutional campuses. remote sites, including temporary sites set up for relief efforts. These BHs are available in 10- or 20-Mbps modulation rates from the factory. The rate is distinguished as BH10 or BH20 in the Software Version field of the General Status tab

(in the Home page) of the module GUI. For these and any other backhaul networks, Table 6 provides a quick reference to information that you would need to establish and maintain the Cyclone wireless backhaul network. Table 6: Essential user guide elements for new backhaul network implementation Title Page Element Section 1.5 Section 5.1.8 Section 8.2 Figure 30 Section 12.2 Section 12.5 Section 15 Section 16.4 Section 17 Section 18.4 Section 18.5 Section 19.4 Section 19.5 Section 19.6 Section 19.9 Section 19.10 Section 19.11 Products Not Covered by This User Guide Cyclone Backhaul Module Section 5.1.11 Cluster Management Module-2 (Part 1008CK-2) Section 5.1.12 Cluster Management Module micro (Part 1070CK) Table 14 Typical range and throughput per frequency band, PTP links BH-BH Links Typical multiple-BH network layout Analyzing the RF Environment Considering Frequency Band Avoiding Hazards Configuring a Point-to-Point Link for Test Preparing Components for Deployment Configuring a BH Timing Master for the Destination Configuring a BH Timing Slave for the Destination Installing a GPS Antenna Installing a CMM2 Installing a CMMmicro Installing a Reflector Dish Installing a BH Timing Master Installing a BH Timing Slave 34 52 53 54 63 99 104 131 136 169 204 235 297 315 338 339 345 356 358 360 Issue2,November2007 Draft5forRegulatoryReview 47 Release8 OverviewofCycloneNetworks Verifying a BH Link Section 19.13 Section 21.2.2 CMMmicro Software and Hardware Compatibility Section 22.2 Section 22.3 Section 24.6 Section 24.7 Section 24.10 Section 24.11 Section 25 Section 28.3 Section 28.4 Section 31.2 Section 31.3 Section 32 Section 33 Section 34 Encrypting Cyclone Radio Transmissions Managing Module Access Objects Supported in the Cyclone 30/60-Mbps BH Objects Supported in the Cyclone 150/300-Mbps BH Traps Provided in the PTP 400 Series Bridge MIB Traps Provided in the PTP 600 Series Bridge MIB Using the Cyclone Network Updater Tool (CNUT) Typical Contents of Release Notes Typical Upgrade Process Analyzing Traffic at an AP or BH with No CMM Analyzing Traffic at an AP or BH with a CMM Troubleshooting Obtaining Technical Support Getting Warranty 361 373 375 377 409 409 410 410 413 451 452 460 460 469 481 487 Issue2,November2007 Draft5forRegulatoryReview 48 Release8 5 EXPLORINGTHESCOPEOFSOLUTIONS OverviewofCycloneNetworks Cyclone wireless broadband applications include:

local area network (LAN) extensions Internet subscriber service high-bandwidth point-to-point connections

multicast video (for instruction or training, for example)

TDM over Ethernet (for legacy voice and data) private branch exchange (PBX) extensions point-to-multipoint data backhaul redundant network backup video surveillance voice over IP (VoIP) 5.1 COMPONENTS Cyclone networks use some or all of the following components. For the components that provide a graphical user interface (GUI), access to the GUI is through a web browser. In Release 8 and later, cascading style sheets (CSS) configure the GUI. Thus an operator is able to customize the GUI by editing these style sheets. 5.1.1 CycloneAccessPointModuleandCycloneOFDMAccessPointModule The Cyclone Access Point (AP) module provides broadband connectivity in a 60 sector. The Cyclone OFDM AP provides broadband connectivity in a 90 sector. Either supports up to 200 subscribers and 4,096 MAC addresses, which may be directly-connected PCs, IP appliances, gateways, Subscriber Modules (SMs), and the AP, except that no limit applies behind subscriber network address translation (NAT) gateways. The AP is configurable through a web interface. A Cyclone AP can only communicate with a Canopy SM, not also an Advantage SM or a Cyclone Lite SM. A Cyclone OFDM AP can only communicate with a Cyclone OFDM SM. 5.1.2 AdvantageAccessPointModule The Cyclone Advantage AP distributes services as broadly as the Cyclone AP. However, the Advantage AP provides greater throughput and less latency. Each tab in the GUI for Cyclone Advantage modules displays the distinctive branding shown in Figure 1. Figure 1: Cyclone Advantage Platform GUI logo The Advantage AP communicates with all Canopy SMs in its frequency band range:

Canopy SMs, Advantage SMs, and Cyclone Lite SMs. Issue2,November2007 Draft5forRegulatoryReview 49 Release8 5.1.3 OverviewofCycloneNetworks CycloneAccessPointClusterandCycloneOFDMAccessPointCluster An AP cluster covers as much as 360. The Cyclone FSK AP cluster consists of two to six APs that provide broadband connectivity to 1,200 or fewer subscribers. Each AP transmits and receives in a 60 sector. The Cyclone OFDM AP cluster consists of two to four APs that provide broadband connectivity to 800 or fewer subscribers. Each AP transmits and receives in a 90 sector. The variety of available APs, Advantage APs, and OFDM APs in frequency band range, power adjustability, and antenna configuration is shown under Acquiring a Cyclone Demonstration Kit, beginning on Page 117. An AP cluster is pictured in Figure 2. An OFDM AP, showing the antenna in front and the radio attached to it, is pictured in Figure 3. Figure 2: Pole-mounted AP cluster Figure 3: OFDM AP - Antenna and Radio 5.1.4 CanopySubscriberModule The Subscriber Module (SM) is a customer premises equipment (CPE) device that provides broadband services through communication with an AP. The SM is configurable through a web interface. The variety of available SMs, Advantage SMs, and OFDM SMs in frequency band range, power adjustability, and antenna configuration is shown under Acquiring a Cyclone Demonstration Kit, beginning on Page 117. Figure 4: Structure-mounted SM Issue2,November2007 Draft5forRegulatoryReview 50 OverviewofCycloneNetworks Release8 A Canopy SM can communicate with either a Cyclone AP or an Advantage AP. A Cyclone OFDM SM can communicate with only a Cyclone OFDM AP. An SM mounted directly to a structure is pictured in Figure 4. An OFDM SM is shown in Figure 5 in both front and side views. Figure 5: OFDM SM, front and side views 5.1.5 5.1.6 AdvantageSubscriberModule The Cyclone Advantage SM provides the same configurability and services as the Canopy SM. However, in a link with an Advantage AP, the Advantage SM provides uncapped sustained 2X throughput. See 2X Operation on Page 90. An Advantage SM can only communicate with an Advantage AP. CycloneLiteSubscriberModule Cyclone Lite SMs cost less and provide less throughput than regular Canopy SMs. They support the same radio frequencies, interference tolerance, and product reliability. They give operators the additional option to serve cost-sensitive customers who want standard services (web browsing, email, VoIP, and downloads), but do not require the higher throughput that is available with a regular Canopy SM. Cyclone Lite SMs support an aggregate(uplink plus downlink) throughput of 512 kbps. Through purchased floating licenses that Prizm manages, they are upgradeable to 1, 2, 4, or 7 Mbps aggregate throughput. A Cyclone Lite SM can communicate with only a Cyclone Advantage AP. A comparison of the Cyclone Lite SM to the Canopy SM and Advantage SM is provided in Table 25 on Page 100. Issue2,November2007 Draft5forRegulatoryReview 51 Release8 5.1.7 OverviewofCycloneNetworks 900MHzAPandSM Cyclone 900 MHz AP and SM modules operate at a 3.3 Mbps carrier rate (compared to 10 Mbps for other Cyclone frequency bands). Figure 6: Examples of flat panel antennas with 900-MHz modules These 900-MHz modules run the same software and provide the same parameters, network features, and connections as all other Cyclone APs and SMs. The physics of longer-wavelength 900 MHz, the power allowed by regulatory authorities, and the low required level of Cyclone Carrier-to-Interference (C/I) ratio combine to support line of sight (LOS) range of up to 40 miles (over 64 km) increased non-line of sight (NLOS) range, depending on RF considerations such as foliage, topography, and obstructions. When collocated with a Canopy SM of another frequency band range, the 900-MHz AP may serve, without a tower or BH, as a remote AP (see Deploying a Remote AP on Page 148). 900-MHz AP/SM links are logical choices for extending radio networks where you wish to

fully used in the other frequency band ranges. add subscriber-handling capacity to a tower that is either

not available to any other frequency band range. reach sparsely populated areas. penetrate foliage. add a remote AP behind an SM that operates in another frequency band range. Issue2,November2007 Draft5forRegulatoryReview 52 Release8 5.1.8 Cyclone OverviewofCycloneNetworks 5.1.9 BackhaulModule A pair of Backhaul Modules (BHs) provide point-to-point connectivity as either

a standalone link a link through a cluster management module to an AP cluster. You must configure a BH as either a timing master (BHM) or timing slave (BHS). The BHM provides synchronization signal (sync) to the BHS. A BH mounted to a passive reflector dish is pictured in Figure 7. Carrier applications for these modules include reaching remote AP clusters, interconnecting campus buildings or remote branch offices, extending private branch exchange (PBX) circuits, backhauling cell sites, and extending central office T1s/E1s. These BHs are supported by this user guide. See Realizing a Wireless Backhaul Network on Page 47. Figure 7: Dish-mounted 10- or 20-Mbps BH 5.1.10 RadioAdjustablePowerCapabilities Cyclone offers adjustable power radios in all frequency bands.See Adjusting Transmitter Output Power on Page 330 to ensure that your radios do not exceed the maximum permitted EIRP. 5.1.11 ClusterManagementModule2(Part1008CK2) The Cluster Management Module-2 (CMM2) provides power, GPS timing from an antenna that is included, and networking connections for an AP cluster. The CMM2 can also connect to a BH, in which case the CMM2 is the central point of connectivity for the entire site. The CMM2 can connect as many as eight collocated modulesAPs, BHMs, BHSsand an Ethernet feed. The CMM2 requires two cables for each connected module:

One provides Ethernet communications and power. This cable terminates in an RJ-45 connector.

The other provides synchronization (sync), GPS status, and time and date in a serial interface. This cable terminates in an RJ-11 connector. A CMM2 is pictured in Figure 8. A CMM2 as part of a mounted Cyclone system is pictured in Figure 9. Issue2,November2007 Draft5forRegulatoryReview 53 Release8 OverviewofCycloneNetworks Figure 8: CMM2 enclosure Figure 9: CMM2 pole-mounted 5.1.12 ClusterManagementModulemicro(Part1070CK) The Cluster Management Module micro (CMMmicro) provides power, GPS timing, and networking connections for an AP cluster. Unlike the CMM2, the CMMmicro is configurable through a web interface. The CMMmicro contains an 8-port managed switch that supports Power over Ethernet

(PoE) on each port and connects any combination of APs, BHMs, BHSs, or Ethernet feed. Cyclone PoE differs from 803.3af PoE, and the two should not be intermixed. The CMMmicro can auto-negotiate speed to match inputs that are either 100Base-TX or 10Base-T, and either full duplex or half duplex, where the connected device is set to auto-negotiate. Alternatively, these parameters are settable. A CMMmicro requires only one cable, terminating in an RJ-45 connector, for each connected module to distribute

Ethernet signaling.

power to as many as 8 collocated modulesAPs, BHMs, or BHSs. Through a browser interface to the managed switch, ports can be powered or not. sync to APs and BHMs. The CMMmicro receives 1-pulse per second timing information from Global Positioning System (GPS) satellites through an antenna

(included) and passes the timing pulse embedded in the 24-V power to the connected modules. GPS status information is available at the CMMmicro, however

CMMmicro provides time and date information to BHMs and APs if both the CMMmicro is operating on CMMmicro Release 2.1 or later and the AP/BHM is operating on Cyclone System Release 4.2 or later. See Time Tab of the AP on Page 191.

CMMmicro does not provide time and date information to BHMs and APs if either the CMMmicro is operating on a release earlier than CMMmicro Release 2.1 or the AP/BHM is operating on a release earlier than Cyclone System Release 4.2. Issue2,November2007 Draft5forRegulatoryReview 54 Release8 5.1.13 GPSAntenna OverviewofCycloneNetworks The Last Mile Gear GPS antenna provides either

timing pulses to the CMMmicro. timing pulses and positioning information to the CMM2. The GPS antenna is pictured in Figure 10. 5.1.14 SurgeSuppressor(Part600SS) The 600SS Surge Suppressor provides a path to ground (Protective Earth ) that reduces the risk to persons, buildings, and inside equipment from over-currents and over-voltages associated with lightning strikes. A 600SS is pictured in Figure 11. Figure 10: Last Mile Gear GPS antenna Figure 11: 600SS surge suppressor 5.1.15 AccessoryComponents In addition to the above modules, the following accessories are available. Power Supplies The various power supplies available for Cyclone modules are listed in Table 7. Table 7: Power supply descriptions For Use With CMMmicro Cyclone radio2 Part Number ACPS81WA ACPS81W-02A ACPS110-03A1 ACPSSW-09A3 ACPSSW-10A3 ACPSSW-11A3 ACPSSW-12A3 Voltage (AC) 100 to 240 100 to 240 120 90 to 240 90 to 240 90 to 240 90 to 240 Cycles per Second (Hz) 50 to 60 50 to 60 50 to 60 50 to 60 50 to 60 50 to 60 50 to 60 Includes US IEC line cord no IEC line cord US plug US, Euro, and UK adaptors Argentina adaptor Australia adaptor China adaptor Issue2,November2007 Draft5forRegulatoryReview 55 Release8 OverviewofCycloneNetworks For Use With Part Number Voltage (AC) Cycles per Second (Hz) Includes NOTES:

1. Pictured in Figure 12. 2. Single transceiver. 3. Pictured in Figure 13. Figure 13: ACPSSW-09A power supply Figure 12: ACPS110-03A power supply Passive Reflector Dish Assembly A 27RD Passive Reflector Dish on both ends of a BH link extends the distance range of the link and provides a narrower beam width, which can reduce both received and transmitted interference. A 27RD on an SM extends the distance range in some bands (notably 5.7-

GHz and 2.4-GHz) and can reduce both received and transmitted interference in all bands. An SMMThe module support tube provides the proper offset focus angle. See Figure 14. For 5.x-GHz radios, the reflector gain is 18dB Figure 14: 27RD with mounted module Issue2,November2007 Draft5forRegulatoryReview 56 OverviewofCycloneNetworks Release8 and the 3 dB beam width is 6 in both azimuth and elevation. For 2.4-GHz radios, the reflector gain is 11dB and the 3 dB beam width is 17 in both azimuth and elevation. Module Support Brackets The SMMB1 support bracket facilitates mounting the SM to various surfaces of a structure and has slots through which chimney straps can be inserted. An SMMB1 is pictured in Figure 15. The SMMB2 is a heavy duty mounting bracket that comes with the 900-MHz integrated SM or AP, and with the 27D passive reflector. It is also available separately for use with 900-MHz connectorized SMs and APs, other connectorized modules, and OFDM SMs. The BH1209 is a pole-mount bracket kit for Cyclone backhaul modules. Figure 15: SMMB1 SM support bracket Cables Cyclone modules that are currently or recently sold can auto-sense whether the Ethernet cable is wired as straight-through or crossover. Some modules that were sold earlier cannot. The MAC address, visible on the module, distinguishes whether the module can. All CMMmicros can auto-sense the cable scheme. Where a non auto-sensing module is deployed

a straight-through cable must be used for connection to a network interface card

(NIC). a crossover cable must be used for connection to a hub, switch, or router. Cyclone-recommended Ethernet and sync cables can be ordered in lengths up to 328 ft

(100 m) from Best-Tronics Manufacturing, Inc. at http://www.best-tronics.com/Last Mile Gear.htm. These cables are listed in Table 8 and Table 9. Table 8: Recommended outdoor UTP Category 5E cables Best-Tronics Part #

BT-0562 BT-0562S BT-0565 BT-0565S Description RJ-45 TO RJ-45; straight-through Ethernet cable RJ-45 TO RJ-45; shielded straight-through Ethernet cable RJ-45 TO RJ-45; crossover Ethernet cable RJ-45 TO RJ-45; shielded crossover Ethernet cable Issue2,November2007 Draft5forRegulatoryReview 57 Release8 OverviewofCycloneNetworks BT-0563 BT-0563S RJ-11 TO RJ-11; sync cable RJ-11 TO RJ-11; shielded sync cable Shielded cable is strongly recommended for all AP cluster and BH installations. NOTE:

Table 9: Recommended indoor UTP Category 5E cables Best-Tronics Part #

Description BT-0596 BT-0595 RJ-45 TO RJ-45; straight-through Ethernet cable RJ-45 TO RJ-45; crossover Ethernet cable Approved Ethernet cables can also be ordered as bulk cable:

CA-0287

CA-0287S (shielded) Cyclone-approved antenna cables can be ordered in lengths up to 100 ft (30.4 m), as listed in Table 10. Table 10: Recommended antenna cables Best-Tronics Part #

Description BT-0564 BT-0716 N TO N GPS antenna cable for CMM2 BNC TO N GPS antenna cable for CMMmicro Category 5 Cable Tester For purchase within the U.S.A., the CTCAT5-01 Cable Tester is available. Override Plug An override plug (sometimes called a default plug) is available to provide access to a module whose password and/or IP address have been forgotten. This plug allows the AP, SM, or BH to be accessed using IP address 169.254.1.1 and no password. During the override session, you can assign any new IP address and set either or both user passwords (display-only and/or full access) as well as make other parameter changes. This plug is available from Best-Tronics Manufacturing, Inc. at http://www.best-tronics.com/Last Mile Gear.htm as Part BT-0583 (RJ-11 Default Plug). Issue2,November2007 Draft5forRegulatoryReview 58 Release8 OverviewofCycloneNetworks Alternatively if you wish, you can fabricate an override plug. For instructions, see Procedure 36 on Page 380 and the pinout in Figure 140 on Page 380. Figure 16: ACATHS-01 alignment headset Alignment Headset The ACATHS-01 Alignment Headset facilitates the operation of precisely aiming an SM toward an AP (or a BHS toward a BHM). This device produces infinitely variable

pitch, higher when the received signal is stronger. volume, louder when jitter is less. An ACATHS-01 is pictured in Figure 16. Pinouts for an alternative listening device are provided under Alignment ToneTechnical Details on Page 184. Module Housing The HSG-01 Cyclone Plastic Housing is available for replacement of a damaged housing on a module that is otherwise functional. The HSG-01 is pictured in Figure 17. The HSG-01 and all module housings of this design provide clearances for cable ties on the Ethernet and sync cables. RECOMMENDATION:

Use 0.14 (40-lb tensile strength) cable ties to secure the Ethernet and sync cables to the cable guides on the module housing. For the Ethernet cable tie, the Ethernet cable groove is molded lower at the top edge. For the sync cable tie, removal of a breakaway plug provides clearance for the sync cable, and removal of two breakaway side plates provides clearance for the sync cable tie. Figure 17: HSG-01 Housing Issue2,November2007 Draft5forRegulatoryReview 59 Release8 5.2 OverviewofCycloneNetworks FREQUENCYBANDRANGES In the 2.4-, 5.2-, 5.1-, 5.4-, and 5.7-GHz frequency band ranges, Cyclone APs, SMs, and BHs are available. Additionally, in the 900-MHz frequency band range, Cyclone APs and SMs are available. National restrictions may apply. See Regulatory and Legal Notices on Page 493. To avoid self-interference, a Cyclone network typically uses two or more of these ranges. For example, where properly arranged, all AP clusters and their respective SMs can use the 2.4-GHz range where the BH links use the 5.7-GHz range. In this scenario, subscriber links can span as far as 5 miles (8 km) with no reflector dishes, and the BH links can span as far as 35 miles (56 km) with reflector dishes on both ends. Within this example network, wherever the 2.4-GHz module is susceptible to interference from other sources, AP clusters and their linked SMs may use the 5.2-GHz range to span as far as 2 miles (3.2 km) with no reflector dishes. The network in this example takes advantage of frequency band range-specific characteristics of Cyclone modules as follows:

The 900-MHz modules cover a larger area, albeit with lower throughput, than modules of the other frequency bands. The 900-MHz modules can be used to

penetrate foliage

establish links that span greater distances

add subscribers

add overall throughput where modules of other frequency bands cannot be used (such as where interference would result or space on a tower is limited).

The 2.4-GHz frequency band range supports AP/SM links of greater than 2-mile spans (with no reflectors).

The 5.7-GHz frequency band range supports BH links that span as far as 35 miles. 5.3 CYCLONEPRODUCTCOMPARISONS 5.3.1 CycloneProductApplications The product applications per frequency band range are is summarized in Table 11. Table 11: Product applications per frequency band range Product Access Point Module Subscriber Module Subscriber Module with Reflector1 Backhaul Module Backhaul Module with Reflector1 900 MHz Frequency Band Range 2.4 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.7 GHz 5.4 GHz OFDM Issue2,November2007 Draft5forRegulatoryReview 60 Release8 OverviewofCycloneNetworks Product CMM2 CMMmicro Power supply Surge suppressor 900 MHz Frequency Band Range 2.4 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.7 GHz 5.4 GHz OFDM NOTES:

1. National or regional regulations may limit EIRP to the same as without a reflector, and therefore require Transmit Output Power to be reduced. In these cases

the reflector used with an SM reduces beamwidth to reduce interference, but does not increase the range of the link. the reflector on both ends of a BH link reduces beamwidth to reduce interference and also increases the range of the link.

5.3.2 LinkPerformanceandEncryptionComparisons Encryption options are summarized in Table 12. Typical Line-of-Site (LOS) range and aggregate useful throughput for Cyclone PTMP links are summarized in Table 13. Typical Line-of-Site (LOS) range and aggregate useful throughput for Cyclone PTP links are summarized in Table 14. Table 12: Products with encryption options available per frequency band, PTMP links Frequency Band 900 MHz 2.4 GHz @100 mW

(ETSI) 2.4 GHz @ 1W 5.1 GHz 5.2 GHz 5.4 GHz 5.7 GHz 5.4 GHz OFDM Products available with the following encryption options DES or none AES or none Issue2,November2007 Draft5forRegulatoryReview 61 Release8 OverviewofCycloneNetworks Table 13: Typical range and throughput per frequency band, PTMP links Advantage AP Cyclone AP Frequency Band 2.4 GHz ETSI 2.4 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.7 GHz Range no SM Reflector mi (km) 0.3 (0.5) 0.6 (1) 2.5 (4) 5 (8) 1 (1.6) 2 (3.2) 1 (1.6) 2 (3.2) 1 (1.6) 2 (3.2) 1 (1.6) 2 (3.2) with SM Reflector mi (km) 0.3 (0.5) 1 0.6 (1) 1 7.5 (12) 15 (24) na na na2 na2 1 (1.6) 1 2 (3.2) 1 5 (8) 10 (16) 900 MHz4 40 (64) 5.4 GHz OFDM 1X 2X 3X na Aggregate Throughput Mbps Round-

trip Latency msec Range no SM Reflector mi (km) with SM Reflector mi (km) Aggregate Throughput3 Mbps Round-

trip Latency msec 14 7 14 7 14 7 14 7 14 7 14 7 4 6 6 6 6 6 6 6 6 6 6 6 6 15 0.6 (1) 0.6 (1) 1 5 (8) 15 (24) 2 (3.2) na 2 (3.2) na2 2 (3.2) 2 (3.2)1 2 (3.2) 10 (16) 5 (8) 2.5 (4) 1.25 (2) 7 7 7 7 7 7 7 14 21 20 20 20 20 20 20 tbd tbd tbd NOTES:

2. In Europe, 2.4-GHz ETSI and 5.4-GHz SMs can have a reflector added to focus the antenna pattern and reduce interference, but transmit output power must be reduced to maintain the same EIRP as without a reflector, so the throughput and range specs for PTMP links remain the same. In the USA and Canada, the use of a reflector with a full power radio in the 5.2-GHz frequency band is not allowed. 3. 4. These values assume a hardware series P9 AP running hardware scheduler. When running software scheduler on a series P7, P8, or P9 AP, aggregate throughput drops to 6.2 Mbps, and only 4 Mbps is available to any one SM. (Series P7 and P8 APs can only run software scheduler.) 5. All 900-MHz APs are Advantage APs. GENERALNOTES:

Range is affected by RF conditions, terrain, obstacles, buildings, and vegetation. An Advantage AP in other than 900 MHz has an aggregate (sum of uplink plus downlink) throughput or capacity of 14 Mbps, if RF conditions, range, and SM hardware version permit. An Advantage SM in other than 900 MHz has an aggregate sustained throughput of 14 Mbps if RF conditions and range permit. A regular SM can burst to 14 Mbps if RF conditions and range permit, then run at 7 Mbps sustained throughput. An OFDM SM has an aggregate throughput or capacity of XX Mbps, if RF conditions and range permit.d Issue2,November2007 Draft5forRegulatoryReview 62 Release8 OverviewofCycloneNetworks Table 14: Typical range and throughput per frequency band, PTP links Frequency Band Modulation Rate (Mbps) Throughput No Reflectors Both Reflectors 2.4 GHz @100 mW

(ETSI) 2.4 GHz @ 1W 5.1 GHz 5.2 GHz 5.2 GHz ER 5.4 GHz 5.7 GHz 10 20 10 20 10 20 10 20 10 20 10 20 10 20 7.5 Mbps to 2 km 14 Mbps to 1 km 7.5 Mbps to 5 mi (8 km) 14 Mbps to 3 mi (5 km) 7.5 Mbps to 2 mi (3.2 km) 14 Mbps to 2 mi (3.2 km) 7.5 Mbps to 2 mi (3.2 km) 7.5 Mbps to 2 mi (3.2 km) 14 Mbps to 1 mi (1.6 km) 7.5 Mbps to 2 mi (3.2 km) 14 Mbps to 1 mi (1.6 km) 7.5 Mbps to 16 km 14 Mbps to 8 km 7.5 Mbps to 35 mi (56 km) 14 Mbps to 35 mi (56 km) 7.5 Mbps to 10 mi (16 km) 14 Mbps to 5 mi (8 km) 7.5 Mbps to 10 mi (16 km)1 14 Mbps to 5 mi (8 km)1 7.5 Mbps to 35 mi (56 km) 14 Mbps to 35 mi (56 km) NOTES:

1. These ranges are with power reduced to within 1 W (30 dBm) EIRP. 2. Use the Link Estimator tool to estimate throughput for a given link. 5.3.3 ClusterManagementProductComparison Cyclone offers a choice between two products for cluster management: CMM2 and CMMmicro. Your choice should be based on the installation environment and your requirements. The similarities and differences between these two products are summarized in Table 15. Table 15: Cluster management product similarities and differences Characteristic Approximate size Approximate weight Cabling Cyclone network interconnection CMM2 17 H x 13 W x 6.5 D

(43 cm H x 33 cm W x 7 cm D) 25 lb ( 11.3 kg) one Ethernet/power cable per radio. one sync cable per radio. CMMmicro 12 H x 10 W x 3 D

(30 cm H x 25 cm W x 8 cm D) 8 lb (3.5 kg) one Ethernet/power/sync cable per radio. 8 Ethernet ports 8 Ethernet ports Issue2,November2007 Draft5forRegulatoryReview 63 Release8 Characteristic Data throughput Ethernet operating speed standard Additional Ethernet ports Power supply SNMP management capability Sync (to prevent self-interference) OverviewofCycloneNetworks CMM2 CMMmicro auto-negotiates to full or half duplex auto-negotiates to 10Base-T or 100Base-TX one for data feed one for local access

(notebook computer) integrated 24-V DC to power APs, BHs, and GPS receiver auto-negotiates to full or half duplex auto-negotiates to 10Base-T or 100Base-TX none external 24-V DC to power APs, BHs, and GPS receiver none provided carried by the additional serial cable to each AP and BHM Time & Date carried by the additional serial cable to each AP and BHM Weatherized enclosure and power supply Web interface none embedded in power-over-Ethernet cable provided by NTP (Network Time Protocol). CMMmicro can be an NTP server. only the enclosure (not the power supply) web pages for status, configuration, GPS status, and other purposes NOTE:

Auto-negotiation of data throughput and Ethernet operating speed depend on the connected device being set to auto-negotiate as well. 5.4 ANTENNASFORCONNECTIONTO900MHzMODULES Like the 2.4-, 5.2-, 5.4-, and 5.7-GHz module, the 900-MHz connectorized module has the same housing. a covered Ethernet port. a utility port for alignment headset, sync cable to CMM2, or override plug. The 900-MHz AP or SM is available either as a connectorized unit with a 16-inch (approximately 40-cm) cable with a male N-type connector for connection to the antenna. with an integrated horizontally-polarized antenna in a different form factor. 5.4.1 CertifiedConnectorizedFlatPanelAntennas Last Mile Gear has certified four connectorized flat panel antenna options. Last Mile Gear resells one of these, whose attributes include gain10 dBi dimensions8.8 x 8.1 x 1.6 inches (22.4 x 20.6 x 4.06 cm)

weight1.2 lbs (0.54 kg) Issue2,November2007 Draft5forRegulatoryReview 64 Release8 OverviewofCycloneNetworks

polarizationvertical or horizontal cable12-inch (30.5 cm) connectorfemale N-type beamwidthapproximately 60 vertical and 60 horizontal at 3 dBm Last Mile Gear has certified three other antennas, which are available through Cyclone resellers. The attributes of one of these other certified antennas include gain10 dBi dimensions12 x12 x 1 inches (30.5 x 30.5 x 2.5 cm)

weight3.3 lbs (1.5 kg)

polarizationvertical or horizontal connectorfemale N-type beamwidthapproximately 60 vertical and 60 horizontal at 3 dBm Examples of these antennas are pictured in Figure 6 on Page 52. 5.4.2 ThirdpartyCertifiedConnectorizedFlatPanelAntenna A third party may certify additional antennas for use with the Cyclone connectorized 900-MHz module. 5.5 ADJUNCTIVESOFTWAREPRODUCTS The capabilities of available applications and tools are summarized for comparison in Table 16. In this table CNUT represents Cyclone Network Updater Tool, Release 1.1 or later, and BAM represents Bandwidth and Authentication Manager, Release 2.0 or later. Table 16: Cyclone applications and tools Application or Tool Capability m z i r P T U N C authenticates SMs controls authentication in APs manages Committed Information Rate (CIR) has dependency on another application3 automatically discovers elements exports network information with hierarchy supports user-defined folder-based operations senses FPGA version on an element upgrades FPGA version on an element enables/disables hardware scheduling M A B Issue2,November2007 Draft5forRegulatoryReview 65 Release8 OverviewofCycloneNetworks Capability Application or Tool m z i r P T U N C M A B manages the high-priority channel imports network information with hierarchy interface to a higher-level network management system (NMS) interface to an operations support system (OSS) manages Maximum Information Rate (MIR) automatically works from root (highest) level element selection can be individual or multiple element selection can be criteria based element selection can be user-defined branch senses software release on an element upgrades software release on an element manages VLAN parameters provides access to element web interface 5.6 BANDWIDTHANDAUTHENTICATIONMANAGER Cyclone Bandwidth and Authentication Manager (BAM) software allows you to use

a primary server to distribute bandwidth resources per subscriber, require SMs to authenticate per AP, and deny service to unauthorized SMs. a secondary server to redundantly store identical SM bandwidth and authentication data and become governing if the primary server goes out of service. an optional tertiary server to do the same if both the primary and secondary servers go out of service. In BAM Release 2.1, subscriber administration for an SM or batch of SMs is performed as follows:

Insert the ESNs. Specify MIR and Security attributes. Specify CIR attributes. Specify whether BAM should send its stored CIR attributes. Specify VLAN attributes. Specify whether BAM should send its stored VLAN attributes. Issue2,November2007 Draft5forRegulatoryReview 66 Release8 OverviewofCycloneNetworks Specify VLAN IDs to associate with the SM(s). This product is supported by the dedicated document Cyclone Bandwidth and Authentication Manager Release 2.1 User Guide and associated release notes. The upgrade path from BAM Release 2.1 is Prizm Release 2.0. See Last Mile Gear Cyclone Prizm User Guide, Issue 3, and Last Mile Gear Cyclone Prizm Release 2.0 Release Notes. 5.7 Prizm The product name PrizmEMS is changed to Prizm in Release 2.0 and later, to reflect that the product capabilities are expanded beyond those of the element management system

(EMS). Throughout this user guide, the name change applies to text for Release 2.0 and for multiple releases that include 2.0. It does not apply to text that is for a previous release. Case by case, software elements such as the GUI in the client application and XML files on the server may retain the PrizmEMS syntax. 5.7.1 NetworkDefinitionandElementDiscovery Prizm allows the user to partition the entire Cyclone network into criteria-based subsets that can be independently managed. To assist in this task of defining networks, Prizm auto discovers Cyclone network elements that are in user-defined IP address ranges

SM-to-AP relationships with APs in the user-defined range

BHS-to-BHM relationships with BHMs in the user-defined range.

PLV Modem-to-PLV Bridge relationships with PLV Bridges in the user-defined range. For a Cyclone AP, SM, BHM, BHS, PLV Bridge, PLV Modem, or CMMmicro, Prizm

auto discovers the element to the extent possible. includes the element in the network tree. shows general information. shows Cyclone information. supports Cyclone-specific operations. For a generic element, Prizm

auto discovers the element as only a generic network element. includes the element in the network tree. shows general information. shows events and alerts. charts port activity. For passive elements (such as CMM2 or a non-manageable switch or hub), Prizm allows you to enter into the network tree a folder/group with name, asset/owner information, and descriptive information. Issue2,November2007 Draft5forRegulatoryReview 67 Release8 Supported element types include OverviewofCycloneNetworks Cyclone Access Point Module Cyclone Backhaul Master Module Cyclone Backhaul Slave Module Cyclone PrizmEMS Canopy Subscriber Module Cluster Management Module micro Cluster Management Module-4 Cluster Management Module-4 Switch Generic Group Generic SNMP Device Generic SNMP Device (08 Port) Generic SNMP Device (16 Port) Generic SNMP Device (24 Port) Generic SNMP Device (26 Port) High-Speed Backhaul Master Module 150/300 Mbps High-Speed Backhaul Master Module 30/60 Mbps High-Speed Backhaul Slave Module 150/300 Mbps High-Speed Backhaul Slave Module 30/60 Mbps PLV Bridge Unit PLV Modem Unit Ultra Light Access Point Ultra Light Outdoor Subscriber Unit 5.7.2 MonitoringandFaultManagement Prizm receives the traps that Cyclone elements send and generates an alert for each of these. Prizm also allows the user to establish sets of criteria that would generate other alerts and trigger email notifications. Optionally, the user can specify a trap template. In this case, Prizm receives traps for non-Cyclone elements in the network. For any individual element that the user selects, Prizm offers text and graphed displays of element configuration parameters and performance statistics from an interval that the user specifies. 5.7.3 ElementManagement Prizm allows the user to perform any of the following operations on any specified element or group of elements:

Manage large amounts of SNMP MIB data.

module passwords.

other communications setup parameters.

site information: Site Name, Site Location, and Site Contact parameters. IP addresses.

Reset the element. 5.7.4 BAMSubsysteminPrizm Prizm Release 2.0 and later integrates Cyclone Bandwidth and Authentication Manager

(BAM) functionality and supports simple migration of a pre-existing BAM data into the Prizm database. These releases also support the maintenance of authentication and bandwidth data on a RADIUS server, to the same extent that BAM Release 2.1 (the final release of BAM) did. Issue2,November2007 Draft5forRegulatoryReview 68 Release8 OverviewofCycloneNetworks Either of the following modes is available for the Prizm server, subject to licensing:

BAM-only functionality, which manages only

authentication, bandwidth service plans, and VLAN profiles of SMs.

authentication of Powerline LV modems.

Full Prizm functionality, which manages attributes for all elements and authentication of SMs and Powerline LV modems. One difference between a service plan (or VLAN profile) and a configuration template that has the identical set of attributes is that the former is a long-term association whereas the latter is a one-time push to the element. When a service plan or VLAN profile is modified, the change is automatically applied to all elements that have the association. Another difference is that a configuration template cannot overwrite any values that a service plan or VLAN profile has set in an element. 5.7.5 NorthboundInterface In Release 1.1 and later, Prizm provides three interfaces to higher-level systems:

a Simple Network Management Protocol (SNMP) agent for integration with a network management system (NMS). a Simple Object Access Protocol (SOAP) XML-based application programming interface (API) for web services that supports integration with an operations support systems (OSS) such as a customer relationship management (CRM), billing, or provisioning system. console automation that allows such higher-level systems to launch and appropriately display the Prizm management console in GUI that is custom developed, using the PrizmEMS Software Development Kit (SDK), which Cyclone provides for this purpose. Together these interfaces constitute the Northbound Interface feature. Prizm server administrator tasks and GUI developer information are provided in the PrizmEMS Software Development Kit (SDK). This SDK also describes the how to define new element types and customize the Details views. All other features of the Prizm product are supported by the dedicated document Last Mile Gear Cyclone Prizm User Guide and associated release notes. 5.8 LICENSEMANAGEMENT Under the original licensing regime for Cyclone networks, licenses were permanently tied to the Media Access Control (MAC) address of the equipment that was licensed or that used the licensed feature. Thus, they were not transferable. Under server-based license management, for some functionalities, Cyclone offers licenses that

float upon demand within the network. are tied to only the osted (MAC address) of the license management server for which they were ordered. Issue2,November2007 Draft5forRegulatoryReview 69 Release8 OverviewofCycloneNetworks In Release 4.2.3 and later, server-based license management adds flexibility and makes available licenses that previously would have been held by de-commissioned equipment. License management technology from Macrovision, based on a FLEXnet Publisher license management model, provides the platform for Cyclone server-based licensing. Cyclone capabilities that are authorized by licenses on this platform are FLEXenabled products. In this platform, the license management server checks and then either assigns or declines to assign a license in real time. See the Cyclone Networks License Manager User Guide. The total number of floating license keys that you need for any feature is the highest number that you will ever want to have simultaneously in use. The proper placement of these keys and the number and placement of fixed Cyclone licenses are listed in Table 17. Table 17: Correct placement of license keys In This Release License Key Must Be in Directory LM 1.0 BAM 2.0 BAM 2.1 PrizmEMS 1.0 PrizmEMS 1.1 License Manager Server BAM Server, AP Auth Server

(APAS), Cap 2 BAM Server, AP Auth Server

(APAS), Cap 2 PrizmEMS Server, Element Pack PrizmEMS Server, Element Pack C:\Program Files\Last Mile Gear\Cyclone\FLEXnet\license_files

/usr/local/Cyclone/FLEXnet/license_files C:\Program Files\Last Mile Gear\Cyclone\FLEXnet\license_files

/usr/local/Cyclone/FLEXnet/license_files

/usr/local/Cyclone/include C:\Program Files\Last Mile Gear\Cyclone\FLEXnet\license_files

/usr/local/Cyclone/FLEXnet/license_files

/usr/local/Cyclone/FLEXnet/license_files C:\Program Files\Last Mile Gear\Cyclone\FLEXnet\license_files

/usr/local/Cyclone/FLEXnet/license_files C:\Program Files\Last Mile Gear\Cyclone\FLEXnet\license_files

/usr/local/Cyclone/Prizm/license_files C:\Program Files\Last Mile Gear\Cyclone\FLEXnet\license_files

/usr/local/Cyclone/FLEXnet/license_files On This Server Device LM Server LM Server1 BAM Server2 LM Server1 BAM Server2 LM Server3 PrizmEMS Server4 LM Server3 If This Platform Windows Enterprise Linux Windows Enterprise Linux Enterprise Linux Windows Enterprise Linux Enterprise Linux Windows Enterprise Linux Windows Enterprise Linux Windows Enterprise Linux Issue2,November2007 Draft5forRegulatoryReview 70 Release8 In This Release Prizm 2.0 and 2.1 for full mgmt Prizm 2.0 and 2.1 for BAM-only or redundant BAM License Key PrizmEMS Server, Element Pack BAM Server, AP Auth Server

(APAS), Cap 2 Cyclone Lite BAM Server, AP Auth Server

(APAS), Cap 2 Cyclone Lite OverviewofCycloneNetworks Must Be in Directory C:\Program Files\Last Mile Gear\Cyclone\FLEXnet\license_files On This Server Device If This Platform Windows

/usr/local/Cyclone/FLEXnet/license_files LM server5 Enterprise Linux C:\Program Files\Last Mile Gear\Cyclone\FLEXnet\license_files Windows

/usr/local/Cyclone/FLEXnet/license_files LM server1 Enterprise Linux NOTES:

1. One key required per each deployed BAM server. 2. Copied here so that BAM can find License Manager. No additional charge for using this copy. 3. One key required per each deployed PrizmEMS server. 4. Copied here so that PrizmEMS can find License Manager. No additional charge for using this copy. 5. One BAMServer key and one PrizmEMSServer key required per each full management Prizm server. 5.9 SPECIFICATIONSANDLIMITATIONS 5.9.1 Radios Cyclone radio specifications are provided at http://Last Mile Gear.Cyclonewireless.com/products/specshome.php. Issue2,November2007 Draft5forRegulatoryReview 71 Release8 5.9.2 OverviewofCycloneNetworks ClusterManagementProducts Table 18: CMM2 specifications and limitations Specification or Limitation Cyclone System Range Max length from Cluster Management Module to any radio Max length from Cluster Management Module to GPS antenna 328 cable feet (100 meters) 100 cable feet (30.5 meters) Dimensions Weight 17.00 H x 12.88 W x 6.50 D

(43.18 cm H x 32.72 cm W x 16.51 cm D) 25.0 lbs. (11.3 kg) Operation Temperature

-40F to +131F (-40C to +55C) Overall Meets CE IP44 according to EN60529:2000 AC Input Voltage and Frequency AC Input Power 100 V 240 V~, 0.7 A 0.35 A, settable to either 230 V or 115 V nominal input. 50 Hz 60 Hz Note: Applying 230 V to a unit that is set to 115 V may damage the unit. Nominal 66 watts, max 92 watts with 8 modules connected to the CMM at max cable length. 24-V DC Input Voltage 18 to 32 V DC, measured at CMM 24-V DC Input Power 24-V DC Usage Nominal 60 watts. Maximum 84 watts with 8 modules connected to the CMM at maximum cable length. 9A inrush upon start-up. If using a typical 24V +/-5% power supply, ensure that CMM is within 400 cable feet (120 m) of the power supply. Use minimum 12 AWG (4 mm2) copper wire. 12-V DC Input Voltage 11.5 to 32 VDC, measured at CMM 12-V DC Usage Ethernet, GPS Sync, and GPS Coax Cables If using a 12V power source (typically an automobile battery in a test or emergency situation), use 12 AWG (4 mm2) wire between the power supply and the CMM, ensure that the CMM is within 10 cable feet (3 m) of the power supply, and ensure the modules are within 20 cable feet (6 m) of the CMM. The use of cables that conform to the operational temperature of the product as well as being UV light protected is mandatory. Issue2,November2007 Draft5forRegulatoryReview 72 Release8 OverviewofCycloneNetworks Table 19: CMMmicro specifications and limitations Specification or Limitation Cyclone System Range Enclosure Size CMMmicro Weight (without DC power supply) Max length from Cluster Management Module to any radio Max length from Cluster Management Module to GPS antenna Approximately 12 H x 10 W x 3 D

(Approximately 30 cm H x 25 cm W x 7.5 cm D) Approximately 8 lb

(Approximately 3.5 k) 328 cable feet (100 meters) 100 cable feet (30.5 meters) Operating Temperature

-40F to +131F (-40C to +55C) Provided DC Power Converter Input Voltage Provided DC Power Converter Input Frequency 100 240 V~

50 60 Hz CMMmicro Power Input Voltage 21.5 26.5 V DC CMMmicro Power Current 3.36 A @ 24 V DC (3.75 3.0 A over voltage range) Ethernet, GPS sync, and GPS coax cables The use of cables that conform to the operational temperature of the product as well as having UV light protection is mandatory. Cables can be ordered from Best-Tronics Manufacturing, Inc. at http://www.best-tronics.com/Last Mile Gear.htm. 5.9.3 300SSand600SSSurgeSuppressors Cyclone Surge Suppressor specifications are provided at http://Last Mile Gear.Cyclonewireless.com/products/specshome.php. Issue2,November2007 Draft5forRegulatoryReview 73 Release8 6 DIFFERENTIATINGAMONGCOMPONENTS OverviewofCycloneNetworks 6.1 INTERPRETINGMODEL(PART)NUMBER The part number of a module typically represents

radio frequency band range. link distance range. the model number, which may indicate

whether the module is Cyclone Advantage.

the module type. the factory-set encryption standard.

whether the reflector dish is included.

whether adjustable power in the module is preset to low.

the antenna scheme of the module. the modulation capability. Radio Frequency Band Range The leading digits usually indicate the frequency band range in which the module can operate. For example, if the part number is 5700BH, then the frequency band range of the module is 5.7 GHz. 5 7 0 0 B H An exception to this general rule is that the leading digits in the part number of 5.1-GHz modules are 52. These modules are differentiated from 5.2-GHz modules by the leading four digits (5202 for 5.1 GHz, 5200 for 5.2 GHz). You cannot change the frequency band range of the module. Link Distance Range or Cyclone Advantage The third digit in the part number may indicate whether the module is an extended range, Cyclone Advantage, or Cyclone model. 1 indicates extended range. For example, if the part number is 5210BH, then the module is an extended range module. If the part number is 5200BH, then the module is not an extended range model. 5 2 0 0 B H 6 in the third position (5760SM, for example) indicates Cyclone Lite. 5 in the third position

(5250AP, for example) indicates that the module is Cyclone Advantage. 0 in the third position (5200AP, for example) indicates that the module is Cyclone. However, part numbering for 900-MHz APs and SMs differs from this general rule. All APs and SMs in this frequency band range are Cyclone Advantage, but none of their part numbers use 5 in the third position. Issue2,November2007 Draft5forRegulatoryReview 75 Release8 OverviewofCycloneNetworks You cannot change the link distance range of the module. However, you can license a Canopy SM to uncap its aggregate throughput (a capability of the Advantage SM). Encryption Standard or Frequency Band Range The fourth digit in the part number usually indicates the encryption standard that was preset at the factory. 1 indicates the Advanced Encryption Standard (AES). 0 indicates the Data Encryption Standard (DES) standard. For example, if the part number is 5201BH, then transmissions from the module are encrypted according to AES. If the part number is 5200BH, then transmissions from the module are encrypted according to DES. 5 7 0 0 B H An exception to this general rule is that the fourth digit in the part number of 5.1-GHz modules is 2. These modules are differentiated from 5.2-GHz modules by the leading four digits (5202 for 5.1 GHz, 5200 for 5.2 GHz). You cannot change the encryption basis (from DES to AES, for example), but you can enable or disable the encryption. Module Type The next two alpha characters indicate the module type. For example, CK indicates that the module is a Cluster Management Module. 1 0 0 8 C K The module type cannot be changed. Reflector Added In specifications tables and price lists, the trailing characters RF or RF20 indicate that the associated information applies to the module being

mounted to the 27RD Passive Reflector Dish, in the case of specifications.

ordered with the 27RD Passive Reflector Dish, in the case of price lists. 2 4 0 0 B H R F 2 0 However, this designation is not shown on either label of the module, and a module ordered with the dish can be deployed without the dish. Issue2,November2007 Draft5forRegulatoryReview 76 Release8 OverviewofCycloneNetworks Antenna Scheme In specifications tables and price lists, the trailing character C indicates that the module is connectorized for an external antenna. 9 0 0 0 S M C An F in this position indicates that the module has an internal antenna with a band-pass filter (for example, 9000APF). You cannot transform a module from connectorized to internal antenna or from internal antenna to connectorized, but you may have flexibility in what external antenna you deploy with it. Adjustable Power Preset to High or Low A trailing WL can indicate that the module had adjustable power that is preset to low. 2 4 0 0 A P W L However, the 5700SMC and 5700APC are connectorized, but also have adjustable power preset to low. No special designation is made for adjustable power that is set to high (no trailing letters are used; for example, 5252AP). You can reset power to higher in a module with adjustable power that is preset to low, but you are constrained by applicable regulations in your region and or nation. Modulation Capability A trailing 20 indicates that the module is capable of being set to either

20-Mbps modulation (aggregate throughput of 14 Mbps) 10-Mbps modulation (aggregate throughput of 7 Mbps). 2 4 0 0 B H R F 2 0 The absence of a trailing 20 indicates that the module is capable of only 10-Mbps modulation. Issue2,November2007 Draft5forRegulatoryReview 77 Release8 6.2 SORTEDMODELNUMBERS OverviewofCycloneNetworks Model numbers of Cyclone modules are listed in Table 20. Not all models are available in all markets. Please check with your Cyclone distributor or reseller for availability. Table 20: Cyclone model numbers Integrated Antenna Connectorized for Antenna Cyclone Advantage Cyclone DES AES AES 5751AP 5751SM DES 5750AP 5750APHZ 5750SM 5750SMHZ DES 5700APC 5700SMC 5700BHC 5700BHC20 AES 5701APC 5701SMC 5701BHC 5701BHC20 Advantage DES AES 5750APC 5750SMC 5751APC 5751SMC 5450AP 5450SM 5451AP 5451SM 5400APC 5400SMC 5400BHC 5400BHC20 5401APC 5401SMC 5401BHC 5401BHC20 5450APC 5450SMC 5451APC 5451SMC 5252AP 5252SM 5201AP 5201SM 5201BH 5211BH20 5211BHRF 5211BHRF20 5251AP 5251SM 5250AP 5250APHZ 5250SM 5250SMHZ 5701AP 5701SM 5701BH 5701BH20 5701BHRF 5701BHRF20 5401AP 5401SM 5401BH 5401BH20 5401BHRF 5401BHRF20 e g n a R 5.7 GHz 5.4 GHz 5.1 GHz 5.2 GHz 5700AP 5700APHZ 5700SM 5760SM 5700SMMHZ 5700BH 5700BH20 5700BHRF 5700BHRF20 5400AP 5400SM 5460SM 5400BH 5400BH20 5400BHRF 5400BHRF20 5202AP 5202SM 5202BH 5212BH20 5212BHRF20 5200AP 5200APHZ 5200SM 5260SM 5200SMHZ 5200BH 5210BHRF 5210BHRF20 Issue2,November2007 Draft5forRegulatoryReview 78 Release8 OverviewofCycloneNetworks Integrated Antenna Connectorized for Antenna Cyclone Advantage Cyclone Advantage e g n a R 2.4 GHz 900 MHz DES AES 2401AP 2401APWL 2401SM 2401SMWL 2401BH 2401BH20 2401BHRF 2401BHRF20 2401BHWL 2401BHWL20 2401BHWLRF 2401BHWLRF20 2400AP 2400APWL 2400SM 2400SMWL 2460SM 2400SMLP 2400BH 2400BH20 2400BHRF 2400BHRF20 2400BHWL 2400BHWL20 2400BHWLRF 2400BHWLRF20 5.4 GHz OFDM 5440AP 5440APC 5440SM DES 2450AP 2450APWL 2450SM 2450SMWL AES 2451AP 2451APWL 2451SM 2451SMWL DES AES DES AES 9000APC 9000SMC 9001APC 9001SMC 9000AP 9000APF 9000SM 9000SMF 9001AP 9001APF 9001SM 9001SMF 6.3 INTERPRETINGELECTRONICSERIALNUMBER(ESN) Cyclone module labels contain a product serial number that could be significant in your dealings with Last Mile Gear or your supply chain. This is the electronic serial number

(ESN), also known as the Media Access Control (MAC) address, of the module. This hexadecimal number identifies the module in

communications between modules. the data that modules store about each other (for example, in the Registered To field). the data that the BAM software applies to manage authentication and bandwidth.

Prizm auto discovery of SMs through the AP (or BHS through the BHM).

software upgrades performed by the Cyclone Network Updater Tool (CNUT). information that CNUT passes to external tools. 6.4 FINDINGTHEMODEL(PART)NUMBERANDESN The labels and locations of Cyclone module model (part) numbers and ESNs are shown in Table 21. Table 21: Labels and locations of model (part) numbers and ESNs Numeric Label and Location Issue2,November2007 Draft5forRegulatoryReview 79 Release8 OverviewofCycloneNetworks String Older Modules Newer Modules Model # outside PN outside Model number ESN/MAC address S/N inside ESN outside Issue2,November2007 Draft5forRegulatoryReview 80 Release8 7 CYCLONELINKCHARACTERISTICS OverviewofCycloneNetworks 7.1 UNDERSTANDINGBANDWIDTHMANAGEMENT 7.1.1 DownlinkFrameContents The AP broadcasts downlink frames that contain control information, allocating slots in succeeding or future uplink frames to SMs that have requested service. The downlink frame also contains a beacon frame, control information, and data that specific SMs have requested. Each SM

examines the downlink frame to distinguish whether data is addressed to that SM. retrieves data addressed to that SM. directs such data to the appropriate end user. 7.1.2 UplinkFrameContents Uplink frames contain control information from each SM that request service on succeeding uplink frames. SMs insert data into the uplink frames in an amount that the AP has established. Optionally, you can configure the AP to change the source MAC address in every packet it receives from its SMs to the MAC address of the SM that bridged the packet, before forwarding the packet toward the public network. If you do, then not more than 10 IP devices at any time are valid to send data to the AP from behind the SM. the AP populates the Translation Table tab of its Statistics web page, displaying the MAC address and IP address of all the valid connected devices. each entry in the Translation Table is associated with the number of minutes that have elapsed since the last packet transfer between the connected device and the SM. if 10 are connected, and another attempts to connect

and no Translation Table entry is older than 255 minutes, the attempt is ignored.

and an entry is older than 255 minutes, the oldest entry is removed and the attempt is successful. the Send Untranslated ARP parameter in the General tab of the Configuration page can be

disabled, so that the AP will overwrite the MAC address in Address Resolution Protocol (ARP) packets before forwarding them.

enabled, so that the AP will forward ARP packets regardless of whether it has overwritten the MAC address. This is the Translation Bridging feature, which you can enable in the General tab of the Configuration web page in the AP. When this feature is disabled, the setting of the Send Untranslated ARP parameter has no effect, because all packets are forwarded untranslated (with the source MAC address intact). Issue2,November2007 Draft5forRegulatoryReview 81 Release8 OverviewofCycloneNetworks See Address Resolution Protocol on Page 162. 7.1.3 DefaultFrameStructures With a 64-byte slot size, the default Cyclone frame in hardware scheduling consists of

variable numbers of uplink and downlink data slots, subject to the following factors:

Maximum range decreases the number of available slots to 32.

Background bit error rate (BER) mode decreases the number of available data slots by one (and bandwidth by 200 kbps).

Every two control slots that are allocated decrease the number of available data slots by one. timing and distribution for the SMs ratio of uplink to downlink allocation 0 to 10 control slots, subject to operator setting 0 to 9 downlink acknowledgement slots, dynamically assigned 0 to 9 uplink acknowledgement slots, dynamically assigned 1 uplink schedule slot 1 beacon slot, which identifies the

ESN of the AP

color code

protocol (point-to-point or point-to-multipoint)

number of registered SMs

control slot information air delay, subject to the value of the Max Range parameter in the AP frame number Control Slots The Radio tab of the Configuration web page in the AP displays the total of control slots

(default 3, maximum 7 in the 900-MHz frequency band range2 and 16 in all others). These control slots are contention slots. If too many SMs contend for these slots, then the number of control slots may be increased. Frame Scheduling When an SM boots, the following sequence occurs:

1. The SM finds this beacon slot from an AP. 2. The SM synchronizes with the AP. 3. If BAM is configured on the AP and the AP is licensed for authentication, then a. the AP sends a Registration Request message to Prizm for authentication. following a successful challenge, Prizm returns an Authentication Grant b. message to the AP. 2 In the 900-MHz frequency band range, the frame size is 16,667 bits. In all others, the frame size is 25,000 bits. The smaller frame does not provide enough space to allocate more than 7 control slots. Issue2,November2007 Draft5forRegulatoryReview 82 Release8 OverviewofCycloneNetworks the AP sends a Registration Grant to the SM. c. If BAM is not configured on the AP or the AP is not licensed for authentication, then the AP simply returns the Registration Grant to the SM. This Registration Grant includes the distance between the AP and SM. The SM uses the distance to distinguish when to transmit data in the uplink frame. The AP performs advance scheduling of up to 1024 frames that each SM will be permitted to use in the uplink frame. 7.1.4 MediaAccessControlandAPCapacity Regardless of whether the maximum number of SMs (200) all request service at the same time, the reservation Media Access Control (MAC) system allows the AP to give a reservation slot to each SM that requests service. Regardless of the distance between any SM and the AP, the reservation MAC system ensures that all SM data slots are free of contention. For this reason

all SMs are equally able to compete for uplink and downlink bandwidth. the capacity of the AP is not degraded by distance from the SMs. 7.1.5 CycloneSlotUsage The frame illustrated in Figure 18 shows both packet fragments (yellow) and unused slot space (red) typical of uplink traffic. Packet sizes smaller than 64 bytes cause unused slot spaces. Figure 18: Uplink data slot usage The following statistics apply to Cyclone frame slot usage:

Slot capacity is 64 bytes.

The optimum Ethernet packet size is 1518 bytes.

The maximum downlink throughput for one AP to one SM is 1800 packets per second (pps).

The maximum uplink throughput for one AP to one SM is 300 pps.

The maximum backhaul throughput is 3000 pps. 7.1.6 DataTransferCapacity Cyclone modules use Time Division Duplex (TDD) on a common frequency to divide frames for uplink (orange) and downlink (green) usage, as shown in Figure 19. Issue2,November2007 Draft5forRegulatoryReview 83 Release8 OverviewofCycloneNetworks Figure 19: TDD dividing Cyclone frames 7.1.7 MaximumInformationRate(MIR)Parameters Cyclone point-to-multipoint links use the following four MIR parameters for bandwidth management:

Sustained Uplink Data Rate (kbps)

Uplink Burst Allocation (kb)

Sustained Downlink Data Rate (kbps)

Downlink Burst Allocation (kb) You can independently set each of these parameters per AP or per SM. Token Bucket Algorithm The Cyclone software uses a token bucket algorithm that

stores credits (tokens) for the SM to spend on bandwidth for reception or transmission. drains tokens during reception or transmission. refills with tokens at the sustained rate set by the network operator. For each token, the SM can send toward the network in the uplink (or the AP can send toward the SM in the downlink) an equivalent number of kilobits. Two buckets determine the permitted throughput: one in the SM for uplink and one in the AP for downlink. The applicable set of Uplink Burst Allocation and Downlink Burst Allocation parameters determine the number of tokens that can fill each bucket. When the SM transmits (or the AP transmits) a packet, the equivalent number of tokens is removed from the uplink (or downlink) bucket. Except when full, the bucket is continuously being refilled with tokens at rates that the applicable set of Sustained Uplink Data Rate and Sustained Downlink Data Rate parameters specify. The bucket often drains at a rate that is much faster than the sustained data rate but can refill at only the sustained data rate. Thus, the effects of the allocation and rate parameters on packet delay are as follows:

the burst allocation affects how many kilobits are processed before packet delay is imposed. the sustained data rate affects the packet delay that is imposed. Issue2,November2007 Draft5forRegulatoryReview 84 Release8 OverviewofCycloneNetworks Which set of these MIR parameters are applicable depends on the interactions of other parameter values. These interactions are described under Setting the Configuration Source on Page 295. Also, where the Configuration Source parameter setting in the AP specifies that BAM values should be used, they are used only if Prizm is configured to send the values that it stores for the MIR parameters. MIR Data Entry Checking Uplink and downlink MIR is enforced as shown in Figure 20. NOTE:

In these figures, entry refers to the setting in the data rate parameter, not the burst allocation parameter. uplink cap enforced =

downlink cap enforced =

uplink entry x aggregate cap for the SM uplink entry + downlink entry downlink entry x aggregate cap for the SM uplink entry + downlink entry Figure 20: Uplink and downlink rate caps adjusted to apply aggregate cap For example, in the Canopy SM, if you set the Sustained Uplink Data Rate parameter to 2,000 kbps and the Sustained Downlink Data Rate parameter to 10,000 kbps, then the uplink and downlink MIR that will be enforced for the SM can be calculated as shown in Figure 21. uplink cap enforced =

downlink cap enforced =

2,000 kbps x 7,000 kbps 2,000 kbps + 10,000 kbps

= 1,167 kbps 10,000 kbps x 7,000 kbps 2,000 kbps + 10,000 kbps

= 5,833 kbps Figure 21: Uplink and downlink rate cap adjustment example Issue2,November2007 Draft5forRegulatoryReview 85 Release8 OverviewofCycloneNetworks In this example case, the derived 1,167-kbps uplink and 5,833-kbps downlink MIR sum to the fixed 7,000-kbps aggregate cap of the Canopy SM. 7.1.8 CommittedInformationRate The Committed Information Rate (CIR) capability feature enables the service provider to guarantee to any subscriber that bandwidth will never decrease to below a specified minimum, unless CIR is oversubscribed. Bandwidth can be, and typically will be, higher than the minimum, but this guarantee helps the WISP to attract and retain subscribers. In BAM Release 2.1 and in Prizm Release 2.0, CIR configuration is supported as follows:

The GUI allows you to view and change CIR configuration parameters per SM.

When an SM successfully registers and authenticates, if BAM or Prizm has CIR configuration data for the SM, then messages make the CIR configuration available to the SM, depending on the Configuration Source setting. (See Setting the Configuration Source on Page 295.)

The operator can disable the CIR feature in the SM without deleting the CIR configuration data. 7.1.9 BandwidthfromtheSMPerspective In the Canopy SM, normal web browsing, e-mail, small file transfers, and short streaming video are rarely rate limited with practical bandwidth management (QoS) settings. When the SM processes large downloads such as software upgrades and long streaming video or a series of medium-size downloads, the bucket rapidly drains, the burst limit is reached, and some packets are delayed. The subscriber experience is more affected in cases where the traffic is more latency sensitive. Example download times for various arbitrary tiers of service are shown in Table 55 on Page 388 and Table 56 on Page 389. 7.1.10 InteractionofBurstAllocationandSustainedDataRateSettings If the Burst Allocation is set to 1200 kb and the Sustained Data Rate is set to 128 kbps, a data burst of 1000 kb is transmitted at full speed because the Burst Allocation is set high enough. After the burst, the bucket experiences a significant refill at the Sustained Data Rate. This configuration uses the advantage of the settable Burst Allocation. If both the Burst Allocation and the Sustained Data Rate are set to 128 kb, a burst is limited to the Burst Allocation value. This configuration does not take advantage of the settable Burst Allocation. If the Burst Allocation is set to 128 kb and the Sustained Data Rate is set to 256 kbps, the actual rate will be the burst allocation (but in kbps). As above, this configuration does not take advantage of the settable Burst Allocation. 7.1.11 HighpriorityBandwidth To support low-latency traffic such as VoIP (Voice over IP) or video, the Cyclone system implements a high-priority channel. This channel does not affect the inherent latencies in the Cyclone system but allows high-priority traffic to be immediately served. The high-

priority pipe separates low-latency traffic from traffic that is latency tolerant, such as standard web traffic and file downloads. Issue2,November2007 Draft5forRegulatoryReview 86 Release8 A Cyclone module prioritizes traffic by OverviewofCycloneNetworks reading the Low Latency bit (Bit 3) in the IPv4 Type of Service (ToS) byte in a received packet. reading the 802.1p field of the 802.1Q header in a received packet, where VLAN is enabled on the module. comparing the 6-bit Differentiated Services Code Point (DSCP) field in the ToS byte of a received packet to a corresponding value in the DiffServe tab of the Configuration page of the module. Low Latency Bit Bit 3 is set by a device outside the Cyclone system. In the uplink frame, the SM monitors Bit 3. If this bit is set, then

the SM prioritizes this traffic in its high-priority queue according to AP configuration settings for the high-priority channel. the system sends the packet on the high-priority channel and services this channel before any normal traffic. 802.1P Field See Priority on VLANs (802.1p) on Page 166. DSCP Field Like Bit 3 of the original IPv4 ToS byte, the DSCP field (Bits 0 through 5) in the redefined ToS byte is set by a device outside the Cyclone system. A packets contains no flag that indicates whether the encoding is for the Low Latency bit or the DSCP field. For this reason, you must ensure that all elements in your trusted domain, including routers and endpoints, set and read the ToS byte with the same scheme. Cyclone modules monitor ToS bytes with DSCP fields, but with the following differences:

The 6-bit length of the field allows it to specify one of 64 service differentiations. These correlate to 64 individual (CodePoint) parameters in the DiffServe tab of the Configuration page. Per RFC 2474, 3 of these 64 are preset and cannot be changed. (See http://www.faqs.org/rfcs/rfc1902.html.) For any or all of the remaining 61 CodePoint parameters, you can specify a value of

0 through 3 for low-priority handling.

4 through 7 for high-priority handling. RECOMMENDATION:

Ensure that your Differentiated Services domain boundary nodes mark any entering packet, as needed, so that it specifies the appropriate Code Point for that traffic and domain. This prevents theft of service level. Issue2,November2007 Draft5forRegulatoryReview 87 Release8 OverviewofCycloneNetworks An example of the DiffServe tab in the Configuration page and parameter descriptions are provided under DiffServe Tab of the AP on Page 259. This tab and its rules are identical from module type to module type in Cyclone. However, any of the 61 configurable Code Points can be set to a different value from module to module, thus defining unique per-hop behavior for some traffic. This tab in the AP and BHM sets the priorities for the various packets in the downstream

(sent from the public network). This tab in the SM and BHS sets the priorities for the various packets in the upstream (sent to the public network). Typically in the Cyclone network, some SMs attach to older devices that use the ToS byte as originally formatted, and others to newer devices that use the DSCP field. The default values in the DiffServe tab allow your modules to prioritize traffic from the older devices roughly the same as they traditionally have. However, these default values may result in more high-priority traffic as DSCP fields from the newer devices are read and handled. So, after making any changes in the DiffServe tab, carefully monitor the high-

priority channel for high packet rates in SMs that you have identified as those to initially set and watch. across your Cyclone network when you have broadly implemented Code Point values, such as via SNMP. The Cyclone frame structure is illustrated in Figure 22. Beacon Beacon Con-

Con-

trol trol Ack Ack Data Data Data Data AP Transmit (Downlink) AP Transmit (Downlink) AP Receive (Uplink) AP Receive (Uplink) Ack Con-

Con-

Ack trol trol Figure 22: Cyclone frame structure 7.1.12 HardwareScheduling Cyclone Release 8 supports only hardware scheduling. Hardware scheduling always sends high-priority traffic first, even to the exclusion of other traffic. IMPORTANT!

The number of channels available to the AP is reduced by the number of SMs configured for the high-priority channel. With this feature enabled on all SMs, an AP can support 100 SMs (instead of 200). Cyclone Release 8 requires APs, BHs, and AES SMs to be Series P9 or later hardware.3 The characteristics of hardware scheduling in a Cyclone sector are summarized in Table 22. 3 See Designations for Hardware in Radios on Page 164. Issue2,November2007 Draft5forRegulatoryReview 88 OverviewofCycloneNetworks Table 22: Characteristics of hardware scheduling Category Factor Treatment Throughput Latency Aggregate throughput, less additional overhead ACK slots in downlink used for data except when request for uplink is present Number of frames required for the scheduling process Round-trip latency1 AP broadcast the download schedule Allocation for uplink high-

priority traffic on amount of high-priority traffic High-priority Channel Allocation for downlink high-

priority traffic on amount of high-priority traffic Order of transmission 14 Mbps Yes 1 6 ms No Dynamic, based on amount of high-priority traffic Dynamic, based on amount of high-priority traffic 1. CIR high-priority 2. CIR low-priority 3. Other high-priority 4. Other low-priority Transmit Frame Spreading CIR Support for Transmit Frame Spreading feature In Release 7.0 and later Capability In all releases NOTES:

1. For 2.4- and 5.n-GHz modules. CAUTION!

Power requirements for modules that run hardware scheduling affect the recommended maximums for power cord length feeding the CMMmicro. See Table 50 on Page 347. However, the requirements do not affect the maximums for the CMM2. Release8 Packets that have a priority of 4 to 7 in either the DSCP or a VLAN 802.1p tag are automatically sent on the high-priority channel, but only where the high-priority channel is enabled. Issue2,November2007 Draft5forRegulatoryReview 89 Release8 7.1.13 OverviewofCycloneNetworks 2XOperation A General tab option in both Advantage SMs and hardware series P9 and greater Canopy SMs provides double the aggregate throughput for SMs that are nearer than half of the maximum typical range from the AP. The requirements of this feature are as follows:

The AP must be an Advantage AP. The SM must be near the AP, roughly half the range of 1X. The SM must be of the P9 hardware series or later and enabled for hardware scheduling. See Designations for Hardware on Page 372. The 2X Rate parameter in the SM must be set to enabled. This is the default setting. The amount of noise and multipath must be low enough to allow the receiver in the 6 dB less sensitive (2X) state to maintain a high carrier-to-interference (C/I) ratio. The flexibility of this feature is as follows:

At the time of registration, signaling is at the 1X rate. However, if the above requirements are all met, then the SM switches to 2X. Thereafter, whenever RF conditions are unfavorable for 2X operation, the SM switches to 1X. When favorable RF conditions allow, the SM switches back to 2X, if user data is present at that time. Similarly, whenever no user data is present, the SM switches to 1X. When user data flow resumes, the SM switches back to 2X, if RF conditions allow. Both links for the SM (uplink and downlink) are independent for this feature.

(One can be operating at 2X operation while the other is operating at 1X.) Other SMs in the sector can be communicating with the AP at the other modulation rate. Although subscribers with Canopy SMs realize higher bursts, and subscribers with Advantage SMs realize both higher burst and higher sustained throughput, the network operator realizes higher sector throughput capacity in the AP. The effect of 2X operation on aggregate throughput for the SM is indicated in Table 23. Issue2,November2007 Draft5forRegulatoryReview 90 Release8 OverviewofCycloneNetworks Table 23: Effect of 2X operation on throughput for the SM Type of SM 900 MHz3 Any other frequency band range Typical Aggregate Rates1 Sustained2 4 Mbps Burst2 4 Mbps 14 Mbps 14 Mbps Advantage SM Regular SM

(at least P9 Hardware Series) Any frequency band range except 900 MHz 7 Mbps 14 Mbps NOTES:

1. Subject to competition among all SMs in the sector. 2. Can be less if limited by the value of Downlink Data set in the Radio tab of the Configuration page in the AP. 3. All 900-MHz modules are Advantage. Competition for Bandwidth When multiple SMs vie for bandwidth, the AP divides its bandwidth among them, considering their effective CIR and MIR values. However, 2X operation uses bandwidth twice as efficiently as 1X, even where MIR values apply. This is because, in 2X operation, the modules transmit their data in 4-level frequency shift keying (FSK), not 2-level as they would in 1X operation. This moves twice the data per slot. Thus, for the sum of all bandwidth that 2X-eligible customers use, the bandwidth available to the remaining customers increases by half of that sum when these eligible customers are transmitting and receiving in 2X operation. Engineering for 2X Operation The following priorities should guide your implementation of 2X operation:

In the near half of the distance range of the AP

enable their SMs first for 2X operation. identify the customers who use the most bandwidth. When you have deployable Cyclone P7 and P8 SMs, do not deploy Cyclone Advantage SMs or Cyclone P9 SMs beyond half the distance range of the AP. At this distance, steady and reliable 2X operation typically is not achievable. Deploy the Cyclone P7 and P8 SMs here. Wherever practical, implement 25 MHz of channel separation for 2X operation. Checking Link Efficiencies in 2X Operation Unlike in 1X operation, efficiencies below 90% on the Link Capacity Test tab in the Tools web page of the SM may be acceptable for stable operation. An efficiency of 60% in 2X operation is equivalent to an efficiency of 120% in 1X. If you read efficiency between 60%

and 90%, check the status of 2X operation (as described below) to confirm that the link is operating at 2X. Since received signal strength typically varies over time, you should perform link tests at various times of day and on various days of the week. Efficiencies should consistently be 60% or greater for 2X operation. You may be able to achieve better efficiencies by re-

aiming the SM, mounting it elsewhere, or adding a reflector dish. Issue2,November2007 Draft5forRegulatoryReview 91 Release8 OverviewofCycloneNetworks Checking the Status of 2X Operation The Session Status tab in the Home page of the AP provides operation status information about each SM-to-AP link. Under the MAC address of each SM, the data in this tab includes a line such as the following:

RATE : VC 19 Rate 2X/2X VC 255 Rate 2X/1X Interpret this information is as follows:

VC means virtual channel. If one VC is displayed, the high-priority channel is disabled. If two are displayed, the high-priority channel is enabled and is using the higher number VC (255 in the above example). 2X/2X indicates that the SM-to-AP link is in 2X operation. 2X/1X indicates that the SM is capable of 2X operation but the SM-to-AP link is in 1X operation. This can be for either of the following reasons:

The SM has not sent data on the channel yet.

The received signal does not support 2X operation. 1X/1X indicates that the SM is capable of only 1X operation. This can be for either of the following reasons:

The SM does not support 2X operation (SM is of the hardware series P7 or P8).

The 2X Rate parameter is disabled in the General tab of the Configuration page in the SM or the AP. CAUTION!

2X operation requires approximately 3 to 5% more power than 1X operation. This additional power affects the recommended maximum for power cord length feeding the CMMmicro. See Table 50 on Page 347. However, 2X operation does not affect the maximums for the CMM2. Disabling 2X Operation Disabling 2X operation for an SM can be helpful for alignment, troubleshooting, or preventing frequent automatic switches between 2X and 1X, where RF conditions are only marginally favorable to 2X. The ability to disable 2X for an SM is inherent since the 2X Operation feature was introduced. Disabling 2X operation for a sector can be helpful for identifying a baseline for 1X-to-2X comparison, broader troubleshooting activities, or forcing all SMs to 1X rather than disabling 2X in each SM. Release 8 provides a 2X Rate parameter in the General tab of the Configuration page in the AP:

If you click Disable, then Save Changes and Reboot, 2X operation is disabled for the sector, regardless of the 2X Rate setting in each SM. If you later click Enable, then Save Changes and Reboot, 2X operation is enabled in the sector for SMs with 2X Rate enabled on their Configuration>General page. SMs with 2X Rate disabled on their Configuration>General page (or P7 or P8 SMs that dont support 2X Rate) will only operate at 1X. Issue2,November2007 Draft5forRegulatoryReview 92 Release8 7.1.14 OverviewofCycloneNetworks 3XOperation(CycloneOFDMmodulesonly) Cyclone OFDM modules offer an additional modulation scheme that provides 3X operation in addition to 1X and 2X operation. In clear space, 3X operation is possible over half the range of 2X (which means it is possible over the range of 1X). However, in NLOS installations (typical for Cyclone OFDM), multipathing may be the predominant RF issue, not free-space attenuation, so the relationship between 1X, 2X, and 3X range may differ from clear space situations. 3X operation is configured on a Cyclone OFDM modules Configuration => General page using the Dynamic Rate Adapt pop-up under Mac Control Parameters. 7.2 UNDERSTANDINGSYNCHRONIZATION The system usesTime Division Duplexing (TDD) - one channel alternately transmits and receives - rather than using one channel for transmitting and a second channel for receiving. To accomplish TDD, the AP must provide sync to its SMs it must keep them in sync. Furthermore, collocated APs must be synced together - an unsynchronized AP that transmits during the receive cycle of a collocated AP can prevent that second AP from being able to decode the signals from its SMs. In addition, across a geographical area, APs that can hear each other benefit from using a common sync to further reduce self-interference within the network. 7.2.1 GPSSynchronization The Navigation Satellite Timing and Ranging (NAVSTAR) Global Positioning System

(GPS) uses 24 satellites to relay information for precise derivation of position and time. The Cyclone Cluster Management Module (CMM) contains a Last Mile Gear Oncore GPS Receiver. The CMM is a critical element in the operation of the Cyclone system. At one AP cluster site or throughout an entire wireless system, the CMM provides a GPS timing pulse to each module, synchronizing the network transmission cycles. The Oncore GPS Receiver tracks eight or more satellites. The CMM uses the signal from at least four of these satellites to generate a one-second interval clock that has a rise time of 100 nsec. This clock directly synchronizes APs and BHMs which, in turn, synchronize the SMs and BHSs in the Cyclone network. The Oncore GPS Receiver also provides

the latitude and longitude of the GPS antenna (collocated with the CMM) the number of satellites that are being tracked the number of satellites that are available the date the time in Universal Coordinated Time (UCT) the altitude of the GPS antenna other information that can be used to diagnose network problems. Alternative to GPS Sync A Cyclone link can operate without GPS sync, but cannot operate without sync. The alternative to GPS sync is to configure the AP or BHM in the link to generate a sync pulse to pass to the SM or BHS, respectively. Depending on the RF environment in which the link operates, this latter alternative may or may not be plausible. Issue2,November2007 Draft5forRegulatoryReview 93 Release8 For example, in Figure 23, AP4 OverviewofCycloneNetworks

is not synchronized with any of the other APs. is transmitting nearby the other APs while they are expecting to receive SM transmissions from a maximum distance. Figure 23: One unsynchronized AP in cluster The result is self-interference. In this scenario, the self-interference can be avoided only by synchronizing the TDD transmit cycles of all APs that operate in the same frequency band. An AP that is isolated by at least 5 miles (8 km) from any other Cyclone equipment, or a BHM in an isolated standalone BH link can generate and pass sync pulse without GPS timing and not risk that interference will result from the generated sync. In any other type of Cyclone link, sync should be derived from GPS timing. NOTE:

The OFDM Series BHMs generate their own sync. For more information about these modules, see the user guides that support them. Titles are listed under Products Not Covered by This User Guide on Page 34. Advantage of GPS Sync Although the embedded timing generation capability of the Cyclone AP and BHM keeps a precise clock, no trigger exists to start the clock at the same moment in each AP of a cluster. So, the individual AP can synchronize communications between itself and registered SMs, but cannot synchronize itself with other Cyclone modules, except by GPS timing (shown in Figure 24). Issue2,November2007 Draft5forRegulatoryReview 94 Release8 OverviewofCycloneNetworks Figure 24: GPS timing throughout the Cyclone network (Cyclone FSK shown) 7.2.2 PassingSyncinaSingleHop Network sync can be passed in a single hop in the following network designs:

Design 1 1. A CMM provides sync to a collocated AP. 2. This AP sends the sync over the air to SMs.

Design 2 1. A CMM provides sync to a collocated BH timing master. 2. This BH timing master sends the sync over the air to a BH timing slave. 7.2.3 PassingSyncinanAdditionalHop Network sync can be extended by one additional link in any of the following network designs:

NOTE:

In each of these following designs, Link 2 is not on the same frequency band as Link 4. (For example, Link 2 may be a 5.2-GHz link while Link 4 is a 5.7- or 2.4-

GHz link.)

Design 3 1. A CMM provides sync to a collocated AP. 2. This AP sends the sync over the air to an SM. 3. This SM delivers the sync to a collocated AP. 4. This AP passes the sync in the additional link over the air to SMs. This design is illustrated in Figure 25. Issue2,November2007 Draft5forRegulatoryReview 95 Release8 AP 1 CMM OverviewofCycloneNetworks 2 SM AP 3 4 4 SM SM Figure 25: Additional link to extend network sync, Design 3

Design 4 1. A CMM provides sync to a collocated AP. 2. This AP sends the sync over the air to an SM. 3. This SM delivers the sync to a collocated BHM. 4. This BHM passes the sync in the additional link over the air to a BHS. This design is illustrated in Figure 26. AP 1 CMM 2 4 SM BH

-M-

3 BH

-S-

Figure 26: Additional link to extend network sync, Design 4

Design 5 1. A CMM provides sync to a collocated BHM or the BHM generates timing. 2. This BHM sends the sync over the air to a BHS. 3. This BHS delivers the sync to a collocated AP. 4. This AP passes the sync in the additional link over the air to SMs. This design is illustrated in Figure 27. Issue2,November2007 Draft5forRegulatoryReview 96 Release8 BH

-M-

1 CMM OverviewofCycloneNetworks 2 BH

-S-

AP 3 4 4 SM SM Figure 27: Additional link to extend network sync, Design 5 Wiring and configuration information for this sync extension is described under Wiring to Extend Network Sync on Page 374. All Cyclone radios support the remote AP functionality. The BHS and the SM can reliably pass the sync pulse, and the BHM and AP can reliably receive it. The sync is passed in a cable that connects Pins 1 and 6 of the RJ-11 timing ports of the two modules. (The sync cable is described under Cables on Page 57.) When you connect modules in this way, you must also adjust configuration parameters to ensure that the AP is set to properly receive sync. the SM will not propagate sync to the AP if the SM itself ceases to receive sync. Issue2,November2007 Draft5forRegulatoryReview 97 Release8 8 MEETINGLINKREQUIREMENTS OverviewofCycloneNetworks 8.1 APSMLINKS APs communicate with SMs using a point-to-multipoint protocol. An AP-SM link has lower throughput and higher latency than a backhaul link for two reasons:

Many endpoints are involved.

The bandwidth request and reservation process consumes bandwidth. In the 900-MHz frequency band range, round-trip latency is typically

40 msec with software scheduling. 15 msec with hardware scheduling. In all other Cyclone frequency band ranges, round-trip latency is typically

15 msec with software scheduling. 6 msec with hardware scheduling. At range settings of greater than 40 miles (64 km) in the 900-MHz AP, more time elapses between transmit and receive cycles to compensate for greater air delay. In each frame, this reduces the number of data slots, which slightly reduces the aggregate throughput of the link. However, the throughput is as predictable as in other Cyclone point-to-multipoint links. Throughput is a factor of the Max Range parameter in the AP and is effective for all SMs, regardless of their distance from the AP. Throughput includes all downlink data to all SMs and all uplink data from all SMs that link to the AP. For throughput with hardware scheduling, see Table 13 on Page 62. End user perspective of throughput is based on both bandwidth in the sending direction and the return of TCP acknowledgement packets in the other. Where sufficient downlink bandwidth exists to support downlink traffic and overhead, transient traffic congestion in the uplink can cause some TCP acknowledgement packets to be dropped, and the end user to perceive a reduction in throughput. This can also occur with sufficient uplink bandwidth and dropping acknowledgment packets in the downlink. However, a Cyclone network operator can optionally enable the Prioritize TCP ACK parameter in the AP and BHM, giving these packets priority over other packet types. This results in fewer of them being dropped. The effects of changing network conditions on PTMP throughput are indicated in Table 24. Issue2,November2007 Draft5forRegulatoryReview 99 Release8 OverviewofCycloneNetworks Table 24: Effects of network conditions on PTMP throughput Changing Network Condition Effect on AP Aggregate Throughput Increasing the Max Range parameter setting1 in the AP Increasing the number of SMs that register in the AP Increase in downlink traffic Increase in uplink traffic Increasing the average bandwidth allotted to the SMs that register in the AP somewhat decreased2 no effect no effect, even when the additional bandwidth is used. NOTES:

1. For non 900-MHz APs, the AP accepts a Max Range value of up to 30 miles (48 km). See Max Range on Page 244. 2. To avoid a decrease of unnecessary proportion, set to not much further than the distance between the AP and the furthest SM that registers in the AP. A comparison of SM products in link with a Cyclone Advantage AP is shown in Table 25. Table 25: Comparison of SM products with Cyclone Advantage AP Upgradability none to Advantage SM capabilities to 1, 2, 4, or 7 Mbps Product Cyclone Advantage SM Maximum Sustained Aggregate Throughput to a Single SM 14 Mbps Burst 14 Mb Cap on Committed Information Rate none Canopy SM 7 Mbps 14 Mb none Cyclone Lite SM as purchased Cyclone Lite SM upgraded to 1 Mbps Cyclone Lite SM upgraded to 2 Mbps Cyclone Lite SM upgraded to 4 Mbps Cyclone Lite SM upgraded to 7 Mbps 512 kbps 768 kb 100 kbps 1 Mbps 1.5 Mb 100 kbps none 2 Mbps 3 Mb 100 kbps none 4 Mbps 7 Mb 200 kbps none 7 Mbps 7 Mb 200 kbps none VoIP Channels Supported multiple multiple 1 1 1 2 2 Issue2,November2007 Draft5forRegulatoryReview 100 Release8 8.2 BHBHLINKS OverviewofCycloneNetworks Cyclone BHs communicate with each other using a point-to-point protocol. This point-to-

point protocol uses a 2.5-msec frame. A BH link has higher throughput and lower latency

(typically 5 msec, 2.5 msec in each direction) for two reasons:

Only two endpoints are involved.

No bandwidth request and reservation process is involved. For 10-Mbps BHs, the aggregate throughput on the channel is 7.5 Mbps. For 20-Mbps BHs, the aggregate throughput on the channel is 14 Mbps. If a BH is set to a downlink ratio of 50%, then the bandwidth in each direction is half of the total BH link bandwidth. Issue2,November2007 Draft5forRegulatoryReview 101 Release8 9 PREVIEWINGNETWORKCONFIGURATIONS OverviewofCycloneNetworks The following are examples of network layouts. Customer experience case studies are also available. 9.1 VIEWINGTYPICALLAYOUTS The following layouts are typical of Cyclone system implementations:

Figure 28: Typical network layout with no BH

Figure 29: Typical network layout with BH

Figure 30: Typical multiple-BH network layout AP Cluster 2 AP Cluster 3 AP Cluster 1 GPS CMM BAM RTR SM RTR PC Figure 28: Typical network layout with no BH WAN (Internet) Issue2,November2007 Draft5forRegulatoryReview 103 Release8 BHM GPS OverviewofCycloneNetworks B HS AP GPS CMM RTR WAN (I n te rn e t ) A P Cl u s te r 2 AP Cluster 3 A P Clu s t e r 1 C MM B A M S M R TR P C PC RTR SM Figure 29: Typical network layout with BH GPS BHS BHM BHM BHS CMM RTR WAN (Internet) Figure 30: Typical multiple-BH network layout Issue2,November2007 Draft5forRegulatoryReview 104 Release8 9.2 VIEWINGCASESTUDIES OverviewofCycloneNetworks Case studies of Cyclone implementations are available as Feature Articles for download from http://www.connectwithCyclone.com/index.cfm?Cyclone=menu.case. Issue2,November2007 Draft5forRegulatoryReview 105 Release8 10 ACCESSINGFEATURES OverviewofCycloneNetworks Cyclone Release 8 networks support the features that are indicated in Table 26. Table 26: Cyclone features Regulatory Features RoHS compliant (EU green mandate) WEEE compliant Complies with Human RF exposure limits

(ETSI) Module Type(s) All modules All modules Controlled in GUI Page/Tab no no All radios no All radios Module Type(s) Radio Features All radios Time Division Duplex Scalable up to 6 sectors per cell. AP SM 200 registered subscribers supported per AP AP SM Fixed /nomadic operation 20 ms or less round trip latency (OTA with Cyclone MAC, under normal conditions) Transmit frame spreading for geographical area co-existence Radio statistics (scheduler) 2X rate, enabled per link (requires Advantage AP or 20 Mbps BH) 2X rate, enabled per sector (requires Advantage AP or 20 Mbps BH ) Manual transmit power control - normal and low (-18 dB) Manual transmit power control, 1 dB increments over 25 dB at the AP All radios All radios All radios AP BHM AP BHM AP BHM SM BHS Controlled in GUI Page/Tab no no no no no Configuration/Radio Statistics/Scheduler Configuration/General Configuration/General Configuration/Radio Configuration/Radio SNMP Control no no no SNMP Control no no no no no yes yes yes yes yes yes Issue2,November2007 Draft5forRegulatoryReview 107 Release8 RF Configuration Features Configurable center-channel carrier frequency 255 configurable "color codes" to manage SM to AP (or (BHS to BHM) registration 16 configurable "sector IDs" for administrative convenience Module Type(s) OverviewofCycloneNetworks Controlled in GUI Page/Tab SNMP Control AP BHM Configuration/Radio All radios Configuration/Radio AP BHM Configuration/Radio Configurable range settings (determines air turn-around time) AP Configuration/Radio Configurable downlink data % (determines transmit/receive ratio) Configurable number of reserved control slots (manages contention for uplink requests) Configurable frequency scan list at SM Packet stats - RF interface Timing Features Configurable AP/BHM sync source - Sync over Power over Ethernet, self-sync, or sync cable

"Remote AP" support, including timing pulse propagation through SM/BHS Ethernet Interface Features Selectable link speeds - 10/100 Base T, half, full-duplex Ethernet link auto-negotiation Accepts straight-through or crossover Ethernet cable wiring (Auto-MDX) Wire line Interface: Ethernet cable with proprietary PoE Disable SM Ethernet link Packet stats - Ethernet interface AP BHM Configuration/Radio AP Configuration/Radio SM BHS All radios Module Type(s) Configuration/Radio Statistics/Radio Controlled in GUI Page/Tab AP BHM Configuration/General SM BHS Configuration/General Module Type(s) Controlled in GUI Page/Tab All modules Configuration/General All modules Configuration/General All modules no All modules no SM All radios Configuration/General Statistics/Ethernet yes yes yes yes yes yes yes yes SNMP Control yes yes SNMP Control yes no no no yes yes Issue2,November2007 Draft5forRegulatoryReview 108 Release8 IP Interface Features Configurable LAN settings (IP address, mask, gateway) Module's management IP address assignable via DHCP Private LAN to support AP to SM (or BHM to BHS) communications Configurable SM mgmt accessibility

(Local/Ethernet only, or Public/RF and Local/Ethernet) Security Features (Authentication, Encryption, and Access Control) Configurable SM authentication using BAM/PrizmEMS Configurable BH authentication, standalone DES encryption on standard product AES encryption on AES product Configurable whether SM/BHS displays AP/BHM beacon information Configurable web, telnet, and ftp session timeout Configurable access to radio management -

up to 3 source IP addresses User/account names (up to 4) and passwords on modules Permission levels control ability to add/delete users/passwords Override plug to override lost IP address or user/password Module Type(s) OverviewofCycloneNetworks Controlled in GUI Page/Tab SNMP Control All radios Configuration/IP All radios Configuration/IP All radios Configuration/IP SM Configuration/IP yes yes yes yes Module Type(s) Controlled in GUI Page/Tab SNMP Control AP SM Configuration/Security BHM BHS All radios All radios Configuration/Security no no AP BHM Configuration/Security All radios Configuration/Security All radios Configuration/Security All radios Account All radios Account All radios no yes no yes yes yes yes yes yes yes no yes no Override plug configurable as a default plug -

reset to factory defaults AP SM BHM BHS Configuration/Unit Settings Override switch to override lost IP address or user/password on CMM CMMmicro no Issue2,November2007 Draft5forRegulatoryReview 109 OverviewofCycloneNetworks Release8 Monitoring Features List of registered SMs/BHSs with full data, with hot links to SMs/BHSs Abbreviated list of SMs/BHSs, with hot links to SMs/BHSs Received power level indication LEDs on modules to display states and activity Received interference level indication (jitter) Configurable web-page auto-refresh SM registration failures Event log Operator can use own logo on GUI pages Operator can use own style sheets for GUI Bridge Management Features Configurable bridge entry timeout Bridging table statistics (up to 4096 entries) Disable bridging on BHs SM Isolation Features (preventing communication between SMs) SM isolation at AP SM isolation at CMM SM Isolation Features Translation bridging (replace customer MAC with SM MAC address) With Translation bridging, choice of sending untranslated ARP Translation table statistics Quick Start Feature AP configuration quick-start wizard Module Type(s) Controlled in GUI Page/Tab AP BHM Configuration/General AP BHM Configuration/General All radios Configuration/General All modules no All radios All modules AP BHM All modules All modules All modules Module Type(s) All radios All radios BHM BHS Module Type(s) AP CMMmicro Module Type(s) AP AP All radios Module Type(s) AP BHM Configuration/General Configuration/General Statistics/Reg Failures Home/Event Log no no Controlled in GUI Page/Tab Configuration/General Statistics/Bridging Table Configuration/General Controlled in GUI Page/Tab Configuration/General Configuration/General Controlled in GUI Page/Tab Configuration/General Configuration/General Statistics/Translation Table Controlled in GUI Page/Tab Quick Start SNMP Control multiple objects multiple objects yes no yes yes yes no yes yes SNMP Control yes yes yes SNMP Control yes yes SNMP Control yes yes yes SNMP Control Issue2,November2007 Draft5forRegulatoryReview 110 OverviewofCycloneNetworks Controlled in GUI Page/Tab SNMP Control Release8 Bandwidth Management Features AP Maximum Information Rate (MIR) default settings Per SM Maximum Information Rate (MIR) Per SM Committed Information Rate (CIR) for high and low channels

"Configuration Source" for MIR/CIR/HP/VLAN can be either SM or BAM/Prizm CIR for low priority channel on BH Configurable priority for TCP Acks, to optimize bandwidth use Bandwidth Management Features Configurable High Priority channel with configurable DiffServ mappings on AP, SM

(2 classes of service) Permanent BH High Priority Channel with configurable DiffServ mappings on BH

(2 classes of service) Virtual channel (high/low priority) statistics Network Address Translation (NAT) Features NAT NAT DMZ NAT DHCP server on LAN with up to 254 IP addresses in pool NAT DHCP client on WAN (obtains NAT address from a DHCP server) NAT port mapping VPN "pass through" for L2TP over IPSec

(but not PPTP) NAT statistics NAT DHCP statistics NAT table Filtering Features Protocol filtering based on protocol Operator-defined port filtering (3 ports) Packet filter statistics Module Type(s) AP SM SM AP Configuration/QoS Configuration/QoS Configuration/QoS Configuration/General BHS Configuration/QoS AP BHM Configuration/General Module Type(s) Controlled in GUI Page/Tab AP SM Configuration/DiffServe BHM BHS Configuration/DiffServe All radios Module Type(s) SM SM Statistics/Data VC Controlled in GUI Page/Tab Configuration/NAT Configuration/NAT SM SM SM SM SM SM Module Type(s) SM SM All radios Configuration/NAT Configuration/NAT Configuration/NAT no Statistics/NAT Stats Statistics/NAT DHCP Statistics Logs/NAT Table Controlled in GUI Page/Tab Configuration/Protocol Filtering Configuration/Protocol Filtering Statistics/Filter yes yes yes yes yes yes SNMP Control yes yes yes SNMP Control yes yes yes yes yes no yes yes no SNMP Control yes yes yes Issue2,November2007 Draft5forRegulatoryReview 111 Release8 OverviewofCycloneNetworks VLAN Management Features Configurable VLAN Highly configurable VLAN (802.1Q) Use of VLAN priorities (802.1p) with high priority channel Module Type(s) AP SM CMMmicro AP SM Controlled in GUI Page/Tab Configuration/VLAN Configuration/VLAN AP SM no Port-based VLAN switching on CMM CMMmicro Configuration VLAN statistics Dynamic Frequency Selection (DFS) Feature DFS v1.2.3 Time Features Time and Date from CMM via Network Time Protocol (NTP) server Time and Date manually settable CMM provides NTP server Spectrum Analyzer Features Spectrum analyzer Ability to switch an AP to an SM (or BHS to BHM) Aim/Link Quality Features Alignment tone for using during aiming/alignment Aiming support page when not using alignment tone LED for alignment Configure SM power-up state - aiming or operational Link capacity test, with configurable packet length Display of SM configuration information at AP Display/evaluation of AP beacon data from all receivable APs Over-the-air radio Bit Error Rate (BER) indicator AP SM Module Type(s) All radios Module Type(s) Statistics/VLAN Controlled in GUI Page/Tab no Controlled in GUI Page/Tab AP BHM Configuration/Time AP BHM CMMmicro Module Type(s) SM BHS Configuration/Time no Controlled in GUI Page/Tab Tools/Spectrum Analyzer AP BHM Configuration/General Module Type(s) Controlled in GUI Page/Tab SM BHS no SM BHS Tools/Alignment SM BHS no SM BHS Configuration/General All radios Tools/Link Capacity Test AP BHM Home/Session Status SM BHS Tools/AP Evaluation All radios Tools/BER Results SNMP Control yes yes yes yes yes SNMP Control yes SNMP Control yes yes no SNMP Control no yes SNMP Control no multiple objects no yes yes yes yes yes Issue2,November2007 Draft5forRegulatoryReview 112 Release8 Frame Tool Feature Frame calculator for supporting collocation Personal Digital Assistant (PDA) Interface Features GUI automatically sized/styled for PDA when displayed on a PDA Spectrum analyzer display for PDA Specific pages for PDA display SNMP Interface Features Support of SNMP v2 Cyclone Enterprise MIB Configurable SNMP community string Configurable SNMP accessing subnet 10 configurable SNMP trap addresses Configurable traps (sync and session) Configurable SNMP permissions (read, read/write) Configurable site information, including site name Upgrade Process Features Upgrading using CNUT and SM Auto-update for SMs Configurable update address to support distributed software upgrades AP Cluster Management Features CMM port power control CMM port reset CMM: Sufficient ports for at least 4 AP, 2 BH, plus management CMM: Sufficient power for at least 4 AP plus 2 BH OverviewofCycloneNetworks Module Type(s) All radios Module Type(s) Controlled in GUI Page/Tab Tools/Frame Calculator Controlled in GUI Page/Tab All radios all All radios All radios Module Type(s) All modules All modules All radios All radios All radios All radios PDA/Spectrum Results (PDA) PDA Controlled in GUI Page/Tab no no Configuration/SNMP Configuration/SNMP Configuration/SNMP Configuration/SNMP All radios Configuration/SNMP All modules Configuration/SNMP Module Type(s) Controlled in GUI Page/Tab All modules no AP Configuration/General Module Type(s) CMMmicro CMMmicro CMMmicro CMMmicro Controlled in GUI Page/Tab Configuration Configuration no no no SNMP Control no SNMP Control no no no SNMP Control no no yes yes yes yes yes yes SNMP Control no yes SNMP Control yes yes no no no Powered from 90-264 VAC, 50/60 Hz; 55 V DC power output AP BH Issue2,November2007 Draft5forRegulatoryReview 113 OverviewofCycloneNetworks Module Type(s) All modules All modules All radios Controlled in GUI Page/Tab no no Home/General All modules no SNMP Control no no no no Release8 Physical Features MTBF > 45 years (~400 000 hours) neg 40 C to + 55 C (Ambient) operation Temperature indication Non-condensing (Indoor/outdoor), weather protected form factor/packaging Element Management System (Prizm) Features Current Prizm to manage all elements of the system (including Mot Backhaul) Up to 1000 APs, plus 100 devices/AP);

minimal storage / minimal polling Redundant configuration for additional storage/reporting capability Commercial Off the Shelf (COTS) Platform and OS support (e.g. Intel, Linux, Windows) COTS Database support (e.g. MySQL, PostgreSQL, MS SQL Server, etc..); Oracle optional 10.1 ACTIVATINGFEATURES A Cyclone feature is active if the software that allows the feature to be turned on or off

(enabled or disabled) is present. 10.1.1 FixedLicenseKeys Some features are activated by loading a fixed license key into the radio. Such a key arrives from Last Mile Gear as a filename.url file. When you double-click on this file, your browser opens and the location bar is populated by a lengthy string. This URL string begins with http://<ModuleIPAddress>/. If you need to load a key into a module whose IP address has changed since Last Mile Gear issued the key, perform the following steps. Procedure 1: Modifying a fixed license key for a module IP address 1. Right-click on the license key filename. 2. Select Properties. 3. Select the Web Document tab. 4. At URL, substitute the current IP address for the original IP address in the URL. 5. Click OK. 6. Double-click on the license key filename. RESULT: The key loads into the module. Issue2,November2007 Draft5forRegulatoryReview 114 Release8 OverviewofCycloneNetworks 7. Open the Configuration web page of the module. 8. Review parameter settings and enable the feature if you wish to do so at this time (see next section). end of procedure 10.2 ENABLINGFEATURES A Cyclone feature is enabled (functioning) if the feature is both active and enabled. For example, Transmit Frame Spreading is active (can be enabled) in any AP or BHM that operates on Release 8. However, Transmit Frame Spreading functions only if the Enable selection for the Transmit Frame Spreading parameter is checked in the Radio tab of the Configuration web page in the module. Issue2,November2007 Draft5forRegulatoryReview 115 Release8 11 ACQUIRINGPROFICIENCIES OverviewofCycloneNetworks Designing and operating a Cyclone network requires fundamental knowledge of radio frequency transmission and reception, Internet Protocol addressing schemes, experimentation with Cyclone equipment, and for most operators participation in some forms of Cyclone training. 11.1 UNDERSTANDINGRFFUNDAMENTALS Cyclone training and user interfaces presume an understanding of RF fundamentals. Excellent written sources for these fundamentals are available. One such source is Deploying License-Free Wireless Wide-Area Networks by Jack Unger (ISBN 1-58705-

069-2), published by Cisco Press. 11.2 UNDERSTANDINGIPFUNDAMENTALS Cyclone training and user interfaces also presume an understanding of Internet Protocol

(IP) fundamentals. Excellent written sources for these fundamentals are available. One such source is Sams Teach Yourself TCP/IP in 24 Hours by Joe Casad

(ISBN 0-672-32085-1), published by Sams Publishing. The default IP address of each Cyclone component is 169.254.1.1. NOTE:

11.3 ACQUIRINGACYCLONEDEMONSTRATIONKIT Cyclone Demonstration Kits are available through your Cyclone representative. 11.3.1 900MHzwithIntegratedAntennaandBandpassFilterDemonstrationKit Each 900-MHz with integrated antenna and band-pass filter Demonstration Kit contains

2 9000SM SMs 1 9000APF AP 1 300SS Surge Suppressor 3 ACPSSW-02 90- to 230-V AC 50- to 60-Hz Power Supplies 3 CBL-0562 Straight-through Category 5 Cables 1 UGTK-0002 Trial Kit Quick Start Guide 1 CPT001-CD02EN Sales Overview on CD 1 CPT002-CD03EN Technical Overview on CD 1 CPT003-CD03EN Cyclone User Guides on CD Part numbers for Demonstration Kits are provided in Table 27. Issue2,November2007 Draft5forRegulatoryReview 117 Release8 11.3.2 OverviewofCycloneNetworks 900MHzwithConnectorizedAntennaDemonstrationKit Each 900-MHz with connectorized (external) antenna Demonstration Kit contains

2 9000SMC SMs 1 9000APC AP 3 AN900 60 9-dBi Antennas 1 300SS Surge Suppressor 1 SMMB2 Universal Heavy Duty Mounting Bracket 3 ACPSSW-02 90- to 230-V AC 50- to 60-Hz Power Supplies 3 CBL-0562 Straight-through Category 5 Cables 1 UGTK-0002 Trial Kit Quick Start Guide 1 CPT001-CD02EN Sales Overview on CD 1 CPT002-CD03EN Technical Overview on CD 1 CPT003-CD03EN Cyclone User Guides on CD Part numbers for Demonstration Kits are provided in Table 27. 11.3.3 2.4GHzwithAdjustablePowerSettoLowDemonstrationKit Each 2.4-GHz with adjustable power set to low Demonstration Kit contains

1 2400SMWL SM 1 2450SMWL Advantage SM 1 2450APWL Advantage AP 1 300SS Surge Suppressor 1 SMMB1 Universal Mounting Bracket 3 ACPSSW-02 90- to 230-V AC 50- to 60-Hz Power Supplies 3 CBL-0562 Straight-through Category 5 Cables 1 UGTK-0002 Trial Kit Quick Start Guide 1 CPT001-CD02EN Sales Overview on CD 1 CPT002-CD03EN Technical Overview on CD 1 CPT003-CD03EN Cyclone User Guides on CD Part numbers for Demonstration Kits are provided in Table 27. 11.3.4 2.4GHzwithAdjustablePowerSettoHighDemonstrationKit Each 2.4-GHz with adjustable power set to high Demonstration Kit contains

1 2400SM SM 1 2450SM Advantage SM 1 2450AP Advantage AP 1 300SS Surge Suppressor 1 SMMB1 Universal Mounting Bracket 3 ACPSSW-02 90- to 230-V AC 50- to 60-Hz Power Supplies 3 CBL-0562 Straight-through Category 5 Cables 1 UGTK-0002 Trial Kit Quick Start Guide Issue2,November2007 Draft5forRegulatoryReview 118 Release8 OverviewofCycloneNetworks

1 CPT001-CD02EN Sales Overview on CD 1 CPT002-CD03EN Technical Overview on CD 1 CPT003-CD03EN Cyclone User Guides on CD Part numbers for Demonstration Kits are provided in Table 27. 11.3.5 5.1GHzDemonstrationKit Each 5.1-GHz Demonstration Kit contains

1 5202SM SM 1 5252SM Advantage SM 1 5252AP Advantage AP 1 300SS Surge Suppressor 1 SMMB1 Universal Mounting Bracket 3 ACPSSW-02 90- to 230-V AC 50- to 60-Hz Power Supplies 3 CBL-0562 Straight-through Category 5 Cables 1 UGTK-0002 Trial Kit Quick Start Guide 1 CPT001-CD02EN Sales Overview on CD 1 CPT002-CD03EN Technical Overview on CD 1 CPT003-CD03EN Cyclone User Guides on CD Part numbers for Demonstration Kits are provided in Table 27. 11.3.6 5.2GHzDemonstrationKit Each 5.2-GHz Demonstration Kit contains

1 5200SM SM 1 5250SM Advantage SM 1 5250AP Advantage AP 1 300SS Surge Suppressor 1 SMMB1 Universal Mounting Bracket 3 ACPSSW-02 90- to 230-V AC 50- to 60-Hz Power Supplies 3 CBL-0562 Straight-through Category 5 Cables 1 UGTK-0002 Trial Kit Quick Start Guide 1 CPT001-CD02EN Sales Overview on CD 1 CPT002-CD03EN Technical Overview on CD 1 CPT003-CD03EN Cyclone User Guides on CD Part numbers for Demonstration Kits are provided in Table 27. 11.3.7 5.4GHzDemonstrationKit Each 5.4-GHz Demonstration Kit contains

1 5400SM SM 1 5450SM Advantage SM 1 5450AP Advantage AP Issue2,November2007 Draft5forRegulatoryReview 119 Release8 OverviewofCycloneNetworks

1 300SS Surge Suppressor 1 SMMB1 Universal Mounting Bracket 3 ACPSSW-02 90- to 230-V AC 50- to 60-Hz Power Supplies 3 CBL-0562 Straight-through Category 5 Cables 1 UGTK-0002 Trial Kit Quick Start Guide 1 CPT001-CD02EN Sales Overview on CD 1 CPT002-CD03EN Technical Overview on CD 1 CPT003-CD03EN Cyclone User Guides on CD Part numbers for Demonstration Kits are provided in Table 27. 11.3.8 5.7GHzwithIntegratedAntennaDemonstrationKit Each 5.7-GHz with integrated antenna Demonstration Kit contains

1 5700SM SM 1 5750SM Advantage SM 1 5750AP Advantage AP 1 300SS Surge Suppressor 1 SMMB1 Universal Mounting Bracket 3 ACPSSW-02 90- to 230-V AC 50- to 60-Hz Power Supplies 3 CBL-0562 Straight-through Category 5 Cables 1 UGTK-0002 Trial Kit Quick Start Guide 1 CPT001-CD02EN Sales Overview on CD 1 CPT002-CD03EN Technical Overview on CD 1 CPT003-CD03EN Cyclone User Guides on CD Part numbers for Demonstration Kits are provided in Table 27. 11.3.9 5.7GHzwithConnectorizedAntennaandAdjustablePowerSettoLow Each 5.7-GHz with connectorized antenna and adjustable power set to low Demonstration Kit contains

1 5700SMC SM 1 5750SMC Advantage SM 1 5750APC Advantage AP 1 300SS Surge Suppressor 1 SMMB2 Universal Heavy Duty Mounting Bracket 3 ACPSSW-02 90- to 230-V AC 50- to 60-Hz Power Supplies 3 CBL-0562 Straight-through Category 5 Cables 1 UGTK-0002 Trial Kit Quick Start Guide 1 CPT001-CD02EN Sales Overview on CD 1 CPT002-CD03EN Technical Overview on CD 1 CPT003-CD03EN Cyclone User Guides on CD Part numbers for Demonstration Kits are provided in Table 27. Issue2,November2007 Draft5forRegulatoryReview 120 Release8 11.3.10 DemonstrationKitPartNumbers OverviewofCycloneNetworks The part numbers for ordering Cyclone demonstration kits are provided in Table 27. Table 27: Demonstration Kit part numbers Frequency Band Range 900 MHz integrated antenna with band-pass filter 900 MHz connectorized antenna 2.4 GHz adjustable power set to low 2.4 GHz adjustable power set to high 5.1 GHz 5.2 GHz 5.4 GHz 5.7 GHz 5.7 GHz connectorized adjustable power set to low Part Number TK10290 TK10290C TK10250 TK10251 TK10253 TK10252 TK10254 TK10257 TK10257C 11.4 ACQUIRINGACYCLONESTARTERKIT Cyclone Starter Kits are also available through your Cyclone representative. 11.4.1 900MHzwithIntegratedAntennaandBandpassFilterStarterKit Each 900-MHz with integrated antenna and band-pass filters Starter Kit contains

20 9000SM SMs 3 9000APF Advantage APs 1 1070CK CMMmicro 21 300SS Surge Suppressors 1 UGSK-0003 Quick Start Guide 1 CPT003-CD03EN Cyclone User Guides on CD Power supplies and SM mounting brackets are not included in this kit. Part numbers for Starter Kits are provided in Table 28. Issue2,November2007 Draft5forRegulatoryReview 121 Release8 11.4.2 OverviewofCycloneNetworks 900MHzwithConnectorizedAntennaStarterKit Each 900-MHz with connectorized (external) antenna Starter Kit contains

20 9000SMC SMs 3 9000APC Advantage APs 23 AN900 60 9-dBi Antennas 1 1070CK CMMmicro 21 300SS Surge Suppressors 20 SMMB2 Universal Heavy Duty Mounting Brackets 1 UGSK-0003 Quick Start Guide 1 CPT003-CD03EN Cyclone User Guides on CD Power supplies are not included in this kit. Part numbers for Starter Kits are provided in Table 28. 11.4.3 2.4GHzwithAdjustablePowerSettoLowStarterKit Each 2.4-GHz with adjustable power set to low Starter Kit contains

30 2400SMWL SMs 6 2450APWL Advantage APs 1 1070CK CMMmicro 31 300SS Surge Suppressors 30 SMMB1 Universal Mounting Brackets 1 UGSK-0003 Quick Start Guide 1 CPT003-CD03EN Cyclone User Guides on CD Power supplies are not included in this kit. Part numbers for Starter Kits are provided in Table 28. 11.4.4 2.4GHzwithAdjustablePowerSettoHighStarterKit Each 2.4-GHz adjustable power set to high Starter Kit contains

30 2400SM SMs 6 2450AP Advantage APs 1 1070CK CMMmicro 31 300SS Surge Suppressors 30 SMMB1 Universal Mounting Brackets 1 UGSK-0003 Quick Start Guide 1 CPT003-CD03EN Cyclone User Guides on CD Power supplies are not included in this kit. Part numbers for Starter Kits are provided in Table 28. Issue2,November2007 Draft5forRegulatoryReview 122 Release8 11.4.5 OverviewofCycloneNetworks 5.1GHzStarterKit Each 5.1-GHz adjustable power set to high Starter Kit contains

30 5202SM SMs 6 5252AP Advantage APs 1 1070CK CMMmicro 31 300SS Surge Suppressors 30 SMMB1 Universal Mounting Brackets 1 UGSK-0003 Quick Start Guide 1 CPT003-CD03EN Cyclone User Guides on CD Power supplies are not included in this kit. Part numbers for Starter Kits are provided in Table 28. 11.4.6 5.2GHzStarterKit Each 5.2-GHz Starter Kit contains

30 5200SM SMs 6 5250AP Advantage APs 1 1070CK CMMmicro 31 300SS Surge Suppressors 30 SMMB1 Universal Mounting Brackets 1 UGSK-0003 Quick Start Guide 1 CPT003-CD03EN Cyclone User Guides on CD Power supplies are not included in this kit. Part numbers for Starter Kits are provided in Table 28. 11.4.7 5.4GHzStarterKit Each 5.4-GHz Starter Kit contains

30 5400SM SMs 6 5450AP Advantage APs 1 1070CK CMMmicro 31 300SS Surge Suppressors 30 SMMB1 Universal Mounting Brackets 1 UGSK-0003 Quick Start Guide 1 CPT003-CD02EN Cyclone System User Guide on CD Power supplies are not included in this kit. Part numbers for Starter Kits are provided in Table 28. Issue2,November2007 Draft5forRegulatoryReview 123 Release8 11.4.8 OverviewofCycloneNetworks 5.7GHzwithIntegratedAntennaStarterKit Each 5.7-GHz with integrated antenna Starter Kit contains

30 5700SM SMs 6 5750AP Advantage APs 1 1070CK CMMmicro 31 300SS Surge Suppressors 30 SMMB1 Universal Mounting Brackets 1 UGSK-0003 Quick Start Guide 1 CPT003-CD03EN Cyclone User Guides on CD Power supplies are not included in this kit. Part numbers for Starter Kits are provided in Table 28. 11.4.9 5.7GHzwithConnectorizedAntennaandAdjustablePowerSettoLow Each 5.7-GHz with connectorized antenna and adjustable power set to low Starter Kit contains

30 5700SMC SMs 6 5750APC Advantage APs 1 1070CK CMMmicro 31 300SS Surge Suppressors 30 SMMB1 Universal Mounting Brackets 1 UGSK-0003 Quick Start Guide 1 CPT003-CD03EN Cyclone User Guides on CD Power supplies are not included in this kit. Part numbers for Starter Kits are provided in Table 28. 11.4.10 StarterKitPartNumbers The part numbers for ordering Cyclone Starter kits are provided in Table 28. Table 28: Starter Kit part numbers Frequency Band Range 900 MHz integrated antenna with band-pass filter 900 MHz connectorized 2.4 GHz adjustable power set to low 2.4 GHz adjustable power set to high 5.1 GHz 5.2 GHz 5.4 GHz Part Number TK10190 TK10190C TK10150 TK10151 TK10153 TK10152 TK10154 Issue2,November2007 Draft5forRegulatoryReview 124 Release8 OverviewofCycloneNetworks Frequency Band Range 5.7 GHz 5.7 GHz connectorized adjustable power set to low Part Number TK10157 TK10157C 11.5 EVALUATINGCYCLONETRAININGOPTIONS Cyclone and its distributors make technical training available to customers. For information on this training, either

send email inquiries to training@Cyclonewireless.com. visit http://www.Last Mile Gear.com/Cyclone. Under Contact Us, select Request Product Info, select Product Info, then under Support, select Training. 11.6 ATTENDINGONLINEKNOWLEDGESESSIONS Irregularly but often, Cyclone presents a knowledge session over the Internet about a new product offering. Some of these knowledge sessions provide the opportunity for participants to interact in real time with the leader of the session. The knowledge session

provides a high-level understanding of the technology that the new product introduces. announces any subtleties and caveats. typically includes a demonstration of the product. is usually recorded for later viewing by those who could not attend in real time. To participate in upcoming knowledge sessions, ask your Cyclone representative to ensure that you receive email notifications. Issue2,November2007 Draft5forRegulatoryReview 125 Release8 PlanningGuide PPPLLLAAANNNNNNIIINNNGGGGGGUUUIIIDDDEEE Issue2,November2007 Draft5forRegulatoryReview 127 Release8 12 ENGINEERINGYOURRFCOMMUNICATIONS PlanningGuide Before diagramming network layouts, the wise course is to

anticipate the correct amount of signal loss for your fade margin calculation

(as defined below). recognize all permanent and transient RF signals in the environment. identify obstructions to line of sight reception. 12.1 ANTICIPATINGRFSIGNALLOSS The C/I (Carrier-to-Interference) ratio defines the strength of the intended signal relative to the collective strength of all other signals. Cyclone modules typically do not require a C/I ratio greater than

3 dB or less at 10-Mbps modulation and 65 dBm for 1X operation. The C/I ratio that you achieve must be even greater as the received power approaches the nominal sensitivity (85 dBm for 1X operation). 10 dB or less at 10-Mbps modulation and 65 dBm for 2X operation. The C/I ratio that you achieve must be even greater as the received power approaches the nominal sensitivity (79 dBm for 2X operation). 10 dB or less at 20-Mbps modulation. 12.1.1 UnderstandingAttenuation An RF signal in space is attenuated by atmospheric and other effects as a function of the distance from the initial transmission point. The further a reception point is placed from the transmission point, the weaker is the received RF signal. 12.1.2 CalculatingFreeSpacePathLoss The attenuation that distance imposes on a signal is the free space path loss. PathLossCalcPage.xls calculates free space path loss. 12.1.3 CalculatingRxSignalLevel The Rx sensitivity of each module is provided at http://Last Mile Gear.Cyclonewireless.com/prod_specs.php. The determinants in Rx signal level are illustrated in Figure 31. Issue2,November2007 Draft5forRegulatoryReview 129 Release8 Tx cable loss Tx power Transmitter transmitter or Amplifier or amplifier PlanningGuide Tx antenna gain Rx antenna gain free space signal distance Rx cable loss Rx signal level receiver or amplifier Figure 31: Determinants in Rx signal level Rx signal level is calculated as follows:

Rx signal level dB = Tx power Tx cable loss + Tx antenna gain free space path loss

+ Rx antenna gain Rx cable loss NOTE:

This Rx signal level calculation presumes that a clear line of sight is established between the transmitter and receiver and that no objects encroach in the Fresnel zone. 12.1.4 CalculatingFadeMargin Free space path loss is a major determinant in Rx (received) signal level. Rx signal level, in turn, is a major factor in the system operating margin (fade margin), which is calculated as follows:

system operating margin (fade margin) dB =Rx signal level dB Rx sensitivity dB Thus, fade margin is the difference between strength of the received signal and the strength that the receiver requires for maintaining a reliable link. A higher fade margin is characteristic of a more reliable link. Issue2,November2007 Draft5forRegulatoryReview 130 Release8 12.2 ANALYZINGTHERFENVIRONMENT PlanningGuide An essential element in RF network planning is the analysis of spectrum usage and the strength of the signals that occupy the spectrum you are planning to use. Regardless of how you measure and log or chart the results you find (through the Spectrum Analyzer in SM and BHS feature or by using a spectrum analyzer), you should do so

at various times of day. on various days of the week. periodically into the future. As new RF neighbors move in or consumer devices in your spectrum proliferate, this will keep you aware of the dynamic possibilities for interference with your network. 12.2.1 MappingRFNeighborFrequencies Cyclone modules allow you to

use an SM or BHS (or a BHM reset to a BHS), or an AP that is temporarily transformed into an SM, as a spectrum analyzer. view a graphical display that shows power level in RSSI and dBm at 5-MHz increments throughout the frequency band range, regardless of limited selections in the Custom Radio Frequency Scan Selection List parameter of the SM. select an AP channel that minimizes interference from other RF equipment. The SM measures only the spectrum of its manufacture. So if, for example, you wish to analyze an area for both 2.4- and 5.7-GHz activity, take both a 2.4- and 5.7-GHz SM to the area. To enable this functionality, perform the following steps:

CAUTION!

The following procedure causes the SM to drop any active RF link. If a link is dropped when the spectrum analysis begins, the link can be re-established when either a 15-minute interval has elapsed or the spectrum analyzer feature is disabled. Procedure 2: Analyzing the spectrum 1. Predetermine a power source and interface that will work for the SM or BHS in the area you want to analyze. 2. Take the SM or BHS, power source, and interface device to the area. 3. Access the Tools web page of the SM or BHS. RESULT: The Tools page opens to its Spectrum Analyzer tab. An example of this tab is shown in Figure 137. 4. Click Enable. RESULT: The feature is enabled. Issue2,November2007 Draft5forRegulatoryReview 131 Release8 PlanningGuide 5. Click Enable again. RESULT: The system measures RSSI and dBm for each frequency in the spectrum. 6. Travel to another location in the area. 7. Click Enable again. RESULT: The system provides a new measurement of RSSI and dBm for each frequency in the spectrum. NOTE: Spectrum analysis mode times out 15 minutes after the mode was invoked. 8. Repeat Steps 6 and 7 until the area has been adequately scanned and logged. end of procedure As with any other data that pertains to your business, a decision today to put the data into a retrievable database may grow in value to you over time. RECOMMENDATION:

Wherever you find the measured noise level is greater than the sensitivity of the radio that you plan to deploy, use the noise level (rather than the link budget) for your link feasibility calculations. 12.2.2 AnticipatingReflectionofRadioWaves In the signal path, any object that is larger than the wavelength of the signal can reflect the signal. Such an object can even be the surface of the earth or of a river, bay, or lake. The wavelength of the signal is approximately

2 inches for 5.2- and 5.7-GHz signals. 5 inches for 2.4-GHz signals. 12 inches for 900-MHz signals. A reflected signal can arrive at the antenna of the receiver later than the non-reflected signal arrives. These two or more signals cause the condition known as multipath. When multipath occurs, the reflected signal cancels part of the effect of the non-reflected signal so, overall, attenuation beyond that caused by link distance occurs. This is problematic at the margin of the link budget, where the standard operating margin (fade margin) may be compromised. 12.2.3 NotingPossibleObstructionsintheFresnelZone The Fresnel (pronounced freNEL) Zone is a theoretical three-dimensional area around the line of sight of an antenna transmission. Objects that penetrate this area can cause the received strength of the transmitted signal to fade. Out-of-phase reflections and absorption of the signal result in signal cancellation. The foliage of trees and plants in the Fresnel Zone can cause signal loss. Seasonal density, moisture content of the foliage, and other factors such as wind may change the amount of loss. Plan to perform frequent and regular link tests if you must transmit though foliage. Issue2,November2007 Draft5forRegulatoryReview 132 Release8 12.2.4 RadarSignatureDetectionandShutdown PlanningGuide With Release 8.1, Cyclone meets ETSI EN 301 893 v1.2.3 for Dynamic Frequency Selection (DFS). DFS is a requirement in certain countries of the EU for systems like Cyclone to detect interference from other systems, notably radar systems, and to avoid co-channel operation with these systems. All 5.4 GHz modules and all 5.7 GHz Connectorized modules running Release 8.1 have DFS. Other modules running Release 8.1 do not. With Release 8.1, Canopy SMs and BHSs as well as Cyclone APs and BHMs will detect radar systems. When an AP or BHM enabled for DFS boots, it receives for 1 minute, watching for the radar signature, without transmitting. If no radar pulse is detected during this minute, the module then proceeds to normal beacon transmit mode. If it does detect radar, it waits for 30 minutes without transmitting, then watches the 1 minute, and will wait again if it detects radar. If while in operation, the AP or BHM detects the radar signature, it will cease transmitting for 30 minutes and then begin the 1 minute watch routine. Since an SM or BHS only transmits if it is receiving beacon from an AP or BHM, the SMs in the sector or BHS are also not transmitting when the AP or BHM is not transmitting. When an SM or BHS with DFS boots, it scans to see if an AP or BHM is present (if it can detect a Cyclone beacon). If an AP or BHM is found, the SM or BHS receives on that frequency for 1 minute to see if the radar signature is present. For an SM, if no radar pulse is detected during this 1 minute, the SM proceeds through normal steps to register to an AP. For a BHS, if no radar pulse is detected during this 1 minute, it registers, and as part of registering and ranging watches for the radar signature for another 1 minute. If the SM or BH does detect radar, it locks out that frequency for 30 minutes and continues scanning other frequencies in its scan list. Note, after an SM or BHS has seen a radar signature on a frequency and locked out that frequency, it may connect to a different AP or BHM, if color codes, transmitting frequencies, and scanned frequencies support that connection. For all modules, the module displays its DFS state on its General Status page. You can read the DFS status of the radio in the General Status tab of the Home page as one of the following:

Normal Transmit Radar Detected Stop Transmitting for n minutes, where n counts down from 30 to 1. Checking Channel Availability Remaining time n seconds, where n counts down from 60 to 1. This indicates that a 30-minute shutdown has expired and the one-minute re-scan that follows is in progress. DFS can be enabled or disabled on a modules Radio page: Configuration > Radio >

DFS. Operators in countries with regulatory requirements for DFS must not disable the feature and must ensure it is enabled after a module is reset to factory defaults. Operators in countries without regulatory requirements for DFS will most likely not want to use the feature, as it adds no value if not required, and adds an additional 1 minute to the connection process for APs, BHMs, and SMs, and 2 minutess for BHSs.

Issue2,November2007 Draft5forRegulatoryReview 133 Release8 PlanningGuide RECOMMENDATION:

Where regulations require that radar sensing and radio shutdown is enabled, you can most effectively share the spectrum with satellite services if you perform spectrum analysis and select channels that are distributed evenly across the frequency band range. A connectorized 5.7-GHz module provides an Antenna Gain parameter. When you indicate the gain of your antenna in this field, the algorithm calculates the appropriate sensitivity to radar signals, and this reduces the occurrence of false positives (wherever the antenna gain is less than the maximum). 12.3 USINGJITTERTOCHECKRECEIVEDSIGNALQUALITY(CYCLONE FSKONLY) The General Status tab in the Home page of the Canopy SM and BHS displays current values for Jitter, which is essentially a measure of interference. Interpret the jitter value as indicated in Table 29. Table 29: Signal quality levels indicated by jitter Correlation of Highest Seen Jitter to Signal Quality High Quality Questionable Quality Poor Quality 0 to 4 5 to 14 0 to 9 10 to 14 15 15 Signal Modulation 1X operation

(2-level FSK) 2X operation

(4-level FSK) In your lab, an SM whose jitter value is constant at 14 may have an incoming packet efficiency of 100%. However, a deployed SM whose jitter value is 14 is likely to have even higher jitter values as interfering signals fluctuate in strength over time. So, do not consider 14 to be acceptable. Avoiding a jitter value of 15 should be the highest priority in establishing a link. At 15, jitter causes fragments to be dropped and link efficiency to suffer. Cyclone modules calculate jitter based on both interference and the modulation scheme. For this reason, values on the low end of the jitter range that are significantly higher in 2X operation can still be indications of a high quality signal. For example, where the amount of interference remains constant, an SM with a jitter value of 3 in 1X operation can display a jitter value of 7 when enabled for 2X operation. However, on the high end of the jitter range, do not consider the higher values in 2X operation to be acceptable. This is because 2X operation is much more susceptible to problems from interference than is 1X. For example, where the amount of interference remains constant, an SM with a jitter value of 6 in 1X operation can display a jitter value of 14 when enabled for 2X operation. As indicated in Table 29, these values are unacceptable. Cyclone OFDM uses a different modulation scheme and does not display a jitter value. Issue2,November2007 Draft5forRegulatoryReview 134 Release8 12.4 USINGLINKEFFICIENCYTOCHECKRECEIVEDSIGNALQUALITY A link test, available in the Link Capacity Test tab of the Tools web page in an AP or BH, provides a more reliable indication of received signal quality, particularly if you launch tests of varying duration. However, a link test interrupts traffic and consumes system capacity, so do not routinely launch link tests across your networks. PlanningGuide 12.4.1 ComparingEfficiencyin1XOperationtoEfficiencyin2XOperation Efficiency of at least 98 to 100% indicates a high quality signal. Check the signal quality numerous times, at various times of day and on various days of the week (as you checked the RF environment a variety of times by spectrum analysis before placing radios in the area). Efficiency less than 90% in 1X operation or less than 60% in 2X operation indicates a link with problems that require action. 12.4.2 WhentoSwitchfrom2Xto1XOperationBasedon60%LinkEfficiency In the above latter case (60% in 2X operation), the link experiences worse latency (from packet resends) than it would in 1X operation, but still greater capacity, if the link remains stable at 60% Efficiency. Downlink Efficiency and Uplink Efficiency are measurements produced by running a link test from either the SM or the AP. Examples of what action should be taken based on Efficiency in 2X operation are provided in Table 30. Table 30: Recommended courses of action based on Efficiency in 2X operation Module Types Further Investigation Result Recommended Action Advantage AP with Advantage SM Check the General Status tab of the Advantage SM.1 See Checking the Status of 2X Operation on Page 92. Rerun link tests. Uplink and downlink are both 60% Efficiency.2 Uplink and downlink are both 60% Efficiency. Rerun link tests. Optionally, re-aim SM, add a reflector, or otherwise mitigate interference. In any case, continue 2X operation up and down. Issue2,November2007 Draft5forRegulatoryReview 135 Release8 Module Types PlanningGuide Further Investigation Result Recommended Action Check the General Status tab of the Canopy SM.1 See Checking the Status of 2X Operation on Page 92. Rerun link tests. Advantage AP with Canopy SM Monitor the Session Status tab in the Advantage AP. Rerun link tests. Rerun link tests. Uplink and downlink are both 60% Efficiency.2 Uplink and downlink are both 60% Efficiency. Results are inconsistent and range from 20% to 80% Efficiency. Link fluctuates between 2X and 1X operation.3 No substantial improvement with consistency is seen. Uplink and downlink are both 90% Efficiency. Rerun link tests. Optionally, re-aim SM, add a reflector, or otherwise mitigate interference. In any case, continue 2X operation up and down. Monitor the Session Status tab in the Advantage AP. Optionally, re-aim SM, add a reflector, or otherwise mitigate interference. Then rerun link tests. On the General tab of the SM, disable 2X operation. Then rerun link tests. Continue 1X operation up and down. NOTES:

1. Or check Session Status page of the Advantage AP, where a sum of greater than 7,000,000 bps for the up- and downlink indicates 2X operation up and down (for 2.4- or 5.x-GHz modules. 2. For throughput to the SM, this is equivalent to 120% Efficiency in 1X operation, with less capacity used at the AP. 3. This link is problematic. 12.5 CONSIDERINGFREQUENCYBANDALTERNATIVES For 5.2-, 5.4-, and 5.7-GHz modules, 20-MHz wide channels are centered every 5 MHz. For 2.4-GHz modules, 20-MHz wide channels are centered every 2.5 MHz. For Cyclone OFDM, the operator can configure center channel frequencies of the 10 MHz channels with a granularity of 0.5 MHz.This allows the operator to customize the channel layout for interoperability where other Cyclone equipment is collocated. Cross-band deployment of APs and BH is the recommended alternative (for example, a 5.2-GHz AP collocated with 5.7-GHz BH). IMPORTANT!

In all cases, channel center separation between collocated Cyclone FSK modules should be at least 20 MHz for 1X operation and 25 MHz for 2X. For Cyclone OFDM, channel center separation between collocated modules should be at least XX MHz for 1X operation, XX for 2 X operation, and XX for 3X operation. Issue2,November2007 Draft5forRegulatoryReview 136 Release8 12.5.1 900MHzChannels PlanningGuide 900-MHz AP Available Channels A 900-MHz AP can operate with its 8-MHz wide channel centered on any of the following frequencies:

(All Frequencies in MHz) 906 909 912 915 918 922 907 910 913 916 919 923 908 911 914 917 920 924 900-MHz AP Cluster Recommended Channels Three non-overlapping channels are recommended for use in a 900-MHz AP cluster:

(All Frequencies in MHz) 906 924 915 This recommendation allows 9 MHz of separation between channel centers. You can use the Spectrum Analysis feature in an SM, or use a standalone spectrum analyzer, to evaluate the RF environment. In any case, ensure that the 8-MHz wide channels you select do not overlap. 12.5.2 2.4GHzChannels 2.4-GHz BHM and AP Available Channels A 2.4-GHz BHM or AP can operate with its 20-MHz wide channel centered on any of the following channels, which are separated by only 2.5-MHz increments.

(All Frequencies in GHz) 2.4150 2.4275 2.4400 2.4525 2.4175 2.4300 2.4425 2.4550 2.4200 2.4325 2.4450 2.4575 2.4225 2.4350 2.4475 2.4250 2.4375 2.4500 The center channels of adjacent 2.4-GHz APs should be separated by at least 20 MHz. 2.4-GHz AP Cluster Recommended Channels Three non-overlapping channels are recommended for use in a 2.4-GHz AP cluster:

(All Frequencies in GHz) 2.4150 2.4350 2.4575 This recommendation allows 20 MHz of separation between one pair of channels and 22.5 MHz between the other pair. You can use the Spectrum Analysis feature in an SM or BHS, or use a standalone spectrum analyzer, to evaluate the RF environment. Where spectrum analysis identifies risk of interference for any of these channels, you can compromise this recommendation as follows:

Select 2.4375 GHz for the middle channel

Select 2.455 GHz for the top channel

Select 2.4175 GHz for the bottom channel Issue2,November2007 Draft5forRegulatoryReview 137 Release8 PlanningGuide In any case, ensure that your plan allows at least 20 MHz of separation between channels. 12.5.3 5.2GHzChannels Channel selections for the AP in the 5.2-GHz frequency band range depend on whether the AP is deployed in cluster. 5.2-GHz BH and Single AP Available Channels A BH or a single 5.2-GHz AP can operate in the following channels, which are separated by 5-MHz increments.

(All Frequencies in GHz) 5.275 5.290 5.305 5.320 5.280 5.295 5.310 5.325 5.285 5.300 5.315 The center channels of adjacent APs should be separated by at least 20 MHz. However, 25 MHz of separation is advised, especially for Advantage APs to take advantage of 2X operation. 5.2-GHz AP Cluster Recommended Channels Three non-overlapping channels are recommended for use in a 5.2-GHz AP cluster:

(All Frequencies in GHz) 5.325 5.275 5.300 12.5.4 5.4GHzChannels Channel selections for the AP in the 5.4-GHz frequency band range depend on whether the AP is deployed in cluster. 5.4-GHz BH and Single AP Available A BH or single 5.4-GHz AP can operate in the following channels, which are separated by 5-MHz.

(All Frequencies in GHz) 5495 5515 5535 5555 5575 5595 5615 5635 5655 5675 5695 5500 5520 5540 5560 5580 5600 5620 5640 5660 5680 5700 5505 5525 5545 5565 5585 5605 5625 5645 5665 5685 5705 5510 5530 5550 5570 5590 5610 5630 5650 5670 5690 The channels of adjacent APs should be separated by at least 20 MHz, especially for Advantage APs to take advantage of 2X operation. 5.4-GHz AP Cluster Recommended Channels The fully populated cluster requires only three channels, each reused by the module that is mounted 180 opposed. In this frequency band range, the possible sets of three non-

overlapping channels are numerous. As many as 11 non-overlapping 20-MHz wide channels are available for 1X operation. Fewer 25-MHz wide channels are available for 2X operation, where this greater separation is recommended for interference avoidance. Issue2,November2007 Draft5forRegulatoryReview 138 Release8 PlanningGuide 5.4-GHz AP Cluster Limit Case In the limit, the 11 channels could support all of the following, vertically stacked on the same mast:

3 full clusters, each cluster using 3 channels a set of 4 APs, the set using the 2 channels that no AP in any of the 3 full clusters is using IMPORTANT!

Where regulations require you to have Dynamic Frequency Selection (DFS) enabled, analyze the spectrum, then spread your channel selections as evenly as possible throughout this frequency band range, appropriately sharing it with satellite services. 12.5.5 5.4GHzOFDMChannels Channel selections for the Cyclone OFDM AP in the 5.4-GHz frequency band range depend on whether the AP is deployed in cluster. 5.4-GHz BH and Single AP Available OFDM modules are configured by the operator for channels, using the Configuration =>

Custom Frequencies page. The channels of adjacent APs should be separated by at least XX MHz, especially for APs to take advantage of 3X operation. 5.4-GHz AP Cluster Recommended Channels The fully populated cluster may be configured for two or four channels. If configured for two channels, each channel is reused by the module that is mounted 180 opposed. The modules are pre-configured with channels which can be used as a starting point for selecting the two or four for use in a full 4 AP cluster. Issue2,November2007 Draft5forRegulatoryReview 139 Release8 12.5.6 PlanningGuide 5.7GHzChannels Channel selections for the AP in the 5.7-GHz frequency band range depend on whether the AP is deployed in cluster. 5.7-GHz BH and Single AP Available Channels A BH or a single 5.7-GHz AP enabled for frequencies can operate in the following channels, which are separated by 5-MHz increments.

(All Frequencies in GHz) 5.735 5.765 5.795 5.825 5.740 5.770 5.800 5.830 5.745 5.775 5.805 5.835 5.750 5.780 5.810 5.840 5.755 5.785 5.815 5.760 5.790 5.820 The channels of adjacent APs should be separated by at least 20 MHz. However, 25 MHz of separation is advised, especially for Advantage APs to take advantage of 2X operation. 5.7-GHz AP Cluster Recommended Channels Six non-overlapping channels are recommended for use in 5.7-GHz AP clusters:

(All Frequencies in GHz) 5.815 5.735 5.755 5.835 5.775 5.795 The fully populated cluster requires only three channels, each reused by the module that is mounted 180 offset. The six channels above are also used for backhaul point-to-point links. As noted above, a 5.7-GHz AP can operate on a frequency as high as 5.840 GHz. Where engineering plans allow, this frequency can be used to provide an additional 5-MHz separation between AP and BH channels. 12.5.7 ChannelsAvailableforPTP400andPTP600radios Channel selections for radios in the PTP400 and PTP 600 series are quoted in the user guides that are dedicated to those products. However, these units dynamically change channels when the signal substantially degrades. Since the available channels are in the 5.4- and 5.7-GHz frequency band ranges, carefully consider the potential effects of deploying these products into an environment where traffic in this range pre-exists. 12.5.8 ExampleChannelPlansforAPClusters Examples for assignment of frequency channels and sector IDs are provided in the following tables. Each frequency is reused on the sector that is at a 180 offset. The entry in the Symbol column of each table refers to the layout in Figure 32 on Page 143. Issue2,November2007 Draft5forRegulatoryReview 140 Release8 PlanningGuide NOTE:

The operator specifies the sector ID for the module as described under Sector ID on Page 443. Table 31: Example 900-MHz channel assignment by sector Direction of Access Point Sector North (0) Northeast (60) Southeast (120) South (180) Southwest (240) Northwest (300) Frequency 906 MHz 915 MHz 924 MHz 906 MHz 915 MHz 924 MHz Sector ID Symbol 0 1 2 3 4 5 A B C A B C Table 32: Example 2.4-GHz channel assignment by sector Direction of Access Point Sector North (0) Northeast (60) Southeast (120) South (180) Southwest (240) Northwest (300) Frequency 2.4150 GHz 2.4350 GHz 2.4575 GHz 2.4150 GHz 2.4350 GHz 2.4575 GHz Sector ID Symbol 0 1 2 3 4 5 A B C A B C Table 33: Example 5.2-GHz channel assignment by sector Direction of Access Point Sector North (0) Northeast (60) Southeast (120) South (180) Southwest (240) Northwest (300) Frequency 5.275 GHz 5.300 GHz 5.325 GHz 5.275 GHz 5.300 GHz 5.325 GHz Sector ID Symbol 0 1 2 3 4 5 A B C A B C Issue2,November2007 Draft5forRegulatoryReview 141 Release8 PlanningGuide Table 34: Example 5.4-GHz channel assignment by sector Direction of Access Point Sector North (0) Northeast (60) Southeast (120) South (180) Southwest (240) Northwest (300) Frequency 5.580 GHz 5.620 GHz 5.660 GHz 5.580 GHz 5.620 GHz 5.660 GHz Sector ID Symbol 0 1 2 3 4 5 A B C A B C Table 35: Example 5.7-GHz channel assignment by sector Direction of Access Point Sector North (0) Northeast (60) Southeast (120) South (180) Southwest (240) Northwest (300) Frequency 5.735 GHz 5.755 GHz 5.775 GHz 5.735 GHz 5.755 GHz 5.775 GHz Sector ID Symbol 0 1 2 3 4 5 A B C A B C 12.5.9 MultipleAccessPointsClusters When deploying multiple AP clusters in a dense area, consider aligning the clusters as shown in Figure 32. However, this is only a recommendation. An installation may dictate a different pattern of channel assignments. Issue2,November2007 Draft5forRegulatoryReview 142 Release8 A A A A A A C B C B C B B C B C B C C B C B A A A A B C B C PlanningGuide C B C B A A A A B C B C Figure 32: Example layout of 7 Access Point clusters 12.6 SELECTINGSITESFORNETWORKELEMENTS The Cyclone APs must be positioned

with hardware that the wind and ambient vibrations cannot flex or move.

where a tower or rooftop is available or can be erected.

where a grounding system is available.

with lightning arrestors to transport lightning strikes away from equipment.

at a proper height:

higher than the tallest points of objects immediately around them (such as trees, buildings, and tower legs).

at least 2 feet (0.6 meters) below the tallest point on the tower, pole, or roof

(for lightning protection).

away from high-RF energy sites (such as AM or FM stations, high-powered antennas, and live AM radio towers). in line-of-sight paths

to the SMs and BH. that will not be obstructed by trees as they grow or structures that are later built. Issue2,November2007 Draft5forRegulatoryReview 143 Release8 PlanningGuide Visual line of sight does not guarantee radio line of sight. NOTE:

12.6.1 ResourcesforMapsandTopographicImages Mapping software is available from sources such as the following:

http://www.microsoft.com/streets/default.asp

Microsoft Streets & Trips (with Pocket Streets) http://www.delorme.com/software.htm

DeLorme Street Atlas USA

DeLorme Street Atlas USA Plus

DeLorme Street Atlas Handheld Topographic maps are available from sources such as the following:

http://www.delorme.com/software.htm

DeLorme Topo USA

DeLorme 3-D TopoQuads http://www.usgstopomaps.com

Timely Discount Topos, Inc. authorized maps Topographic maps with waypoints are available from sources such as the following:

http://www.topografix.com

TopoGrafix EasyGPS

TopoGrafix Panterra

TopoGrafix ExpertGPS Topographic images are available from sources such as the following:

http://www.keyhole.com/body.php?h=products&t=keyholePro

keyhole PRO http://www.digitalglobe.com

various imagery 12.6.2 SurveyingSites Factors to survey at potential sites include

what pre-existing wireless equipment exists at the site. (Perform spectrum analysis.)

whether available mounting positions exist near the lowest elevation that satisfies line of site, coverage, and other link criteria.

whether you will always have the right to decide who climbs the tower to install and maintain your equipment, and whether that person or company can climb at any hour of any day. Issue2,November2007 Draft5forRegulatoryReview 144 Release8 PlanningGuide

whether you will have collaborative rights and veto power to prevent interference to your equipment from wireless equipment that is installed at the site in the future.

whether a pre-existing grounding system (path to Protective Earth ) exists, and what is required to establish a path to it.

who is permitted to run any indoor lengths of cable. 12.6.3 AssuringtheEssentials In the 2.4-, 5.2-, 5.4-, and 5.7-GHz frequency band ranges, an unobstructed line of sight

(LOS) must exist and be maintainable between the radios that are involved in each link. Line of Sight (LOS) Link In these ranges, a line of sight link is both

an unobstructed straight line from radio to radio. an unobstructed zone surrounding that straight line. Fresnel Zone Clearance An unobstructed line of sight is important, but is not the only determinant of adequate placement. Even where the path has a clear line of sight, obstructions such as terrain, vegetation, metal roofs, or cars may penetrate the Fresnel zone and cause signal loss. Figure 33 illustrates an ideal Fresnel zone. Fresnel zone transmitter Transmitter or Amplifier receiver Figure 33: Fresnel zone FresnelZoneCalcPage.xls calculates the Fresnel zone clearance that is required between the visual line of sight and the top of an obstruction that would protrude into the link path. Non-Line of Sight (NLOS) Link The Cyclone 900-MHz modules have a line of sight (LOS) range of 40 miles (more than 64 km) and greater non-line of sight (NLOS) range than Cyclone modules of other frequency bands. NLOS range depends on RF considerations such as foliage, topography, obstructions. 12.6.4 FindingtheExpectedCoverageArea The transmitted beam in the vertical dimension covers more area beyond than in front of the beam center. BeamwidthRadiiCalcPage.xls calculates the radii of the beam coverage area. Issue2,November2007 Draft5forRegulatoryReview 145 Release8 12.6.5 ClearingtheRadioHorizon PlanningGuide Because the surface of the earth is curved, higher module elevations are required for greater link distances. This effect can be critical to link connectivity in link spans that are greater than 8 miles (12 km). AntennaElevationCalcPage.xls calculates the minimum antenna elevation for these cases, presuming no landscape elevation difference from one end of the link to the other. 12.6.6 CalculatingtheAimAngles The appropriate angle of AP downward tilt is derived from both the distance between transmitter and receiver and the difference in their elevations. DowntiltCalcPage.xls calculates this angle. The proper angle of tilt can be calculated as a factor of both the difference in elevation and the distance that the link spans. Even in this case, a plumb line and a protractor can be helpful to ensure the proper tilt. This tilt is typically minimal. The number of degrees to offset (from vertical) the mounting hardware leg of the support tube is equal to the angle of elevation from the lower module to the higher module (<B in the example provided in Figure 34). LEGEND b B A Angle of elevation. Vertical difference in elevation. Horizontal distance between modules. Figure 34: Variables for calculating angle of elevation (and depression) Calculating the Angle of Elevation To use metric units to find the angle of elevation, use the following formula:

tan b =

B 1000A where B is expressed in meters A is expressed in kilometers. Issue2,November2007 Draft5forRegulatoryReview 146 Release8 PlanningGuide To use English standard units to find the angle of elevation, use the following formula:

tan b =

B 5280A where B is expressed in feet A is expressed in miles. The angle of depression from the higher module is identical to the angle of elevation from the lower module. 12.7 COLLOCATINGCYCLONEMODULES A BH and an AP or AP cluster on the same tower require a CMM. The CMM properly synchronizes the transmit start times of all Cyclone modules to prevent interference and desensing of the modules. At closer distances without sync from a CMM, the frame structures cause self interference. Furthermore, a BH and an AP on the same tower require that the effects of their differing receive start times be mitigated by either 100 vertical feet (30 meters) or more and as much spectral separation as possible within the same frequency band range. the use of the frame calculator to tune the Downlink Data parameter in each, so that the receive start time in each is the same. See Using the Frame Calculator Tool (All) on Page 444. Cyclone APs and a BHS can be collocated at the same site only if they operate in different frequency band ranges. Where a single BH air link is insufficient to cover the distance from an AP cluster to your point of presence (POP), you can deploy two BHSs, connected to one another by Ethernet, on a tower that is between a BHM collocated with the AP cluster and another BHM collocated with the POP. This deployment is illustrated in Figure 35. AP BH

-M-

CMM CMM BH

-S-

BH

-S-

BH

-M-

POP CMM CMM Figure 35: Double-hop backhaul links Issue2,November2007 Draft5forRegulatoryReview 147 Release8 PlanningGuide However, the BHSs can be collocated at the same site only if one is on a different frequency band range from that of the other or one of the following conditions applies:

They are vertically separated on a structure by at least 100 feet (30 m). They are vertically separated on a structure by less distance, but either

an RF shield isolates them from each other.

the uplink and downlink data parameters and control channels match (the Downlink Data parameter is set to 50%). The constraints for collocated modules in the same frequency band range are to avoid self-interference that would occur between them. Specifically, unless the uplink and downlink data percentages match, intervals exist when one is transmitting while the other is receiving, such that the receiving module cannot receive the signal from the far end. The interference is less a problem during low throughput periods and intolerable during high. Typically, during low throughput periods, sufficient time exists for the far end to retransmit packets lost because of interference from the collocated module. 12.8 DEPLOYINGAREMOTEAP In cases where the subscriber population is widely distributed, or conditions such as geography restrict network deployment, you can add a Remote AP to provide high-throughput service to near LoS business subscribers. reach around obstructions or penetrate foliage with non-LoS throughput. reach new, especially widely distributed, residential subscribers with broadband service. pass sync to an additional RF hop. In the remote AP configuration, a Cyclone AP is collocated with a Canopy SM. The remote AP distributes the signal over the last mile to SMs that are logically behind the collocated SM. A remote AP deployment is illustrated in Figure 36. AP AP C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y Canopy Canopy SM SM C A N O P Y C A N O P Y C A N O P Y Canopy Canopy SM with SM with Remote AP Remote AP C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y Canopy Canopy SM SM C A N O P Y C A N O P Y C A N O P Y Figure 36: Remote AP deployment Canopy Canopy SM SM C A N O P Y C A N O P Y C A N O P Y Issue2,November2007 Draft5forRegulatoryReview 148 Release8 PlanningGuide The collocated SM receives data in one frequency band, and the remote AP must redistribute the data in a different frequency band. Base your selection of frequency band ranges on regulatory restrictions, environmental conditions, and throughput requirements. IMPORTANT!

Each relay hop (additional daisy-chained remote AP) adds latency to the link as follows:

approximately 6 msec where hardware scheduling is enabled. approximately 15 msec where software scheduling is enabled. 12.8.1 RemoteAPPerformance The performance of a remote AP is identical to the AP performance in cluster. Throughputs, ranges, and patch antenna coverage are identical. Cyclone Advantage and Cyclone modules can be deployed in tandem in the same sector to meet customer bandwidth demands. As with all equipment operating in the unlicensed spectrum, Last Mile Gear strongly recommends that you perform site surveys before you add network elements. These will indicate that spectrum is available in the area where you want to grow. Keep in mind that non-LoS ranges heavily depend on environmental conditions. in most regions, not all frequencies are available. your deployments must be consistent with local regulatory restrictions. 12.8.2 ExampleUseCaseforRFObstructions A remote AP can be used to provide last-mile access to a community where RF obstructions prevent SMs from communicating with the higher-level AP in cluster. For example, you may be able to use 900 MHz for the last mile between a remote AP and the outlying SMs where these subscribers cannot form good links to a higher-level 2.4-GHz AP. In this case, the short range of the 900-MHz remote AP is sufficient, and the ability of the 900-MHz wavelength to be effective around foliage at short range solves the foliage penetration problem. An example of this use case is shown in Figure 37. Issue2,November2007 Draft5forRegulatoryReview 149 Release8 2.4 GHz AP 2.4 GHz AP C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y PlanningGuide 2.4 GHz SM 2.4 GHz SM C A N O P Y C A N O P Y C A N O P Y 2.4 GHz SM 2.4 GHz SM with with Remote 900 MHz AP Remote 900 MHz AP C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y 900 MHz SM 900 MHz SM 900 MHz SM 900 MHz SM C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y C A N O P Y 900 MHz SM 900 MHz SM C A N O P Y C A N O P Y C A N O P Y 900 MHz SM 900 MHz SM C A N O P Y C A N O P Y C A N O P Y 14 Mbps Maximum Aggregate Throughput 14 Mbps Maximum Aggregate Throughput LoS Range 2.5 miles LoS Range 2.5 miles 7 Mbps Maximum Aggregate Throughput 7 Mbps Maximum Aggregate Throughput LoS Range 5 miles LoS Range 5 miles 4 Mbps Maximum Throughput 4 Mbps Maximum Throughput NLoS Range ~2 miles NLoS Range ~2 miles 2 Mbps Maximum Throughput NLoS 2 Mbps Maximum Throughput NLoS Range ~4 miles Range ~4 miles 4 Mbps Maximum Throughput 4 Mbps Maximum Throughput LoS Range 20 miles LoS Range 20 miles 2 Mbps Maximum Throughput 2 Mbps Maximum Throughput LoS Range 40 miles LoS Range 40 miles Figure 37: Example 900-MHz remote AP behind 2.4-GHz SM The 2.4 GHz modules provide a sustained aggregate throughput of up to 14 Mbps to the sector. One of the SMs in the sector is wired to a 900-MHz remote AP, which provides NLoS sustained aggregate throughput4 of 4 Mbps to 900-MHz SMs up to 2 miles away in the sector. 2 Mbps to 900-MHz SMs between 2 and 4 miles away in the sector. 12.8.3 ExampleUseCaseforPassingSync All Cyclone radios support the remote AP functionality. The BHS and the SM can reliably pass the sync pulse, and the BHM and AP can reliably receive it. Examples of passing sync over cable are shown under Passing Sync in an Additional Hop on Page 95. The sync cable is described under Cables on Page 57. 4 NLoS ranges depend on environmental conditions. Your results may vary from these. Issue2,November2007 Draft5forRegulatoryReview 150

 

 

Release8 PlanningGuide The sync is passed in a cable that connects Pins 1 and 6 of the RJ-11 timing ports of the two modules. When you connect modules in this way, you must also adjust configuration parameters to ensure that the AP is set to properly receive sync. the SM will not propagate sync to the AP if the SM itself ceases to receive sync. Perform Procedure 35: Extending network sync on Page 374. 12.8.4 PhysicalConnectionsInvolvingtheRemoteAP The SM to which you wire a remote AP can be either an SM that serves a customer or an SM that simply serves as a relay. Where the SM serves a customer, wire the remote AP to the SM as shown in Figure 38. Figure 38: Remote AP wired to SM that also serves a customer Where the SM simply serves as a relay, you must use a straight-through RJ-45 female-to-female coupler, and wire the SM to the remote AP as shown in Figure 39. Issue2,November2007 Draft5forRegulatoryReview 151 Release8 PlanningGuide Figure 39: Remote AP wired to SM that serves as a relay 12.9 DIAGRAMMINGNETWORKLAYOUTS 12.9.1 AccountingforLinkRangesandDataHandlingRequirements For aggregate throughput correlation to link distance in both point-to-multipoint and point-to-point links, see Link Performance and Encryption Comparisons on Page 61. all regulations that apply in your region and nation(s). 12.9.2 AvoidingSelfInterference For 5.2-, 5.4-, and 5.7-GHz modules, 20-MHz wide channels are centered every 5 MHz. For 2.4-GHz modules, 20-MHz wide channels are centered every 2.5 MHz. For 5.4-GHz OFDM modules, 10-MHz wide channels can be centered every 0.5 MHz. This allows you to customize the channel layout for interoperability where other Cyclone equipment is collocated, as well as select channels with the least background interference level. CAUTION!

Regardless of whether 2.4-, 5.2-, 5.4-, or 5.7-GHz modules are deployed, channel separation between modules should be at least 20 MHz for 1X operation or 25 MHz for 2X. Physical Proximity A BH and an AP on the same tower require a CMM. The CMM properly synchronizes the transmit start times of all Cyclone modules to prevent interference and desensing of the modules. At closer distances without sync from a CMM, the frame structures cause self interference. Issue2,November2007 Draft5forRegulatoryReview 152 Release8 PlanningGuide Furthermore, a BH and an AP on the same tower require that the effects of their differing receive start times be mitigated by either 100 vertical feet (30 meters) or more and as much spectral separation as possible within the same frequency band range. the use of the frame calculator to tune the Downlink Data % parameter in each, so that the receive start time in each is the same. See Using the Frame Calculator Tool (All) on Page 444. Spectrum Analysis (Not available on Cyclone OFDM modules) You can use an SM or BHS as a spectrum analyzer. See Mapping RF Neighbor Frequencies on Page 131. Through a toggle of the Device Type parameter, you can temporarily transform an AP into an SM to use it as a spectrum analyzer. Power Reduction to Mitigate Interference Where any module (SM, AP, BH timing master, or BH timing slave) is close enough to another module that self-interference is possible, you can set the SM to operate at less than full power. To do so, perform the following steps. CAUTION!

Too low a setting of the Transmitter Output Power parameter can cause a link to a distant module to drop. A link that drops for this reason requires Ethernet access to the GUI to re-establish the link. Procedure 3: Reducing transmitter output power In the Transmitter Output Power parameter, reduce the setting. 1. Access the Radio tab of the module. 2. 3. Click Save Changes. 4. Click Reboot. 5. Access the Session Status tab in the Home web page of the SM. 6. Assess whether the link achieves good Power Level and Jitter values. NOTE: The received Power Level is shown in dBm and should be maximized. Jitter should be minimized. However, better/lower jitter should be favored over better/higher dBm. For historical reasons, RSSI is also shown and is the unitless measure of power. The best practice is to use Power Level and ignore RSSI, which implies more accuracy and precision than is inherent in its measurement. 7. Access the Link Capacity Test tab in the Tools web page of the module. 8. Assess whether the desired links for this module achieve 9. uplink efficiency greater than 90%. downlink efficiency greater than 90%.

If the desired links fail to achieve any of the above measurement thresholds, then a. access the module by direct Ethernet connection. b. access the Radio tab in the Configuration web page of the module. in the Transmitter Output Power parameter, increase the setting. c. Issue2,November2007 Draft5forRegulatoryReview 153 Release8 PlanningGuide d. click Save Changes. e. click Reboot. end of procedure 12.9.3 AvoidingOtherInterference Where signal strength cannot dominate noise levels, the network experiences

bit error corrections. packet errors and retransmissions. lower throughput (because bandwidth is consumed by retransmissions) and high latency (due to resends). Be especially cognitive of these symptoms for 900-MHz links. Where you see these symptoms, attempt the following remedies:

Adjust the position of the SM.

Deploy a band-pass filter at the AP.

Consider adding a remote AP closer to the affected SMs. (See Deploying a Remote AP on Page 148.) Certain other actions, which may seem to be potential remedies, do not resolve high noise level problems:

Do not deploy an omnidirectional antenna.

Do not set the antenna gain above the regulated level.

Do not deploy a band-pass filter in the expectation that this can mitigate co-

channel interference. Issue2,November2007 Draft5forRegulatoryReview 154 Release8 13 ENGINEERINGYOURIPCOMMUNICATIONS PlanningGuide 13.1 UNDERSTANDINGADDRESSES A basic understanding of Internet Protocol (IP) address and subnet mask concepts is required for engineering your IP network. 13.1.1 IPAddress The IP address is a 32-bit binary number that has four parts (octets). This set of four octets has two segments, depending on the class of IP address. The first segment identifies the network. The second identifies the hosts or devices on the network. The subnet mask marks a boundary between these two sub-addresses. 13.2 DYNAMICORSTATICADDRESSING For any computer to communicate with a Cyclone module, the computer must be configured to either use DHCP (Dynamic Host Configuration Protocol). In this case, when not connected to the network, the computer derives an IP address on the 169.254 network within two minutes. have an assigned static IP address (for example, 169.254.1.5) on the 169.254 network. IMPORTANT!

If an IP address that is set in the module is not the 169.254.x.x network address, then the network operator must assign the computer a static IP address in the same subnet.

13.2.1 WhenaDHCPServerisNotFound To operate on a network, a computer requires an IP address, a subnet mask, and possibly a gateway address. Either a DHCP server automatically assigns this configuration information to a computer on a network or an operator must input these items. When a computer is brought on line and a DHCP server is not accessible (such as when the server is down or the computer is not plugged into the network), Microsoft and Apple operating systems default to an IP address of 169.254.x.x and a subnet mask of 255.255.0.0 (169.254/16, where /16 indicates that the first 16 bits of the address range are identical among all members of the subnet). Issue2,November2007 Draft5forRegulatoryReview 155 Release8 13.3 PlanningGuide NETWORKADDRESSTRANSLATION(NAT) 13.3.1 NAT,DHCPServer,DHCPClient,andDMZinSM The Cyclone system provides NAT (network address translation) for SMs in the following combinations of NAT and DHCP (Dynamic Host Configuration Protocol):

NAT Disabled (as in earlier releases)

NAT with DHCP Client and DHCP Server

NAT with DHCP Client

NAT with DHCP Server

NAT without DHCP NAT NAT isolates devices connected to the Ethernet/wired side of an SM from being seen directly from the wireless side of the SM. With NAT enabled, the SM has an IP address for transport traffic (separate from its address for management), terminates transport traffic, and allows you to assign a range of IP addresses to devices that are connected to the Ethernet/wired side of the SM. In the Cyclone system, NAT supports many protocols, including HTTP, ICMP (Internet Control Message Protocols), and FTP (File Transfer Protocol). For virtual private network

(VPN) implementation, L2TP over IPSec (Level 2 Tunneling Protocol over IP Security) is supported, but PPTP (Point to Point Tunneling Protocol) is not supported. See NAT and VPNs on Page 161. DHCP DHCP enables a device to be assigned a new IP address and TCP/IP parameters, including a default gateway, whenever the device reboots. Thus DHCP reduces configuration time, conserves IP addresses, and allows modules to be moved to a different network within the Cyclone system. In conjunction with the NAT features, each SM provides

a DHCP server that assigns IP addresses to computers connected to the SM by Ethernet protocol. a DHCP client that receives an IP address for the SM from a network DHCP server. DMZ In conjunction with the NAT features, a DMZ (demilitarized zone) allows the assignment of one IP address behind the SM for a device to logically exist outside the firewall and receive network traffic. The first three octets of this IP address must be identical to the first three octets of the NAT private IP address. Issue2,November2007 Draft5forRegulatoryReview 156 Release8 PlanningGuide NAT Disabled The NAT Disabled implementation is illustrated in Figure 40. Figure 40: NAT Disabled implementation Issue2,November2007 Draft5forRegulatoryReview 157 Release8 PlanningGuide NAT with DHCP Client and DHCP Server The NAT with DHCP Client and DHCP Server implementation is illustrated in Figure 41. Figure 41: NAT with DHCP Client and DHCP Server implementation Issue2,November2007 Draft5forRegulatoryReview 158 Release8 PlanningGuide NAT with DHCP Client The NAT with DHCP Client implementation is illustrated in Figure 42. Figure 42: NAT with DHCP Client implementation Issue2,November2007 Draft5forRegulatoryReview 159 Release8 PlanningGuide NAT with DHCP Server The NAT with DHCP Server implementation is illustrated in Figure 43. Figure 43: NAT with DHCP Server implementation Issue2,November2007 Draft5forRegulatoryReview 160 Release8 NAT without DHCP The NAT without DHCP implementation is illustrated in Figure 44. PlanningGuide Figure 44: NAT without DHCP implementation 13.3.2 NATandVPNs VPN technology provides the benefits of a private network during communication over a public network. One typical use of a VPN is to connect remote employees, who are at home or in a different city, to their corporate network over the public Internet. Any of several VPN implementation schemes is possible. By design, NAT translates or changes addresses, and thus interferes with a VPN that is not specifically supported by a given NAT implementation. With NAT enabled, SMs support L2TP over IPSec (Level 2 Tunneling Protocol over IP Security) VPNs, but do not support PPTP (Point to Point Tunneling Protocol) VPNs. With NAT disabled, SMs support all types of VPNs. Issue2,November2007 Draft5forRegulatoryReview 161 Release8 13.4 DEVELOPINGANIPADDRESSINGSCHEME PlanningGuide Cyclone network elements are accessed through IP Version 4 (IPv4) addressing. A proper IP addressing method is critical to the operation and security of a Cyclone network. Each Cyclone module requires an IP address on the network. This IP address is for only management purposes. For security, you should either

assign an unroutable IP address. assign a routable IP address only if a firewall is present to protect the module. You will assign IP addresses to computers and network components by either static or dynamic IP addressing. You will also assign the appropriate subnet mask and network gateway to each module. 13.4.1 AddressResolutionProtocol As previously stated, the MAC address identifies a Cyclone module in

communications between modules. the data that modules store about each other. the data that BAM or Prizm applies to manage authentication and bandwidth. The IP address is essential for data delivery through a router interface. Address Resolution Protocol (ARP) correlates MAC addresses to IP addresses. For communications to outside the network segment, ARP reads the network gateway address of the router and translates it into the MAC address of the router. Then the communication is sent to MAC address (physical network interface card) of the router. For each router between the sending module and the destination, this sequence applies. The ARP correlation is stored until the ARP cache times out. 13.4.2 AllocatingSubnets The subnet mask is a 32-bit binary number that filters the IP address. Where a subnet mask contains a bit set to 1, the corresponding bit in the IP address is part of the network address. Example IP Address and Subnet Mask In Figure 45, the first 16 bits of the 32-bit IP address identify the network:

Octet 1 Octet 4 IP address 169.254.1.1 10101001 11111110 00000001 00000001 Subnet mask 255.255.0.0 11111111 11111111 00000000 00000000 Octet 2 Octet 3 Figure 45: Example of IP address in Class B subnet In this example, the network address is 169.254, and 216 (65,536) hosts are addressable. Issue2,November2007 Draft5forRegulatoryReview 162 Release8 13.4.3 SelectingNonroutableIPAddresses PlanningGuide The factory default assignments for Cyclone network elements are

unique MAC address IP address of 169.254.1.1, except for an OFDM series BHM, whose IP address is 169.254.1.2 by default subnet mask of 255.255.0.0 network gateway address of 169.254.0.0 For each Cyclone radio and CMMmicro, assign an IP address that is both consistent with the IP addressing plan for your network and cannot be accessed from the Internet. IP addresses within the following ranges are not routable from the Internet, regardless of whether a firewall is configured:

10.0.0.0 10.255.255.255 172.16.0.0 172.31.255.255 192.168.0.0 192.168.255.255 You can also assign a subnet mask and network gateway for each CMMmicro. Issue2,November2007 Draft5forRegulatoryReview 163 Release8 14 ENGINEERINGVLANS PlanningGuide Cyclone radios support VLAN functionality as defined in the 802.1Q (Virtual LANs) specification, except for the following aspects of that specification:

the following protocols:

Generic Attribute Registration Protocol (GARP) GARV

Spanning Tree Protocol (STP)

Multiple Spanning Tree Protocol (MSTP)

GARP Multicast Registration Protocol (GMRP) priority encoding (802.1P) before Release 7.0 embedded source routing (ERIF) in the 802.1Q header

multicast pruning

flooding unknown unicast frames in the downlink As an additional exception, the Cyclone AP does not flood downward the unknown unicast frames to the Canopy SM. A VLAN configuration in Layer 2 establishes a logical group within the network. Each computer in the VLAN, regardless of initial or eventual physical location, has access to the same data. For the network operator, this provides flexibility in network segmentation, simpler management, and enhanced security. 14.1 SMMEMBERSHIPINVLANS With the supported VLAN functionality, Cyclone radios determine bridge forwarding on the basis of not only the destination MAC address, but also the VLAN ID of the destination. This provides flexibility in how SMs are used:

Each SM can be a member in its own VLAN.

Each SM can be in its own broadcast domain, such that only the radios that are members of the VLAN can see broadcast and multicast traffic to and from the SM.

The network operator can define a work group of SMs, regardless of the AP(s) to which they register. Cyclone point-to-multipoint modules provide the VLAN frame filters that are described in Table 36. Issue2,November2007 Draft5forRegulatoryReview 165 Release8 PlanningGuide Table 36: VLAN filters in point-to-multipoint modules Where VLAN is active, if this parameter value is selected any combination of VLAN parameter settings any combination of VLAN parameter settings Allow Frame Types:

Tagged Frames Only Allow Frame Types:

Untagged Frames Only Local SM Management:

Disable in the SM, or All Local SM Management:

Disable in the AP any combination of VLAN parameter settings any combination of VLAN parameter settings then a frame is discarded if entering the bridge/

NAT switch through Ethernet with a VID not in the membership table TCP/IP because of this VLAN filter in the Cyclone software:

Ingress with a VID not in the membership table Local Ingress with no 802.1Q tag with an 802.1Q tag, regardless of VID with an 802.1Q tag and a VID in the membership table Only Tagged Only Untagged Local SM Management leaving the bridge/

NAT switch through Ethernet with a VID not in the membership table TCP/IP Egress with a VID not in the membership table Local Egress 14.2 PRIORITYONVLANS(802.1p) Cyclone radios can prioritize traffic based on the eight priorities described in the IEEE 802.1p specification. When the high-priority channel is enabled on an SM, regardless of whether VLAN is enabled on the AP for the sector, packets received with a priority of 4 through 7 in the 802.1p field are forwarded onto the high-priority channel. VLAN settings in a Cyclone module can also cause the module to convert received non-

VLAN packets into VLAN packets. In this case, the 802.1p priority in packets leaving the module is set to the priority established by the DiffServ configuration. If you enable VLAN, immediately monitor traffic to ensure that the results are as desired. For example, high-priority traffic may block low-priority. For more information on the Cyclone high priority channel, see High-priority Bandwidth on Page 86. Issue2,November2007 Draft5forRegulatoryReview 166 Release8 InstallationandConfigurationGuide IIINNNSSSTTTAAALLLLLLAAATTTIIIOOONNNAAANNNDDD CCCOOONNNFFFIIIGGGUUURRRAAATTTIIIOOONNN GGGUUUIIIDDDEEE Issue2,November2007 Draft5forRegulatoryReview 167 Release8 15 AVOIDINGHAZARDS InstallationandConfigurationGuide Use simple precautions to protect staff and equipment. Hazards include exposure to RF waves, lightning strikes, and power surges. This section specifically recommends actions to abate these hazards. 15.1 EXPOSURESEPARATIONDISTANCES To protect from overexposure to RF energy, install Cyclone radios so as to provide and maintain the minimum separation distances from all persons shown in Table 37. Table 37: Exposure separation distances Module Type Cyclone Module, FSK or OFDM Cyclone Module with Reflector Dish Cyclone Module with LENS Antenna of connectorized 5.7 GHz AP Antenna of connectorized or integrated 900 MHz module Indoor 900 MHz SM Separation Distance from Persons At least 20 cm (approx 8 in) At least 1.5 m (approx 60 in or 5 ft) At least 0.5 m (approx 20 in) At least 30 cm (approx 12 in) At least 60 sm (24 in) At least 10 cm (4 in) Section 15.1.1 and Table 38 give details and discussion of the associated calculations. 15.1.1 DetailsofExposureSeparationDistancesCalculationsandPowerCompliance Margins Limits and guidelines for RF exposure come from:

US FCC limits for the general population. See the FCC web site at http://www.fcc.gov, and the policies, guidelines, and requirements in Part 1 of Title 47 of the Code of Federal Regulations, as well as the guidelines and suggestions for evaluating compliance in FCC OET Bulletin 65. Health Canada limits for the general population. See the Health Canada web site at http://www.hc-sc.gc.ca/rpb and Safety Code 6. ICNIRP (International Commission on Non-Ionizing Radiation Protection) guidelines for the general public. See the ICNIRP web site at http://www.icnirp.de/ and Guidelines for Limiting Exposure to Time-Varying Electric, Magnetic, and Electromagnetic Fields. The applicable power density exposure limits from the documents referenced above are 6 W/m2 for RF energy in the 900-MHz frequency band in the US and Canada. 10 W/m2 for RF energy in the 2.4-, 5.2-, 5.4-, and 5.7-GHz frequency bands. Peak power density in the far field of a radio frequency point source is calculated as follows:

Issue2,November2007 Draft5forRegulatoryReview 169 Release8 S =

P G 4d 2 InstallationandConfigurationGuide where S = power density in W/m2 P = RMS transmit power capability of the radio, in W G = total Tx gain as a factor, converted from dB d = distance from point source, in m Rearranging terms to solve for distance yields d =

P G 4S Table 38 shows calculated minimum separation distances d, recommended distances and resulting power compliance margins for each frequency band and antenna combination. Table 38: Calculated exposure distances and power compliance margins Fre-

quency Band Antenna Variable P G S d

(calcu-

lated) 900 MHz 2.4 GHz 5.2 GHz 5.4 GHz external integrated 0.4 W

(26 dBm) 10.0

(10 dB) 0.25 W

(24 dBm) 15.8

(12 dB) 6 W/m2 23 cm 6 W/m2 23 cm indoor, integrated Simulation model used to estimate Specific Absorption Rate (SAR) levels integrated 0.34 W

(25 dBm) 6.3

(8 dB) integrated plus reflector 0.34 W

(25 dBm) 79.4

(19 dB) integrated 0.2 W

(23 dBm) 5.0

(7 dB) integrated plus reflector integrated plus LENS integrated integrated plus reflector integrated plus LENS 0.0032 W

(5 dBm) 316

(25 dB) 0.025 W

(14 dBm) 0.2 W

(23 dBm) 40

(16 dB) 5.0

(7 dB) 0.0032 W

(5 dBm) 316

(25 dB) 0.020 W

(13 dBm) 0.01 W

(10 dBm) 50

(17 dB) 50

(17 db) 10 W/m2 10 W/m2 10 W/m2 10 W/m2 10 W/m2 10 W/m2 10 W/m2 10 W/m2 10 W/m2 13 cm 46 cm 9 cm 9 cm 9 cm 9 cm 9 cm 9 cm 6 cm 5.4 GHz OFDM integrated Recom-

mended Separation Distance 60 cm

(24 in) 60 cm

(24 in) 10 cm

(4 in) 20 cm

(8 in) 1.5 m

(5 ft) 20 cm

(8 in) 1.5 m

(5 ft) 50 cm

(12 in) 20 cm

(8 in) 1.5 m

(5 ft) 50 cm

(12 in) 20 cm

(8 in) Power Compliance Margin 7 7 2 2.3 10 5 279 31 5 279 31 10 Issue2,November2007 Draft5forRegulatoryReview 170 Release8 InstallationandConfigurationGuide Fre-

quency Band Antenna Variable P G S integrated 0.2 W

(23 dBm) 5.0

(7 dB) integrated plus reflector Integrated plus LENS 0.2 W

(23 dBm) 316

(25 dB) 0.2 W

(23 dBm) 50

(17 dB) 10 W/m2 10 W/m2 1 W/m2 5.7 GHz d

(calcu-

lated) 9 cm 71 cm 28 cm Recom-

mended Separation Distance 20 cm

(8 in) 1.5 m

(5 ft) 50 cm

(12 in) Power Compliance Margin 5 4.5 3.13 The Recommended Distances are chosen to give significant compliance margin in all cases. They are also chosen so that a given item (bare module, reflector, or LENS) always has the same distance, regardless of frequency band, to simplify following exposure distances in the field. These are conservative distances:

They are along the beam direction (the direction of greatest energy). Exposure to the sides and back of the module will be significantly less. They meet sustained exposure limits for the general population (not just short term occupational exposure limits), with considerable margin. In the reflector cases, the calculated compliance distance d is greatly overestimated because the far-field equation models the reflector as a point source and neglects the physical dimension of the reflector. 15.2 GROUNDINGCYCLONEEQUIPMENT Effective lightning protection diverts lightning current safely to ground, Protective Earth

(PE)

. It neither attracts nor prevents lightning strikes. WARNING!

Lightning damage is not covered under the Cyclone warranty. The recommendations in Cyclone guides give the installer the knowledge to protect the installation from the harmful effects of ESD and lightning. These recommendation must be thoroughly and correctly performed. However, complete protection is neither implied or possible. 15.2.1 GroundingInfrastructureEquipment To protect both your staff and your infrastructure equipment, implement lightning protection as follows:

Observe all local and national codes that apply to grounding for lightning protection.

Before you install your Cyclone modules, perform the following steps:

Engage a grounding professional if you need to do so. Issue2,November2007 Draft5forRegulatoryReview 171 Release8 InstallationandConfigurationGuide

Install lightning arrestors to transport lightning strikes away from equipment. For example, install a lightning rod on a tower leg other than the leg to which you mount your module.

Connect your lightning rod to ground.

Use a Cyclone 600SS Surge Suppressor on the Ethernet cable where the cable enters any structure. (Instructions for installing a Cyclone 600SS Surge Suppressor are provided in Procedure 28 on Page 349.)

Install your modules at least 2 feet (0.6 meters) below the tallest point on the tower, pole, or roof. 15.2.2 GroundingSMs This section provides lightning protection guidelines for SMs to satisfy the National Electrical Code (NEC) of the United States. The requirements of the NEC focus on the safety aspects of electrical shock to personnel and on minimizing the risk of fire at a dwelling. The NEC does not address the survivability of electronic products that are exposed to lightning surges. The statistical incidence of current levels from lightning strikes is summarized in Table 39. Table 39: Statistical incidence of current from lightning strikes Percentage of all strikes

<2 25

>50

>80 Peak Current

(amps)

>140,000

>35,000

>20,000

>8,500 At peak, more than one-half of all surges due to direct lightning strikes exceed 20,000 amps. However, only one-quarter exceed 35,000 amps, and less than two percent exceed 140,000 amps. Thus, the recommended Surge Suppressor (300SS) provides a degree of lightning protection to electronic devices inside a dwelling. Summary of Grounding Recommendations Last Mile Gear recommends that you ground each SM as follows:

Extend the SM mounting bracket extend to the top of the SM or higher. Ground the SM mounting bracket via a 10-AWG (6 mm2) copper wire connected by the most direct path either to an eight foot-deep ground rod or to the ground bonding point of the AC power service utility entry. This provides the best assurance that

your grounding system complies with NEC 810-15. lightning takes the ground wire route the ground wire does not fuse open Ground the Cyclone Surge Suppressor 300SS or 600SS ground lug to the same ground bonding point as above, using at least a 10-AWG (6 mm2) copper wire. This provides the best assurance that your grounding system complies with NEC 810-21. Issue2,November2007 Draft5forRegulatoryReview 172 Release8 InstallationandConfigurationGuide Grounding Scheme The proper overall antenna grounding scheme per the NEC is illustrated in Figure 128 on Page 350. In most television antenna or dish installations, a coaxial cable connects the outdoor electronics with the indoor electronics. To meet NEC 810-20, one typically uses a coaxial cable feed-through block that connects the outdoor coax to the indoor coax and also has a screw for attaching a ground wire. This effectively grounds the outer shield of the coax. The block should be mounted on the outside of the building near the AC main panel such that the ground wire of the block can be bonded to the primary grounding electrode system of the structure. For residential installs, in most cases an outdoor rated unshielded twisted pair (UTP) cable is sufficient. To comply with the NEC, Last Mile Gear provides the antenna discharge unit, 300SS or 600SS, for each conductor of the cable. The surge suppressor must be positioned

outside the building.

as near as practicable to the power service entry panel of the building and attached to the AC main power ground electrode, or attached to a grounded water pipe.5 far from combustible material.

grounded in accordance with NEC 810-21, with the grounding wire attached to the screw terminal. The metal structural elements of the antenna mast also require a separate grounding conductor. Section 810-15 of the NEC states:

Masts and metal structures supporting antennas shall be grounded in accordance with Section 810-21. As shown in Figure 128 on Page 350, the Last Mile Gear recommendation for grounding the metal structural element of the Cyclone mounting bracket (SMMB1) is to route the grounding wire from the SMMB1 down to the same ground attachment point as is used for the 300SS discharge unit. Use 10-AWG (6 mm2) Copper Grounding Wire According to NEC 810-21 3(h), either a 16-AWG copper clad steel wire or a 10-AWG copper wire may be used. This specification appears to be based on mechanical strength considerations and not on lightning current handling capabilities. For example, analysis shows that the two wire types are not equivalent when carrying a lightning surge that has a 1-microsecond rise by 65-microsecond fall:

The 16-AWG copper clad steel wire has a peak fusing current of 35,000 amps and can carry 21,000 amps peak, at a temperature just below the ignition point for paper (454 F or 234 C). The 10-AWG copper wire has a peak fusing current of 220,000 amps and can carry 133,000 amps peak, at the same temperature. 5 It is insufficient to merely use the green wire ground in a duplex electrical outlet box for grounding of the antenna discharge unit. Issue2,November2007 Draft5forRegulatoryReview 173 Release8 InstallationandConfigurationGuide Based on the electrical/thermal analysis of these wires, Last Mile Gear recommends 10-

AWG copper wire for all grounding conductors. Although roughly double the cost of 16-

AWG copper clad steel wire, 10-AWG copper wire handles six times the surge current from lightning. Shielding is not Grounding In part, NEC 810-21 states:

A lightning arrester is not required if the lead-in conductors are enclosed in a continuous metal shield, such as rigid or intermediate metal conduit, electrical metallic tubing, or any metal raceway or metal-shielded cable that is effectively grounded. A lightning discharge will take the path of lower impedance and jump from the lead-in conductors to the metal raceway or shield rather than take the path through the antenna coil of the receiver. However, Last Mile Gear does not recommend relying on shielded twisted pair cable for lightning protection for the following reasons:

Braid-shielded 10Base-T cable is uncommon, if existent, and may be unsuitable anyway. At a cost of about two-thirds more than 10-AWG copper UTP, CAT 5 100Base-TX foil-shielded twisted pair (FTP) cable provides a 24-AWG drain wire. If this wire melts open during a lightning surge, then the current may follow the twisted pair into the building. More than 80 percent of all direct lightning strikes have current that exceeds 8,500 amps (see Table 39 on Page 172). A 24-AWG copper wire melts open at 8,500 amps from a surge that has a 1-microsecond by 70-microsecond waveform. Hence, reliance on 24-AWG drain wire to comply with the intent of NEC 810-21 is questionable. Shielded twisted pair cable may be useful for mitigation of interference in some circumstances, but installing surge suppressors and implementing the ground recommendations constitute the most effective mitigation against lightning damage. NEC Reference NEC Article 810, Radio and Television Equipment, and associated documents and discussions are available from http://www.neccode.com/index.php?id=homegeneral, http://www.constructionbook.com/xq/ASP/national-electrical-code-2005/id.370/subID.746/qx/default2.htm, and other sources. 15.3 CONFORMINGTOREGULATIONS For all electrical purposes, ensure that your network conforms to applicable country and local codes, such as the NEC (National Electrical Code) in the US. If you are uncertain of code requirements, engage the services of a licensed electrician. 15.4 PROTECTINGCABLESANDCONNECTIONS Cables that move in the wind can be damaged, impart vibrations to the connected device, or both. At installation time, prevent these problems by securing all cables with cable ties, cleats, or PVC tape. Issue2,November2007 Draft5forRegulatoryReview 174 Release8 InstallationandConfigurationGuide Over time, moisture can cause a cable connector to fail. You can prevent this problem by

using cables that are filled with a dielectric gel or grease. including a drip loop where the cable approach to the module (typically a CMM2 or CMMmicro) is from above.

wrapping the cable with weather-resistant tape. On a module with an external antenna, use accepted industry practices to wrap the connector to prevent water ingress. Although the male and female N-type connectors form a gas-tight seal with each other, the point where the cable enters each connector can allow water ingress and eventual corrosion. Wrapping and sealing is critical to long-

term reliability of the connection. Possible sources of material to seal that point include

the antenna manufacturer (material may have been provided in the package with the antenna).

Universal Electronics (whose web site is http://www.coaxseal.com), who markets a weather-tight wrap named Coax-Seal. Perform the following steps to wrap the cable. Procedure 4: Wrapping the cable 1. Start the wrap on the cable 0.5 to 2 inches (about 1.5 to 5 cm) from the connection. 2. Wrap the cable to a point 0.5 to 2 inches (about 1.5 to 5 cm) above the connection. 3. Squeeze the wrap to compress and remove any trapped air. 4. Wrap premium vinyl electrical tape over the first wrap where desired for abrasion resistance or appearance. 5. Tie the cable to minimize sway from wind. end of procedure Issue2,November2007 Draft5forRegulatoryReview 175 Release8 16 TESTINGTHECOMPONENTS InstallationandConfigurationGuide The best practice is to connect all componentsBHs, APs, GPS antenna, and CMM2 or CMMmicroin a test setting and initially configure and verify them before deploying them to an installation. In this way, any configuration issues are worked out before going on-

site, on a tower, in the weather, where the discovery of configuration issues or marginal hardware is more problematic and work-flow affecting. 16.1 UNPACKINGCOMPONENTS When you receive Cyclone products, carefully inspect all shipping boxes for signs of damage. If you find damage, immediately notify the transportation company. As you unpack the equipment, verify that all the components that you ordered have arrived. Save all the packing materials to use later, as you transport the equipment to and from installation sites. 16.2 CONFIGURINGFORTEST You can use either of two methods to configure an AP or BHM:

Use the Quick Start feature of the product. For more information on Quick Start, see Quick Start Page of the AP on Page 185.

Manually set each parameter. After you change configuration parameters on a GUI web page:

1. Before you leave a web page, click the Save button to save the change(s). 2. After making change(s) on multiple web pages, click the Reboot button to reboot the module and implement the change(s). 16.2.1 ConfiguringtheComputingDeviceforTest If your computer is configured for Dynamic Host Configuration Protocol (DHCP), disconnect the computer from the network. If your computer is instead configured for static IP addressing

set the static address in the 169.254 network set the subnet mask to 255.255.0.0. Issue2,November2007 Draft5forRegulatoryReview 177 Release8 16.2.2 DefaultModuleConfiguration InstallationandConfigurationGuide From the factory, the Cyclone AP, SM, and BH are all configured to not transmit on any frequency. This configuration ensures that you do not accidentally turn on an unsynchronized module. Site synchronization of modules is required because

Cyclone modules

cannot transmit and receive signals at the same time.

use TDD (Time Division Duplexing) to distribute signal access of the downlink and uplink frames.

when one module transmits while an unintended module nearby receives signal, the transmitting module may interfere with or desense the receiving module. In this context, interference is self-interference (within the same Cyclone network). 16.2.3 ComponentLayout As shown in Figure 46, the base cover of the module snaps off when you depress a lever on the back of the base cover. This exposes the Ethernet and GPS sync connectors and diagnostic LEDs. RJ11 Connector Connection LEDs Base Cover RJ45 Connector Ethernet Cable Base Cover Release Lever Base Cover Ether net Cable Figure 46: Cyclone base cover, attached and detached Issue2,November2007 Draft5forRegulatoryReview 178 Release8 16.2.4 DiagnosticLEDs InstallationandConfigurationGuide The diagnostic LEDs report the following information about the status of the module. Table 40 and Table 41 identify the LEDs in order of their left-to-right position as the cable connections face downward. NOTE:

The LED color helps you distinguish position of the LED. The LED color does not indicate any status. Table 40: LEDs in AP and BHM Status Information Color when Label Active LNK/5 green ACT/4 orange Presence of data activity Ethernet link Provided red on the Ethernet link Pulse of sync GPS/3 SES/2 green Unused on the AP SYN/1 orange Presence of sync PWR DC power red Notes Continuously lit when link is present. Flashes during data transfer. Frequency of flash is not a diagnostic indication. Continuously lit as pulse as AP receives pulse. SES is the session indicator on the CMM. Always lit on the AP. Always lit when power is correctly supplied. Label Color when Active Status if Registered LNK/5 green Ethernet link ACT/4 orange Presence of data activity on the Ethernet link Unused Unused red green orange Presence of sync GPS/3 SES/2 SYN/1 Table 41: LEDs in SM and BHS Notes Operating Mode Aiming Mode Continuously lit when link is present. Flashes during data transfer. Frequency of flash is not a diagnostic indication. If this module is not registered to another, then these three LEDs cycle on and off from left to right. These five LEDs act as a bar graph to indicate the relative quality of alignment. As power level and jitter improve during alignment, more of these LEDs are lit. PWR red DC power Always lit when power is correctly supplied. Always lit when power is correctly supplied. Issue2,November2007 Draft5forRegulatoryReview 179 Release8 16.2.5 CMM2ComponentLayout InstallationandConfigurationGuide As shown in Figure 125 on Page 344, the CMM2 comprises four assemblies:

Ethernet switch

Power transformer

Interconnect board

GPS receiver. Some CMM2s that were sold earlier had four openings in the bottom plate, as shown in Figure 47. Currently available CMM2s have two additional Ethernet cable and GPS sync cable openings to allow use of thicker, shielded cables. GPS sync cables Ethernet cables N-connector to GPS antenna Figure 47: Cyclone CMM2, bottom view 16.2.6 CMMmicroComponentLayout The layout of the CMMmicro is shown in Figure 48. Network feed Power feed Issue2,November2007 Draft5forRegulatoryReview 180 Release8 InstallationandConfigurationGuide LEGEND 1. Weatherized enclosure 2. Thumb-screw/slot-screwdriver door fasteners 3. Punch-out for padlock 4. Ethernet switch and power module 5. Female BNC connector 6. Water-tight bulkhead connectors 7. Flange for attachment (stainless steel for grounding to tower or building) using U bolts

(provided) or other hardware such as screws, lag bolts, or attachment straps (not provided) 8. Ground strap (for grounding door to enclosure) 9. 100-W 115/230-V AC to 24-V DC power converter, with 10 ft (3 m) of DC power cable

(not shown) 10. 6-ft (1.8-m) AC power cord for 24 V power converter (not shown) Figure 48: Cluster Management Module micro Issue2,November2007 Draft5forRegulatoryReview 181 Release8 16.2.7 StandardsforWiring InstallationandConfigurationGuide Cyclone modules automatically sense whether the Ethernet cable in a connection is wired as straight-through or crossover. You may use either straight-through or crossover cable to connect a network interface card (NIC), hub, router, or switch to these modules. For a straight-through cable, use the EIA/TIA-568B wire color-code standard on both ends. For a crossover cable, use the EIA/TIA-568B wire color-code standard on one end, and the EIA/TIA-568A wire color-code standard on the other end. Where you use the Cyclone AC wall adapter

the power supply output is +24 VDC. the power input to the SM is +11.5 VDC to +30 VDC. the maximum Ethernet cable run is 328 feet (100 meters). 16.2.8 BestPracticesforCabling The following practices are essential to the reliability and longevity of cabled connections:

Use only shielded cables to resist interference.

For vertical runs, provide cable support and strain relief.

Include a 2-ft (0.6-m) service loop on each end of the cable to allow for thermal expansion and contraction and to facilitate terminating the cable again when needed. Include a drip loop to shed water so that most of the water does not reach the connector at the device.

Properly crimp all connectors.

Use dielectric grease on all connectors to resist corrosion.

Use only shielded connectors to resist interference and corrosion. 16.2.9 RecommendedToolsforWiringConnectors The following tools may be needed for cabling the AP:

RJ-11 crimping tool

RJ-45 crimping tool

electrician scissors

wire cutters

cable testing device. 16.2.10 WiringConnectors The following diagrams correlate pins to wire colors and illustrate crossovers where applicable. Location of Pin 1 Pin 1, relative to the lock tab on the connector of a straight-through cable is located as shown below. Issue2,November2007 Draft5forRegulatoryReview 182 Release8 InstallationandConfigurationGuide Pin 1 Lock tab underneath RJ-45 Pinout for Straight-through Ethernet Cable Pin 1 white / orange Pin 2 orange Pin 3 white / green Pin 4 blue Pin 5 white / blue Pin 6 green Pin 7 white / brown Pin 8 brown Pins 7 and 8 carry power to the modules. Pin 1 Pin 2 Pin 3 Pin 4 Pin 5 Pin 6 Pin 7 Pin 8 Pin 1 2 3 4 5 6 7 8 TX+

TX-

RX+

RX-

+V

+V return RJ-45 Straight-thru Pin 1 2 3 4 5 6 7 8 RX+

RX-

TX-

+V return TX-

+V Figure 49: RJ-45 pinout for straight-through Ethernet cable RJ-45 Pinout for Crossover Ethernet Cable Pin 3 Pin 1 white / orange Pin 6 Pin 2 orange Pin 1 Pin 3 white / green Pin 4 Pin 4 blue Pin 5 Pin 5 white / blue Pin 2 Pin 6 green Pin 7 Pin 7 white / brown Pin 8 brown Pin 8 Pins 7 and 8 carry power to the modules. TX+

TX-

RX+

+V return RX-

+V Pin 1 2 3 4 5 6 7 8 RJ-45 Crossover Pin 3 6 1 4 5 2 7 8 RX+

RX-

TX+

TX-

+V

+V return Figure 50: RJ-45 pinout for crossover Ethernet cable RJ-11 Pinout for Straight-through Sync Cable The Cyclone system uses a utility cable with RJ-11 connectors between the AP or BH and synchronization pulse. Presuming CAT 5 cable and 6-pin RJ-11 connectors, the following diagram shows the wiring of the cable for sync. Issue2,November2007 Draft5forRegulatoryReview 183 Release8 Pin 1 white / orange Pin 1 Pin 2 white / green Pin 2 Pin 3 white / blue Pin 3 Pin 4 Pin 4 green Pin 5 Pin 5 blue Pin 6 orange Pin 6 NOTE:The fourth pair is not used. InstallationandConfigurationGuide sync pulse serial transmit serial receive override plug alignment tone Protective Earth (PE)

(ground) Pin 1 2 3 4 5 6 not used RJ-11 Straight-Thru Pin sync pulse 1 serial receive 2 serial transmit 3 override plug 4 alignment tone 5 Protective Earth (PE)

(ground) 6 not used Figure 51: RJ-11 pinout for straight-through sync cable 16.2.11 AlignmentToneTechnicalDetails The alignment tone output from a Cyclone module is available on Pin 5 of the RJ-11 connector, and ground is available on Pin 6. Thus the load at the listening device should be between Pins 5 and 6. The listening device may be a headset, earpiece, or battery-

powered speaker. 16.3 CONFIGURINGAPOINTTOMULTIPOINTLINKFORTEST Perform the following steps to begin the test setup. Procedure 5: Setting up the AP for Quick Start 1. In one hand, securely hold the top (larger shell) of the AP. With the other hand, depress the lever in the back of the base cover (smaller shell). Remove the base cover. 2. Plug one end of a CAT 5 Ethernet cable into the AP. 3. Plug the Ethernet cable connector labeled To Radio into the jack in the pig tail that hangs from the power supply. WARNING!

From this point until you remove power from the AP, stay at least as far from the AP as the minimum separation distance specified in Table 37 on Page 169. 4. Plug the other connector of the pig tail (this connector labeled To Computer) into the Ethernet jack of the computing device. 5. Plug the power supply into an electrical outlet. 6. Power up the computing device. 7. Start the browser in the computing device. end of procedure Issue2,November2007 Draft5forRegulatoryReview 184 Release8 InstallationandConfigurationGuide The Cyclone AP interface provides a series of web pages to configure and monitor the unit. You can access the web-based interface through a computing device that is either directly connected or connected through a network to the AP. If the computing device is not connected to a network when you are configuring the module in your test environment, and if the computer has used a proxy server address and port to configure a Cyclone module, then you may need to first disable the proxy setting in the computer. Perform the following procedure to toggle the computer to not use the proxy setting. Procedure 6: Bypassing proxy settings to access module web pages 1. Launch Microsoft Internet Explorer. 2. Select ToolsInternet OptionsConnectionsLAN Settings. 3. Uncheck the Use a proxy server box. NOTE:If you use an alternate web browser, the menu selections differ from the above. end of procedure In the address bar of your browser, enter the IP address of the AP. (For example, enter http://169.254.1.1 to access the AP through its default IP address). The AP responds by opening the General Status tab of its Home page. 16.3.1 QuickStartPageoftheAP To proceed with the test setup, click the Quick Start button on the left side of the General Status tab. The AP responds by opening the Quick Start page. The Quick Start tab of that page is displayed in Figure 52. NOTE:

If you cannot find the IP address of the AP, see Override Plug on Page 58. Issue2,November2007 Draft5forRegulatoryReview 185 Release8 InstallationandConfigurationGuide Figure 52: Quick Start tab of AP, example Quick Start is a wizard that helps you to perform a basic configuration that places an AP into service. Only the following parameters must be configured:

RF Carrier Frequency

Synchronization

Network IP Address In each Quick Start tab, you can

specify the settings to satisfy the requirements of the network. review the configuration selected. save the configuration to non-volatile memory. Proceed with the test setup as follows. Issue2,November2007 Draft5forRegulatoryReview 186 Release8 InstallationandConfigurationGuide Procedure 7: Using Quick Start to configure a standalone AP for test 1. At the bottom of the Quick Start tab, click the Go To Next Page => button. RESULT:The AP responds by opening the RF Carrier Frequency tab. An example of this tab is shown in Figure 53. Figure 53: Radio Frequency Carrier tab of AP, example 2. From the pull-down menu in the lower left corner of this tab, select a frequency for the test. 3. Click the Go To Next Page => button. RESULT:The AP responds by opening the Synchronization tab. An example of this tab is shown in Figure 54. Issue2,November2007 Draft5forRegulatoryReview 187 Release8 InstallationandConfigurationGuide Figure 54: Synchronization tab of AP, example 4. At the bottom of this tab, select Generate Sync Signal. 5. Click the Go To Next Page => button. RESULT:The AP responds by opening the LAN IP Address tab. An example of this tab is shown in Figure 55. Issue2,November2007 Draft5forRegulatoryReview 188 Release8 InstallationandConfigurationGuide Figure 55: LAN IP Address tab of AP, example 6. At the bottom of this tab, either

specify an IP Address, a Subnet Mask, and a Gateway IP Address for management of the AP and leave the DHCP state set to Disabled. set the DHCP state to Enabled to have the IP address, subnet mask, and gateway IP address automatically configured by a domain name server

(DNS). 7. Click the Go To Next Page => button. RESULT:The AP responds by opening the Review and Save Configuration tab. An example of this tab is shown in Figure 56. Issue2,November2007 Draft5forRegulatoryReview 189 Release8 InstallationandConfigurationGuide Figure 56: Review and Save Configuration tab of AP, example 8. Ensure that the initial parameters for the AP are set as you intended. 9. Click the Save Changes button. 10. Click the Reboot button. RESULT:The AP responds with the message Reboot Has Been Initiated 11. Wait until the indicator LEDs are not red. 12. Trigger your browser to refresh the page until the AP redisplays the General Status tab. 13. Wait until the red indicator LEDs are not lit. end of procedure Issue2,November2007 Draft5forRegulatoryReview 190 Release8 InstallationandConfigurationGuide Cyclone encourages you to experiment with the interface. Unless you save a configuration and reboot the AP after you save the configuration, none of the changes are effected. 16.3.2 TimeTaboftheAP To proceed with the test setup, click the Configuration link on the left side of the General Status tab. When the AP responds by opening the Configuration page to the General tab, click the Time tab. An example of this tab is displayed in Figure 57. Figure 57: Time tab of AP, example To have each log in the AP correlated to a meaningful time and date, either a reliable network element must pass time and date to the AP or you must set the time and date whenever a power cycle of the AP has occurred. A network element passes time and date in any of the following scenarios:

A connected CMM2 passes time and date (GPS time and date, if received).

A connected CMMmicro passes the time and date (GPS time and date, if received), but only if both the CMMmicro is operating on CMMmicro Release 2.1 or later release. (These releases include an NTP server functionality.)

A separate NTP server is addressable from the AP. If the AP should obtain time and date from either a CMMmicro or a separate NTP server, enter the IP address of the CMMmicro or NTP server on this tab. To force the AP to Issue2,November2007 Draft5forRegulatoryReview 191 Release8 InstallationandConfigurationGuide obtain time and date before the first (or next) 15-minute interval query of the NTP server, click Get Time through NTP. If you enter a time and date, the format for entry is Time :

hh / mm / ss Date :

where MM

/

dd

/

yyyy hh represents the two-digit hour in the range 00 to 24 mm represents the two-digit minute ss represents the two-digit second MM represents the two-digit month dd represents the two-digit day yyyy represents the four-digit year Proceed with the test setup as follows. Enter the appropriate information in the format shown above. Then click the Set Time and Date button. NOTE:The time displayed at the top of this page is static unless your browser is set to automatically refresh. Procedure 8: Setting up the SM for test 1. In one hand, securely hold the top (larger shell) of the SM. With the other hand, depress the lever in the back of the base cover (smaller shell). Remove the base cover. 2. Plug one end of a CAT 5 Ethernet cable into the SM RJ-45 jack. 3. Plug the other end of the Ethernet cable into the jack in the pig tail that hangs from the power supply. 4. Roughly aim the SM toward the AP. WARNING!

From this point until you remove power from the SM, stay at least as far from the SM as the minimum separation distance specified in Table 37 on Page 169. 5. Plug the power supply into an electrical outlet. 6. Repeat the foregoing steps for each SM that you wish to include in the test. 7. Back at the computing device, on the left side of the Time & Date tab, click Home. 8. Click the Session Status tab. end of procedure Issue2,November2007 Draft5forRegulatoryReview 192 Release8 16.3.3 SessionStatusTaboftheAP InstallationandConfigurationGuide An example of the AP Session Status tab is displayed in Figure 58. Figure 58: Session Status tab data from AP, example If no SMs are registered to this AP, then the Session Status tab displays the simple message No sessions. In this case, try the following steps. Procedure 9: Retrying to establish a point-to-multipoint link 1. More finely aim the SM or SMs toward the AP. 2. Recheck the Session Status tab of the AP for the presence of LUIDs. 3. If still no LUIDs are reported on the Session Status tab, click the Configuration button on the left side of the Home page. RESULT:The AP responds by opening the AP Configuration page. 4. Click the Radio tab. 5. Find the Color Code parameter and note the setting. 6. In the same sequence as you did for the AP directly under Configuring a Point-to-

Multipoint Link for Test on Page 184, connect the SM to a computing device and to power. Issue2,November2007 Draft5forRegulatoryReview 193 Release8 InstallationandConfigurationGuide 7. On the left side of the SM Home page, click the Configuration button. RESULT: The Configuration page of the SM opens. 8. Click the Radio tab. 9. If the transmit frequency of the AP is not selected in the Custom Radio Frequency Scan Selection List parameter, select the frequency that matches. 10. If the Color Code parameter on this page is not identical to the Color Code parameter you noted from the AP, change one of them so that they match. 11. At the bottom of the Radio tab for the SM, click the Save Changes button. 12. Click the Reboot button. 13. Allow several minutes for the SM to reboot and register to the AP. 14. Return to the computing device that is connected to the AP. 15. Recheck the Session Status tab of the AP for the presence of LUIDs. end of procedure The Session Status tab provides information about each SM that has registered to the AP. This information is useful for managing and troubleshooting a Cyclone system. All information that you have entered in the Site Name field of the SM displays in the Session Status tab of the linked AP. The Session Status tab also includes the current active values on each SM (LUID) for MIR, CIR, and VLAN, as well as the source of these values (representing the SM itself, BAM, or the AP and cap, if anyfor example, APCAP as shown in Figure 58 above). L indicates a Cyclone Lite SM, and D indicates from the device. As an SM registers to the AP, the configuration source that this page displays for the associated LUID may change. After registration, however, the displayed source is stable and can be trusted. The Session Status tab of the AP provides the following parameters. LUID This field displays the LUID (logical unit ID) of the SM. As each SM registers to the AP, the system assigns an LUID of 2 or a higher unique number to the SM. If an SM loses registration with the AP and then regains registration, the SM will retain the same LUID. The LUID association is lost when a power cycle of the AP occurs. NOTE:

MAC This field displays the MAC address (or electronic serial number) of the SM. State This field displays the current status of the SM as either

IN SESSION to indicate that the SM is currently registered to the AP. IDLE to indicate that the SM was registered to the AP at one time, but now is not. This field also indicates whether the encryption scheme in the module is enabled. Issue2,November2007 Draft5forRegulatoryReview 194 Release8 InstallationandConfigurationGuide Site Name This field indicates the name of the SM. You can assign or change this name on the Configuration web page of the SM. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Software Version This field displays the software release that operates on the SM, the release date and time of the software. Software Boot Version This field indicates the CYCLONEBOOT version number. FPGA Version This field displays the version of FPGA that runs on the SM. Session Timeout This field displays the timeout in seconds for management sessions via HTTP, telnet, or ftp access to the SM. 0 indicates that no limit is imposed. AirDelay This field displays the distance of the SM from the AP. To derive the distance in meters, multiply the displayed number by 0.3048. At close distances, the value in this field is unreliable. Session Count This field displays how many sessions the SM has had with the AP. Typically, this is the sum of Reg Count and Re-Reg Count. However, the result of internal calculation may display here as a value that slightly differs from the sum. If the number of sessions is significantly greater than the number for other SMs, then this may indicate a link problem or an interference problem. Reg Count When an SM makes a registration request, the AP checks its local data to see whether it considers the SM to be already registered. If the AP concludes that the SM is not, then the request increments the value of this field. Re-Reg Count When an SM makes a registration request, the AP checks its local data to see whether it considers the SM to be already registered. If the AP concludes that the SM is not, then the request increments the value of this field. Typically, a Re-Reg is the case where both an SM attempts to reregister for having lost communication with the AP. the AP has not yet observed the link to the SM as being down. A high number in this field is often an indication of link instability or interference problems. RSSI, Jitter, and Power Level (Avg/Last) The Session Status tab shows the received Power Level in dBm and Jitter. Proper alignment maximizes Power Level and minimizes Jitter. As you refine alignment, you should favor lower jitter over higher dBm. For example, if coarse alignment gives an SM a power level of 75 dBm and a jitter measurement of 5, and further refining Issue2,November2007 Draft5forRegulatoryReview 195 Release8 InstallationandConfigurationGuide the alignment drops the power level to 78 dBm and the jitter to 2 or 3, use the refined alignment, with the following caveats:

When the receiving link is operating at 1X, the Jitter scale is 0 to 15 with desired jitter between 0 and 4. When the receiving link is operating at 2X, the Jitter scale is 0 to 15 with desired jitter between 0 and 9. The Session Status tab also shows a historical RSSI, a unitless measure of power. Use Power Level and ignore RSSI. RSSI implies more accuracy and precision than is inherent in its measurement. Sustained Uplink Data Rate This field displays the value that is currently in effect for the SM, with the source of that value in parentheses. This is the specified rate at which each SM registered to this AP is replenished with credits for transmission. The configuration source of the value is indicated in parentheses. See Maximum Information Rate (MIR) Parameters on Page 84 Setting the Configuration Source on Page 295. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 86 Uplink Burst Allocation This field displays the value that is currently in effect for the SM, with the source of that value in parentheses. This is the specified maximum amount of data that each SM is allowed to transmit before being recharged at the Sustained Uplink Data Rate with credits to transmit more. The configuration source of the value is indicated in parentheses. See Maximum Information Rate (MIR) Parameters on Page 84 Setting the Configuration Source on Page 295. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 86 Sustained Downlink Data Rate This field displays the value that is currently in effect for the SM, with the source of that value in parentheses. This is the specified the rate at which the AP should be replenished with credits (tokens) for transmission to each of the SMs in its sector. The configuration source of the value is indicated in parentheses. See Maximum Information Rate (MIR) Parameters on Page 84 Setting the Configuration Source on Page 295. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 86 Downlink Burst Allocation This field displays the value that is currently in effect for the SM, with the source of that value in parentheses. This is the maximum amount of data to allow the AP to transmit to any registered SM before the AP is replenished with transmission credits at the Sustained Downlink Data Rate. The configuration source of the value is indicated in parentheses. See Maximum Information Rate (MIR) Parameters on Page 84 Interaction of Burst Allocation and Sustained Data Rate Settings on Page 86 Issue2,November2007 Draft5forRegulatoryReview 196 Release8 InstallationandConfigurationGuide Setting the Configuration Source on Page 295. Low Priority Uplink CIR This field displays the value that is currently in effect for the SM, with the source of that value in parentheses. The configuration source of the value is indicated in parentheses. See Committed Information Rate on Page 86 Setting the Configuration Source on Page 295. Low Priority Downlink CIR This field displays the value that is currently in effect for the SM, with the source of that value in parentheses. The configuration source of the value is indicated in parentheses. See Committed Information Rate on Page 86 Setting the Configuration Source on Page 295. Rate This field displays whether the high-priority channel is enabled in the SM and the status of 1X or 2X operation in the SM. See Checking the Status of 2X Operation on Page 92. 16.3.4 BeginningtheTestofPointtoMultipointLinks To begin the test of links, perform the following steps:

1. In the Session Status tab of the AP, note the LUID associated with the MAC address of any SM you wish to involve in the test. 2. Click the Remote Subscribers tab. 16.3.5 RemoteSubscribersTaboftheAP An example of a Remote Subscribers tab is displayed in Figure 59. Figure 59: Remote Subscribers tab of AP, example Issue2,November2007 Draft5forRegulatoryReview 197 Release8 InstallationandConfigurationGuide This tab allows you to view the web pages of registered SMs over the RF link. To view the pages for a selected SM, click its link. The General Status tab of the SM opens. 16.3.6 GeneralStatusTaboftheSM An example of the General Status tab of an SM is displayed in Figure 60. Figure 60: General Status tab of SM, example The General Status tab provides information on the operation of this SM. This is the tab that opens by default when you access the GUI of the SM. The General Status tab provides the following read-only fields. Device Type This field indicates the type of the Cyclone module. Values include the frequency band of the SM, its module type, and its MAC address. Issue2,November2007 Draft5forRegulatoryReview 198 Release8 InstallationandConfigurationGuide Software Version This field indicates the Cyclone system release, the time and date of the release, and whether communications involving the module are secured by DES or AES encryption

(see Encrypting Cyclone Radio Transmissions on Page 375). If you request technical support, provide the information from this field. Software BOOT Version This field indicates the version of the CYCLONEBOOT file. If you request technical support, provide the information from this field. Board Type This field indicates the series of hardware. See Designations for Hardware in Radios on Page 372. FPGA Version This field indicates the version of the field-programmable gate array (FPGA) on the module. When you request technical support, provide the information from this field. Uptime This field indicates how long the module has operated since power was applied. System Time This field provides the current time. Any SM that registers to an AP inherits the system time, which is displayed in this field as GMT (Greenwich Mean Time). Ethernet Interface This field indicates the speed and duplex state of the Ethernet interface to the SM. Session Status This field displays the following information about the current session:

Scanning indicates that this SM currently cycles through the radio frequencies that are selected in the Radio tab of the Configuration page.

Syncing indicates that this SM currently attempts to receive sync.

Registering indicates that this SM has sent a registration request message to the AP and has not yet received a response.

Registered indicates that this SM is both

registered to an AP. ready to transmit and receive data packets.

Alignment indicates that this SM is in an aiming mode. See Table 41 on Page 179. Registered AP This field displays the MAC address of the AP to which this SM is registered. RSSI, Power Level, and Jitter The General Status tab shows the received Power Level in dBm and Jitter. Proper alignment maximizes Power Level and minimizes Jitter. As you refine alignment, you should favor lower jitter over higher dBm. For example, if coarse alignment gives an SM a power level of 75 dBm and a jitter measurement of 5, and further refining Issue2,November2007 Draft5forRegulatoryReview 199 Release8 InstallationandConfigurationGuide the alignment drops the power level to 78 dBm and the jitter to 2 or 3, use the refined alignment, with the following caveats:

When the receiving link is operating at 1X, the Jitter scale is 0 to 15 with desired jitter between 0 and 4. When the receiving link is operating at 2X, the Jitter scale is 0 to 15 with desired jitter between 0 and 9. For historical relevance, the General Status tab also shows the RSSI, the unitless measure of power. Use Power Level and ignore RSSI. RSSI implies more accuracy and precision than is inherent in its measurement. NOTE:

Unless the page is set to auto-refresh, the values displayed are from the instant the General Status tab was selected. To keep a current view of the values, refresh the browser screen or set to auto-refresh. Air Delay This field displays the distance in feet between this SM and the AP. To derive the distance in meters, multiply the value of this parameter by 0.3048. Distances reported as less than 200 feet (61 meters) are unreliable. Site Name This field indicates the name of the physical module. You can assign or change this name in the SNMP tab of the SM Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Site Contact This field indicates contact information for the physical module. You can provide or change this information in the SNMP tab of the SM Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Site Location This field indicates site information for the physical module. You can provide or change this information in the SNMP tab of the SM Configuration page. Maximum Throughput This field indicates the limit of aggregate throughput for the SM and is based on the default (factory) limit of the SM and any floating license that is currently assigned to it. Issue2,November2007 Draft5forRegulatoryReview 200 Release8 16.3.7 ContinuingtheTestofPointtoMultipointLinks InstallationandConfigurationGuide To resume the test of links, perform the following steps. Procedure 10: Verifying and recording information from SMs 1. Verify that the Session Status field of the General Status tab in the SM indicates REGISTERED. 2. While you view the General Status tab in the SM, note (or print) the values of the following fields:

Device type

Software Version

Software BOOT Version

Board Type

FPGA Version 3. Systematically ensure that you can retrieve this data (from a database, for example) when you later prepare to deploy the SM to subscriber premises. 4. Return you to the Remote Subscribers tab of the AP. 5. Click the link of the next SM that you wish to test. 6. Repeat the test procedure from that point. When you have tested all of the SMs that you intend to test, return your browser to the General Status tab of the AP. end of procedure Issue2,November2007 Draft5forRegulatoryReview 201 Release8 16.3.8 GeneralStatusTaboftheAP InstallationandConfigurationGuide An example of an AP General Status tab is displayed in Figure 61. Figure 61: General Status tab of AP, example The General Status tab provides information on the operation of this AP. This is the tab that opens by default when you access the GUI of the AP. The General Status tab provides the following read-only fields. Device Type This field indicates the type of the Cyclone module. Values include the frequency band of the AP, its module type, and its MAC address. Software Version This field indicates the Cyclone system release, the time and date of the release, and whether communications involving the module are secured by DES or AES encryption

(see Encrypting Cyclone Radio Transmissions on Page 375). If you request technical support, provide the information from this field. Software BOOT Version This field indicates the version of the CYCLONEBOOT file. If you request technical support, provide the information from this field. Issue2,November2007 Draft5forRegulatoryReview 202 Release8 InstallationandConfigurationGuide Board Type This field indicates the series of hardware. See Designations for Hardware in Radios on Page 372. FPGA Version This field indicates the version of the field-programmable gate array (FPGA) on the module. When you request technical support, provide the information from this field. Uptime This field indicates how long the module has operated since power was applied. System Time This field provides the current time. If the AP is connected to a CMM, then this field provides GMT (Greenwich Mean Time). Any SM that registers to the AP inherits the system time. Last NTP Time Update This field displays when the AP last used time sent from an NTP server. If the AP has not been configured in the Time tab of the Configuration page to request time from an NTP server, then this field is populated by 00:00:00 00/00/00. Ethernet Interface This field indicates the speed and duplex state of the Ethernet interface to the AP. Registered SM Count This field indicates how many SMs are registered to the AP. GPS Sync Pulse Status This field indicates the status of synchronization as follows:

Generating sync indicates that the module is set to generate the sync pulse.

Receiving Sync indicates that the module is set to receive a sync pulse from an outside source and is receiving the pulse.

ERROR: No Sync Pulse indicates that the module is set to receive a sync pulse from an outside source and is not receiving the pulse. NOTE:

When this message is displayed, the AP transmitter is turned off to avoid self-interference within the Cyclone system. Site Name This field indicates the name of the physical module. You can assign or change this name in the SNMP tab of the AP Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Issue2,November2007 Draft5forRegulatoryReview 203 Release8 InstallationandConfigurationGuide Site Contact This field indicates contact information for the physical module. You can provide or change this information in the SNMP tab of the AP Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Site Location This field indicates site information for the physical module. You can provide or change this information in the SNMP tab of the AP Configuration page. Scheduling Type This field indicates the type of frame scheduler that is active in the AP. MP Double Rate This field indicates whether 2X modulation rate is enabled for the sector. 16.3.9 ConcludingtheTestofPointtoMultipointLinks To conclude the test, perform the following steps. Procedure 11: Verifying and recording information from the AP 1. Confirm that the GPS Sync Pulse Status field indicates Generating Sync. NOTE:This indication confirms that the AP is properly functional. 2. While your browser is directed to this General Status tab, note (or print) the values of the following fields:

Device type

Software Version

Software BOOT Version

Board Type

FPGA Version 3. Systematically ensure that you can retrieve this data when you prepare to deploy the AP. end of procedure 16.4 CONFIGURINGAPOINTTOPOINTLINKFORTEST NOTE:

This section supports the Cyclone 10- and 20-Mbps Backhaul Modules. To find setup and configuration guides that support the OFDM Series Backhaul Modules, refer to Products Not Covered by This User Guide on Page 34. Perform the following steps to begin the test setup. Issue2,November2007 Draft5forRegulatoryReview 204 Release8 InstallationandConfigurationGuide Procedure 12: Setting up the BH for Quick Start 1. In one hand, securely hold the top (larger shell) of the BH that you intend to deploy as a timing master. With the other hand, depress the lever in the back of the base cover (smaller shell). Remove the base cover. 2. Plug one end of a CAT 5 Ethernet cable into the timing master. 3. Plug the other end of the Ethernet cable into the jack in the pig tail that hangs from the power supply. 4. Plug the other connector of the pig tail into the Ethernet jack of the computing device. WARNING!

From this point until you remove power from the BH, stay at least as far from the BH as the minimum separation distance specified in Table 37 on Page 169. 5. Plug the power supply into an electrical outlet. 6. Power up the computing device. 7. Start the browser in the computing device. end of procedure The Cyclone BH interface provides a series of web pages to configure and monitor the unit. These screens are subject to change by subsequent software releases. You can access the web-based interface through only a computing device that is either directly connected or connected through a network to the BH. If the computing device is not connected to a network when you are configuring the module in your test environment, and if the computer has used a proxy server address and port to configure a Cyclone module, then you may need to first disable the proxy setting in the computer. To toggle the computer to not use the proxy setting, perform Procedure 6 on Page 185. In the address bar of your browser, enter the IP address of the BHM (default is 169.254.1.1). The BHM responds by opening the General Status tab of its Home page. 16.4.1 QuickStartPageoftheBHM To proceed with the test setup, click the Quick Start button on the left side of the General Status tab. The BHM responds by opening the Quick Start tab of the Quick Start page. An example of this tab is displayed in Figure 62. Issue2,November2007 Draft5forRegulatoryReview 205 Release8 InstallationandConfigurationGuide Figure 62: Quick Start tab of BHM, example Quick Start is a wizard that helps you to perform a basic configuration that places a BHM into service. Only the following variables must be configured:

RF Carrier Frequency

Synchronization

Network IP Address In each page under Quick Start, you can

specify the settings to satisfy the requirements of the network. review the configuration selected. save the configuration to non-volatile memory. Proceed with the test setup as follows. Issue2,November2007 Draft5forRegulatoryReview 206 Release8 InstallationandConfigurationGuide Procedure 13: Using Quick Start to configure the BHs for test 1. At the bottom of the Quick Start tab, click the Go To Next Page => button. RESULT:The BHM responds by opening the RF Carrier Frequency tab. 2. From the pull-down menu in the lower left corner of this page, select a frequency for the test. 3. Click the Go To Next Page => button. RESULT:The BHM responds by opening the Synchronization tab. 4. At the bottom of this page, select Generate Sync Signal. 5. Click the Go To Next Page => button. RESULT:The BHM responds by opening the LAN IP Address tab. 6. At the bottom of this tab, either

specify an IP Address, Subnet Mask, and Gateway IP Address for management of the BHM and leave the DHCP State set to Disabled. set the DHCP State to Enabled to have the IP address, subnet mask, and gateway IP address automatically configured by a domain name server

(DNS). 7. Click the Go To Next Page => button. RESULT:The BHM responds by opening the Review and Save Configuration tab. 8. Ensure that the initial parameters for the BHM are set as you intended. 9. Click the Save Changes button. 10. On the left side of the tab, click the Configuration button. RESULT:The BH responds by opening the General tab of its Configuration page. 11. In the Timing Mode parameter, select Timing Master. 12. Click the Save Changes button. 13. Click the Reboot button. RESULT:The BHM responds with the message Reboot Has Been Initiated. This BH is now forced to provide sync for the link and has a distinct set of web interface pages, tabs, and parameters for the role of BHM. 14. Wait until the indicator LEDs are not red. 15. Trigger your browser to refresh the page until the BHM redisplays the General Status tab of its Home page. 16. Repeat these steps to configure the other BH in the pair to be a BHS, selecting Timing Slave in Step 11. end of procedure Cyclone encourages you to experiment with the interface. Unless you save a configuration and reboot the BHM after you save the configuration, none of the changes are effected. 16.4.2 TimeTaboftheBHM To proceed with the test setup, in the BHM, click the Configuration button on the left side of the General Status tab. The BHM responds by opening its Configuration page to the General tab. Click the Time tab. An example of this tab is displayed in Figure 63. Issue2,November2007 Draft5forRegulatoryReview 207 Release8 InstallationandConfigurationGuide Figure 63: Time tab of BHM, example To have each log in the BHM correlated to a meaningful time and date, either a reliable network element must pass time and date to the BHM or you must set the time and date whenever a power cycle of the BHM has occurred. A network element passes time and date in any of the following scenarios:

A connected CMM2 passes time and date (GPS time and date, if received).

A connected CMMmicro passes the time and date (GPS time and date, if received), but only if the CMMmicro is operating on CMMmicro Release 2.1 or later release. (These releases include an NTP server functionality.)

A separate NTP server is addressable from the BHM. If the BHM should derive time and date from either a CMMmicro or a separate NTP server, enter the IP address of the CMMmicro or NTP server on this tab. To force the BHM to derive time and date before the first (or next) 15-minute interval query of the NTP server, click Get Time through NTP. Issue2,November2007 Draft5forRegulatoryReview 208 Release8 If you enter a time and date, the format for entry is InstallationandConfigurationGuide Time :

hh / mm / ss Date :

where MM

/

dd

/

yyyy hh represents the two-digit hour in the range 00 to 24 mm represents the two-digit minute ss represents the two-digit second MM represents the two-digit month dd represents the two-digit day yyyy represents the four-digit year Proceed with the test setup as follows. Procedure 14: Setting up the BHS for test 1. Enter the appropriate information in the format shown above. 2. Click the Set Time and Date button. 3. NOTE:The time displayed at the top of this page is static unless your browser is set to automatically refresh. In one hand, securely hold the top (larger shell) of the BH that you intend to deploy as a timing slave. With the other hand, depress the lever in the back of the base cover (smaller shell). Remove the base cover. 4. Plug one end of a CAT 5 Ethernet cable into the BHS. 5. Plug the other end of the Ethernet cable into the jack in the pig tail that hangs from the power supply. 6. Roughly aim the BHS toward the BHM. WARNING!

From this point until you remove power from the BHS, stay at least as far from the BHS as the minimum separation distance specified in Table 37 on Page 169. 7. Plug the power supply into an electrical outlet. 8. Back at the computing device, on the left side of the BHM Time tab, click the Home button. When the Home page opens to the General Status tab, click the Remote Subscribers tab. RESULT:The BHM opens the Remote Subscribers tab. An example of this tab is shown in Figure 64. end of procedure Issue2,November2007 Draft5forRegulatoryReview 209 Release8 InstallationandConfigurationGuide Figure 64: Remote Subscribers tab of BHM, example Issue2,November2007 Draft5forRegulatoryReview 210 Release8 16.4.3 BeginningtheTestofPointtoPointLinks InstallationandConfigurationGuide To begin the test of your BH link, in the Remote Subscribers tab of the BHM, click the link to the BHS. The BHS GUI opens to the General Status tab of its Home page. An example of the BHS General Status tab is displayed in Figure 65. Figure 65: General Status tab of BHS, example The General Status tab provides information on the operation of this BHS. This is the tab that opens by default when you access the GUI of the BHS. The General Status tab provides the following read-only fields. Device Type This field indicates the type of the Cyclone module. Values include the frequency band of the BHS, its module type, and its MAC address. Software Version This field indicates the Cyclone system release, the time and date of the release, the modulation rate, and whether communications involving the module are secured by DES or AES encryption (see Encrypting Cyclone Radio Transmissions on Page 375). If you request technical support, provide the information from this field. Issue2,November2007 Draft5forRegulatoryReview 211 Release8 InstallationandConfigurationGuide Software BOOT Version This field indicates the version of the CYCLONEBOOT file. If you request technical support, provide the information from this field. Board Type This field indicates the series of hardware. See Designations for Hardware in Radios on Page 372. FPGA Version This field indicates the version of the field-programmable gate array (FPGA) on the module. When you request technical support, provide the information from this field. Uptime This field indicates how long the module has operated since power was applied. System Time This field provides the current time. When a BHS registers to a BHM, it inherits the system time, which is displayed in this field as GMT (Greenwich Mean Time). Ethernet Interface This field indicates the speed and duplex state of the Ethernet interface to the BHS. Session Status This field displays the following information about the current session:

Scanning indicates that this SM currently cycles through the RF frequencies that are selected in the Radio tab of the Configuration page.

Syncing indicates that this SM currently attempts to receive sync.

Registering indicates that this SM has sent a registration request message to the AP and has not yet received a response.

Registered indicates that this SM is both

registered to an AP. ready to transmit and receive data packets.

Alignment indicates that this SM is in an aiming mode. See Table 41 on Page 179. Registered AP This field displays the MAC address of the BHM to which this BHS is registered. RSSI, Power Level, and Jitter The General Status tab shows the received Power Level in dBm and Jitter. Proper alignment maximizes Power Level and minimizes Jitter. As you refine alignment, you should favor lower jitter over higher dBm. For example, if coarse alignment gives the BHS a power level of 75 dBm and a jitter measurement of 5, and further refining the alignment drops the power level to 78 dBm and the jitter to 2 or 3, use the refined alignment, with the following caveats:

When the receiving link is operating at 1X, the Jitter scale is 0 to 15 with desired jitter between 0 and 4. Issue2,November2007 Draft5forRegulatoryReview 212 Release8 InstallationandConfigurationGuide When the receiving link is operating at 2X, the Jitter scale is 0 to 15 with desired jitter between 0 and 9. For historical relevance, the General Status tab also shows the RSSI, the unitless measure of power. Use Power Level and ignore RSSI. RSSI implies more accuracy and precision than is inherent in its measurement. NOTE:

Unless the page is set to auto-refresh, the values displayed are from the instant the General Status tab was selected. To keep a current view of the values, refresh the browser screen or set to auto-refresh. Air Delay This field displays the distance in feet between the BHS and the BHM. To derive the distance in meters, multiply the value of this parameter by 0.3048. Distances reported as less than 200 feet (61 meters) are unreliable. Site Name This field indicates the name of the physical module. You can assign or change this name in the SNMP tab of the BHS Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Site Contact This field indicates contact information for the physical module. You can provide or change this information in the SNMP tab of the BHS Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Site Location This field indicates site information for the physical module. You can provide or change this information in the SNMP tab of the BHS Configuration page. 16.4.4 ContinuingtheTestofPointtoPointLinks To resume the test, perform the following steps. Procedure 15: Verifying and recording information from the BHS 1. Verify that the Session Status field of the General Status tab in the BHS indicates REGISTERED. NOTE:This indication confirms that the BHS is properly functional. 2. While your browser is set to the General Status tab, note (or print) the values of the following fields:

Device type

Software Version

Software BOOT Version

Board Type

FPGA Version Issue2,November2007 Draft5forRegulatoryReview 213 Release8 InstallationandConfigurationGuide 3. Systematically ensure that you can retrieve this data when you prepare to deploy the BHS. 4. Return your browser to the General Status tab of the BHM. end of procedure 16.4.5 GeneralStatusTaboftheBHM An example of a BHM General Status tab is displayed in Figure 66. Figure 66: General Status tab of BHM, example The Status page provides information on the operation of the module. This is the default web page for the module. The Status page provides the following fields. Device Type This field indicates the type of the Cyclone module. Values include the frequency band of the module, the module type, timing mode, and the MAC address of the module. Software Version This field indicates the software release that is operated on the module, the release date and time of the software release, the modulation rate capability, and whether the module Issue2,November2007 Draft5forRegulatoryReview 214 Release8 InstallationandConfigurationGuide is secured by DES or AES encryption (see Encrypting Cyclone Radio Transmissions on Page 375). When you request technical support, provide the information from this field. Software BOOT Version This field indicates the version of the CYCLONEBOOT file. If you request technical support, provide the information from this field. Board Type This field indicates the series of hardware. See Designations for Hardware in Radios on Page 372. FPGA Version This field indicates the version of the field-programmable gate array (FPGA) on the module. When you request technical support, provide the information from this field. Uptime This field indicates how long the module has operated since power was applied. System Time This field provides the current time. If the BHM is connected to a CMM, then this field provides GMT (Greenwich Mean Time). The BHS that registers to the BHM inherits the system time. Last NTP Time Update If the Time & Date page of the module specifies that time should be received from an NTP server, then this field indicates when the time was last updated by a Network Time Protocol (NTP) server. Ethernet Interface This field indicates the speed and duplex state of the Ethernet interface to the module. Registered SM Count This field confirms that only one BHS is registered to the BHM. GPS Sync Pulse Status This field indicates the status of synchronization as follows:

Generating sync indicates that the module is set to generate the sync pulse.

Receiving Sync indicates that the module is set to receive a sync pulse from an outside source and is receiving the pulse.

ERROR: No Sync Pulse indicates that the module is set to receive a sync pulse from an outside source and is not receiving the pulse. NOTE:

When this message is displayed, the BHM transmitter is turned off to avoid self-interference within the Cyclone system. Issue2,November2007 Draft5forRegulatoryReview 215 Release8 InstallationandConfigurationGuide Site Name This field indicates the name of the physical module. You can assign or change this name in the SNMP tab of the BHM Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Site Contact This field indicates contact information for the physical module. You can provide or change this information in the SNMP tab of the BHM Configuration page. This information is also set into the sysName SNMP MIB-II object and can be polled by an SNMP management server. Site Location This field indicates site information for the physical module. You can provide or change this information in the SNMP tab of the BHM Configuration page. Scheduling Type This field indicates the type of frame scheduler that is active in the BHM. 16.4.6 ConcludingtheTestofPointtoPointLinks To conclude the test, perform the following steps. Procedure 16: Verifying and recording information from the BHM 1. Confirm that the GPS Sync Pulse Status field indicates Generating Sync. NOTE:This indication confirms that the BHM is properly functional. 2. While your browser is set to this BHM Status page, note (or print) the values of the following fields:

Device type

Software Version

Software BOOT Version

Board Type

FPGA Version 3. Systematically ensure that you can retrieve this data when you prepare to deploy the BHM. end of procedure Issue2,November2007 Draft5forRegulatoryReview 216 Release8 16.5 CONFIGURINGACMMMICROFORTEST InstallationandConfigurationGuide 16.5.1 SettingupaCMMmicro The layout of the CMMmicro is as shown in Figure 67. 1 Weatherized enclosure 2 Thumb-screw/slot-screwdriver door fasteners 3 Punch-out for padlock 4 Ethernet switch and power module 5 Female BNC connector 6 Water-tight bulkhead connectors 7 Flange for attachment (stainless steel so it grounds to tower or building) using U bolts (provided) or other hardware such as screws or lag bolts or attachment straps (not provided). 8 Ground strap to ground door to enclosure Figure 67: CMMmicro layout Issue2,November2007 Draft5forRegulatoryReview 217 Release8 Perform the following procedure to set up the CMMmicro. InstallationandConfigurationGuide IMPORTANT!

Start with the 24-V DC power converter unconnected to AC. Procedure 17: Setting up a CMMmicro 1. Connect the converter lead whose insulation has a white stripe to +V on the CMMmicro terminal block. 2. Connect the converter lead whose insulation is solid black to -V on the CMMmicro terminal block. 3. Connect the power converter to an AC receptacle using the AC power cord. 4. Wait until the green LED labeled RDY flashes. NOTE: This should occur in less than one minute and will indicate that the CMMmicro has transitioned from booting to normal operation. 5. Observe which, if any, Ethernet ports are powered, as indicated by a lit red LED to the right of the Ethernet port. NOTE: The position of this +24-V OUT LED is shown in Figure 68 on Page 219. CAUTION!

Never connect any devices other than Cyclone APs and BHs to a powered port. Powered ports are indicated by a red LED to the right of the port. (See Item 7 in Figure 69 on Page 220.) A powered port has 24-V DC on Pins 7 and 8 and 24-V return on Pins 4 and 5. This can damage other networking equipment, such as a computer or a router. 6. On the 8-port Ethernet block of the CMMmicro, use either a straight-through or crossover Ethernet cable to connect any unpowered port (without the red LED lit) to a browser-equipped computer. NOTE: The CMMmicro auto-senses the cable type. 7. Verify these CMMmicro connections against Figure 70 on Page 221. 8. Configure the computer to use DHCP, with no proxy in your network settings. 9. Open the browser. 10. In the address bar, enter 169.254.1.1 (the default IP address of the CMMmicro). RESULT: The browser displays the CMMmicro Status page. end of procedure Issue2,November2007 Draft5forRegulatoryReview 218 Release8 InstallationandConfigurationGuide Figure 68: CMMmicro door label Issue2,November2007 Draft5forRegulatoryReview 219 Release8 InstallationandConfigurationGuide 1 24 V DC power connection on terminal block (+V). 2 24 V DC ground connection on terminal block (-V). 3 Ground bonding point for CMMmicro. Ground connection on terminal block, for grounding to Protective Earth (PE)

. 4 Female BNC connector for connecting to coax cable from GPS antenna. 5 Status display of eight green LEDs. The left LEDs show the number of satellites visible to the CMMmicro (1, 2, 4, and 8), and the right LEDs show status:

RDY (Ready) Flashing LED indicates CMMmicro software has booted and is operational. LED continues to flash during normal operation.

SYNC Constant LED indicates CMMmicro is receiving signal from the GPS antenna and is able to derive sync.

DFLT (default) Constant LED indicates CMMmicro has booted with Override Switch in down/override position, and therefore with default IP address (169.254.1.1) and no password.

PWR (power) Constant LED indicates CMMmicro has power. 6 8-port Ethernet connection block with 2 LEDs per port indicating port status. 7 Constant red LED to the right of each port indicates the port is powered with 24 V DC

(controlled by the CMMmicro Configuration page). 8 Constant green LED to the left of each port indicates the port is detecting Ethernet connectivity. 9 Override toggle switch, for overriding a lost or unknown IP address or password. Down is normal position, while rebooting in the up position brings the CMMmicro up with the default IP address (169.254.1.1) and no password required. Figure 69: CMMmicro circuit board Issue2,November2007 Draft5forRegulatoryReview 220 Release8 InstallationandConfigurationGuide Figure 70: CMMmicro connections Issue2,November2007 Draft5forRegulatoryReview 221 Release8 16.5.2 StatusPageoftheCMMmicro InstallationandConfigurationGuide An example of a CMMmicro Status page is displayed in Figure 71. Figure 71: Status page of CMMmicro, example The Status page provides information on the operation of this CMMmicro. This is the default web page for the CMMmicro. The Status page provides the following fields. Link A red dot indicates that the port is active and detects Ethernet traffic. A grey dot indicates that the port is not active and no traffic is detected. 100BaseT A red dot indicates that the port has auto-negotiated to a 100Base-T connection. A grey dot indicates that the port has auto-negotiated to a 10Base-T connection. (This convention is also used on many routers and network interface cards.) If the far end

(an AP, a BH, a router) has been set to auto-negotiate, then the CMMmicro links at 100Base-T. Full Duplex A red dot indicates that the port has auto-negotiated to a Full Duplex connection. A grey dot indicates that the port has auto-negotiated to a Half Duplex connection. (This convention is also used on many routers and network interface cards.) Issue2,November2007 Draft5forRegulatoryReview 222 Release8 InstallationandConfigurationGuide Powered A red dot indicates that the port is powered with 24 V DC to provide power to an AP or BH. A grey dot indicates that the port is not powered. Port power is turned on and off in the Port Power Control parameter of the Configuration page. A CMMmicro comes from the factory with no Ethernet ports powered. CAUTION!

Never connect any devices other than Cyclone APs and BHs to a powered port. Powered ports are indicated by a red LED to the right of the port. (See Item 7 in Figure 69 on Page 220.) A powered port has 24-V DC on Pins 7 and 8 and 24-V return on Pins 4 and 5. This can damage other networking equipment, such as a computer or a router. Uplink A red dot indicates this link has been configured as an uplink using the CMMmicros Configuration page. Device Type This field displays the MAC address of the CMMmicro. PLD Version This field displays the version of the PLD (Programmable Logic Device) that is installed in the module. Before you request technical support, note this information. Software Version This field displays the version of the software that is installed in the module. Before you request technical support, note this information. System Time This field displays the current time. If the CMMmicro receives the signal from a GPS antenna, then this field expresses the time in Greenwich Mean Time (GMT). Satellites Visible This field displays how many satellites the GPS antenna sees. This differs from the Satellites Tracked field (described below). NOTE:

Latitude If the CMMmicro receives the signal from a GPS antenna, then this field displays the latitude of the site. Issue2,November2007 Draft5forRegulatoryReview 223 Release8 InstallationandConfigurationGuide Height If the CMMmicro receives the signal from a GPS antenna, then this field displays the elevation (above sea level) of the GPS antenna. Uptime This field displays how much time has elapsed since the last boot of the CMMmicro. Satellites Tracked This field displays how many satellites the CMMmicro is tracking. Longitude If the CMMmicro receives the signal from a GPS antenna, then this field displays the longitude of the site. Tracking Mode If the CMMmicro receives the signal from a GPS antenna, then this field describes how the CMMmicro is tracking satellites. Sync Pulse Status This field indicates the status of sync pulse that the CMMmicro is currently able to provide to connected modules. Site Name This field displays administrative information that has been entered on the Configuration page of the CMMmicro. Site Contact This field displays administrative information that has been entered on the Configuration page of the CMMmicro. Issue2,November2007 Draft5forRegulatoryReview 224 Release8 16.5.3 ConfigurationPageoftheCMMmicro InstallationandConfigurationGuide An example of the CMMmicro Configuration page is displayed in Figure 72. Figure 72: Configuration page of CMMmicro, example Issue2,November2007 Draft5forRegulatoryReview 225 Release8 InstallationandConfigurationGuide The Configuration web page contains all of the configurable parameters that define how the CMMmicro operates. The first line of information on the Configuration screen echoes the Device Type from the Status web page. IMPORTANT!

Changes that are made to the following parameters become effective when you click the Save Changes button:

Port Configuration

Description

Webpage Auto Update Power Port Control When these parameters listed above have become effective, if you click the Undo Saved Changes button, the previous values are not restored. Changes that are made to all other parameters become effective only after all of the following have occurred:

you have clicked the Save Changes button. you click the Reboot button. the CMMmicro reboots. Procedure 18: Setting CMMmicro parameters for test To continue the test setup, configure 1. 2. 3. 4. 5. the GPS Timing Pulse parameter. the Lan1 IP parameter. the Lan1 Subnet Mask parameter. the Default Gateway parameter. the Port Power Control parameter. end of procedure GPS Timing Pulse Select Master. (Slave is for future use.) IMPORTANT!

If the GPS Timing Pulse is set to Slave, the CMMmicro GPS receiver is disabled. Issue2,November2007 Draft5forRegulatoryReview 226 Release8 InstallationandConfigurationGuide Lan1 IP Enter the IP address to be associated with the Ethernet connection on this CMMmicro. The default address is 169.254.1.1. If you set and then forget this parameter, then you must both 1. physically access the module. 2. use the CMMmicro override toggle switch to electronically access the module configuration parameters at 169.254.1.1. See Overriding Forgotten IP Addresses or Passwords on CMMmicro on Page 381. RECOMMENDATION:

Note or print the IP settings from this page. Ensure that you can readily associate these IP settings both with the module and with the other data that you store about the module. LAN Subnet Mask Enter the appropriate subnet mask for the module to communicate on the network. The default value for this parameter is 255.255.255.0. Default Gateway Enter the appropriate gateway for the module to communicate on the network. The default for this parameter is 169.254.0.0. Port Configuration If you wish to force a port to a speed or duplex state, or to return the module to auto-

negotiating speed and duplex state, change the selection for the port. The range of selections are defined in Table 42. Table 42: Port Configuration selections for CMMmicro Selection Auto 100FDX 100HDX 10FDX 10HDX Result The port attempts to auto-negotiate speed and duplex state.

(This is the default and recommended setting.) The port is forced to 100 Mbps and full duplex. The port is forced to 100 Mbps and half duplex. The port is forced to 10 Mbps and full duplex. The port is forced to 10 Mbps and half duplex. If you change this value for a port and then click Save Changes, then the change becomes effective immediately and the previous value is lost. Description You can enter text in this parameter (for example, text that helps you to associate the port number with the connected device.) If you change this value for a port and then click Save Changes, then the change becomes effective immediately and the previous value is lost. Issue2,November2007 Draft5forRegulatoryReview 227 Release8 InstallationandConfigurationGuide Power Port Control Ensure that power is off for every port that connects to a router, computer, or other network equipment. Turn on 24-V DC power for ports that connect to Cyclone APs or BHs. CAUTION!

Never connect any devices other than Cyclone APs and BHs to a powered port. Powered ports are indicated by a red LED to the right of the port. (See Item 7 in Figure 69 on Page 220.) A powered port has 24-V DC on Pins 7 and 8 and 24-V return on Pins 4 and 5. This can damage other networking equipment, such as a computer or a router. If you change this value for a port and then click Save Changes, then the change becomes effective immediately and the previous value is lost. Display-Only Access To set this password, enter the same expression in both Display-Only Access fields for verification. When the web-based interface prompts for this password, no user name is required. However, when a telnet or FTP session prompts for this password, you must enter the user name root in addition to the password. If you set and then forget the Display-Only Access password, then you must both 1. physically access the module. 2. use the CMMmicro override toggle switch to electronically access the module configuration parameters at 169.254.1.1. See Overriding Forgotten IP Addresses or Passwords on CMMmicro on Page 381. Full Access If you set the Full Access password, this password will allow

telnet and FTP access to the module. viewing or changing the parameters of the module. To set this password, enter the same expression in both Full Access fields for verification. When the web-based interface prompts for this password, no user name is required. However, when a telnet or FTP session prompts for this password, you must enter the user name root in addition to the password. If you set and then forget the Full Access password, then you must both 1. physically access the module. 2. use the CMMmicro override toggle switch to electronically access the module configuration parameters at 169.254.1.1. See Overriding Forgotten IP Addresses or Passwords on CMMmicro on Page 381. Issue2,November2007 Draft5forRegulatoryReview 228 Release8 InstallationandConfigurationGuide NOTE:

You can unset either password (revert the access to no password required). To do so, type a space into the field and reboot the module. You must enter any password twice to allow the system to verify that the password is not mistyped. After any password is set and a reboot of the module has occurred, a Password Set indicator appears to the right of the field. RECOMMENDATION:

Note the passwords that you enter. Ensure that you can readily associate these passwords both with the module and with the other data that you store about the module. Webpage Auto Update Enter the frequency (in seconds) for the web browser to automatically refresh the web-

based interface. The default setting is 0. The 0 setting causes the web-based interface to never be automatically refreshed. If you change this value and then click Save Changes, then the change becomes effective immediately and the previous value is lost. SNMP Community String Specify a control string that allows an Network Management Station (NMS) to access SNMP information. No spaces are allowed in this string. The default string is Cyclone. The SNMP Community String value is clear text and is readable by a packet monitor. Additional security derives from the configuration of the SNMP Accessing Subnet, Trap Address, and Permission parameters. SNMP Accessing Subnet Specify the addresses that are allowed to send SNMP requests to this CMMmicro. The NMS has an address that is among these addresses (this subnet). You must enter both

The network IP address in the form xxx.xxx.xxx.xxx

The CIDR (Classless Interdomain Routing) prefix length in the form /xx For example

the /16 in 198.32.0.0/16 specifies a subnet mask of 255.255.0.0 (the first 16 bits in the address range are identical among all members of the subnet). 192.168.102.0 specifies that any device whose IP address is in the range 192.168.102.0 to 192.168.102.254 can send SNMP requests to the CMMmicro, presuming that the device supplies the correct SNMP Community String value. Issue2,November2007 Draft5forRegulatoryReview 229 Release8 InstallationandConfigurationGuide RECOMMENDATION:

For more information on CIDR, execute an Internet search on Classless Interdomain Routing. The default treatment is to allow all networks access. Trap Address Specify the IP address (xxx.xxx.xxx.xxx) of one to ten servers (Prizm or NMS) to which trap information should be sent. Trap information informs the monitoring systems that something has occurred. For example, trap information is sent after a reboot of the module.

when Prizm or an NMS attempts to access agent information but either

supplied an inappropriate community string or SNMP version number.

is associated with a subnet to which access is disallowed. Permission Select Read Only if you wish to disallow any parameter changes by Prizm or an NMS. Site Name Specify a string to associate with the physical module. This parameter is written into the sysName SNMP MIB-II object and can be polled by an NMS. The buffer size for this field is 128 characters. Site Contact Enter contact information for the module administrator. This parameter is written into the sysContact SNMP MIB-II object and can be polled by an NMS. The buffer size for this field is 128 characters. Site Location Enter information about the physical location of the module. This parameter is written into the sysLocation SNMP MIB-II object and can be polled by an NMS. The buffer size for this field is 128 characters. The CMMmicro Configuration page also provides the following buttons. Enable 802.1Q Tagging Once 802.1Q Tagging is enabled and an 802.1Q VLAN ID is set, only frames that are VLAN tagged with the configured tag value will be accepted by the management controller of the CMMmicro. All frames outgoing from the management controller of the CMMmicro will have an 802.1Q VLAN tag, set to the configured VLAN ID. 802.1Q VLAN ID Once 802.1Q Tagging is enabled and an 802.1Q VLAN ID is set, only frames that are VLAN tagged with the configured tag value will be accepted by the management controller of the CMMmicro. All frames outgoing from the management controller of the CMMmicro will have an 802.1Q VLAN tag, set to the configured VLAN ID. Issue2,November2007 Draft5forRegulatoryReview 230 Release8 InstallationandConfigurationGuide VLAN Port Configuration Each column in the VLAN Port Configuration section of Figure 72 corresponds to a port. Checkboxes in each column control which ports can transmit traffic that arrives on the

(column) port. For example, in the first column if only Port 2 is checked, then Port 1

(column 1) will only be allowed to send data out on Port 2 (checked box). Port 2 (second column) is able to send data out on all other ports. All other ports, meanwhile, are only allowed to send data out on Port 2. This configuration is also known as an Uplink configuration for Port 2. Each direction (for example, port 1 to port 2 versus port 2 to port 1) must be configured separately. It is possible to configure a port to send data to a second port, but not allow the second port to send data back to the first port (for example, check Port 8 in the Port 2 column, but do not check Port 2 in the Port 8 column). These settings should be changed with caution, and with two-way communication in mind. In all cases, even when not checked, all ports will still be able to communicate with the CMMmicro management controller. Setting (checking) any Uplink Port checkboxes (see Figure 72) will override VLAN Port Configuration settings. If you desire complete control on a port-by-port basis using VLAN Port Configuration, all Uplink Port boxes must be unchecked in the Uplink Port section. Save Changes, Undo Saved Changes, Set to Defaults, Reboot The effects of clicking these buttons are defined in Table 43. Table 43: When changes become effective in CMMmicro For these parameters clicking this button has this effect. Save Changes Any change becomes effective immediately and any previous setting is lost. Reboot Save Changes Set to Defaults Undo Saved Changes No change is undone, and no previous setting is restored. The default setting is not restored. No change that is not already effective becomes effective. Any change is recorded into flash memory but does not become effective immediately, and any previous setting can be restored. Any change recorded into flash memory is undone, and the previous setting is restored. The default setting is restored. Any change recorded in flash memory (and not later undone) becomes effective. Undo Saved Changes Set to Defaults Reboot Port Configuration Description Power Port Control Webpage Auto Update Any other parameter Issue2,November2007 Draft5forRegulatoryReview 231 Release8 InstallationandConfigurationGuide In addition, when you click Reboot, the following events occur and are logged:

The CMMmicro reboots.

Any AP or BH that receives power from the CMMmicro loses power and thus also reboots.

Any AP or BH that does not receive power but receives sync from the CMMmicro loses and then regains sync. 16.5.4 ConfiguringModulesforConnectiontoCMMmicro After configuring the CMMmicro, configure the APs and BHs as follows. In each AP or BH that connects to a CMMmicro, you must set the Sync Input parameter of the Configuration page of that module to Sync to Received Signal (Power Port). See

Sync Input on Page 239.

Sync Input on Page 299. 16.5.5 EventLogPageoftheCMMmicro This page may contain information that can be useful under the guidance of Cyclone technical support. For this reason, the operator should not clear the contents of this page before contacting technical support. 16.5.6 GPSStatusPageoftheCMMmicro An example of the CMMmicro GPS Status page is displayed in Figure 73. Figure 73: GPS Status page of CMMmicro, example Issue2,November2007 Draft5forRegulatoryReview 232 Release8 InstallationandConfigurationGuide The GPS Status page provides information from the GPS antenna and information about the GPS receiver in the CMMmicro. Antenna Connection This field displays the status of the signal from the antenna as follows:

OK indicates that the GPS interface board is detecting an incoming signal on the coaxial cable from the GPS antenna.

No Antenna indicates the GPS interface board is not detecting any incoming signal. The other GPS Status fields are described under Satellites Visible on Page 223. GPS Receiver Information This field displays information about the GPS interface board. 16.5.7 PortMIBPageoftheCMMmicro An example of the Port MIB (Ethernet statistics) web page is displayed in Figure 74. Figure 74: Port MIB page of CMMmicro, example The Port MIB page displays Ethernet statistics and traffic information for the ports on the managed switch. To display the port statistics, click on a port number. Issue2,November2007 Draft5forRegulatoryReview 233 Release8 InstallationandConfigurationGuide Ports 1 through 8 are the regular ports, connected to APs, BHs, or other network elements. Port 9 is the connection between the managed switch and the CMMmicro processor. Thus, updates to interface pages, SNMP activities, and FTP and telnet sessions create traffic on Port 9. These Ethernet statistics can also be retrieved from the CMMmicro by a Network Management Station using SNMP. During advanced troubleshooting, this information can be useful as you see the activity on a single port or as you compare activity between ports of the CMMmicro. Issue2,November2007 Draft5forRegulatoryReview 234 Release8 17 PREPARINGCOMPONENTSFORDEPLOYMENT Your test of the modules not only verified that they are functional, but also yielded data that you have stored about them. Most efficiently preparing modules for deployment involves InstallationandConfigurationGuide

retrieving that data. systematically collecting the data into a single repository, while keeping a strong

(quick) association between the data and the module. immediately merging module access data into this previously stored data. 17.1 CORRELATINGCOMPONENTSPECIFICINFORMATION You can use the data that you noted or printed from the Status pages of the modules to

store modules for future deployment. know, at a glance, how well-stocked you are for upcoming network expansions. efficiently draw modules from stock for deployment. plan any software updates that you

wish to perform to acquire features.

need to perform to have the feature set be consistent among all modules in a network expansion. You can make these tasks even easier by collecting this data into a sortable database. 17.2 ENSURINGCONTINUINGACCESSTOTHEMODULES As you proceed through the steps under Configuring for the Destination on Page 237, you will set values for parameters that specify the sync source, data handling characteristics, security measures, management authorities, and other variables for the modules. While setting these, you will also tighten access to the module, specifically in

the Color Code parameter of Configuration page the Display-Only Access and Full Access password parameters of the Configuration page. the addressing parameters of the IP Configuration page. Before you set these, consider whether and how you may want to set these by a self-

devised scheme. A password scheme can help you when you have forgotten or misfiled a password. An IP addressing scheme may be essential to the operation of your network and to future expansions of your network. As you set these, note the color code and note or print the parameters you set on the Configuration page tabs. Immediately associate them with the following previously stored data about the modules:

device type, frequency band, and MAC address software version and encryption type software boot version

FPGA version Issue2,November2007 Draft5forRegulatoryReview 235 Release8 18 CONFIGURINGFORTHEDESTINATION InstallationandConfigurationGuide 18.1 CONFIGURINGANAPFORTHEDESTINATION If an ADMINISTRATOR-level password has been set in the AP, you must log into the module before you can configure its parameters. See Managing Module Access by Passwords on Page 377. 18.1.1 GeneralTaboftheAP An example of an AP General tab is displayed in Figure 75. Issue2,November2007 Draft5forRegulatoryReview 237 Release8 InstallationandConfigurationGuide Figure 75: General tab of AP, example The General tab of the AP contains many of the configurable parameters that define how the AP and the SMs in the sector operate. As shown in Figure 75, you may set the Configuration page parameters as follows. Issue2,November2007 Draft5forRegulatoryReview 238 Release8 InstallationandConfigurationGuide Device Setting You can temporarily transform an AP into an SM and thereby use the spectrum analyzer functionality. See Using the AP as a Spectrum Analyzer on Page 370. Otherwise, the selection for this parameter is AP. Link Speeds Specify the type of link speed for the Ethernet connection. The default for this parameter is that all speeds are selected. The recommended setting is a single speed selection for all APs, BHs, and SMs in the operator network. Configuration Source See Setting the Configuration Source on Page 295. CAUTION!

Do not set this parameter to BAM where both

a BAM release earlier than 2.1 is implemented. the All Local SM Management parameter (in the VLAN Configuration page of the AP) is set to Enable. This combination causes the SMs to become unmanageable, until you gain direct access with an Override Plug and remove this combination from the AP configuration. Sync Input Specify the type of synchronization for this AP to use:

Select Sync to Received Signal (Power Port) to set this AP to receive sync from a connected CMMmicro.

Select Sync to Received Signal (Timing Port) to set this AP to receive sync from a connected CMM2, an AP in the cluster, an SM, or a BH timing slave. Select Generate Sync Signal where the AP does not receive sync, and no other AP or BHM is active within the link range. Webpage Auto Update Enter the frequency (in seconds) for the web browser to automatically refresh the web-

based interface. The default setting is 0. The 0 setting causes the web-based interface to never be automatically refreshed. Bridge Entry Timeout Specify the appropriate bridge timeout for correct network operation with the existing network infrastructure. The Bridge Entry Timeout should be a longer period than the ARP

(Address Resolution Protocol) cache timeout of the router that feeds the network. Issue2,November2007 Draft5forRegulatoryReview 239 Release8 InstallationandConfigurationGuide CAUTION!

An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of communication with some end users. Translation Bridging If you want the Translation Bridging feature, select Enabled. This has numerous implications. For a full description of them, see Uplink Frame Contents on Page 81. Send Untranslated ARP If the Translation Bridging parameter is set to Enabled, then the Send Untranslated ARP parameter can be disabled, so that the AP will overwrite the MAC address in Address Resolution Protocol (ARP) packets before forwarding them. enabled, so that the AP will forward ARP packets regardless of whether it has overwritten the MAC address. See Uplink Frame Contents on Page 81 and Address Resolution Protocol on Page 162. If the Translation Bridging parameter is set to Disabled, then the Send Untranslated ARP parameter has no effect. SM Isolation Prevent or allow SM-to-SM communication by selecting from the following drop-down menu items:

Disable SM Isolation (the default selection). This allows full communication between SMs. Block SM Packets from being forwarded. This prevents both multicast/broadcast and unicast SM-to-SM communication. Block and Forward SM Packets to Backbone. This not only prevents multicast/broadcast and unicast SM-to-SM communication but also sends the packets, which otherwise would have been handled SM to SM, through the Ethernet port of the AP. Update Application Address Enter the address of the server to access for software updates on this AP and registered SMs. 2X Rate See 2X Operation on Page 90. Prioritize TCP ACK To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. See AP-

SM Links on Page 99. The General tab also provides the following buttons. Issue2,November2007 Draft5forRegulatoryReview 240 Release8 InstallationandConfigurationGuide Save Changes When you click this button, any changes that you made on the this tab are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. 18.1.2 IPTaboftheAP An example of the IP tab of the AP is displayed in Figure 76. Figure 76: IP tab of AP, example Issue2,November2007 Draft5forRegulatoryReview 241 Release8 You may set the IP tab parameters as follows. InstallationandConfigurationGuide LAN1 Network Interface Configuration, IP Address Enter the non-routable IP address to associate with the Ethernet connection on this AP.

(The default IP address from the factory is 169.254.1.1.) If you set and then forget this parameter, then you must both 1. physically access the module. 2. use an override plug to electronically access the module configuration parameters at 169.254.1.1. See Overriding Forgotten IP Addresses or Passwords on AP, SM, or BH on Page 381. RECOMMENDATION:

Note or print the IP settings from this page. Ensure that you can readily associate these IP settings both with the module and with the other data that you store about the module. LAN1 Network Interface Configuration, Subnet Mask Enter an appropriate subnet mask for the AP to communicate on the network. The default subnet mask is 255.255.0.0. See Allocating Subnets on Page 162. LAN1 Network Interface Configuration, Gateway IP Address Enter the appropriate gateway for the AP to communicate with the network. The default gateway is 169.254.0.0. The values of these four LAN1 network interface configuration parameters are displayed read only along with the Ethernet speed and duplex state on the Network Interface tab of the Home page in the AP. LAN1 Network Interface Configuration, DHCP State If you select Enabled, the DHCP server automatically assigns the IP configuration

(IP address, subnet mask, and gateway IP address) and the values of those individual parameters (above) are not used. The setting of this DHCP state parameter is also viewable, but not settable, in the Network Interface tab of the Home page. LAN2 Network Interface Configuration (RF Private Interface), IP Address You should not change this parameter from the default AP private IP address of 192.168.101.1. A /24 CIDR subnet is used to communicate with each of the SMs that are registered. The AP uses a combination of the private IP and the LUID (logical unit ID) of the SM. For example, if an SM is the first to register in an AP, and another SM registers later, then the AP whose Private IP address is 192.168.101.1 uses the following SM Private IP addresses to communicate to each:

SM LUID Private IP First SM registered Second SM registered 2 3 192.168.101.2 192.168.101.3 Issue2,November2007 Draft5forRegulatoryReview 242 Release8 InstallationandConfigurationGuide NOTE:

Where space is limited for subnet allocation, be advised that an SM need not have an operator-assigned IP address. The SM is directly accessible without an LUID if either the SM Color Code parameter is set to 0 or the AP has a direct Ethernet connection to the SM. The IP Configuration page also provides the following buttons. Save Changes When you click this button, any changes that you made on this tab are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. 18.1.3 RadioTaboftheAP An example of the Radio tab of the AP is shown in Figure 77. Figure 77: Radio tab of AP (900 MHz), example Issue2,November2007 Draft5forRegulatoryReview 243 Release8 InstallationandConfigurationGuide The Radio tab of the AP contains some of the configurable parameters that define how the AP operates. As shown in Figure 77, you may set the Radio tab parameters as follows. Radio Frequency Carrier Specify the frequency for the module to transmit. The default for this parameter is None.

(The selection labeled Factory requires a special software key file for implementation.) For a list of channels in the band, see the drop-down list or Considering Frequency Band Alternatives on Page 136. Color Code Specify a value from 0 to 254. For registration to occur, the color code of the SM and the AP must match. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. Color code allows you to force an SM to register to only a specific AP, even where the SM can communicate with multiple APs. On all Cyclone modules, the default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). RECOMMENDATION:

Note the color code that you enter. Ensure that you can readily associate this color code both with the module and with the other data that you store about the module. Sector ID Specify a number in the range 1 to 6 to associate with this AP. The Sector ID setting does not affect the operation of the AP. On the AP Evaluation tab of the Tools page in the SM, the Sector ID field identifies the AP that the SM sees. The following steps may be useful:

Assign a unique Sector ID to each sector in an AP cluster.

Repeat the assignment pattern throughout the entire Cyclone system. Max Range Enter a number of miles (or kilometers divided by 1.61, then rounded to an integer) for the furthest distance from which an SM is allowed to register to this AP. Do not set the distance to any greater number of miles. A greater distance

does not increase the power of transmission from the AP. can reduce aggregate throughput. See Table 24 on Page 100. Regardless of this distance, the SM must meet the minimum requirements for an acceptable link. If the AP is in cluster, then you must set this parameter on all other APs in the cluster exactly the same, except as described in the NOTE admonition below. The default value of this parameter is 2 miles (3.2 km). For APs in the non 900-MHz frequency band ranges, although the typical maximum range where an SM is deployed with a reflector is 15 miles (24 km), you can set this parameter to as far as 30 miles (48 km). Without increasing the power or sensitivity of the Issue2,November2007 Draft5forRegulatoryReview 244 Release8 InstallationandConfigurationGuide AP or SM, the greater value allows you to attempt greater distance where the RF environment and Fresnel zone6 are especially clear. A value of 15 for this parameter decreases the number of available data slots by 1. With a higher value, the number is further decreased as the AP compensates for the expected additional air delay. NOTE:

In a cluster where at least one AP has Scheduling set to Software and at least one to Hardware, you must use the Frame Calculator web page to coordinate the transmit and receive times and you may further need to adjust the value of the Max Range parameter for individual APs in the cluster to avoid self interference. See Using the Frame Calculator Tool (All) on Page 444. Downlink Data Specify the percentage of the aggregate throughput for the downlink (frames transmitted from the AP to the subscriber). For example, if the aggregate (uplink and downlink total) throughput on the AP is 6 Mb, then 75% specified for this parameter allocates 4.5 Mb for the downlink and 1.5 Mb for the uplink. The default for this parameter is 75%. CAUTION!

You must set this parameter exactly the same for all APs in a cluster. Control Slots The recommended number of control slots is as stated in Table 44. Table 44: Control slot settings for all APs in cluster Number of SMs that Register to the AP 1 to 10 11 to 50 51 to 150 151 to 200 Number of Control Slots Recommended 0 1 2 3 Slots reserved for control are used for only SM service requests. For data, the hardware scheduler uses unreserved slots first, then any unused slots are available with any reserved slots to the SMs for service requests. 6 See Noting Possible Obstructions in the Fresnel Zone on Page 67. Issue2,November2007 Draft5forRegulatoryReview 245 Release8 InstallationandConfigurationGuide If too few reserved control slots are specified, then latency increases in high traffic periods. If too many are specified, then the maximum capacity is unnecessarily reduced. External Filters Delay This parameter is present in only 900-MHz modules and can have effect in only those that have interference mitigation filter(s). Leave this value set to 0, regardless of whether the AP has an interference mitigation filter. Transmit Frame Spreading Where multiple AP clusters operate in the same frequency band range and same geographical area, select Enable. Then SMs between two APs can register in the assigned AP (do not register in another AP). Where multiple AP clusters do not operate in the same frequency band range and same geographical area, select Disable, but observe the following caveat. IMPORTANT!

SM throughput is 10% greater with this feature disabled. However, if you disable Transmit Frame Spreading where this feature was previously enabled, monitor the zone for interference over a period of days to ensure that this action has not made any SMs sensitive to the wrong beacon. With this selection enabled, the AP does not transmit a beacon in each frame, but rather transmits a beacon in only pseudo-random frames in which the SM expects the beacon. This allows multiple APs to send beacons to multiple SMs in the same range without interference. Transmitter Output Power Nations and regions may regulate transmitter output power. For example Both 900-MHz and 5.7-GHz modules are available as connectorized radios, which require the operator to adjust power to ensure regulatory compliance. In addition to setting the power in the 5.7-GHz connectorized module, the operator must set the antenna gain/cable loss such that the module can accurately report received power at the antenna. Legal maximum allowable transmitter output power and EIRP (Equivalent Isotropic Radiated Power) in the 2.4-GHz frequency band varies by country and region. The output power of Series P9 2.4-GHz modules can be adjusted to meet these national or regional regulatory requirements. Countries and regions that permit the use of the 5.4-GHz frequency band (CEPT member states, for example), generally require equipment using the band to have adjustable power. The professional installer of Cyclone equipment has the responsibility to

maintain awareness of applicable regulations.

calculate the permissible transmitter output power for the module. confirm that the initial power setting is compliant with national or regional regulations. Issue2,November2007 Draft5forRegulatoryReview 246 Release8 InstallationandConfigurationGuide

confirm that the power setting is compliant following any reset of the module to factory defaults. For information on how to calculate the permissible transmitter output power to enter in this parameter, see Adjusting Transmitter Output Power on Page 330. The Radio tab also provides the following buttons. Save Changes When you click this button, any changes that you made on this tab are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 247 Release8 18.1.4 SNMPTaboftheAP InstallationandConfigurationGuide An example of the SNMP tab of the AP is displayed in Figure 78. Figure 78: SNMP tab of AP, example Issue2,November2007 Draft5forRegulatoryReview 248 Release8 InstallationandConfigurationGuide You may set the SNMP tab parameters as follows. Community String Specify a control string that allows an Network Management Station (NMS) to access SNMP information. No spaces are allowed in this string. The default string is Cyclone. The Community String value is clear text and is readable by a packet monitor. Additional security derives from the configuration of the Accessing Subnet, Trap Address, and Permission parameters. Accessing Subnet Specify the addresses that are allowed to send SNMP requests to this AP. The NMS has an address that is among these addresses (this subnet). You must enter both

The network IP address in the form xxx.xxx.xxx.xxx

The CIDR (Classless Interdomain Routing) prefix length in the form /xx For example

the /16 in 198.32.0.0/16 specifies a subnet mask of 255.255.0.0 (the first 16 bits in the address range are identical among all members of the subnet). 192.168.102.0 specifies that any device whose IP address is in the range 192.168.102.0 to 192.168.102.254 can send SNMP requests to the AP, presuming that the device supplies the correct Community String value. The default treatment is to allow all networks access. For more information on CIDR, execute an Internet search on Classless Interdomain Routing. Trap Address 1 to 10 Specify ten or fewer IP addresses (xxx.xxx.xxx.xxx) to which SNMP traps should be sent. Traps inform Prizm or an NMS that something has occurred. For example, trap information is sent after a reboot of the module.

when an NMS attempts to access agent information but either

supplied an inappropriate community string or SNMP version number.

is associated with a subnet to which access is disallowed. Trap Enable, Sync Status If you want sync status traps (sync lost and sync regained) sent to Prizm or an NMS, select Enabled. If you want these traps suppressed, select Disabled. Trap Enable, Session Status If you want session status traps sent to Prizm or an NMS, select Enabled. For the names and descriptions of session status traps, see Traps Provided in the Cyclone Enterprise MIB on Page 410. If you want these traps suppressed, select Disabled. Read Permissions Select Read Only if you wish to disallow any parameter changes through SNMP

(for example, from Prizm or an NMS). Issue2,November2007 Draft5forRegulatoryReview 249 Release8 InstallationandConfigurationGuide Site Name Specify a string to associate with the physical module. This parameter is written into the sysName SNMP MIB-II object and can be polled by PrizmEMS or an NMS. The buffer size for this field is 128 characters. Site Contact Enter contact information for the module administrator. This parameter is written into the sysContact SNMP MIB-II object and can be polled by PrizmEMS or an NMS. The buffer size for this field is 128 characters. Site Location Enter information about the physical location of the module. This parameter is written into the sysLocation SNMP MIB-II object and can be polled by PrizmEMS or an NMS. The buffer size for this field is 128 characters. The SNMP tab also provides the following buttons. Save Changes When you click this button, any changes that you made on this tab are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 250 Release8 18.1.5 QualityofService(QoS)TaboftheAP InstallationandConfigurationGuide An example of the Quality of Service (QoS) tab of the AP is displayed in Figure 79. Figure 79: Quality of Service (QoS) tab of AP, example In the Quality of Service (QoS) tab, you may set AP bandwidth parameters as follows. Sustained Uplink Data Rate Specify the rate that each SM registered to this AP is replenished with credits for transmission. This default imposes no restriction on the uplink. See Maximum Information Rate (MIR) Parameters on Page 84 Setting the Configuration Source on Page 295. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 86 Uplink Burst Allocation Specify the maximum amount of data to allow each SM to transmit before being recharged at the Sustained Uplink Data Rate with credits to transmit more. See Maximum Information Rate (MIR) Parameters on Page 84 Setting the Configuration Source on Page 295. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 86 Issue2,November2007 Draft5forRegulatoryReview 251 Release8 InstallationandConfigurationGuide Sustained Downlink Data Rate Specify the rate at which the AP should be replenished with credits (tokens) for transmission to each of the SMs in its sector. This default imposes no restriction on the uplink. See Maximum Information Rate (MIR) Parameters on Page 84 Setting the Configuration Source on Page 295. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 86 Downlink Burst Allocation Specify the maximum amount of data to allow the AP to transmit to any registered SM before the AP is replenished with transmission credits at the Sustained Downlink Data Rate. See Maximum Information Rate (MIR) Parameters on Page 84 Setting the Configuration Source on Page 295. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 86 The Quality of Server (QoS) tab also provides the following buttons. Save Changes When you click this button, any changes that you made on this tab are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 252 Release8 18.1.6 SecurityTaboftheAP InstallationandConfigurationGuide An example of the Security tab of the AP is displayed in Figure 80. Figure 80: Security tab of AP, example In the Security tab of the AP, you may set the following parameters. Issue2,November2007 Draft5forRegulatoryReview 253 Release8 InstallationandConfigurationGuide Authentication Mode If the AP has authentication capability, then you can use this field to select from among the following authentication modes:

Authentication Disabledthe AP requires no SMs to authenticate.

Authentication Requiredthe AP requires any SM that attempts registration to be authenticated in BAM or Prizm before registration. If the AP does not have authentication capability, then this parameter displays Authentication Not Available. Authentication Server 1 to 3 If either BAM or the BAM subsystem in Prizm is implemented and the AP has authentication capability, enter the IP address of one or more BAM servers that perform authentication for SMs registered to this AP. Enter these in order of primary, secondary, then tertiary. Encryption Specify the type of air link security to apply to this AP:

Encryption Disabled provides no encryption on the air link. This is the default mode.

Encryption Enabled provides encryption, using a factory-programmed secret key that is unique for each module. Encrypt Downlink Broadcast When Encryption Enabled is selected in the Airlink Security parameter (described above) and Enable is selected in the Encrypt Downlink Broadcast parameter, the AP encrypts downlink broadcast packets as

DES where the AP is DES capable.

AES where the AP is AES capable. For more information about the Encrypt Downlink Broadcast feature, see Encrypting Downlink Broadcasts on Page 384. SM Display of AP Evaluation Data You can use this field to suppress the display of data about this AP on the AP Evaluation tab of the Tools page in all SMs that register. Web, Telnet, FTP Session Timeout Enter the expiry in seconds for remote management sessions via HTTP, telnet, or ftp access to the AP. IP Access Control You can permit access to the AP from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address, including access and management by Prizm. Issue2,November2007 Draft5forRegulatoryReview 254 Release8 InstallationandConfigurationGuide Allowed Source IP 1 to 3 If you selected IP Access Filtering Enabled for the IP Access Control parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the AP from any IP address. You may populate as many as all three. If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. The Security tab of the AP also provides the following buttons. Save Changes When you click this button, any changes that you made on this tab are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 255 Release8 18.1.7 VLANTaboftheAP InstallationandConfigurationGuide An example of the AP VLAN tab is displayed in Figure 81. Figure 81: VLAN tab of AP, example In the VLAN tab of the AP, you may set the following parameters. VLAN Specify whether VLAN functionality for the AP and all linked SMs should (Enabled) or should not (Disabled) be allowed. The default value is Disabled. Dynamic Learning Specify whether the AP should (Enabled) or should not (Disabled) add the VLAN IDs

(VIDs) of upstream frames to the VID table. (The AP passes frames with VIDs that are stored in the table both upstream and downstream.) The default value is Enabled. Allow Frame Types Select the type of arriving frames that the AP should tag, using the VID that is stored in the Untagged Ingress VID parameter. The default value is All Frames. Issue2,November2007 Draft5forRegulatoryReview 256 Release8 InstallationandConfigurationGuide VLAN Aging Timeout Specify how long the AP should keep dynamically learned VIDs. The range of values is 5 to 1440 (minutes). The default value is 25 (minutes). NOTE:

VIDs that you enter for the Management VID and VLAN Membership parameters do not time out. Management VID Enter the VID that the operator wishes to use to communicate with the module manager. The range of values is 1 to 4095. The default value is 1. SM Management VID Pass-through Specify whether to allow the SM (Enable) or the AP (Disable) to control the VLAN settings of this SM. The default value is Enable. CAUTION!

Do not set this parameter to Enable where both

a BAM release earlier than 2.1 is implemented. the Configuration Source parameter in the AP is set to BAM. This combination causes the SMs to become unmanageable, until you gain direct access with an override plug and remove this combination from the AP configuration. Save Changes When you click this button, any changes that you made on this tab are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 257 Release8 18.1.8 VLANMembershipTaboftheAP InstallationandConfigurationGuide An example of the VLAN Membership tab of the AP is displayed in Figure 82. Figure 82: VLAN Membership tab of AP, example You may set the VLAN Membership tab parameter as follows. VLAN Membership Table Configuration For each VLAN in which you want the AP to be a member, enter the VLAN ID and then click the Add Member button. Similarly, for any VLAN in which you want the AP to no longer be a member, enter the VLAN ID and then click the Remove Member button. Issue2,November2007 Draft5forRegulatoryReview 258 Release8 18.1.9 DiffServeTaboftheAP InstallationandConfigurationGuide An example of the DiffServe tab of the AP is displayed in Figure 83. Figure 83: DiffServe tab of AP, example Issue2,November2007 Draft5forRegulatoryReview 259 Release8 You may set the following DiffServe tab parameters. InstallationandConfigurationGuide CodePoint 1 through CodePoint 47 CodePoint 49 through CodePoint 55 CodePoint 57 through CodePoint 63 The default priority value for each settable CodePoint is shown in Figure 113. Priorities of 0 through 3 map to the low-priority channel;

4 through 7 to the high-priority channel. The mappings are the same as 802.1p VLAN priorities. Consistent with RFC 2474

CodePoint 0 is predefined to a fixed priority value of 0

(low-priority channel).

CodePoint 48 is predefined to a fixed priority value of 6

(high-priority channel).

CodePoint 56 is predefined to a fixed priority value of 7

(high-priority channel). You cannot change any of these three fixed priority values. Among the settable parameters, the priority values (and therefore the handling of packets in the high- or low-priority channel) are set in the AP for all downlinks within the sector and in the SM for each uplink. See DSCP Field on Page 87. The DiffServe tab also contains the following buttons. Save Changes When you click this button, any changes that you made on all tabs are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 260 Release8 18.1.10 UnitSettingsTaboftheAP InstallationandConfigurationGuide An example of the Unit Settings tab of the AP is shown in Figure 84. Figure 84: Unit Settings tab of AP, example The Unit Settings tab of the AP contains an option for how the AP should react when it detects a connected override plug. You may set this option as follows. Set to Factory Defaults Upon Default Plug Detection If Enabled is checked, then an override/default plug functions as a default plug. When the module is rebooted with the plug inserted, it can be accessed at the IP address 169.254.1.1 and no password, and all parameter values are reset to defaults. A subscriber, technician, or other person who gains physical access to the module and uses an override/default plug cannot see or learn the settings that were previously configured in it. When the module is later rebooted with no plug inserted, the module uses the new values for any parameters that were changed and the default values for any that were not. If Disabled is checked, then an override/default plug functions as an override plug. When the module is rebooted with the plug inserted, it can be accessed at the IP address 169.254.1.1 and no password, and all previously configured parameter values remain and are displayed. A subscriber, technician, or other person who gains physical access to the module and uses an override/default plug can see and learn the settings. When the module is later rebooted with no plug inserted, the module uses the new values for any parameters that were changed and the previous values for any that were not. See Overriding Forgotten IP Addresses or Passwords on AP, SM, or BH on Page 379. The Unit Settings tab also contains the following buttons. Issue2,November2007 Draft5forRegulatoryReview 261 Release8 InstallationandConfigurationGuide Save Changes When you click this button, any changes that you made on all tabs are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Undo Unit-Wide Saved Changes When you click this button, any changes that you made in any tab but did not commit by a reboot of the module are undone. Set to Factory Defaults When you click this button, all configurable parameters on all tabs are reset to the factory settings. 18.2 CONFIGURINGANSMFORTHEDESTINATION If an ADMINISTRATOR-level password has been set in the SM, you must log into the module before you can configure its parameters. See Managing Module Access by Passwords on Page 377. Issue2,November2007 Draft5forRegulatoryReview 262 Release8 18.2.1 GeneralTaboftheSM InstallationandConfigurationGuide An example of a General tab in the SM is displayed in Figure 85. Figure 85: General tab of SM, example In the General tab of the SM, you may set the following parameters. Link Speeds Specify the type of link speed for the Ethernet connection. The default for this parameter is that all speeds are selected. The recommended setting is a single speed selection for all APs, BHs, and SMs in the operator network. Issue2,November2007 Draft5forRegulatoryReview 263 Release8 InstallationandConfigurationGuide 802.3 Link Enable/Disable Specify whether to enable or disable Ethernet/802.3 connectivity on the wired port of the SM. This parameter has no effect on the wireless link. When you select Enable, this feature allows traffic on the Ethernet/802.3 port. This is the factory default state of the port. When you select Disable, this feature prevents traffic on the port. Typical cases of when you may want to select Disable include:

The subscriber is delinquent with payment(s). You suspect that the subscriber is sending or flooding undesired broadcast packets into the network, such as when

a virus is present in the subscriber's computing device.

the subscriber's home router is improperly configured. Webpage Auto Update Enter the frequency (in seconds) for the web browser to automatically refresh the web-

based interface. The default setting is 0. The 0 setting causes the web-based interface to never be automatically refreshed. Bridge Entry Timeout Specify the appropriate bridge timeout for correct network operation with the existing network infrastructure. Timeout occurs when the AP encounters no activity with the SM

(whose MAC address is the bridge entry) within the interval that this parameter specifies. The Bridge Entry Timeout should be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. This parameter governs the timeout interval, even if a router in the system has a longer timeout interval. The default value of this field is 25 minutes. CAUTION!

An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of communication with some end users. SM Power Up Mode With No 802.3 Link Specify the default mode in which this SM will power up when the SM senses no Ethernet link. Select either

Power Up in Aim Modethe SM boots in an aiming mode. When the SM senses an Ethernet link, this parameter is automatically reset to Power Up in Operational Mode. When the module senses no Ethernet link within 15 minutes after power up, the SM carrier shuts off.

Power Up in Operational Modethe SM boots in Operational mode. The module attempts registration. Unlike in previous releases, this is the default selection in Release 8. 2X Rate Disable this parameter to facilitate initial aiming from the destination. Then see 2X Operation on Page 90. Issue2,November2007 Draft5forRegulatoryReview 264 Release8 InstallationandConfigurationGuide Frame Timing Pulse Gated If this SM extends the sync pulse to a BH master or an AP, select either

EnableIf this SM loses sync from the AP, then do not propagate a sync pulse to the BH timing master or other AP. This setting prevents interference in the event that the SM loses sync.

DisableIf this SM loses sync from the AP, then propagate the sync pulse to the BH timing master or other AP. See Wiring to Extend Network Sync on Page 374. The General tab also contains the following buttons. Save Changes When you click this button, any changes that you made on all tabs are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. 18.2.2 NATandIPTabsoftheSMwithNATDisabled An example of the NAT tab in an SM with NAT disabled is displayed in Figure 86. Issue2,November2007 Draft5forRegulatoryReview 265 Release8 InstallationandConfigurationGuide Figure 86: NAT tab of SM with NAT disabled, example This implementation is illustrated in Figure 40 on Page 157. In the NAT tab of an SM with NAT disabled, you may set the following parameters. Issue2,November2007 Draft5forRegulatoryReview 266 Release8 InstallationandConfigurationGuide NAT Enable/Disable This parameter enables or disabled the Network Address Translation (NAT) feature for the SM. NAT isolates devices connected to the Ethernet/wired side of an SM from being seen directly from the wireless side of the SM. With NAT enabled, the SM has an IP address for transport traffic separate from its address for management, terminates transport traffic, and allows you to assign a range of IP addresses to devices that are connected to the Ethernet/wired side of the SM. For further information, see Network Address Translation (NAT) on Page 156 and NAT and IP Tabs of the SM with NAT Enabled on Page 271. NAT Private Network Interface Configuration, IP Address This parameter is not configurable when NAT is disabled. NAT Private Network Interface Configuration, Subnet Mask This parameter is not configurable when NAT is disabled. DMZ Host Interface Configuration, IP Address This parameter is not configurable when NAT is disabled. DMZ Enable This parameter is not configurable when NAT is disabled. NAT Public Network Interface Configuration, IP Address This field displays the IP address for the SM. DHCP Server will not automatically assign this address when NAT is disabled. NAT Public Network Interface Configuration, Subnet Mask This field displays the subnet mask for the SM. DHCP Server will not automatically assign this address when NAT is disabled. NAT Public Network Interface Configuration, Gateway IP Address This field displays the gateway IP address for the SM. DHCP Server will not automatically assign this address when NAT is disabled. DHCP Start IP This parameter is not configurable when NAT is disabled. Number of IPs to Lease This parameter is not configurable when NAT is disabled. Radio Public Network Interface Configuration, IP Address This parameter is not configurable when NAT is disabled. Radio Public Network Interface Configuration, Interface Enable/Disable This parameter is not configurable when NAT is disabled. Radio Public Network Interface Configuration, Subnet Mask This parameter is not configurable when NAT is disabled. Radio Public Network Interface Configuration, Gateway IP Address This parameter is not configurable when NAT is disabled. Issue2,November2007 Draft5forRegulatoryReview 267 Release8 Radio Public Network Interface Configuration, DHCP State This parameter is not configurable when NAT is disabled. InstallationandConfigurationGuide ARP Cache Timeout If a router upstream has an ARP cache of longer duration (as some use 30 minutes), enter a value of longer duration than the router ARP cache. The default value of this field is 20 minutes. TCP Session Garbage Timeout Where a large network exists behind the SM, you can set this parameter to lower than the default value of 1440 minutes (24 hours). This action makes additional resources available for greater traffic than the default value accommodates. UDP Session Garbage Timeout You may adjust this parameter in the range of 1 to 1440 minutes, based on network performance. The default value of this parameter is 4 minutes. DHCP Client Enable/Disable This parameter is not configurable when NAT is disabled. DHCP Server Enable/Disable This parameter is not configurable when NAT is disabled. DHCP Server Lease Timeout This parameter is not configurable when NAT is disabled. DNS IP Address This parameter is not configurable when NAT is disabled. Preferred DNS IP Address This parameter is not configurable when NAT is disabled. Alternate DNS IP Address This parameter is not configurable when NAT is disabled. The NAT tab also contains the following buttons. Save Changes When you click this button, any changes that you made on all tabs are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. An example of the IP tab in an SM with NAT disabled is displayed in Figure 87. Issue2,November2007 Draft5forRegulatoryReview 268 Release8 InstallationandConfigurationGuide Figure 87: IP tab of SM with NAT disabled, example This implementation is illustrated in Figure 40 on Page 157. In the IP tab of an SM with NAT disabled, you may set the following parameters. LAN1 Network Interface Configuration, IP Address Enter the non-routable IP address to associate with the Ethernet connection on this SM.

(The default IP address from the factory is 169.254.1.1.) If you set and then forget this parameter, then you must both 1. physically access the module. 2. use an override plug to electronically access the module configuration parameters at 169.254.1.1. See Overriding Forgotten IP Addresses or Passwords on AP, SM, or BH on Page 381. RECOMMENDATION:

Note or print the IP settings from this page. Ensure that you can readily associate these IP settings both with the module and with the other data that you store about the module. Issue2,November2007 Draft5forRegulatoryReview 269 Release8 InstallationandConfigurationGuide LAN1 Network Interface Configuration, Network Accessibility Specify whether the IP address of the SM should be visible to only a device connected to the SM by Ethernet (Local) or should be visible to the AP as well (Public). LAN1 Network Interface Configuration, Subnet Mask Enter an appropriate subnet mask for the SM to communicate on the network. The default subnet mask is 255.255.0.0. See Allocating Subnets on Page 162. LAN1 Network Interface Configuration, Gateway IP Address Enter the appropriate gateway for the SM to communicate with the network. The default gateway is 169.254.0.0. LAN1 Network Interface Configuration, DHCP State If you select Enabled, the DHCP server automatically assigns the IP configuration

(IP address, subnet mask, and gateway IP address) and the values of those individual parameters (above) are not used. The setting of this DHCP state parameter is also viewable, but not settable, in the Network Interface tab of the Home page. In this tab, DHCP State is settable only if the Network Accessibility parameter in the IP tab is set to Public. This parameter is also settable in the NAT tab of the Configuration web page, but only when NAT is enabled. The IP tab also contains the following buttons. Save Changes When you click this button, any changes that you made on all tabs are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 270 Release8 18.2.3 NATandIPTabsoftheSMwithNATEnabled InstallationandConfigurationGuide An example of the NAT tab in an SM with NAT enabled is displayed in Figure 88. Figure 88: NAT tab of SM with NAT enabled, example In the NAT tab of an SM with NAT enabled, you may set the following parameters. Issue2,November2007 Draft5forRegulatoryReview 271 Release8 InstallationandConfigurationGuide NAT Enable/Disable This parameter enables or disabled the Network Address Translation (NAT) feature for the SM. NAT isolates devices connected to the Ethernet/wired side of an SM from being seen directly from the wireless side of the SM. With NAT enabled, the SM has an IP address for transport traffic separate from its address for management, terminates transport traffic, and allows you to assign a range of IP addresses to devices that are connected to the Ethernet/wired side of the SM. For further information, see Network Address Translation (NAT) on Page 156 and NAT and IP Tabs of the SM with NAT Enabled on Page 271. NAT Private Network Interface Configuration, IP Address Assign an IP address for SM management through Ethernet access to the SM. Set only the first three bytes. The last byte is permanently set to 1. This address becomes the base for the range of DHCP-assigned addresses. NAT Private Network Interface Configuration, Subnet Mask Assign a subnet mask of 255.255.255.0 or a more restrictive subnet mask. Set only the last byte of this subnet mask. Each of the first three bytes is permanently set to 255. DMZ Host Interface Configuration, IP Address If you will be enabling DMZ in the next parameter, set the last byte of the DMZ host IP address to use for this SM when DMZ is enabled. Only one such address is allowed. The first three bytes are identical to those of the NAT private IP address. Ensure that the device that should receive network traffic behind this SM is assigned this address. The system provides a warning if you enter an address within the range that DHCP can assign. DMZ Enable Either enable or disable DMZ for this SM. See DMZ on Page 156. NAT Public Network Interface Configuration, IP Address This field displays the IP address of the SM. If DHCP Client is enabled, then the DHCP server automatically assigns this address. NAT Public Network Interface Configuration, Subnet Mask This field displays the subnet mask of the SM. If DHCP Client is enabled, then the DHCP server automatically assigns this subnet mask. NAT Public Network Interface Configuration, Gateway IP Address This field displays the gateway IP address for the SM. If DHCP Client is enabled, then the DHCP server automatically assigns this gateway IP address. DHCP Start IP If you will be enabling DHCP Server below, set the last byte of the starting IP address that the DHCP server will assign. The first three bytes are identical to those of the NAT private IP address. Number of IPs to Lease Enter how many IP addresses the DHCP server is allowed to assign. The default value is 50 addresses. Issue2,November2007 Draft5forRegulatoryReview 272 Release8 InstallationandConfigurationGuide Radio Public Network Interface Configuration, IP Address If DHCP Client is enabled, then the DHCP server automatically assigns this address. Otherwise, assign the IP address for over-the-air management of the SM when the radio public interface is enabled in the next parameter. Radio Public Network Interface Configuration, Interface Enable/Disable If you want over-the-air management capability for the SM, select Enabled. If you want to limit management of the SM to its Ethernet interface, select Disabled. Radio Public Network Interface Configuration, Subnet Mask If DHCP Client is enabled, then the DHCP server automatically assigns this subnet mask. Otherwise, assign the subnet mask for over-the-air management of the SM when the radio public interface is enabled. Radio Public Network Interface Configuration, Gateway IP Address If DHCP Client is enabled, then the DHCP server automatically assigns this gateway IP address. Otherwise, assign the gateway IP address for over-the-air management of the SM when the radio public network interface is enabled. RECOMMENDATION:

Note or print the IP settings from this page. Ensure that you can readily associate these IP settings both with the module and with the other data that you store about the module. Radio Public Network Interface Configuration, DHCP State If you select Enabled, the DHCP server automatically assigns the IP configuration

(IP address, subnet mask, and gateway IP address) and the values of those individual parameters (above) are not used. The setting of this DHCP state parameter is also viewable, but not settable, in the Network Interface tab of the Home page. ARP Cache Timeout If a router upstream has an ARP cache of longer duration (as some use 30 minutes), enter a value of longer duration than the router ARP cache. The default value of this field is 20 minutes. TCP Session Garbage Timeout Where a large network exists behind the SM, you can set this parameter to lower than the default value of 1440 minutes (24 hours). This action makes additional resources available for greater traffic than the default value accommodates. The default value of this parameter is 120 minutes. UDP Session Garbage Timeout You may adjust this parameter in the range of 1 to 1440 minutes, based on network performance. The default value of this parameter is 4 minutes. Issue2,November2007 Draft5forRegulatoryReview 273 Release8 DHCP Client Enable/Disable Select either InstallationandConfigurationGuide

Enabled to allow the network DHCP server to assign IP addresses, subnet masks, and gateway IP addresses to devices that are attached to the SM.

Disabled to

disable DHCP server assignment of this address.

enable the operator to assign this address. The implementation of NAT with DHCP client is illustrated in Figure 42 on Page 159. The implementation of NAT with DHCP client and DHCP server is illustrated in Figure 41 on Page 158. The implementation of NAT without DHCP is illustrated in Figure 44 on Page 161. DHCP Server Enable/Disable Select either

Enabled to

allow this SM to assign IP addresses, subnet masks, and gateway IP addresses to attached devices.

assign a start address for DHCP.

designate how many IP addresses may be temporarily used (leased).

Disabled to disallow the SM to assign addresses to attached devices. The implementation of NAT with DHCP server is illustrated in Figure 43 on Page 50. The implementation of NAT with DHCP client and DHCP server is illustrated in Figure 41 on Page 158. The implementation of NAT without DHCP is illustrated in Figure 44 on Page 161. DHCP Server Lease Timeout Based on network performance, enter the number of days between when the DHCP server assigns an IP address and when that address expires. The range of values for this parameter is 1 to 30 days. The default value is 30 days. DNS IP Address Select either

Obtain Automatically to allow the system to set the IP address of the DNS server.

Set Manually to enable yourself to set both a preferred and an alternate DNS IP address. Preferred DNS IP Address Enter the preferred DNS IP address to use when the DNS IP Address parameter is set to Set Manually. Alternate DNS IP Address Enter the DNS IP address to use when the DNS IP Address parameter is set to Set Manually and no response is received from the preferred DNS IP address. The NAT tab also contains the following buttons. Issue2,November2007 Draft5forRegulatoryReview 274 Release8 InstallationandConfigurationGuide Save Changes When you click this button, any changes that you made on all tabs are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. An example of the IP tab in an SM with NAT enabled is displayed in Figure 89. Figure 89: IP tab of SM with NAT enabled, example In the IP tab of an SM with NAT enabled, you may set the following parameters. NAT Network Interface Configuration, IP Address Assign an IP address for SM management through Ethernet access to the SM. Set only the first three bytes. The last byte is permanently set to 1. This address becomes the base for the range of DHCP-assigned addresses. NAT Network Interface Configuration, Subnet Mask Assign a subnet mask of 255.255.255.0 or a more restrictive subnet mask. Set only the last byte of this subnet mask. Each of the first three bytes is permanently set to 255. The IP tab also contains the following buttons. Save Changes When you click this button, any changes that you made on all tabs are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Issue2,November2007 Draft5forRegulatoryReview 275 Release8 Reboot When you click this button InstallationandConfigurationGuide the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. An example of the IP tab in an SM with NAT enabled is displayed in Figure 89. 18.2.4 RadioTaboftheSM An example of the Radio tab in the SM is displayed in Figure 90. Figure 90: Radio tab of SM, example In the Radio tab of the SM, you may set the following parameters. Custom Radio Frequency Scan Selection List Check any frequency that you want the SM to scan for AP transmissions. The frequency band of the SM affects what channels you should select. Issue2,November2007 Draft5forRegulatoryReview 276 Release8 InstallationandConfigurationGuide IMPORTANT!

In the 2.4-GHz frequency band, the SM can register to an AP that transmits on a frequency 2.5 MHz higher than the frequency that the SM receiver locks when the scan terminates as successful. This establishes a poor-quality link. To prevent this, select frequencies that are at least 5 MHz apart. In a 2.4-GHz SM, this parameter displays all available channels, but has only three recommended channels selected by default. See 2.4-GHz AP Cluster Recommended Channels on Page 137. In a 5.2- or 5.4-GHz SM, this parameter displays only ISM frequencies. In a 5.7-GHz SM, this parameter displays both ISM and U-NII frequencies. If you select all frequencies that are listed in this field (default selections), then the SM scans for a signal on any channel. If you select only one, then the SM limits the scan to that channel. Since the frequencies that this parameter offers for each of these two bands are 5 MHz apart, a scan of all channels does not risk establishment of a poor-quality link as in the 2.4-GHz band. A list of channels in the band is provided in Considering Frequency Band Alternatives on Page 136.

(The selection labeled Factory requires a special software key file for implementation.) Color Code Color code allows you to force the SM to register to only a specific AP, even where the SM can communicate with multiple APs. For registration to occur, the color code of the SM and the AP must match. Specify a value from 0 to 254. Color code is not a security feature. Instead, color code is a management feature, typically for assigning each sector a different color code. On all Cyclone modules, the default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). RECOMMENDATION:

Note the color code that you enter. Ensure that you can readily associate this color code both with the module and with the other data that you store about the module. External Filters Delay This parameter is present in only 900-MHz modules and can have effect in only those that have interference mitigation filter(s). If this value is present, leave it set to 0, regardless of whether the SM has an interference mitigation filter. Issue2,November2007 Draft5forRegulatoryReview 277 Release8 InstallationandConfigurationGuide Transmitter Output Power Nations and regions may regulate transmitter output power. For example Both 900-MHz and 5.7-GHz modules are available as connectorized radios, which require the operator to adjust power to ensure regulatory compliance. In addition to setting the power in the 5.7-GHz connectorized module, the operator must set the antenna gain/cable loss such that the module can accurately report received power at the antenna. Legal maximum allowable transmitter output power and EIRP (Equivalent Isotropic Radiated Power) in the 2.4-GHz frequency band varies by country and region. The output power of Series P9 2.4-GHz modules can be adjusted to meet these national or regional regulatory requirements. Countries and regions that permit the use of the 5.4-GHz frequency band (CEPT member states, for example), generally require equipment using the band to have adjustable power. The professional installer of Cyclone equipment has the responsibility to

maintain awareness of applicable regulations.

calculate the permissible transmitter output power for the module. confirm that the initial power setting is compliant with national or regional regulations. confirm that the power setting is compliant following any reset of the module to factory defaults.

For information on how to calculate the permissible transmitter output power to enter in this parameter, see Adjusting Transmitter Output Power on Page 330. The Radio tab also contains the following buttons. Save Changes When you click this button, any changes that you made on all tabs are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 278 Release8 18.2.5 SNMPTaboftheSM InstallationandConfigurationGuide An example of the SNMP tab in an SM is displayed in Figure 91. Figure 91: SNMP tab of SM, example In the SNMP tab of the SM, you may set the following parameters. Community String Specify a control string that allows Prizm or an NMS (Network Management Station) to access MIB information about this SM. No spaces are allowed in this string. The default string is Cyclone. Issue2,November2007 Draft5forRegulatoryReview 279 Release8 InstallationandConfigurationGuide The Community String value is clear text and is readable by a packet monitor. Additional security derives from the configuration of the Accessing Subnet, Trap Address, and Permission parameters. Accessing Subnet Specify the addresses that are allowed to send SNMP requests to this SM. Prizm or the NMS has an address that is among these addresses (this subnet). You must enter both

The network IP address in the form xxx.xxx.xxx.xxx

The CIDR (Classless Interdomain Routing) prefix length in the form /xx For example

the /16 in 198.32.0.0/16 specifies a subnet mask of 255.255.0.0 (the first 16 bits in the address range are identical among all members of the subnet). 192.168.102.0 specifies that any device whose IP address is in the range 192.168.102.0 to 192.168.102.254 can send SNMP requests to the SM, presuming that the device supplies the correct Community String value. The default treatment is to allow all networks access (set to 0). For more information on CIDR, execute an Internet search on Classless Interdomain Routing. RECOMMENDATION:

The subscriber can access the SM by changing the subscriber device to the accessing subnet. This hazard exists because the Community String and Accessing Subnet are both visible parameters. To avoid this hazard, configure the SM to filter (block) SNMP requests. See Filtering Protocols and Ports on Page 382. Trap Address 1 to 10 Specify ten or fewer IP addresses (xxx.xxx.xxx.xxx) to which trap information should be sent. Trap information informs Prizm or an NMS that something has occurred. For example, trap information is sent after a reboot of the module.

when Prizm or an NMS attempts to access agent information but either

supplied an inappropriate community string or SNMP version number.

is associated with a subnet to which access is disallowed. Read Permissions Select Read Only if you wish to disallow Prizm or NMS SNMP access to configurable parameters and read-only fields of the SM. Site Name Specify a string to associate with the physical module. This parameter is written into the sysName SNMP MIB-II object and can be polled by Prizm or an NMS. The buffer size for this field is 128 characters. Issue2,November2007 Draft5forRegulatoryReview 280 Release8 InstallationandConfigurationGuide Site Contact Enter contact information for the module administrator. This parameter is written into the sysContact SNMP MIB-II object and can be polled by Prizm or an NMS. The buffer size for this field is 128 characters. Site Location Enter information about the physical location of the module. This parameter is written into the sysLocation SNMP MIB-II object and can be polled by Prizm or an NMS. The buffer size for this field is 128 characters. The SNMP tab also provides the following buttons. Save Changes When you click this button, any changes that you made on the Configuration page are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 281 Release8 18.2.6 QualityofService(QoS)TaboftheSM InstallationandConfigurationGuide An example of the Quality of Service (QoS) tab in the SM is displayed in Figure 92. Figure 92: Quality of Service (QoS) tab of SM, example In the Quality of Service (QoS) tab of the SM, you may set the following parameters. Sustained Uplink Data Rate Specify the rate that this SM is replenished with credits for transmission. This default imposes no restriction on the uplink. See Maximum Information Rate (MIR) Parameters on Page 84 Setting the Configuration Source on Page 295. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 86 Sustained Downlink Data Rate Specify the rate at which the AP should be replenished with credits (tokens) for transmission to this SM. This default imposes no restriction on the uplink. See Maximum Information Rate (MIR) Parameters on Page 84 Setting the Configuration Source on Page 295. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 86 Issue2,November2007 Draft5forRegulatoryReview 282 Release8 InstallationandConfigurationGuide Uplink Burst Allocation Specify the maximum amount of data to allow this SM to transmit before being recharged at the Sustained Uplink Data Rate with credits to transmit more. See Maximum Information Rate (MIR) Parameters on Page 84 Setting the Configuration Source on Page 295. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 86 Downlink Burst Allocation Specify the maximum amount of data to allow the AP to transmit to this SM before the AP is replenished at the Sustained Downlink Data Rate with transmission credits. See Maximum Information Rate (MIR) Parameters on Page 84 Setting the Configuration Source on Page 295. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 86 Low Priority Uplink CIR See Committed Information Rate on Page 86 Setting the Configuration Source on Page 295. Low Priority Downlink CIR See Committed Information Rate on Page 86 Setting the Configuration Source on Page 295. Hi Priority Channel See High-priority Bandwidth on Page 86 Setting the Configuration Source on Page 295. Hi Priority Uplink CIR See High-priority Bandwidth on Page 86 Committed Information Rate on Page 86 Setting the Configuration Source on Page 295. Issue2,November2007 Draft5forRegulatoryReview 283 Release8 Hi Priority Downlink CIR See InstallationandConfigurationGuide High-priority Bandwidth on Page 86 Committed Information Rate on Page 86 Setting the Configuration Source on Page 295. The Quality of Service (QoS) tab also provides the following buttons. Save Changes When you click this button, any changes that you made in this tab are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 284 Release8 18.2.7 SecurityTaboftheSM InstallationandConfigurationGuide An example of the Security tab in an SM is displayed in Figure 93. Figure 93: Security tab of SM, example Issue2,November2007 Draft5forRegulatoryReview 285 Release8 InstallationandConfigurationGuide In the Security tab of the SM, you may set the following parameters. Authentication Key Only if the AP to which this SM will register requires authentication, specify the key that the SM should use when authenticating. For alpha characters in this hex key, use only upper case. Select Key The Use Default Key selection specifies the predetermined key for authentication in BAM or Prizm. See Authentication Manager Capability on Page 389. The Use Key above selection specifies the 32-digit hexadecimal key that is permanently stored on both the SM and the BAM or Prizm database. NOTE:

The SM and BAM or Prizm pad the key of any length by the addition of leading zeroes, and if the entered keys match, authentication attempts succeed. However, Cyclone recommends that you enter 32 characters to achieve the maximal security from this feature. Web, Telnet, FTP Session Timeout Enter the expiry in seconds for remote management sessions via HTTP, telnet, or ftp access to the SM. Ethernet Access Control If you want to prevent any device that is connected to the Ethernet port of the SM from accessing the management interface of the SM, select Ethernet Access Disabled. This selection disables access through this port to via http (the GUI), SNMP, telnet, ftp, and tftp. With this selection, management access is available through only the RF interface via either an IP address (if Network Accessibility is set to Public on the SM) or the Session Status or Remote Subscribers tab of the AP. NOTE:

This setting does not prevent a device connected to the Ethernet port from accessing the management interface of other SMs in the network. To prevent this, use the IP Access Filtering Enabled selection in the IP Access Control parameter of the SMs in the network. See IP Access Control below. If you want to allow management access through the Ethernet port, select Ethernet Access Enabled. This is the factory default setting for this parameter. Issue2,November2007 Draft5forRegulatoryReview 286 Release8 InstallationandConfigurationGuide IP Access Control You can permit access to the SM from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address, including access and management by Prizm. Allowed Source IP 1 to 3 If you selected IP Access Filtering Enabled for the IP Access Control parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the SM from any IP address. You may populate as many as all three. If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. The Security tab of the SM also provides the following buttons. Save Changes When you click this button, any changes that you made on this tab are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. 18.2.8 VLANTaboftheSM An example of the VLAN tab in an SM is displayed in Figure 94. Issue2,November2007 Draft5forRegulatoryReview 287 Release8 InstallationandConfigurationGuide Figure 94: VLAN tab of SM, example In the VLAN tab of an SM, you may set the following parameters. Dynamic Learning Specify whether the SM should (Enable) or should not (Disable) add the VIDs of upstream frames (that enter the SM through the wired Ethernet interface) to the VID table. The default value is Enable. Allow Frame Types Select the type of arriving frames that the SM should tag, using the VID that is stored in the Untagged Ingress VID parameter. The default value is All Frames. VLAN Aging Timeout Specify how long the SM should keep dynamically learned VIDs. The range of values is 5 to 1440 (minutes). The default value is 25 (minutes). NOTE:

VIDs that you enter for the Untagged Ingress VID and Management VID parameters do not time out. Issue2,November2007 Draft5forRegulatoryReview 288 Release8 InstallationandConfigurationGuide Untagged Ingress VID Enter the VID that the SM(s) should use to tag frames that arrive at the SM(s) untagged. The range of values is 1 to 4095. The default value is 1. Management VID Enter the VID that the SM should share with the AP. The range of values is 1 to 4095. The default value is 1. SM Management VID Pass-through Specify whether to allow the SM (Enable) or the AP (Disable) to control the VLAN settings of this SM. The default value is Enable. The VLAN tab also provides the following buttons. Save Changes When you click this button, any changes that you made on this tab are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. 18.2.9 VLANMembershipTaboftheSM An example of the VLAN Membership tab in an SM is displayed in Figure 95. Figure 95: VLAN Membership tab of SM, example Issue2,November2007 Draft5forRegulatoryReview 289 Release8 InstallationandConfigurationGuide In the VLAN Membership tab, you may set the following parameter. VLAN Membership Table Configuration For each VLAN in which you want the AP to be a member, enter the VLAN ID and then click the Add Member button. Similarly, for any VLAN in which you want the AP to no longer be a member, enter the VLAN ID and then click the Remove Member button. 18.2.10 DiffServeTaboftheSM An example of the DiffServe tab in an SM is displayed in Figure 96. Figure 96: DiffServe tab of SM, example Issue2,November2007 Draft5forRegulatoryReview 290 Release8 In the DiffServe tab of the SM, you may set the following parameters. InstallationandConfigurationGuide CodePoint 1 through CodePoint 47 CodePoint 49 through CodePoint 55 CodePoint 57 through CodePoint 63 The default priority value for each settable CodePoint is shown in Figure 113. Priorities of 0 through 3 map to the low-priority channel;

4 through 7 to the high-priority channel. The mappings are the same as 802.1p VLAN priorities. Consistent with RFC 2474

CodePoint 0 is predefined to a fixed priority value of 0

(low-priority channel).

CodePoint 48 is predefined to a fixed priority value of 6

(high-priority channel).

CodePoint 56 is predefined to a fixed priority value of 7

(high-priority channel). You cannot change any of these three fixed priority values. Among the settable parameters, the priority values (and therefore the handling of packets in the high- or low-priority channel) are set in the AP for all downlinks within the sector and in the SM for each uplink. See DSCP Field on Page 87. The DiffServe tab of the SM also provides the following buttons. Save Changes When you click this button, any changes that you made on this tab are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 291 Release8 18.2.11 ProtocolFilteringTaboftheSM InstallationandConfigurationGuide An example of the Protocol Filtering tab in an SM is displayed in Figure 97. Figure 97: Protocol Filtering tab of SM, example In the Protocol Filtering tab of the SM, you may set the following parameters. Packet Filter Types For any box selected, the Protocol and Port Filtering feature blocks the associated protocol type. Examples are provided in Protocol and Port Filtering with NAT Disabled on Page 383. Issue2,November2007 Draft5forRegulatoryReview 292 Release8 InstallationandConfigurationGuide To filter packets in any of the user-defined ports, you must do all of the following:

Check the box for User Defined Port n (See Below) in the Packet Filter Types section of this tab. In the User Defined Port Filtering Configuration section of this tab, both

provide a port number at Port #n.

check TCP, UDP, or both. User Defined Port Filtering Configuration You can specify ports for which to block subscriber access, regardless of whether NAT is enabled. For more information, see Filtering Protocols and Ports on Page 382. 18.2.12 NATPortMappingTaboftheSM An example of the NAT Port Mapping tab in an SM is displayed in Figure 98. Figure 98: NAT Port Mapping tab of SM, example Issue2,November2007 Draft5forRegulatoryReview 293 Release8 InstallationandConfigurationGuide In the NAT Port Mapping tab of the SM, you may set the following parameters. Port Map 1 to 10 18.2.13 UnitSettingsTaboftheSM An example of the Unit Settings tab in an SM is displayed in Figure 99. Figure 99: Unit Settings tab of SM, example The Unit Settings tab of the SM contains an option for how the SM should react when it detects a connected override plug. You may set this option as follows. Set to Factory Defaults Upon Default Plug Detection If Enabled is checked, then an override/default plug functions as a default plug. When the module is rebooted with the plug inserted, it can be accessed at the IP address 169.254.1.1 and no password, and all parameter values are reset to defaults. A subscriber, technician, or other person who gains physical access to the module and uses an override/default plug cannot see or learn the settings that were previously configured in it. When the module is later rebooted with no plug inserted, the module uses the new values for any parameters that were changed and the default values for any that were not. If Disabled is checked, then an override/default plug functions as an override plug. When the module is rebooted with the plug inserted, it can be accessed at the IP address 169.254.1.1 and no password, and all previously configured parameter values remain and are displayed. A subscriber, technician, or other person who gains physical access to the module and uses an override/default plug can see and learn the settings. When the module is later rebooted with no plug inserted, the module uses the new values for any parameters that were changed and the previous values for any that were not. Issue2,November2007 Draft5forRegulatoryReview 294 Release8 InstallationandConfigurationGuide See Overriding Forgotten IP Addresses or Passwords on AP, SM, or BH on Page 379. The Unit Settings tab also contains the following buttons. Save Changes When you click this button, any changes that you made on all tabs are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Undo Unit-Wide Saved Changes When you click this button, any changes that you made in any tab but did not commit by a reboot of the module are undone. Set to Factory Defaults When you click this button, all configurable parameters on all tabs are reset to the factory settings. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. 18.3 SETTINGTHECONFIGURATIONSOURCE The AP includes a Configuration Source parameter, which sets where SMs that register to the AP are controlled for MIR, VLAN, the high-priority channel, and CIR as follows. The Configuration Source parameter affects the source of

the Hi Priority Channel setting all CIR settings

Low Priority Uplink CIR

Low Priority Downlink CIR

Hi Priority Uplink CIR

Hi Priority Downlink CIR

all MIR settings:

Sustained Uplink Data Rate

Uplink Burst Allocation

Sustained Downlink Data Rate

Downlink Burst Allocation all SM VLAN settings:

Dynamic Learning

Allow Only Tagged Frames

VLAN Ageing Timeout

Untagged Ingress VID

Management VID

VLAN Membership Most operators whose plans are typical should consult Table 45. Issue2,November2007 Draft5forRegulatoryReview 295 Release8 InstallationandConfigurationGuide Table 45: Recommended combined settings for typical operations Most operators who use none BAM Release 2.0

(Consider upgrading to Prizm) BAM Release 2.1

(Consider upgrading to Prizm) Prizm Release 2.0 and 2.1

(being used for BAM functionality) should set this parameter Authentication Mode Configuration Source Authentication Mode Configuration Source Authentication Mode Configuration Source Authentication Mode Configuration Source in this web page Configuration>

Security Configuration>

General of this module AP AP Configuration AP to Authentication Disabled SM Authentication Required Configuration AP BAM+SM Configuration AP Authentication Required Configuration AP BAM Configuration AP Authentication Required Configuration AP BAM Operators whose plans are atypical should consider the results that are described in Table 46 and Table 47. For any SM whose Authentication Mode parameter is set to Authentication Required, the listed settings are derived as shown in Table 46. Table 46: Where feature values are obtained for an SM with authentication required Configuration Source Setting in the AP BAM SM BAM+SM MIR Values VLAN Values BAM SM BAM BAM SM Values are obtained from High Priority Channel State BAM SM CIR Values BAM SM BAM, then SM BAM, then SM BAM, then SM NOTES:

HPC represents the Hi Priority Channel (enable or disable). Where BAM, then SM is the indication, parameters for which BAM does not send values are obtained from the SM. This is the case where the BAM server is operating on a BAM release that did not support the feature. This is also the case where the feature enable/disable flag in BAM is set to disabled. The values are those previously set or, if none ever were, then the default values. Where BAM is the indication, values in the SM are disregarded. Where SM is the indication, values that BAM sends for the SM are disregarded. The high-priority channel is unavailable to Series P7 and P8 SMs that run Cyclone Release 8. For any SM whose Authentication Mode parameter is not set to Authentication Required, the listed settings are derived as shown in Table 47. Issue2,November2007 Draft5forRegulatoryReview 296 Release8 InstallationandConfigurationGuide Table 47: Where feature values are obtained for an SM with authentication disabled Configuration Source Setting in the AP MIR Values Values are obtained from VLAN Values High Priority Channel BAM SM BAM+SM AP SM SM AP SM SM State AP SM SM CIR Values AP SM SM BAM Release 2.0 sends only MIR values. BAM Release 2.1 and Prizm Release 2.0 and 2.1 send VLAN and high-priority channel values as well. For the case where the Configuration Source parameter in the AP is set to BAM, the SM stores a value for the Dynamic Learning VLAN parameter that differs from its factory default. When Prizm does not send VLAN values (because VLAN Enable is set to No in Prizm), the SM

uses this stored Disable value for Dynamic Learning. shows the following in the VLAN Configuration web page:

either Enable or Disable as the value of the Dynamic Learning parameter.

Allow Learning : No under Active Configuration. For the case where the Configuration Source parameter in the AP is set to BAM+SM, and Prizm does not send VLAN values, the SM

uses the configured value in the SM for Dynamic Learning. If the SM is set to factory defaults, then this value is Enable. shows under Active Configuration the result of the configured value in the SM. For example, if the SM is set to factory defaults, then the VLAN Configuration page shows Allow Learning : Yes. This selection (BAM+SM) is not recommended where Prizm manages the VLAN feature in SMs. 18.4 CONFIGURINGABHTIMINGMASTERFORTHEDESTINATION NOTE:

The PTP 400 and PTP 600 series bridges (previously known as 30/60 Mbps and 150/300 Mbps Backhauls) are described in their own dedicated user guides. See Products Not Covered by This User Guide on Page 34. If an ADMINISTRATOR-level password has been set in the BHM, you must log into the module before you can configure its parameters. See Managing Module Access by Passwords on Page 377. Issue2,November2007 Draft5forRegulatoryReview 297 Release8 18.4.1 GeneralTaboftheBHM InstallationandConfigurationGuide An example of the General tab in a BHM is displayed in Figure 100. Figure 100: General tab of BHM, example Issue2,November2007 Draft5forRegulatoryReview 298 Release8 InstallationandConfigurationGuide In the General tab of the BHM, you may set the following parameters. Timing Mode Select Timing Master. This BH will provide sync for the link. Whenever you toggle this parameter to Timing Master from Timing Slave, you should also do the following:

1. Make no other changes in this or any other interface page. 2. Save this change of timing mode. 3. Reboot the BH. RESULT:The set of interface web pages that is unique to a BHM is made available. Link Speeds Specify the type of link speed for the Ethernet connection. The default for this parameter is that all speeds are selected. The recommended setting is a single speed selection for all APs, BHs, and SMs in the operator network. Sync Input Specify the type of synchronization for this BH timing master to use.

Select Sync to Received Signal (Power Port) to set this BHM to receive sync from a connected CMMmicro.

Select Sync to Received Signal (Timing Port) to set this BHM to receive sync from a connected CMM2, an AP in the cluster, an SM, or a BH timing slave.

Select Generate Sync Signal where the BHM does not receive sync, and no AP or other BHM is active within the link range. Webpage Auto Update Enter the frequency (in seconds) for the web browser to automatically refresh the web-

based interface. The default setting is 0. The 0 setting causes the web-based interface to never be automatically refreshed. Bridge Entry Timeout Specify the appropriate bridge timeout for correct network operation with the existing network infrastructure. The Bridge Entry Timeout should be a longer period than the ARP

(Address Resolution Protocol) cache timeout of the router that feeds the network. CAUTION!

An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of communication with some end users. Bridging Functionality Select whether you want bridge table filtering active (Enable) or not (Disable) on this BHM. Selecting Disable allows you to use redundant BHs without causing network addressing problems. Through a spanning tree protocol, this reduces the convergence time from 25 minutes to mere seconds. However, you should disable bridge table filtering as only a deliberate part of your overall network design. Otherwise, disabling it allows unwanted traffic across the wireless interface. Issue2,November2007 Draft5forRegulatoryReview 299 Release8 InstallationandConfigurationGuide Update Application Address For capabilities in future software releases, you can enter the address of the server to access for software updates on this BHM. 2X Rate See 2X Operation on Page 90. Prioritize TCP ACK To reduce the likelihood of TCP acknowledgement packets being dropped, set this parameter to Enabled. This can improve throughput that the end user perceives during transient periods of congestion on the link that is carrying acknowledgements. See AP-

SM Links on Page 99. The General tab of the BHM also provides the following buttons. Save Changes When you click this button, any changes that you made on the Configuration page are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 300

 

 

Release8 18.4.2 IPTaboftheBHM An example of an IP tab in a BHM is displayed in Figure 101. InstallationandConfigurationGuide Figure 101: IP tab of BHM, example You may set the following IP Configuration page parameters. LAN1 Network Interface Configuration, IP Address Enter the non-routable IP address to be associated with the Ethernet connection on this module. (The default IP address from the factory is 169.254.1.1.) If you set and then forget this parameter, then you must both 1. physically access the module. 2. use an override plug to electronically access the module configuration parameters at 169.254.1.1. See Overriding Forgotten IP Addresses or Passwords on AP, SM, or BH on Page 381. RECOMMENDATION:

Note or print the IP settings from this page. Ensure that you can readily associate these IP settings both with the module and with the other data that you store about the module. Issue2,November2007 Draft5forRegulatoryReview 301 Release8 InstallationandConfigurationGuide LAN1 Network Interface Configuration, Subnet Mask Enter an appropriate subnet mask for the BHM to communicate on the network. The default subnet mask is 255.255.0.0. See Allocating Subnets on Page 162. LAN1 Network Interface Configuration, Gateway IP Address Enter the appropriate gateway for the BHM to communicate with the network. The default gateway is 169.254.0.0. LAN1 Network Interface Configuration, DHCP State If you select Enabled, the DHCP server automatically assigns the IP configuration

(IP address, subnet mask, and gateway IP address) and the values of those individual parameters (above) are not used. The setting of this DHCP state parameter is also viewable, but not settable, in the Network Interface tab of the Home page. LAN2 Network Interface Configuration (RF Private Interface), IP Address Enter the IP address to be associated with this BHM for over-the-air access. The IP tab also provides the following buttons. Save Changes When you click this button, any changes that you made on the IP Configuration page are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 302 Release8 18.4.3 RadioTaboftheBHM InstallationandConfigurationGuide An example of the Radio tab in a BHM is displayed in Figure 102. Figure 102: Radio tab of BHM, example In the Radio tab of the BHM, you may set the following parameters. Radio Frequency Carrier Specify the frequency for the BHM to transmit. The default for this parameter is None.

(The selection labeled Factory requires a special software key file for implementation.) In a 5.7-GHz BHM, this parameter displays both ISM and U-NII frequencies. In a 5.2-GHz BHM, this parameter displays only ISM frequencies. For a list of channels in the band, see Considering Frequency Band Alternatives on Page 136. Color Code Specify a value from 0 to 254. For registration to occur, the color code of the BHM and the BHS must match. On all Cyclone modules, the default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). Issue2,November2007 Draft5forRegulatoryReview 303 Release8 InstallationandConfigurationGuide RECOMMENDATION:

Note the color code that you enter. Ensure that you can readily associate this color code both with the module and with the other data that you store about the module. Sector ID You can optionally enter an identifier to distinguish this link. Downlink Data The operator specifies the percentage of the aggregate (uplink and downlink total) throughput that is needed for the downlink. The default for this parameter is 50%. Transmit Frame Spreading If you select Enable, then a BHS between two BHMs can register in the assigned BHM

(not the other BHM). Cyclone strongly recommends that you select this option. With this selection, the BHM does not transmit a beacon in each frame, but rather transmits a beacon in only pseudo-random frames in which the BHS expects the beacon. This allows multiple BHMs to send beacons to multiple BHSs in the same range without interference. Transmitter Output Power Nations and regions may regulate transmitter output power. For example Both 900-MHz and 5.7-GHz modules are available as connectorized radios, which require the operator to adjust power to ensure regulatory compliance. In addition to setting the power in the 5.7-GHz connectorized module, the operator must set the antenna gain/cable loss such that the module can accurately report received power at the antenna. Legal maximum allowable transmitter output power and EIRP (Equivalent Isotropic Radiated Power) in the 2.4-GHz frequency band varies by country and region. The output power of Series P9 2.4-GHz modules can be adjusted to meet these national or regional regulatory requirements. Countries and regions that permit the use of the 5.4-GHz frequency band (CEPT member states, for example), generally require equipment using the band to have adjustable power. The professional installer of Cyclone equipment has the responsibility to

maintain awareness of applicable regulations.

calculate the permissible transmitter output power for the module. confirm that the initial power setting is compliant with national or regional regulations. confirm that the power setting is compliant following any reset of the module to factory defaults.

For information on how to calculate the permissible transmitter output power to enter in this parameter, see Adjusting Transmitter Output Power on Page 330. The Radio tab also provides the following buttons. Issue2,November2007 Draft5forRegulatoryReview 304 Release8 InstallationandConfigurationGuide Save Changes When you click this button, any changes that you made on the IP Configuration page are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 305 Release8 18.4.4 SNMPTaboftheBHM InstallationandConfigurationGuide An example of the SNMP tab in a BHM is displayed in Figure 103. Figure 103: SNMP tab of BHM, example In the SNMP tab of the BHM, you may set the following parameters. Issue2,November2007 Draft5forRegulatoryReview 306 Release8 InstallationandConfigurationGuide Community String Specify a control string that allows Prizm or a Network Management Station (NMS) to access the module through SNMP. No spaces are allowed in this string. The default string is Cyclone. The Community String value is clear text and is readable by a packet monitor. Additional security derives from the configuration of the Accessing Subnet, Trap Address, and Permission parameters. Accessing Subnet Specify the addresses that are allowed to send SNMP requests to this BHM. Prizm or the NMS has an address that is among these addresses (this subnet). You must enter both

The network IP address in the form xxx.xxx.xxx.xxx

The CIDR (Classless Interdomain Routing) prefix length in the form /xx For example the /16 in 198.32.0.0/16 specifies a subnet mask of 255.255.0.0 (the first 16 bits in the address range are identical among all members of the subnet). 192.168.102.0 specifies that any device whose IP address is in the range 192.168.102.0 to 192.168.102.254 can send SNMP requests to the BHM, presuming that the device supplies the correct Community String value. NOTE:

For more information on CIDR, execute an Internet search on Classless Interdomain Routing.

The default treatment is to allow all networks access. Trap Address 1 to 10 Specify ten or fewer IP addresses (xxx.xxx.xxx.xxx) to which trap information should be sent. Trap information informs Prizm or an NMS that something has occurred. For example, trap information is sent after a reboot of the module.

when Prizm or an NMS attempts to access agent information but either

supplied an inappropriate community string or SNMP version number.

is associated with a subnet to which access is disallowed. Trap Enable Select either Sync Status or Session Status to enable SNMP traps. If you select neither, then traps are disabled. Read Permissions Select Read Only if you wish to disallow any parameter changes by Prizm or an NMS. Issue2,November2007 Draft5forRegulatoryReview 307 Release8 InstallationandConfigurationGuide Site Name Specify a string to associate with the physical module. This parameter is written into the sysName SNMP MIB-II object and can be polled by an NMS. The buffer size for this field is 128 characters. Site Contact Enter contact information for the module administrator. This parameter is written into the sysContact SNMP MIB-II object and can be polled by an NMS. The buffer size for this field is 128 characters. Site Location Enter information about the physical location of the module. This parameter is written into the sysLocation SNMP MIB-II object and can be polled by an NMS. The buffer size for this field is 128 characters. The SNMP tab also provides the following buttons. Save Changes When you click this button, any changes that you made on the Configuration page are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 308 Release8 18.4.5 SecurityTaboftheBHM InstallationandConfigurationGuide An example of the Security tab in a BHM is displayed in Figure 104. Figure 104: Security tab of BHM, example In the Security tab of the BHM, you may set the following parameters. Authentication Mode Specify whether the BHM should require the BHS to authenticate. Authentication Key Only if you set the BHM in the previous parameter to require authentication, specify the key that the BHS should use when authenticating. Issue2,November2007 Draft5forRegulatoryReview 309 Release8 Encryption Specify the type of air link security to apply to this BHM:

InstallationandConfigurationGuide

Encryption Disabled provides no encryption on the air link. This is the default mode.

Encryption Enabled provides encryption, using a factory-programmed secret key that is unique for each module. NOTE:

In any BH link where encryption is enabled, the BHS briefly drops registration and re-registers in the BHM every 24 hours to change the encryption key. BHS Display of BHM Evaluation Data You can use this field to suppress the display of data (Disable Display) about this BHM on the BHM Evaluation tab of the Tools page in the BHS. Web, Telnet, FTP Session Timeout Enter the expiry in seconds for remote management sessions via HTTP, telnet, or ftp access to the BHM. IP Access Control You can permit access to the BHM from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address, including access and management by Prizm. Allowed Source IP 1 to 3 If you selected IP Access Filtering Enabled for the IP Access Control parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the BHM from any IP address. You may populate as many as all three. If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. The Security tab also provides the following buttons. Save Changes When you click this button, any changes that you made on the Configuration page are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Issue2,November2007 Draft5forRegulatoryReview 310 Release8 Reboot When you click this button InstallationandConfigurationGuide the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. 18.4.6 DiffServeTaboftheBHM An example of the DiffServe tab in a BHM is displayed in Figure 105. Figure 105: DiffServe tab of BHM, example Issue2,November2007 Draft5forRegulatoryReview 311 Release8 InstallationandConfigurationGuide In the DiffServe tab of the BHM, you may set the following parameters. CodePoint 1 through CodePoint 47 CodePoint 49 through CodePoint 55 CodePoint 57 through CodePoint 63 The default priority value for each settable CodePoint is shown in Figure 113. Priorities of 0 through 3 map to the low-priority channel;

4 through 7 to the high-priority channel. The mappings are the same as 802.1p VLAN priorities. Consistent with RFC 2474

CodePoint 0 is predefined to a fixed priority value of 0

(low-priority channel).

CodePoint 48 is predefined to a fixed priority value of 6

(high-priority channel).

CodePoint 56 is predefined to a fixed priority value of 7

(high-priority channel). You cannot change any of these three fixed priority values. Among the settable parameters, the priority values (and therefore the handling of packets in the high- or low-priority channel) are set in the AP for all downlinks within the sector and in the SM for each uplink. See DSCP Field on Page 87. The DiffServe tab also provides the following buttons. Save Changes When you click this button, any changes that you made on the Configuration page are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 312 Release8 18.4.7 UnitSettingsTaboftheBHM InstallationandConfigurationGuide An example of the Unit Settings tab of the BHM is displayed in Figure 106. Figure 106: Unit Settings tab of BHM, example The Unit Settings tab of the BHM contains an option for how the BHM should react when it detects a connected override plug. You may set this option as follows. Set to Factory Defaults Upon Default Plug Detection If Enabled is checked, then an override/default plug functions as a default plug. When the module is rebooted with the plug inserted, it can be accessed at the IP address 169.254.1.1 and no password, and all parameter values are reset to defaults. A subscriber, technician, or other person who gains physical access to the module and uses an override/default plug cannot see or learn the settings that were previously configured in it. When the module is later rebooted with no plug inserted, the module uses the new values for any parameters that were changed and the default values for any that were not. If Disabled is checked, then an override/default plug functions as an override plug. When the module is rebooted with the plug inserted, it can be accessed at the IP address 169.254.1.1 and no password, and all previously configured parameter values remain and are displayed. A subscriber, technician, or other person who gains physical access to the module and uses an override/default plug can see and learn the settings. When the module is later rebooted with no plug inserted, the module uses the new values for any parameters that were changed and the previous values for any that were not. See Overriding Forgotten IP Addresses or Passwords on AP, SM, or BH on Page 379. The Unit Settings tab also contains the following buttons. Issue2,November2007 Draft5forRegulatoryReview 313 Release8 InstallationandConfigurationGuide Save Changes When you click this button, any changes that you made on the Configuration page are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 314 Release8 18.5 CONFIGURINGABHTIMINGSLAVEFORTHEDESTINATION InstallationandConfigurationGuide If an ADMINISTRATOR-level password has been set in the BHS, you must log into the module before you can configure its parameters. See Managing Module Access by Passwords on Page 377. 18.5.1 GeneralTaboftheBHS An example of the General tab in a BHS is displayed in Figure 107. Figure 107: General tab of BHS, example In the General tab of the BHS, you may set the following parameters. Issue2,November2007 Draft5forRegulatoryReview 315 Release8 InstallationandConfigurationGuide Timing Mode Select Timing Slave. This BH will receive sync from another source. Whenever you toggle this parameter to Timing Slave from Timing Master, you should also do the following:

1. Make no other changes in this or any other interface page. 2. Save this change of timing mode. 3. Reboot the BH. RESULT:The set of interface web pages that is unique to a BHS is made available. NOTE:

In a BHS that cannot be converted to a BHM, this parameter is not present (for example, in a BHS with Hardware Scheduling and Series P8 hardware.) Link Speeds Specify the type of link speed for the Ethernet connection. The default for this parameter is that all speeds are selected. The recommended setting is a single speed selection for all APs, BHs, and SMs in the operator network. Webpage Auto Update Enter the frequency (in seconds) for the web browser to automatically refresh the web-

based interface. The default setting is 0. The 0 setting causes the web-based interface to never be automatically refreshed. Bridge Entry Timeout Specify the appropriate bridge timeout for correct network operation with the existing network infrastructure. Timeout occurs when the BHM encounters no activity with the BHS (whose MAC address is the bridge entry) within the interval that this parameter specifies. The Bridge Entry Timeout should be a longer period than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. This parameter governs the timeout interval, even if a router in the system has a longer timeout interval. The default value of this field is 25 minutes. CAUTION!

An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of communication with some end users. Bridging Functionality Select whether you want bridge table filtering active (Enable) or not (Disable) on this BHS. Selecting Disable allows you to use redundant BHs without causing network addressing problems. Through a spanning tree protocol, this reduces the convergence time from 25 minutes to mere seconds. However, you should disable bridge table filtering as only a deliberate part of your overall network design. Otherwise, disabling it allows unwanted traffic across the wireless interface. Issue2,November2007 Draft5forRegulatoryReview 316 Release8 InstallationandConfigurationGuide SM Power Up Mode With No 802.3 Link Specify the default mode in which this BHS will power up when it senses no Ethernet link. Select either

Power Up in Aim Modethe BHS boots in an aiming mode. When the BHS senses an Ethernet link, this parameter is automatically reset to Power Up in Operational Mode. When the BHS senses no Ethernet link within 15 minutes after power up, the BHS carrier shuts off.

Power Up in Operational Modethe BHS boots in Operational mode and attempts registration. Unlike in previous releases, this is the default selection in Release 8. 2X Rate See 2X Operation on Page 90. Frame Timing Pulse Gated If this BHS extends the sync pulse to a BHM or an AP behind it, select either

EnableIf this BHS loses sync, then do not propagate a sync pulse to the BHM or AP. This setting prevents interference in the event that the BHS loses sync.

DisableIf this BHS loses sync, then propagate the sync pulse anyway to the BHM or AP. See Wiring to Extend Network Sync on Page 374. The General tab also provides the following buttons. Save Changes When you click this button, any changes that you made on the Configuration page are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 317 Release8 18.5.2 IPTaboftheBHS An example of the IP tab in a BHS is displayed in Figure 108. InstallationandConfigurationGuide Figure 108: IP tab of BHS, example In the IP tab of the BHS, you may set the following parameters. LAN1 Network Interface Configuration, IP Address Enter the non-routable IP address to associate with the Ethernet connection on this BHS.

(The default IP address from the factory is 169.254.1.1.) If you set and then forget this parameter, then you must both 1. physically access the module. 2. use an override plug to electronically access the module configuration parameters at 169.254.1.1. See Overriding Forgotten IP Addresses or Passwords on AP, SM, or BH on Page 381. RECOMMENDATION:

Note or print the IP settings from this page. Ensure that you can readily associate these IP settings both with the module and with the other data that you store about the module. Issue2,November2007 Draft5forRegulatoryReview 318 Release8 InstallationandConfigurationGuide LAN1 Network Interface Configuration, Subnet Mask Enter an appropriate subnet mask for the BHS to communicate on the network. The default subnet mask is 255.255.0.0. See Allocating Subnets on Page 162. LAN1 Network Interface Configuration, Gateway IP Address Enter the appropriate gateway for the BHS to communicate with the network. The default gateway is 169.254.0.0. LAN1 Network Interface Configuration, DHCP State If you select Enabled, the DHCP server automatically assigns the IP configuration

(IP address, subnet mask, and gateway IP address) and the values of those individual parameters (above) are not used. The setting of this DHCP state parameter is also viewable, but not settable, in the Network Interface tab of the Home page. The IP tab also provides the following buttons. Save Changes When you click this button, any changes that you made on the IP Configuration page are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 319 Release8 18.5.3 RadioTaboftheBHS InstallationandConfigurationGuide An example of the Radio tab in a BHS is displayed in Figure 109. Figure 109: Radio tab of BHS, example In the Radio tab of the BHS, you may set the following parameters. Custom Radio Frequency Scan Selection List Specify the frequency that the BHS should scan to find the BHM. The frequency band of the BHs affects what channels you select. IMPORTANT!

In the 2.4-GHz frequency band, the BHS can register to a BHM that transmits on a frequency 2.5 MHz higher than the frequency that the BHS receiver locks when the scan terminates as successful. This establishes a poor-quality link. To prevent this, select frequencies that are at least 5 MHz apart. In a 2.4-GHz BHS, this parameter displays all available channels, but has only three recommended channels selected by default. See 2.4-GHz AP Cluster Recommended Channels on Page 137. In a 5.2- or 5.4-GHz BHS, this parameter displays only ISM frequencies. In a 5.7-GHz BHS, this parameter displays both ISM and U-NII frequencies. If you select all frequencies that are listed (default selections), then the module scans for a signal on any Issue2,November2007 Draft5forRegulatoryReview 320 Release8 InstallationandConfigurationGuide channel. If you select only one, then the module limits the scan to that channel. Since the frequencies that this parameter offers for each of these two bands are 5 MHz apart, a scan of all channels does not risk establishment of a poor-quality link as in the 2.4-GHz band. Nevertheless, this can risk establishment of a link to the wrong BHM. A list of channels in the band is provided in Considering Frequency Band Alternatives on Page 136.

(The selection labeled Factory requires a special software key file for implementation.) Color Code Specify a value from 0 to 254. For registration to occur, the color code of the BHM and the BHS must match. On all Cyclone modules, the default setting for the color code value is 0. This value matches only the color code of 0 (not all 255 color codes). RECOMMENDATION:

Note the color code that you enter. Ensure that you can readily associate this color code both with the module and with the other data that you store about the module. Transmitter Output Power Nations and regions may regulate transmitter output power. For example Both 900-MHz and 5.7-GHz modules are available as connectorized radios, which require the operator to adjust power to ensure regulatory compliance. In addition to setting the power in the 5.7-GHz connectorized module, the operator must set the antenna gain/cable loss such that the module can accurately report received power at the antenna. Legal maximum allowable transmitter output power and EIRP (Equivalent Isotropic Radiated Power) in the 2.4-GHz frequency band varies by country and region. The output power of Series P9 2.4-GHz modules can be adjusted to meet these national or regional regulatory requirements. Countries and regions that permit the use of the 5.4-GHz frequency band (CEPT member states, for example), generally require equipment using the band to have adjustable power. The professional installer of Cyclone equipment has the responsibility to

maintain awareness of applicable regulations.

calculate the permissible transmitter output power for the module. confirm that the initial power setting is compliant with national or regional regulations. confirm that the power setting is compliant following any reset of the module to factory defaults.

For information on how to calculate the permissible transmitter output power to enter in this parameter, see Adjusting Transmitter Output Power on Page 330. Issue2,November2007 Draft5forRegulatoryReview 321 Release8 InstallationandConfigurationGuide The Radio tab also provides the following buttons. Save Changes When you click this button, any changes that you made on this tab are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 322 Release8 18.5.4 SNMPTaboftheBHS InstallationandConfigurationGuide An example of the SNMP tab in a BHS is displayed in Figure 110. Figure 110: SNMP tab of BHS, example In the SNMP tab of the BHS, you may set the following parameters. Community String Specify a control string that allows Prizm or an NMS (Network Management Station) to access MIB information about this BHS. No spaces are allowed in this string. The default string is Cyclone. Issue2,November2007 Draft5forRegulatoryReview 323 Release8 InstallationandConfigurationGuide The Community String value is clear text and is readable by a packet monitor. Additional security derives from the configuration of the Accessing Subnet, Trap Address, and Permission parameters. Accessing Subnet Specify the addresses that are allowed to send SNMP requests to this BHS. Prizm or the NMS has an address that is among these addresses (this subnet). You must enter both

The network IP address in the form xxx.xxx.xxx.xxx

The CIDR (Classless Interdomain Routing) prefix length in the form /xx For example

the /16 in 198.32.0.0/16 specifies a subnet mask of 255.255.0.0 (the first 16 bits in the address range are identical among all members of the subnet). 192.168.102.0 specifies that any device whose IP address is in the range 192.168.102.0 to 192.168.102.254 can send SNMP requests to the BHS, presuming that the device supplies the correct Community String value. The default treatment is to allow all networks access (set to 0). For more information on CIDR, execute an Internet search on Classless Interdomain Routing. Trap Address 1 to 10 Specify ten or fewer IP addresses (xxx.xxx.xxx.xxx) to which trap information should be sent. Trap information informs Prizm or an NMS that something has occurred. For example, trap information is sent after a reboot of the module.

when Prizm or an NMS attempts to access agent information but either

supplied an inappropriate community string or SNMP version number.

is associated with a subnet to which access is disallowed. Read Permissions Select Read Only if you wish to disallow Prizm or NMS SNMP access to configurable parameters and read-only fields of the SM. Site Name Specify a string to associate with the physical module. This parameter is written into the sysName SNMP MIB-II object and can be polled by Prizm or an NMS. The buffer size for this field is 128 characters. Site Contact Enter contact information for the module administrator. This parameter is written into the sysContact SNMP MIB-II object and can be polled by Prizm or an NMS. The buffer size for this field is 128 characters. Site Location Enter information about the physical location of the module. This parameter is written into the sysLocation SNMP MIB-II object and can be polled by Prizm or an NMS. The buffer size for this field is 128 characters. Issue2,November2007 Draft5forRegulatoryReview 324 Release8 InstallationandConfigurationGuide The SNMP tab also provides the following buttons. Save Changes When you click this button, any changes that you made on the Configuration page are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. 18.5.5 QualityofService(QoS)TaboftheBHS An example of the Quality of Service tab of the BHS is displayed in Figure 111. Figure 111: Quality of Service (QoS) tab of BHS, example In the Quality of Service (QoS) tab of the BHS, you may set the following parameters. Low Priority Uplink CIR See Committed Information Rate on Page 86 Setting the Configuration Source on Page 295. Issue2,November2007 Draft5forRegulatoryReview 325 Release8 Low Priority Downlink CIR See InstallationandConfigurationGuide Committed Information Rate on Page 86 Setting the Configuration Source on Page 295. 18.5.6 SecurityTaboftheBHS An example of the Security tab in a BHS is displayed in Figure 112. Figure 112: Security tab of BHS, example In the Security tab of the BHS, you may set the following parameters. Authentication Key Only if the BHM to which this BHS will register requires authentication, specify the key that the BHS should use when authenticating. For alpha characters in this hex key, use only upper case. NOTE:

Cyclone recommends that you enter 32 characters to achieve the maximal security from this feature. Issue2,November2007 Draft5forRegulatoryReview 326 Release8 InstallationandConfigurationGuide Select Key The Use Default Key selection specifies that the link should continue to use the automatically generated authentication key. See Authentication Manager Capability on Page 389. The Use Key above selection specifies the 32-digit hexadecimal key that is permanently stored on both the BHS and the BHM. Web, Telnet, FTP Session Timeout Enter the expiry in seconds for remote management sessions via HTTP, telnet, or ftp access to the BHS. IP Access Control You can permit access to the BHS from any IP address (IP Access Filtering Disabled) or limit it to access from only one, two, or three IP addresses that you specify (IP Access Filtering Enabled). If you select IP Access Filtering Enabled, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted from any IP address, including access and management by Prizm. Allowed Source IP 1 to 3 If you selected IP Access Filtering Enabled for the IP Access Control parameter, then you must populate at least one of the three Allowed Source IP parameters or have no access permitted to the BHS from any IP address. You may populate as many as all three. If you selected IP Access Filtering Disabled for the IP Access Control parameter, then no entries in this parameter are read, and access from all IP addresses is permitted. The Security tab of the BHS also provides the following buttons. Save Changes When you click this button, any changes that you made on this tab are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Issue2,November2007 Draft5forRegulatoryReview 327 Release8 18.5.7 DiffServeTaboftheBHS InstallationandConfigurationGuide An example of the DiffServe tab in a BHS is displayed in Figure 113. Figure 113: DiffServe tab of BHS, example Issue2,November2007 Draft5forRegulatoryReview 328 Release8 InstallationandConfigurationGuide You may set the following Differentiated Services Configuration page parameters. CodePoint 1 through CodePoint 47 CodePoint 49 through CodePoint 55 CodePoint 57 through CodePoint 63 The default priority value for each settable CodePoint is shown in Figure 113. Priorities of 0 through 3 map to the low-priority channel;

4 through 7 to the high-priority channel. The mappings are the same as 802.1p VLAN priorities. Consistent with RFC 2474

CodePoint 0 is predefined to a fixed priority value of 0

(low-priority channel).

CodePoint 48 is predefined to a fixed priority value of 6

(high-priority channel).

CodePoint 56 is predefined to a fixed priority value of 7

(high-priority channel). You cannot change any of these three fixed priority values. Among the settable parameters, the priority values (and therefore the handling of packets in the high- or low-priority channel) are set in the BHM for the downlink and in the BHS for the uplink. See DSCP Field on Page 87. 18.5.8 UnitSettingsTaboftheBHS An example of the Unit Settings tab in a BHS is displayed in Figure 114. Figure 114: Unit Settings tab of BHS, example The Unit Settings tab of the BHS contains an option for how the BHS should react when it detects a connected override plug. You may set this option as follows. Issue2,November2007 Draft5forRegulatoryReview 329 Release8 InstallationandConfigurationGuide Set to Factory Defaults Upon Default Plug Detection If Enabled is checked, then an override/default plug functions as a default plug. When the module is rebooted with the plug inserted, it can be accessed at the IP address 169.254.1.1 and no password, and all parameter values are reset to defaults. A subscriber, technician, or other person who gains physical access to the module and uses an override/default plug cannot see or learn the settings that were previously configured in it. When the module is later rebooted with no plug inserted, the module uses the new values for any parameters that were changed and the default values for any that were not. If Disabled is checked, then an override/default plug functions as an override plug. When the module is rebooted with the plug inserted, it can be accessed at the IP address 169.254.1.1 and no password, and all previously configured parameter values remain and are displayed. A subscriber, technician, or other person who gains physical access to the module and uses an override/default plug can see and learn the settings. When the module is later rebooted with no plug inserted, the module uses the new values for any parameters that were changed and the previous values for any that were not. See Overriding Forgotten IP Addresses or Passwords on AP, SM, or BH on Page 379. The Unit Settings tab also contains the following buttons. Save Changes When you click this button, any changes that you made on all tabs are recorded in flash memory. However, these changes do not apply until the next reboot of the module. Reboot When you click this button the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. Undo Unit-Wide Saved Changes When you click this button, any changes that you made in any tab but did not commit by a reboot of the module are undone. Set to Factory Defaults When you click this button, all configurable parameters on all tabs are reset to the factory settings. 18.6 ADJUSTINGTRANSMITTEROUTPUTPOWER Authorities may require transmitter output power to be adjustable and/or lower than the highest that a module produces. Cyclone adjustable power modules include a Radio tab parameter to reduce power on an infinite scale to achieve compliance. If you set this parameter to lower than the supported range extends, the value is automatically reset to the lowest supported value. The professional installer of Cyclone equipment has the responsibility to

maintain awareness of applicable regulations.

calculate the permissible transmitter output power for the module. Issue2,November2007 Draft5forRegulatoryReview 330 Release8 InstallationandConfigurationGuide

confirm that the initial power setting is compliant. confirm that the power setting is compliant following any reset of the module to factory defaults. The total gain per antenna in 5.2 GHz and 5.4 GHz Cyclone radios is stated in Table 48. Table 48: Total gain per antenna Model Cyclone5.2GHzAccessPoints&Backhauls Antenna Antenna Gain Cable Loss Cyclone52XX60 Cyclone52XX90 Cyclone52XX120 Cyclone52XX180 Cyclone52XX60H Cyclone52XX90H Cyclone52XX120H Cyclone52XX360 Cyclone52XXBH TA5204LM860 TA5204LM890 TA5204LM8120 TA5204LM8180 TA5204LMH860 TA5204LMH890 TA5204LMH8120 R380600204 MT485002 16.5dBi 15.5dBi 14.5dBi 13.5dBi 16.0dBi 15.0dBi 13.0dBi 10.0dBi 23dBi 0.5dB 0.5dB 0.5dB 0.5dB 0.5dB 0.5dB 0.5dB 0.5dB 0.5dB Model Cyclone5.4GHzAccessPoints&Backhauls Antenna Antenna Gain Cable Loss Cyclone54XX60 Cyclone54XX90 Cyclone54XX120 Cyclone54XX180 Cyclone54XX60H Cyclone54XX90H Cyclone54XX120H Cyclone54XX360 Cyclone54XXBH TA5204LM860 TA5204LM890 TA5204LM8120 TA5204LM8180 TA5204LMH860 TA5204LMH890 TA5204LMH8120 RO5410NM MT485002 16.5dBi 15.5dBi 14.5dBi 13.5dBi 16.0dBi 15.0dBi 13.0dBi 10.0dBi 23dBi 0.5dB 0.5dB 0.5dB 0.5dB 0.5dB 0.5dB 0.5dB 0.5dB 0.5dB Net Gain 16.0dBi 15.0dBi 14.0dBi 13.0dBi 15.5dBi 14.5dBi 12.5dBi 9.5dBi 22.5dBi Net Gain 16.0dBi 15.0dBi 14.0dBi 13.0dBi 15.5dBi 14.5dBi 12.5dBi 9.5dBi 22.5dBi Issue2,November2007 Draft5forRegulatoryReview 331 Release8 InstallationandConfigurationGuide The calculation of transmitter output power is as follows:

from applicable regulations from the preceding table Transmitter Output Power

=

EIRP Patch Antenna Gain Reflector Gain solve, then set in parameter from the preceding table Transmitter output power is settable as dBm on the Radio tab of the module. Example cases of transmitter output power settings are shown in Table 49. Table 49: Transmitter output power settings, example cases Frequency Band Range and Antenna Scheme Region Maximum EIRP in Region 900 MHz Integrated 900 MHz Connectorized U.S.A. Canada U.S.A. Canada 36 dBm (4 W) 36 dBm (4 W) Australia 30 dBm (1 W) 2.4 GHz Integrated 5.2 GHz Integrated 5.4 GHz Integrated U.S.A. Canada CEPT states U.S.A. Canada CEPT states Depends on antenna gain 20 dBm (100 mW) 12 dBm 30 dBm (1 W) 30 dBm (1 W) 23 dBm 23 dBm Transmitter Output Power Setting AP, SM, or BH with No Reflector 24 dBm 26 dBm1 Depends on antenna 25 dBm SM or BH with Reflector 25 dBm 1 dBm 5 dBm 5.7 GHz Connectorized UK 33 dBm (2 W) Depends on antenna Depends on antenna NOTES:

1. With Mars, MTI, or Maxrad antenna. This is the default setting, and 28 dBm is the highest settable value. The lower default correlates to 36 dBm EIRP where 10-dBi antennas are used. The default setting for this parameter is applied whenever Set to Factory Defaults is selected. Issue2,November2007 Draft5forRegulatoryReview 332 Release8 19 INSTALLINGCOMPONENTS InstallationandConfigurationGuide RECOMMENDATION:

Use shielded cable for all Cyclone infrastructure connections associated with BHs, APs, and CMMs. The environment that these modules operate in often has significant unknown or varying RF energy. Operator experience consistently indicates that the additional cost of shielded cables is more than compensated by predictable operation and reduced costs for troubleshooting and support. 19.1 PDAACCESSTOCYCLONEMODULES For RF spectrum analysis or module aiming on a roof or tower, a personal digital assistant (PDA) is easier to carry than, and as convenient to use as, a notebook computer. The PDA is convenient to use because no scrolling is required to view spectrum analysis results.

RSSI and jitter.

master module evaluation data.

information that identifies the module, software, and firmware. To access this data in a format the fits a 320 x 240 pixel PDA screen, the PDA must have all of the following:

a Compact Flash card slot. any of several Compact Flash wired Ethernet cards. a wired Ethernet connection to the module. a browser directed to http://ModuleIPAddress/pda.html. The initial PDA tab reports link status, as shown in Figure 115. Issue2,November2007 Draft5forRegulatoryReview 333 Release8 InstallationandConfigurationGuide Figure 115: PDA Quick Status tab, example An example of the Spectrum Analyzer tab for PDAs is displayed in Figure 116. For additional information about the Spectrum Analyzer feature, see Monitoring the RF Environment on Page 369. Figure 116: PDA Spectrum Analyzer tab of SM, example Examples of the Spectrum Results and Information tabs for PDAs are shown in Figure 117 and Figure 118. Issue2,November2007 Draft5forRegulatoryReview 334 Release8 InstallationandConfigurationGuide Figure 117: PDA Spectrum Results tab of SM, example Figure 118: PDA Information tab of SM, example Examples of the AP Evaluation and Aim tabs for PDAs are shown in Figure 119 and Figure 120. Issue2,November2007 Draft5forRegulatoryReview 335 Release8 InstallationandConfigurationGuide Figure 119: PDA AP Evaluation tab of SM, example Figure 120: PDA Aim tab of SM, example Issue2,November2007 Draft5forRegulatoryReview 336 Release8 19.2 INSTALLINGANAP InstallationandConfigurationGuide To install the Cyclone AP, perform the following steps. Procedure 19: Installing the AP 1. Begin with the AP in the powered-down state. 2. Choose the best mounting location for your particular application. Modules need not be mounted next to each other. They can be distributed throughout a given site. However, the 60 offset must be maintained. Mounting can be done with stainless steel hose clamps or another equivalent fastener. 3. Align the AP as follows:

a. Move the module to where the link will be unobstructed by the radio horizon and no objects penetrate the Fresnel zone. (The Cyclone System Calculator page AntennaElevationCalcPage.xls automatically calculates the minimum antenna elevation that is required to extend the radio horizon to the other end of the link. The Cyclone System Calculator page FresnelZoneCalcPage.xls automatically calculates the Fresnel zone clearance that is required between the visual line of sight and the top of a high-elevation object.) b. Use a local map, compass, and/or GPS device as needed to determine the direction that one or more APs require to each cover the intended 60 sector. c. Apply the appropriate degree of downward tilt. (The Cyclone System Calculator page DowntiltCalcPage.xls automatically calculates the angle of antenna downward tilt that is required.) d. Ensure that the nearest and furthest SMs that must register to this AP are within the beam coverage area. (The Cyclone System Calculator page BeamwidthRadiiCalcPage.xls automatically calculates the radii of the beam coverage area.) 4. Using stainless steel hose clamps or equivalent fasteners, lock the AP in the proper direction and downward tilt. 5. Remove the base cover of the AP. (See Figure 46 on Page 178.) 6. Attach the cables to the AP.

(See Procedure 5 on Page 184.) NOTE:When power is applied to a Cyclone module or the unit is reset on the web-based interface, the module requires approximately 25 seconds to boot. During this interval, self-tests and other diagnostics are being performed. See Table 40 on Page 179. end of procedure 19.3 INSTALLINGACONNECTORIZEDFLATPANELANTENNA To install a connectorized flat panel antenna to a mast or structure, follow instructions that the manufacturer provides. Install the antenna safely and securely, consistent with industry practices. The Universal Mounting Bracket available from Last Mile Gear (Part Number SMMB-1 and consisting of a mounting bracket and L-shaped aluminum tube) holds one Cyclone module, but cannot hold both the module and a connectorized antenna. The SMMB-2 is a heavy duty bracket that can hold both a 900-MHz module and its connectorized antenna. See Module Support Brackets on Page 57. Issue2,November2007 Draft5forRegulatoryReview 337 Release8 InstallationandConfigurationGuide IMPORTANT!

Connectorized antennas require professional installation. The professional installer is responsible for

selection of an antenna that the regulatory agency has approved for use with the Cyclone 900-MHz AP and SM. setting of the gain consistent with regulatory limitations and antenna specifications. ensuring that the polarityhorizontal or verticalis identical on both ends of the link. (This may be less obvious where an integrated antenna is used on one end and a connectorized on the other.) use of moisture sealing tape or wrap to provide long-term integrity for the connection. 19.4 INSTALLINGAGPSANTENNA The following information describes the recommended tools and procedures to mount the GPS antenna. Recommended Tools for GPS Antenna Mounting The following tools may be needed for mounting the GPS antenna:

3/8 nut driver 12 adjustable wrench 7/16 wrench

Needle-nose pliers Mounting a GPS Antenna Perform the following procedure to mount a GPS antenna. Procedure 20: Mounting the GPS antenna 1. Ensure that the mounting position

has an unobstructed view of the sky to 20 above the horizon. is not the highest object at the site. (This is important for lightning protection.) is not further than 100 feet (30.4 meters) of cable from the CMM2 or CMMmicro. 2. Select a pole that has an outside diameter of 1.25 to 1.5 inches (3 to 4 cm) to which the GPS antenna bracket can be mounted. 3. Place the U-bolts (provided) around the pole as shown in Figure 121. 4. Slide the GPS antenna bracket onto the U-bolts. 5. Slide the ring washers (provided) onto the U-bolts. Issue2,November2007 Draft5forRegulatoryReview 338 Release8 InstallationandConfigurationGuide 6. Slide the lock washers (provided) onto the U-bolts. 7. Use the nuts (provided) to securely fasten the bracket to the U-bolts. end of procedure Figure 121: Detail of GPS antenna mounting 19.4.1 RecommendedMaterialsforCablingtheGPSAntenna The following materials are required for cabling the GPS antenna:

up to 100 feet (30.4 meters) of LMR200 coaxial cable 2 Times Microwave N-male connectors (Times Microwave P/N TC-200-NM) or equivalent connectors. 19.4.2 CablingtheGPSAntenna Connect the GPS coax cable to the female N-connector on the GPS antenna. 19.5 INSTALLINGACMM2 Ensure that you comply with standard local or national electrical and climbing procedures when you install the CMM2. 19.5.1 CMM2InstallationTemperatureRange Install the CMM2 outside only when temperatures are above 4 F (20 C). The bulkhead connector and the bushings and inserts in the bulkhead connector are rated for the full 40 to +131 F (40 to +55 C) range of the CMM2. However, for dynamic operations (loosening, tightening, and inserting), they are compliant at, and rated for, only temperatures at or above 4 F (20 C). Issue2,November2007 Draft5forRegulatoryReview 339 Release8 19.5.2 RecommendedToolsforMountingaCMM2 InstallationandConfigurationGuide The following tools may be needed for mounting the CMM2:

3/8 nut driver 12 adjustable wrench 14-mm wrench for pole-mounting needle-nose pliers 19.5.3 MountingaCMM2 Perform the following procedure to mount the CMM2. Procedure 21: Mounting the CMM2 1. Ensure that the mounting position

is not further than 328 feet (100 meters) of cable from the furthest AP or BH that the CMM2 will serve. is not closer than 10 feet (3 meters) to the nearest AP or BH. is not further than 100 feet (30.4 meters) of cable from the intended mounting position of the GPS antenna. allows you to fully open the door of the CMM2 for service. 2. Select a support structure to which the flanges of the CMM2 can be mounted. 3. If the support structure is a wall, use screws or bolts (neither is provided) to attach the flanges to the wall. If the support structure is an irregular-shaped object, use adjustable stainless steel bands (provided) to attach the CMM2 to the object. If the support structure is a pole that has an outside diameter of 3 to 8 cm, or 1.25 to 3 inches, use a toothed V-bracket (provided) to a. attach the V-bracket to the pole as shown in Figure 122. b. attach the CMM2 flanges to the V-bracket. 4. 5. Figure 122: Detail of pole mounting end of procedure Issue2,November2007 Draft5forRegulatoryReview 340 Release8 19.5.4 CablingaCMM2 InstallationandConfigurationGuide IMPORTANT!

Where you deploy CMM2s, one AP in each AP cluster must be connected to the master port on the CMM2, and each module connected to a CMM2 must be configured to Sync to Received Signal (Timing Port). If either is not done, then the GPS receiver sends no sync pulse to the remaining ports. Perform the following procedure to attach the CMM2 cables on both ends:

Procedure 22: Cabling the CMM2 1. Carefully review the practices recommended in Best Practices for Cabling on Page 182. 2. Remove the base cover from any AP or BH that is to be connected to this CMM2. See Figure 46 on Page 178. 3. Remove the GPS sync cable knockout from the base cover. 4. For any AP that is to be connected to this CMM2, set the AP Sync Input Configuration Page parameter to the Sync to Received Signal (Timing Port) selection. 5. Review the schematic drawing inside the CMM2. 6. Set the 115-/230-volt switch in the CMM2 consistent with the power source. See Figure 123. Fuse receptacle AC power connectors Figure 123: Location of 115-/230-volt switch 115/230 V switch Issue2,November2007 Draft5forRegulatoryReview 341 Release8 InstallationandConfigurationGuide CAUTION!

Failure to set the 115-/230-volt switch correctly can result in damage to equipment. IMPORTANT!

The AC power connectors are labeled N for Neutral, L for Line, and PE for Protective Earth (PE) 4 mm2 or 12 AWG. or ground. The maximum thickness of wire to be used is 7. Route the Ethernet cables from the APs and or BHs to the CMM2. The strain relief plugs on the CMM2 have precut holes. Each hole of the strain relief is designed to hold two CAT 5 UTP cables or one shielded cable. The Ethernet cables have RJ-45 (standard Ethernet) connectors that mate to corresponding ports inside the CMM2. These ports are labeled J3. Eight J3 ports are available on the CMM2 to accommodate any combination of APs and BHs. The logical connections in the CMM2 are displayed in Figure 124. Issue2,November2007 Draft5forRegulatoryReview 342 Release8 InstallationandConfigurationGuide TO DOOR GROUND BT-0488-011 BT-0588 T H W K L B N R G

+-

BT-0563-XXX 8 BT-0563-XXX 7 BT-0563-XXX 6 GPS Receiver S P G P A O T BT-0563-XXX BT-0563-XXX 5 4 J 3 G P S S y n c BT-0563-XXX 3 BT-0563-XXX 2 BT-0563-XXX 1 M a s t e r PWR LED Interconnect Board

-

+

+

-

+

WHT GRN BLK BLK WHT GRN BLK BT-0562-XXX 8 8 BT-0556-008 BT-0562-XXX 7 7 BT-0556-008 BT-0562-XXX 6 6 BT-0556-008 T E N R E H T E P A O T BT-0562-XXX BT-0562-XXX 5 4 J 1 E t h e r n e t I n h c t i w S o t t e n r e h t E 2 J 5 4 BT-0556-008 BT-0556-008 BT-0562-XXX 3 3 BT-0556-008 UPLINK PORT:

NON-CANOPY ETHERNET DEVICES ETHERNET SWITCH PORTS B T

-

0 5 5 6

-

0 0 8 B T

-

0 5 5 6

-

0 0 8 B T

-

0 5 5 6

-

0 0 8 B T

-

0 5 5 6

-

0 0 8 B T

-

0 5 5 6

-

0 0 8 B T

-

0 5 5 6

-

0 0 8 B T

-

0 5 5 6

-

0 0 8 B T

-

0 5 5 6

-

0 0 8 TO J2 Remove lines from power supply if using external DC supply BT-0588 I H T C W S T E N R E H T E O T BT-0562-XXX 2 2 BT-0556-008 Strain relief strap for incoming power wiring BT-0562-XXX 1 1 BT-0556-008 BLK GRN WHT Power Supply Replace Fuse with Type FSM 3.15A 115/230V Switch TO AC LINE SOURCE NEUTRAL GROUND HOT BT-0555-023 TO GPS ANTENNA WARNING: DISCONNECT ALL POWER BEFORE SERVICING Figure 124: Layout of logical connections in CMM2 8. Connect the Ethernet cable from the first AP or BH to the Port 1 in the J3 ports in the CMM2. This port is the master Ethernet port for the CMM2 and should be connected first in all cases. Figure 125 on Page 344 is a photograph of a properly wired CMM2. Issue2,November2007 Draft5forRegulatoryReview 343 InstallationandConfigurationGuide Ethernet switch Extra fuse Release8 GPS sync Ethernet DC power connectors AC power connectors Figure 125: Cyclone CMM2, front view 9. Connect the remaining Ethernet cables to the remaining J3 ports. 10. Route the GPS sync (serial) cables from the APs to the CMM2. The GPS sync cables have 6-conductor RJ-11 connectors that mate to corresponding ports inside the CMM2. These ports are labeled J1. Eight J1 ports are available on the CMM2 to accommodate any combination of APs and BHs. 11. Connect the GPS sync cable from the first AP or BH to the Port 1 in the J1 ports in the CMM2. See Figure 125 on Page 344. This port is the master GPS sync port for the CMM2 and should be connected first in all cases. This is necessary to initialize the GPS on the CMM2. 12. Connect the remaining GPS sync cables to the remaining J1 ports. 13. If this CMM2 requires network connection, perform the following steps:

a. Route a network cable into the CMM2. b. Connect to the uplink port on the switch. c. Properly ground (connect to Protective Earth [PE]

Cyclone Surge Suppressor provides proper grounding for this situation. NOTE: Instructions for installing a Cyclone Surge Suppressor are provided in Procedure 28 on Page 349.

) the Ethernet cable. The Issue2,November2007 Draft5forRegulatoryReview 344 Release8 InstallationandConfigurationGuide 14. Connect GPS coaxial cable to the N-connector on the outside of the CMM2. See Figure 47 on Page 180. 15. Connect AC or DC power to the CMM2, consistent with Figure 124 on Page 343. NOTE: When power is applied, the following indicators are lighted:

the power LED on the Ethernet switch the green LED on the circuit board, as shown in Figure 126. Figure 126: Port indicator LED on Ethernet switch 16. Verify that each port indicator LED on the Ethernet switch is lit (each AP or BH is reliably connected to the Ethernet switch). 17. Replace the base cover on each AP or BH. 18. Close and lock the CMM2. end of procedure 19.5.5 VerifyingCMM2Connections To verify the CMM2 connections after the APs and or BHs have been installed, perform the following steps:

Procedure 23: Verifying CMM2 connections 1. Access the web-based interface for each AP or BHM by opening http://<ip-address>, where the <ip-address> is the address of the individual module. In the General Status tab of the Home page, verify that the System Time field displays the time in GMT. 2. end of procedure 19.6 INSTALLINGACMMmicro Ensure that you comply with standard local or national electrical and climbing procedures when you install the CMMmicro. Issue2,November2007 Draft5forRegulatoryReview 345 Release8 19.6.1 CMMmicroTemperatureRange InstallationandConfigurationGuide Install the CMMmicro outside only when temperatures are above 4 F (20 C). The bulkhead connector and the bushings and inserts in the bulkhead connector are rated for the full 40 to +131 F (40 to +55 C) range of the CMMmicro. However, for dynamic operations (loosening, tightening, and inserting), they are compliant at, and rated for, only temperatures at or above 4 F (20 C). 19.6.2 RecommendedToolsforMountingaCMMmicro The following tools may be needed during installation:

3/8 nut driver 12 adjustable wrench 14-mm wrench for installation of pole-mounting brackets needle-nose pliers 19.6.3 MountingaCMMmicro Perform the following procedure to mount the CMMmicro. Procedure 24: Mounting the CMMmicro 1. Ensure that the mounting position

is not further than 328 feet (100 meters) from the furthest AP or BH that the CMMmicro will serve. is not closer than 10 feet (3 meters) to the nearest AP or BH. is not further than 100 feet (30.5 meters) of cable from the intended mounting position of the GPS antenna. allows you to fully open the door for service. 2. Select a support structure to which the flanges can be mounted. 3. If the support structure is a wall, use screws or bolts (neither is provided) to attach the flanges to the wall. If the support structure is an irregular-shaped object, use adjustable stainless steel bands (provided) to attach the CMMmicro to the object. If the support structure is a pole that has an outside diameter of 1.25 to 3 inches

(3 to 8 cm), use a toothed V-bracket (provided) to d. attach the V-bracket to the pole as shown in Figure 122 on Page 340. e. attach the CMMmicro flanges to the V-bracket. 4. end of procedure 19.6.4 InstallingthePowerSupplyfortheCMMmicro Install the CMMmicro power converter in only a hut, wiring closet, or weatherized NEMA-

approved enclosure. This is imperative to keep moisture away from the power converter, not to shield it from harsh temperatures. Issue2,November2007 Draft5forRegulatoryReview 346 Release8 InstallationandConfigurationGuide WARNING!

Although the output of the power converter is 24 V, the 100-W power rating classifies the converter as a Class 2 electric device. For this reason, whenever you work on power in the CMMmicro, you must first disconnect the DC converter from the AC power source. Perform the following procedure to install the provided power supply. Procedure 25: Installing the Power Supply for the CMMmicro 1. Connect the 6-ft (2-m) AC power cord to the power converter (but not yet to an AC receptacle). 2. Select the length of power cord as follows:

a. b. If either mounting the unit inside with the power converter or outside within 9 ft (2.8 m) of the power converter, select the 10-ft (3-m) DC power cord (rated for outdoor use). If mounting the unit outside and further than 9 ft (2.8 m) from the power converter, ensure that this additional length of cord is either UV-resistant or shielded from UV rays.

use a terminal block, connector, or splice to add the additional length. protect the terminal block, connector, or splice (as inside a weatherized enclosure, for example). Table 50: Wire size for CMMmicro power runs of longer than 9 feet (2.8 m) DC Power Cord Length 990 ft (325 m) 91145 ft (2645 m) 146230 ft (4670 m)

>230 ft (>70 m) Proper Wire Size 12 AWG (4 mm2) 10 AWG (6 mm2) 8 AWG (10 mm2) 6 AWG (16 mm2) 3. Refer to Figure 70: CMMmicro connections on Page 221. 4. Feed the power cord through the bulkhead connector of the CMMmicro. 5. Connect the converter lead whose insulation has a white stripe to +V on the CMMmicro terminal block. 6. Connect the converter lead whose insulation is solid black to V on the CMMmicro terminal block. end of procedure Issue2,November2007 Draft5forRegulatoryReview 347 Release8 19.6.5 CablingaCMMmicro InstallationandConfigurationGuide Perform the following procedure to attach the CMMmicro cables on both ends:

Procedure 26: Cabling the CMMmicro 1. Remove the base cover from any AP or BH that is to be connected to this CMMmicro. See Figure 46 on Page 178. 2. Review the schematic drawing inside the CMMmicro and see Figure 70: CMMmicro connections on Page 221. 3. Note that the inserts in the bulkhead connector bushings have precut holes. 4. Remove the hard silicon spacer. 5. Route the Ethernet cables from the APs through the bulkhead connectors to the Ethernet switch inside the CMMmicro. If the BH at this site is a 30/60- or 150/300-Mbps BH a. connect the BH outdoor unit (ODU) to the ODU port of the power indoor unit 6.

(PIDU). b. connect the PIDU to an unpowered port of the CMMmicro. If the BH is of another modulation rate, route the Ethernet cables from the BH through the bulkhead connectors to the Ethernet switch in the CMMmicro. 7. If the site has a wired network feed, route the cable into the CMMmicro and connect it to an unpowered port on the switch. 8. Mount a Cyclone surge suppressor at a low point of the network feed and connect the surge suppressor to solid ground. 9. On the door label, record the MAC and IP addresses of the CMMmicro and all connected equipment. 10. Consistent with practices in your company, note the above information to add later to the company equipment database. 11. Connect the GPS coax cable from the GPS antenna to the female BNC connector in the CMMmicro. 12. If this CMMmicro requires network connection, perform the following steps:

a. Route a network cable into the CMMmicro. b. Connect to the uplink port on the switch. c. Properly ground (connect to Protective Earth [PE]

Cyclone Surge Suppressor provides proper grounding for this situation. NOTE: Instructions for installing a Cyclone Surge Suppressor are provided as part of Procedure 28 on Page 349.

) the Ethernet cable. The 13. Connect the DC power cable to the CMMmicro. 14. Plug the DC converter into an AC receptacle. 15. Verify that the LEDs light. end of procedure Issue2,November2007 Draft5forRegulatoryReview 348 Release8 19.6.6 VerifyingCMMmicroConnections InstallationandConfigurationGuide To verify the CMMmicro connections after the APs and or BHs have been installed, perform the following steps. Procedure 27: Verifying CMMmicro connections 1. Access the web-based interface for each AP or BH by opening http://<ip-address>, where the <ip-address> is the address of the individual module. In the Status page, verify that the time is expressed in GMT. In the menu on the left-hand side of the web page, click on GPS Status. 2. 3. 4. Verify that the AP or BH is seeing and tracking satellites. (To generate the timing pulse, the module must track at least 4 satellites.) end of procedure 19.7 INSTALLINGANSM Installing a Canopy SM consists of two procedures:

Physically installing the SM on a residence or other location and performing a course alignment using the alignment tone (Procedure 28). Verifying the AP to SM link and finalizing alignment using review of power level and jitter, link tests, and review of registration and session counts (Procedure 29 on Page 353). Procedure 28: Installing the SM 1. Choose the best mounting location for the SM. 2. Select the type of mounting hardware appropriate for this location. (For mounting 2.4, 5.2, 5.4, and 5.7 GHz SMs, Last Mile Gear offers the SMMB-1 mounting bracket. For mounting 900 MHz SMs, Last Mile Gear offers the SMMB-2 mounting bracket.) 3. Remove the base cover of the SM. (See Figure 46 on Page 178.) 4. Terminate the UV outside grade Category 5 Ethernet cable with an RJ-45 connector, and connect the cable to the SM. (See Procedure 8 on Page 192.) 5. Optionally, attach the SM to the arm of the Cyclone Passive Reflector dish assembly as shown in Figure 127. RECOMMENDATION:

A reflector in this instance reduces the beamwidth to reduce interference. The arm is molded to receive and properly aim the module relative to the aim of the dish. Use stainless steel hose clamps for the attachment. Issue2,November2007 Draft5forRegulatoryReview 349 Release8 InstallationandConfigurationGuide Stainless steel hose clamps Reflector dish arm Figure 127: SM attachment to reflector arm 6. Use stainless steel hose clamps or equivalent fasteners to lock the SM into position. NOTE: The SM grounding method is shown in Figure 128. Figure 128: SM grounding per NEC specifications Issue2,November2007 Draft5forRegulatoryReview 350 Release8 InstallationandConfigurationGuide 7. Remove the cover of the 300SS Surge Suppressor. KEYTOCALLOUTS 1 Holesfor mounting the Surge Suppressor to a flat surface

(such as an outside wall). The distance between centers is 4.25 inches (108 mm). 2 RJ-45 connectorsOne side (neither side is better than the other for this purpose) connects to the Cyclone product (AP, SM, BHM, BHS, or cluster management module). The other connects to the AC adaptors Ethernet connector. 3 Ground postuse heavy gauge (10 AWG or 6 mm2) copper wire for connection. Refer to local electrical codes for exact specifications. 4 Ground Cable Openingroute the 10 AWG (6 mm2) ground cable through this opening. 5 CAT-5 Cable Knockoutsroute the two CAT-5 cables through these openings, or alternatively through the Conduit Knockouts. 6 Conduit Knockoutson the back of the case, near the bottom. Available for installations where cable is routed through building conduit. Figure 129: Internal view of Cyclone 300SS Surge Suppressor 8. With the cable openings facing downward, mount the 300SS to the outside of the subscriber premises, as close to the point where the Ethernet cable penetrates the residence or building as possible, and as close to the grounding system

(Protective Earth) as possible. 9. Using diagonal cutters or long nose pliers, remove the knockouts that cover the cable openings to the 300SS. 10. Connect an Ethernet cable from the power adapter (located inside the residence or building, outward through the building penetration) to either RJ-45 port of the 300SS. Issue2,November2007 Draft5forRegulatoryReview 351 Release8 InstallationandConfigurationGuide 11. Connect another Ethernet cable from the other RJ-45 port of the 300SS to the Ethernet port of the SM. 12. Refer to Grounding SMs on Page 172. 13. Wrap an AWG 10 (or 6mm2) copper wire around the Ground post of the 300SS. 14. Tighten the Ground post locking nut in the 300SS onto the copper wire. 15. Securely connect the copper wire to the grounding system (Protective Earth) according to applicable regulations. 16. Connect a ground wire to the 300SS. 17. Replace the cover of the 300SS surge suppressor. 18. For coarse alignment of the SM, use the Audible Alignment Tone feature as follows:

a. Set the 2X Rate parameter in the SM to Disable. b. At the SM, connect the RJ-11 6-pin connector of the Alignment Tool Headset to the RJ-11 utility port of the SM. Alternatively, instead of using the Alignment Tool Headset, use an earpiece or small battery-powered speaker connected to Pin 5 (alignment tone output) and Pin 6 (ground) of an RJ-11 connector. c. Listen to the alignment tone for pitch, which indicates greater signal power (RSSI/dBm) by higher pitch. volume, which indicates better signal quality (lower jitter) by higher volume. Figure 130: Audible Alignment Tone kit, including headset and connecting cable d. Adjust the module slightly until you hear the highest pitch and highest volume. If the Configuration web page of the SM contains a 2X Rate parameter, set it back to Enable. e. 19. When you have achieved the best signal (highest pitch, loudest volume), lock the SM in place with the mounting hardware. end of procedure Issue2,November2007 Draft5forRegulatoryReview 352 Release8 19.8 VERIFYINGANAPSMLINK InstallationandConfigurationGuide To verify the AP-SM link after the SM has been installed, perform the following steps. Procedure 29: Verifying performance for an AP-SM link 1. Using a computer (laptop, desktop, PDA) connected to the SM, open a browser and access the SM using the default IP address of http://169.254.1.1 (or the IP address configured in the SM, if one has been configured.) 2. On the General Status tab of the Home page in the SM (shown in Figure 60 on Page 198), look for Power Level and Jitter. IMPORTANT: The received Power Level is shown in dBm and should be maximized. Jitter should be minimized. However, better/lower jitter should be favored over better/higher dBm. For example, if coarse alignment gives an SM a power level of 75 dBm and a jitter measurement of 5, and further refining the alignment drops the power level to 78 dBm and the jitter to 2 or 3, the latter would be better, with the following caveats:

When the receiving link is operating at 1X, the Jitter scale is 0 to 15 with desired jitter between 0 and 4.

When the receiving link is operating at 2X, the Jitter scale is 0 to 15 with desired jitter between 0 and 9. NOTE:

For historical reasons, RSSI is also shown and is the unitless measure of power. The best practice is to use Power Level and ignore RSSI, which implies more accuracy and precision than is inherent in the measurement. 3. Fine-adjust the SM mounting, if needed, to improve Jitter or Power Level. 4. Click the Link Capacity Test tab of the Tools web page in the SM. NOTE: Use of this tool is described under Using the Link Capacity Test Tool (All) on Page 438. 5. Perform several link tests of 10-second duration as follows:

a. Type into the Duration field how long (in seconds) the RF link should be tested. b. Leave the Packet Length field (when present) set to the default of 1522 bytes or type into that field the packet length at which you want the test conducted. c. Leave the Number of Packets field set to 0 (to flood the link). d. Click the Start Test button. e. View the results of the test. Issue2,November2007 Draft5forRegulatoryReview 353 Release8 6. InstallationandConfigurationGuide If these link tests fail to consistently show 90% or greater efficiency in 1X operation or 50 to 60% efficiency in 2X, troubleshoot the link, using the data as follows:

If the downlink is consistently 90% efficient, but the uplink is only 40%, this indicates trouble for the SM transmitting to the AP. Have link tests performed for nearby SMs. If their results are similar, investigate a possible source of interference local at the AP. If the uplink is consistently 90% efficient, but the downlink is only 40%, this indicates trouble for the AP transmitting to the SM. Investigate a possible source of interference near the SM.

If these link tests consistently show 90% or greater efficiency in 1X operation, or 50 to 60% efficiency in 2X operation, in both uplink and downlink, continue this procedure. 7. Open the Session Status tab in the Home page of the AP. NOTE: An example of this page is shown in Figure 131. Issue2,November2007 Draft5forRegulatoryReview 354 Release8 InstallationandConfigurationGuide Figure 131: AP/SM link status indications in the AP Session Status tab 8. Find the Session Count line under the MAC address of the SM. 9. Check and note the values for Session Count, Reg Count, and Re-Reg Count. Issue2,November2007 Draft5forRegulatoryReview 355 Release8 InstallationandConfigurationGuide 10. Briefly monitor these values, occasionally refreshing this page by clicking another tab and then the Session Status tab again. 11. If these values are low (for example, 1, 1, and 0, respectively, meaning that the SM registered and started a stable session once) and not changing a. consider the installation successful. b. monitor these values from the network office over the next several hours and days. If these values are greater than 1, 1, and 0, or they increase while you are monitoring them, troubleshoot the link. (For example, recheck jitter as described in Procedure 28: Installing the SM or recheck link efficiency as described in this procedure, then look for sources of RF interference or obstructions.) end of procedure 19.9 INSTALLINGAREFLECTORDISH The internal patch antenna of the module illuminates the Cyclone Passive Reflector Dish from an offset position. The module support tube provides the proper angle for this offset. 19.9.1 BothModulesMountedatSameElevation For cases where the other module in the link is mounted at the same elevation, fasten the mounting hardware leg of the support tube vertical for each module. When the hardware leg is in this position

the reflector dish has an obvious downward tilt. the module leg of the support tube is not vertical. For a mount to a non-vertical structure such as a tapered tower, use a plumb line to ensure that the hardware leg is vertical when fastened. Proper dish, tube, and module positions for a link in this case are illustrated in Figure 132. The dish is tipped forward, not vertical, but the focus of the signal is horizontal.

--------------------------------------------EARTH--------------------------------------------

Figure 132: Correct mount with reflector dish Issue2,November2007 Draft5forRegulatoryReview 356 Release8 Improper dish, tube, and module positions for this case are illustrated in Figure 133. InstallationandConfigurationGuide

--------------------------------------------EARTH--------------------------------------------

Figure 133: Incorrect mount with reflector dish 19.9.2 ModulesMountedatDifferentElevations For cases where the other module in the link is mounted at a different elevation, the assembly hardware allows tilt adjustment. The proper angle of tilt can be calculated as a factor of both the difference in elevation and the distance that the link spans. Even in this case, a plumb line and a protractor can be helpful to ensure the proper tilt. This tilt is typically minimal. The number of degrees to offset (from vertical) the mounting hardware leg of the support tube is equal to the angle of elevation from the lower module to the higher module (b in the example provided in Figure 34 on Page 146). 19.9.3 MountingAssembly Both the hardware that Mounting Assembly 27RD provides for adjustment and the relationship between the offset angle of the module and the direction of the beam are illustrated in Figure 134. Issue2,November2007 Draft5forRegulatoryReview 357 Release8 InstallationandConfigurationGuide Figure 134: Mounting assembly, exploded view 19.10 INSTALLINGABHTIMINGMASTER To install the Cyclone BHM, perform the following steps:

Procedure 30: Installing the BHM 1. Access the General tab of the Configuration page in the BHM. 2. If this is a 20-Mbps BH, set the 2X Rate parameter to Disabled (temporarily for easier course aiming). 3. Click the Save Changes button. 4. Click the Reboot button. 5. After the reboot is completed, remove power from the BHM. 6. Choose the best mounting location for your particular application. 7. Attach the BHM to the arm of the Cyclone Passive Reflector dish assembly as shown in Figure 135. RECOMMENDATION:

The arm is molded to receive and properly aim the module relative to the aim of the dish. ( See Figure 132 on Page 356.) Stainless steel hose clamps should be used for the attachment. Issue2,November2007 Draft5forRegulatoryReview 358 Release8 InstallationandConfigurationGuide Stainless steel hose clamps Reflector dish arm Figure 135: BH attachment to reflector arm 8. Align the BHM as follows:

a. Move the module to where the link will be unobstructed by the radio horizon and no objects penetrate the Fresnel zone. (The Cyclone System Calculator page AntennaElevationCalcPage.xls automatically calculates the minimum antenna elevation that is required to extend the radio horizon to the other end of the link. The Cyclone System Calculator page FresnelZoneCalcPage.xls automatically calculates the Fresnel zone clearance that is required between the visual line of sight and the top of a high-elevation object.) b. Use a local map, compass, and/or GPS device as needed to determine the direction to the BHS. c. Apply the appropriate degree of downward or upward tilt. (The Cyclone System Calculator page DowntiltCalcPage.xls automatically calculates the angle of antenna downward tilt that is required.) d. Ensure that the BHS is within the beam coverage area. (The Cyclone System Calculator page BeamwidthRadiiCalcPage.xls automatically calculates the radii of the beam coverage area.) 9. Using stainless steel hose clamps or equivalent fasteners, lock the BHM into position. 10. Remove the base cover of the BHM. (See Figure 46 on Page 178.) 11. If this BHM will not be connected to a CMMmicro, optionally connect a utility cable to a GPS timing source and then to the RJ-11 port of the BHM. 12. Either connect the BHM to the CMM or connect the DC power converter to the BHM and then to an AC power source. RESULT: When power is applied to a Cyclone module or the unit is reset on the web-based interface, the module requires approximately 25 seconds to boot. During this interval, self-tests and other diagnostics are being performed. 13. Access the General tab of the Configuration page of this BHM. Issue2,November2007 Draft5forRegulatoryReview 359 Release8 InstallationandConfigurationGuide 14. If the CMM is a CMMmicro, set the Sync Input parameter to the Sync to Received Signal (Power Port) selection. If the CMM is a CMM2, set the Sync Input parameter to the Sync to Received Signal (Timing Port) selection. end of procedure 19.11 INSTALLINGABHTIMINGSLAVE Installing a Cyclone BHS consists of two procedures:

Physically installing the BHS and performing a course alignment using the alignment tone (Procedure 31). Verifying the BH link and finalizing alignment using review of power level and jitter, link tests, and review of registration and session counts (Procedure 32 on Page 361). Procedure 31: Installing the BHS 1. Choose the best mounting location for the BHS. 2. Remove the base cover of the BHS. (See Figure 46 on Page 178.) 3. Terminate the UV outside grade Category 5 Ethernet cable with an RJ-45 connector, and connect the cable to the BHS. (See Procedure 8 on Page 192.) 4. Attach the BHS to the arm of the Cyclone Passive Reflector dish assembly as shown in Figure 127 on Page 350. RECOMMENDATION:

The arm is molded to receive and properly aim the BH relative to the aim of the dish. Use stainless steel hose clamps for the attachment. 5. Use stainless steel hose clamps or equivalent fasteners to lock the BHS into position. 6. Remove the cover of the 300SS Surge Suppressor. 7. With the cable openings facing downward, mount the 300SS as close to the grounding system (Protective Earth) as possible. 8. Using diagonal cutters or long nose pliers, remove the knockouts that cover the cable openings to the 300SS. 9. Connect an Ethernet cable from the power adapter to either RJ-45 port of the 300SS. 10. Connect another Ethernet cable from the other RJ-45 port of the 300SS to the Ethernet port of the BHS. 11. Refer to Grounding SMs on Page 172. 12. Wrap an AWG 10 (or 6mm2) copper wire around the Ground post of the 300SS. 13. Tighten the Ground post locking nut in the 300SS onto the copper wire. 14. Securely connect the copper wire to the grounding system (Protective Earth) according to applicable regulations. Issue2,November2007 Draft5forRegulatoryReview 360 Release8 InstallationandConfigurationGuide 15. Connect a ground wire to the 300SS. 16. Replace the cover of the 300SS surge suppressor. 17. For coarse alignment of the BHS, use the Audible Alignment Tone feature as follows:

a. If the Configuration web page of the BHS contains a 2X Rate parameter, set it to Disable. b. At the BHS, connect the RJ-11 6-pin connector of the Alignment Tool Headset (shown in Figure 130 on Page 352) to the RJ-11 utility port of the SM. Alternatively, instead of using the Alignment Tool Headset, use an earpiece or small battery-powered speaker connected to Pin 5 (alignment tone output) and Pin 6 (ground) of an RJ-11 connector. c. Listen to the alignment tone for pitch, which indicates greater signal power (RSSI/dBm) by higher pitch. volume, which indicates better signal quality (lower jitter) by higher volume. d. Adjust the module slightly until you hear the highest pitch and highest volume. If the Configuration web page of the BHS contains a 2X Rate parameter, set it back to Enable. e. 18. When you have achieved the best signal (highest pitch, loudest volume), lock the BHS in place with the mounting hardware. end of procedure 19.12 UPGRADINGABHLINKTOBH20 To replace a pair of 10-Mbps BHs with 20-Mbps BHs, you can minimize downtime by temporarily using the 10-Mbps capability in the faster modules. However, both interference and differences in receiver sensitivity can make alignment and link maintenance more difficult than in the previous 10-Mbps link. The effects of these factors are greater at greater link distances, particularly at 5 miles or more. In shorter spans, these factors may not be prohibitive. For these cases, set the first replacement module to 1X Rate and establish the link to the 10-Mbps BH on the far end. Similarly, set the second replacement module to 1X Rate and re-establish the link. With both of the faster modules in place and with an operational link having been achieved, reset their modulation to 2X Rate (20 Mbps). 19.13 VERIFYINGABHLINK To verify the backhaul link after the BHS has been installed, perform the following steps. Procedure 32: Verifying performance for a BH link 1. Using a computer (laptop, desktop, PDA) connected to the BHS, open a browser and access the BHS using the default IP address of http://169.254.1.1 (or the IP address configured in the BHS, if one has been configured.) 2. On the General Status tab of the Home page in the BHS (shown in Figure 65 on Page 211), look for Power Level and Jitter. Issue2,November2007 Draft5forRegulatoryReview 361 Release8 InstallationandConfigurationGuide IMPORTANT: The received Power Level is shown in dBm and should be maximized. Jitter should be minimized. However, better/lower jitter should be favored over better/higher dBm. For example, if coarse alignment gives a BHS a power level of 75 dBm and a jitter measurement of 5, and further refining the alignment drops the power level to 78 dBm and the jitter to 2 or 3, the latter would be better, with the following caveats:

When the receiving link is operating at 1X, the Jitter scale is 0 to 15 with desired jitter between 0 and 4.

When the receiving link is operating at 2X, the Jitter scale is 0 to 15 with desired jitter between 0 and 9. NOTE:

For historical reasons, RSSI is also shown and is the unitless measure of power. The best practice is to use Power Level and ignore RSSI, which implies more accuracy and precision than is inherent in its measurement. 3. Fine-adjust the BHS mounting, if needed, to improve Jitter or Power Level. 4. Click the Link Capacity Test tab of the Tools web page in the BHS. NOTE: Use of this tool is described under Using the Link Capacity Test Tool (All) on Page 438. 5. Perform several link tests of 10-second duration as follows:

a. Type into the Duration field how long (in seconds) the RF link should be tested. b. Leave the Packet Length field (when present) set to the default of 1522 bytes or type into that field the packet length at which you want the test conducted. 6. c. Leave the Number of Packets field set to 0 (to flood the link). d. Click the Start Test button. e. View the results of the test. If these link tests fail to consistently show 90% or greater efficiency in 1X operation or 50 to 60% efficiency in 2X, troubleshoot the link, using the data as follows:

If the downlink is consistently 90% efficient, but the uplink is only 40%, this indicates trouble for the BHS transmitting to the BHM. Investigate a possible source of interference near the BHM. If the uplink is consistently 90% efficient, but the downlink is only 40%, this indicates trouble for the BHM transmitting to the BHS. Investigate a possible source of interference near the BHS.

If these link tests consistently show 90% or greater efficiency in 1X operation, or 50 to 60% efficiency in 2X operation, in both uplink and downlink, continue this procedure. 7. Open the Session Status tab in the Home page of the BHM. NOTE: An example of this page is shown in Figure 136. Issue2,November2007 Draft5forRegulatoryReview 362 Release8 InstallationandConfigurationGuide Figure 136: Session Status tab of BHM 8. Find the Session Count line under the MAC address of the BHS. 9. Check and note the values for Session Count, Reg Count, and Re-Reg Count. 10. Briefly monitor these values, occasionally refreshing this page by clicking another tab and then the Session Status tab again. 11. If these values are low (for example, 1, 1, and 0, respectively, meaning that the BHS registered and started a stable session once) and not changing a. consider the installation successful. b. monitor these values from the network office over the next several hours and days. If these values are greater than 1, 1, and 0, or they increase while you are monitoring them, troubleshoot the link. (For example, recheck jitter as described in Procedure 28: Installing the SM or recheck link efficiency as described in this procedure, then look for sources of RF interference or obstructions.) end of procedure Issue2,November2007 Draft5forRegulatoryReview 363 Release8 20 VERIFYINGSYSTEMFUNCTIONALITY InstallationandConfigurationGuide To verify system functionality after the APs and or BHs have been installed, perform the following steps. Procedure 33: Verifying system functionality 1. For each installed AP, use a computer or PDA connected to an SM set to a compatible configuration (frequency and color code, for example) and verify link functionality. 2. For each BH installed, use a notebook computer connected to a BH (BHM or BHS, as appropriate) set to a compatible configuration and verify link functionality. If a network data feed is present and operational, use an SM or BHS to verify network functionality. 3. end of procedure Issue2,November2007 Draft5forRegulatoryReview 365 Release8 OperationsGuide OOOPPPEEERRRAAATTTIIIOOONNNSSSGGGUUUIIIDDDEEE Issue2,November2007 Draft5forRegulatoryReview 367 Release8 21 GROWINGYOURNETWORK Keys to successfully growing your network include

monitoring the RF environment.

considering software release compatibility. redeploying modules appropriately and quickly. OperationsGuide 21.1 MONITORINGTHERFENVIRONMENT Regardless of whether you are maintaining or growing your network, you may encounter new RF traffic that can interfere with your current or planned equipment. Regularly measuring over a period of time and logging the RF environment, as you did before you installed your first equipment in an area, enables you to recognize and react to changes. 21.1.1 SpectrumAnalyzer(NotavailableforCycloneOFDM) IMPORTANT!

When you enable the Spectrum Analyzer on a module, it enters a scan mode and drops any RF connection it may have had. Scanning mode ends when either you click Disable on the Spectrum Analyzer page, or it times out after 15 minutes and returms to operational mode. For this reason

do not enable the spectrum analyzer on a module you are connected to via RF. The connection will drop for 15 minutes, and when the connection is re-established no readings will be displayed. be advised that, if you enable the spectrum analyzer by Ethernet connection, the RF connection to that module drops. You can use any module to see the frequency and power level of any detectable signal that is within, just above, or just below the frequency band range of the module. RECOMMENDATION:

Vary the days and times when you analyze the spectrum in an area. The RF environment can change throughout the day or throughout the week. Temporarily deploy an SM or BHS for each frequency band range that you need to monitor and access the Spectrum Analyzer tab in the Tools web page of the module.

(For access from a PDA, see PDA Access to Cyclone Modules on Page 333.) To enter the scan mode and view readings, click Enable. After clicking the Enable button on the Spectrum Analyzer page, the first painting may not display bars for all frequencies, especially on frequency bands with a large number of center channels, like the 5.4 GHz band. Clicking Enable again will display the entire spectrum bar graph. Alternatively, you can set the Auto Refresh time on the Configuration => General page to a few seconds to have the Spectrum Analyzer Issue2,November2007 Draft5forRegulatoryReview 369 Release8 OperationsGuide automatically fully displayed and refreshed. (Setting the Auto Refresh time back to 0 will disable refresh.) 21.1.2 GraphicalSpectrumAnalyzerDisplay(NotavailableforCycloneOFDM) An SM/BHS displays the graphical spectrum analyzer. An example of the Spectrum Analyzer tab is shown in Figure 137. Figure 137: Spectrum Analyzer tab of SM, example Colors in the display have the following meanings:

Green bars show the most recent measurements.

Yellow ticks show the maximum measurements from the current spectrum analysis session.

Red ticks show measurements of 40 dBm or stronger. To keep the displayed data current, either set Auto Refresh on the modules Configuration => General page to a few seconds, or repeatedly click the Enable button. When you are finished analyzing the spectrum, click the Disable button to return the module to normal operation. 21.1.3 UsingtheAPasaSpectrumAnalyzer(NotavailableforCycloneOFDM) You can temporarily change an AP into an SM and thereby use the spectrum analyzer functionality. This is the only purpose supported for the transformation. CAUTION!

When you change an AP into an SM, any connections to SMs off that AP are lost. Therefore, you should ensure you are connected to the AP through its Ethernet side (not RF side) before changing it into an SM. For example, if you are connected to an AP through one of its SMs and mistakenly change the AP into an SM, you will lose connectivity and will need to gain access to the Ethernet side of the AP through another part of your network to change it back into an AP. Issue2,November2007 Draft5forRegulatoryReview 370 Release8 OperationsGuide To transform the AP into an SM for spectrum analysis and then return the device to an AP, perform the following steps. Procedure 34: Using the Spectrum Analyzer in AP feature 1. Connect to the wired Ethernet interface of the AP. 2. Access the General tab of the Configuration page in the AP. 3. Set the Device Setting parameter to SM. 4. Click the Save Changes button. 5. Click the Reboot button. 6. When the module has rebooted as an SM, click the Tools navigation link on the left side of the Home page. 7. Click the Spectrum Analyzer tab. 8. Either set this page to automatically refresh or repeatedly click the Enable button. RESULT: The SM enters the scan mode. 9. When you are finished analyzing the spectrum, click the Disable button. 10. In the left-side navigation links, click Configuration. 11. Click the General tab. 12. Set the Device Setting parameter to AP. 13. Click the Save Changes button. 14. Click the Reboot button. RESULT: The AP boots with its previous frequency setting. end of procedure Issue2,November2007 Draft5forRegulatoryReview 371 Release8 21.2 CONSIDERINGSOFTWARERELEASECOMPATIBILITY OperationsGuide Within the same Cyclone network, modules can operate on multiple software releases. However, the features that can be enabled are limited to those that the earliest software supports. 21.2.1 DesignationsforHardwareinRadios Cyclone documentation refers to hardware series (for example, Series P9). Cyclone Release 8 requires APs, BHs, and AES SMs to be Series P9 or later hardware. The correlation between hardware series and the MAC addresses of the radio modules is provided in Table 51. Table 51: Hardware series by MAC address Radio Frequency Band Range 900 2.4 5.2 5.4 5.7 Hardware Series P7 or P8 in These MAC Addresses None 0A003E20672B 0A003E00F4E3 None 0A003EF12AFE P9 or Later in These MAC Addresses All 0A003E20672C 0A003E00F4E4 All 0A003EF12AFF Differences in capabilities among these hardware series are summarized in Table 52. Table 52: Hardware series differences Capability Auto-sense Ethernet cable scheme Support CMMmicro Support hardware scheduling in APs1 Support 2X operation in APs and SMs Availability per Hardware Series P7 P9 yes no yes no no yes yes no P8 yes yes no no NOTES:

1. An SM of P7 or P8 series requires an FPGA load through CNUT for access to hardware scheduling, and then only at 1X operation. An AP of P7 or P8 series cannot perform hardware scheduling. Advantage Series P9 APs provide higher throughput and lower latency than earlier series Advantage APs and support configuring the high-priority channel per SM. Regular Cyclone Series P9 APs do not provide the higher throughput and lower latency, but they do support configuring the high-priority channel per SM. Issue2,November2007 Draft5forRegulatoryReview 372 Release8 21.2.2 CMMmicroSoftwareandHardwareCompatibility OperationsGuide The CMMmicro contains both a programmable logic device (PLD) and software. These must be compatible. For example, the PLD that is compatible with CMMmicro Release 2.0.8 is PLD 5. Further, the CMMmicro must be compatible with both the application software release and the hardware of attached APs and BHs. These attached modules must have been manufactured in October 2002 or later. APs and BHs that were manufactured earlier do not support sync on the power leads of the Ethernet port. To determine whether the AP or BH hardware is compatible with the CMMmicro, see Table 53. Table 53: AP/BH compatibility with CMMmicro Frequency Band Range 900 MHz AP 2.4 GHz 5.2 GHz 5.4 GHz 5.7 GHz Range of MAC Addresses (ESNs) Incompatible with CMMmicro none none 0A003E0021C8 none 0A003EF00F79 Compatible with CMMmicro all all 0A003E0021C9 all 0A003EF00F7A 21.2.3 MIBFileSetCompatibility Although MIB files are text files (not software), they define objects associated with configurable parameters and indicators for the module and its links. In each release, some of these parameters and indicators are not carried forward from the previous release, and some parameters and indicators are introduced or changed. For this reason, use the MIB files from your download to replace previous MIB files in conjunction with your software upgrades, even if the file names are identical to those of your previous files. Date stamps on the MIB files distinguish the later set. 21.3 REDEPLOYINGMODULES Successfully redeploying a module may involve

maintaining full and accurate records of modules being redeployed from warehouse stock. exercising caution about

software compatibility. For example, whether desired features can be

enabled with the redeployed module in the network.

procedural handling of the module. For example

whether to align the SM or BHS by power level and jitter or by only jitter.

whether the module auto-senses the Ethernet cable connector scheme.

hardware compatibility. For example, where a CMMmicro is deployed.

the value of each configurable parameter. Whether all are compatible in the new destination. Issue2,November2007 Draft5forRegulatoryReview 373 Release8 OperationsGuide

remembering to use auto discovery to add the redeployed SM to the network in Prizm. 21.3.1 WiringtoExtendNetworkSync The following procedure can be used to extend network sync by one additional hop, as described under Passing Sync in an Additional Hop on Page 95. Where a collocated module receives sync over the air, the collocated modules can be wired to pass the sync as follows:

Procedure 35: Extending network sync 1. Connect the GPS Utility ports of the collocated modules using a sync cable with RJ-11 connectors. 2. Set the Sync Input parameter on the Configuration page of the collocated AP or BH timing master to Sync to Received Signal (Timing Port). 3. Set the Frame Timing Pulse Gated parameter on the Configuration page of the collocated SM or BH timing slave to Enable. NOTE: This setting prevents interference in the event that the SM or BH timing slave loses sync. end of procedure Issue2,November2007 Draft5forRegulatoryReview 374 Release8 22 SECURINGYOURNETWORK 22.1 ISOLATINGAPSFROMTHEINTERNET Ensure that the IP addresses of the APs in your network OperationsGuide

are not routable over the Internet. do not share the subnet of the IP address of your user. RFC 1918, Address Allocation for Private Subnets, reserves for private IP networks three blocks of IP addresses that are not routable over the Internet:

/8 subnets have one reserved network, 10.0.0.0 to 10.255.255.255.

/16 subnets have 16 reserved networks, 172.16.0.0 to 172.31.255.255.

/24 subnets have 256 reserved networks, 192.168.0.0 to 192.168.255.255. 22.2 ENCRYPTINGCYCLONERADIOTRANSMISSIONS Cyclone systems employ the following forms of encryption for security of the wireless link:

BRAIDa security scheme that the cellular industry uses to authenticate wireless devices.

DESData Encryption Standard, an over-the-air link option that uses secret 56-bit keys and 8 parity bits.

AESAdvanced Encryption Standard, an extra-cost over-the-air link option that provides extremely secure wireless connections. AES uses 128-bit secret keys as directed by the government of the U.S.A. AES is not exportable and requires a special AP to process the large keys. BRAID is a stream cipher that the TIA (Telecommunications Industry Association) has standardized. Standard Cyclone APs and SMs use BRAID encryption to

calculate the per-session encryption key (independently) on each end of a link. provide the digital signature for authentication challenges. 22.2.1 DESEncryption Standard Cyclone modules provide DES encryption. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DES Encryption does not affect the performance or throughput of the system. 22.2.2 AESEncryption Last Mile Gear also offers Cyclone products that provide AES encryption. AES uses the Rijndael algorithm and 128-bit keys to establish a higher level of security than DES. Because of this higher level of security, the government of the U.S.A. controls the export of communications products that use AES (among which the Cyclone AES feature activation key is one) to ensure that these products are available in only certain regions and by special permit. Issue2,November2007 Draft5forRegulatoryReview 375 Release8 OperationsGuide The Cyclone distributor or reseller can advise service providers about current regional availability. Cyclone AES products are certified as compliant with the Federal Information Processing Standards (FIPS) in the U.S.A. The National Institute of Standards and Technology (NIST) in the U.S.A. has specified AES for significantly greater security than that which DES provides. NIST selected the AES algorithm for providing the best combination of security, performance, efficiency, implementation, and flexibility. NIST collaborates with industry to develop and apply technology, measurements, and standards. 22.2.3 AESDESOperabilityComparisons This section describes the similarities and differences between DES and AES products, and the extent to which they may interoperate. The DES AP and the DES BHM modules are factory-programmed to enable or disable DES encryption. Similarly, the AES AP and the AES BHM modules are factory-

programmed to enable or disable AES encryption. In either case, the authentication key entered in the Configuration page establishes the encryption key. For this reason, the authentication key must be the same on each end of the link. See Authentication Key on Page 286. Feature Availability Cyclone AES products run the same software as DES products. Thus feature availability and functionality are and will continue to be the same, regardless of whether AES encryption is enabled. All interface screens are identical. However, when encryption is enabled on the Configuration screen

the AES product provides AES encryption. the DES product provides DES encryption. Cyclone AES products and DES products use different FPGA (field-programmable gate array) loads. However, the AES FPGA will be upgraded as needed to provide new features or services similar to those available for DES products. Cyclone DES products cannot be upgraded to AES. To have the option of AES encryption, the operator must purchase AES products. Interoperability Cyclone AES products and DES products do not interoperate when enabled for encryption. For example, An AES AP with encryption enabled cannot communicate with DES SMs. Similarly, an AES Backhaul timing master module with encryption enabled cannot communicate with a DES Backhaul timing slave module. However, if encryption is disabled, AES modules can communicate with DES modules. Issue2,November2007 Draft5forRegulatoryReview 376 Release8 22.3 MANAGINGMODULEACCESSBYPASSWORDS 22.3.1 AddingaUserforAccesstoaModule OperationsGuide From the factory, each Cyclone module has a preconfigured administrator-level account in the name root, which initially requires no associated password. This is the same root account that you may have used for access to the module by telnet or ftp. If you upgrade a module to Release 8 an account is created in the name admin. both admin and root inherit the password that was previously used for access to the module:

the Full Access password, if one was set. the Display-Only Access password, if one was set and no Full Access password was set. IMPORTANT!

If you use Prizm, do not delete the root account from any module. If you use an NMS that communicates with modules through SNMP, do not delete the root account from any module unless you first can confirm that the NMS does not rely on the root account for access to the modules. Each module supports four or fewer user accounts, regardless of account levels. The available levels are ADMINISTRATOR, who has full read and write permissions. This is the level of the root and admin users, as well as any other administrator accounts that one of them creates. INSTALLER, who has permissions identical to those of ADMINISTRATOR except that the installer cannot add or delete users or change the password of any other user. GUEST, who has no write permissions and only a limited view of General Status tab, as shown in Figure 138, and can log in as a user. Issue2,November2007 Draft5forRegulatoryReview 377 Release8 OperationsGuide Figure 138: General Status tab view for GUEST-level account An example of the Add User tab is displayed in Figure 139. Issue2,November2007 Draft5forRegulatoryReview 378 Release8 OperationsGuide Figure 139: Add User tab of SM, example After a password has been set for any ADMINISTRATOR-level account, initial access to the module GUI opens the view of GUEST level (Figure 138). Accounts that cannot be deleted are the current user's own account. the last remaining account of ADMINISTRATOR level. 22.3.2 OverridingForgottenIPAddressesorPasswordsonAP,SM,orBH Cyclone systems offer a plug that allows you to temporarily override some AP/SM/BH settings and thereby regain control of the module. This plug is needed for access to the module in any of the following cases:

You have forgotten either

the IP address assigned to the module. the password that provides access to the module.

The module has been locked by the No Remote Access feature. (See Denying All Remote Access on Page 457 and Reinstating Remote Access Capability on Page 457.)

You want local access to a module that has had the 802.3 link disabled in the Configuration page. Issue2,November2007 Draft5forRegulatoryReview 379 Release8 OperationsGuide You can configure the module such that, when it senses the override plug, it responds by either resetting the LAN1 IP address to 169.254.1.1, allowing access through the default configuration without changing the configuration, whereupon you will be able to view and reset any non-default values as you wish. resetting all configurable parameters to their factory default values. Acquiring the Override Plug You can either purchase or fabricate an override plug as follows. To purchase an override plug for a nominal fee, order the plug at http://www.best-tronics.com/Last Mile Gear.htm. To fabricate an override plug, perform the following steps. Procedure 36: Fabricating an override plug Install an RJ-11 6-pin connector onto a 6-inch length of CAT 5 cable. 1. 2. Pin out all 6-pins. 3. Short (solder together) Pins 4 and 6 on the other end. Do not connect any other wires to anything. The result should be as shown in Figure 140. end of procedure Pin 1 white / orange Pin 1 Pin 2 Pin 2 white / green Pin 3 Pin 3 white / blue Pin 4 green Pin 6 Pin 5 Pin 5 blue Pin 6 orange Pin 4 Figure 140: RJ-11 pinout for the override plug Using the Override Plug IMPORTANT!

While the override plug is connected to a module, the module can neither register nor allow registration of another module. To regain access to the module, perform the following steps. Issue2,November2007 Draft5forRegulatoryReview 380 Release8 OperationsGuide Procedure 37: Regaining access to a module Insert the override plug into the RJ-11 GPS utility port of the module. 1. 2. Power cycle by removing, then re-inserting, the Ethernet cable. RESULT:The module boots with the default IP address of 169.254.1.1, password fields blank, and all other configuration values as previously set. 3. Wait approximately 30 seconds for the boot to complete. 4. Remove the override plug. 5. Set passwords and IP address as desired. 6. Change configuration values if desired. 7. Click the Save Changes button. 8. Click the Reboot button. end of procedure 22.3.3 OverridingForgottenIPAddressesorPasswordsonCMMmicro By using an override toggle switch on the CMMmicro circuit board, you can temporarily override a lost or unknown IP address or password as follows:

Up is the override position in which a power cycle causes the CMMmicro to boot with the default IP address (169.254.1.1) and no password required.

Down is the normal position in which a power cycle causes the CMMmicro to boot with your operator-set IP address and password(s). To override a lost or unknown IP address or password, perform the following steps. Procedure 38: Using the override switch to regain access to CMMmicro IMPORTANT!

In override mode

a CMMmicro provides no power on its ports. any APs or BHs connected to the CMMmicro are not powered. you cannot gain browser access to the CMMmicro through any connected APs or BHs. 1. Gain physical access to the inside of the CMMmicro enclosure. 2. Establish direct Ethernet connectivity to the CMMmicro (not through an AP or BH). 3. Flip the toggle switch up (toward you). 4. Power cycle the CMMmicro. RESULT: The module reboots with the default IP address of 169.254.1.1, password fields blank, and all other configuration values as previously set. 5. Set passwords as desired, or enter a blank space to set no password. 6. Change configuration values if desired. 7. Click the Save Changes button. Issue2,November2007 Draft5forRegulatoryReview 381 Release8 OperationsGuide 8. Flip the toggle switch down (away from you). 9. Click the Reboot button. end of procedure 22.4 REQUIRINGSMAUTHENTICATION Through the use of Prizm Release 2.0 or later, or BAM Release 2.1, you can enhance network security by requiring SMs to authenticate when they register. Three keys and a random number are involved in authentication as follows:

factory-set key in each SM. Neither the subscriber nor the network operator can view or change this key. authentication key, also known as authorization key and skey. This key matches in the SM and AP as the Authentication Key parameter, and in the Prizm database. random number, generated by Prizm or BAM and used in each attempt by an SM to register and authenticate. The network operator can view this number. session key, calculated separately by the SM and Prizm or BAM, based on both the authentication key (or, by default, the factory-set key) and the random number. Prizm or BAM sends the session key to the AP. The network operator cannot view this key. None of the above keys is ever sent in an over-the-air link during an SM registration attempt. However, with the assumed security risk, the operator can create and configure the Authentication Key parameter. See Authentication Key on Page 286. 22.5 FILTERINGPROTOCOLSANDPORTS You can filter (block) specified protocols and ports from leaving the SM and entering the Cyclone network. This protects the network from both intended and inadvertent packet loading or probing by network users. By keeping the specified protocols or ports off the network, this feature also provides a level of protection to users from each other. Protocol and port filtering is set per SM. Except for filtering of SNMP ports, filtering occurs as packets leave the SM. If an SM is configured to filter SNMP, then SNMP packets are blocked from entering the SM and, thereby, from interacting with the SNMP portion of the protocol stack on the SM. 22.5.1 PortFilteringwithNATEnabled Where NAT is enabled, you can filter only the three user-defined ports. The following are example situations in which you can configure port filtering where NAT is enabled.

To block a subscriber from using FTP, you can filter Ports 20 and 21 (the FTP ports) for both the TCP and UDP protocols.

To block a subscriber from access to SNMP, you can filter Ports 161 and 162

(the SNMP ports) for both the TCP and UDP protocols. NOTE: In only the SNMP case, filtering occurs before the packet interacts with the protocol stack. Issue2,November2007 Draft5forRegulatoryReview 382 Release8 22.5.2 ProtocolandPortFilteringwithNATDisabled OperationsGuide Where NAT is disabled, you can filter both protocols and the three user-defined ports. Using the check boxes on the interface, you can either

allow all protocols except those that you wish to block. block all protocols except those that you wish to allow. You can allow or block any of the following protocols:

PPPoE (Point to Point Protocol over Ethernet)

Any or all of the following IPv4 (Internet Protocol version 4) protocols:

SMB (Network Neighborhood)

SNMP

Up to 3 user-defined ports

All other IPv4 traffic (see Figure 141)

Uplink Broadcast

ARP (Address Resolution Protocol)

All others (see Figure 141) BootP Client BootP Server All Other IPv4 SNMP User Defined Port 1 IPv4 Multicast User Defined Port 3 User Defined Port 2 SMB PPPoE ARP All Others Figure 141: Categorical protocol filtering Issue2,November2007 Draft5forRegulatoryReview 383 Release8 OperationsGuide The following are example situations in which you can configure protocol filtering where NAT is disabled:

If you block a subscriber from only PPoE and SNMP, then the subscriber retains access to all other protocols and all ports. If you block PPoE, IPv4, and Uplink Broadcast, and you also check the All others selection, then only Address Resolution Protocol is not filtered. The ports that are filtered as a result of protocol selections in the Protocol Filtering tab of the SM are listed in Table 54. Further information is provided under Protocol Filtering Tab of the SM on Page 292. Table 54: Ports filtered per protocol selections Protocol Selected SMB SNMP Port Filtered (Blocked) Destination Ports 137 TCP and UDP, 138 UDP, 139 TCP, 445 TCP Destination Ports 161 TCP and UDP, 162 TCP and UDP Bootp Client Source Port 68 UDP Bootp Server Source Port 67 UDP 22.6 ENCRYPTINGDOWNLINKBROADCASTS An AP can be enabled to encrypt downlink broadcast packets such as the following:

ARP

NetBIOS

broadcast packets containing video data on UDP. The encryption used is DES for a DES module, and AES for an AES module. Before the Encrypt Downlink Broadcast feature is enabled on the AP, air link security should be enabled on the AP. 22.7 ISOLATINGSMs In the Release 8 or later AP, you can prevent SMs in the sector from directly communicating with each other. In CMMmicro Release 2.2 or later, you can prevent connected APs from directly communicating with each other, which prevents SMs that are in different sectors of a cluster from communicating with each other. In the AP, the SM Isolation parameter is available in the General tab of the Configuration web page. In the drop-down menu for that parameter, you can configure the SM Isolation feature by any of the following selections:

Disable SM Isolation (the default selection). This allows full communication between SMs. Block SM Packets from being forwarded. This prevents both multicast/broadcast and unicast SM-to-SM communication. Issue2,November2007 Draft5forRegulatoryReview 384 Release8 OperationsGuide Block and Forward SM Packets to Backbone. This not only prevents multicast/broadcast and unicast SM-to-SM communication but also sends the packets, which otherwise would have been handled SM to SM, through the Ethernet port of the AP. In the CMMmicro, SM isolation treatment is the result of how you choose to manage the port-based VLAN feature of the embedded switch, where you can switch all traffic from any AP or BH to an uplink port that you specify. However, this is not packet level switching. It is not based on VLAN IDs. See the VLAN Port Configuration parameter in Figure 72: Configuration page of CMMmicro, example on Page 225. 22.8 FILTERINGMANAGEMENTTHROUGHETHERNET You can configure the SM to disallow any device that is connected to its Ethernet port from accessing the IP address of the SM. If you set the Ethernet Access Control parameter to Enabled, then no attempt to access the SM management interface (by http, SNMP, telnet, ftp, or tftp) through Ethernet can succeed. any attempt to access the SM management interface over the air (by IP address, presuming that LAN1 Network Interface Configuration, Network Accessibility is set to Public, or by link from the Session Status or Remote Subscribers tab in the AP) is unaffected. 22.9 ALLOWINGMANAGEMENTFROMONLYSPECIFIEDIP ADDRESSES The Security tab of the Configuration web page in the AP, SM, and BH includes the IP Access Control parameter. You can specify one, two, or three IP addresses that should be allowed to access the management interface (by http, SNMP, telnet, ftp, or tftp). If you select IP Access Filtering Disabled, then management access is allowed from any IP address, even if the Allowed Source IP 1 to 3 parameters are populated. IP Access Filtering Enabled, and specify at least one address in the Allowed Source IP 1 to 3 parameter, then management access is limited to the specified address(es). If you intend to use Prizm to manage the element, then you must ensure that the IP address of the Prizm server is listed here. 22.10 CONFIGURINGMANAGEMENTIPBYDHCP The IP tab in the Configuration web page of every Cyclone radio contains a LAN1 Network Interface Configuration, DHCP State parameter that, if enabled, causes the IP configuration (IP address, subnet mask, and gateway IP address) to be obtained through DHCP instead of the values of those individual parameters. The setting of this DHCP state parameter is also viewable, but not settable, in the Network Interface tab of the Home page. In the SM, this parameter is settable in the NAT tab of the Configuration web page, but only if NAT is enabled. in the IP tab of the Configuration web page, but only if the Network Accessibility parameter in the IP tab is set to Public. Issue2,November2007 Draft5forRegulatoryReview 385 Release8 23 MANAGINGBANDWIDTHAND OperationsGuide AUTHENTICATION This section provides a high-level description of bandwidth and authentication management in a Cyclone network. For more specific information, see Cyclone Bandwidth and Authentication Manager (BAM) User Guide or the Last Mile Gear Cyclone Prizm User Guide. 23.1 MANAGINGBANDWIDTHWITHOUTBAM Unless Prizm or BAM is deployed and is configured in the AP, bandwidth management is limited to applying a single sustained data rate value (for uplink and for downlink) and a single burst allocation value (for uplink and for downlink) to every SM that registers in the AP. 23.2 BANDWIDTHANDAUTHENTICATIONMANAGER(BAM) SERVICESANDFEATURES Prizm or BAM enables you to perform the following management operations on SMs:

List all ESNs that are associated with a specified VLAN ID.

Change the key that the SMs need for authenticating.

Temporarily suspend or reinstate a subscriber.

Set burst size and data transfer rate caps for an SM or group of SMs.

Use licensing to uncap an SM or group of SMs.

Associate or dissociate an SM or group of SMs with a specified VLAN ID.

Set VLAN parameters.

Toggle whether to send those VLAN parameters to the SMs.

Set CIR parameters for low-priority and high-priority channel rates.

Toggle whether to send those CIR parameters to the SMs.

Toggle whether to enable the high-priority channel in the SMs. 23.2.1 BandwidthManagerCapability Prizm or BAM allows you to set bandwidth per SM for sustained rates and burst rates. With this capability, the Cyclone system allows both

burst rates beyond those of many other broadband access solutions. control of average bandwidth allocation to prevent excessive bandwidth usage by a subscriber. All packet throttling occurs in the SMs and APs based on Quality of Service (QoS) data that the Prizm or BAM server provides. No server processing power or network messages are needed for packet throttling. QoS management also supports marketing of broadband connections at various data rates, for operator-defined groups of subscribers, and at various price points. This allows you to meet customer needs at a price that the customer deems reasonable and affordable. Issue2,November2007 Draft5forRegulatoryReview 387 Release8 OperationsGuide When BAM is enabled in the AP Configuration page, bandwidth management is expanded to apply uniquely specified sustained data rate and burst allocation values to each registered SM. Thus, you can define differently priced tiers of subscriber service. Designing Tiered Subscriber Service Levels Examples of levels of service that vary by bandwidth capability are provided in Table 55 and Table 56. NOTE:

The speeds that these tables correlate to service levels are comparative examples. Actual download times may be greater due to use of the bandwidth by other SMs, congestion on the local network, congestion on the Internet, capacity of the serving computer, or other network limitations. Table 55: Example times to download for typical tiers of service with Cyclone AP AP SM Operation Max burst speed t n e m p u q E i Service Type Sustained Downlink Data Rate Sustained Uplink Data Rate Downlink and Uplink Burst Allocations Web page 5 MB 20 MB 50 MB 300 MB s g n i t t e S e p m a x E l

) c e s

(

d a o n w o D l Cyclone Cyclone 1X 4.4 Mbps Premium Regular 5250 Kbps 1750 Kbps 500000 Kb 1000 Kbps 500 Kbps 80000 Kb

<1 9 36 91 545

<1 9 80 320 2320 Basic 256 Kbps 128 Kbps 40000 Kb

<1 9 470 1400 9220 Issue2,November2007 Draft5forRegulatoryReview 388 Release8 OperationsGuide Table 56: Example times to download for typical tiers of service with Advantage AP i t n e m p u q E AP SM Operation Max burst speed Service Type Sustained Downlink Data Rate Sustained Uplink Data Rate Downlink and Uplink Burst Allocations Web page s g n i t t e S e p m a x E l

) c e s

(

d a o n w o D l 5 MB 20 MB 50 MB 300 MB Advantage Cyclone 1X 5 Mbps Premium Regular 5250 Kbps 1750 Kbps 1000 Kbps 500 Kbps Basic 256 Kbps 128 Kbps 2X 10 Mbps Premium Regular 5250 Kbps 1750 Kbps 1000 Kbps 500 Kbps Basic 256 Kbps 128 Kbps Advantage Advantage 2X 10 Mbps Premium 2000 Kbps 20000 Kbps 500000 Kb 80000 Kb 40000 Kb 500000 Kb 80000 Kb 40000 Kb 500000 Kb

<1 8 32 80 480

<1 8 80 320 2320

<1 8 470 1400 9220

<1 4 16 40 362

<1 4 80 320 2320

<1 4 470 1400 9220

<1 4 16 40 240 23.2.2 AuthenticationManagerCapability Prizm or BAM allows you to set per AP a requirement that each SM registering to the AP must authenticate. When AP Authentication Server (APAS) is enabled in the AP, any SM that attempts to register to the AP is denied service if authentication fails, such as (but not limited to) when no Prizm or BAM server is operating or when the SM is not listed in the database. If a Prizm or BAM server drops out of service where no redundant server exists

an SM that attempts to register is denied service. an SM that is already in session remains in session In a typical Cyclone network, some SMs re-register daily (when subscribers power down the SMs, for example), and others do not re-register in a period of several weeks. Whenever an authentication attempt fails, the SM locks out of any other attempt to register itself to the same AP for the next 15 minutes. Issue2,November2007 Draft5forRegulatoryReview 389 Release8 24 MANAGINGTHENETWORKFROMA OperationsGuide MANAGEMENTSTATION(NMS) SNMPv2 (Simple Network Management Protocol Version 2) can be used to manage and monitor the Cyclone modules under SMI (Structure of Management Information) specifications. SMI specifies management information definitions in ASN.1 (Abstract Syntax Notation One) language. SNMPv2 supports both 32-bit and 64-bit counters. The SMI for SNMPv2 is defined in RFC 1902 at http://www.faqs.org/rfcs/rfc1902.html. 24.1 ROLESOFHARDWAREANDSOFTWAREELEMENTS 24.1.1 RoleoftheAgent In SNMP, software on each managed device acts as the agent. The agent collects and stores management information in ASN.1 format, in a structure that a MIB (management information base) defines. The agent responds to commands to

send information about the managed device.

modify specific data on the managed device. 24.1.2 RoleoftheManagedDevice In SNMP, the managed device is the network element that operates on the agent software. In the Cyclone network, this managed device is the module (AP, SM, or BH). With the agent software, the managed device has the role of server in the context of network management. 24.1.3 RoleoftheNMS In SNMP, the NMS (network management station) has the role of client. An application

(manager software) operates on the NMS to manage and monitor the modules in the network through interface with the agents. 24.1.4 DualRolesfortheNMS The NMS can simultaneously act as an agent. In such an implementation, the NMS acts as

client to the agents in the modules, when polling for the agents for information and sending modification data to the agents. server to another NMS, when being polled for information gathered from the agents and receiving modification data to send to the agents. 24.1.5 SimpleNetworkManagementProtocol(SNMP)Commands To manage a module, SNMPv2 supports the set command, which instructs the agent to change the data that manages the module. Issue2,November2007 Draft5forRegulatoryReview 391 Release8 OperationsGuide To monitor a network element (Cyclone module), SNMPv2 supports

the get command, which instructs the agent to send information about the module to the manager in the NMS. traversal operations, which the manager uses to identify supported objects and to format information about those objects into relational tables. In a typical Cyclone network, the manager issues these commands to the agents of more than one module (to all SMs in the operator network, for example). 24.1.6 TrapsfromtheAgent When a specified event occurs in the module, the agent initiates a trap, for which the agent sends an unsolicited asynchronous message to the manager. 24.1.7 APSNMPProxytoSMs When the AP receives from Prizm or an NMS an SNMP request for an SM, it is capable of sending that request via proxy to the SM. In this case, the SM responds directly to Prizm or the NMS. (The AP performs no processing on the response.) 24.2 MANAGEMENTINFORMATIONBASE(MIB) The MIB, the SNMP-defined data structure, is a tree of standard branches that lead to optional, non-standard positions in the data hierarchy. The MIB contains both

objects that SNMP is allowed to control (bandwidth allocation or access, for example) objects that SNMP is allowed to monitor (packet transfer, bit rate, and error data, for example). The path to each object in the MIB is unique to the object. The endpoint of the path is the object identifier. 24.2.1 CascadingPathtotheMIB The standard MIB hierarchy includes the following cascading branch structures:

the top (standard body) level:

ccitt (0) iso (1)

iso-ccitt (2) under iso (1) above:

standard (0)

member-body (2)

under identified-organization (3) above:

dod (6)

other branches identified-organization (3) registration-authority (1) Issue2,November2007 Draft5forRegulatoryReview 392 Release8 OperationsGuide

internet (1) under dod (6) above:

other branches under internet (1) above:

mgmt (2)

private (4)

other branches under mgmt (2) above: mib-2 (1) and other branches. (See MIB-II below.) under private (4) above: enterprise (1) and other branches. (See Cyclone Enterprise MIB below.) Beneath this level are non-standard branches that the enterprise may define. Thus, the path to an object that is managed under MIB-II begins with the decimal string 1.3.6.1.2.1 and ends with the object identifier and instance(s), and the path to an object that is managed under the Cyclone Enterprise MIB begins with 1.3.6.1.4.1, and ends with the object identifier and instance(s). 24.2.2 ObjectInstances An object in the MIB can have either only a single instance or multiple instances, as follows:

a scalar object has only a single instance. A reference to this instance is designated by .0, following the object identifier. a tabular object has multiple instances that are related to each other. Tables in the MIB associate these instances. References to these instances typically are designated by .1, .2, and so forth, following the object identifier. 24.2.3 ManagementInformationBaseSystemsandInterface(MIBII) The standard MIB-II (Management Information Base systems and interface) objects are programmed into the Cyclone modules. To read this MIB, see Management Information Base for Network Management of TCP/IP-based Internets: MIB II, RFC 1213 at http://www.faqs.org/rfcs/rfc1213.html. The MIB-II standard categorizes each object as one of the types defined in Table 57. Objects in category system interfaces ip icmp Table 57: Categories of MIB-II objects Control or identify the status of system operations in the module. the network interfaces for which the module is configured. Internet Protocol information in the module. Internet Control Message Protocol information in the module.

(These messages flag IP problems and allow IP links to be tested.) Issue2,November2007 Draft5forRegulatoryReview 393 Release8 OperationsGuide Objects in category Control or identify the status of tcp udp Transport Control Protocol information in the module (to control and ensure the flow of data on the Internet). User Datagram Protocol information in the module (for checksum and address). 24.2.4 CycloneEnterpriseMIB The Cyclone Enterprise MIB provides additional reporting and control, extending the objects for any NMS that uses SNMP interaction. This MIB comprises five text files that are formatted in standard ASN.1 (Abstract Syntax Notation One) language. To use this MIB, perform the following steps. Procedure 39: Installing the Cyclone Enterprise MIB files 1. On the NMS, immediately beneath the root directory, create directory mibviewer. Immediately beneath the mibviewer directory, create directory Cyclonemibs. 2. 3. Download the following three standard MIB files from the Internet Engineering Task Force at http://www.simpleweb.org/ietf/mibs into the mibviewer/Cyclonemibs directory on the NMS:

SNMPv2-SMI.txt, which defines the Structure of Management Information specifications.

SNMPv2-CONF.txt, which allows macros to be defined for object group, notification group, module compliance, and agent capabilities.

SNMPv2-TC.txt, which defines general textual conventions. 4. Move the following five files from your Cyclone software package directory into the mibviewer/Cyclonemibs directory on the NMS (if necessary, first download the software package from http://www.Last Mile Gear.com/Cyclone):

whisp-tcv2-mib.txt (Textual Conventions MIB), which defines Cyclone system-specific textual conventions

WHISP-GLOBAL-REG-MIB.txt (Registrations MIB), which defines registrations for global items such as product identities and product components.

WHISP-BOX-MIBV2-MIB.txt (Box MIB), which defines module-level (AP,

WHISP-APS-MIB.txt (APs MIB), which defines objects that are specific to

WHISP-SM-MIB.txt (SM MIB), which defines objects that are specific to

CMM3-MIB.txt (CMM3 MIB), which defines objects that are specific to the SM, and BH) objects. the AP or BH timing master. the SM or BH timing slave. CMMmicro. Issue2,November2007 Draft5forRegulatoryReview 394 Release8 OperationsGuide IMPORTANT!

Do not edit these MIB files in ASN.1. These files are intended for manipulation by only the NMS. However, you can view these files through a commercially available MIB viewer. Such viewers are listed under MIB Viewers on Page 411. 5. Download a selected MIB viewer into directory mibviewer. 6. As instructed by the user documentation that supports your NMS, import the eight MIB files that are listed above. end of procedure 24.3 CONFIGURINGMODULESFORSNMPACCESS Cyclone modules provide the following Configuration web page parameters in the SNMP tab. These govern SNMP access from the manager to the agent:

Community String, which specifies the password for security between managers and the agent.

Accessing Subnet, which specifies the subnet mask that allows managers to poll the agents. Cyclone modules can also be configured to send traps to specified IP addresses, which can be those of Prizm or NMS servers, for example. The parameter for this address is named Trap Address. 24.4 OBJECTSDEFINEDINTHECYCLONEENTERPRISEMIB The Cyclone Enterprise MIB defines separate sets of objects for all radio modules

APs and BH timing masters

SMs and BH timing slaves

CMMmicros NOTE:

The PTP 400 and PTP 600 series bridges (previously known as 30/60 Mbps and 150/300 Mbps Backhauls) do not support these objects. The MIBs that they support are listed under Objects Defined in the PTP 400 and PTP 600 series Bridges MIB on Page 408. Issue2,November2007 Draft5forRegulatoryReview 395 Release8 24.4.1 AP,SM,andBHObjects OperationsGuide The objects that the Cyclone Enterprise MIB defines for all APs, SMs, and BHs are listed in Table 58. Table 58: Cyclone Enterprise MIB objects for APs, SMs, and BHs AP, SM, BH Object Name addVlanMember agingTimeout allowVIDAccess antennaGain1 bridgeEnable clearEventLog codePointn2 commString deleteUser dynamicLearning eirp3 extFilterDelay fecEnable lanDhcpState managementVID mngtIP powerControl reboot removeVlanMember scheduling sessionTimeout setDefaultPlug subnetMask taggedFrame4 transmitterOP trapIPn5 twoXRate userAccessLevel userName userPassword Value Syntax Integer Integer Integer Integer Integer Integer Integer DisplayString DisplayString Integer Integer Integer Integer Integer Integer IpAddress Integer Integer Integer Integer Integer Integer Integer Integer Integer IpAddress Integer Integer DisplayString DisplayString Operation Allowed manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage Issue2,November2007 Draft5forRegulatoryReview 396 Release8 OperationsGuide AP, SM, BH Object Name vlanMemberSource accessLevel boxDeviceType boxDeviceTypeID boxEncryption boxFrequency boxTemperature6 dhcpLanIP dhcpLanGateway dhcpLanSubnetMask dhcpRfPublicIP dhcpRfPublicGateway dhcpRfPublicSubnetMask etherLinkStatus inSyncCount lanDhcpStatus outSyncCount platformType platformVer pllOutLockCount rfPublicDhcpStatus txCalFailure userLoginName userPswd whispBoxBoot whispBoxEsn whispBoxEvntLog whispBoxFPGAVer whispBridgeAge whispBridgeDesLuid whispBridgeExt whispBridgeHash whispBridgeMacAddr whispBridgeTbErr Value Syntax Integer Integer DisplayString DisplayString DisplayString DisplayString DisplayString IpAddress IpAddress IpAddress IpAddress IpAddress IpAddress DisplayString Integer DisplayString Integer Integer Integer Integer DisplayString Integer DisplayString DisplayString DisplayString WhispMACAddress EventString DisplayString Integer WhispLUID Integer Integer MacAddress Integer Operation Allowed manage monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor Issue2,November2007 Draft5forRegulatoryReview 397 Release8 OperationsGuide AP, SM, BH Object Name whispBridgeTbFree whispBridgeTbUsed whispVAge whispVID whispVType Value Syntax Integer Integer Integer Integer DisplayString Operation Allowed monitor monitor monitor monitor monitor NOTES:

1. For only 5.7-GHz radios. 2. Where n is any number, 0 through 63. codePoint0, codePoint48, and codePoint56 can be only monitored. 3. Deprecated. 4. Replaced by frameType. 5. Where n is any number, 1 through 10. 6. The value of this object does not accurately reflect the temperature inside the module for comparison with the operating range. However, it can be helpful as one of many troubleshooting indicators. Although modules no longer report the Temperature field in the GUI, the agent in the modules continues to support this object. 24.4.2 APandBHTimingMasterObjects The objects that the Cyclone Enterprise MIB defines for each AP and BH Timing Master are listed in Table 59. The traps provided in this set of objects are listed under Traps Provided in the Cyclone Enterprise MIB on Page 410. Table 59: Cyclone Enterprise MIB objects for APs and BH timing masters AP, BHM Object Name allowedIPAccess1 allowedIPAccess2 allowedIPAccess3 apBeaconInfo apTwoXRate asIP1 asIP2 asIP3 authKey authMode configSource dAcksReservHigh Value Syntax Operation Allowed manage manage manage manage manage manage manage manage manage manage manage manage IpAddress IpAddress IpAddress Integer Integer IpAddress IpAddress IpAddress DisplayString Integer Integer Integer Issue2,November2007 Draft5forRegulatoryReview 398 Release8 OperationsGuide AP, BHM Object Name defaultGw dfsConfig dwnLnkData dwnLnkDataRate dwnLnkLimit encryptDwBroadcast encryptionMode gpsInput gpsTrap highPriorityUpLnkPct ipAccessFilterEnable lanIp lanMask limitFreqBand900 linkTestAction1 linkTestDuration linkTestLUID maxRange ntpServerIP numCtlSlots numCtlSlotsHW numCtlSlotsReserveHigh numDAckSlots numUAckSlots privateIp regTrap rfFreqCarrier sectorID sesHiDownCIR sesHiUpCIR sesLoDownCIR sesHiDownCIR smIsolation tslBridging Value Syntax Operation Allowed manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage IpAddress Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer IpAddress IpAddress Integer Integer Integer Integer Integer IpAddress Integer Integer Integer Integer Integer IpAddress Integer Integer Integer Integer Integer Integer Integer Integer Integer Issue2,November2007 Draft5forRegulatoryReview 399 Release8 OperationsGuide AP, BHM Object Name txSpreading uAcksReservHigh untranslatedArp updateAppAddress upLnkDataRate upLnkLimit vlanEnable actDwnFragCount actDwnLinkIndex actUpFragCount adaptRate avgPowerLevel dataSlotDwn dataSlotUp dataSlotUpHi dfsStatus downLinkEff downLinkRate dwnLnkAckSlot dwnLnkAckSlotHi expDwnFragCount expUpFragCount fpgaVersion gpsStatus lastPowerLevel linkAirDelay linkAveJitter linkDescr linkESN linkInDiscards linkInError linkInNUcastPkts linkInOctets linkInUcastPkts Value Syntax Operation Allowed manage Integer manage Integer manage Integer manage IpAddress manage Integer manage Integer manage Integer monitor Gauge32 monitor Integer monitor Gauge32 monitor DisplayString monitor DisplayString monitor Integer monitor Integer monitor Integer monitor DisplayString monitor Integer monitor Integer monitor Integer monitor Integer monitor Gauge32 monitor Gauge32 DisplayString monitor DisplayString monitor monitor DisplayString monitor Integer Integer monitor monitor DisplayString monitor PhysAddress Counter32 monitor monitor Counter32 monitor Counter32 Counter32 monitor monitor Counter32 Issue2,November2007 Draft5forRegulatoryReview 400 Release8 OperationsGuide AP, BHM Object Name linkInUnknownProtos linkLastJitter linkLastRSSI linkLUID linkMtu linkOutDiscards linkOutError linkOutNUcastPkts linkOutOctets linkOutQLen linkOutUcastPkts linkRegCount linkReRegCount linkRSSI linkSessState linkSiteName linkSpeed linkTestError linkTestStatus linkTimeOut maxDwnLinkIndex numCtrSlot numCtrSlotHi PhysAddress radioSlicing radioTxGain regCount sesDownlinkLimit sesDownlinkRate sesUplinkLimit sesUplinkRate sessionCount softwareBootVersion softwareVersion Value Syntax Operation Allowed monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor Counter32 Integer Integer Integer Integer Counter32 Counter32 Counter32 Counter32 Gauge32 Counter32 Integer Integer Integer Integer DisplayString Gauge32 DisplayString DisplayString Integer Integer Integer Integer PhysAddress Integer Integer Integer Integer Integer Integer Integer Integer DisplayString DisplayString Issue2,November2007 Draft5forRegulatoryReview 401 Release8 OperationsGuide AP, BHM Object Name testDuration testLUID upLinkEff upLinkRate upLnkAckSlot upLnkAckSlotHi whispGPSStats Value Syntax Operation Allowed monitor monitor monitor monitor monitor monitor monitor Integer Integer Integer Integer Integer Integer Integer NOTES:

1. You can set to 1 to initiate a link test, but not 0 to stop. The value 0 is only an indication of the idle link test state. 24.4.3 SMandBHTimingSlaveObjects The objects that the Cyclone Enterprise MIB defines for each SM and BH Timing Slave are listed in Table 60. Table 60: Cyclone Enterprise MIB objects for SMs and BH timing slaves SM, BHS Object Name allOtherIPFilter allOthersFilter allowedIPAccess1 allowedIPAccess2 allowedIPAccess3 alternateDNSIP arpCacheTimeout arpFilter authKey authKeyOption bootpcFilter bootpsFilter defaultGw dhcpClientEnable dhcpIPStart dhcpNumIPsToLease dhcpServerEnable dhcpServerLeaseTime Value Syntax Integer Integer IpAddress IpAddress IpAddress IpAddress Integer Integer DisplayString Integer Integer Integer IpAddress Integer IpAddress Integer Integer Integer Operation Allowed manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage Issue2,November2007 Draft5forRegulatoryReview 402 Release8 OperationsGuide SM, BHS Object Name Value Syntax dmzEnable dmzIP dnsAutomatic enable8023link ethAccessFilterEnable hiPriorityChannel hiPriorityDownlinkCIR hiPriorityUplinkCIR ingressVID ip4MultFilter ipAccessFilterEnable lanIp lanMask localIP lowPriorityDownlinkCIR lowPriorityUplinkCIR naptEnable naptPrivateIP naptPrivateSubnetMask naptPublicGatewayIP naptPublicIP naptPublicSubnetMask naptRFPublicGateway naptRFPublicIP naptRFPublicSubnetMask networkAccess port port1TCPFilter port2TCPFilter port3TCPFilter port1UDPFilter port2UDPFilter port3UDPFilter powerUpMode Integer IpAddress Integer Integer Integer Integer Integer Integer Integer Integer Integer IpAddress IpAddress IpAddress Integer Integer Integer IpAddress IpAddress IpAddress IpAddress IpAddress IpAddress IpAddress IpAddress Integer Integer Integer Integer Integer Integer Integer Integer Integer Operation Allowed manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage Issue2,November2007 Draft5forRegulatoryReview 403 Release8 OperationsGuide SM, BHS Object Name pppoeFilter prefferedDNSIP protocol radioDbmInt rfDhcpState rfScanList smbFilter snmpFilter tcpGarbageCollectTmout timingPulseGated twoXRate udpGarbageCollectTmout uplinkBCastFilter userDefinedPort1 userDefinedPort2 userDefinedPort3 userP1Filter userP2Filter userP3Filter adaptRate airDelay calibrationStatus dhcpcdns1 dhcpcdns2 dhcpcdns3 dhcpCip dhcpClientLease dhcpCSMask dhcpDfltRterIP dhcpDomName dhcpServerTable dhcpSip hostIp hostLease Value Syntax Integer IpAddress Integer Integer Integer DisplayString Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer DisplayString Integer DisplayString IpAddress IpAddress IpAddress IpAddress TimeTicks IpAddress IpAddress DisplayString DhcpServerEntry IpAddress IpAddress TimeTicks Operation Allowed manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor Issue2,November2007 Draft5forRegulatoryReview 404 Release8 OperationsGuide SM, BHS Object Name Value Syntax hostMacAddress jitter radioDbm radioSlicing radioTxGain registeredToAp rssi sessionStatus PhysAddress Integer DisplayString Integer Integer DisplayString Integer DisplayString Operation Allowed monitor monitor monitor monitor monitor monitor monitor monitor 24.4.4 CMMmicroObjects The objects that the Cyclone Enterprise MIB defines for each CMMmicro are listed in Table 61. Table 61: Cyclone Enterprise MIB objects for CMMmicros CMMmicro Object Name clearEventLog defaultGateWay displayOnlyAccess fullAccess gpsTimingPulse lan1Ip lan1SubnetMask port1Config port1Description port1PowerCtr port2Config port2Description port2PowerCtr port3Config port3Description port3PowerCtr port4Config port4Description port4PowerCtr Value Syntax Operation Allowed manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage Integer IpAddress DisplayString DisplayString Integer IpAddress IpAddress Integer DisplayString Integer Integer DisplayString Integer Integer DisplayString Integer Integer DisplayString Integer Issue2,November2007 Draft5forRegulatoryReview 405 Release8 OperationsGuide CMMmicro Object Name port5Config port5Description port5PowerCtr port6Config port6Description port6PowerCtr port7Config port7Description port7PowerCtr port8Config port8Description port8PowerCtr reboot webAutoUpdate deviceType displayOnlyStatus duplexStatus eventLog fullAccessStatus gpsAntennaConnection gpsDate gpsHeight gpsInvalidMsg gpsLatitude gpsLongitude gpsReceiverInfo gpsRestartCount gpsSatellitesTracked gpsSatellitesVisible gpsTime gpsTrackingMode height latitude linkSpeed Value Syntax Operation Allowed manage manage manage manage manage manage manage manage manage manage manage manage manage manage monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor Integer DisplayString Integer Integer DisplayString Integer Integer DisplayString Integer Integer DisplayString Integer Integer Integer DisplayString DisplayString Integer EventString DisplayString DisplayString DisplayString DisplayString DisplayString DisplayString DisplayString DisplayString Integer DisplayString DisplayString DisplayString DisplayString DisplayString DisplayString Integer Issue2,November2007 Draft5forRegulatoryReview 406 Release8 OperationsGuide CMMmicro Object Name linkStatus longitude macAddress pkts1024to1522Octets pkts128to255Octets pkts256to511Octets pkts512to1023Octets pkts64Octets pkts65to127Octets pldVersion portIndex portNumber powerStatus rxAlignmentErrors rxBroadcastPkts rxDropPkts rxExcessSizeDisc rxFCSErrors rxFragments rxGoodOctets rxJabbers rxMulticastPkts rxOctets rxOversizePkts rxPausePkts rxSAChanges rxSymbolErrors rxUndersizePkts rxUnicastPkts satellitesTracked satellitesVisible softwareVersion syncStatus systemTime Value Syntax Operation Allowed monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor Integer DisplayString DisplayString Counter32 Counter32 Counter32 Counter32 Counter32 Counter32 DisplayString Integer Integer Integer Counter32 Counter32 Counter32 Counter32 Counter32 Counter32 Counter64 Counter32 Counter32 Counter64 Counter32 Counter32 Counter32 Counter32 Counter32 Counter32 DisplayString DisplayString DisplayString DisplayString DisplayString Issue2,November2007 Draft5forRegulatoryReview 407 Release8 OperationsGuide CMMmicro Object Name trackingMode txBroadcastPkts txCollisions txDeferredTransmit txDropPkts txExcessiveCollision txFrameInDisc txLateCollision txMulticastPkts txMultipleCollision txOctets txPausePkts txSingleCollision txUnicastPkts upTime Value Syntax Operation Allowed monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor DisplayString Counter32 Counter32 Counter32 Counter32 Counter32 Counter32 Counter32 Counter32 Counter32 Counter64 Counter32 Counter32 Counter32 DisplayString 24.5 OBJECTSDEFINEDINTHEPTP400ANDPTP600SERIESBRIDGES MIB The objects that the PTP 400 and PTP 600 series bridges MIB defines are listed in Table 63. Table 62: PTP 400 and PTP 600 series bridge MIB objects Object Name Value Syntax iPAddress subnetMask gatewayIPAddress targetMACAddress1 masterSlaveMode maximumTransmitPower receivePower2 vectorError2 transmitPower2 range linkLoss2 IpAddress IpAddress IpAddress DisplayString Integer Integer Integer Integer Integer Integer Integer Operation Allowed manage manage manage manage manage manage manage manage manage manage manage Issue2,November2007 Draft5forRegulatoryReview 408 Release8 OperationsGuide Object Name Value Syntax receiveChannel transmitChannel receiveModulationMode transmitModulationMode receiveSnr2 systemReset softwareVersion hardwareVersion Integer Integer Integer Integer Integer Integer DisplayString DisplayString NOTES:

1. Of the other BH in the link. 2. max, mean, min, last during the past hour. Operation Allowed manage manage manage manage manage monitor monitor monitor 24.6 OBJECTSSUPPORTEDINTHECYCLONE30/60MbpsBH The 30/60-Mbps BH supports the following MIBs:

MIB II, RFC 1213, System Group MIB II, RFC 1213, Interfaces Group WiMAX 802.16 WMAN-IF-MIB Bridge MIB, RFC 1493, dot1dBaseGroup Bridge MIB, RFC 1493, dot1dBasePortTableGroup 30/60-Mbps Backhaul Cyclone proprietary MIB 24.7 OBJECTSSUPPORTEDINTHECYCLONE150/300MbpsBH The 150/300-Mbps BH supports the following MIBs:

MIB II, RFC 1213, System Group MIB II, RFC 1213, Interfaces Group WiMAX 802.16 WMAN-IF-MIB Bridge MIB, RFC 1493, dot1dBaseGroup Bridge MIB, RFC 1493, dot1dBasePortTableGroup High-capacity counter MIB, RFC 2233 150/300-Mbps Backhaul Cyclone proprietary MIB 24.8 INTERFACEDESIGNATIONSINSNMP SNMP identifies the ports of the module as follows:

Interface 1 represents the Ethernet interface of the module. To monitor the status of Interface 1 is to monitor the traffic on the Ethernet interface. Issue2,November2007 Draft5forRegulatoryReview 409 Release8 OperationsGuide

Interface 2 represents the RF interface of the module. To monitor the status of Interface 2 is to monitor the traffic on the RF interface. These interfaces can be viewed on the NMS through definitions that are provided in the standard MIB files. 24.9 TRAPSPROVIDEDINTHECYCLONEENTERPRISEMIB Cyclone modules provide the following SNMP traps for automatic notifications to the NMS:

whispGPSInSync, which signals a transition from not synchronized to synchronized.

whispGPSOutSync, which signals a transition from synchronized to not synchronized.

whispRegComplete, which signals registration completed.

whispRegLost, which signals registration lost.

whispRadarDetected, which signals that the one-minute scan has been completed, radar has been detected, and the radio will shutdown.

whispRadarEnd, which signals that the one-minute scan has been completed, radar has not been detected, and the radio will resume normal operation. The PTP 400 and PTP 600 series bridges do not support the traps listed above. NOTE:

24.10 TRAPSPROVIDEDINTHEPTP400SERIESBRIDGEMIB PTP 400 series bridges (previously known as 30/60-Mbps Backhauls) provide the following SNMP traps for automatic notifications to the NMS:

coldStart linkUp linkDown dfsChannelChange, which signals that the channel has changed. dfsImpulsiveInterferenceDetected, which signals that impulsive interference has been detected. 24.11 TRAPSPROVIDEDINTHEPTP600SERIESBRIDGEMIB PTP 600 series bridges (previously known as 150/300-Mbps Backhauls) provide the following SNMP traps for automatic notifications to the NMS:

coldStart linkUp linkDown Issue2,November2007 Draft5forRegulatoryReview 410 Release8 OperationsGuide

dfsChannelChange, which signals that the channel has changed. dfsImpulsiveInterferenceDetected, which signals that impulsive interference has been detected. 24.12 MIBVIEWERS Any of several commercially available MIB viewers can facilitate management of these objects through SNMP. Some are available as open source software. The Cyclone division does not endorse, support, or discourage the use of any these viewers. To assist end users in this area, Cyclone offers a starter guide for one of these viewers MRTG (Multi Router Traffic Grapher). This starter guide is titled Cyclone Network Management with MRTG: Application Note, and is available in the Document Library section under Support at http://www.Last Mile Gear.com/Cyclone. MRTG software is available at http://mrtg.hdl.com/mrtg.html. Other MIB viewers are available and/or described at the following web sites:

http://ns3.ndgsoftware.com/Products/NetBoy30/mibbrowser.html http://www.adventnet.com/products/snmputilities/

http://www.dart.com/samples/mib.asp http://www.edge-technologies.com/webFiles/products/nvision/index.cfm http://www.ipswitch.com/products/whatsup/monitoring.html http://www.koshna.com/products/KMB/index.asp http://www.mg-soft.si/mgMibBrowserPE.html http://www.mibexplorer.com http://www.netmechanica.com/mibbrowser.html http://www.networkview.com http://www.newfreeware.com/search.php3?q=MIB+browser http://www.nudesignteam.com/walker.html http://www.oidview.com/oidview.html http://www.solarwinds.net/Tools http://www.stargus.com/solutions/xray.html http://www.totilities.com/Products/MibSurfer/MibSurfer.htm Issue2,November2007 Draft5forRegulatoryReview 411 Release8 25 USINGTHECYCLONENETWORKUPDATERTOOL OperationsGuide

(CNUT) The Cyclone Network Updater Tool manages and automates the software and firmware upgrade process for Cyclone radio and CMMmicro modules across the network. This eliminates the need for an administrator to visit each radio in the network (or each AP while using the Autoupdate feature) to upgrade the modules. 25.1 CNUTFUNCTIONS The Cyclone Network Updater Tool

automatically discovers all Cyclone network elements executes a UDP command that initiates and terminates the Autoupdate mode within APs. This command is both secure and convenient:

For security, the AP accepts this command from only the IP address that you specify in the Configuration page of the AP.

For convenience, Network Updater automatically sets this Configuration parameter in the APs to the IP address of the Network Updater server when the server performs any of the update commands. allows you to choose among updating

your entire network.

only elements that you select.

only network branches that you select. provides a Script Engine that you can use with any script that

you define.

Cyclone supplies. 25.2 NETWORKELEMENTGROUPS With the Cyclone Network Updater Tool, you can identify element groups composed of network elements that you select. Identifying these element groups

organizes the display of elements (for example, by region or by AP cluster). allows you to

perform an operation on all elements in the group simultaneously.

set group-level defaults for telnet or ftp password access and SNMP Community String (defaults that can be overridden in an individual element when necessary). 25.3 NETWORKLAYERS A typical Cyclone network contains multiple layers of elements, each layer lying farther from the Point of Presence. For example, SMs are behind an AP and thus, in this context, at a lower layer than the AP. Correctly portraying these layers in Network Updater is essential so that Network Updater can perform radio and AP cluster upgrades in an appropriate order. Issue2,November2007 Draft5forRegulatoryReview 413 Release8 OperationsGuide IMPORTANT!

Correct layer information ensures that Network Updater does not command an AP that is behind another AP/SM pair (such as in a remote AP installation) to perform an upgrade at the same time as the SM that is feeding the AP. If this occurs, then the remote AP loses network connection during the upgrade (when the SM in front of the AP completes its upgrade and reboots). 25.4 SCRIPTENGINE Script Engine is the capability in Network Updater that executes any user-defined script against any network element or element group. This capability is useful for network management, especially for scripts that you repetitively execute across your network. The Autodiscovery capability in Network Updater finds all of your Cyclone network elements. This comprehensive discovery

ensures that, when you intend to execute a script against all elements, the script is indeed executed against all elements.

maintains master lists of elements (element groups) against which you selectively execute scripts. The following scripts are included with CNUT:

AP Data Import from BAM

AP Data Export to BAM

Set Autoupdate Address on APs

Set SNMP Accessibility

Reset Unit 25.5 SOFTWAREDEPENDENCIESFORCNUT CNUT functionality requires

one of the following operating systems

Windows 2000

Windows XP

Red Hat Linux 9

Red Hat Enterprise Linux Version 3 Java Runtime Version 1.4.2 or later

Perl 5.8.0 or ActivePerl 5.8.3 software or later 25.6 CNUTDOWNLOAD CNUT can be downloaded together with each Cyclone system release that supports CNUT. Software for these Cyclone system releases is packaged on the Cyclone Support web page as either

a .zip file for use without the CNUT application. a .pkg file that the CNUT application can open. Issue2,November2007 Draft5forRegulatoryReview 414 Release8 26 USINGINFORMATIONALTABSINTHEGUI OperationsGuide 26.1 VIEWINGGENERALSTATUS(ALL) See General Status Tab of the AP on Page 202. General Status Tab of the SM on Page 198. General Status Tab of the BHM on Page 214. Beginning the Test of Point-to-Point Links on Page 211. 26.2 VIEWINGSESSIONSTATUS(AP,BHM) The Session Status tab in the Home page provides information about each SM that has registered to the AP. This information is useful for managing and troubleshooting a Cyclone system. This tab also includes the current active values on each SM for MIR, CIR, and VLAN, as well as the source of these values, representing the SM itself, BAM, or the AP and cap. An example of the Session Status tab is displayed in Figure 142. Figure 142: Session Status tab data, example Issue2,November2007 Draft5forRegulatoryReview 415 Release8 OperationsGuide An additional example and explanations of the fields on this tab are provided in Session Status Tab of the AP on Page 193. 26.3 VIEWINGREMOTESUBSCRIBERS(AP,BHM) See Remote Subscribers Tab of the AP on Page 197. Continuing the Test of Point-to-Point Links on Page 213. 26.4 INTERPRETINGMESSAGESINTHEEVENTLOG(ALL) Each line in the Event Log of a module Home page begins with a time and date stamp. However, some of these lines wrap as a combined result of window width, browser preferences, and line length. You may find this tab easiest to use if you widen the window until all lines are shown as beginning with the time and date stamp. 26.4.1 TimeandDateStamp The time and date stamp reflect either

GPS time and date directly or indirectly received from the CMM.

the running time and date that you have set in the Time & Date web page. NOTE:

In the Time & Date web page, if you have left any time field or date field unset and clicked the Set Time and Date button, then the time and date default to 00:00:00 UT : 01/01/00. A reboot causes the preset time to pause or, in some cases, to run in reverse. Additionally, a power cycle resets the running time and date to the default 00:00:00 UT : 01/01/00. Thus, whenever either a reboot or a power cycle has occurred, you should reset the time and date in the Time & Date web page of any module that is not set to receive sync. 26.4.2 EventLogDataCollection The collection of event data continues through reboots and power cycles. When the buffer allowance for event log data is reached, the system adds new data into the log and discards an identical amount of the oldest data. Each line that contains the expression WatchDog flags an event that was both

considered by the system software to have been an exception recorded in the preceding line. Conversely, a Fatal Error() message flags an event that is recorded in the next line. Some exceptions and fatal errors may be significant and require either operator action or technical support. Issue2,November2007 Draft5forRegulatoryReview 416 Release8 OperationsGuide An example portion of Event Log data is displayed in Figure 143. In this figure (unlike in the Event Log web page)

lines are alternately highlighted to show the varying length of wrapped lines. the types of event messages (which follow the time and date stamps and the file and line references) are underscored as quoted in Table 63 and Table 64. Issue2,November2007 Draft5forRegulatoryReview 417 Release8 OperationsGuide Figure 143: Event Log tab data, example Issue2,November2007 Draft5forRegulatoryReview 418 Release8 26.4.3 MessagesthatFlagAbnormalEvents OperationsGuide The messages listed in Table 63 flag abnormal events and, case by case, may signal the need for corrective action or technical support. See Troubleshooting on Page 469. Table 63: Event Log messages for abnormal events Event Message Expected LUID = 6 Actual LUID = 7 FatalError() Loss of GPS Sync Pulse Machine Check Exception RcvFrmNum = 0x00066d ExpFrmNum = 0x000799 Meaning Something is interfering with the control messaging of the module. Also ensure that you are using shielded cables to minimize interference. Consider trying different frequency options to eliminate or reduce interference. The event recorded on the line immediately beneath this message triggered the Fatal Error(). Module has lost GPS sync signal. This is a symptom of a possible hardware failure. If this is a recurring message, begin the RMA process for the module. Something is interfering with the control messaging of the module. Also ensure that you are using shielded cables to minimize interference. Consider trying different frequency options to eliminate or reduce interference. System Reset Exception -- External Hard Reset The unit lost power or was power cycled. System Reset Exception -- External Hard Reset WatchDog The event recorded on the preceding line triggered this WatchDog message. 26.4.4 MessagesthatFlagNormalEvents The messages listed in Table 64 record normal events and typically do not signal a need for any corrective action or technical support. Table 64: Event Log messages for normal events Event Message Acquired GPS Sync Pulse. FPGA Features FPGA Version GPS Date/Time Set PowerOn reset from Telnet command line Reboot from Webpage Software Boot Version Software Version System Log Cleared Meaning Module has acquired GPS sync signal. Type of encryption. FPGA (JBC) version in the module. Module is now on GPS time. Reset command was issued from a telnet session. Module was rebooted from management interface. Boot version in the module. Cyclone release version and authentication method for the unit. Event log was manually cleared. Issue2,November2007 Draft5forRegulatoryReview 419 Release8 26.5 VIEWINGTHENETWORKINTERFACETAB(ALL) OperationsGuide Figure 144: Network Interface tab of AP, example Figure 145: Network Interface tab of SM, example In any module, the LAN1 Network Interface section of this tab displays the defined Internet Protocol scheme for the Ethernet interface to the module. In slave devices, this tab also provides an RF Public Network Interface section, which displays the Internet Protocol scheme defined for network access through the master device (AP or BHM). Issue2,November2007 Draft5forRegulatoryReview 420 Release8 26.6 INTERPRETINGRADIOSTATISTICSINTHESCHEDULERTAB OperationsGuide

(ALL) Figure 146: Scheduler tab of SM, example Statistics for the Scheduler are displayed as shown in Figure 146. Issue2,November2007 Draft5forRegulatoryReview 421 Release8 26.7 VIEWINGTHELISTOFREGISTRATIONFAILURES(AP,BHM) OperationsGuide An example of the SM Registration Failures tab is displayed in Figure 147. Figure 147: SM Registration Failures tab of AP, example The SM Registration Failures tab identifies SMs (or BHSs) that have recently attempted and failed to register to this AP (or BHM). With its time stamps, these instances may suggest that a new or transient source of interference exists. Issue2,November2007 Draft5forRegulatoryReview 422 Release8 26.8 INTERPRETINGDATAINTHEBRIDGINGTABLE(ALL) OperationsGuide An example of the Bridging Table tab is displayed in Figure 148. Figure 148: Bridging Table tab of AP, example If NAT (network address translation) is not active on the SM, then the Bridging Table tab provides the MAC address of all devices that are attached to registered SMs (identified by LUIDs). The bridging table allows data to be sent to the correct module as follows:

For the AP, the uplink is from RF to Ethernet. Thus, when a packet arrives in the RF interface to the AP, the AP reads the MAC address from the inbound packet and creates a bridging table entry of the source MAC address on the other end of the RF interface. For the SM, BHM, and BHS, the uplink is from Ethernet to RF. Thus, when a packet arrives in the Ethernet interface to one of these modules, the module reads the MAC address from the inbound packet and creates a bridging table entry of the source MAC address on the other end of the Ethernet interface. Issue2,November2007 Draft5forRegulatoryReview 423 Release8 26.9 TRANSLATIONTABLE(SM) OperationsGuide When Translation Bridging is enabled in the AP, each SM keeps a table mapping MAC addresses of devices attached to the AP to IP addresses, as otherwise the mapping of end-user MAC addresses to IP addresses is lost. (When Translation Bridging is enabled, an AP modifies all uplink traffic originating from registered SMs such that the source MAC address of every packet will be changed to that of the SM which bridged the packet in the uplink direction.) An example of the Translaton Table is displayed in Figure 149. Figure 149: Translation Table tab of SM, example 26.10 INTERPRETINGDATAINTHEETHERNETTAB(ALL) The Ethernet tab of the Statistics web page reports TCP throughput and error information for the Ethernet connection of the module. Issue2,November2007 Draft5forRegulatoryReview 424 Release8 OperationsGuide Figure 150: Ethernet tab of AP, example The Ethernet tab displays the following fields. inoctets Count This field displays how many octets were received on the interface, including those that deliver framing information. inucastpkts Count This field displays how many inbound subnetwork-unicast packets were delivered to a higher-layer protocol. Innucastpkts Count This field displays how many inbound non-unicast (subnetwork-broadcast or subnetwork-

multicast) packets were delivered to a higher-layer protocol. indiscards Count This field displays how many inbound packets were discarded without errors that would have prevented their delivery to a higher-layer protocol. (Some of these packets may have been discarded to increase buffer space.) inerrors Count This field displays how many inbound packets contained errors that prevented their delivery to a higher-layer protocol. Issue2,November2007 Draft5forRegulatoryReview 425 Release8 OperationsGuide inunknownprotos Count This field displays how many inbound packets were discarded because of an unknown or unsupported protocol. outoctets Count This field displays how many octets were transmitted out of the interface, including those that deliver framing information. outucastpkts Count This field displays how many packets for which the higher-level protocols requested transmission to a subnetwork-unicast address. The number includes those that were discarded or not sent. outnucastpkts Count This field displays how many packets for which the higher-level protocols requested transmission to a non-unicast (subnetwork-broadcast or subnetwork-multicast) address. The number includes those that were discarded or not sent. outdiscards Count This field displays how many outbound packets were discarded without errors that would have prevented their transmission. (Some of these packets may have been discarded to increase buffer space.) outerrrors Count This field displays how many outbound packets contained errors that prevented their transmission. RxBabErr This field displays how many receiver babble errors occurred. EthBusErr This field displays how many Ethernet bus errors occurred on the Ethernet controller. CRCError This field displays how many CRC errors occurred on the Ethernet controller. RxOverrun This field displays how many receiver overrun errors occurred on the Ethernet controller. Late Collision This field displays how many late collisions occurred on the Ethernet controller. A normal collision occurs during the first 512 bits of the frame transmission. A collision that occurs after the first 512 bits is considered a late collision. IMPORTANT!

A late collision is a serious network problem because the frame being transmitted is discarded. A late collision is most commonly caused by a mismatch between duplex configurations at the ends of a link segment. Issue2,November2007 Draft5forRegulatoryReview 426 Release8 OperationsGuide RetransLimitExp This field displays how many times the retransmit limit has expired. TxUnderrun This field displays how many transmission-underrun errors occurred on the Ethernet controller. CarSenseLost This field displays how many carrier sense lost errors occurred on the Ethernet controller. 26.11 INTERPRETINGRFCONTROLBLOCKSTATISTICSINTHERADIO TAB(ALL) Figure 151: Radio tab of Statistics page in SM, example The Radio tab of the Statistics page displays the following fields. inoctets Count This field displays how many octets were received on the interface, including those that deliver framing information. inucastpkts Count This field displays how many inbound subnetwork-unicast packets were delivered to a higher-layer protocol. Innucastpkts Count This field displays how many inbound non-unicast (subnetwork-broadcast or subnetwork-

multicast) packets were delivered to a higher-layer protocol. Issue2,November2007 Draft5forRegulatoryReview 427 Release8 OperationsGuide indiscards Count This field displays how many inbound packets were discarded without errors that would have prevented their delivery to a higher-layer protocol. (Some of these packets may have been discarded to increase buffer space.) inerrors Count This field displays how many inbound packets contained errors that prevented their delivery to a higher-layer protocol. inunknownprotos Count This field displays how many inbound packets were discarded because of an unknown or unsupported protocol. outoctets Count This field displays how many octets were transmitted out of the interface, including those that deliver framing information. outucastpkts Count This field displays how many packets for which the higher-level protocols requested transmission to a subnetwork-unicast address. The number includes those that were discarded or not sent. outnucastpkts Count This field displays how many packets for which the higher-level protocols requested transmission to a non-unicast (subnetwork-broadcast or subnetwork-multicast) address. The number includes those that were discarded or not sent. outdiscards Count This field displays how many outbound packets were discarded without errors that would have prevented their transmission. (Some of these packets may have been discarded to increase buffer space.) outerrrors Count This field displays how many outbound packets contained errors that prevented their transmission. 26.12 INTERPRETINGDATAINTHEVLANTAB(AP,SM) The VLAN tab in the Statistics web page provides a list of the most recent packets that were filtered because of VLAN membership violations. An example of the VLAN tab is shown in Figure 152. Issue2,November2007 Draft5forRegulatoryReview 428 Release8 OperationsGuide Figure 152: VLAN tab of AP, example Interpret entries under Most Recent Filtered Frames as follows:

UnknownThis should not occur. Contact Cyclone Technical Support. Only TaggedThe packet was filtered because the configuration is set to accept only packets that have an 802.1Q header, and this packet did not. IngressWhen the packet entered through the wired Ethernet interface, the packet was filtered because it indicated an incorrect VLAN membership. Local IngressWhen the packet was received from the local TCP/IP stack, the packet was filtered because it indicated an incorrect VLAN membership. This should not occur. Contact Cyclone Technical Support. EgressWhen the packet attempted to leave through the wired Ethernet interface, the packet was filtered because it indicated an incorrect VLAN membership. Local EgressWhen the packet attempted to reach the local TCP/IP stack, the packet was filtered because it indicated an incorrect VLAN membership. Issue2,November2007 Draft5forRegulatoryReview 429 Release8 26.13 DATAVC(ALL) OperationsGuide Figure 153: Data VC tab of SM, example The Data VC tab page displays the following fields. VC This field displays the virtual channel number. Low priority channels start at VC18 and count up. High priority channels start at VC255 and count down. If one VC is displayed, the high-priority channel is disabled. If two are displayed, the high-priority channel is enabled CoS This field displays the Class of Service for the virtual channel. The low priority channel is a CoS of 00, and the high priority channel is a CoS of 01. CoS of 02 through 07 are not currently used. Queue Overflow Cnt This is a count of packets that were discarded because the queue for the VC was already full. inoctets Cnt This field displays how many octets were received on the interface, including those that deliver framing information. inucastpkts Cnt This field displays how many inbound subnetwork-unicast packets were delivered to a higher-layer protocol. Issue2,November2007 Draft5forRegulatoryReview 430 Release8 OperationsGuide Innucastpkts Cnt This field displays how many inbound non-unicast (subnetwork-broadcast or subnetwork-

multicast) packets were delivered to a higher-layer protocol. indiscards Cnt This field displays how many inbound packets were discarded without errors that would have prevented their delivery to a higher-layer protocol. (Some of these packets may have been discarded to increase buffer space.) inerrors Cnt This field displays how many inbound packets contained errors that prevented their delivery to a higher-layer protocol. outoctets Cnt This field displays how many octets were transmitted out of the interface, including those that deliver framing information. outucastpkts Cnt This field displays how many packets for which the higher-level protocols requested transmission to a subnetwork-unicast address. The number includes those that were discarded or not sent. outnucastpkts Cnt This field displays how many packets for which the higher-level protocols requested transmission to a non-unicast (subnetwork-broadcast or subnetwork-multicast) address. The number includes those that were discarded or not sent. outdiscards Cnt This field displays how many outbound packets were discarded without errors that would have prevented their transmission. (Some of these packets may have been discarded to increase buffer space.) outerrrors Cnt This field displays how many outbound packets contained errors that prevented their transmission. 26.14 FILTER(SM) The Filter tab displays statistics on packets that have been filtered (dropped) due to the filters set on the SMs Protocol Filtering tab. An example of the Filter tab is shown in Figure 154. Issue2,November2007 Draft5forRegulatoryReview 431 Release8 OperationsGuide Figure 154: Filter tab on SM, example 26.15 NATSTATS(SM) When NAT is enabled on an SM, statistics are kept on the Public and Private (WAN and LAN) sides of the NAT, and displayed on the NAT Stats tab. An example of the NAT Stats tab is shown in Figure 155. Issue2,November2007 Draft5forRegulatoryReview 432 Release8 OperationsGuide Figure 155: Nat Stats tab on SM, example 26.15.1 NATDHCPStatistics(SM) When NAT is enable on an SM with DHCP client and/or Server, statistics are kept for packets transmitted, received, and tossed, as well as a table of lease information for the DHCP server (Assigned IP Address, Hardware Address, and Lease Remained/State). An example of the NAT DHCP Statistics tab is shown in Figure 156. Figure 156: NAT DHCP Statistics tab in SM, example Issue2,November2007 Draft5forRegulatoryReview 433 Release8 26.15.2 InterpretingDataintheGPSStatusPage(AP,BHM) OperationsGuide The GPS Status tab is only displayed when the Sync Input is set to Sync to Received Signal (Timing Port), which is the configuration desired when connecting an AP or BHM to a CMM2. See Sync Input on Page 239. The page displays information similar to that available on the web pages of a CMM3, including Pulse Status, GPS Time and Date, Satellites Tracked, Available Satellites, Height, Lattitude and Longitude. This page also displays the state of the antenna in the Antenna Connection field as

UnknownShown for early CMM2s.

OKShown for later CMM2s where no problem is detected in the signal.

OvercurrentIndicates a coax cable or connector problem.

UndercurrentIndicates a coax cable or connector problem. IMPORTANT!

If Unknown is displayed where a later CMM2 is deployed, then the connection is not working but the reason is unknown. This information may be helpful in a decision of whether to climb a tower to diagnose a perceived antenna problem. Issue2,November2007 Draft5forRegulatoryReview 434 Release8 27 USINGTOOLSINTHEGUI OperationsGuide 27.1 USINGTHESPECTRUMANALYZERTOOL(SM,BHS) See Monitoring the RF Environment on Page 369. 27.2 USINGTHEALIGNMENTTOOL(SM,BHS) An example of the Alignment tab in an SM or BHS is displayed in Figure 157. Figure 157: Alignment tab of BHS, example Proper alignment must achieve all of the following indications for an acceptable link between the modules:

RSSI typically at least 10 dBM above receiver sensitivity

jitter value between 0 and 4 uplink and downlink efficiency greater than 90%, except as described under Comparing Efficiency in 1X Operation to Efficiency in 2X Operation on Page 135. Issue2,November2007 Draft5forRegulatoryReview 435 Release8 OperationsGuide IMPORTANT!

If any of these values is not achieved, a link can be established but will manifest occasional problems. In the Alignment tab, you may set the following parameters. RSSI Only Mode In the RSSI Only Mode, the screen displays the signal strength based on the amount of energy in the selected frequency, regardless of whether the module has registered. This mode simplifies the aiming process for long links. To invoke the RSSI Only Mode, select Enabled. Radio Carrier Frequency If you enabled the RSSI Only Mode, select the frequency (in MHz) for the aiming operation. The Alignment tab also provides the following buttons. Enable A click of this button launches the slave device into alignment mode. Each further click refreshes the data in the tab to display the latest measurements collected. Disable A click of this button changes the slave device from alignment mode back to operating mode. The Alignment tab also provides the following read-only fields. Current Status This field indicates either SM is in Alignment Mode or SM is in Operating Mode. This syntax is used in an SM and in a BHS. RSSI This field displays the Radio Signal Strength Indicator units and, in parentheses, the current power level, of the signal received from the AP or BHM. Jitter This field displays the jitter level of the signal received from the AP or BHM. Number Registered Users This field displays how many slave devices are currently registered to the master device whose beacon is being received during the aiming period. In addition, the Alignment tab includes the following Detailed Beacon Information where it is available. Issue2,November2007 Draft5forRegulatoryReview 436 Release8 OperationsGuide Average measured RSSI This field displays the Radio Signal Strength Indicator units and, in parentheses, the power level as an average of the measurements that were collected throughout the aiming period. Try for the highest power level that you can achieve at the least amount of jitter. For example, if you achieve a power level of 75 dBm with a jitter level of 5, and further refine the alignment to achieve a power level of 78 dBm with a jitter level of 2 or 3, the link is better because of the further refinement. Average measured Jitter This field displays Jitter as an average of the measurements that were collected throughout the aiming period. In 1X operation, jitter values of 0 to 4 are acceptable. In 2X operation, jitter values 0 to 9 are acceptable. In either mode, 0 to 15 is the range of possible values that the Jitter field reports. Within the acceptable range, incremental improvements in the jitter level achieved can significantly improve link quality where power level is not significantly diminished by re-aiming. Users This is a count of the number of SMs registered to the AP you are aligning to. Frequency This field displays the frequency in MHz of the signal that was being received during the aiming period. ESN This field displays the MAC address of the AP or BHM you are aligning to. Color Code This field displays the color code of the AP or BHM you are aligning to. Backhaul This field displays a 1 if the device you are aligning to is a BHM, and a 0 if the device you are aligning to is an AP. Issue2,November2007 Draft5forRegulatoryReview 437 Release8 27.3 USINGTHELINKCAPACITYTESTTOOL(ALL) An example of the Link Capacity Test tab is displayed in Figure 158. OperationsGuide Figure 158: Link Capacity Test tab with 1522-byte packet length, example The Link Capacity Test page allows you to measure the throughput and efficiency of the RF link between two Cyclone modules. Many factors, including packet length, affect throughput. The Link Capacity Test tab contains the settable parameter Packet Length with a range of 64 to 1522 bytes. This allows you to compare throughput levels that result from various packet sizes. For example, the same link was measured in the same time frame at a packet length of 64 bytes. The results are shown in Figure 159. Issue2,November2007 Draft5forRegulatoryReview 438 Release8 OperationsGuide Figure 159: Link Capacity Test tab with 64-byte packet length, example To test a link, perform the following steps. Procedure 40: Performing a Link Capacity Test 1. Access the Link Capacity Test tab in the Tools web page of the module. 2. If you are running this test from an AP a. and you want to see Maximum Information Rate (MIR) data for the SM whose link you will be testing, then perform the following steps:

(1) For Link Test with MIR, select Enabled.

(2) Click the Save Changes button.

(3) Click the Reboot button. b. use the drop-down list to select the SM whose link you want to test. Issue2,November2007 Draft5forRegulatoryReview 439 Release8 OperationsGuide 3. Type into the Duration field how long (in seconds) the RF link should be tested. 4. Type into the Packet Length field the packet length at which you want the test conducted. 5. Type into the Number of Packets field either the number of packets (1 to 64) for the test. 0 to flood the link for as long as the test is in progress.

6. Click the Start Test button. 7. 8. Optionally In the Current Results Status block of this tab, view the results of the test. a. change the packet length. b. c. compare the results to those of other tests. repeat Steps 5 and 6. end of procedure The key fields in the test results are

Downlink RATE and Uplink RATE, expressed in bits per second

Downlink Efficiency and Uplink Efficiency, expressed as a percentage A Cyclone system link is acceptable only if the efficiencies of the link test are greater than 90% in both the uplink and downlink direction, except during 2X operation. See Using Link Efficiency to Check Received Signal Quality on Page 135. Whenever you install a new link, execute a link test to ensure that the efficiencies are within recommended guidelines. The AP downlink data percentage, slot settings, other traffic in the sector, and the quality of the RF environment all affect throughput. However, a Maximum Information Rate

(MIR) throttle or cap on the SM does not affect throughput. 27.4 USINGTHEAPEVALUATIONORBHMEVALUATIONTOOL

(SM,BHS) The AP Evaluation tab in the Tools web page of the SM provides information about the AP that the SM sees. Similarly, the BHM Evaluation tab of the BHS provides information about the BHM. An example of the AP Evaluation tab is shown in Figure 160. NOTE:

The data for this page can be suppressed by the SM Display of AP Evaluation Data selection in the Security tab of the Configuration page in the AP. Issue2,November2007 Draft5forRegulatoryReview 440 Release8 OperationsGuide Figure 160: AP Evaluation tab of SM, example The AP Evaluation tab provides the following fields that can be useful to manage and troubleshoot a Cyclone system:

Index This field displays the index value that the Cyclone system assigns (for only this page) to the AP where this SM is registered (or to the BHM to which this BHS is registered). Frequency This field displays the frequency that the AP or BHM transmits. ESN This field displays the MAC address (electronic serial number) of the AP or BHM. Issue2,November2007 Draft5forRegulatoryReview 441 Release8 OperationsGuide Jitter, RSSI, and Power Level The AP Evaluation tab shows the received Power Level in dBm and Jitter. Proper alignment maximizes Power Level and minimizes Jitter. As you refine alignment, you should favor lower jitter over higher dBm. For example, if coarse alignment gives an SM a power level of 75 dBm and a jitter measurement of 5, and further refining the alignment drops the power level to 78 dBm and the jitter to 2 or 3, use the refined alignment, with the following caveats:

When the receiving link is operating at 1X, the Jitter scale is 0 to 15 with desired jitter between 0 and 4. When the receiving link is operating at 2X, the Jitter scale is 0 to 15 with desired jitter between 0 and 9. For historical relevance, the AP Evaluation tab also shows the RSSI, the unitless measure of power. Use Power Level and ignore RSSI. RSSI implies more accuracy and precision than is inherent in its measurement. NOTE:

Unless the page is set to auto-refresh, the values displayed are from the instant the General Status tab was selected. To keep a current view of the values, refresh the browser screen or set to auto-refresh. Beacon Count A count of the beacons seen in a given time period. BRcvW DFS FEC Type Multipoint indicates an AP, not a BHM. Age Lockout This field displays how many times the SM or BHS has been temporarily locked out of making registration attempts. RegFail This field displays how many registration attempts by this SM or BHS failed. Range This field displays the distance in feet for this link. To derive the distance in meters, multiply the value of this parameter by 0.3048. Issue2,November2007 Draft5forRegulatoryReview 442 Release8 OperationsGuide TxBER A 1 in this field indicates the AP or BHM is sending Radio BER. EBcast A 1 in this field indicates the AP or BHM is encrypting broadcasst packets. A 0 indicates it is not. Session Count This field displays how many sessions the SM (or BHS) has had with the AP (or BHM). Typically, this is the sum of Reg Count and Re-Reg Count. However, the result of internal calculation may display here as a value that slightly differs from the sum. In the case of a multipoint link, if the number of sessions is significantly greater than the number for other SMs, then this may indicate a link problem or an interference problem. NoLUIDs OutOfRange AuthFail This field displays how many times authentication attempts from this SM have failed in the AP. EncryptFail This field displays how many times an encryption mismatch has occurred between the SM and the AP. Rescan Req FrameNumber Sector ID This field displays the value of the Sector ID field that is provisioned for the AP or BHM. Color Code This field displays the value of the Color Code field that is provisioned for the AP or BHM. BeaconVersion Sector User Count This field displays how many SMs are registered on the AP. Frequency This field displays the frequency of the received signal, expressed in MHz. NumULHalfSlots This is the number of uplink half slots in this AP or BHMs frame. To get slots, just divide by 2. Issue2,November2007 Draft5forRegulatoryReview 443 Release8 OperationsGuide NumDLHalfSlots This is the number of downlink half slots in this AP or BHMs frame. To get slots, just divide by 2. NumULContSlots This field displays how many control slots are being used in the uplink portion of the frame. The AP Evaluation tab also provides the following buttons. Rescan APs You can click this button to force the SM or BHS to rescan the frequencies that are selected in the Radio tab of the Configuration page. (See Custom Radio Frequency Scan Selection List on Page 276.) This module will then register to the AP or BHM that provides the best results for power level, jitter, andin an SMthe number of registered SMs. Update Display You can click this button to gather updated data without causing the SM or BHS to rescan and re-register. 27.5 USINGTHEFRAMECALCULATORTOOL(ALL) Cyclone avoids self-interference by syncing collocated APs (so they begin each transmission cycle at the same time) and requiring that collocated APs have the same transmit/receive ratio (so they stop transmitting and start receiving at the same time). This ensures that, at any instant, they are either all receiving or all transmitting. This avoids, for example, the problem of one AP attempting to receive from a distant SM, while a nearby AP is transmitting and overpowering the signal from the distant SM. Parameters that affect transmit/receive ratio include range, slots, downlink data percentage, and high priority uplink percentage. All collocated APs must have the same transmit/receive ratio. Additional engineering is needed for setting the parameters in a mixed cluster one with APs on hardware scheduler and APs on software scheduler. A frame calculator helps to do this. The operator inputs various AP settings into the calculator, and the calculator outputs many details on the frame including the Uplink Rcv SQ Start. This calculation should be done for each AP that has different settings. Then the operator varies the Downlink Data percentage in each calculation until the calculated Uplink Rcv SQ Start for all collocated APs is within 300 time bits. The frame calculator is accessed by clicking on Expanded Stats in the navigation column, then clicking on Frame Calculator (at the bottom of the expanded navigation column). The calculator does not use data on the module or populate new data. It is merely a convenience application running on the module. For this reason, you can use any module to do the calculations for any AP. Running the calculator on the AP in question is not necessary. IMPORTANT!

APs with slightly mismatched transmit/receive ratios and low levels of data traffic may see little effect on throughput. As the data traffic increases, the impact of mismatched transmit/receive ratios will increase. This means that a system that was not tuned for collocation may work fine at low traffic levels, but encounter Issue2,November2007 Draft5forRegulatoryReview 444 OperationsGuide problems at higher traffic level. The conservative practice is to tune for collocation from the beginning, and prevent future problems as sectors are built out and traffic increases. Release8 An example of the Frame Calculator tab is shown in Figure 161. Figure 161: Frame Calculator tab, example Issue2,November2007 Draft5forRegulatoryReview 445 Release8 OperationsGuide In the Frame Calculator tab, you may set the following parameters. Software Version Transmitter From the drop-down menu, select the Cyclone software release that runs on the AP(s). Software Version Receiver From the drop-down menu, select the Cyclone software release that runs on the SM(s). Transmit Sync Input If the APs in the cluster receive sync from a CMMmicro, select Sync to Received Signal (Power Port). receive sync from a CMM2, select Sync to Received Signal (Timing Port). are self timed, select Generate Sync Signal. Link Mode For AP to SM frame calculations, select Multipoint Link. Max Range Set to the same value as the Max Range parameter is set in the AP(s). Air Delay Leave this parameter set to the default value of 0 bits. Scheduling Initially select Software. Mobility Leave the default value of Off selected. Wireless/Wired Leave the default value of Wireless Link selected. Platform Type Transmitter Use the drop-down list to select the hardware series (board type) of the AP. Platform Type Receiver Use the drop-down list to select the hardware series (board type) of the SM. Frequency Band Use the drop-down list to select the radio frequency band of the AP and SM. External Bus Frequency Transmitter Leave this parameter set to the default value of 40. External Bus Frequency Receiver Leave this parameter set to the default value of 40. Issue2,November2007 Draft5forRegulatoryReview 446 Release8 OperationsGuide Downlink Data Initially set this parameter to the same value that the AP has for its Downlink Data parameter (percentage). Then, as you use the Frame Calculator tool in Procedure 41, you will vary the value in this parameter to find the proper value to write into the Downlink Data parameter of all APs in the cluster. High Priority Uplink Percentage If the AP is running Cyclone software earlier than Release 8, set this parameter to the current value of the High Priority Uplink Percentage parameter in the AP. Total Number UACK Slots If the AP is running Cyclone software earlier than Release 8, set this parameter to the current value of the Total NumUAckSlots parameter in the AP. Number High If the AP is running Cyclone software earlier than Release 8, set this parameter to the current value of the Num High parameter associated with Total NumUAckSlots in the AP. Number DACK Slots If the AP is running Cyclone software earlier than Release 8, set this parameter to the current value of the NumDAckSlots parameter in the AP. Number High If the AP is running Cyclone software earlier than Release 8, set this parameter to the current value of the Num High parameter associated with NumDAckSlots in the AP. Number Control Slots Set this parameter to the current value of the Control Slots (for Release 8) or NumCtlSlots (for earlier releases) parameter in the AP. In Release 8, the Control Slots parameter is present in the Radio tab of the Configuration web page. Number High If the AP is running Cyclone software earlier than Release 8, set this parameter to the current value of the Num High parameter associated with NumCtlSlots in the AP. To use the Frame Calculator, perform the following steps. Procedure 41: Using the Frame Calculator 1. Populate the Frame Calculator parameters with appropriate values as described above. 2. Click the Apply Settings button. 3. Click the Calculate button. 4. Scroll down the tab to the Calculated Frame Results section. NOTE: An example of the Calculated Frame Results section is displayed in Figure 162. Issue2,November2007 Draft5forRegulatoryReview 447 Release8 OperationsGuide Figure 162: Calculated Frame Results section of Frame Calculator tab, example 5. Record the value of the Uplink Rcv SQ Start field. 6. Scroll up to the Scheduling parameter. 7. Select Hardware. 8. Click the Apply Settings button. RESULT: The values in the Calculated Frame Results section are updated for hardware scheduling. In the Number Control Slots parameter, type in the number needed. 9. 10. Click the Apply Settings button. 11. Click the Calculate button. 12. Scroll down the tab to the Calculated Frame Results section. If Invalid Configuration is displayed, check and change values and settings, with special attention to the Platform Type parameters (P7, P8, and so on). 13. Record the value of the Uplink Rcv SQ Start field. 14. If the recorded values of the Uplink Rcv SQ Start field are within 150 time bits of each other, skip the next step. 15. Repeat this procedure, changing the value of the Downlink Data parameter until the values that this tool calculates for the Uplink Rcv SQ Start field are within 150 time bits of each other regardless of the selection in the Scheduling parameter. Issue2,November2007 Draft5forRegulatoryReview 448 Release8 OperationsGuide 16. When they are within 150 time bits, access the Radio tab in the Configuration web page of each AP in the cluster and change its Downlink Data parameter

(percentage) to the last value that you used in the Frame Calculator. See Figure 77: Radio tab of AP (900 MHz), example on Page 243. end of procedure 27.6 USINGTHESMCONFIGURATIONTOOL(AP,BHM) The SM Configuration tab in the Tools page of the AP or BHM displays the current values whose control may be subject to the setting in the Configuration Source parameter. an indicator of the source for each value. An example of the SM Configuration tab is displayed in Figure 163. Figure 163: SM Configuration tab of AP, example Issue2,November2007 Draft5forRegulatoryReview 449 Release8 OperationsGuide Indicators for configuration source are explained under Session Status Tab of the AP on Page 193. 27.7 USINGTHEBERRESULTSTOOL(SM,BHS) Radio BER is now supported on hardware scheduling. When looking at Radio BER data it is important to note that it represents bit errors at the RF link level. Due to CRC checks on fragments and packets and ARQ (Automatic Repeat reQuest), the BER of customer data is essentially zero. Radio BER gives one indication of link quality, along with received power level, jitter, and link tests. BER is only instrumented on the downlink, and can be read on each SMs Tools>BER Results page. Each time the tab is clicked, the current results are read, and counters are reset to zero. An example of the BER Results tab is displayed in Figure 164. Figure 164: BER Results tab of SM, example The BER Results tab can be helpful in troubleshooting poor link performance. The value in the Measured Total Bit Error Rate field represents the bit error rate (BER) in the RF link since the last time the BER Results tab was clicked. The link is acceptable if the value of this field is less than 104. If the BER is greater than 104, re-evaluate the installation of both modules in the link. The BER test signal is only broadcast by the AP (and compared to the expected test signal by the SM) when capacity in the sector allows it it is the lowest priority for AP transmissions. Issue2,November2007 Draft5forRegulatoryReview 450

 

 

Release8 28 MAINTAININGYOURCYCLONESOFTWARE OperationsGuide Cyclone provides release compatibility information and caveats about each release. 28.1 HISTORYOFSYSTEMSOFTWAREUPGRADES 28.1.1 CycloneRelease8Features Cyclone Release 8 introduces the following new features:

Links to SM GUI via Session Status and Remote Subscribers Tabs of AP Scheduling Limited to Hardware Scheduler Tiered Permissions and User Accounts GUI Customizable via CSS Dynamic Frequency Selection (DFS) v1.2.3 in All 5.4- and 5.7-GHz Modules Bit Error Rate (BER) Display with Hardware Scheduler AP SNMP Proxy to SMs Translation Bridging (MAC Address Mapping) SM Isolation Management Access Filtering for SM Source IP Management Access for AP and SM Optional DHCP Configuration of Management Interface 28.1.2 CycloneRelease8Fixes Cyclone Release 8 includes the following fixes:

Management Web (http) Access Lockup Fix Enforcement of Ethernet Link Speed Setting MIBs Support Only Applicable Objects 28.2 HISTORYOFCMMmicroSOFTWAREUPGRADES

Cyclone currently supports CMMmicro Releases up through Release 2.2. 28.3 TYPICALCONTENTSOFRELEASENOTES Cyclone supports each release with software release notes, which include

description of features that are introduced in the new release. issues that the new release resolves. known issues and special notes for the new release. installation procedures for the new release. Issue2,November2007 Draft5forRegulatoryReview 451 Release8 28.4 TYPICALUPGRADEPROCESS In a typical upgrade process, proceed as follows:

OperationsGuide 1. Visit the software page of the Cyclone web site. 2. Read the compatibility information and any caveats that Cyclone associates with the release. 3. Read the software release notes from the web site. 4. On the basis of these, decide whether the release is appropriate for your network. 5. Download the software release and associated files. 6. Use CNUT to manage the upgrade across your network. 28.4.1 DownloadingSoftwareandReleaseNotes All supported software releases, the associated software release notes document, and updated MIB files are available for download at any time from http://Last Mile Gear.Last Mile Gear.com/Cyclone/support/software/. This web site also typically provides a summary of the backward compatibility and any advantages or disadvantages of implementing the release. When you click on the release that you wish to download, you are prompted for information that identifies yourself and your organization (such as name, address, and e-mail address). When you complete and submit the form that prompts for this information, the download is made available to you. Issue2,November2007 Draft5forRegulatoryReview 452 Release8 29 REBRANDINGMODULEINTERFACESCREENS OperationsGuide Distinctive fonts indicate literal user input. variable user input. literal system responses. variable system responses. The interface screens on each module display the Cyclone or Cyclone Advantage logo. These logos can be replaced with other logos using Procedure 42. The logo is a hyperlink and clicking on it takes the user to the Cyclone web site. A different site (perhaps the operators support site) can be made the destination using Procedure 43. To return a module to regular logos and hyperlinks, use Procedure 44. The logo at the top of each page is a key indicator to the user whether a module is Cyclone or Cyclone Advantage. If you choose to replace the Cyclone logos, use two noticeably different logos so that users can continue to easily distinguish between a Cyclone module and a Cyclone Advantage module. To replace logos and hyperlinks efficiently throughout your network, read the following two procedures, write a script, and execute your script through the Cyclone Network Updater Tool (CNUT).7 To replace them individually, use one of the following two procedures. Procedure 42: Replacing the Cyclone logo on the GUI with another logo 1. If the current logo is the Cyclone logo, name your custom logo file on your computer Cyclone.jpg and put it in your home directory. If the current logo is the Cyclone Advantage logo, name your custom logo file on your computer advantaged.jpg and put it in your home directory. 2. Use an FTP (File Transfer Protocol) session to transfer this file to the module, as in the example session shown in Figure 165. 7 See Using the Cyclone Network Updater Tool (CNUT) on Page 181. Issue2,November2007 Draft5forRegulatoryReview 453 Release8 OperationsGuide

> ftp ModuleIPAddress Connected to ModuleIPAddress 220 FTP server ready Name (ModuleIPAddress:none): root 331 Guest login ok Password: <password-if-configured>

230 Guest login ok, access restrictions apply. ftp> binary 200 Type set to I ftp> put Cyclone.jpg put advantaged.jpg put top.html ftp> quit 221 Goodbye OR OR Figure 165: Example ftp session to transfer custom logo file 3. Use a telnet session and the addwebfile command to add the new file to the file system, as in the example session shown in Figure 166. NOTE:

Supported telnet commands execute the following results:

addwebfile adds a custom logo file to the file system.

clearwebfile clears the logo file from the file system.

lsweb lists the custom logo file and display the storage space available on the file system. Issue2,November2007 Draft5forRegulatoryReview 454 Release8 OperationsGuide

>telnet ModuleIPAddress

/---------\

C A N O P Y Last Mile Gear Broadband Wireless Technology Center

(Copyright 2001, 2002 Last Mile Gear Inc.) Login: root Password: <password-if-configured>

Telnet +> addwebfile Cyclone.jpg addwebfile advantaged.jpg addwebfile top.html Telnet +> lsweb Flash Web files

/Cyclone.jpg 7867 free directory entries: 31 free file space: 55331 Telnet +> exit OR OR Figure 166: Example telnet session to activate custom logo file end of procedure Procedure 43: Changing the URL of the logo hyperlink 1. In the editor of your choice, create a file named top.html, consisting of one line:

<a href="myurl">

where myurl is the desired URL, for example, http://www.Cyclonewireless.com. 2. Save and close the file as top.html. 3. Use an FTP (File Transfer Protocol) session to transfer this file to the module, as in the example session shown in Figure 165 on Page 454. 4. Use a telnet session and the addwebfile command to add the new file (top.html) to the file system, as in the example session shown in Figure 166. end of procedure If you ever want to restore the original logo and hyperlink in a module, perform the following steps. Procedure 44: Returning a module to its original logo and hyperlink 1. Use a telnet session and the clearwebfile command to clear all custom files from the file system of the module, as in the example session shown in Figure 167 Issue2,November2007 Draft5forRegulatoryReview 455 Release8 below. OperationsGuide

>telnet ModuleIPAddress

/---------\

C A N O P Y Last Mile Gear Broadband Wireless Technology Center

(Copyright 2001, 2002 Last Mile Gear Inc.) Login: root Password: <password-if-configured>

Telnet +> lsweb Flash Web files Cyclone.jpg 7867 free directory entries: 31 free file space: 56468 Telnet +> clearwebfile Telnet +> lsweb Flash Web files free directory entries: 32 free file space 64336 bytes Telnet +> exit Figure 167: Example telnet session to clear custom files end of procedure Issue2,November2007 Draft5forRegulatoryReview 456 Release8 30 TOGGLINGREMOTEACCESSCAPABILITY OperationsGuide Based on your priorities for additional security and ease of network administration, you can deny or permit remote access individually to any AP, SM, or BH. 30.1 DENYINGALLREMOTEACCESS Wherever the No Remote Access feature is enabled by the following procedure, physical access to the module is required for

any change in the configuration of the module. any software upgrade in the module. Where additional security is more important that ease of network administration, you can disable all remote access to a module as follows. Procedure 45: Denying all remote access Insert the override plug into the RJ-11 GPS utility port of the module. 1. 2. Power up or power cycle the module. 3. Access the web page http://169.254.1.1/lockconfig.html. 4. Click the check box. 5. Save the changes. 6. Reboot the module. 7. Remove the override plug. RESULT: No access to this module is possible through HTTP, SNMP, FTP, telnet, or over an RF link. end of procedure 30.2 REINSTATINGREMOTEACCESSCAPABILITY Where ease of network administration is more important than the additional security that the No Remote Access feature provides, this feature can be disabled as follows:

Procedure 46: Reinstating remote access capability Insert the override plug into the RJ-11 GPS utility port of the module. 1. 2. Power up or power cycle the module. 3. Access the web page http://169.254.1.1/lockconfig.html. 4. Click the check box to uncheck the field. 5. Save the changes. 6. Reboot the module. 7. Remove the override plug. RESULT: Access to this module is possible through HTTP, SNMP, FTP, telnet, or over an RF link. end of procedure Issue2,November2007 Draft5forRegulatoryReview 457 Release8 31 SETTINGUPAPROTOCOLANALYZERONYOUR OperationsGuide CYCLONENETWORK Selection of protocol analyzer software and location for a protocol analyzer depend on both the network topology and the type of traffic to capture. However, the examples in this section are based on free-of-charge Ethereal software, which is available at http://ethereal.com/. The equipment required to set up a protocol analyzer includes:

1 hub 1 laptop computer with protocol analyzer software installed 2 straight-through Ethernet cables 1 Cyclone power converter (ACPS110) 31.1 ANALYZINGTRAFFICATANSM The IP address of the protocol analyzer laptop computer must match the IP addressing scheme of the SM. If the SM has DHCP enabled, then configure the laptop computer to automatically obtain an address. If DHCP is not enabled, then ensure that the laptop computer is configured with a static IP address in the same subnet as the SM. The configuration for analyzing traffic at an SM is shown in Figure 168. SM To Radio Cable Power Supply To Computer Cable Subscriber PC HUB Sniffer Laptop Figure 168: Protocol analysis at SM Issue2,November2007 Draft5forRegulatoryReview 459 Release8 31.2 ANALYZINGTRAFFICATANAPORBHWITHNOCMM OperationsGuide The IP address of the protocol analyzer laptop computer must match the IP addressing scheme of the AP/BH. If the router is configured to be a DHCP server, then configure the laptop computer to automatically obtain an address. If DHCP is not enabled, then ensure that the laptop computer is configured with a static IP address in the same subnet as the AP/BH. The configuration for analyzing traffic at an AP or BH that is not connected to a CMM is shown in Figure 169. AP or BH To Radio Cable Power Supply To Computer Cable Router HUB Sniffer Laptop Figure 169: Protocol analysis at AP or BH not connected to a CMM 31.3 ANALYZINGTRAFFICATANAPORBHWITHACMM The IP address of the protocol analyzer laptop computer must match the IP addressing scheme of the AP/BH. If the router is configured to be a DHCP server, then configure the laptop computer to automatically obtain an address. If DHCP is not enabled, ensure that the laptop computer is configured with a static IP address in the same subnet as the AP/BH. Connect the hub to the J2 Ethernet to Switch of the port that is associated with the AP/BH. This example is of capturing traffic from AP/BH 111, which is connected to Port 1. The configuration for analyzing traffic at an AP or BH that is connected to a CMM is shown in Figure 170. Issue2,November2007 Draft5forRegulatoryReview 460 Release8 8 7 6 5 4 3 2 1 AP/BH 111 OperationsGuide CMM J1 to Radio J2 Ethernet to Switch Ethernet Switch 8 7 6 5 4 3 2 1 Sniffer Laptop HUB Router Figure 170: Protocol analysis at AP or BH connected to a CMM 31.4 EXAMPLEOFAPROTOCOLANALYZERSETUPFORANSM The following is an example of a network protocol analyzer setup using Ethereal software to capture traffic at the SM level. The Ethereal network protocol analyzer has changed its name to Wireshark, but functionality and use remains much the same. This example is based on the following assumptions:

All required physical cabling has been completed.

The hub, protocol analyzer laptop computer, and subscriber PC are successfully connected.

The SM is connected

as shown in Figure 169 on Page 460.

to the subscriber PC and the AP.

Ethereal software is operational on the laptop computer. Although these procedures involve the SM, the only difference in the procedure for analyzing traffic on an AP or BH is the hub insertion point. The IP Configuration screen of the example SM is shown in Figure 171. Issue2,November2007 Draft5forRegulatoryReview 461 Release8 OperationsGuide Figure 171: IP tab of SM with NAT disabled and local accessibility Procedure 47: Setting up a protocol analyzer 1. Note the IP configuration of the SM. 2. Browse to StartMy Network PlacesNetwork and Dialup Connections. 3. For Local Area Connection, select Properties. RESULT: The Local Area Connections Properties window opens, as shown in Figure 172. Issue2,November2007 Draft5forRegulatoryReview 462 Release8 OperationsGuide Figure 172: Local Area Connection Properties window 4. Select Internet Protocol (TCP/IP). 5. Click the Properties button. RESULT: The Internet Protocol (TCP/IP) Properties window opens, as shown in Figure 173. Figure 173: Internet Protocol (TCP/IP) Properties window Issue2,November2007 Draft5forRegulatoryReview 463 Release8 OperationsGuide 6. Unless you have a static IP address configured on the SM, select 7. Obtain an IP address automatically for the protocol analyzer laptop computer, as shown in Figure 173. If you have configured a static IP address on the SM, then a. select Use the following IP address. b. enter an IP address that is in the same subnet as the SM. 8. Click OK. 9. Open your web browser. 10. Enter the IP address of the SM. RESULT: The General Status tab of the SM opens, as shown in Figure 60 on Page 198. 11. If the General Status tab did not open, reconfigure how the laptop computer obtains an IP address. 12. Verify that you have connectivity from the laptop computer to the SM with the hub inserted. 13. Launch the protocol analyzer software on the laptop computer. 14. In the Capture menu, select Start. RESULT: The Ethereal Capture Options window opens, as shown in Figure 174. Figure 174: Ethereal Capture Options window Issue2,November2007 Draft5forRegulatoryReview 464 Release8 OperationsGuide 15. Ensure that the Interface field reflects the network interface card (NIC) that is used on the protocol analyzer laptop computer. NOTE: Although you can select filters based on specific types of traffic, all values are defaults in this example. 16. If you wish to select filters, select them now. 17. Click OK. RESULT: The Ethereal Capture window opens, as shown in Figure 175. Figure 175: Ethereal Capture window NOTE: This window graphically displays the types of packets (by percentage) that are being captured. 18. If all packet types are displayed with 0%, either

launch your Web browser on the subscriber PC for the IP address of the SM ping the SM from the home PC. 19. If still all packet types are displayed with 0% (meaning that no traffic is being captured), reconfigure IP addressing until you can successfully see traffic captured on the laptop computer. 20. Whenever the desired number of packets have been captured, click Stop. RESULT: When you stop the packet capture, the <capture> - Ethereal window opens, as shown in Figure 176. end of procedure Issue2,November2007 Draft5forRegulatoryReview 465 Release8 OperationsGuide Figure 176: <capture> - Ethereal window, Packet 1 selected This window has three panes:

The top pane provides a sequenced summary of the packets captured and includes SRC/DEST address and type of protocol. What you select in this pane determines the additional information that is displayed in the lower two panes.

The lower two panes facilitate drill-down into the packet that you selected in the top pane. In this example, Packet 1 (a broadcast ARP request) was selected in the top pane. The lower two panes provide further details about Packet 1. Another example is shown in Figure 177. Issue2,November2007 Draft5forRegulatoryReview 466 Release8 OperationsGuide Figure 177: <capture> - Ethereal window, Packet 14 selected In this second example, Packet 14 (protocol type HTTP) is selected in the top pane. The two lower panes provide further details about Packet 14. Issue2,November2007 Draft5forRegulatoryReview 467 Release8 32 TROUBLESHOOTING OperationsGuide 32.1 GENERALPLANNINGFORTROUBLESHOOTING Effective troubleshooting depends in part on measures that you take before you experience trouble in your network. Cyclone recommends the following measures for each site:

1. 2. Identify troubleshooting tools that are available at your site (such as a protocol analyzer). Identify commands and other sources that can capture baseline data for the site. These may include

ping

tracert or traceroute

Link Capacity Test results

throughput data

Configuration tab captures

Status tab captures

session logs 3. Start a log for the site. 4. Include the following information in the log:

operating procedures

site-specific configuration records

network topology

software releases, boot versions, and FPGA firmware versions

types of hardware deployed

site-specific troubleshooting processes

escalation procedures 5. Capture baseline data into the log from the sources listed in Step 2. 32.2 GENERALFAULTISOLATIONPROCESS Effective troubleshooting also requires an effective fault isolation methodology that includes

attempting to isolate the problem to the level of a system, subsystem, or link, such as

AP to SM

AP to CMM

AP to GPS

CMM to GPS

BHM to BHS

BHM to CMM

power Issue2,November2007 Draft5forRegulatoryReview 469 Release8 OperationsGuide

researching Event Logs of the involved equipment. (See Interpreting Messages in the Event Log on Page 416.) answering the questions listed in the following section. reversing the last previous corrective attempt before proceeding to the next. performing only one corrective attempt at a time. 32.3 QUESTIONSTOHELPISOLATETHEPROBLEM When a problem occurs, attempt to answer the following questions:

1. What is the history of the problem?

Have we changed something recently?

Have we seen other symptoms before this?

2. How wide-spread is the symptom?

Is the problem on only a single SM? (If so, focus on that SM.)

Is the problem on multiple SMs? If so

is the problem on one AP in the cluster? (If so, focus on that AP) is the problem on multiple, but not all, APs in the cluster? (If so, focus on those APs) is the problem on all APs in the cluster? (If so, focus on the CMM and the GPS signal.) 3. Based on data in the Event Log (described in Interpreting Messages in the Event Log on Page 416)

does the problem correlate to External Hard Resets with no WatchDog timers?

(If so, this indicates a loss of power. Correct your power problem.)

is intermittent connectivity indicated? (If so, verify your configuration, power level, jitter, cables and connections, and the speed duplex of both ends of the link).

does the problem correlate to loss-of-sync events?

4. Are connections made via shielded cables?

5. Does the GPS antenna have an unobstructed view of the entire horizon?

32.4 SECONDARYSTEPS After preliminary fault isolation through the above steps 1. check the Cyclone knowledge base (http://Last Mile Gear.Cyclonewireless.com/support/knowledge) to find whether other network operators have encountered a similar problem. 2. proceed to any appropriate set of diagnostic steps. These are organized as follows:

Module Has Lost or Does Not Establish Connectivity

NAT/DHCP-configured SM Has Lost or Does Not Establish Connectivity on Page 472

SM Does Not Register to an AP on Page 474

BHS Does Not Register to the BHM on Page 475

Module Has Lost or Does Not Gain Sync on Page 476 Issue2,November2007 Draft5forRegulatoryReview 470 Release8 OperationsGuide

Module Does Not Establish Ethernet Connectivity on Page 477

Module Does Not Power Up on Page 478

Power Supply Does Not Produce Power on Page 478

CMM2 Does Not Power Up on Page 479

CMM2 Does Not Pass Proper GPS Sync to Connected Modules on Page 479 32.5 PROCEDURESFORTROUBLESHOOTING 32.5.1 ModuleHasLostorDoesNotEstablishConnectivity To troubleshoot a loss of connectivity, perform the following steps. Procedure 48: Troubleshooting loss of connectivity 1. Isolate the end user/SM from peripheral equipment and variables such as routers, switches, and firewalls. 2. Set up the minimal amount of equipment. 3. On each end of the link a. check the cables and connections. b. verify that the cable/connection schemestraight-through or crossoveris correct. c. verify that the LED labeled LNK is green. d. access the General Status tab in the Home page of the module. e. verify that the SM is registered. f. verify that RSSI is 700 or higher. g. verify that jitter is reported as 9 or lower. h. access the IP tab in the Configuration page of the module. i. verify that IP addresses match and are in the same subnet. 4. On the SM end of the link an IP address through DHCP. a. verify that the PC that is connected to the SM is correctly configured to obtain b. execute ipconfig. c. verify that the PC has an assigned IP address. 5. On each end of the link a. access the General tab in the Configuration page of each module. b. verify that the setting for Link Speeds (or negotiation) matches that of the other module. c. access the Radio tab in the Configuration page of each module. d. verify that the Radio Frequency Carrier setting is checked in the Custom Radio Frequency Scan Selection List. e. verify that the Color Code setting matches that of the other module. f. access the browser LAN settings (for example, at ToolsInternet OptionsConnectionsLAN Settings in Internet Explorer). g. verify that none of the settings are selected. Issue2,November2007 Draft5forRegulatoryReview 471 Release8 OperationsGuide h. access the Link Capacity Test tab in the Tools page of the module. i. perform a link test. (See Procedure 40: Performing a Link Capacity Test on Page 439.) verify that the link test results show efficiency greater than 90% in both the uplink and downlink (except as described under Comparing Efficiency in 1X Operation to Efficiency in 2X Operation on Page 135). j. k. execute ping. l. m. verify that response times are not significantly greater than verify that no packet loss was experienced. 2.5 ms from BH to BH 4 ms from AP to SM 15 ms from SM to AP

replace any cables that you suspect may be causing the problem. n. 6. After connectivity has been re-established, reinstall network elements and variables that you removed in Step 1. end of procedure 32.5.2 NAT/DHCPconfiguredSMHasLostorDoesNotEstablishConnectivity Before troubleshooting this problem, identify the NAT/DHCP configuration from the following list:

NAT with DHCP Client and DHCP Server

NAT with DHCP Client

NAT with DHCP Server

NAT without DHCP To troubleshoot a loss of connectivity for an SM configured for NAT/DHCP, perform the following steps. Procedure 49: Troubleshooting loss of connectivity for NAT/DHCP-configured SM Isolate the end user/SM from peripheral equipment and variables such as routers, switches, and firewalls. 1. 2. Set up the minimal amount of equipment. 3. On each end of the link a. check the cables and connections. b. verify that the cable/connection schemestraight-through or crossoveris correct. c. verify that the LED labeled LNK is green. 4. At the SM a. access the NAT Table tab in the Logs web page. NOTE: An example of this tab is shown in Figure 178. Issue2,November2007 Draft5forRegulatoryReview 472 Release8 OperationsGuide Figure 178: NAT Table tab of SM, example b. verify that the correct NAT translations are listed. RESULT: NAT is eliminated as a possible cause if these translations are correct. 5. If this SM is configured for NAT with DHCP, then at the SM a. execute ipconfig. b. verify that the PC has an assigned IP address. c. if the PC does not have an assigned IP address, then enter ipconfig /release Adapter Name.

enter ipconfig /renew Adapter Name.

reboot the PC.

retreat to Step 5a. if the PC has an assigned IP address, then

d. access the NAT DHCP Statistics tab in the Statistics web page of the SM. NOTE: An example of this tab is shown in Figure 179. Issue2,November2007 Draft5forRegulatoryReview 473 Release8 OperationsGuide Figure 179: NAT DHCP Statistics tab of SM, example

verify that DHCP is operating as configured. 6. After connectivity has been re-established, reinstall network elements and variables that you removed in Step 1. end of procedure 32.5.3 SMDoesNotRegistertoanAP To troubleshoot an SM failing to register to an AP, perform the following steps. Procedure 50: Troubleshooting SM failing to register to an AP 1. Access the Radio tab in the Configuration page of the SM. 2. Note the Color Code of the SM. 3. Access the Radio tab in the Configuration page of the AP. 4. Verify that the Color Code of the AP matches that of the SM. 5. Note the Radio Frequency Carrier of the AP. 6. Verify that the value of the RF Frequency Carrier of the AP is selected in the Custom Radio Frequency Scan Selection List parameter in the SM. Issue2,November2007 Draft5forRegulatoryReview 474 Release8 OperationsGuide 7. In the AP, verify that the Max Range parameter is set to a distance slightly greater than the distance between the AP and the furthest SM that must register to this AP. 8. Verify that a clear line of sight exists between the AP and the SM, and that no obstruction significantly penetrates the Fresnel zone of the attempted link. If these conditions are not established, then verify that the AP and SM are 900-MHz modules in close proximity to each other. 9. Access the General Status tab in the Home page of each module. 10. In the Software Version field, verify that both the AP and SM are of the same encryption scheme (AES or DES). 11. Remove the bottom cover of the SM to expose the LEDs. 12. Power cycle the SM. RESULT: Approximately 25 seconds after the power cycle, the green LED labeled LNK should light to indicate that the link has been established. If the orange LED labeled SYN is lit instead, then the SM is in Alignment mode because the SM failed to establish the link. 13. In this latter case, and if the SM has encountered no customer-inflicted damage, then request an RMA for the SM. end of procedure 32.5.4 BHSDoesNotRegistertotheBHM To troubleshoot an BHS failing to register to the BHM, perform the following steps. Procedure 51: Troubleshooting BHS failing to register to a BHM 1. Access the Radio tab in the Configuration page of the BHS. 2. Note the Color Code of the BHS. 3. Access the Radio tab in the Configuration page of the BHM. 4. Verify that the Color Code of the BHM matches that of the BHS. 5. Note the Radio Frequency Carrier of the BHM. 6. Verify that the value of the RF Frequency Carrier of the BHM is selected in the Custom Radio Frequency Scan Selection List parameter on the Configuration page of the BHS. 7. Verify that a clear line of sight exists between the BHM and BHS, and that no obstruction significantly penetrates the Fresnel zone of the attempted link. 8. Access the General Status tab in the Home page of each module. 9. In the Software Version field, verify that both the BHM and BHS are of the same encryption scheme (AES or DES). 10. Also in the Software Version field, verify that both the BHM and BHS are of the same modulation rate from the factory (BH20 or BH10). 11. Remove the bottom cover of the BHS to expose the LEDs. Issue2,November2007 Draft5forRegulatoryReview 475 Release8 OperationsGuide 12. Power cycle the BHS. RESULT: Approximately 25 seconds after the power cycle, the green LED labeled LNK should light to indicate that the link has been established. If the orange LED labeled SYN is lit instead, then the BHS is in Alignment mode because the BHS failed to establish the link. In this latter case, and if the BHS has encountered no customer-inflicted damage, then request an RMA for the BHS. end of procedure 32.5.5 ModuleHasLostorDoesNotGainSync To troubleshoot a loss of sync, perform the following steps. Procedure 52: Troubleshooting loss of sync 1. Access the Event Log tab in the Home page of the SM. NOTE: An example of this tab is shown in Figure 180. Figure 180: Event Log tab of SM, example 2. Check for messages with the following format:

RcvFrmNum =

ExpFrmNum =

(See Table 63: Event Log messages for abnormal events on Page 419.) Issue2,November2007 Draft5forRegulatoryReview 476 Release8 3. 4. 5. 6. 7. 8. OperationsGuide If these messages are present, check the Event Log tab of another SM that is registered to the same AP for messages of the same type. If the Event Log of this second SM does not contain these messages, then the fault is isolated to the first SM. If the Event Log page of this second SM contains these messages, access the GPS Status page of the AP. If the Satellites Tracked field in the GPS Status page of the AP indicates fewer than 4 or the Pulse Status field does not indicate Generating Sync, check the GPS Status page of another AP in the same AP cluster for these indicators. If these indicators are present in the second AP a. verify that the GPS antenna still has an unobstructed view of the entire horizon. b. visually inspect the cable and connections between the GPS antenna and the CMM. if this cable is not shielded, replace the cable with shielded cable. c. If these indicators are not present in the second AP a. visually inspect the cable and connections between the CMM and the AP antenna. if this cable is not shielded, replace the cable with shielded cable. b. end of procedure 32.5.6 ModuleDoesNotEstablishEthernetConnectivity To troubleshoot a loss of Ethernet connectivity, perform the following steps. Procedure 53: Troubleshooting loss of Ethernet connectivity 1. Verify that the connector crimps on the Ethernet cable are not loose. 2. Verify that the Ethernet cable is not damaged. 3. If the Ethernet cable connects the module to a network interface card (NIC), verify that the cable is pinned out as a straight-through cable. If the Ethernet cable connects the module to a hub, switch, or router, verify that the cable is pinned out as a crossover cable. 4. 5. Verify that the Ethernet port to which the cable connects the module is set to auto-negotiate speed. 6. Power cycle the module. RESULT: Approximately 25 seconds after the power cycle, the green LED labeled LNK should light to indicate that the link has been established. If the orange LED labeled SYN is lit instead, then the module is in Alignment mode because the module failed to establish the link. In this latter case, and if the module has encountered no customer-inflicted damage, then request an RMA for the module. end of procedure 7. Issue2,November2007 Draft5forRegulatoryReview 477 Release8 32.5.7 ModuleDoesNotPowerUp OperationsGuide To troubleshoot the failure of a module to power up, perform the following steps. Procedure 54: Troubleshooting failure to power up 1. Verify that the connector crimps on the Ethernet cable are not loose. 2. Verify that the Ethernet cable is not damaged. 3. Verify that the cable is wired and pinned out according to the specifications provided under Wiring Connectors on Page 182. 4. Remove the cover of the module to expose the components on the printed wiring board. 5. Find the Ethernet transformer, which is labeled with either the name Halo or the name Pulse. 6. Verify that the Ethernet transformer does not show damage that would have been caused by improper cabling. (You can recognize damage as the top of the transformer being no longer smooth. The transformer in the following picture is damaged and is ineligible for an RMA.) 7. Connect the power supply to a known good Cyclone module via a known good Ethernet cable. 8. Attempt to power up the known good module and

if the known good module fails to power up, request an RMA for the power supply.

if the known good module powers up, return to the module that does not power up. 9. Reconnect the power supply to the failing module. 10. Connect the power supply to a power source. 11. Verify that the red LED labeled PWR lights. 12. If this LED does not light, and the module has not been powered up since the last previous FPGA firmware upgrade was performed on the module, then request an RMA for the module. end of procedure 32.5.8 PowerSupplyDoesNotProducePower To troubleshoot the failure of a power supply to produce power, perform the following steps. Procedure 55: Troubleshooting failure of power supply to produce power 1. Verify that the connector crimps on the Ethernet cable are not loose. 2. Verify that the Ethernet cable is not damaged. Issue2,November2007 Draft5forRegulatoryReview 478 Release8 OperationsGuide 3. Verify that the cable is wired and pinned out according to the specifications provided under Wiring Connectors on Page 182. 4. Connect the power supply to a known good Cyclone module via a known good Ethernet cable. 5. Attempt to power up the known good module. 6. If the known good module fails to power up, request an RMA for the power supply. end of procedure 32.5.9 CMM2DoesNotPowerUp To troubleshoot a malfunctioning CMM2, perform the following steps. Procedure 56: Troubleshooting CMM2 that malfunctions 1. Verify that the 115-/230-V switch (in the lower right-hand corner of the CMM2) is in the correct position for the power source. (See Figure 123 on Page 341.) Applying power when this switch is in the wrong position can damage the CMM2 and will render it ineligible for an RMA. 2. Verify that the electrical source to the CMM2 meets Cyclone specifications. See Table 18 on Page 72. 3. Verify that the electrical source is connected to the CMM2 at the proper connection point. (See Figure 125 on Page 344.) 4. Verify that the fuse is operational. 5. Verify that the fuse is properly seated in the receptacle. 6. Attempt to power up the CMM2. 7. If the power indicator on the interconnect board of the CMM2 fails to light when power is applied to the CMM2, request an RMA for the CMM2. end of procedure 32.5.10 CMM2DoesNotPassProperGPSSynctoConnectedModules If the Event Log tabs in all connected modules contain Loss of GPS Sync Pulse messages, perform the following steps. Procedure 57: Troubleshooting CMM2 not passing sync 1. Verify that the GPS antenna has an unobstructed view of the entire horizon. 2. Verify that the GPS coaxial cable meets specifications. 3. Verify that the GPS sync cable meets specifications for wiring and length. 4. If the web pages of connected modules indicate any of the following, then find and eliminate the source of noise that is being coupled into the GPS sync cable:

In the GPS Status page

anomalous number of Satellites Tracked (greater than 12, for example)

incorrect reported Latitude and/or Longitude of the antenna

In the Event Log page

garbled GPS messages

large number of Acquired GPS Sync Pulse messages Issue2,November2007 Draft5forRegulatoryReview 479 Release8 OperationsGuide 5. If these efforts fail to resolve the problem, then request an RMA for the CMM2. end of procedure 32.5.11 ModuleSoftwareCannotbeUpgraded If your attempt to upgrade the software of a module fails, perform the following steps. Procedure 58: Troubleshooting an unsuccessful software upgrade 1. Download the latest issue of the target release and the associated release notes. 2. Compare the files used in the failed attempt to the newly downloaded software. 3. Compare the procedure used in the failed attempt to the procedure in the newly 4. 5. downloaded release notes. If these comparisons reveal a difference, retry the upgrade, this time with the newer file or newer procedure. If, during attempts to upgrade the FPGA firmware, the following message is repeatable, then request an RMA for the module:

Error code 6, unrecognized device end of procedure 32.5.12 ModuleFunctionsProperly,ExceptWebInterfaceBecameInaccessible If a module continues to pass traffic, and the telnet and SNMP interfaces to the module continue to function, but the web interface to the module does not display, perform the following steps. Procedure 59: Restoring the web interface to a module 1. Enter telnet DottedIPAddress. RESULT: A telnet session to the module is invoked. 2. At the Login prompt, enter root. 3. At the Password prompt, enter PasswordIfConfigured. 4. At the Telnet +> prompt, enter reset. RESULT: The web interface is accessible again, and this telnet connection is closed. end of procedure Issue2,November2007 Draft5forRegulatoryReview 480 Release8 33 OBTAININGTECHNICALSUPPORT OperationsGuide NOTE:

The contact information for Cyclone Technical Support staff is included at the end of this section (on Page 485). However, in most cases, you should follow the procedure of this section before you contact them. To get information or assistance as soon as possible for problems that you encounter, use the following sequence of actions:

1. Search this document, the user guides of products that are supported by dedicated documents, and the software release notes of supported releases a. b. in the Table of Contents for the topic. in the Adobe Reader search capability for keywords that apply.8 2. Visit http://Last Mile Gear.Cyclonewireless.com/support/knowledge to view the Cyclone Knowledge Base. 3. Ask your Cyclone products supplier to help. 4. View and analyze event logs, error messages, and debug messages to help isolate the problem. 5. Check release notes and verify that all of your Cyclone equipment is on the correct software release. 6. Verify that the Cyclone configuration files match the last known good (baseline) Cyclone configuration files captured in the site log book. 7. Verify connectivity (physical cabling). 8. At the SM level, minimize your network configuration (remove home network devices to help isolate problem). 9. Perform the site verification checklist. 10. Use Table 65 (two pages) as a job aid to collect basic site information for technical support to use. 8 Reader is a registered trademark of Adobe Systems, Incorporated. Issue2,November2007 Draft5forRegulatoryReview 481 Release8 OperationsGuide Table 65: Basic site information for technical support Call Log Number:

Problem Type:

Call Severity (Select One):

1- Urgent-Customer Svc Down 2- Serious- Customer Svc Impacted 3- Non-Critical/General Inquiry Product Types Involved:

(ID the product type) 2400 SM/AP/BHM/BHS 5200 ER /BHM/BHS 5200 SM/AP/BHM/BHS 5700 SM/AP/BHM/BHS 1008CK 300SS ACPS110 Software Releases:

Authentication ?:

Yes/No Type:

Company:

Location:

Site Contact:

Site Phone:

Open Date:

Close Date:

MAC Addresses:

IP Addresses:

Boot Versions:

Is the customer using shielded cables?

Yes/No FPGA Versions:

Remote Access Method:

IP Address:

Issue2,November2007 Draft5forRegulatoryReview 482 Release8 Network Scenario for this issue:

(ID those that apply) SM to Subscriber PC Yes/No SM to AP (Point to Multipoint) Yes/No BHM to BHS (Point to Point) Yes/No 20Meg or 10Meg backhaul Yes/No NAT/DHCP Scenario:

NAT Disabled Yes/No NAT with DHCP Client and DHCP Server Yes/No NAT with DHCP Client Yes/No NAT with DHCP Server Yes/No NAT with no DHCP Yes/No OperationsGuide Reflectors in use:

Yes/No Link Distance:

dBm=

Jitter=

Problem Description:

New Install: Yes/No NAT/DHCP Scenario:

NAT Disabled Yes/No NAT with DHCP Client and DHCP Server Yes/No NAT with DHCP Client Yes/No NAT with DHCP Server Yes/No NAT with no DHCP Yes/No 11. Save your basic site information as file Site_Info. 12. From among Figure 28 on Page 103, Figure 29 on Page 104, and Figure 30 on Page 104, select the basic network topology diagram that most closely matches your network configuration. 13. If you selected Figure 28. a. Indicate how many APs are in each cluster. b. Indicate how many AP clusters are deployed (and what types). c. Include the IP addresses. d. Indicate the frequency for each sector. e. Indicate the type of synchronization. f. Indicate how much separation exists between clusters. g. For each AP collect the following additional information:

Sector number:

SW release:

Frequency:

Color code:

Issue2,November2007 Draft5forRegulatoryReview 483 Release8 OperationsGuide IP address:

Downlink/uplink ratio:

Max range:

Bridge entry timeout:

Number of subscribers:

Method of synchronization:

14. If you selected Figure 29 Indicate how many APs are in each cluster. Indicate how many AP clusters are deployed (and what types). Indicate how many BH links are configured. Include the IP addresses. Indicate the frequency for each sector. Indicate the type of synchronization. Indicate how much separation exists between clusters and BHs. Indicate the types of BH links (10-Mbps or 20-Mbps). a. b. c. d. e. f. g. h. i. Distances of links. j. Frequency used by each BH. k. For each AP and BHM, collect the following additional information:

Sector number:

SW release:

Frequency:

Color code:

IP address:

Downlink/uplink ratio:

Max range:

Bridge entry timeout:

Number of subscribers:

Method of synchronization:

15. If you selected Figure 30, collect the following additional information:

Sector number:

SW release:

Frequency:

Color code:

IP address:

Downlink/uplink ratio:

Max range:

Bridge entry timeout:

Number of subscribers:

Method of synchronization:

16. Add any details that are not present in the generic diagram that you selected. 17. Save your diagram as file Net_Diagram. Issue2,November2007 Draft5forRegulatoryReview 484 Release8 OperationsGuide 18. Capture screens from the following web pages of affected modules:

Home page Status tabs as files SM/AP/BHM/BHS_StatusTabname.gif

Configuration page tabs as files SM/AP/BHM/BHS_ConfigTabname.gif

Home page Event Log as file SM/AP/BHM/BHS_Events.gif

Tools page Link Capacity Test tab (with link test results) as file SM/AP/BHM/BHS_LinkTST.gif

Statistics page Radio tab as file SM/AP/BHM/BHS_RFstats.gif 19. For any affected SM or BHS, capture the Tools page AP Evaluation tab as file SM/BHS_APEval.gif. 20. For any affected SM that has NAT/DHCP enabled, capture screens from the Logs page NAT Table tab as file SM_NatTable.gif following additional web pages:

Configuration page NAT tab as file SM_Natconfig.gif

Configuration page NAT Port Mapping tab as file SM_NatPortmap.gif

Statistics page NAT Stats tab as file SM_NatStats.gif

Statistics page Translation Table tab as file SM_ArpStats.gif

Statistics page NAT DHCP Statistics tab as file SM_DhcpStats.gif Also capture the Windows IP Configuration screen as file SM _WindowsIP.gif. 21. Escalate the problem to Cyclone systems Technical Support (or another technical support organization that has been designated for you) as follows:

a. Start e-mail to technical-support@Cyclonewireless.com. In this email

Describe the problem.

Describe the history of the problem.

Attach the above files.

List the files that you are attaching. List your attempts to solve the problem. b. Send the email. c. Call 1 888 605 2552 (or +1 217 824 9742). end of procedure Issue2,November2007 Draft5forRegulatoryReview 485 Release8 34 GETTINGWARRANTYASSISTANCE OperationsGuide For warranty assistance, contact your reseller or distributor for the process. Issue2,November2007 Draft5forRegulatoryReview 487 Release8 ReferenceInformation RRREEEFFFEEERRREEENNNCCCEEE IIINNNFFFOOORRRMMMAAATTTIIIOOONNN Issue2,November2007 Draft5forRegulatoryReview 489 Release8 35 ADMINISTERINGMODULESTHROUGHTELNET ReferenceInformation INTERFACE In the telnet administrative interface to a module, the Cyclone platform supports the commands defined in Table 66. Many of these are not needed with CNUT. Table 66: Supported telnet commands for module administration Command addwebfile System help Definition Add a custom web file burnfile Burn flash from file Notes Syntax: addwebfile filename. Copies the custom web file filename to non-volatile memory. Syntax: burnfile filename. Updates the CPU firmware with a new image. User the image contained in filename if filename is provided. If provided, filename must match the module type (for example, SMboot.bin for a Subscriber Module or APboot.bin for an Access Point Module). cat Concatenate and display. Syntax: cat filename. Displays the contents clearsyslog Clear the system event log clearwebfile Clear all custom web fpga_conf Update FPGA program files Exit from telnet session Syntax: exit. Terminates the telnet interface File transfer application Syntax: ftp. Launches the ftp client application of filename. Syntax: clearsyslog. Clears the system event log. Syntax: clearwebfile. Deletes all custom web files. session. Syntax: fpga_conf. Forces a module to perform a hard (FPGA and CPU) reset. (See reset.) on the module. Syntax: help. Displays a list of available telnet commands and a brief description of each. Syntax: jbi aprogram file.jbc. Updates the FPGA firmware with the new image contained in file.jbc. Syntax: ls. Lists the file names of all files in the directory. Syntax: ls l. Displays additional information, such as the sizes and dates of the files. Syntax: lsweb. Lists the file names of the saved custom web files. Display command line function help Update FPGA program List the contents of a directory exit ftp help jbi ls lsweb List Flash Web files Issue2,November2007 Draft5forRegulatoryReview 491 Release8 ReferenceInformation Command ping System help Definition Send ICMP ECHO_REQUEST packets to network hosts reset Reboot the unit rm syslog Remove (unlink) files Display system event log:

syslog <optional filename>

telnet Telnet application tftp tftp application update Enable automatic SM code updating updateoff version Disable automatic SM code updating Display the software version string Notes Syntax: ping IPaddress. Sends an ICMP ECHO_REQUEST to IPaddress and waits for a response. If a response is received, the system returns IPaddress is alive. If no response is received, the system returns no answer from IPaddress. Syntax: reset. Forces the module to perform a hard (FPGA and CPU) module reset. (See fpga_conf.) Syntax: rm filename. Remove filename. Syntax: syslog. Displays the contents of the system log. Syntax: syslog filename. Saves the contents of the system log to filename. Caution: overwrites filename if it already exists. Syntax: telnet hostIPaddress. Launches the telnet client application on the Cyclone module. Syntax: tftp hostIPaddress. Launches the tftp client application on the Cyclone module. Syntax: update actionlist.txt. Enables the automated update procedure that actionlist.txt specifies. (Supported for only the Access Point Module.) Syntax: updateoff. Disables the automated update procedure. Syntax: version. Displays the module version string, which contains the software/firmware/hardware versions, the module type, and the operating frequency. Issue2,November2007 Draft5forRegulatoryReview 492 Release8 36 REGULATORYANDLEGALNOTICES ReferenceInformation 36.1 IMPORTANTNOTEONMODIFICATIONS Intentional or unintentional changes or modifications to the equipment must not be made unless under the express consent of the party responsible for compliance. Any such modifications could void the users authority to operate the equipment and will void the manufacturers warranty. 36.2 NATIONALANDREGIONALREGULATORYNOTICES 36.2.1 U.S.FederalCommunicationCommission(FCC)Notification This device complies with Part 15 of the US FCC Rules and Regulations. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) This device must accept any interference received, including interference that may cause undesired operation. This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the US FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with these instructions, may cause harmful interference to radio communications. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment on and off, the user is encouraged to correct the interference by one or more of the following measures:

Increase the separation between the affected equipment and the unit;

Connect the affected equipment to a power outlet on a different circuit from that which the receiver is connected to;

Consult the dealer and/or experienced radio/TV technician for help. FCC IDs and the specific configurations covered are listed in Table 67. Issue2,November2007 Draft5forRegulatoryReview 493 Release8 ReferenceInformation Table 67: US FCC IDs and Industry Canada Certification Numbers and Covered Configurations FCC ID ABZ89FC5809 Frequencies Industry Canada Cert Number 109W-9000 8 MHz channels, centered on 906-

924 MHz in 1 MHz increments (within the 902-928 MHz ISM band) ABZ89FC5808 ABZ89FC3789 ABZ89FC5807 ABZ89FT7623 109W-2400 20 MHz channels, centered on 2415-

2457.5 MHz in 2.5 MHz increments

(within the 2400-

2483.5 MHz ISM band) 109W-5200 20 MHz channels, centered on 5275-

5325 MHz in 5 MHz increments (within the 5250-5350 MHz U-NII band) 109W-5210 20 MHz channels, centered on 5275-

5325 MHz in 5 MHz increments (within the 5250-5350 MHz U-NII band) 20 MHz channels, centered on 5495-

5705 MHz in 5 MHz increments (within the 5470-5725 MHz U-NII band)

---

Module Families Antenna or Reflector 900 SM, AP 2400 BH, SM, AP 12 dBi Cyclone integrated antenna 10 dBi Maxrad Model # Z1681, flat panel 10 dBi Mars Model # MA-

IS91-T2, flat panel 10 dBi MTI Model #MT-

2630003/N, flat panel 8 dBi internal Maximum Transmitter Output Power 24 dBm

(250 mW) 26 dBm

(400 mW) 26 dBm

(400 mW) 26 dBm

(400 mW) 25 dBm

(340 mW) 2400 BH, SM 8 dBi internal +

11 dB reflector 25 dBm

(340 mW) 5200 BH, SM, AP 5200 BH or SM, only P10 Modules 5210 BH 7 dBi internal 7 dBi internal +

18 dB reflector 7 dBi internal +

9 dB lens 23 dBm

(200 mW) 5 dBm

(3.2 mW) 14 dBm 7 dBi internal +

18 dB reflector 5 dBm

(3.2 mW) 5400 BH, SM, AP 5400 BH, SM 7 dBi internal 7 dBi internal +

18 dB reflector 7 dBi internal +

9 dB lens 23 dBm

(200 mW) 5 dBm

(3.2 mW) 14 dBm Issue2,November2007 Draft5forRegulatoryReview 494 Release8 FCC ID

---

ABZ89FC5804 ReferenceInformation Frequencies Industry Canada Cert Number 109W-5400 20 MHz channels, centered on 5495-

5575 and 5675-

5705 MHz in 5 MHz increments (within the 5470-5725 MHz U-NII band with 5600-5650 MHz excluded) 109W-5700 20 MHz channels, centered on 5735-

5840 MHz in 5 MHz increments (within the 5725-5850 MHz ISM band) Module Families Antenna or Reflector 5400 BH, SM, AP 5400 BH, SM 7 dBi internal 7 dBi internal +

18 dB reflector 7 dBi internal +

9 dB lens 5700 BH, SM, AP 5700 BH, SM 7 dBi internal 7 dBi internal +

18 dB reflector Maximum Transmitter Output Power 23 dBm

(200 mW) 5 dBm

(3.2 mW) 14 dBm 23 dBm

(200 mW) 23 dBm

(200 mW) 7 dBi internal +

10 di lens 23 dBm

(200 mW) ABZ89FT7629

---

10 MHz channels, centered on 5476-

5719 in 0.5 MHz increments (within the 5470-5725 MHz U-NII band) 5440 AP 5440 SM 10 dBm 10 dBm 17 dBi connectorized antenna (60 x 5 3 dB beam width) 17 dBi integrated antenna (18 x 18 3 dB beam width) 36.2.2 IndustryCanada(IC)Notification This device complies with RSS-210 of Industry Canada. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) This device must accept any interference received, including interference that may cause undesired operation. Users should be cautioned to take note that in Canada high power radars are allocated as primary users (meaning they have priority) of 5250 5350 MHz and 5650 5850 MHz and these radars could cause interference and/or damage to license-exempt local area networks (LELAN). This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to RSS-210 of Industry Canada. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with these instructions, may cause harmful interference to radio communications. If this equipment does cause harmful interference to radio or Issue2,November2007 Draft5forRegulatoryReview 495 Release8 ReferenceInformation television reception, which can be determined by turning the equipment on and off, the user is encouraged to correct the interference by one or more of the following measures:

Increase the separation between the affected equipment and the unit;

Connect the affected equipment to a power outlet on a different circuit from that which the receiver is connected to;

Consult the dealer and/or experienced radio/TV technician for help. To reduce potential radio interference to other users, the antenna type and its gain should be chosen so its Equivalent Isotropic Radiated Power (EIRP) is not more than that permitted for successful communication. Industry Canada Certification Numbers and the specific configurations covered are listed in Table 67. This device has been designed to operate with the antennas listed in Table 67 and having a maximum gain as shown in Table 67. Antennas not included or having a gain greater than as shown in Table 67 are strictly prohibited from use with this device. Required antenna impedance is 50 ohms. 36.2.3 RegulatoryRequirementsforCEPTMemberStates(www.cept.org) When operated in accordance with the instructions for use, Last Mile Gear Cyclone Wireless equipment operating in the 2.4 and 5.4 GHz bands is compliant with CEPT Recommendation 70-03 Annex 3 for Wideband Data Transmission and HIPERLANs. For compliant operation in the 2.4 GHz band, the transmit power (EIRP) from the built-in patch antenna and any associated reflector dish shall be no more than 100mW (20dBm). For compliant operation in the 5.4 GHz band, the transmit power (EIRP) from the built-in patch antenna and any associated reflector dish shall be no more than 1 W (30 dBm). The following countries have completely implemented CEPT Recommendation 70-03 Annex 3A (2.4 GHz band):

EU & EFTA countries: Austria, Belgium, Denmark, Spain, Finland, Germany, Greece, Iceland, Italy, Ireland, Liechtenstein, Luxembourg, Netherlands, Norway, Portugal, Switzerland, Sweden, UK New EU member states: Bulgaria, Czech Republic, Cyprus, Estonia, Hungary, Lithuania, Latvia, Malta, Poland, Slovenia, Slovakia Other non-EU & EFTA countries: Bosnia and Herzegovina, Turkey The following countries have a limited implementation of CEPT Recommendation 70-03 Annex 3A:

France Outdoor operation at 100mW is only permitted in the frequency band 2400 to 2454 MHz;

Any outdoor operation in the band 2454 to 2483.5MHz shall not exceed

10mW (10dBm);

Indoor operation at 100mW (20dBm) is permitted across the band 2400 to 2483.5 MHz French Overseas Territories:

Guadeloupe, Martinique, St Pierre et Miquelon, Mayotte 100mW indoor &

outdoor is allowed

Runion and Guyana 100mW indoor, no operation outdoor in the band 2400 to 2420MHz Italy If used outside own premises, general authorization required Issue2,November2007 Draft5forRegulatoryReview 496 Release8 ReferenceInformation Luxembourg - General authorization required for public service Romania Individual license required. T/R 22-06 not implemented Last Mile Gear Cyclone Radios operating in the 2400 to 2483.5MHz band are categorized as Class 2 devices within the EU and are marked with the class identifier symbol restriction in the 2.4 GHz band will be removed in 2011.

, denoting that national restrictions apply (for example, France). The French This 2.4 GHz equipment is CE marked Radio & Telecommunications Terminal Equipment (R&TTE) directive 1999/5/EC. The relevant Declaration of Conformity can be found at http://Last Mile Gear.Cyclonewireless.com/doc.php. to show compliance with the European Where necessary, the end user is responsible for obtaining any National licenses required to operate this product and these must be obtained before using the product in any particular country. However, for CEPT member states, 2.4 GHz Wideband Data Transmission equipment has been designated exempt from individual licensing under decision ERC/DEC(01)07. For EU member states, RLAN equipment in both the 2.4 &

5.4GHz bands is exempt from individual licensing under Commission Recommendation 2003/203/EC. Contact the appropriate national administrations for details on the conditions of use for the bands in question and any exceptions that might apply. Also see www.ero.dk for further information. Last Mile Gear Cyclone Radio equipment operating in the 5470 to 5725 MHz band are categorized as Class 1 devices within the EU in accordance with ECC DEC(04)08 and are CE marked Telecommunications Terminal Equipment (R&TTE) directive 1999/5/EC. The relevant Declaration of Conformity can be found at http://Last Mile Gear.Cyclonewireless.com/doc.php. to show compliance with the European Radio &

A European Commission decision, implemented by Member States on 31 October 2005, makes the frequency band 5470-5725 MHz available in all EU Member States for wireless access systems. Under this decision, the designation of Cyclone 5.4GHz products become Class 1 devices and these do not require notification under article 6, section 4 of the R&TTE Directive. Consequently, these 5.4GHz products are only marked with the symbol and may be used in any member state. For further details, see http://europa.eu.int/information_society/policy/radio_spectrum/ref_documents/index_en.ht m 36.2.4 EuropeanUnionNotificationfor5.7GHzProduct The 5.7 GHz connectorized product is a two-way radio transceiver suitable for use in Broadband Wireless Access System (WAS), Radio Local Area Network (RLAN), or Fixed Wireless Access (FWA) systems. It is a Class 2 device and uses operating frequencies that are not harmonized throughout the EU member states. The operator is responsible for obtaining any national licenses required to operate this product and these must be obtained before using the product in any particular country. This equipment is marked R&TTE directive 1999/5/EC. 0977to show compliance with the European Issue2,November2007 Draft5forRegulatoryReview 497 Release8 The relevant Declaration of Conformity can be found at http://www.Cyclonewireless.com/doc.php. ReferenceInformation 36.2.5 EquipmentDisposal Waste

(Disposal) of Electronic and Electric Equipment Please do not dispose of Electronic and Electric Equipment or Electronic and Electric Accessories with your household waste. In some countries or regions, collection systems have been set up to handle waste of electrical and electronic equipment. In European Union countries, please contact your local equipment supplier representative or service center for information about the waste collection system in your country. 36.2.6 EUDeclarationofConformityforRoHSCompliance Last Mile Gear hereby, declares that these Last Mile Gear products are in compliance with the essential requirements and other relevant provisions of Directive 2002/95/EC, Restriction of the use of certain Hazardous Substances (RoHS) in electrical and electronic equipment. The relevant Declaration of Conformity can be found at http://www.Cyclonewireless.com/doc.php. 36.2.7 UKNotification The 5.7 GHz connectorized product has been notified for operation in the UK, and when operated in accordance with instructions for use it is compliant with UK Interface Requirement IR2007. For UK use, installations must conform to the requirements of IR2007 in terms of EIRP spectral density against elevation profile above the local horizon in order to protect Fixed Satellite Services. The frequency range 5795-5815 MHz is assigned to Road Transport & Traffic Telematics (RTTT) in the U.K. and shall not be used by FWA systems in order to protect RTTT devices. UK licensing specifies that radiolocation services shall be protected by a Dynamic Frequency Selection (DFS) mechanism to prevent co-channel operation in the presence of radar signals. 36.2.8 BelgiumNotification Belgium national restrictions in the 2.4 GHz band include EIRP must be lower then 100 mW For crossing the public domain over a distance > 300m the user must have the authorization of the BIPT. No duplex working 36.2.9 LuxembourgNotification For the 2.4 GHz band, point-to-point or point-to-multipoint operation is only allowed on campus areas. 5.4GHz products can only be used for mobile services. Issue2,November2007 Draft5forRegulatoryReview 498 Release8 36.2.10 CzechRepublicNotification ReferenceInformation 2.4 GHz products can be operated in accordance with the Czech General License No. GL-12/R/2000. 5.4 GHz products can be operated in accordance with the Czech General License No. GL-30/R/2000. 36.2.11 NorwayNotification Use of the frequency bands 5725-5795 / 5815-5850 MHz are authorized with maximum radiated power of 4 W EIRP and maximum spectral power density of 200 mW/MHz. The radio equipment shall implement Dynamic Frequency Selection (DFS) as defined in Annex 1 of ITU-R Recommendation M.1652 / EN 301 893. Directional antennae with a gain up to 23 dBi may be used for fixed point-to-point links. The power flux density at the border between Norway and neighboring states shall not exceed 122.5 dBW/m2 measured with a reference bandwidth of 1 MHz. Cyclone 5.7 GHz connectorized products have been notified for use in Norway and are compliant when configured to meet the above National requirements. Users shall ensure that DFS functionality is enabled, maximum EIRP respected for a 20 MHz channel, and that channel spacings comply with the allocated frequency band to protect Road Transport and Traffic Telematics services (for example, 5735, 5755, 5775 or 5835 MHz are suitable carrier frequencies). Note that for directional fixed links, TPC is not required, conducted transmit power shall not exceed 30 dBm, and antenna gain is restricted to 23 dBi (maximum of 40W from the Cyclone 5.7 GHz connectorized products). 36.2.12 GreeceNotification The outdoor use of 5470-5725MHz is under license of EETT but is being harmonized according to the CEPT Decision ECC/DEC/(04) 08, of 9th July. End users are advised to contact the EETT to determine the latest position and obtain any appropriate licenses. 36.2.13 BrazilNotification Local regulations do not allow the use of 900 MHz, 2.4 GHz, or 5.2 GHz Cyclone modules in Brazil. For compliant operation of an AP in the 5.7 GHz band, the Equivalent Isotropic Radiated Power from the built-in patch antenna and any associated reflector dish or LENS shall not exceed 36 dBm (4 W). When using the passive reflector (18 dB), transmitter output power must be configured no higher than 11 dBm. When using the LENS (10 dB at 5.7 GHz), transmitter output power must be configured no higher than 19 dBm. For compliant operation in the 5.4 GHz band, the Equivalent Isotropic Radiated Power from the built-in patch antenna and any associated reflector dish or LENS shall not exceed 30 dBm (1 W). When using the passive reflector (18 dB), transmitter output power must be configured no higher than 5 dBm. When using the LENS (9 dB at 5.4 GHz), transmitter output power must be configured no higher than 14 dBm. When not using the passive reflector or the LENS, the transmitter output power of the radio must be configured no higher than 23 dBm. The operator is responsible for enabling the DFS feature on any Cyclone 5.4 GHz radio by setting the Region Code to Brazil, including after the module is reset to factory defaults. Issue2,November2007 Draft5forRegulatoryReview 499 Release8 ReferenceInformation Important Note: This equipment operates as a secondary application, so it has no rights against harmful interference, even if generated by similar equipment, and cannot cause harmful interference on systems operating as primary applications. 36.2.14 AustraliaNotification 900 MHz modules must be set to transmit and receive only on center channels of 920, 922, or 923 MHz so as to stay within the ACMA approved band of 915 MHz to 928 MHz for the class license and not interfere with other approved users. After taking into account antenna gain (in dBi), 900 MHz modules transmitter output power (in dBm) must be set to stay within the legal regulatory limit of 30 dBm (1 W) EIRP for this 900 MHz frequency band. 36.2.15 LabelingandDisclosureTableforChina The Peoples Republic of China requires that Last Mile Gears products comply with China Management Methods (CMM) environmental regulations. (China Management Methods refers to the regulation Management Methods for Controlling Pollution by Electronic Information Products.) Two items are used to demonstrate compliance; the label and the disclosure table. The label is placed in a customer visible position on the product. Logo 1 means that the product contains no substances in excess of the maximum concentration value for materials identified in the China Management Methods regulation. Logo 2 means that the product may contain substances in excess of the maximum concentration value for materials identified in the China Management Methods regulation, and has an Environmental Friendly Use Period (EFUP) in years, fifty years in the example shown. Logo 1 Logo 2 The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic and Hazardous Substances (T&HS) contained in the Electronic Information Product

(EIP) will not leak or mutate causing environmental pollution or bodily injury from the use of the EIP. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certain field-replaceable parts, such as battery modules, can have a different EFUP and are marked separately. The Disclosure Table is intended only to communicate compliance with China requirements; it is not intended to communicate compliance with EU RoHS or any other environmental requirements. Issue2,November2007 Draft5forRegulatoryReview 500 Release8 ReferenceInformation

(Pb)

(Hg)

(Cd)

(Cr6+)

(PBB)

(PBDE) SJ/T11363-2006 SJ/T11363-2006 Table 68: Disclosure Table 36.3 RFEXPOSURE For important information on RF exposure and separation distances see Section 15.1, Exposure Separation Distances, on Page 169. 36.4 LEGALNOTICES 36.4.1 SoftwareLicenseTermsandConditions ONLY OPEN THE PACKAGE, OR USE THE SOFTWARE AND RELATED PRODUCT IF YOU ACCEPT THE TERMS OF THIS LICENSE. BY BREAKING THE SEAL ON THIS DISK KIT /

CDROM, OR IF YOU USE THE SOFTWARE OR RELATED PRODUCT, YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT. IF YOU DO NOT AGREE TO THESE TERMS, DO NOT USE THE SOFTWARE OR RELATED PRODUCT; INSTEAD, RETURN THE SOFTWARE TO PLACE OF PURCHASE FOR A FULL REFUND. THE FOLLOWING AGREEMENT IS A LEGAL AGREEMENT BETWEEN YOU (EITHER AN INDIVIDUAL OR ENTITY), AND LAST MILE GEAR, INC. (FOR ITSELF AND ITS LICENSORS). THE RIGHT TO USE THIS PRODUCT IS LICENSED ONLY ON THE CONDITION THAT YOU AGREE TO THE FOLLOWING TERMS. Now, therefore, in consideration of the promises and mutual obligations contained herein, and for other good and valuable consideration, the receipt and sufficiency of which are hereby mutually acknowledged, you and Last Mile Gear agree as follows:

Grant of License. Subject to the following terms and conditions, Last Mile Gear, Inc., grants to you a personal, revocable, non-assignable, non-transferable, non-exclusive and limited license to use on a single piece of equipment only one copy of the software contained on this disk (which may have been pre-loaded on the equipment)(Software). You may make two copies of the Software, but only for backup, archival, or disaster recovery purposes. On any copy you make of the Software, you must reproduce and include the copyright and other proprietary rights notice contained on the copy we have furnished you of the Software. Ownership. Last Mile Gear (or its supplier) retains all title, ownership and intellectual property rights to the Software and any copies, Issue2,November2007 Draft5forRegulatoryReview 501 Release8 ReferenceInformation including translations, compilations, derivative works (including images) partial copies and portions of updated works. The Software is Last Mile Gears (or its supplier's) confidential proprietary information. This Software License Agreement does not convey to you any interest in or to the Software, but only a limited right of use. You agree not to disclose it or make it available to anyone without Last Mile Gears written authorization. You will exercise no less than reasonable care to protect the Software from unauthorized disclosure. You agree not to disassemble, decompile or reverse engineer, or create derivative works of the Software, except and only to the extent that such activity is expressly permitted by applicable law. Termination. This License is effective until terminated. This License will terminate immediately without notice from Last Mile Gear or judicial resolution if you fail to comply with any provision of this License. Upon such termination you must destroy the Software, all accompanying written materials and all copies thereof, and the sections entitled Limited Warranty, Limitation of Remedies and Damages, and General will survive any termination. Limited Warranty. Last Mile Gear warrants for a period of ninety (90) days from Last Mile Gears or its customers shipment of the Software to you that (i) the disk(s) on which the Software is recorded will be free from defects in materials and workmanship under normal use and (ii) the Software, under normal use, will perform substantially in accordance with Last Mile Gears published specifications for that release level of the Software. The written materials are provided

"AS IS" and without warranty of any kind. Last Mile Gear's entire liability and your sole and exclusive remedy for any breach of the foregoing limited warranty will be, at Last Mile Gear's option, replacement of the disk(s), provision of downloadable patch or replacement code, or refund of the unused portion of your bargained for contractual benefit up to the amount paid for this Software License. THIS LIMITED WARRANTY IS THE ONLY WARRANTY PROVIDED BY LAST MILE GEAR, AND LAST MILE GEAR AND ITS LICENSORS EXPRESSLY DISCLAIM ALL OTHER WARRANTIES, EITHER EXPRESS OF IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. LAST MILE GEAR DOES NOT WARRANT THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT DEFECTS IN THE SOFTWARE WILL BE CORRECTED. NO ORAL OR WRITTEN REPRESENTATIONS MADE BY LAST MILE GEAR OR AN AGENT THEREOF SHALL CREATE A WARRANTY OR IN ANY WAY INCREASE THE SCOPE OF THIS WARRANTY. LAST MILE GEAR DOES NOT WARRANT ANY SOFTWARE THAT HAS BEEN OPERATED IN EXCESS OF SPECIFICATIONS, DAMAGED, MISUSED, NEGLECTED, OR IMPROPERLY INSTALLED. BECAUSE SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF IMPLIED WARRANTIES, THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU. Limitation of Remedies and Damages. Regardless of whether any remedy set forth herein fails of its essential purpose, IN NO EVENT SHALL LAST MILE GEAR OR ANY OF THE LICENSORS, DIRECTORS, OFFICERS, EMPLOYEES OR AFFILIATES OF THE FOREGOING BE LIABLE TO YOU FOR ANY CONSEQUENTIAL, INCIDENTAL, INDIRECT, SPECIAL OR SIMILAR DAMAGES WHATSOEVER (including, without limitation, damages for loss of business profits, business interruption, loss of business information and the like), whether foreseeable or unforeseeable, arising out of the use or inability to use the Software or accompanying written materials, regardless of the basis of the claim and even if Last Mile Gear or a Last Mile Gear representative has been advised of the possibility of such damage. Last Mile Gear's liability to you for direct damages for any cause whatsoever, regardless of the basis of the form of the action, will be limited to the price paid for the Software that caused the damages. THIS LIMITATION WILL NOT APPLY IN CASE OF PERSONAL INJURY ONLY WHERE AND TO THE EXTENT THAT APPLICABLE LAW REQUIRES SUCH LIABILITY. BECAUSE SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO YOU. Maintenance and Support. Last Mile Gear shall not be responsible for maintenance or support of the software. By accepting the license granted under this agreement, you agree that Last Mile Gear will be under no obligation to provide any support, maintenance or service in connection with the Software or any application developed by you. Any maintenance and support of the Related Product will be provided under the terms of the agreement for the Related Product. Issue2,November2007 Draft5forRegulatoryReview 502 Release8 ReferenceInformation Transfer. In the case of software designed to operate on Last Mile Gear equipment, you may not transfer the Software to another party except: (1) if you are an end-user, when you are transferring the Software together with the Last Mile Gear equipment on which it operates; or 2) if you are a Last Mile Gear licensed distributor, when you are transferring the Software either together with such Last Mile Gear equipment or are transferring the Software as a licensed duly paid for upgrade, update, patch, new release, enhancement or replacement of a prior version of the Software. If you are a Last Mile Gear licensed distributor, when you are transferring the Software as permitted herein, you agree to transfer the Software with a license agreement having terms and conditions no less restrictive than those contained herein. You may transfer all other Software, not otherwise having an agreed restriction on transfer, to another party. However, all such transfers of Software are strictly subject to the conditions precedent that the other party agrees to accept the terms and conditions of this License, and you destroy any copy of the Software you do not transfer to that party. You may not sublicense or otherwise transfer, rent or lease the Software without our written consent. You may not transfer the Software in violation of any laws, regulations, export controls or economic sanctions imposed by the US Government. Right to Audit. Last Mile Gear shall have the right to audit annually, upon reasonable advance notice and during normal business hours, your records and accounts to determine compliance with the terms of this Agreement. Export Controls. You specifically acknowledge that the software may be subject to United States and other country export control laws. You shall comply strictly with all requirements of all applicable export control laws and regulations with respect to all such software and materials. US Government Users. If you are a US Government user, then the Software is provided with

"RESTRICTED RIGHTS" as set forth in subparagraphs (c)(1) and (2) of the Commercial Computer Software-Restricted Rights clause at FAR 52 227-19 or subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, as applicable. Disputes. You and Last Mile Gear hereby agree that any dispute, controversy or claim, except for any dispute, controversy or claim involving intellectual property, prior to initiation of any formal legal process, will be submitted for non-binding mediation, prior to initiation of any formal legal process. Cost of mediation will be shared equally. Nothing in this Section will prevent either party from resorting to judicial proceedings, if (i) good faith efforts to resolve the dispute under these procedures have been unsuccessful, (ii) the dispute, claim or controversy involves intellectual property, or (iii) interim relief from a court is necessary to prevent serious and irreparable injury to that party or to others. General. Illinois law governs this license. The terms of this license are supplemental to any written agreement executed by both parties regarding this subject and the Software Last Mile Gear is to license you under it, and supersedes all previous oral or written communications between us regarding the subject except for such executed agreement. It may not be modified or waived except in writing and signed by an officer or other authorized representative of each party. If any provision is held invalid, all other provisions shall remain valid, unless such invalidity would frustrate the purpose of our agreement. The failure of either party to enforce any rights granted hereunder or to take action against the other party in the event of any breach hereunder shall not be deemed a waiver by that party as to subsequent enforcement of rights or subsequent action in the event of future breaches. 36.4.2 HardwareWarrantyinU.S. Last Mile Gear U.S. offers a warranty covering a period of one year from the date of purchase by the customer. If a product is found defective during the warranty period, Last Mile Gear will repair or replace the product with the same or a similar model, which may be a reconditioned unit, without charge for parts or labor. 36.4.3 LimitofLiability IN NO EVENT SHALL LAST MILE GEAR BE LIABLE TO YOU OR ANY OTHER PARTY FOR ANY DIRECT, INDIRECT, GENERAL, SPECIAL, INCIDENTAL, CONSEQUENTIAL, EXEMPLARY OR OTHER DAMAGE ARISING OUT OF THE USE OR INABILITY TO USE THE PRODUCT

(INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION OR ANY OTHER Issue2,November2007 Draft5forRegulatoryReview 503 Release8 ReferenceInformation PECUNIARY LOSS, OR FROM ANY BREACH OF WARRANTY, EVEN IF LAST MILE GEAR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. (Some states do not allow the exclusion or limitation of incidental or consequential damages, so the above exclusion or limitation may not apply to you.) IN NO CASE SHALL LAST MILE GEARS LIABILITY EXCEED THE AMOUNT YOU PAID FOR THE PRODUCT. Issue2,November2007 Draft5forRegulatoryReview 504 Release8 37 ADDITIONALRESOURCES ReferenceInformation Cyclone provides two additional resources where you can raise questions and find answers:

Cyclone Community Forums at http://Last Mile Gear.Cyclonewireless.com/support/community/. This resource facilitates communication with other users and with authorized Cyclone experts. Available forums include General Discussion, Network Monitoring Tools, and Suggestions.

Cyclone Knowledge Base at http://Last Mile Gear.Cyclonewireless.com/support/knowledge. This resource facilitates exploration and searches, provides recommendations, and describes tools. Available categories include

General (Answers to general questions provide an overview of the Cyclone system.)

Product Alerts

Helpful Hints

FAQs (frequently asked questions)

Hardware Support

Software Support

Tools Issue2,November2007 Draft5forRegulatoryReview 505 Release8 38 HISTORYOFDOCUMENTATION ReferenceInformation This section is a placeholder where changes for Issue 2 and later of this Cyclone System Release 8 User Guide will be listed. Issue2,November2007 Draft5forRegulatoryReview 507 Release8 Glossary GGGLLLOOOSSSSSSAAARRRYYY Issue2,November2007 Draft5forRegulatoryReview 509 Release8

~. 10BaseT 100BaseTX 169.254.0.0 169.254.1.1 169.254.x.x 255.255.0.0 802.3 802.11 802.15 AccessPointCluster Glossary The command that terminates an SSH Secure Shell session to another server. Used on the Bandwidth and Authentication Manager

(BAM) master server in the database replication setup. Technology in Ethernet communications that can deliver 10 Mb of data across 328 feet (100 meters) of CAT 5 cable. Technology in Ethernet communications that can deliver 100 Mb of data across 328 feet (100 meters) of CAT 5 cable. Gateway IP address default in Cyclone modules. IP address default in Cyclone modules. IP address default in Microsoft and Apple operating systems without a DHCP (Dynamic Host Configuration Protocol) server. Subnet mask default in Cyclone modules and in Microsoft and Apple operating systems. An IEEE standard that defines the contents of frames that are transferred through Ethernet connections. Each of these frames contains a preamble, the address to which the frame is sent, the address that sends the frame, the length of the data to expect, the data, and a checksum to validate that no contents were lost. The IEEE standard for wireless local area networks. The IEEE standard for wireless personal area networks. Two to six Access Point Modules that together distribute network or Internet services to a community of 1,200 or fewer subscribers. Each Access Point Module covers a 60 sector. This cluster covers as much as 360. Also known as AP cluster. AccessPointModule Also known as AP. One module that distributes network or Internet services in a 60 sector to 200 subscribers or fewer. ACT/4 Activate Second-from-left LED in the module. In the operating mode, this LED is lit when data activity is present on the Ethernet link. In the aiming mode for a Subscriber Module or a Backhaul timing slave, this LED is part of a bar graph that indicates the quality of the RF link. To provide feature capability to a module, but not to enable (turn on) the feature in the module. See also Enable. AddressResolution Protocol Protocol defined in RFC 826 to allow a network element to correlate a host IP address to the Ethernet address of the host. See http://www.faqs.org/rfcs/rfc826.html. Issue2,November2007 Draft5forRegulatoryReview 510 Release8 AdvancedEncryption Standard Glossary Over-the-air link option that provides extremely secure wireless connections. Advanced Encryption Standard (AES) uses 128-bit secret keys as directed by the government of the U.S.A. AES is not exportable and requires a special AP to process the large keys. AES See Advanced Encryption Standard. AggregateThroughput The sum of the throughputs in the uplink and the downlink. AP APA Apache APAS API APsMIB ARP ASN.1 Attenuation AuthenticationKey Access Point Module. One module that distributes network or Internet services in a 60 sector to 200 subscribers or fewer. Access Point module address. A trademark of Apache Software Foundation, used with permission. Access Point Authentication Server. Licensed to authenticate SMs that attempt to register to it. The AP licensed as APAS may or may not have authentication enabled (turned on). See also Activate and Enable. Application programming interface for web services that supports Prizm integration with an operations support systems (OSS) such as a customer relationship management (CRM), billing, or provisioning system. Management Information Base file that defines objects that are specific to the Access Point Module or Backhaul timing master. See also Management Information Base. Address Resolution Protocol. A protocol defined in RFC 826 to allow a network element to correlate a host IP address to the Ethernet address of the host. See http://www.faqs.org/rfcs/rfc826.html. Abstract Syntax Notation One language. The format of the text files that compose the Management Information Base. Reduction of signal strength caused by the travel from the transmitter to the receiver, and caused by any object between. In the absence of objects between, a signal that has a short wavelength experiences a high degree of attenuation nevertheless. Software key that correlates to the random number that the Bandwidth and Authentication Manager (BAM) server generates and sends in a challenge through the AP to the SM. The network operator can create and, at some security risk, send this key over the air to the SM. The SQL database in the BAM server correlates this key to QoS information about the SM. The format of this key is 32 hexadecimal characters of 0 to 9 and a to f, padded with leading zeroes in Release 4.2.3 and later. This key must be unique to the individual SM. Issue2,November2007 Draft5forRegulatoryReview 511 Release8 BackhaulModule Glossary Also known as BH. A module that provides point-to-point connectivity as either a standalone link or a link to an Access Point cluster through a selected Access Point Module. See also Backhaul Timing Master and Backhaul Timing Slave. BackhaulTiming Master BackhaulTimingSlave Backhaul Module that receives network timing (synchronization) from Backhaul Module that sends network timing (synchronization) to another Backhaul Module, which serves as the Backhaul timing slave. another Backhaul Module, which serves as the Backhaul timing master. BAM BER BH BitErrorRate BoxMIB BRAID Bridge Bandwidth and Authentication Manager. A Cyclone software product that operates on a Linux server to manage bandwidth, high-priority channel, and VLAN settings individually for each registered Subscriber Module. This software also provides secure Subscriber Module authentication and user-specified encryption keys. The upgrade path for this product is to Prizm Release 2.0 or later. Bit Error Rate. The ratio of incorrect data received to correct data received. Backhaul Module. A module that provides point-to-point connectivity as either a standalone link or a link to an Access Point cluster through a selected Access Point Module. Ratio of incorrect data received to correct data received. Management Information Base file that defines module-level objects. See also Management Information Base. Stream cipher that the TIA (Telecommunications Industry Association) has standardized. The secret keys in both modules communicate with each other to establish the Data Encryption Standard key. See Data Encryption Standard. Network element that uses the physical address (not the logical address) of another to pass data. The bridge passes the data to either the destination address, if found in the simple routing table, or to all network segments other than the one that transmitted the data. Cyclone modules are Layer 2 bridges except that, where NAT is enabled for an SM, the SM is a Layer 3 switch. Compare to Switch and Router, and see also NAT. BridgeEntryTimeout Field Value that the operator sets as the maximum interval for no activity with another module, whose MAC address is the Bridge Entry. This interval should be longer than the ARP (Address Resolution Protocol) cache timeout of the router that feeds the network. Buckets Theoretical data repositories that can be filled at preset rates or emptied when preset conditions are experienced, such as when data is transferred. Issue2,November2007 Draft5forRegulatoryReview 512 Release8 Burst C/IRatio Cyclone Glossary Preset amount limit of data that may be continuously transferred. Ratio of intended signal (carrier) to unintended signal (interference). A trademark of Last Mile Gear, Inc. Cyclone.xml File that stores specifications for the Bandwidth and Authentication Manager (BAM) GUI. Carriertointerference Ratio CarSenseLostField CAT5Cable cdf chkconfig Ratio of intended reception to unintended reception. This field displays how many carrier sense lost errors occurred on the Ethernet controller. Cable that delivers Ethernet communications from module to module. Later modules auto-sense whether this cable is wired in a straight-

through or crossover scheme. Cyclone Data Formatter tool that creates an initial ESN Data Table. Inputs for this tool include a list of SM ESNs and default values of sustained data rates and burst allocations for each listed ESN. A command that the Linux operating system accepts to enable MySQL and Apache Server software for various run levels of the mysqld and httpd utilities. CIR See Committed Information Rate. ClusterManagement Module Module that provides power, GPS timing, and networking connections for an AP cluster. Also known as CMM. If this CMM is connected to a Backhaul Module, then this CMM is the central point of connectivity for the entire site. CMM CodePoint ColorCodeField CommittedInformation Rate Cluster Management Module. A module that provides power, GPS timing, and networking connections for an Access Point cluster. If this CMM is connected to a Backhaul Module (BH), then this CMM is the central point of connectivity for the entire site. See DiffServ. Module parameter that identifies the other modules with which communication is allowed. The range of values is 0 to 255. When set at 0, the Color Code does not restrict communications with any other module. For an SM or specified group of SMs, a level of bandwidth that can be guaranteed to never fall below a specified minimum. In the Cyclone implementation, this is controlled by the Low Priority Uplink CIR, Low Priority Downlink CIR, High Priority Uplink CIR, and High Priority Downlink CIR parameters. Issue2,November2007 Draft5forRegulatoryReview 513 Release8 CommunityString Field CPE CRCErrorField CRM DataEncryption Standard Glossary Control string that allows a network management station to access MIB information about the module. Customer premises equipment. This field displays how many CRC errors occurred on the Ethernet controller. Customer relationship management system. Over-the-air link option that uses secret 56-bit keys and 8 parity bits. Data Encryption Standard (DES) performs a series of bit permutations, substitutions, and recombination operations on blocks of data. DateofLastTransaction A field in the data that the cmd show esn command generates from data in the SQL database in the Bandwidth and Authentication Manager (BAM) server. This field identifies the date of the most recent authentication attempt by the SM. Expressed in the database output as DLT. Dell A trademark of Dell, Inc. DemilitarizedZone Internet Protocol area outside of a firewall. Defined in RFC 2647. See http://www.faqs.org/rfcs/rfc2647.html. DES Desensed DHCP Diffraction Data Encryption Standard. An over-the-air link option that uses secret 56-bit keys and 8 parity bits. DES performs a series of bit permutations, substitutions, and recombination operations on blocks of data. Received an undesired signal that was strong enough to make the module insensitive to the desired signal. Dynamic Host Configuration Protocol, defined in RFC 2131. Protocol that enables a device to be assigned a new IP address and TCP/IP parameters, including a default gateway, whenever the device reboots. Thus DHCP reduces configuration time, conserves IP addresses, and allows modules to be moved to a different network within the Cyclone system. See http://www.faqs.org/rfcs/rfc2131.html. See also Static IP Address Assignment. Partial obstruction of a signal. Typically diffraction attenuates a signal so much that the link is unacceptable. However, in some instances where the obstruction is very close to the receiver, the link may be acceptable. Issue2,November2007 Draft5forRegulatoryReview 514 Release8 DiffServ Disable DLT DMZ DynamicHost ConfigurationProtocol ElectronicSerial Number Glossary Differentiated Services, consistent with RFC 2474. A byte in the type of service (TOS) field of packets whose values correlates to the channel on which the packet should be sent. The value is a numeric code point. Cyclone maps each of 64 code points to values of 0 through 7. Three of these code points have fixed values, and the remaining 61 are settable. Values of 0 through 3 map to the low-

priority channel; 4 through 7 to the high-priority channel. The mappings are the same as 802.1p VLAN priorities. Among the settable parameters, the values are set in the AP for all downlinks within the sector and in the SM for each uplink. To turn off a feature in the module after both the feature activation file has activated the module to use the feature and the operator has enabled the feature in the module. See also Activate and Enable. Date of last transaction. A field in the data that the cmd show esn command generates from data in the SQL database in the Bandwidth and Authentication Manager (BAM) server. This field identifies the date of the most recent authentication attempt by the SM. Demilitarized Zone as defined in RFC 2647. An Internet Protocol area outside of a firewall. See http://www.faqs.org/rfcs/rfc2647.html. Protocol defined in RFC 2131 that enables a device to be assigned a new IP address and TCP/IP parameters, including a default gateway, whenever the device reboots. Thus Dynamic Host Configuration Protocol reduces configuration time, conserves IP addresses, and allows modules to be moved to a different network within the Cyclone system. See http://www.faqs.org/rfcs/rfc2131.html. See also Static IP Address Assignment. Hardware address that the factory assigns to the module for identification in the Data Link layer interface of the Open Systems Interconnection system. This address serves as an electronic serial number. Same as MAC Address. ElementPack A license for Prizm management of a multi-point sector and covers the AP and up to 200 SMs, a backhaul link, or an Powerline LV link. Enable Engine ESN To turn on a feature in the module after the feature activation file has activated the module to use the feature. See also Activate. Bandwidth and Authentication Manager (BAM) interface to the AP and SMs. Unique sets of commands are available on this interface to manage parameters and user access. Distinguished from SSE. See also SSE. Electronic Serial Number. The hardware address that the factory assigns to the module for identification in the Data Link layer interface of the Open Systems Interconnection system. This address serves as an electronic serial number. Same as MAC Address. Issue2,November2007 Draft5forRegulatoryReview 515 Release8 ESNDataTable

/etc/services EthBusErrField EthernetProtocol FadeMargin Glossary Table in which each row identifies data about a single SM. In tab-

separated fields, each row stores the ESN, authentication key, and QoS information that apply to the SM. The operator can create and modify this table. This table is both an input to and an output from the Bandwidth and Authentication Manager (BAM) SQL database, and should be identically input to redundant BAM servers. File that stores telnet ports on the Bandwidth and Authentication Manager (BAM) server. This field displays how many Ethernet bus errors occurred on the Ethernet controller. Any of several IEEE standards that define the contents of frames that are transferred from one network element to another through Ethernet connections. The difference between strength of the received signal and the strength that the receiver requires for maintaining a reliable link. A higher fade margin is characteristic of a more reliable link. Standard operating margin. FCC Federal Communications Commission of the U.S.A. FeatureActivationKey Fieldprogrammable GateArray FileTransferProtocol FPGA FrameSpreading Software key file whose file name includes the ESN of the target Cyclone module. When installed on the module, this file activates the module to have the feature enabled or disabled in a separate operator action. Array of logic, relational data, and wiring data that is factory programmed and can be reprogrammed. Utility that transfers of files through TCP (Transport Control Protocol) between computing devices that do not operate on the same platform. Defined in RFC 959. See http://www.faqs.org/rfcs/rfc959.html. Field-programmable Gate Array. An array of logic, relational data, and wiring data that is factory programmed and can be reprogrammed. Transmission of a beacon in only frames where the receiver expects a beacon (rather than in every frame). This avoids interference from transmissions that are not intended for the receiver. FrameTimingPulse GatedField Toggle parameter that prevents or allows the module to continue to propagate GPS sync timing when the module no longer receives the timing. FreeSpacePathLoss Signal attenuation that is naturally caused by atmospheric conditions and by the distance between the antenna and the receiver. FresnelZone Space in which no object should exist that can attenuate, diffract, or reflect a transmitted signal before the signal reaches the target receiver. Issue2,November2007 Draft5forRegulatoryReview 516 Release8 FSK FTP GlobalPositioning System GPS GPS/3 Glossary Frequency Shift Keying, a variation of frequency modulation to transmit data, in which two or more frequencies are used. File Transfer Protocol, defined in RFC 959. Utility that transfers of files through TCP (Transport Control Protocol) between computing devices that do not operate on the same platform. See http://www.faqs.org/rfcs/rfc959.html. Network of satellites that provides absolute time to networks on earth, which use the time signal to synchronize transmission and reception cycles (to avoid interference) and to provide reference for troubleshooting activities. Global Positioning System. A network of satellites that provides absolute time to networks on earth, which use the time signal to synchronize transmission and reception cycles (to avoid interference) and to provide reference for troubleshooting activities. Third-from-left LED in the module. In the operating mode for an Access Point Module or Backhaul timing master, this LED is continuously lit as the module receives sync pulse. In the operating mode for a Subscriber Module or a Backhaul timing slave, this LED flashes on and off to indicate that the module is not registered. In the aiming mode for a Subscriber Module or a Backhaul timing slave, this LED is part of a bar graph that indicates the quality of the RF link. GUI Graphical user interface. HighpriorityChannel HTTP ICMP Channel that supports low-latency traffic (such as Voice over IP) over low-latency traffic (such as standard web traffic and file downloads). To recognize the latency tolerance of traffic, this channel reads the IPv4 Type of Service Low Latency bit. Hypertext Transfer Protocol, used to make the Internet resources available on the World Wide Web. Defined in RFC 2068. See http://www.faqs.org/rfcs/rfc2068.html. Internet Control Message Protocols defined in RFC 792, used to identify Internet Protocol (IP)-level problems and to allow IP links to be tested. See http://www.faqs.org/rfcs/rfc792.html. indiscardscountField How many inbound packets were discarded without errors that would have prevented their delivery to a higher-layer protocol. (Some of these packets may have been discarded to increase buffer space.) inerrorscountField How many inbound packets contained errors that prevented their delivery to a higher-layer protocol. innucastpktscount Field How many inbound non-unicast (subnetwork-broadcast or subnetwork-multicast) packets were delivered to a higher-layer protocol. Issue2,November2007 Draft5forRegulatoryReview 517 Release8 inoctetscountField Glossary How many octets were received on the interface, including those that deliver framing information. Intel A registered trademark of Intel Corporation. inucastpktscountField How many inbound subnetwork-unicast packets were delivered to a higher-layer protocol. inunknownprotoscount Field How many inbound packets were discarded because of an unknown or unsupported protocol. IP Internet Protocol defined in RFC 791. The Network Layer in the TCP/IP protocol stack. This protocol is applied to addressing, routing, and delivering, and re-assembling data packets into the Data Link layer of the protocol stack. See http://www.faqs.org/rfcs/rfc791.html. IPAddress 32-bit binary number that identifies a network element by both network and host. See also Subnet Mask. IPv4 ISM Jitter L2TPoverIPSec LateCollisionField Traditional version of Internet Protocol, which defines 32-bit fields for data transmission. Industrial, Scientific, and Medical Equipment radio frequency band, in the 900-MHz, 2.4-GHz, and 5.8-GHz ranges. Timing-based measure of the reception quality of a link. An acceptable link displays a jitter value between 0 and 4 for a 10-Mbps Backhaul timing slave in Release 4.0 and later, between 0 and 9 for a 20-Mbps Backhaul timing slave, or between 5 and 9 for any Subscriber Module or for a Backhaul timing slave in any earlier release. Level 2 Tunneling Protocol over IP Security. One of several virtual private network (VPN) implementation schemes. Regardless of whether Subscriber Modules have the Network Address Translation feature (NAT) enabled, they support VPNs that are based on this protocol. This field displays how many late collisions occurred on the Ethernet controller. A normal collision occurs during the first 512 bits of the frame transmission. A collision that occurs after the first 512 bits is considered a late collision. A late collision is a serious network problem because the frame being transmitted is discarded. A late collision is most commonly caused by a mismatch between duplex configurations at the ends of a link segment. LatencyTolerance Acceptable tolerance for delay in the transfer of data to and from a module. LineofSight Wireless path (not simply visual path) direct from module to module. The path that results provides both ideal aim and an ideal Fresnel zone. Linux A registered trademark of Linus Torvalds. Issue2,November2007 Draft5forRegulatoryReview 518 Release8 LNK/5 Glossary Furthest left LED in the module. In the operating mode, this LED is continuously lit when the Ethernet link is present. In the aiming mode for a Subscriber Module or a Backhaul timing slave, this LED is part of a bar graph that indicates the quality of the RF link. LogicalUnitID Final octet of the 4-octet IP address of the module. LOS LUID MACAddress Management InformationBase Master Line of sight. The wireless path (not simply visual path) direct from module to module. The path that results provides both ideal aim and an ideal Fresnel zone. Logical Unit ID. The final octet of the 4-octet IP address of the module. Media Access Control address. The hardware address that the factory assigns to the module for identification in the Data Link layer interface of the Open Systems Interconnection system. This address serves as an electronic serial number. Space that allows a program (agent) in the network to relay information to a network monitor about the status of defined variables

(objects). Designation that defines the role of a component relative to the role of another. This designation both applies to a Backhaul module that provides synchronization over the air to another Backhaul module

(a Backhaul timing slave) and applies to a Bandwidth and Authentication Manager (BAM) server whose SQL database is automatically copied onto a redundant BAM server (BAM slave). In each case, the master is not a product. Rather, the master is the role that results from deliberate configuration steps. MaximumInformation Rate The cap applied to the bandwidth of an SM or specified group of SMs. In the Cyclone implementation this is controlled by the Sustained Uplink Data Rate, Uplink Burst Allocation, Sustained Downlink Data Rate, and Downlink Burst Allocation parameters. MediaAccessControl Address Hardware address that the factory assigns to the module for identification in the Data Link layer interface of the Open Systems Interconnection system. This address serves as an electronic serial number. MIB MIR MySQL Management Information Base. Space that allows a program (agent) in the network to relay information to a network monitor about the status of defined variables (objects). See Maximum Information Rate. A registered trademark of MySQL AB Company in the United States, the European Union, and other countries. mysqladmin A command to set the administrator and associated password on the Bandwidth and Authentication Manager (BAM) server. Issue2,November2007 Draft5forRegulatoryReview 519 Release8 mysqlserver NAT NBI NEC NetBIOS Glossary Package group that enables the SQL Database Server application in the Red Hat Linux 9 operating system to provide SQL data for Bandwidth and Authentication Manager (BAM) operations. Network Address Translation defined in RFC 1631. A scheme that isolates Subscriber Modules from the Internet. See http://www.faqs.org/rfcs/rfc1631.html. See Northbound Interface. National Electrical Code. The set of national wiring standards that are enforced in the U.S.A. Protocol defined in RFC 1001 and RFC 1002 to support an applications programming interface in TCP/IP. This interface allows a computer to transmit and receive data with another host computer on the network. RFC 1001 defines the concepts and methods. RFC 1002 defines the detailed specifications. See http://www.faqs.org/rfcs/rfc1001.html and http://www.faqs.org/rfcs/rfc1002.html. NetworkAddress Translation Scheme that defines the Access Point Module as a proxy server to isolate registered Subscriber Modules from the Internet. Defined in RFC 1631. See http://www.faqs.org/rfcs/rfc1631.html. NetworkManagement Station Monitor device that uses Simple Network Management Protocol

(SNMP) to control, gather, and report information about predefined network variables (objects). NMS NorthboundInterface Object OptiPlex OSS Network Management Station. A monitor device that uses Simple Network Management Protocol (SNMP) to control, gather, and report information about predefined network variables (objects). The interface within Prizm to higher-level systems. This interface consists of a Simple Network Management Protocol (SNMP) agent for integration with a network management system (NMS); a Simple Object Access Protocol (SOAP) XML-based application programming interface (API) for web services that supports integration with an operations support systems (OSS) such as a customer relationship management (CRM), billing, or provisioning system; and console automation that allows such higher-level systems to launch and appropriately display the PrizmEMS management console in a custom-developed GUI. Network variable that is defined in the Management Information Base. A trademark of Dell, Inc. Operations support system, such as a customer relationship management (CRM), billing, or provisioning system. The application programming interface (API) for Prizm supports integrating Prizm with an OSS. Issue2,November2007 Draft5forRegulatoryReview 520 Release8 outdiscardscountField How many outbound packets were discarded without errors that would have prevented their transmission. (Some of these packets may have been discarded to increase buffer space.) Glossary outerrrorscountField How many outbound packets contained errors that prevented their transmission. outnucastpktscount Field How many packets for which the higher-level protocols requested transmission to a non-unicast (subnetwork-broadcast or subnetwork-

multicast) address. The number includes those that were discarded or not sent. outoctetscountField How many octets were transmitted out of the interface, including those that deliver framing information. outucastpktscount Field OverridePlug Pentium phpmysql How many packets for which the higher-level protocols requested transmission to a subnetwork-unicast address. The number includes those that were discarded or not sent. Device that enables the operator to regain control of a module that has been locked by the No Remote Access feature, the 802.3 Link Disable feature, or a password or IP address that cannot be recalled. This device can be either fabricated on site or ordered. A registered trademark of Intel Corporation. Package group that enables the Web Server application in the Red Hat Linux 9 operating system to provide data from the SQL Database Server application as PHP in the Bandwidth and Authentication Manager (BAM) GUI. PointtoPointProtocol Standards that RFC 1661 defines for data transmittal on the Internet. Also known as PPP or PTP. See http://www.faqs.org/rfcs/rfc1661.html. PowerControl Feature in Release 4.1 and later that allows the module to operate at less than 18 dB less than full power to reduce self-interference. PPTP Prizm Point to Point Tunneling Protocol. One of several virtual private network implementations. With the Network Address Translation

(NAT) feature enabled, Subscriber Modules do not support VPNs that are based on this protocol. With NAT disabled, they do support VPNs that are based on this protocol. The Cyclone software product that allows users to partition their entire Cyclone networks into criteria-based subsets and independently monitor and manage those subsets. Prizm Release 1.0 and later includes a Northbound Interface to higher-level systems. Prizm Release 2.0 and later integrates Cyclone Bandwidth and Authentication Manager (BAM) functionality and supports simple migration of a pre-existing authentication, bandwidth, and VLAN settings into the Prizm database. Issue2,November2007 Draft5forRegulatoryReview 521 Release8 ProtectiveEarth ProxyServer PTMP PTP QoS QualityofService Glossary Connection to earth (which has a charge of 0 volts). Also known as ground. Network computer that isolates another from the Internet. The proxy server communicates for the other computer, and sends replies to only the appropriate computer, which has an IP address that is not unique or not registered. Point-to-Multipoint Protocol defined in RFC 2178, which specifies that data that originates from a central network element can be received by all other network elements, but data that originates from a non-central network element can be received by only the central network element. See http://www.faqs.org/rfcs/rfc2178.html. Point-to-Point Protocol. The standards that RFC 1661 defines for data transmittal on the Internet. See http://www.faqs.org/rfcs/rfc1661.html. Quality of Service. A frame field that Bandwidth and Authentication Manager (BAM) provides to the AP and SM the sustained data rates and burst data limits of the SM. The format of this field is 64 hexadecimal characters of 0 to 9 and a to f. The BAM SQL database expresses this field as five contiguous subfields. A frame bit that Bandwidth and Authentication Manager (BAM) provides to the AP and SM the sustained data rates and burst data limits of the SM. The format of this field is 64 hexadecimal characters of 0 to 9 and a to f. The BAM SQL database expresses this field as five contiguous subfields. Also known as QoS. QuickStart Interface page that requires minimal configuration for initial module operation. RadioSignalStrength Indicator Relative measure of the strength of a received signal. An acceptable link displays an Radio Signal Strength Indicator (RSSI) value of greater than 700. RandomNumber Number that the Bandwidth and Authentication Manager (BAM) generates, invisible to both the SM and the network operator, to send to the SM as a challenge against an authentication attempt. Reader Recharging RedHat A registered trademark of Adobe Systems, Incorporated. Resumed accumulation of data in available data space (buckets). See Buckets. A registered trademark of Red Hat, Inc. Issue2,November2007 Draft5forRegulatoryReview 522 Release8 Reflection RegistrationsMIB replm repls RES Glossary Change of direction and reduction of amplitude of a signal that encounters an object larger than the wavelength. Reflection may cause an additional copy of the wavelength to arrive at after the original, unobstructed wavelength arrives. This causes partial cancellation of the signal and may render the link unacceptable. However, in some instances where the direct signal cannot be received, the reflected copy may be received and render an otherwise unacceptable link acceptable. Management Information Base file that defines registrations for global items such as product identities and product components. See also Management Information Base. A command that sets up the database replication process on a Bandwidth and Authentication Manager (BAM) master server, uses SFTP to copy both the database and the repl-s script to a BAM slave server, and remotely executes the repl-s script on the BAM slave server. See Master, Slave, repl-s, Secure Shell, and SFTP. A command that sets up the database replication process on a Bandwidth and Authentication Manager (BAM) slave server. See Master, Slave, and repl-m. Result. A field in the data that the cmd show esn command generates from the SQL database in the Bandwidth and Authentication Manager (BAM) server. RetransLimitExpField This field displays how many times the retransmit limit has expired. RF RJ11 RJ45 Router RPM rpm RSSI Radio frequency. How many times each second a cycle in the antenna occurs, from positive to negative and back to positive amplitude. Standard cable that is typically used for telephone line or modem connection. Standard cable that is typically used for Ethernet connection. This cable may be wired as straight-through or as crossover. Later Cyclone modules auto-sense whether the cable is straight-through or crossover. Network element that uses the logical (IP) address of another to pass data to only the intended recipient. Compare to Switch and Bridge. Red Hat Package Manager. A command that the Linux operating system accepts to identify the version of Linux software that operates on the Bandwidth and Authentication Manager (BAM) server. Radio Signal Strength Indicator. A relative measure of the strength of a received signal. An acceptable link displays an RSSI value of greater than 700. Issue2,November2007 Draft5forRegulatoryReview 523 Release8 RxBabErrField RxOverrunField SDK SecureShell Selfinterference SES/2 SessionKey Glossary This field displays how many receiver babble errors occurred. This field displays how many receiver overrun errors occurred on the Ethernet controller. PrizmEMS Software Development Kit (SDK)the document that provides server administrator tasks, GUI developer information for console automation that allows higher-level systems to launch and appropriately display the Prizm management console. The SDK also describes the how to define new element types and customize the Details views. A trademark of SSH Communications Security. Interference with a module from another module in the same network. Third-from-right LED in the module. In the Access Point Module and Backhaul timing master, this LED is unused. In the operating mode for a Subscriber Module or a Backhaul timing slave, this LED flashes on and off to indicate that the module is not registered. In the aiming mode for a Subscriber Module or a Backhaul timing slave, this LED is part of a bar graph that indicates the quality of the RF link. Software key that the SM and Bandwidth and Authentication Manager

(BAM) separately calculate based on that both the authentication key

(or the factory-set default key) and the random number. BAM sends the session key to the AP. Neither the subscriber nor the network operator can view this key. See also Random Number. SFTP Secure File Transfer Protocol. SimpleNetwork ManagementProtocol Standard that is used for communications between a program (agent) in the network and a network management station (monitor). Defined in RFC 1157. See http://www.faqs.org/rfcs/rfc1157.html. skey Slave Software key that correlates to the random number that the Bandwidth and Authentication Manager (BAM) server generates and sends in a challenge through the AP to the SM. The network operator can create and, at some security risk, send this key over the air to the SM. The SQL database in the BAM server correlates this key to QoS information about the SM. The format of this key is 32 hexadecimal characters of 0 to 9 and a to f. This key must be unique to the individual SM. Also known as authentication key. Designation that defines the role of a component relative to the role of another. This designation both applies to a Backhaul slave that receives synchronization over the air from another Backhaul module

(a Backhaul timing master) and applies to a redundant Bandwidth and Authentication Manager (BAM) server whose SQL database is automatically overwritten by a copy from the primary BAM server

(BAM master). In each case, the slave is not a product. Rather, the slave is the role that results from deliberate configuration steps. Issue2,November2007 Draft5forRegulatoryReview 524 Release8 SM SMMIB SNMP SNMPTrap SOAP SSE StandardOperating Margin StaticIPAddress Assignment su SubnetMask Glossary Customer premises equipment (CPE) device that extends network or Internet services by communication with an Access Point Module or an Access Point cluster. Management Information Base file that defines objects that are specific to the Subscriber Module or Backhaul timing slave. See also Management Information Base. Simple Network Management Protocol, defined in RFC 1157. A standard that is used for communications between a program (agent) in the network and a network management station (monitor). See http://www.faqs.org/rfcs/rfc1157.html. Capture of information that informs the network monitor through Simple Network Management Protocol of a monitored occurrence in the module. Simple Object Access Protocol (SOAP). The protocol that the Northbound Interface in Prizm uses to support integration of Prizm with an operations support systems (OSS) such as a customer relationship management (CRM), billing, or provisioning system Bandwidth and Authentication Manager (BAM) interface to the SQL server. Unique sets of commands are available on this interface to manage the BAM SQL database and user access. Distinguished from Engine. See also Engine. See Fade Margin. Assignment of Internet Protocol address that can be changed only manually. Thus static IP address assignment requires more configuration time and consumes more of the available IP addresses than DHCP address assignment does. RFC 2050 provides guidelines for the static allocation of IP addresses. See http://www.faqs.org/rfcs/rfc2050.html. See also DHCP. A command that opens a Linux operating system session for the user root. 32-bit binary number that filters an IP address to reveal what part identifies the network and what part identifies the host. The number of subnet mask bits that are set to 1 indicates how many leading bits of the IP address identify the network. The number of subnet mask bits that are set 0 indicate how many trailing bits of the IP address identify the host. SubscriberModule Customer premises equipment (CPE) device that extends network or Internet services by communication with an Access Point Module or an Access Point cluster. SustainedDataRate Preset rate limit of data transfer. Issue2,November2007 Draft5forRegulatoryReview 525 Release8 Switch SYN/1 Sync TCP tcp TDD TDMA telnet TextualConventions MIB TimeofLast Transaction TLT Glossary Network element that uses the port that is associated with the physical address of another to pass data to only the intended recipient. Compare to Bridge and Router. Second-from-right LED in the module. In the Access Point Module or Backhaul timing master, as in a registered Subscriber Module or Backhaul timing slave, this LED is continuously lit to indicate the presence of sync. In the operating mode for a Subscriber Module or Backhaul timing slave, this LED flashes on and to indicate that the module is not registered. In the aiming mode for a Subscriber Module or a Backhaul timing slave, this LED is part of a bar graph that indicates the quality of the RF link. GPS (Global Positioning System) absolute time, which is passed from one module to another. Sync enables timing that prevents modules from transmitting or receiving interference. Sync also provides correlative time stamps for troubleshooting efforts. Alternatively known as Transmission Control Protocol or Transport Control Protocol. The Transport Layer in the TCP/IP protocol stack. This protocol is applied to assure that data packets arrive at the target network element and to control the flow of data through the Internet. Defined in RFC 793. See http://www.faqs.org/rfcs/rfc793.html. Transport Control type of port. The Cyclone system uses Port 3306:tcp for MySQL database communications, Port 9080:tcp for SSE telnet communications, and Port 9090:tcp for Engine telnet communications. Time Division Duplexing. Time Division Multiple Access. Utility that allows a client computer to update a server. A firewall can prevent the use of the telnet utility to breach the security of the server. See http://www.faqs.org/rfcs/rfc818.html, http://www.faqs.org/rfcs/rfc854.html and http://www.faqs.org/rfcs/rfc855.html. Management Information Base file that defines Cyclone system-

specific textual conventions. See also Management Information Base. A field in the data that the cmd show esn command generates from data in the SQL database in the Bandwidth and Authentication Manager (BAM) server. This field identifies the time of day of the most recent authentication attempt by the SM. Expressed in the database output as TLT. Time of last transaction. A field in the data that the cmd show esn command generates from data in the SQL database in the Bandwidth and Authentication Manager (BAM) server. This field identifies the time of day of the most recent authentication attempt by the SM. Issue2,November2007 Draft5forRegulatoryReview 526 Release8 TNAF TNAR Tokens TOS Glossary Total number of authentication requests failed. A field in the data that the cmd show esn command generates from the SQL database in the Bandwidth and Authentication Manager (BAM) server. This field indicates how many times the SM (identified by ESN in the related data) attempted to authenticate but was denied by BAM. Total number of authentication requests. A field in the data that the cmd show esn command generates from the SQL database in the Bandwidth and Authentication Manager (BAM) server. This field indicates how many times the SM (identified by ESN in the related data) attempted to authenticate, regardless of whether the attempt succeeded. Theoretical amounts of data. See also Buckets. 8-bit field in that prioritizes data in a IP transmission. See http://www.faqs.org/rfcs/rfc1349.html. TxUnderrunField This field displays how many transmission-underrun errors occurred on the Ethernet controller. UDP udp UNII VID VLAN VPN User Datagram Protocol. A set of Network, Transport, and Session Layer protocols that RFC 768 defines. These protocols include checksum and address information but does not retransmit data or process any errors. See http://www.faqs.org/rfcs/rfc768.html. User-defined type of port. Unlicensed National Information Infrastructure radio frequency band, in the 5.1-GHz through 5.8-GHz ranges. VLAN identifier. See VLAN. Virtual local area network. An association of devices through software that contains broadcast traffic, as routers would, but in the switch-level protocol. Virtual private network for communication over a public network. One typical use is to connect remote employees, who are at home or in a different city, to their corporate network over the Internet. Any of several VPN implementation schemes is possible. With the Network Address Translation feature (NAT) enabled, SMs on Cyclone System Release 4.2 or later support L2TP over IPSec (Level 2 Tunneling Protocol over IP Security) VPNs, but do not support PPTP (Point to Point Tunneling Protocol) VPNs. With NAT disabled, SMs support all types of VPNs. Issue2,November2007 Draft5forRegulatoryReview 527