Canopy® Software Release 9.4.
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.
Release 9.4.2 Release Notes Table of Contents 1 2 Introduction ............................................................................................................... 6 1.1 Notes and Highlights .......................................................................................... 6 1.2 Abbreviations ..................................................................................................... 7 1.3 Names ............................................................................
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 ...............
Release 9.4.2 Release Notes List of Tables Table 1: Product Names................................................................................................7 Table 2: Release 9.4.2 enhancements ........................................................................10 Table 3: Packet per Second (pps) performance ..........................................................10 Table 4: Issues resolved in Release 9.4.2 ...................................................................
Release 9.4.2 Release Notes 1 Introduction These notes cover Canopy Release 9.4.2. This release is a general release applicable to PMP 100 and PTP 100 (FSK) PMP 54400 and PTP 54200 (5.4-GHz OFDM) PMP 49400 and PTP 49200 (4.9-GHz OFDM) Release 9.4.2 is not applicable to PMP 35500 (3.5-GHz OFDM) For details on applicability, see section 7.1.1 and Table 9: Radios Upgradeable to Release 9.4.2 on page 22. 1.1 NOTES AND HIGHLIGHTS Highlights of Canopy Release 9.4.
Release 9.4.2 1.2 Release Notes ABBREVIATIONS The following abbreviations may be used in these notes: BH BHM Backhaul Module – timing master BHS Backhaul Module – timing slave AP Access Point Module SM Subscriber Module CNUT Canopy Network Updater Tool CMM Cluster Management Module DFS Dynamic Frequency Selection for radar avoidance MIB Management Information Base P7/P8/P9/P10/P11 1.
Release 9.4.2 Release Notes Product Name Older Name Previous Name Model Number (example) PTP 49200 Series — Canopy 4.9-GHz OFDM BH PMP 500 Series — Canopy 3.5-GHz OFDM PMP CAP 35500 — 3.5-GHz OFDM AP 3540AP CSM 35500 — 3.5-GHz OFDM SM 3540SM 1.
Release 9.4.2 1.6 Release Notes FEEDBACK ON DOCUMENTATION Is this document accurate, complete, and clear? How can it be improved? Please send your feedback on Canopy documentation to technical-documentation@canopywireless.com. 1.7 TECHNICAL SUPPORT Tip! Do not clear the Event Log after you encounter issues. It may be useful to Technical Support, if you need to escalate the issue. Here is the escalation path for resolution of a problem: 1.
Release 9.4.2 Release Notes 2 Features and Enhancements The following sections list features and enhancements for Release 9.4.2. 2.1 RELEASE 9.4.2 ENHANCEMENTS Release 9.4.2 adds the enhancements listed in Table 2. Table 2: Release 9.4.2 enhancements Product Family Enhancement Summary PMP 100 PTP 100 None — PTP 49200 Support for PTP 49200 With Release 9.4.2, 4.9-GHz OFDM radios are now offered as BHs, as well as APs and SMs.
Release 9.4.2 Release Notes Hardware series Product P11 or P10 P9 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 Section 9, Performance Benchmarking Process, on page 31 describes the benchmarking process used to measure packets per second and discusses the meaning and limitations of the benchmark. 2.3 SUPPORT FOR P11 HARDWARE 5.2-GHz and 5.
Release 9.4.2 Release Notes 3 Resolved Issues Issues resolved in Release 9.4.2 are listed in Table 4. Table 4: Issues resolved in Release 9.4.2 Product Family Description Explanation All PPPoE-configured SM stuck in “LCP (Link Control Protocol) Negotiating” Before, on a link with some re-regs, the SM might get stuck in “LCP Negotiating” mode if a PPPoE session was started, but the LCP and IPCP stages never completed. Connect/disconnect buttons wouldn’t have resolved the issue. Release 9.
Release 9.4.2 Release Notes Product Family Description Explanation PMP 54400 PMP 49400 Downlink broadcast traffic can exhibit packet loss (9492) This issue affected all systems (OFDM/PMP 400 and FSK/PMP 100). It is resolved for OFDM in Release 9.4.2, but can still affect FSK systems. For OFDM (PMP 400) systems, set the Broadcast Repeat Count to 0 or 1 on an AP handling broadcast video and to the default of 2 on other APs.
Release 9.4.2 Release Notes 4 Known Open Issues Known open issues for Release 9.4.2 are listed in Table 5. Table 5: Known open issues Product Family Description Discussion and Recommendations All PPPoE In Session message not syncing to AP (10385) Under some conditions, occasionally an SM establishes a PPPoE session successfully and correctly displays PPPoE In Session on the SM’s Home => General Status page, but the AP does not show the SM in a PPPoE session on the AP’s Home => Session Status page.
Release 9.4.2 Release Notes Product Family Description Discussion and Recommendations PMP 49400 PMP 54400 Ranging issues at maximum settings (9798) Workaround: Due to occasional ranging issues at higher settings, 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. Sectors configured for a Max Range of 10 miles or less are not affected by this limitation.
Release 9.4.2 Release Notes 5 Notes and Reference 5.1 NOTES Table 6 lists notes new for this release. Table 7 lists continuing notes first mentioned in previous Release Notes. Table 6: New Notes for Release 9.4.2 Product Family Description Discussion and Recommendations All A derived temperature is now shown on a module’s web page (10379) The temperature is board (not ambient air) temperature. Different hardware vintages use different methods for deriving temperature.
Release 9.4.2 Release Notes Table 7: Previous Notes ID Description Discussion and Recommendations - Changes to boxTemperature OIDs Starting with Release 9.4 the boxTemperature (1.3.6.1.4.1.161.19.3.3.1.5) OID (which returned an octet string value) is no longer valid. Two new OIDS which return integer values are added: boxTemperatureC Object ID: 1.3.6.1.4.1.161.19.3.3.1.35 Syntax: INTEGER Access: read-only Status: current Radio temperature in Celsius. boxTemperatureF Object ID: 1.3.6.1.4.1.161.19.3.3.
Release 9.4.2 Release Notes ID Description Discussion and Recommendations None Managing module accounts and passwords The best security practice is to be aware the unit starts with root and admin accounts, to plan your approach to accounts, and set passwords for all accounts. A module that either is fresh from the factory or has been operator-reset to factory defaults has two user accounts: root and admin, both with ADMINISTRATOR level permissions.
Release 9.4.2 Release Notes ID Description Discussion and Recommendations 4844, 2756 When using Link Test with MIR, need to set both ends To see the effects of MIR capping, you can run a link test with MIR enabled. To get meaningful results, set Link Test with MIR to Enabled on the Tools => Link Capacity Test tab in both the SM and the AP. When it is enabled on only one end, results are misleading.
Release 9.4.2 Release Notes Table 8: Release 9.4.2 operation based on Region Code and frequency band Region 1 Code United States Canada Europe Brazil Australia 900 MHz 2.4 GHz 4.9 GHz 5.1 GHz AP/SM AP/SM /BH AP/SM /BH AP/SM/ BH No effect No effect NA NA No effect No effect No effect No effect No effect No effect No effect NA No effect NA 5.2 GHz AP/ BHM ≥P10: FCC/IC DFS ≤ P9: no DFS NA ≥ P10: FCC/IC DFS ≤ P9: no DFS NA NA NA NA 5.
Release 9.4.2 Release Notes 6 Canopy MIB The Canopy Enterprise MIB (Management Information Base), consisting of 5 MIB definition files, supports SNMP access to Canopy modules. The MIB files are available for download from the Canopy tab of http://motorola.motowi4solutions.com/software/. Detailed information on the Canopy MIBs is available at http://motorola.motowi4solutions.com/support/online_tools/.
Release 9.4.2 Release Notes 7 Upgrading to Release 9.4.2 7.1 BEFORE YOU UPGRADE 7.1.1 Applicability Table 9 shows the product series, hardware series, and radio types that are upgradeable to Release 9.4.2. Table 9: Radios Upgradeable to Release 9.4.
Release 9.4.2 Release Notes PMP 100 PTP 100 (FSK) PMP 54400 PTP 54200 (5.4-GHz OFDM) PMP 49400 PTP 49200 (4.9-GHz OFDM) 8.2.7 8.2.4 8.4.3 9.0 9.3 9.3.1 9.4 Use a .pkg3 file and CNUT 3.12 or Prizm 3.1 for all upgrades 9.4.1 9.4.2 9.4.2 9.4.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.
Release 9.4.2 Release Notes Information on the Motorola Prizm element management system is available at http://motorola.motowi4solutions.com/products/prizm/. Prizm documentation and installers are available for download from the Canopy tab of http://motorola.motowi4solutions.com/software/. .pkg3 Packages Upgrades use package files whose name extensions are .pkg3. Earlier packages (.pkg or .pkg2 files) cannot be used with CNUT Release 3.12 and Prizm Release 3.1. A key aspect of .
Release 9.4.2 7.2.2 Release Notes Obtaining and Preparing Prizm 1. Download Prizm 3.1 Patch 7 and Prizm 3.1 Patch 7 Release Notes. If upgrading PMP 49400 or using PTP 49200 modules, also download Prizm 3.1 Patch 4.9 OFDM. 2. From the Canopy tab of http://motorola.motowi4solutions.com/software/, download Prizm 3.1 Patch 7 Prizm 3.1 Patch 7 Release Notes. If upgrading PMP 49400 or using PTP 49200 modules, also download Prizm 3.1 Patch 4.9 OFDM. 3.
Release 9.4.2 Release Notes 3. Add the appropriate .pkg3 file(s) to the managed packages list. Depending on the package downloaded in section 7.3, Obtaining Upgrade Packages, you will have one or more of the following .pkg3 files: CANOPY94_2BUILDOFFICIAL_DES.pkg3 CANOPY94_2BUILDOFFICIAL_AES.pkg3 CANOPY94_2BUILDOFFICIAL_OFDM_DES.pkg3 CANOPY94_2BUILDOFFICIAL_OFDM_AES.pkg3 4.
Release 9.4.2 Release Notes a. Refresh/Discover. b. Check whether the resulting elements list shows the SM as operating on the new release. c. If it does not, reboot the problem SM. d. Check whether the SM is shown as operating on Release 9.4.2. e. If it is not, re-initiate the upgrade of the SM using CNUT or Prizm. 14. Disable SM Auto-update on CNUT or Prizm, according to CNUT help file or Prizm documentation. 7.4.
Release 9.4.2 Release Notes 8 Collocation 8.1 COLLOCATING 5.2-GHz AND 5.4-GHz MODULES 5.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. This signal can interfere with 5.2-GHz channels as shown In Table 10. Because of this, care needs to be taken in choosing 5.4-GHz channels where 5.4 GHz systems are collocated with 5.2-GHz systems. Choosing 5.
Release 9.4.2 8.2 Release Notes COLLOCATING 5.4-GHz AND 5.7-GHz MODULES For collocation design, the 5.4-GHz and 5.7-GHz frequency bands are essentially one continuous band. When collocating 5.4-GHz and 5.7-GHz modules, use the guidelines for collocating modules within a band listed under Collocating Same-Frequency Band Modules on Page 29. Alternatively, either provide 100 ft (30 m) of vertical separation between the 5.4-GHz and 5.7GHz radios.
Release 9.4.2 Release Notes − Set identical range, downlink data %, and slot settings − Use the Frame Calculator (see Using the Frame Calculator below) to ensure compatible receive start times. This ensures that at any one instant the collocated modules are either all receiving or all transmitting. This avoids, for example, the issue of one AP attempting to receive a signal from a distant SM, while a nearby AP is transmitting and overpowering the signal from the distant SM. 8.3.
Release 9.4.2 Release Notes 9 Performance Benchmarking Process 9.1.1 Definitions The following terms are used where these release notes discuss packet processing: Aggregate Throughput Sum of uplink plus downlink traffic. Offered Load Test equipment generates a specified load to the Ethernet interface of a module (SM or the AP). The specifications of the load include both packet size and packet rate. Carried Load Test equipment measures the load delivered at the Ethernet interface of a module.
Release 9.4.2 9.1.3 Release Notes Benchmark Definition In a complex system, any measurement depends on system configuration, traffic mix, various settings, and measurement techniques, and so to have reproducible results a “benchmark” is defined. System configuration The PMP benchmark system consists of 3 SMs and 1 Advantage AP, as shown in Figure 4 on page 33. Traffic generation and measurement equipment is connected to both SMs and the AP.
Release 9.4.2 3. Release Notes Confirm results by varying Downlink/Uplink Load Ratios to ensure no significant changes around the 50% benchmark.
Release 9.4.2 Release Notes 10 Regulatory and Legal Notices 10.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. Any such modifications could void the user’s authority to operate the equipment and will void the manufacturer’s warranty. 10.2 10.2.1 NATIONAL AND REGIONAL REGULATORY NOTICES U.S. Federal Communication Commission (FCC) Notification For 900-MHz, 2.
Release 9.4.2 FCC ID ABZ89FC5808 ABZ89FC3789 Release Notes Industry Canada Cert Number 109W-2400 109W-5200 ABZ89FC5807 for P7/8/9 109W-5210 for P78/9 ABZ89FC3789 for P10/11 109W-5200 for P10/11 ABZ89FT7623 --- ABZ89FC5804 --- 109W-5400 109W-5700 Frequencies 20 MHz channels, centered on 24152457.5 MHz in 2.5 MHz increments (within the 24002483.
Release 9.4.
Release 9.4.2 Release Notes The following countries have completely implemented CEPT Recommendation 70-03 Annex 3A (2.
Release 9.4.2 Release Notes Class 2 device and uses operating frequencies that are not harmonized throughout the EU member states. The operator is responsible for obtaining any national licenses required to operate this product and these must be obtained before using the product in any particular country. This equipment is marked 0977to show compliance with the European R&TTE directive 1999/5/EC. The relevant Declaration of Conformity can be found at http://www.canopywireless.com/doc.php. 10.2.
Release 9.4.2 Release Notes 10.2.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. The radio equipment shall implement Dynamic Frequency Selection (DFS) as defined in Annex 1 of ITU-R Recommendation M.1652 / EN 301 893. Directional antennae with a gain up to 23 dBi may be used for fixed point-to-point links.
Release 9.4.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, and has an Environmental Friendly Use Period (EFUP) in years, fifty years in the example shown.
Release 9.4.2 Release Notes Antenna of connectorized or integrated 900 MHz module At least 60 sm (24 in) Indoor 900 MHz SM At least 10 cm (4 in) The following section and its Table 14 provide details and discussion of the associated calculations. 10.3.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. See the FCC web site at http://www.fcc.
Release 9.4.2 Release Notes Variable d Recommended Separation Distance P G S (calculated) Power Compliance Margin external 0.4 W (26 dBm) 10.0 (10 dB) 6 W/m 2 23 cm 60 cm (24 in) 7 integrated 0.25 W (24 dBm) 15.8 (12 dB) 6 W/m 2 23 cm 60 cm (24 in) 7 indoor, integrated Simulation model used to estimate Specific Absorption Rate (SAR) levels 10 cm (4 in) 2 integrated 0.34 W (25 dBm) 6.3 (8 dB) 10 2 W/m 13 cm 20 cm (8 in) 2.3 integrated plus reflector 0.34 W (25 dBm) 79.
Release 9.4.2 10.4 Release Notes LEGAL NOTICES 10.4.1 Software License Terms and Conditions ONLY OPEN THE PACKAGE, OR USE THE SOFTWARE AND RELATED PRODUCT IF YOU ACCEPT THE TERMS OF THIS LICENSE. BY BREAKING THE SEAL ON THIS DISK KIT / CDROM, OR IF YOU USE THE SOFTWARE OR RELATED PRODUCT, YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT. IF YOU DO NOT AGREE TO THESE TERMS, DO NOT USE THE SOFTWARE OR RELATED PRODUCT; INSTEAD, RETURN THE SOFTWARE TO PLACE OF PURCHASE FOR A FULL REFUND.
Release 9.4.2 Release Notes ALLOW THE EXCLUSION OR LIMITATION OF IMPLIED WARRANTIES, THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU. Limitation of Remedies and Damages.
Release 9.4.2 Release Notes such executed agreement. It may not be modified or waived except in writing and signed by an officer or other authorized representative of each party. If any provision is held invalid, all other provisions shall remain valid, unless such invalidity would frustrate the purpose of our agreement.
