FR-0143 - FW - Rel - Notes - SP - 1 8 - Rev 1.1 2013-04-02

LIMITED DISTRIBUTION
TRILLIANT CUSTOMER USE ONLY
FIRMWARE RELEASE NOTES

SKYPILOT SYSTEM EMBEDDED SOFTWARE / FIRMWARE RELEASE NOTES
V1.8
P/N FR-0143 REV. 1.1

2 APR 2013
The SkyPilot v1.8 firmware release introduces new functionality as well as corrects some known bugs or
limitations. Specific details are provided here.
1 INTRODUCTION
This document supplements the SkyPilot System product documentation and describes the
capabilities and known limitations of the v1.8 release of the SkyPilot System Embedded Software, i.e.
SkyPilot Firmware. Note that the SkyControl server software details are covered in separate
SkyControl Software Release Notes.
This Release Note should be used in combination with the following user documentation:
Getting Started Guide
Getting Started in Auto Mode Guide
SkyPilot Gateway and SkyPilot Extender Installation Guide
SkyPilot Gateway Pro Installation and Setup Guide
SkyPilot Connector Outdoor Installation Guide
SkyPilot Extender Dualband
SkyPilot Connector Dualband Installation Guide
CLI and Web Reference Guides
Network Admin Guide
As Trilliant wants to provide its customers with the most up-to-date information, be sure to check the SkyPilot by
Trilliant web site at http://skypilot.trilliantinc.com for the latest documentation and software releases. For support
with your SkyPilot System, please see http://skypilot.trilliantinc.com/support or email SkyPilot at
skypilotsupport@trilliantinc.com.
FR-0143_FW_rel_notes_SP_1 8_ rev 1.1 2013-04-02

Trilliant Inc. Confidential Information
page 1 of 22
2 SYSTEM IMAGES
These Release Notes refer to version 1.8 of the SkyPilot System Embedded Software, also known as
the SkyPilot firmware. The system images for this release are named as follows:
Product
File Name
SkyPilot Gateway Pro
GwPro_1.8.bin
SkyPilot Gateway
SkyPilot Gateway DualBand
SkyPilot Gateway TriBand
SkyGate_1.8p1.bin
SkyPilot Extender
SkyPilot Extender DualBand
SkyPilot Extender TriBand
SkyExt_1.8p1.bin
SkyPilot Connector Indoor

SkyPilot Connector Outdoor
SkyConn_1.8.bin
SkyPilot Classic Connector DualBand
SkyAcc_1.8.bin
SkyPilot Connector
Conn_1.8.bin
SkyPilot Connector DualBand
ConnDb_1.8.bin
SkyPilot Connector Mini

SkyPilot Connector Pro
SyncMesh Client
SkyMini_1.8.bin
Extender DualBand Access Point

Extender TriBand Access Point
SkyAP_1.8.bin

page 2 of 22
3 WHATS NEW
Support for SkyPilot Gateway Pro

This firmware release introduces support for the SkyPilot Gateway Pro (SP-5230). For more information
on this product, see the SkyPilot by Trilliant website at http://skypilot.trilliantinc.com. This hardware
requires firmware revision 1.8 or greater and will not function with prior firmware releases. See the
compatibility matrix below for firmware and hardware revision interoperability.
Support for the new SkyPilot Gateway and Extender hardware revision -08R (SP-xx30 products)
This firmware release introduces support for the SkyPilot Gateway SP-6930, Extender SP-2530, and
Extender DualBand SP-2630 (i.e. hardware revision -08R). This hardware requires firmware revision 1.8
or greater and will not function with prior firmware releases. See section 7, Installation and Upgrade
Notes, for firmware and hardware revision interoperability.
000ADB020202> show version hw
Node type
: SkyPilot Gateway
System part no.
: 715-00011-08R
Serial no.
: FL01234567
CPLD Rev no.
: 00010000
Hardware revision
: G
Ethernet MAC
: 00:0A:DB:02:02:02
Switchboard Interface
: B
Switchboard Version
: 0x1
000ADB020202>
Support for SkyPilot Connector hardware revision -02

This firmware release introduces support for the SkyPilot Connector, and Connector DualBand hardware
revision -02. This hardware requires firmware revision 1.8 or higher and will not function with prior
firmware releases. See the compatibility matrix below for firmware and hardware revision interoperability.
Firmware / Hardware compatibility

Prior to deploying any new Gateway / Extender / Gateway Pro hardware revision -08R, all Connectors in
the network must be upgraded to firmware 1.8 or higher. Connectors running earlier firmware versions
will not be able to form an active link with -08R revision hardware. Gateways and Extenders are not
subject to this limitation.
See section 7, Installation and Upgrade Notes, for more information.
Support for network path distances greater than 20 miles

With previous firmware releases, the total path distance (i.e., the sum of the distances from the Gateway
to the first hop Extender and so on to the last hop) is constrained to be ~20 miles / ~32 km due to protocol
design. Any Extender exceeding this path distance would have reduced throughput, increased latency,
and increased packet loss.
With this firmware release, support is provided for path distances of over 100 miles. Note that the perhop limitation of approximately 10 miles / 16km remains unchanged. All SkyPilot Gateways,
Extenders, and Connectors in the network must have firmware release 1.8 or greater in order to support
the extension of the total path distance.

page 3 of 22
This feature can be enabled or disabled on the Gateway. With the path distance extension disabled, the
network will be backward-compatible with prior firmware releases. With the path distance extension
enabled, all devices in the network must have firmware release 1.8 or greater. Extender and Connector
devices, running firmware release 1.8 or greater, will transparently support networks with path distance
enabled or disabled, while also providing backward-compatibility with networks running prior firmware
releases.
When extended path distance support is enabled, additional network overhead requirements result in a
reduction in available network bandwidth of approximately 2.5%.
Path distance extension can be configured with the CLI commands show pathdistance, set prov
pathdistance, show prov pathdistance as shown below:
Syntax: set prov pathdistance [on/off]
Example output:
000ADB121212> show pathdistance
Path Distance Extension
: Enabled
000ADB121212> set prov pathdistance on
: Enabled
000ADB121212> set prov pathdistance off
: Disabled
000ADB121212> show prov pathdistance
: Disabled
This feature is supported by CLI commands only and is not yet implemented in EMS or the Web
Interface.
Antenna sector disable is now supported on Extender node types

With previous releases, only Gateway node types supported the ability to disable specific antenna sectors
on the device. This feature is useful when it is not desired to form links in a specific direction, or on
specific antenna sectors on the device. For example, if the device is installed on the side of a building,
where some antenna sectors face the building structure, it may be desirable to disable the antenna
sectors facing the building structure. With this release, this feature is also supported for Extender node
types.
Interface.
Example output:
000ADB121212> show antenna
Node has 8 antennas.
Enabled antennas
: 0 1 2 3 4 5 6 7
000ADB121212> show prov antenna

Enabled antennas
: 0 1 2 3 4 5 6 7
000ADB121212> set prov antenna
Enabled antennas are: 0 1 2 3 4 5 6 7
-> Select an antenna action: quit, enable or disable ? <q|e|d>: d
-> Enter antenna number <0..7>: 6

page 4 of 22

Enabled antennas are: 0 1 2 3 4 5 7
-> Select an antenna action: quit, enable or disable ? <q|e|d>: q
Please make sure to reboot for the new antenna disable settings to take effect.
000ADB121212> show prov antenna
Enabled antennas
: 0 1 2 3 4 5 7
Derived timing (GPS-less) support

With this firmware release, derived timing mode is now supported on the Extender and Extender
variants. This mode allows the Extender to operate without a GPS signal. This is useful for locations
where GPS coverage is unreliable due to obstruction or interference, for example, while testing indoors.
This mode can be selected and monitored on a per-device basis, using set prov gps, show prov gps and
show gps commands, as shown below.
Example output:
000ADB121212> set prov gps
-> Select user GPS action: quit, coordinates, timing <q|c|t>: t
GPS timing is enabled. Node is using GPS Timing.
-> Select GPS timing action: quit, enable, disable <q|e|d>: d
GPS timing is disabled. Node will use Derived Timing (GPS-less mode).
You must reboot for this change to take effect.
Note that GPS is always required for Gateway node types. It is possible to configure a Gateway for GPSless mode for testing and diagnostics only. Operation in this mode is not supported, and will often result
in reduced performance, increased latency and packet loss.
Interface.
Remaining DHCP lease time is now displayed in show dhcp output

With this release, the show dhcp command has been enhanced to include the remaining DHCP lease
time.
Example output:
000ADB121212> show dhcp
IP address
: 192.168.168.140
Subnet mask
: 255.255.255.0
Default gateway
: 192.168.168.2
Lease duration
: 3600 seconds
Lease rebinding
: 1350 sec
Lease remaining
: 1797 sec
DHCP server
: 192.168.168.2
Hostname
: GW-01
Identify when a link at modulation rate 6 has a high packet error rate
With this release, the show link command has been enhanced to indicate when a link at modulation rate
6 also has a high packet error rate. This is indicated by an asterisk next to the modulation rate in the
show link CLI output.

page 5 of 22
Example output:
000ADB121212> show link
MAC Address
NType State
LRSSI RRSSI LTxMod RTxMod LAnt RAnt
----------------- ----- --------- ------ ------ ------ ------ ---- ---00:0a:db:02:02:02 smext act mgmt 6
10
6*
9
5
5
Interface.
Packet error rate indicator included in show link state output

With this firmware release, the show link state command now includes a field for the packet error rate
indicator. This is an indication of the packet error rate over the past second, and therefore the health of
the link, which is approximately equal to the packet error rate as a percentage.
The packet error rate indication is used in modulation rate selection. If the packet error rate is
consistently low, modulation rates will be increased, to improve the capacity of the link. If the packet error
rate is high, the modulation rate will be decreased, to improve the reliability of the link.
Example output:
MAC Address
NType
----------------- ----00:0a:db:02:02:02 smext
state
State
LAnt RAnt Mod Freq TxPower RxGain Range
Path Dst PER
--------- ---- ---- --- ---- ------- ------ ---------- -------- -----act path 5
5
54 5900 13
7800
11200
6
MAC Address
Link Uptime
Downed Time
First Opt Time
Num Opt
----------------- -------------------- -------------------- -------------------- ------00:0a:db:02:02:02 JAN 01 1970 03:38:38 JAN 01 1970 03:37:40 JAN 01 1970 03:37:40 1
Overall path distance included in show link state output

With this firmware release, the show link state command now includes a field for the link path distance, in
addition to the existing range field. This field will reflect the path distance, in meters, of all links in the
path back to the Gateway, while the range field reflects only the distance to the immediate parent device.
Example output:
MAC Address
NType
----------------- ----00:0a:db:02:02:02 smext
state
State
LAnt RAnt Mod Freq TxPower RxGain Range
Path Dst PER
--------- ---- ---- --- ---- ------- ------ ---------- -------- -----act path 5
5
54 5900 13
7800
11200
6
MAC Address
Link Uptime
Downed Time
First Opt Time
Num Opt
----------------- -------------------- -------------------- -------------------- ------00:0a:db:02:02:02 JAN 01 1970 03:38:38 JAN 01 1970 03:37:40 JAN 01 1970 03:37:40 1
New CLI command: show link monitor

A new CLI command has been added to monitor links. This will repeat the show link command, once a
second, for the specified interval. This command is useful when waiting for a link to change status, or
when adjusting device alignment to obtain optimum signal strength. The command can be stopped prior
to the completion time by pressing Enter.
Syntax: show link monitor [seconds] [MAC]
Default values: show link monitor 60 ALL

page 6 of 22
Example output:
000ADB121212> show link monitor 30 000adb020202
MAC Address
NType State
LRSSI RRSSI LTxMod RTxMod LAnt RAnt
----------------- ----- --------- ------ ------ ------ ------ ---- ---00:0a:db:02:02:02 smgw act path 33
34
54
48
1
1
00:0a:db:02:02:02 smgw
act path
33
34
54
48
00:0a:db:02:02:02 smgw
act path
33
34
54
48
00:0a:db:02:02:02 smgw
act path
34
34
54
48
00:0a:db:02:02:02 smgw
act path
34
34
54
48
00:0a:db:02:02:02 smgw
act path
34
34
54
48
00:0a:db:02:02:02 smgw
act path
34
34
54
48
Monitor mode exited by keypress.

000ADB121212>
New CLI command: show noisefloor

A new CLI command has been added to show the noise floor, as measured by the radio chipset.
Syntax: show noisefloor
Example output:
000ADB121212> show noisefloor
Current calibration interval
Last 5 values, oldest-newest
Average
Programmed noise floor value
Operational range
:
:
:
:
:
60 seconds
-99dBm -99dBm -99dBm -98dBm
-98.800003dBm
-98dBm
Min: -111dBm, Max: -62dBm
-99dBm
000ADB121212>
Interface.
Route cost penalty for links over 10 miles (16 km)

The SkyPilot protocol is designed to support a per-hop maximum distance of 10 miles. For any link
exceeding this distance, the timing may be compromised, leading to an increase in packet loss and a
decrease in bandwidth available on the link.
With previous firmware releases, a link exceeding 10 miles, with a low hop count, would in some cases be
selected over shorter distance links, involving a higher hop count.
With this firmware release, a route cost penalty of 20% plus 2% for each 150 meters over 16.05 km, is
applied to the route cost of any individual link with a distance of over 16 km. This penalty will cause a
node, and its children, to prefer paths with individual links shorter than 16 km.
The original and adjusted route cost can be seen with the show mesh route command.

page 7 of 22
Example output for a 22.5 km link:

MAC Address
NType
----------------- ----00:0a:db:02:02:02 smgw
000ADB121212> show
Mesh Gateway
----------------00:0a:db:02:02:02
state
State
LAnt RAnt Mod Freq TxPower Range
--------- ---- ---- --- ---- ------- ---------act path 0
0
6
5735 13
22500
mesh route
Next Hop
----------------00:0a:db:02:02:02
Raw Cost
-------128
Adj Cost
-------240
Simplified frequency region selection

With previous firmware releases, switching operating frequency band (region) required contacting
support or use of a frequency change certificate.
With this firmware release, alternative operating frequency regions can be selected with the show prov
freq CLI command. For example, customers in the USA can select between US-HI band (5.7-5.8Ghz),
US-MID band (5.5-5.7Ghz) and US-LOWMID band (5.2-5.3Ghz). Please see the supplemental
document, DP-1309 WAN Frequency and Region Selection Guide, for details.
Support for additional countries and regions

With this firmware release, support has been added for many additional countries and regions, including
support for additional frequencies for some countries. Please see the supplemental document, DP-1309
WAN Frequency and Region Selection Guide, for details.
ETSI radar detection definitions updated to v1.5.1

With this firmware release, radar detection signatures for ETSI regions have been updated to conform to
the ETSI v1.5.1 specification.
Web interface updated to support newer web browsers

With this firmware release, the web interface has been updated to provide improved reliability and support
for a broader range of web browsers.
Unified web interface for the Extender DualBand and TriBand

With previous firmware releases, the web interface for the Extender DualBand and TriBand Access Point
was independent from the web interface for the Extender.
With this firmware release, there is a single, unified web interface, for both the Extender and AP
components.
The URL to access the web interface is same as the Extender web interface in previous releases:
End-user page: http://ip-address/
(example: http://192.168.0.2)
Admin pages: http://ip-address/admin
(example: http://192.168.0.2/admin)
SNMP community string can be defined for each trap destination

With previous firmware releases, the SNMP community string for SNMP traps was configured globally, for
all trap receivers.
With this firmware release, the SNMP community string can be defined independently for each trap
receiver.

page 8 of 22
Example output:
000ADB121212> set prov snmp
-> Select an SNMP action: quit, read-write enable,
read-only enable, disable, modify <q|w|r|d|m>: m
-> Select modification: back, read-write, read-only,
trap receivers, quit <b|w|r|t|q>: t
-> Select a trap action: back, add, delete, list, quit <b|a|d|l|q>: a
-> Enter trap destination IP address: 192.168.168.254
IP address entered: 192.168.168.254
-> Enter port number (1 - 65535): 162
Port number entered: 162
-> Enter trap destination Community: private
Trap community entered: private
-> Select a trap action: back, add, delete, list, quit <b|a|d|l|q>: l
Row
IP Address
Port
Community
-----------------------------1
192.168.168.2
162
public
2
192.168.168.254
162
private
-> Select a trap action: back, add, delete, list, quit <b|a|d|l|q>: q
000ADB121212>
Interface.
Preferred Gateway
In a network with multiple Gateways operating on the same frequency, it may be desirable to define a
preferred Gateway for a child device, independent of the immediate parent node. This feature
compliments the preferred parent setting, and facilitates network tuning at a higher level.
For example, in the following topology, it may be desirable to configure Extender C to prefer Gateway A,
without setting a preference for Extender A or Extender B.
Extender A
Extender D
/
\
/
\
Gateway A
Extender C
Gateway B
\
/
Extender B
Syntax: set prov prefgw MAC

Where MAC is the MAC address of the preferred Gateway, or 000000000000 to clear the preferred
Gateway.
The preferred Gateway can be configured as follows:
000ADB121212> set prov prefgw 000adb010203
000ADB121212> show prov node
Provisioning state
Domain
Power mode

: manual
: ALL
: Full power
page 9 of 22
Radar detection
Preferred parent
Preferred gateway
Auto save
:
:
:
:
Disable
00:00:00:00:00:00
00:0a:db:01:02:03
Disabled
000ADB121212>
Interface.
Ability to place a Gateway offline

With this firmware release, it is now possible to place a Gateway in offline mode (disable the Gateway) via
CLI command. This is useful when it is desired to have the Gateway powered, but not transmitting over
the air.
This can be achieved with the set gateway disable and conversely, set gateway enable, CLI commands,
as seen below. While the gateway is disabled, it will not transmit or receive wireless data. Any existing
links will be dropped, and new links will not form. If the Gateway is set to disabled state, it will remain in
this state, even after reboot or power cycle, until the Gateway is enabled once again with the set gateway
enable CLI command.
Example output:
00ADB121212> set gateway disable
Gateway is now disabled.
Gateway is disabled> set gateway enable
Gateway is now enabled.
000ADB121212>
Interface.
Backhaul Ping
For network redundancy, networks are often deployed with Gateways at different physical locations with
overlap between the mesh networks. In this configuration, if a Gateway fails, all nodes routing through
that gateway could failover to the alternate Gateway.
However, with previous firmware releases, if the backhaul or backhaul link at the Gateway location fails,
the nodes don't failover because their chosen Gateway is still up and running. The end result is typically
loss of service due to the stranded nodes.
With this firmware release, support has been introduced for backhaul ping. This feature, which can be
configured on Gateway node types, will ping up to two IP addresses in order to monitor backhaul
connectivity. If the ping fails for a configurable number of consecutive attempts, the Gateway will disable
itself, dropping all wireless links, enabling child nodes to fail over to an alternative Gateway.
When backhaul connectivity is restored, and the ping succeeds for the configured number of consecutive
attempts, the Gateway will re-enable itself, and will once again be available for child devices to form links.
The ping rate is approximately one every five seconds, therefore the default setting of 12 attempts is
approximately 60 seconds.
Backhaul ping can be configured with set bhping and set prov bhping, as follows:

page 10 of 22
000ADB121212> set prov bhping

Enter status (e = enable, d = disable) [disable]: e
Backhaul ping is enabled.
Enter first IP address [0.0.0.0]: 192.168.168.2
Enter second IP address [0.0.0.0]:
Enter ping retries [12]:
000ADB121212> show prov bhping
Status
: Enable
IP address 1
: 192.168.168.2
IP address 2
: 0.0.0.0
Max retry count
: 12
000ADB121212>
In the event of backhaul ping failure, the following will be displayed:

000ADB121212>
0x2a5f0 (spBbping): spBackbonePing.c:165 (SP_BBPING_COMPONENT_ID#1) Gateway is now
disabled due to backhaul ping failure.
Gateway disabled due to backhaul ping>
When the backhaul is restored and ping succeeds:

0x2a5f0 (spBbping): spBackbonePing.c:202 (SP_BBPING_COMPONENT_ID#1) Gateway is now
enabled due to backhaul ping success.
000ADB121212>
If needed, the Gateway can be manually enabled or disabled:

000ADB121212> set gateway disable
Gateway is now disabled.
Gateway is disabled>
Gateway is disabled> set gateway enable
Gateway is now enabled.
000ADB121212>
Interface.
Manual configuration of GPS coordinates

With this release, GPS coordinates can be manually configured for all node types. This can be used to
enter coordinates for Connector node types, which do not have GPS, or to override the GPS coordinates
for other node types.
GPS coordinates can be configured with set prov gps, set gps, show prov gps, and show gps as follows:
Example output:
1060WADDISON> set prov gps
-> Select user GPS action: quit, coordinates, timing <q|c|t>: c
-> Enter latitude in degree(s) decimal format (-90.0 to 90.0): 41.948276

page 11 of 22
-> Enter longitude in degree(s) decimal format (-180.0 to 180.0): -87.654973

GPS settings:
latitude = 41.948276
longitude = -87.654973
-> Select user GPS action: quit, coordinates, timing <q|c|t>:

1060WADDISON> show prov gps
Latitude : 41.948276 degrees
Longitude : -87.654973 degrees
1060WADDISON> show gps
Active GPS
Latitude
Longitude
Altitude
:
:
:
:
User Defined
41.948276 degrees
-87.654973 degrees
Not available
Hardware GPS Detail

------------------- Hardware GPS is locked.
- Hardware GPS coordinate is correct.
- Hardware Latitude : 41.947429 degrees
- Hardware Longitude : -87.656380 degrees
- Hardware Altitude : 601 feet
Hardware GPS Satellite Signal to Noise
-------------------------------------Is GPS locked:
Yes
Number of satellites: 9
Satellite Number |
SNR
10
|
41.00+
19
|
39.00+
28
|
35.00
7
|
31.00
11
|
-36.00
13
|
44.00+
23
|
25.00
8
|
-29.00
Average of the three largest signal strengths: 41.33
'+' Used for calculating average.
'-' No valid data from satellite.
1060WADDISON>
Region-specific power levels

With previous firmware releases, power levels were configured independent of the configured frequency
region, however, some frequency regions restricted the available power levels.
With this firmware release, power levels are now set based on the configured frequency region. There
are four power level settings available for each region:
Power Level
Keyword
Description
Full Power
full
The maximum transmit power allowed for the current

frequency region
Half Power (-3db)
half
3db less than the maximum transmit power allowed

for the current frequency region
Quarter Power (-6db)
quarter

for the current frequency region

page 12 of 22
Low Power
low

for the current frequency region, or the lowest output
power possible for the device.
The CLI now indicates the approximate output power in dBm EIRP for the full power setting for each
frequency region. The commands show freq, show prov freq, set freq, and set prov freq can be used to
show and set the frequency region. For example:
000ADB121212> show freq
Flash frequency region setting
: FCC-HI
- FCC High Band
Current frequency region setting : FCC-HI
- FCC High Band
Current valid frequencies
: 5735 5740 5745 5750 5755
5765 5770 5775 5780 5785
5795 5800 5805 5810 5815
5825 5830 5835
Current frequency
: 5755
Current allowed frequencies
: 5755
Dwell time (minutes)
: 30
5735-5835 42dBm EIRP

5735-5835 42dBm EIRP
5760
5790
5820
000ADB121212>
This firmware release will interpret the power setting from prior firmware releases or EMS releases as
follows:
If your previous setting was
The new setting will be
Default
Full Power
MAX
Full Power
4A (4 Watt Average)
Full Power
4P (4 Watt Peak)
Full Power
2A (2 Watt Average)
Half Power
1A (1 Watt Average)
Quarter Power
250mWa (250 Milliwatt Average)
Low Power
Prior to upgrade, please verify your current settings with this table.
Please see the supplemental document, DP-1309 WAN Frequency and Region Selection Guide, for
details on available frequency regions and power settings within the region.
Radar detection enable/disable based on frequency region

With this firmware release, radar detection will automatically be enabled or disabled as required, based
on the current frequency region. This will ensure radar detection is enabled when needed for regulatory
compliance in the selected frequency region, and ensure radar detection is disabled when not required.
The current radar detection status can be seen with show radar and show prov radar.
For Gateway node types, the radar detection action can be changed with set radar and set prov radar, as
with previous firmware releases. The available modes are Enabled with traffic shutdown and Enabled
with channel change.
For more information in radar detection, and to see which regions require radar detection, please see the
supplemental document, DP-1309 WAN Frequency and Region Selection Guide.

page 13 of 22
Gateway Pro 100BASE-FX fiber Ethernet support

The Gateway Pro provides both a 100BASE-TX RJ45 POE Ethernet port, and a 100BASE-FX SFP slot.
The show eth, set eth, show prov eth, and set prov eth commands have been enhanced to support status
and configuration of the 100BASE-FX Ethernet interface.
The RJ45 and Fiber Ethernet ports are bridged internally and must not be simultaneously connected to
the same network. Generally, only one interface must be used at a time.
For more information, see the SkyPilot Gateway Pro Installation and Setup Guide.

page 14 of 22
Extender DualBand and TriBand AP enhancements
Radio Policy
With previous firmware releases, the radio policy supported b-only and b/g modes.
With this release, radio policy now also supports g-only mode, also known as pure g mode. Thus,
there are now three options: b-only, b/g, or g-only.
Heartbeat Shutdown
When enabled, heartbeat shutdown will direct the AP to mirror the status of the Extenders backhaul
link. When the Extender portion of the device is connected to the network, the SSIDs will be enabled.
When the Extender portion of the device is not connected to the network, the SSIDs will be disabled.
This feature can allow WiFi clients to select an alternate AP which does have network connectivity,
rather than remaining connected to an AP which does not have backhaul connectivity.
This option can be enabled on a per-SSID basis.
ACK Distance
The ACK Distance parameter allows configuration of the maximum supported distance for WiFi client
devices. The value is specified in meters, with a valid range between 100 and 8000, or 0 for default
settings. A larger value allows connectivity to client devices which are a longer distance from the AP,
but may reduce overall throughput capability of the AP.
Dual Power
Many low-power WiFi client devices, such as laptops and cellular phones with WiFi, perform better
when the AP is also configured for a low transmit power. With a high power AP, the low power client
device may select a modulation rate which is too aggressive, resulting in high packet loss, high
latency, and reduced throughput. Reducing the AP power level allows the client device to select the
correct modulation rate for the link.
Dual Power mode allows the AP to transmit at low-power when communicating with low-power client
devices, while also transmitting at high-power, when communicating with high-power client devices.
The client device is identified as a high-power or low-power based on its MAC address.
The new configuration parameters are:
o
Low power level (100mw or 200mw)
High power level (300mw or 400mw)
High power MAC addresses (a list of MAC addresses or partial MAC addresses which
will be considered high-power devices)
This feature can be enabled on a per-SSID basis.
Inactivity Detection
This feature allows detection and automatic disconnection of inactive client devices. With previous
firmware releases, idle/inactive devices could remain connected to the AP indefinitely.

page 15 of 22
Max Inactivity
Maximum time, in seconds, before a client device is considered to be inactive and will be
disconnected due to inactivity
Begin Inactivity Probe

The AP will begin to poll the station for connectivity when it is x seconds from reaching Max
Inactivity seconds
Per-SSID Radius
With previous firmware, Radius configuration was configured on a global basis, for all SSIDs.
With this firmware, the Radius server IP address, port, and secret, can now be configured on a perSSID basis.
MAC Based Radius Authentication

This feature allows Radius authentication for client devices which are not capable of Radius/802.1x
authentication, and/or enables Radius authentication on open SSIDs. The stations MAC address will
be sent to the Radius server as the username and/or password.
o
MAC Based Radius Authentication

enable or disable
Username style
bare mac, colon separated mac, or hyphen separated mac (802.1x format)
Password style
bare mac, colon separated mac, hyphen separated mac (802.1x format), empty string, or
send no password field
This feature can be enabled on a per-SSID basis.

page 16 of 22
4 BUG FIXES
The following known bugs are corrected by this firmware release:
Bug #18183: Failure to upgrade AP Firmware from 1.5pX to 1.8 using auto provisioning
With this release, if a DualBand Extender AP is running any firmware version prior to 1.6 (i.e. 1.5pX or
1.4pX), auto provisioning will fail to configure the AP and will also fail to upgrade the AP firmware.
Workaround Upgrade the AP to firmware 1.8 prior to upgrading the Extender to firmware 1.8.
Alternatively, if the Extender firmware has already been updated to 1.8, the AP firmware can be updated
manually using the ftpimageap command on the Extenders CLI.
Bug #10598: Time zone offset handled incorrectly in some cases

With previous releases, the time zone offset could be handled incorrectly in some cases, resulting in
incorrect date or time display. This would occur in auto mode, when a time zone offset was configured
via set prov timezone, and also configured via node profile.
With this release, when in auto mode, only the time zone offset configured in the node profile will be
considered when calculating time zone offset.
Bug #10815: show ap commands do not show any output if the AP does not respond
With previous releases, if the 2.4 WiFi AP does not respond in a timely manner, show ap commands may
result in no output. This may occur if the AP has been reset and is in the process of booting.
With this release, if the 2.4 WiFi AP does not respond, the CLI will report that the AP is not responding.
Bug #11751: CLI Command help enhancement

With previous releases, some CLI commands were not displayed in the CLI help function, accessible by
entering help or a ? at the command prompt.
With this release, all available CLI commands are listed in the CLI help output.
Bug #11972: ACL logic incorrectly interprets netmask

With previous releases, ACL processing would consider any netmask entry as a netmask of
255.255.255.255, regardless of the intended netmask value.
With this release, ACL processing correctly handles all possible netmask values.
Bug #12379: show link modtrend missing from show tech output
With this release, show tech has been enhanced to include show link modtrend output.
Bug #12574: Incorrect frequency shown on the SkyPilot Connector Mini

With previous releases, the SkyPilot Connector Mini could display the incorrect current frequency in show
freq output. The device could, for example, display a current frequency of 5520, while the actual current
operating frequency is 5745.
With this release, show freq will indicate the actual current operating frequency.
Bug #13520: Web interface allows enabling management VLAN with ID 0 "untagged"

page 17 of 22
With previous releases, the web interface could allow the user to enable the management VLAN with a
VLAN ID of 0. However, 0 is not a valid VLAN ID.
With this release, the web interface will ensure a valid VLAN ID is entered when management VLAN
support is enabled.
Bug #13873: unable to make frame of 8 taus message logged

With previous releases, under some conditions, the message unable to make frame of 8 taus would be
logged while attempting to establish child links, as a result of incorrect ranging information.
With this release, the ranging information is validated prior to acceptance, and the error will no longer be
displayed.
Bug #13887: show link opt produces no output when there are no links
With previous releases, the show link opt command would produce no response if issued on a device with
no links.
With this release, if there are no links, show link opt will report that there are no links.
Bug #14142: RRSSI is never updated once link is active

With some previous releases, the remote RSSI (RRSSI) field is not updated once the link reaches active
state. This field is displayed in show link output and is also available via SNMP.
With this release, the remote RSSI field will be updated approximately every 20 seconds for each link.
Bug #14215: show prov node shows current value for domain, instead of setting in flash
With previous releases, show prov node would show the current active value for the devices domain.
With this release, show prov node will correctly show the configured value for domain, independent of the
current active value. The current value can be viewed with the show status command.
Bug #14615: Gateway is disabled message should be improved

With previous releases, when a Gateway is disabled by configuration, CLI command, or event, the
command prompt will display a generic Gateway is disabled message.
With this release, if the Gateway is disabled due to backhaul ping failure, the message Gateway disabled
due to backhaul ping will be displayed.
Bug #14716: In auto mode, domain setting in flash is ignored

With previous releases, when an Extender or Connector is configured for automatic provisioning, the
device will always start up with domain ALL. This will occur regardless of the domain value configured
through set prov domain or the node profile.
With this release, the device will honor the domain setting entered through set prov domain or the node
profile.
Bug #14786: Auto-save not functional on Gateway node types

With previous releases, the implementation of the configuration auto-save feature supported only
Extender and Connector node types.
With this release, auto-save is now also supported on Gateway node types.
Bug #14790: set prov gps does not save entered longitude value

page 18 of 22
With previous releases, in some cases the user supplied value for longitude is not saved correctly.
With this release, all valid GPS coordinates will be accepted and saved by the set prov gps command.
Bug #15032: tau sync events continuously reported

With previous releases, a device could enter a state where tau sync events are continuously logged, at
a rate of approximately one per second. While in this state, connectivity could be degraded, resulting in
increased packet loss. The device would typically recover from this state within a few hours.
With this release, the clock calibration logic has been improved, and the device will no longer
continuously generate tau sync events.
Bug #15054: 'set prov ip' may cause a reboot on the SkyPilot Connector DualBand
With previous releases, the set prov ip command may result in an unexpected reboot, on the SkyPilot
Connector DualBand. This can occur if the user presses enter at all prompts, without entering any data.
With this release, set prov ip will no longer cause a reboot.
Bug #15120: Valid VLAN ID range should be 1-4094, VID 4095 should not be allowed
With previous releases, a VLAN ID of 4095 could be selected, however, the 802.1q specification limits the
allowed range for VLAN ID to 1-4094, inclusive.
With this release, the accepted range for VLAN has been adjusted to 1-4094, inclusive, to match the
802.1q specification.
Bug #15268: Software scheduler not working under some conditions

With previous releases, if a software schedule is received via provisioning, prior to configuration of device
date/time via NTP, the scheduler would be considered invalid, and would not be honored. Upon reload of
the device, the software schedule would be honored.
With this release, the software schedule will be correctly processed, even if received prior to NTP time
sync.
Bug #15707: Repeat registration to update mac2ip table, if device IP address changes
With previous releases, if the devices IP address changes, via CLI command, or by a change of DHCP
assigned address, the previous IP address would continue to be reflected in the Gateways mac2ip table.
With this release, the mac2ip lookup table will be updated when a devices IP address changes. This
table can be viewed with the show mac2ip and show ip2mac commands on Gateway node types.
In addition, many minor issues were resolved with this release.

page 19 of 22
5 KNOWN LIMITATIONS/BUGS
The following known limitations are present in this firmware release:
Web interface not enabled/disabled on configuration reload

Result When enabling the web server interface via SkyControl, the feature isnt actually enabled until the
device is rebooted. The feature should be enabled upon reloading the configuration file (reload). Similar
behavior exists when disabling the feature.
Workaround Reboot the node to disable/enable this feature.
Software scheduler does not account for Daylight Savings Time

Result When using the software scheduler to program software upgrades for a specific date and time, while
the state of Daylight Savings Time (DST) may be known on the SkyControl server this information isnt known
on the device. The device maintains time according to Zulu Time (GMT). This may result in upgrades
occurring 1 hour before or after the scheduled time. This issue does not impact a node in Manual Provisioning
mode.
Workaround If DST is in effect, schedule the upgrade to occur 1 hour later.
th
Bug #15283: 11 hop Extender shows a flood of warning messages

With this release, an Extender 11 hops from the Gateway will flood the console and message logs with a
warning message More than 12 hops encountered. Cant add self. There is no operational impact beyond
the log messages.
Bug #16913: Telnet timeout parameter configured in EMS is not applied

With this release, the telnet timeout parameter can only be configured through the CLI. Parameter changes
made in the EMS will not be applied to the device.
Workaround Use the CLI command set prov telnet to configure the telnet timeout.
Bug #17001: Embedded web interface does not support the Chrome web browser
With this release, the Chrome web browser does not correctly display the menus of the embedded web
interface. As with previous firmware, Internet Explorer and Firefox are supported.
Workaround Utilize a supported web browser.
Bug #17186: Mini Connector may reroute due to route cost even when preferred parent is set
With this release, a SkyPilot Mini Connector may reroute due to a better cost link available, even when
preferred parent is configured.
6 PLANNED RESOLUTION OF LIMITATIONS/BUGS

As warranted, new firmware will be released to correct any newly discovered bugs or functional limitations.

page 20 of 22
7 INSTALLATION AND UPGRADE NOTES

For existing hardware, this firmware maintains backward compatibility with previous firmware releases;
therefore, no special upgrade or installation procedure is required.
This firmware release also introduces support for the new SkyPilot Gateway SP-6930, Extender SP-2530,
and Extender DualBand SP-2630 (i.e. hardware revision -08R). Prior to deploying the new Gateway /
Extender / Gateway Pro hardware revision -08R, all Connectors in the network must be upgraded to firmware
1.8+. Connectors running earlier firmware versions will not be able to form an active link with -08R revision
hardware. Gateways and Extenders are not subject to this limitation.
Gateway/
Extender
-07,
FW 1.5
Gateway Pro FW 1.8,
Gateway/Extender -08 FW 1.8+
Gateway/Extender -07,
FW 1.5 / FW 1.8+
Connector,
FW 1.5/1.6/1.7
Connector,
FW 1.8+
Gateway/
Extender
-07,
FW 1.8+
Gateway/
Extender
-08,
FW 1.8+
Gateway
Pro,
FW 1.8
Y = compatible
N = not compatible
Device hardware revision can be verified with the following command:
000ADB020202> show version hw
Node type
: SkyPilot Gateway
System part no.
: 715-00030-08R
Serial no.
: FL01234567
CPLD Rev no.
: 00010000
Hardware revision
: G
Ethernet MAC
: 00:0A:DB:02:02:02
Switchboard Interface
: B
Switchboard Version
: 0x1
000ADB020202>

page 21 of 22
APPENDIX PART NUMBERS

Trilliant SkyPilot firmware part numbers for this release are listed below.
Description
SkyPilot Gateway Pro (SP5230) Application Firmware
SkyPilot Gateway (SP-6900 and
SP-6930), SkyPilot Gateway
DualBand and SkyPilot Gateway
TriBand Application Firmware
SkyPilot Extender (SP-2500),
SkyPilot Extender DualBand,
and SkyPilot Extender TriBand
Application Firmware
SkyPilot Connector Indoor and
SkyPilot Classic Connector
(Outdoor) Application Firmware
SkyPilot Classic Connector
DualBand Application Firmware
SkyPilot Connector (SP-4700)
Application Firmware
SkyPilot Connector DualBand
(SP-3800) Application Firmware
SkyPilot Connector Mini (SP4500), SkyPilot Connector Pro
(SP-4600), and
SyncMesh Client Application
Firmware
Extender DualBand Access
Point, and
Extender TriBand Access Point
Access Point Firmware
firmware version
GwPro_1.8.bin
New part number

670-00037-02 rev 1.8
Previous Part Number

N/A
SkyGate_1.8.1.bin
670-00007-25 rev 1.8p1
670-00007-24 rev 1.5p10
SkyExt_1.8.1.bin
670-00008-25 rev 1.8p1
670-00008-24 rev 1.5p10
SkyConn_1.8.bin
670-00009-25 rev 1.8
670-00009-24 rev 1.5p10
SkyAcc_1.8.bin
670-00019-25 rev 1.8
670-00019-24 rev 1.5
Conn_1.8.bin
670-00028-02 rev 1.8
670-00028-01 rev 1.7p5
ConnDb_1.8.bin
670-00027-02 rev 1.8
670-00027-01 rev 1.7p5
SkyMini_1.8.bin
670-00023-03 rev 1.8
670-00023-02 rev 1.6.2
SkyAP_1.8.bin
670-00013-25 rev 1.8
670-00013-24 rev 1.5p10
Trilliant Incorporated
1100 Island Drive Redwood City, CA 94065 USA +1.650.204.5050 www.trilliantinc.com
Trilliant, CellReader , CellGateway, SecureMesh, SerViewCom , UnitySuite, SkyPilot , SyncMesh, the Trilliant logo, and the SkyPilot logo are trademarks of Trilliant Incorporated
and/or its subsidiaries. All other trademarks are the property of their respective owners. This material is provided for informational purposes only; Trilliant assumes no liability related to its
use and expressly disclaims any implied warranties of merchantability or fitness for any particular purpose.
All specifications, descriptions, and information contained herein are subject to change without prior notice.
Copyright 2011 Trilliant Incorporated. ALL RIGHTS RESERVED.

page 22 of 22

FR-0143 - FW - Rel - Notes - SP - 1 8 - Rev 1.1 2013-04-02

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

FR-0143 - FW - Rel - Notes - SP - 1 8 - Rev 1.1 2013-04-02

Transféré par

Droits d'auteur :

Formats disponibles

LIMITED DISTRIBUTION

TRILLIANT CUSTOMER USE ONLY

FIRMWARE RELEASE NOTES

P/N FR-0143 REV. 1.1

FR-0143_FW_rel_notes_SP_1 8_ rev 1.1 2013-04-02

SkyPilot Gateway Pro

SkyPilot Connector Indoor

SkyPilot Classic Connector DualBand

SkyPilot Connector DualBand

SkyPilot Connector Mini

Extender DualBand Access Point

FR-0143_FW_rel_notes_SP_1 8_ rev 1.1 2013-04-02

Support for SkyPilot Gateway Pro

Support for SkyPilot Connector hardware revision -02

Firmware / Hardware compatibility

Support for network path distances greater than 20 miles

FR-0143_FW_rel_notes_SP_1 8_ rev 1.1 2013-04-02

Antenna sector disable is now supported on Extender node types

000ADB121212> show prov antenna

FR-0143_FW_rel_notes_SP_1 8_ rev 1.1 2013-04-02

Node has 8 antennas.

Derived timing (GPS-less) support

Remaining DHCP lease time is now displayed in show dhcp output

FR-0143_FW_rel_notes_SP_1 8_ rev 1.1 2013-04-02

Packet error rate indicator included in show link state output

Overall path distance included in show link state output

New CLI command: show link monitor

FR-0143_FW_rel_notes_SP_1 8_ rev 1.1 2013-04-02

Monitor mode exited by keypress.

New CLI command: show noisefloor

Route cost penalty for links over 10 miles (16 km)

FR-0143_FW_rel_notes_SP_1 8_ rev 1.1 2013-04-02

Example output for a 22.5 km link:

Simplified frequency region selection

Support for additional countries and regions

ETSI radar detection definitions updated to v1.5.1

Web interface updated to support newer web browsers

Unified web interface for the Extender DualBand and TriBand

SNMP community string can be defined for each trap destination

FR-0143_FW_rel_notes_SP_1 8_ rev 1.1 2013-04-02

Syntax: set prov prefgw MAC

FR-0143_FW_rel_notes_SP_1 8_ rev 1.1 2013-04-02

Ability to place a Gateway offline

FR-0143_FW_rel_notes_SP_1 8_ rev 1.1 2013-04-02

000ADB121212> set prov bhping

In the event of backhaul ping failure, the following will be displayed:

When the backhaul is restored and ping succeeds:

If needed, the Gateway can be manually enabled or disabled:

Manual configuration of GPS coordinates

FR-0143_FW_rel_notes_SP_1 8_ rev 1.1 2013-04-02

-> Enter longitude in degree(s) decimal format (-180.0 to 180.0): -87.654973

-> Select user GPS action: quit, coordinates, timing <q|c|t>:

Hardware GPS Detail

Region-specific power levels

The maximum transmit power allowed for the current

Half Power (-3db)

3db less than the maximum transmit power allowed

Quarter Power (-6db)

6db less than the maximum transmit power allowed

FR-0143_FW_rel_notes_SP_1 8_ rev 1.1 2013-04-02

12db less than the maximum transmit power allowed

5735-5835 42dBm EIRP

The new setting will be