Is it possible to share DXL/TIE servers with multiple ePO servers? This would be useful during a transition to a new ePO server or between a test & production ePO servers.
Are there issues when updating DXL/TIE software or extensions?
Solved! Go to Solution.
Hi @ctcc-dave ,
There are two queries let me answer both,
1. DXL and TIE extension upgrade do not cause any conflict. But if you are upgrading TIE extension ensure the TIE server appliance is also upgraded to the same version. Since there is a Health check called extension compatibility for TIE server hence if extension and product version is different it would result in the check to fail.
2. To share the DXL / TIE infrastructure
For example, if you have two ePO's namely ePO A and ePO B. Assume you manage TIE & DXL in ePO A and in ePO B setup you can only have the DXL broker installed. Then you can create a DXL bridge (outgoing/incoming) which would help both infra's to be managed by a single TIE server.
For more information about creating a DXL bridge kindly review the URL https://docs.mcafee.com/bundle/data-exchange-layer-4.1.0-product-guide-epolicy-orchestrator/page/GUI...
Please, let me know if you find my response helpful by clicking 'Accept as Solution' and share a 'Kudos'
Regards
Adarsh.
Hi @ctcc-dave ,
There are two queries let me answer both,
1. DXL and TIE extension upgrade do not cause any conflict. But if you are upgrading TIE extension ensure the TIE server appliance is also upgraded to the same version. Since there is a Health check called extension compatibility for TIE server hence if extension and product version is different it would result in the check to fail.
2. To share the DXL / TIE infrastructure
For example, if you have two ePO's namely ePO A and ePO B. Assume you manage TIE & DXL in ePO A and in ePO B setup you can only have the DXL broker installed. Then you can create a DXL bridge (outgoing/incoming) which would help both infra's to be managed by a single TIE server.
For more information about creating a DXL bridge kindly review the URL https://docs.mcafee.com/bundle/data-exchange-layer-4.1.0-product-guide-epolicy-orchestrator/page/GUI...
Please, let me know if you find my response helpful by clicking 'Accept as Solution' and share a 'Kudos'
Regards
Adarsh.
If I am setting up a new ePO server and I require the new MA 5.6.3 & the DXL 6.0 client that would use a new DXL broker with the 6.0 version.
Would the new DXL broker(6.0) be able to bridge with an older version of DXL (5.0.2)?
thanks
dave
Hi @ctcc-dave ,
DXL Broker extension are backward compatible and it would connect.
For further information, kindly review this article https://kc.mcafee.com/corporate/index?page=content&id=KB90421 and if you require any clarification you can use this channel.
Please, let me know if you find my response helpful by sharing a 'Kudos'
I seem to have a successful DXL bridge between the two ePO environments now. What steps would be necessary for the TIE reputations to be viewed on the new ePO server?
dave
I do see the task Send State DXL State Event is scheduled and running daily.
Should the TIE extension be added to the new server? Are there any additional steps in this process?
Dave
Hi @ctcc-dave ,
Definitely you may require a TIE service (Extension and appliance) in the ePO B setup which would help you to handle the reputation requests and sent to the primary in ePO A.
I would recommend you to review this architecture referred in this URL https://docs.mcafee.com/bundle/data-exchange-layer-5.0.x-product-guide/page/GUID-B80F2B8C-F57E-40D2-...
Please, let me know if you find my response helpful by sharing a "Kudos"
Corporate Headquarters
6220 America Center Drive
San Jose, CA 95002 USA