<?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 dhcprelay in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/dhcprelay/m-p/2692027#M191548</link>
    <description>&lt;P&gt;Trying to set DHCPRelay so DHCP requests from the inside interface of the ASA are routed to a DHCP server in another site. Get an error message when issuing the configuration command "dhcprelay enable inside" that states the inside interface is already set as a DHCP Client.&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I issue the command "sh dhcprelay state", I get this;&lt;/P&gt;&lt;P&gt;Context &amp;nbsp;Not Configured for DHCP&lt;BR /&gt;Interface inside, Configured for DHCP CLIENT&lt;BR /&gt;Interface OutSide, Configured for DHCP RELAY&lt;/P&gt;&lt;P&gt;If I run that command on an ASA that's configured correctly, I get this;&lt;/P&gt;&lt;P&gt;Context &amp;nbsp;Configured as DHCP Relay&lt;BR /&gt;Interface inside, Configured for DHCP RELAY SERVER&lt;BR /&gt;Interface OutSide, Configured for DHCP RELAY&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I had six firewalls behaving this way, and after reloading them, I was able to issue the "dhcprelay enable inside" successfully on four of them, but two still would not accept that change.&lt;/P&gt;&lt;P&gt;How do I change the inside interface from DHCP CLIENT to DHCP RELAY SERVER?&lt;/P&gt;&lt;P&gt;How do I set the context to DHCP Relay?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 05:56:27 GMT</pubDate>
    <dc:creator>momeara</dc:creator>
    <dc:date>2019-03-12T05:56:27Z</dc:date>
    <item>
      <title>dhcprelay</title>
      <link>https://community.cisco.com/t5/network-security/dhcprelay/m-p/2692027#M191548</link>
      <description>&lt;P&gt;Trying to set DHCPRelay so DHCP requests from the inside interface of the ASA are routed to a DHCP server in another site. Get an error message when issuing the configuration command "dhcprelay enable inside" that states the inside interface is already set as a DHCP Client.&amp;nbsp;&lt;/P&gt;&lt;P&gt;If I issue the command "sh dhcprelay state", I get this;&lt;/P&gt;&lt;P&gt;Context &amp;nbsp;Not Configured for DHCP&lt;BR /&gt;Interface inside, Configured for DHCP CLIENT&lt;BR /&gt;Interface OutSide, Configured for DHCP RELAY&lt;/P&gt;&lt;P&gt;If I run that command on an ASA that's configured correctly, I get this;&lt;/P&gt;&lt;P&gt;Context &amp;nbsp;Configured as DHCP Relay&lt;BR /&gt;Interface inside, Configured for DHCP RELAY SERVER&lt;BR /&gt;Interface OutSide, Configured for DHCP RELAY&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I had six firewalls behaving this way, and after reloading them, I was able to issue the "dhcprelay enable inside" successfully on four of them, but two still would not accept that change.&lt;/P&gt;&lt;P&gt;How do I change the inside interface from DHCP CLIENT to DHCP RELAY SERVER?&lt;/P&gt;&lt;P&gt;How do I set the context to DHCP Relay?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 05:56:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/dhcprelay/m-p/2692027#M191548</guid>
      <dc:creator>momeara</dc:creator>
      <dc:date>2019-03-12T05:56:27Z</dc:date>
    </item>
  </channel>
</rss>

