<?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: VIP for SNMP Trap in Extensions</title>
    <link>https://community.dynatrace.com/t5/Extensions/VIP-for-SNMP-Trap/m-p/239529#M4193</link>
    <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/52253"&gt;@gchastne&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Not sure what your idea is, but some notes from my side:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;If you have a VIP and the SNMP "load balancer" is able to send it to one of the AGs behind it, there should be no issue&lt;/LI&gt;&lt;LI&gt;If you send it to more than one AG , you will get repeated traps/logs in Dynatrace&lt;/LI&gt;&lt;LI&gt;SNMP traps are UDP based, so there is no good way for a "load balancer" to detect if traps are being received or not&lt;/LI&gt;&lt;LI&gt;There was an issue sometime ago where IPs with no reverse lookup would block some SNMP traps being received. Not sure if it has been resolved. Please make sure they are resolvable; in my case I had to put them in local AG host files...&lt;/LI&gt;&lt;LI&gt;A VIP for SNMP might be an interesting idea if you are forwarding traps to more than one platform, and don't want to change configurations on emitting devices...&lt;/LI&gt;&lt;/UL&gt;</description>
    <pubDate>Mon, 11 Mar 2024 19:43:49 GMT</pubDate>
    <dc:creator>AntonioSousa</dc:creator>
    <dc:date>2024-03-11T19:43:49Z</dc:date>
    <item>
      <title>VIP for SNMP Trap</title>
      <link>https://community.dynatrace.com/t5/Extensions/VIP-for-SNMP-Trap/m-p/239526#M4192</link>
      <description>&lt;P&gt;Has anyone successfully configured a VIP in front of a pair of ActiveGate for resilient SNMP Trap ingestion?&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2024 08:22:21 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Extensions/VIP-for-SNMP-Trap/m-p/239526#M4192</guid>
      <dc:creator>gchastne</dc:creator>
      <dc:date>2024-03-12T08:22:21Z</dc:date>
    </item>
    <item>
      <title>Re: VIP for SNMP Trap</title>
      <link>https://community.dynatrace.com/t5/Extensions/VIP-for-SNMP-Trap/m-p/239529#M4193</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/52253"&gt;@gchastne&lt;/a&gt;,&lt;/P&gt;&lt;P&gt;Not sure what your idea is, but some notes from my side:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;If you have a VIP and the SNMP "load balancer" is able to send it to one of the AGs behind it, there should be no issue&lt;/LI&gt;&lt;LI&gt;If you send it to more than one AG , you will get repeated traps/logs in Dynatrace&lt;/LI&gt;&lt;LI&gt;SNMP traps are UDP based, so there is no good way for a "load balancer" to detect if traps are being received or not&lt;/LI&gt;&lt;LI&gt;There was an issue sometime ago where IPs with no reverse lookup would block some SNMP traps being received. Not sure if it has been resolved. Please make sure they are resolvable; in my case I had to put them in local AG host files...&lt;/LI&gt;&lt;LI&gt;A VIP for SNMP might be an interesting idea if you are forwarding traps to more than one platform, and don't want to change configurations on emitting devices...&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Mon, 11 Mar 2024 19:43:49 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Extensions/VIP-for-SNMP-Trap/m-p/239529#M4193</guid>
      <dc:creator>AntonioSousa</dc:creator>
      <dc:date>2024-03-11T19:43:49Z</dc:date>
    </item>
    <item>
      <title>Re: VIP for SNMP Trap</title>
      <link>https://community.dynatrace.com/t5/Extensions/VIP-for-SNMP-Trap/m-p/243298#M4332</link>
      <description>&lt;P&gt;Graham,&lt;/P&gt;&lt;P&gt;I think this is possible using a NGINX in reverse proxy mode:&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.nginx.com/nginx/admin-guide/load-balancer/tcp-udp-load-balancer/" target="_blank"&gt;TCP and UDP Load Balancing | NGINX Documentation&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Fri, 19 Apr 2024 09:46:12 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Extensions/VIP-for-SNMP-Trap/m-p/243298#M4332</guid>
      <dc:creator>gautier_begin</dc:creator>
      <dc:date>2024-04-19T09:46:12Z</dc:date>
    </item>
    <item>
      <title>Re: VIP for SNMP Trap</title>
      <link>https://community.dynatrace.com/t5/Extensions/VIP-for-SNMP-Trap/m-p/259694#M5386</link>
      <description>&lt;P&gt;Our network team was against adding a load balancer for that, so we implemented a VIP.&lt;BR /&gt;The&amp;nbsp;VIP (virtual IP) switches over the pair of AGs (Active Gate) using the keepalived redhat service&amp;nbsp;where our "SNMP Traps" extension is running to ingest these traps.&lt;BR /&gt;N.B. as a side effect, the AG has a new address assigned to it, and it took the name of that new VIP.&lt;/P&gt;</description>
      <pubDate>Fri, 18 Oct 2024 11:31:43 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Extensions/VIP-for-SNMP-Trap/m-p/259694#M5386</guid>
      <dc:creator>LaurentBignens</dc:creator>
      <dc:date>2024-10-18T11:31:43Z</dc:date>
    </item>
  </channel>
</rss>

