User manual

SM User Manual January 2004
Software Release 4.1
2 ABOUT THIS DOCUMENT
The following information describes the purpose of this document and the reasons for reissue.
2.1 INTENDED USE
This manual includes Canopy features through Software Release 4.1. The audience for this
manual comprises system operators, network administrators, and equipment installers. The user
of this manual should have
basic knowledge of RF theory. (See General RF Considerations on Page 48.)
network experience. (See General IP Addressing Concepts on Page 66.)
2.2 NEW IN THIS ISSUE
This document has been revised to include changes in technical content.
Issue 5 introduces the following changes:
Rearrangement of topics to make the document easier to return to as a reference
source.
Editorial changes to reduce redundancy and clarify technical concepts.
Revision of the warranty stated in the legal section above (effective for products
purchased on or after October 1, 2003).
Information that supports 2.4-GHz Canopy modules. See
Types of SM Applications on Page 16.
Selection of SM Types and Passive Reflectors on Page 47.
Channel Plans on Page 58.
Table 11 on Page 70.
Custom RF Frequency Scan Selection List on Page 87.
SM MODULE SPECIFICATIONS on Page 117.
Reminders to observe local and national regulations.
Description of the Canopy Bandwidth and Authentication Manager (BAM) and BAM
features, which provide bandwidth and security above what an AP without the BAM
provides. See Bandwidth and Authentication Manager (BAM) on Page 22.
Examples of interactions between burst data rate and sustained data rate settings. See
Interaction of Burst Data and Sustained Data Settings on Page 23.
A Configuration page selection in the AP that allows multiple APs to send beacons to
multiple SMs in the same range without interference. See Transmit Frame Spreading
on Page 26.
More logical telnet session for branding the interface screens. See Figure 11
on Page 28.
Procedures to deny or permit remote access to an SM. See Denying All Remote
Access on Page 28 and Reinstating Remote Access Capability on Page 29.
Issue 5 Page 13 of 119