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

7/26/2019 FR-0143_FW_rel_notes_SP_1 8_ rev 1.1 2013-04-02

1/22

LIMITED DISTRIBUTION

TRILLIANT CUSTOMER USE ONLY

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

Trilliant Inc. Confidential Information page 1 of 22

FIRMWARE RELEASE NOTES

SKYPILOT SYSTEM EMBEDDED SOFTWARE/FIRMWARE RELEASE NOTES

V1.8

P/NFR-0143REV.1.1

2APR 2013

The SkyPilot v1.8 firmware release introduces new functionality as well as corrects some known bugs orlimitations. Specific details are provided here.

1 INTRODUCTION

This document supplements the SkyPilot System product documentation and describes thecapabilities 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 DualbandInstallation 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 byTrilliant web site at http://skypilot.trilliantinc.com for the latest documentation and software releases. For supportwith your SkyPilot System, please see http://skypilot.trilliantinc.com/support or email SkyPilot [email protected].


2/22





2 SYSTEM IMAGES

These Release Notes refer to version 1.8 of the SkyPilot System Embedded Software, also known asthe SkyPilot firmware. The system images for this release are named as follows:

Product File Name

SkyPilot Gateway Pro GwPro_1.8.bin

SkyPilot GatewaySkyPilot Gateway DualBandSkyPilot Gateway TriBand

SkyGate_1.8p1.bin

SkyPilot ExtenderSkyPilot Extender DualBandSkyPilot 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 MiniSkyPilot Connector ProSyncMesh Client

SkyMini_1.8.bin

Extender DualBand Access PointExtender TriBand Access Point

SkyAP_1.8.bin


3/22





3 WHATS NEW

Support for SkyPilot Gateway Pro

This firmware release introduces support for the SkyPilot Gateway Pro (SP-5230). For more informationon this product, see the SkyPilot by Trilliant website at http://skypilot.trilliantinc.com. This hardwarerequires firmware revision 1.8 or greater and will not function with prior firmware releases. See thecompatibility 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, andExtender DualBand SP-2630 (i.e. hardware revision -08R). This hardware requires firmware revision 1.8or greater and will not function with prior firmware releases. See section 7, Installation and UpgradeNotes, for firmware and hardware revision interoperability.

000ADB020202> show version hwNode type : SkyPilot GatewaySystem part no. : 715-00011-08RSerial no. : FL01234567

CPLD Rev no. : 00010000Hardware revision : GEthernet MAC : 00:0A:DB:02:02:02Switchboard Interface : BSwitchboard Version : 0x1

000ADB020202>

Support for SkyPilot Connector hardware revision -02

This firmware release introduces support for the SkyPilot Connector, and Connector DualBand hardwarerevision -02. This hardware requires firmware revision 1.8 or higher and will not function with priorfirmware 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 inthe network must be upgraded to firmware 1.8 or higher. Connectors running earlier firmware versionswill not be able to form an active link with -08R revision hardware. Gateways and Extenders are notsubject 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 Gatewayto the first hop Extender and so on to the last hop) is constrained to be ~20 miles / ~32 km due to protocoldesign. 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 per-hop 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 supportthe extension of the total path distance.


4/22





This feature can be enabled or disabled on the Gateway. With the path distance extension disabled, thenetwork will be backward-compatible with prior firmware releases. With the path distance extensionenabled, all devices in the network must have firmware release 1.8 or greater. Extender and Connectordevices, running firmware release 1.8 or greater, will transparently support networks with path distanceenabled or disabled, while also providing backward-compatibility with networks running prior firmwarereleases.

When extended path distance support is enabled, additional network overhead requirements result in areduction in available network bandwidth of approximately 2.5%.

Path distance extension can be configured with the CLI commands show pathdistance, set provpathdistance, show prov pathdistanceas shown below:

Syntax: set prov pathdistance [on/off]

Example output:

000ADB121212> show pathdistancePath Distance Extension : Enabled

000ADB121212> set prov pathdistance onPath Distance Extension : Enabled

000ADB121212> set prov pathdistance offPath Distance Extension : Disabled

000ADB121212> show prov pathdistancePath Distance Extension : Disabled

This feature is supported by CLI commands only and is not yet implemented in EMS or the WebInterface.

Antenna sector disable is now supported on Extender node types

With previous releases, only Gateway node types supported the ability to disable specific antenna sectorson 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 antennasectors facing the building structure. With this release, this feature is also supported for Extender nodetypes.


Example output:

000ADB121212> show antennaNode has 8 antennas.Enabled antennas : 0 1 2 3 4 5 6 7

000ADB121212> show prov antennaNode has 8 antennas.Enabled antennas : 0 1 2 3 4 5 6 7

000ADB121212> set prov antennaNode has 8 antennas.Enabled antennas are: 0 1 2 3 4 5 6 7

-> Select an antenna action: quit, enable or disable ? : d-> Enter antenna number : 6


5/22





Node has 8 antennas.Enabled antennas are: 0 1 2 3 4 5 7

-> Select an antenna action: quit, enable or disable ? : q

Please make sure to reboot for the new antenna disable settings to take effect.

000ADB121212> show prov antennaNode has 8 antennas.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 Extendervariants. This mode allows the Extender to operate without a GPS signal. This is useful for locationswhere 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 gpsandshow gpscommands, as shown below.

Example output:

000ADB121212> set prov gps-> Select user GPS action: quit, coordinates, timing : tGPS timing is enabled. Node is using GPS Timing.-> Select GPS timing action: quit, enable, disable : 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 GPS-less mode for testing and diagnostics only. Operation in this mode is not supported, and will often resultin reduced performance, increased latency and packet loss.


Remaining DHCP lease time is now displayed in show dhcp output

With this release, the show dhcpcommand has been enhanced to include the remaining DHCP leasetime.

Example output:

000ADB121212> show dhcpIP address : 192.168.168.140Subnet mask : 255.255.255.0Default gateway : 192.168.168.2Lease duration : 3600 secondsLease 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 rate6 also has a high packet error rate. This is indicated by an asterisk next to the modulation rate in theshow link CLI output.


6/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


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 rateindicator. This is an indication of the packet error rate over the past second, and therefore the health ofthe 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 isconsistently low, modulation rates will be increased, to improve the capacity of the link. If the packet errorrate is high, the modulation rate will be decreased, to improve the reliability of the link.

Example output:

000ADB121212> show link stateMAC Address NType State LAnt RAnt Mod Freq TxPower RxGain Range Path Dst PER----------------- ----- --------- ---- ---- --- ---- ------- ------ ---------- -------- ------00:0a:db:02:02:02 smext 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 statecommand now includes a field for the link path distance, inaddition to the existing range field. This field will reflect the path distance, in meters, of all links in thepath back to the Gateway, while the range field reflects only the distance to the immediate parent device.

Example output:

000ADB121212> show link stateMAC Address NType State LAnt RAnt Mod Freq TxPower RxGain Range Path DstPER----------------- ----- --------- ---- ---- --- ---- ------- ------ ---------- --------------00:0a:db:02:02:02 smext 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 linkcommand, once asecond, for the specified interval. This command is useful when waiting for a link to change status, orwhen adjusting device alignment to obtain optimum signal strength. The command can be stopped priorto the completion time by pressing Enter.

Syntax: show link monitor [seconds] [MAC]Default values: show link monitor 60 ALL


7/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 1 1

00:0a:db:02:02:02 smgw act path 33 34 54 48 1 1

00:0a:db:02:02:02 smgw act path 34 34 54 48 1 1

00:0a:db:02:02:02 smgw act path 34 34 54 48 1 1

00:0a:db:02:02:02 smgw act path 34 34 54 48 1 1

00:0a:db:02:02:02 smgw act path 34 34 54 48 1 1

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 : 60 secondsLast 5 values, oldest-newest : -99dBm -99dBm -99dBm -98dBm -99dBmAverage : -98.800003dBmProgrammed noise floor value : -98dBm

Operational range : Min: -111dBm, Max: -62dBm

000ADB121212>


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 linkexceeding this distance, the timing may be compromised, leading to an increase in packet loss and adecrease in bandwidth available on the link.

With previous firmware releases, a link exceeding 10 miles, with a low hop count, would in some cases beselected 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, isapplied to the route cost of any individual link with a distance of over 16 km. This penalty will cause anode, 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 routecommand.


8/22





Example output for a 22.5 km link:

000ADB121212> show link stateMAC Address NType State LAnt RAnt Mod Freq TxPower Range----------------- ----- --------- ---- ---- --- ---- ------- ----------00:0a:db:02:02:02 smgw act path 0 0 6 5735 13 22500

000ADB121212> show mesh route

Mesh Gateway Next Hop Raw Cost Adj Cost----------------- ----------------- -------- --------00:0a:db:02:02:02 00:0a:db:02:02:02 128 240

Simplified frequency region selection

With previous firmware releases, switching operating frequency band (region) required contactingsupport or use of a frequency change certificate.

With this firmware release, alternative operating frequency regions can be selected with the show provfreq 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 supplementaldocument, 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, includingsupport for additional frequencies for some countries. Please see the supplemental document, DP-1309WAN 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 tothe 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 Pointwas independent from the web interface for the Extender.

With this firmware release, there is a single, unified web interface, for both the Extender and APcomponents.

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, forall trap receivers.

With this firmware release, the SNMP community string can be defined independently for each trapreceiver.


9/22





Example output:

000ADB121212> set prov snmp

-> Select an SNMP action: quit, read-write enable,read-only enable, disable, modify : m

-> Select modification: back, read-write, read-only,trap receivers, quit : t

-> Select a trap action: back, add, delete, list, quit : a

-> Enter trap destination IP address: 192.168.168.254IP address entered: 192.168.168.254

-> Enter port number (1 - 65535): 162Port number entered: 162

-> Enter trap destination Community: privateTrap community entered: private

-> Select a trap action: back, add, delete, list, quit : lRow IP Address Port Community--- --------------- ----- ----------1 192.168.168.2 162 public2 192.168.168.254 162 private

-> Select a trap action: back, add, delete, list, quit : q

000ADB121212>


Preferred Gateway

In a network with multiple Gateways operating on the same frequency, it may be desirable to define apreferred Gateway for a child device, independent of the immediate parent node. This featurecompliments 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 MACis the MAC address of the preferred Gateway, or 000000000000 to clear the preferredGateway.

The preferred Gateway can be configured as follows:

000ADB121212> set prov prefgw 000adb010203

000ADB121212> show prov nodeProvisioning state : manualDomain : ALLPower mode : Full power


10/22





Radar detection : DisablePreferred parent : 00:00:00:00:00:00Preferred gateway : 00:0a:db:01:02:03

Auto save : Disabled

000ADB121212>

This feature is supported by CLI commands only and is not yet implemented in EMS or the Web

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) viaCLI command. This is useful when it is desired to have the Gateway powered, but not transmitting overthe air.

This can be achieved with the set gateway disableand conversely, set gateway enable, CLI commands,as seen below. While the gateway is disabled, it will not transmit or receive wireless data. Any existinglinks will be dropped, and new links will not form. If the Gateway is set to disabled state, it will remain inthis state, even after reboot or power cycle, until the Gateway is enabled once again with the set gatewayenableCLI command.

Example output:

00ADB121212> set gateway disableGateway is now disabled.

Gateway is disabled> set gateway enableGateway is now enabled.

000ADB121212>


Backhaul Ping

For network redundancy, networks are often deployed with Gateways at different physical locations withoverlap between the mesh networks. In this configuration, if a Gateway fails, all nodes routing throughthat 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 typicallyloss of service due to the stranded nodes.

With this firmware release, support has been introduced for backhaul ping. This feature, which can beconfigured on Gateway node types, will ping up to two IP addresses in order to monitor backhaulconnectivity. If the ping fails for a configurable number of consecutive attempts, the Gateway will disableitself, 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 consecutiveattempts, 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 isapproximately 60 seconds.

Backhaul ping can be configured with set bhpingand set prov bhping, as follows:


11/22





000ADB121212> set prov bhpingEnter status (e = enable, d = disable) [disable]: eBackhaul ping is enabled.Enter first IP address [0.0.0.0]: 192.168.168.2Enter second IP address [0.0.0.0]:Enter ping retries [12]:

000ADB121212> show prov bhpingStatus : EnableIP address 1 : 192.168.168.2IP address 2 : 0.0.0.0Max 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 nowdisabled 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 nowenabled due to backhaul ping success.

000ADB121212>

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

000ADB121212> set gateway disableGateway is now disabled.

Gateway is disabled>

Gateway is disabled> set gateway enableGateway is now enabled.

000ADB121212>


Manual configuration of GPS coordinates

With this release, GPS coordinates can be manually configured for all node types. This can be used toenter coordinates for Connector node types, which do not have GPS, or to override the GPS coordinatesfor other node types.

GPS coordinates can be configured with set prov gps, set gps, show prov gps, and show gpsas follows:

Example output:

1060WADDISON> set prov gps

-> Select user GPS action: quit, coordinates, timing : c

-> Enter latitude in degree(s) decimal format (-90.0 to 90.0): 41.948276


12/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 :

1060WADDISON> show prov gps

Latitude : 41.948276 degreesLongitude : -87.654973 degrees

1060WADDISON> show gps

Active GPS : User DefinedLatitude : 41.948276 degreesLongitude : -87.654973 degreesAltitude : 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: YesNumber of satellites: 9Satellite Number | SNR

10 | 41.00+19 | 39.00+28 | 35.007 | 31.00

11 | -36.0013 | 44.00+23 | 25.008 | -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 frequencyregion, however, some frequency regions restricted the available power levels.

With this firmware release, power levels are now set based on the configured frequency region. Thereare four power level settings available for each region:

Power Level Keyword Description

Full Power full The maximum transmit power allowed for the currentfrequency region

Half Power (-3db) half3db less than the maximum transmit power allowedfor the current frequency region

Quarter Power (-6db) quarter6db less than the maximum transmit power allowedfor the current frequency region


13/22





Low Power low12db less than the maximum transmit power allowedfor the current frequency region, or the lowest outputpower possible for the device.

The CLI now indicates the approximate output power in dBm EIRP for the full power setting for eachfrequency 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 5735-5835 42dBm EIRPCurrent frequency region setting : FCC-HI - FCC High Band 5735-5835 42dBm EIRPCurrent valid frequencies : 5735 5740 5745 5750 5755 5760

5765 5770 5775 5780 5785 57905795 5800 5805 5810 5815 58205825 5830 5835

Current frequency : 5755Current allowed frequencies : 5755Dwell time (minutes) : 30

000ADB121212>

This firmware release will interpret the power setting from prior firmware releases or EMS releases asfollows:

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, fordetails 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, basedon the current frequency region. This will ensure radar detection is enabled when needed for regulatorycompliance in the selected frequency region, and ensure radar detection is disabled when not required.

The current radar detection status can be seen with show radarand show prov radar.

For Gateway node types, the radar detection action can be changed with set radarand set prov radar, aswith previous firmware releases. The available modes are Enabled with traffic shutdown and Enabledwith channel change.

For more information in radar detection, and to see which regions require radar detection, please see thesupplemental document, DP-1309 WAN Frequency and Region Selection Guide .


14/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 ethcommands have been enhanced to support statusand 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.


15/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-onlymode, 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 backhaullink. 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 clientdevices. The value is specified in meters, with a valid range between 100 and 8000, or 0 for defaultsettings. 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 betterwhen the AP is also configured for a low transmit power. With a high power AP, the low power clientdevice may select a modulation rate which is too aggressive, resulting in high packet loss, highlatency, and reduced throughput. Reducing the AP power level allows the client device to select thecorrect modulation rate for the link.

Dual Power mode allows the AP to transmit at low-power when communicating with low-power clientdevices, 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)

o High power level (300mw or 400mw)

o High power MAC addresses (a list of MAC addresses or partial MAC addresses whichwill 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 previousfirmware releases, idle/inactive devices could remain connected to the AP indefinitely.



16/22





o Max Inactivity

Maximum time, in seconds, before a client device is considered to be inactive and will bedisconnected due to inactivity

o Begin Inactivity Probe

The AP will begin to poll the station for connectivity when it is x seconds from reaching MaxInactivity 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 per-SSID basis.

MAC Based Radius Authentication

This feature allows Radius authentication for client devices which are not capable of Radius/802.1xauthentication, 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

o Username style

bare mac, colon separated mac, or hyphen separated mac (802.1x format)

o 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.


17/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 or1.4pX), auto provisioning will fail to configure the AP and will also fail to upgrade the AP firmware.

WorkaroundUpgrade 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 updatedmanually 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 inincorrect date or time display. This would occur in auto mode, when a time zone offset was configuredvia 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 apcommands 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 apcommands mayresult 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 byentering 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 of255.255.255.255, regardless of the intended netmask value.

With this release, ACL processing correctly handles all possible netmask values.

Bug #12379: show link modtrendmissing from show techoutput

With this release, show techhas been enhanced to include show link modtrendoutput.

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

freqoutput. The device could, for example, display a current frequency of 5520, while the actual currentoperating frequency is 5745.

With this release, show freqwill indicate the actual current operating frequency.

Bug #13520: Web interface allows enabling management VLAN with ID 0 "untagged"


18/22





With previous releases, the web interface could allow the user to enable the management VLAN with aVLAN 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 VLANsupport is enabled.

Bug #13873: unable to make frame of 8 tausmessage logged

With previous releases, under some conditions, the message unable to make frame of 8 taus would belogged 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 bedisplayed.

Bug #13887: show link optproduces no output when there are no links

With previous releases, the show link optcommand would produce no response if issued on a device withno links.

With this release, if there are no links, show link optwill 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 activestate. This field is displayed in show linkoutput 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 nodeshows current value for domain, instead of setting in flash

With previous releases, show prov nodewould show the current active value for the devices domain.

With this release, show prov nodewill correctly show the configured value for domain, independent of thecurrent active value. The current value can be viewed with the show statuscommand.

Bug #14615: Gateway is disabledmessage should be improved

With previous releases, when a Gateway is disabled by configuration, CLI command, or event, thecommand 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 disableddue 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, thedevice will always start up with domain ALL. This will occur regardless of the domain value configuredthrough set prov domainor the node profile.

With this release, the device will honor the domain setting entered through set prov domainor the nodeprofile.

Bug #14786: Auto-save not functional on Gateway node types

With previous releases, the implementation of the configuration auto-save feature supported onlyExtender 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


19/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 gpscommand.

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 inincreased 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 longercontinuously generate tau sync events.

Bug #15054: 'set prov ip' may cause a reboot on the SkyPilot Connector DualBand

With previous releases, the set prov ipcommand may result in an unexpected reboot, on the SkyPilotConnector DualBand. This can occur if the user presses enter at all prompts, without entering any data.

With this release, set prov ipwill 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 theallowed 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 the802.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 devicedate/time via NTP, the scheduler would be considered invalid, and would not be honored. Upon reload ofthe device, the software schedule would be honored.

With this release, the software schedule will be correctly processed, even if received prior to NTP timesync.

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 DHCPassigned 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. Thistable can be viewed with the show mac2ipand show ip2maccommands on Gateway node types.

In addition, many minor issues were resolved with this release.


20/22





5 KNOWN LIMITATIONS/BUGS

The following known limitations are present in this firmware release:

Web interface not enabled/disabled on configuration reload

ResultWhen enabling the web server interface via SkyControl, the feature isnt actuallyenabled until thedevice is rebooted. The feature should be enabled upon reloading the configuration file (reload). Similarbehavior exists when disabling the feature.

WorkaroundReboot the node to disable/enable this feature.

Software scheduler does not account for Daylight Savings Time

ResultWhen using the software scheduler to program software upgrades for a specific date and time, whilethe state of Daylight Savings Time (DST) may be known on the SkyControl server this information isnt knownon the device. The device maintains time according to Zulu Time (GMT). This may result in upgradesoccurring 1 hour before or after the scheduled time. This issue does not impact a node in Manual Provisioningmode.

WorkaroundIf DST is in effect, schedule the upgrade to occur 1 hour later.

Bug #15283: 11th

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 awarning message More than 12 hops encountered. Cant add self. There is no operational impact beyondthe 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 changesmade in the EMS will not be applied to the device.

WorkaroundUse the CLI command set prov telnetto 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 webinterface. As with previous firmware, Internet Explorer and Firefox are supported.

WorkaroundUtilize 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 whenpreferred parent is configured.

6 PLANNED RESOLUTION OF LIMITATIONS/BUGSAs warranted, new firmware will be released to correct any newly discovered bugs or functional limitations.


21/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 firmware1.8+. Connectors running earlier firmware versions will not be able to form an active link with -08R revisionhardware. Gateways and Extenders are not subject to this limitation.

Gateway/

Extender

-07,

FW 1.5

Gateway/

Extender

-07,

FW 1.8+

Gateway/

Extender

-08,

FW 1.8+

Gateway

Pro,

FW 1.8

Gateway Pro FW 1.8,

Gateway/Extender -08 FW 1.8+Y Y Y Y

Gateway/Extender -07,

FW 1.5 / FW 1.8+

Y Y Y Y

Connector,

FW 1.5/1.6/1.7Y Y N N

Connector,

FW 1.8+Y Y Y Y

Y = compatibleN= not compatible

Device hardware revision can be verified with the following command:

000ADB020202> show version hwNode type : SkyPilot GatewaySystem part no. : 715-00030-08R

Serial no. : FL01234567CPLD Rev no. : 00010000Hardware revision : GEthernet MAC : 00:0A:DB:02:02:02Switchboard Interface : BSwitchboard Version : 0x1

000ADB020202>


22/22



APPENDIXPART NUMBERS

Trilliant SkyPilot firmware part numbers for this release are listed below.

Description firmware version New part number Previous Part Number

SkyPilot Gateway Pro (SP-

5230) Application Firmware

GwPro_1.8.bin 670-00037-02 rev 1.8 N/A

SkyPilot Gateway (SP-6900 andSP-6930), SkyPilot GatewayDualBand and SkyPilot GatewayTriBand Application Firmware

SkyGate_1.8.1.bin 670-00007-25 rev 1.8p1 670-00007-24 rev 1.5p10

SkyPilot Extender (SP-2500),SkyPilot Extender DualBand,and SkyPilot Extender TriBandApplication Firmware

SkyExt_1.8.1.bin 670-00008-25 rev 1.8p1 670-00008-24 rev 1.5p10

SkyPilot Connector Indoor andSkyPilot Classic Connector(Outdoor) Application Firmware

SkyConn_1.8.bin 670-00009-25 rev 1.8 670-00009-24 rev 1.5p10

SkyPilot Classic Connector

DualBand Application Firmware

SkyAcc_1.8.bin 670-00019-25 rev 1.8 670-00019-24 rev 1.5

SkyPilot Connector (SP-4700)Application Firmware

Conn_1.8.bin 670-00028-02 rev 1.8 670-00028-01 rev 1.7p5

SkyPilot Connector DualBand(SP-3800) Application Firmware

ConnDb_1.8.bin 670-00027-02 rev 1.8 670-00027-01 rev 1.7p5

SkyPilot Connector Mini (SP-4500), SkyPilot Connector Pro(SP-4600), andSyncMesh Client ApplicationFirmware

SkyMini_1.8.bin 670-00023-03 rev 1.8 670-00023-02 rev 1.6.2

Extender DualBand AccessPoint, andExtender TriBand Access Point

Access Point Firmware

SkyAP_1.8.bin 670-00013-25 rev 1.8 670-00013-24 rev 1.5p10

Tri l l iant Incorp orated1100 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.
https://app.bom.com/items/detail-spec?item_id=149857608&version_id=1312744607https://app.bom.com/items/detail-spec?item_id=149857608&version_id=1312744607https://app.bom.com/items/detail-spec?item_id=149857670&version_id=1331740827https://app.bom.com/items/detail-spec?item_id=149857670&version_id=1331740827https://app.bom.com/items/detail-spec?item_id=149857681&version_id=1331729347https://app.bom.com/items/detail-spec?item_id=149857681&version_id=1331729347https://app.bom.com/items/detail-spec?item_id=149857681&version_id=1331729347https://app.bom.com/items/detail-spec?item_id=149857681&version_id=1331729347https://app.bom.com/items/detail-spec?item_id=149857680&version_id=1331729337https://app.bom.com/items/detail-spec?item_id=149857680&version_id=1331729337https://app.bom.com/items/detail-spec?item_id=149857675&version_id=1312745277https://app.bom.com/items/detail-spec?item_id=149857675&version_id=1312745277https://app.bom.com/items/detail-spec?item_id=149857654&version_id=1312745067https://app.bom.com/items/detail-spec?item_id=149857654&version_id=1312745067https://app.bom.com/items/detail-spec?item_id=149857654&version_id=1312745067https://app.bom.com/items/detail-spec?item_id=149857654&version_id=1312745067https://app.bom.com/items/detail-spec?item_id=149857675&version_id=1312745277https://app.bom.com/items/detail-spec?item_id=149857675&version_id=1312745277https://app.bom.com/items/detail-spec?item_id=149857680&version_id=1331729337https://app.bom.com/items/detail-spec?item_id=149857680&version_id=1331729337https://app.bom.com/items/detail-spec?item_id=149857681&version_id=1331729347https://app.bom.com/items/detail-spec?item_id=149857681&version_id=1331729347https://app.bom.com/items/detail-spec?item_id=149857670&version_id=1331740827https://app.bom.com/items/detail-spec?item_id=149857608&version_id=1312744607

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

Documents

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