1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
|
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<chapter id="bugs-limitations">
<title>Known Issues and Limitations in this Release</title>
<para>This chapter lists the known general issues and limitations that
affect the current release.</para>
<itemizedlist>
<listitem>
<para><remark>LXCR-9904</remark>Enea Edge Runtime cannot be installed on
USB storage devices.</para>
</listitem>
<listitem>
<para><remark>LXCR-9799</remark>Proper boot order is not ensured if a
uCPE device has more than one HDD attached.</para>
</listitem>
<listitem>
<para><remark>ELCCR-527</remark>Canceling a file upload in the Enea Edge
Management application will require the user to close and reopen the
upload window for the next upload to work.</para>
</listitem>
<listitem>
<para><remark>ELCCR-577</remark>If 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.</para>
</listitem>
<listitem>
<para><remark>LXCR-10750</remark>In order to avoid an incorrect boot
order after a failed upgrade, the user should remove the upgrade image
before attempting again.</para>
</listitem>
<listitem>
<para><remark>ELCCR-474</remark>Deleting VNF instances with flows
configured on the OVS bridges can be done only after removing the
flows.</para>
</listitem>
<listitem>
<para><remark>ELCCR-572</remark>Sometimes when selecting and deleting
more than one VNF instance simultaneously, an error message might be
triggered, even if the delete operation succeeds.</para>
</listitem>
<listitem>
<para><remark>ELCCR-847</remark>The 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.</para>
</listitem>
<listitem>
<para><remark>USERDOCAP-648</remark>The <literal>storage size</literal>
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.</para>
</listitem>
<listitem>
<para><remark>LXCR-9853</remark>The WAN interface of a uCPE device needs
to be connected to a network with at least a router/gateway installed
for next-hop communication.</para>
</listitem>
<listitem>
<para><remark>LXCR-9992</remark>Depending on hardware capabilities,
there are certain limitations regarding the <literal>vfio-pci</literal>
and <literal>igb_uio</literal> drivers. While the Enea Edge Runtime uses
the <literal>vfio-pci</literal> driver by default, for certain hardware
configurations, <literal>igb_uio</literal> should be used instead, by
providing custom scripting. Please contact Enea for further
details.</para>
</listitem>
<listitem>
<para><remark>STCR-6224</remark>The Enea Edge Automation Framework and
Test Harness do not support multiple custom scripts uploaded to a uCPE
device at the same time.</para>
</listitem>
<listitem>
<para><remark>STCR-6292</remark>Management of WAN Interfaces is not
implemented in the Enea Edge Automation Framework and Test
Harness.</para>
</listitem>
<listitem>
<para><remark>USERDOCAP-628</remark>The Enea Edge Automation Framework
and Test Harness do not have support for product features implemented in
Enea Edge 2.4.0 or newer.</para>
</listitem>
<listitem>
<para><remark>ELCCR-912</remark>When 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 <literal>glib2</literal> to version 2.54.2 or later, using
<literal>#yum update glib2</literal>.</para>
</listitem>
<listitem>
<para><remark>USERDOCAP-641</remark>Enea Edge does not have support for
IPv6 addresses on both uCPE devices and the Enea Edge Management
installation.</para>
</listitem>
<listitem>
<para><remark>USERDOCAP-651</remark>Wireless AP configuration is
optimized for wireless modules that use the <literal>ath10k</literal>
driver. Using other wireless modules may result in undefined
behavior.</para>
</listitem>
<listitem>
<para><remark>ELCCR-1565</remark>Before starting an Enea Edge Management
upgrade, any owned Tomcat certificates should be manually copied into
the
<literal>/opt/ems/ucpemanager/application/config/certificates</literal>
folder.</para>
</listitem>
<listitem>
<para><remark>ELCCR-1497</remark>If 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.</para>
</listitem>
<listitem>
<para><remark>ELCCR-1468</remark>When 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 <olink
targetdoc="book_enea_edge_getting_started"
targetptr="device_up_process">The uCPE device Upgrade Process in the
<xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
xmlns:xi="http://www.w3.org/2001/XInclude"
xpointer="element(book_enea_edge_getting_started/1)" /></olink> Manual)
or install it manually.</para>
</listitem>
<listitem>
<para><remark>ELCCR-1688, ELCCR-1809</remark>It is possible to end up
with a corrupted VM image from the download operation. If that happens,
the VNF instantiation will fail. The corrupted image has to be manually
removed from <literal>/var/odm/vm_images/startup/</literal>.</para>
</listitem>
<listitem>
<para><remark>ELCCR-1925</remark>VNF filtering based on VIM does not
work.</para>
</listitem>
<listitem>
<para><remark>ELCCR-1733</remark>Logging into the Enea Edge Management
application over HTTP can fail. If this happens, the user should clear
the session cookie from the browser.</para>
</listitem>
<listitem>
<para><remark>ELCCR-1571</remark>Uploading a domain update script when
instantiating a VNF does not work. The modifications from the script are
not taken into account.</para>
</listitem>
<listitem>
<para><remark>ELCCR-1757</remark>The management WAN interface can be
overwritten from an offline config.</para>
</listitem>
<listitem>
<para><remark>ELCCR-1845</remark>Enea Edge Telemetry does not work.</para>
</listitem>
<listitem>
<para><remark>ELCCR-1873</remark>Failover to a previous working image
when booting a faulty Enea Edge Runtime image does not work.</para>
</listitem>
<listitem>
<para><remark>ELCCR-1753</remark>For tap interfaces, port numbers
assigned to VM bridge interfaces can change when the VMs are
restarted.</para>
</listitem>
<listitem>
<para><remark>ELCCR-1758</remark>Socket Memory filed in DPDK settings
needs to be larger than 1 GB.</para>
</listitem>
<listitem>
<para><remark>ELCCR-1658</remark>VNFs that have been offboarded after a
backup is complete, cannot be restored by the NFVi backup
functionality.</para>
</listitem>
<listitem condition="hidden">
<para><remark>LXCR-3283</remark><emphasis role="bold">PDF
navigation</emphasis>: 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.</para>
</listitem>
</itemizedlist>
<!-- The file with a section below is autocreated by make init -->
<!-- <xi:include href="jiraissues_generated.xml"
xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
</chapter>
|
