November 16, 2023

New features supported

Features	Details	Feature Flag
Enhance message inspector for 3rd party sensors	As an IT/Tenant admin, I want to see both Join Requests from sensors and Join Accepts from IAV to troubleshoot all sensors trying to connect to IAV.	N
Arctic support in IAV (EFT release)	As an IT/Tenant admin, want to use the LoRaWAN PIM as a gateway for LoRaWAN, with the IR1101 being managed externally by a Cisco management tool.	Y
Cisco SSO Login Experience (New Feature)	IoT Operations Dashboard is integrated with Cisco Customer Identity (CCI) for an improved and seamless login experience. Cisco Customer Identity (CCI) is an identity provider managed and used by Cisco. Most users are already familiar with CCI and using it for logging into Cisco.com. This integration of IoT OD with CCI provides enhanced secure authentication and enables users to navigate across multiple Cisco applications and websites with one set of login credentials ensuring seamless operation. Refer CCI Integration.	N

Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.

From January 12, 2022, API Keys will no longer be available for North Bound APIs. Users should refer to the DevNet documentation for instructions on using login credentials to get the access token.

To ensure NAT works smoothly, it's best to avoid using source ports below 1024 and the port 1900. If not, there's a risk that the IPSec tunnel between the IXM and the cloud environment may fail to connect due to blocked traffic.
If sensors are onboarded but haven't sent any data, their DevEUI won't appear in the MQTT integration's topic path.

Features	Details	Feature Flag
Downlink support for cisco sensors	As an IT/Tenant admin, the user can change the uplink frequency of a sensor so it can report data in increments other than default	N
Bulk add of 3rd party sensors	Users will be able to upload 3rd party sensors in bulk using CSV file and API.	Y

Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.

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.

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.

Features	Details	Feature Flag
IAV 3rd party passthrough - Phase 1	As an IT/Tenant admin, the user can add an analog sensor to a sensor catalog so that the OT/Installer team can start onboarding the new sensors easily without having to configure individually.	Y

Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.

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.

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.

Features	Details	Feature Flag
Transition of org hierarchy to common OD feature	Organization Hierarchy Management, the service developed by IAV will be made into a common service that can be utilized by other services (CCV, EDM, SEA, EI, etc)	Y
Alerts / templates for velocity RMS X and Y axis	* User should be able to create alert rules for Velocity RMS on the X, Y, and Z axis of the Vibration Sensor. * User should be able to add an alert to a template and receive notifications. * When active, an alert should be visible on the dashboard, asset, and the sensor pages	N
Support for Pulse Counting - Phase-1	* Dashboard - A line card to show the cumulative pulse value count * The user will have the capability to manually modify the reading so that the physical meter value matches the IAV pulse counter. * Decode the pulse counting data (from two digital inputs) and pass it over the MQTT stream	N

Feature Flag (Y) — The feature is available to select EFT customers by request. Please contact your Cisco support representative for assistance.

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.

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.