EI 1.2.6 - December 15, 2020
Upgrade requirements
All EI Agents must be updated to the latest version to ensure full feature compatibility with the Cisco EI cloud software. For example, upgrading the EI Agent allows you to use new connection types for Assets and Data Destinations and perform all Data Policy management actions.
In this release, you must manually upgrade the EI Agents using GMM/FND/Local Manager. Because this upgrade process removes all data policy information from the agent, you must also download a summary of your Data Policies, un-deploy the policies, upgrade the EI Agents and then redeploy the policies to the same EI Agents.
New and revised features
Support for new Asset Types and Assets
- Serial
Data Destinations enhancements
- Enhancements to Generic MQTT destinations
- IBM Watson (telemetry)
- Cumulocity IoT (telemetry, dynamic provisioning)
- AWS IoT Core (using Generic MQTT, telemetry, just-in-time provisioning)
- Azure IoT Central Telemetry support using Azure IoT Hub
Data Logic enhancements
Data Logic now supports the following:
- Read data from multiple asset types (one asset per type)
- Write back into a subset of supported devices that support writable attributes (Local Action)
- Transfer files using the Data Logic script
- Ability to define the structure of output of a Data Logic within the script
- Improved configuration and deployment workflow for Data Logic based policies
Known issues and limitations
- The latest features and enhancements are available only if all EI Agents are upgraded to the latest release.
- File transfer feature in the Data Logic script has the following limitations:
- Currently, the maximum file size supported is 30 MB.
- At any given point of time, only one data logic script which is doing file transfer should be running on an EI Agent.
- EI agents with $ in their name are not detected - workaround: do not use $ in the name of an EI Agent.
- Global objects (e.g. "performance", "output", "parameters", "trigger”) provided/implemented by Scripting Engine are not iterable and accessing the internal properties such as “_name” and “0” will lead to run time java script error.
Updated network device requirements and caveats
See Supported network devices and firmware for information on the supported IOS/IOx versions and caveats for this release.
Open Caveats
| Caveat ID | Description |
|---|---|
| CSCvw76411 | Error "Removing partly instantiated policy" in Modbus leading to removal of shared asset in case two policies are using the same modbus asset where one of them is a multi-input asset policy, the other one is a single-asset data rule policy. |
| CSCvw46410 | Sometimes there is an error seen in UI during policy re-deployment, while in fact on Edge, policy creation is successfully completed. |
| CSCvw53849 | EI agents with certain characters in their name are not detected. |
| CSCvw71631 | Error message in modbus log "Device can't start" while pipeline is processing fine. |
| CSCvw53849 | EI agents with certain characters in their name are not detected. |
| CSCvw71631 | Error message in modbus log "Device can't start" while policy is processing fine. |
Resolved Caveats
| Caveat ID | Description |
|---|---|
| CSCvw78017 | Reduced too big default size of IOx data partition on IR1101 to 256MB and on IC3K to 1GB. |
| CSCvv09366 | Azure connector increased memory when MS Azure Quota was exceeded. |
| CSCvv77875 | New Data Logic automatically created saved last selected EI Agent and Data Destination instead of default values. |
| CSCvv13912 | Selected Data Destination not seen after un-deployment of Data Logic. |
| CSCvv77861 | EI Agents and Data Destination were reset to default on deployment errors. |
| CSCvv19431 CSCvv50110 |
MQTT egress configurations was removed, the policy metadata was not removed from the multiple policy store. This caused issues on undeploy/redeploy operations. |
| CSCvv39915 | MQTT connector disconnected after application restart. |
| CSCvv68959 | MQTT server stopped receiving traffic after policy redeployment. |
| CSCvw66134 | Modbus Link: device model was incompletely configured at the edge. |
| CSCvw66138 | Modbus Link: device model was deployed with incomplete attributes. |
| CSCvw70940 | Modbus serial: added support for parity flag "NONE". |
| CSCvw06800 | Policy status counts were not getting updated (decremented) when a gateway was deleted from the system. |
| CSCvu96074 CSCvu98461 CSCvv23439 |
Several fixes in error messages and error message handling. |
| CSCvw29293 CSCvw29278 CSCvw27432 |
fixed security vulnerabilities: CVE-2020-8203 CVE-2010-4756 CVE-2016-3706 CVE-2020-10029 CVE-2020-1752 CVE-2020-6096 CVE-2020-15168 |
EI 1.0.4 - September 15, 2020
New and revised features
The following production server URLs are now supported when logging in to Cisco IoT from the VS Code app:
See Data Logic for more information.
EI 1.0.2 - August 6, 2020
New and revised features
- EI now supports the IR1101 gateway.
- See Supported edge devices and firmware for more information.
- Download the EI Agent from the Cisco Download Center.
Resolved caveats
| Caveat ID | Description |
|---|---|
| CSCvu99869 | The Modbus connector did not reconnect in rare cases in case the connection was lost. |
| CSCvv23439 | Too many health monitoring updates were sent to the cloud in case a connection was lost in one of the connectors. |
| CSCvv09344 | Fast deploy and un-deploy data policies. |
EI 1.0.0 - July 22, 2020
Supported Features
| Feature | Benefit |
|---|---|
| Integrated device connectivity | Edge Intelligence provides various industry-standard connectors such as Open Platform Communications Unified Architecture (OPC UA), MQ Telemetry Transport (MQTT), and Modbus TCP and Remote Terminal Unit (RTU), and integrates seamlessly with your environment. |
| Data model editor | Customize data models that describe exactly what data will be extracted from your assets. |
| Data logic engine | Deploy custom logic using JavaScript to transform data at the edge. Use data logic to sample high-frequency data streams, apply transformation logic, perform rule-based range validation, or normalize data, depending on specific needs. |
| Microsoft Visual Studio (VS) Code plug-in | Simplify development of data logic by leveraging standard development tools. |
| Data governance | Achieve fine-grained control to help ensure that the right data is delivered to the right applications. Data from any source can be filtered at the attribute level and delivered to multiple selected applications. |
| Application data integration | Deliver your data to any application, either cloud hosted or on premises, using built-in connectivity to services such as Microsoft Azure IoT Hub or industry-standard protocols such as MQTT. |
| Role-based access control | Use segmented configuration and operation to control who has access to what elements of the configuration and operation of your Edge Intelligence solution. |
| Audit trail | Log all operations in Edge Intelligence to help ensure accountability for the integrity of your solution configuration and deployment. |
| Security | Deploy industry-leading built-in security that protects your data and your business. Edge applications are protected through a comprehensive security architecture anchored to a hardware root of trust and built-in Transport Layer Security (TLS). |
| Centralized administration | Use the management software to create all aspects of your edge stack configuration in a centralized place, including data models, data logic, destinations, and policies, to greatly simplify the deployment of these pieces at massive scale. |
| Scalability | Manage the lifecycle of an edge stack and associated workflows on thousands of Cisco network devices. |
| Operational health monitoring | Gain real-time visibility into the operational state of the Edge Intelligence agents and execute state of deployed policies. |
| Data explorer |
Known issues and limitations
The attribute names of asset model definition should be alphanumeric and can contain underscores. The names should not contain hyphens.
There is no limitation on the attribute label naming convention.
Open Caveats
| Caveat ID | Description |
|---|---|
| CSCvu98461 | Error message does not indicate offline status of EI Agent during deployment. |
| CSCvu96074 | Error message is slightly misleading during deletion of a destination in use. |
| CSCvu98296 | The policy status summary for a GW and the detailed policy status (asset offline/online status) are not in synch. |
| CSCvu93540 | Adding prefix to brokerName causes broker to not appear in EI Agents list. |
| CSCvv10758 | Error while creating data policy with certain length of input fields. |
| CSCvv09366 | Azure increases memory when MS Azure Quota is exceeded. |
| CSCvv09344 | Fast deploy and un-deploy data policies. |
EI Agent ( IOx Platform) Caveats
| Caveat ID | Description |
|---|---|
| CSCvt55266 | IOx Secure Storage not responding after a dozen of minutes. |
| CSCvv03543 | Secure storage may not respond due to docker inspect hanging. |
| CSCvu76926 | Unable to activate the EI application due to USB storage mapping being mandated. |