12-13-2011 04:35 AM - edited 07-03-2021 09:13 PM
Hi
We’ve recently installed a 5508 wlan controller for my organization wireless network and each time devices connect to this wireless network they receive an ip conflict error.
All devices conflict with the ip address of IP address 0.0.0.0 with mac address 00-00-00-00-00-00.
All devices event viewer has this TCP error: “The system detected an address conflict for IP address 0.0.0.0 with the system having network hardware address 00-00-00-00-00-00. Network operations on this system may be disrupted as a result.”
We previously experienced the same ip conflict with 12000 wlan network that he had used as proof of concept.
12-13-2011 04:40 AM
Can you share a little bit about your deisgn and code rev. That is unusally. Ive installed more WCLs then I care to count and I havent seen that issue before.
12-13-2011 05:13 AM
We have 3 internal networks 10.2.0.0, 10.2.1.0 and 10.2.3.0 with subnet 255.255.252.0 which leasing is managed by a 2008 DHCP server. ip 10.2.3.115 to 10.2.3.202 has been reserved for wireless network.
WLAN management ip is 10.2.3.111, virtual ip 1.1.1.1, internal DHCP enabled. Dhcp ip 10.2.3.111
7 Access point assigned static ip addresses from 10.2.3.115 to 121 and the rest is leased for wireless clients
Software version: 6.0.199.4
12-13-2011 05:15 AM
if your subnet really 255.255.252.0 or 255.255.255.0 ?
12-13-2011 05:18 AM
it's 255.255.252.0
12-13-2011 05:26 AM
And you mentioned your networks are below, correct ?
10.2.0.0
10.2.1.0
10.2.3.0
If this is correct your networks are off if you are using /22. Your first network assumes all 3 networks. See below
10.2.0.0 - 10.2.3.255
12-13-2011 05:35 AM
Yes our network is odd, perhaps this is the course of these errors.
However we do have another similar setup at another branch and they have never experienced these errors. The only difference at that branch is that the DHCP is hosted at a router level.
12-13-2011 05:39 AM
Yeah, I know what you mean it works here but why not there.
I would have to say, it would be best to correct the network situation first. Thats asking for problems when you cross networks like that. In fact, I dont think the WLC will allow you to add those interfaces, I think it should flag it stating its being used already.
Can you post your WLC config i would like to take a peek?
12-13-2011 06:32 AM
This is the config. i did not include my passwords for security reasons.
Please notify me if you find anything wrong.
config advanced 802.11b channel add 1
config advanced 802.11b channel add 6
config advanced 802.11b channel add 11
config advanced 802.11a channel add 36
config advanced 802.11a channel add 40
config advanced 802.11a channel add 44
config advanced 802.11a channel add 48
config advanced 802.11a channel add 52
config advanced 802.11a channel add 56
config advanced 802.11a channel add 60
config advanced 802.11a channel add 64
config certificate generate webauth
config interface address management 10.2.3.111 255.255.255.0 10.2.3.254
config interface vlan management 10
config interface dhcp management primary 10.2.0.110
config interface address service-port 10.10.10.1 255.255.255.0
config interface dhcp service-port disable
config interface address virtual 2.2.2.2
config 802.11b 11gsupport enable
config logging traceinfo disable debugging
config license boot auto
config mobility group domain ????????
config dhcp domain ????????_APs ????????
config dhcp lease ????????_APs 86400
config dhcp dns-servers ????????_APs 10.2.0.110
config dhcp address-pool ????????_APs 10.2.3.200 10.2.3.206
config dhcp network ????????_APs 10.2.3.0 255.255.255.0
config dhcp create-scope ????????_APs
config dhcp default-router ????????_APs 10.2.3.254
config dhcp enable ????????_APs
config spanningtree port mode off 1
config spanningtree port mode off 2
config spanningtree port mode off 3
config spanningtree port mode off 4
config spanningtree port mode off 5
config spanningtree port mode off 6
config spanningtree port mode off 7
config spanningtree port mode off 8
config lag enable
config database size 2048
config cdp advertise-v2 enable
config snmp community create
config snmp community create
config snmp community accessmode ro
config snmp community ipaddr 10.64.68.0 255.255.255.0 ITALA-MON
config snmp community mode enable ????????-MON
config snmp community create ????????-MON
config network rf-network-name ????????
config network broadcast enable
config network master-base enable
config network mgmt-via-wireless enable
config country ????????
config mgmtuser add encrypt ????????read-write
config mgmtuser add encrypt ????????read-write
config wlan session-timeout 1 1800
config wlan security wpa akm psk set-key hex encrypt 1 ????????1
config wlan security wpa akm psk enable 1
config wlan security wpa akm 802.1x disable 1
config wlan security wpa enable 1
config wlan exclusionlist 1 60
config wlan wmm allow 1
config wlan radius_server acct disable 1
config wlan radius_server auth disable 1
config wlan interface 1 management
config wlan create 1 ????????
config wlan broadcast-ssid enable 1
config wlan channel-scan defer-priority 5 enable 1
config wlan channel-scan defer-priority 6 enable 1
config wlan mfp client enable 1
config wlan enable 1
config sysname ????????_WLC
12-14-2011 08:58 PM
Try and do a show run-config
12-14-2011 10:27 PM
This conflict problem seems to be solved, i have disable the WLAN service port and since then i have not recieced any conflicts.
12-14-2011 10:32 PM
That will do it... You should also not leave the service port at 0.0.0.0 change it to an address that is not routable since this is out if band management.
Sent from Cisco Technical Support iPhone App
12-14-2011 10:35 PM
thanks will do
01-16-2012 02:34 AM
The problem is still on going. I configured this clients WLC's. Both for them. The one works with no problems the other as u can see is giving Wireless clients an ip conflict 0.0.0.0/0 MAC 00-00-00-00-00 <-- This how ever looks like an ARP issue. Also the SP is not even used right now (not connected). and if set to 0.0.0.0 is the default to obtain and DHCP ip address for your out of band managment port.
I do not believe this is a Controller or a DHCP problem. I will tweak the access layer arp counters to see if it helps and also try and get a go ahead with enabling DHCP snooping on the network.
But please if anyone has any ideas please share :<
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: