<?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 Duplicate IP address with ASA Interface Mac Address in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/duplicate-ip-address-with-asa-interface-mac-address/m-p/1775190#M494436</link>
    <description>&lt;P&gt;We have an ESX server will multiple virtual servers defined. I am trying to migrate the default gateway IP address (.1) from a 3900 router to an ASA firewall. When the default gateway is assigned to the 3900 there are no issues. Shortly after moving the default gateway to the ASA, the virtual server will report a duplicate IP address. The offending mac address is the interface of the ASA firewall. The network to be moved is a class C. There are only 4 hosts on the network. This leaves many other IP addresses to test with all of which have never been used. When the virtual server is configured for a new, never before used IP address, the server will report a duplicate IP address and the ASA mac address is listed for the duplicate mac. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have moved other networks from the 3900 to ASA without issue. To the best of my knowledge the only difference is how the ESX server attaches the virtual server/IP address to a NIC. The ESX server has five network interfaces: 1 ilo, 2 management and 2 production. The IP addresses and networks associated with ilo and mgmt are working without trouble. The virtual servers using the production interfaces are having trouble when the default gateway is the ASA firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The switch configuration for the ilo and management interface is defined as an access switchport. The production interfaces are each defined as a trunk and allows two networks on the trunk.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can’t help but think the issue is with the relationship between the switch trunks and the ESX server. The trunk interfaces operate independently. The have not been teamed together (LACP). Do the 3900 router and ASA handle arp differently thus expose a problem that’s been there all along?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA Firewall&lt;/P&gt;&lt;P&gt;ASA Version 8.2(5)13&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/2&lt;/P&gt;&lt;P&gt; description 4948 g1/22&lt;/P&gt;&lt;P&gt; no nameif&lt;/P&gt;&lt;P&gt; no security-level&lt;/P&gt;&lt;P&gt; no ip address&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/2.82&lt;/P&gt;&lt;P&gt; description esx production VM servers&lt;/P&gt;&lt;P&gt; shutdown&lt;/P&gt;&lt;P&gt; vlan 82&lt;/P&gt;&lt;P&gt; nameif esx_prod&lt;/P&gt;&lt;P&gt; security-level 70&lt;/P&gt;&lt;P&gt; ip address 192.168.82.1 255.255.255.0&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-list esx_prod_in extended permit ip any any&lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;/P&gt;&lt;P&gt;nat (esx_prod) 1 192.168.82.0 255.255.255.0&lt;/P&gt;&lt;P&gt;static (inside,esx_prod) 192.168.0.0 192.168.0.0 netmask 255.255.0.0&lt;/P&gt;&lt;P&gt;static (inside,esx_prod) 172.16.0.0 172.16.0.0 netmask 255.240.0.0&lt;/P&gt;&lt;P&gt;access-group esx_prod_in in interface esx_prod&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Switch&lt;/P&gt;&lt;P&gt;interface GigabitEthernet1/1&lt;/P&gt;&lt;P&gt; description ESX server production&lt;/P&gt;&lt;P&gt; switchport trunk encapsulation dot1q&lt;/P&gt;&lt;P&gt; switchport trunk allowed vlan 82,193&lt;/P&gt;&lt;P&gt; switchport mode trunk&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Router&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/0.82&lt;/P&gt;&lt;P&gt; description esx production VM servers&lt;/P&gt;&lt;P&gt; encapsulation dot1Q 82&lt;/P&gt;&lt;P&gt; ip address 192.168.82.1 255.255.255.0&lt;/P&gt;&lt;P&gt; ip pim sparse-dense-mode&lt;/P&gt;&lt;P&gt; ip cgmp&lt;/P&gt;&lt;P&gt;end&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 21:44:40 GMT</pubDate>
    <dc:creator>rmeans</dc:creator>
    <dc:date>2019-03-11T21:44:40Z</dc:date>
    <item>
      <title>Duplicate IP address with ASA Interface Mac Address</title>
      <link>https://community.cisco.com/t5/network-security/duplicate-ip-address-with-asa-interface-mac-address/m-p/1775190#M494436</link>
      <description>&lt;P&gt;We have an ESX server will multiple virtual servers defined. I am trying to migrate the default gateway IP address (.1) from a 3900 router to an ASA firewall. When the default gateway is assigned to the 3900 there are no issues. Shortly after moving the default gateway to the ASA, the virtual server will report a duplicate IP address. The offending mac address is the interface of the ASA firewall. The network to be moved is a class C. There are only 4 hosts on the network. This leaves many other IP addresses to test with all of which have never been used. When the virtual server is configured for a new, never before used IP address, the server will report a duplicate IP address and the ASA mac address is listed for the duplicate mac. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have moved other networks from the 3900 to ASA without issue. To the best of my knowledge the only difference is how the ESX server attaches the virtual server/IP address to a NIC. The ESX server has five network interfaces: 1 ilo, 2 management and 2 production. The IP addresses and networks associated with ilo and mgmt are working without trouble. The virtual servers using the production interfaces are having trouble when the default gateway is the ASA firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The switch configuration for the ilo and management interface is defined as an access switchport. The production interfaces are each defined as a trunk and allows two networks on the trunk.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can’t help but think the issue is with the relationship between the switch trunks and the ESX server. The trunk interfaces operate independently. The have not been teamed together (LACP). Do the 3900 router and ASA handle arp differently thus expose a problem that’s been there all along?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA Firewall&lt;/P&gt;&lt;P&gt;ASA Version 8.2(5)13&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/2&lt;/P&gt;&lt;P&gt; description 4948 g1/22&lt;/P&gt;&lt;P&gt; no nameif&lt;/P&gt;&lt;P&gt; no security-level&lt;/P&gt;&lt;P&gt; no ip address&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/2.82&lt;/P&gt;&lt;P&gt; description esx production VM servers&lt;/P&gt;&lt;P&gt; shutdown&lt;/P&gt;&lt;P&gt; vlan 82&lt;/P&gt;&lt;P&gt; nameif esx_prod&lt;/P&gt;&lt;P&gt; security-level 70&lt;/P&gt;&lt;P&gt; ip address 192.168.82.1 255.255.255.0&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-list esx_prod_in extended permit ip any any&lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;/P&gt;&lt;P&gt;nat (esx_prod) 1 192.168.82.0 255.255.255.0&lt;/P&gt;&lt;P&gt;static (inside,esx_prod) 192.168.0.0 192.168.0.0 netmask 255.255.0.0&lt;/P&gt;&lt;P&gt;static (inside,esx_prod) 172.16.0.0 172.16.0.0 netmask 255.240.0.0&lt;/P&gt;&lt;P&gt;access-group esx_prod_in in interface esx_prod&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Switch&lt;/P&gt;&lt;P&gt;interface GigabitEthernet1/1&lt;/P&gt;&lt;P&gt; description ESX server production&lt;/P&gt;&lt;P&gt; switchport trunk encapsulation dot1q&lt;/P&gt;&lt;P&gt; switchport trunk allowed vlan 82,193&lt;/P&gt;&lt;P&gt; switchport mode trunk&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Router&lt;/P&gt;&lt;P&gt;interface GigabitEthernet0/0.82&lt;/P&gt;&lt;P&gt; description esx production VM servers&lt;/P&gt;&lt;P&gt; encapsulation dot1Q 82&lt;/P&gt;&lt;P&gt; ip address 192.168.82.1 255.255.255.0&lt;/P&gt;&lt;P&gt; ip pim sparse-dense-mode&lt;/P&gt;&lt;P&gt; ip cgmp&lt;/P&gt;&lt;P&gt;end&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 21:44:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/duplicate-ip-address-with-asa-interface-mac-address/m-p/1775190#M494436</guid>
      <dc:creator>rmeans</dc:creator>
      <dc:date>2019-03-11T21:44:40Z</dc:date>
    </item>
    <item>
      <title>Duplicate IP address with ASA Interface Mac Address</title>
      <link>https://community.cisco.com/t5/network-security/duplicate-ip-address-with-asa-interface-mac-address/m-p/1775191#M494437</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am continuing to research.&amp;nbsp; I suspect proxy arp may be the issue.&amp;nbsp; I plan to disable and test shortly.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Oct 2011 19:47:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/duplicate-ip-address-with-asa-interface-mac-address/m-p/1775191#M494437</guid>
      <dc:creator>rmeans</dc:creator>
      <dc:date>2011-10-31T19:47:55Z</dc:date>
    </item>
    <item>
      <title>Duplicate IP address with ASA Interface Mac Address</title>
      <link>https://community.cisco.com/t5/network-security/duplicate-ip-address-with-asa-interface-mac-address/m-p/1775192#M494440</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yup, you got it. The issue is proxy arp. The only way that the ASA is going to answer an ARP request is if there proxyarp feature is enable. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, it is enable by default, and what causes the ASA to answer the solicited ARP requests is NAT configuration. On which interface of the firewall is the Server located? What is the subnet that the ASA is responding to? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Oct 2011 22:15:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/duplicate-ip-address-with-asa-interface-mac-address/m-p/1775192#M494440</guid>
      <dc:creator>Maykol Rojas</dc:creator>
      <dc:date>2011-10-31T22:15:44Z</dc:date>
    </item>
    <item>
      <title>Re: Duplicate IP address with ASA Interface Mac Address</title>
      <link>https://community.cisco.com/t5/network-security/duplicate-ip-address-with-asa-interface-mac-address/m-p/1775193#M494443</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Disabling proxy arp worked (sysopt noproxyarp &lt;INTERFACE&gt;).&lt;/INTERFACE&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 01 Nov 2011 10:51:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/duplicate-ip-address-with-asa-interface-mac-address/m-p/1775193#M494443</guid>
      <dc:creator>rmeans</dc:creator>
      <dc:date>2011-11-01T10:51:29Z</dc:date>
    </item>
  </channel>
</rss>

