As of May 14, 2024, Knowledge Base (KB) articles will only be published and updated in our new Trellix Thrive Knowledge space.
Log in to the Thrive Portal using your OKTA credentials and start searching the new space. Legacy KB IDs are indexed and you will be able to find them easily just by typing the legacy KB ID.
Issue resolutions in updates and major releases are cumulative; Technical Support recommends that you install the latest version. To find the most recent release for your product, go to the Product Downloads site.
IMPORTANT:
This article only applies to the DXL Broker.
The DXL 5.0.0 client and later are now integrated with McAfee Agent (MA) 5.6.0 and later. It's no longer a standalone component deployed by DXL.
All DXL client issues are contained within the MA Known Issues articles.
Contents
Click to expand the section you want to view:
Issue: This hotfix repackages the DXL extension to work with Tomcat 9.
Starting with ePO 5.10 cumulative Update 10, the version of Tomcat used by ePO is upgraded to Tomcat 9. This change requires several extensions to be updated before you apply update 10.
ePO 5.10 is upgrading the Tomcat on ePO 5.10 to Tomcat version 9 because of the forthcoming End of Life (EOL) of Tomcat version 7.
Issue: DXL Broker service on Windows doesn't contain a quoted string for a binary path.
Resolution: This issue is resolved in DXL 6.0.0 Hotfix 1.
Reference Number
Related Article
Found
In
Fixed
In
Issue Description (DXL Broker)
DXLM-4495
-
DXL 6.0.0
DXL 6.0.3
Issue: On the Trellix DXL Broker appliance, reconfig‑dxl fails to set the custom Trellix DXL Broker Listen Port.
DXLM-7201
-
DXL 6.0.0
DXL 6.0.3
Issue: Previously switching the Trellix ePO - SaaS customer account on MVISION Cloud Bridge doesn't update IAM credentials in the Trellix DXL Broker server. Because of this problem, the Trellix DXL Broker server fails to send EDR traces to a new account.
DXLM-7040
-
DXL 6.0.0
DXL 6.0.3
Issue: When a user visits the Trellix TIE topology page for Trellix DXL connection health check, the Audit Log in Trellix ePO - on-premises makes the following incorrect entry:
Failed to return the service zone setting for the node.
DXLM-7038
-
DXL 6.0.0
DXL 6.0.3
Issue: When MVISION Cloud Bridge fails to link the IAM account, the Audit Log in Trellix ePO - on-premises records the following entry:
Process ePO Tokens DXL Event.
DXLM-7237
-
DXL 6.0.0
DXL 6.0.3
Issue: The file name of IPE logs of DXL 6.0.0 Hotfix 5 doesn't update in chronological order.
DXLM-7157
-
DXL 6.0.0 Hotfix 3
DXL 6.0.0 Hotfix 5
Issue: The compatibility issues are occurred due to the removal of third-party library packages.
DXLM-7165
-
-
DXL 6.0.0 Hotfix 5
Issue: DXL Broker appliance is updated with Trellix Agent 5.7.7.
DXLM-4484
-
DXL 6.0
DXL 6.0.0 Hotfix 3
Issue: Certificate validation issue, and traffic from the DXL extension is blocked.
DXLM-3865
-
-
DXL 6.0.0
Issue: DXL Broker fails to submit the trace data to the MAR Cloud.
-
-
DXL 6.x
-
Issue: The error message below is recorded in the DXL client logs: