1 started, troubleshooting steps
TRANSCRIPT
Getting Started with the SkyPilot Network
© 2005 SkyPilot Networks, Inc. All rights reserved.
SkyConnector, SkyControl, SkyExtender, SkyGateway, SkyPilot, SkyPilot Networks, SkyProvision, the SkyPilot logo, and other designated trademarks, trade names, logos, and
brands are the property of SkyPilot Networks, Inc. or their respective owners.
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.
Getting Started with the SkyPilot Network 3
Contents About This Guide 5
1 The SkyPilot Network 7
The SkyPilot Networks solution 7 Hardware components 8
Software components 9
2 Network Topologies 11
Point-to-point 11
Point-to-multipoint 12
Mesh 12 Topology and network architecture 15
3 Initial Setup and Configuration 17
Overview 17
Stage 1: Identifying equipment locations 18
Stage 2: Choosing an operating frequency 19 Stage 3: Provisioning and installing devices 20
Stage 4: Verifying connectivity 32
4 Troubleshooting 37
Troubleshooting power-on problems 38
Troubleshooting Ethernet connectivity problems 39
Troubleshooting IP connectivity problems 40 Troubleshooting SkyGateway transmission problems 45
Troubleshooting link failure problems 47
A Accessing the Command-Line Interface 63
Getting access via Ethernet 63
Getting access via a serial connection (SkyGateway/SkyExtender only) 64
Getting Started with the SkyPilot Network 5
A b o u t T h i s G u i d e This guide introduces the SkyPilot Networks™ wireless broadband solution and provides a “cookbook” for the initial setup of a SkyPilot™ wireless network. It also includes an overview
of the network topologies supported by SkyPilot and provides procedures for troubleshooting startup or connectivity problems that may arise.
The guide contains numerous references to the following SkyPilot documentation, where you’ll find more detailed information about the topics discussed here:
SkyPilot SkyGateway/SkyExtender Installation Guide
SkyPilot SkyConnector Installation Guide (Indoor Version)
SkyPilot SkyConnector Installation Guide (Outdoor Version)
SkyPilot Network Administration Guide
OS Installation Guide: Red Hat Linux 9.0
OS Installation Guide: Fedora Core 2
SkyPilot EMS Installation Guide
Complete SkyPilot documentation is available on the SkyPilot Network Software CD provided with your equipment or on the SkyPilot website at www.skypilot.com.
This guide assumes administrator-level knowledge of IP networks and a familiarity with wireless networking.
Getting Started with the SkyPilot Network 7
T h e S k y P i l o t N e t w o r k This chapter introduces the SkyPilot Networks wireless broadband solution and provides an overview of its hardware and software components.
The SkyPilot Networks solution SkyPilot Networks uses sophisticated engineering of existing technologies to deliver a wireless, end-to-end broadband solution that seamlessly supports high-capacity,
high-coverage networks. Designed for managed-access networks and service providers, the SkyPilot network takes broadband wireless the “last mile” with a cost-
effective, robust infrastructure solution.
SkyPilot gives carriers an opportunity to expand rapidly into new markets and extend their offerings to include high-bandwidth applications such as voice, on-demand video, and location-based services.
The SkyPilot solution offers a “tipping point” for converting dial-up customers to broadband and will help drive the growth of neighborhood “hotspots,” offering
ubiquitous wireless connectivity to local communities.
Based on a high-performance architecture that deploys intelligent antenna arrays, the SkyPilot network delivers dynamic bandwidth allocation, VoIP, and Quality of Service.
SkyPilot’s plug-and-play wireless devices are simple to install and will easily fit into any type of business or home environment.
1
Getting Started with the SkyPilot Network 8
Hardware components A SkyPilot network includes the following physical components:
SkyGateway™
SkyExtender™ (optional)
SkyConnector™ (indoor and outdoor)
This section introduces the individual components; the next chapter illustrates and explains how they work together in the various network topologies.
SkyGateway
The SkyGateway operates as a base station for your wireless network. It provides an interface between wired infrastructure and a wireless network of subscribers who
enjoy secure, high-speed access to the Internet or wide area networks.
NOTE A SkyPilot wireless network requires at least one SkyGateway for normal operations.
If necessary, you can add additional SkyGateways to increase network capacity or provide redundancy.
The SkyGateway typically resides at a location—usually a POP or data center—providing easy access to wired infrastructure.
For optimal performance, install the SkyGateway on an elevated site such as a cell tower or the top of a tall building.
SkyExtender
The SkyExtender functions as a “repeater” that extends the wireless range of a SkyGateway. By adding SkyExtenders to your network, you can expand your coverage footprint and provide redundancy through SkyPilot’s mesh-networking
features.
SkyExtenders provide a cost-effective way to add capacity and balance network loads.
Getting Started with the SkyPilot Network 9
For optimal performance, install the SkyExtender on an elevated, fixed location such as a roof, tower, or utility pole. (A SkyExtender can also provide subscribers with a direct connection to the wireless network via its Ethernet port.)
SkyConnector
SkyConnectors link your subscribers to the SkyPilot wireless network. An Ethernet port on the SkyConnector enables connecting to the subscribers’ computers or a
local area network (via a switch or router).
For flexibility of installation, SkyPilot offers indoor and outdoor versions of the SkyConnector.
Designed for installation by the service provider, the outdoor version of the SkyConnecter attaches to an external structure such as an eave, roof, or pole. In
general, the outdoor SkyConnector provides greater range than the indoor unit.
The indoor version of the SkyConnector is a plug-and-play network device that a subscriber can easily install without technical assistance. Advise subscribers to place
the SkyConnector in a location with an optimal sight line to the SkyGateway or a SkyExtender—for example, on a windowsill or in a window frame.
Software components The software components of a SkyPilot system are:
SkyProvision™, a server-based application that automates device provisioning by enabling devices to get their configuration information from the server.
SkyControl™, a real-time monitoring and management application for managing automatically provisioned devices. This software provides a graphical
view of your network topology with at-a-glance updates on topology, routing, and performance. SNMP-based, SkyControl supports both standard and private
MIBs.
Third-party applications provided as part of the EMS server installation. The package includes open-source versions of FTP, HTTP, and DHCP servers plus an
open-source database for storing device configuration information. For more
information on these third-party applications, see the SkyPilot EMS Installation
Guide.
Getting Started with the SkyPilot Network 10
A comprehensive command-line interface built into all SkyPilot devices.
SkyProvision and the command-line interface enter into the procedures introduced in this guide. Complete details on all of these software components can be found in
the SkyPilot Network Administration Guide.
Getting Started with the SkyPilot Network 11
N e t w o r k T o p o l o g i e s The highly flexible SkyPilot architecture supports the full range of network topologies: point-to-point, point-to-multipoint, and mesh.
Regardless of its initial configuration, your SkyPilot network automatically adapts to changes in the topology, without loss of service or expensive upgrades.
Point-to-point The most basic wireless topology, point-to-point connects a SkyGateway directly to a SkyConnector at a subscriber site. A point-to-point network is ideal for extending
high-performance networks between buildings.
Figure 1. Point-to-point configuration
2
Getting Started with the SkyPilot Network 12
Point-to-multipoint A point-to-multipoint topology employs a SkyGateway as the hub of a “star” configuration of multiple SkyConnectors.
This topology scales easily. You can add subscribers simply by installing a SkyConnector at the customer site, or by delivering a SkyConnector to the
subscriber for plug-and-play installation.
A point-to-multipoint SkyPilot network is ideal for delivering wireless broadband service to both residential customers and small businesses.
Figure 2. Point-to-multipoint configuration
Mesh A mesh topology uses SkyExtenders to extend range and add network flexibility. In a mesh configuration, subscribers can either connect to the SkyGateway directly or
connect to it indirectly via SkyExtenders (see Figure 3). In addition to adding range, a mesh network allows connections from locations where obstructions prevent line-
of-sight access to a SkyGateway hub.
Getting Started with the SkyPilot Network 13
Mesh networks are ideal for dense subscriber environments, for filling in coverage “holes,” and for reaching subscribers in areas where RF communications is obstructed by hills, trees, buildings, or other obstacles.
Figure 3. Mesh configuration
In addition to extending the service range and overcoming obstructions, SkyPilot’s mesh technology makes your network “self-healing.” If a connection fails, affected
devices automatically seek out alternate network paths and bring themselves back
online.
Figure 4 shows how a SkyPilot network can respond to a loss of connection by using alternate network paths—a capability that’s unavailable in conventional wired broadband installations.
Getting Started with the SkyPilot Network 14
Figure 4. A self-healing mesh network
Getting Started with the SkyPilot Network 15
Topology and network architecture
A SkyPilot wireless network is an intelligent, switched-Ethernet system. A sophisticated transport layer (Layer 2) lets subscribers move between SkyGateways
without requiring updates to their IP addresses.
Advanced techniques for rate control and packet prioritization permit multiple service offerings and provide support for high-quality VoIP. Packet filtering and wireless-link encryption ensure high levels of data security.
SkyPilot fully supports VLANs and filters for managing subscriber traffic across a wireless network.
Figure 5 illustrates how a SkyPilot network fits into a basic LAN environment.
Figure 5. LAN configuration
The SkyPilot solution supports a variety of techniques for IP addressing and Layer 3 end points across a broad range of devices. Figure 6 shows how you can easily
segment SkyPilot traffic at the IP layer, without installing additional equipment.
Getting Started with the SkyPilot Network 16
Figure 6. IP segmentation across a SkyPilot network
Getting Started with the SkyPilot Network 17
I n i t i a l S e t u p a n d C o n f i g u r a t i o n This chapter describes the steps you need to follow to set up a SkyPilot wireless network and successfully bring it online. The procedures refer to SkyPilot
documentation that contains more detailed information where applicable.
Overview Table 1 summarizes the four stages of SkyPilot network deployment.
Table 1. Four stages of deployment
Stage Description
1 Identifying equipment locations
Identify and prepare locations for installation.
2 Choosing an operating frequency
Choose a “clean” center frequency that permits interference-free operation of devices.
3 Provisioning and installing SkyPilot devices
Choose a provisioning mode for the devices: manual or automatic.
Provision the devices (for automatic provisioning, install operating system and SkyPilot EMS software).
Install the devices.
4 Verifying connectivity Confirm that the SkyGateway is online.
Confirm that installed SkyConnectors and SkyExtenders have established a link with the SkyGateway.
Review link characteristics and network performance.
3
Getting Started with the SkyPilot Network 18
Stage 1: Identifying equipment locations Deployment of a SkyPilot network starts with a site survey to help you identify the devices you need and choose optimal locations for installation.
Identifying locations for the SkyGateway and SkyConnectors is straightforward. For the SkyGateway, location depends on proximity to existing network infrastructure
and site elevation. SkyConnectors are placed at subscriber sites—homes or offices.
SkyExtenders are far more flexible in terms of location. If you determine that you need SkyExtenders in order to reach all your customers or add redundancy, you
must also identify optimal locations for their installation.
Guidelines for adding SkyExtenders
Multiple factors can affect wireless network performance—and dictate the need for SkyExtenders.
Physical distance. Are all your subscriber sites close enough to the SkyGateway for radio communications? If a SkyGateway is installed in a high location with a clear sight line to subscriber sites, it can maintain radio communications with
SkyConnectors or SkyExtenders at greater distances.
Elevation. There is a correlation between range and device elevation. By installing SkyPilot devices on raised locations, such as towers or tops of
buildings, you can avoid traffic “collisions” that occur at ground level, thereby extending the range at which the devices can operate normally.
Obstructions. An optimal link between a SkyGateway and a SkyConnector requires a clear line of sight. Obstructions, both artificial and natural, can reduce
effective network range or block radio communications entirely.
Type of SkyConnecter. Because it’s typically placed outside and at higher elevation than the indoor connector, the outdoor version of the SkyConnector
provides greater wireless range than the indoor version.
If there are obstructions blocking subscriber access (as in Figure 7) or if there are subscriber sites beyond the distance that a wireless link can maintain, you need to
add one or more SkyExtenders to the network.
Getting Started with the SkyPilot Network 19
Figure 7. Using a SkyExtender to extend the wireless network behind an obstruction
Preparing SkyExtender sites
If SkyExtenders are required, perform a survey of possible sites before beginning
installation. See the SkyGateway/SkyExtender Installation Guide for a detailed discussion of site requirements.
For optimal service, attach SkyExtenders to elevated, fixed locations with easy and continuous access to power.
Stage 2: Choosing an operating frequency All the devices on a SkyPilot network operate on a single frequency. Before beginning the installation, visit the deployment area and identify an optimal
operating frequency. Use a spectrum analyzer or other frequency-planning tool to
identify the best available frequency for the SkyPilot wireless network—a “clean” center frequency that permits interference-free operation of devices.
Getting Started with the SkyPilot Network 20
See the SkyGateway/SkyExtender Installation Guide for detailed information on frequency planning.
Stage 3: Provisioning and installing devices Stage 3 involves these tasks:
Choosing a provisioning mode: automatic or manual
Preparing the network infrastructure (for automatic provisioning, installing a supported operating system and SkyPilot software)
Installing the devices
Choosing a provisioning mode
Each SkyPilot device must be provisioned by being given a network configuration and being optimized for wireless operation. SkyPilot gives you a choice of two provisioning modes: automatic or manual.
Automatic provisioning allows unattended configuration of SkyPilot devices from a central server at your network operations center (NOC). Although automatic
provisioning requires more setup time than manual provisioning, it greatly simplifies network administration as your network grows.
Manual provisioning, on the other hand, has the advantage that it lets you configure a device with the minimum settings required for a wireless link.
Configuration settings are stored in flash memory; manually provisioned devices are
not dependent on a server for configuration. Manual provisioning is a logical choice if you’re installing a test network or rolling out a small-scale installation that’s not
expected to expand.
NOTE Manual provisioning does not offer some of the features included with automatic provisioning, such as access control lists, rate limits and traffic prioritization, and end-user traffic filtering.
Provisioning mode and device operations
The provisioning mode you choose for devices (automatic or manual) affects the procedure that devices use to come online.
Getting Started with the SkyPilot Network 21
Figures 8 and 9 illustrate the steps taken by devices—both manually and automatically provisioned—from power-on through the formation of network links.
Figure 8 shows the steps taken by a SkyGateway up to the point at which the device begins sending hello beacons that other SkyPilot devices can use to
form links on the wireless network.
Figure 9 (divided over two pages) shows the steps taken by SkyExtenders and SkyConnectors up to the point at which the device starts forming links with other devices on the wireless network.
Getting Started with the SkyPilot Network 22
Figure 8. SkyGateway power-on and link formation
Getting Started with the SkyPilot Network 23
Figure 9(a). SkyExtender/SkyConnector power-on and link formation
Getting Started with the SkyPilot Network 24
Figure 9(b). SkyExtender/SkyConnector power-on and link formation
Getting Started with the SkyPilot Network 25
General provisioning guidelines
Some requirements are independent of the provisioning mode you choose. To ensure that network devices form effective links, always follow these guidelines:
Set the domain of SkyExtenders and SkyConnectors to match the domain assigned to the SkyGateway.
To allow devices to establish network links more quickly, make sure that the primary frequency of SkyExtenders and SkyConnectors is the same as the
primary frequency assigned to the SkyGateway.
Make sure that the netkeys match on all devices attempting for form links.
All SkyPilot devices ship with a same default public netkey: SkyPilot Network,
Inc.
Provisioning tools: SkyProvision and the command-line interface
SkyPilot Networks provides tools to assist you in the provisioning of network devices.
If you plan to set up devices for automatic provisioning, you’ll use the SkyProvision application for configuration. You’ll install both the server and client components of
SkyProvision.
For manual provisioning, all SkyPilot devices provide a command-line interface that allows you to interact with the equipment through typed commands. (You’ll also
use the command-line interface to configure the management VLAN, if any, when setting up automatic provisioning for a SkyGateway.)
You can access the command-line interface by connecting a PC or laptop to the device’s Ethernet port and using Telnet to start a communications session. The
SkyGateway and SkyExtender also include a serial port for connecting to a console via a serial cable. For more information, see Appendix A, “Accessing the Command-
Line Interface.”
Getting Started with the SkyPilot Network 26
Mixed provisioning
If necessary, you can set up a SkyPilot network to use both provisioning modes. Although a “mixed” network will operate normally, individual devices will behave
differently depending on the provisioning mode:
Automatically provisioned devices will establish network links only when
SkyProvision is available to provide configuration information from a server.
Manually provisioned devices will form network links according to configuration settings stored in flash memory.
Order of installation
You can ensure optimal operations—and reduce administrative overhead—by installing your network devices in this order: first SkyGateway, then SkyExtenders
(optional), and finally SkyConnectors.
You install the SkyGateway first because, as the base station of the SkyPilot wireless network, it must be present in order for other devices to establish network links. When provisioned and powered on, the SkyGateway immediately starts
transmitting hello beacons that SkyExtenders and Sky Connectors use to form links.
After installing the SkyGateway, you add SkyExtenders (if required) and then SkyConnectors. Upon powering on, each device responds to the base station’s
hello beacon and starts forming links with the SkyGateway. Each device attempts to establish as many links as possible before choosing an optimal path.
After establishing network links, SkyExtenders on your network also begin transmitting hello beacons, extending the range of beacons available to other
devices. (SkyConnectors do not transmit hello beacons.)
The specific procedures for doing the necessary provisioning and installation are described in the sections that follow, first for manual provisioning and then (on page 29) for automatic provisioning.
Manually provisioning devices
Manual provisioning stores settings in the device’s flash memory, where they remain available for recall when the device starts up. For more information about
manual provisioning features, see the SkyPilot Network Administration Guide.
Getting Started with the SkyPilot Network 27
NOTE If you’re installing the device in a location that poses difficulties, consider delaying the final mounting until you can confirm that provisioning was successful.
Manually provisioning a SkyGateway
To manually provision a SkyGateway:
1 Prepare the SkyGateway for installation.
Follow the instructions in the SkyGateway/SkyExtender Installation Guide for
cabling the device and readying it for service. Do not install the device yet.
2 Power on the SkyGateway.
NOTE To complete startup, a SkyGateway must be able to detect a GPS signal that allows it to synchronize with other devices on the network. Without the GPS signal, you won’t be able to log in to the device.
3 Connect a computer to the SkyGateway and access the command-line interface.
For more information on accessing the command-line interface, see
Appendix A.
4 Enable manual provisioning.
From the command line, enter set prov manual to enable manual provisioning.
5 Make the configuration settings.
From the command line, enter set prov and follow the prompts for configuration settings. At a minimum, the device requires frequency and
domain settings to start transmitting.
Make any other settings you require; for example, enable VLAN management or
assign an IP address to the SkyGateway.
See the SkyPilot Network Administration Guide for detailed descriptions of
set prov and related commands for making configuration settings.
Getting Started with the SkyPilot Network 28
6 Power off the SkyGateway.
7 Install the SkyGateway.
Follow the instructions in the SkyGateway/SkyExtender Installation Guide for
installing the device.
8 Power on the SkyGateway.
The SkyGateway starts up in manual provisioning mode and immediately begins transmitting hello beacons on the frequency and within the domain
specified in the configuration.
Manually provisioning SkyExtenders and SkyConnectors
The procedures for manually provisioning SkyExtenders and SkyConnectors are identical.
To manually provision a SkyExtender or SkyConnector:
1 Prepare the device for installation.
Follow the instructions in the SkyGateway/SkyExtender Installation Guide or the
SkyConnector Installation Guide for cabling the device and readying it for
service. Do not install the device yet.
2 Power on the device.
NOTE To complete startup, a SkyExtender must be able to detect a GPS signal that allows it to synchronize with other devices on the network.
3 Connect a computer to the device and access the command-line interface.
For more information on accessing the command-line interface, see
Appendix A.
4 Enable manual provisioning.
From the command line, enter set prov manual to enable manual provisioning.
Getting Started with the SkyPilot Network 29
See the SkyPilot Network Administration Guide for detailed instructions on enabling manual provisioning.
5 Make the configuration settings.
From the command line, enter set prov and follow the prompts for configuration settings. At a minimum, the device requires a configuration that
supplies both a domain and a frequency. Setting a preferred frequency can
reduce the time it takes a device to establish a link and come online.
You can use either the set prov command or the set freq command to configure a list of preferred and allowed frequencies that the device will use to hunt for links. If you don’t set a starting frequency, the device uses the default
starting frequency stored in its configuration.
See the SkyPilot Network Administration Guide for detailed descriptions of
set prov, set freq, and related commands for making configuration settings.
6 Power off the device.
7 Install the device.
Follow the instructions in the SkyGateway/SkyExtender Installation Guide or
SkyConnector Installation Guide for installing the device.
8 Power on the device.
The device starts up in manual provisioning mode and begins attempting to form links and bring itself up on the network.
Preparing the SkyPilot network for automatic provisioning
To enable automatic provisioning, you must first install SkyProvision (on a central server and a client) and set it up to configure SkyPilot devices from the server. Each
automatically provisioned device will establish a link to the SkyGateway (or to a SkyExtender) and use DHCP to retrieve an IP address and the instructions for
downloading configuration information stored on the server.
Here’s an overview of what you’ll do:
1 Ensure that the system requirements for the server and client are met.
Getting Started with the SkyPilot Network 30
2 Custom-install the operating system software on the server.
3 Install SkyPilot software (SkyProvision and SkyControl) on the server and the client.
4 Set up the DHCP server and, if the provisioning server is behind a firewall, specify ports for data traffic between the server and network devices.
5 Set up the SkyGateway, SkyExtenders, and SkyConnectors (in that order) for automatic provisioning.
Detailed procedures are provided in the following subsections and in related
documentation (primarily the SkyPilot Network Administration Guide) available on
the SkyPilot Network Software CD or the SkyPilot website at www.skypilot.com.
Performing a custom OS installation
Before you can install SkyPilot software on the provisioning server, you must perform a “clean” installation (or reinstallation) of your operating system on that
server. You must customize the installation to (among other things) exclude
software packages or services duplicated by the SkyPilot software installation.
See the appropriate guide for your operating system, available on the SkyPilot
Network Software CD or the SkyPilot website.
Installing SkyPilot server software
For detailed instructions on installing SkyPilot server software, including
SkyProvision and SkyControl, see the SkyPilot EMS Installation Guide.
Setting up DHCP
Set up the DHCP server and provide configuration information in SkyProvision. If the provisioning server is behind a firewall, you must specify ports for data traffic
between the server and network devices. Details can be found in the SkyPilot
Network Administration Guide.
Setting up SkyPilot devices for automatic provisioning
Follow these instructions for setting up SkyPilot devices that will be provisioned automatically via SkyProvision.
Getting Started with the SkyPilot Network 31
1 Set up the SkyGateway for automatic provisioning:
a Install the SkyGateway and power it on.
Follow the instructions in the SkyGateway/SkyExtender Installation Guide for
installing and powering on the device.
NOTE To complete startup, a SkyGateway must be able to detect a GPS signal that it can use to synchronize with other devices on the network.
b (Optional) Log in to the SkyGateway and configure the management VLAN.
VLAN configuration affects the SkyGateway’s ability to receive a configuration file. If you’re using a management VLAN, you must use the
command-line interface to configure it manually. For more information on accessing the command-line interface, see Appendix A.
From the command line, use the set vlan command to enable the VLAN and configure it for the SkyGateway. For details on enabling a VLAN, see the
set vlan command description in the SkyPilot Network Administration
Guide.
NOTE For a SkyPilot network, you configure a management VLAN on the SkyGateway only. SkyExtenders and SkyConnectors learn of this VLAN through hello beacons and use it as a basis for creating VLAN tags for management traffic. You configure the data VLAN for a SkyExtender or SkyConnector in SkyProvision.
If provisioning is successful, no further SkyGateway configuration is necessary.
When the SkyGateway receives its configuration file, it immediately begins transmitting hello beacons on the frequency and within the domain specified
in the configuration.
2 Set up the SkyExtenders and SkyConnectors (in that order) for automatic provisioning. The procedure is the same for both; do the following for each device:
a Install the device.
Getting Started with the SkyPilot Network 32
Follow the instructions in the SkyGateway/SkyExtender Installation Guide or
the SkyConnector Installation Guide for installing the device and readying it
for service.
NOTE To complete startup, a SkyExtender must be able to detect a GPS signal that allows it to synchronize with other devices on the network.
b Power on the device.
The device starts up in automatic provisioning mode and immediately attempts to form links with the network and bring itself online.
If provisioning is successful, no further configuration is necessary.
NOTE If necessary, you can use the set freq command to configure the frequency list and speed up initial link hunting. See the SkyPilot Network Administration Guide for detailed instructions on using set freq.
Stage 4: Verifying connectivity After provisioning and installing your SkyPilot devices, follow these procedures to confirm that the devices are properly connected to the network.
Confirming SkyGateway connectivity
There are two ways to confirm SkyGateway connectivity:
Check the LED status lights on the SkyGateway to verify that the device is fully online.
See Table 4 for a summary of what the LED status lights mean. For a detailed
description of the status lights, see the SkyGateway/SkyExtender Installation
Guide.
Getting Started with the SkyPilot Network 33
Table 4. SkyGateway LED status lights
Device state Link LED Activity LED
Startup in progress Slow, staggered blinking by both LEDs
Startup failure Off On
Initializing image (and acquiring GPS signal)
Blinks 4 times; repeats cycle
Blinks 4 times; repeats cycle
Initialization failure Fast, synchronized blinking of both LEDs
Successful initialization, but authorization failure
On Off
Connected On On
Alternatively, from the command line, use the ping command to poll the default gateway specified in the device’s DHCP lease.
For example:
> ping 192.168.5.1 PING 192.168.5.1: 56 data bytes 64 bytes from 192.168.5.1: icmp_seq=0. time=11. ms 64 bytes from 192.168.5.1: icmp_seq=1. time=12. ms 64 bytes from 192.168.5.1: icmp_seq=2. time=12. ms ----192.168.5.1 PING Statistics---- 3 packets transmitted, 3 packets received, 0% packet loss round-trip (ms) min/avg/max = 0/16/32
Confirming SkyExtender and SkyConnector connectivity
Use one or more of the following methods to confirm SkyExtender and SkyConnector connectivity:
Check the LED status lights to verify that the unit is fully online.
For a summary of what the LED status lights mean, see Table 5 for a SkyExtender or Table 6 for a SkyConnector. For a detailed description of the status lights, see
the SkyGateway/SkyExtender Installation Guide or SkyConnector Installation
Guide.
Getting Started with the SkyPilot Network 34
Table 5. SkyExtender LED status lights
Device state Link LED Activity LED
Startup in progress Slow, staggered blinking by both LEDs
Startup failure Off On
Initializing image (and acquiring GPS signal)
Blinks 4 times; repeats
Blinks 4 times; repeats
Initialization failure Fast, synchronized blinking of both LEDs
Successful initialization, but can’t locate hello
On Off
Successful initialization; heard hello on RSSI
Off Blink (RSSI rate-based)
Successful initialization; link is not optimized or is in pre-authorization
Slow blink Blink (RSSI rate-based)
Successful initialization; link is in standby state on RSSI
Fast blink Blink (RSSI rate-based)
Connected On On
Getting Started with the SkyPilot Network 35
Table 6. SkyConnector LED legend
LED LED state Device state
LAN Link Steady illumination SkyConnector is connected to another device via its Ethernet port.
LAN Act Blinking Device is transmitting or receiving data via its Ethernet port.
WAN Link Blinking (fast blink when device is in standby mode)
Device is attempting to establish an authorized connection on the wireless network.
Steady illumination Device is connected to the wireless network.
WAN Act None Device cannot detect a wireless network.
Blinking Device is within the coverage area of a wireless network. Blink rate communicates signal strength:
• Fast (8x per second) = excellent • Medium (4x per second) = good • Slow (<1x per second) = poor
From the command line, use the show link command to confirm that an active link exists.
The device is online if the output displays an act path (active path) link state. For example:
Node Id LType NType State RSSI LTxMod RTxMod LAnt RAnt ----------------- ----- ----- --------- ---- ------ ------ ---- ---- 00:0a:db:00:00:43 data ext act path 39 48 36 2 4
Use the traceroute command to confirm that you can send and receive data across the wireless network.
Traceroute is a SkyPilot protocol trace that shows the path to the SkyGateway.
Entering the traceroute command without parameters returns a path that the
device identifies as its exit from the network.
Getting Started with the SkyPilot Network 36
Here’s an example of a traceroute command:
traceroute to 00:0a:db:00:00:a6 >> 1 (48) --> 00:00:43 --> (36) 2 (36) --> 00:00:a6 --> (36)
Use the ping command to verify that you can reach the device’s default
gateway.
For example:
> ping 192.168.5.1 PING 192.168.5.1: 56 data bytes 64 bytes from 192.168.5.1: icmp_seq=0. time=11. ms 64 bytes from 192.168.5.1: icmp_seq=1. time=12. ms 64 bytes from 192.168.5.1: icmp_seq=2. time=12. ms ----192.168.5.1 PING Statistics---- 3 packets transmitted, 3 packets received, 0% packet loss round-trip (ms) min/avg/max = 0/16/32
Getting Started with the SkyPilot Network 37
T r o u b l e s h o o t i n g This chapter provides procedures for troubleshooting startup or connectivity problems with a SkyPilot device. Each procedure is presented in a table set up like
this (with varying numbers of steps and substeps):
1 You’ll be told to check for something as described in what follows:
a Here there will be a description of an action to take to accomplish the
check.
Here you’ll see paragraphs describing what to do next, depending on the outcome of the action you
took.
The following open-lock symbol is shown when
you have solved the problem.
If advised to contact SkyPilot customer support, you can do so via email ([email protected]) or by
telephone at (408) 764-8000.
Additional troubleshooting information may be found in the SkyPilot Network
Administration Guide, in the appropriate device documentation, or on the SkyPilot
website at www.skypilot.com.
The chapter makes numerous references to commands available through the command-line interface that all SkyPilot devices provide, either through Telnet over an Ethernet connection or (for SkyGateway and SkyExtender only) via a terminal
session from a console connected to the device’s serial port. For instructions on
accessing the command-line interface, see Appendix A. For detailed descriptions of the commands, as well as sample output for many of these commands, see the
SkyPilot Network Administration Guide.
4
Getting Started with the SkyPilot Network 38
Troubleshooting power-on problems This section provides a procedure for troubleshooting the failure of a SkyPilot device to power on. It applies to any SkyPilot device and to either provisioning mode
(manual or automatic).
1 Check whether the device is getting power:
a Verify that the device is plugged into an AC power supply.
If plugged in, go to substep b.
If not plugged in, plug in and restart.
b Test your power source with a voltage meter.
If power is available, go to step 2.
If power is not available, try an alternate power
source and restart.
2 Check whether the power injector is OK:
Check whether the red light on the power injector is lit.
If the red light is lit, go to step 3.
If the light is not lit, replace the power injector and restart.
3 Check whether the device is properly cabled:
Verify that the device is connected to the power injector with a
straight-through cable.
If the correct cable is being used, go to step 4.
If the wrong cable is connecting the device, replace it with the correct cable and restart.
Getting Started with the SkyPilot Network 39
4 Check whether the cable is defective:
Use a cable tester to check the cable.
If the cable is not defective, go to step 5.
If the cable is defective, replace it and restart.
5 Check whether the cable is plugged into the correct port:
On a SkyGateway or SkyExtender, confirm that the cable is plugged
into the horizontal powered Ethernet port and not the vertical
serial port.
If the cable is plugged into the serial port, attach it to the powered Ethernet port and restart.
If the cable is connected to the correct port on a
SkyGateway or SkyExtender, or if the device is a SkyConnector, contact SkyPilot customer support.
Troubleshooting Ethernet connectivity problems This section addresses problems that a SkyPilot device can have in making Ethernet connections. It applies to any SkyPilot device and to either provisioning mode
(manual or automatic).
1 Check whether the SkyPilot device is connected with the proper cables:
Verify the use of the following CAT5 twisted-pair cables:
� Straight-through cable between power injector and the device
� Straight-through cable between power injector and an Ethernet switch or hub
� Crossover cable between power injector and computer.
If the correct cables are being used, go to step 2.
If an incorrect cable is being used, replace it and restart.
Getting Started with the SkyPilot Network 40
2 Check whether any of the cables are defective:
Use a cable tester to check each cable connected to the device.
If none of the cables are defective, go to step 3.
If a cable is defective, replace it and restart.
3 Check whether Ethernet is enabled on all network devices connected to the SkyPilot device:
Confirm that Ethernet is enabled
on all equipment connected to
the SkyPilot device you’re
troubleshooting.
If Ethernet is enabled on all devices, go to step 4.
If Ethernet is not enabled on a device, enable it and
restart all devices.
4 Check whether all of the connected devices are able to auto-negotiate an Ethernet
connection:
a Confirm that each network device is able to auto-negotiate an
Ethernet connection.
If all network device settings are correct, go to substep b.
If the settings for any device are incorrect, modify its
configuration and restart the device.
b To check the SkyPilot device, use
the show eth command to view its
current settings.
If the settings for the SkyPilot device are incorrect,
use the set eth command to modify the Ethernet
configuration, and then restart the device.
If the device settings are correct and the problem
persists, contact SkyPilot customer support.
Troubleshooting IP connectivity problems This section addresses device problems related to IP connectivity. It includes two subsections for solving problems related to SkyGateway IP connectivity: one for manually provisioned SkyGateways and another for SkyGateways provisioned
automatically. The remaining subsection addresses IP connectivity problems related
Getting Started with the SkyPilot Network 41
to SkyExtenders and SkyConnectors, whether manually provisioned or set up for
automatic provisioning.
The primary causes of IP connectivity problems with SkyPilot devices are a failure to acquire a GPS signal (SkyGateway or SkyExtender), the location of a device on the
wrong subnet, and conflicts with VLAN management solutions.
SkyGateway IP connectivity problems (manual provisioning)
This subsection addresses IP connectivity problems with a manually provisioned SkyGateway.
1 Check whether the SkyGateway is able to acquire a GPS signal:
Log in to the SkyGateway via the serial port and observe the output at startup to verify the acquisition of
a GPS signal.
See Appendix A for instructions on
accessing the command-line
interface of a SkyPilot device.
If the output confirms that the SkyGateway is
receiving a GPS signal, go to step 2.
If the SkyGateway is failing to acquire a signal, move it to an alternate location and retest.
2 Check whether the SkyGateway is on the correct subnet:
Use the show prov command to verify that the SkyGateway is
configured with the desired IP
address. (A SkyGateway does not have a default IP address.)
If the command output shows the correct IP address, go to step 3.
If the output shows an incorrect IP address, use
the set ip command to apply the correct IP
address, and then restart the SkyGateway.
Getting Started with the SkyPilot Network 42
SkyGateway IP connectivity problems (automatic provisioning)
This subsection addresses IP connectivity problems with a SkyGateway that is provisioned automatically from the SkyProvision server.
3 Check whether VLAN settings are preventing access to the SkyGateway:
If a management VLAN is present, it
might be preventing local access to the SkyGateway from the network.
Use the show vlan command to check whether a management
VLAN is configured on the SkyGateway.
If the SkyGateway has been incorrectly
configured with a management VLAN, modify (or
remove) the VLAN with the set vlan command
and retest.
If the VLAN settings are correct and the problem
persists, contact SkyPilot customer support.
1 Check whether the SkyGateway is able to acquire a GPS signal:
Log in to the SkyGateway via the serial port and observe the output at startup to verify the acquisition of a
GPS signal.
See Appendix A for instructions on
accessing the command-line
interface of a SkyPilot device.
If the output confirms that the SkyGateway is
receiving a GPS signal, go to step 2.
If the SkyGateway is failing to acquire a signal,
move it to an alternate location and retest.
Getting Started with the SkyPilot Network 43
2 Check whether VLAN settings are preventing access to the SkyGateway:
If a management VLAN is present, it
might be preventing local access to the SkyGateway from the network.
Use the show vlan command to check whether a management VLAN
is configured on the SkyGateway.
If the SkyGateway has been incorrectly
configured with a management VLAN,
modify (or remove) the VLAN with the set
vlan command and retest.
If the VLAN settings are correct and the
problem persists, contact SkyPilot customer
support.
3 Check whether the SkyGateway is on the correct subnet:
Use the show dhcp command to verify that the SkyGateway received
an IP address from DHCP. (A SkyGateway does not have a default
IP address.)
If the command output shows that the SkyGateway did not get an IP address from DHCP or that it received an incorrect IP
address, modify the configuration on the
DHCP server and retest.
If the output shows that the SkyGateway has
received an IP address from DHCP, contact SkyPilot customer support.
Getting Started with the SkyPilot Network 44
SkyExtender/SkyConnector IP connectivity problems
This subsection addresses IP connectivity problems with a SkyExtender or SkyConnector.
1 (SkyExtender only) Check whether the device is able to acquire a GPS signal:
Log in to the SkyExtender via the serial port and observe the output
at startup to verify the acquisition of
a GPS signal.
See Appendix A for instructions on accessing the command-line
interface of a SkyPilot device.
If the output confirms that the SkyExtender is
receiving a GPS signal, go to step 2.
If the SkyExtender is failing to acquire a signal, move it to an alternate location and retest.
2 Check whether the subscriber’s client computer is on the correct subnet:
To communicate over the LAN, a subscriber’s computer must be on
the same subnet as the SkyPilot
device.
Both SkyExtenders and
SkyConnectors use the IP address 192.168.0.2.
Open the network settings panel of the computer to confirm that it is
using these settings:
IP address: 192.168.0.3
Subnet mask: 255.255.255.0
If the computer’s network settings are correct, go to step 3.
If the computer’s network settings are incorrect, apply the correct settings and retest.
Getting Started with the SkyPilot Network 45
Troubleshooting SkyGateway transmission problems This section describes steps for troubleshooting SkyGateway devices with wireless transmission problems. It includes separate subsections for SkyGateways
provisioned manually and those set up for automatic provisioning.
3 Check whether VLAN settings are preventing access to the device:
a
If a management VLAN is present on the SkyGateway, it will prevent
local network access to a SkyExtender or SkyConnector after
the device forms a link with the
SkyGateway.
On the SkyGateway, use the show
vlan command to check whether a management VLAN matching the
Ethernet switch is configured for
that device.
If the SkyGateway has not been configured with a management VLAN,, go to substep b.
If the SkyGateway has been configured with a
management VLAN, modify (or remove) the
VLAN with the set vlan command and retest.
b
If a data VLAN is present on the SkyExtender/SkyConnector, it will
prevent local network access to the
device.
For a SkyExtender, log in to the
device via the serial port; for a SkyConnector, log in via Telnet
across the wireless network. Then
use the show vlan command to check whether a data VLAN has
been enabled on the device.
If the command output indicates that a data
VLAN is present on the device, use the set vlan
command to remove the VLAN, and then
retest.
If the output does not indicate that a data VLAN is
present and the problem persists, contact SkyPilot customer support.
Getting Started with the SkyPilot Network 46
SkyGateway not transmitting (manual provisioning)
This subsection addresses wireless transmission problems with a manually provisioned SkyGateway (which immediately begins transmitting network signals
upon completing startup).
SkyGateway not transmitting (automatic provisioning)
This subsection addresses transmission problems with a SkyGateway that is set up for automatic provisioning.
1 Check whether the SkyGateway is in manual provisioning mode:
Log in to the SkyGateway via the
serial port and use the show prov
command to confirm that the SkyGateway was placed in manual
provisioning mode.
If the command output indicates that the device
is not in manual provisioning mode, use the set
prov manual command to set that mode, and
then restart the SkyGateway. (After a SkyGateway is placed in manual provisioning mode, restarting
it is necessary to activate the mode.)
If the SkyGateway is in manual provisioning mode
but is unable to transmit signals, contact SkyPilot customer support.
1 Check whether the SkyGateway is getting its IP settings from DHCP:
Log in to the SkyGateway via the
serial port and use the show dhcp command to confirm that it
received the correct IP settings,
including IP address, subnet mask,
default gateway, HTTP server (SkyProvision), and FTP server
(SkyProvision).
If the command output shows that the device received the correct IP settings, go to step 2.
If the device did not receive IP settings from DHCP or has incorrect settings, modify the configuration
on the DHCP server and retest.
Getting Started with the SkyPilot Network 47
Troubleshooting link failure problems This section describes steps for troubleshooting all SkyPilot devices having problems forming links that allow network communications. It provides separate
sections for troubleshooting manually provisioned devices and devices set up for automatic provisioning through SkyProvision.
Device failing to form links (manual provisioning)
This subsection addresses problems that a manually provisioned SkyPilot device may have in forming links that allow it to connect with other devices on the wireless
network.
2 Check whether the SkyGateway received a configuration file with correct settings:
A SkyGateway set up for automatic provisioning receives its
configuration from the SkyProvision
server.
Use the show config command to confirm that the device received
correct configuration information,
including the desired frequency and
domain. If no settings are present, the SkyGateway did not receive a
configuration file.
You can also review the contents of
the /var/log/messages file on the
SkyProvision server to verify that the SkyGateway is requesting a
configuration and, if so, that
SkyProvision is responding to the request.
If the command output indicates that the SkyGateway is not getting its configuration from
SkyProvision or that it received incorrect settings,
first confirm that the SkyProvision server is running. If the server is up, modify the
configuration settings for the SkyGateway and
retest.
If the output indicates that the SkyGateway is
getting the correct configuration settings from the SkyProvision server, contact SkyPilot
customer support.
Getting Started with the SkyPilot Network 48
1 Check whether the device is listening on the desired frequency:
a Initially, a SkyPilot device scans for frequencies that are on its list of
preferred or allowed frequencies.
Use the show prov freq
command on the device to verify
that the desired frequency is on the list. (You can also use the
show prov freq command on the
SkyGateway to check the frequency.)
If the command output indicates that the desired frequency is on the list of preferred or allowed
frequencies, go to substep b.
If the desired frequency is not on the list, use the set
freq command to specify the desired frequency as
the device’s primary frequency, and then restart.
b Use the set log hello 3 or (Telnet
only) debug on command to
observe frequency hunting in real time. The log will tell you whether
the device is switching to the
desired frequency.
Note that after attempting each
allowed frequency twice, the device opens up to all
frequencies.
If the log confirms that the device is switching to the desired frequency, go to step 2.
If the log does not show the device switching to
the desired frequency, use the set freq command to specify the desired frequency as the primary
frequency, and then restart.
2 Check whether the device is detecting signals from other devices:
a
Use the show link command to find out whether the device is also
receiving hello packets from a
SkyGateway or SkyExtenders.
If the command output indicates that the device is not hearing a SkyGateway or any SkyExtenders, go
to substep b.
If the output confirms that the device is hearing a
SkyGateway or one or more SkyExtenders, go to step 3.
Getting Started with the SkyPilot Network 49
b Use the set log hello 3 or (Telnet
only) debug on command to
observe frequency hunting in real
time.
The log will tell you whether the device is receiving hello packets
from other devices when it
switches to the desired frequency.
If the log indicates that the device is switching to the desired frequency but failing to receive hello
packets, go to substep c.
If the log confirms that the device is switching to
the desired frequency and also receiving hello
packets from other devices, go to step 3.
c Adjust the device mount for improved signal reception and
display the log again as in
substep b.
If the log indicates that the device is still not receiving hello packets, try additional mounting
points. If the device still fails to receive hello packets,
go to substep d.
If the log confirms that the device is now receiving hello packets, secure the mount and restart the
device.
d Move the device to an alternate site with proven coverage (for example, next to a connected
device) and display the log again
as in substep b.
If the log confirms that the device is now receiving hello packets, add an intermediary SkyExtender to improve signal coverage at the device’s original
location.
If the log indicates that output is significantly lower
than shown by other devices operating at this location, contact SkyPilot customer support.
3 Check whether the device is failing to start optimization:
a Use the show link command to see if the MAC addresses heard by the device are remaining inactive.
Look for evidence of link states
that have changed from inactive
to non-opt (non-optimized).
If the command output fails to show inactive links
that have changed to the non-opt state, go to
substep b.
If the output shows non-opt states, the device is
starting link optimization. Go to step 4.
b Use the set log link 3 or (Telnet
only) debug on command to
If the log fails to show inactive links changing to
Getting Started with the SkyPilot Network 50
observe link state changes in real
time. Look for link states that
change from inactive to non-opt.
non-opt links, go to substep c.
If the log shows inactive links changing to non-opt
links, the device is starting link optimization. Go to
step 4.
c Use the show link opt command to view a table displaying average
RSSI and the number of hello
packets the device is hearing. (The device will not attempt to
optimize a link until it hears 5
packets.)
An RSSI value of less than 10 on the optimal antenna pair indicates
a weak signal. An RSSI value of 20
or greater is preferred.
If the table shows a low RSSI value (less than 10), the signal is probably too weak for the device to
attempt optimization. Go to substep d.
If the table indicates a threshold RSSI value (10 or
greater), the signal should be strong enough for the device to attempt optimization. The problem is
likely related to local radio interference, which can
reduce the number of packets the device can hear. Monitor the area for sources of interference and
retest.
d Adjust the device mount for improved signal reception and
display the table again as in
substep c.
If the table shows RSSI values less than 10, try additional mount adjustments. If the device
continues to display RSSI values less than 10, go to
substep e.
If the table shows that RSSI is now 10 or greater,
secure the mount and restart the device.
e Move the device to an alternate site with demonstrated signal
coverage (for example, next to a connected device) and display
the table again as in substep c.
If the table shows RSSI values of 10 or greater, add an intermediary SkyExtender to improve signal
coverage at the device’s original location.
If the table indicates that output is significantly lower than shown by other SkyPilot devices
operating at this location, contact SkyPilot
customer support.
4 Check whether the device is failing to complete link optimization:
Getting Started with the SkyPilot Network 51
a Use the show link command to see if the MAC addresses heard by
the device have ever reached the
pre-auth (pre-authorized) state, which indicates optimized links.
If the command output does not show pre-auth states, go to substep b.
If the output shows pre-auth link states, the device
is able to optimize links. Go to step 5.
b Use the set log link 3 or (Telnet
only) debug on command to
observe link state changes in real
time. Look for link states that
change from non-opt to pre-
auth.
If the log fails to show non-opt links changing to
pre-auth links, go to substep c.
If the log shows non-opt links changing to pre-
auth links, the device is successfully optimizing
links. Go to step 5.
c Use the show link opt command to view a table displaying average RSSI and the number of hello
packets the device is hearing. (The
device will not complete optimization of a link until it hears
5 packets.)
If the table shows a low RSSI value (less than 10), the signal is probably too weak for the device to attempt optimization. Go to substep d.
If the table indicates a threshold RSSI value (10 or greater), the signal should be strong enough for
the device to complete optimization. The problem is likely related to local radio noise that’s interfering
with SkyPilot signals. (Local radio interference on
either side of the link can reduce the number of
packets a device can hear and prevent it from completing optimization.) Monitor the area for
sources of interference and retest.
Getting Started with the SkyPilot Network 52
d Adjust the device mount and display the table again as in
substep c.
If the table shows RSSI values remaining below 10, try additional mount adjustments. If the device
continues to display RSSI values less than 10, go to substep e.
If the table shows that RSSI is now 10 or greater on the optimal antenna pair, secure the mount and
restart the device.
e Move the device to an alternate site with demonstrated signal
coverage (for example, next to a
connected device) and display
the table again as in substep c..
If the table shows RSSI values of 10 or greater, add an intermediary SkyExtender to improve signal
coverage at the device’s original location.
If the table indicates that output is significantly
lower than shown by other SkyPilot devices
operating at this location, contact SkyPilot customer support.
5 Check whether the device is authenticating links:
a Use the show link command to see if the MAC addresses heard by
the device have ever reached a
standby state, which indicates
authorized links.
If authentication failures prevent
link states from reaching standby,
they will return to auth-fail and
inactive.
If the command output does not show any
standby states, go to substep b.
If the output shows standby states, the device is
successfully forming links and is probably looking
for alternates. Once the device exhausts attempts to form more links, it will choose an optimal
standby link as the active path and come online.
b Use the set log link 3 or (Telnet
only) debug on command to
observe link state changes in real
time. Look for link states that
change from pre-auth to
standby.
If the log fails to show pre-auth links changing to
standby links, go to substep c.
If the log shows pre-auth links changing to
standby links, the device is successfully forming
links and is probably looking for alternates. Once
the device exhausts attempts to form more links, it
Getting Started with the SkyPilot Network 53
will choose an optimal standby link as the active
path and come online.
c Use the set log auth 3 or (Telnet
only) debug on command to
observe authorization events in
real time. Look for reports of
authentication failure due to timeouts or mismatched netkeys.
If the log reports any failure to authenticate due to timeouts or mismatched keys, go to substep d.
If the log reports successful authentication, the problem may be with provisioning. Go to step 6.
d Use the verifykey command to confirm the presence of a SkyPilot
private key for the device.
If a private key exists, go to substep e.
If no private key exists, contact SkyPilot and obtain a private key.
e Use the show netkey command to confirm that the hashed
equivalent of the netkey is identical to the value on all other
connected devices.
Mismatching keys will cause
authentication to fail.
If the netkeys do not match, use the set netkey command to modify the public key so that it
matches the key used by other devices on the
network. Restart the device.
If the netkeys match and the device continues to report authentication failures, contact SkyPilot
customer support.
6 Check whether the problem is related to a conflict due to configuration:
a Use the show link command to see if the MAC addresses heard by
the device have ever reached a
standby state.
If authentication is successful but
link states fail to change from pre-
auth to standby, they will return
to prov-fail and eventually go
back to inactive.
If the command output does not show standby states, go to substep b.
If the output shows standby states, the device is
successfully forming links and is probably looking for alternates. Once the device exhausts attempts
to form more links, it will choose an optimal
standby link as the active path and come online.
Getting Started with the SkyPilot Network 54
b Use the set log link 3 or (Telnet
only) debug on command to
observe link state changes in real
time. Look for link states that
change from pre-auth to
standby.
If the log fails to show pre-auth links changing to
standby links, go to substep c.
If the log shows pre-auth links changing to
standby links, the device is successfully forming
links and is probably looking for alternates. Once
the device exhausts attempts to form more links, it
will choose an optimal standby link as the active
path and come online.
c If the SkyGateway’s configuration
parameters do not match the frequency or domain settings of
the SkyGateway or SkyExtender it
is using to form links, devices will sever the links before connections
can be made.
Use the show prov command to
confirm that the SkyGateway’s
configuration settings for frequency and/or domain match
the frequency and/or domain it is
trying to use.
If the command output shows mismatched
configuration information, modify the configuration to allow the SkyGateway’s frequency
and/or domain and retest.
If the provisioning information matches the
SkyGateway’s frequency and/or domain and the device is still reporting provisioning failures, contact
SkyPilot customer support.
Device failing to form links (automatic provisioning)
This subsection addresses problems that an automatically provisioned SkyPilot device might have forming links that allow it to connect with other devices on the wireless network.
1 Check whether the device is listening on the correct frequency:
a Initially, a SkyPilot device scans for frequencies that are on its list of
preferred or allowed frequencies.
If the command output indicates that the desired frequency is on the list of preferred or allowed
frequencies, go to substep b.
Getting Started with the SkyPilot Network 55
Use the show prov freq command to verify that the
desired frequency is on the list.
If the desired frequency is not on the list, use the set
freq command to specify the desired frequency as
the device’s primary frequency, and then restart.
b Use the set log hello 3 or (Telnet
only) debug on command to
observe frequency hunting in real
time. The log will tell you whether
the device is switching to the desired frequency.
Note that after attempting each allowed frequency twice, the
device opens up to all
frequencies.
If the log confirms that the device is switching to the desired frequency, go to step 2.
If the log does not show the device switching to
the desired frequency, use the set freq command
to specify the sought frequency as the primary
frequency, and then restart.
2 Check whether the device is detecting signals from other devices:
a
Use the show link command to find out whether the device is also
receiving hello packets from a SkyGateway or SkyExtenders.
If the command output indicates that the device is not hearing a SkyGateway or any SkyExtenders, go to substep b.
If the output confirms that the device is hearing a SkyGateway or one or more SkyExtenders, go to
step 3.
b Use the set log hello 3 or (Telnet
only) debug on command to
observe frequency hunting in real
time.
The log will tell you whether the
device is receiving hello packets for other devices when it switches
to the desired frequency.
If the log indicates that the device is switching to the desired frequency but failing to receive hello
packets, go to substep c.
If the log confirms that the device is switching to the desired frequency and also receiving hello
packets from other devices, go to step 3.
c Adjust the device mount for improved signal reception and
If the log indicates that the device is still not receiving hello packets, try additional mounting
Getting Started with the SkyPilot Network 56
display the log again as in
substep b.
points. If the device still fails to receive hello packets,
go to substep d.
If the log confirms that the device is now receiving hello packets, secure the mount and restart the
device.
d Move the device to an alternate site with proven coverage (for example, next to a connected
device) and display the log again
as in substep b.
If the log confirms that the device is now receiving hello packets, add an intermediary SkyExtender to improve signal coverage at the device’s original
location.
If the log indicates that output is substantially lower
than shown by other SkyPilot devices at this
location, contact SkyPilot customer support.
3 Check whether the device is failing to start optimization:
a Use the show link command to see if the MAC addresses heard by
the device are remaining inactive. Look for evidence of link states
that have changed from inactive
to non-opt (non-optimized).
If the command output fails to show inactive links
that have changed to non-opt states, go to
substep b.
If the output shows non-opt states, the device is
starting link optimization. Go to step 4.
b Use the set log link 3 or (Telnet
only) debug on command to
observe link state changes in real
time. Look for link states that
change from inactive to non-opt.
If the log fails to show inactive links changing to
non-opt links, go to substep c.
If the log shows inactive links changing to non-
opt links, the device is starting link optimization. Go
to step 4.
c Use the show link opt command to view a table displaying average
RSSI and the number of hello
packets the device is hearing. (The
device will not attempt to optimize a link until it hears 5
If the table shows a low RSSI value (less than 10), the signal is probably too weak for the device to
attempt optimization. Go to substep d.
If the table indicates a threshold RSSI value (10 or
greater), the signal should be strong enough for
the device to attempt optimization. The problem is
Getting Started with the SkyPilot Network 57
packets.)
An RSSI value of less than 10 on
the optimal antenna pair indicates a weak signal. An RSSI value of 20
or greater is preferred.
likely related to local radio noise that’s interfering
with SkyPilot signals. (Local radio interference can reduce the number of packets the device can
hear.) Monitor the area for sources of interference
and retest.
d Adjust the device mount for improved signal reception and display the table again as in
substep c.
If the table shows RSSI values less than 10, try additional mount adjustments. If the device continues to display RSSI values less than 10, go to
substep e.
If the table shows that RSSI is now 10 or greater,
secure the mount and restart the device.
e Move the device to an alternate site with demonstrated signal
coverage (for example, next to a
connected device). and display the table again as in substep c.
If the table confirms RSSI values of 10 or greater, add an intermediary SkyExtender to improve signal
coverage at the device’s original location.
If the table indicates that output is significantly
lower than shown by other SkyPilot devices operating at this location, contact SkyPilot
customer support.
4 Check whether the device is failing to complete link optimization:
a Use the show link command to see if the MAC addresses heard by
the device have ever reached a
pre-auth (pre-authorized) state,
which indicates optimized links.
If the command output does not show pre-auth states, go to substep b.
If the output shows pre-auth link states, the device
is able to optimize links. Go to step 5.
b Use the set log link 3 or (Telnet
only) debug on command to observe link state changes in real
time. Look for link states that
change from non-opt to pre-
auth.
If the log fails to show non-opt links changing to
pre-auth links, go to substep c.
If the log shows non-opt links changing to pre-
auth links, the device is successfully optimizing links. Go to step 5.
Getting Started with the SkyPilot Network 58
c Use the show link opt command to view a table displaying average
RSSI and the number of hello
packets the device is hearing. (The device will not complete
optimization of a link until it hears
5 packets.)
If the table shows a low RSSI value (less than 10), the signal is probably too weak for the device to
complete optimization. Go to substep d.
If the table indicates a threshold RSSI value (10 or
greater), the signal should be strong enough for the device to attempt optimization. The problem is
likely related to local radio noise that’s interfering
with SkyPilot signals. (Local radio interference on either side of the link can reduce the number of
packets a device can hear and prevent it from
completing optimization.) Monitor the area for sources of interference and retest.
d Adjust the device mount and display the table again as in
substep c.
If the table shows RSSI values remaining below 10, try additional mount adjustments. If the device
continues to display RSSI values less than 10, go to substep e.
If the table shows that RSSI is now 10 or greater on the optimal antenna pair, secure the mount and
restart the device.
e Move the device to an alternate site with demonstrated signal
coverage (for example, next to a
connected device) and display the table again as in substep c..
If the table shows RSSI values of 10 or greater, add an intermediary SkyExtender to improve signal
coverage at the device’s original location.
If the table indicates that output is substantially
lower than shown by other SkyPilot devices operating at this location, contact SkyPilot
customer support.
5 Check whether the device is authenticating links:
a Use the show link command to see if the MAC addresses heard by
the device have ever reached a
standby state, which indicates
If the command output does not show any
standby states, go to substep b.
If the output shows standby states, the device is successfully forming links and is probably looking
Getting Started with the SkyPilot Network 59
authorized links.
If authentication failures prevent
link states from reaching standby,
they will return to auth-fail and
inactive.
for alternates. Once the device exhausts attempts
to form more links, it will choose an optimal
standby link as the active path and come online.
b Use the set log link 3 or (Telnet
only) debug on command to
observe link state changes in real time. Look for link states that
change from pre-auth to
standby.
If the log fails to show pre-auth links changing to
standby links, go to substep c.
If the log shows pre-auth links changing to
standby links, the device is successfully forming
links and is probably looking for alternates. Once the device exhausts attempts to form more links, it
will choose an optimal standby link as the active
path and come online.
c Use the set log auth 3 or (Telnet
only) debug on command to
observe authorization events in
real time.. Look for reports of
authentication failure due to timeouts or mismatched netkeys.
If the log reports any failure to authenticate due to timeouts or mismatched keys, go to substep d.
If the log reports successful authentication, the problem may be with provisioning. Go to step 6.
d Use the verifykey command to confirm the presence of a SkyPilot
private key for the device.
If a private key exists, go to substep e.
If no private key exists, contact SkyPilot and obtain
a private key.
e Use the show netkey command to confirm that the hashed
equivalent of the netkey is
identical to the value on all other
connected devices.
Mismatching keys will cause authentication to fail.
If the netkeys do not match, use the set netkey command to modify the public key so that it
matches the key used by other devices on the
network. Restart the device.
If the netkeys match and the device continues to
report authentication failures, contact SkyPilot customer support.
Getting Started with the SkyPilot Network 60
6 Check whether the device is failing to receive a configuration due to problems
related to DHCP:
a Use the show link command to see if the MAC addresses heard by
the device have ever reached a
standby state, which indicates
successful provisioning,.
If authentication is successful but
link states fail to change from pre-
auth to standby, they will return
to prov-fail and eventually go
back to inactive.
If the command output does not show standby states, go to substep b.
If the output shows standby states, the device is
successfully forming links and is probably looking
for alternates. Once the device exhausts attempts to form more links, it will choose an optimal
standby link as the active path and come online.
b Use the set log link 3 or (Telnet
only) debug on command to
observe link state changes in real
time. Look for link states that
change from pre-auth to
standby.
If the log fails to show pre-auth links changing to
standby links, go to substep c.
If the log shows pre-auth links changing to
standby links, the device is successfully forming
links and is probably looking for alternates. Once the device exhausts attempts to form more links, it
will choose an optimal standby link as the active
path and come online.
c An incorrect DHCP configuration will prevent the device from
obtaining its configuration from
the provisioning server.
Use the show dhcp command to
verify that the device is getting an IP address and other
configuration information from
the DHCP server.
If the command output indicates that the device received an IP address from the DHCP server, go to
step 7.
If the output indicates that the device is not getting
an IP address from the DHCP server, or that it’s
receiving incorrect information from the DHCP server, edit the DHCP content to include the correct
information and restart.
Getting Started with the SkyPilot Network 61
d Use the set log prov 3 or (Telnet
only) debug on command to
observe provisioning events in
real time. Monitor the DHCP server logs to confirm that the device
successfully made its request and
check the server’s response.
Note: that if you’re using the ISC
DHCP server, you can monitor
server output in real time by
tailing the /var/log/messages file.
If the log indicates that the device received an IP address from the DHCP server, go to step 7.
If the log indicates that the device is not getting an
IP address and other configuration information
from the DHCP server, or that it is receiving incorrect information from the DHCP server, edit
the DHCP content to include the correct
information and restart.
7 Check whether the problem is related to unsuccessful provisioning:
a Use the show link command to see if the MAC addresses heard by
the device have ever reached a
standby state., which indicates
successful provisioning.
If authentication is successful but
link states fail to change from pre-
auth to standby, they will return
to prov-fail and eventually go
back to inactive.
If the command output does not show standby states, go to substep b.
If the output shows standby states, the device is successfully forming links and is probably looking
for alternates. Once the device exhausts attempts
to form more links, it will choose an optimal
standby link as the active path and come online.
b Use the set log link 3 or (Telnet
only) debug on command to
observe link state changes in real
time. Look for link states that
change from pre-auth to
standby.
If the log fails to show pre-auth links changing to
standby links, go to substep c.
If the log shows pre-auth links changing to
standby links, the device is successfully forming
links and is probably looking for alternates. Once
the device exhausts attempts to form more links, it
will choose an optimal standby link as the active
path and come online.
c If the device’s configuration If the command output does not show
Getting Started with the SkyPilot Network 62
parameters do not match the
frequency or domain settings of the SkyGateway or SkyExtender it
is using to form links, devices will
sever the links before connections
can be made.
Use the show config command to confirm that the device has
completed provisioning and view
the configuration parameters.
configuration parameters, SkyProvision may have
no record of the SkyGateway. Go to substep d.
If the output shows mismatched configuration information, modify the configuration to allow the
SkyGateway’s frequency or domain and retest.
d Use the set log prov 3 or (Telnet
only) debug on command to
observe provisioning events in
real time. Look for reports of
failure to download the device’s configuration file, or rejection of a
link’s domain or frequency based
on the contents of the device configuration.
Note: You can verify that SkyProvision is offering a
configuration file by monitoring
the /var/log/messages file, which contains a log of SkyProvision
configuration transactions.
If the log reports failures related to the domain and frequency values stored in the device’s
configuration file, edit the settings to include the
correct values and restart the device.
If the log does not report any offering of a
configuration file, verify that the device’s information has been correctly added into
SkyProvision and retest.
If you confirm that the provisioning server is
sending the correct configuration file to the device but the device continues to report that that the file
was not offered, or that the device continues to
sever links, contact SkyPilot customer support.
Getting Started with the SkyPilot Network 63
A c c e s s i n g t h e C o m m a n d - L i n e I n t e r f a c e This appendix describes how to access the command-line interface that all SkyPilot devices provide for provisioning and monitoring.
You can connect to a device and access the command-line interface through Telnet over an Ethernet connection, or (for SkyGateway and SkyExtender only) via a
terminal session from a console connected to the device’s RJ-45 serial port. After
logging in (by supplying a password), you can enter commands at the command prompt.
Getting access via Ethernet
1 Prepare a PC or laptop.
Open the network settings panel and assign the computer an IP address in the range 192.168.0.3 to 192.168.0.254 and a subnet mask of 255.255.255.0.
NOTE All SkyExtenders and SkyConnectors ship with the default IP address 192.168.0.2.
2 Connect the computer to the SkyPilot device.
Use an Ethernet crossover cable (provided) to connect the computer to the
power injector.
Connect the Ethernet straight-through cable (provided) between the power injector and the Ethernet port on the base of the SkyGateway or SkyExtender.
Plug the AC adapter into the power injector.
A
Getting Started with the SkyPilot Network 64
Figure 10. Connecting a computer to a SkyGateway/SkyExtender via Ethernet
3 Start a Telnet session.
From Telnet, connect to the device by supplying its IP address.
4 Log in by entering the password at the command prompt. (The default is public.)
Getting access via a serial connection (SkyGateway/SkyExtender only)
1 Connect the console to the SkyPilot device.
Getting Started with the SkyPilot Network 65
Plug the DB-9 adapter into a serial port on the console.
Plug one end of the serial straight-through cable (provided) into the DB-9 adapter and the other end into the RJ-45 serial port under the base of the SkyGateway or SkyExtender.
Connect the Ethernet straight-through cable (provided) between the power injector and the Ethernet port on the base of the SkyGateway or SkyExtender.
Figure 11. Making a serial port connection to a SkyGateway/SkyExtender
Getting Started with the SkyPilot Network 66
2 Start a communications session.
From the console, start a terminal emulation program (for example, HyperTerminal or the open-source terminal client Tera Term).
Select the COM port you used to physically connect the console to the device.
Connect to the SkyPilot device using these serial communication settings:
38400 bps, 8 data bits, no parity, one stop bit, no flow control.
3 Log in by entering the default password (public) at the command prompt.