December 7, 2022
New supported features
| Features | Details | Feature Flag |
|---|---|---|
| Alerts / templates for 3rd party sensors | 3rd party sensors template * Add, edit and delete a template for 3rd party sensor * List view and details information for a 3rd party sensor template * 3rd party sensor default template 3rd party sensors alerts * Add an alert rule for 3rd party sensor * Alert raise for 3rd party sensor |
N |
| Throttle Email / SMS notifications | Email/SMS notifications are sent only once for any alert raised. This avoids spamming user mail box. | 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
- For North Bound APIs, API Keys are not supported from January 12, 2022 release. Users will need to use the login credentials to retrieve the access token as described in the DevNet documentation.
Limitations
- Per NAT best practices, source ports 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 uplinks and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
November 14, 2022
New supported features
This release has no customer-facing features. It includes platform efficiency and stability updates.
Caveats/Known Issues
None
Limitations
- Per NAT best practices, source ports 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 uplinks and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
September 6, 2022
New supported features
| Features | Details | Feature Flag |
|---|---|---|
| Alerts / templates support for Bridge | Templates for Bridge * Add a bridge template with unreachable alert * Edit the bridge template * List view for bridge template * Show the details information for a bridge template * Delete a bridge template * Bridge status (online/Offline) support |
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
- For North Bound APIs, API Keys are not supported from the release of January 2022. Users will need to use the login credentials to retrieve the access token as described in the DevNet documentation.
- When data spans across page boundary, sorting columns with duplicate values gives inconsistent results.
- On the mobile app,
- If the user switches from one tenant (with the Bridge feature flag enabled) to the other tenant (with the Bridge feature flag disabled), then they will still see the Bridge inventory tab.
- If the user switches from one tenant (with the Bridge feature flag disabled) to the other tenant (with the Bridge feature flag enabled), then they won't be able to see the Bridge Inventory tab. The work-around to the above issue is to log out and log in to the mobile app, whenever the user wants to switch tenants.
Limitations
- Per NAT best practices, source ports 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 uplinks and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
June 22, 2022
New supported features
| Features | Details | Feature Flag |
|---|---|---|
| Bridge 3rd Party Sensor Input Configuration (WebUI) | Support for creating and managing the 3rd party sensors * View the bridge input details from Web UI * Configure the Analog/Digital inputs * Configure sensors with category/unit and provide the input/output mapping * Update the unit of a sensor from the Bridge input page * Assign a sensor to an org hierarchy * Delete a sensor |
Y |
| Bridge 3rd Party Sensor Data/Graph Viewing | Support for viewing the 3rd party sensor telemetry data and graphs * View telemetry data (raw and mapped values) in tabular format * Export the telemetry data to a CSV file * View the telemetry data in Zing charts (Graph visualization) * View sensor health * View 3rd party sensors in the sensor inventory list view * View the transform data tab with the respective mapping values |
Y |
| Mobile App - Bridge Onboarding | Support for Bridge Onboarding through Mobile App * Onboard the Bridge and assign it to an org hierarchy * View the Bridge list from Inventory tab * View Bridge details along with configured inputs and their respective sensor assignments |
Y |
| Support of Zing charts for sensors and assets | * Migration of existing sensors and assets line charts (AM charts) to Zing charts * New look for boolean charts |
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
- For North Bound APIs, API Keys are not supported from the release of January 2022. Users will need to use the login credentials to retrieve the access token as described in the DevNet documentation.
- When data spans across page boundary, sorting columns with duplicate values gives inconsistent results.
- On the mobile app,
- If the user switches from one tenant (with the Bridge feature flag enabled) to the other tenant (with the Bridge feature flag disabled), then they will still see the Bridge inventory tab.
- If the user switches from one tenant (with the Bridge feature flag disabled) to the other tenant (with the Bridge feature flag enabled), then they won't be able to see the Bridge inventory tab.
The work-around to the above issue is to log out and log in to the mobile app, whenever the user wants to switch tenants.
Limitations
- Per NAT best practices, source ports 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 uplinks and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
April 26, 2022
New supported features
| Features | Details | Feature Flag |
|---|---|---|
| 3rd Party Unit Library Management (WebUI) | Support for creating and managing Unit library for 3rd party sensors 1. Analog input Sensor Type * View the Cisco supported default Sensor types and units. * Manage custom Sensor type and units 2. Digital input * Manage Alias Types and Alias |
Y |
| Bridge Base Configuration Management (WebUI) | Bridge Base configuration from the IAV Web UI. * Add a Bridge using API * Bridge management (View, Edit, Delete) * View the raw payload data in the Message Inspector. |
Y |
| Bridge Health/Troubleshooting | * Bridge Health — Display the Bridge health status, power status and LoRa parameters. * Troubleshooting — Support for Troubleshooting Bridge - Similar to Sensor troubleshooting. |
Y |
| Alerts/Templates support for Vibration sensor | * Support for creating Alert rules for Vibration sensor * Alert attributes supported - Velocity (rms value Z Axis) and Temperature * Default template and template support for Vibration sensor. |
Y |
Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.
Caveats/Known Issues
- For North Bound APIs, API Keys are not supported. Users will need to use the login credentials to retrieve the access token as described in the DevNet documentation.
- Forbidden error message pop up is observed intermittently in the sensor telemetry page when the user hits the Refresh button multiple times.
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 uplinks and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
February 15, 2022
New supported features
| Features | Details | Feature Flag |
|---|---|---|
| Mobile App | * Ability to view sensor data on the mobile app * Home/Landing page changed to the Inventory screen * Support for Hierarchy and RBAC in the app * Sensor and Network devices list with pagination support in the Inventory screen * Sensor summary screen with support for viewing Sensor alerts. |
N |
| Organization Hierarchy Management | * Support for Tenant/IT Admin to view all Access Control Groups of the selected Organization Level * Warning message for Edit/Delete template scenario when the user does not have access to all devices present under the Template. |
N |
| Alert Dashboard Enhancements | * Support for additional filters for all or specific sensors, network devices and assets. | N |
| Generic Bridge (4-20mA, 0-10V, digital input) PoC | * Support for adding/on-boarding the Bridge and viewing raw Telemetry Data * Support for sending raw Telemetry data over MQTT / Azure. |
Y |
Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.
Caveats/Known Issues
- For North Bound APIs, API Keys are not supported. Users will need to use the login credentials to retrieve the access token as described in the DevNet documentation.
- Forbidden error message pop up is observed intermittently in the alert dashboard page. As a work-around, users can refresh the page (browser refresh) to get rid of this message.
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 uplinks and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.
January 12, 2022
New supported features
| Features | Details | Feature Flag |
|---|---|---|
| Access control for Organization Hierarchy Management | * Organization Hierarchy Management * View the local or aggregated alert counts in the Organization hierarchy adjacent to the Organization levels * Auto-populate selected Organization hierarchy in the Add Asset page * Support of Organization Hierarchy with access control * Manage an Access Control Group * Manage User association to Access Control Groups * Support for system-defined and user-defined across control groups * Support for user sync from UI and auto-assignment of access control group based on user role * Access control group granular filtering of Assets, Sensors, Network devices and Alerts in the landing dashboard and inventory pages * Support of aggregation of Sensors/Assets/Network devices in the Organization hierarchy based on defined access levels |
N |
| Alert dashboard Enhancements | * Filter the alerts by severity, status, asset and device name * Cross launch to Alert Dashboard from Sensor, Gateway and Asset pages with automatic filter |
N |
| UI Enhancements | * UI Unification - Support of 'Refresh' button in top right of all pages * Missing frame symbol visibility improvement in satellite view for RF Performance tool |
Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.
Caveats/Known Issues
- For North Bound APIs, API Keys will not be supported from this release. Users will need to use the login credentials to retrieve the access token as described in the DevNet documentation.
- An error will be shown in the Mobile app during Device onboarding in case the user selects an Organization level that they do not have access to.
- Alert rule name modification will raise new alerts instead of updating the event count for the older alert name.
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 uplinks and end up in unreachable state, DevEUI will not be present in the Topic path for MQTT integration.