Trilliant Networks DBE1010 Tri-Band 2.4GHz/5Ghz Wireless LAN User Manual SkyExtender TriBand Installation and Setup

Download:
Mirror Download [FCC.gov]
Document ID	705359
Application ID	bXvqUFKXbsj9dkIqeJNhUg==
Document Description	Manual
Short Term Confidential	No
Permanent Confidential	No
Supercede	No
Document Type	User Manual
Display Format	Adobe Acrobat PDF - pdf
Filesize	30.83kB (385340 bits)
Date Submitted	2006-09-15 00:00:00
Date Available	2006-09-15 00:00:00
Creation Date	2006-06-12 11:59:34
Producing Software	Acrobat Distiller 7.0.5 (Windows)
Document Lastmod	2006-09-13 14:55:43
Document Title	SkyExtender TriBand Installation and Setup
Document Creator	FrameMaker 7.2
Document Author:	SkyPilot Networks

SkyExtender TriBand Installation and Setup
671-00006-01 Rev B
© 2006 SkyPilot Networks, Inc. All rights reserved
This publication, or parts thereof, may not be reproduced in any form, by any method, for any purpose.
Product specifications are subject to change without notice. This material is provided for informational purposes only; SkyPilot assumes no liability related
to its use and expressly disclaims any implied warranties of merchantability or fitness for any particular purpose.
SkyPilot Trademarks
SkyConnector, SkyControl, SkyExtender, SkyGateway, SkyPilot, SkyPilot Networks, SkyProvision, and the SkyPilot logo are the trademarks and registered trademarks of
SkyPilot Networks, Inc.
Third-Party Trademarks
Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.
MySQL is a registered trademark of MySQL AB in the United States, the European Union, and other countries.
All other designated trademarks, trade names, logos, and brands are the property of their respective owners.
Third-Party Software Program Credits
This product includes software developed by the Apache Software Foundation (http://www.apache.org/), licensed under the Apache License.
This product includes the DHCP Server software from Internet Systems Consortium, licensed under the DHCP License. The DHCP Server software is copyright © 2004
Internet Systems Consortium, Inc. (“ISC”). Copyright © 1995–2003 Internet Software Consortium. All rights reserved. Redistribution and use in source and binary forms,
with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of ISC, ISC DHCP, nor the names of its contributors may be
used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY INTERNET SYSTEMS
CONSORTIUM AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL ISC OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes the FTP Server software from vsftpd (http://vsftpd.beasts.org/), licensed under the GNU General Public License.
This product includes Java software from Sun Microsystems, licensed under Sun Microsystems' Binary Code License Agreement. Copyright 2003, Sun Microsystems, Inc.
All rights reserved. Use is subject to license terms. Sun, Sun Microsystems, the Sun logo, Solaris, Java, the Java Coffee Cup logo, J2SE, and all trademarks and logos based
on Java are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.
This product includes JBOSS Version 3.2.3 software from JBoss, licensed under the GNU Lesser General Public License. Some bundled products in JBOSS are licensed
under the Apache License.
This product contains Java Telnet Application (JTA 2.0).
This product contains the MibBrowser software from Mibble.
This product includes software the copyright of which is owned by and licensed from MySQLAB.
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/). Copyright (c) 1998–2005 The OpenSSL
Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are
met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must
reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.
3. All advertising materials mentioning features or use of this software must display the following acknowledgment: “This product includes software developed by the
OpenSSL Project for use in the OpenSSL Toolkit. (http://www.openssl.org/)” 4. The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to endorse or
promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org. 5. Products derived
from this software may not be called “OpenSSL” nor may “OpenSSL” appear in their names without prior written permission of the OpenSSL Project. 6. Redistributions of
any form whatsoever must retain the following acknowledgment: “This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit
(http://www.openssl.org/)”. THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT
OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes libraries developed by Eric Young and is licensed under the Original SSLeay License. This product includes cryptographic software written by Eric
Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com). Copyright (C) 1995–1998 Eric Young (eay@cryptsoft.com). All
rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1.
Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the
above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All
advertising materials mentioning features or use of this software must display the following acknowledgement: “This product includes cryptographic software written
by Eric Young (eay@cryptsoft.com)” The word 'cryptographic' can be left out if the routines from the library being used are not cryptographic related :-). 4. If you include
any Windows specific code (or a derivative thereof ) from the apps directory (application code) you must include an acknowledgement: “This product includes
software written by Tim Hudson (tjh@cryptsoft.com)”. THIS SOFTWARE IS PROVIDED BY ERIC YOUNG ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR
OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE,
EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This product includes SNMP software from WestHawk, licensed under the WestHawk License.
This product includes JFreeCharts from http://www.jfree.org/, licensed under GNU Lesser General Public License.
This product includes JasperReports from http://jasperreports.sourceforge.net/index.html, licensed under GNU Lesser Public License.
GOVERNMENT USE
The following provision applies to United States Government end users. This product is comprised of “commercial computer software” and “commercial computer
software documentation” as such terms are used in 48 C.F.R. 12.212 and are provided to the Government (i) for acquisition by or on behalf of civilian agencies,
consistent with the policy set forth in 48 C.F.R. 12.212; or (ii) for acquisition by or on behalf of units of the Department of Defense, consistent with the policies set forth
in 48 C.F.R. 227.7202-1 and 227.7202-3.
SkyPilot Firmware 1.3
Document Last Revised: June 12, 2006
Contents
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v
Audience and Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi
How This Guide Is Organized . . . . . . . . . . . . . . . . . . . . . . . . . vi
Conventions Used in This Guide . . . . . . . . . . . . . . . . . . . . . . .vii
Chapter 1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
TriBand Topologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Default Access Point Configuration . . . . . . . . . . . . . . . . . . . . . 2
Chapter 2
Your SkyExtender TriBand Kit . . . . . . . . . . . . . . . . . . 3
Kit Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 3
Installing SkyExtender TriBand . . . . . . . . . . . . . . . . . 7
Planning Your Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Mounting and Cabling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Powering Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 4
Configuring a SkyExtender TriBand . . . . . . . . . . . . . .13
Before You Begin . . . . . . . . . . . . .
Choosing a WLAN Configuration . . .
Automatic vs. Manual Configuration
Preparing Software Images . . . . . .
Automatic Provisioning Procedure. .
Manual Provisioning Procedure. . . .
Appendix A
14
14
16
17
17
21
FCC Statements . . . . . . . . . . . . . . . . . . . . . . . . . . .23
SkyExtender TriBand Installation and Setup | iii
iv
About This Guide
This guide provides directions for installing and setting up a SkyPilot™
SkyExtender™ TriBand which can provide access point services to users of
802.11b/g wireless (Wi-Fi) networks.
Chapter Highlights
Audience and purpose
How this guide is organized
Conventions used in this guide
SkyExtender TriBand Installation and Setup | v
Audience and Purpose
This guide provides directions for installing and setting up a SkyPilot™ SkyExtender
TriBand that can provide access point services for users of 802.11b/g wireless
(Wi-Fi) Networks.
This guide assumes administrator-level knowledge of IP networks and a familiarity
with configuring wireless devices.
How This Guide Is Organized
This guide is organized as follows:
Chapter 1, “Introduction,” provides an overview of the SkyExtender TriBand,
including its topologies and default access point configuration.
Chapter 2, “Your SkyExtender TriBand Kit,” provides information you need
before you begin your installation.
Chapter 3, “Installing SkyExtender TriBand,” provides instructions for the
physical installation of the TriBand.
Chapter 4, “Configuring a SkyExtender TriBand,” explains how to use SkyPilot
EMS software to configure the TriBand for both mesh networking and Wi-Fi
operation.
Appendix A, “FCC Statements,” provides the FCC radio frequency interference
statements for the SkyGateway, SkyExtender, SkyExtender DualBand, and
SkyExtender TriBand devices.
vi | About This Guide
Conventions Used in This Guide
This section describes the text and syntax conventions used throughout this
guide.
Text Conventions
This guide uses the following text conventions:
Italic is used to introduce new terms.
Bold is used to indicate what you click or type in a graphical user interface (for
example, commands names or text being entered). In examples showing user
interaction with the command-line interface, bold is used to indicate user
input as opposed to command output.
A monospace font is used for code elements (variable names, data values,
function names, and so forth), command lines, scripts, and source code
listings.
Italic-monospace is used for replaceable elements and placeholders
within code listings.
Syntax Conventions
This guide uses the following conventions when showing syntax:
Angle brackets, “<“ and “>”, enclose mandatory elements. You must enter
these elements. For example:
ping 
Square brackets, “[“ and “]”, enclose optional elements. You can omit these
elements. For example:
show filter [filter-table-number]
Square brackets are also used to show the current value of parameters in the
output of some commands.
A vertical bar, “|”, separates choices. For example:
show bridge [cache | port]
Conventions Used in This Guide | vii
viii
1
Introduction
SkyExtender TriBand is a dual-radio solution that combines SkyPilot’s long-range,
high-capacity 5 GHz mesh backhaul with high-powered 2.4 GHz 802.11b/g and
4.9 GHz 802.11a access points that allow service providers and municipalities to
offer standard Wi-Fi services over great distances—for targeted hot zones or
dense, ubiquitous coverage patterns. With the ability to create multiple WLANS,
each with its own VLAN and security policy, the SkyExtender TriBand can support
several business models with a single service installation.
Chapter Highlights
TriBand topologies
Default access point configuration
SkyExtender TriBand Installation and Setup | 1
TriBand Topologies
SkyExtender TriBand provides a unique opportunity for WISPs (wireless ISPs)
looking to combine scalable Wi-Fi capacity with the seamless coverage of a
wireless mesh network.
TriBand nodes on a wireless mesh network offer a basis for multi service networks
capable of providing end-to-end security and quality of service for a variety of
bandwidth-hungry applications and services, including VoIP and video
surveillance solutions.
The auto-discovery and rapid provisioning features of a SkyPilot wireless mesh
network can greatly reduce deployment and maintenance costs. Multiple
topology options and network scalability create intriguing options for rapidly
growing a metro Wi-Fi customer base.
Default Access Point Configuration
The SkyExtender TriBand access point is set up to provide Wi-Fi access right out of
the box. The access point includes a preconfigured WLAN with the SSID (Service
Set Identifier) SkyPilotTriBand, providing WPA-PSK (Wireless Protected
Access–Pre-Shared Key) protection. The first time that users attempt to connect to
the SkyPilotTriBand WLAN, they must provide a public password,
publicpublic.
You have the option of leaving the default configuration in place or creating a
new configuration for the access point.
NOTE
A wireless network protected by WPA-PSK is vulnerable. To provide a
more secure level of protection, configure the WLAN for WPA
authentication, in which each user is authenticated separately.
2 | Chapter 1 Introduction
2
Your SkyExtender TriBand Kit
Your SkyPilot SkyExtender TriBand kit provides everything you need to install the
device and configure it as both an extender for your wireless mesh network and
an integrated 802.11b/g Wi-Fi access point.
Chapter Highlights
Kit contents
Before you begin
Getting help
SkyExtender TriBand Installation and Setup | 3
Kit Contents
The SkyPilot SkyExtender TriBand kit includes:
The SkyPilot SkyExtender TriBand
One 2.4 GHz antenna
One 4.9 GHz antenna
A PoE (Power over Ethernet) adapter for powering the SkyExtender TriBand
Before You Begin
Before starting installation, you need the following:
A computer connected to the same network as the SkyExtender TriBand
(which by default is IP address 192.168.0.2).
A CAT-5 straight-through Ethernet cable for connecting the TriBand to a
power source.
Setup information for the access point:

A (case-sensitive) wireless SSID for each virtual WLAN Wi-Fi network.

A unique IP address for the management of the access point if it’s not
connected to a DHCP server.

A default gateway and subnet mask for the management network if the
access point is not on the same subnet as your PC.

MAC addresses for the TriBand and for the WLANs you set up for the
access point.
Each TriBand has 32 MAC addresses assigned to it. The MAC address of
the TriBand’s 5 Ghz radio (as seen from the SkyGateway™) is printed on
the label affixed to the bottom of the TriBand. The MAC address for the
access point is 1 less than the MAC address of the 5 GHz radio. The MAC
addresses reserved for use by WLAN BSSIDs begin with the MAC address
of the 5 GHz radio minus 31.
For example, if the MAC address of the TriBand is 000ADB01319F
(hexadecimal), the reserved addresses start at 000ADB013180 (the
difference being 1F hexadecimal, or 31 decimal).
4 | Chapter 2 Your SkyExtender TriBand Kit
NOTE
Plan to configure the SkyExtender TriBand before mounting it. Some
steps, such as those requiring a serial cable, are easier if the
SkyExtender TriBand is more accessible.
Getting Help
For technical assistance during the beta release period, contact SkyPilot support
by logging in to customer support at www.skypilot.com/support/.
Getting Help | 5
6
3
Installing SkyExtender TriBand
This chapter provides instructions for the physical installation of the SkyExtender
TriBand.
Chapter Highlights
Planning your installation
Mounting and cabling
Powering up
SkyExtender TriBand Installation and Setup | 7
Planning Your Installation
When choosing a site for the SkyExtender TriBand, consider the radio frequency
(RF) environment and the physical layout of the area.
Trees, buildings, and hills can impede a wireless signal. When assessing a site,
examine the overall topology of the wireless path for possible obstructions—both
existing and planned. The RF environment is dynamic and can deteriorate over
time as structures appear or are relocated.
Plan to use test signals to determine the suitability of the link topology for target
applications. Interference on your desired frequency results in overlapping signals,
causing outages or intermittent drops in throughput.
Once you’ve identified a potential site, use a topographic map or path profile
software to ensure that terrain or obstacles will not interfere with the links.
The site survey process should be ongoing. To verify that a site is interference-free,
make site audits every six to twelve months, scheduling regular maintenance visits
to coincide with the site audits.
Mounting and Cabling
The section provides instructions for physically installing the SkyExtender TriBand.
To install the SkyExtender TriBand:
Mount the SkyExtender TriBand.
Follow the instructions provided in the SkyGateway/SkyExtender Installation
and Setup document.
Make sure that you allow enough clearance for the 2.4 GHz antennas you
attach to the bottom of the TriBand.
8 | Chapter 3 Installing SkyExtender TriBand
2
Connect the antennas.
The access point requires attachment of the antennas provided with the
device. Screw the antennas onto the standard N-connectors on the bottom of
the TriBand:

4.9 GHz antenna onto Ant1

2.4 GHz antenna onto Ant2
Figure 3-1. Attaching the antennas
Connect the TriBand to the power supply.
As shown in Figure 3-2, connect the Ethernet straight-through cable
(provided) between the power injector and the Ethernet port on the bottom
of the TriBand.
Plug the AC adapter into the power injector.
Mounting and Cabling | 9
Figure 3-2. Providing power to the SkyExtender TriBand
NOTE
The Ethernet port on the TriBand is used to provide power and
Ethernet over a single CAT-5 cable. To use the Ethernet port, connect
a CAT-5 cable from the power injector port marked “Computer” to a
network switch or other device.
Powering Up
When power is supplied to the SkyExtender TriBand, it starts a routine power-up
sequence which you can monitor by observing the pair of LED lights on the
bottom of the device.
While the device is initializing and searching for a GPS signal, both LED lights blink
four times in a repeating cycle. (The SkyExtender TriBand must have access to a
GPS signal to complete its power-up sequence.)
When the Link LED turns steady green and the Activity LED is off, the TriBand is
initialized and listening for hello signals from other devices.
10 | Chapter 3 Installing SkyExtender TriBand
When both LEDs are steady, the TriBand is successfully connected to the wireless
network.
The sequence takes about 15 minutes to complete (while waiting to acquire a GPS
signal).
NOTE
Depending on your SkyPilot network configuration, the SkyExtender
TriBand may be unable to connect to the network until the device has
been configured as described in Chapter 4, “Configuring a SkyExtender
TriBand.”
Powering Up | 11
12
4
Configuring a SkyExtender TriBand
After installing the SkyExtender TriBand™, you need to provide the device’s
SkyExtender and access point components with the configuration information
they need for network operations.
This chapter explains how to use SkyPilot EMS software to configure the TriBand
for both mesh networking and Wi-Fi operation.
Chapter Highlights
Before you begin
Choosing a WLAN configuration
Automatic vs. manual configuration
Preparing software images
Automatic provisioning procedure
Manual provisioning procedure
SkyExtender TriBand Installation and Setup | 13
Before You Begin
Before starting configuration, make sure the SkyExtender TriBand is powered up
and capable of receiving a signal from a SkyGateway or SkyExtender.
Additionally, make sure the EMS software is installed (on both a central server and
a client) and set up for configuring SkyPilot devices. Detailed procedures for using
EMS software are provided in SkyPilot Network Administration, available from the
SkyPilot website at www.skypilot.com/support/.
Choosing a WLAN Configuration
Before starting configuration, decide on the type of Wi-Fi network you want to
configure at the access point location.
Most WLAN deployments use one of two common types of WLAN configurations:
Open—Allows anyone with Wi-Fi capability to connect to the wireless
network via the SkyExtender TriBand access point. An open WLAN does not
authenticate users at the network layer, nor does it depend on authentication
by a backend system.
An open configuration raises obvious security concerns. The lack of
encryption other than SSL/TLS (which is available only during login) makes
the network vulnerable to unauthorized access and malicious actions
(including denial-of-service attacks).
You can provide backend authentication at the application layer through a
captive portal mechanism operating outside your wireless mesh network. A
captive portal forces all HTTP traffic from an unauthenticated user to a login
Web page and blocks the traffic until the user successfully logs in. (For more
information about captive portal mechanisms, refer to the following Web
page: http://en.wikipedia.org/wiki/Captive_portal.)
An additional disadvantage of open configurations is that users must begin
each session from a Web browser before they can use other Internet
applications, such as email, ssh, ftp, and chat clients.
14 | Chapter 4 Configuring a SkyExtender TriBand
Protected—A Wi-Fi Protected Access (WPA) network which uses standardsbased client authentication and encryption. Users are authenticated via a
Radius server (which you’ll need to implement using a third-party solution).
WPA uses the IEEE 802.11b/g and IETF EAP protocols to give users a secure
connection with both the access point and the Radius server, allowing the
exchange of credentials (username@domain and password) and keys for
encrypting all traffic between the client and the access point—even after
authentication.
WPA encryption is by WEP, with the addition of keys that are unique to each
session and client. This additional keying mechanism eliminates the security
problems of the original WEP. You can use AES encryption with the TriBand for
even stronger encryption capabilities.
For more information about WPA, refer to the following Web page:
http://en.wikipedia.org/wiki/Wi-Fi_Protected_Access.
As you follow the procedure for configuring the TriBand, it will refer you to the
appropriate steps depending on the WLAN configuration you’ve chosen.
Setting Up a Radius Server for Authenticating
Users
If you plan to configure your SkyExtender TriBand access point for WPA, you must
first configure a Radius server with the following:
The IP address and shared secret of the TriBand access point.
EAP-PEAP/MSCHAPv2 and EAP-TTLS/PAP or MSCHAPv2 (not EAP-TLS) suitable
for WPA. (Your Radius supplier can provide instructions.)
A Users database with user names and passwords. (You may also need to
identify a proxy Radius if you’re delegating some domains to other service
providers.)
Choosing a WLAN Configuration | 15
Automatic vs. Manual Configuration
The SkyExtender and its contained access point require network configurations to
operate on the wireless mesh network. SkyPilot gives you a choice of two modes
for provisioning devices with configurations:
Automatic provisioning—Requires the use of SkyPilot EMS software to
create configurations that an unattended central server can distribute to
devices on the wireless mesh network. Although automatic provisioning
requires more setup time than manual provisioning, it greatly simplifies the
administration of a growing network.
After getting a configuration from the provisioning server, the SkyExtender
TriBand will establish a link to the SkyGateway (or to a SkyExtender or another
TriBand) and use DHCP to retrieve an IP address and instructions for
downloading configuration information stored on the server.
For automatic provisioning instructions, see “Automatic Provisioning
Procedure” on page 17.
Manual provisioning—Usually performed in the field, manual provisioning
permits the configuration of only a single device at a time, creating the
minimum settings required for a wireless link and storing them in the device’s
flash memory.
For manual provisioning instructions, see “Manual Provisioning Procedure” on
page 21.
For more information on provisioning modes, see Getting Started with the SkyPilot
Network, available from the SkyPilot website at www.skypilot.com/support/.
16 | Chapter 4 Configuring a SkyExtender TriBand
Preparing Software Images
EMS Software
Before you use the SkyPilot EMS software to set up the automatic configuration of
the SkyExtender TriBand, make sure the most current software images are
available to the EMS program.
To provide the EMS program with access to software images, copy the images to
the folder /var/ftp/pub/images on the provisioning server.
Access Point Firmware
You can update the firmware in a SkyExtender TriBand access point either before
or after TriBand configuration. All you need is the IP address of the TriBand access
point and FTP installed on the host computer that contains the desired firmware
image. For detailed procedures, refer to “Updating Access Point Firmware” in
SkyPilot Network Administration.
Automatic Provisioning Procedure
Table 4-1 summarizes the steps required to configure a SkyExtender TriBand
device operating in automatic provisioning mode.
Table 4-1. Automatically Provisioning a SkyExtender TriBand (Page 1 of 4)
Step
Refer to
Make sure the most current
software images are available to
the EMS client software.
“Preparing Software Images” on
page 17
Start the EMS client.
“Starting the EMS Client” in
SkyPilot Network Administration
Choose the software images the
provisioning server will use to
configure the new device.
“Configuring Software Images” in
SkyPilot Network Administration
Preparing Software Images | 17
Table 4-1. Automatically Provisioning a SkyExtender TriBand (Page 2 of 4)
Step
Refer to
Specify a domain for the TriBand
that is consistent with the
domain assigned to the
SkyGateway operating as a hub
for the wireless mesh network.
“Configuring Domains” in SkyPilot
Network Administration
Confirm that an appropriate node
profile exists for the TriBand.
“Configuring Node Profiles” in
SkyPilot Network Administration
If no appropriate profile exists,
create one.
NOTE This node profile is
separate from the one
you’ll later use for the
TriBand access point.
Add the TriBand as a new node
on the wireless mesh network,
using the node profile you
identified or created in step 5.
“Configuring Nodes” in SkyPilot
Network Administration
When you add a node and
identify its type as SkyExtender
TriBand, an access point node is
automatically created (but not
assigned an access point profile),
and access point operations
become available on the EMS
client taskbar.
Confirm that an appropriate AP
security profile exists for Telnet
communications with the
SkyExtender TriBand Access Point.
If no appropriate profile exists,
create one.
18 | Chapter 4 Configuring a SkyExtender TriBand
“AP Security Profile Operations” in
SkyPilot Network Administration
Table 4-1. Automatically Provisioning a SkyExtender TriBand (Page 3 of 4)
Step
Refer to
Decide which type of Wi-Fi
network you want to configure
for the device’s access point:
“Choosing a WLAN Configuration”
on page 14
Protected access (WPA)
Open access
If you’re configuring an open
access network, skip this step.
“AP Radius Profile Operations” in
SkyPilot Network Administration
For protected access (WPA)
configurations, confirm that an
appropriate AP Radius profile
exists to provide the WAN with
information about the Radius
server that will be used to
authenticate users.
NOTE The steps to configure a
Radius server vary
depending on the vendor
solution, and are outside
the scope of SkyPilot
documentation.
If no appropriate profile exists,
create one.
10
Confirm that an appropriate AP
WLAN SSID profile exists for the
desired network configurations
(protected or open). The profile
should be set up as follows:
“AP WLAN SSID Profile Operations”
in SkyPilot Network Administration
If you’re setting up multiple
WLAN SSIDs with different
security policies and/or
multiple IP address spaces, the
use of VLANs is highly
recommended.
Broadcast SSID should be
enabled.
SSID Status should be active.
An appropriate security policy
should be set: WPA for
protected networks, None for
open networks.
If no appropriate profile exists,
create one.
Automatic Provisioning Procedure | 19
Table 4-1. Automatically Provisioning a SkyExtender TriBand (Page 4 of 4)
11
Step
Refer to
Confirm that an appropriate
access point node profile exists.
(Remember that this profile is
separate from the one that’s
assigned to the TriBand node you
added in step 6.)
“Access Point Node Profile
Operations” in SkyPilot Network
Administration
The profile’s attributes should
include the access point profiles
you created in the previous steps:
AP security, AP Radius (for
protected networks), and WLAN
SSID.
If no appropriate profile exists,
create one.
12
Complete the configuration of
the access point node that was
automatically created when you
added its associated TriBand
node to the network (step 6).
“Access Point Node Operations” in
SkyPilot Network Administration
Modify the access point node,
assigning to it the access point
node profile you identified or
created in step 11.
13
Verify that the newly configured
TriBand is configured as a node
on the mesh network.
“Domain Map” function in
SkyControl, described in SkyPilot
Network Administration
14
(Optional) Set TriBand polling
intervals and other provisioning
parameters.
SkyControl and SkyProvision
functions, described in SkyPilot
Network Administration
20 | Chapter 4 Configuring a SkyExtender TriBand
Manual Provisioning Procedure
To configure a TriBand that’s in manual provisioning mode, you first configure its
SkyExtender portion (following the same procedure as for SkyExtenders), and then
you configure its access point.
To manually provision a SkyExtender TriBand:
Log in to the SkyExtender portion of the TriBand.
You can connect to a TriBand and access its command-line interface via a
terminal session from a console connected to the TriBand’s RJ-45 serial port.
After logging in (by supplying a password), you can enter commands at the
command prompt. For detailed cabling and access instructions for the
command-line interface, refer to the SkyPilot Command-Line Interface
Reference.
Configure the SkyExtender by using the set prov batch command.
Enter the set prov manual command so that the SkyExtender uses
manual provisioning mode when it next starts.
Log in to the TriBand’s access point.
You can connect to an access point and access its Web-based interface via a
network connection to the SkyExtender portion of the TriBand or by a direct
Wi-Fi connection to the access point. After logging in (by supplying a
password), you can configure the access point through its Web-based
interface. For detailed network setting requirements and access instructions
for the Web-based interface, refer to the SkyPilot Web Interface Reference.
Using the Access Point Configuration page, configure the access point’s
global configuration parameters.
Using the WLANs Settings page, configure the SSIDs.
Optionally, configure any additional access point settings that you want.
Manual Provisioning Procedure | 21
22
A
FCC Statements
FCC Radio Frequency Interference Statement
SkyExtender TriBand FCC Number: RV7-DBE1010
This equipment has been tested and found to comply with the limits for a class B
digital device, pursuant to part 90 of the FCC Rules. These limits are designed to
provide reasonable protection against interference in a residential installation. This
equipment generates, uses, and can radiate radio frequency energy and if not
installed, and used in accordance with the instructions, may cause harmful
interference to radio communications. However, there is no guarantee that
interference will not occur in a particular installation. If this equipment does cause
harmful interference to radio or television reception, which can be determined by
turning the equipment off and on, the user is encouraged to try and correct the
interference by one or more of the following measures:
Reorient or relocate the receiving antenna.
Increase the distance between the equipment and the receiver.
Connect the equipment to an outlet on a circuit different from that to which
the receiver is connected.
Consult the dealer or an experienced radio/TV technician for help.
This equipment has been certified to comply with the limits for a class B
computing device, pursuant to FCC Rules. In order to maintain compliance with
FCC regulations, shielded cables must be used with this equipment. Operation
with non-approved equipment or unshielded cables is likely to result in
interference to radio and TV reception. The user is cautioned that changes and
modifications made to the equipment without the approval of manufacturer
could void the user's authority to operate this equipment.
SkyExtender TriBand Installation and Setup | 23
Maximum Permissible Exposure
In order to meet the FCC’s requirement of 1 mW/cm2 for Maximum Permissible Exposure
(MPE) at 4.9 GHz, the SkyGateway/SkyExtender units must be located a minimum of 36
cm (14 inches) from all persons. This distance is determined based upon the
aforementioned 1 mW/cm2 limit, measured data, and the following far-field peak power
density equation:
d=
0.282 10 (( P +G ) / 20 )
where:
d = MPE distance in cm
P = Power in dBm (peak)
G = Antenna Gain in dBi
S = Power Density Limit in mW/cm2 (1 mW/cm2)
Certified laboratory measurements indicate that the FCC’s Power Density Limit of 1
mW/cm2 is met at a distance of much less than 36 cm (14 inches). However the
minimum distance for fixed or mobile transmitters is 36 cm even if calculations indicate
the MPE distance is much less.
FCC 15.203 statement
Because this device uses standard RF connectors for the external removable antennas,
professional installation is required.
IC RSS-210 statement
This device has been designed to operate with the antennas listed below. Antennas
having a gain greater than those on this list are strictly prohibited for use with this device.
The required antenna impedance is 50 ohms.
Approved antennas:
Manufacturer
Model
Comet
SF245
Comet
SF245+12
Comet
SF245+12x
Comet
SF495+9x
24 | Appendix A FCC Statements

---

Source Exif Data:

File Type                       : PDF
File Type Extension             : pdf
MIME Type                       : application/pdf
PDF Version                     : 1.5
Linearized                      : No
Page Count                      : 32
Page Mode                       : UseOutlines
Page Layout                     : SinglePage
Has XFA                         : No
XMP Toolkit                     : XMP toolkit 2.9.1-13, framework 1.6
About                           : uuid:e62938d6-6813-4de3-b516-e46900b77239
Producer                        : Acrobat Distiller 7.0.5 (Windows)
Create Date                     : 2006:06:12 11:59:34Z
Creator Tool                    : FrameMaker 7.2
Modify Date                     : 2006:09:13 14:55:43-07:00
Metadata Date                   : 2006:09:13 14:55:43-07:00
Document ID                     : uuid:245d7e7c-d4a8-4a55-b2be-69bd3a987f69
Instance ID                     : uuid:00eba3a6-735a-4592-afbc-2dcec6308319
Format                          : application/pdf
Creator                         : SkyPilot Networks
Title                           : SkyExtender TriBand Installation and Setup
Author                          : SkyPilot Networks

EXIF Metadata provided by EXIF.tools