Version 2.2.0-25-x86-64 - Manual - Industrial Edge - Industrial Edge - Industrial Edge - Documentation of the Industrial Edge Platform - IEM - Hub - Industrial - Device - IED - Edge - IEH

Title	Description
Firmware name	simatic-ipc-ied-os-2.2.0-25-x86-64
Industrial Edge Device Kit version	1.19.1-1
Docker version	20.10.5
Operating system	Debian 11 Bullseye
Release date	July 12, 2024
What's new?	The following features are inside SIMATIC IPC Industrial Edge Device OS (SIMATIC IPC IED-OS) V2.2: IEDK v1.19.1 features (Resource Manager features (e.g. CPU/NIC/GPU allocation) are not included) sosreport upgrade (v4.6.1) - text based logs support
Known Issues	The following are the known issues: Issue Troubleshooting Connecting an Edge Device to the IEM fails and the "Nginx configuration test failed" error message is displayed during activating the Edge Device phase. Check the DNS server configuration since the error message is DNS server related. The DNS server must be configured properly and reachable for the IEM. In case user data of edge device is corrupted due to unexpected power-outage or forcibly shutdown of edge device. IED-OS filesystem recovery process is going to take place. The process might take 2-3 hours depending on hardware specification of the running device. - Sporadically, the Edge Device might stuck during the boot phase when you perform a firmware update. Switch off the Edge Device and switch the Edge Device on again manually. After switching on the Edge Device, the Edge Device will boot from the previous firmware version. After that, you can again trigger the firmware update process. In case several apps are being installed at the same time, it takes a while to reach the Edge Device UI. Wait for a while to reach the Edge Device UI After you onboard a SIMATIC IPC427E Edge Device with IED-OS version 1.3.0-57, the "Unknown Version" notification will be displayed in the "Firmware Update" screen when updating the Edge Device. After updating the IED-OS to a newer version, this message disappears. Firmware update gets stuck in IED-OS v1.9 after the device is reset. Device should be rebooted one more time manually via IED or IEM after reset process is completed. During firmware update IED might fail to activate device due to a failure in IE Device Catalog service and might get stucked in Activating state. The device should be rebooted. It is expected that the device would boot from the previous firmware. Firmware update should be triggered again. Depending on the restart policies of the apps, the apps might not restart automatically after the reboot (includes also firmware update since it reboots the device). These apps should be manually started. IED can have two selected Gateway Interfaces when one network interface configured as Gateway Interface from IED UI before onboard and another network interface configured as Gateway Interface during the creation of Edge Device configuration file in IEM. While connecting the IPC Edge Device, Pre-Onboard Network Configurations made from IED UI should be checked in order to perform a flawless connection with New IPC Edge Device Onboarding Network Configurations generated from IEM. After network settings change from static IP to DHCP via Device UI, it takes a while to finalize the setting of new IP. Wait for a while to see the new IP settings. If you set the IPs on the same subnet for network inter‐faces, one of the connections may be broken. Do not set more than one IP on the same sub‐net.
Fixed issues	The following bugs have been fixed with SIMATIC IPC IED-OS V2.2: Bug fixes for the IE Runtime.
Other information	You can find more information from Release Notes & Operational Manual