September 21, 2021
New supported features
| Features | Details | Feature Flag |
|---|---|---|
| Organization Hierarchy Management | * Manage Organization Hierarchy * Manage Sensors, Assets and Network devices under an Organization Hierarchy * Support for special Organization Hierarchy sub-node "Unused" for Sensors and Network devices in Inventory state * Support for Organization Hierarchy filter in the Landing page dashboard and inventory pages * Support for local persistence of Organization Hierarchy selection filter across Dashboard and inventory pages * Support for single/bulk movement of Assets, Sensors and Network devices to new Organization Hierarchy level * View count of Assets/Sensors in Hierarchy details page and cross-launch to inventory pages with associated filter * Selection of Organization Hierarchy while on-boarding Sensor/Network devices on the Mobile app |
Y |
| RF Performance Tool | * Filter the best Gateway in the RF performance tool * View the missed frames in the RF performance map view |
N |
| Anomaly Visualization | * Multiple threshold line visualization for the alert severity | N |
| Alert dashboard enhancements | * Alerts sidebar support containing the alert details - with Acknowledge/Clear actions and cross launch links * "Alert Name" header in the table has been renamed to "Alert Rule" * Added Asset column to the alert dashboard |
N |
| Enhancements | * Support for selecting multiple sensors while creating/updating a template * Support for multi-delete of Sensors and Network devices |
N |
| Mobile App | * Version 1.0.4 of Mobile app for iOS and Android * Selection of Organization Hierarchy while on-boarding Sensor/Network devices * Pull-to-refresh support on the Network devices inventory page |
N |
Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.
Caveats/Known Issues
Alert Dashboard
- Asset name for Sensor would be displayed only for newly created alerts and not for the existing alerts.
- Alert threshold value is not rounded-up in UI in the Alert details sidebar in case alert is created with Fahrenheit as the Unit.
- Asset name will be displayed for sensors even if they have been un-asssigned from the asset after alert has been raised. Asset name will not be shown in the sidebar in this case.
- Asset name will not be displayed for sensors if they have been assigned to an asset after alert has been raised. Asset name will be shown in the sidebar in this case.
Limitations
- Per NAT best practices, source port of 1900 and source ports below 1024 should be avoided, else, there can be instances in which the IPSec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
- For sensors that have been on-boarded, but have not sent any up-links and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
- Text search in Alert Dashboard is not supported for Asset and Device name fields.
- On the Alert Dashboard, Acknowledge and Clear options don't get disabled if Alert is already Acknowledged or Cleared. This works fine in the Sidebar.
August 3, 2021
New features
| Feature | Details | Feature Flag |
|---|---|---|
| MQTT support for Dynamic Topic Pattern | * Support for dynamic variables in topic pattern for MQTT integration. | N |
| RF Performance Tools enhancements | * Support for Tabular Telemetry * Support for exporting telemetry data in CSV format |
Y |
| SSO support | * Single Sign On Support for the web app and mobile app using SAML 2.0 | N |
| Visually indicate anomalies | * Support for viewing open alerts in sensor telemetry graphical view * Support for viewing alert thresholds in sensor telemetry graphical view |
N |
| Organization Hierarchy Management | Support for creation and management of Hierarchy | Y |
Limitations
- Per NAT best practices, source port of 1900 and source ports below 1024 should be avoided, else, there can be instances in which the IPSec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
- For sensors that have been onboarded, but have not sent any up-links and end up in an unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
June 9, 2021
New features
| Feature | Details |
|---|---|
| RF Performance Tool | * Support for Adeunis Field Test Device * RF coverage based on the Field Test Device data sets |
| Localization Support | * Support for Imperial and Metric Unit Systems. * Sensor data visualization based on the configured preferences * Integrations, Email and SMS alert notifications use metric units |
| Northbound APIs | * Support of Northbound APIs (Asset Types, Assets, Sensors) |
| Mobile App Enhancements | * Support for template selection during sensor on-boarding * Help page explaining steps to turn on the sensors. * Support for showing the progress of network device on-boarding |
| Region Support | * IN and AU region support in EU Cluster |
| UI Enhancements | * For AV300 GPS sensors, Latitude and Longitude values of 0 are not plotted. Similarly, fix failed co-ordinates are not plotted. |
Open Issues / Caveats
| Feature | Details |
|---|---|
| Sensor troubleshooting | Sensor troubleshooting UI uses a fixed value of one day to calculate un-reachability and does not use the configured template value for the sensor. |
| Alert Dashboard | The widget in alert dashboard is not auto refreshed although the alert table below is auto refreshed. So, if the user is on the alert dashboard page and there are new alerts added/cleared, then there will be a discrepancy in the alert count between the widget and the table below. |
Limitations
Per NAT best practices, source port of 1900 and source ports below 1024 should be avoided, else, there can be instances in which the IPSec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
May 20, 2021
New features
- Template Management
- Create/Edit/Delete a template
- Add a device from the template details page
- View associated template from sensor list, detail pages
- Update the Timeout (Missed uplinks) for the Sensor unreachable condition in the templates
- Default IXM Template Support for Unreachable Gateway
- Alert Rule Management
- Create/Edit/View an Alert rule
- List view for Alert rules
- Geofence Alert Support
- Create a Geofence alert
- Miscellaneous Enhancements
- Create an Azure Integration with Certificate based authentication
- Message Inspector enhanced by showing frame summary information without expanding into frame details
Limitations
Per NAT best practices, source port of 1900 and source ports below 1024 should be avoided, else, there can be instances in which the IPSec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
Open caveats
- System template (IXM unreachable ) edit template - Fails to show already added recipients (if any)
- All types of upgraded Integrations will show the "Updated by" field as "asset-visibility".
March 16, 2021
New features
- Azure IoT Integration (Learn more)
- Create/Update/Delete an Azure IoT Integration
- Azure IoT Integration with support for streaming sensor telemetry data
- MQTT Integration (Learn more)
- Support for X509 based authentication
- Support for streaming alerts and sensor telemetry data via MQTT
- UI Enhancements
- View Sensor Type information in sensor list view
- Feature support to edit Gateway name and location post creation
- Message inspector feature now enabled only for IT admin users
- View the timestamp in seconds in the Telemetry page
- Launch Network device from sensor troubleshooting page
- View the Network status in the Network device details page
Limitations
- When using NAT, source ports below 1024 should be avoided. Also, a source port of 1900 should be avoided. Otherwise, there can be instances in which the IPsec tunnel between the IXM and the cloud environment will not establish due to blocked traffic.
- The option "enableSSL" will be true by default in the integrations that are created with PEM (Certificate) based authentication.
- Data and alert payloads for MQTT and Azure have the following placeholder fields which will have default values in this release. In subsequent releases, support for sending actual values for these placeholder fields will be added.
- fCnt (LoRaWAN Frame counter) - This is currently zero.
- Asset ID - This is currently an empty string.
- Gateway Serial - Serial numbers for Network devices. This is currently an empty string.
February 2, 2021
New features
Geofences can be used to track the location of GPS-enabled sensors and associated assets in relation to an area on a map. This allows you to create a virtual perimeter for your real-world geographic area, and receive information as sensors and associated assets enter or leave that area. Learn more.
In future releases, you will be able to apply rules or trigger alerts based on where a sensor is in relation to that "geofence".Note: Geofencing is available to select EFT customers by request. Please contact your Cisco support representative for assistance.
The name and location of a Sensor can now be edited using UI. Learn more.
Note: Manually adding sensors is available to select EFT customers by request. Please contact your Cisco support representative for assistance.
Limitations
- The Message Inspector is currently beta functionality and not fully implemented. Cisco will enhance the Message Inspector in future releases and make it generally available.
- Some Cisco sensors may have QR codes that are too small to scan with the mobile application. We advise installers to either scan the full-size QR code on the packaging or enter the DevEUI manually in the mobile application.
- Only public network devices are supported currently.
- Customers need to ensure either of the following:
- Each IXM gets a unique public IP when communicating with the IoT Operations Dashboard (non-NAT deployments scenario).
- If two or more IXM are behind the same NAT, then the deployment sequence of IXMs should be staggered i.e. please maintain a gap of 10 minutes between two IXM starts.