Proxim Tsunami MP11a 5054

Part Number 72282
Tsunami MP.11
Model 5054 (MP.11a)
Installation and Management
Version 2.5
Tsunami MP.11 5054 Installation and Management
COPYRIGHT
2006 Proxim Wireless Corporation, San Jose, 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. This manual and the software
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 trademarks of Proxim Wireless Corporation. All other trademarks
mentioned herein are the property of their respective owners.
FCC COMPLIANCE
This document provides regulatory information for the following wireless indoor products:
5054 BSU, 5054 SU, 5054 RSU
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions:
(1) This device may not cause harmful interference
(2) This device must accept any interference received, including interference that may cause undesired
operation.
This device must be professionally installed.
Changes or modifications not expressly approved by Proxim Wireless Corporation could void the your authority to
operate the equipment.
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), you
are encouraged to attempt 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 or television technician for help.
This device must be professionally installed. Antennas used for the MP.11a product must be fix-mounted on
permanent structures.
Notices
Contents
CHAPTER 1. OVERVIEW .........................................................................................................................................5
About This Book ...................................................................................................................................................5
Reference Manual .........................................................................................................................................6
Wireless Network Topologies...............................................................................................................................6
Point-to-Point Link .........................................................................................................................................7
Point-to-Multipoint Network ...........................................................................................................................7
Power-over-Ethernet ............................................................................................................................................8
Identifying Network Topology and Equipment .....................................................................................................8
Finding a Suitable Location..................................................................................................................................8
CHAPTER 2. INSTALLATION ..................................................................................................................................9
Installation Procedure ..........................................................................................................................................9
Attaching a Kensington Security Lock (Optional)...............................................................................................12
Mounting the Unit ...............................................................................................................................................12
Desktop Mounting........................................................................................................................................12
Wall Mounting ..............................................................................................................................................12
Ceiling Mounting ..........................................................................................................................................14
Powering On the Unit .........................................................................................................................................14
Installing Documentation and Software .............................................................................................................15
Aligning the Antenna ..........................................................................................................................................16
Antenna Alignment Commands...................................................................................................................16
CHAPTER 3. MANAGEMENT OVERVIEW............................................................................................................17
IP Address..........................................................................................................................................................18
Setting the IP Address .................................................................................................................................18
Starting the Web Interface .................................................................................................................................19
Changing Basic Configuration Information ........................................................................................................21
Country and Related Settings......................................................................................................................21
Dynamic Frequency Selection (DFS) ..........................................................................................................22
Transmit Power Control ...............................................................................................................................23
SU Registration ..................................................................................................................................................23
Virtual Local Area Networks (VLANs) ................................................................................................................24
Quality of Service (QoS) ....................................................................................................................................24
Concepts and Definitions.............................................................................................................................25
CHAPTER 4. BASIC MANAGEMENT....................................................................................................................29
Rebooting and Resetting....................................................................................................................................29
Rebooting ....................................................................................................................................................30
Resetting Hardware .....................................................................................................................................30
Soft Reset to Factory Default ......................................................................................................................30
General Configuration Settings ..........................................................................................................................31
Monitoring Settings ............................................................................................................................................32
Security Settings ................................................................................................................................................32
Encryption....................................................................................................................................................32
Passwords ...................................................................................................................................................32
Default Settings ..................................................................................................................................................33
Upgrading the Unit .............................................................................................................................................34
CHAPTER 5. USING THE WEB INTERFACE........................................................................................................35
System Status ....................................................................................................................................................35
View System Status.....................................................................................................................................35
View the Event Log Contents ......................................................................................................................36
Configure the Units Settings..............................................................................................................................37
1) Configure System Parameters ................................................................................................................37
2) Configure Network Parameters ...............................................................................................................42
3) Configure Interface Settings....................................................................................................................52
4) Configure SNMP Parameters..................................................................................................................62
5) Configure RIP Parameters ......................................................................................................................62
6) Configure Management Parameters .......................................................................................................65
7) Configure Security Parameters ...............................................................................................................68
Contents
8) Configure Packet Filtering .......................................................................................................................70

9) Configure Intra-Cell Blocking (Base Station only) ...................................................................................80
10) Configure VLAN Parameters.................................................................................................................83
11) QoS (Quality of Service) Parameters ....................................................................................................91
12) SU Access to the Public Network (NAT) .............................................................................................100
Monitor Settings and Performance...................................................................................................................103
1) Monitor Wireless Settings......................................................................................................................103
2) View Number of ICMP Messages .........................................................................................................105
3) View Per Station Statistics ....................................................................................................................105
4) View Features Supported......................................................................................................................105
5) Test Link Quality....................................................................................................................................106
6) View Interface Performance Details ......................................................................................................107
7) View IP and MAC Address Mapping .....................................................................................................107
8) View Active IP Routes ...........................................................................................................................108
9) View MAC Addresses Detected ............................................................................................................108
10) View RIP Data .....................................................................................................................................108
11) View Radius Traffic Information ..........................................................................................................109
Issue Commands .............................................................................................................................................110
1) Download Files to the Unit ....................................................................................................................110
2) Upload a Configuration File...................................................................................................................111
3) Reboot the Device .................................................................................................................................111
4) Reset the Device ...................................................................................................................................111
5) Set the Help Link Location ....................................................................................................................112
6) Downgrade to a Previous Release........................................................................................................112
CHAPTER 6. PROCEDURES ...............................................................................................................................114
TFTP Server Setup ..........................................................................................................................................114
Web Interface Image File Download ................................................................................................................115
Configuration Backup.......................................................................................................................................115
Configuration Restore ......................................................................................................................................116
Soft Reset to Factory Default ...........................................................................................................................116
Hard Reset to Factory Default..........................................................................................................................117
Forced Reload..................................................................................................................................................117
Image File Download with the Bootloader .......................................................................................................118
Download with ScanTool ...........................................................................................................................118
Download with CLI.....................................................................................................................................119
CHAPTER 7. TROUBLESHOOTING....................................................................................................................120
5054 Connectivity Issues .................................................................................................................................120
5054 Does Not Boot ..................................................................................................................................120
Serial Link Does Not Work.........................................................................................................................120
HyperTerminal Connection Problems........................................................................................................120
Communication Issues.....................................................................................................................................122
Two Units Are Unable to Communicate Wirelessly...................................................................................122
Setup and Configuration Issues .......................................................................................................................122
Lost the 5054 Password ............................................................................................................................122
The 5054 Responds Slowly.......................................................................................................................123
Web Interface Does Not Work...................................................................................................................123
Command Line Interface Does Not Work..................................................................................................123
TFTP Server Does Not Work.....................................................................................................................124
Online Help Is Not Available ......................................................................................................................124
Changes Do Not Take Effect.....................................................................................................................124
VLAN Operation Issues....................................................................................................................................125
Troubleshooting Link Problems........................................................................................................................125
General Check...........................................................................................................................................125
Statistics Check .........................................................................................................................................126
Analyzing the Spectrum.............................................................................................................................127
Avoiding Interference.................................................................................................................................127
Conclusion .................................................................................................................................................127
Strange Behavior After Upgrade ......................................................................................................................128
BSU Behaving Like an SU ...............................................................................................................................128
Contents
APPENDIX A. COUNTRY CODES/CHANNELS ...................................................................................................129

TECHNICAL SUPPORT.........................................................................................................................................142
Email Support ............................................................................................................................................142
Telephone Support ....................................................................................................................................142
Proxim Web Site Support ..........................................................................................................................142
STATEMENT OF WARRANTY..............................................................................................................................143
Contents
Chapter 1. Overview
The Tsunami MP.11a (Tsunami MP.11 Model 5054) is a flexible wireless outdoor router that lets you design
solutions for point-to-point links and point-to-multipoint networks. The Tsunami MP.11 5054 is a product family
comprising several products (such as the 5054 Base Station and the 5054 Residential Subscriber Unit). For
simplification, all products that are part of the 5054 Product Family are referred to as 5054.
Some of the key features of the 5054 are:
The use of a highly optimized protocol for outdoor applications

Routing and bridging capability
Asymmetric bandwidth management
Management through a Web Interface, a Command Line Interface (CLI), or Simple Network Management
Protocol (SNMP)
Software and configuration upgrade through file transfer (TFTP)
ABOUT THIS BOOK

Before installing and using the 5054, Proxim recommends you review the following chapters of this manual:
Chapter 1 Overview (this chapter)
Provides an overview of the content of this manual as well as wireless network topologies and combinations
that can be built with the 5054.
Chapter 2 Installation on page 9
Provides detailed installation instructions for the 5054.
Chapter 3 Management Overview on page 17
Explains how to access the 5054 for configuration and maintenance.
Chapter 4 Basic Management on page 29
Explains the most common settings used to manage the 5054.
Chapter 5 Using the Web Interface on page 35
Depicts the Web Interface in a hierarchical manner, so you can easily find details about each item.
Chapter 6 Procedures on page 114
This chapter provides a set of procedures, including TFTP Server Setup, Configuration Backup, Restore, and
Download, Forced Reload, and Reset to Factory Defaults.
Chapter 7 Troubleshooting on page 120
This chapter helps you to isolate and solve problems with your radio unit.
The appendixes contain supplementary information you may not need immediately, including Country Code
Tables and Technical Support information.
Chapter 1. Overview
Reference Manual
As a companion to the Installation and Management manual, the Tsunami MP.11 Reference Manual provides the
following supplemental information:
Command Line Interface
Documents the text-based configuration utilitys keyboard commands and parameters.
Event Log Error Messages
Documents the error messages that you may see in your Event Log.
Alarm Traps
Documents the alarm traps that can be set.
Microsoft Windows IAS Radius Server Configuration
Provides information to assist you in setting up the IAS Radius Server.
Addition of Units to a Routed Network
Describes how to add more units to your routed network.
Glossary
Describes terms used in the Tsunami MP.11 documentation and in the wireless industry.
If you are already familiar with this type of product, you can use the Quick Install Guide to install the unit.
WIRELESS NETWORK TOPOLOGIES

The unit can be used in various network topologies and combinations. The required equipment depends upon the
wireless network topology you want to build. Make sure all required equipment is available before installing the
unit.
You can set up the following types of topologies:
Point-to-Point Link
Point-to-Multipoint Network
Each unit is set up as either a Base Station Unit (BSU) or a Subscriber Unit (SU). A BSU can, depending upon its
configuration, connect to one or more SUs. An SU, however, can connect only to one BSU. A direct link between
two locations always consists of a BSU and a SU.
Chapter 1. Overview
Point-to-Point Link
With a BSU and an SU, it is easy to set up a wireless point-to-point link as depicted in the following figure.
A point-to-point link lets you 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
Point-to-Multipoint Network
If you want to connect more than two buildings, you can set up a single point-to-multipoint network with a single
BSU and multiple SUs, as depicted in the following figure.
Up to 250 SUs can be connected to a BSU. If a BSU already has 250 SU, a new SU cannot be connected to the
BSU. In this figure, the system is designed as follows:
The central building B is equipped with a BSU, connected to either an omni-directional, or a wide angle
antenna.
The two other buildings A and C are both equipped with an SU connected to a directional antenna.
Chapter 1. Overview
POWER-OVER-ETHERNET
The unit is equipped with an Active Ethernet module. Using Power-over-Ethernet (PoE), you can provide
electricity and wired connectivity to the unit over a single Category 5 cable. If you use Active Ethernet, there is no
difference in operation; the only difference is the power source.
The Active Ethernet integrated module provides 48 VDC over a standard Cat5 Ethernet cable.
Maximum power supplied to the 5054 is 11 Watts. The units typically draw less than 7.5 Watts.
You must have an Active Ethernet hub (also known as a power injector) connected to the network to use
Active Ethernet. The Active Ethernet hub is not a repeater and does not amplify the Ethernet data signal.
If connected to an Active Ethernet hub and an AC power supply simultaneously, the radio draws power
from Active Ethernet.
The cable length between the Active Ethernet hub and the radio should not exceed 100 meters
(approximately 325 feet).
Note:
Cable length affects range by inserting loss in the signal path between the radio and the antenna. The
amount of loss depends on the type and length of cable and type of connectors. Proxim offers
standard low loss cables in the following lengths with RTNC connectors, the connector type on the
Stratum MP: 5 feet (0.6 dB loss), 10 feet (0.9 dB loss), 20 feet (1.5 dB loss), and 50 feet (3.5 dB loss).
Custom cables can address longer cable runs.
IDENTIFYING NETWORK TOPOLOGY AND EQUIPMENT

The 5054 can be used in various network topologies and combinations. The required equipment depends upon
the wireless network topology you want to build. Make sure all required equipment is available before installing
the 5054.
You can connect the 5054 to an outdoor antenna installation with an optional antenna kit. See the Antenna
Installation Guide for details.
WARNING!
If you want to connect the 5054 to an outdoor antenna system, consult the appropriate
manufacturers documentation for additional regulatory information, safety instructions,
and installation requirements.
FINDING A SUITABLE LOCATION

To make optimal use of the 5054, you must find a suitable location for the hardware. The range of the unit largely
depends upon the position of the antenna. Proxim recommends you do a site survey, observing the following
requirements, before mounting the 5054 hardware.
The location must allow easy disconnection of the unit from the power outlet if necessary.
The unit must not be covered and the air must be able to flow freely around the unit.
The unit must be kept away from vibration, excessive heat, and humidity, and kept free from dust buildup.
The installation must conform to local regulations at all times.
Notes:
The Configure System window provides a selectable Country field that automatically provides the
allowed bandwidth and frequencies for the selected country as well as, where applicable, Dynamic
Frequency Selection (DFS) and Transmit Power Control (TPC).
Non-US installers should not add an antenna system until the Country is selected, the unit is rebooted,
and the proper power level is configured. The output power level of the final channel selected by DFS
scan can be found in the Event Log (see View the Event Log Contents on page 36).
Chapter 1. Overview
Chapter 2. Installation
This chapter describes the steps required to install and mount the 5054, including installing, mounting, and
aligning the radio. The installation procedure does not include the mounting and connection of antennas. See
the Tsunami MP.11 Antenna Installation Guide for this information.
If you are already familiar with this type of product, you can use the Quick Install Guide for streamlined installation
procedures.
IMPORTANT!
Before installing this product, see the important regulatory compliance and safety information on page 1.
The 5054 supports two power methodsan AC power outlet and Active Ethernet. The power supply accepts an
input AC voltage in the range of 100-240 VAC.
The following installation procedure provides instructions for attaching both the power and Ethernet connectors.
In situations without an external antenna (for example, during a desk tryout), the antenna cable is not required.
WARNING!
For your own safety, use only the power cord supplied with the unit. The metal case of the unit must be
grounded through the ground connection that is provided on the metal case. The antenna grounding, the
surge arrestor, and the 5054 unit housing must be bonded together and grounded in one location to avoid
ground current loops.
INSTALLATION PROCEDURE
To install the 5054:
1. Unpack the unit and accessories from the shipping box. The 5054 kit contains the following items:
Shown in picture:
1
2
3
4
5
Tsunami 5054 unit

Mounting stand
Documentation and software CD
Wall mounting hardware
Power supply with power cord
Note:
All software CDs that come with your Tsunami products include a Release Notes file. This file
contains information about the software version and drivers. You are advised to print and read the
Release Notes file prior to installing your Tsunami products, as it may contain additional information
that was not available when this document was printed.
The shipment also includes the Tsunami 5054 Quick Install Guide.
2. If you intend to install the unit free-standing, or if you intend to mount it to the ceiling, use a Phillips
screwdriver to attach the metal base to the underside of the unit. The metal base and screws are provided
(see Mounting the Unit on page 12 for more information).
3. Unlock the units cable cover. To release the cable cover, press down on the cable cover lock located in the
front center of the unit.
4. Remove the cable cover.
5. Remove the front cover from the unit (the side with the LED indicators, shown in the figure on left); then
remove the back cover (figure on right).
10
6. Connect the grounding wire to the 5054 using the Faston plug on the metal case, next to the power plug.
7. Connect one end of an Ethernet cable (not supplied) to the Ethernet port. The other end of the cable should
not be connected to another device until after installation is complete.
Use a straight-through Ethernet cable if you intend to connect the 5054 to a hub, switch, patch panel,
or Active Ethernet power injector.
Use a cross-over Ethernet cable if you intend to connect the 5054 to a single computer.
8. If you are not using Active Ethernet, or you want to connect the 5054 to Active Ethernet and AC power
simultaneously, attach the AC power cable to the units power port.
To disconnect the power cable, slide back the black plastic fitting around the connector and gently pull the
connector from the 5054 unit.
9. Connect the free end of the Ethernet cable to a hub, switch, patch panel, Active Ethernet power injector, or an
Ethernet port on a computer.
10. If using AC power, connect the power cord to a power source (such as a wall outlet) to turn on the unit.
11. Place the unit in the final installation location (see Mounting the 5054 on page 12 for details).
12. Replace the back cover, front cover, and cable cover. Be careful to avoid trapping the antenna, power, and
Ethernet cables when replacing the cable cover.
11
ATTACHING A KENSINGTON SECURITY LOCK (OPTIONAL)

If so desired, you can attach a Kensington lock to secure the cable cover into place. This protects the unit from
unauthorized tampering.
The 5054 enclosure includes a Kensington Security Slot for use with a Kensington locking mechanism. When
properly installed, a Kensington lock can prevent unauthorized personnel from stealing the 5054. In addition, the
Kensington lock secures the cable cover in place, which prevents tampering with the Ethernet and power cables.
The Kensington Security Slot is shown in the following figures (the figure on the left shows the slot with the cable
cover attached; the figure on the right shows the slot with the cable cover removed).
For information about Kensington security solutions, go to http://www.kensington.com .
MOUNTING THE UNIT

The following are the mounting options for the 5054:
Desktop Mount
Wall Mount
Ceiling Mount
Desktop Mounting
This procedure consists of attaching the metal base to the 5054 unit. See Installation Procedure on page 9.
Wall Mounting
Follow these steps to mount the unit on a wall:
1. Identify the location at which you intend to mount the unit.
2. If the units power supply is plugged in, unplug it,
3. Use a Phillips screwdriver to remove the metal base from the underside of the 5054 unit (if you have not
already done so).
4. Press down on the cable cover lock to release the cable cover .
12
5. Remove the cable cover from the unit.
6. Remove the front and back covers from the unit.
7. Place the back cover on the mounting location and mark the center of the three mounting holes.
8. Remove the cover from the wall and drill a hole at each of the locations you marked. Each hole should be
wide enough to hold a mounting plug (6 mm x 35 mm).
9. Insert a plug into each hole.
(Four 6 mm x 35 mm plugs are provided; you need to use only three of these for wall mounting.)
10. Insert a screw into each of the mounting holes molded into the back cover.
(Four 3.5 mm x 40 mm pan-head screws are provided; you need to use only three of these for wall mounting.)
11. Insert the screws into the wall plugs; use a screwdriver to tighten the screws and attach the back cover to the
wall.
12. Attach Ethernet and power cables to the 5054 unit, as necessary.
13. Snap the unit into the back cover, replace the front cover, and replace the cable cover.
14. Turn on the 5054 (see Powering On the Unit on page 14).
13
Ceiling Mounting
Follow these steps to mount the 5054 to a ceiling:
1. If the 5054s power supply is plugged in, unplug it.
2. Use a Phillips screwdriver to attach the metal base to the underside of the 5054, if you have not already done
so. See Installation Procedure on page 9 for an illustration.
3. Feed a mounting screw through each of the four rubber feet. The 5054 comes with four 3.5 mm x 40 mm
pan-head screws.
4. Remove the screws from the rubber feet.

5. Turn the 5054 upside down and position the base against the ceiling where you want to mount the unit.
6. Mark the center of the four mounting holes in the rubber feet.
7. Set the 5054 aside and drill a hole at each of the locations you marked above. Each hole should be wide
enough to hold a mounting plug (6 mm x 35 mm).
8. Insert a plug into each hole. The 5054 comes with four 6 mm x 35 mm plugs.
9. Insert the screws into the holes you made previously in the rubber feet.
10. Insert the screws into the mounting plugs. Use a screwdriver to tighten the screws and attach the 5054s
metal base to the ceiling.
POWERING ON THE UNIT

The 5054 can be powered by a power supply (just plug the power cord of the power supply into an AC power
outlet), or by Active Ethernet (connect an Active Ethernet splitter to the Ethernet cabling).
When the unit is powered on, the 5054 performs startup diagnostics. When startup is completed, the LEDs show
the operational state of the 5054 (see the following figure).
Power
Ethernet Link
Wireless Link
The following table shows the status of the LEDs when the 5054 is operational (the fourth LED is only
used during Dynamic Frequency Selection on a BSU; flashing green indicates scanning).
14
Power
OFF
GREEN
AMBER
RED
Ethernet Link
OFF
GREEN
BLINKING GREEN
AMBER
BLINKING AMBER
RED
Wireless Link
OFF
GREEN
BLINKING GREEN
Power is not present or is malfunctioning.

Power is present; the unit is operational.
The unit is initializing after reboot (less than two minutes); it cannot get a dynamic IP
address.
A fatal error in the unit.
Not connected.
Connected at 10 Mbps.
Data is being sent at 10 Mbps.
Connected at 100 Mbps, or the unit is initializing after reboot (less than two minutes).
Data is being sent at 100 Mbps.
An error in data transfer.
Wireless interface is up properly but no wireless link established.
Immediately after connecting a wireless link.
Data is being sent or the wireless interface is initializing after reboot (less
than two minutes).
RED
There is a fatal error on the wireless interface.
* See Forced Reload on page 117.
INSTALLING DOCUMENTATION AND SOFTWARE

The 5054 also comes with documentation and software on a CD.
To install the documentation and software on a computer or network:
1. Place the CD in a CD-ROM drive. The installer normally starts automatically. You can also start the installer
manually by running the setup.exe program in the root directory of the CD.
2. Click the Install Help and Software button and perform the necessary steps.
In addition to the software installation utility, the CD contains the following documentation and software:
Online help
This is the help for the Web Interface. It is also stored on your computer or network during the installation
process, so it is always available (see c:\Program Files\Tsunami\MP.11). You can also find the help in the
Docs folder of the product CD.
Documentation
Documentation is provided in PDF format, including:
Release Notes
Quick Install Guide
Installation and Management
Tsunami MP.11 Reference Manual
Tsunami MP.11 Antenna Installation
Tsunami MP.11 Recommended 5 GHz and 2.4 GHz Antennas
You can find this documentation in the Docs folder of the product CD. This documentation also is installed at
c:\Program Files\Tsunami\MP.11.
ScanTool
ScanTool lets you find the IP address of a Tsunami MP.11 5054 by referencing the MAC address in a Scan
List, and lets you assign an IP address if one has not been assigned. The tool automatically detects the units
15
installed on your network, regardless of IP address, and lets you configure each units IP settings. In addition,
you can use ScanTool to download new software to a unit that does not have a valid software image installed.
See Setting the IP Address on page 18 for details. You can find ScanTool in the Xtras directory of the
product CD. It is installed at c:\Program Files\Tsunami\MP.11.
TFTP Server
The TFTP (Trivial File Transfer Protocol) server lets you transfer files across the network. You can download
configuration files, as well as image files for embedded software upgrades, and you can upload files from the
5054 for backup. See TFTP Server Setup on page 114, Download on page 110, and Upload on page 111
for more information. You can find the TFTP Server in the Xtras directory of the product CD. It is installed at
c:\Program Files\Tsunami\MP.11. Here downloading means transferring files to the 5054 and uploading
means transferring files in the opposite direction.
ALIGNING THE ANTENNA

Antenna Alignment Display (AAD) provides a measurement of signal quality in an easy-to-interpret mannera
numeric printed signal value at the CLI and serial ports. The SNR is numerically displayed on the CLI or serial
port by two decimal characters representing a number from 00 to 99. On the serial port, AAD is enabled by
default after booting.
To start the display, you must enable AAD and a wireless link must be established between the BSU and the SU.
Aiming is complete if moving in any direction results in a falling SNR value.
Antenna Alignment Commands

set aad enable local
Enables display of the local SNR. Local SNR is the SNR measured by the receiver at the near end.
set aad enable remote
Enables display of the remote SNR. Remote SNR is the SNR as measured by the receiver at the far end.
set aad enable average
Enables display of the average SNR. The average SNR is the average of the local and remote SNR.
set aad disable
Disables Antenna Alignment Display (Ctrl-C also disables AAD).
16
Chapter 3. Management Overview

This chapter describes how to gain access to the 5054 for configuration and management. Three interfaces are
provided for viewing or changing the units settings:
Web Interface
The Web interface (HTTP) provides easy access to configuration settings and network statistics from any
computer on the network. You can access the Web interface over your network, over the Internet, or with a
crossover Ethernet cable connected directly to your computers Ethernet port. See Chapter 5. Using the
Web Interface on page 35 for more information.
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 and manage the 5054 unit. You enter command statements,
composed of CLI commands and their associated parameters. You can issue commands from the keyboard
for realtime control or from scripts that automate configuration. See Command Line Interface in the
Tsunami MP.11 Reference Manual for more information.
SNMP
In addition to the Web interface and the CLI, you also can manage and configure your unit using the Simple
Network Management Protocol (SNMP). Note that this requires an SNMP manager program, such as Hewlett
Packards OpenView or Castelrocks SNMPc. The 5054 supports several Management Information Base
(MIB) files that describe the parameters that can be viewed and configured using SNMP:
mib802.mib
orinoco.mib
rfc1213.mib
rfc1493.mib
rfc1643.mib
Proxim provides these MIB files on the CD included with your unit. You must compile one or more of these
MIB files into your SNMP programs database before you can manage your unit using SNMP. See the
documentation that came with your SNMP manager for instructions about how to compile MIBs.
Note:
When you update the software in the unit, you must also update the MIBs to the same release.
Because the parameters in the MIB may have changed, you will not otherwise have full control over
the features in the new release.
The enterprise MIB (orinoco.mib) defines the read and read/write objects you can view or configure using
SNMP. These objects correspond to most of the settings and statistics that are available with the other
management interfaces. See the enterprise MIB for more information; the MIB can be opened with any text
editor, such as Microsoft Word, Notepad, and WordPad. See Configure SNMP Parameters on page 62 for
setup procedures.
Connecting to the 5054 requires a direct physical connection with an Ethernet cross-over cable, a serial RS232C cable, or a connection through the network.
For the serial connection, you can use only the CLI to configure and manage the 5054. The other
connections allow the use of the Web Interface, SNMP, and the CLI. These other connections require the IP
address of the 5054 before you can use the Web Interface, SNMP, or the CLI. See IP Address on page 18
for more information.
17
You can also manage the 5054 without an IP address by accessing the unit through the serial port with a
terminal program such as HyperTerminal (see HyperTerminal Connection Properties in the Tsunami MP.11
Reference Manual).
IP ADDRESS
Because each network is different, an IP address suitable for your network must be assigned to the unit. You
must know this IP address to configure and manage the unit through its Web Interface, SNMP, or the CLI. You
can manage other basic parameters as well. ScanTool is included on the documentation and software CD to
assist you in finding and changing the units IP address.
The unit can use either a static or dynamic IP address. The unit either obtains its IP address automatically
through DHCP (dynamic IP address) or it must be set manually (static IP address).
With ScanTool (a software utility that is included on the product installation CD), you can find out the current IP
address of the unit and, if necessary, change it so that is appropriate for your network. The units are shipped with
the static IP address 10.0.0.1 configured.
ScanTool lets you find the IP address of a Tsunami MP.11 5054 by referencing the MAC address in a Scan List,
or to assign an IP address if the correct one has not been assigned. The tool automatically detects the units
installed on your network segment, regardless of IP address, and lets you configure each units IP settings. In
addition, you can use ScanTool to download new software to a unit that does not have a valid software image
installed.
Setting the IP Address

If you want to set the IP address:
1. Run ScanTool on a computer connected to the same LAN subnet as the unit, or a computer directly
connected to the unit with a cross-over Ethernet cable. ScanTool (scantool.exe) has been installed on your
computer at the following location: c:\Program Files\Tsunami\MP.11
ScanTool scans the subnet for 5054 units and displays a list of the units it finds in the main window. The
following figure is an example of the main window. If necessary, click Rescan to re-scan the subnet and
update the display. You can assign a new IP address to one unit, even if more than one unit has the same
(default) IP address 10.0.0.1, but the new IP address must be unique to allow use of the management
interfaces.
2. Select the unit for which you want to set the IP address and click Change. The Change dialog window is
displayed, as shown in the following window.
18
3. To set the IP address manually, ensure that Static is selected as the IP Address Type and fill in the IP
Address and Subnet Mask suitable for the LAN subnet to which the unit is connected.
To set the IP address dynamically, ensure that Dynamic is selected as the IP Address Type. The unit will
request its IP address from a DHCP server on your network.
4. Enter the Read/Write Password (the default value is public) and click OK to confirm your changes. The
respective unit reboots to make the changes effective.
Note:
The number of asterisks displayed after you enter the password does not necessarily equal the
number of characters in the actual password string. This is done for added security.
STARTING THE WEB INTERFACE

The Web Interface provides a graphical user interface through which you can easily configure and manage the
5054. This section describes only how to access the Web Interface; the Web Interface itself described in
Chapter 4. Basic Management on page 29 and Chapter 5. Web Interface on page 35.
To use the Web Interface, you need only the IP address of the 5054. (See IP Address on page 18 for details.)
Note:
If the connection is slow or you are not able to connect, use the Internet Explorer Tools option to ensure
you are not using a proxy server for the connection with your Web browser.
To access the 5054 with a Web browser, start your Web browser and enter the IP address of the unit. The Web
address should appear as http://<ip address> (for example, http://10.0.0.1). A window such as the following is
displayed.
19
Do not fill in the User Name, enter only the password and click OK. The default password is public.
The System Status window is displayed. You now have access to the units Web Interface. To find out more
about the information presented in this window, see System Status on page 35.
20
CHANGING BASIC CONFIGURATION INFORMATION

To view or change basic system information, click the Configure button on the left side of the Web interface
window, then click the System tab. See Configure System Parameters on page 37 for detailed information
about the fields and selections in this window.
Note:
System Name by default contains the actual model number. The following screenshot is for information
only.
Country and Related Settings

The units Configure System window provides a selectable Country field that automatically provides the allowed
bandwidth and frequencies for the selected country.
Units sold in the United States are pre-configured to scan and display only the outdoor frequencies permitted by
the FCC. No other Country can be configured. Units sold outside of the United States support the selection of a
Country by the professional installer.
Note:
Non-US installers should not add an antenna system until the Country is selected, the unit is rebooted,
and the propr power level is configured. The output power level of the final channel selected by DFS
scan can be found in the Event Log (see Event Log on page 36).
The Dynamic Frequency Selection (DFS) feature is enabled automatically when you choose a country with a
regulatory domain that requires it. The Transmit Power Control (TPC) feature is always available.
Click the Configure button and the System tab; then select the appropriate country for your regulatory domain
from the Country drop-down box.
Continue configuring settings as desired; then click the Commands button and the Reboot tab to save and
activate the settings. Alternatively, if you want to save the configuration settings to the flash memory but not
activate the settings, use the save config CLI command.
21
Dynamic Frequency Selection (DFS)

The Tsunami MP.11 5054 supports Dynamic Frequency Selection (DFS) for European Telecommunications
Standard Institute (ETSI) domains per EN 301-893 regulations. The ETSI requires that 802.11a devices use DFS
to prevent interference with radar systems and other devices that already occupy the 5 GHz band.
During boot-up, the unit scans the available frequency and selects a channel that is quiet and free of radar
interference. If the unit subsequently detects radar interference on its channel, it rescans to find a better channel.
Upon finding a new channel, the unit waits 60 seconds to detect radar interference; if it finds no interference, it
switches to the new channel.
If you are using a 5054 unit in Europe or other applicable countries, keep in mind the following:
DFS is not a configurable parameter; it is always enabled and cannot be disabled.
You cannot manually select the devices operating channel; you must let the unit select the channel.
However, you can specify a particular preferred channel that you want to scan first whenever the DFS
process starts. You may also make channels unavailable by manually blacklist them and prevent those
channels to be scanned, as well as display the Channel Blacklist Table.
You cannot configure the Auto Channel Select option. Within the HTTP or CLI interface, this option always
appears enabled.
With 5054 units, Dynamic Frequency Selection (DFS) is enabled automatically based upon the country you
select. You can tell DFS is in use because the frequency selection field displays only the DFS-selected
frequency. DFS scans all available frequencies, starting with the DFS preferred channel and skipping blacklisted
channels, to select the operating frequency automatically.
A country selection with DFS enabled causes the Base Station to come up in scan mode. It scans the available
frequencies and channels to avoid radar and selects a channel with the least interference.
Note:
Scanning is performed only on the frequencies allowed in the regulatory domain of the country selected
when it is required for radar detection and avoidance.
To comply with your countrys regulations, change the DFS selection to specify your country. You can do this by
logging into the unit, clicking the Configure button and selecting the System tab. There is a drop-down box
labeled Country with all available countries from which to select. Choose your country, configure the unit as
required, and reboot for the settings to take effect.
The SU also comes up in scan mode to scan all available frequencies to find a BSU with which it can register.
Scanning may take several minutes. After establishing a wireless link, the wireless LED stops flashing and
continues to shine green.
Note:
Because DFS may need to scan for radar on multiple channels, you must allow a sufficient amount of
time for the units to start up. This is considerably longer than when the unit is not using DFS. This is
expected behavior. Startup time is within four minutes if no radar is detected, but up to one minute is
added for every selected channel that results in radar detection.
DFS is required for two purposes:

1. Radar avoidance both at startup and while operational. To meet these requirements, the BSU scans
available frequencies at startup for the presence of a radar signal on all available frequencies. If a radar signal
is detected on any DFS enabled channel, the system will blacklist the channel for a period of 30 minutes in
accordance to EN301-893. Once fully operational on a frequency, the BSU actively monitors the occupied
frequency for radar interference. If radar interference is detected, the BSU blacklists the channel, logs a
message and rescans to find a new frequency free of radar interference.
22
Radar detection is performed only by the BSU and not by the SU. When an SU is set to a country in which
DFS is used, it scans all available channels upon startup looking for a BSU that best matches its connection
criteria (such as Base Station System Name, Network Name, and Shared Secret). The SU connects to the
BSU automatically on whatever frequency the BSU has selected. Because of this procedure, it is best to set
up the BSU and have it fully operational before installing the SU, although this is not required. If a BSU
rescans because of radar interference, the SU loses its wireless link. The SU waits 30 seconds (when the
Mobility feature is enabled, the SU starts scanning for a BSU instantly rather than waiting 30 seconds); if it
finds that it could not receive the BSU in this amount of time, it rescans the available frequencies for an active
BSU.
2. Guarantee the efficient use of available frequencies by all devices in a certain area. To meet this
requirement, the BSU scans each available frequency upon startup and selects a frequency based upon the
least amount of noise and interference detected. This lets multiple devices operate in the same area with
limited interference. This procedure is done only at startup; if another non-radar device comes up on the
same frequency, the BSU does not detect this or rescan because of it. It is expected that other devices using
these frequencies also are in compliance with country regulations, so this should not happen.
Transmit Power Control

Transmit Power Control is a manual configuration selection to reduce the units output power. The maximum
output power level for the operating frequency can be found in the event log of the units embedded software.
By default, the unit lets you transmit at the maximum output power that the radio can sustain for data rate and
frequency selected. However, with Transmit Power Control (TPC), you can adjust the output power of the unit to
a lower level in order to reduce interference to neighboring devices or to use a higher gain antenna without
violating the maximum radiated output power allowed for your country. Also, most countries in the ETSI
regulatory domain require the transmit power to be set to a 6 dB lower value than the maximum allowed EIRP
when link quality permits, as part of the DFS requirements.
You can see your units current output power for the selected frequency in the event log. The event log shows the
selected power for all data rates, so you must look up the relevant data rate to determine the actual power level.
Note:
This feature only lets you decrease your output power; you cannot increase your output power beyond
the maximum the radio allows for your frequency and data rate.
See Configure System Parameters on page 37 to configure Country. See Configure the Wireless Interface on
page 52 to configure Transmit Power Control.
SU REGISTRATION
The list of parameters you must configure for registration of the SU on a BSU are:
Network Name
Base Station System Name (when used; otherwise, leave blank)
Network Secret
Encryption (when used)
Frequency Channel (or Roaming, or DFS)
See Configure System Parameters on page 37 to see the description of these fields and to configure them.
Notes:
The frequency channel must be the same for the BSU and the SU in order to register the SU when
roaming is not enabled and DFS is not required.
Channel Bandwidth and Turbo mode must be the same for the BSU and SU in order to register the SU.
23
Roaming will automatically select a channel on the SU corresponding to the BSU channel. Roaming is
the procedure in which an SU terminates the session with the current BSU and starts the registration
procedure with another BSU when it finds the quality of the other BSU to be better.
VIRTUAL LOCAL AREA NETWORKS (VLANs)

Virtual Local Area Networks (VLANs) are logical groupings of network hosts. Defined by software settings, other
VLAN members or resources appear (to connected hosts) to be on the same physical segment, no matter where
they are attached on the logical LAN or WAN segment. They simplify allowing traffic to flow between hosts and
their frequently-used or restricted resources according to the VLAN configuration.
Tsunami MP.11 5054 units are fully VLAN-ready; however, by default, VLAN support is disabled. Before enabling
VLAN support (by assigning a VLAN Management ID), certain network settings should be configured and network
resources such as VLAN-aware switches should be available, dependent upon the type of configuration.
VLANs are used to conveniently, efficiently, and easily manage your network in the following ways:
Manage VLAN configuration from a single window
Define groups
Reduce broadcast and multicast traffic to unnecessary destinations
Improve network performance and reduce latency
Increase security
Secure network restricts members to resources on their own VLAN
VLAN tagged data is collected and distributed through a units Ethernet interface . The units can communicate
across a VLAN-capable switch that analyzes VLAN-tagged packet headers and directs traffic to the appropriate
ports when the units are working in their Transparent mode.
VLAN features can be managed via:
The BSUs Web interface (see Chapter 5. Using the Web Interface on page 35)
The Command Line Interface (see Command Line Interface in the Reference Manual)
SNMP (see the MIBs provided on the product CD)
For more information about VLAN configuration, see Configure VLAN Parameters on page 83.
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 main priority is to guarantee a reliable and adequate
transmission quality for for all types of traffic under conditions of high congestion and bandwidth oversubscription.
24
Concepts and Definitions

The software supports QoS provisioning from the BSU only. You may define different classes of service on a BSU
that can then be assigned to the SUs that are associated, or that may get associated, with that BSU.
The software provides the ability to create, edit, and delete classes of service that are specified by the following
hierarchy of parameters:
Packet Identification Rule (PIR) up to 64 rules, including 17 predefined rules

Service Flow class (SFC) up to 32 SFs, including 7 predefined SFCs; up to 8 PIRs may be associated
per SFC
Priority for each rule within each SF class 0 to 255, with 0 being lowest priority
QoS class up to 8 QoS classes, including 4 predefined classes; up to 4 SFCs may be associated per
QoS class
Packet Identification Rule (PIR)

A Packet Identification Rule is a combination of parameters that specifies what type of traffic is allowed or
disallowed. The software allows to create up to 64 different PIRs, including 17 predefined PIRs. It provides the
ability to create, edit, and delete PIRs that contain none, one, or more of the following classification fields:
Rule Name
IP ToS (Layer 3 QoS identification)
IP Protocol List containing up to 4 IP protocols
802.1p tag (layer 2 QoS identification)
Up to 4 pairs of Source IP address + Mask
Up to 4 pairs of Destination IP address + Mask
Up to 4 source TCP/UDP port ranges
Up to 4 destination TCP/UDP port ranges
Up to 4 source MAC addresses
Up to 4 destination MAC addresses
VLAN ID
Ether type (Ethernet protocol identification)
A good example is provided by the 17 predefined PIRs. Note that these rules help to identify specific traffic types:
1. All No classification fields, all traffic matches
2. Cisco VoIP UL
a. Protocol Source Port Range (16,000-32,000)
b. IP Protocol List (17 = UDP)
3. Vonage VoIP UL
a. Protocol Source Port Range (8000-8001, 10000-20000)
4. Cisco VoIP DL
a. Protocol Destination Port Range (16,000-32,000)
5. Vonage VoIP DL
a. Protocol Destination Port Range (8000-8001, 10000-20000)
6. TCP
a. IP Protocol List (6)
7. UDP
a. IP Protocol List (17)
25
8. PPPoE Control
a. Ethertype (type 1, 0x8863)
9. PPPoE Data
10. IP
11. ARP
12. Expedited Forwarding
a. IP TOS/DSCP (low=0x2D, high=0x2D, mask = 0x3F)
13. Streaming Video (IP/TV)
a. IP TOS/DSCP (low=0x0D, high=0x0D, mask = 0x3F)
14. 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)
15. 802.1p Voice
16. 802.1p Video
17. L2 Broadcast/Multicast
a. Ethernet Destination (dest = 0x80000000, mask = 0x80000000)
Two different VoIP rule names have been defined for each direction of traffic, Uplink (UL) and Downlink (DL),
(index numbers 2 to 5). 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 Vonagetype VoIP service.
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. The software allows to create up to 32 different SFs, including seven
predefined SFs. The software provides the ability to create, edit, and delete SFs that contain the following
parameters and values:
Service flow name

Scheduling type Best Effort (BE); Real-Time Polling Service (RtPS)
Service Flow Direction Downlink (DL: traffic from BSU to SU); Uplink (UL: traffic from SU to BSU)
Maximum sustained data rate (or Maximum Information Rate, MIR) specified in units of 1 Kbps from 8
Kbps up to the maximum rate of 108000 Kbps per SU
Minimum reserved traffic rate (or Committed Information Rate, CIR) specified in units of 1 Kbps from 0
Kbps up to the maximum rate of 10000 Kbps per SU
Maximum Latency specified in increments of 5 ms steps from a minimum of 5 ms up to a maximum of
100 ms
Tolerable Jitter specified in increments of 5 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
Maximum number of data messages in a burst one (1) to four (4), which affects the percentage of the
maximum throughput of the system according to the table Error! Bookmark not defined.
Activation state Active; Inactive
26
Note that traffic priority refers to the prioritization of this specific Service Flow.
The software tries to deliver the packets within the specified latency and jitter requirements, relative to the
moment of receiving the packets in the unit. For delay-sensitive traffic the jitter must be equal to or less than the
latency. A packet is buffered until an interval of time equal to the difference between Latency and Jitter (Latency
Jitter) has elapsed. The software will attempt to deliver the packet within a time window starting at (Latency
Jitter) until the maximum Latency time is reached. If the SFCs scheduling type is real-time polling (rtPS), and the
packet is not delivered by that time, it will be discarded. 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.
Users are able to 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 seven predefined SFCs:
1. UL-Unlimited BE
a. Scheduling Type = Best Effort
b. Service Flow Direction = Uplink
c. Initialization State = Active
d. Maximum Sustained Data Rate = 20 Mbps
e. Traffic Priority = 0
2. DL-Unlimited BE (same as UL-Unlimited BE, except Service Flow Direction = Downlink)
3. UL-G711 20 ms VoIP rtPS
a. Schedule type = Real time Polling
b. Service Flow Direction = Uplink
d. Maximum Sustained Data Rate = 88 Kbps
e. Minimum Reserved Traffic Rate = 88 Kbps
f. Maximum Latency = 20 milliseconds
g. Traffic Priority = 1
4. DL-G711 20 ms VoIP rtPS (same as UL-G711 20ms VoIP rtPS, except Service Flow Direction =
Downlink)
5. UL-G729 20 ms VoIP rtPS (same as UL-G711 20ms VoIP rtPS, except Maximum Sustained Data Rate
and Maximum Reserved Traffic Rate = 64 Kbps)
6. DL-G729 20 ms VoIP rtPS (same as UL-G729 20ms VoIP rtPS, except Service Flow Direction =
Downlink)
7. DL-2Mbps Video
a. Schedule type = Real time Polling
b. Service Flow Direction = Downlink
d. Maximum Sustained Data Rate = 2 Mbps
e. Minimum Reserved Traffic Rate = 2 Mbps
f. Maximum Latency = 20 milliseconds
g. Traffic Priority = 1
Two different VoIP Service Flow classes for each direction of traffic have been defined (index numbers 3 to 6)
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.
27
QoS Class
A QoS class is defined by a set of parameters that includes the PIRs and SFCs that were previously configured.
The software allows creating up to eight different QoS classes, including four predefined QoS classes. Up to four
SF classes can be associated to each QoS 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 DLG711 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.
The software provides the ability to 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 four 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-63, with priority 63 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 four 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. 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
3. 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
4. 2Mbps Video
a. SF class: DL-2Mbps Video
PIR: Streaming Video (IP/TV); PIR Priority: 1
28
Chapter 4. Basic Management

This chapter describes how to configure and monitor the units basic features. In most cases, configuring these
basic features is sufficient. A full overview of the Web Interface is provided in Chapter 5. Using the Web
Interface on page 35. The Glossary in the Tsunami MP.11 Reference Manual provides a brief explanation of
the terms used. For CLI commands you can use for basic management, see Command Line Interface in the
Tsunami MP.11 Reference Manual.
The following topics are discussed in this chapter:
Rebooting and Resetting below

General Configuration Settings on page 31
Monitoring Settings on page 32
Security Settings on page 32
Default Settings on page 33
Upgrading the Unit on page 34
To use the Web Interface for configuration and management, you must access the unit. With ScanTool you can
determine the units current IP address. Then enter http://<ip address> in your Web browser (for example
http://10.0.0.1). See Setting the IP Address on page 18 for details.
Note:
If you have your Security Internet Options set to High, you may not be able to access the Web interface
successfully; a high security setting disables JavaScript, which is required for running Proxims Web
browser interface. Adding the radios IP address as a Trusted site should fix this problem.
The Web Interface consists of Web page buttons and tabs. A tab can also contain sub-tabs. The following figure
shows the convention used to guide you to the correct tab or sub-tab.
Click Configure Interfaces Wireless
The Web Interface also provides online help, which is stored on your computer (see Installing Documentation
and Software on page 15 for details).
REBOOTING AND RESETTING

All configuration changes require a restart unless otherwise stated. New features explicitly state whether a reboot
is required or not. You can restart the unit with the Reboot command; see the first method described in the
following sub-sections.
Most changes you make become effective only when the 5054 is rebooted. A reboot stores configuration
information in non-volatile memory and then restarts the 5054 with the new values (see Soft Reset to Factory
Default on page 30).
In some cases, the 5054 reminds you that a reboot is required for a change to take effect. You need not reboot
immediately; you can reboot after you have made all your changes.
29
Note:
Saving of the units configuration occurs only during a controlled reboot or by specifically issuing the CLI
Save command. If you make changes to settings without a controlled reboot (command) and you have
not issued the Save command, a power outage would wipe out all changes since the last reboot.
For example, entering static routes takes effect immediately; however, the routes are not saved until the
unit has gone through a controlled reboot. Proxim strongly recommends saving your settings immediately
when you finish making changes.
Rebooting
When you reboot, the changes you have made become effective and the 5054 is restarted. The changes are
saved automatically in non-volatile memory before the actual reboot takes place.
To reboot, click the Commands button, then the Reboot tab. Click the Reboot button. The 5054 restarts the
embedded software. During reboot, you are redirected to a page showing a countdown timer, and you are
redirected to the Status page after the timer counts down to 0 (zero). The CLI is disconnected during reboot.
This means that a new telnet session must be started.
Resetting Hardware
If the unit does not respond for some reason and you are not able to reboot, you can restart by means of a
hardware reset. This restarts the hardware and embedded software. The last saved configuration is used. Any
changes that you have made since then are lost.
To reset the hardware, press and release the RESET button on the 5054 unit with, for example, a pencil.
Soft Reset to Factory Default

If necessary, you can reset the unit to the factory default settings. This must be done only when you are
experiencing problems. Resetting to the default settings requires you to reconfigure the 5054.
To reset to factory default settings:
1. Click the Commands button, then the Reset tab.
2. Click the Reset to Factory Default button. The device configuration parameter values are reset to their
factory default values.
If you do not have access to the unit, you can use the procedure described in Hard Reset to Factory Default on
page 117 as an alternative.
30
GENERAL CONFIGURATION SETTINGS

System Status
The status tab showing the system status is displayed automatically when you log into the Web interface. It is
also the default window displayed when you click the Status button on the left side of the window. See View
System Status on page 35 for more information.
System Configuration
The System Configuration window lets you change the units country, system name, location name, and so on
(see the window to the right). The Country selection is required to enable the correct radio parameters. The
other details help distinguish this unit from other routers, and let you know whom to contact in case of
problems. See 1) Configure System Parameters on page 37 for more information.
IP Configuration
The IP Configuration window lets you change the units IP parameters. These settings differ between
Routing and Bridge mode. See 2) Configure Network Parameters on page 42 for more information.
Interface Configuration
The Interface configuration pages let you change the Ethernet and Wireless parameters. The Wireless tab
is displayed by default when you click the Interfaces tab.
Ethernet
To configure the Ethernet interface, click the Configure button, the Interfaces tab, and the Ethernet
sub-tab. You can set the Configuration parameter from this tab for the type of Ethernet transmission.
The recommended setting is auto-speed auto-duplex. See Configure the Ethernet Interface on page
58 for more information.
Wireless
To configure the wireless interface, click the Configure button followed by the Interfaces tab; then click
the Wireless sub-tab. For BSUs, the wireless interface can be placed in either WORP Base or WORP
Satellite mode (selected from the Interface Type drop-down box). SUs can be placed only in WORP
Satellite mode. (See 3) Configure Interfaces Settings on page 52 for more information.)
VLAN Configuration
To configure BSU VLAN parameters, click the Configure button followed by the VLAN tab; the BSU Table
tab is displayed. Click the SUs Table tab to configure SU VLAN parameters. Virtual LAN (VLAN)
implementation in the Tsunami MP.11 products lets the BSU and SU be used in a VLAN-aware network and
processes IEEE 802.1Q VLAN-tagged packets. Network resources behind the BSU and SU can be assigned
to logical groups. See 10) Configure VLAN Parameters on page 83 for more information.
31
MONITORING SETTINGS
The unit offers various facilities to monitor its operation and interfaces. Only the most significant monitoring
categories are mentioned here.
Wireless
To monitor the wireless interfaces, click the Monitor button and the Wireless tab. This tab lets you monitor
the general performance of the radio and the performance of the WORP Base or WORP Satellite interfaces.
Interfaces
To monitor transmission details, click the Monitor button and the Interfaces tab. The Interfaces tab provides
detailed information about the MAC-layer performance of the wireless network and Ethernet interfaces.
Per Station
Click the Monitor button and the Per Station tab to view Station Statistics. On the SU, the Per Station
page shows statistics of the BSU to which the SU is registered. On the BSU, it shows statistics of all the SUs
connected to the BSU. The pages statistics refresh every 4 seconds.
SECURITY SETTINGS
To prevent misuse, the 5054 provides wireless data encryption and password-protected access. Be sure to set
the encryption parameters and change the default passwords.
In addition to Wired Equivalent Privacy (WEP), the units support Advanced Encryption Standard (AES) 128-bit
encryption. Two types of the AES encryption are available. Previous releases supported only the AEC-OCB; the
AES CCM protocol is now also supported.
Proxim highly recommends you change the Network Name, Encryption Key, and Shared Secret as soon as
possible. To do so, click the Configure button and the Interfaces tab; then click the Wireless sub-tab. The
encryption key is set using the Security tab. For systems that will use roaming features, the Network Name,
Encryption Key, and the Shared Secret should each be the same for all SUs that are allowed to roam as well as
for all BSUs to which these SUs are allowed to roam.
Encryption
You can protect the wireless data link by using encryption. Encryption keys can be 5 (64-bit), 13 (WEP 128-bit),
or 16 (AES 128-bit) characters in length. Both ends of the wireless data link must use the same parameter
values.
To set the encryption parameters, click the Configure button, the Security tab, and the Encryption sub-tab. See
Configure Encryption on page 69.
Passwords
Access to the units are protected with passwords. The default password is public. For better security it is
recommended to change the default passwords to a value (6-32 characters) known only to you.
To change the units HTTP, Telnet, or SNMP passwords, click the Configure button, the Management tab, and
the Password sub-tab. See Configure Passwords on page 65.
32
DEFAULT SETTINGS
FEATURE
5054 Setting
System Name
Tsunami MP.11 5054
Mode of Operation
Bridge
Routing
Disabled
IP Address Assignment Type
Static
IP Address
10.0.0.1
Subnet Mask
255.255.255.0
Default Router IP Address
10.0.0.1
Default TTL
64
RIPv2
Enabled when in Routing Mode
Base Station System Name
Wireless Router
Network Name
OR_WORP
Frequency Channel
Channel 149, Frequency 5.745 GHz (FCC Only devices)

DFS Enabled (World Mode devices)
0 dB
Data Rate
36 Mbps
Registration Timeout
Network Secret
Public
Turbo Mode
Disabled
Channel Bandwidth
20 MHz (not configurable)
Input bandwidth limit (in Kbps)
36032
Output bandwidth limit (in Kbps)
36032
Ethernet Configuration
Auto-Speed Auto-Duplex
Serial port Baud Rate
9600
SNMP Management Interface
Enabled
Telnet Management Interface
Enabled
HTTP Management Interface
Enabled
HTTP Port
80
Telnet Port
23
Telnet Login Timeout
30
Telnet Session Timeout
900
Password
public
Maximum Satellites (per BSU)
250
MAC Authentication
Disabled
Radius Authentication
Disabled
Encryption
Disabled
Static MAC Address Filter
Disabled / No Entries
Ethernet Protocol Filtering
All Filters Disabled
DFS Priority Frequency Channel
Disabled
Announcement Period (when roaming enabled)
100 ms
33
FEATURE
5054 Setting
Multi-Frame Bursting
Enabled
Storm Threshold
Broadcast/Multicast Unlimited
Broadcast Protocol Filtering
All Protocols Allowed
Dynamic Data Rate Selection
Disabled
Roaming
Disabled
NAT
Disabled
Intra-Cell Blocking
Disabled
Antenna Alignment
Disabled
Country Selection
US-only device US
World device GB
DHCP Server
Disabled
DHCP Relay
Disabled
Spanning Tree Protocol
Disabled
Antenna Gain
0 (For DFS Threshold compensation)
VLAN Mode
BSU: Transparent Mode SU: Transparent mode when BSU

is in Transparent mode; Trunk mode when the BSU is in Trunk
mode.
Access VLAN ID
BSU: N/A; SU: 1
Access VLAN Priority
BSU: N/A; SU: 0
Management VLAN ID
BSU: -1;
SU: -1
Management VLAN Priority
BSU: 0;
SU: 0
VLAN ID in Trunk VLAN Table
BSU: N/A; SU: 1
UPGRADING THE UNIT

The units are equipped with embedded software that can be updated when new versions are released. Updating
the embedded software is described in Image File Download With The Bootloader on page 118. A TFTP server is
provided on the Documentation and Software CD; the server is required to transfer the downloaded file to the unit.
See TFTP Server Setup on page 114.
To access all resolved problems in our solution database, or to search by product, category, keywords, or
phrases, go to http://support.proxim.com/. You can also find links to drivers, documentation, and downloads at
this link.
34
Chapter 5. Using the Web Interface

This section describes the 5054s Web Interface. The interface is described hierarchically according to these
buttons, which appear on the left side of the Web page:
System Status below

Configure on page 37
Monitor on page 103
Commands on page 110
Help and Exit buttons also appear; click the Help button to access online help; click the Exit button to exit the
application.
For an introduction to the basics of management, see Chapter 4. Basic Management on page 29.
SYSTEM STATUS
When you click the Status button, System Status is displayed automatically. The other tab under Status is the
Event Log tab.
View System Status

The Status tab showing the system status is displayed automatically when you log into the Web Interface. It also
is the default window displayed when you click the Status button on the left side of the window.
The Status tab shows the System Status and the System Traps.
System Status
The basic system status is shown in this section, including the version number of the embedded software.
Systems Traps
The status of system traps is shown in this section. System traps occur when the 5054 encounters
irregularities. Deleting system traps has no effect on the operation of the 5054. System traps also are sent to
an SNMP manager station (if so configured). See Alarm Traps in the Tsunami MP.11 Reference Manual for
a list and description of the traps.
35
View the Event Log Contents

Click the Status button and the Event Log tab to view the contents of your Event Log. The Event Log keeps
track of events that occur during the operation of the 5054. The Event Log displays messages that may not be
captured by System Traps, such as the Transmit Power for the Frequency Channel selected.
See Event Log Error Messages in the Tsunami MP.11 Reference Manual for an explanation of messages that
can appear in the Event Log.
36
CONFIGURE THE UNITS SETTINGS

Use the Configure section to change the units settings. The following tabs are in this section:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
System Parameters below

Network Parameters on page 42
Interfaces on page 52
SNMP on page 62
RIP on page 62
Management on page 65
Security on page 68
Filtering on page 70
Intra-Cell Blocking on page 79 (for BSUs in Bridge mode only)
VLAN (Virtual Local Area Network) on page 100 (for BSUs in Bridge mode only)
QoS (Quality of Service) on page 90 (for BSUs only)
NAT (Network Address Translation) on page 100 (for SUs in Routing mode only)
1) Configure System Parameters

The System configuration page lets you change the 5054s System Name, Location, and so on. These details
help you to distinguish the unit from other routers and let you know whom to contact in case you experience
problems.
Click the Configure button and the System tab; the following window is displayed.
In this window, you can view or change the basic system information. Mode of Operation sets the unit as bridge
(layer 2) or as router (layer 3). See Bridge and Routing Modes on page 39 for more information.
37
Field Descriptions
You can enter the following details:
System Name
This is the system name for easy identification of the BSU or SU. The System Name field is limited to a
length of 32 bytes. Use the system name of a BSU to configure the Base Station System Name parameter
on an SU if you want the SU to register only with this BSU. If the Base Station System Name is left blank
on the SU, it can register with any Base Station that has a matching Network Name and Network Secret.
Country
The Dynamic Frequency Selection (DFS) and Transmit Power Control (TPC) features are enabled
automatically when you choose a country with a regulatory domain that requires them. The Country
selection pre-selects and displays only the allowed frequencies for the selected country.
Click the Configure button, the Interfaces tab, and the Wireless sub-tab to see the channel/frequency list for
the selected Country.
Note:
Units sold in the United States are pre-configured to scan and display only the outdoor frequencies
permitted by the FCC. No other Country selections, channels, or frequencies can be configured.
Units sold outside of the United States and Canada support the selection of a Country by the
professional installer. If you change the Country, a reboot of the unit is necessary for the upgrade to
take place.
Support for the 5.25 5.35 GHz and 5.725 5.825 GHz frequency bands is provided with a single country
selection, UNITED STATES (US), which does not provide DFS capability in these frequency bands.
For a non US-only device, the default country selected is United Kingdom (GB).
Notes: (1) The channel center frequencies are not regulated; only the band edge frequencies are
regulated.
(2) If, before upgrade, US was selected as a country for a non US-Only device (which is an
incorrect configuration), the country is changed automatically to United Kingdom upon upgrade.
See Appendix A. Country Code/Channels Tables on page 129 for a list of country codes.
Location
This field can be used to describe the location of the unit, for example Main Lobby.
Contact Name, Contact Email, and Contact Phone
In these fields, you can enter the details of the person to contact.
Mode of Operation
This field lets you choose one of two operating modes: Bridge mode or Routing mode.
The static fields on this window are described as follows:
ObjectID
This field shows the OID of the product name in the MIB.
Ethernet MAC Address
The MAC address of the Ethernet interface of the device.
Descriptor
Shows the product name and firmware build version.
Up Time
The length of time the device has been up and running since the last reboot.
38
Bridge and Routing Modes
Bridge Mode
A bridge is a product that connects a local area network (LAN) to another local area network that uses the same
protocol (for example, Ethernet). You can envision a bridge as being a device that decides whether a message
from you to someone else is going to the local area network in your building or to someone on the local area
network in the building across the street. A bridge examines each message on a LAN, passing those known to be
within the same LAN, and forwarding those known to be on the other interconnected LAN (or LANs).
In bridging networks, computer or node addresses have no specific relationship to location. For this reason,
messages are sent out to every address on the network and accepted only by the intended destination node.
Bridges learn which addresses are on which network and develop a learning table so that subsequent messages
can be forwarded to the correct network.
Bridging networks are generally always interconnected LANs since broadcasting every message to all possible
destination would flood a larger network with unnecessary traffic. For this reason, router networks such as the
Internet use a scheme that assigns addresses to nodes so that a message or packet can be forwarded only in
one general direction rather than forwarded in all directions.
A bridge works at the data-link (physical) layer of a network, copying a data packet from one network to the next
network along the communications path.
The default Bridging Mode is Transparent Bridging.
This mode works if you do not use source routing in your network. If your network is configured to use source
routing, then you should use either Multi-Ring SRTB or Single-Ring SRTB mode.
In Multi-Ring SRTB mode, each unit must be configured with the Bridge number, Radio Ring number, and Token
Ring number. The Radio Ring number is unique for each Token Ring Access Point and the Bridge number is
unique for each Token Ring Access Point on the same Token Ring segment.
Alternatively, you may use the Single-Ring SRTB mode. In this mode, only the Token Ring number is required for
configuration.
Routing Mode
Routing mode can be used by customers seeking to segment their outdoor wireless network using routers instead
of keeping a transparent or bridged network. By default the unit is configured as a bridge device, which means
traffic between different outdoor locations can be seen from any point on the network.
By switching to routing mode, your network now is segmented by a layer 3 (IP) device. By using Routing mode,
each network behind the BSU and SUs can be considered a separate network with access to each controlled
through routing tables.
The use of a router on your network also blocks the retransmission of broadcast and multicast packets on your
networks, which can help to improve the performance on your outdoor network in larger installations.
The use of Routing mode requires more attention to the configuration of the unit and thorough planning of the
network topology of your outdoor network. The unit can use Routing mode in any combination of BSU and SUs.
For example, you may have the BSU in Routing mode and the SU in Bridge mode, or vice versa.
When using Routing mode, pay close attention to the configuration of the default gateway both on your unit and
on your PCs and servers. The default gateway controls where packets with unknown destinations (Internet)
should be sent. Be sure that each device is configured with the correct default gateway for the next hop router.
Usually this is the next router on the way to your connection to the Internet. You can configure routes to other
networks on your Intranet through the addition of static routes in your routers routing table.
39
Key Reasons to Use Routing Mode

One key reason why customers would use Routing mode is to implement virtual private networks (VPNs) or to let
nodes behind two different SUs communicate with each other. Many customers do this same thing in Bridging
mode by using secondary interfaces on the router at the BSU or virtual interfaces at the BSU in VLAN mode to
avoid some of the drawbacks of IP Routing mode.
Routing mode prevents the transport of non-IP protocols, which may be desirable for Service Providers
Routing mode is theoretically more efficient because Ethernet headers are not transported and non-IP traffic is
blocked.
Benefits of using Routing Mode
Enabling RIP makes the 5054 easier to manage for a Service Provider that uses RIP to dynamically manage
routes. RIP is no longer very common for Service Providers or Enterprise customers and an implementation
of a more popular routing protocol like OSPF would be desirable.
Routing mode saves bandwidth by not transporting non-IP protocols users might have enabled, like NetBEUI
or IPX/SPX, which eliminates the transmission of broadcasts and multicasts.
The MAC header is:
Destination MAC 6 bytes
Source MAC 6 bytes
Ethernet Type 2 bytes
If the average packet size is 1000 bytes, the overhead saved is 1.5%; With a frame size of 64 bytes, the
overhead saved is 20%; and for frame sizes of 128 bytes, the saving is 10%. Network researches claim that most
network traffic consists of frames smaller than 100 bytes.
In order to support routers behind the SUs with multiple subnets and prevent routing loops, you want individual
routes (and more then one) per SU.
Routing Mode Examples
In the first example, both the BSU and the SUs are configured for Routing mode. This example is appropriate for
businesses connecting remote offices that have different networks.
In example 2, the BSU is in Routing mode and the SUs are in Bridge mode. Notice the PCs behind the SUs must
configure their default gateways to point to the BSU, not the SU.
40
Notes:
One of the most important details to pay attention to in Routing mode are the units and the PCs default
gateways. It is a common mistake to set up the PCs gateway to point to the SU when the SU is in Bridge
mode and the BSU is in Routing mode. Always check to make sure the PCs on your network are configured
to send their IP traffic to the correct default gateway.
Be sure to reboot the unit to permanently save static routes. New routes take effect immediately without a
reboot, but are not permanently saved with your configuration until you do reboot the device. An unexpected
power outage could cause static routes you entered to disappear when the unit reboots if they have not
been saved. You also should save a copy of your units configuration file in case the unit must be reloaded.
This saves you from being required to re-enter numerous static routes in a large network.
The routing table supports up to 500 static routes.
41
2) Configure Network Parameters

Change IP Parameters
The IP Configuration window lets you change the 5054 IP parameters. These settings differ when the 5054 is in
Routing mode.
Click the Configure button, the Network tab, and the IP Configuration sub-tab to view and configure local IP
address information. See Setting the IP Address on page 18 for more information.
If the device is configured in Bridge mode, you can set the IP Address Assignment Type parameter:
Select Static if you want to assign a static IP address to the unit.
Select Dynamic to have the device run in DHCP client mode, which gets an IP address automatically from a
DHCP server over the network.
If you do not have a DHCP server or if you want to manually configure the IP settings, set this parameter to
Static.
When the 5054 is in Bridge mode, only one IP address is required. This IP address also can be changed with
ScanTool (see Setting the IP Address on page 18). In Routing mode, both Ethernet and Wireless interfaces
require an IP address.
You can set the following remaining parameters only when the IP Address Assignment Type is set to Static.
IP Address
The units static IP address (default IP address is 10.0.0.1).
Subnet Mask
The mask of the subnet to which the 5054 is connected (the default subnet mask is 255.255.255.0).
Default Router IP Address
The IP address of the default gateway.
Default TTL
The default time-to-live value.
42
Configure Spanning Tree Options

This protocol is executed between the bridges to detect and logically remove redundant paths from the network.
Spanning Tree can be used to prevent link-layer loops (broadcast is forwarded to all port where another device
may forward it and, finally, it gets back to this unit; therefore, it is looping). Spanning Tree can also be used to
create redundant links and operates by disabling links: hot standby customer is creating a redundant link without
routing function.
If your network does not support Spanning Tree, be careful to avoid creating network loops between radios. For
example, creating a WDS link between two units connected to the same Ethernet network creates a network loop
(if spanning tree is disabled).
The Spanning Tree configuration options are advanced settings. Proxim recommends that you leave these
parameters at their default values unless you are familiar with the Spanning Tree protocol.
Click the Spanning Tree tab to change Spanning Tree values.
Click Edit Table Entries to make changes; enter your changes and click OK.
43
Configure IP Routes (Routing Mode only)

Click the Configure button, the Network tab and the IP Routes sub-tab to configure IP routes. You cannot
configure IP Routes in Bridge mode. In Routing mode, the Add Table Entries and Edit/Delete Table Entries
buttons are enabled.
Click the Add button to add entries; a window such as the following is displayed:
44
Enter the route information and click Add. The IP Address and Subnet Mask combination is validated for a
proper combination.
Note:
When adding a new entry, the IP address of the Route Destination must be in either the Ethernet subnet
or in the wireless subnet of the unit.
Click the Edit/Delete Table Entries button to make changes to or delete existing entries.
Edit the route information and click OK. The IP address and subnet mask combination is validated for a proper
combination.
Enable or Disable Roaming

Roaming is a feature by which an SU terminates the session with the current BSU and starts the registration
procedure with another BSU when it finds the quality of the other BSU to be better. Roaming provides MAC level
connectivity to the SU that roams from one BSU to another. Roaming takes place across the range of frequencies
and channel bandwidths (5, 10, or 20 MHz) that are available per configuration (for a 5054 unit only the 20 MHz
bandwidth is applicable). The current release offers handoff times of up to a maximum of 80 ms. This is fast
enough to allow the SU to seamlessly roam from one BSU to the other therefore supporting session persistence
for delay-sensitive applications. The feature also functions as BSU backup in case the current BSU fails or
becomes unavailable.
The Roaming feature lets the SU monitor local SNR and data rate for all frames received from the current BSU.
As long as the average local SNR for the current BSU is greater than the slow scanning threshold, and the
number of retransmitted frames is greater than the slow scanning threshold given in percentage, the SU does not
scan other channels for a better BSU.
45
The normal scanning procedure starts when the average local SNR for the current BSU is less than or equal
to the slow scanning threshold and the number of retransmitted frames is greater than the slow scanning
threshold given in percentage. During the normal scanning procedure the SU scans the whole list of active
channels while maintaining the current session uninterrupted.
Fast scanning is the scanning procedure performed when the average local SNR for the current BSU is very
low (below the fast scanning threshold) and the number of retransmitted frames is greater than the fast
scanning retransmission threshold given in %, so that the current session should terminate as soon as
possible. During this procedure, the SU scans other active channels as fast as possible.
Roaming can only occur if the normal scanning or fast scanning procedure is started under the following
conditions:
1. If the roaming is started from the normal scanning procedure (after the SU scans all the active channels), the
SU selects the BSU with the best SNR value on all available channels. The SU roams to the best BSU only if
the SNR value for the current BSU is still below the slow scanning SNR threshold, and best BSU offers a
better SNR value for at least roaming threshold than the current BSU. The SU starts a new registration
procedure with the best BSU without ending the current session.
2. If the roaming is started from the fast scanning procedure, the SU selects the first BSU that offers better SNR
than the current BSU, and starts a new registration procedure with the better BSU without ending the current
session.
Roaming with Dynamic Data Rate Selection (DDRS) Enabled

There are two multicast rates to be configured when DDRS is enabled:
Default DDRS Data Rate (ddrsdefdatarate):
The data rate at which the BSU starts communication. This parameter is configurable; the default data rate is
adapted to the actual condition of the radio link.
Maximum DDRS Data Rate (ddrsmaxdatarate):
The maximum data rate at which the device can operate (the default is 36 Mbps)
When an SU roams from BSU-1 to BSU-2, the data rate at which it connects to BSU 2 is the default data rate. If
this remains at the factory default of 6 Mbps, there can be issues with the application if it requires more then
6 Mbps (for example multiple video streams).
Applications requiring a higher data rate could experience a slight data loss during the roaming process while
DDRS selects a higher rate (based upon link conditions).
When the applications re-transmit at a possibly slower rate, the WORP protocol initially services the data at
6 Mbps and increases the data rate to the "Maximum DDRS Data Rate" one step at a time. Because the
applications are not being serviced at the best possible rate, they further slow down the rate of data send.
The DDRS algorithm requires data traffic (a minimum of 128 frames) to raise the rate to a higher value. Although
roaming occurs successfully, the previous scenario causes applications to drop their sessions; hence session
persistence is not maintained.
For a discussion of DDRS, see Dynamic Data Rate Selection (DDRS) Status on page 53.
Note:
You must know the data rate required for the applications running and you must ensure (during network
deployment) that the ranges and RF links can support the necessary data rate. You also must set the
default DDRS rate at the capacity necessary for the application so that it connects to the next base
station at the required capacity if roaming occurs. Set the Default DDRS Data Rate to a greater value
(24, 36, 48 or 54 Mbps, for example) for applications requiring session persistence when roaming occurs.
46
Click the Configure button, the Network tab and the Roaming sub-tab to configure Roaming. The screen differs
depending on whether the unit is configured as a BSU or as an SU.
BSU Screen
Enable or disable the Roaming feature by clicking on the Enable Roaming Status check box. The default value
is disabled (clear). If you enable roaming, you may set the Announcement Period (from 25 to 100 ms, default is
100 ms).
On this screen you may also enable or disable the Multi-Frame Bursting (default value is enabled).
Click the check box

to enable roaming.
An SU scans all available channels for a given bandwidth during roaming. In order to reduce the number of
channels an SU has to scan and thus decrease the roaming time, a channel priority list that tells the SU what
channels to scan is implemented. Each channel in the channel priority list is specified with its corresponding
bandwidth and the priority with which it should be scanned, either Active (standard priority), Active High (high
priority), or Inactive.
An SU will scan all channels indicated as Active during roaming. However, it will scan active channels indicated
as High Priority before scanning active channels indicated as standard priority. Channels that are not going to
be used in the wireless network should be configured as Inactive so that the SU can skip over those channels
during scanning saving this way time.
A BSU broadcasts the channel priority list to all valid authenticated SUs in its sector. It re-broadcasts the channel
priority list to all SUs every time the list is updated on the BSU.
47
Click Edit Table Entries to make changes; enter your changes and click OK.
Note that an SU may roam from one BSU with a bandwidth setting to another BSU with a different bandwidth
setting. Since in this case more channels need to be scanned than with only one channel bandwidth setting, it is
important that the channel priority list mentioned above is properly used to limit scanning time.
When Scanning Across Bandwidth on the SU is enabled (see Configure Interface Settings on page 52), the
SU supports bandwidth selection of the communications channel of either 20 MHz, 10 MHz, or 5 MHz. This allows
the BSUs in the network to be set to different bandwidths while an SU can still roam from one BSU to the next,
because it will not only scan other frequencies (when the signal level or quality are lower than the threshold) but it
will also switch to other bandwidths to find a BSU that may be on another bandwidth than its current one.
During roaming, the SU will start scanning first the channels on its current bandwidth from the Active channel list
provided by the BSU in order to find a BSU to register, since that is the most likely setting for other BSUs in the
network. If the SU cannot find an acceptable roaming candidate, it will switch bandwidth and start scanning
channels on that corresponding bandwidth from the Active channel list provided by the BSU. The process is
repeated until the SU finds an appropriate BSU to register.
In the example above, an SU whose current bandwidth is 20 MHz will start scanning all active channels within the
bandwidth of 20 MHz. If it cannot find a suitable BSU, it will switch to a 10 MHz bandwidth and start scanning all
active channels within that bandwidth, in this case channel 56 first since it is configured as high priority and
channel 60 next. No channels will be scanned on the 5 MHz bandwidth since all those channels are configured as
inactive.
48
SU Screen
Enable or disable the Roaming feature in the Roaming Status drop-down box. The default value is disabled.
Note: To enable roaming, you must enable Roaming Status on both the BSU and the SU.
Enable and Configure the DHCP Server

Click the Configure button, the Network tab and the DHCP Server sub-tab to enable the unit on a DHCP Server.
The Gateway IP Address and Primary DNS IP Address must be entered, there must be at least one entry in the
DHCP Server IP Pool Table, and the DHCP Relay Agent must be disabled, in order to enable the DHCP Server.
When enabled, the DHCP server allows allocation of IP addresses to hosts on the Ethernet side of the SU or
BSU. Specifically, the DHCP Server feature lets the SU or BSU respond to DHCP requests from Ethernet hosts
with the following information:
Host IP address
Gateway IP address
Subnet Mask
DNS Primary Server IP address
DNS Secondary Server IP address
49
Field Descriptions
DHCP Server Status
Verify that DHCP Relay Agent is disabled. After you have made at least one entry in the DHCP server IP Pool
Table, enable DHCP Server by selecting Enable from the DHCP Server Status pull-down menu.
Note:
There must be at least one entry in the DHCP server IP Pool Table to enable DHCP server. Also,
DHCP server cannot be enabled if DHCP Relay Agent is enabled.
Subnet Mask
The unit supplies this subnet mask in its DHCP response to a DHCP request from an Ethernet host. Indicates
the IP subnet mask assigned to hosts on the Ethernet side using DHCP.
Gateway IP Address
The 5054 supplies this gateway IP address in the DHCP response. Indicates the IP address of a router
assigned as the default gateway for hosts on the Ethernet side.
Primary DNS IP Address
The 5054 supplies this primary DNS IP address in the DHCP response. Indicates the IP address of the
primary DNS server that hosts on the Ethernet side uses to resolve Internet host names to IP addresses
Secondary DNS IP Address
The 5054 supplies this secondary DNS IP address in the DHCP response.
Number of IP Pool Table Entries
The number of IP pool table entries is a read-only field that indicates the total number of entries in the DHCP
server IP Pool Table. See DHCP Server IP Pool Table below.
Add Entries to the DHCP Server IP Pool Table

You can add up to 20 entries in the IP Pool Table. An IP address can be added if the entrys network ID is the
same as the network ID of the device. To add an entry click Add Table Entries.
Enter the following parameters and click Add.

Note: After adding entries, you must reboot the unit before the values take effect.
Field Descriptions
Start IP Address
Indicates the starting IP address that is used for assigning address to hosts on the Ethernet side in the
configured subnet.
50
End IP Address
Indicates the ending IP address that is used for assigning address to hosts on the Ethernet side in the
configured subnet.
Default Lease Time
Specifies the default lease time for IP addresses in the address pool. The value is 3600-86400 seconds.
Max Lease Time
The maximum lease time for IP addresses in the address pool. The value is 3600-86400 seconds.
Comment
The comment field is a descriptive field of up to 255 characters.
Edit/Delete Entries to the DHCP Server IP Pool Table Entries

Click Edit/Delete Table Entries to make changes; enter your changes and click OK.
Enable the DHCP Relay Agent (Routing mode only)

Click the Configure button, the Network tab, and the DHCP RA sub-tab to enable the 5054 DHCP Relay Agent.
When enabled, the DHCP relay agent forwards DHCP requests to the set DHCP server.
Note that DHCP Relay Agent parameters are configurable only in Routing mode.
Add Entries to the DHCP Relay Agent Table

To add entries to the table of DHCP Relay Agents, click Add Table Entries; the following window is displayed.
51
Enter the Server IP Address and any optional comments; click Add.
Edit/Delete Entries to the DHCP Relay Agent Table

Click Edit/Delete Table Entries to make changes; enter your changes and click OK.
3) Configure Interface Settings

Configure the Wireless Interface
To configure the wireless interface, click the Configure button followed by the Interfaces tab; then click the
Wireless sub-tab.
For Base Station units, the wireless interface can be placed in either WORP Base or WORP Satellite mode
(selected from the Interface Type drop-down box). SUs can be placed only in WORP Satellite mode. The
wireless interface settings depend upon whether the mode is Base or Satellite.
The Wireless Outdoor Router Protocol (WORP) is a polling algorithm designed for wireless outdoor networks.
WORP takes care of the performance degradation incurred by the so-called hidden-node problem, which can
occur when wireless LAN technology is used for outdoor building-to-building connectivity. In this situation, when
multiple radios send an RTS, if another radio is transmitting, it corrupts all data being sent, degrading overall
performance. The WORP polling algorithm ensures that these collisions cannot occur, which increases the
performance of the overall network significantly.
WORP dynamically adapts to the number of SUs that are active on the network and the amount of data they have
queued to send.
The following are examples of the Wireless window when the country selected is US, and for countries different
than the US:
52
Base Mode US Country
Field Descriptions:
Interface Type
The interface type can be WORP Satellite or WORP Base.
Network Name
A Network Name is a name given to a network so that multiple networks can reuse the same frequency
without problems. An SU can only register to its base if it has the same Network Name. The Network Name
is one of the parameters that allow a Subscriber Unit to register on a Base Station. The Base Station
System Name and Frequency Channel also are parameters to guide the SU to the proper BSU on the
network, but they provide no security. Basic security is provided through encryption, as it causes none of the
messages to be sent in the clear. Further security is provided by mutual authentication of the BSU and SU
using the Network Secret. The Network Name can be 2 to 32 characters in length.
Operational Mode (not configurable)
This field indicates the operational mode of the unit 11a, 11b, or 11g depending upon the specific
Tsunami MP.11. This operational mode cannot be changed as it is based upon a license file. For the 5054,
this field shows 11a.
Dynamic Data Rate Selection (DDRS) Status
The WORP Dynamic Data Rate Selection (DDRS) lets the BSU and SUs monitor the remote average
signal-to-noise ratio (SNR) and to adjust the data rate to an optimal value (to provide best possible
throughput) according to the current communication conditions during run-time.
Each frame received in the WORP protocol reports the signal and noise level in dBm at which the sender
received the previous frame from the receiver, and provides the values to calculate the signal to noise ratio
(SNR) in dB. SNR is calculated then averaged:
53
SNR [dB] = signal level [dBm] noise level [dBm]

This information lets the sender adjust the transmission data rate to the optimal level to provide the best
possible throughput.
When you enable or disable WORP DDRS on the BSU, the BSU sends an announcement to the SUs and the
SUs enable or disable WORP DDRS automatically.
Note:
DDRS threshold values must be configured in the BSU and SUs separately through the CLI or the
SNMP interface.
Both the BSU and the SU monitor the remote SNR. The BSU monitors and calculates the average remote
SNR for each SU that is registered. An SU monitors and calculates the average remote SNR for the BSU.
The DDRS Status is configurable only for the WORP Base Mode. For WORP Base Mode, select the DDRS
Status Enable or Disable from the drop-down box provided.
For the WORP Satellite Mode, DDRS Status is read-only parameter and its value is based upon the WORP
Base to which this SU is associated.
By default, the 5054 lets you transmit at the maximum output power for the country or regulatory domain and
frequency selected. However, with Transmit Power Control (TPC), you can adjust the output power of the
unit to a lower level in order to reduce interference to neighboring devices or to use a higher gain antenna
without violating the maximum radiated output power allowed for your country. Also, most countries in the
ETSI regulatory domain require the transmit power to be set to a 6 dB lower value than the maximum allowed
EIRP when link quality permits. You can see your units current output power for the selected frequency in the
event log.
The event log shows the selected power for all data rates, so you must look up the proper data rate to
determine the actual power level.
Note:
This feature only lets you decrease your output power; it does not let you increase your output power
beyond the maximum allowed defaults for your frequency and country.
Select one of the following options and click OK at the bottom of the window. Your original output power is
adjusted relative to the value selected. The new setting takes effect immediately without rebooting:
TPC Selection
dB
0
-3
-6
-9
-12
-15
-18 (minimum TPC level)
Maximum TX Power
dBm
16
13
10
7
4
1
0
Enable Turbo Mode

Check this box to enable Turbo Mode. Turbo Mode is supported only in the United States.
Enabling turbo mode, in its current implementation, allows the 5054 to use two adjacent frequency channels
to transmit and receive a signal. This works at 12, 18, 24 and 36 Mbps. By enabling turbo mode, the receive
sensitivity improves by 4 dB for the 36 Mbps data rate and by 2 dB for the 24 Mbps data rate.
54
Note:
The additional sensitivity is provided with the impact of using twice as much spectrum and thus
increasing the opportunity of interference and decreased ability for system collocation. Generally,
Turbo mode is not recommended except when the extra sensitivity is absolutely required
Frequency Channel
The frequency channel indicates the band center frequency the unit uses for communicating with peers. This
frequency channel can be set in several ranges, depending upon regulatory domain. Refer to Appendix A.
Country Codes/Channels on page 129 for channelization information.
For countries in which DFS is not enabled, the Frequency Channel list displays only the channels and
frequencies allowed for the selected country.
Multicast Rate
The rate at which data is to be transferred. This drop down box is unavailable when DDRS is enabled.
The default data rate for the 5054 is 36 Mbps. The SU must never be set to a lower data rate than the BSU
because timeouts will occur at the BSU and communication will fail.
Selections for multicast rate are shown in the following table:
Date Rate
6 Mbps
9 Mbps
12 Mbps
18 Mbps
24 Mbps
36 Mbps
48 Mbps (see Note)
54 Mbps (see Note)
Note:
Date Rate, Turbo Enabled

12 Mbps
18 Mbps
24 Mbps
36 Mbps
48 Mbps
72 Mbps
96 Mbps (see Note)
108 Mbps (see Note)
If you select 48 or 54 Mbps (96 or 108 in Turbo mode) DDRS is automatically turned on.
Antenna Gain (BSU only)

You can modify the sensitivity of the radio card when detecting radar signals in accordance with ETSI and
FCC Dynamic Frequency Selection (DFS) requirements. Given the radar detection threshold is fixed by ETSI
and the FCC and that a variety of antennas with different gains may be attached to the 5054, you must adjust
this threshold to account for higher than expected antenna gains and avoid false radar detection events. This
can result in the units constantly changing frequency channels.
You can 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 35. The default value is 0.
Satellite Density
The Satellite Density setting is a valuable feature for achieving maximum bandwidth in a wireless network. It
influences the receive sensitivity of the radio interface and improves operation in environments with a high
noise level. Reducing the sensitivity of the unit enables unwanted noise to be filtered out (it disappears
under the threshold).
You can configure the Satellite Density to be Large, Medium, Small, Mini, or Micro. The default value for
this setting is Large. The smaller settings are appropriate for high noise environments; a setting of Large
would be for a low noise environment.
A long distance link may have difficulty 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 10 dB below the present signal strength.
55
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
configuration, the BSU should have a density setting suitable for all of its registered SUs, especially the ones
with the lowest signal levels (longest links).
Take care when configuring a remote interface; check the available signal level first, using Remote Link Test.
Warning!
When the remote interface accidentally is set at too small a value and communication is lost, it cannot be
reconfigured remotely and a local action is required to bring the communication back. Therefore, the best place
to experiment with the level is at the unit 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.
To set the Satellite Density, click the Configure button, then the Interfaces tab and the Wireless sub-tab.
Make your density selection from the drop-down menu. This setting requires a reboot of the unit.
Sensitivity threshold settings related to the density settings for the MP.11a are:
Satellite Density
Large
Medium
Small
Mini
Micro
Receive Sensitivity Threshold
-95 dBm
-86 dBm
-78 dBm
-70 dBm
-62 dBm
Defer Threshold
-62 dBm
-62 dBm
-52 dBm
-42 dBm
-36 dBm
Maximum Satellites (BSU only)

You can specify a maximum value of 250 in this field, because up to 250 SUs can be connected to a BSU. If a
BSU already has as many SUs as specified in this field, a new SU cannot connect to the BSU.
No-Sleep Mode (BSU only)
No-Sleep Mode was a feature used to control jitter in Tsunami MP.11 products running 2.2.6, and earlier,
versions of software. The introduction of QoS and the new WORP resource scheduling mechanism have
eliminated the need for No-Sleep Mode. Furthermore, QoS provides better control over jitter and latencysensitive applications (see QoS (Quality of Service) Parameters on page 91 for details on configuration).
This field is inactive and makes no difference whether is enabled or disabled.
Automatic Multi-Frame Bursting (BSU only)
In order to achieve higher throughput, WORP protocol allows each side (BSU or SU) to send a burst of up to
4 data messages instead of a single data message. The sole criteria for sending a burst is enough traffic to be
sent out. This feature is called Multi-Frame Bursting support.
Automatic Multi-Frame bursting optimizes multi-burst performance when configuring QoS high-priority Service
Flows. Three scenarios may be defined:
No Multi-Frame burst support To disable Multi-Frame burst support, click Disable on the drop-down
box of the Configure, Network, Roaming sub-tab (see BSU Screen on page 53). In this case, each
active SFC is limited to send a single data message. Total throughput available to remaining best effort
traffic is around 76% of the maximum available throughput.
Multi-Frame burst support The system will enable Multi-Frame burst for all SFCs, but the maximum
number of data messages sent in a burst will be defined by the parameter Number of data messages in
a burst for each of the SFCs (see Service Flow Class (SFC) on page 26). This scenario is set by
enabling Multi-Frame burst on the drop-down box of the Configure, Network, Roaming sub-tab (see
BSU Screen Error! Bookmark not defined.) and disabling Automatic Multi-Frame Bursting (this
parameter).
The maximum number of data messages in a burst directly influences the total throughput of the system.
Typical values are:
56
No. of messages in a burst:
% of the maximum throughput:
100 %
97.6 %
92.9 %
76.2%
Automatic Multi-Frame burst support The system will continuously be monitoring which of the active
SFCs has the highest priority and dynamically enable Multi-Frame burst for the highest priority SFC only,
keeping all the lower priority SFCs with Multi-Frame burst disabled. If there are multiple SFCs having the
same, highest priority, all of them will have Multi-Frame burst enabled. The maximum number of data
messages sent in a burst is defined by the parameter Number of data messages in a burst and it can be
different for each SFC (see Service Flow Class (SFC) on page 26). This scenario is set by enabling
Multi-Frame burst on the drop-down box of the Configure, Network, Roaming sub-tab (see BSU
Screen Error! Bookmark not defined.) and enabling Automatic Multi-Frame Bursting (this
parameter). In this case, even the lowest priority SFC will have Multi-Frame burst dynamically enabled as
long as it is the only SFC in the system that has traffic. By default, configuring even a single high priority
SFC with automatic multi-frame bursting enabled will decrease throughput of low priority best-effort traffic
to approximately 76% of maximum available throughput, because low priority traffic will have Multi-Frame
burst disabled to optimize bandwidth for the high priority traffic.
Registration Timeout
This is the registration process time-out of an SU on a BSU. Default is 5 seconds.
Network Secret
A network secret is a secret password given to all nodes of a network. An SU can only register to a BSU if it
has the same Network Secret. The Network Secret is sent encrypted and can be used as a security option.
Input / Output Bandwidth Limit
These parameters limit the data traffic received on the wireless interface and transmitted to the wireless
interface, respectively. Selections are in steps of 64 Kbps from 64 to 108,064 Kbps.
57
Satellite Mode US Country
Field Descriptions
All the fields that are common to both the BSU and the SU are applicable here. The SU features two additional
fields:
Base Station System Name (SU only)
The name found on the system page of the BSU to which this SU is connecting. This parameter can be used
as an added security measure, and when there are multiple BSUs in the network and you want an SU to
register with only one when it may actually have adequate signal strength for either. The System Name field
is limited to a length of 32 bytes.
If the Base Station System Name is left blank on the SU, it can register with any BSU with a matching
Network Name and Network Secret.
58
Base Mode Non-US Country
Select a DFS
preferred channel
from the channels
defined as Disable
in the Channel
Blacklist Table.
Click Edit if you

want to manually
blacklist DFS
channels.
Field Descriptions
The differences between the BSU Wireless interface screen for a non-US country and the equivalent screen for
the US are:
There is no Turbo Mode.

Frequency Channel is not configurable. Instead the channel is auto-selected by the DFS process.
All the other fields that appear in the US screen for the BSU are applicable. There are also these additional fields:
DFS Preferred Channel
A single DFS preferred frequency channel on the BSU is provided so that when the DFS process starts the
BSU will first try the DFS preferred channel before scanning all the other active channels in the DFS channel
list. The DFS preferred channel must be selected from those channels indicated as Disable in the DFS
59
channel blacklist list. It is not possible to select the DFS preferred channel from those channels in the DFS
channel blacklist list indicated as Enable.
Channel Blacklist Table
The DFS channel blacklist table shows all the channels in the current bandwidth and specifies the blacklist
status of each channel as one of the following:
Enable Channels that are made unavailable either for a certain period of time upon detection of a radar
signal, or permanently because the operator has configured them as blacklisted. These channels are
skipped over during DFS channel selection.
Disable Channels that are to be scanned during DFS.
Edit Entries to the Channel Blacklist Table

In accordance to the EN301-893 non-occupancy rule, when a radar signal is detected on any active channel, the
blacklist status of that channel will change to Enable and the Radar Detected status will change to TRUE (see
previous figure). The channel will not be used for a period of 30 minutes after the radar signal has been detected.
The elapsed time is also shown in the DFS channel blacklist table. When the elapsed time for a channel in the
blacklist is greater than or equal to 30 minutes, the blacklist status of the channel will change to Disable and the
Radar Detected and Elapsed Time fields will change accordingly.
If an operator knows in advance on which channels a radar signal is likely to exist, those channels can be
blacklisted and hence they will be skipped during DFS. Similarly, if the operator knows of channels where a radar
signal is unlikely to be detected, those channels can be defined as active and hence they will be scanned during
DFS. This makes the whole process more efficient.
When you click Edit the channel blacklist table screen appears. Here you can manually configure each channel
as active (Blacklist Status = Disable) or blacklisted (Blacklist Status = Enable). Enter your changes and click
OK. To go back, click on the arrow button.
60
Satellite Mode Non-US Country
Field Descriptions
The differences between the SU Wireless interface screen for a non-US country and the equivalent screen for the
US are:
There is no Turbo Mode.

Frequency Channel is not configurable. Instead the channel is auto-selected by the DFS process.
All the other fields that appear in the US screen for the SU are applicable.
Notes:
Turbo mode is available only when the specified Country is US.
The list of parameters to configure for registration of the SU on a Base Station are:
Network Name
Base Station System Name (when used)
Channel Frequency
Encryption (when used)
Network Secret
61
Configure the Ethernet Interface

To set the Ethernet speed, duplex mode, and input and output bandwidth limits, click the Configure button, the
Interfaces tab, and the Ethernet sub-tab.
You can set the desired speed and transmission mode by clicking on Configuration. Select from these settings
for the type of Ethernet transmission:
Half-duplex means that only one side can transmit at a time.
Full-duplex lets both sides transmit.
Auto-duplex selects the best transmission mode available when both sides are set to auto-select.
The recommended setting is auto-speed-auto-duplex.
4) Configure SNMP Parameters

Click the Configure button and the SNMP tab to enable or disable trap groups, and to configure the SNMP
management stations to which the 5054 sends system traps. See Trap Groups in the Tsunami MP.11 Reference
Manual for a list of the system traps.
Trap Groups
You can enable or disable different types of traps in the system. By default, all traps are enabled.
Trap Host Table
This table shows the SNMP management stations to which the 5054 sends system traps.
Add Entries to the Trap Host Table

Click the Add Table Entries button to add entries to the Trap Host Table.
Edit/Delete Entries to the Trap Host Table

Click the Edit/Delete Table Entries button to make changes to or delete existing entries.
5) Configure RIP Parameters

Routing Internet Protocol (RIP) is a dynamic routing protocol you can use to help automatically propagate routing
table information between routers. The Tsunami 5054 can be configured as RIPv1, RIPv2, RIPv1 Compatible, or
a combination of all three versions, while operating in Routing mode. In general, the 5054 RIP module is based
upon RFC 1389.
Note:
RIP does not work when Network Address Translation (NAT) is enabled.
62
Note the following:
There is no option to turn off receiving RIP advertisements. Once the unit is in Routing mode, it receives RIP
updates when there is another RIP-enabled device advertising on your network. Although it receives and
processes these updates, it does not further propagate these updates unless configured to advertise RIP.
The ability to enable or disable default route propagation is not user configurable. Once initialized, the 5054
uses its static default route and does not advertise this route in RIP updates. If another router on your
network is configured to advertise its default route, this route overwrites the static default route configured on
the 5054. The 5054 then also propagates the new dynamic default route throughout the network.
Be aware that, once a dynamic default route is learned, it behaves just as any other dynamic route learned
through RIP. This means if the device sending the default route stops sending RIP updates, the default route
times out and the unit has no default route to the network. Workarounds for this condition include rebooting or reentering a static default route. In general, the best approach is to disable the propagation of default routes on the
other routers in your network unless you understand the risks.
The following table describes the properties and features of each version of RIP supported.
Properties and Features of Supported RIP Versions
RIPv1
RIPv2
RIPv1 Compatible
Broadcast
Multicast
Broadcast
No Authentication
Authentication
Authentication
Class routing
Classless routing (VLSM)
Classless routing (VLSM)
Distance-vector protocol
Metric-Hops
Metric-Hops
Metric-Hops
Maximum Distance 15
Maximum Distance 15
Maximum Distance 15
IGP
IGP
IGP
63
RIP Example
In the following example, assume that both the BSU and the SUs all are configured in Routing mode with RIP
enabled to send and receive on both the Ethernet and Wireless interfaces. The network converges through
updates until each unit has the following routing table:
BSU
0.0.0.0
172.16.0.0
10.0.0.0
100.0.0.0
200.0.0.0
172.16.0.1
172.16.0.20
10.0.0.1
10.0.0.2
10.0.0.3
metric
metric
metric
metric
metric
1
1
1
2
2
10.0.0.1
10.0.0.2
100.0.0.1
10.0.0.1
10.0.0.2
metric
metric
metric
metric
metric
1
1
1
2
2
10.0.0.1
10.0.0.3
200.0.0.1
10.0.0.1
10.0.0.2
metric
metric
metric
metric
metric
1
1
1
2
2
SU1
0.0.0.0
10.0.0.0
100.0.0.0
172.16.0.0
200.0.0.0
SU2
0.0.0.0
10.0.0.0
200.0.0.0
172.16.0.0
100.0.0.0
64
RIP Notes
Ensure that routers on the same physical network are configured to use the same version of RIP.
Routing updates occur every 30 seconds. It may take up to 3 minutes for a route that has gone down to
timeout in a routing table.
RIP is limited to networks with 15 or fewer hops.
6) Configure Management Parameters

When you click the Management button, Passwords is displayed automatically. The other tab under
Management is the Services tab.
Configure Passwords
The Password tab lets you configure the SNMP, Telnet, and HTTP (Web Interface) passwords.
Field Descriptions
For all password fields, the passwords must be between 6 and 32 characters.. Changes take effect immediately
after you click OK.
SNMP Read Community Password
The password for read access to the 5054 using SNMP. Enter a password in both the Password field and the
Confirm field. The default password is public.
SNMP Read/Write Community Password
The password for read and write access to the 5054 using SNMP. Enter a password in both the Password
field and the Confirm field. The default password is public.
Telnet (CLI) Password
The password for the CLI interface (via serial or Telnet). Enter a password in both the Password field and the
65
HTTP (Web) Password

The password for the Web browser HTTP interface. Enter a password in both the Password field and the
Configure Service Parameters

The Services tab lets you configure the SNMP, Telnet, and HTTP (Web Interface) parameters. Changes to these
parameters require a reboot to take effect.
SNMP Configuration Settings

SNMP Interface Bitmask:
Configure the interface or interfaces (Ethernet, Wireless, All Interfaces) from which you will manage the
5054 using SNMP. You also can select Disabled to prevent a user from accessing the unit through SNMP.
HTTP Configuration Settings

HTTP Interface Bitmask
Configure the interface or interfaces (Ethernet, Wireless, All Interfaces) from which you will manage the
5054 through the Web interface. For example, to allow Web configuration through the Ethernet network only,
set HTTP Interface Bitmask to Ethernet. You can also select Disabled to prevent a user from accessing the
5054 from the Web interface.
HTTP Port
Configure the HTTP port from which you will manage the 5054 through the Web interface. By default, the
HTTP port is 80.
66
Telnet Configuration Settings

Note:
To use HyperTerminal for CLI access, make sure to check Send line ends with line feeds in the ASCII
Setup window (click Properties from the HyperTerminal window; select Setup, then ASCII Setup. See
HyperTerminal Connection Properties in the Tsunami MP.11 Reference Manual for more information).
Telnet Interface Bitmask

Select the interface (Ethernet, Wireless, All Interfaces) from which you can manage the 5054 through telnet.
This parameter can also be used to disable telnet management.
Telnet Port Number
The default port number for Telnet applications is 23. However, you can use this field if you want to change
the Telnet port for security reasons (but your Telnet application also must support the new port number you
select).
Telnet Login Timeout (seconds)
Enter the number of seconds the system is to wait for a login attempt. The 5054 terminates the session when
it times out. The range is 1 to 300 seconds; the default is 30 seconds.
Telnet Session Timeout (seconds)
Enter the number of seconds the system is to wait during a session while there is no activity. The 5054 ends
the session upon timeout. The range is 1 to 36000 seconds; the default is 900 seconds.
Serial Configuration Settings

The serial port interface on the 5054 is enabled at all times. See Serial Port in the Tsunami MP.11 Reference
Manual for information about how to access the CLI interface through the serial port. You can configure and view
following parameters:
Serial Baud Rate
Select the serial port speed (bits per second). Choose between 2400, 4800, 9600, 19200, 38400, or 57600;
the default Baud Rate is 9600.
Serial Flow Control
Select either None (default) or Xon/Xoff (software controlled) data flow control.
To avoid potential problems when communicating with the 5054 through the serial port, Proxim recommends
that you leave the Flow Control setting at None (the default value).
Serial Data Bits
This is a read-only field and displays the number of data bits used in serial communication (8 data bits by
default).
Serial Parity
This is a read-only field and displays the number of parity bits used in serial communication (no parity bits by
default).
Serial Stop Bits
This is a read-only field that displays the number of stop bits used in serial communication (1 stop bit by
default).
The serial port bit configuration is commonly referred to as 8N1.
67
7) Configure Security Parameters

Configure MAC Authentication
Click the Configure button, the Security tab, and the MAC Auth sub-tab to build a list of authorized wireless
stations that can register at the 5054 and access the network.
MAC authentication is available only for BSUs.
This feature is supported on the wireless interface and only wireless MAC addresses should be entered in the list.
For example, build a list of wireless MAC addresses on the BSU for the authorized SUs.
To add table entries, click the Add Table Entries button; a window such as the following is displayed:
Enter the MAC address and any comment, then click Add. The maximum number of MAC addresses that can be
entered is 250.
To edit or delete table entries, click the Edit/Delete Table Entries button; make your corrections in the window
displayed and click OK.
68
Configure RADIUS Authentication

Click the Configure button, the Security tab, and the Radius Auth sub-tab to set the IP address of the RADIUS
server containing the central list of MAC addresses that are allowed to access the network. The RADIUS
parameters let you enable HTTP or Telnet RADIUS management access to configure a RADIUS Profile for
management access control, to enable or disable local user access, and to configure the local password.
RADIUS authentication is available only for BSUs.
In large networks with multiple 5054 devices, you can maintain a list of MAC addresses on a centralized location
using a RADIUS authentication server that grants or denies access. If you use this kind of authentication, you
must specify at least the primary RADIUS server. The backup RADIUS server is optional.
Configure Encryption Parameters

Be sure to set the encryption parameters and change the default passwords.
You can protect the wireless data link by using encryption. Encryption keys can be 5 (64-bit), 13 (WEP 128-bit),
or 16 (AES 128-bit) characters in length. Both ends of the wireless data link must use the same parameter
values.
In addition to Wi-Fi Protected Access (WPA) and Wired Equivalent Privacy (WEP), the unit supports Advanced
Encryption Standard (AES) 128-bit encryption. To provide even stronger encryption, the AES CCM Protocol is
also supported.
Click the Configure button, the Security tab, and the Encryption sub-tab to set encryption keys for the data
transmitted and received by the 5054. Note that all devices in one network must use the same encryption
parameters to communicate to each other.
69
8) Configure Packet Filtering

Click the Configure button and the Filtering tab to configure packet filtering. Packet filtering can be used to
control and optimize network performance. Filtering sub-tabs are as follows:
The Filtering feature can selectively filter specific packets based upon their Ethernet protocol type. Protocol
filtering is done at the Bridge layer.
Protocol filters are useful for preventing bridging of selected protocol traffic from one segment of a network to
other segments (or subnets). You can use this feature both to increase the amount of bandwidth available on
your network and to increase network security.
Increasing Available Bandwidth

It may be unnecessary to bridge traffic from a subnet using IPX/SPX or AppleTalk to a segment of the network
with UNIX workstations. By denying the IPX/SPX AppleTalk traffic from being bridged to the UNIX subnet, the
UNIX subnet is free of this unnecessary traffic.
Increasing Network Security

By bridging IP and IP/ARP traffic and blocking LAN protocols used by Windows, Novell, and Macintosh servers,
you can protect servers and client systems on the private local LAN from outside attacks that use those LAN
protocols. This type of filtering also prevents private LAN data from being bridged to an untrusted remote network
or the Internet.
To prevent blocking your own access to (administrator) the unit, Proxim recommends that IP (0x800) and ARP
(0x806) protocols are always passed through.
70
Sample Use and Validation

Configure the protocol filter to let only IP and ARP traffic pass through the MP.11 (bridge) from one network
segment to another. Then, attempt to use Windows file sharing across the bridge. The file should not allow
sharing; the packets are discarded by the bridge.
Setting the ARP Filter

There may be times when you need to set the ARP or Multicast. Usually, this is required when there are many
nodes on the wired network that are sending ARP broadcast messages or multicast packets that unnecessarily
consume the wireless bandwidth. The goal of these filters is to allow only necessary ARP and multicast traffic
through the 1.6 Mbps wireless pipe.
The TCP/IP Internet Protocol Suite uses a method known as ARP (Address Resolution Protocol) to match a
device's MAC (Media Access Control) address with its assigned IP address. The MAC address is a unique 48-bit
identifier assigned to each hardware device at the factory by the manufacturer. The MAC address is commonly
represented as 6 pairs of hexadecimal digits separated by colons. For example, a RangeLAN2 device may have
the MAC address of 00:20:A6:33:ED:45.
When devices send data over the network (Ethernet, Token Ring, or wireless), they use the MAC address to
identify a packet's source and destination. Therefore, an IP address must be mapped to a MAC address in order
for a device to send a packet to particular IP address. In order to resolve a remote node's IP address with its MAC
address, a device sends out a broadcast packet to all nodes on the network. This packet is known as an ARP
request or ARP broadcast and requests that the device assigned a particular IP address respond to the sender
with its MAC address.
Because ARP requests are broadcast packets, these packets are forwarded to wireless nodes by default, even if
the packet is not meant for a wireless node. As the number of nodes on a network backbone increases, so does
the number of ARP broadcasts that are forwarded to the wireless nodes. Many of these ARP broadcasts are
unnecessary and can consume valuable wireless bandwidth. On some networks, there are so many ARP
broadcasts that the performance of the wireless network will degrade due to the amount of bandwidth being
consumed by these messages.
To reduce the number of ARP broadcasts that are forwarded to the wireless nodes, you can enable ARP filtering.
When enabled, the ARP Filter allows the unit to forward only those ARP broadcasts destined for an IP address
that falls within the range specified by the ARP Filter Network Address and the ARP Filter Subnet Mask. The ARP
Filter performs a logical AND function (essentially keeping what is the same and discarding what is different) on
the IP address of the ARP request and the ARP Filter Subnet Mask. It then compares the result of the logical
AND to the ARP Filter Network Address. If the two values match, the ARP broadcast is forwarded to the wireless
network by the unit.
71
Configure Ethernet Protocol Filtering

The Ethernet Protocol filter blocks or forwards packets based upon the Ethernet protocols they support. Click the
Configure button, the Filtering tab, and the Ethernet Protocol sub-tab to enable or disable certain protocols in
the table. Entries can be selected from a drop-down box.
Follow these steps to configure the Ethernet Protocol Filter:

3. Select the interfaces that will implement the filter from the Ethernet Protocol Filtering drop-down menu.
Ethernet: Packets are examined at the Ethernet interface
Wireless-Slot A or Wireless-Slot B: Packets are examined at the Wireless A or B interfaces
All Interfaces: Packets are examined at both interfaces
Disabled: The filter is not used

4. Select the Filter Operation Type.
If set to Passthru, only the enabled Ethernet Protocols listed in the Filter Table pass through the
bridge.
If set to Block, the bridge blocks enabled Ethernet Protocols listed in the Filter Table.
5. Configure the Ethernet Protocol Filter Table. This table is pre-populated with existing Ethernet Protocol
Filters, however, you may enter additional filters by specifying the appropriate parameters.
To add an entry, click Add, and then specify the Protocol Number and a Protocol Name.
Protocol Number: Enter the protocol number. See http://www.iana.org/assignments/ethernetnumbers for a list of protocol numbers.
Protocol Name: Enter related information, typically the protocol name.
To edit or delete an entry, click Edit and change the information, or select Enable, Disable, or Delete
from the Status drop-down menu.
An entrys status must be enabled in order for the protocol to be subject to the filter.
An entrys status must be enabled in order for the protocol to be subject to the filter.
72
Add Entries to the Ethernet Protocol Filter Table

To add an entry to the table, click Add Table Entries, select the protocol name from the drop-down box and click
the Add button.
To edit or delete table entries, click Edit/Delete Table Entries, make your changes or deletions, and click OK.
Configure Static MAC Pair Filtering

The Static MAC Address filter optimizes the performance of a wireless (and wired) network. When this feature is
configured properly, the unit can block traffic between wired devices on the wired (Ethernet) interface and devices
on the wireless interface based upon MAC address.
Note:
The device on the wireless interface can be any device connected through the link, it can be directly
connected to the Ethernet interface of the peer unit, or it can be attached through multiple hops. The only
thing important is the MAC address in the packets arriving at the wireless interface.
The filter is an advanced feature that lets you limit the data traffic between two specific devices (or between
groups of devices based upon MAC addresses) through the wireless interface of the 5054. For example, if you
have a server on your network with which you do not want wireless clients to communicate, you can set up a
static MAC filter to block traffic between these devices. The Static MAC Filter Table performs bi-directional
filtering. However, note that this is an advanced filter and it may be easier to control wireless traffic through other
filter options, such as Protocol Filtering.
73
Click the Configure button, the Filtering tab, and the Static MAC sub-tab to access the Static MAC Address
filter.
Each MAC address or mask is comprised of 12 hexadecimal digits (0-9 and 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 unit looks
for when examining packets. The unit uses Boolean logic to perform an and operation between the MAC
address and the mask at the bit level. However, for most users, you do not need to think in terms of bits. It
should be sufficient to create a filter using only the hexadecimal digits 0 and F in the mask (where 0 is any value
and F is the value specified in the MAC address). A mask of 00:00:00:00:00:00 corresponds to all MAC
addresses, and a mask of FF:FF: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 unit examines 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 unit looks only for the specific MAC address (in this case, 00:20:A6:12:54:C3).
When creating a filter, you can configure the Wired parameters only, the Wireless parameters only, or both sets of
parameters. Which parameters to configure depends upon the traffic that you want to block.
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 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 and Wireless mask (leave the Wired MAC address and Wired mask set to
all zeros).
To block traffic between a specific wired MAC address and a specific wireless MAC address, configure all four
parameters.
74
Add Entries to the Static MAC Filter Table

To add the entries to Filter table, click the Add Table Entries button.
After entering the data, click the Add button. The entry is enabled automatically when saved.
To edit an entry, click Edit. To disable or remove an entry, click Edit and change the Status field from Enable to
Disable or Delete.
Field Descriptions
Wired MAC Address
Enter the MAC address of the device on the Ethernet network that you want to prevent from communicating
with a device on the wireless network.
Wired Mask
Enter the appropriate bit mask to specify the range of MAC addresses to which this filter is to apply. To
specify only the single MAC address you entered in the Wired MAC Address field, enter 00:00:00:00:00:00
(all zeroes).
Wireless MAC Address
Enter the MAC address of the wireless device that you want to prevent from communicating with a device on
the wired network.
Wireless Mask
Enter the appropriate bit mask to specify the range of MAC addresses to which this filter is to apply. To
specify only the single MAC address you entered in the Wireless MAC Address field, enter 00:00:00:00:00:00
(all zeroes).
Comment
Enter related information.
Status
The Status field can show Enable, Disable, or Delete.
75
Static MAC Filter Examples

Consider a network that contains a wired server and three wireless clients. The MAC address for each unit is as
follows:
Wired Server: 00:40:F4:1C:DB:6A
Wireless Client 1: 00:02:2D:51:94:E4
Wireless Client 2: 00:02:2D:51:32:12
Wireless Client 3: 00:20:A6:12:4E:38
Prevent two specific devices from communicating:
Configure the following settings to prevent the Wired Server and Wireless Client 1 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 Server and Wireless Client 1 is blocked. Wireless Clients 2 and 3 still can
communicate with the Wired Server.
Prevent Multiple Wireless Devices From Communicating With a Single Wired Device
Configure the following settings to prevent Wireless Clients 1 and 2 from communicating with the Wired Server:

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 Client 1 and Wireless Client
2 share the same prefix (00:02:2D), traffic between the Wired Server and Wireless Clients 1 and 2 is blocked.
Wireless Client 3 can still communicate with the Wired Server since it has a different prefix (00:20:A6).
Prevent All Wireless Devices From Communicating With a Single Wired Device
Configure the following settings to prevent all three Wireless Clients from communicating with Wired Server 1:

Wireless MAC Address: 00:00:00:00:00:00
Wireless Mask: 00:00:00:00:00:00
Result: The unit blocks all traffic between Wired Server 1 and all wireless clients.
Prevent A Wireless Device From Communicating With the Wired Network
Configure the following settings to prevent Wireless Client 3 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
Wireless MAC Address: 00:20:A6:12:4E:38
Wireless Mask: FF:FF:FF:FF:FF:FF
Result: The unit blocks all traffic between Wireless Client 3 and the Ethernet network.
76
Prevent Messages Destined for a Specific Multicast Group from Being Forwarded to the Wireless LAN
If there are devices on your Ethernet network that use multicast packets to communicate and these packets are
not required by your wireless clients, you can set up a Static MAC filter to preserve wireless bandwidth. For
example, if routers on your network use a specific multicast address (such as 01:00:5E:00:32:4B) to exchange
information, you can set up a filter to prevent these multicast packets from being forwarded to the wireless
network:
Wired MAC Address: 01:00:5E:00:32:4B

Wireless MAC Address: 00:00:00:00:00:00
Wireless Mask: 00:00:00:00:00:00
Result: The unit does not forward any packets that have a destination address of 01:00:5E:00:32:4B to the
wireless network.
Configure Storm Threshold Filtering

Click the Configure button, the Filtering tab, and the Storm Threshold sub-tab to use threshold limits to prevent
broadcast/multicast overload.
Storm Threshold is an advanced Bridge setup option that you can use to protect the network against data
overload by specifying:
A maximum number of frames per second as received from a single network device (identified by its MAC
address).
An absolute maximum number of messages per port.
The Storm Threshold parameters let you specify a set of thresholds for each port of the 5054, identifying
separate values for the number of broadcast messages per second and multicast messages per second.
When the number of frames for a port or identified station exceeds the maximum value per second, the 5054
ignores all subsequent messages issued by the particular network device, or ignores all messages of that type.
77
Field Descriptions
Per Address Threshold
Enter the maximum allowed number of packets per second.
Ethernet Threshold
Wireless Threshold
Configure Broadcast Protocol Filtering

Click the Configure button, the Filtering tab, and the Broadcast Protocol sub-tab to deny specific IP broadcast,
IPX broadcast, and multicast traffic.
Click the Edit Table Entries button to display an editable window such as the following. You can configure
whether this traffic must be blocked for Ethernet to wireless, wireless to Ethernet, or both.
78
Configure IP Access Table Filtering

Entries in this table show which wireless stations are allowed to use SNMP, HTTP, and telnet management
interfaces.
To add an entry, click the Add Table Entries button, specify the IP address and mask of the wireless stations to
which you want to grant access, and click Add. To edit or delete table entries, click the Edit/Delete Table
Entries button, make your changes, and click OK.
For example, 172.17.23.0/255.255.255.0 allows access from all wireless stations with an IP address in the
172.17.23.xxx range.
Ensure that the IP address of the management PC you use is within the first entry in the table, as this filter takes
effect immediately. Otherwise, you have locked yourself out.
When you do lock yourself out, you may try to give the PC the correct IP address; otherwise you must reset the
unit.
79
9) Configure Intra-Cell Blocking (Base Station only)

The Intra-Cell Blocking feature lets traffic be blocked between two SUs registered to the same Base Station.
There are two potential reasons to isolate traffic among wireless subscribers:
To provide better security to the subscribers by isolating the traffic from one subscriber to another in a public
space.
To block unwanted traffic between subscribers to prevent this traffic from using bandwidth.
You can form groups of SUs at the Base Station, which define the filtering criteria. All data to or from SUs
belonging to the same group are bridged. All other data from SUs that do not belong to a particular group are
automatically forwarded through the Ethernet interface of the Base Station. If an SU does not belong to any
group, the Base Station discards the data.
You 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 Base Station are forwarded to the Security Gateway MAC address
(configured in the Security Gateway tab).
When you change the device from Bridge to Routing mode, Intra-Cell Blocking stops working with or without a
reboot. When you change the device from Routing to Bridge mode, Intra-Cell Blocking starts working with or
without a reboot.
Enable Intra-Cell Blocking

The Group Table tab lets you enable the Intra-Cell Blocking feature and to configure Intra-Cell Blocking Groups.
Field Descriptions
Intra-Cell Blocking Status
Enables or disables the Intra-Cell Blocking feature.
Group Table
Entries in this table show the Intra-Cell Blocking filter groups that have been configured. When Intra-Cell
Blocking is enabled, the Base Station Unit discards all packets coming from one SU to another SU, if both
SUs do not belong to the same filter group.
80
Configure Intra-Cell Blocking Groups

Click the Add Table Entries button to add groups.
Enter the group name, and click Add. The group is assigned an Index and appears in the Group Table. Up to 16
groups can be configured per Base Station.
You can enable, disable or delete an existing filter group by using the Edit/Delete Table Entries button.
Assign MAC Addresses

After configuring the Intra-Cell Blocking Groups on the Group Table tab, use the MAC Table tab to assign
specific MAC addresses to an Intra-Cell Blocking Group.
81
Adding Entries
Click the Add Table Entries button.
Enter the MAC address of the SU. Select Enable from the drop-down menu for the Group Index
Click Add. The MAC address is assigned to the groups. Additions to the MAC Table take effect immediately after
clicking the Add button. You can enable, disable, delete, or reassign the groups for a MAC address by using
the Edit/Delete Table Entries button. A maximum of 250 MAC addresses can be added among all filter groups.
Block Traffic Between SUs

You can configure a Security Gateway to block traffic between SUs connected to different BSUs. Verify that IntraCell Blocking has been enabled on the Group Table tab before configuring the Security Gateway.
Security Gateway Status

Enables or disables packet forwarding to the external Security Gateway.
Security Gateway MAC Address
Lets you configure the MAC address of the external Security Gateway.
82
Intra-Cell Blocking Group Rules

The following rules apply to Intra-Cell Blocking Groups:
One 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.
Example of Intra-Cell Blocking Groups

Four Intra-Cell Blocking Groups have been configured on one BSU Unit. SUs 1 through 6 are registered to BSU
1. SUs 7 through 9 are registered to BSU 2.
Intra-Cell Blocking Group Example
Group 1
Group 2
Group 3
Group 4
SU 1
SU 2
SU 6
SU 8
SU 4
SU 3
SU 1
SU 9
SU 5
SU 8
SU 3
SU 2
In this example, SU 1 belongs to two groups, Group 1 and Group 3. Therefore, packets from SU 1 destined to SU
4, SU 5, SU 6, and SU 3 are not blocked. However, SU 9 belongs to group 4 only and packets from SU 9 are
blocked unless sent to SU 8 or SU 2.
Achieving Communication Between Two SUs

In a multipoint configuration, an SU can communicate with another SU through the BSU when in Bridge mode by
default. Use the intra-cell blocking feature if this is not desired. In a routing configuration, each of the SUs must
have a different subnet on their Ethernet port to distinguish traffic for each SU, and each subnet must be entered
into a routing rule in the BSU as well as into an upstream router. The wireless side of all SUs must share the
same subnet with the BSU wireless interface. These IP addresses must be used as next hop when creating the
routes for the SU subnets.
10) Configure VLAN Parameters

Virtual LAN (VLAN) implementation in the Tsunami MP.11 products:
Lets the BSU and SU be used in a VLAN-aware network.

Processes IEEE 802.1Q VLAN-tagged packets.
Network resources behind the BSU and SU can be assigned to logical groups.
VLAN Modes
Transparent Mode
Transparent mode applies to both the SU and the BSU. This mode is equivalent to NO VLAN support and is the
default mode. It is used when the devices behind the SU and BSU are both VLAN aware or unaware. The
SU/BSU transfers both tagged and untagged frames received on Ethernet or WORP interface. Both tagged and
untagged management frames can access the device.
Trunk Mode
Trunk mode VLAN applies to both the SU and the BSU. It is used when all devices behind the SU and BSU are
VLAN aware. The SU and BSU transfer only tagged frames received on Ethernet or WORP interface.
83
Access Mode
Access mode applies only to the SU. It is used when the devices behind the SU are VLAN unaware. Frames to
and from the Ethernet interface behind the SU map into only one VLAN segment.
Frames received on the Ethernet interface are tagged with the configured Access VLAN ID before forwarding
them to the WORP interface. Only management frames so tagged can access the device from the WORP
interface; however, untagged management frames can access the device from Ethernet Interface.
VLAN Forwarding
The VLAN Trunk mode provides a means to configure a list of VLAN IDs in a Trunk VLAN Table. The SU and
BSU only forward frames (between Ethernet and WORP interface) tagged with the VLAN IDs configured in the
Trunk VLAN Table. Up to 256 VLAN IDs can be configured for the BSU and up to 16 VLAN IDs can be
configured for the SU.
VLAN Relaying
The VLAN Trunk mode for BSU operation provides an option to enable and disable a VLAN relaying flag; when
enabled, the BSU shall relay frames between SUs on the same BSU having the same VLAN ID.
Management VLAN
The BSU and SU allow the configuration of a separate VLAN ID and priority for SNMP, ICMP, Telnet, and TFTP
management frames for device access.
The management VLAN ID and management VLAN priority apply in both Trunk and Access mode. The
management stations tag the management frames they send to the BSU or SU with the management VLAN ID
configured in the device. The BSU and SU tag all the management frames from the device with the configured
management VLAN and priority.
BSUs and SUs in Trunk mode let only management frames tagged with the configured management VLAN
ID access the device from both WORP and Ethernet interfaces.
SUs in Access mode let management frames tagged with the configured management VLAN ID access the
device from WORP interface; untagged management frames can access the device from Ethernet Interface.
BSU in Transparent Mode

When the BSU is in Transparent mode, all associated SUs must be in Transparent mode.
84
How the BSU and SUs function in Transparent mode is described in the following table.
BSU Function Transparent Mode
SU Function Transparent Mode
BSU forwards both tagged an untagged

frames received on the WORP interface or
on the Ethernet Interface.
SU forwards both tagged an untagged frames

received on either the WORP interface or on the
Ethernet Interface.
BSU lets both tagged and untagged

management frames access the device.
SU lets both tagged and untagged management

frames access the device.
BSU in Trunk Mode

When the BSU is in Trunk mode, the associated SUs must be in either Access mode or Trunk mode. When an
SU associates to a BSU that is in Trunk mode, it gets the VLAN mode from the BSU.
How the BSU and SUs function in Trunk mode is described in the following table.
BSU Function
SU Function
Trunk Mode
Access Mode
Trunk Mode
Up to 256 VLAN IDs can be

configured on a BSU
SUs discard all tagged frames received

from the Ethernet interface (unexpected).
Up to 16 VLAN IDs can be

configured on SUs.
The BSU discards all untagged

frames received from the
Ethernet interface or from any
of the associated SUs.
SUs allow untagged management frames

to access the device from the Ethernet
interface .
The BSU forwards only

VLAN-tagged frames received
from the Ethernet interface, or
any of the associated SUs that
are tagged with the configured
VLAN IDs, and discards all
other tagged frames.
SUs allow only management frames

tagged with the configured management
VLAN ID to access the device through the
BSU.
SUs discard all untagged

frames received from the
Ethernet interface or from
the BSU (unexpected).
SUs forward only VLANtagged frames received

from the Ethernet interface
or from the BSU that are
tagged with the configured
VLAN IDs; it discards all
other tagged frames.
SUs allow only

management frames
tagged with the configured
management VLAN ID to
access them.
SUs tag all management

frames generated by them
with the configured
management VLAN ID and
priority.
The BSU allows only

management frames tagged
with the configured
management VLAN ID to
access it.
The BSU tags all management

frames generated by the BSU
with the configured
management VLAN ID and
priority.
SUs tag all management frames generated

by the SU with the configured management
VLAN ID and priority.
SUs tag all untagged frames received from

the Ethernet interface with the configured
Access VLAN ID and forwards them to the
BSU.
SUs untag all tagged frames received from

the BSU that are tagged with the
configured Access VLAN ID and forwards
them to the Ethernet interface, and
discards all other tagged frames from the
BSU.
85
BSU in Trunk Mode
BSU VLAN Configuration

The HTTP Interface to configure SU VLAN parameters is shown in the following figure.
The BSU Trunk VLAN Table applies when the BSU is in Trunk mode. The VLAN ID values for the Trunk VLAN
Table range from 1 to 4095; the default value is -1. The maximum number of VLAN IDs that can be configured in
the Trunk VLAN Table for the BSU is 256. An SU in Trunk mode is assigned VLAN IDs from this table.
The following VLAN parameters must be configured for the BSU:
VLAN Mode
The BSU VLAN mode can be either Transparent mode or Trunk mode. By default, the BSU is in
Transparent mode.
Management VLAN ID
The Management VLAN ID applies when the BSU is in Trunk mode. The management VLAN ID has a
86
default value of -1 in Transparent mode and must be configured with a value in the range of 1 to 4095 to
change the BSU VLAN mode to Trunk mode.
The Management VLAN priority values range from 0 to 7 and the default priority is 0 (zero).
Relaying Flag
When this flag is enabled, the BSU relays frames between SUs on the same BSU.
Add BSU Table Entries

To add entries to the BSU table, click the Add Table Entries button on the BSU Table tab. Enter a VLAN ID and
select a Status, then click Add to add your entry to the table.
Edit or Delete BSU Table Entries

To edit or delete entries in the BSU Table, click the Edit/Delete Table Entries button on the BSU Table tab,
make your changes, then click OK for your changes to take effect.
87
Restrict Unit Management

Management access to the unit can be secured easily by making management stations or hosts and the unit itself
members of a common VLAN. Simply configure a non-zero management VLAN ID; management of the unit will
be restricted to members of the same VLAN.
CAUTION
If a non-zero management VLAN ID is configured, management access to the unit is

restricted to hosts that are members of the same VLAN. Ensure your management platform
or host is a member of the same VLAN before attempting to manage the unit.
1. Click the Configure button and the VLAN tab.

2. Set the Management ID to a value between 1 and 4095.
3. Click OK.
Provide Access to a Host in the Same VLAN

The VLAN feature lets hosts manage the unit. If the VLAN Management ID matches a VLAN Access ID, those
hosts who are members of that VLAN will have management access to the unit.
CAUTION
Once a VLAN Management ID is configured and is equivalent to one of the VLAN User IDs on the unit,
all members of that VLAN will have management access to the unit. Be careful to restrict VLAN
membership to those with legitimate access to the unit.
1. Click the Configure button and the VLAN tab.

2. Set the VLAN Management ID to the same value as the wireless client VLAN User ID.
3. Click OK.
SU VLAN Configuration
The HTTP Interface to configure SU VLAN parameters is shown in the following figure.
The Trunk VLAN table applies when the SU is in Trunk mode. The VLAN ID values for the Trunk VLAN Table
range from 1 to 4095; the default value is -1. A maximum of 16 VLAN IDs can be configured in the Trunk VLAN
Table for each SU. The VLAN IDs must be in the Trunk VLAN Table that corresponds to the BSU.
The following VLAN parameters must be configured for each SU associated to the BSU.
VLAN Mode
The SU VLAN mode can be either Transparent mode, Trunk mode, or Access mode.
By default, the BSU is in Transparent mode.
When the BSU is in Transparent mode, the SU must be in Transparent mode.

When the BSU is in Trunk mode the SU must be in either Access mode or Trunk mode.
88
When the BSU is changed to Trunk mode from Transparent mode, all the configured SUs are
changed to Trunk mode by default.
Access VLAN ID
The Access VLAN ID applies when the SU is in Access mode.
The Access VLAN ID values range from 1 to 4095; the default value is 1.
Access VLAN Priority
The Access VLAN Priority applies when the SU is in Access Mode. The Access VLAN priority values range
from 0 to 7; the default priority is 0. For voice frames, the priority field is set to the VoIP configured value (5
according to latest IETF draft, or 6 according to IEEE 802.1D) regardless of the priority value configured.
Management VLAN ID
The management VLAN ID applies when the SU is in Trunk mode or Access mode. The management
VLAN ID values range from 1 to 4095; the default value is 1.
The Management VLAN Priority applies when the SU is in Trunk mode or Access mode. The management
VLAN priority values range from 0 to 7; the default priority is 0.
Adding SU Table Entries

To add entries to the SU Table, click the Add Table Entries button. Enter the VLAN ID and select a Status, then
click Add to add and save the entry.
Editing SU Table Entries

To edit SU table entries, click the Edit/Delete Table Entries button; make your changes on the window
displayed, then click OK to save your changes.
89
Typical User VLAN Configurations

VLANs segment network traffic into groups, which lets you limit broadcast and multicast traffic. These groups
enable hosts from different VLANs to access different resources using the same network infrastructure. Hosts
using the same physical network are limited to those resources available to their workgroup.
The unit can segment users into a maximum of 16 different VLANs per unit, based upon a VLAN ID.
The primary scenarios for using VLAN workgroups are as follows:
VLAN disabled:
Your network does not use VLANs.
VLAN enabled:
1. Each VLAN workgroup uses a different VLAN ID Tag
2. A mixture of Tagged and Untagged workgroups
90
11) QoS (Quality of Service) Parameters

The Quality of Service (QoS) feature is based on 802.16 standard and defines the classes, service flows (SFCs),
and packet identification rules (PIRs) for specific types of traffic. QoS main priority is to guarantee a reliable and
adequate transmission quality for all traffic types under conditions of high congestion and bandwidth oversubscription (for a complete discussion on QoS see Quality of Service (QoS) on page 24).
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 class by defining PIRs; then you associate some of those PIRs to specific Service Flow classes (SFCs);
you assign priorities to each PIR within each SFC; and finally you define the QoS class by associating relevant
SFCs to each QoS class.
QoS PIR Configuration

Click the Configure button, the QoS tab and the QoS PIR Table sub-tab. The 17 predefined PIRs are shown.
To view/edit the parameters of each PIR click on its Details button. You may enable, disable or delete this PIR
entry by clicking on the Status drop-down box and then clicking OK.
91
To add entries to the PIR Table, click the Add Table Entries button. Enter the Rule Name and select Enable or
Disable from the Entry Status drop-down box, then click Add to add the entry. Once the new entry shows up on
the screen, click its Details button to view/edit its parameters.
92
QoS SFC Configuration

Click the Configure button, the QoS tab and the QoS SF Class sub-tab. The 7 predefined SFCs are shown.
To add entries to the SFC Table, click the Add Table Entries button.
Field Descriptions
SF Name
Enter the name of the SF class you want to add.
SF Schd Type
This field can be set to BE (Best Effort) or RtPS (Real-Time Polling Service).
SF Direction
This field can be set to Downlink (DL: traffic from BSU to SU) or Uplink (UL: traffic from SU to BSU).
93
MIR (Maximum Information Rate)

The maximum sustained data rate specified in units of 1 Kbps from 8 Kbps up to the maximum rate of 108000
Kbps per SU.
CIR (Committed Information Rate)
The minimum reserved traffic rate specified in units of 1 Kbps from 0 Kbps up to the maximum rate of 10000
Kbps per SU.
Latency
The maximum allowed latency specified in increments of 5 ms steps from a minimum of 5 ms up to a
maximum of 100 ms.
Jitter
The maximum tolerable jitter specified in increments of 5 ms steps from a minimum of 0 ms up to the
Maximum Latency (in ms).
Priority
The priority of this SFC from zero (0) to seven (7), 0 being the lowest, 7 being the highest.
Number of Frames per Burst
The Maximum number of data messages in a Multi-Frame burst from one (1) to four (4), which affects the
percentage of the maximum throughput of the system according to the table Error! Bookmark not defined..
SF Entry State
This field can be set to Enable, Disable, or Delete.
Click Add to add the entry. The new entry will show up on the screen taking up the next sequential index entry.
To make changes to the entries of the SFC Table, click the Edit/Delete Table Entries button.
Enter your changes and click OK. To delete an entry, click the Status drop-down box and select Delete, then
click OK.
94
QoS Class Configuration

Click the Configure button, the QoS tab and the QoS Class sub-tab. The 4 predefined QoS classes are shown.
To view/edit a QoS Class click on its Details button. You may enable, disable or delete this QoS Class entry by
clicking on the Status drop-down box and then clicking OK. You may also edit an existing SFC associated to this
QoS class, or add a new SFC.
95
To edit an existing SFC associated to this QoS Class click its Details button. You may enable, disable or delete
this SFC entry by clicking on the Status drop-down box and then clicking OK. You may also delete a PIR
associated to this SFC by clicking on the Status drop-down box and then clicking OK, or add a new PIR to this
SFC.
To add more PIRs to this SFC click the Add Table Entries button.
Field Descriptions
PIR Table Reference Index
Select one of the possible PIRs that have been previously configured from the drop-down box.
PIR Priority
This priority per rule defines the order of execution of PIRs during packet identification process. The PIR
priority is a number in the range 0-63, with priority 63 being executed first, and priority 0 being executed last.
96
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
This field is always set to Enable.
You may delete any PIR entry by clicking on the Status drop-down box.
Back to the QoS Class screen on page 95, to add a new SFC and associate it to this QoS Class click the Add
Table Entries button.
Field Descriptions
SF Table Reference Index
Select one of the possible SFCs that have been previously configured from the drop-down box to associate to
this QoS Class.
Select one of the possible PIRs that have been previously configured from the drop-down box to associate to
this SFC.
PIR Priority
class.
Entry Status
97
From this screen you may also edit an existing SFC by clicking on its Details button. This will take you to the
same QoS Class SF Class Entry Details screen on page 96.
Finally, to add a new QoS Class click the Add Table Entries button on the screen on page 95.
Field Descriptions
Class Name
Enter the name of the QoS class you want to add.
SF Table Reference Index
Select one of the possible SFCs that have been previously configured from the drop-down box to associate to
this QoS Class.
Select one of the possible PIRs that have been previously configured from the drop-down box to associate to
this SFC.
PIR Priority
class.
Entry Status
From this screen you may also edit an existing QoS Class by clicking on its Details button. This will take you to
the same QoS Class Entry View/Edit screen on page 95.
98
QoS SU Configuration
Click the Configure button, the QoS tab and the QoS SU sub-tab.
This screen defines which QoS Classes will be associated to which given SUs by using their MAC addresses.
To add entries to the QoS SU Table, click the Add Table Entries button.
Field Descriptions
SU MAC Address
The MAC Address of the SU you want to associate to a specific QoS Class.
SU QOSC Index
Select one of the possible QoS Classes that have been previously configured from the drop-down box to
associate to this SU.
SU QOSC State
This field can be set to Enable, Disable, or Delete.
99
To make changes to QoS SU Table, click the Edit/Delete Table Entries button.
Enter your changes and click OK. To delete an entry, click the Status drop-down box and select Delete, then
click OK.
12) SU Access to the Public Network (NAT)

The NAT (Network Address Translation) feature lets hosts on the Ethernet side of the SU transparently access
the public network through the BSU. All hosts in the private network can have simultaneous access to the public
network.
Note: The NAT tab is available for SUs in Routing mode only. The SU supports NAPT (Network Address Port
Translation) where all private IP addresses are mapped to a single public IP address, and does not
support Basic NAT (where private IP addresses are mapped to a pool of public IP addresses).
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.
In dynamic mapping, the SU 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.
Static mapping is used to provide inbound access. The SU maps a private IP address and its local port to
a fixed public port of the global IP address. 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. Up to 1000
ports (500 UDP and 500 TCP) are supported.
100
Field Descriptions
NAT Status
Enables or disables the NAT feature. NAT can be enabled only for SUs in Routing mode.
The default is disabled.
Note: Changes to NAT parameters including the NAT Static Port Mapping Table require a reboot to take effect.
NAT Static Bind Status
Enables or disables the NAT Static Bind status (static mapping) to allow public hosts to access hosts in a
private network. The default is disabled.
Public IP Address
The NAT Public IP address is the wireless interface IP address.
NAT Feature Interactions

When NAT is enabled, the DHCP Relay Agent feature is not supported (DHCP Relay Agent must be disabled
before NAT is enabled) and RIP updates are not sent or received.
DHCP Server Interaction

You can configure a DHCP server to allocate IP addresses to hosts on the Ethernet side of the SU/BSU (see
DHCP Server).
NAT Static Port Mapping Table

Adding entries to the NAT Static Mapping Table lets the configured hosts in a private address realm on the
Ethernet side of the SU access hosts in the public network using Network Address Port Translation (NAPT). Up to
1000 entries can be configured (500 UDP ports and 500 TCP ports).
To add an entry:
1.
2.
3.
4.
Click the Add Table Entries button.

Enter the Local IP Address of the host on the Ethernet side of the SU.
Select the Port Type: TCP, UDP, or Both.
Enter the Start Port and End Port; click Add.
101
Supported Session Protocols

The NAT feature supports the following session protocols for both inbound and outbound access with the required
support, applications, and limitations given in the following table.
Certain Internet 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.
These VPN protocols are supported with their corresponding ALGs: IPsec, PPTP, L2TP.
Protocol
Support
Applications
ICMP
ICMP ALG
Ping
FTP
FTP ALG
File transfer
H.323
H.323 ALG
Multimedia conferencing
HTTP
Port mapping for inbound

connection.
Web browser
TFTP

connection.
File transfer
Telnet

connection.
Remote login
CUSeeMe
Port mapping for inbound and

outbound connection.
Video conferencing
IMAP

connection.
Mail
PNM

connection.
Streaming media with Real

Player
POP3

connection.
E-mail
SMTP

connection.
E-mail
RTSP

connection.
Streaming audio/video with

Quick Time and Real Player
ICQ

connection.
Chat and file transfer
Limitations
One user is allowed for video

conferencing
Mails with IP addresses of MTAs or

using IP addresses in place of FQDN
are not supported (requires SMTP
ALG).
Each host using ICQ needs to be

mapped for different ports.
102

Protocol
Support
Applications
Limitations
IRC

connection.
Chat and file transfer
Each host using IRC needs to be

mapped for different ports.
MSN
Messenger

Conference and Share files

with Net meeting
Only one user is allowed for net

meeting.
Net2Phone

Voice communication
IP Multicast
Pass Through
Multicasting
Stream works

connection.
Streaming video
Quake

connection.
Games
When a Quake server is configured

within the private network behind a SU,
the SU cannot provide information
about that server on the public
network.
Also, certain Quake servers do not let
multiple users log in using the same IP
address, in which case only one Quake
user is allowed.
MONITOR SETTINGS AND PERFORMANCE

Use this section of the interface to obtain detailed information about the settings and performance of the 5054.
Note:
The Radius tab is available on BSUs only.
1) Monitor Wireless Settings

General Performance
Click the Monitor button and the General tab to monitor the general performance of the wireless interface.
103
WORP Interface Performance

Click the Monitor button, the Wireless tab, and the WORP tab to monitor the performance of the WORP Base or
WORP SU interfaces.
The Registration Last Reason field indicates either a successful registration (a value of 1) or it indicates the
reason why the last registration failed.
Possible values for the Registration Last Reason field are as follows:
1 = None (successful registration)
2 = Maximum number of SUs reached
3 = Authentication failure
4 = Roaming
5 = No response from SU within the Registration Timeout Period
6 = Low Signal Quality
104
2) View Number of ICMP Messages

Click the Monitor button and the ICMP tab to view the number of ICMP messages send and received by the
5054. It includes ping, route, and host unreachable messages.
3) View Per Station Statistics

Click the Monitor button and the Per Station tab to view Station Statistics. On the SU, the Per Station page
shows statistics of the BSU to which the SU is registered. On the BSU, it shows statistics of all the SUs
connected to the BSU.
The pages statistics refresh every 4 seconds.
4) View Features Supported

Click the Monitor button and the Features tab to view the following information:
105
Note:
A BSU shows how many WORP SUs it can support; the SU shows how many Ethernet hosts they
support on their Ethernet port as the Max Users on Satellite parameter.
5) Test Link Quality

Click the Monitor button and the Link Test tab to find out which wireless stations are in range and to check their
link quality.
Note: Link Test requires Internet Explorer version 6.0 or later. Earlier versions do not support Link Test.
Link Test for the MP.11a reports a single Receive Signal Strength Indicator (RSSI) value; the higher the number,
the better the signal.
Explore from a BSU displays all its registered SUs.

Explore from an SU or RSU displays only the BSU with which it is registered.
All stations displayed after Explore come up Disabled. Select a station by changing Disabled to Start and
click the Link Test button. You can change multiple stations to Start, but only the last station in the list is
displayed as the remote partner when you click the Link Test button. See the following figure:
The Link Test provides the following information.
Link Test stops when you close the Link Test page.
106
6) View Interface Performance Details

Click the Monitor button and the Interfaces tab to view detailed information about the IP-layer performance of the
5054 interfaces. There are two sub-tabs: Wireless and Ethernet.
The following figure shows the Wireless interface; the same information is provided for the Ethernet interface on
the Ethernet sub-tab.
7) View IP and MAC Address Mapping

Click the Monitor button and the IP ARP Table tab to view the mapping of the IP and MAC addresses of all
radios registered at the 5054. This information is based upon the Address Resolution Protocol (ARP).
107
8) View Active IP Routes

Click the Monitor button and the IP Routes tab to view all active IP routes of the 5054. These can be either
static or dynamic (obtained through RIP). This tab is available only in Routing mode, and you can add routes
only when in Routing mode.
9) View MAC Addresses Detected

Click the Monitor button and the Learn Table tab to view all MAC addresses the 5054 has detected on an
interface. The Learn Table displays information relating to network bridging. It reports the MAC address for each
node that the device has learned is on the network and the interface on which the node was detected. There can
be up to 10,000 entries in the Learn Table. This tab is only available in Bridge mode.
10) View RIP Data

Click the Monitor button and the RIP tab to view Routing Internet Protocol data for the Ethernet and Wireless
interfaces.
108
11) View Radius Traffic Information

Click the Monitor button and the Radius tab to view information about the traffic exchanged with a RADIUS
server.
109
ISSUE COMMANDS
This section describes the commands that you can perform with the Web Interface. The following tabs are in the
Commands section: Download, Upload, Downgrade, Reboot, Reset, and Help Link.
1) Download Files to the Unit

Click the Commands button and the Download tab to download image, configuration, and license files to the
unit.
Server IP address
Enter the TFTP Server IP address. (Double-click the TFTP server icon on your desktop and locate the IP
address assigned to the TFTP server.)
File Name
Enter the name of the file to be downloaded.
File Type
Config, image, BspBl, or license.
File Operation
Download or Download and Reboot.
110
2) Upload a Configuration File

Click the Commands button and the Upload tab to upload a configuration file from the 5054. Enter Server IP
Address, File Name, select a Filetype, and click OK.
Filetype can be configured as Eventlog, or Config.
3) Reboot the Device

Click the Commands button and the Reboot tab to restart the embedded software of the 5054. Configuration
changes are saved and the unit is reset.
CAUTION: Rebooting the unit causes all users currently connected to lose their connection to the
network until the 5054 has completed the restart process and resumed operation.
4) Reset the Device

Click the Commands button and the Reset tab to restore the configuration of the 5054 to the factory default
values.
You can also reset the 5054 from the RESET button located on the side of the unit. Because this resets the
5054s current IP address, a new IP address must be assigned.
CAUTION: Resetting the 5054 to its factory default configuration permanently overwrites all changes
made to the unit. The 5054 reboots automatically after this command has been issued.
111
5) Set the Help Link Location

Click the Commands button and the Help Link tab to set the location of the help files of the Web Interface. Upon
installation, the help files are installed in the C:\Program Files\Tsunami\MP.11\Help\ folder.
If you want to place these files on a shared drive, copy the Help folder to the new location and specify the new
path in the Help Link box.
6) Downgrade to a Previous Release

Click the Commands button and the Downgrade tab to downgrade to a previous release. Downgrade currently
is supported only to release 2.0.1 and later. Once you enter this command, the unit is downgraded to the
specified release and is automatically rebooted. The filename specified and the filename of the image selected
for downgrade must be the same version. The unit will download the file, re-format the configuration to match the
version, and reboot to put the image into effect.
112
113
Chapter 6. Procedures
This chapter contains a set of procedures, as described in the following table:
Procedure
Description
TFTP Server Setup
Prepares the TFTP server for transferring files to and from the 5054. This
procedure is used by the other procedures that transfer files.
Image File Download
Upgrades the embedded software.
Configuration Backup
Saves the configuration of the 5054.
Configuration Restore
Restores a previous configuration through configuration file download.
Soft Reset to Factory

Default
Resets the 5054 to the factory default settings through the Web or Command
Line Interface.
Hard Reset to Factory

Default
In some cases, it may be necessary to revert to the factory default settings (for
example, if you cannot access the 5054 or you lost the password for the Web
Interface.
Force Reload
Completely resets the 5054 and erases the embedded software. Use this
procedure only as a last resort if the 5054 does not boot and the Hard Reset to
Factory Default procedure did not help. If you perform a Forced Reload, you
must download a new image file as described in Image File Download with the
Boot Loader.
Image File Download

with the Boot Loader
If the 5054 does not contain embedded software, or the embedded software is
corrupt, you can use this procedure to download a new image file.
TFTP SERVER SETUP

A Trivial File Transfer Protocol (TFTP) server lets you transfer files across a network. You can upload files from
the radio for backup or copying, and you can download the files for configuration and Image upgrades. The
SolarWinds TFTP server software is located on the 5054 product installation CD, or can be downloaded from
http://support.proxim.com . You can also download the latest TFTP software from Solarwinds Web.
Note:
If a TFTP server is not available in the network, you can perform similar file transfer operations using the
HTTP interface.
To download or upload a file, you must connect to the computer with the TFTP server through the 5054s Ethernet
port. This can be any computer in the network or a computer connected to the 5054 with a cross-over Ethernet
cable. For information about installing the TFTP server, see Installing Documentation and Software on page
15.
Ensure that the upload or download directory is correctly set, the required file is present in the directory, and the
TFTP server is running. The TFTP server must be running only during file upload and download. You can
check the connectivity between the 5054 and the TFTP server by pinging the 5054 from the computer that hosts
the TFTP server. The ping program should show replies from the 5054.
114
WEB INTERFACE IMAGE FILE DOWNLOAD

In some cases, it may be necessary to upgrade the embedded software of the 5054 by downloading an image
file. To download an image file through the Web Interface:
1. Set up the TFTP server as described in TFTP Server Setup on page 114.
2. Access the 5054 as described in Web Interface Overview on page 19.
3. Click the Commands button and the Download tab.
4. Fill in the following details:
Server IP Address <IP address TFTP server>
File Name <image file name>
File Type Image
File Operation Download
5. Click OK to start the file transfer.

The 5054 downloads the image file. The TFTP server program should show download activity after a few
seconds. When the download is complete, the 5054 is ready to start the embedded software upon reboot.
CONFIGURATION BACKUP
You can back up the 5054 configuration by uploading the configuration file. You can use this file to restore the
configuration or to configure another 5054 (see Configuration Restore on page 116).
To upload a configuration file through the Web Interface:
3. Click the Commands button and the Upload tab.
File Name <configuration file name>
File Type Config
File Operation Upload

The 5054 uploads the configuration file. The TFTP server program should show upload activity after a few
seconds. When the upload is complete, the configuration is backed up.
115
CONFIGURATION RESTORE
You can restore the configuration of the 5054 by downloading a configuration file. The configuration file contains
the configuration information of an 5054.
To download a configuration file through the Web Interface:
3. Click the Commands button and the Download tab.
File Name <configuration file name>
File Type Config
File Operation Download
The 5054 downloads the configuration file. The TFTP server program should show download activity after a few
seconds. When the download is complete and the system rebooted, the configuration is restored.
SOFT RESET TO FACTORY DEFAULT

If necessary, you can reset the 5054 to the factory default settings. Resetting to default settings means that you
must configure the 5054 anew.
To reset to factory default settings using the Web Interface:
1. Click the Commands button and the Reset tab.
2. Click the Reset to Factory Default button.
The device configuration parameter values are reset to their factory default values.
If you do not have access to the 5054, you can use the procedure described in Hard Reset to Factory Default on
page 117 as an alternative.
116
HARD RESET TO FACTORY DEFAULT

If you cannot access the unit or you have lost its password, you can reset the 5054 to the factory default settings.
Resetting to default settings means you must configure the 5054 anew.
To reset to factory default settings, press and hold the RELOAD button on the 5054 unit for about 10 seconds.
The 5054 reboots and restores the factory default settings.
To access the 5054 see Chapter 3. Management Overview on page 17.
FORCED RELOAD
With Forced Reload, you reset the 5054 to the factory default settings and erase the embedded software. Use this
procedure only as last resort if the 5054 does not boot and the Reset to Factory Defaults procedure did not help.
If you perform a Forced Reload, you must download a new image file with the Boot Loader (see Image File
Download with the Boot Loader below).
Caution! The following procedure erases the embedded software of the 5054. This software image
must be reloaded through an Ethernet connection with a TFTP server. The image filename to
be downloaded can be configured with either ScanTool through the Ethernet interface or with
the Boot Loader CLI through the serial port to make the 5054 functional again.
To do a forced reload:
1. Press the RESET button on the 5054 unit; the 5054 resets and the LEDs flash.
2. Immediately press and hold the RELOAD button on the 5054 unit for about 20 seconds. Now image and
configuration are deleted from the unit.
3. Follow the procedure Image File Download with the Boot Loader to download an image file.
117
IMAGE FILE DOWNLOAD WITH THE BOOTLOADER

The following procedures download an image file to the 5054 after the embedded software has been erased with
Forced Reload or when the embedded software cannot be started by the Boot Loader.
A new image file can be downloaded to the 5054 with ScanTool or the Command Line Interface through the 5054
serial port. In both cases, the file is transferred through Ethernet with TFTP. Because the CLI serial port option
requires a serial RS-232C cable, Proxim recommends the ScanTool option.
Download with ScanTool

To download an image file with the ScanTool:
5. Run ScanTool on a computer that is connected to the same LAN subnet as the unit. ScanTool scans the
subnet for units and displays the found units in the main window. If in Forced Reload, ScanTool does not find
the device until the unit bootloader times out from its default operation to download an image. Click Rescan
to re-scan the subnet and update the display until the unit shows up in Bootloader mode..
6. Select the unit to which you want to download an image file and click Change.
7. Ensure that IP Address Type Static is selected and fill in the following details:
Password
IP Address and Subnet Mask of the unit.
TFTP Server IP Address and, if necessary, the Gateway IP Address of the TFTP server.
Image File Name of the file with the new image.

The unit downloads the image file. The TFTP server program should show download activity after a few
seconds. When the download is complete, the LED pattern should return to reboot state. the unit is ready to
start the embedded software.
After a Forced Reload procedure, the 5054 returns to factory default settings and must be reconfigured.
ScanTool can be used to set the system name and IP address.
To access the 5054 see Chapter 3. Management Overview on page 17.
118
Download with CLI

To use the CLI through the serial port of the 5054 you need a serial RS-232C cable with a male and a female
DB9 connector, and an ASCII terminal program such as HyperTerminal. Proxim recommends you switch off the
5054 and the computer before connecting or disconnecting the serial RS-232C cable.
To download an image file:
2. Start the terminal program (such as HyperTerminal), set the following connection properties, and then
connect:
COM port
Bits per second
Data bits
Stop bits
Flow control
Parity
(for example COM1 or COM2, to which the MP.11 serial port is connected)
9600
8
1
None
None
3. Press the RESET button on the 5054 unit; the terminal program displays Power On Self Test (POST)
messages.
4. When the Sending Traps to SNMP manager periodically message is displayed after about 30
seconds, press the ENTER key.
5. The command prompt is displayed; enter the following commands:
set ipaddr <IP address MP.11>
set ipsubmask <subnet mask>
set ipaddrtype static
set tftpipaddr <IP address TFTP server>
set tftpfilename <image file name>
set ipgw <gateway IP address>
reboot
For example:
set ipaddr 10.0.0.12
set ipsubmask 255.255.255.0
set ipaddrtype static
set tftpipaddr 10.0.0.20
set tftpfilename image.bin
set ipgw 10.0.0.30
reboot
The 5054 reboots and downloads the image file. The TFTP server program should show download activity after a
few seconds. When the download is complete, the 5054 is ready for configuration.
To access the 5054 see Chapter 3. Management Overview on page 17. Note that the IP configuration in
normal operation differs from the IP configuration of the Boot Loader.
119
Chapter 7. Troubleshooting
This chapter helps you to isolate and solve problems with your 5054. In the event this chapter does not provide a
solution, or the solution does not solve your problem, check our support website at http://support.proxim.com/
Before you start troubleshooting, it is important that you have checked the details in the product documentation.
For details about RADIUS, TFTP, terminal and telnet programs, and Web browsers, refer to their appropriate
documentation.
In some cases, rebooting the 5054 clears the problem. If nothing else helps, consider a Soft Reset to Factory
Defaults (on page 30) or a Forced Reload (on page 117). The Forced Reload option requires you to download
a new image file to the 5054.
5054 CONNECTIVITY ISSUES

The issues described in this section relate to the connections of the 5054.
5054 Does Not Boot

The 5054 shows no activity (the power LED is off).
1.
2.
3.
4.
Ensure that the power supply is properly working and correctly connected.
Ensure that all cables are correctly connected.
Check the power source.
If you are using an Active Ethernet splitter, ensure that the voltage is correct.
Serial Link Does Not Work

The 5054 cannot be reached through the serial port.
1. Check the cable connection between the 5054 and the computer.
2. Ensure that the correct COM port is used.
3. Start the terminal program; set the following connection properties and then connect.
COM port
Bits per second
Data bits
Stop bits
Flow control
Parity
Line ends
For example, COM1 or COM2, to which the MP.11 serial port is connected
9600
0
1
None
None
Carriage return with line feed
4. Ensure that the 5054 and the computer use the same serial port configuration parameters.
5. Press the RESET button on the 5054 unit. The terminal program displays Power On Self Tests (POST)
messages and displays the following after approximately 90 seconds:
Please enter password:
HyperTerminal Connection Problems

The serial connection properties can be found in HyperTerminal as follows:
1. Start HyperTerminal and select Properties from the File menu.
2. Select Direct to Com 1 in the Connect using: drop-down list (depending upon the COM port you use); then
click Configure. A window such as the following is displayed:
120
3. Make the necessary changes and click OK.

4. Click the Settings tab and then ASCII Setup. A window similar to the following is displayed:
5. Ensure that Send line ends with line feeds is selected and click OK twice. HyperTerminal is now correctly
configured.
Ethernet Link does not work

First check the Ethernet LED;
GREEN
BLINKING GREEN
Power is on, the radio is up, and the Ethernet link is also up..
Power is on, the radio is coming up and the Ethernet is down.
Verify pass-through versus cross-over cable.
Cannot use the Web Interface:

1.
Open a command prompt window and enter ping <ip address MP.11> (for example ping 10.0.0.1).
If the 5054 does not respond, make sure that you have the correct IP address.
If the 5054 responds, the Ethernet connection is working properly, continue with this procedure.
2.
Ensure that you are using one of the following Web browsers:
Microsoft Internet Explorer version 5.0 or later (Version 6.0 or later recommended)
Netscape version 6.0 or later.
121
3. Ensure that you are not using a proxy server for the connection with your Web browser.
4. Ensure that you have not exceeded the maximum number of Web Interface or CLI sessions.
5. Double-check the physical network connections. Use a well-known unit to ensure the network connection is
properly functioning.
6. Perform network infrastructure troubleshooting (check switches, routers, and so on).
COMMUNICATION ISSUES
Two Units Are Unable to Communicate Wirelessly
If a wireless link is possible after testing two units within close distance of each other, then there are two possible
reasons why wireless connectivity is not possible while the MP.11 units are at their desired locations:
There may be a problem in the RF path, for example, a bad connector attachment (this is the most common
problem in installations) or a bad cable (water ingress).
Note:
The cables can be swapped with known good ones as a temporary solution to verify cable quality.
Another reason may be related to an interference problem caused by a high signal level from another radio. This
can be checked by changing the frequency and then verifying whether another channel works better or by
changing the polarization as a way of avoiding the interfering signal. To know in advance how much interference
is present in a given environment, a Spectrum Analyzer can be attached to a (temporary) antenna for measuring
the signal levels on all available Channels.
Note: The antennas are usually not the problem, unless mounted upside down causing the drain hole to be
quickly filled with radome.
If a wireless link is not possible after testing two units within close distance of each other, then the problem is
either hardware or configuration related, such as a wrong Network name, Encryption key, Network Secret or Base
Station Name. To eliminate these issues from being a factor, resetting the both units to factory defaults is the
recommended solution.
If a wireless link is not possible after resetting the units and verifying that one unit is a BSU with WORP Base
interface configured and the other is a Satellite, then the problem is not configuration related and the only
remaining reason is a possible hw problem. Acquiring a third MP.11 and then testing it amongst the existing units
will help pinpoint the broken unit.
SETUP AND CONFIGURATION ISSUES

The following issues relate to setup and configuration problems.
Lost the 5054 Password

If you lost your password, you must reset the 5054 to the default settings. See Hard Reset to Factory Default on
page 117. The default password is public.
If you record your password, keep it in a safe place.
122
The 5054 Responds Slowly

If the 5054 takes a long time to become available, it could mean that:
No DHCP server is available.
The IP address of the 5054 is already in use.

Verify that the IP address is assigned only to the 5054. Do this by switching off the 5054 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 5054 uses a static IP address, switching to DHCP mode could remedy this problem. Also see Setting the
IP Address on page 18.
There is too much network traffic.
Web Interface Does Not Work

If you cannot connect to the 5054 Web server through the network:
1. Connect a computer to the serial port of the 5054 and check the HTTP status. The HTTP status can restrict
HTTP access at different interfaces. For more information, see Serial Port in the Tsunami MP.11
Reference Manual.
2. Open a command prompt window and enter:
ping <ip address MP.11> (for example ping 10.0.0.1)
If the 5054 does not respond, ensure that you have the correct IP address. If the 5054 responds, the
Ethernet connection is working properly, continue with this procedure.
3. Ensure that you are using one of the following Web browsers:
Microsoft Internet Explorer version 5.0 or later (Version 6.0 or later recommended)
Netscape version 6.0 or later
4. Ensure that you are not using a proxy server for the connection with your Web browser.
5. Ensure that you have not exceeded the maximum number of Web Interface sessions.
Command Line Interface Does Not Work

If you cannot connect to the 5054 through the network:
1. Connect a computer to the serial port of the 5054 and check the SNMP table. The SNMP table can restrict
telnet or HTTP access. For more information, see Serial Port in the Tsunami MP.11 Reference Manual.
2. Open a command prompt window and enter: ping <ip address MP.11>
(for example ping 10.0.0.1).
If the 5054 does not respond, ensure that you have the correct IP address.
If the 5054 responds, the Ethernet connection is working properly; continue with this procedure.
3. Ensure that you have not exceeded the maximum number of CLI sessions.
123
TFTP Server Does Not Work

With TFTP, you can transfer files to and from the 5054. Also see TFTP Server Setup on page 114. If a TFTP
server is not properly configured and running, you cannot upload and download files. The TFTP server:
Can be situated either local or remote

Must have a valid IP address
Must be set for send and receive without time-out
Must be running only during file upload and download
If the TFTP server does not upload or download files, it could mean:
The TFTP server is not 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
Online Help Is Not Available

Online help is not available
1. Make sure that the Help files are installed on your computer or server. Also see Installing Documentation
and Software on page 15.
2. Verify whether the path of the help files in the Web Interface refers to the correct directory. See Help Link
on page 112.
Changes Do Not Take Effect

Changes made in the Web Interface do not take effect:
1. Restart your Web browser.
2. Log into the radio unit again and make changes.
3. Reboot the radio unit when prompted to do so.
Wait until the reboot is completed before accessing the 5054 again.
124
VLAN OPERATION ISSUES

The correct VLAN configuration can be verified by pinging wired hosts from both sides of the device and the
network switch. Traffic can be sniffed on the wired (Ethernet) network. Packets generated by hosts and viewed
on one of the backbones should contain IEEE 802.1Q compliant VLAN headers when in Transparent mode. The
VLAN ID in the headers should correspond to one of the VLAN Management IDs configured for the unit in Trunk
mode.
The correct VLAN assignment can be verified by pinging:
The unit to ensure connectivity

The switch to ensure VLAN properties
Hosts past the switch to confirm the switch is functional
Ultimately, traffic can be sniffed on the Ethernet interface using third-party packages. Most problems can be
avoided by ensuring that 802.1Q compliant VLAN tags containing the proper VLAN ID have been inserted in the
bridged frames. The VLAN ID in the header should correspond to the assigned VLAN.
What if network traffic is being directed to a nonexistent host?
All sessions are disconnected, traffic is lost, and a manual override is necessary.
Workaround: You can configure the switch to mimic the nonexistent host.
TROUBLESHOOTING LINK PROBLEMS

While wireless networking emerges more and more, the number of wireless connections to networks grows every
day. The Tsunami MP.11 5054 is one of the successful product families used by customers today who enjoy the
day after day high-speed, cost-effective connections. To successfully use the connections, technicians must be
able to troubleshoot the system effectively. This section gives hints on how a 5054 network could be analyzed in
the case of no link, a situation in which the customer thinks that the link is down because there is no traffic being
passed.
The four general reasons that a wireless link may not work are related to:
Hardware
Configuration
Path issues (such as distance, cable loss, obstacles)
Environment (anything that is outside the equipment and not part of the path itself)
You have tested the equipment in the office and have verified that the hardware and configurations are sound.
The path calculation has been reviewed, and the path has been double-checked for obstacles and canceling
reflections. Still, the user reports that the link does not work.
Most likely, the problem reported is caused by the environment or by improper tests to verify the connection. This
article assumes that the test method, cabling, antennas, and antenna alignment have been checked. Always do
this before checking the environment.
General Check
Two general checks are recommended before taking any action:
Check whether the software version at both sides is the most current
Check for any reported alarm messages in the Event Log
125
Statistics Check
Interference and other negative environment factors always have an impact on the number of correctly received
frames. The Tsunami MP.11 models give detailed information about transmission errors in the Web interface,
under Monitor.
The windows that are important for validating the health of the link are
Monitor / Wireless / General (Lowest level of the wireless network)
Check FCS errors: Rising FCS errors indicate interference or low fade margin. So does Failed count. If
only one of those is high, this indicates that a source of interference is significant near one end of the link/
Monitor / Interfaces / Wireless (One level higher than Wireless / General)
The information is given after the wireless Ethernet frame is converted into a normal Ethernet frame. The
parameters shown are part of the so-called MIB-II.
Both operational and admin status should be up. An admin status of down indicates that the interface is
configured to be down.
In Discards and Out Discards indicate overload of the buffers, likely caused by network traffic, which is too
heavy.
In Errors and Out Errors should never happen; however, it might happen if a frames FCS was correct while
the content was still invalid.
Monitor / Wireless / WORP (Statistics on WORP)
WORP runs on top of normal Ethernet, which means that the WORP frame is in fact the data field of the
Ethernet frame. Send Failure or Send Retries must be low in comparison to Send Success. Low is about
1%. The same applies for Receive Success versus Receive Retries and Receive Failures. Note that the
Receive Failures and Retries can be inaccurate. A frame from the remote site might have been transmitted
without even being received; therefore, the count of that frame might not have been added to the statistics
and the receiver simply could not know that there was a frame.
Remote Partners indicates how many SUs are connected (in case of a BSU) or whether a Base is connected
(in case of a Subscriber).
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.
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.
126
Monitor / Link Test (Information used by Administrators for on-the-spot checking)

Check the received signal level (RSL) and noise level. Compare the RSL with the values from path analysis.
If the figures differ significantly from the values recorded at the Per Station window, check for environment
conditions that change over time.
Analyzing the Spectrum

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 degrees, one can check from
which direction the interference is coming. 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.
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:
Changing the channel to a frequency away from the interference is the first step in avoiding
interference. For countries that require DFS, it might be not possible to manually select a
different frequency.
Each antenna has a polarization; try to change to a polarization different from the interferer.
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.
Lowering the antennas can help avoid seeing interference from far away.
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.
Conclusion
A spectrum analyzer can be a great help to identify whether interference might be causing link problems on
Tsunami MP.11 systems.
Before checking for interference, the link should be verified by testing in an isolated environment, to make sure
that hardware works and your configurations are correct. The path analysis, cabling and antennas should be
checked as well.
Statistics in the web interface under Monitor tell if there is a link, if the link is healthy, and a continuous test can be
done using the Link Test
127
STRANGE BEHAVIOR AFTER UPGRADE

If, after upgrading to version 2.x, the LEDs on your unit display the following pattern (see the following figure for a
visual), it is possible that the required License Key is missing.
Power LED is blinking Red

Ethernet Link is a solid Amber
Wireless Link is a solid Amber
Wireless Network Activity is Grey or off
In this current state, your unit may not be operational, so a firmware reload will be required. Run the Forced
Reload procedure and then re-load the previous version of the Tsunami MP.11 5054 firmware.
Once operability to the Tsunami MP.11 has been restored, you can verify whether the License Key is really
missing.
Using Telnet or a serial cable, login and enter show files. If the file named LIC1.cfg is missing, the License Key
has somehow been deleted. To obtain a License Key, contact Technical Support and provide the following
information:
Product type: [MP.11a BSU] or [MP.11 RSU]
Serial number: ##CC######## (# = Number, C = Character)
Ethernet MAC: [0020a6-000001]
Wireless MAC: [00022d-000002]
Once you have received and uploaded the new License Key, re-run the upgrade.
BSU BEHAVING LIKE AN SU

The cause behind this is one of two things:
The result of resetting a Tsunami MP.11 or MP.11a BSU to factory defaults and then recycling the power to
the BSU within 5 minutes of the factory reset. This may have happened prior to shipment or during your own
configuration. In this case, the device allows you to simply select BSU mode from the configuration page or
through Telnet/CLI. Simply manually re-configure the device to BSU.
The BSU is missing a license key. This would be exhibited by a red LED state upon first power-up, and after
loading a new image file, the BSU is permanently an SU and the user cannot select BSU mode.
In this case, contact Proxim support and have the unit serial number and wired MAC address available.
Support will be able to help you recover the device without sending the unit in for return.
These two conditions are being researched so that customers will not experience this symptom in the future.
We apologize for any inconvenience.
Note:
If a BSU, SU, or RSU is missing its license key, this device will behave as an SU, will support only eight
MAC devices from its Ethernet interface, and bandwidth throttling is forced to 64Kbits/sec.
128
Appendix A. Country Codes/Channels

In the CLI and MIB browser, the country code is set using the string code, as shown in the following example.
Example: To set Taiwan as the country:
set syscountrycode tw
Model 5054 (5.8 GHz) Channels/Frequencies by Country

Country (Code)
Frequency
Bands
DFS
Allowed Channels (Center Freq)

20 MHz
10 MHz (N/A to the 5054)
Argentina (AR)
5.25 - 5.35 GHz and

5.725 - 5.825 GHz
No
56 (5280), 60 (5300),
64 (5320), 149 (5745),
153 (5765), 157 (5785),
161 (5805)
56 (5280), 58 (5290),
60 (5300), 62 (5310),
64 (5320), 149 (5745),
151 (5755), 153 (5765),
155 (5775), 157 (5785),
159 (5795), 161 (5805)
56 (5280), 57 (5285), 58 (5290),

59 (5295), 60 (5300), 61 (5305),
62 (5310), 63 (5315), 64 (5320),
149 (5745), 150 (5750), 151 (5755),
152 (5760), 153 (5765), 154 (5770),
155 (5775), 156 (5780), 157 (5785),
158 (5790), 159 (5795), 160 (5800),
161 (5805)
Australia (AU)
5.725 - 5.85 GHz
No
149 (5745), 153 (5765),

157 (5785), 161 (5805),
165 (5825)
147 (5735), 149 (5745),

151 (5755), 153 (5765),
155 (5775), 157 (5785),
159 (5795), 161 (5805),
163 (5815), 165 (5825),
167 (5835)
147 (5735), 148 (5740), 149 (5745),

150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815), 164 (5820),
165 (5825), 166 (5830), 167 (5835)
Austria (AT)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Belgium (BE)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Belize (BZ)
5.725 - 5.85 GHz
No
149 (5745), 153 (5765),

157 (5785), 161 (5805),
165 (5825)
149 (5745), 151 (5755),

153 (5765), 155 (5775),
157 (5785), 159 (5795),
161 (5805), 163 (5815),
165 (5825), 167 (5835)
149 (5745), 150 (5750), 151 (5755),

152 (5760), 153 (5765), 154 (5770),
155 (5775), 156 (5780), 157 (5785),
158 (5790), 159 (5795), 160 (5800),
161 (5805), 162 (5810), 163 (5815),
164 (5820), 165 (5825), 166 (5830),
167 (5835)
Bolivia (BO)
5.725 - 5.85 GHz
No
149 (5745), 153 (5765),

157 (5785), 161 (5805),
165 (5825)
149 (5745), 151 (5755),

153 (5765), 155 (5775),
157 (5785), 159 (5795),
161 (5805), 163 (5815),
165 (5825), 167 (5835)
149 (5745), 150 (5750), 151 (5755),

152 (5760), 153 (5765), 154 (5770),
155 (5775), 156 (5780), 157 (5785),
158 (5790), 159 (5795), 160 (5800),
161 (5805), 162 (5810), 163 (5815),
164 (5820), 165 (5825), 166 (5830),
167 (5835)
129

Country (Code)
Frequency
Bands
DFS

20 MHz
Brazil (BR)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Brazil1 (B1)
5.725 - 5.85 GHz
No
149 (5745), 153 (5765),

157 (5785), 161 (5805),
165 (5825)
149 (5745), 151 (5755),

153 (5765), 155 (5775),
157 (5785), 159 (5795),
161 (5805), 163 (5815),
165 (5825), 167 (5835)
149 (5745), 150 (5750), 151 (5755),

152 (5760), 153 (5765), 154 (5770),
155 (5775), 156 (5780), 157 (5785),
158 (5790), 159 (5795), 160 (5800),
161 (5805), 162 (5810), 163 (5815),
164 (5820), 165 (5825), 166 (5830),
167 (5835)
Brunei
Darussalam (BN)
5.725 - 5.85 GHz
No
149 (5745), 153 (5765),

157 (5785), 161 (5805),
165 (5825)
149 (5745), 151 (5755),

153 (5765), 155 (5775),
157 (5785), 159 (5795),
161 (5805), 163 (5815),
165 (5825), 167 (5835)
149 (5745), 150 (5750), 151 (5755),

152 (5760), 153 (5765), 154 (5770),
155 (5775), 156 (5780), 157 (5785),
158 (5790), 159 (5795), 160 (5800),
161 (5805), 162 (5810), 163 (5815),
164 (5820), 165 (5825), 166 (5830),
167 (5835)
Bulgaria (BG)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Canada (CA)
5.25 - 5.35 GHz and

5.725 - 5.85 GHz
No
56 (5280), 60 (5300),
64 (5320), 149 (5745),
153 (5765), 157 (5785),
161 (5805), 165 (5825)
54 (5270), 56 (5280),
58 (5290), 60 (5300),
62 (5310), 64 (5320),
66 (5330), 147 (5735),
149 (5745), 151 (5755),
153 (5765), 155 (5775),
157 (5785), 159 (5795),
161 (5805), 163 (5815),
165 (5825), 167 (5835)
53 (5265), 54 (5270), 55 (5275),

56 (5280), 57 (5285), 58 (5290),
59 (5295), 60 (5300), 61 (5305),
62 (5310), 63 (5315), 64 (5320),
65 (5325), 66 (5330), 67 (5335),
147 (5735), 148 (5740), 149 (5745),
150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815), 164 (5820),
165 (5825), 166 (5830), 167 (5835)
China (CN)
5.725 - 5.85 GHz
No
149 (5745), 153 (5765),

157 (5785), 161 (5805),
165 (5825)
149 (5745), 151 (5755),

153 (5765), 155 (5775),
157 (5785), 159 (5795),
161 (5805), 163 (5815),
165 (5825), 167 (5835)
149 (5745), 150 (5750), 151 (5755),

152 (5760), 153 (5765), 154 (5770),
155 (5775), 156 (5780), 157 (5785),
158 (5790), 159 (5795), 160 (5800),
161 (5805), 162 (5810), 163 (5815),
164 (5820), 165 (5825), 166 (5830),
167 (5835)
130

Country (Code)
Frequency
Bands
DFS

20 MHz
Colombia (CO)
5.25 - 5.35 GHz and

5.725 - 5.85 GHz
No
56 (5280), 60 (5300),
64 (5320), 149 (5745),
153 (5765), 157 (5785),
161 (5805), 165 (5825)
54 (5270), 56 (5280),
58 (5290), 60 (5300),
62 (5310), 64 (5320),
66 (5330), 147 (5735),
149 (5745), 151 (5755),
153 (5765), 155 (5775),
157 (5785), 159 (5795),
161 (5805), 163 (5815),
165 (5825), 167 (5835)
53 (5265), 54 (5270), 55 (5275),

56 (5280), 57 (5285), 58 (5290),
59 (5295), 60 (5300), 61 (5305),
62 (5310), 63 (5315), 64 (5320),
65 (5325), 66 (5330), 67 (5335),
147 (5735), 148 (5740), 149 (5745),
150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815), 164 (5820),
165 (5825), 166 (5830), 167 (5835)
Cyprus (CY)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Denmark (DK)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Dominican
Republic (DO)
5.25 - 5.35 GHz and

5.725 - 5.85 GHz
No
56 (5280), 60 (5300),
64 (5320), 149 (5745),
153 (5765), 157 (5785),
161 (5805), 165 (5825)
54 (5270), 56 (5280),
58 (5290), 60 (5300),
62 (5310), 64 (5320),
66 (5330), 147 (5735),
149 (5745), 151 (5755),
153 (5765), 155 (5775),
157 (5785), 159 (5795),
161 (5805), 163 (5815),
165 (5825), 167 (5835)
53 (5265), 54 (5270), 55 (5275),

56 (5280), 57 (5285), 58 (5290),
59 (5295), 60 (5300), 61 (5305),
62 (5310), 63 (5315), 64 (5320),
65 (5325), 66 (5330), 67 (5335),
147 (5735), 148 (5740), 149 (5745),
150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815), 164 (5820),
165 (5825), 166 (5830), 167 (5835)
Estonia (EE)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
131

Country (Code)
Frequency
Bands
DFS

20 MHz
Finland (FI)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
France (FR)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Germany (DE)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Greece (GR)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Guatemala (GT)
5.25 - 5.35 GHz and

5.725 - 5.85 GHz
No
56 (5280), 60 (5300),
64 (5320), 149 (5745),
153 (5765), 157 (5785),
161 (5805), 165 (5825)
54 (5270), 56 (5280),
58 (5290), 60 (5300),
62 (5310), 64 (5320),
66 (5330), 147 (5735),
149 (5745), 151 (5755),
153 (5765), 155 (5775),
157 (5785), 159 (5795),
161 (5805), 163 (5815),
165 (5825), 167 (5835)
53 (5265), 54 (5270), 55 (5275),

56 (5280), 57 (5285), 58 (5290),
59 (5295), 60 (5300), 61 (5305),
62 (5310), 63 (5315), 64 (5320),
65 (5325), 66 (5330), 67 (5335),
147 (5735), 148 (5740), 149 (5745),
150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815), 164 (5820),
165 (5825), 166 (5830), 167 (5835)
132

Country (Code)
Frequency
Bands
DFS

20 MHz
Hong Kong (HK)
5.725 - 5.85 GHz
No
149 (5745), 153 (5765),

157 (5785), 161 (5805),
165 (5825)
147 (5735), 149 (5745),

151 (5755), 153 (5765),
155 (5775), 157 (5785),
159 (5795), 161 (5805),
163 (5815), 165 (5825),
167 (5835)
147 (5735), 148 (5740), 149 (5745),

150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815), 164 (5820),
165 (5825), 166 (5830), 167 (5835)
Hungary (HU)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Iceland (IS)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
India (IN)
5.15 - 5.35 GHz and

5.725 - 5.825 GHz
No
36 (5180), 40 (5200),
44 (5220), 48 (5240),
52 (5260), 56 (5280),
60 (5300), 64 (5320),
149 (5745), 153 (5765),
157 (5785), 161 (5805)
36 (5180), 38 (5190),
40 (5200), 42 (5210),
44 (5220), 46 (5230),
48 (5240), 50 (5250),
52 (5260), 54 (5270),
56 (5280), 58 (5290),
60 (5300), 62 (5310),
64 (5320), 66 (5330),
147 (5735), 149 (5745),
151 (5755), 153 (5765),
155 (5775), 157 (5785),
159 (5795), 161 (5805),
163 (5815)
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), 50 (5250),
51 (5255), 52 (5260), 53 (5265),
54 (5270), 55 (5275), 56 (5280),
57 (5285), 58 (5290), 59 (5295),
60 (5300), 61 (5305), 62 (5310),
63 (5315), 64 (5320), 65 (5325),
66 (5330), 67 (5335), 147 (5735),
148 (5740), 149 (5745), 150 (5750),
151 (5755), 152 (5760), 153 (5765),
154 (5770), 155 (5775), 156 (5780),
157 (5785), 158 (5790), 159 (5795),
160 (5800), 161 (5805), 162 (5810),
163 (5815)
Iran (IR)
5.725 - 5.85 GHz
No
149 (5745), 153 (5765),

157 (5785), 161 (5805),
165 (5825)
149 (5745), 151 (5755),

153 (5765), 155 (5775),
157 (5785), 159 (5795),
161 (5805), 163 (5815),
165 (5825), 167 (5835)
149 (5745), 150 (5750), 151 (5755),

152 (5760), 153 (5765), 154 (5770),
155 (5775), 156 (5780), 157 (5785),
158 (5790), 159 (5795), 160 (5800),
161 (5805), 162 (5810), 163 (5815),
164 (5820), 165 (5825), 166 (5830),
167 (5835)
133

Country (Code)
Frequency
Bands
DFS

20 MHz
Ireland (IE)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Ireland 5.8 GHz (I1)
5.725 - 5.85 GHz
Yes
147 (5735), 151 (5755),

155 (5775), 167 (5835)
145 (5725), 147 (5735),

149 (5745), 151 (5755),
153 (5765), 155 (5775),
157 (5785), 163 (5815),
165 (5825), 167 (5835),
169 (5845)
145 (5725), 146 (5730), 147 (5735),

148 (5740), 149 (5745), 150 (5750),
151 (5755), 152 (5760), 153 (5765),
154 (5770), 155 (5775), 156 (5780),
157 (5785), 158 (5790), 159 (5795),
163 (5815), 164 (5820), 165 (5825),
166 (5830), 167 (5835), 168 (5840),
169 (5845), 170 (5850)
Italy (IT)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Japan (JP)
5.25 - 5.35 GHz
Yes
56 (5280), 60 (5300),
64 (5320)
54 (5270), 56 (5280),
58 (5290), 60 (5300),
62 (5310), 64 (5320),
66 (5330)
53 (5265), 54 (5270), 55 (5275),

56 (5280), 57 (5285), 58 (5290),
59 (5295), 60 (5300), 61 (5305),
62 (5310), 63 (5315), 64 (5320),
65 (5325), 66 (5330), 67 (5335)
Japan1 (JP1)
5.15 - 5.25 GHz
No
36 (5180), 40 (5200),
44 (5220), 48 (5240)
36 (5180), 38 (5190),
40 (5200), 42 (5210),
44 (5220), 46 (5230),
48 (5240)
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)
Japan2 (J2)
5.15 - 5.25 GHz
No
36 (5180), 40 (5200),
44 (5220), 48 (5240)
36 (5180), 38 (5190),
40 (5200), 42 (5210),
44 (5220), 46 (5230),
48 (5240)
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)
Japan3 (JP3)
5.15 - 5.25 GHz and

4.9 GHz
No
8 (5040), 12 (5060),
16 (5080), 34 (5170),
38 (5190), 42 (5210),
46 (5230), 184 (4920),
188 (4940), 192 (4960),
196 (4980)
6 (5030), 8 (5040), 10 (5050),

12 (5060), 14 (5070),
16 (5080), 32 (5160),
34 (5170), 36 (5180),
38 (5190), 40 (5200),
42 (5210), 44 (5220),
46 (5230), 182 (4910),
184 (4920), 186 (4930),
188 (4940), 190 (4950),
192 (4960), 194 (4970),
196 (4980)
6 (5030), 7 (5035), 8 (5040), 9 (5045),

10 (5050), 11 (5055), 12 (5060),
13 (5065), 14 (5070), 15 (5075),
16 (5080), 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), 181 (4905), 182 (4910),
183 (4915), 184 (4920), 185 (4925),
186 (4930), 187 (4935), 188 (4940),
189 (4945), 190 (4950), 191 (4955),
192 (4960), 193 (4965), 194 (4970),
195 (4975), 196 (4980)
134

Country (Code)
Frequency
Bands
DFS

20 MHz
Japan4 (JP4)
5.25 - 5.35 GHz
Yes
56 (5280), 60 (5300),
64 (5320)
54 (5270), 56 (5280),
58 (5290), 60 (5300),
62 (5310), 64 (5320),
66 (5330)
53 (5265), 54 (5270), 55 (5275),

56 (5280), 57 (5285), 58 (5290),
59 (5295), 60 (5300), 61 (5305),
62 (5310), 63 (5315), 64 (5320),
65 (5325), 66 (5330), 67 (5335)
Japan5 (JP5)
5.25 - 5.35 GHz
Yes
56 (5280), 60 (5300),
64 (5320)
54 (5270), 56 (5280),
58 (5290), 60 (5300),
62 (5310), 64 (5320),
66 (5330)
53 (5265), 54 (5270), 55 (5275),

56 (5280), 57 (5285), 58 (5290),
59 (5295), 60 (5300), 61 (5305),
62 (5310), 63 (5315), 64 (5320),
65 (5325), 66 (5330), 67 (5335)
Korea Republic (KR) 5.725 - 5.825 GHz
No
149 (5745), 153 (5765),

157 (5785), 161 (5805)
147 (5735), 149 (5745),

151 (5755), 153 (5765),
155 (5775), 157 (5785),
159 (5795), 161 (5805),
163 (5815)
147 (5735), 148 (5740), 149 (5745),

150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815)
Korea
Republic2 (KR2)
5.725 - 5.825 GHz
No
149 (5745), 153 (5765),

157 (5785), 161 (5805)
147 (5735), 149 (5745),

151 (5755), 153 (5765),
155 (5775), 157 (5785),
159 (5795), 161 (5805),
163 (5815)
147 (5735), 148 (5740), 149 (5745),

150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815)
Latvia (LV)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Liechtenstein (LI)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Lithuania (LT)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
135

Country (Code)
Frequency
Bands
DFS

20 MHz
Luxembourg (LU)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Macau (MO)
5.725 - 5.85 GHz
No
149 (5745), 153 (5765),

157 (5785), 161 (5805),
165 (5825)
147 (5735), 149 (5745),

151 (5755), 153 (5765),
155 (5775), 157 (5785),
159 (5795), 161 (5805),
163 (5815), 165 (5825),
167 (5835)
147 (5735), 148 (5740), 149 (5745),

150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815), 164 (5820),
165 (5825), 166 (5830), 167 (5835)
Malaysia (MY)
5.25 - 5.35 GHz and

5.725 - 5.85 GHz
No
56 (5280), 60 (5300),
64 (5320), 149 (5745),
153 (5765), 157 (5785),
161 (5805), 165 (5825)
54 (5270), 56 (5280),
58 (5290), 60 (5300),
62 (5310), 64 (5320),
66 (5330), 147 (5735),
149 (5745), 151 (5755),
153 (5765), 155 (5775),
157 (5785), 159 (5795),
161 (5805), 163 (5815),
165 (5825), 167 (5835)
53 (5265), 54 (5270), 55 (5275),

56 (5280), 57 (5285), 58 (5290),
59 (5295), 60 (5300), 61 (5305),
62 (5310), 63 (5315), 64 (5320),
65 (5325), 66 (5330), 67 (5335),
147 (5735), 148 (5740), 149 (5745),
150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815), 164 (5820),
165 (5825), 166 (5830), 167 (5835)
Malta (MT)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Mexico (MX)
5.725 - 5.85 GHz
No
149 (5745), 153 (5765),

157 (5785), 161 (5805),
165 (5825)
147 (5735), 149 (5745),

151 (5755), 153 (5765),
155 (5775), 157 (5785),
159 (5795), 161 (5805),
163 (5815), 165 (5825),
167 (5835)
147 (5735), 148 (5740), 149 (5745),

150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815), 164 (5820),
165 (5825), 166 (5830), 167 (5835)
Netherlands (NL)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
136

Country (Code)
Frequency
Bands
DFS

20 MHz
New Zealand (NZ)
5.725 - 5.85 GHz
No
149 (5745), 153 (5765),

157 (5785), 161 (5805),
165 (5825)
147 (5735), 149 (5745),

151 (5755), 153 (5765),
155 (5775), 157 (5785),
159 (5795), 161 (5805),
163 (5815), 165 (5825),
167 (5835)
147 (5735), 148 (5740), 149 (5745),

150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815), 164 (5820),
165 (5825), 166 (5830), 167 (5835)
North Korea (KP)
5.725 - 5.825 GHz
No
149 (5745), 153 (5765),

157 (5785), 161 (5805)
147 (5735), 149 (5745),

151 (5755), 153 (5765),
155 (5775), 157 (5785),
159 (5795), 161 (5805),
163 (5815)
147 (5735), 148 (5740), 149 (5745),

150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815)
Norway (NO)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Panama (PA)
5.25 - 5.35 GHz and

5.725 - 5.85 GHz
No
56 (5280), 60 (5300),
64 (5320), 149 (5745),
153 (5765), 157 (5785),
161 (5805), 165 (5825)
54 (5270), 56 (5280),
58 (5290), 60 (5300),
62 (5310), 64 (5320),
66 (5330), 147 (5735),
149 (5745), 151 (5755),
153 (5765), 155 (5775),
157 (5785), 159 (5795),
161 (5805), 163 (5815),
165 (5825), 167 (5835)
53 (5265), 54 (5270), 55 (5275),

56 (5280), 57 (5285), 58 (5290),
59 (5295), 60 (5300), 61 (5305),
62 (5310), 63 (5315), 64 (5320),
65 (5325), 66 (5330), 67 (5335),
147 (5735), 148 (5740), 149 (5745),
150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815), 164 (5820),
165 (5825), 166 (5830), 167 (5835)
Philippines (PH)
5.25 - 5.35 GHz and

5.725 - 5.85 GHz
No
56 (5280), 60 (5300),
64 (5320), 149 (5745),
153 (5765), 157 (5785),
161 (5805), 165 (5825)
54 (5270), 56 (5280),
58 (5290), 60 (5300),
62 (5310), 64 (5320),
66 (5330), 147 (5735),
149 (5745), 151 (5755),
153 (5765), 155 (5775),
157 (5785), 159 (5795),
161 (5805), 163 (5815),
165 (5825), 167 (5835)
53 (5265), 54 (5270), 55 (5275),

56 (5280), 57 (5285), 58 (5290),
59 (5295), 60 (5300), 61 (5305),
62 (5310), 63 (5315), 64 (5320),
65 (5325), 66 (5330), 67 (5335),
147 (5735), 148 (5740), 149 (5745),
150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815), 164 (5820),
165 (5825), 166 (5830), 167 (5835)
Poland (PL)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
137

Country (Code)
Frequency
Bands
DFS

20 MHz
Portugal (PT)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Puerto Rico (PR)
5.25 - 5.35 GHz and

5.725 - 5.85 GHz
No
56 (5280), 60 (5300),
64 (5320), 149 (5745),
153 (5765), 157 (5785),
161 (5805), 165 (5825)
54 (5270), 56 (5280),
58 (5290), 60 (5300),
62 (5310), 64 (5320),
66 (5330), 147 (5735),
149 (5745), 151 (5755),
153 (5765), 155 (5775),
157 (5785), 159 (5795),
161 (5805), 163 (5815),
165 (5825), 167 (5835)
53 (5265), 54 (5270), 55 (5275),

56 (5280), 57 (5285), 58 (5290),
59 (5295), 60 (5300), 61 (5305),
62 (5310), 63 (5315), 64 (5320),
65 (5325), 66 (5330), 67 (5335),
147 (5735), 148 (5740), 149 (5745),
150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815), 164 (5820),
165 (5825), 166 (5830), 167 (5835)
Russia (RU)
5.15 - 5.85 GHz
No
30 (5150), 34 (5170),
38 (5190), 42 (5210),
46 (5230), 50 (5250),
54 (5270), 58 (5290),
62 (5310), 66 (5330),
70 (5350), 74 (5370),
78 (5390), 82 (5410),
86 (5430), 90 (5450),
94 (5470), 98 (5490),
102 (5510), 106 (5530),
110 (5550), 114 (5570),
118 (5590), 122 (5610),
126 (5630), 130 (5650),
134 (5670), 138 (5690),
142 (5710), 146 (5730),
150 (5750), 154 (5770),
158 (5790), 162 (5810),
166 (5830), 170 (5850)
30 (5150), 32 (5160),
34 (5170), 36 (5180)
38 (5190), 40 (5200),
42 (5210), 44 (5220),
46 (5230), 48 (5240),
50 (5250), 52 (5260),
54 (5270), 56 (5280),
58 (5290), 60 (5300),
62 (5310), 64 (5320),
66 (5330), 68 (5340),
70 (5350), 72 (5360),
74 (5370), 76 (5380),
78 (5390), 80 (5400),
82 (5410), 84 (5420),
86 (5430), 88 (5440),
90 (5450), 92 (5460),
94 (5470), 96 (5480),
98 (5490), 100 (5500),
102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710), 144 (5720),
146 (5730), 148 (5740),
150 (5750), 152 (5760),
154 (5770), 156 (5780),
158 (5790), 160 (5800),
162 (5810), 164 (5820),
166 (5830), 168 (5840),
170 (5850)
30 (5150), 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), 50 (5250),
51 (5255), 52 (5260), 53 (5265),
54 (5270), 55 (5275), 56 (5280),
57 (5285), 58 (5290), 59 (5295),
60 (5300), 61 (5305), 62 (5310),
63 (5315), 64 (5320), 65 (5325),
66 (5330), 67 (5335), 68 (5340),
69 (5345), 70 (5350), 71 (5355),
72 (5360), 73 (5365), 74 (5370),
75 (5375), 76 (5380), 77 (5385),
78 (5390), 79 (5395), 80 (5400),
81 (5405), 82 (5410), 83 (5415),
84 (5420), 85 (5425), 86 (5430),
87 (5435), 88 (5440), 89 (5445),
90 (5450), 91 (5455), 92 (5460),
93 (5465), 94 (5470), 95 (5475),
96 (5480), 97 (5485), 98 (5490),
99 (5495), 100 (5500), 101 (5505),
102 (5510), 103 (5515), 104 (5520),
105 (5525), 106 (5530), 107 (5535),
108 (5540), 109 (5545), 110 (5550),
111 (5555), 112 (5560), 113 (5565),
114 (5570), 115 (5575), 116 (5580),
117 (5585), 118 (5590), 119 (5595),
120 (5600), 121 (5605), 122 (5610),
123 (5615), 124 (5620), 125 (5625),
126 (5630), 127 (5635), 128 (5640),
129 (5645), 130 (5650), 131 (5655),
132 (5660), 133 (5665), 134 (5670),
135 (5675), 136 (5680), 137 (5685),
138 (5690), 139 (5695), 140 (5700),
141 (5705), 142 (5710), 143 (5715),
144 (5720), 145 (5725), 146 (5730),
147 (5735), 148 (5740), 149 (5745),
150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815), 164 (5820),
165 (5825), 166 (5830), 167 (5835),
168 (5840), 169 (5845), 170 (5850)
138

Country (Code)
Frequency
Bands
DFS

20 MHz
Saudi Arabia (SA)
5.15 - 5.35 GHz and

5.725 - 5.825 GHz
No
36 (5180), 40 (5200),
44 (5220), 48 (5240),
52 (5260), 56 (5280),
60 (5300), 64 (5320),
149 (5745), 153 (5765),
157 (5785), 161 (5805)
36 (5180), 38 (5190),
40 (5200), 42 (5210),
44 (5220), 46 (5230),
48 (5240), 50 (5250),
52 (5260), 54 (5270),
56 (5280), 58 (5290),
60 (5300), 62 (5310),
64 (5320), 66 (5330),
147 (5735), 149 (5745),
151 (5755), 153 (5765),
155 (5775), 157 (5785),
159 (5795), 161 (5805),
163 (5815)
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), 50 (5250),
51 (5255), 52 (5260), 53 (5265),
54 (5270), 55 (5275), 56 (5280),
57 (5285), 58 (5290), 59 (5295),
60 (5300), 61 (5305), 62 (5310),
63 (5315), 64 (5320), 65 (5325),
66 (5330), 67 (5335), 147 (5735),
148 (5740), 149 (5745), 150 (5750),
151 (5755), 152 (5760), 153 (5765),
154 (5770), 155 (5775), 156 (5780),
157 (5785), 158 (5790), 159 (5795),
160 (5800), 161 (5805), 162 (5810),
163 (5815)
Singapore (SG)
5.15 - 5.25 GHz and

5.725 - 5.85 GHz
No
36 (5180), 40 (5200),
44 (5220), 48 (5240),
149 (5745), 153 (5765),
157 (5785), 161 (5805),
165 (5825)
36 (5180), 38 (5190),
40 (5200), 42 (5210),
44 (5220), 46 (5230),
48 (5240), 147 (5735),
149 (5745), 151 (5755),
153 (5765), 155 (5775),
157 (5785), 159 (5795),
161 (5805), 163 (5815),
165 (5825), 167 (5835)
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), 147 (5735), 148 (5740),
149 (5745), 150 (5750), 151 (5755),
152 (5760), 153 (5765), 154 (5770),
155 (5775), 156 (5780), 157 (5785),
158 (5790), 159 (5795), 160 (5800),
161 (5805), 162 (5810), 163 (5815),
164 (5820), 165 (5825), 166 (5830),
167 (5835)
Slovak Republic (SK) 5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Slovenia (SI)
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
5.47 - 5.725 GHz
139

Country (Code)
Frequency
Bands
DFS

20 MHz
South Africa (ZA)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Spain (ES)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Sweden (SE)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Switzerland (CH)
5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
Taiwan (TW)
5.25 - 5.35 GHz and

5.725 - 5.825 GHz
No
56 (5280), 60 (5300),
64 (5320), 149 (5745),
153 (5765), 157 (5785),
161 (5805)
54 (5270), 56 (5280),
58 (5290), 60 (5300),
62 (5310), 64 (5320),
66 (5330), 147 (5735),
149 (5745), 151 (5755),
153 (5765), 155 (5775),
157 (5785), 159 (5795),
161 (5805), 163 (5815)
53 (5265), 54 (5270), 55 (5275),

56 (5280), 57 (5285), 58 (5290),
59 (5295), 60 (5300), 61 (5305),
62 (5310), 63 (5315), 64 (5320),
65 (5325), 66 (5330), 67 (5335),
147 (5735), 148 (5740), 149 (5745),
150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815)
140

Country (Code)
Frequency
Bands
DFS

20 MHz
No
149 (5745), 153 (5765),

157 (5785), 161 (5805)
147 (5735), 149 (5745),

151 (5755), 153 (5765),
155 (5775), 157 (5785),
159 (5795), 161 (5805),
163 (5815)
147 (5735), 148 (5740), 149 (5745),

150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815)
United Kingdom (GB) 5.47 - 5.725 GHz
Yes
100 (5500), 104 (5520),

108 (5540), 112 (5560),
116 (5580), 120 (5600),
124 (5620), 128 (5640),
132 (5660), 136 (5680),
140 (5700)
98 (5490), 100 (5500),

102 (5510), 104 (5520),
106 (5530), 108 (5540),
110 (5550), 112 (5560),
114 (5570), 116 (5580),
118 (5590), 120 (5600),
122 (5610), 124 (5620),
126 (5630), 128 (5640),
130 (5650), 132 (5660),
134 (5670), 136 (5680),
138 (5690), 140 (5700),
142 (5710)
97 (5485), 98 (5490), 99 (5495),

100 (5500), 101 (5505), 102 (5510),
103 (5515), 104 (5520), 105 (5525),
106 (5530), 107 (5535), 108 (5540),
109 (5545), 110 (5550), 111 (5555),
112 (5560), 113 (5565), 114 (5570),
115 (5575), 116 (5580), 117 (5585),
118 (5590), 119 (5595), 120 (5600),
121 (5605), 122 (5610), 123 (5615),
124 (5620), 125 (5625), 126 (5630),
127 (5635), 128 (5640), 129 (5645),
130 (5650), 131 (5655), 132 (5660),
133 (5665), 134 (5670), 135 (5675),
136 (5680), 137 (5685), 138 (5690),
139 (5695), 140 (5700), 141 (5705),
142 (5710)
United Kingdom 5.8

GHz (G1)
5.725 - 5.85 GHz
Yes
147 (5735), 151 (5755),

155 (5775), 167 (5835)
145 (5725), 147 (5735),

149 (5745), 151 (5755),
153 (5765), 155 (5775),
157 (5785), 163 (5815),
165 (5825), 167 (5835),
169 (5845)
145 (5725), 146 (5730), 147 (5735),

148 (5740), 149 (5745), 150 (5750),
151 (5755), 152 (5760), 153 (5765),
154 (5770), 155 (5775), 156 (5780),
157 (5785), 158 (5790), 159 (5795),
163 (5815), 164 (5820), 165 (5825),
166 (5830), 167 (5835), 168 (5840),
169 (5845), 170 (5850)
United States (US)
5.25 - 5.35 GHz and

5.725 - 5.85 GHz
No
56 (5280), 60 (5300),
64 (5320), 149 (5745),
153 (5765), 157 (5785),
161 (5805), 165 (5825)
54 (5270), 56 (5280),
58 (5290), 60 (5300),
62 (5310), 64 (5320),
66 (5330), 147 (5735),
149 (5745), 151 (5755),
153 (5765), 155 (5775),
157 (5785), 159 (5795),
161 (5805), 163 (5815),
165 (5825), 167 (5835)
53 (5265), 54 (5270), 55 (5275),

56 (5280), 57 (5285), 58 (5290),
59 (5295), 60 (5300), 61 (5305),
62 (5310), 63 (5315), 64 (5320),
65 (5325), 66 (5330), 67 (5335),
147 (5735), 148 (5740), 149 (5745),
150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815), 164 (5820),
165 (5825), 166 (5830), 167 (5835)
Uruguay (UY)
5.725 - 5.825 GHz
No
149 (5745), 153 (5765),

157 (5785), 161 (5805)
147 (5735), 149 (5745),

151 (5755), 153 (5765),
155 (5775), 157 (5785),
159 (5795), 161 (5805),
163 (5815)
147 (5735), 148 (5740), 149 (5745),

150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815)
Venezuela (VE)
5.725 - 5.825 GHz
No
149 (5745), 153 (5765),

157 (5785), 161 (5805)
147 (5735), 149 (5745),

151 (5755), 153 (5765),
155 (5775), 157 (5785),
159 (5795), 161 (5805),
163 (5815)
147 (5735), 148 (5740), 149 (5745),

150 (5750), 151 (5755), 152 (5760),
153 (5765), 154 (5770), 155 (5775),
156 (5780), 157 (5785), 158 (5790),
159 (5795), 160 (5800), 161 (5805),
162 (5810), 163 (5815)
Thailand (TH)
5.725 - 5.825 GHz
141
Technical Support
If you are having a problem using a Proxim WAN product and cannot resolve it with the information in the product
documentation, gather the following information and contact Proxim Technical Support at
http://support.proxim.com/:
What kind of network are you using?

What were you doing when the error occurred?
What error message did you see?
Can you reproduce the problem?
Be sure to obtain an RMA number at http://www.proxim.com/support/rmaservices/ before sending any equipment

to Proxim for repair.
Email Support
To receive E-mail technical support, be sure to include the serial number of the product(s) in question. The serial
number should be on the product and conform to the following format: ##UT########, or ##R7########. We are
unable to respond to your inquiry without this information.
Telephone Support
Telephone support is available M-F 8:00 AM to 6:00 PM, Pacific Time. Use the following telephone numbers:
USA and Canada: 1-866-674-6626 (Toll Free)
International:
+1-408-542-5390
Proxim Web Site Support

Search Knowledgebase:
http://support.proxim.com/
Download latest software and documentation:
http://support.proxim.com/
Technical Support
142
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 In the event a Product fails to perform in accordance with its specification during the Warranty
Period, Proxim offers return-to-factory repair or replacement, with a thirty (30) business-day turnaround from the date of
receipt of the defective Product at a Proxim Wireless Corporation Repair Center. When Proxim has reasonably determined
that a returned Product is defective and is still under Warranty, Proxim shall, at its option, either: (a) repair the defective
Product; (b) replace the defective Product with a refurbished Product that is equivalent to the original; or (c) where repair or
replacement cannot be accomplished, refund the price paid for the defective Product. The Warranty Period for repaired or
replacement Products shall be ninety (90) days or the remainder of the original Warranty Period, whichever is longer. This
constitutes Buyers sole and exclusive remedy and Proxims sole and exclusive liability under this Warranty.
Limitations of Warranty The express warranties set forth in this Agreement will not apply to defects in a Product caused;
(i) through no fault of Proxim during shipment to or from Buyer, (ii) by the use of software other than that provided with or
installed in the Product, (iii) by the use or operation of the Product in an application or environment other than that intended or
recommended by Proxim, (iv) by modifications, alterations, or repairs made to the Product by any party other than Proxim or
Proxims authorized repair partners, (v) by the Product being subjected to unusual physical or electrical stress, or (vii) by
failure of Buyer to comply with any of the return procedures specified in this Statement of Warranty.
Support Procedures Buyer should return defective LAN Products1 within the first 30 days to the merchant from which the
Products were purchased. Buyer can contact a Proxim Customer Service Center either by telephone or via web. Calls for
support for Products that are near the end of their warranty period should be made not longer than seven (7) days after
expiration of warranty. Repair of Products that are out of warranty will be subject to a repair fee. Contact information is shown
below. Additional support information can be found at Proxims web site at http://support.proxim.com.
LAN Products 1:
Domestic calls:
1-866-674-6626
International calls: 1-408-542-5390
WAN Products 2: Domestic calls:

1-866-674-6626
International calls: 1-408-542-5390
(24 hours per day, 7 days per week)

(8:00 A.M. 5:00 P.M, M-F Pacific Time)
When contacting the Customer Service Center 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 Proxims 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 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, 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 Service Contract or the call is made within the first thirty (30) days of the Products invoice date. Calls that are
outside of the 30-day free support time will be charged a fee of $25.00 (US Dollars) per Support Call.
If Proxim 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 stores all resolved problems in a solution database: http://support.proxim.com.
Ask a Question or Open an Issue Submit a question or open an issue to Proxim technical support staff:
http://support.proxim.com/cgi-bin/proxim.cfg/php/enduser/ask.php.
Other Adapter Cards Proxim does not support internal mini-PCI devices that are built into laptop computers, even if
identified as "ORiNOCO" devices. Customers having such devices should contact the laptop vendor's technical support for
assistance. For support for a PCMCIA card carrying a brand name other than Proxim, ORiNOCO, Lucent, Wavelan, or
Skyline, Customer should contact the brand vendor's technical support for assistance.
LAN products include: ORiNOCO
WAN products include: Lynx, Tsunami, Tsunami MP, Tsunami QuickBridge
Statement of Warranty
143

Proxim Tsunami MP11a 5054

Uploaded by

Copyright:

Available Formats

Proxim Tsunami MP11a 5054

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Proxim Tsunami MP11a 5054

Uploaded by

Copyright:

Available Formats

What are the different wireless network topologies discussed in the document?

What are the different wireless network topologies discussed in the document?

What are the steps to take if a product causes harmful interference?

What are the steps to take if a product causes harmful interference?

Part Number 72282

Tsunami MP.11 5054 Installation and Management

Reorient or relocate the receiving antenna.

Tsunami MP.11 5054 Installation and Management

Tsunami MP.11 5054 Installation and Management

8) Configure Packet Filtering .......................................................................................................................70

Tsunami MP.11 5054 Installation and Management

APPENDIX A. COUNTRY CODES/CHANNELS ...................................................................................................129

Tsunami MP.11 5054 Installation and Management

The use of a highly optimized protocol for outdoor applications

ABOUT THIS BOOK

Tsunami MP.11 5054 Installation and Management

WIRELESS NETWORK TOPOLOGIES

Tsunami MP.11 5054 Installation and Management

Leased lines in building-to-building connections

Wired Ethernet backbones between wireless access points in difficult-to-wire environments

Tsunami MP.11 5054 Installation and Management

IDENTIFYING NETWORK TOPOLOGY AND EQUIPMENT

FINDING A SUITABLE LOCATION

Tsunami MP.11 5054 Installation and Management

Tsunami 5054 unit

Tsunami MP.11 5054 Installation and Management

4. Remove the cable cover.

Tsunami MP.11 5054 Installation and Management

Tsunami MP.11 5054 Installation and Management

ATTACHING A KENSINGTON SECURITY LOCK (OPTIONAL)

For information about Kensington security solutions, go to http://www.kensington.com .

MOUNTING THE UNIT

Tsunami MP.11 5054 Installation and Management

5. Remove the cable cover from the unit.

6. Remove the front and back covers from the unit.

Tsunami MP.11 5054 Installation and Management

4. Remove the screws from the rubber feet.

POWERING ON THE UNIT

Tsunami MP.11 5054 Installation and Management

Power is not present or is malfunctioning.

INSTALLING DOCUMENTATION AND SOFTWARE

Tsunami MP.11 5054 Installation and Management

ALIGNING THE ANTENNA

Antenna Alignment Commands

Tsunami MP.11 5054 Installation and Management

Chapter 3. Management Overview

Chapter 3. Management Overview

Tsunami MP.11 5054 Installation and Management

Setting the IP Address

Chapter 3. Management Overview

Tsunami MP.11 5054 Installation and Management

STARTING THE WEB INTERFACE

Chapter 3. Management Overview

Tsunami MP.11 5054 Installation and Management

Chapter 3. Management Overview

Tsunami MP.11 5054 Installation and Management

CHANGING BASIC CONFIGURATION INFORMATION

Country and Related Settings

Chapter 3. Management Overview

Tsunami MP.11 5054 Installation and Management