This chapter lists the known general issues and limitations that affect the current release. LXCR-9904Enea Edge Runtime cannot be installed on USB storage devices. LXCR-9799Proper boot order is not ensured if a uCPE device has more than one HDD attached. ELCCR-527Cancelling a file upload in the Enea Edge Management will require the user to close and reopen the upload window for the next upload to work. ELCCR-577If the Enea Edge Management application is restored from a backup made on a release version older than Enea NFV Access 2.2.3, VNFs cannot be instantiated from the GUI. ELCCR-1134In order to avoid an incorrect boot order after a failed upgrade, the user should remove the upgrade image before attempting again. ELCCR-474Deleting VNF instances with flows configured on the OVS bridges can be done only after removing the flows. ELCCR-572Sometimes when selecting and deleting more than one VNF instance simultaneously, an error message might be triggered, even if the delete operation succeeds. ELCCR-847The Juniper vSRX VNF cannot be instantiated on the Xeon-D architectures due to missing CPU features in the VNF's domain XML. This impacts all example use cases where the Juniper VNF is used. USERDOCAP-648The storage size parameter on the VNF onboarding page is ignored. The default storage size specified when creating the VM image is used when instantiating the VM and when presenting VM information. LXCR-9853The WAN interface of a uCPE device needs to be connected to a network with at least a router/gateway installed for next-hop communication. ELCCR-1504To change the type of an interface from DPDK to SR-IOV, first delete the existing interface, then recreate it with the desired type. LXCR-9992Depending on hardware capabilities, there are certain limitations regarding the vfio-pci and igb_uio drivers. While the Enea Edge Runtime uses the vfio-pci driver by default, for certain hardware configurations, igb_uio should be used instead, by providing custom scripting. Please contact Enea for further details. STCR-6224The Enea Edge Automation and the Enea Edge Automation Framework and Test Harness do not support multiple custom scripts uploaded to a uCPE device at the same time. STCR-6292Management of WAN Interfaces is not implemented in the Enea Edge Automation Framework and Test Harness. USERDOCAP-628Enea Edge Automation Framework and Test Harness does not have support for product features implemented in Enea Edge 2.4.0 or newer. ELCCR-912When the Enea Edge Management application is installed on CentOS 7, prior to C7.1804 (kernel version 3.10.0-862), adding an upgrade image fails. As a workaround, please update glib2 to version 2.54.2 or later, using #yum update glib2. USERDOCAP-641Enea Edge does not have support for IPv6 addresses on both uCPE devices and the Enea Edge Management installation. USERDOCAP-651Wireless AP configuration is optimized for wireless modules that use the ath10k driver. Using other wireless modules may result in undefined behavior. ELCCR-1518The Wireless AP's wpa2psk password should not contain white space characters. ELCCR-1561Before starting an Enea Edge Management upgrade, any owned Tomcat certificates should be manually copied into the /opt/ems/ucpemanager/application/3rdParty/apache-tomcat/conf/config/certificates folder. ELCCR-1378Modifying the type of the external interfaces can lead to errors. Instead of modifying, it is recommended to delete the old interfaces and recreate them with the desired type. ELCCR-1497If the Enea Edge Management application has an incorrect database configuration, when performing an uninstallation, the Tomcat instance and Watchdog service will not be stopped automatically. Instead, they must be killed explicitly. ELCCR-1468When using the Enea Edge Management application in HTTPS mode, upgrading a device from NFV Access 2.3.0 is not possible. Either switch to HTTP mode (for more details see The uCPE device Upgrade Process in the Manual) or install it manually. LXCR-3283PDF navigation: When using links to open other PDFs, or jump to another place in the same PDF, jumping back sometimes fails. This has been observed when opening a PDF in Adobe Reader, inside a browser with PDF add-on, as well as when the browser is configured to open PDF files in an external PDF reader. As a workaround, open the HTML version of the document.