<?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 IP address conflict detection on Extreme Layer 2 switches in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ip-address-conflict-detection-on-extreme-layer-2-switches/m-p/28162#M4280</link>
    <description>Is there any logging feature on Extreme devices (switches or routers) that can detect IP address conflicts (in this case, on windows machines)?</description>
    <pubDate>Thu, 12 Jun 2014 21:04:00 GMT</pubDate>
    <dc:creator>Jimmy2</dc:creator>
    <dc:date>2014-06-12T21:04:00Z</dc:date>
    <item>
      <title>IP address conflict detection on Extreme Layer 2 switches</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ip-address-conflict-detection-on-extreme-layer-2-switches/m-p/28162#M4280</link>
      <description>Is there any logging feature on Extreme devices (switches or routers) that can detect IP address conflicts (in this case, on windows machines)?</description>
      <pubDate>Thu, 12 Jun 2014 21:04:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ip-address-conflict-detection-on-extreme-layer-2-switches/m-p/28162#M4280</guid>
      <dc:creator>Jimmy2</dc:creator>
      <dc:date>2014-06-12T21:04:00Z</dc:date>
    </item>
    <item>
      <title>RE: IP address conflict detection on Extreme Layer 2 switches</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ip-address-conflict-detection-on-extreme-layer-2-switches/m-p/28163#M4281</link>
      <description>Hey Jimmy&lt;BR /&gt;
&lt;BR /&gt;
The switch will detect a duplicate IP address by default and warn you if a station is set to the same IP  Address of a VLAN.  Using DHCP snooping helps this as it does not allow any static IP addresses on the network.&lt;BR /&gt;
&lt;BR /&gt;
Also look at Duplicate Address Detection (DAD) in the concepts guide.  It is on page 1255 of the 15.4 guide.&lt;BR /&gt;
&lt;BR /&gt;
Hope that helps&lt;BR /&gt;
P&lt;BR /&gt;</description>
      <pubDate>Thu, 12 Jun 2014 23:04:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ip-address-conflict-detection-on-extreme-layer-2-switches/m-p/28163#M4281</guid>
      <dc:creator>Paul_Russo</dc:creator>
      <dc:date>2014-06-12T23:04:00Z</dc:date>
    </item>
    <item>
      <title>RE: IP address conflict detection on Extreme Layer 2 switches</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ip-address-conflict-detection-on-extreme-layer-2-switches/m-p/28164#M4282</link>
      <description>IP DAD is a good feature.&lt;BR /&gt;
&lt;BR /&gt;
We can also use UPM script to avoid duplicate ip in network.&lt;BR /&gt;
It is quite common scenario to have protection for VRRP gateway to avoid network outage.&lt;BR /&gt;
&lt;BR /&gt;
These commands are to be applied on edge switch .Core switch has VRRP.&lt;BR /&gt;
&lt;BR /&gt;
configure log filter DupIP add events FDB.arpViolation create log target upm Disable_DupIP_Port&lt;BR /&gt;
enable log target upm Disable_DupIP_Port&lt;BR /&gt;
configure log target upm Disable_DupIP_Port filter DupIP severity Warning&lt;BR /&gt;
&lt;BR /&gt;
enable ip-security arp gratuitous-protection vlan &lt;NAME&gt;&lt;BR /&gt;
enable ip-security arp gratuitous-protection vlan &lt;NAME&gt;&lt;BR /&gt;
&lt;BR /&gt;
UPM script&lt;BR /&gt;
&lt;BR /&gt;
create upm profile Disable_DupIP_Port&lt;BR /&gt;
set var up1 47&lt;BR /&gt;
set var up2 48&lt;BR /&gt;
## please specify the uplink ports as up1,up2..&lt;BR /&gt;
if ($match($EVENT.LOG_PARAM_3,$up1) &amp;amp;&amp;amp; $match($EVENT.LOG_PARAM_3,$up2)) then&lt;BR /&gt;
disable port $EVENT.LOG_PARAM_3&lt;BR /&gt;
create log entry "PORT $(EVENT.LOG_PARAM_3) WAS DISABLED DUE TO VRRP VIP CLASH"&lt;BR /&gt;
endif&lt;BR /&gt;&lt;/NAME&gt;&lt;/NAME&gt;</description>
      <pubDate>Fri, 13 Jun 2014 09:11:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ip-address-conflict-detection-on-extreme-layer-2-switches/m-p/28164#M4282</guid>
      <dc:creator>PARTHIBAN_CHINN</dc:creator>
      <dc:date>2014-06-13T09:11:00Z</dc:date>
    </item>
    <item>
      <title>RE: IP address conflict detection on Extreme Layer 2 switches</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ip-address-conflict-detection-on-extreme-layer-2-switches/m-p/28165#M4283</link>
      <description>To fix ip address conflict, contact your ISP . After that, you can check your ip by using  &lt;A href="http://www.ip-details.com/" target="_blank" rel="nofollow noreferrer noopener"&gt; Ip-details.com &lt;/A&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 09 Jan 2015 16:25:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/ip-address-conflict-detection-on-extreme-layer-2-switches/m-p/28165#M4283</guid>
      <dc:creator>sandwood</dc:creator>
      <dc:date>2015-01-09T16:25:00Z</dc:date>
    </item>
  </channel>
</rss>

