canopy release 7.3 release notes issue 1 -...

CAN7.3-SRN-en

Issue 1

December 2005

CanopyTM Software Release 7.3 Software Release Notes

Canopy Software Release 7.3 Software Release Notes

Issue 1, December, 2005 of 27

Notices See important regulatory and legal notices in Section 8 on page 18.

Trademarks, Product Names, and Service Names MOTOROLA, the stylized M Logo and all other trademarks indicated as such herein are trademarks of Motorola, Inc. ® Reg. US Pat & Tm. Office. Canopy is a trademark of Motorola, Inc. All other product or service names are the property of their respective owners.

© 2005 Motorola, Inc. All rights reserved

http://www.motorola.com/canopy



Table of Contents

1 Introduction ________________________________________________________ 5 1.1 Document Change History ______________________________________________ 6 1.2 Feedback on Documentation ____________________________________________ 6 1.3 Technical Support_____________________________________________________ 6

2 Release 7.3.6 Features ________________________________________________ 7

3 Issues Resolved in Release 7.3.6 ________________________________________ 8

4 Known Issues and Special Notes for Release 7.3.6 _________________________ 8 4.1 Issue with collocated BHMs running software scheduling under Release 7.2.9 or 7.3.6. 9

5 Canopy Management Information Base (MIB) ___________________________ 10

6 Upgrading to Release 7.3.6 ___________________________________________ 11 6.1 Before You Begin ____________________________________________________ 11

6.1.1 Applicability ______________________________________________________________ 11 6.1.2 Upgrade only from Release 7.2.9 ______________________________________________ 11 6.1.3 Upgrade using CNUT (Canopy Network Update Tool) _____________________________ 11 6.1.4 Upgrade AP and SMs to at least Release 6.1 before enabling VLAN __________________ 11 6.1.5 Don’t Downgrade __________________________________________________________ 11

6.2 Procedures to Upgrade to Release 7.3.6 __________________________________ 11 7 Enabling Hardware Scheduling _______________________________________ 13

7.1 Collocating APs running Software Scheduling and APs running Hardware Scheduling_______________________________________________________________ 14 7.2 Procedures to Enable Hardware Scheduling ______________________________ 16

8 Regulatory and Legal Notices_________________________________________ 18 8.1 Important Note on Modifications _______________________________________ 18 8.2 National and Regional Regulatory Notices ________________________________ 19

8.2.1 US Federal Communication Commission (FCC) and Industry Canada (IC) Notification ___ 19 8.2.2 Regulatory Requirements for CEPT Member States (www.cept.org) __________________ 20 8.2.3 European Union Notification _________________________________________________ 21 8.2.4 Equipment Disposal ________________________________________________________ 21 8.2.5 UK Notification____________________________________________________________ 21 8.2.6 Belgium Notification________________________________________________________ 21 8.2.7 Luxembourg Notification ____________________________________________________ 21 8.2.8 Czech Republic Notification __________________________________________________ 21 8.2.9 Brazil Notification__________________________________________________________ 21 8.2.10 Australia Notification ______________________________________________________ 22

8.3 Exposure Separation Distance __________________________________________ 22 8.3.1 Details of Exposure Separation Distances Calculations _____________________________ 22

8.4 Legal Notices ________________________________________________________ 23 8.4.1 Software License Terms and Conditions_________________________________________ 23



8.4.2 Hardware Warranty in US____________________________________________________ 26 8.5 Limit of Liability_____________________________________________________ 26

List of Figures Figure 1: Discovering Downlink Data Percentages for Collocation ......................................................... 15 Figure 2: Discovering Downlink Data Percentages for Collocation (Cont’d) ........................................... 16 Figure 3: CNUT Tool Menu ..................................................................................................................... 17

List of Tables Table 1: Release 7.3.6 Features.................................................................................................................. 7 Table 2: Issues Resolved in Release 7.3.6 ................................................................................................... 8 Table 3: Issues and Special Notes for Release 7.3.6.................................................................................... 8 Table 4: Features and Issues with collocated Backhauls........................................................................... 10 Table 5: CNUT Telnet/FTP Passwords..................................................................................................... 12 Table 6: Software Version ........................................................................................................................ 13 Table 7: Software Boot Version ................................................................................................................ 13 Table 8: FPGA Version ............................................................................................................................ 13 Table 9: Control Slots vs Number of SMs on AP....................................................................................... 18 Table 10: US FCC IDs and Industry Canada Certification Numbers ........................................................ 19 Table 11: Exposure Separation Distances................................................................................................. 22 Table 12: Exposure Calculation Results and Power Compliance Margins ................................................ 23



1 Introduction Important! Backhauls (BHs) should generally not be upgraded to Release 7.2.9 or 7.3.6, but rather left on Release 7.1.4. See Section 4.1 for details.

Highlights of Release 7.3.6 include:

o For all operators:

• The ability to enable hardware scheduling on non-Advantage series P9 APs, which then gives

o the ability to use Committed Information Rate (CIR) on either P8 or P9 SMs

o the ability to enable a High Priority channel per SM (rather than per AP sector) on P9 SMs

and since the uplink High Priority channel is dynamically sized under hardware scheduling (vs statically sized under software scheduling), this gives better handling of priority and non-priority traffic

A non-Advantage Series 9 AP enabled for hardware scheduling does not provide the higher capacity, higher throughput, and lower latency of an Advantage AP.

• Additional information on the AP Sessions page to give visibility into the operational MIR, CIR, and VLAN settings and their source, either from BAM, SM, or AP.

• The ability to configure a module so that the override/default plug functions either as an override plug (current operation – overriding IP address and passwords) or a default plug (returning the unit to factory default values) when the unit is rebooted with the override/default plug inserted.

o For operators using the High Priority Channel:

o Release 7.3.6 running either software or hardware scheduler resolves issues with the High Priority Channel not working correctly in some instances, and is therefore strongly recommended for APs and SMs in networks using the High Priority channel.

Important! Release 7.3.6 is strongly recommended for the APs and SMs in any networks running with High Priority channel enabled.

Sections 2 covers the complete list of new features.

Section 3 list and describes resolved issues.

Section 4 lists known issues and special notes on Release 7.3.

Modules should be running Release 7.2.9 before upgrading to Release 7.3.6. Other upgrade paths are not supported. See Section 6.1.2 on page 11 for details.



Important! The two schedulers, hardware scheduler and software scheduler, don’t cross-communicate. An SM enabled for hardware scheduling only communicates with an AP enabled for hardware scheduling – it will not communicate with an AP enabled for software scheduling. An SM enabled for software scheduling only communicates with an AP enabled for software scheduling – it will not communicate with an AP enabled for hardware scheduling. Due to this, care and caution is needed in the upgrade procedure and the sequence for enabling hardware scheduling in APs and SMs to avoid stranding SMs.

The following abbreviations are used throughout these notes:

BH Backhaul Module, either timing master or timing slave

BHM Backhaul Module – timing master

BHS Backhaul Module – timing slave

AP Access Point Module

SM Subscriber Module

1.1 Document Change History

Issue 1 First Issue

1.2 Feedback on Documentation We welcome your feedback on Canopy documentation. Comments on structure, content, accuracy, completeness, or any other area are appreciated. Please send your feedback to [email protected].

1.3 Technical Support If problems arise during upgrade or use of Canopy Release 7.3.6, the Canopy support team is here to help. Here is the escalation path for resolution of a problem:

1. Check this document, especially the Troubleshooting section.

2. Escalate the problem to your Canopy supplier.

3. Escalate the problem to Canopy Technical Support or other designated Tier 3 technical support:

Canopy Technical Support email: [email protected]

1 888 605 2552 or +1 217 824 9742

When you send e-mail or call, please include the following information:

• Information on your network configuration, especially IP addresses and MAC addresses, whether you are using Software Scheduling or Hardware Scheduling, and features enabled, like NAT, VLAN, high priority channel, or CIR.



• Version numbers of the software on the modules with problems.

2 Release 7.3.6 Features Release 7.3.6 adds the new features listed in Table 1.

Table 1: Release 7.3.6 Features

Feature Name Requires Advantage AP?

Category Benefits

Hardware Scheduling on non-Advantage series P9 APs

No Quality of Service (QoS) control

Support for Committed Information Rate (CIR) on P8 and P9 SMs. The ability to enable a High Priority channel per SM (rather than per AP sector) on P9 SMs, and since the uplink High Priority channel is dynamically sized under hardware scheduling (vs statically sized under software scheduling), this gives better handling of priority and non-priority traffic.

A non-Advantage Series 9 AP enabled for hardware scheduling does not provide the higher capacity, higher throughput, and lower latency of an Advantage AP.

Additional information on the AP Sessions page

No Operations Gives visibility into currently active MIR, CIR, and VLAN values, and source (SM, BAM, or AP) for those values. During transitions (reboot, re-registration), you may observe changing sources, depending on system operation and number of SMs simultaneously registering, as the AP and SM go through their registration process. After registration, during normal operation, you should see a non-changing source.

Option to have override/default plug reset module to factory defaults

No Security The ability to configure a module so that the override/default plug functions either as an override plug (current operation – overriding IP address and passwords) or a default plug (returning the unit to factory default values) when the unit is rebooted with the override/default plug inserted.

In some situations, operators may prefer the default operation so that anybody gaining physical access to a module and using an override/default plug will reset the module to factory settings and not be able to learn the module’s settings. In other situations, operators may prefer the ease-of-operation of only overriding IP addresss and password, and still being able to see the other configured settings.

The option is set on a modules Configuration page, under the parameter “Set To Factory Defaults Upon Default Plug Detection”. If this parameter is enabled, an override/default plug functions as a default plug. If this parameter is disabled, an



Feature Name Requires Advantage AP?

Category Benefits

override/default plug functions as an override plug.

The factory default for this option itself is “Disabled”, so be sure you re-enable the option (if desired) when resetting all the parameters on a module that has been reset to factory defaults.

3 Issues Resolved in Release 7.3.6 Release 7.3.6 resolves the issues listed in Table 2.

Table 2: Issues Resolved in Release 7.3.6

Applicable to Summary

Software Scheduling

Hardware Scheduling

With High Priority channel enabled, under some conditions and settings of MIR (Maximum Information Rate), the low priority traffic would get priority over high priority traffic, up to “starving” the high priority traffic. This issue is resolved in Release 7.3.6

Yes Yes

Correct value is returned when doing a SNMP query for linkOutOctets on an AP running HW scheduling. (The SNMP query was returning 0 in Release 7.2.9.)

No Yes

4 Known Issues and Special Notes for Release 7.3.6 Table 3 lists known issues and special notes for Release 7.3.6. The “Applicable to” column of the table indicates whether the item applies to software scheduling, hardware scheduling, or both.

Table 3: Issues and Special Notes for Release 7.3.6

Applicable to Summary

Software Scheduling

Hardware Scheduling

Issue with collocation of BHMs running software scheduler under Release 7.2.9 or 7.3.6. See Section 4.1 for details.

Y N

When enabling hardware scheduling on a sector running 7.3.6, use CNUT and the “Configure Advantage Platform Scheduler 7.2” tool

Y Y

Low incidence web interface lock-up Y Y



Low incidence of calibration values lost when upgrading a module Y Y

Transmit Frame Spreading can decrease available throughput at the SM Y Y

“Registered SM count” is in error (high) under certain conditions Y Y

Erroneous RSSI and dBm “jumps” when running hardware scheduling N Y

BER is not available when running hardware scheduling N Y

AP broadcast repeat count not settable when running hardware scheduling

N Y

Higher power usage for hardware scheduling and 2X operation N Y

Link Efficiencies less than 90% okay in 2X operation N Y

At certain ranges, may need to force 1X operation when running hardware scheduling

N Y

Custom logo has different name for Advantage (advantaged.jpg) vs standard modules (canopy.jpg).

N Y

Actual CIR (Committed Information Rate) values double when operating at 2X using hardware scheduling

N Y

When running a Link Test via SNMP, the packet length defaults to 1518 bytes and cannot be set higher

Y Y

BAM 2.0 only allows a 10,000 kbps maximum sustained uplink or downlink rate

Y Y

Anomalies in the Release 7.2 expansion to 10 IP addresses for SNMP traps.

Y Y

4.1 Issue with collocated BHMs running software scheduling under Release 7.2.9 or 7.3.6.

Important! Do not collocate BHMs running software scheduling and Release 7.2.9 or 7.3.6. When collocated BHMs run software scheduling under Release 7.2.9 or 7.3.6, one BHM (one link) will connect normally while the other BHMs will never connect. BHMs running hardware scheduling do not see the problem.

You can have collocated BHMs running 7.2.9 or 7.3.6 if no more than one of the BHMs is running software scheduling (in other words, any other BHMs are running hardware scheduling), but do note that only P9 BHs can run hardware scheduling - P8 BHs can never run hardware scheduling. Also, you can run a single BH running Release 7.2.9 or 7.3.6 and software scheduling at a given site without issues – the issue only arises with collocation.

Collocated BHMs means two or more BHMs operating in very close proximity, for example on the same tower, that are synchronized and operating in the same frequency band.

When collocating BHs using hardware and software scheduling, for optimum capacity use the procedure detailed in Section 7.1 to tune the transmit/receive ratio by varying the Downlink Data %.

Important! Due to this issue, BHs should generally not be upgraded to Release 7.2.9 or 7.3.6, unless specific features are desired, and care is taken in planning to prevent two software-scheduled 7.2.9 or 7.3.6 BHs operating in close proximity.

The following table lists the useful combinations of release, hardware series, and scheduler, and resulting features and issues.



Table 4: Features and Issues with collocated Backhauls

Release Series Scheduler Features Issues

7.1.4 P8 or P9

Software No issues with collocation Doesn’t support 7.2.9 backhaul features

7.2.9 or 7.3.6

P8 or P9

Software or Hardware

Differentiated Services

Option to disable bridge filtering

Software scheduled BHs running 7.2.9 or 7.3.6 cannot be collocated.

7.2.9 or 7.3.6

P9 Hardware 20 Mbps BHs will auto-rate-adapt down to 10 Mbps if RF environment deteriorates.

Ability to set a Committed Information Rate (CIR). This can be useful when running with the high priority channel enabled - set CIR on the low priority channel after enabling High Priority channel, to keep the low priority channel from being starved completely under high use of the high priority channel.

Can be collocated with other hardware scheduled BHs, or with one software scheduled BH.

Throughput reduced by ~5%.

Requires P9 series hardware on both ends of the link.

5 Canopy Management Information Base (MIB) The Canopy Enterprise MIB, consisting of 5 MIB definition files, has been updated to include SNMP access to the new and changed features in Release 7.3.6.

MIB files are used by Network Management Systems (NMSs) to support a host of surveillance, monitoring, control, and operational tasks.

If you are not using an SNMP Network Management System: Skip this section on MIBs.

If you are using an SNMP Network Management System: Load the MIBs per the instructions for your NMS.

Important! When loading the Canopy MIB files,

• First load the three standard MIB files,

• Then load the Canopy MIB files.

Some NMSs are not sensitive to order, but some require a specific loading order to build a MIB “tree”. Loading in the recommended order will avoid any issues with loading sequence.



For more information on using SNMP with your Canopy system, or understanding the Canopy MIBs, see the module user manuals and the application note “Canopy Network Management with MRTG”. These are available on the Canopy website at http://motorola.canopywireless.com/support_library.php.

6 Upgrading to Release 7.3.6

6.1 Before You Begin

6.1.1 Applicability

Release 7.3.6 is applicable to all Canopy modules, except for 30/60 and 300 Mbps Backhaul modules and CMMs (Cluster Management Modules).

6.1.2 Upgrade only from Release 7.2.9

Modules currently running Release 7.2.9 can be upgraded to Release 7.3.6. Modules running releases prior to Release 7.2.9 should first be upgraded to Release 7.2.9, then upgraded to Release 7.3.6. Direct upgrade from, say, Release 6.1 to Release 7.3.6 is not supported.

6.1.3 Upgrade using CNUT (Canopy Network Update Tool)

Using CNUT makes the upgrade easier and simpler, and avoids potential issues with stranding SMs. Release 7.3.6 is only be available as a CNUT package – individual software loads and FPGA loads are not available. For more information and details on installing CNUT on a PC or Linux machine, download the CNUT software and help file from the support section of http://www.motorola.com/canopy.

CNUT 1.1 contains improvements to both the underlying scripts and to the user interface over CNUT 1.0, and is recommended for performing the upgrade to Release 7.3.6.

6.1.4 Upgrade AP and SMs to at least Release 6.1 before enabling VLAN

Before enabling VLAN on an AP, upgrade the AP and all its SMs to at least 6.1. If VLAN is enabled on the AP while some SMs are running a release previous to 6.1, those SMs will lose connectivity and will not be able to register to the AP. The recovery action is to disable VLAN at the AP, upgrade the SM, then enable VLAN.

6.1.5 Don’t Downgrade

Downgrades are not recommended. You can put individual modules in a nonfunctioning state by attempting to load software that is older than the minimum load needed for that hardware series, type, scheduler, or frequency band. If you believe you have a need to downgrade to an older software release, contact technical support before you attempt the downgrade.

6.2 Procedures to Upgrade to Release 7.3.6 The following steps should be used for upgrading to Release 7.3.6. For steps involving CNUT, see the CNUT help file or click on the Help menu in the CNUT application for additional information.

When using CNUT you will be required to provide the Telnet/FTP password of any module you are updating, either as a network setting or for individual modules. The password is either the “Display-Only Access” password or the “Full Access” password you set previously on the module’s Configuration page. Table 5 shows which password to use for the CNUT Telnet/FTP password.



Table 5: CNUT Telnet/FTP Passwords

On the module’s Configuration page, which passwords are set?

“Display-Only Access” Password?

“Full Access” Password?

Then use this password with CNUT:

No password No password No password required Set* No Password* “Display-Only Access” password* No password Set “Full-Access” password Set Set “Full-Access” password

* Note, if you have set only the “Display-Only Access” password, then that password gives full access (read and write) to the module for FTP and telnet, as well as for configuration changes on the module’s interface pages.

Upgrade Steps

1. Plan your upgrade. Many operators perform an upgrade on a lab system or a friendly AP sector to gain experience with the upgrade procedures and also gain experience with the new features, then proceed with a full network upgrade. Schedule the upgrade during a maintenance window.

2. Obtain the following from the Canopy web site at http://www.motorola.com/canopy -> Support -> Software Updates:

• Canopy Network Updater Tool (CNUT) 1.1 for Windows or Linux

Note! CNUT 1.1 is a big download (~50 MB) that contains Java 1.5 in order to simplify installation and use of CNUT. • CNUT 1.1 Release Notes

• Canopy System Software package for Release 7.3.6

Then

1. Install CNUT on a PC or a Linux machine. Follow the CNUT 1.1 Release Notes, paying particular attention to confirming you have PERL installed per the notes.

2. Within CNUT, add your Canopy infrastructure (APs, BHs, and CMMs) elements to the “Network Root”.

3. Move and Modify the elements until you have captured your network in CNUT.

IMPORTANT! Pay particular attention to the connectivity you establish in CNUT’s outline view. This should be the connectivity as viewed from the point you connect to the network, not necessarily your network hierarchy (depending on where you connect to your network to do the update). When CNUT “discovers” the network, it will update any elements that are misnamed, but CNUT relies on the connectivity information you enter in the outline view to manage the network update and step through the infrastructure elements during update.

Now, using CNUT,

1. Refresh/Discover Entire Network to have CNUT find information on your network elements, and auto-detect all your SMs.

2. Add the Canopy 7.3.6 package to CNUT.



3. Just before doing any updates, use Refresh/Discover to confirm all SMs are active before upgrading.

4. Choose the elements you wish to update at this time – a selection of elements, a network branch, or the entire network. As mentioned before, most operators will plan to gain experience by upgrading a portion of their network at a time, depending on network size and their own operations procedures.

5. Update, and monitor the update’s progress.

6. After the update is complete, Refresh/Discover to confirm all elements have updated.

7. To update SMs that do not have Publicly Accessible IP addresses, turn on SM Auto-update on the APs that those SMs are registered to.

8. Confirm the upgrade is complete by comparing the Software Version, Software Boot Version, and FPGA Version indicated on each module’s Status page against the following tables:

Table 6: Software Version

Software Version CANOPY 7.3.6

Table 7: Software Boot Version

Software Boot Version CANOPYBOOT 3.0

Table 8: FPGA Version

Hardware Series

Scheduler DES Encryption AES Encryption

P9 Hardware 07-06-05 (DES) 07-06-05 (AES)

P9 Software 02-02-05 02-03-05

P7, P8 Hardware 07-13-05 (P7-P8) Not supported

P7, P8 Software 05-11-04 (DES) 05-11-04 (AES)

Note! With an AP or BHM upgraded to 7.3.6 and running software scheduling, and an SM or BHS running a previous release, there is a very small probability that there will be a framing mismatch due to a particularly unlucky combination of range settings, downlink percentage settings, and slot settings. If after upgrading an AP or BHM you have trouble connecting to an SM or BHS running on a previous load, click on the “Adjust Frame for All” button at the bottom of the Configuration page. If “Reboot Required” is shown in red next to the “Reboot” button, then you did have frame mismatch - click “Reboot”. If “Reboot Required” isn’t shown, continue troubleshooting of other possible causes for the lack of connection.

7 Enabling Hardware Scheduling Section 7 applies to any P9 series AP, either Advantage or non-Advantage

Advantage APs and SMs previously enabled for hardware scheduling remain hardware scheduled after the upgrade to Release 7.3.6.



Series P9 APs and subtending SMs running software scheduling and Release 7.3.6 can be enabled for hardware scheduling using the procedures in section 7.2. On sectors with Advantage APs, hardware scheduling supports 2X operation and reduced latency, as well as other Advantage features. On sectors with non-Advantage APs (but still P9 series hardware), hardware scheduling provides per-SM High Priority channel and Committed Information Rate (CIR). Unlike Advantage APs, the non-Advantage APs do not support reduced latency or 2X operation.

7.1 Collocating APs running Software Scheduling and APs running Hardware Scheduling

Canopy avoids self-interference by syncing collocated APs (so they begin each transmission cycle at the same time) and requiring that collocated APs have the same transmit/receive ratio (so they stop transmitting and start receiving at the same time). This ensures that at any one instant they 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.

Parameters that affect transmit/receive ratio include range, slots, downlink data percentage, and high priority uplink percentage. Previous to Release 6.1, Canopy ensured that APs in a cluster had the same transmit/receive ratio by requiring that all these parameters be set the same. Release 6.1 introduced a new frame structure for hardware scheduling (different than for software scheduling), but the rule remains to have all collocated APs have the same transmit/receive ratio. Additional engineering is needed for setting the parameters in a mixed cluster containing APs running both hardware and software scheduling.

Release 6.1 and later releases include a frame calculator to help do this. The operator inputs various AP settings into the calculator, and the calculator outputs many details on the frame including a value called “Uplink Rcv SQ Start”. This calculation should be done for each AP that has different settings. 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 300 “time bits”.

The frame calculator is available on any module running Release 6.1 or later by clicking on Expanded Stats in the navigation column, then clicking on Frame Calculator (at the bottom of the expanded navigation column). Figure 1 and Figure 2 show the steps to use the calculator to discover values of Downlink Data % that will put all the “Uplink Rcv SQ Start” values within the required 300 “time bits”.

Note the calculator is not using the data on the module or setting any module parameters - it is just a convenience application running on the module. Also note you can use any module running Release 6.1 or later to do the calculations for any AP – you don’t have to do the calculations by running the calculator on the AP in question.

Important! APs with mismatched transmit/receive ratios and low levels of data traffic may see little effect on throughput. As the data traffic increases, the impact of mismatched transmit/receive ratios will increase. This means that a system that isn’t “tuned” for collocation may work fine at low traffic levels, but have issues at higher traffic level. The best practice is to “tune” for collocation from the beginning, and prevent future issues as the sectors get built out and traffic increases.



Figure 1: Discovering Downlink Data Percentages for Collocation



Figure 2: Discovering Downlink Data Percentages for Collocation (Cont’d)

7.2 Procedures to Enable Hardware Scheduling The following steps should be used for enabling hardware scheduling on Series P9 APs and any SMs that will communicate with a Series P9 AP. These steps apply for both Advantage and non-Advantage Series P9 APs. For steps involving CNUT, see CNUT Help for additional information. For steps involving the “Configure Advantage Platform Scheduler”, see its documentation associated with CNUT.



Important! If you have SMs which are powered-down during the Release 7.3.6 upgrade, you will want to take actions to get them powered-up and upgraded to Release 7.3.6 before enabling hardware scheduling. If you have SMs which have been upgraded to Release 7.3.6 but which are powered-down during the enabling of hardware scheduling, you will have to take the AP back to software scheduling to communicate to those SMs and turn on hardware scheduling (or gain access through the Ethernet port of the SM to turn on hardware scheduling).

Use the “Configure Advantage Platform Scheduler 7.2” to enable hardware scheduling on a sector of an AP and SMs running Release 7.3.6.

• Obtain and load the “Configure Advantage Platform Scheduler 7.2”, if not downloaded previously. All downloads of Release 7.3.6, and downloads of Release 7.2.9 since August, 2005, include the 7.2 version of the scheduler configurator tool in the standard download. Alternatively, the 7.2 version of “Advantage Platform Scheduler Configurator Tool” can be downloaded by itself from the Canopy web site. The net result is that a new JAR file, CNUTHwScheduler72.jar, is used to support enabling hardware (or software) scheduling.

Important! Confirm you have the 7.2 version of the Configure Advantage Platform Scheduler before enabling hardware scheduler on APs and SMs running Release 7.3.6 by looking at the CNUT Tools menu – see

Figure 3.

Figure 3: CNUT Tool Menu

• Enable hardware scheduling on an AP sector, a standalone SM or AP, or your entire network,



• After enabling hardware scheduling, go to the AP’s Configuration page and enter the appropriate number of reserved Control Slots from Table 9. With hardware scheduling, one parameter, Control Slots, replaces the 6 slot parameters used with software scheduling.

Table 9: Control Slots vs Number of SMs on AP

Number of SMs Registering to AP Reserved Control Slots Recommended

1 – 10 0

11 – 50 1

51 – 150 2

151 – 200 3

Slots reserved for control are only used for SM service requests – the hardware scheduler doesn’t assign data to the reserved slots. Unreserved slots will first be used by the hardware scheduler for data, and then any unused slots are available to the SMs for service requests, along with any reserved slots. Selecting the number of slots to reserve for control is then a trade-off: “too few” reserved control slots means that under high traffic latency will increase, and “too many” reserved control slots means that the maximum capacity is slightly reduced unnecessarily. Table 9 gives the best starting point for configuring typical systems. Operators wanting to maximize capacity may want to trial running with fewer control slots than shown, and operators wanting to reduce the probability of increased latency may want to trial running with more control slots.

• Click on Save Changes, and click on Reboot.

• Confirm that all SMs are connected and communicating with the AP.

• If running collocated software and hardware scheduling APs, go to the AP’s Configuration page and enter the Downlink Data % you discovered in section 7.1, Collocating APs running Software Scheduling and APs running Hardware Scheduling.

• If some SMs are not connecting, review your previous steps and decide on a course of action:

o Either take the AP back to software scheduling and confirm the SM is running Release 7.2, then enable the AP and the SM for hardware scheduling. During the time the AP is using software scheduling it will not communicate with SMs running hardware scheduling.

o Or gain access to the Ethernet port of the SM and upgrade it to Release 7.2 (if needed) and then enable hardware scheduling.

8 Regulatory and Legal Notices

8.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.



8.2 National and Regional Regulatory Notices

8.2.1 US Federal Communication Commission (FCC) and Industry Canada (IC) Notification

This device complies with part 15 of the US FCC Rules and Regulations and with RSS-210 of Industry Canada. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) This device must accept any interference received, including interference that may cause undesired operation. In Canada, users should be cautioned to take note that high power radars are allocated as primary users (meaning they have priority) of 5250 – 5350 MHz and 5650 – 5850 MHz and these radars could cause interference and/or damage to license-exempt local area networks (LELAN).

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the US FCC Rules and with RSS-210 of Industry Canada. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio-frequency energy and, if not installed and used in accordance with these instructions, may cause harmful interference to radio communications. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment on and off, the user is encouraged to correct the interference by one or more of the following measures:

• Increase the separation between the affected equipment and the unit; • Connect the affected equipment to a power outlet on a different circuit from that which the

receiver is connected to; • Consult the dealer and/or experienced radio/TV technician for help.

FCC IDs and Industry Canada Certification Numbers are listed in Table 10:

Table 10: US FCC IDs and Industry Canada Certification Numbers Module Types

Operating Frequency Range

Maximum Transmitter Output Power

Reflector or Antenna

FCC ID Industry Canada Certification Number

SM AP ISM 902 to 928 MHz

250 mW (24 dBm) 400 mW (26 dBm) 400 mW (26 dBm) 400 mW (26 dBm)

Canopy integrated antenna with 12 dBi gain

Maxrad Model # Z1681, flat panel with 10 dBi gain

Mars Model # MA-IS91-T2, flat panel with10 dBi gain

MTI Model #MT-2630003/N, flat panel with 10 dBi gain

ABZ89FC5809 109W-9000ISM

SM AP BH

ISM 2400-2483.5 MHz

340 mW Allowed on SM and BH

ABZ89FC5808 109W-2400

SM AP BH

U-NII 5250-5350 MHz

200 mW Not Allowed ABZ89FC3789 109W-5200

BH U-NII 5250-5350 MHz

3.2 mW Recommended ABZ89FC5807 109W-5210

SM AP BH

ISM 5725-5850 MHz

200 mW Allowed on SM and BH

ABZ89FC5804 109W-5700



8.2.2 Regulatory Requirements for CEPT Member States (www.cept.org)

When operated in accordance with the instructions for use, Motorola Canopy Wireless equipment operating in the 2.4 and 5.4 GHz bands is compliant with CEPT Recommendation 70-03 Annex 3 for Wideband Data Transmission and HIPERLANs. For compliant operation in the 2.4 GHz band, the transmit power (EIRP) from the built-in patch antenna and any associated reflector dish shall be no more than 100mW (20dBm). For compliant operation in the 5.4 GHz band, the transmit power (EIRP) from the built-in patch antenna and any associated reflector dish shall be no more than 1 W (30 dBm).

The following countries have completely implemented CEPT Recommendation 70-03 Annex 3A (2.4 GHz band):

• EU & EFTA countries: Austria, Belgium, Denmark, Spain, Finland, Germany, Greece, Iceland, Italy, Ireland, Liechtenstein, Luxembourg, Netherlands, Norway, Portugal, Switzerland, Sweden, UK

• New EU member states: Czech Republic, Cyprus, Estonia, Hungary, Lithuania, Latvia, Malta, Poland, Slovenia, Slovakia

• Other non-EU & EFTA countries: Bulgaria, Bosnia and Herzegovina, Turkey

The following countries have a limited implementation of CEPT Recommendation 70-03 Annex 3A:

• France - Outdoor operation at 100mW is only permitted in the frequency band 2400 to 2454 MHz; o Any outdoor operation in the band 2454 to 2483.5MHz shall not exceed 10mW (10dBm); o Indoor operation at 100mW (20dBm) is permitted across the band 2400 to 2483.5 MHz

• French Overseas Territories: o Guadeloupe, Martinique, St Pierre et Miquelon, Mayotte – 100mW indoor & outdoor is

allowed o Réunion and Guyana – 100mW indoor, no operation outdoor in the band 2400 to 2420MHz

• Italy - If used outside own premises, general authorization required • Luxembourg - General authorization required for public service • Romania - Individual license required. T/R 22-06 not implemented

Motorola Canopy Radios operating in the 2400 to 2483.5MHz band and 5470 to 5725 MHz band are

categorized as “Class 2” devices within the EU and are marked with the class identifier symbol , denoting that national restrictions apply (for example, France). The French restriction in the 2.4 GHz band will be removed in 2011. Users are advised to contact their national administrations for the current status on the implementation of ECC DEC(04)08 for the 5.4GHz band.

This equipment is “CE” marked to show compliance with the European Radio & Telecommunications Terminal Equipment (R&TTE) directive 1999/5/EC. The relevant Declaration of Conformity can be found at http://www.canopywireless.com/doc.php.

Where necessary, the end user is responsible for obtaining any National licenses required to operate this product and these must be obtained before using the product in any particular country. However, for CEPT member states, 2.4 GHz Wideband Data Transmission equipment has been designated exempt from individual licensing under decision ERC/DEC(01)07. For EU member states, RLAN equipment in both the 2.4 & 5.4GHz bands is exempt from individual licensing under Commission Recommendation 2003/203/EC. Contact the appropriate national administrations for details on the conditions of use for the bands in question and any exceptions that might apply. Also see www.ero.dk for further information.



8.2.3 European Union Notification

The 5.7 GHz connectorized product is a two-way radio transceiver suitable for use in Broadband Wireless Access System (WAS), Radio Local Area Network (RLAN), or Fixed Wireless Access (FWA) systems. It is a Class 2 device and uses operating frequencies that are not harmonized throughout the EU member states. The operator is responsible for obtaining any national licenses required to operate this product and these must be obtained before using the product in any particular country.

This equipment is marked 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.

8.2.4 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. In some countries or regions, collection systems have been set up to handle waste of electrical and electronic equipment. In European Union countries, please contact your local equipment supplier representative or service centre for information about the waste collection system in your country.

8.2.5 UK Notification

The 5.7 GHz connectorized product has been notified for operation in the UK, and when operated in accordance with instructions for use it is compliant with UK Interface Requirement IR2007. For UK use, installations must conform to the requirements of IR2007 in terms of EIRP spectral density against elevation profile above the local horizon in order to protect Fixed Satellite Services. The frequency range 5795-5815 MHz is assigned to Road Transport & Traffic Telematics (RTTT) in the U.K. and shall not be used by FWA systems in order to protect RTTT devices. UK Interface Requirement IR2007 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.

8.2.6 Belgium Notification Belgium national restrictions in the 2.4 GHz band include

• EIRP must be lower then 100 mW • For crossing the public domain over a distance > 300m the user must have the authorization of the

BIPT. • No duplex working

8.2.7 Luxembourg Notification

For the 2.4 GHz band, point-to-point or point-to-multipoint operation is only allowed on campus areas. 5.4GHz products can only be used for mobile services.

8.2.8 Czech Republic Notification

This product can be operated in accordance with the Czech General Licence No. GL-12/R/2000

8.2.9 Brazil Notification

Local regulations do not allow the use of 900 MHz, 2.4 GHz, or 5.2 GHz Canopy modules in Brazil, nor do they allow the use of passive reflectors on 5.4 or 5.7 GHz Canopy Access Points.



For compliant operation in the 5.4 GHz band, the transmit power (EIRP) from the built-in patch antenna and any associated reflector dish shall be no more than 1 W (30 dBm). When using the passive reflector along with a 5.4 GHz Canopy radio, the transmitter output power of the radio must be configured no higher than 5 dBm. When not using the passive reflector, the transmitter output power of the radio must be configured no higher than 23 dBm.

The operator is responsible for enabling the DFS feature on any Canopy 5.4 GHz radio, and re-enabling it if the module is reset to factory defaults.

Important Note: This equipment operates as a secondary application, so it has no rights against harmful interference, even if generated by similar equipment, and cannot cause harmful interference on systems operating as primary applications.

8.2.10 Australia Notification

900 MHz modules must be set to transmit and receive only on 919, 920, 922, 923 or 924 MHz so as to stay within the ACA approved band of 915 MHz to 928 MHz for the class license, given Canopy’s 8 MHz channels (at 900 MHz).

After taking into account antenna gain (in dBi), 900 MHz modules transmitter output power (in dBm) must be set to stay within the legal regulatory limit of 30 dBm (1 W) EIRP for this 900 MHz frequency band.

8.3 Exposure Separation Distance The following table shows separation distances that support applicable exposure limits:

Table 11: Exposure Separation Distances

Module Type Separation Distance from all Persons

Canopy Module At least 20 cm (approx 8 in)

Canopy Module with Reflector Dish At least 1.5 m (approx 60 in or 5 ft)

Antenna of a Canopy 900 MHz Module At least 60 cm (approx 24 in)

8.3.1 Details of Exposure Separation Distances Calculations

A Canopy module with or without reflector dish has a maximum RMS power that does not exceed 0.34 W.

Currently certified 900 MHz antennas have an antenna gain of 10 dBi and 12 dBi, which means they are limited to a maximum RMS power of 0.4 W (26 dBm) or less to remain within the regulatory limit of 4 W (36 dBm) for the 900 MHz frequency band.

When installed with the above separation distances, the module’s RF field is within Health Canada limits for the general population; consult Safety Code 6, obtainable from Health Canada’s website http://www.hc-sc.gc.ca/rpb.

The applicable power density exposure limit is 10 Watt/m2 in the 2.4, 5.2, 5.4, and 5.7 GHz bands, and 6 Watt/m2 in the 900 MHz band, according to the US FCC OET Bulletin 65, the ICNIRP guidelines, and the Health Canada Safety Code 6. The corresponding compliance distances referenced above have been determined by assuming worst-case scenarios and defining a consistent compliance distance across all modules. The peak power density (S) in the far-field of a radio-frequency source with rms transmitter power P and antenna gain G at a distance d is

24 d

GPS

!

"=



The calculation results, recommended distances and power compliance margins for the various cases are shown in Table 12.

Table 12: Exposure Calculation Results and Power Compliance Margins Reflec-tor?

Frequency Band

Power Density Exposure Limit

Gain d (calculated)

Recom-mended Distance

Power Compliance Margin

No 900 MHz 6 Watt/m2 10 dBi 23 cm 60 cm (~24 in)

~7

Yes 2.4 GHz 10 Watt/m2 19 dBi (x80)

46 cm 1.5 m (~5 ft)

> 10

Yes 5.4, 5.7 GHz 10 Watt/m2 25 dBi (x316)

71 cm 1.5 m (~5 ft)

>4

No 2.4 GHz 10 Watt/m2 8 dBi (x6.3)

13 cm 20 cm (~8 in)

>2

No 5.2, 5.4, 5.7 GHz

10 Watt/m2 7 dBi (x5)

9 cm 20 cm (~8 in)

>5

The compliance distance is greatly overestimated in the reflector cases because the far-field equation neglects the physical dimension of the reflector, which is modeled as a point-source.

8.4 Legal Notices

8.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. THE FOLLOWING AGREEMENT IS A LEGAL AGREEMENT BETWEEN YOU (EITHER AN INDIVIDUAL OR ENTITY), AND MOTOROLA, INC. (FOR ITSELF AND ITS LICENSORS). THE RIGHT TO USE THIS PRODUCT IS LICENSED ONLY ON THE CONDITION THAT YOU AGREE TO THE FOLLOWING TERMS.

Now, therefore, in consideration of the promises and mutual obligations contained herein, and for other good and valuable consideration, the receipt and sufficiency of which are hereby mutually acknowledged, you and Motorola agree as follows:

Grant of License. Subject to the following terms and conditions, Motorola, Inc., grants to you a personal, revocable, non-assignable, non-transferable, non-exclusive and limited license to use on a single piece of equipment only one copy of the software contained on this disk (which may have been pre-loaded on the equipment)(Software). You may make two copies of the Software, but only for backup, archival, or disaster recovery purposes. On any copy you make of the Software, you must reproduce and include the copyright and other proprietary rights notice contained on the copy we have furnished you of the Software. Ownership. Motorola (or its supplier) retains all title, ownership and intellectual property rights to the Software and any copies,



including translations, compilations, derivative works (including images) partial copies and portions of updated works. The Software is Motorola’s (or its supplier's) confidential proprietary information. This Software License Agreement does not convey to you any interest in or to the Software, but only a limited right of use. You agree not to disclose it or make it available to anyone without Motorola’s written authorization. You will exercise no less than reasonable care to protect the Software from unauthorized disclosure. You agree not to disassemble, decompile or reverse engineer, or create derivative works of the Software, except and only to the extent that such activity is expressly permitted by applicable law.

Termination. This License is effective until terminated. This License will terminate immediately without notice from Motorola or judicial resolution if you fail to comply with any provision of this License. Upon such termination you must destroy the Software, all accompanying written materials and all copies thereof, and the sections entitled Limited Warranty, Limitation of Remedies and Damages, and General will survive any termination.

Limited Warranty. Motorola warrants for a period of ninety (90) days from Motorola’s or its customer’s shipment of the Software to you that (i) the disk(s) on which the Software is recorded will be free from defects in materials and workmanship under normal use and (ii) the Software, under normal use, will perform substantially in accordance with Motorola’s published specifications for that release level of the Software. The written materials are provided "AS IS" and without warranty of any kind. Motorola's entire liability and your sole and exclusive remedy for any breach of the foregoing limited warranty will be, at Motorola's option, replacement of the disk(s), provision of downloadable patch or replacement code, or refund of the unused portion of your bargained for contractual benefit up to the amount paid for this Software License.

THIS LIMITED WARRANTY IS THE ONLY WARRANTY PROVIDED BY MOTOROLA, AND MOTOROLA AND ITS LICENSORS EXPRESSLY DISCLAIM ALL OTHER WARRANTIES, EITHER EXPRESS OF IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. MOTOROLA DOES NOT WARRANT THAT THE OPERATION OF THE SOFTWARE WILL BE UNINTERRUPTED OR ERROR-FREE, OR THAT DEFECTS IN THE SOFTWARE WILL BE CORRECTED. NO ORAL OR WRITTEN REPRESENTATIONS MADE BY MOTOROLA OR AN AGENT THEREOF SHALL CREATE A WARRANTY OR IN ANY WAY INCREASE THE SCOPE OF THIS WARRANTY. MOTOROLA DOES NOT WARRANT ANY SOFTWARE THAT HAS BEEN OPERATED IN EXCESS OF SPECIFICATIONS, DAMAGED, MISUSED, NEGLECTED, OR IMPROPERLY INSTALLED. BECAUSE SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF IMPLIED WARRANTIES, THE ABOVE LIMITATIONS MAY NOT APPLY TO YOU.

Limitation of Remedies and Damages. Regardless of whether any remedy set forth herein fails of its essential purpose, IN NO EVENT SHALL MOTOROLA OR ANY OF THE LICENSORS, DIRECTORS, OFFICERS, EMPLOYEES OR AFFILIATES OF THE FOREGOING BE LIABLE TO YOU FOR ANY CONSEQUENTIAL, INCIDENTAL, INDIRECT, SPECIAL OR SIMILAR DAMAGES WHATSOEVER (including, without limitation, damages for loss of business profits, business interruption, loss of business information and the like), whether foreseeable or unforeseeable, arising out of the use or inability to use the Software or accompanying written materials, regardless of the basis of the claim and even if Motorola or a Motorola representative has been advised of the possibility of such damage. Motorola's liability to you for direct damages for any cause whatsoever, regardless of the basis of the form of the action, will be limited to the price paid for the Software that caused the damages. THIS LIMITATION WILL NOT APPLY IN CASE OF PERSONAL INJURY ONLY WHERE AND TO THE EXTENT THAT APPLICABLE LAW REQUIRES SUCH LIABILITY. BECAUSE SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, THE ABOVE LIMITATION MAY NOT APPLY TO YOU.



Maintenance and Support. Motorola shall not be responsible for maintenance or support of the software. By accepting the license granted under this agreement, you agree that Motorola will be under no obligation to provide any support, maintenance or service in connection with the Software or any application developed by you. Any maintenance and support of the Related Product will be provided under the terms of the agreement for the Related Product.

Transfer. In the case of software designed to operate on Motorola equipment, you may not transfer the Software to another party except: (1) if you are an end-user, when you are transferring the Software together with the Motorola equipment on which it operates; or 2) if you are a Motorola licensed distributor, when you are transferring the Software either together with such Motorola equipment or are transferring the Software as a licensed duly paid for upgrade, update, patch, new release, enhancement or replacement of a prior version of the Software. If you are a Motorola licensed distributor, when you are transferring the Software as permitted herein, you agree to transfer the Software with a license agreement having terms and conditions no less restrictive than those contained herein. You may transfer all other Software, not otherwise having an agreed restriction on transfer, to another party. However, all such transfers of Software are strictly subject to the conditions precedent that the other party agrees to accept the terms and conditions of this License, and you destroy any copy of the Software you do not transfer to that party. You may not sublicense or otherwise transfer, rent or lease the Software without our written consent. You may not transfer the Software in violation of any laws, regulations, export controls or economic sanctions imposed by the US Government.

Right to Audit. Motorola shall have the right to audit annually, upon reasonable advance notice and during normal business hours, your records and accounts to determine compliance with the terms of this Agreement.

Export Controls. You specifically acknowledge that the software may be subject to United States and other country export control laws. You shall comply strictly with all requirements of all applicable export control laws and regulations with respect to all such software and materials.

US Government Users. If you are a US Government user, then the Software is provided with "RESTRICTED RIGHTS" as set forth in subparagraphs (c)(1) and (2) of the Commercial Computer Software-Restricted Rights clause at FAR 52 227-19 or subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013, as applicable.

Disputes. You and Motorola hereby agree that any dispute, controversy or claim, except for any dispute, controversy or claim involving intellectual property, prior to initiation of any formal legal process, will be submitted for non-binding mediation, prior to initiation of any formal legal process. Cost of mediation will be shared equally. Nothing in this Section will prevent either party from resorting to judicial proceedings, if (i) good faith efforts to resolve the dispute under these procedures have been unsuccessful, (ii) the dispute, claim or controversy involves intellectual property, or (iii) interim relief from a court is necessary to prevent serious and irreparable injury to that party or to others.

General. Illinois law governs this license. The terms of this license are supplemental to any written agreement executed by both parties regarding this subject and the Software Motorola is to license you under it, and supersedes all previous oral or written communications between us regarding the subject except for such executed agreement. It may not be modified or waived except in writing and signed by an officer or other authorized representative of each party. If any provision is held invalid, all other provisions shall remain valid, unless such invalidity would frustrate the purpose of our agreement. The failure of either party to enforce any rights granted hereunder or to take action against the other party in the event of any breach hereunder shall not be deemed a waiver by that party as to subsequent enforcement of rights or subsequent action in the event of future breaches.



8.4.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 a product is found defective during the warranty period, Motorola will repair or replace the product with the same or a similar model, which may be a reconditioned unit, without charge for parts or labor.

8.5 Limit of Liability IN NO EVENT SHALL MOTOROLA BE LIABLE TO YOU OR ANY OTHER PARTY FOR ANY DIRECT, INDIRECT, GENERAL, SPECIAL, INCIDENTAL, CONSEQUENTIAL, EXEMPLARY OR OTHER DAMAGE ARISING OUT OF THE USE OR INABILITY TO USE THE PRODUCT (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF BUSINESS PROFITS, BUSINESS INTERRUPTION, LOSS OF BUSINESS INFORMATION OR ANY OTHER PECUNIARY LOSS, OR FROM ANY BREACH OF WARRANTY, EVEN IF MOTOROLA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. (Some states do not allow the exclusion or limitation of incidental or consequential damages, so the above exclusion or limitation may not apply to you.) IN NO CASE SHALL MOTOROLA’S LIABILITY EXCEED THE AMOUNT YOU PAID FOR THE PRODUCT.

canopy release 7.3 release notes issue 1 -...

Documents