Cisco Aironet Workgroup Bridge Software Configuration Guide: 340 and 350 Series
Cisco Aironet Workgroup Bridge Software Configuration Guide: 340 and 350 Series
Corporate Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 526-4100
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION
PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO
LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as
part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE
PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED
OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL
DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR
INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
AccessPath, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the
Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing,
FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness
Scorecard, MGX, the Networkers logo, Packet, PIX, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN,
Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That’s
Possible, and Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco
Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo,
Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, Post-Routing,
Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates
in the U.S. and certain other countries.
All other brands, names, or trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word
partner does not imply a partnership relationship between Cisco and any other company. (0102R)
Preface ix
Audience x
Organization x
Conventions xi
Related Publications xi
Obtaining Documentation xi
World Wide Web xi
Documentation CD-ROM xii
Ordering Documentation xii
Documentation Feedback xii
Obtaining Technical Assistance xiii
Cisco.com xiii
Technical Assistance Center xiii
Contacting TAC by Using the Cisco TAC Website xiii
Contacting TAC by Telephone xiv
Overview 1-2
Terminology 1-3
Overview 8-2
Overview 9-2
INDEX
This publication explains the steps for configuration, control, and maintenance of the Cisco Aironet
workgroup bridge.
The following topics are covered in this section:
• Audience, page x
• Organization, page x
• Conventions, page xi
• Related Publications, page xi
• Obtaining Documentation, page xi
• Obtaining Technical Assistance, page xiii
Audience
This publication is for the person configuring and operating a workgroup bridge. The person should be
familiar with network structures and with network terms and concepts.
Organization
The major sections of this guide are:
• Chapter 1, “Workgroup Bridge Overview,” contains a general overview and a summary of key
features.
• Chapter 2, “Using the Console System,” introduces the Console System, the Main menu, and shows
you how to set up and configure the bridge’s parameters.
• Chapter 3, “Using the Configuration Menu,” provides an overview of the Configuration menu and
how to save and restore your configurations.
• Chapter 4, “Configuring the Radio Network,” contains detailed procedures for configuring the radio
network.
• Chapter 5, “Configuring the Ethernet Port,” contains detailed procedures for configuring the
Ethernet port.
• Chapter 6, “Setting Network Identifiers,” outlines the procedures for setting the bridge’s Network
Identifiers.
• Chapter 7, “Viewing Statistics,” describes how to use the Statistics menu to monitor the performance
of the bridge.
• Chapter 8, “Using the Association Table,” provides an introduction to the association process and
detailed procedures for setting up the bridge’s association table.
• Chapter 9, “Using Filters,” describes the use of filters to improve network performance.
• Chapter 10, “Setting Up Event Logs,” outlines the procedures for setting up event logs and lists the
common error log messages received on the bridge.
• Chapter 11, “Performing Diagnostics,” provides detailed procedures for restarting your bridge,
returning to your default configuration, and loading new firmware versions.
• Appendix A, “Workgroup Bridge Specifications,” details the bridge radio and physical
specifications.
• Appendix B, “Console Menu Tree,” provides menu maps for the bridge’s configuration menus.
Conventions
This publication uses the following conventions to convey instructions and information:
• Commands and keywords are in boldface type.
• Web-browser page links are underlined.
Note Means reader take note. Notes contain helpful suggestions or references to materials not contained
in this manual.
Timesaver Means the described action saves time. You can save time by performing the action described in the
paragraph.
Caution Means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
Related Publications
For more information about installation and related products, refer to the following publications:
• Cisco Aironet Workgroup Bridge Hardware Installation Guide
• Mounting Instructions for Cisco Aironet 340 and 350 Series Access Points, Base Stations, and
Workgroup Bridges
• Release Notes for Cisco Aironet Workgroup Bridges
Obtaining Documentation
The following sections provide sources for obtaining documentation from Cisco Systems.
Documentation CD-ROM
Cisco documentation and additional literature are available in a CD-ROM package, which ships
with your product. The Documentation CD-ROM is updated monthly and may be more current than
printed documentation. The CD-ROM package is available as a single unit or as an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
• Registered Cisco Direct Customers can order Cisco Product documentation from the Networking
Products MarketPlace:
http://www.cisco.com/cgi-bin/order/order_root.pl
• Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription
Store:
http://www.cisco.com/go/subscription
• Nonregistered Cisco.com users can order documentation through a local account representative by
calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by
calling 800 553-NETS(6387).
Documentation Feedback
If you are reading Cisco product documentation on the World Wide Web, you can submit technical
comments electronically. Click Feedback in the toolbar and select Documentation. After you complete
the form, click Submit to send it to Cisco.
You can e-mail your comments to [email protected].
To submit your comments by mail, use the response card behind the front cover of your document, or
write to the following address:
Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open
access to Cisco information and resources at anytime, from anywhere in the world. This highly
integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline
business processes and improve productivity. Through Cisco.com, you can find information about Cisco
and our networking solutions, services, and programs. In addition, you can resolve technical issues with
online technical support, download and test software packages, and order Cisco learning materials and
merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and
services. Registered users can order products, check on the status of an order, access technical support,
and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
http://www.cisco.com
This chapter provides an overview of the workgroup bridge and how it operates in a wireless
infrastructure.
Here’s what you’ll find in this chapter:
• Overview, page 1-2
• Data Transparency and Protocols, page 1-2
• Ethernet Compatibility and Protocols Supported, page 1-2
• Radio Characteristics, page 1-2
• Radio Ranges, page 1-3
• Radio Antenna, page 1-3
• Security Features, page 1-3
• Terminology, page 1-3
• Bridge Configuration, page 1-4
Overview
The Cisco Aironet Workgroup Bridge (hereafter referred to as the bridge) is a small, stand-alone unit
that provides a wireless infrastructure connection for Ethernet-enabled devices. Figure 1 on page 1-5
shows a typical network configuration. A device connected to a bridge communicates with a network
infrastructure through a Cisco Aironet Access Point (hereafter referred to as an access point). The bridge
connects to a device through a standard Ethernet port using a 10BASE-T/RJ-45 (twisted pair) connector.
The bridge provides wireless LAN connections for up to eight devices connected to a hub through an
Ethernet cable.
Radio Characteristics
The bridge uses Direct Sequence Spread Spectrum (DSSS) transmission. It combines high data
throughput with excellent immunity to interference. The bridge operates in the 2.4-GHz license-free
Industrial Scientific and Medical (ISM) band and transmits over a half-duplex radio channel operating
at up to 11 megabits per second (Mbps).
Radio Ranges
Because the bridge is a radio device, it is susceptible to common causes of interference that can reduce
throughput and range. Follow these guidelines to ensure the best possible performance:
• Install the bridge in an area where large steel structures such as shelving units, bookcases, and filing
cabinets will not obstruct radio signals to and from the bridge.
• Install the bridge away from microwave ovens. Microwave ovens operate on the same frequency as
the bridge and can cause signal interference.
• Clear or open areas provide better radio range than closed or filled areas. Also, the less cluttered the
work environment, the greater the range.
Radio Antenna
The bridge comes with two possible antenna configurations: one captured antenna or two reverse-TNC
antenna connectors to which the user can attach one or two antennas.
Security Features
The bridge offers the following security features:
• DSSS technology, previously developed for military “anti-jamming” and “low probability of
intercept” radio systems.
• Wired Equivalent Privacy (WEP), an IEEE 802.11 feature that provides data confidentiality
equivalent to a wired LAN without crypto techniques.
• A service set identifier (SSID) that must match the SSID used by the parent access point.
• The ability to set passwords and privilege levels.
Terminology
In describing wireless LANs and LAN components, Cisco Aironet uses the following terminology:
Association—each root unit or repeater (defined later in this section) in the infrastructure contains an
association table that controls the routing of packets between the access point and the wireless
infrastructure. The association table maintains entries for all the nodes situated below the access point
on the infrastructure including repeaters and client nodes.
Cell—the area of radio range or coverage in which the bridge can communicate with the access point.
The size of a single cell depends upon the speed of the transmission, the type of antenna used, and the
physical environment as well as other factors.
End node—a client device such as a workstation or laptop computer that has a wired Ethernet
connection to the bridge though a hub.
Infrastructure—the communications system that combines access points, bridges, mobile nodes and
fixed nodes. access points within the infrastructure can be root units, which are physically wired to the
LAN backbone, or they can act as wireless repeaters (defined later in this section). Other wireless
devices serve as fixed nodes or mobile nodes.
Parent/child node—refers to the relationships between nodes in the wireless infrastructure. The
complete set of relationships is sometimes described as a network tree. For example, the access point (at
the top of the tree) is the parent of the end nodes, and the end nodes are the children of the access point.
Repeater—an access point that extends the radio range of the infrastructure. A repeater is not physically
attached to the wired LAN but communicates by radio to another access point, which is either a root unit
or another repeater.
Root unit—a point that is located at the top, or starting point, of a wireless infrastructure. A root unit
provides the physical connection to the wired LAN and contains configuration information in its
association table that covers all nodes that access the wired infrastructure. All access points directly
attached to the wired LAN backbone are root units.
Bridge Configuration
Figure 1-1 shows a typical configuration for a wireless LAN that incorporates a bridge.
Wired LAN
File server
Access point
Workgroup
bridge
Station with
radio card
Hub
1X 2X
ETHERN
ET 3X
SPEED
4X
LED
100BaseTX
SOLID 1 2 3
10BaseT 4
BLINK 5 6 7
8
5X 6X 7X 8X
MDI
Workstation
MDI-X
Workstation
Laptop
Workstation
39283
This chapter describes the console system of the bridge. This system contains all commands necessary
to configure and monitor the operation of the bridge.
Here’s what you’ll find in this chapter:
• Starting a Telnet Session, page 2-2
• Main Menu, page 2-2
• Web Access, page 2-5
• About the Menus, page 2-6
Step 1 On your computer’s Start menu, choose Programs > Accessories > Telnet.
If Telnet is not listed in your Accessories menu, click Start > Run, type Telnet in the entry field, and
press Enter.
Step 2 When the Telnet window appears, click Connect and select Remote System. In Windows 2000, the
Telnet window does not contain pull-down menus. To start the Telnet session in Windows 2000, type
open followed by the bridge’s IP address, and skip to Step 4.
Step 3 In the Host Name field, type the bridge’s IP address provided by the IP Finder utility. (See the bridge’s
hardware installation guide for detailed instructions on using the IP Finder Utility.)
Step 4 Click Connect.
Main Menu
After the bridge is assigned an IP address and is connected wirelessly to the infrastructure, you can
connect to the console system from a remote PC or host by using the Telnet program. When the
connection is made, the Main menu displays. The console system is organized as a set of menus. Each
selection in a menu list can lead to a submenu or displays a command that configures or displays
information controlling the bridge. Here is the Main menu.
To select an item from the menu, type either the number displayed beside the selection or the name listed
in the option column and then press Enter. If you use the name method, you need to type only enough
characters to make the name unique from the other selection names in the menu. The Backspace key
deletes a single character and the Delete key deletes the entire line.
Submenus
If the selection is a submenu, the new menu will display. You can choose a selection from this menu or
return to the previous menu by pressing the Escape key. To return to the Main menu, type the equal sign
(=) at the cursor prompt.
If the string contains a space, enclose the string in quotation marks. To type an empty string, type
two quotation marks with nothing between them.
• Decimal integer: a number. The prompt will indicate the range of allowed values.
Enter a size between 1 and 100 : 99
• Hexadecimal integer: a number specified in hexadecimal using the characters 0-9 and a-f or A-F.
Enter a hex number between 1h and ffh : 1a
• IP address: an Internet address in the form of four numbers from 0 through 255 separated by dots
(.). Leading zeros in any of the numbers may be omitted.
Enter an IP address : 192.200.1.50
When all information is typed, the command executes. If the information typed changed a
configuration item, the new value is displayed in the menus.
Some configuration commands allow only one of two fixed values. When the menu item is selected,
the opposite value to the current value is chosen. For example, if the configuration item is only a
selection between on and off, and the current value is on, then selecting the menu option selects the
off value.
Some commands that have a severe effect on the operation of the bridge (such as the Restart
command) prompt to be sure you want to execute the command.
Are you sure [y/n] :
Caution Changes to radio parameters take effect immediately. If your Telnet or browser session is accessing
the bridge over a radio link, you could lose the session because the bridge may no longer be
associated to an access point on the network. If this happens, it is necessary to change the access
point’s radio parameters to reestablish the radio link. You can also use a crossover cable to attach the
bridge to the Ethernet port on a PC to configure it.
Parts of the prompt may or may not be present depending on the display. If you are not at the first
page of the display, you can type an f to return to the first page or p to return to the previous page.
If you are not at the last page, you can type an n to go to the next page.
Command-Line Mode
Another way to move within the console system is to type commands directly from the Main menu.
Commands allow you to bypass the menu system and go directly to any level submenu or option. If you
are familiar with the options, you can include an option setting as part of the command.
To access the Radio Configuration menu (located two submenus down) but not change a setting, follow
these steps:
To access the packet size option from the Radio link test menu (located three submenus down) and set a
packet size of 512 bytes, follow these steps:
Step 1 At the Main menu prompt enter configuration radio linktest size 512.
Step 2 Press Enter. The packet size is set and the Main menu appears.
Web Access
The bridge also supports access to the console system through an HTML browser. To start a connection,
go to this address:
http://ip address of bridge/
The Home page is the equivalent to the Main menu screen when you access the console system using
Telnet. In order to make changes to the bridge, you must click Allow Config Changes. When you click
a configuration link, its configuration page displays. This figure shows a typical Configuration Ethernet
page:
To make changes, enter the values for the parameter you want to change and click Save. You must click
Save for each parameter you change. When you have finished making changes, click Home to return to
the Home Page.
This chapter provides a general introduction to the Configuration menu and describes the procedures for
saving and restoring your configurations.
Here’s what you’ll find in this chapter:
• Viewing the Configuration Menu, page 3-2
• Configuration Menu Options, page 3-2
• Using the Configuration Security Menu, page 3-3
• Using the Configuration Console Menu, page 3-4
• Using the Configuration Time Menu (Time), page 3-8
• Backing Up Your Configuration (Dump), page 3-9
• Restoring Your Configuration, page 3-10
Step 1 Choose Security from the Configuration menu. The Configuration Security menu appears.
Step 2 Choose Mode. The following message appears:
Enter one of [off eap]
Step 3 Choose eap and press Enter to return to the Configuration Security menu.
Step 4 Choose Username. The following message appears:
Enter a string:
Step 5 Enter your bridge’s username and press Enter to return to the Configuration Security menu.
Step 6 Choose Userpwd. The following message appears:
Enter a string:
Step 7 Enter your bridge’s password and press Enter to return to the Configuration Security menu.
Step 8 Press Escape once to return to the Configuration menu or twice to return to the Main menu.
Caution Perform all the steps in the above procedure. Even with eap enabled, the bridge will not pass data
until you are connected to the ACS server.
Step 1 Select Privilege from the Main menu. The following message appears:
Enter one of [off, readonly, write] :
Step 2 Type the first letter of your selection and press Enter.
Step 3 Select the appropriate password option from the Configuration Console menu:
• Rpassword: for read-only privilege
• WPassword: for read/write privilege
• None: type this text string if no password is needed
Step 4 If you select RPassword or WPassword, the following message appears:
Enter one of [none, a password of between 5 and 10 characters] :
Step 5 Type your password and press any key. The following message appears:
Enter the password again, one of [none, a password of between 5 and 10 characters] :
Note After a privilege level is assigned, anyone attempting to access that level is prompted for the
password; therefore, you can set various privilege levels for individuals, providing them with access
to some options while denying them access to others. Remember that passwords are case sensitive.
If an incorrect password is typed, the console pauses briefly before reprompting. The connection is
dropped after three consecutive failures, and a severe error log is displayed.
Caution Make sure you write down the passwords you have established and keep them in a safe place. If you
forget your password, the bridge will have to be returned for factory servicing. Please contact Cisco
Technical Support for further instructions.
Caution The first MAC or IP address you add should be that of the PC you are using to Telnet or browse to
the bridge.
Display
Displays a list of MAC or IP addresses of any stations permitted to access the bridge remotely.
Add
Adds a host to the remote host list. You are prompted for the address of the host to add.
Delete
Removes a host from the remote host list. You are prompted for the address of the host to remove.
Note An error response is returned to the NMS if the NMS is trying a set request used with a community
that has Read Only access.
The Console does not automatically complete any typed commands or information when a space or
carriage return is inserted.
To enable linemode, choose Main > Configuration > Console > Linemode.
Note Some Telnet programs automatically invoke linemode by sending the appropriate Telnet commands
when they connect to the bridge.
Note You can also use the Config option to back up your configuration. See Chapter 11, “Performing
Diagnostics.”
This chapter describes the procedures for configuring the bridge’s radio network.
Here’s what you’ll find in this chapter:
• Using the Configuration Radio Menu, page 4-2
• Establishing an SSID (Ssid), page 4-2
• Selecting the Data Rate and Basic Rate (Rates, Basic_rates), page 4-2
• Setting the World Mode (World), page 4-2
• Using the Configuration Radio IEEE 802.11 Menu (I80211), page 4-3
• Using the Configuration Radio Link Tests Menu (Linktests), page 4-6
• Using the Configuration Radio Extended Menu (Extended), page 4-10
Caution Changes to radio parameters take effect immediately. If your Telnet or browser session is accessing
the bridge over a radio link, you might lose the session because the bridge may no longer be
associated to an access point on the network. If this happens, it may be necessary to change the access
point’s radio parameters to reestablish the radio link. You can also use a crossover cable to attach the
bridge to the Ethernet port on a PC to configure it.
The Key value establishes the WEP key the bridge uses to receive packets. The value must match the key
used by the access point. You can set two levels of encryption: 40-bit and 128-bit. The 40-bit key consists
of 10 hexadecimal characters. The 128-bit key consists of 26 hexadecimal characters. The hexadecimal
characters may be any combination of 0 through 9, a through f, or A through F. The WEP key can contain
combinations of any of these characters. Hexadecimal WEP keys are not case-sensitive.
To set the key, follow these steps:
Step 1 In the Privacy menu, choose Key. The following message appears:
Enter a number [ 1 to 4]:
Step 2 Enter the number of the key the bridge will use and press Enter. The following message appears:
Enter a key of hex digits:
Step 3 Enter the hexadecimal digits for the key (10 digits for 40-bit encryption or 26 digits for 128-bit
encryption) and press Enter. The following message appears:
Enter a key again:
Step 4 Enter the key again for confirmation and press Enter. After a few seconds, the Configuration Radio
I80211 Privacy prompt appears.
Step 5 Press Enter again to return to the Privacy menu.
The Transmit key establishes the WEP key the bridge will use to transmit packets. You can use the key
established when you set the key in the procedure above or you can use a different key. If you use a
different key, a matching key must be established on the access point.
Follow these steps to set the Transmit key:
Step 1 In the Privacy menu, choose Transmit. The following message appears:
Enter a number [ 1 to 4]:
The Auth parameter determines which authentication mode the system uses. Options are open or
shared_key. The following is an explanation of each mode:
• Open: allows any access point, regardless of its WEP setting, to authenticate and then attempt to
communicate with the bridge. Open is the default authentication mode.
• Shared_key: instructs the bridge to send a plain-text, shared-key query to any access point
attempting to communicate with the bridge. The shared-key setting can leave the bridge open to a
known-text attack from intruders, and it is therefore not as secure as the open setting.
To set the authorization mode, follow these steps:
Step 1 In the privacy menu, choose Auth and press Enter. The following message appears:
Enter one of [open, shared_key]:
Turning on Encryption
The Encryption option sets encryption parameters on all data packets except association packets and
some control packets. Options are off, on, mixed on, or mixed off. The access point must also have
encryption active and a key set properly. The following is an explanation of each option:
• Off: the default setting that turns off all encryption. The bridge cannot communicate with access
points that use WEP.
• On: requires all data transfers to be encrypted. The bridge only communicates with access points
that use WEP.
• Mixed on: means that the bridge always uses WEP when communicating with the access point but
that the access point communicates with all devices whether they use WEP or not.
• Mixed off: means that the bridge does not use WEP when communicating with the access point, but
the access point communicates with all devices whether they use WEP or not.
Caution If you select on or mixed on as the WEP category and you are configuring the bridge through its radio
link, you will lose connectivity to the bridge if the WEP key is set incorrectly. Be sure the WEP key
you set exactly matches the WEP key used on your wireless LAN.
Step 1 In the Privacy menu, choose Encryption. The following message appears:
Enter one of [off, on, mixed_on, mixed_off]:
Step 2 Enter the encryption option the bridge will use and press Enter.
Caution The WEP key you use to transmit data must be set to exactly the same value on your access point and
your bridge.
The time displays in milliseconds. Each packet contains the time it was sent. When a packet is received
by the source, the time difference indicates the round-trip time. Longer times indicate full bandwidth of
either the processor or the radio.
The signal strength and quality parameters report on the radio signal at the time the packets are received
at each end. Signal strength and quality are expressed in decibels referenced to an input signal of one
milliwatt of power (dBm) and as a percentage of full power.
The time displays in milliseconds. Each packet contains the time it was sent. When a packet is received
by the source, the time difference indicates the round- trip time. Longer times indicate full bandwidth of
either the processor or the radio.
The signal strength and quality parameters report on the radio signal at the time the packets are received
at each end. Signal strength and quality are expressed in decibels referenced to an input signal of one
milliwatt of power (dBm) and as a percentage of full power.
If the path to the target node was over the radio, the report displays the total number of radio retries
necessary to complete the test. A large number of retries indicates radio interference problems.
Rate (Rate)
The Rate option allows you to force the link test to transmit packets at only one of the allowed rates, or
you can select auto to use the highest allowed rate and rate-shift if necessary.
The Autotest procedure helps determine the placement of bridges. For example, at each prospective
location, an installer could cycle the power on the bridge and watch the indicator displays for the results
of the link test. As the test begins to fail, the installer could determine the radio range to the infrastructure
and adjust the location accordingly.
Diversity (Diversity)
The Diversity option enables the dual diversity feature of a bridge equipped with two antennas. This
option is not available for bridge models with one captured antenna. For bridge models with two
antennas installed, the Diversity setting defaults to on.
Caution If your bridge is equipped with one antenna, verify that the Diversity option is turned off and make
sure the antenna is attached to the connector nearest the power connector, as shown in the illustration
below. Attaching the antenna to the opposite connector will result in reduced operation.
Options (Options)
The Options feature is reserved for future system improvements.
This chapter describes the procedures for administering the devices attached to the bridge through its
Ethernet port.
Here’s what you’ll find in this chapter:
• Using the Configuration Ethernet Menu, page 5-2
• Enabling / Disabling the Ethernet Port (Active), page 5-2
• Setting the Maximum Ethernet Frame Size (Size), page 5-2
• Adding, Removing, and Displaying Client Node Addresses (Add, Remove, Display), page 5-2
• Determining the Bridge’s Idle Time (Staletime), page 5-3
• Overriding the Staletime Setting (Keep), page 5-3
Note After you change the parameter, you must restart the bridge by powering it off and then on or by
selecting Diagnostics > Restart.
Caution The first MAC address you add should be that of the PC you are using to Telnet or browse to the
bridge.
You should add MAC addresses if there are more than eight Ethernet devices attached to the hub to which
the bridge is connected. This ensures that the selected devices communicate through the bridge. After
an address is added, the bridge won’t learn any more addresses. You must type each MAC address you
wish to have communicate through the bridge (up to eight).
Once you enter the first MAC address, the MAC addresses of every other device that you want the bridge
to communicate with must be entered. The process is not automatic and the bridge will no longer “learn”
any addresses. The addresses must be manually entered.
Note The Keep option must be set to off to enable the Staletime option.
This chapter describes the procedures for setting the bridge’s network identifiers.
Here’s what you’ll find in this chapter:
• Using the Configuration Identity Menu, page 6-2
• Using the Internet Bootstrap Protocol and Dynamic Host Configuration Protocol (Bootp/DHCP),
page 6-2
• Establishing a Node Name (Name), page 6-3
• Configuring DHCP Servers (Class), page 6-3
• Assigning an IP Address (Inaddr), page 6-3
• Specifying the IP Subnet Mask (Inmask), page 6-3
• Specifying the Internet Default Gateway (Gateway), page 6-4
• Configuring the IP Routing Table (Routing), page 6-4
• Using DNS Server Names (DNS1), page 6-5
• Using DNS Server Names (DNS2), page 6-5
• Using Name Domains (Domain), page 6-5
• Setting SNMP Location and Contact Identifiers (Location, Contact), page 6-5
Note The current configuration is not set back to the defaults before the file is processed. Therefore, the
file contents do not have to be a complete configuration but can just contain the items to be changed.
Once the configuration is processed, the name stored in the diagnostics load FTP filename parameter is
assumed to be the name of a firmware file to download. If the parameter is not empty, the bridge uses
the TFTP protocol to load the file into RAM.
If the firmware is different from the current version, the bridge programs the flash memory with the new
code and restarts to execute it. If the firmware is the same, the bridge discards the loaded file and
continues normal operation.
If the destination IP address exactly matches a host entry in the routing table, the packet is forwarded to
the MAC address corresponding to the next-hop IP address from the table entry.
If the destination address is on another subnet and matches the infrastructure portion of a net entry in the
table (using the associated subnet mask), the packet is forwarded to the MAC address corresponding to
the next-hop IP address from the table entry.
If the destination address is on another subnet and does not match any entry in the table, the packet is
forwarded to the MAC address corresponding to the default gateway’s IP address.
Routing Table
Destination Next Hop Mask Flags Use
---------------- --------------- --------------- ------ ---
149.023.166.000 149.023.165.071 255.255.255.000 S N 0
default 149.023.165.050 000.000.000.000 S N 0
149.023.130.020 149.023.165.060 255.255.255.000 S H 0
The Use column indicates the number of packets that have been forwarded using this table entry.
In the sample table, all addresses that match 149.23.166.xxx are forwarded to the router at address
149.23.165.71. Any packet for address 149.23.130.20 is forwarded to the address 149.23.165.60. All
other packets not on the current subnet are forwarded to the router at 149.23.165.50.
This chapter describes how to use the Statistics menu to monitor the performance of the Workgroup
Bridge.
Here’s what you’ll find in this chapter:
• Viewing the Statistics Menu, page 7-2
• Viewing Throughput Statistics (Throughput), page 7-2
• Viewing Error Statistics (Radio), page 7-3
• Viewing Error Statistics (Ethernet), page 7-4
• Displaying Overall Status (Status), page 7-5
• Displaying the Network Map (Map), page 7-6
• Recording a Statistic History (Watch), page 7-6
• Displaying a Statistic History (History), page 7-7
• Displaying Node Information (Nodes), page 7-8
• Displaying ARP Information (ARP), page 7-8
• Setting Screen Display Time (Display_time), page 7-9
• Decrypt errors: packets were received without errors but could not be decrypted with available
encryption keys.
• Retries: cumulative count of the number of times a frame had to be retransmitted because an
acknowledgment was not received.
• Max retries / frame: maximum number of times any one frame had to be retransmitted. Excessive
retries may indicate a poor quality radio link.
• Excessive retries: number of times a packet has taken four or more retries before it was successfully
transmitted.
• Queue full discards: number of times a packet was not transmitted because of too many retries to
the same destination. Discards only occur if packets destined to this address are taking up more than
their share of transmit buffers.
• Holdoffs: indicates that another node was transmitting when this node tried to start a transmit of its
own. This is a usual occurrence but a high rate of holdoffs is an indication of a congested cell.
• Holdoff timeouts: indicates that a transmission was held off by other activity longer than the length
of time it would take to transmit the longest allowed 802.11 packet. This is usually an indication of
some sort of outside interference.
• Frame alignment errors: number of frames received whose size in bits was not a multiple of 8.
Occasionally, extra bits of data are inadvertently attached to a transmitted packet causing a frame
alignment error.
• Over-length frames: number of frames received that are longer than the configured maximum
packet size.
• Short frames: number of frames received that are shorter than the allowed minimum packet size of
64 bytes.
• Overruns: number of times the hardware receive FIFO buffer overflowed. This should be a rare
occurrence.
• Misses: number of Ethernet packets that were lost because of a lack of buffer space on the bridge.
• Excessive Collisions: number of times transmissions failed because of excessive collisions. Usually
indicates the frame had to be continuously retried because of heavy traffic on the Ethernet
infrastructure.
• Deferrals: number of times frames had to wait before transmitting because of activity on the cable.
• Excessive deferrals: number of times the frame failed to transmit because of excessive deferrals.
This error usually indicates the frame had to be continuously retried because of heavy traffic on the
Ethernet infrastructure.
• No carrier sense present: number of times the carrier was not present when a transmission was
started. This error usually indicates a problem with a cable on the Ethernet infrastructure.
• Carrier sense lost: number of times the carrier was lost during a transmission. This error usually
indicates a problem with a cable on the Ethernet infrastructure.
• Out of window collisions: number of times a collision occurred after the 64th byte of a frame was
transmitted. Out of window collisions usually indicate a problem with a cable on the Ethernet
infrastructure.
• Underruns: number of times the hardware transmit FIFO buffer became empty during a transmit.
Underruns should be a rare occurrence.
• Bad length: number of times an attempt was made to transmit a packet larger than the specified
maximum allowed.
Step 1 Choose Main Menu > Statistics > Watch. The following menu appears:
Step 3 Type the applicable statistic index number and press Enter. The following prompt appears:
Enter a sample time in seconds from 1 to 3600 :
This chapter describes the procedures for setting up and viewing the association table for the bridge.
Here’s what you’ll find in this chapter:
• Overview, page 8-2
• Using the Association Menu, page 8-2
• Displaying the Association Table (Display), page 8-2
• Specifying How Node Addresses are Displayed (Niddisp), page 8-3
Overview
Data in the association table keeps track of the bridge’s network status. The association table identifies
the parent device and the clients for which the bridge is passing data. Table data includes address, device,
association type, and ASCII name.
This chapter describes how to use filters to improve the performance of your bridge.
Here’s what you’ll find in this chapter:
• Overview, page 9-2
• Using the Filter Menu, page 9-2
• Filtering Multicast Addresses (Multicast), page 9-2
• Filtering Node Addresses (Node), page 9-3
• Filtering Protocols (Protocol), page 9-4
• Accessing Packet Direction (Direction), page 9-8
Overview
If your bridge is connected to an infrastructure with a large amount of multi-protocol traffic, you may
be able to reduce the amount of radio traffic by blocking out (filtering) unneeded addresses or protocols.
Filtering is especially important for battery-operated radio nodes that might otherwise have to waste
considerable battery power receiving irrelevant multicast messages.
If protocol monitoring is enabled, when you select add, the current monitor table is displayed. Follow
these steps to select a monitored protocol:
Step 1 Type the desired filter protocol’s number that is displayed at the start of each line of the monitor display.
If the monitored protocol was unrecognized and was not given a name, you are prompted to assign a
name.
Step 2 Type the action to take when the protocol is encountered: discard, forward, high_priority or log, and
press Enter.
Step 1 Type add and give the filter a name that does not start with a number and does not match one of the
predefined names.
Step 2 Type the action to take when the protocol is encountered: discard, forward, high_priority or log, and
press Enter. The following message appears:
Enter one of [protocol, snap+protocol, llc]:
Step 3 Choose whether the protocol is defined by an Ethernet or SNAP+protocol identifier or by an LLC header.
If you type protocol:
a. The following prompt appears:
Type a value in hex from 200h to ffffh:
Type the value for the protocol identifier to be filtered and press Enter. The following prompt
appears:
Type one of [a mask start position, none]:
The protocol identifier value allows you to specify a bit mask and corresponding hexadecimal value
to be applied to the packet. These two values must match the packet contents before the protocol is
identified. You must first specify a mask start position in the packet and match the mask value. The
mask start position value should be a 0-based byte offset from the start of the data portion of the
frame (after the MAC layer header). If you set the position to none, no mask is tested.
b. Type a mask start position value (or none, if applicable) and press Enter. The following prompt
appears:
Type a hex value of 1 to 30 characters:
c. Type the value to be matched as a string of up to 30 hexadecimal digits and press Enter. If the
numbered digits are odd, the mask value is adjusted to ignore the lowest 4 bits of the corresponding
byte. Then the following prompt appears:
Type a hex don’t care mask of 1 to 6 characters:
This value allows you to type a string of hexadecimal digits to indicate which bits of the packet data
are meaningful. A bit set in this value causes the corresponding bit in the packet to be ignored.
Therefore, a 0 mask means that the packet contents must exactly match the previous value typed. If
the mask entered is shorter than the value entered it is automatically extended to the correct length
with zeros.
d. Type the applicable hexadecimal digits and press Enter.
For example, to type a mask that matches the value 4128H in the 16th byte data portion of the packet
and have the high bit of each byte ignored, complete as follows:
Type one of [a mask start position, none]: 15
Type a hex value of 1 to 30 characters: 4128
Type a hex don’t care mask of 1 to 6 characters: 8080
a. Type a 16-bit value for the DSAP/SSAP combination (with the DSAP being in the high 8 bits) and
press Enter. The following prompt appears:
Type one of [a OUI value in hex of ffffffh or less, any]:
This value is used to specify an OUI value to further refine the protocol identification.
If you type a OUI value in hex of ffffffh or less, it must match the protocol field in addition to the
SAP value.
If you type any, the protocol values are not checked and the protocol is defined only by the SAP
values.
b. Type the applicable OUI value or any and press Enter.
If you typed an OUI value, the following prompt appears:
Type one of [a LLC protocol value in hex of ffffh or less, any]:
c. Type the applicable LLC protocol value or any and press Enter. You are then prompted for a mask
description as described below.
If you type a LLC protocol value in hex of ffffh or less, the mask must match the protocol field in
addition to the SAP and OUI values.
If you type any, the protocol values are not checked and the protocol is defined only by the SAP and
OUI values.
Use the Logs menu to set up and view event logs on the bridge.
Here’s what you’ll find in this chapter:
• Event Logs, page 10-2
• Using the Logs Menu, page 10-3
• Severe Error Log, page 10-3
• Viewing the History Log (History), page 10-4
• Clearing the History Buffer (Clear), page 10-4
• Specifying the Type of Log to Print (Printlevel), page 10-5
• Specifying the Type of Log to Save (Loglevel), page 10-5
• Specifying the Type of Event to Light Status Indicators (Ledlevel), page 10-5
• Setting Statistic Parameters (Statistics), page 10-5
• Logging Network Roaming (Network), page 10-6
• Backbone Nodes (Bnodelog), page 10-6
• SNMP Traps (Snmp), page 10-7
• Forwarding Events to a UNIX System (Syslog, SysLevel, Facility, Rcvsyslog), page 10-8
Event Logs
The bridge produces logs that record significant events occurring within your bridge and on the
infrastructure. The type of logs include the following:
• Information log: records status changes that occur in the normal operation of the system. For
example, when an end node associates to a parent access point.
• Error log: records errors that occur occasionally, but which are easily recovered from by the bridge.
For example, errors that occur during the reception and transmission of packets to and from the
bridge.
• Severe error log: records errors that drastically affect the operation of the system. The system
continues to run, but action is required to return the bridge to normal operating standards.
Information Log
The following events appear in the Information log:
• BOOTP/DHCP set new IP address: the BOOTP/DHCP server answered the request and assigned
the bridge an IP address different from the configured value.
• Node “node address” “device name” added: a nonvolatile entry was added to the association table.
• Node “node address” “device name” “ASCII name” removed, max radio retries: a node was
removed from the table because a response was not received from the node after attempts were made
to transmit a packet to it. The node may have failed or moved to another cell.
• RARP set new IP address: a Reverse Address Resolution Protocol (RARP) server answered a
request for an IP address with an address different from the one currently saved. The currently saved
value is overwritten.
• Connected to parent “node address”: The bridge associated to its parent node.
• SNMP: “command text”: a SNMP management station sent the bridge a set variable request which
was successfully executed. The command text is a similar menu command that has the same effect
as the SNMP request.
• SNMP access failure from “community name” “IP address” (node address): a SNMP
management station attempted to access the SNMP agent with an invalid community name or a name
that it was not allowed to use.
• TFTP is loading “file name” from “ip address”: the BOOTP server gives the bridge the name of
a configuration file and then the name of a firmware file to load.
Error Log
The following events appear in the Error log:
• “Category” Error: nnn “type” errors: an error occurred that is marked by an asterisk * after its
count in the statistics displays. These errors are serious enough to affect the operation of the bridge.
See the sections on each display for an explanation of each error.
• Unable to locate IP address “ip address”: the bridge was trying to send a packet to an IP address
without knowing the hardware node ID. When this occurs, the bridge uses the ARP protocol to try
to determine the proper address. This event is logged if there was no answer to the ARP request.
Usually the bridge is trying to find the destination for the SNMP traps.
Note If a power failure occurs, events contained in the memory are not saved.
OLDEST
0:00:00 I Node 004096109e30 APBR2000-E Floor_2_109e30 added locally
0:00:03 I Node 0040961064de AP2000-E F3_1064de added for 004096109e30
30:35:09 NEWEST, cleared at 0:00:00
b[ackward], f[orward], n[ewest], o[ldest], a[ll], C[lear], q[uit] :
Enter your statistics category choice. Enter the number or the short form. The short form is used to store
the command in the configuration.
Step 3 The menu of the types of statistics for your chosen statistics category appears. For example, if you enter
1_ ra Radio, the following menu appears:
Step 4 If any of the statistics already have an alarm associated, the current setting is displayed after the name.
Enter a category number or the short form of the particular statistics that you wish to change and press
Enter. The following prompt appears:
Enter an action, one of [off, any, rate]:
Note Since the path to the trap destination may be through a failed or not yet established radio link, it is
possible that cold start and link down traps could be lost.
The generated trap contains the text of the event message along with the severity of the event. The
different severities are:
• Error/severe: displays all errors and severe errors.
• Severe: displays severe errors only.
• All: displays all errors, severe errors and information.
• Off: no events are displayed.
By default, the bridge receives and displays syslog messages from other bridges in the network. The
Rcvsyslog option enables or disables this function. You could choose one bridge to monitor and have all
other units configured with this bridge as their syslog host.
This chapter describes how to use the Diagnostics menu to maintain the bridge.
Here’s what you’ll find in this chapter:
• Using the Diagnostics Menu, page 11-2
• Using the Network Menu (Network), page 11-2
• Running a Link Test (Linktests), page 11-3
• Restarting the Bridge (Restart), page 11-3
• Returning the Bridge to the Default Configuration (Defaults/Reset), page 11-4
• Loading New Code Versions (Load), page 11-4
After connecting, you can close a Telnet session and return to the local console by:
• Entering the escape sequence of characters as defined by the Escape option in the Diagnostics menu.
See “Changing the Escape Sequence” below.
• If the remote node is a Cisco Aironet node, choose the Close option which is accessible on the Main
menu during a Telnet session only.
• Using the remote node’s logout command.
Note Before you download or upload new code versions, make sure you have set the IP address on all
bridges involved.
When you select the Ftp option, the Diagnostics Load FTP menu appears:
Navigation: Choose Main > Diagnostics > Load > Ftp
Use the Get option to download (retrieve) firmware or a configuration file. After the file loads, the bridge
checks the first characters of the file. If !CONFIGURATION is present, the file contains menu
configuration commands. Otherwise, the file is considered to be firmware and is loaded in Flash memory
and executed. Follow these steps:
Step 1 Load the file onto the PC, host, or bridge from which you will retrieve the firmware.
Step 2 Choose the Dest option and enter the IP address of the host PC or bridge.
Step 3 Choose the Username option and enter the username required to access the firmware file.
If downloading from another Cisco Aironet bridge, the Username option must have a value even though
the value is not used by the remote bridge.
Step 4 Choose the Password option and enter the password associated with the username.
If downloading from another Cisco Aironet bridge, the login password value must match the console
write privilege password on the remote bridge.
Step 5 Choose the Filename option and enter the name of the firmware file you are retrieving (including drive
and directory), then press Enter.
If downloading from another Cisco Aironet bridge, the Filename option must have a value even though
the value is not used by the remote bridge.
Step 6 Choose the Get option.
The bridge begins an FTP session to the host PC, retrieves the file, programs the Flash memory and
reboots. A message similar to the following is displayed.
Use the Put option to upload (send) a copy of the currently running firmware to another system. If the
system is a PC or host, a copy of the firmware is stored on the system’s disk, possibly for downloading
to other bridges later.
If the system is a Cisco bridge, the remote bridge flashes the new code and begins running it
immediately. You can use one bridge to upgrade another bridge. Follow these steps:
Step 1 Choose the Dest option and enter the IP address of the remote PC, host, or bridge you are sending to and
press Enter.
Step 2 Choose the Username option and enter the username for the remote PC, host, or bridge you are sending
to and Press Enter.
If you are uploading to another Cisco bridge, the Username option must have a value even though the
value is not used by the remote bridge.
Step 3 Choose the Password option and enter the access password for the remote PC, host, or console. Press
Enter.
Step 4 Choose the Filename option and enter the name of the firmware file you are sending to the PC, host, or
bridge (including drive and directory) and press Enter.
If uploading to another Cisco bridge, the Filename option must have a value even though the value is not
used by the remote bridge.
Step 5 Choose the Put option. The bridge begins an FTP session to the remote PC host or bridge.
The Config option saves the configuration on a remote host or PC in a format suitable for later
downloading using FTP or BOOTP.
You are first prompted for the name of the file to be created on the remote system. You are then prompted
to choose All, Non-default, or the Distributable configuration options:
• All: sends every configuration item.
• Non-default: sends only those configuration items that have been modified from their default
values.
• Distributable: sends the configuration items that can be distributed to other bridges.
The file transfer begins after you choose the configuration file type.
The Diagnostics Load Distribute menu provides a range of options for distributing firmware or
configuration from one bridge to all other bridges on the infrastructure. These options reduce the time
needed to perform firmware upgrades or make global changes to the configuration.
If you are distributing a configuration, examine the parts of the bridge’s configuration that will be
distributed by choosing Main > Configuration > Dump > Distributable > Standard.
The Go option starts the distribution. The following message appears:
Finding the other units ....
When the command executes, the local bridge sends a special broadcast message to all other bridges in
the radio infrastructure. The message reports that the bridge has a new firmware file with its assigned
version number or a configuration file.
The remote bridges then determine whether to respond based on the value of their control parameter.
Any responses are displayed on the local bridge similar to the following message.
AIR-WGB340 004096285e73 has code version 8.36 (checksum 1829)
When the local bridge receives a response to its request, the remote bridge is added to a list of bridges
to be loaded. When the response time-out period has expired, the local bridge begins loading all remote
bridges in parallel using a proprietary protocol. A message similar to the following is displayed.
Loading 004096001d45
Loading 00409610345f
If any remote bridges timeout during the load, they are removed from the list. After all bridges finish
loading, the local bridge displays a count of the successful loads. A message similar to the following is
displayed.
Completed loading 004096001d45
Completed loading 00409610345f
Loading of 2 Workgroup Bridges completed
The Type option selects the file type to be distributed. Choices are firmware or configuration.
The Control option controls how the remote bridges respond to a request to send a configuration or
firmware. You can choose from the following options:
• None: the bridge never responds and cannot be loaded by another bridge using the distribute
command.
• Newer: the bridge only responds if the version of firmware being distributed has a larger version
number than the code currently running. This selection applies only to firmware downloads.
• Any: the bridge always responds. It is up to the distributing bridge to determine whether to load the
local bridge.
• A password of at most 8 characters: a password that must be typed by the operator of the bridge
doing the distribution. The local bridge will not respond to any distributions that do not supply this
password.
If the distribution is password protected, only those bridges that have the same password configured in
the control parameter accept the distribution. Therefore, the bridges can be protected from unwanted
loads. The password may also be used to divide the bridges into code load groups such that the loads to
one group do not affect the other groups.
If the distribution is done without a password, the load is ignored by remote bridges with a configured
password. If a remote bridge does not have a password and firmware is being distributed, it only accepts
the load based on the version number and code checksum.
The Add option changes the distributable configuration. Each line of the configuration carries a
designation either send or local. After typing the encoded configuration ID, type either send or local to
change the assigned designation and press Enter twice to apply the change.
The Remove option reverses the most recent change. You can choose between reversing the change made
to a single encoded configuration ID or typing all to reverse all designations.
The Show option lists the changes made to configuration items.
The Dump option displays the complete configuration.
Radio Characteristics
Table A-2 Radio Characteristics
Characteristic Description
Frequency 2.400 to 2.497 GHz
Modulation Direct Sequence Spread Spectrum
Antenna Standard is single captured antenna.
Option is two RP-TNC diversity connectors to install
remote antennas.
Power Output 340 series: 1 to 30 mW
350 series: 1 to 100 mW
Compliance Operates license-free under FCC Part 15 and
complies as a Class B computing device. Complies
with DOC regulations.
Complies with ETS 300.328, FTZ 2100 and MPT
1349 standards (and others).
Physical Specifications
Table A-3 Physical Specifications
Specification Description
Size 20 x 15 x 5 cm (7.8 x 5.9 x 1.9 in.)
Status indicators Top panel: radio traffic activity, Ethernet traffic
activity, status
Back panel (Ethernet only): Ethernet Rx and Tx
activity, polarity
Power supply Power pack. The power pack is either 120VAC/60Hz
or 90–264VAC/47–63Hz, whichever is appropriate
for country of use.
Weight 0.7 kg (1 lb 8 oz)
Operating environment –20°c to 50°C (–4°F to 122°F)
The console system consists of multiple sub-menus that branch off the Main menu, much like a tree. This
appendix provides you with a detailed listing of all menus, sub-menus, and options contained in the
console system.
Main Menu
Main Menu
45014
Configuration Menu
Main Menu
Configuration
45010
Autotest
Continuous
Statistics Menu
Main Menu
Statistics
Throughput
Radio
Ethernet
Status
Map
Watch
History
Nodes
ARP
45015
Display_time
Association Menu
Main Menu
Association
Display
45009
Niddisp
Filter Menu
Main Menu
Filter
45012
Show
Clear
Logs Menu
Main Menu
Logs
History
Clear
Printlevel
Loglevel
Ledlevel
Statistics
Network
Bnodelog
Snmp
Trapdest
Trapcomm
Loglevel
Authtrap
Syslog
Syslevel
Facility
45013
Rcvsyslog
Diagnostics Menu
Main Menu
Diagnostics
45011
Dump
entering 6-5
F
Inmask option 6-3
Facility option 10-8 Internet default gateway, specifying 6-4
failure to associate 7-5 IP address 6-3
File Transfer Protocol (FTP) 11-4 IPdisplay option 9-4
filtering protocols 9-4 to 9-8 IP routing table, configuring 6-4
Filter menu 9-2 to 9-8 IP subnet mask, specifying 6-3
Find option 11-3
firmware
distributing 11-7
K
downloading new version 11-5 Keep option 5-3
uploading new version 11-6
Fragment option 4-11
L
fragment size, setting 4-11
FTP option 11-4 Ledlevel option 10-5
Length option 9-8
Linemode option 3-7
G
link test, continuous 4-9
Gateway option 6-4 link tests 4-6
Get option 11-5 Linktests option
Configuration Radio menu 4-6
Diagnostics menu 11-3
H
Load option 11-4
history buffer, clearing 10-4 Location option 6-5
history log, viewing 10-4 Loglevel option 10-7
History option logs
Logs menu 10-4 specifying event to light LEDs 10-5
Statistics menu 7-7 specifying type to print 10-5
Host option 6-5 specifying type to save 10-5
host route, entering 6-5 Logs menu 10-3 to 10-8
I M
IEEE 802.11 menu 4-3 to 4-6 MAC address
Inaddr option 6-3 adding 5-2
information logs 10-2 displaying 5-3
infrastructure defined 1-3 removing 5-3
infrastructure route Main menu 2-2 to 2-4
deleting 6-5 Map option 7-6