WMC v2.3 wiki
Product Overview
Using
OSS API*
Advanced
Resources
User Tools
Sidebar
wiki:ran_2.2
This is an old revision of the document!
Table of Contents
RAN v2.2
It is recommended to use the MEGAPACKAGE that installs all mandatory packages onto your system (BSCC, SNMP, LIBLORAGW-FPGA, SPF). This package preserves any change to your current network configuration (VPN and GSM/ETH configuration). This megapackage can be used as well remotely (from RAN dashboard for instance) and locally (USB, debug link, SSH).
| Product | Megapackage |
|---|---|
| iBTS | ran_gateway_lpbs_v2.2.1.tar.gz |
| Wirnet Station | dota_ran_gateway_v2.2.2.tar.gz |
| ifemtoCell | ran_gateway_wifc_v2.2.1.tar.gz |
To update your system, you can use the “drag&drop” software update feature from the RAN dashboard interface.
IT IS RECOMMENDED TO HAVE A DHCP DEFINED IN YOUR LOCAL NETWORK
Using static IP can lead to a connection issue to the RAN
Using static IP can lead to a connection issue to the RAN
It is recommended to update the OpenVPN package to v1.11 before using the megapackage
For Wirnet Station, if your BSCC and SNMP packages are RAN 2.0 compatible (v1.13), you must first install the RAN 2.1 packages (v2.1) before using the megapackage.
For ifemtocell, before installing the megapackage, you should remove the old libloragw by installing the following special package on your system : libloragw-remove-backup.ipk
Don't be afraid by the following message: “– Remove package from libloragw-remove.ipk: ERROR (255)”: that simply indicates that the package is not present in the backup storage).
Don't be afraid by the following message: “– Remove package from libloragw-remove.ipk: ERROR (255)”: that simply indicates that the package is not present in the backup storage).
The megapackage does not contain any OpenVPN certificate. If you install this megapackage without RAN connection (i.e you never installed any OpenVPN certificate on your system), you should ask for an OpenVPN certificate to
support@kerlink.fr and install it on your system. In this case, you need to install these packages (OpenVPN certificate and megapackage) via a local access (USB, debug link, SSH). For Keros sytems (Wirnet iBTS and Wirnet iFemtoCell), if you use the scp command, don't forget to dezip and uncompress the mega-package before upgrading the system !
tar xvf *ran_gateway*.tar.gz
Compatibility Matrix
You can manually install your packages individually by selecting the packages you want to update on to your system as specified in the compatibility matrix :
| Product | BSCC | SNMP | Firmware | LoRa HAL | Packet Forwarder | VPN |
|---|---|---|---|---|---|---|
| iBTS | bscc_v2.2.1 | snmp_v2.2.1 | keros 3.1.16 | not available yet | not available yet | 1.11 |
| Wirnet Station | dota_v2.2.1_bscc | dota_v2.2.1_snmp | firmware 3.3 (not available yet) | custo_libloragw-fpga_4.1.3-klk7_wirnet | spf_3.1.0-klk15_4.1.3-klk7_wirnet | 1.11 |
| Wirnet iFemtoCell | bscc_v2.2.1_wifc | lorasnmp_v2.2.1_wifc | keros 3.1.14 | libloragw-fpga_4.1.3-klk7_klk_wifc | spf_3.1.0-klk15_4.1.3-klk7_klk_wifc | 1.11 |
For ifemtocell, before installing the libloragw-fpga_4.1.3-klk7_klk_wifc.ipk,you should remove the old libloragw by installing the following special package on your system: libloragw-remove-backup.ipk
Don't be afraid by the following message: “– Remove package from libloragw-remove.ipk: ERROR (255)”: that simply indicates that the package is not present in the backup storage).
Don't be afraid by the following message: “– Remove package from libloragw-remove.ipk: ERROR (255)”: that simply indicates that the package is not present in the backup storage).
Main Changes
- Full support of Class C end-devices
- New packet forwarder KPIs
- Uptime per period of time
- Number of restarts per period of time
- Workflow editor
- Spectrum analysis support for Wirnet Stations
- Display of all uplink and downlink messages for each end-device
- Per-cluster payload encoding using HEX or BASE64
- Improved CSV export of gateways and end-devices
- Enhanced mass creation or deletion of gateways or end-devices
Main Improvements
- RAN interface automatic page refresh doesn’t generates random “Server error” messages
- Cluster configuration update does not need push password to be filled in
- Superadmin role is not limited on alarms menu
- RNC cluster filter is working
- Wirnet Station KPI “Downlink bytes” is supported
- Wirnet Station VPN/Supervision configuration doesn’t update gateway onboard parameters
- Https can be configured within the push URL using the dashboard
Main Restrictions
- Trusted Key Management is not fully supported
- VPN IP address modification is not displayed on dashboard
- Spectrum analysis is not supported on Wirnet iFemtoCells
- RX timestamp not available when GPS is not locked
- Unknown gateway interface label is sometimes displayed
- RNC raw radio configuration update doesn’t indicate ignored changes
wiki/ran_2.2.1519227892.txt.gz · Last modified: 2018/02/21 16:44 by tda
