all | frequencies |
|
|
|
|
|
|
|
|
|
|
exhibits | applications |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
manuals | photos |
app s | submitted / available | |||||||
---|---|---|---|---|---|---|---|---|
1 2 3 4 5 6 7 |
|
Antenna installation guide | Users Manual | 2.30 MiB | April 09 2014 / August 10 2014 | |||
1 2 3 4 5 6 7 |
|
HW guide revised | Users Manual | 3.24 MiB | April 09 2014 / August 10 2014 | |||
1 2 3 4 5 6 7 |
|
Manual | Users Manual | 4.45 MiB | ||||
1 2 3 4 5 6 7 |
|
Software guide1 | Users Manual | 3.28 MiB | / August 10 2014 | |||
1 2 3 4 5 6 7 |
|
software guide2 | Users Manual | 2.66 MiB | / August 10 2014 | |||
1 2 3 4 5 6 7 |
|
user manual | Users Manual | 586.71 KiB | February 04 2014 | |||
1 2 3 4 5 6 7 | Users Manual | June 05 2014 / October 08 2014 | ||||||
1 2 3 4 5 6 7 | Users Manual | June 05 2014 / October 08 2014 | ||||||
1 2 3 4 5 6 7 |
|
EUT photo | External Photos | 285.22 KiB | / August 10 2014 | |||
1 2 3 4 5 6 7 |
|
antenna photo | External Photos | 459.31 KiB | / August 10 2014 | |||
1 2 3 4 5 6 7 | Cover Letter(s) | |||||||
1 2 3 4 5 6 7 | Cover Letter(s) | |||||||
1 2 3 4 5 6 7 | Cover Letter(s) | |||||||
1 2 3 4 5 6 7 | Test Report | |||||||
1 2 3 4 5 6 7 | Test Report | |||||||
1 2 3 4 5 6 7 | Test Report | |||||||
1 2 3 4 5 6 7 | Test Report | |||||||
1 2 3 4 5 6 7 | Test Report | |||||||
1 2 3 4 5 6 7 | Test Report | |||||||
1 2 3 4 5 6 7 | Test Setup Photos | |||||||
1 2 3 4 5 6 7 | Cover Letter(s) | |||||||
1 2 3 4 5 6 7 | Cover Letter(s) | |||||||
1 2 3 4 5 6 7 | Cover Letter(s) | |||||||
1 2 3 4 5 6 7 | Test Report | |||||||
1 2 3 4 5 6 7 | Test Report | |||||||
1 2 3 4 5 6 7 | RF Exposure Info | |||||||
1 2 3 4 5 6 7 | Test Setup Photos | |||||||
1 2 3 4 5 6 7 |
|
Antenna list of max gain | Parts List/Tune Up Info | 5.95 KiB | May 06 2014 / August 10 2014 | |||
1 2 3 4 5 6 7 |
|
C2PC letter | Cover Letter(s) | 25.40 KiB | May 06 2014 / August 10 2014 | |||
1 2 3 4 5 6 7 | Cover Letter(s) | |||||||
1 2 3 4 5 6 7 |
|
Confidential Letter Revised | Cover Letter(s) | 16.21 KiB | / August 10 2014 | |||
1 2 3 4 5 6 7 | Attestation Statements | June 05 2014 / October 08 2014 | ||||||
1 2 3 4 5 6 7 | Attestation Statements | September 04 2014 / October 08 2014 | ||||||
1 2 3 4 5 6 7 |
|
EIRP compliance declaration revised2 | Attestation Statements | 2.07 MiB | April 09 2014 / August 10 2014 | |||
1 2 3 4 5 6 7 |
|
antenna pattern of GTT-AC-05-001 | Parts List/Tune Up Info | 22.15 KiB | January 09 2014 / August 10 2014 | |||
1 2 3 4 5 6 7 |
|
antenna pattern of MA-WA55-30 | Parts List/Tune Up Info | 27.79 KiB | January 09 2014 / August 10 2014 | |||
1 2 3 4 5 6 7 |
|
antenna pattern of MA-WB55-20 | Parts List/Tune Up Info | 27.60 KiB | January 09 2014 / August 10 2014 | |||
1 2 3 4 5 6 7 |
|
antenna pattern of SAA08-220570 | Parts List/Tune Up Info | 32.05 KiB | January 09 2014 / August 10 2014 | |||
1 2 3 4 5 6 7 | software security | SDR Software/Security Inf | June 05 2014 | confidential | ||||
1 2 3 4 5 6 7 | Test Report | / August 10 2014 | ||||||
1 2 3 4 5 6 7 | Test Report | |||||||
1 2 3 4 5 6 7 | Cover Letter(s) | |||||||
1 2 3 4 5 6 7 | Cover Letter(s) | |||||||
1 2 3 4 5 6 7 | Test Setup Photos | |||||||
1 2 3 4 5 6 7 | External Photos | |||||||
1 2 3 4 5 6 7 | External Photos | |||||||
1 2 3 4 5 6 7 | Test Report | |||||||
1 2 3 4 5 6 7 | Cover Letter(s) | |||||||
1 2 3 4 5 6 7 | Test Report | |||||||
1 2 3 4 5 6 7 | Internal Photos | |||||||
1 2 3 4 5 6 7 | RF Exposure Info | |||||||
1 2 3 4 5 6 7 | Cover Letter(s) | |||||||
1 2 3 4 5 6 7 | Test Setup Photos | |||||||
1 2 3 4 5 6 7 | Cover Letter(s) | |||||||
1 2 3 4 5 6 7 | Cover Letter(s) | |||||||
1 2 3 4 5 6 7 | Cover Letter(s) | |||||||
1 2 3 4 5 6 7 | Cover Letter(s) | February 04 2014 | ||||||
1 2 3 4 5 6 7 | Internal Photos | February 04 2014 | ||||||
1 2 3 4 5 6 7 | Cover Letter(s) | February 04 2014 | ||||||
1 2 3 4 5 6 7 | Cover Letter(s) | February 04 2014 | ||||||
1 2 3 4 5 6 7 | RF Exposure Info | February 04 2014 | ||||||
1 2 3 4 5 6 7 | Test Report | February 04 2014 | ||||||
1 2 3 4 5 6 7 | Cover Letter(s) | February 04 2014 | ||||||
1 2 3 4 5 6 7 | External Photos | February 04 2014 | ||||||
1 2 3 4 5 6 7 | ID Label/Location Info | February 04 2014 | ||||||
1 2 3 4 5 6 7 | Test Report | February 04 2014 | ||||||
1 2 3 4 5 6 7 | Test Report | January 04 2014 | ||||||
1 2 3 4 5 6 7 | ID Label/Location Info | January 04 2014 |
1 2 3 4 5 6 7 | Antenna installation guide | Users Manual | 2.30 MiB | April 09 2014 / August 10 2014 |
Tsunami 800 and 8000 Series
(Point-to-point and Point-to-multipoint Products) Antenna Installation Guide Products Covered
--> Tsunami Multipoint
- MP-820-BSU-100
- MP-820-SUA-50+
- MP-8100-BSU and MP-8200-BSU
- MP-8100-SUA
- MP-8200-SUA
- MP-8160-BSU
- MP-8160-SUA
--> Tsunami Quickbridge
- QB-8100-EPA
- QB-8100-LNK
- QB-8200-EPA
- QB-8200-LNK Copyright 2013 Proxim Wireless Corporation, Milpitas, CA. All rights reserved. Covered by one or more of the following U.S. patents: 5,231,634;
5,875,179; 6,006,090; 5,809,060; 6,075,812; 5,077,753. The content described herein are copyrighted with all rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form by any means without the written permission of Proxim Wireless Corporation. Trademarks Tsunami, Proxim, and Proxim logo are the trademarks of Proxim Wireless Corporation. All other trademarks mentioned herein are the property of their respective owners. Disclaimer Proxim reserves the right to revise this publication and to make changes in content from time-to-time without obligation on the part of Proxim to provide notification of such revision or change. Proxim may make improvements or changes in the product(s) described in this guide at any time. When using these device, basic safety precautions should always be followed to reduce the risk of fire, electric shock and injury to persons. Tsunami 800 and 8000 Series - Antenna Installation Guide Documentation Version: 1.8 P/N 77036, February 2014 Tsunami 800 and 8000 Series - Hardware Installation Guide 2 Preface. 4 1 Antenna Installation . 7 Safety Precautions . 7 Installation Process . 8 Required Materials . 9 Determining the Optimal Antenna Placement . 9 Mounting the Antenna . 10 Antenna Mast Requirements. 11 Connecting the Cables. 11 Connecting the Antenna Cable . 12 Connecting the Surge Arrestor and Ethernet / Power cables . 13 Grounding the System . 14 Sealing the Cable Connectors . 14 Antenna Polarization . 18 Aligning the Antenna . 19 Audible Antenna Alignment. 19 Antenna Alignment using CLI Commands . 20 2 Measuring Signal Performance. 21 Introduction . 21 Determining the Range . 21 Fresnel Zone . 22 Fresnel Zone Calculation . 22 Clearance Factor . 23 Calculations . 25 Calculating Link Budget . 25 3 Statement of Warranty . 29 4 Technical Services and Support . 31 Tsunami 800 and 8000 Series - Antenna Installation Guide 3 Preface Preface This chapter contains information on the following:
About this Guide Who Should Use This Guide Documentation Conventions Related Documents About this Guide The guide gives an insight on how to set up and install the outdoor antenna(s) for the Tsunami 800 and 8000 series products that are tabulated below:
Product(s) MP-820-BSU-100 MP-820-SUA-50+
MP-8100-BSU MP-8100-SUA MP-8200-BSU MP-8200-SUA MP-8160-BSU Description The MP-820 Base Station unit, is a flexible wireless outdoor product that operates in 5.150 5.925 GHz frequency band. This connectorized device comes with 2x2 MIMO radio and two N-Type connectors to connect external antennas. It provides an aggregate throughput of 100 Mbps. The MP-820 Subscriber unit, is a flexible wireless outdoor product that operates in 5.150 to 5.925 GHz frequency band. This connectorized device comes with a 2x2 MIMO radio and two N-Type connectors to connect external antennas. It provides an aggregate throughput of 50 Mbps, license upgradable to 100 Mbps. The Tsunami MP-8100 Base Station unit, is a flexible wireless outdoor product that operates in 2.3 2.5 and 4.9 6.0 GHz frequency band. This connectorized device comes with a 3x3 MIMO radio and three N-Type connectors to connect external antennas. The Tsunami MP-8100 Subscriber unit, is a flexible wireless outdoor product that operates in 2.3 2.5 and 4.9 6.0 GHz frequency band. This connectorized device comes with a 3x3 MIMO radio and three N-Type connectors to connect external antennas. The Tsunami MP-8200 Base Station unit, is a flexible wireless outdoor product that operates in 4.900 to 5.925 GHz frequency band. This connectorized device comes with a 3x3 MIMO high power radio and three N-Type connectors to connect external antennas. The Tsunami MP-8200 Subscriber unit, is a flexible wireless outdoor product that operates in 4.900 to 5.925 GHz frequency band. This connectorized device comes with a 3x3 MIMO high power radio and three N-Type connectors to connect external antennas. The Tsunami MP-8160 Base Station unit, is a flexible outdoor product that operates in 5.9 6.4 GHz frequency band. This connectorized device comes with a high power 2x2 MIMO radio and two N-Type connectors to connect external antennas. Tsunami 800 and 8000 Series - Antenna Installation Guide 4 Preface MP-8160-SUA QB-8100-EPA QB-8100-LNK QB-8200-EPA The Tsunami MP-8160 Subscriber unit, is a flexible outdoor product that operates in 5.9 6.4 GHz frequency band. This connectorized device comes with a high power 2x2 MIMO radio and two N-Type connectors to connect external antennas. The Tsunami QB-8100-EPA QuickBridge operates in 2.3 2.5 and 4.9 6.0 GHz frequency band. This connectorized device comes with a 3x3 MIMO radio and three N-Type connectors to connect external antennas. A pair of Tsunami QB-8100-EPA devices form a link. The Tsunami QB-8200-EPA QuickBridge operates in 4.900 5.925 GHz frequency band. This connectorized device comes with a 3x3 MIMO high power radio and three N-Type connectors to connect external antennas. QB-8200-LNK A pair of Tsunami QB-8200-EPA devices form a link. Who Should Use This Guide At a basic level, the person referring to this guide should meet the following pre-requisites:
A professional experienced in mounting outdoor antennas, installing surge arrestors, installing and configuring network components. Have a working knowledge on installation procedures for network operating systems like Microsoft Windows. However, Proxim recommends only a qualified antenna installation professional to install the antennas and follow the following guidelines:
The outdoor antennas should be mounted only on an antenna tower, on a roof, or on the external surface of the building. The site pre-requisites must be verified by the professional, familiar with the applicable national electrical code and with other regulations governing this type of installation, within the country of use. If you are not aware about the regulations that apply in your country, contact Proxims Technical Services and Support. While installing the outdoor antennas, ensure to comply with the local radio regulations and use the correct cable type and surge arrestor. Local radio regulations or legislation may impose restrictions on the use of specific combinations of:
Low - loss antenna cables and outdoor antennas. Selected radio channels that are connected to specific outdoor antennas. Tsunami 800 and 8000 Series - Antenna Installation Guide 5 Preface Documentation Conventions Icon Representation Name Image Meaning Note A special instruction that draws attention of a user. Important A note of significant importance that a user should be aware of. Caution A warning that cautions a user of the possible danger. Related Documents In addition to this guide, you can refer to the following documents for Tsunami 800 and 8000 series products, that are available at Proxims support site http://my.proxim.com. Quick Installation Guide (QIG) - A quick reference guide that provides essential information to install and configure the device. Hardware Installation Guide - A guide that provides an overview about the installation methods and hardware specifications of the device. Software Management Guide - A guide that gives jump-start working knowledge on the step-by-step procedure to configure, manage and monitor the device, by using Web Interface. Reference Guide - A guide that provides instructions on how to configure, manage and monitor the device by using Command Line Interface. Safety and Regulatory Compliance Guide - A guide that provides country specific safety and regulatory norms to be followed while installing the devices. Recommended Antennas Guide - A guide that gives insight on the recommended antennas for the device, along with the antenna specifications. Tsunami 800 and 8000 Series - Antenna Installation Guide 6 1 Antenna Installation This chapter contains information on the following:
Safety Precautions Installation Process Required Materials Determining the Optimal Antenna Placement Mounting the Antenna Antenna Mast Requirements Connecting the Cables Connecting the Antenna Cable
- Antenna Cable Routing Connecting the Surge Arrestor and Ethernet / Power cables Grounding the System
- Grounding the Antennas Sealing the Cable Connectors Antenna Polarization Aligning the Antenna Audible Antenna Alignment Antenna Alignment using CLI Commands 1.1 Safety Precautions Listed below are the safety precautions to be satisfied, prior to the outdoor antennas installation:
Outdoor antennas and antenna cables (good conductors of electricity) should be installed properly to avoid the transients or electrostatic discharges (that occur due to lightning during thunderstorm) from damaging your equipment and causing personal injury or death to the persons touching the exposed metal connectors of the equipment. When installing, disconnecting, or replacing one of the cable components, ensure that each of the exposed metal connectors of the antenna cabling system are grounded locally. Do not install the antenna, where there is a possibility of contact with the high-voltage arc-over from the power cables or service drops to the buildings. Ensure that the antenna-mast or antenna-tower are not close by any power line, during the installation or removal of antennas. Apply a Danger label on a plainly visible area of the antenna support structure. Do not climb the rooftops during a thunderstorm, in wet or windy conditions, or on the equipment installation area which is covered with ice or snow. Do not touch the antennas, surge arrestors, or antenna cables during a thunderstorm. Install the antennas at a safe distance (at least twice the height of the antenna-mast plus the antenna) from power lines or telephone lines. Mount the antennas at a safe distance, avoiding any human contact during the normal equipment operation. Ensure that the human proximity to the antenna is atleast 50 cm (8 inches) high, avoid the possibility of exceeding the FCC radio frequency exposure limits, during the normal operation of the equipment. Tsunami 800 and 8000 Series - Antenna Installation Guide 7 Antenna Installation Verify that the low-loss antenna cable used to connect the antenna with the surge arrestor, or the ethernet cable used to connect the surge arrestor, are at least 1 m (3 ft.) away from any high voltage current cable. Check whether the antenna mast and its guy wires or wall bracket are positioned correctly and secured properly to the roof or walls. Also, ensure that the base area, where the antenna-mast is mounted is weatherproofed. Ensure, that the grounding system for the antenna mast and the surge arrestor have been installed. The grounding system must comply with the local electrical code and other requirements. See Grounding the Antennas Always consult an experienced electrician to assure that the antenna mast, surge arrestor, and the equipment hardware are grounded properly. The antenna cable between the antenna and the surge arrestor should be grounded. Ensure that the exposed metal connector of the cable is grounded locally, if the cable is disconnected at one end (disconnected to replace the surge arrestor). 1.2 Installation Process Follow the following step-by-step procedure to install outdoor antennas:
1. Ensure that all the materials, essential to install the outdoor antennas are acquired. See Required Materials. 2. Once you have acquired all the required materials, refer Quick Installation Guide (that comes along with your product) to mount the outdoor equipment and begin the outdoor antenna installation. 3. Verify the optimal antenna placement, maintaining a clear line-of-sight. See Determining the Optimal Antenna Placement. 4. Mount the antenna to the support structure, following the guidelines as described in Mounting the Antenna. 5. Verify that the device, support structure for antenna (antenna-mast) and entire cable set-up for the antenna are connected properly. See Connecting the Cables. 6. Connect the antenna cable to the antenna. See Connecting the Antenna Cable. 7. Ensure that the cabling of ethernet / power cables and the surge arrestor is proper. See Connecting the Surge Arrestor and Ethernet / Power cables 8. Ensure that the antennas are grounded properly to the grounding system, satisfying the local electrical code requirements. See Grounding the Antennas 9. Once the antenna is properly positioned, grounded and the outdoor cable setup is verified, secure all the cables and use weatherproofing tape to seal all the outdoor connectors. See Sealing the Cable Connectors. 10. Make sure that the outdoor antennas at both the ends maintain the same antenna polarizations. See Step 4: Next, wrap a layer of the butyl mastic tape on the adhesive side. 11. Align the antennas to establish a wireless link with a better throughput, by using device antenna alignment utilities like Audible Antenna Alignment and Antenna Alignment using CLI commands. See Aligning the Antenna.
: For easy outdoor antenna installation, note the following:
Go through the Safety Precautions. Read all the requirements outlined in this chapter. See Required Materials. Familiarize yourself with the antenna and the radio-specific mounting instructions, prior to climbing any roof or ladder. Verify that you have arranged all safety measures for outdoor installation or rooftop installation. See Safety Precautions. Test all the equipment before beginning the actual rooftop installation, to determine if all the required equipment is functioning properly. Tsunami 800 and 8000 Series - Antenna Installation Guide 8 Install the grounding system for the antenna mast, device, and surge arrestor before connecting the cables. This protects your system against lightning strikes during installation. When you remove or relocate the antenna, verify the Required Materials and Safety Precautions, before you restart the installation process, and follow the above steps in exactly the reverse order. Antenna Installation 1.2.1 Required Materials The outdoor installation of the equipment and the antennas, require the following:
An outdoor radio unit. An outdoor antenna, supporting the local electrical code. A low-loss antenna cable.
: We recommend you to use a coaxial antenna cable (P/N CBL-5054-600-6), that is available with your distributor. Antenna mast or wall bracket for the antenna/device. A grounding system that meets the local electrical code. See Grounding the System Weatherproofing kit for sealing all the cable connections. See Sealing the Cable Connectors Tools and material to mount the antenna. See Mounting the Antenna Tape or wraps to attach the antenna cable to the mast. Ethernet cable (RJ 45 cable / CAT5e or CAT6 cable) with waterproof cap. Proper tools for system installation. Ethernet Surge Arrestor and Surge Protector (RF-cable). See Connecting the Surge Arrestor and Ethernet / Power cables Ensure that you have acquired all the materials listed above, to begin with the outdoor antenna installation. Refer to the Quick Installation Guide, that comes along with your product, for details on mounting the outdoor equipment. 1.2.2 Determining the Optimal Antenna Placement To achieve the maximum throughput, the outdoor antenna must have clear line-of-sight with the antenna at the other end. The outdoor antennas are said to have a clear line-of-sight, when there are:
No obstacles in the direct path between the antennas (antenna beam) No obstacles within a defined zone around the antenna beam Although, the radio signal can work well without the clear line-of-sight in urban environments, where the signal is transported by reflection rather than transporting it directly along the obstacles. The following figure shows some typical examples of obstacles you must avoid in urban environments, for the directional antenna to operate effectively. Tsunami 800 and 8000 Series - Antenna Installation Guide 9 Antenna Installation Figure 1-1 Obstacles to be avoided : (a) Neighbouring Buildings (b) Tall Trees (c) Power Lines To minimize the signal interference or reflections due to obstacles, note the following guidelines:
Mount the antenna as high as possible above the ground to allow maximum clearance. In open areas, ground is the actual surface of the earth. In dense urban areas, ground is to be interpreted as the height of the highest obstacle in the signal path between the two antenna sites. Avoid trees in the signal path to avoid signal absorption due to seasonal changes (leaves or ice). Install the antenna at least 2 m (6 ft.) away from all other antennas. Other situations in which reflections of the radio signal may cause interference are environments with large reflecting surfaces, parallel or partly perpendicular to the antenna beam, such as:
Mirror-glass buildings. Crowded parking lots. Water surface, moist earth and moist vegetation. Electric power lines and telephone lines above the ground level.
: Reflective surfaces can be used to improve the performance of a link, if the direct line-of-sight is impaired or absent. In the absence of a direct path or clear line-of-sight, transporting a signal through reflection depends on two factors:
Fresnel Zone: It is required to calculate the distance of the obstacle from the antenna. See Fresnel Zone Clearance Factor: It is required for optimal performance (See Clearance Factor). Ensure that the type and placement of the antennas leave sufficient clearance of the Fresnel Zone at the maximum width of the bulge, which is typically at the mid-point between the antennas. 1.2.3 Mounting the Antenna Mounting an antenna directly to the wall does not let you align the antenna properly with the corresponding antenna at the opposite end of your wireless link. Poor antenna alignment typically results in poor performance and therefore, we recommend mounting the antennas to a mast. Tsunami 800 and 8000 Series - Antenna Installation Guide 10 Antenna Installation The two methods followed frequently to erect an antenna mast are:
Tripod Mount: The tripod mount is used primarily on peak and flat roofs. The antenna mast must be secured to the roof using three or four guy wires equally spaced around the mast. When the height of the antenna mast is more than 3 meters (10 ft.), you should use at least three guy wires for every 3-meter (10-foot) section of the mast. Wall (Side) Mount: A wall (side) mount allows you to mount the antenna (mast) on the side of a building or on the side of an elevator penthouse. This provides you with a convenient mounting location, when the roof overhang is not excessive or when the location is high enough to provide a clear line-of-sight. When mounting multiple antennas on a single mast, use the following methods to minimize the influence of cross-talk interference between the antennas:
Place your antennas as far as possible. Mount the directional antennas, such that the identical side of both the antennas face the same direction. For 8xxx connectorized unit, use the antenna port A1, if you are using a single polarized antenna. Use the antenna port A1 and A3, if If you are using a dual polarized antenna. For 82x connectorized unit, use antenna ports A1 and A2 for dual polarized antenna.
: As the mounting procedures for the various antennas differ from one another, refer to the guide that comes along with the antenna.
: The antennas installed at both the ends of a wireless link should maintain same antenna polarizations. See Step 4: Next, wrap a layer of the butyl mastic tape on the adhesive side. 1.2.3.1 Antenna Mast Requirements To accommodate the antennas, the antenna mast must satisfy the following requirements:
The construction of the antenna mast must contain sturdy, weatherproof, and non-corrosive material (for example, galvanized or stainless steel construction pipe). Diameter of the mast should be between 35 mm (1.4 inches) and 41 mm (1.6 inches). The diameter of the antenna mast vary depending on the type of antenna you intend to install. The height of the antenna mast must be high enough to allow the antenna to be installed at least 1.5 m (5 ft.) above the roof. The height of the antenna should be at least 3 m (10 ft.) above, if it is a metal roof. The antenna mast or wall bracket must be free from any material (like paint) that prevents a good electrical conduction with the antenna. 1.2.4 Connecting the Cables Once the outdoor antennas are properly mounted, the cable setup essential to complete the outdoor antenna installation is depicted in the following figure:
Tsunami 800 and 8000 Series - Antenna Installation Guide 11 Antenna Installation Figure 1-2 Cable Setup The entire outdoor cabling setup requires the following cabling to be done:
1. Connecting the Antenna Cable 2. Connecting the Surge Arrestor and Ethernet / Power cables 3. Grounding the System 1.2.4.1 Connecting the Antenna Cable Follow the following steps to connect an antenna to the device, by using an antenna cable. 1. Use an RF cable (antenna cable) to connect the outdoor device to an external antenna. 2. Connect the right-angled N-male connector of RF cable on the antenna. The antenna cables run from the external antenna to the N-Type connectors on the device. The N-Type connectors have built-in surge protection for Tsunami 800 and 8000 product series. 3. Secure the antenna cable to the antenna mast, as the cable connectors do not support the full weight of the cable. 4. Connect the other end of the antenna cable to the device.
: Do not use tools to tighten the cable connectors, as they damage the antenna cable and connectors. Tsunami 800 and 8000 Series - Antenna Installation Guide 12 Antenna Installation If required, adjust the direction of the antenna. 5. 6. Tighten the nuts of the antenna to lock the antenna into its position.
: Avoid over-tightening of the connector, nuts and screws that are used to mount the antenna, to protect the antenna and device from getting damaged. 7. Secure the cable along its complete length with a cable or electrical tape to relieve strain on the antenna connector. No part of the cable should be allowed to hang free, especially the parts that are routed outside the building. 8. Weatherproof all the outdoor connectors. See Sealing the Cable Connectors Ensure you follow the below guidelines while using the antenna cable:
The entire cable used must be secured and no part of the antenna cable should be allowed to hang free, precisely the outdoor cable parts. The antenna cable and cable connectors are not designed to withstand excessive force. Do not use the connectors like cable grips, to pull the cable through raceways or conduits. Do not use the cable connector to support the weight of the cable during or after installation. Do not use any tool to tighten the connectors. Always seal the connectors using the weatherproofing tape. Avoid any water or moisture entering the cable, as it impacts the performance of the wireless link. Prior to sealing the outdoor connectors and permanently securing the cable to the wall with cable ties and wall hooks, assure that the components that are installed are functioning properly. Antenna Cable Routing The antenna cable must be routed and fixed in such a way, that the installation technicians have a clear passage area. All the connectors that are located outdoor must have a weatherproof seal. We recommend you to seal the connectors only after completing the final radio test. See Sealing the Cable Connectors 1.2.4.2 Connecting the Surge Arrestor and Ethernet / Power cables Perform the following steps to ensure proper surge protection, and ethernet or power cabling:
Connect the surge arrestor near the outdoor device with a CAT5e/CAT6 ethernet cable (properly ground it near to the cable ingress point of the building, complying with the local electrical code requirements). Connect the RJ 45 LAN-IN port on the POE (power injector) and the network interface card of the personal computer with a CAT5e/CAT6 ethernet cable. Plug one end of the Cat5e/Cat6 cable into the ethernet port of the surge arrestor (near building ingress point) and connect the other end of the cable to the PWR-LAN-OUT port on the POE. Ensure that the cable connector is latched securely. Connect the remaining ports on both the surge arrestors (one near the outdoor device and other at the building ingress point) with an RJ 45 terminated cable.
: Proxim recommends two approved lightning surge protectors to be installed, one near to the device and the other at the building ingress point. To buy an additional Surge Protector (with Part Number: 235-00001), place an order separately with your distributor. Tsunami 800 and 8000 Series - Antenna Installation Guide 13 Antenna Installation
: The surge arrestor and the antenna mast must be connected to the same grounding system, by using the shortest cable possible, as prescribed by local electrical codes. 1.2.4.3 Grounding the System Direct grounding of the antenna mast, device, and surge arrestor is extremely important. Refer to the Quick Installation Guide, that comes along with your product, for detailed illustration on grounding the outdoor device and surge arrestors.
: A safety grounding system is necessary to protect your radio from lightning strikes and the static electricity generated from it. Grounding the Antennas Following precautions should be satisfied, while grounding the antenna:
The antenna mast and the grounding system should be installed only by qualified installation professionals and electrician, who are familiar with local building, safety, and electrical codes in the country of use. The antenna mast, the device, and the surge arrestor must be connected to the same ground, by using an equi-
potential bonding conductor. A good electrical connection should be made to one or more ground rods, by using at least a 10AWG ground wire and non-corrosive hardware. 1.2.5 Sealing the Cable Connectors Corrosion of the antenna cable, cable connectors and other wireless outdoor installations degrade the performance of the wireless link. To avoid, you must always seal the outdoor cable connectors using weatherproofing tape. To weatherproof the antenna connectors at both the ends of a wireless link, follow the following step-by-step procedure:
1. Collect the required material:
The material required for weatherproofing connectors are, Any standard Butyl Mastic Tape Any standard Vinyl Tape We have used the following Butyl Mastic Tape and Vinyl Tape as an example to demonstrate the weatherproofing steps:
2. Follow the following weatherproofing steps:
: We have taken MP-8100-BSU and 16 dBi dual polarized sector antenna as an example to explain the weatherproofing steps. Follow the same method to weatherproof the antenna connectors of the Tsunami 800 and 8000 series products. Tsunami 800 and 8000 Series - Antenna Installation Guide 14 Step 1: Wrap a vinyl tape in a half-lapped fashion, from the weatherproofed connector end and continue wrapping till 3 inches onto the cable. a. Weatherproofing at the device end:
Antenna Installation b. Weatherproofing at the antenna end:
(a)
(b)
(a)
(b)
(c) Step 2: Wrap a second layer of the vinyl tape over the first layer but in other direction. a. Weatherproofing at the device end:
b. Weatherproofing at the antenna end:
(a)
(b)
(a)
(b) Tsunami 800 and 8000 Series - Antenna Installation Guide 15 Step 3: Now, wrap a layer of vinyl tape with the adhesive side out as it provides sticky surface for the next layer. a. Weatherproofing antenna connectors on the device:
Antenna Installation b. Weatherproofing antenna cable:
(a) Step 4: Next, wrap a layer of the butyl mastic tape on the adhesive side. a. Weatherproofing antenna connectors on the device:
(a)
(b)
(b) b. Weatherproofing antenna cable:
(a)
(b)
(a)
(b) Tsunami 800 and 8000 Series - Antenna Installation Guide 16 Step 5: Finally, wrap vinyl tap over the butyl layer. a. Weatherproofing antenna connectors on the device:
b. Weatherproofing antenna cable:
(a) The figure below depicts the complete weatherproofing of the RF connection.
(a) Antenna Installation
(b)
(b) Tsunami 800 and 8000 Series - Antenna Installation Guide 17 Antenna Installation 1.2.6 Antenna Polarization For optimal wireless link performance, you must always verify that the same antenna polarizations are maintained on both the ends of a wireless link. Tabulated below are the antenna polarizations for the Tsunami 800 and 8000 product series. Product 3x3 MIMO 2x2 MIMO MP-820-BSU-100 Not Applicable MP-820-SUA-50+
Not Applicable MP-8100-BSU/SUA MP-8200-BSU/SUA Antenna (A1) = +45 degree Polarization Antenna (A2) = Vertical Polarization Antenna (A3) = -45 degree polarization Antenna (A1) = +45 degree Polarization Antenna (A2) = Vertical Polarization Antenna (A3) = -45 degree polarization MP-8160-BSU/SUA Not Applicable QB-8100-EPA QB-8200-EPA
:
Antenna (A1) = +45 degree Polarization Antenna (A2) = Vertical Polarization Antenna (A3) = -45 degree polarization Antenna (A1) = +45 degree Polarization Antenna (A2) = Vertical Polarization Antenna (A3) = -45 degree polarization Antenna (A1) = Horizontal polarization Antenna (A2) = Vertical polarization Antenna (A1) = Horizontal polarization Antenna (A2) = Vertical polarization Antenna (A1) = Vertical polarization Antenna (A2) = Not connected Antenna (A3) = Horizontal polarization Antenna (A1) = Vertical polarization Antenna (A2) = 50 ohm load Antenna (A3) = Horizontal polarization Antenna (A1) = Horizontal polarization Antenna (A2) = Vertical polarization Antenna (A1) = Vertical polarization Antenna (A2) = Not connected Antenna (A3) = Horizontal polarization Antenna (A1) = Vertical polarization Antenna (A2) = 50 ohm load Antenna (A3) = Horizontal polarization If you are using all the antenna ports of a MIMO device, we recommend you to maintain different antenna polarizations on both the ends to avoid coupling. If you are using a single polarized or dual polarized antenna, it is recommended to terminate the unused antenna ports with an N-male 50 ohm terminator (supplied with the product package). Refer Tsunami 800 and 8000 Series
- Hardware Installation Guide, for details. Tsunami 800 and 8000 Series - Antenna Installation Guide 18 Antenna Installation Consider mounting the antenna for horizontal polarization and minimize the influence of cross-talk between antennas, only under the following circumstances:
When you are using single polarized antennas at both the ends of a wireless link. When multi-directional antennas are mounted to the same mast. When the wireless link receives interference from a vertically polarized antenna in the vicinity. 1.2.7 Aligning the Antenna Antenna alignment is the process of physically aligning the antenna of the radio receiver and transmitter to establish a link with a better throughput. The antenna alignment process is usually performed during the installation of the antennas. You can align the antennas by using the following two methods:
Audible Antenna Alignment Antenna Alignment using CLI Commands Alternatively, consult an antenna installation service professional to optimize the antenna alignment. 1.2.7.1 Audible Antenna Alignment The device has a built-in audible antenna alignment tool that can be activated by plugging in the supplied RJ11 serial dongle. It is audible up to a distance of 30 meters. The CLI command enables both audible and numerical feedback as the CLI shows the running Signal-to-Noise Ratio (SNR) values twice a second. The output from the beeper consists of short beeps with a variable interval. The interval changes with the SNR level to assist in correctly aligning the antenna. An increase in signal level is indicated by a shorter interval between beeps and a reduction in signal level results in longer beeps. The alignment process averages the SNR, which is represented by an average length beep. When a higher SNR is received, the beep period becomes shorter, dependent upon the difference to the average. A lower SNR results in a longer period between beeps. Figure 1-3 Beep Interval When the antenna is aimed, the beep intuitively represents whether the SNR is rising or falling. The higher the SNR rises, the higher is the frequency of the beep and shorter beep is heard. When you change the position of the antenna, SNR averaging settles at the new value and the beeping returns to the average length so the antenna can again be aimed for rising SNR. Aiming is complete if moving the antenna in any direction results in a falling SNR value (which can be heard as longer periods between beeps). Tsunami 800 and 8000 Series - Antenna Installation Guide 19 Antenna Installation
:
The range of the average SNR is limited to values from 5 to 43. Anything over 43 always results in a short period between beeps and values below 5 always have a long period. The Antenna Alignment Display (AAD) CLI command is automatically disabled 30 minutes after it is enabled to remove the load of extra messages on the wireless interface. The default telnet time-out is 300 seconds (5 minutes). It is applicable only to 8xxx devices. 1.2.7.2 Antenna Alignment using CLI Commands To enable the antenna alignment display from the CLI prompt, enter the following commands:
aad enable local: Enables display of the local signal, noise and SNR. aad enable remote: Enables display of the remote signal, noise and SNR. aad enable: Enables display of local and remote signal, noise and SNR.
: Use a flat blade screw driver to disconnect and pull out the serial cable from the enclosure after the antenna alignment is done. After withdrawing the cables, seal the serial port carefully to avoid water seepage. Tsunami 800 and 8000 Series - Antenna Installation Guide 20 Measuring Signal Performance This chapter contains information on the following:
2 Introduction Determining the Range Fresnel Zone Fresnel Zone Calculation Clearance Factor Calculations Calculating Link Budget 2.1 Introduction The performance of a microwave link (wireless link established between two outdoor antennas) is closely related to the following factors:
Range Fresnel Zone Clearance Factor Calculating the above factors help you align the antennas properly and achieve a better throughput. 2.2 Determining the Range Range is the maximum distance a microwave link travels and is based on the:
Type of the outdoor antenna equipment (Outdoor antennas differ in technical specifications). Data speed of the wireless link. Clearance of the signal path (see Clearance Factor). Use the following formula to determine the range of the microwave link:
Range = Maximum Range x Clearance Factor 1. Maximum Range: It is the theoretically calculated value achieved under optimal circumstances, by using the available products and their technical specifications that comply with the local radio regulations. The calculations made assuming the optimal radio conditions do not guarantee of achieving the same maximum distance at your location. 2. Clearance Factor: See Clearance Factor. Variations in calculations of the above two factors occur due to any of the following reasons:
Incorrect alignment of antennas (Refer to Aligning the Antenna). Polarization mismatch of the antennas. Sources of interference or unexpected reflections in the signal path that affect the quality of communication (Refer Determining the Optimal Antenna Placement). Severe weather conditions such as heavy rainfall, snow or strong winds. Unexpected obstacles in the link path. Seasonal influences such as leaves on trees or icing of the antennas. Tsunami 800 and 8000 Series - Antenna Installation Guide 21 Measuring Signal Performance 2.3 Fresnel Zone The narrow antenna beam emerged from the antennas contain a bulged area called as Fresnel Zone. The first Fresnel Zone is known to be an imaginary boundary line offset along the direct path of the signal, where a signal reflected will travel an additional one-half distance of wavelength. Each succeeding Fresnel Zone boundary adds an additional half-wavelength to the reflected path distance than the direct signal path between the antennas. When any significant part of the Fresnel Zone is obstructed, a portion of the radio energy is lost that results in reduced performance. Reduced performance can also occur when obstacles close to the antenna beam cause signal reflections or noise that interfere with the radio signal. Weather conditions (rain or snow) usually do not have much impact on the performance of your device, provided you have sealed all the cable connectors with weatherproofing tape. Seasonal influence on signal propagation can occur in the following situations:
Marginal communications quality in late fall (with no leaves on the trees along the signal path) might fail in the summer (with leaves on the trees along the signal path). In winter, a wireless link can fail when the antenna is exposed to ice buildup or when the antenna elements are covered with snow. Radio paths over water or extremely flat ground require optimization of antenna height at one end. This is due to in-phase or out-of-phase reflections. Adjustment of antenna height by 1 to 3 meters may move the signal from null to peak. Long distance links may be obstructed by earth curvature, so the antenna height requirements must not only take the height of obstructions and Fresnel Zone into account but also the earth bulge. The earth bulge is approximately 5 meters (16.4 ft.) at a link distance of 16 Kilometers (10 millimeters). Consult your supplier to take appropriate steps to maintain or optimize wireless link performance. 2.3.1 Fresnel Zone Calculation The exact shape and width of the Fresnel Zone is determined by calculating the Fresnel Radius. The distance between the Fresnel Zone boundary and a straight line running along the signal path (shortest path) between the antennas is called the Fresnel Radius. Fresnel Radius can be determined by using the path difference (difference between the shortest path and alternative path) and frequency of the radio signal. If there are no obstacles in the space forming 60% of the path difference, then the propagation characteristics are said to be the same as that in free space. Figure 2-1 Fresnel Zone Calculation Tsunami 800 and 8000 Series - Antenna Installation Guide 22 Lets say, in the above figure:
Measuring Signal Performance d1 is the distance between the obstacle and the antenna at one end. d2 is the distance between the obstacle and the antenna at the other end. is the wavelength of the operating frequency. Then, Path Difference (d3) and Fresnel Radius (rn, radius of the nth Fresnel Zone) can be calculated from the formula below:
(where n = 1, for the first Fresnel Zone and rn = r1) The path difference is the required clearance of the antenna beam from obstacles in its path to avoid loss of radio signal. Signals reflected from any even-numbered Fresnel Zone result in signal cancellation while the odd-numbered Fresnel Zones add to the direct path signal. 2.4 Clearance Factor Clearance Factor is a correction value (in percentage) that should be used in case, where the signal path of your wireless link does not provide the minimum clearance as listed in the Maximum Range Table. In general, clearance factor is taken as 60%
of the Fresnel Zone and is calculated as:
Clearance Factor = Fresnel Zone x 60%
For optimal performance of your outdoor wireless link, the signal path between the BSU and SU must provide sufficient clearance. Clearance is interpreted as:
The total height above the surface of the earth, in the open areas without obstacles in the signal path. Lets say antenna is mounted on the roof, then clearance is the total height including the height of the building and the height of the mast above the rooftop. The height above the highest possible obstacle, in the areas with obstacles along the signal path (path between two antennas). The height above the rooftop or highest obstacle in the signal path, in dense urban areas.
: An outdoor wireless link that lacks sufficient clearance will exhibit poor performance, which is typically perceived as slow network response time. However, your radio equipment automatically retransmits every lost data frame due to an out-of-range situation or frame collision. The larger the number of retransmissions, the lower is the throughput efficiency of your wireless link. Figure 2-2 Clearance required for the Optimal Performance Tsunami 800 and 8000 Series - Antenna Installation Guide 23 Measuring Signal Performance As shown in the above figure, the clearance required for optimal performance is interpreted as:
Vertical clearance above the ground and the highest buildings or objects along the signal path Horizontal clearance from neighboring buildings and objects along the signal path For optimal range and throughput performance, you must ensure that your antenna installation provides maximum clearance in both horizontal and vertical directions. If the local authorities, proprietor of the premises or other miscellaneous factors do not allow you to set up an antenna mast for the clearance requirements, then you may not achieve a full line-of-sight clearance. However, if the distance that your wireless outdoor installation covers is less than the listed maximum range, you dont need full clearance. To determine the effect of insufficient signal path clearance, you must determine the Clearance Factor and also calculate its effect on the range for your antenna installation, by using the formula described in Determining the Range. Figure 2-3 Clearance Factor If the clearance for your antenna installation is equal to or better than the minimum clearance required, then the Clearance Factor for your installation is 100%. If your actual clearance is less than the minimum clearance, then refer Figure 2-3 to determine the actual range that applies to the current requirement.
: Practically, it is impossible to achieve the maximum range due to the interference from the other radio products. Proxim recommends you to maintain at least 60-70% of the first Fresnel Zone free. If the clearance is lower than this percentage, then the link budget and acquired fade margin are affected. Clearances more than 100% of the Fresnel Zone can cause reflections that are 180 degrees out of phase and can cancel the signal. The Fresnel Zone works in both the horizontal and vertical paths. Tsunami 800 and 8000 Series - Antenna Installation Guide 24 Measuring Signal Performance 2.5 Calculations A microwave link is established along the path between antennas. Availability of the microwave path is therefore a prediction of the percent of time that the wireless link operates. In the absence of direct interference, availability of microwave path is affected by the following factors:
Path length Fade margin Frequency Terrain (smooth, average, mountainous) Climate (dry, temperate, humid) Availability of the microwave path can be improved by increasing the fade margin, either by making the path shorter or by using the higher gain antennas in conjunction with lower loss antenna cable (using a higher quality antenna cable, shortening the length, or both). Establish a wireless link for a specific availability rate of microwave path, depending upon the type of information carried over the link and the overall network design redundancy. Lets say, the data or voice traffic carried by the radio is critical, then the link can be established at a very high availability rate of microwave path (say, 99.999% or 5.3 minutes of predicted outage per year). 2.5.1 Calculating Link Budget Use the following formula to estimate the received signal level (RSL):
RSL (dBm) = Pout - L1+ G1 + G2 - L2 - Lp where:
Pout is the output power (in dBm) of the transmitter. G1 is the gain of the antenna on one side of the link (in dB). G2 is the gain of the antenna on the opposite side of the link (in dB). L1 is the total loss of all transmission elements between the antenna and the RF device on one side of the link (in dB). L2 is the total loss of all transmission elements between the antenna and the RF device on the opposite side of the link (in dB). Lp is the Path loss, defined by:
Lp (dB) = 96.6 + 20 log10F + 20 log10D; where:
F is the frequency of the radio system in GHz. D is the distance of the path in miles.
:
This formula is available on a calculation sheet provided by Proxim to generate an estimate of link distance and reliability. The path loss must be smaller than the link budget minus the minimum required fade margin. The maximum ranges cause the path loss plus the fade margin to be the same as the link budget. Tsunami 800 and 8000 Series - Antenna Installation Guide 25 The following figure is a pictorial representation of the elements in the Link Budget equation. Measuring Signal Performance Figure 2-4 Link Budget Equation-Pictorial Representation Procedure 1. Start with the transmit power and the number of the channel to be used in dBm. Subtract the total loss of all transmission elements between the antenna and the radio on one side of the link (dB). 2. Add the dBi of the antenna you will be using. The total is the EIRP (Equivalent Isotropically Radiated Power). 3. Determine the path loss of the microwave link by using the mathematical formula of Lp, illustrated in Calculating Link Budget. 4. Add the gain of the antenna on the second side of the link. 5. Subtract the total loss of all transmission elements between the antenna and the radio on the second side of the link. The result is the Received Signal Level (RSL). 6. For details on the receive sensitivity and data rate values used for the wireless link, please refer to the Tsunami 800 and 8000 series - Hardware Installation Guide. 7. Subtract this value from the Received Signal Level; this is the Fade Margin.
:
The RSL must be higher than the Receiver Sensitivity plus the Fade Margin for a good link. The amount of Fade Margin indicates the reliability of the link. The more the Fade Margin, the more reliable is the link. The results of this link budget calculation are very important for determining any potential problems during installation. If you have calculated the expected RSL, you can verify that it has been achieved during installation and troubleshooting. Tsunami 800 and 8000 Series - Antenna Installation Guide 26 Measuring Signal Performance Tabulated below is the relation between the Distance and Link Budget, for a selected frequency:
Reference Frequency: 5600 MHz Center Frequency for Europe Link Budget Distance
(dB) 61 62 63 64 65 66 67 68 69
(m) 4.8 5.4 6.0 6.8 7.6 8.5 9.5 11 12 Link Budget Distance
(dB) 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90
(m) 13 15 17 19 21 24 27 30 34 38 43 48 54 60 68 76 85 95 107 120 135 Fresnel Zone (m) 0.3 0.3 0.3 0.3 0.3 0.3 0.4 0.4 0.4 Fresnel Zone (m) 0.4 0.5 0.5 0.5 0.5 0.6 0.6 0.6 0.7 0.7 0.8 0.8 0.8 0.9 1.0 1.0 1.1 1.1 1.2 1.3 1.3 Link Budget Distance
(dB) 91 92 93 94 95 96 97 98 99
(m) 151 170 190 214 240 269 302 339 380 Link Budget Distance
(dB) 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120
(m) 426 478 537 602 676 758 850 954 1071 1201 1348 1512 1697 1904 2136 2397 2689 3018 3386 3799 4263 Fresnel Zone (m) 1.4 1.5 1.6 1.7 1.8 1.9 2.0 2.1 2.3 Fresnel Zone (m) 2.4 2.5 2.7 2.8 3.0 3.2 3.4 3.6 3.8 4.0 4.2 4.5 4.8 5.0 5.3 5.7 6.0 6.4 6.7 7.1 7.6 Link Budget Distance
(dB) 121 122 123 124 125 126 127 128 129
(m) 4.8 5.4 6.0 6.8 7.6 8.5 9.5 10.7 12.0 Link Budget Distance
(dB) 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150
(m) 13.5 15.1 17.0 19.0 21.4 24.0 26.9 30.2 33.9 38.0 42.6 47.8 53.7 60.2 67.6 75.8 85.0 95.4 107.1 120.1 134.8 Fresnel Zone (m) 8.0 8.5 9.0 9.5 10.1 10.7 11.3 12.0 12.7 Fresnel Zone (m) 13.4 14.2 15.1 16.0 16.9 17.9 19.0 20.1 21.3 22.6 23.9 25.3 26.8 28.4 30.1 31.9 33.7 35.7 37.9 40.1 42.5
: The Distance (m) is calculated by assuming the 60% of the 1st Fresnal to be clear. Tsunami 800 and 8000 Series - Antenna Installation Guide 27 Measuring Signal Performance Effective Isotropic Radiated Power (EIRP) In countries like USA and Canada, radio can be installed with any directional antennas gain, as there is no Effective Isotropic Radiated Power (EIRP) limit for the application of these systems for fixed point-to-point applications in the 5.8 GHz frequency band. In other bands and in other countries, EIRP limits may apply. In the case of EIRP limits, use the lower values of either
(Pout - L1+ G1) or the EIRP limit, within the Link Budget equation. You should check this calculation in both the directions to assure legal application. An EIRP limit is the maximum RF energy that can be transmitted as measured at the transmitting antenna and is usually determined by government regulations. For details, we recommend you to refer the Max EIRP values listed under the Wireless Interface properties, in the Tsunami 800 and 8000 Series - Software Management Guide. The figure below illustrates the calculation of range through Proxim Link (MP/QB 81XX) Calculator, available at http://
my.proxim.com, that dynamically adapts the transmit power and receive sensitivity values for a selected product to follow the local EIRP rule. Figure 2-5 Proxim Link Calculator Tsunami 800 and 8000 Series - Antenna Installation Guide 28 Statement of Warranty Warranty Coverage 3 Proxim Wireless Corporation warrants that its products are manufactured solely from new parts, conform substantially to specifications, and will be free of defects in material and workmanship for a Warranty Period of 1 year from the date of purchase. Repair or Replacement When Proxim determines that a returned product does not meet the warranted criteria during the warranty period, Proxim at its option, will either: (a) repair the defective product; (b) replace the defective product with a new or refurbished product that is at least equivalent to the original; or (c) refund the price paid for the defective product. Generally, products are repaired or replaced within thirty (30) business days of receipt of the product at a Proxim Logistical/Repair Center. The warranty period for repaired or replacement products is ninety (90) days or the remainder of the original warranty period, whichever is longer. These three alternatives constitute the customers sole and exclusive remedy and Proxims sole and exclusive liability under warranty provisions. Limitations of Warranty Proxims warranties do not apply to any product (hardware or software) which has (a) been subjected to abuse, misuse, neglect, accident, or mishandling, (b) been opened, repaired, modified, or altered by anyone other than Proxim, (c) been used for or subjected to applications, environments, or physical or electrical stress or conditions other than as intended and recommended by Proxim, (d) been improperly stored, transported, installed, or used, or (e) had its serial number or other identification markings altered or removed. Buyers can contact Proxim Wireless Customer Service Center either by telephone or via web. Support and repair of products that are out of warranty will be subject to a fee. Contact information is shown below. Additional support information can be found at Proxim Wirelesss web site at http://my.proxim.com. Contact technical support via telephone as follows:
USA and Canada Customers Phone: +1-408-383-7700; +1-866-674-6626 Business Hours: 24x7 live response. Tier 3 support: 8 a.m. to 5 p.m. M-F PDT (UTC/GMT -7 hrs) International Customers Phone: +1-408-383-7700; 0800-916475 (France); 8-800-100-9485 (Russia) Business Hours: 24x7 live response. Tier 3 support: 8 a.m. to 5 p.m. M-F PDT (UTC/GMT -7 hrs) Tsunami 800 and 8000 Series - Antenna Installation Guide 29 Statement of Warranty General Procedures When contacting the Customer Service for support, Buyer should be prepared to provide the product description and serial number and a description of the problem. The serial number should be on the product. In the event the Customer Service Center determines that the problem can be corrected with a software update, Buyer might be instructed to download the update from Proxim Wirelesss web site or, if thats not possible, the update will be sent to Buyer. In the event the Customer Service Center instructs Buyer to return the product to Proxim Wireless for repair or replacement, the Customer Service Center will provide Buyer a Return Material Authorization (RMA) number and shipping instructions. Buyer must return the defective product to Proxim Wireless, properly packaged to prevent damage, shipping prepaid, with the RMA number prominently displayed on the outside of the container. Calls to the Customer Service Center for reasons other than product failure will not be accepted unless Buyer has purchased a Proxim Wireless Service Contract or the call is made within the warranty period. After the warranty period, Technical Support is fee based (detailed in Technical Services and Support). If Proxim Wireless reasonably determines that a returned product is not defective or is not covered by the terms of this Warranty, Buyer shall be charged a service charge and return shipping charges. Other Information Search Knowledgebase Proxim Wireless stores all resolved problems in a solution database at the following URL: http://my.proxim.com. Create a Support Request Submit a question or open an issue to Proxim Wireless technical support staff at the following URL:
https://my.proxim.com/new_case. Tsunami 800 and 8000 Series - Antenna Installation Guide 30 Technical Services and Support Obtaining Technical Service and Support 4 If you are having trouble using the Proxim product, please read this guide and the additional documentation provided with your product. If you require additional support to resolve your issue, please be ready to provide the following information before you contact Proxims Technical Services team:
Product information Part number and serial number of the suspected faulty device Trouble/error information Trouble/symptom being experienced Activities completed to confirm fault Network information (What kind of network are you using?) Circumstances that preceded or led up to the error Message or alarms viewed Steps taken to reproduce the problem ServPak information (if a Servpak customer):
ServPak account number Registration information If the product is not registered, date and location where you purchased the product
: Technical Support is free for the warranty period from the date of purchase. Support Options Proxim eService Web Site Support The Proxim eService Web site is available 7x24x365 at http://my.proxim.com. On the Proxim eService Web Site, you can access the following services:
Product Download Page: Provides quick links to product firmware, software, and documentation downloads. Proxim TV Links: A link to helpful video tutorials. Knowledgebase: A solution database of all the resolved problems. You can search by product, category, keywords, or phrases. Live Chat: Chat with a support technician on-line or request to call back at a later time. Create a Support Request: Create a support request with our technical support staff who will reply to you by email. Case Management: Login to check the status of your support cases, update your personal profile, or access restricted information and features. Provide Feedback: Submit a suggestion, complaint, or other feedback about the support site and our products. Tsunami 800 and 8000 Series - Antenna Installation Guide 31 Technical Services and Support Telephone Support Contact technical support via telephone as follows:
USA and Canada Customers Phone: +1-408-383-7700; +1-866-674-6626 Business Hours: 24x7 live response. Tier 3 support: 8 a.m. to 5 p.m. M-F PDT (UTC/GMT -7 hrs) International Customers Phone: +1-408-383-7700; 0800-916475 (France); 8-800-100-9485 (Russia) Business Hours: 24x7 live response. Tier 3 support: 8 a.m. to 5 p.m. M-F PDT (UTC/GMT -7 hrs) ServPak Support To provide even greater investment protection, Proxim Wireless offers a cost-effective support program called ServPak. ServPak is a program of enhanced service support options that can be purchased as a bundle or individually, tailored to meet your specific needs. Whether your requirement is round the clock technical support or advance replacement service, we are confident that the level of support provided in every service in our portfolio will exceed your expectations. All ServPak service bundles are sold as service contracts that provide coverage for specific products from 1 to 3 years. Servpak bundles are considered an upgrade to the standard product warranty and not an extension. 24x7 Basic Technical Support Basic Advanced Replacement
(Two business days/
International economy shipment service) Priority Advanced Replacement
(Next business day/
International priority shipment service) Priority Comprehensive Advance Replacement
(Next business day/
International priority shipment service) 8x7 Advanced Technical Support Software Maintenance Access to Knowledge Base 24x7 Advanced Technical 24x7 Advanced Technical Support Support PVES & PV NMS Support PVES & PV NMS Support Post-Installation Optimization 50% discount on Onsite Technical Support and Services Tsunami 800 and 8000 Series - Antenna Installation Guide 32 Technical Services and Support Additional Information on ServPak Options Advanced Replacement of Hardware In the event of a hardware failure, our guaranteed turnaround time for return to factory repair is 30 days or less. Customers who purchase this service are guaranteed replacement of refurbished or new hardware to be shipped out within one or two business days, as applicable. Options are available for shipment services depending on the customers support needs. Hardware is shipped on business days, Monday Friday excluding Holidays, 8:00 AM 3:30 PM Eastern Time. Comprehensive Advanced Replacement of Hardware In addition to ServPak Prime options, in the event of a hardware failure, Proxim will repair or replace the failed product for any reason, other than vandalism. 7x24x365 Availability Unlimited, direct access to technical support engineers 24 hours a day, 7 days a week, 365 days a year including Holidays. 8x5 Availability Unlimited, direct access to world-class technical support engineers 8 hours a day, 5 days a week, Monday through Friday from 8:00AM - 5:00PM Pacific Standard Time. Basic Technical Support Customers who purchase this service can be rest assured that their call will be answered by Proxims Tier 1 technical support and a case opened immediately to document the problem and provide initial troubleshooting to identify the solution and resolve the incident in a timely manner. Advanced Technical Support In addition to Proxims world-class Tier 1 technical support, customers will be able to have their more complex issues escalated to our world-class Tier 3 technical support engineers. Our Tier 3 engineers will review specific configurations to troubleshoot intricate issues and will also provide helpful insights regarding Proxims products and various tips from decades of collective experience in the wireless industry. Software Maintenance It's important to maintain and enhance security and performance of wireless equipment and Proxim makes this easy by providing a Software Maintenance program that enables customers to access new feature and functionality rich software upgrades and updates. Customers will also have full access to Proxim's vast Knowledgebase of technical bulletins, white papers and troubleshooting documents. Post-Installation Optimization You can consult with our technical support engineers to enhance performance and efficiency of your network. Post-installation optimization services include:
Review frequencies to select best possible channel Review Modulation, Channel Bandwidth, MIMO, and WORP settings to optimize throughput and link quality Review Satellite Density & TPC/ATPC settings Assistance with Bandwidth controls Tsunami 800 and 8000 Series - Antenna Installation Guide 33 Assistance with QoS, RADIUS, and VLAN settings on Proxim equipment Technical Services and Support To purchase ServPak support services, please contact your authorized Proxim distributor. To receive more information or for questions at http://www.proxim.com/support/servpak, call Proxim Support (For telephone numbers, see Telephone Support) or send an email to servpak@proxim.com. our website available options, ServPak support please visit any the on of Technical Support Policy Technical Support for Current Products during Warranty Period All Customers are entitled to free technical support for the Proxim products they purchase from Proxims authorized resellers or distributors. Technical Support is defined as communication via the Proxim Support website (http://my.proxim.com) and/or via telephone. This technical support will be provided for free for the entire time the product is covered by a Proxim warranty. The term of Proxims warranty is determined according to the agreement under which the product was sold and generally varies from 3 months to 2 years depending on the product. If a Customer disagrees with Proxims determination of warranty duration, a request for review supported by a copy of all product purchase documentation may be submitted. Technical Support for Current Products after Warranty Period After the warranty period, technical support on products then being sold by Proxim will be based upon one of the following three options Customers can choose:
Customers can choose to purchase one of Proxims ServPak extended warranty and enhanced support packages for the product Customers can choose to purchase one-time per-incident technical support for the product for a fee Customers can choose to call the reseller or distributor who sold them the product for technical support Tech Support on Discontinued Products Technical Support on some products that Proxim has declared as EOL (End of Life) or otherwise is no longer selling is available based upon one of the following three options Customers can choose:
For some discontinued products, Customers can choose to purchase one of Proxims EOL ServPak support packages for the product No EOL ServPak support package will be available for any product discontinued more than 5 years ago No EOL ServPak support package is available for certain discontinued products Customers can choose to purchase one-time per-incident technical support for the product on a per hour basis at a rate of $125 an hour (4 hours minimum payable in advance by major credit card). This fee is payable in addition to any RMA fee that may be charged to subsequently repair the product. Customers can choose to call the reseller or distributor who sold them the product for technical support All Proxim technical support for discontinued products, whether through an EOL ServPak package or otherwise, is provided on a best effort basis and is subject to the continued availability of necessary components, equipment, and other technical resources. Note that Proxim is unable to support or warrant any equipment that has been modified, whether this modification is physical, or if third-party software codes have been loaded onto the product. Tsunami 800 and 8000 Series - Antenna Installation Guide 34
1 2 3 4 5 6 7 | Manual | Users Manual | 4.45 MiB |
Tsunami 800 & 8000 Series
(Point-to-point and Point-to-multipoint Products) Software Management Guide Products Covered
--> Tsunami Multipoint
- MP-8200-BSU-G; MP-8250-BS9-G; MP-8250-BS1-G
- MP-8200-BSU; MP-8250-BS9; MP-8250-BS1
- MP-820-BSU-100
- MP-822-BSU-100
- MP-825-BS3-100
- MP-820-SUA-50+
- MP-820-SUA-100
- MP-822-SUA-100
- MP-825-SUR-50+
- MP-825-SUR-100
- MP-825-CPE-50
- MP-825-CPE-100
- MP-835-CPE-10
- MP-835-CPE-25
- MP-835-CPE-50
- MP-835-CPE-100
- MP-8100-SUA
- MP-8150-SUR
- MP-8150-SUR-100
- MP-8200-SUA
- MP-8250-SUR
--> Tsunami Quickbridge
- QB-8200-EPA-G/LNK-G
- QB-8250-EPR-G/LNK-G
- QB-8200-EPA/LNK
- QB-8250-EPR/LNK
- QB-825-EPR/LNK-50+
- QB-825-EPR/LNK-100
- QB-835-EPR/LNK-25
- QB-835-EPR/LNK-50
- QB-826-EPR/LNK-100 Copyright 2015 Proxim Wireless Corporation, Fremont, CA. All rights reserved. Covered by one or more of the following U.S. patents: 5,231,634;
5,875,179; 6,006,090; 5,809,060; 6,075,812; 5,077,753. The content described herein are copyrighted with all rights reserved. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language in any form by any means without the written permission of Proxim Wireless Corporation. Trademarks Tsunami, Proxim, and the Proxim logo are the trademarks of Proxim Wireless Corporation. All other trademarks mentioned herein are the property of their respective owners. Disclaimer Proxim reserves the right to revise this publication and to make changes in content from time-to-time without obligation on the part of Proxim to provide notification of such revision or change. Proxim may make improvements or changes in the product(s) described in this guide at any time. When using these devices, basic safety precautions should always be followed to reduce the risk of fire, electric shock and injury to persons. GPL License Note Tsunami products include, in part, some free software that is developed by Free Software Foundation. A user is granted license to this software under the terms of either the GNU General Public License or GNU Lesser General Public License (See http://www.gnu.org/licenses/
licenses.html). This license allows the user to freely copy, modify and redistribute this software and no other statement or documentation from us. To get a copy of this software, or for any other information, please contact our customer support team Telephone Support). OpenSSL License Note Tsunami products contains software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/) and that is subject to the following copyright and conditions:
Copyright (c) 1998-2002 The OpenSSL Project. All rights reserved. The names OpenSSL Toolkit and OpenSSL Project must not be used to refer to, endorse, or promote the products or for any other purpose related to the products without prior written permission. For written permission, please contact openssl-core@openssl.org. This software is provided by the OpenSSL Project as is and any expressed or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed. In no event shall the OpenSSL Project or its contributors be liable for any direct, indirect, incidental, special, exemplary, or consequential damages (including, but not limited to, procurement of substitute goods or services; loss of use, data, or profits; or business interruption) however caused and on any theory of liability, whether in contract, strict liability, or tort (including negligence or otherwise) arising in any way out of the use of this software, even if advised of the possibility of such damage. Tsunami 800 and 8000 Series - Software Management Guide Documentation Version: 6.5 P/N 765-00131, May 2016 Tsunami 800 & 8000 Series - Software Management Guide 2 Preface. 10 1 Overview . 13 About Tsunami 800 and 8000 Products . 13 Wireless Network Topology . 18 Point-to-Multipoint (PTMP). 18 Point-to-Point Link . 22 Multiple-Input-Multiple-Output (MIMO) . 25 Wireless Outdoor Router Protocol (WORP) . 25 2 Management and Monitoring Capabilities . 27 Web (HTTP/HTTPS) Interface . 27 Command Line Interface . 27 HyperTerminal . 27 Telnet . 28 Secure Shell (SSH) . 28 Simple Network Management Protocol (SNMP) Management . 28 PV Advanced . 29 3 Device Initialization . 30 Initialization . 30 ScanTool . 30 Initialize Device by using ScanTool . 31 Modifying the IP Address of the Device by using ScanTool . 32 Logging onto the Web Interface . 33 Home Page . 35 COMMIT. 36 REBOOT . 37 Factory Default Configuration . 37 4 Basic Configuration . 40 5 Advanced Configuration . 47 System . 48 Network . 50 IP Configuration . 51 Bridge Mode . 51 Routing Mode . 55 Routing Mode with PPPoE Client Enabled . 58 Static Route Table . 61 Adding Static Route Entries . 62 Network Address Translation (NAT). 63 Tsunami 800 & 8000 Series - Software Management Guide 3 Supported Session Protocols . 65 RIP . 66 PPPoE End Point (SU Only) . 67 IP over IP Tunneling. 73 Create a Tunnel . 75 View Existing Tunnels . 77 Ethernet . 77 Basic Ethernet Configuration . 77 Advanced Configuration. 79 Wireless . 80 Link Profiles . 81 Add a Link Profile . 82 Edit a Link Profile . 82 Wireless Outdoor Router Protocol (WORP). 89 Wireless Interface Properties . 95 Basic . 95 Sync . 104 MIMO . 112 Frequency Filter . 113 Dynamic Frequency Selection (DFS) . 114 Dynamic Channel Selection (DCS). 117 Manual Blacklist . 119 Roaming . 120 BSU / SU Profiles. 122 Add a Profile . 122 Edit a Mapped Profile . 125 Security . 125 Wireless Security . 125 Creating a New Security Profile . 126 Editing an existing Security Profile . 128 RADIUS . 128 MAC ACL . 130 Add SUs/End Point B to MAC Access Control Table . 131 Edit the existing SUs/End Point B from MAC Access Control Table. 131 Quality of Service (QoS) . 131 QoS Concepts and Definitions . 132 Packet Identification Rule (PIR) . 132 Service Flow Class (SFC). 133 QoS Class. 136 QoS Configuration . 137 QoS PIR Configuration . 141 QoS Service Flow Configuration (SFC) . 149 Tsunami 800 & 8000 Series - Software Management Guide 4 QoS Class Configuration . 151 QoS SU or End Point B List Configuration . 154 QoS Configuration for a Management Station . 155 RADIUS Based SU QoS Configuration . 158 VLAN (Bridge Mode Only) . 159 System-Level VLAN Configuration. 160 Ethernet VLAN Configuration. 161 Transparent Mode. 161 Access Mode . 162 Trunk Mode . 163 RADIUS Based SU VLAN Configuration . 166 Filtering (Bridge Only) . 168 Protocol Filter. 169 Protocol Filter Table . 170 Add User-defined Protocols to the Filter Table . 171 Static MAC Address Filter . 171 Static MAC Address Filter Configuration. 173 Advanced Filtering . 174 Edit Advanced Filtering Table Entries . 175 TCP/UDP Port Filter. 176 TCP/UDP Port Filter Table . 176 Adding User-defined TCP/UDP Port Filter Entries . 177 Storm Threshold Filter . 178 WORP Intra Cell Blocking . 179 WORP Intra Cell Blocking Group Table . 180 WORP Intra Cell Blocking MAC Table . 181 DHCP . 182 DHCP Pool. 182 Adding a New Pool Entry . 183 DHCP Server . 183 DHCP Relay (Routing Mode only) . 185 IGMP Snooping . 186 6 Management . 188 System . 188 System Information . 188 Inventory Management . 189 Licensed Features . 190 License Upgrade Procedure . 191 File Management . 192 TFTP Server. 192 Text Based Configuration (TBC) File Management . 192 Tsunami 800 & 8000 Series - Software Management Guide 5 Generating TBC File . 192 Editing the TBC File . 193 Loading the TBC file . 194 Upgrade Firmware . 194 Upgrade Firmware via HTTP . 194 Upgrade Firmware via TFTP. 195 Upgrade Configuration . 196 Upgrade Configuration via HTTP . 196 Upgrade Configuration via TFTP . 196 Upgrade License . 198 Upgrade License via HTTP. 198 Upgrade License via TFTP . 199 Retrieve From Device . 199 Retrieve from Device via HTTP . 199 TFTP Retrieve. 201 Services . 203 HTTP/HTTPS . 203 Telnet/SSH . 204 SNMP. 205 SNMP Trap Host Table . 208 Edit SNMP Trap Host Table . 209 Logs . 209 Configure a Remote Syslog host . 210 Simple Network Time Protocol (SNTP) . 211 Access Control . 213 Add Host(s) to Management Access Control Table . 214 Edit Management Access Control Table Entries. 214 Reset to Factory . 215 Convert QB to MP . 215 Auto Config Recovery . 216 7 Monitor . 218 System . 218 RSSI LED Behavior . 218 Sync LED Behavior . 219 Interface Statistics . 219 Ethernet Statistics . 219 Wireless Statistics . 221 PPPoE Statistics . 223 IP Tunnels . 224 WORP Statistics . 225 General Statistics . 225 Tsunami 800 & 8000 Series - Software Management Guide 6 Basic Statistics . 227 Advanced Statistics. 228 Link Statistics . 229 SU / End Point B Link Statistics . 229 BSU/End Point A Link Statistics . 232 QoS Statistics (BSU or End Point A Only) . 233 Active VLAN . 234 Bridge . 235 Bridge Statistics . 235 Learn Table . 236 Network Layer . 236 Routing Table . 236 IP ARP . 237 ICMP Statistics . 238 IP Address Table . 239 DNS Addresses . 239 Neighbour Table . 240 RIP Database. 240 RADIUS (BSU or End Point A only) . 241 Authentication Statistics . 241 IGMP . 242 Ethernet or Wireless Multicast List. 242 Router Port List . 242 DHCP . 243 Logs . 244 Event Log. 244 View Event Log . 244 Hide Event Log . 244 Clear Event Log . 245 Debug Log . 245 Temperature Log . 245 View Temperature Log . 246 Hide Temperature Log . 247 Clear Temperature Log . 247 Tools . 248 Wireless Site Survey . 248 Scan Tool . 248 sFlow . 249 sFlow Receiver Configuration . 251 Sampling Configuration. 251 Counter Polling Configuration . 252 Console Commands. 253 Tsunami 800 & 8000 Series - Software Management Guide 7 Spectrum Analyzer. 254 Basic Mode . 255 Advanced . 258 Radio Link Test Tool . 260 Configuration Options . 260 Statistics Options. 263 rlt Command Options . 264 SNMP v3 Statistics . 265 8 Troubleshooting . 267 PoE Injector . 268 Connectivity Issues . 269 Surge or Lightning Issues (For Connectorized devices) . 270 Setup and Configuration Issues . 270 Application Specific Troubleshooting . 272 Wireless Link Issues . 272 Wired (Ethernet) Interface Validation . 274 Wireless Interface Validation . 275 Recovery Procedures . 276 Operational Mode. 276 Bootloader Mode . 278 Load a New Image . 279 Using the ScanTool . 279 Using the Bootloader CLI . 279 Setting IP Address using Serial Port . 280 Hardware and Software Requirements . 281 Attach the Serial Port Cable . 281 Initializing the IP Address using CLI . 281 Spectrum Analyzer . 282 Avoiding Interference . 282 Conclusion . 282 Miscellaneous . 283 Unable to Retrieve Event Logs through HTTPS . 283 A Feature Applicability . 284 B Parameters Requiring Reboot. 286 C Frequency Domains and Channels. 290 D LACP - Device Management . 306 E QinQ. 309 Tsunami 800 & 8000 Series - Software Management Guide 8 F BSU Redundancy . 311 G Bootloader CLI and ScanTool . 314 H SNR Information . 321 I Configuration File Cross-loading across the Products . 327 J Abbreviations . 329 K Lightning Protection . 333 L Warranty and Technical Support . 334 Tsunami 800 & 8000 Series - Software Management Guide 9 Preface Preface This chapter contains the following information:
About this Guide Products Covered Audience Prerequisites Related Documents Documentation Conventions About this Guide This guide gives a jump-start working knowledge of the Tsunami 800 and 8000 products. It explains the step-by-step procedure to configure, manage and monitor the device by using Web Interface. Products Covered Product(s) Supported Countries Supported Software Version MP-8200-BSU-G MP-8250-BS9-G MP-8250-BS1-G MP-8200-BSU MP-8250-BS9 MP-8250-BS1 MP-820-BSU-100 MP-822-BSU-100 MP-825-BS3-100 MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 MP-8200-SUA MP-8250-SUR MP-820-SUA-50+
MP-820-SUA-100 MP-822-SUA-100 MP-825-SUR-50+
US, WD, EU US, WD, EU US, WD US, WD, EU US, WD, EU US, WD US, WD, EU IC US, WD, EU US, WD, EU US, WD, EU US, WD, EU US, WD, EU, JP US, WD, EU, JP US, WD, EU US, WD IC US, WD, EU MP-825-SUR-100 US, WD MP-825-CPE-50 US, WD, EU 3.2.1 (901050) 3.2.1 (901050) 3.2.1 (901050) 3.2.1 (901050) 3.2.1 (901050) 3.2.1 (901050) 3.3.0 (905192) 3.3.0 (905192) 3.3.0 (905192) 3.2.1 (901050) 3.2.1 (901050) 3.2.1 (901050) 3.2.1 (901050) 3.2.1 (901050) 3.3.0 (905192) 3.3.0 (905192) 3.3.0 (905192) 3.3.0 (905192) 3.3.0 (905192) 3.3.0 (905192) Tsunami 800 & 8000 Series - Software Management Guide 10 Product(s) Supported Countries Supported Software Version Preface MP-825-CPE-100 MP-835-CPE-10 MP-835-CPE-25 MP-835-CPE-50 MP-835-CPE-100 US, WD, EU US, WD, EU US, WD, EU US, WD, EU US, WD, EU QB-8200-EPA-G/LNK-G US, WD, EU QB-8250-EPR-G/LNK-G US, WD, EU QB-8200-EPA/LNK QB-8250-EPR/LNK QB-825-EPR/LNK-50+
QB-825-EPR/LNK-100 QB-835-EPR/LNK-25 QB-835-EPR/LNK-50 US, WD, EU US, WD, EU US, WD, EU US, WD US, WD US, WD QB-826-EPR/LNK-100 WD 3.3.0 (905192) 3.3.0 (905192) 3.3.0 (905192) 3.3.0 (905192) 3.3.0 (905192) 3.2.1 (901050) 3.2.1 (901050) 3.2.1 (901050) 3.2.1 (901050) 3.3.1 (905201) 3.3.1 (905201) 3.3.1 (905201) 3.3.1 (905201) 3.3.1 (905201) Audience The intended audience for this guide is the network administrators who install and/or manage the device. Prerequisites The reader of this document should have working knowledge of Wireless Networks, Local Area Networking (LAN) concepts, Network Access Infrastructures and Client-Server Applications. Related Documents For more information, please refer to the following additional documents that are available at Proxims support site http://my.proxim.com. Quick Installation Guide (QIG): A quick reference guide that provides essential information for installing and configuring the device. Hardware Installation Guide: A guide that provides a hardware overview and details about the installation procedures and hardware specifications. Reference Guide: A guide that provides essential information on how to configure, manage and monitor the device using the Command Line Interface. Safety and Regulatory Compliance Guide: A guide that provides essential information on the country specific safety and regulatory norms to be followed while installing the device. Antenna Recommendation Guide - A guide that gives insight on the recommended antennas for the device, along with the antenna specifications. Antenna Installation Guide - A guide that gives insight on how to set up and install the outdoor antenna(s). Proxim recommends you to visit its support site http://my.proxim.com for regulatory information and latest product updates. Tsunami 800 & 8000 Series - Software Management Guide 11 Preface Documentation Conventions Icon Representation Name Image Meaning Note Important Caution A special instruction that draws attention of a user. A note of significant importance that the user should be aware of. A warning that cautions the user of a possible danger. Tsunami 800 & 8000 Series - Software Management Guide 12 1 Overview This chapter contains information on the following:
About Tsunami 800 and 8000 Products Wireless Network Topology Point-to-Multipoint (PTMP) Point-to-Point Link Multiple-Input-Multiple-Output (MIMO) Wireless Outdoor Router Protocol (WORP) 1.1 About Tsunami 800 and 8000 Products Proxims Tsunami 800 and 8000 product series, consists of point-to-point and point-to-multipoint devices that are designed to provide wireless networking solutions to enterprises and business markets. This product series consists of the following products:
Product MP-8200-BSU-G MP-8250-BS9-G MP-8250-BS1-G MP-8200-BSU MP-8250-BS9 MP-8250-BS1 MP-820-BSU-100 Description Image The MP-8200 Base Station unit, is a flexible wireless outdoor product that operates in 4.900 to 5.925 GHz frequency band. This connectorized device comes with GPS Sync ready, a 3x3 MIMO high power radio and three N-Type connectors to connect external antennas. The MP-8250 Base Station unit comes with GPS Sync ready, a high power 2x2 MIMO radio and 16 dBi integrated 90 sector antenna that operates in 4.900 5.925 GHz frequency band. The MP-8250 Base Station unit comes with GPS Sync ready, a high power 2x2 MIMO radio and 23 dBi integrated 10 panel antenna that operates in 4.900 5.925 GHz frequency band. The MP-8200 Base Station unit is a flexible wireless outdoor product that operates in 4.900 to 5.925 GHz frequency band. This connectorized device comes with a 3x3 MIMO high power radio and three N-Type connectors to connect external antennas. The MP-8250 Base Station unit comes with a high power 2x2 MIMO radio and 16 dBi integrated 90 sector antenna that operates in 4.900 5.925 GHz frequency band. The MP-8250 Base Station unit comes with a high power 2x2 MIMO radio and 23 dBi integrated 10 panel antenna that operates in 4.900 5.925 GHz frequency band. The MP-820 Base Station unit, is a flexible wireless outdoor product that operates in 4.900 to 5.925 GHz frequency band. This connectorized device comes with GPS Sync Ready, a 2x2 MIMO radio and two N-Type connectors to connect external antennas. It provides an aggregate throughput of 100 Mbps. Tsunami 800 & 8000 Series - Software Management Guide 13 Overview Image Product MP-822-BSU-100 MP-825-BS3-100 Description The MP-822 Base Station unit, is a flexible wireless outdoor product that operates in 4.900 to 5.925 GHz frequency band. This connectorized device comes with a 2x2 MIMO radio and two N-Type connectors to connect external antennas. It provides an aggregate throughput of 100 Mbps. The MP-825 Base Station unit comes with GPS Sync Ready, a 2x2 MIMO radio and 15 dBi integrated dual-polarized panel antenna that operates in 4.900 to 5.925 GHz frequency band. It provides an aggregate throughput of 100 Mbps. MP-8100-SUA MP-8150-SUR The MP-8100 Subscriber unit, is a flexible wireless outdoor product that operates in 2.3 2.5 and 4.9 6.0 GHz frequency band. This connectorized device comes with a 3x3 MIMO radio and three N-Type connectors to connect external antennas. The MP-8150 Subscriber unit comes with a 2x2 MIMO radio and 23 dBi Integrated dual-polarized panel antenna that operates in 4.900 5.925 GHz frequency band. MP-8150-SUR-100 MP-8200-SUA The MP-8150 Subscriber unit comes with a 2x2 MIMO radio and 21 dBi integrated dual-polarized panel antenna that operates in 4.900 5.875 GHz frequency band. It provides a throughput of up to 50 Mbps (Uplink) and 50 Mbps (Downlink). The MP-8200 Subscriber unit, is a flexible wireless outdoor product that operates in 4.900 to 5.925 GHz frequency band. This connectorized device comes with a 3x3 MIMO high power radio and three N-Type connectors to connect external antennas. MP-8250-SUR The MP-8250 Subscriber unit comes with a 2x2 MIMO high power radio and 23 dBi integrated dual-polarized panel antenna that operates in 4.900 5.925 GHz frequency band. MP-820-SUA-50+
MP-820-SUA-100 MP-822-SUA-100 The MP-820 Subscriber unit, is a flexible wireless outdoor product that operates in 4.900 to 5.925 GHz frequency band. This connectorized device comes with a 2x2 MIMO radio and two N-Type connectors to connect external antennas. It provides an aggregate throughput of 50 Mbps, license upgradable to 100 Mbps. The MP-820 Subscriber unit, is a flexible wireless outdoor product that operates in 4.900 to 5.925 GHz frequency band. This connectorized device comes with a 2x2 MIMO radio and two N-Type connectors to connect external antennas. It provides an aggregate throughput of 100 Mbps. The MP-822 Subscriber unit, is a flexible wireless outdoor product that operates in 4.900 to 5.925 GHz frequency band. This connectorized device comes with a 2x2 MIMO radio and two N-Type connectors to connect external antennas. It provides an aggregate throughput of 100 Mbps. Tsunami 800 & 8000 Series - Software Management Guide 14 Overview Image Product MP-825-SUR-50+
MP-825-SUR-100 MP-825-CPE-50 MP-825-CPE-100 MP-835-CPE-10 MP-835-CPE-25 MP-835-CPE-50 MP-835-CPE-100 QB-8200-EPA-G Description The MP-825 Subscriber unit comes with a 2x2 MIMO radio and 15 dBi integrated dual-polarized panel antenna that operates in 4.900 to 5.925 GHz frequency band. It provides an aggregate throughput of 50 Mbps, license upgradable to 100 Mbps. The MP-825 Subscriber unit comes with a 2x2 MIMO radio and 15 dBi integrated dual-polarized panel antenna that operates in 4.900 to 5.925 GHz frequency band. It provides an aggregate throughput of 100 Mbps. The MP-825 Customer Premises Equipment comes with a 2x2 MIMO radio and 15 dBi integrated dual-polarized panel antenna that operates in 4.900 to 5.925 GHz frequency band with aggregate throughput of 50 Mbps. The MP-825 Customer Premises Equipment comes with a 2x2 MIMO radio and 15 dBi integrated dual-polarized panel antenna that operates in 4.900 to 5.925 GHz frequency band with an aggregate throughput of 100 Mbps. The MP-835 Customer Premises Equipment comes with a 2x2 MIMO radio and 15 dBi integrated dual-polarized panel antenna that operates in 4.900 to 5.925 GHz frequency band with an aggregate throughput of 10 Mbps. The MP-835 Customer Premises Equipment comes with a 2x2 MIMO radio and 15 dBi integrated dual-polarized panel antenna that operates in 4.900 to 5.925 GHz frequency band with an aggregate throughput of 25 Mbps. The MP-835 Customer Premises Equipment comes with a 2x2 MIMO radio and 15 dBi integrated dual-polarized panel antenna that operates in 4.900 to 5.925 GHz frequency band with an aggregate throughput of 50 Mbps. The MP-835 Customer Premises Equipment comes with a 2x2 MIMO radio and 15 dBi integrated dual-polarized panel antenna that operates in 4.900 to 5.925 GHz frequency band with an aggregate throughput of 100 Mbps. The QB-8200-EPA-G QuickBridge operates in 4.900 5.925 GHz frequency band. This connectorized device comes with GPS Sync ready, a 3x3 MIMO high power radio and three N-Type connectors to connect external antennas. QB-8200-LNK-G A pair of QB-8200-EPA-G -G devices form a link. Tsunami 800 & 8000 Series - Software Management Guide 15 Product QB-8250-EPR-G Description The QB-8250-EPR QuickBridge comes with GPS Sync ready, a 2x2 MIMO high power radio and 23 dBi integrated dual-polarized panel antenna that operates in 4.900 5.925 GHz frequency band. QB-8250-LNK-G A pair of QB-8250-EPR-G devices form a link. Overview Image QB-8200-EPA The QB-8200-EPA QuickBridge operates in 4.900 5.925 GHz frequency band. This connectorized device comes with a 3x3 MIMO high power radio and three N-Type connectors to connect external antennas. QB-8200-LNK A pair of QB-8200-EPA devices form a link. QB-8250-EPR The QB-8250-EPR QuickBridge comes with a 2x2 MIMO high power radio and 23 dBi integrated dual-polarized panel antenna that operates in 4.900 5.925 GHz frequency band. QB-8250-LNK A pair of QB-8250-EPR devices form a link. QB-825-EPR-50+
The QB-825-EPR-50+ device comes with GPS Sync Ready, a 2x2 MIMO high power radio and 15 dBi integrated dual-polarized panel antenna that operates in 4.900 to 5.925 GHz frequency band. It provides an aggregate throughput of 50 Mbps, license upgradable to 100 Mbps. QB-825-LNK-50+
A pair of QB-825-EPR-50+ devices form a link. QB-825-EPR-100 The QB-825-EPR-100 device comes with a 2x2 MIMO high power radio and 15 dBi integrated dual-polarized panel antenna that operates in 4.900 to 5.925 GHz frequency band. It provides an aggregate throughput of100 Mbps. Tsunami 800 & 8000 Series - Software Management Guide 16 Product Description QB-825-LNK-100 A pair of QB-825-EPR-100 devices form a link. Overview Image QB-835-EPR-25 The QB-835-EPR-25 device comes with a 2x2 MIMO radio and 15 dBi integrated dual-polarized panel antenna that operates in 4.900 to 5.925 GHz frequency band with aggregate throughput of 25 Mbps License upgradable to 50 Mbps. QB-835-LNK-25 A pair of QB-835-EPR-25 devices form a link. QB-835-EPR-50 The QB-825-EPR-50 device comes with a 2x2 MIMO high power radio and 15 dBi integrated dual-polarized panel antenna that operates in 4.900 to 5.925 GHz frequency band with aggregate throughput of 50 Mbps. QB-835-LNK-50 A pair of QB-835-EPR-50 devices form a link. QB-826-EPR-100 The QB-826-EPR-100 device comes with a 2x2 MIMO high power radio and 15 dBi integrated dual-polarized panel antenna that operates in 5.900 6.425 GHz frequency band. It provides an aggregate throughput of 100 Mbps. QB-826-LNK-100 A pair of QB-826-EPR-100 devices form a link. Tsunami 800 & 8000 Series - Software Management Guide 17 Overview 1.2 Wireless Network Topology 1.2.1 Point-to-Multipoint (PTMP) Point-to-multipoint is a wireless network that has a central communication device such as a Base Station Unit (BSU), providing connectivity to multiple devices such as Subscribers (SUs) or clients. Any transmission of data that originates from the BSU is received by all SUs; whereas, the data originating from any of the SU is received only by the BSU. This allows numerous sites in a wide area to share resources, including a single high-speed connection to the Internet. Given below are the deployment scenarios, where Proxim's point-to-multipoint devices are recommended. The Proxim devices used in the deployment images are commonly referred to as BSU (Base Station Unit) and SU (Subscriber Unit). The combinations that are used for BSU and SU multipoint devices are:
Base Station Unit Subscriber Unit
(BSU)
(SU) MP-822-BSU-100 MP-822-SUA-100 MP-8200-BSU-G MP-8250-BS9-G MP-8250-BS1-G MP-8200-BSU MP-8250-BS9 MP-8250-BS1 MP-820-BSU-100 MP-825-BS3-100 MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 MP-8200-SUA MP-8250-SUR MP-820-SUA-50+
MP-820-SUA-100 MP-825-SUR-50+
MP-825-SUR-100 MP-825-CPE-100 MP-825-CPE-50 MP-835-CPE-10 MP-835-CPE-25 MP-835-CPE-50 MP-835-CPE-100 Last Mile Access: Competitive broadband service access alternative to Digital Subscriber Line (DSL) or cable for residences and T1 or Ethernet for businesses. Tsunami 800 & 8000 Series - Software Management Guide 18 Overview Security and Surveillance: High definition IP-surveillance cameras for monitoring city streets, airports, bridges, seaports, transportation hubs, offices and warehouses. Tsunami 800 & 8000 Series - Software Management Guide 19 Metropolitan Area Network: Secure and reliable connectivity between city buildings. Overview Enterprise Campus Connectivity: Extend the main network to remote offices, warehouses or other buildings without leased lines. Tsunami 800 & 8000 Series - Software Management Guide 20 Wireless Intelligent Transport System (ITS): Increases the traffic efficiency and reduces the commuting time in cities and metropolitan areas. Overview Roaming: A mobile device (SU) provides seamless network services. Tsunami 800 & 8000 Series - Software Management Guide 21 Offshore Communications: Establishes connectivity between seashore and the ships that are nearing the port locations, or connectivity between off-shore oil rigs and sea shore and so on. Overview 1.2.2 Point-to-Point Link A point-to-point link is a dedicated wireless link that connects only two stations. With a point-to-point link, you can set up a connection between two locations as an alternative to:
Leased lines in building-to-building connections Wired Ethernet backbones between wireless access points in difficult-to-wire environments. It is easy to set up a wireless point-to-point link as shown in the following figure. Each device is set up as either an End Point A or an End Point B. Figure 1-1 Point-to-Point-Link (An Example) Tsunami 800 & 8000 Series - Software Management Guide 22 Given below are the deployment scenarios, where Proxim's point-to-point devices are recommended. The proxim devices used in the deployment images are commonly referred to as End Point A and End Point B. The combinations that are used for point-to-point devices are:
Overview End Point A End Point B QB-8200-EPA-G/QB-8200-EPA QB-8200-EPA-G/QB-8200-EPA QB-8250-EPR-G/QB-8250-EPR QB-825-EPR-50+
QB-8250-EPR-G/QB-8250-EPR QB-825-EPR-50+
QB-825-EPR-100 QB-835-EPR-25 QB-835-EPR-50 QB-826-EPR-100 QB-825-EPR-100 QB-835-EPR-25 QB-835-EPR-50 QB-826-EPR-100 Listed below are the applications, where Proxims point-to-point devices can be used:
Backhaul to a Central POP: Avoids expensive installation and recurring charge of a second wireline backhaul to a remote virtual POP. Tsunami 800 & 8000 Series - Software Management Guide 23 Repeater: Extends distance or overcomes path blockage by adding point-to-point hops. Overview High-bandwidth Last Mile Access: Delivers Transparent LAN Services (TLS) to corporate parks. High Availability and Link Aggregation: Achieves high availability and link aggregation in wireless medium by using two parallel links and additional Link Aggregation Control Protocol (LACP) capable switches. This is applicable only to QB-8200-EPA-G/LNK-G, and QB-8250-EPR-G/LNK-G devices. Tsunami 800 & 8000 Series - Software Management Guide 24 Leased Line Redundancy: Eliminates recurring DS-3 leased line charges with one time installation charge of a QuickBridge link. Inter-POP Redundancy: Avoids downtimes caused by a wireline backhaul failure by adding a QuickBridge link as an inter-POP redundancy. Overview 1.3 Multiple-Input-Multiple-Output (MIMO) Proxims 800 & 8000 point-to-point and point-to-multipoint devices support Multiple-Input-Multiple-Output (MIMO) antenna technology that uses multiple antennas at both the transmitter and receiver to improve communication performance. The underlying technology of Proxims product radio(s) are based on a combination of MIMO and OFDM (Orthogonal Frequency Division Multiplexing). MIMO-OFDM combination radios solve interference, fading and multipath problems On the receiver side, having multiple receivers increases the amount of received power and also reduces multipath problems by combining the received signals for each frequency component separately. Hence, MIMO significantly improves the overall gain. MIMO also uses Spatial multiplexing transmission technique to transmit independent and separately encoded data signals from each of the multiple transmit antennas while reusing or multiplexing in the space dimension. These independent data signals are called Spatial streams. The transmitting antenna uses multiple radio Tx chains and signal paths to simultaneously transmit different data streams, whereas the receiver combines the Rx signals resulting in higher throughput. By increasing the number of receiving and transmitting antennas, the throughput of the channel increases linearly resulting in high spectral efficiency. 1.4 Wireless Outdoor Router Protocol (WORP) WORP is a protocol, designed by Proxim to optimize the performance of outdoor wireless Point-to-Point (PtP) and Point-to-Multipoint edge Multiple-Input-Multiple-Output (MIMO) technology. links using packet the use of technology, including cutting
(PtMP) radio WORP overcomes the performance degradation, which standards-based wireless technologies are susceptible to when used for outdoor long-range connectivity. Benefits:
More Net Bandwidth: WORP increases the overall net bandwidth of the multipoint system. The net bandwidth by using WORP is higher than any other protocol solution used in an outdoor environment. WORP is a more efficient protocol that protects the system from packet collisions and transmits the data in an optimal way, which increases the overall performance. More Concurrent Subscribers: An outdoor point-to-multipoint solution based on 802.11 may connect from 5 to 10 remote nodes, but sometimes performance starts to suffer from collisions with as little as only 2 remote nodes. A solution using WORP, on the other hand, can connect up to 100 remote nodes without adverse effects on usable bandwidth, allowing more concurrent Subscriber Units (SU) to be active in a wireless multipoint environment. Smart Scheduling: WORP uses smart scheduling for remote node polling to avoid wasting bandwidth on nodes that have no traffic to be sent. The Base Station Unit (BSU) dynamically decides how frequently a remote node should be polled based on the current traffic to and from each remote node and the priority settings for that traffic. The scheduling is adapted dynamically to the actual traffic and further optimized by following the bandwidth limits as configured for each remote node. Dynamic Data Rate Selection (DDRS): DDRS enables WORP to dynamically adjust the data rate at which the wireless traffic is sent. This feature is especially important in point-to-multipoint networks, when different SUs can sustain different data rates because of the different distances from the BSU. With DDRS, WORP dynamically optimizes the wireless data rate to each of the SUs independently, keeping the overall net throughput at the highest possible level. This feature optimizes throughput even for links with different RF conditions on the BSU and SU, by optimizing downlink. Tsunami 800 & 8000 Series - Software Management Guide 25 Quality of Service: WORP ensures that the most important data arrives with priority by differentiating between priorities of traffic as defined in the profiles for QoS (Quality of Service), similar to the 802.16 WiMAX QoS standard definition. Bandwidth Control: WORP allows service providers to control network bandwidth by throttling outgoing traffic in both base station and subscriber devices, thus protecting the network from excessive bandwidth use by any one station. Additionally, it allows service providers to differentiate their service offerings. Asymmetric Bandwidth Controls: Asymmetric bandwidth gives network managers the ability to set different maximum bandwidth rates for a variety of customer groups. This allows service providers to further differentiate their service offerings and maximize revenues. Overview Tsunami 800 & 8000 Series - Software Management Guide 26 2 Management and Monitoring Capabilities A Network administrator can use the following interfaces to configure, manage and monitor the device. Web (HTTP/HTTPS) Interface Command Line Interface Simple Network Management Protocol (SNMP) Management PV Advanced 2.1 Web (HTTP/HTTPS) Interface The Web interface (HTTP) provides easy access to configuration settings and network statistics from any computer on the network. The Web interface can be accessed, through LAN (switch, hub and so on), the Internet, or with an Ethernet cable connected directly to the computers Ethernet port. HTTPS interface provides an HTTP connection over a Secure Socket Layer (SSL). HTTPS allows the user to access the device in a secure fashion by using SSL over port 443. The device supports SSLv3 with a 128-bit encryption certificate maintained by the device for secure communication between the device and the HTTP client. All communications are encrypted by using the server and the client-side certificate.
:
Compatible browser for Web Interface:
Microsoft Internet Explorer 7.0 or later Mozilla Firefox 3.0 or later When working with Internet Explorer 9 in Windows 2008 Server, navigate to Internet Options -> Security ->
Internet -> Custom Level -> Scripting -> Active Scripting to enable active scripting. When working with Internet Explorer 10 and facing web page issues, click the Broken Page icon available on the right side of the address bar. 2.2 Command Line Interface The Command Line Interface (CLI) is a text-based configuration utility that supports a set of keyboard commands and parameters to configure, manage and monitor the device. You can enter the command statements composed of CLI commands and their associated parameters. For example, when downloading a file, an administrator enters the download CLI command along with the IP address, file name, and file type parameters. Commands can be issued from the keyboard for real-time control, or from scripts that automate configuration. 2.2.1 HyperTerminal The CLI can be accessed over a HyperTerminal serial connection. HyperTerminal is a program that connects to other Computers, Telnet Sites, Bulletin Board Systems (BBS), Online Services, and Host Computers, by using either modem or a null modem cable. Tsunami 800 & 8000 Series - Software Management Guide 27 If using RS-232 cable, verify the following information in the HyperTerminal serial port setup:
Management and Monitoring Capabilities Port COM1 (default) Baud Rate 115200 Data Parity Stop Flow Content 8-bit None 1-bit None
: When using Windows 7, use a Terminal Emulator program like Teraterm Pro for serial connection. 2.2.2 Telnet The device can be accessed through CLI by using Telnet. The device can be accessed through LAN (switch, hub and so on), the Internet, or with an Ethernet cable connected directly to the computers Ethernet port. 2.2.3 Secure Shell (SSH) The device can be securely accessed through CLI by using Secure Shell (SSH). The device supports SSH version 2, for secure remote CLI (Telnet) sessions. SSH provides strong authentication and encryption of session data. The SSH server has host keys
- a pair of asymmetric keys (a private key that resides on the device) and a public key that is distributed to the clients, to connect to the device. Clients need to verify that they are communicating with the correct SSH server. 2.3 Simple Network Management Protocol (SNMP) Management The device can also be configured, managed and monitored by using Simple Network Management Protocol (SNMP). This requires an SNMP Manager Program (sometimes called MIB browser) or a Network Manager program using SNMP. The device supports the following Management Information Base (MIB) files that describe the parameters that can be viewed and/or configured over SNMP:
PXM-SNMP.mib (Enterprise MIB) RFC-1213.mib (MIB-II) RFC-1215.mib (Trap MIB) RFC-1757-RMON.mib (Remote Monitoring) RFC-2571.mib (SNMP Framework) RFC-3411-SNMP-FRAME-WORK.mib (SNMP Framework) RFC-2790.mib (Host Resources) RFC-3291-INET-ADDRESS-MIB.mib RFC-3412.mib (SNMP-MPD-MIB) RFC-3414.mib (SNMP-USER-BASED-SM-MIB) SFLOW.mib Before managing the device by using SNMP, compile one or more of these MIB files into your SNMP programs database. Tsunami 800 & 8000 Series - Software Management Guide 28 The PXM MIB files are available on the Proxim support site at http://my.proxim.com. The enterprise MIB (PXM-SNMP.mib) defines the Read and Read/Write objects that can be viewed or configured by using SNMP. These objects correspond to most of the settings and statistics that are available with other management interfaces. The MIB can be opened with any text editor, such as Microsoft Word, Notepad, or WordPad. Management and Monitoring Capabilities 2.4 PV Advanced PV Advanced is the state-of-the-art network management system to administer Proxims devices on the network. PV Advanced offers the following network management and monitoring features:
Network Management --> Network Discovery, Geographical and Logical Maps Fault Management --> Event Logs and Alarms Performance Management --> Statistics Collection and Analysis Security Management --> User Provisioning Scheduled Bulk Operations and Task - Backup, Software Upgrade, and Bulk SNMP Parameter Configuration Configuration Management --> Device Configuration For details, refer to PV Advanced Installation and Management Guide at http://my.proxim.com.
: This guide explains the method to initialize and manage the device by using Web Interface only. To configure and manage the device by using Command Line Interface, please refer to the Tsunami 800
& 8000 Series Reference Guide available on the Proxims support site at http://my.proxim.com. Tsunami 800 & 8000 Series - Software Management Guide 29 3 Device Initialization This chapter contains information on the following:
Initialization ScanTool Initialize Device by using ScanTool Modifying the IP Address of the Device by using ScanTool Logging onto the Web Interface Home Page COMMIT REBOOT Factory Default Configuration 3.1 Initialization Once the device installation completes, access the device either through Web Interface, Command Line Interface, or an SNMP Interface.
: For installation procedure, please refer to the Hardware Installation Guide available on the Proxims support site at http://my.proxim.com. To access the device by using CLI commands, connect a serial RS-232 cable to the Serial port of the device. To access the device by using Web or SNMP interface, connect an Ethernet cable to the Ethernet port of the device. For all the modes of connection, the IP address of the device should be configured. As each network is different, a suitable IP address on the network must be assigned to the device. This IP address helps to configure, manage and monitor the device by using Web Interface, SNMP, or Telnet/CLI. The device can be assigned a static/dynamic/auto IP address. When set to static, the user has to set the IP address manually; if set to dynamic, the IP address is obtained dynamically from the Dynamic Host Configuration Protocol (DHCP) server. By default, the device IP Address is set to 169.254.128.132. In case of QB-8250-LNK-G/QB-8250-LNK, the factory configured IP address for End Point B is 169.254.128.131. If required, the end user can change it to the default IP address.
: MP-825-CPE-50, MP-825-CPE-100, MP-835-CPE-10, MP-835-CPE-25, MP-835-CPE-50, MP-835-CPE-100 and QB-826-EPR/LNK-100 devices does not have a Serial Port. However, the user has the flexibility to configure, manage and monitor the device through command mode via Telnet. 3.1.1 ScanTool Proxims ScanTool (Answer ID - 1735) is a software utility that runs on Microsoft Windows machine. By using ScanTool, a user can, Scan devices (Proxim devices only) available on the network ScanTool v3.0.1 scans devices based on IPv4 or IPv6 address Obtain devices IP address Modify devices IP Configuration parameters (IP Address, Address Type, Gateway and so on) Tsunami 800 & 8000 Series - Software Management Guide 30 Launch the Web interface Switch between the network adapters, if there are multiple network adapters in the Personal Computer Device Initialization
:
IPv6 is supported only by ScanTool v3.0.1 and higher versions. Network Adapter of ScanTool supports up to 16 virtual / real interfaces Disable Windows Firewall (or add an exception) for ScanTool to function or to detect the radio. 3.1.2 Initialize Device by using ScanTool To scan and locate the devices on a network by using ScanTool, do the following:
1. Power on, or reset the device. 2. To download Proxims ScanTool, log on to Proxims support site at http://my.proxim.com and search for ScanTool with 3.
(Answer ID 1735). Upon successful download, double-click the icon to start the ScanTool. If there are more than one network adapter installed on the computer, then the user will be prompted to select the adapter for scanning Proxim devices. Use an Ethernet adapter. Select an adapter and click OK. The following Scan List screen appears, which displays all devices that are connected to the selected adapter. Figure 3-1 Scan List - Scanned Devices (IPv4) Figure 3-2 Scan List - Scanned Devices (IPv6) This screen contains the following device information:
MAC Address Tsunami 800 & 8000 Series - Software Management Guide 31 Device Initialization IP Address System Name Uptime System Description: The system description comprises the following information:
Device Description: For example, MP-820-BSU-100-WD Firmware Version: 2.X.Y; For example, version 2.6.2 Serial Number : For example, SN-12PI06000034 Bootloader Version: For example, BL - V1.0.4 4. Click Select Adapter, to change adapter settings. 5. From the list, identify and select the MAC address of the device that needs to be initialized, and click Web Config to log on to the Web Interface.
: If the device does not appear in the Scan List, click Rescan in the Scan List screen. If the device still does not appear in the list, see Troubleshooting. Note that after rebooting the device, it may take up to five minutes for the device to appear in the Scan List. 3.1.3 Modifying the IP Address of the Device by using ScanTool To modify the IP address of a device by using ScanTool, select the device from the scan list and click Change. A Change screen appears as shown in the following screen. The system automatically populates the MAC Address, System Name, TFTP Server IP Address and Image File Name of the device, which are read-only. Figure 3-3 Modifying Devices IP Address (IPv4) Tsunami 800 & 8000 Series - Software Management Guide 32 Device Initialization Figure 3-4 Modifying Devices IP Address (IPv6) 1. Select the IP Address Type as static/dynamic for IPv4 and as static/dynamic/auto for IPv6 Static: When set to static, the IP address of the device can be manually changed. Dynamic: When set to dynamic, the IP address is dynamically generated by the DHCP server. Auto: When set to auto, the IPv6 address is calculated by the device using the router advertisement messages. 2. Type the appropriate IP Address, Subnet Mask, and the Gateway IP Address parameters. 3. Enter the SNMP Read/Write password in the Read/Write Password box. By default, it is public. 4. Click OK to save the details. The device automatically reboots. To log on to the Web Interface, click Web Configuration. The user is then prompted to enter its username and password. For more information on how to logon, please see Logging onto the Web Interface. 3.2 Logging onto the Web Interface Once the device is connected to the network, use a web browser to configure, manage and monitor the device. Enter the default IP address of the device (For example, http://169.254.128.132) in the address bar or access the Web Interface using ScanTool (see Initialization). The user is now prompted to enter its username and password. Tsunami 800 & 8000 Series - Software Management Guide 33 Device Initialization Figure 3-5 Login Screen Based on the access credentials, two types of users can access the device. They are, 1. Administrator User: The Administrator user administers the entire device. This user type has the write access to all the features of the device and also has the privilege to change his or her own password and that of the Monitor user
(the other user type). To change the password, refer to Services. 2. Monitor User - The Monitor user has only view access to all the features of the device. This user is restricted from the following privileges:
Change the device functionality Change his or her own password Run any of the test tools like Wireless Site Survey and so on. However, the user can view the logs and statistics of the test tools. Run the Spectrum Analyzer. However, the user can view the last scanned results. The Monitor user has the privilege to retrieve event logs and temperature logs for debugging. To logon to the device, 1. Type a valid user name in the User Name box. The user name is admin for the Administrator user and monitor for the Monitor user. 2. Type the password in the Password box. By default, the password is public for both the Administrator user and the Monitor user.
:
By default the password is public. For security reasons, it is recommended to change the password after the first logon to the device. Depending on the settings made during the device initialization, the IP address may be either a dynamic IP address assigned by a network DHCP server or a static IP address which is manually configured. Refer to ScanTool for information on how to determine the devices IP address and manually configure a new IP address. If the connection is slow or unable to connect, use the Internet Explorer Tools option to ensure that the proxy server is not used for the connection. If unable to log on to the configuration pages by using default user name and password, please check with the administrator or follow Recovery Procedures. While using Internet Explorer, if wrong password is entered consecutively for three times, the HTTP session will get disconnected. If case of other browsers, the login screen will reset until a correct password is entered. In the Internet Explorer, to get best results, click on Tools > Internet Options > General. Click Settings in the Browsing History and select Every visit to the webpage. Tsunami 800 & 8000 Series - Software Management Guide 34 For QB-8xx products, three types of user can access the device; Administrator, Monitor and Advanced. Refer Tsunami Quickbridge 800 Series User Guide available at http://my.proxim.com for more details. Device Initialization 3.2.1 Home Page Upon successful logon, the device home page appears. The home page contains the following information:
Figure 3-6 Home Page Device Description: The device description is displayed on the top-right corner of the home page. It displays the logged in user type and the device name along with the latest firmware version and build number. System Summary: The System Summary screen displays the summary of system information such as System Name, IP Address, Radio Mode, Interface Status, Event Log, Sync Status, and so on. Sync Status: The glowing LED in this field displays the Sync status. The LED behavior for Sync mode is tabulated below:
Sync LED Behavior Sync Status OFF (Grey) Synchronous mode is disabled or the device is out of Sync Blinking (Green-Fast) Synchronous mode is enabled, but Sync signal is not received ON (Solid-Green) Synchronous mode is enabled and Sync signal is received COMMIT Button: See COMMIT Tsunami 800 & 8000 Series - Software Management Guide 35 Device Initialization REBOOT Button: See REBOOT HOME: Display system summary screen. BASIC CONFIGURATION: The BASIC CONFIGURATION tab allows the user to configure the minimum set of parameters required for a device to be operational and establish a link on the network. For more details, see Basic Configuration. ADVANCED CONFIGURATION: The ADVANCED CONFIGURATION tab allows the user to configure the advanced parameters of the device. For more details, see Advanced Configuration. MANAGEMENT Tab: The MANAGEMENT tab allows the user to manage the device. For more details, see Management. MONITOR Tab: The MONITOR tab allows the user to monitor the device. For more details, see Monitor. 3.2.2 COMMIT COMMIT operation is used to apply the configuration changes onto the device. When changes are made to the configuration parameters of the device, the changes will not take effect, until COMMIT is clicked. Some parameters may require system reboot for the changes to take effect. On clicking COMMIT, the system evaluates all the configuration dependencies and displays the configuration status. Before applying commit, the system displays a confirmation message, as shown in the following figure:
Click OK, to confirm the changes. On successful COMMIT operation, the following screen appears:
Figure 3-7 Commit If the configured parameters requires reboot, on committing the following screen appears. Figure 3-8 Commit Status Tsunami 800 & 8000 Series - Software Management Guide 36 Figure 3-9 Commit Status with Reboot Message Device Initialization 3.2.3 REBOOT Reboot operation is required for any change in the key parameters to take effect. For example, settings such as configuring the Radio Mode, IP Address, Network Mode and so on, require device reboot for the changes to take effect. It is recommended that the device must be rebooted immediately after modifying a rebootable parameter. On clicking Reboot, system displays a confirmation window, as shown below.
: It is always mandatory to commit the changes before REBOOT, otherwise the changes will not take effect. Figure 3-10 Reboot To reboot the device, click OK. 3.3 Factory Default Configuration Parameter BSU Mode/
End Point A SU Mode/
End Point B User Password System Name Network Mode Routing IP Mode IP Address Subnet Mask Address Type Gateway IP Address Network Name Secondary BSU Name DNS Proxy Legacy Mode public System-Name Bridge Disabled IPv4 Only 169.254.128.132 255.255.255.0 Static 169.254.128.132 MY_NETWORK Not Applicable public System-Name Bridge Disabled IPv4 Only 169.254.128.131 255.255.255.0 Static 169.254.128.132 MY_NETWORK SU - Blank (Secondary BSU name is not configured) End Point B - Not Applicable Enabled Enabled BSU - Disabled End Point A - Not Applicable SU - Disabled End Point B - Not Applicable Tsunami 800 & 8000 Series - Software Management Guide 37 Device Initialization SU Mode/
End Point B Not Applicable 10 Seconds Default Link Profile Enabled As per license As per license BSU - Disabled End Point A - Not Applicable SU - Disabled End Point B - Not Applicable Enabled with profile name WORP Security Enabled with profile name WORP Security Parameter BSU Mode/
End Point A Maximum Number of SUs (per BSU) MP-8200-BSU-G/ MP-8200-BSU --> 250 MP-8250-BS9-G/ MP-8250-BS9 --> 250 MP-8250-BS1-G/ MP-8250-BS1--> 250 MP-820-BSU-100 -->32 MP-822-BSU-100 -->32 MP-825-BS3-100 -->32 Registration Timeout 10 Seconds Link Profiles DDRS Input Bandwidth Limit Output Band Limit Roaming Security Profile RADIUS Profile MAC Authentication RADIUS MAC Authentication Channel Bandwidth Active Channel Selection ATPC Network Secret QoS Management VLAN VLAN Status Default Link Profile Enabled As per license As per license Enabled with profile name Default Radius Disabled Disabled 20 MHz Disabled Enabled public Unlimited BE Disabled Disabled VLAN Mode (Ethernet) Transparent Allow Untagged Management Access Disabled Disabled Disabled Global Filtering DHCP Server STP/LACP DHCP Relay IGMP Snooping Not Applicable Not Applicable Not Applicable 20 MHz Enabled Enabled public Not Applicable Disabled Disabled Transparent Disabled Disabled Disabled Enabled (configured as passthru) Enabled (configured as passthru) Disabled Disabled Disabled Disabled Tsunami 800 & 8000 Series - Software Management Guide 38 Device Initialization Parameter BSU Mode/
End Point A SU Mode/
End Point B RIP NAT PPPoE Client Disabled Disabled Not Applicable HTTP Management Interface Telnet Management Interface Enabled Enabled Disabled Disabled Disabled in SU Mode Not Applicable in End Point B Enabled Enabled SNMP Management Interface Enabled with SNMPv1-v2c Enabled with SNMPv1-v2c Simple Network Time Protocol (SNTP) Disabled Management Access Control Event Log Priority SysLog Status SysLog Priority LED Display Status Disabled Notice Enabled Critical Disabled Disabled Notice Enabled Critical RSSI Enabled RSSI Enabled Tsunami 800 & 8000 Series - Software Management Guide 39 Basic Configuration 4 The BASIC CONFIGURATION tab provides a one-place access to a minimum set of configuration parameters to quickly set up a Point-to-point or Point-to-multipoint network. To configure basic parameters of the device, click BASIC CONFIGURATION tab. The following screen appears:
Figure 4-1 Basic Configuration (BSU) Tsunami 800 & 8000 Series - Software Management Guide 40 Basic Configuration Figure 4-2 Basic Configuration (SU) Tsunami 800 & 8000 Series - Software Management Guide 41 Basic Configuration Figure 4-3 Basic Configuration (End Point A) Tsunami 800 & 8000 Series - Software Management Guide 42 Basic Configuration Below is the table which explains basic parameters and the method to configure the configurable parameter(s):
Figure 4-4 Basic Configuration (End Point B)
: Recommended characters for the name field are A-Z a-z 0-9 - _ =: . @ $ & and space. Parameter Description System Name By default, the device name is System-Name. Change the default device name to the desired one, with name ranging from 0 to 64 characters.
: The system name configured for the device shall be unique across all devices in a given WORP network. Tsunami 800 & 8000 Series - Software Management Guide 43 Parameter Frequency Domain Description This parameter specifies the country of operation, permitted frequency bands and regulatory rules for a particular country or domain. When the frequency domain is selected, the Dynamic Frequency Selection (DFS) and Automatic Transmit Power Control
(ATPC) features are enabled automatically if the selected country and band has a regulatory domain that requires it. The Frequency domain selection pre-selects and displays only the allowed frequencies for the selected country or domain. Basic Configuration
:
Devices are pre-configured to scan and display only the outdoor frequencies permitted in the respective country. No other countries, channels, or frequencies can be configured. Do not exceed the maximum EIRP permitted in the particular country. Configure the ATPC/TPC parameters by choosing the correct cable type /
attenuator It is the responsibility of the professional installer to properly install and configure the device parameters in accordance with the respective country laws. For non-US device, the default frequency domain selected is World 5MHz. For more details on frequency domains, see Frequency Domains and Channels. Radio Mode Represents the radio mode of the device. Based on the SKU, the radio mode is set to either BSU, SU, End Point A or End Point B. In a BSU device, the radio mode can be changed from BSU to SU and vice versa. Also, in an End Point A device, the radio mode can be changed from End Point A to End Point B and vice versa.
: A change in radio mode will reset wireless and WORP parameters to defaults after reboot. Channel Bandwidth Represents the width of the frequency band that is used to transmit data on the wireless interface. By default, it is set to 20 MHz. 40 MHz can be selected for higher throughputs depending on the distance and signal quality. 5 and 10 MHz can be selected for greater flexibility in spectrum selection.
: The 40 MHz frequency band is not applicable to MP 800 & 8000 BSU and SU devices, when configured in Legacy Mode. For more details on supported Channel Bandwidth, see Frequency Domains and Channels. Tsunami 800 & 8000 Series - Software Management Guide 44 Basic Configuration Parameter Auto Channel Selection (ACS) Description Enables a device to select the best channel for data transmission on the wireless medium, with less interference. By default, ACS is disabled on a BSU/End Point A and enabled on an SU/End Point B device. When ACS is enabled on a BSU/End Point A, it scans all the channels and selects the best channel during the start up. If ACS is enabled on the SU/End Point B, it continuously scans all the channels till it connects to a BSU or End Point A respectively.
: Irrespective of the ACS status, the BSU/End Point A will automatically select a new channel upon radar detection. Preferred Channel Active Channel Applicable only when the Auto Channel Selection (ACS) is disabled. This parameter enables to select a specific channel (in the specified frequency domain) for the device to operate. Displays the current active channel of operation. When the Auto Channel Selection parameter is enabled or when the device moves to a different channel because of radar detection, this parameter enables you to view the current operating channel. Network Name Network name to identify a wireless network. The network name can be of minimum 1 or maximum 32 characters. The default network name is MY_NETWORK.
: For a BSU and SU to establish a wireless link, both should in the same network. The same applies to End Point A and End Point B as well. Primary BSU Name Applicable only to an SU. Represents the Primary BSU name. If the primary BSU name is configured then SU establishes link with it. If a name is not configured then SU establishes link with any BSU on the same network, which meets the registration criteria. End Point A Name Applicable only to an End Point B. If a name is configured for End Point A then End Point B establishes a wireless link with it. If a name is not configured then End Point B establishes link with any End Point A on the same network that meets the registration criteria. Tsunami 800 & 8000 Series - Software Management Guide 45 Parameter Legacy Mode Description By default, this parameter is disabled. When enabled, the MP 800 & 8000 BSU and SU devices can interoperate with the legacy products of the Tsunami MP.11 family. The MP 800 & 8000 clients that provide legacy support are, Basic Configuration MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 MP-8200-SUA MP-8250-SUR MP-820-SUA-50+
MP-820-SUA-100 MP-822-SUA-100 MP-825-SUR-50+
MP-825-SUR-100 MP-825-CPE-50 MP-825-CPE-100 MP-835-CPE-10 MP-835-CPE-25 MP-835-CPE-50 MP-835-CPE-100
: MP 800/8000 BSU device in legacy mode can connect to a MP 800/8000 SU device only when configured in legacy mode. IP Configuration, and Default Gateway IP Address See Network. After configuring the required parameters, click OK and then COMMIT.
: Reboot the device, if any of the parameters with an asterisk symbol(*) are configured. Tsunami 800 & 8000 Series - Software Management Guide 46 Advanced Configuration 5 The ADVANCED CONFIGURATION tab provides a means to configure the following advanced features of the device:
System Network Ethernet Wireless Security Quality of Service (QoS) RADIUS Based SU QoS Configuration RADIUS Based SU VLAN Configuration DHCP VLAN (Bridge Mode Only) Filtering (Bridge Only) IGMP Snooping
: Recommended characters for the name field are A-Z a-z 0-9 - _ = : . @ $ & and space. Tsunami 800 & 8000 Series - Software Management Guide 47 5.1 System The System tab enables to configure system specific information. To configure system specific parameters, navigate to ADVANCED CONFIGURATION > System. The System screen appears:
Advanced Configuration Figure 5-1 System Configuration Given below is the table which explains System parameters and the method to configure the configurable parameter(s):
Parameter Radio Mode Description Represents the radio mode of the device. Based on the SKU, the radio mode is set to either BSU, SU, End Point A or End Point B. In a BSU device, the radio mode can be changed from BSU to SU and vice versa. Also, in an End Point A device, the radio mode can be changed from End Point A to End Point B and vice versa. But note that a change in radio mode will reset wireless and WORP parameters of the device after reboot. Frequency Domain A valid frequency domain must be set before the device can be configured with any other parameters. Selecting a frequency domain makes the device compliant with the allowed frequency bands and channels for that regulatory domain. See Frequency Domains and Channels. Network Mode The device can be configured in two network modes: Bridge and Routing. By default, the network mode is Bridge mode. Tsunami 800 & 8000 Series - Software Management Guide 48 Parameter Maximum MTU
(Maximum Transmission Unit) Description Given below are the devices and their corresponding MTU configurable range:
Devices MTU Configurable Range Advanced Configuration MP-820-SUA-100; MP-820-SUA-50+
MP-822-SUA-100 MP-825-SUR-50+; MP-825-SUR-100 MP-825-CPE-50; MP-825-CPE-100 MP-835-CPE-10; MP-835-CPE-25;
MP-835-CPE-50; MP-835-CPE-100;
MP-820-BSU-100, MP-825-BS3-100 MP-822-BSU-100;QB-825-EPR/LNK-50+
QB-825-EPR/LNK-100;
QB-835-EPR/LNK-25;
QB-835-EPR/LNK-50 QB-826-EPR/LNK-100 MP-8100-SUA; MP-8150-SUR MP-8150-SUR-100; MP-8200-BSU-G MP-8200-SUA; MP-8250-BS9/BS1-G MP-8200-BSU; MP-8250-BS9; MP-8250-BS1 MP-8250-SUR; QB-8200-EPA-G/LNK-G QB-8250-EPR-G/LNK-G;
QB-8200-EPA/LNK; QB-8250-EPR/LNK;
1500 to 2048 bytes 1500 to 1514 bytes Maximum Frame Size = Configured MTU + Ethernet Header (14 bytes) + VLAN Header (4 bytes) + Frame Check Sequence (4 bytes) Maximum Payload = Configured MTU Feature Header Feature Feature Header
(in bytes) Maximum Payload (in Bytes)
#
MP-8200-BSU-G MP-8250-BS9/BS1-G MP-8200-BSU MP-8250-BS9/BS1 MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 MP-8200-SUA MP-8250-SUR QB-8200-EPA-G/LNK-G QB-8250-EPR-G/LNK-G QB-8200-EPA/LNK QB-8250-EPR/LNK
*
MP-820-SUA-50+
MP-820-SUA-100 MP-822-SUA-100 MP-825-SUR-50+
MP-825-SUR-100 MP-825-CPE-50 MP-825-CPE-100 MP-835-CPE-10 MP-835-CPE-25 MP-835-CPE-50 MP-835-CPE-100 MP-820-BSU-100 MP-822-BSU-100 MP-825-BS3-100 QB-825-EPR/LNK-50+
QB-825-EPR/LNK-100 QB-835-EPR/LNK-25 QB-835-EPR/LNK-50 QB-826-EPR/LNK-100 General or Single VLAN QinQ PPPoE IP Tunneling (IP in IP Encapsulation) IP Tunneling (GRE Encapsulation) 0 4 8 20 24 1514 1510 1506 1494 1490 2048 2044 2040 2028 2024 Tsunami 800 & 8000 Series - Software Management Guide 49 Advanced Configuration Parameter Description
# Assuming that MTU is configured as 1514
* Assuming that MTU is configured as 2048 For optimal performance, MTU should be configured same on both the ends. Controller Status This feature helps the user to manage the device through ProximVision Advanced controller which automatically updates the device with the latest firmware, if device is using old firmware. By default, controller status is set to Standalone Mode. When set to Controller Mode, the device automatically discovers the controller and establishes a secure communication through two-way authentication.
:
Not Applicable to MP-8200-BSU-G; MP-8250-BS9-G; MP-8250-BS1-G;
MP-8200-BSU; MP-8250-BS9; MP-8250-BS1; MP-8100-SUA; MP-8150-SUR;
MP-8150-SUR-100; MP-8200-SUA; MP-8250-SUR; QB-8200-EPA-G/LNK-G;
QB-8250-EPR-G/LNK-G; QB-8200-EPA/LNK and QB-8250-EPR/LNK devices. Controller feature should be enabled in ProximVision Advanced also. Appicable only when the device is in Bridge Network Mode. LED Status The configurable options: Disable, RSSI, and Sync. By default, it is set to RSSI. The Received Signal Strength Indicator (RSSI) LEDs indicates that the unit is powered on, and LEDs will glow based on the RSSI value indicating link status. By default, all 5 LEDs will blink at an interval of 1 sec. If the LED Status is disabled, all LEDs will be turned off. If it is set to Sync, the third LED behavior of the scaling mask will indicate the Sync status.
: LED Status is applicable only to 82x MP and QB devices. SU Wireless MAC Address This field is applicable only for a BSU. In order to monitor the SU link statistics, the user should first configure the wireless MAC address of the SU. If the configured SU is registered with the BSU, then the LEDs will glow based on the RSSI value else all the 5 LEDs will blink. To get the SU Wireless MAC Address, navigate to MONITOR > WORP Statistics >Interface 1 > SU Link Statistics. After configuring the required parameters, click OK, COMMIT and then REBOOT. 5.2 Network The Network tab allows to view and configure the network specific information of the device. To view the current operating network mode of the device, navigate to ADVANCED CONFIGURATION > Network. If the network mode of the device is configured in Bridge mode, then following screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 50 Advanced Configuration If the network mode of the device is configured in Routing mode, then the following screen appears:
Figure 5-2 Bridge Mode Figure 5-3 Routing Mode 5.2.1 IP Configuration The IP addresses can be configured in two modes. They are:
IPv4: IPv4 is the widely used version of Internet Protocol defining the IP address in 32-bit in size. IPv6: Ipv6 is the latest version of Internet Protocol with new addressing system for more IP addresses than IPv4. The IPv6 address is 128-bit in size.
: IPv6 address is supported only in bridge mode. 5.2.1.1 Bridge Mode 5.2.1.1.1 IP Configuration (IPv4 Only) To configure the IP parameters of the device when operating in Bridge mode, navigate to ADVANCED CONFIGURATION >
Network > IP Configuration. The following IP Configuration screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 51 Figure 5-4 IPv4 Configuration (Bridge Mode) Given below is the table which explains the method to configure IP parameters in Bridge mode:
Parameter IP Mode Represents the IP Mode of the device. The IP Mode can be set to either IPv4 Only or Dual
(IPv4 and IPv6). By default, IP Mode is set to IPv4 Only. Description Advanced Configuration
: A change in IP mode requires device reboot. Ethernet (Please note that the number of Ethernet interfaces depend on your device.) Address Type Specifies whether the Ethernet interface parameters are to be configured through Dynamic Host Configuration Protocol (DHCP) or to be assigned statically. By default, the address type is set to Static meaning which the user can manually configure the network parameters. Select Dynamic to configure the device as a DHCP client. If Dynamic is selected, the device obtains the IP parameters from a DHCP server automatically during the bootup. If a DHCP server is not available or to manually configure the devices IP settings, select Static. IP Address Represents the IP address of the Ethernet interface. When the address type is set to Static (default address type), the IP address can be manually configured. By default, the static IP address is set to 169.254.128.132. When the address type is set to Dynamic, this parameter is read-only and displays the device IP address obtained from the DHCP server. The device will fall back to 169.254.128.132, if it cannot obtain the IP address from the DHCP server. Subnet Mask Represents the subnet mask of the Ethernet interface. When the address type is set to Static (default address type), the subnet mask can be manually configured. By default, the subnet mask is set to 255.255.255.0. When the address type is set to Dynamic, this parameter is read-only and displays the device current subnet mask obtained from the DHCP server. The subnet mask will fall back to 255.255.255.0, if the device cannot obtain the subnet mask from the DHCP server. IP Address Represents the gateway IP address of the device. Default Gateway IP Address When the address type is set to Static (default address type), the gateway IP address can be manually configured. By default, the gateway IP address is set to 169.254.128.132. When the address type is set to Dynamic, this parameter is read-only and displays the devices current gateway IP address that is obtained from the DHCP server. The gateway IP address will fall back to 169.254.128.132, if it cannot obtain the gateway IP address from a DHCP server. After configuring the required parameters, click OK, COMMIT and then REBOOT. 5.2.1.1.2 IP Configuration (IPv4 and IPv6) To configure the IP parameters of the device when operating in Bridge mode, navigate to ADVANCED CONFIGURATION >
Network > IP Configuration. The following IP Configuration screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 52 Advanced Configuration Given below is the table which explains the method to configure IP parameters in Bridge mode:
Figure 5-5 IPv6 Configuration (Bridge Mode) Parameter IP Mode Represents the IP Mode of the device. The IP Mode can be set to either IPv4 Only or Dual
(IPv4 and IPv6). By default, the IP Mode is set to IPv4 Only. Description
: A change in IP mode requires device reboot. Ethernet (Please note that the number of Ethernet interfaces depend on your device.) Link Local IP Address Link Local IP Address is an Internet protocol that is intended for communication within the segment of a local network or point-to-point connection that a host is connected to. During initial bootup, each system is assigned with a Link Local IP Address whose prefix is fe80::../64. The Link Local IP Address is a read only parameter. Tsunami 800 & 8000 Series - Software Management Guide 53 Parameter Address Type Advanced Configuration Description Specifies whether the Ethernet interface parameters are to be configured through Dynamic Host Configuration Protocol (DHCP) or Stateless Auto Configuration or to be assigned statically. Select Auto (default address type) to configure the device automatically. If Auto is selected, device obtains the IPv6 address, using the prefix obtained from the router advertisement. Select Static to configure the device manually. If Static is selected, the user should manually configure the network parameters. Select Dynamic to configure the device as a DHCP client. If Dynamic is selected, device obtains the IPv6 parameters from a DHCP server automatically. If the DHCP server is not available, the device will be accessible through Link Local IP Address. IP Address with Prefix Represents the IP address of the Ethernet interface. For Example: The IP address is represented as 2000::220:a6ff:fe00:1/64, where /64 is called the IP prefix or network prefix. When the address type is set to Auto (default address type), this parameter is read-only and displays the device IP address obtained from the router advertisements. When the address type is set to Dynamic, this parameter is read-only and displays the device IPv6 address obtained from the DHCP server. If device fails to get dynamic IP from DHCP server, the device will be accessible through Link Local IP Address. When the address type is set to Static, the IPv6 address should be manually configured along with prefix. IP Address Represents the gateway IP address of the device. Default Gateway IP Address When the address type is set to Auto (default address type), this parameter is read-only and displays the device IP address obtained from the router advertisement. When the address type is set to Static, the gateway IP address should be manually configured (prefix is not required). When the address type is set to Dynamic, the device uses the IP address obtained from DHCP server. The IP address obtained from DHCP server can be viewed in Routing Table. If IP address is not obtained from the DHCP server, then the device uses the user configured IP address. 5.2.1.1.3 DNS DNS server is used to resolve/translate a domain name into an IP address. To configure Primary and Secondary DNS IP parameters of the device when operating in Bridge mode, navigate to ADVANCED CONFIGURATION > Network > IP Configuration. The following IP Configuration screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 54 Advanced Configuration Figure 5-6 DNS Configuration (Bridge Mode) Parameter Primary and Secondary IP Address Represents the IP address of the Primary and Secondary DNS Server. Description Primary and Secondary IP Address can be configured manually irrespective of the IP mode. The DNS address obtained from the DHCP server (Dynamic mode) or from the router advertisement (Auto Mode) is given preference over the manually configured IP Addresses. The device lists all the IP addresses from DNS server configured manually or obtained from DHCP server/ router advertisement and only top three DNS server IP addresses will be used. To view the IP addresses refer DNS Addresses.
: IPv4 addresses will be given preference over IPv6 addresses. 5.2.1.2 Routing Mode
:
A device (BSU/SU) will act as a DHCP Client only when configured in Bridge Mode. In Routing Mode, With PPPoE Client disabled, the device (BSU/SU) IP addresses are assigned only statically. With PPPoE Client enabled, the device (SU) IP addresses can be assigned both statically and dynamically. See Routing Mode with PPPoE Client Enabled To configure the IP parameters of the device when operating in Routing mode, navigate to ADVANCED CONFIGURATION >
Network > IP Configuration. The IP Configuration screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 55 Advanced Configuration Given below is the table which explains the method to configure IP parameters in Routing mode:
Figure 5-7 IP Configuration (Routing Mode) Parameter Description Ethernet (Please note that the number of Ethernet interfaces depend on your device.) IP Address Represents the IP address of the Ethernet interface. By default, the static IP address for Ethernet1 is set to 169.254.128.132 and for Ethernet2 it is set to 169.254.129.132. You can manually change the IP address. Subnet Mask Represents the subnet mask of the Ethernet interface. By default, the static subnet mask is set to 255.255.255.0. You can manually change the subnet mask. IP Address Represents the IP address of the wireless interface. Wireless By default, the static IP address is set to 169.254.130.132. You can manually change the IP address. Tsunami 800 & 8000 Series - Software Management Guide 56 Advanced Configuration Parameter Description Subnet Mask Represents the subnet mask of the wireless interface. By default, the static subnet mask is set to 255.255.255.0. You can manually change the subnet mask. IP Address Represents the gateway IP address of the device. Default Gateway IP Address By default, the Gateway IP address is set to 169.254.128.132. You can manually change the gateway IP address. DNS Proxy It is a read-only parameter, which is enabled by default. DNS Proxy When DNS Proxy is enabled along with the DHCP server, the device will serve its own address as the Primary DNS address to the DHCP client on the Ethernet.
:
If the DNS request from the client is destined to the devices interface address then the device acts as a DNS Proxy. DNS Proxy is configurable through CLI/SNMP. When DNS Proxy is disabled, you need to configure the DNS settings manually so that the end-to-end communication works properly. 5.2.1.2.1 DNS To configure the IP parameters of the device when operating in Routing mode, navigate to ADVANCED CONFIGURATION >
Network > IP Configuration. The IP Configuration screen appears:
Figure 5-8 DNS Configuration (Routing Mode) Tsunami 800 & 8000 Series - Software Management Guide 57 Advanced Configuration Parameter Description Primary IP Address Represents the IP Address of the Primary DNS Server. Secondary IP Address Represents the IP Address of the Secondary DNS Server.
: In routing mode, the Primary and Secondary IP Address cannot be configured as IPv6 addresses. After configuring the required parameters, click OK, COMMIT and then REBOOT.
:
To obtain dynamic IP address of the SU over WORP, Scenario 1: When BSU and SU are in Bridge Mode with DHCP Client enabled in SU, and if external DHCP server is running behind BSU, then SU will get the IP Address over WORP. Scenario 2: When BSU and SU are in Bridge mode with DHCP client enabled in SU, and if BSU has an embedded DHCP server running on the wireless interface, then SU will get the IP address from BSU. Scenario 3: When BSU is in Routing Mode and SU is in Bridge mode, and DHCP server is in a different network than SU, then configure DHCP relay in BSU to get the IP for SU over WORP. Scenario 4: When BSU is in Routing mode and SU in Bridge mode, and if BSU has an embedded DHCP server running on the wireless interface, then SU will get the IP address from BSU. 5.2.1.3 Routing Mode with PPPoE Client Enabled
: IP Configuration in Routing mode with PPPoE Client enabled is applicable only in SU mode. See PPPoE End Point (SU Only) To configure the IP parameters of the device when configured in Routing mode with PPPoE client enabled, navigate to ADVANCED CONFIGURATION > Network. The IP Configuration screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 58 Advanced Configuration Figure 5-9 IP Configuration (Routing Mode with PPPoE Client Enabled) Given below is the table which explains the method to configure IP parameters in Routing mode with PPPoE client enabled:
Parameter Description Ethernet (Please note that the number of Ethernet interfaces depend on your device.) IP Address Represents the IP address of the Ethernet interface. By default, the static IP address for Ethernet1 is set to 169.254.128.132 and 169.254.129.132 for Ethernet2. You can manually change the IP address. Subnet Mask Represents the subnet mask of the Ethernet interface. By default, the static subnet mask is set to 255.255.255.0. You can manually change the subnet mask. Tsunami 800 & 8000 Series - Software Management Guide 59 Advanced Configuration Parameter Description Wireless (PPPoE) Address Type This parameter specifies whether the wireless interface parameters are to be configured through PPPoE server or to be assigned statically. By default, the address type is set to PPPoE-ipcp meaning which the PPPoE client obtains the IP parameters from a network PPPoE server automatically during the bootup. To manually configure the PPPoE Clients IP settings, select Static. IP Address Represents the Primary IP address of the wireless interface. When the address type is set to PPPoE-ipcp, this parameter is read-only and displays the PPPoE clients IP address obtained from the PPPoE server. The client will fallback to 169.254.130.132, if it cannot obtain the IP address from the PPPoE server. When the address type is set to Static, the IP address by default is set to 169.254.130.132. You can manually change the IP address. Subnet Mask Represents the subnet mask of the wireless interface. When the address type is set to PPPoE-ipcp, this parameter is read-only and is set to Host Mask as it is a point-to-point interface. The client will fallback to 255.255.255.0, if it cannot obtain the IP address from the PPPoE server. When the address type is set to Static, the subnet mask by default is set to 255.255.255.0. You can manually change the subnet mask. PPPoE Secondary IP IP Address Represents the Secondary IP address of the wireless interface. The Secondary IP serves as an alternate source to access/manage the device irrespective of the PPPoE link is up or down, as long as the WORP link is up. By using Secondary IP address, only management access to the device is allowed. Configure Secondary IP address manually. When PPPoE is disabled, the Secondary IP address is not applicable. Subnet Mask Represents the subnet mask of the Secondary IP address. IP Address The subnet mask by default is set to 0.0.0.0. You can manually change the subnet mask. The subnet mask of the Secondary IP address should be different from other subnets. Default Gateway IP Address Represents the gateway IP address of the device. When the address type is set to PPPoE-ipcp, this parameter is read-only and displays the PPPoE clients gateway IP address (which is nothing but the IP address of the PPPoE server). If it cannot obtain the IP address from a PPPoE server, then there will be no gateway for the device. When the address type is set to Static, the gateway IP address by default is set to 169.254.128.132. You can manually change the gateway IP address. Tsunami 800 & 8000 Series - Software Management Guide 60 Parameter Description DNS Proxy DNS Proxy It is a read-only parameter, which is enabled by default. Advanced Configuration When DNS Proxy is enabled along with the DHCP server, the device will serve its own address as the Primary DNS address to the DHCP client on the Ethernet.
:
If the DNS request from the client is destined to the devices interface address then the device acts as a DNS Proxy. DNS Proxy is mostly applicable in scenarios where PPPoE Client is enabled on a device and obtains its IP addresses dynamically from the PPPoE Server; And at the same time, the device acts as a DHCP Server for a client. 5.2.1.3.1 DNS To configure the IP parameters of the device when operating in Routing mode, navigate to ADVANCED CONFIGURATION >
Network > IP Configuration. The IP Configuration screen appears:
Figure 5-10 DNS Configuration (Routing Mode) Parameter Primary and Secondary IP Address Represents the IP address of the Primary and Secondary DNS Server. Description Primary and Secondary IP address can be configured manually. The DNS address obtained from the PPPoE-ipcp is given preference over manually configured IP addresses. After configuring the required parameters, click OK, COMMIT and then REBOOT. 5.2.2 Static Route Table
: Applicable only in routing mode. The Static Route Table stores the route to various destinations in the network. When packets are to be routed, the routing table is referred for the destination address. Tsunami 800 & 8000 Series - Software Management Guide 61 To configure the static routing table, navigate to ADVANCED CONFIGURATION > Network > Static Route Table. The Static Route Table screen appears. Advanced Configuration Given below is the table which explains Static Route Table entries and the method to configure the configurable parameter(s):
Figure 5-11 Static Route Table Parameter Static Route Status If Static Route Status is enabled, the packets are sent as per route configured in the static routing table. If disabled, forwards the packet to the default gateway. Description Destination Address Represents the destination IP address to which the data has to be routed. Subnet Mask Route Next Hop Admin Metric Entry Status Represents the subnet mask of the destination IP address to which the data has to be routed. Represents the IP address of the next hop to reach the destination IP address. Next hop IP should belong to at least one of the subnets connected to the device. It is a metric that specifies the distance to the destination IP address, usually counted in hops. The lower the metric, the better. The metrics can range from 0 to 16. If enabled, considers the packets for routing. If disabled, forwards the packet to the default gateway. 5.2.2.1 Adding Static Route Entries Click Add in the Static Route Table screen.The following Static Route Table Add Row screen appears:
Figure 5-12 Static Route Table Add Row Tsunami 800 & 8000 Series - Software Management Guide 62 Advanced Configuration Add the route entries and click Add and then COMMIT.
:
You can add a maximum of 256 routes to the static route table. The IP address of the Next Hop must be on the subnet of one of the devices network interfaces. 5.2.3 Network Address Translation (NAT)
: NAT is applicable only to an SU and an End Point B, in routing mode. The Network Address Translation (NAT) feature allows hosts on the Ethernet side of the SU or End Point B device to transparently access the public network through the BSU/End Point A device. All the hosts in the private network can have simultaneous access to the public network. The SU/End Point B device supports Network Address Port Translation (NAPT) feature, where all the private IP addresses are mapped to a single public IP address. The SU/End Point B device supports both Dynamic Mapping (allowing private hosts to access hosts in the public network) and Static Mapping (allowing public hosts to access hosts in the private network) are supported. 1. Static NAT: Static mapping is used to provide inbound access. The SU/End Point B maps the public IP address and its transport identifiers to the private IP address (local host address) in the local network. This is used to provide inbound access to a local server for hosts in the public network. Static port mapping allows only one server of a particular type. A maximum of 100 entries are supported in the static port bind table. 2. Dynamic NAT: In dynamic mapping, the SU/End Point B maps the private IP addresses and its transport identifiers to transport identifiers of a single Public IP address as they originate sessions to the public network. This is used only for outbound access.
:
When NAT is enabled, the network on the wireless side of the device is considered public and the network on the Ethernet side is considered private. When NAT functionality is enabled, the DHCP Relay and RIP features are not supported. The DHCP Relay Agent and RIP must be disabled before enabling NAT. To configure NAT parameters, navigate to ADVANCED CONFIGURATION > Network > NAT. The following NAT screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 63 Advanced Configuration Figure 5-13 NAT Given below is the table which explains NAT parameters and the method to configure the configurable parameter(s):
Parameter Description Status This parameter is used to either enable or disable NAT on an SU or an End Point A. Dynamic Start Port and Dynamic End Port Represents the start and end port sessions originated from private to public host. By default, the Dynamic Start Port is configured to 1 and Dynamic End Port is configured to 65535. Configure the start and end port as desired.
: Care should be taken to avoid overlap of Dynamic Port range and Static Port range. Port Forwarding Status This parameter is used to either enable or disable the Static NAT feature within different networks. It allows public hosts to access hosts in a private network. By default, it is disabled. After configuring the required parameters, click OK and then COMMIT.
:
To enable Dynamic NAT, set the NAT Status to Enable. To enable Static NAT, set the NAT Status to Enable and the Port Forwarding Status to Enable. NAT uses the IP address of the wireless interface as the Public IP address. To add entries in the NAT Port Bind Table, navigate to ADVANCED CONFIGURATION > Network > NAT > Static Port Bind. The NAT Port Bind Table screen appears. Click Add in the NAT Port Bind Table screen. The following NAT Port Bind Table Add Row appears:
Tsunami 800 & 8000 Series - Software Management Guide 64 Advanced Configuration Figure 5-14 NAT Port Bind Table Add Row Given below is the table which explains the NAT Port Bind Table entries and the method to configure the configurable parameter(s):
Parameter Description Local Address Enter the local IP Address of the host on the Ethernet (private) side of the SU/End Point B. Port Type Select the Port Type as: TCP, UDP, or Both. Start and End Port Number Represents the start and end port for transferring the data from public to private host.
: Care should be taken to avoid overlap of Dynamic Port range and Static Port range. Entry Status If enabled, the data is transferred from the public network to the private host, on the specified ports. After configuring the required parameters, click ADD and then COMMIT. 5.2.3.1 Supported Session Protocols Certain applications require an Application Level Gateway (ALG) to provide the required transparency for an application running on a host in a private network to connect to its counterpart running on a host in the public network. An ALG may interact with NAT to set up state information, use NAT state information, modify application-specific payload, and perform the tasks necessary to get the application running across address realms. No more than one server of a particular type is supported within the private network behind the SU/End Point B. The following table lists the supported protocols with their corresponding default ALG's:
S.No. Protocol Support Applications 1 2 3 H.323 HTTP TFTP H.323 ALG Multimedia Conferencing Port Mapping for inbound connection Web Browser Port Mapping for inbound connection Trivial file transfer Tsunami 800 & 8000 Series - Software Management Guide 65 Advanced Configuration S.No. Protocol Support Applications 4 5 6 7 8 9 10 Telnet IRC Port Mapping for inbound connection Remote login Port Mapping for inbound connection Chat and file transfer AMANDA Port Mapping for inbound connection Backup and archiving FTP PPTP SNMP DNS FTP ALG PPTP ALG SNMP ALG File Transfer VPN related Network Management Port Mapping for inbound connection Domain Name Service 5.2.4 RIP
: RIP is configurable only when the devices are in Routing Mode and Network Address Translation (NAT) is disabled. Routing Information Protocol (RIP) is a dynamic routing protocol, which can be used to automatically propagate routing table information between routers. The device can be configured in RIPv1, RIPv2, or both while operating in Routing mode. When a router receives a routing update including changes to an entry, it updates its routing table to reflect the new route. RIP maintains only the best route to a destination. Therefore, whenever new information provides a better route, the old route information is replaced. To configure RIP parameters, navigate to ADVANCED CONFIGURATION > Network > RIP. The following RIP screen appears:
By default, RIP is not enabled on the device. To enabled, select Enable and click OK. The RIP screen is updated with the following tabulated parameters:
Figure 5-15 RIP Tsunami 800 & 8000 Series - Software Management Guide 66 Advanced Configuration Parameter Name Status Description Displays the interface type as either Ethernet 1, Ethernet 2, or Wireless. Enables you to either enable or disable RIP for a particular network interface. Authorization Type Enables you to select the appropriate Authorization Type. This parameter is not applicable if RIP v1 is selected as the Version number. Authorization Key Version Number Direction Enter the authorization key. This parameter is not applicable if RIP v1 is selected as the Version number. It is not applicable when the Authorization Type is set to None. Select RIP Version number from the Version Number list. Available options are V1, V2 and both. The default is V2. You can enable RIP for both receiving and transmitting the data. To enable RIP only for Receiving, select Rx Only. To enable RIP for both receiving and transmitting, select Rx and Tx. After configuring the required parameters, click OK and then COMMIT.
:
Authorization Type and Authorization Key are valid only for RIPV2 and both versions. The maximum metric of a RIP network is 15 hops, that is, a maximum of 15 routers can be traversed between a source and destination network before a network is considered unreachable. By default, a RIP router will broadcast or multicast its complete routing table for every 30 seconds, regardless of whether anything has changed. RIP supports the split horizon, poison reverse and triggered update mechanisms to prevent incorrect routing updates being propagated. When RIP is enabled with Simple Authentication, MP 82x/8000 SUs/BSUs will not exchange RIP packets with 5012 or 5054 SUs/BSUs. 5.2.5 PPPoE End Point (SU Only) Proxims SU devices support Point-to-Point Protocol over Ethernet (PPPoE) which is a network protocol for transmitting PPP frames over Ethernet. This feature is commonly used by Internet Service Providers (ISPs) to establish a Digital Subscriber Line (DSL) Internet service connection with clients. The Proxims SU devices support PPPoE only when they are configured in Routing Mode with NAT enabled. Also, the BSU should always operate in Bridge Mode. Tsunami 800 & 8000 Series - Software Management Guide 67 Advanced Configuration Figure 5-16 PPPoE Architecture Given below are the stages for a PPPoE client to establish link with the PPPoE server and then transfer PPP frames over Ethernet:
Discovery and Session Stage: In this stage, to initiate a PPPoE session, the PPPoE client discovers a PPPoE server
(called Access Concentrator). Once discovered, a session ID is assigned and a session is established. Point-to-point Protocol (PPP) Stages: The PPP stage comprises the following sub-stages:
1. Physical Link: For sending and receiving PPP frames, the PPP driver calls the services of PPP Channels (used in connection with serial links). A PPP channel encapsulates a mechanism for transporting PPP frames from one machine to another and then the frames are forwarded on the physical Ethernet link. 2. Link Establishment: In this stage, Link Configuration Protocol (LCP) performs the basic setup of the link. As part of this setup, the configuration process is undertaken whereby the PPPoE client and the server negotiate and agree on the parameters on how data should be passed between them. Only when both the client and server come to an agreement, the link is considered to be open and will proceed to the Authentication stage. 3. Authentication: In this stage, LCP invokes an authentication protocol (PAP/CHAP/MS CHAP v2/EAP-MD5) when PPP is configured to use authentication. 4. Encryption: In this stage, both PPPoE client and server negotiate the encryption protocol configuration. Our device support MPPE as encryption protocol. MPPE is negotiated within option 18 in the PPP Compression Control Protocol (CCP). 5. Network Layer Protocol: After successful authentication, the link proceeds to the Network-Layer Protocol stage. In this stage, the specific configuration of the appropriate network layer protocol is performed by invoking the appropriate Network Control Protocol (NCP) such as IPCP. We support only IPCP Protocol as a part of NCP. Given below are the features supported by PPPoE client:
Preferred Server Configuration by using Access Concentrator Name/Service Name PAP/CHAP/MSCHAP v2/EAP-MD5 Authentication Protocols IP Configuration: Static IP/ PPPoE-IPCP Echo Interval and Echo Failure to detect server unavailability MPPE with stateful and stateless mode aligned with 40/56/128 bit encryption To configure PPPoE feature, 1. Navigate to ADVANCED CONFIGURATION > Network > PPPoE > PPPoE Client. The following PPPoE Client screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 68 Advanced Configuration Figure 5-17 PPPoE Client Status 2. By default, the PPPoE feature is disabled on the client. To enable, select Enable from Status drop-down box. 3. Next, click OK. Please note that a change in the PPPoE client status requires you to reboot the device. 4. On enabling the PPPoE client feature, the following screen appears:
Figure 5-18 PPPoE Client Configuration Tsunami 800 & 8000 Series - Software Management Guide 69 5. Given below is the table which explains PPPoE client parameters and the method to configure the configurable parameter(s):
Parameter Description Authentication Protocol PPPoE supports the following types of user authentication protocols that provide varying levels of security:
Advanced Configuration None: Represents that no authentication is required for transferring PPP frames over Ethernet between PPPoE client and server. Password Authentication Protocol (PAP): PAP is an access control protocol used to authenticate clients password on the server. The server requests a password from the client and sends the retrieved password to an authentication server for verification. As an authentication protocol, PAP is considered the least secure because the password is not encrypted in transmission. Challenge Handshake Authentication Protocol (CHAP): CHAP is similar to PAP with several unique characteristics. Instead of requesting a password, the server sends a challenge message to the client. The challenge message is a random value. The client encrypts the challenge message with user's password and sends the combination back to the server. The server forwards the challenge/password combination to the authentication server. The authentication server encrypts the challenge with the user's password stored in the authentication database. If the user's response is a match, the password is considered authentic. CHAP uses the model of a shared secret (the user password) to authenticate the user. The use of CHAP is considered a moderately secure method of authentication. Microsoft Challenge-Handshake Authentication Protocol version 2
(MSCHAP v2): MSCHAP V2 is a mutual authentication method that supports password-based user or computer authentication. During the MSCHAP v2 authentication process, both the client and the server prove that they have knowledge of the user's password for authentication to succeed. Mutual authentication is provided by including an authenticator packet returned to the client after a successful server authentication.This method is proprietary to the Microsoft mostly used in windows servers and client. EAP-MD5: EAP-MD5 enables a server to authenticate a connection request by verifying an MD5 hash of a user's password. The server sends the client a random challenge value, and the client proves its identity by hashing the challenge and its password with MD5. By default, the authentication protocol is set to CHAP. You can configure the authentication protocol to the desired one and click OK. LCP Echo Interval To check the link connection, periodically, the PPPoE client sends an LCP echo-request frame to the PPPoE server. If the PPPoE server respond to the echo-request by sending an echo-reply, then the connection is alive. To configure LCP Echo Interval, enter a time ranging from 5 to 300 seconds. By default, the echo interval is set to 30 seconds. Tsunami 800 & 8000 Series - Software Management Guide 70 Advanced Configuration Parameter LCP Echo Failure Description This parameter indicates the maximum number of consecutive failures to receive the LCP echo-reply to consider the connection to be down. To configure LCP Echo Failure value, enter a a value ranging from 1 to 25. By default, the echo failure is set to 5. On a noisy wireless link, it is recommended to set this value to higher. Preferred Service Name Specifies the service which the PPPoE server (Access Concentrators) provides to the PPPoE client. Leave this parameter blank, if PPPoE client accepts any service offered by the PPPoE server. To specify the desired service name, enter the service name ranging from 1 to 32 characters. Access Concentrator Name Specifies Access Concentrator (PPPoE server) name. Leave this parameter blank, when PPPoE client can connect to any PPPoE server on the network. To connect to a desired PPPoE server, type the server name ranging from 1 to 32 characters. User Name and Password Before establishing a link, the PPPoE server first authenticates the PPPoE client based on the User Name and Password as shared by the service provider. Type the user name and password in the User Name and Password box respectively. You can type user name ranging from 4 to 32 characters and password ranging from 6 to 32 characters.
: User Name and Password parameters are not applicable when the Authentication Protocol is configured as None. Tsunami 800 & 8000 Series - Software Management Guide 71 Parameter MPPE Status Advanced Configuration Description
: MPPE Status parameter is applicable only when the Authentication Protocol is configured as MSCHAP v2. Microsoft Point-to-Point Encryption (MPPE) is a protocol for transferring encrypted data over point-to-point links. The PPPoE client negotiates on the encryption parameters based on the MPPE Status configured. The MPPE Status can be configured as following:
Mandatory: When the MPPE status is configured as Mandatory, the PPPoE client negotiates the configured MPPE parameters with the PPPoE server. If the server does not agree to the parameters then the link will not be established. Optional: When the MPPE status is configured as Optional, the link is established with or without encryption depending on the PPPoE server configuration. If the PPPoE server supports MPPE encryption then the PPPoE client agrees with the PPPoE servers MPPE parameters and link gets established with encryption. If the PPPoE server does not support MPPE encryption then link gets established without encryption. Disable: When the MPPE status is configured as Disable, then the PPPoE client does not agree to the MPPE parameters suggested by the PPPoE server. Configure the desired status and click OK. Stateless Encryption Mode
: This parameter is applicable only when Authentication Protocol is configured as MSCHAP v2 and MPPE Status is configured as Mandatory. When stateless encryption is negotiated, the session key changes for every packet transferred. In stateless mode, the sender must change its key before encrypting and transmitting each packet and the receiver must change its key after receiving, but before decrypting, each packet. When stateful encryption is negotiated, the PPPoE server and the client monitor the synchronization of MPP encryption engine on both the sides. When one of the peer detects that they are out of sync then the peer should transmit a packet with the coherency count set to 0xFF(a flag packet); the sender must change its key before encrypting and transmitting any packet and the receiver must change its key after receiving a flag packet, but before decrypting. To enable stateless encryption, select Enable. To enable stateful encryption, select Disable.
: Enabling Stateless Encryption impacts throughput. It is useful to enable Stateless encryption when packet drops are more in the wireless link. Tsunami 800 & 8000 Series - Software Management Guide 72 Parameter MPPE Key Length Advanced Configuration Description
: This parameter is applicable only when Authentication Protocol is configured as MSCHAP v2 and MPPE Status is configured as Mandatory. MPPE supports 40-bit, 56-bit and 128-bit encryption key length. To configure the desired key length, select a key length from the MPPE Key Length drop-down box. Link Status Indicates the status of the PPPoE link between the PPPoE client and server. The link can be in any of the following three stages:
Disconnected: No connection is established between PPPoE client and server. Connecting: A connection attempt is in progress between PPPoE client and server. Connected: Connection is established between PPPoE client and server. The Link Status can be viewed in Home Page. 6. After configuring the required parameters, click OK and then COMMIT. Reboot the device, if you have changed the PPPoE Status configuration. 5.2.6 IP over IP Tunneling
: Applicable only in Routing Mode. Proxims point-to-multipoint and point-to-point devices support IP Tunneling, which serves as a communication channel between two disjoint IP networks that do not have a native routing path to communicate with each other. To enable communication between two disjoint networks using IP Tunneling, the following steps are involved:
1. The tunnel entry point receives the IP packet (Sender Source IP + Recipient IP) sent by the original sender. IP Packet Sender Source IP Recipient IP 2. The tunnel entry point encapsulates the IP packet (Sender Source IP + Recipient IP) with the IP addresses of the tunnel endpoints. The tunneled packet (Sender Source IP + Recipient IP + Tunnel Entry Point IP + Tunnel Exit Point IP) is then forwarded to the tunnel exit point. Tunneled IP Packet
(Inner IP Header)
(Outer IP Header) Sender Source IP Recipient IP Tunnel Entry Point IP Tunnel Exit Point IP 3. On receiving the tunneled packet, the tunnel exit point removes the tunnel IP addresses and forwards the packet to the recipient. The inner IP header Source Address and Destination Address identify the original sender and recipient of the packet, respectively. The outer IP header Source Address and Destination Address identify the endpoints of the tunnel. Tsunami 800 & 8000 Series - Software Management Guide 73 The following figure shows an IP tunnel configuration using two end points. Advanced Configuration Figure 5-19 An Example: Tunnel Configuration Lets say that the Computer with an IP address: 10.0.0.1 wants to communicate with the Computer with an IPA address:
192.168.9.101. Since there is no native routing path between these two computers, the communication can happen via the tunnel. The SU1device with wireless IP address: 20.0.0.132 and SU2 device with wireless IP address: 30.0.0.132 are the end points of the tunnel, respectively. With IP tunneling, the tunnel entry point (SU1) encapsulates the tunnel end points IP addresses (20.0.0.132 + 30.0.0.132) with the sender IP addresses (10.0.0.1 + 192.168.9.101) before sending the data through the tunnel. When the tunnel exit point (SU2) receives traffic, it removes the outer IP header before forwarding the packet to the recipient. IP Packet Sender Source IP (10.0.0.1) Recipient IP (192.168.9.101) Tunneled IP Packet
(Inner IP Header)
(Outer IP Header) Sender Source IP
(10.0.0.1) Recipient IP
(192.168.9.101) Tunnel Entry Point IP
(20.0.0.132) Tunnel Exit Point IP
(30.0.0.132)
: IP tunnel establishment does not involve any protocol message exchange. To setup an IP tunnel, the device has to be configured properly on both the ends. By following the steps below, the tunnel is automatically established. 1. Create a tunnel (Refer to Create a Tunnel) To create a tunnel as given in Figure 5-19, do the following:
SU1 Configuration Virtual IP Address = 50.0.0.1 Local IP Address = 20.0.0.132 Remote IP Address = 30.0.0.132 Tsunami 800 & 8000 Series - Software Management Guide 74 Advanced Configuration SU2 Configuration Virtual IP address = 50.0.0.2 Local IP Address = 30.0.0.132 Remote IP Address = 20.0.0.132 2. Add a Static Route for Remote IP Address of the tunnel (Refer to Static Route Table) On SU1, add a static route for 30.0.0.xxx as next hop 20.0.0.1 On SU2, add a static route for 20.0.0.xxx as next hop 30.0.0.1 3. Add a route for the pass-through traffic through the tunnel (Next Hop IP Address should be that of the tunnel interface). On SU1, add a static route for 192.168.9.xxx as next hop 50.0.0.1 On SU2, add a static route for 10.0.0.xxx as next hop 50.0.0.2 5.2.6.1 Create a Tunnel To create a Tunnel interface, 1. Navigate to ADVANCED CONFIGURATION > Network > IP Tunneling. The following IP Tunneling screen appears:
Figure 5-20 IP Tunneling Status 2. By default, the IP Tunneling feature is disabled on the device. To enable, select Enable from the Tunneling Status drop-down box. 3. Next, click OK. 4. On enabling the IP Tunneling feature, the following screen appears:
5. Click Add, to create a new tunnel interface. The following Tunneling Table Add Row screen appears:
Figure 5-21 IP Tunneling Interfaces Tsunami 800 & 8000 Series - Software Management Guide 75 Advanced Configuration Figure 5-22 Adding a new Tunnel Interface 6. Given below is the table which explains the parameters for creating a new tunnel:
Parameter Description Name Represents the name of the tunnel interface. Type a name for the tunnel interface. Encapsulation Method The device supports two types of network tunnels:
ipip: A tunneling protocol that allow only IP traffic over the tunnel. gre (Generic Routing Encapsulation): A tunneling protocol that allows encapsulation of a wide variety of packet types in Internet Protocol (IP) packets, thereby creating a virtual point-to-point link. Select the tunnel type as either ipip or gre. Virtual IP Address Local IP Address Represents the virtual IP address of the tunnel interface. Enter the virtual IP address of the tunnel interface. Represents the IP address of the tunnel entry point. Select the IP address of the tunnel entry point from the available list of addresses. Remote IP Address Represents the IP address of the tunnel exit point. Type the IP address of the tunnel exit point. Please note that the Remote IP address should be routable. TTL TTL stands for Time to Live. This parameter enables to configure a fixed TTL value on the tunneled packets. The TTL value can be configured in the range 0 to 255. By default, the TTL value is set to 0 meaning that tunneled packets inherit the TTL value from the IP packet originated by the sender. Entry Status By using this parameter, a tunnel interface can be enabled or disabled. By default, it is enabled. To disable, select Disable. 7. Next, click Add.
:
You can create a maximum of 16 tunnels. Tsunami 800 & 8000 Series - Software Management Guide 76 The Maximum Transmission Unit (MTU) of the tunnel interface depends on the underlying interface. It is advised that both PPPoE and the IP Tunneling feature do not function simultaneously on the device. IP configuration of Ethernet and Wireless interface should NOT be in the same subnet of virtual IP addresses of Advanced Configuration tunnels. 5.2.6.2 View Existing Tunnels The IP Tunneling screen displays all the tunnels created on the device. The entries against each tunnel cannot be edited. However, the status of each tunnel entry can be modified. You can either enable, disable or delete a tunnel by selecting the desired one from Entry Status box in the IP Tunneling screen. Figure 5-23 IP Tunneling Interfaces 5.3 Ethernet The Ethernet tab enables you to view and configure the Ethernet interface properties of the device. 5.3.1 Basic Ethernet Configuration To view and perform basic Ethernet configuration, navigate to ADVANCED CONFIGURATION > Ethernet. The Ethernet Interface Properties screen appears:
Figure 5-24 Basic Ethernet Configuration Tsunami 800 & 8000 Series - Software Management Guide 77 Given below is the table which explains Basic Ethernet parameters and the method to configure the configurable parameter(s):
Advanced Configuration Parameter Description MAC Address Displays the MAC address of the Ethernet interface. Operational Speed Displays the current operational speed of the Ethernet interface. Given below is the maximum operational speed of the Ethernet interface product wise:
Product (s) Maximum Speed 1 Gbps 100 Mbps MP-8200-BSU-G MP-8250-BS9-G MP-8250-BS1-G MP-8200-BSU MP-8250-BS9 MP-8250-BS1 MP-820-BSU-100 MP-822-BSU-100 MP-825-BS3-100 MP-8200-SUA MP-8250-SUR MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 MP-820-SUA-50+
MP-820-SUA-100 MP-822-SUA-100 MP-825-SUR-50+
MP-825-SUR-100 QB-8200-EPA-G/LNK-G QB-8250-EPR-G/LNK-G QB-8200-EPA/LNK QB-8250-EPR/LNK QB-825-EPR/LNK-50+
QB-825-EPR/LNK-100 MP-825-CPE-50 MP-825-CPE-100 MP-835-CPE-10 MP-835-CPE-25 MP-835-CPE-50 MP-835-CPE-100 QB-835-EPR/LNK-25 QB-835-EPR/LNK-50 QB-826-EPR/LNK-100 Tsunami 800 & 8000 Series - Software Management Guide 78 Advanced Configuration Parameter Operational Tx Mode Description Displays the current operational transmission mode of the Ethernet interface. It supports two types of transmission modes:
Half Duplex: Allows one-way data transmission at a time. Full Duplex: Allows two-way transmission simultaneously. Speed And TxMode Enables the user to select the speed and transmission mode of the Ethernet interface. By default, it is set to Auto. When set to Auto (recommended to set), both the transmitter and the receiver negotiate and derive at the best transmission mode.
:
Please ensure the same transmission modes are configured on the transmitter and the receiver device. In case of 82x devices, the Auto option will support Gigabit if the other end is capable of supporting it. Admin Status This parameter is applicable only when the device support more than one Ethernet interface. By default, both the Ethernet interfaces of the device are enabled. The first Ethernet interface is always enabled; whereas the second Ethernet interface can be either enabled or disabled as desired. After configuring the required parameters, click OK and then COMMIT. Reboot the device, if you have changed the Admin Status configuration. 5.3.2 Advanced Configuration The Advanced Configuration feature enables you to achieve high availability and link aggregation in a wireless medium by using two or more parallel links and additional Link Aggregation Control Protocol (LACP) capable switches.
: Applicable only to QB-8200-EPA-G/LNK-G, QB-8250-EPR-G/LNK-G, QB-8200-EPA/LNK and QB-8250-EPR/LNK To view and perform advanced Ethernet configuration, click Advanced in the Ethernet Interface Properties screen. The following screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 79 Advanced Configuration Figure 5-25 Advanced Ethernet Configuration Given below is the table which explains Advanced Ethernet parameters and the method to configure the configurable parameter(s):
Parameter Auto Shutdown Description This parameter facilitates LACP capable Ethernet switches to use two or more QuickBridge links to achieve higher throughput and redundancy. By default, it is Disabled. If Auto Shutdown is enabled on the Ethernet Interface, then the Ethernet port will be automatically disabled, when the wireless link is DOWN. It will be automatically enabled once the wireless link is UP again.
: This feature works only if STP/LACP Frames is set to passthru (See Filtering
(Bridge Only)) Tsunami QuickBridge devices that are part of LACP link cannot be managed through the switches, so it is recommended to use the second Ethernet port for management.
: When using second Ethernet port for management, ensure to disable Auto Shutdown for Ethernet2. For details on how to manage the QuickBridge devices through the second Ethernet port, refer LACP - Device Management. After configuring the required parameters, click OK and then COMMIT. 5.4 Wireless The Wireless tab allows you to configure wireless properties (such as Network Name, Channel Bandwidth, DDRS and ATPC) on the device, which enables wireless communication between the Base Station and Subscriber, and Quick Bridges. The features configurable under Wireless tab are as follows:
Link Profiles Tsunami 800 & 8000 Series - Software Management Guide 80 Advanced Configuration Wireless Outdoor Router Protocol (WORP) Wireless Interface Properties BSU / SU Profiles 5.4.1 Link Profiles The Link Profiles feature enables you to create wireless profiles on a per link basis. These link profiles help to determine the wireless transmission properties (Tx data rate, TPC, Tx antenna ports) of a WORP link. On SU, it determines the transmission properties of all the transmitted packets. On BSU, it determines the transmission properties of all the unicast packets. On BSU, it determines the transmission properties of all the broadcast/multicast and announcement packets by considering all the active link properties and active profiles. While sending broadcast messages, BSU considers the most viable wireless parameters (Tx Rate, Data Streams and TPC) so that all the connected SUs receive the message. In point-to-multipoint (BSU and SU) devices, you can create a maximum of eight link profiles including the default pre-configured profile. Profiles that are created on the BSU are mapped to the SUs, and vice versa. If BSU/SU is not mapped to any configured profile, it will be mapped to the default profile. The point-to-point (Quick Bridges) devices support only one link profile.
: When working with multiple link profiles with varying data rates, the overall wireless network performance gets affected. To optimize the overall network performance, use QoS.
: On upgrade from prior software versions, the WORP link configurations are copied to the Default link profile. To create a link profile, navigate to ADVANCED CONFIGURATION > Wireless > Link Profiles. The Link Profiles screen appears:
In the Link Profiles screen, you can add, edit and delete the link profiles. Figure 5-26 Link Profiles The default profile can be modified to suit the network requirements. However, it is possible that one profile may not be able to satisfy the requirements of all the WORP links (due to different operating conditions, link distance etc). In such a case, additional link profiles can be defined and associated with respective links appropriately (refer BSU / SU Profiles on how to associate profile to a link). Tsunami 800 & 8000 Series - Software Management Guide 81 It is intended that all the WORP links that are expected to exhibit similar behavior be grouped under one link profile. Advanced Configuration
:
You can edit but not delete the Default profile. The link profiles in use cannot be deleted; This includes the Roaming Link Profile irrespective of the roaming status. A single profile can be mapped to multiple SUs/BSUs. Link profiles are local to the device and should be configured independently on all devices. 5.4.1.1 Add a Link Profile To add a link profile, click Add in the Link Profiles screen. The Link Profile Add Entry screen appears:
Type a name for the link profile in the Profile Name field. Next, click ADD and then COMMIT. Figure 5-27 Add a Link Profile
:
By default, the link profiles are created with default values. After adding a link profile it must be associated with a peer (refer BSU / SU Profiles for it to be effective. 5.4.1.2 Edit a Link Profile The link profiles are created with pre-configured wireless parameters. In order to edit these pre-configured values for a desired profile, click Edit symbol Profile Edit Entry 1 screen appears, which is classified under two categories: Basic and Advanced. in the Link Profiles screen. The Link Tsunami 800 & 8000 Series - Software Management Guide 82 Advanced Configuration Figure 5-28 Edit a Link Profile (Basic) 5.4.1.2.1 Basic Under Basic screen, you can configure and view the following parameters. Parameter Profile Name DDRS Status Description Represents the link profile name whose wireless parameters are edited. Enter a new name, if you wish to edit the existing profile name. Dynamic Data Rate Selection (DDRS) feature adjusts the transmission data rate to an optimal value to provide the best possible throughput according to the current communication conditions and link quality. The factors for adjusting the transmission data rate are, 1. Remote average Signal-to-noise (SNR) ratio 2. Number of retransmissions The DDRS Status parameter allows to either enable or disable DDRS per link profile. By default, DDRS is enabled. Tsunami 800 & 8000 Series - Software Management Guide 83 Parameter Description Data Streams Select the data stream as either as Auto, Single or Dual. Advanced Configuration Dual Stream: Select Dual, for higher throughput. Single Stream: Select Single, for reliability and longer range. Auto Stream: When configured to Auto, DDRS decides the stream modes based on the environmental conditions When DDRS is enabled, based on the selected data stream, DDRS dynamically chooses the data rate.
:
Data Stream mode is not applicable in legacy mode. When DDRS is disabled, Auto stream is not applicable. DDRS Minimum Data Rate and DDRS Maximum Data Rate Tx Rate ATPC Status Represents the minimum and maximum data rate for DDRS to dynamically select the transmission data rate. These will vary depending on the configured data stream. This parameter enables you to manually set the transmission data rate, wh en DDRS is disabled. A change in data streams resets Tx rate to its default value. If Adaptive Transmit Power Control (ATPC) is enabled, then the device automatically adjusts the transmit power to avoid saturation of remote receiver, which could cause data errors leading to lower throughput and link outage. If disabled, user can manually adjust the transmit power. By default, ATPC is enabled on the device. Transmit Power Control (TPC) is calculated based on two factors:
Equivalent Isotropically Radiated Power (EIRP) Maximum Optimal SNR In case of a BSU, when ATPC is enabled, TPC is adjusted on a per link basis.
: In 82x /82xx US SKUs, ATPC cannot be disabled for DFS frequencies. Tsunami 800 & 8000 Series - Software Management Guide 84 Parameter TPC This parameter enables you to manually set the Transmit Power Control (TPC) value when ATPC is disabled. You can manually set TPC ranging from 0 to 25 dB. Description Advanced Configuration
: In case of 82x devices, you can manually set TPC ranging from 0 to 15 dB. With TPC, you can adjust the output power of the device to a lower level. This is performed to reduce interference with the neighbouring devices. It can be helpful when higher gain antenna is used without violating the maximum radiated output power for a country or regulatory domain. By default, it is set to 0 dB.
:
Adjust TPC such that the wireless link SNR does not cross the maximum optimal SNR value (For minimum and maximum SNR values, see An Example - Local SNR Information). TPC only lets you decrease the output power; it does not let you increase the output power beyond the maximum allowed defaults for the selected frequency and country. TPC can be configured in the steps of 0.5 dB Auto Tx Antenna Status Applicable only in single data stream mode. Antenna Status When Auto Tx Antenna Status is enabled for single stream, the device automatically selects the antenna port with highest received RSSI for data transmission. Tx Antenna Status Applicable only when Auto Tx Antenna Status is disabled. Allows the user to select the antenna port(s) for data transmission. Select the checkbox against each antenna(s) for data transmission and click OK.
:
On a BSU, selection of antenna ports is on a per link basis. The Tx Antenna port being used for each link can be seen on the Link Statistics page. Atleast two Tx antenna ports should be enabled when Data Stream is dual or auto. After configuring the required parameters, click OK and then COMMIT. 5.4.1.2.2 Advanced Under Advanced screen, you can configure and view the following parameters. Tsunami 800 & 8000 Series - Software Management Guide 85 Advanced Configuration Parameter DDRS Minimum Data Rate and DDRS Maximum Data Rate DDRS Lower SNR Correction Figure 5-29 Edit a Link Profile (Advanced) Description Represents the minimum and maximum data rate for DDRS to dynamically select the transmission data rate. These will vary depending on the configured data stream. Represents the margin value to be added to the minimum required SNR, for the purpose of removing the data rate from the valid data rate table. Doing so, avoids Hysteresis in the dynamic data rate. By default, it is configured to 0 dB. DDRS Upper SNR Correction Represents the margin value to be added to the maximum required SNR, for the purpose of adding the data rate to the valid data rate table. Doing so, avoids Hysteresis in the dynamic data rate. By default, it is set to 3 dB. Tsunami 800 & 8000 Series - Software Management Guide 86 Advanced Configuration Parameter Description DDRS Rate Incr RTX Threshold Represents a threshold for the percentage of retransmissions, below which the rate can be increased. By default, it is set to 10%.
: If the percentage of retransmissions is between Rate Increment RTX Threshold and Rate Decrement RTX Threshold then the current operation rate is maintained. DDRS Rate Decr RTX Threshold Represents a threshold for percentage of retransmissions, above which the rate can be decreased. By default, it is set to 15%. Please note that if the percentage of retransmissions is between Rate Increment RTX Threshold and Rate Decrement RTX Threshold then the current operation rate is maintained. DDRS Chain Balance Threshold In the case of MIMO, the difference in SNR between two chains must be less than or equal to this threshold for the chains to be considered as Balanced. By default, it is set to 15 dB.
:
This parameter is applicable only in Auto stream mode. When Auto stream mode is configured and if chains are not balanced, then Single Stream rates are considered. DDRS Rate Back Off Interval DDRS algorithm constantly attempts higher data rates, when the current rate is stable. If not successful, it goes back to older stable rate. Before the next attempt, it waits for a minimum duration. This duration starts with 10 seconds and increases exponentially up to Rate Back Off Interval and remains at this value. By default, it is set to 300 seconds. DDRS Rate Blacklist Interval Applicable when data stream mode is set to Auto. DDRS algorithm dynamically determines the performance of the single and dual stream data rates independently and blacklists unviable data rates to avoid unnecessary fluctuations, for a period of DDRS Rate Blacklist Interval. By default, it is set to 600 seconds.
: DDRS Rate Back Off Interval must be less than the DDRS Rate Blacklist Interval. DDRS Rate Stable Interval DDRS algorithm attempts higher data rates only when the current data rate is stable for a period of DDRS Rate Stable Interval. By default, it is set to 10 seconds. Tsunami 800 & 8000 Series - Software Management Guide 87 Advanced Configuration Parameter ATPC Upper Margin and Lower Margin Description SNR Upper Limit = Maximum Optimal SNR SNR Initial = SNR Upper Limit ATPC Upper Margin SNR Lower Limit = SNR Initial ATPC Lower Margin ATPC Algorithm, after reducing the power to honor the Maximum EIPR limit, adjusts the power based on Maximum Optimal SNR, ATPC Upper Margin and ATPC Lower Margin. To begin with, ATPC will adjust the power to bring the SNR to SNR Initial and adjusts power only when the current SNR goes beyond the SNR Upper Limit and SNR Lower Limit. By default, the ATPC Lower Margin and ATPC Upper Margin is 10 dB. To configure, type a value ranging from 0 to 20 dB. Click Local SNR-Table, to view the optimal SNR values that are exchanged with the peer for optimal throughput.ju Figure 5-30 An Example - SNR Information Tsunami 800 & 8000 Series - Software Management Guide 88 After configuring the required parameters, click OK and then COMMIT. 5.4.2 Wireless Outdoor Router Protocol (WORP) WORP is protocol, designed by Proxim that protects the network from packet collisions and solves the hidden node problem to transmit the data in an optimal way. To configure the WORP properties, navigate to ADVANCED CONFIGURATION > Wireless > Interface1 > WORP. The WORP Configuration screen appears:
Advanced Configuration Figure 5-31 WORP Configuration (BSU) Tsunami 800 & 8000 Series - Software Management Guide 89 Advanced Configuration Given below is the table which explains WORP parameters and the method to configure the configurable parameter(s):
Figure 5-32 WORP Configuration (SU) Parameter Description Mode Represents the device type (BSU, SU, End Point A or End Point B). Primary BSU Name Applicable only to an SU. Represents the Primary BSU name. If the primary BSU name is configured then SU establishes link with it. If a name is not configured then SU establishes link with any BSU on the same network, which meets the registration criteria.
: This is the system name as configured on a BSU. Tsunami 800 & 8000 Series - Software Management Guide 90 Parameter Secondary BSU Name Advanced Configuration Description This parameter serves as a Secondary / Redundant BSU for the SU and helps in reducing the network outage in the case of Primary BSU failure. This feature can help in reducing the network outage in case of the Primary BSU failure. This feature enables the SU to keep track of the Primary and the Secondary BSU availability through a proprietary protocol. This allows the SU to switch between the Primary and the Secondary BSU depending on the link status. If both the Primary and the Secondary BSU are not available, the SU attempts to find any other BSU within its network. This feature is activated only on a SU. By default, it is disabled. Use a non-empty string to enable this feature and an empty string to disable this feature. When this feature is enabled, it is mandatory to configure both the Primary and the Secondary BSU name on the SU. It is expected that the Primary and the Secondary BSUs are connected to the same L2 Broadcast domain and are configured with the same Network Name as the SU. The Primary and the Secondary BSU names should be unique. The Secondary BSU name is the System Name of the BSU used as a secondary BSU. Frequency Domain, Channel Bandwidth and Channel Offset should be same for all BSUs which participate in redundancy. If the BSU that participates in redundancy, operates in a channel that is blacklisted, SU will not switch. An SU will switch to a BSU only when the BSU has not reached its maximum SU limit. When Secondary BSU name is configured, Roaming is not applicable. When Secondary BSU name is configured, Automatic Channel Selection is automatically enabled on the SU. End Point A Name Applicable only to an End Point B. If a name is configured for End Point A then End Point B establishes a wireless link with it. If a name is not configured then End Point B establishes link with any End Point A on the same network that meets the registration criteria. Network Name It is a unique name of given to a logical network. Devices only within this logical network can establish wireless connection. The Network Name can be of 1 to 32 characters in length. By default it is MY_NETWORK. Tsunami 800 & 8000 Series - Software Management Guide 91 Advanced Configuration Parameter Description Max SUs Represents the maximum number of SUs that can register with a BSU. Given below are the base stations and the maximum number of subscribers supported by each of them:
Base Station Maximum Number of Subscribers MP-8200-BSU-G/ MP-8200-BSU MP-8250-BS9-G/ MP-8250-BS9 MP-8250-BS1-G/ MP-8250-BS1 MP-820-BSU-100 MP-822-BSU-100 MP-825-BS3-100
: Applicable only to the BSU. 250 250 250 32 32 32 WORP MTU Super Framing Sleep Mode WORP MTU (Maximum Transmission Unit) is the largest size of the data payload in wireless frame that can be transmitted. The MTU size can range from 350 to 3808 bytes for High throughput modes and 350 to 2304 bytes for legacy mode. The default and maximum value of the WORP MTU is 3808 bytes for higher throughput and 2304 bytes for legacy mode. Super Framing refers to the mechanism that enables multiple Ethernet/802.3 frames to be packed in a single WORP data frame. When the WORP MTU size is configured larger than the Ethernet frame size, then WORP constructs a super frame with size of the WORP MTU configured and pack multiple Ethernet frames. It results in reducing the number of frames transmitted over wireless medium thereby conserving wireless medium and increasing the overall throughput. By default, it is enabled. A BSU can put SUs in sleep mode when there is no data transmission during the past 15 seconds. This reduces the traffic congestion in the wireless medium and preserves the wireless bandwidth for other SUs in the network. BSU polls sleeping SUs once in every 4 seconds to maintain the wireless connection. By default, it is disabled on a BSU; however, in Sync mode, by default it is enabled and it cannot be disabled.
: Applicable only to the BSU. Tsunami 800 & 8000 Series - Software Management Guide 92 Advanced Configuration Parameter Multi Frame Bursting Description To achieve higher throughput, WORP protocol allows the transmitter or receiver to send multiple data frames in sequence without waiting for acknowledgment for every data frame and treats it as a single burst. During the burst transmission, the receiver is not allowed to interrupt the transmitter. After compilation of the burst, the receiver response by sending the acknowledgment. By default, the Multi Frame Bursting feature is enabled on the device. When Multi Frame Bursting is enabled, the maximum data frames that can be transmitted for each burst can be configured as part of Quality of Service (QoS).
: Though Multi Frame Bursting configuration is not applicable to SU/End Point B, the SU/End Point B does Multi Frame Bursting under the control of BSU/End Point A respectively. Auto Multi Frame Bursting Auto Multi Frame Bursting feature takes effect only when Multi Frame Bursting feature is enabled. When enabled, the device monitors all active QoS Service Flow Classes and determines the highest priority QoS Service Flow Class for all wireless connections. The device enables the burst transmission for the active highest priority QoS Service Flow Class and disables the burst transmission for other active lower priority QoS Service Flow Classes. By default, Auto Multi Frame Bursting is disabled on the device.
: Though Auto Multi Frame Bursting configuration is not applicable to SU/End Point B, the SU/End Point B does Auto Multi Frame Bursting under the control of BSU/End Point A respectively. Registration Timeout Represents the maximum time for an SU to register with the BSU or vice versa, or an End Point B to register with the End Point A or vice versa. The registration timeout value can be set in the range 1 to 10 seconds. The default registration timeout value is 10 seconds. Retry Count Represents the maximum number of times the data is retransmitted by the transmitter over the wireless medium, if acknowledgment from the peer is not received. The Retry Count parameter can be configured in the range 0 to 10. By default, it is set to 3. Input Bandwidth Limit and Output Bandwidth Limit This parameter limits the data received or transmitted to the wireless interface. It limits the data from a minimum of 64 Kbps to the maximum value specified in the License File.
: Input/Output Bandwidth throttling does not throttle broadcast/multicast traffic. These traffic can be throttled by the Maximum Information Rate (MIR) / Committed Information Rate (CIR) configured for the Downlink L2 Broadcast QoS Class in QoS Service Flow. See QoS Service Flow Configuration (SFC) Bandwidth Limit Type Specifies the action performed when the traffic utilization exceeds the configured input or output limits. By default it is set to Shaping. Policing: When the traffic utilization reaches the configured limit, the excess traffic will be discarded. Shaping: When the traffic utilization reaches the configured limit, the excess traffic will be buffered and sent at the rate specified in the Output Bandwidth Limit. Tsunami 800 & 8000 Series - Software Management Guide 93 Advanced Configuration Parameter Security Profile Name Description The Security Profile Name represents the encryption method used to encrypt the data over the wireless medium. The default configured Security Profile Name is WORP Security. See Security. Radius Profile Name The Radius Profile Name, containing the IP address of the RADIUS server, is used to authenticate an SU or an End Point B. See RADIUS.
: Not applicable in SU mode and End Point B mode. MAC ACL Status When enabled, based on the configured Access Control list (ACL), the BSU/End Point A decides if SU/End Point B can register with them respectively.
: Not applicable in SU mode and End Point B mode. Radius MAC ACL Status This parameter is used to enable authentication using RADIUS server. When enabled, the BSU or End Point A contacts the RADIUS server for authenticating the SU or End Point B during the registration process.
: Not applicable in SU mode and End Point B mode. Poll BackOff on Timeout When enabled, the BSU will back-off polling the SUs that timeout (due to interference or low SNR etc). When multiple SUs are connected, it is possible that some SUs are performing well without much retransmissions and other SUs are timing out. In such a scenario to make sure that the good SUs do not suffer due to under performing SUs, it is recommended to enable this parameter. By default, this parameter is disabled. It is recommended that this parameter should be enabled only when there is a mix of good and bad SUs and when good SUs are really suffering. Error Count Threshold If the error percentage of the transmitted frames is greater than or equal to the configured threshold, an SNMP trap is generated by the device. For traps, see Reference Guide available at http://my.proxim.com. RSSI Drop Threshold Applicable only to an SU/End Point B. If SNR, on any of the antenna ports, drops by more than or equal to the configured threshold, an SNMP trap is generated by the SU. For traps, see Reference Guide available at http://my.proxim.com. After configuring the required parameters, click OK and then COMMIT. Tsunami 800 & 8000 Series - Software Management Guide 94 Advanced Configuration
:
Modifying any of the WORP parameters result in temporary loss of connectivity between the transmitter and receiver. MAC ACL Status and RADIUS MAC ACL Status parameters cannot be enabled simultaneously. After configuring the required parameters, click OK and then COMMIT. Click Refresh, to view updated/refreshed blacklisted channels. 5.4.3 Wireless Interface Properties To configure the wireless interface properties, navigate to ADVANCED CONFIGURATION > Wireless > Interface 1 >
Properties. The Wireless Interface Properties screen is classified under the following categories: Basic, Sync, MIMO, Frequency Filter, DFS, DCS, Manual Blacklist, and Roaming.The parameters displayed in the Wireless Interface Properties screen may vary according to the device type. 5.4.3.1 Basic Under Basic tab, you can configure and view the following parameters. Figure 5-33 Wireless Interface Properties (BSU) Tsunami 800 & 8000 Series - Software Management Guide 95 Advanced Configuration The parameters under the Basic tab are described and tabulated below. Figure 5-34 Wireless Interface Properties (SU) Parameter Preferred Channel Bandwidth Descriptions By default it is to 20 MHz. 40 MHz can be selected for higher throughputs depending on the distance and signal quality. 5 and 10 MHz can be selected for greater flexibility in spectrum selection.
:
40 MHz channel bandwidth is not applicable in Legacy mode. A change in Preferred Channel Bandwidth will reset the Tx Rate, Maximum EIRP, and Antenna Gain to default value. For more details, see Frequency Domains and Channels. Tsunami 800 & 8000 Series - Software Management Guide 96 Parameter Preferred Channel Offset Advanced Configuration Descriptions
: Applicable only to MP-820-BSU-100; MP-822-BSU-100; MP-825-BS3-100;
MP-820-SUA-50+; MP-820-SUA-100; MP-822-SUA-100; MP-825-SUR-50+;
MP-825-SUR-100; MP-825-CPE-50; MP-825-CPE-100; MP-835-CPE-10;
MP-835-CPE-25; MP-835-CPE-50; MP-835-CPE-100; QB-825-EPR/LNK-50+;
QB-825-EPR/LNK-100; QB-835-EPR/LNK-25; QB-835-EPR/LNK-50 and QB-826-EPR/LNK-100 devices. This parameter helps to change the operating channel center frequency. If the predefined center frequencies are not desirable, the user can shift the center frequency to suit the requirement by configuring the Preferred Channel Offset. By default it is set to 0. The configurable range: -2 to +2 MHz. For example, consider a channel number 100 with the center channel frequency set to 5500 MHz. If the Preferred Channel Offset is set to 0 MHz, the center channel frequency remains at 5500 MHz. If you configure this to 2MHz then the center channel frequency will change to 5502MHz. Similarly if it is set to -2MHz, the center channel frequency will change to 5498 MHz.
:
Even though the center channel frequency is changed, the channel number still remains same, in this case 100. This parameter is not available for 82xx SU. Auto Channel Selection
(ACS) Auto Channel Selection (ACS) enables the device to determine the best channel for wireless data transmission with less interference. If ACS is enabled on the BSU/End Point A, it scans all the channels and selects the best channel at the startup. If ACS is enabled on the SU/End Point B, it continuously scans all the channels till it finds the suitable BSU/End Point A and connects to it. By default, ACS is disabled on BSU/End Point A and enabled on SU/End Point B.
: On BSU/End Point A, ACS is performed only during startup. Preferred Channel This parameter allows the user to select and operate in the Preferred Channel. Preferred channel can be configured only when ACS is disabled. If Dynamic Frequency Selection
(DFS) is active, the device will automatically pick a new channel when radar interference is detected.
: This parameter is not applicable for a SU (82xx & 82x series) as ACS is always enabled. Active Channel A read-only parameter that displays the current operating channel.
: Active Channel can be different from the Preferred Channel if radar or other interference is detected and the channel is blacklisted. Tsunami 800 & 8000 Series - Software Management Guide 97 Parameter Satellite Density Advanced Configuration Descriptions Satellite Density setting helps to achieve maximum bandwidth in a wireless network. It influences the receive sensitivity of the radio interface and improves operation in environments with high noise level. Reducing the sensitivity of the device enables unwanted noise to be filtered out (it disappears under the threshold). You can configure the Satellite Density to be Disable, Large, Medium, Small, Mini, or Micro. By default, Satellite Density is set to Large. The Medium, Small, Mini, and Micro settings are appropriate for higher noise environments; whereas, Large is appropriate for a lower noise environment. A long distance link can have difficulty in maintaining a connection with a small density setting because the wanted signal can disappear under the threshold. Consider both noise level and distance between the peers in a link when configuring this setting. The threshold should be chosen higher than the noise level, but sufficiently below the signal level. A safe value is 10dB below the present signal strength. If the Signal-to-Noise Ratio (SNR) is not sufficient, you may need to set a lower data rate or use antennas with higher gain to increase the margin between wanted and unwanted signals. In a point-to-multipoint link, the BSU or End Point A should have a density setting suitable for an SU or End Point B, especially the ones with the lowest signal levels (longest links). Take care when configuring a remote interface; check the available signal level first. Defer Threshold (CCA Threshold) parameter enables the device (BSU or SU) to establish a reliable link in high interference environments by increasing its value.This allows the device to defer the transmission as long as other interference signals in the wireless medium are greater than the configured Defer Threshold value. Interference Signal Radio Behavior Greater than or equal to Defer Threshold Defer the transmission Less than Defer Threshold Continue the transmission Given below are the Sensitivity Threshold Values corresponding to various Satellite Density values:
Satellite Density Receive Sensitivity Defer Threshold Threshold Large Medium Small Mini Micro Disabled 3 9 17 25 33 0-63 28 33 43 53 59 28 Tsunami 800 & 8000 Series - Software Management Guide 98 Parameter Descriptions Advanced Configuration
: When the remote interface is accidentally set to small and communication is lost, it cannot be reconfigured remotely and a local action is required to restore the communication link. Therefore, the best place to experiment with the level is at the device that can be managed without going through the link. If the link is lost, the setting can be adjusted to the correct level to bring the link back.
: Defer Threshold is not applicable for the Sync enabled devices. Sensitivity Sensitivity is identical to Receive Sensitivity Threshold. Please refer the table given above for the Receive Sensitivity Threshold values. STBC Status By means of the Satellite Density only specific Receive Sensitivity Threshold values can be set. By using the Sensitivity parameter tune the Receive Sensitivity Threshold values in the SNR range of
(0-63) and its default value is 0.
: Sensitivity parameter is visible only if the Satellite Density is set to Disable. STBC (Space Time Block Coding) is a provision to transmit multiple copies of a single data-stream to different antenna ports. After obtaining the data, the receiver compares, aggregates and processes it, to minimize the data loss. This redundancy in data increases the reliability of the data-transmission and therefore helps to improve the overall data transfer in the hostile RF environments. By default STBC is disabled.
: STBC is applicable only to 82x products and it works only when a single data-stream is used for transmission. Tsunami 800 & 8000 Series - Software Management Guide 99 Parameter Max EIRP Descriptions The maximum effective power that a radio antenna is allowed to radiate as per the regulatory standard. By default, the maximum EIRP is set as per the regulatory requirements for each frequency domain. Given below are the default maximum EIRP values that are set according to regulatory domain:
Advanced Configuration Regulatory Domain Maximum EIRP (dBm) PTP Mode PTMP Mode United States 5 GHz United States 5.8 GHz World 5 GHz World 4.9 GHz Canada 5 GHz Europe 5.8 GHz Europe 5.4 GHz Russia 5 GHz Thaiwan 5 GHz Canada 5.8 GHz Japan 4.9 GHz UK 5.8 GHz World 5.9 GHz US2 (5.3 & 5.8) GHz India 5.8 GHz Brazil 5.4 GHz Brazil 5.8 GHz 53 53 100 100 30 36 30 100 36 53 37 36 100 53 36 30 100 36 36 100 100 30 36 30 100 36 36 37 36 100 36 36 30 32 Australia 5.4 GHz 30 (20 and 40 MHz) 30 (20 and 40 MHz) Australia 5.8 GHz 36 Unites states 4.9 GHz 33(20MHz) 30 (10 MHz) 27 (5 MHz) 36 33(20MHz) 30 (10 MHz) 27 (5 MHz) Canada 4.9 GHz 33 (20 and 40 MHz) 33 (20 and 40 MHz) 30 (10 MHz) 27 (5 MHz) 30 (10 MHz) 27 (5 MHz) Legacy 5 GHz Japan 5.6 GHz 100 100 100 100 Tsunami 800 & 8000 Series - Software Management Guide 100 Parameter Descriptions Advanced Configuration Regulatory Domain Maximum EIRP (dBm) PTP Mode PTMP Mode World 5.8 GHz Indonesia 5.7 GHz US3 (5.2 & 5.8) GHz Egypt 5.8 GHz Thailand 5.2 GHZ Thailand 5.6 GHz US4 (4.9 & 5) GHz Industry Canada (IC) 5.2 GHz 100 100 53 36 23 30 53 23 100 100 36 36 23 30 36 23 Frequency Domains applicable for 81xx Products Regulatory Domain Maximum EIRP (dBm) United States 2.4 GHz World 2.4 GHz World 2.3 GHz World 2.5 GHz Europe 2.4 GHz PTP Mode 32 100 100 100 20 PTMP Mode 36 (BSU) 32(SU) 100 100 100 20
:
If the maximum EIRP is not defined in the above table then it is set to 100 (unlimited EIRP). Maximum EIRP criterion is enforced only when ATPC is enabled. For DFS bands (5.25-5.725 GHz), the EIRP limit is 23 dBm for the Subscriber units if DFS is not activated. Operation is not allowed in 5.600 - 5.650 GHz in USA, Canada, Australia and European Countries. Tsunami 800 & 8000 Series - Software Management Guide 101 Parameter Antenna Gain When using external antenna, the professional installer should ensure to configure proper antenna gain so that the radio does not exceed the EIRP allowed per regulatory domain. Descriptions Advanced Configuration Calculate the antenna gain as follows:
Antenna Gain to be configured = Antenna Gain of the antenna used - Cable Loss Example: Consider an example where the device is operating in United States 5.3 GHz with the EIRP 30 dBm. The antenna gain of the antenna used is 23 dBi and the cable loss is 1dB. Given this case, Configurable Antenna Gain = [23 dBi 1 dB] = 22 dBi Maximum Radio Power = EIRP Configured Antenna Gain
= 30 dBm 22 dBi
= 8 dBm With this configuration, the ATPC feature will limit the radio power to a maximum of 8 dBm to avoid exceeding EIRP limit of 30 dBm. Tsunami 800 & 8000 Series - Software Management Guide 102 Parameter Descriptions Advanced Configuration Improper configuration of Antenna Gain will affect the sensitivity of the radio card. As the radar detection threshold is fixed by ETSI, the FCC and IC, any change in sensitivity of the radio card will result in false radar detections or actual radar signal not being detected. If the configured antenna gain is higher than the actual antenna gain, Radar signals may go undetected. If the configured antenna gain is lower than the actual antenna gain, False Radar may be detected. Configure the threshold for radar detection at the radio card to compensate for increased external antenna gains. The Antenna Gain value ranges from 0 to 40 dBi. For devices with connectorized antenna, the Antenna Gain by default is set to zero dBi. Given below are the default Antenna Gain, for devices with integrated antenna:
Product (s) Antenna Gain MP-8250-BS1-G/ MP-8250-BS1 MP-8150-SUR-100 MP-8250-BS9-G/ MP-8250-BS9 MP-822-BSU-100 MP-822-SUA-100 MP-825-BS3-100 MP-825-SUR-50+
MP-825-SUR-100 MP-825-CPE-50 MP-825-CPE-100 MP-835-CPE-10 MP-835-CPE-25 MP-835-CPE-50 MP-835-CPE-100 QB-8250-EPR-G/LNK-G QB-8250-EPR/LNK QB-825-EPR/LNK-50+
QB-825-EPR/LNK-100 QB-835-EPR/LNK-25 QB-835-EPR/LNK-50 QB-826-EPR/LNK-100 23 dBi 21 dBi 16 dBi 15 dBi 23 dBi 15 dBi Wireless Inactivity Timer Resets the wireless interface if there is no change in the Tx and Rx Packet Count in the specified interval of time. The default value is set to 5 seconds (disabled if set to 0 seconds) and can be configured between 5 to 600 seconds. Tsunami 800 & 8000 Series - Software Management Guide 103 Parameter Legacy Mode Advanced Configuration Descriptions By default, Legacy Mode is disabled. When enabled, the MP 800 & 8000 BSU and SU devices can inter-operate with the legacy products of the Tsunami MP.11 family. The MP 800 & 8000 devices that provide legacy support are, MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 MP-8200-SUA MP-8250-SUR MP-820-SUA-50+
MP-820-SUA-100 MP-822-SUA-100 MP-825-SUR-50+
MP-825-SUR-100 MP-825-CPE-50 MP-825-CPE-100 MP-835-CPE-10 MP-835-CPE-25 MP-835-CPE-50 MP-835-CPE-100
: MP 800/8000 BSU device in legacy mode can connect to a MP 800/8000 SU device only when configured in legacy mode. After configuring the required parameters, click OK and then COMMIT.
: Reboot the device, if you have changed any of the Wireless Interface parameters with an asterisk(*) symbol. 5.4.3.2 Sync WORP Sync is a TDMA (Time Division Multiple Access) based implementation of the Proxims proprietary Wireless Outdoor Routing Protocol which eliminates the co-location interference. With WORP Sync, all the BSUs transmission and reception are time-synchronized by means of GPS Synchronization techniques. This eliminates the co-location interference and improves the overall performance of the network.
: Sync tab is applicable only for a BSU and by default, it is in disabled state. Sync Status can be set to Enable/Disable by selecting an option from the drop-down menu. For a BSU, Set the Sync Status to Enable, to configure or modify the Sync parameters. Under the Sync tab, by default Compatibility is set to Proxim. Using the drop-down menu you can also select Cambium-PMP or ePMP. Based on the option selected, the corresponding WORP Sync screen appears as shown below. Tsunami 800 & 8000 Series - Software Management Guide 104 5.4.3.2.1 Proxim Advanced Configuration Figure 5-35 WORP Sync (Proxim) After configuring all the parameters, click OK and COMMIT the changes.To view the latest configuration, click on Sync Configuration at the bottom left corner of the WORP Sync screen. The following Sync configuration screen appears for Proxim mode. Tsunami 800 & 8000 Series - Software Management Guide 105 Figure 5-36 Sync Configuration (Proxim) 5.4.3.2.2 Cambium-PMP Advanced Configuration Figure 5-37 WORP Sync (Cambium-PMP) After configuring all the parameters, click OK and COMMIT the changes.To view the latest configuration, click on Sync Configuration at the bottom left corner of the WORP Sync screen. The following Sync configuration screen appears for Proxim/Cambium-PMP compatibility mode. Tsunami 800 & 8000 Series - Software Management Guide 106 Figure 5-38 Sync Configuration (Cambium-PMP) 5.4.3.2.3 ePMP Advanced Configuration Figure 5-39 WORP Sync (ePMP) After configuring all the parameters, click OK and COMMIT the changes.To view the latest configuration, click on Sync Configuration at the bottom left corner of the WORP Sync screen. The following Sync configuration screen appears for Proxim/Cambium-PMP/ePMP compatibility mode. Tsunami 800 & 8000 Series - Software Management Guide 107 Figure 5-40 Sync Configuration (ePMP) To view the Sync configuration support for PROXIM/Cambium-PMP/ePMP compatibility modes at different data rates for various bandwidths, click on Required Minimum Data Rate for Different DL Ratio at the bottom left corner of the WORP Sync screen. The following screen appears for Proxim/Cambium-PMP compatibility mode. Advanced Configuration Figure 5-41 Required Minimum Data Rate for Different DL Ratio & Sub-slot configurations The WORP Sync screen parameters are described and tabulated below:
Parameter Sync Status GPS Source Descriptions By default it is enabled on a BSU. This parameter will change based on the GPS source. Set to Serial if Garmin module is used. Set to Ethernet if CTM2 module (CMM or CMM Micro) is used.
: For 82xx series, it is a read-only parameter as the hardware pin configuration for Serial and Ethernet ports remain the same; however, for 82x series, it is a variable parameter due to the varied hardware pin configuration. Tsunami 800 & 8000 Series - Software Management Guide 108 Parameter Descriptions Compatibility By default it is set to Proxim. It is used when the network cluster has only Proxim BSUs. Advanced Configuration Set Cambium-PMP if the devices have to co-exist with Cambium-PMP Base Stations in the network. If this option is selected, configure the Sync offset field. Set ePMP if the devices have to co-exist with Cambium-ePMP Base Stations in the network. If this option is selected, configure the Sync offset field.
: Cambium doesnot support the synchronization of the co-located PMP and ePMP base stations on the same tower. The time frame for the various options are given below:
Compatibility Mode Time Frame (micro sec) Proxim Cambium-PMP ePMP 2500 2500 5000 DL Ratio This parameter specifies the time allocated for downlink transmission in terms of percentage, for uplink transmission, it is internally derived based on the DL ratio. For Proxim and Cambium-PMP compatibility modes:
UL (Uplink) Ratio = 100 - DL (Downlink) Ratio Delays = Inter Frame Delay + Intra Frame Delay DL Time Frame = ((Time Frame - Delays) * DL ratio)) / 100 UL Time Frame = ((Time Frame - Delays) * UL ratio)) / 100 By default it is set to 50. The configurable values: 15 - 85;It will be in multiples of 5. For ePMP compatibility mode:
UL (Uplink) Ratio = 100 - DL (Downlink) Ratio DL Time Frame = ((Time Frame * DL ratio) / 100 ) - Intra Frame Delay UL Time Frame = ((Time Frame * UL ratio) / 100 ) - Inter Frame Delay By default it is set to 75. The configurable values are: 30, 50, 75 Tsunami 800 & 8000 Series - Software Management Guide 109 Parameter Descriptions Sub Slots The Sub-slots values for all the compatibility modes are tabulated below:
Advanced Configuration Compatibility Default Value Mode Proxim Cambium-PMP ePMP 1 1 1 Configurable Values 1&2 1&2 1,2 & 3
: Before configuring the sub-slot value to more than, 2 - please check the Minimum required data rate Table 5-41, to know, if it supports the corresponding DL ratio or not. Exempting this would lead to issues related to link establishment through WORP. Also, configure the DDRS minimum data rate as per the table, when the DDRS is enabled. Inter Frame Delay This parameter specifies the time interval between two time frames. Intra Frame Delay This parameter specifies the time interval between DL (Downlink) and UL (Uplink) time frames. Control Slots This parameter is applicable only to Cambium-PMP & ePMP compatibility modes. By default, it is set to 0. The configurable values: 0 - 15. Intra Frame Delay = 100 + (Control Slots * 10) Max Distance By default it is set to 0. The configurable values: 0 - 40 miles. Inter Frame Delay =100 + (max_distance -2) * 10 Tsunami 800 & 8000 Series - Software Management Guide 110 Parameter Descriptions Sync offset The Sync offset values are tabulated below:
Advanced Configuration The values given in the first table are applicable for the Cambium-PMP compatibility mode:
Sync Hardware Module 8200 Sync Offset Value
((s) in microseconds) 820 Sync Offset Value
((s) in microseconds) 30% and 50% DL 75%DL 30% and 50% DL 75%DL CMM CTM2 GPS 16x 3470 3420 3590 3870 3820 3990 3440 3390 3560 3840 3790 3960 The values given in the tables below are applicable for the ePMP compatibility mode:
For MP-8200 devices 30% DL 50% DL 75% DL 16x GPS CTM2 CMM 3590 3420 3470 3590 3420 3470 3990 3820 3870 For MP-820 devices 30% DL 50% DL 75% DL 16x GPS CTM2 CMM 3560 3390 3440 3560 3390 3440 3960 3790 3840 BSU Operation
(without GPS signal) This parameter defines the BSU operation when the GPS signal is not available. By default it is set to Enable. The configurable options: Enable and Disable, for both the options, GPS pulse is used for time synchronization. Enable:
The BSU operates normally even if five consecutive GPS pulses are missed as the internal clock synchronizes itself with the last received pulse. In case of no GPS pulse at all, the internal clock is used. Disable: If five consecutive GPS pulses are missed, the BSU is disabled to avoid interference to the nearby sectors. Tsunami 800 & 8000 Series - Software Management Guide 111 Advanced Configuration
:
WORP Sync version supports fixed data rates and DDRS (Dynamic Data Rate Selection). In Cambium-PMP & ePMP mode, configure the Control Slots value based on the configuration of the Cambium devices. The Control Slots and Maximum Distance configuration values are internally required to calculate the Intra and Inter Frame Delays, and also to ensure proper synchronization timing between the Proxim and Cambium systems. 5.4.3.3 MIMO The MIMO Properties tab allows you to configure the Multiple-Input-Multiple-Output (MIMO) parameters to achieve high throughput and longer range. The MIMO screen appears as shown below. Figure 5-42 MIMO Properties Parameter Description Frequency Extension Frequency Extension is applicable only when the Channel Bandwidth is set to 40 MHz. While choosing 40MHz bandwidth, you can select either 40 PLUS (Upper Extension Channel) or 40 MINUS (Lower Extension Channel). 40 PLUS means the center frequency calculation is done for 20MHz and add another 20MHz to the top edge of 20MHz. 40 MINUS means the center frequency calculation is done for 20MHz and add another 20MHz to the bottom edge of 20MHz. Tsunami 800 & 8000 Series - Software Management Guide 112 Advanced Configuration Parameter Guard Interval Description Guard Interval determines the space between symbols being transmitted. The guard interval can be configured as either Short GI - 400n seconds or Full GI-800n seconds. In 802.11 standards, when 40 MHz Channel Bandwidth is configured then Short GI can be used to improve the overall performance and throughout. By default, Full GI is enabled for 5 MHz, 10 MHz and 20 MHz channels.
:
Short GI-400 nSec is valid only for 40 MHz channel bandwidth Short GI-400 nSec is not valid for 82x devices. Rx Antennas Status Allows the user to select the antenna(s) for receiving data. Select the check-box against each antenna(s) for receiving data and click OK.
: Atleast two Rx antenna ports should be enabled when data stream is dual or auto. After configuring the required MIMO parameters, click OK and then COMMIT. 5.4.3.4 Frequency Filter The Frequency Filter tab allows you to configure the lower and upper frequency band edges, which helps to limit the available frequency band, for a given frequency domain, to a smaller band. By limiting the frequency band, the time taken by a device to scan and connect to any other device in the network is reduced. The Frequency Filter Configuration screen appears as shown below. Figure 5-43 Frequency Filter Configuration The frequency range limit for the filter lower and upper edge is 0 - 10000 MHz; by default, the lower frequency edge is set to 0 MHz and the upper frequency edge is set to 10000 MHz. Configure the values and Click OK and then COMMIT. Tsunami 800 & 8000 Series - Software Management Guide 113 5.4.3.5 Dynamic Frequency Selection (DFS) The Tsunami products support Dynamic Frequency Selection (DFS) for FCC, IC, and ETSI regulatory domains per FCC Part 15 Rules for U-NII devices, IC RSS-210, and ETSI EN 301-893 regulations, respectively. These rules and regulations require that the devices operating in the 5 GHz band must use DFS to prevent interference with RADAR systems. Advanced Configuration
: For US DFS countries:
Units deployed after June 2016, United States 5.3 GHz and 5.4 GHz band follows the DFS FCC15407 Rule. Units sold or deployed before June 2016, the user can either use the existing DFS Rule or configure the DFS FCC15407 Rule from the drop-down menu. After configuration click OK, COMMIT and then REBOOT. 5.4.3.5.1 DFS in BSU or End Point A mode Under the DFS tab for a BSU / End Point A, you can configure and view the following parameters. Figure 5-44 Dynamic Frequency Selection (BSU / End Point A) Explained below is the DFS functionality and the way it operates on a BSU or in End Point A devices. 1. Based on the selected frequency (regulatory) domain, DFS is automatically enabled on the device. 2. During bootup, If Automatic Channel Selection (ACS) is disabled on the device, the device chooses the Preferred Channel to be the operational channel.
: By default, ACS is disabled on the BSU or End Point A device. If ACS is enabled, then the device scans all the channels and selects the channel with the best RSSI to be the operational channel. 3. Once the operating channel is selected, the device scans the channel for the presence of the RADAR for a duration of the configured Channel Wait Time (by default, configured to 60 seconds). During this time, no transmission of data occurs. If no RADAR is detected, the device starts operating in that channel. 4. Tsunami 800 & 8000 Series - Software Management Guide 114 Advanced Configuration 5. If RADAR is detected, the channel is blacklisted for 30 minutes. Now, ACS will scan all the non-blacklisted channels and select the channel with best RSSI. Upon choosing the best channel, the device again scans the selected channel for the presence of the RADAR for a duration of the configured Channel Wait Time. Again, during this time no transmission of data occurs. If no RADAR is detected, it operates in that channel else repeats step 5. 6. 7. While operating in a channel, the device continuously monitors for potential interference from a RADAR source (this is referred to as in-service monitoring). If RADAR is detected, then the device stops transmitting in that channel. The channel is added to the blacklisted channel list. 8. A channel in the blacklisted list can be purged once the Non Occupancy Period (NOP) has elapsed for that channel.
:
When a channel is blacklisted, all its sub-channels that are part of the current channel bandwidth are also blacklisted. For Europe 5.8 GHz channel, once the device finds a RADAR free channel (after 60 seconds RADAR scan), it does not perform scan for the next 24 hours. This is not applicable when device is rebooted or a particular channel is blacklisted earlier. Even if the preferred channel is configured with a DFS channel manually, the SU will scan for the BSU / End PointA's channel and associates automatically. 5.4.3.5.2 DFS in SU or End Point B Mode Under the DFS tab for a SU / End Point B, you can configure and view the following parameters. Figure 5-45 Dynamic Frequency Selection (SU / End Point B) Explained below is the DFS functionality and the way it operates on an SU or a End Point B. 1. When SU/End Point B has no WORP link, it scans continuously all the channels in the configured Frequency Domain for the presence of BSU/End Point A. If suitable BSU/End Point A is found in any scanned channel, the SU or End Point B tries to establish WORP link. 2. After selecting the suitable BSU/End Point As channel, If SU/End Point B DFS is disabled, then SU/End Point B tries to connect to BSU/End Point A. Tsunami 800 & 8000 Series - Software Management Guide 115 Advanced Configuration If SU/End Point B DFS is enabled, the SU/End Point B scans the selected channel for the presence of the RADAR for a duration of the configured Channel Wait Time (by default configured to 60 seconds). During this time, if the SU/End Point B detects radar, the channel is blacklisted and it starts scanning on non-blacklisted channels for a BSU/End Point A as given in step 1. If no radar is detected, a connection will be established. 3. While WORP link is present, the SU/End Point B continuously monitors the current active channel for potential interference from a RADAR source (this is referred to as in-service monitoring). If RADAR is detected, the SU/End Point B sends a message to the BSU or End Point A indicating the RADAR detection on the active channel and blacklists that channel for Non Occupancy Period (NOP). The default NOP is 30 Minutes. On receiving the RADAR detection message from SU/End Point B, the BSU/ End Point A blacklists the active channel and ACS starts scanning for an interference free channel.
: The BSU will blacklist the channel only when the number of SUs reporting the RADAR equals or exceeds the configured SUs Reporting RADAR parameter. 4. A blacklisted channel can be purged once the Non Occupancy Period (NOP) has elapsed.
:
On the SU/End Point B, if the preferred channel is configured with a DFS channel then SU will scan all the channels even if ACS is disabled. When a channel is blacklisted, all its sub-channels that are part of that channel bandwidth are also blacklisted. Parameter Channel Wait Time Description Once the device selects the best channel, it scans that channel for the presence of RADAR for a period of set Channel Wait Time. The wait time can be configured in the range 60 to 3600 seconds. By default, the wait time is set to 60 seconds. SUs Reporting RADAR Applicable only to BSU. When an SU detects a RADAR, it reports to BSU. The BSU will take a decision on whether to blacklist this channel based on SUs Reporting RADAR parameter. If the number of SU reporting RADAR equals or exceed the configured SUs Reporting RADAR parameter then BSU blacklists that channel. If SUs reporting the RADAR is less than this configured value then BSU continues to operate in the same channel. The range varies depending on the product license. By default, it is set to 0. DFS Status Applicable only to SU or End Point B devices. An SU or End Point B device can either enable or disable DFS. By default, DFS is disabled. For detailed information on DFS enabled countries, see Frequency Domains and Channels. Blacklist Information The parameters under Blacklisted Information are described in the table given below. Parameter Description Frequency Range Indicates the blacklisted channel in terms of frequency range. Tsunami 800 & 8000 Series - Software Management Guide 116 Parameter Reason Specifies the reason for blacklisting a frequency range. Following are the reasons for blacklisting a frequency range:
Description Advanced Configuration 1. Remote Radar: An SU/End Point B detects radar and informs BSU/End Point A respectively. 2. Local Radar: The device detects the radar on its own. Interference: BSU detects interference based on the retransmission threshold. 3. 4. Unusable: For bandwidths more than 5 MHz, frequencies that are not usable because they fall in the other, radar / manual blacklisted frequency range. For example, if channel 110 is blacklisted, then channels 107 to 113 will become unusable for 20 MHz bandwidth. That is, in terms of frequency range, (5540 - 5560) MHz is blacklisted. 5. Manual: A frequency range is manually blacklisted by the administrator. Time Elapsed This parameter specifies the time elapsed since the frequency range was blacklisted due to radar / interference. When the frequency range is blacklisted it will be white listed after 30 minutes. This parameter is applicable for radar and interference blacklisted frequency range only. Click Refresh, to view updated / refreshed blacklisted frequency range. After configuring the required parameters, click OK and then COMMIT. 5.4.3.6 Dynamic Channel Selection (DCS) Dynamic Channel Selection feature enables you to monitor the link quality (retransmissions due to interference) on the operating channel. If the link quality is found to be below the threshold, then the device stops transmitting on that channel and switches to another channel, among the available channels without terminating the link. 5.4.3.6.1 DCS in BSU / End Point A Mode Under the DCS tab for a BSU / End Point A, you can configure and view the following parameters. Figure 5-46 Dynamic Channel Selection (BSU or End Point A) Tsunami 800 & 8000 Series - Software Management Guide 117 Advanced Configuration Explained below is the DCS functionality and the way it operates on (BSU / End Point A) devices. DCS Status can be set to enable/disable by selecting an option from the drop-down menu. By default, it is in disabled state. When DCS is enabled, the device periodically monitors the channel for link quality. In case of interference, this feature automatically changes the current operating channel. The channel change is triggered, When the percentage of retransmissions computed exceeds the configured Retransmission Threshold value.
(or) The number of SUs reporting bad channel equals or exceeds the configured SUs Reporting Interference value. If one of the above conditions is satisfied then the current operating channel will be blacklisted for 30 Minutes (due to interference), and the BSU will switch to the next available channel. A channel in the blacklisted list is purged once the Non Occupancy Period (NOP) has elapsed for that channel. The BSU switches to the preferred channel once it is de-blacklisted.
:
If DCS is enabled in BSU, ensure that ACS is enabled in SU. For DCS to work, the channel list should have more than one available channel. 5.4.3.6.2 DCS in SU / End Point B Mode Under the DCS tab for a SU / End Point B, you can configure and view the following parameters. Figure 5-47 Dynamic Channel Selection (SU or End Point B) Explained below is the DCS functionality and the way it operates on (SU / End Point B) devices. DCS Status can be set to enable/disable by selecting an option from the drop-down menu. By default, it is in disabled state. When DCS is enabled, the device computes the percentage of retransmissions (due to interference) for each link:
If the link quality is above the threshold, the SU continues to operate in the same channel. If the link quality is bad, the SU will trigger DCS message with reason code as interference to the connected BSU.
: SU will not blacklist the channels due to interference. Tsunami 800 & 8000 Series - Software Management Guide 118 Advanced Configuration Given below is the table which explains Dynamic Channel Selection (DCS) parameters and the method to configure the configurable parameter(s):
Parameter Description Dynamic Channel Selection (DCS) Status This parameter is used to enable DCS on the device. By default, DCS is disabled. To enable, select Enable and Click OK. Retransmission Threshold This parameter enables to configure the retransmission threshold percentage on the device. The device computes percentage of retransmission for each link and compares with the configured threshold. If the retransmission percentage is greater than the user configured retransmission threshold, the link is considered as bad link. By default, the retransmission percentage is set to 50. SUs Reporting Interference Applicable only to BSU. The BSU decides to blacklist the operating channel based on the value configured for this parameter. If the number of SUs reporting interference (Between BSU and SU) equals or exceeds the configured value of this parameter then the channel is blacklisted. Else, it continues to operate in the same channel. By default, Bad Link Threshold value is set to 1. Blacklist Information Refer Blacklist Information, for detailed explanation. After configuring the required parameters, click OK and then COMMIT. Click Refresh, to view updated / refreshed blacklisted frequency range. 5.4.3.7 Manual Blacklist Manual Blacklisting enables you to manually blacklist one or more channels in terms of frequency range for the following reasons: radar, interference, and to reduce the number of channels to scan. The Manual Blacklist screen appears as shown below. Tsunami 800 & 8000 Series - Software Management Guide 119 Figure 5-48 Manual Blacklist Advanced Configuration To manually blacklist a frequency range, enter the start and end frequency in the Start Frequency and End Frequency boxes respectively. Next, click Add. All the selected frequency ranges are added to the Blacklist Information table. After configuring the required parameters, click OK and then COMMIT. Click Refresh, to view updated/refreshed manually blacklisted frequency range. For detailed explanation of Blacklist Information, please refer Blacklist Information. However, there are few conditions to be followed while manually blacklisting a channel:
When ACS is disabled, the preferred channel and its sub-channels that are part of the current channel bandwidth cannot be manually blacklisted. When WORP link is UP, the active channel and its sub-channels that are part of the current channel bandwidth cannot be manually blacklisted. When DFS/ACS is enabled, at least one channel or its sub-channels that are part of the current channel bandwidth should be available for operation. That is, all the frequencies cannot be blacklisted.
:
Only manually blacklisted frequencies can be de-blacklisted. If a manually blacklisted frequency range overlaps with the operating channel then the WORP link will be terminated and the BSU will trigger channel selection procedure. Manually blacklisted frequency information is not exchanged between the BSU and SU as it local to the device. 5.4.3.8 Roaming The Roaming feature enables a mobile SU to provide seamless network services by constantly monitoring the quality of the wireless link with the current associated BSU.
: Roaming feature is not applicable to devices operating in WORP Sync mode; by default, it is disabled. The Roaming Configuration screen appears as follows. Figure 5-49 Roaming (WORP Sync Mode) Tsunami 800 & 8000 Series - Software Management Guide 120 Advanced Configuration Figure 5-50 Roaming Parameter Description Roaming Status The Roaming feature can either be enabled or disabled on a BSU. By default, it is disabled. When the roaming status is enabled on a BSU, the other roaming parameters such as Roaming Link Profile, Downlink Buffering, Announce Period, Maximum Packets Per Burst and Roaming VLAN ID are configurable. These parameters are used by the registered SU when any of the roaming procedure starts.
: Roaming can be enabled on the BSU, independent of the roaming status of the SU. Downlink Buffering This parameter provides support to buffer the downlink traffic from BSU to SU. This buffered traffic is sent to the Roaming SU through a newly associated BSU, using the Inter BSU protocol. Roaming Link Profile This parameter enables you to configure a roaming link profile for the roaming enabled SUs. When roaming is enabled on the BSU, select a profile from the configured link profiles, which serves as the roaming profile. The Default profile serves as the roaming profile when no profile is selected. The configured roaming profile is mapped to all the roaming enabled SUs. For the SUs with roaming disabled, the profile configured in the SU profiles list will be used. When roaming is disabled on the BSU, the SUs are mapped to the corresponding profile from the SU Profiles list. Tsunami 800 & 8000 Series - Software Management Guide 121 Advanced Configuration Parameter Announce Period Description When roaming is enabled on a BSU, the BSU sends ANNOUNCE messages for every configured Announce period. The Announce period can be configured in the range 25 to 100 milliseconds. By default, it is configured to 25 milliseconds. When roaming is disabled on a BSU, the Announce period is set to 150 milliseconds.
: Reducing the Announce Period improves the roaming time and may result in lower throughput. Max. Packets Per Burst When roaming is enabled on a BSU, the maximum number of messages that can be sent in a burst can be configured in the range 1 to 16. When roaming is disabled on a BSU, the maximum packets per burst is set to 4.
:
Reducing the number of messages per burst improves the roaming time and may result in lower throughput. If the maximum packets per burst configured in QoS (See Adding a New Service Flow (SFC)) is greater than this value, then this parameter supersedes. Roaming VLAN ID This parameter enables the user to configure the VLAN ID for Roaming management frames. By default, the Roaming VLAN ID is set to -1 which indicates no tag is added to the Roaming management frame. To set VLAN tag to the Roaming management frame, enter a value ranging from 1 to 4094. After configuring the above parameters, click OK and then COMMIT. 5.4.4 BSU / SU Profiles In the BSU / SU Profiles tab, you can explicitly map a link profile to the peer device (See Link Profiles). When a link is established, using the peer MAC address, it is associated with a link profile based on the mapping created here. When no explicit mapping is created then the link is associated with the default profile. 5.4.4.1 Add a Profile
: In this section, we have explained the method to map a link profile to an SU. The same method should be followed to map a link profile to a BSU. To map a link profile to an SU device, navigate to ADVANCED CONFIGURATION > Wireless > Interface 1 > SU Profiles. The SU Profiles screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 122 Advanced Configuration Click Add in the SU Profiles screen. The SU Profile Add Entry screen appears:
Figure 5-51 SU Profiles Configure the following parameters:
Figure 5-52 Add an SU Profile Entry SU Wireless MAC Address: Type the MAC Address of the peer. Device Name: Type the name of the peer. Link Profile Name: Map a link profile to the peer from the list of Link Profiles. After configuring the required parameters, click ADD and then COMMIT. The profile is mapped to the peer device and is listed in the SU Profiles screen. Figure 5-53 SU Profiles Entry Added Consider a case where a device is currently connected to its peer and no link profile is explicitly mapped. Then in such a scenario, the default link profile is assigned and displayed in the SU Profiles screen along with a Save option, as shown below:
Tsunami 800 & 8000 Series - Software Management Guide 123 Advanced Configuration For such entries, user has the option to click Save button and configure this mapping in the profiles table. When you click Save, the following screen appears:
Figure 5-54 Save an SU Profile If you wish to map the peer with a profile other than default, then select a link profile (say Profile1) from Link Profile Name and click Add. Figure 5-55 Add an SU Profile Figure 5-56 SU Profile Added The newly configured link profile will not be the Active Link Profile until you commit the changes. That is the reason, in the above screen, you are still able to see Default as the Active Link Profile for index 2, even though Profile1 is configured. When you commit the changes, the Active Link Profile will change to Profile1, as shown in the following figure. Tsunami 800 & 8000 Series - Software Management Guide 124 Advanced Configuration Figure 5-57 Active SU Link Profile
:
You can add a maximum of 250 entries in the profiles table. Under Link Statistics page, you can view the active profile the link is associated with. 5.4.4.2 Edit a Mapped Profile
: In this section, we have explained the method to edit a mapped link profile of an SU. The same method should be followed to edit a mapped link profile of a BSU. To edit a mapped profile, click Edit in the SU Profiles screen. The SU Profile Edit Entry screen appears:
Make the necessary edits, and click OK followed by COMMIT. Figure 5-58 Edit a Mapped Profile
: When the radio mode is changed (say BSU to SU, or SU to BSU), the link profiles and the peer profile mapping list is retained. 5.5 Security 5.5.1 Wireless Security The Wireless Security feature helps to configure security mechanisms to secure the communication link between a BSU and an SU, and a link between End Point A and End Point B. By default, the default security is WORP Security. A maximum of eight security profiles can be created as required; however, only one security profile can be active at a time. The active security profile is configured as part of the WORP property Security Profile Name. For a security profile to be active, it must be enabled. Refer to Wireless Outdoor Router Protocol (WORP) for more details. Tsunami 800 & 8000 Series - Software Management Guide 125
: Configure the same security profile on the either ends to establish a connection. To configure the Wireless security profile, navigate to ADVANCED CONFIGURATION > Security > Wireless Security. The Wireless Security Configuration screen appears:
Advanced Configuration Given below is the table which explains Wireless Security parameters:
Figure 5-59 Wireless Security Configuration Parameter Profile Name Entry status Edit Description Specifies the security profile name. By default, it is WORP Security. Enables a user to either Enable or Disable the security profile on the device. By default, it is enabled. Enables you to edit the existing security profiles. Click Edit to modify any of the security profile parameters. After configuring the required parameters, click OK and then COMMIT. 5.5.1.1 Creating a New Security Profile To create a new security profile, click Add in the Wireless Security Configuration screen. The following Wireless Security Add Row screen appears:
Figure 5-60 Creating a New Security Profile Tsunami 800 & 8000 Series - Software Management Guide 126 Given below is the table which explains the method to create a new Security Profile:
Parameter Description Profile Name A name to uniquely identify a security profile name. Encryption Type Select encryption type as either None, WEP, TKIP or AES-CCM. Advanced Configuration 1. None - If the encryption type is selected as None, then there exist no security to the data frames transmitted over the wireless medium. 2. WEP (Wired Equivalent Privacy) - Represents the WEP Encryption type, which uses RC4 stream cipher for confidentiality and CRC-32 for integrity. The supported key lengths for WEP are 5/13/16 ASCII characters or 10/26/32 Hexadecimal digits. Key1 / Key 2 / Key 3 / key 4: You can configure a maximum of four WEP keys. Enter 5/13/16 ASCII Characters or 10/26/32 Hexadecimal digits for WEP keys. Transmit Key: Select one out of the four keys described above as the default transmit key, which is used for encrypting and transmitting the data. 3. TKIP - Represents the TKIP Encryption type, which uses RC4 stream cipher for confidentiality. TKIP provides per-packet key mixing, a message integrity check and a re-keying mechanism. It uses 128-bit keys for encryption. The key length for TKIP is 16 ASCII characters or 32 Hexadecimal digits. Key1 / Key 2 / Key 3 / key 4: You can configure a maximum of four TKIP keys. Enter 16 ASCII characters or 32 Hexadecimal digits. Transmit Key: Select one out of the four keys described above as the default transmit key, which is used for encrypting and transmitting the data. 4. AES-CCM - Represents CCM Protocol with AES Cipher restricted to 128 bits. Key: Enter 16 ASCII characters or 32 Hex Digits for AES-CCM encryption keys. Entry status Network Secret Enables you to either Enable or Disable the security profile on the device. By default, it is enabled. Enter the WORP Protocol Secret Key, ranging from 6 to 32 characters, used for authenticating an SU with a BSU, and an End Point B with End Point A. The network secret should be same for both BSU and SU. Similarly, the network secret should be same for an End Point A and an End Point B.
:
You can create a maximum of eight security profiles. A QuickBridge supports AES-CCM encryption type only. Special characters like - = \ " ' ? / space are not allowed while configuring the keys. All four Keys (Key1, Key2, Key3, Key4) must be of same length and same type, that is, all four Keys must be either ASCII characters or Hexadecimal digits. Transmit Key can be any one of the four keys, provided all the four keys are same in an SU and BSU, or End Point devices. WEP and TKIP Encryption types are supported only in legacy modes. The encryption mode should not be selected as AES-CCM while the device is interoperating with legacy Tsunami MP.11 family devices. After configuring the required parameters, click Add and then COMMIT. Tsunami 800 & 8000 Series - Software Management Guide 127 5.5.1.1.1 Sample Security Profile Configuration Advanced Configuration End Point A End Point B Profile Name WORP Security Encryption Type AES-CCM WORP Security AES-CCM Key 1234567890abcdef1234567890abcdef
(32 Hexadecimal digits) or publicpublic1234
(16 ASCII Characters) 1234567890abcdef1234567890abcdef
(32 Hexadecimal digits) or publicpublic1234
(16 ASCII Characters) Entry Status Enable Network Secret public Enable public 5.5.1.2 Editing an existing Security Profile To edit the parameters of the existing security profiles, click Edit The Wireless Security Edit Row screen appears:
icon in the Wireless Security Configuration screen. Edit the required parameters and click OK and then COMMIT. Figure 5-61 Wireless Security Edit Row 5.5.2 RADIUS
:Applicable only to a BSU and End Point A devices. The RADIUS tab allows you to configure a RADIUS authentication server on a BSU/End Point A that remotely authenticates an SU or an End Point B while registering with a BSU or an End Point A respectively. These servers are also used to configure few features (VLAN and QoS) on an SU. Tsunami 800 & 8000 Series - Software Management Guide 128 A RADIUS server profile consists of a Primary and a Secondary RADIUS server that can act as Authentication servers. Configuration of Secondary Authentication Server is optional. The RADIUS server is applicable only when it is enabled in the WORP Configuration page (See Wireless Outdoor Router Protocol (WORP)). To configure the RADIUS Server profile, navigate to ADVANCED CONFIGURATION > Security > RADIUS. The following RADIUS Server Profile screen appears:
Advanced Configuration Figure 5-62 Configuring RADIUS Server Profile Given below is the table which explains RADIUS Server parameters and the method to configure the configurable parameter(s):
Parameter Description Profile Name A name that represents the Radius Server profile. By default, it is Default Radius. Max Retransmissions Represents the maximum number of times an authentication request may be retransmitted to the configured RADIUS server. The range is 0 to 3. By default, it is set to 3. Message Response Time Re Authentication Period Represents the response time (in seconds) for which that the BSU/End Point A should wait for the RADIUS server to respond to a request. The range is 3 to 9 seconds. By default, it is set to 3 seconds. Represents the time period after which the RADIUS server should re-authenticate an SU or an End Point B. The re-authenticate period ranges from 900 to 65535 seconds. By default, the re-authentication period is set to 0. Entry status A read-only parameter which displays the status of the RADIUS server profile as enabled. The Entry status cannot be disabled or edited. Server Type For better accessibility and reliability, you can configure two RADIUS servers:
1. Primary RADIUS Server 2. Secondary RADIUS Server The secondary RADIUS server serves as backup when the primary RADIUS server is down or not reachable. Tsunami 800 & 8000 Series - Software Management Guide 129 Advanced Configuration Parameter Description IP Address Represents the IPv4 / IPv6 address of the primary and secondary RADIUS servers.
: IPv6 address should be the global IP address and not the link local IP address. Server Port Shared Secret Specifies the port number that is used by the BSU/End Point A and the RADIUS server to communicate. By default, RADIUS Authentication Server communicates on port 1812. Specifies the password shared by the BSU/End Point A and the RADIUS server to communicate. The default password is public. Care should be taken to configure same Shared Secret on both BSU/End Point A and RADIUS Server, otherwise no communication is possible between BSU/End Point A and RADIUS server. Entry Status You can either enable or disable the configured RADIUS servers. By default, the Primary RADIUS server is enabled and the secondary RADIUS server is disabled. After configuring the required parameters, click OK and then COMMIT. Listed below are the points to be noted before configuring the Radius Server Profile, 1. Message Response Time should always be less than WORP Registration Timeout. 2. 3. The value of Max Retransmissions multiplied by Message Response Time should be less than WORP If Max Retransmissions is configured as Zero, then retransmissions do not occur. Registration Timeout value. 5.5.3 MAC ACL
:Applicable only to a BSU and End Point A device. The MAC ACL feature allows only the authenticated SUs/End Point Bs to access the wireless network. Please note that MAC Authentication is supported only on the wireless interface. The MAC ACL feature is applicable only when it is enabled in the WORP Configuration page (See Wireless Outdoor Router Protocol (WORP)). To configure the MAC Access Control List, navigate to ADVANCED CONFIGURATION > Security > MAC ACL. The MAC Access Control screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 130 Figure 5-63 MAC Access Control Configuration Select the Operation Type as either Allow or Deny. Allow: Allows only the SUs/End Point Bs configured in the MAC Access Control Table to access the wireless network. Deny: Does not allow the SUs/End Point B devices configured in the MAC Access Control Table to access the wireless Advanced Configuration network. Click OK, if you have changed the Operation Type parameters. 5.5.3.1 Add SUs/End Point B to MAC Access Control Table To add entries to MAC Access Control table, click Add in the MAC Access Control screen. The MAC ACL Add Row screen appears:
Figure 5-64 MAC ACL Add Row 1. Type the MAC Address of the SU/End Point B. 2. Add comments, if any. 3. Select the Entry Status as either Enable or Disable. 4. Next, click Add.
:
The maximum number of SUs/End Point Bs that can be added to the MAC ACL table is 250. Either RADIUS MAC or Local MAC can be enabled at one time. 5.5.3.2 Edit the existing SUs/End Point B from MAC Access Control Table To edit the existing SUs/End Point B from MAC Access Control Table, edit parameters from the MAC Access Control Table in MAC Access Control screen and click OK. 5.6 Quality of Service (QoS) The Quality of Service (QoS) feature is based on the 802.16 standard and defines the classes, service flows, and packet identification rules for specific types of traffic. QoS guarantees a reliable and adequate transmission quality for all types of traffic under conditions of high congestion and bandwidth over-subscription. There are already several pre-defined QoS classes, SFCs and PIRs available that you may choose from which cover the most common types of traffic. If you want to configure something else, you start building the hierarchy of a QoS classes by adding or using existing PIRs and SFCs; you define the QoS class by associating those PIRs to relevant SFCs with priorities to each PIR within each SFC. QoS can be applied on standard 802.3 frames and to Ethernet frames as well as to PPPoE encapsulated frames. Tsunami 800 & 8000 Series - Software Management Guide 131 5.6.1 QoS Concepts and Definitions QoS feature is applicable on both BSU/End Point A and SU/End Point B, but is configurable only on BSU/End Point A. When configured on BSU/End Point A, the QoS parameters is populated to all the registered SUs/End Point Bs and allows them to use the QoS configuration, as soon as they are connected to the BSU/ End Point A. You can create, edit, and delete classes of service that are specified below in the following hierarchy of parameters:
Advanced Configuration Packet Identification Rule (PIR) up to 64 rules, including 18 predefined rules Service Flow class (SFC) up to 32 SFCs, including 8 predefined SFCs; up to 8 out of maximum 64 PIRs may be associated per SFC Class List - Priority for each rule within each QoS class 0 to 255, with 0 being lowest priority QoS class up to 8 QoS classes, including 5 predefined classes; up to 8 out of maximum 32 SFCs may be associated per QoS class 5.6.1.1 Packet Identification Rule (PIR) A Packet Identification Rule is a combination of parameters that specifies what type of traffic is allowed or not allowed. You can create a maximum of 64 different PIRs, including 18 predefined PIRs. Also, you can create, edit, and delete PIRs that contain none, one, or more of the following classification fields:
Rule Name IP ToS (Layer 3 QoS identification) 802.1p tag (layer 2 QoS identification) IP Protocol List containing up to 4 IP protocols VLAN ID PPPoE Encapsulation Ether Type (Ethernet Protocol identification) Up to 4 TCP/UDP Source port ranges Up to 4 TCP/UDP Destination port ranges Up to 4 pairs of Source IP address + Mask Up to 4 pairs of Destination IP address + Mask Up to 4 source MAC addresses + Mask Up to 4 destination MAC addresses + Mask
: IP Address, TCP/UDP Port, MAC Address need to be configured separately and associate those classification in PIR details if required. A good example is provided by the 18 predefined PIRs. Note that these rules help identify specific traffic types:
1. All No classification fields, all traffic matches 2. L2 Multicast a. Ethernet Destination (dest = 0x010000000000, mask = 0x010000000000) 3. L2 Broadcast a. Ethernet Destination (dest = 0xffffffffffff, mask = 0xffffffffffff) 4. Cisco VoIP UL a. TCP/UDP Source Port Range (16,000-33,000) b. IP Protocol List (17 = UDP) 5. Vonage VoIP UL Tsunami 800 & 8000 Series - Software Management Guide 132 Advanced Configuration a. TCP/UDP Source Port Range (5060-5061, 10000-20000) b. IP Protocol List (17 = UDP) 6. Cisco VoIP DL a. TCP/UDP Destination Port Range (16,000-33,000) b. IP Protocol List (17 = UDP) 7. Vonage VoIP DL a. TCP/UDP Destination Port Range (5060-5061, 10000-20000) b. IP Protocol List (17 = UDP) 8. TCP a. IP Protocol List (6) 9. UDP a. IP Protocol List (17) 10. PPPoE Control a. Ether Type Rule (Ether Type = DIX-Snap, Ether Value = 0x8863) 11. PPPoE Data a. Ether Type Rule (Ether Type = DIX-Snap, Ether Value = 0x8864) 12. IP a. Ether Type Rule (Ether Type = DIX-Snap, Ether Value = 0x0800) 13. ARP a. Ether Type Rule (Ether Type = DIX-Snap, Ether Value = 0x0806) 14. Expedited Forwarding a. IP TOS/DSCP (ToS low=46(0x2E), ToS high=46(0x2E), ToS mask = 63(0x3F)) 15. Streaming Video (IP/TV) a. IP TOS/DSCP (ToS low=13(0x0D), ToS high=13(0x0D), ToS mask = 63(0x3F)) 16. 802.1p BE a. Ethernet Priority (low=0, high=0) (this is the equivalent of the User Priority value in the TCI (Tag Control Information) field of a VLAN tag) 17. 802.1p Voice a. Ethernet Priority (ToS low=6, ToS high=6) (this is the equivalent of the User Priority value in the TCI (Tag Control Information) field of a VLAN tag) 18. 802.1p Video a. Ethernet Priority (ToS low=5, ToS high=5) (this is the equivalent of the User Priority value in the TCI (Tag Control Information) field of a VLAN tag)
: Two different VoIP rule names have been defined for each direction of traffic, Uplink (UL) and Downlink (DL), (index numbers 4 to 7). This has been done to distinguish the proprietary nature of the Cisco VoIP implementation as opposed to the more standard Session Initiation Protocol (SIP) signaling found, for example, in the Vonage-type VoIP service. 5.6.1.2 Service Flow Class (SFC) A Service Flow class defines a set of parameters that determines how a stream of application data that matches a certain classification profile will be handled. You can create up to 32 different SFCs, including 8 predefined SFCs. Also, you can create, edit, and delete SFCs where, each SFC contains the following parameters and values:
Service flow name Tsunami 800 & 8000 Series - Software Management Guide 133 Advanced Configuration Scheduling type Best Effort (BE); Real-Time Polling Service (RTPS) Best Effort Services: Best Effort Services are typically provided by the Internet today for Web surfing. In the Tsunami 800 and 8000 devices, Best Effort parameters include Maximum Information Rate, Committed Information Rate, Latency, Jitter and traffic priority. Real-Time Polling Services (RTPS): RTPS is designed to support real-time services that generate fixed or variable size data packets on a periodic basis. Variable traffic can include MPEG video or VoIP with silence suppression. In the Tsunami 800 and 8000 devices, RTPS QoS parameters include Maximum Information Rate, Committed Information Rate, Latency, Jitter and traffic priority. Time sensitive and real-time traffic should use RTPS (Including VoIP, Multicast Video and Serial Data). All other traffic
(Variable Data, Unicast traffic, Internet) should be scheduled and prioritized using the Best Effort Service Flows. For QoS to function properly, ensure Interference is mitigated, keeping PHY and CRC errors at a minimum (<10/sec/avg). Retransmission at the PHY layer can cause latency, jitter overhead, packet loss and lower than expected throughput. Service Flow Direction Downlink (DL: traffic from BSU/End Point A to SU/End Point B); Uplink (UL: traffic from SU/End Point B to BSU/End Point A) Maximum sustained data rate (or Maximum Information Rate (MIR) specified in units of 1 Kbps from 8 Kbps up to the maximum rate specified in the license. Minimum reserved traffic rate (or Committed Information Rate (CIR) specified in units of 1 Kbps from 0 Kbps up to the currently specified Maximum Information Rate (MIR) Maximum Latency specified in increments of 1 ms steps from a minimum of 5 ms up to a maximum of 100 ms Maximum number of data messages in a burst one (1) to sixteen (16), which affects the percentage of the maximum Tolerable Jitter specified in increments of 1 ms steps from a minimum of 0 ms up to the Maximum Latency (in ms) Traffic priority zero (0) to seven (7), 0 being the lowest, 7 being the highest throughput of the system Entry Status Enable, Disable, and Delete The Traffic Priority with Scheduling Type and Committed Information Rate (CIR), defines the absolute Traffic Priority for a specific Service Flow as given below:
Committed Information Rate Scheduling Type Traffic Priority Absolute Priority
(CIR) 0 0 0 0 0 0 0 0 0 0 0 0 BE BE BE BE BE BE BE BE RtPS RtPS RtPS RtPS 0 1 2 3 4 5 6 7 0 1 2 3 0 1 2 3 4 5 6 7 8 9 10 11 Tsunami 800 & 8000 Series - Software Management Guide 134 Committed Information Rate Scheduling Type Traffic Priority Absolute Priority Advanced Configuration
(CIR) 0 0 0 0
> 0 (<= MIR)
> 0 (<= MIR)
> 0 (<= MIR)
> 0 (<= MIR)
> 0 (<= MIR)
> 0 (<= MIR)
> 0 (<= MIR)
> 0 (<= MIR)
> 0 (<= MIR)
> 0 (<= MIR)
> 0 (<= MIR)
> 0 (<= MIR)
> 0 (<= MIR)
> 0 (<= MIR)
> 0 (<= MIR)
> 0 (<= MIR) RtPS RtPS RtPS RtPS BE BE BE BE BE BE BE BE RtPS RtPS RtPS RtPS RtPS RtPS RtPS RtPS 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Obviously, there are 32 different absolute traffic priorities, priority 0 being the lowest and priority 31 being the highest. It is important to note that for each SFC with CIR > 0, there are effectively two absolute traffic priorities alloted (total 16 priorities for the 8 SFC entries). The higher priority is used as long as the throughput of the traffic being sent through SFC is below or equal to the CIR, and the lower priority is used for the rest of the traffic, taking MIR configuration as the second priority. This switching of the priorities is done automatically by the scheduler, which makes sure that lower priority traffic gets transported only after all the higher priorities are transported successfully. The device tries to deliver the packets within the specified latency and jitter requirements, relative to the moment of receiving the packets in the device. For all types of traffic, the device will try to keep the jitter within the range 0 to configured Jitter value in milliseconds(ms). In order to allow the device maintain the traffic within the configured jitter range, each packet is buffered until a time interval equal to the difference between Latency and jitter (Latency Jitter) has elapsed. When this interval elapses, the receiving device will deliver the packet. The delay of the packets is kept in the range (Latency Jitter) to configured Latency value in millisecond(ms), that in turn maintains the jitter within the range 0 to configured Jitter value in milliseconds(ms). However, possible retransmissions can increase maximum delay of the packet beyond Latency milliseconds, which can result in increased jitter as well. If the SFCs scheduling type is real-time polling (RtPS) and the packet is not delivered out from the Tsunami 800 & 8000 Series - Software Management Guide 135 transmitting unit within the time period equal to the Latency milliseconds, then the packet will be discarded on transmitting device. This can lead to loss of packets without reaching the maximum throughput of the wireless link. For example, when the packets arrive in bursts on the Ethernet interface and the wireless interface is momentarily maxed out, then the packets at the end of the burst may be timed out before they can be sent. Therefore RtPS type of polling must be used only if it is absolutely necessary. Users can set up their own traffic characteristics (MIR, CIR, latency, jitter, etc.) per service flow class to meet their unique requirements. A good example is provided by the 8 predefined SFCs:
Advanced Configuration 1. UL-Unlimited BE a. Scheduling Type = Best Effort b. Service Flow Direction = Uplink c. Entry Status = Enable d. Maximum Sustained Data Rate = 102400 Mbps e. Traffic Priority = 0 2. DL-Unlimited BE (same as UL-Unlimited BE, except Service Flow Direction = Downlink) 3. DL-L2 Broadcast BE (same as UL-Unlimited BE, except Service Flow Direction = Downlink) 4. UL-G711 20 ms VoIP RTPS a. Schedule type = RTPS (Real time Polling Service) b. Service Flow Direction = Uplink c. Entry Status = Enable d. Maximum Sustained Data Rate = 88 Kbps e. Minimum Reserved Traffic Rate = 88 Kbps f. Maximum Latency = 20 milliseconds g. Traffic Priority = 1 5. DL-G711 20 ms VoIP rtPS (same as UL-G711 20ms VoIP rtPS, except Service Flow Direction = Downlink) 6. UL-G729 20 ms VoIP rtPS (same as UL-G711 20ms VoIP rtPS, except Maximum Sustained Data Rate and Committed Information rate = 66 Kbps) 7. DL-G729 20 ms VoIP rtPS (same as UL-G729 20ms VoIP rtPS, except Service Flow Direction = Downlink) 8. DL-2Mbps Video Initialization State = Active a. Schedule type = Real time Polling b. Service Flow Direction = Downlink c. d. Maximum Sustained Data Rate = 2 Mbps e. Minimum Reserved Traffic Rate = 2 Mbps f. Maximum Latency = 20 milliseconds g. Traffic Priority = 1 Note that two different VoIP Service Flow classes for each direction of traffic have been defined (index numbers 4 to 7) which follow the ITU-T standard nomenclatures: G.711 refers to a type of audio companding and encoding that produces a 64 Kbps bitstream, suitable for all types of audio signals. G.729 is appropriate for voice and VoIP applications, but cannot transport music or fax tones reliably. This type of companding and encoding produces a bitstream between 6.4 and 11.8 Kbps (typically 8 Kbps) according to the quality of voice transport that is desired. 5.6.1.3 QoS Class A QoS class is defined by a set of parameters that includes the PIRs and SFCs that were previously configured. You can create up to eight different QoS classes, including five predefined QoS classes. Up to eight SF classes can be associated to each QoS Tsunami 800 & 8000 Series - Software Management Guide 136 Advanced Configuration class, and up to eight PIRs can be associated to each SF class. For example, a QoS class called G711 VoIP may include the following SFCs: UL-G711 20 ms VoIP rtPS and DL-G711 20 ms VoIP rtPS. In turn, the SFC named UL-G711 20 ms VoIP rtPS may include the following rules: Cisco VoIP UL and Vonage VoIP UL. You can create, edit, and delete QoS classes that contain the following parameters:
QoS class name Service Flow (SF) class name list per QoS class (up to eight SF classes can be associated to each QoS class) Packet Identification Rule (PIR) list per SF class (up to eight PIRs can be associated to each SF class) Priority per rule which defines the order of execution of PIRs during packet identification process. The PIR priority is a number in the range 0-255, with priority 255 being executed first, and priority 0 being executed last. The PIR priority is defined within a QoS class and can be different for the same PIR in some other QoS class. If all PIRs within one QoS class have the same priority, the order of execution of PIR rules will be defined by the order of definition of SFCs, and by the order of definition of PIRs in each SFC, within that QoS class. A good example of this hierarchy is provided by the five predefined QoS classes:
1. Unlimited Best Effort a. SF class: UL-Unlimited BE PIR: All; PIR Priority: 0 b. SF class: DL-Unlimited BE PIR: All; PIR Priority: 0 2. L2 Broadcast Best Effort a. SF class: DL-L2 Broadcast BE PIR: L2 Broadcast; PIR Priority: 0 3. G711 VoIP a. SF class: UL-G711 20 ms VoIP rtPS PIR: Vonage VoIP UL; PIR Priority: 1 PIR: Cisco VoIP UL; PIR Priority: 1 b. SF class: DL-G711 20 ms VoIP rtPS PIR: Vonage VoIP DL; PIR Priority: 1 PIR: Cisco VoIP DL; PIR Priority: 1 4. G729 VoIP a. SF class: UL-G729 20 ms VoIP rtPS PIR: Vonage VoIP UL; PIR Priority: 1 PIR: Cisco VoIP UL; PIR Priority: 1 b. SF class: DL-G729 20 ms VoIP rtPS PIR: Vonage VoIP DL; PIR Priority: 1 PIR: Cisco VoIP DL; PIR Priority: 1 5. 2Mbps Video a. SF class: DL-2Mbps Video PIR: Streaming Video (IP/TV); PIR Priority: 1 5.6.2 QoS Configuration There are several pre-defined QoS classes, SFCs, and PIRs available that cover the most common types of traffic. To add new QoS classes, SFC and PIR, build the hierarchy of a QoS class as follows:
1. If new MAC Address, IP Address, and/or TCP/UDP Port are necessary, define the PIR MAC Address, IP Address and/or TCP/UDP Port Entries. Tsunami 800 & 8000 Series - Software Management Guide 137 Advanced Configuration 2. Define PIRs and specify packet classification rules, associate MAC Address/IP Address/TCP-UDP Port Entries if required. 3. Define SFCs 4. Define QoS Class by associating PIRs with relevant SFC. 5. Assign priorities to each PIR within each SFC. For detailed instructions on configuring a management station (a single station used for managing an entire network), refer to QoS Configuration for a Management Station. 5.6.2.0.1 QoS PIR MAC Address Configuration 1. Navigate to ADVANCED CONFIGURATION > QoS > PIR List > MAC Address Entries, the QoS PIR MAC Address Entries screen appears:
2. Three predefined MAC Address entries are displayed in this page. You can configure a maximum of 256 entries. MAC Address and Mask combination should be unique. This MAC Address entry can be referred in the PIR Rules Source or Destination MAC Address Classification. MAC Entry referred by any PIR rule cannot be deleted. Figure 5-65 QoS PIR MAC Address Entries 3. Click OK. To Add a New PIR MAC Address Entry, a. Navigate to ADVANCED CONFIGURATION > QoS > PIR List > MAC Address Entries, the QoS PIR MAC Address Entries screen appears. b. Click Add on the QoS PIR MAC Address Entries screen to add a new entry. The following screen appears for configuring the MAC Entry Details. Figure 5-66 QoS PIR MAC Address Add Entry c. Provide the MAC Address, Mask, Comment, Entry Status details and click Add. Comment field can be used to identify when this particular entry is referred in PIR Rule/QoS Class. Tsunami 800 & 8000 Series - Software Management Guide 138 Advanced Configuration The bit that is enabled in the MAC Mask configuration, the corresponding bits value in the MAC Address configuration should match with the same bit of the incoming traffics MAC Address (other bits of the incoming traffic are ignored). Then it is considered as matching traffic and the rest are unmatched traffic. The following is explained with the help of an example:
1. Creating Matching profile for single MAC address To apply QoS classification for traffic which is originated / destined from / to a Device only. MAC Address: 00:20:A6:00:00:01 MAC Mask: FF:FF:FF:FF:FF:FF In this example, all bits in the MAC Mask are enabled, so incoming traffics MAC address should exactly match with specified configured MAC Address (that is, 00:20:A6:00:00:01). Other traffics are considered as non-matching traffic. 2. Creating Matching profile for all MAC Address MAC Address: 00:00:00:00:00:00 MAC Mask: 00:00:00:00:00:00 In this example, all bits in the MAC Mask are disabled, so any traffic is considered as matching traffic. 3. Creating Matching Profile for Broadcast MAC Address MAC Address: FF:FF:FF:FF:FF:FF MAC Mask: FF:FF:FF:FF:FF:FF 4. Creating Matching Profile for all Multicast MAC Address MAC Address: 01:00:00:00:00:00 MAC Mask: 01:00:00:00:00:00 5. Creating Matching Profile for range of MAC Address (00:20:A6:00:00:01 to 00:20:A6:00:00:FF) MAC Address: 00:20:A6:00:00:00 MAC Mask: FF:FF:FF:FF:FF:00 5.6.2.0.2 QoS PIR IP Address Configuration 1. Navigate to ADVANCED CONFIGURATION > QoS > PIR List > IP Address Entries, the QoS PIR IP Address Entries screen appears. A single predefined IP Address entry is displayed. You can configure a maximum of 256 entries. IP Address, Subnet Mask combination should be unique. This IP Address entry can be referred in the PIR Rules Source or Destination IP Address Classification. IP Address Entry referred by any PIR rule cannot be deleted. 2. Click OK. To Add a New PIR IP Address Entry, Figure 5-67 QoS PIR IP Address Entries a. Navigate to ADVANCED CONFIGURATION > QoS > PIR List > IP Address Entries. The QoS PIR IP Address Entries screen appears b. Click Add on the QoS PIR IP Address Entries screen to add a new entry. The following screen appears for configuring the IP Address Entry Details. Tsunami 800 & 8000 Series - Software Management Guide 139 Advanced Configuration Figure 5-68 QoS PIR IP Address Add Entry c. Provide the IP Address, Subnet Mask, Comment, Entry Status details and click Add. Comment field can be used by the user to identify when this particular entry is referred in PIR Rule or QoS Class. 5.6.2.0.3 QoS PIR TCP/UDP Port Configuration 1. Navigate to ADVANCED CONFIGURATION > QoS > PIR List > TCP/UDP Port Entries. The QoS PIR TCP/UDP Port Entries screen appears. Three predefined TCP/UDP Port Entries are displayed. You can configure a maximum of 256 entries. Start Port, End Port combination should be unique. This TCP/UDP Port entry can be referred in the PIR Rules Source or Destination TCP/UDP Port Classification. TCP/UDP Port Entry referred by any PIR rule can not be deleted. 2. Click OK. To Add a New PIR TCP/UDP Port Entry, Figure 5-69 QoS PIR TCP/UDP Port Entries a. Navigate to ADVANCED CONFIGURATION > QoS > PIR List > TCP/UDP Port Entries. The QoS PIR TCP/UDP Port Entries screen appears. b. Click Add on the QoS PIR TCP/UDP Port Entries screen to add a new entry. The following screen appears for configuring the IP Address entry details. Tsunami 800 & 8000 Series - Software Management Guide 140 Advanced Configuration Figure 5-70 QoS PIR TCP/UDP Port Add Entry c. Provide the Start Port, End Port, Entry Status details and click Add. Comment field can be used to identify when this particular entry is referred in PIR Rule or QoS Class. 5.6.2.1 QoS PIR Configuration 1. Navigate to ADVANCED CONFIGURATION > QoS > PIR List. The QoS PIR Entries screen appears. 18 predefined PIR Rules are displayed in this page. You can configure a maximum of 64 entries. PIR Rule Name should be unique. This PIR Rule can be referred in the QoS Class Service Flow Details. PIR rule referred by any QoS Class cannot be deleted. 2. Click OK. Tsunami 800 & 8000 Series - Software Management Guide 141 Figure 5-71 QoS PIR Entries To Add a New PIR Rule, a. Navigate to ADVANCED CONFIGURATION > QoS > PIR List. The QoS PIR Entries screen appears. b. Click Add on the QoS PIR Entries screen to add a new entry. The following screen appears for configuring the New PIR Entry. Advanced Configuration Figure 5-72 QoS PIR Add Entry c. Provide the PIR Name, Entry Status details and click Add. 5.6.2.1.1 PIR Rule Clarification Details 1. Navigate to ADVANCED CONFIGURATION > QoS > PIR List and click Details for editing a particular PIR Rule. Tsunami 800 & 8000 Series - Software Management Guide 142 Figure 5-73 QoS PIR Edit Entry Parameter Rule Name ToS Rule Description This parameter specifies the Name of the Packet Identification Rule (PIR) and can have a length of 1-32 characters. This parameter is used to enable or disable a TOS rule. When ToS rule is enabled, configure the values for the following to specify the ToS-related configuration:
Advanced Configuration ToS Low ToS High ToS Mask In ToS Configuration, enter the decimal value of entire ToS 1 byte in ToS Low and ToS High parameters of the PIR rule. Figure 5-74 IP Header Format ToS Low and ToS High values can be derived from DSCP (6 bits) and ECN (2 bits) values. ToS Value (8 bits) = DSCP Value (most significant 6 bits) + ECN Value (least significant 2 bits) Consider the following while configuring PIR TOS parameters:
1. To prioritize traffic based on specific DSCP value, configure the ToS Low and ToS High to the value derived from that DSCP (as mentioned in the example below) For Example: To configure ToS Low and Tos High values, when the DSCP packet value is 10:
- DSCP (6 bit) = 10 (Binary value = 001010)
- ECN (2 bit) = 0 (Binary value = 00)
- ToS (Low and High) (8 bit) = DSCP(001010) + ECN(00) = 40 Configure:
- ToS Low = 40
- ToS High = 40 2. To prioritize the traffic based on range of DSCP value, configure ToS low and ToS High to a range. For Example: To configure ToS Low and ToS High values, when the DSCP packet is in range of 10 to 20, configure:
- ToS Low = 40 (DSCP = 10 (Binary 001010) + ECN = 0 (Binary 00))
- ToS High = 80 (DSCP = 20 (Binary 010100) + ECN = 0 (Binary 00)) Tsunami 800 & 8000 Series - Software Management Guide 143 Parameter Description Advanced Configuration 3. To prioritize DSCP packets based on IP-Precedence/DSCP value/ToS value, configure ToS Mask. a. IP Precedence: To prioritize based on only IP precedence, set all the 3 IP Precedence bits in the ToS Mask parameter to 1 and set rest of the bits in the ToS Mask parameter to 0 (i.e decimal value = 224). b. DSCP Value: To prioritize based on DSCP value, set all the DSCP bits in the ToS Mask parameter to 1 and set rest of the bits in the ToS Mask parameter to 0 (i.e decimal value = 252). c. ToS Value: To prioritize based on entire ToS value then set all the bits in the ToS Mask parameter to 1 (i.e decimal value = 255). Ether Priority Rule This parameters is used to enable or disable 802.1p priority rule. Enter the values for the following to specify 802.1p priority configuration:
Priority Low Priority High VLAN Rule This parameters allows to enable or disable VLAN rule. Enter the VLAN ID when the VLAN rule is enabled. PPPoE Encapsulation This parameter is used to classify PPPoE traffic. If you Enable/disable the PPPoE Configuration, it will automatically disable the Ether Type Rule. User can configure it again by enabling Ether Type Rule. When PPPoE Encapsulation is enabled, incoming packet will be checked against Ether value 0x8864 and look for PPPoE Protocol Id value 0x0021(IP Protocol) by default. User can modify the PPPoE Protocol Id but all the other classification rules which are specified in the PIR rule will work only if the PPPoE Protocol Id is 0021. Ether Value is not valid when PPPoE Encapsulation is enabled. Ether Type Rule This parameters is used to enable or disable Ether Type rule. Enter the values for the following to specify the Ether Type rule related configuration:
:
Ether Type PPPoE Protocol Id Ether Value PPPoE Protocol Id is not valid if PPPoE Encapsulation is disabled. Ether Value is not valid if PPPoE Encapsulation is enabled. 5.6.2.1.2 Adding Protocol ID a. Navigate to ADVANCED CONFIGURATION > QoS > PIR List. Click Details. The QoS PIR Edit Entry screen appears. b. Navigate to Protocol Id Entries tab and then click Add to add a new Protocol entry. The following screen appears. Tsunami 800 & 8000 Series - Software Management Guide 144 Advanced Configuration c. Enter the details and click Add. For deleting an entry, click Delete for the corresponding entry in PIR Details Figure 5-75 QoS PIR Protocol ID screen. 5.6.2.1.3 Adding TCP/UDP Source Port Add Entry a. Navigate to ADVANCED CONFIGURATION > QoS > PIR List. Click Details. The QoS PIR Edit Entry screen appears. b. Navigate to TCP/UDP Source Port Entries tab and then click Add to add a new entry. The following screen appears. Figure 5-76 QoS PIR TCP/UDP Source Port Add Entry c. All the Entries present in the PIR TCP/UDP Port Entries are displayed in the TCP/UDP Port Entry Table. Select the appropriate radio button and click Add. When an entry is added for the specific PIR, the entry gets displayed in the existing TCP/UDP Port Entries table. For deleting an entry, click Delete for the corresponding entry in the PIR Details page. 5.6.2.1.4 Adding TCP/UDP Destination Port Add Entry a. Navigate to ADVANCED CONFIGURATION > QoS > PIR List. Click Details. The QoS PIR Edit Entry screen appears. b. Navigate to TCP/UDP Destination Port Entries tab and then click Add to add a new entry. The following screen appears. Tsunami 800 & 8000 Series - Software Management Guide 145 Advanced Configuration Figure 5-77 QoS PIR TCP/UDP Destination Port Add Entry c. All the entries present in the PIR TCP/UDP Port Entries are displayed in the TCP/UDP Port Entry Table. Select the appropriate radio button and click Add. When an entry is added for a specific PIR, it gets displayed in the existing TCP/UDP Port Entries table. For deleting an entry, click Delete for the corresponding entry in the PIR Details page. 5.6.2.1.5 Adding IP Addresses 5.6.2.1.5.1 Adding Source IP Address a. Navigate to ADVANCED CONFIGURATION > QoS > PIR List. Click Details. The QoS PIR Edit Entry screen appears. b. Navigate to Source IP Address Entries tab and then click Add to add a new entry. The following screen appears:
Figure 5-78 QoS PIR Source IP Address Add Entry c. All the entries present in the PIR IP Address Entries are displayed in the IP Address Entry Table. Select the appropriate radio button and click Add. After adding the entry for this specific PIR, it is displayed in the Existing IP Address Entries table. For deleting an entry, click Delete for the corresponding entry in the PIR Details page. Tsunami 800 & 8000 Series - Software Management Guide 146 5.6.2.1.5.2 Adding Destination IP Address a. Navigate to ADVANCED CONFIGURATION > QoS > PIR List. Click Details. The QoS PIR Edit Entry screen appears. b. Navigate to Destination IP Address Entries tab and then click Add to add a new entry. The following screen appears. Advanced Configuration Figure 5-79 QoS PIR Destination IP Address Add Entry c. All the entries present in the PIR IP Address Entries are displayed in the IP Address Entry Table. Select the appropriate radio button and click Add. After adding the entry for this specific PIR, it is displayed in the Existing IP Address Entries table. For deleting an entry, click Delete for the corresponding entry in the PIR Details page. The following is explained with the help of an example:
1. Creating Matching profile for single IP address To apply QoS classification for traffic which is originated / destined from / to a Device only. IP Address: 169.254.28.133 IP Mask: 255.255.255.255 In this example, all bits in the IP Mask are enabled, so incoming traffics IP address should exactly match with specified configured IP Address (i.e, 169.254.28.133). Other traffic is considered as non-matching traffic. 2. Creating Matching profile for all IP Address IP Address: 0.0.0.0 IP Mask: 0.0.0.0 In this example, all bits in the IP Mask are disabled, so any traffic is considered as matching traffic. 3. Creating Matching Profile for range of IP Address (169.254.128.0 to 169.254.128.255) IP Address: 169.254.128.0 IP Mask: 255.255.255.0 4. Creating Matching Profile for Broadcast IP Address IP Address: 255.255.255.255 IP Mask: 255.255.255.255 5. Creating Matching Profile for Single Multicast IP Address IP Address: 224.0.0.9 IP Mask: 255.255.255.255 Tsunami 800 & 8000 Series - Software Management Guide 147 In this example, all bits in the IP Mask are enabled, so incoming traffics multicast IP address should exactly match with specified configured multicast IP Address (i.e, 224.0.0.9). Other traffic is considered as non-matching traffic. 6. Creating Matching Profile for range of Multicast IP Address (224.0.0.0 to 224.0.0.255) Advanced Configuration IP Address: 224.0.0.9 IP Mask: 255.255.255.255 5.6.2.1.6 Adding Source MAC Address a. Click Add to add a new entry. The following screen appears. Figure 5-80 QoS PIR Source MAC address Add Entry b. All the entries present in the PIR MAC Address Entries are displayed in the MAC Address Entry Table. Select the appropriate radio button and click Add. After adding the entry for this specific PIR, it is displayed in the Existing MAC Address Entries table. For deleting an entry, click Delete for the corresponding entry in the PIR Details page. 5.6.2.1.7 Adding Destination MAC Address a. Click Add to add a new entry. The following screen appears. Figure 5-81 QoS PIR Destination MAC address Add Entry Tsunami 800 & 8000 Series - Software Management Guide 148 b. All the entries present in the PIR MAC Address Entries are displayed in the MAC Address Entry Table. Select the appropriate radio button and click Add. After adding the entry for this specific PIR, it is displayed in the Existing MAC Address Entries table. For deleting an entry, click Delete for the corresponding entry in the PIR Details page. Advanced Configuration 5.6.2.2 QoS Service Flow Configuration (SFC) 1. Click ADVANCED CONFIGURATION > QoS > SFC List. Ten predefined SFCs are displayed in this page. This table allows the user to configure maximum of 32 entries. Service Flow Name should be unique. This SFC can be referred in the QoS Class Details. SFC referred by any QoS Class cannot be deleted. Adding a New Service Flow (SFC) Click Add to add new entry. The following screen appears for configuring the new SU SFC Entry. Figure 5-82 QoS Service Flow Entries Tsunami 800 & 8000 Series - Software Management Guide 149 Advanced Configuration Figure 5-83 QoS Service Flow Add Entry 2. Specify details for the Service Flow Name, Scheduler Type, Traffic Direction, MIR, CIR, Max Latency, Tolerable Jitter, Traffic Priority, Max Messages in Burst and Entry Status. 3. Click Add. Parameter Description Service Flow Name Specifies the Name of the Service Flow. It can be of length 1-32 characters. Scheduler Type Traffic Direction MIR (Maximum Information Rate) CIR (Committed Information Rate) Specifies the Scheduler methods to be used. Scheduler type supports BE (Best Effort), RTPS
(Real-Time Polling Service). Specifies the Direction (Downlink or Uplink) of the traffic in which the configuration has to be matched. Specifies the maximum bandwidth allowed for this Service Flow. This value ranges from 8 Kbps to maximum value specified in the license file. Specifies the reserved bandwidth allowed for this Service Flow. This value ranges from 0 to maximum value specified in the license file. Max Latency Specifies the Latency value. This value ranges from 5 to 100 ms. Tolerable Jitter Specifies the Jitter value. This value ranges from 0 to 100 ms. Traffic Priority Specifies the priority of the Service flow when multiple Service flows are assigned to single QoS Class. This value ranges from 0 to 7. Tsunami 800 & 8000 Series - Software Management Guide 150 Advanced Configuration Parameter Description Max Messages in Burst Specifies the maximum number of messages that can be sent in a burst. This value ranges from 1 to 16.
: Reducing the number of messages impacts the throughput. Maximum Demand Enable- Specifies the demand(equal to Committed Information Rate CIR Mbps) is configured or set for a particular SFC, regardless of whether or not the demand exists. Disable- Specifies the demand is not configured for a particular SFC.
: Enabling the Maximum demand affects the latency & performance of the system. Entry Status Specifies the Service Flow status. 5.6.2.3 QoS Class Configuration 1. Click ADVANCED CONFIGURATION > QoS > Class List. Five predefined QoS Classes are displayed in this page. You can configure maximum 8 entries. QoS Class Name should be unique. This QoS Class can be referred in the Default QoS Class or L2 Broadcast QoS Class. Any QoS Class referred cannot be deleted. 2. Click OK. Figure 5-84 QoS Class List Tsunami 800 & 8000 Series - Software Management Guide 151 Advanced Configuration Parameter Default QoS Class L2 Broadcast QoS Class Description This parameter specifies the QoS Class profile that needs to be associated with an SU or End Point B which is not listed in the QoS SU or End Point B List but connected. This parameter specifies WORP to use this particular class for WORP broadcast facility. L2 Broadcast QoS Class is valid only for Downlink Direction. QoS Class assigned to this profile should have at least one Downlink SFC. 4. Add a New QoS Class:
a. Click Add to add new entry. The following screen appears for configuring the New Class Entry. b. Specify the QoS Class Name, Service Flow Name PIR Rule Name Priority and Entry Status and click Add. Figure 5-85 QoS Class Add Entry Parameter Description Class Name Specifies the Name of the QoS Class. This name length can range from 1 to 32 characters. Service Flow Name Specifies the Service Flow to be associated with the QoS Class. Select one of the possible SFCs that have been previously configured in the SFC List. PIR Rule Name Priority Specifies the PIR Rule need to be associated with this Service Flow. Select one of the possible PIRs that have been previously configured in the PIR List. Specifies priority or order of execution of PIRs during packet identification process. The PIR priority is a number that can range from 0-255, with priority 255 being executed first, and priority 0 being executed last. The PIR priority is defined within a QoS class, and can be different for the same PIR in some other QoS class. If all PIRs within one QoS class have the same priority, the order of execution of PIR rules will be defined by the order of definition of SFCs, and by the order of definition of PIRs in each SFC, within that QoS class. Entry Status Specifies the status of the QoS Class as enable/disable. 5.6.2.3.1 Adding Service Flows in QoS Class 1. Click on the corresponding Details of the QoS Class for adding more Service Flows. Each QoS Class can have maximum 8 Service Flows. At least there should be one service flow per QoS Class. The following screen is displayed to configure the new SFC entry inside the QoS Class. Tsunami 800 & 8000 Series - Software Management Guide 152 2. Click OK. Advanced Configuration 3. Click Add. The following screen appears for association of the new SFC in this QoS Class. Figure 5-86 QoS Class Service Flow Details Figure 5-87 QoS Class Service Flow Add Entry 4. Specify the Service Flow Name, PIR Rule Name, Priority and Entry Status and click Add to add a new entry. 5.6.2.3.2 Adding PIR in QoS Class 1. Click on the corresponding Details provided in the Service Flow of a particular QoS Class. Maximum 8 PIR rules can be associated per SFC of an QoS Class. At least there should be one PIR per SFC of an QoS Class. The following screen appears to associate the new PIR entry inside an SFC of an QoS Class. 2. Click OK. Tsunami 800 & 8000 Series - Software Management Guide 153 Advanced Configuration 3. Click Add. The following screen appears for association of the new PIR rule in an SFC already associated in an QoS Class. Figure 5-88 QoS Class PIR Details 4. Specify the PIR Rule Name, Priority and Entry Status and click Add to add a new entry. Figure 5-89 QoS Class PIR Add Entry
: When you change the entry status of an existing QoS Class, the status changes immediately. For example, when you change the entry status to delete, the corresponding QoS Class get deleted even before you click OK. 5.6.2.4 QoS SU or End Point B List Configuration 1. Navigate to ADVANCED CONFIGURATION > QoS > SU or End Point B List. By default, the table does not have any entry. User can configure the Wireless MAC Address of the SU or End Point B here and associate the QoS Class that is to be used for that particular SU or End Point B. Tsunami 800 & 8000 Series - Software Management Guide 154 Figure 5-90 QoS SU or End Point B List 2. If an SU or End Point B is not in the list and is associated, the default QoS class configuration is applied. 5.6.2.4.1 Adding a New SU or End Point B 1. Navigate to ADVANCED CONFIGURATION > QoS > SU or End Point B List. The QoS SU or End Point B Entries screen appears. 2. Click Add to add a new entry. The following QoS SU or End Point B Table Add Row screen appears. Advanced Configuration Figure 5-91 QoS SU or End Point B Table Add Entry 3. Specify the Wireless Mac Address of the SU or End Point B, Class Name, Comment and Entry Status and click Add. Previously defined Class Name can be viewed in the Class Name drop-down box.
:
QoS SU Entries configuration can be done locally or through a RADIUS Server. Local configuration takes priority over RADIUS Based QoS configuration. RADIUS Configuration is applicable only when the RADIUS MAC ACL Status is enabled on the BSU. When the link is down, the RADIUS configuration is lost. 5.6.3 QoS Configuration for a Management Station As stated previously, the QoS feature enables prioritization of traffic and allocation of the available bandwidth based on that prioritization. The system is designed in such a way that higher priority traffic preempts lower priority traffic, keeping lower priority traffic on hold until higher priority traffic finishes. This mechanism ensures that the available bandwidth is always given first to the higher priority traffic; if all the bandwidth is not consumed, the remaining bandwidth is given to the lower priority traffic. If QoS is not properly configured, the system becomes difficult to access in heavily loaded networks. One of the side effects of this misconfiguration is ping time-out, which is usually interpreted as a disconnection of the pinged node. However, with the correct QoS configuration, every node in the network can be reached at any point of time. The following configuration instructions explain how to configure the system so that configuration parameters can always be changed, and ping requests and responses get higher priority in order to show the actual connectivity of the pinged node. The configuration suggested here assumes that the whole network is managed from a single work station, called the management station. This station can be connected anywhere in the network, and can be recognized by either its IP address, or by its MAC Ethernet address if the network uses DHCP. In this configuration, any traffic coming from or going to the management station is treated as management traffic. Therefore, the management station should be used only for configuration of the BSU/End Point A or SU/End Point B nodes in the network and to check connectivity of the nodes, but it should not be used for any throughput measurements.
: While this QoS configuration is used, the TCP or UDP throughput should not be measured from the management station. Tsunami 800 & 8000 Series - Software Management Guide 155 Advanced Configuration 5.6.3.0.1 Step 1: Add Packet Identification Rules To recognize management traffic, the system needs to recognize ARP requests or responses and any traffic coming from or going to the management station. 5.6.3.0.2 A. Confirm the Attributes of the Existing ARP PIR The default QoS configuration contains the PIR called ARP, which recognizes ARP requests or responses by the protocol number 0x0806 in the Ethernet Type field of the Ethernet packet. Confirm that the ARP PIR parameters are correct, as follows:
1. Navigate to ADVANCED CONFIGURATION > QoS > PIR list. 2. Click Details corresponding to the ARP PIR. 3. Confirm the following attributes:
Rule Name: ARP Status: Enable Enable Ether Type Rule: Yes (checkbox is selected) Ether Type: DIX-Snap Ether Value: 08:06(hex) 5.6.3.0.3 B. Create New PIRs to Recognize Management Traffic To recognize the traffic coming from or going to the management station, the system must contain two additional PIRs: one with either the destination IP address or the destination MAC address equal to the management stations IP or MAC address, and another with either the source IP address or the source MAC address equal to the management stations IP or MAC address. The following examples explain PIR rules based on the IP Address of the Management Station. 1. Navigate to ADVANCED CONFIGURATION > QoS > PIR list > IP Address Entries. 2. Click Add. The screen for adding the Management Station's IP Address appears. Enter proper IP Address, Subnet mask as 255.255.255.255, Entry status as Enable and then click Add. This adds the Management Stations IP details in the IP Address Entries of the PIR List. 3. Navigate to ADVANCED CONFIGURATION > QoS > PIR list. 4. Add PIR Rule for Source IP Address. a. Click Add. The screen for adding the New PIR Rule appears. Enter the PIR Rule Name as Management Station SRC IP, Entry status as Enable and click Add. This adds the new PIR rule in the PIR List. By default, no classification rules are applied. b. Navigate to ADVANCED CONFIGURATION > QoS > PIR list. Click Details for Management Station SRC IP PIR rule. This displays all the classification rule details for this particular rule. c. Click Add that corresponds to Source IP Address Entries. This displays a screen for referring the Management Stations IP Address. New Entry Table displays all the IP Address Entries of the PIR List. Select the option button corresponding to the Management Station and then click Add. This adds the IP Address of the Management Station to the Existing Entries. Click Back and the new entry appears in the Source IP Address Entries Table. 5. Add PIR Rule for Destination IP Address. a. Click Add. This displays a screen for adding the New PIR Rule. Enter the PIR Rule Name as Management Station DST IP, Entry status as Enable and then click Add. This adds the new PIR rule in the PIR List. By default, no classification rules are applied. b. Navigate to ADVANCED CONFIGURATION > QoS > PIR list. Click Details corresponding to the Management Station DST IP PIR rule. This displays the classification rule details for this particular rule. Tsunami 800 & 8000 Series - Software Management Guide 156 c. Click Add corresponding to Destination IP Address Entries. This displays a screen for referring the Management Stations IP Address. New Entry Table displays all the Entries of the IP Address Entries of the PIR List. Select the option button corresponding to the Management Station and click Add. This adds the IP Address of the Management Station to the Existing Entries. Click Back and the new entry appears in the Destination IP Address Entries Table. 5.6.3.0.4 Step 2: Add Service Flow Classes To handle management traffic, the system needs two Service Flow Classes: one for uplink traffic and one for downlink traffic. Advanced Configuration 1. Configure the Downlink Service Flow. a. Navigate to ADVANCED CONFIGURATION > QoS > SFC list. b. Click Add. c. Enter the following parameters:
Service Flow Name: DL-Management Scheduler Type: RtPS Traffic Direction: Downlink MIR: 1000 CIR: 1000 Max Latency: 20 Tolerable Jitter: 10 Priority: 7 Max Messages in Burst: 16 Entry Status: Enable d. Click Add. The DL-Management Service Flow is added to the QoS SFC List. 2. Configure the Uplink Service Flow. a. Navigate to ADVANCED CONFIGURATION > QoS > SFC list. b. Click Add. c. Enter the following parameters:
Service Flow Name: UL-Management Scheduler Type: RtPS Traffic Direction: Uplink MIR: 1000 CIR: 1000 Max Latency: 20 Tolerable Jitter: 10 Priority: 7 Max Messages in Burst: 16 Entry Status: Enable d. Click Add. The UL-Management SF is added to the QoS SFC List.
: The input and output bandwidth limits set on the End Point A or BSU or on the End Point B or SU are used for limiting aggregate bandwidth used by the SU or End Point B. These limits override any limit imposed by MIR in the SFC. Therefore, these limits should be set to at least 1000 Kbps (MIR values in UL-Management and DL-Management SFCs). Tsunami 800 & 8000 Series - Software Management Guide 157 Advanced Configuration 5.6.3.0.5 Step 3: Configure QoS Classes Finally, the DL-Management SFC and UL-Management SFCs created in Step 2 must be added to each QoS Class used by the Quick Bridge network. Additionally, within the QoS class, these SFC must have the three PIRs mentioned in Step 1 associated with them. 1. Add SFCs to QoS Class. a. Navigate to ADVANCED CONFIGURATION > QoS > Class list. b. Click Details corresponding to the first class (Unlimited Best Effort) you wish to modify. c. Under the QoS Class Service Flow, click Add. d. Configure the following parameters, and click Add. This adds the New SFC & PIR relation to the QoS Class. Service Flow Name: DL-Management PIR Rule Name: ARP PIR Priority: 63 Entry Status: Enable. e. Again click Add under the QoS Class Service Flow Details. f. Configure the following parameters and click Add. This adds the New SFC & PIR relation to the QoS Class. Service Flow Name: UL-Management PIR Rule Name: ARP PIR Priority: 63 Entry Status: Enable 2. Add PIRs to SFCs within the QoS Class. a. Navigate to ADVANCED CONFIGURATION > QoS > Class list. b. Click Details corresponding to the first class (Unlimited Best Effort) you wish to modify. c. Under the QoS Class Service Flow Details, click Details corresponding to the DL-Management Service Flow. d. Under the QoS Class PIR Details heading, click Add. e. Add the Management Station SRC IP PIR to this Service Flow by configuring the following parameters:
PIR Rule Name: Management Station SRC IP PIR Priority: 63 Entry Status: Enable f. Return to the Class List and add the UL-Management Service Flow in this class. g. Add the Management Station DST IP PIR to this Service Flow by configuring the following parameters:
PIR Rule Name: Management Station DST IP PIR Priority: 63 Entry Status: Enable 5.7 RADIUS Based SU QoS Configuration RADIUS based QoS configuration enables you to configure QoS parameters on an SU through RADIUS Server. This way of configuring QoS parameters, reduces the task of manually configuring QoS parameters on each SU available on the network. Explained below is the process followed to configure QoS parameters on an SU from a RADIUS Server. Tsunami 800 & 8000 Series - Software Management Guide 158 Advanced Configuration Figure 5-92 RADIUS Based QoS Configuration To establish a connection with the BSU, the SU sends a registration request to BSU. On receiving the registration request, the BSU sends an Access request along with the SU MAC address, to the RADIUS Server. The RADIUS Server then checks the authentication of the user. If it is an authenticated user, it sends an Access-Accept response along with Vendor assigned QoS parameters value to the BSU. On receiving the response, the BSU sends the response to the SU. The received QoS parameters are then applied on the SU. Given below are the vendor specific attributes:
Name of the attribute Vendor Assigned Attribute Number Attribute Format Attribute Value QoS Class Index QoS Class SU Table Status 34 35 Decimal Decimal 1 8 1 Enable / 2 Disable
:
RADIUS Based QoS configuration takes priority over Local QoS configuration. When the link is down, the configuration received from the RADIUS is lost. 5.8 VLAN (Bridge Mode Only) The Virtual Local Area Network (VLAN) feature helps in logical grouping of network host on different physical LAN segments, which can communicate with each other as if they are all on the same physical LAN segment. With VLANs, you can conveniently, efficiently, and easily manage your network in the following ways:
Define groups Limits the broadcast and multicast traffic to a specific VLAN group Improve network performance and reduce latency Increase security Secure network restricts members to resources on their own VLAN The SUs and End Point devices support QinQ VLAN feature that enables service providers to use a single VLAN ID to support multiple customer VLANs by encapsulating the 802.1Q VLAN tag within another 802.1Q frame. The benefits with QinQ are, Tsunami 800 & 8000 Series - Software Management Guide 159 Increases the VLAN space in a provider network or enterprise backbone Reduce the number of VLANs that a provider needs to support within the provider network for the same number of customers Enables customers to plan their own VLAN IDs, without running into conflicts with service provider VLAN IDs Provides a simple Layer 2 VPN solution for small-sized MANs (Metropolitan Area Networks) or intranets Provides customer traffic isolation at Layer 2 within a service provider network Advanced Configuration 5.8.1 System-Level VLAN Configuration To configure system-level VLAN parameters, navigate to ADVANCED CONFIGURATION > VLAN. The VLAN configuration screen appears. Figure 5-93 System-Level VLAN Configuration (BSU) Figure 5-94 System-Level VLAN Configuration (SU/End Point A/End Point B) 1. VLAN Status: This parameter is used to either enable or disable VLAN feature on the device. By default, this parameter is disabled. To enable VLAN, select the VLAN Status box. If VLAN status is enabled, it indicates that locally configured VLAN parameters will be applied on the device. If VLAN status is disabled, it indicates that the device is open for remote VLAN configuration. 2. Management VLAN Id: This parameter enables the user to configure VLAN Id for management frames (SNMP, ICMP, Telnet and TFTP). The stations that manage the device must tag the management frames with the management VLAN Id. By default, the Management VLAN Id is set to -1 which indicates no tag is added to the management frame. To set VLAN tag to the management frame, enter a value ranging from 1 to 4094.
: Before setting the Management VLAN Id, make sure that the station that manages the device is a member of the same VLAN; else, your access to the device will be lost. Tsunami 800 & 8000 Series - Software Management Guide 160 Advanced Configuration 3. Management VLAN Priority: This parameter is used to set IEEE 802.1p priority for the management frames. By default, the priority is set to 0. To set the VLAN priority, enter a value ranging from 0 to 7. 4. Double VLAN (Q in Q) Status: Q in Q (also called as Double VLAN or Stacked VLAN) mechanism expands the VLAN space by tagging the tagged packets, thus producing a double-tagged frame. The expanded VLAN space allows the service provider to provide certain services, such as Internet access on specific VLANs for specific customers, and still allows the service provider to provide other types of services for their other customers on other VLANs. By default, Double VLAN is disabled on the device. To enable, select Enable from the Double VLAN (Q in Q) Status box and click OK.
:
Only SU, End Point A and End Point B support Double VLAN (Q in Q) feature. If Double VLAN (Q in Q) Status is enabled, device expects Double VLAN tagged packet in Downlink direction. Management can be accessed with single VLAN based on the management VLAN ID configured. For more details on QinQ, refer to Appendix QinQ. 5. Service VLAN TPID: The Tag Protocol Identifier (TPID) helps to identify the frame as VLAN tagged frame. The user can configure Service VLAN TPID as either 0x8100, 0x9100, or 0x88a8. By default the Service VLAN TPID is set to 0x8100. 6. Service VLAN Id: This parameter enables the user to configure outer/service provider VLAN ID for the data frames. By default, the Service VLAN ID is set to -1 which indicates no outer/service VLAN tag is added to the data frame. To set VLAN tag to the frame, enter a value ranging from 1 to 4094.
: When Double VLAN is enabled on the device, the Service VLAN ID should not be set to -1. 7. Service VLAN Priority: This parameter is used to set IEEE 802.1p priority in outer/service VLAN tag for the data frames. By default, the priority is set to 0. To set the VLAN priority, enter a value ranging from 0 to 7. 5.8.2 Ethernet VLAN Configuration You can configure VLAN on the Ethernet interface(s) by using any one of the following VLAN Modes:
1. Transparent Mode 2. Access Mode 3. Trunk Mode 5.8.2.1 Transparent Mode Transparent mode can be configured in a BSU, SU and End Point devices. This mode is equivalent to NO VLAN support and is the default mode. It is used to connect VLAN aware or unaware networks. In this mode, the device transfers both tagged and untagged frames received on the Ethernet or WORP interface. To configure the Ethernet interface of the device in VLAN Transparent Mode, navigate to ADVANCED CONFIGURATION >
VLAN > Ethernet. The VLAN Ethernet Configuration screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 161 Advanced Configuration Given below is the table which explains the method to configure the device in Transparent mode:
Figure 5-95 Transparent Mode Parameters Interface VLAN Mode Description Displays the name of the Ethernet interface. Select the VLAN mode as Transparent.
: When the device is configured in Double VLAN mode, do not configure the Ethernet interface of the device in Transparent Mode. Click OK and then COMMIT.
: Wireless Interface of the device will always be in transparent mode. There is no support provided to edit the VLAN parameters of the wireless interface. 5.8.2.2 Access Mode Access Mode can be configured in an SU, End Point A and End Point B. This mode is used to connect VLAN aware networks with VLAN unaware networks. The ingress untagged traffic received on the Ethernet interface are tagged with the configured Access VLAN Id and Access VLAN priority before forwarding to the WORP interface. Similarly all egress tagged frames with specified VLAN Id are untagged at the Ethernet interface and then forwarded. Based on the Management VLAN ID configuration, both tagged and untagged management frames can access the device from the WORP interface. However, only untagged management frames can access the device from the Ethernet Interface; the tagged frames are dropped. To configure the Ethernet interface of the device in Access Mode, navigate to ADVANCED CONFIGURATION > VLAN >
Ethernet. The VLAN Ethernet Configuration screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 162 Advanced Configuration Given below is the table which explains the method to configure the device in Access Mode:
Figure 5-96 Access Mode Parameter Interface VLAN Mode Access VLAN Id Description Displays the name of the Ethernet interface. Select the VLAN mode as Access and click OK. Enter the Access VLAN Id in the Access VLAN Id box. The untagged data frames received at the Ethernet interface are tagged with this configured VLAN Id and then forwarded to the WORP interface. By default, the Access VLAN Id is set to -1 which indicates no tag is added to the data frame. To set Access VLAN tag to the data frame, enter a value ranging from 1 to 4094.
: When Double VLAN is enabled on the device, the Access VLAN ID should not be set to -1. Access VLAN Priority This parameter is used to set IEEE 802.1p priority for the data frames. By default, the priority is set to 0. To set the Access VLAN priority, enter a value ranging from 0 to 7. Allow Untagged Mgmt Access When enabled, the Management Access is allowed using untagged packets. By default, it is disabled. Click OK and then COMMIT. 5.8.2.3 Trunk Mode Trunk Mode can be configured in a BSU, SU, End Point A and End Point B. This mode is used to connect VLAN aware networks with VLAN aware networks. In the Trunk mode, the Ethernet interface of the device forwards only those tagged frames whose VLAN Id matches with a VLAN Id present in the trunk table. If the device receives untagged frames and the Allow Untagged Frames functionality is disabled, then the untagged packets are dropped. If the Allow Untagged Frames functionality is enabled, then functionality varies based on the device:
Tsunami 800 & 8000 Series - Software Management Guide 163 In case of a BSU, the untagged packets are forwarded to the destination. In case of an SU, End Point A and End Point B, the device behaves as in Access Mode for untagged traffic. The untagged frames are tagged with the configured Port VLAN ID and forwarded to the destination. Advanced Configuration
: Mixed VLAN Mode = Trunk Mode + Allow Untagged Frames + Port VLAN ID To configure the Ethernet interface of the device in Trunk mode, navigate to ADVANCED CONFIGURATION > VLAN >
Ethernet. The VLAN Ethernet Configuration screen appears:
Figure 5-97 Trunk Mode (BSU)
: Ensure to configure an entry in Ethernet Trunk table, with a Trunk ID identical to Roaming VLAN ID. Figure 5-98 Trunk Mode (SU/End Point A/End Point B) Tsunami 800 & 8000 Series - Software Management Guide 164 Given below is the table which explains the method to configure the device in Trunk Mode:
Advanced Configuration Parameter Interface VLAN Mode Allow Untagged Frames Description Displays the name of the Ethernet interface. Select the VLAN Mode as Trunk. Select Enable or Disable. By default, it is disabled. Disable: If this option is selected, the Ethernet interface forwards only tagged frames whose VLAN Id matches with a VLAN ID present in trunk table. Enable:
In case of a BSU, when Allow Untagged Frames is enabled, the Ethernet interface of the device forwards the data packets as-is. In case of an SU/End Point A/End Point B, when Allow Untagged Frames is enabled, the device behaves as in Access mode. Click OK. Port VLAN ID Enter the Port VLAN ID in the Port VLAN ID box. The untagged data frames received at the Ethernet interface are tagged with this port VLAN Id and then forwarded to the destination interface. By default, the Port VLAN Id is set to -1 which indicates no tag is added to the data frame. To set Port VLAN tag to the data frame, enter a value ranging from 1 to 4094.
:
Applicable only on an SU, End Point A and End Point B. When Double VLAN is enabled on the device, the Port VLAN ID should not be set to -1. The configured Port VLAN Id should not exist in the Trunk table. Port VLAN Priority This parameter is used to set IEEE 802.1p priority for the data frames. By default, the priority is set to 0. To set the Port VLAN priority, enter a value ranging from 0 to 7.
: Applicable only to SU and End Point devices. After configuring the required parameters, click OK and then COMMIT. 5.8.2.3.1 Add VLAN IDs to Trunk Table To add VLAN IDs to the trunk table, 1. Click Add in the VLAN Ethernet Configuration screen. The VLAN Trunk Table Add Row screen appears. Tsunami 800 & 8000 Series - Software Management Guide 165 Figure 5-99 Add VLAN IDs to Trunk Table Given below is the table which explains the method to add VLAN IDs to Trunk Table:
Parameter Trunk Id Entry Status Enter VLAN ID in the Trunk Id box. Description This parameter indicates the status of each VLAN Trunk Id entry. By default, the Trunk Id is enabled. To disable, select Disable from the Entry Status box. Advanced Configuration 2. Click Add. 3. To save and apply the configured parameters on the device, click COMMIT.
: You can configure a maximum of 256 trunk VLAN Ids in a BSU and End Point A device, and 16 trunk VLAN Ids in an SU and End Point B device. 5.9 RADIUS Based SU VLAN Configuration RADIUS based VLAN configuration enables you to configure VLAN parameters on an SU through RADIUS Server. This way of configuring VLAN parameters, Reduces the task of manually configuring VLAN parameters on each SU available on the network Allows SU to remain on the same VLAN as it moves across the network Explained below is the process followed to configure VLAN parameters on an SU from a RADIUS Server. Figure 5-100 RADIUS Based VLAN Configuration To connect to a BSU, the SU sends a registration request to BSU. On receiving the registration request, the BSU sends an Access request along with the SU MAC address, to the RADIUS Server. The RADIUS Server then checks the authentication of the user. If it is an authenticated user, it sends an Access-Accept response along with Vendor assigned VLAN parameters value to the BSU. On receiving the response, the BSU sends the response to the SU. The received VLAN parameters are then applied on the SU. Given below are the vendor specific attributes:
Name of the attribute Vendor Assigned Attribute Number Attribute Format Attribute Value SU VLAN MAC 3 MacAddr SU Mac Address Tsunami 800 & 8000 Series - Software Management Guide 166 Advanced Configuration Name of the attribute Vendor Assigned Attribute Number Attribute Format Attribute Value Ethernet 1 VLAN Mode SU VLAN Name Ethernet 1 Access VLAN ID Ethernet 1 Access VLAN Priority Management Attribute VLAN ID Management VLAN Priority 4 5 6 7 8 9 Decimal 1 Transparent Mode 2 Access Mode / 3 Trunk Mode String SU VLAN Name Decimal 1 4095 Decimal 0 7 Decimal 1 4095 Decimal 0 7 VLAN Ethernet 1 Trunk IDs 1 to 16 10 25 Decimal 1 4095 SU VLAN Table Status
(Applicable only to MP/QB.11devices) Service VLAN ID (Q-in-Q) Service VLAN Priority (Q-in-Q) QoS Class Index QoS Class SU Table Status Ethernet 2 VLAN Mode Ethernet 2 Access VLAN ID Ethernet 2 Access VLAN Priority 26 32 33 34 35 40 41 42 Decimal 1 enable / 2 disable / 3 delete Decimal 1 4095 Decimal Decimal 0 7 1 8 Decimal 1 Enable / 2 Disable Decimal 1 Transparent Mode 2 Trunk Mode / 3 Access Mode Decimal 1 4095 Decimal 0 7 VLAN Ethernet 2 Trunk IDs 1 to 16 43 58 Decimal 1 4095 Double VLAN (Q-in-Q) Status Serviceably TPID (Q-in-Q) Ethernet 1 Port VLAN ID Ethernet 1 port VLAN Priority VLAN Ethernet 1 Allow Untag Frames Ethernet 2 Port VLAN ID Ethernet 2 Port VLAN Priority VLAN Ethernet 2 Allow Untag Frames VLAN Ethernet 1 Allow Untag Management VLAN Ethernet 2 Allow Untag Management 59 60 61 62 63 64 65 66 68 69 Decimal 1 Enable / 2 Disable Decimal 1 - InnerTag / 2 - Outer Tag Decimal 1 4095 Decimal 0 7 Decimal 1 Enable / 2 Disable Decimal 1 4095 Decimal 0 7 Decimal 1 Enable / 2 Disable Decimal Decimal 1-Enable 2-Disable 1-Enable 2-Disable Tsunami 800 & 8000 Series - Software Management Guide 167 Advanced Configuration
:
RADIUS configuration is applicable only when the VLAN Status is disabled on the SU. Local VLAN configuration takes priority over RADIUS Based VLAN configuration. When the link is down, the configuration received from the RADIUS is lost. An MP.11 SU should locally configure VLAN parameters when connected to a MP 82x/8000 BSU in legacy mode as the BSU will not assign any VLAN parameters based on RADIUS authentication. An MP 82x/8000 SU should locally configure VLAN in legacy mode when connected to a MP.11 BSU, should locally configure VLAN parameters as the BSU shall not assign VLAN parameters based on RADIUS authentication. 5.10 Filtering (Bridge Only) Filtering is useful in controlling the amount of traffic exchanged between the wired and wireless networks. By using filtering methods, we can restrict any unauthorized packets from accessing the network. Filtering is available only in bridge mode. The various filtering mechanisms supported by the device are as follows:
Protocol Filter Static MAC Address Filter Advanced Filtering TCP/UDP Port Filter Storm Threshold Filter WORP Intra Cell Blocking Filters get activated only when they are globally enabled on the device. To apply/configure global filters on the device, navigate to ADVANCED CONFIGURATION > Filtering. The Filtering screen appears. Figure 5-101 Filtering Given below is the table which explains Filtering parameters and the method to configure the configurable parameter(s):
Parameter Global Filter Flag Description By default, Global Filtering is disabled meaning which no filters are applied on the device. To apply filters on the device, enable the Global Filter Flag. Please note that if Global Filter Flag is not enabled on the device, then none of the filters can be applied on the device. Tsunami 800 & 8000 Series - Software Management Guide 168 Parameter STP/LACP Frames Advanced Configuration Description This parameter allows you to either Block or Passthru STP/LACP frames on the network. Passthru: By allowing the STP/LACP frames, any loops that occurs within a network can be avoided. If configured to Passthru, the STP/LACP frames in the system are bridged. Block: When blocked, the STP/LACP frames encountered on a network are terminated at bridge. By default, STP/LACP frames are allowed on the network.
: STP or LACP Frame Status will block or passthru the frames destined to IEEE 802.1D and 802.1Q reserved MAC address (01:80:C2:00:00:00 to 01:80:C2:00:00:0F). After configuring the required parameters, click OK and then COMMIT. 5.10.1 Protocol Filter The Protocol Filter blocks or forwards packets based on the protocols supported by the device. To configure Protocol Filter on the device, navigate to ADVANCED CONFIGURATION > Filtering > Protocol Filter. The Protocol Filter screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 169 Figure 5-102 Protocol Filter Given below is the table which explains Protocol Filter parameters and the method to configure the configurable parameter(s):
Advanced Configuration Parameter Filtering Control Filtering Type Description This parameter is used to apply filters on the devices interface. The filtering can be applied on any of the following interfaces:
Ethernet: Packets are examined at the Ethernet interface. Wireless: Packets are examined at the Wireless interface. All Interfaces: Packets are examined at both Ethernet and Wireless interface. By default, the Filtering Control is set to Disable, meaning which Protocol Filters are disabled on all the interfaces.
: In addition to enabling Filtering Control, the Global Filter Flag should also be enabled to apply filters. This parameter specifies the action to be performed on the data packets whose protocol type is not defined in the protocol filter table (this table contains a list of default protocols supported by the device and the protocols defined by the user), or whose Entry Status is in Disable state. The available filtering types are:
Block: The protocols with entry status Disable or the protocols which do not exist in the protocol filtering table are blocked. Passthru: The protocols with entry status Disable or the protocols which do not exist in the protocol filtering table are allowed through the configured interface. After configuring the required parameters, click OK and then COMMIT. 5.10.1.1 Protocol Filter Table The Protocol Filter table displays a list of default protocols supported by the device and the protocols created by the user. By default, the system generates 19 protocols entries. Each of the Protocol contains the following information:
Parameter Protocol Name Protocol Number Description Represents the Protocol name. The system throws an error when you try to edit the name of a default protocol. Represents the Protocol number. The value is of 4 digit hexadecimal format. The system throws an error when you try to edit the Protocol number of a default protocol. Filter Status The supported filter status are, Passthru: When the filter status is set to Passthru and entry status is Enable, all packets whose protocol matches with the given protocol number are forwarded on the configured interface. Block: When the filter status is set to Block and entry status is Enable, all packets whose protocol matches with the given protocol number are dropped on the configured interface. Entry Status Set the entry status as either Enable, Disable or Delete. By default, the status is set to Block. Enable: Enables filter status on a protocol. Disable: Disables filter status on a protocol. Delete: Deletes a protocol entry from the Protocol Filter Table. Tsunami 800 & 8000 Series - Software Management Guide 170
\
: System-defined default protocols cannot be deleted. 5.10.1.2 Add User-defined Protocols to the Filter Table To add user-defined protocols to the Protocol Filter Table, click Add in the Protocol Filter screen. The Protocol Filter Add Row screen appears. Advanced Configuration Enter details for all the required parameters and click Add. Figure 5-103 Add User-defined Protocols
: The maximum number of Protocol Filters that can be added to the table are 64, out of which 19 are default entries. 5.10.2 Static MAC Address Filter The Static MAC Address filter optimizes the performance of a wireless (and wired) network. With this feature configured, the device can block traffic between wired devices and wireless devices based on the MAC address. Each MAC Address or Mask is comprised of 12 hexadecimal digits (0-9, A-F) that correspond to a 48-bit identifier. (Each hexadecimal digit represents 4 bits (0 or 1)). Taken together, a MAC Address/Mask pair specifies an address or a range of MAC addresses that the device will look for when examining packets. The device uses Boolean logic to perform an AND operation between the MAC Address and the Mask at the bit level. A Mask of 00:00:00:00:00:00 corresponds to all MAC addresses, and a Mask of FF:FF:FF:FF:FF:FF applies only to the specified MAC Address. For example, if the MAC Address is 00:20:A6:12:54:C3 and the Mask is FF:FF:FF:00:00:00, the device will examine the source and destination addresses of each packet looking for any MAC address starting with 00:20:A6. If the Mask is FF:FF:FF:FF:FF:FF, the device will only look for the specific MAC address (in this case, 00:20:A6:12:54:C3). You can configure the Static MAC Address Filter parameters depending on the following scenarios:
To prevent all traffic from a specific wired MAC address from being forwarded to the wireless network, configure only the Wired MAC Address and Wired Mask (leave the Wireless MAC Address and Wireless Mask set to all zeros). To prevent all traffic from a specific wireless MAC address from being forwarded to the wired network, configure only the Wireless MAC address and Wireless Mask (leave the Wired MAC Address and Wired Mask set to all zeros). To prevent traffic between a specific wired MAC address and a specific wireless MAC address, configure all four parameters. Configure the wired and wireless MAC address and set the wired and wireless mask to all Fs. To prevent all traffic from a specific wired Group MAC address from being forwarded to the wireless network, configure only the Wired MAC Address and Wired Mask (leave the Wireless MAC Address and Wireless Mask set to all zeros). Tsunami 800 & 8000 Series - Software Management Guide 171 To prevent all traffic from a specific wireless Group MAC address from being forwarded to the wired network, configure only the Wireless MAC address and Wireless Mask (leave the Wired MAC Address and Wired Mask set to all zeros). To prevent traffic between a specific wired Group MAC address and a specific wireless Group MAC address, configure all four parameters. Configure the wired and wireless MAC address and set the wired and wireless mask to all Fs. Static MAC Filter Examples Consider a network that contains a wired PC and three wireless PCs. The MAC addresses for each PCs are as follows:
Advanced Configuration MAC Address of the wired PC: 00:40:F4:1C:DB:6A MAC Address of the wireless PC1: 00:02:2D:51:94:E4 MAC Address of the wireless PC2: 00:02:2D:51:32:12 MAC Address of the wireless PC3: 00:20:A6:12:4E:38 5.10.2.0.1 Prevent two specific PCs from communicating Configure the following settings to prevent the wired PC and wireless PC1 from communicating:
Wired MAC Address: 00:40:F4:1C:DB:6A Wired Mask: FF:FF:FF:FF:FF:FF Wireless MAC Address: 00:02:2D:51:94:E4 Wireless Mask: FF:FF:FF:FF:FF:FF Result: Traffic between the wired PC and wireless PC1 is blocked. wireless PC2 and PC3 can still communicate with the wired PC. 5.10.2.0.2 Prevent multiple Wireless PCs from communicating with a single wired PC Configure the following settings to prevent wireless PC1 and PC2 from communicating with the wired PC:
Wired MAC Address: 00:40:F4:1C:DB:6A Wired Mask: FF:FF:FF:FF:FF:FF Wireless MAC Address: 00:02:2D:51:94:E4 Wireless Mask: FF:FF:FF:00:00:00 Result: When a logical AND is performed on the Wireless MAC Address and Wireless Mask, the result corresponds to any MAC address beginning with the 00:20:2D prefix. Since wireless PC1 and wireless PC2 share the same prefix (00:02:2D), traffic between the wired Server and wireless PC1 and PC2 is blocked. Wireless PC3 can still communicate with the wired PC since it has a different prefix (00:20:A6). 5.10.2.0.3 Prevent all wireless PCs from communicating with a single wired PC Configure the following settings to prevent wired PC from communicating with all three wireless PCs:
Wired MAC Address: 00:40:F4:1C:DB:6A Wired Mask: FF:FF:FF:FF:FF:FF Wireless MAC Address: 00:00:00:00:00:00 Wireless Mask: 00:00:00:00:00:00 Result: The device blocks all traffic between the wired PC and all wireless PCs. 5.10.2.0.4 Prevent a wireless PC from communicating with the wired network Configure the following settings to prevent wireless PC3 from communicating with any device on the Ethernet:
Wired MAC Address: 00:00:00:00:00:00 Wired Mask: 00:00:00:00:00:00 Tsunami 800 & 8000 Series - Software Management Guide 172 Wireless MAC Address: 00:20:A6:12:4E:38 Wireless Mask: FF:FF:FF:FF:FF:FF Result: The device blocks all traffic between wireless PC3 and the Ethernet network. Advanced Configuration 5.10.2.1 Static MAC Address Filter Configuration To configure Static MAC Filter parameters, navigate to ADVANCED CONFIGURATION > Filtering > Static MAC Address Filter. The Static MAC Address Filter screen appears:
Click Add in the Static MAC Address Filter screen. The Static MAC Address Filter Add Row screen appears. Figure 5-104 Static MAC Address Filter Figure 5-105 Static MAC Address Filter Add Entry Given below is the table which explains Static MAC Address Filter parameters and the method to configure the configurable parameter(s):
Parameter Wired MAC Address Specifies the MAC address of the device on the wired network that is restricted from communicating with a device on the wireless network. Description Wired MAC Mask Specifies the range of MAC address to which this filter is to be applied. Wireless MAC address Specifies the MAC address of the device on the wireless network that is restricted from communicating with a device on the wired network. Wireless MAC Mask Specifies the range of MAC address to which this filter is to be applied. Tsunami 800 & 8000 Series - Software Management Guide 173 Advanced Configuration Parameter Comment Status Description Specifies the comment associated with Static MAC Filter table entry. Specifies the status of the newly created filter. Click Add and then COMMIT.
:
You can configure a maximum of 200 MAC address filters. The Wired MAC address and the Wireless MAC address should be a unicast MAC address. The MAC Address or Mask includes 12 hexadecimal digits (each hexadecimal equals to 4 bits containing 0 or 1) which is equivalent to 48 bit identifier. 5.10.3 Advanced Filtering With Advanced Filtering, you can filter pre-defined IP Protocol traffic on the network. By default, 5 IP protocols are pre-defined and based on the configuration they can be blocked or allowed to enter the network. To apply filters on the IP protocols, navigate to ADVANCED CONFIGURATION > Filtering > Advanced Filtering. The Advanced Filtering screen appears:
The Advanced Filtering table contains a list of 5 pre-defined protocols on which Advanced Filtering is applied. The following table explains the Filtering table parameters:
Figure 5-106 Advanced Filtering Tsunami 800 & 8000 Series - Software Management Guide 174 Parameter Protocol Name Represents the protocol name. By default, Advanced Filtering is supported on the following 5 default protocols:
Description Advanced Configuration Deny IPX RIP Deny IPX SAP Deny IPX LSP Deny IP Broadcasts Deny IP Multicasts Direction Represents the direction of an IP Protocol traffic that needs to be filtered. The directions that can be filtered are, Ethernet to wireless Wireless to ethernet Both Entry Status The filters are applied on the IP protocol only when Entry Status is enabled.
:
The Advanced Filtering table contains a maximum of 5 pre-defined IP protocols. User-defined IP protocols cannot be added to the Advanced Filtering table. 5.10.3.1 Edit Advanced Filtering Table Entries To edit Advanced Filtering table protocols, click Edit in the Advanced Filtering screen. The Advanced Filtering - Edit Entries screen appears. Tsunami 800 & 8000 Series - Software Management Guide 175 Figure 5-107 Advance Filtering- Edit Entries Modify the IP protocol traffic direction that needs to be filtered, and the filtering status for the desired IP Protocol. Advanced Configuration Next click OK and then COMMIT. 5.10.4 TCP/UDP Port Filter TCP/UDP Port Filtering allows you to enable or disable Transmission Control Protocol (TCP) ports and User Datagram Port
(UDP) ports on network devices. A user specifies a Protocol Name, Port Number, Port Type (TCP, UDP, or TCP/UDP), and filtering interfaces (Only Wireless, Only Ethernet or Both) in order to block access to services such as Telnet and FTP, and traffic such as NETBIOS and HTTP. To apply filters on TCP/UDP Port, navigate to ADVANCED CONFIGURATION > Filtering > TCP/UDP Port Filter. The TCP/UDP Port Filter screen appears. The Filter Control parameters determines if filter has to be applied or not on a TCP/UDP Port. By default, it is disabled. To apply filters, select Enable and click OK. Figure 5-108 TCP/UDP Port Filter 5.10.4.1 TCP/UDP Port Filter Table The TCP/UDP Port Filter table displays a list of default TCP/UDP ports and user-defined ports which can be enabled or disabled as desired. By default, the device support 7 default TCP/UDP port filter entries. Parameter Protocol Name Represents the name of the service/protocol. Please note that the system throws an error when an attempt is made to edit the default service/protocol name. Description Tsunami 800 & 8000 Series - Software Management Guide 176 Parameter Port Number Represents the destination port number. Please note that the system throws an error when an attempt is made to edit the port number. Description Port Type Represents the port type (TCP, UDP, Both). Filter Interface Represents the interface on which the filter is applied. The supported interfaces are, Advanced Configuration Only Ethernet Only Wireless All Interfaces Entry Status Set the entry status as either Enable, Disable or Delete. Enable: Filter is applied and filters the packet based on the Port number and port type. Disable: No filter is applied. Delete: Allows to delete only user-defined TCP/UDP port filter entry. When you attempt to delete default entries, the device throws an error. If you have configured any user-defined protocols then click OK and then COMMIT. For example, a device with the following configuration would discard frames received on its Ethernet interface with a UDP destination port number of 137, effectively blocking NETBIOS Name Service packets. Please note that even the Filtering Control should be enabled to apply the filter. Protocol Name NETBIOS Name Service Port Number 137 Port Type UDP Filter Interface Entry Status (Enable/Disable) Ethernet Enable 5.10.4.2 Adding User-defined TCP/UDP Port Filter Entries To add user-defined TCP/UDP port filter entries to the table, click Add in the TCP / UDP Port Filter screen. The TCP/UDP Port Filter Add Row screen appears:
Figure 5-109 Add User-defined TCP/UDP Protocols Provide details for all the parameters and click Add. To apply the configured parameters, click COMMIT. Tsunami 800 & 8000 Series - Software Management Guide 177 Advanced Configuration
:
The TCP/UDP filtering operation is allowed only when the Global Flag and Filter Control options are enabled. You can add a maximum of 64 TCP/UDP Port Filter entries to the table, out of which 7 are default entries. 5.10.5 Storm Threshold Filter The Storm Threshold Filter restricts the excessive inbound multicast or broadcast traffic on layer two interfaces. This protects against broadcast storms resulting from spanning tree misconfiguration. A broadcast or multicast filtering mechanism needs to be enabled so that a large percentage of the wireless link remains available to the connected mobile terminals. To configure Storm Threshold Filter, navigate to ADVANCED CONFIGURATION > Filtering > Storm Threshold Filter. The Storm Threshold Filter screen appears. This screen contains information about the threshold values per second of the multicast and broadcast packets that can be processed for the interface(s) present in the device. Given below is the table which explains Storm Threshold Filter parameters and the method to configure the configurable parameter(s):
Figure 5-110 Storm Threshold Filter Parameter Interface Multicast Threshold Broadcast Threshold Description Allows to configure the type of interface on which filtering has to be applied. The Storm Threshold filter can be used to filter the traffic on two types of interfaces: Ethernet or Wireless. By default, Storm Threshold filtering is disabled on both Ethernet and Wireless interfaces. Allows to configure the threshold value of the multicast packets to be processed for the Ethernet or Wireless interface. Packets more than threshold value are dropped. If threshold value for multicast packets is set to '0', filtering is disabled. The default Multicast Threshold value is 0 per second. Allows to configure the threshold value of the broadcast packets to be processed for the Ethernet or Wireless interface. Packets more than threshold value are dropped. If threshold value for broadcast packets is set to '0', filtering is disabled. The default Broadcast Threshold value is 0 per second. After configuring the required parameters, click OK and then COMMIT. Tsunami 800 & 8000 Series - Software Management Guide 178 5.10.6 WORP Intra Cell Blocking Advanced Configuration
: Intra Cell Blocking is applicable only to a BSU in Bridge Mode only. The WORP Intra Cell Blocking feature restricts traffic between SUs which are registered to the same BSU. The two potential reasons to isolate traffic among the SUs are:
To provide better security by isolating the traffic from one SU to another in a public space. To block unwanted traffic between SUs to prevent this traffic from using bandwidth. The user can form groups of SUs at the BSU which define the filtering criteria. All data to/from SUs belonging to the same group are bridged. If an SU does not belong to any group, the BSU discards the data. The user can also configure a Security Gateway to block traffic between SUs connected to different BSUs. All packets destined for SUs not connected to the same BSU are forwarded to the Security Gateway MAC address (configured under Security Gateway). The following rules apply to Intra Cell Blocking Groups:
an SU can be assigned to more than one group. an SU that has not been assigned to any group cannot communicate to any other SU connected to the same or different BSU. 5.10.6.0.1 Example of Intra-Cell Blocking Groups Assume that four Intra Cell Blocking Groups have been configured on a BSU. SUs 1 through 10 are registered to the BSU. Group1 Group2 Group3 Group4 SU1 SU4 SU5 SU2 SU3 SU8 SU6 SU1 SU7 SU8 SU9 SU10 In this example, SU1 belongs to two groups, Group 1 and Group 3. Therefore, packets from SU1 destined to SU4, SU5, SU6 and SU7 are not blocked. However, SU9 belongs to group 4 only and packets from SU9 are blocked unless sent to SU8 or SU 10. To configuring Intra-Cell Blocking parameters, navigate to ADVANCED CONFIGURATION > Filtering> WORP Intra Cell Blocking. The following screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 179 Figure 5-111 Intra Cell Blocking This screen is classified into two categories: Intra Cell Blocking and Security Gateway. Given below are the configuration details. Advanced Configuration Parameter Description Intra Cell Blocking Status By default, Intra Cell Blocking is disabled on a BSU. Select Enable to enable the feature and then Click OK and then COMMIT. Security Gateway Status MAC Address By default, Security Gateway is disabled on a BSU. Select Enable to enable the feature. Represents the MAC address of the security gateway. This gateway routes the packets transmitted by the SU to the different BSUs to which it belongs. After configuring the required parameters, click OK and then COMMIT.
: Intra Cell Blocking is configurable only in Bridge mode. When you change the device from Bridge to Routing mode or vice-versa, Intra-Cell Blocking stops or starts working only after device reboot. 5.10.6.1 WORP Intra Cell Blocking Group Table The user can form groups of SUs at the BSU which define the filtering criteria. All data to/from SUs belonging to the same group are bridged. If an SU does not belong to any group, the BSU discards the data. By default, a BSU supports 16 groups and each group can contain a maximum of 240 SUs. Please note that a single SU can be a member of all the existing groups. To view and configure the Intra Cell Blocking Group table, navigate to ADVANCED CONFIGURATION > Filtering> WORP Intra Cell Blocking > Group Table. The WORP Intra Cell Blocking Group Table screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 180 Figure 5-112 WORP Intra Cell Blocking Group Table Advanced Configuration This table displays the list of groups. If the Entry Status for a group is set to Enable then BSU discards all the packets coming from SUs which are not members of that group. If set to Disable, then allows all the packets coming from SUs which are not the members of that group. If you have changed the Entry Status of a group, then click OK and then COMMIT. 5.10.6.2 WORP Intra Cell Blocking MAC Table The WORP Intra Cell Blocking MAC table allows to add SUs MAC address and assign them to the groups. You can add a maximum of 250 SUs to the table. To add SU to the table, navigate to ADVANCED CONFIGURATION > Filtering > WORP Intra Cell Blocking > MAC Table. The WORP Intra Cell Blocking MAC Table screen appears:
5.10.6.2.1 To add MAC addresses, click Add. The following screen appears. Figure 5-113 WORP Intra Cell Blocking MAC Table Figure 5-114 WORP Intra Cell Blocking MAC Table Add Entry Tsunami 800 & 8000 Series - Software Management Guide 181 Given below is the table which explains the WORP Intra Cell Blocking MAC Table entries and the method to configure the configurable parameter(s):
Advanced Configuration Parameter Description MAC Address Represents the MAC address of the SU. Group IDs 1 to 16 By default, a Group ID is disabled meaning which the SU is not a part of that group. To make it a part of that group, select Enable. Entry Status If SU is part of a group and its Entry Status is enabled then it can communicate with all the SUs belonging to that group. If Entry Status is disabled, then the communication is blocked. After adding the MAC address, click Add. To edit the existing MAC addresses, click Edit icon in the WORP Intra Cell Blocking MAC Table screen. Modify the parameters as desired in the WORP Intra Cell Blocking MAC Table Add Row screen and click OK and then COMMIT. In the WORP Intra Cell Blocking MAC Table, you can change the Entry Status as either Enable/Disable/Delete. Once the status is changed, click OK and then COMMIT. 5.11 DHCP Dynamic Host Configuration Protocol (DHCP) is a network protocol that enables a server to assign an IP address to the DHCP client from a defined range of IP addresses configured for a given network. Allocating IP addresses from a central location simplifies the process of configuring IP addresses to individual DHCP clients, and also avoids IP conflicts. 5.11.1 DHCP Pool DHCP Pool is a pool of defined IP addresses which enables a DHCP Server to dynamically pick IP address from the pool and assign it to the DHCP client. To configure a range of IP addresses in the DHCP Pool, navigate to ADVANCED CONFIGURATION > DHCP > DHCP Server
> Pool. The DHCP Pool screen appears:
Each pool entry comprises the following tabulated information:
Parameter Description Figure 5-115 DHCP Pool Interface Specifies the interface type, that is, Bridge or Routing (Ethernet and Wireless). Start IP Address and End IP Address Specifies the start and end IP address of the addresses to be added to the pool. Delete Allows you to delete a pool entry. Tsunami 800 & 8000 Series - Software Management Guide 182 Advanced Configuration
: You can add a maximum of five pool entries to the table. A pool entry can be deleted but cannot be edited. 5.11.1.1 Adding a New Pool Entry To add a new entry to the DHCP Pool, click Add on the DHCP Pool screen. The following DHCP Pool Table Add Row screen appears:
Figure 5-116 DHCP Pool Table Add Entry Enter the pool details and click Add. The entry will be updated in the DHCP pool table. To apply the configured changes, click COMMIT. 5.11.2 DHCP Server If DHCP Server is enabled, it picks automatically the IP addresses from the specific interface address pool and assigns them to the respective DHCP clients. DHCP Server feature is applicable to both Bridge and Routing Mode. In Routing mode, DHCP Server can be configured for each interface (Ethernet and Wireless) separately. Unless the DHCP Server functionality is enabled for an interface, the DHCP Server does not respond to the DHCP requests received on that interface. To configure the DHCP server parameters, navigate to ADVANCED CONFIGURATION > DHCP > DHCP Server > Interface. The DHCP Server screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 183 Figure 5-117 DHCP Server (Bridge Mode) Advanced Configuration Given below is the table which explains DHCP Server parameters and the method to configure the configurable parameter(s):
Figure 5-118 DHCP Server (Routing Mode) Parameter Description DHCP Server Status By default, DHCP Server is disabled on a device. To enable DHCP Server, select Enable. A DHCP Server can be enabled only when the following two conditions are satisfied:
1. Before enabling, atleast one interface should be enabled on which the DHCP Server has to run. 2. The DHCP pool table should have atleast one pool configured for that interface. Max Lease Time Specifies the maximum lease time for which the DHCP client can use the IP address provided by the DHCP Server. The value ranges from 3600 - 172800 seconds. DHCP Interface Table Interface Type Net Mask Specifies the interface for which the DHCP Server functionality shall be configured. That is Bridge or Ethernet/Wireless in case of Routing mode. Specifies the subnet mask to be sent to the DHCP client along with the assigned IP address. The netmask configured here should be greater than or equal to the netmask configured on the interface. Default Gateway Specifies the default gateway to be sent to the DHCP client along with the assigned IP Address. Default Gateway is a node that serves as an accessing point to another network. Primary DNS Specifies the primary DNS (Domain Name Server) IP address to be sent to the DHCP client. Secondary DNS Specifies the secondary DNS IP address to be sent to the DHCP client. Tsunami 800 & 8000 Series - Software Management Guide 184 Advanced Configuration Parameter Default Lease Time Description DHCP Server uses this option to specify the lease time it is willing to offer to the DHCP client over that interface. Once the lease time expires, the DHCP Server allocates a new IP address to the device. The Default Lease Time should be less than or equal to the configured Max Lease Time. Comment Entry Status Specifies a note for the device administrator. Used to Enable or Disable the DHCP Server functionality over the interface. After configuring the required parameters, click OK and then COMMIT. 5.11.3 DHCP Relay (Routing Mode only) The DHCP relay agent relays DHCP messages between the DHCP Clients and the configured DHCP Servers on different IP networks. You can configure a maximum of five DHCP Servers. There must be at least one DHCP Server configured in order to relay DHCP request.
: DHCP Relay Agent is configurable only in Routing mode. It cannot be enabled when NAT or DHCP Server is enabled. To view and configure DHCP Relay Server parameters, navigate to ADVANCED CONFIGURATION > DHCP > DHCP Relay >
Relay Server. The DHCP Relay screen appears:
Figure 5-119 DHCP Relay By default, DHCP Relay is disabled on the device. To enable it, atleast one DHCP Server IP address should be configured. To add a DHCP Server to the Relay Server Table, click Add in the DHCP Relay screen. The DHCP Relay Server Add Row screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 185 Figure 5-120 DHCP Relay Server Add Entry Advanced Configuration Enter the DHCP Server IP Address and then click Add. After configuring the required parameters, click OK and then COMMIT.
: DHCP server is disabled automatically if DHCP Relay agent is enabled and vice-verse. 5.12 IGMP Snooping
: IGMP Snooping is applicable only in Bridge Mode. Proxims Tsunami devices support Internet Group Management Protocol (IGMP) Snooping feature. With IGMP Snooping enabled on the device, multicast traffic is only forwarded to ports that are members of the specific multicast group. By forwarding the traffic only to the destined ports, reduces unnecessary load on devices to process packets. Explained below is the IGMP Snooping process with the help of a diagram:
The router forwards the IP multicast data to the BSU/End Point A. Figure 5-121 IGMP Snooping Process Tsunami 800 & 8000 Series - Software Management Guide 186 Lets say, with IGMP Snooping not enabled on the BSU/End Point A, the multicast data is transmitted over the wireless medium irrespective of whether the multicast group address is a member of the multicast group table maintained in each BSU/End Point A. With IGMP Snooping enabled, the BSU/End Point A transmits the data only when the multicast group address is a member of the multicast group table, else drops the packet. The SU/End Point B will receive the multicast data. Advanced Configuration Similarly, with IGMP Snooping not enabled on the SU/End Point B, the multicast data is transmitted irrespective of whether the multicast group address is a member of the multicast group table maintained in each SU/End Point B. With IGMP Snooping enabled, the SU/End Point B transmits the data to the host only when the multicast group address is a member of the multicast group table, else drops the packet. IGMP Snooping is of 2 kinds:
Active: Active IGMP Snooping listens to IGMP traffic and filters IGMP packets to reduce load on the multicast router. Passive: Passive IGMP Snooping simply listens to IGMP traffic and does not filter or interfere with IGMP.
:
Tsunami devices supports only passive IGMP Snooping. IGMP versions v1,v2 and v3 are supported. The device can add a maximum of 64 Multicast groups in the Snooping table. To configure IGMP Snooping parameters, navigate to ADVANCED CONFIGURATION > IGMP Snooping. The following IGMP Snooping screen appears:
Figure 5-122 IGMP Snooping Given below is the table which explains IGMP Snooping parameters and the method to configure the configurable parameter(s):
Parameter IGMP Snooping Status IGMP Membership Aging Timer IGMP Router Port Aging Timer IGMP Forced Flood Description By default, IGMP Snooping Status is disabled on the device, meaning which, the device transmits IP multicast traffic to all the ports. To forward the traffic only to the members of the specific multicast group, enable IGMP Snooping Status. Represents the time after which the IGMP multicast group age-outs or elapses. It ranges from 135 to 635 seconds. The default Aging Timer is 260 seconds. Represents the time after which the IGMP Router port age-outs or elapses. It ranges from 260 to 635 seconds. The default Aging Timer is 300 seconds. If you select Yes, all the unregistered IPv4 multicast traffic (with destination address which does not match any of the groups announced in earlier IGMP Membership reports) and IGMP Membership Reports will be flooded to all the ports. By default, IGMP Forced Flood is set to No. After configuring the required parameters, click OK and then COMMIT. Tsunami 800 & 8000 Series - Software Management Guide 187 Management 6 This chapter provides information on how to manage the device by using Web interface. It contains information on the following:
System File Management Services Simple Network Time Protocol (SNTP) Access Control Reset to Factory Convert QB to MP Auto Config Recovery
: Recommended characters for the name field are A-Z a-z 0-9 - _ = : . @ $ & and space. 6.1 System 6.1.1 System Information The System Information tab enables you to view and configure system specific information such as System Name, System Description, Contact Details of the person managing the device, and so on. To view and configure system specific Information, navigate to MANAGEMENT > System > Information. The System Information screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 188 Figure 6-1 System Information Management Given below is the table which explains System parameters and the method to configure the configurable parameter(s):
Parameter System Up-Time This is a read-only parameter. It represents the operational time of the device since its last reboot. Description System Description This is a read-only parameter. It provides system description such as system name, firmware version and the latest firmware build supported. System Name Email Phone Number Location GPS Longitude GPS Latitude GPS Altitude For example: MP-8200-BSU-G-US-v3.X.Y(Build No.) Represents the name assigned to the device. You can enter a system name of maximum 64 characters and should be unique across all devices in WORP network. Represents the email address of the person administering the device. You can enter an email address of minimum 6 and maximum 32 characters. Represents the phone number of the person administering the device. You can enter a phone number of minimum 6 and maximum 32 characters. Represents the location where the device is installed. You can enter the location name of minimum 0 and maximum 255 characters. Represents the longitude at which the device is installed. You can enter a longitude value of minimum 0 and maximum 255 characters. Represents the latitude at which the device is installed. You can enter a latitude value of minimum 0 and maximum 255 characters. Represents the altitude at which the device is installed. You can enter a altitude value of minimum 0 and maximum 255 characters. After configuring the required parameters, click OK and then COMMIT. 6.1.2 Inventory Management The Inventory Management tab provides inventory information about the device. To view inventory information, navigate to MANAGEMENT > System > Inventory Management. The System Inventory Management Table appears. Tsunami 800 & 8000 Series - Software Management Guide 189 Management Figure 6-2 An Example - Inventory Management By default, the components information is auto-generated by the device and is used only for reference purpose. Click Refresh, to view the updated system inventory management information. 6.1.3 Licensed Features Licensing is considered to be the most important component of an enterprise-class device which typically has a feature-based pricing model. It is also required to prevent the misuse and tampering of the device by a wide-variety of audience whose motives may be intentional or accidental. Licensed Features are, by default, set by the company. To view the licensed features set on the device, click MANAGEMENT > System > Licensed Features. The Licensed Features screen appears. Figure 6-3 An Example - Licensed Features Tsunami 800 & 8000 Series - Software Management Guide 190 Management Given below is the table which explains each of the parameters:
Parameter Description Product Description Description about the device. Number of Radios The number of radios the device supports. Number of Ethernet Interfaces Radio 1 Allowed Frequency Band The number of Ethernet interfaces supported by the device. The operational frequency band supported by the device radio. US 5.2 Support The US 5.2 frequency band is supported by the device if yes. Maximum Output Bandwidth Maximum Input Bandwidth The maximum output bandwidth limit of the device. It is represented in mbps. The maximum input bandwidth limit of the device. It is represented in mbps.
: The Input and Output Bandwidth features are referred with respect to the wireless interface. Input bandwidth refers to the data received on the wireless interface and output bandwidth refers to the data sent out of the wireless interface. Maximum Aggregate Bandwidth The maximum cumulative bandwidth of the device, which is the sum of configured output and input bandwidths. Product Family Represents the product family of the device. Product Class Represents the product class of the device, which is either indoor or outdoor. Allowed Operational Modes of Radio1 Maximum SUs Allowed MAC address of the Device is Represents the operational mode of the device, that is, BSU/SU/End Point A/End Point B. The maximum number of SUs that a BSU supports. The MAC address of the device. 6.1.3.1 License Upgrade Procedure In order to get additional bandwidth/US 5.2 G Hz frequency band Upgrade the License by following the procedure given below:
Retrieve the license information (License Info file with .lic extension) from the device. For more details, refer Retrieve From Device section. To purchase a license upgrade, please contact your Proxim Sales Representative; to generate a unique license file for your device, please refer to the Technical Note available on Proxim support site: https://my.proxim.com/article/3003 (for bandwidth), and https://my.proxim.com/article/3008 (for US 5.2 G Hz support). Upgrade the bandwidth using the license file(.bin extension) generated in the above step. For more details, refer Upgrade License section. Tsunami 800 & 8000 Series - Software Management Guide 191 6.2 File Management The File Management tab enables you to upgrade the firmware and configuration files onto the device, and retrieve configuration and log files from the device through Hypertext Transfer Protocol (HTTP) and Trivial File Transfer Protocol (TFTP). Management 6.2.1 TFTP Server A Trivial File Transfer Protocol (TFTP) server lets you transfer files across a network. By using TFTP, you can retrieve files from the device for backup or copying, and you can upgrade the firmware or the configuration files onto the device. You can download the SolarWinds TFTP server application from http://my.proxim.com. You can also download the latest TFTP software from SolarWinds Web site at http://www.solarwinds.net. While using TFTP server, ensure the following:
The upload or download directory is correctly set (the default directory is C:\TFTP-Root). The required firmware file is present in the directory. The TFTP server is running during file upload and download. You can check the connectivity between the device and the TFTP server by pinging the device from the Personal Computer that hosts the TFTP server. The ping program should show replies from the device. The TFTP server should be configured to transmit and receive files (on the Security tab under File > Configure), with no automatic shutdown or time-out (on the Auto-Close tab).
: The instructions listed above are based on the assumption that you are using the SolarWinds TFTP server; otherwise the configuration may vary. 6.2.2 Text Based Configuration (TBC) File Management Text Based Configuration (TBC) file is a simple text file that holds device template configurations. The device supports the TBC file in XML format which can be edited in any XML or text editors. You can generate the TBC file from the CLI Session and manually edit the configurations and then load the edited TBC file to the device so that the edited configurations are applied onto the device. It differs mainly from the binary configuration file in terms of manual edition of configurations. The generated TBC file is a template which has only the default and modified configurations on the live CLI session. 6.2.2.1 Generating TBC File The TBC file is generated through CLI by executing generate command. While generating the TBC file from CLI, there is an option to generate it with or without all Management and Security Passwords. The management passwords include Network-Secret/Encryption-Key(s)/RADIUS-Shared-Secret. If included, these passwords become a part of the generated TBC file and are in a readable form. If excluded, all these passwords are not part of the generated TBC file. include CLI/WEB/SNMP passwords. The security passwords The commands used for the generation of TBC file are:
T8000-00:00:01# generate tbc-with-pwds T8000-00:00:01# generate tbc-without-pwds The generated TBC file contains, Default configurations Any user-added or edited configurations on current live CLI session The generated Text Based Template Configuration file appears as shown below:
Tsunami 800 & 8000 Series - Software Management Guide 192 Management Figure 6-4 TBC File in xml Format 6.2.2.2 Editing the TBC File The TBC file can easily be opened and edited in any standard Text-Editors like Wordpad, MS-Word, Notepad++, Standard XML Editors. Proxim recommends XML Notepad 7 editor for editing the TBC file. You can modify any value between the double quotes() in the TBC file. It is recommended not to change the text outside the double quotes () or XML tags in the TBC file. Remove unchanged configurations from the TBC file before loading onto the device. Tsunami 800 & 8000 Series - Software Management Guide 193 Management 6.2.2.3 Loading the TBC file The TBC file can be loaded onto the device by using either SNMP, Web Interface or CLI. You can either use TFTP or HTTP to load the TBC file. By using Web Interface, you can load the TBC file by navigating to MANAGEMENT > File Management > Upgrade Configuration. To load the TBC file, it should be generated or downloaded onto the device. While loading the TBC file onto the device, any file name is accepted. Once loaded, the TBC file name is renamed to PXM-TBC.xml. If the TBC file does not contain correct XML syntax, the file will be discarded with DOM error and no configurations will be loaded. All duplicate values entered are considered as errors while loading and syslogs will be generated accordingly. Therefore, it is recommended to delete all unchanged parameters from the TBC file during its edition. Commit is required to retain the configurations across reboots after loading the TBC file.
: Both Commit and Reboot are required to accept the modifications done in the TBC File. Only reboot is required to reject the modifications. Loading the TBC file is allowed only once in an active device session (that is, if TBC file is loaded, reboot is required to apply all configurations or to load another TBC file). All configurations in the TBC file are loaded to the device irrespective of their default or modified or added configurations. Loading the TBC file takes approximately 10-20 seconds depending on the number of configurations added.
:
Remove any unmodified parameters from the TBC file, before loading it. If you get any timeout errors while loading TBC file from SNMP interface, increase the time-out value to more than 30 seconds in the MIB Browser. 6.2.3 Upgrade Firmware You can update the device with the latest firmware either through HTTP or TFTP.
:
Make sure the firmware being loaded is compatible to the device being upgraded. In a point-to-multipoint network, it is recommended to upgrade the base station first and then the subscriber(s). In a point-to-point network, it is recommended to upgrade the End Point A first and then the End Point B. 6.2.3.1 Upgrade Firmware via HTTP To upgrade the firmware via HTTP, do the following:
1. Navigate to MANAGEMENT > File Management > Upgrade Firmware > HTTP. Tsunami 800 & 8000 Series - Software Management Guide 194 Management Figure 6-5 Upgrade Firmware - HTTP 2. In the HTTP screen, click Browse to select the latest firmware file from the desired location. Ensure that the file name does not contain any space or special characters. 3. Click Upgrade. 6.2.3.2 Upgrade Firmware via TFTP To upgrade the firmware via TFTP Server, do the following:
1. Navigate to MANAGEMENT > File Management > Upgrade Firmware > TFTP. Figure 6-6 Upgrade Firmware - TFTP 2. Based on the IP mode configure either IPv4 or IPv6 address as TFTP Server address. 3. Enter the name of the latest firmware file (including the file extension) that has to be loaded onto the device in the File Name box. 4. To upgrade the device with new firmware click Upgrade and then reboot the device, or click Upgrade & Reboot.
:
After upgrading the device with the new firmware, reboot the device; Otherwise the device will continue to run with the old firmware. It is recommended not to navigate away from the upgrade screen, while the upgrade is in progress. Tsunami 800 & 8000 Series - Software Management Guide 195 If the device configuration is upgraded from the version 2.6.x to 3.0.x, with the channel bandwidth 5MHz, then the device boots up in the custom compatibility mode with 10ms timeframe. Management 6.2.4 Upgrade Configuration You can upgrade the device with the latest configuration files either through HTTP or TFTP.
: Make sure the configuration file being loaded into the device is compatible. That is, the configuration file being loaded should have been retrieved from a device of the same SKU. 6.2.4.1 Upgrade Configuration via HTTP To upgrade the configuration files by using HTTP, do the following:
1. Navigate to MANAGEMENT > File Management > Upgrade Configuration > HTTP. Figure 6-7 Upgrade Configuration - HTTP 2. 3. 4. 5. In the HTTP screen, click Browse to locate the configuration file. Select a Binary Configuration file or a Config Profile file, or a PXM-TBC.xml for Text Based Configuration file. Make sure that the file name does not contain any space or special characters. If you are upgrading the device with Binary Configuration file then click Upgrade and then reboot the device. If you are upgrading the device with Config Profile file then click Upgrade and then reboot the device. On upgrade, the device shall come up with the loaded profile. If the configuration profile is not compatible, then on reboot, the device will rollback to its old configuration. If you are upgrading the device with Text Based Configuration file then click Upgrade to upgrade the device with the config file and then click Load for loading the config file onto the device. Alternatively, you can perform both upgrade and load operation in one single step, by clicking Upgrade & Load. 6.2.4.2 Upgrade Configuration via TFTP To upgrade the configuration files by using TFTP Server, do the following:
1. Navigate to MANAGEMENT > File Management > Update Configuration > TFTP. Tsunami 800 & 8000 Series - Software Management Guide 196 Management Figure 6-8 Upgrade Binary Configuration via TFTP 2. You can update the device with three types of configuration files: Binary, Text Based and Config Profile. To update the device with Binary Configuration file, select Binary Config. Based on the IP mode configure either IPv4 or IPv6 address as TFTP Server address. Enter the name of the Binary file (including the file extension) that has to be downloaded onto the device in the File Name box. 3. To update the device with Text Based Configuration files, select Text Based Config. Based on the IP mode configure either IPv4 or IPv6 address as TFTP Server address. Enter the name of the Text Based file (including the file extension) that has to be downloaded onto the device in the File Name box. Figure 6-9 Upgrade Text Based Configuration via TFTP 4. To update the device with Configuration Profile files, select Config Profile. Based on the IP mode, configure either IPv4 or IPv6 address as TFTP Server address. Enter the name of the Config Profile file (including the file extension) that has to be downloaded onto the device in the File Name box. Tsunami 800 & 8000 Series - Software Management Guide 197 Management Figure 6-10 Upgrade Configuration Profile via TFTP 5. 6. 7. If you are upgrading the device with Binary Configuration file then click Upgrade and then reboot the device, or click Upgrade & Reboot. If you are upgrading the device with Text Based Configuration file, click Upload and then click Apply. If you are upgrading the device with Config profile file then click Upload and then reboot the device, or click Apply
& Reboot.
: It is recommended not to navigate away from the upgrade screen, while the upgrade is in progress. 6.2.5 Upgrade License You can upgrade the license file on the device either through HTTP or TFTP. Refer License Upgrade Procedure section for more details. 6.2.5.1 Upgrade License via HTTP To upgrade the license using HTTP, do the following:
1. Navigate to MANAGEMENT > File Management > Upgrade License > HTTP. Tsunami 800 & 8000 Series - Software Management Guide 198 Figure 6-11 Upgrade License via HTTP In the HTTP screen, click Browse to locate the license upgrade(.bin) file to be loaded on the device. 2. 3. Click Upgrade button to upgrade the license on the device and then reboot the device. 6.2.5.2 Upgrade License via TFTP To upgrade the license file using TFTP Server, do the following:
1. Navigate to MANAGEMENT > File Management > Update License > TFTP. Management Figure 6-12 Upgrade License via TFTP 2. Based on the IP mode, configure either IPv4 or IPv6 address as TFTP Server address. 3. Enter the name of the file (including the file extension) that has to be loaded on the device, in the File Name box. 4. Click Upgrade button to upgrade the license on the device and then reboot the device.
:
Upgrade license can be done through CLI/Web Interface/SNMP. License Upgrade for Bandwidth:
It is applicable only to MP-820-SUA-50+ and MP-825-SUR-50+ devices. Please refer to https://my.proxim.com/article/3003 to obtain license. After license upgrade and device reboot, please reconfigure the WORP input and output bandwidth limits as per the new licensed values; for more information, refer Input Bandwidth Limit and Output Bandwidth Limit. License Upgrade for WORP Sync Functionality:
For 82xx-G and 82x Series MP and QB devices, WORP sync is enabled on units produced till the end of 2014. After this time period, license has to be obtained to enable this functionality. Please contact customer support/SE for more details on how to obtain the license. 6.2.6 Retrieve From Device The Retrieve From Device tab allows you to retrieve logs, config files, and license info from the device either through HTTP or TFTP. 6.2.6.1 Retrieve from Device via HTTP To retrieve files from the device by using HTTP, do the following:
1. Navigate to MANAGEMENT > File Management > Retrieve from Device > HTTP. Tsunami 800 & 8000 Series - Software Management Guide 199 Management Figure 6-13 Retrieve Files via HTTP 2. Select the type of file that you want to retrieve from the device from the File Type drop down box. The files may vary depending on your device. The File Types are:
a. Config b. Event Log c. Temperature Log d. Text Based Template Config e. Debug Log f. Config Profile g. License Info The Config Profile is used for replicating the configuration of a master device on to other similar devices by excluding the unique parameters like System information, IP configuration, Ethernet configuration, Wireless configuration based on the selection. By default, System Information and IP Configuration parameters are excluded. On selecting config profile type the following screen appears:
Figure 6-14 Retrieve Config Profile File via HTTP Tsunami 800 & 8000 Series - Software Management Guide 200 After excluding the unique parameters, click Create Profile for creating the profile and then click Retrieve. When the retrieved configuration profile file is loaded on target devices, the target devices will come up with configuration of the master device except the excluded parameters. The excluded parameters are retained as configured on the target device. Management
: Config Profile is applicable only to the compatible devices. 3. Click Retrieve. Based on the selected file, the following Download screen appears. 4. Right-click the Download link and select Save Target As or Save Link As to save the file to the desired location. Figure 6-15 Download Screen 6.2.6.2 TFTP Retrieve To retrieve files from the device by using TFTP, do the following:
1. Navigate to MANAGEMENT > File Management > Retrieve from Device > TFTP. Figure 6-16 Retrieve Files via TFTP Tsunami 800 & 8000 Series - Software Management Guide 201 2. Based on the IP mode, configure either IPv4 or IPv6 address as TFTP Server address. 3. Enter the name of the file (including the file extension) that has to be retrieved from the device, in the File Name box. 4. Select the file type that you want to retrieve from the device, from the File Type drop down box. The file types are:
Management a. Config b. Event Log c. Temperature Log d. Text Based Template Config e. Debug Log f. Config Profile g. License Info The Config Profile is used for replicating the configuration of a master device on to other similar devices by excluding the unique parameters like System information, IP configuration, Ethernet configuration, Wireless configuration based on the selection. By default, System Information and IP Configuration parameters are excluded. On selecting config profile type the following screen appears:
Figure 6-17 Retrieve Config Profile File via TFTP After excluding the unique parameters, click Create Profile for creating the profile and then click Retrieve. When the retrieved configuration profile file is loaded on the target devices, the target devices will come up with configuration of the master device except the excluded parameters. The excluded parameters are retained as configured on the target device. 5. Click Retrieve. The retrieved file can be found in the TFTP Server folder.
:
Config Profile is applicable only to the compatible devices. Tsunami 800 & 8000 Series - Software Management Guide 202 When the device is running with default factory settings, there is no Binary Configuration file present and hence it cannot be retrieved. Similarly, the Text Based Template Configuration file does not exist if it is not generated from the CLI. You can retrieve Event Logs only when they are generated by the device. For more information on license upgrade, refer License Upgrade Procedure and Upgrade License sections. Management 6.3 Services The Services tab lets you configure the HTTP/HTTPS, Telnet/SSH and SNMP interface parameters. 6.3.1 HTTP/HTTPS To configure HTTP/HTTPS interface parameters, navigate to MANAGEMENT > Services > HTTP / HTTPS. Given below is the table which explains HTTP/HTTPS parameters and the method to configure the configurable parameter(s). Figure 6-18 HTTP/HTTPS Parameter Admin Password Description By default, the Administrator password to access HTTP/HTTPS interface is public. For security reasons, it is recommended to change the default password. The password should be alphanumeric with minimum of 6 and maximum of 32 characters.
: The following special characters are not allowed in the password:
- = \ ? / space Tsunami 800 & 8000 Series - Software Management Guide 203 Management Parameter Monitor Password Description The Administrator user has the privilege to change the Monitor user password. By default, the Monitor user password to access HTTP/HTTPS interface is public. For security reasons it is recommended to change the default password. The password should be alphanumeric with minimum of 6 and maximum of 32 characters. HTTP HTTP Port HTTPS
: The following special characters are not allowed in the password:
- = \ ? / space By default, a user can manage the device through Web Interface. To prevent access to the device through Web Interface, select Disable. Represents the HTTP port to manage the device through Web Interface. By default, the HTTP port is 80. By default, a user can manage the device through Web Interface over secure socket Layer
(HTTPS). To prevent access to the device through HTTPS, select Disable.
: The password configuration for HTTPS is same as configured for HTTP. After configuring the required parameters, click OK, COMMIT and then REBOOT. 6.3.2 Telnet/SSH To configure Telnet/SSH interface parameters, navigate to MANAGEMENT > Services > Telnet / SSH. Tsunami 800 & 8000 Series - Software Management Guide 204 Figure 6-19 Telnet/SSH Given below is the table which explains Telnet/SSH parameters and the method to configure the configurable parameter(s):
Management Parameter Admin Password Description By default, the Administrator password to access Telnet/SSH interface is public. For security reasons, it is recommended to change the default password. The password should be alphanumeric with minimum of 6 and maximum of 32 characters.
: The following special characters are not allowed in the password:
- = \ ? / space Monitor Password The Administrator user has the privilege to change the Monitor user password. By default, the Monitor user password to access Telnet/SSH interface is public. For security reasons it is recommended to change the default password. The password should be alphanumeric with minimum of 6 and maximum of 32 characters. Telnet Telnet Port Telnet Sessions SSH SSH Port SSH Sessions
: The following special characters are not allowed in the password:
- = \ ? / space By default, a user can manage the device through Telnet. To prevent access to the device through Telnet, select Disable. Represents the port to manage the device using Telnet. By default, the Telnet port is 23. The number of Telnet sessions which controls the number of active Telnet connections. A user is restricted to configure a maximum of 3 Telnet sessions. By default, the number of Telnet sessions allowed is 2. By default, a user can manage the device through SSH. To prevent access to the device through SSH, select Disable. Represents the port to manage the device using Secure Shell. By default, the Secure Shell port is 22. Represents the number of SSH sessions which controls the number of active SSH connections. A user is restricted to configure a maximum of 3 SSH sessions. By default, the number of SSH sessions allowed is 1.
: The total number of CLI sessions allowed is 3, so the sum of Telnet and SSH sessions cannot be more than 3. For example, if you configure the number of Telnet sessions as 2, then the number of SSH sessions can only be a value 0 or 1. After configuring the required parameters, click OK, COMMIT and then REBOOT. 6.3.3 SNMP To configure SNMP interface parameters, navigate to MANAGEMENT > Services > SNMP. Tsunami 800 & 8000 Series - Software Management Guide 205 Management Figure 6-20 SNMPv1-v2c Tsunami 800 & 8000 Series - Software Management Guide 206 Figure 6-21 SNMPv3 Management Given below is the table which explains SNMP parameters and the method to configure the configurable parameter(s):
Parameter SNMP By default, the user has the access to manage the device through SNMP Interface. To prevent access to the device through SNMP, select Disable. Description
: Any change in the SNMP status will affect the Network Management System access. Version Allows you to configure the SNMP version. The supported SNMP versions are v1-v2c and v3. By default, the SNMP version is v1-v2c. SNMP v1-v2c Specific Parameters Read Password Represents the read only community string used in SNMP Protocol. It is sent along with each SNMP GET / WALK / GETNEXT / GETBULK request to allow or deny access to the device. This password should be same as read password set in the NMS or MIB browser. The default password is public. The password should be of minimum 6 and maximum 32 characters. Read/Write Password
: The following special characters are not allowed in the password:
- = \ ? / space Represents the read-write community string used in SNMP Protocol. It is sent along with each SNMP GET / WALK / GETNEXT / SET request to allow or deny access to the device. This password should be same as read-write password set in the NMS or MIB browser. The default password is public. The password should be of minimum 6 and maximum 32 characters.
: The following special characters are not allowed in the password:
- = \ ? / space SNMP v3 Specific Parameters Security level The supported security levels for the device are AuthNoPriv and AuthPriv. Select AuthNoPriv for Extensible Authentication or AuthPriv for both Authentication and Privacy (Encryption). Priv Protocol Applicable only when the Security Level is set to AuthPriv. Represents the type of privacy (or encryption) protocol. Select the encryption standard as either AES-128 (Advanced Encryption Standard) or DES (Data Encryption Standard). The default Priv Protocol is AES-128.
: The following special characters are not allowed in the password:
- = \ ? / space Tsunami 800 & 8000 Series - Software Management Guide 207 Management Parameter Description Priv Password Applicable only when the Security Level is set to AuthPriv. Represents the pass key for the selected Privacy protocol. The default password is public123. The password should be of minimum 8 and maximum 32 characters.
: The following special characters are not allowed in the password:
- = \ ? / space Auth Protocol Represents the type of Authentication protocol. Select the encryption standard as either SHA (Secure Hash Algorithm) or MD5 (Message-Digest algorithm). The default Auth Protocol is SHA. Auth Password Represents the pass key for the selected Authentication protocol. The default password is public123. The password should be of minimum 8 and maximum 32 characters. After configuring the required parameters, click OK, COMMIT and then REBOOT. 6.3.3.1 SNMP Trap Host Table The SNMP Trap Host table allows you to add a maximum of 5 Trap servers IP address to which the SNMP traps will be delivered. By default, the SNMP traps are delivered to 169.254.128.133.
: The default SNMP Trap Host Table entry cannot be deleted. To add entries to the Trap Host Table, click Add in the Services screen. The SNMP Trap Host Table Add Row screen appears:
Figure 6-22 Add Entries to SNMP Host Table Configure the following parameters:
IP Address: Based on the IP mode, enter the IPv4 or IPv6 address of the Trap server to which SNMP traps will be delivered.
: IPv6 address should be the global IP address and not the link local IP address. Tsunami 800 & 8000 Series - Software Management Guide 208 Password: Type the password to authenticate the Trap Server. The following special characters are not allowed in the password: - = \ ? / space Management
: Applicable only to SNMP v1-v2c. Comment: Type comments, if any. Entry Status: Select the entry status as either Enable or Disable. If enabled, the device will send SNMP traps to the authenticated Trap Server. After configuring the required parameters, click Add and then COMMIT. 6.3.3.2 Edit SNMP Trap Host Table Edit the desired SNMP Trap Host Table entries and click OK, COMMIT and then REBOOT. 6.3.4 Logs The device supports two types of log mechanisms:
1. Event Log: Based on the configured event log priority, all the log messages are logged and used for any analysis. This log messages remain until they are cleared by the user. 2. Syslog: They are similar to Event logs except that they are cleared on device reboot. To configure Event log and Syslog priority, navigate to MANAGEMENT > Services > Logs. The following screen appears:
Figure 6-23 Logs Event Log Priority: By default, the priority is set to Notice. You can configure the event log priority as one of the following:
Emergency Alert Critical Error Warning Notice Tsunami 800 & 8000 Series - Software Management Guide 209 Management Info Debug Please note that the priorities are listed in the order of their severity, where Emergency takes the highest severity and Debug the lowest. When the log priority is configured as high, all the logs with low priority are also logged. For example, if Event Log Priority is set to Notice, then the device will log all logs with priorities Notice, Warning, Error, Critical, Alert and Emergency. Syslog Status: By default, Syslog Status is enabled and default priority is Critical. If desired, you can choose to disable. Syslog Priority: Configuration is same as Event Log Priority. After configuring the required parameters, click OK and then COMMIT. 6.3.4.1 Configure a Remote Syslog host Configure a syslog host (server) in order to forward syslog messages to it.
: You can configure only one syslog host. Follow the following steps to configure a remote syslog host:
1. Click Add in the Syslog Host Table screen. The Syslog Host Table Add Row screen appears:
2. IP Address: Based on the IP mode, enter IPv4 or IPv6 address of the Syslog host. Figure 6-24 Syslog Host Table Add Row
: IPv6 address should be the global IP address and not the link local IP address. 3. Host Port: Represents the port on which the Syslog host listens to the log messages sent by the device. The default port is 514.
: The user must configure the correct port number on which the Syslog host is running. Choice of port number must be in line with the standards for port number assignments defined by Internet Assigned Numbers Authority (IANA). 4. Comments: Types comments, if any. 5. Click Add. The syslog host is added to the Syslog Host Table. Tsunami 800 & 8000 Series - Software Management Guide 210 Management For some reason, if the configured syslog host parameters are changed then you can edit it directly in the Syslog Host Table entry. You can change the following parameters:
Figure 6-25 Syslog Host Configured IP Address Port Host Comments Entry Status:
Enable: By default, the configured Syslog host is enabled on the device. Disable: To disable an entry in the Syslog Host Table, click Disable. Delete: To delete the configured Syslog host, click Delete. After doing the necessary changes, click OK followed by COMMIT. 6.4 Simple Network Time Protocol (SNTP) Proxims point-to-multipoint and point-to-point devices are furnished with Simple Network Time Protocol (SNTP) Client software that enables to synchronize devices time with the network time servers. The SNTP Client when enabled on the device(s), sends an NTP (Network Time Protocol) request to the configured time servers. Upon receiving the NTP response, it decodes the response and sets the received date and time on the device after adjusting the time zone and day light saving. In case, the time servers are not available, then users also have the option to manually set the date and time on the device. To synchronize devices time with time servers or manually set the time, navigate to MANAGEMENT > SNTP. The SNTP screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 211 Management Given below is the table which explains SNTP parameters and the method to configure the configurable parameter(s):
Figure 6-26 Time Synchronization Parameter Enable SNTP Status Select this parameter to enable SNTP Client on the device. If enabled, the SNTP Client tries to synchronize the devices time with the configured time servers. Description By default, the SNTP status is disabled. Primary Server IP Address/Domain Name Enter the host name, or the IP address based on IP modes (IPv4 only or IPv4 and IPv6) of the primary SNTP time server. The SNTP Client tries to synchronize devices time with the configured primary server time.
:
If host name is configured, instead of IP address then make sure that DNS server IP is configured on the device. IPv6 address should be the global IP address and not the link local IP address. Secondary Server IP Address/Domain Name Enter the host name, or the IP address based on IP modes (IPv4 only or IPv4 and IPv6) of the secondary SNTP time server. If the primary server is not reachable, then SNTP client tries to synchronize devices time with the secondary server time.
:
If the SNTP client is not able to sychronize the time with both the servers
(primary and secondary), then it tries to synchronize again after every one minute. IPv6 address should be the global IP address and not the link local IP address. Tsunami 800 & 8000 Series - Software Management Guide 212 Management Parameter Time Zone Day Light Saving Time Description Configure the time zone from the available list. This configured time zone is considered before setting the time, received from the time servers, on the device. Configure the Day Light Saving time from the available list. This configured Day Light Saving time is considered before setting the time, received from the time servers, on the device. ReSync Interval Set ReSync time interval ranging from 0 to 1440 minutes. Once the time is synchronized, the SNTP Client tries to resynchronize with the time servers after every set time interval. Sync Status By default, the ReSync interval is set to 60 minutes. Specifies the SNTP Client sync status when it tries to ReSync again with the time servers. The status is as follows:
Disabled: The SNTP client will not synchronize the time with the time servers and displays the status as Disabled. Synchronizing: The SNTP client is in the process of synchronzing time with the time servers. Synchronized: The SNTP client has synchronized time with the time servers. Current Date/Time Displays the current date and time. If SNTP is enabled, it displays the time the device received from the SNTP server. If SNTP is not enabled, then it displays the time manually set by the user. Manual Time Configuration If SNTP Client is disabled on the device or the time servers are not available on the network, then the user can manually set the time. Enter the time manually in the format:
MM-DD-YYYY HH:MM:SS.
:
Manual time configuration is not retained across reboots. After every reboot the user has to set the time again. Over a period of time, with manual time configuration, the device may lag behind the actual time. So, it is recommended to periodically check and adjust the time. To save the configured parameters, click OK and then COMMIT. 6.5 Access Control The Access Control tab enables you to control the device management access through specified host(s). You can specify a maximum of five hosts to control device management access. To configure management access control parameters, navigate to MANAGEMENT > Access Control. The Management Access Control screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 213 Management Figure 6-27 Management Access Control By default, the Management Access Control feature is disabled on the device. To enable, select Enable from the Access Table Status box and click OK. Reboot the device, for the changes to take effect.
: Only when the Access Table Status is enabled, you can add host(s) to the Management Access Control Table. 6.5.0.1 Add Host(s) to Management Access Control Table To add a host to the Management Access Control Table, do the following:
1. Click Add in the Management Access Control screen. The Management Access Table Add Row screen appears:
Figure 6-28 Management Access Table Add Row 2. IP Address: Based on the IP mode, configure either IPv4 or IPv6 address of the host that controls the device management access. 3. Entry Status: By default, the entry status is enabled meaning which the specified host can control the device management access. Edit the status to Disable, if you do not want the host to control the device management access. 4. Click Add.
: If MAC ACL is enabled, configure at least one entry in the Management Access Table with the IP address (of the PC or the management station), in order to manage the device. 6.5.0.2 Edit Management Access Control Table Entries Edit the desired host entries and click OK, COMMIT and then REBOOT. Tsunami 800 & 8000 Series - Software Management Guide 214 6.6 Reset to Factory The Reset to Factory tab allows you to reset the device to its factory default state. When this operation is performed, the device will reboot automatically and comes up with default configurations. To reset the device to its factory defaults, navigate to MANAGEMENT > Reset To Factory. The Factory Reset screen appears:
Management Click OK, if you wish to proceed with factory reset, else click Cancel. Figure 6-29 Reset to Factory Defaults 6.7 Convert QB to MP The Convert QB to MP tab lets you convert a QB to SU so that the converted device can connect to a BSU and operate as a SU. This feature is applicable only to, QB-8200-EPA-G/QB-8200-EPA which converts to a MP-8200-SUA QB-8250-EPR-G/QB-8250-EPR which converts to a MP-8250-SUR You can convert a QB to SU mode by using two methods:
Method 1: Web Interface Method 2: Load an SU config file (retrieved from another SU) onto the QB device and then reboot.
: Even after conversion from QB to MP, the device description still shows as QB. To convert a QB to SU using Web Interface, do the following:
1. Navigate to MANAGEMENT > Convert QB to MP. The Convert QB to MP screen appears:
Figure 6-30 Convert QB to MP 2. Click OK.
:
A QB after converting to SU will function in SU mode only. It will accept only MP firmware for upgrade. Tsunami 800 & 8000 Series - Software Management Guide 215 The version of the firmware being upgraded to should be 2.4.0 or later. If earlier version of the firmware is loaded, the device will reset to factory default upon initialization and operate in QB mode. When upgrading a converted device from Bootloader, it must be done using a QB image, as the device is licensed as QB. The conversion of the device from QB to SU requires a reboot. In case of Method 1 (Web Interface) conversion, QB mode configuration will be deleted. Reset to factory defaults, always results in the device initializing in QB mode. Management 6.8 Auto Config Recovery This feature enables a QB device to fall back to the last successful link configuration when it fails to establish connection with its peer.
:
It is applicable only to QB-825-EPR/LNK-50+, QB-825-EPR/LNK-100, QB-835-EPR/LNK-25, QB-835-EPR/LNK-50 and QB-82xx Series. By default, it is disabled on End Point A and enabled on End Point B. It is started either during device initialization or on COMMIT success. The detailed explanation of the feature is given below:
On successful COMMIT/ device initialization, the WORP link status is checked after the Auto Config Recovery Delay time expires. If the WORP link is established, then the device saves the current configuration as the last successful link configuration. If the WORP link is not established, the device will fall back to the last successful link configuration (only if available) and reboot. If the WORP link is still not established after the auto config recovery delay time expires, the device will fall back to auto config recovery defaults. The Auto Config Recovery Defaults vary from the Factory Reset Defaults by the following four parameters:
Parameter Description Network Name Represents the current network name of the device. Auto Config Recovery Feature Status This parameter is Enabled. IP Address Radio Mode For End Point B (EPB), the IP address is 169.254.128.131. For End Point B (EPB), this parameter will come up as EPB only on fallback to auto config recovery defaults To enable this feature on End Point A/ B, navigate to Management> Auto Config Recovery. In the following screen, Enable the Auto Config Recovery Status using the drop-down menu and click OK. Tsunami 800 & 8000 Series - Software Management Guide 216 Management Next, enter the Auto Config Recovery Delay as shown in the following screen. By default, it is set to 120 seconds, but the configurable value ranges from 30 300 seconds. Figure 6-31 Auto Config Recovery
: If ACS is enabled, irrespective of the auto config recovery delay configured time, an extra 3 Minutes is added to the delay. Figure 6-32 Auto Config Recovery Click OK and then COMMIT.
:
If the Recovery delay time expires during the firmware upgrade, then the Auto Config Recovery functionality is not triggered. During the primary testing/ deployment, it is recommended to Disable this feature at both ends of the link and Enable it after the successful establishment of WORP link. This feature does not impact the last known good configuration which is used in case of configuration corruption. If the configured channel is DFS channel, then Recovery Delay starts after the CACT process is completed. Tsunami 800 & 8000 Series - Software Management Guide 217 Monitor 7 This chapter contains information on how to monitor the device by using Web interface. It contains information on the following:
Active VLAN Bridge System Interface Statistics WORP Statistics Network Layer RADIUS (BSU or End Point A only) IGMP DHCP Logs Tools SNMP v3 Statistics 7.1 System
: 'System' section is applicable only to 82x devices. For 82x devices, the System tab enables you to view system specific information namely LED/RSSI Display when Sync/RSSI is enabled in LED Display Status. To configure the LED Display Status, navigate to Advanced Configuration > System and select any one of the configurable values: Disable, RSSI, and Sync. Refer, LED Status for more details. 7.1.1 RSSI LED Behavior When the link is established, the Received Signal Strength Indicator (RSSI) LEDs on the scaling mask glow. Scaling mask LEDs indicate the received signal strength of the link. The more LEDs on the scaling mask glow, better is the signal. By default, RSSI Display mode is enabled, if required the user can select the Disable (LEDs Off) mode. In Disable (LEDs Off) mode, all the 5 LEDs will be off.
: 'RSSI LED' feature is applicable only to 82x devices. To view RSSI, navigate to MONITOR > System. The LED/RSSI Display screen appears as shown below. Figure 7-1 LED/RSSI Display (RSSI) Tsunami 800 & 8000 Series - Software Management Guide 218 Monitor The LED behavior in RSSI Display mode is given below:
By default all the 5 LEDs will blink for an interval of 1 second to indicate the device is UP. For a BSU, in order to monitor the SU link statistics, the user should first configure the wireless MAC address of the SU. If the configured SU is registered with the BSU, then the LEDs will glow based on the RSSI value else all the 5 LEDs will blink. For a SU, if the SU is registered with the BSU, then the LEDs will glow based on the RSSI value else all the 5 LEDs will blink. For a CPE, if the CPE is registered with the BSU, then the LEDs will glow based on the RSSI value else all the 5 LEDs will blink. For QB, if EndPointA is registered with EndPointB, then the LEDs will glow based on the RSSI value of each EndPoint. else all the 5 LEDs will blink. 7.1.2 Sync LED Behavior If Sync mode is enabled, the third LED behavior of the scaling mask will indicate the Sync status. To view the Sync status, navigate to Monitor > System. The LED/RSSI Display screen appears as shown below. The LED behavior in Sync mode is described and tabulated below. Figure 7-2 LED/RSSI Display (Sync) Sync LED Behavior Sync Status OFF (Grey) Synchronous mode is disabled or the device is out of Sync Blinking (Green-Fast) Synchronous mode is enabled, but Sync signal is not received ON (Solid-Green) Synchronous mode is enabled and Sync signal is received 7.2 Interface Statistics Interface Statistics allows you to monitor the status and performance of the Ethernet and Wireless interfaces of the device. 7.2.1 Ethernet Statistics To view the Ethernet interface statistics, click MONITOR > Interface Statistics. The Interface Statistics screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 219 Monitor Figure 7-3 Ethernet Interface Statistics To view Ethernet statistics, click Ethernet 1 or Ethernet 2 depending on the Ethernet interfaces supported by your device. Given below is the table which explains the parameters displayed in the Ethernet Statistics screen:
Parameter MTU Description Specifies the largest size of the data packet received or sent on the Ethernet interface. The MTU size varies from 1500 to 1514 depending on the MTU configuration (See System). MAC Address Specifies the MAC address at the Ethernet protocol layer. Operational Status Specifies the current operational state of the Ethernet interface. In Octets Specifies the total number of octets received on the Ethernet interface. In Unicast Packets Specifies the number of subnetwork- unicast packets delivered to the higher level protocol. In Non-unicast Packets Specifies the number of non-unicast subnetwork packets delivered to the higher level protocol. In Errors Out Octets Out Packets Out Discards Specifies the number of inbound packets that contained errors and are restricted from being delivered. Specifies the total number of octets transmitted out from the Ethernet interface. Specifies the total number of packets requested by the higher level protocol and then, transmitted. Specifies the number of error-free outbound packets chosen to be discarded to prevent them from being transmitted. One possible reason for discarding such a packet could be to free up buffer space. Tsunami 800 & 8000 Series - Software Management Guide 220 Monitor Parameter Description Out Errors Specifies the number of outbound packets that are not transmitted because of errors. To view the updated Ethernet statistics, click Refresh. To delete the Ethernet statistics, click Clear. 7.2.2 Wireless Statistics To view the Wireless interface statistics, click MONITOR > Interface Statistics > Wireless1. Figure 7-4 Wireless Interface Statistics Tsunami 800 & 8000 Series - Software Management Guide 221 Monitor Given below is the table which explains the parameters displayed in the Wireless statistics screen:
Parameter MTU Description Specifies the largest size of the data packet received or sent on the wireless interface. The MTU size can range from 350 to 3808 bytes for High throughput modes and 350 to 2304 bytes for legacy mode. The default and maximum value of the WORP MTU is 3808 bytes for higher throughput and 2304 bytes for legacy mode. MAC Address Specifies the MAC address at the wireless protocol layer. Operational Status Specifies the current operational state of the wireless interface. In Octets In Packets In Errors Out Octets Out Packets Out Discards Out Errors Retunes Specifies the total number of octets received on the wireless interface. Specifies the number of packets delivered to the higher level protocol. Specifies the number of inbound packets that contained errors and are restricted from being delivered. Specifies the total number of octets transmitted out from the wireless interface. Specifies the total number of packets requested by the higher level protocol and then, transmitted. Specifies the number of error-free outbound packets chosen to be discarded to prevent them from being transmitted. One possible reason for discarding such a packet could be to free up buffer space. Specifies the number of outbound packets that are not transmitted because of errors. Specifies the number of times the radio is re-tuned for better performance of the device. Max Tx Power Indicates the maximum power that the radio can radiate. SNR Statistics represents the signal strength with regard to the noise at the antenna ports. SNR Statistics Antenna Status Control Extension Decrypt Errors CRC Errors PHY Errors Specifies the antenna ports available for the product. Please note that the antenna ports vary depending on the product. Specifies the configuration status of the antenna ports. ON indicates that antenna port is enabled and OFF indicates that antenna port is disabled. Specifies the SNR value of the packet received at the selected channel frequency. This parameter is applicable only to the 40 MHz modes, that is, 40 PLUS and 40 Minus. It specifies the SNR value of the packet received on the extension channel (20MHz). Rx Error Details This parameter is applicable only if security is enabled. It indicates the number of received packets that failed to decrypt. Specifies the number of received packets with invalid CRC. Specifies the total Rx PHY Errors. It generally indicates the interference in the wireless medium. Collisions Specifies the total numbers of collisions occurred. Tsunami 800 & 8000 Series - Software Management Guide 222 To view the updated Wireless statistics, click Refresh. To delete the Wireless statistics, click Clear. 7.2.3 PPPoE Statistics
: Applicable only to an SU in Routing mode. To view PPPoE interface statistics, navigate to MONITOR > Interface Statistics > PPPoE > PPP Interface Stats. Monitor The PPPoE interface parameters are same as the Ethernet interface parameters. Please note that if a link is not established between a PPPoE client and server, then the device displays the following message. Figure 7-5 PPPoE Interface Statistics Figure 7-6 PPPoE Server - No Link Established To view the updated PPPoE interface statistics, click Refresh. Please note that for every 4 seconds, the interface statistics gets refreshed. To view the PPPoE connection status such as the number of attempts made to start a session between PPPoE client and server, and the number of attempts failed to establish a connection, click PPPoE Connection Stats. Tsunami 800 & 8000 Series - Software Management Guide 223 Monitor Figure 7-7 PPPoE Connection Statistics To view updated connection statistics, click Refresh. To restart the session between the PPPoE client and server, click Restart PPPoE Session. On successfully re-establishing a session, the IP address of the wireless interface will be assigned again by the PPPoE server, if Address Type is set to PPPoE-ipcp. To clear the existing connection statistics, click Clear. 7.2.4 IP Tunnels
: Applicable only in Routing Mode. To view IP Tunnels interface statistics, click MONITOR > Interface Statistics > IP Tunnels. The following IP Tunnel Interface Statistics screen appears:
Given below is an explanation to each of these parameters:
Figure 7-8 IP Tunnels Interface Statistics Parameter Name Alias Maximum Transmission Unit
(MTU) Description Specifies the tunnel interface name. Specifies the supplementary tunnel interface name. Specifies the largest size packet or frame that can be sent over the tunnel interface. The MTU of the tunnel interface is derived from the underlying interface:
For IP-IP tunnel interface: MTU = Underlying interface MTU 20 bytes (IP header) For IP-GRE interface: MTU = Underlying interface MTU 24 bytes (IP header + gre protocol) Tsunami 800 & 8000 Series - Software Management Guide 224 Monitor Parameter Operational Status The Operational Status indicates only the tunnel interface status. The status can be either UP or DOWN. Description
: For the tunnel to function correctly both ends should be configured correctly. Details Provides a more detailed statistics about the tunnel interface. To view the detailed statistics, click
. Figure 7-9 Detailed IP Tunnels Interface Statistics The detailed tunnel interface parameters are similar to the Ethernet Interface Statistics. Please refer to Ethernet Statistics. 7.3 WORP Statistics 7.3.1 General Statistics WORP General Statistics provides general statistics about the WORP. To view General Statistics, navigate to MONITOR > WORP Statistics > Interface 1 > General Statistics. The following WORP General Statistics screen appears. Tsunami 800 & 8000 Series - Software Management Guide 225 Monitor Figure 7-10 WORP General Statistics (SU/End Point A/End Point B) Figure 7-11 WORP General Statistics (BSU) Tsunami 800 & 8000 Series - Software Management Guide 226 7.3.1.1 Basic Statistics Given below is an explanation to the basic parameters:
Monitor Parameter Description Interface Type Specifies the type of radio interface. WORP Protocol Version Specifies the version of the WORP Protocol used. This information is useful to the customer support team for debugging purpose only. WORP Data Messages Specifies the sent or received data frames through wireless interface. Refers to the number of polls with data messages sent or received. Refers to the number of polls with no data messages sent or received. Refers to the number of poll replies with data messages sent or received. Poll Data Poll No Data Reply Data Reply More Data Refers to the number of poll replies with more data messages sent or received. Reply No Data Poll No Replies Refers to the number of poll replies with no data messages sent or received. Refers to the number of times the poll messages are sent by a BSU/End Point A and received no reply from SU/End Point B. This parameter is applicable only to a BSU. Specifies the number of transmissions occurred through the interface. Data Transmission Statistics Send Success Send Retries Send Failures Refers to the number of data messages sent and acknowledged by the peer successfully. Refers to the number of data messages that are re-transmitted and acknowledged by the peer successfully. Refers to the number of data messages that are not acknowledged by the peer even after the specified number of retransmissions. Receive Success Refers to the number of data messages received and acknowledged successfully. Receive Retries Refers to the number of successfully received re-transmitted data messages. Receive Failures Refers to the number of data messages that were not received successfully. Registration Details Specifies the status of the entire registration process. Remote Partners Refers to the number of remote partners. For an SU/End Point A/End Point B, the number of remote partners is always zero or one. Announcements Refers to the number of Announcement messages sent or received on WORP interface. Request For Service Refers to the number of requests for service messages sent or received. Registration Requests Refers to the number of registration request messages sent or received on WORP interface. Registration Rejects Refers to the number of registration reject messages sent or received on WORP interface. Authentication Requests Refers to the number of authentication request messages sent or received on WORP interface. Tsunami 800 & 8000 Series - Software Management Guide 227 Monitor Parameter Description Authentication Confirms Refers to the number of authentication confirm messages sent or received on WORP interface. Registration Attempts Refers to the number of times a registration attempt has been initiated. Registration Incompletes Refers to the number of registration attempts that are not yet completed. Registration Timeouts Refers to the number of times the registration procedure timed out. Registration Last Reason Refers to the reason for the last registration getting aborted or failed.
: For better results, the Send Failure or Send Retrieve must be low in comparison to Send Success. The same applies for Receive Retries or Receive Failure. Click Clear to delete existing general statistics. Click Refresh to view updated WORP general statistics. 7.3.1.2 Advanced Statistics Advanced statistics is applicable only to the BSU. The Advanced Statistics screen displays the wireless transmission values used by the BSU to send announcement and broadcast messages. Given below is an explanation to the advanced parameters:
Figure 7-12 WORP Advanced Statistics Parameter Description Tx Rate Displays the Data Transmission Rate used by the BSU. Data Stream Displays the Data Streams used by the BSU. Tsunami 800 & 8000 Series - Software Management Guide 228 Parameter Description TPC EIRP Power Displays the TPC value currently applied by the device to adjust the transmit power radiated by the radio. Displays the current EIRP that a radio antenna radiates (after applying the TPC). Displays the current transmit power radiated by the radio (after applying the TPC). Tx Antenna Ports Indicates the status of the antenna ports at the BSU end. Monitor Click Refresh to view updated WORP advanced statistics. 7.3.2 Link Statistics 7.3.2.1 SU / End Point B Link Statistics
: SU Link Statistics is applicable only to a BSU, and End Point B Link Statistics is applicable only to a End Point A device. SU Link statistics provides information about the SUs connected to a BSU. Similarly, End Point B Link Statistics provides information about an End Point B currently connected to an End Point A device. To view link statistics, navigate to MONITOR > WORP Statistics > Interface 1 > SU Link Statistics. Given below is an explanation to each of these parameters:
Figure 7-13 An Example - SU Link Statistics Parameter SU Name/
End Point B Name MAC Address Represents the name of the SU/End Point B connected to a BSU/End Point A respectively. Description Represents the MAC address of the SU/End Point B connected to a BSU/End Point A respectively. Local Tx Rate (Mbps) Represents the data transmission rate at the local (current device) end. Tsunami 800 & 8000 Series - Software Management Guide 229 Parameter Remote Tx Rate
(Mbps) Represents the data transmission rate at the remote (peer) end. Description Local Tx Antenna Port Info Indicates the status of the antenna ports at the transmitting end. The following symbols indicate the status of the antenna ports. Monitor Indicates the antenna port is disabled. Indicates the antenna port is enabled and signal is present. Local Rx Antenna Port Info Indicates the status of the antenna ports at the receiving end. The following symbols indicate the status of the antenna ports. Indicates the antenna port is disabled. Indicates the antenna port is enabled and signal is present. Local Signal (dBm) Represents the signal level with which the device at the local end receives frames from the device at the remote end, through wireless medium. Local Noise (dBm) Represents the noise measured at the local end antenna ports. Local SNR (dB) Represents the SNR measured by the receiver at the local end and is based on the Local Signal and Local Noise. Remote Rx Antenna Port Info Indicates the status of the remote end antenna ports. The antenna ports status is same as explained in Local Antenna Port Info. Remote Signal (dBm) Represents the signal level with which the device at the remote end receives frames, through wireless medium. Remote Noise (dBm) Represents the noise measured at the remote end antenna ports. Remote SNR (dB) Current Tx Power
(dBm) Represents the SNR measured by the receiver at the remote end and is based on the Remote Signal and Remote Noise. TPC: Displays the TPC value currently applied by the device to adjust the transmit power radiated by the radio antenna.
: For a given data rate, if the configured TPC value is greater than the maximum transmit power supported by the radio then maximum transmit power supported by radio value is applied. EIRP: Displays the current EIRP that a radio antenna radiates (after applying the TPC). Power: Displays the current transmit power radiated by the radio (after applying the TPC). Click Refresh to view updated link statistics. Tsunami 800 & 8000 Series - Software Management Guide 230 To view detailed SU/End Point B Link statistics, click Details icon following screen appears depending on your device:
in the SU/End Point B Link Statistics screen. The Monitor Figure 7-14 An Example - SU Detailed Statistics The detailed page displays Remote SNR information, that is, the Minimum Required SNR and the Maximum Optimal SNR value for a given data rate or modulation, to achieve optimal throughput. To disconnect an SU/End Point B from BSU/End Point A respectively, click Disconnect. To view updated detailed statistics, click Refresh. Tsunami 800 & 8000 Series - Software Management Guide 231 on the top-right corner of SU/End To view the local SNR table, there is an option as Point B Link Statistics screen. you can also refer An Example - SU Link Statistics for more details. The following screen appears depending on your device:
Monitor These configured values are used by ATPC and DDRS to derive TPC and data rate for optimal throughput. Figure 7-15 An Example - Local SNR Information 7.3.2.2 BSU/End Point A Link Statistics
: BSU Link Statistics is applicable only to an SU, and End Point A Link Statistics is applicable only to an End Point B device. BSU Link statistics provides information about the BSU to which SUs are connected. Similarly, End Point A Link Statistics provides information about an End Point A currently linked to an End Point B device. Tsunami 800 & 8000 Series - Software Management Guide 232 Monitor Figure 7-16 An Example - BSU Link Statistics To access the Radio Link Test Tool, navigate to MONITOR > WORP Statistics > Interface 1 > SU/BSU Link Statistics > Details. Click
. The SU/BSU WORP Detailed Statistics screen appears. In this screen, click the Radio Link Test button. For detailed description of this tool, refer Radio Link Test Tool. 7.3.3 QoS Statistics (BSU or End Point A Only)
: This parameter is applicable only to BSU or End Point A radio modes. To view QoS Statistics, navigate to MONITOR > WORP Statistics > Interface 1 > QoS Statistics. The following QoS Summary screen appears. This screen shows the total, minimum and maximum bandwidth allocated per BSU/End Point A, and the minimum and maximum bandwidth allocated for each SU/End Point B registered with the BSU/End Point A respectively. Figure 7-17 QoS Summary Tsunami 800 & 8000 Series - Software Management Guide 233 7.4 Active VLAN Monitor
: Active VLAN is applicable only to a device in SU (Bridge) mode. The Active VLAN page enables you to identify the VLAN Configuration mode applied on a device in SU mode. To view active VLAN applied on the device in SU mode, navigate to MONITOR > Active VLAN. The Active VLAN page appears:
Figure 7-18 Active VLAN The Active VLAN Config parameter helps you to identify the current VLAN configuration applied on the device in SU mode. Local: VLAN configuration is done locally from the device. Remote: VLAN configuration is done through RADIUS Server. This page also displays the VLAN parameters and their values that are configured either locally or remotely. To view active VLAN Ethernet Configuration, navigate to MONITOR > Active VLAN > Ethernet. The Active VLAN Ethernet Configuration page appears:
This page displays the VLAN Ethernet parameters and their values that are configured either locally or remotely. Figure 7-19 Active VLAN Ethernet Configuration
: Please note that the number of Ethernets vary depending on the device. Tsunami 800 & 8000 Series - Software Management Guide 234 7.5 Bridge 7.5.1 Bridge Statistics The Bridge Statistics allows you to monitor the statistics of the Bridge. To view the Bridge Statistics, navigate to MONITOR > Bridge > Bridge Statistics. The following Bridge Statistics screen appears:
Monitor The following table lists the parameters and their description:
Figure 7-20 Bridge Statistics Parameter Description Description This parameter provides a description about the bridge. MTU Represents the largest size of the data packet sent on the bridge. MAC Address Represents the MAC address at the bridge protocol layer. Operational Status Represents the current operational status of the bridge: UP (ready to pass packets) or DOWN (not ready to pass packets). In Octets Represents the total number of octets received on the bridge interface, including the framing characters. In Unicast Packets Represents the number of unicast subnetwork packets delivered to the higher level protocol. In Non-unicast Packets Represents the number of non-unicast subnetwork packets delivered to the higher level protocol. In Errors Represents the number of inbound packets with errors and that are restricted from being delivered. Tsunami 800 & 8000 Series - Software Management Guide 235 Monitor Parameter Description Out Octets Out Packets Out Discards Out Errors Represents the total number of octets transmitted out of the bridge, including the framing characters. Represents the total number of packets requested by higher-level protocols to be transmitted out of the bridge interface to a sub-network address, including those that were discarded or not sent. Represents the number of error-free outbound packets which are discarded to prevent them from being transmitted. One possible reason for discarding such a packet could be to free up buffer space. Represents the number of outbound packets that could not be transmitted because of errors. To view updated Bridge statistics, click Refresh. To clear the Bridge statistics, click Clear. 7.5.2 Learn Table Learn Table allows you to view all the MAC addresses that the device has learnt on all of its interfaces. To view Learn Table statistics, navigate to MONITOR > Bridge > Learn Table. The Learn Table screen appears. The Learn Table displays the MAC address of the learnt device, the bridge port number, aging timer for each device learnt on an interface, and the local (DUT's local interfaces)/remote (learned entries through bridging) status of the learnt device. Figure 7-21 Learn Table To view updated learn table statistics, click Refresh. To clear learn table statistics, click Clear. 7.6 Network Layer 7.6.1 Routing Table Routing table displays all the active routes of the network. These can be either static or dynamic (obtained through RIP). For every route created in the network, the details of that particular link or route will get updated in this table. To view the Routing Table, navigate to MONITOR > Network Layer > Routing Table. The Routing Table screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 236 Monitor 7.6.2 IP ARP Figure 7-22 Routing Table Address Resolution Protocol (ARP) is a protocol for mapping an Internet Protocol address (IP address) to a physical address on the network. The IP ARP table is used to maintain a correlation between each IP address and its corresponding MAC address. ARP provides the protocol rules for making this correlation and providing address conversion in both directions. To view IP Address Resolution Protocol (ARP) statistics, navigate to MONITOR > Network Layer > IP ARP. The IP ARP Table screen appears. The IP ARP Table contains the following information:
Figure 7-23 IP ARP Table Index: Represents the interface type. MAC Address: Represents the MAC address of a node on the network. Net Address: This parameter represents the corresponding IP address of a node on the network. Type: This parameter represents the type of mapping, that is, Dynamic or Static. To view updated IP ARP entries, click Refresh. To clear the IP ARP entries, click Clear. Tsunami 800 & 8000 Series - Software Management Guide 237 7.6.3 ICMP Statistics The ICMP Statistics attributes enable you to monitor the message traffic that is received and transmitted by the device. To view ICMP statistics, navigate to MONITOR > Network Layer > ICMP Statistics. The ICMP Statistics screen appears. Monitor The following table lists the ICMP Statistics parameters and their description:
Figure 7-24 ICMP Statistics Parameter Description In Msgs or Out Msgs Represents the number of ICMP messages that are received/transmitted by the device. In Errors or Out Errors Represents the number of ICMP messages that are received/transmitted by the device but determined as having ICMP-specific errors such as Bad ICMP checksums, bad length and so on. In Dest Unreachs or Out Dest Unreachs Represents the number of ICMP destination unreachable messages that are received/transmitted by the device. In Time Excds or Out Time Excds Represents the number of ICMP time exceeded messages that are received/transmitted by the device. In Parm Probs or Out Parm Probs Represents the number of ICMP parameter problem messages that are received/transmitted by the device. In Srec Quenchs or Out Srec Quenchs Represents the number of ICMP source quench messages that are received/transmitted by the device. In Redirects or Out Redirects Represents the rate at which the ICMP redirect messages are received/transmitted by the device. In Echos Represents the rate at which the ICMP echo messages are received. In EchoReps or Out EchoReps Represents the rate at which the ICMP echo reply messages are received/transmitted by the device. Tsunami 800 & 8000 Series - Software Management Guide 238 Monitor Parameter Description In Timestamps or Out Timestamps Represents the rate at which the ICMP timestamp (request) messages are received/transmitted by the device. In Timestamps Reps or Out Timestamps Reps Represents the rate at which the ICMP timestamp reply messages are received/transmitted by the device. In Addr Masks or Out Addr Masks Represents the number of ICMP address mask request messages that are received/transmitted by the device. In Addr Mask Reps or Out Addr Mask Reps Represents the number of ICMP address mask reply messages that are received/transmitted by the device. To view updated ICMP Statistics, click Refresh. 7.6.4 IP Address Table The IP Address Table shows all IP addresses of the device. The IP Address Table screen contains IP addresses of the interface. To view table, navigate to MONITOR > Network Layer > IP Address Table. The IP Address Table screen appears. Figure 7-25 IP Address Table 7.6.5 DNS Addresses It shows DNS Addresses currently active on the device. To view DNS addresses, navigate to MONITOR > Network Layer >
DNS Addresses. The DNS Addresses screen appears. Figure 7-26 DNS Addresses Tsunami 800 & 8000 Series - Software Management Guide 239 7.6.6 Neighbour Table
: This parameter is applicable only in IPv4 and IPv6 mode, not in IPv4 only mode. Monitor The Neighbour Table contains a list of neighbouring routers and information about them. To view Neighbour Table, navigate to MONITOR > Network Layer > Neighbour Table. The Neighbour table screen appears. Figure 7-27 Neighbour Table 7.6.7 RIP Database
: Applicable only in routing mode. The RIP Database screen contains routes (Routing Information Protocol updates) learnt from other routers. Tsunami 800 & 8000 Series - Software Management Guide 240 Figure 7-28 RIP Database Monitor 7.7 RADIUS (BSU or End Point A only)
: RADIUS is applicable only to a BSU or an End Point A device. 7.7.1 Authentication Statistics Authentication Statistics provides information on RADIUS Authentication for both the primary and backup servers for each RADIUS server profile. To view Authentication statistics, navigate to MONITOR > RADIUS > Authentication Statistics. The RADIUS Client Authentication Statistics screen appears:
The following table lists the Authentication Statistics parameters and their description:
Figure 7-29 Radius Client Authentication Statistics Parameter Round Trip Time Reqs RTMS Accepts Rejects Resp Mal Resp Bad Auths Time Outs Description Represents the round trip time for messages exchanged between RADIUS client and authentication server since the client startup. Represents the number of RADIUS access request messages transmitted from the RADIUS client to the authentication server since client startup. This parameter represents the number of times the RADIUS access requests are being transmitted to the server from the device since the client startup. Represents the number of RADIUS access accept messages received by the device since client startup. Represents the number of RADIUS access reject messages received by the device since client startup. Represents the number of RADIUS response packets received by the device since client startup. Represents the number of malformed RADIUS access response messages received by the device since client startup. Represents the number of malformed RADIUS access response messages containing invalid authenticators received by the device since client startup. Represents the total number of timeouts for RADIUS access request messages since client startup. Tsunami 800 & 8000 Series - Software Management Guide 241 Parameter UnKnown Types This parameter specifies the number of messages with unknown RADIUS message code since client startup. Description Packets Dropped Represents the number of RADIUS packets dropped by the device. To view updated RADIUS Client Authentication statistics, click Refresh. Monitor 7.8 IGMP
: Applicable in Bridge mode only. To view IGMP statistics, navigate to MONITOR > IGMP > IGMP Snooping Stats. The Ethernet or Wireless Multicast List screen appears:
Figure 7-30 Ethernet1 Multicast List 7.8.1 Ethernet or Wireless Multicast List The Multicast List table contains the IGMP Multicast IP and Multicast MAC address details for the Ethernet or Wireless interfaces. The following table lists the parameters and their description. Parameter Group IP MAC Address Time Elapsed Description Represents the IP address of the multicast group for Ethernet or Wireless interface learned by IGMP snooping. Represents the MAC address of the multicast group for Ethernet or Wireless interface learned by IGMP snooping. Represents the time elapsed since the multicast entry has been created for the Ethernet or Wireless interface. To view updated IGMP statistics, click Refresh. 7.8.2 Router Port List The Router Port List displays the list of ports on which multicast routers are attached. Tsunami 800 & 8000 Series - Software Management Guide 242 To view Router Port List, navigate to MONITOR > IGMP > Router Port List. The Router Port List screen appears:
Monitor The following table lists the parameters and their description. Figure 7-31 Router Port List Parameter Port Number Represents the port number on which multicast router is attached (on which IGMP Query has been received). Description Time Elapsed Represents the time elapsed since the port is marked as the router port. To view updated Router Port list, click Refresh. 7.9 DHCP DHCP Leases file stores the DHCP client database that the DHCP Server has served. The information stored includes the duration of the lease, for which the IP address has been assigned, the start and end dates for the lease, and the MAC address of the network interface card of the DHCP client. To view DHCP Leases, navigate to MONITOR > DHCP > Leases. Figure 7-32 DHCP Leases Tsunami 800 & 8000 Series - Software Management Guide 243 7.10 Logs 7.10.1 Event Log Event Log file keeps track of events that occur during the operation of the device. It displays the event occurring time, event type, and the name of the error or the error message. Based on the priority (the log priority is set under MANAGEMENT >
Services > Logs), the event details are logged and can be used for any future reference or troubleshooting. 7.10.1.1 View Event Log To view the event log messages, navigate to MONITOR > Logs > Event Log. The following Event Log screen appears:
Monitor Figure 7-33 Event Log Messages To retrieve the event log file from the device, see Retrieve From Device. The maximum size of the event log file is 65 KB. If the file size exceeds 65 KB, then all the log messages are moved to a backup file and only the recent 100 lines are displayed in the log file. When the size of the log file exceeds again then it overwrites the backup file. Backup files can be retrieved by using retrieve CLI command. For more details, see Tsunami 800 and 8000 Series Reference guide available at http://my.proxim.com.
: Log messages can be stored in the log file approximately up to 6 days with logging interval of 5 minutes. 7.10.1.2 Hide Event Log To hide the event log messages, click Hide Event Log. Tsunami 800 & 8000 Series - Software Management Guide 244 7.10.1.3 Clear Event Log To clear the event log messages, click Clear Event Log. The messages are cleared and moved to the backup file leaving the event log file empty. An event is generated on clearing the event log messages. Monitor
: The current and the backed up event logs are stored in the flash memory and can be retrieved even after device reboot. 7.10.2 Debug Log Debug Log helps you to debug issues related to important features of the device. Currently, this feature supports only DDRS and DFS. This feature helps the engineering team to get valuable information from the field to analyze the issues and provide faster solution. This feature should be used only in consultation with the Proxim Customer Support team. Once logging is enabled, the Debug Log file can be retrieved via HTTP or TFTP. To enable Debug Log, navigate to MONITOR > Logs > Debug Log. The Debug Log screen appears:
Features: Select the appropriate features to be logged. The available features are Select All, DDRS Level 1, DDRS Level 2, DDRS Level 3 and DFS. Figure 7-34 Debug Log File Status: This parameter displays the current size of the Debug Log file. After selecting the DDRS level, click OK. To delete the Debug Log, click Clear Log. To get the updated status of the Debug Log File, Click Refresh. 7.10.3 Temperature Log
: Temperature Log is not applicable to MP-825-CPE-50, MP-825-CPE-100, MP-835-CPE-10, MP-835-CPE-25, MP-835-CPE-50, MP-835-CPE-100, MP-820-SUA-50+, MP-820-SUA-100, MP-822-SUA-100, MP-825-SUR-50+, MP-825-SUR-100 and QB-826-EPR/LNK-100 devices. Temperature Log feature is used to log the internal temperature of the device for the configured temperature logging interval
(By default, it is 5 minutes). It also generates a trap and an event message when the internal temperature of the device Tsunami 800 & 8000 Series - Software Management Guide 245 reaches or exceeds the configured threshold range. The device issues a warning trap when the temperature is 5 Celsius less than the configured threshold range. To access this feature, navigate to MONITOR > Logs > Temperature Log. The following Temperature screen appears:
Monitor Figure 7-35 Temperature Log Current Unit Temperature: Displays the current internal temperature of the device in Celsius. High and Low Temperature Threshold:
Configure the high temperature threshold ranging from -40C to 60C. By default, it is set to 60C. Configure the low temperature threshold ranging from -40C to 60C. By default, it is set to -40C. When the current internal temperature of the device reaches or exceeds this threshold range, then a trap and event message is generated for every one hour (as long as it stays in the same state). If the temperature of the device further changes, then the device will immediately generates another trap and an event message. For example, lets say the configured threshold range is -30(low) to 40 (high). If the device temperature reaches 50 then a trap and event message is generated for every one hour till it remains at 50. So, when the temperature increases to 51 then it will immediately generate another trap and an event message. Temperature Logging Interval: A logging interval from 1 to 60 minutes with 5 minute increment can be selected. For example, if you configure logging interval as 10 minutes then the device temperature is logged for every 10 minutes.
: If the logging interval is configured 0, then the temperature log feature will be disabled. After configuring the parameters, click OK followed by COMMIT. 7.10.3.1 View Temperature Log To view the temperature Log, click Show Temp Log. Tsunami 800 & 8000 Series - Software Management Guide 246 Monitor Figure 7-36 View Temperature Log To retrieve the temperature log file from the device, see Retrieve From Device. The maximum size of the temperature log file is 65 KB. If the file size exceeds 65 KB, then all the log messages are moved to a backup file and only the recent 100 lines are displayed in the log file. When the size of the log file exceeds again then it overwrites the backup file. Backup files can be retrieved by using retrieve CLI command. For more details, see Tsunami 800 and 8000 Series Reference guide available at http://my.proxim.com.
: Log messages can be stored in the log file approximately up to 6 days with logging interval of 5 minutes. 7.10.3.2 Hide Temperature Log To hide the temperature log messages, click Hide Temp Log. 7.10.3.3 Clear Temperature Log To clear the temperature log messages, click Clear Temp Log. The messages are cleared and moved to the backup file leaving the temperature log file empty. An event is generated on clearing the temperature log messages.
: The current and the backed up temperature logs are stored in the flash memory and can be retrieved even after device reboot. Tsunami 800 & 8000 Series - Software Management Guide 247 7.11 Tools 7.11.1 Wireless Site Survey Monitor
: Applicable only to a device in SU or End Point B mode. Wireless Site Survey is done by the SU or End Point B only. This feature scans all the available channels according to the current Channel Bandwidth, and collects information about all BSUs or Endpoint A configured with the same network name as SUs or End Point B. Figure 7-37 Wireless Site Survey - SU Mode To initialize the survey process, click Start. This process list the details of all the available BSUs or End Point A. To stop the site survey process, click Stop. During the scan process, click Refresh to view the latest discovered BSU/End Point A.
: Site Survey cannot be performed, when Roaming is enabled. 7.11.2 Scan Tool With Scan Tool, you can scan all the Proxim devices available on the network. To scan the devices, navigate to MONITOR > Tools > Scan Tool. The Scan Tool screen appears. In the Scan Tool screen, select Scan Mode as IPv4. Click Scan to scan and refresh the devices on the network. The scanned devices are displayed as shown below:
Figure 7-38 An Example - Scanned Devices (IPv4) Tsunami 800 & 8000 Series - Software Management Guide 248 In the Scan Tool screen, select Scan Mode as IPv6 to scan the 82x devices with IPv6 mode. Click Scan to scan and refresh the devices on the network. The scanned 82x devices are displayed as shown below:
Monitor Figure 7-39 An Example - Scanned Devices (IPv6)
:
ScanTool IPv6 support is applicable only for the 82x devices with IPv6 mode. ScanTool can display a maximum of 50 devices. 7.11.3 sFlow Proxims point-to-multipoint and point-to-point devices support sFlow technology, developed by InMon Corporation. The sFlow technology provides the ability to measure network traffic on all interfaces simultaneously by collecting, storing, and analyzing traffic data. Depicted below is the sFlow architecture that consists of a sFlow Agent and a sFlow Receiver. Figure 7-40 sFlow Architecture - An Example with a BSU and SUs The sFlow Agent, which is running on devices, captures traffic information received on all the Ethernet interfaces, and sends sampled packets to the sFlow Receiver for analysis. The sampling mechanism used to sample data are as follows:
Tsunami 800 & 8000 Series - Software Management Guide 249 Monitor Packet Flow Sampling: In this sampling, the data packets received on the Ethernet interface of the device are sampled based on a counter. With each packet received, the counter is decremented. When the counter reaches zero, the packet is packaged and sent to the sFlow Receiver for analysis. These packets are referred to as Packet Flow Samples. Counter Polling Sampling: In this sampling, the sFlow Agent sends counters periodically to the sFlow Receiver based on the set polling interval. If polling interval is set to 5 seconds then the sFlow Agent sends counters to sFlow Receiver every 5 seconds. These packets are referred to as Counter Polling Samples. The Packet Flow Samples and Counter Polling Samples are collectively sent to the sFlow Receiver as sFlow Datagrams. It is possible to enable either or both types of sampling. sFlow Sampling effects the system performance and hence care must be taken in configuring the sFlow parameters. To configure sFlow, navigate to MONITOR > Tools > sFlow. The following sFlow screen appears:
This screen displays the following information about the sFlow Agent:
Figure 7-41 sFLOW Version: The version displayed is 1.3;Proxim Wireless Corp.; v6.4. The version comprises the following information:
1. sFlow MIB Version: Indicates the agents MIB version. The MIB specifies how the agent extracts and bundles sampled data, and the sFlow receiver must support the agents MIB. The sFlow MIB version is 1.3. so the sFlow Receivers version must also be at least 1.3. 2. Organization: Specifies the organization implementing sFlow Agent functionality on the device, that is, Proxim Wireless Corp. 3. Revision: Specifies the sFlow Agent version, that is, v6.4. Address Type: Specifies the protocol version for IP addresses. Agent Address: Specifies the sFlow Agents IP address. Tsunami 800 & 8000 Series - Software Management Guide 250 7.11.3.1 sFlow Receiver Configuration The Receiver Configuration page allows you to configure sFlow Receiver(s), which receives samples from all agents on the network, combines and analyzes the samples to produce a report of network activity. To configure sFlow Receiver, navigate to MONITOR > Tools > sFlow and select Receiver Configuration tab. Given below is the table which explains sFlow parameters and the method to configure the configurable parameter(s):
Monitor Parameter Description S.No. Owner Time Out Represents the Receiver index number. Please note that the number of indexes depends on the Ethernet interfaces your device supports. Enter a string, which uniquely identifies the sFlow Receiver. Enter a value ranging from 30 to 31536000 seconds (365 days) in the Time Out box. The sFlow Agent sends sampled packets to the specified sFlow Receiver till it reaches zero. At zero, all the Receiver parameters are set to default values. Max Datagram Size Enter the maximum size of a sFlow datagram (in bytes), which the Receiver can receive, in the Max Datagram Size box. By default, the maximum datagram size is set to 1400 bytes. It can range from 200 to 1400 bytes. Address Type The address type supported by sFlow Receiver is ipv4, which is by default selected.
: Only IPv4 is currently supported. Receiver Address Enter the sFlow Receivers IP address in the Receiver Address box. Receiver Port By default, the sFlow Receiver listens to the sFlow datagrams on 6343 port. To change the port, enter a valid port ranging from 0 to 65535 in the Receiver Port box. Datagram Version The sFlow datagram version used is 5. Click Apply, to save the sFlow Receiver configuration parameters. Once the Receiver configurations are done, either Packet Flow sampling or Counter Polling Sampling or both can be started.
:
Enabling sampling effects the system performance and hence care should be taken in setting the right values for Timeout and Max Datagram Size. When the Owner string is cleared, the Flow Sampling and Counter Polling stops. 7.11.3.2 Sampling Configuration To configure and start packet flow sampling, do the following:
1. Navigate to MONITOR > Tools > sFlow and select Sampling Configuration tab. Tsunami 800 & 8000 Series - Software Management Guide 251 Monitor Figure 7-42 sFlow Sampling Configuration 2. From the Receiver Index drop-down box, select the receiver index number associated with the sFlow Receiver to which the sFlow Agent should send the sFlow Datagrams.
: If device has two Ethernet interfaces, then configure different Receiver indexes for each of the interface. 3. Type a value in the Packet Sampling Rate box. This value determines the number of packets the sFlow Agent samples from the total number of packets passing through the Ethernet interface of the device. 4. Type a value in the Maximum Header Size box, to set the amount of data (in bytes) to be included in the sFlow datagram. The sFlow Agent samples the specified number of bytes. For example, if you set the Maximum Header Size to 100, the sFlow Agent places the first 100 bytes of every sampled frame in the datagram. The value should match the size of the frame and packet header so that the entire header is forwarded. The default size is 128 bytes. The header size can range from 20 to 256 bytes. 5. Next, click Apply to start packet flow sampling. Once it starts, the Time Out parameter (see sFlow Receiver Configuration) keeps decrementing till it reaches a zero value. On reaching zero, the corresponding Receiver and Sampling values are set to default values.
:
Enabling sFlow packet sampling effects the system performance, and hence care must be taken when choosing the right value for Packet Sampling Rate and Maximum Header Size. Receiver Index for packet Sampling table and Counter Polling table should be same for each Ethernet interface. 7.11.3.3 Counter Polling Configuration To configure and start Counter Polling sampling, do the following:
1. Navigate to MONITOR > Tools > sFlow and select Counter Polling Configuration tab. Tsunami 800 & 8000 Series - Software Management Guide 252 Monitor Figure 7-43 Counter Polling Configuration 2. From the Receiver Index drop-down box, choose the receiver index number associated with the sFlow Receiver to which the sFlow Agent sends the counters.
: If Packet Flow Sampling is already configured and running, then you should configure the Receiver index same as configured in the Packet Flow Sampling for each Ethernet interface. 3. Set the polling interval by typing a value in the Interval box. Lets say, the polling interval is set to 30 seconds. So for every 30 seconds, the counters are collected and send to the sFlow Receiver. The valid range for polling interval is 0 to 231 - 1 seconds. 4. Next, click Apply to start Counter Polling Sampling. Once it starts, the Time Out parameter (see sFlow Receiver Configuration) keeps decrementing till it reaches a zero value. On reaching zero, the corresponding Receiver and Counter Polling values are set to default values. Enabling sFlow counter sampling effects the system performance, and hence care must be taken when choosing the right value sampling interval. Receiver Index for packet Sampling table and Counter Polling table should be same for each Ethernet interface. If a sampling starts and there is already another sampling running then we consider the time out value of the current/already running sampling. 7.11.4 Console Commands The Console Commands feature helps Proxims Technical Support team to debug field issues. Tsunami 800 & 8000 Series - Software Management Guide 253 7.11.5 Spectrum Analyzer Spectrum Analyzer helps to analyze a spectrum for interference, and select a relatively low interference channel. This tool is not a replacement for the commercial Spectrum Analyzers as this is only intended to help with channel selection and diagnose performance issues. Monitor
: Only an administrator user can use Spectrum Analyzer to scan the spectrum. However, the Monitor user can view the last scanned results. To scan all the channels in the configured frequency domain, do the following:
Navigate to MONITOR > Tools > Spectrum Analyzer. The following Spectrum Analyzer screen appears:
Figure 7-44 Spectrum Analyzer Channel Scan Time: Enter the time (ranging from 100 to 60000 milliseconds) to scan each channel. By default, the scan time is set to 1000 milliseconds. Low Frequency Filter & High Frequency Filter: Enter the appropriate low and high frequency filter values to limit the number of channels to scan. Next, click OK. Navigate to Spectrum Analyzer > Scan. The following Spectrum Analyzer Scan screen appears. In this screen, you can either select Basic or Advanced tab. Figure 7-45 Spectrum Analyzer Scan
:
The total duration of scan depends on the number of channels available, channel scan time and scan iterations. While scanning, Spectrum Analyzer does not consider channel offset. Spectrum Analyzer detects only 802.11 modulated signals. A minor variation in Spectrum Analyzer results can be expected due to the following reasons: variation in the radio properties between various device models and Satellite Density Configuration. Tsunami 800 & 8000 Series - Software Management Guide 254 Monitor
:
When the Spectrum Analyzer starts, the wireless link, if established, is terminated and re-established after the scan is completed.
As the wireless link is down during spectrum analysis, the remote device cannot be accessed. Hence, if Spectrum Analyzer is started on a remote device, the results will not be available until spectrum scan is completed and wireless link gets re-established. 7.11.5.1 Basic Mode This mode helps to collect SNR and packet statistics report. The parameters under the Basic tab are described and tabulated below:
Parameter Description Approximate Scan Duration This parameter displays the total time (dd:hh:mm:ss) required to complete the scan. Last Scanned Time This parameter displays the time at which the last spectrum scan was done. Scan Iterations This parameter specifies the number of times the scan iterates. By default, the scan iteration is set to 1. The configurable value can range from 1 - 1000. After configuring the Scan iteration value, click OK. Next, click Start, to scan. The scanned results are displayed in the form of a graph as follows:
:
The frequencies are scanned by 5MHz slice starting from the lower edge of the frequency filter, and displays the results captured at that particular instance. When working in a high interference network, ensure to run the spectrum analyzer with multiple iterations
(increase the Scan Time) to get accurate results. Figure 7-46 An Example - Scanned Results (Basic Mode) Tsunami 800 & 8000 Series - Software Management Guide 255 Monitor Graph Results Interpretation Consider a network with a device operating on channel 159 with 20 MHz channel bandwidth. In the same vicinity, when we run the Spectrum Analyzer on a Tsunami radio it will display the results as shown in Figure 7-46. From the results, we see interfering signals on channels 153 to 170. It also shows strong interfering signal on channels 157 to163 indicating the presence of a device operating on channel 159, and moderate interfering signals on channels 153-156 and 164-166 (which are side band signals from the same interference source). We recommend to avoid using these channels while installing Tsunami products, otherwise radio will report huge PHY and CRC errors. However, to make these channels usable and to ignore the low interference signals, we recommend configuring Satellite Density on the devices. By default, for each channel, the graph represents the following statistics:
Parameter Maximum RSSI Description Legend Represents the maximum RSSI of all the signals received during the scan on a given channel. Minimum RSSI Represents the minimum RSSI of all the signals received during the scan on a given channel. Average RSSI Represents the average RSSI of all the signals received during the scan on a given channel. Activity Count Represents the total wireless activities (including OFDM Signal and Errors) during the scan on a given channel. Please note that the Current Iteration parameter helps to learn the current scan iteration. For example, if Scan Iteration is configured as 2, and currently only one scan cycle is complete then Current Iteration parameter displays 1. To view the statistics of a particular channel, point the cursor to that channel on the graph. The statistics is displayed as shown below:
It is also possible to view only the selected statistics on the graph. For example, to view only Minimum and Maximum RSSI on the graph, uncheck the box against Activity Count and Avg on the top of the graph. Figure 7-47 Channel Statistics Figure 7-48 An Example - Selective Graph Statistics Tsunami 800 & 8000 Series - Software Management Guide 256 At a time, the graph represents the statistics of a maximum of 32 channels. To view the graph(s) of the remaining channels, click Next (available on the upper right corner of the graph). Click Previous to view the statistics of the previous channels. To view the tabular format of the graph statistics, click Detailed Statistics on the bottom left of the graph. The detailed statistics is displayed as follows:
Monitor Tsunami 800 & 8000 Series - Software Management Guide 257 Figure 7-49 An Example - Detailed Statistics 7.11.5.2 Advanced This mode helps to scan the user configured bandwidth to identify the other devices operating on different channels. This displays the device information such as Bandwidth, Channel Number, MAC Address, System Name, Mode, Encryption, SNR, and Packet count along with the information provided in Basic scanning mode. Monitor
:
The frequencies are scanned based on the configured Scan Bandwidth slice starting from the lower edge of the frequency filter, and displays the results captured at that particular instance. By default, the scan iteration is always 1 in Advanced scanning mode. For example, let us consider the configuration values shown in the Spectrum Analyzer screen given below:
Figure 7-50 An Example - Spectrum Analyzer Next, navigate to Spectrum Analyzer > Scan. Select the Advance tab and the following Spectrum Analyzer Scan screen appears. Figure 7-51 An Example - Spectrum Analyzer Scan (Advance Mode) Scan Bandwidth: Select the appropriate bandwidth from the drop-down menu and click OK. Next, click the Start button to scan. The scanned results for the detected devices are displayed as shown below:
Tsunami 800 & 8000 Series - Software Management Guide 258 Monitor Figure 7-52 An Example - Spectrum Analyzer Scanned Results (Advance Mode) The device information displayed in Advance Scanning mode are described and tabulated below. Parameter Bandwidth Channel Number MAC Address System Name Mode Description This parameter displays Bandwidth of the detected device. This parameter displays the channel number on which the detected device is operating. This parameter displays the MAC Address of the detected device. This parameter displays either the Device Name or the SSID of the detected device. This parameter displays the Mode of the detected device. BSU: Base Station Unit SU: Subscriber Unit AP: Access Point STA: Station Encryption SNR This parameter indicates whether encryption is enabled on the detected device. This parameter displays the Signal-to-Noise Ratio (SNR) value of the detected device in the scanned channel. Packet Count This parameter displays the Packet Count for the detected device. Tsunami 800 & 8000 Series - Software Management Guide 259 Monitor 7.11.6 Radio Link Test Tool
: It is applicable to 82x / 8xxx devices. In general, whenever the network has some performance issue, it is required to identify whether the issue is due to the wireless link or due to other network parameters. The Radio Link Test (RLT) tool helps to measure and diagnose any performance issues in the wireless link. At MAC level, this tool internally generates the traffic between the two radios, monitors the traffic, and generates a test report.The test report will help in analyzing the wireless link performance and other related issues such as interference, lower throughput, and wireless errors. Especially for the static link establishment, this is very helpful to check the link between the two radios when installing for the first time or if any performance issues are noticed after the installation. If the link between the radios is of expected quality, then there is no issue with the wireless link. In case, if there is any issue due to wireless parameters, the link may need some tuning in configuration such as channel, Data Rate, Tx power or distance between the radios. In spite of all the testing and tuning, if the performance still fails to improve, then it may be due to installation related issues such as antenna alignment or the physical path. In the worst case, it may be a hardware related issue.
:
This is not a replacement for other wireless performance measuring tools and should be used in conjunction with other tools like Iperf or any other commercial tools. It is recommended to use this tool with caution on live networks as it will be generating internal traffic which may impact the network performance. Radio Link test is an experimental feature and will be improved in future releases. This tool can be accessed through web interface, console commands, and CLI. Both ends of a link cannot simultaneously run this test. 7.11.6.1 Configuration Options The configuration options for the Radio Link Test tool are tabulated below:
Parameter Description Test Duration Traffic Direction Traffic Rate Time duration for which the Radio Link Test is performed (Default: 60 seconds) Direction of the traffic (Downlink/Uplink /Bi-directional) Amount of traffic to be generated (K bps) Periodic Report Interval Time interval in which the report is presented to the user interface (seconds) Packet Size MAC Address Verbose Mode Help Version
:
Generate packet size (Default value: 1500 bytes) Wireless MAC address of the device running in server mode Detailed statistics information List of possible options (Usage) Display tool version information The following parameters can also be configured/modified through Console commands and CLI: Test Duration, Traffic Rate, Periodic Packet Interval, and Packet Size. Please refer rlt Command Options section for detailed explanation of rlt commands. Tsunami 800 & 8000 Series - Software Management Guide 260 To access this tool through web interface, navigate to MONITOR > WORP Statistics > Interface 1 > BSU/SU Link Statistics > Details. Click as shown in An Example - SU Link Statistics. Monitor The following BSU/SU WORP Detailed Statistics screen appears. Figure 7-53 An Example - SU Link Statistics Click the Radio Link Test Button. The following Radio Link Test screen appears. Figure 7-54 Radio Link Test Tool In the Radio Link Test screen, you can select the required type of traffic from the given options namely Uplink, Downlink, and Bidirection. By selecting Verbose along with any one of the traffic options, you can get a detailed test report for the traffic selected. In the above screen, for example, select Bidirection and Verbose. Next, click the START button. Tsunami 800 & 8000 Series - Software Management Guide 261 Monitor Figure 7-55 An Example - Radio Link Test (Bidirectional Traffic with Verbose mode) The test runs for 60 seconds and displays the Radio Link Test Report as shown below. Figure 7-56 An Example - Test Report (Bidirectional Traffic with Verbose mode) Tsunami 800 & 8000 Series - Software Management Guide 262 7.11.6.2 Statistics Options The test report can be analyzed by using the statistics options tabulated below:
Monitor Parameter Traffic Statistics Tx Packets Rx Packets Lost Packets Duplicated Packets Tx Rate Rx Rate Wireless Statistics Phy Errors Description Total packets transmitted from the moment user initiated the test. Total packets received from the moment user initiated the test. Packets lost due to any reason. Number of packets received in duplicate for the already received packets. The rate at which the packets are sent. The rate at which the packets are received. Total number of error packets received from the moment user initiated the test . The possible reasons:
It indicates the interference in the wireless medium Low signal level CRC Errors Number of packets received with invalid CRC. The possible reasons:
It indicates the interference in the wireless medium Low signal level Number of times the radio detected busy medium while trying to transmit the frame. This could be due to interference on that specific channel. Refers to the number of data messages sent and acknowledged by the peer successfully. Refers to the number of data messages that are not acknowledged by the peer even after the specified number of retransmissions. Refers to the number of data messages that are re-transmitted and acknowledged by the peer successfully. Refers to the number of data messages received and acknowledged successfully. Refers to the number of successfully received re-transmitted data messages. Refers to the number of data messages that were not received successfully. Medium Busy WORP Statistics Send success Send failure Send retires Receive success Receive failures Receive retires Signal Statistics Tsunami 800 & 8000 Series - Software Management Guide 263 Monitor Parameter Description Signal Noise SNR Signal measured at the radio port Noise detected at the radio port Signal to Noise Ratio (dB) 7.11.6.3 rlt Command Options Using the rlt command options tabulated below, you run the radio link test tool through Web Console. Options Description
-t
-i
-s
-o Traffic Direction
-d
-u Test duration (Default: 60 seconds) Periodic report display interval (Default: 0 - disabled) Packet size (Default: 1500 bytes) Ignore timeout during test (Default: do not ignore) Downlink throughput test with specified traffic rate in K bps (Default: Unlimited) Uplink throughput test with specified traffic rate in K bps (Default: Unlimited) No option Default: Bi-Directional test with unlimited rate Miscellaneous
-h, --help
-v, --version
-V Tool usage Tool version number Verbose mode (Enables detailed statistics display) The -i option to display the test report at regular intervals works only with the -V verbose option for all traffic directions. To access this tool through Web Console, navigate to MONITOR > Tools > Console Commands. In the Web Console screen do the following:
Tsunami 800 & 8000 Series - Software Management Guide 264 Monitor Figure 7-57 An Example - Radio Link Test Through Web Console Command: Type the required rlt command. Click the Execute button. The command execution is displayed in the Web Console screen. To run the Radio Link Test tool through Command Line Interface (CLI), refer the Tsunami 800 and 8000 Series Reference Guide. 7.12 SNMP v3 Statistics SNMP v3 statistics can be viewed only when SNMPv3 feature is enabled on the device. See SNMP. To view the SNMPv3 Statistics, navigate to MONITOR > SNMPV3 Statistics. The following SNMP v3 Statistics screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 265 Figure 7-58 SNMP v3 Statistics Monitor The following table lists the SNMP v3 parameters and their description:
Parameter Unsupported Sec Levels Description This parameter specifies the total number of packets dropped by the SNMP engine because they requested a security level that was unknown to the SNMP engine or otherwise unavailable. Not In Time Windows This parameter specifies the total number of packets dropped by the SNMP engine because they appeared outside the authoritative SNMP engine's window. Unknown User Names This parameter specifies the total number of packets dropped by the SNMP engine because they correspond to a user that is unknown to an SNMP engine. Unknown Engine IDs This parameter specifies the total number of packets dropped by the SNMP engine because they correspond to an SNMP Engine ID that is unknown to an SNMP engine. Wrong Digests Decryption Errors This parameter specifies the total number of packets dropped by the SNMP engine because they do not contain the expected digest value. This parameter specifies the total number of packets dropped by the SNMP engine because they could not be decrypted. Tsunami 800 & 8000 Series - Software Management Guide 266 Troubleshooting 8 This chapter helps you to address the problems that might arise while using our device. If the procedures discussed in this chapter does not provide a solution, or the solution does not solve your problem, check our support site at http://my.proxim.com which stores all resolved problems in its solution database. Alternatively, you can post a question on the support site, to a technical person who will reply to your email. Before you start troubleshooting, check the details in the product documentation available on the support site. For details about RADIUS, TFTP, Terminal and Telnet programs, and Web Browsers, refer to their appropriate documentation. In some cases, rebooting the device solves the problem. If nothing else helps, refer to Recovery Procedures. This chapter provides information on the following:
Surge or Lightning Issues (For Connectorized devices) Setup and Configuration Issues Application Specific Troubleshooting PoE Injector Connectivity Issues Wireless Link Issues Wired (Ethernet) Interface Validation Wireless Interface Validation Recovery Procedures Miscellaneous Spectrum Analyzer Tsunami 800 & 8000 Series - Software Management Guide 267 8.1 PoE Injector Problem The Device Does Not Work Troubleshooting Make sure that you are using a standard UTP Solution Category 5e/6 cable in case of MP-8100-SUA, MP-8150-SUR, MP-8150-SUR-100, MP-8200-BSU-G, MP-8250-BS9-G, MP-8250-BS1-G, MP-8200-BSU, MP-8250-BS9, MP-8250-BS1, MP-820-BSU-100, MP-822-BSU-100, MP-825-BS3-100, MP-8200-SUA, MP-820-SUA-50+, MP-820-SUA-100, MP-822-SUA-100, MP-825-SUR-50+, MP-825-SUR-100, QB-8200-LNK-G, QB-8200-LNK, QB-825-EPR/LNK-50+, QB-825-EPR/LNK-100, QB-835-EPR/LNK-25 and QB-835-EPR/LNK-50 devices Category 5/5e cable in case of MP-835-CPE-10, MP-835-CPE-10, MP-835-CPE-25, MP-835-CPE-50, MP-835-CPE-100,MP-825-CPE-50, MP-825-CPE-100 and QB-826-EPR/LNK-100. Try a different port on the same PoE Injector hub (remember to move the input port accordingly) if it works then there is a problem in the previous RJ45 port or a bad RJ45 port connection. Try to connect the device to a different PoE Injector hub. Try using a different Ethernet cable if it works, there is probably a fault in the cable or its connection. Check the power plug and hub. If the Ethernet link goes down, check the cable, cable type, switch and hub. There is No Data Link Verify that the indicator on the device port is ON. Verify that the Ethernet cable from PoE Injector hub to the Ethernet port of the device is properly connected. Make sure that you are using a standard UTP Category 5e/6 cable in case of MP-8100-SUA, MP-8150-SUR, MP-8150-SUR-100, MP-8200-BSU-G, MP-8250-BS9-G, MP-8250-BS1-G, MP-8200-BSU, MP-8250-BS9, MP-8250-BS1, MP-820-BSU-100, MP-822-BSU-100, MP-825-BS3-100, MP-8200-SUA, MP-820-SUA-50+, MP-820-SUA-100, MP-822-SUA-100, MP-825-SUR-50+, MP-825-SUR-100, QB-8200-LNK-G, QB-8200-LNK, QB-825-EPR/LNK-50+, QB-825-EPR/LNK-100, QB-835-EPR/LNK-25 and QB-835-EPR/LNK-50 devices Category 5/5e cable in case of MP-835-CPE-10, MP-835-CPE-25, MP-835-CPE-50, MP-835-CPE-100, MP-825-CPE-50, MP-825-CPE-100 and QB-826-EPR/LNK-100. The length of the cable from the Ethernet port of the device to the PoE should be less than 100 meters (approximately 325 feet). Try to connect a different device to the same port on the PoE Injector hub if it works and a link is established then there is probably a fault in the data link of the device. Try to re-connect the cable to a different output port (remember to move the input port accordingly) if it works then there is a fault probably in the output or input port of the PoE Injector hub or a bad RJ45 connection. Connect the device to a PoE Injector. Move the device into a different output port (remember to move the input port Ensure that there is no short over on any of the connected cables. accordingly) - if it works then there is a fault probably in the previous RJ45 port or bad RJ45 port connection. Overload Indications Tsunami 800 & 8000 Series - Software Management Guide 268 Troubleshooting 8.2 Connectivity Issues Connectivity issues include any problem that prevents from powering or connecting to the device. Problem Does Not Boot - No LED Activity Ethernet Link Does Not Work Make sure the power source is ON. Make sure all the cables to the device are connected properly. Solution Check the Ethernet LED Solid Green: The Ethernet link is up. Blinking Green: The Ethernet link is down. Serial Link Does Not Work Double-check the physical network connections. Make sure your PC terminal program (such as HyperTerminal) is active and configured to the following values:
Com Port: (COM1, COM2 and so on depending on your computer);
Baud rate: 115200; Data bits: 8; Stop bits: 1; Flow Control: None; Parity:
None;
Line Feeds with Carriage Returns
(In HyperTerminal select: File > Properties > Settings > ASCII Setup > Send Line Ends with Line Feeds)
: Not applicable to MP-835-CPE-10, MP-835-CPE-25, MP-835-CPE-50, MP-835-CPE-100, MP-825-CPE-50 and MP-825-CPE-100 as it does not support serial interface. Cannot Access the Web Interface Open a command prompt window and type the Ping command along with the IP address of the device. For example, ping 10.0.0.1. If the device does not respond, check if you have the correct IP address. If the device responds then it means the Ethernet connection is working properly. Ensure that you are using Microsoft Internet Explorer 7.0 (or later) or Mozilla Firefox 3.0 (or later). Ensure that you are not using a proxy server for the network connection with your Web browser. Ensure that you have not exceeded the maximum number of Web Interfaces or CLI sessions. Double-check the physical network connections. Use a well-known device to ensure the network connection is functioning properly. Troubleshoot the network infrastructure (check switches, routers, and so on).
: At any point of time, if the device is unable to connect to your network, reset the device by unplugging and plugging the cables from the PoE. Tsunami 800 & 8000 Series - Software Management Guide 269 Troubleshooting 8.3 Surge or Lightning Issues (For Connectorized devices) Problem Solution Surge or Lighting Problem In case of any lightning or surge occurrence, check for the conditions specified below:
Check the RF signals by referring to RSSI statistics and if the signal strength has been lowered considerably, replace the Surge Arrestor. Unscrew the N-Type connector at the top and visually inspect the Surge Arrestor for electrical burns. If any, replace it. 8.4 Setup and Configuration Issues Problem Device Reboots Continuously Lost Telnet or SNMP Password Solution One of the reason for the device to reboot continuously is that the radio card is not properly placed in the mini-PCI slot. When you power on the device and you do not see the WIRELESS NETWORK1 PASSED in the POST message in the Serial Console, please contact Proxims support site at http://my.proxim.com. Perform Operational Mode procedure. This procedure resets system and network parameters, but does not affect the image of the device. The default HTTP, Telnet, and SNMP username is admin and password is public. Device Responds Slowly If the device takes a long time to respond, it could mean that:
Incorrect Device IP Address No DHCP server is available. The IP address of the device is already in use. Verify that the IP address is assigned only to the device you are using. Do this by switching off the device and then pinging the IP address. If there is a response to the ping, another device in the network is using the same IP address. If the device uses a static IP address, switching to DHCP mode could solve this problem. The network traffic is more. The default IP address assignment mode is Static and the default IP address of the device is 169.254.128.132. If the IP address assignment mode is set to Dynamic, then the DHCP Server will assign an IP address automatically to the device. If the DHCP server is not available on your network, then the fall back IP address (169.254.128.132) of the device is used. Use ScanTool, to find the current IP address of the device. Once you have the current IP address, use Web Interface or CLI Interface to change the device IP settings, if necessary. If you are using static IP address assignment, and cannot access the device over Ethernet, refer to Initializing the IP Address using CLI. Perform Operational Mode procedure. This will reset the device to static mode. Tsunami 800 & 8000 Series - Software Management Guide 270 Problem HTTP Interface or Telnet Does Not Work Solution Make sure you are using a compatible browser:
Microsoft Internet Explorer 7.0 or later Mozilla Firefox 3.0 or later Troubleshooting
:
When working with Internet Explorer 9 in Windows 2008 Server, navigate to Internet Options -> Security -> Internet -> Custom Level ->
Scripting -> Active Scripting to enable active scripting. When working with Internet Explorer 10 and facing web page issues, click the Broken Page icon available on the right side of address bar. Make sure you have the correct IP address of the device. Enter the device IP address in the address bar of the browser, for example http://169.254.128.132. When the Enter Network Password window appears, enter the User Name and and Password. The default HTTP username is admin and password is public. Use CLI, to check the IP Access Table which can restrict access to Telnet and HTTP. Telnet CLI Does Not Work Make sure you have the correct IP address. Enter the device IP address in the Telnet connection dialog, from a DOS prompt: C:\> telnet <Device IP Address>
Use HTTP, to check the IP Access Table which can restrict access to Telnet and HTTP. Enable Telnet in Vista or Windows 7 as it is by default disabled. The TFTP server is not properly configured and running The IP address of the TFTP server is invalid The upload or download directory is not correctly set The file name is not correct 1. Restart your Web browser. 2. Log on to the device again and make changes. 3. Reboot the device. 4. Click COMMIT for the changes to take effect. 5. Wait until the device reboots before accessing the device again. Use NIC cards of the same vendor Wait for few seconds and re-perform the commit operation. TFTP Server Does Not Work Changes in Web Interface Do Not Take Effect Imbalance in the throughputs of the aSymmetric Uplink &
Downlink, if NIC cards of different vendors are used At the SU during commit, a Pop up with message "Failed to apply WORP link profile Configuration" is observed, though the configuration is valid. Tsunami 800 & 8000 Series - Software Management Guide 271 8.5 Application Specific Troubleshooting Troubleshooting Problem RADIUS Authentication Server Services unavailable TFTP Server Solution If RADIUS Authentication is enabled on the device, then make sure that your networks RADIUS servers are operational. Otherwise, clients will not be able to log on to the device. There are several reasons for the authentication servers services to be unavailable. To make it available, Make sure you have the proper RADIUS authentication server information setup configured on the device. Check the RADIUS Authentication Servers Shared Secret and Destination Port number (default is 1812; for RADIUS Accounting, the default is 1813). Make sure the RADIUS authentication server RAS setup matches the device. If a TFTP server is not configured and running, you will not be able to download and upload images and configuration files to or from the device. Remember that the TFTP server need not be local, as long as you have a valid TFTP IP address. Note that you do not need a TFTP server running unless you want to transfer files to or from the device. After the TFTP server is installed:
Check to see that TFTP is configured to point to the directory containing the device Image. Make sure you have the proper TFTP server IP Address, the proper device image file name, and that the TFTP server is connected. Make sure the TFTP server is configured to both Transmit and Receive files (on the TFTP servers Security tab), with no automatic shutdown or time-out (on the Auto Close tab). 8.6 Wireless Link Issues Given below are the possible reasons for a wireless link not getting established and the relevant observations. Reason(s) Mismatch in network name Incorrect or invalid configured BSU/End Point A name Mismatch in network secret Observation The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented in BSU/End Point A and SU/End Point B. The WORP counters are not affected. The remote device is not listed in the Site Survey. The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented in SU/End Point B. The WORP counters are not affected. The remote device is not listed in the Site Survey. The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented in BSU/End Point A and SU/End Point B. The WORP counters are incremented (Req for Serv, Reg Req, Auth Req, Reg Attempts, Reg LastReason: Incorrect Parameter) on both ends. Tsunami 800 & 8000 Series - Software Management Guide 272 Reason(s) Encryption set to No Encryption in BSU/End Point A and AES Encryption in SU/End Point B Encryption set to AES Encryption in BSU/End Point A and No Encryption in SU/End Point B Encryption set to AES Encryption in both BSU/End Point A and SU/End Point B. A mismatch in Encryption key BSU exceeds the maximum SU limit Interference issues due to wider beam width of the antenna With multiple link profiles, the wireless network performance is getting affected. Troubleshooting Observation The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented in BSU/End Point A; No decrypt errors are observed in SU/End Point B. In SU/End Point B, the WORP counters (Announcements, Req for Serv, Reg Attempts, Reg incomplete, Reg timeout, Reg Last Reason: Timeout) are incremented. In BSU/End Point A, no WORP counters are incremented except announcements. The remote device is not listed in the Site Survey. The Wireless Statistics counters and WORP counters are not incremented in SU/End Point B. The remote device is not listed in the Site Survey. The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented only in SU/End Point B. The remote device is not listed in the Site Survey. The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented in SU/End Point B but fails to authenticate. The WORP counters (Announcements, Req for Serv, Reg Attempts, Reg Incompletes, Reg Timeouts, Reg Last Reason: Timeout) are incremented in SU/End Point B. The remote device is listed in the Site Survey. MP-835-CPE-10, MP-835-CPE-25, MP-835-CPE-50, MP-835-CPE-100, MP-825-CPE-50, MP-825-CPE-100, MP-825-SUR-50+, MP-825-SUR-100 and QB-826-EPR/LNK-100 uses a wider beam width antenna (up to 38 o) with a gain of 15dBi. Due to its wider beam width, it may pick up more interfering signals and may report large number of errors compared to other Tsunami products. Wireless interference may also lead to:
SNR value fluctuations between the Antenna (A1/A2) ports DDRS operation at lower data rates Higher number of PHY errors which may result in false RADAR detection in DFS bands To overcome these issues, use a spectrum analyzer and switch to a noise-free channel. The overall performance of the wireless network gets affected when using multiple link profiles and atleast one of the subscriber is operating with a lower data rate. For example, consider a wireless network with a BSU and 5 SU profiles. Each SU is transmitting data at a data rate as tabulated below. As SU1 is operating at a lower data rate (6.5 Mbps), the entire performance of the network gets affected. Tsunami 800 & 8000 Series - Software Management Guide 273 Reason(s) Observation Troubleshooting SU Profile(s) Data Rate Throughput SU1 SU2 SU3 SU4 SU5 6.5 Mbps 39 Mbps 78 Mbps 130 Mbps 78 Mbps Aggregated throughput can be a maximum of 13 Mbps In order to optimize the network performance, apply QoS. Given below is an example on how the network performance can be improved by applying QoS. QoS is applied for SU1 with the following configuration:
PIR based on the ToS value 96 SFC with MIR/CIR= 1Mbps; Priority = 3; Latency/Jitter=10ms Subscribers SU2...SU5 use the default QoS configuration. Profiles Data Rate Throughput SU1 SU2 SU3 SU4 SU5 6.5 Mbps 39 Mbps 78 Mbps 130 Mbps 78 Mbps With QoS applied for SU1, expected throughput is 26 Mbps
: Given above is just an example and values might vary from case-to-case. 8.7 Wired (Ethernet) Interface Validation Problem Wired (Ethernet) Interface Validation Solution Run iperf commands Use iperf commands with w option as 202k. The throughput is expected to be equal in both directions and should be comparable from laptop to laptop or desktop to desktop performance If the above throughput value is not in the expected range, Check speed and duplex settings between the device and Personal Computer or switch or router connected Make sure the connection established is of same speed and full duplex is as expected
(10 or 100 or 1000) With auto negotiation, if you notice this issue, then try manually setting the speed and duplex Update the Ethernet driver in the Personal Computer to the latest one Tsunami 800 & 8000 Series - Software Management Guide 274 8.8 Wireless Interface Validation Troubleshooting Problem Wireless Interface Validation Wireless Interface Validation Solution Run iperf commands (You can run Embedded iperf commands only through Telnet.) iperf s w 202k (command for iperf server) Iperf c ipaddress w 202k t time Period I <intermediateResultInterval> P <4 or 6> (command to run iperf client) Ipaddress -> of the SU/End Point B or BSU/End Point A device where the iperf server is running P -> No of pairs (Streams) Use d option to run bidirectional throughput Use r option to run unidirectional throughput one after another without changing the server and SU ends If the expected throughput is not achieved, then check the following:
Antenna Alignment Note whether the antenna ports are balanced SNR/RSSI provided for Local and Remote in the BSU/SU Link Statistics page or by using aad command Signal difference of <=5 dBm is considered as balanced and recommended If the chains are not balanced, then look at the alignment and connectors of RF cables, used between antenna and device If in RMA (Returned from Customer), check the RF cable to radio port connectivity Avoid nearby metal surfaces, if you are using Omni antenna Data Streams Select Single stream instead of Dual stream mode DDRS - with single stream data rate or with Auto mode Dual stream data rates can be used only when the signal in both antenna ports is balanced. Antenna Port Selection For devices with 3x3 MIMO radio, make sure you are either enabling all antenna ports for 3x3 MIMO or using A1 and A3 antenna ports for 2x2 MIMO mode For devices with 2x2 MIMO radio, use A1 and A2 antenna ports For using single stream, it is mandatory to select antenna port A1 Enabling all antenna port will not cause any issue even if it is not in use. Bad Channel Check for CRC errors, PHY errors, WORP Retries and WORP Failures in Monitor Interface Statistics page. If this count increments steadily (Refreshing the web page is required) then Either change the channel and check for a better channel Use Wi-Spy or similar tool and check the environment for better channel Data Rate Issues Ensure same data rates are selected if you are using fixed data rate between BSU/SU and End Point A/End Point B to have predictable throughput and link Alternatively, use DDRS with Auto mode enabled Tsunami 800 & 8000 Series - Software Management Guide 275 Problem Solution Performance and Stability Issues Troubleshooting Check the distance between two co-locating devices. The distance between two co-locating devices should be minimum 3 meters, in order to achieve good throughput and maintain link stability. The operating adjacent channel should maintain 5MHz spacing if managed by a single administrator. When DDRS is disabled, check the Minimum Required SNR for the current data rate by navigating to MONITOR --> WORP Statistics --> Interface 1
--> Link Statistics Page --> Click here for Local SNR-Table. If the current SNR is not meeting the minimum required SNR criteria for the current data rate, then accordingly reduce the data rate. If SNR is more than the maximum optimal SNR limit (MONITOR --> WORP Statistics --> Interface 1 --> Link Statistics Page --> Click here for Local SNR-Table) then it causes radio receiver saturation thus impacting the performance of the link. To overcome this situation, set the TPC appropriately or enable ATPC to adjust the signal level automatically. Also, enabling DDRS can help in choosing right data rate automatically. To measure and diagnose any performance issues in the wireless link, use the Radio Link Test Tool. To use this tool, navigate to MONITOR --> WORP Statistics --> Interface 1 --> Link Statistics Page --> Details -->Click icon. For detailed description of this tool, refer Radio Link Test Tool 8.9 Recovery Procedures Recovery Procedure is used to restore the device to its factory default operating state. Depending on the device state, the recovery procedures can be classified under two modes:
1. Operational Mode: Device is up and in running state. 2. Bootloader Mode: Device operating image is deleted. 8.9.1 Operational Mode S.No 1 Scenario Restore the device to its factory default configuration while accessing it through web interface Recovery Procedure In the web interface, navigate to MANAGEMENT > Reset to Factory. The Factory Reset screen appears:
In the screen, click OK. The device now reboots and comes with:
IP Address: 169.254.128.132 Username: admin Password: public For Reload procedure using ScanTool specific to MP-835 device series, refer Reset/Reload Procedure Tsunami 800 & 8000 Series - Software Management Guide 276 S.No 2 Scenario The device is not accessible for reasons such as user has forgotten the web interface login password, Management VLAN Id is changed, wrong VLAN configuration. Recovery Procedure Press and hold the Reload button (use a pin or the end of a paper clip) on the POE injector for a time frame as mentioned in the following table:
Troubleshooting Timings 5 to 6 seconds Device MP-8200-BSU-G; MP-8100-SUA MP-8150-SUR; MP-8150-SUR-100 MP-8250-BS9-G; MP-8250-BS1-G MP-8200-BSU;MP-8250-BS9;MP-8250-BS1 MP-820-BSU-100; MP-822-BSU-100;
MP-825-BS3-100 MP-8200-SUA; MP-8250-SUR MP-825-CPE-50; MP-825-CPE-100;
MP-835-CPE-10, MP-835-CPE-25, MP-835-CPE-50, MP-835-CPE-100, MP-820-SUA-50+; MP-820-SUA-100 MP-822-SUA-100;
MP-825-SUR-50+; MP-825-SUR-100 QB-8200-EPA-G / LNK-G QB-8250-EPR / LNK-G QB-8200-EPA / LNK QB-8250-EPR / LNK QB-825-EPR/LNK-50+
QB-825-EPR/LNK-100 QB-835-EPR/LNK-25 QB-835-EPR/LNK-50 QB-826-EPR/LNK-100 To use this procedure, use a PoE injector with Reload functionality. The device operating image will get deleted, if you press the button for more than the above mentioned time. The timings mentioned above are valid from the time the device is powered UP (that is during POST). The device now reboots and comes with: IP Address: 169.254.128.132;
Username: admin; and Password: public For Reload procedure using ScanTool specific to MP-820 / 830 series devices, refer Reset/Reload Procedure Tsunami 800 & 8000 Series - Software Management Guide 277 Troubleshooting 8.9.2 Bootloader Mode S.No 1 Scenario a) The device operating image is corrupted for reasons such as power interruption while upgrading
(For only MP-820-BSU-100;
MP-822-BSU-100;
MP-820-SUA-50+;
MP-820-SUA-100;
MP-822-SUA-100;
MP-825-BS3-100;
MP-825-SUR-50+;
MP-825-SUR-100;
devices). b) The device operating image is corrupted for reasons such as power interruption while upgrading
(For all devices). 2 The device is not accessible for reasons such as user has forgotten the web interface login password, Management VLAN Id is changed, and wrong VLAN configuration. And, you do not have a reload capable PoE but Serial access is possible Recovery Procedure After powering-up the device, press and hold the Reload button on the PoE injector (use a pin or the end of a paper clip) for first 15 seconds and then release the button between 15-30 seconds. By doing so, the operating image will get deleted.
:
No reload via Ethernet cross cable. It is not applicable to MP-835-CPE-10, MP-835-CPE-25, MP-835-CPE-50, MP-835-CPE-100, MP-825-CPE-50 and MP-825-CPE-100, QB-835-EPR/LNK-25, QB-835-EPR/LNK-50 and QB-826-EPR/LNK-100 devices. After deleting the operating image, refer Using the ScanTool and Using the Bootloader CLI sections to load the firmware onto the device. For Reload procedure using ScanTool specific to MP-820 / 830 series devices, refer Reset/Reload Procedure Do one of the following:
While powering the device, press and hold the Reload button on the PoE injector (use a pin or the end of a paper clip) for 15 seconds. By doing so, the operating image will get deleted. Use a 4-pair (Gigabit) cross over Ethernet cable between the PoE and the device. By doing so, the reload functionality gets activated and forcibly deletes the operating image. If you are having serial access to the device during POST, press SHIFT+u to enter into forced user mode of the bootloader. From the Bootloader prompt, enter the command firmware_delete. After deleting the operating image, refer Using the ScanTool and Using the Bootloader CLI sections to load the firmware onto the device. If you are having serial access to the device during POST, press SHIFT+u to enter into forced user mode of the bootloader. From the Bootloader prompt, enter the command config_delete. This command will also delete the Upgrade License file. Next, issue the command reboot. The device now reboots and comes with: IP Address: 169.254.128.132;
Username: admin; and Password: public Tsunami 800 & 8000 Series - Software Management Guide 278 8.9.3 Load a New Image Follow one of the procedures below to load a new image to the device:
Using the ScanTool Using the Bootloader CLI Troubleshooting
: A new image cannot be downloaded using Bootloader CLI onto MP-835-CPE-10, MP-835-CPE-25, MP-835-CPE-50, MP-835-CPE-100, MP-825-CPE-50, MP-825-CPE-100 and QB-826-EPR/LNK-100 as it does not provide a serial interface. 8.9.3.1 Using the ScanTool To download the firmware image to the device, you will need an Ethernet connection to the computer on which the TFTP server resides and to a computer that is running ScanTool (this is either two separate computers connected to the same network or a single computer running both programs). ScanTool automatically detects the device that does not have a valid software image. The TFTP Server and Image File Name parameters are enabled in the ScanTools Change screen so that you can download a new image to the device. (These fields are disabled, if ScanTool detects a software image on the device). See Initialization. Preparing to Download the Device Image Before starting the download process, you need to know the device IP Address, Subnet Mask, the TFTP Server IP Address, and the Image file name. Make sure the TFTP server is running and properly configured to point to the folder containing the image to be downloaded. Download Procedure Follow these steps to download a software image to the device by using ScanTool:
1. Download the latest software from http://my.proxim.com, and copy it to the default directory of the TFTP server. 2. Launch Proxims ScanTool. 3. Highlight the entry for the device that you want to update and click Change. 4. Set IP Address Type to Static.
: You need to assign static IP information temporarily to the device since its DHCP client functionality is not available when no image is installed on the device. 5. Now enter the IP address, Subnet mask, Default-gateway, Server - IP address and the image filename. 6. Click OK. The device will reboot and the download starts automatically. 7. Click OK when prompted to return to the Scan List screen after the device has been updated successfully. 8. Click Cancel to close the ScanTool. After the download process is completed, the device will reboot and initialize. After successful initialization, the device is ready to be configured. 8.9.3.2 Using the Bootloader CLI To download the new device image, you will need an Ethernet connection to the computer on which the TFTP server resides. This can be any computer on the LAN or connected to the device with an Ethernet cable. You must also connect the device to a computer with a standard serial cable and use a terminal client. From the terminal, enter the CLI commands to set the IP address of the device and to download the device image. Tsunami 800 & 8000 Series - Software Management Guide 279 Troubleshooting Preparing to Download the device image Before starting, you need to know the device IP Address, Subnet Mask, the TFTP Server IP Address, and the device image file name. Make sure the TFTP server is running and configured to point to the default directory containing the image to be downloaded. Download Procedure 1. Download the latest software from http://my.proxim.com, and copy it to the default directory of the TFTP server. 2. Connect the device serial port to your computers serial port. 3. Open your terminal emulator program and set the following connection properties:
Com Port: COM1, COM2 and so on, depending on your computer Baud Rate: 115200 Data Bits: 8 Stop Bits: 1 Flow Control: None Parity: None 4. Under File > Properties > Settings > ASCII Setup, enable the Send line ends with line feeds option. Terminal Emulator program sends a line return at the end of each line of code. The terminal display shows Power On Self Tests (POST) activity. After approximately 30 seconds, a message indicates:
Starting ScanTool interface, press any key to enter CLI 5. After this message appears, press any key. Now the bootloader prompt appears as below:
Bootloader=>
5. Enter the following commands:
Bootloader=> show (to view configuration parameters and values) Bootloader=> set ipaddr <Access Point IP Address>
Bootloader=> set serverip <TFTP Server IP Address>
Bootloader=> set filename <Device Image File Name, including file extension>
Bootloader=> set gatewayip <Gateway Ip Address>
Bootloader=> set netmask <Network Mask>
Bootloader=> set ipaddrtype static Bootloader=> show (to confirm your new settings) Bootloader=> reboot Example:
Bootloader=> show Bootloader=> set ipaddr 169.254.128.132 Bootloader=> set serverip 169.254.128.133 Bootloader=> set filename image_proxim.sei Bootloader=> set gatewayip 169.254.128.133 Bootloader=> set netmask 255.255.255.0 Bootloader=> set ipaddrtype static Bootloader=> show Bootloader=> reboot The device will reboot and then download the image file. When the download process is complete, configure the device. 8.9.4 Setting IP Address using Serial Port If the ScanTool fails to scan the device and users knows the login credentials then you can set the IP address for the device using serial port. Tsunami 800 & 8000 Series - Software Management Guide 280 Troubleshooting 8.9.4.1 Hardware and Software Requirements Standard serial (RS-232) cable ASCII Terminal software 8.9.4.2 Attach the Serial Port Cable 1. Connect one end of the serial cable to the device and the other end to a serial port on your computer. 2. Power on the computer and the device. 8.9.4.3 Initializing the IP Address using CLI After connecting the cable to the serial port, you can use the CLI to communicate with the device. CLI supports the most-generic terminal emulation programs. In addition, many web sites offer shareware or commercial terminal programs that you can download. Once the IP address has been assigned, you can use the HTTP interface or the Telnet to complete the configuration. Follow these steps to assign an IP address to the device:
1. Open your terminal emulation program and set the following connection properties:
Com Port: COM1, COM2, and so on depending on your computer Baud Rate: 115200 Data Bits: 8 Stop Bits: 1 Flow Control: None Parity: None The terminal display shows Power On Self Tests (POST) activity, and then displays the software version. It prompts you to enter the CLI username and password. The commands to enter the username and password are as follows:
#################################################|
# +-++-++-++-++-++-+
# |p||r||o||x||i||m|
# +-++-++-++-++-++-+
# Version: 1.0.0 B208100
# Architecture: MIPS 7660
# Creation: 10-Aug-2009 (IST) 08:16:14 PM
#################################################|
Username: admin Password:
This process may take up to 90 seconds. 2. Enter the CLI Username and password. By default username is admin and password is public. The terminal displays a welcome message and then the CLI Prompt. Enter show ip as shown below:
System Name> show ip The following Ethernet IP information is displayed:
// Ethernet IP CONFIGURATION //
INDEX 1 IP Address: 10.0.0.1 Mask: 255.255.255.0 Address Type: static Tsunami 800 & 8000 Series - Software Management Guide 281
// IP Gateway Configuration //
Gateway IP Address: 169.254.128.1 Troubleshooting 3. Change the IP address and other network values using the following CLI commands (use your own IP address and Subnet mask). System Name> enable System Name# configure System Name(config)#network System Name(config-net)# ip System Name(config-net-ip)# ethernet-ip-table System Name(config-net-ip-etherip)# rowedit 1 ipaddress <ipaddress>
System Name(config-net-ip-etherip)# rowedit 1 mask <subnet mask>
System Name(config-net-ip-etherip)# rowedit 1 address-type <Address Type>
System Name(config-net-ip)# default-gateway <IP Gateway>
System Name(config-net-ip-etherip)#exit System Name(config-net-ip)#exit System Name(config-net)#exit System Name(config)# commit 1 System Name(config)# reboot 1 4. After the device reboots, verify the new IP address by reconnecting to the CLI. Alternatively, you can ping the device from a network computer to confirm that the new IP address has taken effect. When a proper IP address is set, use HTTP interface or Telnet to configure the rest of the operating parameters of the device. 8.10 Spectrum Analyzer The ultimate way to discover whether there is a source of interference is to use a Spectrum Analyzer. Usually, the antenna is connected to the analyzer when measuring. By turning the antenna 360, one can check the direction of the interference. The analyzer will also display the frequencies and the level of signal is detected. Proxim recommends performing the test at various locations to find the most ideal location for the equipment. 8.10.1 Avoiding Interference When a source of interference is identified and when the level and frequencies are known, the next step is to avoid the interference. Some of the following actions can be tried:
Change the channel to a frequency that has no or least interference. Try changing the antenna polarization. A small beam antenna looks only in one particular direction. Because of the higher gain of such an antenna, lowering the output power or adding extra attenuation might be required to stay legal. This solution cannot help when the source of interference is right behind the remote site. Adjusting the antenna angle/height can help to reduce the interference. Move the antennas to a different location on the premises. This causes the devices to look from a different angle, causing a different pattern in the reception of the signals. Use obstructions such as buildings, when possible, to shield from the interference. 8.10.2 Conclusion A spectrum analyzer can be a great help to identify whether interference might be causing link problems on the device. Before checking for interference, the link should be verified by testing in an isolated environment, to make sure that the hardware works and your configurations are correct. The path analysis, cabling and antennas should be checked as well. Base Announces should increase continuously. Tsunami 800 & 8000 Series - Software Management Guide 282 Registration Requests and Authentication Requests should be divisible by 3. WORP is designed in a way that each registration sequence starts with 3 identical requests. It is not a problem if, once in a while, one of those requests is missing. Missing requests frequently is to be avoided. Monitor / Per Station (Information per connected remote partner): Check that the received signal level (RSL) is the same on both sides. This should be the case if output power is the same. Two different RSLs indicate a broken transmitter or receiver. A significant difference between Local Noise and Remote Noise could indicate a source of interference near the site with the highest noise. Normally, noise is about 80 dBm at 36 Mbps. This number can vary from situation to situation, of course, also in a healthy environment. Troubleshooting 8.11 Miscellaneous 8.11.1 Unable to Retrieve Event Logs through HTTPS If using Internet Explorer 7 and are not able to retrieve event logs through HTTPS, do the following:
1. Open Internet Explorer 2. Navigate to Tool > Internet Options > Advanced 3. Go to Security and uncheck/unselect Do not save encrypted pages to disk Alternatively, use Mozilla Firefox 3.5 or later. Tsunami 800 & 8000 Series - Software Management Guide 283 Feature Applicability Given below are the feature(s) applicable to the respective point-to-point devices:
A Tsunami 800 & 8000 Series - Software Management Guide 284 Given below are the feature(s) applicable to the respective point-to-multipoint devices:
Feature Applicability Tsunami 800 & 8000 Series - Software Management Guide 285 Parameters Requiring Reboot Given below are the parameters that require the device to reboot. B Parameter(s) Web Page(s) System Configuration Applicable Device Mode*
Frequency Domain BASIC CONFIGURATION ADVANCED CONFIGURATION -> System Network Mode ADVANCED CONFIGURATION -> System Maximum MTU ADVANCED CONFIGURATION -> System Radio Mode BASIC CONFIGURATION ADVANCED CONFIGURATION -> System Controller Status ADVANCED CONFIGURATION -> System All All All All All Applicable only to MP-820-BSU-100 MP-822-BSU-100 MP-825-BS3-100 MP-820-SUA-50+
MP-820-SUA-100 MP-822-SUA-100 MP-825-SUR-50+
MP-825-SUR-100 MP-825-CPE-50 MP-825-CPE-100 MP-835-CPE-10 MP-835-CPE-25 MP-835-CPE-50 MP-835-CPE-100 QB-825-EPR/LNK-50+
QB-825-EPR/LNK-100 QB-835-EPR/LNK-25 QB-835-EPR/LNK-50 QB-826-EPR/LNK-100 Ethernet Default Gateway IP Address DNS IP Configuration (Bridge Mode) BASIC CONFIGURATION ADVANCED CONFIGURATION -> Network -> IP Configuration All All All Tsunami 800 & 8000 Series - Software Management Guide 286 Parameter(s) Web Page(s) Applicable Device Mode*
IP Configuration (Routing Mode) Parameters Requiring Reboot Ethernet Wireless Wireless (With PPPoE) Default Gateway IP Address DNS (Primary and Secondary Address) BASIC CONFIGURATION ADVANCED CONFIGURATION -> Network -> IP Configuration All All SU Mode All All NAT Status ADVANCED CONFIGURATION -> Network -> NAT SU Mode / End Mode B mode Dynamic Start Port ADVANCED CONFIGURATION -> Network -> NAT SU Mode / End Mode B mode Dynamic End Port ADVANCED CONFIGURATION -> Network -> NAT SU Mode / End Mode B mode Status ADVANCED CONFIGURATION -> Network -> PPPoE Client SU Mode PPPoE Admin Status ADVANCED CONFIGURATION -> Network -> Ethernet Ethernet Interface Properties Wireless Interface Properties ADVANCED CONFIGURATION > Wireless > Interface 1 >
Properties > Basic Tab All All Legacy Mode Sync Status ADVANCED CONFIGURATION > Wireless > Interface 1 >
Properties > Sync Tab BSU Mode Applicable to the devices MP-8200-BSU-G MP-8250-BS9-G MP-8250-BS1-G MP-8200-BSU MP-8250-BS9 MP-8250-BS1 MP-820-BSU-100 MP-822-BSU-100 MP-825-BS3-100 Upgrade Firmware and Configuration Upgrade Firmware MANAGEMENT -> File Management -> Upgrade Firmware All Upgrade Configuration MANAGEMENT -> File Management -> Upgrade Configuration All Tsunami 800 & 8000 Series - Software Management Guide 287 Parameter(s) Web Page(s) Applicable Device Mode*
Parameters Requiring Reboot Upgrade License MANAGEMENT -> File Management -> Upgrade License Applicable only to, MP-820-SUA MP-822-SUA MP-825-SUR MP-825-CPE MP-835-CPE MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 MP-8200-BSU-G MP-8200-BSU MP-8200-SUA MP-8250-BS9-G MP-8250-BS1-G MP-8250-BS9 MP-8250-BS1 MP-825-BS3-100 MP-820-BSU-100 MP-822-BSU-100 MP-8250-SUR Admin Password Monitor Password HTTP HTTP Port HTTPS SNMP Version Read Password Read / Write Password SNMP Trap Host Table HTTP / HTTPS MANAGEMENT -> Services -> HTTP / HTTPS SNMP (If SNMP v1-v2c is enabled) MANAGEMENT -> Services -> SNMP SNMP (If SNMP v3 is enabled) All All All All All All All All All All Tsunami 800 & 8000 Series - Software Management Guide 288 Web Page(s) Applicable Device Mode*
Parameters Requiring Reboot Parameter(s) SNMP Version Security Level Priv Protocol Priv Password Auth Protocol Auth Password SNMP Trap Host Table Admin Password Monitor Password Telnet Telnet Port Telnet Sessions SSH SSH Port SSH Sessions Access Table Status Management Access Control Table MANAGEMENT -> Services -> SNMP Telnet / SSH MANAGEMENT -> Services -> Telnet / SSH Management Access Control MANAGEMENT -> Access Control All All All All All All All All All All All All All All All All All All All Reset to Factory MANAGEMENT -> Reset to Factory Convert QB to MP MANAGEMENT -> Convert QB to MP Applicable only to QB-8200-EPA-G/LNK-G QB-8200-EPA/LNK QB-825-EPR/LNK -50+
QB-825-EPR/LNK -100 QB-835-EPR/LNK -25 QB-835-EPR/LNK -50 QB-826-EPR/LNK-100
* BSU: Refers to a Base Station SU Mode: Refers to both SU and CPE End Point A Mode: Refers to a device in End Point A mode End Point B Mode: Refers to a device in End Point B mode Tsunami 800 & 8000 Series - Software Management Guide 289 Frequency Domains and Channels C Introduction The Tsunami point-to-point and point-to-multipoint products are available in two SKUs: United States (US) and rest of the World (WD) markets. Depending on the SKU, the device is hard programmed at factory per the regulatory domain. Regulatory domain controls the list of frequency domains that are available in that SKU. Further each frequency domain will define the country specific regulatory rules and frequency bands. The frequency domains can be easily configured using the Web Interface as it is a drop down list with all the available domains. The following table lists all the Tsunami 800 and 8000 Series products with the applicable frequency domains and their corresponding ENUM values, SKUs supported and licensed frequency bands. US Frequency Domains Product(s) MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 Point to Multipoint Devices MP-8200-BSU-G MP-8200-BSU MP-8200-SUA MP-8250-BS9 / BS1-G MP-8250-BS9 / BS1 MP-8250-SUR US US US (For Products manufact ured prior 1st June 2016) US (For Products manufact ured after 1st June 2016) MP-820-SUA-50+
MP-820-SUA-100 MP-825-CPE-50 MP-825-CPE-100 MP-835-CPE-10 MP-835-CPE-25 MP-835-CPE-50 MP-835-CPE-100 MP-825-SUR-50+
MP-825-SUR-100 MP-825-BS3-100 MP-820-BSU-100 US Licensed Bands (in GHz) 2.4, 4.9, 5.0 5.0 4.9, 5.0 4.9, 5.0 4.9 L mask 5.0 s n i a m o D y c n e u q e r F United States 5 GHz - US*
United States 5.8 GHz - US*
United States 2.4 GHz - US*
US2 (5.3 and 5.8 GHz) - US*
United States 4.9 GHz US3 (5.2 and 5.8 GHz) - US*
US4 (4.9 and 5 GHz) - US*
US1 (5.3 and 5.4 GHz) - US*
s e u l a V M U N E 1 2 3 22 28 38 44 45
* Applicable to US SKU only
# US SKU is not applicable to QB-8150-LNK-12
** For US4, 5.3 and 5.4 GHz bands are not available.
**
Tsunami 800 & 8000 Series - Software Management Guide 290 Product(s) Licensed Bands (in GHz) United States 5 GHz - US*
United States 5.8 GHz - US*
United States 2.4 GHz - US*
US2 (5.3 and 5.8 GHz) - US*
United States 4.9 GHz US3 (5.2 and 5.8 GHz) - US*
US4 (4.9 and 5 GHz) - US*
US1 (5.3 and 5.4 GHz) - US*
i s n a m o D y c n e u q e r F l s e u a V M U N E Frequency Domains and Channels Point to Point Devices QB-8200-EPA-G/LNK-G QB-8250-EPR-G/LNK-G QB-8200-EPA/LNK QB-8250-EPR/LNK QB-825-EPR/LNK-100 QB-825-EPR/LNK-50 QB-835-EPR/LNK-25 QB-835-EPR/LNK-50 US (For Products prior 1st June 2016) US (For Products after 1st June 2016) 4.9, 5.0 4.9, 5.0 US 4.9 L mask 5.0 1 2 3 22 28 38 44 45
**
* Applicable to US SKU only
# US SKU is not applicable to QB-8150-LNK-12
** For US4, 5.3 and 5.4 GHz bands are not available. Tsunami 800 & 8000 Series - Software Management Guide 291 World Frequency Domains Product(s) MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 Point to Multipoint Devices Licensed Bands (in GHz) WD 2.4, 4.9, 5.0 WD 4.9, 5.0 Frequency Domains and Channels MP-8200-BSU-G MP-8200-SUA MP-8250-BS9 / BS1-G MP-8250-SUR MP-820-SUA-50+
MP-820-BSU-100 MP-8200-BSU MP-8250-BS9 MP-8250-BS1 WD 4.9, 5.0 MP-825-SUR-50+
MP-825-CPE-50 MP-825-CPE-100 MP-835-CPE-10 MP-835-CPE-25 MP-835-CPE-50 MP-835-CPE-100 MP-825-BS3-100 WD 4.9 L mask 5.0 i s n a m o D y c n e u q e r F World 5 GHz World 4.9 GHz World 2.4 GHz World 2.3 GHz World 2.5 GHz Canada 5 GHz WD Europe 5.8 GHz WD Europe 5.4 GHz WD-Europe 2.4 GHz Russia 5 GHz Taiwan 5 GHz WD United States 5 GHz Canada 5.8 GHz World 6.4 GHz WD UK 5.8 GHz World 5.9 GHz India 5.8 GHz Brazil 5.4 GHz Brazil 5.8 GHz Australia 5.4 GHz Australia 5.8 GHz WD United States 4.9 GHz Canada 4.9 GHz WD Japan 4.9 GHz Legacy 5GHz WD Japan 5.6 GHz WD United States 5.8 World 5.8 GHz Indonesia 5.7 GHz Egypt 5.8 GHz l s e u a V M U N E 4 5 6 7 8 9 10 11 12 13 14 1 16 17 20 21 23 24 25 26 27 28 30 19 32 33 2 35 36 39 Tsunami 800 & 8000 Series - Software Management Guide 292 Frequency Domains and Channels Product(s) Licensed Bands (in GHz) Point to Point Devices QB-8200-EPA-G/LNK-G QB-8250-EPR-G/LNK-G QB-8200-EPA/LNK QB-8250-EPR/LNK QB-825-EPR/LNK-50 QB-825-EPR/LNK-100 QB-835-EPR/LNK-25 QB-835-EPR/LNK-50 QB-826-EPR/LNK-100 WD 4.9, 5.0 WD 4.9 L mask 5.0 WD 6.4 i s n a m o D y c n e u q e r F World 5 GHz World 4.9 GHz World 2.4 GHz World 2.3 GHz World 2.5 GHz Canada 5 GHz WD-Europe 5.8 GHz WD-Europe 5.4 GHz WD-Europe 2.4 GHz Russia 5 GHz Taiwan 5 GHz WD United States 5 GHz Canada 5.8 GHz World 6.4 GHz World UK 5.8 GHz World 5.9 GHz India 5.8 GHz Brazil 5.4 GHz Brazil 5.8 GHz Australia 5.4 GHz Australia 5.8 GHz WD United States 4.9 GHz Canada 4.9 GHz WD Japan 4.9 GHz Legacy 5 GHz WD Japan 5.6 GHz WD United States 5.8 GHz World 5.8 GHz Indonesia 5.7 GHz Egypt 5.8 GHz US4 (4.9 and 5 GHz) l s e u a V M U N E 4 5 6 7 8 9 10 11 12 13 14 1 16 17 20 21 23 24 25 26 27 28 30 19 32 33 2 35 36 39 44 Tsunami 800 & 8000 Series - Software Management Guide 293 Europe Frequency Domains Point to Multipoint Devices Frequency Domains and Channels Product(s) MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 Licensed Bands (in GHz) EU 2.4, 4.9, 5.0 EU 4.9, 5.0 MP-8200-BSU-G MP-8200-SUA MP-8250-BS9-G MP-8250-SUR MP-820-BSU-100 MP-8200-BSU MP-8250-BS9 MP-8250-BS1 EU 4.9, 5.0 MP-820-SUA-50+
EU 4.9, 5.0 MP-825-SUR-50+
MP-825-CPE-50 MP-825-CPE-100 MP-835-CPE-10 MP-835-CPE-25 MP-835-CPE-50 MP-835-CPE-100 MP-825-BS3-50+
EU 5.0 Europe 5.8 GHz Europe 5.4 GHz i s UK 5.8 GHz n a m o D y c n e u q e r F Europe 2.4 GHz l s e u a V M U N E 20 10 11 12 Product(s) Licensed Bands (in GHz) Point to Point Devices QB-8200-EPA-G/LNK-G QB-8250-EPR-G/LNK-G QB-8200-EPA/LNK QB-8250-EPR/LNK QB-825-EPR/LNK-50+
QB-825-EPR/LNK-100 QB-835-EPR/LNK-25 QB-835-EPR/LNK-50 EU 4.9, 5.0 EU 5.0 Europe 5.8 GHz Europe 5.4 GHz i s UK 5.8 GHz n a m o D y c n e u q e r F Europe 2.4 GHz 20 10 11 12 l s e u a V M U N E When the device is configured by using CLI or SNMP, care has to be taken to set the domains by using a predefined ENUM value. Example: The CLI commands to set WORLD 5 GHz as frequency domain are as follows:
T8000-C1:65:7E(config)# system-configure T8000-C1:65:7E(config-sysconfig)# network-mode bridge Changes in Network mode requires Reboot. T8000-C1:65:7E(config-sysconfig)# frequency-domain ?
Possible completions:
<Use 'show supported-frequency-domains' to get supported frequency domains list>
Frequency Domain Configuration T8000-C1:65:7E(config-sysconfig)# frequency-domain 4 Changes in Frequency Domain requires Reboot. T8000-C1:65:7E(config-sysconfig)#exit T8000-C1:65:7E(config)#exit Tsunami 800 & 8000 Series - Software Management Guide 294 Frequency Domains and Channels
: All DFS countries support only 20 and 40 MHz channel bandwidths. Thailand Frequency Domains Product(s) MP-8250-SUR MP-8250-BS9 Point to Multipoint Devices Licensed Bands (in GHz) Thailand Thailand 5.0 4.9 5.0 4.9 MP-825-CPE-50 MP-835-CPE-10 MP-835-CPE-25 MP-835-CPE-50 MP-835-CPE-100 Thailand 5.0 i Thailand 5.6 GHz s Thailand 5.2 GHz n a m o D y c n e u q e r F 42 43 l s e u a V M U N E Point to Point Devices Product(s) QB-8250-EPR Licensed Bands (in GHz) i Thailand 5.6 GHz s Thailand 5.2 GHz n a m o D y c n e u q e r F Thailand 5.0 4.9 42 43 l s e u a V M U N E QB-825-EPR/LNK-50+
QB-825-EPR/LNK-100 QB-835-EPR/LNK-25 QB-835-EPR/LNK-50 Thailand 5.0 IC(Industry Canada) 5.2 GHz Frequency Domains Point to Multipoint Devices Product(s) Licensed Bands (in GHz) Industry Canada 5.2 GHz 45 MP-822-BSU-100 MP-822-SUA-100 Canada
(5.150 - 5.250) l s e u a V M U N E i s n a m o D y c n e u q e r F Tsunami 800 & 8000 Series - Software Management Guide 295 Frequency Domains and Channels 2.4 GHz Channels Frequency Domain Frequency Band
(Start Frequency ~
End Frequency in MHz) United States 2.4 GHz 2412 ~ 2462 World 2.3 GHz 2277 ~ 2397 World 2.4 GHz 2412 ~ 2472 World 2.5 GHz 2477 ~ 2507 WD-Europe 2.4 GHz 2412 ~ 2472 Europe 2.4 GHz 2412 ~ 2472 Allowed Channels (Center Frequency in GHz) 5 MHz 10 MHz 20 MHz 40 PLUS MHz 1 (2412), 2 (2417)... 10 (2457), 11 (2462). 100 (2277), 101 (2282)... 123 (2392), 124 (2397). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 200(2477), 201(2482)... 205 (2502), 206(2507). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). US SKU 1 (2412), 2 (2417)... 10 (2457), 11 (2462). World SKU 100 (2277), 101 (2282)... 122 (2387), 123 (2392). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 200(2477), 201(2482)... 205 (2502), 206(2507). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). EU SKU 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 1 (2412), 2 (2417)... 10 (2457), 11 (2462). 1 (2412), 2 (2417)... 6 (2437), 7 (2442). 101 (2282), 102 (2287)... 121(2382), 122 (2387). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 201(2482), 202 (2487)... 204(2497), 205 (2502). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 101 (2282), 102 (2287)... 117 (2362), 118 (2367). 1 (2412), 2 (2417)... 8 (2447), 9 (2452).
-
1 (2412), 2 (2417)... 8 (2447), 9 (2452). 1 (2412), 2 (2417)... 8 (2447), 9 (2452). 40 MINUS MHz 5 (2432), 6 (2437)... 10 (2457), 11 (2462). 105 (2302), 106(2307)... 121(2382), 122 (2387). 5 (2432), 6 (2437)... 12 (2467), 13 (2472).
-
5 (2432), 6 (2437)... 12 (2467), 13 (2472). 5 (2432), 6 (2437)... 12 (2467), 13 (2472). Tsunami 800 & 8000 Series - Software Management Guide 296 4.9 and 5 GHz Channels Frequency Domain Frequency Band Allowed Channels (Center Frequency in GHz)
(Start Frequency ~ End Frequency in MHz) 5 MHz 10 MHz 20 MHz 40 PLUS MHz 40 MINUS MHz Frequency Domains and Channels United States 5 GHz 5180 ~ 5240 (Non-DFS) 5260 ~ 5320 (DFS) 5500 ~ 5580 (DFS) 5660 ~ 5700 (DFS) 5745 ~ 5825 (non-DFS)
-
US SKU
-
United States 5.8 GHz 5740 ~ 5830 (Non-DFS) 148(5740), 149(5745)... 165(5825), 166(5830). United States2 (5.3, 5.8 GHz) 5260 ~ 5320 (DFS) 5745 ~ 5825 (Non-DFS)
-
149(5745), 150(5750)... 164(5820), 165(5825).
-
United States 4.9 GHz 4942 ~ 4987 (Non-DFS) 5(4942.5), 15(4947.5)... 85(4982.5), 95(4987.5). 10(4945), 20(4950)... 80(4980), 90(4985). 36(5180), 37(5185), 38(5190), 39(5195), 40(5200), 41(5205), 42(5210), 43(5215), 44(5220), 52(5260), 53(5265)... 59(5295), 60(5300). 100(5500), 101(5505)... 111(5555), 112(5560). 133(5665), 134(5670)... 135(5675), 136(5680). 149(5745), 150(5750)... 160(5800), 161(5805). 149(5745), 150(5750)... 160(5800), 161(5805). 52(5260), 53(5265)... 59(5295), 60(5300). 149(5745), 150(5750)... 160(5800), 161(5805). 40(5200), 41(5205), 42(5210), 43(5215), 44(5220), 45(5225), 46(5230), 47(5235), 48(5240), 56(5280), 57(5285)... 63(5315), 64(5320). 104(5520), 105(5525)... 115(5575), 116(5580). 136(5680), 137(5685)... 139(5695), 140(5700). 153(5765), 154(5770)... 164(5820), 165(5825). 153(5765), 154(5770)... 164(5820), 165(5825). 56(5280), 57(5285)... 63(5315), 64(5320). 153(5765), 154(5770)... 164(5820), 165(5825).
-
-
36(5180), 37(5185), 38(5190), 39(5195), 40(5200), 41(5205), 42(5210), 43(5215), 44(5220), 45(5225), 46(5230), 47(5235), 48(5240), 52(5260), 53(5265)... 63(5315), 64(5320). 100(5500), 101(5505)... 115(5575), 116(5580). 132(5660), 133(5665)... 139(5695), 140(5700). 149(5745), 150(5750)... 164(5820), 165(5825). 149(5745), 150(5750)... 164(5820), 165(5825). 52(5260), 53(5265)... 63(5315), 64(5320). 149(5745), 150(5750)... 164(5820), 165(5825). 20(4950), 30(4955)... 70(4975), 80(4980). Tsunami 800 & 8000 Series - Software Management Guide 297 Frequency Domain Frequency Band Allowed Channels (Center Frequency in GHz) Frequency Domains and Channels 10 MHz 20 MHz 40 PLUS MHz 40 MINUS MHz
(Start Frequency ~ End Frequency in MHz) United States3 (5.2, 5.8 GHz) 5180 ~ 5240 (Non-DFS) 5745 ~ 5825 (Non-DFS) Please note that all 82x and 8xxx SKUs support this frequency. 5 MHz 36(5180), 37(5185), 38(5190), 39(5195), 40(5200), 41(5205), 42(5210), 43(5215), 44(5220), 45(5225), 46(5230), 47(5235), 48(5240), 148(5740), 149(5745)... 165(5825), 166(5830). 36(5180), 37(5185), 38(5190), 39(5195), 40(5200), 41(5205), 42(5210), 43(5215), 44(5220), 45(5225), 46(5230), 47(5235), 48(5240), 149(5745), 150(5750)... 164(5820), 165(5825).
-
-
United States4 (4.9, 5 GHz) 4950 - 4980 (Non-DFS) 5180 - 5195 (Non-DFS) 5205 - 5240 (Non-DFS) 5260 - 5295 (DFS) 5305 - 5320 (DFS) 5500 - 5580 (DFS) 5660 - 5700 (DFS) 5745 - 5825 (Non-DFS) 36(5180), 37(5185), 38(5190), 39(5195), 40(5200), 41(5205), 42(5210), 43(5215), 44(5220), 149(5745), 150(5750)... 160(5800), 161(5805). 40(5200), 41(5205), 42(5210), 43(5215), 44(5220), 45(5225), 46(5230), 47(5235), 48(5240), 153(5765), 154(5770)... 164(5820), 165(5825).
-
-
36(5180), 37(5185), 38(5190), 39(5195), 40(5200), 41(5205), 42(5210), 43(5215), 44(5220), 45(5225), 46(5230), 47(5235), 48(5240), 149(5745), 150(5750)... 164(5820), 165(5825). 20 (4950), 30 (4955), 40 (4960), 50 (4965), 60 (4970), 70 (4975), 80 (4980). 36 (5180), 37 (5185), 38 (5190), 39 (5195). 41 (5205), 42 (5210).... 47 (5235), 48 (5240). 52 (5260), 53 (5265).... 58 (5290), 59 (5295). 61 (5305), 62 (5310), 63 (5315), 64 (5320). 100 (5500), 101 (5505).... 115 (5575), 116 (5580). 132 (5660), 133 (5665).... 139 (5695), 140 (5700). 149 (5745), 150 (5750).... 164 (5820), 165 (5825). Japan 4.9 GHz 4912 ~ 4980 (Non-DFS) Japan SKU 182(4912.5), 183(4917.5)... 188(4942.5), 189(4947.5). 183(4915), 184(4920)... 188(4940), 189(4945). 184(4920), 188(4940), 192(4960), 196(4980). 184(4920), 192(4960). 188(4940), 196(4980). Tsunami 800 & 8000 Series - Software Management Guide 298 Frequency Domain Frequency Band Allowed Channels (Center Frequency in GHz) Frequency Domains and Channels 10 MHz 20 MHz 40 PLUS MHz 40 MINUS MHz
(Start Frequency ~ End Frequency in MHz) Japan 5.6 GHz 5500 ~ 5700 (DFS) WD United States 5 GHz 5180 ~ 5240 (Non-DFS) 5260 ~ 5320 (DFS) 5500 ~ 5580 (DFS) 5660 ~ 5700 (DFS) 5745 ~ 5825 (non-DFS)
-
-
5 MHz
-
World SKU
-
100(5500) 104(5520) 108(5540) 112(5560) 116(5580) 120(5600) 124(5620) 128(5640) 132(5660) 136(5680) 140(5700) 36(5180), 37(5185), 38(5190), 39(5195), 40(5200), 41(5205), 42(5210), 43(5215), 44(5220), 45(5225), 46(5230), 47(5235), 48(5240), 52(5260), 53(5265)... 63(5315), 64(5320). 100(5500), 101(5505)... 115(5575), 116(5580). 132(5660), 133(5665)... 139(5695), 140(5700). 149(5745), 150(5750)... 164(5820), 165(5825). 32(5160), 33(5165)... 213(6065), 214(6070). 182(4910), 183(4915) 187(4935), 188(4940). 10(4945), 20(4950) 90(4985), 100(4990). 100(5500) 108(5540) 116(5580) 124(5620) 136(5680) 104(5520) 112(5560) 120(5600) 128(5640) 140(5700) 36(5180), 37(5185), 38(5190), 39(5195), 40(5200), 41(5205), 42(5210), 43(5215), 44(5220), 52(5260), 53(5265)... 59(5295), 60(5300). 100(5500), 101(5505)... 111(5555), 112(5560). 133(5665), 134(5670)... 135(5675), 136(5680). 149(5745), 150(5750)... 160(5800), 161(5805). 32(5160), 33(5165)... 209(6045), 210(6050). 182(4910), 183(4915) 187(4935), 188(4940). 10(4945), 20(4950) 50(4965), 60(4970). 40(5200), 41(5205), 42(5210), 43(5215), 44(5220), 45(5225), 46(5230), 47(5235), 48(5240), 56(5280), 57(5285)... 63(5315), 64(5320). 104(5520), 105(5525)... 115(5575), 116(5580). 136(5680), 137(5685)... 139(5695), 140(5700). 153(5765), 154(5770)... 164(5820), 165(5825). 36(5180), 37(5185)... 213(6065), 214(6070). 186(4930), 187(4935), 188(4940), 10(4945), 20(4950) 90(4985), 100(4990). World 5 GHz 5155 ~ 6075 (Non-DFS) Please note that 8200 & 82x SKUs support upto 5920 MHz frequency. World 4.9 GHz 4905 ~ 4995 (Non-DFS) 31(5155), 32(5160)... 214(6070), 215(6075). 181(4905), 182(4910) 187(4935), 188(4940). 10(4945), 20(4950) 100(4990), 110(4995). 31(5155), 32(5160)... 214(6070), 215(6075). 181(4905), 182(4910) 187(4935), 188(4940). 10(4945), 20(4950) 100(4990), 110(4995). Tsunami 800 & 8000 Series - Software Management Guide 299 Frequency Domain Frequency Band Allowed Channels (Center Frequency in GHz) Frequency Domains and Channels 10 MHz 20 MHz 40 PLUS MHz 40 MINUS MHz
(Start Frequency ~ End Frequency in MHz) World 5.9 GHz 5880 ~ 5920 (Non-DFS) 5 MHz 176(5880), 177(5885)... 183(5915), 184(5920). Canada 5 GHz 5255 ~ 5325 (DFS) 5495 ~ 5585 (DFS) 5655 ~ 5705 (DFS) WD-Europe 5.4 GHz 5495 ~ 5585 (DFS) 5655 ~ 5705 (DFS) WD-Europe 5.8 GHz 5735 ~ 5870 (DFS)
-
-
-
176(5880), 177(5885)... 183(5915), 184(5920).
-
-
-
Russia 5 GHz 5155 ~ 6075 (Non-DFS) Please note that 8200 & 82x SKUs support upto 5920 MHz frequency. 31(5155), 32(5160)... 214(6070), 215(6075). Taiwan 5 GHz 5495 ~ 5705 (DFS) 5740 ~ 5810 (Non-DFS)
-
31(5155), 32(5160)... 214(6070), 215(6075).
-
India 5.8 GHz 5830 ~ 5870 (Non-DFS) 5735 ~ 5855 (Non-DFS) Canada 5.8 GHz WD U.K 5.8 GHz 166(5830), 167(5835)... 173(5865), 174(5870). 147(5735), 148(5740)... 170(5850), 171(5855). 166(5830), 167(5835)... 173(5865), 174(5870). 147(5735), 148(5740)... 170(5850), 171(5855). 5730 ~ 5790 (DFS) 5820 ~ 5845 (DFS)
-
-
177(5885), 178(5890)... 182(5910), 183(5915). 52(5260), 53(5265)... 63(5315), 64(5320). 100(5500), 101(5505)... 115(5575), 116(5580). 132(5660), 133(5665)... 139(5695), 140(5700). 100(5500), 101(5505)... 115(5575), 116(5580). 132(5660), 133(5665)... 139(5695), 140(5700). 149(5745), 150(5750)... 172(5860), 173(5865). 32(5160), 33(5165)... 213(6065), 214(6070). 100(5500), 101(5505)... 139(5695), 140(5700). 149(5745), 150(5750)... 160(5800), 161(5805). 167(5835), 168(5840)... 172(5860), 173(5865). 148(5740), 149(5745)... 169(5845), 170(5850). 147(5735), 148(5740)... 156(5780), 157(5785). 167(5835). 177(5885) 178(5890) 179(5895) 181(5905) 182(5910) 183(5915) 52(5260), 53(5265)... 59(5295), 60(5300). 100(5500), 101(5505)... 111(5555), 112(5560). 132(5660), 133(5665)... 135(5675), 136(5680). 100(5500), 101(5505)... 111(5555), 112(5560). 132(5660), 133(5665)... 135(5675), 136(5680). 149(5745), 150(5750) 168(5840), 169(5845). 32(5160), 33(5165)... 209(6045), 210(6050). 100(5500), 101(5505)... 135(5675), 136(5680). 149(5745), 150(5750)... 156(5780), 157(5785). 167(5835) 168(5840) 169(5845) 148(5740), 149(5745)... 165(5825), 166(5830). 147(5735), 148(5740)... 152(5760), 153(5765). 56(5280), 57(5285)... 63(5315), 64(5320). 104(5520), 105(5525)... 115(5575), 116(5580). 136(5680), 137(5685)... 139(5695), 140(5700). 104(5520), 105(5525)... 115(5575), 116(5580). 136(5680), 137(5685)... 139(5695), 140(5700). 153(5765), 154(5770)... 172(5860), 173(5865). 36(5180), 37(5185)... 213(6065), 214(6070). 104(5520), 105(5525)... 139(5695), 140(5700). 153(5765), 154(5770)... 160(5800), 161(5805). 171(5855) 172(5860) 173(5865) 152(5760), 153(5765)... 169(5845), 170(5850). 151(5755), 152(5760)... 156(5780), 157(5785). Tsunami 800 & 8000 Series - Software Management Guide 300 Frequency Domain Frequency Band Allowed Channels (Center Frequency in GHz) Frequency Domains and Channels 10 MHz 20 MHz 40 PLUS MHz 40 MINUS MHz
(Start Frequency ~ End Frequency in MHz) Australia 5.4 GHz 5475 ~ 5595 (DFS) 5655 ~ 5720 (DFS) 5 MHz
-
-
Australia 5.8 GHz Brazil 5.4 GHz Brazil 5.8 GHz 5730 ~ 5845 (Non-DFS) 146(5730), 147(5735) 168(5840), 169(5845). 146(5730), 147(5735)... 148(5740), 169(5845). 5475 ~ 5720 (DFS)
-
-
5730 ~ 5845 (Non-DFS) Canada 4.9 GHz 4945 ~ 4985 (Non-DFS) 146(5730), 147(5735)... 168(5840), 169(5845). 10(4945), 20(4950)... 80(4980), 90(4985). Egypt 5.8 GHz 5.725 ~ 5.85(DFS) NA Legacy 5GHz 5150 ~ 6080 (Non-DFS) Please note that 8200 & 82x SKUs support upto 5920 MHz frequency. WD Japan 4.9 4912 ~ 4980 (Non-DFS) Please note that 8100 SKUs does not support this frequency. 30(5150), 31(5155)... 215(6075), 216(6080). 182(4912.5), 183(4917.5)... 188(4942.5), 189(4947.5). 146(5730), 147(5735)... 168(5840), 169(5845). 10(4945), 20(4950)... 80(4980), 90(4985). 146(5730), 147(5735)... 168(5840), 169(5845). 30(5150), 32(5160)... 214(6070), 216(6080). 183(4915), 184(4920)... 188(4940), 189(4945). WD-Japan 5.6 5500 ~ 5700 (DFS)
-
-
WD United States 4.9 GHz 4942 ~ 4987 (Non-DFS) 5(4942.5), 15(4947.5)... 85(4982.5), 95(4987.5), 10(4945), 20(4950)... 80(4980), 90(4985). 96(5480), 97(5485) 113(5565), 114(5570). 132(5660), 133(5665) 138(5690), 139(5695). 147(5735), 148(5740)... 163(5815), 164(5820). 96(5480), 97(5485) 138(5690), 139(5695). 147(5735), 148(5740)... 163(5815), 164(5820). 20(4950), 30(4955), 40(4960). NA
-
100(5500), 101(5505) 117(5585), 118(5590). 136(5680), 137(5685) 142(5710), 143(5715). 151(5755), 152(5760) 167(5835), 168(5840). 100(5500), 101(5505) 142(5710), 143(5715). 151(5755), 152(5760)... 167(5835), 168(5840). 60(4970), 70(4975), 80(4980). NA
-
184(4920) 192(4960) 188(4940) 196(4980) 100(5500) 108(5540) 116(5580) 124(5620) 136(5680) 104(5520) 112(5560) 120(5600) 128(5640) 140(5700)
-
-
96(5480), 97(5485) 117(5585), 118(5590). 132(5660), 133(5665) 142(5710), 143(5715). 147(5735), 148(5740) 167(5835), 168(5840). 96(5480), 97(5485) 142(5710), 143(5715). 147(5735), 148(5740)... 167(5835), 168(5840). 20(4950), 30(4955)... 70(4975), 80(4980). 147(5735), 148(5740)... 167(5835), 168(5840). 30(5150), 34(5170)... 210(6050), 216(6070). 184(4920), 188(4940), 192(4960), 196(4980). 100(5500) 104(5520) 108(5540) 112(5560) 116(5580) 120(5600) 124(5620) 128(5640) 132(5660) 136(5680) 140(5700) 20(4950), 30(4955)... 70(4975), 80(4980). Tsunami 800 & 8000 Series - Software Management Guide 301 Frequency Domain Frequency Band Allowed Channels (Center Frequency in GHz) Frequency Domains and Channels
(Start Frequency ~ End Frequency in MHz) WD United States 5.8 GHz 5740 ~ 5830 (Non-DFS) World 5.8 GHz 5720 ~ 5855 (Non-DFS) Indonesia 5.7 GHz 5730 ~ 5820 (Non-DFS) Thailand 5.2 GHz 5170 ~ 5330 (Non-DFS) Thailand 5.6 GHz 5490 ~ 5835 (Non-DFS) Industry Canada (IC) 5.2 GHz 5125 ~ 5250(Non-DFS) 5 MHz 148(5740), 149(5745)... 165(5825), 166(5830). 144(5720), 145(5725)... 170(5850), 171(5855). 146(5730), 147(5735)... 163(5815), 164(5820). 35(5170), 36(5180)..... 64(5320), 65(5330). 99(5490), 100(5500)... 165(5825), 166(5830). 31(5155), 32(5160), 33(5165), 34(5170), 35(5175), 36(5180), 37(5185), 38(5190), 39(5195), 40(5200), 41(5205), 42(5210), 43(5215), 44(5220), 45(5225), 46(5230), 47(5235), 48(5240), 49(5245). 10 MHz 20 MHz 40 PLUS MHz 40 MINUS MHz 149(5745), 150(5750)... 164(5820), 165(5825). 144(5720), 145(5725)... 170(5850), 171(5855). 146(5730), 147(5735)... 163(5815), 164(5820). 35(5170), 36(5180)..... 64(5320), 65(5330). 99(5490), 100(5500)... 165(5825), 166(5830). 31(5155), 32(5160), 33(5165), 34(5170), 35(5175), 36(5180), 37(5185), 38(5190), 39(5195), 40(5200), 41(5205), 42(5210), 43(5215), 44(5220), 45(5225), 46(5230), 47(5235), 48(5240), 49(5245). 149(5745), 150(5750)... 160(5800), 161(5805). 145(5725), 146(5730)... 165(5825), 166(5830). 153(5765), 154(5770)... 164(5820), 165(5825). 149(5745), 150(5750)... 169(5845), 170(5850).
--
--
36(5180), 37(5185)... 59(5295), 60(5300). 100(5500) 101(5505)... 160(5800), 161(5805). 32(5160), 33(5165), 34(5170), 35(5175), 36(5180), 37(5185), 38(5190), 39(5195), 40(5200), 41(5205), 42(5210), 43(5215), 44(5220). 40(5200), 41(5205).... 63(5315), 64(5320). 104(5520), 105(5525)... 164(5820), 165(5825). 36(5180), 37(5185), 38(5190), 39(5195), 40(5200), 41(5205), 42(5210), 43(5215), 44(5220), 45(5225), 46(5230), 47(5235), 48(5240). 149(5745), 150(5750)... 164(5820), 165(5825). 145(5725), 146(5730)... 169(5845), 170(5850). 147(5735), 148(5740)... 162(5810), 163(5815). 36(5180), 37(5185)... 63(5315), 64(5320). 100(5500) 101(5505)... 164(5820), 165(5825). 32(5160), 33(5165), 34(5170), 35(5175), 36(5180), 37(5185), 38(5190), 39(5195), 40(5200), 41(5205), 42(5210), 43(5215), 44(5220), 45(5225), 46(5230), 47(5235), 48(5240). Tsunami 800 & 8000 Series - Software Management Guide 302 Frequency Domain Frequency Band Allowed Channels (Center Frequency in GHz)
(Start Frequency ~ End Frequency in MHz) 5 MHz EU SKU 10 MHz 20 MHz 40 PLUS MHz 40 MINUS MHz Frequency Domains and Channels U.K 5.8 GHz 5730 ~ 5790 (DFS) 5820 ~ 5845 (DFS) Europe 5.8 GHz Europe 5.4 GHz 5735 ~ 5870 (DFS) 5495 ~ 5585 (DFS) 5655 ~ 5705 (DFS)
-
-
-
-
-
-
147(5735), 148(5740)... 156(5780), 157(5785). 167(5835) 149(5745), 150(5750)... 172(5860), 173(5865). 100(5500), 101(5505)... 115(5575), 116(5580). 132(5660), 133(5665)... 139(5695), 140(5700). 147(5735), 148(5740)... 152(5760), 153(5765). 149(5745), 150(5750) 168(5840), 169(5845). 100(5500), 101(5505)... 111(5555), 112(5560). 132(5660), 133(5665)... 135(5675), 136(5680). 151(5755), 152(5760)... 156(5780), 157(5785). 153(5765), 154(5770)... 172(5860), 173(5865). 104(5520), 105(5525)... 115(5575), 116(5580). 136(5680), 137(5685)... 139(5695), 140(5700). 6.4 GHz Channels Frequency Domain Frequency Band
(Start Frequency ~ End Frequency in MHz) World 6.4 GHz 5905 ~ 6420 Allowed Channels (Center Frequency) 5 MHz 10 MHz 20 MHz 40 PLUS MHz 40 MINUS MHz 181 (5905), 182 (5910)... 283 (6415), 284 (6420). 181 (5905), 182 (5910)... 283 (6415), 284 (6420). 182 (5910), 183 (5915)... 282 (6410), 283 (6415). 182 (5910), 183 (5915)... 278 (6390), 279 (6395). 186 (5930) 187 (5935)... 282 (6410), 283 (6415).
: The center frequency listed in the above tables are based on channel offset set to 0. If channel offset is set to any value other than 0 then the center frequency will be shifted accordingly. You can set the channel offset ranging from in MP-835-CPE-10, MP-835-CPE-25, MP-835-CPE-50, MP-835-CPE-100, MP-825-CPE-50,
-2 to +2 MHz MP-825-CPE-100, MP-820-SUA-50+, MP-820-SUA-100, MP-822-SUA-100, MP-825-SUR-50+, MP-825-SUR-100 and QB-826-EPR/LNK-100. Details for 40MHz Bandwidth While choosing 40MHz bandwidth, you can select 40 PLUS (Upper Extension) or 40 MINUS (Lower Extension). 40 PLUS means the center frequency calculation is done for 20MHz and add another 20MHz to the top edge of 20MHz. 40 MINUS means the center frequency calculation is done for 20MHz and add another 20MHz to the bottom edge of 20MHz. For 40 PLUS 2.4GHz ->
Channel 1 = 2412 MHz Bandwidth starts from 2403 MHz and ends at 2442 MHz Tsunami 800 & 8000 Series - Software Management Guide 303 Frequency Domains and Channels 5GHz ->
Channel 52 = 5260 MHz Bandwidth starts from 5251 MHz and ends at 5290 MHz 6.4GHz ->
Channel 181 = 5910 MHz Bandwidth starts from 5901 MHz and ends at 5940 MHz For 40 MINUS 2.4GHz ->
Channel 5 = 2432 MHz Bandwidth starts from 2403 MHz and ends at 2442 MHz 5GHz ->
Channel 56 = 5280 MHz Bandwidth starts from 5251 MHz and ends at 5290 MHz Tsunami 800 & 8000 Series - Software Management Guide 304 Frequency Domains and Channels 6.4GHz ->
Channel 186 = 5930 MHz Bandwidth starts from 5901 MHz and ends at 5940 MHz Tsunami 800 & 8000 Series - Software Management Guide 305 LACP - Device Management D Tsunami Quickbridge devices that are part of the LACP link cannot be managed through the switches, so it is recommended to use the second Ethernet port for management.
:
When using second Ethernet port for management, ensure to disable Auto Shutdown for Ethernet2. See Auto Shutdown). STP/LACP Frames should be set to passthru. See Filtering (Bridge Only)
: Whenever the Ethernet port1 is connected to CTM2 device and the Ethernet port2 is connected to PC via a passive PoE (Without the AC Power plugged in, Part No: PD-4401). Proxim recommends the usage of PD-4401 for passive PoE, as the other PoEs cannot guarentee the desired Ethernet Sync functionality Figure D-1 Ethernet Port2 of 8xxx device connected to a PC via a Passive PoE (Proxim recommends PoE Adapter with Part number PD-4401 to be used as Passive PoE) In this chapter, we have chosen the following two examples to explain the device management in the LACP link, by using the second Ethernet port. Tsunami 800 & 8000 Series - Software Management Guide 306 Example1 LACP - Device Management Figure D-2 Device Management with No VLAN In this example, we have considered a network with two QuickBridge links each supporting LACP mode. In this setup, VLAN is not configured on both LACP switches and devices. The Ethernet1 of all the devices is connected to the LACP port and is used for data transfer. To manage the devices, use a dedicated management Personal Computer per QuickBridge link. Use Ethernet2 port of the device to connect the Personal Computer.
: In Fail Over Mode (if one of the link goes down), the remote device of a particular link cannot be managed. Example2 Tsunami 800 & 8000 Series - Software Management Guide 307 Figure D-3 Device Management with VLAN LACP - Device Management In this example, we have considered a network with two QuickBridge links each supporting LACP mode. In this setup, Ethernet 1 of all the devices is connected to the LACP port, with no VLAN. The Ethernet 2 of all the devices is connected to the tagged VLAN management port with Spanning Tree enabled. To manage all the devices in the QuickBridge network, use one dedicated management Personal Computer connected to the untagged VLAN port of the switch. To manage the devices, configure same management VLAN Id on all the devices. The Ethernet 1 should be configured in transparent VLAN mode to allow data transfer. The Ethernet2 can be configured either in transparent mode or trunk mode to allow management traffic to the devices. With Spanning Tree enabled on the LACP Switches, you will be able to manage all the QuickBridge devices, even if one of the wireless link goes down. For VLAN configuration, refer VLAN (Bridge Mode Only). Tsunami 800 & 8000 Series - Software Management Guide 308 QinQ E The Subscribers and End Point devices support QinQ VLAN feature that enables service providers to use a single VLAN ID to support multiple customer VLANs by encapsulating the 802.1Q VLAN tag within another 802.1Q frame. The benefits with QinQ are as follows:
Increases the VLAN space in a provider network or enterprise backbone Reduce the number of VLANs that a provider needs to support within the provider network for the same number of customers Enables customers to plan their own VLAN IDs, without running into conflicts with service provider VLAN IDs Provides a simple Layer 2 VPN solution for small-sized MAN (Metropolitan Area Networks) or Intranet Provides customer traffic isolation at Layer 2 within a service provider network Consider a BSU and SU network, with QinQ (Double VLAN (Q in Q) Status) enabled on the SU. Subscriber:
Based on the Ethernet VLAN configuration on the Subscriber, the data packets are tagged as follows:
Access Mode: SU double tags the packet with Access VLAN ID as inner tag and Service VLAN ID as outer tag.
: When Double VLAN is enabled on the device, the Access VLAN ID should not be set to -1. Trunk Mode: SU expects a tagged packet (inner tag) and tags the packet with Service VLAN ID as outer tag.
: When Double VLAN is enabled on the device, the Port VLAN ID should not be set to -1. Transparent Mode: When QinQ is enabled, SU cannot be configured in the Transparent mode. In case of downlink traffic, SU always expects double tagged packet from the wireless side. If the outer VLAN tag matches with Service VLAN ID then SU will untag the packet and forward to Ethernet. Based on Ethernet VLAN configuration, the data packets are handled accordingly. When the outer VLAN tag does not match the Service VLAN ID, the packet is dropped. Different outer VLAN IDs can be configured for different SUs, but those VLAN IDs should also be configured on the BSU Ethernet. Base Station:
BSU always considers the first VLAN tag available in the packet; in case of double tagged packet it is the outer VLAN ID. Trunk Mode: The outer tag of the packet arriving at the Ethernet side should match with the VLAN ID configured in the trunk table. Transparent Mode: When configured in transparent mode, ensure the data packet is double tagged. Device Management From the BSU Ethernet side, the BSU/SU can be managed with a single VLAN tagged packet that matches the Management VLAN ID. From the SU Ethernet side, only SU can be managed with a single VLAN tagged packet that matches the Management VLAN ID; BSU cannot be managed from the SU Ethernet side. Tsunami 800 & 8000 Series - Software Management Guide 309 QinQ
:
In a QuickBridge link, Q-in-Q should be enabled either on an End Point A or an End Point B. The user configurable TPID is only used in the Service Provider VLAN tag. The Inner or customer VLAN tag should always have TPID as 0x8100. An Example:
The following diagram is the pictorial representation of how traffic flows in a QinQ enabled network. The Computer behind SU can be used to manage the SU. To manage BSU, connect another Computer to BSU Ethernet port through a VLAN switch with PVID as 100. Tsunami 800 & 8000 Series - Software Management Guide 310 BSU Redundancy F The BSU Redundancy feature can help in reducing the network outage in case of the Primary BSU failure. This feature enables the SU to keep track of the Primary and the Secondary BSU availability through a proprietary protocol. This allows the SU to switch between the Primary and the Secondary BSU depending on the link status. If both the BSUs are not available, the SU attempts to find any other BSU within its network. Configuration Guidelines This feature is activated only on a SU. By default, it is disabled. Use a non-empty string to enable this feature and an empty string to disable this feature. When this feature is enabled, it is mandatory to configure both the Primary and the Secondary BSU name on the SU. The Primary and the Secondary BSU names should be unique. It is expected that the Primary and the Secondary BSUs are connected to the same L2 Broadcast domain and are configured with the same Network Name as the SU. Example SU SU1 SU SUn Primary BSU Secondary BSU Other BSU POE POE POE Switch ThePrimaryandtheSecondaryBSUsareinthesameL2Broadcastdomain. Figure F-1 An Example - BSU Redundancy Feature Tsunami 800 & 8000 Series - Software Management Guide 311 Log Samples for BSU Redundancy SU - During Boot Up BSU Redundancy Channel 160 is set as the current channel. SU is trying to register with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26). SU received QoS Class: Unlimited Best Effort (indx: 1). SU registered with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26) on channel 160(0x14004A0) (SNR: A1:46 A2:0 A3:40[dB]) at WORP port[ 0 ]. Link Profile Index: 1. Wireless: WORP Link Established with Primary BSU: BSU1 Wireless: SU discovered Secondary BSU:BSU2 on channel:60 After getting connected to the Primary BSU, the SU should discover the secondary BSU. Primary BSU Down - Connected to Secondary BSU SU unregistered from BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26). Channel 60 is set as the current channel. SU is trying to register with BSU: BSU2 (MAC: 00:0b:6b:b7:4b:ff). SU received QoS Class: Unlimited Best Effort (indx: 1). SU registered with BSU: BSU2 (MAC: 00:0b:6b:b7:4b:ff) on channel 60(0x78043C) (SNR: A1:51 A2:0 A3:49[dB]) at WORP port[ 0 ]. kernel:Worp: Link Profile Index: 1. Wireless: WORP Link Established with Secondary BSU: BSU2 Connected to Other BSU 01:52:25 kernel:Worp: WARNING: Channel 100 is set as the current channel. 01:52:25 kernel:Worp: SU is trying to register with BSU: BSU3 (MAC: 00:20:a6:d3:ed:e5). 01:52:25 kernel:Worp: SU received QoS Class: Unlimited Best Effort (index: 1). 01:52:25 kernel:Worp: SU registered with BSU: BSU3 (MAC: 00:20:a6:d3:ed:e5) on channel 100(0xC80464) (SNR:
A1:58 A2:0 A3:54[dB]) at WORP port[ 0 ]. 01:52:25 kernel:Worp: Link Profile Index: 1. 01:52:25: Wireless: WORP Link Established with Other BSU: BSU3 01:54:35: Wireless: SU discovered Secondary BSU:BSU2 on channel:60 01:54:35: Wireless: SU discovered Primary BSU:BSU1 on channel:160 SU should discover both the Primary and the Secondary BSU, and connect to the Primary BSU after the switch time interval. BSU Switch Time Interval - 15 Minutes 1Wireless: WORP Link Established with Secondary BSU: BSU2 00:08:34: Wireless: SU discovered Primary BSU:BSU1 on channel:160 00:23:34 kernel:Worp: SU unregistered from BSU: BSU2 (MAC: 00:0b:6b:b7:4b:ff). 00:23:34 kernel:Worp: WARNING: Channel 0 is set as the current channel. 00:23:35 kernel:Worp: SU is trying to register with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26). 00:23:35 kernel:Worp: SU received QoS Class: Unlimited Best Effort (indx: 1). Tsunami 800 & 8000 Series - Software Management Guide 312 00:23:35 kernel:Worp: SU registered with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26) on channel 160(0x14004A0) (SNR:
A1:43 A2:0 A3:36[dB]) at WORP port[ 0 ]. 00:23:35 kernel:Worp: Link Profile Index: 1. 00:23:35: Wireless: WORP Link Established with Primary BSU: BSU1 00:24:34: Wireless: SU discovered Secondary BSU:BSU2 on channel:60 BSU Redundancy Connect to Primary BSU 01:59:25: Wireless: WORP Link Established with Other BSU: BSU3 02:02:25 kernel:Worp: SU unregistered from BSU: BSU3 (MAC: 00:20:a6:d3:ed:e5).. 02:02:25: Wireless: SU discovered Secondary BSU:BSU2 on channel:60 02:02:25: Wireless: SU discovered Primary BSU:BSU1 on channel:160 02:02:25 kernel:Worp: SU is trying to register with BSU: BSU2 (MAC: 00:0b:6b:b7:4b:ff). 02:02:25 kernel:Worp: SU received QoS Class: Unlimited Best Effort (indx: 1). 02:02:25 kernel:Worp: SU registered with BSU: BSU2 (MAC: 00:0b:6b:b7:4b:ff) on channel 60(0x78043C) (SNR:
A1:37 A2:0 A3:35[dB]) at WORP port[ 0 ]. 02:02:25: Wireless: WORP Link Established with Secondary BSU: BSU2 02:04:25 kernel:Worp: SU unregistered from BSU: BSU2 (MAC: 00:0b:6b:b7:4b:ff). 02:04:25 kernel:Worp: SU is trying to register with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26). 02:04:25 kernel:Worp: SU registered with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26) on channel 160(0x14004A0)
(SNR: A1:46 A2:0 A3:42[dB]) at WORP port[ 0 ]. 02:05:25: Wireless: SU discovered Secondary BSU:BSU2 on channel:60 02:04:25: Wireless: WORP Link Established with Primary BSU: BSU1 No Response Message 03:32:25 kernel:Worp: WARNING: Channel 0 is set as the current channel. 03:32:25 kernel:Worp: SU is trying to register with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26). 03:32:25 kernel:Worp: SU received QoS Class: Unlimited Best Effort (indx: 1). 03:32:25 kernel:Worp: SU registered with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26) on channel 160(0x14004A0) (SNR:
A1:45 A2:0 A3:42[dB]) at WORP port[ 0 ]. 03:32:25 kernel:Worp: Link Profile Index: 1. 03:32:25: Wireless: WORP Link Established with Primary BSU: BSU1 03:33:25: Wireless: SU discovered Secondary BSU:BSU2 on channel:60 03:40:43: Wireless: Secondary BSU: BSU2 not Available Tsunami 800 & 8000 Series - Software Management Guide 313 Bootloader CLI and ScanTool Bootloader CLI G The Bootloader CLI is a minimal subset of the normal CLI that is used to perform initial configuration of the device. The Bootloader CLI is available when the device embedded software is not running. This interface is only accessible through the serial interface, if:
The device does not contain a software image An existing image is corrupted An automatic (default) download of image over TFTP has failed The Bootloader CLI provides the ability to configure the initial setup parameters; and depending on this configuration, a software file is downloaded to the device during startup. The Bootloader CLI supports the following commands:
factory_reset: Restore the factory settings help: Print Online Help reboot: Reboot the device set: Set the parameters show: Show the parameters The Bootloader CLI supports the following parameters (for viewing and modifying):
ipaddr: IP Address systemname: System Name gatewayip: Gateway IP Address serverip: Server IP Address ipaddrtype: IP Address Type netmask: Net Mask filename: Image file name (including the file extension) If the Bootloader fails to load the firmware from flash, it tries to get the firmware from the network. While trying to get firmware from the network, the device should be powered on using Ethernet 1 interface of the device. The default configuration of the Bootloader parameters are as follows:
Parameter Value ipaddr netmask gatewayip systemname serverip filename ipaddrtype 169.254.128.132 255.255.255.0 169.254.128.132 systemname 169.254.128.133 imagename dynamic Tsunami 800 & 8000 Series - Software Management Guide 314 Bootloader CLI and ScanTool To Load the Firmware from the Network Use the show command to view the parameters and their values, and use the set command to set the parameter value. To Load the Firmware by using Dynamic IP Parameters 1. Set the ipaddrtype to dynamic 2. Run the BOOTP and TFTP Servers followed by device reboot When the device reboots, the device gets the IP Address and Boot filename from the BOOTP server. You need not change any of the default Bootloader parameters. After BOOTP succeeds, the device initiates a TFTP request with the filename it gets from BOOTP. To Load the Firmware by using Static IP Parameters 1. Use the set command to set the IP parameters like ipaddr, serverip, filename and also set the parameter ipaddrtype to static. 2. Run the TFTP Server followed by device reboot. When the device reboots, the TFTP request is initiated with the value taken from the parameter filename. This request is sent to the IP address set as serverip. In this case, the TFTP Server should be reachable to the device. ScanTool If you want to access the device with ScanTool, then the host running the ScanTool should also be in the same network as the device. The ScanTool broadcast requests are discarded by the routers if the device and the host running the ScanTool are in different network. This means that the ScanTool cannot discover the device.
: In bootloader mode, Scan Tool will support only IPv4. A device in Bootloader can be recognized by looking at the system description. If the system description does not contain any build number in braces, conclude that the device is in Bootloader mode. For example:
MP-8100-BSU-WD vX.Y.Z - Firmware Version SN-11Pl15010031 - Serial Number BL-v1.3.1 - Bootloader version
- Description of the device Figure G-1 Scan Tool View of a Device in Bootloader Mode (An Example) Tsunami 800 & 8000 Series - Software Management Guide 315 Bootloader CLI and ScanTool Reset/Reload Procedure Pre-requisites Download ScanTool v3.1.1 or above from http://my.proxim.com To view the Reload/Reset button on the ScanTool window, the operating system in the PC must be Windows 07/08. Ensure that the Windows Firewall is turned off before the ScanTool is launched. Ensure that the ScanTool is Run as Administrator. Device must be connected directly to the PC over Ethernet. User must be able to turn on & off the power supply, during the device reload/reset procedure. Step-by-Step instructions to perform Reload/Reset operation on a device using ScanTool application 1. Right click the ScanTool Application and then click Run as Administrator. 2. Choose a Network Adapter to which the device is connected and then click OK. 3. Click Reload/Reset button, at the bottom-left corner of the window. Tsunami 800 & 8000 Series - Software Management Guide 316 4. Click OK, on the dialog box. Bootloader CLI and ScanTool 5. Click the Reset/Reload button, as per the requirement. 6. Reload/Reset pattern is initialized.
: The message on the screenshots consists of either Reload or Reset as per the operation selected. 7. Perform the following steps:
a. Switch off the power supply to the device by unplugging the RJ45 cable from the PWR LAN-OUT port on the PoE Adapter. b. Click OK on the dialog box. Tsunami 800 & 8000 Series - Software Management Guide 317 c. Switch on the power supply to the device by re-plugging the RJ45 cable at the PWR LAN-OUT port on the PoE Adapter. Bootloader CLI and ScanTool
:
It can be noted that the steps a,b & c together constitute the Power recycle process. During Reload operation, ensure that the BOOTP and TFTP servers are properly configured and started. Unintentional press on the release-latch of the Ethernet cables during the Reload/Reset process unplugs the cable and results in failure of the Reload/Reset operation. 8. During the progress of the Reload/Reset-Request operation, various messages are displayed on the dialog box as given below:
Tsunami 800 & 8000 Series - Software Management Guide 318 9. Reload/Reset operation is started successfully. Bootloader CLI and ScanTool
: It is recommended to close the dialog box, as soon as the Reload/Reset operation is completed. The Reload/Reset operation has been triggered successfully. A new firmware is loaded on to the device with Reload operation, or else the device configuration is restored to the factory default settings with Reset operation. Troubleshooting the Reset/Reload Operation Failure 1.Reload/Reset operation fails a. If the LAN-IN cable gets unplugged during the power recycle process. b. If the LAN-IN cable is inserted in a NIC port, which is incompatible with the ScanTool application. Tsunami 800 & 8000 Series - Software Management Guide 319 Bootloader CLI and ScanTool c. If the dialog box appears as given below 1. Check the connectivity issues of the Ethernet cable from the LAN port to the PC. 2. Check the Firewall status. If the Windows Firewall is turned on, perform the following steps:
a. Under Windows Firewall, click Allow a program for Windows Firewall. b. Click Change Settings and then click Allow another program. c. View the Add a Program dialog box. d. Select the ScanTool program from the list and then click Add. e. Select the Home/Work (Private), Public checkboxes and then click OK. Tsunami 800 & 8000 Series - Software Management Guide 320 SNR Information Given below are the SNR values for the following devices:
H MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 MCS Index Modulation MCS0 BPSK 1/2 MCS1 QPSK 1/2 MCS2 QPSK 3/4 No of Streams Single Single Single MCS3 16 QAM 1/2 Single MCS4 16 QAM 3/4 Single MCS5 64 QAM 2/3 Single MCS6 64 QAM 3/4 Single MCS7 64 QAM 5/6 Single MCS8 BPSK 1/2 MCS9 QPSK 1/2 MCS10 QPSK 3/4 MCS11 16 QAM 1/2 MCS12 16 QAM 3/4 MCS13 64 QAM 2/3 MCS14 64 QAM 3/4 MCS15 64 QAM 5/6 Dual Dual Dual Dual Dual Dual Dual Dual MCS Index Modulation MCS0 BPSK 1/2 MCS1 QPSK 1/2 MCS2 QPSK 3/4 No of Streams Single Single Single MCS3 16 QAM 1/2 Single 2.4 GHz 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR 1.6 3.3 4.9 6.5 9.7 13 14.6 16.2 3.3 6.5 9.7 13 19.5 26 29.3 32.5 10 15 21 23 26 29 30 32 12 20 22 23 27 30 36 39 86 86 84 82 80 79 79 78 86 84 82 80 80 79 78 78 3.3 6.5 9.7 13 19.5 26 29.3 32.5 6.5 13 19.5 26 39 52 58.5 65 10 16 21 23 26 29 31 32 14 21 23 23 27 30 35 38 86 86 84 82 80 79 78 78 86 84 82 80 80 79 77 77 12 21 21 23 25 27 30 32 14 21 22 24 30 34 37 39 6.5 13 19.5 26 39 52 58.5 65 13 26 39 52 78 104 117 130 5 GHz 86 86 84 82 80 78 77 77 86 84 82 80 78 78 77 76 13.5 27 40.5 54 81 108 121.5 135 27 54 81 108 162 216 243 270 15 30 45 60 90 120 135 150 30 60 90 120 180 240 270 300 26 26 26 30 33 37 40 42 16 26 28 32 35 37 43 45 80 80 79 77 77 76 75 75 80 80 79 77 77 76 75 75 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR 1.6 3.3 4.9 6.5 6 8 10 14 86 86 84 82 3.3 6.5 9.7 13 7 8 13 16 86 86 84 82 6.5 13 19.5 26 6 9 11 14 86 86 84 82 13.5 27 40.5 54 15 30 45 60 9 11 15 16 80 80 79 77 321 Tsunami 800 & 8000 Series - Software Management Guide SNR Information 5 GHz MCS Index Modulation No of Streams 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR MCS4 16 QAM 3/4 Single MCS5 64 QAM 2/3 Single MCS6 64 QAM 3/4 Single MCS7 64 QAM 5/6 Single MCS8 BPSK 1/2 MCS9 QPSK 1/2 MCS10 QPSK 3/4 MCS11 16 QAM 1/2 MCS12 16 QAM 3/4 MCS13 64 QAM 2/3 MCS14 64 QAM 3/4 MCS15 64 QAM 5/6 Dual Dual Dual Dual Dual Dual Dual Dual 9.7 13 14.6 16.2 3.3 6.5 9.7 13 19.5 26 29.3 32.5 17 22 25 28 8 12 14 16 20 25 29 30 80 79 79 78 86 84 82 80 80 79 78 78 19.5 26 29.3 32.5 6.5 13 19.5 26 39 52 58.5 65 20 24 26 29 9 12 15 16 21 26 29 30 80 79 78 78 86 84 82 80 80 79 77 77 39 52 58.5 65 13 26 39 52 78 104 117 130 18 22 25 28 9 12 14 16 20 26 29 30 80 78 77 77 86 84 82 80 78 78 77 76 81 108 121.5 135 27 54 81 108 162 216 243 270 90 120 135 150 30 60 90 120 180 240 270 300 20 24 27 30 9 13 17 22 25 27 30 33 77 76 75 75 80 80 79 77 77 76 75 75 Given below are the SNR values for the following device(s) in legacy mode:
MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 Modulation 5 MHz 2.4 GHz 10 MHz 20 MHz 5 MHz 5 GHz 10 MHz 20 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Min SNR Max SNR Min SNR Max SNR Min SNR Max SNR BPSK 1/2 BPSK 3/4 QPSK 1/2 QPSK 3/4 16QAM 1/2 16QAM 3/4 64QAM 2/3 64QAM 3/4 1.5 2.25 3 4.5 6 9 12 13.5 10 10 12 14 17 20 27 29 84 84 84 84 82 82 81 80 3 4.5 6 9 12 18 24 27 10 11 11 13 17 23 29 30 84 84 84 84 80 78 76 74 6 9 12 18 24 36 48 54 13 13 15 15 22 25 28 29 84 84 84 84 80 73 73 72 8 9 10 12 16 18 24 27 84 84 82 82 82 82 80 80 8 9 10 11 16 18 24 27 84 84 82 82 82 80 80 80 7 8 9 12 15 18 24 27 81 81 81 81 80 80 78 76 Tsunami 800 & 8000 Series - Software Management Guide 322 Given below are the SNR values for the following devices:
SNR Information MP-8200-BSU-G MP-8250-BS9-G MP-8250-BS1-G MP-8200-BSU MP-8250-BS9 MP-8250-BS1 MP-8200-SUA MP-8250-SUR QB-8200-EPA-G/LNK-G QB-8250-EPR-G/LNK-G QB-8200-EPA/LNK QB-8250-EPR/LNK 4.900 - 5.925 GHz MCS Index Modulation MCS0 BPSK 1/2 MCS1 QPSK 1/2 MCS2 QPSK 3/4 No of Streams Single Single Single MCS3 16 QAM 1/2 Single MCS4 16 QAM 3/4 Single MCS5 64 QAM 2/3 Single MCS6 64 QAM 3/4 Single MCS7 64 QAM 5/6 Single MCS8 BPSK 1/2 MCS9 QPSK 1/2 MCS10 QPSK 3/4 MCS11 16 QAM 1/2 MCS12 16 QAM 3/4 MCS13 64 QAM 2/3 MCS14 64 QAM 3/4 MCS15 64 QAM 5/6 Dual Dual Dual Dual Dual Dual Dual Dual 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR 1.6 3.3 4.9 6.5 9.7 13 14.6 16.2 3.3 6.5 9.7 13 19.5 26 29.3 32.5 7 9 11 15 19 23 25 28 8 12 15 18 20 25 29 30 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 3.3 6.5 9.7 13 19.5 26 29.3 32.5 6.5 13 19.5 26 39 52 58.5 65 7 10 13 16 20 24 26 29 9 12 15 18 21 26 29 30 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 6.5 13 19.5 26 39 52 58.5 65 13 26 39 52 78 104 117 130 7 11 13 16 20 24 26 29 9 12 15 18 21 26 29 30 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 13.5 27 40.5 54 81 108 121.5 135 27 54 81 108 162 216 243 270 15 30 45 60 90 120 135 150 30 60 90 120 180 240 270 300 9 10 14 16 20 24 27 29 10 13 16 20 24 27 30 33 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 Tsunami 800 & 8000 Series - Software Management Guide 323 Given below are the SNR values for the following device(s) in legacy mode:
SNR Information MP-8200-BSU-G MP-8250-BS9-G MP-8250-BS1-G MP-8200-BSU MP-8250-BS9 MP-8250-BS1 MP-8200-SUA MP-8250-SUR QB-8200-EPA-G/LNK-G QB-8250-EPR-G/LNK-G QB-8200-EPA/LNK QB-8250-EPR/LNK 4.900 - 5.925 GHz Modulation 5 MHz 10 MHz 20 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR BPSK 1/2 BPSK 3/4 QPSK 1/2 QPSK 3/4 16QAM 1/2 16QAM 3/4 64QAM 2/3 1.5 2.25 3 4.5 6 9 12 7 8 10 12 16 20 25 64QAM 3/4 13.5 27 80 80 79 78 77 76 74 73 3 4.5 6 9 12 18 24 27 7 9 10 12 16 20 24 27 80 79 77 76 74 72 70 68 6 9 12 18 24 36 48 54 8 9 10 12 16 21 25 79 77 76 74 73 72 69 27 68 Given below are the SNR values for the following devices:
MP-820-SUA-50+
MP-820-SUA-100 MP-822-SUA-100 MP-825-SUR-50+
MP-825-SUR-100 MP-825-CPE-50 MP-825-CPE-100 MP-835-CPE-10 MP-835-CPE-25 MP-835-CPE-50 MP-835-CPE-100 MP-820-BSU-100 MP-822-BSU-100 Tsunami 800 & 8000 Series - Software Management Guide 324 SNR Information MP-825-BS3-50+
QB-825-EPR/LNK-50+
QB-825-EPR/LNK-100 QB-835-EPR/LNK-25 QB-835-EPR/LNK-50 MCS Index Modulation MCS0 BPSK 1/2 MCS1 QPSK 1/2 MCS2 QPSK 3/4 No of Streams Single Single Single MCS3 16 QAM 1/2 Single MCS4 16 QAM 3/4 Single MCS5 64 QAM 2/3 Single MCS6 64 QAM 3/4 Single MCS7 64 QAM 5/6 Single MCS8 BPSK 1/2 MCS9 QPSK 1/2 MCS10 QPSK 3/4 MCS11 16 QAM 1/2 MCS12 16 QAM 3/4 MCS13 64 QAM 2/3 MCS14 64 QAM 3/4 MCS15 64 QAM 5/6 Dual Dual Dual Dual Dual Dual Dual Dual 5 GHz 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR 1.6 3.3 4.9 6.5 9.7 13.0 14.6 16.2 3.3 6.5 9.7 13.0 19.5 26.0 29.3 32.5 9 10 13 17 20 24 26 30 10 13 15 18 23 27 29 31 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 3.3 6.5 9.7 13 19.5 26 29.3 32.5 6.5 13 19.5 26 39 52 58.5 65 9 10 13 17 21 25 27 29 10 12 16 19 23 26 29 30 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 6.5 13 19.5 26 39 52 58.5 65 13 26 39 52 78 104 117 130 9 12 13 16 22 25 27 30 10 12 15 17 23 27 30 31 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 13.5 27 40.5 54 81 108 121.5 135 27 54 81 108 162 216 243 270 9 11 15 16 24 28 29 30 10 13 17 22 25 27 30 33 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50
: Short GI - 400 nSec is not valid for the 82x devices. Tsunami 800 & 8000 Series - Software Management Guide 325 Given below are the SNR values for the following device in legacy mode:
SNR Information MP-820-SUA-50+
MP-820-SUA-100 MP-822-SUA-100 MP-825-SUR-50+
MP-825-SUR-100 MP-825-CPE-50 MP-835-CPE-10 MP-835-CPE-25 MP-835-CPE-50 MP-835-CPE-100 MP-825-CPE-100 QB-825-EPR/LNK-50+
QB-825-EPR/LNK-100 QB-835-EPR/LNK-25 QB-835-EPR/LNK-50 MP-820-BSU-100 MP-822-BSU-100 MP-825-BS3-50+
5 GHz Modulation 10 MHz 20 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR BPSK 1/2 BPSK 3/4 QPSK 1/2 QPSK 3/4 16QAM 1/2 16QAM 3/4 64QAM 2/3 64QAM 3/4 3 4.5 6 9 12 18 24 27 8 9 11 12 16 21 24 28 50 50 50 50 50 50 50 50 6 9 12 18 24 36 48 54 8 9 12 13 16 21 25 28 50 50 50 50 50 50 50 50 Tsunami 800 & 8000 Series - Software Management Guide 326 Configuration File Cross-loading across the Products I Proxim portfolio comprises different product lines and SKUs which differ in features and capabilities depending on the hardware platform and the country setting or licensing used in them. This document describes the process to successfully apply the configuration file on a device(s) and about the software checks run while applying the configuration file on a device(s). The user can apply a configuration file retrieved from a (Source) device to another compatible (Target) device. In order to successfully apply the configuration file, the following criteria should be met. 1. The Hardware Inventory Component ID should be same for both the source device and the target device. Hardware Inventory Component ID Products 2000 2001 2003 2005 2006 AP-800; AP-8000 MP-8100-BSU; MP-8100-SUA; MP-8150-SUR MP-8150-SUR-100 MP-8160-BSU; MP-8160-SUA; MP-8160-BS9 MP-8200-BSU; MP-8200-SUA; MP-8250-BS9/SUR MP-8200-BSU-G; MP-8250-BS9/BS1-G MP-8200-BSU; MP-8250-BS9/BS1 MP-820-BSU-100; MP-822-BSU-100;
MP-825-BS3-100 QB-8200-EPA-G; QB-8250-EPR-G QB-8200-EPA; QB-8250-EPR QB-825-EPR/LNK-50+
QB-825-EPR/LNK-100 QB-835-EPR/LNK-25 QB-835-EPR/LNK-50 QB-8xxx-EPA; QB-8xxx-EPR MP-8150-CPE Tsunami 82x Series AP-8100 NOTE:The configuration file can be applied only to the devices of the same family. The configuration file retrieved from an 8xx series device cannot be applied to a device from 81xx series. The configuration file of a MP-8160-BSU/MP-8160-SUA device cannot be applied to an 8100/8200 series device and vice versa even though they share the same component ID. The configuration file of a MP-8150-CPE device cannot be applied to a MP-8160-CPE device and vice versa even though they share the same component ID. The configuration file of a MP-82xx-BSx can be applied on a MP-82xx-BSx-G device where as the configuration file of MP-82xx-BSx-G cannot be applied on MP-82xx-BSx. 2. The Regulatory Domain should be same in both the source device and the target device.The available Regulatory Domains are listed below:
WD Tsunami 800 & 8000 Series - Software Management Guide 327 Configuration File Cross-loading across the Products US JP EU*
NOTE: WD SKU is compatible only with the EU SKU. For example, if the configuration file retrieved from a WD SKU device is loaded on a US or JP SKU target device then the upgrade fails. If the above criteria are met, the configuration file can be successfully applied on the target device else an error message is thrown. Once the configuration file is loaded and the device is rebooted, the software tries to apply the new configuration file during the system boot-up process. Sometimes, a device from a particular product series may have a different license information compared to other devices of the same series. Therefore, the start-up process validates the configuration file against the license file of the device before applying the configuration file. The configuration file is valid, if the following conditions are met:
1. The input bandwidth limit in the configuration file should be less than or equal to the input bandwidth limit in the license file. 2. The output bandwidth limit in the configuration file should be less than or equal to the output bandwidth limit in the license file. 3. The sum of the input and output bandwidth limit in the configuration file should be less than or equal to the cumulative bandwidth limit in the license file. 4. The frequency band (2.4, 4.9, and 5 G Hz) in the configuration file should match with any one of the supported frequency bands in the license file. 5. The radio operation mode (BSU/SU/AP) in the configuration file should match with any one of supported radio operating modes in the license file. 6. The number of satellites in the configuration file should be less than or equal to the number of satellites in the license file. 7. The product family (TMP/TQB/AP) value in the configuration file should match the product family value in the license file. 8. Tx/Rx antenna chain mask in the configuration file should match the Tx/Rx antenna chain mask in the license file. NOTE: If any one of the above conditions is not met, the configuration file will be removed by the flash control module during initialization and the device will boot-up with the last known good configuration. Before deleting the configuration file, an eventlog is generated about the violation of the license parameters. In some cases, if the last known good configuration does not exist internally, the device can reset the configuration to factory defaults and boot up. Tsunami 800 & 8000 Series - Software Management Guide 328 Abbreviations J ACL ACS AES ALG ARP ATPC A Access Control List Automatic Channel Selection Advanced Encryption Standard Application Level Gateway Address Resolution Protocol Adaptive Transmit Power Control B BSU Base Station Unit CCP CHAP CLI CIR CPE CRC DDRS DES DFS DHCP DNS DSL EIRP EOL ETSI FCC C Compression Control Protocol Challenge Handshake Authentication Protocol Command Line Interface Committed Information Rate Customer Premises Equipment Cyclic Redundancy Check D Dynamic Data Rate Selection Data Encryption Standard Dynamic Frequency Selection Dynamic Host Configuration Protocol Domain Name System Digital Subscriber Line E Equivalent Isotropically Radiated Power End of Life European Telecommunications Standards Institute Federal Communications Commission F Tsunami 800 & 8000 Series - Software Management Guide 329 FCS Frame Check Sequence Abbreviations Gbps GPL GRE HTTP HTTPS IANA IC ICMP IGMP ISP ITS LACP LAN LCP LED LGPL MAN Mbps MD5 MIB MIMO MIR MP MPPE Gigabit Per Second General Public License Generic Routing Encapsulation G H HyperText Transfer Protocol HyperText Transfer Protocol Secure I Internet Assigned Numbers Authority (IANA) Industry Canada Internet Control Message Protocol Internet Group Management Protocol Internet Service Provider Intelligent Transportation System L Link Aggregation Control Protocol Local Area Network Link Configuration Protocol Light Emitting Diode Lesser General Public License M Metropolitan Area Networks Megabits Per Second Message-Digest algorithm Management Information Base Multiple-input and multiple-output Maximum Information Rate Multipoint Microsoft Point-to-Point Encryption MSCHAP v2 Microsoft Challenge-Handshake Authentication Protocol MTU Maximum Transmission Unit Tsunami 800 & 8000 Series - Software Management Guide 330 Abbreviations NAPT NAT NCP NBD NMS NOP PAP PC PoE PPPoE PTMP PTP PVES QB QoS N Network Address Port Translation Network Address Translation Network Control Protocol Next Business Day Network Management System Non Occupancy Period P Password Authentication Protocol Personal Computer Power Over Ethernet Point-to-point Protocol over Ethernet Point-to-multipoint Point-to-point ProximVision ES QuickBridge Quality of Service Q R RADIUS Remote Authentication Dial In User Service RAS RF RIP RMA RLT RSSI SHA SKU SNMP SNR SNTP SSH Remote Access Services Radio Frequency Routing Information Protocol Return Material Authorization Radio Link Test Received Signal Strength Indicator S Secure Hash Algorithm Stock Keeping Unit Simple Network Management Protocol Signal-to-noise Ratio Simple Network Time Protocol Secure Shell Tsunami 800 & 8000 Series - Software Management Guide 331 Abbreviations Secure Socket Layer Spanning Tree Protocol Subscriber Unit T Text Based Configuration Transmission Control Protocol Trivial File Transfer Protocol Temporal Key Integrity Protocol Transmit Power Control Tag Protocol Identifier Time to Live SSL STP SU TBC TCP TFTP TKIP TPC TPID TTL UDP UTP User Datagram Protocol Unshielded Twisted Pair VLAN Virtual Local Area Network U V W WEP WORP Wired Equivalent Privacy Wireless Outdoor Router Protocol Tsunami 800 & 8000 Series - Software Management Guide 332 Lightning Protection K Lightning protection is used to maximize the reliability of the communications equipment by safely re-directing current from a lightning strike or a power surge traveling along the Cat 5/Cat5e/Cat 6 Ethernet cabling to the ground using the shortest path possible. Designing a proper grounding system prior to installing any communications equipment is critical to minimize the possibility of equipment damage, void warranties, and cause serious injury. The surge arrestor (sometimes referred to as a lightning protector) can protect your sensitive electronic equipment from high-voltage surges caused by discharges and transients at the PoE. Proxim Wireless offers superior lightning and surge protection for Tsunami series products. Contact your reseller or distributor for more information. Tsunami 800 & 8000 Series - Software Management Guide 333 Warranty and Technical Support For Warranty and Technical Support Policy, please visit http://proxim.com/support. L Obtaining Technical Service and Support If you are having trouble using the Proxim product, please read this guide and the additional documentation provided with your product. If you require additional support to resolve your issue, please be ready to provide the following information before you contact Proxims Technical Services team:
Product information Part number and serial number of the suspected faulty device Trouble/error information Trouble/symptom being experienced Activities completed to confirm fault Network information (What kind of network are you using?) Circumstances that preceded or led up to the error Message or alarms viewed Steps taken to reproduce the problem ServPak information (if a Servpak customer):
ServPak account number Registration information If the product is not registered, date and location where you purchased the product
: Technical Support is free for the warranty period from the date of purchase. Support Options Proxim eService Web Site Support The Proxim eService Web site is available 7x24x365 at http://my.proxim.com. On the Proxim eService Web Site, you can access the following services:
Product Download Page: Provides quick links to product firmware, software, and documentation downloads. Proxim TV Links: A link to helpful video tutorials. Knowledgebase: A solution database of all the resolved problems. You can search by product, category, keywords, or phrases. Live Chat: Chat with a support technician on-line or request to call back at a later time. Create a Support Request: Create a support request with our technical support staff who will reply to you by email. Case Management: Login to check the status of your support cases, update your personal profile, or access restricted information and features. Provide Feedback: Submit a suggestion, complaint, or other feedback about the support site and our products. Tsunami 800 and 8000 Series - Software Management Guide 334 Warranty and Technical Support Telephone Support Contact technical support via telephone as follows:
USA and Canada Customers Phone: +1-408-383-7700; +1-866-674-6626 Business Hours: 24x7 live response. Tier 3 support: 8 a.m. to 5 p.m. M-F PDT (UTC/GMT -7 hrs) International Customers Phone: +1-408-383-7700; 0800-916475 (France); 8-800-100-9485 (Russia) Business Hours: 24x7 live response. Tier 3 support: 8 a.m. to 5 p.m. M-F PDT (UTC/GMT -7 hrs) ServPak Support To provide even greater investment protection, Proxim Wireless offers a cost-effective support program called ServPak. ServPak is a program of enhanced service support options that can be purchased as a bundle or individually, tailored to meet your specific needs. Whether your requirement is round the clock technical support or advance replacement service, we are confident that the level of support provided in every service in our portfolio will exceed your expectations. All ServPak service bundles are sold as service contracts that provide coverage for specific products from 1 to 3 years. Servpak bundles are considered an upgrade to the standard product warranty and not an extension. 24x7 Basic Technical Basic Advanced Replacement Support
(Two business days/
International economy shipment service) 8x7 Advanced Technical Support Software Maintenance Access to Knowledge Base Priority Advanced Replacement
(Next business day/
International priority shipment service) 24x7 Advanced Technical Support Proxim Vision Support Additional Information on ServPak Options Advanced Replacement of Hardware In the event of a hardware failure, our guaranteed turnaround time for return to factory repair is 30 days or less. Customers who purchase this service are guaranteed replacement of refurbished or new hardware to be shipped out within one or two business days, as applicable. Options are available for shipment services depending on the customers support needs. Hardware is shipped on business days, Monday Friday excluding Holidays, 8:00 AM 3:30 PM Eastern Time. Tsunami 800 and 8000 Series - Software Management Guide 335 Warranty and Technical Support 7x24x365 Availability Unlimited, direct access to technical support engineers 24 hours a day, 7 days a week, 365 days a year including Holidays. 8x5 Availability Unlimited, direct access to world-class technical support engineers 8 hours a day, 5 days a week, Monday through Friday from 8:00AM - 5:00PM Pacific Standard Time. Basic Technical Support Customers who purchase this service can be rest assured that their call will be answered by Proxims Tier 1 technical support and a case opened immediately to document the problem and provide initial troubleshooting to identify the solution and resolve the incident in a timely manner. Advanced Technical Support In addition to Proxims world-class Tier 1 technical support, customers will be able to have their more complex issues escalated to our world-class Tier 3 technical support engineers. Our Tier 3 engineers will review specific configurations to troubleshoot intricate issues and will also provide helpful insights regarding Proxims products and various tips from decades of collective experience in the wireless industry. Software Maintenance It's important to maintain and enhance security and performance of wireless equipment and Proxim makes this easy by providing a Software Maintenance program that enables customers to access new feature and functionality rich software upgrades and updates. Customers will also have full access to Proxim's vast Knowledgebase of technical bulletins, white papers and troubleshooting documents. To purchase ServPak support services, please contact your authorized Proxim distributor. To receive more information or for questions at http://www.proxim.com/support/servpak, call Proxim Support (For telephone numbers, see Telephone Support) or send an email to servpak@proxim.com. our website available options, ServPak support please visit any the on of Tsunami 800 and 8000 Series - Software Management Guide 336
1 2 3 4 5 6 7 | software guide2 | Users Manual | 2.66 MiB | / August 10 2014 |
Advanced Configuration Given below is the table which explains Protocol Filter parameters and the method to configure the configurable parameter(s):
Parameter Filtering Control This parameter is used to apply filters on the devices interface. The filtering can be applied on any of the following interfaces:
Description Filtering Type enabled to apply filters. Ethernet: Packets are examined at the Ethernet interface.
: In addition to enabling Filtering Control, the Global Filter Flag should also be By default, the Filtering Control is set to Disable, meaning which Protocol Filters are disabled on all the interfaces. This parameter specifies the action to be performed on the data packets whose protocol type is not defined in the protocol filter table (this table contains a list of default protocols supported by the device and the protocols defined by the user), or whose Entry Status is in Disable state. The available filtering types are:
Wireless: Packets are examined at the Wireless interface. All Interfaces: Packets are examined at both Ethernet and Wireless interface. Passthru: The protocols with entry status Disable or the protocols which do not exist in the protocol filtering table are allowed through the configured interface. Block: The protocols with entry status Disable or the protocols which do not exist in the protocol filtering table are blocked. After configuring the required parameters, click OK and then COMMIT. 5.10.1.1 Protocol Filter Table The Protocol Filter table displays a list of default protocols supported by the device and the protocols created by the user. By default, the system generates 19 protocols entries. Each of the Protocol contains the following information:
Parameter Protocol Name Protocol Number Description Represents the Protocol name. The system throws an error when you try to edit the name of a default protocol. Represents the Protocol number. The value is of 4 digit hexadecimal format. The system throws an error when you try to edit the Protocol number of a default protocol. Filter Status The supported filter status are, Passthru: When the filter status is set to Passthru and entry status is Enable, all packets whose protocol matches with the given protocol number are forwarded on the configured interface. Block: When the filter status is set to Block and entry status is Enable, all packets whose protocol matches with the given protocol number are dropped on the configured interface. By default, the status is set to Block. Tsunami 800 & 8000 Series - Software Management Guide 171 Entry Status Set the entry status as either Enable, Disable or Delete. Advanced Configuration
: System-defined default protocols cannot be deleted. Enable: Enables filter status on a protocol. Disable: Disables filter status on a protocol. Delete: Deletes a protocol entry from the Protocol Filter Table. 5.10.1.2 Add User-defined Protocols to the Filter Table To add user-defined protocols to the Protocol Filter Table, click Add in the Protocol Filter screen. The Protocol Filter Add Row screen appears. Enter details for all the required parameters and click Add. Figure 5-95 Add User-defined Protocols
: The maximum number of Protocol Filters that can be added to the table are 64, out of which 19 are default entries. 5.10.2 Static MAC Address Filter The Static MAC Address filter optimizes the performance of a wireless (and wired) network. With this feature configured, the device can block traffic between wired devices and wireless devices based on the MAC address. Each MAC Address or Mask is comprised of 12 hexadecimal digits (0-9, A-F) that correspond to a 48-bit identifier. (Each hexadecimal digit represents 4 bits (0 or 1)). Taken together, a MAC Address/Mask pair specifies an address or a range of MAC addresses that the device will look for when examining packets. The device uses Boolean logic to perform an AND operation between the MAC Address and the Mask at the bit level. A Mask of 00:00:00:00:00:00 corresponds to all MAC addresses, and a Mask of FF:FF:FF:FF:FF:FF applies only to the specified MAC Address. For example, if the MAC Address is 00:20:A6:12:54:C3 and the Mask is FF:FF:FF:00:00:00, the device will examine the source and destination addresses of each packet looking for any MAC address starting with 00:20:A6. If the Mask is FF:FF:FF:FF:FF:FF, the device will only look for the specific MAC address (in this case, 00:20:A6:12:54:C3). You can configure the Static MAC Address Filter parameters depending on the following scenarios:
To prevent all traffic from a specific wired MAC address from being forwarded to the wireless network, configure only the Wired MAC Address and Wired Mask (leave the Wireless MAC Address and Wireless Mask set to all zeros). Tsunami 800 & 8000 Series - Software Management Guide 172 Advanced Configuration To prevent all traffic from a specific wireless MAC address from being forwarded to the wired network, configure only the Wireless MAC address and Wireless Mask (leave the Wired MAC Address and Wired Mask set to all zeros). To prevent traffic between a specific wired MAC address and a specific wireless MAC address, configure all four parameters. Configure the wired and wireless MAC address and set the wired and wireless mask to all Fs. To prevent all traffic from a specific wired Group MAC address from being forwarded to the wireless network, configure only the Wired MAC Address and Wired Mask (leave the Wireless MAC Address and Wireless Mask set to all zeros). To prevent all traffic from a specific wireless Group MAC address from being forwarded to the wired network, configure only the Wireless MAC address and Wireless Mask (leave the Wired MAC Address and Wired Mask set to all zeros). To prevent traffic between a specific wired Group MAC address and a specific wireless Group MAC address, configure all four parameters. Configure the wired and wireless MAC address and set the wired and wireless mask to all Fs. Static MAC Filter Examples Consider a network that contains a wired PC and three wireless PCs. The MAC addresses for each PCs are as follows:
MAC Address of the wired PC: 00:40:F4:1C:DB:6A MAC Address of the wireless PC1: 00:02:2D:51:94:E4 MAC Address of the wireless PC2: 00:02:2D:51:32:12 MAC Address of the wireless PC3: 00:20:A6:12:4E:38 Wired MAC Address: 00:40:F4:1C:DB:6A Wired Mask: FF:FF:FF:FF:FF:FF Wireless MAC Address: 00:02:2D:51:94:E4 Wireless Mask: FF:FF:FF:FF:FF:FF Wired MAC Address: 00:40:F4:1C:DB:6A Wired Mask: FF:FF:FF:FF:FF:FF Wireless MAC Address: 00:02:2D:51:94:E4 Wireless Mask: FF:FF:FF:00:00:00 Wired MAC Address: 00:40:F4:1C:DB:6A Wired Mask: FF:FF:FF:FF:FF:FF Wireless MAC Address: 00:00:00:00:00:00 Wireless Mask: 00:00:00:00:00:00 5.10.2.0.1 Prevent two specific PCs from communicating Configure the following settings to prevent the wired PC and wireless PC1 from communicating:
Result: Traffic between the wired PC and wireless PC1 is blocked. wireless PC2 and PC3 can still communicate with the wired PC. 5.10.2.0.2 Prevent multiple Wireless PCs from communicating with a single wired PC Configure the following settings to prevent wireless PC1 and PC2 from communicating with the wired PC:
Result: When a logical AND is performed on the Wireless MAC Address and Wireless Mask, the result corresponds to any MAC address beginning with the 00:20:2D prefix. Since wireless PC1 and wireless PC2 share the same prefix (00:02:2D), traffic between the wired Server and wireless PC1 and PC2 is blocked. Wireless PC3 can still communicate with the wired PC since it has a different prefix (00:20:A6). 5.10.2.0.3 Prevent all wireless PCs from communicating with a single wired PC Configure the following settings to prevent wired PC from communicating with all three wireless PCs:
Tsunami 800 & 8000 Series - Software Management Guide 173 Result: The device blocks all traffic between the wired PC and all wireless PCs. 5.10.2.0.4 Prevent a wireless PC from communicating with the wired network Configure the following settings to prevent wireless PC3 from communicating with any device on the Ethernet:
Advanced Configuration Result: The device blocks all traffic between wireless PC3 and the Ethernet network. Wired MAC Address: 00:00:00:00:00:00 Wired Mask: 00:00:00:00:00:00 Wireless MAC Address: 00:20:A6:12:4E:38 Wireless Mask: FF:FF:FF:FF:FF:FF 5.10.2.1 Static MAC Address Filter Configuration To configure Static MAC Filter parameters, navigate to ADVANCED CONFIGURATION > Filtering > Static MAC Address Filter. The Static MAC Address Filter screen appears:
Click Add in the Static MAC Address Filter screen. The Static MAC Address Filter Add Row screen appears. Figure 5-96 Static MAC Address Filter Figure 5-97 Static MAC Address Filter Add Entry Tsunami 800 & 8000 Series - Software Management Guide 174 Given below is the table which explains Static MAC Address Filter parameters and the method to configure the configurable parameter(s):
Advanced Configuration Parameter Wired MAC Address Specifies the MAC address of the device on the wired network that is restricted from communicating with a device on the wireless network. Description Wired MAC Mask Specifies the range of MAC address to which this filter is to be applied. Wireless MAC address Specifies the MAC address of the device on the wireless network that is restricted from communicating with a device on the wired network. Wireless MAC Mask Specifies the range of MAC address to which this filter is to be applied. Comment Status Specifies the comment associated with Static MAC Filter table entry. Specifies the status of the newly created filter. Click Add and then COMMIT.
You can configure a maximum of 200 MAC address filters. The Wired MAC address and the Wireless MAC address should be a unicast MAC address. The MAC Address or Mask includes 12 hexadecimal digits (each hexadecimal equals to 4 bits containing 0 or 1) which is equivalent to 48 bit identifier. 5.10.3 Advanced Filtering With Advanced Filtering, you can filter pre-defined IP Protocol traffic on the network. By default, 5 IP protocols are pre-defined and based on the configuration they can be blocked or allowed to enter the network. To apply filters on the IP protocols, navigate to ADVANCED CONFIGURATION > Filtering > Advanced Filtering. The Advanced Filtering screen appears:
Figure 5-98 Advanced Filtering Tsunami 800 & 8000 Series - Software Management Guide 175 Advanced Configuration The Advanced Filtering table contains a list of 5 pre-defined protocols on which Advanced Filtering is applied. The following table explains the Filtering table parameters:
Parameter Protocol Name Represents the protocol name. By default, Advanced Filtering is supported on the following 5 default protocols:
Description Deny IPX RIP Deny IPX LSP Deny IPX SAP Deny IP Multicasts Deny IP Broadcasts Ethernet to wireless Wireless to ethernet Both Represents the direction of an IP Protocol traffic that needs to be filtered. The directions that can be filtered are, The filters are applied on the IP protocol only when Entry Status is enabled. Direction Entry Status
5.10.3.1 Edit Advanced Filtering Table Entries The Advanced Filtering table contains a maximum of 5 pre-defined IP protocols. User-defined IP protocols cannot be added to the Advanced Filtering table. To edit Advanced Filtering table protocols, click Edit in the Advanced Filtering screen. The Advanced Filtering - Edit Entries screen appears. Tsunami 800 & 8000 Series - Software Management Guide 176 Advanced Configuration Modify the IP protocol traffic direction that needs to be filtered, and the filtering status for the desired IP Protocol. Figure 5-99 Advance Filtering- Edit Entries Next click OK and then COMMIT. 5.10.4 TCP/UDP Port Filter TCP/UDP Port Filtering allows you to enable or disable Transmission Control Protocol (TCP) ports and User Datagram Port
(UDP) ports on network devices. A user specifies a Protocol Name, Port Number, Port Type (TCP, UDP, or TCP/UDP), and filtering interfaces (Only Wireless, Only Ethernet or Both) in order to block access to services such as Telnet and FTP, and traffic such as NETBIOS and HTTP. To apply filters on TCP/UDP Port, navigate to ADVANCED CONFIGURATION > Filtering > TCP/UDP Port Filter. The TCP/UDP Port Filter screen appears. Tsunami 800 & 8000 Series - Software Management Guide 177 Advanced Configuration The Filter Control parameters determines if filter has to be applied or not on a TCP/UDP Port. By default, it is disabled. To apply filters, select Enable and click OK. Figure 5-100 TCP/UDP Port Filter 5.10.4.1 TCP/UDP Port Filter Table The TCP/UDP Port Filter table displays a list of default TCP/UDP ports and user-defined ports which can be enabled or disabled as desired. By default, the device support 7 default TCP/UDP port filter entries. Parameter Protocol Name Port Number Description Represents the name of the service/protocol. Please note that the system throws an error when an attempt is made to edit the default service/protocol name. Represents the destination port number. Please note that the system throws an error when an attempt is made to edit the port number. Port Type Represents the port type (TCP, UDP, Both). Filter Interface Represents the interface on which the filter is applied. The supported interfaces are, All Interfaces Only Ethernet Only Wireless Tsunami 800 & 8000 Series - Software Management Guide 178 Parameter Description Entry Status Set the entry status as either Enable, Disable or Delete. Advanced Configuration attempt to delete default entries, the device throws an error. Enable: Filter is applied and filters the packet based on the Port number and port type. Disable: No filter is applied. Delete: Allows to delete only user-defined TCP/UDP port filter entry. When you Entry Status (Enable/Disable) Port Number Port Type Filter Interface Ethernet Enable UDP If you have configured any user-defined protocols then click OK and then COMMIT. For example, a device with the following configuration would discard frames received on its Ethernet interface with a UDP destination port number of 137, effectively blocking NETBIOS Name Service packets. Please note that even the Filtering Control should be enabled to apply the filter. Protocol Name NETBIOS Name Service 137 5.10.4.2 Adding User-defined TCP/UDP Port Filter Entries To add user-defined TCP/UDP port filter entries to the table, click Add in the TCP / UDP Port Filter screen. The TCP/UDP Port Filter Add Row screen appears:
Figure 5-101 Add User-defined TCP/UDP Protocols Provide details for all the parameters and click Add. To apply the configured parameters, click COMMIT.
5.10.5 Storm Threshold Filter The TCP/UDP filtering operation is allowed only when the Global Flag and Filter Control options are enabled. You can add a maximum of 64 TCP/UDP Port Filter entries to the table, out of which 7 are default entries. The Storm Threshold Filter restricts the excessive inbound multicast or broadcast traffic on layer two interfaces. This protects against broadcast storms resulting from spanning tree misconfiguration. A broadcast or multicast filtering mechanism needs to be enabled so that a large percentage of the wireless link remains available to the connected mobile terminals. Tsunami 800 & 8000 Series - Software Management Guide 179 To configure Storm Threshold Filter, navigate to ADVANCED CONFIGURATION > Filtering > Storm Threshold Filter. The Storm Threshold Filter screen appears. This screen contains information about the threshold values per second of the multicast and broadcast packets that can be processed for the interface(s) present in the device. Advanced Configuration Given below is the table which explains Storm Threshold Filter parameters and the method to configure the configurable parameter(s):
Figure 5-102 Storm Threshold Filter Parameter Interface Multicast Threshold Broadcast Threshold Description Allows to configure the type of interface on which filtering has to be applied. The Storm Threshold filter can be used to filter the traffic on two types of interfaces: Ethernet or Wireless. By default, Storm Threshold filtering is disabled on both Ethernet and Wireless interfaces. Allows to configure the threshold value of the multicast packets to be processed for the Ethernet or Wireless interface. Packets more than threshold value are dropped. If threshold value for multicast packets is set to '0', filtering is disabled. The default Multicast Threshold value is 0 per second. Allows to configure the threshold value of the broadcast packets to be processed for the Ethernet or Wireless interface. Packets more than threshold value are dropped. If threshold value for broadcast packets is set to '0', filtering is disabled. The default Broadcast Threshold value is 0 per second. After configuring the required parameters, click OK and then COMMIT. 5.10.6 WORP Intra Cell Blocking
: Intra Cell Blocking is applicable only to a BSU in Bridge Mode only. The WORP Intra Cell Blocking feature restricts traffic between SUs which are registered to the same BSU. The two potential reasons to isolate traffic among the SUs are:
To provide better security by isolating the traffic from one SU to another in a public space. To block unwanted traffic between SUs to prevent this traffic from using bandwidth. Tsunami 800 & 8000 Series - Software Management Guide 180 Advanced Configuration The user can form groups of SUs at the BSU which define the filtering criteria. All data to/from SUs belonging to the same group are bridged. If an SU does not belong to any group, the BSU discards the data. The user can also configure a Security Gateway to block traffic between SUs connected to different BSUs. All packets destined for SUs not connected to the same BSU are forwarded to the Security Gateway MAC address (configured under Security Gateway). The following rules apply to Intra Cell Blocking Groups:
an SU can be assigned to more than one group. an SU that has not been assigned to any group cannot communicate to any other SU connected to the same or different BSU. 5.10.6.0.1 Example of Intra-Cell Blocking Groups Assume that four Intra Cell Blocking Groups have been configured on a BSU. SUs 1 through 10 are registered to the BSU. Group1 Group2 Group3 Group4 SU1 SU4 SU5 SU2 SU3 SU8 SU6 SU1 SU7 SU8 SU9 SU10 In this example, SU1 belongs to two groups, Group 1 and Group 3. Therefore, packets from SU1 destined to SU4, SU5, SU6 and SU7 are not blocked. However, SU9 belongs to group 4 only and packets from SU9 are blocked unless sent to SU8 or SU 10. To configuring Intra-Cell Blocking parameters, navigate to ADVANCED CONFIGURATION > Filtering> WORP Intra Cell Blocking. The following screen appears:
Figure 5-103 Intra Cell Blocking Tsunami 800 & 8000 Series - Software Management Guide 181 This screen is classified into two categories: Intra Cell Blocking and Security Gateway. Given below are the configuration details. Advanced Configuration Parameter Description Intra Cell Blocking Status By default, Intra Cell Blocking is disabled on a BSU. Select Enable to enable the feature and then Click OK and then COMMIT. Security Gateway Status By default, Security Gateway is disabled on a BSU. Select Enable to enable the feature. MAC Address Represents the MAC address of the security gateway. This gateway routes the packets transmitted by the SU to the different BSUs to which it belongs. After configuring the required parameters, click OK and then COMMIT.
: Intra Cell Blocking is configurable only in Bridge mode. When you change the device from Bridge to Routing mode or vice-versa, Intra-Cell Blocking stops or starts working only after device reboot. 5.10.6.1 WORP Intra Cell Blocking Group Table The user can form groups of SUs at the BSU which define the filtering criteria. All data to/from SUs belonging to the same group are bridged. If an SU does not belong to any group, the BSU discards the data. By default, a BSU supports 16 groups and each group can contain a maximum of 240 SUs. Please note that a single SU can be a member of all the existing groups. To view and configure the Intra Cell Blocking Group table, navigate to ADVANCED CONFIGURATION > Filtering> WORP Intra Cell Blocking > Group Table. The WORP Intra Cell Blocking Group Table screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 182 Advanced Configuration Figure 5-104 WORP Intra Cell Blocking Group Table This table displays the list of groups. If the Entry Status for a group is set to Enable then BSU discards all the packets coming from SUs which are not members of that group. If set to Disable, then allows all the packets coming from SUs which are not the members of that group. If you have changed the Entry Status of a group, then click OK and then COMMIT. 5.10.6.2 WORP Intra Cell Blocking MAC Table The WORP Intra Cell Blocking MAC table allows to add SUs MAC address and assign them to the groups. You can add a maximum of 250 SUs to the table. To add SU to the table, navigate to ADVANCED CONFIGURATION > Filtering > WORP Intra Cell Blocking > MAC Table. The WORP Intra Cell Blocking MAC Table screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 183 Advanced Configuration 5.10.6.2.1 To add MAC addresses, click Add. The following screen appears. Figure 5-105 WORP Intra Cell Blocking MAC Table Figure 5-106 WORP Intra Cell Blocking MAC Table Add Entry Given below is the table which explains the WORP Intra Cell Blocking MAC Table entries and the method to configure the configurable parameter(s):
Parameter Description MAC Address Represents the MAC address of the SU. Group IDs 1 to 16 By default, a Group ID is disabled meaning which the SU is not a part of that group. To make it a part of that group, select Enable. Entry Status If SU is part of a group and its Entry Status is enabled then it can communicate with all the SUs belonging to that group. If Entry Status is disabled, then the communication is blocked. After adding the MAC address, click Add. Tsunami 800 & 8000 Series - Software Management Guide 184 Advanced Configuration To edit the existing MAC addresses, click Edit icon in the WORP Intra Cell Blocking MAC Table screen. Modify the parameters as desired in the WORP Intra Cell Blocking MAC Table Add Row screen and click OK and then COMMIT. In the WORP Intra Cell Blocking MAC Table, you can change the Entry Status as either Enable/Disable/Delete. Once the status is changed, click OK and then COMMIT. 5.11 DHCP Dynamic Host Configuration Protocol (DHCP) is a network protocol that enables a server to assign an IP address to the DHCP client from a defined range of IP addresses configured for a given network. Allocating IP addresses from a central location simplifies the process of configuring IP addresses to individual DHCP clients, and also avoids IP conflicts. 5.11.1 DHCP Pool DHCP Pool is a pool of defined IP addresses which enables a DHCP Server to dynamically pick IP address from the pool and assign it to the DHCP client. To configure a range of IP addresses in the DHCP Pool, navigate to ADVANCED CONFIGURATION > DHCP > DHCP Server
> Pool. The DHCP Pool screen appears:
Each pool entry comprises the following tabulated information:
Figure 5-107 DHCP Pool Parameter Description Interface Specifies the interface type, that is, Bridge or Routing (Ethernet and Wireless). Start IP Address and End IP Address Specifies the start and end IP address of the addresses to be added to the pool. Delete Allows you to delete a pool entry.
: You can add a maximum of five pool entries to the table. A pool entry can be deleted but cannot be edited. 5.11.1.1 Adding a New Pool Entry To add a new entry to the DHCP Pool, click Add on the DHCP Pool screen. The following DHCP Pool Table Add Row screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 185 Advanced Configuration Figure 5-108 DHCP Pool Table Add Entry Enter the pool details and click Add. The entry will be updated in the DHCP pool table. To apply the configured changes, click COMMIT. 5.11.2 DHCP Server If DHCP Server is enabled, it picks automatically the IP addresses from the specific interface address pool and assigns them to the respective DHCP clients. DHCP Server feature is applicable to both Bridge and Routing Mode. In Routing mode, DHCP Server can be configured for each interface (Ethernet and Wireless) separately. Unless the DHCP Server functionality is enabled for an interface, the DHCP Server does not respond to the DHCP requests received on that interface. To configure the DHCP server parameters, navigate to ADVANCED CONFIGURATION > DHCP > DHCP Server > Interface. The DHCP Server screen appears:
Figure 5-109 DHCP Server (Bridge Mode) Tsunami 800 & 8000 Series - Software Management Guide 186 Advanced Configuration Given below is the table which explains DHCP Server parameters and the method to configure the configurable parameter(s):
Figure 5-110 DHCP Server (Routing Mode) Parameter Description DHCP Server Status By default, DHCP Server is disabled on a device. To enable DHCP Server, select Enable. A DHCP Server can be enabled only when the following two conditions are satisfied:
1. Before enabling, atleast one interface should be enabled on which the DHCP Server has to run. 2. The DHCP pool table should have atleast one pool configured for that interface. Max Lease Time Specifies the maximum lease time for which the DHCP client can use the IP address provided by the DHCP Server. The value ranges from 3600 - 172800 seconds. DHCP Interface Table Interface Type Net Mask Specifies the interface for which the DHCP Server functionality shall be configured. That is Bridge or Ethernet/Wireless in case of Routing mode. Specifies the subnet mask to be sent to the DHCP client along with the assigned IP address. The netmask configured here should be greater than or equal to the netmask configured on the interface. Default Gateway Specifies the default gateway to be sent to the DHCP client along with the assigned IP Address. Default Gateway is a node that serves as an accessing point to another network. Primary DNS Specifies the primary DNS (Domain Name Server) IP address to be sent to the DHCP client. Secondary DNS Specifies the secondary DNS IP address to be sent to the DHCP client. Tsunami 800 & 8000 Series - Software Management Guide 187 Advanced Configuration Parameter Default Lease Time Description DHCP Server uses this option to specify the lease time it is willing to offer to the DHCP client over that interface. Once the lease time expires, the DHCP Server allocates a new IP address to the device. The Default Lease Time should be less than or equal to the configured Max Lease Time. Comment Specifies a note for the device administrator. Entry Status Used to Enable or Disable the DHCP Server functionality over the interface. After configuring the required parameters, click OK and then COMMIT. 5.11.3 DHCP Relay (Routing Mode only) The DHCP relay agent relays DHCP messages between the DHCP Clients and the configured DHCP Servers on different IP networks. You can configure a maximum of five DHCP Servers. There must be at least one DHCP Server configured in order to relay DHCP request.
: DHCP Relay Agent is configurable only in Routing mode. It cannot be enabled when NAT or DHCP Server is enabled. To view and configure DHCP Relay Server parameters, navigate to ADVANCED CONFIGURATION > DHCP > DHCP Relay >
Relay Server. The DHCP Relay screen appears:
Figure 5-111 DHCP Relay By default, DHCP Relay is disabled on the device. To enable it, atleast one DHCP Server IP address should be configured. To add a DHCP Server to the Relay Server Table, click Add in the DHCP Relay screen. The DHCP Relay Server Add Row screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 188 Advanced Configuration Figure 5-112 DHCP Relay Server Add Entry Enter the DHCP Server IP Address and then click Add. After configuring the required parameters, click OK and then COMMIT.
: DHCP server is disabled automatically if DHCP Relay agent is enabled and vice-verse. Tsunami 800 & 8000 Series - Software Management Guide 189 5.12 IGMP Snooping Advanced Configuration
: IGMP Snooping is applicable only in Bridge Mode. Proxims Tsunami devices support Internet Group Management Protocol (IGMP) Snooping feature. With IGMP Snooping enabled on the device, multicast traffic is only forwarded to ports that are members of the specific multicast group. By forwarding the traffic only to the destined ports, reduces unnecessary load on devices to process packets. Explained below is the IGMP Snooping process with the help of a diagram:
The router forwards the IP multicast data to the BSU/End Point A. Figure 5-113 IGMP Snooping Process Lets say, with IGMP Snooping not enabled on the BSU/End Point A, the multicast data is transmitted over the wireless medium irrespective of whether the multicast group address is a member of the multicast group table maintained in each BSU/End Point A. With IGMP Snooping enabled, the BSU/End Point A transmits the data only when the multicast group address is a member of the multicast group table, else drops the packet. The SU/End Point B will receive the multicast data. Tsunami 800 & 8000 Series - Software Management Guide 190 Similarly, with IGMP Snooping not enabled on the SU/End Point B, the multicast data is transmitted irrespective of whether the multicast group address is a member of the multicast group table maintained in each SU/End Point B. With IGMP Snooping enabled, the SU/End Point B transmits the data to the host only when the multicast group address is a member of the multicast group table, else drops the packet. IGMP Snooping is of 2 kinds:
Advanced Configuration Active: Active IGMP Snooping listens to IGMP traffic and filters IGMP packets to reduce load on the multicast router. Passive: Passive IGMP Snooping simply listens to IGMP traffic and does not filter or interfere with IGMP.
To configure IGMP Snooping parameters, navigate to ADVANCED CONFIGURATION > IGMP Snooping. The following IGMP Snooping screen appears:
IGMP versions v1,v2 and v3 are supported. Tsunami devices supports only passive IGMP Snooping. The device can add a maximum of 64 Multicast groups in the Snooping table. Given below is the table which explains IGMP Snooping parameters and the method to configure the configurable parameter(s):
Figure 5-114 IGMP Snooping Parameter IGMP Snooping Status IGMP Membership Aging Timer IGMP Router Port Aging Timer IGMP Forced Flood Description By default, IGMP Snooping Status is disabled on the device, meaning which, the device transmits IP multicast traffic to all the ports. To forward the traffic only to the members of the specific multicast group, enable IGMP Snooping Status. Represents the time after which the IGMP multicast group age-outs or elapses. It ranges from 135 to 635 seconds. The default Aging Timer is 260 seconds. Represents the time after which the IGMP Router port age-outs or elapses. It ranges from 260 to 635 seconds. The default Aging Timer is 300 seconds. If you select Yes, all the unregistered IPv4 multicast traffic (with destination address which does not match any of the groups announced in earlier IGMP Membership reports) and IGMP Membership Reports will be flooded to all the ports. By default, IGMP Forced Flood is set to No. After configuring the required parameters, click OK and then COMMIT. Tsunami 800 & 8000 Series - Software Management Guide 191 Management This chapter provides information on how to manage the device by using Web interface. It contains information on the following:
6.1 System
: Recommended characters for the name field are A-Z a-z 0-9 - _ = : . @ $ & and space. 6.1.1 System Information The System Information tab enables you to view and configure system specific information such as System Name, System Description, Contact Details of the person managing the device, and so on. To view and configure system specific Information, navigate to MANAGEMENT > System > Information. The System Information screen appears:
Figure 6-1 System Information Tsunami 800 & 8000 Series - Software Management Guide 192 Management Given below is the table which explains System parameters and the method to configure the configurable parameter(s):
Parameter System Up-Time This is a read-only parameter. It represents the operational time of the device since its last reboot. Description System Description This is a read-only parameter. It provides system description such as system name, firmware version and the latest firmware build supported. System Name Email Phone Number Location GPS Longitude GPS Latitude GPS Altitude For example: MP-8100-BSU-WD-v2.X.Y(Build No.) Represents the name assigned to the device. You can enter a system name of maximum 64 characters and should be unique across all devices in WORP network. Represents the email address of the person administering the device. You can enter an email address of minimum 6 and maximum 32 characters. Represents the phone number of the person administering the device. You can enter a phone number of minimum 6 and maximum 32 characters. Represents the location where the device is installed. You can enter the location name of minimum 0 and maximum 255 characters. Represents the longitude at which the device is installed. You can enter a longitude value of minimum 0 and maximum 255 characters. Represents the latitude at which the device is installed. You can enter a latitude value of minimum 0 and maximum 255 characters. Represents the altitude at which the device is installed. You can enter a altitude value of minimum 0 and maximum 255 characters. After configuring the required parameters, click OK and then COMMIT. 6.1.2 Inventory Management The Inventory Management tab provides inventory information about the device. To view inventory information, navigate to MANAGEMENT > System > Inventory Management. The System Inventory Management Table appears. Tsunami 800 & 8000 Series - Software Management Guide 193 Management Figure 6-2 An Example - Inventory Management By default, the components information is auto-generated by the device and is used only for reference purpose. Click Refresh, to view the updated system inventory management information. 6.1.3 Licensed Features Licensing is considered to be the most important component of an enterprise-class device which typically has a feature-based pricing model. It is also required to prevent the misuse and tampering of the device by a wide-variety of audience whose motives may be intentional or accidental. Licensed Features are, by default, set by the company. To view the licensed features set on the device, click MANAGEMENT > System > Licensed Features. The Licensed Features screen appears. Figure 6-3 Licensed Features Tsunami 800 & 8000 Series - Software Management Guide 194 Management Given below is the table which explains each of the parameters:
Parameter Description Product Description Description about the device. Number of Radios The number of radios the device supports. Number of Ethernet Interfaces Radio 1 Allowed Frequency Band Maximum Output Bandwidth Maximum Input Bandwidth The number of Ethernet interfaces supported by the device. The operational frequency band supported by the device radio. The maximum output bandwidth limit of the device. It is represented in mbps. The maximum input bandwidth limit of the device. It is represented in mbps.
: The Input and Output Bandwidth features are referred with respect to the wireless interface. Input bandwidth refers to the data received on the wireless interface and output bandwidth refers to the data sent out of the wireless interface. Maximum Aggregate Bandwidth The maximum cumulative bandwidth of the device, which is the sum of configured output and input bandwidths. Product Family Represents the product family of the device. Product Class Represents the product class of the device, which is either indoor or outdoor. Allowed Operational Modes of Radio1 Maximum SUs Allowed MAC address of the Device is Represents the operational mode of the device, that is, BSU/SU/End Point A/End Point B. The maximum number of SUs that a BSU supports. The MAC address of the device. 6.1.3.1 License Upgrade Procedure In order to get additional bandwidth, Upgrade the License by following the procedure given below:
To purchase a license upgrade, please contact your Proxim Sales Representative; to generate a unique license file for Upgrade the bandwidth using the license file(.bin extension) generated in the above step. For more details, refer Retrieve the license information (License Info file with .lic extension) from the device. For more details, refer
section.
your device, please refer to the Technical Note available on Proxim support site:
section.
195 The File Management tab enables you to upgrade the firmware and configuration files onto the device, and retrieve configuration and log files from the device through Hypertext Transfer Protocol (HTTP) and Trivial File Transfer Protocol (TFTP). 6.2 File Management Tsunami 800 & 8000 Series - Software Management Guide
: The instructions listed above are based on the assumption that you are using the SolarWinds TFTP server; otherwise 6.2.1 TFTP Server Management A Trivial File Transfer Protocol (TFTP) server lets you transfer files across a network. By using TFTP, you can retrieve files from the device for backup or copying, and you can upgrade the firmware or the configuration files onto the device. You can
. You can also download the latest TFTP The upload or download directory is correctly set (the default directory is C:\TFTP-Root). The TFTP server is running during file upload and download. You can check the connectivity between the device and the TFTP server by pinging the device from the Personal Computer that hosts the TFTP server. The ping program should show replies from the device. The TFTP server should be configured to transmit and receive files (on the Security tab under File > Configure), with no automatic shutdown or time-out (on the Auto-Close tab).
While using TFTP server, ensure the following:
The required firmware file is present in the directory. download the SolarWinds TFTP server application from
software from SolarWinds Web site at the configuration may vary. 6.2.2 Text Based Configuration (TBC) File Management Text Based Configuration (TBC) file is a simple text file that holds device template configurations. The device supports the TBC file in XML format which can be edited in any XML or text editors. You can generate the TBC file from the CLI Session and manually edit the configurations and then load the edited TBC file to the device so that the edited configurations are applied onto the device. It differs mainly from the binary configuration file in terms of manual edition of configurations. The generated TBC file is a template which has only the default and modified configurations on the live CLI session. 6.2.2.1 Generating TBC File The TBC file is generated through CLI by executing generate command. While generating the TBC file from CLI, there is an option to generate it with or without all Management and Security Passwords. The management passwords include Network-Secret/Encryption-Key(s)/RADIUS-Shared-Secret. If included, these passwords become a part of the generated TBC file and are in a readable form. If excluded, all these passwords are not part of the generated TBC file. include CLI/WEB/SNMP passwords. The security passwords The commands used for the generation of TBC file are:
The generated TBC file contains, Default configurations
0 0 1 1 2 2 3 3 2 2 4 4 5 5 6 6 2 2 6 6 7 7 8 8
9 9
6 6
9 6
9
Any user-added or edited configurations on current live CLI session The generated Text Based Template Configuration file appears as shown below:
Tsunami 800 & 8000 Series - Software Management Guide 196 Management Figure 6-4 TBC File in xml Format 6.2.2.2 Editing the TBC File The TBC file can easily be opened and edited in any standard Text-Editors like Wordpad, MS-Word, Notepad++, Standard XML Editors. Proxim recommends XML Notepad 7 editor for editing the TBC file. You can modify any value between the double quotes() in the TBC file. It is recommended not to change the text outside the double quotes () or XML tags in the TBC file. Remove unchanged configurations from the TBC file before loading onto the device. Tsunami 800 & 8000 Series - Software Management Guide 197 Management 6.2.2.3 Loading the TBC file The TBC file can be loaded onto the device by using either SNMP, Web Interface or CLI. You can either use TFTP or HTTP to load the TBC file. By using Web Interface, you can load the TBC file by navigating to MANAGEMENT > File Management > Upgrade Configuration. To load the TBC file, it should be generated or downloaded onto the device. While loading the TBC file onto the device, any file name is accepted. Once loaded, the TBC file name is renamed to PXM-TBC.xml. If the TBC file does not contain correct XML syntax, the file will be discarded with DOM error and no configurations will be loaded. All duplicate values entered are considered as errors while loading and syslogs will be generated accordingly. Therefore, it is recommended to delete all unchanged parameters from the TBC file during its edition. Commit is required to retain the configurations across reboots after loading the TBC file.
: Both Commit and Reboot are required to accept the modifications done in the TBC File. Only reboot is required to reject the modifications. Loading the TBC file is allowed only once in an active device session (that is, if TBC file is loaded, reboot is required to apply all configurations or to load another TBC file). All configurations in the TBC file are loaded to the device irrespective of their default or modified or added configurations. Loading the TBC file takes approximately 10-20 seconds depending on the number of configurations added.
If you get any timeout errors while loading TBC file from SNMP interface, increase the time-out value to more than 30 seconds in the MIB Browser. 6.2.3 Upgrade Firmware You can update the device with the latest firmware either through HTTP or TFTP.
Remove any unmodified parameters from the TBC file, before loading it. Make sure the firmware being loaded is compatible to the device being upgraded. 1. Navigate to MANAGEMENT > File Management > Upgrade Firmware > HTTP. To upgrade the firmware via HTTP, do the following:
6.2.3.1 Upgrade Firmware via HTTP In a point-to-multipoint network, it is recommended to upgrade the base station first and then the subscriber(s). In a point-to-point network, it is recommended to upgrade the End Point A first and then the End Point B. Tsunami 800 & 8000 Series - Software Management Guide 198 Management Figure 6-5 Upgrade Firmware - HTTP 2. In the HTTP screen, click Browse to select the latest firmware file from the desired location. Ensure that the file name does not contain any space or special characters. 3. Click Upgrade. 6.2.3.2 Upgrade Firmware via TFTP To upgrade the firmware via TFTP Server, do the following:
1. Navigate to MANAGEMENT > File Management > Upgrade Firmware > TFTP. Figure 6-6 Upgrade Firmware - TFTP 2. Based on the IP mode configure either IPv4 or IPv6 address as TFTP Server address. 3. Enter the name of the latest firmware file (including the file extension) that has to be loaded onto the device in the File Name box. 4. To upgrade the device with new firmware click Upgrade and then reboot the device, or click Upgrade & Reboot. Tsunami 800 & 8000 Series - Software Management Guide 199
Management After upgrading the device with the new firmware, reboot the device; Otherwise the device will continue to run with the old firmware. It is recommended not to navigate away from the upgrade screen, while the upgrade is in progress. 6.2.4 Upgrade Configuration You can upgrade the device with the latest configuration files either through HTTP or TFTP.
: Make sure the configuration file being loaded into the device is compatible. That is, the configuration file being loaded should have been retrieved from a device of the same SKU. 6.2.4.1 Upgrade Configuration via HTTP To upgrade the configuration files by using HTTP, do the following:
1. Navigate to MANAGEMENT > File Management > Upgrade Configuration > HTTP. Figure 6-7 Upgrade Configuration - HTTP 2. 3. 4. 5. In the HTTP screen, click Browse to locate the configuration file. Select a Binary Configuration file or a Config Profile file, or a PXM-TBC.xml for Text Based Configuration file. Make sure that the file name does not contain any space or special characters. If you are upgrading the device with Binary Configuration file then click Upgrade and then reboot the device. If you are upgrading the device with Config Profile file then click Upgrade and then reboot the device. On upgrade, the device shall come up with the loaded profile. If the configuration profile is not compatible, then on reboot, the device will rollback to its old configuration. If you are upgrading the device with Text Based Configuration file then click Upgrade to upgrade the device with the config file and then click Load for loading the config file onto the device. Alternatively, you can perform both upgrade and load operation in one single step, by clicking Upgrade & Load. Tsunami 800 & 8000 Series - Software Management Guide 200 6.2.4.2 Upgrade Configuration via TFTP To upgrade the configuration files by using TFTP Server, do the following:
1. Navigate to MANAGEMENT > File Management > Update Configuration > TFTP. Management Figure 6-8 Upgrade Binary Configuration via TFTP 2. You can update the device with three types of configuration files: Binary, Text Based and Config Profile. To update the device with Binary Configuration file, select Binary Config. Based on the IP mode configure either IPv4 or IPv6 address as TFTP Server address. Enter the name of the Binary file (including the file extension) that has to be downloaded onto the device in the File Name box. 3. To update the device with Text Based Configuration files, select Text Based Config. Based on the IP mode configure either IPv4 or IPv6 address as TFTP Server address. Enter the name of the Text Based file (including the file extension) that has to be downloaded onto the device in the File Name box. Figure 6-9 Upgrade Text Based Configuration via TFTP Tsunami 800 & 8000 Series - Software Management Guide 201 4. To update the device with Configuration Profile files, select Config Profile. Management Based on the IP mode, configure either IPv4 or IPv6 address as TFTP Server address. Enter the name of the Config Profile file (including the file extension) that has to be downloaded onto the device in the File Name box. Figure 6-10 Upgrade Configuration Profile via TFTP 5. 6. 7. If you are upgrading the device with Binary Configuration file then click Upgrade and then reboot the device, or click Upgrade & Reboot. If you are upgrading the device with Text Based Configuration file, click Upload and then click Apply. If you are upgrading the device with Config profile file then click Upload and then reboot the device, or click Apply
& Reboot.
: It is recommended not to navigate away from the upgrade screen, while the upgrade is in progress. 6.2.5 Upgrade License 6.2.5.1 Upgrade License via HTTP more details. You can upgrade the license file on the device either through HTTP or TFTP. Refer ) To upgrade the license using HTTP, do the following:
1. Navigate to MANAGEMENT > File Management > Upgrade License > HTTP.
A
section for Tsunami 800 & 8000 Series - Software Management Guide 202 Management Figure 6-11 Upgrade License via HTTP 2. In the HTTP screen, click Browse to locate the license upgrade(.bin) file to be loaded on the device. 3. Click Upgrade button to upgrade the license on the device and then reboot the device. 6.2.5.2 Upgrade License via TFTP To upgrade the license file using TFTP Server, do the following:
1. Navigate to MANAGEMENT > File Management > Update License > TFTP. Figure 6-12 Upgrade License via TFTP 2. Based on the IP mode, configure either IPv4 or IPv6 address as TFTP Server address. 3. Enter the name of the file (including the file extension) that has to be loaded on the device, in the File Name box. 4. Click Upgrade button to upgrade the license on the device and then reboot the device.
It is applicable only to MP-820-BSU-100, MP-820-SUA-50+, MP-825-SUR-50+, and QB-825-LNK-50+ devices. Tsunami 800 & 8000 Series - Software Management Guide 203 Upgrade license can be done through CLI/Web Interface/SNMP. Management 6.2.6 Retrieve From Device The Retrieve From Device tab allows you to retrieve logs, config files, and license info from the device either through HTTP or TFTP. 6.2.6.1 Retrieve from Device via HTTP To retrieve files from the device by using HTTP, do the following:
1. Navigate to MANAGEMENT > File Management > Retrieve from Device > HTTP. Figure 6-13 Retrieve Files via HTTP 2. Select the type of file that you want to retrieve from the device from the File Type drop down box. The files may vary depending on your device. The File Types are:
a. Config b. Event Log c. Temperature Log d. Text Based Template Config e. Debug Log f. Config Profile g. License Info The Config Profile is used for replicating the configuration of a master device on to other similar devices by excluding the unique parameters like System information, IP configuration, Ethernet configuration, Wireless excluded. On selecting config profile type the following screen appears:
configuration based on the selection# By default, System Information and IP Configuration parameters are Tsunami 800 & 8000 Series - Software Management Guide 204 Management Figure 6-14 Retrieve Config Profile File via HTTP After excluding the unique parameters, click Create Profile for creating the profile and then click Retrieve. When the retrieved configuration profile file is loaded on target devices, the target devices will come up with configuration of the master device except the excluded parameters. The excluded parameters are retained as configured on the target device.
: Config Profile is applicable only to the compatible devices. 3. Click Retrieve. Based on the selected file, the following Download screen appears. 4. Right-click the Download link and select Save Target As or Save Link As to save the file to the desired location. Figure 6-15 Download Screen Tsunami 800 & 8000 Series - Software Management Guide 205 6.2.6.2 TFTP Retrieve To retrieve files from the device by using TFTP, do the following:
1. Navigate to MANAGEMENT > File Management > Retrieve from Device > TFTP. Management Figure 6-16 Retrieve Files via TFTP 2. Based on the IP mode, configure either IPv4 or IPv6 address as TFTP Server address. 3. Enter the name of the file (including the file extension) that has to be retrieved from the device, in the File Name box. 4. Select the file type that you want to retrieve from the device, from the File Type drop down box. The file types are:
a. Config b. Event Log c. Temperature Log d. Text Based Template Config e. Debug Log f. Config Profile g. License Info The Config Profile is used for replicating the configuration of a master device on to other similar devices by excluding the unique parameters like System information, IP configuration, Ethernet configuration, Wireless configuration based on the selection. By default, System Information and IP Configuration parameters are excluded. On selecting config profile type the following screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 206 Management Figure 6-17 Retrieve Config Profile File via TFTP After excluding the unique parameters, click Create Profile for creating the profile and then click Retrieve. When the retrieved configuration profile file is loaded on the target devices, the target devices will come up with configuration of the master device except the excluded parameters. The excluded parameters are retained as configured on the target device. 5. Click Retrieve. The retrieved file can be found in the TFTP Server folder. cannot be retrieved. MP-825-SUR-50+, and QB-825-LNK-50+ devices. Config Profile is applicable only to the compatible devices. When the device is running with default factory settings, there is no Binary Configuration file present and hence it Similarly, the Text Based Template Configuration file does not exist if it is not generated from the CLI. You can retrieve Event Logs only when they are generated by the device. Retrieval of license info file (CLI/Web Interface/SNMP) is supported only by MP-820-BSU-100, MP-820-SUA-50+,
For more information on license upgrade, refer )
sections.
and '
A
To configure HTTP/HTTPS interface parameters, navigate to MANAGEMENT > Services > HTTP / HTTPS. The Services tab lets you configure the HTTP/HTTPS, Telnet/SSH and SNMP interface parameters. 6.3.1 HTTP/HTTPS 6.3 Services Tsunami 800 & 8000 Series - Software Management Guide 207 Management Given below is the table which explains HTTP/HTTPS parameters and the method to configure the configurable parameter(s). Figure 6-18 HTTP/HTTPS Parameter Admin Password Description By default, the Administrator password to access HTTP/HTTPS interface is public. For security reasons, it is recommended to change the default password. The password should be alphanumeric with minimum of 6 and maximum of 32 characters.
: The following special characters are not allowed in the password:
- = \ ? / space Monitor Password The Administrator user has the privilege to change the Monitor user password. By default, the Monitor user password to access HTTP/HTTPS interface is public. For security reasons it is recommended to change the default password. The password should be alphanumeric with minimum of 6 and maximum of 32 characters.
: The following special characters are not allowed in the password:
- = \ ? / space HTTP HTTP Port By default, a user can manage the device through Web Interface. To prevent access to the device through Web Interface, select Disable. Represents the HTTP port to manage the device through Web Interface. By default, the HTTP port is 80. Tsunami 800 & 8000 Series - Software Management Guide 208 Management Parameter HTTPS By default, a user can manage the device through Web Interface over secure socket Layer
(HTTPS). To prevent access to the device through HTTPS, select Disable. Description
: The password configuration for HTTPS is same as configured for HTTP. After configuring the required parameters, click OK, COMMIT and then REBOOT. 6.3.2 Telnet/SSH To configure Telnet/SSH interface parameters, navigate to MANAGEMENT > Services > Telnet / SSH. Figure 6-19 Telnet/SSH Tsunami 800 & 8000 Series - Software Management Guide 209 Given below is the table which explains Telnet/SSH parameters and the method to configure the configurable parameter(s):
Management Parameter Admin Password Description By default, the Administrator password to access Telnet/SSH interface is public. For security reasons, it is recommended to change the default password. The password should be alphanumeric with minimum of 6 and maximum of 32 characters.
: The following special characters are not allowed in the password:
- = \ ? / space Monitor Password The Administrator user has the privilege to change the Monitor user password. By default, the Monitor user password to access Telnet/SSH interface is public. For security reasons it is recommended to change the default password. The password should be alphanumeric with minimum of 6 and maximum of 32 characters.
: The following special characters are not allowed in the password:
- = \ ? / space Telnet By default, a user can manage the device through Telnet. To prevent access to the device through Telnet, select Disable. Telnet Port Represents the port to manage the device using Telnet. By default, the Telnet port is 23. Telnet Sessions SSH SSH Port SSH Sessions The number of Telnet sessions which controls the number of active Telnet connections. A user is restricted to configure a maximum of 3 Telnet sessions. By default, the number of Telnet sessions allowed is 2. By default, a user can manage the device through SSH. To prevent access to the device through SSH, select Disable. Represents the port to manage the device using Secure Shell. By default, the Secure Shell port is 22. Represents the number of SSH sessions which controls the number of active SSH connections. A user is restricted to configure a maximum of 3 SSH sessions. By default, the number of SSH sessions allowed is 1.
: The total number of CLI sessions allowed is 3, so the sum of Telnet and SSH sessions cannot be more than 3. For example, if you configure the number of Telnet sessions as 2, then the number of SSH sessions can only be a value 0 or 1. After configuring the required parameters, click OK, COMMIT and then REBOOT. Tsunami 800 & 8000 Series - Software Management Guide 210 6.3.3 SNMP To configure SNMP interface parameters, navigate to MANAGEMENT > Services > SNMP. Management Figure 6-20 SNMPv1-v2c Tsunami 800 & 8000 Series - Software Management Guide 211 Management Given below is the table which explains SNMP parameters and the method to configure the configurable parameter(s):
Figure 6-21 SNMPv3 Parameter SNMP By default, the user has the access to manage the device through SNMP Interface. To prevent access to the device through SNMP, select Disable. Description
: Any change in the SNMP status will affect the Network Management System access. Version Allows you to configure the SNMP version. The supported SNMP versions are v1-v2c and v3. By default, the SNMP version is v1-v2c. SNMP v1-v2c Specific Parameters Read Password Represents the read only community string used in SNMP Protocol. It is sent along with each SNMP GET / WALK / GETNEXT / GETBULK request to allow or deny access to the device. This password should be same as read password set in the NMS or MIB browser. The default password is public. The password should be of minimum 6 and maximum 32 characters. Tsunami 800 & 8000 Series - Software Management Guide 212 Management Parameter Description
: The following special characters are not allowed in the password:
- = \ ? / space Read/Write Password Represents the read-write community string used in SNMP Protocol. It is sent along with each SNMP GET / WALK / GETNEXT / SET request to allow or deny access to the device. This password should be same as read-write password set in the NMS or MIB browser. The default password is public. The password should be of minimum 6 and maximum 32 characters.
: The following special characters are not allowed in the password:
- = \ ? / space SNMP v3 Specific Parameters Security level The supported security levels for the device are AuthNoPriv and AuthPriv. Select AuthNoPriv for Extensible Authentication or AuthPriv for both Authentication and Privacy (Encryption). Priv Protocol Applicable only when the Security Level is set to AuthPriv. Represents the type of privacy (or encryption) protocol. Select the encryption standard as either AES-128 (Advanced Encryption Standard) or DES (Data Encryption Standard). The default Priv Protocol is AES-128.
: The following special characters are not allowed in the password:
- = \ ? / space Priv Password Applicable only when the Security Level is set to AuthPriv. Represents the pass key for the selected Privacy protocol. The default password is public123. The password should be of minimum 8 and maximum 32 characters.
: The following special characters are not allowed in the password:
- = \ ? / space Auth Protocol Represents the type of Authentication protocol. Select the encryption standard as either SHA (Secure Hash Algorithm) or MD5 (Message-Digest algorithm). The default Auth Protocol is SHA. Auth Password Represents the pass key for the selected Authentication protocol. The default password is public123. The password should be of minimum 8 and maximum 32 characters. After configuring the required parameters, click OK, COMMIT and then REBOOT. Tsunami 800 & 8000 Series - Software Management Guide 213 Management 6.3.3.1 SNMP Trap Host Table The SNMP Trap Host table allows you to add a maximum of 5 Trap servers IP address to which the SNMP traps will be delivered. By default, the SNMP traps are delivered to 169.254.128.133.
: The default SNMP Trap Host Table entry cannot be deleted. To add entries to the Trap Host Table, click Add in the Services screen. The SNMP Trap Host Table Add Row screen appears:
Configure the following parameters:
Figure 6-22 Add Entries to SNMP Host Table IP Address: Based on the IP mode, enter the IPv4 or IPv6 address of the Trap server to which SNMP traps will be delivered.
: IPv6 address should be the global IP address and not the link local IP address. Password: Type the password to authenticate the Trap Server. The following special characters are not allowed in the password: - = \ ? / space
: Applicable only to SNMP v1-v2c. Comment: Type comments, if any. Entry Status: Select the entry status as either Enable or Disable. If enabled, the device will send SNMP traps to the authenticated Trap Server. After configuring the required parameters, click Add and then COMMIT. 6.3.3.2 Edit SNMP Trap Host Table Edit the desired SNMP Trap Host Table entries and click OK, COMMIT and then REBOOT. Tsunami 800 & 8000 Series - Software Management Guide 214 Management 6.3.4 Logs The device supports two types of log mechanisms:
1. Event Log: Based on the configured event log priority, all the log messages are logged and used for any analysis. This log messages remain until they are cleared by the user. 2. Syslog: They are similar to Event logs except that they are cleared on device reboot. To configure Event log and Syslog priority, navigate to MANAGEMENT > Services > Logs. The following screen appears:
Event Log Priority: By default, the priority is set to Notice. You can configure the event log priority as one of the following:
Figure 6-23 Logs Emergency Alert Critical Error Warning Notice Info Debug Please note that the priorities are listed in the order of their severity, where Emergency takes the highest severity and Debug the lowest. When the log priority is configured as high, all the logs with low priority are also logged. For example, if Event Log Priority is set to Notice, then the device will log all logs with priorities Notice, Warning, Error, Critical, Alert and Emergency. Syslog Status: By default, Syslog Status is enabled and default priority is Critical. If desired, you can choose to disable. Syslog Priority: Configuration is same as Event Log Priority. After configuring the required parameters, click OK and then COMMIT. Tsunami 800 & 8000 Series - Software Management Guide 215 Management 6.3.4.1 Configure a Remote Syslog host Configure a syslog host (server) in order to forward syslog messages to it.
: You can configure only one syslog host. Follow the following steps to configure a remote syslog host:
1. Click Add in the Syslog Host Table screen. The Syslog Host Table Add Row screen appears:
2. IP Address: Based on the IP mode, enter IPv4 or IPv6 address of the Syslog host. Figure 6-24 Syslog Host Table Add Row
: IPv6 address should be the global IP address and not the link local IP address. 3. Host Port: Represents the port on which the Syslog host listens to the log messages sent by the device. The default port is 514.
: The user must configure the correct port number on which the Syslog host is running. Choice of port number must be in line with the standards for port number assignments defined by Internet Assigned Numbers Authority (IANA). 4. Comments: Types comments, if any. 5. Click Add. The syslog host is added to the Syslog Host Table. Tsunami 800 & 8000 Series - Software Management Guide 216 Management Figure 6-25 Syslog Host Configured For some reason, if the configured syslog host parameters are changed then you can edit it directly in the Syslog Host Table entry. You can change the following parameters:
IP Address Port Host Comments Entry Status:
Enable: By default, the configured Syslog host is enabled on the device. Disable: To disable an entry in the Syslog Host Table, click Disable. Delete: To delete the configured Syslog host, click Delete. After doing the necessary changes, click OK followed by COMMIT. 6.4 Simple Network Time Protocol (SNTP) Proxims point-to-multipoint and point-to-point devices are furnished with Simple Network Time Protocol (SNTP) Client software that enables to synchronize devices time with the network time servers. The SNTP Client when enabled on the device(s), sends an NTP (Network Time Protocol) request to the configured time servers. Upon receiving the NTP response, it decodes the response and sets the received date and time on the device after adjusting the time zone and day light saving. In case, the time servers are not available, then users also have the option to manually set the date and time on the device. To synchronize devices time with time servers or manually set the time, navigate to MANAGEMENT > SNTP. The SNTP screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 217 Management Given below is the table which explains SNTP parameters and the method to configure the configurable parameter(s):
Figure 6-26 Time Synchronization Parameter Enable SNTP Status Select this parameter to enable SNTP Client on the device. If enabled, the SNTP Client tries to synchronize the devices time with the configured time servers. Description By default, the SNTP status is disabled. Primary Server IP Address/Domain Name Enter the host name, or the IP address based on IP modes (IPv4 only or IPv4 and IPv6) of the primary SNTP time server. The SNTP Client tries to synchronize devices time with the configured primary server time.
If host name is configured, instead of IP address then make sure that DNS server IP is configured on the device. IPv6 address should be the global IP address and not the link local IP address. Secondary Server IP Address/Domain Name Enter the host name, or the IP address based on IP modes (IPv4 only or IPv4 and IPv6) of the secondary SNTP time server. If the primary server is not reachable, then SNTP client tries to synchronize devices time with the secondary server time. If the SNTP client is not able to sychronize the time with both the servers
(primary and secondary), then it tries to synchronize again after every one minute. IPv6 address should be the global IP address and not the link local IP address. Tsunami 800 & 8000 Series - Software Management Guide 218
Management Parameter Time Zone Configure the time zone from the available list. This configured time zone is considered before setting the time, received from the time servers, on the device. Description Day Light Saving Time Configure the Day Light Saving time from the available list. This configured Day Light Saving time is considered before setting the time, received from the time servers, on the device. ReSync Interval Set ReSync time interval ranging from 0 to 1440 minutes. Once the time is synchronized, the SNTP Client tries to resynchronize with the time servers after every set time interval. By default, the ReSync interval is set to 60 minutes. Sync Status Specifies the SNTP Client sync status when it tries to ReSync again with the time servers. The status is as follows:
Current Date/Time Manual Time Configuration displays the status as Disabled. Displays the current date and time. Synchronized: The SNTP client has synchronized time with the time servers. Synchronizing: The SNTP client is in the process of synchronzing time with the time servers. Disabled: The SNTP client will not synchronize the time with the time servers and If SNTP Client is disabled on the device or the time servers are not available on the network, then the user can manually set the time. Enter the time manually in the format:
MM-DD-YYYY HH:MM:SS. If SNTP is enabled, it displays the time the device received from the SNTP server. If SNTP is not enabled, then it displays the time manually set by the user.
To save the configured parameters, click OK and then COMMIT. 6.5 Access Control the user has to set the time again. behind the actual time. So, it is recommended to periodically check and adjust the time. Manual time configuration is not retained across reboots. After every reboot Over a period of time, with manual time configuration, the device may lag The Access Control tab enables you to control the device management access through specified host(s). You can specify a maximum of five hosts to control device management access. To configure management access control parameters, navigate to MANAGEMENT > Access Control. The Management Access Control screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 219 Management Figure 6-27 Management Access Control By default, the Management Access Control feature is disabled on the device. To enable, select Enable from the Access Table Status box and click OK. Reboot the device, for the changes to take effect.
: Only when the Access Table Status is enabled, you can add host(s) to the Management Access Control Table. 6.5.0.1 Add Host(s) to Management Access Control Table To add a host to the Management Access Control Table, do the following:
1. Click Add in the Management Access Control screen. The Management Access Table Add Row screen appears:
Figure 6-28 Management Access Table Add Row 2. IP Address: Based on the IP mode, configure either IPv4 or IPv6 address of the host that controls the device management access. 3. Entry Status: By default, the entry status is enabled meaning which the specified host can control the device management access. Edit the status to Disable, if you do not want the host to control the device management access. 4. Click Add.
: If MAC ACL is enabled, configure at least one entry in the Management Access Table with the IP address (of the PC or the management station), in order to manage the device. 6.5.0.2 Edit Management Access Control Table Entries Edit the desired host entries and click OK, COMMIT and then REBOOT. Tsunami 800 & 8000 Series - Software Management Guide 220 6.6 Reset to Factory The Reset to Factory tab allows you to reset the device to its factory default state. When this operation is performed, the device will reboot automatically and comes up with default configurations. To reset the device to its factory defaults, navigate to MANAGEMENT > Reset To Factory. The Factory Reset screen appears:
Management Click OK, if you wish to proceed with factory reset, else click Cancel. Figure 6-29 Reset to Factory Defaults 6.7 Convert QB to MP The Convert QB to MP tab lets you convert a QB to SU so that the converted device can connect to a BSU and operate as a SU. This feature is applicable only to, You can convert a QB to SU mode by using two methods:
QB-8151-EPR which converts to a SU QB-8250-EPR which converts to a MP-8250-SUR QB-8150-EPR which converts to a MP-8150-SUR QB-8200-EPA which converts to a MP-8200-SUA QB-8100-EPA which converts to a MP-8100-SUA QB-8150-EPR-100 which converts to a MP-8150-SUR-100 QB-825-EPR-50 which converts to a MP-825-CPE-50 QB-825-EPR-50+ which converts to a MP-825-SUR-50+
Method 1: Web Interface Method 2: Load an SU config file (retrieved from another SU) onto the QB device and then reboot.
: Even after conversion from QB to MP, the device description still shows as QB. Tsunami 800 & 8000 Series - Software Management Guide 221 To convert a QB to SU using Web Interface, do the following:
1. Navigate to MANAGEMENT > Convert QB to MP. The Convert QB to MP screen appears:
Management Figure 6-30 Convert QB to MP 2. Click OK. 3. Reboot the device for the changes to take effect.
QB. the device will reset to factory default upon initialization and operate in QB mode. In case of Method 1 (Web Interface) conversion, QB mode configuration will be deleted. A QB after converting to SU will function in SU mode only. It will accept only MP firmware for upgrade. The version of the firmware being upgraded to should be 2.4.0 or later. If earlier version of the firmware is loaded, When upgrading a converted device from Bootloader, it must be done using a QB image, as the device is licensed as The conversion of the device from QB to SU requires a reboot. Reset to factory defaults, always results in the device initializing in QB mode. Tsunami 800 & 8000 Series - Software Management Guide 222 Monitor This chapter contains information on how to monitor the device by using Web interface. It contains information on the following:
H
E
I
C
B
F
G
7.1 System
The System tab enables to view system specific information such as LED/RSSI Display.
: 'RSSI LED' feature is applicable only to 82x devices. To view LED/RSSI Display, navigate to MONITOR > System. The LED/RSSI Display screen appears:
Figure 7-1 LED/RSSI Display When the link is established, Received Signal Strength Indicator (RSSI) LEDs on the scaling mask glow. Scaling mask LEDs indicate the received signal strength of the link. The more LEDs on the scaling mask glow, better is the signal. To select the LED Display Status, navigate to Advanced Configuration > System. By default, RSSI Display mode is enabled, if required the user can select the Disable (LEDs Off) mode. In Disable (LEDs Off) mode, all the 5 LEDs will be off. The LED behavior in RSSI Display mode is given below:
By default all the 5 LEDs will blink for an interval of 1 second to indicate the device is UP. For a BSU, in order to monitor the SU link statistics, the user should first configure the wireless MAC address of the SU. If the configured SU is registered with the BSU, then the LEDs will glow based on the RSSI value else all the 5 LEDs will blink. Tsunami 800 & 8000 Series - Software Management Guide 223 D
B
B
For a SU, if the SU is registered with the BSU, then the LEDs will glow based on the RSSI value else all the 5 LEDs will blink. For a CPE, if the CPE is registered with the BSU, then the LEDs will glow based on the RSSI value else all the 5 LEDs will blink. For QB, if EndPointA is registered with EndPointB, then the LEDs will glow based on the RSSI value of each EndPoint. else all the 5 LEDs will blink. Monitor Interface Statistics allows you to monitor the status and performance of the Ethernet and Wireless interfaces of the device. 7.2 Interface Statistics 7.2.1 Ethernet Statistics To view the Ethernet interface statistics, click MONITOR > Interface Statistics. The Interface Statistics screen appears:
Figure 7-2 Ethernet Interface Statistics To view Ethernet statistics, click Ethernet 1 or Ethernet 2 depending on the Ethernet interfaces supported by your device. Given below is the table which explains the parameters displayed in the Ethernet Statistics screen:
Specifies the largest size of the data packet received or sent on the Ethernet interface. The MTU size varies from 1500 to 1514 depending on the MTU configuration (See Description Specifies the MAC address at the Ethernet protocol layer. Specifies the current operational state of the Ethernet interface. Specifies the total number of octets received on the Ethernet interface. Parameter MTU MAC Address Operational Status In Octets
Tsunami 800 & 8000 Series - Software Management Guide 224 Monitor Parameter In Unicast Packets Specifies the number of subnetwork- unicast packets delivered to the higher level protocol. Description In Non-unicast Packets Specifies the number of non-unicast subnetwork packets delivered to the higher level protocol. In Errors Out Octets Out Packets Out Discards Specifies the number of inbound packets that contained errors and are restricted from being delivered. Specifies the total number of octets transmitted out from the Ethernet interface. Specifies the total number of packets requested by the higher level protocol and then, transmitted. Specifies the number of error-free outbound packets chosen to be discarded to prevent them from being transmitted. One possible reason for discarding such a packet could be to free up buffer space. Out Errors Specifies the number of outbound packets that are not transmitted because of errors. To view the updated Ethernet statistics, click Refresh. To delete the Ethernet statistics, click Clear. Tsunami 800 & 8000 Series - Software Management Guide 225 7.2.2 Wireless Statistics To view the Wireless interface statistics, click MONITOR > Interface Statistics > Wireless1. Monitor Given below is the table which explains the parameters displayed in the Wireless statistics screen:
Figure 7-3 Wireless Interface Statistics Parameter MTU Description Specifies the largest size of the data packet received or sent on the wireless interface. The MTU size can range from 350 to 3808 bytes for High throughput modes and 350 to 2304 bytes for legacy mode. The default and maximum value of the WORP MTU is 3808 bytes for higher throughput and 2304 bytes for legacy mode. MAC Address Specifies the MAC address at the wireless protocol layer. Operational Status Specifies the current operational state of the wireless interface. In Octets In Packets Specifies the total number of octets received on the wireless interface. Specifies the number of packets delivered to the higher level protocol. Tsunami 800 & 8000 Series - Software Management Guide 226 Monitor Parameter Description In Errors Out Octets Out Packets Out Discards Out Errors Retunes Specifies the number of inbound packets that contained errors and are restricted from being delivered. Specifies the total number of octets transmitted out from the wireless interface. Specifies the total number of packets requested by the higher level protocol and then, transmitted. Specifies the number of error-free outbound packets chosen to be discarded to prevent them from being transmitted. One possible reason for discarding such a packet could be to free up buffer space. Specifies the number of outbound packets that are not transmitted because of errors. Specifies the number of times the radio is re-tuned for better performance of the device. Max Tx Power Indicates the maximum power that the radio can radiate. SNR Statistics represents the signal strength with regard to the noise at the antenna ports. SNR Statistics Antenna Status Control Extension Decrypt Errors CRC Errors PHY Errors Specifies the antenna ports available for the product. Please note that the antenna ports vary depending on the product. Specifies the configuration status of the antenna ports. ON indicates that antenna port is enabled and OFF indicates that antenna port is disabled. Specifies the SNR value of the packet received at the selected channel frequency. This parameter is applicable only to the 40 MHz modes, that is, 40 PLUS and 40 Minus. It specifies the SNR value of the packet received on the extension channel (20MHz). Rx Error Details This parameter is applicable only if security is enabled. It indicates the number of received packets that failed to decrypt. Specifies the number of received packets with invalid CRC. Specifies the total Rx PHY Errors. It generally indicates the interference in the wireless medium. To view the updated Wireless statistics, click Refresh. To delete the Wireless statistics, click Clear. 7.2.3 PPPoE Statistics
: Applicable only to an SU in Routing mode. To view PPPoE interface statistics, navigate to MONITOR > Interface Statistics > PPPoE > PPP Interface Stats. Tsunami 800 & 8000 Series - Software Management Guide 227 Monitor The PPPoE interface parameters are same as the Ethernet interface parameters. Please note that if a link is not established between a PPPoE client and server, then the device displays the following message. Figure 7-4 PPPoE Interface Statistics Figure 7-5 PPPoE Server - No Link Established To view the updated PPPoE interface statistics, click Refresh. Please note that for every 4 seconds, the interface statistics gets refreshed. To view the PPPoE connection status such as the number of attempts made to start a session between PPPoE client and server, and the number of attempts failed to establish a connection, click PPPoE Connection Stats. Figure 7-6 PPPoE Connection Statistics Tsunami 800 & 8000 Series - Software Management Guide 228 To view updated connection statistics, click Refresh. To restart the session between the PPPoE client and server, click Restart PPPoE Session. On successfully re-establishing a session, the IP address of the wireless interface will be assigned again by the PPPoE server, if Address Type is set to PPPoE-ipcp. Monitor To clear the existing connection statistics, click Clear. 7.2.4 IP Tunnels
: Applicable only in Routing Mode. To view IP Tunnels interface statistics, click MONITOR > Interface Statistics > IP Tunnels. The following IP Tunnel Interface Statistics screen appears:
Given below is an explanation to each of these parameters:
Figure 7-7 IP Tunnels Interface Statistics Parameter Description Name Alias Maximum Transmission Unit
(MTU) Specifies the tunnel interface name. Specifies the supplementary tunnel interface name. Specifies the largest size packet or frame that can be sent over the tunnel interface. The MTU of the tunnel interface is derived from the underlying interface:
For IP-IP tunnel interface: MTU = Underlying interface MTU 20 bytes (IP header) For IP-GRE interface: MTU = Underlying interface MTU 24 bytes (IP header + gre protocol) Operational Status The Operational Status indicates only the tunnel interface status. The status can be either UP or DOWN.
: For the tunnel to function correctly both ends should be configured correctly. Tsunami 800 & 8000 Series - Software Management Guide 229 Parameter Details Provides a more detailed statistics about the tunnel interface. To view the detailed statistics, click
. Description Monitor Figure 7-8 Detailed IP Tunnels Interface Statistics The detailed tunnel interface parameters are similar to the Ethernet Interface Statistics. 7.3 WORP Statistics 7.3.1 General Statistics Please refer to G
. WORP General Statistics provides general statistics about the WORP. To view General Statistics, navigate to MONITOR > WORP Statistics > Interface 1 > General Statistics. The following WORP General Statistics screen appears. Tsunami 800 & 8000 Series - Software Management Guide 230 Monitor Figure 7-9 WORP General Statistics (SU/End Point A/End Point B) Figure 7-10 WORP General Statistics (BSU) Tsunami 800 & 8000 Series - Software Management Guide 231 7.3.1.1 Basic Statistics Given below is an explanation to the basic parameters:
Monitor Parameter Description Interface Type Specifies the type of radio interface. WORP Protocol Version Specifies the version of the WORP Protocol used. This information is useful to the customer support team for debugging purpose only. Specifies the sent or received data frames through wireless interface. WORP Data Messages Poll Data Refers to the number of polls with data messages sent or received. Poll No Data Refers to the number of polls with no data messages sent or received. Reply Data Refers to the number of poll replies with data messages sent or received. Reply More Data Refers to the number of poll replies with more data messages sent or received. Reply No Data Refers to the number of poll replies with no data messages sent or received. Poll No Replies Refers to the number of times the poll messages are sent by a BSU/End Point A and received no reply from SU/End Point B. This parameter is applicable only to a BSU. Specifies the number of transmissions occurred through the interface. Data Transmission Statistics Send Success Refers to the number of data messages sent and acknowledged by the peer successfully. Send Retries Send Failures Refers to the number of data messages that are re-transmitted and acknowledged by the peer successfully. Refers to the number of data messages that are not acknowledged by the peer even after the specified number of retransmissions. Receive Success Refers to the number of data messages received and acknowledged successfully. Receive Retries Refers to the number of successfully received re-transmitted data messages. Receive Failures Refers to the number of data messages that were not received successfully. Registration Details Specifies the status of the entire registration process. Remote Partners Refers to the number of remote partners. For an SU/End Point A/End Point B, the number of remote partners is always zero or one. Announcements Refers to the number of Announcement messages sent or received on WORP interface. Request For Service Refers to the number of requests for service messages sent or received. Registration Requests Refers to the number of registration request messages sent or received on WORP interface. Registration Rejects Refers to the number of registration reject messages sent or received on WORP interface. Authentication Requests Refers to the number of authentication request messages sent or received on WORP interface. Tsunami 800 & 8000 Series - Software Management Guide 232 Monitor Parameter Description Authentication Confirms Refers to the number of authentication confirm messages sent or received on WORP interface. Registration Attempts Refers to the number of times a registration attempt has been initiated. Registration Incompletes Refers to the number of registration attempts that are not yet completed. Registration Timeouts Refers to the number of times the registration procedure timed out. Registration Last Reason Refers to the reason for the last registration getting aborted or failed.
: For better results, the Send Failure or Send Retrieve must be low in comparison to Send Success. The same applies for Receive Retries or Receive Failure. Click Clear to delete existing general statistics. Click Refresh to view updated WORP general statistics. 7.3.1.2 Advanced Statistics Advanced statistics is applicable only to the BSU. The Advanced Statistics screen displays the wireless transmission values used by the BSU to send announcement and broadcast messages. Given below is an explanation to the advanced parameters:
Figure 7-11 WORP Advanced Statistics Parameter Description Tx Rate Displays the Data Transmission Rate used by the BSU. Data Stream Displays the Data Streams used by the BSU. Tsunami 800 & 8000 Series - Software Management Guide 233 Monitor Parameter Description TPC EIRP Power Displays the TPC value currently applied by the device to adjust the transmit power radiated by the radio. Displays the current EIRP that a radio antenna radiates (after applying the TPC). Displays the current transmit power radiated by the radio (after applying the TPC). Tx Antenna Ports Indicates the status of the antenna ports at the BSU end. Click Refresh to view updated WORP advanced statistics. 7.3.2 Link Statistics 7.3.2.1 SU / End Point B Link Statistics
: SU Link Statistics is applicable only to a BSU, and End Point B Link Statistics is applicable only to a End Point A device. SU Link statistics provides information about the SUs connected to a BSU. Similarly, End Point B Link Statistics provides information about an End Point B currently connected to an End Point A device. To view link statistics, navigate to MONITOR > WORP Statistics > Interface 1 > SU Link Statistics. Figure 7-12 An Example - SU Link Statistics (For 82x Devices) Tsunami 800 & 8000 Series - Software Management Guide 234 Monitor Figure 7-13 An Example - SU Link Statistics (For All Devices) Given below is an explanation to each of these parameters:
Parameter SU Name/
End Point B Name MAC Address Represents the name of the SU/End Point B connected to a BSU/End Point A respectively. Description Represents the MAC address of the SU/End Point B connected to a BSU/End Point A respectively. Local Tx Rate (Mbps) Represents the data transmission rate at the local (current device) end. Remote Tx Rate
(Mbps) Represents the data transmission rate at the remote (peer) end. Local Antenna Port Info Indicates the status of the antenna ports at the local end. The following symbols indicate the status of the antenna ports. Indicates the antenna port is disabled. Indicates the antenna port is enabled and signal is present. Local Tx Antenna Port Info Indicates the status of the antenna ports at the transmitting end. The following symbols indicate the status of the antenna ports. Indicates the antenna port is disabled. Indicates the antenna port is enabled and signal is present. Local Rx Antenna Port Info Indicates the status of the antenna ports at the receiving end. The following symbols indicate the status of the antenna ports. Indicates the antenna port is disabled. Indicates the antenna port is enabled and signal is present. Tsunami 800 & 8000 Series - Software Management Guide 235 Monitor Parameter Local Signal (dBm) Represents the signal level with which the device at the local end receives frames from the device at the remote end, through wireless medium. Description Local Noise (dBm) Represents the noise measured at the local end antenna ports. Local SNR (dB) Represents the SNR measured by the receiver at the local end and is based on the Local Signal and Local Noise. Remote Rx Antenna Port Info Indicates the status of the remote end antenna ports. The antenna ports status is same as explained in Local Antenna Port Info. Remote Signal (dBm) Represents the signal level with which the device at the remote end receives frames, through wireless medium. Remote Noise (dBm) Represents the noise measured at the remote end antenna ports. Remote SNR (dB) Represents the SNR measured by the receiver at the remote end and is based on the Remote Signal and Remote Noise. Current Tx Power
(dBm) TPC: Displays the TPC value currently applied by the device to adjust the transmit power radiated by the radio antenna.
: For a given data rate, if the configured TPC value is greater than the maximum transmit power supported by the radio then maximum transmit power supported by radio value is applied. EIRP: Displays the current EIRP that a radio antenna radiates (after applying the TPC). Power: Displays the current transmit power radiated by the radio (after applying the TPC). Click Refresh to view updated link statistics. To view detailed SU/End Point B Link statistics, click Details icon following screen appears depending on your device:
in the SU/End Point B Link Statistics screen. The Tsunami 800 & 8000 Series - Software Management Guide 236 Monitor Figure 7-14 An Example - SU Detailed Statistics The detailed page displays Remote SNR information, that is, the Minimum Required SNR and the Maximum Optimal SNR value for a given data rate or modulation, to achieve optimal throughput. To disconnect an SU/End Point B from BSU/End Point A respectively, click Disconnect. To view updated detailed statistics, click Refresh. To view local SNR table, click Click here for Local SNR-Table on the upper-right of SU/End Point B Link Statistics screen Tsunami 800 & 8000 Series - Software Management Guide
(Refer
G
J
K L
). The following screen appears depending on your device:
237 Monitor These configured values are used by ATPC and DDRS to derive TPC and data rate for optimal throughput. Figure 7-15 An Example - Local SNR Information 7.3.2.2 BSU/End Point A Link Statistics
: BSU Link Statistics is applicable only to an SU, and End Point A Link Statistics is applicable only to an End Point B device. BSU Link statistics provides information about the BSU to which SUs are connected. Similarly, End Point A Link Statistics provides information about an End Point A currently linked to an End Point B device. Tsunami 800 & 8000 Series - Software Management Guide 238 Monitor Figure 7-16 An Example - BSU Link Statistics (For 82x Devices) Figure 7-17 An Example - BSU Link Statistics (For All Devices) To access the Radio Link Test Tool, navigate to MONITOR > WORP Statistics > Interface 1 > SU/BSU Link Statistics >
Details. Click
. The SU/BSU WORP Detailed Statistics screen appears. In this screen, click the Radio Link Test button. 7.3.3 QoS Statistics (BSU or End Point A Only) For detailed description of this tool, refer
: This parameter is applicable only to BSU or End Point A radio modes. To view QoS Statistics, navigate to MONITOR > WORP Statistics > Interface 1 > QoS Statistics. The following QoS Summary screen appears. Tsunami 800 & 8000 Series - Software Management Guide 239 Monitor This screen shows the total, minimum and maximum bandwidth allocated per BSU/End Point A, and the minimum and maximum bandwidth allocated for each SU/End Point B registered with the BSU/End Point A respectively. Figure 7-18 QoS Summary 7.4 Active VLAN
: Active VLAN is applicable only to a device in SU (Bridge) mode. The Active VLAN page enables you to identify the VLAN Configuration mode applied on a device in SU mode. To view active VLAN applied on the device in SU mode, navigate to MONITOR > Active VLAN. The Active VLAN page appears:
The Active VLAN Config parameter helps you to identify the current VLAN configuration applied on the device in SU mode. Figure 7-19 Active VLAN Local: VLAN configuration is done locally from the device. Remote: VLAN configuration is done through RADIUS Server. Tsunami 800 & 8000 Series - Software Management Guide 240 This page also displays the VLAN parameters and their values that are configured either locally or remotely. To view active VLAN Ethernet Configuration, navigate to MONITOR > Active VLAN > Ethernet. The Active VLAN Ethernet Configuration page appears:
Monitor This page displays the VLAN Ethernet parameters and their values that are configured either locally or remotely. Figure 7-20 Active VLAN Ethernet Configuration
: Please note that the number of Ethernets vary depending on the device. 7.5 Bridge 7.5.1 Bridge Statistics The Bridge Statistics allows you to monitor the statistics of the Bridge. To view the Bridge Statistics, navigate to MONITOR > Bridge > Bridge Statistics. The following Bridge Statistics screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 241 Monitor Figure 7-21 Bridge Statistics Description Parameter The following table lists the parameters and their descriptionM Operational Status MAC Address MTU This parameter provides a description about the bridge. Represents the largest size of the data packet sent on the bridge. Represents the MAC address at the bridge protocol layer. Description Represents the current operational status of the bridge: UP (ready to pass packets) or DOWN (not ready to pass packets). In Octets Represents the total number of octets received on the bridge interface, including the framing characters. In Unicast Packets Represents the number of unicast subnetwork packets delivered to the higher level protocol. In Non-unicast Packets Represents the number of non-unicast subnetwork packets delivered to the higher level protocol. In Errors Out Octets Out Packets Out Discards Represents the number of inbound packets with errors and that are restricted from being delivered. Represents the total number of octets transmitted out of the bridge, including the framing characters. Represents the total number of packets requested by higher-level protocols to be transmitted out of the bridge interface to a sub-network address, including those that were discarded or not sent. Represents the number of error-free outbound packets which are discarded to prevent them from being transmitted. One possible reason for discarding such a packet could be to free up buffer space. Tsunami 800 & 8000 Series - Software Management Guide 242 Monitor Parameter Out Errors Represents the number of outbound packets that could not be transmitted because of errors. Description To view updated Bridge statistics, click Refresh. To clear the Bridge statistics, click Clear. 7.5.2 Learn Table Learn Table allows you to view all the MAC addresses that the device has learnt on all of its interfaces. To view Learn Table statistics, navigate to MONITOR > Bridge > Learn Table. The Learn Table screen appears. The Learn Table displays the MAC address of the learnt device, the bridge port number, aging timer for each device learnt on an interface, and the local (DUT's local interfaces)/remote (learned entries through bridging) status of the learnt device. Figure 7-22 Learn Table To view updated learn table statistics, click Refresh. To clear learn table statistics, click Clear. 7.6 Network Layer 7.6.1 Routing Table Routing table displays all the active routes of the network. These can be either static or dynamic (obtained through RIP). For every route created in the network, the details of that particular link or route will get updated in this table. To view the Routing Table, navigate to MONITOR > Network Layer > Routing Table. The Routing Table screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 243 Monitor 7.6.2 IP ARP Figure 7-23 Routing Table Address Resolution Protocol (ARP) is a protocol for mapping an Internet Protocol address (IP address) to a physical address on the network. The IP ARP table is used to maintain a correlation between each IP address and its corresponding MAC address. ARP provides the protocol rules for making this correlation and providing address conversion in both directions. To view IP Address Resolution Protocol (ARP) statistics, navigate to MONITOR > Network Layer > IP ARP. The IP ARP Table screen appears. The IP ARP Table contains the following information:
Figure 7-24 IP ARP Table Net Address: This parameter represents the corresponding IP address of a node on the network. Type: This parameter represents the type of mapping, that is, Dynamic or Static. To view updated IP ARP entries, click Refresh. Index: Represents the interface type. MAC Address: Represents the MAC address of a node on the network. To clear the IP ARP entries, click Clear. Tsunami 800 & 8000 Series - Software Management Guide 244 7.6.3 ICMP Statistics The ICMP Statistics attributes enable you to monitor the message traffic that is received and transmitted by the device. To view ICMP statistics, navigate to MONITOR > Network Layer > ICMP Statistics. The ICMP Statistics screen appears. Monitor Figure 7-25 ICMP Statistics Parameter In Msgs or Out Msgs The following table lists the ICMP Statistics parameters and their descriptionM In Errors or Out Errors In Dest Unreachs or Out Dest Unreachs Description Represents the number of ICMP messages that are received/transmitted by the device. Represents the number of ICMP messages that are received/transmitted by the device but determined as having ICMP-specific errors such as Bad ICMP checksums, bad length and so on. Represents the number of ICMP destination unreachable messages that are received/transmitted by the device. In Time Excds or Out Time Excds Represents the number of ICMP time exceeded messages that are received/transmitted by the device. In Parm Probs or Out Parm Probs Represents the number of ICMP parameter problem messages that are received/transmitted by the device. In Srec Quenchs or Out Srec Quenchs Represents the number of ICMP source quench messages that are received/transmitted by the device. In Redirects or Out Redirects Represents the rate at which the ICMP redirect messages are received/transmitted by the device. In Echos Represents the rate at which the ICMP echo messages are received. In EchoReps or Out EchoReps Represents the rate at which the ICMP echo reply messages are received/transmitted by the device. Tsunami 800 & 8000 Series - Software Management Guide 245 Monitor Parameter Description In Timestamps or Out Timestamps Represents the rate at which the ICMP timestamp (request) messages are received/transmitted by the device. In Timestamps Reps or Out Timestamps Reps Represents the rate at which the ICMP timestamp reply messages are received/transmitted by the device. In Addr Masks or Out Addr Masks Represents the number of ICMP address mask request messages that are received/transmitted by the device. In Addr Mask Reps or Out Addr Mask Reps Represents the number of ICMP address mask reply messages that are received/transmitted by the device. To view updated ICMP Statistics, click Refresh. 7.6.4 IP Address Table The IP Address Table shows all IP addresses of the device. The IP Address Table screen contains IP addresses of the interface. To view table, navigate to MONITOR > Network Layer > IP Address Table. The IP Address Table screen appears. Figure 7-26 IP Address Table 7.6.5 DNS Addresses It shows DNS Addresses currently active on the device. To view DNS addresses, navigate to MONITOR > Network Layer >
DNS Addresses. The DNS Addresses screen appears. Tsunami 800 & 8000 Series - Software Management Guide 246 Figure 7-27 DNS Addresses 7.6.6 Neighbour Table
: This parameter is applicable only in IPv4 and IPv6 mode, not in IPv4 only mode. The Neighbour Table contains a list of neighbouring routers and information about them. To view Neighbour Table, navigate to MONITOR > Network Layer > Neighbour Table. The Neighbour table screen appears. Monitor Figure 7-28 Neighbour Table 7.6.7 RIP Database
: Applicable only in routing mode. The RIP Database screen contains routes (Routing Information Protocol updates) learnt from other routers. Tsunami 800 & 8000 Series - Software Management Guide 247 Figure 7-29 RIP Database Monitor 7.7 RADIUS (BSU or End Point A only)
: RADIUS is applicable only to a BSU or an End Point A device. 7.7.1 Authentication Statistics Authentication Statistics provides information on RADIUS Authentication for both the primary and backup servers for each RADIUS server profile. To view Authentication statistics, navigate to MONITOR > RADIUS > Authentication Statistics. The RADIUS Client Authentication Statistics screen appears:
Figure 7-30 Radius Client Authentication Statistics Parameter Round Trip Time The following table lists the Authentication Statistics parameters and their descriptionM Description RTMS Reqs Represents the number of RADIUS access request messages transmitted from the RADIUS client to the authentication server since client startup. This parameter represents the number of times the RADIUS access requests are being transmitted to the server from the device since the client startup. Represents the round trip time for messages exchanged between RADIUS client and authentication server since the client startup. Accepts Rejects Resp Mal Resp Bad Auths Time Outs Represents the number of RADIUS access accept messages received by the device since client startup. Represents the number of RADIUS access reject messages received by the device since client startup. Represents the number of RADIUS response packets received by the device since client startup. Represents the number of malformed RADIUS access response messages received by the device since client startup. Represents the number of malformed RADIUS access response messages containing invalid authenticators received by the device since client startup. Represents the total number of timeouts for RADIUS access request messages since client startup. Tsunami 800 & 8000 Series - Software Management Guide 248 Parameter UnKnown Types This parameter specifies the number of messages with unknown RADIUS message code since client startup. Description Packets Dropped Represents the number of RADIUS packets dropped by the device. To view updated RADIUS Client Authentication statistics, click Refresh. Monitor 7.8 IGMP
: Applicable in Bridge mode only. To view IGMP statistics, navigate to MONITOR > IGMP > IGMP Snooping Stats. The Ethernet or Wireless Multicast List screen appears:
Figure 7-31 Ethernet1 Multicast List 7.8.1 Ethernet or Wireless Multicast List The Multicast List table contains the IGMP Multicast IP and Multicast MAC address details for the Ethernet or Wireless interfaces. The following table lists the parameters and their description. Parameter Group IP MAC Address Time Elapsed Description Represents the IP address of the multicast group for Ethernet or Wireless interface learned by IGMP snooping. Represents the MAC address of the multicast group for Ethernet or Wireless interface learned by IGMP snooping. Represents the time elapsed since the multicast entry has been created for the Ethernet or Wireless interface. To view updated IGMP statistics, click Refresh. 7.8.2 Router Port List The Router Port List displays the list of ports on which multicast routers are attached. To view Router Port List, navigate to MONITOR > IGMP > Router Port List. The Router Port List screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 249 Monitor Figure 7-32 Router Port List The following table lists the parameters and their description. Parameter Port Number Represents the port number on which multicast router is attached (on which IGMP Query has been received). Description Time Elapsed Represents the time elapsed since the port is marked as the router port. To view updated Router Port list, click Refresh. 7.9 DHCP DHCP Leases file stores the DHCP client database that the DHCP Server has served. The information stored includes the duration of the lease, for which the IP address has been assigned, the start and end dates for the lease, and the MAC address of the network interface card of the DHCP client. To view DHCP Leases, navigate to MONITOR > DHCP > Leases. Figure 7-33 DHCP Leases Tsunami 800 & 8000 Series - Software Management Guide 250 Monitor 7.10 Logs 7.10.1 Event Log Event Log file keeps track of events that occur during the operation of the device. It displays the event occurring time, event type, and the name of the error or the error message. Based on the priority (the log priority is set under MANAGEMENT >
Services > Logs), the event details are logged and can be used for any future reference or troubleshooting. 7.10.1.1 View Event Log To view the event log messages, navigate to MONITOR > Logs > Event Log. The following Event Log screen appears:
Figure 7-34 Event Log Messages The maximum size of the event log file is 65 KB. If the file size exceeds 65 KB, then all the log messages are moved to a backup file and only the recent 100 lines are displayed in the log file. When the size of the log file exceeds again then it overwrites the backup file. Backup files can be retrieved by using retrieve CLI command. For more details, see Tsunami 800 and 8000 Series To retrieve the event log file from the device, see N Reference guide available at Y U X
V R _ U Q Z
V
Z P P V 7.10.1.2 Hide Event Log To hide the event log messages, click Hide Event Log. O P
. Q R O S O T Q U V W O S R X O .
: Log messages can be stored in the log file approximately up to 6 days with logging interval of 5 minutes. Tsunami 800 & 8000 Series - Software Management Guide 251 Monitor 7.10.1.3 Clear Event Log To clear the event log messages, click Clear Event Log. The messages are cleared and moved to the backup file leaving the event log file empty. An event is generated on clearing the event log messages.
: The current and the backed up event logs are stored in the flash memory and can be retrieved even after device reboot. 7.10.2 Debug Log Debug Log helps you to debug issues related to important features of the device. Currently, this feature supports only DDRS and DFS. This feature helps the engineering team to get valuable information from the field to analyze the issues and provide faster solution. This feature should be used only in consultation with the Proxim Customer Support team. Once logging is enabled, the Debug Log file can be retrieved via HTTP or TFTP. To enable Debug Log, navigate to MONITOR > Logs > Debug Log. The Debug Log screen appears:
Features: Select the appropriate features to be logged. The available features are Select All, DDRS Level 1, DDRS Level 2, DDRS Level 3 and DFS. Figure 7-35 Debug Log File Status: This parameter displays the current size of the Debug Log file. After selecting the DDRS level, click OK. To delete the Debug Log, click Clear Log. To get the updated status of the Debug Log File, Click Refresh. 7.10.3 Temperature Log
: Temperature Log is not applicable to MP-8150-CPE, MP-8160-CPE, MP-825-CPE-50, MP-820-BSU-100, MP-820-SUA-50+, MP-825-SUR-50+, QB-825-EPR/LNK-50, QB-825-EPR/LNK-50+ and QB-8150-LNK-12/50 devices. Temperature Log feature is used to log the internal temperature of the device for the configured temperature logging interval
(By default, it is 5 minutes). It also generates a trap and an event message when the internal temperature of the device Tsunami 800 & 8000 Series - Software Management Guide 252 reaches or exceeds the configured threshold range. The device issues a warning trap when the temperature is 5 Celsius less than the configured threshold range. To access this feature, navigate to MONITOR > Logs > Temperature Log. The following Temperature screen appears:
Monitor Figure 7-36 Temperature Log Current Unit Temperature: Displays the current internal temperature of the device in Celsius. High and Low Temperature Threshold:
Configure the high temperature threshold ranging from -40C to 60C. By default, it is set to 60C. Configure the low temperature threshold ranging from -40C to 60C. By default, it is set to -40C. When the current internal temperature of the device reaches or exceeds this threshold range, then a trap and event message is generated for every one hour (as long as it stays in the same state). If the temperature of the device further changes, then the device will immediately generates another trap and an event message. For example, lets say the configured threshold range is -30(low) to 40 (high). If the device temperature reaches 50 then a trap and event message is generated for every one hour till it remains at 50. So, when the temperature increases to 51 then it will immediately generate another trap and an event message. Temperature Logging Interval: A logging interval from 1 to 60 minutes with 5 minute increment can be selected. For example, if you configure logging interval as 10 minutes then the device temperature is logged for every 10 minutes.
: If the logging interval is configured 0, then the temperature log feature will be disabled. After configuring the parameters, click OK followed by COMMIT.
Tsunami 800 & 8000 Series - Software Management Guide 253 7.10.3.1 View Temperature Log To view the temperature Log, click Show Temp Log. Monitor Figure 7-37 View Temperature Log The maximum size of the temperature log file is 65 KB. If the file size exceeds 65 KB, then all the log messages are moved to a backup file and only the recent 100 lines are displayed in the log file. When the size of the log file exceeds again then it overwrites the backup file. Backup files can be retrieved by using retrieve CLI command. For more details, see Tsunami 800 and 8000 Series To retrieve the temperature log file from the device, see N Reference guide available at Y V U X
V R _ U Q
. V Z Z
P P
O P Q R O S O T Q U V W O S R X O .
: Log messages can be stored in the log file approximately up to 6 days with logging interval of 5 minutes. Tsunami 800 & 8000 Series - Software Management Guide 254 Monitor 7.10.3.2 Hide Temperature Log To hide the temperature log messages, click Hide Temp Log. 7.10.3.3 Clear Temperature Log To clear the temperature log messages, click Clear Temp Log. The messages are cleared and moved to the backup file leaving the temperature log file empty. An event is generated on clearing the temperature log messages.
: The current and the backed up temperature logs are stored in the flash memory and can be retrieved even after device reboot. 7.11 Tools 7.11.1 Wireless Site Survey
: Applicable only to a device in SU or End Point B mode. Wireless Site Survey is done by the SU or End Point B only. This feature scans all the available channels according to the current Channel Bandwidth, and collects information about all BSUs or Endpoint A configured with the same network name as SUs or End Point B. Figure 7-38 Wireless Site Survey - SU Mode To initialize the survey process, click Start. This process list the details of all the available BSUs or End Point A. To stop the site survey process, click Stop. During the scan process, click Refresh to view the latest discovered BSU/End Point A.
: Site Survey cannot be performed, when Roaming is enabled. Tsunami 800 & 8000 Series - Software Management Guide 255 7.11.2 Scan Tool With Scan Tool, you can scan all the Proxim devices available on the network. To scan the devices, navigate to MONITOR > Tools > Scan Tool. The Scan Tool screen appears. In the Scan Tool screen, select Scan Mode as IPv4. Click Scan to scan and refresh the devices on the network. The scanned devices are displayed as shown below:
Monitor Figure 7-39 An Example - Scanned Devices (IPv4) In the Scan Tool screen, select Scan Mode as IPv6 to scan the 82x devices with IPv6 mode. Click Scan to scan and refresh the devices on the network. The scanned 82x devices are displayed as shown below:
Figure 7-40 An Example - Scanned Devices (IPv6)
: ScanTool IPv6 support is applicable only for the 82x devices with IPv6 mode. 7.11.3 sFlow Proxims point-to-multipoint and point-to-point devices support sFlow technology, developed by InMon Corporation. The sFlow technology provides the ability to measure network traffic on all interfaces simultaneously by collecting, storing, and analyzing traffic data. Depicted below is the sFlow architecture that consists of a sFlow Agent and a sFlow Receiver. Tsunami 800 & 8000 Series - Software Management Guide 256 Monitor Figure 7-41 sFlow Architecture - An Example with a BSU and SUs The sFlow Agent, which is running on devices, captures traffic information received on all the Ethernet interfaces, and sends sampled packets to the sFlow Receiver for analysis. The sampling mechanism used to sample data are as follows:
Packet Flow Sampling: In this sampling, the data packets received on the Ethernet interface of the device are sampled based on a counter. With each packet received, the counter is decremented. When the counter reaches zero, the packet is packaged and sent to the sFlow Receiver for analysis. These packets are referred to as Packet Flow Samples. Counter Polling Sampling: In this sampling, the sFlow Agent sends counters periodically to the sFlow Receiver based on the set polling interval. If polling interval is set to 5 seconds then the sFlow Agent sends counters to sFlow Receiver every 5 seconds. These packets are referred to as Counter Polling Samples. The Packet Flow Samples and Counter Polling Samples are collectively sent to the sFlow Receiver as sFlow Datagrams. It is possible to enable either or both types of sampling. sFlow Sampling effects the system performance and hence care must be taken in configuring the sFlow parameters. To configure sFlow, navigate to MONITOR > Tools > sFlow. The following sFlow screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 257 Monitor This screen displays the following information about the sFlow Agent:
Figure 7-42 sFLOW Version: The version displayed is 1.3;Proxim Wireless Corp.; v6.4. The version comprises the following information:
1. sFlow MIB Version: Indicates the agents MIB version. The MIB specifies how the agent extracts and bundles sampled data, and the sFlow receiver must support the agents MIB. The sFlow MIB version is 1.3. so the sFlow Receivers version must also be at least 1.3. 2. Organization: Specifies the organization implementing sFlow Agent functionality on the device, that is, Proxim Wireless Corp. 3. Revision: Specifies the sFlow Agent version, that is, v6.4. Address Type: Specifies the protocol version for IP addresses. Agent Address: Specifies the sFlow Agents IP address. 7.11.3.1 sFlow Receiver Configuration The Receiver Configuration page allows you to configure sFlow Receiver(s), which receives samples from all agents on the network, combines and analyzes the samples to produce a report of network activity. To configure sFlow Receiver, navigate to MONITOR > Tools > sFlow and select Receiver Configuration tab. Given below is the table which explains sFlow parameters and the method to configure the configurable parameter(s):
Parameter Description S.No. Owner Represents the Receiver index number. Please note that the number of indexes depends on the Ethernet interfaces your device supports. Enter a string, which uniquely identifies the sFlow Receiver. Tsunami 800 & 8000 Series - Software Management Guide 258
Monitor Parameter Description Time Out Enter a value ranging from 30 to 31536000 seconds (365 days) in the Time Out box. The sFlow Agent sends sampled packets to the specified sFlow Receiver till it reaches zero. At zero, all the Receiver parameters are set to default values. Max Datagram Size Enter the maximum size of a sFlow datagram (in bytes), which the Receiver can receive, in the Max Datagram Size box. By default, the maximum datagram size is set to 1400 bytes. It can range from 200 to 1400 bytes. Address Type The address type supported by sFlow Receiver is ipv4, which is by default selected.
: Only IPv4 is currently supported. Receiver Address Enter the sFlow Receivers IP address in the Receiver Address box. Receiver Port By default, the sFlow Receiver listens to the sFlow datagrams on 6343 port. To change the port, enter a valid port ranging from 0 to 65535 in the Receiver Port box. Datagram Version The sFlow datagram version used is 5. Click Apply, to save the sFlow Receiver configuration parameters. Once the Receiver configurations are done, either Packet Flow sampling or Counter Polling Sampling or both can be started.
7.11.3.2 Sampling Configuration Timeout and Max Datagram Size.
` Enabling sampling effects the system performance and hence care should be taken in setting the right values for
` When the Owner string is cleared, the Flow Sampling and Counter Polling stops. 1. Navigate to MONITOR > Tools > sFlow and select Sampling Configuration tab. To configure and start packet flow sampling, do the following:
Tsunami 800 & 8000 Series - Software Management Guide 259 Monitor Figure 7-43 sFlow Sampling Configuration 2. From the Receiver Index drop-down box, select the receiver index number associated with the sFlow Receiver to which the sFlow Agent should send the sFlow Datagrams.
: If device has two Ethernet interfaces, then configure different Receiver indexes for each of the interface. 3. Type a value in the Packet Sampling Rate box. This value determines the number of packets the sFlow Agent samples from the total number of packets passing through the Ethernet interface of the device. 4. Type a value in the Maximum Header Size box, to set the amount of data (in bytes) to be included in the sFlow datagram. The sFlow Agent samples the specified number of bytes. For example, if you set the Maximum Header Size to 100, the sFlow Agent places the first 100 bytes of every sampled frame in the datagram. The value should match the size of the frame and packet header so that the entire header is forwarded. The default size is 128 bytes. The header size can range from 20 to 256 bytes.
Sampling values are set to default values. right value for Packet Sampling Rate and Maximum Header Size. 5. Next, click Apply to start packet flow sampling. Once it starts, the Time Out parameter (see a T b U c N O X O R S O Q d e ) keeps decrementing till it reaches a zero value. On reaching zero, the corresponding Receiver and U e f R g h Q i P R U
` Enabling sFlow packet sampling effects the system performance, and hence care must be taken when choosing the
` Receiver Index for packet Sampling table and Counter Polling table should be same for each Ethernet interface. 1. Navigate to MONITOR > Tools > sFlow and select Counter Polling Configuration tab. 260 To configure and start Counter Polling sampling, do the following:
7.11.3.3 Counter Polling Configuration Tsunami 800 & 8000 Series - Software Management Guide Monitor Figure 7-44 Counter Polling Configuration 2. From the Receiver Index drop-down box, choose the receiver index number associated with the sFlow Receiver to which the sFlow Agent sends the counters.
: If Packet Flow Sampling is already configured and running, then you should configure the Receiver index same as configured in the Packet Flow Sampling for each Ethernet interface. 3. Set the polling interval by typing a value in the Interval box. Lets say, the polling interval is set to 30 seconds. So for every 30 seconds, the counters are collected and send to the sFlow Receiver. The valid range for polling interval is 0 to 231 - 1 seconds. right value sampling interval. Counter Polling values are set to default values. 4. Next, click Apply to start Counter Polling Sampling. Once it starts, the Time Out parameter (see a T b U c N O X O R S O Q d e ) keeps decrementing till it reaches a zero value. On reaching zero, the corresponding Receiver and U e f R g h Q i P R U
` Enabling sFlow counter sampling effects the system performance, and hence care must be taken when choosing the
` Receiver Index for packet Sampling table and Counter Polling table should be same for each Ethernet interface.
If a sampling starts and there is already another sampling running then we consider the time out value of the current/already running sampling. The Console Commands feature helps Proxims Technical Support team to debug field issues. 7.11.4 Console Commands Tsunami 800 & 8000 Series - Software Management Guide 261 Monitor 7.11.5 Spectrum Analyzer
: Spectrum Analyzer is not applicable to MP-8150-CPE and QB-8150-LNK-12/50 devices. Spectrum Analyzer helps to analyze a spectrum for interference, and select a relatively low interference channel. This tool is not a replacement for the commercial Spectrum Analyzers as this is only intended to help with channel selection and diagnose performance issues.
: Only an administrator user can use Spectrum Analyzer to scan the spectrum. However, the Monitor user can view the last scanned results. To scan all the channels in the configured frequency domain, do the following:
1. Navigate to MONITOR > Tools > Spectrum Analyzer. The following Spectrum Analyzer screen appears:
Figure 7-45 An Example - Spectrum Analyzer 2. Channel Scan Time: Enter the time (ranging from 100 to 60000 milliseconds) to scan each channel. By default, the scan time is set to 1000 milliseconds. 3. Scan Iterations: Enter a number (ranging from 1 to 1000) which represents the number of times the scan iterates. By default, the scan iteration is set to 1. 4. After configuring the Channel Scan Time and Scan Iterations, click OK. Upon clicking OK, the Approximate Scan Duration parameter displays the total time (dd:hh:mm:ss) required to complete the scan. 5. Last Scanned Time: Represents the time at which the last spectrum scan was done. 6. Next click Start, to start the scan. Click Stop to stop the scan or wait for completion of the scan.
results captured at that particular instance. d d
` Spectrum Analyzer scan cannot be performed when W l is enabled. j W k e U R P X
e i V R X Y i e e
` The total duration of scan depends on the number of channels available, channel scan time and scan iterations.
` To reduce scan duration, configure the appropriate frequency filter lower and upper edges.
` While scanning, Spectrum Analyzer does not consider channel offset.
` The frequencies are scanned by 5MHz slice starting from the lower edge of the frequency filter, and displays the
` Spectrum Analyzer detects only 802.11 modulated signals. j O O O b b 262 Tsunami 800 & 8000 Series - Software Management Guide Monitor
(increase the Scan Time) to get accurate results.
` When working in a high interference network, ensure to run the spectrum analyzer with multiple iterations As the wireless link is down during spectrum analysis, the remote device cannot be accessed. Hence, if Spectrum Analyzer is started on a remote device, the results will not be available until spectrum scan is completed and wireless link gets re-established. When the Spectrum Analyzer starts, the wireless link, if established, is terminated and re-established after the scan is completed. 7. The scanned results are displayed in the form of a graph as follows:
` A minor variation in Spectrum Analyzer results can be expected due to the following reasons:
` Satellite Density Configuration
` A variation in the radio properties between various device models. Figure 7-46 An Example - Scanned Results Tsunami 800 & 8000 Series - Software Management Guide 263 Graph Results Interpretation Consider a network with a device operating on channel 122 with 20 MHz channel bandwidth. In the same vicinity, when we Monitor We recommend to avoid using these channels while installing Tsunami products, otherwise radio will report huge PHY and CRC errors. However, to make these channels usable and to ignore the low interference signals, we recommend configuring interfering signals on channels 115 to 129. It also shows strong interfering signal on channels 120 to124 indicating the presence of a device operating on channel 122, and moderate interfering signals on channels 115-119 and 125-129 (which are side band signals from the same interference source). on the devices. By default, for each channel, the graph represents the following statistics:
run the Spectrum Analyzer on a Tsunami radio it will display the results as shown in T P R a e O W O P R b b O P i j Maximum RSSI Minimum RSSI Description Parameter
Represents the maximum RSSI of all the signals received during the scan on a given channel. Represents the minimum RSSI of all the signals received during the scan on a given channel. Average RSSI Represents the average RSSI of all the signals received during the scan on a given channel. R g h Q O m n o p . From the results, we see Legend Activity Count Represents the total wireless activities (including OFDM Signal and Errors) during the scan on a given channel. Please note that the Current Iteration parameter helps to learn the current scan iteration. For example, if Scan Iteration is configured as 2, and currently only one scan cycle is complete then Current Iteration parameter displays 1. To view the statistics of a particular channel, point the cursor to that channel on the graph. The statistics is displayed as shown below:
It is also possible to view only the selected statistics on the graph. For example, to view only Minimum and Maximum RSSI on the graph, uncheck the box against Activity Count and Avg on the top of the graph. Figure 7-47 Channel Statistics Tsunami 800 & 8000 Series - Software Management Guide 264 Monitor Figure 7-48 An Example - Selective Graph Statistics At a time, the graph represents the statistics of a maximum of 32 channels. To view the graph(s) of the remaining channels, click Next (available on the upper right corner of the graph). Click Previous to view the statistics of the previous channels. To view the tabular format of the graph statistics, click Detailed Statistics on the bottom left of the graph. The detailed statistics is displayed as follows:
Figure 7-49 An Example - Detailed Statistics Tsunami 800 & 8000 Series - Software Management Guide 265 Monitor
: Spectrum Analyzer configuration parameters and results are not persistent across reboots. 7.11.6 Radio Link Test Tool In general, whenever the network has some performance issue, it is required to identify whether the issue is due to the wireless link or due to other network parameters. The Radio Link Test (RLT) tool helps to measure and diagnose any performance issues in the wireless link. At MAC level, this tool internally generates the traffic between the two radios, monitors the traffic, and generates a test report.The test report will help in analyzing the wireless link performance and other related issues such as interference, lower throughput, and wireless errors. Especially for the static link establishment, this is very helpful to check the link between the two radios when installing for the first time or if any performance issues are noticed after the installation. If the link between the radios is of expected quality, then there is no issue with the wireless link. In case, if there is any issue due to wireless parameters, the link may need some tuning in configuration such as channel, Data Rate, Tx power or distance between radios. In spite of all the testing and tuning, if the performance still fails to improve, then it may be due to installation related issues such as antenna alignment or the physical path. In the worst case, it may be a hardware related issue. It is applicable only to 82x devices. other tools like Iperf or any other commercial tools. It is recommended to use this tool with caution on live networks as it will be generating internal traffic which may impact the network performance.
` This is not a replacement for other wireless performance measuring tools and should be used in conjunction with
` Radio Link test is an experimental feature and will be improved in future releases.
` This tool can be accessed through web interface, console commands, and CLI.
` Both ends of a link cannot simultaneously run this test. Time duration for which the Radio Link Test is performed (Default: 60 seconds) Description Parameter The configuration options for the Radio Link Test tool are tabulated below:
Test Duration 7.11.6.1 Configuration Options Traffic Direction Traffic Rate Direction of the traffic (Downlink/Uplink /Bi-directional) Amount of traffic to be generated (K bps) Periodic Report Interval Time interval in which the report is presented to the user interface (seconds) Packet Size MAC Address Verbose Mode Help Version Generate packet size (Default value: 1500 bytes) Wireless MAC address of the device running in server mode Detailed statistics information List of possible options (Usage) Display tool version information Tsunami 800 & 8000 Series - Software Management Guide 266 Monitor To access this tool through web interface, navigate to MONITOR > WORP Statistics > Interface 1 > BSU/SU Link Statistics > Details. Click as shown in q e r _ i V Z b O n j s t R e u j P i P R a P R X a . The following BSU/SU WORP Detailed Statistics screen appears. Figure 7-50 An Example - SU Link Statistics Click the Radio Link Test Button. The following Radio Link Test screen appears. Figure 7-51 Radio Link Test Tool In the Radio Link Test screen, you can select the required type of traffic from the given options namely Uplink, Downlink, and Bidirection. By selecting Verbose along with any one of the traffic options, you can get a detailed test report for the traffic selected. In the above screen, for example, select Bidirection and Verbose. Next, click the START button. Tsunami 800 & 8000 Series - Software Management Guide 267 Monitor Figure 7-52 An Example - Radio Link Test (Bidirectional Traffic with Verbose mode) The test runs for 60 seconds and displays the Radio Link Test Report as shown below. Figure 7-53 An Example - Test Report (Bidirectional Traffic with Verbose mode) Tsunami 800 & 8000 Series - Software Management Guide 268 7.11.6.2 Statistics Options The test report can be analyzed by using the statistics options tabulated below:
Monitor Parameter Traffic Statistics Tx Packets Rx Packets Lost Packets Duplicated Packets Tx Rate Rx Rate Wireless Statistics Phy Errors CRC Errors Medium Busy WORP Statistics Send success Send failure Send retires Receive success Receive failures Receive retires Description Total packets transmitted from the moment user initiated the test. Total packets received from the moment user initiated the test. Packets lost due to any reason. Number of packets received in duplicate for the already received packets. The rate at which the packets are sent. The rate at which the packets are received. Total number of error packets received from the moment user initiated the test . The possible reasons:
It indicates the interference in the wireless medium Low signal level Number of packets received with invalid CRC. The possible reasons:
It indicates the interference in the wireless medium Low signal level Number of times the radio detected busy medium while trying to transmit the frame. This could be due to interference on that specific channel. Refers to the number of data messages sent and acknowledged by the peer successfully. Refers to the number of data messages that are not acknowledged by the peer even after the specified number of retransmissions. Refers to the number of data messages that are re-transmitted and acknowledged by the peer successfully. Refers to the number of data messages received and acknowledged successfully. Refers to the number of successfully received re-transmitted data messages. Refers to the number of data messages that were not received successfully.
Tsunami 800 & 8000 Series - Software Management Guide 269 Monitor Parameter Signal Statistics Signal Noise SNR Description Signal measured at the radio port Noise detected at the radio port Signal to Noise Ratio (dB) Using the rlt command options tabulated below, you run the radio link test tool through Web Console. Options Description
-t
-i
-s
-o Traffic Direction
-d
-u Test duration (Default: 60 seconds) Periodic report display interval (Default: 0 - disabled) Packet size (Default: 1500 bytes) Ignore timeout during test (Default: do not ignore) Downlink throughput test with specified traffic rate in K bps (Default: Unlimited) Uplink throughput test with specified traffic rate in K bps (Default: Unlimited) No option Default: Bi-Directional test with unlimited rate Miscellaneous
-h, --help Tool usage
-v, --version Tool version number
-V Verbose mode (Enables detailed statistics display)
w x
x
x
x
x
w
w x y z
x
x
v w x x y
z
Tsunami 800 & 8000 Series - Software Management Guide 270 To access this tool through Web Console, navigate to MONITOR > Tools > Console Commands. In the Web Console screen do the following:
Monitor Figure 7-54 An Example - Radio Link Test Through Web Console To run the Radio Link Test tool through Command Line Interface (CLI), refer the Tsunami 800 and 8000 Series Reference Guide. 7.12 SNMP v3 Statistics The command execution is displayed in the Web Console screen. Command: Type the required rlt command. Click the Execute button.
SNMP v3 statistics can be viewed only when SNMPv3 feature is enabled on the device. See j
. To view the SNMPv3 Statistics, navigate to MONITOR > SNMPV3 Statistics. The following SNMP v3 Statistics screen appears:
Tsunami 800 & 8000 Series - Software Management Guide 271 Monitor Figure 7-55 SNMP v3 Statistics Parameter Unsupported Sec Levels The following table lists the SNMP v3 parameters and their description Not In Time Windows Unknown User Names This parameter specifies the total number of packets dropped by the SNMP engine because they requested a security level that was unknown to the SNMP engine or otherwise unavailable. This parameter specifies the total number of packets dropped by the SNMP engine because they appeared outside the authoritative SNMP engine's window. This parameter specifies the total number of packets dropped by the SNMP engine because they correspond to a user that is unknown to an SNMP engine. Description Unknown Engine IDs This parameter specifies the total number of packets dropped by the SNMP engine because they correspond to an SNMP Engine ID that is unknown to an SNMP engine. Wrong Digests This parameter specifies the total number of packets dropped by the SNMP engine because they do not contain the expected digest value. Decryption Errors This parameter specifies the total number of packets dropped by the SNMP engine because they could not be decrypted. Tsunami 800 & 8000 Series - Software Management Guide 272 Troubleshooting 8 This chapter helps you to address the problems that might arise while using our device. If the procedures discussed in this chapter does not provide a solution, or the solution does not solve your problem, check our support site at which stores all resolved problems in its solution database. Alternatively, you can post a question on Before you start troubleshooting, check the details in the product documentation available on the support site. For details about RADIUS, TFTP, Terminal and Telnet programs, and Web Browsers, refer to their appropriate documentation. O X U S O Q
Q U X O h Q O a . R P
Q S X X U U V This chapter provides information on the following:
the support site, to a technical person who will reply to your email. Y P P Z
V
Z Q U _ R V In some cases, rebooting the device solves the problem. If nothing else helps, refer to N
U r e O d
U e e O X P
h U O g Q j
P j O h Z i q
P i R b Z Z X
O O Q R a b a
r k R Q O
a R Q O b O a
O N Q S U X O
V h Q P X O Z j
i b O X a R b j Q f O t h a l
d Y O O U Q h g a O g e Y u b U R X a a d U P q T e e t e O e e e e h O U U e e O U O O O O U e g h i U e h O Z O U h O Y U U e g h O e O e i O i i U e i O i i e U h O i O a a X a a a a a X X a a X
X a
a S X a k Q Q Q Q Q Q Q Q Q l R R P P P P f P P P f P P f P R R R R R R R R R b R R b R R b Tsunami 800 & 8000 Series - Software Management Guide 273 8.1 PoE Injector Problem The Device Does Not Work There is No Data Link Overload Indications Troubleshooting Solution Check the power plug and hub. Verify that the indicator on the device port is ON. Try to connect the device to a different PoE Injector hub. MP-825-CPE-50, QB-825-EPR/LNK-50, and QB-8150-LNK-12/50 Category 5/5e cable in case of MP-8150-CPE, MP-8160-CPE-A100, If the Ethernet link goes down, check the cable, cable type, switch and hub. Category 5e/6 cable in case of MP-8100-BSU, MP-8100-SUA, MP-8150-SUR, Category 5e/6 cable in case of MP-8100-BSU, MP-8100-SUA, MP-8150-SUR, Try using a different Ethernet cable if it works, there is probably a fault in the cable or its connection. Try a different port on the same PoE Injector hub (remember to move the input port accordingly) if it works then there is a problem in the previous RJ45 port or a bad RJ45 port connection. MP-8150-SUR-100, MP-8160-BSU, MP-8160-BS9, MP-8160-SUA, QB-8100-EPA/LNK, QB-8150-EPR/LNK, QB-8150-LNK-100, QB-8151-EPR/LNK, MP-8200-BSU, MP-8250-BS9, MP-8250-BS1, MP-8200-SUA, MP-820-BSU-100, MP-820-SUA-50+, MP-825-SUR-50+, QB-825-EPR/LNK-50+, and QB-8200-LNK devices Verify that the Ethernet cable from PoE Injector hub to the Ethernet port of the device is properly connected.
` Make sure that you are using a standard UTP
` Make sure that you are using a standard UTP
` Move the device into a different output port (remember to move the input port MP-8150-SUR-100, MP-8160-BSU, MP-8160-BS9, MP-8160-SUA, QB-8100-EPA/LNK, QB-8150-EPR/LNK, QB-8150-LNK-100, QB-8151-EPR/LNK, MP-8200-BSU, MP-8250-BS9, MP-8250-BS1, MP-8200-SUA, MP-820-BSU-100, MP-820-SUA-50+, MP-825-SUR-50+, QB-825-EPR/LNK-50+, and QB-8200-LNK devices Try to re-connect the cable to a different output port (remember to move the input port accordingly) if it works then there is a fault probably in the output or input port of the PoE Injector hub or a bad RJ45 connection. Try to connect a different device to the same port on the PoE Injector hub if it works and a link is established then there is probably a fault in the data link of the device. accordingly) - if it works then there is a fault probably in the previous RJ45 port or bad RJ45 port connection. The length of the cable from the Ethernet port of the device to the PoE should be less than 100 meters (approximately 325 feet). Category 5/5e cable in case of MP-8150-CPE, MP-8160-CPE-A100, Ensure that there is no short over on any of the connected cables. MP-825-CPE-50, QB-825-EPR/LNK-50, and QB-8150-LNK-12/50 Connect the device to a PoE Injector. Tsunami 800 & 8000 Series - Software Management Guide 274 8.2 Connectivity Issues Connectivity issues include any problem that prevents from powering or connecting to the device. Troubleshooting Problem Does Not Boot - No LED Activity Ethernet Link Does Not Work Serial Link Does Not Work Cannot Access the Web Interface Solution Check the Ethernet LED None;
support serial interface. configured to the following values:
Line Feeds with Carriage Returns Solid Green: The Ethernet link is up. Blinking Green: The Ethernet link is down. Double-check the physical network connections. Com Port: (COM1, COM2 and so on depending on your computer);
Baud rate: 115200; Data bits: 8; Stop bits: 1; Flow Control: None; Parity:
: Not applicable to MP-825-CPE-50, and MP-8160-CPE-A100 as it does not
(In HyperTerminal select: File > Properties > Settings > ASCII Setup > Send Line Ends with Line Feeds)
` Make sure the power source is ON.
` Make sure all the cables to the device are connected properly.
` Make sure your PC terminal program (such as HyperTerminal) is active and
` Open a command prompt window and type the Ping command along with the IP
address of the device. For example, ping 10.0.0.1. If the device does not respond, check if you have the correct IP address. If the device responds then it means the Ethernet connection is working properly. Ensure that you are not using a proxy server for the network connection with your Web browser. Ensure that you have not exceeded the maximum number of Web Interfaces or CLI sessions. Double-check the physical network connections. Use a well-known device to ensure the network connection is functioning properly. Ensure that you are using Microsoft Internet Explorer 7.0 (or later) or Mozilla Firefox 3.0 (or later).
: At any point of time, if the device is unable to connect to your network, reset Troubleshoot the network infrastructure (check switches, routers, and so on). the device by unplugging and plugging the cables from the PoE. Tsunami 800 & 8000 Series - Software Management Guide 275 8.3 Surge or Lightning Issues (For Connectorized devices) Troubleshooting Problem Surge or Lighting Problem In case of any lightning or surge occurrence, check for the conditions specified below:
Solution Check the RF signals by referring to RSSI statistics and if the signal strength has been lowered considerably, replace the Surge Arrestor. Unscrew the N-Type connector at the top and visually inspect the Surge Arrestor for electrical burns. If any, replace it. 8.4 Setup and Configuration Issues Problem Device Reboots Continuously Lost Telnet or SNMP Password Device Responds Slowly Incorrect Device IP Address Solution One of the reason for the device to reboot continuously is that the radio card is not properly placed in the mini-PCI slot. When you power on the device and you do not see the WIRELESS NETWORK1 PASSED in the POST message in the Serial Console,
. If the device takes a long time to respond, it could mean that:
parameters, but does not affect the image of the device. The default HTTP, Telnet, and SNMP username is admin and password is public. P P O procedure. This procedure resets system and network The IP address of the device is already in use. Verify that the IP address is assigned only to the device you are using. Do this by switching off the device and then pinging the IP address. If there is a response to the ping, another device in the network is using the same IP address. If the device uses a static IP address, switching to DHCP mode could solve this problem. V V V Z Z U U
_ X Q
R b The default IP address assignment mode is Static and the default IP address of the device is 169.254.128.132. If the IP address assignment mode is set to Dynamic, then the DHCP Server will assign an IP address automatically to the device. If the DHCP server is not available on your network, then the fall back IP address (169.254.128.132) of the device is used. Use ScanTool, to find the current IP address of the device. Once you have the current IP address, use Web Interface or CLI Interface to change the device IP settings, if necessary. If you are using static IP address assignment, and cannot access the device over R U i e U No DHCP server is available.
please contact Proxims support site at Y Perform P i Q O Z
Ethernet, refer to Perform Z O Q i P R U e The network traffic is more. R U e i e i P R R b R b q O Q O Y P g O procedure. This will reset the device to static mode. h e g t a a a R d Tsunami 800 & 8000 Series - Software Management Guide 276 Problem HTTP Interface or Telnet Does Not Work Telnet CLI Does Not Work TFTP Server Does Not Work Changes in Web Interface Do Not Take Effect Troubleshooting Solution
Broken Page icon Mozilla Firefox 3.0 or later Microsoft Internet Explorer 7.0 or later available on the right side of address bar. in the address bar of the browser, for example http://169.254.128.132. and Password. The default HTTP username is admin and password is public. Use CLI, to check the IP Access Table which can restrict access to Telnet and HTTP. Internet Options -> Security -> Internet -> Custom Level -> Scripting ->
Active Scripting to enable active scripting.
` Make sure you are using a compatible browser:
` When working with Internet Explorer 9 in Windows 2008 Server, navigate to
` When working with Internet Explorer 10 and facing web page issues, click the
` Make sure you have the correct IP address of the device. Enter the device IP address
` When the Enter Network Password window appears, enter the User Name and
` Make sure you have the correct IP address. Enter the device IP address in the Telnet
Use HTTP, to check the IP Access Table which can restrict access to Telnet and HTTP. connection dialog, from a DOS prompt: C:\> telnet <Device IP Address>
5. Wait until the device reboots before accessing the device again. Enable Telnet in Vista or Windows 7 as it is by default disabled. The TFTP server is not properly configured and running The upload or download directory is not correctly set 4. Click COMMIT for the changes to take effect. 2. Log on to the device again and make changes. The IP address of the TFTP server is invalid 1. Restart your Web browser. The file name is not correct 3. Reboot the device. Tsunami 800 & 8000 Series - Software Management Guide 277 Troubleshooting 8.5 Application Specific Troubleshooting Problem RADIUS Authentication Server Services unavailable Solution If RADIUS Authentication is enabled on the device, then make sure that your networks RADIUS servers are operational. Otherwise, clients will not be able to log on to the device. There are several reasons for the authentication servers services to be unavailable. To make it available, TFTP Server After the TFTP server is installed:
configured on the device. Check the RADIUS Authentication Servers Shared Secret and Destination Port number (default is 1812; for RADIUS Accounting, the default is 1813). If a TFTP server is not configured and running, you will not be able to download and upload images and configuration files to or from the device. Remember that the TFTP server need not be local, as long as you have a valid TFTP IP address. Note that you do not need a TFTP server running unless you want to transfer files to or from the device.
` Make sure you have the proper RADIUS authentication server information setup
` Make sure the RADIUS authentication server RAS setup matches the device.
` Make sure you have the proper TFTP server IP Address, the proper device image
` Make sure the TFTP server is configured to both Transmit and Receive files (on the TFTP servers Security tab), with no automatic shutdown or time-out (on the Auto Close tab). Check to see that TFTP is configured to point to the directory containing the device Image. file name, and that the TFTP server is connected. Tsunami 800 & 8000 Series - Software Management Guide 278 8.6 Wireless Link Issues Given below are the possible reasons for a wireless link not getting established and the relevant observations. Troubleshooting Reason(s) Mismatch in network name Incorrect or invalid configured BSU/End Point A name Mismatch in network secret Encryption set to No Encryption in BSU/End Point A and AES Encryption in SU/End Point B Encryption set to AES Encryption in BSU/End Point A and No Encryption in SU/End Point B Encryption set to AES Encryption in both BSU/End Point A and SU/End Point B. A mismatch in Encryption key BSU exceeds the maximum SU limit Observation The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented in BSU/End Point A and SU/End Point B. The WORP counters are not affected. The remote device is not listed in the Site Survey. The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented in SU/End Point B. The WORP counters are not affected. The remote device is not listed in the Site Survey. The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented in BSU/End Point A and SU/End Point B. The WORP counters are incremented (Req for Serv, Reg Req, Auth Req, Reg Attempts, Reg LastReason: Incorrect Parameter) on both ends. The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented in BSU/End Point A; No decrypt errors are observed in SU/End Point B. In SU/End Point B, the WORP counters (Announcements, Req for Serv, Reg Attempts, Reg incomplete, Reg timeout, Reg Last Reason: Timeout) are incremented. In BSU/End Point A, no WORP counters are incremented except announcements. The remote device is not listed in the Site Survey. The Wireless Statistics counters and WORP counters are not incremented in SU/End Point B. The remote device is not listed in the Site Survey. The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented only in SU/End Point B. The remote device is not listed in the Site Survey. The Wireless Interface Statistics (In Octets, In Non-Unicast Packets) are incremented in SU/End Point B but fails to authenticate. The WORP counters (Announcements, Req for Serv, Reg Attempts, Reg Incompletes, Reg Timeouts, Reg Last Reason: Timeout) are incremented in SU/End Point B. The remote device is listed in the Site Survey. Tsunami 800 & 8000 Series - Software Management Guide 279
Troubleshooting Reason(s) With multiple link profiles, the wireless network performance is getting affected. Observation The overall performance of the wireless network gets affected when using multiple link profiles and atleast one of the subscriber is operating with a lower data rate. For example, consider a wireless network with a BSU and 5 SU profiles. Each SU is transmitting data at a data rate as tabulated below. As SU1 is operating at a lower data rate (6.5 Mbps), the entire performance of the network gets affected. SU Profile(s) Data Rate Throughput SU1 SU2 SU3 SU4 SU5 6.5 Mbps 39 Mbps 78 Mbps 130 Mbps 78 Mbps Aggregated throughput can be a maximum of 13 Mbps In order to optimize the network performance, apply QoS. Given below is an example on how the network performance can be improved by applying QoS. QoS is applied for SU1 with the following configuration:
PIR based on the ToS value 96 SFC with MIR/CIR= 1Mbps; Priority = 3; Latency/Jitter=10ms Subscribers SU2...SU5 use the default QoS configuration.
Profiles Data Rate Throughput SU1 SU2 SU3 SU4 SU5 6.5 Mbps 39 Mbps 78 Mbps 130 Mbps 78 Mbps With QoS applied for SU1, expected throughput is 26 Mbps
: Given above is just an example and values might vary from case-to-case. Tsunami 800 & 8000 Series - Software Management Guide 280 Reason(s) Interference issues due to wider beam width of the antenna 8.7 Wired (Ethernet) Interface Validation Problem Wired (Ethernet) Interface Validation Troubleshooting Observation Run iperf commands Solution DFS bands DDRS operation at lower data rates SNR value fluctuations between the Antenna (A1/A2) ports Higher number of PHY errors which may result in false RADAR detection in To overcome these issues, use a spectrum analyzer and switch to a noise-free channel. QB-825-EPR/LNK-50+ uses a wider beam width antenna (up to 38 o) with a gain of 15dBi. Due to its wider beam width, it may pick up more interfering signals and may report large number of errors compared to other Tsunami products. Wireless interference may also lead to:
` MP-825-CPE-50, MP-825-SUR-50+, QB-825-EPR/LNK-50, and
` Make sure the connection established is of same speed and full duplex is as expected
` With auto negotiation, if you notice this issue, then try manually setting the speed
Use iperf commands with w option as 202k. The throughput is expected to be equal in both directions and should be comparable from laptop to laptop or desktop to desktop performance Check speed and duplex settings between the device and Personal Computer or switch or router connected Update the Ethernet driver in the Personal Computer to the latest one
(10 or 100 or 1000) and duplex If the above throughput value is not in the expected range, Tsunami 800 & 8000 Series - Software Management Guide 281 8.8 Wireless Interface Validation Troubleshooting Problem Wireless Interface Validation Run iperf commands (You can run Embedded iperf commands only through Telnet.) Solution If the expected throughput is not achieved, then check the following:
connectivity server is running P -> No of pairs (Streams) iperf s w 202k (command for iperf server) RF cables, used between antenna and device Use d option to run bidirectional throughput Select Single stream instead of Dual stream mode DDRS - with single stream data rate or with Auto mode Avoid nearby metal surfaces, if you are using Omni antenna If in RMA (Returned from Customer), check the RF cable to radio port Signal difference of <=5 dBm is considered as balanced and recommended If the chains are not balanced, then look at the alignment and connectors of Ipaddress -> of the SU/End Point B or BSU/End Point A device where the iperf Use r option to run unidirectional throughput one after another without changing the server and SU ends Note whether the antenna ports are balanced SNR/RSSI provided for Local and Remote in the BSU/SU Link Statistics page or by using aad command Iperf c ipaddress w 202k t time Period I <intermediateResultInterval> P <4 or 6> (command to run iperf client)
` Antenna Alignment
` Data Streams
` Antenna Port Selection
` Use Wi-Spy or similar tool and check the environment for better channel For devices with 3x3 MIMO radio, make sure you are either enabling all antenna ports for 3x3 MIMO or using A1 and A3 antenna ports for 2x2 MIMO mode Dual stream data rates can be used only when the signal in both antenna ports is balanced. Monitor Interface Statistics page. If this count increments steadily (Refreshing the web page is required) then Enabling all antenna port will not cause any issue even if it is not in use. Check for CRC errors, PHY errors, WORP Retries and WORP Failures in For using single stream, it is mandatory to select antenna port A1 For devices with 2x2 MIMO radio, use A1 and A2 antenna ports Either change the channel and check for a better channel Bad Channel Tsunami 800 & 8000 Series - Software Management Guide 282 Problem Wireless Interface Validation Troubleshooting Solution
` Data Rate Issues
Ensure same data rates are selected if you are using fixed data rate between BSU/SU and End Point A/End Point B to have predictable throughput and link Alternatively, use DDRS with Auto mode enabled Performance and Stability Issues Check the distance between two co-locating devices. The distance between two co-locating devices should be minimum 3 meters, in order to achieve good throughput and maintain link stability. The operating adjacent channel should maintain 5MHz spacing if managed by a single administrator. When DDRS is disabled, check the Minimum Required SNR for the current data rate by navigating to MONITOR --> WORP Statistics --> Interface 1
--> Link Statistics Page --> Click here for Local SNR-Table. If the current SNR is not meeting the minimum required SNR criteria for the current data rate, then accordingly reduce the data rate. If SNR is more than the maximum optimal SNR limit (MONITOR --> WORP Statistics --> Interface 1 --> Link Statistics Page --> Click here for Local SNR-Table) then it causes radio receiver saturation thus impacting the performance of the link. To overcome this situation, set the TPC appropriately or enable ATPC to adjust the signal level automatically. Also, enabling DDRS can help in choosing right data rate automatically. To measure and diagnose any performance issues in the wireless link, use the Radio Link Test Tool. To use this tool, navigate to MONITOR --> WORP Statistics --> Interface 1 --> Link Statistics Page --> Details -->Click 8.9 Recovery Procedures Recovery Procedure is used to restore the device to its factory default operating state. Depending on the device state, the recovery procedures can be classified under two modes:
icon. For detailed description of this tool, refer N i R U t R e u O a P U U b 1. Operational Mode: Device is up and in running state. 2. Bootloader Mode: Device operating image is deleted. Tsunami 800 & 8000 Series - Software Management Guide 283 Troubleshooting 8.9.1 Operational Mode S.No 1 Scenario Recovery Procedure Restore the device to its factory default configuration while accessing it through web interface In the web interface, navigate to MANAGEMENT > Reset to Factory. The Factory Reset screen appears:
In the screen, click OK. The device now reboots and comes with:
2 The device is not accessible for reasons such as user has forgotten the web interface login password, Management VLAN Id is changed, wrong VLAN configuration. Press and hold the Reload button (use a pin or the end of a paper clip) on the POE injector for a time frame as mentioned in the following table:
Device Timings 5 to 6 seconds IP Address: 169.254.128.132 Password: public
` Username: admin
MP-8100-BSU; MP-8100-SUA MP-8150-SUR; MP-8150-SUR-100 MP-8160-BSU; MP-8160-BS9 MP-8160-SUA; MP-8200-BSU MP-8250-BS9; MP-8250-BS1 MP-8200-SUA; MP-8250-SUR MP-825-CPE-50; MP-825-SUR-50+;
MP-820-BSU-100; MP-820-SUA-50+
QB-825-EPR/LNK-50+;
QB-825-EPR/LNK-50;
QB-8100-EPA/LNK; QB-8150-EPR/LNK QB-8150-LNK-100; QB-8151-EPR/LNK QB-8200-EPA / LNK; QB-8250-EPR / LNK MP-8150-CPE; MP-8160-CPE-A100;
QB-8150-LNK-12; QB-8150-LNK-50 15 seconds
To use this procedure, use a PoE injector with Reload functionality. The device operating image will get deleted, if you press the button for more than the above mentioned time. The timings mentioned above are valid from the time the device is powered UP (that is during POST). The device now reboots and comes with: IP Address: 169.254.128.132;
Username: admin; and Password: public
Tsunami 800 & 8000 Series - Software Management Guide 284 8.9.2 Bootloader Mode Troubleshooting S.No 1 Scenario Recovery Procedure a) The device operating image is corrupted for reasons such as power interruption while upgrading
(For 82x devices). b) The device operating image is corrupted for reasons such as power interruption while upgrading
(For all devices). 2 The device is not accessible for reasons such as user has forgotten the web interface login password, Management VLAN Id is changed, and wrong VLAN configuration. And, you do not have a reload capable PoE but Serial access is possible
Do one of the following:
No reload via Ethernet cross cable. It is not applicable to MP-825-CPE-50 and QB-825-EPR/LNK-50 devices. injector (use a pin or the end of a paper clip) for 15 seconds. By doing so, the operating image will get deleted. After powering-up the device, press and hold the Reload button on the PoE injector (use a pin or the end of a paper clip) for first 15 seconds and then release the button between 15-30 seconds. By doing so, the operating image will get deleted.
After deleting the operating image, refer s b and s P Y O j X i e U U a R e g P Y O d sections to load the firmware onto the device. U U P b U i O Q t
` While powering the device, press and hold the Reload button on the PoE
After deleting the operating image, refer s b and s O Y P g e R a U U e i X j O Y P d sections to load the firmware onto the device. U U P b U i O Q t If you are having serial access to the device during POST, press SHIFT+u to enter into forced user mode of the bootloader. From the Bootloader prompt, enter the command config_delete. If you are having serial access to the device during POST, press SHIFT+u to enter into forced user mode of the bootloader. From the Bootloader prompt, enter the command firmware_delete. Use a 4-pair (Gigabit) cross over Ethernet cable between the PoE and the device. By doing so, the reload functionality gets activated and forcibly deletes the operating image. The device now reboots and comes with: IP Address: 169.254.128.132;
Username: admin; and Password: public Next, issue the command reboot. e e g g a a R R 8.9.3 Load a New Image Follow one of the procedures below to load a new image to the device:
s s a a R R e e g g P P Y Y O O j X U i U e P U b U i U b O Q d t Tsunami 800 & 8000 Series - Software Management Guide 285 Troubleshooting
: A new image cannot be downloaded using Bootloader CLI onto MP-825-CPE-50, MP-8160-CPE-A100 and QB-825-EPR-50 as it does not provide a serial interface. 8.9.3.1 Using the ScanTool To download the firmware image to the device, you will need an Ethernet connection to the computer on which the TFTP server resides and to a computer that is running ScanTool (this is either two separate computers connected to the same network or a single computer running both programs). ScanTool automatically detects the device that does not have a valid software image. The TFTP Server and Image File Name screen so that you can download a new image to the device. (These fields Before starting the download process, you need to know the device IP Address, Subnet Mask, the TFTP Server IP Address, and the Image file name. Make sure the TFTP server is running and properly configured to point to the folder containing the image to be downloaded. Follow these steps to download a software image to the device by using ScanTool:
e R P R i b R i P R U e . Download Procedure Preparing to Download the Device Image parameters are enabled in the ScanTools are disabled, if ScanTool detects a software image on the device). See 1. Download the latest software from Y V U X
V R _ available when no image is installed on the device. 4. Set IP Address Type to Static. 2. Launch Proxims ScanTool.
V Z Z U
Q
P P
3. Highlight the entry for the device that you want to update and click Change.
: You need to assign static IP information temporarily to the device since its DHCP client functionality is not 5. Now enter the IP address, Subnet mask, Default-gateway, Server - IP address and the image filename. 6. Click OK. The device will reboot and the download starts automatically. 7. Click OK when prompted to return to the Scan List screen after the device has been updated successfully. 8. Click Cancel to close the ScanTool. After the download process is completed, the device will reboot and initialize. After successful initialization, the device is ready to be configured. 8.9.3.2 Using the Bootloader CLI To download the new device image, you will need an Ethernet connection to the computer on which the TFTP server resides. This can be any computer on the LAN or connected to the device with an Ethernet cable. You must also connect the device to a computer with a standard serial cable and use a terminal client. From the terminal, enter the CLI commands to set the IP address of the device and to download the device image. Preparing to Download the device image Before starting, you need to know the device IP Address, Subnet Mask, the TFTP Server IP Address, and the device image file name. Make sure the TFTP server is running and configured to point to the default directory containing the image to be downloaded. Tsunami 800 & 8000 Series - Software Management Guide 286
, and copy it to the default directory of the TFTP server. Troubleshooting
, and copy it to the default directory of the TFTP server. 2. Connect the device serial port to your computers serial port. 3. Open your terminal emulator program and set the following connection properties:
Com Port: COM1, COM2 and so on, depending on your computer 4. Under File > Properties > Settings > ASCII Setup, enable the Send line ends with line feeds option. Terminal Emulator program sends a line return at the end of each line of code. The terminal display shows Power On Self Tests (POST) activity. After approximately 30 seconds, a message indicates:
Starting ScanTool interface, press any key to enter CLI 5. After this message appears, press any key. Now the bootloader prompt appears as below:
Download Procedure Stop Bits: 1 Data Bits: 8 Baud Rate: 115200 Flow Control: None 1. Download the latest software from Y
5. Enter the following commands:
Parity: None P P Z
V
Z Q
U _ V R X U V 8.9.4.1 Hardware and Software Requirements Standard serial (RS-232) cable ASCII Terminal software
The device will reboot and then download the image file. When the download process is complete, configure the device. 8.9.4 Setting IP Address using Serial Port If the ScanTool fails to scan the device and users knows the login credentials then you can set the IP address for the device using serial port. Tsunami 800 & 8000 Series - Software Management Guide 287 Troubleshooting 8.9.4.2 Attach the Serial Port Cable 1. Connect one end of the serial cable to the device and the other end to a serial port on your computer. 2. Power on the computer and the device. 8.9.4.3 Initializing the IP Address using CLI After connecting the cable to the serial port, you can use the CLI to communicate with the device. CLI supports the most-generic terminal emulation programs. In addition, many web sites offer shareware or commercial terminal programs that you can download. Once the IP address has been assigned, you can use the HTTP interface or the Telnet to complete the configuration. Follow these steps to assign an IP address to the device:
1. Open your terminal emulation program and set the following connection properties:
Com Port: COM1, COM2, and so on depending on your computer Baud Rate: 115200 Data Bits: 8 Stop Bits: 1 Flow Control: None Parity: None The terminal display shows Power On Self Tests (POST) activity, and then displays the software version. It prompts you to enter the CLI username and password. The commands to enter the username and password are as follows:
This process may take up to 90 seconds. Subnet mask). 3. Change the IP address and other network values using the following CLI commands (use your own IP address and Tsunami 800 & 8000 Series - Software Management Guide 288 2. Enter the CLI Username and password. By default username is admin and password is public. The terminal displays a welcome message and then the CLI Prompt. Enter show ip as shown below:
Troubleshooting 4. After the device reboots, verify the new IP address by reconnecting to the CLI. Alternatively, you can ping the device from a network computer to confirm that the new IP address has taken effect. When a proper IP address is set, use HTTP interface or Telnet to configure the rest of the operating parameters of the device. 8.10 Spectrum Analyzer The ultimate way to discover whether there is a source of interference is to use a Spectrum Analyzer. Usually, the antenna is connected to the analyzer when measuring. By turning the antenna 360, one can check the direction of the interference. The analyzer will also display the frequencies and the level of signal is detected. Proxim recommends performing the test at various locations to find the most ideal location for the equipment. 8.10.1 Avoiding Interference When a source of interference is identified and when the level and frequencies are known, the next step is to avoid the interference. Some of the following actions can be tried:
Change the channel to a frequency that has no or least interference. Try changing the antenna polarization. A small beam antenna looks only in one particular direction. Because of the higher gain of such an antenna, lowering the output power or adding extra attenuation might be required to stay legal. This solution cannot help when the source of interference is right behind the remote site. Adjusting the antenna angle/height can help to reduce the interference. Move the antennas to a different location on the premises. This causes the devices to look from a different angle, causing a different pattern in the reception of the signals. Use obstructions such as buildings, when possible, to shield from the interference. 8.10.2 Conclusion A spectrum analyzer can be a great help to identify whether interference might be causing link problems on the device. Before checking for interference, the link should be verified by testing in an isolated environment, to make sure that the hardware works and your configurations are correct. The path analysis, cabling and antennas should be checked as well. Base Announces should increase continuously. Registration Requests and Authentication Requests should be divisible by 3. WORP is designed in a way that each registration sequence starts with 3 identical requests. It is not a problem if, once in a while, one of those requests is missing. Missing requests frequently is to be avoided. Tsunami 800 & 8000 Series - Software Management Guide 289
Troubleshooting same on both sides. This should be the case if output power is the same. Two different RSLs indicate a broken transmitter or receiver. A significant difference between Local Noise and Remote Noise could indicate a source of interference near the site with the highest noise. Normally, noise is about 80 dBm at 36 Mbps. This number can vary from situation to situation, of course, also in a healthy environment.
` Monitor / Per Station (Information per connected remote partner): Check that the received signal level (RSL) is the 8.11.1 Unable to Retrieve Event Logs through HTTPS 8.11 Miscellaneous If using Internet Explorer 7 and are not able to retrieve event logs through HTTPS, do the following:
1. Open Internet Explorer 2. Navigate to Tool > Internet Options > Advanced 3. Go to Security and uncheck/unselect Do not save encrypted pages to disk Alternatively, use Mozilla Firefox 3.5 or later. Tsunami 800 & 8000 Series - Software Management Guide 290 Feature Applicability Given below are the feature(s) applicable to the respective point-to-point devices:
Tsunami 800 & 8000 Series - Software Management Guide 291 Given below are the feature(s) applicable to the respective point-to-multipoint devices:
Feature Applicability Tsunami 800 & 8000 Series - Software Management Guide 292 Parameters Requiring Reboot Given below are the parameters that require the device to reboot. Parameter(s) Web Page(s) Applicable Device Mode*
System Configuration Radio Mode Frequency Domain BASIC CONFIGURATION ADVANCED CONFIGURATION -> System BASIC CONFIGURATION ADVANCED CONFIGURATION -> System Network Mode ADVANCED CONFIGURATION -> System Maximum MTU ADVANCED CONFIGURATION -> System ADVANCED CONFIGURATION -> System ADVANCED CONFIGURATION -> System IP Configuration (Bridge Mode) BASIC CONFIGURATION ADVANCED CONFIGURATION -> Network -> IP Configuration IP Configuration (Routing Mode) BASIC CONFIGURATION ADVANCED CONFIGURATION -> Network -> IP Configuration Frequency Filter Lower Edge Frequency Filter Upper Edge Ethernet Default Gateway IP Address DNS Ethernet Wireless Wireless (With PPPoE) Default Gateway IP Address DNS (Primary and Secondary Address) All All All All All All All All All All All SU Mode All All Status ADVANCED CONFIGURATION -> Network -> NAT SU Mode / End Mode B mode Dynamic Start Port ADVANCED CONFIGURATION -> Network -> NAT SU Mode / End Mode B mode Dynamic End Port ADVANCED CONFIGURATION -> Network -> NAT SU Mode / End Mode B mode NAT Status ADVANCED CONFIGURATION -> Network -> PPPoE Client SU Mode Admin Status ADVANCED CONFIGURATION -> Network -> Ethernet All Ethernet Interface Properties PPPoE Tsunami 800 & 8000 Series - Software Management Guide 293 Parameters Requiring Reboot Parameter(s) Web Page(s) Applicable Device Mode*
Channel Bandwidth BASIC CONFIGURATION ADVANCED CONFIGURATION -> Wireless -> Interface1 ->
Properties All Wireless Properties Channel Offset ADVANCED CONFIGURATION -> Wireless -> Properties Applicable only to, Auto Channel Selection Legacy Mode BASIC CONFIGURATION ADVANCED CONFIGURATION -> Wireless -> Interface1 ->
Properties BASIC CONFIGURATION ADVANCED CONFIGURATION -> Wireless -> Interface1 ->
Properties Applicable only to BSU. Applicable only to, MP-820-BSU-100 MP-820-SUA-50+
MP-825-SUR-50+
MP-825-CPE-50 MP-8150-CPE MP-8160-BSU MP-8160-BS9 MP-8160-SUA MP-8160-CPE-A100 QB-825-EPR/LNK-50 QB-825-EPR/LNK-50+
QB-8150-LNK-12/50 MP-820-BSU-100 MP-820-SUA-50+
MP-825-SUR-50+
MP-825-CPE-50 MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-CPE MP-8150-SUR-100 MP-8200-BSU MP-8200-SUA MP-8250-BS9 MP-8250-BS1 MP-8250-SUR Frequency Extension ADVANCED CONFIGURATION -> Wireless -> Interface1 ->
All Properties -> MIMO Properties -> MIMO Upgrade Firmware MANAGEMENT -> File Management -> Upgrade Firmware All Upgrade Firmware and Configuration Tsunami 800 & 8000 Series - Software Management Guide 294 Parameters Requiring Reboot Web Page(s) Applicable Device Mode*
MANAGEMENT -> File Management -> Upgrade Configuration All HTTP / HTTPS MANAGEMENT -> Services -> HTTP / HTTPS All All All All All Parameter(s) Upgrade Configuration Admin Password Monitor Password HTTP HTTP Port HTTPS Parameter(s) Web Page(s) Applicable Device Mode*
SNMP (If SNMP v1-v2c is enabled) SNMP Version Read Password Read / Write Password SNMP Trap Host Table SNMP Version Security Level Priv Protocol Priv Password Auth Protocol Auth Password SNMP Trap Host Table MANAGEMENT -> Services -> SNMP SNMP (If SNMP v3 is enabled) MANAGEMENT -> Services -> SNMP Telnet / SSH All All All All All All All All All All All All All Tsunami 800 & 8000 Series - Software Management Guide 295 Parameters Requiring Reboot Web Page(s) Applicable Device Mode*
Parameter(s) Admin Password Monitor Password Telnet Telnet Port Telnet Sessions SSH SSH Port SSH Sessions Access Table Status Management Access Control Table MANAGEMENT -> Services -> Telnet / SSH Management Access Control MANAGEMENT -> Access Control All All All All All All All All All All All Reset to Factory MANAGEMENT -> Reset to Factory Convert QB to MP MANAGEMENT -> Convert QB to MP Applicable only to
* BSU: Refers to a Base Station SU Mode: Refers to both SU and CPE End Point A Mode: Refers to a device in End Point A mode End Point B Mode: Refers to a device in End Point B mode QB-825-EPR/LNK-50 QB-825-EPR/LNK-50+
QB-8100-EPA/LNK QB-8150-EPR/LNK QB-8150-LNK-100 QB-8151-EPR/LNK QB-8200-LNK Tsunami 800 & 8000 Series - Software Management Guide 296 Frequency Domains and Channels Introduction The Tsunami point-to-point and point-to-multipoint products are available in two SKUs: United States (US) and rest of the World (WD) markets. Depending on the SKU, the device is hard programmed at factory per the regulatory domain. Regulatory domain controls the list of frequency domains that are available in that SKU. Further each frequency domain will define the country specific regulatory rules and frequency bands. The frequency domains can be easily configured using the Web Interface as it is a drop down list with all the available domains. The following table lists all the Tsunami 800 and 8000 Series products with the applicable frequency domains and their corresponding ENUM values, SKUs supported and licensed frequency bands. US Frequency Domains Point to Multipoint Devices Product(s) MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 MP-8150-CPE MP-8200-BSU / SUA MP-8250-BS9 / BS1 MP-8250-SUR MP-820-BSU-100 MP-820-SUA-50+
MP-825-CPE-50 MP-825-SUR-50+
Licensed Bands (in GHz) 2.4, 4.9, 5.0 5.0 5.0 4.9, 5.0 5.0 i s n a m o D y c n e u q e r F United States 5 GHz - US*
United States 5.8 GHz - US*
United States 2.4 GHz - US*
US2 (5.3 and 5.8GHz) - US*
United States 4.9 GHz l s e u a V M U N E 1 2 3 22 28 Point to Point Devices Product(s) QB-8100-EPA/LNK QB-8150-EPR QB-8150-LNK QB-8150-LNK-100 QB-8151-EPR/LNK QB-8150-LNK-12#
QB-8150-LNK-50 QB-8200-EPA/LNK QB-8250-EPR/LNK QB-825-EPR/LNK-50 QB-825-EPR/LNK-50+
US 2.4, 5.0 US 5.0 US 5.0 US 4.9, 5.0 US 5.0 Licensed Bands (in GHz) United States 5 GHz - US*
United States 5.8GHz - US*
United States 2.4 GHz - US*
US2 (5.3 and 5.8GHz) - US*
United States 4.9 GHz s n i a m o D y c n e u q e r F 1 2 3 22 28 s e u l a V M U N E Tsunami 800 & 8000 Series - Software Management Guide
297 World Frequency Domains Frequency Domains and Channels Product(s) MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-CPE MP-8150-SUR-100 Point to Multipoint Devices MP-8160-BSU MP-8160-BS9 MP-8160-SUA MP-8160-CPE MP-8200-BSU / SUA MP-8250-BS9 / BS1 MP-8250-SUR MP-820-BSU-100 MP-820-SUA-50+
MP-825-SUR-50+
MP-825-CPE-50 Licensed Bands (in GHz) WD 2.4, 4.9, 5.0 WD 4.9, 5.0 WD 5.0 WD 6.4 WD 4.9, 5.0 WD 5.0 i s n a m o D y c n e u q e r F World 5 GHz World 4.9 GHz World 2.4 GHz World 2.3 GHz World 2.5 GHz Canada 5 GHz WD Europe 5.8 GHz WD Europe 5.4 GHz WD-Europe 2.4 GHz Russia 5 GHz Taiwan 5 GHz WD United States 5 GHz Canada 5.8 GHz World 6.4 GHz WD UK 5.8 GHz World 5.9 GHz India 5.8 GHz Brazil 5.4 GHz Brazil 5.8 GHz Australia 5.4 GHz Australia 5.8 GHz WD United States 4.9 GHz Canada 4.9 GHz WD Japan 4.9 GHz Legacy 5GHz WD Japan 5.6 GHz WD United States 5.8 World 5.8 GHz Indonesia 5.7 GHz l s e u a V M U N E 4 5 6 7 8 9 10 11 12 13 14 15 16 17 20 21 23 24 25 26 27 29 30 31 32 33 34 40 41 Tsunami 800 & 8000 Series - Software Management Guide 298 Frequency Domains and Channels Point to Point Devices Product(s) QB-8100-EPA/LNK QB-8150-EPR QB-8150-LNK QB-8150-LNK-100 QB-8151-EPR/LNK QB-8150-LNK-12#
QB-8150-LNK-50 QB-8200-EPA/LNK QB-8250-EPR/LNK QB-825-EPR/LNK-50 QB-825-EPR/LNK-50+
Licensed Bands (in GHz) WD 2.4, 4.9, 5.0 WD 4.9, 5.0 WD 5.0 WD 4.9, 5.0 WD 5.0 i s n a m o D y c n e u q e r F World 5 GHz World 4.9 GHz World 2.4 GHz World 2.3 GHz World 2.5 GHz Canada 5 GHz WD-Europe 5.8 GHz WD-Europe 5.4 GHz WD-Europe 2.4 GHz Russia 5 GHz Taiwan 5 GHz WD United States 5 GHz Canada 5.8 GHz World 6.4 GHz World UK 5.8 GHz World 5.9 GHz India 5.8 GHz Brazil 5.4 GHz Brazil 5.8 GHz Australia 5.4 GHz Australia 5.8 GHz WD United States 4.9 GHz Canada 4.9 GHz WD Japan 4.9 GHz Legacy 5 GHz WD Japan 5.6 GHz WD United States 5.8 GHz World 5.8 GHz Indonesia 5.7 GHz l s e u a V M U N E 4 5 6 7 8 9 10 11 12 13 14 15 16 17 20 21 23 24 25 26 27 29 30 31 32 33 34 40 41 Tsunami 800 & 8000 Series - Software Management Guide 299 Europe and Japan Frequency Domains Frequency Domains and Channels Point to Multipoint Devices Product(s) MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 MP-8200-BSU / SUA MP-8250-BS9 / BS1 MP-8250-SUR MP-820-BSU-100 MP-820-SUA-50+
MP-825-SUR-50+
MP-825-CPE-50 Licensed Bands (in GHz) EU 2.4, 4.9, 5.0 EU 4.9, 5.0 EU 4.9, 5.0 JP 4.9, 5.0 EU 4.9, 5.0 EU 5.0 i s n a m o D y c n e u q e r F Japan 2.4 GHz Japan 4.9 GHz UK 5.8 GHz Europe 5.8 GHz Europe 5.4 GHz Europe 2.4 GHz Japan 5.6 GHz l s e u a V M U N E 18 19 35 36 37 38 39 Point to Point Devices Product(s) QB-8100-EPA/LNK QB-8150-EPR QB-8150-LNK QB-8150-LNK-100 QB-8151-EPR/LNK QB-8200-EPA/LNK QB-8250-EPR/LNK QB-825-EPR/LNK-50 QB-825-EPR/LNK-50+
Licensed Bands (in GHz) EU 2.4, 4.9, 5.0 EU 4.9, 5.0 JP 4.9, 5.0 EU 4.9, 5.0 EU 5.0 i s n a m o D y c n e u q e r F Japan 2.4 GHz Japan 4.9 GHz UK 5.8 GHz Europe 5.8 GHz Europe 5.4 GHz Europe 2.4 GHz Japan 5.6 GHz l s e u a V M U N E 18 19 35 36 37 38 39 When the device is configured by using CLI or SNMP, care has to be taken to set the domains by using a predefined ENUM value. Example: The CLI commands to set WORLD 5 GHz as frequency domain are as follows:
D
6
A
1 6
7
. 7
9
C 0
. 5
B
6
2
E
8
D
0
1
7
2
9
0
1
1
3
4
4
E
) 1
, 0
. 9
0
1
1
1
1
7
G 0
7
9
9
0 4
0 2
9 9
1
. G 7
. 5 1 1
1
0 0
. B
. 1
. 5
3
4 4 4
4
5 7 7
1
0
F 1
. 4
1
. 9 0
, 4
7
300 Tsunami 800 & 8000 Series - Software Management Guide Frequency Domains and Channels
: All DFS countries support only 20 and 40 MHz channel bandwidths. 2.4 GHz Channels Frequency Frequency Allowed Channels (Center Frequency in GHz) Domain Band
(Start Frequency ~
End Frequency in MHz) United States 2.4 GHz 2412 ~ 2462 World 2.3 GHz 2277 ~ 2397 World 2.4 GHz 2412 ~ 2472 World 2.5 GHz 2477 ~ 2507 WD-Europe 2.4 GHz 2412 ~ 2472 Europe 2.4 GHz 2412 ~ 2472 5 MHz 10 MHz 20 MHz 40 PLUS 40 MINUS MHz MHz 1 (2412), 2 (2417)... 10 (2457), 11 (2462). US SKU 1 (2412), 2 (2417)... 10 (2457), 11 (2462). World SKU 1 (2412), 2 (2417)... 10 (2457), 11 (2462). 1 (2412), 2 (2417)... 6 (2437), 7 (2442). 5 (2432), 6 (2437)... 10 (2457), 11 (2462). 100 (2277), 101 (2282)... 123 (2392), 124 (2397). 100 (2277), 101 (2282)... 122 (2387), 123 (2392). 101 (2282), 102 (2287)... 121(2382), 122 (2387). 101 (2282), 102 (2287)... 117 (2362), 118 (2367). 105 (2302), 106(2307)... 121(2382), 122 (2387). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 200(2477), 201(2482)... 205 (2502), 206(2507). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 200(2477), 201(2482)... 205 (2502), 206(2507). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). EU SKU 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 201(2482), 202 (2487)... 204(2497), 205 (2502). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 1 (2412), 2 (2417)... 8 (2447), 9 (2452). 5 (2432), 6 (2437)... 12 (2467), 13 (2472).
1 (2412), 2 (2417)... 8 (2447), 9 (2452). 5 (2432), 6 (2437)... 12 (2467), 13 (2472). 1 (2412), 2 (2417)... 12 (2467), 13 (2472). 1 (2412), 2 (2417)... 8 (2447), 9 (2452). 5 (2432), 6 (2437)... 12 (2467), 13 (2472). Tsunami 800 & 8000 Series - Software Management Guide 301 Frequency Domains and Channels 4.9 and 5 GHz Channels Frequency Frequency Band Allowed Channels (Center Frequency in GHz) Domain
(Start Frequency ~
End Frequency in MHz) 5 MHz 10 MHz 20 MHz 40 PLUS 40 MINUS MHz MHz United States 5 GHz
5260 ~ 5320 (DFS) 5500 ~ 5580 (DFS) 5660 ~ 5700 (DFS) 5745 ~ 5825 (non-DFS) US SKU
5740 ~ 5830 (Non-DFS) United States 5.8 GHz 148(5740), 149(5745)... 165(5825), 166(5830). United States2 (5.3, 5.8 GHz) 5260 ~ 5320 (DFS) 5745 ~ 5825 (Non-DFS)
149(5745), 150(5750)... 164(5820), 165(5825).
4942 ~ 4987 (Non-DFS) United States 4.9 GHz 5(4942.5), 15(4947.5)... 85(4982.5), 95(4987.5). 10(4945), 20(4950)... 80(4980), 90(4985). Japan SKU 52(5260), 53(5265)... 59(5295), 60(5300). 100(5500), 101(5505)... 111(5555), 112(5560). 133(5665), 134(5670)... 135(5675), 136(5680). 149(5745), 150(5750)... 160(5800), 161(5805). 149(5745), 150(5750)... 160(5800), 161(5805). 52(5260), 53(5265)... 59(5295), 60(5300). 149(5745), 150(5750)... 160(5800), 161(5805). 56(5280), 57(5285)... 63(5315), 64(5320). 104(5520), 105(5525)... 115(5575), 116(5580). 136(5680), 137(5685)... 139(5695), 140(5700). 153(5765), 154(5770)... 164(5820), 165(5825). 153(5765), 154(5770)... 164(5820), 165(5825). 56(5280), 57(5285)... 63(5315), 64(5320). 153(5765), 154(5770)... 164(5820), 165(5825).
52(5260), 53(5265)... 63(5315), 64(5320). 100(5500), 101(5505)... 115(5575), 116(5580). 132(5660), 133(5665)... 139(5695), 140(5700). 149(5745), 150(5750)... 164(5820), 165(5825). 149(5745), 150(5750)... 164(5820), 165(5825). 52(5260), 53(5265)... 63(5315), 64(5320). 149(5745), 150(5750)... 164(5820), 165(5825). 20(4950), 30(4955)... 70(4975), 80(4980). Japan 4.9 4912 ~ 4980 (Non-DFS) 182(4912.5), 183(4917.5)... 188(4942.5), 189(4947.5). 183(4915), 184(4920)... 188(4940), 189(4945). 184(4920), 188(4940)... 192(4960), 196(4980). 184(4920), 185(4925), 191(4955)... 192(4960). 188(4940), 189(4945), 195(4975)... 196(4980). Tsunami 800 & 8000 Series - Software Management Guide 302 Frequency Frequency Band Allowed Channels (Center Frequency in GHz) Frequency Domains and Channels 10 MHz 20 MHz 40 PLUS 40 MINUS Domain
(Start Frequency ~
End Frequency in MHz) 5 MHz Japan 5.6 5500 ~ 5700 (DFS)
WD United States 5 GHz 5255 ~ 5325 (DFS) 5495 ~ 5585 (DFS) 5655 ~ 5705 (DFS) 5740 ~ 5830 (non-DFS) World SKU
100(5500) 104(5520) 108(5540) 112(5560) 116(5580) 120(5600) 124(5620) 128(5640) 132(5660) 136(5680) 140(5700) 52(5260), 53(5265)... 63(5315), 64(5320). 100(5500), 101(5505)... 115(5575), 116(5580). 132(5660), 133(5665)... 139(5695), 140(5700). 149(5745), 150(5750)... 164(5820), 165(5825) 32(5160), 33(5165)... 213(6065), 214(6070). MHz MHz 100(5500) 108(5540) 116(5580) 124(5620) 136(5680) 104(5520) 112(5560) 120(5600) 128(5640) 140(5700) 52(5260), 53(5265)... 59(5295), 60(5300). 100(5500), 101(5505)... 111(5555), 112(5560). 133(5665), 134(5670), 135(5675), 136(5680). 149(5745), 150(5750)... 160(5800), 161(5805). 32(5160), 33(5165)... 209(6045), 210(6050). 56(5280), 57(5285)... 63(5315), 64(5320). 104(5520), 105(5525)... 115(5575), 116(5580). 136(5680), 137(5685)... 139(5695), 140(5700). 153(5765), 154(5770)... 164(5820), 165(5825). 36(5180), 37(5185)... 213(6065), 214(6070). 186(4930), 187(4935), 188(4940), 10(4945), 20(4950) 90(4985), 100(4990). World 5 GHz 5155 ~ 6075 (Non-DFS) Please note that 8200 &
82x SKUs support upto 5920 MHz frequency. 4905 ~ 4995 (Non-DFS) World 4.9 GHz 31(5155), 32(5160)... 214(6070), 215(6075). 31(5155), 32(5160)... 214(6070), 215(6075). 181(4905), 182(4910) 187(4935), 188(4940). 10(4945), 20(4950) 100(4990), 110(4995). 181(4905), 182(4910) 187(4935), 188(4940). 10(4945), 20(4950) 100(4990), 110(4995). 182(4910), 183(4915) 187(4935), 188(4940). 10(4945), 20(4950) 90(4985), 100(4990). 182(4910), 183(4915) 187(4935), 188(4940). 10(4945), 20(4950) 50(4965), 60(4970). Tsunami 800 & 8000 Series - Software Management Guide 303 Frequency Frequency Band Allowed Channels (Center Frequency in GHz) Frequency Domains and Channels 10 MHz 20 MHz 40 PLUS 40 MINUS 5 MHz 176(5880), 177(5885)... 183(5915), 184(5920). 176(5880), 177(5885)... 183(5915), 184(5920). Domain World 5.9 GHz
(Start Frequency ~
End Frequency in MHz) 5880 ~ 5920 (Non-DFS) Canada 5 GHz 5255 ~ 5325 (DFS) 5495 ~ 5585 (DFS) 5655 ~ 5705 (DFS) WD-Europe 5.4 GHz 5495 ~ 5585 (DFS) 5655 ~ 5705 (DFS)
WD-Europe 5.8 GHz 5735 ~ 5870 (DFS)
Russia 5 GHz 5155 ~ 6075 (Non-DFS) Please note that 8200 &
82x SKUs support upto 5920 MHz frequency. 31(5155), 32(5160)... 214(6070), 215(6075). 31(5155), 32(5160)... 214(6070), 215(6075). Taiwan 5 GHz 5495 ~ 5705 (DFS) 5740 ~ 5810 (Non-DFS)
MHz MHz 177(5885) 178(5890) 179(5895) 181(5905) 182(5910) 183(5915) 52(5260), 53(5265)... 59(5295), 60(5300). 100(5500), 101(5505)... 111(5555), 112(5560). 132(5660), 133(5665)... 135(5675), 136(5680). 100(5500), 101(5505)... 111(5555), 112(5560). 132(5660), 133(5665)... 135(5675), 136(5680). 149(5745), 150(5750) 168(5840), 169(5845). 32(5160), 33(5165)... 209(6045), 210(6050). 100(5500), 101(5505)... 135(5675), 136(5680). 149(5745), 150(5750)... 156(5780), 157(5785). 56(5280), 57(5285)... 63(5315), 64(5320). 104(5520), 105(5525)... 115(5575), 116(5580). 136(5680), 137(5685)... 139(5695), 140(5700). 104(5520), 105(5525)... 115(5575), 116(5580). 136(5680), 137(5685)... 139(5695), 140(5700). 153(5765), 154(5770)... 172(5860), 173(5865). 36(5180), 37(5185)... 213(6065), 214(6070). 104(5520), 105(5525)... 139(5695), 140(5700). 153(5765), 154(5770)... 160(5800), 161(5805). 177(5885), 178(5890)... 182(5910), 183(5915). 52(5260), 53(5265)... 63(5315), 64(5320). 100(5500), 101(5505)... 115(5575), 116(5580). 132(5660), 133(5665)... 139(5695), 140(5700). 100(5500), 101(5505)... 115(5575), 116(5580). 132(5660), 133(5665)... 139(5695), 140(5700). 149(5745), 150(5750)... 172(5860), 173(5865). 32(5160), 33(5165)... 213(6065), 214(6070). 100(5500), 101(5505)... 139(5695), 140(5700). 149(5745), 150(5750)... 160(5800), 161(5805). Tsunami 800 & 8000 Series - Software Management Guide 304 Frequency Frequency Band Allowed Channels (Center Frequency in GHz) Frequency Domains and Channels 10 MHz 20 MHz 40 PLUS 40 MINUS Domain India 5.8 GHz Canada 5.8 GHz
(Start Frequency ~
End Frequency in MHz) 5830 ~ 5870 (Non-DFS) 5735 ~ 5855 (Non-DFS) WD U.K 5.8 GHz 5730 ~ 5790 (DFS) 5820 ~ 5845 (DFS) Australia 5.4 GHz 5475 ~ 5595 (DFS) 5655 ~ 5720 (DFS) 5 MHz 166(5830), 167(5835)... 173(5865), 174(5870). 147(5735), 148(5740)... 170(5850), 171(5855).
166(5830), 167(5835)... 173(5865), 174(5870). 147(5735), 148(5740)... 170(5850), 171(5855).
Australia 5.8 GHz Brazil 5.4 GHz Brazil 5.8 GHz 5730 ~ 5845 (Non-DFS) 146(5730), 147(5735) 168(5840), 169(5845). 146(5730), 147(5735)... 148(5740), 169(5845). 5475 ~ 5720 (DFS)
5730 ~ 5845 (Non-DFS) Canada 4.9 GHz 4945 ~ 4985 (Non-DFS) 146(5730), 147(5735)... 168(5840), 169(5845). 10(4945), 20(4950)... 80(4980), 90(4985). 146(5730), 147(5735)... 168(5840), 169(5845). 10(4945), 20(4950)... 80(4980), 90(4985). MHz MHz 167(5835) 168(5840) 169(5845) 171(5855) 172(5860) 173(5865) 148(5740), 149(5745)... 165(5825), 166(5830). 147(5735), 148(5740)... 152(5760), 153(5765). 152(5760), 153(5765)... 169(5845), 170(5850). 151(5755), 152(5760)... 156(5780), 157(5785). 96(5480), 97(5485) 113(5565), 114(5570). 132(5660), 133(5665) 138(5690), 139(5695). 147(5735), 148(5740)... 163(5815), 164(5820). 96(5480), 97(5485) 138(5690), 139(5695). 147(5735), 148(5740)... 163(5815), 164(5820). 100(5500), 101(5505) 117(5585), 118(5590). 136(5680), 137(5685) 142(5710), 143(5715). 151(5755), 152(5760) 167(5835), 168(5840). 100(5500), 101(5505) 142(5710), 143(5715). 151(5755), 152(5760)... 167(5835), 168(5840). 20(4950), 30(4955), 40(4960). 60(4970), 70(4975), 80(4980). 167(5835), 168(5840)... 172(5860), 173(5865). 148(5740), 149(5745)... 169(5845), 170(5850). 147(5735), 148(5740)... 156(5780), 157(5785). 167(5835). 96(5480), 97(5485) 117(5585), 118(5590). 132(5660), 133(5665) 142(5710), 143(5715). 147(5735), 148(5740) 167(5835), 168(5840). 96(5480), 97(5485) 142(5710), 143(5715). 147(5735), 148(5740)... 167(5835), 168(5840). 20(4950), 30(4955)... 70(4975), 80(4980). Tsunami 800 & 8000 Series - Software Management Guide 305 Frequency Frequency Band Allowed Channels (Center Frequency in GHz) Frequency Domains and Channels Domain
(Start Frequency ~
End Frequency in MHz) Legacy 5GHz 5150 ~ 6080 (Non-DFS) Please note that 8200 &
82x SKUs support upto 5920 MHz frequency. 4912 ~ 4980 (Non-DFS) Please note that 8100 SKUs does not support this frequency. WD Japan 4.9 WD-Japan 5.6 5500 ~ 5700 (DFS)
5 MHz 30(5150), 31(5155)... 215(6075), 216(6080). 10 MHz 20 MHz 40 PLUS 40 MINUS MHz MHz 30(5150), 32(5160)... 214(6070), 216(6080). 30(5150), 34(5170)... 210(6050), 216(6070).
182(4912.5), 183(4917.5)... 188(4942.5), 189(4947.5). 183(4915), 184(4920)... 188(4940), 189(4945). 184(4920), 188(4940), 192(4960), 196(4980). 184(4920) 192(4960) 188(4940) 196(4980) 100(5500) 104(5520) 108(5540) 112(5560) 116(5580) 120(5600) 124(5620) 128(5640) 132(5660) 136(5680) 140(5700) 20(4950), 30(4955)... 70(4975), 80(4980). 149(5745), 150(5750)... 164(5820), 165(5825). 145(5725), 146(5730)... 169(5845), 170(5850). 147(5735), 148(5740)... 162(5810), 163(5815). 100(5500) 108(5540) 116(5580) 124(5620) 136(5680) 104(5520) 112(5560) 120(5600) 128(5640) 140(5700)
149(5745), 150(5750)... 160(5800), 161(5805). 145(5725), 146(5730)... 165(5825), 166(5830). 147(5735), 148(5740)... 158(5790), 159(5795). 153(5765), 154(5770)... 164(5820), 165(5825). 149(5745), 150(5750)... 169(5845), 170(5850). 151(5755), 152(5760)... 162(5810), 163(5815). WD United States 4.9 GHz WD United States 5.8 GHz World 5.8 GHz 4942 ~ 4987 (Non-DFS) 5740 ~ 5830 (Non-DFS) 5720 ~ 5855 (Non-DFS) Indonesia 5.7 GHz 5730 ~ 5820 (Non-DFS) 5(4942.5), 15(4947.5)... 85(4982.5), 95(4987.5), 148(5740), 149(5745)... 165(5825), 166(5830). 144(5720), 145(5725)... 170(5850), 171(5855). 146(5730), 147(5735)... 163(5815), 164(5820). 10(4945), 20(4950)... 80(4980), 90(4985). 149(5745), 150(5750)... 164(5820), 165(5825). 144(5720), 145(5725)... 170(5850), 171(5855). 146(5730), 147(5735)... 163(5815), 164(5820). Tsunami 800 & 8000 Series - Software Management Guide 306 Frequency Frequency Band Allowed Channels (Center Frequency in GHz) Domain
(Start Frequency ~
End Frequency in MHz) 5 MHz 10 MHz 20 MHz 40 PLUS 40 MINUS MHz MHz Frequency Domains and Channels U.K 5.8 GHz 5730 ~ 5790 (DFS) 5820 ~ 5845 (DFS) Europe 5.8 GHz 5735 ~ 5870 (DFS) Europe 5.4 GHz 5495 ~ 5585 (DFS) 5655 ~ 5705 (DFS)
EU SKU
147(5735), 148(5740)... 156(5780), 157(5785). 167(5835) 149(5745), 150(5750)... 172(5860), 173(5865). 100(5500), 101(5505)... 115(5575), 116(5580). 132(5660), 133(5665)... 139(5695), 140(5700). 147(5735), 148(5740)... 152(5760), 153(5765). 151(5755), 152(5760)... 156(5780), 157(5785). 149(5745), 150(5750) 168(5840), 169(5845). 100(5500), 101(5505)... 111(5555), 112(5560). 132(5660), 133(5665)... 135(5675), 136(5680). 153(5765), 154(5770)... 172(5860), 173(5865). 104(5520), 105(5525)... 115(5575), 116(5580). 136(5680), 137(5685)... 139(5695), 140(5700). Tsunami 800 & 8000 Series - Software Management Guide 307 Frequency Domains and Channels 6.4 GHz Channels Frequency Frequency Band Allowed Channels (Center Frequency) Domain
(Start Frequency ~
End Frequency in MHz) World 6.4 GHz 5905 ~ 6420 5 MHz 10 MHz 20 MHz 40 PLUS 40 MINUS MHz MHz 181 (5905), 182 (5910)... 283 (6415), 284 (6420). 181 (5905), 182 (5910)... 283 (6415), 284 (6420). 182 (5910), 183 (5915)... 282 (6410), 283 (6415). 182 (5910), 183 (5915)... 278 (6390), 279 (6395). 186 (5930) 187 (5935)... 282 (6410), 283 (6415).
: The center frequency listed in the above tables are based on channel offset set to 0. If channel offset is set to any value other than 0 then the center frequency will be shifted accordingly. You can set the channel offset ranging from
-2 in MP-8150-CPE, MP-8160-BSU, MP-8160-SUA, MP-8160-CPE-A100, MP-825-CPE-50, MP-820-BSU-100, MP-820-SUA-50+, MP-825-SUR-50+, QB-8150-EPR/LNK-12/50, QB-825-EPR/LNK-50, and QB-825-EPR/LNK-50+. to +2 MHz Details for 40MHz Bandwidth While choosing 40MHz bandwidth, you can select 40 PLUS (Upper Extension) or 40 MINUS (Lower Extension). 40 PLUS means the center frequency calculation is done for 20MHz and add another 20MHz to the top edge of 20MHz. 40 MINUS means the center frequency calculation is done for 20MHz and add another 20MHz to the bottom edge of 20MHz. For 40 PLUS 2.4GHz ->
Channel 1 = 2412 MHz Bandwidth starts from 2403 MHz and ends at 2442 MHz 5GHz ->
Channel 52 = 5260 MHz Bandwidth starts from 5251 MHz and ends at 5290 MHz Tsunami 800 & 8000 Series - Software Management Guide 308 6.4GHz ->
Channel 181 = 5910 MHz Bandwidth starts from 5901 MHz and ends at 5940 MHz Frequency Domains and Channels For 40 MINUS 2.4GHz ->
Channel 5 = 2432 MHz Bandwidth starts from 2403 MHz and ends at 2442 MHz 5GHz ->
Channel 56 = 5280 MHz Bandwidth starts from 5251 MHz and ends at 5290 MHz 6.4GHz ->
Channel 186 = 5930 MHz Bandwidth starts from 5901 MHz and ends at 5940 MHz Tsunami 800 & 8000 Series - Software Management Guide 309 Frequency Domains and Channels Tsunami 800 & 8000 Series - Software Management Guide 310 LACP - Device Management Tsunami Quickbridge devices that are part of the LACP link cannot be managed through the switches, so it is recommended to use the second Ethernet port for management.
When using second Ethernet port for management, ensure to disable Auto Shutdown for Ethernet2. See H L M P ). I O K N J STP/LACP Frames should be set to passthru. See Q plugged-in) or Gigabit 48 VDC Injector (GIG-POE-INJ-48VDC-T) (without 48 VDC power plugged-in). Directly connecting the Ethernet port2 of the device to the PC Ethernet NIC may damage the PC NIC port or Ethernet port on the switch.
: The second Ethernet port is POE out; it should be connected via a passive POE (Without the AC power Y X I K T P V N V T P Z U W U
J J R S R R S In this chapter, we have chosen the following two examples to explain the device management in the LACP link, by using the second Ethernet port. Example1 Tsunami 800 & 8000 Series - Software Management Guide 311 Figure D-1 Device Management with No VLAN LACP - Device Management In this example, we have considered a network with two QuickBridge links each supporting LACP mode. In this setup, VLAN is not configured on both LACP switches and devices. The Ethernet1 of all the devices is connected to the LACP port and is used for data transfer. To manage the devices, use a dedicated management Personal Computer per QuickBridge link. Use Ethernet2 port of the device to connect the Personal Computer.
: In Fail Over Mode (if one of the link goes down), the remote device of a particular link cannot be managed. Example2 Figure D-2 Device Management with VLAN In this example, we have considered a network with two QuickBridge links each supporting LACP mode. In this setup, Ethernet 1 of all the devices is connected to the LACP port, with no VLAN. The Ethernet 2 of all the devices is connected to the tagged VLAN management port with Spanning Tree enabled. To manage all the devices in the QuickBridge network, use one dedicated management Personal Computer connected to the untagged VLAN port of the switch. To manage the devices, configure same management VLAN Id on all the devices. The Ethernet 1 should be configured in transparent VLAN mode to allow data transfer. The Ethernet2 can be configured either in transparent mode or trunk mode to allow management traffic to the devices. With Spanning Tree enabled on the LACP Switches, you will be able to manage all the QuickBridge devices, even if one of the wireless link goes down. For VLAN configuration, refer \
H
W X U R N V T _ K N T Y P S Z
[ . Tsunami 800 & 8000 Series - Software Management Guide 312 QinQ The Subscribers and End Point devices support QinQ VLAN feature that enables service providers to use a single VLAN ID to support multiple customer VLANs by encapsulating the 802.1Q VLAN tag within another 802.1Q frame. The benefits with QinQ are as follows:
Increases the VLAN space in a provider network or enterprise backbone Reduce the number of VLANs that a provider needs to support within the provider network for the same number of customers Enables customers to plan their own VLAN IDs, without running into conflicts with service provider VLAN IDs Provides a simple Layer 2 VPN solution for small-sized MAN (Metropolitan Area Networks) or Intranet Provides customer traffic isolation at Layer 2 within a service provider network Consider a BSU and SU network, with QinQ (Double VLAN (Q in Q) Status) enabled on the SU. Subscriber:
Based on the Ethernet VLAN configuration on the Subscriber, the data packets are tagged as follows:
Different outer VLAN IDs can be configured for different SUs, but those VLAN IDs should also be configured on the In case of downlink traffic, SU always expects double tagged packet from the wireless side. If the outer VLAN tag BSU Ethernet.
: When Double VLAN is enabled on the device, the Port VLAN ID should not be set to -1.
: When Double VLAN is enabled on the device, the Access VLAN ID should not be set to -1. Transparent Mode: When QinQ is enabled, SU cannot be configured in the Transparent mode. Trunk Mode: SU expects a tagged packet (inner tag) and tags the packet with Service VLAN ID as outer tag. matches with Service VLAN ID then SU will untag the packet and forward to Ethernet. Based on Ethernet VLAN configuration, the data packets are handled accordingly. When the outer VLAN tag does not match the Service VLAN ID, the packet is dropped. Access Mode: SU double tags the packet with Access VLAN ID as inner tag and Service VLAN ID as outer tag. Trunk Mode: The outer tag of the packet arriving at the Ethernet side should match with the VLAN ID configured in the trunk table. Transparent Mode: When configured in transparent mode, ensure the data packet is double tagged. VLAN ID. 313 BSU always considers the first VLAN tag available in the packet; in case of double tagged packet it is the outer Base Station:
Tsunami 800 & 8000 Series - Software Management Guide QinQ Device Management From the BSU Ethernet side, the BSU/SU can be managed with a single VLAN tagged packet that matches the Management VLAN ID. From the SU Ethernet side, only SU can be managed with a single VLAN tagged packet that matches the Management VLAN ID; BSU cannot be managed from the SU Ethernet side.
In a QuickBridge link, Q-in-Q should be enabled either on an End Point A or an End Point B. The user configurable TPID is only used in the Service Provider VLAN tag. The Inner or customer VLAN tag should always have TPID as 0x8100. An Example:
The following diagram is the pictorial representation of how traffic flows in a QinQ enabled network. The Computer behind SU can be used to manage the SU. To manage BSU, connect another Computer to BSU Ethernet port through a VLAN switch with PVID as 100. Tsunami 800 & 8000 Series - Software Management Guide 314 BSU Redundancy The BSU Redundancy feature can help in reducing the network outage in case of the Primary BSU failure. This feature enables the SU to keep track of the Primary and the Secondary BSU availability through a proprietary protocol. This allows the SU to switch between the Primary and the Secondary BSU depending on the link status. If both the Primary and the Secondary BSU are not available, the SU attempts to find any other BSU within its network. Configuration Guidelines This feature is activated only on a SU. By default, it is disabled. Example The Primary and the Secondary BSU names should be unique. Use a non-empty string to enable this feature and an empty string to disable this feature. It is expected that the Primary and the Secondary BSUs are connected to the same L2 Broadcast domain and are configured with the same Network Name as the SU. When this feature is enabled, it is mandatory to configure both the Primary and the Secondary BSU name on the SU.
z
y y
a
b
e i u
k v a w b x y
q g z
f b
r Tsunami 800 & 8000 Series - Software Management Guide 315 Figure F-1 An Example - BSU Redundancy Feature b
c d e f g d h
g i j
k a b
l b m n l
o g d h i j p q g d n d
o s g j m g q k j n f g e i t Log Samples for BSU Redundancy SU - During Boot Up BSU Redundancy SU registered with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26) on channel 160(0x14004A0) (SNR: A1:46 A2:0 A3:40[dB]) at WORP port[ 0 ]. SU registered with BSU: BSU2 (MAC: 00:0b:6b:b7:4b:ff) on channel 60(0x78043C) (SNR: A1:51 A2:0 A3:49[dB]) at WORP port[ 0 ]. After getting connected to the Primary BSU, the SU should discover the secondary BSU. Primary BSU Down - Connected to Secondary BSU SU is trying to register with BSU: BSU2 (MAC: 00:0b:6b:b7:4b:ff). SU is trying to register with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26). Link Profile Index: 1. kernel:Worp: Link Profile Index: 1. Channel 60 is set as the current channel. Channel 160 is set as the current channel. SU received QoS Class: Unlimited Best Effort (indx: 1). SU received QoS Class: Unlimited Best Effort (indx: 1). SU unregistered from BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26). Wireless: WORP Link Established with Primary BSU: BSU1 Wireless: SU discovered Secondary BSU:BSU2 on channel:60 Wireless: WORP Link Established with Secondary BSU: BSU2 1Wireless: WORP Link Established with Secondary BSU: BSU2 01:52:25 kernel:Worp: Link Profile Index: 1. 01:52:25: Wireless: WORP Link Established with Other BSU: BSU3 Connected to Other BSU 01:52:25 kernel:Worp: WARNING: Channel 100 is set as the current channel. 01:52:25 kernel:Worp: SU is trying to register with BSU: BSU3 (MAC: 00:20:a6:d3:ed:e5). 01:52:25 kernel:Worp: SU received QoS Class: Unlimited Best Effort (index: 1). 01:52:25 kernel:Worp: SU registered with BSU: BSU3 (MAC: 00:20:a6:d3:ed:e5) on channel 100(0xC80464) (SNR:
A1:58 A2:0 A3:54[dB]) at WORP port[ 0 ]. 01:54:35: Wireless: SU discovered Secondary BSU:BSU2 on channel:60 01:54:35: Wireless: SU discovered Primary BSU:BSU1 on channel:160 SU should discover both the Primary and the Secondary BSU, and connect to the Primary BSU after the switch time interval. BSU Switch Time Interval - 15 Minutes 00:08:34: Wireless: SU discovered Primary BSU:BSU1 on channel:160 00:23:34 kernel:Worp: SU unregistered from BSU: BSU2 (MAC: 00:0b:6b:b7:4b:ff). 00:23:34 kernel:Worp: WARNING: Channel 0 is set as the current channel. 00:23:35 kernel:Worp: SU is trying to register with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26). 00:23:35 kernel:Worp: SU received QoS Class: Unlimited Best Effort (indx: 1). Tsunami 800 & 8000 Series - Software Management Guide 316 00:23:35 kernel:Worp: SU registered with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26) on channel 160(0x14004A0) (SNR:
A1:43 A2:0 A3:36[dB]) at WORP port[ 0 ]. 00:23:35 kernel:Worp: Link Profile Index: 1. 00:23:35: Wireless: WORP Link Established with Primary BSU: BSU1 00:24:34: Wireless: SU discovered Secondary BSU:BSU2 on channel:60 BSU Redundancy Connect to Primary BSU 01:59:25: Wireless: WORP Link Established with Other BSU: BSU3 02:02:25 kernel:Worp: SU unregistered from BSU: BSU3 (MAC: 00:20:a6:d3:ed:e5).. 02:02:25: Wireless: SU discovered Secondary BSU:BSU2 on channel:60 02:02:25: Wireless: SU discovered Primary BSU:BSU1 on channel:160 02:02:25 kernel:Worp: SU is trying to register with BSU: BSU2 (MAC: 00:0b:6b:b7:4b:ff). 02:02:25 kernel:Worp: SU received QoS Class: Unlimited Best Effort (indx: 1). 02:02:25 kernel:Worp: SU registered with BSU: BSU2 (MAC: 00:0b:6b:b7:4b:ff) on channel 60(0x78043C) (SNR:
A1:37 A2:0 A3:35[dB]) at WORP port[ 0 ]. 02:02:25: Wireless: WORP Link Established with Secondary BSU: BSU2 02:04:25 kernel:Worp: SU unregistered from BSU: BSU2 (MAC: 00:0b:6b:b7:4b:ff). 02:04:25 kernel:Worp: SU is trying to register with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26). 02:04:25 kernel:Worp: SU registered with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26) on channel 160(0x14004A0)
(SNR: A1:46 A2:0 A3:42[dB]) at WORP port[ 0 ]. 02:05:25: Wireless: SU discovered Secondary BSU:BSU2 on channel:60 02:04:25: Wireless: WORP Link Established with Primary BSU: BSU1 No Response Message 03:32:25 kernel:Worp: WARNING: Channel 0 is set as the current channel. 03:32:25 kernel:Worp: SU is trying to register with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26). 03:32:25 kernel:Worp: SU received QoS Class: Unlimited Best Effort (indx: 1). 03:32:25 kernel:Worp: SU registered with BSU: BSU1 (MAC: 00:0b:6b:b7:4c:26) on channel 160(0x14004A0) (SNR:
A1:45 A2:0 A3:42[dB]) at WORP port[ 0 ]. 03:32:25 kernel:Worp: Link Profile Index: 1. 03:32:25: Wireless: WORP Link Established with Primary BSU: BSU1 03:33:25: Wireless: SU discovered Secondary BSU:BSU2 on channel:60 03:40:43: Wireless: Secondary BSU: BSU2 not Available Tsunami 800 & 8000 Series - Software Management Guide 317 Bootloader CLI and ScanTool Bootloader CLI The Bootloader CLI is a minimal subset of the normal CLI that is used to perform initial configuration of the device. The Bootloader CLI is available when the device embedded software is not running. This interface is only accessible through the serial interface, if:
The device does not contain a software image An existing image is corrupted An automatic (default) download of image over TFTP has failed The Bootloader CLI provides the ability to configure the initial setup parameters; and depending on this configuration, a software file is downloaded to the device during startup. The Bootloader CLI supports the following commands:
: Restore the factory settings The Bootloader CLI supports the following parameters (for viewing and modifying):
: Image file name (including the file extension) If the Bootloader fails to load the firmware from flash, it tries to get the firmware from the network. While trying to get firmware from the network, the device should be powered on using Ethernet 1 interface of the device. The default configuration of the Bootloader parameters are as follows:
: Print Online Help
: Reboot the device
: Set the parameters
: Show the parameters
: IP Address
: System Name
: Gateway IP Address
: Server IP Address
: IP Address Type
: Net Mask Parameter Value ipaddr netmask 169.254.128.132 255.255.255.0 gatewayip 169.254.128.132 systemname systemname serverip filename 169.254.128.133 imagename ipaddrtype dynamic Tsunami 800 & 8000 Series - Software Management Guide 318 Bootloader CLI and ScanTool command to set the parameter To Load the Firmware from the Network To Load the Firmware by using Dynamic IP Parameters 1. Set the ipaddrtype to dynamic 2. Run the BOOTP and TFTP Servers followed by device reboot command to view the parameters and their values, and use the When the device reboots, the device gets the IP Address and Boot filename from the BOOTP server. You need not change any of the default Bootloader parameters. After BOOTP succeeds, the device initiates a TFTP request with the filename it gets from BOOTP. To Load the Firmware by using Static IP Parameters ipaddrtype to static. 2. Run the TFTP Server followed by device reboot. command to set the IP parameters like ipaddr, serverip, filename and also set the parameter When the device reboots, the TFTP request is initiated with the value taken from the parameter filename. This request is sent to the IP address set as serverip. In this case, the TFTP Server should be reachable to the device. value. Use the 1. Use the ScanTool If you want to access the device with ScanTool, then the host running the ScanTool should also be in the same network as the device. The ScanTool broadcast requests are discarded by the routers if the device and the host running the ScanTool are in different network. This means that the ScanTool cannot discover the device. A device in Bootloader can be recognized by looking at the system description. If the system description does not contain any build number in braces, conclude that the device is in Bootloader mode. For example:
MP-8100-BSU-WD
- Description of the device vX.Y.Z - Firmware Version SN-11Pl15010031 - Serial Number BL-v1.3.1 - Bootloader version Figure G-1 Scan Tool View of a Device in Bootloader Mode (An Example) Tsunami 800 & 8000 Series - Software Management Guide 319 SNR Information Given below are the SNR values for the following devices:
QB-8151-EPR/LNK QB-8150-EPR/LNK QB-8100-EPA/LNK QB-8150-LNK-100 MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 Modulation QPSK 1/2 BPSK 1/2 Single Single No of MCS Index MCS0 MCS1 Streams MCS2 QPSK 3/4 Single MCS3 16 QAM 1/2 Single MCS4 16 QAM 3/4 Single MCS5 64 QAM 2/3 Single MCS6 64 QAM 3/4 Single MCS7 64 QAM 5/6 Single MCS8 BPSK 1/2 MCS9 QPSK 1/2 MCS10 QPSK 3/4 Dual Dual Dual MCS11 16 QAM 1/2 Dual MCS12 16 QAM 3/4 Dual MCS13 64 QAM 2/3 Dual MCS14 64 QAM 3/4 Dual MCS15 64 QAM 5/6 Dual 2.4 GHz 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR 1.6 3.3 4.9 6.5 9.7 13 14.6 16.2 3.3 6.5 9.7 13 19.5 26 29.3 32.5 10 15 21 23 26 29 30 32 12 20 22 23 27 30 36 39 86 86 84 82 80 79 79 78 86 84 82 80 80 79 78 78 3.3 6.5 9.7 13 19.5 26 29.3 32.5 6.5 13 19.5 26 39 52 58.5 65 10 16 21 23 26 29 31 32 14 21 23 23 27 30 35 38 86 86 84 82 80 79 78 78 86 84 82 80 80 79 77 77 6.5 13 19.5 26 39 52 58.5 65 13 26 39 52 78 104 117 130 12 21 21 23 25 27 30 32 14 21 22 24 30 34 37 39 86 86 84 82 80 78 77 77 86 84 82 80 78 78 77 76 13.5 27 40.5 54 81 15 30 45 60 90 108 120 121.5 135 135 150 27 54 81 108 162 216 243 270 30 60 90 120 180 240 270 300 26 26 26 30 33 37 40 42 16 26 28 32 35 37 43 45 80 80 79 77 77 76 75 75 80 80 79 77 77 76 75 75 Tsunami 800 & 8000 Series - Software Management Guide 320 SNR Information 5 GHz MCS Index Modulation No of Streams 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR MCS0 BPSK 1/2 Single MCS1 QPSK 1/2 Single MCS2 QPSK 3/4 Single MCS3 16 QAM 1/2 Single MCS4 16 QAM 3/4 Single MCS5 64 QAM 2/3 Single MCS6 64 QAM 3/4 Single MCS7 64 QAM 5/6 Single MCS8 BPSK 1/2 MCS9 QPSK 1/2 MCS10 QPSK 3/4 Dual Dual Dual MCS11 16 QAM 1/2 Dual MCS12 16 QAM 3/4 Dual MCS13 64 QAM 2/3 Dual MCS14 64 QAM 3/4 Dual MCS15 64 QAM 5/6 Dual 1.6 3.3 4.9 6.5 9.7 13 14.6 16.2 3.3 6.5 9.7 13 19.5 26 29.3 32.5 6 8 10 14 17 22 25 28 8 12 14 16 20 25 29 30 86 86 84 82 80 79 79 78 86 84 82 80 80 79 78 78 3.3 6.5 9.7 13 19.5 26 29.3 32.5 6.5 13 19.5 26 39 52 58.5 65 7 8 13 16 20 24 26 29 9 12 15 16 21 26 29 30 86 86 84 82 80 79 78 78 86 84 82 80 80 79 77 77 6.5 13 19.5 26 39 52 58.5 65 13 26 39 52 78 104 117 130 6 9 11 14 18 22 25 28 9 12 14 16 20 26 29 30 86 86 84 82 80 78 77 77 86 84 82 80 78 78 77 76 13.5 27 40.5 54 81 15 30 45 60 90 108 120 121.5 135 135 150 27 54 81 108 162 216 243 270 30 60 90 120 180 240 270 300 9 11 15 16 20 24 27 30 9 13 17 22 25 27 30 33 80 80 79 77 77 76 75 75 80 80 79 77 77 76 75 75 Given below are the SNR values for the following device(s) in legacy mode:
MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 Data Rate 2.25 1.5 10 10 5 MHz Min SNR Modulation BPSK 1/2 BPSK 3/4 QPSK 1/2 QPSK 3/4 16QAM 1/2 16QAM 3/4 3 4.5 6 9 12 14 17 20 2.4 GHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5 GHz Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Min SNR Max SNR Min SNR Max SNR Min SNR Max SNR 84 84 84 84 82 82 3 4.5 6 9 12 18 10 11 11 13 17 23 84 84 84 84 80 78 6 9 12 18 24 36 13 13 15 15 22 25 84 84 84 84 80 73 8 9 10 12 16 18 84 84 82 82 82 82 8 9 10 11 16 18 84 84 82 82 82 80 7 8 9 12 15 18 81 81 81 81 80 80 321 Tsunami 800 & 8000 Series - Software Management Guide SNR Information Modulation 5 MHz 2.4 GHz 10 MHz 20 MHz 5 MHz 10 MHz 20 MHz 5 GHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Min SNR Max SNR Min SNR Max SNR Min SNR Max SNR 64QAM 2/3 12 64QAM 3/4 13.5 27 29 81 80 24 27 29 30 76 74 48 54 28 29 73 72 24 27 80 80 24 27 80 80 24 27 78 76 Given below are the SNR values for the following devices:
QB-8150-LNK-12/50 MP-8150-CPE Modulation QPSK 1/2 BPSK 1/2 MCS Index MCS0 MCS1 No of Streams Single Single MCS2 QPSK 3/4 Single MCS3 16 QAM 1/2 Single MCS4 16 QAM 3/4 Single MCS5 64 QAM 2/3 Single MCS6 64 QAM 3/4 Single MCS7 64 QAM 5/6 Single MCS8 BPSK 1/2 MCS9 QPSK 1/2 MCS10 QPSK 3/4 Dual Dual Dual MCS11 16 QAM 1/2 Dual MCS12 16 QAM 3/4 Dual MCS13 64 QAM 2/3 Dual MCS14 64 QAM 3/4 Dual MCS15 64 QAM 5/6 Dual 5 GHz 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR 1.6 3.3 4.9 6.5 9.7 13 14.6 16.2 3.3 6.5 9.7 13 19.5 26 29.3 32.5 8 8 10 13 16 20 22 24 9 10 12 16 19 24 29 33 82 82 82 82 82 81 80 80 82 82 82 82 80 80 80 80 3.3 6.5 9.7 13 19.5 26 29.3 32.5 6.5 13 19.5 26 39 52 58.5 65 8 9 11 15 19 22 24 26 8 10 12 16 20 24 30 33 82 82 82 82 82 81 80 80 82 82 82 82 82 80 78 78 6.5 13 19.5 26 39 52 58.5 65 13 26 39 52 78 104 117 130 8 9 11 17 19 23 25 26 9 12 13 18 19 24 27 32 82 82 82 82 82 81 13.5 27 40.5 54 81 15 30 45 60 90 108 120 80 121.5 135 80 82 82 82 82 82 80 78 78 135 150 27 54 81 108 162 216 243 270 30 60 90 120 180 240 270 300 8 9 11 16 18 23 24 26 9 11 13 15 20 24 29 32 82 82 80 80 80 79 79 79 82 80 80 78 68 60 58 56 Tsunami 800 & 8000 Series - Software Management Guide 322 Given below are the SNR values for the following device(s) in legacy mode:
SNR Information QB-8150-LNK-12/50 MP-8150-CPE Modulation 5 MHz 5 GHz 10 MHz 20 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR BPSK 1/2 BPSK 3/4 QPSK 1/2 QPSK 3/4 16QAM 1/2 16QAM 3/4 64QAM 2/3 1.5 2.25 3 4.5 6 9 12 64QAM 3/4 13.5 7 8 9 12 16 20 24 27 81 81 80 78 76 72 69 68 3 4.5 6 9 12 18 24 27 7 8 9 12 16 20 24 27 81 81 80 78 76 71 69 68 6 9 12 18 24 36 48 54 7 8 9 12 16 20 24 27 81 81 79 78 73 71 69 66 Given below are the SNR values for the following devices:
MP-8160-BSU MP-8160-BS9 MP-8160-SUA MP-8160-CPE Modulation QPSK 1/2 BPSK 1/2 MCS Index MCS0 MCS1 No of Streams Single Single MCS2 QPSK 3/4 Single MCS3 16 QAM 1/2 Single MCS4 16 QAM 3/4 Single MCS5 64 QAM 2/3 Single MCS6 64 QAM 3/4 Single MCS7 64 QAM 5/6 Single MCS8 BPSK 1/2 MCS9 QPSK 1/2 Dual Dual 6.4 GHz 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR 1.6 3.3 4.9 6.5 9.7 13 14.6 16.2 3.3 6.5 6 8 10 13 16 21 22 24 8 10 87 87 86 84 80 74 70 67 87 87 3.3 6.5 9.7 13 19.5 26 29.3 32.5 6.5 13 6 8 10 14 16 21 23 24 8 10 87 87 84 84 78 70 67 65 87 87 6.5 13 19.5 26 39 52 58.5 65 13 26 6 7 10 13 16 20 22 24 7 11 87 87 86 82 76 70 67 65 86 84 13.5 27 40.5 54 81 15 30 45 60 90 108 120 121.5 135 135 150 27 54 30 60 7 8 12 13 19 21 24 27 10 12 87 86 82 74 70 62 56 55 86 82 Tsunami 800 & 8000 Series - Software Management Guide 323 SNR Information 6.4 GHz MCS Index Modulation No of Streams 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR MCS10 QPSK 3/4 Dual MCS11 16 QAM 1/2 Dual MCS12 16 QAM 3/4 Dual MCS13 64 QAM 2/3 Dual MCS14 64 QAM 3/4 Dual MCS15 64 QAM 5/6 Dual 9.7 13 19.5 26 29.3 32.5 15 16 20 25 27 28 84 80 74 70 66 64 19.5 26 39 52 58.5 65 13 17 23 24 27 29 84 80 74 66 62 62 39 52 78 104 117 130 13 17 20 24 27 29 82 78 71 65 62 62 81 108 162 216 243 270 90 120 180 240 270 300 15 18 22 25 27 30 75 74 56 55 53 52 Given below are the SNR values for the following devices:
QB-8250-EPR/LNK QB-8200-EPA/LNK MP-8200-BSU / SUA MP-8250-BS9 / BS1 MP-8250-SUR Modulation QPSK 1/2 BPSK 1/2 No of Single Single MCS Index MCS0 MCS1 Streams MCS2 QPSK 3/4 Single MCS3 16 QAM 1/2 Single MCS4 16 QAM 3/4 Single MCS5 64 QAM 2/3 Single MCS6 64 QAM 3/4 Single MCS7 64 QAM 5/6 Single MCS8 BPSK 1/2 MCS9 QPSK 1/2 MCS10 QPSK 3/4 Dual Dual Dual MCS11 16 QAM 1/2 Dual MCS12 16 QAM 3/4 Dual MCS13 64 QAM 2/3 Dual MCS14 64 QAM 3/4 Dual 4.900 - 5.925 GHz 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR 1.6 3.3 4.9 6.5 9.7 13 14.6 16.2 3.3 6.5 9.7 13 19.5 26 29.3 7 9 11 15 19 23 25 28 8 12 15 18 20 25 29 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 3.3 6.5 9.7 13 19.5 26 29.3 32.5 6.5 13 19.5 26 39 52 58.5 7 10 13 16 20 24 26 29 9 12 15 18 21 26 29 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 6.5 13 19.5 26 39 52 58.5 65 13 26 39 52 78 104 117 7 11 13 16 20 24 26 29 9 12 15 18 21 26 29 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 13.5 27 40.5 54 81 15 30 45 60 90 108 120 121.5 135 135 150 27 54 81 108 162 216 243 30 60 90 120 180 240 270 9 10 14 16 20 24 27 29 10 13 16 20 24 27 30 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 Tsunami 800 & 8000 Series - Software Management Guide 324 SNR Information MCS Index Modulation No of Streams 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR MCS15 64 QAM 5/6 Dual 32.5 30 50 65 30 50 130 30 50 270 300 33 50 4.900 - 5.925 GHz Given below are the SNR values for the following device(s) in legacy mode:
MP-8200-BSU / SUA MP-8250-BS9 / BS1 MP-8250-SUR BPSK 1/2 BPSK 3/4 Modulation QPSK 1/2 QPSK 3/4 16QAM 1/2 16QAM 3/4 64QAM 2/3 4.900 - 5.925 GHz 5 MHz 10 MHz 20 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR 1.5 2.25 3 4.5 6 9 12 7 8 10 12 16 20 25 80 80 79 78 77 76 74 73 3 4.5 6 9 12 18 24 27 7 9 10 12 16 20 24 27 80 79 77 76 74 72 70 68 6 9 12 18 24 36 48 54 8 9 10 12 16 21 25 79 77 76 74 73 72 69 27 68 64QAM 3/4 13.5 27 Tsunami 800 & 8000 Series - Software Management Guide 325 Given below are the SNR values for the following device:
SNR Information QB-825-EPR/LNK-50 MP-820-BSU-100 MP-820-SUA-50+
MP-825-SUR-50+
MP-825-CPE-50 QB-825-EPR/LNK-50 Modulation QPSK 1/2 BPSK 1/2 No of Single Single Streams MCS Index MCS0 MCS1 MCS2 QPSK 3/4 Single MCS3 16 QAM 1/2 Single MCS4 16 QAM 3/4 Single MCS5 64 QAM 2/3 Single MCS6 64 QAM 3/4 Single MCS7 64 QAM 5/6 Single MCS8 BPSK 1/2 MCS9 QPSK 1/2 MCS10 QPSK 3/4 Dual Dual Dual MCS11 16 QAM 1/2 Dual MCS12 16 QAM 3/4 Dual MCS13 64 QAM 2/3 Dual MCS14 64 QAM 3/4 Dual MCS15 64 QAM 5/6 Dual 5 GHz 5 MHz 10 MHz 20 MHz 40 MHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR Data Rate Full Short Min SNR Max SNR 1.6 3.3 4.9 6.5 9.7 13.0 14.6 16.2 3.3 6.5 9.7 13.0 19.5 26.0 29.3 32.5 9 10 13 17 20 24 26 30 10 13 15 18 23 27 29 31 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 3.3 6.5 9.7 13 19.5 26 29.3 32.5 6.5 13 19.5 26 39 52 58.5 65 9 10 13 17 21 25 27 29 10 12 16 19 23 26 29 30 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 6.5 13 19.5 26 39 52 58.5 65 13 26 39 52 78 104 117 130 9 12 13 16 22 25 27 30 10 12 15 17 23 27 30 31 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 13.5 27 40.5 54 81 108 121.5 135 27 54 81 108 162 216 243 270
9 11 15 16 24 28 29 30 10 13 17 22 25 27 30 33 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 50 Tsunami 800 & 8000 Series - Software Management Guide 326 Given below are the SNR values for the following device in legacy mode:
SNR Information MP-820-BSU-100 MP-820-SUA-50+
MP-825-CPE-50 MP-825-SUR-50+
Modulation 10 MHz 20 MHz 5 GHz Data Rate Min SNR Max SNR Data Rate Min SNR Max SNR 3 4.5 6 9 12 18 24 27 8 9 11 12 16 21 24 28 50 50 50 50 50 50 50 50 6 9 12 18 24 36 48 54 8 9 12 13 16 21 25 28 50 50 50 50 50 50 50 50 BPSK 1/2 BPSK 3/4 QPSK 1/2 QPSK 3/4 16QAM 1/2 16QAM 3/4 64QAM 2/3 64QAM 3/4 Tsunami 800 & 8000 Series - Software Management Guide 327 Configuration File Cross-loading across the Products Proxim portfolio comprises different product lines and SKUs which differ in features and capabilities depending on the hardware platform and the country setting or licensing used in them. This document describes the process to successfully apply the configuration file on a device(s) and the software checks run while applying the configuration file on a device(s). The user can apply a configuration file retrieved from a (Source) device to another compatible (Target) device. In order to successfully apply the configuration file, the following criteria should be met. 1. The Hardware Inventory Component ID should be same for both the source device and the target device. Hardware Inventory Component ID Products 2000 2001 2003 2005 2006 AP-800; AP-8000 MP-8100-BSU; MP-8100-SUA; MP-8150-SUR MP-8150-SUR-100 MP-8160-BSU; MP-8160-SUA; MP-8160-BS9 MP-8200-BSU; MP-8200-SUA; MP-8250-BS9/SUR QB-8xxx-EPA; QB-8xxx-EPR;
MP-8150-CPE Tsunami 82x Series AP-8100 Domains are listed below:
though they share the same component ID. and vice versa even though they share the same component ID. 2. The Regulatory Domain should be same in both the source device and the target device.The available Regulatory The configuration file can be applied only to the devices of the same family. The configuration file retrieved from an 8xx series device cannot be applied to a device from 81xx series. The configuration file of a MP-8160-BSU/MP-8160-SUA device cannot be applied to an 8100/8200 series device The configuration file of a MP-8150-CPE device cannot be applied to a MP-8160-CPE device and vice versa even WD SKU is compatible only with the EU SKU. For example, if the configuration file retrieved from a WD SKU If the above criteria are met, the configuration file can be successfully applied on the target device else an error message is thrown. Once the configuration file is loaded and the device is rebooted, the software tries to apply the new configuration file during the system boot-up process. device is loaded on a US or JP SKU target device then the upgrade fails. 328 Tsunami 800 & 8000 Series - Software Management Guide Configuration File Cross-loading across the Products Sometimes, a device from a particular product series may have different a license information compared to other devices of the same series. Therefore, the start-up process validates the configuration file against the license file of the device before applying the configuration file. The configuration file is valid, if the following conditions are met:
1. The input bandwidth limit in the configuration file should be less than or equal to the input bandwidth limit in the license file. 2. The output bandwidth limit in the configuration file should be less than or equal to the output bandwidth limit in the license file. 3. The sum of the input and output bandwidth limit in the configuration file should be less than or equal to the cumulative bandwidth limit in the license file. 4. The frequency band (2.4, 4.9, and 5 G Hz) in the configuration file should match with any one of the supported frequency bands in the license file. 5. The radio operation mode (BSU/SU/AP) in the configuration file should match with any one of supported radio operating modes in the license file. 6. The number of satellites in the configuration file should be less than or equal to the number of satellites in the license file. 7. The product family (TMP/TQB/AP) value in the configuration file should match the product family value in the license file. 8. Tx/Rx antenna chain mask in the configuration file should match the Tx/Rx antenna chain mask in the license file. during initialization and the device will boot-up with the last known good configuration. Before deleting the configuration file, an eventlog is generated about the violation of the license parameters. In some cases, if the last known good configuration does not exist internally, the device can reset the configuration to factory defaults and boot up. If any one of the above conditions is not met, the configuration file will be removed by the flash control module Tsunami 800 & 8000 Series - Software Management Guide 329 Abbreviations ACL ACS AES ALG ARP A Access Control List Automatic Channel Selection Advanced Encryption Standard Application Level Gateway Address Resolution Protocol ATPC Adaptive Transmit Power Control BSU Base Station Unit B C CCP CHAP CLI CIR CPE CRC DDRS DES DFS DHCP DNS DSL EIRP EOL ETSI Compression Control Protocol Challenge Handshake Authentication Protocol Command Line Interface Committed Information Rate Customer Premises Equipment Cyclic Redundancy Check D Dynamic Data Rate Selection Data Encryption Standard Dynamic Frequency Selection Dynamic Host Configuration Protocol Domain Name System Digital Subscriber Line E Equivalent Isotropically Radiated Power End of Life European Telecommunications Standards Institute F FCC Federal Communications Commission Tsunami 800 & 8000 Series - Software Management Guide 330 FCS Frame Check Sequence Abbreviations Gbps GPL GRE HTTP HTTPS IANA IC ICMP IGMP ISP ITS LACP LAN LCP LED LGPL MAN Mbps MD5 MIB MIMO MIR MP MPPE Gigabit Per Second General Public License Generic Routing Encapsulation G H HyperText Transfer Protocol HyperText Transfer Protocol Secure I Internet Assigned Numbers Authority (IANA) Industry Canada Internet Control Message Protocol Internet Group Management Protocol Internet Service Provider Intelligent Transportation System L Link Aggregation Control Protocol Local Area Network Link Configuration Protocol Light Emitting Diode Lesser General Public License M Metropolitan Area Networks Megabits Per Second Message-Digest algorithm Management Information Base Multiple-input and multiple-output Maximum Information Rate Multipoint Microsoft Point-to-Point Encryption MSCHAP v2 Microsoft Challenge-Handshake Authentication Protocol MTU Maximum Transmission Unit Tsunami 800 & 8000 Series - Software Management Guide 331 Abbreviations NAPT NAT NCP NBD NMS NOP PAP PC PoE PPPoE PTMP PTP PVES QB QoS N Network Address Port Translation Network Address Translation Network Control Protocol Next Business Day Network Management System Non Occupancy Period P Password Authentication Protocol Personal Computer Power Over Ethernet Point-to-point Protocol over Ethernet Point-to-multipoint Point-to-point ProximVision ES QuickBridge Quality of Service Q R RADIUS Remote Authentication Dial In User Service RAS RF RIP RMA RLT RSSI SHA SKU SNMP SNR SNTP SSH Remote Access Services Radio Frequency Routing Information Protocol Return Material Authorization Radio Link Test Received Signal Strength Indicator S Secure Hash Algorithm Stock Keeping Unit Simple Network Management Protocol Signal-to-noise Ratio Simple Network Time Protocol Secure Shell Tsunami 800 & 8000 Series - Software Management Guide 332 Abbreviations Secure Socket Layer Spanning Tree Protocol Subscriber Unit T Text Based Configuration Transmission Control Protocol Trivial File Transfer Protocol Temporal Key Integrity Protocol Transmit Power Control Tag Protocol Identifier Time to Live SSL STP SU TBC TCP TFTP TKIP TPC TPID TTL UDP UTP User Datagram Protocol Unshielded Twisted Pair VLAN Virtual Local Area Network U V W WEP WORP Wired Equivalent Privacy Wireless Outdoor Router Protocol Tsunami 800 & 8000 Series - Software Management Guide 333 Lightning Protection Lightning protection is used to maximize the reliability of the communications equipment by safely re-directing current from a lightning strike or a power surge traveling along the Cat 5/Cat5e/Cat 6 Ethernet cabling to the ground using the shortest path possible. Designing a proper grounding system prior to installing any communications equipment is critical to minimize the possibility of equipment damage, void warranties, and cause serious injury. The surge arrestor (sometimes referred to as a lightning protector) can protect your sensitive electronic equipment from high-voltage surges caused by discharges and transients at the PoE. Proxim Wireless offers superior lightning and surge protection for Tsunami series products. Contact your reseller or distributor for more information. Tsunami 800 & 8000 Series - Software Management Guide 334 Statement of Warranty Warranty Coverage Proxim Wireless Corporation warrants that its products are manufactured solely from new parts, conform substantially to specifications, and will be free of defects in material and workmanship for a Warranty Period of 1 year from the date of purchase. Repair or Replacement When Proxim determines that a returned product does not meet the warranted criteria during the warranty period, Proxim at its option, will either: (a) repair the defective product; (b) replace the defective product with a new or refurbished product that is at least equivalent to the original; or (c) refund the price paid for the defective product. Generally, products are repaired or replaced within thirty (30) business days of receipt of the product at a Proxim Logistical/Repair Center. The warranty period for repaired or replacement products is ninety (90) days or the remainder of the original warranty period, whichever is longer. These three alternatives constitute the customers sole and exclusive remedy and Proxims sole and exclusive liability under warranty provisions. Limitations of Warranty Proxims warranties do not apply to any product (hardware or software) which has (a) been subjected to abuse, misuse, neglect, accident, or mishandling, (b) been opened, repaired, modified, or altered by anyone other than Proxim, (c) been used for or subjected to applications, environments, or physical or electrical stress or conditions other than as intended and recommended by Proxim, (d) been improperly stored, transported, installed, or used, or (e) had its serial number or other identification markings altered or removed. Buyers can contact Proxim Wireless Customer Service Center either by telephone or via web. Support and repair of products that are out of warranty will be subject to a fee. Contact information is shown below. Additional support information can be Contact technical support via telephone as follows:
. Phone: +1-408-383-7700; +1-866-674-6626 Business Hours: 24x7 live response. Tier 3 support: 8 a.m. to 5 p.m. M-F PDT (UTC/GMT -7 hrs) Phone: +1-408-383-7700; 0800-916475 (France); 8-800-100-9485 (Russia) Business Hours: 24x7 live response. Tier 3 support: 8 a.m. to 5 p.m. M-F PDT (UTC/GMT -7 hrs) International Customers USA and Canada Customers found at Proxim Wirelesss web site at General Procedures When contacting the Customer Service for support, Buyer should be prepared to provide the product description and serial number and a description of the problem. The serial number should be on the product. In the event the Customer Service Center determines that the problem can be corrected with a software update, Buyer might be instructed to download the update from Proxim Wirelesss web site or, if thats not possible, the update will be sent to Buyer. In the event the Customer Service Center instructs Buyer to return the product to Proxim Wireless for repair or replacement, the Customer Service Center will provide Buyer a Return Material Authorization (RMA) number and shipping instructions. Buyer must return the defective product to Proxim Wireless, properly packaged to prevent damage, shipping prepaid, with the RMA number prominently displayed on the outside of the container. Tsunami 800 and 8000 Series - Software Management Guide 335 Statement of Warranty Calls to the Customer Service Center for reasons other than product failure will not be accepted unless Buyer has purchased a Proxim Wireless Service Contract or the call is made within the warranty period. After the warranty period, Technical Support If Proxim Wireless reasonably determines that a returned product is not defective or is not covered by the terms of this Warranty, Buyer shall be charged a service charge and return shipping charges. Search Knowledgebase Other Information Create a Support Request
). is fee based (detailed in Proxim Wireless stores all resolved problems in a solution database at the following URL:
. Submit a question or open an issue to Proxim Wireless technical support staff at the following URL:
. Tsunami 800 and 8000 Series - Software Management Guide 336 Technical Services and Support Obtaining Technical Service and Support If you are having trouble using the Proxim product, please read this guide and the additional documentation provided with your product. If you require additional support to resolve your issue, please be ready to provide the following information before you contact Proxims Technical Services team:
If the product is not registered, date and location where you purchased the product
: Technical Support is free for the warranty period from the date of purchase. Part number and serial number of the suspected faulty device Network information (What kind of network are you using?) Circumstances that preceded or led up to the error Support Options Proxim eService Web Site Support Product information Registration information Trouble/error information ServPak account number Message or alarms viewed Trouble/symptom being experienced Activities completed to confirm fault Steps taken to reproduce the problem ServPak information (if a Servpak customer):
The Proxim eService Web site is available 7x24x365 at On the Proxim eService Web Site, you can access the following services:
Product Download Page: Provides quick links to product firmware, software, and documentation downloads. Proxim TV Links: A link to helpful video tutorials. Knowledgebase: A solution database of all the resolved problems. You can search by product, category, keywords, or phrases. Live Chat: Chat with a support technician on-line or request to call back at a later time. Create a Support Request: Create a support request with our technical support staff who will reply to you by email. Case Management: Login to check the status of your support cases, update your personal profile, or access restricted information and features. Provide Feedback: Submit a suggestion, complaint, or other feedback about the support site and our products. Tsunami 800 and 8000 Series - Software Management Guide 337 Telephone Support Contact technical support via telephone as follows:
Technical Services and Support USA and Canada Customers Phone: +1-408-383-7700; +1-866-674-6626 Business Hours: 24x7 live response. Tier 3 support: 8 a.m. to 5 p.m. M-F PDT (UTC/GMT -7 hrs) International Customers Phone: +1-408-383-7700; 0800-916475 (France); 8-800-100-9485 (Russia) Business Hours: 24x7 live response. Tier 3 support: 8 a.m. to 5 p.m. M-F PDT (UTC/GMT -7 hrs) ServPak Support To provide even greater investment protection, Proxim Wireless offers a cost-effective support program called ServPak. ServPak is a program of enhanced service support options that can be purchased as a bundle or individually, tailored to meet your specific needs. Whether your requirement is round the clock technical support or advance replacement service, we are confident that the level of support provided in every service in our portfolio will exceed your expectations. All ServPak service bundles are sold as service contracts that provide coverage for specific products from 1 to 3 years. Servpak bundles are considered an upgrade to the standard product warranty and not an extension. 24x7 Basic Technical Support Basic Advanced Replacement
(Two business days/
International economy shipment service) Priority Advanced Replacement
(Next business day/
International priority shipment service) Priority Comprehensive Advance Replacement
(Next business day/
International priority shipment service) 8x7 Advanced Technical Support Software Maintenance Access to Knowledge Base 24x7 Advanced Technical 24x7 Advanced Technical Support Support PVES & PV NMS PVES & PV NMS Support Support Post-Installation Optimization 50% discount on Onsite Technical Support and Services Tsunami 800 and 8000 Series - Software Management Guide 338 Technical Services and Support Additional Information on ServPak Options Advanced Replacement of Hardware In the event of a hardware failure, our guaranteed turnaround time for return to factory repair is 30 days or less. Customers who purchase this service are guaranteed replacement of refurbished or new hardware to be shipped out within one or two business days, as applicable. Options are available for shipment services depending on the customers support needs. Hardware is shipped on business days, Monday Friday excluding Holidays, 8:00 AM 3:30 PM Eastern Time. Comprehensive Advanced Replacement of Hardware In addition to ServPak Prime options, in the event of a hardware failure, Proxim will repair or replace the failed product for any reason, other than vandalism. 7x24x365 Availability Unlimited, direct access to technical support engineers 24 hours a day, 7 days a week, 365 days a year including Holidays. 8x5 Availability Unlimited, direct access to world-class technical support engineers 8 hours a day, 5 days a week, Monday through Friday from 8:00AM - 5:00PM Pacific Standard Time. Basic Technical Support Customers who purchase this service can be rest assured that their call will be answered by Proxims Tier 1 technical support and a case opened immediately to document the problem and provide initial troubleshooting to identify the solution and resolve the incident in a timely manner. Advanced Technical Support In addition to Proxims world-class Tier 1 technical support, customers will be able to have their more complex issues escalated to our world-class Tier 3 technical support engineers. Our Tier 3 engineers will review specific configurations to troubleshoot intricate issues and will also provide helpful insights regarding Proxims products and various tips from decades of collective experience in the wireless industry. Software Maintenance It's important to maintain and enhance security and performance of wireless equipment and Proxim makes this easy by providing a Software Maintenance program that enables customers to access new feature and functionality rich software upgrades and updates. Customers will also have full access to Proxim's vast Knowledgebase of technical bulletins, white papers and troubleshooting documents. Post-Installation Optimization You can consult with our technical support engineers to enhance performance and efficiency of your network. Post-installation optimization services include:
Review frequencies to select best possible channel Review Modulation, Channel Bandwidth, MIMO, and WORP settings to optimize throughput and link quality Review Satellite Density & TPC/ATPC settings Assistance with Bandwidth controls Tsunami 800 and 8000 Series - Software Management Guide 339 Technical Services and Support To purchase ServPak support services, please contact your authorized Proxim distributor. To receive more information or for questions at our website options, support visit the of
) or send an All Customers are entitled to free technical support for the Proxim products they purchase from Proxims authorized resellers
) and/or via telephone. This technical support will be provided for free for the entire time the product is covered by a Proxim warranty. The term of Proxims warranty is determined according to the agreement under which the product was sold and generally varies from 3 months to 2 years depending on the product. If a Customer disagrees with Proxims determination of warranty duration, a request for review supported by a copy of all product purchase documentation may be submitted. After the warranty period, technical support on products then being sold by Proxim will be based upon one of the following three options Customers can choose:
Customers can choose to purchase one of Proxims ServPak extended warranty and enhanced support packages for the product Customers can choose to purchase one-time per-incident technical support for the product for a fee Customers can choose to call the reseller or distributor who sold them the product for technical support Technical Support Policy Technical Support for Current Products after Warranty Period Technical Support for Current Products during Warranty Period
. on any please ServPak available Assistance with QoS, RADIUS, and VLAN settings on Proxim equipment
, call Proxim Support (For telephone numbers, see email to or distributors. Technical Support is defined as communication via the Proxim Support website (
No EOL ServPak support package is available for certain discontinued products Tech Support on Discontinued Products Technical Support on some products that Proxim has declared as EOL (End of Life) or otherwise is no longer selling is available based upon one of the following three options Customers can choose:
For some discontinued products, Customers can choose to purchase one of Proxims EOL ServPak support packages for the product No EOL ServPak support package will be available for any product discontinued more than 5 years ago Customers can choose to purchase one-time per-incident technical support for the product on a per hour basis at a rate of $125 an hour (4 hours minimum payable in advance by major credit card). This fee is payable in addition to any RMA fee that may be charged to subsequently repair the product. Customers can choose to call the reseller or distributor who sold them the product for technical support All Proxim technical support for discontinued products, whether through an EOL ServPak package or otherwise, is provided on a best effort basis and is subject to the continued availability of necessary components, equipment, and other technical resources. Note that Proxim is unable to support or warrant any equipment that has been modified, whether this modification is physical, or if third-party software codes have been loaded onto the product. Tsunami 800 and 8000 Series - Software Management Guide 340
1 2 3 4 5 6 7 | user manual | Users Manual | 586.71 KiB | February 04 2014 |
Warning Statement FCC NOTICE This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. 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 the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:
Reorient or relocate the receiving antenna. Increase the separation between the equipment and receiver. Connect the equipment into an outlet on a circuit different from that to which the receiver is connected. Consult the dealer or an experienced radio/TV technician for help. FCC Compliance Statement: This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:
This device may not cause harmful interference, and This device must accept any interference received, including interference that may cause undesired operation. RF Exposure warning The equipment complies with FCC RF exposure limits set forth for an uncontrolled environment. This device and its antenna(s) must not be co-located with any other transmitters except in accordance with FCC multi-transmitter product procedures. Refering to the multi-transmitter policy, multiple-transmitter(s) and module(s) can be operated simultaneously without C2P. This device is going to be operated in 5.15~5.25GHz frequency range, it is restricted in indoor environment only. Devices will not permit operations on channels 120-132 for 11a and 11n/a which overlap the 5600 - 5650 MHz band. IMPORTANT NOTE:
This module is intended for OEM integrator. The OEM integrator is responsible for the compliance to all the rules that apply to the product into which this certified RF module is integrated. Additional testing and certification may be necessary when multiple modules are used. 20cm minimum distance has to be able to be maintained between the antenna and the users for the host this module is integrated into. Under such configuration, the FCC radiation exposure limits set forth for an population/uncontrolled environment can be satisfied. Any changes or modifications not expressly approved by the manufacturer could void the user's authority to operate this equipment. USERS MANUAL OF THE END PRODUCT:
In the users manual of the end product, the end user has to be informed to keep at least 20cm separation with the antenna while this end product is installed and operated. The end user has to be informed that the FCC radio-frequency exposure guidelines for an uncontrolled environment can be satisfied. The end user has to also be informed that any changes or modifications not expressly approved by the manufacturer could void the user's authority to operate this equipment. If the size of the end product is smaller than 8x10cm, then additional FCC part 15.19 statement is required to be available in the users manual: This device complies with Part 15 of FCC rules. 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. LABEL OF THE END PRODUCT:
The final end product must be labeled in a visible area with the following "
Contains TX FCC ID: HZB-XB92WFR ". If the size of the end product is larger than 8x10cm, then the following FCC part 15.19 statement has to also be available on the label: This device complies with Part 15 of FCC rules. 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. IC NOTICE This device complies with Industry Canada license-exempt RSS standard(s). Operation is subject to the following two conditions: (1) this device may not cause interference, and (2) this device must accept any interference, including interference that may cause undesired operation of the device. Le prsent appareil est conforme aux CNR d'Industrie Canada applicables aux appareils radio exempts de licence. L'exploitation est autorise aux deux conditions suivantes : (1) l'appareil ne doit pas produire de brouillage, et (2) l'utilisateur de l'appareil doit accepter tout brouillage radiolectrique subi, mme si le brouillage est susceptible d'en compromettre le fonctionnement. This device and its antenna(s) must not be co-located with any other transmitters except in accordance with IC multi-transmitter product procedures. Refering to the multi-transmitter policy, multiple-transmitter(s) and module(s) can be operated simultaneously without reassessment permissive change. Cet appareil et son antenne (s) ne doit pas tre co-localiss ou fonctionnement en association avec une autre antenne ou transmetteur. Dynamic Frequency Selection (DFS) for devices operating in the bands 5250- 5350 MHz, 5470-5600 MHz and 5650-5725 MHz Slection dynamique de frquences (DFS) pour les dispositifs fonctionnant dans les bandes 5250-5350 MHz, 5470-5600 MHz et 5650-5725 MHz The device for the band 5150-5250 MHz is only for indoor usage to reduce potential for harmful interference to co-channel mobile satellite systems. les dispositifs fonctionnant dans la bande 5150-5250 MHz sont rservs uniquement pour une utilisation lintrieur afin de rduire les risques de brouillage prjudiciable aux systmes de satellites mobiles utilisant les mmes canaux. The maximum antenna gain permitted (for devices in the bands 5250-5350 MHz and 5470-5725 MHz) to comply with the e.i.r.p. limit. le gain maximal dantenne permis pour les dispositifs utilisant les bandes 5250-5350 MHz et 5470-5725 MHz doit se conformer la limite de p.i.r.e. Users should also be advised that high-power radars are allocated as primary users (i.e. priority users) of the bands 5250-5350 MHz and 5650-5850 MHz and that these radars could cause interference and/or damage to LE-LAN devices. De plus, les utilisateurs devraient aussi tre aviss que les utilisateurs de radars de haute puissance sont dsigns utilisateurs principaux (c.--d., quils ont la priorit) pour les bandes 5250-5350 MHz et 5650-5850 MHz et que ces radars pourraient causer du brouillage et/ou des dommages aux dispositifs LAN-EL. IMPORTANT NOTE:
IC Radiation Exposure Statement:
This equipment complies with IC RSS-102 radiation exposure limits set forth for an uncontrolled environment. This equipment should be installed and operated with minimum distance 20cm between the radiator & your body. Cet quipement est conforme aux limites d'exposition aux rayonnements IC tablies pour un environnement non contrl. Cet quipement doit tre install et utilis avec un minimum de 20 cm de distance entre la source de rayonnement et votre corps. IMPORTANT NOTE:
This module is intended for OEM integrator. The OEM integrator is still responsible for the IC compliance requirement of the end product, which integrates this module. USERS MANUAL OF THE END PRODUCT:
In the users manual of the end product, the end user has to be informed to keep at least 20cm separation with the antenna while this end product is installed and operated. The end user has to be informed that the IC radio-frequency exposure guidelines for an uncontrolled environment can be satisfied. The end user has to also be informed that any changes or modifications not expressly approved by the manufacturer could void the user's authority to operate this equipment. IC statement is required to be available in the users manual: This Class B digital apparatus complies with Canadian ICES-003. 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. LABEL OF THE END PRODUCT:
The final end product must be labeled in a visible area with the following "
Contains TX IC : 1856A-XB92WFR ". This radio transmitter (identify the device by certification number, or model number if Category II) has been approved by Industry Canada to operate with the antenna types listed below with the maximum permissible gain and required antenna impedance for each antenna type indicated. Antenna types not included in this list, having a gain greater than the maximum gain indicated for that type, are strictly prohibited for use with this device. Le prsent metteur radio (identifier le dispositif par son numro de certification ou son numro de modle s'il fait partie du matriel de catgorie I) a t approuv par Industrie Canada pour fonctionner avec les types d'antenne numrs ci-dessous et ayant un gain admissible maximal et l'impdance requise pour chaque type d'antenne. Les types d'antenne non inclus dans cette liste, ou dont le gain est suprieur au gain maximal indiqu, sont strictement interdits pour l'exploitation de l'metteur. Antenna list:
Ant. 1 2 3 4 Brand MARS MARS MARS Grand-Tek Model No. MA-WA55-30 MA-WB55-20 MA-WO55-10NH GTT-AC-05-001 Type Panel Sector Omni Panel Connector N Type N Type N Type MMCX type Ant. Gain (dBi) Cable Loss (dB) Ant. 5850-5925 MHz 29 20 10 16 1 2 3 4 Band1&4 30 20 10 16 5850-5925 Band1&
MHz 2 2 2 0 4 2 2 2 0 Attenuator
(dB) 12 10 0 0 Test Gain (dBi) 5850-5925 MHz 15 8 8 16 Band1&4 16 8 8 16 This device complies with the Electromagnetic Compatibility Directive
(89/336/EEC) issued by the Commission of the European Community. Compliance with this directive implies conformity to the following European Norms
(in brackets are the equivalent international standards.) Electromagnetic Interference (Conduction and Radiation): EN 55022 (CISPR 22) Electromagnetic Immunity: EN 55024 (IEC61000-4-2, 3, 4, 5, 6, 8, 11) Low Voltage Directive: EN 60 950: 1992+A1: 1993+A2: 1993+A3: 1995+A4:
1996+A11: 1997. CE Mark: following the provisions of the EC directive. The wireless card in this product complies with the R&TTE Directive (1999/5/EC) issued by the Commission of the European Community. Compliance with this directive implies conformity to the following:
EMC Standards: FCC: 47 CFR Part 15, Subpart B, 47 CFR Part 15, Subpart C
(Section 15.247); CE:
EN 300 328-2, EN 300 826 (EN 301 489-17) CE Mark: following the provisions of the EC directive. Manual Version: 2.08c (June 2010) This manual is written based on Firmware version 2.00 Overview the Product Introduction The high-performance Wireless Network Access Point (AP) is designed for enterprise and public access applications. Embedded with the Atheros chipset, it boasts network robustness, stability and wider network coverage. Based on 802.11n (Draft 2.0), the access point supports high-speed data transmission of up to 300Mbps. The access point is capable of operating in different modes, which makes it suitable for a wide variety of wirelessapplications, including long-distance deployments. Designed with dual polarization high gain antenna it offers a compact, rugged design for outdoor installation and excellent performance. Moreover, its integrated Power over Ethernet (PoE) allows the access point to be used in areas where power outlets are not readily available. To protect your security and privacy, the access point is armed with many enhanced and latest wireless security features such as IEEE 802.11i standards, MAC Address Filtering, IEEE 802.1x Authentication and 64/128-bit WEP (Wired Equivalent Privacy) to ensure privacy for the heterogeneous mix of users within the same wireless network. The access point also incorporates a unique set of advanced features such as:
Virtual AP to deliver multiple services; Long-Range parameter fine-tuning which provide the access point with the ability to auto-calculate parameters such as slot time, ACK time-out and CTS time-out to achieve a longer range. Features and Benefits Point-to-Point & Point-to-MultiPoint Support Point-to-Point and Point-to-MultiPoint communication between different buildings enables you to bridge wireless clients that are kilometres apart while unifying the networks. Virtual AP (Multiple SSID) Virtual AP implements mSSID (Multi-SSID) This allows a single wireless card to be set up with multiple virtual AP connections with different SSIDs or BSSID
(Basic Service Set Identifier) and security modes. Highly Secured Wireless Network The access point supports the highest available wireless securitystandard:
IEEE802.11i compliant. The access point also supports IEEE 802.1x for secure and centralized user-based authentication. Wireless clients are thus required to authenticate through highly secure methods like EAP-TTLS and EAP-PEAP, in order to obtain access to the network. uConfig Utility The exclusive uConfig utility allows users to access the user-friendly Web configuration interface of the access point without having to change the TCP/IP setup of the workstation. HTTPS The access point supports HTTPS (SSL) in addition to the standard HTTP. HTTPS (SSL) features additional authentication and encryption for secure communication. Telnet Telnet allows a computer to remotely connect to the access point CLI
(Command Line Interface) for control and monitoring. SSH SSH (Secure Shell Host) establishes a secure host connection to the access point CLI for control and monitoring. Operation Modes and Connection Examples Access Point and Access Point WDS Mode The Access Point Mode is the default mode of the device. It enables the bridging of wireless clients to wired network infrastructure and enables transparent access and communication with each other. The illustration below shows a typical resources sharing application example using this device. The wireless users are able to access the file server connected to the switch, through the access point in Access Point Mode. Access Point WDS Mode This is mode is generally use for point-to-point or point-to-multi-point connection. It is mainly use with Station WDS to build the point and multi-point connections. Station Mode In Station mode the device acts as a wireless client. When connected to an access point, it creates a network link between the Ethernet network connected at this client device, and the wireless Ethernet network connected at the access point. In this example the workgroup PCs on the ethernet network connected to the Station device can access the printer across the wireless connection to the access point where the printer is connected. Station WDS Mode Station WDS mode is similar to Station mode. The difference is Station WDS must connect to access point configured to Access Point WDS (or RootAP) mode. Station WDS is mainly use for point-topoint connection between 2 buildings or locations as far as several kilometer away. Router Mode In Router Mode, the device also operates as a router. Either the wireless or Ethernet can be setup as WAN connection to a broadband modem. Wireless as WAN is known as Station + Router mode (or Wireless Routing Client mode) and Ethernet as WAN is known as AP + Router mode(or Gateway mode). Device supports several types of broadband connections Static IP, Dynamic IP and PPPoE. For setup details refer to the respective section. The illustration below shows the Ethernet port is setup as the WAN port and the wireless connection as the LAN. Broadband Internet Access Type:
Static IP Address Use Static IP Address you have subscribed a fixed IP or range IP addresses from your ISP. Dynamic IP Address With Dynamic IP Address the device automatically request IP address from modem or ISP. PPP over Ethernet (PPPoE) When using ADSL services provided byyour ISP support PPPoE connection. Repeater WDS Mode Repeater WDS Mode to mainly to extend the wireless range and coverage of the wireless network allowing access and communications over places generally difficult for wireless clients to connect to the network. In Repeater mode, the access point acts as a relay for network signals on the network by regenerating the signals it receives, and retransmitting them to main network infrastructure. Detailed information on the Repeater mode is available in the Repeater Setup section. Install the Hardware This section will show you how to install the hardware of the access point. Antenna Alignment The antenna alignment of the access point must first be considered to ensure that the signal is strong. Installation Direction After considering the antenna alignment, the direction in which the access point is facing must be considered to ensure that the signal is actually being directed to the receiving end. Setting Up Lastly, after making these considerations and confirming the final position and facing direction of the access point, follow the instructions to physically set up and complete the installation of the access point Setup Requirements CAT5/5e Networking Cable. At least 1 computer installed with a web browser and a wired or wireless network interface adapter. All network nodes installed with TCP/IP and properly configured IP address parameters. Mount the Unit on a Pole Access point is designed to mount to a pole. The mounting method will be described as shown below. Note the following guidelines for choosing the best location for your wireless AP:
Place the AP as close as possible tothe area where users will require access to the WLAN. Choose an elevated location where trees, buildings and large steel structures will not obstruct the antenna signals and which offers maximum line-of-sight propagation with the users. Select an appropriate antenna to improve range and/or coverage and the access point also lets you fine-tune parameters such as the transmit power to achieve the best results
1 2 3 4 5 6 7 | EUT photo | External Photos | 285.22 KiB | / August 10 2014 |
Photographs of EUT Report No.:342910-07 SPORTON International Inc. TEL : 886-3-327-3456 FAX : 886-3-327-0973 PAGE NUMBER : 1 OF 3 ISSUED DATE
: Aug. 29, 2014 Report No.:342910-07 SPORTON International Inc. TEL : 886-3-327-3456 FAX : 886-3-327-0973 PAGE NUMBER : 2 OF 3 ISSUED DATE
: Aug. 29, 2014 Report No.:342910-07 SPORTON International Inc. TEL : 886-3-327-3456 FAX : 886-3-327-0973 PAGE NUMBER : 3 OF 3 ISSUED DATE
: Aug. 29, 2014
1 2 3 4 5 6 7 | antenna photo | External Photos | 459.31 KiB | / August 10 2014 |
Photographs of EUT Ant. 1 Model No. MA-WA55-30 Report No.:342910-07 SPORTON International Inc. TEL : 886-3-327-3456 FAX : 886-3-327-0973 PAGE NUMBER : 1 OF 8 ISSUED DATE
: Aug. 29, 2014 Report No.:342910-07 SPORTON International Inc. TEL : 886-3-327-3456 FAX : 886-3-327-0973 PAGE NUMBER : 2 OF 8 ISSUED DATE
: Aug. 29, 2014 Report No.:342910-07 Ant. 2 Model No. MA-WB55-20 SPORTON International Inc. TEL : 886-3-327-3456 FAX : 886-3-327-0973 PAGE NUMBER : 3 OF 8 ISSUED DATE
: Aug. 29, 2014 Report No.:342910-07 SPORTON International Inc. TEL : 886-3-327-3456 FAX : 886-3-327-0973 PAGE NUMBER : 4 OF 8 ISSUED DATE
: Aug. 29, 2014 Report No.:342910-07 SPORTON International Inc. TEL : 886-3-327-3456 FAX : 886-3-327-0973 PAGE NUMBER : 5 OF 8 ISSUED DATE
: Aug. 29, 2014 Report No.:342910-07 Ant. 3 Model No. SAA08-220570 SPORTON International Inc. TEL : 886-3-327-3456 FAX : 886-3-327-0973 PAGE NUMBER : 6 OF 8 ISSUED DATE
: Aug. 29, 2014 Report No.:342910-07 Ant. 4 Model No. GTT-AC-05-001 SPORTON International Inc. TEL : 886-3-327-3456 FAX : 886-3-327-0973 PAGE NUMBER : 7 OF 8 ISSUED DATE
: Aug. 29, 2014 Report No.:342910-07 SPORTON International Inc. TEL : 886-3-327-3456 FAX : 886-3-327-0973 PAGE NUMBER : 8 OF 8 ISSUED DATE
: Aug. 29, 2014
1 2 3 4 5 6 7 | Antenna list of max gain | Parts List/Tune Up Info | 5.95 KiB | May 06 2014 / August 10 2014 |
Ant 1 2 3 4 Brand MARS MARS MARS Model MA-WA55-30 MA-WA55-30 MA-WO55-10NH Grand-tek GTT-AC-05-001 Type Panel Sector Omni Panel Ant. Gain cable loss attenuator testing gain 30 20 10 16 2 2 2 2 12 10
-
-
16 8 8 16
1 2 3 4 5 6 7 | C2PC letter | Cover Letter(s) | 25.40 KiB | May 06 2014 / August 10 2014 |
Request for Permissive Change Date: 2014/6/3 To: Federal Communications Commission, Authorization and Evaluation Division Subject: Class II Permissive Change Under new UNII rule from R&O 14-30A1 FCC ID: HZB-XB92WFR With the recent release of R&O 14-30A1 allowing higher power in the UNII 1 band we, the undersigned, Proxim Wireless Corporation, would like to apply for a Class II Permissive Change for FCC ID: HZB-XB92WFR to allow higher power operation under the R&O for our existing equipment in UNII Band 1under this ID. There have been no hardware changes to the equipment covered under this grant. We propose to allow customers to upgrade the software in the field implementing operation in the UNII 1 band and complying with the new R&O requirements. In support of this application for a Class II permissive change, we include the following:
Our FCC ID demonstrating compliance with 15.407 in the UNII 1 band under the old rules. Document FCC KDB 594280 D02 UNII Device Security v01- Proxim Response.pdf in accordance with guidance from KDB 594280 D02 UNII Device Security v01, stating how we secure our software such that it cannot be changed outside regulatory limitations. Our HW installation guide, Hardware Installation Guide.pdf and an excerpt from that guide titled FCC- Antenna Tilt Angles & corresponding EIRP value .pdf demonstrating how this equipment complies with the EIRP limitation of 125mw above 30 degrees as measured from the horizon. For the detail of antennas, please reference to Antenna-List.pdf We further attest per document KDB 594280 D02 UNII Device Security v01, that the equipment as granted under FCC ID HZB-XB92WFR when operated in a bridge mode (the equipment does not support mesh) complies with UNII 1 rules contained in KDB Publication 905462 D02 for Fixed outdoor applications. FCC Grantee contact person information:
Applicants company name
: Proxim Wireless Corporation Applicants company address Signature
: 1561 Buckeye Drive, Milpitas CA 95035 USA
:
_____________________________ Job Title and Dept.
: Cor van de Water /Chief Scientist E-Mail Tel.
: cwater@proxim.com
: 408 383 7626
1 2 3 4 5 6 7 | Confidential Letter Revised | Cover Letter(s) | 16.21 KiB | / August 10 2014 |
Proxim Wireless Corporation 1561 Buckeye Drive, Milpitas CA 95035 USA Tel: 408 383 7600 / Fax: 408 383 7680 Confidential Letter Date: 2014/08/21 Federal Communications Commission Authorization and Evaluation Division FCC ID HZB-XB92WFR Confidentiality Request Pursuant to Reference Section 0.457 (d) and 0.459 of the FCC Rules, the applicant hereby request confidential treatment of information accomparting this Application as outlined below:
1. Software Security Request The above materials contain trade secrets and proprietary information not customarily released to the public. The public disclosure of these matters might be harmful to the Applicant and provide unjustified benefits to its competitors. Sincerely, Applicants company name Applicants company address Signature
: Proxim Wireless Corporation
: 1561 Buckeye Drive, Milpitas CA 95035 USA
:
_____________________________ Job Title and Dept.
: Cor van de Water / Sr. Regulatory and Compliance Manager E-Mail Tel.
: cwater@proxim.com
: 408 383 7600
1 2 3 4 5 6 7 | EIRP compliance declaration revised2 | Attestation Statements | 2.07 MiB | April 09 2014 / August 10 2014 |
Device installation report for FCC U-NII-1 band (5.15- 5.25GHz) compliance The Federal Communications Commission (FCC) established new rules for the 5.15 5.25 GHz U-NII-1 band in the Report and Order FCC-14-30A1, which would be effective from 2nd June, 2014. With the help of professional installation, all the Proxim devices can be configured to comply with the power requirements set in the rules. For an angle of elevation which is above 30 degrees, the maximum EIRP limit should be set to 125mW (21 dBm). The compliance can be achieved through proper selection of antenna, angle of installation, and Tx power control. The appropriate selection of these parameters avoids the transmission interference between the authorized devices of the users and also in the co-channel NGSO/MSS operations. Proxim devices such as BSUs (Base Station Units)/ SUs (Subscriber Units) are installed by professional installers to work in fixed outdoor configurations. These devices are in general mounted on a tower, roof, or at a place above the street level;
therefore, it implies that all Proxim devices whether they have an external antenna or an integrated antenna support vertical alignment to achieve downward tilt. All devices support TPC (Transmit Power Control) configuration with a range of (0 21dB*) that allows professional installers to lower the power when necessary. Note: * Transmit power control varies with the product type and specific modulation. The antenna/devices located at different altitudes should be tilted at the correct angle to transmit/receive the signals effectively; thus, it optimizes the transmission and reception of signals between the devices in the wireless network. The Figure 1.1 below shows the antenna tilt and its importance when the successive devices are at different elevations above the ground. Fig 1.1 Typical installation showing device/antenna tilt angle FCC ID HZB-PROXMB82 HZB-XB92WFR HZB-XB92WLE HZB-MB83HP5 Device Models MP-8100-BSU MP-8100-SUA MP-8150-SUR MP-8150-SUR-100 QB-8100-EPA/LNK QB-8150-EPR/LNK QB-8150-LNK-100 QB-8151-EPR/LNK MP-8150-CPE QB-8150-LNK-12/50 MP-820-BSU-100 MP-825-BS3-100 MP-820-SUA-50+
MP-820-SUA-100 MP-825-SUR-50+
MP-825-SUR-100 MP-825-CPE-50 MP-825-CPE-100 QB-825-EPR / LNK-50+
QB-825-EPR / LNK-50 MP-8200-BSU MP-8250-BS9 MP-8250-BS1 MP-8200-SUA MP-8250-SUR QB-8200-EPA / LNK QB-8250-EPR / LNK Table 1: FCC IDs for Proxim Products Maximum EIRP at any elevation angle greater than 300 1. FCC ID: HZB-PROXMB82 Antenna Model No: MA-WA55-30 Gain: 30dBi Antenna Type: Panel Antenna, Linear Polarization (Vertical or Horizontal), 50 Bandwidth Table 2: Maximum EIRP values at an angle greater than 30 deg for the Antenna model "MA-WA55-30"
with FCC ID HZB-PROXMB82 Figure 1: Radiation pattern for the Antenna Model "MA-WA55-30, E-plane"
Figure 2: Radiation pattern for the Antenna Model "MA-WA55-30, H-plane"
Antenna Model No: MA-WB55-20 Gain: 20dBi Antenna Type: Sector Antenna, Linear Polarization (Vertical) Table 3: Maximum EIRP values at an angle greater than 30 deg for the Antenna Model "MA-WB55-20 with FCC ID HZB-PROXMB82 Figure 3: Radiation pattern for the Antenna Model "MA-WB55-30, E-plane"
Figure 4: Radiation pattern for the Antenna Model "MA-WB55-20, H-plane"
Antenna Model No: SAA08-220570 Gain: 10dBi Antenna Type: Omni Antenna Table 4: Maximum EIRP values at an angle greater than 30 deg for the Antenna Model "SAA08-220570 with the FCC ID HZB-PROXMB82 2. FCC ID: HZB-XB92WFR Antenna Model No: MA-WA55-30 Gain: 30dBi Antenna Type: Panel Antenna, Linear Polarization (Vertical or Horizontal), 50 Bandwidth Table 5: Maximum EIRP values at an angle greater than 30 deg for the Antenna Model "MA-WA55-30 with the FCC ID HZB-XB92WFR Antenna Model No: MA-WB55-20 Gain: 20dBi Antenna Type: Sector Antenna, Linear Polarization (Vertical) Table 6: Maximum EIRP values at an angle greater than 30 deg for the Antenna Model "MA-WB55-20 with the FCC ID HZB-XB92WFR Antenna Model No: SAA08- 220570 Gain: 10dBi Antenna Type: Omni Antenna Table 7: Maximum EIRP values at an angle greater than 30 deg for the Antenna Model "SAA08-220570 with the FCC ID HZB-XB92WFR Antenna Model No: GTT-AC-05-001 Gain: 16dBi Antenna Type: Panel Antenna Table 8: Maximum EIRP values at an angle greater than 30 deg for the Antenna Model "GTT-AC-05-001 with the FCC ID HZB-XB92WFR Radiation Patterns for GTT-AC-05-001 Model Antenna 3. FCC ID: HZB-XB92WLE Antenna Model No: MA-WA55-30 Gain: 30dBi Antenna Type: Panel Antenna, Linear Polarization (Vertical or Horizontal), 50 Bandwidth Table 9: Maximum EIRP values at an angle greater than 30 deg for the Antenna Model "MA-WA55-30 with the FCC ID HZB-XB92WLE Antenna Model No: MA-WB55-20 Gain: 20dBi Antenna Type: Sector Antenna, Linear Polarization (Vertical) Table 10: Maximum EIRP values at an angle greater than 30 deg for the Antenna Model "MA-WB55-20 with the FCC ID HZB-XB92WLE Antenna Model No: SAA08-220570 Gain: 10dBi Antenna Type: Omni Antenna Table 11: Maximum EIRP values at an angle greater than 30 deg for the Antenna Model "SAA08-220570 with the FCC ID HZB-XB92WLE Antenna Model No: GTT-AC-05-001 Gain: 16dBi Antenna Type: Panel Antenna Table 12: Maximum EIRP values at an angle greater than 30 deg for the Antenna Model "GTT-AC-05-001 with the FCC ID HZB-XB92WLE 4. FCC ID: HZB-MB83HP5 Antenna Model No: MA-WA55-30 Gain: 30dBi Antenna Type: Panel Antenna, Linear Polarization (Vertical or Horizontal), 50 Bandwidth Table 13: Maximum EIRP values at an angle greater than 30 deg for the Antenna Model "MA-WA55-30 with the FCC ID HZB-MB83HP5 Antenna Model No: MA-WB55-20 Gain: 20dBi Antenna Type: Sector Antenna, Linear Polarization (Vertical) Table 14: Maximum EIRP values at an angle greater than 30 deg for the Antenna Model "MA-WB55-20 with the FCC ID HZB-MB83HP5 Antenna Model No: SAA08-220570 Gain: 10dBi Antenna Type: Omni Antenna Table 15: Maximum EIRP values at an angle greater than 30 deg for the Antenna Model "SAA08-220570 with the FCC ID HZB-MB83HP5 Antenna Model No: PX3F-52-N7A Gain: 34dBi Antenna Type: Dish Antenna Figure 5: Radiation pattern for the Antenna Model "PX3F-52-N7A Antenna Model No: MA-WA56-DP25N Gain: 23.5dBi Antenna Type: Panel Antenna Figure 6: Radiation patterns for the Antenna Model "MA-WA56-DP25N"
Antenna Model No: MA-WD56-DP16 Gain: 16dBi Antenna Type: Sector Antenna Figure 7: Radiation patterns for the Antenna Model "MA-WD56-DP16"
1 2 3 4 5 6 7 | antenna pattern of GTT-AC-05-001 | Parts List/Tune Up Info | 22.15 KiB | January 09 2014 / August 10 2014 |
-8.30575
-8.30088
-8.4948
-8.33439
-9.67527
-9.3989
-3.66503
-5.09716
-4.75185
-5.6282
-6.86435
-6.8629
-9.21114 Theta (deg)5150 MHz 5350 MHz 5500 MHz 5700 MHz 5875 MHz
-2.688
-6.8332
-180
-9.35649
-3.61699
-6.788
-179 -11.13584
-3.89142
-6.47159
-10.1377
-178
-4.06342
-6.68892
-9.71206
-177
-4.16833
-9.22062
-176
-8.97612
-5.52636
-9.44769
-175 -11.70189
-174 -11.15246 -10.57187 -10.07115
-7.83928
-173 -12.94278 -12.96423 -13.34922 -11.19372 -11.35274
-172 -11.01193 -13.09787 -13.17578
-13.6922 -14.55783
-171 -11.43323 -16.31904 -19.47978 -15.58352 -14.46304
-170 -13.59871 -16.41508 -20.69918 -32.03392 -26.83639
-169 -13.83771 -14.56489 -21.55804 -27.06233 -19.63839
-168 -13.69667 -15.64478 -17.22104 -29.95062 -16.23636
-167 -14.03863 -12.70466 -13.80017 -16.83471 -16.67466
-166 -13.77878 -14.86361 -12.53363 -12.97356 -14.93232
-165 -12.67986 -12.89556 -11.92592 -11.96021 -15.79564
-164 -13.25604 -13.12475 -11.00744 -11.34269 -12.58918
-163 -12.94161 -13.71486 -13.00313 -10.78994 -10.42282
-162 -12.63135 -10.34915 -10.00387 -10.46756 -10.19621
-9.73948 -11.10795 -12.28617
-161 -13.41792 -10.86754
-9.07225
-160 -13.06894 -10.47719
-10.8595 -12.47512
-159 -11.97767
-9.55208
-11.2579 -12.92049 -17.31632
-158 -10.81681 -11.42438 -12.22775 -13.72179 -21.86273
-11.6286 -12.45271 -15.11123
-157 -11.77137 -12.65092
-156
-11.3721 -12.98498
-11.3157 -15.02971
-21.9118
-155 -10.98895 -12.04135 -11.89043 -14.94718 -23.24364
-154 -10.78114 -13.40921 -15.61814 -11.21717 -16.63387
-153 -11.88998 -14.06218 -14.81861 -12.22062
-11.1645
-152 -13.63039 -16.85105 -12.14714 -10.88775 -15.43328
-151 -13.20794 -16.37273 -13.80496 -10.34011
-9.85653
-7.88839
-9.25321
-150 -14.26484 -17.80653 -12.32174
-9.11921
-8.73593
-149 -14.58664 -17.27933 -11.42186
-7.2556
-8.35416
-148 -13.99923 -18.89893 -11.72873
-9.0092
-7.93264
-147 -15.25868 -18.83168 -11.33249
-146 -18.42545 -18.07817 -11.47832
-8.94611
-8.62566
-7.89849
-145 -16.85171 -15.51701
-7.08977
-10.1751
-8.92443 -10.18722
-144
-16.9786 -16.95743 -12.04966
-8.63209 -10.06345
-143 -17.48363 -17.80378 -10.03899
-142 -17.31482 -12.15741
-9.99559
-8.92555
-141 -17.46987 -12.64541 -10.88162
-9.33461 -12.04137
-140 -20.90452 -15.83907 -11.21216 -10.69679 -10.83367
-139 -20.31704 -16.32701 -11.50869 -10.94796 -16.86754
-138 -20.90426 -20.00582 -11.21934 -13.31562 -14.10958
-137 -19.91105 -15.29153 -11.99934 -12.13717 -15.67827
-136 -18.52832 -17.14918 -15.81723 -15.49033
-20.3381
-135 -38.00156
-17.857 -14.72481 -18.82451 -16.14769
-134 -22.97763 -19.80628 -16.91774 -23.11439 -18.15203
-133 -26.49298 -24.71935 -19.73464 -16.37719 -15.33563
-132 -23.74286 -19.91814 -22.55256 -17.76719 -13.88803
-131 -33.15542
-27.806 -25.92711 -15.33562 -13.03708
-130 -23.69625 -26.37215
-18.1624 -16.19229 -19.71064
-129 -28.76657 -22.52261 -18.15445 -14.85317 -13.07581
-128 -23.01645 -30.55075 -15.04766 -14.01134 -16.67564
-9.4701
-15.8865
-13.8537 -20.42866 -20.93999
-127 -23.36473 -21.66709 -20.86325 -15.58598 -13.26388
-126 -25.05546 -24.64258 -19.04231 -13.54471 -13.58773
-125 -20.05149 -24.66151 -15.80752 -15.48999 -15.40388
-124 -30.18618 -22.55096 -20.40126 -15.69095 -19.17858
-123 -29.03894 -24.07457 -18.14143
-19.1585
-122 -27.60272 -26.75103 -24.86034 -17.04116 -16.34852
-121 -25.08311 -17.48579 -21.39335 -18.41173 -17.00036
-120 -22.52855 -17.29632 -16.35354 -15.93535
-16.7789
-119 -18.08357 -19.44597 -17.13035 -18.65445 -19.08792
-118 -19.91461 -19.94021 -16.16157 -16.79827 -18.76541
-117 -16.41819 -17.35737 -24.28782 -18.49167 -17.42914
-116 -19.17363 -14.30142 -19.22092
-23.4834 -23.30219
-115 -15.90368 -15.84923 -18.25678 -23.68297 -21.19943
-23.5563 -22.44534
-114 -18.71734 -14.17556 -16.55249
-113 -16.17438
-21.1452
-112 -14.84661 -14.66509 -18.08881 -29.44478 -20.56256
-111 -13.66608 -12.54258 -16.94141 -21.22461 -20.74766
-110 -12.95435 -13.79085 -16.60856 -21.09539 -19.43771
-109 -12.46411 -12.85897
-14.7134 -21.78292 -18.83551
-108 -11.94227 -10.71512 -15.41239 -14.96277 -14.85149
-107 -12.75611 -12.73443 -15.56218 -15.62899 -15.20888
-17.0625
-106 -11.45807 -12.86831 -15.62875 -16.20038
-105 -11.80021 -11.03354 -14.26683
-14.8122
-15.1945
-104 -12.85293 -10.89565 -12.90057 -13.97606 -12.72514
-103
-10.9282 -13.29581 -13.94271 -14.56924 -15.82144
-102 -11.30088 -13.21226 -12.64373 -13.41836 -12.60253
-101 -10.78843 -12.60352 -10.67915 -12.88025
-14.0383
-14.397 -14.06897
-100 -11.32361 -12.26026 -10.96562
-8.90781 -11.43539 -12.56993
-99
-98 -12.59875 -10.94078 -10.41404 -10.58127 -14.28981
-9.32045 -10.19258 -15.58071
-97 -11.18959 -13.24574
-9.96981 -10.12373 -15.10826
-96 -12.20253 -11.85728
-95 -15.26644 -11.98392
-8.96869 -10.73078 -14.88026
-9.17657 -11.19297 -16.57954
-94
-11.652 -12.24254
-8.96499 -12.55618
-93 -12.84877 -11.47458
-8.94127
-9.09105 -16.00766
-92 -13.15072 -10.22877 -10.30267
-8.09191
-91 -12.29026 -10.77723
-9.9576 -11.88301
-90 -12.96685
-9.44147
-8.76502
-9.84806 -15.37313
-7.04805 -10.89763 -13.65396
-89 -10.73983
-9.59614
-9.12878
-88 -11.87749 -10.51106
-9.2035 -13.27339
-8.48835 -11.40058 -14.60182
-87 -12.84344 -10.00133
-86 -11.88884
-9.6464
-8.35774
-8.56868 -12.03021
-7.45961 -11.72551
-8.41703
-85 -13.53598 -10.67499
-6.85933
-84 -14.36181
-9.96745
-12.0399
-8.25256 -11.35335
-8.23254
-83 -13.21773 -10.34234
-82 -12.36938 -10.57419
-7.04338
-8.99575 -10.73287
-8.99564
-7.96656
-7.95078
-81 -12.71996 -11.50708
-8.23031
-7.40686
-80 -14.48497 -12.22995
-8.63897
-7.66159 -10.84807
-9.2679
-79 -13.91093 -12.97429
-78 -15.94786 -12.91934
-8.50808
-7.59404
-8.27471
-7.12223 -10.24681
-9.28112
-77
-14.6157 -12.18713
-9.09907
-7.98926
-8.4864
-76 -14.93091 -13.88528
-9.11071
-7.95575
-8.05676
-75 -14.60976
-11.9405
-74 -13.58496
-16.6703
-8.87259
-6.7885
-7.46015
-8.0483
-8.34039
-9.01698
-73 -13.54005 -16.81916
-72 -14.82228 -17.58571
-10.378
-7.53795
-7.67907
-13.4747 -13.02083
-8.7956
-6.9845 -13.83555
-9.91472 -18.25944 -10.92985
-8.70315
-17.5004 -11.33565
-8.74793
-71 -12.95882 -22.30292
-70 -13.62226 -24.59654
-9.21896
-69 -12.37185 -28.37968 -10.21282
-68 -11.03123 -22.45161
-9.1707
-9.34199 -19.15113 -12.88738
-67
-9.17707 -21.45897 -12.67004
-66
-9.27043 -15.16581 -16.79073
-65
-7.41069
-64
-16.1521 -17.14164
-63
-6.62723 -13.27978 -19.12184
-7.50101
-62
-8.5137 -18.57238
-5.54552
-61
-5.61153
-60
-59
-4.12569
-3.74589
-58
-3.56772
-57
-3.02679
-56
-55
-2.58023
-1.87551
-54
-1.72735
-53
-1.5521
-52
-51
-1.33192
-1.05087
-50
-1.01045
-49
-1.25256
-48
-47
-1.11561
-1.01919
-46
-1.06583
-45
-1.50783
-44
-43
-1.95586
-2.85435
-42
-3.13999
-41
-3.41311
-40
-39
-4.029
-4.72224
-38
-5.32238
-37
-4.49563
-36
-4.36301
-35
-34
-3.93204
-3.22911
-33
-2.93816
-32
-1.86163
-31
-30
-1.53888
-1.40572
-29
-1.08683
-28
-0.93556
-27
-26
-0.95056
-1.39738
-25
-2.05412
-24
-2.6263
-23
-22
-4.06874
-5.76123
-21
-7.74501
-20
-8.75623
-19
-18
-6.61805
-3.71855
-17
-16
-0.41785
-7.37809
-8.01653
-7.31901
-7.431
-7.31043
-7.20742
-7.95972
-7.91123
-8.23889
-8.91237
-9.19664
-8.11
-7.56917
-9.95427
-8.89321
-9.5289
-9.89458
-8.85378
-10.0023 -10.02436
-9.68721
-9.86813
-11.9069 -11.12352
-6.53991 -12.29963 -12.43562 -10.37861
-9.5106 -11.02352
-6.09981 -12.13968
-9.79811 -10.92621
-9.03557
-7.42407
-7.00322 -11.09838
-6.95392 -10.15914
-6.22052
-7.44199
-7.37276
-4.93571
-7.6733
-5.09792
-4.06181
-3.29471
-4.36252
-7.47699
-4.78626
-3.11193
-2.71769
-3.82942
-2.00573
-2.60017
-3.7309
-1.76832
-1.77039
-1.39576
-1.39234
-2.28853
-1.29788
-0.72311
-0.95932
-1.18037
-0.68606
-1.12759
-0.71659
-1.04299
-0.77139
-0.48052
-0.32018 0.01082
-0.06498
-0.31502
-1.1084
-0.17713
-1.22506
-1.01302
-0.46429
-0.99212
-1.53209
-1.57608
-1.81842
-0.79184
-1.04416
-2.44667
-2.17685
-2.05292
-3.09609
-3.54266
-2.23771
-3.52473
-2.49129
-3.94889
-4.71474
-3.18264
-3.18684
-5.14666
-5.09173
-5.82567
-3.51481
-7.84594
-5.52498 -10.44227
-2.92819
-4.87843 -16.64996
-2.45908
-1.15513
-4.72044
-10.7136
-9.65071
-3.02282
-0.39103
-8.20523
-1.30056 0.16827
-4.8814
-1.22679 1.00348 1.26652 0.04341
-4.11267
-2.85021 0.11148 1.49021
-2.13354 0.52118 1.86065
-2.80674 0.79956 1.3089 1.02384 0.40403
-2.9717
-3.77898
-0.35077 0.73744
-3.99383
-0.95935 0.00633
-3.49741
-1.57927
-7.00506
-2.7826
-5.52282 -11.19855
-4.83759 -10.73875
-13.2259
-5.07219 -16.14456 -10.09637
-4.4185
-3.89671
-3.0755
-2.71779
-1.99325
-2.21098
-1.54441
-0.45735
-0.45271
-0.27337 0.03787
-0.69976
-0.47486
-0.69035
-0.65909
-1.49884
-1.68946
-2.86321
-3.19574
-3.40299
-3.98746
-4.16937
-3.22963
-2.96148
-2.00795
-1.0091
-1.06765
-0.11665 1.07138 1.10675 1.41412 1.5495 1.49213 0.97127 0.60252
-0.17378
-1.43638
-2.23908
-3.84187
-3.33485
-2.28476
-15
-14
-13
-12
-11
-10 15.2 12.0626 14.5 15.38871 13.9686 14.65652 0.22867 2.4548 4.59783 6.28019 7.94552 9.20318 10.3764
-2.69612
-0.39618 2.21181 4.33835 6.58671 8.17469 9.48532
-2.99301
-7.0783 2.04862 0.40133
-2.1889 3.7573 3.24936 1.83859 5.62121 5.73444 3.91107 7.08365 7.54635 6.31006 8.34868 8.21011 9.02301 9.49703
-9 10.39289 9.35398 10.51932
-8 11.22505 11.40581 10.55069 10.84618 11.49219
-7 12.2259 11.48812 11.78517 12.45577
-6 12.58889 12.93307 12.52165 12.68119 13.22151
-5 13.1692 13.66525 13.12559 13.40221 13.92189
-4 13.61192 14.18925 13.78195 13.89657 14.50501
-3 14.2457 14.40549 14.80142
-2 14.18319 14.99795 14.73547 14.78941 15.04343 14.9621 15.18729
-1 14.42292 15.20262 14.89697 15.3 0 14.49728 15.37594 15.12249 15.18812 1 15.2 15.2761 2 14.46242 15.4 15.19876 15.02663 15.05457 3 14.26309 15.36597 15.04249 14.95714 14.83603 15.1602 14.85574 14.61281 14.35692 4 13.94507 5 13.78897 14.77475 14.5347 14.21596 13.82148 6 13.28387 14.43909 14.09921 13.64313 13.13172 7 12.76202 13.90814 13.56217 12.93424 12.25155 12.9823 12.10955 11.32678 8 12.0901 13.26824 9 11.192 10.01005 11.2657 12.70037 12.11524 8.47059 9.91637 11.2692 6.69546 8.57179 10.8003 10.31124 4.6972 7.00563 9.03426 9.69415 1.88504 4.58928 8.57199 7.75688 2.01203
-3.13701 5.8619 6.96565
-2.13567 -10.68696 4.19034 5.32273
-8.05468 -20.88835 1.7675 3.65002
-16.0328
-7.62835 1.79399
-0.52581
-3.37688
-7.32135
-2.81781 0.11451
-0.95646
-4.22369
-3.42529
-0.63183 0.67616
-1.32974
-3.48271
-0.86769 1.55707 0.35305
-1.26746
-0.56946 1.32215 1.62483 0.26439 0.29008 1.9426 1.91968 1.17345 1.23124 2.04502 2.02405 1.36196 2.18499 1.5792 1.833 1.56742 2.80045 1.28865
-0.37273 3.18385 2.16094
-1.29255 0.58157 1.90752 3.29714
-1.88291
-0.45245 1.99528 2.72818
-5.46669
-1.44314 0.97986 2.91579
-4.33894
-7.38753 2.37634 0.04942
-9.84346
-6.68206
-0.38249 1.90843
-9.0852
-1.61429 1.64535
-9.73236
-7.05783
-3.20042 -22.60325 0.39854
-0.96965
-5.82258 -17.52349
-4.37473
-2.61157
-8.52063 -12.00341
-1.83582
-0.54867
-8.08674
-3.94442
-12.078 0.8429
-4.40813
-5.44888 -18.26101
-8.16088 -18.15075
-2.08683 1.81202 2.05886
-1.32036
-5.77359 -10.55835 -12.55475
-7.47058 -13.03593
-8.6389 0.18032 2.48679 10 10.49907 11.61846 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 9.47384 8.24693 7.01041 5.35634 3.52198 1.40219
-0.6045
-3.17539
-3.75934
-3.26134
-1.83557
-0.97562 0.89168 1.7269 2.38118 2.53978 2.7704 2.7904 2.92997 2.60759 2.14581 1.51641 1.19314 0.09539
-0.26725
-1.64138
-3.58001
-4.4754 0.30707 0.99845 1.02319 1.40267 1.2301 1.74812 1.77816 1.17052 0.79422
-0.12515
-0.46548
-1.06141
-2.29035
-3.78895
-4.55634
-6.0465 2.9884
-5.94503
-9.31528 -13.83599 41 2.99696
-5.38112 42 -12.42462 -10.77258 2.982
-3.64234
-9.70894 43 -14.02988 3.14618
-2.84773
-8.06674 44 -13.48534 2.904
-1.24356 45 -12.77293
-7.10457 2.34853
-1.33003
-6.12147 46 -11.51633 2.07266
-1.37219
-4.89159
-9.77214 47 1.29625
-1.229
-4.451
-9.04963 48 0.42264
-0.83682 49
-8.16747
-4.15337 0.15741
-1.24025
-3.48798
-6.88691 50
-0.63901
-1.80963
-3.06033
-6.98067 51
-1.59681
-1.79363
-3.3729
-6.56488 52
-4.06238
-2.70215 53
-5.51633
-3.40907
-4.7411
-3.41055
-3.39568
-5.56097 54
-6.04779
-4.65197
-3.91077
-5.51677 55
-9.89011
-4.29157
-3.90854
-6.34769 56
-6.66121 -10.81916
-5.01859 57
-5.23421
-4.52172
-7.14011 -10.29376 -16.64689
-5.34363
-6.15479 58
-9.17235 -11.55835 -27.73342
-5.95124
-6.43804 59
-6.45479
-6.22236 60
-9.95459 -14.97166 -22.05778
-7.36936 -10.52234 -17.53509 -15.31525 61
-6.16701
-7.81326
-7.24188 62
-12.9331 -15.67209 -13.36412
-7.70875 -12.55642 -19.86507 -12.22431
-7.26288 63
-14.1327 -19.69635 -11.12017
-9.21641
-7.54502 64 65
-8.86378
-9.83103 -18.18985 -13.90819
-9.32219
-7.74338
-8.80439 66
-12.392 -21.46821 -13.19298
-7.68113
-9.48359 -11.92699 -22.31817 -11.46904 67
-5.90222
-12.4089 -21.42918 -10.18854
-9.74519 68 69
-9.94963 -17.26085 -19.20657
-9.64908
-5.36669
-4.49643 70 -11.33889 -17.47745 -20.71152
-9.4745
-5.37074
-14.6942 -20.73225 -10.01562 71
-9.96426
-4.43965
-7.85937 72 -13.03017
-18.7776 -15.81204 73 -12.65054 -14.24831 -14.46988
-7.82962
-4.47607
-4.27725
-7.44718 74 -15.26754 -15.95109 -15.42812
-5.08197
-7.22002 75 -14.34266
-18.8356 -13.05085
-3.77779
-6.53671 76 -14.36145 -15.52878 -15.24009
-4.20108
-7.4077 77 -13.91779 -18.92991 -12.01611 78
-12.669
-6.84751
-5.20925
-15.109 -17.35709
-4.64033
-6.26633 79 -17.85189 -16.93424
-13.9662
-4.45178
-7.17807 80 -14.53106 -16.61662 -12.63588
-4.32371
-6.20852 81 -15.40988 -12.78226
-11.9461 82 -16.41856 -14.30889 -12.61978
-6.79797
-6.00913
-4.66916
-6.82401 83 -18.27039 -14.63912 -11.12671
-5.15381
-6.68245 84 -15.68484 -15.39463 -11.90342
-5.44582
-8.44825 85 -15.23173 -13.19665 -11.96312 86 -21.53702 -14.31515 -12.43463
-7.89457
-7.4275
-6.41841
-8.02272 87 -14.75197 -17.19426 -11.13273
-5.53974 88 -15.83549
-15.1705 -11.99918
-8.66637
-7.01818
-10.9973 -10.34658 89 90 -15.78141 -13.95283 -12.80362
-9.27642
-6.88875
-6.9447 91 -16.27937
-16.3187 -12.44543 -10.31633
-6.69116 92 -17.31179 -14.07297 -14.12926 -11.93982
-9.01854 93 -17.26934
-13.6107 94 -18.38978 -13.06125 -14.63395 -13.60987
-9.16816 95 -17.88246 -14.69673 -14.46234 -15.56122
-10.2771 96 -23.26695 -16.65267 -13.31959 -16.08869 -11.97594
-15.3956 -18.14186
-15.9077 -14.35171
-18.267
-19.7592 -15.65835 97 -19.09801 -15.09989 -16.71228 -15.90004 -12.93491 98 -21.24819 -15.90165 -13.37498 -19.01302
-12.1584 99 -20.30582 -15.69851 -15.51381 -15.79635 -11.16735
-21.6992 -14.12165 100 -23.40973 -16.19723 -17.54661
-14.741 -12.74202 -13.66494 101 -19.33664 -17.61386 102 -21.67106 -17.80161 -16.22551 -19.92966 -13.57304 103 -21.76734 -17.12755 -14.35564 -25.88715 -14.24742
-14.9672 104 -21.45175 -16.29207 -15.27955
-23.47 105 -22.27379 -16.18467 -14.33082 -23.58629
-14.1968 106 -21.07862 -18.58815
-13.7985 -20.42164 -15.39769 107 -21.28107 -16.35397 -13.81487 -21.14554 -17.44797 108 -30.52562 -16.15008 -13.62072
-17.5052 -16.98822 109 -23.55134 -15.30037 -13.52086 -16.81644 -17.27143 110 -26.23552 -15.24509 -14.28801 -19.68493 -22.96831 111 -35.27488 -14.55485 -12.42753 -22.29564 -22.23616 112
-13.0861 -20.22912 -22.05221 113 -22.40313 -13.50075 -14.60263 -20.57715 -20.21496
-23.56 -16.88103 -15.06029 -15.25094 -20.02564 114 115 -19.79004 -12.61236 -14.04596 -15.97403
-17.0322
-21.9524 -15.38781 -11.76256 -15.57692 -13.88155 116 117
-17.6062 -15.78818 -13.40963 -16.63332 -15.82125 118
-13.0059 -13.49852 -12.27781 -19.65085 119 -15.57844 -15.19148 -13.12667 -13.04471 -16.31501 120 -15.75863 -12.41546 -13.50343 -12.74414 -14.79677 121 -13.20768 -11.52199 -13.55175 -15.19812 -14.12806 122 -12.94305 -12.62284 -12.80222 -12.15201
-14.73 123 -12.88239 -12.84224 -11.92132
-10.7828 -12.06877 124 -13.44394 -11.23824 -12.52569 -12.33117 -16.14173 125 -12.89174 -11.51713 -12.94157 -10.19816 -12.53904 126 -12.30372 -12.41063 -13.11541 -10.81608 -14.12956 127 -12.36261 -10.56592 -10.42491
-14.9419 128 -11.99414 -12.47138 -10.27614
-9.8639 -16.42092 129 -12.38652 -11.83284 -10.79384 -11.84121 -10.63584 130 -13.34821 -12.10649 -13.18643
-11.6994 -15.86664 131 -13.30905 -13.56646 -10.83596 -12.16251 -13.07984
-14.1792 -11.77071 -11.23808 -12.21746 -14.22711 132 133
-14.8912 -13.90813 -10.13997 -10.91115
-15.7756 134 -13.42363 -18.51299 -12.05935 -10.63234 -15.35195 135 -15.82988 -17.65564 -10.81735 -11.37414 -16.58657 136 -18.94932 -18.76027 -12.26877 -12.82199 -14.18705 137 -20.82884 -16.83743 -14.87997 -12.34896
-15.9485 138 -21.82116 -19.40526
-11.4542 -13.12645 139 -25.61705 -26.47215 -14.75723 -14.08745 -13.16736 140 -22.30915 -23.18784 -16.31548 -17.16321 -13.29315 141 -21.82154 -24.04503 -18.51346 -14.20211 -11.26277 142
-11.0938
-16.0641 -16.32227 -16.20306 -13.04406
-9.95674 143 -15.04419 -19.01304 -15.13252 -12.54083 144
-14.773 -16.89988 -17.92695 -11.17935
-10.6942 145 -14.37442 -13.81248 -19.13568
-14.8023 -11.54933 146 -11.39141 -16.66112 -19.06081 -12.61649 -10.75857 147 -12.26019 -12.98543 -21.53498 -14.26274 -11.93109
-14.7857 -20.05004 -12.40321 -11.15312 148 -10.26645 149 -10.02062
-15.7875 -17.32756 -15.42431 -11.14083 150
-9.83163 -15.92566 -18.67306 -16.34316 -12.22036 151 -12.10852 -15.41778 -15.71662 -18.84263 -15.75924 152 -11.17241 -14.90559 -14.84861 -16.73255 -16.53529
-14.4138
-9.53674 153 -12.29476 -13.90194 -12.86164 -14.91024 -22.51615 154 -12.12312 -17.93033
-12.9359 -18.09131 -16.39351 155 -13.25113 -14.58932 -15.39692 -19.57516 -23.64319 156 -15.01192 -15.62936 -13.40643 -17.11387 -21.23247 157 -15.01172 -15.37935 -11.61626 -13.62556 -13.82452 158 -15.92835 -13.19347 -12.95242 -14.51322 -14.18903 159 -14.44692 -16.66376 -11.69432 -14.14792 -14.52806 160 -15.85418
-13.31 -11.04465 -12.31708 -11.98426 161 -13.37297 -15.49891 -11.97663 -11.55481 -10.91964
-11.7431 -13.34679 -11.07137 162 -13.75213 -13.83053 163 -14.80944 -13.30972 -13.71014
-11.1707 -11.14716 164 -12.30402 -15.70814 -11.33671 -12.95134 -11.11487 165 -14.79904
-14.0586 -11.07443 -13.36346 -12.57328 166 -11.58352 -15.54382 -15.47043 -11.24635 -14.63657 167 -13.36367 -13.50181 -12.95034 -15.28415 -17.51318 168 -15.78313 -14.11302 -13.04506 -12.05823 -27.72107 169 -18.09297 -17.19542 -12.03748 -13.03321 -16.00925 170 -15.42812 -14.65838 -12.81537 -10.33875
-18.1315
-11.3451 -12.16961 -12.65403 171 -22.90525 -17.33698
-9.37158 -10.38721
-9.46274 172 -20.69958 -15.41593 173 -20.53117 -14.08626
-9.13844
-7.24363
-7.45857
-7.74911
-6.55366
-8.7706
-15.9238 -13.21844 174
-4.80266
-5.4919
-7.75336 175 -16.50936
-11.563
-4.98848
-4.63252
-6.57168 176 -15.63913 -11.13819 177 -13.34461
-9.86073
-6.02103
-5.11509
-2.78965
-2.79937
-3.60207
-5.20699
-9.22913 178 -11.94007
-3.35794
-3.89449
-5.75548
-8.93958 179 -11.51871 180
-8.97037
-7.93027
-6.85495
-4.94788
-2.99819
1 2 3 4 5 6 7 | antenna pattern of MA-WA55-30 | Parts List/Tune Up Info | 27.79 KiB | January 09 2014 / August 10 2014 |
29.51 90.00 CH1 File Name:
ROLL 90.00 Frequency POL Ch. Beam Switch Gain AZ [deg]
-179.5000
-178.5000
-177.5000
-176.5000
-175.5000
-174.5000
-173.5000
-172.5000
-171.5000
-170.5000
-169.5000
-168.5000
-167.5000
-166.5000
-165.5000
-164.5000
-163.5000
-162.5000
-161.5000
-160.5000
-159.5000
-158.5000
-157.5000
-156.5000
-155.5000
-154.5000
-153.5000
-152.5000
-151.5000
-150.5000
-149.5000
-148.5000
-147.5000
-146.5000
-145.5000
-144.5000
-143.5000
-142.5000
-141.5000
-140.5000
-139.5000
-138.5000
-137.5000
-136.5000
-135.5000
-134.5000
-133.5000
-132.5000
-131.5000
-130.5000
-129.5000
-128.5000
-127.5000
-126.5000
-125.5000
-124.5000
-123.5000 MA-WA55-30 MA-WA55-30_-CAL.nff
[deg]
5.150 G [GHz]
[deg]
dBi Amplitude [dB] Phase [deg]
-28.0316
-29.8156
-28.1781
-43.5960
-43.1363
-30.5463
-25.7882
-26.1762
-29.3011
-30.5558
-26.2958
-26.1300
-29.6307
-27.1524
-23.4854
-26.4970
-24.9600
-24.6199
-24.0383
-24.6502
-21.8297
-23.2235
-22.4370
-22.5895
-21.7012
-22.2685
-22.1108
-21.5690
-21.4510
-20.8808
-21.7873
-21.6929
-21.0288
-22.5435
-22.3578
-21.4192
-22.1605
-20.6732
-20.7616
-20.6598
-19.4210
-19.1601
-19.3191
-18.3545
-18.9801
-19.0532
-20.1025
-19.3122
-19.3235
-18.1848
-17.9353
-17.6197
-18.5499
-18.2376
-18.8132
-18.8165
-19.2179
-104.9151
-88.3414
-93.3924
-46.3020 44.2964 70.9690 70.2771 97.7360 123.1408 135.6667
-152.9879
-90.1141
-65.1919
-42.0784
-8.6441
-3.2101 48.1934 102.1812 128.8332 159.6128
-178.7133
-155.3877
-112.1241
-90.4760
-53.4714
-23.0167
-0.0586 23.0628 57.2969 80.6687 109.4285 141.1349 162.0171
-163.4174
-140.4116
-116.8683
-84.5898
-49.2691
-25.9055
-1.0939 26.5061 49.4942 78.1846 87.8758 114.2639 133.7075 157.6241
-170.5705
-153.1749
-133.1585
-108.4458
-92.7082
-74.8398
-65.1234
-46.5079
-21.1703 0.1177 Page 1
-122.5000
-121.5000
-120.5000
-119.5000
-118.5000
-117.5000
-116.5000
-115.5000
-114.5000
-113.5000
-112.5000
-111.5000
-110.5000
-109.5000
-108.5000
-107.5000
-106.5000
-105.5000
-104.5000
-103.5000
-102.5000
-101.5000
-100.5000
-99.5000
-98.5000
-97.5000
-96.5000
-95.5000
-94.5000
-93.5000
-92.5000
-91.5000
-90.5000
-89.5000
-88.5000
-87.5000
-86.5000
-85.5000
-84.5000
-83.5000
-82.5000
-81.5000
-80.5000
-79.5000
-78.5000
-77.5000
-76.5000
-75.5000
-74.5000
-73.5000
-72.5000
-71.5000
-70.5000
-69.5000
-68.5000
-67.5000
-66.5000
-65.5000
-64.5000
-63.5000
-62.5000
-61.5000
-60.5000
-59.5000
-58.5000
-57.5000
-56.5000
-55.5000
-18.0610
-17.4730
-16.6753
-16.9402
-17.0979
-17.1900
-17.4045
-15.9032
-17.6674
-16.8331
-16.9985
-17.1144
-15.5679
-16.0122
-15.6839
-16.8046
-16.7730
-17.0059
-16.1588
-15.9514
-15.9987
-15.9824
-15.7182
-16.2761
-15.8032
-15.5322
-16.6091
-16.1394
-16.2602
-16.6187
-17.6202
-18.0106
-19.6349
-17.8111
-20.3744
-21.4181
-21.6103
-26.1586
-27.3452
-26.1281
-32.3457
-28.4624
-26.6785
-22.1141
-18.8269
-16.7696
-15.5876
-15.5236
-13.3823
-12.6768
-11.7870
-11.6753
-12.1032
-12.2988
-13.4481
-14.8834
-16.3005
-17.5837
-14.9855
-11.7919
-9.2370
-7.2166
-5.8568
-4.6233
-4.4775
-4.4845
-4.8832
-5.5724 MA-WA55-30 18.8991 36.1957 51.3318 67.7315 76.7890 98.3889 105.1308 126.8521 139.8103 152.9961 167.5575 177.2438
-174.8083
-165.6363
-155.1090
-147.7175
-141.0757
-124.1775
-118.7482
-108.5849
-100.1640
-92.4954
-89.6698
-83.1569
-75.8312
-74.7723
-67.9415
-63.5736
-61.3678
-57.1569
-55.5939
-53.7316
-54.9021
-53.4028
-60.2093
-53.9539
-56.2878
-53.0184
-61.9173
-126.3564
-149.0278 175.7949 156.6176 149.9903 150.4536 150.4605 147.1739 143.7913 138.7799 145.7649 138.2984 135.9468 131.6570 125.9628 118.6040 106.6786 85.9365 50.7118 15.7716 0.3735
-6.8518
-14.8502
-20.2184
-22.1583
-21.8796
-22.0392
-20.0154
-17.9101 Page 2
-54.5000
-53.5000
-52.5000
-51.5000
-50.5000
-49.5000
-48.5000
-47.5000
-46.5000
-45.5000
-44.5000
-43.5000
-42.5000
-41.5000
-40.5000
-39.5000
-38.5000
-37.5000
-36.5000
-35.5000
-34.5000
-33.5000
-32.5000
-31.5000
-30.5000
-29.5000
-28.5000
-27.5000
-26.5000
-25.5000
-24.5000
-23.5000
-22.5000
-21.5000
-20.5000
-19.5000
-18.5000
-17.5000
-16.5000
-15.5000
-14.5000
-13.5000
-12.5000
-11.5000
-10.5000
-9.5000
-8.5000
-7.5000
-6.5000
-5.5000
-4.5000
-3.5000
-2.5000
-1.5000
-0.5000 0.5000 1.5000 2.5000 3.5000 4.5000 5.5000 6.5000 7.5000 8.5000 9.5000 10.5000 11.5000 12.5000 MA-WA55-30
-11.9893
-4.9756 1.8441 9.6400 16.0784 14.9859
-3.1984
-18.5570
-31.1237
-38.6575
-42.6593
-44.8045
-45.0852
-42.7652
-33.7596
-6.2526 44.2852 73.7620 84.4375 87.7995 87.4433 83.9735 73.0779 35.8338
-36.2912
-58.4295
-67.1800
-70.4360
-72.6671
-74.2007 93.0531 98.7460 97.8536 96.6991 95.7825 94.7605 92.9707
-81.0732
-87.5137
-90.0624
-93.0380
-97.9640
-112.0805 155.2124 109.7120 100.7138 95.7556 91.0652 81.5337 7.3702
-63.5207
-72.4565
-75.5669
-6.6941
-8.1540
-9.7449
-10.9396
-11.7824
-11.2808
-10.9285
-8.6601
-6.2595
-3.4491
-1.6003
-0.4857
-0.2715
-0.9262
-2.9745
-6.5368
-6.2698
-2.0171 1.3749 2.9966 3.4393 2.4004
-0.5034
-5.6268
-3.3959 1.6848 4.2315 4.7907 3.1333
-2.8644
-11.3912 2.4535 7.3874 9.3943 9.4906 7.2788 0.6766
-5.4456 6.9631 10.8599 12.0621 10.9012 6.2390 1.0551 10.6818 15.2080 17.0251 16.6409 13.2048 4.6812 16.1857 22.3286 25.9595 28.0830 -76.8005 29.2068 -77.1420 29.4577 -76.8937 28.8687 -76.1313 27.4072 -74.7277 24.8389 -71.8259 20.7262 -66.0222 13.5875 -48.3757 7.6882 41.4043 13.9028 83.3350 15.9844 93.8959 15.5452 100.5487 12.8836 109.3309 6.7626 131.6904 2.9542 -144.7439 Page 3 MA-WA55-30
-52.1890
-2.8475 -170.4795 178.3378 13.5000 8.7923 -103.9967 14.5000 11.1754 -91.9520 15.5000 11.1686 -84.3411 16.5000 9.0758 -76.9270 17.5000 3.8480 -62.7305 18.5000
-5.2290 5.6712 19.5000 2.3129 80.2286 20.5000 5.8518 96.4438 21.5000 6.4303 107.5555 22.5000 4.9395 122.9433 23.5000 1.9047 152.7287 24.5000 1.3348 -156.4045 25.5000 4.5354 -121.8692 26.5000 6.9649 -105.2897 27.5000 7.8062 -96.0025 28.5000 7.1292 -89.4223 29.5000 4.9260 -83.3573 30.5000 0.2964 -76.4077 31.5000
-11.8483 32.5000
-5.8884 94.4275 33.5000 0.5037 105.7119 34.5000 2.4406 112.8232 35.5000 2.6223 120.9581 36.5000 1.4914 133.9849 37.5000
-1.0131 154.2213 38.5000 39.5000
-1.8880 -131.7419 40.5000 0.1371 -109.8710 41.5000 1.3641 -97.0578 42.5000 1.2040 -90.0974 43.5000 0.1595 -86.1429 44.5000
-2.9654 -85.0966 45.5000
-8.8289 -96.1938 46.5000
-13.4259 47.5000
-5.0523 144.3662 48.5000
-0.8203 141.3848 49.5000 1.4937 143.0955 50.5000 2.9930 149.0625 51.5000 3.6635 155.8073 52.5000 4.0459 163.7550 53.5000 3.9963 173.1745 54.5000 3.8773 -176.3245 55.5000 3.9362 -165.5351 56.5000 3.8843 -154.3793 57.5000 3.7089 -143.5673 58.5000 3.5137 -134.3754 59.5000 3.2688 -126.4571 60.5000 2.9533 -118.6560 61.5000 2.3198 -112.8903 62.5000 1.6000 -106.6061 63.5000 0.5581 -100.2426 64.5000
-0.5446 -94.1788 65.5000
-2.0045 -88.0424 66.5000
-3.9554 -82.3944 67.5000
-5.9116 -71.8643 68.5000
-8.2791 -61.5311
-47.2067 69.5000 -10.4346
-24.0007 70.5000 -12.6915
-6.7579 71.5000 -13.9791 18.3986 72.5000 -13.7234 73.5000 -13.5719 36.1065 45.8842 74.5000 -12.9571 55.0359 75.5000 -12.2718 56.3811 76.5000 -11.7008 65.3740 77.5000 -12.3293 78.5000 -12.3391 67.0606 72.3097 79.5000 -12.8649 80.5000 -12.8006 73.8212 Page 4 MA-WA55-30 81.5000 -13.9245 77.5507 82.5000 -14.4527 76.5238 83.5000 -14.8325 80.9657 84.5000 -16.2985 82.4570 85.5000 -16.6564 80.5379 86.5000 -18.3917 86.7387 87.5000 -18.3696 95.6632 88.5000 -20.0143 91.8288 89.5000 -19.9526 85.7632 90.5000 -19.5588 98.9720 91.5000 -20.9973 106.4958 92.5000 -22.1486 112.6503 93.5000 -21.1637 114.2572 94.5000 -21.5703 105.2574 95.5000 -21.0302 116.0074 96.5000 -21.0346 116.0688 97.5000 -22.6657 116.5716 98.5000 -22.6185 116.6902 99.5000 -26.1320 108.3608 100.5000
-26.2847 101.5000
-24.4972 102.5000
-25.7730 103.5000
-27.5433 104.5000
-26.0757 105.5000
-26.0008 106.5000
-23.2525 107.5000
-25.0701 108.5000
-24.4247 109.5000
-23.6493 110.5000
-24.7399 111.5000
-23.6761 112.5000
-26.2161 113.5000
-24.7858 114.5000
-25.3582 115.5000
-26.4422 116.5000
-27.1033 117.5000
-34.7478 118.5000
-31.0076 119.5000
-31.0548 120.5000
-34.9916 121.5000
-35.2017 122.5000
-39.0812 123.5000
-26.3235 124.5000
-27.8417 125.5000
-32.0531 126.5000
-29.2026 127.5000
-30.1257 128.5000
-35.5545 129.5000
-34.4326 130.5000
-42.3873 131.5000
-41.5006 132.5000
-30.7878 133.5000
-31.0653 134.5000
-36.7846 135.5000
-33.5577 136.5000
-42.3286 137.5000
-35.6746 138.5000
-38.0082 139.5000
-33.6133 140.5000
-40.7371 141.5000
-40.5231 142.5000
-32.6587 143.5000
-40.5294 144.5000
-40.6058 145.5000
-38.0671 146.5000
-35.4695 147.5000
-35.8342 148.5000
-48.4446 100.1797 91.4989 70.8679 42.8718 43.0461 36.3811 14.4058 8.6613 7.8829
-2.5354
-21.9795
-29.1618
-40.2588
-56.0275
-53.7203
-49.8931
-68.0145
-77.3872
-104.3727
-159.7881
-158.7109 160.2735 149.3338 144.5822 135.8584 137.6722 110.5996 121.7311 155.3123
-177.4833
-152.2014 11.3041
-71.3804
-86.4348
-22.4715
-41.0052
-72.0289
-75.4168
-118.6137
-74.9657
-18.2313
-94.1245
-79.2986 16.6087
-88.1844 1.4591 90.4796
-90.5626
-8.3107 Page 5 149.5000 150.5000 151.5000 152.5000 153.5000 154.5000 155.5000 156.5000 157.5000 158.5000 159.5000 160.5000 161.5000 162.5000 163.5000 164.5000 165.5000 166.5000 167.5000 168.5000 169.5000 170.5000 171.5000 172.5000 173.5000 174.5000 175.5000 176.5000 177.5000 178.5000 179.5000
-38.7206
-39.9426
-37.9327
-35.3572
-31.0989
-31.4807
-30.1716
-39.5999
-36.9673
-40.2983
-35.9456
-36.9229
-42.9844
-37.2298
-33.8505
-33.5616
-34.4702
-44.3096
-39.7603
-30.6838
-29.3967
-29.6102
-33.9878
-31.9312
-36.9308
-42.0664
-34.6581
-51.5803
-34.7695
-32.0336
-29.7637 MA-WA55-30
-65.2704
-22.8133
-69.3417
-89.7209
-75.8001
-54.6840
-104.5906
-76.1138
-112.3260
-112.7257
-77.3890
-151.0312 172.4233
-49.4707
-74.8135
-52.2579
-60.0605
-133.5414
-109.1278
-133.3813
-156.8480
-155.2498 132.7078 154.7272 137.6239 45.6365 146.9603 94.8404
-162.4453
-101.5510
-126.8682 Page 6
1 2 3 4 5 6 7 | antenna pattern of MA-WB55-20 | Parts List/Tune Up Info | 27.60 KiB | January 09 2014 / August 10 2014 |
CH1 20.29 90.00 File Name:
POL Frequency ROLL 90.00 Ch. Beam Switch Gain AZ [deg]
-179.5000
-178.5000
-177.5000
-176.5000
-175.5000
-174.5000
-173.5000
-172.5000
-171.5000
-170.5000
-169.5000
-168.5000
-167.5000
-166.5000
-165.5000
-164.5000
-163.5000
-162.5000
-161.5000
-160.5000
-159.5000
-158.5000
-157.5000
-156.5000
-155.5000
-154.5000
-153.5000
-152.5000
-151.5000
-150.5000
-149.5000
-148.5000
-147.5000
-146.5000
-145.5000
-144.5000
-143.5000
-142.5000
-141.5000
-140.5000
-139.5000
-138.5000
-137.5000
-136.5000
-135.5000
-134.5000
-133.5000
-132.5000
-131.5000
-130.5000
-129.5000
-128.5000
-127.5000
-126.5000
-125.5000
-124.5000 MA-WB55-20 MA-WB55-20-CAL.nff
[deg]
5.200 G [GHz]
[deg]
dBi Amplitude [dB] Phase [deg]
-28.6666
-28.2058
-32.1546
-29.9479
-34.3301
-33.1609
-38.0371
-36.8065
-32.6058
-31.2864
-41.2571
-32.9061
-37.3165
-41.3964
-36.4430
-38.7510
-39.5114
-43.8090
-30.2488
-33.5117
-34.5848
-36.3261
-42.2270
-37.5082
-44.3224
-36.9881
-46.5887
-42.0651
-37.5170
-32.6648
-34.8344
-33.9824
-31.8301
-38.5086
-38.7879
-33.5810
-54.8861
-46.4703
-35.3469
-39.6978
-47.9565
-33.2973
-43.1252
-38.6046
-32.6199
-31.5438
-26.8904
-27.6926
-27.3131
-23.0421
-22.5966
-23.7866
-23.9644
-22.7877
-25.7597
-27.6464
-43.3069
-12.0943 5.6244
-5.1692
-7.4273 16.1252
-33.1913
-22.9987
-65.5540
-18.0973 5.9570 44.1151 6.5062
-144.4268 106.0923
-120.4358 171.6844
-127.3908
-131.0498
-123.0461
-77.2314
-113.3454
-59.4036
-93.5057 56.7101
-89.5577
-89.0211
-87.2428 36.4009
-62.2419
-61.4695 33.0135
-3.8858
-0.3278 22.5533 14.9212 38.1579 66.0791 78.3623
-151.2181 163.4582
-129.9193 175.7586
-105.2126
-38.1611
-13.2697
-3.5883 37.5678 25.0432 44.3947 43.7157 47.3454 67.0402 72.3386 62.7053 88.3240 Page 1
-123.5000
-122.5000
-121.5000
-120.5000
-119.5000
-118.5000
-117.5000
-116.5000
-115.5000
-114.5000
-113.5000
-112.5000
-111.5000
-110.5000
-109.5000
-108.5000
-107.5000
-106.5000
-105.5000
-104.5000
-103.5000
-102.5000
-101.5000
-100.5000
-99.5000
-98.5000
-97.5000
-96.5000
-95.5000
-94.5000
-93.5000
-92.5000
-91.5000
-90.5000
-89.5000
-88.5000
-87.5000
-86.5000
-85.5000
-84.5000
-83.5000
-82.5000
-81.5000
-80.5000
-79.5000
-78.5000
-77.5000
-76.5000
-75.5000
-74.5000
-73.5000
-72.5000
-71.5000
-70.5000
-69.5000
-68.5000
-67.5000
-66.5000
-65.5000
-64.5000
-63.5000
-62.5000
-61.5000
-60.5000
-59.5000
-58.5000
-57.5000
-56.5000 MA-WB55-20 76.4293 162.5574 137.6737
-131.7828
-86.3124
-80.9482
-87.0277
-103.5822
-76.1776
-87.7073
-64.0428
-52.2666
-57.8398
-24.4608
-17.8819 2.5564 14.8211 22.4505 35.1085 44.8546 52.3661 64.0063 68.8560 89.2175 91.7730 93.1314 103.6164 127.8298 119.3350 136.9330 136.3664 150.7512 136.4991 158.1808 152.4984 162.5032 157.6530 171.3866 173.6908 175.2277
-174.7427
-177.0005
-148.0867
-172.0410
-147.2540
-153.7718
-137.2644
-143.0204
-129.1637
-135.8940
-90.1434
-101.4043
-115.9266
-135.6674
-109.0633
-138.4213
-173.3654 137.3351 134.6408 136.4434 132.4385 133.0742 136.9678 134.2823
-31.6048
-44.8449
-33.6250
-32.0595
-28.5270
-26.8783
-23.4706
-24.9627
-22.1932
-22.3356
-23.0597
-25.3379
-24.9453
-24.8859
-27.2865
-25.2793
-26.8463
-24.1612
-23.1571
-25.1705
-23.5160
-24.6670
-23.3959
-23.6506
-21.8785
-23.6135
-23.3644
-22.8555
-22.2908
-21.6215
-23.4160
-22.3033
-22.1526
-22.1709
-21.8175
-21.5198
-22.1963
-20.8091
-21.0783
-20.3967
-22.1089
-21.9344
-22.8408
-23.8373
-22.7710
-23.3816
-23.6881
-24.4455
-25.8369
-25.6293
-27.4167
-26.4058
-26.5683
-27.7654
-34.0220
-32.0952
-32.5449
-26.4843
-24.3025
-19.6109
-17.7878
-15.9236
-13.1885
-11.6286
-9.4314 132.7427
-8.7369 133.9292
-7.8214 136.5773
-6.9821 137.7889 Page 2 MA-WB55-20
-173.0611
-139.7436
-106.0272 40.3489 54.7819 68.6891 67.3715 56.1293
-9.4451
-39.7502
-70.6435 147.7219
-6.4754 139.7953
-6.4481 142.0474
-6.9304 145.6238
-7.3895 149.0467
-8.4985 157.6328
-9.9135 167.1015
-11.8184
-13.3255
-11.3559
-8.7555 -87.1777
-6.3988 -73.2379
-4.4896 -66.7390
-3.1977 -61.8594
-2.1102 -57.4918
-1.4485 -52.5503
-1.4249 -48.6670
-1.5682 -44.0639
-2.0740 -38.6925
-2.8749 -31.8851
-4.1889 -26.0740
-6.0717 -13.9767
-7.7605 -2.2710
-9.5839 15.5491
-10.3868
-10.7127
-11.3817
-13.7117
-16.2311
-17.6817
-11.9822
-6.7453 -48.1599
-3.3771 -51.2878
-1.2339 -53.5070
-0.0851 -53.5570 0.4109 -53.7354
-0.0621 -54.2972
-1.4711 -54.4028
-4.7025 -58.1534
-13.3919
-12.9126
-3.1195 139.2708 0.8436 135.5381 3.1815 136.0179 4.2635 136.4940 4.2480 139.2460 2.8054 145.2872
-55.5000
-54.5000
-53.5000
-52.5000
-51.5000
-50.5000
-49.5000
-48.5000
-47.5000
-46.5000
-45.5000
-44.5000
-43.5000
-42.5000
-41.5000
-40.5000
-39.5000
-38.5000
-37.5000
-36.5000
-35.5000
-34.5000
-33.5000
-32.5000
-31.5000
-30.5000
-29.5000
-28.5000
-27.5000
-26.5000
-25.5000
-24.5000
-23.5000
-22.5000
-21.5000
-20.5000
-19.5000
-18.5000
-17.5000
-16.5000
-15.5000
-14.5000
-13.5000
-12.5000
-11.5000
-10.5000
-9.5000 -0.5375 161.7749
-8.5000 -4.1356 -142.3119
-7.5000 2.1173 -87.5195
-6.5000 7.7912 -72.9658
-5.5000 11.6447 -66.9165
-4.5000 14.4595 -64.2381
-3.5000 16.5101 -62.6954
-2.5000 18.0062 -61.8647
-1.5000 19.0782 -61.5774
-0.5000 19.7621 -61.4808 0.5000 20.0972 -61.7252 1.5000 20.0803 -61.9004 2.5000 19.6981 -62.3554 3.5000 18.9007 -63.0727 4.5000 17.6902 -64.0209 5.5000 15.9379 -65.6161 6.5000 13.5843 -68.0308 7.5000 10.1987 -72.2362 8.5000 5.4488 -81.4315 9.5000 -1.7969 -115.7722 10.5000 -1.5865 169.5713 11.5000 2.7679 144.5007 Page 3 12.5000 4.6956 137.4746 13.5000 5.0436 134.9150 14.5000 4.0895 134.9664 15.5000 1.9287 138.5860 16.5000 -2.3908 148.0979 17.5000 -8.5802 -169.4721 18.5000 -5.6680 -98.8990 19.5000 -0.7454 -79.0763 20.5000 1.7819 -71.3293 21.5000 3.1802 -67.9775 22.5000 3.4828 -65.4741 23.5000 3.0451 -62.2819 24.5000 1.9645 -59.3752 25.5000 -0.1290 -54.7104 26.5000 -3.2541 -47.2096 27.5000 -8.1821 -28.9736 28.5000 -12.2007 29.5000 -8.0505 76.4738 30.5000 -4.8798 92.6437 31.5000 -2.8486 99.0422 32.5000 -1.8016 103.9256 33.5000 -1.5890 106.7100 34.5000 -1.9087 107.9662 35.5000 -2.9604 110.1992 36.5000 -3.9024 112.6910 37.5000 -5.7508 113.6331 38.5000 -7.9552 115.1643 39.5000 -10.4248 40.5000 -12.5736 41.5000 -15.3115 42.5000 -17.9045 43.5000 -18.1751 44.5000 -16.7383 45.5000 -15.0575 46.5000 -13.9012 47.5000 -11.2942 48.5000 -10.2560 49.5000 -9.0237 121.9349 50.5000 -8.2659 122.4808 51.5000 -7.8652 117.7651 52.5000 -7.2064 115.1917 53.5000 -7.6468 111.3038 54.5000 -7.9339 105.4709 55.5000 -8.0633 100.4229 56.5000 -8.4745 94.5790 57.5000 -9.4304 86.8628 58.5000 -9.7251 81.7492 59.5000 -10.4774 60.5000 -11.4583 61.5000 -12.2697 62.5000 -14.0158 63.5000 -15.1796 64.5000 -15.2157 65.5000 -16.2798 66.5000 -16.6394 67.5000 -18.0344 68.5000 -18.4549 69.5000 -18.8810 70.5000 -20.2879 71.5000 -19.6352 72.5000 -18.6731 73.5000 -18.9983 74.5000 -18.4995 75.5000 -17.7145 76.5000 -17.2714 77.5000 -16.7115 78.5000 -15.8696 79.5000 -15.6031 27.6114 116.0524 117.2932 124.9470 132.8508 139.3773 138.2434 134.0813 135.0111 130.3944 127.6272 72.8736 65.4782 58.6882 46.9878 40.4748 34.6221 25.6704 18.9638 3.6337
-2.1958
-15.9355
-27.5680
-29.9024
-35.4259
-42.2342
-50.3658
-50.5712
-63.3755
-64.7887
-67.0942
-75.1763 MA-WB55-20 Page 4 MA-WB55-20 80.5000 -15.2270
-75.6198 81.5000 -15.6275
-84.8827 82.5000 -15.3105
-84.6628 83.5000 -15.5617
-88.9274 84.5000 -15.4645
-93.2629 85.5000 -15.3123
-98.1383 86.5000 -14.7806
-103.1249 87.5000 -15.8660
-110.6245 88.5000 -15.4240
-109.2076 89.5000 -14.9574
-113.1232 90.5000 -14.8276
-124.2374 91.5000 -15.9017
-128.6655 92.5000 -15.6128
-132.6158 93.5000 -16.0839
-133.3907 94.5000 -15.9170
-138.8388 95.5000 -16.5717
-145.8923 96.5000 -16.7893
-147.7657 97.5000 -17.1852
-154.8148 98.5000 -17.4269
-162.2935 99.5000 -17.7366
-165.4276 100.5000
-18.9007 101.5000
-18.9551 102.5000
-19.2775 103.5000
-17.7468 104.5000
-18.9131 105.5000
-19.2503 106.5000
-19.7261 107.5000
-20.4381 108.5000
-19.2146 109.5000
-19.1848 110.5000
-20.2990 111.5000
-20.4034 112.5000
-20.9954 113.5000
-23.7830 114.5000
-21.8576 115.5000
-22.5270 116.5000
-23.1593 117.5000
-24.8785 118.5000
-24.6608 119.5000
-24.3414 120.5000
-23.2896 121.5000
-25.8235 122.5000
-25.2174 123.5000
-23.2620 124.5000
-23.6882 125.5000
-22.4708 126.5000
-23.3607 127.5000
-23.3367 128.5000
-21.5016 129.5000
-20.7719 130.5000
-21.6139 131.5000
-20.9327 132.5000
-20.7022 133.5000
-20.6797 134.5000
-21.1689 135.5000
-21.8256 136.5000
-25.0591 137.5000
-23.8306 138.5000
-24.5407 139.5000
-24.3590 140.5000
-24.1627 141.5000
-23.5210 142.5000
-24.8548 143.5000
-22.8365 144.5000
-23.6732 145.5000
-24.4895 146.5000
-23.9645 147.5000
-25.8930
-174.0763
-178.1982 177.2353 163.9288 157.1026 148.0461 145.2016 129.3931 123.8166 121.0079 112.2064 93.5003 87.6741 73.9829 65.2694 44.6949 38.8565 29.3354 7.1069
-8.3333
-34.0411
-55.2043
-68.9751
-91.5820
-100.7835
-115.1183
-139.0657
-147.4458
-176.1297 169.8778 148.7173 138.6791 125.2450 103.9563 91.8896 68.7929 54.7437 18.3639
-7.2620
-5.4352
-50.1297
-61.7171
-84.7974
-101.3283
-112.5160
-124.8507
-159.6854 157.3283 Page 5
-26.2926
-28.1772
-25.3642
-30.1918
-26.6418
-29.2109
-30.4167
-34.5373
-29.9406
-34.8427
-32.2561
-34.2157
-33.0029
-35.9119
-34.8624
-33.4757
-42.5965
-37.8707
-32.1036
-38.6544
-40.6515
-53.3068
-34.5646
-37.8391
-40.7604
-36.4604
-40.4009
-34.5270
-31.2877
-28.2880
-27.3343
-34.0546 MA-WB55-20 155.7455 105.4173 109.0440 69.9800 52.2609 45.7509 20.0395
-21.7887
-22.6260
-65.7393
-109.8417
-131.0675
-135.0726
-175.6306
-170.9561
-172.0983 117.6360
-63.0498
-3.6311 8.4820
-176.4970
-95.4545
-97.2331
-127.8620
-66.0297 28.3112
-4.7082
-24.4621
-32.9792
-60.6329
-37.1235
-34.3275 148.5000 149.5000 150.5000 151.5000 152.5000 153.5000 154.5000 155.5000 156.5000 157.5000 158.5000 159.5000 160.5000 161.5000 162.5000 163.5000 164.5000 165.5000 166.5000 167.5000 168.5000 169.5000 170.5000 171.5000 172.5000 173.5000 174.5000 175.5000 176.5000 177.5000 178.5000 179.5000 Page 6
1 2 3 4 5 6 7 | antenna pattern of SAA08-220570 | Parts List/Tune Up Info | 32.05 KiB | January 09 2014 / August 10 2014 |
5.1GHz 5.2GHz 5.3GHz 5.4GHz 5.5GHz 5.6GHz 5.7GHz 5.8GHz 5.9GHz
-14.9246
-14.8336
-14.0466
-13.2976
-13.1636
-12.1716
-10.4706
-9.5676
-9.8456
-9.8746
-9.8976
-9.7116
-9.7356
-10.5016
-10.9466
-11.2616
-11.7046
-12.9896
-13.3836
-13.7656
-14.4046
-13.7996
-15.3856
-18.6146
-23.2256
-25.7556
-17.8156
-13.4226
-10.0576
-9.1776
-10.2646
-14.0716
-18.3226
-14.9186
-11.6446
-7.2506
-5.5336
-4.8376
-5.9556
-7.2046
-9.3926
-8.1716
-16.1556
-13.5316
-14.0376
-12.6976
-12.4066
-11.5746
-9.9856
-10.0706
-8.8356
-8.4516
-7.4736
-7.4946
-7.4616
-8.0986
-8.8766
-10.2886
-11.5186
-10.1686
-11.1456
-9.7006
-9.2616
-8.5526
-10.7526
-11.0966
-12.8476
-13.3176
-11.6706
-10.4076
-9.6886
-10.9376
-10.8726
-12.4256
-15.0796
-13.9326
-11.4206
-9.7986
-7.0996
-5.4906
-5.0406
-5.7246
-7.3036
-10.1926
-12.2476
-12.6176
-13.6056
-14.6266
-17.8416
-25.4726
-22.5526
-16.2366
-10.8126
-8.3196
-5.4056
-4.5386
-2.6806
-1.7296
-1.8366
-1.8766
-2.7336
-3.4416
-6.6566
-9.5206
-13.8426
-16.9046
-12.8696
-8.8426
-8.3746
-7.8826
-8.8416
-10.3906
-13.5936
-22.8726
-31.9076
-18.3716
-14.1976
-11.3226
-11.0186
-12.9916
-15.7616
-15.4266
-13.0546
-11.8216
-12.8706
-16.9676
-14.4866
-12.7526
-12.9606
-12.0226
-11.4136
-11.4746
-10.4436
-11.0056
-11.9646
-11.5646
-13.7736
-12.4466
-12.6566
-12.4796
-9.7786
-8.6126
-6.4036
-6.3716
-4.6586
-4.1176
-3.7576
-3.0026
-3.6126
-3.1716
-2.6926
-2.5586
-2.2656
-1.9076
-2.0006
-2.0916
-2.6546
-4.0096
-5.4536
-6.5486
-7.4096
-7.5196
-7.0476
-5.4926
-5.1446
-4.3496
-4.8396
-5.0416
-180 -12.2026
-179 -12.1066
-178 -13.0516
-177 -12.5096
-176 -12.2366
-175 -11.6126
-174 -11.4956
-173 -12.8816
-172 -12.5966
-171 -13.5756
-170 -14.9056
-169 -15.0126
-168 -14.0686
-167 -10.5956
-9.3536
-7.0526
-5.1496
-4.6776
-3.9696
-3.7486
-4.0826
-5.0406
-6.2356
-8.2406
-9.3986
-9.6856
-7.2586
-5.5936
-4.8796
-4.3226
-4.9506
-6.5626
-8.1766
-9.4596
-9.4476
-8.4716
-7.2286
-5.9766
-5.7606
-6.1176
-6.4386
-8.0066
-166
-165
-164
-163
-162
-161
-160
-159
-158
-157
-156
-155
-154
-153
-152
-151
-150
-149
-148
-147
-146
-145
-144
-143
-142
-141
-140
-139
-8.9906
-12.2746
-14.0366
-23.7946
-14.9696
-11.4636
-10.4396
-11.5226
-14.8606
-8.8636
-8.8656
-129 -12.2246
-126 -11.7066
-125 -22.3956
-124 -11.1276
-5.2296
-3.6426
-3.9666
-6.0726
-8.2246
-6.7916
-5.0956
-5.4076
-7.0826
-7.2266
-6.8586
-6.4546
-5.3976
-5.5416
-3.8106
-2.1196
-0.6756
-1.7276
-4.2156
-3.4126
-1.7136
-1.7636
-4.3496
-4.9496
-2.8356
-2.6226
-2.0496 0.6304 3.2084
-138
-137
-136
-135
-134
-133
-132
-131
-130
-128
-127
-123
-122
-121
-120
-119
-118
-117
-116
-115
-114
-113
-112
-111
-110
-109
-108
-107
-106
-105
-104
-103
-102
-101
-100
-99
-98
-97
-96
-95
-6.9846
-5.7356
-5.3816
-7.7266
-9.5276
-10.6066
-10.4196
-8.4286
-8.0806
-10.2426
-11.8056
-11.2656
-10.8066
-9.1846
-10.1586
-11.5256
-18.8476
-24.9276
-9.7036
-6.8056
-5.2256
-6.1386
-7.5636
-8.6636
-8.7436
-7.8836
-7.4176
-7.1466
-6.6086
-5.9996
-5.2206
-5.5876
-8.4566
-11.0556
-13.9606
-14.4536
-5.9396
-3.2396
-2.1436
-0.4716 3.0144 4.7374 5.2764 5.3384
-10.5796
-8.7026
-10.0126
-9.2566
-11.8316
-12.7676
-18.3316
-28.6686
-14.9216
-11.2536
-9.7506
-10.8606
-9.7806
-5.9426
-4.5836
-3.8286
-4.4006
-5.4346
-3.9856
-3.9406
-4.8686
-8.4396
-15.7466
-18.6546
-12.4566
-11.8556
-16.9126
-24.8626
-12.0756
-13.2806
-15.4776
-9.2666
-7.6496
-10.7766
-16.4986
-16.3296
-9.6186
-3.9096
-2.7716
-4.3546
-3.9136 3.2584 5.7344 6.7374
-24.0756
-25.7216
-33.0826
-15.2186
-10.9066
-7.9186
-8.6806
-9.9326
-10.2616
-8.2156
-7.0996
-10.8336
-27.4606
-8.7666
-5.6806
-4.6356
-5.0666
-9.7126
-15.3666
-15.7186
-9.3996
-5.1306
-5.0296
-8.3536
-12.3196
-13.8116
-7.9346
-4.5646
-4.7306
-11.8966
-15.6156
-3.6346
-2.1756
-4.4636
-8.1306
-10.0646
-6.8826
-6.0756
-5.4556
-5.4426
-1.4766 1.9434 2.7044 2.3874
-5.7856
-6.5166
-6.6066
-7.2276
-8.2976
-7.6046
-8.5966
-8.8416
-8.9916
-6.1446
-5.1506
-5.0626
-7.6006
-13.2056
-18.0656
-16.4326
-17.5006
-20.0766
-23.3666
-19.5826
-15.3266
-10.4546
-10.1166
-9.4496
-6.9196
-4.2546
-3.6706
-4.8686
-7.9236
-7.0716
-3.6226 0.0714 0.6094 0.7054 1.5024 2.7194 3.2794 1.4264 0.1054 0.9904 2.7674 3.4314 3.4874 4.3834
-94
-93
-92
-91
-90
-89
-88
-87
-86
-85
-84
-83
-82
-81
-80
-79
-78
-77
-76
-75
-74
-73
-72
-71
-70
-69
-68
-67
-66
-65
-64 3.8774 4.7334 6.4624 7.3694 7.0924 6.4224 5.5854 5.7354 5.0794 3.3034
-0.2436
-1.1716
-0.3516
-0.8886
-2.4356
-5.5656
-6.0156
-3.6026
-2.1176
-0.0626 1.2314 2.1104 2.2874 0.1104
-2.6356
-7.0546
-3.1886
-1.4226
-1.5316
-4.0536
-6.8676
-63 -11.0786
-62 -13.0596
-61 -11.6426
-60
-59
-58
-57
-56
-55
-54
-53
-52
-51
-7.0976
-5.5966
-4.5056
-5.2126
-6.8356
-7.0736
-5.6436
-5.4126
-6.2006
-9.3246 6.4484 7.2824 7.7084 7.5804 7.9854 8.0434 7.3394 4.8504 4.2724 4.5824 3.6934 1.6824
-3.8266
-11.1986
-19.1126
-17.3286
-10.7786
-7.9486
-6.2506
-6.0936
-8.6036
-19.9466
-10.6646
-6.4686
-6.1526
-11.4376
-21.4326
-7.6366
-5.5646
-6.2146
-9.0816
-9.6516
-10.0196
-11.9586
-15.0346
-13.1176
-11.2726
-9.5256
-11.5886
-18.3096
-15.8046
-13.2356
-11.7366
-12.3196 6.3014 6.0634 7.5294 8.5404 9.6464 9.7994 8.5174 6.8014 5.3274 6.0834 6.6624 4.4194 0.8664
-11.8966
-14.1116
-6.5156
-8.1696
-13.3606
-8.5506
-5.9236
-6.6876
-12.3106
-22.3466
-14.3936
-11.2046
-10.9026
-12.4096
-7.8776
-1.0446 2.0024 3.0304 1.7714
-2.0016
-4.8896
-5.2516
-3.5286
-2.1716
-2.1516
-0.0226 1.3044 1.6884 1.1594 0.0104
-2.4976 4.2874 6.8794 7.2774 6.8364 7.4774 8.4924 8.0884 6.6254 5.9084 6.3804 4.8704
-3.2656
-7.1366
-1.6956
-3.4696
-11.0436
-3.2546
-2.9976
-8.0156
-5.8226
-1.4616
-3.2416
-15.0386
-4.2316
-1.7156
-2.3686
-2.6016
-1.7066
-2.1926
-15.3266
-10.5156
-1.4146
-0.2746
-2.4616
-13.5396
-14.5446
-7.4976
-7.1606
-7.0516
-7.4166
-11.7166
-14.0476
-5.5676
-1.3536 5.8324 6.5044 5.7494 5.8024 6.7904 6.6084 3.9434 4.0134 4.9774 3.7364
-1.1666
-1.1056
-2.6646
-13.0156
-3.1856 1.0664
-0.0396 0.5394 2.8784 2.6804
-1.5506
-10.3006
-5.5226
-6.4196
-8.4836
-6.2216
-6.6556
-11.9056
-9.1096
-4.9806
-7.1736
-19.5886
-5.5936
-4.1016
-6.2046
-12.1826
-11.6426
-9.8486
-11.2576
-8.0886
-3.3406
-2.5356
-4.3876
-9.5526
-50 -13.9606
-49 -16.9426
-48 -20.4596
-47 -28.9256
-46 -20.7456
-45 -12.2356
-44
-43
-42
-41
-40
-39
-38
-37
-36
-35
-34
-7.7226
-6.2006
-5.6816
-5.7206
-5.6566
-5.9996
-6.0726
-5.7536
-6.4086
-7.4086
-8.9116
-33 -11.3666
-32 -14.3826
-31 -15.4636
-30 -12.7766
-29 -10.2736
-28
-27
-26
-25
-9.8616
-8.9866
-9.9006
-9.2446
-24 -10.5966
-23 -11.2686
-22 -11.3016
-21 -10.3886
-20
-19
-18
-17
-16
-15
-14
-13
-12
-11
-10
-9
-8
-7
-8.0246
-6.9806
-5.8356
-5.1016
-4.6196
-4.5016
-4.0076
-3.9006
-3.8606
-4.0896
-4.4436
-4.9116
-5.6186
-6.1736
-12.7916
-9.9366
-6.5776
-5.4456
-5.4146
-6.9626
-8.6216
-10.0446
-7.4386
-4.0566
-3.4726
-3.1816
-3.1956
-4.4876
-6.7206
-9.0986
-10.6006
-10.7186
-10.9536
-10.4066
-9.0306
-8.4706
-7.7666
-7.9416
-7.6616
-9.1126
-10.0986
-10.9926
-11.0436
-9.6886
-8.5496
-6.9216
-6.2046
-5.4206
-4.5736
-4.3456
-4.2146
-4.1056
-4.7156
-4.6056
-4.8496
-4.9916
-5.6286
-6.1286
-3.1606
-2.2216
-1.2416
-1.8216
-2.8626
-3.8706
-2.5416
-1.1836
-0.2396
-0.6576
-3.2796
-6.0386
-17.6526
-17.8296
-14.3266
-12.0256
-11.5906
-12.0286
-13.2206
-12.3106
-11.5086
-10.7756
-8.0976
-5.8896
-3.9086
-3.2806
-2.6836
-2.4546
-2.3416
-3.1366
-4.5826
-6.6356
-9.3056
-15.9886
-17.8296
-14.6046
-10.0986
-8.0106
-6.6706
-5.6606
-5.6446
-5.2916
-5.9216
-6.0626
-0.5406
-2.0946
-8.5666
-13.2286
-7.7526
-5.4146
-8.7246
-10.2166
-7.5096
-5.4896
-3.9986
-5.1796
-7.8296
-8.9836
-7.9446
-5.2376
-4.0946
-4.4966
-5.6376
-7.6896
-10.7746
-14.9546
-20.5846
-18.1796
-15.3076
-11.0946
-8.6226
-6.3856
-4.1156
-3.7076
-2.3986
-2.1826
-2.0546
-2.5876
-3.5726
-4.1166
-5.2476
-6.3086
-7.9996
-9.8856
-11.1056
-11.9446
-13.2796
-12.6396
-7.2996
-5.1616
-4.6896
-8.7816
-14.5686
-17.4066
-12.5646
-13.2896
-10.9506
-6.7896
-2.0666
-1.1226
-1.0576
-2.4626
-5.6366
-13.0506
-13.9126
-11.1906
-8.4486
-8.3756
-8.1336
-6.2556
-5.8576
-4.5596
-4.5696
-5.2716
-6.2846
-6.5186
-4.4786
-2.7666
-0.7916
-0.2076 0.5544 0.8754 0.7694 0.0154
-0.4306
-0.9046
-1.8776
-3.6126
-4.3986
-5.5696
-6.7806
-8.2356
-6
-5
-4
-3
-6.8096
-8.0336
-8.7426
-9.6756
-2 -10.1046
-1 -10.9636 0 -12.8996 1 -13.9026 2 -15.6166 3 -17.8726 4 -20.4376 5 -22.6286 6 -28.9816 7 -28.6206 8 -24.4456 9 -17.6686 10 -15.0956 11 -12.4536 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
-9.7976
-7.7666
-6.5036
-5.5936
-4.3836
-3.5656
-3.0756
-2.7246
-3.1416
-3.0136
-3.6896
-4.2966
-4.8126
-6.1396
-6.3816
-6.3816
-7.2276
-7.6646
-8.7166 31 -12.1436 32 -17.7466 33 -34.2426 34 -17.4106 35 -12.3416 36 -10.1616 37
-9.3866
-6.9216
-7.6966
-7.5116
-8.4396
-8.4806
-9.6036
-10.9956
-11.2926
-11.4806
-12.2196
-12.2756
-14.2026
-16.2766
-17.4996
-20.7406
-22.2726
-20.3916
-15.1846
-12.9706
-11.1646
-10.4966
-9.1836
-8.7236
-8.2606
-8.2436
-9.1056
-8.7966
-7.8306
-7.2736
-7.3476
-7.2716
-7.5696
-7.7236
-8.9226
-9.0026
-10.3656
-11.3426
-12.0916
-12.5816
-12.8976
-12.2306
-10.5376
-8.2206
-6.9826
-6.7776
-7.5696
-8.2626
-9.7896
-11.8246
-12.9756
-15.5606
-16.3516
-19.5966
-16.4376
-17.0976
-14.7046
-11.4626
-10.5526
-10.3086
-8.8156
-8.0736
-7.4996
-8.0686
-7.1196
-7.7906
-7.2506
-6.5966
-6.1636
-6.2036
-5.2856
-4.8626
-4.7646
-5.2826
-5.9506
-8.0706
-9.8926
-10.8286
-11.0966
-10.4106
-11.0536
-12.8676
-14.9286
-14.0046
-10.2206
-9.1036
-8.3156
-8.8396
-11.2646
-14.0116
-11.8246
-11.2886
-10.1386
-9.0936
-8.1656
-7.5036
-7.1376
-6.1736
-5.7226
-5.6666
-5.6596
-5.8986
-6.4536
-7.2616
-8.4156
-10.5876
-11.7156
-11.9276
-8.6096
-7.6936
-5.2796
-3.9876
-2.7626
-2.5756
-2.6466
-3.5516
-5.2456
-7.6266
-13.3816
-18.6696
-14.1926
-12.6086
-9.8436
-10.9956
-13.4316
-11.9526
-7.5466
-5.3096
-3.5246
-4.2266
-6.7536
-12.3826
-13.6626
-9.5736
-11.5446
-12.3766
-13.9706
-15.6516
-17.7246
-19.4486
-15.8836
-14.8426
-13.9906
-12.4906
-11.4026
-11.9156
-11.9196
-10.9026
-12.0806
-10.6666
-9.2156
-7.6966
-5.4436
-4.1826
-3.4666
-2.2036
-1.8316
-1.7986
-2.4296
-3.6496
-5.3426
-7.7746
-9.4676
-9.7106
-8.9506
-8.9456
-10.5216
-18.1346
-30.7846
-14.1416
-10.1706
-10.0526
-11.7386
-15.4396
-10.1566
-5.8456
########
38
-9.9426 39 -11.2956 40 41 42
-9.9336
-9.3216
-9.0796 43 -10.4706 44 -11.1716 45 -15.2146 46 -19.7726 47 -18.1856 48 -18.6376 49 -17.1796 50 -15.2986 51 -10.8196 52 53
-9.5266
-9.0226 54 -10.0716 55 56 57 58 59 60
-9.9326
-8.1116
-5.3926
-5.0026
-5.3916
-9.3106 61 -12.3456 62 -12.9586 63 -10.9376 64 65 66 67 68 69 70 71 72 73 74 75 76 77
-7.6896
-5.4496
-3.6996
-4.7136
-6.9686
-6.5966
-1.9986
-0.4996
-0.4586
-2.7416
-4.5626
-5.4906
-6.2626
-7.7866 78 -10.0826 79 80 81
-9.0276
-6.5256
-3.4216
-5.6676
-5.7816
-6.1366
-7.7616
-10.4906
-11.8466
-14.4176
-17.2866
-23.2006
-28.1396
-21.2156
-18.7766
-21.8436
-25.1746
-16.2566
-10.4116
-9.9736
-11.2296
-20.7996
-14.2306
-10.2596
-7.0386
-11.0816
-17.0666
-12.1136
-7.9366
-9.7216
-22.9596
-11.4516
-8.2666
-6.7016
-10.7826
-19.5826
-17.6296
-26.3716
-17.2146
-9.0046
-9.0976
-10.9566
-12.8406
-11.5326
-16.8756
-4.5396 0.5334
-13.0476
-10.5366
-7.7686
-6.0126
-5.6576
-7.4106
-10.8496
-21.1666
-24.2666
-17.1766
-17.4146
-30.7406
-17.1086
-8.8006
-5.4196
-4.5286
-4.4006
-6.5146
-10.4126
-20.2666
-25.1736
-24.4946
-15.4376
-8.3766
-6.1166
-6.1526
-9.4186
-8.9476
-6.3986
-6.2356
-7.6706
-9.7266
-10.1976
-10.1626
-13.8676
-15.3556
-18.1556
-10.0856
-5.7396
-6.0476
-9.0896
-1.7946 0.4894
-0.1636
-6.8916
-3.7636
-3.1986
-5.9536
-12.8196
-12.7146
-8.6246
-8.2516
-11.6676
-12.0586
-5.4346
-3.6786
-4.8606
-12.3536
-13.0516
-6.3966
-3.7976
-4.4196
-6.1146
-7.0576
-7.6066
-12.9746
-16.5526
-6.6746
-5.4976
-8.8826
-8.2056
-6.3436
-5.1266
-6.4676
-5.5686
-7.2736
-11.0206
-5.4076
-1.2746
-2.8556
-8.9076
-6.3156
-1.9966
-4.5316
-14.8316
-5.7036
-4.0996
-2.4626
-1.4276
-2.6726
-6.8126
-12.4876
-11.1186
-7.2946
-8.7226
-14.6966
-8.7086
-5.9756
-5.1636
-10.3436
-9.5026
-4.1306
-2.4096
-3.0096
-9.6386
-13.7146
-10.2836
-12.9196
-10.3756
-4.9856
-2.1886
-4.9676
-11.0346
-11.8946
-7.3156
-9.1616
-20.5436
-15.9476
-15.8266
-16.4546
-7.1016
-8.2296
-10.6566
-1.4116 0.2604
-1.2956
-1.9256 1.2004 2.4964
-3.1676
-5.0646 1.5494 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112
-2.1166
-1.5016 0.3554 3.7414 4.7834 4.7324 4.4854 4.9664 5.4524 5.0804 4.2774 3.3294 2.9054 2.2044
-0.3866
-1.7306
-1.9296
-2.5416
-4.5036
-2.4296 0.1284 0.0704
-2.2326
-3.4856
-1.7346
-1.4606
-5.0296
-9.1896
-7.3916
-5.0176
-6.7856 113 -12.6406 114 -21.8386 115 -27.5546 116 -24.4006 117 -16.4456 118 -11.1946 119 120 121 122 123
-9.3946
-6.7046
-4.9696
-4.8116
-7.3416 124 -10.5896 125
-8.8976 2.9754 2.9764 3.7544 5.2624 6.2584 5.6324 5.2844 6.2364 6.3454 5.1514 3.2474 4.2824 4.8164 3.2074
-0.5306
-1.3476
-1.3716
-5.2006
-10.2566
-11.7586
-10.7726
-11.7376
-7.6236
-3.8946
-4.3056
-6.9006
-8.4166
-7.4216
-9.0986
-11.2006
-16.6756
-15.6356
-11.3526
-8.2776
-6.9596
-9.2316
-12.8176
-9.2536
-5.7166
-4.6806
-5.0136
-7.5816
-10.5996
-9.0796
-1.7326 2.9954 5.5674 6.7824 6.4404 6.0444 5.9254 6.0944 7.3414 8.0204 7.3494 4.9294 4.3794 5.3014 4.9474 2.1154
-1.3176
-5.9036
-14.1446
-18.4096
-13.2216
-22.6786
-9.0496
-3.5426
-1.5446
-2.7946
-6.3296
-11.9536
-15.0256
-25.8736
-18.9976
-16.5716
-13.8196
-9.4926
-7.5226
-5.2476
-5.6096
-6.8526
-9.7516
-10.4276
-9.1136
-6.0436
-7.5366
-10.5006 1.1884 2.3994 1.8484 4.4054 6.6524 7.7164 6.4844 5.7634 6.9514 7.5674 6.5394 4.1204 1.9884 1.2254
-1.2656
-5.1076
-6.9106
-9.4516
-28.5446
-15.4436
-11.7986
-15.2806
-9.3036
-7.6416
-15.9176
-14.9126
-7.3156
-6.3456
-10.8156
-15.5116
-8.1486
-5.8676
-5.4676
-5.5636
-6.1466
-12.0336
-16.1166
-8.9596
-5.6746
-7.4776
-11.5356
-32.3286
-13.0586
-9.8466 1.0744
-1.9006 2.1794 4.8064 4.2204 4.8524 6.6724 6.3224 4.6944 5.4274 5.8754 3.3244
-0.6546 0.4334 0.3114
-3.3546
-8.9196
-10.0346
-2.4746
-0.9556
-2.1196
-3.8306
-0.6496 1.0044
-1.9486
-6.6096
-10.2506
-4.6276
-2.8326
-3.0176
-6.2096
-6.4266
-3.3076
-2.5066
-4.6156
-12.4446
-11.1036
-8.9726
-7.9866
-9.1016
-12.6616
-11.6736
-5.7386
-3.9986 126 127 128
-5.2006
-4.3926
-6.3296 129 -12.0266 130 -18.3566 131 -15.4626 132 -15.7096 133 -23.0486 134 -13.7166 135 136 137 138 139 140 141 142 143 144 145 146
-7.1626
-4.7536
-4.5836
-5.0406
-6.5566
-6.7706
-5.5066
-4.0296
-3.8456
-4.0086
-6.2056
-7.4816 147 -10.9846 148 -11.9836 149 150 151 152 153 154 155 156
-9.5316
-7.5906
-5.6756
-4.8696
-5.0246
-6.0176
-7.3556
-9.5036 157 -13.7416 158 -14.3486 159 -11.3446 160 161 162 163 164 165 166 167 168 169
-7.9606
-6.6546
-5.7236
-4.6956
-4.5386
-4.2346
-4.0636
-4.2286
-4.5536
-5.0596
-4.7346
-3.2196
-2.8676
-4.5006
-9.3406
-9.6426
-5.8106
-4.5506
-4.3986
-6.0796
-7.9136
-11.9826
-12.8266
-11.0686
-8.9496
-8.2266
-8.8466
-10.6726
-15.7506
-27.3546
-20.8236
-15.6236
-13.3066
-12.5316
-12.4796
-14.8476
-17.8666
-17.8876
-15.0646
-12.4386
-11.7926
-12.1056
-15.0556
-20.4486
-29.0706
-32.8986
-20.4636
-19.8966
-14.5286
-13.3846
-12.4796
-12.2246
-12.4596
-12.9206
-21.4316
-10.0016
-7.0446
-6.7646
-8.2396
-11.6386
-13.4796
-11.6886
-9.5676
-9.6386
-11.2936
-18.2206
-18.3256
-8.3546
-6.9106
-5.9316
-5.9866
-6.5356
-7.2856
-7.9796
-8.3906
-9.8906
-11.6226
-18.7086
-33.2216
-13.3396
-11.0206
-8.8026
-9.4286
-9.7466
-13.7086
-18.4926
-31.2696
-18.7546
-12.2246
-9.8616
-8.2186
-7.6536
-7.1626
-7.4396
-8.3336
-8.9576
-9.3476
-11.0596
-8.5956
-7.7686
-9.0446
-7.6026
-5.5876
-5.2656
-5.5316
-8.9516
-9.3006
-11.3906
-15.2916
-19.0926
-11.7166
-8.3486
-7.0936
-10.1736
-16.2266
-13.2786
-8.5776
-6.7486
-6.7966
-8.3066
-10.3176
-19.6766
-19.7906
-11.0916
-8.9936
-7.2156
-8.2966
-7.6566
-9.8106
-14.5976
-16.3866
-15.3666
-9.6526
-7.1726
-6.2726
-5.4376
-4.9096
-4.6806
-5.1796
-5.8866
-7.0576
-8.8606
-4.8446
-9.1106
-11.7426
-10.6276
-9.8906
-13.8366
-14.9736
-17.5786
-14.1846
-11.5676
-9.1786
-8.6816
-8.0316
-9.6776
-10.6196
-12.4926
-9.3726
-7.5966
-7.2046
-7.2036
-7.8956
-9.2076
-9.9066
-9.4886
-9.3786
-7.6346
-7.7336
-7.3656
-8.2346
-9.2236
-12.1046
-13.2826
-11.3246
-8.7296
-6.6046
-5.8166
-5.8596
-5.1736
-5.7816
-6.6746
-7.5886
-8.8136
-11.1136
-14.8626 170 171 172 173 174 175 176
-5.5356
-6.2786
-7.2216
-7.2596
-8.3306
-8.9306
-9.5676 177 -10.0346 178 -11.2416 179 -11.7276 180 -12.2566
-14.1556
-14.0226
-14.7266
-14.1196
-14.6086
-15.0156
-14.5456
-14.8966
-15.4166
-15.1596
-13.8036
-17.4216
-16.4536
-20.6526
-19.3516
-16.8486
-14.6556
-15.4176
-14.0066
-14.3016
-13.8816
-8.6126
-10.5846
-11.0726
-11.5306
-11.0966
-12.6456
-11.7076
-11.6206
-11.9756
-12.1646
-13.1476
-16.0236
-22.0476
-25.7416
-23.1786
-22.5996
-23.1726
-17.9326
-19.2416
-15.4246
-15.9916
-15.0326
frequency | equipment class | purpose | ||
---|---|---|---|---|
1 | 2016-07-30 | 5860 ~ 5920 | TNB - Licensed Non-Broadcast Station Transmitter | Class II Permissive Change |
2 | 2016-06-24 | 5745 ~ 5825 | NII - Unlicensed National Information Infrastructure TX | |
3 | 2014-10-08 | 5180 ~ 5240 | NII - Unlicensed National Information Infrastructure TX | |
4 | 2014-05-27 | 5660 ~ 5700 | NII - Unlicensed National Information Infrastructure TX | |
5 | 2014-04-02 | 5860 ~ 5920 | TNB - Licensed Non-Broadcast Station Transmitter | Original Equipment |
6 | 2014-04-01 | 5190 ~ 5230 | NII - Unlicensed National Information Infrastructure TX | |
7 | 5755 ~ 5795 | DTS - Digital Transmission System |
app s | Applicant Information | |||||
---|---|---|---|---|---|---|
1 2 3 4 5 6 7 | Effective |
2016-07-30
|
||||
1 2 3 4 5 6 7 |
2016-06-24
|
|||||
1 2 3 4 5 6 7 |
2014-10-08
|
|||||
1 2 3 4 5 6 7 |
2014-05-27
|
|||||
1 2 3 4 5 6 7 |
2014-04-02
|
|||||
1 2 3 4 5 6 7 |
2014-04-01
|
|||||
1 2 3 4 5 6 7 | Applicant's complete, legal business name |
Proxim Wireless Corporation
|
||||
1 2 3 4 5 6 7 | FCC Registration Number (FRN) |
0005850607
|
||||
1 2 3 4 5 6 7 | Physical Address |
47633 Westinghouse Drive
|
||||
1 2 3 4 5 6 7 |
Fremont, CA
|
|||||
1 2 3 4 5 6 7 |
United States
|
|||||
app s | TCB Information | |||||
1 2 3 4 5 6 7 | TCB Application Email Address |
d******@compliancetesting.com
|
||||
1 2 3 4 5 6 7 |
T******@TIMCOENGR.COM
|
|||||
1 2 3 4 5 6 7 |
S******@phoenix-testlab.de
|
|||||
1 2 3 4 5 6 7 | TCB Scope |
B2: General Mobile Radio And Broadcast Services equipment in the following 47 CFR Parts 22 (non-cellular) 73, 74, 90, 95, 97, & 101 (all below 3 GHz)
|
||||
1 2 3 4 5 6 7 |
A4: UNII devices & low power transmitters using spread spectrum techniques
|
|||||
app s | FCC ID | |||||
1 2 3 4 5 6 7 | Grantee Code |
HZB
|
||||
1 2 3 4 5 6 7 | Equipment Product Code |
XB92WFR
|
||||
app s | Person at the applicant's address to receive grant or for contact | |||||
1 2 3 4 5 6 7 | Name |
C******** v****
|
||||
1 2 3 4 5 6 7 | Title |
Sr. Regulatory and Compliance Manager
|
||||
1 2 3 4 5 6 7 | Telephone Number |
408 3********
|
||||
1 2 3 4 5 6 7 | Fax Number |
408 3********
|
||||
1 2 3 4 5 6 7 |
c******@proxim.com
|
|||||
app s | Technical Contact | |||||
1 2 3 4 5 6 7 | Firm Name |
Proxim Wireless Corporation
|
||||
1 2 3 4 5 6 7 |
Sporton International Inc.
|
|||||
1 2 3 4 5 6 7 | Name |
C******** H********
|
||||
1 2 3 4 5 6 7 |
V****** H******
|
|||||
1 2 3 4 5 6 7 | Physical Address |
9F-1,No.146,Wenxing Rd.,Guishan Township
|
||||
1 2 3 4 5 6 7 |
No.8, Lane 724, Bo-ai St., Jhubei City
|
|||||
1 2 3 4 5 6 7 |
Taoyuan
|
|||||
1 2 3 4 5 6 7 |
Hsinchu, 302
|
|||||
1 2 3 4 5 6 7 |
Taiwan
|
|||||
1 2 3 4 5 6 7 | Telephone Number |
88632******** Extension:
|
||||
1 2 3 4 5 6 7 |
886-3******** Extension:
|
|||||
1 2 3 4 5 6 7 | Fax Number |
88632********
|
||||
1 2 3 4 5 6 7 |
886-3********
|
|||||
1 2 3 4 5 6 7 |
C******@proxim.com
|
|||||
1 2 3 4 5 6 7 |
v******@sporton.com.tw
|
|||||
app s | Non Technical Contact | |||||
1 2 3 4 5 6 7 | Firm Name |
Proxim Wireless Corporation
|
||||
1 2 3 4 5 6 7 |
Sporton International Inc.
|
|||||
1 2 3 4 5 6 7 | Name |
C******** H********
|
||||
1 2 3 4 5 6 7 |
V**** H****
|
|||||
1 2 3 4 5 6 7 | Physical Address |
9F-1,No.146,Wenxing Rd.,Guishan Township
|
||||
1 2 3 4 5 6 7 |
No.8, Lane 724, Bo-ai St., Jhubei City
|
|||||
1 2 3 4 5 6 7 |
Taoyuan
|
|||||
1 2 3 4 5 6 7 |
Hsinchu, 302
|
|||||
1 2 3 4 5 6 7 |
Taiwan
|
|||||
1 2 3 4 5 6 7 | Telephone Number |
88632******** Extension:
|
||||
1 2 3 4 5 6 7 |
886-3******** Extension:
|
|||||
1 2 3 4 5 6 7 | Fax Number |
88632********
|
||||
1 2 3 4 5 6 7 |
886-3********
|
|||||
1 2 3 4 5 6 7 |
C******@proxim.com
|
|||||
1 2 3 4 5 6 7 |
v******@sporton.com.tw
|
|||||
app s | Confidentiality (long or short term) | |||||
1 2 3 4 5 6 7 | Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | No | ||||
1 2 3 4 5 6 7 | Yes | |||||
1 2 3 4 5 6 7 | Long-Term Confidentiality Does this application include a request for confidentiality for any portion(s) of the data contained in this application pursuant to 47 CFR § 0.459 of the Commission Rules?: | No | ||||
if no date is supplied, the release date will be set to 45 calendar days past the date of grant. | ||||||
app s | Cognitive Radio & Software Defined Radio, Class, etc | |||||
1 2 3 4 5 6 7 | Is this application for software defined/cognitive radio authorization? | No | ||||
1 2 3 4 5 6 7 | Equipment Class | TNB - Licensed Non-Broadcast Station Transmitter | ||||
1 2 3 4 5 6 7 | NII - Unlicensed National Information Infrastructure TX | |||||
1 2 3 4 5 6 7 | DTS - Digital Transmission System | |||||
1 2 3 4 5 6 7 | Description of product as it is marketed: (NOTE: This text will appear below the equipment class on the grant) | Access Point | ||||
1 2 3 4 5 6 7 | 802.11 a/n PCIe Module | |||||
1 2 3 4 5 6 7 | 802.11a/n PCIe Module | |||||
1 2 3 4 5 6 7 | Related OET KnowledgeDataBase Inquiry: Is there a KDB inquiry associated with this application? | No | ||||
1 2 3 4 5 6 7 | Yes | |||||
1 2 3 4 5 6 7 | Modular Equipment Type | Single Modular Approval | ||||
1 2 3 4 5 6 7 | Limited Single Modular Approval | |||||
1 2 3 4 5 6 7 | Purpose / Application is for | Class II Permissive Change | ||||
1 2 3 4 5 6 7 | Original Equipment | |||||
1 2 3 4 5 6 7 | Composite Equipment: Is the equipment in this application a composite device subject to an additional equipment authorization? | Yes | ||||
1 2 3 4 5 6 7 | Related Equipment: Is the equipment in this application part of a system that operates with, or is marketed with, another device that requires an equipment authorization? | No | ||||
1 2 3 4 5 6 7 | Grant Comments | Output Power listed is conducted. This modular transmitter module is approved only for use in DSRCS onboard units and roadside units. To satisfy RF exposure, only those antenna(s) tested with the device or similar antenna(s) with equal or lesser gain may be used with this transmitter and must be installed to provide a separation distance of at least 20 cm from all persons and must not be co-located or operating with any other antenna or transmitter, except in accordance with the FCC multi-transmitter policy. End-users and installers must be provided with the antenna installation instructions and transmitter operating conditions for satisfying RF exposure compliance. This device is approved with the incorporated unlicensed DTS and UNII transmitter certified under the same FCC ID. C2PC to add 4.9GHz band operation. Output Power listed is conducted. To satisfy RF exposure, only those antenna(s) tested with the device or similar antenna(s) with equal or lesser gain may be used with this transmitter and must be installed to provide a separation distance of at least 20 cm from all persons and must not be co-located or operating with any other antenna or transmitter, except in accordance with the FCC multi-transmitter policy. End-users and installers must be provided with the antenna installation instructions and transmitter operating conditions for satisfying RF exposure compliance. This device is approved with the incorporated unlicensed DTS and UNII transmitter certified under the same FCC ID. The 4.9GHz band operation is only approved only for hosts identified in the EMC report. | ||||
1 2 3 4 5 6 7 | Output Power listed is the maximum combined conducted output power as indicated in the filing. This OEM module is approved for use in products operating as mobile or fixed transmitting device. The only antennas approved for use with this module are those documented in the filing, and must be installed in the manner specified therein. The device with its antennas must be operated with a separation distance of at least 20 cm from all persons and must not be co-located or operating with any other antenna or transmitter, except in accordance with the FCC multi-transmitter policy. The device is approved together with the incorporated DTS transmitter certified under the same FCC ID. End users may not be provided with the module installation instructions. Device is operating in a 2T2R Spatial Multiplexing MIMO configuration as described in this filing. This device has 5, 10, 20, and 40 MHz bandwidth modes. (Date of Grant: 10/08/2014) Class II Permissive Change: This Class II Permissive Change is to update the 5 GHz Band 2a 2c and 3 to FCC New Rules from Old Rules. 5 GHz band 3 is updated to 15.407(b)(4)(ii) of New Rules (ET Docket No. 13-49; FCC 16-24). | |||||
1 2 3 4 5 6 7 | Class II Permissive Change: Output Power listed is the maximum combined conducted output power as indicated in the filing. This OEM module is approved for use in products operating as mobile or fixed transmitting device. The only antennas approved for use with this module are those documented in the filing, and must be installed in the manner specified therein. The device with its antennas must be operated with a separation distance of at least 20 cm from all persons and must not be co-located or operating with any other antenna or transmitter, except in accordance with the FCC multi-transmitter policy. The device is approved together with the incorporated DTS transmitter certified under the same FCC ID. End users may not be provided with the module installation instructions. Device is operating in a 2T2R Spatial Multiplexing MIMO configuration as described in this filing. When operating in 802.11n 40 MHz mode, the operating frequency segment is limited to 5190 to 5230 MHz. This device has 5, 10, 20, and 40 MHz bandwidth modes. | |||||
1 2 3 4 5 6 7 | Output Power listed is the maximum combined conducted output power as indicated in the filing. This OEM module is approved for use in products operating as mobile or fixed transmitting device. The only antennas approved for use with this module are those documented in the filing, and must be installed in the manner specified therein. The device with its antennas must be operated with a separation distance of at least 20 cm from all persons and must not be co-located or operating with any other antenna or transmitter, except in accordance with the FCC multi-transmitter policy. End users may not be provided with the module installation instructions. Device is operating in a 2T2R Spatial Multiplexing MIMO configuration as described in this filing. Operating of this device in the 5150 MHz to 5250 MHz range is restricted to indoor use only. | |||||
1 2 3 4 5 6 7 | Output Power listed is conducted. This modular transmitter module is approved only for use in DSRCS onboard units and roadside units. To satisfy RF exposure, only those antenna(s) tested with the device or similar antenna(s) with equal or lesser gain may be used with this transmitter and must be installed to provide a separation distance of at least 20 cm from all persons and must not be co-located or operating with any other antenna or transmitter, except in accordance with the FCC multi-transmitter policy. End-users and installers must be provided with the antenna installation instructions and transmitter operating conditions for satisfying RF exposure compliance. This device is approved with the incorporated unlicensed DTS and UNII transmitter certified under the same FCC ID. | |||||
1 2 3 4 5 6 7 | Output Power listed is the maximum combined conducted output power as indicated in the filing. This OEM module is approved for use in products operating as mobile or fixed transmitting device. The only antennas approved for use with this module are those documented in the filing, and must be installed in the manner specified therein. The device with it's antennas must be operated with a separation distance of at least 20 cm from all persons and must not be co-located or operating with any other antenna or transmitter, except in accordance with the FCC multi-transmitter policy. The device is approved together with the incorporated DTS transmitter certified under the same FCC ID. End users may not be provided with the module installation instructions. Device is operating in a 2T2R Spatial Multiplexing MIMO configuration as described in this filing. When operating in 802.11n 40 MHz mode, the operating frequency segment is limited to 5190 to 5230 MHz. Operating of this device in the 5150 MHz to 5250 MHz range is restricted to indoor use only. | |||||
1 2 3 4 5 6 7 | Output Power listed is the maximum combined conducted output power as indicated in the filing. This OEM module is approved for use in products operating as mobile or fixed transmitting device. The only antennas approved for use with this module are those documented in the filing, and must be installed in the manner specified therein. The device with it's antennas must be operated with a separation distance of at least 20 cm from all persons and must not be co-located or operating with any other antenna or transmitter, except in accordance with the FCC multi-transmitter policy. The device is approved together with the incorporated UNII transmitter certified under the same FCC ID. End users may not be provided with the module installation instructions. Device is operating in a 2T2R Spatial Multiplexing MIMO configuration as described in this filing. When operating in 802.11n, 40 MHz mode, the operating frequency segment is limited to5755 to 5795 MHz. | |||||
1 2 3 4 5 6 7 | Is there an equipment authorization waiver associated with this application? | No | ||||
1 2 3 4 5 6 7 | If there is an equipment authorization waiver associated with this application, has the associated waiver been approved and all information uploaded? | No | ||||
app s | Test Firm Name and Contact Information | |||||
1 2 3 4 5 6 7 | Firm Name |
Compliance Testing, LLC
|
||||
1 2 3 4 5 6 7 |
SPORTON International Inc.
|
|||||
1 2 3 4 5 6 7 |
SPORTON INTERNATIONAL INC.
|
|||||
1 2 3 4 5 6 7 |
Sporton International Inc.
|
|||||
1 2 3 4 5 6 7 | Name |
M**** S******
|
||||
1 2 3 4 5 6 7 |
S****** J******
|
|||||
1 2 3 4 5 6 7 |
A**** C******
|
|||||
1 2 3 4 5 6 7 | Telephone Number |
480-9********
|
||||
1 2 3 4 5 6 7 |
886-3******** Extension:
|
|||||
1 2 3 4 5 6 7 |
886-3******** Extension:
|
|||||
1 2 3 4 5 6 7 |
886-3******** Extension:
|
|||||
1 2 3 4 5 6 7 | Fax Number |
480 9********
|
||||
1 2 3 4 5 6 7 |
886-3********
|
|||||
1 2 3 4 5 6 7 |
886-3********
|
|||||
1 2 3 4 5 6 7 |
886-3********
|
|||||
1 2 3 4 5 6 7 |
m******@compliancetesting.com
|
|||||
1 2 3 4 5 6 7 |
s******@sporton.com.tw
|
|||||
1 2 3 4 5 6 7 |
a******@sporton.com.tw
|
|||||
Equipment Specifications | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
1 | 1 | 9 | MO | 4942.5 | 4987.5 | 0.006 | 1.5 ppm | 4M64D1D | |||||||||||||||||||||||||||||||||
1 | 2 | 9 | MO | 4945 | 4985 | 0.016 | 1.5 ppm | 8M71D1D | |||||||||||||||||||||||||||||||||
1 | 3 | 9 | MO | 4950 | 4980 | 0.032 | 1.5 ppm | 17M8D1D | |||||||||||||||||||||||||||||||||
1 | 4 | 90,95L | CC MO | 5860 | 5920 | 0.01 | 8 ppm | 20M9D1D | |||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
2 | 1 | 15E | 38 MO | 5180 | 5240 | 0.1972 | |||||||||||||||||||||||||||||||||||
2 | 2 | 15E | 38 MO | 5260 | 5320 | 0.1545 | |||||||||||||||||||||||||||||||||||
2 | 3 | 15E | 38 MO | 5500 | 5580 | 0.1419 | |||||||||||||||||||||||||||||||||||
2 | 4 | 15E | 38 MO | 5660 | 5700 | 0.1216 | |||||||||||||||||||||||||||||||||||
2 | 5 | 15E | 38 MO | 5745 | 5825 | 0.375 | |||||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
3 | 1 | 15E | 39 MO | 5180.00000000 | 5240.00000000 | 0.1972000 | |||||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
4 | 1 | 15E | CC MO | 5180 | 5240 | 0.031 | |||||||||||||||||||||||||||||||||||
4 | 2 | 15E | CC MO ND | 5260 | 5320 | 0.1545 | |||||||||||||||||||||||||||||||||||
4 | 3 | 15E | CC MO ND | 5500 | 5580 | 0.1419 | |||||||||||||||||||||||||||||||||||
4 | 4 | 15E | CC MO ND | 5660 | 5700 | 0.1216 | |||||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
5 | 1 | 90,95L | CC MO | 5860.00000000 | 5920.00000000 | 0.0100000 | 8.0000000000 ppm | 20M9D1D | |||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
6 | 1 | 15E | CC MO | 5180 | 5240 | 0.031 | |||||||||||||||||||||||||||||||||||
6 | 2 | 15E | CC MO | 5190 | 5230 | 0.029 | |||||||||||||||||||||||||||||||||||
Line | Rule Parts | Grant Notes | Lower Frequency | Upper Frequency | Power Output | Tolerance | Emission Designator | Microprocessor Number | |||||||||||||||||||||||||||||||||
7 | 1 | 15C | CC MO | 5745 | 5825 | 0.171 | |||||||||||||||||||||||||||||||||||
7 | 2 | 15C | CC MO | 5755 | 5795 | 0.245 |
some individual PII (Personally Identifiable Information) available on the public forms may be redacted, original source may include additional details
This product uses the FCC Data API but is not endorsed or certified by the FCC