12-21-2012 01:03 PM
I recently placed two AP105 Accespoints at a customer site.
But I now have the strange behaviour when both accespoints are powered up some of the laptops tell that there is an IP conflict with an other device in the network.
I have done some tests in the network enviroment with a fluke network tester, and can not see any strange behaviour.
When both AP's are on I see that a couple of IP addresses showing up in the fluke tester with double MAC addresses.
One MAC address is the original MAC address of the laptop and the other MAC address is a phantom address starting with 02:....
Our LAN subnet is 192.168.10.x/24
We are using firmware Version: 126.96.36.199-188.8.131.52_35899
I have tested for over a week now with one accesspoint enabled and everything is working fine. When I connected the second AP to cover the ground floor I got IP conflict messages again.
Does anyone has the same problem?
12-21-2012 02:24 PM
Are the TWO ip addresses in the same subnet?
What is the DHCP server?
Is there more than one DHCP server?
Can you see what is assigning those addresses?
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
Validated Reference Design Guides : http://community.arubanetworks.com/t5/Validated-Reference-Design/tkb-p/Aruba-VRDs
12-26-2012 11:18 PM
I am using a Windows 2003 server as DHCP server, this is also my Domain controller and exchange server.
The dupicate addresses are in the same subnet. For the LAN subnet we use 192.168.10.0/24, where the DHCP server is 192.168.10.10. On the laptop it seems that the address is assigned by the correct DHCP server.
I did some research on the network when I was on location but I was unable to find the devices with the MAC addresses starting with 02:F0:AF., so I could not check the addresses on these devices.
On the search I checked all running computers and did not find any virtual machines which could cause this kind of behaviour.
The MAC address are gone on the fluke network tester when I disconnect 1 of the accesspoints.
I discoverd that the aruba accesspoints had also a DHCP config using the 192.168.10.0 subnet. I changed this to another subnet, but according to me this could not cause the problems becuase DHCP is turned off in the Aruba accesspoints.