Skip to main content

Illumio Core What's New and Release Notes 22.2

What's New and Changed in Release 22.2.10

Illumio Core 22.2.10 introduces the following new features and enhancements.

Important

Illumio Core 22.2.10-PCE is available for Illumio Core On-Premises customers only.

The 22.2.10-VEN is available for both Illumio Core On-Premises customers and Illumio Core Cloud customers.

Illumio Core 22.2.10 Maintenance Release

Illumio provides regular maintenance updates for reported bugs and security issues, and to add support for new operating system versions. As a maintenance release, Illumio Core 22.2.10 solved software and security issues to refine the software and improve its reliability and performance.

For more information about the Illumio software release types and software support, see Versions and Compatibility on the Illumio Support portal (login required).

New Features in Illumio Core 22.2.10

PCE Replication and Failover

To increase reliability, you can set up replication and failover for PCEs. Having a PCE on "warm standby," ready to take over if the active PCE fails, contributes to a resilient disaster recovery (DR) plan.

For PCE replication and failover, set up PCEs in pairs. Each pair has an active PCE and a standby PCE. A combination of continuous real-time replication and periodic synchronization is used to keep the standby PCE's data up to date with the active PCE. If the active PCE fails, the standby PCE can take over and become the new active PCE.

Reassign a NEN from one PCE to Another in a Supercluster through CLI or API

You can move a NEN from one PCE to another PCE in the same supercluster using either a command line or through the API. When a NEN is moved in this way, associated Server Load Balancers maintain policy for managed virtual servers. After the PCE database is restored, the moved NEN remains connected to the new PCE. For details on reassigning a NEN from one PCE to another in a Supercluster using either method.

Enhancements in the Illumio Core REST APIs

Illumio Core 22.2.10 introduced the following new public experimental REST API.

Update the NEN with a New Target PCE hostname

/api/v2/orgs/<org-id>/network_enforcement_nodes/<uuid>

Use the following payload:

{
  "$schema": "http://json-schema.org/draft-04/schema#",
  "description": "Update a NEN's target PCE.",
  "type": "object",
  "additionalProperties": false,
  "properties": {
    "target_pce_fqdn": {
      "description": "cluster FQDN for target PCE",
      "type": "string"
    }
  }
}