<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Dynatrace managed multiple network interfaces in Dynatrace Managed Q&amp;A</title>
    <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187247#M1968</link>
    <description>&lt;P&gt;Kindly raise a support ticket if its for any organization.&lt;/P&gt;</description>
    <pubDate>Thu, 26 May 2022 04:25:09 GMT</pubDate>
    <dc:creator>techean</dc:creator>
    <dc:date>2022-05-26T04:25:09Z</dc:date>
    <item>
      <title>Dynatrace Managed multiple network interfaces</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187201#M1967</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;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..&lt;/P&gt;
&lt;P&gt;So all agents and activeGates use a list of addresses that can not be used, ever!&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This situation exist for a long time, does anybody have a suggestion how to remove those unused interface from Dynatrace config?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;KR Henk&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 16 Jun 2023 11:21:22 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187201#M1967</guid>
      <dc:creator>henk_stobbe</dc:creator>
      <dc:date>2023-06-16T11:21:22Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace managed multiple network interfaces</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187247#M1968</link>
      <description>&lt;P&gt;Kindly raise a support ticket if its for any organization.&lt;/P&gt;</description>
      <pubDate>Thu, 26 May 2022 04:25:09 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187247#M1968</guid>
      <dc:creator>techean</dc:creator>
      <dc:date>2022-05-26T04:25:09Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace managed multiple network interfaces</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187263#M1969</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/11427"&gt;@henk_stobbe&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;You can define what gets announced in CMC. For each node check out "Deployment status", then "Configure" on each node. At the bottom, check:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AntonioSousa_0-1653553717636.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/5855i599D965887946603/image-size/medium?v=v2&amp;amp;px=400" role="button" title="AntonioSousa_0-1653553717636.png" alt="AntonioSousa_0-1653553717636.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 May 2022 08:29:31 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187263#M1969</guid>
      <dc:creator>AntonioSousa</dc:creator>
      <dc:date>2022-05-26T08:29:31Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace managed multiple network interfaces</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187265#M1970</link>
      <description>&lt;P&gt;Hi Antonio,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;For this I need to go for option 1, the ticket (-;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;KR Henik&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 May 2022 09:12:14 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187265#M1970</guid>
      <dc:creator>henk_stobbe</dc:creator>
      <dc:date>2022-05-26T09:12:14Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace managed multiple network interfaces</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187267#M1971</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/11427"&gt;@henk_stobbe&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;The AGs will follow that CMC configuration too, so it should resolve for both OneAgents and ActiveGates.&lt;/P&gt;</description>
      <pubDate>Thu, 26 May 2022 09:27:15 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187267#M1971</guid>
      <dc:creator>AntonioSousa</dc:creator>
      <dc:date>2022-05-26T09:27:15Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace managed multiple network interfaces</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187286#M1972</link>
      <description>&lt;P&gt;Hi Antonio,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Just had to check (-; installed a oneAgent and found the error in the list the oneAgent gets from the cluster:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ClusterAG ip:9999&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; ip:443&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ClusterNode1 ip:8443&lt;/P&gt;&lt;P&gt;ClusterNode2 ip:8443&lt;/P&gt;&lt;P&gt;ClusterNode3 ip:8443&lt;/P&gt;&lt;P&gt;ClusterNode4 ip:8443&lt;/P&gt;&lt;P&gt;ClusterNode5 ip:8443&lt;/P&gt;&lt;P&gt;ClusterNode5 ip2:8443&lt;/P&gt;&lt;P&gt;ClusterNode5 ip3:8443&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ClusterNode5 hostname:8443&lt;/P&gt;&lt;P&gt;ClusterNode5 hostname_backup_interface:8443&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So there is a error on the cluster I assume Node5 -&amp;gt; I will create a ticket for this&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Normal behavior for an activeGate is to connect to :&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL class=""&gt;&lt;LI&gt;Index 1—Embedded ActiveGates&lt;/LI&gt;&lt;LI&gt;Index 2—Cluster ActiveGates&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;In this use case, the AG can only connect to the Cluster ActiveGate )-;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;KR Henk&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 May 2022 21:41:46 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187286#M1972</guid>
      <dc:creator>henk_stobbe</dc:creator>
      <dc:date>2022-05-26T21:41:46Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace managed multiple network interfaces</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187287#M1973</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/11427"&gt;@henk_stobbe&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Looks like there are some dependencies that I was not aware of. Have you tried Network Zones to segment traffic?&lt;/P&gt;</description>
      <pubDate>Thu, 26 May 2022 21:44:04 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187287#M1973</guid>
      <dc:creator>AntonioSousa</dc:creator>
      <dc:date>2022-05-26T21:44:04Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace managed multiple network interfaces</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187288#M1974</link>
      <description>&lt;P&gt;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!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;KR Henk&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 May 2022 21:59:31 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187288#M1974</guid>
      <dc:creator>henk_stobbe</dc:creator>
      <dc:date>2022-05-26T21:59:31Z</dc:date>
    </item>
    <item>
      <title>Re: Dynatrace managed multiple network interfaces</title>
      <link>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187289#M1975</link>
      <description>&lt;P&gt;Ticket raised for the cluster issue, thx!&lt;/P&gt;</description>
      <pubDate>Thu, 26 May 2022 22:00:44 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dynatrace-Managed-Q-A/Dynatrace-Managed-multiple-network-interfaces/m-p/187289#M1975</guid>
      <dc:creator>henk_stobbe</dc:creator>
      <dc:date>2022-05-26T22:00:44Z</dc:date>
    </item>
  </channel>
</rss>

