Protection Workspace showing Data eXchange Layer out of compliance on RHEL 6 ONLY

[BleachX]

We have a small amount of RHEL 6 boxes still being used on some Government contracts.  DXL was working for all systems until we upgraded to Trellix Agent 5.7.9.  I've been unable to figure out why this is happening.  By chance, is anyone else out there noticing DXL issues in Protection Workspace after upgrading to TA 5.7.9?  Does anyone have an idea of what I can try to fix this?

Update: As soon as I removed TA 5.7.9 and put the previous version on it, DXL connected again and compliance went up.  Is there something that stops DXL with RHEL 6 when installing TA 5.7.9???

[cdinet]

What is the version of dxl that is running on the RHEL systems?  I want to verify it was upgraded.  There should also be a dxl log in C:\ProgramData\McAfee\Data_Exchange_Layer folder.  What errors does that show?  Did you also upgrade the dxl broker to latest version?

That being said, RHEL 6.x has note in KB51573

For TA 5.7.9, version glibc 2.17 or later needs to be installed to support DXL client.

[BleachX]

Good morning.  The DXL Platform we have is 6.0.3.990.  The DXL Broker version shows 6.0.0.301.  I just noticed through Data Exchange Layer Fabric that all brokers except the ePO are disconnected or showing offline.  However, I know the servers are online.

I show glibc-2.17-326 is installed.  I'll check the DoD patch repository for an update to DXL Broker.  That must be it.

[BleachX · Accepted solution]

Apologies for the late response.  I've been doing a lot of testing for this issue and have found the entire issue has been caused by Network Administrators that made changes to the network that caused port 8883 to be blocked at the ASA level.  Systems on a different network being unable to reach the ePO for DXL is what changed the compliance numbers of course.

Once again, thank you for your help @cdinet