Canopy® Software Release 9.4.

2 Release Notes
Issue 1 May 2009

Notices See important regulatory and legal notices in Section 10 on Page 34. Trademarks, Product Names, and Service Names MOTOROLA, the stylized M Logo, Canopy, and all other trademarks indicated as such herein are registered trademarks of Motorola, Inc. ® Reg. US Pat & Tm. Office. All other product or service names are the property of their respective owners. © 2009 Motorola, Inc. All rights reserved

http://www.motorola.com/canopy

Release 9.4.2

Release Notes

Table of Contents
1 Introduction ............................................................................................................... 6 1.1 1.2 1.3 1.4 1.5 1.6 1.7 2 Notes and Highlights .......................................................................................... 6 Abbreviations ..................................................................................................... 7 Names ............................................................................................................... 7 Identifying Hardware Series (P7, P8, P9, P10, P11) .......................................... 8 Document Change History ................................................................................. 8 Feedback on Documentation ............................................................................. 9 Technical Support .............................................................................................. 9

Features and Enhancements .................................................................................. 10 2.1 2.2 2.3 Release 9.4.2 Enhancements .......................................................................... 10 Performance – Packets per Second ................................................................. 10 Support for P11 Hardware................................................................................ 11

3 4 5

Resolved Issues ...................................................................................................... 12 Known Open Issues ................................................................................................ 14 Notes and Reference ............................................................................................... 16 5.1 5.2 Notes ............................................................................................................... 16 Operation Based on Region Code and Frequency Band .................................. 19

6 7

Canopy MIB.............................................................................................................. 21 Upgrading to Release 9.4.2 ..................................................................................... 22 7.1 7.2 7.3 7.4 Before You Upgrade ........................................................................................ 22 Obtaining and preparing CNUT or Prizm.......................................................... 24 Obtaining Upgrade Packages .......................................................................... 25 Performing the Upgrade Via CNUT or Prizm .................................................... 25

8

Collocation............................................................................................................... 28 8.1 8.2 8.3 Collocating 5.2-GHz and 5.4-GHz Modules...................................................... 28 Collocating 5.4-GHz and 5.7-GHz modules...................................................... 29 Collocating Same-Frequency Band Modules ................................................... 29

9

Performance Benchmarking Process .................................................................... 31

10 Regulatory and Legal Notices................................................................................ 34

Issue 1, May 2009

Page 3

Release 9.4.2

Release Notes

10.1 Important Note on Modifications ...................................................................... 34 10.2 National and Regional Regulatory Notices....................................................... 34 10.3 RF Exposure Separation Distances ................................................................. 40 10.4 Legal Notices................................................................................................... 43 10.5 Limit of Liability ................................................................................................ 45

Issue 1, May 2009

Page 4

...................4.....................14 Table 6: New Notes for Release 9...................................................................................................40 Table 14: Calculated exposure distances and power compliance margins ................................................................16 Table 7: Previous Notes ............................4.23 Figure 4: Benchmark test setup......................................................17 Table 8: Release 9.........................................40 Table 13: Exposure separation distances........................................8 Figure 2: Scheduling option – if viewable..2 ......2 enhancements ...........4.......4.......................... indicates this is a P9 board............................................................10 Table 3: Packet per Second (pps) performance .....and 5...........................2 .....2 Release Notes List of Tables Table 1: Product Names..............4..............2 operation based on Region Code and frequency band ...............................41 List of Figures Figure 1: Board Type on modules running Release 8......2-GHz interfering frequencies .............. ..........8 Figure 3: Upgrade path for operating sectors .............................34 Table 12: Disclosure table ............33 Issue 1................20 Table 9: Radios Upgradeable to Release 9................................................................................................22 Table 10: 5...........28 Table 11: US FCC IDs and Industry Canada Certification Numbers and covered configurations ........2 ...... May 2009 Page 5 ..........................................................................................................10 Table 4: Issues resolved in Release 9.......7 Table 2: Release 9.................................................................................................................................................................................12 Table 5: Known open issues .........................................................Release 9............4......................................4..

Release 9.1. see section 7.2 is not applicable to PMP 35500 (3. This release is a general release applicable to    PMP 100 and PTP 100 (FSK) PMP 54400 and PTP 54200 (5. see Upgrade Tool Options on Page 23. never released for download.4-GHz OFDM). PMP 54400 and PTP 54200 (5.5-GHz OFDM) For details on applicability.4. For details. If you receive new radios with Release 9. May 2009 Page 6 .1 was a manufacturing-only release.4.1 and Table 9: Radios Upgradeable to Release 9. and PMP 49400 and PTP 49200 (4.4.9-GHz OFDM BHs) are now supported.4.2. see    Table 2: Release 9.4.9-GHz OFDM).4. Issue 1.1.4.1 with Patch 7 is recommended for upgrading modules to Release 9.4. For detailed information. PTP 49200 bridges (4. This release brings all these products up to the same level of features and resolved issues.9-GHz OFDM) Release 9.4-GHz OFDM) PMP 49400 and PTP 49200 (4.2.2 enhancements on Page 10 Table 4: Issues resolved in Release on Page 12 Table 5: Known open issues on Page 14 Either CNUT 3.4.2 include   Release 9. 1. Highlights of Canopy Release 9.2. PMP 54400 and PTP 54200 (5.1 NOTES AND HIGHLIGHTS  One uniform release for PMP 100 and PTP 100 (FSK).2 on page 22.4.12 or Prizm 3.2 Release Notes 1 Introduction These notes cover Canopy Release 9. upgrade them to Release 9.4-GHz OFDM) now offer the Release 9 feature set.

either timing master or timing slave Backhaul Module – timing master Backhaul Module – timing slave Access Point Module Subscriber Module Canopy Network Updater Tool Cluster Management Module Dynamic Frequency Selection for radar avoidance Management Information Base Shorthand for hardware series levels European Telecommunications Standards Institute Point to Multi-Point Point to Point The following abbreviations may be used in these notes: P7/P8/P9/P10/P11 ETSI PMP PTP 1.4-GHz OFDM PMP 5. May 2009 Page 7 .9-GHz OFDM PMP 4.9-GHz OFDM AP 4.4-GHz OFDM SM Canopy 5.4-GHz OFDM BH Canopy 4.2 ABBREVIATIONS BH BHM BHS AP SM CNUT CMM DFS MIB Backhaul Module. and example model numbers. older names.4-GHz OFDM AP 5.3 NAMES Table 1: Product Names Product Name Previous Name Older Name Model Number (example) — 5700AP 5750AP 5760SM 5700SM 5750SM — — 5700BH 5700BH20 — 5440AP 5440SM 5440BH — 4940AP 4940SM Table 1 maps product names to previous names. PMP 100 Series CAP 120 CAP 130 CSM 110 CSM 120 CSM 130 PTP 100 Series PTP 110 PTP 120 PTP 130 PMP 54400 Series CAP 54400 CSM 54400 PTP 54200 Series PMP 49400 Series CAP 49400 CSM 49400 PMP 100 and PMP 200 Series CAP 100 CAP 200 — CSM 100 CSM 200 — — PTP 100 Lite PTP 100 Full — — — — — — — Canopy FSK point-to-multipoint Classic AP Advantage AP Lite SM SM Advantage SM Canopy FSK BHs 4 Mbps BH.2 Release Notes 1.4.Release 9.9-GHz OFDM SM Issue 1. 2 Mbps BH BH10 (7 Mbps BH) BH20 (14 Mbps BH) Canopy 5.

9-GHz OFDM BH Canopy 3. 1. The following methods can be used to identify the hardware series of a module: Figure 1: Board Type on modules running Release 8  ◦ For modules that are running Release 7. If a Scheduling option is present. then the hardware series is P9. under Board Type as shown in Figure 1. The hardware series is shown under Hardware Platform as 7.6.4.Release 9.2 Release Notes Product Name Previous Name Older Name Model Number (example) 4940BH — 3540AP 3540SM PTP 49200 Series PMP 500 Series CAP 35500 CSM 35500 — — — — Canopy 4.4 IDENTIFYING HARDWARE SERIES (P7. 10. P9. as shown in Figure 2. or 11. P8.  For modules running any release.5 Issue 1 DOCUMENT CHANGE HISTORY First issue Issue 1. 9. May 2009 Page 8 .5-GHz OFDM PMP 3. 8.3. view the Configuration web page.5-GHz OFDM SM 1. then the series is either P7 or P8. P10.5-GHz OFDM AP 3. look on the Home => General Status tab. Figure 2: Scheduling option – if viewable. P11)  For modules that are running Release 8 or Release 9. indicates this is a P9 board. open a telnet interface to the module and enter version. ◦ If no Scheduling option is present.

software release on each module. complete.7 TECHNICAL SUPPORT Tip! Do not clear the Event Log after you encounter issues.motowi4solutions. as appropriate. Europe email: essc@motorola. Escalate the problem to Canopy Technical Support or other designated Tier 3 technical support: Worldwide Canopy Technical Support email: technical-support@canopywireless.com/support/library/. IP addresses. Here is the escalation path for resolution of a problem: 1.com phone: +44 (0)1793 564680 Calls are logged 24 x 7. high priority channel. Consider checking the Community Forum and Knowledge Base at http://motorola.6 FEEDBACK ON DOCUMENTATION Is this document accurate. 1. Escalate the problem to your Canopy supplier or reseller. VLAN. cases are worked Mon-Fri 09:00 – 17:00 GMT. like NAT. Check documentation:   this document Canopy System Release 8 Users Guide. You may be asked to run the Support Tool on CNUT or Prizm to provide a complete network picture. MAC addresses. or CIR. please include. 2.com/support/community. and clear? How can it be improved? Please send your feedback on Canopy documentation to technical-documentation@canopywireless. May 2009 Page 9 . and features enabled.com phone: 1-888-605-2552 or +1 217 824 9742 Canopy Technical Support. 4. Issue 1.4. 3. It may be useful to Technical Support.com. When you send e-mail or call.2 Release Notes 1.motowi4solutions.Release 9. if you need to escalate the issue. available at http://motorola.

rapid refresh of the Link Status table on the AP’s Tools => Link Status page could potentially cause performance issues on the sector. Product Family PMP 100 PTP 100 PTP 49200 PMP 49400 Enhancement None Support for PTP 49200 Change to existing feature: per-SM query replaces Link Status table Summary — With Release 9.3 Release Notes Release 9.9-GHz OFDM radios are now offered as BHs. but not display a table. On sectors with large numbers of SMs. 4.Release 9.4. To avoid this.1 RELEASE 9.4.0 Release Notes Release 9.4.4. the table has been replaced with the ability to query each SM for all bidirectional link data.2 enhancements Release 9. 5.4-GHz OFDM radios now support the general features and enhancements listed in ◦ ◦ ◦ Release 9. Table 3: Packet per Second (pps) performance Hardware series Product P11 or P10 PMP 5x100 and PMP 24100 PMP 5x100 and PMP 24100 with VLAN PMP 09100 (900 MHz) PTP 5x100 and PTP 24100 PMP 54400 PTP 54200 PMP 49400 PMP 49400 with VLAN 6200 5200 4600 6200 6800 4800 6300 5300 P9 3500 3200 3600 3200 — — — — 1 Issue 1.4.2.2 PERFORMANCE – PACKETS PER SECOND Packet per Second (PPS) performance for Release 9.2 adds the enhancements listed in Table 2.2 is the same as for recent releases.2 Release Notes 2 Features and Enhancements The following sections list features and enhancements for Release 9. May 2009 Page 10 . as well as APs and SMs. 2. Benchmark values are shown in Table 3. 2.2 ENHANCEMENTS Table 2: Release 9.4.4.4 Release Notes PMP 54400 PTP 54200 Support for features and enhancements since previous release Please refer to those release notes for details.2.

2 before being deployed. May 2009 Page 11 .4. on page 31 describes the benchmarking process used to measure packets per second and discusses the meaning and limitations of the benchmark.0. it can be run in a sector with an AP and other SMs running Release 9.3 SUPPORT FOR P11 HARDWARE 5. at a minimum. Release 9. Release 9.1 Mixing Hardware Vintages P11 APs and SMs can be mixed with other hardware vintages in a sector.2-GHz and 5.0.1 installed.3 and will initially ship with Release 9.2. if you purchase an SM and it is P11 hardware running Release 9.4 or Release 9.4.4.4 and will initially ship with Release 9.3. at a minimum. in a sector is supported.0 and 9. 2. it can be run with a sector of SMs running Release 9. or Releases 9. Before deploying P11 hardware into a sector.0. Issue 1.Release 9. These modules should be upgraded to Release 9. P11 modules exhibit performance similar to P10. Or.3 installed. mixing Releases 9.2 Mixing Software Releases To smooth the transition to P11 hardware. if you purchase an AP and it is P11 hardware running Release 9. as shown in Table 3 on page 10.3.4-GHz P11 modules require.4.2 Release Notes Hardware series Product P11 or P10 Note: No significant difference between DES and AES 1: Links with a P9 module on one end and a P10 or P11 module on the other perform between 3200 and 3500 pps P9 Section 9.2 from the factory. 5. 2. 2.0 and 9. existing APs and SMs in the sector should first be upgraded to at least Release 9.4. Performance Benchmarking Process.3 from the factory. P11 BHs can be mixed with P9 and P10 BHs on a link.7-GHz P11 modules require.3. For example.

PMP 100 Issue 1. Using a TFTP server can significantly speed up upgrades because ◦ Each sector can have 20 SMs under upgrade at a time (network performance permitting) instead of the 4 SMs maximum when files are served from the AP. All TFTP server option available for upgrades (9958.4.4. The TFTP server doesn’t use a 20-minute inactivity timer between servicing different hardware series (P7/8/9.4. and Release 9.2 resolves this display issue for P9 900MHz radios and retains the improvements in P10 900-MHz Received Power reporting accuracy.4 improvement in P10 FSK 900-MHz radios’ displayed Received Power caused an issue with displayed Received Power on P9 FSK 900-MHz radios in some cases.4.4. on a link with some re-regs. and P11) as it can serve any hardware series SM on demand. For additional information on using the TFTP server option see the CNUT Help user guide.4 doesn’t allow changing of the Config Source or VLAN Allow Frame types using the GUI.2 Product Family All Description PPPoE-configured SM stuck in “LCP (Link Control Protocol) Negotiating” Explanation Before. A new stage of PPPoE session status called Connecting was added.4 partially resolved this issue.2 Release Notes 3 Resolved Issues Issues resolved in Release 9. Table 4: Issues resolved in Release 9. Release 9.4. but the LCP and IPCP stages never completed.Release 9. Release 9. the SM might get stuck in “LCP Negotiating” mode if a PPPoE session was started. P10. unable to change Config Source and VLAN Allow Frame types (10357) P9 FSK 900-MHz radios may show erratic Received Power (10380) On P9 FSK APs. 10352) The TFTP server option for distributing files to SMs during upgrading now works. The underlying performance of the radio was not affected. This is resolved in Release 9.2 fully resolves it. Release 9. To use a TFTP server for upgrading SMs ◦ ◦ ◦ The TFTP server must be located on the same machine as the CNUT or Prizm software.2 A Release 9. PMP 100 On P9 FSK APs. Now if there is a problem setting up the PADI/PADO part of the PPPoE session Connecting will be reported rather than LCP Negotiating. Connect/disconnect buttons wouldn’t have resolved the issue. The SMs must be configured with Public Network Accessibility (not Local) and have assigned IP addresses.2 are listed in Table 4. May 2009 Page 12 .

3 (the previous 5. set the Broadcast Repeat Count to 0 or 1 on an AP handling broadcast video and to the default of 2 on other APs.0 Release Notes ◦ Release 9. With Release 9. It is resolved for OFDM in Release 9. Release 9.3.4.9-GHz radios.4.2 resolves general issues listed in the following Release Notes: ◦ Release 9.4-GHz radios.4.1 (the previous 4.4 Release Notes Please refer to those release notes for details. PMP 54400 PTP 54200 Same default for both read/write and read-only community strings for 5. Issue 1.4.4. For OFDM (PMP 400) systems. these radios now default to “canopy” for the read/write community string and “canopyro” for the read-only community string. Use either 1 or 2 repeats.4GHz OFDM radios (10264) 5.4.4 Release Notes Please refer to those release notes for details.4-GHz OFDM release) PMP 49400 PTP 49200 Resolves general issues since Release 9. the Broadcast Repeat Count on the AP’s Configuration => Radio page should not be set to 0.2. Release 9. the same as other radios.9-GHz OFDM release) For 4.Release 9.2 resolves general issues listed in ◦ Release 9. For FSK (PMP 100) systems. For 5.3 used “canopy” as the default for both the read/write and read-only community strings.2 Release Notes Product Family PMP 54400 PMP 49400 Description Downlink broadcast traffic can exhibit packet loss (9492) Explanation This issue affected all systems (OFDM/PMP 400 and FSK/PMP 100). to reduce the potential for packet loss. but can still affect FSK systems. May 2009 Page 13 .2. PMP 54400 PTP 54200 Resolves general issues since Release 8.4-GHz OFDM modules running Release 8.4.3 Release Notes ◦ Release 9.

Broadcast Repeat Count on the AP’s Configuration => Radio page should not be set to 0. (The Scheduler page appears on every module type . This issue has been resolved for OFDM radios. Workaround: When using applications such as broadcast video that make significant use of downlink broadcast packets. the Translation Table is associated with Translation Bridging and only displays data when Translation Bridging is enabled at the AP. If you have configured an NTP server IP Address on the AP’s Configuration => Time page. Otherwise. All Anomalous Event Log messages associated with NTP server (10402) Starting with Release 9. leave the parameter set to the default of 2. All ARP table shows 00-00-00-00-00-00 for the NAT WAN interface (9711) No SNMP support for Translation Table (10053) The SM’s Statistics => ARP page shows a physical address of 00-00-00-00-00-00 in the NAT WAN ARP Table in error. All All No SNMP support for counters on Scheduler page (10595) Prizm 3. SM. (9764) Downlink broadcast traffic on FSK radios can exhibit packet loss (9492) All PMP 100 Issue 1.2 Release Notes 4 Known Open Issues Known open issues for Release 9.1 cannot change LED Panel Mode. check the SM’s Home => General Status page. in most cases.1 cannot set the LED Panel Mode to Revised Mode.4. but the AP does not show the SM in a PPPoE session on the AP’s Home => Session Status page. The correct physical address for the IP address is shown in the Public RF NAT Table further down on the page.2. LEDs are in Legacy Mode by default. you may get “zero delay no update necessary” messages in the Event Log. The message can mean either the NTP server did not respond (in which case the message wording should be different). set the parameter to 1.2 are listed in Table 5. Table 5: Known open issues Product Family All Description PPPoE In Session message not syncing to AP (10385) Discussion and Recommendations Under some conditions. (For background.4. OIDs do not exist for the data on the SM’s Statistics => Translation Table page and therefore the data is not retrievable using SNMP.) Prizm 3. Workaround: Ignore the “zero delay no update necessary” message and continue to use previous methods for debugging NTP server issues.4. Currently there is no way to tell from the message which case is indicated. or the NTP server did respond but there was no time difference from the previous NTP message and no display update was needed (in which case it is an extraneous error message that can be ignored). Workaround: If in doubt about the status of a PPPoE session to an SM. Workaround: Set LED Panel Mode using the GUI.) OIDs do not exist for the data on the Statistics => Scheduler page and therefore the data is not retrievable using SNMP. Use either 1 or 2 repeats. but can still affect FSK radios running Release 9. and BH. some Event Log messages were added to aid debug of NTP server issues. May 2009 Page 14 .Release 9.4.AP. occasionally an SM establishes a PPPoE session successfully and correctly displays PPPoE In Session on the SM’s Home => General Status page.

Issue 1. Sectors configured for a Max Range of 10 miles or less are not affected by this limitation.2 Release Notes Product Family PMP 49400 PMP 54400 Description Ranging issues at maximum settings (9798) Discussion and Recommendations Workaround: Due to occasional ranging issues at higher settings. May 2009 Page 15 . a sector configured for a Max Range of 11 miles or greater should have its Downlink Data set no higher than 80%. Max Range and Data Downlink are set on the AP's Configuration => Radio page.4.Release 9.

prioritizing TCP ACKs can cause sporadic choppy video in the uplink.4. May 2009 Page 16 .4. on the AP’s Configuration => General page configure Prioritized TCP ACK to Disabled.Release 9. this may or may not affect a given installation. Guard times in the OFDM PTP scheduler were increased slightly. at 3 miles the slots are 32/32 for both Release 8. For example. When optimizing a system for broadcast video. Depending on the distance between BHs and the configured Downlink Data %. Different hardware vintages use different methods for deriving temperature.4.4.1 NOTES Table 6 lists notes new for this release.2 resulting in no change in throughput between the releases. Table 7 lists continuing notes first mentioned in previous Release Notes. at 0 miles and 50% Downlink Data the uplink/downlink slots change from 33/33 in Release 8.4. However. whereas older hardware vintages may see significant differences between radios and from the same radio over time.2 Product Family All Description A derived temperature is now shown on a module’s web page (10379) Disable TCP ACK prioritizing in broadcast video applications (10263) Discussion and Recommendations The temperature is board (not ambient air) temperature. Newer hardware vintages will see a temperature indication that tracks more closely with temperature changes and is more consistent from radio to radio. Table 6: New Notes for Release 9. All PTP 54200 5.4-GHz OFDM BHs may see a 600 kbps reduction in uplink or downlink throughput (9574) Issue 1. resulting in 600 Mbps less downlink throughput.3 and Release 9. In a system being used for internet access or similar applications prioritizing TCP ACKs improves downloading of FTP files and other activities making significant use of TCP ACKs under heavy load. in a system being used for broadcast video or video surveillance. changing the ranges at which time slots are lost to air delay.2 Release Notes 5 Notes and Reference 5.2.4. However.3 to 33/32 with Release 9.

1.1. go ahead and reboot.3.xml button is clicked on the SM’s Tools => Spectrum Analyzer page or the AP’s Tools => Remote Spectrum Analyzer page. Issue 1.19.4.3. downgrade the module and then upgrade it again.3. The actual performance of the radio has not changed.4.4.6. right click and select “Save Target As” on a Windows PC. such as rebooting every time you try to access the GUI.35 Syntax: INTEGER Access: read-only Status: current Radio temperature in Celsius. The displayed Received Power may be lower or higher than for the same radio running a previous release.Release 9. If CNUT reports the module as upgraded and refuses to upgrade again.4. Recovery: Attempt to upgrade again. More accurate Received Power readings for P10 900-MHz radios For P10 900-MHz radios.6. boxTemperatureF Object ID: 1. May 2009 Page 17 . To save the underlying XML file.3.3.5) OID (which returned an octet string value) is no longer valid. P10 900-MHz radios should see less variation of displayed Received Power over time (as temperature changes) and from radio to radio.36 Syntax: INTEGER Access: read-only Status: current Radio temperature in Fahrenheit.161.3. When the SpectrumAnalysis.19.1. If you make frequency changes on the SM GUI. Release 9.6.1.19.4 included improvements in the accuracy of the displayed Received Power based on improvements in temperature measurement.4 the boxTemperature (1. 8484 Procedures for saving an XML file of a spectrum graph 8172 SM scan frequencies not “cancelled” by SNMP actions 8241 Avoid power cycling modules during upgrading Power cycling a module while it is upgrading can cause anomalous events. With this accuracy improvement. or equivalent action for other operating systems. just to clear the message.1.161. and then back them out using SNMP. Workaround: If it says Reboot Required. the spectrum graph is redisplayed using XML and XSL if the browser supports XSL. Two new OIDS which return integer values are added: boxTemperatureC Object ID: 1.161.2 Release Notes Table 7: Previous Notes ID Description Changes to boxTemperature OIDs Discussion and Recommendations Starting with Release 9.1.1.1.1.3. the Reboot Required message remains on the GUI.3.3.

It is generally advisable to ping such a system. You can set Community Strings that include characters like ~`!@#$%^&.Release 9. so more than 16 characters may be entered. However. since Canopy handles that ping with the same priority as is given all other transport traffic. the Tools => AP Evaluation tab maintains AP entries for 15 minutes. A module that either is fresh from the factory or has been operator-reset to factory defaults has two user accounts: root and admin. access the Account => Change Users Password tab and add a password to each of these accounts. Alternatively. A ping size larger than 1494 Bytes to a Canopy module times out and fails. To help during aiming. To secure a module.*()_+[]{}|.:. passwords. and Community Strings Timed Spectrum Analyzer settings anomaly SNMP doesn’t do data-entry checking. The results are unaffected by ping size and by the load on the Canopy module that brokers this traffic. However. for 15 minutes the AP is listed twice in the AP Evaluation tab.. a ping of this size or larger to a system that is behind a Canopy module typically succeeds. the best practice is still for you to set a Region Code in the SM so that displayed options are consistent with the region. If you set this parameter to lower than the range capable on a radio. disregarding any Region code set in the SM by you. 7442 None Best Practice is to set SM to same Region Code as AP Details on pinging Canopy modules 4831 5298 AP may be listed twice in AP Evaluation tab Lowest settable Transmitter Output Power varies 4789 Issue 1. an operator’s practices may be to delete the admin account or delete the root account and replace them with their own account(s). When an SM registers to an AP. NOTE: The high end of the range of settable Transmitter Output Power does not vary from radio to radio.4. an account without a password will accept any password potentially giving the impression the unit is protected when it isn’t. and set passwords for all accounts. If the frequency of an AP is changed. By default Prism and CNUT use the root account to manage the module. it assumes the Region Code and associated parameters of the AP. Values of Timed Spectrum Analyzer duration and Spectrum Analysis on Boot get saved by clicking any button on the page. Adding a password to only one account still leaves the other open.2 Release Notes ID None Description Managing module accounts and passwords Discussion and Recommendations The best security practice is to be aware the unit starts with root and admin accounts. both with ADMINISTRATOR level permissions. but SNMP only accepts alphanumeric characters and SNMP get or set commands will return errors./<>? from the GUI. 7808 Use up to 16 alphanumeric characters in user account names. Furthermore. but only 16 characters will be saved and displayed. to plan your approach to accounts. and once with the new. May 2009 Page 18 . so if you delete root accounts on modules you will need to make coordinated changes to Prizm and CNUT to access them with your own accounts. The low end of the Transmitter Output Power can vary from radio to radio due to manufacturing tolerances. not just when clicking Save Changes or Start Time Spectrum Analysis (which is typical operation for other pages). the value is automatically reset to the lowest capable. once with the former frequency.

Use half duplex settings when using a hub. After you run perform a link test with MIR capping enabled. Canada. especially in frequency bands that have a large number of center channels. the US. Table 8 shows operation based on Region Code. due to the way a hub works. not allowed in Europe. weather radar in several Regions. to be in regulatory compliance. and Australia. Canada or Australia notches out these frequencies and ensures compliance. May 2009 Page 19 . Canada. to disable refresh. need to set both ends Discussion and Recommendations To see the effects of MIR capping. the display includes the entire spectrum bar graph.2.Release 9. You can later reset the Webpage Auto Update time back to 0. and Australia 5407 7557 When connecting to a hub. If you observe this. Setting the Region Code to Europe. Issue 1. 2756 Description When using Link Test with MIR. consider immediately changing Link Test with MIR to Disabled in both the SM and the AP. In some instances. To get meaningful results. such as the 5. refresh your browser window. to have the Spectrum Analyzer automatically fully displayed and refreshed. operators must not transmit on these frequencies. For reference. the interface presents a blank screen to a user who logs in to an SM through the Home => Session Status tab in the AP. Canada.4-GHz band.2 Release Notes ID 4844. set Link Test with MIR to Enabled on the Tools => Link Capacity Test tab in both the SM and the AP. depending on network activity and network design. Canopy center channel frequencies of 5590 MHz through 5660 MHz may interfere with. results are misleading. the resulting display may omit bars for some frequencies. When it is enabled on only one end. set the Webpage Auto Update parameter to a few seconds. including Europe.4. by frequency band and module type. If you clicking Enable again. In Europe. 4706 Blank screen after logging in to SM through AP Session Status tab 5590 through 5660 may interfere with weather radar. use only half duplex Ethernet settings 5. to avoid mistakenly capping only one end of the link test.2 OPERATION BASED ON REGION CODE AND FREQUENCY BAND There are no changes to Region Code operation in Release 9.4. Ethernet connections set to 10 Base T Full Duplex or 100 Base T Full Duplex will not connect to an SM through a hub. or be interfered by. TIP: In the Configuration => General tab. Operators who perform a site survey in the United States should use the built-in Spectrum Analyzer or a stand-alone spectrum analyzer to check for activity on these channels and select other channels as appropriate. and Australia. 5284 Click Spectrum Analyzer Enable button twice After you click the Enable button in the Tools => Spectrum Analyzer tab. you can run a link test with MIR enabled.

3. 08: 5590-5660 MHz not 2. 2008.4. No effect No effect No effect No effect No effect In all cases.7 GHz AP/ BHM SM/ BHS United States No effect No effect No effect NA No effect FCC/IC DFS No effect No effect No effect Canada No effect No effect No effect NA No effect FCC/IC DFS 5590-5660 MHz not 2 available P11: ETSI 1.4 GHz module is “newer” or “older” by setting the Region Code to Europe – if the notch frequencies are not shown on the Configuration => Radio page.3. 3.1 DFS >July 1. To meet this requirement.1 DFS ≤ P10: ETSI 1.4. In some countries a “weather notch” is required to avoid impinging on these frequencies.Release 9. You can tell if a 5. set the Region Code to the region you are in.1 DFS Brazil NA NA No effect NA NA NA No effect Australia No effect No effect No effect NA NA NA 5590-5660 MHz not 2 available No effect No effect No effect Russia NA NA No effect No effect Display Community options No effect No effect No effect No effect No effect NA NA No effect No effect No effect Other 1. May 2009 Page 20 .4 available No effect Europe NA No effect No effect NA NA NA ≤ P10: ETSI 1.4 GHz SM/ BHS 5.4.3.4.1 DFS >July 1.4. then the module is “newer”.1 DFS No effect No effect No effect P11: ETSI 1. if the notch frequencies are shown.1 DFS No effect P11: ETSI 1. 08: 5590-5660 MHz not 2. the software checks the date code of the module and implements the weather notch accordingly.4 available P11: ETSI 1.3.1 DFS ≤ P10: ETSI 1. the module is “older”.1 GHz AP/SM/ BH 5. Radios placed on market in Europe after July 1. and the software will determine the correct use of DFS.4.4 GHz AP/SM /BH 4. Weather radar operates on frequencies from 5600 through 5650 MHz. 2. can’t impinge on weather radar frequencies.2 Release Notes Table 8: Release 9.2 GHz AP/ BHM ≥P10: FCC/IC DFS ≤ P9: no DFS ≥ P10: FCC/IC DFS ≤ P9: no DFS SM/ BHS AP/ BHM 5.4.1 DFS ≤ P10: ETSI 1. Issue 1.9 GHz AP/SM /BH 5.3.1 DFS ≤ P10: ETSI 1.1 DFS FCC/IC DFS P11: ETSI 1.2 operation based on Region Code and frequency band Region 1 Code 900 MHz AP/SM 2.

Information on the Motorola Prizm element management system is available at http://motorola. Issue 1. May 2009 Page 21 .com/software/. Loading in the recommended order avoids any problems arising from loading sequence. Then load the Canopy MIB files.motowi4solutions. Some NMSs are not sensitive to order. If you are using an SNMP network management system (NMS) or element management system (EMS) other than Prizm: Load the MIBs per the instructions for your NMS or EMS. monitoring.com/software/.motowi4solutions.Release 9. Prizm documentation and installers are available for download from the Canopy tab of http://motorola. such as the Motorola Prizm system. You do not need to load MIB files. First load the standard MIB files. The MIB files are available for download from the Canopy tab of http://motorola. consisting of 5 MIB definition files. but some require a specific loading order to build a MIB tree. MIB files are used by Network Management Systems and Element Management Systems. 2. If you are using Prizm: Prizm software includes the MIB information.motowi4solutions.com/products/prizm/. Detailed information on the Canopy MIBs is available at http://motorola. control. and operational tasks. to support a host of surveillance.motowi4solutions. supports SNMP access to Canopy modules.2 Release Notes 6 Canopy MIB The Canopy Enterprise MIB (Management Information Base). Important! When loading the Canopy MIB files 1.4.com/support/online_tools/.

Release 9. P8 No No No P9. AP BH Yes Yes Yes Yes PTP 54200 (5.4-GHz OFDM) All vintages Yes Yes Yes Yes SM.4.4. P11 Yes Yes Yes P7. and radio types that are upgradeable to Release 9.4. Issue 1.2 Release Notes 7 Upgrading to Release 9.1 7.9-GHz OFDM) PTP 49200 (4.2.4-GHz OFDM) PMP 49400 (4. hardware series.2 7.4. Table 9: Radios Upgradeable to Release 9. P10.9-GHz OFDM) Release 9. May 2009 Page 22 . P8 PMP 100 (Canopy FSK) AES Product P9.5 GHz OFDM APs and SMs) PTP 300 Series Bridges PTP 400 Series Bridges (formerly 30-/60-Mbps backhaul modules) PTP 500 Series Bridges PTP 600 Series Bridges (formerly 150-/300-Mbps backhaul modules) CMMs (Cluster Management Modules) Powerline MU Gateway and Modem 7. P11 Yes Yes Yes SM AP BH Yes No No PTP 100 (Canopy FSK) All vintages PMP 54400 (5.1 BEFORE YOU UPGRADE Applicability Table 9 shows the product series.1.4. AP BH SM. P10.2 Product Family Radio Type Product Encryption Type DES Product Hardware Vintage P7.2 is not applicable to        PMP 500 Series modules (Canopy 3.1.2 Supported Upgrade Path Upgrade paths for operating sectors are shown in Figure 3.

Prizm 3.2 Figure 3: Upgrade path for operating sectors Each release has new feature content and may have changes to message structures and protocols used between the AP and the SMs. or in the worst case SMs being stranded by the use of untested combinations. so sectors that run software scheduling must first be switched to hardware scheduling using CNUT.0 9.com/software/.1. CNUT CNUT (Canopy Network Updater Tool) is a free tool for upgrading Canopy modules.4. May 2009 Page 23 . Standalone modules such as spares can be upgraded from any Release 8.2.motowi4solutions. and should be used for upgrading modules to Release 9.4.Release 9. especially the Release 7.1 9. then use Prizm to upgrade their Canopy modules to Release 9.4.2.pkg3 file and CNUT 3.3.1 or later does not include the Hardware Scheduler Update tool.12 or Prizm 3.4. Following the tested upgrade path is strongly recommended for operating sectors.2. For details on upgrading modules running software scheduling see previous release notes.3. especially the release notes for Canopy Release 7.1 with Patch 7 supports upgrading modules to Release 9.4. Operators running Prizm releases earlier than Release 3.2 Release Notes PMP 100 PTP 100 (FSK) 8.4-GHz OFDM) PMP 49400 PTP 49200 (4.4 9. For details on switching to hardware scheduling. These changes may affect operation of APs and SMs operating on untested mixed releases during the upgrade period.4. 7.12 release notes for additional details. resulting in features or indicators not working properly. CNUT 3.1 or later to manage upgrades.3.2 9.1 for all upgrades 8.2.4.2. For information and details on installing CNUT on a PC or Linux machine.3 9. If you need to upgrade from a previous CNUT release.4.3 Upgrade Tool Options Use either CNUT or Prizm for the upgrade.9-GHz OFDM) Use a .2. Issue 1.3 9.4. see previous release notes.12 supports upgrades of P11 modules. ensure you back up your network file before upgrading CNUT. download the CNUT software and help file from the Canopy tab of http://motorola. including 2 Mbps and 4 Mbps BHs. Prizm Motorola offers Prizm as an EMS that provides monitoring and management functions.4 9. See the CNUT 3.6 Release Notes. Prizm 3.1 9.2 PMP 54400 PTP 54200 (5. including module upgrade.7 8.1 should upgrade to the current Prizm release.6.x (or any hardware scheduling release) to Release 9. before using Prizm 3.4.

motowi4solutions.pkg or .12 for Windows or Network Updater Tool Release 3.2.12 on Windows or Linux using the CNUT release notes. but since these channels are not available on equipment placed on market in Europe from July 1. If you are connecting at your POP.1.2 OBTAINING AND PREPARING CNUT OR PRIZM Use either CNUT Release 3. 7. . it relies on the connectivity information you enter in the network tree. and CMMs) to the network root and Move and Modify the elements until you have captured your network. 2008.com/products/prizm/. it should reflect connectivity from that point.Release 9. adding SMs or replacing SMs or APs becomes problematic. this will be the same as your network hierarchy.12 or later or Prizm Release 3. Install CNUT Release 3. download    Network Updater Tool Release 3.2 Release Notes Information on the Motorola Prizm element management system is available at http://motorola.12 and Prizm Release 3.pkg3 packages and the tools that use them is that they support upgrading modules using module accounts other than root and therefore do not require a module to have an account named root. A key aspect of .pkg2 files) cannot be used with CNUT Release 3. Operators with modules set to a Region Code of Europe may need to perform channel planning and coordinated change of the transmitting channel on APs and BHMs before the upgrade.com/software/. 7.com/software/. 3.motowi4solutions. Earlier packages (.motowi4solutions. This should be the connectivity as viewed at the point from where you connect to the network to perform the upgrade.12 for Linux Network Updater Tool Release 3.4. IMPORTANT! Pay particular attention to the connectivity that you establish in the network tree.pkg3 Packages Upgrades use package files whose name extensions are . Obtaining and Preparing CNUT From the Canopy tab of http://motorola.4 GHz Radios Operators with modules set to a Region Code of Europe are well-served to ensure they are not using any channels with center frequencies of 5590 to 5660 MHz inclusive (in the weather notch) before upgrading. A sector currently using 5590 to 5660 MHz inclusive will complete the upgrade successfully and existing SMs will register and function. add your Canopy infrastructure elements (APs. When CNUT discovers the network and when it steps through the infrastructure elements during an upgrade. Issue 1.pkg3. BHs. 7.1 with Patch 7 or later for the upgrade.4 Special Planning for European Operators using 5.1 1. If you are connecting at some point other than your POP. If you do not have a previously stored network archive file within CNUT. Prizm documentation and installers are available for download from the Canopy tab of http://motorola.12 Release Notes 2.1. May 2009 Page 24 .

If you do not have a previously stored network archive file within Prizm. perform the following steps: PMP 100 and PTP 100 series (Canopy FSK radios) use the FSK software. Enter the password(s) for the root login accounts of all modules you are upgrading into CNUT or Prizm. 4.4.motowi4solutions.pkg3 package or packages will download to your computer. 2. 3. May 2009 Page 25 . see the CNUT help file or click on the Help menu in the CNUT application. 2.1 Patch 7 and Prizm 3. Click Accept User Agreement and Request Download Links.1 Patch 7 Release Notes. For additional details on using Prizm. RESULT: You will receive an email with a link or links to the software. On the software download page. The CNUT help file and Prizm user guide are available for download from the Canopy tab of http://motorola. download    Prizm 3.2. From the Canopy tab of http://motorola. Refresh/Discover Entire Network to auto-detect all of your SMs and to display information about your network elements. 5.4. If taking advantage of the ability to use accounts other than root.9 OFDM.motowi4solutions. If upgrading PMP 49400 or using PTP 49200 modules.9 OFDM.4. 5. 1. 7.1 Patch 4. Issue 1.2 Release Notes 7. add your Canopy infrastructure elements (APs.1 Patch 7 Prizm 3.2 FSK Software . enter the accounts and passwords.9 OFDM. see the Prizm user guide. also download Prizm 3.4 GHz and 4. PMP 400 and PTP 200 series (Canopy OFDM radios.com/software/. Options include     Release 9. If upgrading PMP 49400 or using PTP 49200 modules. OBTAINING UPGRADE PACKAGES Go to http://www. In the email sent to you. also download Prizm 3.DES Release 9.com/software/. Obtaining and Preparing Prizm Download Prizm 3.com/software/. 4.4.4 PERFORMING THE UPGRADE VIA CNUT OR PRIZM Upgrade using the following steps. Install Patch 7 using the Patch 7 Release Notes. select the appropriate package or packages. 7. and CMMs) to the network root and Move and Modify the elements until you have captured your network.1 Patch 7 Release Notes.2 OFDM Software . For additional details on using CNUT.AES Release 9. install Patch 4.3 1.Release 9.AES To download the Canopy software to your computer. RESULT: The appropriate.9 GHz) use the OFDM software.2 FSK Software . If upgrading PMP 49400 or using PTP 49200 modules. click on the desired link or links. both 5.2 OFDM Software .DES Release 9. 2.motowi4solutions.1 Patch 4.2 1. Follow the directions on that page to access the software download page.4. BHs. 3.

or the entire network. Use Prizm or CNUT to confirm use of SM Auto-update. updates all registered or registering P11 SMs that require an upgrade.2. For example.4.1 with Patch 7. or did reboot but CNUT or Prizm displayed a message such as “Reboot failed” or “Failed to find Element in update.Release 9.2. Consider rebooting APs on sectors you plan to update to eliminate any memory fragmentation issues and ensure there is space to hold the new image. Choose the elements that you want to update at this time: a selection of elements.3. perform the following steps: Issue 1. Cannot open new telnet connection to device”. c. There will be quiet times during a sector upgrade due to the 20-minute inactivity timer. 10. which significantly reduces the time needed for updating an entire network.pkg3 files:     CANOPY94_2BUILDOFFICIAL_DES. 7. without operator action. f. 6. g. Monitor the update progress through the Network Tree. waits for 20 minutes of no upgrade or new P7/8/9 registration activity. Refresh/Discover. Initiate the Update operation. 9.4. and if the rest of the sector successfully upgraded and became stable on Release 9. leaving CNUT/Prizm active. Verify that the Software Version for each module is shown as CANOPY 9. any SMs that are not properly upgraded are found by CNUT or Prizm on a subsequent cycle and then successfully upgraded. 12. a network branch. Obtaining Upgrade Packages. May 2009 Page 26 . depending on network size and their own procedures. followed by active updating of SMs. b. SMs are updated by their AP instead of by CNUT. Depending on the package downloaded in section 7. With CNUT 3.4. sectors with no P7/8/9 SMs should be set to upgrade P10 SMs first and not upgrade P7/P8/P9 SMs to avoid a 20 minute wait until upgrade of P10 SMs begins. updates all registered or registering P10 SMs that require an upgrade. updates all registered or registering P7/8/9 SMs that require an upgrade. the operator can choose the update order among P7/P8/P9 SMs. Add the appropriate . 11.pkg3 CANOPY94_2BUILDOFFICIAL_OFDM_AES. until all involved SMs are upgraded. In addition.pkg3 4. e. you will have one or more of the following . and P11 SMs by setting the SM Autoupdate Configuration. Most operators gain experience by upgrading a portion of their network at a time. P10 SMs. After the upgrade appears to have completed. 13. continues this cycle until Auto-update is disabled (using CNUT or Prizm) or until the AP is rebooted.pkg3 CANOPY94_2BUILDOFFICIAL_AES. Just before doing any updates. d. waits for 20 minutes of no upgrade or new P10 registration activity. use Refresh/Discover to confirm that all SMs are active. An AP enabled for Auto-update a. as these SMs are not addressable by CNUT or Prizm over the network. SM Auto-update must be used to update any SMs that have their Network Accessibility parameter set to Local. waits for 20 minutes of no upgrade or new P11 registration activity.pkg3 CANOPY94_2BUILDOFFICIAL_OFDM_DES. 8. as appropriate. If any SM completed the software loading and then failed to reboot. 5. Allow the update to run. With this algorithm.pkg3 file(s) to the managed packages list. With SM Autoupdate.2 Release Notes 3.12 or Prizm 3.

re-initiate the upgrade of the SM using CNUT or Prizm. May 2009 Page 27 . reboot the problem SM. and Reboot.4.1 Setting the Region Code After a sector or link or standalone module has been upgraded to Release 9. 14. If it does not. 7.4. Check whether the resulting elements list shows the SM as operating on the new release. If needed. Issue 1. set the Region Code and associated parameters correctly on each module. If it is not. c.2. Disable SM Auto-update on CNUT or Prizm.4.2.4. or APs or BHMs that have been reset to factory defaults. d. Save Changes. e. On new APs or BHMs. Refresh/Discover. b. according to CNUT help file or Prizm documentation. Check whether the SM is shown as operating on Release 9. the Region Code must be set before the module will transmit.2 Release Notes a. confirm that the Region Code on each module is set to the local region.Release 9.

Release 9.2-GHz systems.2-GHz AND 5. care needs to be taken in choosing 5.2-GHz radios. 5320 5305. 5310. 5280 5275. 5285. 5315. This signal is present at all times (both during transmit and receive). 5300. Alternatively. 5280. during transmit and receive.4 GHz systems are collocated with 5. 5280.2-GHz radios. 5285 5275. 5295.4-GHz MODULES 5.4-GHz center channel (in MHz)… 5545 5550 5555 5560 5565 5570 5575 5580 5585 5590 5595 may interfere with these 5. 5290.4. 5295. 5290.4. Issue 1.2-GHz and the 5. 5295. Table 10: 5. Choosing 5.2 Release Notes 8 Collocation 8. but do not help this collocation issue. Using sync and ensuring compatible receive start times are necessary to avoid other collocation issues. 5285. it is strong enough to interfere with a closely collocated Canopy radio in another band. 5310. 5325 Background What causes this collocation issue? As part of their radio operation. 5280.1 COLLOCATING 5. or in cases of partial clusters of 5. this signal is above the band for some center channel frequencies and below the band for other center channel frequencies. Because of this. 5315 5300. 5300 5285. 5305. 5315. 5290. If a CMM provides sync and ensures compatible receive start times (as advised in Collocating Same-Frequency Band Modules on Page 29).and 5. 5310 5295.and 5. 5310. 5305 5290. if that radio is using a channel impinged upon by the out of band signal.2-GHz channels as shown In Table 10. This signal can interfere with 5. 5300. 5285.2-GHz interfering frequencies This 5. 5320. 5290 5275. 5305.4-GHz radios.4-GHz channels where 5. Canopy radios produce a low level signal outside of their frequency band. because the interfering signal is present at all times. May 2009 Page 28 .4-GHz radios that are set to a center channel frequency of 5595 MHz or lower produce a signal that is 280 MHz below their center channel.4-GHz channels of 5495 through 5540 MHz or 5600 through 5705 MHz avoids this collocation issue and is often the best option.2-GHz channels (in MHz) 5275 5275. and is well within regulatory requirements for out-of-band emissions. aren’t collocation issues avoided? No. 5305. However.4. 5300. By design. provide 100 ft (30 m) of vertical separation between the 5. 5295 5280. select 5. as can happen between 5.4-GHz channels that will not interfere.

and choose frequencies far apart within the combined 5. and use of reflectors on BHs. if 100 ft (30 m) of vertical separation is not possible. the 5. May 2009 Page 29 .4-GHz and 5. ensure the over-illumination around the edges of the reflector is not directed at the APs. 4.4-GHz and 5. When collocating 5. influenced by tower geometries. choose channels for the AP that are at the bottom of the 5.4-GHz and 5. 8. If this is not possible 1. albeit one with possibilities for large spectral separation of channels.4-GHz APs with a 5.Release 9.4. Alternatively. For example. and use standard frequency re-use around each cluster (ABCABC). among other variables. 3. provide 100 vertical feet of separation. either   provide 100 ft (30 m) of vertical separation between the 5. The physical and spectral separation and local RF conditions. If you collocate radios of the same frequency band.7-GHz APs.2 COLLOCATING 5. provide as much vertical separation as possible.7-GHz Canopy modules have different radio front ends. confirm with simultaneous link tests. set them all to the same range. use the guidelines for collocating modules within a band listed under Collocating Same-Frequency Band Modules on Page 29.7-GHz modules. only BHMs. or only BHSs).4-GHz and 5.7GHz radios.7-GHz bands. and control slots. downlink data %.2 Release Notes 8.7-GHz frequency bands are essentially one continuous band.7-GHz) are considered separate? 5. Use a CMM. so that transmit start times are in sync.3 COLLOCATING SAME-FREQUENCY BAND MODULES Canopy can avoid self-interference if collocated modules in the same frequency band are of the same type.4-GHz APs with a cluster of six 5. locate the modules so the reflector on the BH shields the APs from the BH module. when collocating a cluster of six 5.4-GHz and 5.4-GHz and 5.2-GHz and 5. For another example. but testing and monitoring will be required to confirm that they do. Use identical scheduler type (hardware or software) Either Issue 1.4-GHz AND 5. collocate only one type of module (only APs.2-GHz and 5. and start each frame reception at the same time. 5. start each frame transmission at the same time. whereas 5.7-GHz bands are essentially one continuous band.4-GHz band. For collocation design.7-GHz radios use the same radio front end.7-GHz bands considered one band for Canopy collocation. whereas other bands (say 5. choose a channel for the BH that is at the top of the 5. Background Why are 5.7-GHz band.7-GHz BH that is retrofitted with a reflector.4-GHz and 5. may support good performance. layout and position of modules. when collocating a cluster of six 5.7-GHz MODULES For collocation design. do the following also:     Within the same band. the 5. all hardware scheduled. 2.

Release 9.com/support/library/ under User Guides.3. alternatively provide as much vertical separation as possible.2 Release Notes − − Set identical range.1 Using the Frame Calculator Parameters that affect receive start times include range.4. This calculation should be done for each AP that has different settings. For more details on using the frame calculator. If you do not use the Frame Calculator A system that is under no load with SMs registered and is able to communicate indicates basic connectivity. and choose frequencies far apart within the band. available at http://motorola. This ensures that at any one instant the collocated modules are either all receiving or all transmitting. refer to the Canopy Release 8 User Guide. the less you will see interference issues. and the calculator outputs details on the frame including an Uplink Rcv SQ Start value. Issue 1. layout and position of modules. The physical and spectral separation and local RF conditions (influenced by tower geometries. the issue of one AP attempting to receive a signal from a distant SM. The frame calculator in a module can be used to perform all frame calculations. which may be hidden under light loads. downlink data percentage.3. but cause problems when the system becomes heavily loaded. among other variables) may support good performance. while a nearby AP is transmitting and overpowering the signal from the distant SM. 8.canopywireless. and use of reflectors on BHs. and high priority uplink percentage (with software scheduling only). 8. but testing and monitoring will be required to confirm that they do. A frame calculator is included in every module as a helper application to help calculate compatible settings. downlink data %. slots. May 2009 Page 30 . and slot settings Use the Frame Calculator (see Using the Frame Calculator below) to ensure compatible receive start times. The frame calculator does not itself configure or change any settings on the module. Then the operator varies the Downlink Data % in each calculation until the calculated values of Uplink Rcv SQ Start for all collocated APs are within 150 time bits. This avoids. if 100 ft (30 m) of vertical separation is not possible. The operator enters settings into the calculator. but does not indicate that the system will function well under heavy load. The more conservatively you design collocation. for example.2 Establishing Vertical Separation   provide 100 ft (30 m) of vertical separation between same-band modules.

The ratio of downlink Carried Load to uplink Carried Load. Even though there may be airtime or slots available.4. Larger Packets With larger packets (Canopy handles packets up to 1522 Bytes). The specifications of the load include both packet size and packet rate. Longer range settings can reduce the number of slots in a frame and packet size (breakage on 64-byte boundaries) can affect packing efficiency (the percentage of fragments fully packed with 64 bytes). Test equipment measures the load delivered at the Ethernet interface of a module. Different combinations of system inputs will result in different constraints limiting system performance. Issue 1. the system constraint is processing power in any module handling the traffic stream. 14 Mbps is a typical maximum aggregate throughput for larger packet sizes for an FSK system.1.2 System Performance and System Constraints In any complex system like Canopy there are multiple performance constraints. As resources are exhausted at any point in the system. or maximum bits per second.2 Release Notes 9 Performance Benchmarking Process 9.1 Definitions Aggregate Throughput Offered Load Sum of uplink plus downlink traffic. The load is calculated from packet size and number of packets. May 2009 Page 31 . The Downlink/Uplink Load Ratio is determined from the Carried Loads. which can also be stated as slots. NOTE: Do not confuse the Downlink/Uplink Load Ratio with the Downlink Data configuration parameter. as the Canopy system is a Time Division Duplex (TDD) system.Release 9.1. the system constraint is airtime. packets may be dropped. The following terms are used where these release notes discuss packet processing: Carried Load Downlink/Uplink Load Ratio 9. The Downlink Data is set by the operator and determines the split of downlink and uplink slots in the air frame. The Carried Load equals the Offered Load minus Dropped Packets. the overall throughput is limited by packet handling ability. This can be calculated as follows: 64 Bytes/fragment x 2 fragments/slot x 34 slots/frame x 400 frames/sec x 8 bits/byte = 14 Mbps This is an aggregate (uplink plus downlink) limit. Smaller Packets With smaller packets. Test equipment generates a specified load to the Ethernet interface of a module (SM or the AP).

Confirm results by running longer tests at selected load rates. as shown in Figure 4 on page 33. Traffic is generated such that any one packet attempts to traverse an SM and then the AP. traffic mix. Review the results. The packet format used is a valid Ethernet/IP packet. noting where the packet loss (the difference between the Offered Load and Carried Load) is essentially zero (<0. May 2009 Page 32 . Count the frames that are received correctly at both sides.000 kbits/sec sustained rate and 500. RF conditions are maintained such that all links run at max rate (2X or 3X). No SM-to-SM traffic is included in the benchmark. 2. Traffic mix/Packet size All generated packets have a size of 64 Bytes. Repeat this through the load rates of interest. various settings. or the AP and then an SM.001%).3 Benchmark Definition In a complex system.Release 9. The PTP benchmark system consists of 1 BHM and 1 BHS. with traffic generation and measurement equipment connected to both BHs. Issue 1. and measurement techniques.1. any measurement depends on system configuration. The performance of interest is performance near a 50% Downlink/Uplink Load Ratio.000 kbits burst allocation (defaults) CIR: 0 (default) NAT: Disabled (default) VLAN: Disabled (default) High Priority: Disabled (default) Measurement technique 1.2 Release Notes 9. and so to have reproducible results a “benchmark” is defined. Traffic generation and measurement equipment is connected to both SMs and the AP.4. PMP Settings           PTP Settings    Downlink Data: 50% Max rate (2X or 3X) Enabled Encryption: Enabled (DES modules) Downlink Data: 50% Control Slots: 2 Range: 2 miles Max rate (2X or 3X) Enabled Encryption: Enabled (DES modules) MIR: 20. This is the Carried Load. This is the Offered Load. Send a specific number of frames at a specific rate through SMs and AP (uplinks) and AP and SM (downlink) simultaneously. System configuration The PMP benchmark system consists of 3 SMs and 1 Advantage AP.

2 Release Notes 3.4. x/6 pps x/6 pps SM1 x pps x/6 pps x/6 pps SM2 AP x/2 pps SM3 x/6 pps x/6 pps Ixia Test Controller and Load Modules x/2 pps All packets 64 Bytes Figure 4: Benchmark test setup Issue 1. May 2009 Page 33 . Confirm results by varying Downlink/Uplink Load Ratios to ensure no significant changes around the 50% benchmark.Release 9.

refer to FCC regulations.S. Any such modifications could void the user’s authority to operate the equipment and will void the manufacturer’s warranty. 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.9-GHz devices: The 4.2-GHz. AP Antenna. and (2) This device must accept any interference received. Operation is subject to the following two conditions: (1) This device may not cause harmful interference. If this equipment does cause harmful interference to radio or television reception.2. centered on 906-924 MHz in 1 MHz increments (within the 902-928 MHz ISM band) Issue 1.4-GHz. Federal Communication Commission (FCC) Notification For 900-MHz.7-GHz devices: This device complies with Part 15 of the US FCC Rules and Regulations. including interference that may cause undesired operation. 2. For additional information. which can be determined by turning the equipment on and off.2 10. may cause harmful interference to radio communications. and 5. if not installed and used in accordance with these instructions. This equipment generates. flat panel Maximum Transmitter Output 1 Power 24 dBm (250 mW) 26 dBm (400 mW) 26 dBm (400 mW) 26 dBm (400 mW) FCC ID Frequencies ABZ89FC5809 8 MHz channels.Release 9. 5. or 1 Lens 12 dBi integrated antenna 10 dBi Maxrad Model # Z1681. flat panel 10 dBi MTI Model #MT-2630003/N.9 GHz licenses.1 IMPORTANT NOTE ON MODIFICATIONS Intentional or unintentional changes or modifications to the equipment must not be made unless under the express consent of the party responsible for compliance.4-GHz. flat panel 10 dBi Mars Model # MA-IS91T2. Consult the dealer and/or experienced radio/TV technician for help. These limits are designed to provide reasonable protection against harmful interference in a residential installation. Reflector.4. May 2009 Page 34 .9-GHz band is a licensed band allocated to public safety services. This equipment has been tested and found to comply with the limits for a Class B digital device.1 NATIONAL AND REGIONAL REGULATORY NOTICES U. FCC IDs and the specific configurations covered are listed in Table 11. State and local government entities that provide public safety services are eligible to apply for 4. pursuant to Part 15 of the US FCC Rules. 5. Connect the affected equipment to a power outlet on a different circuit from that which the receiver is connected to. 10.2 Release Notes 10 Regulatory and Legal Notices 10. and can radiate radio-frequency energy and. Table 11: US FCC IDs and Industry Canada Certification Numbers and covered configurations Industry Canada Cert Number 109W-9000 Module Families 9000 SM. For 4. uses.

SM. AP P7/8/9 5200 BH SM.2 Release Notes FCC ID Industry Canada Cert Number Frequencies Module Families Antenna.5 MHz ISM band) 20 MHz channels. centered on 52755325 MHz in 5 MHz increments (within the 5250-5350 MHz U-NII band) 20 MHz channels. centered on 57355840 MHz in 5 MHz increments (within the 5725-5850 MHz ISM band) ABZ89FC5804 109W-5700 5700 BH. centered on 52755325 MHz in 5 MHz increments (within the 5250-5350 MHz U-NII band) 2400 BH. SM. centered on 24152457. AP 2400 BH. AP 7 dBi internal + 18 dB reflector 7 dBi internal + 9 dB lens 7 dBi internal 5400 BH.2 mW) 14 dBm (25 mW) 23 dBm (200 mW) 23 dBm (200 mW) 23 dBm (200 mW) 19 dBm (80 mW) --- 109W-5400 20 MHz channels.2 mW) 14 dBm (25 mW) 5 dBm (3. centered on 54955575 and 5675-5705 MHz in 5 MHz increments (within the 5470-5725 MHz U-NII band with 5600-5650 MHz excluded) 20 MHz channels.4.5 MHz increments (within the 24002483. SM. or 1 Lens 8 dBi integrated antenna (Indoor SM) Maximum Transmitter Output 1 Power 26 dBm (400 mW) 25 dBm (340 mW) ABZ89FC5808 109W-2400 20 MHz channels. SM 5700 AP Issue 1. SM. Reflector. SM. AP 7 dBi internal 7 dBi internal + 18 dB reflector 7 dBi internal + 10 dB lens 7 dBi internal + 10 dB lens 23 dBm (200 mW) 5 dBm (3. AP P10/11 8 dBi internal 8 dBi internal + 11 dB reflector 7 dBi internal 25 dBm (340 mW) 23 dBm (200 mW) 5 dBm (3. SM 5200 BH. May 2009 Page 35 . centered on 54955705 MHz in 5 MHz increments (within the 5470-5725 MHz U-NII band) 5210 BH ABZ89FT7623 --- 7 dBi internal 5400 BH.5 MHz in 2.2 mW) ABZ89FC3789 109W-5200 7 dBi internal + 18 dB reflector 7 dBi internal + 9 dB lens 7 dBi internal + 18 dB reflector ABZ89FC5807 for P7/8/9 ABZ89FC3789 for P10/11 109W-5210 for P78/9 109W-5200 for P10/11 20 MHz channels.2 mW) 14 dBm (25 mW) 23 dBm (200 mW) 5 dBm (3. AP 7 dBi internal + 18 dB reflector 7 dBi internal + 9 dB lens 5700 BH.Release 9.

2.2 Release Notes FCC ID Industry Canada Cert Number Frequencies Module Families Antenna.9-GHz devices: The 4.9-GHz band is a licensed band allocated to public safety services. For additional information.2. May 2009 Page 36 .4 and 5. and 5. pursuant to RSS-210 of Industry Canada. if displayed. Antennas not included or having a gain greater than as shown in Table 11 are strictly prohibited from use with this device.cept. Operation is subject to the following two conditions: (1) This device may not cause harmful interference. This equipment has been tested and found to comply with the limits for a Class B digital device.2-GHz. including DFS compliance. which can be determined by turning the equipment on and off. Government entities that provide public safety services are eligible to apply for 4. For compliant operation in the 2.2 Industry Canada (IC) Notification For 900-MHz.9 GHz licenses. or 1 Lens Maximum Transmitter Output 1 Power Note 1: To ensure regulatory compliance. may cause harmful interference to radio communications. 10. Motorola Canopy Wireless equipment operating in the 2. If this equipment does cause harmful interference to radio or television reception. This equipment generates. To reduce potential radio interference to other users. 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.4-GHz. Industry Canada Certification Numbers and the specific configurations covered are listed in Table 11. Users should be cautioned to take note that in Canada high power radars are allocated as primary users (meaning they have priority) of 5250 – 5350 MHz and 5650 – 5850 MHz and these radars could cause interference and/or damage to license-exempt local area networks (LELAN). These limits are designed to provide reasonable protection against harmful interference in a residential installation. Required antenna impedance is 50 ohms. and (2) This device must accept any interference received. uses.4 GHz band.3 Regulatory Requirements for CEPT Member States (www. This device has been designed to operate with the antennas listed in Table 11 and having a maximum gain as shown in Table 11.Release 9. and can radiate radio-frequency energy and. Reflector. Consult the dealer and/or experienced radio/TV technician for help. For 4. the transmit power (EIRP) from the built-in patch antenna and any associated reflector dish shall be no more than 100mW (20dBm). 5.4 GHz band.2. Issue 1. 5. the antenna type and its gain should be chosen so its Equivalent Isotropic Radiated Power (EIRP) is not more than that permitted for successful communication. including interference that may cause undesired operation.7-GHz devices: This device complies with RSS-210 of Industry Canada. the professional installer is responsible for ◦ ◦ setting the Transmitter Output Power on the Confiiguration => Radio page no higher than listed for a given configuration setting the Region Code on the Configuration => General page to the correct region setting the External Gain on the Configuration => Radio page. to the gain of any external device (reflector. For compliant operation in the 5. refer to Industry Canada regulations. lens) ◦ 10.4-GHz.org) When operated in accordance with the instructions for use.4 GHz bands is compliant with CEPT Recommendation 70-03 Annex 3 for Wideband Data Transmission and HIPERLANs.4. Connect the affected equipment to a power outlet on a different circuit from that which the receiver is connected to. if not installed and used in accordance with these instructions. the transmit power (EIRP) from the built-in patch antenna and any associated reflector dish shall be no more than 1 W (30 dBm).

for CEPT member states. see http://europa. Denmark. The relevant Declaration of Conformity can be found at http://motorola. Contact the appropriate national administrations for details on the conditions of use for the bands in question and any exceptions that might apply. Czech Republic. Belgium. UK New EU member states: Bulgaria.canopywireless. Finland. implemented by Member States on 31 October 2005.General authorization required for public service Romania – Individual license required.dk for further information. 2. Liechtenstein.4GHz bands is exempt from individual licensing under Commission Recommendation 2003/203/EC. For further details. Martinique. Indoor operation at 100mW (20dBm) is permitted across the band 2400 to 2483.Release 9.4. Luxembourg.php. the designation of Canopy 5. Ireland. makes the frequency band 5470-5725 MHz available in all EU Member States for wireless access systems.7 GHz connectorized product is a two-way radio transceiver suitable for use in Broadband Wireless Access System (WAS). Lithuania.4 & 5.4GHz products become “Class 1 devices” and these do not require notification under article 6. Slovakia Other non-EU & EFTA countries: Bosnia and Herzegovina. Estonia. Any outdoor operation in the band 2454 to 2483. Poland. Switzerland. section 4 of the R&TTE Directive.5MHz shall not exceed 10mW (10dBm).com/doc.canopywireless. Spain.4 European Union Notification for 5.2. no operation outdoor in the band 2400 to 2420MHz    Italy – If used outside own premises.htm 10. Germany.ero. For EU member states.4GHz products are only marked with the symbol and may be used in any member state.com/doc. May 2009 Page 37 .int/information_society/policy/radio_spectrum/ref_documents/index_en. The relevant Declaration of Conformity can be found at http://motorola. It is a Issue 1. St Pierre et Miquelon. these 5.4 GHz Wideband Data Transmission equipment has been designated exempt from individual licensing under decision ERC/DEC(01)07.4 GHz band will be removed in 2011.php. Slovenia. Turkey   The following countries have a limited implementation of CEPT Recommendation 70-03 Annex 3A:  − − − − France – Outdoor operation at 100mW is only permitted in the frequency band 2400 to 2454 MHz. RLAN equipment in both the 2. denoting that national restrictions apply (for example. Italy. or Fixed Wireless Access (FWA) systems.2 Release Notes The following countries have completely implemented CEPT Recommendation 70-03 Annex 3A (2. Sweden. T/R 22-06 not implemented Motorola Canopy Radios operating in the 2400 to 2483. Mayotte – 100mW indoor & outdoor is allowed Réunion and Guyana – 100mW indoor. Consequently. Where necessary. Iceland.5MHz band are categorized as “Class 2” devices within the EU and are marked with the class identifier symbol . Under this decision. Hungary. This 2. Radio Local Area Network (RLAN). Portugal. Also see www. Latvia. Norway. France). Greece. However. Motorola Canopy Radio equipment operating in the 5470 to 5725 MHz band are categorized as “Class 1” devices within the EU in accordance with ECC DEC(04)08 and are “CE” marked to show compliance with the European Radio & Telecommunications Terminal Equipment (R&TTE) directive 1999/5/EC.4 GHz band):  EU & EFTA countries: Austria.7 GHz Product The 5. Netherlands. Malta. general authorization required Luxembourg . the end user is responsible for obtaining any National licenses required to operate this product and these must be obtained before using the product in any particular country. Cyprus.eu. The French restriction in the 2.5 MHz  French Overseas Territories: Guadeloupe. A European Commission decision.4 GHz equipment is “CE” marked to show compliance with the European Radio & Telecommunications Terminal Equipment (R&TTE) directive 1999/5/EC.

6 EU Declaration of Conformity for RoHS Compliance Motorola hereby.2.Release 9. The relevant Declaration of Conformity can be found at http://www.5 Equipment Disposal Waste (Disposal) of Electronic and Electric Equipment Please do not dispose of Electronic and Electric Equipment or Electronic and Electric Accessories with your household waste.10Czech Republic Notification 2. Issue 1. No duplex working 10. GL-12/R/2000.2. 10.canopywireless. 10. The relevant Declaration of Conformity can be found at http://www.2.7 UK Notification The 5. declares that these Motorola products are in compliance with the essential requirements and other relevant provisions of Directive 2002/95/EC.php.7 GHz connectorized product has been notified for operation in the UK.2.com/doc.9 Luxembourg Notification For the 2. installations must conform to the requirements of IR2007 in terms of EIRP spectral density against elevation profile above the local horizon in order to protect Fixed Satellite Services.2.8 Belgium Notification Belgium national restrictions in the 2. 5. 5.canopywireless.2.4 GHz products can be operated in accordance with the Czech General License No. The frequency range 5795-5815 MHz is assigned to Road Transport & Traffic Telematics (RTTT) in the U. May 2009 Page 38 . point-to-point or point-to-multipoint operation is only allowed on campus areas. please contact your local equipment supplier representative or service center for information about the waste collection system in your country.4. For UK use. The operator is responsible for obtaining any national licenses required to operate this product and these must be obtained before using the product in any particular country. In European Union countries.2 Release Notes Class 2 device and uses operating frequencies that are not harmonized throughout the EU member states. UK licensing specifies that radiolocation services shall be protected by a Dynamic Frequency Selection (DFS) mechanism to prevent co-channel operation in the presence of radar signals. 10. 10. 10.4 GHz band include    EIRP must be lower then 100 mW For crossing the public domain over a distance >300m the user must have the authorization of the BIPT.4 GHz products can be operated in accordance with the Czech General License No.com/doc.K.4 GHz band. and when operated in accordance with instructions for use it is compliant with UK Interface Requirement IR2007. and shall not be used by FWA systems in order to protect RTTT devices. In some countries or regions.php. GL-30/R/2000. This equipment is marked 0977to show compliance with the European R&TTE directive 1999/5/EC.4GHz products can only be used for mobile services. collection systems have been set up to handle waste of electrical and electronic equipment. Restriction of the use of certain Hazardous Substances (RoHS) in electrical and electronic equipment.

and antenna gain is restricted to 23 dBi (maximum of 40W from the Canopy 5.13Australia Notification 900 MHz modules must be set to transmit and receive only on center channels of 920.2. and cannot cause harmful interference on systems operating as primary applications. transmitter output power must be configured no higher than 14 dBm. 5735. (China Management Methods refers to the regulation Management Methods for Controlling Pollution by Electronic Information Products.12Brazil Notification Local regulations do not allow the use of 900 MHz.Release 9. transmitter output power must be configured no higher than 19 dBm. maximum EIRP respected for a 20 MHz channel. When using the passive reflector (18 dB). and that channel spacings comply with the allocated frequency band to protect Road Transport and Traffic Telematics services (for example.  Logo 1 means that the product contains no substances in excess of the maximum concentration value for materials identified in the China Management Methods regulation. When using the LENS (9 dB at 5. 5755. The radio equipment shall implement Dynamic Frequency Selection (DFS) as defined in Annex 1 of ITU-R Recommendation M.2. or 923 MHz so as to stay within the ACMA approved band of 915 MHz to 928 MHz for the class license and not interfere with other approved users.11Norway Notification Use of the frequency bands 5725-5795 / 5815-5850 MHz are authorized with maximum radiated power of 4 W EIRP and maximum spectral power density of 200 mW/MHz. even if generated by similar equipment. For compliant operation of an AP in the 5.4 GHz.1652 / EN 301 893. including after the module is reset to factory defaults. Canopy 5.7 GHz connectorized products). Note that for directional fixed links. For compliant operation in the 5. or 5. Users shall ensure that DFS functionality is enabled.2 Release Notes 10. the label and the disclosure table.7 GHz).4. May 2009 Page 39 .4 GHz radio by setting the Region Code to “Brazil”.14Labeling and Disclosure Table for China The People’s Republic of China requires that Motorola’s products comply with China Management Methods (CMM) environmental regulations. Important Note: This equipment operates as a secondary application. 5775 or 5835 MHz are suitable carrier frequencies). transmitter output power must be configured no higher than 5 dBm.4 GHz). When using the passive reflector (18 dB). 900 MHz modules’ transmitter output power (in dBm) must be set to stay within the legal regulatory limit of 30 dBm (1 W) EIRP for this 900 MHz frequency band. TPC is not required. Issue 1. 10. Directional antennae with a gain up to 23 dBi may be used for fixed point-to-point links.5 dBW/m measured with a reference bandwidth of 1 MHz. 2.2.4 GHz band.2. When not using the passive reflector or the LENS. The label is placed in a customer visible position on the product. When using the LENS (10 dB at 5. the transmitter output power of the radio must be configured no higher than 23 dBm. 922.2 GHz Canopy modules in Brazil.) Two items are used to demonstrate compliance. 10.7 GHz band. the Equivalent Isotropic Radiated Power from the built-in patch antenna and any associated reflector dish or LENS shall not exceed 36 dBm (4 W). 10. the Equivalent Isotropic Radiated Power from the built-in patch antenna and any associated reflector dish or LENS shall not exceed 30 dBm (1 W). The operator is responsible for enabling the DFS feature on any Canopy 5. After taking into account antenna gain (in dBi). transmitter output power must be configured no higher than 11 dBm. The power 2 flux density at the border between Norway and neighboring states shall not exceed – 122.7 GHz connectorized products have been notified for use in Norway and are compliant when configured to meet the above National requirements. so it has no rights against harmful interference. conducted transmit power shall not exceed 30 dBm.

such as battery modules. fifty years in the example shown.5 m (approx 20 in) Issue 1. Table 13: Exposure separation distances Module Type Canopy Module Canopy Module with Reflector Dish Canopy Module with LENS Separation Distance from Persons At least 20 cm (approx 8 in) At least 1. The EFUP indicated by the Logo 2 label applies to a product and all its parts. Certain field-replaceable parts. and has an Environmental Friendly Use Period (EFUP) in years. it is not intended to communicate compliance with EU RoHS or any other environmental requirements. install Canopy radios so as to provide and maintain the minimum separation distances from all persons shown in Table 13.3 RF EXPOSURE SEPARATION DISTANCES To protect from overexposure to RF energy.4. The Disclosure table is intended to communicate compliance with only China requirements. can have a different EFUP and are marked separately. May 2009 Page 40 .2 Release Notes  Logo 2 means that the product may contain substances in excess of the maximum concentration value for materials identified in the China Management Methods regulation. Table 12: Disclosure table 有毒有害物质或元素 部件名称 铅 (Pb) 汞 (Hg) 镉 (Cd) 六价铬 (Cr6+) 多溴联苯 (PBB) 多溴二苯醚 (PBDE) 金属部件 电路模块 电缆及电缆组件 塑料和聚合物部件 × × × ○ ○ ○ ○ ○ × × × ○ × × × ○ ○ ○ ○ ○ ○ ○ ○ × ○: ×: 表示该有毒有害物质在该部件所有均质材料中的含量均在SJ/T11363-2006 标准规定的限量要求以下。 表示该有毒有害物质至少在该部件的某一均质材料中的含量超出SJ/T11363-2006 标准规定的限量要求。 10.Release 9. Logo 1 Logo 2 The Environmental Friendly Use Period (EFUP) is the period (in years) during which the Toxic and Hazardous Substances (T&HS) contained in the Electronic Information Product (EIP) will not leak or mutate causing environmental pollution or bodily injury from the use of the EIP.5 m (approx 60 in or 5 ft) At least 0.

ca/rpb and Safety Code 6.de/ and Guidelines for Limiting Exposure to Time-Varying Electric.1 Details of Exposure Separation Distances Calculations and Power Compliance Margins Limits and guidelines for RF exposure come from:  US FCC limits for the general population.gc. See the Health Canada web site at http://www. and Electromagnetic Fields. as well as the guidelines and suggestions for evaluating compliance in FCC OET Bulletin 65. 5. 10 W/m for RF energy in the 2.3.hc-sc. and requirements in Part 1 of Title 47 of the Code of Federal Regulations. 2 2 Peak power density in the far field of a radio frequency point source is calculated as follows: P"G S= 4 # d2 where 2 S = power density in W/m P = RMS transmit power capability of the radio. in m ! Rearranging terms to solve for distance yields d= P"G 4# S Table 14 shows calculated minimum separation distances d. Health Canada limits for the general population.fcc. and 5. Table 14: Calculated exposure distances and power compliance margins ! Band Antenna P Variable G S d (calculated) Recommended Separation Distance Power Compliance Margin Issue 1. guidelines. converted from dB d = distance from point source. 5.4. May 2009 Page 41 . 10.icnirp.gov.Release 9.4-. in W G = total Tx gain as a factor. ICNIRP (International Commission on Non-Ionizing Radiation Protection) guidelines for the general public. See the ICNIRP web site at http://www.2 Release Notes Antenna of connectorized or integrated 900 MHz module Indoor 900 MHz SM At least 60 sm (24 in) At least 10 cm (4 in) The following section and its Table 14 provide details and discussion of the associated calculations. See the FCC web site at http://www. Magnetic. and the policies.2-.4-.7-GHz frequency bands.   The applicable power density exposure limits from the documents referenced above are   6 W/m for RF energy in the 900-MHz frequency band in the US and Canada. recommended distances and resulting power compliance margins for each frequency band and antenna combination.

integrated 2 Simulation model used to estimate Specific Absorption Rate (SAR) levels 0.2 W (23 dBm) 0.25 W (24 dBm) G 10.4 GHz integrated integrated plus reflector integrated plus LENS 5.5 m (5 ft) 50 cm (12 in) Power Compliance Margin 7 7 2 2.Release 9.0 (10 dB) 15.3 (8 dB) 79. May 2009 Page 42 .0 (7 dB) 316 (25 dB) 40 (16 dB) 5. Exposure to the sides and back of the module is significantly less.0 (7 dB) 316 (25 dB) 50 (17 dB) 10 2 W/m 10 2 W/m 10 2 W/m 10 2 W/m 10 2 W/m 10 2 W/m 10 2 W/m 10 2 W/m 10 2 W/m 10 2 W/m 1 2 W/m 13 cm 46 cm 9 cm 9 cm 9 cm 9 cm 9 cm 9 cm 9 cm 71 cm 28 cm 2.34 W (25 dBm) 0.2 W (23 dBm) 0.4. Issue 1.0 (7 dB) 316 (25 dB) 50 (17 dB) 5.2 W (23 dBm) 6. or LENS) always has the same distance. These are conservative distances:    They are along the beam direction (the direction of greatest energy).5 m (5 ft) 50 cm (12 in) 20 cm (8 in) 1.2 GHz integrated integrated plus reflector integrated plus LENS 5.0032 W (5 dBm) 0. regardless of frequency band.2 W (23 dBm) 0.0032 W (5 dBm) 0.34 W (25 dBm) 0. the calculated compliance distance d is greatly overestimated because the far-field equation models the reflector as a point source and neglects the physical dimension of the reflector.4 W (26 dBm) 0.4 GHz integrated integrated plus reflector 5.2 W (23 dBm) 0.7 GHz integrated integrated plus reflector Integrated plus LENS The Recommended Separation Distance is chosen to give significant compliance margin in all cases.5 m (5 ft) 20 cm (8 in) 1.8 (12 dB) S 6 W/m 6 W/m 2 d (calculated) 23 cm 23 cm Recommended Separation Distance 60 cm (24 in) 60 cm (24 in) 10 cm (4 in) 20 cm (8 in) 1.13 900 MHz external integrated indoor. to simplify following exposure distances in the field.2 Release Notes Variable Band Antenna P 0. reflector.025 W (14 dBm) 0.4 (19 dB) 5. It is also chosen so that a given item (bare module. with considerable margin.3 10 5 279 31 5 279 31 5 4. They meet sustained exposure limits for the general population (not just short-term occupational exposure limits).5 3.020 W (13 dBm) 0.5 m (5 ft) 50 cm (12 in) 20 cm (8 in) 1. In the reflector cases.

Inc. derivative works (including images) partial copies and portions of updated works. non-assignable. including translations. Motorola's entire liability and your sole and exclusive remedy for any breach of the foregoing limited warranty will be. Upon such termination you must destroy the Software. replacement of the disk(s). or disaster recovery purposes. Motorola (or its supplier) retains all title.4 LEGAL NOTICES 10. You may make two copies of the Software. or refund of the unused portion of your bargained for contractual benefit up to the amount paid for this Software License. decompile or reverse engineer. EITHER EXPRESS OF IMPLIED.2 Release Notes 10. under normal use. RETURN THE SOFTWARE TO PLACE OF PURCHASE FOR A FULL REFUND. Ownership. archival. except and only to the extent that such activity is expressly permitted by applicable law. in consideration of the promises and mutual obligations contained herein. The Software is Motorola’s (or its supplier's) confidential proprietary information. AND MOTOROLA AND ITS LICENSORS EXPRESSLY DISCLAIM ALL OTHER WARRANTIES. INSTEAD.4. the receipt and sufficiency of which are hereby mutually acknowledged. MOTOROLA DOES NOT WARRANT THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERRORFREE. DO NOT USE THE SOFTWARE OR RELATED PRODUCT. (FOR ITSELF AND ITS LICENSORS). non-transferable. and for other good and valuable consideration. Motorola. 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.. 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). This License is effective until terminated. provision of downloadable patch or replacement code.1 Software License Terms and Conditions ONLY OPEN THE PACKAGE. compilations. and General will survive any termination. May 2009 Page 43 . all accompanying written materials and all copies thereof. BY BREAKING THE SEAL ON THIS DISK KIT / CDROM. ownership and intellectual property rights to the Software and any copies. The written materials are provided "AS IS" and without warranty of any kind. THIS LIMITED WARRANTY IS THE ONLY WARRANTY PROVIDED BY MOTOROLA. THE FOLLOWING AGREEMENT IS A LEGAL AGREEMENT BETWEEN YOU (EITHER AN INDIVIDUAL OR ENTITY). and the sections entitled Limited Warranty. BECAUSE SOME JURISDICTIONS DO NOT Issue 1. IF YOU DO NOT AGREE TO THESE TERMS. Subject to the following terms and conditions. You agree not to disassemble. AND MOTOROLA. THE RIGHT TO USE THIS PRODUCT IS LICENSED ONLY ON THE CONDITION THAT YOU AGREE TO THE FOLLOWING TERMS. MOTOROLA DOES NOT WARRANT ANY SOFTWARE THAT HAS BEEN OPERATED IN EXCESS OF SPECIFICATIONS. but only a limited right of use.4. MISUSED. DAMAGED. OR IMPROPERLY INSTALLED. On any copy you make of the Software. You agree not to disclose it or make it available to anyone without Motorola’s written authorization. This Software License Agreement does not convey to you any interest in or to the Software.Release 9. INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. you must reproduce and include the copyright and other proprietary rights notice contained on the copy we have furnished you of the Software. NEGLECTED. INC. revocable. OR IF YOU USE THE SOFTWARE OR RELATED PRODUCT. Limited Warranty. will perform substantially in accordance with Motorola’s published specifications for that release level of the Software. at Motorola's option. you and Motorola agree as follows: Grant of License. OR USE THE SOFTWARE AND RELATED PRODUCT IF YOU ACCEPT THE TERMS OF THIS LICENSE. grants to you a personal. OR THAT DEFECTS IN THE SOFTWARE WILL BE CORRECTED. This License will terminate immediately without notice from Motorola or judicial resolution if you fail to comply with any provision of this License. Termination. but only for backup. or create derivative works of the Software. YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT. Now. 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. You will exercise no less than reasonable care to protect the Software from unauthorized disclosure. Limitation of Remedies and Damages. therefore.

when you are transferring the Software together with the Motorola equipment on which it operates. rent or lease the Software without our written consent. 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. THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU. you agree that Motorola will be under no obligation to provide any support. whether foreseeable or unforeseeable. or 2) if you are a Motorola licensed distributor. regulations. Illinois law governs this license. when you are transferring the Software either together with such Motorola equipment or are transferring the Software as a licensed duly paid for upgrade. You may transfer all other Software. Any maintenance and support of the Related Product will be provided under the terms of the agreement for the Related Product. when you are transferring the Software as permitted herein. By accepting the license granted under this agreement. EMPLOYEES OR AFFILIATES OF THE FOREGOING BE LIABLE TO YOU FOR ANY CONSEQUENTIAL. without limitation. INCIDENTAL. or (iii) interim relief from a court is necessary to prevent serious and irreparable injury to that party or to others. General. export controls or economic sanctions imposed by the US Government. THE ABOVE LIMITATION MAY NOT APPLY TO YOU. 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.4. SPECIAL OR SIMILAR DAMAGES WHATSOEVER (including. May 2009 Page 44 . You may not sublicense or otherwise transfer. INDIRECT. enhancement or replacement of a prior version of the Software. update. controversy or claim. 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. Regardless of whether any remedy set forth herein fails of its essential purpose. regardless of the basis of the form of the action. business interruption. Limitation of Remedies and Damages.2 Release Notes ALLOW THE EXCLUSION OR LIMITATION OF IMPLIED WARRANTIES. new release. Motorola's liability to you for direct damages for any cause whatsoever. your records and accounts to determine compliance with the terms of this Agreement. OFFICERS. loss of business information and the like). Motorola shall not be responsible for maintenance or support of the software. IN NO EVENT SHALL MOTOROLA OR ANY OF THE LICENSORS.Release 9. You may not transfer the Software in violation of any laws. Cost of mediation will be shared equally. upon reasonable advance notice and during normal business hours. You and Motorola hereby agree that any dispute. claim or controversy involves intellectual property. controversy or claim involving intellectual property. You specifically acknowledge that the software may be subject to United States and other country export control laws. maintenance or service in connection with the Software or any application developed by you. will be submitted for non-binding mediation. However. prior to initiation of any formal legal process. THIS LIMITATION WILL NOT APPLY IN CASE OF PERSONAL INJURY ONLY WHERE AND TO THE EXTENT THAT APPLICABLE LAW REQUIRES SUCH LIABILITY. US Government Users. as applicable. regardless of the basis of the claim and even if Motorola or a Motorola representative has been advised of the possibility of such damage. damages for loss of business profits. DIRECTORS. Maintenance and Support. BECAUSE SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES. If you are a Motorola licensed distributor. to another party. Motorola shall have the right to audit annually. patch. arising out of the use or inability to use the Software or accompanying written materials. will be limited to the price paid for the Software that caused the damages. You shall comply strictly with all requirements of all applicable export control laws and regulations with respect to all such software and materials. you may not transfer the Software to another party except: (1) if you are an end-user. except for any dispute. (ii) the dispute. Transfer. prior to initiation of any formal legal process. Nothing in this Section will prevent either party from resorting to judicial proceedings. Export Controls. not otherwise having an agreed restriction on transfer. If you are a US Government user. Disputes. and you destroy any copy of the Software you do not transfer to that party. if (i) good faith efforts to resolve the dispute under these procedures have been unsuccessful. you agree to transfer the Software with a license agreement having terms and conditions no less restrictive than those contained herein. and supersedes all previous oral or written communications between us regarding the subject except for Issue 1.227-7013. Right to Audit. In the case of software designed to operate on Motorola equipment.

2 Release Notes such executed agreement. CONSEQUENTIAL.) IN NO CASE SHALL MOTOROLA’S LIABILITY EXCEED THE AMOUNT YOU PAID FOR THE PRODUCT. May 2009 Page 45 . If a product is found defective during the warranty period. Issue 1. INCIDENTAL. INDIRECT. so the above exclusion or limitation may not apply to you. which may be a reconditioned unit. all other provisions shall remain valid. EXEMPLARY OR OTHER DAMAGE ARISING OUT OF THE USE OR INABILITY TO USE THE PRODUCT (INCLUDING. (Some states do not allow the exclusion or limitation of incidental or consequential damages. 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. DAMAGES FOR LOSS OF BUSINESS PROFITS. WITHOUT LIMITATION.5 LIMIT OF LIABILITY IN NO EVENT SHALL MOTOROLA BE LIABLE TO YOU OR ANY OTHER PARTY FOR ANY DIRECT. SPECIAL. 10.2 Hardware Warranty in US Motorola US offers a warranty covering a period of 1 year from the date of purchase by the customer. If any provision is held invalid. EVEN IF MOTOROLA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 10. OR FROM ANY BREACH OF WARRANTY.4. LOSS OF BUSINESS INFORMATION OR ANY OTHER PECUNIARY LOSS. It may not be modified or waived except in writing and signed by an officer or other authorized representative of each party. Motorola will repair or replace the product with the same or a similar model. without charge for parts or labor. BUSINESS INTERRUPTION.4. unless such invalidity would frustrate the purpose of our agreement. GENERAL.Release 9.

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer: Get 4 months of Scribd and The New York Times for just $1.87 per week!

Master Your Semester with a Special Offer from Scribd & The New York Times