LKT-BMAX-2-23BreezeMAX 4Motion Broadband Wireless Access System

4Motion ® System Manual Release 2.5M2 April 2010 P/N 215637 Document History 4Motionii System Manual Document History TopicDescriptionDate Issued Preliminary Release for Early Field Trials New System ManualJanuary 2008 Preliminary Release for BetaMay 2008 Release for GAJuly 2008 SDR Section 1.3.1.3 RemovedAugust 2008 TemplateChangedSeptember 2008 Power Feeder Section 1.3.4 Supported in release 2.5December 2008 7 MHz Channel Bandwidth Table 1-4, relevant sections in Chapter 4. Supported in release 2.5December 2008 Installing 4x2 ODU Section 2.1.4 Updated (including new installation options)December 2008 Installation recommendation Section 2.3.9.1 Recommendation on installing AUs in a 3-sector configuration December 2008 Trap Manager Section 2.1.5 Modified instructions for initial configurationDecember 2008 Operation and Administration Using the CLI Chapter 4 Updated to reflect NPU SW Version 2_5_1_8December 2008 Rate Limiting for the NPU Section 3.3.7.2 Rate limits are configurable only by the vendor. May 2009 Configuring ACLs Section 3.3.10 Updated default ACLs.May 2009 Configuring Performance Data Collection Section 3.3.13 Added support for new counters groups, updated names. May 2009 Configuring the Power Control Required C/N Level Parameters Section 3.8.6.2.2 Updated Defaults for cqi, cdma, qam64-1by2, qam64-2by3, qam64-3by4, qam64-5by6. May 2009 Managing the BS Keep-Alive Functionality Section 3.8.26 Updated commands’ syntax.May 2009 Managing the BS Idle Mode Parameters Section 3.8.28 New featureMay 2009 Document History 4Motioniii System Manual Managing BS Services Section 3.8.4 Added new parameters: paging-cycle, paging-offset, lm-traffic-idle-period, dl-def-rate. Updated range and default value for max-subburst. May 2009 Managing Ranging Parameters Section 3.8.23 The following tables were removed from operator CLI: Bandwidth Request, Handover Ranging, Initial Ranging, Periodic Ranging, Timing Correction. contbased-rsrvtimeout was removed from Ranging General table. May 2009 Airframe General Parameters Sections 3.8.16.2.1, 3.8.16.3.1, 3.8.16.5.1 Updated parameters: Removed: enable-ul-scrotation. Added: auto-diversity, auto-rx-enable. Corrected name: ul-duration. May 2009 Airframe Cyclic Delay Parameters Section 3.8.16.2.4 Updated descriptions.May 2009 Airframe Linear Delay Parameters Previousely Section 4.8.16.2.5 Updated descriptions.May 2009 Airframe Mapping Parameters Previousely Section 4.8.16.2.6 Updated descriptions.May 2009 Airframe Receive Parameters Previousely Section 4.8.16.2.7 Updated descriptions.May 2009 Airframe Downlink Diversity Parameters Section 3.8.16.2.3 Changed value range and default for the mimo parameter. May 2009 Airframe MIMO Parameters Sections 3.8.16.2.8, 3.8.16.3.5, 3.8.16.5.8 New Airframe parameters table.May 2009 Neighbor BS General Parameters Sections 3.8.13.2.1, 3.8.13.3.1, 3.8.13.7.1 Updated parameters: Removed: restartcount ucd-configchangecount and dcd-configchangecount must be set to 0. Added: paging-grp-id, nbr-strt-rng-codes. Updated range and description: preamble-idx May 2009 TopicDescriptionDate Issued Document History 4Motioniv System Manual Service Mapping Rule R1 Profile Parameters Sections 3.8.5.2.3, 3.8.5.6.3 Removed: sdu-length, sdu-size. All possible values of datadeliverytype are supported (including rTVR and nRTVR). Updated descriptions of cir, mir, latency. Updated range for cir, mir. May 2009 Service Mapping Rule R6 Profile Parameters Section 3.8.5.2.4, Updated range for cir, mir.May 2009 Feedback Allocation Parameters Section 3.8.7 Removed: pr-cdma, ert-poll-enable. Default value of ir-cdma changed from 20 to 2. Updated description of max-cqi. May 2009 Trigger Setup Parameters Section 3.8.10 Removed: hysteresismargin, timetotrigger Updated description of avgduration-rssi. May 2009 Neighbor BS Trigger Setup Parameters Sections 3.8.13.2.3, 3.8.13.3.3, 3.8.13.7.3 Removed: hysteresismargin, timetotriggerMay 2009 Rate Adaptation Parameters (was previously Section 4.8.20) All Rate Adaptation parameters were removed. May 2009 Scan Negotiation Parameters Section 3.8.11 Removed: all parameters except enable-modify. May 2009 Handover Negotiation at SBS (was previously 4.8.12) All Handover Negotiation at SBS parameters were removed. May 2009 UCD Parameters (was previously 4.8.15) All UCD parameters were removed.May 2009 DCD Parameters (was previously 4.8.16) All DCD parameters were removed.May 2009 Authentication Relay Parameters Section 3.8.18 Removed: nonauth-macctrlratethrshld, nonauth-pduratethrshld Updated the default value of maxeaproundsthrshld to 100. Updated the default value of suspendedeapprocthrshld to 10000. Updated the description. Updated the default value of activemsthrshld to 1024. May 2009 TopicDescriptionDate Issued Document History 4Motionv System Manual Handover Control Parameters Section 3.8.23 All configurable (read-write) parameters were removed. A new read-only parameter added: CINRReuse. May 2009 BS Management Alarm Thresholds (was previously 4.8.26) All BS Management Alarm Thresholds parameters were removed. May 2009 BS Alarm Threshold Parameters Section 3.8.24 Removed: dl-droppedpackets, unalloc-slots, dl-retransmissions, ul-retransmissions, dl-subburstdrop, ul-subburstdrop. Updated description, range and default for ul-mednoise, ul-99prcntnoise. Added: Be-exc-dl-drop-thr, rt-exc-dl-drop-thr, nrt-exc-dl-drop-thr, ugs-exc-dl-drop-thr, ert-exc-dl-drop-thr. May 2009 Managing the Site General Information Section 3.3.15.7 Added section on displaying the site general information. Address parameter value was changed to up to 70 characters. Removed: AsnName, Region. May 2009 Managing the Unique Identifier Section 3.3.15.8 Added section on displaying the site ID.May 2009 Displaying the Vendor Identifier Section 3.3.15.9 New feature.May 2009 AU Connectivity Parameters Sections 3.5.2.3, 3.5.3.3, 3.5.6.3 Added new parameters: service-ip, service-mask, service-next-hop. Updatated possible values of bearervlanid and the read…

Text truncated - open the document above for the full version.

Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion159 System Manual 3.3.8.2Managing QoS Classification Rules QoS classification rules classify packets into flows, based on the following parameters: „IP address of the host originating the traffic (the IP address assigned to the bearer, internal-management or external-management interface) „Layer 3 protocol indicating either TCP or UDP „Layer 4-source port for the application that needs to be marked (for example, FTP, Telnet, SNMP, MIP, or RADIUS) A class-map can be associated with each flow to define separate DSCP and/or VLAN priority bits for QoS handling of each flow. 1Enable the ACL configuration mode for ACL 199 (refer to Section 3.3.8.2.1). Syntax Description ParameterDescriptionPresenceDefault Value Possible Values [<class-map- num(1-65535) >] Indicates the identifier of the class-map for which configuration information is to be displayed. Do not specify a value for this parameter if you want to view the configuration information for all class-maps. OptionalN/A1-65535 Display Format (for each class-map if requested for all class-maps) Class map <class map number> ---------------------------------------------- CoS Value : <value> DSCP Value : <value> Command Modes Global command mode To configure a QoS classification rule: Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion160 System Manual 2You can now: »Configure one or more QoS classification rules (refer to Section 3.3.8.2.2) »Delete one or more QoS classification rules (refer to Section 3.3.8.2.3) »Terminate the ACL configuration mode (refer to Section 3.3.8.2.4) You can, at any time, enable/disable QoS marking (refer to Section 3.3.8.3) or view the configuration information for ACL 199 (refer to Section 3.3.8.4). 3.3.8.2.1Enabling the ACL Configuration Mode for ACL 199 To configure QoS classification rules for host-originating traffic, first enable the extended ACL 199 configuration mode. Run the following command to enable the extended ACL configuration mode for ACL 199. npu(config)# ip access-list {standard <access-list-number (1-99)> | extended <access-list-number (100-199)>} [name<string>] After you enable the ACL 199 configuration mode, you can configure one or several QoS classification rules, and associate them with the appropriate class-maps. IMPORTANT QoS classification rules can be associated only with ACL 199. IMPORTANT QoS classification rules can be added only to extended ACL 199 Command Syntax npu(config)# ip access-list {standard <access-list-number (1-99)> | extended <access-list-number (100-199)>} [ name <string>] Privilege Level 10 Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion161 System Manual 3.3.8.2.2Configuring a QoS Classification Rule You can configure the QoS classification rules for the ACL with respect the following parameters: „Source IP address for the host-originating application traffic „Application protocol (TCP or UDP) „L4 source port of the application traffic „QoS class-map identifier By default, there are 8 pre-configured QoS classification rules associated with the 8 pre-configured QoS class-maps: Syntax Description ParameterDescriptionPresenceDefault Value Possible Values extended <access-list-n umber (100-199)> Indicates the identifier of the extended ACL for which the ACL configuration mode is to be enabled. You must specify 199 to enable configuration of QoS classification rules. MandatoryN/A199 [ name <string>] Indicates the name of the ACL for which the ACL configuration mode is to be enabled. Note: If you do not specify the ACL name, the ACL number is used as the default ACL name. OptionalN/AString (upto 20 characters) Command Modes Global configuration mode Table 3-15: Pre-Configured QoS Classification Rules and Class-Maps IP InterfaceType of TrafficProtocolSource Port Class Map DSCP802.1p BearerRADIUSUDP1812177 Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion162 System Manual After configuring QoS classification rules for this ACL, enable QoS marking for this ACL. By default, QoS marking is disabled. For details, refer to Section 3.3.8.3. Run the following command to configure a QoS classification rule for this ACL: npu(config-ext-nacl)# qos-mark {{host <src-ip-address>} {{tcp | udp} srcport <short (1-65535)>} qosclassifier <short (1-65535)>} When you execute this command, a new QoS classification rule is added to the ACL for which the configuration mode is enabled. BearerMobileIP-AgentUDP434277 BearerWiMAX ASN Control Plane Protocol UDP2231377 Internal-ManagementOBSAI message exchange between NPU and AU UDP10009400 Internal-ManagementTrivial File Transfer Protocol UDP69500 External-ManagementTelnetTCP23600 External-ManagementSSH Remote Login Protocol TCP22700 External-ManagementSNMPUDP161800 IMPORTANT An error may occur if: „You have specified a source port that is not within the range, 1-65535. „The host IP address or class-map identifier that you have specified do not exist. Command Syntax npu(config-ext-nacl)# qos-mark {{host <src-ip-address>} {{tcp | udp} srcport <short (1-65535)>} qosclassifier <short (1-65535)>} Privilege Level 10 Table 3-15: Pre-Configured QoS Classification Rules and Class-Maps IP InterfaceType of TrafficProtocolSource Port Class Map DSCP802.1p Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion163 System Manual 3.3.8.2.3Deleting a QoS Classification Rule To delete a QoS classification rule for an ACL, run the following command: npu(config-ext-nacl)# no qos-mark {{host <src-ip-address>} {{tcp | udp} srcport <short (1-65535)>} qosclassifier <short (1-65535)>} Syntax Description ParameterDescriptionPresenceDefault Value Possible Values {host <src-ip-addres s>} Indicates the IP address of the host interface that generates the traffic for which this classification rule is to be configured. Specify the IP address that you have assigned to the internal-management, ex…

Text truncated - open the document above for the full version.

Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion359 System Manual „NPU Counters Groups (per-NPU counters): »NPU DATA port »NPU MGMT port »NPU CASCADE port »AU ports »NPU internal-management interface »NPU external-management interface »NPU local-management interface »NPU bearer interface »Service Flow Authorization functionality »Data path functionality »AAA client functionality »Authenticator function »Context function »DHCP proxy functionality »DHCP relay functionality »DHCP server functionality »MS state change functionality Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion360 System Manual „AU Counters Groups (per-BS counters) »De-Registration »Integrity »Mobility »Network Entry (NE) »Traffic »Utilization »“Idle Mode” »“Fast Feedback CQI Handling” »“Ack/Nack Channel Handling” »“End Transaction Update” »“DL Frame Data Zone Histograms” »“TxR1 Net Traffic” »“RxR1 Net Traffic” »“TxR1 Total Traffic” »“RxR1 Total Traffic” »“DL HARQ Sub-Bursts Drops” »“DL HARQ Transmissions” »General »All MS Basic Mode »Specific MS Advanced Mode For details on the performance data counters collected for each group refer to the relevant 4Motion Performance Management document. You can specify the group for which performance data is to be stored and collected. Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion361 System Manual The data is stored in an XML file called, prf_<SiteID>_yyyymmddhhmm.xml.gz in the path,/tftpboot/management/performance. The system maintains this data for a maximum of 24 hours after which it is deleted. It is recommended that you periodically make a backup of these files on an external server. You can enable/disable collection of performance data for each group separately. This section describes: „“Enabling Collection and Storage of Historical Performance Data” on page 361 „“Disabling Collection and Storage of Performance Data” on page 366 „“Displaying the Status of Performance Data Collection” on page 368 3.3.13.1Enabling Collection and Storage of Historical Performance Data 4Motion collects and stores performance data for the a number of system groups (refer to Section 3.3.13). To enable collection and storage of performance data for a group, run the following command: To enable collection and storage of performance data for an NPU counters group: npu(config)# pm-group enable npu {BckhlPort | MgmtPort | CascPort | AuPortTable | IntMgmtIf | ExtMgmtIf | LclMgmtIf | BearerIf | Sfa | DatapathFn | AaaClient | Authenticator | ContextFn | ProxyDhcp | RelayDhcp | ServerDhcp | MsStateChangeFn} To enable collection and storage of performance data for an AU counters group: npu(config)# pm-group enable au { BsDeRegistrationTable | BsIntegrity | BsMobilityTable | BsNetworkEntryTable | BsTrafficTable | BsUtilizationTable | BsIdleModeTable | BsFastFeedbackCQIHandlingTable | BsAckNackChannelHandlingTable | BsEndTransactionUpdateTable | BsDlDataZoneFrameHistogramsTable | BsTxR1NetTrafficTable | BsRxR1NetTrafficTable | BsTxR1TotalTrafficTable | BsRxR1TotalTrafficTable | BsDLHARQSbDropsTable | BsDLHARQTransmissionTable | BsGeneral | Bsallmsbasicmode | Bsspecificmsadvancedmode} Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion362 System Manual You can display whether performance data collection is currently enabled or disabled for a particular group. For details, refer Section 3.3.13.3. The parameters in this command correspond to the groups listed in the following tables: NOTE Using this command, you can enable collection of performance data for only one group at a time. For example, run the following command if you want to enable performance data collection and storage for the data path function: npu(config)# pm-group enable npu DatapathFn Table 3-25: NPU Counters Groups for which Performance Data can be Collected Parameter NameRefers to... BckhlPortNPU DATA port MgmtPortNPU MGMT port CascPortNPU CASCADE port AuPortTableAU ports IntMgmtIfNPU internal-management interface ExtMgmtIfNPU external-management interface LclMgmtIfNPU local-management interface BearerIfNPU bearer interface SfaService flow authorization DatapathFnData path functionality AaaClientAAA client functionality AuthenticatorAuthenticator function ContextFnContext function ProxyDhcpDHCP proxy functionality RelayDhcpDHCP relay functionality ServerDhcpDHCP server functionality MsStateChangeFnMS state change functionality Table 3-26: AU Counters Groups for which Performance Data can be Collected Parameter NameRefers to... BsDeRegistrationTable De-Registration BsIntegrity Integrity Chapter 3 - Operation and Administration Using the CLINPU Configuration 4Motion363 System Manual For example, run the following command if you want to enable performance data collection for the NPU DATA port: npu(config)# pm-group enable npu BckhlPort When you run this command, collection and storage of performance data is enabled for the DATA port counters. After you have enabled collection and storage of performance data is fetched every quarter of an hour. BsMobilityTable Mobility BsNetworkEntryTable Network Entry BsTrafficTable Traffic BsUtilizationTable Utilization BsIdleModeTable Idle Mode BsFastFeedbackCQIHandlingTable Fast Feedback CQI Handling BsAckNackChannelHandlingTable Ack/Nack Channel Handling BsEndTransactionUpdateTable End Transaction Update BsDlDataZoneFrameHistogramsTable DL Frame Data Zone Histograms BsTxR1NetTrafficTable TxR1 Net Traffic BsRxR1NetTrafficTable RxR1 Net Traffic BsTxR1TotalTrafficTable TxR1 Total Traffic BsRxR1TotalTrafficTable RxR1 Total Traffic BsDLHARQSbDropsTable DL HARQ Sub-Bursts Drop BsDLHARQTransmissionTable DL HARQ Transmissions BsGeneral General Bsallmsbasicmode All MS Basic Modec Bsspecificmsadvancedmode Specific MS Advanced Mode NOTE When you enable collection of performance data collection, the data is stored in a file called, prf_<SiteID>_yyyymmddhhmm.xml.gz in the path, /tftpboot/management/perfo…

Text truncated - open the document above for the full version.

BreezeMAX 4Motion™ Federal Communications Commission 7435 Oakland Mills Road Columbia, MD 21046 Gentlemen: This letter serves as an official request for permanent confidentiality under FCC Rule Section 0.457 and 0.459. Alvarion would like the following documents regarding this submission for FCC ID: LKT-BMAX-2-23 to be kept confidential: 1. Block Diagram. 2. Schematics. 3. Operational description. 4. Part List The above material contains trade secrets or technical data, which would customarily be guarded from competitors. We do not want these documents to be accessible to the general public. Sincerely, Sincerely, AVNER RUTA

BreezeMAX 4Motion™ Alvarion Ltd. BreezeCOM and Floware unite 21a HaBarzel St. Tel Aviv, 69710 Israel Main Line / Fax: 972 3 645 6262 / 6222 www.alvarion.com July 27, 2010 BreezeMAX 4M 2300MHz system FCC ID: LKT-BMAX-2-23 Frequency and power determination before shipment: Before the product shipment from the factory, the units pass automatic calibration sequence tests where the unit is calibrated (including power out) and frequency is tested. Base station installation. The user configures the unit according to licensed frequencies (user may have several frequencies)

Test Report No. 9012332795 Applicant: ALVARION Ltd. Equipment Under Test: BreezeMAX 4 Motion Broadband Wireless Access System Base station. From The Standards Institution Of Israel Industry Division Electronics & Telematics Laboratory EMC Section ACLASS Accreditation Services Certificate Number: AT-1359 Test report No: 9012332795 Page 1 of 44 Pages Title: BreezeMax 4Motion Broadband Wireless Access System Model : ODU-2305-2360-000N-38-2x2-Y-0 FCC ID: LKT-BMAX-2-23 Table of Contents 1. Applicant information .............................................................................. 2 2. Test performance ..................................................................................... 2 3. Summary of test:...................................................................................... 3 4. Equipment under test description. ......................................................... 4 4.1 General description ................................................................................. 4 4.2 EUT configuration. ................................................................................... 5 5. Test results ............................................................................................... 6 5.1 Transmitter characteristics .................................................................... 6 5.1.1 Occupied bandwidth according to § 2.1049........................................... 6 5.1.2 Peak output power test § 27.50 (h)(1)(ii)................................................. 9 5.1.3 Spurious emissions at antenna terminal § 27.53 ................................ 12 5.1.4 Radiated emissions test according to §§ 2.1053, 27.53 ...................... 26 5.1.5 Frequency stability test according to § 27.54...................................... 37 APPENDIX A Photographs ............................................................................... 38 APPENDIX B Test equipment used .................................................................. 40 APPENDIX C General information.................................................................... 44 Test report No: 9012332795 Page 2 of 44 Pages Title: BreezeMax 4Motion Broadband Wireless Access System Model : ODU-2305-2360-000N-38-2x2-Y-0 FCC ID: LKT-BMAX-2-23 1. Applicant information Applicant: Alvarion Ltd Address: 21A Habarzel str, Tel-Aviv, 69710, Israel Sample for test selected by: The customer The date of test: 20 - 27 June 5 July 2010 Equipment under test information Description of Equipment Under Test (EUT ): Transmitter BreezeMAX 2300 Model: ODU-2305-2360-000N-38-2x2-Y-0 Serial Number: NA Manufactured by: Alvarion Ltd 2. Test performance Location: SII EMC Section Purpose of test: Apparatus compliance verification in accordance with emission requirements Test specifications: 47CFR part 15, part 27, part 2 §§ 2.1049, 2.1053, part 1 §1.1310 This Test Report contains 44 pages and may be used only in full. This Test Report applies only to the specimen tested and may not be applied to other specimens of the same product. Test report No: 9012332795 Page 3 of 44 Pages Title: BreezeMax 4Motion Broadband Wireless Access System Model : ODU-2305-2360-000N-38-2x2-Y-0 FCC ID: LKT-BMAX-2-23 3. Summary of test: The EUT was found to be in compliance with requirements of: 47CFR part 27, §§ 27.50, 27.53, 27.54 and part 2 §§ 2.1049 Transmitter characteristics Subclasses Transmitter characteristics Occupied bandwidth 2.1049 Peak output power 27.50 Spurious emissions at antenna terminal 27.53 Spurious emissions radiated 27.53 Frequency stability 27.54 Test performed by: Mr. Michael Feldman test technician Test report prepared by: Mr. Michael Feldman test technician Test report approved by: Mr. Yuri Rozenberg Head of EMC Branch Measurement uncertainty. Were relevant, the following measurement uncertainty level have been estimated for tests performed on the EUT as specified in CISPR 16-4-2: This uncertainty represents an expended uncertainty expressed at approximately the 95% confidence level using a coverage factor of k=2. Test description Expanded uncertainty Radiated emissions in the open field test site at 3 m measuring distance: 30 MHz – 1.0 GHz 1.0 GHz – 18 GHz 2 Uc (E) = ± 4.32 dB 2 Uc (E) = ± 4.47 dB Test report No: 9012332795 Page 4 of 44 Pages Title: BreezeMax 4Motion Broadband Wireless Access System Model : ODU-2305-2360-000N-38-2x2-Y-0 FCC ID: LKT-BMAX-2-23 4. Equipment under test description. *The customer provided description. 4.1 General description BreezeMax 4M 2.3 GHz is digital modulated TDD system. The frequency range of the BMAX 4M 2.3 GHz is 2300 MHz up to 2400 MHz Nominal output power is 38 dBm at transmitter antenna connector. The system contains a base station unit and a subscriber unit. The basic system configuration is a two-box configuration that contains: 1. Indoor unit that contains the IF unit, digital card, power supply and modem. 2. Outdoor unit contain the radio and digital control section unit. The following describes the transmit path and receive path of the BMAX 4M 2300 MHz AU ODU Basic + HPA (for 2x2 ODU configuration). The outdoor unit (ODU) is a high-power, multi-carrier radio unit that connects to one or more external antennas. The ODU is designed to provide high system gain and interference robustness utilizing high transmit power and low noise figure. It is HW-ready for supporting a bandwidth of up to 20 MHz, enabling future options. Such as increased capacity through the use of a multiplexer or wider frequency channels EUT technical characteristics Technical characteristics of transmitter. Note Stand-alone/fixed use Always at distance at least 2 m from the people and public area. Assigned frequency range 2305 – 2320 MHz and 2345 – 2360 MHz 2305 – 2315 MHz Declare frequency range 2350 – 2360 MHz 2307.5 - 2312.5; 2352.5 - 2357.5 MHz 5 MHz EBW Operating frequencies 2310 and 2355 MHz 10 MHz EBW Antenna connection N-Type connector Professional installation Transmitter 99% power bandwidth 5 MHz…

Text truncated - open the document above for the full version.

Conducted measurements Measurement of radiated emission Measurement of radiated emission