Skip to main content

Illumio Core What's New and Release Notes 24.5

Resolved Issues in NEN 2.4.0

  • VS filtering failed to work correctly on secondary NEN nodes (E-90850)

    The secondary NEN node didn't perform Virtual Server (VS) filtering even though VS filtering was enabled on the NEN. This meant that VS filtering occurred only on the primary NEN node, which sometimes caused the VS to appear and disappear in the PCE Web Console.

  • For an AVI SLB, NENs reported tenant names incorrectly in the non-admin tenant space (E-90758)

    When discovering non-admin tenant Virtual Servers on an AVI multi-tenant Server Load Balancer (SLB), the NEN reported Virtual Server names according to their tenant UUID instead of their tenant name (Infrastructure > Load Balancers > AVI SLB > Virtual Servers tab). The NEN also used the tenant UUID in the API header it sent to the AVI SLB when it tried to program the Virtual Server. This prevented policy from being programmed on those Virtual Servers. This issue is resolved; NENs now correctly use the tenant name of discovered Virtual Servers.

  • When adding a switch, the list of supported switches was incomplete for the attached NENs (E-85844)

    Given two active NENs attached to a PCE, each a different version supporting different switches:

    When adding a new switch through the PCE Web Console, the Manufacturer drop down list showed only switches that are supported by the first NEN in the NEN host name drop down list. This occurred regardless of which NEN host the user selected. The incomplete list of switches could've prevented users from selecting the precise switch type they were trying to integrate or might have lead them to select a switch type that's not supported by the selected NEN host. This issue is resolved. The Manufacturer list now shows the switch(es) supported by whichever host is selected in the NEN host name drop down list.

  • Memory leak in NEN process (E-85114)

    When programming a large number of virtual servers, excessive memory consumption in the network_enforcement_ndconfig process could've resulted in an out-of-memory exception in rare circumstances. This issue is resolved.