WCS -- WLC "Device un reachable"

Added WLC to WCS. Rebooted WLC from WLC and WCS cant reach WLC eventhough I can ping and access WLC. Verified SNMP and looks fine. Happened on two WLC's. I am waiting for almost 2 hours for WCS to talk WLC...

Please update the following informations
'show run-config' from the WLC and 'show run' from Switch connected to WLC while specifying the ports of Switch that connect to WLC in 2 separate text files.
=> Show msglog after the problem happens.
=> Check if there is crashes file available (WLC GUI ->Management ->Controller Crash)
=> 'show port summary' from the WLC when such problem happens.
=> 'show ip int br' from Switch connected to the WLC when such problem happens.
=> 'show arp switch' form WLC when such problem happens.
=> 'show arp' from Switch when such problem happens
The following URL will help you:
http://www.cisco.com/warp/public/707/cisco-amb-20070412-wlc.shtml

Similar Messages

Photosmart C4385 "Device Not Reachable"

I know this has been addressed in other threads, but none of the solutions have worked for me and my configuration is a little different. So here goes:
I'm running OS 10.6 Snow Leopard with my C4385. My computer is connected to a wireless network via an extender. I don't know anything about the router other than it's probably a Cisco since that's in the network name. The router and extender are both in my landlord's house, so I don't have access to them to reboot, check settings, or anything. Until this morning my printer was associated with the main network, which worked fine, but the signal is very weak and I would rather have it associated with the extender network. I went through the HP Setup Assistant and now all I get is the "Device Not Reachable" error message, whether I use the extender or main network.
I printed a Network Configuration Page and typed the printer's IP into my browser, and it shows up just fine, saying it's connected to the main network. Print & Fax under System Preferences disagrees and I can't print at all anymore (except with the USB cable). The only thing I changed recently is switching to a manual IP address for my laptop since I had lots of connectivity issues with automatic IPs, but after that everything worked until this morning when I ran Setup Assistant.
Sorry for writing a novel. I wish I had more information about the hardware but my landlord's not very helpful with these sorts of things. Any advice would be great! I've tried scrubbing software and reinstalling it and resetting the printing system, with no luck.

I see a couple of potential problems, here.
First, adding the printer by IP is dicey. If the router changes the printer's IP (actually WHEN it does, because eventually it will), then your Mac may lose track of it. Plus, adding by IP usually only enables printing, not scanning.
Second, HP printers don't seem to play well with wifi extenders. Is there a way to move your printer so that it is connected to the main router, not the extender?
Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
I am employed by HP

Configuring Device - Device not reachable

My new Envy 4500 _IS_ on my network.
My new MacBook Pro _IS_ on my network.
I get to the configuration step and all looks good until I get the response below:
"Configuring Device
0 Select Device
0 Confirm Wreless Settings
O Select Network
Configuring Device
Configuration Results
Device Not Reachable
Th) wireless network settings were successfully downloaded to your device. However, your Mac
was unable to locate the device on the network.
Please make sure that:
• Your Mac is connected to a wired or wireless network that has access to your device.
• Your device is connected to the wireless network "AC Network".
Fomore information online, visithftp://www.hp.com/o/wirelessprinting"
This is the second HP printer that I am trying to configure that is doing the same darn thing. I thought the first one was faulty, so I exchanged for a slightly different printer. This one has a control screen, so I KNOW that it's on the network. And I KNOW my computer is on the network, or I wouldn't be able to write this.
But they refuse to talk with each other. SO frustrating. I'm ready to give up on HP.
Joe
This question was solved.
View Solution.

Found the problem. HP printers don't support AC Wifi. That would have been nice to know before I wasted 4 hours on 2 printers......

Antenna type in WCS / WLC

Hello, I am still somewhat new to the wireless side and I saw something today while trying to troubleshoot a wireless issue we were having that I have not heard or read about from my CCNA Wireless studies. I noticed that the antenna types our WCS is showing attached to my APs are wrong.
My question is, do the APs / WCS / WLC know what type of antenna is connected to the APs automatically or is this a manual process that someone should assign them? The second question is, if it is a manual process (which I suspect it will be) can I change it without disrupting current connections or should I wait until a maintenance window to do this?
We have 3502e AP with AIR-ANT-1728 and AIR-ANT-5150V-R antennas attached to them, but my WCS says they have the rubber duckies on them. Any insight would be greatly appreciated.
Thank you in advance for any help you can provide!

There is no way the WLC even knows what antennas you have. If your using antennas besides the rubber ducks then you need to define that on WCS. If you have Cisco antennas, there is a drop list of the antennas. You also have to make sure of the antenna orientation. This is all defined in the WCS user guide.
Note
If you have a ceiling-mounted AP with an integrated omni-directional antenna, the antenna orientation does not really need to be set in WCS. However, if you mount that same AP on the wall, you must set the antenna orientation to 90 degrees.
Sent from Cisco Technical Support iPhone App

Envy100 "Device not reachable"

I have searched but could not find an answer to my question and appreciate any input.
I have just purchased an HP Envy 100 and my problem is that I cannot connect it wireless. iMac OS 10.6.7, HP Software 10.6, Airport Xtreme router, I can connect via USB to print but when setting up wireless I receive the following message " device not reachable" the printer provided an ip address in the network settings which i have tried to manually set this on the imac but to no avail. I also have an ipad 4.3.1v that cannot see it and along with an macbook pro 10.6.7v. that i cannot get it to work with. The printer is less than 2ft away from the airport extreme. There are no security password to the network and all computers are using the same network name. I have powered on/off and reset the printer. I have uninstall the printer software and rebooted and reinstalled but no luck.
This question was solved.
View Solution.

Let's start over. From the front of the printer: Setup > Network > Reset Network Defaults. Now, from the same menu run the Wireless Setup Wizard to connect the printer to the router.
Now, on your Mac let's reset the printing system:
- Sys Prefs, Print & Fax
- Right (control) click in the rectangle listing your printers and select Reset Printing System.
WARNING - this will delete ALL of your printers!
Finally, run the software again to connect your Mac to the printer.
Say thanks by clicking "Kudos" "thumbs up" in the post that helped you.
I am employed by HP

Config archive of Cisco 4404/4402 WLC devices

Hi,
I am currently having an issue backing up WLC devices in CiscoWorks LMS 3.2. i can see that from an inventory perspective they are discovered correctly. I have tested the credentials on the CLI and that works fine, but when doing a archive collection from the ciscoworks application it fails, stating that it is a timeout issue.
I have noticed that when trying to connect via the CLI using SSH example below, it does not just prompt for a password, it prompts for the username again, i am not sure if this is the issue
ssh -l test 10.1.2.3
Any assistance will be much appreciated
Kind Regards
James

Hi
telnet output on port 22:
Trying *.*.*.*
Connected to *.*.*.*
Escape character is '^]'.
SSH-2.0-OpenSSH_4.0
Protocol mismatch.
Connection to *.*.*.* closed by foreign host.
Failed info in job output:
CM0151 PRIMARY RUNNING Config fetch failed for hostname Cause: fig from device: java.net.SocketTimeoutException: Read timed out Action: Check if protocol is supported by device and required device package is installed. Check device credentials. Increase timeout value, if required.
dcmaservice.log output:
[ Tue Apr 13 10:46:48 BST 2010 ],INFO ,[Thread-5],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,triggerConfigFetch,52,#### Start of Sweep Tue Apr 13 10:46:48 BST 201
0 ####
[ Tue Apr 13 10:46:48 BST 2010 ],WARN ,[Thread-6033],com.cisco.nm.rmeng.util.DCRWrapperAPIs,getResultFromQuery,3315,SQLException occurred as connection closed. Re-connecting
to DB...
[ Tue Apr 13 10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,769,Inside RMEDeviceContext's getCmdSvc ....
[ Tue Apr 13 10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,774,Protocol and Platforms passed = SSH , RME_WLC
[ Tue Apr 13 10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,786,Iam inside ssh ....
[ Tue Apr 13 10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,787,Initial time_out : 0
[ Tue Apr 13 10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,792,Computed time_out : 60
[ Tue Apr 13 10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getCmdSvc,800,After computing time_out : 60
[ Tue Apr 13 10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getSshCmdSvc,819,inside getSshCmdSvc with timeout : 60000
[ Tue Apr 13 10:46:48 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getSshProtocols,872,Inside getsshprotocols with time out : 60000
[ Tue Apr 13 10:46:54 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.rmeng.util.rmedaa.RMEDeviceContext,getSshCmdSvc,826,SSH2 is running
[ Tue Apr 13 10:47:00 BST 2010 ],ERROR,[Thread-6033],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,error,19,Warning: Received USERAUTH_SUCCESS in response to 'none' authen
tication request
[ Tue Apr 13 10:47:23 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.xms.xdi.pkgs.SharedDcmaWLC.transport.WLCCliOperator,getCmd2Fetch,342,SNMP initialization completed
[ Tue Apr 13 10:47:23 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.xms.xdi.pkgs.SharedDcmaWLC.transport.WLCCliOperator,getCmd2Fetch,349,Current Running image version:NoSuchIns
tance
[ Tue Apr 13 10:47:23 BST 2010 ],INFO ,[Thread-6033],com.cisco.nm.xms.xdi.pkgs.SharedDcmaWLC.transport.WLCCliOperator,getCmd2Fetch,351,Using the latest command as image veris
on is greater than 5.2
[ Tue Apr 13 10:48:25 BST 2010 ],ERROR,[Thread-6033],com.cisco.nm.xms.xdi.transport.cmdsvc.LogAdapter,error,19,IOException received during block() of Channel[UInt32[ 0 ]:UInt
32[ 0 ]]
[ Tue Apr 13 10:48:26 BST 2010 ],ERROR,[Thread-6033],com.cisco.nm.rmeng.dcma.configmanager.ConfigManager,updateArchiveForDevice,678,PRIMARY RUNNING Config fetch Failed for
hostname
[ Tue Apr 13 10:48:26 BST 2010 ],INFO ,[Thread-1],com.cisco.nm.rmeng.dcma.configmanager.CfgThreadManager,run,99,#### End of Sweep Tue Apr 13 10:48:26 BST 2010 ####
SNOOP output:
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56325 Syn Seq=1825561549 Len=0 Win=49640 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56325 Ack=669720941 Seq=1825561550 Len=0 Win=50040
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56325 Ack=669720961 Seq=1825561550 Len=0 Win=50040
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56325 Fin Ack=669720961 Seq=1825561550 Len=0 Win=50040
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Syn Seq=2323886065 Len=0 Win=32850 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56325 Ack=669720962 Seq=1825561551 Len=0 Win=50040
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673581283 Seq=2323886066 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673581303 Seq=2323886066 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673581303 Seq=2323886066 Len=15 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673581303 Seq=2323886081 Len=248 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673581943 Seq=2323886329 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673581943 Seq=2323886329 Len=144 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582407 Seq=2323886473 Len=16 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582407 Seq=2323886489 Len=52 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582459 Seq=2323886541 Len=68 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582495 Seq=2323886609 Len=60 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582547 Seq=2323886669 Len=76 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582583 Seq=2323886745 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673582707 Seq=2323886789 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582775 Seq=2323886789 Len=52 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673582879 Seq=2323886841 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582879 Seq=2323886841 Len=52 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582931 Seq=2323886893 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673582931 Seq=2323886937 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583039 Seq=2323886981 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583083 Seq=2323887025 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583127 Seq=2323887069 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583171 Seq=2323887113 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583215 Seq=2323887157 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583259 Seq=2323887201 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583303 Seq=2323887245 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583347 Seq=2323887289 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673583407 Seq=2323887333 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583407 Seq=2323887333 Len=60 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583467 Seq=2323887393 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673583535 Seq=2323887437 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583535 Seq=2323887437 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673583595 Seq=2323887481 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583595 Seq=2323887481 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583639 Seq=2323887525 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673583707 Seq=2323887569 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583707 Seq=2323887569 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583775 Seq=2323887613 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583843 Seq=2323887657 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583887 Seq=2323887701 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583931 Seq=2323887745 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673583975 Seq=2323887789 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584019 Seq=2323887833 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584063 Seq=2323887877 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584107 Seq=2323887921 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584151 Seq=2323887965 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673584219 Seq=2323888009 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584219 Seq=2323888009 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673584287 Seq=2323888053 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584287 Seq=2323888053 Len=52 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584339 Seq=2323888105 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673584415 Seq=2323888149 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584415 Seq=2323888149 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673584483 Seq=2323888193 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584483 Seq=2323888193 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584527 Seq=2323888237 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673584587 Seq=2323888281 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584587 Seq=2323888281 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584647 Seq=2323888325 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584707 Seq=2323888369 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584751 Seq=2323888413 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584795 Seq=2323888457 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584839 Seq=2323888501 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584883 Seq=2323888545 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584927 Seq=2323888589 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673584971 Seq=2323888633 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673585015 Seq=2323888677 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673585075 Seq=2323888721 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE UDP D=161 S=53008 LEN=77
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673585075 Seq=2323888721 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673585135 Seq=2323888765 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673585135 Seq=2323888765 Len=68 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673585203 Seq=2323888833 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673585735 Seq=2323888877 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673585735 Seq=2323888877 Len=44 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673585735 Seq=2323888921 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673587523 Seq=2323888921 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673587523 Seq=2323888921 Len=36 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Push Ack=673587523 Seq=2323888957 Len=128 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Ack=673587524 Seq=2323889085 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56332 Fin Ack=673587524 Seq=2323889085 Len=0 Win=33072 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56446 Syn Seq=3874994962 Len=0 Win=49640 Options=
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56446 Ack=754769594 Seq=3874994963 Len=0 Win=50040
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56446 Fin Ack=754769594 Seq=3874994963 Len=0 Win=50040
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56446 Rst Seq=3874994964 Len=0 Win=50040
LMS-SERVER -> WLC-DEVICE TCP D=22 S=56446 Rst Seq=3874994964 Len=0 Win=0
Kind Regards
James

WCS/WLC Disabled WLAN still broadcasts! BUG?

Versions 6.0.182.0 on controllers (4 WISMs) and 6.0.132.0 on WCS.
Created a test WLAN which was used for a week or so, WPA2/PSK, broadcast ssid, standard stuff. I no longer wish to use it and set the enabled state in the template to disable and then saved and applied the template to the controllers. On various devices, I can still see it broadcasting! I have even checked on the individual controllers and the WLAN is set disabled, so no WCS sync issue. I also tried switching the broadcast ssid to off and reapplying it and this makes no difference.
If I try to connect to the WLAN, this fails, which is obviously a good thing! I have not tried to delete it yet as there are situations where we need the ability to enable/disable wlans.
Anybody else seen this issue before I report it to TAC?

If the WCS and WLC has been synchronized, you should not see this issue. Since you have already verified and ruled out a sync issue, this looks like a bug.

Prime Infrastructure 2.0 and add a WLC device

Hi,
One question regarding to add a device / WLC Controller into NCS 2.0. I done this in the past with NCS 1.3 without problems
but now I don´t know why but if I add a device into the NCS 2.0 I get the the message CLI Failure / timeout.
I doublechecked all on the controller but I don´t see any failure . For my understanding I have to add a user under"Local Managmeent User " and then add this credentials into the Telnet/SSH Parameters on the NCS 2.0 .
Thanks for help.

Hi Scott,
Upto 7.3 config guide it was documented we have to reboot WLC when we configuring SNMP v3 which is wrong. (here is 7.3 config guide link for reference). May be older version (prior to 7.0) had that requirement, not too sure about it
http://www.cisco.com/en/US/docs/wireless/controller/7.3/configuration/guide/b_wlc-cg_chapter_0100.html#d16741e4514a1635
From 7.4 onwards config guide does not talk about it all. I deleted the default SNMPv3 user & create a new user in 7.4 & add it to prime without rebooting WLC.
Once you configureed a SNMPv3 user on a WLC, I do no think you can edit/change the password. You have to delete the user & recreate it with modified username/password.Then re-add the WLC to prime
The behaviour you mentioned is with any of later codes of WLC ?
Rasika

Problem audit mismatch WCS/WLC for local net user

HI,
I have a problem in my WCS the audit status is mismatch for my two controllers. When I see the details of the mismatch, it is said that all my 400 users are "not present in controller".
However, I checked directly on my web interface of my controllers and my users are there (Security--> AAA--> Local Net Users). I've also checked on the WCS (ConfigureàControllersà controlerà Security à AAA -> local net user).
In both My users are present and are identical.
When i refresh config from controllers on the WCS it disappears but a week after the mismatch comes back.
If anyone can help, Thanks
Alex

Anyone able to answer this one?
We are having the same issue. We had WLC code 7.0.116.0 with WCS giving us mismatches on certain thresholds, despite the fact that the controller and the WCS configs were a match and no one made changes. We would refresh confgi from controller and a week later, the mismatch was back. It's as if there was something wrong with the WCS database. We upgraded to NCS 1.1 and are now on WLC code 7.0.230.0 and it worked for a while, but we are now randomly experiencing the same issues and then some with NCS.
We have a multi-tenant campus that has several of another organizations access points configured as friendly in NCS, but the controllers still had them as rogue and were containing them. We are also experiencing a max client count threshold that is set to 20 on the controller, but NCS is now reverting back to the default 12 value and giving off a mismatch. I don't know if there is a SQL issue with the database or not, but we service roughly 3000 users on a 5 million sq. ft. campus and some of these mismatches and failure to identify critical mismatches is starting to become a problem. Going to open a TAC case, but if anyone has any insight in the mean time, that would be helpful. Thanks!

WCS WLC support

Hi,
We are running version 4.2.62 of Cisco WCS.
I'd like to upgrade to 4.2.128. We run version 4.2.209.0 on our WLCs.
The release notes for WCS version 4.2.128 does not list WLC version 4.2.209 as a supported version.
I would think it would be OK but can anyone confirm if this will actually work?
Also, is it worth upgrading the WCS to the more recent 7x versions?
thanks.

Hi,
The release notes mention with which version the WCS has been tested. So since 4.2.62 WCS came at the same time as 4.2.61 WLC it doesn't state it supports other 4.2 versions since it could not have been tested with those. However, since they are the same major release, all should be ok but you'll maybe face minor bugs here and there.
So just upgrade your WCS to the last 4.2 version of WCS and you'll be good to go :-)
Regards,
Nicolas
===
Don't forget to rate answers that you find useful

ISE, WLC Device Profiling

Hi, I hope someone can provide some advice/assistance. I am currently trialling ISE 1.1.1 on VM with a Cisco 5500 WLC 7.2.110.0. I have configured this setup so clients authenticate to the WLC via 802.1x and use the ISE as a AAA Server. I have setup this configuration so VLAN ID's can be pushed to clients based on their login credentials(from AD), this all works fine. I'd like to take this on a step further and differentiate users and their devices based on their device type, iPhone, iPad etc. I have enabled DHCP profiling on the WLC. I only seem to be able to identify a device based on their DHCP hostname, should it contain iPhone etc, is there another way I can get more information from the clients or their initial 802.1x communication? I want to use 802.1x as given the nature of the users connecting the VLAN push based on credentials is key to my possible deployment.
My second query is relating to VLAN pushing on a Flex Auth AP. I've got a remote site with some AP's, it is over a L3 connection. I have my WAP at this site registered to the WLC. Over my sites I have standard VLAN numbers and IP address ranges, site 1 is x.1.a.x, x.1.b.x etc, site 2 is x.2.a.x, x.2.b.x etc. What I would ideally like to do is push VLAN's to the Flex Auth WAP's so that users in site 2 get a site 2 IP address and can use local switching for printing and other local activities. Is this supported? I know it wasn't in H-REAP when I trialled ISE/WLC 4400 last year. I tried to configure this and it looks like users always get IP addresses from site 1.
Thanks for any advice/assistance.
Kenny.

Kenny,
For the first part of your question there is no more information you can get outside of the dhcp hostname (which will get you the info you are looking for) and the mac address (which only gets you to the Apple Device policy). If you do not want to perform any redirection, then your best bet is to use a span to span all the traffic over to the ISE node in order to span the http traffic in order to profile the devices using the http user agent string.
As far as your 2nd question- the flex auth aps do not support COA and arent a "supported network access device" from Cisco's webpage.
http://www.cisco.com/en/US/docs/security/ise/1.1.1/compatibility/ise_sdt.html#wp55038
However the APs do support dynamic vlan assignment. So once an endpoint connects to these APs you can set them on the vlan once, however if you are performing posturing and need coa to place them in another rule once a decision has been made then this is where the deployment will break.
http://www.cisco.com/en/US/products/ps11635/products_tech_note09186a0080b7f141.shtml
thanks,
Tarik Admani
*Please rate helpful posts*

WCS & WLC version compatibility

Are there any compatibility issues between WCS version 7.0.164.0 and WLC version 7.0.116.0?

Hi Jason,
Table 1 WCS Versions
WCS Version Supported Controller Versions Supported Location Server Versions Supported MSE Versions Release Date Upgrade Supported From Operating System Requirement
7.0.172.0
7.0.116.0
7.0.98.218
7.0.98.0
6.0.202.0
6.0.199.4
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
4.2.209.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.202.0
7.0.201.0
April 2011
7.0.164.3
7.0.164.0
6.0.202.0
6.0.196.0
6.0.181.0
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
7.0.164.3
7.0.98.0
6.0.202.0
6.0.199.4
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
4.2.209.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.103.0
7.0.105.0
December 2010
7.0.164.0
6.0.196.0
6.0.181.0
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
7.0.164.0
7.0.98.0
6.0.202.0
6.0.199.4
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
4.2.209.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.103.0
7.0.105.0
June 2010
6.0.181.0
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
6.0.202.0
6.0.202.0
6.0.199.4
6.0.199.0 (pulled from CCO)
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.209.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.202.0
6.0.202.0
April 2011
6.0.196.0
6.0.181.0
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
6.0.196.0
6.0.199.4
6.0.199.0 (pulled from CCO)
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.209.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.102.0
6.0.105.0
15 July 2010
6.0.181.0
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
6.0.181.0
6.0.196.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.101.0
6.0.103.0
17 Feb 2010
6.0.170.0
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
6.0.170.0
6.0.188.0
6.0.182.0
6.0.108.0
5.2.193.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.97.0
6.0.97.0
8 Nov 2009
6.0.132.0
5.2.148.0
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
6.0.132.0
6.0.182.0
6.0.108.0
5.2.178.0
5.2.157.0
5.1.163.0
5.1.151.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
6.0.85.0
6.0.85.0
11 June 2009
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.2.148.0
5.2.193.0
5.2.178.0
5.2.157.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
5.2.100.0
5.2.100.0
25 June 2009
5.2.130.0
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.128.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.2.130.0
5.2.178.0
5.2.157.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
5.2.91.0
5.2.91.0
21 Feb 2009
5.2.125.0
5.2.110.0
5.1.65.4
5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.2.125.0
5.2.178.0
5.2.157.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
5.2.91.0
5.2.91.0
10 Feb 2009
5.2.110.0
5.1.65.4
5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.2.110.0
5.2.157.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
5.2.91.0
5.2.91.0
24 Nov 2008
5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.1
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.1.65.4
5.1.163.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
5.1.35.0
5.1.35.0
9 Jan 2009
5.1.64.0
5.0.72.0
5.0.56.2
5.0.56.0
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.x
RHEL 5.x
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.1.64.0
5.1.151.0
5.0.148.2
5.0.148.0
4.2.176.0
4.2.173.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
5.1.30.0
5.1.30.0
21 July 2008
5.0.56.2
5.0.56.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
Windows 2003 SP2 32-bit
RHEL 5.1
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.0.72.0
5.0.148.2
5.0.148.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.38.0
Not Applicable
5 Aug 2008
5.0.56.2
5.0.56.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
Windows 2003 SP2 32-bit
RHEL 5.1
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.0.56.2
5.0.148.0
4.2.61.0
4.1.x.x
4.0.33.0
Not Applicable
14 Apr 2008
5.0.56.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
Windows 2003 SP2 32-bit
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
5.0.56.0
5.0.148.0
4.2.61.0
4.1.x.x
4.0.32.0
Not Applicable
16 Feb 2008
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
Windows 2003 SP2 32-bit
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
4.2.128.0
4.2.207.0
4.2.205.0
4.2.176.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0
3.1.43.0
Not Applicable
13 May 2009
4.2.110.0
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0
Windows 2003 SP2 32-bit
RHEL 4.0
RHEL 5.0 (5.1 and later no supported)
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
4.2.110.0
4.2.176.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0
3.1.42.0
Not Applicable
29 Sep 2008
4.2.97.0
4.2.81.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0
Windows 2003 SP2 32-bit
RHEL 4.0
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
4.2.97.0
4.2.176.0
4.2.130.0
4.2.112.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0
3.1.38.0
Not Applicable
3 Jun 2008
4.2.81.0
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0
Windows 2003 SP2 32-bit
RHEL 4.0
RHEL 5.0
Windows/RHEL on ESX 3.0.1 and above
No support for 64 bit
4.2.81.0
4.2.99.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0
3.1.36.0
Not Applicable
17 Mar 2008
4.2.62.11
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0
Windows 2003 SP2 32-bit
RHEL 4.0
RHEL 5.0
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
4.2.62.11
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0
3.1.35.0
Not Applicable
25 Jan 2008
4.2.62.0
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0
Windows 2003 SP2 32-bit
RHEL 4.0 Update 5
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
4.2.62.0
4.2.61.0
4.1.185.0
4.1.171.0
4.0.216.0
4.0.206.0
4.0.179.11
4.0.179.8
4.0.155.0
3.1.35.0
Not Applicable
9 Nov 2007
4.1.91.0
4.1.83.0
4.0.100.0
4.0.97.0
4.0.96.0
4.0.87.0
4.0.81.0
4.0.66.0
Windows 2003 SP2 32-bit
RHEL 4.0 Update 5
Windows/ RHEL on ESX 3.0.1 and above
No support for 64 bit
http://www.cisco.com/en/US/docs/wireless/wcs/release/notes/WCS_RN7_0_172.html
Cheers!
Rob
PS: +5 to my friend Leo using the invisible Stars

WCS/WLC read-only access

We use WCS and AAA in our wireless environment. Reading through the WCS user guide (http://www.cisco.com/en/US/docs/wireless/wcs/5.2/configuration/guide/5_2manag.html#wp1089936) , authorization seems awfully course grained. Is there a way to provide a security group with login and read-only rights to all aspects of all wireless components (or at least to WCS and all WLC)? Ideally, the security group would be able to login to any WLC at any time and verify settings, etc.

Hi,
We need to follow following document to ensure that user with which we are logging in has the appropriate attributes assigned,
http://www.cisco.com/en/US/tech/tk722/tk809/technologies_tech_note09186a0080851f7c.shtml
What different roles means, please go through following document,
http://www.cisco.com/en/US/docs/wireless/controller/4.1/configuration/guide/c41sol.html#wp1208657
HTH
Regards,
JK
Plz rate helpful posts-

WCS/WLC and Wii

All,
I am on a University campus where we allow students to plug in there game consoles into our network for online gaming. We recently purchased a WCS solution from Cisco and deployed it this summer. The students coming to campus have brought in their Wii consoles and are unable to connect to the network.
I have attempted to use the Wii with an Access Point prior to joing the WCS system but once it is joined it will no longer connect. Is there a setting within the WCS system that needs to be tweaked to allow Wii connectivity?
Best Regards.

Rob,
Thank You for the response. We spent several days troubleshooting this this week with Cisco and came to a resolution although not an ideal one.
Problem Statement: Nintendo Wii Wireless consoles would not work with Cisco access points once they are added to the Wireless Lan Controller (WLC) solution. The Light Weight Access Point (LWAPP) would receive DHCP requests from the Wii and the DHCP server would send back an Offer but the Wii would not acknowledge the offer and would not accept a DHCP address. If the same model autonomous access point is used (not WCS/LWAPP) the Wii works as expected.
Infrastructure background: Our DHCP server is a Unix platform which must DHCP Relay through a Cisco Clean Access (CCA) solution and then DHCP Relay through the WLC solution. Somewhere in all the relaying an address was changing that the Wii console could not understand and as a result never got the DHCP address. We are not using any encryption at this time.
The solution: By creating a new DHCP scope and placing it directly on the WLC systems we were able to bypass any DHCP relaying and provide the address directly from the WLC to the Wii console. We are aware of at least one additional institution whose DHCP infrastructure is the same as ours who is also using CCA who had the exact same problem. They claim that a Nintendo Wii running firmware version 2.x will work with their system but once it is upgraded to 3.x it fails to connect. We haven't been able to validate that for ourselves but if this was the case, it would seem that Wii software version 3.0 handles DHCP a little differently than 2.0.
Regards

Campusmanager 3.1, unconnected devices are reachable and CDP works fine

Hi,
our customer has the following installation: CD-One 4th-edition on Win2000-Server.
The campusmanager does not show all cat2950 wich are connected to cat 3550-12G with enhanced image. Each uplink to the 2950 is configured as "switchport mode access" and one (same) vlan is assigned on both side. I can see the cdp neighbors completely on both switches. But it is impossible to integrate the 2950 into the campusmanager.
Tese devices are presente as unconnected devices with status reachable.
Where is the failure.
Best regards.
Volker

Since you're using Campus 3.1, are the Cat2950 and 3550-12G showing up with the correct icon on the map?. Since, I don't see these listed in the Supported Device List at:
http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cw2000/camp_mgr/sup_dev/dev_spt.htm

WCS -- WLC "Device un reachable"

Similar Messages

Maybe you are looking for