Resolved Issues in 22.5.22-PCE
High memory consumption on Supercluster data nodes could occur (E-105671, E-104608)
Due to a memory leak in the database replication process, the memory consumption on data nodes of a Supercluster could gradually increase. This issue is resolved. In this release, a memory leak no longer causes memory consumption by the PCE to continuously increase.
Traffic worker not coming up after stop/start (E-105637, E-104519)
After operations involving changes in the runlevel and/or service restart, in rare circumstances, the app gateway service generated duplicate proxy ports. This resulted in the failure of services, such as traffic worker, to connect to Redis-related services, with a "wrong password" exception. This issue is resolved.
Illumination Plus could show allowed traffic as blocked (E-105554, E-101506)
When selecting “Deep rule analysis” from the View menu, Illumination Plus could show traffic was blocked for flows that had
allow
rules. However, when you selected “Quick Draft Rules” from the View menu in Illumination Plus, or used the classic version of Explorer, you saw that the traffic was allowed. This issue is resolved. Using Deep Rule Analysis to view traffic that hasallow
rules now correctly shows that the traffic is allowed.Data in exported CSV files didn't match policy decision data in Explorer (E-104439)
When exporting policy data from Explorer, the content in the CSV file didn't match the policy data on the Explorer page. This issue occurred because the PCE exported the aggregate traffic flows and not the individual connections, which the Explorer page displays. This issue is resolved. In this release, exporting policy data from Explorer correctly exports the individual connections. The CSV file now matches the data displayed in the PCE web console Explorer page.