Unable to see both nodes of a cluster in the ePO directory when they share a MAC address
Last Modified: 2023-07-11 09:26:41 Etc/GMT
Affected Products
Languages:
This article is available in the following languages:
Trellix CEO, Bryan Palma, explains the critical need for security that’s always learning.
As per Gartner, "XDR is an emerging technology that can offer improved threat prevention, detection and response."
Trellix announced the establishment of the Trellix Advanced Research Center to advance global threat intelligence.
Trellix Advanced Research Center analyzes threat data on ransomware, nation-states, sectors, vectors, LotL, MITRE ATT&CK techniques, and emails.
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.
Unable to see both nodes of a cluster in the ePO directory when they share a MAC address
Technical Articles ID:
KB57886
Last Modified: 2023-07-11 09:26:41 Etc/GMT Environment
ePolicy Orchestrator (ePO) 5.x McAfee Agent (MA) 5.x Problem
You're unable to see both nodes of a cluster in the ePO directory. Both nodes share a MAC address. A single entry for these systems exists, and the properties are regularly overwritten. System ChangeCause
When an agent communicates with the ePO server, the server first checks whether the agent's GUID exists in the database:
In this situation, the first node to communicate is added to the database correctly. But, when the second node communicates, its properties replace those properties of the first node because it has a new GUID, but the same MAC address. When the first node communicates again, its properties replace the properties of the second node. As a result, only one node displays in ePO at any given time. Solution
To resolve this situation, disable the additional MAC search on the server long enough to allow all nodes to be added to the database. NOTES:
Workaround
ePO 5.10.0 or later This version has a new feature to add the
Affected ProductsLanguages:This article is available in the following languages: |
|