Release Notes for the Cisco LoRaWAN Gateway, Release 2.0.32
These release notes include important information about Cisco LoRaWAN Gateway Software Release 2.0.32 and the limitations, restrictions, and caveats, if any, that apply to this release.
 Note |
The documentation set for this product strives to use bias-free language. For purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. |
Introduction
The Cisco LoRaWAN Gateway is one of the Cisco Internet of Things (IoT) extension module series. It can be connected to the Cisco 809 and 829 Industrial Integrated Services Routers (IR800 series) for virtual mode or standalone for low-power wide-area (LPWA) access and is positioned as a carrier-grade gateway for outdoor deployment, including harsh environments. It adds a ruggedized remote LoRaWAN radio modem interface to create a gateway between the Cisco Field Network Director and a partner’s LoRa network server.
Note |
The Cisco LoRaWAN Gateway was previously named Cisco LoRaWAN Interface Module. |
There are two LoRaWAN gateway modes as below:
-
Virtual interface mode – IR800 series including the LoRaWAN module as a virtual interface
-
Standalone mode – The LoRaWAN module working alone as an Ethernet backhaul gateway
You can configure the LoRaWAN IXM running on virtual interface mode or standalone mode through CLI or IoT FND. For more information, see the Cisco Wireless Gateway for LoRaWAN Software Configuration Guide.
System Requirements
Hardware Supported
|
Model No. |
Description |
|---|---|
|
IXM-LPWA-800-16-K9 |
Cisco LoRaWAN Gateway, IoT extension module series, radio spectrum from 863–870 MHz, 16 LoRa channels, IP67 |
|
IXM-LPWA-900-16-K9 |
Cisco LoRaWAN Gateway, IoT extension module series, radio spectrum from 902–928 MHz, 16 LoRa channels, IP67 |
Software Images
|
Filename |
Description |
LoRa Forwarder Package (LRR) Version |
||||
|---|---|---|---|---|---|---|
|
ixm_mdm_i_k9-2.0.32.tar.gz |
Cisco LoRaWAN Gateway OS Image Version 2.0.32 with Semtech Release Version 2.3.0, FPGA Version 61, and HAL Version 5.1.0 |
LRR 2.4.21
|
Note |
The LRR version has dependencies with the IXM LoRaWAN firmware/FPGA/HAL release. Contact your Cisco representative if you are using different versions. |
Installation of a New Software Release
For both standalone mode and virtual mode, after you upgrade the LoRaWAN gateway to Release 2.0.30, you can only downgrade to Release 2.0.20. Downgrading to releases earlier than 2.0.20 is not supported. For example, from Release 2.0.30 to Release 2.0.11, or from Release 2.0.30 to Release 2.0.10, is not supported..
To upgrade to Release2.0.x, any older versions must first be upgraded to Release 1.0.20. For example, Release 1.0.4, 1.0.5, or 1.0.6 has to be upgraded to 1.0.20 first and then upgraded to Release 2.0.x.
Virtual Mode Installation
Note |
Before upgrading to Release 2.0.x from Release 1.0.x, make sure you have the FPGA v58 properly installed. The FPGA upgrade will be triggered once the IXM boots up with the image version 1.0.20. After 10 - 15 minutes, you can use the following command to check the FPGA version. Do not install the packet forwarder software or perform radio related configuration while the FPGA is upgrading or downgrading. |
IR829_1#show virtual-lpwa 10 modem info
Name : Virtual-LPWA 10
ModemImageVer : 2.0.32
BootloaderVer : 20180130_cisco
ModemAgentVer : 1.02
SerialNumber : FOC20394AEB
PID : IXM-LPWA-800-16-K9
UTCTime : 02:11:25.625 UTC Mon Sep 10 2018
IPv4Address : 192.168.100.2
IPv6Address : none
FPGAVersion : 61
TimeZone : PDT
LocalTime : Sun Sep 9 19:11:25 PDT 2018
ACT2 Authentication : PASS
ModemVersionID : V01
ProtocolVersion : 2
ChipID : LSB = 0x286cf912 MSB = 0x00f14392
LoRaSerialNumber : FOC20427A86
LoRaCalc : <142,130,122,114,106,102,98,94,85,76,67,58,50,45,41,37-141,129,121,113,105,101,97,93,84,75,66,57,49,44,40,36>
CalTempCelsius : 34
CalTempCodeAD9361 : 91
RSSIOffset : -204.86,-203.58
AESKey : Unknown
IR829_1#
Follow this procedure to upgrade to Release 2.0.32:
Procedure
| Step 1 |
Log in to the IR809 or IR829 system with terminal through SSH or Console. |
||||
| Step 2 |
Copy the image file into IR809 or IR829 from your host, and the image will be stored in flash. Example: |
||||
| Step 3 |
(Optional) If you are upgrading from an older version to Release 1.0.20, the upgrade will result in updating the FPGA to version 61. After upgrading the image, no action should be taken while the FPGA is upgrading. You must wait until you get the upgrade status of Ready, as the following example shows. Example: |
||||
| Step 4 |
Upgrade the firmware to Release 2.0.x using the following factory install CLI: |
||||
| Step 5 |
After the image is installed successfully, verify the status. As shown in the following output, ModemImageVer has been updated, but BootloaderVer remains the same. Example: |
||||
| Step 6 |
Upgrade the firmware to Release 2.0.x using the same CLI with uboot or uboot-only option:
|
||||
| Step 7 |
After the image is installed successfully, verify the status. You will find from the output that both ModemImageVer and BootloaderVer have been upgraded. Example: |
Firmware Upgrade From Standalone Mode
Note |
We assume that you have the latest FPGA v58. If you have loaded any recent release like 2.0.10 or 2.0.11 on the IXM, use the show inventory command to check the FPGA status. If the FPGA version is not 58, upgrade first with an image that has FPGA v58. Refer to the release support matrix on various FPGA version and LRR version support. |
Follow these steps to install a new software image on the standalone mode LoRaWAN Gateway:
Procedure
| Step 1 |
Log into the Cisco LoRaWAN Gateway through the console port, or SSH if configured.
|
||||
| Step 2 |
Check the current version before upgrade. Example: |
||||
| Step 3 |
Download the image file to the Cisco LoRaWAN Gateway from a TFTP server or from a USB device, and install the image.
Use the following command to download and install the firmware.
Example: |
||||
| Step 4 |
After the image is installed successfully, verify the status. Example: |
||||
| Step 5 |
Check the FPGA status using the following command: Example:Wait until the FPGA is upgraded and shown as 61. |
Switching Between Standalone Mode and Virtual Mode
When the LoRaWAN gateway is in standalone mode, use the switchover EXEC command to switch to the virtual mode.
#switchover
You can switch the LoRaWAN gateway from virtual mode to standalone mode through IR8x9, using the following command.
IR800#virtual-lpwa 1 modem standalone mode enable
New and Changed Information
This section contains new and changed information for this release.
New Commands in Release 2.0.32
This section contains new commands introduced for this release. For more information, see the Cisco LoRaWAN Gateway Software Configuration Guide.
The following commands are added in this release for the standalone mode:
-
container log all – Configure logging through syslog-ng in container.
-
show gps history – Show the last known GPS information.
Open Caveats
This section contains open caveats for this release.
-
CSCvi92370
Symptom: Upgrading IXM image via USB and having the USB connected to the unit while upgrading can cause problem and block the upgrade.
Workaround: Copy the IXM image to flash and perform archive download via FLASH. Unplug USB while the boot is happening. If the IXM is in error state, simply unplug the USB. The device will recover from the error state after several minutes.
-
CSCvh06187
Symptom: In virtual mode, the XPKI CA server is not supported when SCEP is configured from file instead of profile.
Workaround: Configure the XPKI CA server using the lpwa modem scep profile command, and make sure that every parameter is configured properly.
-
CSCvh00511
Symptom: FTP server does not accept passwords with special characters like ! or #.
Workaround: Avoid using these special characters.
-
CSCvm55580
Symptom: For any displayed GPS Information, the satellites in use are incorrect.
Workaround: The correct number for satellites in use can be determined by looking at the NMEA GSA messages displayed in show gps log.
Resolved Caveats
This section contains resolved caveats for this release.
-
CSCvi70922
Symptom: The virtual-lpwa packet forwarder install/uninstall exec commands have no effect.
Workaround: In IOS, the packet forwarder installation exec commands are not supported and have been removed.
Known Issues
-
Problem: If the USB is used to upgrade the IXM image and plugged in during boot, IXM may sometimes fall into an error state during boot.
Workaround:
1. Copy the IXM image to flash and perform archive download via FLASH. Unplug the USB while the boot is happening.
2. If the IXM is in error state, simply unplug the USB and the device will recover from the error state after several minutes.
-
Problem: GPS synchronization issue while UBX is on.
Symptom: There is issue with UBX interoperating with LRR.
Workaround: You are recommended to turn off UBX while LRR is running. Currently, there is no effect on other functions with UBX off.
-
Problem: Container logging takes about 40 seconds to configure for the first time.
-
Problem: Starting the packet forwarder takes about 30 seconds for the first time.
Related Documentation
These documents provide detailed information about the Cisco LoRaWAN Gateway and are available at: www.cisco.com/go/lorawanmodule
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What’s New in Cisco Product Documentation .
To receive new and revised Cisco technical content directly to your desktop, you can subscribe to the What’s New in Cisco Product Documentation RSS feed . The RSS feeds are a free service.
Feedback