01-08-2013 06:01 AM - edited 07-03-2021 11:18 PM
Hi,
I have a Cisco Wlan Controller 2504 with 1042N AP (3-nos) every thing was working fine from past 2 months. Now i am getting a issue with clients which are connected to the wireless AP, they are not able to get an dhcp IP address from the 2960 Switch (DHCP Server). The clients are getting IP address as 0.0.0.0.
This is My Configuration:
System Information
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 7.0.220.0
Bootloader Version............................... 1.0.16
Field Recovery Image Version..................... 1.0.0
Firmware Version................................. PIC 16.0
Build Type....................................... DATA + WPS
System Name...................................... WLAN
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1279
IP Address....................................... 192.168.0.7
Last Reset....................................... Power on reset
System Up Time................................... 0 days 2 hrs 23 mins 22 secs
System Timezone Location.........................
Current Boot License Level....................... base
Current Boot License Type........................ Permanent
Next Boot License Level.......................... base
Switch Configuration
802.3x Flow Control Mode......................... Disable
FIPS prerequisite features....................... Disabled
secret obfuscation............................... Enabled
Strong Password Check Features:
case-check ...........Enabled
consecutive-check ....Enabled
default-check .......Enabled
username-check ......Enabled
Press Enter to continue or <ctrl-z> to abort
Network Information
RF-Network Name............................. MEC
Web Mode.................................... Disable
Secure Web Mode............................. Enable
Secure Web Mode Cipher-Option High.......... Disable
Secure Web Mode Cipher-Option SSLv2......... Enable
OCSP........................................ Disabled
OCSP responder URL..........................
Secure Shell (ssh).......................... Enable
Telnet...................................... Disable
Ethernet Multicast Forwarding............... Disable
Ethernet Broadcast Forwarding............... Disable
AP Multicast/Broadcast Mode................. Multicast Address : 0.0.0.0
IGMP snooping............................... Disabled
IGMP timeout................................ 60 seconds
IGMP Query Interval......................... 20 seconds
User Idle Timeout........................... 300 seconds
ARP Idle Timeout............................ 300 seconds
Cisco AP Default Master..................... Disable
AP Join Priority............................ Disable
Mgmt Via Wireless Interface................. Disable
Mgmt Via Dynamic Interface.................. Disable
Please Help !!!
Solved! Go to Solution.
01-09-2013 08:18 AM
Well maybe the configuration was never saved and then it was rebooted without saving the changes?
Thanks,
Scott
Help out other by using the rating system and marking answered questions as "Answered"
01-09-2013 08:22 AM
So, the config on the WLC looks fine. You do not need to do the DHCP overide under the WLAN, just have the server configured in the interface.
But out of curiosity, can you look at the switch to see if someone has enabled teh dot1q native vlan tag command?
HTH,
Steve
------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered
01-09-2013 08:52 AM
Yes the switch Port (gig interface 1/0/2) to which the WLAN is connectd is dot1q. i.e., trunk port right....?
find this:
SW1#show interfaces trunk
Port Mode Encapsulation Status Native vlan
Gi1/0/2 on 802.1q trunking 1
Port Vlans allowed on trunk
Gi1/0/2 1-4094
Port Vlans allowed and active in management domain
Gi1/0/2 1-3
Port Vlans in spanning tree forwarding state and not pruned
Gi1/0/2 1-3
It is just a basic setup with a single vlan i.e., default vlan 1 and with router, WLAN and acces points.
01-09-2013 09:11 AM
pull a show run of the switch, there might be a command that is vlan dot1q tag native. it changes the behavior of the switch. If it somehow got enabled, turn it off.
HTH,
Steve
------------------------------------------------------------------------------------------------
Please remember to rate useful posts, and mark questions as answered
01-09-2013 05:30 PM
01-09-2013 08:36 PM
weather dhcp server over ride checked are not but still not able to get the dhcp ip..
as the client laptops wifi adapter says limited connectivity and gets ip address of 169.17.x.x some thing..
i.e., no dhcp ip address.
01-09-2013 08:51 PM
will this be the issue as i am using the thwo sets of passwords to get connected to the wifi. (Keysize=104bits, Key Index=1&2, Encryption key=*************, Key format= ASCII)
01-09-2013 09:12 PM
Hi,
Use only Key Index 1.
Try creating an new SSID or may be make this SSID itself for testing with open authetication (Security None) and verify if the DHCP works.
Regards
Najaf
01-09-2013 11:10 PM
Solved
Thank you Guys.
Changed the single set index key to access the wifi and got the dhcp working fine....
but recreated agin the same problem in order toconfirm it. as with two set of keys it dosent provide the dhcp itself where as with single set of index key it works fine..
Dont know why there is different set index keys option is it releated to some other things.
06-13-2018 02:54 AM
Hi Guys,
Same issue, i do facing now. But My ssid is PSK enabled. Please help me to fix this.
06-13-2018 04:21 AM
You should open a new thread and include information on your wlan setting and code you are running on your WLC and AP model. The more information the better.
06-13-2018 04:30 AM
06-13-2018 04:42 AM
02-23-2016 06:44 PM
Well i had this issue with cisco 2500 series wlan. the problem wasn't the wlan but at our core switch cisco 4503. in the specified vlan, there was a wrong ip helper:
switch(conf)#int vlanX(the vlan the ssid belongs to)
switch(conf-if)#ip helper-address x.x.x.x (this it the ip of the dhcp server)
switch(conf-if)#end
After doing this, the wlan got updates from the dhcp and users had IP and the connection was established.
Hope this helps too.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide