I ran into a strange problem moving a server from a PIX I was retiring to my ASA.

I currently have 4 untagged VLANs on a Dell 5324 Switch. The Cisco ASA is using 3 interfaces (Outside, DMZ, Inside). The Outside interface of the ASA is on a VLAN with the outside interface of my Pix 505 as well as my internet access from my ISP. The Inside interfaces for both the PIX and ASA are on their own VLANs. The DMZ is on its own VLAN.

I changed the IP address of the server from the inside PIX subnet to an address on my ASA DMZ subnet. I moved the cable from a port on the inside PIX subnet to the DMZ subnet. I removed the PIX from the environment. I cleared the arp cache from the 5324 and on the ASA.

When I plugged the server into the new switch port, all traffic on the VLAN stopped. I thought it was a loop/STP issue, ip conflict, or arp cache issue. I did not get any ip dupe errors on any device or the server. I changed it anways. Once I did this and plugged the server back into the DMZ VLAN traffic to/from server at this point worked. I then created the following NAT rule on the ASA:

static (DMZ,Outside) XX.XX.XX.61 10.112.216.61 netmask 255.255.255.255

As soon as I enter this command, I no longer can route to the internet and vice versa.

I go back and remove the command and place the NAT on a different server using the same address and it translates fine.

I attempted to configure an open interface on the ASA with just the server and still have issues when configuring NAT. I also attempted to swap NICs on the server but that didnt work.

I think it may be my ISP at this point and they need to clear their switch's arp cache.