Professional Documents
Culture Documents
CanopyAP PDF
CanopyAP PDF
User Manual
AP-UM-en
Issue 5
January 2004
AP User Manual January 2004
Software Release 4.1
NOTICES
U.S. Federal Communication Commision (FCC) and Industry Canada (IC) Notification
This device complies with part 15 of the U. S. FCC Rules and Regulations and with RSS-210 of Industry Canada. Operation is subject
to the following two conditions: (1) This device may not cause harmful interference, and (2) This device must accept any interference
received, including interference that may cause undesired operation. In Canada, users should be cautioned to take note that high power
radars are allocated as primary users (meaning they have priority) of 5250 – 5350 MHz and 5650 – 5850 MHz and these radars could
cause interference and/or damage to license-exempt local area networks (LELAN).
This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the U.S. FCC
Rules and with RSS-210 of Industry Canada. These limits are designed to provide reasonable protection against harmful interference in
a residential installation. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in
accordance with these instructions, may cause harmful interference to radio communications. If this equipment does cause harmful
interference to radio or television reception, which can be determined by turning the equipment on and off, the user is encouraged to
correct the interference by one or more of the following measures:
Increase the separation between the affected equipment and the unit;
Connect the affected equipment to a power outlet on a different circuit from that which the receiver is connected to;
Consult the dealer and/or experienced radio/TV technician for help.
FCC IDs and Industry Canada Certification Numbers are listed in the following table:
Maximum
Module Transmitter Industry Canada
Types Frequency Band Range Power Reflector FCC ID Cert Number
SM AP BH ISM 2400-2483.5 MHz 340 mW Allowed on SM and ABZ89FC5808 109W-2400
BH
SM AP BH U-NII 5250-5350 MHz 200 mW Not Allowed ABZ89FC3789 109W-5200
SM BH U-NII 5250-5350 MHz 3.2 mW Recommended ABZ89FC5807 109W-5210
SM AP BH U-NII 5725-5825 MHz 200 mW Allowed on SM and ABZ89FC4816 109W-5700
BH
SM AP BH ISM 5725-5850 MHz 200 mW Allowed on SM and ABZ89FC5804 109W-5700
BH
The term “IC:” before the radio certification number only signifies that Industry Canada technical specifications were met.
Declaration of conformity:
Motorola declares the GHz radio types listed below comply with the essential requirements and other relevant provisions of
Directive1999/5/EC.
Relevant Specification
EN 301 893 or similar - radio spectrum
EN301489-17 - EMC
EN60950 – safety
Product Details for Products Tested for Compliance with Relevant EC Directives
Module Type Frequency Maximum Effective Isotropic Modulation Type Operating Channels Non-
Band Range Transmitter Radiated Power overlapping
(EIRP) Channel
Power Spacing
Access Point 5.725 to 5.825 200 mW RMS 1 Watt EIRP High Index 2-level 5745 to 5805 MHz in 20 MHz
GHz FSK 5-MHz increments
Subscriber 5.725 to 5.825 200 mW RMS 1 Watt EIRP High Index 2-level 5745 to 5805 MHz in 20 MHz
Module GHz FSK 5-MHz increments
Subscriber 5.725 to 5.825 200 mW RMS 63 Watts EIRP High Index 2-level 5745 to 5805 MHz in 20 MHz
Module with GHz FSK 5-MHz increments
Reflector
Backhaul 5.725 to 5.825 200 mW RMS 1 Watt EIRP High Index 2-level 5745 to 5805 MHz in 20 MHz
GHz or 4-level FSK 5-MHz increments
Backhaul with 5.725 to 5.825 200 mW RMS 63 Watts EIRP High Index 2-level 5745 to 5805 MHz in 20 MHz
Reflector GHz or 4-level FSK 5-MHz increments
Canopy can be configured to operate at a range of frequencies, but at this time, only channels from 5745 MHz through 5805 MHz of the
5.7 GHz product have been tested for compliance with relevant EC directives. Before configuring equipment to operate outside this
range, please check with your regulator.
Exposure Note
A Canopy module must be installed to provide a separation distance of at least 20 cm (7.9 in) from all persons. When adding the Canopy
reflector dish, the reflector dish must be installed to provide a separation distance of at least 1.5m (59.1 in) from all persons. When so
installed, the module’s RF field is within Health Canada limits for the general population; consult Safety Code 6, obtainable from Health
Canada’s website http://www.hc-sc.gc.ca/rpb.
In both configurations the maximum RMS power does not exceed 340mW.
The applicable power density exposure limit is 10 Watt/m2, according to the FCC OET Bulletin 65, the ICNIRP guidelines, and the
Health Canada Safety Code 6. The corresponding compliance distances referenced above have been determined by assuming worst-case
scenarios. The peak power density (S) in the far-field of a radio-frequency source with rms transmit power P and antenna gain G at a
distance d is
P⋅G
S=
4π d 2
In the case of the Canopy SM without reflector, the gain is 8 dBi (a factor of 6.3), so the peak power density equals the exposure limit at
a distance of 13 cm for 2.4 GHz product and 10 cm for 5.2 and 5.7 GHz product. A power compliance margin of over 2 is artificially
introduced by setting the distance to a consistent 20 cm across all modules, giving a power compliance margin of x2.4 for 2.4 GHz
modules and x4 for 5.2 and 5.7 GHz modules.
In the case of the Canopy SM with reflector, the gain depends on frequency and ranges from 19 dBi (a factor of 80) for 2.4 GHz modules
to 26 dBi (a factor of 400) for 5.2 GHz Extended Range and 5.7 GHz modules, so the peak power density equals the exposure limit at a
distance of 10 to 80 cm. A power compliance margin is artificially introduced by defining a consistent compliance distance of 1.5 m
across all modules with reflectors, giving a power compliance margin of x10 for 2.4 GHz modules, x220 for 5.2 GHz Extended Range
modules, and x3.5 for 5.7 GHz modules. The compliance distance is greatly overestimated in this case because the far-field equation
neglects the physical dimension of the antenna, which is modeled as a point-source.
Now, therefore, in consideration of the promises and mutual obligations contained herein, and for other good and valuable consideration,
the receipt and sufficiency of which are hereby mutually acknowledged, you and Motorola agree as follows:
Grant of License. Subject to the following terms and conditions, Motorola, Inc., grants to you a personal, revocable, non-assignable,
non-transferable, non-exclusive and limited license to use on a single piece of equipment only one copy of the software contained on this
disk (which may have been pre-loaded on the equipment)(Software). You may make two copies of the Software, but only for backup,
archival, or disaster recovery purposes. On any copy you make of the Software, you must reproduce and include the copyright and other
proprietary rights notice contained on the copy we have furnished you of the Software.
Ownership. Motorola (or its supplier) retains all title, ownership and intellectual property rights to the Software and any copies,
including translations, compilations, derivative works (including images) partial copies and portions of updated works. The Software is
Motorola’s (or its supplier's) confidential proprietary information. This Software License Agreement does not convey to you any interest
in or to the Software, but only a limited right of use. You agree not to disclose it or make it available to anyone without Motorola’s
written authorization. You will exercise no less than reasonable care to protect the Software from unauthorized disclosure. You agree not
to disassemble, decompile or reverse engineer, or create derivative works of the Software, except and only to the extent that such activity
is expressly permitted by applicable law.
Termination. This License is effective until terminated. This License will terminate immediately without notice from Motorola or
judicial resolution if you fail to comply with any provision of this License. Upon such termination you must destroy the Software, all
accompanying written materials and all copies thereof, and the sections entitled Limited Warranty, Limitation of Remedies and
Damages, and General will survive any termination.
Limited Warranty. Motorola warrants for a period of ninety (90) days from Motorola’s or its customer’s shipment of the Software to
you that (i) the disk(s) on which the Software is recorded will be free from defects in materials and workmanship under normal use and
(ii) the Software, under normal use, will perform substantially in accordance with Motorola’s published specifications for that release
level of the Software. The written materials are provided "AS IS" and without warranty of any kind. Motorola's entire liability and your
sole and exclusive remedy for any breach of the foregoing limited warranty will be, at Motorola's option, replacement of the disk(s),
provision of downloadable patch or replacement code, or refund of the unused portion of your bargained for contractual benefit up to the
amount paid for this Software License.
THIS LIMITED WARRANTY IS THE ONLY WARRANTY PROVIDED BY MOTOROLA, AND MOTOROLA AND ITS
LICENSORS EXPRESSLY DISCLAIM ALL OTHER WARRANTIES, EITHER EXPRESS OF IMPLIED, INCLUDING BUT NOT
LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT. MOTOROLA DOES NOT WARRANT THAT THE OPERATION OF THE SOFTWARE WILL BE
UNINTERRUPTED OR ERROR-FREE, OR THAT DEFECTS IN THE SOFTWARE WILL BE CORRECTED. NO ORAL OR
WRITTEN REPRESENTATIONS MADE BY MOTOROLA OR AN AGENT THEREOF SHALL CREATE A WARRANTY OR IN
ANY WAY INCREASE THE SCOPE OF THIS WARRANTY. MOTOROLA DOES NOT WARRANT ANY SOFTWARE THAT
HAS BEEN OPERATED IN EXCESS OF SPECIFICATIONS, DAMAGED, MISUSED, NEGLECTED, OR IMPROPERLY
INSTALLED. BECAUSE SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF IMPLIED
WARRANTIES, THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU.
Limitation of Remedies and Damages. Regardless of whether any remedy set forth herein fails of its essential purpose, IN NO EVENT
SHALL MOTOROLA OR ANY OF THE LICENSORS, DIRECTORS, OFFICERS, EMPLOYEES OR AFFILIATES OF THE
FOREGOING BE LIABLE TO YOU FOR ANY CONSEQUENTIAL, INCIDENTAL, INDIRECT, SPECIAL OR SIMILAR
DAMAGES WHATSOEVER (including, without limitation, damages for loss of business profits, business interruption, loss of business
information and the like), whether foreseeable or unforeseeable, arising out of the use or inability to use the Software or accompanying
written materials, regardless of the basis of the claim and even if Motorola or a Motorola representative has been advised of the
possibility of such damage. Motorola's liability to you for direct damages for any cause whatsoever, regardless of the basis of the form
of the action, will be limited to the price paid for the Software that caused the damages. THIS LIMITATION WILL NOT APPLY IN
CASE OF PERSONAL INJURY ONLY WHERE AND TO THE EXTENT THAT APPLICABLE LAW REQUIRES SUCH
LIABILITY. BECAUSE SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR
CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO YOU.
Maintenance and Support. Motorola shall not be responsible for maintenance or support of the software. By accepting the license
granted under this agreement, you agree that Motorola will be under no obligation to provide any support, maintenance or service in
connection with the Software or any application developed by you. Any maintenance and support of the Related Product will be
provided under the terms of the agreement for the Related Product.
Transfer. In the case of software designed to operate on Motorola equipment, you may not transfer the Software to another party except:
(1) if you are an end-user, when you are transferring the Software together with the Motorola equipment on which it operates; or 2) if
you are a Motorola licensed distributor, when you are transferring the Software either together with such Motorola equipment or are
transferring the Software as a licensed duly paid for upgrade, update, patch, new release, enhancement or replacement of a prior version
of the Software. If you are a Motorola licensed distributor, when you are transferring the Software as permitted herein, you agree to
transfer the Software with a license agreement having terms and conditions no less restrictive than those contained herein. You may
transfer all other Software, not otherwise having an agreed restriction on transfer, to another party. However, all such transfers of
Software are strictly subject to the conditions precedent that the other party agrees to accept the terms and conditions of this License, and
you destroy any copy of the Software you do not transfer to that party. You may not sublicense or otherwise transfer, rent or lease the
Software without our written consent. You may not transfer the Software in violation of any laws, regulations, export controls or
economic sanctions imposed by the U.S. Government.
Right to Audit. Motorola shall have the right to audit annually, upon reasonable advance notice and during normal business hours, your
records and accounts to determine compliance with the terms of this Agreement.
Export Controls. You specifically acknowledge that the software may be subject to United States and other country export control laws.
You shall comply strictly with all requirements of all applicable export control laws and regulations with respect to all such software and
materials.
U.S. Government Users. If you are a U.S. Government user, then the Software is provided with "RESTRICTED RIGHTS" as set forth
in subparagraphs (c)(1) and (2) of the Commercial Computer Software-Restricted Rights clause at FAR 52 227-19 or subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, as applicable.
Disputes. You and Motorola hereby agree that any dispute, controversy or claim, except for any dispute, controversy or claim involving
intellectual property, prior to initiation of any formal legal process, will be submitted for non-binding mediation, prior to initiation of
any formal legal process. Cost of mediation will be shared equally. Nothing in this Section will prevent either party from resorting to
judicial proceedings, if (i) good faith efforts to resolve the dispute under these procedures have been unsuccessful, (ii) the dispute, claim
or controversy involves intellectual property, or (iii) interim relief from a court is necessary to prevent serious and irreparable injury to
that party or to others.
General. Illinois law governs this license. The terms of this license are supplemental to any written agreement executed by both parties
regarding this subject and the Software Motorola is to license you under it, and supersedes all previous oral or written communications
between us regarding the subject except for such executed agreement. It may not be modified or waived except in writing and signed by
an officer or other authorized representative of each party. If any provision is held invalid, all other provisions shall remain valid, unless
such invalidity would frustrate the purpose of our agreement. The failure of either party to enforce any rights granted hereunder or to
take action against the other party in the event of any breach hereunder shall not be deemed a waiver by that party as to subsequent
enforcement of rights or subsequent action in the event of future breaches.
IN NO EVENT SHALL MOTOROLA BE LIABLE TO YOU OR ANY OTHER PARTY FOR ANY DIRECT, INDIRECT,
GENERAL, SPECIAL, INCIDENTAL, CONSEQUENTIAL, EXEMPLARY OR OTHER DAMAGE ARISING OUT OF THE USE
OR INABILITY TO USE THE PRODUCT (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS
PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION OR ANY OTHER PECUNIARY LOSS, OR FROM
ANY BREACH OF WARRANTY, EVEN IF MOTOROLA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
(Some states do not allow the exclusion or limitation of incidental or consequential damages, so the above exclusion or limitation may
not apply to you.) IN NO CASE SHALL MOTOROLA’S LIABILITY EXCEED THE AMOUNT YOU PAID FOR THE PRODUCT.
Motorola, Inc
Broadband Wireless Technology Center
50 East Commerce Drive
Schaumburg, IL 60173
USA
http://www.motorola.com/canopy
TABLE OF CONTENTS
1 WELCOME ................................................................................................................................11
1.1 Feedback.........................................................................................................................11
1.2 Technical Support ...........................................................................................................11
2 ABOUT THIS DOCUMENT.......................................................................................................12
2.1 Intended Use ...................................................................................................................12
2.2 New in This Issue............................................................................................................12
2.3 Additional Feature Information ........................................................................................13
3 SYSTEM OVERVIEW ...............................................................................................................14
3.1 Module-to-Module Communications ...............................................................................14
3.2 Types of AP Applications ................................................................................................14
3.3 Synchronization...............................................................................................................16
3.3.1 Unsynchronized Modules ..................................................................................16
3.3.2 Passing Sync .....................................................................................................16
3.4 Wiring ..............................................................................................................................18
4 ADVANCED FEATURES..........................................................................................................19
4.1 Security Features ............................................................................................................19
4.1.1 BRAID................................................................................................................19
4.1.2 DES Encryption .................................................................................................19
4.1.3 AES Encryption..................................................................................................19
4.1.4 AES-DES Operability Comparisons ..................................................................19
4.2 Bandwidth Management .................................................................................................20
4.2.1 Bandwidth and Authentication Manager (BAM) ................................................20
4.2.2 Recharging Buckets ..........................................................................................21
4.2.3 Subscriber Module Perspective.........................................................................21
4.2.4 Interaction of Burst Data and Sustained Data Settings.....................................21
4.3 High-Priority Bandwidth...................................................................................................22
4.3.1 High Priority Uplink Percentage.........................................................................23
4.3.2 UAcks Reserved High .......................................................................................23
4.3.3 DAcks Reserved High .......................................................................................23
4.3.4 NumCtlSlots Reserved High..............................................................................23
4.3.5 Allocations to Downlink and Uplink....................................................................23
4.4 Branding ..........................................................................................................................24
4.5 Denying All Remote Access............................................................................................26
4.6 Reinstating Remote Access Capability ...........................................................................26
4.7 SNMP ..............................................................................................................................26
4.7.1 Agent .................................................................................................................27
4.7.2 Managed Device................................................................................................27
4.7.3 NMS...................................................................................................................27
4.7.4 Dual Roles .........................................................................................................27
4.7.5 SNMP Commands .............................................................................................27
4.7.6 Traps..................................................................................................................27
4.7.7 MIBS ..................................................................................................................28
4.7.8 MIB-II .................................................................................................................29
4.7.9 Canopy Enterprise MIB .....................................................................................29
LIST OF FIGURES
Figure 1: Additional link to extend network sync, Design 3 ..............................................................17
Figure 2: Additional link to extend network sync, Design 4 ..............................................................17
Figure 3: Additional link to extend network sync, Design 5 ..............................................................18
Figure 4: Canopy system wiring .......................................................................................................18
Figure 5: Burst Allocation vs. Sustained Rate, Example 1 ...............................................................21
Figure 6: Burst Allocation vs. Sustained Rate, Example 2 ...............................................................22
Figure 7: Burst Allocation vs. Sustained Rate, Example 3 ...............................................................22
Figure 8: Burst Allocation vs. Sustained Rate, Example 4 ...............................................................22
Figure 9: High-priority channel layout ...............................................................................................23
Figure 10: Example FTP session......................................................................................................24
Figure 11: Example telnet session to change screen logo ...............................................................25
Figure 12: Canopy System Calculator page for beam width ............................................................41
Figure 13: Canopy System Calculator page for antenna elevation ..................................................42
Figure 14: Canopy System Calculator page for antenna downward tilt ...........................................43
Figure 15: Fresnel zone ....................................................................................................................44
Figure 16: Canopy System Calculator page for Fresnel zone dimensions ......................................45
Figure 17: Determinants in Rx signal level .......................................................................................46
Figure 18: Canopy System Calculator page for path loss ................................................................47
Figure 19: FTP to AP for SM auto-update ........................................................................................49
Figure 20: Telnet to AP for SM auto-update .....................................................................................49
Figure 21: Telnet to AP to turn off SM auto-update..........................................................................50
Figure 22: Example layout of 7 Access Point clusters......................................................................57
Figure 23: Example of IP address in Class B subnet .......................................................................58
Figure 24: Canopy AP base cover, attached and detached .............................................................61
Figure 25: Location of 115-/230-volt switch ......................................................................................72
Figure 26: Quick Start screen ...........................................................................................................74
Figure 27: Status screen...................................................................................................................76
Figure 28: Configuration screen .......................................................................................................78
Figure 29: Configuration screen, continued......................................................................................83
Figure 30: IP Configuration screen ...................................................................................................86
Figure 31: Event Log screen.............................................................................................................88
Figure 32: LUID Select screen..........................................................................................................89
Figure 33: Link Test screen ..............................................................................................................90
Figure 34: Time & Data screen.........................................................................................................91
Figure 35: Example Sessions page data ..........................................................................................92
Figure 36: GPS Status screen ..........................................................................................................94
Figure 37: Reg Failed SMs screen ...................................................................................................97
Figure 38: Bridge Table screen ........................................................................................................98
LIST OF TABLES
LIST OF PROCEDURES
1 WELCOME
Thank you for purchasing Motorola Canopy™ Access Point Modules.1 This technology is the latest
innovation in high speed wireless networking. Canopy system features include
• network speeds of 10/100 BaseT
• small compact design
• no special requirements for PC setup.
1.1 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. Please send your comments to technical-documentation@canopywireless.com.
1
Canopy is a trademark of Motorola, Inc.
2
Reader is a registered trademark of Adobe Systems, Incorporated.
− free space path loss (see Free Space Path Loss on Page 45).
• A procedure to use the AP to update the software release of all registered SMs that
are entered onto an action list. See AP Update of SM Software Release on Page 48.
• A procedure to reduce the power of module transmission to mitigate or avoid
interference. See Power Reduction to Mitigate Interference on Page 51.
• Expansion and clarification of available channel frequencies.
See 5.2-GHz AP Channels on Page 53 and 5.7-GHz AP Channels on Page 54.
• Corrections for the roles of Pins 4 and 5 (to +V return) and Pins 7 and 8 (to +V) and
inclusion of a Protective Earth label for ground. See Connector Wiring on Page 63.
• Clarifications about the use of an override plug to regain control of a module.
See Overriding IP Address and Password Setting on Page 66.
• A procedure that allows sync to be passed to an AP by a collocated SM or a BH timing
slave that receives sync over the air from another AP. See Wiring to Extend Network
Sync on Page 67.
• A new field in the Status page to specify the active encryption technology with reboot
and software version information. See Software Version on Page 76.
• New fields in the Configuration page to
− specify how synchronization is sent to or from the AP. See Sync Input on Page 79.
− clarify the interactions of password settings. See Display-Only Access on Page 82.
− specify the type of air link security to be used on this AP. See Airlink Security on
Page 83.
− allow the operator to suppress the display of AP data on the AP Eval Data page of
all SMs that register. See SM Scan Privacy on Page 83.
− indicate whether SMs can authenticate on the AP (whether the BAM server is
used). See Authentication Mode on Page 84.
− enable SNMP traps. See Trap Enable on Page 85.
− allow multiple APs to send beacons to multiple SMs in the same range without
interference. See Transmit Frame Spreading on Page 85.
• A new web page for TCP/IP addressing. See IP Configuration Page on Page 86.
• A new field that displays antenna status. See GPS Status Page on Page 94.
• A new web page that provides information about any SM that attempted to register
with the AP but failed since the last power cycle or reboot. See Expanded Stats Page
on Page 96.
• Clarifications in the module specifications table. See AP MODULE SPECIFICATIONS
on Page 100.
See also HISTORY OF CHANGES IN THIS DOCUMENT on Page 102.
3 SYSTEM OVERVIEW
The Canopy network uses the Canopy components that are defined in Table 1.
Component Definition
Access Point Module (AP) One module that distributes network or Internet services in a 60°
sector to 200 subscribers or fewer.
Access Point cluster Two to six APs that together distribute network or Internet services to
(AP cluster) a community of 1,200 or fewer subscribers. Each AP covers a 60°
sector. This cluster covers as much as 360°.
Subscriber Module (SM) A customer premises equipment (CPE) device that extends network
or Internet services by communication with an AP or an AP cluster.
Cluster Management A module that provides power, GPS timing, and networking
Module (CMM) connections for an AP cluster. If this CMM is connected to a
Backhaul Module (BH), then this CMM is the central point of
connectivity for the entire site.
The AP uses a point-to-multipoint protocol to communicate with each registered SM. The BH timing
master uses a point-to-point protocol to communicate with a BH timing slave.
For more information about the BH, see Canopy Backhaul Module (BH) User Manual. For more
information about the SM, see Canopy Subscriber Module (SM) User Manual.
A 2.4-GHz or 5.7-GHz SM can be used with a Canopy Passive Reflector dish. This reflector
extends the maximum span of a link as defined in Table 2.
2400SM (DES)
with
2400AP (DES)
none 5 miles (8 km)
2401SM (AES)
with
2401AP (AES)
2400SMRF (DES)
with on SM 15 miles (24 km)
2400AP (DES)
2401SMRF (AES)
with on SM 15 miles (24 km)
2401AP (AES)
5200SM (DES)1
with
5200AP (DES) None allowed in
U.S.A or Canada 2 miles (3.2 km)
5201SM (AES)2
with
5201AP (AES)
5700SM (DES)
with
5700AP (DES)
none 2 miles (3.2 km)
5701SM (AES)
with
5701AP (AES)
5700SMRF (DES)
with on SM 10 miles (16 km)
5700AP (DES)
5701SMRF (AES)
with on SM 10 miles (16 km)
5701AP (AES)
NOTES:
1. DES indicates that the module is preconfigured for Data
Encryption Standard security. See DES Encryption on
Page 19.
2. AES indicates that the module is preconfigured for
Advanced Encryption Standard security. See AES
Encryption on Page 19.
3. Terrain and other line of sight circumstances affect the
distance that can be achieved. Additionally, local or
national radio regulations may govern whether and how
the Passive Reflector can be deployed.
3.3 SYNCHRONIZATION
The CMM is a critical element in the operation of the Canopy system. At one AP cluster site or
throughout an entire wireless system, the CMM provides a GPS timing pulse to each module,
synchronizing the network transmission cycles.
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 in Ethernet protocol to a collocated AP.
2. This AP sends the sync in multipoint protocol over the air to an SM.
3. This SM delivers the sync in Ethernet protocol to a collocated AP.
4. This AP passes the sync in multipoint protocol in the additional link over the air to
SMs.
This design is illustrated in Figure 1.
AP 2 4
SM AP SM
4
3
1
SM
CMM
• Design 4
1. A CMM provides sync in Ethernet protocol to a collocated AP.
2. This AP sends the sync in multipoint protocol over the air to an SM.
3. This SM delivers the sync in Ethernet protocol to a collocated BH timing master.
4. This BH timing master passes the sync in point-to-point protocol in the additional
link over the air to a BH timing slave.
This design is illustrated in Figure 2.
2 BH 4 BH
AP SM -M- -S-
3
1
CMM
• Design 5
1. A CMM provides sync in Ethernet protocol to a collocated BH timing master.
2. This BH timing master sends the sync in point-to-point protocol over the air to a BH
timing slave.
3. This BH timing slave delivers the sync in Ethernet protocol to a collocated AP.
4. This AP passes the sync in multipoint protocol in the additional link over the air to
SMs.
This design is illustrated in Figure 3.
BH 2 BH 4
-M- -S-
AP SM
4
3
1
SM
CMM
Wiring and configuration information for this sync extension is described under Wiring to Extend
Network Sync on Page 67.
3.4 WIRING
The wiring scheme of the Canopy system is displayed in Figure 4.
AP units
network connection
in
300SS CMM2
AC or DC
power in
grounding
system
* Two cables, Ethernet and GPS sync, connect each sector AP to the CMM2.
4 ADVANCED FEATURES
The following features are available in the Canopy system but not required for basic operation.
4.1.1 BRAID
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.
Key Consistency
The DES AP and the DES Backhaul timing master module are factory-programmed to enable or
disable DES encryption. Similarly, the AES AP and the AES Backhaul timing master module are
factory-programmed to enable or disable AES encryption.
In either case, the authentication key entered in the Backhaul Configuration page establishes the
encryption key. For this reason, the authentication key must be the same on each end of the
backhaul link.
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.
Upgradeability
Canopy DES products cannot be upgraded to AES. To have the option of AES encryption, the
service provider 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.
The Canopy software uses token buckets to manage the bandwidth of each SM. Each SM
employs two buckets: one for uplink and one for downlink throughput. These buckets are
continuously being filled with tokens at a rate set by the Sustained Data Rate variable field in the
AP.
BAM also provides secure SM authentication and user-specified DES encryption keys. BAM is an
optional Canopy software product that operates on a networked PC.
If the SM transfers data at the Sustained Data Rate, then the bucket refills at the same rate, and
burst is impossible. If the SM transfers data at a rate less than the Sustained Data Rate, then the
bucket continues to fill with unused tokens. In this case, required bursting occurs at the rate
determined by the number of unused tokens.
After a burst is completed, the bucket is recharged at the Sustained Data Rate. Short bursts
recharge faster than large bursts.
When the burst limit is reached, the data rate falls to the Sustained Data Rate setting. Then later,
when the SM is either idle or transferring data at a rate slower than Sustained Data Rate, the burst
limit recharges at the Sustained Data Rate.
Input Rate
56 Kbps
Sustained Rate
128 Kbps
Burst Allocation
512 Kb
Effective Rate
56 Kbps plus Burst
Input Rate
128 Kbps
Sustained Rate
128 Kbps
Burst Allocation
128 Kb
Effective Rate
128 Kbps with no Burst
Input Rate
128 Kbps
Sustained Rate
128 Kbps
Burst Allocation
56 Kb
Effective Rate
56 Kbps with no Burst
Input Rate
128 Kbps
Sustained Rate
128 Kbps
Burst Allocation
0 Kb
Effective Rate
0 Kbps
The Canopy system separates this traffic by recognizing the IPv4 Type of Service Low Latency bit
(Bit 3). Bit 3 is set by a device outside the Canopy system. If this bit is set, the system sends the
packet on the high-priority channel and services this channel before any normal traffic.
NOTE: To enable the high-priority channel, the operator must configure all high-priority
parameters.
The high-priority channel is enabled by configuration of four parameters in the Configuration web
page. These parameters are:
• High Priority Uplink Percentage
• UAcks Reserved High
• DAcks Reserved High
• NumCtrlSlots Reserved High
(NOT TO SCALE)
Downlink Uplink
Data H
Beacon Control Data Slots Collision Control
Slots P
HP indicates
high-priority slots
Example Allocation
At AP default downlink-to-uplink settings (75% downlink and 25% uplink), if High Priority is set to
25%, then
• in the uplink, the total of reserved slots is equivalent to 25% (2 slots in this example)
and
− the bandwidth is 64 bytes per slot, repeated 400 times each second.
− [2 slots/instance] x [64 bytes/slot] x [8 bits/byte] x [400 instances/second] = 409,600 bps
≈ 400 kbps of uplink bandwidth
• in the downlink, the AP
− does not reserve slots, but will service all high-priority bandwidth requests.
− may become saturated by attempting to service too much high-priority traffic.
− monitors the Low Latency TOS (Type of Service) bit, Bit 3, in the Ethernet frame.
− prioritizes the traffic in the high-priority queue (when Bit 3 is set) according to the
AP configuration settings for the high-priority channel.
4.4 BRANDING
The web-based interface screens on each Canopy module contain the Canopy logo. This logo can
be replaced with a custom company logo. A file named canopy.jpg generates the Canopy logo.
ftp> binary
200 Type set to I
ftp> put canopy.jpg
ftp> quit
221 Goodbye
3. Use a telnet session to add the new canopy.jpg file to the file system, as in the
example session shown in Figure 11.
/---------\
C A N O P Y
Login: root
Password: <password-if-configured>
Telnet+> lsweb
4.7 SNMP
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.
4.7.1 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.
4.7.3 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.
4.7.6 Traps
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.
4.7.7 MIBS
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.
Paths
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)
− registration-authority (1)
− member-body (2)
− identified-organization (3)
• under identified-organization (3) above:
− dod (6)
− other branches
• under dod (6) above:
− 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).
Objects
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.
4.7.8 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 3:
Objects in
category… Control or identify the status of…
NOTE: The operator should not edit these MIB files in ASN.1. These files are intended for
manipulation by only the NMS. However, the operator can view these files through a
commercially available MIB viewer.
• Accessing Subnet, which specifies the subnet mask allows managers to poll the
agents.
• Trap Address, which specifies the IP address of the NMS.
For more information about each of these fields, see the user document that supports the module.
Table 5: Canopy Enterprise MIB objects for APs and BH timing masters
Table 6: Canopy Enterprise MIB objects for SMs and BH timing slaves
To assist end users in this area, the Canopy division offers a starter guide for one of these
viewers—MRTG (Multi Router Traffic Grapher). This starter guide is titled Canopy Network
Management with MRTG: Application Note, and is available in the Library section under Support at
http://www.motorola.com/canopy. MRTG software is available at http://mrtg.hdl.com/mrtg.html.
Other MIB viewers are available and/or described at the following web sites:
http://ns3.ndgsoftware.com/Products/NetBoy30/mibbrowser.html
http://www.adventnet.com/products/snmputilities/
http://www.dart.com/samples/mib.asp
http://www.edge-technologies.com/webFiles/products/nvision/index.cfm
http://www.ipswitch.com/products/whatsup/monitoring.html
http://www.koshna.com/products/KMB/index.asp
http://www.mg-soft.si/mgMibBrowserPE.html
http://www.mibexplorer.com
http://www.netmechanica.com/mibbrowser.html
http://www.networkview.com
http://www.newfreeware.com/search.php3?q=MIB+browser
http://www.nudesignteam.com/walker.html
http://www.oidview.com/oidview.html
http://www.solarwinds.net/Tools
http://www.stargus.com/solutions/xray.html
http://www.totilities.com/Products/MibSurfer/MibSurfer.htm
5 SITE PLANNING
The following considerations are critical in the choice of a location for the wireless network
infrastructure.
Note: Since each site is unique, typically many additional considerations are critical.
Canopy™ System
Calculator
Automatically calculate
Inner Radius of Vertical Beam Width
Outer Radius of Vertical Beam Width
Distance from near -3 dB to far -3 dB
from known
Angle of Antenna Downward Tilt
Elevation of Antenna
Vertical Beam Width
Canopy™ System
Calculator
Automatically calculate
Minimum Antenna Elevation
from known
Distance from Transmitter to Receiver
Canopy™ System
Calculator
Automatically calculate
Angle of Antenna Downward Tilt
from known
Distance from Transmitter to Receiver
Elevation of Transmitter
Elevation of Receiver
Figure 14: Canopy System Calculator page for antenna downward tilt
An unobstructed line of sight is important, but is not the only determinant of adequate placement.
Even where the path has a clear line of sight, obstructions such as terrain, vegetation, metal roofs,
or cars may penetrate the Fresnel zone and cause signal loss. Figure 15 illustrates an ideal
Fresnel zone.
Fresnel zone
transmitter
Transmitter
or Amplifier
receiver
Canopy™ System
Calculator
Automatically calculate
Fresnel Zone (vertical dimension)
from known
Distance from Transmitter to Receiver
Distance from High-elevation Object to Receiver
Frequency
Figure 16: Canopy System Calculator page for Fresnel zone dimensions
Tx antenna Rx antenna
loss gain
free space signal
Tx Rx
cable cable
loss loss
distance
Rx
Tx signal
power level
Transmitter
transmitter receiver
or amplifier
Amplifier or amplifier
Canopy™ System
Calculator
Automatically calculate
Free Space Path Loss
from known
Distance from Transmitter to Receiver
Frequency
2. Update the SMs in a telnet session to the AP, as shown in Figure 20.
3. In the Canopy Boot Version field of the Status page of each SM that was targeted for
update, confirm that the SM has been updated.
4. Turn off updating in a telnet session to the AP, as shown in Figure 21.
RESULT: All SMs that are registered to the AP are upgraded to the later release.
Regardless of whether 2.4-, 5.2-, or 5.7-GHz modules are deployed, channel separation
between modules should be at least 20 MHz.
A BH and an AP on the same tower, or separated by less than 100 feet (30 meters), require a
CMM. The CMM properly synchronizes all Canopy modules to prevent interference and desensing
of the modules.
This functionality can be used during the alignment of an SM, but is especially helpful for frequency
selection during site planning.
The following procedure causes the SM to drop any active RF link. If a link is dropped
when the spectrum analysis begins, the link can be re-established after a 15-minute
interval has elapsed.
The following procedure can cause the SM to drop an active RF link to a module that is
too far from the low-power AP. If a link is dropped when Power Control is set to Low,
the link can be re-established by only Ethernet access.
This recommendation allows 20 MHz of separation between one pair of channels and 22.5 MHz
between the other pair. The network planner can use the Spectrum Analysis feature in an SM or
BHS, or use a standalone spectrum analyzer, to evaluate the RF environment.
Where spectrum analysis identifies risk of interference for any of these channels, the planner can
compromise this recommendation as follows:
• Select 2.4375 GHz for the middle channel
• Select 2.455 GHz for the top channel
• Select 2.4175 GHz for the bottom channel
In any case, the plan should allow at least 20 MHz of separation between channels. See Spectrum
Analysis on Page 50.
The channels of adjacent APs should be separated by at least 20 MHz. However, 25 MHz of
separation is advised.
The channels of adjacent APs should be separated by at least 20 MHz. However, 25 MHz of
separation is recommended.
The fully populated cluster requires only three channels, each reused by the module that is
mounted 180° opposed. The four channels above are also used for backhaul point-to-point links.
The channels of adjacent APs should be separated by at least 20 MHz. However, 25 MHz of
separation is advised.
The fully populated cluster requires only three channels, each reused by the module that is
mounted 180° offset. The six channels above are also used for backhaul point-to-point links.
As noted above, a 5.7-GHz AP enabled for ISM/U-NII frequencies can operate on a frequency as
high as 5.840 GHz. Where engineering plans allow, this frequency can be used to provide an
additional 5-MHz separation between AP and BH channels.
NOTE: For more information on sector IDs, see Configuration Page on Page 78.
Direction of Access
Point Sector Frequency Sector ID Symbol
Direction of Access
Point Sector Frequency Sector ID Symbol
Direction of Access
Point sector Frequency Sector ID Symbol
C B
A B C A
C B A C B
B C A B C
A C B A
A B C A
C B A C B
B C A B C
A C B A
B C
6 IP NETWORK PLANNING
A proper IP addressing method is critical to the operation and security of a Canopy network. The
following information provides the background for the planner or operator to select an appropriate
method.
6.1.1 IP Address
The IP address is a 32-bit binary number that has four parts (octets). This set of four octets has two
segments, depending on the class of IP address. The first segment identifies the network. The
second identifies the hosts or devices on the network. The subnet mask marks a boundary
between these two sub-addresses.
In this example, the network address is 169.254, and 216 (65,536) hosts are addressable.
When a computer is brought online and a DHCP server is not accessible (such as when the server
is down or the computer is not plugged into the network), Microsoft and Apple operating systems
default to an IP address of 169.254.x.x and a subnet mask of 255.255.0.0 (169.254/16).
From the factory, each Canopy module—AP, BH, or SM—is assigned a unique MAC (Media
Access Control) address and the following default networking information:
• IP address of 169.254.1.1
• Subnet mask of 255.255.0.0
• Network gateway of 169.254.0.0
The operator must first know how the service provider assigns IP addresses on this
network.
7 AP MODULE INSTALLATION
The following steps are required to install a Canopy AP:
1. Unpacking the Canopy Products. See Page 61.
2. Cabling the AP. See Page 62.
3. Configuring the AP. See Page 67.
4. Installing the AP and, optionally, the CMM and GPS (Global Positioning System) antenna.
See Installing the AP on Page 70.
5. Verifying System Performance See Page 72.
Unpack the equipment, making sure that all of the components ordered have arrived. Saving all the
packing materials is recommended. These can be used to either return products or transport the
equipment to and from installation sites.
Canopy AP
RJ11
Connector
RJ45
Connector
Connection
LEDs
Base Cover
Base Cover Base Cover
Release Ethernet
Ethernet
Cable
Lever Cable
NOTE: Table 11 identifies the LEDs in order of their left-to-right position as the cable
connections face downward.
Color
when Status Information
Label Active Provided Notes
ACT/4 orange Presence of data activity Flashes during data transfer. Frequency of flash is
on the Ethernet link not a diagnostic indication.
SES/2 green Unused on the AP SES is the session indicator on the CMM.
Either RJ-45 straight-thru or RJ-45 crossover cable can be used to connect a (network interface
card), hub, router, or switch to a module. Canopy modules that are currently available can auto-
sense whether the Ethernet cable in a connection is wired as straight-thru or crossover. Some
modules that were sold earlier do not.
Table 12 identifies by MAC address whether a module auto-senses the Ethernet cable type.
TX+ 1 1 RX+
TX- 2 2 RX-
RX+ 3 3 TX-
4 4
+V return +V return
5 5
RX- 6 6 TX-
7 7
+V +V
8 8
An RJ-11 cable is commonly used to connect a device to a phone line. This cable resembles the
RJ-45 Ethernet cable except for a thinner cord and smaller plug. The Canopy system uses an
RJ-11 cable to connect the AP or BH to GPS synchronization. Presuming CAT 5 cable and 6-pin
RJ-11 connectors, the following diagram shows the wiring of the cable for GPS sync.
Pin 1 → white / orange ← Pin 1
Pin 2 → white / green ← Pin 2
Pin 3 → white / blue ← Pin 3
Pin 4 → green ← Pin 4
Pin 5 → blue ← Pin 5
Pin 6 → orange ← Pin 6
RX+ 3 3 TX+
not 4 4 not
used used
5 5
Protective Earth (PE) Protective Earth (PE)
(ground) 6 6 (ground)
not not
used used
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.
Procedure 11: Bypassing proxy settings to gain access module web pages
1. Launch Microsoft Internet Explorer.
2. Select Tools → Internet Options → Connections → LAN Settings.
3. Uncheck the Use a proxy server… box.
NOTE: If an alternate web browser is used, the menu selections differ from the above.
Required Steps
Perform the following steps to configure the AP:
Procedure 12: Setting mandatory Configuration page parameters
1. Remove the base cover of the AP. (See Figure 24 on Page 61.)
2. In the powered down state, connect the Ethernet cable to the Ethernet port on both the AP
and the computer.
3. Connect a power source to the AP.
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. See Diagnostic LEDs on
Page 62.
4. Based on the origination source of the sync pulse for this AP, set the Sync Input
parameter. See Sync Input on Page 79.
5. Assign an RF frequency for the module to transmit. See RF Frequency Carrier on Page 79.
6. Assign values for uplink and downlink bandwidth capping. See
• Sustained Uplink Data Rate on Page 81.
• Uplink Burst Allocation on Page 81.
• Sustained Downlink Data Rate on Page 81.
• Downlink Burst Allocation on Page 81.
NOTE: If the AP is in a cluster with other modules, then this parameter must be set
exactly the same on all modules.
7. Assign an IP address to the module for the target network, and assign an appropriate
subnet mask and network gateway. See
• LAN1 Network Interface Configuration, IP Address on Page 87.
• LAN1 Network Interface Configuration, Subnet Mask on Page 87.
• LAN1 Network Interface Configuration, Gateway IP Address on Page 87.
8. Configure the appropriate color code on the AP so that SMs can register. (The SM color
codes must match the AP color code for registration.) See Color Code on Page 81.
9. Configure the maximum range at which the AP can register an SM. See Max Range on
Page 81.
NOTE: If the AP is in a cluster with other modules, then this parameter must be set
exactly the same on all modules.
Optional Steps
In addition, the operator can perform the following optional steps:
“ , . ‘ { } / \
; : [ ] ( ) ` ~
NOTE: Canopy products offer no software utility for alignment of APs or Backhaul timing
master modules.
4. 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.)
5. Using stainless steel hose clamps or equivalent fasteners, lock the AP in the proper
direction and downward tilt.
One AP in each AP cluster must be connected to a CMM. For a module that is connected
to a CMMmicro, the Sync Input parameter in the Configuration web page must be
configured to Sync to Received Signal (Power Port). For a module that is connected to a
CMM2, the Sync Input parameter in the Configuration web page must be configured to
Sync to Received Signal (Timing Port).
6. For a single AP that is collocated with a CMM, connect the module to an Ethernet/Power
port on the CMM, as shown in Figure 25.
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. See Diagnostic LEDs on
Page 62.
Fuse receptacle
AC power
connectors
115/230 V switch
NOTE: The AC power connectors are labeled N for Neutral, L for Line, and PE for
Protective Earth or ground. The maximum thickness of wire to be used is 4 mm2
or 12 AWG.
For a single AP that is not collocated with a CMM, connect the module to a power supply.
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. See Diagnostic LEDs on
Page 62.
For an AP cluster, connect the GPS sync port cable of at least one AP to the CMM.
Access to the web-based interface is available only through a computer that is directly connected
or connected through a network to the AP. If the computer is not connected to a network when
configuring the module on a bench, disabling the proxy setting in the computer may be required.
In the address bar of your browser, enter the IP address of the AP (default is 169.254.1.1).
Quick Start
Status
Configuration
IP Configuration
Event Log
LUID Select
Link Test
Time & Date
Sessions
GPS Status
Ethernet Stats
Expanded Stats
The Status page provides information on the operation of the module. This is the default web page
for the module.
Device Type
This field indicates the type of the Canopy module. Values include the frequency band of the
module, the protocol that is used, and the MAC address of the module.
Software Version
This field indicates the software release that is operated on the module, the release date of the
software, the time, and whether the module is secured by DES or AES encryption (see Security
Features on Page 19). When requesting technical support, provide the information from this field.
FPGA Version
This field indicates the version of the field-programmable gate array (FPGA) on the module. When
requesting 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.
Ethernet Interface
This field indicates the configuration of the Ethernet interface on the module.
Registered SM Count
This field indicates how many SMs are registered to the AP.
• Generating sync indicates that the module is set to generate the sync pulse.
• Receiving Sync indicates that the module is set to receive a sync pulse from an
outside source and is receiving the pulse.
• ERROR: No Sync Pulse indicates that the module is set to receive a sync pulse from
an outside source and is not receiving the pulse.
NOTE: When this message is displayed, the AP transmitter is turned off to avoid
self-interference within the Canopy system.
Site Name
This field indicates the name of the physical module. The operator can assign or change this name
on the Configuration web 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. The operator can provide or
change this information on the Configuration web page. This information is also set into the
sysName SNMP MIB-II object and can be polled by an SNMP management server.
The Configuration web page contains all of the configurable parameters that define how the
module operates. The first line of information on the Configuration screen echoes the Device Type
from the Status web page.
Sync Input
The operator specifies the type of synchronization for this AP to use.
The operator selects Sync to Received Signal (Power Port) to set this AP to receive GPS sync
from a connected CMMmicro.
The operator selects 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.
The operator selects Generate Sync Signal where the AP does not receive sync, and no other AP
or BHM is active within the link range. For link range information, see Table 2 on Page 15.
RF Frequency Carrier
The operator specifies the frequency that the module will 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
• 2.4-GHz AP Channels on Page 52.
• 5.2-GHz AP Channels on Page 53.
• 5.7-GHz AP Channels on Page 54.
Downlink Data
The operator specifies the percentage of the aggregate throughput that is needed 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%.
If the AP is in cluster, then this parameter must be set exactly the same on all other
modules in the cluster.
NOTE: Parameter settings for the high-priority channel require careful consideration
because bandwidth that is allocated to this channel decreases bandwidth on the regular
channel, regardless of whether high-priority traffic exists. See High-Priority Bandwidth on
Page 22.
Where the high-priority channel is desired, all high-priority parameters must be set. If all
are not set, then the high-priority channel is not active.
Total NumUAckSlots
The operator specifies how many slots are used to acknowledge data that an SM receives. The
default value of this parameter is 3. This value should be kept, except when the operator
anticipates a high amount of traffic. If the value of 3 is entered for the following (Uacks Reserved
High) parameter, then this parameter should be set to 6. The allowed range for this parameter is
1 to 7.
If the AP is in cluster, then this parameter must be set exactly the same on all other
modules in the cluster.
NumDAckSlots
The operator specifies how many slots are used to acknowledge data that the AP receives. The
default value of this parameter is 3. This value should be kept, except when the operator
anticipates a high amount of traffic. If the value of 3 is entered for the following (Dacks Reserved
High) parameter, then this parameter should be set to 6. The allowed range for this parameter is
1 to 7.
If the AP is in cluster, then this parameter must be set exactly the same on all other
modules in the cluster.
NumCtlSlots
The operator specifies how many slots are used to send control messages to an AP. The default
value of this parameter is 3. This value should be kept, except when the operator anticipates a high
amount of traffic. If the value of 3 is entered for the following (NumCtlSlots Reserved High)
parameter, then this parameter should be set to 6. The allowed range for this parameter is 1 to 16.
If the AP is in cluster, then this parameter must be set exactly the same on all other
modules in the cluster.
NOTE: A description of the interactions between sustained and burst data settings for the following
parameters is provided in Interaction of Burst Data and Sustained Data Settings on Page 21.
Color Code
The operator specifies 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. Color code allows the operator to
segregate an individual network or neighbor Canopy networks.
Color code also allows the operator to force an SM to register to only a specific AP, even if the SM
can reach 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).
Sector ID
The operator specifies a number to associate with this AP. The Sector ID does not affect the
operation of the AP.
On the AP Eval Data web page of the SM, the Sector ID field identifies the AP that the SM sees.
For efficient and accurate network management, the operator is advised to
• assign a unique Sector ID to each sector in an AP cluster.
• repeat the assignment pattern throughout the entire Canopy system.
Max Range
The operator enters a number of miles that specifies the furthest distance from which an SM is
allowed to register. Regardless of this distance, the SM must meet the minimum requirements for
an acceptable link. If the AP is in cluster, then this parameter on all units must be set exactly the
same. The default Max Range is 2 miles.
NOTE: A value of 15 for this parameter decreases the number of available data slots by 1.
Display-Only Access
The operator enters the same password in both Display-Only Access fields for verification. When
used, the display-only password allows only viewing activities on the module.
This protection interacts with the Full Access password protection as follows:
• If the display-only password is set and the Full Access password is not, then:
− The display-only password is tied to telnet and FTP sessions to the module.
− Anyone who enters the display-only password can view or change activities. This
configuration is not recommended.
• If the Full Access password is also set, then the Full Access password is tied to
telnet and FTP sessions.
• If the display-only password is not set and the Full Access password is, then no
password is required to view activities on the module.
• If neither password is set, then anyone can view or change activities. This
configuration is not recommended.
If the operator-assigned Display-Only Access password is forgotten, then the operator must both
Full Access
The operator enters the same Full Access password in both fields for verification. When used, the
Full Access password
• allows both viewing and change activities on the module.
• is tied to telnet and FTP sessions to the module.
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, the user name root must be entered in
addition to the password.
If the operator-assigned Full Access password is forgotten, then the operator 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 IP Address and Password Setting on Page 66.
NOTE: The operator can unset either password (revert the access to no password required). To do
so, the operator types a space into the field and reboots the module. Any password must be
entered twice to allow the system to verify that 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.
As shown in Figure 29, the Configuration page continues with the following parameters:
Airlink Security
The operator specifies the type of air link security to be used on 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.
SM Scan Privacy
When the SM Scan Privacy feature is enabled, the operator can use this field to suppress the
display of data about this AP on the AP Eval Data page of all SMs that register.
Authentication Mode
If the optional Bandwidth and Authentication Manager (BAM) server is implemented, then the
operator can use this field to select from among the following authentication modes:
• Authentication Not Available if not using the BAM—no SM is allowed to
authenticate.
• Authentication Enabled—any SM can authenticate in the BAM server.
• Authentication Optional—an SM that is not compatible with the BAM server can
access the wireless network through this AP.
An inappropriately low Bridge Entry Timeout setting may lead to temporary loss of
communication with some end users.
• If the AP is in cluster, then the AP Background BER Mode must be set exactly the
same on all other modules in the cluster.
• When the AP Background BER Mode is turned on, the aggregate available bandwidth
decreases by approximately 200 kbps. For this reason, BER data collection should be
limited to diagnostic intervals.
Power Control
In Release 4.1 and later releases, the operator selects either
• Low to set the BH timing master to operate at 18 dB less than full power to reduce the
possibility of self-interference with a nearby module.
• Normal to allow the BH timing master to operate at full power.
Selection of Low can cause the BH to drop an active RF link to a module that is too far
from the low-power BH. If a link is dropped when Power Control is set to Low, the link
can be re-established by only Ethernet access.
See Power Reduction to Mitigate Interference on Page 51.
Community String
The operator specifies a control string that allows an SNMP management server to access SNMP
information. No spaces are allowed in this string. The default string is Canopy.
Accessing Subnet
The operator specifies the network that is allowed to access SNMP information from the module.
The following two types of information must be entered:
• the network IP address in the form xxx.xxx.xxx.xxx
• the CIDR (Classless Interdomain Routing) prefix length in the form /xx (for example,
198.32.0.0/16 where /16 is a subnet mask of 255.255.0.0).
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
The operator specifies the IP address (xxx.xxx.xxx.xxx) of an SNMP management server to which
trap information should be sent. Trap information informs the monitoring system that something has
occurred. For example, trap information is sent:
• After a reboot of the module.
• When an SNMP management server 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
The operator can select either Sync Status or Session Status to enable SNMP traps.
Permission
The operator can set this parameter to Read Only to disallow any parameter changes by the
SNMP.
With this selection, 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.
Site Name
The operator specifies 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 SNMP management server. The buffer
size for this field is 128 characters.
Site Contact
The operator enters contact information for the module administrator. This parameter is written into
the sysContact SNMP MIB-II object and can be polled by an SNMP management server. The
buffer size for this field is 128 characters.
Site Location
The operator enters 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 SNMP management server. The
buffer size for this field is 128 characters.
Save Changes
When the operator clicks this button, any changes that have been 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 the operator clicks this button, the module reboots. When the operator has changed
parameters in the Configuration page, the system highlights Reboot button as a reminder that a
reboot (in addition to a save) is required to implement the changes.
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
If the private IP address of the AP is changed, then the new address must
• designate a Class C subnet that is not used for anything else.
• have the form xxx.xxx.xxx.1, where 1 is the value of the last octet of the address.
NOTE: An SM is not required to have an operator-assigned IP address where space is limited for
subnet allocation. 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.
Save Changes
When the operator clicks this button, any changes that have been 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 the operator clicks this button, the module reboots. When the operator has changed
parameters in the Configuration page, the system highlights Reboot button as a reminder that a
reboot (in addition to a save) is required to implement the changes.
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.
This web page allows the operator to view the web pages of registered SMs over the RF link.
The Link Capacity Test page allows the operator to measure the throughput and efficiency of the
RF link between two Canopy modules.
The Time & Date web page allows the operator to set the time and date for the AP. The operator
must set the time and date whenever both
• the AP is not connected to a CMM.
• a power cycle of the AP has occurred.
Time hh:mm:ss
Date mm/dd/yyyy
where:
The Session web page provides information about each SM that has registered to the AP. This
information is useful for managing and troubleshooting a Canopy system.
LUID
This field displays the LUID (logical unit ID) of the SM. As each SM registers to the AP, the system
assigns an LUID of 2 or a higher number to the SM. If an SM loses registration with the AP and
then regains registration, the will retain the same LUID.
NOTE: The LUID association is lost when a power cycle of the AP occurs.
MAC
This field displays the MAC address (or electronic serial number) of the SM.
State
This field displays the current status of the SM as either
• IN SESSION to indicate that the SM is currently registered to the AP.
• IDLE to indicate that the SM was registered to the AP at one time, but now is not.
Software Version
This field displays the software release that operates on the SM, the release date of the software,
the time, and whether the module is secured by DES or AES encryption (see Security Features on
Page 19). When requesting technical support, provide the information from this field.
An unpopulated Software Version parameter indicates a version earlier than Version 3.1.
FPGA Version
This field displays the version of FPGA that runs on the SM. An unpopulated FPGA Version
parameter indicates that a version earlier than Version 082002 runs on the SM.
Session Timeout
This field indicates the maximum interval in hours that the SM may sustain a single session with
this AP.
AirDelay
This field displays the distance of the SM from the AP. To derive the distance in meters, the
operator multiplies the displayed number by 0.3048. To derive the distance in feet, the operator
multiplies the displayed number by 49.
Session Count
This field displays how many sessions the SM has had with the AP. If the number of sessions is far
greater than the number that other SMs registered to the AP have had, then this SM may have an
installation problem.
Reg Count
This field displays how many registration request messages the AP has received from the SM. If
the number of these messages is far greater than the number from other SMs registered to the AP,
then this SM may have an installation problem.
Re-Reg Count
This field displays how many registration request messages the AP has received from the SM that
is already in session. If the number of these messages is far greater than the number from other
SMs that are both registered to the AP and in session, then this SM may have an installation
problem.
RSSI (Avg/Last)
This field displays the average and the latest RSSI (received signal strength indicator) value for the
SM.
Jitter (Avg/Last)
This field displays the average and the latest jitter value for the SM.
This page also displays the state of the antenna in the Antenna Status field as either Unknown or
OK. This information may be helpful in a decision of whether to climb a tower to diagnose a
perceived antenna problem.
inoctets count
This field displays how many octets were received on the interface, including those that deliver
framing information.
inucastpkts count
This field displays how many inbound subnetwork-unicast packets were delivered to a higher-layer
protocol.
innucastpkts count
This field displays how many inbound non-unicast (subnetwork-broadcast or subnetwork-multicast)
packets were delivered to a higher-layer protocol.
indiscards count
This field displays how many inbound packets were discarded without errors that would have
prevented their delivery to a higher-layer protocol. (Some of these packets may have been
discarded to increase buffer space.)
inerrors count
This field displays how many inbound packets contained errors that prevented their delivery to a
higher-layer protocol.
inunknownprotos count
This field displays how many inbound packets were discarded because of an unknown or
unsupported protocol.
outoctets count
This field displays how many octets were transmitted out of the interface, including those that
deliver framing information.
outucastpkts count
This field displays how many packets for which the higher-level protocols requested transmission to
a subnetwork-unicast address. The number includes those that were discarded or not sent.
outnucastpkts count
This field displays how many packets for which the higher-level protocols requested transmission to
a non-unicast (subnetwork-broadcast or subnetwork-multicast) address. The number includes
those that were discarded or not sent.
outdiscards count
This field displays how many outbound packets were discarded without errors that would have
prevented their transmission. (Some of these packets may have been discarded to increase buffer
space.)
outerrrors count
This field displays how many outbound packets contained errors that prevented their transmission.
RxBabErr
This field displays how many receiver babble errors occurred.
EthBusErr
This field displays how many Ethernet bus errors occurred on the Ethernet controller.
CRCError
This field displays how many CRC errors occurred on the Ethernet controller.
RxOverrun
This field displays how many receiver overrun errors occurred on the Ethernet controller.
Late Collision
This field displays how many late collisions occurred on the Ethernet controller. A normal collision
occurs during the first 512 bits of the frame transmission. A collision that occurs after the first 512
bits is considered a late collision.
A late collision is a serious network problem because the frame being transmitted is
discarded. A late collision is most commonly caused by a mismatch between
duplex configurations at the ends of a link segment.
RetransLimitExp
This field displays how many times the retransmit limit has expired.
TxUnderrun
This field displays how many transmission-underrun errors occurred on the Ethernet controller.
CarSenseLost
This field displays how many carrier sense lost errors occurred on the Ethernet controller.
The Expanded Stats page includes a link to a Reg Failed SMs web page, which provides
• the MAC address of each SM that attempted to register with this AP but failed.
• the time of the attempt.
• the reason for the failure.
A power cycle or reboot drops the contents of this page.
The Reg Failed SMs web page identifies SMs that have recently attempted and failed to register to
this AP.
If NAT (network address translation) is not active on this AP, then the Bridge Table web page
provides the MAC addresses of the SMs for which this AP serves as a Layer 2 bridge.
NOTE: For the RF environment in which Canopy BHs, APs, and CMMs typically
operate, the use of shielded cable is strongly recommended for infrastructure
cables that connect these modules.
10 AP MODULE SPECIFICATIONS
Table 13 provides the specifications of the Canopy AP.
Maximum Aggregate Downlink: 4.6 Mbps at default allocation of 75%, but variable
Throughput for 2.4-, 5.2-, based on packet size.
and 5.7-GHz SMs Uplink: 1.6 Mbps at default allocation of 25%, but variable based
on packet size.
Operating Range Up to 2 miles (3.2 km) with integrated antenna in the 5.2-GHz
band.
Up to 5 miles (8 km) with integrated antenna in the 2.4-GHz band
Up to 10 miles (16 km) with SM mounted to passive reflector in
the 5.7-GHz band.
Up to 15 miles (24 km) with SM mounted to passive reflector on
the SM in the 2.4-GHz band.
Antenna Gain 7 dB
F/B Ratio 15 dB
Ethernet, GPS sync, and The use of cables that are rated for the operation temperature of
GPS coax cables the product and that conform to UV light protection specifications
is mandatory. The use of shielded cables is strongly
recommended. For information about the supplier of these
cables, see CANOPY SYSTEM ACCESSORIES on Page 99.
Protocols Used IPV4, UDP, TCP, ICMP, Telnet, HTTP, FTP, SNMP, DES.
Optionally, AES.
Protocols Supported Switched Layer 2 Transport with support for all common Ethernet
protocols, such as IPV6, NetBIOS, DHCP, IPX.
Reflector Dish Weight 6.5 lb (2.9 kg) with assembly, without module