802.11 n support in Wism and WCS

Is the new wless standard 802.11n is supported in current shipments of Cisco WLC 44XX and WiSM ( 6500 wireless controller card) ?
Also I need to know whether is is supported in WCS 4.1 ?

Hi Nalaka,
Yes, 802.11n is supported on the WISM and WCS starting with the following releases in the 4.2 train;
Release Notes for Cisco Wireless LAN Controllers and Lightweight Access Points for Release 4.2.61.0
http://www.cisco.com/en/US/docs/wireless/controller/release/notes/crn4200.html#wp302677
The following new features are available in WCS 4.2.62.0
802.11n support-The introduction of the Cisco Aironet 1250 series access point, a business-class access point based on the IEEE 802.11n draft 2.0 standard. The access point offers combined data rates of up to 600 Mbps to meet bandwidth requirements. Cisco WCS display screens include a listing for configuring, managing, and monitoring 802.11n access points and their associated wireless LAN controllers.
The newest WLC and WCS 5.0 trains are now released as well :)
Hope this helps!
Rob

Similar Messages

Adding a secure WLAN - WISM and WCS

I have a setup including a WISM and WCS which currently only runs a guest service using webauth to get online. The service (by request) is not secured over the air. I would like to implement a second SSID with security but before going the whole way with 802.1x I wanted to implement a half way house. Service will still only be a guest service but I want the air traffic secured.
So I guess my options are WEP (forget it) or WPA/WPA2.
My question is do I have to run this service with a shared secret that I then need to inform all users of in order for them to be able to connect to the service or is there a way to implement a WPA service that uses some kind of credential check against the already configured RADIUS (ACS) servers?
And if this is possible I assume there is no longer need for a webauth as this just seems to duplicate the login process.
Thanks for any pointers in advance
Paul

The best thing you can do is start with the Configuration Guides. If you don't have a test environment and have SMARTNET on the WiSMs/ WCS, utilize TAC to help you get up and going. I would also suggest utilizing a Cisco Partner to help with the initial implementation as well.
I would recommend upgrading your WiSMs and WCS to the latest versions and making sure configurations are the same across modules. I upgraded our WiSMs from 4.x to 7.0.98.0 and WCS to 7.x. Ran into a bug here and there but that is expected. Just make sure the wireless devices support those versions. If you are unsure, you can always work towards the AssureWave tested code. WCS 7.x should be backwards compatible (check the release notes just to verify). The Design Zone and Release Notes are your friend too.
-Rick

How to create guest access in wireless by WISM and WCS and ACS?

dear sir
i neeed to know the steps of how we can make guest access to our network like hotels by using our WISM v 7.0.220 and wireless control system and ACS ?

You need to define your requirements a little bit. The WLC can do WebAuth and an employee can access either the WLC or WCS to put in the username and password credentials, but you would need to figure out what's best for you.
Here is a support doc that you can reference.
https://supportforums.cisco.com/docs/DOC-13954
Sent from Cisco Technical Support iPhone App

WiSM and WCS Issues

1. WiSM code 4.1.171. When a user login using a wrong password and failed, WiSM still counts it as a login session. So when the same user try to login from another computer, he may get the error about too many login sessions. I think if the login fails, the WiSM should not count it as a login session.
2. Just upgraded to WCS 4.1.83 on Windows 2003 server. Once log out from the console, the WCS stops. Anyone sees this problem?
Zhenning

RE #2. In case you haven't figured this one out yet, it's a bug. Seems WCS gets started as an app instead of service regardless of config. You'll sometime notice when you exit the console (or term svc console) that you briefly see a black dos box screen & then it closes. Then wcs is no longer running. Fixed in later versions supposedly.

1230 Series LAP and WCS 6.0.199.0 Heatmap Problem

I recently upgraded from WLC 4.2.207.0 to 6.0.199.0 (WiSM), and WCS 5.2.130.0 to 6.0.196.0. All my heatmaps that contain 1231G LAPs are solid "maroon" (-35 dBm) in color. If I remove the 1231 APs from the heatmap selection on the right hand side, my coexisting 1131 and 1142's display their heatmaps properly. My maps are all CAD format (dwg) converted to .png's using WCS. My goal is to migrate to 802.11n in small steps which our Cisco rep said we could do. Any ideas?

Unfortunately, this is a bug in 6.0.199.0. The "fix" is to upgrade to 7.0.98.0 or 6.0.199.4. As you figured out, it only affects 1230 series APs, and only on the 802.11b/g side. Bug ID was
CSCti05687
Incorrect power unit was used on AIR-AP1231G-A-K9 and IR-AP1220-IOS-UPGRD.

Why doesn't the AEBS 802.11n support NTFS?

I am wondering why users need to go through hoops to make the $200 AEBS 802.11n recognize NTFS formatted disks. Is it really that complicated for Apple engineers to add this support? Is there any way to reach Apple tech and request this? Or is asking for NTFS support utterly ludicrous and fundamentally not feasible. If it is futile to hope for Apple to add support for NTFS to the AEBS 802.11n, then how does one go about returning - who to contact to return and get the money refunded.

Hello durlov. Welcome to the Apple Discussions!
... how does one go about returning - who to contact to return and get the money refunded.
Here is Apple's Return and Refund Policy.

Mitel phone 802.1x with Cat 3560 and Cisco ACS5.2 problem

I am piloting an 802.1x implementation for a client who has Mitel IP Phones. I have setup the switch and ACS based on previous experience and a windows PC can authenticate onto the network OK. When I use a Mitel phone however, it seems to skip past the first 802.1x LCD message and goes straight to LLDP and DHCP discovery, which obviously fails. The phone are 5224s and the controller is on the original v10 release. I have cleared the 802.1x config on the phone and rebooting as per Mitel documentation which leads me to believe it should then prompt for a user/pass on next reboot. It does not do this.
I known the ACS is setup to support EAP-MD5 and I have tried all the various types of host modes including the default and Multi-Auth, Multi-Domain and none of them seem to make any difference. I have tried with and without a PC attached to the phone as well.
A wireshark shows the EAP identity request from the switch, and I see an EAP response from the phone, although it is slightly different to the PC's response. In the end the phone issues an EAP 4 failure message. So something in that EAP conversation doesnt seem to work. Does anybody have an experience of this?

A wireshark capture shows a difference in the EAP request message from a Cisco Cat 3560 (12.2.55) to the Mitel, compared to a HP Procurve to the Mitel which the Mitel responds to:
Cisco EAP Request trace:
Frame 17 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: Cisco_99:06:84 (00:1e:49:99:06:84), Dst: Mitel_2c:ad:3b (08:00:0f:2c:ad:3b)
    Destination: Mitel_2c:ad:3b (08:00:0f:2c:ad:3b)
    Source: Cisco_99:06:84 (00:1e:49:99:06:84)
    Type: 802.1X Authentication (0x888e)
    Trailer: 000000000000000000000000000000000000000000000000...
802.1X Authentication
   Version: 3
    Type: EAP Packet (0)
    Length: 5
    Extensible Authentication Protocol
        Code: Request (1)
        Id: 1
        Length: 5
        Type: Identity [RFC3748] (1)
HP EAP Request trace:
Frame 36 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: Procurve_03:b7:40 (00:1b:3f:03:b7:40), Dst: Mitel_42:f5:21 (08:00:0f:42:f5:21)
    Destination: Mitel_42:f5:21 (08:00:0f:42:f5:21)
    Source: Procurve_03:b7:40 (00:1b:3f:03:b7:40)
    Type: 802.1X Authentication (0x888e)
    Trailer: 000000000000000000000000000000000000000000000000...
802.1X Authentication
    Version: 1
    Type: EAP Packet (0)
    Length: 15
    Extensible Authentication Protocol
        Code: Request (1)
        Id: 1
        Length: 15
        Type: Identity [RFC3748] (1)
        Identity (10 bytes): User name:
The HP seems to be requesting a User name as a string in the Identity field, whcih the Mitel phone then responds with an EAP response packet with an identity of MITEL.
The other difference seems to be that a Version code of 3 is being used by the Catalyst but Version 1 by the HP and Mitel phone.
Any ideas anyone?

Ask the Expert: Cisco's 802.11ac Solutions - Deployment, Design, and Interop

Ask your Questions on Cisco’s 802.11ac Solutions - Deployment, Design, and Interop with Cisco Experts: Richard Hamby and Shankar Ramanathan.
Monday, March 30th, 2015 to Friday, April 10th, 2015
Richard Hamby is a senior technical support engineer and Team Lead of the Cisco Technical Assistance Center in Richardson, Texas. He is an expert in Indoor and Outdoor wireless for the full line of Cisco Unified and Converged Access Wireless products, as well as TAC Engineering Engagement Engineer liaison to project engineering teams for new Cisco wireless products. Prior to his current role, Richard was a customer support engineer with the AAA Security TAC team supporting Cisco identity management solutions and been with Cisco since 2009.
Shankar Ramanathan is a Customer Support Engineer at the Cisco Technical Center. He is a Technical Content Engineer and Subject Matter Expert for Cisco Enterprise Unified and Converged Access wireless mobility solution including Wireless LAN Controller 2500/5500/WISM2/7500/8500, Converged access 5760/3650/3850 switches, Access Points Lightweight and Autonomous, VoWLAN (792x/9971) , Cisco Prime Infrastructure SNMP management, Cisco Mobility Services Engine(MSE/ CMX). Prior to joining Cisco in November 2011, he worked as a wireless network engineer at Elan Technologies, responsible for RF wireless network planning, simulation, propagation path analysis, and optimization of Wi-Fi 802.11 mesh and WiMax (802.16 d/e) networks for various system integration and automation projects. Shankar holds a master of science degree in electrical engineering specializing in communications and signal process from the State University of New York, Buffalo. Shankar has a CCIE in Wireless(#40548) and CCNA certified (number 410004168640IMZF) and has over six years of industry experience.
Find other https://supportforums.cisco.com/expert-corner/events.
**Ratings Encourage Participation! **
Please be sure to rate the Answers to Questions

A common question we are asked is 'why is my device not achieving 11ac data rates?'
One of the most common answers relates to client compatibility/capability. To get the highest possible data rates of 11ac (assuming proper distance and RF health), the AP and the client device must both be capable supporting the requirements - 5GHZ, 80MHz Channel, short guard interval, 3 spatial streams. Each spatial stream has a max of 433.3Mb/s (at 80MHz, short GI).
The majority of 11ac-capable wireless cards on the market do not support 3 spatial streams. Most adapters in wireless-capable devices are 1SS or 2SS. For example, the Intel 7260 11ac adapter used in many devices is a 2SS adapter - therefore it's max possible data rate is 866.7. Another common adapter in use is the 11ac Broadcom 3SS that Apple uses in the newer Macbooks. These devices can achieve the 1.3GBs PHY data rate.
This guidance is the same for 11n adapters as well. To achieve max rate, your 11n AP and adapter must both support 40MHz channels, 3SS, short GI.
Note: The 11n and 11ac standards both define support for 4SS. 4SS-capable devices are rare, so 3SS is essentially our reality.
One of the most useful references for questions related to this topic is the AP Data Sheet for each AP. Here's the AP3700 for example:
http://www.cisco.com/c/en/us/products/collateral/wireless/3700-series-access-point/data_sheet_c78-729421.html
Table 1 lists the expected data rate per MCS Index value by #SS at each channel width and GI. Indexes 0-7 are the same for 11n and 11ac (11n limited to 40MHz channels of course). And MCS 8 & 9 are 11ac-only 256-QAM modulations.

Cisco CSM and WCS on same server

Hi,
Currently we are running Cisco CSM and Cisco WCS applications on different servers.
Please let me know can it possible to install Cisco CSM and Cisco WCS on one server.
Regards,

As per their datasheet, both CSM and WCS support VMware or can run as virtual servers. So it should be possible to implement both as virtual servers and run on the same physical server.

WinPE 5 802.1x Support with SCCM 2012 R2

Please see updated information a few posts down.
I am trying to get 802.1x support working to deploy windows 7-8 machines using MDT2012. I have checked IEEE 802.1x network authenication protocol under features of the deployment share properties. I am trying to follow the guide on the deploymentguys.
I have my files on the boot image and can do a net start dot3svc, we are not using certificates at the moment for our 802.1x so I am skipping that line. doing a netsh lan add profile filename="X:\8021x\ Local Area Connection.xml " interface="Ethernet2"
does work. I am having a problem with the third step when I run the following command netsh lan set eapuserdata filename=x:\8021x\Wired-WinPE-UserData-PEAP-MSChapv2.xml allusers=yes interface="Ethernet2" All i get is error setting
user data for interface ethernet2, the operation is not supported.
How does one get 802.1x working in WinPE 4.0?
Heres the latest updated in this first post so you dont have to scroll way to the bottom to get the latest relevant information:
So here's the current situation and hopefully someone has seen it before.
My boot image has the prestart command set to x:\8021x\configure8021x.cmd. If i make a USB boot media this command will run and work with an 8021x wire plugged in. If I PXE boot with a non8021x
wire plugged in this command will run. If I PXE Boot with an 8021x
wire plugged in it does not run the command. If the boot image gets staged from the windows software center it
also will not run my command.
Does anyone know why the staged boot image and booting from PXE are not running my prestart command? It seems that during PXE and staged boot that the network initializes BEFORE it runs any prestart commands?

Well progress on this issue has been made. So why I was getting the operation not supported is because I was exporting our corporate 8021x LAN profile which gets put in place by group policy, which i assumed would work. So i unjoined the windows
7 machine from the domain and was then able to modify the LAN profile to be what is exactly in the documentation with images.
Then the above command works and I no longer get the operation is not supported and I am able to move on to the next steps which is to create a script file which contains the net start and the netsh commands i was using above to test it. Great!
Now my next issue comes up when the instructions tell me to modify the winpeshl.ini file which it says is located at X:\windows\System32\Winpeshl.ini. So I mount the boot.wim file that I did earlier and I browse to the location in question however
the first thing I notice is that when I open the winpeshl.ini file to go to modify it I expect to see:
[LAUNCHAPPS]
“%SYSTEMDRIVE%\sms\bin\i386\TsBootShell.exe”
Instead what I find is it says:
[LAUNCHAPPS]
%Windir%\system32\netstart.exe, -prompt%SYSTEMDRIVE%\sources\recovery\recenv.exe
So I thought ok I will create a copy of this file and rename it to winpeshl.ini.bak and then modify it to say what It says it should be in the instructions which is:
[LAUNCHAPPS]
winpeinit.exe
%SYSTEMDRIVE%\Windows\System32\wscript.exe, %SYSTEMDRIVE%\8021x\Configure8021xUser.wsf
“%SYSTEMDRIVE%\sms\bin\i386\TsBootShell.exe”
Next I unmount the boot.wim file and overwrite the copy I had. Next I update the distribution points and PXE boot a test machine. What I see next is
what I dont understand. Upon booting and hiting F8 to get to a command line I cd into x:\windows\system32\ and notice that I do indeed still have my winpeshl.ini.bak file so I open the winpeshl.ini file I had thought I modified earlier and low and behold
it contains this which is different when I look at it when I mounted the wim file:
[LAUNCHAPPS]
“%SYSTEMDRIVE%\sms\bin\i386\TsBootShell.exe”
So something is modifying this file and setting it this way effectively overwriting what I put in so that my script can run and configure the 8021x user settings.
Is there some updated documentation somewhere, how do I proceed from here??
The next steps after this would be to modify the unattend.xml file at a certain location to run the Configure8021xUserWindows.wsf script which does the winpe script just instead
of running from X: it runs from C: as it says in the documentation. But I can't move on to test this yet without getting the winpe part working.

No 802.11n support in macbook pro leopard install

I upgraded my MacBook Pro to Leopard last week (and then updated to 1.5.1 yesterday)
Other users here have claimed that they see 802.11n support in the Network utility (choosing en1 as the Network Interface). However, I do not. I only see a/b/g.
I also went ahead and purchased the 802.11n enabler (for $2.16). I got an error message that the software is incompatible with my hardware. My guess is that the enabler is probably incompatible with Leopard - although the Apple Store says nothing about this.
Why did others get 802.11n installed automatically via their Leopard upgrade but in my case it did not?
How do I upgrade my MacBook Pro (10.5.1) to 802.11n?
Thanks,
Bill

I just realized that I don't have the right mbpro for 802.11n as I don't have core 2 duo.
***** to be me I guess.
I'll look for an after market solution to upgrade to 802.11n.
Thanks.

Help Enabling 802.11b Support

Can anyone help? All I want to do is enable 802.11b support on my Cisco 877W. My 802.11g clients can see and attach to it no problems. My 802.11b clients cannot see it at all. I have tried all sorts but nothing has helped. My config looks like this:
interface Dot11Radio0
no ip address
encryption key 1 size 128bit 7 BC48CE99C4E9B683819990D3C1A5 transmit-key
encryption mode wep mandatory
ssid *****
authentication open
speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0 12.0 18.0 24.0 36.0
48.0 54.0
station-role root
no dot11 extension aironet
bridge-group 1
bridge-group 1 spanning-disabled
What do I need to add to make it visible and available to 802.11b clients?
Many Thanks,
Matt

I'd start by defaulting the AP back to factory default, no WEP, no authentication.
Check to see if the 802.11b clients can connect.
If all the 802.11b clients are running the same software, check to see that they are up-to-date drivers & client software. If you're using the MS client software (Zero Wireless Config) try a client using the vendor's client software instead.
If the clients are not eve associating, look at the basic parameters: things like preamble length (legacy default is "long" which is a one meg data rate)
If you can get the 802.11b client to connect whith all open parameters, then add WEP. Be advised that some clients need the WEP entered as HEX, not ASCII.
For example ASCII "ABCD" would be "41 42 43 44" in hex ... make sure you're using the same system. IF youre using something like "12345abcde" that can be a valid (but incorrect) hex string when ou really intend for it to be ASCII.
Also note that leading or training spaces (ASCII 20) are valid characters. Make sure you do not have leading or training spaces in your WEP (unless you really want them there, in whch case, make sure they're there)
Make sure the Ethernet format is correct: use the Web GUI to set up. Check the parameters on the "Interfaces" page and do not (at least initially) use the "Best throughput" or "Best Range" settings, leave it at "Default Settings"
If your 802.11b clients are PDAs, bar-code scanners, or other hand-held devices, check that they are at default settings for the standard 802.11b protocols; some use proprietary protocols for better performance or security.
That's about it for me ... let us know if any of that changes (works / doesn't work, but acting differently / doesn't work, looks the same).
Good Luck
Scott

How fast can Broadcom 802.11n support for maximum?

hey everybody,i got U160 yesterday that the WLAN adapter is Broadcom 802.11n but i just got a connection speed of 65Mbps but i can get 150 Mbps with my G230 with intel 5100 bgn ,connecting to the same N-Router,so i am wondering how fast can Broadcom 802.11n support for maximum.......

if readycomm installed, remove it.
check your firewall is active and using high performance.
by the way, which model of broadcom are you using?

Complex problem: 802.11n, Bluetooth, Iphone 4 and Magic pheripherals...

Hi folks,
My hardware:
- Macbook Pro with Apple LED Cinema Display
- Magic Mouse, Trackpad and Wireless Keyboard
- Time Capsule as WiFi Router
- Apple TV
- Iphone 4
- Airport Express as WiFi printer connection
My problem:
- As known, time machine backup causes lags on BT devices when WiFi is run in 802.11n (b/g compatible) and switching to 802.11n only (5GHz) solves the problem. I solved the problem with my WiFi printer (Samsung 4500W, 802.11b/g) by connecting it to my Airport Express.
- The persisting problem is that my Iphone 4 only supports 802.11n (2,4GHz) and this frequency seems to still interfere with BT so at this point I have to live with the following: Using my Iphone as a remote in my Apple-powered network with lags on BT peripherals OR using BT peripherals in a 802.11n (5GHz) environment without using my Iphone 4 in the WiFi.
Does anyone know a solution to this?
And if the guys from Apple read this:
- Please update my Iphone to 802.11n (5GHz)
- Please remove the f...... mouse acceleration in Lion ;-)

When connected to the wi-fi network, on your iPhone go to Settings > Wi-Fi. Select the right facing arrow in a blue circle icon to view the wi-fi network settings. Select Forget this Network at the top.
Follow this by rejoining the network.
If no change after this, on your iPhone go to Settings > General > Reset and select Reset Network Settings. This will erase all wi-fi network settings for all wi-fi networks you have connected your iPhone with and will require re-joining every wi-fi network you have access to including your own.

Can't connect to Time Capsule + no 802.11n support

I just got my new 13" MacBook (late 2008). Originally, I thought I couldn't connect to my wireless N router which happens to be Apple Time Machine. According to network utility program, my MacBook only supports a/b/g - this is not right! Now, I discover that in addition to the N problem I can't even connect to my Time Capsule wirelessly! Good thing I have 2 separate wireless routers (linksys).
My other Macs (white MacBook and 20" iMac) have no problem connecting to Time Capsule over 802.11n. Both machine indicates 802.11n support under network utility program.
Compound this problem with stuck 'a' key on my keyboard.
I really, don't get this problem. I spent an hour with Apple tech with no avail. I am thinking about returning this new MacBook.

I have the exact same problem you have described. Unable to find a solution. Odd because I have a 2007 MacBook Pro and it works fine wirelessly. Wireless-N on the MacBook works fine and it can connect to other wireless networks, just not it's home one.
If anybody is interested, here's a dump from the console log when airport attempts to connect. Our wireless station doesn't broadcast.
Macintosh-6 airportd[6001]: Could not find any preferred networks; trying broadcast requests..
Macintosh-6 airportd[6001]: Broadcast requests also failed..
Macintosh-6 airportd[6001]: Probing highest ranked networks via directed scan..
Macintosh-6 kernel[0]: AirPort: Link Up on en1
Macintosh-6 kernel[0]: AirPort: Link Down on en1
Macintosh-6 airportd[6001]: Error: Apple80211Associate() failed -25
Macintosh-6 mDNSResponder[20]: setsockopt - IPMULTICASTIF error 169.254.141.134 -1 errno 49 (Can't assign requested address)
Macintosh-6 configd[14]: rtmsg: error writing to routing socket

802.11 n support in Wism and WCS

Similar Messages

Maybe you are looking for