VMware NSX Intelligence 4.1.2 | 11 APR 2024 | Build 23624714

Check for additions and updates to these release notes.

What's New

VMware NSX® IntelligenceTM 4.1.2 provides the following support and new enhancements:

NSX Intelligence 4.1.2 is an update release that comprises bug fixes only.

System Requirements

For system requirements information, see Activating and Upgrading VMware NSX Intelligence. You can also install NSX Intelligence 4.1.2 using NSX Application Platform Automation Appliance 4.1.2. See Deploying and Managing NSX Application Platform Using Automation Appliance.

For information about ports and protocols required for NSX Intelligence, see the VMware Ports and Protocols information for VMware NSX Application Platform, which hosts the NSX Intelligence application.

Compatibility Notes

  • For NSX Intelligence and NSX interoperability information, see VMware Product Interoperability Matrices.

  • NSX Intelligence is interoperable with NSX Federation deployments but does not directly support NSX Global Managers. To use the NSX Intelligence user interface, you must access the Local Manager instead of the Global Manager. For deployments with NSX Federation, if an NSX Intelligence instance is deployed with the Local Manager on a specific site, you will see groups from the Global Manager and traffic flows from workloads that are connected to the global objects. However, the visualization will not reflect specifics from other sites. NSX Intelligence recommendations will also not function across various sites because NSX Intelligence does not integrate with the Global Manager of NSX Data Center.

API and CLI Resources

See the NSX Intelligence and NSX Application Platform API Reference page for the available NSX Intelligence REST API and CLI resources.

Available Languages

NSX Intelligence has been localized into multiple languages: English, German, French, Italian, Japanese, Simplified Chinese, Korean, Traditional Chinese, and Spanish. Because NSX Intelligence localization utilizes the browser language settings, ensure that your settings match the desired language.

Resolved Issues

  • Fixed Issue 3360704: In some cases, a control plane node memory calculation error might cause executions to remain perpetually pending.

    The control plane node in the Kubernetes cluster does not have enough memory to allocate to all the executors.

  • Fixed Issue 3257000: The Spark operator responsible for submitting Spark applications might encounter submission issues due to incorrect submission arguments or a lack of retries after failure.

    The Spark applications pods are not on the list of running pods. If these pods are not running, the flows cannot be ingested and processed by NSX Intelligence.

  • Fixed Issue 3367686: NSX Intelligence UI displays alarms that persistent storage is high with an error message, The disk usage of Data Storage service is above the high threshold value of 75%.

    Due to recurring failures of Druid reindexing tasks in high-scale environments, the NSX Application Platform disk usage is high, resulting in storage reaching capacity.

  • Fixed Issue 3360720: Reusing a group API with zero members might cause a null pointer exception.

    When you start a recommendation, reuse it for an existing group, and remove all the existing members. Clicking the group rule in the UI to view group details might result in a null pointer exception.

  • Fixed Issue 3262210: Traffic flows might be visualized into only a single cluster node named Unclustered.

    When viewing the traffic flows using the Computes or Groups view visualization after upgrading to NSX Intelligence 4.1.1, the traffic flows might be displayed as one cluster node only, named Unclustered, even after a few hours since the upgrade to version 4.1.1 has completed.

Known Issues

  • Issue 3399401: In the Suspicious Traffic feature, the VM exclusion configuration for the "Netflow Beaconing" detector is ignored.

    The VM exclusion configuration is ignored by the Netflow Beaconing detector. 

    As a consequence, this detector monitors all VMs including those that may be configured as excluded and may generate events for these VMs.

  • Issue 3403381: In the Suspicious Traffic page, events generated from the "Port Profiler" and "Server Port Profiler" cannot be expanded.

    Attempting to expand an event generated by the "Port Profiler" or "Server Port Profiler" detectors in the Suspicious Traffic UI, an error occurs, and the details pane displays the message 'No details found'.

    Only high-level information for the affected event is available, including timestamp, affected VMs, MITRE ATT&CK information and detector information.

  • Issue 3215655: While upgrading the NSX Application Platform, some periodic NSX Intelligence cronjobs might not run if an older repository URL is blocked before the repository URL is updated to point to the new repository that contains the uploaded target version charts and images.

    Some pods might encounter the ImagePullBackoff error after the old repository URL is blocked before the repository URL is updated to point to the new repository. The NSX Application Platform upgrade might complete but certain periodic NSX Intelligence cron jobs might not be able to run after the upgrade completes.

    Workaround: Log in to the NSX Manager and use the following command to manually delete the failed or stuck jobs.

    napp-k delete job <job-name>

    Also, avoid blocking access to an older repository URL before the NSX Application Platform upgrade has completed.

  • Issue 2389691: Publish recommendation job fails with error "request payload size exceeds the permitted limit, max 2,000 objects are allowed per request."

    If you try to publish a single recommendation job that contains more than 2,000 objects, it will fail with error "request payload size exceeds the permitted limit, max 2,000 objects are allowed per request."

    Workaround: Reduce the number of objects to fewer than 2,000 in the recommendation job and retry the publication.

  • Issue 2599301: Some active sessions are not visible on the NSX Intelligence user interface for the Last 1 Hour view and are not picked up by the Recommendations module for recommending policies.

    There are active traffic flows running on compute hosts, but these traffic flows are not visible in the Last 1 Hour view on the NSX Intelligence user interface. Starting a recommendation analysis for the involved compute hosts does not generate any recommendations for those traffic flows even though those traffic flows are unsegmented.

    Workaround: Synchronize the timestamps across all the compute hosts that are exporting the network traffic flows.

  • Issue 2839668: Old traffic flow data and configuration data from the previous NSX Intelligence deployment are still displayed after NSX Intelligence is reactivated.

    If NSX Intelligence is deactivated, but the NSX Application Platform remains deployed, the old traffic flow data and configuration data from the previous NSX Intelligence deployment continue to be displayed after NSX Intelligence is reactivated. There is no easy way to clean up the old data and keep them from being displayed.

    Workaround: Contact the VMware Support team for assistance with cleaning up the old data.

Document Revision History

Revision Date

Edition

Changes

11 APR, 2024

1

Initial edition.

10 JUL, 2024

2

Added known issues 3403381, 3399401.
check-circle-line exclamation-circle-line close-line
Scroll to top icon