<?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: Rogue DHCP Server in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/rogue-dhcp-server/m-p/23617#M2361</link>
    <description>You can also create an alarm in Netsight:&lt;BR /&gt;
&lt;BR /&gt;
Add this section in trapd.conf and create the alarm.&lt;BR /&gt;
&lt;BR /&gt;
EVENT extremeIpSecurityViolation .1.3.6.1.4.1.1916.1.34.1.0.1 "Status Alarms" Critical&lt;BR /&gt;
&lt;BR /&gt;
 FORMAT Rogue DHCP server on vlan $2&lt;BR /&gt;
&lt;BR /&gt;
 SDESC&lt;BR /&gt;
&lt;BR /&gt;
 "IP Security Violation"&lt;BR /&gt;
&lt;BR /&gt;
 EDESC&lt;BR /&gt;
&lt;BR /&gt;</description>
    <pubDate>Wed, 18 Mar 2015 15:44:00 GMT</pubDate>
    <dc:creator>JohanHendrikx</dc:creator>
    <dc:date>2015-03-18T15:44:00Z</dc:date>
    <item>
      <title>Rogue DHCP Server</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/rogue-dhcp-server/m-p/23613#M2357</link>
      <description>Create Date: Mar 26 2012  9:36AM&lt;BR /&gt;
&lt;BR /&gt;
 What is the best way to track down a rogue DHCP server in an Extreme switch environment.  I've done it many times in a Cisco environment, but assigning a secondary IP to a router interface, pinging the bad default gateway, and then digging through the mac-address tables on each switch to find the connected port.  The problem I'm having is that I can't successfully ping the gateway address from a host that recieved the bad IP assigment.  As a result I cannot find the server.  I believe that the server may be built into some automation software that one team runs, but I'm having a hard time verifying that.  &lt;BR /&gt;
&lt;BR /&gt;
 Also, what is the syntax to enable DHCP snooping on an extreme switch?&lt;BR /&gt;
&lt;BR /&gt;
 -NB&lt;BR /&gt;
&lt;BR /&gt;
  (from N_B)</description>
      <pubDate>Wed, 08 Jan 2014 05:52:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/rogue-dhcp-server/m-p/23613#M2357</guid>
      <dc:creator>EtherNation_Use</dc:creator>
      <dc:date>2014-01-08T05:52:00Z</dc:date>
    </item>
    <item>
      <title>RE: Rogue DHCP Server</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/rogue-dhcp-server/m-p/23614#M2358</link>
      <description>Create Date: Mar 26 2012 11:16AM&lt;BR /&gt;
&lt;BR /&gt;
 By default DHCP snooping is disabled on the switch. To enable DHCP snooping on the switch, use the&lt;BR /&gt;
&lt;BR /&gt;
 following command: enable ip-security dhcp-snooping {vlan} &lt;VLAN_NAME&gt; ports [all | ] violationaction[drop-packet {[block-mac | block-port] [duration &lt;DURATION_IN_SECONDS&gt; |permanently] | none]}] {snmp-trap}  (from Arpit_Bhatt)&lt;/DURATION_IN_SECONDS&gt;&lt;/VLAN_NAME&gt;</description>
      <pubDate>Wed, 08 Jan 2014 05:52:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/rogue-dhcp-server/m-p/23614#M2358</guid>
      <dc:creator>EtherNation_Use</dc:creator>
      <dc:date>2014-01-08T05:52:00Z</dc:date>
    </item>
    <item>
      <title>RE: Rogue DHCP Server</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/rogue-dhcp-server/m-p/23615#M2359</link>
      <description>Create Date: Mar 26 2012 11:19AM&lt;BR /&gt;
&lt;BR /&gt;
 Configure a Trusted DHCP server and the switch will only forward packets from the Trusted server. Go through "DHCP Snooping and Trusted DHCP Server" in the concepts guide and that should help you.&lt;BR /&gt;
&lt;BR /&gt;
  &lt;BR /&gt;
&lt;BR /&gt;
 Let me know if that works for you.&lt;BR /&gt;
&lt;BR /&gt;
  (from Arpit_Bhatt)</description>
      <pubDate>Wed, 08 Jan 2014 05:52:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/rogue-dhcp-server/m-p/23615#M2359</guid>
      <dc:creator>EtherNation_Use</dc:creator>
      <dc:date>2014-01-08T05:52:00Z</dc:date>
    </item>
    <item>
      <title>RE: Rogue DHCP Server</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/rogue-dhcp-server/m-p/23616#M2360</link>
      <description>Create Date: Mar 26 2012 11:25AM&lt;BR /&gt;
&lt;BR /&gt;
Once DHCP snooping and trusted server are enabled you can use the command show ip-security dhcp-snooping violations to see where the rogue DHCP packet was received.&lt;BR /&gt;
&lt;BR /&gt;
  (from Paul_Russo)</description>
      <pubDate>Wed, 08 Jan 2014 05:52:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/rogue-dhcp-server/m-p/23616#M2360</guid>
      <dc:creator>EtherNation_Use</dc:creator>
      <dc:date>2014-01-08T05:52:00Z</dc:date>
    </item>
    <item>
      <title>RE: Rogue DHCP Server</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/rogue-dhcp-server/m-p/23617#M2361</link>
      <description>You can also create an alarm in Netsight:&lt;BR /&gt;
&lt;BR /&gt;
Add this section in trapd.conf and create the alarm.&lt;BR /&gt;
&lt;BR /&gt;
EVENT extremeIpSecurityViolation .1.3.6.1.4.1.1916.1.34.1.0.1 "Status Alarms" Critical&lt;BR /&gt;
&lt;BR /&gt;
 FORMAT Rogue DHCP server on vlan $2&lt;BR /&gt;
&lt;BR /&gt;
 SDESC&lt;BR /&gt;
&lt;BR /&gt;
 "IP Security Violation"&lt;BR /&gt;
&lt;BR /&gt;
 EDESC&lt;BR /&gt;
&lt;BR /&gt;</description>
      <pubDate>Wed, 18 Mar 2015 15:44:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/rogue-dhcp-server/m-p/23617#M2361</guid>
      <dc:creator>JohanHendrikx</dc:creator>
      <dc:date>2015-03-18T15:44:00Z</dc:date>
    </item>
  </channel>
</rss>

