# Dynatrace Managed multiple network interfaces **URL:** \ **Category:** Dynatrace Managed\ **Tags:** dynatrace-managed, managed-cluster\ **Created:** [May 25, 2022, 2:02pm UTC](https://community.dynatrace.com/t/dynatrace-managed-multiple-network-interfaces/35278 "2022-05-25T14:02:52Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![henk\_stobbe](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/henk_stobbe/32/30434_2.png) [@henk\_stobbe](https://community.dynatrace.com/u/henk_stobbe)\ **Post date:** [May 25, 2022, 2:02pm UTC](https://community.dynatrace.com/t/dynatrace-managed-multiple-network-interfaces/35278/1 "2022-05-25T14:02:52Z")
Hello, We have multiple interfaces on our nodes hosting the Dynatrace managed cluster. Only one interface per host can be used by agents and activeGates to connect to the cluster.. So all agents and activeGates use a list of addresses that can not be used, ever! This situation exist for a long time, does anybody have a suggestion how to remove those unused interface from Dynatrace config? KR Henk ---
**Author:** ![techean](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/techean/32/227_2.png) [@techean](https://community.dynatrace.com/u/techean)\ **Post date:** [May 26, 2022, 4:25am UTC](https://community.dynatrace.com/t/dynatrace-managed-multiple-network-interfaces/35278/2 "2022-05-26T04:25:09Z")
Kindly raise a support ticket if its for any organization. ---
**Author:** ![AntonioSousa](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/antoniosousa/32/50_2.png) [@AntonioSousa](https://community.dynatrace.com/u/AntonioSousa)\ **Post date:** [May 26, 2022, 8:29am UTC](https://community.dynatrace.com/t/dynatrace-managed-multiple-network-interfaces/35278/3 "2022-05-26T08:29:31Z")
[@henk\_stobbe](https://community.dynatrace.com/user/11427), You can define what gets announced in CMC. For each node check out “Deployment status”, then “Configure” on each node. At the bottom, check: ![AntonioSousa_0-1653553717636.png](https://global.discourse-cdn.com/dynatrace/original/2X/6/64a5804b27b6ea5f8d6886b101b509e9e663a9a8.png) ---
**Author:** ![henk\_stobbe](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/henk_stobbe/32/30434_2.png) [@henk\_stobbe](https://community.dynatrace.com/u/henk_stobbe)\ **Post date:** [May 26, 2022, 9:12am UTC](https://community.dynatrace.com/t/dynatrace-managed-multiple-network-interfaces/35278/4 "2022-05-26T09:12:14Z")
Hi Antonio, Thx for your response, this takes care of 50% of the answer the Agent search path. Looking back on the original “security complaint” I notice it is about the activeGates. They are trying to connect the “unreachable” interfaces on the cluster. For this I need to go for option 1, the ticket (-; KR Henik ---
**Author:** ![AntonioSousa](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/antoniosousa/32/50_2.png) [@AntonioSousa](https://community.dynatrace.com/u/AntonioSousa)\ **Post date:** [May 26, 2022, 9:27am UTC](https://community.dynatrace.com/t/dynatrace-managed-multiple-network-interfaces/35278/5 "2022-05-26T09:27:15Z")
[@henk\_stobbe](https://community.dynatrace.com/user/11427), The AGs will follow that CMC configuration too, so it should resolve for both OneAgents and ActiveGates. ---
**Author:** ![henk\_stobbe](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/henk_stobbe/32/30434_2.png) [@henk\_stobbe](https://community.dynatrace.com/u/henk_stobbe)\ **Post date:** [May 26, 2022, 9:38pm UTC](https://community.dynatrace.com/t/dynatrace-managed-multiple-network-interfaces/35278/6 "2022-05-26T21:38:38Z")
Hi Antonio, Just had to check (-; installed a oneAgent and found the error in the list the oneAgent gets from the cluster: ClusterAG ip:9999 ip:443 ClusterNode1 ip:8443 ClusterNode2 ip:8443 ClusterNode3 ip:8443 ClusterNode4 ip:8443 ClusterNode5 ip:8443 ClusterNode5 ip2:8443 ClusterNode5 ip3:8443 ClusterNode5 hostname:8443 ClusterNode5 hostname\_backup\_interface:8443 So there is a error on the cluster I assume Node5 → I will create a ticket for this General (I do not think this this is available) for security reasons e.g. preventing calls to unavailable destinations, it would be nice to have an option to turn off traffic to cluster-nodes or to the cluster activeGate completely. Normal behavior for an activeGate is to connect to : - Index 1—Embedded ActiveGates - Index 2—Cluster ActiveGates In this use case, the AG can only connect to the Cluster ActiveGate )-; KR Henk ---
**Author:** ![AntonioSousa](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/antoniosousa/32/50_2.png) [@AntonioSousa](https://community.dynatrace.com/u/AntonioSousa)\ **Post date:** [May 26, 2022, 9:44pm UTC](https://community.dynatrace.com/t/dynatrace-managed-multiple-network-interfaces/35278/7 "2022-05-26T21:44:04Z")
[@henk\_stobbe](https://community.dynatrace.com/user/11427), Looks like there are some dependencies that I was not aware of. Have you tried Network Zones to segment traffic? ---
**Author:** ![henk\_stobbe](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/henk_stobbe/32/30434_2.png) [@henk\_stobbe](https://community.dynatrace.com/u/henk_stobbe)\ **Post date:** [May 26, 2022, 9:58pm UTC](https://community.dynatrace.com/t/dynatrace-managed-multiple-network-interfaces/35278/8 "2022-05-26T21:58:54Z")
No not yet, I will propose it. (-; Just figured out that agents that are technically limited to connect to one Environment ActiveGate, still get the long node list, and will thy them all! So implementing network zones looks to me as a great idea! KR Henk ---
**Author:** ![henk\_stobbe](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/henk_stobbe/32/30434_2.png) [@henk\_stobbe](https://community.dynatrace.com/u/henk_stobbe)\ **Post date:** [May 26, 2022, 10:00pm UTC](https://community.dynatrace.com/t/dynatrace-managed-multiple-network-interfaces/35278/9 "2022-05-26T22:00:44Z")
Ticket raised for the cluster issue, thx!