This page contains a list of features, changes, known issues and known limitations of the Nerve releases.
This version was released on October 13, 2023. Unless otherwise stated, all known issues and limitations of the previous version are still valid.
|Product features||Docker Compose workloads now work with multiple containers.|
|Management System||Added a UI for Nerve DNA.
|Local UI||Container logs for Docker and Docker Compose workloads are now accessible in workload management.
Web UI links to access container UIs are generated in the workload management section for Docker Compose workloads.
|Nerve Data Services||Nerve Data Services now available as a Docker compose workload, adding modularity to the overall solution.
Removed the instance of the Nerve Data Services in the Management System.
Dropped support for the Nerve Data Services SDK.
Refer to What's new in 2.7.0? for more information on new features.
- Added workload and version names to the deployment log for easier identification.
- Target ports are now shown in remote connection lists.
- Remote connections can now be configured immediately at node registration.
- Added tabs to the node details view, Overview, Logs and DNA.
- Reserved a range for static IP addresses in the DHCP pool for Nerve internal networks.
- Added a copy to clipboard icon to the serial number field in the Local UI.
- Improved Nerve DNA behavior when a reconfiguration is cancelled.
- Added a flag to applying a target configuration for Nerve DNA to continue configuration after an unexpected event.
- Improved the behavior of the licensing component.
- Improved the communication of the system through error and log messages.
- Miscellaneous UI improvements.
- Nerve Data Services: Improved the data retention policy.
- Nerve Data Services: Improved the logging output of the Gateway.
- Fixed an issue where manually re-installing a node might have given the wan interface of the node a new IP address. An RFC4361 compliant DHCP client identifier is now used.
- Fixed an issue where selecting multiple nodes in the node tree while holding the Shift key caused unwanted duplicates and moving of nodes.
- Fixed an issue where remote connections would be stuck in the connecting state due to slow network speeds.
- Fixed an issue where cloning a Docker Compose workload version would behave differently compared to creating a new version regularly.
- Fixed an issue where deploying workloads and fetching workload lists behaved erroneously in air-gapped Management Systems when the versions between the Management System and the node did not match.
- Fixed an issue where VM workloads would be stuck in the restarting state if the workload is restarted immediately after unpausing.
- Fixed an issue where log messages would not be sent to the Management System due to logging components not being configured correctly after a node update.
- Fixed an issue where CODESYS could not be started due to license issues after an RTVM or node reboot.
- Fixed an issue where 2.2.0 version nodes would produce internal server errors when connected to a 2.6.0 version Management System.
- Fixed an issue where the browser would freeze if the image path of a Docker workload was changed.
- Fixed an issue where an API call would cause the node CPU to reach 100% usage.
- Fixed an issue where a workload version could not be displayed when float values where used for the memory limit.
- Fixed an issue where updating from version 2.5.0 to 2.6.1 was not possible on the Siemens SIMATIC IPC427E.
- Fixed an issue where being logged out of the Management System after inactivity would cause a redirection loop.
- Nerve Data Services: Fixed an issue where the Gateway would crash and fail to restart if the
nameparameters were both defined for MQTT formats.
- Nerve Data Services: Fixed an issue where changing the
publisherIdTypeparameter would not be applied and the parameter stayed the same after a refresh.
Known issues and limitations
- A critical vulnerability was found in CODESYS v.188.8.131.52-7 that is used in the node image for Nerve 2.7.0. CODESYS components CmpApp and CmpAppBP are affected among others. Tags containing commands are not checked for size when sent to the PLC, meaning that attacks on storage are possible.
- When starting a deployment of a workload, the status of the deployment might be wrongly shown as Done in the deployment log.
- In rare cases, nodes go offline after a reboot. A power cycle fixes the issue.
- Removing a node from the Management System produces a large number of logs in the Management System and the node due to continuous reconnection attempts.
- The login page does not adapt after turning LDAP authentication on or off and signing out. Refreshing the page solves the issue.
- In some cases Nerve internal networks stop working due to unknown reasons. The internal networks need to be restarted manually by Nerve service technicians in that case.
- VM workloads provisioned in older Management Systems might not work in the current Management System version.
- Synchronization of LDAP roles and permissions does not work as expected after the initial synchronization. Making changes in the LDAP configuration after the initial configuration and attempting to synchronize new changes for user roles in the Management System does not carry over changes successfully.
Refer to the table below for information on the compatibility between different components of the Nerve system with the current version of the Management System.
|Management System version||Node version||MS/node compatibility||Nerve Connection Manager (v1.0.13)||Incremental node update||Full support|
For more information on technical limitations (), and requesting assistance with setting up older versions in the current version (), contact a sales representative or write an issue through the TTTech Industrial support portal.
Scaling and performance limitations
This release has been tested to perform within the following scaling boundaries:
|Maximum number of concurrent devices||200|
|Maximum number of concurrently logged in users||5|
|Maximum workload size||50 GB|
|Maximum number of concurrent remote access sessions||3|
|Maximum number of workloads in workload repository||200|
|Maximum data upload per node||5 datagrams per second with at least 10 sensor values for 200 nodes in parallel.|