Redline Connect v3.9 RelNotes
Redline Connect v3.9 RelNotes
Release Notes
RDL-3000 XP
Connect-Series: IWS / OW / OW-ER
v3.9
This document provides information about a specific product software release. To avoid or
minimize potential service interruption, ensure that you have read and understand the contents of
this release note and are aware of all changes specific to the capabilities of your devices before
installing this software release.
Upgrade
Refer to the following table for important upgrade information.
Upgrade Information
Binary File RDL3KR4_MAIN_0309_007.sbin
Upgrade Path Refer to Upgrade Path and Over-the-Air Compatibility sections.
Options Keys An options key is required for system operation. An upgraded options key
enabling v3.x functionality is required for each system being upgraded.
New Features All new features are set to factory default values and may require manual
& Feature adjustment before the system is operated in a production network. Review
Changes all configuration settings after installing this release.
Upgrade Path
Use the following table to verify that versions are upwards compatible before upgrading. For
downgrades, refer to Software Downgrade Procedure at the end of this document.
Upgrade Compatibility Table
Intermediate
Current Version Notes Final Version
Version
2.23 1, 2, 3 2.25 v3.9
2.25 Update 9 (or higher) 1, 2, 3 v3.9
3.0 / 3.0 Update 1 v3.9
3.1 4 N/A N/A
3.2 - 3.8 v3.9
1. The RDL-3000 U-Boot must be at version '2013.Feb' before upgrading to firmware v3.xx.
If any system is not at the correct U-Boot version do not perform the firmware upgrade.
Contact Redline Support at: [email protected].
2. Upgrading from v2.25 to v3.x requires a new v3.x option key.
3. Link MCS-related parameters must be reviewed and configured following upgrade (MCS
values are set to minimum as default).
4. FIPS is not available on this platform.
IMPORTANT: v3.x software is not over-the-air compatible with any version of v2.x.
For sectors operating at v3.x all new/replacement remote terminals must be running v3.x
before installation in the field.
Interoperability
Full support of system features requires all communicating systems to be operating at the same
release version. Refer to the RDL-3000 family User Manual for a complete list of supported remote
terminals.
Interoperability Table
RDL-3000 XP
RDL-3000 XP Remote Terminals (same sector)
Base station
Connect-OW (-ER), Edge, Elte-MT, Endurance
Ellipse
RAS Elite, RAS Extend, UHP
Resolved Issues
The following table tracks identified issues that have been resolved release 3.x.
Resolved Issues
# Problem Description Release
1 Following a spectrum scan, subscriber terminates initial link to base station 3.2
and then immediately reconnects.
2 User password not allowing dash (-) or underscore (_). 3.2
3 Added Management VLAN ID to the LLDP TLV. 3.2
4 Deleting the original administrator account (username:admin) resulted in the 3.4
user being unable to login to the management interface.
2051 5 Activating 'Factory Defaults' does not restore the original administrator 3.4
account (username:admin, password:admin) if this account was deleted
2008 6 User is not able to login to RDL-3000 using ssh when the User 3.4
Authentication setting is set to 'Radius-Only'.
2006 7 The dot.decimal representation of the TFTP address in SNMP traps 3.4
rdlBwiSWUpgradeFailed and rdlBwiSWUpgradeSuccesswas reversed.
For example, '192.168.05.101' was sent as '101.05.168.192'.
2176 8 Changing user authentication mode requires reboot (e.g., changing from 3.6
Local Only to RADIUS w. Local Fallback).
Resolved Issues
2181 9 When logging in from CLI with authentication set to 'RADIUS Only', 'RADIUS 3.6
+ Local' or 'RADIUS w. Local Fallback', entering any existing or non existing
user name and no password results in successful login with limited
commands (e.g., restricted version of user account).
2164 10 Username not allowing dash (-) or underscore (_). 3.6
2176 11 Changing from Local Only to RADIUS requires a system reboot. 3.6 Upd. 1
2179 12 When logging in from Web with authentication set to 'RADIUS w. Local 3.6 Upd. 1
Fallback' and RADIUS server is connected, system accepts local credentials.
2271 13 User was allowed to enter a new administrator password that exceeded the 3.7
15 character limit (truncated).
System Behavior
Operating Restrictions
The following table lists restrictions associated with this release. Operating the system at settings
exceeding these recommendations may exceed the scope of the Redline support policy and may
void the equipment warranty.
Operating Restrictions
Parameter Description
Web Browsers Internet Explorer 10+, Firefox 38.0+, Google Chrome 43.0+
Tx Power Tx power settings are controlled by options keys. Factory default is -5 dBm.
Maximum power is limited by regional regulations and the attached antenna.
Ethernet The maximum Ethernet packet size for this release is 1866 bytes. Packets
Packet exceeding this size are discarded.
Important Notes:
1. Options Keys: Operation of the Ellipse requires an options key be installed and activated before
the radio will operate. The options key is unique to each system and limits the transmit power,
operating frequency range, and channel bandwidth per the regulator domain governing the location
where the system is deployed. The operator does not have the option to select the country or
regulatory region of operation. The professional installer and operator can not override these
operational restrictions.
2. EIRP Levels: Where required by local regulations, the maximum operational power per channel
for a specific antenna must not exceed the maximum allowable EIRP levels, The RF output power
settings must be professionally programmed by the manufacturer or a trained professional installer.
Configuration
1. The operator MUST reboot the wireless terminal after making changes to any of the following
RF parameters (including changing the active options key). Failure to reboot the wireless
terminal after making these changes may result in loss of wireless communications.
4. Do not logout or issue new commands until the previous CLI command has finished
processing. For 'save config' or 'script' commands this may be approximately three seconds.
When writing script files, insert pauses after these commands.
5. Enabling AES encryption requires the operator to first enter a pre-shared key or load ECDSA
certificates. The shared key entry field is hidden when Encryption Type is set to 'None' and/or
'ECDSA Authentication Enable' is checked. Uncheck this item and select AES 128/256 to view
the Shared Key field.
6. Telnet support is not available to delete frequency ranges. Use the Web interface to delete
frequency ranges.
7. For enhanced security, SSH tunneling is disabled (v3.7 and above).
Management
1. A permanent Options Key must be entered for in-service operation. During the last 45 days
before a temporary key expires: an event message is logged once per day, an SNMP trap is
generated every six hours, and an expiry notice is displayed in the Product Options screen.
2. User management does not allow administrators to modify other administrator accounts.
Delete the account and re-create with the required parameter changes.
3. When Secure Mode is enabled, user lockout (e.g., loss of admin password) can be recovered
only by returning the unit to a Redline authorized service center.
4. Long reset procedure (timed power-cycle) is not available (v3.4 and higher) to restore access
to an RDL-3000 system.
5. Password and IP recovery tool available (v3.4 and higher) using a Redline supplied
Windows™ based application to access a Redline wireless system. Replaces long reset
procedure. Refer to the RDL-3000 Family User Manual for complete instructions.
Operation
1. When performing a spectrum sweep that includes the lower band edge for that wireless
terminal, the results may falsely indicate a signal is present on the lowest channel. Repeat the
spectrum sweep to verify the reported results.
2. Google map display feature is not available for GPS position (Status screen). Starting June 11,
2018, Google has restricted access to map APIs.
Upgrade/Downgrade Procedures
Before You Begin
Review the following list before beginning the upgrade procedure.
Obtain a copy of the v3.9 software binary file.
The operator must login as administrator.
The RDL-3000 XP U-Boot must be at version '2013.Feb' before upgrading to firmware v3.x. If
any system is not at the correct U-Boot version do not perform the firmware upgrade.
For new installations, an options key must be purchased for each system. For existing
systems, an upgraded options key must be obtained.
A network computer or portable PC is required. Configure a TFTP server and copy the PMP
software binary file to the server default directory.
Over-the-air upgrades must be performed from the base station.
Upgrade all wireless terminals before upgrading the base station. Refer to the minimum
version requirements before upgrading any subscriber.
Software Upgrade Using the Web Interface
1. Upload the v3.9 Software:
Login to the unit and click Firmware. Enter the IP address of the TFTP server and the full
name of the PMP software file including the binary extension (.sbin). When using FTP the
operator must also enter the FTP account name and password. Click the Upload File button to
start the upload process. A status message will indicate when the software file has been
completely uploaded.
2. Enter a new or renewed options key (if required):
Click Product Options and enter the PMP-enabled options key in Options Key 1 or Options
Key 2 field. Select the appropriate key in the Active Options Key field and click Activate Key
to validate and activate the new key.
3. Change Versions:
To change versions, click the Change Version button in the Firmware Management screen.
The system will automatically reboot.
4. Post Upgrade:
It is important to review the system configuration following any upgrade. Login to each unit to
review and adjust settings as required.
Important: Review all configuration settings after installing this release, especially Min and
Max Burst Rate settings for each subscriber.
This completes the upgrade procedure using the Web interface.
IMPORTANT: Downgrading with Secure Mode enabled will cause in user lock-out.