FCC ID: ABZ89FT7623 5400xxyyzzab

Canopy System Release 8 User Guide Sys8-UG-en Issue 2 February 2007 includes Planning Guide Installation and Configuration Guide Operations Guide Reference Information Draft 3 - for Regulatory Review R Notices See the following information:

important regulatory and legal notices in Section 36 on Page 489. personal safety guidelines in Section 15 on Page 169. Trademarks, Product Names, and Service Names MOTOROLA, the stylized M Logo and all ot her trademarks indicated as such herein are trademarks of Motorola, Inc. Reg. U.S. Pat & Tm. Office. Canopy is a registered trademark and MOTOwi4 is a trademark of Motorola, 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 Motorola, Inc. All rights reserved. http://www.motorola.com/canopy TABLE OF SECTIONS Guide To This User Guide Overview of Canopy Networks Planning Guide Installation and Configuration Guide Operations Guide Reference Information Glossary 31 43 127 167 363 485 501 Draft 3 - for Regulatory Review TABLE OF CONTENTS UIDE TTO O TT HIS HIS UU SER SER GGUIDEUIDE ......................... ........................ 3131 GGUIDE 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 MOTOwi4 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 Interpreting Typeface and Other Conventions ................................................ 41 2.2 2.3 Getting Additional Help................................................................................... 42 2.4 Sending Feedback ......................................................................................... 42 ETWORKS ................ VERVIEW OF CCANOANOPY PY NNETWORKS

................ 4343 OOVERVIEW OF 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 Canopy Access Point Module............................................................................. 49 5.1.2 Advantage Access Point Module ....................................................................... 49 5.1.3 Access Point Cluster ........................................................................................... 50 5.1.4 Canopy Subscriber Module ................................................................................ 50 5.1.5 Advantage Subscriber Module ........................................................................... 50 Draft 3 - for Regulatory Review 5.1.6 Canopy Lite Subscriber Module ......................................................................... 50 5.1.7 900-MHz AP and SM .......................................................................................... 51 5.1.8 Backhaul Module................................................................................................. 52 5.1.9 OFDM Series Backhaul Modules ....................................................................... 52 5.1.10 Power Indoor Units for OFDM Series Backhaul Modules .............................. 53 5.1.11 Radio Adjustable Power Capabilities ............................................................... 54 5.1.12 T1/E1 Multiplexer............................................................................................... 54 5.1.13 Cluster Management Module-2 (Part 1008CK-2) ........................................... 55 5.1.14 Cluster Management Module micro (Part 1070CK)........................................ 56 5.1.15 GPS Antenna..................................................................................................... 56 5.1.16 Surge Suppressor (Part 300SS)....................................................................... 57 5.1.17 Accessory Components .................................................................................... 57 5.2 Frequency Band Ranges................................................................................ 61 5.3 Canopy Product Comparisons........................................................................ 62 5.3.1 Canopy Product Applications ............................................................................. 62 5.3.2 Link Performance and Encryption Comparisons............................................... 63 5.3.3 Cluster Management Product Comparison ....................................................... 67 5.4 Antennas for Connection to 900-MHz Modules .............................................. 68 5.4.1 Certified Connectorized Flat Panel Antennas ................................................... 68 5.4.2 Third-party Certified Connectorized Flat Panel Antenna.................................. 68 5.5 Adjunctive Software Products......................................................................... 69 5.6 Bandwidth and Authentication Manager ......................................................... 70 5.7 Prizm.............................................................................................................. 70 5.7.1 Network Definition and Element Discovery ....................................................... 70 5.7.2 Monitoring and Fault Management .................................................................... 71 5.7.3 Element Management......................................................................................... 71 5.7.4 BAM Subsystem in Prizm ................................................................................... 72 5.7.5 Northbound Interface .......................................................................................... 72 5.8 License Management ..................................................................................... 72 5.9 Specifications and Limitations ........................................................................ 74 5.9.1 Radios .................................................................................................................. 74 5.9.2 Cluster Management Products........................................................................... 75 5.9.3 300SS and 600SS Surge Suppressors ............................................................. 76 6 Differentiating Among Components...................................................................... 77 Interpreting Model (Part) Number ................................................................... 77 6.1 6.2 Sorted Model (Part) Numbers......................................................................... 80 6.3 Interpreting Electronic Serial Number (ESN) .................................................. 81 6.4 Finding the Model (Part) Number and ESN .................................................... 81 7 Canopy Link Characteristics .................................................................................. 83 7.1 Understanding Bandwidth Management......................................................... 83 7.1.1 Downlink Frame Contents .................................................................................. 83 7.1.2 Uplink Frame Contents ....................................................................................... 83 7.1.3 Frame Structure................................................................................................... 84 7.1.4 Media Access Control and AP Capacity ............................................................ 85 7.1.5 Canopy Slot Usage ............................................................................................. 85 7.1.6 Data Transfer Capacity ....................................................................................... 85 7.1.7 Maximum Information Rate (MIR) Parameters ................................................. 85 7.1.8 Committed Information Rate............................................................................... 87 7.1.9 Bandwidth from the SM Perspective.................................................................. 88 7.1.10 Interaction of Burst Allocation and Sustained Data Rate Settings................. 88 7.1.11 High-priority Bandwidth..................................................................................... 88 7.1.12 Hardware Scheduling........................................................................................ 90 7.1.13 2X Operation...................................................................................................... 91 7.2 Understanding Synchronization...................................................................... 94 7.2.1 GPS Synchronization .......................................................................................... 94 7.2.2 Passing Sync in a Single Hop ............................................................................ 96 7.2.3 Passing Sync in an Additional Hop .................................................................... 97 8 Meeting Link Requirements ................................................................................... 99 8.1 AP-SM Links .................................................................................................. 99 8.2 BH-BH Links................................................................................................. 100 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 Draft 3 - for Regulatory Review 11.1 Understanding RF Fundamentals ............................................................... 117 11.2 Understanding IP Fundamentals................................................................. 117 11.3 Acquiring a Canopy 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 ........................... 117 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 ................................................................... 120 11.4 Acquiring a Canopy 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 Canopy Training Options........................................................... 125 11.6 Attending On-line Knowledge Sessions ...................................................... 125 UIDE ................................ ....................................... PPLANNING LANNING GGUIDE

........ 127127 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 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 (Dynamic Frequency Selection DFS) ................................................................................................................. 132 12.3 Using Jitter to Check Received Signal Quality ............................................ 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........................................................................................... 137 12.5.4 5.4-GHz Channels........................................................................................... 138 12.5.5 5.7-GHz Channels........................................................................................... 139 12.5.6 Channels Available for OFDM Backhaul Modules........................................ 140 12.5.7 Example Channel Plans for AP Clusters ....................................................... 140 12.5.8 Multiple Access Points Clusters ..................................................................... 141 12.6 Selecting Sites for Network Elements ......................................................... 142 12.6.1 Resources for Maps and Topographic Images ............................................. 143 12.6.2 Surveying Sites................................................................................................ 143 12.6.3 Assuring the Essentials................................................................................... 144 12.6.4 Finding the Expected Coverage Area............................................................ 144 12.6.5 Clearing the Radio Horizon............................................................................. 145 12.6.6 Calculating the Aim Angles............................................................................. 145 12.7 Collocating Canopy Modules ...................................................................... 146 12.8 Deploying a Remote AP ............................................................................. 147 12.8.1 Remote AP Performance................................................................................ 148 12.8.2 Example Use Case for RF Obstructions........................................................ 148 12.8.3 Example Use Case for Passing Sync ............................................................ 149 12.8.4 Physical Connections Involving the Remote AP ........................................... 150 12.9 Diagramming Network Layouts................................................................... 151 12.9.1 Accounting for Link Ranges and Data Handling Requirements................... 151 12.9.2 Avoiding Self Interference............................................................................... 151 12.9.3 Avoiding Other Interference............................................................................ 153 Draft 3 - for Regulatory Review 13.1.1 13 Engineering Your IP Communications .............................................................. 155 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........................................................ 161 13.4.1 Address Resolution Protocol .......................................................................... 162 13.4.2 Allocating Subnets........................................................................................... 162 13.4.3 Selecting Non-routable IP Addresses ............................................................ 162 14 Engineering VLANs............................................................................................. 165 14.1 SM Membership in VLANs.......................................................................... 165 14.2 Priority on VLANs (802.1p) ......................................................................... 166 ONFIGURATION GGUIDEUIDE 167167 II NSTALLATION AND NSTALLATION AND CCONFIGURATION 15 Avoiding Hazards................................................................................................ 169 15.1 Preventing Overexposure to RF Energy ..................................................... 169 15.1.1 Details of Calculations for Separation Distances and Power Compliance Margins............................................................................................................. 169 15.2 Grounding Canopy Equipment.................................................................... 171 15.2.1 Grounding Infrastructure Equipment.............................................................. 171 15.2.2 Grounding Canopy 30/60- and 150/300-Mbps Backhaul Modules.............. 172 15.2.3 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 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 ........................................... 200 16.3.8 General Status Tab of the AP......................................................................... 201 16.3.9 Concluding the Test of Point-to-Multipoint Links........................................... 203 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 ...................................................................................... 206 16.4.3 Beginning the Test of Point-to-Point Links .................................................... 210 16.4.4 Continuing the Test of Point-to-Point Links ................................................... 212 16.4.5 General Status Tab of the BHM ..................................................................... 213 16.4.6 Concluding the Test of Point-to-Point Links .................................................. 215 16.4.7 Setting up a CMMmicro .................................................................................. 216 16.4.8 Status Page of the CMMmicro ....................................................................... 221 16.4.9 Configuration Page of the CMMmicro............................................................ 224 16.4.10 Configuring Modules for Connection to CMMmicro...................................... 231 16.4.11 Event Log Page of the CMMmicro ................................................................. 231 16.4.12 GPS Status Page of the CMMmicro .............................................................. 231 16.4.13 Port MIB Page of the CMMmicro ................................................................... 232 17 Preparing Components for Deployment............................................................ 233 17.1 Correlating Component-specific Information ............................................... 233 17.2 Ensuring Continuing Access to the Modules............................................... 233 Draft 3 - for Regulatory Review 18 Configuring for the Destination.......................................................................... 235 18.1 Configuring an AP for the Destination......................................................... 235 18.1.1 General Tab of the AP .................................................................................... 235 18.1.2 IP Tab of the AP .............................................................................................. 239 18.1.3 Radio Tab of the AP........................................................................................ 241 18.1.4 SNMP Tab of the AP....................................................................................... 246 18.1.5 Quality of Service (QoS) Tab of the AP ......................................................... 249 18.1.6 Security Tab of the AP .................................................................................... 251 18.1.7 VLAN Tab of the AP........................................................................................ 253 18.1.8 VLAN Membership Tab of the AP .................................................................. 255 18.1.9 DiffServe Tab of the AP .................................................................................. 256 18.1.10 Unit Settings Tab of the AP ............................................................................ 258 18.2 Configuring an SM for the Destination ........................................................ 259 18.2.1 General Tab of the SM.................................................................................... 260 18.2.2 NAT and IP Tabs of the SM with NAT Disabled ........................................... 262 18.2.3 NAT and IP Tabs of the SM with NAT Enabled ............................................ 268 18.2.4 Radio Tab of the SM ....................................................................................... 273 18.2.5 SNMP Tab of the SM ...................................................................................... 276 18.2.6 Quality of Service (QoS) Tab of the SM ........................................................ 279 18.2.7 Security Tab of the SM ................................................................................... 282 18.2.8 VLAN Tab of the SM ....................................................................................... 284 18.2.9 VLAN Membership Tab of the SM ................................................................. 286 18.2.10 DiffServe Tab of the SM.................................................................................. 287 18.2.11 Protocol Filtering Tab of the SM..................................................................... 289 18.2.12 NAT Port Mapping Tab of the SM .................................................................. 290 18.2.13 Unit Settings Tab of the SM............................................................................ 291 18.3 Setting the Configuration Source ................................................................ 292 18.4 Configuring a BH Timing Master for the Destination ................................... 294 18.4.1 General Tab of the BHM................................................................................. 295 18.4.2 IP Tab of the BHM........................................................................................... 298 18.4.3 Radio Tab of the BHM..................................................................................... 300 18.4.4 SNMP Tab of the BHM ................................................................................... 303 18.4.5 Security Tab of the BHM................................................................................. 306 18.4.6 DiffServe Tab of the BHM............................................................................... 308 18.4.7 Unit Settings Tab of the BHM......................................................................... 310 18.5 Configuring a BH Timing Slave for the Destination ..................................... 312 18.5.1 General Tab of the BHS.................................................................................. 312 18.5.2 IP Tab of the BHS ........................................................................................... 315 18.5.3 Radio Tab of the BHS ..................................................................................... 316 18.5.4 SNMP Tab of the BHS .................................................................................... 319 18.5.5 Quality of Service (QoS) Tab of the BHS ...................................................... 321 18.5.6 Security Tab of the BHS ................................................................................. 322 18.5.7 DiffServe Tab of the BHS ............................................................................... 324 18.5.8 Unit Settings Tab of the BHS.......................................................................... 325 18.6 Adjusting Transmitter Output Power ........................................................... 326 Installing Components........................................................................................ 331 19.1 PDA Access to Canopy Modules ................................................................ 331 Installing an AP........................................................................................... 334 19.2 19.3 Installing a Connectorized Flat Panel Antenna............................................ 335 Installing a GPS Antenna............................................................................ 336 19.4 19.4.1 Recommended Materials for Cabling the GPS Antenna .............................. 337 19.4.2 Cabling the GPS Antenna............................................................................... 337 Installing a CMM2....................................................................................... 337 19.5.1 CMM2 Installation Temperature Range......................................................... 337 19.5.2 Recommended Tools for Mounting a CMM2 ................................................ 337 19.5.3 Mounting a CMM2 ........................................................................................... 338 19.5.4 Cabling a CMM2.............................................................................................. 338 19.5.5 Verifying CMM2 Connections ......................................................................... 342 Installing a CMMmicro ................................................................................ 342 19.6.1 CMMmicro Temperature Range..................................................................... 343 19.6.2 Recommended Tools for Mounting a CMMmicro ......................................... 343 19.6.3 Mounting a CMMmicro.................................................................................... 343 19.6.4 Installing the Power Supply for the CMMmicro ............................................. 343 19.6.5 Cabling a CMMmicro....................................................................................... 344 19.6.6 Verifying CMMmicro Connections.................................................................. 345 19.7 Installing an SM .......................................................................................... 346 19.8 Verifying an AP-SM Link............................................................................. 349 19.9 Installing a Reflector Dish ........................................................................... 352 19.9.1 Both Modules Mounted at Same Elevation ................................................... 352 19.9.2 Modules Mounted at Different Elevations...................................................... 353 19.5 19.6 Draft 3 - for Regulatory Review 19

..................................... PERATIONS GGUIDEUIDE ................................ 19.9.3 Mounting Assembly ......................................................................................... 353 19.10 Installing a BH Timing Master ..................................................................... 354 19.11 Installing a BH Timing Slave ....................................................................... 356 19.12 Upgrading a BH Link to BH20..................................................................... 357 19.13 Verifying a BH Link ..................................................................................... 357 20 Verifying System Functionality .......................................................................... 361 OOPERATIONS

..... 363363 21 Growing Your Network ....................................................................................... 365 21.1 Monitoring the RF Environment .................................................................. 365 21.1.1 Spectrum Analyzer .......................................................................................... 365 21.1.2 Graphical Spectrum Analyzer Display ........................................................... 365 21.1.3 Using the AP as a Spectrum Analyzer........................................................... 366 21.2 Considering Software Release Compatibility .............................................. 367 21.2.1 Designations for Hardware in Radios ............................................................ 367 21.2.2 CMMmicro Software and Hardware Compatibility ........................................ 368 21.2.3 MIB File Set Compatibility............................................................................... 368 21.3 Redeploying Modules ................................................................................. 369 21.3.1 Wiring to Extend Network Sync...................................................................... 369 22 Securing Your Network....................................................................................... 371 22.1 Isolating APs from the Internet.................................................................... 371 22.2 Encrypting Canopy Radio Transmissions ................................................... 371 22.2.1 DES Encryption ............................................................................................... 371 22.2.2 AES Encryption ............................................................................................... 371 22.2.3 AES-DES Operability Comparisons............................................................... 372 22.3 Managing Module Access by Passwords.................................................... 373 22.3.1 Adding a User for Access to a Module .......................................................... 373 22.3.2 Overriding Forgotten IP Addresses or Passwords on AP, SM, or BH......... 375 22.3.3 Overriding Forgotten IP Addresses or Passwords on CMMmicro ............... 377 22.4 Requiring SM Authentication ...................................................................... 377 22.5 Filtering Protocols and Ports....................................................................... 378 22.5.1 Port Filtering with NAT Enabled ..................................................................... 378 22.5.2 Protocol and Port Filtering with NAT Disabled .............................................. 378 22.6 Encrypting Downlink Broadcasts................................................................. 380 22.7 Isolating SMs .............................................................................................. 380 22.8 Filtering Management through Ethernet...................................................... 381 22.9 Allowing Management from Only Specified IP Addresses........................... 381 22.10 Configuring Management IP by DHCP........................................................ 381 23 Managing Bandwidth and Authentication ......................................................... 383 23.1 Managing Bandwidth without BAM ............................................................. 383 23.2 Bandwidth and Authentication Manager (BAM) Services and Features ...... 383 23.2.1 Bandwidth Manager Capability....................................................................... 383 23.2.2 Authentication Manager Capability ................................................................ 385 24 Managing the Network From a Management Station (NMS) ............................ 387 24.1 Roles of Hardware and Software Elements ................................................ 387 24.1.1 Role of the Agent............................................................................................. 387 24.1.2 Role of the Managed Device .......................................................................... 387 24.1.3 Role of the NMS .............................................................................................. 387 24.1.4 Dual Roles for the NMS .................................................................................. 387 24.1.5 Simple Network Management Protocol (SNMP) Commands ...................... 387 24.1.6 Traps from the Agent ...................................................................................... 388 24.1.7 AP SNMP Proxy to SMs ................................................................................. 388 24.2 Management Information Base (MIB) ......................................................... 388 24.2.1 Cascading Path to the MIB............................................................................. 388 24.2.2 Object Instances.............................................................................................. 389 24.2.3 Management Information Base Systems and Interface (MIB-II).................. 389 24.2.4 Canopy Enterprise MIB................................................................................... 390 24.3 Configuring Modules for SNMP Access ...................................................... 391 24.4 Objects Defined in the Canopy Enterprise MIB ........................................... 391 24.4.1 AP, SM, and BH Objects................................................................................. 391 24.4.2 AP and BH Timing Master Objects ................................................................ 394 24.4.3 SM and BH Timing Slave Objects.................................................................. 398 24.4.4 CMMmicro Objects.......................................................................................... 401 24.5 Objects Defined in the Canopy OFDM BH Module MIB .............................. 404 24.6 Objects Supported in the Canopy 30/60-Mbps BH...................................... 405 24.7 Objects Supported in the Canopy 150/300-Mbps BH.................................. 405 Interface Designations in SNMP ................................................................. 405 24.8 Draft 3 - for Regulatory Review 24.9 Traps Provided in the Canopy Enterprise MIB ............................................ 406 24.10 Traps Provided in the Canopy 30/60-Mbps BH Module MIB ....................... 406 24.11 Traps Provided in the Canopy 150/300-Mbps BH Module MIB ................... 406 24.12 MIB Viewers ............................................................................................... 407 25 Using the Canopy Network Updater Tool (CNUT)............................................. 409 25.1 CNUT Functions ......................................................................................... 409 25.2 Network Element Groups............................................................................ 409 25.3 Network Layers........................................................................................... 409 25.4 Script Engine .............................................................................................. 410 25.5 Software Dependencies for CNUT.............................................................. 410 25.6 CNUT Download......................................................................................... 410 26 Using Informational Tabs in the GUI.................................................................. 411 26.1 Viewing General Status (All) ....................................................................... 411 26.2 Viewing Session Status (AP, BHM) ............................................................ 411 26.3 Viewing Remote Subscribers (AP, BHM) .................................................... 412 26.4 Interpreting Messages in the Event Log (All) .............................................. 412 26.4.1 Time and Date Stamp ..................................................................................... 412 26.4.2 Event Log Data Collection .............................................................................. 412 26.4.3 Messages that Flag Abnormal Events ........................................................... 414 26.4.4 Messages that Flag Normal Events ............................................................... 414 26.5 Viewing the Network Interface Tab (All) ...................................................... 415 26.6 Interpreting Radio Statistics in the Scheduler Tab (All) ............................... 416 26.7 Viewing the List of Registration Failures (AP, BHM) ................................... 417 26.8 Interpreting Data in the Bridging Table (All) ................................................ 418 26.9 Translation Table (SM) ............................................................................... 419 26.10 Interpreting Data in the Ethernet Tab (All)................................................... 419 26.11 Interpreting RF Control Block Statistics in the Radio Tab (All) .................... 422 26.12 Interpreting Data in the VLAN Tab (AP, SM)............................................... 423 26.13 Data VC (All)............................................................................................... 425 26.14 Filter (SM)................................................................................................... 426 26.15 NAT Stats (SM) .......................................................................................... 427 26.15.1 NAT DHCP Statistics (SM) ............................................................................. 428 26.15.2 Interpreting Data in the GPS Status Page (AP, BHM).................................. 429 27 Using Tools in the GUI........................................................................................ 431 27.1 Using the Spectrum Analyzer Tool (SM, BHS)............................................ 431 27.2 Using the Alignment Tool (SM, BHS).......................................................... 431 27.3 Using the Link Capacity Test Tool (All) ....................................................... 434 27.4 Using the AP Evaluation or BHM Evaluation Tool (SM, BHS) ..................... 436 27.5 Using the Frame Calculator Tool (All) ......................................................... 440 27.6 Using the SM Configuration Tool (AP, BHM) .............................................. 445 27.7 Using the BER Results Tool (SM, BHS)...................................................... 446 28 Maintaining Your Canopy Software ................................................................... 447 28.1 History of System Software Upgrades ........................................................ 447 28.1.1 Canopy Release 8.1 Features........................................................................ 447 28.1.2 Canopy Release 8.1 Fixes.............................................................................. 447 28.2 History of CMMmicro Software Upgrades ................................................... 447 28.3 Typical Contents of Release Notes............................................................. 447 28.4 Typical Upgrade Process............................................................................ 447 28.4.1 Downloading Software and Release Notes................................................... 448 29 Rebranding Module Interface Screens .............................................................. 449 30 Toggling Remote Access Capability.................................................................. 453 30.1 Denying All Remote Access........................................................................ 453 30.2 Reinstating Remote Access Capability ....................................................... 453 31 Setting Up a Protocol Analyzer on Your Canopy Network............................... 455 31.1 Analyzing Traffic at an SM.......................................................................... 455 31.2 Analyzing Traffic at an AP or BH with No CMM .......................................... 456 31.3 Analyzing Traffic at an AP or BH with a CMM ............................................. 456 31.4 Example of a Protocol Analyzer Setup for an SM ....................................... 457 32 Troubleshooting.................................................................................................. 465 32.1 General Planning for Troubleshooting ........................................................ 465 32.2 General Fault Isolation Process.................................................................. 465 32.3 Questions to Help Isolate the Problem........................................................ 466 32.4 Secondary Steps ........................................................................................ 466 32.5 Procedures for Troubleshooting.................................................................. 467 32.5.1 Module Has Lost or Does Not Establish Connectivity .................................. 467 Draft 3 - for Regulatory Review 32.5.2 NAT/DHCP-configured SM Has Lost or Does Not Establish Connectivity.. 468 32.5.3 SM Does Not Register to an AP..................................................................... 470 32.5.4 BHS Does Not Register to the BHM .............................................................. 471 32.5.5 Module Has Lost or Does Not Gain Sync...................................................... 472 32.5.6 Module Does Not Establish Ethernet Connectivity ....................................... 473 32.5.7 Module Does Not Power Up ........................................................................... 474 32.5.8 Power Supply Does Not Produce Power....................................................... 474 32.5.9 CMM2 Does Not Power Up ............................................................................ 475 32.5.10 CMM2 Does Not Pass Proper GPS Sync to Connected Modules............... 475 32.5.11 Module Software Cannot be Upgraded ......................................................... 476 32.5.12 Module Functions Properly, Except Web Interface Became Inaccessible.. 476 33 Obtaining Technical Support ............................................................................. 477 34 Getting Warranty Assistance ............................................................................. 483

............................ 485485 RREFERENCE EFERENCE IINFORMATION 35 Administering Modules through telnet Interface.............................................. 487 36 Legal and Regulatory Notices............................................................................ 489 36.1 Important Note on Modifications ................................................................. 489 36.2 National and Regional Regulatory Notices.................................................. 489 NFORMATION............................ 36.2.1 U.S. Federal Communication Commission (FCC) and Industry Canada (IC) Notification ....................................................................................................... 489 36.2.2 Regulatory Requirements for CEPT Member States (http://www.cept.org) 490 36.2.3 European Union Notification........................................................................... 491 36.2.4 UK Notification................................................................................................. 492 36.2.5 Belgium Notification......................................................................................... 492 36.2.6 Luxembourg Notification ................................................................................. 492 36.2.7 Czech Republic Notification............................................................................ 492 36.2.8 Norway Notification ......................................................................................... 492 36.2.9 Greece Notification.......................................................................................... 493 36.2.10 Brazil Notification............................................................................................. 493 36.2.11 Australia Notification ....................................................................................... 493 36.3 Exposure .................................................................................................... 493 36.4 Equipment Disposal.................................................................................... 494 36.5 Legal Notices.............................................................................................. 494 36.5.1 Software License Terms and Conditions....................................................... 494 36.5.2 Hardware Warranty in U.S.............................................................................. 496 36.5.3 Limit of Liability ................................................................................................ 496 37 Additional Resources ......................................................................................... 497 38 History of Documentation................................................................................... 499

................... 501501 GGLOSSARY

................................................... LOSSARY ................................ Draft 3 - for Regulatory Review LIST OF FIGURES Figure 1: Canopy Advantage Platform GUI logo.............................................................. 49 Figure 2: Pole-mounted AP cluster.................................................................................. 50 Figure 3: Structure-mounted SM ..................................................................................... 50 Figure 4: Examples of flat panel antennas with 900-MHz modules.................................. 51 Figure 5: Dish-mounted 10- or 20-Mbps BH.................................................................... 52 Figure 6: 30/60- or 150/300-Mbps Backhaul Module, integrated antenna........................ 52 Figure 7: 30/60- or 150/300-Mbps Backhaul Module, connected to external antenna..... 53 Figure 8: PIDU for 30/60-Mbps BH.................................................................................. 53 Figure 9: PIDU for 150/300-Mbps BH.............................................................................. 53 Figure 10: T1/E1 Multiplexer, front view .......................................................................... 54 Figure 11: T1/E1 Multiplexer, rear view ........................................................................... 54 Figure 12: CMM2 enclosure ............................................................................................ 55 Figure 13: CMM2 pole-mounted...................................................................................... 55 Figure 14: Motorola GPS antenna................................................................................... 56 Figure 15: 300SS surge suppressor ................................................................................ 57 Figure 16: ACPS110-03A power supply .......................................................................... 58 Figure 17: ACPSSW-09A power supply .......................................................................... 58 Figure 18: 27RD with mounted module ........................................................................... 58 Figure 19: SMMB1 SM support bracket........................................................................... 59 Figure 20: ACATHS-01 alignment headset...................................................................... 61 Figure 21: HSG-01 Housing ............................................................................................ 61 Figure 22: Uplink data slot usage .................................................................................... 85 Figure 23: TDD dividing Canopy frames.......................................................................... 85 Figure 24: Uplink and downlink rate caps adjusted to apply aggregate cap..................... 87 Figure 25: Uplink and downlink rate cap adjustment example ......................................... 87 Figure 26: Canopy channel, 75% downlink, 0% high priority in uplink ............................. 90 Figure 27: One unsynchronized AP in cluster.................................................................. 95 Figure 28: GPS timing throughout the Canopy network................................................... 96 Figure 29: Additional link to extend network sync, Design 3 ............................................ 97 Figure 30: Additional link to extend network sync, Design 4 ............................................ 98 Figure 31: Additional link to extend network sync, Design 5 ............................................ 98 Figure 32: Canopy Path Profiler tool ............................................................................. 101 Figure 33: OFDM series BH Link Estimator tool ............................................................ 102 Figure 34: Typical network layout with no BH................................................................ 103 Figure 35: Typical network layout with BH..................................................................... 104 Figure 36: Typical multiple-BH network layout............................................................... 104 Figure 37: Determinants in Rx signal level .................................................................... 130 Figure 38: Example layout of 7 Access Point clusters ................................................... 142 Figure 39: Fresnel zone ................................................................................................ 144 Figure 40: Variables for calculating angle of elevation (and depression) ....................... 145 Figure 41: Double-hop backhaul links ........................................................................... 146 Figure 42: Remote AP deployment ............................................................................... 147 Figure 43: Example 900-MHz remote AP behind 2.4-GHz SM ...................................... 149 Figure 44: Remote AP wired to SM that also serves a customer ................................... 150 Figure 45: Remote AP wired to SM that serves as a relay............................................. 151 Figure 46: NAT Disabled implementation ...................................................................... 157 Figure 47: NAT with DHCP Client and DHCP Server implementation ........................... 158 Figure 48: NAT with DHCP Client implementation......................................................... 159 Figure 49: NAT with DHCP Server implementation ....................................................... 160 Figure 50: NAT without DHCP implementation.............................................................. 161 Figure 51: Example of IP address in Class B subnet..................................................... 162 Figure 52: Canopy base cover, attached and detached................................................. 178 Figure 53: Canopy CMM2, bottom view ........................................................................ 180 Figure 54: Cluster Management Module micro.............................................................. 181 Figure 55: RJ-45 pinout for straight-through Ethernet cable .......................................... 183 Figure 56: RJ-45 pinout for crossover Ethernet cable.................................................... 183 Figure 57: RJ-11 pinout for straight-through sync cable ................................................ 184 Figure 58: Quick Start tab of AP, example .................................................................... 186 Figure 59: Radio Frequency Carrier tab of AP, example ............................................... 187 Figure 60: Synchronization tab of AP, example............................................................. 188 Figure 61: LAN IP Address tab of AP, example............................................................. 189 Figure 62: Review and Save Configuration tab of AP, example..................................... 190 Figure 63: Time tab of AP, example .............................................................................. 191 Figure 64: Session Status tab data from AP, example .................................................. 193 Figure 65: Remote Subscribers tab of AP, example...................................................... 197 Draft 3 - for Regulatory Review Figure 66: General Status tab of SM, example.............................................................. 198 Figure 67: General Status tab of AP, example .............................................................. 201 Figure 68: Quick Start tab of BHM, example ................................................................. 205 Figure 69: Time tab of BHM, example........................................................................... 207 Figure 70: Remote Subscribers tab of BHM, example................................................... 209 Figure 71: General Status tab of BHS, example............................................................ 210 Figure 72: General Status tab of BHM, example ........................................................... 213 Figure 73: CMMmicro layout ......................................................................................... 216 Figure 74: CMMmicro door label ................................................................................... 218 Figure 75: CMMmicro circuit board ............................................................................... 220 Figure 76: CMMmicro connections................................................................................ 220 Figure 77: Status page of CMMmicro, example............................................................. 221 Figure 78: Configuration page of CMMmicro, example.................................................. 224 Figure 79: GPS Status page of CMMmicro, example .................................................... 231 Figure 80: Port MIB page of CMMmicro, example......................................................... 232 Figure 81: General tab of AP, example ......................................................................... 236 Figure 82: IP tab of AP, example................................................................................... 239 Figure 83: Radio tab of AP (900 MHz), example ........................................................... 241 Figure 84: SNMP tab of AP, example............................................................................ 246 Figure 85: Quality of Service (QoS) tab of AP, example................................................ 249 Figure 86: Security tab of AP, example ......................................................................... 251 Figure 87: VLAN tab of AP, example............................................................................. 253 Figure 88: VLAN Membership tab of AP, example ........................................................ 255 Figure 89: DiffServe tab of AP, example ....................................................................... 256 Figure 90: Unit Settings tab of AP, example.................................................................. 258 Figure 91: General tab of SM, example......................................................................... 260 Figure 92: NAT tab of SM with NAT disabled, example................................................. 263 Figure 93: IP tab of SM with NAT disabled, example..................................................... 266 Figure 94: NAT tab of SM with NAT enabled, example.................................................. 268 Figure 95: IP tab of SM with NAT enabled, example ..................................................... 272 Figure 96: Radio tab of SM, example ............................................................................ 273 Figure 97: SNMP tab of SM, example ........................................................................... 276 Figure 98: Quality of Service (QoS) tab of SM, example ............................................... 279 Figure 99: Security tab of SM, example......................................................................... 282 Figure 100: VLAN tab of SM, example .......................................................................... 284 Figure 101: VLAN Membership tab of SM, example...................................................... 286 Figure 102: DiffServe tab of SM, example..................................................................... 287 Figure 103: Protocol Filtering tab of SM, example......................................................... 289 Figure 104: NAT Port Mapping tab of SM, example ...................................................... 290 Figure 105: Unit Settings tab of SM, example ............................................................... 291 Figure 106: General tab of BHM, example .................................................................... 295 Figure 107: IP tab of BHM, example ............................................................................. 298 Figure 108: Radio tab of BHM, example........................................................................ 300 Figure 109: SNMP tab of BHM, example....................................................................... 303 Figure 110: Security tab of BHM, example .................................................................... 306 Figure 111: DiffServe tab of BHM, example .................................................................. 308 Figure 112: Unit Settings tab of BHM, example............................................................. 310 Figure 113: General tab of BHS, example..................................................................... 312 Figure 114: IP tab of BHS, example .............................................................................. 315 Figure 115: Radio tab of BHS, example ........................................................................ 317 Figure 116: SNMP tab of BHS, example ....................................................................... 319 Figure 117: Quality of Service (QoS) tab of BHS, example ........................................... 321 Figure 118: Security tab of BHS, example..................................................................... 322 Figure 119: DiffServe tab of BHS, example ................................................................... 324 Figure 120: Unit Settings tab of BHS, example ............................................................. 325 Figure 121: PDA Quick Status tab, example ................................................................. 332 Figure 122: PDA Spectrum Analyzer tab of SM, example ............................................. 332 Figure 123: PDA Spectrum Results tab of SM, example ............................................... 333 Figure 124: PDA Information tab of SM, example.......................................................... 333 Figure 125: PDA AP Evaluation tab of SM, example..................................................... 334 Figure 126: PDA Aim tab of SM, example ..................................................................... 334 Figure 127: Detail of GPS antenna mounting ................................................................ 337 Figure 128: Detail of pole mounting............................................................................... 338 Figure 129: Location of 115-/230-volt switch ................................................................. 339 Figure 130: Layout of logical connections in CMM2 ...................................................... 340 Figure 131: Canopy CMM2, front view .......................................................................... 341 Figure 132: Port indicator LED on Ethernet switch ........................................................ 342 Draft 3 - for Regulatory Review Figure 133: SM attachment to reflector arm .................................................................. 346 Figure 134: SM grounding per NEC specifications ........................................................ 347 Figure 135: Internal view of Canopy 300SS Surge Suppressor ..................................... 348 Figure 136: Audible Alignment Tone kit, including headset and connecting cable ......... 349 Figure 137: AP/SM link status indications in the AP Session Status tab........................ 351 Figure 138: Correct mount with reflector dish ................................................................ 352 Figure 139: Incorrect mount with reflector dish.............................................................. 353 Figure 140: Mounting assembly, exploded view ............................................................ 354 Figure 141: BH attachment to reflector arm................................................................... 355 Figure 142: Session Status tab of BHM......................................................................... 359 Figure 143: Spectrum Analyzer tab of SM, example...................................................... 366 Figure 144: General Status tab view for GUEST-level account ..................................... 374 Figure 145: Add User tab of SM, example..................................................................... 375 Figure 146: RJ-11 pinout for the override plug .............................................................. 376 Figure 147: Categorical protocol filtering ....................................................................... 379 Figure 148: Session Status tab data, example .............................................................. 411 Figure 149: Event Log tab data, example...................................................................... 413 Figure 150: Network Interface tab of AP, example ........................................................ 415 Figure 151: Network Interface tab of SM, example........................................................ 415 Figure 152: Scheduler tab of SM, example ................................................................... 416 Figure 153: SM Registration Failures tab of AP, example ............................................. 417 Figure 154: Bridging Table tab of AP, example ............................................................. 418 Figure 155: Translation Table tab of SM, example ........................................................ 419 Figure 156: Ethernet tab of AP, example....................................................................... 420 Figure 157: Radio tab of Statistics page in SM, example............................................... 422 Figure 158: VLAN tab of AP, example........................................................................... 424 Figure 159: Data VC tab of SM, example ...................................................................... 425 Figure 160: Filter tab on SM, example........................................................................... 427 Figure 161: Nat Stats tab on SM, example.................................................................... 428 Figure 162: NAT DHCP Statistics tab in SM, example .................................................. 428 Figure 163: Alignment tab of BHS, example.................................................................. 431 Figure 164: Link Capacity Test tab with 1522-byte packet length, example................... 434 Figure 165: Link Capacity Test tab with 64-byte packet length, example....................... 435 Figure 166: AP Evaluation tab of SM, example ............................................................. 437 Figure 167: Frame Calculator tab, example................................................................... 441 Figure 168: Calculated Frame Results section of Frame Calculator tab, example......... 444 Figure 169: SM Configuration tab of AP, example......................................................... 445 Figure 170: BER Results tab of SM, example ............................................................... 446 Figure 171: Example ftp session to transfer custom logo file......................................... 450 Figure 172: Example telnet session to activate custom logo file .................................... 451 Figure 173: Example telnet session to clear custom files .............................................. 452 Figure 174: Protocol analysis at SM.............................................................................. 455 Figure 175: Protocol analysis at AP or BH not connected to a CMM ............................. 456 Figure 176: Protocol analysis at AP or BH connected to a CMM ................................... 457 Figure 177: IP tab of SM with NAT disabled and local accessibility ............................... 458 Figure 178: Local Area Connection Properties window ................................................. 459 Figure 179: Internet Protocol (TCP/IP) Properties window ............................................ 459 Figure 180: Ethereal Capture Options window .............................................................. 460 Figure 181: Ethereal Capture window ........................................................................... 461 Figure 182: <capture> - Ethereal window, Packet 1 selected ........................................ 462 Figure 183: <capture> - Ethereal window, Packet 14 selected ...................................... 463 Figure 184: NAT Table tab of SM, example................................................................... 469 Figure 185: NAT DHCP Statistics tab of SM, example .................................................. 470 Figure 186: Event Log tab of SM, example ................................................................... 472 Draft 3 - for Regulatory Review LIST OF TABLES Table 1: Canopy 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: Adjustable power radios .................................................................................... 54 Table 8: Power supply descriptions................................................................................. 57 Table 9: Recommended outdoor UTP Category 5E cables ............................................. 59 Table 10: Recommended indoor UTP Category 5E cables ............................................. 60 Table 11: Recommended antenna cables ....................................................................... 60 Table 12: Product applications per frequency band range............................................... 62 Table 13: Products with encryption options available per frequency band, PTMP links ... 63 Table 14: Typical range and throughput per frequency band, PTMP links....................... 64 Table 15: Products with encryption options available per frequency band, PTP links ...... 65 Table 16: Typical range and throughput per frequency band, PTP links.......................... 66 Table 17: Cluster management product similarities and differences ................................ 67 Table 18: Canopy applications and tools......................................................................... 69 Table 19: Correct placement of license keys ................................................................... 73 Table 20: CMM2 specifications and limitations................................................................ 75 Table 21: CMMmicro specifications and limitations ......................................................... 76 Table 22: Canopy model numbers (part numbers) for AES and DES encryption modules80 Table 23: Canopy model numbers (part numbers) for proprietary encryption modules.... 81 Table 24: Labels and locations of model (part) numbers and ESNs ................................ 81 Table 25: Characteristics of hardware scheduling ........................................................... 91 Table 26: Effect of 2X operation on throughput for the SM .............................................. 92 Table 27: Effects of network conditions on PTMP throughput........................................ 100 Table 28: Comparison of SM products with Canopy Advantage AP .............................. 100 Table 29: Canopy features ............................................................................................ 107 Table 30: Demonstration Kit part numbers .................................................................... 121 Table 31: Starter Kit part numbers ................................................................................ 124 Table 32: Modules with DFS, by Region ....................................................................... 133 Table 33: Signal quality levels indicated by jitter ........................................................... 134 Table 34: Recommended courses of action based on Efficiency in 2X operation .......... 135 Table 35: Example 900-MHz channel assignment by sector ......................................... 140 Table 36: Example 2.4-GHz channel assignment by sector .......................................... 140 Table 37: Example 5.2-GHz channel assignment by sector .......................................... 140 Table 38: Example 5.4-GHz channel assignment by sector .......................................... 141 Table 39: Example 5.7-GHz channel assignment by sector .......................................... 141 Table 40: VLAN filters in point-to-multipoint modules .................................................... 166 Table 41: Exposure separation distances...................................................................... 169 Table 42: Calculated distances and power compliance margins.................................... 170 Table 43: Statistical incidence of current from lightning strikes...................................... 172 Table 44: LEDs in AP and BHM .................................................................................... 179 Table 45: LEDs in SM and BHS .................................................................................... 179 Table 46: Port Configuration selections for CMMmicro.................................................. 226 Table 47: When changes become effective in CMMmicro ............................................. 230 Table 48: Control slot settings for all APs in cluster....................................................... 243 Table 49: Recommended combined settings for typical operations ............................... 293 Table 50: Where feature values are obtained for an SM with authentication required ... 293 Table 51: Where feature values are obtained for an SM with authentication disabled ... 294 Table 52: Total gain per antenna................................................................................... 327 Table 53: Patch antenna and reflector gain................................................................... 327 Table 54: Transmitter output power settings, example cases ........................................ 329 Table 55: Wire size for CMMmicro power runs of longer than 9 feet (2.8 m) ................. 344 Table 56: Hardware series by MAC address ................................................................. 367 Table 57: Hardware series differences .......................................................................... 367 Table 58: AP/BH compatibility with CMMmicro.............................................................. 368 Table 59: Ports filtered per protocol selections.............................................................. 380 Table 60: Example times to download for arbitrary tiers of service with Canopy AP ...... 384 Table 61: Example times to download for arbitrary tiers of service with Advantage AP . 385 Table 62: Categories of MIB-II objects .......................................................................... 389 Table 63: Canopy Enterprise MIB objects for APs, SMs, and BHs ................................ 391 Table 64: Canopy Enterprise MIB objects for APs and BH timing masters .................... 394 Table 65: Canopy Enterprise MIB objects for SMs and BH timing slaves ...................... 398 Draft 3 - for Regulatory Review Table 66: Canopy Enterprise MIB objects for CMMmicros ............................................ 401 Table 67: Canopy OFDM BH module MIB objects......................................................... 404 Table 68: Event Log messages for abnormal events..................................................... 414 Table 69: Event Log messages for normal events......................................................... 414 Table 70: Basic site information for technical support.................................................... 478 Table 71: Supported telnet commands for module administration ................................. 487 Table 72: US FCC IDs and Industry Canada certification numbers ............................... 490 LIST OF PROCEDURES Procedure 1: Modifying a fixed license key for a module IP address ............................. 114 Procedure 2: Analyzing the spectrum............................................................................ 131 Procedure 3: Invoking the low power mode................................................................... 152 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........................................ 200 Procedure 11: Verifying and recording information from the AP .................................... 203 Procedure 12: Setting up the BH for Quick Start ........................................................... 204 Procedure 13: Using Quick Start to configure the BHs for test ...................................... 206 Procedure 14: Setting up the BHS for test..................................................................... 208 Procedure 15: Verifying and recording information from the BHS.................................. 212 Procedure 16: Verifying and recording information from the BHM ................................. 215 Procedure 17: Setting up a CMMmicro.......................................................................... 217 Procedure 18: Setting CMMmicro parameters for test................................................... 225 Procedure 19: Installing the AP..................................................................................... 334 Procedure 20: Mounting the GPS antenna.................................................................... 336 Procedure 21: Mounting the CMM2............................................................................... 338 Procedure 22: Cabling the CMM2 ................................................................................. 339 Procedure 23: Verifying CMM2 connections.................................................................. 342 Procedure 24: Mounting the CMMmicro ........................................................................ 343 Procedure 25: Installing the Power Supply for the CMMmicro....................................... 344 Procedure 26: Cabling the CMMmicro........................................................................... 344 Procedure 27: Verifying CMMmicro connections........................................................... 345 Procedure 28: Installing the SM .................................................................................... 346 Procedure 29: Verifying performance for an AP-SM link ............................................... 349 Procedure 30: Installing the BHM.................................................................................. 354 Procedure 31: Installing the BHS .................................................................................. 356 Draft 3 - for Regulatory Review Procedure 32: Verifying performance for a BH link........................................................ 357 Procedure 33: Verifying system functionality ................................................................. 361 Procedure 34: Using the Spectrum Analyzer in AP feature ........................................... 366 Procedure 35: Extending network sync ......................................................................... 369 Procedure 36: Fabricating an override plug................................................................... 376 Procedure 37: Regaining access to a module ............................................................... 376 Procedure 38: Using the override switch to regain access to CMMmicro ...................... 377 Procedure 39: Installing the Canopy Enterprise MIB files .............................................. 390 Procedure 40: Performing a Link Capacity Test ............................................................ 435 Procedure 41: Using the Frame Calculator.................................................................... 443 Procedure 42: Replacing the Canopy logo on the GUI with another logo ...................... 449 Procedure 43: Changing the URL of the logo hyperlink................................................. 451 Procedure 44: Returning a module to its original logo and hyperlink ............................. 452 Procedure 45: Denying all remote access ..................................................................... 453 Procedure 46: Reinstating remote access capability ..................................................... 453 Procedure 47: Setting up a protocol analyzer................................................................ 458 Procedure 48: Troubleshooting loss of connectivity....................................................... 467 Procedure 49: Troubleshooting loss of connectivity for NAT/DHCP-configured SM....... 468 Procedure 50: Troubleshooting SM failing to register to an AP...................................... 470 Procedure 51: Troubleshooting BHS failing to register to a BHM .................................. 471 Procedure 52: Troubleshooting loss of sync.................................................................. 472 Procedure 53: Troubleshooting loss of Ethernet connectivity ........................................ 473 Procedure 54: Troubleshooting failure to power up ....................................................... 474 Procedure 55: Troubleshooting failure of power supply to produce power..................... 474 Procedure 56: Troubleshooting CMM2 that malfunctions .............................................. 475 Procedure 57: Troubleshooting CMM2 not passing sync............................................... 475 Procedure 58: Troubleshooting an unsuccessful software upgrade............................... 476 Procedure 59: Restoring the web interface to a module ................................................ 476 Release 8 Guide To This User Guide GGUIDEUIDE TTOO TTHISHIS UUSERSER GGUIDEUIDE Issue 2, December 2006 Draft 2 for Regulatory Review 31 Release 8 1 NEW IN THIS ISSUE 1.1 NEW PRODUCTS AND FEATURES DESCRIBED IN ISSUE 2 Guide To This User Guide Connectorized 5.7 GHz modules with FCC approval 1.2 NEW DESCRIPTIONS AND REVISIONS IN ISSUE 2 This section is a placeholder where other new descriptions, as wells as clarifications and corrections, will be listed in future issues. 1.3 MOTOwi4 PORTFOLIO Motorola has introduced the broad MOTOwi4 portfolio of fixed, nomadic, and mobile wireless broadband solutions, among which Canopy products are significant. The MOTOwi4 portfolio meets residential and enterprise data transport needs with the following present and future solutions:

residential access fixed solutions Canopy Access Point and Subscriber Modules in the following frequency band ranges:

900 MHz 2.4 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.7 GHz WiMAX fixed and mobile solutions, based on the 802.16e (WiMAX) standard, in the following frequency band ranges:

2.3 GHz 2.5 GHz 3.5 GHz Metro WiFi local area mesh network solutions, based on the 802.11 standard backhaul solutions, based on the 802.16e (WiMAX) standard or Canopy protocols, in the following frequency band ranges:

2.4 GHz 5.2 GHz 5.4 GHz 5.7 GHz 1.4 PRODUCTS COVERED BY THIS USER GUIDE Most Canopy products are covered by this user guide:

radio-networked modules in the following frequency band ranges:

900 MHz 2.4 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.7 GHz Cluster Management Module-2 (CMM2) Cluster Management Module micro (CMMmicro) Surge Suppressor Issue 2, December 2006 Draft 2 for Regulatory Review 33 Guide To This User Guide 1.5 PRODUCTS NOT COVERED BY THIS USER GUIDE Release 8 Some specific-use Canopy products are referred to in this user guide but fully described in their own separate user guides:

30-Mbps Backhaul Module. See Canopy 30 Mbps 60 Mbps Backhaul User Guide and Motorola Canopy OFDM Backhaul Quick Start Guide. 30/60-Mbps Backhaul Module. See Canopy 30 Mbps 60 Mbps Backhaul User Guide and Motorola Canopy OFDM Backhaul Quick Start Guide for (30/60 Mbps). 150/300-Mbps Backhaul Module. See Canopy 150 Mbps 300 Mbps Backhaul User Guide and Motorola Canopy OFDM Backhaul Quick Start Guide

(for 150/300 Mbps). MOTOwi4 Ultra Light Access Point (ULAP) and Ultra Light Outdoor Subscriber Unit (OSU). See Canopy 3500 System User Guide. Bandwidth and Authentication Manager. See Canopy Bandwidth and Authentication Manager (BAM) Release 2.1 User Guide (or Canopy Bandwidth and Authentication Manager (BAM) User Guide for earlier releases). License Manager. See Canopy Networks License Manager User Guide. Prizm. See Motorola Canopy Prizm User Guide. T1/E1 Multiplexer. See Canopy T1/E1 Multiplexer User Guide. 1.6 SOFTWARE COMPATIBILITY DESCRIBED IN THIS USER GUIDE The following sections of this document provide details and caveats about the compatibility of Canopy products:

Designations for Hardware on Page 367 CMMmicro Software and Hardware Compatibility on Page 368 MIB File Set Compatibility on Page 368 34 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 2 USING THIS USER GUIDE Guide To This User Guide This document should be used with Canopy features through Software Release 8 and CMMmicro Release 2.1.1. The audience for this document includes system operators, network administrators, and equipment installers. 2.1 2.1.1 FINDING THE INFORMATION YOU NEED Becoming Familiar with This User Guide 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. Issue 2, December 2006 Draft 2 for Regulatory Review 35 Guide To This User Guide Release 8 Quick Reference The Canopy User Guide comprises six sections, as described in Table 1. Section Guide to This User Guide

(this section) Table 1: Canopy 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 Canopy Networks what the various typefaces and admonitions indicate. how to contact Canopy. 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 Canopy products and how they communicate. descriptions of data handling and synchronization. a review of Canopy optional features. resources for developing familiarity and proficiencies with Canopy networks. Planning Guide Provides essential information for evaluating an area for a Canopy 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 Canopy equipment. Operations Guide Provides guidance for expanding network coverage. improving the security of Canopy 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 Canopy documentation. Glossary Defines terms and concepts that are used in this user guide. 36 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Guide To This User Guide 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 Avoiding Self Interference on Page 151 because this topic is important to RF planning. Monitoring the RF Environment on Page 365 this topic is also important to managing the network. what types of slots compose the Canopy frame Understanding Bandwidth Management on Page 83 this information is helpful for understanding Canopy networks. 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. Noting Possible Obstructions in the Fresnel Zone on Page 132 Cables on Page 35 Procedure 20 on Page 336 or Procedure 24 on Page 343 Messages that Flag Abnormal Events on Page 414 and Messages that Flag Normal Events on Page 414 Specifications and Limitations on Page 73, then downward to a table for a Canopy Part Number that includes RF. Installing a Reflector Dish on Page 352 High-priority Bandwidth on Page 88 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. Issue 2, December 2006 Draft 2 for Regulatory Review 37 Release 8 Guide To This User Guide 2.1.2 Searching This User Guide 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. Finding Parameter and Field Definitions for Module Web Pages 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. 2.1.3 Table 3: Locations of screen captures and associated documentation Tab or Web Page Displayed Page 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 375 431 437 446 418 444 224 256 308 324 287 420 413 472 441 201 213 210 198 374 236 295 312 1 Reader is a registered trademark of Adobe Systems, Incorporated. 38 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Guide To This User Guide 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 260 231 239 298 315 458 266 272 189 434 435 470 290 263 268 469 334 334 333 332 332 333 232 289 249 321 279 186 205 187 241 300 317 273 Issue 2, December 2006 Draft 2 for Regulatory Review 39 Guide To This User Guide Release 8 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 209 190 416 251 306 322 282 193 411 445 417 246 303 319 276 366 221 188 191 207 258 310 325 291 255 286 253 284 40 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 2.2 Guide To This User Guide INTERPRETING TYPEFACE AND OTHER CONVENTIONS This document employs distinctive fonts to indicate the type of information, as described in Table 4. Font variable width bold Table 4: Font types Type of Information Selectable option in a graphical user interface or settable parameter in the web-based interface to a Canopy component. constant width regular constant width italic constant width bold constant width bold italic 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 Canopy 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. Issue 2, December 2006 Draft 2 for Regulatory Review 41 Guide To This User Guide Admonition Label Release 8 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. 2.3 GETTING ADDITIONAL HELP Help is available for problems with supported products and features. Obtaining Technical Support on Page 477 provides the sequence of actions that you should take if these problems arise. 2.4 SENDING FEEDBACK We welcome your feedback on Canopy 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@canopywireless.com. 42 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Overview of Canopy Networks OOVERVIEW OF VERVIEW OF CCANOPY ANOPY NNETWORKS ETWORKS Issue 2, December 2006 Draft 2 for Regulatory Review 43 Release 8 3 ADVANCING FROM RESEARCH TO IMPLEMENTATION Overview of Canopy Networks Before you begin to research a possible Canopy 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 Canopy Link Characteristics on Page 83. Understanding IP Fundamentals on Page 117. Engineering Your IP Communications on Page 155. Issue 2, December 2006 Draft 2 for Regulatory Review 45 Release 8 4 REALIZING A WIRELESS BACKHAUL NETWORK Overview of Canopy Networks Canopy backhaul modules (BHs) can connect Canopy 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 Canopy wireless backhaul network. Table 6: Essential user guide elements for new backhaul network implementation Element Section 1.5 Section 5.1.8 Section 5.1.9 Title Products Not Covered by This User Guide Backhaul Module OFDM Series Backhaul Module Section 5.1.10 Power Indoor Units for OFDM Series Backhaul Modules Section 5.1.12 T1/E1 Multiplexer Section 5.1.13 Cluster Management Module-2 (Part 1008CK-2) Section 5.1.14 Cluster Management Module micro (Part 1070CK) Table 15 Table 16 Section 8.2 Figure 36 Products with encryption options available per frequency band, PTP links Typical range and throughput per frequency band, PTP links BH-BH Links Typical multiple-BH network layout Section 12.2 Analyzing the RF Environment Section 12.5 Considering Frequency Band Section 15 Avoiding Hazards Section 16.4 Configuring a Point-to-Point Link for Test Section 17 Preparing Components for Deployment Section 18.4 Configuring a BH Timing Master for the Destination Section 18.5 Configuring a BH Timing Slave for the Destination Section 19.4 Installing a GPS Antenna Section 19.5 Installing a CMM2 Section 19.6 Installing a CMMmicro Page 34 51 52 53 54 55 56 65 66 99 104 131 136 169 204 233 294 312 336 337 342 Issue 2, December 2006 Draft 2 for Regulatory Review 47 Overview of Canopy Networks Release 8 Section 19.9 Installing a Reflector Dish Section 19.10 Installing a BH Timing Master Section 19.11 Installing a BH Timing Slave Section 19.13 Verifying a BH Link Section 21.2.2 CMMmicro Software and Hardware Compatibility Section 22.2 Encrypting Canopy Radio Transmissions Section 22.3 Managing Module Access Section 24.6 Objects Supported in the Canopy 30/60-Mbps BH Section 24.7 Objects Supported in the Canopy 150/300-Mbps BH Section 24.10 Traps Provided in the Canopy 30/60-Mbps BH Module MIB Section 24.11 Traps Provided in the Canopy 150/300-Mbps BH Module MIB Section 25 Using the Canopy Network Updater Tool (CNUT) Section 28.3 Typical Contents of Release Notes Section 28.4 Typical Upgrade Process Section 31.2 Analyzing Traffic at an AP or BH with No CMM Section 31.3 Analyzing Traffic at an AP or BH with a CMM Section 32 Section 33 Section 34 Troubleshooting Obtaining Technical Support Getting Warranty 352 354 356 357 368 371 373 405 405 406 406 409 447 447 456 456 465 477 483 48 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 5 EXPLORING THE SCOPE OF SOLUTIONS Overview of Canopy Networks Canopy 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 5.1.1 Canopy 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. Canopy Access Point Module The Canopy Access Point (AP) module distributes network or Internet services in a 60 sector to not more than 200 subscribers or fewer 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 Canopy AP can communicate with only a Canopy SM, not also an Advantage SM or a Canopy Lite SM. 5.1.2 Advantage Access Point Module The Canopy Advantage AP distributes services as broadly as the Canopy AP. However, the Advantage AP provides greater throughput and less latency. Each tab in the GUI for Canopy Advantage modules displays the distinctive branding shown in Figure 1. Figure 1: Canopy Advantage Platform GUI logo The Advantage AP communicates with all Canopy SMs in its frequency band range:

Canopy SMs, Advantage SMs, and Canopy Lite SMs. Issue 2, December 2006 Draft 2 for Regulatory Review 49 Overview of Canopy Networks 5.1.3 Access Point Cluster Release 8 The AP cluster consists of two to six APs that together distribute network or Internet services to a community of 1,200 or fewer subscribers. Each AP transmits and receives in a 60 sector. An AP cluster covers as much as 360. The variety of available APs and Advantage APs in frequency band range, power adjustability, and antenna configuration is shown under Acquiring a Canopy Demonstration Kit, beginning on Page 117. An AP cluster is pictured in Figure 2. 5.1.4 Canopy Subscriber Module The Subscriber Module (SM) is a customer premises equipment (CPE) device that extends network or Internet services by communication with an AP. The SM is configurable through a web interface. The variety of available SMs and Advantage SMs in frequency band range, power adjustability, and antenna configuration is shown under Acquiring a Canopy Demonstration Kit, beginning on Page 117. A Canopy SM can communicate with either a Canopy AP or an Advantage SP. An SM mounted directly to a structure is pictured in Figure 3. 5.1.5 Advantage Subscriber Module Figure 2: Pole-mounted AP cluster Figure 3: Structure-mounted SM 5.1.6 The Canopy Advantage SM provides the same configurability and services as the Canopy SM. However, in a link with the Advantage AP, the Advantage SM provides uncapped sustained throughput through the 2X operation feature. See 2X Operation on Page 91. An Advantage SM can communicate with only an Advantage AP. Canopy Lite Subscriber Module Canopy 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. Canopy 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 Canopy Lite SM can communicate with only a Canopy Advantage AP. A comparison of the Canopy Lite SM to the Canopy SM and Advantage SM is provided in Table 28 on Page 100. 50 Draft 2 for Regulatory Review Issue 2, December 2006 Overview of Canopy Networks Release 8 5.1.7 900-MHz AP and SM Canopy 900 MHz AP and SM modules operate at 3.3 Mbps (compared to 10 Mbps for other Canopy frequency bands). With Downlink Data set to 75% in the AP, the AP supports high throughput to an SM. Figure 4: 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 Canopy APs and SMs. The physics of longer-wavelength 900 MHz, the power allowed by regulatory authorities, and the low required level of Canopy 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 147). 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. Issue 2, December 2006 Draft 2 for Regulatory Review 51 Release 8 Overview of Canopy Networks 5.1.8 Backhaul Module 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 5. 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. 5.1.9 OFDM Series Backhaul Modules These high-speed BHs provide point-to-point data connectivity via a 5.4- or 5.7-GHz wireless Ethernet bridge that operates at broadband data rates. They provide non-Line of Sight

(NLOS) operation through the use of Orthogonal Frequency Division Multiplex

(OFDM) modulation and Transmit Diversity. Transmissions penetrate foliage, such that almost universal coverage is typical at short range. The link consists of a pair of identical BHs that transmit and receive on an automatically selected but configurable frequency. The installer sets up one unit as the master and the other as the slave. (Each unit is preconfigured as master or slave but can be reconfigured to the other.) These modules are available as either connectorized for an external antenna or equipped with an integrated antenna. Each end of the link consists of both an outdoor transceiver (ODU) that contains all the radio and networking electronics (see Figure 6 and Figure 7) an indoor passive connection box

(PIDU) that contains status indicators and network connection (see Figure 8 and Figure 9. Available modulations are 30/60 Mbps and 150/300 Mbps. A 30-Mbps BH is software-

Figure 5: Dish-mounted 10- or 20-Mbps BH Figure 6: 30/60- or 150/300-Mbps Backhaul Module, integrated antenna 52 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 upgradable to 60 Mbps, and a 150-Mbps BH is likewise software-upgradable to 300 Mbps. Products in this series are supported by dedicated user guides. Overview of Canopy Networks By default, these BHs use a proprietary data scrambling and encryption scheme. The 30/60-

Mbps BHs have AES encryption available as a licensed option. The 150/300-Mbps BHs support virtual private networking (VPN). 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.

(OFDM Series BHs were previously available in 45-Mbps modulation, which can be upgraded to 60 Mbps by software.) Figure 7: 30/60- or 150/300-Mbps Backhaul Module, connected to external antenna 5.1.10 Power Indoor Units for OFDM Series Backhaul Modules Canopy also offers the required power indoor unit (PIDU) that generates the voltage for the 30/60- or 150/300-Mbps BHs. The PIDU provides status indicators for the ODU. Examples of these PIDUs are shown in Figure 8 and Figure 9. CAUTION!

The PIDU for the 30/60-Mbps BH and the PIDU for the 150/300-Mbps BH are clearly distinguished by their front labels. These units are unique and are not interchangeable under any circumstances. Their pinouts vary. Using any power unit other than the proper one of these two will destroy the module. Figure 8: PIDU for 30/60-Mbps BH Figure 9: PIDU for 150/300-Mbps BH Issue 2, December 2006 Draft 2 for Regulatory Review 53 Overview of Canopy Networks 5.1.11 Radio Adjustable Power Capabilities To help network operators become or remain compliant with applicable regulations in their regions and nations, Canopy offers adjustable power radios in various frequency band ranges, as indicated in Table 7. See also Adjusting Transmitter Output Power on Page 326 to ensure that your radios do not exceed the maximum permitted EIRP. 5.1.12 T1/E1 Multiplexer The Canopy T1/E1 Multiplexer converts the data stream from T1/E1 ports into Ethernet packets that are then transported over the Canopy BH link. This enables up to three T1 (or up to two E1) circuits to be extended over Ethernet networks. The T1/E1 Multiplexer is available in two power configurations:

an external 3.3-v DC power source from a 120/240-v AC adapter (supplied by Canopy) an optional connection to an external 48 v DC supply for battery backup. The T1/E1 Multiplexer supports synchronous TDM-based services over wireless Ethernet networks. CAS signaling transparent to all other signaling protocols on T1/E1. 10Base-T/100Base-TX uplink to the network. management interfaces. simplified troubleshooting through T1/E1 line loopback test. Release 8 Table 7: Adjustable power radios Introduced in Canopy System Release 7.0 Frequency Band Range 900 MHz1 2.4 GHz1 5.4 GHz2 5.7 GHz1 NOTES:

1. As a distinct part number. 2. In the base model. 6.1 4.2.7 4.2.7 Figure 10: T1/E1 Multiplexer, front view Figure 11: T1/E1 Multiplexer, rear view 54 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Applications include Overview of Canopy Networks obviating leased lines. implementing wireless PBX networking. establishing cellular backhaul links. providing homeland security backup or emergency voice networks. routing LAN/WAN data on excess bandwidth. This product is supported by the dedicated document Canopy T1/E1 Multiplexer User Guide. 5.1.13 Cluster Management Module-2 (Part 1008CK-2) 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 12. A CMM2 as part of a mounted Canopy system is pictured in Figure 13. Figure 12: CMM2 enclosure Figure 13: CMM2 pole-mounted Issue 2, December 2006 Draft 2 for Regulatory Review 55 Overview of Canopy Networks 5.1.14 Cluster Management Module micro (Part 1070CK) Release 8 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)2 on each port and connects any combination of APs, BHMs, BHSs, or Ethernet feed. 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 Canopy 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 Canopy System Release 4.2. 5.1.15 GPS Antenna The Motorola GPS antenna provides either timing pulses to the CMMmicro. timing pulses and positioning information to the CMM2. The GPS antenna is pictured in Figure 14. Figure 14: Motorola GPS antenna 2 Through a proprietary scheme, different from IEEE Standard 803.af. Also, BHs in the OFDM Series use yet another proprietary scheme. 56 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 5.1.16 Surge Suppressor (Part 300SS) The 300SS Surge Suppressor provides a path to ground (Protective Earth ) that protects connected equipment from near-miss lightning strikes. A 300SS is pictured in Figure 15. Overview of Canopy Networks Figure 15: 300SS surge suppressor 5.1.17 Accessory Components In addition to the above modules, the following accessories are available. Power Supplies The various power supplies available for Canopy modules are listed in Table 8. Table 8: Power supply descriptions Part Number ACPS81WA ACPS81W-02A ACPS110-03A1 ACPSSW-09A3 ACPSSW-10A3 ACPSSW-11A3 ACPSSW-12A3 For Use With CMMmicro Canopy radio2

(except OFDM backhauls) 30/60-Mbps OFDM BH Voltage (AC) Cycles per Second (Hz) Includes 100 to 240 100 to 240 120 90 to 240 90 to 240 90 to 240 90 to 240 50 to 60 50 to 60 50 to 60 50 to 60 50 to 60 50 to 60 50 to 60 47 to 63 US IEC line cord no IEC line cord US plug US, Euro, and UK adaptors Argentina adaptor Australia adaptor China adaptor US, Euro, and UK leads ACPSSW200-02A4 100 to 250 AC or 48 DC ACPSSW200-01A 100 to 250 47 to 63 100 to 250 47 to 63 ACPSSW200-03A5 150/300-Mbps OFDM BH NOTES:

1. Pictured in Figure 16. 2. Single transceiver. 3. Pictured in Figure 17. 4. Pictured in Figure 8 on Page 53. 5. Pictured in Figure 9 on Page 53. Issue 2, December 2006 Draft 2 for Regulatory Review 57 Overview of Canopy Networks Figure 16: ACPS110-03A power supply Release 8 Figure 17: ACPSSW-09A power supply Passive Reflector Dish Assembly The 27RD Passive Reflector Dish on both ends of a BH link extends the distance range of the link and focuses the beam into a narrower angle to reduce interference. The 27RD on an SM only helps to reduce interference. The module support tube provides the proper offset focus angle. See Figure 18. For 5.n-GHz radios, the reflector gain is 18dB and the beam width is 6 at 3 dB. For 2.4-GHz radios, the reflector gain is 11dB and the beam width is 17 at 3 dB. These beam width statements apply to both azimuth and elevation in each case. Figure 18: 27RD with mounted module 58 Draft 2 for Regulatory Review Issue 2, December 2006 Overview of Canopy Networks Release 8 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 19. The SMMB2 is a heavy duty mounting bracket for the 900-MHz connectorized SM and its external antenna. The BH1209 is a pole-mount bracket kit for Canopy backhaul modules. Figure 19: SMMB1 SM support bracket Cables Canopy 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. Canopy-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/motorola.htm. These cables are listed in Table 9 and Table 10. Table 9: Recommended outdoor UTP Category 5E cables Best-Tronics Part #

BT-0562 Description RJ-45 TO RJ-45; straight-through Ethernet cable BT-0562S RJ-45 TO RJ-45; shielded straight-through Ethernet cable BT-0565 RJ-45 TO RJ-45; crossover Ethernet cable BT-0565S RJ-45 TO RJ-45; shielded crossover Ethernet cable BT-0563 RJ-11 TO RJ-11; sync cable BT-0563S RJ-11 TO RJ-11; shielded sync cable Issue 2, December 2006 Draft 2 for Regulatory Review 59 Overview of Canopy Networks Release 8 Shielded cable is strongly recommended for all AP cluster and BH installations. NOTE:

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

BT-0596 BT-0595 Description 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) Canopy-approved antenna cables can be ordered in lengths up to 100 ft (30.4 m), as listed in Table 11. Table 11: Recommended antenna cables Best-Tronics Part #

BT-0564 BT-0716 Description 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/motorola.htm as Part BT-0583 (RJ-11 Default Plug). Alternatively if you wish, you can fabricate an override plug. For instructions, see Procedure 36 on Page 376 and the pinout in Figure 146 on Page 376. 60 Draft 2 for Regulatory Review Issue 2, December 2006 Overview of Canopy Networks Release 8 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 Figure 20: ACATHS-01 alignment headset pitch, higher when the received signal is stronger. volume, louder when jitter is less. An ACATHS-01 is pictured in Figure 20. Pinouts for an alternative listening device are provided under Alignment ToneTechnical Details on Page 184. Module Housing The HSG-01 Canopy Plastic Housing is available for replacement of a damaged housing on a module that is otherwise functional. The HSG-01 is pictured in Figure 21. 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 21: HSG-01 Housing 5.2 FREQUENCY BAND RANGES In the 2.4-, 5.2-, 5.1-, 5.4-, and 5.7-GHz frequency band ranges, Canopy APs, SMs, and BHs are available. Additionally, in the 900-MHz frequency band range, Canopy APs and SMs are available. National restrictions may apply. See Legal and Regulatory Notices on Page 489. To avoid self-interference, a Canopy 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. Issue 2, December 2006 Draft 2 for Regulatory Review 61 Overview of Canopy Networks Release 8 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 Canopy 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 CANOPY PRODUCT COMPARISONS 5.3.1 Canopy Product Applications The product applications per frequency band range are is summarized in Table 12. Table 12: Product applications per frequency band range Product 900 MHz 2.4 GHz Frequency Band Range 5.2 GHz 5.1 GHz 5.4 GHz 5.7 GHz Access Point Module Subscriber Module Subscriber Module with Reflector1 Backhaul Module Backhaul Module with Reflector1 OFDM Series Backhaul Module CMM2 CMMmicro T1/E1 Multiplexer 62 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Overview of Canopy Networks Product 900 MHz 2.4 GHz Frequency Band Range 5.2 GHz 5.1 GHz 5.4 GHz 5.7 GHz Power supply Surge suppressor 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. See National and Regional Regulatory Notices on Page 489. 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 Link Performance and Encryption Comparisons The encryption options on Canopy point-to-multipoint (PTMP) products are summarized in Table 13. Typical Line-of-Site (LOS) range and aggregate useful throughput for Canopy PTMP links are summarized in Table 14. Table 13: Products with encryption options available per frequency band, PTMP links Frequency Band 2.4 GHz @100 mW

(ETSI) 2.4 GHz @ 1W 5.1 GHz 5.2 GHz 5.4 GHz 5.7 GHz 900 MHz Products available with the following encryption options DES or none AES or none Issue 2, December 2006 Draft 2 for Regulatory Review 63 Overview of Canopy Networks Release 8 Table 14: Typical range and throughput per frequency band, PTMP links Advantage AP Canopy AP 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) 40 (64) 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 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) 15 7 7 7 7 7 7 20 20 20 20 20 20 Frequency Band 2.4 GHz ETSI 2.4 GHz 5.1 GHz 5.2 GHz 5.4 GHz 5.7 GHz 900 MHz4 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. GENERAL NOTES:

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. The encryption options on Canopy point-to-point (PTP) products are summarized in Table 15. Typical Line-of-Site (LOS) range and aggregate useful throughput for Canopy PTP links are summarized in Table 16. 64 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Overview of Canopy Networks Table 15: Products with encryption options available per frequency band, PTP links Frequency Band Modulation Rate (Mbps) Products available with the following encryption options DES or none AES or none Proprietary Proprietary or AES licensed upgrade 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 30 60 150 300 10 20 30 60 150 300 Issue 2, December 2006 Draft 2 for Regulatory Review 65 Overview of Canopy Networks Release 8 Table 16: Typical range and throughput per frequency band, PTP links Frequency Band Modulation Rate (Mbps) 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 30 60 150 300 10 20 30 60 150 300 Throughput No Reflectors Both Reflectors 7.5 Mbps to 2 km 14 Mbps to 1 km 7.5 Mbps to 16 km 14 Mbps to 8 km 7.5 Mbps to 5 mi (8 km) 7.5 Mbps to 35 mi (56 km) 14 Mbps to 3 mi (5 km) 14 Mbps to 35 mi (56 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) dynamically variable from 1.5 to 21 Mbps aggregate2 dynamically variable from 3 to 43 Mbps aggregate2 dynamically variable from 7 to 150 Mbps aggregate2 dynamically variable from 14 to 300 Mbps aggregate2 7.5 Mbps to 2 mi (3.2 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 1 mi (1.6 km) 14 Mbps to 35 mi (56 km) dynamically variable from 1.5 to 21 Mbps aggregate2 dynamically variable from 3 to 43 Mbps aggregate2 dynamically variable from 7 to 150 Mbps aggregate2 dynamically variable from 14 to 300 Mbps aggregate2 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. 66 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 5.3.3 Overview of Canopy Networks Cluster Management Product Comparison Canopy 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 17. Table 17: Cluster management product similarities and differences Characteristic Approximate size CMM2 17 H x 13 W x 6.5 D

(43 cm H x 33 cm W x 7 cm D) CMMmicro 12 H x 10 W x 3 D

(30 cm H x 25 cm W x 8 cm D) Approximate weight 25 lb ( 11.3 kg) 8 lb (3.5 kg) Cabling Canopy network interconnection one Ethernet/power cable per radio. one sync cable per radio. one Ethernet/power/sync cable per radio. 8 Ethernet ports 8 Ethernet ports Data throughput auto-negotiates to full or half duplex auto-negotiates to full or half duplex Ethernet operating speed standard auto-negotiates to 10Base-T or 100Base-TX auto-negotiates to 10Base-T or 100Base-TX Additional Ethernet ports one for data feed one for local access

(notebook computer) none Power supply integrated 24-V DC to power APs, BHs, and GPS receiver external 24-V DC to power APs, BHs, and GPS receiver SNMP management capability none provided Sync (to prevent self-interference) carried by the additional serial cable to each AP and BHM embedded in power-over-Ethernet cable Time & Date carried by the additional serial cable to each AP and BHM Weatherized enclosure and power supply Web interface none 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. Issue 2, December 2006 Draft 2 for Regulatory Review 67 Overview of Canopy Networks 5.4 ANTENNAS FOR CONNECTION TO 900-MHz MODULES Release 8 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 antenna in a different form factor. Certified Connectorized Flat Panel Antennas Motorola has certified through regulatory agencies four connectorized flat panel antenna options. Motorola offers one of these, whose attributes include 5.4.1 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) polarizationvertical or horizontal cable12-inch (30.5 cm) connectorfemale N-type beamwidthapproximately 60 vertical and 60 horizontal at 3 dBm Motorola has certified three other antennas, which are available through Canopy 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 5.4.2 Examples of these antennas are pictured in Figure 4 on Page 51. Third-party Certified Connectorized Flat Panel Antenna A third party may certify additional antennas for use with the Canopy connectorized 900-MHz module. 68 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 5.5 ADJUNCTIVE SOFTWARE PRODUCTS Overview of Canopy Networks The capabilities of available applications and tools are summarized for comparison in Table 18. In this table CNUT represents Canopy Network Updater Tool, Release 1.1 or later, and BAM represents Bandwidth and Authentication Manager, Release 2.0 or later. Table 18: Canopy 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 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 M A B Issue 2, December 2006 Draft 2 for Regulatory Review 69 Overview of Canopy Networks 5.6 BANDWIDTH AND AUTHENTICATION MANAGER Release 8 Canopy 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. Specify VLAN IDs to associate with the SM(s). This product is supported by the dedicated document Canopy 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 Motorola Canopy Prizm User Guide, Issue 3, and Motorola Canopy 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 Network Definition and Element Discovery Prizm allows the user to partition the entire Canopy network into criteria-based subsets that can be independently managed. To assist in this task of defining networks, Prizm auto discovers Canopy 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 Canopy AP, SM, BHM, BHS, PLV Bridge, PLV Modem, or CMMmicro, Prizm auto discovers the element to the extent possible. 70 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Overview of Canopy Networks includes the element in the network tree. shows general information. shows Canopy information. supports Canopy-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. Supported element types include Canopy Access Point Module Canopy Backhaul Master Module Canopy Backhaul Slave Module Canopy 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 Monitoring and Fault Management Prizm receives the traps that Canopy 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-Canopy 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. Element Management Prizm allows the user to perform any of the following operations on any specified element or group of elements:

5.7.3 Manage large amounts of SNMP MIB data. module passwords. Issue 2, December 2006 Draft 2 for Regulatory Review 71 Overview of Canopy Networks Release 8 IP addresses. other communications setup parameters. site information: Site Name, Site Location, and Site Contact parameters. Reset the element. 5.7.4 BAM Subsystem in Prizm Prizm Release 2.0 and later integrates Canopy 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. 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 Northbound Interface 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 Canopy 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 Motorola Canopy Prizm User Guide and associated release notes. 5.8 LICENSE MANAGEMENT Under the original licensing regime for Canopy networks, licenses were permanently tied to the Media Access Control (MAC) address of the equipment that was licensed or that 72 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Overview of Canopy Networks used the licensed feature. Thus, they were not transferable. Under server-based license management, for some functionalities, Canopy offers licenses that float upon demand within the network. are tied to only the hostID (MAC address) of the license management server for which they were ordered. 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 Canopy server-based licensing. Canopy 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 Canopy 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 Canopy licenses are listed in Table 19. Table 19: Correct placement of license keys On This Server Device LM Server LM Server1 In This Release License Key Must Be in Directory If This Platform LM 1.0 BAM 2.0 BAM 2.1 License Manager Server BAM Server, AP Auth Server

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

(APAS), Cap 2 PrizmEMS 1.0 PrizmEMS Server, Element Pack C:\Program Files\Motorola\Canopy\FLEXnet\license_files Windows

/usr/local/Canopy/FLEXnet/license_files Enterprise Linux C:\Program Files\Motorola\Canopy\FLEXnet\license_files Windows

/usr/local/Canopy/FLEXnet/license_files Enterprise Linux

/usr/local/canopy/include Enterprise Linux BAM Server2 C:\Program Files\Motorola\Canopy\FLEXnet\license_files Windows

/usr/local/Canopy/FLEXnet/license_files

/usr/local/Canopy/FLEXnet/license_files LM Server1 Enterprise Linux Enterprise Linux BAM Server2 C:\Program Files\Motorola\Canopy\FLEXnet\license_files Windows

/usr/local/Canopy/FLEXnet/license_files Enterprise Linux C:\Program Files\Motorola\Canopy\FLEXnet\license_files Windows

/usr/local/Canopy/Prizm/license_files Enterprise Linux LM Server3 PrizmEMS Server4 Issue 2, December 2006 Draft 2 for Regulatory Review 73 Overview of Canopy Networks In This Release License Key Must Be in Directory If This Platform C:\Program Files\Motorola\Canopy\FLEXnet\license_files Windows

/usr/local/Canopy/FLEXnet/license_files Enterprise Linux C:\Program Files\Motorola\Canopy\FLEXnet\license_files Windows Release 8 On This Server Device LM Server3 PrizmEMS 1.1 Prizm 2.0 and 2.1 for full mgmt Prizm 2.0 and 2.1 for BAM-

only or redundant BAM PrizmEMS Server, Element Pack PrizmEMS Server, Element Pack BAM Server, AP Auth Server

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

(APAS), Cap 2 Canopy Lite

/usr/local/Canopy/FLEXnet/license_files LM server5 Enterprise Linux C:\Program Files\Motorola\Canopy\FLEXnet\license_files Windows

/usr/local/Canopy/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 SPECIFICATIONS AND LIMITATIONS 5.9.1 Radios Canopy radio specifications are provided at http://motorola.canopywireless.com/products/specshome.php. 74 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 5.9.2 Cluster Management Products Overview of Canopy Networks Table 20: CMM2 specifications and limitations Specification or Limitation Canopy 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 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. Ethernet, GPS Sync, and GPS Coax Cables The use of cables that conform to the operational temperature of the product as well as being UV light protected is mandatory. Issue 2, December 2006 Draft 2 for Regulatory Review 75 Overview of Canopy Networks Release 8 Table 21: CMMmicro specifications and limitations Specification or Limitation Canopy System Range Enclosure Size Approximately 12 H x 10 W x 3 D

(Approximately 30 cm H x 25 cm W x 7.5 cm D) CMMmicro Weight (without DC power supply) Approximately 8 lb

(Approximately 3.5 k) 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) 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/motorola.htm. 5.9.3 300SS and 600SS Surge Suppressors Canopy Surge Suppressor specifications are provided at http://motorola.canopywireless.com/products/specshome.php. 76 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 6 DIFFERENTIATING AMONG COMPONENTS 6.1 INTERPRETING MODEL (PART) NUMBER The part number of a module typically represents Overview of Canopy Networks radio frequency band range. link distance range. the model number, which may indicate whether the module is Canopy 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 Canopy Advantage The third digit in the part number may indicate whether the module is an extended range, Canopy Advantage, or Canopy 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 Canopy Lite. 5 in the third position

(5250AP, for example) indicates that the module is Canopy Advantage. 0 in the third position (5200AP, for example) indicates that the module is Canopy. However, part numbering for 900-MHz APs and SMs differs from this general rule. All APs and SMs in this frequency band range are Canopy Advantage, but none of their part numbers use 5 in the third position. Issue 2, December 2006 Draft 2 for Regulatory Review 77 Overview of Canopy Networks Release 8 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. 78 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Overview of Canopy Networks 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. Issue 2, December 2006 Draft 2 for Regulatory Review 79 Overview of Canopy Networks 6.2 SORTED MODEL (PART) NUMBERS Release 8 The various model/part numbers of Canopy products are categorically listed in Table 22. Table 22: Canopy model numbers (part numbers) for AES and DES encryption modules Integrated Antenna Connectorized for Antenna Canopy Advantage Canopy Advantage DES AES DES AES DES AES DES AES 5750AP 5750SM 5751AP 5751SM 5700APC 5700BHC 5700BHC20 5700SMC 5701APC 5701BHC 5701BHC20 5701SMC 5750APC 5750SMC 5751APC 5751SMC e g n a R 5.7 GHz 5.4 GHz 5.1 GHz 5.2 GHz 2.4 GHz 5700AP 5700BH 5700BH20 5700BHRF 5700BHRF20 5700SM 5760SM 5400AP 5400BH 5400BH20 5400BHRF 5400BHRF20 5400SM 5202AP 5202BH 5202SM 5212BH20 5212BHRF20 5200AP 5200BH 5200SM 5210BHRF 5210BHRF20 5701AP 5701BH 5701BH20 5701BHRF 5701BHRF20 5701SM 5401AP 5401BH 5401BH20 5401BHRF 5401BHRF20 5401SM 5450AP 5450SM 5451AP 5451SM 5252AP 5252SM 5201AP 5201BH 5201SM 5211BH20 5211BHRF 5211BHRF20 5250AP 5250SM 5251AP 5251SM 2400AP 2400APWL 2400BH 2400BH20 2400BHRF 2400BHRF20 2400BHWL 2400BHWL20 2400BHWLRF 2400BHWLRF20 2400SM 2400SMWL 2401AP 2401APWL 2401BH 2401BH20 2401BHRF 2401BHRF20 2401BHWL 2401BHWL20 2401BHWLRF 2401BHWLRF20 2401SM 2401SMWL 900 MHz 2450AP 2450APWL 2450SM 2450SMWL 2451AP 2451APWL 2451SM 2451SMWL 9000AP 9000APF 9000SM 9000SMF 9001AP 9001APF 9001SM 9001SMF 9000APC 9000SMC 9001APC 9001SMC 80 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Overview of Canopy Networks Table 23: Canopy model numbers (part numbers) for proprietary encryption modules Range 5.7 GHz Integrated Antenna 5830BH 5830BH15 5730BH 5730BH20 Connectorized for Antenna 5830BHC 5830BHC15 5730BHC 5730BHC20 5.4 GHz 5430BH 5430BH20 5430BHC 5430BHC20 6.3 INTERPRETING ELECTRONIC SERIAL NUMBER (ESN) Canopy module labels contain a product serial number that could be significant in your dealings with Motorola 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 Canopy Network Updater Tool (CNUT). information that CNUT passes to external tools. 6.4 FINDING THE MODEL (PART) NUMBER AND ESN The labels and locations of Canopy module model (part) numbers and ESNs are shown in Table 24. Table 24: Labels and locations of model (part) numbers and ESNs Label and Location Numeric String Model (part) number PN outside S/N inside ESN/MAC address Older Modules Newer Modules Model # outside ESN outside Issue 2, December 2006 Draft 2 for Regulatory Review 81 Release 8 7 CANOPY LINK CHARACTERISTICS 7.1 UNDERSTANDING BANDWIDTH MANAGEMENT 7.1.1 Downlink Frame Contents Overview of Canopy Networks 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 Uplink Frame Contents 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 and an entry is older than 255 minutes, the oldest entry is removed and the ignored. 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). See Address Resolution Protocol on Page 162. Issue 2, December 2006 Draft 2 for Regulatory Review 83 Overview of Canopy Networks 7.1.3 Frame Structure The Canopy frame consists of Release 8 Variable numbers of uplink and downlink 64-byte data slots, subject to the following factors:

Maximum range decreases the number of available slots. Every two control slots that are reserved 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 (guard time), 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 These control slots are reserved contention slots for bandwidth requests. 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 the AP sends a Registration Request message to Prizm for authentication. a. b. following a successful challenge, Prizm returns an Authentication Grant message to the AP. 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. 84 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 7.1.4 Media Access Control and AP Capacity Overview of Canopy Networks 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 Canopy Slot Usage The frame illustrated in Figure 22 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 22: Uplink data slot usage The following statistics apply to Canopy frame slot usage:

Slot size 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 Data Transfer Capacity Canopy modules use Time Division Duplex (TDD) on a common frequency to divide frames for uplink (orange) and downlink (green) usage, as shown in Figure 23. Figure 23: TDD dividing Canopy frames 7.1.7 Maximum Information Rate (MIR) Parameters Canopy point-to-multipoint links use the following four MIR parameters for bandwidth management:

Issue 2, December 2006 Draft 2 for Regulatory Review 85 Release 8 Overview of Canopy Networks 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 Canopy 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. 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 292. 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 24. NOTE:

In these figures, entry refers to the setting in the data rate parameter, not the burst allocation parameter. 86 Draft 2 for Regulatory Review Issue 2, December 2006 Overview of Canopy Networks Figure 24: Uplink and downlink rate caps adjusted to apply aggregate cap Release 8 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 25. 7.1.8 Figure 25: Uplink and downlink rate cap adjustment example 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. Committed Information Rate 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 292.) The operator can disable the CIR feature in the SM without deleting the CIR configuration data. Issue 2, December 2006 Draft 2 for Regulatory Review 87 uplink cap enforced =uplink entry x aggregate cap for the SMuplink entry + downlink entrydownlink cap enforced =downlink entry x aggregate cap for the SMuplink entry + downlink entryuplink cap enforced =2,000 kbps x 7,000 kbps2,000 kbps + 10,000 kbps= 1,167 kbpsdownlink cap enforced =10,000 kbps x 7,000 kbps2,000 kbps + 10,000 kbps= 5,833 kbps Release 8 Overview of Canopy Networks 7.1.9 Bandwidth from the SM Perspective 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. 7.1.10 Example download times for various arbitrary tiers of service are shown in Table 60 on Page 384 and Table 61 on Page 385. Interaction of Burst Allocation and Sustained Data Rate Settings 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 High-priority Bandwidth To support low-latency traffic such as VoIP (Voice over IP) or video, the Canopy system implements a high-priority channel. This channel does not affect the inherent latencies in the Canopy 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. A Canopy module prioritizes traffic by 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 Canopy 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. 88 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Overview of Canopy Networks 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 Canopy 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. Canopy 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. An example of the DiffServe tab in the Configuration page and parameter descriptions are provided under DiffServe Tab of the AP on Page 256. This tab and its rules are identical from module type to module type in Canopy. 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 Canopy 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 Canopy network when you have broadly implemented Code Point values, such as via SNMP. The standard channel in Canopy PTMP communications is illustrated in Figure 26. Issue 2, December 2006 Draft 2 for Regulatory Review 89 Overview of Canopy Networks Release 8 Figure 26: Canopy channel, 75% downlink, 0% high priority in uplink 7.1.12 Hardware Scheduling Canopy 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 only 100 SMs (instead of 200). IMPORTANT!

In a Canopy BH link with Canopy T1/E1 Multiplexers, the BHs must be configured for an uplink/downlink ratio of 50% uplink/50% downlink. The Canopy T1/E1 Multiplexers are full duplex. Canopy Release 8 requires APs, BHs, and AES SMs to be Series P9 or later hardware.3 The characteristics of hardware scheduling in a Canopy sector are summarized in Table 25. 3 See Designations for Hardware in Radios on Page 367. 90 Draft 2 for Regulatory Review Issue 2, December 2006 Con-trolBeaconDataAP Transmit(Downlink)AP Receive(Uplink)DataAckCon-trolAckCon-trolBeaconDataAP Transmit(Downlink)AP Receive(Uplink)DataAckCon-trolAck Overview of Canopy Networks Table 25: Characteristics of hardware scheduling Category Factor Treatment Aggregate throughput, less additional overhead 14 Mbps Throughput ACK slots in downlink used for data except when request for uplink is present Latency 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 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 Support for Transmit Frame Spreading feature In Release 7.0 and later Capability CIR NOTES:

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

Power requirements for modules that run hardware scheduling affect the recommended maximums for power cord length feeding the CMMmicro. See Table 55 on Page 344. However, the requirements do not affect the maximums for the CMM2. Release 8 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. 7.1.13 2X Operation A General tab option in both Advantage SMs and some Canopy SMs provides double the aggregate throughput for SMs that are nearer than half of the distance range from the AP Issue 2, December 2006 Draft 2 for Regulatory Review 91 Overview of Canopy Networks Release 8

(the nearest one-fourth of the SMs in the sector). The requirements of this feature are as follows:

The AP must be an Advantage AP. The SM must be near the AP, as described above. The SM must be of the P9 hardware series and enabled for hardware scheduling. See Designations for Hardware on Page 367. 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 26. Table 26: Effect of 2X operation on throughput for the SM Type of SM 900 MHz3 Advantage Any other frequency band range Typical Aggregate Rates1 Sustained2 4 Mbps Burst2 4 Mbps 14 Mbps 14 Mbps Canopy P9 Any frequency band range except 900 MHz 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 14 Mbps 7 Mbps Radio tab of the Configuration page in the AP. 3. All 900-MHz modules are Advantage. 92 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Overview of Canopy Networks 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 Canopy P7 and P8 SMs, do not deploy Canopy Advantage SMs or Canopy P9 SMs beyond half the distance range of the AP. At this distance, steady and reliable 2X operation typically is not achievable. Deploy the Canopy 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 do not necessarily indicate a poor quality link. Efficiency of 45% in 2X operation is equivalent to efficiency of 90% in 1X. If you read efficiency between 45%

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 45% or greater for 2X operation. Where readings are lower, you are unlikely to solve the RF problem by enabling 1X operation. (For example, if you read 40% at 2X, you can expect 80% at 1X.) In these cases, you may be able to achieve better efficiencies by re-

aiming the SM, mounting it elsewhere, or retrofitting it with a reflector dish. 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. Issue 2, December 2006 Draft 2 for Regulatory Review 93 Overview of Canopy Networks Release 8 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 The 2X Rate parameter is disabled in the General tab of the Configuration or P8). page in the SM. 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 55 on Page 344. 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. 7.2 UNDERSTANDING SYNCHRONIZATION 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 GPS Synchronization 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 Canopy Cluster Management Module (CMM) contains a Motorola Oncore GPS Receiver. The CMM is a critical element in the operation of the Canopy system. At one 94 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Overview of Canopy Networks 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 Canopy 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 Canopy 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. For example, in Figure 27, AP4 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 27: One unsynchronized AP in cluster Issue 2, December 2006 Draft 2 for Regulatory Review 95 Overview of Canopy Networks Release 8 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 Canopy 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 Canopy 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 Canopy 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 Canopy modules, except by GPS timing (shown in Figure 28). Figure 28: GPS timing throughout the Canopy network 7.2.2 Passing Sync in a Single Hop 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. 96 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 7.2.3 Overview of Canopy Networks Passing Sync in an Additional Hop 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 29. Figure 29: 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 30. Issue 2, December 2006 Draft 2 for Regulatory Review 97 CMMAPAPSMSMSM21344 Overview of Canopy Networks Release 8 Figure 30: 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 31. Figure 31: 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 369. All Canopy 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 59.) 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. 98 Draft 2 for Regulatory Review Issue 2, December 2006 CMMBH-M-APBH-S-SM2134CMMBH-M-APBH-S-SMSM21344 Release 8 8 MEETING LINK REQUIREMENTS 8.1 AP-SM LINKS Overview of Canopy Networks 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 Canopy 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 Canopy 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 14 on Page 64. 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 Canopy 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 27. Issue 2, December 2006 Draft 2 for Regulatory Review 99 Overview of Canopy Networks Release 8 Table 27: 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 somewhat decreased2 no effect Increasing the average bandwidth allotted to the SMs that register in the AP NOTES:

1. For non 900-MHz APs, the AP accepts a Max Range value of up to 30 no effect, even when the additional bandwidth is used. miles (48 km). See Max Range on Page 242. 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 Canopy Advantage AP is shown in Table 28. Table 28: Comparison of SM products with Canopy Advantage AP Product Maximum Sustained Aggregate Throughput to a Single SM Burst Cap on Committed Information Rate Upgradability Canopy Advantage SM 14 Mbps 14 Mb none none Canopy SM 7 Mbps 14 Mb none to Advantage SM capabilities to 1, 2, 4, or 7 Mbps Canopy Lite SM as purchased Canopy Lite SM upgraded to 1 Mbps Canopy Lite SM upgraded to 2 Mbps Canopy Lite SM upgraded to 4 Mbps Canopy 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 8.2 BH-BH LINKS Canopy 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. 100 Draft 2 for Regulatory Review Issue 2, December 2006

Release 8 18.1.6 Security Tab of the AP Installation and Configuration Guide An example of the Security tab of the AP is displayed in Figure 86. Figure 86: Security tab of AP, example In the Security tab of the AP, you may set the following parameters. 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. Issue 2, December 2006 Draft 2 for Regulatory Review 251 Installation and Configuration Guide Release 8 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 380. 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. 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. 252 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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. 18.1.7 VLAN Tab of the AP An example of the AP VLAN tab is displayed in Figure 87. Figure 87: 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. Issue 2, December 2006 Draft 2 for Regulatory Review 253 Installation and Configuration Guide Release 8 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. 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. 254 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 18.1.8 VLAN Membership Tab of the AP Installation and Configuration Guide An example of the VLAN Membership tab of the AP is displayed in Figure 88. Figure 88: 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. Issue 2, December 2006 Draft 2 for Regulatory Review 255 Installation and Configuration Guide 18.1.9 DiffServe Tab of the AP An example of the DiffServe tab of the AP is displayed in Figure 89. Release 8 Figure 89: DiffServe tab of AP, example 256 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 You may set the following DiffServe tab parameters. Installation and Configuration Guide 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 119. 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 89. 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. Issue 2, December 2006 Draft 2 for Regulatory Review 257 Installation and Configuration Guide 18.1.10 Unit Settings Tab of the AP An example of the Unit Settings tab of the AP is shown in Figure 90. Release 8 Figure 90: 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 375. The Unit Settings tab also contains the following buttons. 258 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 CONFIGURING AN SM FOR THE DESTINATION 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 373. Issue 2, December 2006 Draft 2 for Regulatory Review 259 Installation and Configuration Guide 18.2.1 General Tab of the SM An example of a General tab in the SM is displayed in Figure 91. Release 8 Figure 91: 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. 260 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 91. Issue 2, December 2006 Draft 2 for Regulatory Review 261 Installation and Configuration Guide Release 8 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 369. 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 NAT and IP Tabs of the SM with NAT Disabled An example of the NAT tab in an SM with NAT disabled is displayed in Figure 92. 262 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide Figure 92: NAT tab of SM with NAT disabled, example This implementation is illustrated in Figure 46 on Page 157. In the NAT tab of an SM with NAT disabled, you may set the following parameters. Issue 2, December 2006 Draft 2 for Regulatory Review 263 Installation and Configuration Guide Release 8 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 268. 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. 264 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Radio Public Network Interface Configuration, DHCP State This parameter is not configurable when NAT is disabled. Installation and Configuration Guide 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 93. Issue 2, December 2006 Draft 2 for Regulatory Review 265 Installation and Configuration Guide Release 8 Figure 93: IP tab of SM with NAT disabled, example This implementation is illustrated in Figure 46 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 377. 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. 266 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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. Issue 2, December 2006 Draft 2 for Regulatory Review 267 Installation and Configuration Guide 18.2.3 NAT and IP Tabs of the SM with NAT Enabled Release 8 An example of the NAT tab in an SM with NAT enabled is displayed in Figure 94. Figure 94: NAT tab of SM with NAT enabled, example In the NAT tab of an SM with NAT enabled, you may set the following parameters. 268 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 268. 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. Issue 2, December 2006 Draft 2 for Regulatory Review 269 Installation and Configuration Guide Release 8 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. 270 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 DHCP Client Enable/Disable Select either Installation and Configuration Guide 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 48 on Page 159. The implementation of NAT with DHCP client and DHCP server is illustrated in Figure 47 on Page 158. The implementation of NAT without DHCP is illustrated in Figure 50 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 49 on Page 50. The implementation of NAT with DHCP client and DHCP server is illustrated in Figure 47 on Page 158. The implementation of NAT without DHCP is illustrated in Figure 50 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. Issue 2, December 2006 Draft 2 for Regulatory Review 271 Installation and Configuration Guide Release 8 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 95. Figure 95: 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. 272 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Reboot When you click this button Installation and Configuration Guide 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 95. 18.2.4 Radio Tab of the SM An example of the Radio tab in the SM is displayed in Figure 96. Figure 96: 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. Issue 2, December 2006 Draft 2 for Regulatory Review 273 Installation and Configuration Guide Release 8 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 Canopy 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. 274 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 Canopy 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 326. 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. Issue 2, December 2006 Draft 2 for Regulatory Review 275 Installation and Configuration Guide 18.2.5 SNMP Tab of the SM An example of the SNMP tab in an SM is displayed in Figure 97. Release 8 Figure 97: 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 Canopy. 276 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 378. 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. Issue 2, December 2006 Draft 2 for Regulatory Review 277 Installation and Configuration Guide Release 8 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. 278 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 18.2.6 Quality of Service (QoS) Tab of the SM Installation and Configuration Guide An example of the Quality of Service (QoS) tab in the SM is displayed in Figure 98. Figure 98: 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 85 Setting the Configuration Source on Page 292. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 88 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 85 Setting the Configuration Source on Page 292. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 88 Issue 2, December 2006 Draft 2 for Regulatory Review 279 Installation and Configuration Guide Release 8 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 85 Setting the Configuration Source on Page 292. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 88 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 85 Setting the Configuration Source on Page 292. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 88 Low Priority Uplink CIR See Committed Information Rate on Page 87 Setting the Configuration Source on Page 292. Low Priority Downlink CIR See Committed Information Rate on Page 87 Setting the Configuration Source on Page 292. Hi Priority Channel See High-priority Bandwidth on Page 88 Setting the Configuration Source on Page 292. Hi Priority Uplink CIR See High-priority Bandwidth on Page 88 Committed Information Rate on Page 87 Setting the Configuration Source on Page 292. Hi Priority Downlink CIR See High-priority Bandwidth on Page 88 280 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide Committed Information Rate on Page 87 Setting the Configuration Source on Page 292. 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. Issue 2, December 2006 Draft 2 for Regulatory Review 281 Installation and Configuration Guide 18.2.7 Security Tab of the SM An example of the Security tab in an SM is displayed in Figure 99. Release 8 Figure 99: Security tab of SM, example 282 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 385. 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, Canopy 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. 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. Issue 2, December 2006 Draft 2 for Regulatory Review 283 Installation and Configuration Guide Release 8 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 VLAN Tab of the SM An example of the VLAN tab in an SM is displayed in Figure 100. Figure 100: VLAN tab of SM, example 284 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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. 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. Issue 2, December 2006 Draft 2 for Regulatory Review 285 Installation and Configuration Guide 18.2.9 VLAN Membership Tab of the SM An example of the VLAN Membership tab in an SM is displayed in Figure 101. Release 8 Figure 101: VLAN Membership tab of SM, example 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. 286 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 18.2.10 DiffServe Tab of the SM Installation and Configuration Guide An example of the DiffServe tab in an SM is displayed in Figure 102. Figure 102: DiffServe tab of SM, example Issue 2, December 2006 Draft 2 for Regulatory Review 287 Installation and Configuration Guide In the DiffServe tab of the SM, you may set the following parameters. Release 8 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 119. 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 89. 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. 288 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 18.2.11 Protocol Filtering Tab of the SM Installation and Configuration Guide An example of the Protocol Filtering tab in an SM is displayed in Figure 103. Figure 103: 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 378. Issue 2, December 2006 Draft 2 for Regulatory Review 289 Installation and Configuration Guide Release 8 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 378. 18.2.12 NAT Port Mapping Tab of the SM An example of the NAT Port Mapping tab in an SM is displayed in Figure 104. Figure 104: NAT Port Mapping tab of SM, example 290 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide In the NAT Port Mapping tab of the SM, you may set the following parameters. Port Map 1 to 10 18.2.13 Unit Settings Tab of the SM An example of the Unit Settings tab in an SM is displayed in Figure 105. Figure 105: 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. Issue 2, December 2006 Draft 2 for Regulatory Review 291 Installation and Configuration Guide Release 8 See Overriding Forgotten IP Addresses or Passwords on AP, SM, or BH on Page 375. 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 SETTING THE CONFIGURATION SOURCE 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 49. 292 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide Table 49: 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 50 and Table 51. For any SM whose Authentication Mode parameter is set to Authentication Required, the listed settings are derived as shown in Table 50. Table 50: Where feature values are obtained for an SM with authentication required Configuration Source Setting in the AP MIR Values VLAN Values Values are obtained from BAM SM BAM SM BAM SM High Priority Channel State BAM SM CIR Values BAM SM BAM BAM, then SM BAM, then SM BAM, then SM BAM+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 Canopy Release 8. For any SM whose Authentication Mode parameter is not set to Authentication Required, the listed settings are derived as shown in Table 51. Issue 2, December 2006 Draft 2 for Regulatory Review 293 Installation and Configuration Guide Release 8 Table 51: Where feature values are obtained for an SM with authentication disabled Configuration Source Setting in the AP BAM SM BAM+SM Values are obtained from MIR Values VLAN Values High Priority Channel State CIR Values AP SM SM AP SM SM AP SM SM 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 CONFIGURING A BH TIMING MASTER FOR THE DESTINATION NOTE:

The OFDM Series BHs 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 373. 294 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 18.4.1 General Tab of the BHM Installation and Configuration Guide An example of the General tab in a BHM is displayed in Figure 106. Figure 106: General tab of BHM, example Issue 2, December 2006 Draft 2 for Regulatory Review 295 Installation and Configuration Guide Release 8 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. 296 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 91. 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. Issue 2, December 2006 Draft 2 for Regulatory Review 297 Installation and Configuration Guide 18.4.2 IP Tab of the BHM An example of an IP tab in a BHM is displayed in Figure 107. Release 8 Figure 107: 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 377. 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. 298 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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. Issue 2, December 2006 Draft 2 for Regulatory Review 299 Installation and Configuration Guide 18.4.3 Radio Tab of the BHM An example of the Radio tab in a BHM is displayed in Figure 108. Release 8 Figure 108: 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 Canopy 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). 300 Draft 2 for Regulatory Review Issue 2, December 2006

Release 8 Installation and Configuration Guide 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). Canopy 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 Canopy 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 326. The Radio tab also provides the following buttons. Issue 2, December 2006 Draft 2 for Regulatory Review 301 Installation and Configuration Guide Release 8 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. 302 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 18.4.4 SNMP Tab of the BHM Installation and Configuration Guide An example of the SNMP tab in a BHM is displayed in Figure 109. Figure 109: SNMP tab of BHM, example In the SNMP tab of the BHM, you may set the following parameters. Issue 2, December 2006 Draft 2 for Regulatory Review 303 Installation and Configuration Guide Release 8 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 Canopy. 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. 304 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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. Issue 2, December 2006 Draft 2 for Regulatory Review 305 Installation and Configuration Guide 18.4.5 Security Tab of the BHM An example of the Security tab in a BHM is displayed in Figure 110. Release 8 Figure 110: 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. 306 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Encryption Specify the type of air link security to apply to this BHM:

Installation and Configuration Guide 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. Issue 2, December 2006 Draft 2 for Regulatory Review 307 Installation and Configuration Guide Reboot When you click this button Release 8 the module reboots. 1. 2. any changes that you saved by a click of the Save Changes button are implemented. 18.4.6 DiffServe Tab of the BHM An example of the DiffServe tab in a BHM is displayed in Figure 111. Figure 111: DiffServe tab of BHM, example 308 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 119. 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 89. 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. Issue 2, December 2006 Draft 2 for Regulatory Review 309 Installation and Configuration Guide 18.4.7 Unit Settings Tab of the BHM An example of the Unit Settings tab of the BHM is displayed in Figure 112. Release 8 Figure 112: 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 375. The Unit Settings tab also contains the following buttons. 310 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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. Issue 2, December 2006 Draft 2 for Regulatory Review 311 Installation and Configuration Guide 18.5 CONFIGURING A BH TIMING SLAVE FOR THE DESTINATION Release 8 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 373. 18.5.1 General Tab of the BHS An example of the General tab in a BHS is displayed in Figure 113. Figure 113: General tab of BHS, example In the General tab of the BHS, you may set the following parameters. 312 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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. Issue 2, December 2006 Draft 2 for Regulatory Review 313 Installation and Configuration Guide Release 8 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 91. 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 369. 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. 314 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 18.5.2 IP Tab of the BHS An example of the IP tab in a BHS is displayed in Figure 114. Installation and Configuration Guide Figure 114: 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 377. 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 BHS to communicate on the network. The default subnet mask is 255.255.0.0. See Allocating Subnets on Page 162. Issue 2, December 2006 Draft 2 for Regulatory Review 315 Installation and Configuration Guide Release 8 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. 18.5.3 Radio Tab of the BHS An example of the Radio tab in a BHS is displayed in Figure 115. 316 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide Figure 115: 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 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 Canopy 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 Issue 2, December 2006 Draft 2 for Regulatory Review 317 Installation and Configuration Guide Release 8 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 Canopy 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 326. 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. 318 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 18.5.4 SNMP Tab of the BHS Installation and Configuration Guide An example of the SNMP tab in a BHS is displayed in Figure 116. Figure 116: 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 Canopy. Issue 2, December 2006 Draft 2 for Regulatory Review 319 Installation and Configuration Guide Release 8 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. 320 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 Quality of Service (QoS) Tab of the BHS An example of the Quality of Service tab of the BHS is displayed in Figure 117. Figure 117: 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 87 Setting the Configuration Source on Page 292. Low Priority Downlink CIR See Committed Information Rate on Page 87 Issue 2, December 2006 Draft 2 for Regulatory Review 321 Installation and Configuration Guide Setting the Configuration Source on Page 292. Release 8 18.5.6 Security Tab of the BHS An example of the Security tab in a BHS is displayed in Figure 118. Figure 118: 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:

Canopy recommends that you enter 32 characters to achieve the maximal security from this feature. 322 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 385. 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. Issue 2, December 2006 Draft 2 for Regulatory Review 323 Installation and Configuration Guide 18.5.7 DiffServe Tab of the BHS An example of the DiffServe tab in a BHS is displayed in Figure 119. Release 8 Figure 119: DiffServe tab of BHS, example 324 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 119. 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 89. 18.5.8 Unit Settings Tab of the BHS An example of the Unit Settings tab in a BHS is displayed in Figure 120. Figure 120: 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. Issue 2, December 2006 Draft 2 for Regulatory Review 325 Installation and Configuration Guide Release 8 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 375. 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 ADJUSTING TRANSMITTER OUTPUT POWER Authorities may require transmitter output power to be adjustable and/or lower than the highest that a module produces. Canopy adjustable power modules include a Radio tab parameter to reduce power to achieve compliance. If you set this parameter to lower than the range of the hardware in a given module, the value is automatically reset to the lowest value the hardware is capable of. The best practice is to maintain awareness of applicable regulations. calculate the permissible transmitter output power for the module. confirm that the initial power setting is compliant. 326 Draft 2 for Regulatory Review Issue 2, December 2006 Installation and Configuration Guide confirm that the power setting is compliant following any reset of the module to factory defaults. Adjust (usually reduce) transmit power so as to have a good signal at the receiver without transmitting excesss power. Note this usually means reducing transmit power for close-in SMs, while setting the AP to reach its most distant SM. For BHs, this usually means reducing the power symmetrically. IMPORTANT!

In the European Union, operators are under regulatory requirements to control transmit power so as to enhance sharing with other band users. Release 8 The total gain per antenna in 900-MHz and 5.7-GHz Canopy radios is stated in Table 52. Table 52: Total gain per antenna Antenna 900-MHz Integrated 900-MHz Connectorized with Mars, MTI, or Maxrad antenna. Antenna Gain Cable Loss1 12.5 dBi 0.2 dB Net Gain 12 dBi 10 to 10.5 dBi 0.3 dB 10 dBi 5.7-GHz Connectorized variable 0.3 dB + from any additional cable See Note 2 15.5 dBi 5.7-GHz Connectorized with Mars antenna NOTES:

1. Received signal measurements take this loss into account, but the transmitter output power setting cannot. Set the transmitter output power higher by this amount. 0.3 dB 15 dBi 2. Antenna gain minus cable loss. Integrated patch antenna and reflector gains are provided in Table 53. Table 53: Patch antenna and reflector gain Gain Frequency Band Range Patch Antenna Reflector 2.4 GHz 5.2, 5.4, or 5.7 GHz 8 dBi 7 dBi 11dBi 18dBi Issue 2, December 2006 Draft 2 for Regulatory Review 327 Installation and Configuration Guide The calculation of transmitter output power is as follows:

Release 8 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 54. 328 Draft 2 for Regulatory Review Issue 2, December 2006 TransmitterOutput Power= EIRPPatch Antenna GainReflector Gain--solve, then setin parameterfrom applicableregulationsfrom the precedingtablefrom the precedingtable Release 8 Installation and Configuration Guide Table 54: 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) Transmitter Output Power Setting AP, SM, or BH with No Reflector SM or BH with Reflector 24 dBm 26 dBm1 Depends on antenna 25 dBm 2.4 GHz Integrated 5.2 GHz Integrated 5.4 GHz Integrated U.S.A. Canada CEPT states U.S.A. Canada CEPT states U.S.A Canada Depends on antenna gain 20 dBm (100 mW) 12 dBm 25 dBm 1 dBm 30 dBm (1 W) 23 dBm 30 dBm (1 W) 23 dBm 5 dBm 5.7 GHz Connectorized UK 33 dBm (2 W) Depends on antenna U.S.A 5.7 GHz Connectorized2 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. 36 dBm (4W) 21 dBm 2. Only AP available Issue 2, December 2006 Draft 2 for Regulatory Review 329 Release 8 19 INSTALLING COMPONENTS Installation and Configuration Guide RECOMMENDATION:

Use shielded cable for all Canopy 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 PDA ACCESS TO CANOPY MODULES 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 121. Issue 2, December 2006 Draft 2 for Regulatory Review 331 Installation and Configuration Guide Release 8 Figure 121: PDA Quick Status tab, example An example of the Spectrum Analyzer tab for PDAs is displayed in Figure 122. For additional information about the Spectrum Analyzer feature, see Monitoring the RF Environment on Page 365. Figure 122: PDA Spectrum Analyzer tab of SM, example Examples of the Spectrum Results and Information tabs for PDAs are shown in Figure 123 and Figure 124. 332 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide Figure 123: PDA Spectrum Results tab of SM, example Figure 124: PDA Information tab of SM, example Examples of the AP Evaluation and Aim tabs for PDAs are shown in Figure 125 and Figure 126. Issue 2, December 2006 Draft 2 for Regulatory Review 333 Installation and Configuration Guide Release 8 Figure 125: PDA AP Evaluation tab of SM, example Figure 126: PDA Aim tab of SM, example 19.2 INSTALLING AN AP To install the Canopy AP, perform the following steps. Procedure 19: Installing the AP 334 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 Canopy 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 Canopy 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 Canopy 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 Canopy 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 52 on Page 178.) 6. Attach the cables to the AP.

(See Procedure 5 on Page 184.) NOTE: When power is applied to a Canopy 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 44 on Page 179.

=========================== end of procedure ===========================

19.3 INSTALLING A CONNECTORIZED FLAT PANEL ANTENNA 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 Motorola (Part Number SMMB-1 and consisting of a mounting bracket and L-shaped aluminum tube) holds one Canopy 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 59. Issue 2, December 2006 Draft 2 for Regulatory Review 335 Installation and Configuration Guide Release 8 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 Canopy 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 INSTALLING A GPS ANTENNA 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 127. 4. Slide the GPS antenna bracket onto the U-bolts. 5. Slide the ring washers (provided) onto the U-bolts. 336 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 127: Detail of GPS antenna mounting 19.4.1 Recommended Materials for Cabling the GPS Antenna 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 Cabling the GPS Antenna Connect the GPS coax cable to the female N-connector on the GPS antenna. 19.5 INSTALLING A CMM2 Ensure that you comply with standard local or national electrical and climbing procedures when you install the CMM2. 19.5.1 CMM2 Installation Temperature Range 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). 19.5.2 Recommended Tools for Mounting a CMM2 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 Issue 2, December 2006 Draft 2 for Regulatory Review 337 Installation and Configuration Guide 19.5.3 Mounting a CMM2 Perform the following procedure to mount the CMM2. Procedure 21: Mounting the CMM2 1. Ensure that the mounting position Release 8 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 128. b. attach the CMM2 flanges to the V-bracket. 4. 5. Figure 128: Detail of pole mounting

=========================== end of procedure ===========================

19.5.4 Cabling a CMM2 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. 338 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 52 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 129. Fuse receptacle AC power connectors 115/230 V switch Figure 129: Location of 115-/230-volt switch 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 Issue 2, December 2006 Draft 2 for Regulatory Review 339 Installation and Configuration Guide Release 8 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 130. Figure 130: 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 131 on Page 341 is a photograph of a properly wired CMM2. 340 Draft 2 for Regulatory Review Issue 2, December 2006 J3 GPS Sync87654321J1 Ethernet In87654321UPLINK PORT:NON-CANOPYETHERNETDEVICESJ2 Ethernet to Switch87654321BLKWHTGRNBLKWHTGRNBLKWHTGRNBLKBT-0588BLKGRNWHTNEUTRALGROUNDHOTTO ACLINESOURCEBT-0488-011TO DOOR GROUNDBT-0563-XXXBT-0563-XXXBT-0563-XXXBT-0563-XXXBT-0563-XXXBT-0563-XXXBT-0563-XXXBT-0563-XXXBT-0562-XXXBT-0562-XXXBT-0562-XXXBT-0562-XXXBT-0562-XXXBT-0562-XXXBT-0562-XXXBT-0562-XXXTO AP GPSTO AP ETHERNETETHERNET SWITCH PORTSBT-0556-008BT-0556-008BT-0556-008BT-0556-008BT-0556-008BT-0556-008BT-0556-008BT-0556-008TO ETHERNET SWICTH BT-0556-008BT-0556-008 BT-0556-008BT-0556-008 BT-0556-008BT-0556-008 BT-0556-008BT-0556-008TO J2TO GPSANTENNABT-0555-023Interconnect BoardGPSReceiverPower SupplyStrain relief strap forincoming power wiringWARNING: DISCONNECT ALL POWER BEFORE SERVICING+-+-115/230V SwitchReplace Fuse withType FSM 3.15A+-+BT-0588Remove lines from power supply if using external DC supplyMasterPWR LED Release 8 Installation and Configuration Guide Figure 131: Canopy 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 131 on Page 341. 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]

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

) the Ethernet cable. The Issue 2, December 2006 Draft 2 for Regulatory Review 341 Release 8 Installation and Configuration Guide Figure 53 on Page 180. 14. Connect GPS coaxial cable to the N-connector on the outside of the CMM2. See 15. Connect AC or DC power to the CMM2, consistent with Figure 130 on Page 340. 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 132. Figure 132: 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 Verifying CMM2 Connections 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 INSTALLING A CMMmicro Ensure that you comply with standard local or national electrical and climbing procedures when you install the CMMmicro. 342 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 19.6.1 CMMmicro Temperature Range Installation and Configuration Guide 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 Recommended Tools for Mounting a CMMmicro 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 Mounting a CMMmicro 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 128 on Page 338. e. attach the CMMmicro flanges to the V-bracket. 4.

=========================== end of procedure ===========================

19.6.4 Installing the Power Supply for the CMMmicro 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. Issue 2, December 2006 Draft 2 for Regulatory Review 343 Installation and Configuration Guide Release 8 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 55: 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 76: CMMmicro connections on Page 220. 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 ===========================

19.6.5 Cabling a CMMmicro 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 52 on Page 178. 344 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 2. Review the schematic drawing inside the CMMmicro and see Figure 76: CMMmicro connections on Page 220. 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 Canopy 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]

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

) 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 ===========================

19.6.6 Verifying CMMmicro Connections 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.) Issue 2, December 2006 Draft 2 for Regulatory Review 345 Installation and Configuration Guide Release 8

=========================== end of procedure ===========================

19.7 INSTALLING AN SM 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 349). 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, Motorola offers the SMMB-1 mounting bracket. For mounting 900 MHz SMs, Motorola offers the SMMB-2 mounting bracket.) 3. Remove the base cover of the SM. (See Figure 52 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 Canopy Passive Reflector dish assembly as shown in Figure 133. 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. Stainless steel hose clamps Reflector dish arm Figure 133: SM attachment to reflector arm 346 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 6. Use stainless steel hose clamps or equivalent fasteners to lock the SM into position. NOTE: The SM grounding method is shown in Figure 134. Figure 134: SM grounding per NEC specifications 7. Remove the cover of the 300SS Surge Suppressor. Issue 2, December 2006 Draft 2 for Regulatory Review 347 Installation and Configuration Guide Release 8 KEY TO CALLOUTS 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 Canopy 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 135: Internal view of Canopy 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. 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. 348 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 136: Audible Alignment Tone kit, including headset and connecting cable d. Adjust the module slightly until you hear the highest pitch and highest e. volume. If the Configuration web page of the SM contains a 2X Rate parameter, set it back to Enable. 19. When you have achieved the best signal (highest pitch, loudest volume), lock the SM in place with the mounting hardware.

=========================== end of procedure ===========================

19.8 VERIFYING AN AP-SM LINK 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 Issue 2, December 2006 Draft 2 for Regulatory Review 349 Installation and Configuration Guide Release 8 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 66 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 434. 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 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. 350 Draft 2 for Regulatory Review Issue 2, December 2006

Release 8 Installation and Configuration Guide 7. Open the Session Status tab in the Home page of the AP. NOTE: An example of this page is shown in Figure 137. Figure 137: AP/SM link status indications in the AP Session Status tab 8. Find the Session Count line under the MAC address of the SM. Issue 2, December 2006 Draft 2 for Regulatory Review 351

Release 8 Improper dish, tube, and module positions for this case are illustrated in Figure 139. Installation and Configuration Guide

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

Figure 139: Incorrect mount with reflector dish 19.9.2 Modules Mounted at Different Elevations 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 40 on Page 145). 19.9.3 Mounting Assembly 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 140. Issue 2, December 2006 Draft 2 for Regulatory Review 353 Installation and Configuration Guide Release 8 Figure 140: Mounting assembly, exploded view 19.10 INSTALLING A BH TIMING MASTER To install the Canopy 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 Canopy Passive Reflector dish assembly as shown in Figure 141. RECOMMENDATION:

The arm is molded to receive and properly aim the module relative to the aim of the dish. ( See Figure 138 on Page 352.) Stainless steel hose clamps should be used for the attachment. 354 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide Stainless steel hose clamps Reflector dish arm Figure 141: 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 Canopy 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 Canopy 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 Canopy 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 Canopy 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 52 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 Canopy 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. 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 ===========================

Issue 2, December 2006 Draft 2 for Regulatory Review 355 Installation and Configuration Guide 19.11 INSTALLING A BH TIMING SLAVE Installing a Canopy BHS consists of two procedures:

Release 8 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 357). Procedure 31: Installing the BHS 1. Choose the best mounting location for the BHS. 2. Remove the base cover of the BHS. (See Figure 52 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 Canopy Passive Reflector dish assembly as shown in Figure 133 on Page 346. 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. 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. 356 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide b. At the BHS, connect the RJ-11 6-pin connector of the Alignment Tool Headset (shown in Figure 136 on Page 349) 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 UPGRADING A BH LINK TO BH20 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 VERIFYING A BH LINK 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 71 on Page 210), 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 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. Issue 2, December 2006 Draft 2 for Regulatory Review 357 Installation and Configuration Guide Release 8 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 434. 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 142. 358 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide Figure 142: 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 ===========================

Issue 2, December 2006 Draft 2 for Regulatory Review 359 Release 8 20 VERIFYING SYSTEM FUNCTIONALITY Installation and Configuration Guide 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 ===========================

Issue 2, December 2006 Draft 2 for Regulatory Review 361 Release 8 Operations Guide OOPERATIONS PERATIONS GGUIDEUIDE Issue 2, December 2006 Draft 2 for Regulatory Review 363 Release 8 21 GROWING YOUR NETWORK Keys to successfully growing your network include monitoring the RF environment. considering software release compatibility. redeploying modules appropriately and quickly. Operations Guide 21.1 MONITORING THE RF ENVIRONMENT 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 Spectrum Analyzer IMPORTANT!

The following sections describe the use of a Canopy module in scan mode to analyze the RF spectrum. While a module is in the scan mode, no RF connectivity to that module is possible until either you click Disable on the Spectrum Analyzer page or 15 minutes elapses since the module entered the scan mode. For this reason do not enable the spectrum analyzer from an RF-connected module.

(No readings will be displayed when the RF connection is re-

established.) be advised that, if you enable the spectrum analyzer by Ethernet connection, any current RF connection to that module drops. You can use any AP, SM, or BHS to see at once the frequency and power level of any detectable signal that is within, above, or 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 Canopy Modules on Page 331.) To enter the scan mode and view readings, click Enable. 21.1.2 Graphical Spectrum Analyzer Display An SM/BHS displays the graphical spectrum analyzer. An example of the Spectrum Analyzer tab is shown in Figure 143. Issue 2, December 2006 Draft 2 for Regulatory Review 365 Operations Guide Release 8 Figure 143: 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 this page to automatically refresh 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 Using the AP as a Spectrum Analyzer You can temporarily transform an AP into an SM and thereby use the spectrum analyzer functionality. This is the only purpose supported for the transformation. CAUTION!

You lose connectivity to the AP during spectrum analysis, have no service to any SMs that are connected to it, and can regain connectivity (and toggle it back to AP) through only the wired Ethernet interface to the AP. For this reason, you should perform the transformation to SM in the Ethernet interface. 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. 366 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Operations Guide 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 ===========================

21.2 CONSIDERING SOFTWARE RELEASE COMPATIBILITY Within the same Canopy 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 Designations for Hardware in Radios Canopy documentation refers to hardware series (for example, Series P9). Canopy 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 56. Table 56: 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 P9 or Later in These MAC Addresses All 0A003E20672B 0A003E20672C 0A003E00F4E3 0A003E00F4E4 None All 0A003EF12AFE 0A003EF12AFF Differences in capabilities among these hardware series are summarized in Table 57. Table 57: Hardware series differences Capability Auto-sense Ethernet cable scheme Availability per Hardware Series P7 P9 yes no P8 yes Issue 2, December 2006 Draft 2 for Regulatory Review 367 Operations Guide Release 8 no no yes yes Support CMMmicro Support hardware scheduling in APs1 Support 2X operation in APs and SMs 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. yes yes no no no 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 Canopy Series P9 APs do not provide the higher throughput and lower latency, but they do support configuring the high-priority channel per SM. 21.2.2 CMMmicro Software and Hardware Compatibility 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 58. Table 58: 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 Compatible with CMMmicro none none all all 0A003E0021C8 0A003E0021C9 none all 0A003EF00F79 0A003EF00F7A 21.2.3 MIB File Set Compatibility 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. 368 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 21.3 REDEPLOYING MODULES Successfully redeploying a module may involve Operations Guide 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. remembering to use auto discovery to add the redeployed SM to the network in Prizm. 21.3.1 Wiring to Extend Network Sync 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 97. 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 ===========================

Issue 2, December 2006 Draft 2 for Regulatory Review 369 Release 8 22 SECURING YOUR NETWORK 22.1 ISOLATING APS FROM THE INTERNET Ensure that the IP addresses of the APs in your network Operations Guide 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 ENCRYPTING CANOPY RADIO TRANSMISSIONS Canopy 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 Canopy 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 DES Encryption Standard Canopy 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 AES Encryption Motorola also offers Canopy 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 Canopy AES feature activation key is one) to ensure that these products are available in only certain regions and by special permit. Issue 2, December 2006 Draft 2 for Regulatory Review 371 Operations Guide Release 8 The Canopy distributor or reseller can advise service providers about current regional availability. Canopy 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 AES-DES Operability Comparisons 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 283. Feature Availability Canopy 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. Canopy 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. Canopy DES products cannot be upgraded to AES. To have the option of AES encryption, the operator must purchase AES products. Interoperability Canopy 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. 372 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 22.3 MANAGING MODULE ACCESS BY PASSWORDS 22.3.1 Adding a User for Access to a Module Operations Guide From the factory, each Canopy 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 144, and can log in as a user. Issue 2, December 2006 Draft 2 for Regulatory Review 373 Operations Guide Release 8 Figure 144: General Status tab view for GUEST-level account An example of the Add User tab is displayed in Figure 145. 374 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Operations Guide Figure 145: 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 144). Accounts that cannot be deleted are the current user's own account. the last remaining account of ADMINISTRATOR level. 22.3.2 Overriding Forgotten IP Addresses or Passwords on AP, SM, or BH Canopy 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 453 and Reinstating Remote Access Capability on Page 453.) You want local access to a module that has had the 802.3 link disabled in the Configuration page. You can configure the module such that, when it senses the override plug, it responds by either Issue 2, December 2006 Draft 2 for Regulatory Review 375

Operations Guide Release 8 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/motorola.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 146.

=========================== 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 146: 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. 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. 376 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Operations Guide 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 Overriding Forgotten IP Addresses or Passwords on CMMmicro 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. 8. Flip the toggle switch down (away from you). 9. Click the Reboot button.

=========================== end of procedure ===========================

22.4 REQUIRING SM AUTHENTICATION 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:

Issue 2, December 2006 Draft 2 for Regulatory Review 377 Operations Guide Release 8 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 283. 22.5 FILTERING PROTOCOLS AND PORTS You can filter (block) specified protocols and ports from leaving the SM and entering the Canopy 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 Port Filtering with NAT Enabled 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. 22.5.2 Protocol and Port Filtering with NAT Disabled 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 378 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Operations Guide Up to 3 user-defined ports All other IPv4 traffic (see Figure 147) Uplink Broadcast ARP (Address Resolution Protocol) All others (see Figure 147) Figure 147: Categorical protocol filtering 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 59. Further information is provided under Protocol Filtering Tab of the SM on Page 289. Issue 2, December 2006 Draft 2 for Regulatory Review 379 PPPoEARPAll Other IPv4UserDefinedPort 1IPv4MulticastBootPServerBootPClientSNMPSMBUserDefinedPort 3UserDefinedPort 2All Others Operations Guide Release 8 Table 59: 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 ENCRYPTING DOWNLINK BROADCASTS 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 ISOLATING SMs 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. 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 78: Configuration page of CMMmicro, example on Page 224. 380 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 22.8 FILTERING MANAGEMENT THROUGH ETHERNET Operations Guide 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 ALLOWING MANAGEMENT FROM ONLY SPECIFIED IP 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 CONFIGURING MANAGEMENT IP BY DHCP The IP tab in the Configuration web page of every Canopy 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. Issue 2, December 2006 Draft 2 for Regulatory Review 381 Release 8 23 MANAGING BANDWIDTH AND AUTHENTICATION Operations Guide This section provides a high-level description of bandwidth and authentication management in a Canopy network. For more specific information, see Canopy Bandwidth and Authentication Manager (BAM) User Guide or the Motorola Canopy Prizm User Guide. 23.1 MANAGING BANDWIDTH WITHOUT BAM 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 BANDWIDTH AND AUTHENTICATION MANAGER (BAM) SERVICES AND FEATURES 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 Bandwidth Manager Capability Prizm or BAM allows you to set bandwidth per SM for sustained rates and burst rates. With this capability, the Canopy 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. 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. Issue 2, December 2006 Draft 2 for Regulatory Review 383 Operations Guide Release 8 Designing Tiered Subscriber Service Levels Examples of levels of service that vary by bandwidth capability are provided in Table 60 and Table 61. 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 60: Example times to download for arbitrary tiers of service with Canopy AP t n e m p u q E i 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 AP SM Operation Max burst speed 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 Canopy Canopy 1X 4.4 Mbps Premium Regular Basic 5250 Kbps 1750 Kbps 1000 Kbps 500 Kbps 500000 Kb 80000 Kb

<1 9 36 91 545

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

<1 9 470 1400 9220 384 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Operations Guide Table 61: Example times to download for arbitrary tiers of service with Advantage AP t n e m p u q E i 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 AP SM Operation Max burst speed 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 Advantage Canopy 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 Authentication Manager Capability 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 Canopy 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. Issue 2, December 2006 Draft 2 for Regulatory Review 385 Release 8 24 MANAGING THE NETWORK FROM A MANAGEMENT STATION (NMS) Operations Guide SNMPv2 (Simple Network Management Protocol Version 2) can be used to manage and monitor the Canopy 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 ROLES OF HARDWARE AND SOFTWARE ELEMENTS 24.1.1 Role of the Agent 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 Role of the Managed Device In SNMP, the managed device is the network element that operates on the agent software. In the Canopy 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 Role of the NMS 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 Dual Roles for the NMS 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 Simple Network Management Protocol (SNMP) Commands To manage a module, SNMPv2 supports the set command, which instructs the agent to change the data that manages the module. Issue 2, December 2006 Draft 2 for Regulatory Review 387 Operations Guide Release 8 To monitor a network element (Canopy 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 Canopy 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 Traps from the Agent 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 AP SNMP Proxy to SMs 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 MANAGEMENT INFORMATION BASE (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 Cascading Path to the MIB 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 under dod (6) above:

identified-organization (3) registration-authority (1) 388 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Operations Guide internet (1) 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 Canopy 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 Canopy Enterprise MIB begins with 1.3.6.1.4.1, and ends with the object identifier and instance(s). 24.2.2 Object Instances 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 Management Information Base Systems and Interface (MIB-II) The standard MIB-II (Management Information Base systems and interface) objects are programmed into the Canopy 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 62. Table 62: Categories of MIB-II objects Control or identify the status of system operations in the module. Objects in category system interfaces the network interfaces for which the module is configured. ip icmp tcp udp 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.) 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). Issue 2, December 2006 Draft 2 for Regulatory Review 389 Operations Guide 24.2.4 Canopy Enterprise MIB Release 8 The Canopy 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 Canopy Enterprise MIB files 1. On the NMS, immediately beneath the root directory, create directory mibviewer. 2. Immediately beneath the mibviewer directory, create directory canopymibs. 3. Download the following three standard MIB files from the Internet Engineering Task Force at http://www.simpleweb.org/ietf/mibs into the mibviewer/canopymibs 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 Canopy software package directory into the mibviewer/canopymibs directory on the NMS (if necessary, first download the software package from http://www.motorola.com/canopy):

whisp-tcv2-mib.txt (Textual Conventions MIB), which defines Canopy 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, SM, and BH) objects. WHISP-APS-MIB.txt (APs MIB), which defines objects that are specific to the AP or BH timing master. WHISP-SM-MIB.txt (SM MIB), which defines objects that are specific to the SM or BH timing slave. CMM3-MIB.txt (CMM3 MIB), which defines objects that are specific to the CMMmicro. 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 407. 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 ===========================

390 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 24.3 CONFIGURING MODULES FOR SNMP ACCESS Operations Guide Canopy 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. Canopy 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 OBJECTS DEFINED IN THE CANOPY ENTERPRISE MIB The Canopy Enterprise MIB defines separate sets of objects for all radio modules APs and BH timing masters SMs and BH timing slaves CMMmicros NOTE:

The OFDM Series BHs do not support these objects. The MIBs that they support are listed under Objects Defined in the Canopy OFDM BH Module MIB on Page 404. 24.4.1 AP, SM, and BH Objects The objects that the Canopy Enterprise MIB defines for all APs, SMs, and BHs are listed in Table 63. Table 63: Canopy Enterprise MIB objects for APs, SMs, and BHs AP, SM, BH Object Name Value Syntax Operation Allowed addVlanMember agingTimeout allowVIDAccess antennaGain1 bridgeEnable clearEventLog codePointn2 commString deleteUser Integer Integer Integer Integer Integer Integer Integer DisplayString DisplayString manage manage manage manage manage manage manage manage manage Issue 2, December 2006 Draft 2 for Regulatory Review 391 Operations Guide Release 8 AP, SM, BH Object Name Value Syntax dynamicLearning eirp3 extFilterDelay fecEnable lanDhcpState managementVID mngtIP powerControl reboot removeVlanMember scheduling sessionTimeout setDefaultPlug subnetMask taggedFrame4 transmitterOP trapIPn5 twoXRate userAccessLevel userName userPassword vlanMemberSource accessLevel boxDeviceType boxDeviceTypeID boxEncryption boxFrequency boxTemperature6 dhcpLanIP dhcpLanGateway dhcpLanSubnetMask dhcpRfPublicIP dhcpRfPublicGateway Integer Integer Integer Integer Integer Integer IpAddress Integer Integer Integer Integer Integer Integer Integer Integer Integer IpAddress Integer Integer DisplayString DisplayString Integer Integer DisplayString DisplayString DisplayString DisplayString DisplayString IpAddress IpAddress IpAddress IpAddress IpAddress dhcpRfPublicSubnetMask IpAddress Operation Allowed manage manage manage 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 392 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Operations Guide AP, SM, BH Object Name Value Syntax etherLinkStatus DisplayString Operation Allowed monitor inSyncCount lanDhcpStatus outSyncCount platformType platformVer pllOutLockCount Integer DisplayString Integer Integer Integer Integer rfPublicDhcpStatus DisplayString txCalFailure userLoginName userPswd whispBoxBoot whispBoxEsn Integer DisplayString DisplayString DisplayString WhispMACAddress whispBoxEvntLog EventString whispBoxFPGAVer DisplayString whispBridgeAge Integer whispBridgeDesLuid WhispLUID whispBridgeExt whispBridgeHash Integer Integer whispBridgeMacAddr MacAddress whispBridgeTbErr whispBridgeTbFree whispBridgeTbUsed whispVAge Integer Integer Integer Integer monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor Issue 2, December 2006 Draft 2 for Regulatory Review 393 Operations Guide Release 8 AP, SM, BH Object Name Value Syntax whispVID Integer Operation Allowed monitor DisplayString whispVType 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. monitor 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 AP and BH Timing Master Objects The objects that the Canopy Enterprise MIB defines for each AP and BH Timing Master are listed in Table 64. The traps provided in this set of objects are listed under Traps Provided in the Canopy Enterprise MIB on Page 406. Table 64: Canopy Enterprise MIB objects for APs and BH timing masters AP, BHM Object Name Value Syntax Operation Allowed allowedIPAccess1 allowedIPAccess2 allowedIPAccess3 apBeaconInfo apTwoXRate asIP1 asIP2 asIP3 authKey authMode configSource dAcksReservHigh defaultGw dfsConfig dwnLnkData dwnLnkDataRate IpAddress IpAddress IpAddress Integer Integer IpAddress IpAddress IpAddress DisplayString Integer Integer Integer IpAddress Integer Integer Integer manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage manage 394 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Operations Guide AP, BHM Object Name 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 txSpreading uAcksReservHigh untranslatedArp Value Syntax 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 Integer Integer Integer updateAppAddress IpAddress 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 Issue 2, December 2006 Draft 2 for Regulatory Review 395 Operations Guide Release 8 AP, BHM Object Name Value Syntax Operation Allowed manage manage manage monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor Integer Integer Integer Gauge32 Integer Gauge32 DisplayString DisplayString Integer Integer Integer DisplayString Integer Integer Integer Integer Gauge32 Gauge32 DisplayString upLnkDataRate upLnkLimit vlanEnable actDwnFragCount actDwnLinkIndex actUpFragCount adaptRate avgPowerLevel dataSlotDwn dataSlotUp dataSlotUpHi Status downLinkEff downLinkRate dwnLnkAckSlot dwnLnkAckSlotHi expDwnFragCount expUpFragCount fpgaVersion gpsStatus DisplayString monitor lastPowerLevel DisplayString linkAirDelay linkAveJitter linkDescr linkESN linkInDiscards linkInError linkInNUcastPkts linkInOctets linkInUcastPkts linkInUnknownProtos linkLastJitter linkLastRSSI linkLUID Integer Integer DisplayString PhysAddress Counter32 Counter32 Counter32 Counter32 Counter32 Counter32 Integer Integer Integer monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor monitor 396 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Operations Guide AP, BHM Object Name Value Syntax 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 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 softwareBootVersion softwareVersion DisplayString DisplayString testDuration testLUID upLinkEff upLinkRate Integer Integer Integer Integer 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 Issue 2, December 2006 Draft 2 for Regulatory Review 397 Operations Guide Release 8 AP, BHM Object Name Value Syntax upLnkAckSlot upLnkAckSlotHi Integer Integer Operation Allowed monitor monitor whispGPSStats NOTES:

1. You can set to 1 to initiate a link test, but not 0 to stop. monitor Integer The value 0 is only an indication of the idle link test state. 24.4.3 SM and BH Timing Slave Objects The objects that the Canopy Enterprise MIB defines for each SM and BH Timing Slave are listed in Table 65. Table 65: Canopy Enterprise MIB objects for SMs and BH timing slaves SM, BHS Object Name Value Syntax allOtherIPFilter allOthersFilter allowedIPAccess1 allowedIPAccess2 allowedIPAccess3 alternateDNSIP arpCacheTimeout arpFilter authKey authKeyOption bootpcFilter bootpsFilter defaultGw dhcpClientEnable dhcpIPStart dhcpNumIPsToLease dhcpServerEnable dhcpServerLeaseTime dmzEnable dmzIP dnsAutomatic enable8023link Integer Integer IpAddress IpAddress IpAddress IpAddress Integer Integer DisplayString Integer Integer Integer IpAddress Integer IpAddress Integer Integer Integer Integer IpAddress 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 398 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Operations Guide SM, BHS Object Name ethAccessFilterEnable hiPriorityChannel hiPriorityDownlinkCIR hiPriorityUplinkCIR ingressVID ip4MultFilter ipAccessFilterEnable lanIp lanMask localIP lowPriorityDownlinkCIR lowPriorityUplinkCIR naptEnable naptPrivateIP naptPrivateSubnetMask naptPublicGatewayIP naptPublicIP naptPublicSubnetMask naptRFPublicGateway naptRFPublicIP Value Syntax Integer Integer Integer Integer Integer Integer Integer IpAddress IpAddress IpAddress Integer Integer Integer IpAddress IpAddress IpAddress IpAddress IpAddress IpAddress IpAddress naptRFPublicSubnetMask IpAddress networkAccess port port1TCPFilter port2TCPFilter port3TCPFilter port1UDPFilter port2UDPFilter port3UDPFilter powerUpMode pppoeFilter prefferedDNSIP protocol radioDbmInt Integer Integer Integer Integer Integer Integer Integer Integer Integer Integer IpAddress 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 Issue 2, December 2006 Draft 2 for Regulatory Review 399 Operations Guide Release 8 SM, BHS Object Name 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 hostMacAddress jitter radioDbm radioSlicing Value Syntax 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 Operation Allowed 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 DhcpServerEntry monitor IpAddress IpAddress TimeTicks PhysAddress Integer DisplayString Integer monitor monitor monitor monitor monitor monitor monitor 400 Draft 2 for Regulatory Review Issue 2, December 2006

Release 8 Board Type FPGA Version Installation and Configuration Guide 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 ===========================

16.3.8 General Status Tab of the AP An example of an AP General Status tab is displayed in Figure 67. Figure 67: 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. Issue 2, December 2006 Draft 2 for Regulatory Review 201 Installation and Configuration Guide Release 8 Device Type This field indicates the type of the Canopy module. Values include the frequency band of the AP, its module type, and its MAC address. Software Version This field indicates the Canopy system release, the time and date of the release, and whether communications involving the module are secured by DES or AES encryption

(see Encrypting Canopy Radio Transmissions on Page 371). If you request technical support, provide the information from this field. Software BOOT Version This field indicates the version of the CANOPYBOOT 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 367. 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. 202 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide NOTE:

When this message is displayed, the AP transmitter is turned off to avoid self-interference within the Canopy 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. 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 Concluding the Test of Point-to-Multipoint Links 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 ======================

Issue 2, December 2006 Draft 2 for Regulatory Review 203 Installation and Configuration Guide 16.4 CONFIGURING A POINT-TO-POINT LINK FOR TEST Release 8 NOTE:

This section supports the Canopy 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. 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 under Preventing Overexposure to RF 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 Canopy 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 Canopy 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. 204 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 16.4.1 Quick Start Page of the BHM Installation and Configuration Guide 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 68. Figure 68: 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. Issue 2, December 2006 Draft 2 for Regulatory Review 205 Installation and Configuration Guide Proceed with the test setup as follows. Release 8 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 ===========================

Canopy 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 Time Tab of the BHM 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 69. 206 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide Figure 69: 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. Issue 2, December 2006 Draft 2 for Regulatory Review 207 Installation and Configuration Guide If you enter a time and date, the format for entry is Release 8 hh MM

/ mm / ss

dd

yyyy Time :

Date :

where 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. 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. 3. 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 under Preventing Overexposure to RF 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 70.

=========================== end of procedure ======================

208 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide Figure 70: Remote Subscribers tab of BHM, example Issue 2, December 2006 Draft 2 for Regulatory Review 209 Installation and Configuration Guide 16.4.3 Beginning the Test of Point-to-Point Links Release 8 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 71. Figure 71: 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 Canopy module. Values include the frequency band of the BHS, its module type, and its MAC address. Software Version This field indicates the Canopy 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 Canopy Radio Transmissions on Page 371). If you request technical support, provide the information from this field. 210 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide Software BOOT Version This field indicates the version of the CANOPYBOOT 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 367. 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 45 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. Issue 2, December 2006 Draft 2 for Regulatory Review 211 Release 8 When the receiving link is operating at 2X, the Jitter scale is 0 to 15 with desired Installation and Configuration Guide 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 Continuing the Test of Point-to-Point Links 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 212 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 General Status Tab of the BHM An example of a BHM General Status tab is displayed in Figure 72. Figure 72: 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 Canopy 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 Issue 2, December 2006 Draft 2 for Regulatory Review 213 Installation and Configuration Guide Release 8 is secured by DES or AES encryption (see Encrypting Canopy Radio Transmissions on Page 371). When you request technical support, provide the information from this field. Software BOOT Version This field indicates the version of the CANOPYBOOT 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 367. 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 Canopy system. 214 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 Concluding the Test of Point-to-Point Links 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 ===========================

Issue 2, December 2006 Draft 2 for Regulatory Review 215 Installation and Configuration Guide 16.4.7 Setting up a CMMmicro The layout of the CMMmicro is as shown in Figure 73. Release 8 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 73: CMMmicro layout 216 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Perform the following procedure to set up the CMMmicro. Installation and Configuration Guide 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 74 on Page 218. CAUTION!

Never connect any devices other than Canopy 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 75 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 76 on Page 220. 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 ===========================

Issue 2, December 2006 Draft 2 for Regulatory Review 217 Installation and Configuration Guide Release 8 Figure 74: CMMmicro door label 218 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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. Issue 2, December 2006 Draft 2 for Regulatory Review 219 Installation and Configuration Guide Figure 75: CMMmicro circuit board Release 8 Figure 76: CMMmicro connections 220 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 16.4.8 Status Page of the CMMmicro Installation and Configuration Guide An example of a CMMmicro Status page is displayed in Figure 77. Figure 77: 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.) Issue 2, December 2006 Draft 2 for Regulatory Review 221 Installation and Configuration Guide Release 8 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 Canopy 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 75 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. 222 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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. Issue 2, December 2006 Draft 2 for Regulatory Review 223 Installation and Configuration Guide 16.4.9 Configuration Page of the CMMmicro An example of the CMMmicro Configuration page is displayed in Figure 78. Release 8 Figure 78: Configuration page of CMMmicro, example 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 224 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 the Device Type from the Status web page. Installation and Configuration Guide 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. 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. Issue 2, December 2006 Draft 2 for Regulatory Review 225 Installation and Configuration Guide Release 8 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 377. 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 46. Table 46: Port Configuration selections for CMMmicro Selection Auto Result The port attempts to auto-negotiate speed and duplex state.

(This is the default and recommended setting.) 100FDX The port is forced to 100 Mbps and full duplex. 100HDX The port is forced to 100 Mbps and half duplex. 10FDX 10HDX 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. 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 Canopy APs or BHs. 226 Draft 2 for Regulatory Review Issue 2, December 2006 Installation and Configuration Guide CAUTION!

Never connect any devices other than Canopy 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 75 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. Release 8 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 377. 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 377. 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. Issue 2, December 2006 Draft 2 for Regulatory Review 227 Installation and Configuration Guide Release 8 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 Canopy. 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. RECOMMENDATION:

For more information on CIDR, execute an Internet search on Classless Interdomain Routing. The default treatment is to allow all networks access. 228 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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. VLAN Port Configuration Each column in the VLAN Port Configuration section of Figure 78 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 Issue 2, December 2006 Draft 2 for Regulatory Review 229 Installation and Configuration Guide Release 8 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 78) 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 47. Table 47: When changes become effective in CMMmicro For these parameters clicking this button has this effect. Port Configuration Description Power Port Control Webpage Auto Update Save Changes Any change becomes effective immediately and any previous setting is lost. Undo Saved Changes No change is undone, and no previous setting is restored. Set to Defaults The default setting is not restored. Reboot Save Changes Any other parameter Undo Saved Changes 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. Set to Defaults The default setting is restored. Reboot Any change recorded in flash memory (and not later undone) becomes effective. 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. 230 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 16.4.10 Configuring Modules for Connection to CMMmicro Installation and Configuration Guide 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 237. Sync Input on Page 296. 16.4.11 Event Log Page of the CMMmicro This page may contain information that can be useful under the guidance of Canopy technical support. For this reason, the operator should not clear the contents of this page before contacting technical support. 16.4.12 GPS Status Page of the CMMmicro An example of the CMMmicro GPS Status page is displayed in Figure 79. Figure 79: GPS Status page of CMMmicro, example 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. Issue 2, December 2006 Draft 2 for Regulatory Review 231 Release 8 Installation and Configuration Guide signal. No Antenna indicates the GPS interface board is not detecting any incoming The other GPS Status fields are described under Satellites Visible on Page 222. GPS Receiver Information This field displays information about the GPS interface board. 16.4.13 Port MIB Page of the CMMmicro An example of the Port MIB (Ethernet statistics) web page is displayed in Figure 80. Figure 80: 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. 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. 232 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 17 PREPARING COMPONENTS FOR DEPLOYMENT Installation and Configuration Guide 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 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 CORRELATING COMPONENT-SPECIFIC INFORMATION 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 ENSURING CONTINUING ACCESS TO THE MODULES As you proceed through the steps under Configuring for the Destination on Page 235, 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 Issue 2, December 2006 Draft 2 for Regulatory Review 233 Release 8 18 CONFIGURING FOR THE DESTINATION 18.1 CONFIGURING AN AP FOR THE DESTINATION Installation and Configuration Guide 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 373. 18.1.1 General Tab of the AP An example of an AP General tab is displayed in Figure 81. Issue 2, December 2006 Draft 2 for Regulatory Review 235 Installation and Configuration Guide Release 8 Figure 81: 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 81, you may set the Configuration page parameters as follows. 236 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 366. 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 292. 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. Issue 2, December 2006 Draft 2 for Regulatory Review 237 Installation and Configuration Guide Release 8 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 83. 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 83 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 91. 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. 238 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 IP Tab of the AP An example of the IP tab of the AP is displayed in Figure 82. Figure 82: IP tab of AP, example Issue 2, December 2006 Draft 2 for Regulatory Review 239 Installation and Configuration Guide You may set the IP tab parameters as follows. Release 8 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 377. 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 240 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 Radio Tab of the AP An example of the Radio tab of the AP is shown in Figure 83. Figure 83: Radio tab of AP (900 MHz), example Issue 2, December 2006 Draft 2 for Regulatory Review 241 Installation and Configuration Guide Release 8 The Radio tab of the AP contains some of the configurable parameters that define how the AP operates. As shown in Figure 83, 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 Canopy 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 Canopy 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 27 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 242 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 440. 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 48. Table 48: Control slot settings for all APs in cluster Number of SMs that Register to the AP Number of Control Slots Recommended 1 to 10 11 to 50 51 to 150 151 to 200 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 132. Issue 2, December 2006 Draft 2 for Regulatory Review 243 Installation and Configuration Guide Release 8 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 Canopy 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. 244 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 326. 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. Issue 2, December 2006 Draft 2 for Regulatory Review 245 Installation and Configuration Guide 18.1.4 SNMP Tab of the AP An example of the SNMP tab of the AP is displayed in Figure 84. Release 8 Figure 84: SNMP tab of AP, example 246 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 Installation and Configuration Guide 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 Canopy. 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 Canopy Enterprise MIB on Page 406. 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). Issue 2, December 2006 Draft 2 for Regulatory Review 247 Installation and Configuration Guide Release 8 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. 248 Draft 2 for Regulatory Review Issue 2, December 2006 Release 8 18.1.5 Quality of Service (QoS) Tab of the AP Installation and Configuration Guide An example of the Quality of Service (QoS) tab of the AP is displayed in Figure 85. Figure 85: 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 85 Setting the Configuration Source on Page 292. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 88 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 85 Setting the Configuration Source on Page 292. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 88 Issue 2, December 2006 Draft 2 for Regulatory Review 249 Installation and Configuration Guide Release 8 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 85 Setting the Configuration Source on Page 292. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 88 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 85 Setting the Configuration Source on Page 292. Interaction of Burst Allocation and Sustained Data Rate Settings on Page 88 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. 250 Draft 2 for Regulatory Review Issue 2, December 2006